Credit Card Decline Codes: The Complete Merchant Reference

What a Decline Code Actually Is

When a customer taps, dips, or swipes a card, your terminal sends an authorization request through your processor to the card network, which routes it to the bank that issued the card. That issuing bank makes the decision — approve or decline — and sends back a two-digit response code, which your terminal displays with or without a short message.

Here's the key thing most merchants never get told: the decline is almost never your processor's decision. It's the customer's bank talking. The code is the bank's one-line explanation, passed back through the network to your countertop.

These response codes come from the ISO 8583 messaging standard card networks are built on, but exact wording varies slightly by processor — one terminal says "Do Not Honor" where another says "Declined — 05." The meanings below follow Shift4's published decline code reference, cross-checked against Chargeback Gurus' industry reference; if your processor's documentation words a code differently, trust their version for your equipment.

The Three Families Every Merchant Should Recognize

Before memorizing individual codes, learn the three buckets. Every decline falls into one, and the bucket tells you what to do:

• Soft declines — retryable. Temporary conditions: insufficient funds, issuer system down, daily limit reached. The card itself is fine. One polite retry or "try again tomorrow" is appropriate.
• Hard declines — do not retry. The card is expired, invalid, closed, or the transaction type isn't allowed. No amount of re-swiping fixes it. Ask for another payment method.
• Fraud and pickup codes — stop. Codes like 04, 41, and 43 mean the issuer has flagged the card as lost, stolen, or compromised. Don't retry, don't argue, and never put yourself at risk trying to confiscate anything — decline the sale and ask for a different payment method.

The Decline Code Reference Table

The standard response codes merchants actually see, what each means, and what to do at the counter — this is the cheat sheet to tape near the register.

Code	Meaning	What to Do at the Counter
00	Approved	Nothing — this is the code you want. Transaction completed.
01	Refer to card issuer	The bank wants to talk to its customer. Ask the customer to call the number on the back of the card, or use a different card.
02	Refer to issuer, special condition	Same as 01 with an extra flag on the account. Customer calls their bank; take another card in the meantime.
04	Pickup card	Hard stop. The issuer wants the card back — likely lost, stolen, or compromised. Do not retry; ask for another payment method. Never physically confiscate a card.
05	Do not honor	The most common decline. The bank refused without a reason. Ask for another card; the customer can call their bank. One retry after 24 hours is reasonable — repeated same-day retries are not.
12	Invalid transaction	Something about the transaction type isn't allowed — often a setup or entry issue on your side. Verify the transaction type and your terminal configuration before retrying once.
13	Invalid amount	The amount field is malformed — a typo, a negative number, a stray symbol. Re-enter the amount carefully and run it again.
14	Invalid card number	The card number failed validation. If it was keyed in, re-key it. If it was read from the chip or stripe, the card itself is bad — ask for another.
15	No such issuer	The card number doesn't map to any real bank. Check the first digit (Visa 4, Mastercard 5 or 2, Discover 6, Amex 3). If it was read electronically, treat the card as suspect.
19	Re-enter transaction	A processing hiccup, not a decision. Run the transaction again — this one is genuinely "try again."
41	Lost card	The cardholder reported this card lost. Hard stop — do not retry, ask for another payment method.
43	Stolen card	The cardholder reported this card stolen. Hard stop. Do not retry, do not return the sale to the card, and prioritize staff safety over the card.
46	Closed account	The account behind the card no longer exists. Hard decline — another card is the only fix.
51	Insufficient funds	Not enough money or available credit for this amount. Classic soft decline: offer to try a smaller amount, split the payment, or take another card.
54	Expired card	The card is past its expiration date. Check the date on the front; ask for a current card. Never retry with a guessed expiration date.
57	Transaction not permitted to cardholder	The card can't be used for this type of transaction (some cards block online, international, or specific merchant categories). Customer needs their bank or a different card.
58	Transaction not permitted to terminal	The mirror image of 57 — your merchant account isn't set up for this transaction type. This one is on your side: call your processor.
61	Exceeds withdrawal limit	The transaction pushes the card past its per-transaction or daily amount limit. Offer a smaller amount, a split payment, or another card.
62	Restricted card	The card is blocked for this use — often region or country restrictions. Another card is the practical fix.
63	Security violation	A security check on the card failed. Don't retry; the customer should contact their bank.
65	Activity limit exceeded	The card has hit its count of allowed transactions for the day. Soft decline — tomorrow it will likely work. Take another card today.
78	No account / blocked, first use	Brand-new cards that haven't been activated often throw this. Ask if the card is new — activation by phone or app usually fixes it in minutes.
85	No reason to decline	Not really a decline — issuers return this on account verifications ($0 authorizations) to say the card checks out.
91	Issuer unavailable	The bank's authorization system is down or unreachable. Nothing is wrong with the card. Wait a few minutes and retry, or take another card.
96	System error	A malfunction somewhere in the processing chain. Retry once after a short wait; if it persists, call your processor.

You may also see letter-number codes on modern terminals (like CVV-failure codes on card-not-present transactions). The same three families apply: temporary, permanent, or fraud.

Retry Etiquette: What Each Family Allows

Soft declines (51, 61, 65, 91, 96, 19)

One or two retries, spaced out, are fine. A 91 or 96 is infrastructure, not the customer — wait a few minutes. A 51 or 61 is the amount — offer a split payment before giving up on the sale.

Hard declines (04, 14, 15, 41, 43, 46, 54, 57)

Do not retry these. Ever. Repeated attempts on dead cards look exactly like card testing — the pattern fraudsters use to probe stolen numbers — and card networks now bill for it. Under Visa's reattempt rules, the hardest declines (lost, stolen, closed, invalid account) are Category 1 and may not be reattempted at all; every retry on one draws a per-attempt excessive reattempt fee. Softer decline categories are capped at 15 reattempts within 30 days before per-attempt fees kick in (per CardPointe's published summary of Visa's decline rules — fee amounts vary by region and change over time, so confirm current figures with your processor).

At the counter this rarely matters — nobody re-swipes a card 16 times. Where it bites is recurring billing and e-commerce, where an automated system can hammer a closed card every night for a month and hand you a fee per attempt. If you bill on a schedule, make sure your system distinguishes hard from soft declines and stops retrying the hard ones.

The "Do Not Honor" Deep-Dive

Code 05 deserves its own section because it's both the most common decline and the least explained. "Do not honor" is the issuing bank's way of saying no without saying why. The real reasons behind it:

• The bank's fraud model flagged the transaction as unusual — wrong city, odd hour, unfamiliar merchant category.
• A temporary hold or freeze on the account.
• The account is in bad standing in some way the bank won't disclose.
• Some issuers use 05 as a catch-all where another bank would return a specific code like 51.

What it is not: proof the customer is broke or up to something. Plenty of 05 declines happen to cardholders with money, on cards they use every day. The right counter move is neutral: "The card came back declined by the bank — do you have another card? Your bank can tell you why if you give them a call." Their bank can see the real reason; you never will.

A wave of 05s across many different customers in one day suggests the problem is on your side — see the section on decline spikes below.

Declines Online vs. In Person

In-person declines are simple: the issuer said no, the code says roughly why. Card-not-present transactions add a second layer — verification mismatches.

• AVS (Address Verification Service) checks the billing ZIP/address the customer typed against the bank's file. A mismatch often surfaces as a decline even when the issuer approved the funds.
• CVV mismatch means the security code was wrong. One typo is human; repeated CVV failures on one card are a card-testing red flag.

For online orders, let the customer re-enter their details once — most mismatches are typos or an old billing address after a move. If it fails again, request a different card. Don't loosen AVS and CVV settings to "fix" declines: turning off your first line of defense trades a few recovered sales for a much larger fraud problem. Our fraud prevention guide covers tuning these checks without strangling good orders.

When Declines Spike: What It Signals

Your normal decline rate is background noise — a few percent of attempts, mostly 05s and 51s. When it suddenly jumps, treat it as a signal:

• Many different cards, same code, short window — likely a fraud attack. Card testers run scripts against checkout pages with stolen numbers; you'll see bursts of 14s, 15s, and CVV failures. Tighten velocity limits and CAPTCHA, and alert your processor.
• Everything declining, mixed codes, including your regulars — check for 91s and 96s first. An issuer or processor outage looks like the end of the world for twenty minutes, then resolves itself.
• One transaction type always failing (58, 57, 12) — a configuration problem. Your merchant category code (MCC), terminal setup, or account permissions may not match what you're selling. This is fixable in a phone call to your processor.
• A gradual creep on recurring billing — normal card churn (expirations, reissues, closed accounts). An account updater service from your processor quietly fixes most of it.

Declined-then-retried transactions also feed disputes when a frustrated customer gets billed twice. If disputes are part of your spike, read what is a chargeback next — declines and disputes are cousins.

Keep the Customer: What to Say When a Card Declines

A decline handled badly costs you the sale and the customer. A decline handled well is forgotten by dinner. Three rules:

1. Blame the machine, not the person. "Looks like the bank didn't approve that one" beats "your card was declined" — same fact, no accusation.
2. Offer the next step immediately. "Do you have another card, or want to try tap instead?" keeps the line moving and gives the customer a graceful exit.
3. Keep the code to yourself unless asked. If the customer wants specifics, the number on the back of their card is the fastest route to the real reason.

Scripts worth training staff on:

• Soft decline (51, 61): "The bank didn't approve that amount — want to split it across two payments, or use another card?"
• Hard decline (54, 46): "That card came back as expired/closed on the bank's end. Do you have another one handy?"
• Pickup codes (04, 41, 43): "That card isn't going through — do you have another way to pay?" Then stop. No detective work at the register.

Fewer Declines Starts With Better Equipment and a Better Setup

Some declines are the bank's call and always will be. But misconfigured terminals, wrong MCCs, and outdated equipment cause declines that never needed to happen — and every one is a sale walking out the door. Modern merchant terminals with current EMV and contactless certifications produce cleaner authorization data, which means fewer 12s, 58s, and false fraud flags.

If your decline rate feels high or your statement is full of fees you can't explain, Payment USA will look at both for free. Send us a statement through our free statement review and we'll show you what's normal, what's fixable, and what it's costing you.

Sources

• Shift4, "Understand Credit Card Decline Codes" — https://shift4.zendesk.com/hc/en-us/articles/22375220994835-Understand-Credit-Card-Decline-Codes (observed September 2026)
• Chargeback Gurus, "Understanding Your Credit Card Decline Codes" — https://www.chargebackgurus.com/blog/credit-card-decline-codes (observed September 2026)
• CardPointe Support, "Visa Decline Rules and Responses" — https://support.cardpointe.com/compliance/visa-decline-rules-and-responses/ (observed September 2026)