PREDICTOR

Platform Documents · 04 / 04

Technical Integration

Predictor is a hosted game: your platform opens one launch URL with a session token, and the game drives your wallet through a small, idempotent callback API. Nothing to install, nothing to host.

Hosted — zero infrastructure on your side Seamless wallet, 4 operations Sandbox before go-live

01 · Architecture

One URL in, four calls out

Your casino
Launch
The player opens Predictor from your lobby; your platform redirects to the game-launch URL with a session token.
→
Predictor
Session
Predictor validates the token against your platform API, opens a game session, and loads the game UI for the player.
→
During play
Wallet calls
Bets and settlements arrive as signed server-to-server calls to your wallet API, one transaction id each.

The game runs full-window or inside your shell via redirect — the launch URL's return and deposit parameters bring the player back to you.

02 · Game launch

The launch URL

Your platform id, the game code and the exact host are assigned during onboarding. The launch call is a plain GET redirect:

GET https://<api-host>/api/rgs/platforms/{platformId}/GameLaunch ?gamecode={gameCode} &token={session-token} &playerid={playerId} &currency={USD|EUR|…} &lang={en|am|ru|tr|es} &device={desktop|mobile} &playmode={real|fun} &returnUrl={url} &depositUrl={url}
ParameterMeaning
gamecodePredictor's game identifier, fixed per environment and provided at onboarding.
tokenYour platform's session token for the player. Predictor exchanges it with your platform API to authorize the session — the token itself is never stored client-side.
playeridYour player id; the same id used in wallet calls and free-spin grants.
currencyThe player's wallet currency; stakes display converted at the live rate.
langUI and question language: en, am, ru, tr or es.
deviceLayout hint; the UI is fully responsive either way.
playmodereal for money play; fun for demo.
returnUrl / depositUrlWhere the game sends the player on exit, and on an insufficient-balance prompt.

03 · Wallet callbacks

Four operations, all idempotent

Predictor calls your wallet with signed server-to-server requests. Every call carries a unique transaction id; retries reuse the same id, so processing is safely idempotent on your side.

OperationWhenAmount
BetPlayer joins a round− stake
Win settlementRound settles with the player on the winning side+ payout (net; rake reported alongside)
Loss settlementRound settles against the player0 (closes the round; rake reported)
Refund void / rollbackRound voids, or an in-doubt bet is rolled back+ stake

Timeout handling, the in-doubt ledger and reconciliation guarantees are specified in Financial Logic & Settlement, section 05. Native adapters exist per platform wallet dialect; new wallet APIs are integrated as plugins on Predictor's side — no change required in your casino.

04 · Bonus & localization

Free spins, languages, currency

CapabilitySummary
Free spinsOne grant endpoint for your bonus engine; rounds consumed automatically on matching joins; wins pay real money. Full spec: Free Spins.
LanguagesUI and the full question bank in English, Armenian, Russian, Turkish, Spanish — selected by the lang launch parameter. New locales are added through the translation pipeline without a client release.
CurrencyMulti-currency with live-rate conversion; bets and settlements always reconcile in the player's wallet currency.
Demo modeplaymode=fun launches the full game against a demo balance — useful for your QA and for player onboarding.

05 · Back office

Operator controls

AreaWhat you manage
Question bank1,000+ questions with per-language text; activate or retire questions; per-answer vote statistics.
Game configsStake tiers, player limits, round timings, tournament schedules.
Free spinsManual grants and grant inspection, alongside the API.
MonitoringGame history and transaction ledger per player and per round, matching your wallet's transaction ids line by line.

06 · Onboarding

From keys to go-live

StepWhat happens
1 · ExchangeWe exchange signing keys and assign your platform id, game code and API hosts.
2 · NetworkIP allowlists are set up in both directions where your policy requires them.
3 · WalletYou provide wallet endpoint URLs; we map them to the matching adapter.
4 · SandboxLaunch, play, settle and reconcile on the staging environment with test players — including free-spin and refund cases.
5 · Go-liveProduction keys armed, launch URL flipped to production, first real rounds verified together.
Typical effort on your side: one launch-URL integration plus your standard seamless-wallet handlers. Platforms with an existing RGS-style integration usually complete the sandbox phase in days, not weeks.