Summarised from Stripe's own documentation
Stripe Smart Retries: what they retry, and the declines they can't fix
Stripe Billing retries failed payments automatically, and it does that part well. This page is a plain summary of what Stripe's documentation says those retries can and cannot fix — quoted and linked, so you can check every line against the source. There are no figures of ours on this page, because we have no published recovery results to quote yet.
Source: docs.stripe.com/billing/revenue-recovery/smart-retries
Checked 2 October 2026. Stripe's documentation is the source of truth; if it changes, this summary is out of date before Stripe is.
What Smart Retries actually do
- Smart Retries use data points to choose the best time to retry a failed payment, rather than retrying on a fixed schedule — and Stripe recommends them over a custom schedule.
- You set how many retries and over how long. The options are 1 week, 2 weeks, 3 weeks, 1 month or 2 months — and Stripe's recommended default setting is 8 tries within 2 weeks.
- It is configured in the Dashboard without writing code, and the
invoice.payment_failedwebhook reports each failure and retry attempt.
“The recommended default setting is 8 tries within 2 weeks.”
When Stripe doesn't retry at all
Stripe's documentation lists four cases in which no retry is attempted:
- No payment methods are available.
- The issuer returned a hard decline code.
- The payment card is India-issued.
- The Stripe Connect account has been disconnected.
“Stripe doesn't retry payments if: …”
The hard declines a retry can never fix
When the card issuer returns one of these hard decline codes, Stripe can't retry the payment at all — a retry can only succeed once a new payment method is attached to the customer. Stripe schedules the retries anyway, and the attempt counter keeps rising, but nothing is actually charged.
- incorrect_number
- lost_card
- pickup_card
- stolen_card
- revocation_of_authorization
- revocation_of_all_authorizations
- authentication_required
- highest_risk_level
- transaction_not_allowed
“If a failure returns a hard decline code, we can't retry invoice payment without a new payment method. Retries continue to be scheduled, and attempt_count continues to increment, but retries only execute after detecting a new payment method.”
“For these failures, the scheduled retries continue but the payment only executes if you obtain a new payment method.”
Source: Stripe Docs — Hard decline codes
A custom retry schedule caps at three retries
If you turn Smart Retries off and write your own rules instead, the schedule is short: three retries, each with a set number of days after the previous attempt.
“You can configure up to three retries, each with a specific number of days after the previous attempt.”
What happens when the retries run out
Stripe hands the subscription to whichever end state you configured:
- Cancel the subscription
- The subscription becomes canceled after the maximum number of days defined in the retry schedule.
- Mark the subscription unpaid
- The subscription becomes unpaid after the maximum number of days defined in the retry schedule. Invoices continue to be generated and stay in draft.
- Leave the subscription past-due
- It stays past due after the maximum number of days defined in the retry schedule, and continues to be charged under your retry settings.
- Pause the subscription
- If it is eligible, it becomes paused, and Stripe doesn't generate new subscription invoices until it resumes.
“After the final payment attempt, Stripe makes no further payment attempts. Changing your subscription settings only affects future retries.”
Source: Stripe Docs — If recovery fails
Where the gap is
Read the four sections above together and the shape of the gap is hard to argue with. Stripe's retries are timing logic on a payment method that still works. For a hard decline, the retry is scheduled but never executes — the payment needs a new card, and the only person who can attach one is your customer. Stripe cannot ask them for it. Stripe can email them if you switch those emails on — but an email can't attach a card, and that is the step where a recoverable failure becomes a lost invoice.
Recoverly does the chasing: we watch for failed payments on your Stripe account, write to the customer with a link to Stripe's own hosted page for that invoice, and keep going through the retry window Stripe has given up on. During pilots a person runs that schedule and sends each message by hand, from the text our tool renders. We're looking for our first design partners now, so we have no case studies to show you — what we do have is a free audit that tells you what is actually recoverable in your account.
And the honest limit, from the same documentation: hard declines, stolen or cancelled cards and some regional mandates need a new payment method, and India-issued cards aren't retried at all. Where a customer won't attach a new card, nothing recovers that invoice. The audit separates the two.
Source: Stripe Docs — Revenue recovery
Find out what this is costing you
The free Failed-Payment Leak Audit gives you one page: the money at risk from your own Stripe invoice data, which declines a new card would fix, and which ones it wouldn't. We'll come back to you by email.
Request the free leak audit