402 insufficient_balance.
How it works
1
Save a card
Do one normal top-up in the dashboard. That payment saves the card for
future off-session charges (via Stripe’s
setup_future_usage; Omnia never
stores card numbers). This is the prerequisite for auto-reload: a card must
be on file before it can charge automatically.2
Set a threshold and amount
In Usage → Auto-reload, set the balance threshold that triggers a
top-up and the amount to add each time.
3
Let it run
Whenever your balance falls below the threshold after a charge, Omnia
charges the saved card off-session for your configured amount and credits
the wallet.
Choosing a threshold
The threshold is evaluated after each charge, so set it high enough to cover the traffic between the moment your balance dips below it and the moment the reload lands. Base it on your spend rate: a workspace burning a few dollars a minute wants a higher threshold than one spending pennies an hour.Safeguards
Idempotent: no double-charging
Idempotent: no double-charging
Auto-reload charges are idempotent. A trigger firing twice in quick
succession won’t charge your card twice or double-credit the wallet.
Soft decline on extra authentication
Soft decline on extra authentication
Some charges require extra authentication (for example, 3-D Secure), which
needs you present and therefore can’t complete off-session. Omnia treats
this as a soft decline: it pauses auto-reload rather than retry-looping,
and prompts you to top up manually (or re-authorize the card) so the wallet
isn’t left silently draining.
Related
Managing your wallet
Top up, track balance, and understand holds.
Usage & invoices
See recent top-ups and per-request costs.