Skip to main content
GitSlotPark calls your /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

POST {your_callback_base_url}/RollbackTransaction
Replace {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.
agentID
string
required
Your Partner ID assigned by GitSlotPark.
userID
string
required
The player’s ID in your system.
transactionID
string
required
The transactionID of the original transaction to reverse. This matches the transactionID that was sent in the original Withdraw, Deposit, or BetWin request.
sign
string
required
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

{
  "agentID": "Partner01",
  "userID": "player_12345",
  "transactionID": "txn_abc001",
  "sign": "Q7R8S9T0..."
}

Response fields

Your server must respond with Content-Type: application/json and HTTP 200.
result
integer
required
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.
balance
number
The player’s balance after the rollback has been applied. Required when result is 0.

Example success response

{
  "result": 0,
  "balance": 100.00
}

Example: transaction already rolled back

{
  "result": 9,
  "message": "Transaction already rolled back"
}

Example: transaction not found

{
  "result": 8,
  "message": "Transaction not found"
}

Result codes

CodeMeaning
0Success
1General error
3Invalid sign
8Transaction not found
9Already rolled back

Notes

If you receive a rollback for a transactionID that your system never recorded, return result 8 (transaction not found). Do not treat an unknown transactionID as a general error.
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.
Store the transactionID of every processed Withdraw, Deposit, and BetWin along with the balance delta. This makes it straightforward to reverse the exact amount when a rollback arrives.