Payment retry scheduling
Payment retry scheduling provides operations leads with precise control over delayed transaction timing to maximise successful authorisations. Cardflo applies smart payment retry scheduling, deploying machine learning models that execute subsequent attempts based on velocity limits and historical payday signals.
- Category
- Recovery
- Capabilities
- 10
- Available on
- All plans
Payment retry scheduling systematically re-attempts transactions after an initial decline. Merchants configure precise rules within the Cardflo orchestration layer to dictate the timing and frequency of these re-attempts. This mechanism helps to recover revenue from transient declines without increasing operational overheads.
Effective scheduling considers multiple variables, including the decline reason, issuer behaviour, and card scheme regulations. Implementing a well-defined retry schedule improves the probability of successful authorisation and reduces lost sales. Cardflo's tools allow for granular control over this critical process.
Cardflo automates the resubmission of failed recurring payments using user-defined intervals optimised for individual transaction outcomes and SCA requirements. This scheduling boosts recovery rates across international markets, maximising subscription revenue.
Payment retry scheduling overview
A payment retry schedule specifies the exact intervals and conditions under which a previously declined transaction will be re-submitted for authorisation. This process is distinct from the initial authorisation attempt and is governed by a separate set of rules defined by the merchant within the Cardflo platform.
The primary objective is to capture revenue that might otherwise be lost due to temporary issues such as insufficient funds or system outages at the issuing bank.
Cardflo's scheduling engine allows for the configuration of sophisticated retry logic, moving beyond simple fixed-interval re-attempts. Merchants can specify variable backoff curves, adjust retry timings to align with known payday cycles, or adhere to specific dunning calendars for subscription services.
The system supports dynamic adjustments based on real-time decline codes and historical success rates, ensuring that each retry attempt is as intelligent as possible.
Implementing a robust payment retry schedule requires careful consideration of card scheme rules and issuer-specific behaviours. Some schemes impose limits on the number or frequency of re-attempts, while certain issuers might be more receptive to retries at particular times of day or month.
Cardflo provides the tools to manage these complexities, helping merchants to optimise their retry strategies across different markets and customer segments.
How payment retry scheduling works
Define retry parameters
Merchants configure initial retry parameters within the Cardflo dashboard. This includes setting the maximum number of attempts, the interval for the first retry, and defining the incrementing delays for subsequent attempts. Specific decline codes can be mapped to different retry schedules, allowing for granular control over the process.
Automated schedule execution
Upon receiving a recoverable decline, the Cardflo orchestration layer automatically places the transaction into the defined retry schedule. The system monitors the specified intervals, adjusting for factors like local time zones and national holidays. It then re-submits the transaction to the appropriate acquirer at the scheduled time without manual intervention.
Dynamic timing adjustments
The system dynamically adjusts retry timing based on predefined rules. This can involve aligning attempts with the expected salary payment dates for subscription services or delaying retries until after known banking system maintenance windows. Rules can be configured to consider the hour of day or day of month for optimal success rates.
Scheme and issuer compliance
Cardflo ensures all retry attempts adhere to the regulations set by card schemes such as Visa and Mastercard, as well as specific issuer guidelines. The platform prevents excessive or non-compliant re-attempts that could lead to penalties or blacklisting. Retry logic is continuously updated to reflect changes in scheme mandates.
Why payment retry scheduling matters
Optimise revenue capture from declines
Effectively scheduled retries can convert a significant portion of initially declined transactions into successful authorisations. By systematically re-attempting payments at more opportune times, merchants reduce lost revenue from transient issues like temporary insufficient funds or system outages. This direct impact on the bottom line is achieved through intelligent timing rather than repeated, unthinking submissions, which can incur scheme penalties.
Enhance customer experience for recurring payments
For subscription businesses, intelligent retry scheduling significantly reduces involuntary churn caused by payment failures. By aligning retry attempts with customer paydays or billing cycles, the system increases the likelihood of a successful renewal without requiring direct customer interaction. This proactive approach prevents service interruptions and maintains a positive customer relationship, reducing the need for manual dunning processes and improving retention rates.
Payment retry scheduling use cases
Salary date retry windows
Payroll-linked lenders collecting scheduled repayments can see insufficient-funds declines before salary deposits reach cardholders’ accounts, while repeated attempts risk scheme velocity controls. Cardflo uses machine learning scheduling to analyse prior success patterns and place re-attempts on likely pay days, with configurable intervals and daily attempt limits.
Utility meter payment retries
Prepayment energy operators may receive failed card top-ups around overnight bank ledger updates, delaying meter credit when re-attempts are poorly timed. Cardflo schedules retries for local daytime windows associated with stronger authorisation rates, while operators configure minimum delays and attempt ceilings to respect scheme velocity limits.
Corporate card renewal timing
Software publishers collecting annual enterprise licence renewals may encounter temporary corporate card limits near month-end, and concentrated re-attempts can create avoidable scheme fees. Cardflo models account-level payment history to stagger retries across finance teams’ likely budget-reset dates and permits customised delay intervals within the renewal collection window.
Instalment collection date optimisation
Consumer finance providers collecting fixed card instalments may see insufficient-funds declines when due dates fall several days before a borrower’s usual income credit. Cardflo analyses historical authorisation timing to schedule later attempts around likely balance replenishment, while configurable spacing prevents excessive re-attempts within scheme and merchant velocity limits.
Payment retry scheduling by the numbers
This range reflects typical industry outcomes for recovering soft declines in the subscription sector through automated logic rather than manual outreach.
Expected decrease in total churn for recurring revenue businesses when implementing systematic recovery for secondary and tertiary payment attempts.
The majority of successful recoveries typically occur within this timeframe following the initial decline, according to standard payment processing benchmarks.
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 Payment retry scheduling
- Define custom backoff curves, specifying increasing intervals between successive retry attempts after a decline.
- Set precise limits on the maximum number of retry attempts for individual transactions.
- Configure specific hours of the day and days of the month when retry attempts are permitted.
- Align retry schedules with common payday cycles to coincide with anticipated fund availability.
- Establish dunning calendars for recurring payments, factoring in billing dates and grace periods.
- Adhere to specific card scheme rules regarding the frequency and number of transaction re-attempts.
- Account for issuer-specific limitations or preferences for retry timing based on historical data.
- Vary retry intervals based on the initial decline reason code and its perceived recoverability.
- Implement distinct retry schedules for different markets, reflecting local payment behaviours.
- Adjust retry logic dynamically based on the performance of previous retry batches and authorisation rates.
A short scoping call, then a written plan for your MIDs.
Questions about Payment retry scheduling
What is the difference between a soft decline and a hard decline in retry logic?
A soft decline, such as an insufficient funds (NSF) message or a temporary technical error, indicates that the payment might succeed on a later attempt.
A hard decline, such as a stolen card or an invalid account number, indicates a permanent failure where further attempts are prohibited by card schemes like Visa and Mastercard. Retry scheduling is only applicable to soft declines.
Attempting to retry a hard decline can lead to significant fines from the acquirer and potential flagging of the Merchant ID (MID) for non-compliant behaviour.
How does retry scheduling impact merchant fees and scheme penalties?
Excessive retries without a change in transaction circumstances can lead to scheme penalties. For instance, Mastercard and Visa have specific rules regarding the number of times a merchant can retry a single transaction within a certain timeframe.
Effective scheduling avoids these penalties by spacing out attempts and halting the process once the maximum limit is reached. Properly configured logic ensures that the cost of recovery does not outweigh the value of the transaction being processed.
Can retry scheduling be configured for 3D Secure transactions?
Retry scheduling is primarily used for Merchant Initiated Transactions (MITs) where the cardholder is off-session. Transactions that require 3D Secure (3DS) authentication are typically Customer Initiated Transactions (CITs).
For these to be retried automatically, the merchant must have an initial agreement (Mandate) and the first transaction must be fully authenticated.
Subsequent retries are then flagged as MITs, using the exemption for recurring payments under SCA, though they must still refer back to the original authenticated session.
Does retrying a payment affect my authorisation rate metrics?
Initial attempts that fail will negatively impact your raw authorisation rate. However, successful retries improve your net recovery rate and overall revenue.
Most sophisticated payment analytics separate the 'first-time pass rate' from the 'final success rate' after retries. By analysing these separately, merchants can understand whether their initial authorisation issues are due to poor traffic quality or temporary technical hurdles that the scheduling logic is successfully mitigating.
How many times should a failed payment be retried before giving up?
Industry standards generally suggest a maximum of four to six attempts over a period of 15 to 30 days, depending on the MCC and the nature of the product.
The first few retries usually occur within the first 72 hours of the failure, as this is when recovery probability is highest.
Beyond 30 days, the likelihood of success for a soft decline drops significantly, and the risk of a dispute or chargeback if the cardholder has forgotten the subscription increases.
What role does the decline code play in timing the retry?
The decline code is the primary data point for scheduling. For example, a '51: Insufficient Funds' code suggests a retry should be timed near common paydays, such as the 1st or the 15th of the month, or every Friday.
A '05: Do Not Honour' or '96: System Malfunction' might suggest a technical glitch at the issuer, warranting a much faster retry, perhaps within hours, to catch the system after a reboot or sync.
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.