Credit Card Decline Codes: What They Mean and What to Do About Each One

Written by

Gerard Hill

Founder of Dunning Lite. 12+ years in digital marketing and SEO, former CTO, Google Partner, and two Masters in Digital Marketing. Built Dunning Lite after watching his own micro-SaaS lose hundreds in MRR to expired cards — and realizing every recovery tool on the market was built for companies 10x his size.

@IllGerardLinkedInGitHub

What Are Credit Card Decline Codes?

A credit card decline code is the issuing bank's way of telling you why a payment didn't go through. Instead of just saying "nope," the bank sends back a code — usually a two-digit number or a short string — that explains what happened. Insufficient funds? There's a code for that. Expired card? Code for that too. Bank just feels suspicious about a Tuesday afternoon transaction? Yep, there's a code for that (it's the wonderfully vague "Do Not Honor").

For SaaS founders running subscriptions on Stripe, these codes are the difference between recovering a failed payment and losing a customer silently. They tell you whether to retry the charge, email the customer, or stop trying altogether. Ignore them, and you're basically treating a headache and a broken leg with the same aspirin.

Where Decline Codes Come From (The Chain)

When a payment fails, the decline code travels through a chain before it reaches you:

Each layer can translate or normalize the code. The bank sends a raw ISO 8583 code, Visa or Mastercard categorizes it, and Stripe translates it into something human-readable like insufficient_funds or expired_card. By the time it reaches your webhook, it's already been interpreted — which is actually helpful, because raw bank codes are about as readable as assembly language.

Hard Declines vs. Soft Declines: The Only Classification That Matters

Every decline code on the planet falls into one of two buckets. Get this distinction right and you'll handle 90% of payment failures correctly. Get it wrong and you'll waste retries on dead cards while ignoring recoverable revenue.

Soft Declines: Retry-Worthy

A soft decline means something temporary went wrong. The card is valid, the account exists, but right now the payment can't go through. Common reasons:

• Insufficient funds — The customer doesn't have the money today. They might on Friday.
• Processing error — The bank's system hiccuped. Retry in a few hours.
• Generic decline / Do Not Honor — The bank said no without saying why. Often resolves on retry.
• Card activity limit — Too many transactions today. Try tomorrow.

Soft declines make up roughly 80% of all payment failures. Most of them can be recovered with smart retry timing — no customer email needed.

Hard Declines: Stop Retrying, Start Communicating

A hard decline means the payment method is dead. Retrying won't help — and actually makes things worse. Mastercard's excessive authorization penalties hit $0.50 per violation, and they're expanding in 2026. Not a bill you want.

• Expired card — The card's past its expiry date. New card required.
• Stolen/lost card — Flagged by the bank. Do NOT retry.
• Invalid card number — Typo or cancelled card. Needs new payment method.
• Authentication required — SCA/3D Secure needed. Customer must act.

The right response to a hard decline is always the same: contact the customer. Send them an email explaining what happened and give them a one-click link to update their payment details. If you need templates for this, check our dunning email examples.

The Complete Decline Code Reference Table

Bookmark this. Every decline code you'll realistically encounter as a SaaS founder, what it means, and what to do about it — all in one place.

The Most Common Codes — Explained in Detail

According to Visa's Global Declines Transaction Analysis, "Do Not Honor" (05) and "Insufficient Funds" (51) account for approximately 76% of all declined transactions. Handle just these two correctly and you've addressed the vast majority of your failed payments.

Stripe Decline Codes: A Developer's Quick Reference

If you're on Stripe (and if you're reading this, you probably are), Stripe translates raw bank codes into its own human-readable format. You get these in the invoice.payment_failed webhook event under payment_intent.last_payment_error.decline_code.

Here are the Stripe-specific codes you'll see most often and how they map to what we've covered above:

For a step-by-step guide on handling these in your Stripe integration — including webhook setup and retry logic — read our guide to recovering failed Stripe payments. For the developer's playbook — including webhook code, retry logic, and SCA handling — see our Stripe decline codes developer guide.

What to Do When a Payment Is Declined (The Founder's Playbook)

Knowing what each code means is only half the job. The other half is responding correctly — and quickly. Here's the decision tree:

How Decline Codes Connect to Involuntary Churn

Here's why all of this matters for your bottom line: every unhandled decline code is a customer walking out the door without knowing they left.

Industry data tells a clear story: 20-40% of total SaaS churn is involuntary — caused entirely by failed payments. And across the subscription economy, 15-25% of recurring payments get declined on the first attempt. If your only response to that is Stripe's default retry logic, you're recovering roughly 15-22% of those failures. The rest? Gone.

The good news: SaaS companies have the highest past-due recovery rate of any industry at 53.5% (Recurly benchmarks). With a proper decline-code-aware dunning system — smart retries for soft declines, targeted emails for hard declines, card updaters for prevention — that number climbs to 70-85%.

If you want to understand the full picture of how payment failures connect to churn, read our guide to involuntary churn. To see the revenue impact on your specific numbers, try our Lost MRR Calculator.

5 Ways to Reduce Your Decline Rate

Handling decline codes after they happen is essential. But the real win is preventing declines before they happen. These five strategies can reduce your decline rate by 15-30%:

For a detailed comparison of tools that automate all of this, check our dunning software comparison. For the full dunning strategy — prevention, recovery, and escalation — read our complete dunning management guide.

Frequently Asked Questions