Skip to main content

Appendix

This page lists all possible status codes and their descriptions that may occur in the Transfer Wallet API, along with additional lists.

Status Code Overview

Status CodeResponse MessageDescriptionRelated API
0No errorSuccessAll API
2The balance is not enoughInsufficient balanceTransaction, All Cash Out
3The transaction already existThe transaction already existsTransaction, All Cash Out
4The transaction doesn't existThe transaction does not existQuery Transaction Detail
5Game is not foundThe game does not exist or has been taken offlineOpen Game, Get BetLog, Query Transaction Details, Get BetLog Reply
6The username already existThe username already existsCreate Member
7Internal server errorInternal server errorAll API
8The User is not existThe member does not existGet Balance, Transaction, All Cash Out, Open Game, Query Transaction Details
10Agent code was not found or blockAgent does not exist or is blockedGet Access Token
11Parameters errorParameter errorAll API
14The BetId is not existBetLog does not existQuery Transaction Details, Get BetLog Reply
19Invalid accountInvalid accountGet Balance, Transaction, All Cash Out, Open Game
20Member wallet is temporarily lockedMember wallet temporarily lockedTransaction, All Cash Out
35The transaction is pendingTransaction is processingTransaction, All Cash Out, Query Transaction Detail
77Too many request, please try again laterToo many requestsGet BetLog, Get Daily Report, Query Member Report
81Branch config not foundBranch configuration not foundGet Balance, Transaction, All Cash Out, Open Game, Get BetLog, Kick Out Player, Get Member Sessions
82Please check siteId is for this playersiteId does not match the playerOpen Game
83Signature verification failedSignature verification failedAll API
84Encryption failedEncryption failedAll API

Status Code Categories

Success

CodeDescription
0Request successful, no errors

Member Management Errors

CodeDescriptionCommon CauseSuggested Action
6Username already existsAttempting to create a member using an already registered usernameUse a different username
8The member does not existQuerying or operating on a non-existent memberVerify the member ID or username, and call the Create Member API first
19Invalid accountIncorrect account format or abnormal account statusCheck the account format and status
20Member wallet temporarily lockedThe member wallet is temporarily locked due to certain reasonsRetry later or contact technical support
CodeDescriptionCommon CauseSuggested Action
2Insufficient balanceInsufficient balance during withdrawal or bettingCheck the member balance and ensure it is sufficient
3Transaction already existsUsing a duplicate transaction ID (transId)Use a new unique transaction ID
4Transaction does not existQuerying a non-existent transaction recordVerify that the transaction ID is correct
35Transaction is processingThe transaction is still being processed and not yet completedWait or query the transaction status

Game Management Errors

CodeDescriptionCommon CauseSuggested Action
5Game not foundUsing an invalid game code or the game has been taken offlineVerify that the game code is correct and confirm the game supports the current currency
82siteId mismatchThe siteId does not correspond to the playerVerify that the siteId parameter is correct

Get BetLog Errors

CodeDescriptionCommon CauseSuggested Action
14Get BetLog not foundQuerying a non-existent BetLog or incorrect txTimeVerify that the betId and txTime parameters are correct

System-Level Errors

CodeDescriptionCommon CauseSuggested Action
7Internal server errorServer-side internal errorContact technical support and provide the logUUID
10Agent errorIncorrect agentId or secret, or the agent is blockedVerify authentication information and contact the administrator to confirm the agent status
11Parameter errorMissing parameters, invalid format, or parameters not meeting requirementsCheck all required parameters and their formats
77Too many requestsToo many requests sent in a short period of timeReduce request frequency and retry later
81Branch configuration not foundMissing system configurationContact technical support
83Signature verification failedIncorrect signature calculation or invalid request headersCheck the signature generation logic and request headers
84Encryption failedInvalid encryption key or incorrect encryption methodVerify the encryption configuration and implementation

Authentication Error Details

10 – Agent Error

Occurs in the /v2/auth API. Possible causes include:

  1. agentId does not exist: An unregistered agent ID is used
  2. Invalid secret: The decrypted secret does not match the agentId
  3. Agent is blocked: The agent account has been disabled by the system administrator

Handling Suggestion:

  • Verify that the agentId and secret are correct
  • Check that the x-agentid request header matches the agentId in 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:

  1. Incorrect signature string composition order

    • The correct order should be: agentId + secret + timestamp + nonce + cipherText
    • Use SHA256 hashing (not HMAC-SHA256)
  2. 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)
  3. Nonce validation failure

    • A duplicate nonce value is used (each request must use a unique nonce)
  4. 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

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:

  1. Incorrect encryption algorithm: Must use AES-256-GCM
  2. Invalid encryption key: Encryption key configuration is incorrect
  3. 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

Game Type Mapping

CodeDescription
1Slot Game

Languages

CodeDescription
enEnglish (default language; used if the game provider does not support the requested language)
zh-HansSimplified Chinese
thThai
myBurmese
idIndonesian
viVietnamese
jpJapanese
ptPortuguese
koKorean
tlTagalog
hiHindi
msMalay
bnBengali
esSpanish

Currency

CodeDescription
AUDAustralian Dollar
BDTBangladeshi Taka
BRLBrazilian Real
CADCanadian Dollar
CNYChinese Yuan (RMB)
EGPEgyptian Pound
EUREuro
GBPBritish Pound
HKDHong Kong Dollar
IDRIndonesian Rupiah (1:1000)
IDR1Indonesian Rupiah (1:1)
INRIndian Rupee
JPYJapanese Yen
KHRCambodian Riel
KRWKorean Won (1:1)
KRW1Korean Won (1:1000)
LAKLao Kip (1:1000)
LAK1Lao Kip (1:1)
LKRSri Lankan Rupee
MMKMyanmar Kyat (1:1000)
MMK1Myanmar Kyat (1:1)
MYRMalaysian Ringgit
MYR1Malaysian Ringgit (in-game display 100:1)
NPRNepalese Rupee
PHPPhilippine Peso
THBThai Baht
USDUS Dollar
USDTTether (USDT)
VNDVietnamese Dong (1:1000)
VND1Vietnamese Dong (1:1)
ZARSouth African Rand

betSourceId (Source of the transaction)

CodeDescription
1General spin
2Task system
3Prizes
4System reward
5Treasure Chest
6Cash Ticket
7Multi Quest
8Card
9Operator Card