Failed payment recovery
Cardflo's failed payment recovery system is engineered to minimise lost revenue from unsuccessful transactions. We deploy a multi-faceted approach, combining smart retries, dynamic routing, and data-driven insights to maximise payment authorisation and improve your bottom line.
- Category
- Recovery
- Capabilities
- 10
- Available on
- All plans
The overview
Failed payment recovery comprises the technical processes and logic sequences used to capture revenue that would otherwise be lost to transaction declines.
When a merchant submits an authorisation request, the issuer may return a refusal for diverse reasons, including insufficient funds, technical timeouts, or suspected fraud. Recovery mechanisms operate within the payment orchestration layer to address these soft declines through systematic intervention.
By utilising automated retries, account updater services, and intelligent routing, merchants can address correctable errors without manual customer involvement. This process is critical for subscription-based businesses and high-volume e-commerce where churn is often a direct result of passive payment failure.
The objective is to navigate the complex interplay between the acquirer, the card scheme, and the issuing bank to reach an authorised state, ensuring that the transaction lifecycle continues to settlement and reconciliation while maintaining compliance with scheme rules regarding retry limits.
How it works
Categorising decline response codes
The system first analyses the reason code returned by the issuer via the gateway. Distinguishing between a hard decline, such as a stolen card, and a soft decline, such as a temporary limit or technical error, is essential.
Only soft declines are funnelled into recovery workflows to prevent excessive scheme fees or penalties.
Automated intelligent retry logic
For soft declines, the platform executes a retry strategy based on historical data. This involves re-submitting the transaction at specific intervals or times of day when authorisation success is statistically higher for particular BIN ranges.
This automated process attempts to capture funds before the transaction reaches a final refusal state.
Account currency and data refreshment
If a failure stems from expired credentials or changed card numbers, the system queries card scheme databases via an account updater. This retrieves the most current PAN and expiry information, updating the tokenised record in the vault.
This ensures the subsequent authorisation attempt uses the most accurate data available.
Dynamic acquirer failover routing
In instances of gateway downtime or regional acquirer instability, the transaction is rerouted to an alternative Merchant Identification Number.
By switching to a different processing bank, the system bypasses localised technical outages or restrictive risk filters that may have caused the initial failure during the first attempt.
Why it matters
Reduces involuntary customer churn
Involuntary churn occurs when a customer intends to remain a subscriber but their payment fails due to backend technicalities. A robust recovery system identifies and resolves these issues before the service is interrupted.
By automating the capture of these funds, businesses maintain their active user base without requiring the customer to update their payment method, which often triggers a manual review of the necessity of the service.
Optimises net revenue collection
Transaction declines represent a direct leakage of revenue that has already incurred acquisition costs. Recovering a failed payment is significantly more cost-effective than acquiring a new customer.
By improving the authorisation rate by even a small percentage through systematic retries and BIN-specific routing, a merchant can substantially increase their bottom line while ensuring all successful captures are moved to settlement efficiently.
Use cases
SaaS and subscription billing
Subscription models often face periodic declines due to card expiry or fluctuating balances. Automated recovery ensures renewals are processed successfully without service disconnection, minimising the workload for accounts receivable teams.
High-volume retail events
During peak sales periods, issuer systems may experience lags leading to timeouts. Dynamic routing and immediate retries ensure these time-sensitive transactions are recovered while the inventory is still reserved for the purchaser.
International cross-border commerce
Transactions processed across borders frequently trigger fraud flags. Rerouting these to a local acquirer or retrying with specific 3DS parameters can help overcome geographic restrictions that caused the initial decline.
By the numbers
This range reflects typical industry performance for recovering soft declines through automated retries and account updates before a permanent loss occurs.
In many subscription sectors, a majority of initial declines are classified as soft, suggesting they are theoretically recoverable through systematic technical intervention.
Implementing a comprehensive recovery strategy generally results in a modest but significant lift in total authorisation rates across the entire transaction volume.
Related terms
Talk to our team about a live rollout on your acquiring stack.
What you get with Failed payment recovery
- Identification of ISO 8583 response codes to separate hard and soft transaction declines.
- Scheduling of retries aligned with issuer processing windows for higher probability of success.
- Integrated account updater services to refresh expired credentials before the next billing cycle.
- Failover routing to secondary acquirers when primary processing pathways return technical errors.
- Tokenisation of payment data to ensure secure re-attempts without storing raw card numbers.
- Customisable dunning logic to coordinate email communication alongside backend technical recovery efforts.
- Monitoring of scheme-mandated retry limits to avoid excessive fee penalties from card networks.
- Analysis of BIN-level performance to identify specific issuer behaviour patterns and refusal trends.
- Real-time reporting on recovery rates and the total value of rescued transactions.
- Support for Merchant Initiated Transactions to facilitate recovery for recurring billing agreements.
A short scoping call, then a written plan for your MIDs.
Questions about Failed payment recovery
What is the difference between a hard decline and a soft decline in recovery?
A hard decline is a permanent failure where the issuer indicates the transaction should not be retried, such as for a lost or stolen card or an invalid account. Attempting to recover these violates scheme rules and may lead to fines.
A soft decline is a temporary issue, such as a technical timeout, suspected fraud that can be cleared via 3DS, or insufficient funds.
Recovery systems focus exclusively on soft declines, using logic to re-present the transaction when the inhibiting condition is likely to have been resolved.
How do card scheme rules impact the frequency of payment retries?
Visa and Mastercard have strict regulations regarding the number of times a merchant can attempt to authorise a failed transaction. Generally, a merchant is limited to a specific number of retries within a 30-day window for the same transaction.
Exceeding these limits can result in excessive retry fees. A professional recovery system tracks these attempts per transaction ID to ensure compliance, prioritising the highest quality attempts to avoid unnecessary costs while trying to secure the authorisation.
Can failed payment recovery assist with 3-D Secure authentication failures?
Yes, to a certain extent. If a transaction fails due to a 3DS challenge not being completed, the recovery system can trigger a notification to the customer to re-authenticate.
In some cases, if the failure was a technical error in the 3DS server, a retry through a different gateway or at a later time may result in a successful frictionless flow.
However, for SCA-mandated regions, the customer usually needs to be involved in the first instance of a new session.
What role does an account updater play in the recovery process?
An account updater is a service provided by card schemes that allows a PSP to check if a saved card has been replaced or updated. When a payment fails due to an expired card or an outdated PAN, the recovery system queries the updater.
If new details are found, the merchant's vault is updated automatically. The system then retries the payment with the new data, often recovering the payment without the customer ever being aware there was a potential issue.
How does smart routing contribute to recovering failed transactions?
Smart routing directs a transaction to the acquirer most likely to approve it based on the card's BIN, geographic location, and currency.
If an initial attempt fails at Acquirer A due to a technical refusal, the recovery system can instantly route a second attempt to Acquirer B.
This is particularly effective for cross-border payments where a local acquirer may have a better relationship or lower fraud suspicion for a specific issuer than a foreign bank.
Is it possible to recover payments that failed due to insufficient funds?
Transactions declined for insufficient funds are the most common type of soft decline. Recovery logic typically involves retrying these transactions on dates when customers are most likely to have received funds, such as common paydays at the end of the month.
By intelligently timing these retries rather than attempting them immediately, the probability of finding an adequate balance increases, leading to a successful authorisation and settlement.
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.