Retry Timing Best Practices
Industry benchmarks for optimal retry windows, payday patterns, time-of-day effects, and spacing strategies for soft and hard declines.
When you retry a failed payment matters as much as whether you retry at all. A well-timed retry can recover revenue silently, while a poorly-timed one wastes an attempt and may hurt your processor relationship. This guide covers the data behind optimal retry timing so you can evaluate LostChurn's defaults and configure overrides when needed.
Best Days to Retry
Failed payments caused by insufficient funds follow predictable patterns tied to when customers receive income. The strongest recovery days cluster around paydays.
Payday Patterns
| Day of Month | Why It Works | Relative Recovery Rate |
|---|---|---|
| 1st | Monthly salary deposits for salaried employees | High |
| 15th | Biweekly and semi-monthly pay cycles | High |
| Last day | End-of-month payroll for some employers | Medium-High |
| Fridays | Weekly pay cycle deposits | Medium |
| 2nd-3rd | Spillover from 1st-of-month deposits | Medium |
LostChurn automatically detects payday patterns for individual customers over time and adjusts retry timing accordingly. If a customer's payments consistently succeed on the 15th, future retries will be scheduled around that date.
Days to Avoid
- Sundays -- lowest card authorization rates across all processors
- Major holidays -- bank processing delays reduce approval rates by 10-15%
- December 24-26, January 1 -- authorization rates drop significantly due to processor maintenance windows and reduced fraud-review staffing
Best Hours to Retry
Time of day affects authorization rates because banks batch-process transactions and fraud detection systems have different sensitivity thresholds throughout the day.
| Time Window (Customer's Timezone) | Authorization Rate Impact | Notes |
|---|---|---|
| 9:00 AM - 11:00 AM | Highest | Banks fully staffed, fraud systems at baseline sensitivity |
| 12:00 PM - 2:00 PM | Above average | Post-lunch processing window |
| 6:00 AM - 8:00 AM | Average | Early morning batch processing underway |
| 3:00 PM - 6:00 PM | Below average | End-of-day processing backlogs |
| 7:00 PM - 11:00 PM | Low | Reduced bank staffing, higher fraud sensitivity |
| 12:00 AM - 5:00 AM | Lowest | Minimal processing, highest fraud flag rates |
LostChurn uses the customer's billing address or IP geolocation to determine their timezone and schedule retries during the optimal local window. Configure timezone detection priority in Retry Strategies.
Spacing Between Retries
Retry spacing should escalate over time. Rapid-fire retries on a fresh decline are unlikely to succeed and can trigger processor rate limiting. Spacing out retries gives the underlying issue time to resolve.
Recommended Spacing for Soft Declines
Soft declines (insufficient funds, processing errors, rate limits) are temporary by nature. The spacing strategy gives the issue time to resolve while capturing the recovery window before the customer's next billing cycle.
| Retry Attempt | Wait After Previous | Cumulative Time | Expected Recovery Rate |
|---|---|---|---|
| 1st retry | 1 hour | 1 hour | 15-20% |
| 2nd retry | 24 hours | 25 hours | 25-35% (cumulative) |
| 3rd retry | 72 hours | ~4 days | 35-45% (cumulative) |
| 4th retry | 7 days | ~11 days | 40-50% (cumulative) |
After the 4th retry, additional silent attempts yield diminishing returns. LostChurn defaults to escalating to active dunning via Campaigns at this point.
Recommended Spacing for Hard Declines
Hard declines (expired card, do not honor) require customer action. Silent retries are unlikely to succeed, but a single delayed retry can catch cases where the customer updated their card after seeing a processor notification.
| Retry Attempt | Wait After Previous | Cumulative Time | Notes |
|---|---|---|---|
| 1st retry | 24 hours | 24 hours | Catches card updates from bank notifications |
| 2nd retry | 72 hours | 4 days | Final check before dunning-only mode |
Do not retry hard declines more than twice. Processors track retry rates by merchant, and excessive retries on hard-declined cards can result in increased processing fees or account reviews.
Soft vs. Hard Decline Timing Summary
The fundamental difference: soft declines reward patience and well-timed retries, while hard declines reward fast customer communication.
| Factor | Soft Declines | Hard Declines |
|---|---|---|
| First action | Silent retry after 1 hour | Dunning email immediately + 1 retry after 24 hours |
| Total retry attempts | 4 | 2 |
| Total retry window | 11 days | 4 days |
| Primary recovery method | Silent retries | Customer updates payment method |
| Dunning trigger | After retry 4 fails | Immediately, in parallel with retries |
| Expected recovery rate | 40-50% (silent) | 20-30% (with dunning) |
Holiday and Weekend Considerations
Weekends
Authorization rates drop 5-8% on weekends compared to weekdays. LostChurn's default behavior:
- Saturday retries are delayed to Monday morning unless the customer has a history of weekend payment success
- Sunday retries are always delayed to Monday 9:00 AM in the customer's timezone
- Weekend dunning emails are still sent (email open rates on weekends are comparable to weekdays)
Holidays
LostChurn maintains a holiday calendar for major markets (US, UK, EU, Canada, Australia) and adjusts retry timing automatically.
- Bank holidays -- retries are delayed to the next business day, as bank processing may be reduced
- Shopping holidays (Black Friday, Cyber Monday) -- retries are paused during peak processing hours to avoid competing with high-volume merchant traffic
- Year-end holidays (Dec 24 - Jan 2) -- retry spacing is extended by 48 hours to account for processor delays
You can customize holiday handling per-market in your Retry Strategies configuration.
Benchmark Recovery Rates by Strategy
The following table compares recovery rates across different timing strategies, based on aggregate data from subscription businesses processing $1M+ in monthly recurring revenue.
| Strategy | 7-Day Recovery Rate | 14-Day Recovery Rate | 30-Day Recovery Rate |
|---|---|---|---|
| Fixed interval (every 24h) | 18% | 23% | 26% |
| Escalating interval (1h/24h/72h/7d) | 25% | 35% | 40% |
| Payday-aligned | 22% | 38% | 45% |
| ML-optimized (LostChurn default) | 30% | 42% | 52% |
| ML-optimized + dunning | 38% | 52% | 62% |
The ML-optimized strategy combines escalating intervals with payday detection, time-of-day optimization, and per-customer learning. Adding dunning campaigns for hard declines and exhausted soft retries yields the highest overall recovery rate.
These benchmarks represent medians. Your actual recovery rates depend on your customer demographics, average transaction size, payment method mix, and industry vertical. B2C subscriptions under $50/month tend to see higher recovery rates than B2B subscriptions over $500/month.
Configuring Retry Timing in LostChurn
LostChurn's retry timing is configured through Retry Strategies. The defaults match the ML-optimized strategy described above. You can override:
- Maximum retry attempts per decline category
- Minimum spacing between retries
- Retry windows (allowed hours and days)
- Holiday calendars per market
- Dunning escalation triggers (after N retries or N days)
For most businesses, the defaults perform well out of the box. Consider overrides only if you have specific processor requirements or customer demographics that differ significantly from the general subscription population.
Next Steps
- Dunning Copy Best Practices -- what to say when silent retries are exhausted
- Retry Strategies -- configure timing in LostChurn
- Campaigns -- build multi-channel dunning flows that complement retry timing
- Recovery Overview -- return to the three pillars of recovery optimization
Recovery Optimization Overview
Learn the three pillars of payment recovery — timing, messaging, and channels — and avoid the most common mistakes that cost subscription businesses revenue.
Dunning Copy Best Practices
Write dunning emails and SMS messages that recover revenue — subject line formulas, tone guidance, escalation templates, and A/B testing recommendations.