Balance - Query Balance
Query the player's current available balance.
Request Parameters
Request Before Decryption
{
"cipherText": "asdqwcqwqe"
}
info
For encryption description, please refer to Operator API Implementation Guide
Request After Decryption
{
"action": "balance",
"uid": "gameTest1",
"currency": "PHP",
"brand": "VP"
}
| Parameter | Type | Required | Description |
|---|---|---|---|
| action | string | Yes | Fixed as "balance" |
| uid | string | Yes | Player Account |
| currency | string | Yes | Currency code |
| brand | string | Yes | Brand code, fixed as VP |
Response Format
info
The response is plaintext JSON, no encryption is 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 | Current available Balance |
| responseTime | string | Response time |
Response Status and Transaction Result
| Status | Query Status | Whether to trigger retry |
|---|---|---|
| 0000 | Success | No |
| 9999 | Failure | Yes |
| Timeout | Failure | Yes |
Important Notes
- Token validation: Token validity is checked for each query
- Real-time Balance: The returned Balance is the real-time available Balance
- Currency consistency: Ensure consistency with the currency set by VP
- Caching strategy: It is recommended for the Operator to cache Balance appropriately to reduce query frequency
- Concurrency control: May need to wait for lock release under high concurrency
- Retry strategy: Queries will continuously retry on timeout or failure, the mechanism is the same as BetNSettle
- Retry frequency: Retry 5 times, using an exponential back-off policy between each retry (1s, 3s, 5s, 7s, 9s)