BetNSettle - Bet and Settle

Execute bet and settlement operations, this is the core API of the game.

Request Parameters

Request Before Decryption

{
  "cipherText": "G0ZMDELeJwx+7JcIfIFOLJjkSzANPu6krGM2uw==..." 
}

info

For encryption Description, please refer to Operator API Implementation Guide

Request After Decryption

{
  "action": "betNSettle",
  "uid": "testaccount01",
  "roundId": "testroundId001",
  "transferId": "testroundId001",
  "betId": "7634846433511800000",
  "brand": "VP",
  "currency": "THB",
  "gameCode": "VP_230001_1",
  "betTime": "2025-11-17T16:01:13.155Z",
  "txTime": "2025-11-17T16:01:13.155Z",
  "gameInfo": "{\"featureBuy\":0,\"spinID\":[\"7634278403511200000\",\"7634278403512200000\",\"7634278403513700000\"],\"cardType\":1,\"deviceType\":0}",
  "actualBetAmt": 0,
  "validBetAmt": 0,
  "winAmt": 1.3,
  "jackpotWin": 0,
  "jackpotContribute": 0,
  "betSourceId": 1,
  "featureMode": 1
}

Parameter	Type	Required	Description
action	string	Yes	Fixed as "betNSettle"
uid	string	Yes	Player Account
roundId	string	Yes	Games round number
transferId	string	Yes	Transaction Unique Identifier (scheduled for removal)
betId	string	Yes	Bet ID, unique for VP
brand	string	Yes	Brand code, fixed as VP
currency	string	Yes	Currency code
gameCode	string	Yes	Game Code
betTime	string	Yes	Bet time
txTime	string	Yes	Settlement time
gameInfo	string	Yes	JSON string of Games related information
actualBetAmt	number	Yes	Actual Bet Amount
validBetAmt	number	Yes	Valid bet amount
winAmt	number	Yes	Win amount, can be 0 or positive
jackpotWin	number	Yes	Jackpot win amount
jackpotContribute	number	Yes	Jackpot contribution amount, default is 0
betSourceId	number	Yes	Transaction source code
featureMode	number	Yes	Feature Mode

Response Format

info

The response is plaintext JSON, no encryption required.

Success Response

{
  "status": "0000",
  "errText": "",
  "balance": 12345.67,
  "responseTime": "2024-12-11T01:23:38.271Z"
}

Field	Type	Description
status	string	Status Code, see Status Code Description below
errText	string	Error message, empty string on Success
balance	number	Player Balance after transaction
responseTime	string	Response time

Response Status and Transaction Result

Status	Bet Status Determination	Trigger Retry	Bet Status
0000	Success	No	Established
9999	Failed	Yes	Canceled
1006	Failed	No	Canceled
2001	Success	No	Established
2002	Failed	No	Canceled
Timeout	Failed	Yes	Canceled

Important Notes

Atomic operation: BetNSettle is an atomic operation, it will either be all Success or all failed
Balance calculation: afterBalance = beforeBalance - actualBetAmt + winAmt
betId uniqueness: The betId for each Games round is unique
Retry strategy: If no Success is received, it will continuously retry
- Retry frequency: Retries 5 times, each retry uses an exponential backoff policy (1s, 3s, 5s, 7s, 9s)
  - If all above retries fail, normal transactions enter the rollback phase
  - If all above retries fail, Item, Operator Card transactions enter the retryBet phase
Parameter adjustment: transferId will be removed and replaced by betId
Jackpot parameters: jackpotWin is a reserved Field, current value is fixed at 0; jackpotContribute is a reserved Field, current default is 0

Request Parameters​

Request Before Decryption​

Request After Decryption​

Response Format​

Success Response​

Response Status and Transaction Result​

Important Notes​