Soft Decline

Unlike a hard decline which is a permanent rejection indicating the card cannot be used for that transaction under any circumstances a soft decline signals that the barrier to authorization is conditional and potentially removable. The same card, on the same merchant, may successfully authorize on a subsequent attempt once the underlying condition is resolved.

How Soft Declines Work?

When a transaction is submitted for authorization, the issuing bank evaluates it against a set of criteria available funds, fraud signals, card status, transaction limits, and authentication requirements. When the evaluation fails on a temporary or conditional basis rather than a permanent one, the issuing bank returns a soft decline code that indicates the nature of the issue and implicitly the action required to resolve it.

The acquiring bank or payment processor receives the decline code, classifies it as soft or hard based on the code type, and returns the result to the merchant's payment infrastructure. A well-configured payment system recognizes soft decline codes and triggers the appropriate response an automatic retry, a step-up authentication request, or a customer notification rather than treating the decline as a final rejection.

Common Soft Decline Reasons

Insufficient funds: the cardholder's account does not have sufficient available balance or credit to cover the transaction amount at the moment of authorization. The most common soft decline reason. Retrying at a later time when funds may have been replenished or offering a lower transaction amount can resolve this decline type.

Temporary hold or freeze: the issuing bank has placed a temporary restriction on the card due to suspected fraud, a disputed transaction under investigation, or a routine security review. The hold is typically lifted within hours or days without permanent impact on the card's usability.

Transaction limit exceeded: the transaction amount exceeds a daily, weekly, or per-transaction limit set by the issuing bank or the cardholder. Splitting the transaction into smaller amounts or retrying after the limit resets may resolve the decline.

Authentication required: the issuing bank requires additional cardholder verification before approving the transaction typically a 3D Secure challenge but the initial authorization attempt did not include the required authentication step. Triggering a 3DS challenge flow resolves this decline type without requiring the customer to re-enter payment details.

Card velocity limit: the card has been used too many times within a defined window, triggering the issuing bank's fraud velocity controls. Retrying after the velocity window resets typically resolves this decline.

Do not honor general: a broad soft decline code that indicates the issuing bank is declining the transaction without specifying a precise reason. Often triggered by fraud scoring models that flag the transaction as elevated risk. May resolve on retry if the fraud signal was a false positive, or may require the cardholder to contact their bank directly.

Soft Decline vs. Hard Decline

The distinction between soft and hard declines is the most important classification in authorization rate optimization:

• A soft decline is temporary and potentially recoverable. The appropriate response is a structured retry strategy or a step-up authentication request not immediate abandonment of the transaction.

A hard decline is permanent and unrecoverable in the current transaction context. Common hard decline reasons include a stolen or blocked card, an invalid card number, an expired card, or a closed account. Retrying a hard decline wastes authorization attempts, risks triggering additional fraud flags, and will not produce a different outcome. The appropriate response is to request an alternative payment method from the customer.

Soft DeclineHard DeclineNatureTemporary, conditionalPermanent, unconditionalRetry appropriateYes, with strategyNoCommon causesInsufficient funds, auth required, velocity limitStolen card, invalid number, closed accountCustomer action neededSometimesAlmost alwaysResolutionRetry, authentication, timingNew payment method

Soft Declines in Recurring Payments and Subscriptions

Soft declines are particularly consequential for subscription businesses where the same payment credential is charged repeatedly over an extended period. A soft decline on a recurring charge most commonly due to insufficient funds or an expired card that has been reissued can trigger involuntary churn if not handled correctly.

A payment infrastructure that treats all declines as final and immediately cancels the subscription or suspends access will churn customers whose payment failure was temporary and self-resolving. A well-configured retry logic that recognizes soft decline codes and retries at optimized intervals recovers a meaningful proportion of these failures before they become permanent churn events.

Dunning management: the practice of systematically retrying failed payments and communicating with customers about payment issues is built around the soft decline recovery opportunity. An effective dunning sequence retries at intervals calibrated to the most common soft decline resolution windows, escalates to customer communication when automated retries are exhausted, and captures the outcome data needed to continuously optimize the retry strategy.

Retry Strategy for Soft Declines

Not all soft declines should be retried in the same way. An intelligent retry strategy calibrates timing, frequency, and approach based on the specific decline code:

Insufficient funds: retry at the end of the month or beginning of the following month when salary payments are most likely to have replenished the account. Retrying on the day after a failed insufficient funds decline rarely produces a different outcome.

Authentication required: do not retry silently. Trigger the appropriate authentication flow 3DS challenge and route the cardholder through it before resubmitting the authorization. Silent retries on authentication-required declines will produce the same result.

Do not honor general: retry once after 24 hours. If the second attempt also fails, escalate to customer communication rather than continuing to retry, as persistent do-not-honor declines often indicate the issuing bank has flagged the transaction for manual review.

Velocity limit exceeded: wait for the velocity window to reset typically 24 hours before retrying.

Card network retry rules govern how frequently and under what conditions a declined transaction can be retried. Visa and Mastercard publish specific retry guidelines that define the maximum number of retries permitted for different decline codes within defined time windows. Exceeding these limits risks scheme non-compliance fees and potential acquiring bank penalties.

Soft Declines and Authorization Rate Optimization

For any business processing at meaningful volume, the soft decline rate and the recovery rate on retried soft declines are among the most commercially significant metrics in the payment stack.

A 5% soft decline rate on a business processing $1,000,000 per month represents $50,000 of potentially recoverable revenue per month before any retry recovery is applied. A retry strategy that recovers 40% of soft declines converts $20,000 of that potential monthly loss into recognized revenue. Compounded annually, the difference between no retry logic and optimized retry logic on soft declines alone can represent hundreds of thousands of dollars in recovered revenue.

Related words

• Network token
• Payment Token
• Interchange Fee‍
• Payout Fee
• Chargeback Fee
• 3d Secure
• Scheme Fee