Payment decline

DEFINITION

A payment decline is when a card issuer or processor refuses to approve a transaction, and declines fall into temporary soft declines and permanent hard declines that call for different recovery actions.

A payment decline happens when a card issuer or payment processor refuses to approve a transaction, so the charge does not go through. Declines fall into two broad groups. Soft declines are temporary and can often succeed on a later retry, such as when a card has insufficient funds. Hard declines are permanent and will fail again on the same card, such as a closed account or a card reported lost or stolen. For subscription businesses, declines on recurring charges are a leading cause of involuntary churn, so how they are detected and handled has a direct effect on how much revenue is recovered.

When a decline comes back, the issuer or processor is saying no to a charge, and the reason it gives determines what to do next. The response includes a code that maps to a cause, and those causes split into temporary and permanent. A soft decline means the card is generally valid but the charge failed for a passing reason, so a retry later may work. A hard decline means the card or account has a durable problem, so retrying the same card is pointless and the customer has to update their payment method. The common mistake is treating every decline the same way, when the value comes from reading the reason and matching the response to it. For recurring billing, declines are a routine part of running renewals at scale rather than rare edge cases.

Why payment declines matter for subscription businesses

In a subscription business, a declined renewal that is not recovered becomes lost revenue and, eventually, a churned customer who never chose to leave. This is involuntary churn, and it can quietly erode recurring revenue when declines are handled poorly. Because a meaningful share of recurring charges will fail for one reason or another, the difference between a strong recovery process and a weak one shows up directly in retained revenue. Handling declines well also protects the customer relationship, since customers do not want to lose access over a payment issue they were never told about.

How to handle payment declines

Treat declines as the start of a recovery workflow rather than a dead end:

  • Capture the decline reason code on every failed charge and classify it as soft or hard.

  • Retry soft declines on a sensible schedule, since many resolve on their own within a short window.

  • For hard declines, stop retrying and prompt the customer to update their payment method.

  • Pair automated retries with clear customer communication, so recoverable payments are collected and unrecoverable ones prompt the customer to act.

  • Watch decline rates over time to spot patterns tied to a card type, region, or issuer.

Benefits and examples

A deliberate approach to declines recovers revenue that would otherwise leak away and keeps customers from lapsing by accident. For example, when a monthly subscriber's card is declined for insufficient funds, the business can retry a few days later when the balance is likely restored, recovering the payment without ever bothering the customer. If the card was canceled instead, the business recognizes the hard decline, skips the futile retries, and emails the customer to add a new card. Each path fits the cause, which is what makes recovery efficient.

A subscription management platform helps most by turning raw decline responses into an automated recovery process. Rather than a team reading codes and deciding case by case, an integrated billing system can classify each decline, retry the recoverable ones on smart timing, and route the rest into customer outreach or a payment update flow. At the operator level, the payoff is more recovered revenue and less involuntary churn without manual triage of every failed charge. Recurly's Intelligent Retries adapts retry timing to each decline's specific cause rather than applying one fixed schedule, and treats hard declines as generally non-retryable by default. Account Updater checks for card changes about a week ahead of renewal and again after an initial decline, catching many hard-decline causes before they reach the customer, while a parallel dunning campaign prompts the customer directly when their action is what is actually needed.

Frequently asked questions

What is a payment decline? It is when a card issuer or processor refuses a transaction, so the payment does not complete. The response includes a reason code that explains why, which determines the right way to respond.

What are the main types of payment decline? Soft declines are temporary, like insufficient funds, and can often succeed if retried later. Hard declines are permanent, like a closed or stolen card, and need the customer to provide a new payment method.

Why do payments get declined? Reasons range from insufficient funds and temporary issuer holds to expired cards, closed accounts, cards reported lost or stolen, and fraud flags. Some are temporary and some are permanent, which is why the reason code matters.

How do you reduce payment declines and their impact? Retry soft declines on a sensible schedule, keep card details current with an updater or self-service flow, prompt customers quickly on hard declines, and monitor decline patterns so you can address ones tied to a particular card type or issuer.

Are payment declines a major cause of churn? Yes. Declines on recurring charges are a leading cause of involuntary churn, where customers lapse because a payment failed rather than because they decided to leave. Recovering those payments protects recurring revenue.