Appendix
This page lists all possible error codes and their Descriptions in the Seamless Wallet API.
Status Code Overview
| Code | Response Message | Description | Related API |
|---|---|---|---|
| 0 | No error | Request Success | All API |
| 5 | Game is not found | Games not found or delisted | Open Game, Query Bet Logs, Query Bet Detail, Query Bet Replay |
| 6 | The username already exist | Player Account already exists | Create Player |
| 7 | Internal server error | Internal server error | All API |
| 8 | The User is not exist | Player does not exist | Open Game, Query Bet Detail |
| 10 | Agent code was not found or block | Agent not found or blocked | Get Access Token |
| 11 | Parameters error | Parameters error | All API |
| 14 | The BetId is not exist | Query Bet Logs does not exist | Query Bet Detail, Query Bet Replay |
| 19 | Invalid account | Invalid account | Open Game |
| 37 | The Function is not supported | This function is not supported | Query Bet Detail, Query Bet Replay |
| 38 | Query not allowed as the betId has expired | Transaction details/replay has exceeded query time | Query Bet Detail, Query Bet Replay |
| 77 | Too many request, please try again later | Too many requests | Query Bet Logs, Query Daily Report, Query player report |
| 78 | Operator card spinId was used | Item ID already used | Send Operator Card, Send Simple FreeSpin Operator Card |
| 81 | Branch config not found | Branch config not found | Open Game, Query Bet Logs |
| 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 verification |
| 84 | Encryption failed | Encryption failed | All APIs requiring encryption |
| 85 | Key config setting error | Key config setting error | All API |
| 86 | Game is restricted | Games rejected due to restriction | Open Game, Send Operator Card, Send Simple FreeSpin Operator Card, Send Simple FeatureGame Operator Card |
| 87 | Invalid item parameter value | Operator Card Parameter Combination Error | Send Operator Card, Send Simple FreeSpin Operator Card, Send Simple FeatureGame Operator Card |
| 88 | Only one item can be active at a time in the same game | Item cannot be Triggered simultaneously | Send Operator Card, Send Simple FreeSpin Operator Card, Send Simple FeatureGame Operator Card |
| 89 | The item has not been used yet, or the spinId does not exist | Item not yet used, cannot query result | Send Operator Card, Send Simple FreeSpin Operator Card, Send Simple FeatureGame Operator Card |
| 100 | The server is busy, please try again later | Service busy | Open Game |
Error Code Classification
Success Codes
| Code | Description |
|---|---|
| 0 | Request Success, no error |
Player Management Errors
| Code | Description | Possible Reason | Handling Suggestion |
|---|---|---|---|
| 6 | Player Account already exists | Create Player with an already registered Player Account | Use another Player Account |
| 8 | Player does not exist | Query or operate 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 | Retry later or Contact Customer Support Team |
Game Management Errors
| Code | Description | Possible Reason | Handling Suggestion |
|---|---|---|---|
| 5 | Games not found | Using invalid Game Code or Games already delisted | Confirm Game Code is correct |
| 82 | Site ID does not match | Site ID does not correspond to Player | Contact Customer Support Team, provide logUUID |
| 86 | Games rejected due to restriction | This Games cannot be opened due to currency, line, etc. | First confirm if the Game List document has a Description, Contact Customer Support Team, provide logUUID |
| 100 | Service busy, unable to generate new Games link | Service has reached its capacity, more Players are rejected to ensure quality | Retry later |
Query Bet Log Errors
| Code | Description | Possible Reason | Handling Suggestion |
|---|---|---|---|
| 14 | Query Bet Logs does not exist | Query non-existent Query Bet Logs or incorrect txTime | Confirm betId and txTime parameters are correct |
| 37 | This function is not supported | This query transaction supports this API function | Confirm whether the transaction is within the queryable range |
| 38 | Transaction details/replay has exceeded query time | Transaction occurred more than 30 days ago | Contact Customer Support Team |
Item-related errors
| Code | Description | Possible Reason | Handling Suggestion |
|---|---|---|---|
| 78 | Duplicate Item Transaction ID | Item ID already used | Change spinId parameter |
System Level Errors
| Code | Description | Possible Reason | Handling Suggestion |
|---|---|---|---|
| 7 | Internal server error | Server internal error | Contact Customer Support Team, provide logUUID |
| 10 | Agent error | Incorrect agentId or secret, or Agent is blocked | Check Authentication information, contact administrator to confirm Status |
| 11 | Parameters error | Request parameters missing, format error, or do not meet requirements | Check all Required parameters and formats |
| 77 | Too many requests | Too many requests sent in a short period | Reduce request frequency, retry later |
| 81 | Branch config not found | System configuration missing | Contact Customer Support Team |
| 83 | Signature verification failed | Signature calculation error or incorrect request header | Check signature generation logic and request header |
| 84 | Encryption failed | Encryption key error or incorrect encryption method | Check encryption configuration and implementation |
| 85 | Key config setting error | System unable to read valid Key information | Contact Customer Support Team |
| 87 | Operator Card Parameter Combination Error | Please check the corresponding API Operator Card sending rules | Reconfirm parameter rules or Contact Customer Support Team |
| 88 | Only one item can be active at a time in the same game | Player currently has another card active in the Games that has not been used yet | Please ask Player to re-enter the corresponding Games and use it before sending again |
| 89 | The item has not been used yet, or the spinId does not exist | Send Operator Card, Send Simple FreeSpin Operator Card, Send Simple FeatureGame Operator Card | Reconfirm if Item has been used or if Item has expired and does not exist |
Authentication Related Error Details
10 - Agent Error
Occurs in /v2/auth API, possible reasons:
- agentId does not exist: Used an unregistered Agent ID
- secret is incorrect: After decryption, the secret parameter does not match the agentId
- Agent is blocked: Agent ID has been disabled by the system
Handling Suggestion:
- Confirm agentId and secret are correct
- Contact Customer Support Team to check Agent Status
- Check if x-agentid request header matches 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
- 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 13-digit millisecond timestamp)
-
Nonce verification failed
- Used a duplicate nonce value (must be unique for each request)
-
Missing or incorrect request headers
- Missing required headers: x-agentid, x-timestamp, x-nonce, x-signature
- Request header values do not match the values used for actual signature calculation
Handling Suggestion:
- Refer to Get Access Token Overview to check 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
- Key error: Incorrect encryption key configuration
- Data format error: Incorrect data format before encryption
Handling Suggestion:
- Check if encryption implementation uses AES-256-GCM
- Confirm encryption key is correct
- Refer to the encryption example in Get Access Token Overview
Transaction Status Code
After the Operator API receives a request from the platform, 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 Balance |
| 2003 | Not cancelled, Bet Status: Confirmed (for Bet cancellation only) |
Games Type Mapping Table
| Code | Description |
|---|---|
| 1 | Slot |
Language
| Code | Description |
|---|---|
| en | English (Default Language, if VP does not support the corresponding Language, then it's 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 |
Currency
| 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) |
| MXN | Mexican Peso |
| MYR | Malaysian Ringgit |
| MYR1 | Malaysian Ringgit (displayed as 100:1 in Games) |
| NPR | Nepalese Rupee |
| NZD | New Zealand Dollar |
| PHP | Philippine Peso |
| PKR | Pakistani Rupee |
| THB | Thai Baht |
| THB1 | Thai Baht (displayed as 100:1 in Games) |
| USD | US Dollar |
| USDT | USDT |
| VND | Vietnamese Dong (1:1000) |
| VND1 | Vietnamese Dong (1:1) |
| ZAR | South African Rand |
Transaction Source Code
| Code | Description |
|---|---|
| 1 | Normal Bet |
| 2 | Task System |
| 3 | Prize |
| 4 | System Reward |
| 5 | Treasure Chest |
| 6 | Cash Ticket |
| 7 | Multi Quest |
| 8 | Card |
| 9 | Operator Card |