Decline recovery
Decline recovery interprets exact response codes from the issuing bank to separate temporary blocks from permanent rejections. Merchants implement issuer decline recovery to map specific failure reasons and apply targeted response workflows that salvage valid transactions safely.
- Category
- Recovery
- Capabilities
- 10
- Available on
- All plans
Payment declines are an inevitable part of online commerce. Cardflo's decline recovery interprets the specific reason codes returned by issuers and acquirers, classifying them to determine the most effective recovery path. This allows for intelligent intervention rather than simply retrying the same transaction.
Merchants can mitigate lost revenue by understanding why a payment failed and responding strategically. Cardflo orchestrates recovery workflows, whether that involves routing to a different acquirer, suggesting an alternative payment method, or prompting the cardholder to update their details.
Cardflo's decline recovery system intelligently retries failed transactions and dynamically routes them to optimal acquirer partners, significantly improving success rates. This process converts previously lost sales into successful authorisations, boosting overall payment performance.
Decline recovery overview
Understanding the precise reason for a declined transaction is the first step towards successful recovery. Cardflo's system parses the numerical and alpha-numeric codes returned by payment gateways, acquirers, and card schemes, cross-referencing them against a comprehensive library of decline meanings.
This deep interpretation allows for differentiation between transient errors, such as a temporary system unavailability, and more permanent issues like insufficient funds or an expired card, guiding subsequent actions with precision and purpose.
Not all declines warrant a recovery attempt; some indicate fraudulent activity or an irreversible customer decision. Cardflo's decline recovery process incorporates a critical assessment of each decline code's recoverability, ensuring that resources are not expended on transactions that are highly unlikely to convert.
This prevents unnecessary processing fees and maintains a positive customer experience by avoiding repeated attempts on irrevocably failed payments, ensuring efficiency in the recovery strategy and protecting merchant profitability.
Once a decline is deemed recoverable, Cardflo automates the appropriate remedial action. This can range from submitting the transaction to an alternative acquirer capable of processing that specific card type or geography, to triggering a prompt for the customer to provide updated payment information.
For recurring payments, it might involve leveraging account updater services. Each recovery path is chosen to maximise the probability of successful conversion while adhering to scheme rules and best practices for customer communication.
How decline recovery works
Decline code interpretation
When an authorisation request is declined, Cardflo captures the raw decline code returned by the payment gateway, acquirer, or issuer. Our system then parses and cross-references this code against a continuously updated database of scheme-specific and acquirer-specific meanings, providing a granular understanding of the failure reason. This initial step is crucial for classifying the decline.
Recovery eligibility assessment
Following interpretation, the decline is assessed for its recovery potential. Declines are classified as temporary (e.g., system error), permanent (e.g., insufficient funds), or irrecoverable (e.g., suspected fraud, lost card). This assessment determines whether any further action is legitimate or if the transaction should be abandoned to prevent unnecessary costs and maintain customer trust.
Orchestrated recovery action
For recoverable declines, Cardflo initiates a pre-configured recovery workflow. This might involve submitting the transaction to a different acquirer with a higher historical success rate for that card type, or sending a direct communication to the cardholder with a secure link to update their payment information. For subscriptions, account updater services are leveraged to obtain new card details automatically.
Performance tracking and reporting
Each recovery attempt and its outcome are meticulously tracked. Merchants receive detailed reports on recovered revenue, success rates for different recovery strategies, and insights into common decline reasons. This data allows for continuous optimisation of recovery rules and provides transparency on the financial impact of improved authorisation rates.
Why decline recovery matters
Maximise recoverable revenue
Simply retrying declined transactions without understanding the cause often leads to further declines and increased processing costs. Cardflo intelligently identifies recoverable transactions, directing resources only to those with a genuine chance of success. This targeted approach directly converts otherwise lost sales into completed payments, significantly boosting a merchant's overall transaction approval rate and safeguarding revenue streams. The mechanism focuses on actionable decline reasons.
Optimise operational efficiency
Manual review of decline codes and subsequent action is time-consuming and prone to human error. Cardflo automates the entire decline recovery process, from interpretation to action, reducing the operational burden on internal teams. This automation ensures that recovery attempts are initiated promptly and consistently, freeing up staff to focus on other critical business functions while improving overall payment processing efficiency and reducing overheads associated with manual intervention in payment failures.
Decline recovery use cases
Wallet deposit limit declines
Digital wallet operators receiving velocity limit or daily deposit ceiling codes risk repeating attempts that issuers have already classified as ineligible. Cardflo maps these responses as hard declines, suppresses prohibited retries and returns a reason category that lets the operator direct the account holder towards another eligible funding instrument.
Luxury purchase decline recovery
Retailers often receive a generic do not honour response where the issuer has not exposed whether the rejection is temporary, fraud-related or permanent. Cardflo normalises acquirer partner responses into conditional decline classes, applies scheme-compliant retry eligibility and prevents ambiguous codes from triggering repeated authorisation attempts without a permitted recovery path.
Insufficient funds response rules
Merchants handling large payment volumes need to distinguish insufficient funds responses from lost card, invalid account and restricted card codes before another authorisation is attempted. Cardflo applies code-specific rules that classify insufficient funds as potentially recoverable while marking prohibited conditions as hard declines, with retry handling constrained by Visa and Mastercard requirements.
Digital service decline mapping
European card payments may return a soft decline when an issuer requires SCA rather than rejecting the underlying account or available funds. Cardflo identifies authentication-required response codes and directs the transaction into a 3DS2 challenge flow, while terminal account, stolen card or invalid credential responses remain blocked from inappropriate resubmission.
Decline recovery by the numbers
This represents the typical percentage of soft declines that can be successfully converted into approvals through automated retry and routing strategies across the payments industry.
Industry benchmarks suggest that implementing robust decline recovery logic can significantly reduce churn caused by failed payments in subscription based business models.
Optimising the recovery layer of the payment stack often results in a measurable increase in total authorisation rates, based on standard global processing data for enterprise merchants.
Methodology: these figures are illustrative ranges drawn from published industry data and observed merchant cohorts, not guarantees. Actual results depend on your risk profile, card mix, geography and acquiring setup, and are confirmed only in your own pricing and approval terms.
Related terms
Talk to our team about a live rollout across our acquirer partners' rails.
What you get with Decline recovery
- Identify specific issuer and acquirer decline codes immediately after an authorisation failure occurs.
- Categorise declines into temporary, permanent, or unrecoverable based on detailed analysis.
- Route recoverable temporary declines to alternative acquirers within the merchant's network.
- Trigger customer notifications for specific permanent decline reasons, requesting updated payment details.
- Utilise scheme account updater services for recurring payments associated with expired or reissued cards.
- Distinguish between recoverable and unrecoverable declines to avoid unnecessary transaction retries.
- Measure the uplift in successful transactions directly attributable to recovery efforts.
- Monitor decline trends across different payment methods and geographical regions.
- Configure specific recovery workflows based on transaction value thresholds or merchant segments.
- Integrate seamlessly with existing payment orchestration and risk management systems.
A short scoping call, then a written plan for your MIDs.
Questions about Decline recovery
What is the difference between a soft decline and a hard decline?
A soft decline occurs when the issuing bank approves the card but the specific transaction cannot be processed at that moment; examples include insufficient funds, technical failures, or exceeding a temporary limit. These are typically eligible for recovery via retries.
A hard decline occurs when the payment cannot be authorised under any circumstances, such as a stolen card, a closed account, or an invalid card number.
Hard declines should not be retried as they are permanent and continuing to do so can lead to penalties from card schemes.
How many times can a merchant retry a declined transaction?
Card schemes like Visa and Mastercard have strict rules regarding retry attempts. Generally, merchants are permitted to retry a soft decline up to 15 times within a 30 day period, though this varies by region and specific decline reason.
Retrying a hard decline is strictly prohibited. Excessive retries on a single account can result in additional scheme fees and may lead to the merchant being flagged for suspicious activity by the issuer's risk engine.
How does dynamic routing help with decline recovery?
Dynamic routing involves sending a transaction to a different payment acquirer if the first attempt fails. This is effective when a decline is caused by an acquirer's internal risk filters, a regional outage, or an issuer's preference for domestic processing.
By switching the acquirer mid-stream, the merchant can present the transaction in a way that is more likely to be accepted, effectively recovering a sale that would have failed on a single acquirer setup.
Can decline recovery help with SCA and PSD2 compliance?
Yes. If an issuer declines a transaction with a specific code indicating that Strong Customer Authentication (SCA) is required, the recovery system can react by initiating a 3D Secure flow.
This redirects the customer to authenticate their identity, satisfying the regulatory requirements of PSD2. Without this recovery logic, the transaction would simply fail, and the merchant would lose the revenue due to a technical refusal related to authentication mandates.
What role does an account updater play in recovery?
An account updater is a service provided by card networks that automatically provides new card numbers or expiry dates when a customer's card is replaced. This is a proactive recovery tool.
If a recurring payment fails because a card has expired, the recovery system can query the updater service for the new details and retry the transaction with the updated credentials, preventing the decline from recurring in subsequent billing cycles.
How does Merchant Category Code (MCC) affect recovery strategies?
Issuers apply different risk models based on the MCC of the merchant. High risk categories may experience higher decline rates for certain transaction types.
A sophisticated recovery strategy adjusts retry logic and routing based on the MCC to align with the specific risk appetite of issuing banks for that sector, ensuring that recovery attempts do not inadvertently trigger fraud alerts.
Are there specific fees associated with retrying transactions?
Yes, card schemes often charge 'misuse of authorisation' fees or 'excessive retry' fees if a merchant ignores decline codes and continues to process unapproved transactions. Effective decline recovery systems are designed to parse these codes and cease attempts on hard declines to minimise these costs.
The goal is to balance the potential revenue from a successful recovery against the incremental cost of the processing attempts.
Related features.
Related guides.
See how Cardflo compares.
Ready to improve your payments setup?
Tell us about your business. We'll match you with the right acquiring partners and the right route, typically inside a week.