Game Top-Up & Voucher Reseller Platform

No. You do not need KYC documents, a company registration or scanned paperwork to open a reseller account and start selling. Sign up with an email address, switch on two-factor authentication, and the account is live. We verify behaviour on the platform rather than paperwork at the door, which is why onboarding takes minutes.

There is no sandbox — the key you receive on day one is a production key against production endpoints. Catalog browsing and player validation work immediately and cost nothing, so you can build and test the whole integration against real data before funding your wallet. Nothing you write has to be rewritten to go live.

You can send a live order as soon as your wallet holds balance, which for a crypto deposit is usually the same session you signed up in. The sequence is account, two-factor authentication, wallet funding, order — with no approval queue and no sales call between any two of those steps.

Your API key is issued immediately after you enable two-factor authentication on the account. It works for the catalog, requirements and player-validation endpoints straight away. The order endpoints are the only ones that additionally need a funded wallet behind them.

Fund your wallet with USDT on any supported network, or with the other methods available in the reseller panel. Crypto deposits are detected on-chain and credited automatically, so there is no invoice to chase and no banking window to wait for. The balance itself is held in USD.

Two kinds: direct top-ups that credit a player account from its player ID, and code-based products that return a voucher or gift-card code you hand to your customer. Both go through the same order endpoint, and the catalog tells you which shape a product uses before you order it.

You send the player ID plus whatever extra fields that product requires, such as a server or zone. We resolve the player name against the game, confirm the account sits in a supported region, then charge your wallet and fulfil the order automatically, with no manual step in between. The currency appears in the account without a code changing hands.

Each product category exposes its own requirements list through the API, naming every field you must send and its type. Read it once per category, cache it, and build your checkout form from it — you never have to guess which games want a server, a zone, or nothing but a numeric ID.

Yes, validation happens before the order is accepted rather than after. If the player ID does not resolve, or resolves to an account outside the regions that product serves, the order is rejected and your balance is untouched. Player names always come from the game, never from anything a buyer typed.

A failed order moves to a refunded status and the money returns to your wallet automatically. If only part of a multi-unit order was delivered, only the undelivered units are refunded. The status sits on the order record, so your system can react without anyone opening a ticket.

No, as long as you send your own UUID as the order reference — it acts as an idempotency key. Retry a request with the same reference after a timeout or a dropped connection and you get the original order back rather than a second charge, which makes safe retries a two-line change in your client.

Yes. Order creation accepts an optional expected unit price, and the order is rejected rather than filled when the live figure sits above it. That turns a moving catalog into a predictable one: your storefront can quote a customer and be certain it will never be charged above what it quoted against.

Both are supported. Webhooks push order status changes to your endpoint as they happen, and the status, batch and list endpoints are there whenever you would rather pull. Most integrations use webhooks for the happy path and a periodic list call as a safety net.

List your orders filtered by status and a date range, page through the result, and match it against your own records. Every order carries your reference, the charged amount, the currency and both timestamps, which is enough to reconcile a full month without exporting anything by hand.

The catalog spans 30+ player regions, and the consumer storefront runs in 7 languages, Arabic and Persian included with full RTL layout. Region support is set per product rather than globally, so the catalog response tells you exactly where each item can be delivered.

Restrict the key to an IP allowlist, keep two-factor authentication switched on, and rotate the key from the reseller panel if it is ever exposed. Key usage and session activity are logged, so unusual access is visible rather than invisible. Treat the key like a wallet password, because that is what it is.