Appendix
This page lists all possible error codes and their Descriptions in the Seamless Wallet API.
Status Code Overview
| Code | Response Message | Description | Related APIs |
|---|---|---|---|
| 0 | No error | Request Successful | All APIs |
| 5 | Game is not found | Game does not exist or has been removed | Open Game, Query Bet Logs & Reports, Query Bet Details, Query Bet Replay |
| 6 | The username already exist | Player Account already exists | Create Player |
| 7 | Internal server error | Internal system error | All APIs |
| 8 | The User is not exist | Player does not exist | Open Game, Query Bet Details |
| 10 | Agent code was not found or block | Agent does not exist or is blocked | Get Access Token |
| 11 | Parameters error | Parameters error | All APIs |
| 14 | The BetId is not exist | Query Bet Logs & Reports does not exist | Query Bet Details, Query Bet Replay |
| 19 | Invalid account | Invalid account | Open Game |
| 77 | Too many request, please try again later | Too many requests | Query Bet Logs & Reports, Query Daily Report, Query player report |
| 81 | Branch config not found | Branch configuration not found | Open Game, Query Bet Logs & Reports |
| 82 | Please check Site ID is for this player | Site ID does not match Player | Open Game |
| 83 | Signature verification failed | Signature verification failed | All APIs requiring authentication |
| 84 | Encryption failed | Encryption failed | All APIs requiring encryption |
Error Code Categories
Success Codes
| Code | Description |
|---|---|
| 0 | Request Successful, no errors |
Player Management Errors
| Code | Description | Possible Cause | Handling Suggestion |
|---|---|---|---|
| 6 | Player Account already exists | Attempted to Create Player with an already registered Player Account | Use another Player Account |
| 8 | Player does not exist | Querying or operating on a non-existent Player | Confirm Player ID or Player Account is correct, call Create Player API first |
| 19 | Invalid Player Account | Player Account format error or abnormal Status | Check Player Account format and Status |
| 20 | Player Wallet temporarily locked | Player Wallet temporarily locked for some reason | Try again later or Contact Customer Support Team |
Game Management Errors
| Code | Description | Possible Cause | Handling Suggestion |
|---|---|---|---|
| 5 | Game does not exist | Using an invalid game code or the game has been removed | Confirm the game code is correct, check if the game supports the current currency |
| 82 | Site ID Mismatch | Site ID does not correspond to Player | Contact Customer Support Team, provide logUUID |
Query Bet Logs & Reports Errors
| Code | Description | Possible Cause | Handling Suggestion |
|---|---|---|---|
| 14 | Query Bet Logs & Reports does not exist | Querying a non-existent Query Bet Logs & Reports or incorrect txTime | Confirm betId and txTime parameters are correct |
System-level Errors
| Code | Description | Possible Cause | Handling Suggestion |
|---|---|---|---|
| 7 | Internal system error | Internal server error | Contact Customer Support Team, provide logUUID |
| 10 | Agent error | Incorrect Agent ID or secret, or Agent is blocked | Check Authentication information, contact administrator to confirm Status |
| 11 | Parameters error | Missing request parameters, incorrect format, or non-compliance with requirements | Check all required parameters and formats |
| 77 | Too many requests | Too many requests sent in a short period | Reduce request frequency, try again later |
| 81 | Branch configuration not found | Missing system configuration | Contact Customer Support Team |
| 83 | Signature verification failed | Incorrect signature calculation or incorrect request header | Check signature generation logic and request header |
| 84 | Encryption failed | Incorrect encryption key or incorrect encryption method | Check encryption configuration and implementation |
Authentication Related Error Details
10 - Agent Error
Occurs in the /v2/auth API, possible causes:
- Agent ID does not exist: Used an unregistered Agent ID
- Incorrect secret: The secret parameter after decryption does not match the Agent ID
- Agent blocked: Agent ID has been deactivated by the system
Handling Suggestion:`
- Confirm Agent ID and secret are correct
- Contact Customer Support Team to check Agent Status
- Check if x-agentid request header is consistent with agentId in the body
83 - Signature Verification Failed
This is the most common Authentication error, which may be caused by the following reasons:
-
Incorrect signature string combination order
- The correct order should be: agentId + secret + timestamp + nonce + cipherText
- Use SHA256 (not HMAC-SHA256) for hashing
-
Timestamp verification failed
- Operator and server time difference exceeds the allowed range (usually ±1 minute)
- Incorrect timestamp format (should be a 13-digit millisecond timestamp)
-
Nonce verification failed
- Used a duplicate nonce value (each request must be unique)
-
Missing or incorrect request headers
- Missing required headers: x-agentid, x-timestamp, x-nonce, x-signature
- Header values are inconsistent with the values used for actual signature calculation
Handling Suggestion:`
- Refer to Get Access Token Overview to check the signature generation logic
- Ensure server time synchronization (using NTP)
- Generate a new nonce for each request
- Confirm all request headers are correctly set
84 - Encryption Failed
Encryption/decryption related errors:
- Incorrect encryption method: Must use AES-256-GCM
- Incorrect key: Incorrect encryption key configuration
- Incorrect data format: Incorrect data format before encryption
Handling Suggestion:`
- Check if the encryption implementation uses AES-256-GCM
- Confirm the encryption key is correct
- Refer to the encryption example in Get Access Token Overview
Transaction Status Code
After the Operator API receives a platform request, the status Field in the response format represents the transaction result.
| Status | Description |
|---|---|
| 0000 | Success |
| 9999 | Failed |
| 1006 | Invalid session |
| 2000 | Transaction ID not found |
| 2001 | Transaction ID already exists |
| 2002 | Insufficient current Balance |
| 2003 | Not cancelled, Bet Status: Established (for Bet cancellation only) |
Game Type Mapping Table
| Code | Description |
|---|---|
| 1 | Slots |
Language
| Code | Description |
|---|---|
| en | English (Default Language, if VP does not support the corresponding Language, then the Default Language) |
| zh-Hans | Simplified Chinese |
| th | Thai |
| my | Burmese |
| id | Indonesian |
| vi | Vietnamese |
| jp | Japanese |
| pt | Portuguese |
| ko | Korean |
| tl | Tagalog |
| hi | Hindi |
| ms | Malay |
| bn | Bengali |
| es | Spanish |
Currencies
| Code | Description |
|---|---|
| AUD | Australian Dollar |
| BDT | Bangladeshi Taka |
| BRL | Brazilian Real |
| CAD | Canadian Dollar |
| CNY | Chinese Yuan |
| EGP | Egyptian Pound |
| EUR | Euro |
| GBP | British Pound |
| HKD | Hong Kong Dollar |
| IDR | Indonesian Rupiah (1:1000) |
| IDR1 | Indonesian Rupiah (1:1) |
| INR | Indian Rupee |
| JPY | Japanese Yen |
| KHR | Cambodian Riel |
| KRW | Korean Won (1:1) |
| KRW1 | Korean Won (1:1000) |
| LAK | Lao Kip (1:1000) |
| LAK1 | Lao Kip (1:1) |
| LKR | Sri Lankan Rupee |
| MMK | Myanmar Kyat (1:1000) |
| MMK1 | Myanmar Kyat (1:1) |
| MYR | Malaysian Ringgit |
| MYR1 | Malaysian Ringgit (displayed as 100:1 in-game) |
| NPR | Nepalese Rupee |
| PHP | Philippine Peso |
| THB | Thai Baht |
| USD | US Dollar |
| USDT | Tether |
| VND | Vietnamese Dong (1:1000) |
| VND1 | Vietnamese Dong (1:1) |
| ZAR | South African Rand |
Transaction Source Code
| Code | Description |
|---|---|
| 1 | General Bet |
| 2 | Mission System |
| 3 | Red Packet Draw |
| 4 | System Reward |
| 5 | Open Treasure Chest |
| 6 | Cash Voucher |
| 7 | Multiplier Reward |
| 8 | Card |
| 9 | Operator Card |