Soft decline vs. hard decline: what's the difference?

Every card decline is the issuing bank — not the processor — refusing a charge, but the reason behind the refusal determines whether the same card can ever succeed. That is the line between a soft decline and a hard decline.

A soft decline is temporary. The card itself is valid and active; something about this specific attempt failed — the balance was short, a hold tied up available funds, or the issuer's velocity rules flagged too many recent charges. The same card frequently clears on a later attempt once the condition passes.

A hard decline is permanent for that card. The account is closed, the card was reported lost or stolen, or the issuer suspects fraud. No amount of retrying recovers it; the customer has to supply a different payment method.

The ISO 8583 response code the issuer returns tells you which bucket a decline falls into, and processors map those codes to their own labels.

• Soft: 51 Insufficient Funds, 61 Exceeds Withdrawal Limit, 65 Activity Limit Exceeded, 91 Issuer Unavailable.
• Hard: 41 Lost Card, 43 Stolen Card, 46 Closed Account, 14 Invalid Card Number.
• Ambiguous: 05 Do Not Honor is a generic refusal that can be either — treat it as a cautious soft decline and limit retries.

Treating both types the same wastes effort and money. Hammering a hard decline with retries burns through attempts, annoys the issuer, and can erode your merchant-account standing with the card networks — all for a card that will never work.

The right response is split. Soft declines get retries timed to when funds are likely available (a payday cadence for insufficient funds) plus a light nudge. Hard declines skip retries entirely and go straight to a message asking the customer to update their card. Revatto runs both paths for you — AI times the soft-decline retries and a real team handles the outreach over email and SMS — and you only pay when the payment is recovered (20% of the first recovered payment, $0 monthly).