Rollback transaction
DELETE/v1/rollbacks/:id
Reverse a withdrawal that must not remain. The platform calls this endpoint in two cases: a later step of bet placement failed, or the outcome of the withdrawal is unknown (no answer, a timeout, or a 5xx response).
The second case is the common one. The operator can receive a rollback for a withdrawal that it has not yet completed.
The {id} parameter is the value that the platform sent as id in the body of the original POST /v1/withdrawals request. It is not the id that the operator returns in the withdrawal response. The platform cannot use the returned value, because a rollback usually follows a lost or failed response.
If the withdrawal was applied, the operator must credit the player's balance back by the original withdrawal amount. If the operator has no withdrawal for that {id}, it must not credit the balance.
Rollbacks are never called for deposits — only for withdrawals that need compensation.
If the withdrawal was applied, the operator must credit the player's balance back by the original withdrawal amount. If the operator has no withdrawal for that {id}, it must not credit the balance.
Rollbacks are never called for deposits — only for withdrawals that need compensation.
Required headers:
X-Payload-Signature— HMAC-SHA256 hex signature of the request body
Request
Responses
- 200
- 403
- 404
- 409
- 5XX
Successful Response
HMAC signature verification failed.
Transaction ID not found — no matching withdrawal exists for the given {id}.
No matching withdrawal exists for the given {id}. Equivalent to 404; both are accepted.
Server error — the platform retries up to 3 times with exponential backoff before treating the request as failed.