A soft decline is an authorization decline that is temporary in nature and may be resolved by retrying the transaction, often with additional information or after a short waiting period. Unlike a hard decline, which indicates a permanent problem with the card or account that will not be resolved by retrying, a soft decline signals that the issuer was unable to approve the transaction under the current conditions but may approve it under different circumstances.
Common causes of soft declines include temporary holds on the account, fraud prevention triggers that require additional cardholder verification, insufficient funds that may be resolved by the cardholder’s next deposit, or issuer system issues that prevented normal authorization processing. The specific reason is communicated through a decline response code that the gateway or processor uses to determine whether and how to retry the transaction.
Soft decline management is a meaningful revenue recovery opportunity for merchants, particularly in subscription billing and recurring payment environments where a declined transaction that is not retried results in lost revenue and potential customer churn.
Diving Deeper into Soft Decline
Authorization declines are not all created equal. The difference between a soft decline and a hard decline determines whether a merchant should retry a transaction, how they should retry it, and what the likely outcome of a retry will be. Understanding this distinction and building appropriate retry logic into payment workflows is one of the more accessible and high-impact optimizations available to merchants processing recurring or subscription payments.
Soft Decline vs. Hard Decline
The fundamental distinction between soft and hard declines is whether the underlying issue is temporary or permanent.
A hard decline indicates a permanent problem. The card has been reported lost or stolen, the account is closed, the card number is invalid, or the issuer has placed a permanent block on the account. Retrying a hard-declined transaction is pointless and may be counterproductive — some issuers flag merchants who repeatedly retry hard-declined cards as potential fraud signals.
A soft decline indicates a temporary condition. The transaction failed this time, but the same card might succeed if tried again under different conditions. The appropriate response to a soft decline depends on the specific decline code and the context of the transaction.
Common Soft Decline Codes
Card networks and issuers use standardized response codes to communicate the reason for a decline. Soft decline codes signal temporary conditions that may be retriable.
Insufficient Funds
Decline code 51 indicates the cardholder does not have sufficient funds or credit available to cover the transaction amount at the time of authorization. For debit card transactions, this may resolve after the cardholder’s next deposit. For credit cards, it may resolve after the billing cycle closes and available credit is restored. Retrying after a few days is often effective for this decline code.
Do Not Honor
Decline code 05, do not honor, is a broad code that issuers use when they decline a transaction for reasons they do not wish to specify. It is one of the most common soft decline codes and can indicate anything from fraud scoring concerns to temporary account restrictions. Retrying after a short delay is sometimes effective, though repeated do not honor responses suggest the issuer has a persistent concern about the transaction.
Issuer Temporarily Unavailable
Codes indicating that the issuer’s system was unavailable or that the transaction timed out are clearly temporary and warrant immediate retry. These declines occur when the issuer’s authorization system experiences downtime or latency rather than when the issuer has made a deliberate decision to decline the transaction.
Refer to Card Issuer
This response indicates the issuer wants the cardholder to contact them before the transaction proceeds. In card-present environments, this code may prompt the terminal to request that the cardholder call their bank. In card-not-present environments, it typically signals that additional cardholder verification is needed and may be addressed through 3D Secure authentication or by having the cardholder contact their issuer.
Retry Logic and Best Practices
Card networks publish guidelines for retry behavior that merchants and processors should follow. Retrying declines too aggressively — submitting the same transaction multiple times in rapid succession — can trigger fraud flags at the issuer and result in the card being blocked for that merchant. Card networks impose limits on retry attempts and may fine merchants or processors who exceed them.
Effective retry logic varies the timing and sometimes the transaction amount based on the specific decline code. A transaction declined for insufficient funds is best retried after several days. A transaction declined due to issuer unavailability can be retried immediately. A transaction declined with a do not honor code should be retried once after a day or two, and if the second attempt fails, treated as effectively a hard decline.
Soft Declines in Subscription Billing
Subscription and recurring billing businesses are most directly affected by soft decline management because their revenue depends on successfully charging stored payment credentials on a defined schedule. A subscriber whose card declines on the billing date is at risk of involuntary churn — the loss of a customer not because they chose to cancel but because the payment did not process successfully.
Dunning management systems automate the process of retrying failed recurring payments according to optimized retry schedules, updating customers on payment failures, and collecting updated payment credentials when retries are exhausted. Well-implemented dunning can recover a significant percentage of initially declined recurring transactions, directly improving subscription revenue retention.
Network-Specific Retry Rules
Visa and Mastercard have both tightened their retry rules in recent years in response to excessive retry behavior by some merchants. Visa’s retry rules limit the number of times a declined transaction can be retried within defined time windows and impose fees for excessive retries. Mastercard has similar restrictions. Merchants using automated retry logic must ensure their systems comply with current network retry rules to avoid fees and potential compliance issues.