Jackpot RGS

The Remote Gaming Server (RGS) handles game sessions, provably fair game logic, and wallet transactions for Jackpot Studio's casino platform.

API-First

HMAC-authenticated REST API for launching sessions and managing games. Your backend calls us — we call you back for wallet operations.

18 Games, 38 Codes

Dice, Limbo, Plinko, Keno, Mines, Wheel, Baccarat, HiLo, Towers, Lightning Plinko, Lightning Keno, Blackjack, Blackjack (Multi Seat), Doctor Pump, Roulette, Cases, Coinflip, and Pinball — available at multiple RTP levels. 38 game codes total.

Multi-Region

Geo-distributed infrastructure with latency-based routing. Player data stays in the closest region.

How It Works

As an operator, you integrate by:

Calling the RGS to launch sessions and list games (HMAC-authenticated)
Receiving callbacks from the RGS for player authentication, bets, and wins (your wallet server)
Embedding the game iframe in your platform using the launch URL

sequenceDiagram
    participant Operator as Operator Backend
    participant RGS as RGS API
    participant Client as Game Client (iframe)

    Operator->>RGS: POST /operator/launch
    RGS->>Operator: POST /callback/authenticate
    Operator-->>RGS: { status, balance }
    RGS-->>Operator: { sessionToken, launchUrl }

    Operator->>Client: Embed iframe at launchUrl

    Client->>RGS: POST /game/play
    RGS->>Operator: POST /callback/debit
    Operator-->>RGS: { balance }

    RGS->>Operator: POST /callback/credit
    Operator-->>RGS: { balance }

    RGS-->>Client: { game result }

Next Steps

Onboarding Get your credentials and start exploring Quick Start Full technical walkthrough of the launch and game flow Responsible Gaming Reality checks, session limits, bet limits, and self-exclusion enforcement

Onboarding