Appendix
This page lists all possible status codes and their descriptions that may occur in the Seamless Wallet API, along with additional lists.
Status Code Overview
| Status Code | Request Message | Description | Related API |
|---|---|---|---|
| 0 | No error | Success | All APIs |
| 5 | Game is not found | The game does not exist or has been taken offline | Open Game, Get BetLog, Query Transaction Details, Get BetLog Reply |
| 6 | The username already exist | The username already exists | Create Member |
| 7 | Internal server error | Internal system error | All APIs |
| 8 | The User is not exist | The member does not exist | Open Game, Query Transaction Details |
| 10 | Agent code was not found or block | The agent does not exist or is blocked | Get Access Token |
| 11 | Parameters error | Parameter error | All APIs |
| 14 | The BetId is not exist | BetLog does not exist | Query Transaction Details, Get BetLog Reply |
| 19 | Invalid account | Invalid account | Open Game |
| 77 | Too many request, please try again later | Too many requests | Get BetLog, Get Daily Report, Query Member Report |
| 81 | Branch config not found | Branch configuration not found | Open Game, Get BetLog |
| 82 | Please check siteId is for this player | The siteId does not match the player | Open Game |
| 83 | Signature verification failed | Signature verification failed | All APIs |
| 84 | Encryption failed | Encryption failed | All APIs |
Status Code Categories
Success碼
| Code | Description |
|---|---|
| 0 | Request successful, no errors |
Member Management Errors
| Code | Description | Common Cause | Suggested Action |
|---|---|---|---|
| 6 | Username already exists | Attempting to create a member using an already registered username | Use a different username |
| 8 | The member does not exist | Querying or operating on a non-existent member | Verify the member ID or username, and call the Create Member API first |
| 19 | Invalid account | Incorrect account format or abnormal account status | Check the account format and status |
| 20 | Member wallet temporarily locked | The member wallet is temporarily locked due to certain reasons | Retry later or contact technical support |
Game Management Errors
| Code | Description | Common Cause | Suggested Action |
|---|---|---|---|
| 5 | Game not found | Using an invalid game code or the game has been taken offline | Verify that the game code is correct and confirm the game supports the current currency |
| 82 | siteId mismatch | The siteId does not correspond to the player | Verify that the siteId parameter is correct |
Get BetLog Errors
| Code | Description | Common Cause | Suggested Action |
|---|---|---|---|
| 14 | Get BetLog not found | Querying a non-existent BetLog or incorrect txTime | Verify that the betId and txTime parameters are correct |
System-Level Errors
| Code | Description | Common Cause | Suggested Action |
|---|---|---|---|
| 7 | Internal server error | Server-side internal error | Contact technical support and provide the logUUID |
| 10 | Agent error | Incorrect agentId or secret, or the agent is blocked | Verify authentication information and contact the administrator to confirm the agent status |
| 11 | Parameter error | Missing parameters, invalid format, or parameters not meeting requirements | Check all required parameters and their formats |
| 77 | Too many requests | Too many requests sent in a short period of time | Reduce request frequency and retry later |
| 81 | Branch configuration not found | Missing system configuration | Contact technical support |
| 83 | Signature verification failed | Incorrect signature calculation or invalid request headers | Check the signature generation logic and request headers |
| 84 | Encryption failed | Invalid encryption key or incorrect encryption method | Verify the encryption configuration and implementation |
Authentication Error Details
10 – Agent Error
Occurs in the /v2/auth API. Possible causes include:
- agentId does not exist: An unregistered agent ID is used
- Invalid secret: The decrypted
secretdoes not match theagentId - Agent is blocked: The agent account has been disabled by the system administrator
Handling Suggestion:
- Verify that the
agentIdandsecretare correct - Check that the
x-agentidrequest header matches theagentIdin the request body - Contact the administrator to confirm the agent status
83 – Signature Verification Failed
This is the most common authentication error and may be caused by the following:
-
Incorrect signature string composition order
- The correct order should be:
agentId + secret + timestamp + nonce + cipherText - Use SHA256 hashing (not HMAC-SHA256)
- The correct order should be:
-
Timestamp validation failure
- The time difference between the client and server exceeds the allowed range (typically ±1 minute)
- Incorrect timestamp format (must be a 13-digit millisecond timestamp)
-
Nonce validation failure
- A duplicate nonce value is used (each request must use a unique nonce)
-
Missing or incorrect request headers
- Required headers are missing:
x-agentid,x-timestamp,x-nonce,x-signature - Header values do not match those used during signature generation
- Required headers are missing:
Handling Suggestion:
- Refer to the Authentication Overview to verify the signature generation logic
- Ensure server time synchronization (use NTP)
- Generate a new nonce for every request
- Confirm that all required headers are correctly set
84 – Encryption Failed
Encryption / decryption related errors:
- Incorrect encryption algorithm: Must use AES-256-GCM
- Invalid encryption key: Encryption key configuration is incorrect
- Invalid data format: The data format before encryption is incorrect
Handling Suggestion:
- Verify that AES-256-GCM is used for encryption
- Confirm that the encryption key is correct
- Refer to the encryption examples in the Authentication Overview
Transaction status
The status field in the response returned by the operator API represents the transaction result after the platform request is received.
| Status | Description |
|---|---|
| 0000 | Success |
| 9999 | Failed |
| 1006 | Invalid session |
| 2000 | TransferId not found |
| 2001 | TransferId has already operation |
| 2002 | Balance not enough |
| 2003 | Can not Rollback, transaction need to be settled (Rollback only) |
Game Type Mapping
| Code | Description |
|---|---|
| 1 | Slot Game |
Languages
| Code | Description |
|---|---|
| en | English (default language; used if the game provider does not support the requested 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 (RMB) |
| 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 (in-game display 100:1) |
| NPR | Nepalese Rupee |
| PHP | Philippine Peso |
| THB | Thai Baht |
| USD | US Dollar |
| USDT | Tether (USDT) |
| VND | Vietnamese Dong (1:1000) |
| VND1 | Vietnamese Dong (1:1) |
| ZAR | South African Rand |
betSourceId (Source of the transaction)
| Code | Description |
|---|---|
| 1 | General spin |
| 2 | Task system |
| 3 | Prizes |
| 4 | System reward |
| 5 | Treasure Chest |
| 6 | Cash Ticket |
| 7 | Multi Quest |
| 8 | Card |
| 9 | Operator Card |