Revenue recovery
Cardflo's revenue recovery solutions address failed transactions directly. We employ strategic retries, intelligent routing, and real-time analytics to convert declined payments into approved ones.
This approach minimises lost sales and maximises your transaction success rates, ensuring that potential revenue is captured efficiently.
- Category
- Recovery
- Capabilities
- 10
- Available on
- All plans
The overview
Revenue recovery describes the systematic processes employed to capture funds from transactions that initially failed during the authorisation stage. In the payments stack, this sits between the initial gateway refusal and the final abandonment of a transaction.
The mechanics involve a combination of technical interventions, such as account updaters and retry logic, designed to address specific decline reason codes.
When an issuer sends a refusal, the merchant or PSP must distinguish between soft declines, which are temporary issues like insufficient funds or technical timeouts, and hard declines, which indicate permanent issues like account closure.
By applying automated logic to these responses, businesses attempt to repair the transaction without requiring additional customer input. This process is critical for maintaining high success rates in subscription models and high-volume e-commerce, where friction during manual re-entry often leads to permanent customer churn.
How it works
Analysis of decline codes
The system receives an authorisation refusal from the issuer via the acquirer. It instantly parses the specific response code to determine if the failure is a soft or hard decline.
This categorisation dictates whether a recovery attempt is viable and which specific tactic, such as a retry or account update, is appropriate.
Automated account information refresh
Before or after a failure, the system queries card schemes for updated credentials through an account updater service.
If a card has expired or been replaced due to loss, the service replaces the stale data with the new PAN and expiry date, preventing declines before they occur in the auth flow.
Intelligent retry scheduling
For soft declines like insufficient funds, the system schedules subsequent authorisation attempts. These are timed based on historical data indicating when accounts are most likely to be funded, such as typical salary cycles.
This avoids triggering fraud flags at the issuer level while maximising the probability of a successful capture.
Dynamic acquirer routing
If a transaction fails due to a technical refusal or gateway timeout, the system may reroute the request to an alternative merchant identification number or a different acquirer.
This redundancy ensures that regional outages or specific acquirer risk filters do not result in a lost sale for the merchant.
Why it matters
Reduction in involuntary churn
Involuntary churn occurs when a customer intends to pay, but technical failures or expired card details prevent the transaction. By automating the refresh of credentials and retrying failed payments, businesses can maintain service continuity for the user.
This protects the lifetime value of the customer and reduces the operational costs associated with manual outreach or dunning processes.
Optimisation of authorisation rates
High refusal rates can negatively impact a merchant's standing with card schemes and issuers, potentially leading to increased scrutiny or higher interchange costs. Effective recovery strategies improve the overall ratio of successful transactions.
By resolving soft declines through intelligent logic, a merchant demonstrates better transaction health, which may lead to more favourable treatment by fraud scoring engines.
Use cases
Subscription services
Recurring billing models rely on continuous authorisation. Recovery tools manage the high volume of monthly renewals, handling expired cards and temporary balance issues to ensure subscription revenue remains stable without manual customer intervention.
International e-commerce
Cross-border transactions often face higher refusal rates due to issuer risk profiles. Routing failures through local acquirers or retrying with specific flags can significantly improve the success rate for global merchants.
High-volume retail
Large merchants processing thousands of transactions daily use recovery logic to capture revenue that would otherwise be lost to transient gateway timeouts or network latency issues during peak shopping periods.
By the numbers
This represents the industry-typical range of previously declined transactions that are successfully captured through automated retry and account updater logic.
Merchants using automated credential refreshes often see this level of reduction in churn caused specifically by payment failures rather than customer intent.
A standard percentage increase in total successful transactions observed when deploying intelligent routing and retry mechanisms across a diverse payment portfolio.
Related terms
Talk to our team about a live rollout on your acquiring stack.
What you get with Revenue recovery
- Categorisation of decline codes into actionable soft and hard refusal buckets for precise response.
- Integration with card scheme account updaters to maintain current payment credential accuracy automatically.
- Configurable retry logic based on specific decline reason codes to avoid redundant processing fees.
- Smart routing to secondary acquirers when primary gateway connections return technical or connectivity errors.
- Support for Merchant Initiated Transactions to facilitate background recovery of recurring subscription payments.
- Real-time visibility into recovery performance via granular reporting on successful authorisation after initial failure.
- Customisable dunning cycles that align retry attempts with regional banking hours and funding patterns.
- Utilisation of network tokens to improve authorisation rates and reduce reliance on static card data.
- Compliance with PSD2 and SCA requirements when performing recovery on European economic area transactions.
- Historical analysis of BIN performance to inform the selection of the best recovery pathway.
A short scoping call, then a written plan for your MIDs.
Questions about Revenue recovery
What is the difference between a soft decline and a hard decline in revenue recovery?
A soft decline occurs when the issuer refuses the transaction for a temporary reason, such as insufficient funds or a technical timeout. These can be retried immediately or after a delay.
A hard decline is a permanent refusal, such as a stolen card or a closed account, where retrying the same credentials will not result in a success.
Revenue recovery systems prioritise soft declines, as attempting to retry hard declines can lead to excessive scheme fees and potential monitoring by card brands for poor processing behaviour.
How does an account updater service assist in recovering lost revenue?
Account updaters are services provided by card schemes like Visa and Mastercard that allow merchants to refresh stored card details. When a card is reissued due to expiry or theft, the updater provides the new card number or expiry date.
By updating the vault before a scheduled payment, the merchant avoids a decline. If a decline has already occurred, the updater can be used to repair the record before a retry attempt, significantly increasing the likelihood of a successful authorisation.
Are there limits to how many times a failed transaction can be retried?
Yes, card schemes have specific rules regarding the frequency and volume of retries. Excessive retries for the same transaction, especially after a hard decline, can result in fines and negative impact on the merchant's reputation with issuers.
Most industry-standard strategies limit retries to a handful of attempts over a 15 to 30-day period, focusing on the most likely windows of success to remain compliant with scheme behaviour requirements.
How does SCA impact revenue recovery for European transactions?
Strong Customer Authentication (SCA) under PSD2 requires many transactions to be authenticated via 3DS. For revenue recovery, this means that Merchant Initiated Transactions (MITs) must be correctly flagged and linked to an initial customer-authenticated session.
If a transaction falls out of scope or qualifies for an exemption, recovery can proceed. However, if an issuer requests a challenge, the transaction cannot be recovered in the background without the customer being present to authenticate.
Can intelligent routing prevent technical declines?
Intelligent routing helps recover revenue lost to infrastructure issues. If a specific acquirer or gateway is experiencing downtime, or if their connection to a certain issuer is unstable, the system can route the transaction to a different path.
This redundancy ensures that the payment attempt reaches a functional authorisation centre, turning a potential technical failure into a successful capture.
Does revenue recovery affect the merchant's chargeback ratio?
Revenue recovery primarily focuses on successful authorisations and does not directly increase chargebacks if the underlying transaction is legitimate. However, aggressive dunning or retrying after a customer has revoked consent could lead to disputes.
Professional recovery systems ensure that only authorised, legitimate transactions are retried, maintaining a balance between revenue capture and risk management to protect the merchant's MID.
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.