What is a Soft Decline in Card Payments?

A soft decline is a temporary card payment refusal. The issuer hasn't said the card is bad — it's said "not right now, try again later, or fix the thing that's blocking it." Common reasons include insufficient funds, an expired card, an issuer system outage, or a 3D Secure challenge the customer didn't finish. Soft declines are recoverable: a sensible retry logic approach can recover a large slice of them, which is why every modern payment platform separates them from hard declines and treats them differently.

If you've ever had a card payment fail and then go through ten minutes later with no change, you've already met a soft decline. The card is fine. The cardholder is fine. Something around the transaction — the balance, the date, the issuer's authorisation system, an additional check — wasn't right at that exact moment, and the issuer wants the merchant to try again rather than walk away.

That distinction matters more than it sounds. Treating every decline the same way costs merchants serious revenue. Industry data from card networks and payment processors consistently shows that a meaningful share of recurring-billing failures and one-off checkout failures are soft, not hard — and that lifting the recovery rate on those alone can move a business's overall authorisation rate by several percentage points.

Soft Decline vs Hard Decline

The cleanest way to think about it: a soft decline says "come back later," a hard decline says "don't come back at all." Soft declines are transient. Hard declines are permanent — fraud suspected, account closed, card reported lost or stolen, do-not-honour. Retrying a hard decline doesn't help and can actively hurt: extra decline fees, fraud-monitoring flags, and in some cases a temporary block on your merchant account for excessive retries.

The issuer signals which one you've hit through the response code that comes back with the authorisation request. Get those codes wrong and you'll either give up on a recoverable sale or hammer a dead card until the network notices.

Common Soft Decline Codes

Most acquirers send back response codes derived from the ISO 8583 message standard. Codes vary slightly between Visa, Mastercard, Amex, and Discover, but the broad categories line up. The ones you'll see most often on the soft side:

• 51 — Insufficient funds. The card itself is good, the cardholder's balance is the problem. Often clears within hours once payday lands or money moves between accounts.
• 59 — Suspected fraud. The issuer's fraud system has flagged the transaction. The cardholder usually has to confirm the charge through their banking app or call their bank, after which a retry succeeds.
• 61 — Exceeds withdrawal limit. The cardholder has hit a daily or per-transaction limit. Resolves once the limit period rolls over or the cardholder asks their bank for a temporary increase.
• 62 — Restricted card. The card has restrictions on certain merchant categories or geographies. Sometimes resolvable, sometimes not — worth one retry, no more.
• 65 — Exceeds withdrawal frequency. Too many transactions in too short a window. Backing off and retrying later usually works.
• 91 — Issuer unavailable. The issuer's authorisation system is offline or unreachable. Network glitch on their side. Retry in a few minutes.
• 92 — Financial institution unknown. Routing issue between the acquirer and the issuer. Almost always transient.
• 96 — System malfunction. Generic technical failure somewhere in the authorisation chain. Retry is appropriate.

The shape of these codes makes the strategy obvious. "Insufficient funds" is fixable by waiting. "Issuer unavailable" is fixable by retrying. "Suspected fraud" is fixable by the cardholder confirming the charge. None of them are reasons to delete the card from file and chase the customer for a new one.

What a Sensible Retry Strategy Looks Like

Retrying a soft decline well isn't "keep hitting the same card every five minutes until something works." That trips network-imposed velocity limits and triggers fraud monitoring on both the issuer and acquirer side. Useful retry strategies share a few traits.

They wait. A first retry within a few hours catches most issuer-unavailable cases. A second retry the next day catches most insufficient-funds cases — by then, payday has landed or the cardholder has noticed and moved money. A third retry three or four days out catches the rest before the recovery curve flattens.

They use the right network token or updated card details. Most card schemes now run a Card Account Updater (Visa Account Updater, Mastercard Automatic Billing Updater) that pushes new card numbers and expiry dates to merchants when an issuer reissues a card. Retrying with stale details when the actual card has changed is wasted effort.

They throttle. Two or three retries on a single soft-declined transaction is plenty. Beyond that, the card has gone from "temporarily blocked" to "definitely something wrong," and continuing to retry costs you decline fees with no realistic upside.

They prompt the customer when retry alone won't help. Codes like 59 (suspected fraud) need the cardholder to take action. Surfacing a clear message — "Your bank has asked you to confirm this payment, please check your banking app and try again" — recovers transactions that automatic retries never will.

Soft Declines and Recurring Billing

The economic case for treating soft declines properly is sharpest in subscription and recurring-billing businesses. Every failed monthly charge that doesn't get recovered is a churn event — and a large chunk of subscription churn is what the industry calls involuntary churn, where the customer still wants the service but the payment quietly failed.

Card networks publish guidance, and the major payment processors all offer some form of smart retry built around it. Done well, the recovery rate on soft declines in a subscription context can reach 30-70% depending on the customer base, card mix, and retry sophistication.

Soft Declines and Phone Payments

On a live phone payment, a soft decline plays out differently. There's no overnight retry window — the customer is on the line and waiting. The right response is to surface the decline clearly to the agent, explain the likely cause in plain English, and offer the obvious next steps: try a different card, fix the issue with the bank, or use an alternative method like a payment link sent by email or SMS so the customer can retry once they've sorted out the underlying problem.

What you don't want is an agent guessing — telling a customer their card is bad when it's just a temporary fraud check, or vice versa. The response code is the truth; the customer experience depends on translating it into plain language.