The difference between a soft decline and a hard decline comes down to whether the card can work later. A soft decline is temporary: the card is valid, but the issuing bank won’t approve this specific charge right now. A hard decline is permanent for that card: the issuer has decided the transaction cannot proceed, and retrying will produce the same result. That single distinction controls what you do next. Soft declines can be recovered with a well-timed retry. Hard declines require a different card or payment method, and retrying them costs you money in network fees without ever succeeding.
What Triggers a Soft Decline
A soft decline happens when the issuing bank recognizes the card as legitimate but blocks a specific charge at that moment. The account is open and in good standing. Typical causes include insufficient funds or an over-limit credit line, a daily or per-transaction spending cap being hit, a temporary issuer system outage, a fraud flag placed for review rather than a permanent block, and, in regions with Strong Customer Authentication rules, a missing two-factor verification step the issuer expects the merchant to resubmit.
Cross-border transactions get soft-declined at noticeably higher rates than domestic ones. When a card issued in one country is used at a merchant in another, the issuing bank faces higher fraud risk and more complex settlement, so it tightens its authorization criteria.
The common thread: the underlying problem can clear on its own or with a small change. The customer deposits funds, a daily limit resets at midnight, or the bank’s authorization system comes back online. That’s why retrying is a reasonable strategy for soft declines.
What Triggers a Hard Decline
A hard decline signals a permanent problem with the card itself. Common causes are a closed account, an invalid card number (from a typo or a fabricated number), a card the issuer has flagged as lost or stolen, an expired card with no activated replacement, a CVV mismatch, or a card that’s been restricted for the transaction type, merchant category, or geographic region.
When any of these come back, retrying the same card wastes processing resources and, as covered below, risks fines from the card networks. The only path forward is to contact the customer and request a different payment method.
How Response Codes Tell You Which One You Got
Every failed transaction returns a numeric response code from the issuing bank, based on the ISO 8583 messaging standard. These codes appear in your payment gateway dashboard or API logs and explain why the charge was refused. Code 51, for example, means insufficient funds; code 41 means the card was reported lost.1Google for Developers. Standard Payments – Response Codes Most gateways also translate the number into a plain description like “Expired Card” or “Exceeds withdrawal limit.”
A short list worth memorizing:
- 05 (Do Not Honor): a general-purpose decline. The issuer won’t say why. It can be either soft or hard depending on the issuer’s internal reasoning, which makes it the most frustrating code to receive.2Mastercard Developers. Network Response Codes
- 51 (Insufficient Funds): classic soft decline. The account is valid but can’t cover the charge.2Mastercard Developers. Network Response Codes
- 14 (Invalid Account Number): hard decline. The number doesn’t match any account.
- 41 or 43 (Lost or Stolen Card): hard decline. The issuer wants the card stopped.
- 91 (Issuer Unavailable): soft decline. The bank’s system is temporarily down.1Google for Developers. Standard Payments – Response Codes
- 54 (Expired Card): hard decline. Waiting won’t fix it.
Code 05 deserves special caution. Visa treats it as a Category 1 decline when there’s no reasonable expectation of recovery, meaning no retries. But some processors map it to a softer category. If your gateway marks a “Do Not Honor” as retryable, one or two carefully spaced retries are reasonable; back off quickly if they fail.
Retry Limits and What Excessive Retries Cost
Card networks don’t leave retry behavior to merchant discretion. Visa groups every decline code into four categories with different rules. Category 1 covers responses the issuer will never approve, such as lost or stolen cards, closed accounts, and restricted cards; no retries are permitted, and a single retry triggers a fee immediately.3PayPal. How to Avoid Excessive Retries Penalties Category 2 covers issuer-can’t-approve-right-now situations like insufficient funds, spending limits, suspected fraud, and system outages; retries are allowed up to 15 times within 30 days. Category 3 covers bad data such as an incorrect CVV or expiration date, where retries are allowed only after the customer corrects the information. Category 4 is a catch-all with the same 15-attempt, 30-day limit as Category 2.
Mastercard runs a similar program, classifying retries as excessive after 10 declined attempts on the same card within 30 days.
The fees are per transaction. As of April 2026, Visa charges $0.10 per excessive retry on domestic transactions and $0.25 on cross-border, the cross-border figure having jumped 67% from its previous $0.15 level.3PayPal. How to Avoid Excessive Retries Penalties Mastercard’s fees can reach $0.50 per transaction once the retry threshold is breached. These flow from the card network to the acquirer and typically get passed straight through to the merchant.
A dime sounds trivial in isolation. A subscription business with 50,000 customers and a 5% monthly decline rate can generate hundreds of excess retries per billing cycle if retry logic is poorly tuned. The fees compound, and consistently high retry-to-approval ratios can lead acquirers to raise processing rates or, in extreme cases, revoke processing privileges.
Smart Retry Timing for Soft Declines
When you retry matters as much as whether you retry. Blasting the same charge five minutes after a soft decline almost never works and burns through your retry allowance for nothing.
For insufficient funds, wait three to five days. Retrying immediately after an empty-account decline wastes an attempt because the money isn’t there yet. Aligning retries with typical customer payday patterns improves recovery. For “do not honor” responses, wait 24 to 72 hours to give the issuer time to clear whatever internal flag caused the decline. For velocity or spending-limit issues, 24 hours usually lets the daily cap reset.
Technical failures are the exception. When the code indicates a system outage or network timeout, such as 91 or 96, retrying within minutes often succeeds because the infrastructure problem has already resolved.
An exponential backoff pattern works well as a default: retry after 1 day, then 3 days, then 7 days, then 14 days. This front-loads attempts when recovery is most likely and tapers off before you annoy the customer or trip network limits. Most successful retries happen within the first three attempts. If three well-timed retries all fail, the odds of a fourth working are slim.
Handling Hard Declines
The response to a hard decline is simple: stop charging that card and reach out to the customer. The details still matter.
For codes flagging lost or stolen cards (41, 43) or suspected fraud, document the transaction and follow your fraud protocols. If the order includes physical goods that haven’t shipped, hold the shipment. These codes sometimes surface during legitimate purchases when the cardholder recently reported a lost wallet and then found it, so contacting the customer before canceling outright is worth doing.
For expired cards, invalid numbers, and closed accounts, you just need updated payment information. An automated email with a direct link to update the card on file resolves most of these without any human intervention. A brief, friendly message recovers more accounts than a formal or alarming one.
One tool prevents many hard declines before they happen: automatic account updater services. When a bank reissues a card with a new number or expiration date, it sends the updated details to the card network. Merchants enrolled in Visa Account Updater or Mastercard’s Automatic Billing Updater can pull those updates automatically, keeping stored cards current without any customer action.4Visa Developer. Visa Account Updater Overview Up to 15% of payment declines stem from outdated card details, so account updater enrollment eliminates a meaningful slice of hard declines entirely.
Why the Distinction Matters for Subscription Revenue
Failed payments quietly drain subscription businesses. Involuntary churn, where customers leave because their payment method stopped working rather than because they chose to cancel, accounts for an estimated 20% to 40% of total churn in SaaS and subscription companies. The average subscription business loses roughly 9% of its monthly recurring revenue to failed payments each year.
Treating every decline the same way is what makes this expensive. Retrying hard declines racks up network fees while never recovering the charge. Retrying soft declines too quickly wastes attempts before the underlying condition has cleared. A dunning process that reads the response code, waits the right interval for genuinely retryable declines, and pivots to customer outreach for the rest captures the majority of recoverable revenue. On the day a payment fails, a plain email explaining what happened with a two-click update link is the baseline. Follow-ups spaced across the next 30 days, and an in-app banner during the dunning window, catch customers who ignore email.
Does a Decline Affect the Customer’s Credit Score?
No. A declined transaction does not appear on a credit report and does not affect a credit score, whether the decline is soft or hard.5Experian. Does Having Your Credit Card Declined Hurt Your Credit? Card networks and issuing banks do not report individual transaction outcomes to Equifax, Experian, or TransUnion.
The underlying cause can still matter indirectly. A card that’s maxed out month after month carries a high utilization ratio that drags a score down, but the decline itself isn’t the mechanism. Banks also keep internal risk profiles separate from credit bureau data, and repeated declines or rapid transaction attempts can trigger fraud systems that impose temporary account restrictions, which then cause more declines in a cascade.