Start with the owner of the balance
In the callback wallet model used by WGC, the casino platform holds the player wallet. WGC calls your platform for a balance or for the result of a gaming transaction. WGC does not store player wallets; the only exception is a demo client created by WGC staff, who uses a test wallet.
The player reference identifies a player in the casino's own system, as a string of 1 to 64 printable ASCII characters. It is not the commercial account used to access WGC. Agree on this boundary first, so that both teams know which system is authoritative when a request fails or an amount is disputed.
Follow a transaction through the systems
A typical integration needs a balance check and a way to record a bet and its result. The WGC callback contract names three commands: getBalance to read the balance, writeBet to record a bet with its win in one request, and rollback to cancel a bet. When a studio sends the bet and the result separately, WGC joins them into one round with a round id, and both calls travel inside it.
Keep the player, currency, game, round and transaction references together in your records. A launch link is only the entry point to a game; it does not confirm that a balance check or a settlement has completed.
Treat a retry as the same transaction
A network timeout can happen after an operation was accepted but before the answer reached the caller. Repeating that operation blindly can debit a player twice. An idempotent handler recognizes the same transaction id and returns the recorded result instead of applying the amounts again. With WGC this is a condition of the integration: writeBet is recorded once per transaction id, and a repeated call returns the same balance.
Timeouts have rules too. WGC waits three seconds for your answer, and an answer counts only with a 2xx status. If there is no answer in time, the bet is refused to the studio, the operation becomes unknown and a rollback follows. The rollback is repeated on a schedule for up to 30 days, so keep your records of operations at least that long.
Include concurrent duplicates, delayed answers and a retry after a timeout in your acceptance tests. Retries of opening a session are a separate contract, and you should not assume the wallet works the same way.
Make currency and amounts explicit
A player wallet may use a different currency from the commercial account of the operator. Every operation has to identify its currency and follow the agreed precision rules. An amount is a number, or a string with a dot, and a single operation can be at most one million USD at the rate of the round.
The commercial balance with WGC is kept in USD, and it is not the player's spendable balance. Do not derive one from the other. Do not assume either that a currency shown in a back office is supported by every game: a game that does not open in a currency is marked in the catalog. Confirm the intended combinations before testing.
Test failures as well as successful play
Prepare checks for the cases that matter most:
- Insufficient funds. A refusal is written in the body, for example with an insufficient funds error and status 200.
- An unknown player or an unsupported currency.
- An invalid signature. Every call is signed with HMAC-SHA256; check the signature on the raw body, compare in constant time and reject calls older than five minutes.
- A delayed answer and a duplicate delivery.
Keep the transaction reference and a support request id in your own records, and compare the accepted transactions on both sides, not only the final balances.
A dry run can validate the shape of a message, but it cannot prove that a real studio and your wallet settle correctly together. To rehearse, a test key opens a test game that makes real calls to your Callback URL without money, and an option to lose the answer checks your rollback. In the back office, the integration check shows a live log of every call, and the integration test runs 14 checks of your wallet.
Confirm the readiness of each connection
WGC provides a callback contract and a tester for preparing this work, and the wallet Callback works. Handler examples for Node.js, PHP and Python and a go-live checklist of 14 points are public. Readiness of each connection is still confirmed per project: discuss the supported flow, the failure policy and the acceptance criteria with the integration team. Your manager provides access details directly.
For the full contract, read the seamless wallet page, and for the steps around it the integration page, demo and test mode and the Casino API overview.