Seamless
Seamless Wallet API
Functions
Action 14: Deposit

Action 14: Deposit

Function Description

  • JDB will call the API when a player leaves the game for returning balance, with sum of bet / sum of win.
  • If the request is received and has already been successfully processed, please return 0000.
  • If call the API failed, JDB will retry every minutes for 12 hours until status 0000.
seamless wallet deposit flow chart

Request Parameter

ParameterFormatDescription
actionInteger14
tsLongCurrent system time
transferIdLongTransfer ID
uidString(50)Player ID
currencyString(10)Please refer to: Currency Code
amountDoubleAmount that should be transferred to player balance.
It will always be positive.
refTransferIdsArray of LongWhich withdrawal will be deposited, can be referred to Action 13's transferId
totalBetDoubleThe total bet that occurred between transfer in and out
totalWinDoubleThe total win that occurred between transfer in and out
gTypeIntegerGame types
See Game Provider
mTypeIntegerMachine Type
systemSessionIdString(150)System Session ID, will be different in each login when using action 21 get game launch url.

Game Type supports range: FISH(7)

This is not included by default, contact JDB service if needed.

More data fields are vary by gType, listed in the following table:

Request Example

{
  "action": 14,
  "ts": 1664521584150,
  "transferId": 251917,
  "uid": "testpl",
  "currency": "RM",
  "amount": 5285.0,
  "refTransferIds": [
    252925
  ],
  "totalBet": 300.0,
  "totalWin": 300.0,
  "gType": 0,
  "mType": 8001
}

Response Parameter

ParameterFormatDescription
statusString(4)Success: 0000
It would be considered as failure if the status is not 0000, and trigger resend mechanism.
err_textString(255)Error message

Response Example

{
  "status": "0000",
  "err_text": ""
}