We’re excited to announce a new enhancement to our Stripe integration: Orb now supports syncing customer addresses directly from Stripe. This upgrade eliminates manual address entry and ensures your billing and tax workflows run smoothly.

🌟 Why this matters 

Many of our customers faced  billing issues and invoice failures when address data in Stripe wasn’t reflected in Orb. This gap created operational overhead and made it difficult to maintain accurate tax calculations. 

With this new feature:  
- Customer addresses will automatically sync from Stripe when an Orb customer is linked to a corresponding Stripe customer.
- Address updates in Stripe will be reflected in Orb automatically—no manual input required.
- This feature is can be toggled through the Integrations tab under Settings, so you have control over when and how syncing happens.


🔍 Use Case: Tax Integration Support 

This upgrade is part of our broader initiative to enhance tax readiness and automation. Many tax providers require accurate billing and shipping addresses for compliance and jurisdictional calculation. With synced data from Stripe, you can now:

-   Avoid misapplied taxes or missing tax data due to incomplete addresses.
-   Reduce friction in integrating Orb with tax engines.
-   Confidently support invoicing requirements.

⚙️ Configuration 

You can enable the feature with a single toggle: Settings > Integrations > Stripe > Sync customer addresses This creates a one-way sync from Stripe → Orb. Addresses in Orb will not update Stripe, and unlinked Orb customers will remain unaffected.

We've launched a new API endpoint that enables you to evaluate the output of multiple prices for a given customer and time range. This powerful endpoint supports up to 100 prices in a single request, helping you build more detailed usage dashboards and audit invoice calculations.

Key capabilities:

• Evaluate up to 100 prices in a single API call for improved performance
• Use ingested or preview events - evaluate against real usage data or test with up to 500 preview events
• Advanced filtering and grouping with computed properties for granular analysis
• Inline price definitions - test new pricing models without creating them first

Common use cases:

• Build detailed usage breakdowns for customer dashboards
• Audit and verify invoice line item subtotals
• Test pricing changes before implementation
• Display usage patterns grouped by custom dimensions (e.g., by hour, region, or product feature)

Example grouping: Group usage by hour and custom property: ["hour_floor_timestamp_millis(timestamp_millis)", "region"]

Example filtering: Filter for specific usage: product_type = 'premium' AND region = 'us-east'

The endpoint is available now at POST /prices/evaluate. Check out our Querying data with SQL page for additional details and examples.

When adding a pre-purchase allocation to a plan or subscriptions, Orb now supports a custom expiration option for each allocation credit block. This option allows you to set a specific number of days or months after which the block should expire. This option can be configured in both our UI and API.

To learn more about allocations, please visit our docs.

Orb now supports Apple Pay, Google Pay, and Amazon Pay for both automatic payment collection as well as manual invoice payment in the invoice and customer portals.

To enable these methods, head to your Stripe Dashboard → Payments → Payment Methods. In the configuration labeled “Default — Orb Configuration”, simply toggle on the payment methods you’d like to offer.

These options will now appear automatically during checkout and can be saved for future use — no additional setup required.

You can now lock accounting periods in Orb Reports. 

This control in your Reports Settings ensures that no billing activity, including backdated subscriptions or invoice edits, impact closed reporting periods so you can stay compliant with ASC 606 standards.

Learn more about setup and expected recognition treatment in our docs.

When configuring a new plan, plan version, or subscription, it is now possible to copy a price from an existing plan. This simplifies the provisioning process and reduces the potential for mistakes when setting up your pricing. 

Orb now empowers teams to create bespoke subscriptions without needing to define a new plan via Custom Contracts. When working with enterprise customers who have unique pricing, billing terms, or usage requirements, it’s common to run into edge cases that don’t neatly fit into standardized plans.

Instead of creating a one-off plan per customer, you can now build a custom contract directly (in app and via the API) — giving you the flexibility to meet your enterprise customers’ needs without bloating your plan catalog.

Read more here on when and how to build a contract from scratch or from an existing plan template. This feature is currently available to a subset of customers.

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.