Skip to main content
The cancel callback is sent when a player’s bet fails to complete — due to network issues, timeouts, or system errors. Your server must refund the full bet amount back to the player’s balance to ensure account accuracy. This operation is idempotent — if your wallet receives more than one request with the same transactionId, you must register the refund only once. No need to add “Cancel” at the end of your callback URL; you can get the request body “command” to identify which callback is coming.
  • URL: Your configured Callback URL(ex: https://mycallback.com/cb)
  • Method: POST
  • Headers: X-Request-Signature, Content-Type, Accept

​
Request parameters

​
string
required
Always "cancel" for this callback type.
​
long
required
Unique reference of this cancel transaction created in our system. Use this to enforce idempotency.
​
string
required
Unique identifier of the player from your system.
​
long
required
Unique reference of the game round.
​
number
required
Unique identifier of the game provider in our system.
​
number
required
Unique game id of the game in our system.
​
number
required
Unix timestamp of the request.

​
Response fields

Your server must respond with HTTP 200 and a JSON body containing the following fields:
​
number
required
The player’s updated balance after the refund is applied.
​
string
required
Result of the operation. Must be "OK" on success. See the status codes table below for all possible values.

​
Status codes

Your response must be returned within 4 seconds. If the request times out or returns an error, we will automatically retry the request up to 2 more times.
Use referenceId to locate the original bet in your database. If the bet was never recorded (e.g., your system never received it), you can safely return OK with the player’s current balance — there is nothing to refund.

​
Examples