Time for a Level Playing Field for Regulated UK Gambling Payments
Download Whitepaper
Transaction Processing

Soft Decline

What Is a Soft Decline? Definition and How It Works

Definition

A soft decline is an authorisation response indicating that the transaction was not approved due to a temporary or conditional reason, and the transaction may be retried or recovered through alternative actions such as step-up authentication or a retry at a later time.

How it works

Soft declines communicate that the decline condition is not permanent. The most common soft decline code is 05 (Do Not Honor), a generic issuer decline that may reflect a momentary risk assessment decision, a temporary account issue, or an issuer system applying cautious logic to an unfamiliar transaction pattern. Other soft decline codes include 51 (Insufficient Funds) and 65 (Transaction Not Permitted), as well as SCA-related codes that request step-up authentication.

Card scheme rules permit retrying soft declines, but with restrictions on timing and frequency. Visa and Mastercard each publish specific retry rules that define how many times a soft-declined transaction can be retried, with what minimum waiting period between attempts, and for what duration after the first decline. These rules are designed to prevent merchants from flooding issuers with repeated authorisation attempts on transactions the issuer has already declined.

SCA-related soft declines are a distinct subcategory: when an EEA issuer returns a soft decline because SCA authentication is required, the merchant should not simply retry the same transaction. The correct response is to initiate a 3DS authentication flow and then resubmit the authorisation with the authentication result.

The distinction between soft and hard declines must be enforced in automated retry systems. A retry system that treats all declines the same will retry hard declines (which is a scheme rule violation) and may also miss the specific handling required for SCA-related soft declines.

Why it matters

Retry strategy for soft declines has measurable revenue recovery potential: a well-configured retry system that applies the correct timing and frequency for each soft decline code category can recover 2-5% of soft-declined transactions. This is incremental revenue at zero acquisition cost.

Scheme retry rules must be followed precisely: card networks publish explicit retry rules with waiting periods and maximum attempt counts. Violating these, submitting too many retries or retrying too quickly, results in scheme fines that can be substantial for high-volume merchants.

Soft decline codes require classification, not just identification: the handling for a 05 (Do Not Honor) differs from a 65 (SCA Required) differs from a 51 (Insufficient Funds). Retry systems should map each decline code to the appropriate recovery action: wait and retry, initiate 3DS, request alternative payment method, or abandon.

Retry timing windows are scheme-specific: Visa and Mastercard retry rules differ. A merchant operating with both Visa and Mastercard cards must apply the correct retry window for each. Unified retry logic that applies a single rule across all card types will violate one scheme's rules.

With PXP

PXP's platform classifies decline codes as soft or hard at the point of receipt and applies scheme-compliant retry logic automatically. SCA-related soft declines trigger 3DS step-up flows where supported. Retry performance, including recovery rates by decline code, is reported in PXP's analytics dashboard.

Talk to a payments specialist

Frequently asked questions

What is the difference between a soft decline and a hard decline?

A soft decline indicates a temporary or conditional reason for non-approval, the transaction may succeed on retry or with additional authentication. A hard decline indicates a permanent card-level condition such as a stolen or restricted card, retrying is prohibited by scheme rules. The classification determines the correct merchant response: retry with appropriate timing for soft declines; remove from stored credentials and do not retry for hard declines.

How long should merchants wait before retrying a soft decline?

Retry timing depends on the decline code and the card scheme. Visa's retry rules specify minimum waiting periods for each decline code category, many require at least 24 hours between attempts. Mastercard has similar but not identical rules. Merchants should consult the current published retry rules for each scheme rather than applying a single universal wait time. Retrying before the mandated waiting period is a scheme rule violation.

Can all soft declines be recovered through retry?

No. Retry is appropriate for codes where the decline condition is likely to have resolved with time (Insufficient Funds, Do Not Honor). Some soft declines indicate a specific required action: SCA-related codes require step-up authentication, not a simple retry. If the same soft decline code repeats across multiple retry attempts, the condition may not be as temporary as the code implies, and the transaction should be abandoned to avoid violating retry frequency limits.

What is the revenue impact of optimising soft decline retry?

The recoverable revenue from soft decline retry depends on the volume of soft declines and the retry success rate. Merchants with 5% soft decline rates and 25% retry success rates on eligible declines recover approximately 1.25 percentage points of otherwise-lost authorisation rate. On $200M of annual card volume, that is approximately $2.5M in recovered transactions. The actual impact depends on the merchant's decline code mix and the quality of retry timing and logic.