Hard vs soft declines
DEFINITION
A hard decline is a permanent card refusal that will not succeed on retry, while a soft decline is a temporary failure, such as insufficient funds, that may succeed if the charge is attempted again. Recurly reads the issuer's decline code to decide whether to retry.
TABLE OF CONTENTS
RELATED TERMS
A hard decline and a soft decline are the two categories a failed card payment falls into. A hard decline is a permanent refusal that will not succeed on retry, such as a closed account, a reported-stolen card, or a blocked transaction. A soft decline is a temporary failure that may well succeed if attempted again, such as insufficient funds, a temporary hold, or a network timeout.
The distinction matters because it decides what to do next. A soft decline is worth retrying, since the underlying issue often clears on its own, while a hard decline calls for a different response, usually asking the customer to update their payment details, because retrying the same card will keep failing. The issuer signals which category applies through the decline response code returned with the failure. A subscription platform such as Recurly reads these response codes to guide its recovery flow, and the exact mapping of codes to retry behavior it uses is that hard declines are treated as generally non-retryable by default, while soft declines are scheduled for retry based on the specific decline reason rather than a single fixed schedule.
Why hard and soft declines matter for subscription businesses
Recurring billing generates repeated charges, so declines are a constant fact of subscription life and a leading cause of involuntary churn. Treating every decline the same wastes effort and can make matters worse. Retrying a hard decline over and over will never work and can draw issuer scrutiny, while giving up on a soft decline throws away revenue that a well-timed retry would have recovered.
Sorting declines into the right category lets a business:
Retry soft declines intelligently, recovering payments that fail only temporarily.
Route hard declines straight to a customer prompt to update their card, rather than retrying in vain.
Protect its standing with issuers by not hammering cards that will never approve.
Getting this right directly affects how much revenue is recovered rather than lost to failed renewals.
How to tell hard and soft declines apart
The issuer's response code is what separates the two, and the recovery flow branches on it. In practice:
A card charge is declined and the issuer returns a decline response code.
The code is classified as a hard or a soft decline.
Soft declines are queued for a retry, ideally timed to when the charge is more likely to succeed.
Hard declines skip retries and trigger a request for the customer to update their payment method.
Dunning notifications keep the customer informed while recovery is attempted.
If recovery does not succeed within the configured window, the subscription follows its end-of-dunning rule.
Some declines are ambiguous or vary by issuer, so the mapping is not always clean.
Hard declines vs soft declines
The two categories differ mainly in whether the failure is permanent and what the right response is:
A hard decline is permanent. Common causes include a closed or invalid account, a card reported lost or stolen, or a transaction blocked by the issuer. The right response is to stop retrying and ask for new payment details.
A soft decline is temporary. Common causes include insufficient funds, a temporary hold, an expired authorization, or a processing or network error. The right response is to retry, ideally with smart timing.
The shared goal for both is to recover the payment where possible and to keep the subscription active without annoying the customer or the issuer.
Benefits and examples
Distinguishing hard from soft declines helps a subscription business recover more revenue, avoid wasted retries, and protect its relationship with card issuers. In practice that means higher recovery on temporary failures, fewer pointless retries on permanent ones, and dunning that asks the customer to act only when they actually need to.
As an illustrative scenario, imagine two failed renewals on the same day. One returns an insufficient-funds code, a soft decline, so the system schedules a retry for a few days later and the charge succeeds after payday. The other returns a lost-or-stolen-card code, a hard decline, so the system skips retries and emails the customer to add a new card. Handling each by its category recovers the first without harassing the second. This example is hypothetical.
Frequently asked questions
What is the difference between a hard decline and a soft decline? A hard decline is a permanent refusal that will not succeed on retry, such as a closed account or a stolen card. A soft decline is a temporary failure, such as insufficient funds or a network error, that may succeed if the charge is attempted again.
Should you retry a hard decline? No. A hard decline will keep failing on the same card, and repeated attempts can draw issuer scrutiny. The right step is to ask the customer to update their payment details.
How do you know if a decline is hard or soft? The issuer returns a decline response code with the failure, and that code classifies the decline. Billing systems map the codes to retry or no-retry behavior, and Recurly's mapping treats hard declines as non-retryable by default, with exceptions for cases like a billing information update.
How do declines relate to involuntary churn? Failed renewals are a primary source of involuntary churn. Recovering soft declines through well-timed retries and prompting customers to fix hard declines keeps subscribers who would otherwise be lost to a payment failure.
