Error Codes
Error Codes
Every response carries an error_code. error_code == 0 means success; any
other value indicates a failure. Determine success from error_code, not from
the HTTP status code alone.
| error_code | Meaning | Description | Suggested handling |
|---|---|---|---|
0 | Success | — | — |
90000 | Invalid parameters | Missing required field, invalid email, missing or inconsistent allowlist fields, invoice missing payer / due_date, etc. | Fix the request parameters and retry. |
90001 | Unauthorized | Authentication failed or merchant identity is missing. | Check your API Key and signature. |
90111 | Invalid receiving chain | receiving_network is not supported, the receiving address is not bound to the chain, or an allowlisted chain is invalid. | Correct the receiving chain / allowlist. |
90112 | Wallet not found | receiving_address does not belong to your merchant account. | Use a receiving address configured under your account. |
90120 | Invalid receiving token | The token (symbol + contract address) is not supported, or an allowlisted token is invalid. | Correct the receiving token / allowlist. |
80000 – 80099 | System error | The service is temporarily unavailable or hit an internal error. | Retry later; if it persists, contact support with the trace. |
note
80000–80099are transient or internal server-side errors. Clients do not need to distinguish specific values — treat them as retryable system errors.msgis for troubleshooting only and is not meant to be shown to end users. When reporting an issue, include thetracevalue.