By Editorial Team, reviewed by Editorial Team (approved by site owner) · Published · 1 min read
Each game provider has its own documentation, but most integrations share the same shape. This checklist helps you cover the essentials.
Before you start
- Obtain the provider's documentation, test credentials and a sandbox.
- Confirm the integration model: seamless wallet (the provider calls your wallet) or transfer wallet (funds move to the provider).
- Ask about certification, supported currencies, languages and jurisdictions.
Game launch
- Generate a launch URL or token for each session, tied to the player and a short expiry.
- Pass currency, language and responsible-gambling settings as the provider expects.
- Handle the return from the game to your site, including errors.
Wallet callbacks
- Authenticate every callback and verify signatures.
- Implement balance, bet, win, refund and rollback operations.
- Store each transaction reference before applying it, and return the stored result for repeats.
- Handle out-of-order callbacks, for example a rollback arriving for a bet you have not seen.
- Respond within the provider's time limit and return the exact error codes they expect.
Rounds and sessions
- Keep round-level records linking bets and wins.
- Decide how to handle unfinished rounds and sessions that end suddenly.
Reconciliation
- Pull provider reports on a schedule and compare totals with your ledger.
- Investigate every difference and keep a record of the resolution.
Testing
- Run the provider's test scripts and your own scenarios: duplicates, timeouts, insufficient funds, rollbacks and concurrent bets.
- Test with real devices, not only browsers on a desktop.
Go-live
- Prepare monitoring for callback errors and latency, with alerts.
- Agree a support contact and an escalation route with the provider.
- Release to a small group first, then widen.
Building an adapter layer with one internal model for all providers keeps later integrations quicker and safer.
