Skip to main content
Rollback
POST /credit/rollback
This operation is idempotent.

Headers


Request Parameters


Response Parameters


Error

If an error occurs while processing a request, the API must return a response with HTTP Status Code: 400 Bad Request

Responsibility of the wallet platform
The wallet platform must verify that the incoming playerId, roundId, transactionId and amount correspond to the latest wager placed in the game round. It must also ensure that no debit has been issued for the game round. If any of these assertions fail, the rollback request must be refused. If promotionExternalId is present, the wallet platform must validate that it belongs to the active promotion session for the player and use it as the promo wallet context. A rollback happens if something goes wrong during action processing and the system needs to restore the previous state. However, there are two conditions:
  • There haven’t been any winnings in this round yet.
  • A jackpot hasn’t been won during the round.
If the specified transaction is not found or has already been rolled back, the wallet platform must return an INVALID_TRANSACTION error code. This error response will be interpreted as a successful rollback, ensuring that the rollback will not be sent repeatedly. For all other errors, the RGS platform will attempt to send the rollback again.