01 / Build the connection
Connect the wallet
Follow money movement between your wallet and the game services.
Wildvolt asks your wallet to move funds while a game runs. Your handlers authenticate each request, apply the transaction once and return the resulting player balance.
Follow the transaction
| Moment | Callback to your wallet | Action |
|---|---|---|
| The player places a bet | POST /withdraw | Deduct the stake |
| The bet settles | POST /deposit | Apply the result; a loss can have an amount of zero |
| A withdrawal is reversed | POST /rollback | Reverse the previous withdrawal |
| The game needs a current balance | POST /player-balance | Return the current player balance |
The API directory includes these contracts and the batch-credit request. Use each endpoint's field definitions for units, transaction identifiers and supported transaction types.
Return an explicit outcome
Successful responses include a balance and a Unix-millisecond timestamp:
{"type": "SUCCESS", "balance": 1234.56, "timestamp": 1712401234567}Business errors use the error envelope and should include the balance when available:
{"type": "ERROR", "code": "INSUFFICIENT_BALANCE", "balance": 1234.56}These wallet response envelopes use HTTP 200; the type field carries the transaction outcome. Check each endpoint for its supported error codes. Returned balances are in currency units, while request amounts use the units defined in the request contract.
Build for retries
Verify the signature before processing. Store the transaction outcome so a repeated request can return it without another balance change. Review callback reliability before testing, then use reconciliation to investigate records that need follow-up.