Infrastructure / RGS Protocol

OpenRGS connects your platform to every FourPlay game.

One signed protocol for session launch, round results, and wallet callbacks. No SDK, no client to maintain - just REST, and a webhook your team already knows how to handle.

Request Integration Read Docs

01 Your Platform Operator / Aggregator

session/launch

02 OpenRGS Engine Signed - Stateful - Logged

wallet/debit, credit

03 Player Wallet Your infrastructure

<40msAvg Latency

99.98%Uptime SLA

HMAC-SHA256Session Auth

REST - JSONNo SDK Required

Protocol Philosophy

Built to disappear into your stack.

"Operators don't need another platform to manage. They need games that show up, behave, and report back."

OpenRGS lives behind an iframe and a webhook. Your wallet stays on your servers, your player data stays yours, and every round is signed and logged on ours.

Whether you connect through an aggregator or integrate direct, the contract doesn't change: signed requests in, signed responses out, every time.

Request to Response

Integration Flow

Protocol: REST / JSON

Casino Launch

Your platform sends player and game details to /session/launch. No login screens, no redirects.

→

Secure Token

OpenRGS signs a session token with HMAC-SHA256 and a short, configurable expiry.

→

Game Session

The game loads inside your iframe using the signed launch URL. Session state lives on our side.

→

Wallet Callback

Every bet and win triggers a real-time callback to your wallet - debit, credit, or rollback.

→

Round Result

Balances reconcile, the round closes, and the full record is stored for audit.

Live Demo

Try The Launch Flow

Sandbox / No Auth Required

Pick a game, a currency and an operator ID, then trigger /rgs/v1/session/launch. The console mirrors exactly what your server gets back - a signed launch URL, ready to drop into an iframe.

This is the same call your platform makes in production. Sandbox responses use mock tokens, but the shape of the payload is identical.

Session Launcher

Game

Currency

Operator ID

// Awaiting session request.

> RGS: idle

> Endpoint ready: /rgs/v1/session/launch

Engine FourPlay Game engine v2.x

Protocol OpenRGS RGS specification

Wallet External Operator-controlled

Auth HMAC-SHA256 Signed session tokens

B2B Infrastructure

What OpenRGS Handles

System Status: Stable

01 / Security

Token-Based Auth

Every session gets a signed HMAC-SHA256 token with a configurable expiry. Per-round nonces stop replay attempts cold.

Auth: HMAC-SHA256

02 / Transactions

Callback API

Debit, credit, and rollback run through REST callbacks, each with an immutable transaction ID for reconciliation.

Channel: Wallet_Callback

03 / Control

Operator Control

Bet limits, currencies, languages, demo mode - all configured per session, by you.

Config: Per_Session

04 / State

Session Management

Session state lives server-side, with automatic recovery and clean expiry handling.

Storage: Server_Side

05 / Audit

Round History

Full round logs - seeds, outcomes, transactions, timestamps - ready for audits and reporting.

Retention: Full_Log

06 / Performance

Low Latency

Multi-region infrastructure keeps responses under 40ms, with rate limiting and failover built in.

Regions: Multi_Region

Reference

Core Endpoints

REST - JSON - HTTPS

Starts an authenticated game session and returns a launch URL with a signed session token.

Request

{
  "operator_id": "op_demo_001",
  "player_id": "player_88291",
  "game_id": "battle_royale_engine",
  "currency": "BRL"
}

Response

{
  "launch_url": "https://play.fourplay.studio/s/fp_sess_9a87cdb8",
  "session_token": "fp_sess_9a87cdb85fec1823",
  "expires_in": 600
}

Callback sent to your wallet endpoint before each round, to validate and reserve player funds.

Request

{
  "transaction_id": "tx_deb_8192a",
  "session_token": "fp_sess_9a87cdb85fec1823",
  "amount": "5.00",
  "currency": "BRL"
}

Response

{
  "status": "OK",
  "balance": "1445.00"
}

Returns round results, provably fair seed data, and transaction history for a given round.

Request

GET /rgs/v1/round/rnd_77281f
Authorization: Bearer fp_sess_9a87cdb85fec1823

Response

{
  "round_id": "rnd_77281f",
  "seed": "a13f7e...e92c",
  "outcome": "WIN",
  "payout": "40.00",
  "timestamp": 1781234567
}

OpenRGS Protocol●REST API● HMAC-SHA256 Signed●Wallet Callbacks● Sub-40ms Latency●99.98% Uptime● Operator-Controlled●Session-Based Auth● OpenRGS Protocol●REST API● HMAC-SHA256 Signed●Wallet Callbacks● Sub-40ms Latency●99.98% Uptime● Operator-Controlled●Session-Based Auth●

OpenRGS - Production Ready

Your Wallet. Your Control. Our Infrastructure.

Bring FourPlay games into your platform without giving up control of player funds, sessions, or data. One protocol, fully documented, ready when you are.

Request Integration Read Docs

Versionv2.4.1

Status All Systems Online

SpecOpenRGS / REST / JSON