The purpose of this guide is to help Issuers, Acquirers and Merchants utilize authorization response codes appropriately in order to improve the payments ecosystem by increasing better transparency when an authorization is declined and reducing unnecessary reattempted transactions. Authorization processing requires a careful balance between participants and ensuring appropriate information flow is critical to creating optimal behavior for all players within the ecosystem.
Action Codes - General Guide
| Code | Description | Practical Definition | What you should do |
| 00 | Approved and completed successfully | ||
| 01 | Refer to Card Issuer | The issuing bank (Visa, Mastercard, etc.) prevented the transaction | Ask for a separate card to complete the transaction and/or ask the customer to call their credit card bank and figure out why the transaction was declined. |
| 02 | Refer to card issuer, special condition | Just like 01, the issuing bank (Visa, Mastercard, etc.) prevented the transaction. | Same as 01 - Ask for a separate card to complete the transaction and/or ask the customer to call their credit card bank and figure out why the transaction was declined. |
| 03 | Invalid merchant | ||
| 04 | Pick up card (no fraud) | The issuing bank (Visa, Mastercard, etc.) prevented the transaction. | Same as the first two codes - Ask for a separate card to complete the transaction and/or ask the customer to call their credit card bank and figure out why the transaction was declined. |
| 05 | Do not honor. | The issuing bank (Visa, Mastercard, etc.) prevented the transaction and is also telling you not to honor the card. | Ask for a separate card to complete the transaction and/or ask the customer to call their credit card bank and figure out why the transaction was declined. |
| 07 | Pick up card, special condition (fraud account) | The issuing bank (Visa, Mastercard, etc.) prevented the transaction because it has flagged this account as fraudulent. | If it’s for a one-time transaction, do not run the card again, and don’t provide any more goods or services for the cardholder. If it was a recurring or scheduled transaction, follow up with your customer to make sure your business wasn’t incorrectly flagged as fraudulent. Ask that they follow up with their bank OR update their account with a newly provided card. |
| 12 | Invalid transaction | The transaction is not authorized due to critical technical issues or restrictive card usage by the Issuer. | Transaction should never be reattempted. |
| 13 | Invalid amount or currency conversion field overflow | The number field you attempted to transact was invalid. This usually is the result of a typo (negative amount or ineligible symbol). | Double check what you entered and make sure it wasn’t negative or included incorrect symbols. |
| 14 | Invalid account number (no such number) | The card number is invalid, and your terminal is having trouble finding the relevant account. | Double check the account number given & try again. |
| 15 | No such issuer | The card number entered is wrong since it doesn’t start with a 3 (AMEX), 4 (Visa), 5 (MasterCard) or 6 (Discover). | Double check the card number entered. |
| 19 | Re-enter transaction | An unknown error occurred. | Try it again, and if it continues, contact your merchant provider. |
| 28 | File temporarily not available for update or inquiry | A temporary error occurred during the authorization process. | Try it again, and if the problem continues, contact your merchant provider. |
| 41 | Lost card, pick up (fraud account) | The right owner has reported this card as lost or stolen, and the issuing bank has denied the transaction as a result. | Don’t try the transaction again and do not provide any additional goods or services to the card holder. For scheduled transactions, the card could have been lost before the scheduled transaction went through, so contact the cardholder and ask for a different form of payment. |
| 43 | Stolen card, pick up (fraud account) | The right owner has reported this card as lost or stolen, and the issuing bank has denied the transaction as a result. | Don’t try the transaction again and do not provide any additional goods or services to the card holder. Make sure you report the transaction attempt to the relevant issuing bank. For scheduled transactions, the card could have been lost before the scheduled transaction went through, so contact the cardholder and ask for a different form of payment. |
| 51 | Not sufficient funds | The customer’s issuing bank has denied the transaction because either the customer is already over their credit limit or that transaction will put the customer’s credit card over the limit. | Either ask the customer to call their issuing bank and request a credit limit or request a different form of payment. |
| 54 | Expired card or expiration date is missing | The expiration date entered is in the past. | Double check you entered it correctly, ask the customer to confirm the expiration date with their issuing bank, or request an alternate payment method. |
| 57 | Transaction not permitted to cardholder | This code will appear if you are attempting a transaction and your customer’s card is not configured for that type of transaction. | Have your customer call their issuing bank (the number is typically printed on the back of the credit card) and ask that the transaction be permitted. When the bank confirms it will process correctly, attempt the transaction again. |
| 59 | Suspected fraud | ||
| 61 | Exceeds approval amount limit | ||
| 62 | Restricted card (card invalid in this region or country) | This means one of two things: You’re attempting to transact an AmEx card or a Discover transaction and your system doesn’t support them. A customer tried to pay online with a card that doesn’t support online payments. A customer tried to pay online with a card that doesn’t support online payments. | For the first reason, call your merchant provider and make sure your terminal/POS supports American Express or Discover transactions. For online payment errors, let your customer know they can pay in person or to pay with a different card when using the online portal. |
| 63 | Security violation (source is not correct issuer) | The three-digit CVV2 or four-digit CID code on the back of the credit card wasn’t read correctly. | Attempt the transaction again without entering a CVV2/CID number. It should process normally. Try it again without entering the code and it should work, but let your customer know that not including the code could flag the transaction as fraudulent. |
| 65 | Activity Limit Exceeded | Your customer is over their credit limit or this transaction would put them over it. | Have them use a different transaction method or have them call and request a credit limit adjustment. |
| 85 | No reason to decline a request for address verification, CVV2 verification, or a credit voucher or merchandise return | There’s no apparent problem, but something still went wrong. This error is sort of a catch-all. | Try it again. If the transaction still won’t go through, contact your payment processor. |
| 91 | Issuer or switch inoperative and STIP not applicable or not available for this transaction; Time-out when no stand-in; POS Check Service: Destination unavailable; Credit Voucher and Merchandise Return Authorizations: V.I.P. sent the transaction to the issuer, but the issuer was unavailable. | The authorization communication failed for no specific reason. | Try it again. If the transaction still won’t go through, contact your payment processor or the relevant issuing bank. |
| 93 | Transaction cannot be completed - violation of law | There’s a violation on the customer account, and the issuing bank has prevented the transaction. | Ask your customer to call their bank, and if the bank confirms everything is okay on their end, attempt the transaction again. Otherwise, just ask for a different card or payment method. |
| 94 | Duplicate transmission. Transaction submitted containing values in tracing data fields that duplicate values in a previously submitted transaction. Note: This code is available in SMS raw data in case of duplicate transmission. | ||
| 96 | System malfunction or certain field error conditions | A temporary error occurred during the transaction. | Wait a minute or two and try again. Contact your payment processor if it still didn’t work. |
| B2 | Surcharge amount not supported by debit network issuer. | ||
| Q1 | Card Authentication failed | ||
| R0 | Customer requested stop of specific recurring payment | Your customer asked their bank to deny charges from your account. | Stop the recurring payments immediately. Then follow up with the customer to see if the request to stop payment was a mistake. |
Related pages: