Seamless wallet casino API integration

What is a seamless wallet casino API?

A seamless wallet casino API is a wallet model in which the operator keeps all player balances and the aggregator never holds money. Instead of pre-funding a separate game wallet and reconciling transfers, our platform calls your callback URL in real time for every balance check, bet and win. Funds always stay on your side.

This is the opposite of a transfer wallet, where money is moved into and out of a game-side balance and then reconciled afterwards. Transfer wallets create latency, failure points and accounting overhead. The seamless model removes all of that: there is one source of truth for player money — your platform — and every game transaction is just a synchronous call to your endpoint.

For operators, that means cleaner compliance, simpler reconciliation and full control of funds, while still offering a catalogue of 4,000+ games from 50+ providers behind a single integration.

How the seamless wallet works

There are three callback actions, all sent to the URL you configure in your operator backend:

• balance — sent at the start of a session to read the player's current balance.
• debit — sent for each bet; you subtract the amount and return the new balance, or return an insufficient-funds code with the current balance.
• credit — sent for each win; you add the amount and return the new balance.

Every call carries a unique call_id transaction id so you can de-duplicate safely, plus round_id and game_id for traceability. Balances are always integer cents (e.g. $2.50 is 250). Your endpoint must always return HTTP 200 and report any error in the JSON body. Rollbacks arrive flagged with rb=1 and are processed like a normal debit or credit.

Security and signature validation

Every seamless-wallet callback carries a timestamp and a key. You validate that the timestamp is within a short window (e.g. 30 seconds) and that the key matches md5(timestamp + your_salt_key), where the salt key is shown in your operator backend. If validation fails, your endpoint returns an error code and applies no balance change.

This keeps the integration tamper-resistant without adding a heavyweight handshake on every request. Combined with the unique transaction id for de-duplication, the model is both fast and safe under high volume. The full request and response shapes for each action are documented in our API documentation.

Sandbox to go-live in four steps

Integration follows a familiar, well-trodden path, so your developers move quickly:

• Register your operation and tell us about your platform.
• Get approved and receive your opaque API credentials and salt key.
• Integrate and test the full balance, debit, credit and rollback flow in the sandbox.
• Go live by topping up your prepaid credit and opening the games to players.

Because the API mirrors the standard seamless-wallet specification, most operators complete integration in days rather than months — and the same wallet integration covers the entire 4,000+ game catalogue.

Seamless wallet casino API FAQ

Explore more