/RollbackTransaction endpoint to cancel and reverse a previously completed Withdraw, Deposit, or BetWin transaction. Your server must restore the player’s balance to what it was before the original transaction was applied. If the transactionID was never processed on your end, return result 8. You implement this endpoint on your own server.
Endpoint
{your_callback_base_url} with the HTTPS base URL you registered with GitSlotPark (for example, https://casino.com/WalletService).
Your endpoint must be served over HTTPS and must always return HTTP 200. Use the
result field in the JSON body to communicate success or failure.Request parameters
GitSlotPark sends the following JSON body to your endpoint.Your Partner ID assigned by GitSlotPark.
The player’s ID in your system.
The
transactionID of the original transaction to reverse. This matches the transactionID that was sent in the original Withdraw, Deposit, or BetWin request.HMAC-SHA-256 signature computed over
agentID + userID + transactionID (concatenated in that order) using your secret key. Expressed as a 64-character uppercase hex string.Example request from GitSlotPark
Response fields
Your server must respond withContent-Type: application/json and HTTP 200.
Result code. Use
0 for success, 8 if the transaction was not found, or 9 if the transaction was already rolled back. See result codes below.The player’s balance after the rollback has been applied. Required when
result is 0.Example success response
Example: transaction already rolled back
Example: transaction not found
Result codes
| Code | Meaning |
|---|---|
0 | Success |
1 | General error |
3 | Invalid sign |
8 | Transaction not found |
9 | Already rolled back |
Notes
If you receive the same rollback request more than once for a transaction you have already reversed, return result
9 (already rolled back). Do not reverse the balance a second time.