Balance - Query Balance
Query Player's current available Balance.
Request Parameters
Request Before Decryption
{
"cipherText": "asdqwcqwqe"
}
info
For Encryption Description, please refer to [Operator API Implementation Description](./overview.md#1-Security Requirements)
Decrypted Request
{
"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 |
Response Format
info
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 | Current available Balance |
| responseTime | string | Response time |
Response Status and Transaction Result
| Status | Query Status | Trigger Retry? |
|---|---|---|
| 0000 | Success | No |
| 9999 | Failed | Yes |
| Timeout | Failed | Yes |
Important Notes
- Token Validation: The validity of the Token is validated with 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 appropriately cache Balance to reduce query frequency
- Concurrency Control: Under high concurrency, it may be necessary to wait for locks to be released
- Query Frequency: Sent once every 10 seconds after the Player enters the game, until the Player leaves the game