Integration Guide · 2026
Live casino API integration checklist: wallet, disconnects, limits and streams
Live dealer tables look like one more game category, but they behave differently from slots. A round has a betting window, hundreds of players can bet on it at once, and the result settles in seconds. These are the checks to run before live casino goes live on your platform.
The short version
- Confirm which studios and tables are cleared for each market and language.
- Prove the wallet answers fast and handles rollbacks and retries.
- Test disconnects mid-round on every game type.
- Set table limits per market and brand.
- Check streams on mobile and weak connections.
1. Studios, tables and markets
Start with the list, not the integration. Which live studios are available in each market you operate in, which tables run in which languages, and which game shows are cleared? With the IGP live casino API, studios such as Evolution, Ezugi and Pragmatic Play come through one connection, and availability is set per market.
2. The wallet under live load
Live rounds close their betting window on a timer, and many players bet in the same seconds. Your wallet has to answer debits quickly and consistently, because a slow answer can mean a rejected bet. Every call must be idempotent on the transaction ID, and rollbacks must reference the original transaction.
- Debit at bet placement, credit at settlement: check both arrive for every round.
- Send the same transaction twice: the balance must move once.
- Cancel a round in the studio: the rollback must restore the stake.
- Check settlement for side bets and multipliers separately.
3. Disconnects and voided rounds
A live round continues whether the player is connected or not. Decide, and test, what happens to open decisions (blackjack, baccarat squeeze, poker) and how the result is shown when the player comes back. When a studio voids a round, for example after a dealing error, the stake should come back through a rollback, and your support team should be able to see why.
4. Table limits and responsible gambling
Live tables carry minimum and maximum stakes, and many markets set their own rules on limits and session behaviour. Configure limits per market and per brand, and check that player-level limits from your platform stop a bet before it reaches the table.
5. Streams and mobile
Most live play happens on phones. Test tables on real devices, in portrait and landscape, on a weak connection and on Wi-Fi. Check how the stream adapts its quality, how long the table takes to open and what the player sees when the stream drops.
6. Lobby and reporting
The lobby needs the table list with dealer language, limits and open seats where the game shows them. Reporting needs every live round in the same format as slots, so live GGR reconciles with the wallet like the rest of the catalogue. Through the same casino API live and RNG content report in one format.
| Check | Pass when |
|---|---|
| Market list | Every live table shown is cleared for that market |
| Wallet speed | Bets are accepted within the betting window under load |
| Idempotency | A repeated transaction moves the balance once |
| Rollbacks | A voided round returns the stake |
| Disconnects | Rounds settle and results show on return |
| Limits | Market and player limits stop bets before the table |
| Mobile | Tables open and stream on real devices |
Frequently asked questions
Live tables through one integration
Evolution, Ezugi, Pragmatic Play and more live studios on the same API and wallet as 18,000+ RNG games, with tables and limits set per market.
See the casino API →
