How many times should you retry a failed payment?

It depends on the decline type. Soft declines (insufficient funds, velocity limits) may warrant 3-5 attempts over 2-4 weeks, spaced around payday cycles. Hard declines (expired card, closed account) should not be retried — route them to customer outreach instead. Excessive retries on hard declines waste attempts and can flag the merchant as high-risk.

When is the best time to retry a declined payment?

For insufficient funds, retry after payday (1st and 15th of the month, or known payroll dates). For velocity limits, wait 24 hours for the window to reset. For issuer-unavailable errors, retry within hours. Avoid late-night and weekend retries when issuer fraud teams are more cautious.

Do smart retries work on all decline types?

No. Smart retries work on soft declines where the condition may resolve — insufficient funds, velocity limits, temporary issuer errors. They do not work on hard declines where the card itself is invalid (expired, closed, lost/stolen). Hard declines require customer outreach to collect a new payment method.

Can too many retries hurt my merchant account?

Yes. Processors track retry patterns, and excessive failed attempts — especially on the same card in a short window — can increase your decline rate metrics and flag you as high-risk. Smart retry systems limit attempts and space them appropriately to protect merchant standing.

How does Revatto time its retries?

Revatto analyzes the decline code, the processor, and historical success patterns for similar declines. It schedules retries around payday cycles, velocity-window resets, and optimal times of day. When retries are unlikely to succeed (hard declines), it routes to customer outreach instead.

What are smart retries? (intelligent retry logic explained)

By Jay Stevens · Founding EngineerReviewed by Jordan MederichUpdated July 13, 20264 min read

Summarize with AI

Quick answer

Smart retries are automated payment re-attempts that use timing, decline-code analysis, and historical patterns to maximize the chance of approval. Rather than immediately retrying a failed charge (which often triggers the same decline), smart retry systems wait for optimal windows: after a velocity-limit resets, on a different day of the week when issuers are less strict, or after payday when insufficient-funds declines are more likely to clear. The approach differs by decline type — soft declines (temporary conditions) benefit from timed retries, while hard declines (permanent card problems) require customer outreach instead. According to industry data, properly timed retries can recover 15-30% of soft declines without any customer contact.

Key takeaways

Smart retries time re-attempts for optimal approval odds instead of immediate retry.
The strategy varies by decline type — soft declines retry automatically; hard declines need customer outreach.
Timing factors include velocity-window resets, day of week, time of month (payday cycles), and issuer patterns.
Properly timed retries can recover 15-30% of soft declines without customer contact.
Blind immediate retries often trigger the same decline and can worsen the merchant's standing with the processor.

About this term

Recovery

Also known as: intelligent retries, retry logic, automatic retries, retry scheduling.

What smart retries mean

Smart retries are automated re-attempts of declined payments that use intelligence — timing, decline-code classification, and historical success patterns — to maximize approval odds. The key insight is that timing matters: a charge that fails at 2am on the 28th may succeed at 10am on the 1st, because the underlying condition (insufficient funds, velocity limit, issuer maintenance window) has changed.

The opposite of smart retries is blind retries — immediately re-running the same charge with the same parameters. Blind retries rarely succeed because the condition that caused the decline has not changed. Worse, repeated failed attempts can flag the merchant as high-risk with the processor, degrading future approval rates.

How smart retry timing works

Smart retry systems analyze the decline code and schedule the next attempt accordingly:

Insufficient funds (code 51) — retry after payday cycles, typically the 1st and 15th of the month.
Velocity limit (code 65) — wait for the issuer's velocity window to reset, often 24 hours.
Issuer unavailable (code 91) — retry after a short delay (minutes to hours) once the issuer is back online.
Do Not Honor (code 05) — analyze historical patterns; some issuers are stricter at night or on weekends.
Fraud-flagged transactions — do not auto-retry; route to customer outreach instead.

Smart retries and decline classification

Smart retries work best on soft declines — temporary conditions where the card itself is valid. Insufficient funds, velocity limits, and issuer-unavailable errors are soft: the underlying problem can resolve on its own, and a well-timed retry may succeed.

Hard declines — expired cards, closed accounts, lost/stolen cards — will not benefit from retries. The card itself is the problem, and no amount of timing will change that. Smart systems classify the decline and route hard declines to customer outreach instead of wasting retry attempts.

How Revatto handles smart retries

Revatto combines smart retries with human outreach for complete recovery coverage. AI classifies the decline, times retries for soft declines, and routes hard declines to email and SMS outreach under your brand. When retries stall, a human follows up.

You only pay when the payment is recovered — 20% of the first recovered payment, $0 monthly. The retry timing adapts based on decline code, processor, and historical success rates for your specific merchant profile.

See what Revatto would recover for you

Failed payments recovered automatically — no engineering, no manual chasing. We do the work; you keep the revenue.

See Your Recovery Potential