If you need… | Choose… |
---|---|
Standardized experiences for many customers | Plan Template |
Custom rates, terms, or structures for a single customer | Plant Template with overrides |
Component prices | Term | Billing period |
---|---|---|
2 Monthly usage charges | Monthly | Monthly |
2 Monthly usage charges, Annual platform fee | Annual | Monthly |
Monthly charge for storage, Quarterly charge for services, Annual platform fee | Annual | Monthly |
Quarterly charge for services, Annual fee | Annual | Quarterly |
Status | Description |
---|---|
upcoming | The subscription’s start_date is in the future. Sending usage data for the corresponding customer will not be associated with any charges since there is no active subscription. |
active | The subscription is currently active, and may accrue charges as usage events are ingested. |
ended | The subscription’s end_date is in the past, likely as a result of a cancellation. |
requested_date
(via the cancel subscription endpoint) is the effective date. Note that backdated cancellations are allowed only if there are no paid invoices between the action date and the requested date. In these examples, assume that the subscription bills $50 monthly up front, and has a usage based fee.
Subscription start date | Cancellation action date | Cancellation effective date | Behavior |
---|---|---|---|
01-01-2022 | 01-15-2022 | 01-13-2022 | Consistent with prorations for in-advance fees, Orb will generate a balance refund for the unused time for the month of January, and an in-arrears invoice capturing any usage from 01-01 to 01-13. |
01-01-2022 | 01-15-2022 | 01-01-2022 | Orb will void the invoice issued on 01-01, and generate no further invoices. |
01-01-2022 | 02-15-2022 | 02-01-2022 | Orb will void the invoice issued on 02-01 which includes the upfront charge for February, and issue a new invoice for 02-01 capturing the usage for the month of January. |