Build Your GitSlotPark Seamless Wallet Callback Service

Build the HTTPS endpoints GitSlotPark calls to check balances and post transactions during gameplay. Covers all five callbacks with sign formulas and examples.

GitSlotPark calls your server via HTTPS POST for every wallet operation that occurs during gameplay. Your callback service must be accessible at the base URL you registered with GitSlotPark — for example, https://casino.com/WalletService. Each of the five endpoints is appended to that base URL as a path (for example, https://casino.com/WalletService/GetBalance).

Your callback service must always return HTTP 200. Any other HTTP status code is treated as a server error and GitSlotPark will retry the request. Use the result field in the JSON response body to communicate errors such as insufficient funds or missing transactions.

Callbacks are idempotent. If you receive a request with a transactionID you have already processed, return a success response without re-processing the transaction. Return result code 11 if you need to signal that the transaction is a duplicate.

GetBalance

GitSlotPark calls /GetBalance to read a player’s current wallet balance before and after game events.

Endpoint: POST /GetBalance

Sign formula: agentID + userID

Request

{
  "agentID": "Partner01",
  "userID": "player_456",
  "sign": "<hmac-sha256>"
}

Withdraw

GitSlotPark calls /Withdraw to debit the player’s balance when a bet is placed. You must check that the player has sufficient funds before applying the debit.

Endpoint: POST /Withdraw

Sign formula: agentID + userID + amount (2 decimal places) + transactionID + roundID

Request

{
  "agentID": "Partner01",
  "userID": "player_456",
  "amount": "10.00",
  "transactionID": "txn_abc123",
  "roundID": "round_789",
  "sign": "<hmac-sha256>"
}

Format amount with exactly two decimal places when computing the sign — for example, 10.00 not 10. The concatenated string must match exactly.

Deposit

GitSlotPark calls /Deposit to credit the player’s balance when a win is awarded.

Endpoint: POST /Deposit

Sign formula: agentID + userID + amount + transactionID + roundID

Request

{
  "agentID": "Partner01",
  "userID": "player_456",
  "amount": "22.30",
  "transactionID": "txn_def456",
  "roundID": "round_789",
  "sign": "<hmac-sha256>"
}

BetWin

GitSlotPark calls /BetWin for certain game types that resolve a bet and a win in a single atomic event. The bet amount is debited and the win amount is credited in one request.

Endpoint: POST /BetWin

Sign formula: agentID + userID + betAmount + winAmount + transactionID + roundID

Request

{
  "agentID": "Partner01",
  "userID": "player_456",
  "betAmount": "10.00",
  "winAmount": "15.00",
  "transactionID": "txn_ghi789",
  "roundID": "round_101",
  "sign": "<hmac-sha256>"
}

RollbackTransaction

GitSlotPark calls /RollbackTransaction to cancel and reverse a previously processed transaction — for example, if a game round is voided or a network error caused an incomplete round.

Endpoint: POST /RollbackTransaction

Sign formula: agentID + userID + transactionID

Request

{
  "agentID": "Partner01",
  "userID": "player_456",
  "transactionID": "txn_abc123",
  "sign": "<hmac-sha256>"
}

If you receive a rollback request for a transactionID that was already rolled back, return result code 9 rather than an error. This allows GitSlotPark to safely retry rollback requests without causing double-reversals.

Result codes

The following result codes are relevant to callback responses:

Code	Meaning
0	Success
1	General error
2	Wrong input
3	Invalid sign
6	Insufficient funds
8	Transaction not found (ref not found)
9	Already rolled back
11	Duplicate transaction