Decline recovery
Cardflo's decline recovery solutions systematically address and resolve payment failures, converting declined transactions into successful ones. We employ advanced strategies to re-attempt payments effectively, recapture lost revenue, and improve overall authorisation rates for merchants.
- Category
- Recovery
- Capabilities
- 10
- Available on
- All plans
The overview
Decline recovery encompasses the technical processes and logic required to address unsuccessful transaction attempts within the payment authorisation flow. When a merchant submits an authorisation request via a gateway, various actors, including the risk engine, the acquirer, and the issuer, may return a decline.
These failures generally fall into two categories: soft declines, resulting from temporary issues like insufficient funds or technical timeouts, and hard declines, which indicate permanent issues such as an invalid account.
Recovery strategies sit at the orchestration layer, analysing the specific decline codes sent via the ISO 8583 standard. By interpreting these codes, the system can determine if a re-attempt is permissible under card scheme rules.
Effective recovery involves a combination of intelligent retry schedules, dynamic routing to secondary acquirers, and the use of account updater services. This systematic approach aims to stabilise merchant revenue by capturing transactions that would otherwise be abandoned due to transient technical or financial friction.
How it works
Response code analysis
The system receives a decline response and immediately parses the specific reason code provided by the issuer or acquirer. It distinguishes between transient errors, such as a temporary processor timeout, and permanent errors, like a closed account.
This initial triage determines whether the transaction is eligible for an automated recovery attempt or requires customer intervention.
Intelligent retry scheduling
For soft declines, the recovery logic calculates an optimal window for a secondary authorisation attempt. For subscription models, this often involves matching the retry to common payroll cycles.
The timing is calibrated to comply with card scheme regulations, such as those from Visa or Mastercard, which limit the number of attempts within specific timeframes.
Dynamic acquirer routing
If a transaction fails due to a suspected regional mismatch or an acquirer specific risk block, the recovery engine reroutes the request to a different merchant identification number (MID) or a secondary acquirer.
This pathing can bypass local outages or issuer preferences for certain domestic processing entities, increasing the likelihood of approval.
Credential update check
Behind the scenes, the recovery process may query network token services or account updaters to verify if the payment credentials have changed.
If a card was replaced due to expiry or loss, the system retrieves the updated details before the next retry, preventing repeat declines caused by stale payment data.
SCA fallback execution
When a decline occurs because an issuer requires Strong Customer Authentication, the recovery logic can trigger a step-up process.
This prompts the user to complete a 3D Secure challenge, converting a technical soft decline into a successful authorised transaction by satisfying PSD2 compliance requirements in the United Kingdom and EEA.
Why it matters
Stabilising subscription revenue
In recurring billing models, even a small percentage increase in involuntary churn can severely impact the lifetime value of a customer cohort. Automated decline recovery ensures that temporary issues, such as a card reaching its credit limit mid-month, do not result in immediate service cancellation.
By systematically managing retries, merchants maintain continuity of service and protect their monthly recurring revenue without needing manual support intervention.
Reducing operational costs
Manual outreach to customers for updated payment information is resource intensive and often results in higher friction. Automating the response to decline codes allows the billing department to focus on high value tasks.
Furthermore, sophisticated recovery logic ensures compliance with scheme rules regarding retries, avoiding potential fines or excessive fees associated with non compliant transaction behaviour that issuers may flag as suspicious.
Enhancing the customer experience
Payment failures at the point of sale or during a renewal can lead to immediate cart abandonment or negative brand perception. Recovery mechanisms that operate silently in the background, such as account updates or intelligent routing, prevent the customer from experiencing a service interruption.
This creates a frictionless environment where the technical complexities of the payment stack remain invisible to the end user.
Use cases
SaaS and subscription boxes
Digital service providers use recovery logic to manage high volumes of monthly renewals, specifically targeting soft declines through scheduled retries and account updater services before subscriptions are terminated for non payment.
High volume e-commerce
Online retailers implement dynamic routing across multiple acquirers during peak periods to recover transactions that fail due to acquirer specific downtime or restrictive risk thresholds on certain BIN ranges.
International marketplaces
Merchants selling across borders use decline recovery to retry transactions via domestic acquirers, bypassing the higher decline rates often associated with cross border authorisation requests and complex currency conversions.
Digital content streaming
Media platforms employ SCA fallback and 3D Secure optimisation to recover transactions flagged by issuers as requiring extra authentication, ensuring compliant processing under PSD2 without losing the sale.
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.
Related terms
Talk to our team about a live rollout on your acquiring stack.
What you get with Decline recovery
- Automatic identification of soft decline versus hard decline reason codes from issuers.
- Compliance with Visa and Mastercard retry limits to avoid excessive fee penalties.
- Detection of technical timeouts for immediate retry through alternative gateway paths.
- Integration with card account updaters to refresh expired or replaced credit cards.
- Dynamic routing to secondary merchant identification numbers for improved authorisation probability.
- Support for 3D Secure step-up logic when issuers request Strong Customer Authentication.
- Customisable retry logic based on specific Merchant Category Codes and transaction risk scores.
- Analysis of decline trends by card brand, issuing bank, and geographic region.
- Usage of network tokens to maintain lifecycle management of stored payment credentials.
- Detailed reporting on recovery success rates to evaluate the effectiveness of routing rules.
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.
Ready for velocity?
Tell us about your business. We'll match you with the right acquiring partners and the right route, typically inside a week.