Step 1: create a test key

You create keys yourself in the back office, under Settings, Integration. An account can have up to two test keys and up to five production keys, and the value of a key is shown once, so store it when you create it. A test key starts with wgc_test_ and can open demo games; a production key opens only games for money. Reading the catalog is done with a production key, because the catalog of a test key shows only the test game.

Step 2: play the test game

A test key opens one game, WGC Test Slot: a page with three bet sizes and a Spin button. Each spin makes two real calls to your Callback URL, a bet and then a result, marked with "test": true and the header X-WGC-Test: 1, so your handler can tell them from real play. No money moves, no commission is charged and no ledger entries are made. The test rows appear in the Test tab of the reports. Limits apply: two spins per second for a session and 2,000 spins a day for an account.

Step 3: check signatures and answers

Every wallet call is signed with HMAC-SHA256. Your handler must verify the signature on the raw body before parsing JSON, compare in constant time and reject a call whose timestamp is older than five minutes. It must answer within three seconds with a status from 200 to 299, and a refusal is { "ok": false, "error": "insufficient_funds" } with status 200. Test a wrong signature, a missing signature and a slow answer, and write down what your handler does in each case.

Step 4: test the failure path

A wallet integration is defined by how it fails. The test page has an option to lose the answer. The operation becomes unknown, and after about a minute a rollback with the reason unknown_outcome arrives at your Callback URL. Use it to confirm that your handler cancels a bet once, that a repeated rollback is harmless and that you answer a rollback of a bet you never booked with the current balance. WGC repeats a rollback that is not taken for up to 30 days, so your records of operations must be kept at least that long.

Step 5: run the integration check

In the back office, Integration check runs a real game of your own account through your own wallet. It shows a live log of the launch and of every getBalance, writeBet and rollback call, with the request and the answer, and a tab for signatures. Use it with a test player. If a call fails, the log shows what WGC sent and what your wallet returned.

Step 6: run the integration test

The integration test runs 14 checks of your wallet and gives a verdict for each: passed, works but a fix is advised, or must be fixed, with a hint on what to change. The checks cover balance reads, wrong and missing signatures, a bet that lowers the balance, a repeated transaction that must not be charged twice, a win, a bet above the balance, an unknown kind, two equal bets at the same moment, rollbacks and the time of every answer. Calls carry a test flag, and the test returns the operations your wallet accepted, so use it with a test player or a test wallet.

Step 7: use the public examples

Handlers for the Callback in Node.js, PHP and Python, a self-check script called wallet-check.mjs and a go-live checklist are public and need no sign-in. The self-check sends your endpoint signed requests the way WGC does, including a repeat of a bet and two identical bets at once, and prints the result item by item. It moves the balance of the test player by small amounts and puts it back, so run it only against a test environment.

Step 8: open demo sessions of real games

Pick games with the demo flag from the catalog, then open them with a test key in demo mode:

POST /v1/sessions   X-API-Key: wgc_test_…   Idempotency-Key: open-0001
{"publicId":"sweet-bonanza-1","playerId":"casino-side-player-42","currency":"USD","mode":"demo","language":"en"}
→ 200 { "ok": true, "requestId": "req_…", "data": { "url": "https://play.worldgamingconnect.com/play/Zk3p9xQ2vL8mTn4r", "sessionId": "cmgq3r8v40001l8xyz5k2abcd", "expiresAt": "2026-10-12T10:45:00.000Z" } }

Demo moves no money and is not refused for lack of balance. A game that does not support demo answers invalid_request. The launch also uses an Idempotency-Key: the same key and the same body return the same answer for 24 hours, so test a repeated open as its own case.

Step 9: a small real launch

Open a game for money with a production key, a test player and a small stake. A real launch needs money on your commercial account: the balance plus the credit limit must be above zero. In the reports, the Rounds tab in the main view should show the bet as accepted.

The go-live checklist

The public checklist has 14 points. In short:

  1. The API key is kept on your server only.
  2. The catalog is synced in full, then by changes, with a full sync at least daily.
  3. A game is opened from your server and the link is opened in the player's browser.
  4. The Callback URL is public and every answer comes within three seconds.
  5. The signature and the age of the timestamp are verified on the raw body.
  6. getBalance and writeBet answer as the contract says, and a refusal is a body with ok: false.
  7. writeBet is booked once per transactionId, and an unknown kind is refused.
  8. rollback is implemented and idempotent, or answers 404 or 405.
  9. Unknown fields are ignored.
  10. The self-check passes against your test endpoint.
  11. The integration test shows no failed check.
  12. A demo launch and then a small real launch work.
  13. The alerts bot is connected.
  14. Two-factor protection is on for every superuser.

Help while you test

Ask WGC, the assistant in the back office, answers from the documentation with sources. With the integration right enabled, its integration mode reads a limited snapshot of your own integration from the last seven days, without secrets or request bodies, and explains why your calls fail. Live support is in the back office too: quote the request id, the transaction id, the round id and the time in UTC. See demo and test mode, the integration steps, the seamless wallet contract, the back office and the Casino API overview.