Who integrates poker instead of buying a room
Operators who already run a casino or a sportsbook, with player accounts, KYC and a wallet in place, and want poker as another vertical for the same players. The poker server comes from a vendor; you keep the account, the cashier and the customer. If poker is meant to be the main business, with its own pool and its own brand, the decision is different and lives on the standalone poker platform page.
The direct answer: integrate when poker is a cross-sell and your platform already has a single wallet, real-time limits and an AML team. Budget most of the work for the wallet, because poker breaks three assumptions a casino wallet is built on.
What changes in the wallet
A casino studio debits your wallet for each spin and credits each win, which is the model on the casino API page. A poker table cannot work that way, because a pot is won from other players, not from you. Poker servers therefore keep a table balance separate from the account balance. The API of Poker Mavens, a commercial poker server, is one example: it reports a player's account balance and chips in play at ring games as separate fields, and reports the amount and net result when a player leaves a table.
| Moment | Casino game | Poker table or tournament |
|---|---|---|
| Money leaves the balance | A debit per spin or hand | One debit at buy-in, or at tournament registration |
| During play | Your ledger is the record | The poker server holds the table stack or the prize pool |
| Money comes back | A credit per win | One credit when the player leaves the table, or a prize when the tournament ends |
| Rollback | Reverses a named transaction in a round | A settled hand cannot be reversed: the pot went to other players. Only an unused buy-in or a cancelled tournament is refunded |
| Disconnect | Resolved by the studio's own rules | The stack stays at the table; an "away from play" status skips turns, then removes the player |
| What you earn | Stakes minus wins | Rake and tournament fees, reported separately |
The practical consequence is in reconciliation. At any moment part of a player's money may sit at a poker table, and your withdrawal screen, responsible-gaming limits and finance reports all need that figure. Ask the vendor how it is exposed before you sign.
One account, one set of limits
The point of integrating is that a player does not register twice. One login and one KYC record from your player account management mean one self-exclusion and one set of limits across casino, sportsbook and poker. Three details need deciding at scoping:
- Nickname. Players at a table see each other, so poker needs a screen name separate from the account name, with your moderation rules applied to it.
- Limits in real time. A self-exclusion or a new deposit limit must reach the poker server at once and stop new buy-ins, not wait for the next session.
- Loss limits. A poker loss goes to other players, and a tournament buy-in is a loss only once the tournament ends. Define how buy-ins and table results count against each limit before launch.
Where the liquidity comes from
Integration settles the account and the wallet. It does not answer who your players will play against. There are two answers. Your players join the vendor's network, where they sit with other operators' players; or your brand gets a room of its own on the vendor's engine, which is a standalone room behind an integration.
On a network, the network sets the rules. One vendor's network-skin page, for example, keeps table configuration, tournament scheduling and anti-fraud under central control, while an API integration lets the operator keep its own payments and user accounts. Licences add conditions too. On the Isle of Man, operators who supply players to a Network Services licensee must contract with it and are expected to meet Isle of Man AML and KYC standards for those players. Your KYC level becomes a condition of entry to the network.
What your platform must already do
| Requirement | Why poker needs it | If it is missing |
|---|---|---|
| Licence scope covering poker | Not every licence does: Cyprus prohibits poker for private operators | No integration can fix it |
| Single wallet with idempotent transaction IDs | Buy-ins and cash-outs are retried after network faults | Duplicate buy-ins or lost cash-outs |
| Real-time limit and exclusion events | Buy-ins must stop the moment a limit changes | A self-excluded player still seated |
| Bonus rules that can release on rake | Poker rewards such as rakeback are earned through rake, not wagering | Casino-style wagering rules that do not fit poker |
| AML monitoring between players | Chip dumping moves money from one account to another | Collusion that the poker vendor flags and nobody acts on |
| Support access to hand history | Disputes are about specific hands against specific players | Every dispute escalated to the vendor |
Chip dumping is listed in GLI-19, the interactive gaming systems standard from Gaming Laboratories International, as one of four collusion patterns the operator must take measures against. The standard puts that duty on the operator, so on an integration it stays with you even when the vendor runs the detection.
Who should not integrate poker
- An operator whose licence does not cover poker in the target market.
- A platform with a transfer-only wallet or limits that sync once a day. Fix those first.
- A brand that expects poker to be profitable on its own from month one. As a cross-sell it keeps players; as a standalone business it needs its own case.
Where poker integrations fail
- Money nobody can see. Table stacks are missing from the player's balance view, so withdrawals and limits are calculated on the wrong number.
- Casino rollback logic applied to poker. A rollback after a settled hand fails, or worse, succeeds and creates money.
- Bonus abuse through poker. Casino bonus money reaches a poker table and is dumped to a partner account.
- Two support desks. The vendor holds the hand histories, your team holds the customer, and every dispute waits on both.
Questions for the poker vendor, including us
- Which wallet calls does poker make, and how is money at a table or in a prize pool reported to my platform?
- What happens to a buy-in, a table stack and a tournament entry if the connection between our systems fails?
- How do self-exclusion and limit changes reach the poker server, and how fast?
- Do my players join a network or a room of their own, and whose rules apply in each case?
- Who reviews collusion and bot alerts, and what do I receive when a case involves my player?
- Can my support team open hand histories, or only request them?
We integrate poker into casino and sportsbook platforms through the same five stages as any delivery, and the wallet contract is the first document we agree.
Frequently asked
Can poker share a wallet with my sportsbook and casino?
Yes. The difference is that poker moves money into a table or a tournament and back, instead of debiting per bet, so the wallet must show money at a table as part of the player's position.
Is a poker API the same as a casino game integration?
No. A casino game is one player against the game. Poker is players against each other, with a server that holds stacks, prize pools and hand histories. The launch flow looks similar; the money flow and the integrity duties do not.
Do I need my own poker liquidity?
No. Joining the vendor's network gives your players full tables from the first day. Your own room only makes sense when your players can fill tables on their own, which the standalone platform page helps you test.
Who handles collusion and bots?
Usually the vendor runs detection, and on a network it is central. The licensed operator still has the duty to act, so agree who reviews alerts, who closes accounts and who reports to the regulator.
Can casino bonuses be used at poker tables?
They can, but bonus money at a table between players can be passed to a partner account by chip dumping. Keeping casino bonus money out of poker, and rewarding poker players through rakeback or rake-based release, closes that route.