Skip to content
VAS HUB
Getting started

Games integration

Put VAS HUB games in your casino in two parts: a launch link that opens the game in an iframe, and a small wallet API on your side that our game servers call to read balances and move money.

Players stay yours: their accounts, balances and transaction history live in your platform. Our game servers run the rounds, prove they're fair, and ask your wallet for every balance change, signed with a secret only you and we know. If you already integrate providers that use signed auth / withdraw / deposit wallet calls, most of your code carries over.

How it works

  1. 1
    Player→Your casino

    Opens a game. You create a launch token and open the game URL in an iframe.

  2. 2
    Our game server→Your wallet

    /auth with the token. You answer with the player's ID and balance.

  3. 3
    Our game server→Your wallet

    /withdraw when the player bets: you take the stake.

  4. 4
    Our game server→Your wallet

    /deposit when the bet wins (the full payout) or its stake goes back (rollback). Lost bets get no call.

At a glance

PartIn short
LaunchAn iframe URL with your operator name and a launch token: Game launch.
Wallet APIYour HTTPS base URL. We call /auth, /info, /withdraw, /deposit: Wallet API.
FormatHTTPS POST with a JSON body; you reply { code, message, data }.
SecurityX-Client-ID, X-Client-TS and X-Client-Signature (HMAC-SHA256): Securing requests.
MoneyBalances stay with you. Every money call is idempotent by provider_tx_id.
FairnessEvery round is provably fair: players can check any result inside the game.

Games

AvioniXavionix · 9 gamesAviator HUBaviatorhub · 1 gameHotCrashhotcrash · 1 gameFairCrashfaircrash · 1 game

Where to go next

Game launchBuild the iframe URL and launch tokens.Wallet APIThe four calls we make to your platform.Securing requestsVerify our HMAC-SHA256 signature.Go-live checklistWhat we exchange, and what to test.