Guide · Live
Two live tables means two streams of debits
Some players want a roulette wheel open beside a blackjack seat. Each table has its own betting window and its own debits. The wallet has to accept both without merging them into one round.
7 min readUpdated By the Turnkeyxgaming team
Decide if you allow it, then test it
If your policy is one live table at a time, refuse the second launch with a sentence that says so. If your policy allows both, the balance has to cope with two reserves in the same second. A lock that serialises the whole player across unrelated rounds will time out the second table. Use row-level updates that can apply two different round ids. History must show two tables, not a blended 'live' line.
Limits are per table and per account. The player can be inside every table limit and outside the account loss limit. The account limit wins. Check it on each debit, not only at launch, because the two windows will both be open when the limit is crossed.
A lock that wraps the whole player will time out the second table whenever the first is mid-debit. Take row-level updates keyed by round id so two bets in the same second both commit. History has to show two tables. A single 'live' line that adds the stakes together cannot be voided correctly when one shoe breaks and the other settles. If your policy is one live seat, say so on the second launch and do not leave the race in place as an accident.
One seat or two, decided on purpose
Either refuse the second launch with a sentence, or support two debit streams. A lobby that sometimes allows both is the version that corrupts history.
| Policy | Second launch | Wallet behaviour |
|---|---|---|
| One live table | Refused, with a reason the player can read. | A single open round. No second debit stream to reconcile. |
| Two tables allowed | Its own launch and its own session. Not a second seat inside the first URL. | Two round ids, two idempotency keys, row-level balance updates. |
| Account limit crossed while both are open | No further launch will help. The windows are already open. | Decline the next debit from either table. Checking only at launch is too late. |
| One table voids, the other settles | Leave the healthy table alone. | Void only the round id that voided. The blended line cannot do this. |
Policy then implementation
- 01
Say yes or no
Either block the second live launch or support it. Do not leave it to chance.
- 02
Distinct rounds
Keep each table's round id intact in history and in idempotency.
- 03
Limit on each debit
Re-check the account limit on every debit from either table.
The lobby can show both. The wallet must not merge them
Correlation is by player, so the account limit sees both streams. Correlation is not by a shared round id. Merging the shoes into one debit makes a void on one table claw back the other.
A void on one table while the other settles
At 21:52 a shoe is pulled mid-hand and the studio voids the blackjack round. At 21:53 the roulette table settles a winning number. The player opened both from two launches, so your ledger holds two round ids, two debits, two idempotency keys and one player id. None of that is unusual. What makes it an incident is a history table that wrote both bets into a single line labelled live.
The void references the blackjack round id. If the row carrying that id also carries the roulette stake, reversing the void refunds money the roulette table already won, and the settlement arriving a minute later reads as a duplicate. Keep the round id as the unit of record, and let a screen group by player without ever collapsing the ids underneath.
Order of arrival is the second trap. A void can land before the settlement that follows it, and a reconciliation job that reads a balance delta rather than individual round states will draw the wrong conclusion from whichever message came first. Read state per round id, then add. A display may show one balance and two tables. A ledger cannot.
What has to exist per open table, before the second launch is allowed
- A launch record per table: the game id, the table, and the session that opened it.
- A round id and an idempotency key belonging to that table alone, so a retry cannot cross the two.
- The debit written against the round rather than against the player's live total, so a void has something exact to reverse.
- A settlement or a void per round id, applied in the order received, with neither inferred from the other.
- A history view that lists two tables under one player without merging their money; see round history disputes.
- The account limit checked on each debit, since both betting windows are open before either stake is taken.
FAQ
Questions operators ask
Can one launch URL serve two tables?
No. Each table is its own launch and its own session. The lobby can show both. The wallet correlates them by player, not by a shared round.
Can one launch URL open roulette beside blackjack?
No. Each table is its own launch and its own session. The lobby may display both windows. The wallet ties them together by player id when it checks the account limit, and keeps their round ids apart.
What fails if we serialise all debits for that player on one lock?
The second betting window. It will time out while the first debit holds the lock, and the studio will treat the timeout as an unanswered stake. Row-level updates on distinct round ids let both commits land.
Our history page shows one live total per player. What breaks when one table voids?
The void has no round to attach to, so the reverse either hits the total or hits nothing. Refunding against the total can return a stake the other table already settled, and the studio's settlement then reads as a second credit. Store per round id first and let the page derive a total from those rows.
Can a player at a blackjack seat also join a game show from the same balance?
The balance is one, the sessions are not. Each table is launched separately and each has its own betting window, so the real question is whether your policy permits a second concurrent session and whether the wallet can take two debits in the same second. Answer it as policy first; the implementation follows.
Keep reading
Related pages
- Product · Live dealerLive casinoRoulette, blackjack, baccarat, game shows, teen patti and andar bahar on one dealer-table wallet and one GGR report, per licensed market.Read
- Catalogue · BlackjackBlackjackLive blackjack shoes, side bets, bet-behind seats and speed deals, each settling on your existing wallet with no second integration.Read
- Catalogue · RouletteRouletteEuropean, American and multiplier roulette need the wheel type, the limits and a rollback path for when a spin voids mid-round.Read
- Guide · LiveVIP table limitsHow minimum and maximum stakes define a live table, and why a VIP wheel should not share a lobby row with a low-limit one.Read
Get a written quote and sandbox access
Tell us your licence, target markets and products. You get the GGR rate in writing, the studio list for your markets and sandbox credentials.