The prepaid credit wallet on Orbit now has two self-serve controls every operator can reach without a support ticket: a top-up dialog on the dashboard's Billing page, and an auto-reload threshold that recharges your wallet when the balance falls below a level you set. Every charge returns a Stripe receipt email to your billing contact. This announcement closes the last gap in the prepaid-credits rollout — the March 10 changelog entry shipped the wallet ledger and low-balance alerts; this post announces the two controls that complete the funding loop.
Quick answer: Open Billing in the dashboard to fund the wallet ad hoc. Open Billing → Payment to set a threshold-based auto-reload (threshold, recharge amount, and an optional monthly cap) — a tenant-owned configuration, decided per workspace, never a platform default.
What shipped
Three surfaces complete the prepaid-credit funding loop:
- The top-up dialog. From the dashboard's Billing page, the wallet card opens a top-up dialog that starts a Stripe Checkout session and credits the wallet when the session completes. The ledger records every credit and debit with the resolved rate at send time — the same wallet the March announcement shipped; manual funding now takes a minute, not a ticket.
- Auto-reload, tenant-owned. Under Billing → Payment, the auto-top-up section holds a threshold config: the balance level that triggers a recharge, the recharge amount, and an optional monthly spending cap. It is disabled until you enable it, only workspace owners can change it, and it charges in your account currency — a tenant-owned control in the strictest sense: the workspace sets the policy; the platform runs it.
- Receipt email notification. Every completed charge — manual top-up or auto-reload — returns a Stripe receipt email to the workspace's billing contact, so finance has the paper trail either way.
Where to find it
Two routes, plus the source entry this post anchors:
- Dashboard. The wallet lives at
/billing— the top-up dialog sits on the wallet card. The auto-reload config lives at/billing/payment, next to the saved payment method it charges. - API. The same auto-reload config is readable and writable per workspace through the billing endpoints, so an organization managing configuration in code can promote threshold values without a browser session.
- Changelog. The original capability is recorded in the prepaid credits and marketplace entry from March 10; this announcement is the editorial slot the roll-out was missing.
How to use it
- Top up ad hoc. Open Billing, use the top-up dialog on the wallet card, and complete the Stripe Checkout session — the balance updates when the session succeeds, and the receipt email lands.
- Set auto-reload. Under Billing → Payment, in the auto-top-up section, set the threshold (trigger level) and the recharge amount, optionally cap the monthly spend, and save — the first eligible low-balance event recharges within its guardrails.
- Adjust or clear it later. Auto-reload is a tenant-owned setting all the way down: change the values, or clear the config entirely, from the same section — it stays off until you turn it on.
Frequently asked questions
Where do I add credit to my workspace?
From the dashboard, open the Billing page and use the top-up dialog on the wallet card. It starts a Stripe Checkout session against your saved payment method, and the wallet credits when the session completes.
How does auto-reload decide when to charge?
You set the threshold. When the wallet balance falls below it, an auto-reload charges the configured amount against the workspace's saved payment method, subject to the optional monthly cap. It is disabled until an owner enables it, and clearing the config stops it.
Who gets the receipt after a charge?
The workspace's billing contact gets a Stripe receipt email for every completed charge, whether the funding happens through the manual top-up dialog or the auto-reload threshold.
Can I set auto-reload from the API?
Yes. The auto-reload config is readable and writable per workspace through the billing endpoints, so threshold and recharge values can be managed alongside the rest of your configuration in code.
Resources
- Pricing — the pay-as-you-go rates the prepaid wallet funds, across messaging, voice, and video.
- Changelog — the canonical history; the March 10 prepaid-credits entry this post anchors lives there.
- Usage and delivery anomaly detection — the ledger-backed detection modules that watch spend per lane.
Published 14 September 2026.