Soft Decline

Issuers return a reason code with every declined authorisation. The distinction between soft and hard declines determines whether a retry is worth attempting and what form it should take.

Hard vs Soft Declines

Hard declines are permanent rejections:

• Do not honour – fraud — card flagged as compromised
• Stolen card — card reported to issuer
• Restricted card — card blocked for all transactions
• Invalid account number — account closed or doesn’t exist

Retrying a hard decline wastes processing cost and can generate negative signals for your merchant profile. The correct response is to abandon and, for recurring billing, contact the customer.

Soft declines are conditional rejections that may resolve:

• Do not honour (generic code 05) — catch-all; issuer preference, risk model, or daily spend limit. Resolves in 3–7 days.
• Insufficient funds (51) — balance too low at time of transaction. Often resolves 24–48 hours later (post-payday or daily limit reset).
• Transaction not permitted (57) — card control setting (e.g., card not enabled for CNP). May resolve if cardholder updates settings.
• Exceeds withdrawal limit (61) — daily/weekly limit hit. Resolves at next reset window.
• Authentication required (65 / SCA) — issuer requires 3DS challenge. Retry with 3DS authentication flow.

Technical declines are infrastructure failures, not issuer rejections:

• Processing timeout
• Network unavailability
• System error

Retry technical declines immediately via a different routing path.

Soft Decline Recovery Strategies

Timing by reason code. Retrying immediately after a soft decline often fails and can compound the problem. Insufficient funds declines resolve most frequently 24–48 hours after initial decline. Do not honour (generic) resolves more frequently after 3–7 days. Using decline-code-specific retry timing curves — available from PSPs and retry optimisation tools — materially improves recovery rates versus fixed-interval retry.

Account updater before retry. Visa Account Updater (VAU) and Mastercard Automatic Billing Updater (ABU) let merchants query whether a stored card has been replaced. Querying before a retry eliminates the sub-category of soft declines caused by card reissue.

3DS2 retry path. Many issuers who soft-decline a standard CNP authorisation will approve the same transaction if presented via 3DS2 frictionless authentication. The liability shift makes the issuer more willing to approve.

Impact

On subscription merchants, 2–4% of recurring authorisation attempts are soft declines that are recoverable with appropriate retry strategy. On $10M monthly recurring volume, that’s $200,000–$400,000 in revenue that retries correctly — or churns if not retried.