Environments & onboarding
Sandbox vs production, IP allowlists, credentials, SLA, per-operator config
Environments
| Environment | Launcher base URL | Game iframe host | Replay host |
|---|---|---|---|
| Sandbox | https://api.lpmbackstagedevelop.com/game/gamelauncher | bingo.lpmbackstagedevelop.com | replay.lpmbackstagedevelop.com |
| Production | TBD (issued at go-live) | TBD | TBD |
Sandbox is shared across all integrators in development. Production hosts
are provisioned during onboarding. The lpmbackstagedevelop.com domain is
our development sandbox — production runs on a separate domain you'll receive
in writing during go-live.
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
We require allowlisting in both directions:
- Inbound (you → us) — share your egress IPs (the public IPs your servers
use when calling out) so we can allow them through to
/gamelauncher/*. - Outbound (us → you) — for direct integrators only. We share our egress IPs so you can allow them through to 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: 401 responses include a Basic realm="..." value that differs by endpoint:
/gamelauncher/play→Basic realm="VisionLINK Provider API"/gamelauncher/replay→Basic realm="lpg-gamelauncher-replay"
The realm is the human-readable label browsers show in the auth prompt and is informational only. Ignore it.
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 like Gametech, we don't publish a parallel reconciliation feed. Your aggregator's wallet record is the canonical source — for Gametech, that's the transaction export available in 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 alphabetic codes
- Stake ladders — the allowed per-card stake values (configured per operator on our side, not exposed as an API field), in the currency's smallest unit (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
- Jurisdiction — affects RTP profile, replay retention, and which responsible-gambling defaults apply
- Languages — currently
en; ask if you need others - Channels —
web,mobile-web,native - Whether
DEMOmode should be available in your environment
Configuration changes take effect on the next session — no deployment required on your side.