Wallet and top-ups
The player's 0x balance — card top-ups settled in USDT on five networks or in Bitcoin, how they are credited, and how your game can send a player to top up.
Players pay for games, items and subscriptions from their 0x balance. The balance is held in US dollars (cents) and topped up by card on 0x's payment partner's page. The card buys USDT, or bitcoin, which reaches 0x over the network the player picks. You never handle a card or a chain: your game only sees "paid" or "not enough balance".
Top-ups are live on 0x.limo. Players manage their balance at https://0x.limo/wallet.
#Networks
| Network | Settled as | Top-ups | Developer payouts |
|---|---|---|---|
| Ethereum | USDT (ERC-20) | yes | yes |
| Tron | USDT (TRC-20) | yes | yes |
| Arbitrum One | USDT (ERC-20) | yes | yes |
| BNB Smart Chain | USDT (BEP-20) | yes | yes |
| Polygon PoS | USDT (ERC-20) | yes | yes |
| Bitcoin | BTC (pass-through) | yes | no: payouts are always in USDT |
The network changes only the fees. Before paying, the player sees the expected card charge on each network, cheapest first (POST /v1/me/wallet/estimate {amountUsd}).
#How a top-up works
- The player picks an amount in whole dollars, $20 to $500, and a network. This is
POST /v1/me/wallet/topups {amountUsd, network}, which takes anIdempotency-Key. - They pay by card on the checkout's page. On a USDT network, the card is charged the amount plus a small processing fee, which is shown before they pay.
- The balance is credited when the checkout confirms the payment: by its webhook, by the wallet page polling the top-up, or by a background check that catches a lost webhook or a late payment. Each top-up is credited once.
- An unpaid top-up expires after about an hour, and the player can cancel it before then (
POST /v1/me/wallet/topups/{id}/cancel). An expired top-up stays expired, so the player starts a new one. A late payment within a day is still credited.
What is credited:
- USDT networks: the full amount the player picked. The processing fee was added on top of it.
- Bitcoin: the player picks what the card is charged. The checkout keeps the bitcoin and credits its USD value when the payment confirms, less its Bitcoin fee (about 4 %). The balance can therefore end up a little more or less than the estimate. The wallet shows the approximate BTC and the expected balance before the player pays.
Top-ups themselves can't be refunded through 0x. A refunded purchase goes back to the balance, never to the card or the chain.
#Your game and the balance
- Games never read or debit the balance directly. Purchases go through the launcher's dialogs: Buy for games, the confirm dialog for in-game purchases and subscriptions.
- When the balance is short, those dialogs already offer Top up $x more, which opens
https://0x.limo/wallet?need=<cents>&game=<game id>. Your game needs no top-up UI of its own. - Guests can't pay: buying, purchases and top-ups need a 0x account (
403 account_required).
#Player API (reference)
These routes are used by the 0x launcher. They are listed so you can recognise them; your game doesn't call them.
| Method and path | |
|---|---|
GET /v1/me/wallet | balance (balance cents, balanceUsd), top-up limits, recent ledger rows and top-ups |
POST /v1/me/wallet/estimate {amountUsd} | the expected card charge per network |
POST /v1/me/wallet/topups {amountUsd, network?} | {topup: {id, status, amountUsd, chargedUsd, feeUsd}, checkoutUrl} |
GET /v1/me/wallet/topups[/{id}] | the player's top-ups / one top-up (the return page polls it) |
POST /v1/me/wallet/topups/{id}/cancel | give up on an unpaid top-up (409 if it is already closed) |
POST /v1/store/orders {appid} | buy a game from the balance (409 insufficient_funds with missing) |
Top-up statuses: pending, confirming (payment received, waiting for confirmations), paid, paid_short (the provider delivered less than it charged; the balance still gets the full amount), expired, cancelled, failed, mismatch (under review by 0x support) and resolved (settled by 0x support).
