Orb now supports the ability to configure which webhook types are sent to each registered webhook endpoint directly in the Orb UI.

As a reminder, webhook endpoints can be found under Developers --> Webhooks on the Orb sidebar.

Orb allows you to preview the side-effects of the actions you take by including the `Include-Changed-Resources` on most significant billing mutations. 

We're introducing support for a new header value, `payable_invoices`, which returns only invoices that are immediately payable. Note that these invoices will often include only upfront fixed fees, making it a great fit and more performant option for checkout and preview flows. This new header value is also compatible with pending changes.

Orb now supports Stripe shared payment tokens in private preview. Shared payment tokens allow your customers or prospects to use agents to transact with your service, and use an underlying payment method with support for usage restrictions, deactivation, and expiry. Shared payment tokens are a new part of the agent-facilitated commerce ecosystem.

In Orb's billing engine, you can set a shared payment token as a customer's default payment method. On collection for an invoice, Orb will use the SPT, and Stripe will clone the underlying Payment Method if the token is valid and under the (recurring or one-time) usage limit. 

For more information on shared payment tokens, visit Orb's documentation.

Licenses in Orb bring support for seat-based pricing and per-user spend controls to life. Give every seat, agent, or workflow its own credit allocation, automatically track consumption per license, and decide whether to block access, alert, or bill overage when a user hits their limit.

As your customers grow, they need ways of ensuring fairness, promoting adoption, and reigning in spend. Licenses can help:

1. Find product champions and build leaderboards by tracking individual usage
2. Prevent power users from eating away team spend with billing-enforced guardrails
3. Have more personalized plan growth conversations to drive upsells and add ons
4. Seamlessly run freemium and trial programs

Learn more in our docs, reach out to Orb with help getting started, or try it out now.

All credit purchases with a non-zero cost-basis now automatically generate an invoice.

• This ensures accurate billings and deferred revenue reporting in Orb, aligned with ASC606 accounting standards.
• Workflows that previously allowed granting non-zero cost-basis credits without issuing an invoice are no longer supported.
• $0 cost-basis credits can still be granted without an invoice.
• For customers that invoice or collect payment outside of Orb, check the "Mark this invoice as paid" option to prevent duplicate invoicing effects.

Learn more about credit configuration and cost basis in our docs.

If your business or tax information has changed (e.g. shipping address or customer information), you are now able to regenerate your invoice to reflect the new business information. Please note that it is your responsibility to ensure compliance with regulations in the relevant jurisdiction, including any tax laws that do not allow billing documents to be modified. 

In the Orb dashboard, you can now reset and disable the customer portal link on a per-customer basis. This allows you to selectively disable or re-issue links for more granular access management. 

Note that both options immediately revoke access to existing customer portals for that customer.

The AR aging report is now available in Orb.

Orb’s Accounts Receivable Aging (AR aging) report breaks down outstanding receivables invoiced through Orb by how long they’ve been unpaid, helping finance teams manage collections and end-of-month reporting. Use this report to:

• Assess and forecast cash flow
• Monitor customer payment behavior
• Support bad-debt and allowance calculations
• Prepare financial statements as part of your month-end close

Try it now in Orb Reports, and learn more in our docs.

We've added 2 new resource types Orb's Data Exports.

1. Payment application
2. Payment attempt

These resources give you deeper visibility into the full payments lifecycle, from attempted charges (including retries through Orb's dunning process) to successful payments. Use these resources to better understand cash vs. AR, improve collections, and reconcile payments.

Learn more about data exports in our docs.

We're excited to announce support for non-zero cost basis allocations, enabling usage-based revenue recognition for recurring commitments and prepaid usage.

What's new
Previously, recurring commitments required using fixed fees with straight-lined revenue recognition—where a $12,000 annual commitment would be recognized as $1,000/month regardless of actual usage.

Now, you can assign a per-unit cost basis to allocations, allowing revenue to be recognized as credits are consumed rather than on a time-based schedule. This enables true usage-based accrual accounting for prepaid commitments.

Use cases
- Usage-based recognition: A customer commits to $100,000 for the year. Instead of recognizing $8,333/month on a fixed schedule, recognize revenue as they actually consume credits—even if usage is uneven throughout the year.
- Prepaid credits: A customer purchases 10,000 credits at $0.50/credit. Revenue is recognized proportionally as each credit is used, not straight-lined over time.
- Flexible pricing: Combine free promotional credits (zero cost basis) with paid allocations in the same plan.

How it works
When configuring an allocation price, you can now specify a `per_unit_cost_basis`:
- Free allocations: Set cost basis to $0 (default behavior)
- Paid allocations: Set cost basis to match the prepayment amount divided by the allocation quantity
- Revenue recognition: As credits are consumed, revenue is recognized proportionally—not straight-lined over time like a fixed fee

This gives you the flexibility to choose between time-based recognition (fixed fees) and usage-based recognition (non-zero cost basis allocations) depending on your business model and accounting needs.

Questions? Reach out to our support team or check the documentation for implementation details.