betwin callback is sent when a player’s bet and its outcome complete in a single atomic operation. Your implementation must deduct betAmount from the player’s balance and add winAmount in one transaction — both operations succeed or neither does. This endpoint is used in game types where the bet and outcome are determined simultaneously, avoiding the need for a separate withdraw followed by a deposit.
- URL: Your configured Callback URL
- Method: POST
- Headers:
X-Request-Signature,Content-Type,Accept
Request parameters
Always
"betwin" for this callback type.Unique reference of the transaction created in iGamingAce. Use this to enforce idempotency.
Unique identifier of the player from your system.
Unique reference of the game round.
Unique identifier of the game provider in iGamingAce.
Unique game id of the game in iGamingAce.
Player currency code per ISO-4217 (e.g.,
EUR, USD).Bet amount to deduct from the player’s balance.
0: no bonus, else the bonus id related
Unix timestamp of the request.
Response fields
Your server must respond with HTTP 200 and a JSON body containing the following fields:The player’s updated balance after the bet is deducted.
Result of the operation. Must be
"OK" on success. See the status codes table below for all possible values.Status codes
| Status code | Description |
|---|---|
OK | Request successful |
ERR_NOT_AUTHENTICATED | The player is not authenticated |
ERR_NOT_ENOUGH_MONEY | The player’s account has insufficient funds |
ERR_INTEGRITY_CHECK_FAILED | Message integrity check failed |
ERR_UNKNOWN | Internal server error |
