Error codes

When the Global 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

Errors do not always include a type field. Use the HTTP status, code, message, and endpoint together. 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`	Applies to 27 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	`400` `IP not allowed`	Applies to 27 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	`1014` `Banking account is not activated`	Applies to 27 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	`1114` `Failed identity verification`	Applies to 27 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	`1122` `Api not enabled`	Applies to 27 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` `invalid x-on-behalf-of account id`	Applies to 27 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`	Applies to 24 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`	Applies to 24 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`	Applies to 24 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`	Applies to 24 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`	Applies to 27 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` `invalid request`	Applies to 27 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 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.
400 Legacy flat	`400` `page_number must be a positive integer`	List Transfers `GET /v1/transfer` operationId: `list-transfers`	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` `page_size must be between 1 and 100`	List Transfers `GET /v1/transfer` operationId: `list-transfers`	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` `transfer_status must be completed or failed`	List Transfers `GET /v1/transfer` operationId: `list-transfers`	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 currency filter`	List Transfers `GET /v1/transfer` operationId: `list-transfers`	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` `start_time invalid`	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` `end_time invalid`	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` `query transfers failed`	List Transfers `GET /v1/transfer` operationId: `list-transfers`	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_account_id, target_account_id and reason are required`	Create Transfer `POST /v1/transfer` operationId: `create-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 Legacy flat	`400` `source and target account cannot be the same`	Create Transfer `POST /v1/transfer` operationId: `create-transfer`	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 currency code`	Create Transfer `POST /v1/transfer` operationId: `create-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 Legacy flat	`400` `invalid transfer amount`	Create Transfer `POST /v1/transfer` operationId: `create-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 Legacy flat	`400` `amount must be an integer for %s`	Create Transfer `POST /v1/transfer` operationId: `create-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 Legacy flat	`400` `authenticated account must be source or target account`	Create Transfer `POST /v1/transfer` operationId: `create-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 Legacy flat	`400` `idempotency key reused with a different request payload`	Create Transfer `POST /v1/transfer` operationId: `create-transfer`	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` `transfer create failed`	Create Transfer `POST /v1/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 Legacy flat	`400` `insufficient balance`	Create Conversion `POST /v1/conversion` operationId: `create-conversion` Create Payout `POST /v1/payouts` operationId: `create-payout` Create Transfer `POST /v1/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 Legacy flat	`400` `transfer not found`	Retrieve Transfer `GET /v1/transfer/{id}` operationId: `retrieve-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 Legacy flat	`400` `payout_date invalid`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `purpose_code invalid`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `amount invalid`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `payment amount must equal receiving amount`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `payment currency must equal receiving currency`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `neither beneficiary_id nor beneficiary can be empty`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `beneficiary invalid`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `entity_type is required`	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` `account_number is required`	Create Beneficiary `POST /v1/beneficiaries` operationId: `create-beneficiary` Create Payout `POST /v1/payouts` operationId: `create-payout` Update Beneficiary `POST /v1/beneficiaries/{id}` operationId: `update-beneficiary`	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` `Iban format error`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `swift_code is required`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `routing_code_type1 or routing_code_value1 is missing`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `routing_code_type1 invalid: ACH requires ‘ach’`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `routing_code_type1 invalid: FEDWIRE requires ‘aba’`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `EFT requires routing_code_type1/2 as ‘bank_code’ and ‘branch_code’`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `routing_code_value1 or routing_code_value2 is missing`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `CAD-EFT account number length must be 7-12 digits`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `HKD-LOCAL requires routing_code_type1=‘bank_code’ and non-empty value`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `FASTER PAYMENTS requires routing_code_type1=‘sort_code’ and non-empty value`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `AUD account number length must be 5-20 digits`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `AUD-LOCAL requires routing_code_type1=‘bsb_code’ and non-empty value`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `IFSC requires routing_code_type1=‘ifsc’ and non-empty value`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `PayNow requires non-empty proxy_id`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `additional_info.id_type is required`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `additional_info.id_number is required`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `additional_info.msisdn is required`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `additional_info.tax_id is required`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `Field ‘address.country’ is required (current value: )`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `Field ‘address.city’ is required (current value: )`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `Field ‘address.state’ is required (current value: )`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `Field ‘address.street_address’ is required (current value: )`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `Field ‘address.postal_code’ is required (current value: )`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `CN-CNH requires routing_code_type1=‘cnaps_number’ and non-empty value`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `bank_name is required`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `bank_address is required`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `Bic/Swift code format error`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `The account number field allows only English letters (a-z, A-Z) and digits (0-9)`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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 number format error`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `Please provide a valid account holder name.`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `The account holder name needs to be between 2 and 140 characters.`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `The account holder name (individual) can only contain English letters and spaces.`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `The account holder name may include invalid characters or is incomplete.`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `The account holder name (company) contains invalid characters.`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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 requires non-empty first_name and last_name`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `company requires non-empty company_name`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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_holder cannot be empty`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `street_address cannot be empty`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `city cannot be empty`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `state cannot be empty`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `clearing_system cannot be empty`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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 paymentMethods err`	Check Beneficiary `POST /v1/beneficiaries/check` operationId: `check-beneficiary` Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `clearing system not support for country: %s, currency: %s, paymentMethod: %s`	Check Beneficiary `POST /v1/beneficiaries/check` operationId: `check-beneficiary` Create Payout `POST /v1/payouts` operationId: `create-payout`	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`	Applies to 4 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` `currency not supported`	Create Conversion `POST /v1/conversion` operationId: `create-conversion` Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `idempotency key reused with different request payload`	Create Conversion `POST /v1/conversion` operationId: `create-conversion` Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `payout create failed`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `create payout failed, please try again`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `fee_paid_by must be OURS or SHARED for SWIFT payout`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `payout reference contains unsupported characters for SWIFT`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `for INR payouts using LOCAL payment method, an invoice document is required`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `pay on behalf of (POBO) is not enabled for this account`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `POBO or payout with transfer is not enable for your account`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `payer not exists`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `with-transfer requires an active subaccount linked to an active House account`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `beneficiary target account invalid`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `beneficiary target account mismatch`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `internal payout does not support cross-currency`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `quote invalid or mismatched`	Create Conversion `POST /v1/conversion` operationId: `create-conversion` Create Payout `POST /v1/payouts` operationId: `create-payout`	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`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `SGD FAST payout cannot exceed 200,000 per transaction`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `beneficiary not found`	Create Payout `POST /v1/payouts` operationId: `create-payout` Retrieve Beneficiary `GET /v1/beneficiaries/{id}` operationId: `retrieve-beneficiary` Update Beneficiary `POST /v1/beneficiaries/{id}` operationId: `update-beneficiary`	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` `beneficiary not active`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `recipient repeat addition`	Create Beneficiary `POST /v1/beneficiaries` operationId: `create-beneficiary` Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `payout product not enrolled`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `payout fee tier not configured`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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 active payout channel for this currency pair`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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` `the specified payout channel is not active`	Create Payout `POST /v1/payouts` operationId: `create-payout`	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 payouts failed`	List Payouts `GET /v1/payouts` operationId: `list-payouts`	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` `payout not found`	Retrieve Payout `GET /v1/payouts/{id}` operationId: `retrieve-payout`	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` `retrieve payout failed`	Retrieve Payout `GET /v1/payouts/{id}` operationId: `retrieve-payout`	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` `retrieve beneficiary bank failed`	Check Beneficiary `POST /v1/beneficiaries/check` operationId: `check-beneficiary` Retrieve Beneficiary `GET /v1/beneficiaries/{id}` operationId: `retrieve-beneficiary` Retrieve Payout `GET /v1/payouts/{id}` operationId: `retrieve-payout`	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` `retrieve beneficiary address failed`	Check Beneficiary `POST /v1/beneficiaries/check` operationId: `check-beneficiary` Retrieve Beneficiary `GET /v1/beneficiaries/{id}` operationId: `retrieve-beneficiary` Retrieve Payout `GET /v1/payouts/{id}` operationId: `retrieve-payout`	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` `find recipient occur error`	Create Beneficiary `POST /v1/beneficiaries` operationId: `create-beneficiary`	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` `create beneficiary failed`	Create Beneficiary `POST /v1/beneficiaries` operationId: `create-beneficiary`	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` `beneficiary_id invalid`	Delete Beneficiary `POST /v1/beneficiaries/{id}/delete` operationId: `delete-beneficiary` Retrieve Beneficiary `GET /v1/beneficiaries/{id}` operationId: `retrieve-beneficiary` Update Beneficiary `POST /v1/beneficiaries/{id}` operationId: `update-beneficiary`	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` `can’t change entity_type`	Update Beneficiary `POST /v1/beneficiaries/{id}` operationId: `update-beneficiary`	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 beneficiary failed`	Update Beneficiary `POST /v1/beneficiaries/{id}` operationId: `update-beneficiary`	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` `delete beneficiary failed`	Delete Beneficiary `POST /v1/beneficiaries/{id}/delete` operationId: `delete-beneficiary`	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` `find beneficiary error`	Check Beneficiary `POST /v1/beneficiaries/check` operationId: `check-beneficiary`	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` `currency is invalid`	Retrieve Balance `GET /v1/balances/{currency}` operationId: `retrieve-balance`	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` `balance not found`	Retrieve Balance `GET /v1/balances/{currency}` operationId: `retrieve-balance`	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 balances failed`	List Balances `GET /v1/balances` operationId: `list-balances`	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` `query transactions failed`	List Balances Transactions `GET /v1/balances/transactions` operationId: `list-balances-transactions`	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` `query deposits failed`	List Deposits `GET /v1/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` `invalid deposit_id`	Retrieve Deposit `GET /v1/deposit/{id}` operationId: `retrieve-deposit`	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 not found`	Retrieve Deposit `GET /v1/deposit/{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` `query virtual accounts failed`	List Virtual Accounts `GET /v1/virtual/accounts` operationId: `list-virtual-accounts`	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` `Request parameters invalid`	Create Virtual Account `POST /v1/virtual/accounts` operationId: `create-virtual-account`	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 conversions failed`	List Conversion `GET /v1/conversion` operationId: `list-conversion`	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 amount: provide positive sell_amount or buy_amount`	Create Conversion `POST /v1/conversion` operationId: `create-conversion` Create Quote `POST /v1/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` `invalid conversion_date`	Create Conversion `POST /v1/conversion` operationId: `create-conversion` Create Quote `POST /v1/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` `unsupported currency pair`	Create Conversion `POST /v1/conversion` operationId: `create-conversion` Create Quote `POST /v1/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` `No available conversion date`	Create Conversion `POST /v1/conversion` operationId: `create-conversion` Create Quote `POST /v1/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` `The currency exchange service is temporarily unavailable during %s-%s UTC+8. Please select another time slot.`	Create Conversion `POST /v1/conversion` operationId: `create-conversion` Create Quote `POST /v1/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 type does not support conversion`	Create Conversion `POST /v1/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` `account margin balance insufficient`	Create Conversion `POST /v1/conversion` operationId: `create-conversion`	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` `conversion create failed`	Create Conversion `POST /v1/conversion` operationId: `create-conversion`	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` `conversion not found`	Retrieve Conversion `GET /v1/conversion/{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` `invalid quote request (check currencies/amount)`	Create Quote `POST /v1/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/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` `quote product not enrolled for this account`	Create Quote `POST /v1/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` `conversion quote failed`	Create Quote `POST /v1/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` `Too many request parameters`	List Current Rates `GET /v1/exchange/rates` operationId: `list-current-rates`	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` `Exchange rates are temporarily unavailable. Please try again later.`	List Current Rates `GET /v1/exchange/rates` operationId: `list-current-rates`	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` `Field ‘account_id’ is required`	Simulate Deposit Creation `POST /v1/simulation/deposit` operationId: `simulate-deposit-creation`	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 Amount must not be less than 0`	Simulate Deposit Creation `POST /v1/simulation/deposit` operationId: `simulate-deposit-creation`	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` `Amount must be an integer for %s`	Simulate Deposit Creation `POST /v1/simulation/deposit` operationId: `simulate-deposit-creation`	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 account failed`	Simulate Deposit Creation `POST /v1/simulation/deposit` operationId: `simulate-deposit-creation`	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` `account status error`	Simulate Deposit Creation `POST /v1/simulation/deposit` operationId: `simulate-deposit-creation`	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` `get va deposit product error`	Simulate Deposit Creation `POST /v1/simulation/deposit` operationId: `simulate-deposit-creation`	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` `create deposit failed`	Simulate Deposit Creation `POST /v1/simulation/deposit` operationId: `simulate-deposit-creation`	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.

Overview

Virtual Account

Payout & Deposit

Foreign Exchange

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