Dunning is the automated sequence of retries, alerts, and reminders that recovers failed subscription payments before a customer churns without ever meaning to. The single highest-leverage move is pairing smart retries with a one-click billing-update link and a staged, multi-channel message sequence. Get that combination right, and you cut involuntary churn without a single collections call.
TL;DR:
- Automated retries should be tailored by decline reason, with hard declines receiving no retries and soft declines retrying up to 15 times within 30 days.
- Prevention tactics like card-update services and proactive notices ahead of expiration significantly reduce involuntary churn, which can account for up to 40% of total cancellations.
- The recovery process must include stage-specific messaging, with clear, actionable information and one-click update links in emails and in-app alerts delivered within the first week.
- High-value accounts require manual follow-up and customized thresholds for pausing or canceling, as automation alone may not be sufficient to recover their payments.
- Using a single platform that combines payments, recovery, and messaging improves efficiency and reduces the likelihood of lost revenue due to disconnected tools.
Table of Contents
- What Dunning for Subscriptions Actually Means
- The Three-Phase Dunning Process: Prevention, Recovery, Escalation
- Retry Logic and Segmentation: When and How Often to Try Again
- Dunning Communications: Sequence, Channels, and Message Design
- Tooling and Automation: Smart Retries, Card Updaters, and Routing Fallbacks
- Measuring Dunning: The Metrics and Cohort Reports That Matter
- How Commas Maps to This Dunning Playbook
- Your 30-Day Dunning Rollout Checklist
- Put Your Dunning Recovery on One Platform
- Where to Go Deeper on Dunning Standards
- Sources
- FAQ
What Dunning for Subscriptions Actually Means
Dunning gets confused with debt collection constantly, and that mix-up costs businesses money. Collection is chasing someone who won't pay. Dunning for subscriptions is recovering payment from someone who wants to pay but hit a technical snag, an expired card, a bank that flagged the charge, a processor hiccup. The customer isn't the problem. The plumbing is.
That distinction matters because involuntary churn (customers who leave not by choice but because their payment silently failed) accounts for 20% to 40% of total churn at most subscription companies. That's revenue walking out the door with no complaint, no support ticket, and no warning until the monthly recurring revenue report looks off.
Most declines trace back to a handful of repeat offenders:
- Expired or reissued cards that were never updated on file
- Soft declines, temporary issues like insufficient funds or a bank's fraud filter
- Issuer routing quirks, where a transaction gets flagged for extra verification
- Processor-side errors unrelated to the customer's card at all
Each cause needs a different fix, which is exactly why a one-size-fits-all retry schedule fails so often.
The Three-Phase Dunning Process: Prevention, Recovery, Escalation
Effective dunning runs in three distinct phases, and treating them as one blob is where most billing teams lose recoverable revenue. Each phase has its own timeline, owner, and success metric.
- Prevention (ongoing, before any failure happens). This is where card-account-updater services earn their keep, quietly refreshing expired or reissued card numbers before a charge ever gets declined. Pair that with pre-expiry notices sent 30 days ahead for annual plans and 3 to 7 days ahead for monthly ones, plus routine data hygiene to catch dead email addresses and stale billing contacts before they become a problem.
- Recovery (days 0 through 7 after a failed charge). The clock starts the moment a payment bounces. Fire the first retry within the smart-retry window rather than immediately, since instant resubmission on the same card usually just fails again. Send a day-0 email with a one-click update link that takes the customer straight to a hosted payment page, no login required. Layer in an in-app reminder banner for anyone who logs into your product during this window.
- Escalation (day 7 onward). This is where judgment calls replace automation. Decide in advance whether a non-paying account gets paused (access frozen, data retained) or canceled outright, and set that threshold by account value, not gut feeling. High-value or annual-contract accounts deserve a personal email or phone call before the system ever cancels them. Set a firm write-off date, typically 14 to 30 days out, so accounts don't linger in limbo indefinitely.
The phases overlap in practice. A prevention tactic like an account updater keeps running during recovery and escalation too. What changes is who's driving: automation in phase one and two, a human decision-maker by phase three.
Retry Logic and Segmentation: When and How Often to Try Again
Not every decline deserves the same number of attempts, and treating them identically wastes gateway fees while annoying customers with duplicate charge notifications from their bank.
Start by classifying the decline itself:
- Hard declines (stolen card, closed account, "do not honor") should get zero automatic retries. Retrying here just burns processor fees and risks fraud flags on your merchant account.
- Soft declines (insufficient funds, temporary hold, issuer timeout) are the ones worth retrying, and Visa's own response-code rules permit reattempts on these codes up to 15 times within a 30-day window.
- Ambiguous or processor-side errors deserve one immediate retry, since these often resolve within minutes.
Smart retries beat fixed-interval retries because they adjust timing based on decline reason and historical success patterns, rather than blindly trying every 24 or 72 hours regardless of why the card failed. A card declined for insufficient funds, for instance, recovers better on a retry timed around typical payday cycles than one fired at a random midnight interval.
Segment your retry strategy by account type, too. A $15-a-month self-serve subscriber can ride the fully automated sequence end to end. A $50,000 annual enterprise contract should never touch a generic dunning email. That account needs its billing contact flagged for manual follow-up the moment the first retry fails, not after the third automated attempt strikes out.
Pro Tip: Pull your decline-reason codes into a monthly report before you touch retry timing. Half the "failed payment" tickets billing teams chase are soft declines that would have resolved on their own with one well-timed retry.
Dunning Communications: Sequence, Channels, and Message Design
Every recovery email, text, or in-app alert needs to answer four questions instantly: how much is owed, in what currency, for which subscription or workspace, and what's the one action to take right now. Bury any of those and recovery rates drop.
A message that just says "your payment failed, please update your card" without showing the exact amount or a direct link makes the customer do research they'll postpone indefinitely. The winning format states the number, names the plan, and drops a secure, one-click link straight to a hosted update page, exactly the pattern Recurly's dunning documentation recommends for reducing friction at the moment of highest customer intent.
A cadence that performs well across most subscription businesses looks like this:
- Day 0: Automated email immediately after the failed charge, friendly tone, clear amount, one-click update link
- Day 3: Second email plus an in-app banner for anyone who logs in
- Day 7: Reminder with mid-window urgency, still helpful in tone, not threatening
- Day 12 to 14: Final notice before pause or cancellation, stated plainly with the exact date
For enterprise or high-ARR accounts, layer in SMS or a phone call well before that final notice. Email alone routinely gets buried in a billing department's inbox. Keep every message branded and warm. Nothing should read like a form letter from a collections agency, because functionally, it isn't one.
Consumer-protection and telemarketing rules vary by channel and region, and phone-based follow-up in particular sits under regulations like the FTC's guidance on debt-collection practices. Review your outreach scripts against local rules before scaling phone or SMS dunning, especially for anything that could be read as a collections-style demand.
Tooling and Automation: Smart Retries, Card Updaters, and Routing Fallbacks
Smart retry engines work by analyzing the specific decline code and retrying at the moment historically most likely to succeed, rather than on a fixed schedule blind to why the card failed in the first place. That distinction alone is why automated dunning outperforms manual follow-up.
Card-account-updater services do quieter but equally important work. Visa's Account Updater automatically refreshes replacement PAN numbers when a card gets reissued, meaning a subscriber's payment can keep processing without them ever noticing their card expired.
- Enable automatic card-updater syncing on every recurring payment method, not just failed ones
- Route persistent failures to a second gateway when your primary processor shows elevated decline rates
- Prompt an alternate payment method (a different card, a bank transfer) after two failed attempts on the same card
Stripe's own dunning guidance backs this layered approach: automated retries, customizable emails, and a self-serve billing portal together recover more revenue than any single tactic alone. The response-code reclassification Visa rolled out also means merchants who haven't updated their retry logic recently are likely retrying declines that no longer qualify for reattempt, a quiet source of wasted gateway fees.
Measuring Dunning: The Metrics and Cohort Reports That Matter
You can't tune a dunning process you're not measuring correctly, and the biggest measurement mistake is using the wrong denominator.
Track these core metrics on a rolling cohort basis:
- Recovery rate: recovered failed invoices divided by eligible failed invoices, excluding refunded, disputed, or never-eligible invoices from the denominator
- Recovered revenue: dollar value recovered divided by total failed revenue for the period
- Involuntary churn rate: subscribers lost specifically to payment failure, isolated from voluntary cancellations
- Time to recovery: average days between initial failure and successful payment
- Retry success by decline reason: broken out by hard, soft, and processor-error categories so you can see which retry rules are actually working
Run a weekly report on retry success by decline code to catch a gateway problem fast. Run a monthly cohort report on recovery rate and involuntary churn to see whether cadence or segmentation changes are moving the number. Cohort reporting matters because lumping every failed payment into one bucket hides which segment (self-serve versus enterprise, monthly versus annual) is dragging your overall recovery rate down.
How Commas Maps to This Dunning Playbook
Commas Payments builds one-click payment-update experiences directly into checkout, so the link in a day-0 recovery email doesn't send a customer hunting through account settings. The update flow and the original purchase experience share the same interface, which is the exact friction point most dunning sequences lose customers at.
The platform also uses AI-driven funnel logic to help coordinate messaging sequencing and retry timing without stitching together a separate email tool, a separate retry engine, and a separate analytics dashboard. For higher-touch recovery scenarios, tools like the Qualifier feature help identify which accounts warrant a personal follow-up instead of another automated email, and agency or partner billing setups can route recovery communications through the right team via agency billing or the Affiliate Center when a partner manages the customer relationship.
Your 30-Day Dunning Rollout Checklist
Days 1 to 3: Turn on card-account-updater syncing, add a one-click payment-update link to every failure email, and get the day-0 to day-1 email firing automatically.
Days 4 to 14: Build out smart retry logic by decline code, pull enterprise and annual accounts out of the automated sequence, and add in-app reminder banners.
Days 15 to 30: Set data-backed pause versus cancel thresholds, turn on personal outreach for high-ARR accounts, and start running weekly cohort reports.
— FanBasis
Put Your Dunning Recovery on One Platform
Most billing teams end up duct-taping together a payment processor, a separate email tool, and a spreadsheet to track recovery, and each handoff between them is where a recoverable payment quietly slips through. Commas combines payments, checkout, and funnel logic in a single dashboard, so the one-click update link in your day-0 recovery email and the original purchase flow run through the same system instead of three disconnected ones.
That matters most for the accounts you can't afford to lose to a bounced card. Vibe Funnels lets you build the update and upsell flow a recovering customer sees without hiring a developer, and Commas Payments handles the retry-friendly checkout underneath it. If you're rebuilding your dunning sequence this quarter, start by looking at how your payment-update link actually performs on mobile. Check out Commas Payments to see how an integrated checkout and one-click update flow could fit your current billing stack.
Where to Go Deeper on Dunning Standards
Billing teams implementing any of the retry rules above should read the primary documentation directly rather than relying on secondhand summaries. Visa's Account Updater program and its response-code resubmission rules govern what your gateway is legally allowed to retry and how often. On the platform side, Recurly's dunning management documentation and Stripe's dunning guidance both lay out configuration specifics worth comparing against your own setup. For a broader view of how dunning fits into retention strategy overall, this rundown of proven retention tactics is a useful companion read.
Sources
- Dunning management — Recurly docs
- Dunning Management: The Complete Guide for SaaS — Baremetrics
- Visa Account Updater (VAU) — Visa developer
- Visa: updates to rules for declined transaction resubmission and use of authorization response codes
- Dunning: What subscription-based businesses need to know — Stripe
FAQ
What Is Dunning in a Subscription Business?
Dunning is the automated process of retrying failed payments and notifying customers to update their billing details before their subscription lapses. It runs in three phases, prevention, recovery, and escalation, and combines smart retries with staged email, SMS, or in-app messaging.
What Does Dunning Mean, Exactly?
The term comes from "dun," an old word for pressing someone to pay a debt, but in subscriptions it describes recovering payments from customers who want to stay, not chasing down people who refuse to pay. That's why subscription dunning leans on helpful reminders and one-click update links rather than collections-style language.
Is a Dunning Letter Legal?
Yes, dunning communications are legal, but they need to follow consumer-protection and telemarketing rules depending on the channel and region. Phone-based follow-up in particular falls under regulations covered in the FTC's debt-collection guidance, so review your scripts before scaling SMS or call-based dunning.
What Does "Dunning Costs" Mean?
Dunning costs refer to the operational expense of running failed-payment recovery, including gateway fees for retry attempts, the cost of card-updater services, and staff time spent on manual escalation for high-value accounts. Retrying hard declines needlessly is one of the biggest avoidable costs, since certain decline codes aren't eligible for resubmission and retrying them anyway just burns processor fees.
How Do I Choose the Right Dunning Cadence?
A cadence that works for most subscription businesses sends a day-0 email immediately after the failure, a follow-up around day 3, a reminder near day 7, and a final notice before day 14. Adjust the exact timing by account segment, since enterprise accounts typically need personal outreach layered in well before that final notice.