Credit Card Decline Codes: Complete Reference for Merchants

Key Takeaways

A credit card decline code is a two-digit alphanumeric code that tells merchants exactly why a transaction was not authorized.
Codes 51 (insufficient funds) and 05 (do not honor) account for the majority of declines merchants encounter.
Hard declines are final and must not be retried — retrying them triggers fraud flags and chargeback risk.
Cross-border transactions have higher baseline decline rates; the payment infrastructure you use directly affects how often codes like 62 and 57 fire.

A declined payment costs more than just the transaction. There's the time spent investigating, the customer friction, and the real chance of losing the sale entirely. Decline codes exist to tell you exactly why the card didn't go through — but they're only useful if you know how to read them. This guide covers every standard code, the critical hard vs. soft distinction, and actionable steps to bring your decline rate down. It starts with the payment authorization process — because understanding who sends a code and why determines what you can actually do about it.

What Is a Credit Card Decline Code?

A credit card decline code is a two-digit alphanumeric code returned during authorization to explain why a transaction was not approved. It comes from one of three sources: the issuing bank (the cardholder's bank), the card network (Visa, Mastercard, Amex), or the payment processor.

The source matters. An issuer code — like 51 or 54 — points to a problem with the cardholder's account. A processor code may indicate a merchant configuration issue. A network code typically signals routing or a security flag. Merchants who receive a code they don't recognize should check with their processor, since network-specific codes exist outside the standard list below.

Complete List of Credit Card Decline Codes

The table below covers standard credit card decline codes with a Hard/Soft classification and a one-line merchant action. Hard declines must not be retried. Soft declines can be reattempted once the underlying issue is resolved. Codes marked * are ambiguous — treat them as hard unless the customer has contacted their bank.

Code	Meaning	Hard / Soft	Merchant Action
01	Refer to issuer	Soft	Ask customer to call their bank, then retry
02	Refer to issuer (special condition)	Soft	Ask customer to contact their bank
03	Invalid merchant	Soft	Check merchant account/processor configuration
04	Pick up card (no fraud)	Hard	Request alternate payment method
05	Do not honor	Hard*	Request alternate payment; customer must call bank
06	Error	Soft	Retry; if recurring, check for system error
07	Pick up card (fraud)	Hard	Do not retry; contact issuer if possible
10	Partial approval	—	Collect remainder with another payment method
12	Invalid transaction	Soft	Check payment settings; correct and retry
13	Invalid amount	Soft	Verify amount for errors (negative value, symbols)
14	Invalid account number	Soft	Ask customer to re-enter card number
15	No such issuer	Hard	Request another card
19	Re-enter transaction	Soft	Ask customer to re-enter payment details
21	No action taken	Soft	Retry transaction
25	Unable to locate record	Soft	Contact your processor
28	File temporarily unavailable	Soft	Retry after a short delay
41	Lost card	Hard	Do not retry; request alternate payment method
43	Stolen card	Hard	Do not retry; request alternate payment method
46	Closed account	Hard	Request another payment method
51	Insufficient funds	Soft	Request alternate payment method
52	No checking account	Hard	Request another card
53	No savings account	Hard	Request another card
54	Expired card	Hard	Ask for updated card details
55	Incorrect PIN	Soft	Ask customer to re-enter PIN
57	Transaction not permitted — card	Hard	Request different card or payment method
58	Transaction not permitted — terminal	Soft	Check gateway or terminal configuration
59	Suspected fraud	Hard*	Customer must contact bank to authorize
61	Exceeds approval amount limit	Soft	Customer contacts bank to raise limit, or use another card
62	Restricted card	Hard	Request another payment method
63	Security violation	Hard	Customer must contact bank
64	Transaction violates AML requirement	Hard	Do not retry
65	Exceeds withdrawal frequency limit	Soft	Customer contacts bank, or retry later
70	PIN data required / Contact issuer	Soft	Customer contacts bank
75	Exceeds PIN entry attempts	Hard	Customer must reset PIN with bank
76	Unsolicited reversal	—	Contact your processor
78	Blocked, first use	Soft	Customer activates card with bank, then retry
79	Already reversed / Expired card	Hard	Request updated card
82	CVV check failed	Soft	Ask customer to re-check CVV; if fails again, request another card
85	No reason to decline	Soft	Retry
86	Cannot verify PIN	Soft	Try different payment method or terminal
91	Issuer or switch unavailable	Soft	Retry after a short delay
92	Unable to route transaction	Soft	Retry; if persistent, contact processor
93	Transaction cannot be completed — violation of law	Hard	Do not retry
94	Duplicate transaction	Soft	Verify if duplicate; if not, retry with a new reference
96	System error	Soft	Retry; if persistent, contact processor
N7 / 97	Invalid CVV	Soft	Ask customer to re-check CVV
1A	Additional customer authentication required	Soft	Complete 3D Secure authentication
5C	Transaction unsupported or blocked by issuer	Hard	Request another payment method
9G	Cardholder blocked transaction	Hard	Do not retry; customer must contact bank
R0	Recurring payment stopped at customer request	Hard	Do not retry; contact customer directly
R1	Customer revoked recurring authorization	Hard	Do not retry; contact customer directly

Hard Declines vs. Soft Declines: What Merchants Need to Know

Before deciding how to respond to any decline code, one question matters most: is this a hard or soft decline?

A soft decline is temporary. The transaction failed because of something fixable — insufficient funds, a mistyped CVV, or a transient technical issue at the bank. Once the underlying problem is resolved, the transaction can be reattempted.

A hard decline is final. The issuer has made a permanent decision to reject the transaction. Retrying a hard decline won't change the outcome — and it can make things worse. Repeated attempts on a hard-declined card trigger additional fraud flags, raise your chargeback exposure, and can put your merchant account at risk of excess activity penalties.

Hard decline codes — do not retry:

04, 07, 15, 41, 43, 46, 52, 53, 54, 57, 62, 63, 64, 75, 79, 93, 9G, R0, R1

Soft decline codes — retry after resolving the issue:

01, 02, 06, 12, 13, 14, 19, 21, 28, 51, 55, 58, 61, 65, 70, 78, 82, 85, 86, 91, 92, 94, 96, N7, 1A

Codes 03, 05, and 59 are ambiguous — the issuer is declining but not disclosing the exact reason. Treat them as hard unless the customer has already spoken with their bank and confirmed the issue is resolved.

Your payment processor publishes retry rules that specify how many attempts are permitted and the required wait time between them. Automated billing systems must follow these rules — network violations carry fines.

The Most Common Credit Card Decline Codes Explained

Code 51 — Insufficient Funds

The most frequent decline code, accounting for roughly 44% of all declines. The cardholder's account doesn't have enough available balance or credit to cover the transaction. Ask for an alternate payment method. Retrying the same card is pointless — the balance hasn't changed between attempts.

Code 05 — Do Not Honor

The second most common code and one of the least informative. The issuing bank refuses to process the transaction but won't disclose the specific reason. Causes range from a billing address mismatch to an internal fraud flag. The cardholder needs to call their bank directly. Don't retry without the customer's involvement — the issue won't resolve itself.

Code 54 — Expired Card

The card is past its expiration date. For one-time transactions, ask for updated card details. For subscription businesses, expired cards are the leading cause of renewal failures — stored card details go stale while customers don't notice until access is cut off. Proactively prompt customers to update their payment method before the expiry date, not after the first failed renewal.

Code 14 — Invalid Account Number

The card number doesn't match any active account in the issuer's database. Almost always a data entry error in card-not-present transactions. Ask the customer to re-enter their card number. A format check at input — validating length and Luhn algorithm — catches most of these before they reach the network.

Code N7 / 82 / 97 — CVV Mismatch

The CVV entered doesn't match the issuer's records. Customers frequently mistype the three-digit code on the back of their card (or four digits on Amex). Ask them to re-check it. Two failures with the same card is a clear signal to request a different payment method — further attempts will continue to fail.

Code 91 — Issuer or Switch Unavailable

The issuing bank's systems can't be reached — a technical outage, not a fraud flag. There's no problem with the card or the cardholder. Retry after a short delay. If retries keep failing over an extended period, the network outage is on the issuer's end and will typically resolve without merchant intervention.

Code 65 — Exceeds Withdrawal Frequency Limit

The transaction would push the cardholder over their daily, weekly, or monthly spending or withdrawal limit. The customer can contact their bank to raise the limit, split the purchase across two payment methods, or come back once the limit resets. Don't retry the same amount on the same card — it will fail again.

Code R0 / R1 — Recurring Charge Stopped

The cardholder asked their bank to stop this specific recurring charge. This is a deliberate decision, not a technical failure. Do not retry — the bank has been explicitly instructed to block it. Contact the customer directly to resolve billing. Retrying without resolution creates direct chargeback exposure.

Why Cross-Border Transactions Have Higher Decline Rates

International card transactions are declined at meaningfully higher rates than domestic ones — some corridors see 2–3x the baseline decline rate. Several structural factors drive this, and they map directly to specific decline codes.

Code 62 — Restricted Card

Many consumer cards are configured by their issuing bank to block cross-border use by default, or to require explicit cardholder authorization before an international transaction clears. Businesses collecting from international customers regularly see code 62 when buyers haven't notified their bank about foreign spending — and neither the merchant nor the cardholder did anything wrong.

Code 59 — Suspected Fraud

Card networks and issuers use behavioral models to flag unusual patterns. A first-time payment from a new country, an unfamiliar merchant category, or a large cross-border transaction all score higher on risk models — triggering precautionary declines on legitimate transactions. The cardholder needs to call their bank to confirm the transaction is genuine.

AVS Mismatch and Code 05

Address Verification Service (AVS) compares the billing address the customer submits against what's on file with their issuer. International addresses frequently don't conform to the format US-centric or UK-centric AVS systems expect — wrong postal code structure, abbreviated province names, apartment format differences. Merchants with aggressive AVS rejection rules create unnecessary code 05 declines on legitimate international orders.

Code 57 — Transaction Not Permitted

Some card types aren't authorized for international transactions or specific merchant categories. Basic consumer debit cards are the most common example. Businesses with B2B customers who sometimes pay on personal cards encounter this regularly. For recurring international vendor payments, virtual cards issued through a cross-border payment platform reduce code 57 exposure — they're configured for international use by default, unlike standard consumer cards.

Currency routing friction also plays a role. When a transaction is routed through a foreign acquirer rather than a domestic one, it crosses additional network hops — each with its own authorization rules. Platforms with local acquiring infrastructure in the customer's region process transactions closer to domestic, reducing the probability of triggering these cross-border-specific codes.

How to Reduce Your Credit Card Decline Rate

Most merchants have more control over their decline rate than they realize. These six steps address the most common root causes.

Validate card data at input. Real-time format checking — card number length, Luhn validation, expiry date format, CVV field presence — catches entry errors before they reach the network. Errors that become code 14 and 13 declines are almost always preventable at this stage.
Calibrate AVS rules correctly. AVS reduces fraud, but aggressive rules that reject partial address matches will decline legitimate transactions from international customers with non-standard address formats. A full-reject policy on AVS mismatches typically costs more in declined revenue than it saves in fraud.
Build smart retry logic for soft declines. A failed subscription renewal due to insufficient funds (code 51) can often be recovered by retrying 3–5 days later when the customer's next paycheck clears. Build retry intervals that respect your processor's network rules and give customers time to resolve their account.
Use 3D Secure on high-value or high-risk transactions. 3DS adds a customer authentication step that shifts fraud liability to the issuer and can turn some soft declines into approvals. The additional friction is worth it for high-ticket transactions or markets with elevated fraud rates.
Give customers clear, non-technical decline messages. Most decline codes don't translate into anything actionable for the customer. Instead of surfacing error code 05, explain that their bank declined the payment and they should contact their card issuer. Customers who are confused about why their card was declined typically just need to know the next step — not the error code.
Match payment infrastructure to transaction type. For businesses processing cross-border B2B payments, payment approval rates are directly tied to how the platform handles international routing. PhotonPay supports 90+ currencies across 200+ countries with local routing infrastructure designed to reduce cross-border friction at the network level — systematically reducing the frequency of codes 62 and 57 for businesses collecting and sending international payments.

Decline Codes in Recurring and Subscription Billing

Subscription businesses face decline management challenges one-time merchants don't. A card that works for the initial purchase may fail at renewal for reasons that didn't exist at signup.

Code 54 (expired card) is the most common recurring billing failure. Cards expire and stored details go stale while customers don't notice. Proactively send payment update prompts before expiry, not after the first failed renewal.
Code R0/R1 (recurring charge stopped) means the customer has explicitly asked their bank to block this charge. Do not retry — contact the customer. Retrying R0/R1 codes is one of the fastest ways to accumulate unauthorized transaction chargebacks and push your chargeback ratio above network warning thresholds.
Code 65 (exceeds limit) on subscription renewals often means the customer's account is under financial stress. A grace period — temporarily restricting access rather than canceling — recovers more revenue than immediate cancellation. Most customers who can't pay today can pay within a few days.

Merchants using automated billing should define explicit policies for: how many retries to attempt, how long to wait between them, what happens to account access during a billing failure, and how to communicate the status to customers. Most card networks publish retry frequency rules — violations carry fines.

Frequently Asked Questions

What is the most common credit card decline code?

Code 51 (insufficient funds) is the most frequent, accounting for roughly 44% of all declines. Code 05 (do not honor) is the second most common and is harder to resolve — the issuer declines without disclosing the specific reason.

What does decline code 05 mean?

Code 05 means the issuing bank refuses to authorize the transaction. It's one of the least specific codes — possible causes include a billing address mismatch, a fraud flag, or an internal policy block. The cardholder must contact their bank. Merchants shouldn't retry without the customer's direct involvement.

What does decline code 51 mean?

Code 51 means the cardholder doesn't have sufficient funds or available credit for the transaction. Ask for an alternate payment method. Don't retry the same card immediately — the balance won't change between attempts.

What is the difference between a hard decline and a soft decline?

A soft decline is temporary — the issue can be resolved and the transaction reattempted. A hard decline is final — the issuer has permanently rejected the transaction. Retrying a hard decline is ineffective and can trigger fraud flags and chargeback liability. The Hard/Soft column in the table above identifies which category each code falls into.

Can I retry a declined transaction?

Only for soft declines, and only within the retry limits published by your card network and processor. Never retry hard declines — codes like 41 (lost card), 43 (stolen card), 54 (expired), or R0/R1 (recurring charge stopped). Automated systems should be configured to block retries on hard decline codes.

Why do international card payments get declined more often?

Cross-border transactions face additional risk screening from card networks and issuers, higher rates of billing address mismatches through AVS, and restrictions on cards not configured for international use (code 62). The routing infrastructure of your payment platform also matters — platforms with local acquiring in the customer's region handle cross-border transactions more cleanly than those routing everything through a single foreign acquirer.