Built for regulated gaming from the first line
ReelXtra is designed for the scrutiny real-money gaming demands: certified game maths, strict separation between customers, and a record of everything that happens to a bet.
How we protect every bet
Signed API requests
Every call from your backend, whether you are a game Provider or a casino, is signed with HMAC using a secret key issued to you. Your identity comes from the key alone, never from the request body, and keys can be rotated without downtime.
One-time launch links and session keys
The widget starts from a one-time launch code and then uses a random session key that lasts at most 24 hours and is replaced by a relaunch. A launch link works only once, so a copied link is useless.
The widget never handles money
The widget, including the casino overlay, only displays results. It holds no secrets, places no bets and moves no funds; every bet comes from your server. The overlay can run on any page you choose, and its level buttons are advisory (your backend confirms every level), and its on/off switch can only stop or allow play.
Tenant isolation
Each Partner sees only its own Operators, players and Rounds. Every request and every report is scoped to the caller, and cross-tenant access is tested on every endpoint.
Controlled money settings
Changes that affect money or game maths, such as bet levels, RTP choices and jackpot set-up, need a two-factor step-up from the administrator (a code of its own for each change to game maths or RTP choices, and for settlement decisions and staff access; one code that covers other money settings for a short 30-minute session), are effective-dated, and are recorded in a tamper-evident change log that a second person reviews every week.
Full round audit trail
Every Round is recorded with its outcome, win and the exact configuration it was played under, and every jackpot movement sits on an append-only ledger.
Idempotent retries
Retrying a bet with the same bet id returns the original result. A bet is never played twice, and a saved outcome is never re-rolled.
Encrypted throughout
Traffic is encrypted in transit and data is encrypted at rest. Player ids are stored pseudonymised; we never need names, emails or balances.
Certified maths, checked every time
Outcomes are decided only by our game engines and a cryptographic random number generator. The engines and their maths are being submitted to an accredited test lab, and the running game files are checked against the submitted versions.
The display layer is kept separate from the game maths, so visual changes to the widget never alter an outcome.
Operator controls
- Choose the RTP variant per game, from 70% to 96% (Reel Triple from 80%).
- Set the bet amount of every bet level in every currency.
- Set a maximum win cap per Operator.
- Choose private, Group, Partner or Network jackpot Pools.
Hooks for responsible gaming
The Operator stays in charge of its players’ safety. ReelXtra gives Partners and Operators the hooks to enforce it in the Extra Game too.
Player block
Block a player from the Extra Games with a single API call, for example after self-exclusion, and unblock them the same way. A block closes the player’s open sessions and can end on a date you set.
Bet limits
Minimum and maximum bet amounts and a maximum win cap are enforced on our side, on every bet, whatever the client sends.
Compliance Profiles
Market-specific rules applied on the server: minimum time between rounds, whether demo play is allowed, rules and RTP display, and a maximum win. Reality checks stay with the casino.
Player data is pseudonymised: we receive an opaque player id from you, never a name or contact details. Where a market requires player data to stay in the country, ReelXtra is designed to run as a separate, independent deployment.
Questions from your compliance team?
Tell us what your compliance team needs to know about ReelXtra and we will answer directly.