Error Codes

MixPay uses two code namespaces:

• top-level API response code reports whether an API request was accepted;
• payments_result.data.failureCode reports why an accepted payment order reached failed.

Do not treat them as interchangeable. failureCode is returned as a string, while the top-level API code is normally a number.

Global error response

Global error response, example:

{
  "code": 10008,
  "success": false,
  "message": "The system is under maintenance and cannot be paid temporarily. If you have any questions, please contact customer service.",
  "data": [],
  "timestampMs": 1635734004508
}

API response codes

Code	Message
-1	Server error, please try again later.
2000	Insufficient permissions.
404	The payment link you visited does not exist.
1017	Parameter error.
1429	Your request frequency is too high, please try again later.
10000	Mixin authorization expired.
10001	User does not exist.
10002	The currency does not exist or does not supported exchanging.
10003	Does not support this quote asset.
10004	The price is too low.
10005	The price is too high.
10006	The transfer amount exceeds 1000 USDT.
10007	We can not provide service to you.
10008	Payments are suspended temporarily due to system maintenance. Please contact customer service if you have any questions.
10009	Withdrawals are suspended temporarily due to system maintenance. If you have any questions, please contact customer service.
10010	Insufficient balance of assets.
10011	Parameter error
10020	The trace or merchant order has already completed, or is already attached to an order that cannot be recreated.
10032	For the payment-cancellation endpoint, the payment cannot be cancelled in its current state; the endpoint returns HTTP 409. Other endpoints can reuse this API code with endpoint-specific meaning.
10033	The same user can be added only 3 times in 24 hours.
10034	Price exception, please try again later.
10035	The multisigId does not belong to the token.
10036	The robot does not exist.
10037	This is not a robot.
10039	This is not your robot and cannot be bound.
10040	The robot is already bound.
10041	The threshold cannot exceed the number of payees.
10042	More than 20 multi-signature group bindings.
10043	More than 20 robot bindings.
10044	Please set the name of this multi-signature group first.
10061	The callback URL must use HTTPS.
10062	The requested order does not exist.
10063	The requested expiration is below the accepted minimum.
10064	The requested expiration exceeds the accepted maximum.
10065	The trace has expired or is already in a terminal failed state and cannot create another payment.
10084	The trace is not available for the requested operation.
10131	The requested callback event is invalid.

The API response message is intended for diagnostics and can change. Branch on the endpoint and code together.

Payment-result failure codes

For current order-level failures, payments_result returns one of these values when data.status === "failed":

failureCode	Meaning
40000	No valid payment was received before the payment deadline, or a fully recognized payment did not obtain the required confirmations before the server-side confirmation deadline.
40020	A wrong payment asset was received and the payment cannot be corrected.
40024	The payment deadline passed while the recognized amount was insufficient.
40025	The payment could not be completed because market-volatility or settlement-loss checks failed.
40027	The payment could not be completed because the requested settlement asset was restricted or unavailable under strict settlement requirements.
40032	The payment was cancelled.
10095	The payment was rejected during risk, compliance, or manual review.

Historical and refund-derived records can expose additional compatibility values. See the complete Failure codes section, including its unknown-code fallback guidance.

Cancellation codes

For payment cancellation, 10032 and 40032 describe different stages. 10032 is the immediate API error returned when cancellation is not allowed. 40032 is the payment-result failure code after a cancellation is accepted and the order reaches failed.

A failed result does not mean that a refund has completed. Refund and settlement processing have separate lifecycles.

Reason for refund

The following codes can appear in legacy refund flows. New payment integrations should use the payment-result table above for terminal order handling.

Code	Message
10002	This currency does not exist or is not supported for exchange.
10003	The Quote currency in Memo is abnormal and not available.
10011	Parameter error.
10021	The payee in Memo does not support the settlement currency in Memo.
10052	Settlement currency is not available in Memo.
10053	The current payment currency cannot be used as quote currency.
10054	The current payment currency is not available.
10055	The settlement currency in Memo has been removed.
10057	The current payment currency has been removed.
10056	The current quote currency has been removed.
10066	The payee in Memo does not support the settlement currency in Memo.
10067	The payee in Memo does not support payment in the current currency.
10068	The payee in Memo does not support using the current payment currency as the quote currency.
10069	The current payment currency does not meet the minimum limit.
10070	The current payment currency does not meet the maximum limit.
10071	The current payment currency does not meet the minimum limit.
10072	The current payment currency does not meet the maximum limit.
10074	The payeeId is not available.
40000	Payment deadline or confirmation deadline exceeded.
40001	The payee does not exist in the url.
40002	The asset in url does not exist or does not support exchanging.
40003	The transfer amount exceeds 1000 USDT.
40005	The minimum number of decimal places in url exceeds the limit.
40006	The minimum number of integer digits in url exceeds the limit.
40008	Insufficient balance of assets.
40009	Server error.
40011	The system is temporarily out of service.
40012	Withdrawal methods with memo do not exist.
40013	Withdrawal assets with memo do not exist.
40014	The withdrawal address with memo does not exist.
40015	You currently have an incomplete withdrawal, please complete it first and then try again.
40016	The withdrawal amount is too large.
40017	The Withdrawal amount is too small.
40018	Transfer amount is too small.
40019	Transfer amount is too large.
40020	Wrong payment asset.
40021	Double payment.
40022	TraceId does not exist.
40023	Payee does not exist in Memo.
40024	Payment deadline passed with an insufficient amount.
40025	Too much market volatility.
40027	Your payment fails due to transaction restrictions on settlement assets.