If an error occurs while processing a request, the API must return a response with HTTP Status Code: 400 Bad Request
Name
Type
Description
error_code
string
Error code describing the specific issue.
Show Possible Error Codes
Error Code
Description
INVALID_PLAYER_ID
The provided player ID is invalid or does not exist in the system.
INVALID_SESSION
The provided session ID is invalid or does not exist in the system.
INVALID_PLAYER_CURRENCY
The player’s currency is invalid or mismatched.
INVALID_GAME
The specified game UUID is invalid or does not exist.
INVALID_TRANSACTION
The transaction for rollback is invalid or cannot be processed.
TECHNICAL_ERROR
An unexpected error occurred.
NOT_AUTHORIZED
The request is not authorized due to invalid X-Auth-Token header.
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 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.