Reverses a previously credited amount from the player’s balance.
POST /credit/rollback
| Name | Type | Description |
|---|---|---|
| X-Auth-Token | string | Custom authentication header in the format X-Auth-Token: your_token_here. This token is required to authorize API requests. |
| Name | Type | Description |
|---|---|---|
| playerId | string | Unique identifier of the player. |
| amount | decimal | Amount to rollback. |
| gameUuid | string | Unique identifier of the game. |
| sessionId | string | Unique identifier of the player session. |
| roundId | string | Unique identifier of the game round. |
| transactionId | string | Unique identifier of the game round transaction. |
| transactionTimestamp | integer | Timestamp of the transaction in milliseconds. |
| currency | string | Currency code of the player. |
| Name | Type | Description |
|---|---|---|
| balance | decimal | The updated balance of the player after the rollback. |
HTTP Status Code: 400 Bad Request| Name | Type | Description |
|---|---|---|
| error_code | string | Error code describing the specific issue. |
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.