A successful API response does not prove that a game is ready for production. A launch can still be blocked by missing titles, incorrect currency settings, failed balance updates or unclear procedures for interrupted rounds. Use the following seven checks as a practical review before go-live.
This is a general operator checklist, not a substitute for the specific API documentation, provider requirements or approvals that apply to your market. Confirm the exact acceptance criteria with your integration team.
01 Confirm the game list for each target market
Start with the provider and title list your project actually needs. Do not assume that every title from a supported studio is available in every market or for every setup.
- Identify the intended providers and launch titles.
- Verify availability for each target market and project configuration.
- Record which games are approved for launch and which need follow-up.
Launch evidence: an agreed list of available titles by market, rather than a generic provider catalogue.
02 Verify currencies and bet settings
Currency support, stake values and game configuration need to fit the operator's wallet and market requirements. Check these before players enter the games.
- Confirm required currencies with the integration team.
- Test how balance and bet amounts are represented across systems.
- Check applicable minimum and maximum bet limits where supported.
Launch evidence: test results for the project currencies and applicable stake settings.
03 Test wallet debits, credits and round history
The operator keeps its existing wallet and lobby. That makes end-to-end testing between the platform and game content especially important.
- Launch a test game from the existing casino lobby.
- Verify balance changes for bets and wins.
- Confirm that round and transaction history can be reconciled against the platform's records.
Launch evidence: successful test rounds with expected balances and traceable records.
04 Check interrupted sessions and unsuccessful requests
A normal round is not enough. Reproduce realistic interruptions and agree with the technical team how the integrated systems should respond.
- Test a session interruption during a game round.
- Check the expected behaviour when a request fails or is repeated.
- Document how unresolved rounds are investigated before launch.
Launch evidence: agreed expected responses and a clear path for investigating discrepancies.
05 Review provider-specific features
Promotional tools and gameplay features may differ by provider, title or project configuration. Treat each relevant feature as a separate acceptance item.
- Check whether required promotional features are supported.
- Test any enabled feature in staging rather than assuming catalogue-level support.
- Record limitations and configuration dependencies for your launch team.
Launch evidence: a feature checklist reflecting what is actually enabled for your project.
06 Complete a staging acceptance run
Staging provides a place to review the API connection and project settings before production. The acceptance run should cover the whole player journey, not only the technical handshake.
- Prepare your callback URL, target markets and required currencies for setup.
- Verify that selected games can be opened from the intended lobby.
- Repeat the core wallet, session and configuration checks after any important change.
Launch evidence: a documented pass/fail result for the launch-critical scenarios.
07 Agree on production handover and support
The last step is operational: everyone should know who approves the launch, who responds to incidents and which configuration was tested.
- Agree on the final game list and production settings.
- Identify the operator and technical contacts for launch issues.
- Confirm the support route for issues that appear after go-live.
Launch evidence: an agreed launch checklist, owner and escalation path.
Pre-launch checklist at a glance
- Approved titles and markets
- Currencies and stake settings
- Wallet, balance and round records
- Interruptions and unsuccessful requests
- Required provider features
- End-to-end staging acceptance
- Production handover and support
A game being accessible in staging is a good start. A documented acceptance run is what helps a technical team decide whether the integration is ready for production.
