Help / Wallet & prepaid credit
How wallet billing works
Prepaid credit covers orders and renewals before we ever charge your card. Tops up via Stripe, PayPal, or USDT-TRC20.
The wallet is a prepaid balance on your account. When you order a new server with it, or a wallet-billed server renews, the platform debits the wallet — your card is never involved. This article explains how the money moves; for the click-by-click tour of the Wallet and Billing pages, see Billing, invoices, and wallet.
What the wallet is
- Prepaid service credit. It never expires, and it only deducts when you order or renew a server — plus usage-based extras like call-forwarding minutes, AI Agent minutes, or TTS if you use them.
- Top-ups are non-refundable. Top up what you expect to spend.
- Only team members with the Owner or Billing role can top up or change billing settings.
New orders: wallet covers in full, or not at all
At checkout the wallet must cover the entire order. If your balance is short, the wallet option stays greyed out — top up first, or pay by card instead. There is no splitting one order between wallet and card.
The choice is made per order: pay by card at checkout and that server becomes a card-billed Stripe subscription that renews against your saved card; pay from the wallet and its renewals debit the wallet from then on. Servers you already had on card billing stay on card billing — the wallet does not take them over.
Topping up
- Card (Stripe) or PayPal — minimum $10. Amounts up to $1,000 by card or $500 by PayPal credit within seconds; larger payments go through a short admin review, usually within one business day.
- USDT on the Tron (TRC-20) network — minimum $25. You send an exact quoted amount to the address shown and the credit lands automatically, typically within 1–3 minutes of network confirmation. Amounts up to $2,000 credit automatically; larger deposits get the same admin review. See Topping up with USDT-TRC20 for the step-by-step.
Renewals: the daily sweep
Every day at 02:30 UTC the platform looks at wallet-billed servers whose renewal date has arrived and debits the next period’s cost. With enough balance the renewal is silent — you just get a receipt email.
If the balance cannot cover a renewal, the sequence is automatic:
- The debit fails and you get an email naming the server, your balance, and the shortfall. The server is suspended and a 7-day grace window starts.
- You get a reminder each day, naming the exact deletion date.
- The platform retries the debit every day. Top up enough at any point and the next retry lifts the suspension and brings the server back on its own — no ticket needed.
- If 7 days pass without enough balance, the server is terminated. A final backup stays downloadable for 7 more days, and the termination email says so.
One thing the wallet does not do: fall back to your card. If a wallet-billed server’s renewal fails, the platform does not charge your saved Stripe card — topping up is the only fix. Turn on the low-balance alert on the Wallet page and you will get an email days before it matters.
Good to know
- The balance never expires and there is no rush to spend it — but top-ups are non-refundable, so keep it close to what you plan to use.
- A new order must be covered in full; you cannot split a checkout between wallet and card.
- Card-billed servers keep renewing through Stripe even if you have a wallet balance — the wallet only pays for servers that were ordered with it, plus usage extras.
- Your balance, top-up options, and full history live on the Wallet page; the Billing page shows the same ledger with filters.
Tags: billing, wallet, top-up
You might also like
Agent Mobile App: enabling sign-in for your agents
The agent softphone app requires the Agent Mobile App add-on on your server. How to enable it, and what agents see when it is off.
Read article →Forwarding Portal — how minutes are billed
Per-inbound-minute, including ring, rounded up, debited from your wallet.
Read article →What "awaiting confirmation" means for manual orders
Your provider has to confirm payment receipt before your server boots.
Read article →