You can now fetch a summary of a customer's credit balance with a single request to GET /v1/customers/{customer_id}/credits/balance. Previously, getting a total balance meant paging through a customer's credit blocks and adding them up yourself.

The response includes:

• balance: the customer's current credit balance
• pending_payment_balance: credits that are pending payment
• next_expiry_date and next_expiry_balance: when the next credits expire, and how many
• currency: the currency of the balance

Learn more about credits in our docs.

You can now update the metadata on an existing credit block with the new PUT /v1/credit_blocks/{block_id} endpoint.

Use it to keep the identifiers and tags you store on credit blocks in sync with your own systems after a block has been issued, for example to record a contract reference, the reason for a grant, or a reconciliation status.

Send the keys you want to set, or set a key to null to remove it.

The credit ledger for each customer in the dashboard now opens with a Credit blocks view: a burndown chart of how the credit balance changes over the selected timeframe. Each lane is a credit block or recurring allocation, placed by effective date, under the total balance at the end of each day.

• See every active credit grant and recurring allocation in the timeframe, and how much of each block remains.
• Spot backdated and forward-dated blocks, expired unused credits, voids, scheduled blocks, and days with no credits left where usage is billed as overage.
• See who added each block.
• Hover the total balance to see what each block did that day, and select a block to filter the ledger below to its entries.

Learn more about prepaid credits in our docs.

Enterprise Commitment is now in Early Access. 

With commitments, your customers agree to a minimum spend over a contract term, which Orb tracks for you. Postpaid commitment invoices any shortfall as a true-up, while prepaid commitment is granted upfront as credits.

• Set the true-up or credit grant cadence to match the contract, at term end or on a recurring schedule.
• Configure credit rollover for unused commitment.
• Track each commitment in a dedicated ledger view in the dashboard.
• Bill usage and true-ups together on a single invoice.

Learn more about enterprise commitments in our docs.

Reach out to your Orb contact to get access. 

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.

You can now set a customizable invoice date when creating an invoice for a credit increment. By default, the invoice will use the credit block’s effective date, but you can override this by specifying a custom invoice date.

This option is available in the dashboard and via the API by setting invoice_settings.invoice_date when creating a ledger entry.

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.

In-arrears fixed fees can now be denominated in virtual currencies (custom credits). These fees will automatically deduct from customers' prepaid credit balances, similar to usage-based fees.

This enhancement enables new pricing scenarios — for example, you can now set enterprise support fees in credits that draw from the customer's prepaid enterprise commitment rather than triggering a separate charge.

We’re excited to share that Orb now allows users to remove credit blocks from the credit ledger. This can be done by voiding the original credit block amount through the “adjust credits” workflow on the customer page within the UI. This new capability is particularly helpful for correcting errors in credit block creation or removing a block in case of a refund for a credit grant.

Customers can now receive an allocation of credits – of one or more currency units – automatically as part of their subscription. Allocations can be configured in the ‘create plan’ flow and overridden on a per-subscription basis, with an amount, optional rollover behavior, and cadence. Whereas the set of usage-based prices on the subscription determines how Orb will deduct credits from the balance (or accrue them as overages on the invoice), allocations allow you to set up a recurring schedule of increments on the customer’s credit ledger. Because allocations are configured at the plan-level, Orb allows you to standardize credit treatment and ensure consistency across thousands of customers.

Learn more here.