Understanding Your Credit Card Decline Codes

Key Takeaways:

Decline Code Definition: A credit card decline code is an alphanumeric response that explains why a transaction was not authorized. Merchants can use the code to determine whether the underlying problem may be corrected or whether another payment method is needed.

Soft vs. Hard Declines: A soft decline may be retried after the underlying issue is resolved, while a hard decline should not be reattempted. Merchants should follow processor guidance and prevent automated systems from repeatedly retrying transactions that received hard declines.

Retry Carefully: Merchants should not repeatedly force a declined transaction through without valid authorization. When a soft decline is corrected and authorization is obtained, the steps taken should be documented in case the transaction is later disputed.

Operational Playbook: A decline code reference guide can help employees respond consistently. Clear internal instructions on whether to retry, correct information, ask the customer to contact the issuer, or request another payment method can improve recovery while reducing authorization-related chargeback risk.

Table of Contents

1. What Are Credit Card Decline Codes?
2. List of Credit Card Decline Codes
3. What’s the Difference Between a Hard Decline and a Soft Decline?
4. Emerging Trends in Credit Card Decline Prevention
5. What Does Decline Code 51 Mean?
6. What Does Decline Code 05 Mean?
7. What Does Decline Code 91 Mean?

A credit card being declined is never a fun experience. Many customers feel both a sense of frustration at the delay in making their purchase and a sense of embarrassment, worrying that anyone around might assume they're someone who spends money recklessly. Merchants know, however, that there are a wide variety of possible reasons for a credit card being declined. Some of these reasons can be resolved quickly and easily, while others require the merchant to ask for another method of payment or even take some other action requested by the issuer.

In order to respond properly to a declined credit card and salvage those transactions that can be salvaged, merchants need to be familiar with the decline codes they might receive and what those codes mean. Let's talk about the most common decline codes and how merchants should respond when they receive them.

Most decline codes are sent early in the transaction process, when the merchant first attempts to obtain authorization to run the card.

A decline message doesn’t mean the transaction is a loss. Even if the customer doesn’t have an alternate payment method, many decline codes indicate errors or inconsistencies that can be corrected.

If this can be done, the merchant can keep attempting the transaction until the reasons for the decline are addressed and the transaction goes through. However, merchants need to be careful about getting the proper authorization and re-running transactions correctly, or else they could end up liable for authorization-related chargebacks down the line.

Many entities are involved in processing a credit card transaction. It starts with the merchant and the customer, but before any money actually changes hands, it will go through a payment processor, gateway, and the customer’s issuing bank. If any of these parties detects a problem with the transaction, they may reject it. If this happens, they will send back a decline code that specifies the reason why the transaction could not be processed.

Decline codes aren't completely uniform across all networks, but after a major effort to standardize these codes across the industry, there's now a standardized list of codes covering most situations.

When merchants encounter a network-specific decline code, they'll need to reference that network's list of response codes in order to understand what it means.

List of Credit Card Decline Codes

What Are the Most Common Decline Codes?

The list of credit card decline codes is long—even longer if you were to include all those specific to one network or issuer—but some codes are more common than others. Codes 51 (insufficient funds) and 05 (do not honor) are especially common.

Here's a rundown of the most common decline codes:

• 51 - Insufficient funds: At the time authorization was requested, the customer’s account did not have sufficient funds to cover the transaction.
• 65 - Withdrawal limit exceeded: The transaction would exceed the maximum withdrawal amount on the account. This code may specify that the limit is daily, weekly, or monthly.
• 05 - Do not honor: The issuer will not process the transaction. The customer will need to contact them for further details
• 54 - Expired card: The card is past its expiration date.
• 14 - Invalid card number: The card number provided does not match any active card in the issuer's database.
• N7 - Invalid CVV: The CVV number provided does not match what the issuer has on file. Incorrect CVV numbers may also result in code 63, which indicates a security violation.
• 94 - Duplicate transaction: The transaction details match an earlier transaction and the processor is flagging it to prevent an erroneous double charge.
• R0 or R1 - Recurring charge stopped at customer request: The customer asked their bank to stop accepting a particular recurring charge.
• 03 - Invalid merchant: The merchant may not have configured their payment processor software correctly.
• 41 or 43 - Pick up card, lost or stolen: The card has been reported lost or stolen, and the issuer is asking the merchant to keep the card, if possible, and call them.

Obviously, you wouldn’t want to keep trying to run a card that had been reported lost or stolen, but it’s not unheard of to mistype a CVV number or expiration date. You can try to correct errors and attempt a transaction a second time when you understand which transactions are safe to retry and which should not be attempted again. The key is knowing the difference between hard and soft declines.

Aggressive anti-fraud tools at the processor level can sometimes cause soft declines. Your processor will have rules and guidelines for retrying soft-declined transactions. Review the information they have provided you and be especially careful about allowing automated retries. In a card-not-present environment, your system should ideally be set up to block repeated attempts at a transaction that has returned a hard decline code.

The best way to recover sales in the case of hard declines is to offer the customer alternate payment methods. You can also offer to hold an item in reserve if they need to contact their bank to resolve a security flag or get their limit increased.

Merchants should never attempt to “brute force” a transaction without proper authorization, as these can result in chargebacks that they will be unable to fight. When you do work with a customer to get around a soft decline and obtain authorization for a transaction, make sure you carefully document the actions you took and retain that information as evidence in case they ever decide to dispute it. Good record-keeping can be crucial to successfully fighting a chargeback dispute.

Merchants may benefit from keeping a reference sheet on hand with a list of decline codes and instructions for employees on how to handle each. This allows employees to inform customers why their card has been declined and prevents any mix-ups involving retrying or not retrying a transaction.

Having consistent policies for handling various decline codes can help process any transactions that can be processed and prevent authorization-related chargebacks.

Managing Declines on Recurring Payments

When a customer’s first payment succeeds but subscription renewals fail, the billing setup is worth checking. A card saved for one-click purchases may not have been set up for recurring billing. Free trials deserve particular attention because there may be no initial purchase to prompt authentication. Merchants can authenticate the card during signup without collecting payment.

Renewal payments also need information connecting them to the original subscription transaction. Processors often handle this connection automatically, but merchants using a separate card vault may need to supply the original transaction reference. If declines increase after a processor migration or billing integration change, checking whether that information survived the transition is a useful starting point.

Merchants also need a defined policy for subscriptions that remain unpaid. Depending on the service, that might involve a grace period, restricted access, or a temporary pause. The policy should explain whether charges continue during that period and what happens to stored data, account settings, or unused benefits.

If service is suspended, the account should clearly display how to restore access and whether the original billing schedule will resume. This reduces uncertainty for customers returning to an interrupted subscription.

Nobody likes getting a decline code—not the customer, and certainly not the merchant—but they serve an important purpose by preventing problematic transactions from going through and alerting you to the issues that need to be resolved. When merchants understand the decline codes their processor returns, they can act quickly and decisively to recover sales by correcting transaction errors and offering alternative payment methods.

FAQ