The 5 endpoints you actually need

GET /games — the catalog
POST /session — creates a launch token
POST /wallet/balance — called by the game before every bet
POST /wallet/debit and /wallet/credit — the round callbacks
POST /wallet/rollback — for reversals and disconnects

Session token flow

Player clicks a game → your backend POSTs to /session with player_id, currency, language → aggregator returns a signed launch_url → you iframe it. The token is single-use and expires in ~5 minutes.

Callback security

Every wallet callback must be HMAC-signed. Verify the signature before touching the wallet. Idempotency keys are mandatory — the same transaction_id must never debit twice.

Rollback and disconnect handling

If a round fails mid-way the RGS sends a rollback with the original transaction_id. If your service is down the aggregator retries with exponential backoff. Handle both or you'll have reconciliation nightmares.

Testing

Every real Casino Game Integration ships with a sandbox that lets you simulate wins, losses, disconnects and rollbacks. Don't go live without covering all four.

Want to see it in action? Read the docs or check pricing.