Go-live checklist

Sandbox completed

• Successful POST /gamelauncher/play (REAL mode)
• Launch URL renders in your iframe; player can complete a round
• Player-closes-tab-mid-round flow tested — wallet still receives settlement; balance reconciles
• Iframe wrapper has its own close button (since the iframe doesn't emit an exit signal)
• Replay endpoint integration tested (your support team can pull a replay)

For direct integrators (additional)

• All four wallet endpoints implemented (getbalance, debit, credit, reverse)
• Idempotency verified — duplicate transid returns the same result
• Zero-win round closure tested — credit with creditamount: 0 and roundended: true
• Reverse path tested — debit then reverse leaves the wallet balance unchanged
• Reverse-against-closed-round rejected with ROUND_ALREADY_CLOSED
• NOT_SUFFICIENT_FUNDS path tested
• BET_LIMIT_REACHED / GAMING_LIMIT_REACHED path tested (if you use betting limits)
• Round IDs stored as strings, not UUIDs (a slot spin is slots:<uuid>)
• We've run our automated test suite against your sandbox endpoints

If your rooms offer slots

• Spin with a win, and a spin with no win (creditamount: 0 closes it)
• A spin while the player's bingo round is still open
• Duplicate and late /credit with the same transid returns the same result (the background retry)
• Debits with "autoplay": true accepted
• A slot spin's replay opens from /gamelauncher/replay

If you use free cards

• Campaign set up with us for each game and currency
• /freebet/give with a unique externalfreebetid per grant
• A free round played end to end: FREEBET debit with debitamount: 0, then FREEBET credit with freebetended: true
• /freebet/cancel on an unused grant

Compliance artefacts

Request these from your account manager before any regulator review:

• RNG (Random Number Generator) certificate from our certification lab
• RTP (Return To Player) statement for each game variant in your catalogue, including slot games if your rooms offer them
• List of jurisdictions in which the game is approved (varies; ask for the current list)
• Game rules document (per language, if applicable)
• Responsible-gambling configuration per operator (session limits, reality checks)

Operational

• Our production wallet-call IP allowlisted on your side (direct integrators)
• Production Basic Auth credentials issued and stored in your secrets manager (not in code)
• Per-operator config submitted (currencies, stake limits, RTP, slots, free cards, jurisdictions, languages)
• CSP frame-src updated for the production domain
• Reconciliation feed confirmed: aggregator path uses your aggregator's transaction export; direct path uses your wallet logs
• Smoke test plan agreed for first 24 hours of production traffic
• We have your on-call contact for production incidents; you have ours. SLA confirmed in writing

After go-live

• We monitor session create rate, debit/credit success rate, and round settlement latency on our side. We'll reach out if anything looks off.
• You should monitor wallet endpoint latency and error rate on your side. We retry 5xx with backoff — if you start seeing sustained 5xx, escalate.
• For incident playbooks and what to send support, see Troubleshooting.