Failed payment recovery for Stripe
By Sean Weas · Co-Founder, Product & EngineeringReviewed by Jay StevensUpdated 3 min readSummarize with AI
Quick answer
Stripe retries a card a few times and gives up. Smart Retries reattempts charges on an ML-timed schedule (a recommended 8 tries over two weeks), plus dunning emails and an automatic card updater — but the comms are email-only, and after the final retry the subscription just cancels. Dunning alone recovers ~20%; a human team gets 60–85%+. Revatto re-attempts the charge through Stripe's API and runs email + SMS + human outreach on top, done for you. You pay 20% of the first recovered payment, $0 setup, $0 monthly, cancel anytime.
The gap Stripe leaves open
What Stripe recovers on its own
- Smart Retries reattempts failed charges on an ML-timed schedule — a recommended 8 attempts over two weeks, configurable up to two months.
- A custom, non-ML retry schedule is capped at 3 attempts, each a set number of days apart.
- Automated dunning emails (failed payment, card expiring, 3D-Secure) link the customer to a hosted card-update page.
- The Card Account Updater refreshes saved card details automatically when an issuer reissues a card.
stops at
adds- Stripe stops at: Stripe's recovery comms are email-only — a failed-payment email, but no SMS and no phone outreach.Revatto adds: Email + SMS + a human recovery specialist, all sending under your brand.
- Stripe stops at: Smart Retries is an opaque ML black box — you can't layer your own per-decline timing on top without turning it off.Revatto adds: AI-timed retries you can see, plus cross-client learning from millions of recovered payments.
- Stripe stops at: After the final retry, Stripe makes no further attempts — the subscription just cancels, with no win-back.Revatto adds: Recovery continues past Stripe's last attempt, with human follow-up that actually reconnects the card.
- Stripe stops at: A custom (non-ML) retry schedule maxes out at 3 attempts.Revatto adds: Revatto re-attempts on a recovery-optimized cadence and falls back to a backup card when the primary keeps failing.
How Revatto recovers failed Stripe payments
- 1Detect the failure instantlyRevatto ingests Stripe's invoice.payment_failed webhook the moment a charge fails — no polling, no delay.
- 2Diagnose the declineRevatto reads Stripe's named decline_code (most processors only return generic text) to tell a soft retry-now from a hard needs-the-customer.
- 3Re-attempt intelligentlyWhere a retry can clear it, Revatto triggers an AI-timed rebill through Stripe's API, falling back to a backup card on file when the primary keeps failing.
- 4Reach the customerWhere a retry won't clear it, email + SMS + a human recovery specialist reach the cardholder under your brand to update the card.
- 5Stop on successStripe's invoice.payment_succeeded webhook ends the sequence automatically — no double-charge, no stray outreach.
How a Stripe decline maps across stacks
Insufficient funds — ISO 51 (a charge Stripe Smart Retries targets). Recovery looks the same across every stack Revatto runs on — here is how the same issuer decision is named on each.
ProcessorCodeWhat it’s called
ISO 8583
Code51
CalledInsufficient FundsClassic soft decline
Codeinsufficient_funds
Calledcard_declinedStripe Smart Retries target this code
Code2
CalledDeclinedReason code 2 — detail in the response text
Code202
CalledInsufficient fundsresponse_code 202 (response = 2)
See what Revatto would recover from Stripe
Failed payments recovered automatically — no engineering, no manual chasing. We do the work; you keep the revenue.
Frequently asked questions
No — it works on top of them. Stripe's Smart Retries handle the silent ML-timed re-attempts; Revatto adds the channels Stripe doesn't (SMS and human outreach), continues recovery past Stripe's final attempt, and applies cross-client learning Stripe's per-account ML can't.
Yes. Stripe exposes a full payment API, so Revatto can trigger a rebill — including against a backup card on file — on a recovery-optimized schedule, not just send a reminder email.
No. Stripe's revenue-recovery notifications are email-only (failed-payment, card-expiring, and 3D-Secure emails). SMS and phone follow-up are exactly what Revatto adds.
Stripe makes no further attempts and transitions the subscription to canceled, unpaid, or past_due per your settings. Revatto keeps recovering past that point with human follow-up to reconnect the card.