Orb now allows you to anchor your billing cycles to a custom date. Previously, you were able to specify the day of the month on which billing cycles were anchored. Now, you're able to specify a full date.
For example, a quarterly subscription anchored on March 16, 2024 with a start date of October 10, 2023 and an end date of March 16, 2024 would have the following billing periods: October 10, 2023 - December 16, 2023, December 16, 2023 - March 16, 2024.
Orb now supports specifying a custom billing cadence or one-time service period. Previously, prices could only recur monthly, quarterly, semi-annually, or annually. Now you're able to specify a custom duration in days or months. You can also now specify a custom service period duration for one-time prices, which determines the duration of the line item.
The new billable metric "Debugging" tab enables you to test your metric before publishing. It shows you the result of evaluating the metric for a customer over a time range without needing to create a subscription. To create a new metric, we recommend the following workflow:
We've added a "maximum spend" concept to our pricing models! This allows you to configure plans with a spend-cap at the price or the plan level from the plan or subscription creation flows.
We've also added support for limiting spend on an individual invoice at the line item or invoice level through the existing invoice edits flow.
Plans in Orb can now be configured with prices in a combination of custom credits and real-world currencies. The custom credits concept backs Orb's prepurchase ledger.
When configuring a plan, each price can be in either credits or the plan's invoicing currency. If the user subscribed to a mixed credits/currency plan and has pre-purchased credits, prices in credits will draw down from the pre-purchase balance, and any overage will be invoiced at the end of the billing period at the configured 'price per unit' rate for credits.
Learn more about working with prepaid balance in Orb's docs.