Every failed payment is a subscription dying in slow motion. The customer didn’t churn out of malice. Their card expired, their bank flagged a transaction, or they hit a spending limit. Left alone, that account drifts into delinquency, then cancellation, then a negative review on your churn dashboard. The worst part? Most of these customers would have stayed if someone — or something — had simply nudged them to fix the problem.
That is what dunning management does. It is the automated process of retrying failed payments, sending targeted emails, and updating billing information before the customer even realizes something went wrong. For solopreneurs running micro-SaaS products, a solid dunning workflow can recover 15–40% of what would otherwise be involuntary churn. That is revenue you do not have to re-acquire. It is money already in your pipeline that almost walked out the door.
This guide is not a theoretical overview of billing theory. It is a practical playbook for building or choosing a dunning system that runs without you, keeps cash flow predictable, and turns payment failures into a non-event. We will cover why payments fail, how to build a recovery sequence, which tools handle the heavy lifting, and the specific metrics you need to watch.
Why Payments Fail (And Why It Is Not Your Fault)
Before you fix the problem, you need to understand the mechanics. Payment failures fall into two categories: hard declines and soft declines.
Hard declines mean the card is dead. The account is closed, the card was stolen and replaced, or the bank issued a new number and forgot to tell you. These recover at low rates — maybe 5–10% — because the customer has to actively update their billing information. Your job is to make that update as frictionless as possible.
Soft declines are temporary. The card has insufficient funds, the issuer requested a retry, or the bank flagged the charge for fraud review. These are your goldmine. A well-timed retry, sent at the right hour on the right day, can recover 30–60% of soft declines without the customer ever lifting a finger.
Common specific reasons include:
- Expired cards: The most predictable failure. Cards expire every 3–5 years. If you are not using an account updater service, you are guaranteed to hit this.
- Insufficient funds: Common for B2B cards near month-end or consumer cards after payday cycles.
- Bank fraud rules: International transactions, unusually large amounts, or velocity triggers can cause a decline even on a valid card.
- Incorrect CVV or address: Usually a data entry issue during manual card updates.
- 3D Secure authentication failure: More common in Europe where Strong Customer Authentication (SCA) is required.
The critical insight: most of these failures are solvable. The customer still wants your product. You just need a system that catches the failure and acts before the subscription lapses.
The Anatomy of a Dunning Sequence
A dunning sequence is a timed workflow that triggers when a payment fails. It combines automated retries, email outreach, and in-app warnings. The best sequences are simple, relentless, and respectful. They do not apologize for existing. They treat the failure as a technical problem to be solved.
Phase 1: The Silent Retry (Hour 0–48)
Do not email the customer immediately. Many soft declines resolve on their own if you simply retry at a better time. The best practice is to retry after 24 hours, then again after 48 hours. Stripe data shows that retrying on the 3rd, 5th, and 7th day after a failure captures the most successful recoveries.
Why wait? Because “insufficient funds” often means “insufficient funds today.” A card that fails on a Sunday evening may sail through on Tuesday morning. Retrying too aggressively wastes processor fees and trains the bank’s fraud model to distrust your merchant account. Patience pays.
Tools that handle smart retries:
- Stripe Billing: Built-in dunning with configurable retry schedules. Best for teams already on Stripe.
- Chargebee: Advanced retry logic with machine learning that optimizes retry timing based on your specific decline patterns.
- Recurly: Enterprise-grade retry algorithms with customizable retry windows and backup payment method fallback.
- Paddle: Handles retries automatically as part of their merchant-of-record model. Good if you want to outsource all billing complexity.
- Braintree: Native retry logic with configurable retry counts and intervals.
Phase 2: The First Email (Day 3)
If the silent retries fail, it is time to notify the customer. The first email should be technical, not salesy. Assume the customer does not know their payment failed. Assume they are busy. Give them a one-click fix.
Your first email must include:
- The exact reason for the failure (“Your card ending in 4242 was declined because it expired on 04/2026.”)
- A direct link to update billing information — no login required if possible
- A clear statement that their service is still active (create urgency without threatening)
- Contact information if they need help
Subject line formula: “Action needed: Update your [Product] billing info.” No clickbait. No fear. Just clarity.
Email tools that integrate with billing:
- Customer.io: Excellent for behavioral triggered emails. You can segment by failure reason and personalize the message.
- Loops: Simple, API-first email platform designed for SaaS. Good for lightweight dunning flows.
- Postmark: Best deliverability for transactional emails. Your dunning emails must land in the inbox, not promotions.
- SendGrid: Scalable and affordable. Use their dynamic templates to customize by failure type.
- Mailgun: Developer-friendly with strong webhook support for real-time retry triggers.
- Buttondown: Minimalist newsletter tool that also handles transactional sends. Great for indie hackers.
- ConvertKit: Surprisingly capable for SaaS founders already using it for marketing automation.
Phase 3: The Escalation (Day 7–14)
If the first email fails, send a second. Change the tone slightly. The service is still running, but the clock is ticking. Mention the specific feature or data they will lose if the subscription lapses. Not a threat — a reminder of value.
Example: “Your [Product] account is still active, but your annual report data will be paused if billing is not updated by May 27. Update your card in 30 seconds.”
At day 14, send a final notice. This one should be shorter, more direct, and include a calendar date. “Your subscription will pause on June 3. Click here to update your card.”
Throughout this phase, continue background retries every few days. If the customer updates their card on day 10, you want the system to immediately retry the outstanding invoice and confirm success.
Phase 4: The Grace Period (Day 14+)
Before you cancel the account, consider a grace period. For some products, especially those with data or collaboration features, immediate cancellation is destructive. A 7-day grace period where the account is “paused” but not deleted gives the customer one more chance to recover and preserves goodwill.
During the grace period:
- Lock new feature access but preserve existing data
- Send one more email: “Your account is paused. All your data is safe. Update billing to resume instantly.”
- Stop all background retries to avoid racking up processor fees on a dead card
Building Your Own Dunning Flow vs. Buying a Tool
For micro-SaaS founders, the build-vs-buy decision is a constant tension. Dunning is no exception.
Build It If:
- You are already deep into Stripe and enjoy writing webhook handlers
- You have fewer than 500 customers and failure volume is low
- You want full control over email timing, copy, and UX
- You have a custom billing model that off-the-shelf tools do not support
A basic DIY dunning flow in Stripe looks like this: listen for invoice.payment_failed, schedule a retry via Stripe’s API, trigger a Postmark email on day 3, trigger a second email on day 7, and cancel the subscription on day 14 if no payment succeeds. It is maybe 200 lines of code if you are using a framework like Next.js or Laravel.
Buy It If:
- You process more than 1,000 invoices per month
- Your failure rate is above 3% and manual recovery is eating your time
- You want machine learning retry optimization without building it
- You need multi-gateway fallback (Stripe fails, retry on Braintree)
Most billing platforms — Chargebee, Recurly, Paddle, Stripe Billing — include dunning as a standard feature. The cost is usually a small percentage of recovered revenue, which is trivial compared to the engineering time you would spend building and maintaining your own retry logic.
Account Updater Services: The Preventive Medicine
The best dunning is the dunning you never have to run. Account updater services automatically refresh card details when banks issue new numbers. Visa, Mastercard, and Amex all offer these programs, and most payment processors integrate them.
Stripe offers this through their card account updater. It runs silently in the background and has recovered millions of expired-card failures before they ever trigger a dunning email. Chargebee and Recurly include similar services.
The catch: not all card types are supported, and not all banks participate. But for the cards that are covered, account updater can cut your involuntary churn by 20–30% before any sequence even fires. It is the closest thing to a free lunch in SaaS billing.
Turn this on before you build a single email. It is a 30-second configuration change in most platforms and pays dividends for years.
Key Metrics to Track
If you do not measure recovery, you are flying blind. Track these four numbers:
- Recovery rate: The percentage of failed payments that eventually succeed. Benchmark: 15–25% for basic dunning, 30–45% for advanced sequences with smart retries.
- Days to recovery: How long it takes from first failure to successful payment. If this is climbing, your retry timing is off.
- Email click-through rate: On dunning emails, this should be 40–60%. Lower means your CTA is buried or your subject line is weak.
- Involuntary churn rate: The percentage of total churn caused by payment failures. If this is above 5% of your total customer base per month, you have a billing problem worth fixing immediately.
Most billing dashboards expose these numbers. If yours does not, build a simple spreadsheet: log payment failures, track outcomes, and calculate recovery rates weekly. The data will tell you exactly where your sequence is weak.
Common Mistakes That Kill Recovery
- Emailing too soon: A customer who sees a billing email 2 hours after a soft decline is annoyed, not informed. Give the retry cycle room to work.
- Generic copy: “Your payment failed, please update billing” is lazy. Name the failure reason. Name the product. Name the consequence.
- No mobile optimization: 60% of these emails are opened on phones. If your billing update form is not thumb-friendly, you are losing recoveries.
- Ignoring timezone patterns: A card that fails at 2 AM local time is likely a bank maintenance window. Retry during business hours in the customer’s timezone.
- Canceling too fast: Some founders cancel subscriptions at the first failure to “keep their numbers clean.” That is financial self-harm. The customer did not choose to leave. Give them a chance to stay.
Strategic Takeaway
Dunning management is not a back-office accounting task. It is a retention strategy. Every failed payment is a customer who still wants your product but hit a technical speed bump. Your job is to clear the road before they give up and drive away.
Start with account updater to prevent the most common failures. Add smart retries to catch soft declines without bothering the customer. Build a 3-email sequence that is clear, specific, and mobile-optimized. Measure recovery rates weekly. And above all, treat dunning as a product feature, not a billing afterthought.
The solopreneurs who master this recover thousands of dollars per year in revenue they never had to re-market, re-sell, or re-onboard. That is the leverage of automation applied to the most boring, most important part of your business: getting paid.
