Payment retry scheduling
Payment retry scheduling automates the resubmission of failed transactions. This feature allows merchants to configure specific retry logic based on decline codes, transaction history, and customer segments.
It is designed to recover revenue without requiring manual intervention, improving overall transaction success rates for recurring payments and subscriptions.
- Category
- Recovery
- Capabilities
- 10
- Available on
- All plans
The overview
Payment retry scheduling sits within the recovery layer of the payment stack, specifically addressing soft declines for Merchant Initiated Transactions (MIT).
Unlike hard declines caused by lost cards or closed accounts, soft declines often result from temporary issues such as insufficient funds, technical timeouts, or general bank errors.
By applying logic to these failures, a merchant can resubmit authorisation requests at intervals most likely to coincide with account funding or system stability.
This process typically involves a combination of fixed-interval schedules and dynamic logic that considers the specific decline reason code provided by the issuer. For businesses operating subscription models or recurring billing, this automation minimises the administrative burden of manual outreach while reducing passive churn.
The mechanic relies on mapping response codes to specific retry paths, ensuring that further attempts do not violate card scheme rules or trigger excessive fee penalties from the acquirer.
How it works
Initial Response Code Analysis
When an authorisation request fails, the system parses the specific response code from the issuer. It distinguishes between hard declines, which require no further action, and soft declines that are eligible for recovery.
This step ensures the merchant remains compliant with scheme rules regarding prohibited retry attempts on specific refusal categories.
Logic Application and Scheduling
The system applies a predefined or dynamic schedule based on the failure reason. For insufficient funds (NSF) declines, the retry might be paused until typical salary dates.
For technical errors, a short-term retry within minutes or hours is often prioritised to capture the transaction during a period of stability.
Request Re-submission via Gateway
The scheduled request is sent back to the acquirer at the designated time, often utilising stored credentials and specific indicators to denote a subsequent attempt.
This process maintains the link to the original transaction attempt where necessary, ensuring the payment flow complies with SCA and PSD2 requirements for MITs.
Outcome Monitoring and Settlement
If the retry is successful, the transaction proceeds to capture and settlement. The result is documented in the recovery logs to assess the efficiency of the timing logic.
If the retry fails, the system either moves to the next scheduled attempt or terminates the cycle as a final decline.
Why it matters
Reduction in Passive Churn
Passive churn occurs when a customer has no intention of cancelling a service, but their payment fails due to avoidable technical or financial factors. Automated scheduling addresses these failures in the background.
By recovering these transactions, merchants maintain continuity of service for the cardholder, preventing the friction of manual re-entry and reducing the likelihood of the customer abandoning the subscription due to a service interruption.
Optimised Operational Efficiency
Manual dunning and customer service outreach for failed payments are resource-intensive tasks. Implementing a systematic retry framework reduces the volume of tickets handled by support teams.
By automating the recovery process at the gateway or orchestration level, businesses can focus on growth while the infrastructure handles the complexities of bank response codes and scheme-compliant interval management for recurring billing cycles.
Use cases
Subscription-Based SaaS Platforms
SaaS providers use retry scheduling to handle monthly renewals. If an authorisation fails at midnight on the first of the month, the system ensures subsequent attempts occur when banking systems are most responsive.
Utility and Telecom Billing
For essential services where service disconnection is a risk, retrying payments across a 14-day window following a soft decline ensures revenue capture while avoiding the legal complexities of debt collection.
Digital Content and Media
Streaming services utilise aggressive but compliant retry logic in the first 48 hours following a failure to ensure uninterrupted access to content for high-volume, low-value monthly transactions.
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.
Related terms
Talk to our team about a live rollout on your acquiring stack.
What you get with Payment retry scheduling
- Differentiates between soft and hard declines to ensure compliance with card scheme retry rules.
- Categorises issuer response codes to prioritise transactions with the highest probability of eventual success.
- Adjusts retry timestamps based on historical data regarding issuer uptime and typical consumer funding cycles.
- Supports customisable intervals for recurring billing cycles to align with specific business accounting periods.
- Integrated logic to prevent excessive scheme fees caused by over-retrying declined transactions without changes.
- Automates the transition from failed authorisation to recovered status without manual customer support intervention.
- Utilises stored payment credentials securely via tokenisation for all subsequent Merchant Initiated Transactions.
- Provides granular reporting on recovery rates organised by decline type and specific retry attempt number.
- Maintains compliance with PSD2 and SCA requirements by correctly flagging recurring transaction recovery attempts.
- Reduces the need for immediate dunning emails, favouring silent recovery to maintain customer experience.
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.
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.