Poker API Integration: Five Handoffs Worth Defining Up Front

When a poker API integration runs late, the code is rarely the reason. The delay sits at a handoff: a point where a player, a balance or a complaint passes from your platform to the network, and nobody agreed beforehand who catches it.

On an API integration with WePlay, you keep the player account, the wallet, KYC, payments and the licence. We run the tables, the tournament schedule, the network promotions, anti-fraud and settlement between operators. Between those two lists sit five handoffs. Each one hides a decision that takes ten minutes in a scoping call and a lot longer in a live incident on a Sunday night.

This post assumes you run your own platform and licence and connect through our API. If you're still choosing a route, our comparison of white label and API models covers that first. The five handoffs below come in the order a player meets them.

Five poker API handoffs between your platform and WePlay Network: login, wallet, player protection, promotions, support and security

1. Login: who the player is at the table

Your player already has an account with you, and with an API integration they don't need a second one for poker. Your platform tells the network who is sitting down, and the network trusts that answer. The decision is how much your platform says.

Keep it short. The network needs a stable player ID, a currency, a country and a status that says this player may play. It doesn't need a name, a home address or a passport scan. Those stay with you, under your KYC process and your licence, and every field that doesn't cross the API is one less item in the GDPR checks both sides go through before signing.

Then settle the nickname. At a shared table your player sits next to players from every brand on the network, so a nickname has to be unique across the whole network, not just on your site. Agree who picks it (the player at first launch, or your platform by a rule) and what happens when it's already taken. Decide too whether your brand name may appear in it. A nickname like "BrandX_VIP7" tells every regular at the table which skin the player came from, and regulars keep notes on skins.

The last login question is about change. When you close an account, suspend it or freeze it for a KYC review, the network has to hear about it while the player may still be seated. Agree how that status reaches the tables and how fast. It leads straight into the third handoff.

2. Wallet: every buy-in and every cash-out

With a shared wallet, often called a seamless wallet, poker draws on the same balance as your casino and sportsbook. The network asks your wallet to debit the player when they sit down at a cash table or register for a tournament, and to credit them when they stand up, cash a prize or unregister. Your slot providers already call your wallet this way. Poker adds two things a slot round doesn't have.

The first is time. A spin is settled in seconds. A cash game seat can stay open all evening and a tournament can run for ten hours, with the player's money committed the whole time. Agree what your balance shows while chips are on the table, and tell your finance team that money sitting at a poker table still belongs to the player. Your revenue is the rake.

The second is failure. Sooner or later a call times out: the network asked for a debit and never got an answer. Was the player charged or not? Two rules settle it before it happens. Every transaction carries its own ID, and a request repeated with the same ID gets the same answer without moving money twice. And no chips appear at the table until your wallet has confirmed the debit. GLI-19, the technical standard many regulators test online gaming systems against, asks for a confirmation or a denial of every financial transaction a system starts.

Cash-outs need the opposite rule. A credit that fails can't simply be dropped, because leaving a game has to put the player's money back in their account balance. So agree how a failed credit is retried until your wallet confirms it. The transaction ID is what stops the retry from paying the player twice.

Currency is the last wallet decision. If your players hold euros or reais and the tables play in dollars, agree who converts, at which rate, and when: at the buy-in, at the cash-out, or both. A player who buys in for 100 and stands up an hour later with the same stack will ask why only 98 came back. Either answer to that question can be defended. Hearing the question first from the player can't.

Poker API wallet flow showing a confirmed debit, in-game chips, a timed-out credit and an idempotent retry paid once

3. Player protection: limits, exclusions and the tournament in progress

Your licence carries the responsible gambling rules, and your platform holds each player's limits and exclusions. The network has to respect them at the table. The front door is the easy part: an excluded player can't open the poker client or register for a tournament. Your wallet stands behind that door too, because a debit request for an excluded account should come back refused. Agree the error code as well, so the player reads "your account is excluded" and not "technical error, please try again".

The harder case is a player who is already sitting down. Poker money stays in play for hours, so an exclusion can land in the middle of a hand, a session or a tournament. GLI-19 asks operators to spell out in their terms what happens to wagers that are still undecided when an exclusion takes effect, and whether they're returned or settled. For poker, that means a written rule for each case. One workable set:

  • In a cash game, the hand in progress plays out, then the player leaves the table and the stack goes back to their balance.
  • In a tournament that hasn't started, the registration is cancelled and the buy-in refunded.
  • In a tournament that's running, the player is sat out and the stack blinds away, with any prize it reaches paid to their balance.

The last one deserves a second look. Pulling a stack out of a running tournament changes the prize equity of every other player in it, and on a network those players came from other brands. Sitting the player out leaves the tournament as it was. An excluded player can still withdraw, so a prize paid to the balance doesn't have to sit there.

Limits need the same care, because poker money doesn't move like a stake on a slot. A player who sits down with 50 and leaves with 62 has risked 50 and lost nothing. A player who re-enters a tournament three times has made three buy-ins. Agree how buy-ins, re-entries and cash-outs count against the loss and stake limits your licence asks you to offer, and whether a limit reached mid-session stops the next hand or only the next buy-in. If your licence requires reality checks, agree where the poker client shows them: between hands. A pop-up over an all-in decision helps nobody.

4. Promotions: who pays for what, and where it lands

On a network, promotions come from two places. The network calendar runs for every brand: the guaranteed tournaments, the Daily Ticket System with its freerolls and satellites, and the Bad Beat Jackpot, which every player on your brand is in from their first hand. Network guarantees come at no extra cost to you and need no integration work beyond a place in your lobby. Your own promotions sit on top: private tournaments, tickets as CRM rewards, or something only your brand runs, like tournament tickets for your biggest cash-game losers.

The handoff questions are about your own promotions. Does your CRM issue a ticket through the API, or does your team do it in the back office? Which balance does a cash reward land in? And the one that matters most at a shared table: can a poker buy-in draw on bonus money?

Think that last one through before saying yes. On a slot, the house edge wins most bonus money back while the player clears the wagering requirement. At a shared poker table, a chip bought with bonus money can end up with a player from another brand, and there it's real money. The monthly settlement between operators counts it at face value.

Bonus rules also attract the people who read them most carefully. Sumsub describes the poker version of bonus abuse: a player loses chips on purpose to a partner while clearing a wagering requirement. Agree who can claim a ticket or a poker bonus, how often, and from how many linked accounts, and write it down next to the ticket API in the scoping document.

Then agree what comes back. Your CRM can only run a casino-to-poker journey if it hears what happens at the tables: a first tournament registration, a first cash game, a ticket won and not yet used. Decide which poker events reach your platform, through the API or the back office reports, and how often, so your CRM team can build on them from launch day.

5. Support and security: who answers the player

Your support team will get poker questions from day one, and not all of them are theirs to answer. A pending withdrawal is yours. A player who swears the river is rigged, wants a hand history or got disconnected on the bubble needs someone who knows the game and can see the tables.

Agree the split before launch. Your agents handle the account, payments and KYC. Game questions go to the network's poker support, with a response time and a set way of passing the ticket over, so the player doesn't have to tell the bad beat story twice. Give your agents access to hand histories in the back office as well: plenty of "rigged" tickets close the moment someone shows the player they got it in as a 4-to-1 underdog. On WePlay, the escalation route is one shared chat with our support, tech, anti-fraud, marketing and finance people, across every time zone.

Security runs the other way. The network sees every table, so we detect collusion, bots, chip dumping and multi-accounting, and the penalties are set out in our published Security & Ecology Policy. The player's money, though, sits in your wallet. A chip dumper's plan only works if the money leaves before anyone looks. Sumsub's advice is to act before funds are withdrawn, and to treat a withdrawal that follows a deposit with little genuine play in between as a reason to investigate. So agree how fast your payments team can hold a withdrawal when we ask, who tells the player, and what evidence we send so your team can stand behind the decision.

Players need a way in, too. GLI-19 asks operators to give players a way to report suspected cheating, collusion or bots. Decide whether those reports come through your support desk or go straight to ours, and tell your agents where to send them.

Poker support escalation table mapping player questions to operator support, WePlay poker support or WePlay security

What stays off your integration list

Those five handoffs are the whole list on your side. Everything behind them is the network's daily work and needs no integration from you: filling the tables, the cash game spread and the tournament schedule, the guarantees, player ecology, fraud detection and settlement between operators. The rake your players generate stays with you, and once a month the network squares what players won and lost across brands in a single settlement.

Put all five in the scoping document

Every WePlay integration starts with a technical welcome: architecture, APIs and integration options, ending in a signed scoping document. That document is where these five answers belong. We set the timeline with you from it rather than promise a date on the first call, because an open handoff tends to surface late, in testing, when it's slowest to fix.

Printable poker API integration checklist covering login, wallet, player protection, promotions and support decisions

Want the five answers before your platform team writes a line of code? Book a technical call, bring your platform people, and we'll go through each handoff against your setup.

Book a call

Poker API integration: quick answers

What is a poker API integration?

It connects a poker network's games to your existing casino or sportsbook platform. Your player accounts, wallet, KYC and payments stay where they are, and your players reach the tables through your site with the same login and the same balance.

Do I need my own licence to integrate poker through an API?

Yes. With an API integration, poker runs under your licence and your brand. Operators without a licence can launch as a Whitelabel Skin under WePlay's licence instead. Either way, each operator stays responsible for the legality of its operation in the markets it targets.

How long does a poker API integration take?

It depends on your platform and on how quickly the handoffs get agreed. WePlay sets the timeline with you in the scoping document at the start, rather than quoting a date before anyone has seen your stack.

Can players use one wallet for casino, sportsbook and poker?

Yes. With a shared wallet, poker buy-ins and cash-outs go through the same balance as casino and sportsbook, so a tournament prize sits one tap away from the slot lobby or the bet slip.

Who handles KYC and responsible gambling on an API integration?

You do, under your licence. The network applies the limits and exclusions your platform sends, at the tables and at tournament registration.

Who deals with collusion and chip dumping?

The network detects it and sets penalties under its published Security & Ecology Policy. Player funds sit in your wallet, so your team holds withdrawals and acts on the account when a case needs it.