Skip to Content

Error Codes

Error code (code) indicates the processing result of API requests.

Success Response

Response CodeDescription
0Interface response successful

Important Note

code being 0 only means interface call succeeded, not transaction success. Transaction final status needs to be determined by transactionStatus.

Security Restriction Errors (S prefix)

Error CodeDescriptionSolution
S01Invalid IP addressCheck if merchant has configured IP whitelist and add calling server IP to whitelist
S02Request timestamp deviation from server time too largeSync client system time, ensure time difference within allowed range (±10 minutes)
S03Signature verification failedCheck signature algorithm, key, and parameter order, confirm parameters involved in signature have not been modified
S04Interface call frequency exceededReduce call frequency, follow platform frequency limit rules
S05Data decryption failedCheck code encryption logic or check if key settings are correct
S06Insufficient permissionsContact administrator to apply for permissions or check if permissions are correct
S07TMK key does not exist or key expiredRe-obtain TMK
S08Working key does not exist or key expiredRe-obtain working key
S09Login session expired or not logged inLog in again
S10Request authentication failedCheck key settings or authentication algorithm calculation is correct
S11Duplicate requestUse different X-Request-Id to initiate request again, or wait 10 minutes before retrying

Client Errors (C prefix)

Error CodeDescriptionSolution
C01Request parameter missingEnsure all required parameters are provided
C02Request JSON format errorCheck JSON structure, bracket matching, and data type validity
C03Merchant does not exist or is disabledCheck if merchant ID is correct and confirm merchant status
C04Store does not exist or is disabledCheck if store ID is correct and confirm store status
C05Device does not existCheck if device SN is correct and confirm the merchant or store bound to the device is correct
C06Duplicate request serial numberEnsure uniqueness of merchant request number, avoid duplicate submission
C07Duplicate merchant order numberEnsure uniqueness of merchant order number to avoid duplicate submission
C08Transaction locked (prevent concurrent operations)Wait for current operation to complete before initiating new request, recommend business layer locking control
C09Order unpaidCheck if order number is correct and confirm order status
C10Order already paidConfirm order status through order query interface, no need to repeat operation
C11Order closedCreate a new order and initiate the request again
C12Order does not existCheck if order number is correct and order’s merchant
C13Pricing currency not supportedCheck merchant-supported pricing currencies and ensure request currency is in the allowed list
C14Transaction amount exceeds allowed rangeCheck platform’s amount limit rules for this merchant/payment method, adjust request amount
C15Refund amount exceeds original order amount or refundable balanceVerify original order amount and refunded amount, ensure total refund amount does not exceed refundable limit
C16Request parameter is emptyEnsure non-empty parameters are set with correct values
C17Request parameter format error or non-compliant with API specificationEnsure all values are filled according to documentation specifications
C18Requested API endpoint does not existCheck API endpoint URL
C19Unsupported HTTP methodCheck API HTTP method
C20Device does not existComplete device activation or bind the device on the platform
C21Security configuration missing or not foundComplete configuration
C22Merchant is not authorized to access this applicationCheck configuration and request parameters
C23Terminal does not match merchantCheck the merchant associated with the terminal
C24Original transaction status not allowedCheck transaction status
C25Transaction type not allowedCheck transaction type
C26There are transactions currently being processedRetry later
C27Terminal transaction concurrencyRetry later
C28No transactions in the current batch are eligible for settlementPlease call Batch Query first to check pending settlement transactions before requesting Batch Close

Merchant Configuration Errors (M prefix)

Error CodeDescriptionSolution
M01Interface call permission insufficient or not activatedApply for corresponding interface permission or renew
M02Application does not exist or unavailableCheck if appId is correct and confirm application status on open platform
M03Application and merchant binding relationship does not matchConfirm the application has been correctly authorized to the merchant and use the correct pairing information
M04Merchant has not activated this payment product or payment parameters not configured or configured incorrectlyConfirm merchant has activated corresponding payment product, complete payment parameter configuration
M05Failed to push message to terminalConfigure Taplink connection mode of terminal to Cloud

System Errors (E prefix)

Error CodeDescriptionSolution
E01System busy, please try again laterCall order query interface to confirm transaction status, if unpaid order can retry
E02Network timeout or errorCall order query interface to confirm transaction status, if unpaid order can retry
E03Unknown exceptionCall order query interface to confirm transaction status, if unpaid order can retry

Error Handling Recommendations

  • When encountering E01, E02, E03 errors, should first call order query interface to confirm transaction status
  • If order is unpaid, can retry; if multiple attempts still fail, contact technical support
  • When encountering C08, C26, C27 and other concurrency-related errors, recommend retrying later
Last updated on