The Best Retry Schedule for Failed Payments in 2026

Why Retry Timing Matters

When a payment fails, your instinct might be to retry immediately and keep retrying until it works. But retry timing significantly impacts recovery rates. Retry too soon and you'll hit the same issue. Retry too late and the customer has moved on.

The optimal retry schedule depends on three factors:

1. The decline code — why the payment failed
2. The day of the week/month — when customers are most likely to have funds
3. The number of previous attempts — diminishing returns after 4-6 retries

The Optimal Retry Schedule

Based on industry data and payment processor recommendations, here's the schedule that maximizes recovery:

| Retry | Timing | Rationale | |-------|--------|-----------| | 1st | 4-6 hours after failure | Catches processing errors and temporary holds | | 2nd | 3 days later | Gives time for insufficient funds to clear | | 3rd | 5 days later (Day 8 total) | Mid-week, post-payroll window | | 4th | 6 days later (Day 14 total) | Next payroll cycle | | 5th | 7 days later (Day 21 total) | Final attempt, different time of month |

Why This Works

First retry (4-6 hours): About 15-20% of failures are temporary — processing errors, bank system outages, or velocity limits. A quick retry catches these without any customer friction.

Second retry (Day 3): The most common decline reason is insufficient funds. A 3-day window allows for payday deposits, pending transfers to clear, and credit limit resets.

Third retry (Day 8): By targeting mid-week (Tuesday-Thursday), you hit the window when bank balances are highest. Most people get paid bi-weekly, and Tuesday-Wednesday are statistically the best days for successful charges.

Fourth retry (Day 14): This catches the next payroll cycle for bi-weekly earners. Also coincides with the 15th of the month — a common payday for monthly salaried employees.

Fifth retry (Day 21): Final attempt, three weeks out. This captures end-of-month payrolls and gives maximum time for the customer to resolve any banking issues.

Adjusting by Decline Code

Not all failures should follow the same schedule. Here's how to optimize based on the specific decline code:

Soft Declines — Retry Aggressively

Soft declines are temporary and highly recoverable:

| Decline Code | Recommended Retry | Timing | |---|---|---| | insufficient_funds | Retry 3-4 times | Space 3-5 days apart (catch payroll cycles) | | processing_error | Retry immediately | 1-4 hours, then follow standard schedule | | card_declined (generic) | Retry 3-4 times | Standard schedule | | try_again_later | Retry within hours | 2-6 hours, then standard schedule |

Hard Declines — Don't Retry, Communicate

Hard declines will never succeed on retry. Stop retrying and email the customer instead:

| Decline Code | Retry? | Action | |---|---|---| | expired_card | No | Email immediately — customer must update card | | stolen_card | No | Email immediately — card is blocked | | invalid_number | No | Email — card number on file is wrong | | card_not_supported | No | Email — need a different card type |

Retrying hard declines wastes attempts and can trigger fraud flags with the issuing bank.

Ambiguous Declines

Some decline codes could go either way:

| Decline Code | Strategy | |---|---| | do_not_honor | Retry once after 3 days, then email customer | | restricted_card | Retry once, then email | | withdrawal_count_limit_exceeded | Wait 3-5 days, then retry |

Day-of-Week Optimization

Payment success rates vary by day:

| Day | Success Rate (Relative) | Why | |-----|------------------------|-----| | Monday | Medium | Start of week, accounts settling | | Tuesday | Highest | Post-weekend deposits cleared | | Wednesday | High | Mid-week balance peak | | Thursday | Medium-High | Pre-weekend spending starts | | Friday | Medium | Weekend spending begins | | Saturday | Low | Banks process fewer transactions | | Sunday | Lowest | Minimal processing |

Best practice: Schedule retries for Tuesday-Thursday when possible, avoiding weekends.

Time-of-Day Optimization

| Time Window | Success Rate | Notes | |------------|-------------|-------| | 6am-9am | Medium | Pre-market, accounts stable | | 9am-12pm | Highest | Business hours, banks fully active | | 12pm-3pm | High | Afternoon processing window | | 3pm-6pm | Medium | End of business day | | 6pm-12am | Lower | After-hours, fewer approvals | | 12am-6am | Lowest | Minimal bank processing |

Retry during business hours (9am-3pm) in the customer's local time zone for best results.

Stripe's Default vs. Optimized Schedule

| Aspect | Stripe Default | Optimized Schedule | |--------|---------------|-------------------| | Number of retries | Up to 4 | 5 (with decline code routing) | | Window | ~23 days | 21 days | | Decline code routing | No | Yes | | Day-of-week optimization | Partial (ML) | Yes | | Time-of-day optimization | Yes (ML) | Yes | | Hard decline handling | Retries anyway | Stops + emails customer | | Recovery rate | ~50-55% | 70-85% (with communication) |

Stripe's ML-based Smart Retries are good at picking optimal times, but they don't differentiate strategy based on decline codes, and they don't communicate with customers about the failure.

Implementation Tips

1. Pair Retries with Communication

A retry schedule alone isn't enough. Each retry should be paired with a customer communication touchpoint:

| Retry | Customer Email | |-------|---------------| | 1st retry (hours) | First failure notification | | 2nd retry (Day 3) | Reminder email | | 3rd retry (Day 8) | Value reminder | | 4th retry (Day 14) | Save offer | | 5th retry (Day 21) | Final notice |

See our dunning email templates for the full sequence.

2. Stop Retrying on Hard Declines

Configure your system to check the decline code before scheduling a retry. Hard declines should trigger an immediate customer notification, not another retry attempt.

3. Track Recovery by Retry Number

Monitor which retry attempt actually succeeds:

• If most recoveries happen on retry 1-2, your initial timing is right
• If recoveries spike on retry 4-5, your customers need more time (consider spacing retries further apart)
• If few recoveries happen after retry 3, you might be retrying too many times

4. Consider the Billing Cycle

If most of your customers are billed on the 1st of the month and a payment fails on January 1st, your retry schedule should account for typical payroll dates (1st, 15th, bi-weekly Fridays).

5. Don't Retry More Than 5-6 Times

More retries don't mean more recovery. After 5-6 attempts:

• You've covered multiple payroll cycles
• The customer has received multiple emails
• Further retries show diminishing returns
• Excessive retries can flag your account with payment processors

Key Takeaways

1. The first retry should happen within hours — it catches 15-20% of failures immediately
2. Space subsequent retries 3-7 days apart — align with payroll cycles
3. Don't retry hard declines — email the customer instead
4. Tuesday-Thursday, 9am-3pm are the best times for successful retries
5. Pair every retry with a customer email — retries alone aren't enough
6. 5 retries over 21 days is the sweet spot — more than that shows diminishing returns