Compliance

Responsible gaming hooks, Compliance Profiles, trigger rules, bet limits and what stays with the Operator (including autoplay).

On this page

Who does what

ResponsibilityWho
Player identity, age and KYC (know your customer)Operator
Combined-bet limits (the Extra Bet plus the triggering bet, where a jurisdiction caps them): we do not check the trigger betOperator (and the Provider, in game integration)
Age-based bet limits (for example a lower cap for ages 18-24): the Operator must not send a play that breaks its own player's limitOperator (and the Provider, in game integration)
Deposits, limits, self-exclusionOperator (through the Provider, in game integration)
Reality checks and session-time reminders: ReelXtra has no reality-check setting, no widget reminder and no SDK event, so the Operator shows its own, from its own clockOperator (through the Provider, in game integration)
Showing responsible-gaming tools to the playerOperator (and the Provider in its game)
Telling us about blocks and exclusionsThe Partner, on the Operator's behalf
Autoplay and turbo: not starting plays from them where a jurisdiction bans them (we cannot observe them and have no autoplay flag)Operator (and the Provider, in game integration)
Game fairness, game maths and RNG (lab-certified)ReelXtra
Enforcing the rules we can observe on Extra Bets (level price, minimum round interval, exposure and max-win caps, demo and game rules, player blocks)ReelXtra, using the Operator's Compliance Profile

Block a player

When a player self-excludes or is blocked by the Operator, tell us:

POST /v1/partner/players/{playerId}/block — signed, nonce required

json
{ "operatorId": "op-42", "reason": "selfExclusion", "until": "2027-09-01T00:00:00Z" }

until is optional (the block is indefinite if absent); we store it, and the block ends at that time. operatorId is optional for an Operator Partner with exactly one Operator. Bets for a blocked player fail with 1501, and the block closes the player's open sessions, so the player needs a new session after the block ends. Undo with POST /v1/partner/players/{playerId}/unblock. You should still stop the player on your side; our block is a second line of defence.

A block can only be lifted by the Partner that set it, or by the Operator's own Operator Partner (an Operator Partner of the same Operator, whoever set the block). Any other Partner gets 1103 unblockNotAllowed and the block stays; this includes a selfExclusion, so a game Provider cannot lift a self-exclusion that the casino's Partner recorded. A block or unblock applies on every server within 5 seconds.

Jurisdiction profiles

Each Operator has a Compliance Profile that we enforce on every bet. A profile belongs to one Domain and may name a jurisdiction; an Operator is given a profile of its own Domain and of its own jurisdiction, or one with no jurisdiction. Each Domain has a default profile with no jurisdiction: in the Open Domain it allows demo play and has every other rule off, and in the Regulated Domain it is strict (2,500 ms between rounds, win-smaller-than-bet-amount celebration suppressed, no "hot" display, demo only in a verified session). A profile can set:

  • whether demo play is allowed, and whether it needs a verified session;
  • a minimum time between rounds for one player (across all sessions and both streams);
  • display rules: no celebration of wins smaller than the bet amount (a loss disguised as a win) and no "hot" jackpot display;
  • a maximum win for fixed (non-jackpot) wins.

Which games and versions may run in a jurisdiction is switched by an emergency stop (1502), not by the profile.

A bet refused because the profile is missing or unusable fails with 1503. A play that breaks the minimum round interval fails with 1505 roundTooSoon and a nextPlayAt.

Trigger

The trigger (bet, gameRef, betRef) is optional context. We store it and show it in reconciliation and support, but never check it against a limit, so a missing or any-sized trigger is never refused. We recommend sending it for reconciliation.

Autoplay and turbo

Autoplay and turbo are your own game modes, and the player's client never calls our interface: your backend does. We cannot see whether autoplay is on, so we enforce no autoplay rule and the bet request has no autoplay field. Where a jurisdiction bans autoplay (for example the UK), it is your responsibility not to send a play that comes from slot autoplay, a casino auto-bet feature or a crash-game auto-bet.

Classification of the casino stream

How a side game attached to arbitrary casino bets is classified differs by regulator and is still pending per regulator (the UK Gambling Commission first). Casino integration pilots therefore run on Operators in the Open Domain (or an already-cleared jurisdiction) first. We will tell pilot Operators when a jurisdiction is cleared.

Bet amount and win limits

  • Bet amounts are the current level prices (see 09-games.md); any other amount is refused. The player chooses the level.
  • Max win: fixed (non-jackpot) wins respect the lower of the Operator's and the jurisdiction's limit. Jackpot payouts are exempt and always paid in full.
  • Risk limits: each Operator has exposure limits agreed with us, covering both streams; when reached, bets fail with 1500. Per-key limits apply to each Partner key.

Rules and RTP

GET /v1/partner/games/{gameId}/rules?operatorId=...&language=... returns the rules text and paytable for the Operator's Game Variant, including the RTP (return to player), the jackpot contribution, the seed and how carried-over bonuses work. Show it in your game's help screen or casino overlay; the widget also links to it. Send the same language as on the session: every language the widget supports has its own rules text, and language in the answer says which one was used.

Operator responsibilities (casino integration)

  • Debit the Extra Bet only once you have decided to send the play, and refund it on a rejection.
  • Keep the launch link from the server to the browser only.
  • Check the origin of overlay SDK events before acting on them.
  • Show responsible-gaming tools to the player next to the overlay.

Personal data

Send only an opaque playerId. We store it only in our player register, linked to an internal player key that no other table or log carries, and never receive names, emails, addresses, age or age band, or payment details. We act as a processor under a data processing agreement with the Operator.