Error codes

Stablecoin Account API Publisher Disclaimer When the Stablecoin Account API returns an error, search for its type, code, or message, then narrow the result by the endpoint you called. The table shows the first recommended action; expand a row only when you need more context.

How to use this page

Save the error details

Save the endpoint, HTTP status, complete response body, and request time. Do not include API keys, access tokens, PANs, or other sensitive card data in logs or support requests.

Search the response

Paste the complete type, code, or message into “Search response.” If more than one result remains, filter by operation name, operationId, HTTP method, or path.

Follow the recommended action

Confirm the Endpoint column, then follow the primary action. Expand “View details” for the reason, retry guidance, and conditions for contacting UQPAY.

Error response format

This product uses both typed error responses and compatibility formats without a type field. The same code can represent more than one message or condition, so do not identify an error from a single field alone.

Error code table

The type, code, and message columns preserve the values returned by the API. Endpoint entries include the operation name, operationId, HTTP method, and path. Dynamic messages are represented by a confirmed stable pattern or description.

Before contacting UQPAY, prepare the HTTP method and path, x-response-id, request time, and complete error response. Remove API keys, access tokens, PANs, and other sensitive information. Each row lists only the additional information needed for that error.

HTTP / Type	Code / Message	Endpoint	Recommended action
400 Legacy flat	`403` `Login expired`	All public endpoints	Refresh authentication Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The authentication details are missing, expired, or invalid. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`403` `banking account not found`	All public endpoints	Verify the resource Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The resource is missing, unavailable, or does not belong to the current account. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`403` `account not active / not tradable`	All public endpoints	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`403` `api trading not enabled for this account`	All public endpoints	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `IP not allowed`	All public endpoints	Refresh authentication Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The authentication details are missing, expired, or invalid. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`1084` `invalid x-on-behalf-of account id`	All public endpoints	Correct the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`1084` `banking account not found`	All public endpoints	Verify the resource Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The resource is missing, unavailable, or does not belong to the current account. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`1084` `account not active / not tradable`	All public endpoints	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`1084` `not authorized to act on behalf of the target account`	All public endpoints	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`1084` `Select user failed`	All public endpoints	Retry later Retry only after the condition identified by the message has been resolved. View details Why this happened: The request could not be completed and changing request parameters alone may not resolve it. Retry: Retry only when the returned condition has been resolved and the operation permits it. When to contact UQPAY: Contact UQPAY if the same error persists after the recommended action and limited retries. Also provide: x-response-id, request time, HTTP method and path, complete error response.
400 Legacy flat	`403` `Forbidden`	All public endpoints	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `query balances failed`	List Assets `GET /v1/ramp/asset` operationId: `list-assets`	Check the balance Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The available balance or currency does not meet the operation requirements. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `balance not found`	Retrieve Asset `GET /v1/ramp/asset/{balance_currency}` operationId: `retrieve-asset`	Verify the resource Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The resource is missing, unavailable, or does not belong to the current account. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `query transactions failed`	List Asset Transactions `GET /v1/ramp/asset/transactions` operationId: `list-asset-transactions`	Retry later Retry only after the condition identified by the message has been resolved. View details Why this happened: The request could not be completed and changing request parameters alone may not resolve it. Retry: Retry only when the returned condition has been resolved and the operation permits it. When to contact UQPAY: Contact UQPAY if the same error persists after the recommended action and limited retries. Also provide: x-response-id, request time, HTTP method and path, complete error response.
400 `invalid_request_error`	`invalid_parameter` `parameter is invalid`	Create Transfer `POST /v1/ramp/transfer` operationId: `create-transfer` Retrieve Transfer `GET /v1/ramp/transfer/{order_id}` operationId: `retrieve-transfer`	Correct the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry after correcting the request or resource state.
400 `transfer_error`	`create_transfer_failed` `create transfer failed`	Create Transfer `POST /v1/ramp/transfer` operationId: `create-transfer`	Retry later Retry only after the condition identified by the message has been resolved. View details Why this happened: The request could not be completed and changing request parameters alone may not resolve it. Retry: Retry only when the returned condition has been resolved and the operation permits it. When to contact UQPAY: Contact UQPAY if the same error persists after the recommended action and limited retries. Also provide: x-response-id, request time, HTTP method and path, complete error response.
400 `not_found`	`not_found` `Error to Geting Account Product Data`	Create Transfer `POST /v1/ramp/transfer` operationId: `create-transfer`	Retry later Retry only after the condition identified by the message has been resolved. View details Why this happened: The request could not be completed and changing request parameters alone may not resolve it. Retry: Retry only when the returned condition has been resolved and the operation permits it. When to contact UQPAY: Contact UQPAY if the same error persists after the recommended action and limited retries. Also provide: x-response-id, request time, HTTP method and path, complete error response.
400 `account_error`	`account_error` `Account not found or deactivated`	Create Transfer `POST /v1/ramp/transfer` operationId: `create-transfer`	Verify the resource Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The resource is missing, unavailable, or does not belong to the current account. Retry: Retry after correcting the request or resource state.
400 `account_error`	`account_error` `Account not active`	Create Transfer `POST /v1/ramp/transfer` operationId: `create-transfer`	Retry later Retry only after the condition identified by the message has been resolved. View details Why this happened: The request could not be completed and changing request parameters alone may not resolve it. Retry: Retry only when the returned condition has been resolved and the operation permits it. When to contact UQPAY: Contact UQPAY if the same error persists after the recommended action and limited retries. Also provide: x-response-id, request time, HTTP method and path, complete error response.
400 `not_found`	`not_found` `Error to Geting Balance Data`	Create Transfer `POST /v1/ramp/transfer` operationId: `create-transfer`	Check the balance Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The available balance or currency does not meet the operation requirements. Retry: Retry after correcting the request or resource state.
400 `transfer_error`	`insufficient_balance` `Insufficient account balance`	Create Transfer `POST /v1/ramp/transfer` operationId: `create-transfer`	Check the balance Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The available balance or currency does not meet the operation requirements. Retry: Retry after correcting the request or resource state.
400 `api_error`	`risk_verify_failed` `Risk verification failed`	Create Transfer `POST /v1/ramp/transfer` operationId: `create-transfer`	Retry later Retry only after the condition identified by the message has been resolved. View details Why this happened: The request could not be completed and changing request parameters alone may not resolve it. Retry: Retry only when the returned condition has been resolved and the operation permits it. When to contact UQPAY: Contact UQPAY if the same error persists after the recommended action and limited retries. Also provide: x-response-id, request time, HTTP method and path, complete error response.
400 `not_found`	`not_found` `Error to Geting Transfer Data`	Retrieve Transfer `GET /v1/ramp/transfer/{order_id}` operationId: `retrieve-transfer`	Retry later Retry only after the condition identified by the message has been resolved. View details Why this happened: The request could not be completed and changing request parameters alone may not resolve it. Retry: Retry only when the returned condition has been resolved and the operation permits it. When to contact UQPAY: Contact UQPAY if the same error persists after the recommended action and limited retries. Also provide: x-response-id, request time, HTTP method and path, complete error response.
400 Legacy flat	`400` `invalid request`	Applies to 6 public endpoints	Correct the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `invalid amount`	Applies to 4 public endpoints	Correct the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `fixed_currency must equal sell_currency or buy_currency`	Create Quote `POST /v1/ramp/conversion/quote` operationId: `create-quote`	Correct the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `currency not supported`	Create Conversion `POST /v1/ramp/conversion` operationId: `create-conversion` Create Quote `POST /v1/ramp/conversion/quote` operationId: `create-quote` Create Withdraw `POST /v1/ramp/withdraw` operationId: `create-withdraw`	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `invalid quote request (check currencies/amount)`	Create Quote `POST /v1/ramp/conversion/quote` operationId: `create-quote`	Correct the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `no exchange rate available for this currency pair`	Create Quote `POST /v1/ramp/conversion/quote` operationId: `create-quote`	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `account not active`	Create Conversion `POST /v1/ramp/conversion` operationId: `create-conversion` Create Quote `POST /v1/ramp/conversion/quote` operationId: `create-quote` Create Withdraw `POST /v1/ramp/withdraw` operationId: `create-withdraw`	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `exchange not enabled for account`	Create Conversion `POST /v1/ramp/conversion` operationId: `create-conversion` Create Quote `POST /v1/ramp/conversion/quote` operationId: `create-quote`	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `exchange limit not configured for account`	Create Quote `POST /v1/ramp/conversion/quote` operationId: `create-quote`	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `amount below minimum`	Create Quote `POST /v1/ramp/conversion/quote` operationId: `create-quote` Create Withdraw `POST /v1/ramp/withdraw` operationId: `create-withdraw`	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `amount above maximum`	Create Quote `POST /v1/ramp/conversion/quote` operationId: `create-quote` Create Withdraw `POST /v1/ramp/withdraw` operationId: `create-withdraw`	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `amount exceeds daily limit`	Create Quote `POST /v1/ramp/conversion/quote` operationId: `create-quote` Create Withdraw `POST /v1/ramp/withdraw` operationId: `create-withdraw`	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `amount exceeds monthly limit`	Create Quote `POST /v1/ramp/conversion/quote` operationId: `create-quote` Create Withdraw `POST /v1/ramp/withdraw` operationId: `create-withdraw`	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `exchange create failed`	Create Conversion `POST /v1/ramp/conversion` operationId: `create-conversion` Create Quote `POST /v1/ramp/conversion/quote` operationId: `create-quote`	Retry later Retry only after the condition identified by the message has been resolved. View details Why this happened: The request could not be completed and changing request parameters alone may not resolve it. Retry: Retry only when the returned condition has been resolved and the operation permits it. When to contact UQPAY: Contact UQPAY if the same error persists after the recommended action and limited retries. Also provide: x-response-id, request time, HTTP method and path, complete error response.
400 Legacy flat	`400` `insufficient balance`	Create Conversion `POST /v1/ramp/conversion` operationId: `create-conversion` Create Withdraw `POST /v1/ramp/withdraw` operationId: `create-withdraw`	Check the balance Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The available balance or currency does not meet the operation requirements. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `quote invalid or mismatched`	Create Conversion `POST /v1/ramp/conversion` operationId: `create-conversion`	Correct the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `quote already used`	Create Conversion `POST /v1/ramp/conversion` operationId: `create-conversion`	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `market price moved beyond tolerance since quote; please re-quote`	Create Conversion `POST /v1/ramp/conversion` operationId: `create-conversion`	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `query orders failed`	List Conversions `GET /v1/ramp/conversion` operationId: `list-conversions`	Retry later Retry only after the condition identified by the message has been resolved. View details Why this happened: The request could not be completed and changing request parameters alone may not resolve it. Retry: Retry only when the returned condition has been resolved and the operation permits it. When to contact UQPAY: Contact UQPAY if the same error persists after the recommended action and limited retries. Also provide: x-response-id, request time, HTTP method and path, complete error response.
400 Legacy flat	`400` `order not found`	Retrieve Conversion `GET /v1/ramp/conversion/{order_id}` operationId: `retrieve-conversion`	Verify the resource Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The resource is missing, unavailable, or does not belong to the current account. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `query deposits failed`	List Deposits `GET /v1/ramp/deposit` operationId: `list-deposits`	Retry later Retry only after the condition identified by the message has been resolved. View details Why this happened: The request could not be completed and changing request parameters alone may not resolve it. Retry: Retry only when the returned condition has been resolved and the operation permits it. When to contact UQPAY: Contact UQPAY if the same error persists after the recommended action and limited retries. Also provide: x-response-id, request time, HTTP method and path, complete error response.
400 Legacy flat	`400` `deposit not found`	Retrieve Deposit `GET /v1/ramp/deposit/{order_id}` operationId: `retrieve-deposit`	Verify the resource Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The resource is missing, unavailable, or does not belong to the current account. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `asset and network are required`	Deposit Wallet Address `GET /v1/ramp/deposit/address` operationId: `deposit-wallet-address`	Correct the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `deposit address not found`	Deposit Wallet Address `GET /v1/ramp/deposit/address` operationId: `deposit-wallet-address`	Verify the resource Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The resource is missing, unavailable, or does not belong to the current account. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `query deposit address failed`	List Deposit Addresses `GET /v1/ramp/deposit/addresses` operationId: `list-deposit-addresses`	Retry later Retry only after the condition identified by the message has been resolved. View details Why this happened: The request could not be completed and changing request parameters alone may not resolve it. Retry: Retry only when the returned condition has been resolved and the operation permits it. When to contact UQPAY: Contact UQPAY if the same error persists after the recommended action and limited retries. Also provide: x-response-id, request time, HTTP method and path, complete error response.
400 Legacy flat	`400` `address_id or withdraw_address is required`	Create Withdraw `POST /v1/ramp/withdraw` operationId: `create-withdraw`	Correct the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `destination address not whitelisted`	Create Withdraw `POST /v1/ramp/withdraw` operationId: `create-withdraw`	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `withdraw product/fee not configured`	Create Withdraw `POST /v1/ramp/withdraw` operationId: `create-withdraw`	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `withdraw limit not configured for account`	Create Withdraw `POST /v1/ramp/withdraw` operationId: `create-withdraw`	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `amount too small to cover network fee`	Create Withdraw `POST /v1/ramp/withdraw` operationId: `create-withdraw`	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `risk verification rejected`	Create Withdraw `POST /v1/ramp/withdraw` operationId: `create-withdraw`	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `destination address risk score too high`	Create Withdraw `POST /v1/ramp/withdraw` operationId: `create-withdraw`	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `withdraw channel not configured for this account/asset`	Create Withdraw `POST /v1/ramp/withdraw` operationId: `create-withdraw`	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `destination address requires compliance info, please complete it in address book`	Create Withdraw `POST /v1/ramp/withdraw` operationId: `create-withdraw`	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `aml screening temporarily unavailable, please retry later`	Create Withdraw `POST /v1/ramp/withdraw` operationId: `create-withdraw`	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `withdraw create failed`	Create Withdraw `POST /v1/ramp/withdraw` operationId: `create-withdraw`	Retry later Retry only after the condition identified by the message has been resolved. View details Why this happened: The request could not be completed and changing request parameters alone may not resolve it. Retry: Retry only when the returned condition has been resolved and the operation permits it. When to contact UQPAY: Contact UQPAY if the same error persists after the recommended action and limited retries. Also provide: x-response-id, request time, HTTP method and path, complete error response.
400 Legacy flat	`400` `query withdrawals failed`	List Withdraws `GET /v1/ramp/withdraw` operationId: `list-withdraws`	Retry later Retry only after the condition identified by the message has been resolved. View details Why this happened: The request could not be completed and changing request parameters alone may not resolve it. Retry: Retry only when the returned condition has been resolved and the operation permits it. When to contact UQPAY: Contact UQPAY if the same error persists after the recommended action and limited retries. Also provide: x-response-id, request time, HTTP method and path, complete error response.
400 Legacy flat	`400` `withdrawal not found`	Retrieve Withdraw `GET /v1/ramp/withdraw/{order_id}` operationId: `retrieve-withdraw`	Verify the resource Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The resource is missing, unavailable, or does not belong to the current account. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `query assets failed`	List Supported Assets and Networks `GET /v1/ramp/config/assets` operationId: `list-supported-assets`	Retry later Retry only after the condition identified by the message has been resolved. View details Why this happened: The request could not be completed and changing request parameters alone may not resolve it. Retry: Retry only when the returned condition has been resolved and the operation permits it. When to contact UQPAY: Contact UQPAY if the same error persists after the recommended action and limited retries. Also provide: x-response-id, request time, HTTP method and path, complete error response.
400 Legacy flat	`400` `asset is required`	Estimate Network Fee `GET /v1/ramp/config/network-fee` operationId: `estimate-network-fee`	Correct the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `network fee unavailable`	Estimate Network Fee `GET /v1/ramp/config/network-fee` operationId: `estimate-network-fee`	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `legal_declaration does not match address_type`	Create Address Book `POST /v1/ramp/wallet_address` operationId: `create-address-book`	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `invalid travel rule meta_data json: invalid character ‘x’ looking for beginning of value`	Create Address Book `POST /v1/ramp/wallet_address` operationId: `create-address-book` Submit Deposit Sender Travel Rule `POST /v1/ramp/wallet_address/deposit-sender` operationId: `create-deposit-sender` Update Address Book `POST /v1/ramp/wallet_address/update` operationId: `update-address-book`	Correct the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `invalid wallet_type`	Create Address Book `POST /v1/ramp/wallet_address` operationId: `create-address-book` Submit Deposit Sender Travel Rule `POST /v1/ramp/wallet_address/deposit-sender` operationId: `create-deposit-sender` Update Address Book `POST /v1/ramp/wallet_address/update` operationId: `update-address-book`	Correct the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `invalid address_party`	Create Address Book `POST /v1/ramp/wallet_address` operationId: `create-address-book` Submit Deposit Sender Travel Rule `POST /v1/ramp/wallet_address/deposit-sender` operationId: `create-deposit-sender` Update Address Book `POST /v1/ramp/wallet_address/update` operationId: `update-address-book`	Correct the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `individual third party requires first_name and last_name`	Create Address Book `POST /v1/ramp/wallet_address` operationId: `create-address-book` Submit Deposit Sender Travel Rule `POST /v1/ramp/wallet_address/deposit-sender` operationId: `create-deposit-sender` Update Address Book `POST /v1/ramp/wallet_address/update` operationId: `update-address-book`	Correct the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `corporation third party requires company_name`	Create Address Book `POST /v1/ramp/wallet_address` operationId: `create-address-book` Submit Deposit Sender Travel Rule `POST /v1/ramp/wallet_address/deposit-sender` operationId: `create-deposit-sender` Update Address Book `POST /v1/ramp/wallet_address/update` operationId: `update-address-book`	Correct the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `invalid entity_type`	Create Address Book `POST /v1/ramp/wallet_address` operationId: `create-address-book` Submit Deposit Sender Travel Rule `POST /v1/ramp/wallet_address/deposit-sender` operationId: `create-deposit-sender` Update Address Book `POST /v1/ramp/wallet_address/update` operationId: `update-address-book`	Correct the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `third party requires country and city`	Create Address Book `POST /v1/ramp/wallet_address` operationId: `create-address-book` Submit Deposit Sender Travel Rule `POST /v1/ramp/wallet_address/deposit-sender` operationId: `create-deposit-sender` Update Address Book `POST /v1/ramp/wallet_address/update` operationId: `update-address-book`	Correct the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `hosted wallet requires vasp_id or vasp_name`	Create Address Book `POST /v1/ramp/wallet_address` operationId: `create-address-book` Submit Deposit Sender Travel Rule `POST /v1/ramp/wallet_address/deposit-sender` operationId: `create-deposit-sender` Update Address Book `POST /v1/ramp/wallet_address/update` operationId: `update-address-book`	Correct the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `this address is not allowed`	Create Address Book `POST /v1/ramp/wallet_address` operationId: `create-address-book`	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `invalid address format for network ETH`	Create Address Book `POST /v1/ramp/wallet_address` operationId: `create-address-book`	Correct the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `add address failed`	Create Address Book `POST /v1/ramp/wallet_address` operationId: `create-address-book`	Retry later Retry only after the condition identified by the message has been resolved. View details Why this happened: The request could not be completed and changing request parameters alone may not resolve it. Retry: Retry only when the returned condition has been resolved and the operation permits it. When to contact UQPAY: Contact UQPAY if the same error persists after the recommended action and limited retries. Also provide: x-response-id, request time, HTTP method and path, complete error response.
400 Legacy flat	`400` `address label already exists`	Create Address Book `POST /v1/ramp/wallet_address` operationId: `create-address-book`	Avoid duplicate submission Retry only after the condition identified by the message has been resolved. View details Why this happened: The same request or resource may already exist or still be processing. Retry: Retry only when the returned condition has been resolved and the operation permits it.
400 Legacy flat	`400` `invalid address_kind`	List Address Book `GET /v1/ramp/wallet_address` operationId: `list-address-book`	Correct the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `query wallet addresses failed`	List Address Book `GET /v1/ramp/wallet_address` operationId: `list-address-book`	Retry later Retry only after the condition identified by the message has been resolved. View details Why this happened: The request could not be completed and changing request parameters alone may not resolve it. Retry: Retry only when the returned condition has been resolved and the operation permits it. When to contact UQPAY: Contact UQPAY if the same error persists after the recommended action and limited retries. Also provide: x-response-id, request time, HTTP method and path, complete error response.
400 Legacy flat	`400` `whitelist address not found`	Update Address Book `POST /v1/ramp/wallet_address/update` operationId: `update-address-book`	Verify the resource Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The resource is missing, unavailable, or does not belong to the current account. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `load address failed`	Update Address Book `POST /v1/ramp/wallet_address/update` operationId: `update-address-book`	Retry later Retry only after the condition identified by the message has been resolved. View details Why this happened: The request could not be completed and changing request parameters alone may not resolve it. Retry: Retry only when the returned condition has been resolved and the operation permits it. When to contact UQPAY: Contact UQPAY if the same error persists after the recommended action and limited retries. Also provide: x-response-id, request time, HTTP method and path, complete error response.
400 Legacy flat	`400` `check label failed`	Update Address Book `POST /v1/ramp/wallet_address/update` operationId: `update-address-book`	Retry later Retry only after the condition identified by the message has been resolved. View details Why this happened: The request could not be completed and changing request parameters alone may not resolve it. Retry: Retry only when the returned condition has been resolved and the operation permits it. When to contact UQPAY: Contact UQPAY if the same error persists after the recommended action and limited retries. Also provide: x-response-id, request time, HTTP method and path, complete error response.
400 Legacy flat	`400` `label already used`	Update Address Book `POST /v1/ramp/wallet_address/update` operationId: `update-address-book`	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `invalid is_whitelist`	Update Address Book `POST /v1/ramp/wallet_address/update` operationId: `update-address-book`	Correct the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `update failed`	Update Address Book `POST /v1/ramp/wallet_address/update` operationId: `update-address-book`	Retry later Retry only after the condition identified by the message has been resolved. View details Why this happened: The request could not be completed and changing request parameters alone may not resolve it. Retry: Retry only when the returned condition has been resolved and the operation permits it. When to contact UQPAY: Contact UQPAY if the same error persists after the recommended action and limited retries. Also provide: x-response-id, request time, HTTP method and path, complete error response.
400 Legacy flat	`400` `travel rule already set, cannot edit`	Update Address Book `POST /v1/ramp/wallet_address/update` operationId: `update-address-book`	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `update travel rule failed`	Update Address Book `POST /v1/ramp/wallet_address/update` operationId: `update-address-book`	Retry later Retry only after the condition identified by the message has been resolved. View details Why this happened: The request could not be completed and changing request parameters alone may not resolve it. Retry: Retry only when the returned condition has been resolved and the operation permits it. When to contact UQPAY: Contact UQPAY if the same error persists after the recommended action and limited retries. Also provide: x-response-id, request time, HTTP method and path, complete error response.
400 Legacy flat	`400` `source_address and network are required`	Submit Deposit Sender Travel Rule `POST /v1/ramp/wallet_address/deposit-sender` operationId: `create-deposit-sender`	Correct the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `metadata is required`	Submit Deposit Sender Travel Rule `POST /v1/ramp/wallet_address/deposit-sender` operationId: `create-deposit-sender`	Correct the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `submit failed`	Submit Deposit Sender Travel Rule `POST /v1/ramp/wallet_address/deposit-sender` operationId: `create-deposit-sender`	Retry later Retry only after the condition identified by the message has been resolved. View details Why this happened: The request could not be completed and changing request parameters alone may not resolve it. Retry: Retry only when the returned condition has been resolved and the operation permits it. When to contact UQPAY: Contact UQPAY if the same error persists after the recommended action and limited retries. Also provide: x-response-id, request time, HTTP method and path, complete error response.
400 Legacy flat	`400` `for non-stablecoin swaps, amount must be on the crypto side and a multiple of the OKX contract step`	Create Quote `POST /v1/ramp/conversion/quote` operationId: `create-quote`	Correct the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `crypto service is not active for this account`	Create Conversion `POST /v1/ramp/conversion` operationId: `create-conversion` Create Withdraw `POST /v1/ramp/withdraw` operationId: `create-withdraw`	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `destination asset is not activated for this account`	Create Conversion `POST /v1/ramp/conversion` operationId: `create-conversion`	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `destination asset is inactive for this account`	Create Conversion `POST /v1/ramp/conversion` operationId: `create-conversion`	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `another swap for this account is in progress`	Create Conversion `POST /v1/ramp/conversion` operationId: `create-conversion`	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `buy/sell supports stablecoins only; use swap for non-stablecoins`	Create Conversion `POST /v1/ramp/conversion` operationId: `create-conversion`	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `no balance account for this asset`	Create Withdraw `POST /v1/ramp/withdraw` operationId: `create-withdraw`	Check the balance Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The available balance or currency does not meet the operation requirements. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `asset is required for a universal whitelist address`	Create Withdraw `POST /v1/ramp/withdraw` operationId: `create-withdraw`	Correct the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `asset does not match the whitelisted address`	Create Withdraw `POST /v1/ramp/withdraw` operationId: `create-withdraw`	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `Invalid idempotency key.`	Applies to 7 public endpoints	Avoid duplicate submission Retry only after the condition identified by the message has been resolved. View details Why this happened: The same request or resource may already exist or still be processing. Retry: Retry only when the returned condition has been resolved and the operation permits it.
400 Legacy flat	`400` `The idempotency key provided failed authentication, please check client id.`	Applies to 7 public endpoints	Avoid duplicate submission Retry only after the condition identified by the message has been resolved. View details Why this happened: The same request or resource may already exist or still be processing. Retry: Retry only when the returned condition has been resolved and the operation permits it.
400 Legacy flat	`400` `Idempotent request endpoint does not match the initial one.`	Applies to 7 public endpoints	Avoid duplicate submission Retry only after the condition identified by the message has been resolved. View details Why this happened: The same request or resource may already exist or still be processing. Retry: Retry only when the returned condition has been resolved and the operation permits it.
400 Legacy flat	`1005` `Idempotency key reused with different request payload`	Applies to 7 public endpoints	Avoid duplicate submission Retry only after the condition identified by the message has been resolved. View details Why this happened: The same request or resource may already exist or still be processing. Retry: Retry only when the returned condition has been resolved and the operation permits it.
409 Legacy flat	`409` `Request is processing, please try again later.`	Applies to 7 public endpoints	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
500 Other envelope	`""` `An internal error occurred, please try again`	Applies to 7 public endpoints	Retry later Retry only after the condition identified by the message has been resolved. View details Why this happened: The request could not be completed and changing request parameters alone may not resolve it. Retry: Retry only when the returned condition has been resolved and the operation permits it. When to contact UQPAY: Contact UQPAY if the same error persists after the recommended action and limited retries. Also provide: x-response-id, request time, HTTP method and path, complete error response.

Getting Started

Assets & Balances

Deposits

Withdrawals

Conversions & Transfers

Reference

How to use this page

Error response format

Error code table

​How to use this page

​Error response format

​Error code table

​Related documentation

How to use this page

Error response format

Error code table

Related documentation