Environments & onboarding
Sandbox vs production, IP allowlists, credentials, SLA, per-operator config
Environments
Every environment uses the same host pattern on its own domain:
| What | Host pattern | Sandbox example |
|---|---|---|
| Launcher API | https://api.<domain>/game/gamelauncher | https://api.lpmbackstagedevelop.com/game/gamelauncher |
| Game iframe | https://<game-host>.<domain> (one per game) | https://bingo.lpmbackstagedevelop.com |
| Replay | https://replay.<domain> | https://replay.lpmbackstagedevelop.com |
| Replay dashboard | https://replay-dashboard.<domain> | https://replay-dashboard.lpmbackstagedevelop.com |
Sandbox is shared across all integrators in development. The
lpmbackstagedevelop.com domain is our development sandbox — production runs
on a separate domain you'll receive in writing during go-live. Game hosts
always come to you inside the launchurl, so you never need to build them.
SLA and uptime
Indicative targets — final numbers are confirmed in your contract:
| Metric | Target |
|---|---|
| Monthly uptime (production) | 99.5% |
| Incident acknowledgement | 30 minutes during business hours |
| Major-incident comms | Updates every 30 minutes until resolved |
| Planned maintenance | Announced ≥ 7 days in advance, outside peak windows |
A public status page is provided at go-live. Subscribe to it for incident and maintenance notifications. We treat any of the following as a major incident:
- A spike in wallet-call failures
- A burst of
5xxresponses (server-side errors, status 500–599) from the launcher API - Settlement delays over 60 seconds
IP allowlists
- Inbound (you → us) — we identify your calls by the credentials we issue you.
- Outbound (us → you) — for direct integrators only. Our wallet calls come from a fixed egress IP (the public IP our servers use when calling out). We share it at onboarding so you can allowlist it on your wallet endpoints.
We support TLS 1.2 and 1.3 only — TLS 1.1 and earlier are rejected.
A note on the WWW-Authenticate header: our 401 responses include a
Basic realm="..." value, and that label may differ between endpoints.
The realm is only the human-readable string a browser shows in its native
auth prompt and carries no integration meaning — treat it as
informational.
Credentials
Basic Auth credentials are exchanged out-of-band during onboarding. Rotate on request; rotation requires coordinated cutover.
Reconciliation feed (aggregator path)
If you're going through an aggregator, we don't publish a parallel reconciliation feed. Your aggregator's wallet record is the canonical source — typically a transaction export from their operator portal.
If you need transaction-level data from us directly (e.g., for an internal-audit dashboard), we can provide signed CSV exports per operator on request. Talk to us during onboarding.
Per-operator configuration
Tell us, per operator and per brand:
- Supported currencies — ISO 4217 codes, or sweepstakes codes such as
SCandGC - Stake ladders — the allowed per-card stake values (configured per operator on our side, not exposed as an API field), expressed in player-facing game units. Wallet wire conversion happens inside our integration adapter (see Money).
- Lucky line bet percent options — pick the subset you want (e.g., 10%, 25%, 50%, 100% of card stake)
- Maximum cards per player per round
- Payout rate (RTP) — for some games we can set your own RTP, even when your players share a room with other operators; ask which
- Slots — which slot games your rooms offer, and the per-spin stakes per currency (see Slots)
- Free cards — whether to switch them on, and your campaigns (see Free cards)
- Jurisdictions — where you operate, so we can confirm the game is approved there
- Languages — currently
en; ask if you need others
Configuration changes take effect from the next round — no deployment required on your side.