When to Retry Failed Payments: Optimal Timing Strategies

Timing is everything in payment recovery. Retry a failed payment at the right moment, and it goes through silently. Retry at the wrong moment, and you've wasted an attempt that could have worked later.

This guide covers when to retry based on decline type, optimal days and times, and how to build a retry strategy that maximizes recovery.

The basics of retry timing

When a payment fails, you have limited attempts before you need to involve the customer. Most payment processors allow 3-4 retries before flagging aggressive behavior. Each attempt matters.

The goal is simple: retry when the conditions that caused the failure have changed.

• "Insufficient funds" → Retry when the customer likely has money (after payday)
• "Processing error" → Retry when bank systems are working (few hours later)
• "Card declined" → Retry when fraud systems have cooled down (next day)

Blindly retrying every 24 hours ignores these patterns and leaves money on the table.

Timing by decline type

Different failures need different timing.

Insufficient funds

The customer's account didn't have enough money at the moment you charged. This is contextual — the money might be there tomorrow or next week.

Best timing:

• Wait 3-5 days (allow payday deposits)
• Retry on the 1st-5th or 15th-20th of month
• Early morning (before daily spending starts)
• Tuesday-Thursday (most stable banking days)

Avoid:

• Retrying same day or next day
• End of month (accounts typically lowest)
• Weekends (less banking activity)

Processing error / Timeout

Something went wrong technically. The bank's systems hiccupped, there was a network issue, or the request timed out.

Best timing:

• Retry in 2-6 hours
• Avoid immediate retry (same issue might persist)
• Any day is fine — this isn't calendar-dependent

Avoid:

• Waiting too long (customer might forget they made a purchase)
• Middle of the night (more maintenance windows)

Generic "card declined"

The bank rejected it without a specific reason. Often a fraud system being cautious.

Best timing:

• Wait 24-48 hours
• Retry during business hours
• Mid-week is typically best

Avoid:

• Immediate retry (fraud system will reject again)
• Multiple rapid retries (looks suspicious)

Do not honor

The bank explicitly refused without explanation. Could be fraud suspicion, unusual activity, or internal bank policy.

Best timing:

• Wait 48-72 hours minimum
• Try a different time of day
• Consider this a weak candidate for retry

Avoid:

• Quick retries (you're on a watchlist)
• More than 2 retry attempts

Exceeds limit

Customer hit their daily or monthly spending cap.

Best timing:

• Wait until the next day (daily limit resets)
• Or wait until next month (monthly limit)
• Early morning before other spending

Optimal days for retries

Not all days are equal for payment success.

Best days:

1. Tuesday — Banks fully operational, weekend backlog cleared
2. Wednesday — Peak business day
3. Thursday — Strong but starting to tail off

Okay days:

• Monday — Weekend backlog can cause issues
• Friday morning — Fine before afternoon

Avoid:

• Friday afternoon — Banks winding down
• Saturday/Sunday — Reduced processing, more maintenance
• Holidays — Skeleton crews, higher failure rates

Payday timing matters too:

• 1st-5th of month — Monthly salary deposits
• 15th-20th — Bi-weekly payday window
• Last 5 days — Accounts often at lowest

Optimal times for retries

Time of day affects success rates more than most people realize.

Best times:

• 9 AM - 12 PM local time — Business hours, banks fully staffed
• 2 PM - 5 PM — Secondary peak

Okay times:

• 7 AM - 9 AM — Systems warming up
• 5 PM - 8 PM — Evening, still processing

Avoid:

• 12 AM - 6 AM — Maintenance windows, skeleton crews
• 11 PM - 12 AM — Day rollover issues

For recurring billing, if you can choose when the billing cycle starts, aim for mid-month Tuesday-Thursday for the initial charge. Fewer failures to recover in the first place.

Building a retry schedule

Here's a practical retry schedule for a soft decline:

Insufficient funds scenario

Day 0: Initial failure at 3 PM
Day 0: No retry yet — just happened
Day 3: First retry at 10 AM (Tuesday)
Day 6: Second retry at 10 AM (Friday AM)
Day 10: Third retry at 10 AM (Tuesday)
Day 10: After 3rd failure, rely on dunning emails only

Processing error scenario

Hour 0: Initial failure at 2 PM
Hour 4: First retry at 6 PM same day
Day 1: Second retry at 10 AM next morning
Day 3: Third retry at 10 AM

Generic decline scenario

Day 0: Initial failure at 4 PM
Day 2: First retry at 10 AM
Day 5: Second retry at 10 AM
Day 8: Third retry at 10 AM

Coordinating retries with dunning

Retries and dunning emails should work together, not independently.

Bad approach:

• Retry silently for 7 days
• Then start sending emails
• Customer has no idea anything was wrong

Good approach:

• Retry #1 scheduled + Email #1 sent (Day 0)
• Retry #2 (Day 2-3)
• Email #2 sent (Day 3)
• Retry #3 (Day 5-6)
• Email #3 "urgent" sent (Day 6)
• Account suspended (Day 7-10)

If a retry succeeds, cancel pending emails. If retries fail, emails become the primary recovery path.

The customer's time zone matters

If you're charging customers globally, timing in YOUR time zone is irrelevant.

A retry at 10 AM EST is:

• 7 AM PST (okay)
• 3 PM London (good)
• 11 PM Tokyo (bad)

Better systems adjust retry timing to the customer's local time zone. At minimum, avoid retrying in the middle of someone's night.

How many retries?

More isn't better. Each failed retry:

• Uses up your "budget" with the bank
• Can trigger fraud alerts
• Delays the real solution (customer updating their card)
• Hurts your metrics with the payment processor

Recommended:

• 3-4 retry attempts maximum
• Spread over 7-10 days
• Stop retrying hard declines entirely

Some processors monitor retry rates. Excessive retries can lead to account reviews or higher fees.

Measuring retry effectiveness

Track these metrics:

Retry success rate by attempt number

Attempt 1: 25% success
Attempt 2: 15% success
Attempt 3: 8% success
Attempt 4: 3% success

If attempt 4 is only 3%, is it worth the risk? Maybe stop at 3.

Success rate by day of week If Tuesday retries succeed at 28% and Sunday at 12%, adjust your schedule.

Success rate by decline code Some codes have near-zero retry success. Stop wasting attempts on them.

Time to recovery How many days from first failure to successful payment? Shorter is better — both for cash flow and customer experience.

Automation vs manual tuning

You have two options:

Use your processor's smart retries Stripe, Braintree, Recurly all have machine learning-powered retry systems. They analyze millions of transactions to pick optimal timing.

Pros: Zero effort, constantly improving Cons: No customization, black box

Build custom retry logic Implement the rules in this guide based on your specific data.

Pros: Full control, can optimize for your patterns Cons: Development effort, ongoing maintenance

For most SaaS, the processor's smart retries plus good dunning emails is the right answer. Custom retry logic makes sense only at scale (thousands of failures monthly) where optimization has meaningful dollar impact.

Quick start checklist

1. Enable smart retries in your payment processor
2. Set up basic dunning emails to run in parallel
3. Don't retry hard declines (expired cards, etc.)
4. Space retries at least 24 hours apart
5. Avoid weekends and late night retries
6. Limit to 3-4 total attempts
7. Track success rate by attempt and decline code
8. Adjust timing based on your actual data