Not all Scheme mandated codes have corresponding ledger’s response because authorisation requests are sent to the ledger via the Authorisation Request API interface only when Enfuce has validated and approved them. Hence, some of them might have been declined by us. For example, if the cardholder has entered the wrong CVC, Enfuce declines the request and returns N7 to the scheme.
Response Codes
The following table lists the scheme mandated codes:| Scheme Response Code | Ledger’s Response | Description | Use Case |
|---|---|---|---|
| Approvals | |||
| 00 | APPROVED | Approved/Successfully Completed | A customer makes a successful purchase using their card. The transaction is successfully approved for the requested amount. |
| 08 | Honor with ID | ||
| 10 | PARTIALLY_APPROVED | Partial Approval | A cardholder uses their card at an automatic fuel pump, but due to a spend limit, only part of the requested amount is approved. The full amount cannot be approved due to insufficient funds or spending limits. Instead, a partial approval is granted. Only applicable if a merchant indicates that it accepts partial approvals. |
| 85 | Not Declined (Mastercard Only):
| A card verification request is processed successfully without fund hold. Zero amount authorisation request validates the card number without holding funds. Approval or ‘no reason to decline’ may be returned. | |
| 87 | Purchase Amount Only (no cashback) | ||
| Declines | |||
| 03 | Invalid Merchant | The purchase is declined as the merchant is not allowed by the issuer. Indicates that the purchases at this merchant (MID) or merchant category (MCC) are not allowed. | |
| 04 | Pick Up Card | A cardholder tries to use a card that has been reported as fraudulently used — card status is either BLOCKED_SUSPECTED_FRAUD or CLOSED_DUE_TO_FRAUD. | |
| 05 | DO_NOT_HONOR | Generic decline reasons, such as, address verification failure; audit entry error; CVV/ICVV/AAV/CAVV failure; Visa ARQC failure; Mastercard CVV2 failure, etc. | |
| 12 | Invalid Transaction — InvalidStatusException for a non-terminal invalid status and Account Funding Transactions (AFT) business rules. | ||
| 13 | Invalid Amount | A cardholder accidentally enters an incorrect card number during an online purchase or fraudulent attempts are made to guess valid card numbers. The transaction amount is not valid for processing. | |
| 14 | Invalid Account Number; the card could not be found or the card validity has expired. | ||
| 15 | Invalid Issuer | ||
| 30 | Format Error — the authorisation message does not comply with format requirements (ISO 8583); the field that does not comply with the requirements is specified in the response. | ||
| 32 | Partial Reversal (0400 messages only) | ||
| 41 | Lost Card | A card reported as lost is used for a transaction and gets declined due to security measures. | |
| 43 | Stolen Card | A fraudster attempts to use a stolen card but it is already reported and declined. | |
| 46 | Closed Account — an authorisation request is declined when the card status is CLOSED; however, the same response is returned when the card status is ACTIVE/BLOCKED, yet the card version status is CLOSED. | ||
| 51 | NOT_SUFFICIENT_FUNDS | Not Sufficient Funds | A cardholder attempts to purchase an item but does not have enough funds available. |
| 54 | Expired Cards | A cardholder tries to make a payment using an expired card — the card status is CLOSED/CLOSED_DUE_TO_FRAUD/CLOSED_LOST/CLOSED_STOLEN/CLOSED_EXPIRED and the card version status is CLOSED. | |
| 55 | Incorrect PIN or Missing — offline PIN check failed or crypto PIN verification failed. | ||
| 57 | Transaction Not Permitted For Cardholder:
| ||
| 58 | Transaction Not Permitted for Acquirer (Mastercard Only) | A merchant category is restricted from accepting transactions from a particular card type. May be used in the case of Mastercard fallback transactions. The transaction is declined when the card does not allow the specified transaction type or if the type is unrecognized. Used when POS Entry Mode or terminal capability mismatches the transaction type as per issuer policy. | |
| 59 | Suspected Fraud (Visa Only) | A high-value purchase triggers the fraud detection system and the transaction is blocked. | |
| 61 | EXCEEDS_WITHDRAWAL_LIMIT | Exceeds Withdrawal Amount Limit; declined as it failed to comply with a spend control rule (LIMIT classifier) or the ledger has confirmed that the cardholder is exceeding the withdrawal amount limit | A cardholder tries to withdraw more money from an ATM than their daily limit allows. The transaction exceeds the allowed spending limit. |
| 62 | RESTRICTED_CARD | Restricted Card:
| |
| 63 | Security Violation (Mastercard Only) | ||
| 65 | EXCEEDS_WITHDRAWAL_FREQUENCY_LIMIT | Exceeds Withdrawal Frequency Limit:
| A cardholder attempts multiple contactless Mastercard transactions without PIN verification. A Mastercard cardholder inserts their card into a chip terminal, but the terminal does not prompt for a PIN when it should. A transaction may be declined if a spend control or contactless counter restricts usage or if authentication, such as 3D Secure (3DS) or PIN, is required. If PSD2 Strong Customer Authentication (SCA) applies and was not used, retry the transaction with 3DS. |
| 70 | PIN Data Required:
| A cardholder attempts multiple contactless Visa transactions without PIN verification. A Visa cardholder inserts their chip card into a terminal, but the terminal fails to prompt for a PIN when required. This is a Visa-specific code used when a contactless transaction is declined due to a usage counter limit and/or required PIN data is not included in the authorization request. | |
| 71 | PIN Not Changed | The cardholder attempted to change their card PIN, but the PIN change was not completed. The PIN change transaction is declined, as the PIN is not updated. | |
| 72 | Account Not Yet Activated — the card status is ACTIVE and the card version status is INITIAL | A cardholder attempts to use a new card that has not yet been activated. Effective June 3, 2025: Mastercard code for payment declined due to the account not being activated (e.g., newly issued card). | |
| 75 | Allowable PIN Tries Exceeded — PIN counter check failed | A cardholder enters their PIN incorrectly multiple times, locking the card. The cardholder has exceeded the maximum allowed PIN attempts. | |
| 76 | Invalid to Account | ||
| 77 | Invalid From Account | ||
| 78 | Invalid Account | A cardholder tries to use a blocked credit card, and the authorisation request is rejected. The authorisation request is declined due to issuer or customer-set rules. This also applies when a Visa card or account is blocked for reasons not related to fraud. Additionally, it is used for declines related to the reminder process on a credit product. | |
| 83 | Fraud Security; Declines Mastercard Only | ||
| 84 | Invalid Authorization Lifecycle | ||
| 86 | PIN Validation Not Possible | A cardholder attempts a cash withdrawal, but the PIN validation system is unavailable. The transaction is declined, during the STIP mode, when PIN validation fails or cannot be completed by the card Scheme. | |
| 88 | Cryptographic Failure — Authorisation Request Cryptogram (ARQC) verification failure (Mastercard Only) | ||
| 89 | Unacceptable PIN — Weak PIN check failure when PIN is set or changed | ||
| 91 | SYSTEM_ERROR | Issuer Unresponsive — ledger connection failure or ledger returned SYSTEM_ERROR to the request sent via the Authorisation Request API endpoint | A transaction fails because the issuer’s system is temporarily offline. The external ledger is unavailable to process the authorisation request. Mastercard invokes the STIP mode; Visa does not initiate the STIP mode, unless the N0 response code is used. |
| 92 | Unable to Route Transaction | ||
| 93 | Violation of Law (Visa Only) | A cardholder is blocked from online transactions due to legal or compliance rules. Used for regulatory blocks, for example, gambling, non-opt-in CNP, or missing second-factor authorisation for domestic e-commerce. | |
| 94 | Duplicate Transmission Detected | A repeated authorisation request is declined as a duplicate. A merchant resends an authorisation request that was already processed. | |
| 96 | System Error | A transaction fails due to internal processing error. A system issue prevents payments processing or exceeds the Scheme response time limits. | |
| N7 | CVV2 Failure (Visa Only) | A Visa cardholder has entered the wrong CVC number. A Visa authorization request did not pass CVV2 (Card Verification Value) verification. It is usually used in Card-Not-Present transactions, when the CVV2 provided by the cardholder does not match with the issuer’s records. Do not use this code if the CVV2 was not provided. It applies only when a CVV2 is present, but fails verification. | |
| 5C | Transaction Not Supported (Visa Only):
| A Visa issuer blocks a transaction, as it is not supported as per internal policy. Applicable only for Visa transactions — transaction not permitted to the cardholder, can be used as an alternative to 57. | |
| 1A | Additional Customer Authentication Required (Visa Only):
| A customer tries to complete an online purchase without passing 3D Secure authentication. Authentication is required. If the transaction falls under PSD2 regulations and was not processed through 3D Secure, retry with 3D Secure. (Applicable only in the European region.) | |
| Z5 | Account Verification Amount Exceeded (Visa Only) — amount verification check failed (account verification beyond the allowed limit); an authorisation ID is still generated |