Error codes

When the Card Issuance 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 `""`	`""` `Bad Request`	Applies to 35 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 does not exist.`	Applies to 13 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 status error`	Simulate Authorization `POST /v1/simulation/issuing/authorization` operationId: `simulate-authorization` Simulate Reversal `POST /v1/simulation/issuing/reversal` operationId: `simulate-reversal`	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` `An active or in-progress elevate request already exists for this card`	Elevate Per-Transaction Limit `POST /v1/issuing/cards/{id}/elevate_limit` operationId: `elevate-card-limit`	Correct the request Retry only after the condition identified by the message has been resolved. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry only when the returned condition has been resolved and the operation permits it.
400 Legacy flat	`400` `An internal error occurred, please try again`	Elevate Per-Transaction Limit `POST /v1/issuing/cards/{id}/elevate_limit` operationId: `elevate-card-limit`	Contact UQPAY Stop frequent retries. Wait briefly, then retry with exponential backoff. View details Why this happened: UQPAY must check an account configuration, quota, or service-side condition. Retry: Retry with exponential backoff; stop and contact UQPAY if the error persists. 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, complete error response.
400 Legacy flat	`400` `Card authorize transaction is error`	Simulate Authorization `POST /v1/simulation/issuing/authorization` operationId: `simulate-authorization`	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` `Card currency is not supported for elevate limit`	Elevate Per-Transaction Limit `POST /v1/issuing/cards/{id}/elevate_limit` operationId: `elevate-card-limit`	Correct the request Retry only after the condition identified by the message has been resolved. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry only when the returned condition has been resolved and the operation permits it.
400 Legacy flat	`400` `Card does not exists`	Activate Card `POST /v1/issuing/cards/activate` operationId: `activate-card` Elevate Per-Transaction Limit `POST /v1/issuing/cards/{id}/elevate_limit` operationId: `elevate-card-limit` Simulate Authorization `POST /v1/simulation/issuing/authorization` operationId: `simulate-authorization`	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` `Card product is error`	Activate Card `POST /v1/issuing/cards/activate` operationId: `activate-card`	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` `Card reversal transaction is error`	Simulate Reversal `POST /v1/simulation/issuing/reversal` operationId: `simulate-reversal`	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` `Card status is invalid`	Activate Card `POST /v1/issuing/cards/activate` operationId: `activate-card` Simulate Authorization `POST /v1/simulation/issuing/authorization` operationId: `simulate-authorization`	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` `Card status must be ACTIVE to elevate the per-transaction limit`	Elevate Per-Transaction Limit `POST /v1/issuing/cards/{id}/elevate_limit` operationId: `elevate-card-limit`	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` `Elevate limit amount exceeds the per-currency cap`	Elevate Per-Transaction Limit `POST /v1/issuing/cards/{id}/elevate_limit` operationId: `elevate-card-limit`	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` `Elevate per-transaction limit is not supported for this card`	Elevate Per-Transaction Limit `POST /v1/issuing/cards/{id}/elevate_limit` operationId: `elevate-card-limit`	Correct the request Retry only after the condition identified by the message has been resolved. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry only when the returned condition has been resolved and the operation permits it.
400 Legacy flat	`400` `Invalid activation code.`	Activate Card `POST /v1/issuing/cards/activate` operationId: `activate-card`	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 channel code`	Simulate Authorization `POST /v1/simulation/issuing/authorization` operationId: `simulate-authorization` Simulate Reversal `POST /v1/simulation/issuing/reversal` operationId: `simulate-reversal`	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 no pin payment amount precision.`	Activate Card `POST /v1/issuing/cards/activate` operationId: `activate-card`	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 type for field …`	Card Recharge `POST /v1/issuing/cards/{id}/recharge` operationId: `card-recharge` Simulate Reversal `POST /v1/simulation/issuing/reversal` operationId: `simulate-reversal`	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 type for request field, please see document`	Applies to 8 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` `Login expired`	Simulate Authorization `POST /v1/simulation/issuing/authorization` operationId: `simulate-authorization` Simulate Reversal `POST /v1/simulation/issuing/reversal` operationId: `simulate-reversal`	Authenticate again Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The access token is missing, expired, or invalid. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `MCC is error`	Simulate Authorization `POST /v1/simulation/issuing/authorization` operationId: `simulate-authorization`	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` `Negative no pin payment amount.`	Activate Card `POST /v1/issuing/cards/activate` operationId: `activate-card`	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` `Remote service error`	Applies to 10 public endpoints	Contact UQPAY Stop frequent retries. Wait briefly, then retry with exponential backoff. View details Why this happened: UQPAY must check an account configuration, quota, or service-side condition. Retry: Retry with exponential backoff; stop and contact UQPAY if the error persists. 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, complete error response.
400 Legacy flat	`400` `Request parameters invalid`	Applies to 9 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` `Restrict config error`	Simulate Authorization `POST /v1/simulation/issuing/authorization` operationId: `simulate-authorization` Simulate Reversal `POST /v1/simulation/issuing/reversal` operationId: `simulate-reversal`	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. When to contact UQPAY: Contact UQPAY if the same error persists after the recommended action and limited retries. Also provide: card ID, non-sensitive request fields.
400 Legacy flat	`400` `The card activation is processing.`	Activate Card `POST /v1/issuing/cards/activate` operationId: `activate-card`	Wait and retry Wait for the current operation or resource state to change, then retry. View details Why this happened: The related request or resource is still being processed. Retry: Wait for the operation or state change before retrying; do not poll rapidly.
400 Legacy flat	`400` `The card has been activated.`	Activate Card `POST /v1/issuing/cards/activate` operationId: `activate-card`	Correct the request Retry only after the condition identified by the message has been resolved. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry only when the returned condition has been resolved and the operation permits it.
400 Legacy flat	`400` `The card has expired`	Activate Card `POST /v1/issuing/cards/activate` operationId: `activate-card`	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 no_pin_payment_amount restrict configuration cannot be found`	Activate Card `POST /v1/issuing/cards/activate` operationId: `activate-card`	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` `TransactionId`	Simulate Reversal `POST /v1/simulation/issuing/reversal` operationId: `simulate-reversal`	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` `TransactionId cannot be empty`	Simulate Reversal `POST /v1/simulation/issuing/reversal` operationId: `simulate-reversal`	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` `Unexpected error`	Simulate Reversal `POST /v1/simulation/issuing/reversal` operationId: `simulate-reversal`	Contact UQPAY Stop frequent retries. Wait briefly, then retry with exponential backoff. View details Why this happened: UQPAY must check an account configuration, quota, or service-side condition. Retry: Retry with exponential backoff; stop and contact UQPAY if the error persists. 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, complete error response.
400 Legacy flat	`400` `Update card error`	Activate Card `POST /v1/issuing/cards/activate` operationId: `activate-card`	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_number is invalid’]`	List Cards `GET /v1/issuing/cards` operationId: `list-cards`	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` `card id is invalid`	Card Recharge `POST /v1/issuing/cards/{id}/recharge` operationId: `card-recharge` Card Withdraw `POST /v1/issuing/cards/{id}/withdraw` operationId: `card-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` `card limit is illegal`	Update Card `POST /v1/issuing/cards/{id}` operationId: `update-card`	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` `card_number value is illegal`	List Cards `GET /v1/issuing/cards` operationId: `list-cards`	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` `card_status value is illegal`	List Cards `GET /v1/issuing/cards` operationId: `list-cards`	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 [name_on_card] exceeds the maximum length of 26`	Update Card `POST /v1/issuing/cards/{id}` operationId: `update-card`	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` `id is invalid`	Applies to 7 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 no pin payment amount for the current currency.`	Activate Card `POST /v1/issuing/cards/activate` operationId: `activate-card`	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 no pin payment amount precision`	Update Card `POST /v1/issuing/cards/{id}` operationId: `update-card`	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` `limit_amount must be greater than 0`	Elevate Per-Transaction Limit `POST /v1/issuing/cards/{id}/elevate_limit` operationId: `elevate-card-limit`	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` `limit_amount precision invalid`	Elevate Per-Transaction Limit `POST /v1/issuing/cards/{id}/elevate_limit` operationId: `elevate-card-limit`	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` Message pattern `missing field: [{field}]`	Activate Card `POST /v1/issuing/cards/activate` operationId: `activate-card`	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` `negative no pin payment amount`	Update Card `POST /v1/issuing/cards/{id}` operationId: `update-card`	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 pin payment amount failed.`	Activate Card `POST /v1/issuing/cards/activate` operationId: `activate-card`	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` `recharge amount is invalid`	Card Recharge `POST /v1/issuing/cards/{id}/recharge` operationId: `card-recharge`	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` `transaction amount is invalid`	Simulate Authorization `POST /v1/simulation/issuing/authorization` operationId: `simulate-authorization`	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 reason too long`	Update Card Status `POST /v1/issuing/cards/{id}/status` operationId: `update-card-status`	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` `withdraw amount is invalid`	Card Withdraw `POST /v1/issuing/cards/{id}/withdraw` operationId: `card-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 Other envelope	`cardholder_incomplete_fields` `cardholder_required_fields is incomplete for one-time card issuance`	Create Card `POST /v1/issuing/cards` operationId: `create-card`	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 `account_error`	`account_balance_error` `insufficient balance or currency balance unavailable`	Create Card `POST /v1/issuing/cards` operationId: `create-card` Create Issuing Transfer `POST /v1/issuing/transfers` operationId: `create-issuing-transfer` Retrieve Issuing Balance `POST /v1/issuing/balances` operationId: `retrieve-issuing-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 `account_error`	`account_not_found` `account not found or deactivated`	Applies to 30 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 `account_error`	`product_not_found` `product not found or inactive`	Create Issuing Transfer `POST /v1/issuing/transfers` operationId: `create-issuing-transfer` List Card Arts `GET /v1/issuing/cards/arts` operationId: `list-card-arts`	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 `account_error`	`sub_account_not_found` `sub-account associated with the on-behalf-of not found or deactivated`	Applies to 22 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 `card_error`	`card_art_not_available` `card_art_id is not available for this account`	Set Default Card Art `POST /v1/issuing/cards/arts/default` operationId: `set-default-card-art`	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 `card_error`	`card_art_not_supported` `card_art_id is not supported for this product`	Create Card `POST /v1/issuing/cards` operationId: `create-card`	Correct the request Retry only after the condition identified by the message has been resolved. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry only when the returned condition has been resolved and the operation permits it.
400 `card_error`	`card_expired_error` `card has expired`	Activate Card `POST /v1/issuing/cards/activate` operationId: `activate-card` Set or Reset Virtual Card PIN `POST /v1/issuing/cards/manage/pin` operationId: `manage-card-pin`	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 `card_error`	`card_not_found` `card not found or deactivated`	Endpoints that retrieve or modify a card by card ID	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. When to contact UQPAY: Contact UQPAY if the same error persists after the recommended action and limited retries. Also provide: card ID. Related endpoints: List Cards · Retrieve Card
400 `card_error`	`currency_not_allowed` `card currency is not allowed`	Create Card `POST /v1/issuing/cards` operationId: `create-card`	Correct the request Retry only after the condition identified by the message has been resolved. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry only when the returned condition has been resolved and the operation permits it.
400 `card_error`	`enable_3ds_not_allowed` `merchant not allowed to set enable_3ds`	Create Card `POST /v1/issuing/cards` operationId: `create-card`	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 `card_error`	`insufficient_sub_bin` `insufficient available cards for sub-bin`	Create Card `POST /v1/issuing/cards` operationId: `create-card`	Contact UQPAY Wait for the current operation or resource state to change, then retry. View details Why this happened: UQPAY must check an account configuration, quota, or service-side condition. Retry: Wait for the operation or state change before retrying; do not poll rapidly. When to contact UQPAY: Contact UQPAY if the same error persists after the recommended action and limited retries. Also provide: account ID, card product ID or BIN.
400 `card_error`	`limit_out_of_range` `card limit is either less than minimum card limit or greater than maximum card limit`	Create Card `POST /v1/issuing/cards` operationId: `create-card`	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 `card_error`	`operation_not_authorized` `requested card operation type is not authorized`	Create Card `POST /v1/issuing/cards` operationId: `create-card`	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 `card_error`	`risk_control_not_allowed` `risk control setting is not allowed`	Create Card `POST /v1/issuing/cards` operationId: `create-card`	Correct the request Retry only after the condition identified by the message has been resolved. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry only when the returned condition has been resolved and the operation permits it.
400 `card_error`	`status_not_supported` `card status or activation status not supported by request`	Applies to 4 public endpoints	Wait and retry Retry only after the condition identified by the message has been resolved. View details Why this happened: The related request or resource is still being processed. Retry: Retry only when the returned condition has been resolved and the operation permits it. Note: Keep the endpoint, method, and request unchanged when reusing an idempotency key. Related endpoints: Retrieve Card
400 `card_error`	`virtual_card_pin_error` `virtual cards do not allow pin settings`	Activate Card `POST /v1/issuing/cards/activate` operationId: `activate-card`	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 `cardholder_error`	`cardholder_cannot_update_during_review` `cannot update KYC fields while review is pending`	Update Cardholder `POST /v1/issuing/cardholders/{id}` operationId: `update-cardholder`	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 `cardholder_error`	`cardholder_kyc_failed` `cardholder KYC has been rejected`	Create Card `POST /v1/issuing/cards` operationId: `create-card` Update Cardholder `POST /v1/issuing/cardholders/{id}` operationId: `update-cardholder`	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 `cardholder_error`	`cardholder_kyc_pending` `cardholder KYC is under review, cannot proceed`	Create Card `POST /v1/issuing/cards` operationId: `create-card`	Wait and retry Wait for the current operation or resource state to change, then retry. View details Why this happened: The related request or resource is still being processed. Retry: Wait for the operation or state change before retrying; do not poll rapidly. When to contact UQPAY: Contact UQPAY if the same error persists after the recommended action and limited retries. Also provide: cardholder ID, latest KYC status. Related endpoints: Retrieve Cardholder
400 `cardholder_error`	`cardholder_missing_info` `either cardholder_id or complete cardholder_required_fields must be provided`	Create Card `POST /v1/issuing/cards` operationId: `create-card`	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 `cardholder_error`	`cardholder_not_found` `cardholder not found or deactivated`	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. When to contact UQPAY: Contact UQPAY if the same error persists after the recommended action and limited retries. Also provide: cardholder ID. Related endpoints: List Cardholders
400 `cardholder_error`	`document_duplicated` `document already successfully reviewed`	Create Cardholder `POST /v1/issuing/cardholders` operationId: `create-cardholder` Update Cardholder `POST /v1/issuing/cardholders/{id}` operationId: `update-cardholder`	Correct the request Retry only after the condition identified by the message has been resolved. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry only when the returned condition has been resolved and the operation permits it.
400 `cardholder_error`	`document_size_exceeded` `document size exceeds 2MB limit`	Update Cardholder `POST /v1/issuing/cardholders/{id}` operationId: `update-cardholder`	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 `cardholder_error`	`email_duplicated` `email already used by another cardholder under account`	Create Cardholder `POST /v1/issuing/cardholders` operationId: `create-cardholder` Update Cardholder `POST /v1/issuing/cardholders/{id}` operationId: `update-cardholder`	Correct the request Retry only after the condition identified by the message has been resolved. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry only when the returned condition has been resolved and the operation permits it.
400 `cardholder_error`	`file_type_not_supported` `unsupported document file type`	Update Cardholder `POST /v1/issuing/cardholders/{id}` operationId: `update-cardholder`	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 `cardholder_error`	`invalid_date_of_birth` `cardholder under 18 or invalid date of birth format`	Create Cardholder `POST /v1/issuing/cardholders` operationId: `create-cardholder` Update Cardholder `POST /v1/issuing/cardholders/{id}` operationId: `update-cardholder`	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 `cardholder_error`	`invalid_delivery_address` `invalid delivery address`	Create Cardholder `POST /v1/issuing/cardholders` operationId: `create-cardholder`	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 `cardholder_error`	`invalid_file_content` `invalid base64 encoded document content`	Create Card `POST /v1/issuing/cards` operationId: `create-card` Create Cardholder `POST /v1/issuing/cardholders` operationId: `create-cardholder` Update Cardholder `POST /v1/issuing/cardholders/{id}` operationId: `update-cardholder`	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. Note: Keep the endpoint, method, and request unchanged when reusing an idempotency key. Also provide: file type, file size (do not send the identity file).
400 `cardholder_error`	`invalid_first_name` `invalid first name, only letters and spaces allowed, no leading or trailing spaces`	Create Cardholder `POST /v1/issuing/cardholders` operationId: `create-cardholder`	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 `cardholder_error`	`invalid_identity_type` `invalid identity type, must be ID_CARD or PASSPORT`	Update Cardholder `POST /v1/issuing/cardholders/{id}` operationId: `update-cardholder`	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 `cardholder_error`	`invalid_last_name` `invalid last name, only letters and spaces allowed, no leading or trailing spaces`	Create Cardholder `POST /v1/issuing/cardholders` operationId: `create-cardholder`	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 `cardholder_error`	`invalid_phone_number` `invalid phone number or country code`	Create Cardholder `POST /v1/issuing/cardholders` operationId: `create-cardholder` Update Cardholder `POST /v1/issuing/cardholders/{id}` operationId: `update-cardholder`	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 `cardholder_error`	`invalid_residential_address` `invalid residential_address, only letters, numbers, spaces and common punctuation (, . ’ / # ( ) - &) allowed`	Update Cardholder `POST /v1/issuing/cardholders/{id}` operationId: `update-cardholder`	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 `cardholder_error`	`kyc_insufficient` Dynamic message Message 会说明持卡人信息不满足产品要求，并返回 missing_fields。	Assign Card `POST /v1/issuing/cards/assign` operationId: `assign-card` Create Card `POST /v1/issuing/cards` operationId: `create-card`	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. When to contact UQPAY: Contact UQPAY if the same error persists after the recommended action and limited retries. Also provide: card product ID, missing_fields. Related endpoints: Update Cardholder
400 `cardholder_error`	`kyc_insufficient` `cardholder information does not meet this product’s requirements`	Assign Card `POST /v1/issuing/cards/assign` operationId: `assign-card` Create Card `POST /v1/issuing/cards` operationId: `create-card`	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 `cardholder_error`	`missing_date_of_birth` `missing legal date of birth for document upload`	Create Cardholder `POST /v1/issuing/cardholders` operationId: `create-cardholder` Update Cardholder `POST /v1/issuing/cardholders/{id}` operationId: `update-cardholder` Create Card `POST /v1/issuing/cards` operationId: `create-card`	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 `cardholder_error`	`phone_number_duplicated` `phone number used by another cardholder under account`	Create Cardholder `POST /v1/issuing/cardholders` operationId: `create-cardholder` Update Cardholder `POST /v1/issuing/cardholders/{id}` operationId: `update-cardholder`	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 `cardholder_error`	`reference_id_duplicated` `reference_id already used by another cardholder`	Create Cardholder `POST /v1/issuing/cardholders` operationId: `create-cardholder` Update Cardholder `POST /v1/issuing/cardholders/{id}` operationId: `update-cardholder` Create Card `POST /v1/issuing/cards` operationId: `create-card`	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 `idempotency_error`	`invalid_key_format` `invalid idempotency key format`	Applies to 18 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 `idempotency_error`	`key_mismatch_account` `key does not belong to account`	Reset Card PIN `POST /v1/issuing/cards/pin` operationId: `reset-pin`	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 `idempotency_error`	`key_mismatch_api` `api associated with key is not the original`	All public endpoints that use x-idempotency-key	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. Note: Keep the endpoint, method, and request unchanged when reusing an idempotency key.
400 `idempotency_error`	`request_being_processed` `request is being processed`	All public endpoints that use x-idempotency-key	Wait and retry Wait briefly, then retry with the same Idempotency-Key and exactly the same request body. View details Why this happened: The related request or resource is still being processed. Retry: Reuse the key only when the endpoint, method, and request body are unchanged. Note: Keep the endpoint, method, and request unchanged when reusing an idempotency key. When to contact UQPAY: Contact UQPAY if the same error persists after the recommended action and limited retries. Also provide: Idempotency-Key, original request time, retry time.
400 `invalid_request_error`	`invalid_request_error` `Account card quota exceeded.`	Assign Card `POST /v1/issuing/cards/assign` operationId: `assign-card`	Contact UQPAY Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: UQPAY must check an account configuration, quota, or service-side condition. Retry: Retry after correcting the request or resource state. 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, complete error response.
400 `invalid_request_error`	`invalid_request_error` `COUNTRY_PRODUCT_MISMATCH`	Assign Card `POST /v1/issuing/cards/assign` operationId: `assign-card`	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 `invalid_request_error`	`invalid_request_error` `Cardholder card quota exceeded.`	Assign Card `POST /v1/issuing/cards/assign` operationId: `assign-card`	Contact UQPAY Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: UQPAY must check an account configuration, quota, or service-side condition. Retry: Retry after correcting the request or resource state. 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, complete error response.
400 `invalid_request_error`	`invalid_request_error` `HA_TO_SA feature unavailable`	Create Issuing Transfer `POST /v1/issuing/transfers` operationId: `create-issuing-transfer`	Correct the request Retry only after the condition identified by the message has been resolved. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry only when the returned condition has been resolved and the operation permits it.
400 `invalid_request_error`	`invalid_request_error` Dynamic message Message 会指出 page_number 或 page_size 的校验问题。	List Merchant Brands `GET /v1/issuing/merchant_brands` operationId: `list-merchant-brands`	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 `invalid_request_error`	`invalid_request_error` Dynamic message Message 会指出不合法的字段或校验规则。	Create Card `POST /v1/issuing/cards` operationId: `create-card`	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. When to contact UQPAY: Contact UQPAY if the same error persists after the recommended action and limited retries.
400 `invalid_request_error`	`invalid_request_error` Dynamic message Message 会说明 token 无法解析。	All public endpoints	Correct 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 `invalid_request_error`	`invalid_request_error` `PIN cannot be part of the cardholder phone number.`	Set or Reset Virtual Card PIN `POST /v1/issuing/cards/manage/pin` operationId: `manage-card-pin`	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 `invalid_request_error`	`invalid_request_error` `PIN cannot contain the same digit repeated.`	Set or Reset Virtual Card PIN `POST /v1/issuing/cards/manage/pin` operationId: `manage-card-pin`	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 `invalid_request_error`	`invalid_request_error` `PIN cannot match the last four digits of the card.`	Set or Reset Virtual Card PIN `POST /v1/issuing/cards/manage/pin` operationId: `manage-card-pin`	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 `invalid_request_error`	`invalid_request_error` `PIN length is invalid.`	Set or Reset Virtual Card PIN `POST /v1/issuing/cards/manage/pin` operationId: `manage-card-pin`	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 `invalid_request_error`	`invalid_request_error` `PIN must contain digits only.`	Set or Reset Virtual Card PIN `POST /v1/issuing/cards/manage/pin` operationId: `manage-card-pin`	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 `invalid_request_error`	`invalid_request_error` `SA_TO_HA feature unavailable`	Create Issuing Transfer `POST /v1/issuing/transfers` operationId: `create-issuing-transfer`	Correct the request Retry only after the condition identified by the message has been resolved. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry only when the returned condition has been resolved and the operation permits it.
400 `invalid_request_error`	`invalid_request_error` `The current card requires an Card SKU number.`	Assign Card `POST /v1/issuing/cards/assign` operationId: `assign-card`	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 `invalid_request_error`	`invalid_request_error` `This card does not support PIN management.`	Set or Reset Virtual Card PIN `POST /v1/issuing/cards/manage/pin` operationId: `manage-card-pin`	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 `invalid_request_error`	`invalid_request_error` `This operation cannot be performed on One-Time Card.`	Assign Card `POST /v1/issuing/cards/assign` operationId: `assign-card`	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 `invalid_request_error`	`invalid_request_error` `a release request for this original transaction is already in progress`	Claim Unsolicited Refund `POST /v1/issuing/transactions/unsolicited_refund/release` operationId: `claim-unsolicited-refund`	Wait and retry Wait for the current operation or resource state to change, then retry. View details Why this happened: The related request or resource is still being processed. Retry: Wait for the operation or state change before retrying; do not poll rapidly.
400 `invalid_request_error`	`invalid_request_error` `account balance is less than total amount`	Assign Card `POST /v1/issuing/cards/assign` operationId: `assign-card`	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 `invalid_request_error`	`invalid_request_error` `account balance is not active`	Assign Card `POST /v1/issuing/cards/assign` operationId: `assign-card`	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 `invalid_request_error`	`invalid_request_error` `account balance status is not available`	Assign Card `POST /v1/issuing/cards/assign` operationId: `assign-card`	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 `invalid_request_error`	`invalid_request_error` `assign country unsupported for card product`	Assign Card `POST /v1/issuing/cards/assign` operationId: `assign-card`	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 `invalid_request_error`	`invalid_request_error` `card currency is not supported`	Assign Card `POST /v1/issuing/cards/assign` operationId: `assign-card`	Correct the request Retry only after the condition identified by the message has been resolved. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry only when the returned condition has been resolved and the operation permits it.
400 `invalid_request_error`	`invalid_request_error` `card form err`	Assign Card `POST /v1/issuing/cards/assign` operationId: `assign-card`	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 `invalid_request_error`	`invalid_request_error` `card has already been reserved`	Assign Card `POST /v1/issuing/cards/assign` operationId: `assign-card`	Correct the request Retry only after the condition identified by the message has been resolved. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry only when the returned condition has been resolved and the operation permits it.
400 `invalid_request_error`	`invalid_request_error` `card not available for this account`	Assign Card `POST /v1/issuing/cards/assign` operationId: `assign-card`	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 `invalid_request_error`	`invalid_request_error` `card number expired`	Assign Card `POST /v1/issuing/cards/assign` operationId: `assign-card`	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 `invalid_request_error`	`invalid_request_error` `card number not exist`	Assign Card `POST /v1/issuing/cards/assign` operationId: `assign-card`	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 `invalid_request_error`	`invalid_request_error` `card_art_id cannot be empty`	Set Default Card Art `POST /v1/issuing/cards/arts/default` operationId: `set-default-card-art`	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 `invalid_request_error`	`invalid_request_error` Message pattern `destination account[{destination_account_id}] not found`	Create Issuing Transfer `POST /v1/issuing/transfers` operationId: `create-issuing-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 `invalid_request_error`	`invalid_request_error` `display_name or merchant_code cannot be empty`	List Merchant Brands `GET /v1/issuing/merchant_brands` operationId: `list-merchant-brands`	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 `invalid_request_error`	`invalid_request_error` `field [page_size] exceeds the maximum length of 100`	List Issuing Balances `GET /v1/issuing/balances` operationId: `list-issuing-balances`	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 `invalid_request_error`	`invalid_request_error` `field [page_size] is shorter than the minimum length of 10`	List Issuing Balances `GET /v1/issuing/balances` operationId: `list-issuing-balances`	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 `invalid_request_error`	`invalid_request_error` `inconsistent formats between start time and end time`	Create Report `POST /v1/issuing/reports` operationId: `create-report`	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 `invalid_request_error`	`invalid_request_error` `insufficient account balance`	Create Issuing Transfer `POST /v1/issuing/transfers` operationId: `create-issuing-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 `invalid_request_error`	`invalid_request_error` `invalid JSON request body`	Reset Card PIN `POST /v1/issuing/cards/pin` operationId: `reset-pin`	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 `invalid_request_error`	`invalid_request_error` `invalid card metadata`	Assign Card `POST /v1/issuing/cards/assign` operationId: `assign-card`	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 `invalid_request_error`	`invalid_request_error` `invalid card number`	Assign Card `POST /v1/issuing/cards/assign` operationId: `assign-card`	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 `invalid_request_error`	`invalid_request_error` `invalid card number format`	Assign Card `POST /v1/issuing/cards/assign` operationId: `assign-card`	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 `invalid_request_error`	`invalid_request_error` `invalid card number format`	Assign Card `POST /v1/issuing/cards/assign` operationId: `assign-card`	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 `invalid_request_error`	`invalid_request_error` `invalid card_id format`	Create PAN Token `POST /v1/issuing/cards/{id}/token` operationId: `create-pan-token`	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 `invalid_request_error`	`invalid_request_error` `invalid cardholder id`	Assign Card `POST /v1/issuing/cards/assign` operationId: `assign-card`	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 `invalid_request_error`	`invalid_request_error` `invalid character …`	Applies to 35 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 `invalid_request_error`	`invalid_request_error` `invalid end time:…`	Create Report `POST /v1/issuing/reports` operationId: `create-report`	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 `invalid_request_error`	`invalid_request_error` Message pattern `invalid merchant_code: {merchant_code}`	Create Card `POST /v1/issuing/cards` operationId: `create-card` Update Card `POST /v1/issuing/cards/{id}` operationId: `update-card`	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 `invalid_request_error`	`invalid_request_error` `invalid spending control amount due to negative amount or invalid logical relationships`	Create Card `POST /v1/issuing/cards` operationId: `create-card`	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 `invalid_request_error`	`invalid_request_error` `invalid start time:…`	Create Report `POST /v1/issuing/reports` operationId: `create-report`	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 `invalid_request_error`	`invalid_request_error` `invalid time format`	List Cards Transactions `GET /v1/issuing/transactions` operationId: `list-cards-transactions` List Issuing Balances Transactions `GET /v1/issuing/balances/transactions` operationId: `list-issuing-balances-transactions`	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 `invalid_request_error`	`invalid_request_error` `invalid token format`	All public endpoints	Correct 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 `invalid_request_error`	`invalid_request_error` `invalid transfer between two sub accounts`	Create Issuing Transfer `POST /v1/issuing/transfers` operationId: `create-issuing-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 `invalid_request_error`	`invalid_request_error` `invalid usage type`	Create Card `POST /v1/issuing/cards` operationId: `create-card`	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 `invalid_request_error`	`invalid_request_error` Message pattern `merchant rule is incomplete: {merchant_code}`	Create Card `POST /v1/issuing/cards` operationId: `create-card` Update Card `POST /v1/issuing/cards/{id}` operationId: `update-card`	Contact UQPAY Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: UQPAY must check an account configuration, quota, or service-side condition. Retry: Retry after correcting the request or resource state. 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, merchant_code.
400 `invalid_request_error`	`invalid_request_error` Message pattern `merchant_code cannot be empty at index {index}`	Create Card `POST /v1/issuing/cards` operationId: `create-card` Update Card `POST /v1/issuing/cards/{id}` operationId: `update-card`	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 `invalid_request_error`	`invalid_request_error` `missing authentication token`	All public endpoints	Correct 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 `invalid_request_error`	`invalid_request_error` `missing card_product_id`	List Card Arts `GET /v1/issuing/cards/arts` operationId: `list-card-arts`	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 `invalid_request_error`	`invalid_request_error` Message pattern `missing field: [{field}]`	Applies to 11 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 `invalid_request_error`	`invalid_request_error` `negative amount after fee deduction`	Create Issuing Transfer `POST /v1/issuing/transfers` operationId: `create-issuing-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 `invalid_request_error`	`invalid_request_error` `no unsolicited refund intercept transaction found to claim`	Claim Unsolicited Refund `POST /v1/issuing/transactions/unsolicited_refund/release` operationId: `claim-unsolicited-refund`	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 `invalid_request_error`	`invalid_request_error` `old_pin is only allowed for UPDATE`	Reset Card PIN `POST /v1/issuing/cards/pin` operationId: `reset-pin`	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 `invalid_request_error`	`invalid_request_error` `old_pin is required`	Set or Reset Virtual Card PIN `POST /v1/issuing/cards/manage/pin` operationId: `manage-card-pin`	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 `invalid_request_error`	`invalid_request_error` `old_pin is required for UPDATE`	Reset Card PIN `POST /v1/issuing/cards/pin` operationId: `reset-pin`	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 `invalid_request_error`	`invalid_request_error` Message pattern `old_pin must contain exactly {expected_length} digits`	Reset Card PIN `POST /v1/issuing/cards/pin` operationId: `reset-pin`	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 `invalid_request_error`	`invalid_request_error` `one-time card limit must be greater than 0`	Create Card `POST /v1/issuing/cards` operationId: `create-card`	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 `invalid_request_error`	`invalid_request_error` `only one of allowed_merchants or blocked_merchants can be set`	Create Card `POST /v1/issuing/cards` operationId: `create-card` Update Card `POST /v1/issuing/cards/{id}` operationId: `update-card`	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 `invalid_request_error`	`invalid_request_error` `original transaction is not a valid authorization source transaction`	Claim Unsolicited Refund `POST /v1/issuing/transactions/unsolicited_refund/release` operationId: `claim-unsolicited-refund`	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 `invalid_request_error`	`invalid_request_error` `original transaction not found or not owned by current account`	Claim Unsolicited Refund `POST /v1/issuing/transactions/unsolicited_refund/release` operationId: `claim-unsolicited-refund`	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 `invalid_request_error`	`invalid_request_error` `permission denied on the connected account`	Create Issuing Transfer `POST /v1/issuing/transfers` operationId: `create-issuing-transfer`	Correct the request Retry only after the condition identified by the message has been resolved. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry only when the returned condition has been resolved and the operation permits it.
400 `invalid_request_error`	`invalid_request_error` `physical card creation not allowed`	Assign Card `POST /v1/issuing/cards/assign` operationId: `assign-card`	Correct the request Retry only after the condition identified by the message has been resolved. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry only when the returned condition has been resolved and the operation permits it.
400 `invalid_request_error`	`invalid_request_error` `pin cannot be part of the cardholder phone number`	Reset Card PIN `POST /v1/issuing/cards/pin` operationId: `reset-pin`	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 `invalid_request_error`	`invalid_request_error` `pin cannot contain the same digit repeated`	Reset Card PIN `POST /v1/issuing/cards/pin` operationId: `reset-pin`	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 `invalid_request_error`	`invalid_request_error` `pin cannot match the last four digits of the card`	Reset Card PIN `POST /v1/issuing/cards/pin` operationId: `reset-pin`	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 `invalid_request_error`	`invalid_request_error` Message pattern `pin must contain exactly {expected_length} digits`	Reset Card PIN `POST /v1/issuing/cards/pin` operationId: `reset-pin`	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 `invalid_request_error`	`invalid_request_error` `pin must differ from old_pin`	Reset Card PIN `POST /v1/issuing/cards/pin` operationId: `reset-pin`	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 `invalid_request_error`	`invalid_request_error` `pin must differ from old_pin.`	Set or Reset Virtual Card PIN `POST /v1/issuing/cards/manage/pin` operationId: `manage-card-pin`	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 `invalid_request_error`	`invalid_request_error` `product not found`	Assign Card `POST /v1/issuing/cards/assign` operationId: `assign-card`	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 `invalid_request_error`	`invalid_request_error` `products not found`	Assign Card `POST /v1/issuing/cards/assign` operationId: `assign-card`	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 `invalid_request_error`	`invalid_request_error` `report has expired`	Download Report `GET /v1/issuing/reports/{id}` operationId: `download-report-file`	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 `invalid_request_error`	`invalid_request_error` Message pattern `report[{report_id}] not found`	Download Report `GET /v1/issuing/reports/{id}` operationId: `download-report-file`	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 `invalid_request_error`	`invalid_request_error` `required valid email address`	Update Cardholder `POST /v1/issuing/cardholders/{id}` operationId: `update-cardholder`	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 `invalid_request_error`	`invalid_request_error` `risk control setting is not allowed`	Create Card `POST /v1/issuing/cards` operationId: `create-card`	Correct the request Retry only after the condition identified by the message has been resolved. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry only when the returned condition has been resolved and the operation permits it.
400 `invalid_request_error`	`invalid_request_error` Message pattern `source account[{source_account_id}] not found`	Create Issuing Transfer `POST /v1/issuing/transfers` operationId: `create-issuing-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 `invalid_request_error`	`invalid_request_error` `start time is later than end time`	Create Report `POST /v1/issuing/reports` operationId: `create-report`	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 `invalid_request_error`	`invalid_request_error` `the card does not exist or has already been assigned`	Assign Card `POST /v1/issuing/cards/assign` operationId: `assign-card`	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 `invalid_request_error`	`invalid_request_error` `the provided transfer id does not belong to the connected account`	Retrieve Issuing Transfer `GET /v1/issuing/transfers/{id}` operationId: `retrieve-issuing-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 `invalid_request_error`	`invalid_request_error` Message pattern `transaction[{transaction_id}] not found under the connected account`	Retrieve Cards Transaction `GET /v1/issuing/transactions/{id}` operationId: `retrieve-cards-transaction`	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. When to contact UQPAY: Contact UQPAY if the same error persists after the recommended action and limited retries. Also provide: transaction ID. Related endpoints: List Cards Transactions
400 `invalid_request_error`	`invalid_request_error` Message pattern `transfer[{transfer_id}] not found`	Retrieve Issuing Transfer `GET /v1/issuing/transfers/{id}` operationId: `retrieve-issuing-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 `invalid_request_error`	`invalid_request_error` `type must be 0, 1 or 2`	Reset Card PIN `POST /v1/issuing/cards/pin` operationId: `reset-pin`	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 `invalid_request_error`	`invalid_request_error` `type must be SET or RESET`	Set or Reset Virtual Card PIN `POST /v1/issuing/cards/manage/pin` operationId: `manage-card-pin`	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 `invalid_request_error`	`invalid_request_error` `unknown report type: UNKNOWN`	Create Report `POST /v1/issuing/reports` operationId: `create-report`	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 `invalid_request_error`	`invalid_request_error` `unsolicited refund claim only supported on VISA`	Claim Unsolicited Refund `POST /v1/issuing/transactions/unsolicited_refund/release` operationId: `claim-unsolicited-refund`	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.
401 `unauthorized_error`	`unauthorized_error` `auth url not config`	Applies to 35 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.
401 `unauthorized_error`	`unauthorized_error` `create request failed`	Applies to 35 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.
401 `unauthorized_error`	`unauthorized_error` `internal configconfig error`	Applies to 35 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.
401 `unauthorized_error`	`unauthorized_error` `ip not allowed`	Applies to 35 public endpoints	Contact UQPAY Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: UQPAY must check an account configuration, quota, or service-side condition. Retry: Retry after correcting the request or resource state. 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, complete error response, request egress IP.
401 `unauthorized_error`	`unauthorized_error` `marshal request failed`	Applies to 35 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.
401 `unauthorized_error`	`unauthorized_error` `request failed`	Applies to 35 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.
401 `unauthorized_error`	`unauthorized_error` `token has expired`	All public endpoints	Authenticate again Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The access token is missing, expired, or invalid. Retry: Retry after correcting the request or resource state.
403 `unauthorized_error`	`forbidden` `forbidden`	Retrieve Sensitive Card Details `GET /v1/issuing/cards/{id}/secure` operationId: `retrieve-card-secure`	Contact UQPAY Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: UQPAY must check an account configuration, quota, or service-side condition. Retry: Retry after correcting the request or resource state. 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, complete error response.
404 `card_error`	`card_not_found` `card not found or deactivated`	Reset Card PIN `POST /v1/issuing/cards/pin` operationId: `reset-pin`	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.
409 `card_error`	`card_expired_error` `card has expired`	Reset Card PIN `POST /v1/issuing/cards/pin` operationId: `reset-pin`	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.
409 `card_error`	`status_not_supported` `card status or activation status not supported by request`	Reset Card PIN `POST /v1/issuing/cards/pin` operationId: `reset-pin`	Wait and retry Wait for the current operation or resource state to change, then retry. View details Why this happened: The related request or resource is still being processed. Retry: Wait for the operation or state change before retrying; do not poll rapidly.
409 `idempotency_error`	`idempotency_key_mismatch` `idempotency key was already used with a different request`	Reset Card PIN `POST /v1/issuing/cards/pin` operationId: `reset-pin`	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.
409 `idempotency_error`	`request_being_processed` `request is being processed`	Reset Card PIN `POST /v1/issuing/cards/pin` operationId: `reset-pin`	Wait and retry Wait for the current operation or resource state to change, then retry. View details Why this happened: The related request or resource is still being processed. Retry: Wait for the operation or state change before retrying; do not poll rapidly.
409 `invalid_request_error`	`pin_operation_processing` `A PIN operation for this card is already processing.`	Reset Card PIN `POST /v1/issuing/cards/pin` operationId: `reset-pin`	Wait and retry Wait for the current operation or resource state to change, then retry. View details Why this happened: The related request or resource is still being processed. Retry: Wait for the operation or state change before retrying; do not poll rapidly.
422 `invalid_request_error`	`pin_operation_not_supported` `This card does not support the requested PIN operation.`	Reset Card PIN `POST /v1/issuing/cards/pin` operationId: `reset-pin`	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.
429 Legacy flat	`429` `Request is too frequent`	Create PAN Token `POST /v1/issuing/cards/{id}/token` operationId: `create-pan-token` Elevate Per-Transaction Limit `POST /v1/issuing/cards/{id}/elevate_limit` operationId: `elevate-card-limit`	Wait and retry Stop frequent retries. Wait briefly, then retry with exponential backoff. View details Why this happened: The related request or resource is still being processed. Retry: Retry with exponential backoff; stop and contact UQPAY if the error persists. When to contact UQPAY: Contact UQPAY if the same error persists after the recommended action and limited retries. Also provide: card ID, actual request rate.
500 `api_error`	`api_error` `api service error`	Applies to 31 public endpoints	Contact UQPAY Stop frequent retries. Wait briefly, then retry with exponential backoff. View details Why this happened: UQPAY must check an account configuration, quota, or service-side condition. Retry: Retry with exponential backoff; stop and contact UQPAY if the error persists. 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, complete error response.
503 `idempotency_error`	`idempotency_unavailable` `Idempotency protection is temporarily unavailable`	Reset Card PIN `POST /v1/issuing/cards/pin` operationId: `reset-pin`	Wait and retry Wait for the current operation or resource state to change, then retry. View details Why this happened: The related request or resource is still being processed. Retry: Wait for the operation or state change before retrying; do not poll rapidly. 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, complete error response.

Getting Started

Cardholders

Cards

Funding

Controls & Security

Integration

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