Skip to content

Introduction

Welcome to the Game Provider integration documentation.

Game Provider is a casino game provider that lets you embed and operate a growing catalog of games — both classic iframe titles (e.g. Chicken Race) and server-driven titles (e.g. Aviadrone) — on your casino platform.

How the Integration Works

From the Operator's perspective the integration boils down to two things:

  1. Launch — you call one endpoint on Game Provider to open a game session for a player and receive a launch_url to embed.
  2. Wallet callbacks — Game Provider calls four endpoints on your backend to authorize the player, place bets, settle wins, and (for server-driven games) roll back voided rounds.

The same four callback endpoints serve every game in the catalog — classic and server-driven alike. Rollbacks for server-driven games reuse the existing /deposit endpoint with action: "ROLL_BACK", so no extra endpoint is required.

Key Features

  • One contract, all games — launch + 4 callbacks regardless of game type.
  • Secure by default — HMAC-SHA256 signature on every callback, per-operator keys.
  • Idempotent financial flow — safe to retry on transient failures; dedupe by provider_tx_id.
  • Millis money model — all amounts are integers in 1/1000ths of the main currency unit (e.g. 5440 = 5.44 USD).

Where to Start