Hard decline

A hard decline is a payment failure that the card issuer signals as permanent, meaning the transaction should not be retried as-is because another attempt on the same card will fail again. Common causes include a closed or canceled account, a card reported lost or stolen, an expired card, or the issuer blocking the transaction outright. Recovering from a hard decline usually requires the customer to take action, such as providing a new or updated payment method, rather than simply retrying the charge. This is the opposite of a soft decline, which is temporary and can often succeed on a later retry.

When a card issuer declines a transaction, it returns a reason code, and those codes fall into two broad groups. A hard decline points to a durable problem with the card or account: the card is closed, expired, reported lost or stolen, or the issuer has decided not to allow the charge. Because the underlying condition will not change on its own, retrying the same card produces the same failure. For subscription businesses, this distinction shapes how failed payments are handled, because it tells the recovery system whether an automatic retry is worth attempting or whether the only path forward is to reach the customer and get updated card details.

Why hard declines matter for subscription businesses

Recurring revenue leaks when payments fail and go unrecovered, and treating hard declines like soft declines wastes effort while annoying customers. Retrying a card that has been closed or reported stolen will never succeed, and repeated attempts can even raise flags with the issuer. Recognizing a hard decline early lets a business stop pointless retries and instead do the one thing that can actually recover the revenue: prompt the customer to update their payment method. Getting this right protects both the revenue and the customer relationship, since customers do not want to see a string of failed charge attempts on an account they need to fix themselves.

How to use hard declines

Use the hard versus soft distinction to drive different recovery actions:

• Read the decline reason code returned by the issuer and classify the failure as hard or soft before deciding what to do.

• For a hard decline, stop retrying the same card and move straight to asking the customer for a new or updated payment method.

• Trigger customer outreach promptly, since a hard decline means access or service is at risk until the card is fixed.

• Keep a card updater or self-service update flow available so customers can resolve a hard decline with as little friction as possible.

Hard decline vs soft decline

Both are declined authorizations, but they call for opposite responses.

• A hard decline is permanent. The card or account has a durable problem, such as being closed, expired, or reported lost or stolen. Retrying the same card will fail again, so recovery depends on getting a new or updated payment method from the customer.

• A soft decline is temporary. The card is generally valid, but the charge failed for a passing reason such as insufficient funds or a temporary issuer hold. A retry a little later often succeeds, which is why soft declines are the main target of automated retry logic.

The practical rule is that soft declines are worth retrying and hard declines are not; hard declines need the customer to act. See Payment decline for the broader category and Authorization for the step where a decline is returned.

Benefits and examples

Handling hard declines correctly saves wasted retry attempts and focuses recovery on the action that works. For example, if a customer's card was reported stolen and reissued with a new number, every automatic retry on the old card is a hard decline. Rather than cycling through retries, the business emails the customer to update their card, and the subscription resumes once they do. The result is faster recovery, fewer failed attempts on record, and a customer who is guided to the fix instead of left guessing.

A subscription management platform helps here by classifying declines automatically and routing each type to the right recovery path. Instead of a team reading raw issuer codes, an integrated system can tell a hard decline from a soft one, skip futile retries, and launch customer outreach or a payment update flow for the cases that need it. At the operator level, that means more recovered revenue with less manual triage and fewer wasted retries. Recurly's Intelligent Retries classifies hard declines as generally non-retryable and skips futile retries by default, while Account Updater proactively checks for card changes about a week ahead of renewal and again after an initial decline, catching many hard-decline causes, like an expired or reissued card, before they ever reach the customer.

Frequently asked questions

What is a hard decline? It is a payment failure the issuer marks as permanent, usually because the card or account has a lasting problem like being closed, expired, or reported lost or stolen. Retrying the same card will not work; the customer needs to provide a new payment method.

What is the difference between a hard decline and a soft decline? A hard decline is permanent and will fail again on retry, so it needs the customer to update their card. A soft decline is temporary, such as insufficient funds, and can often succeed if you retry later.

Should you retry a hard decline? No, not on the same card. The underlying problem will not resolve on its own, so retrying just produces the same failure. Instead, reach the customer and ask them to update their payment method.

What causes a hard decline? Typical causes include a closed or canceled account, an expired card, a card reported lost or stolen, or the issuer refusing the transaction. The common thread is that the condition will not change without the customer acting.

How do you recover from a hard decline? Prompt the customer to update or replace their payment method, ideally through a simple self-service flow or a card updater, then resume billing once a valid card is on file.