Approved
Transaction authorised successfully and funds reserved.
推薦行動: Proceed with settlement and fulfilment.
Visa、Mastercard 和發卡銀行使用的 ISO 8583 授權回應碼。按代碼、名稱或意思搜尋,以了解交易被批准、拒絕或轉介的原因。
顯示 30 個(共 30 個)代碼
Transaction authorised successfully and funds reserved.
推薦行動: Proceed with settlement and fulfilment.
Generic issuer decline, often triggered by risk rules.
推薦行動: Retry once through an alternative acquirer or after 3D Secure authentication.
The available balance or credit limit is too low.
推薦行動: Retry after a short delay or prompt the customer to use another card.
The transaction exceeds the cardholder's daily or per-transaction limit.
推薦行動: Retry with a lower amount or prompt the customer for a different card.
The issuer or scheme switch could not be reached.
推薦行動: Retry through a backup acquirer or after a short delay.
Issuer suspects the card is lost, stolen or compromised.
推薦行動: Do not retry; void the order and ask for a different payment method.
The card number failed the Luhn check or does not exist.
推薦行動: Ask the customer to re-enter their card details; do not retry the same number.
The cardholder has reported the card as lost.
推薦行動: Do not retry; void the order and request a new payment method.
The cardholder has reported the card as stolen.
推薦行動: Do not retry; flag the transaction and request a new payment method.
The card has passed its expiry date.
推薦行動: Ask the customer to update their expiry date or use a different card.
The card product does not allow this transaction type.
推薦行動: Do not retry; ask for an alternative payment method.
The issuer's fraud system has flagged the transaction.
推薦行動: Do not retry; request an alternative payment method and review the order.
The card has restrictions that block the transaction.
推薦行動: Do not retry; ask the customer to use another card.
The account has not been activated or is not yet usable.
推薦行動: Do not retry; ask the customer to activate their account or use another card.
The card verification value does not match issuer records.
推薦行動: Ask the customer to re-enter the CVV; do not retry if repeated.
The cardholder has requested that recurring payments be stopped.
推薦行動: Cancel the subscription or recurring agreement; do not retry.
The CVV is invalid or missing for a card-not-present transaction.
推薦行動: Ask the customer to provide the correct CVV and retry once.
PSD2 requires the transaction to be authenticated.
推薦行動: Restart the flow with 3D Secure step-up authentication.
Issuer wants additional verification before approving.
推薦行動: Ask the customer to contact their issuer, or retry with voice authorisation if available.
Issuer requires special conditions to be met.
推薦行動: Contact the issuer for guidance before reattempting.
The merchant ID, terminal ID or service is not recognised.
推薦行動: Check acquiring configuration and retry; do not retry if the MID is suspended.
Technical error at the issuer or scheme level.
推薦行動: Retry after a short delay; escalate if the error persists.
The transaction type or data format is not valid.
推薦行動: Check request fields and retry with corrected data.
The amount is malformed, zero, or outside allowed limits.
推薦行動: Verify the amount, currency and decimals, then retry.
The issuer did not receive the transaction cleanly.
推薦行動: Retry the transaction without changing the data.
The merchant terminal or MID is not configured for this transaction.
推薦行動: Check MID configuration and routing rules before retrying.
A security check on the transaction data failed.
推薦行動: Review authentication data and retry with corrected security fields.
The issuer did not respond within the allowed time.
推薦行動: Perform a reversal check, then retry the transaction.
The transaction could not be routed to the correct destination.
推薦行動: Check routing configuration and retry.
A system error occurred at the issuer, acquirer or scheme.
推薦行動: Retry after a short delay; contact support if the error persists.
Cardflo's orchestration layer inspects the raw response code from every processor, applies scheme-specific mapping, and feeds the outcome into intelligent routing and retry logic. Soft declines are retried through alternative acquirers or after customer prompts, while hard declines are suppressed so merchants avoid excessive-authorisation fees and protect their MID standing.