Go-live checklist

Everything that must be true on your side before real-money traffic, with one checklist per integration stream.

On this page

These are your responsibilities under the agreement. We verify the technical items in the sandbox certification run. Complete Both streams, then the list for your stream.

Both streams

Security

  • API (application programming interface) secrets are stored in a secrets manager and never logged; access is limited to named staff.
  • Only your servers call the API (application programming interface). sessionToken and secrets never reach a browser. The launchUrl goes from your server to the browser only.
  • Your egress IPs are registered for the IP allowlist.
  • You can rotate keys without downtime, and you have a contact who reports a suspected key compromise to us immediately.
  • Your servers use NTP (Network Time Protocol); timestamps are UTC (Coordinated Universal Time).

Bets and money

  • Every bet has a new, unique betId, never reused.

  • Retries resend the identical request (including trigger) with the same betId until a definite answer, then cancel after the retry horizon.

  • You credit the win field (which includes any carried-over bonus) on committed.

  • You refund on voided, cancelled and on every 4xx error.

  • Amounts are handled as decimal strings, never floating point.

  • betCreatedAt is the real creation time.

  • Every bet sends the level the player chose and an amount equal to that level's current price (from /levels), never derived from the triggering bet.

  • On 1201 priceMismatch you refund, read the returned level and price (or /levels), and only then send a new bet with a new betId.

  • On 1506 maintenance (HTTP 503, but definite) you refund the bet, don't retry that betId, and send new plays with new betIds only after maintenanceUntil.

  • On 1507 settlementSuspended (HTTP 403, definite) you refund the bet, don't retry that betId, and stop sending new plays for that Operator's Network Pools until your account manager says the suspension is lifted (staff lift it by hand, on the next configuration publication). Retries of accepted bets still return their result.

  • You hide the Extra Game while maintenance.active is true (from GET /v1/partner/games or /levels) and until maintenanceUntil, and you handle 1506 on session create and relaunch.

Sessions and widget

  • Your CSP (Content Security Policy) allows our one host (frame-src and script-src).
  • You relaunch with POST /v1/partner/sessions/{sessionId}/launch on page reload or navigation, instead of creating a new session.
  • You send the Operator's own player id as playerId (required for Operator Partners, recommended for Providers).
  • The rules screen (from GET /v1/partner/games/{gameId}/rules) is reachable from your page.

Compliance

  • Blocks and self-exclusions are forwarded with POST /v1/partner/players/{playerId}/block.
  • You keep the combined bet (the Extra Bet plus the triggering bet) within the Operator's jurisdiction cap: we do not check it.
  • You never start a play from autoplay (slot autoplay, casino auto-bet or crash auto-bet) where the Operator's jurisdiction bans it. We cannot observe autoplay and enforce nothing on it.
  • You never send a play that breaks the player's own age-based bet limit (we receive no age data and cannot check it).
  • Only opaque player ids are sent; no personal data.

Operations

  • Daily reconciliation runs, and breaks are reported to us within the agreed time.
  • You act on reconciliation requests after any incident.
  • Support staff know how to look up a bet (GET /v1/partner/rounds/{betId}) and quote requestId and roundId.
  • You have subscribed to our status and change notices.

Game integration (Provider)

  • Each Extra Bet is debited before POST /v1/partner/bets, and refunded on a rejection.
  • Each play carries a trigger (optional, but recommended for reconciliation) with the base spin's bet, game and spin reference.
  • You call reveal(roundId) when the base reels stop (Level 1). Level 2 has no reveal call. If you don't call it, the result shows after the Operator's short timeout (default 2 s).
  • You don't call us for free spins or bonus rounds, or any spin where no Extra Bet was charged.
  • The player can switch the Extra Game on and choose the bet level in your game, and you send that level and its price as level and amount.
  • You read enabled from the ready event and from every optInChanged { enabled, reason }, and you send no play while it is false. You hide the widget only with rx.hide(), and you treat 1508 sideGameOff as "off": refund, don't retry.
  • You send operatorId on every call.

Casino integration (Operator)

  • Your trigger rule is written down and decides which casino bets trigger a play (including whether free spins and bonus rounds count).
  • You debit the Extra Bet only after you have decided to send the play, and refund it on any rejection.
  • You keep nextPlayAt per player and skip the play, before debiting, on 1505 roundTooSoon.
  • Your backend confirms the player's opt-in and level and sends the level in each play. The widget never sends a bet.
  • You read enabled from the ready event and from every optInChanged { enabled, reason }, and you stop offering and sending the side game while it is false (the player's switch or a hidden widget). You resume when it is true.
  • You hide the widget only with rx.hide() (and show it with rx.show(), or mount it with hidden: true). Hiding the iframe in any other way can't be enforced and plays unseen.
  • You treat 1508 sideGameOff as "the side game is off": you refund the bet amount, don't retry, and don't count it as a failure.
  • You check the origin of the SDK events (optInChanged, levelChosen) before acting on them. If ReelXtra turned on widget level control for your Operator, levelChosen is only a hint your backend confirms; if not, your own level picker feeds your backend.
  • You run one SDK instance per Extra Game shown in the overlay.
  • Responsible-gaming tools are shown next to the overlay.
  • The combined bet (the Extra Bet plus the triggering bet) stays within the jurisdiction's cap (UK): we do not check it. trigger is optional context.
  • Your pilot runs on an Operator in the Open Domain or a jurisdiction we have confirmed as cleared.