Dunning for SaaS: How to Handle Failed Payments, Reduce Involuntary Churn and Write Recovery Emails
SaaS · Billing
What dunning is, why payments fail, a five-part strategy, an illustrative timeline, an email outline and metrics.
Last updated: October 2026. Written by Athar Ahmad, Certified Bubble.io Developer and Tech Architect, Simple Automation Solutions.
Quick answer
Dunning is retrying failed subscription payments and communicating with customers to recover revenue and avoid involuntary churn. Payments fail for expired cards, insufficient funds, bank declines, authentication requirements and card limits. Use smart retries over several days, a friendly email sequence with one-click card updates, in-app prompts, a clear grace period and an easy reactivation route. Measure failed-payment rate, recovery rate, time to recovery and involuntary churn.
Key takeaways
- Involuntary churn from failed payments is often among the easiest churn to reduce.
- Use smart retries, friendly emails, in-app prompts and a grace period.
- Make updating payment details one click; never include payment details in email.
- Support authentication flows where required.
- Measure failed-payment rate, recovery rate and involuntary churn.
In this guide
What is dunning?
Dunning is the process of communicating with customers and retrying payments when a subscription charge fails, in order to recover the revenue and keep the customer. The term comes from the practice of chasing debts. In SaaS it matters because failed payments cause involuntary churn, customers who never meant to cancel but whose subscriptions lapse anyway.
Why do payments fail?
| Cause | Typical share of the problem | What helps |
|---|---|---|
| Expired or replaced card | Common | Card update reminders, account updater services where offered |
| Insufficient funds | Common, often temporary | Retries on different days, such as after typical pay dates |
| Bank decline or fraud flag | Occasional | Retries, asking the customer to contact the bank |
| Authentication required | Can arise where strong customer authentication rules apply | Support for authentication flows, prompts to complete verification |
| Card limit exceeded | Occasional | Retry later, suggest another method |
| Technical errors | Rare | Monitoring, retries and alerts |
Exact rates vary by business, so measure your own failed-payment rate and recovery rate rather than relying on generic figures.
A dunning strategy in five parts
- Smart retries. Retry failed payments on a schedule over several days, rather than once, and avoid hammering the card. Many providers offer built-in retry logic.
- A friendly email sequence. Notify the customer, explain what happened and make updating payment details one click.
- In-app prompts. A clear banner or message when payment has failed, with a link to update.
- A sensible grace period. Keep access for a defined period before restricting it, and say so clearly.
- A clean end. If payment cannot be recovered, pause or cancel according to your terms, and make reactivation easy.
Example dunning timeline (illustrative)
| Day | Action |
|---|---|
| Day 0 | Payment fails. Retry automatically. Send a short, friendly notice with a link to update payment details. |
| Day 3 | Retry. If it fails, send a second email and show an in-app message. |
| Day 7 | Retry. Send a clear reminder explaining that access will change on a given date. |
| Day 10 to 14 | Final retry. Send a final notice. Offer help if the customer is struggling. |
| After the grace period | Pause or limit access according to your terms. Keep data safe and allow easy reactivation. |
Adjust timing to your product and customers. Annual plans and high-value customers may deserve personal outreach.
Email copy principles
- Be calm, clear and helpful, not accusatory.
- Say what happened, what will happen next and by when.
- Give one obvious action: update payment details.
- Do not include sensitive payment details in the email.
- Provide a way to get help.
- Follow your terms and any consumer or email marketing rules where you operate.
Dunning email outline
Subject: We could not process your payment for [Product]
Opening: Your latest payment did not go through, which can happen for several ordinary reasons.
Action: Please update your payment details here: [secure link].
What happens next: We will try again on [date]. Your access continues until [date].
Help: If you have questions, reply to this email.
What should you measure?
| Metric | What it tells you |
|---|---|
| Failed payment rate | How often charges fail |
| Recovery rate | Share of failed payments eventually collected |
| Time to recovery | How quickly you recover |
| Involuntary churn | Customers lost to failed payments |
| Support contacts about billing | Where the experience is confusing |
What mistakes should you avoid?
- A single retry, then cancel.
- Silent failure: the customer never knows.
- Harsh or threatening language.
- No easy way to update a card.
- Cutting access instantly with no grace.
- Ignoring authentication requirements.
- Never measuring recovery.
How do you build it?
Dunning needs events from your payment provider, such as failed payments and recoveries, stored against each customer, plus email and in-app messages, access rules and an admin view. Plan these in the PRD. See our security guide for handling billing data safely, and what to cut before you build. Builds at Simple Automation Solutions start at $3,500, and a $345 Discovery Sprint, credited toward the build, scopes the billing flow. See also our guide to churn analysis.
Frequently asked questions
What is dunning in SaaS?
The process of retrying failed subscription payments and communicating with customers to recover the revenue and avoid involuntary churn.
Why do subscription payments fail?
Expired or replaced cards, insufficient funds, bank declines, authentication requirements, card limits and occasional technical errors.
How many times should I retry a failed payment?
Several times over a number of days, rather than once, timed sensibly. Many providers offer built-in smart retries.
Should I cut off access immediately if payment fails?
Usually not. A clear grace period reduces frustration and recovers more revenue.
How do I reduce involuntary churn?
Retries, a friendly email sequence, in-app prompts, easy card updates, support for authentication and a sensible grace period.
Building subscriptions and want failed payments handled properly?
Email us your plans and payment provider. We will design the billing and recovery flow into the build.
Athar Ahmad, Certified Bubble.io Developer and Tech Architect, Simple Automation Solutions
About Simple Automation Solutions (SA Solutions)
Simple Automation Solutions is a Bubble.io development studio led by Athar Ahmad, a Certified Bubble.io Developer and Tech Architect. It builds web and mobile apps, client portals and SaaS products for founder-led businesses such as law firms, accounting firms, boutique agencies and consultants. Services include a free 30-minute Idea Audit, a $345 Discovery Sprint (a Product Requirements Document delivered within 24–48 hours, credited toward the build) and builds starting at $3,500. Website: sasolutionspk.com.