We've released a redesign of the Plan Version Migration creation flow, to increase transparency and safety when running migrations. The new flow more clearly states what to expect, and you can now also review each subscription by previewing the invoices that will be created as a result of the migration.
Previewing invoices:
We’re excited to introduce a new webhook event: customer.balance_transaction_created. This webhook notifies your systems whenever a balance transaction is created for a customer, for example, when the balance is added via a refund credit note or deducted during invoice issuance.
To start using this webhook, configure your webhook endpoints in the Orb dashboard and ensure your systems are set up to handle the customer.balance_transaction_created event.
For more details, refer to our webhook documentation.
We’re excited to announce the launch of our officially supported Ruby SDK! You can integrate seamlessly with Orb in your Ruby projects using the orb-billing gem, available on RubyGems.org.
To get started, add this line to your Gemfile:
gem 'orb-billing', '~> 0.1.3'
Or install it directly with:
gem install orb-billing
Ruby now joins our growing SDK family alongside Python, TypeScript, Go, Java, and Kotlin, making it even easier to integrate Orb no matter your stack.
Do you have a language you’d like us to support next? Let us know - we’re all ears!
Orb's data exports feature now supports the following new resource types:
This information can be used to power use cases like: recognizing revenue according to custom rules, contra revenue breakdown, reconciliation, and collections analysis.
For customers with data exports included in your plan, these resources will automatically be included in the list of resources exported to your data destination.
For more information about these resource types, please check out our documentation. If you'd like to learn more about the data exports product generally, including setup, please reference this introductory guide, or reach out to the Orb team.
Over the past few months, many customers have launched GenAI features and wrestle with the same question: "How do we monetize this?" This inspired us to build something to help our customers iterate and refine their pricing strategy.
Orb Simulations lets you build scenarios for different pricing strategies and run them against historical usage data in Orb. You can visualize price changes before you make them, without any of the complicated data legwork or churn risk of live testing with customers.
Use cases:
Try Simulations now in Beta, or learn more in our docs. When made generally available, we’ll update you on pricing. For new customers, join the waitlist.
Orb now has support for creating hierarchical relationships between your customers to power flexible pricing, usage aggregation, and invoicing.
This capability is particularly valuable when your customers desire to aggregate usage across multiple customers on a single parent invoice while maintaining the ability to configure pricing per customer or groups of customers.
Learn more about this new powerful capability in our product documentation
You can now set up invoicing sync or accounting sync in a multi-step flow that includes configuration and mapping items from Orb to your external provider. This allows for quicker setup without having to navigate to separate pages.
Learn more about integration setup in Orb’s product documentation
Subscription modification endpoints now support an optional boolean parameter: allow_invoice_credit_or_void.
• Defaults to True (maintains existing behavior).
• Set to False to prevent modifications that would create a credit note or void an invoice. Instead, such requests will fail with a validation error.
When to use this
Certain modifications, like canceling a subscription mid-period with an in-advance fixed fee, typically generate credit notes. If you’re confident your modifications shouldn’t create these, set allow_invoice_credit_or_void=False as a safeguard.
Equivalent to a Dry-Run
This functions similarly to sending a dry-run request and previewing changes first, which allows for more precise validation of side effects.
Supported Endpoints
We have launched a new endpoint to update a customer's payment methods in Orb from their Stripe payment methods. (And a second endpoint using the customer's external ID.)
This endpoint can be called before taking an action that may cause the customer to be charged, ensuring that the most up-to-date payment method is charged.