Resources

Why Payments Fail: Every Reason a Card Declines

A payment fails when the bank that issued your subscriber's card refuses the charge, or when the charge never reaches that bank in a clean, complete form. The card can be real, the customer can want the product, and the subscription can still fail — because a decline is not one problem. It is a category of problems, and each one needs a different response.

That distinction matters more than the failure itself. Some failures clear on their own in a few days. Some clear only when the subscriber updates a card. Some will never clear on that card, no matter how many times you try it.

This page is the taxonomy: why payments fail, in plain terms, and what each failure type means for getting paid. Prevention and the full fix-it sequence live in our guide to how to reduce failed payments. The causes live here.

Soft declines vs. hard declines: the split that decides everything

Every decline falls into one of two buckets.

Soft declines are temporary. The account exists and the card is fundamentally usable, but something about this attempt, at this moment, did not work: not enough money today, a card that needs updating, a processing hiccup, a security check that was not completed. Soft declines are recoverable — by retrying at the right time, by getting an updated card, or by asking the subscriber to complete a step.

Hard declines are final for that card. The account is closed, the card was reported stolen, or the issuer has said, in effect, do not try this card again. Hard declines are not recoverable on the same payment method. The only path back is a new card from the subscriber — and if that does not happen, the subscription ends.

That split determines whether you retry, what you say, and when you stop. We compare the two further in hard declines vs. soft declines, and every major code is summarized on the decline code cheat sheet.

Soft decline 1: Insufficient funds

This is the largest single reason payments fail. Across 5.4M failed payments, insufficient funds is the largest decline category at 40.6%, according to Churnkey's published analysis of Stripe data.

The mechanics are simple. The charge arrives when the account does not have enough money in it — the day before payday, or after a large purchase. The card is not broken. The timing is.

That is why insufficient-funds declines are among the most recoverable failures you will see. The fix is rarely a new card. It is a better moment: a retry aligned to when money is likely to be back in the account, spaced far enough from the first attempt that you are not just hitting the same empty balance again. We go deeper on this category in insufficient funds declines.

Soft decline 2: Expired and outdated cards

Cards expire. They are also replaced — after a loss, a fraud scare, or a routine reissue — and the new card carries a new number, a new expiry date, or a new security code. If your subscription still holds the old details, the renewal charge fails even though the subscriber has a perfectly good card in their wallet.

Nothing about the subscriber's intent changed. They did not cancel, and they probably do not know anything is wrong until you tell them.

Recovery here has two routes. The first is silent: card networks and issuers offer account updater services that refresh stored card details when a card is replaced, so some of these failures never reach the subscriber at all. The second is a clear, branded card-update request — an email or text that takes the subscriber to a secure page where they enter the new card. A blind retry does not work: the old details fail the same way every time. For the full picture, see expired card payments.

Soft decline 3: Processing and technical errors

Sometimes no one is at fault. The issuer's systems time out, a processor has a brief outage, or a message between the networks arrives incomplete and the charge is rejected as a precaution. These errors look alarming in a dashboard, but they are often the easiest failures to recover, because nothing about the card or the account is wrong.

The correct response is patience measured in hours or days, not minutes. A short pause, then a retry, clears many of them without the subscriber ever knowing there was a problem. The mistake is sending a "your payment failed, update your card" message to someone whose card is fine — that creates worry, support tickets, and occasionally a cancellation that would never have happened.

Soft decline 4: Authentication and issuer security checks

Banks increasingly ask for proof that a charge is legitimate: a one-time confirmation, an authentication step, or an approval inside a banking app. When that step is not completed — the subscriber missed the prompt, dismissed it, or never saw it — the charge can fail even with money in the account and a valid card.

These failures are recoverable, but not by retry timing alone. The subscriber has to do something: complete the authentication, or confirm with their bank that the recurring charge is theirs. Your message therefore has to say something different from the insufficient-funds message. "Try again later" is our job. "Your bank needs you to approve this" is theirs — and the sooner you say it clearly, the better the chance they act.

Hard declines: Stolen, closed, and do-not-honor

Hard declines carry a different instruction: stop charging this card.

Stolen or lost cards. The card was reported missing and cancelled by the issuer. Any further charge is, by definition, being attempted on a dead card. The subscriber may well have a replacement — but you do not have its details, and only they can give them to you.

Closed accounts. The subscriber closed the bank account or the card account entirely. There is nothing behind the card to charge, and the old payment method is finished.

Do-not-honor patterns. This is the issuer's most general refusal: the bank will not say exactly why, only that it will not accept the charge. A single do-not-honor can occasionally behave like a soft decline, but repeated do-not-honor responses are a stop signal, not a challenge. Retrying a card the issuer keeps refusing wastes attempts and can damage your standing with processors. We explain the nuance in what a do-not-honor decline means.

For all hard declines, the playbook is short: do not retry the card, contact the subscriber once, clearly, with an easy way to add a new payment method, and set a firm point at which the subscription is cancelled if they do not.

Which failures are recoverable? A quick reference

Failure type	Bucket	Recoverable?	What recovers it
Insufficient funds	Soft	Yes, often	Retry timed to when funds return
Expired or replaced card	Soft	Yes	Account updater, or subscriber updates the card
Processing error	Soft	Yes, often	Short pause, then retry
Authentication not completed	Soft	Yes	Subscriber completes the bank's check
Stolen or lost card	Hard	Not on that card	Subscriber provides a new card
Closed account	Hard	Not on that card	Subscriber provides a new card
Repeated do-not-honor	Hard	Not on that card	Stop retrying; ask for a new card

Read the table as a routing guide. Soft declines go into a retry and outreach sequence. Hard declines go straight to a card-update request and a deadline. Mixing the two routes is where most recovery efforts lose money.

The system view: a decline code is an instruction

Every failed payment arrives with a decline code — the processor's short label for what the issuer said. That code is not trivia for a report. It is the instruction that should drive the next step: retry this one on payday logic, do not retry that one at all, ask this subscriber for a new card, ask that one to approve the charge with their bank.

A decline-code-aware system works that way by design. In Swipe Again, smart retries read the decline code and run up to 6 attempts over roughly 16 days for failures that can clear, while hard declines are never retried. Branded dunning emails and text messages run alongside the retries, so when a failure does need the subscriber — a new card, an approval — the ask arrives while the retries are still working the failures that do not.

The point is not the number of attempts. It is that each failure type gets the response that matches its cause. A failed payment is information — and businesses that ignore it misread the loss as churn, when the subscriber never chose to leave at all.

The bottom line

Payments fail for a short list of reasons, and the list splits cleanly in two. Soft declines — insufficient funds, outdated cards, processing errors, incomplete authentication — are temporary and largely recoverable with the right timing and the right ask. Hard declines — stolen cards, closed accounts, persistent do-not-honor responses — are final for that card, and the only recovery is a new payment method. Learn which bucket a failure sits in, and the correct next step usually becomes obvious.

Frequently asked questions

What is the most common reason payments fail?

Insufficient funds. Across 5.4M failed payments, it is the largest decline category at 40.6%, according to Churnkey's published analysis of Stripe data. It is also a soft decline, which means it is often recoverable with a retry timed to when money returns to the account.

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

A soft decline is temporary: the account and card are usable, but this attempt failed because of timing, outdated details, a processing error, or an incomplete security check. A hard decline is final for that card — it was reported stolen, the account is closed, or the issuer will not honor charges on it — and retrying it will not work.

Should you retry a hard decline?

No. Retrying a stolen, closed, or persistently refused card cannot succeed, wastes attempts, and can hurt your standing with processors. The only recovery path for a hard decline is asking the subscriber to provide a new payment method before a set deadline.

Why did a payment fail when the customer has money and a valid card?

Usually a processing error or an incomplete authentication step. Issuer systems time out, messages between networks arrive incomplete, and banks increasingly require the customer to approve a charge. In all three cases the card is fine and the failure is often cleared by a later retry or by the customer completing the bank's check.

Does a failed payment mean the subscriber wants to cancel?

No. A failed payment means a charge was declined, not that a decision was made. Many failures happen without the subscriber knowing anything went wrong — an expired card, a lean account on the wrong day. Treating a decline as a cancellation gives up subscribers who would have stayed.

Related reading: In-app purchase billing