.svg)
.svg)
.svg)
.svg)
.svg)
The unified orchestration layer for wallets and alternative payments
.svg)
The secure repository for all your payment methods
.svg)
Workflow-driven payments intelligence for smarter routing and higher auth rates
.svg)
A flexible fraud and authentication layer. Instantly add advanced fraud tools and 3DS
One integration to sell inside ChatGPT, Gemini, and every agentic platform
The visual workflow builder that ties fraud, identity, and payment routing together in one place
The unified orchestration layer for wallets and alternative payments
The secure repository for all your payment methods
Workflow-driven payments intelligence for smarter routing and higher auth rates
A flexible fraud and authentication layer. Instantly add advanced fraud tools and 3DS
One integration to sell inside ChatGPT, Gemini, and every agentic platform
The visual workflow builder that ties fraud, identity, and payment routing together in one place
Soft Decline
A soft decline is a payment decline caused by a temporary or potentially recoverable condition, one where the transaction may succeed if retried at the right time, through a different gateway, or after a specific action (such as the cardholder authenticating through 3DS or updating their payment details). Soft declines are distinguished from Hard Declines by the recoverability of the underlying condition.
Common soft decline conditions include: insufficient funds (the cardholder's account balance is temporarily low but may be replenished), "do not honor" responses from risk scoring (a temporary flag that may not recur on a subsequent attempt), Strong Customer Authentication (SCA) required (the issuer is requesting additional authentication before approving, not a refusal, but a redirect to authentication), and card velocity flags (the card has been used for many transactions in a short window, a pattern the issuer flagged but which may clear on retry).
The "65, Authentication Required" response is a particularly important soft decline in SCA-mandated markets. When an issuer returns this code, it is not declining the transaction on its merits, it is requesting that the merchant submit the transaction with 3DS2 authentication. A well-configured payment system recognizes this response and re-submits the transaction through a 3DS flow rather than treating it as a final decline. Merchants who do not have this handling in place effectively lose transactions that would succeed with authentication.
Soft declines are the primary target of Retry Logic and Decline Salvage / Cascading strategies. Not all soft declines should be retried identically, a "insufficient funds" decline at 11 PM may succeed if retried the following morning after payroll has cleared; an "authentication required" decline should trigger a 3DS flow rather than a bare retry; a "do not honor" may succeed on a different gateway with a different acquiring path to the issuer.
Frequently Asked Questions
How quickly should a soft decline be retried?
Retry timing depends on the decline code. "Insufficient funds" declines are generally best retried after 24-72 hours to give the cardholder time to fund their account. "Do not honor" declines may be worth retrying within a few hours, the issuer's risk flag may have cleared. "Authentication required" declines should trigger immediate re-submission through a 3DS flow rather than a time-delayed retry.
What are card network retry limits for soft declines?
Visa and Mastercard have both published explicit retry guidelines for declined transactions. For transactions declined with "do not honor" or "insufficient funds" codes, card networks generally permit up to 15 retries over a 30-day period, with specific minimum intervals between attempts. Exceeding these limits, aggressive retry patterns that hammer declined cards dozens of times, can result in issuer blocks and network-imposed fees.
How do soft declines affect subscription revenue?
Soft declines are a primary driver of Involuntary Churn in subscription businesses. A monthly subscription renewal that hits a soft decline, insufficient funds at the time of charge, a temporary risk flag, an expired card, may not recover if the merchant lacks appropriate retry logic. The subscriber did not intend to cancel, but the payment failure results in service interruption and, frequently, subscriber loss.
