What Is Soft Decline? Definition, Payment Flow, and Examples
Soft Decline is a decline that may be resolved by added authentication, corrected data, or a later retry, depending on the reason. This guide focuses on Soft Decline's real role, boundaries, and common points of confusion.
Key points
- Definition: Soft Decline is a decline that may be resolved by added authentication, corrected data, or a later retry, depending on the reason.
- Flow position: The merchant sends an authorization request, and the issuer side returns an approval or decline based on account, amount, credentials, risk, and product rules.
- Do not confuse: Soft Decline / Hard Decline
How it fits into the payment flow
For Soft Decline, the relevant process is as follows: The merchant sends an authorization request, and the issuer side returns an approval or decline based on account, amount, credentials, risk, and product rules. Authorization codes, response data, and decline codes describe that decision; they are not capture, posting, or final merchant funding.
A practical review of Soft Decline should account for this: A merchant should handle declines according to response information and network rules without exposing sensitive internal detail. A soft decline may support an appropriate authentication or retry path, while repeated submission is not a sound answer to a hard decline.
Practical example
An issuer returns a soft decline because more authentication is needed, and the merchant follows a supported 3DS path before resubmitting. The retry addresses a known reason instead of looping indefinitely.
How it differs from related terms
| Term | Definition |
|---|---|
| Soft Decline | is a decline that may be resolved by added authentication, corrected data, or a later retry, depending on the reason |
| Hard Decline | is a decline that generally should not be retried immediately with the same credentials because of invalidity, restrictions, or a firm risk decision |
| Decline Code | indicates a category of reason or handling guidance when a transaction is not approved, often simplified in customer-facing messages |
Soft Decline focuses on the fact that it is a decline that may be resolved by added authentication, corrected data, or a later retry, depending on the reason. Hard Decline, by contrast, is a decline that generally should not be retried immediately with the same credentials because of invalidity, restrictions, or a firm risk decision. They can appear in one transaction while answering different questions.
Use cases and limits
A key limit of Soft Decline is the following: blind retries can create duplicate holds, trigger controls, or worsen the customer experience. Approval is only a prerequisite for later processing; fulfillment and final accounting remain separate.
Frequently asked questions
These answers address two common search questions about Soft Decline.
Is it the same as Hard Decline?
No. Soft Decline is a decline that may be resolved by added authentication, corrected data, or a later retry, depending on the reason. Hard Decline is a decline that generally should not be retried immediately with the same credentials because of invalidity, restrictions, or a firm risk decision. Compare the object, processing stage, and responsible party.
Does an authorization code mean the merchant has received funds?
For Soft Decline, no. It relates to the authorization decision. Posting and interparty settlement generally follow capture, clearing, and settlement steps.
These primary sources support the definition and process for Soft Decline. Current product, network, and local rules still control a real transaction.