POST /Deposit — Credit a Player's Balance After a Win

Called by GitSlotPark when a player wins. Credit the win amount to the player’s wallet and return the updated balance. Handle duplicates with result code 11.

GitSlotPark calls your /Deposit endpoint when a player wins. Your server must add the specified amount to the player’s balance and return the new balance. A deposit always succeeds as long as the player exists — there is no concept of insufficient funds when crediting a win. You implement this endpoint on your own server.

Endpoint

POST {your_callback_base_url}/Deposit

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.

amount · string · required

The amount to credit, expressed as a string with exactly 2 decimal places (for example, "25.00").

transactionID · string · required

A unique identifier for this transaction, generated by GitSlotPark. Store this value so you can detect duplicate requests and handle any subsequent rollback.

roundID · string · required

The game round identifier this win belongs to.

sign · string · required

HMAC-SHA-256 signature computed over agentID + userID + amount + transactionID + roundID (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",
  "amount": "25.00",
  "transactionID": "txn_win002",
  "roundID": "round_xyz001",
  "sign": "I9J0K1L2..."
}

Response fields

Your server must respond with Content-Type: application/json and HTTP 200.

result · integer · required

Result code. Use 0 for success or 11 for a duplicate transaction. See result codes below.

balance · number

The player’s balance after the credit. Required when result is 0 or 11.

transactionID · string

Your internal transaction reference. Optional — include it if you want to correlate GitSlotPark transactions with your own records.

Example success response

{
  "result": 0,
  "balance": 112.50,
  "transactionID": "your-internal-ref-002"
}

Example duplicate transaction response

{
  "result": 11,
  "balance": 112.50
}

Result codes

Code	Meaning
0	Success
1	General error
3	Invalid sign
5	User not found
11	Duplicate transaction

Notes

Callbacks are idempotent. If you receive a Deposit request with a transactionID you have already processed successfully, return result 11 along with the player’s current balance. Do not credit the amount a second time.

Check for an existing record of the transactionID before applying any balance change. This protects against network retries delivering the same request more than once.