Recover Failed Payments Automatically With Baremetrics
Failed payment recovery turns declined subscription charges back into paid invoices. Some churn is not churn at all. The customer still wants the product, but a card expired, a bank blocked the charge, or funds ran short on billing day. Thi...
Failed payment recovery turns declined subscription charges back into paid invoices. Some churn is not churn at all. The customer still wants the product, but a card expired, a bank blocked the charge, or funds ran short on billing day.
This guide explains why charges fail, how to match each decline type to the right response, and how Baremetrics Recover and Stripe settings automate the work. Vendor figures appear with a clear label. Confirm every setting on the official pages linked below before you change your billing flow.
Why failed payments cause silent churn
Voluntary churn points to product or pricing problems. Failed payments point to billing problems. Teams who merge both into one churn number hide the second problem and fix the wrong thing.
A failed charge works like a locked door with the customer still outside. The customer never chose to leave. Baremetrics says failed payments drain about 9 percent of MRR in its recovery article, while another section of the same article gives a range of 5 to 15 percent. Baremetrics gives no source for either figure, so measure your own failure rate before you set targets.
Start with a simple split in your billing reports. Count failed charges, count recovered charges, and count accounts which cancelled after a failure. Those three numbers show how much revenue the billing system loses without any customer decision.
Soft declines versus hard declines
Not every failure needs the same response. Baremetrics separates temporary problems from problems which need customer action.
| Decline type | Examples | Best response |
|---|---|---|
| Soft decline | Insufficient funds, network errors | Retry later, often around payday or midweek |
| Hard decline | Expired card, cancelled card | Ask the customer for a new card |
| Bank-side block | Fraud prevention rules at the issuer | Retry once, then ask for a different payment method |
Stripe documents hard decline codes on its Smart Retries page. Examples include incorrect_number, lost_card, stolen_card, and authentication_required. Stripe keeps scheduling retries for these failures, but the payment only runs after the customer adds a new payment method.
The five stages of automated recovery
A strong recovery system covers the whole life of a payment. Use the stages below as a checklist.
Stage 1: Prevent failures before they happen
Pre-dunning messages warn customers before a card expires. Baremetrics recommends about 30 days before expiry. Stripe offers an expiring card email which goes out 1 month before the card on file expires. Renewal reminders also help annual plans, because long gaps between charges make expired cards more likely.
Stage 2: Retry at better times
Stripe Smart Retries use AI to pick retry times from signals such as device activity and local time. Stripe lets you set a retry window of 1 week, 2 weeks, 3 weeks, 1 month, or 2 months. The recommended default is 8 tries within 2 weeks. Stripe also supports a custom schedule with up to three retries. Configure retries in the Stripe Dashboard under Billing, then Revenue recovery, then Retries.
Stage 3: Notify the customer fast
Stripe sends a failed payment email after each failed subscription payment when you enable the setting. Baremetrics advises a first email within 24 hours of failure and a sequence of 4 to 6 emails. Its example schedule runs on day 0, 3, 7, and 14. Keep every message short, plain, and tied to one action.
Stage 4: Make the card update easy
The email is half the job. If the update flow feels clumsy, recovery drops. Offer one secure link, a short form, and as few steps as possible. Stripe emails can link to a Stripe-hosted page or to your own subscription page, and the link stops working when the subscription becomes cancelled, incomplete expired, or unpaid.
Stage 5: Escalate or pause with a clear rule
Decide what happens when retries end. Stripe offers four end states: cancelled, unpaid, past due, or paused when the subscription is eligible. Baremetrics suggests in-app reminders and paywalls for active users who ignore email. Pick one rule, write the dates in your help center, and apply the same rule to every account.
What Baremetrics Recover adds
The Recover feature page lists these functions.
- A sequence of up to 7 customizable emails after a failed charge in Stripe or Braintree.
- Card expiration reminders at 30 and 7 days before expiry.
- Email and SMS sequences in one place.
- A branded billing link which writes the new card back to the processor.
- A widget with a banner and an optional paywall after a grace period.
- Pricing based on MRR after a 14 day free trial. Check the page for current terms.
For the full setup order, read this Baremetrics dunning management setup guide. For the Stripe side of the same problem, see Stripe failed payment recovery.
Stripe settings to check first
You may recover many failures with native Stripe settings before you add any tool. Review the options below in your Dashboard.
| Setting | Detail from Stripe documentation |
|---|---|
| Smart Retries window | 1 week, 2 weeks, 3 weeks, 1 month, or 2 months |
| Recommended default | 8 tries within 2 weeks |
| Custom retry schedule | Up to three retries, each set in days after the previous attempt |
| After retries end | Cancel, mark unpaid, leave past due, or pause |
| Failed payment email | Sent after each failed card payment when enabled |
| Expiring card email | Sent 1 month before the card expires |
| Email logs | Available on the Customers page for 60 days |
Stripe publishes these details on its customer emails page and its Smart Retries page. Stripe also skips retries when no payment method exists or when the card is India-issued.
Metrics to watch after launch
Review the numbers weekly for the first month, then monthly. Small timing changes can lift results without any pricing or product change.
| Metric | Meaning | If weak |
|---|---|---|
| Failure rate | Share of charges which decline | Check card types and billing dates |
| Recovery rate | Share of failed charges later paid | Review retry timing and email copy |
| Recovered MRR | Revenue won back | Compare against the cost of your tools |
| Days delinquent | Time between failure and payment | Shorten the first email delay |
| Involuntary churn | Cancellations after failures | Tighten your escalation rule |
Split soft declines from hard declines in every report. Strong soft decline recovery means retry timing works. Weak hard decline recovery means the email or the update page needs work.
Vendor figures to treat with care
Baremetrics publishes engagement figures for dunning emails. The company gives no method, so treat them as vendor claims.
| Email timing | Open rate reported | Recovery rate reported |
|---|---|---|
| Immediate email | 41.29 percent | 13.25 percent |
| Email at 30 days | 26.83 percent | 4.2 percent |
| Pre-dunning email | 47.41 percent | 14.37 percent |
The pattern is useful even if the exact numbers vary. Early messages perform better than late ones. Read the full Baremetrics article on recovering failed payments and the dunning management guide before you copy any benchmark.
Build your recovery plan in one afternoon
You can set up a basic system quickly. Work through the list below in order.
- Export the last three months of failed charges and label each decline as soft or hard.
- Turn on Stripe Smart Retries and choose a retry window.
- Enable the failed payment email and the expiring card email.
- Draft a four email sequence with one clear link in each message.
- Set the end rule for accounts with no payment: cancel, unpaid, past due, or pause.
- Add DNS records for your sending domain so reminders reach inboxes.
- Create a weekly report with failure rate, recovery rate, and recovered MRR.
After the first month, compare the report with your starting numbers. Keep what works and remove what adds noise. Annual plans deserve special care, because one failed yearly charge costs far more than one failed monthly charge. Consider personal outreach for large accounts. The Baremetrics dunning guide suggests personal contact for accounts above about $50,000 ARR between day 5 and day 7.
Common mistakes to avoid
- Sending the first email after a week instead of within 24 hours.
- Retrying hard declines instead of asking for a new card.
- Locking access on day one while retries are still running.
- Using harsh language in billing emails.
- Skipping DNS records, which sends reminders to spam.
- Tracking one churn number instead of splitting voluntary and involuntary churn.
Pair recovery work with wider retention work. Baremetrics lists proven ways to reduce SaaS churn across product, pricing, and billing.
FAQ
What is the difference between dunning and failed payment recovery?
Dunning means the reminder messages. Failed payment recovery covers retries, messages, card updates, and access rules together.
How soon should the first email go out?
Baremetrics recommends within 24 hours of the failure.
Should I retry hard declines?
No. Hard declines need a new payment method. Stripe keeps the retry schedule but runs the payment only after the customer updates the card.
Do I need a paid tool?
Not always. Start with Stripe retries and emails. Add a tool when you need SMS, a widget, a paywall, or deeper reporting.
Where do I confirm current pricing?
Use the official Baremetrics Recover page and the Stripe documentation. Prices and defaults change.
Conclusion
Failed payments need their own playbook. Split soft declines from hard declines, retry at sensible times, message customers within a day, make the card update simple, and set a clear end rule. Measure recovered MRR each week and adjust. Revenue lost to billing friction is not always gone. Often the customer only needs a better path back.
