%201.svg)
Smart Dunning Management: Recover Failed Payments Without Chargebacks
Chargebacks?
No longer your problem.
Recover 4x more chargebacks and prevent up to 90% of incoming ones, powered by AI and a global network of 20,000 merchants.
600+ reviews
TL;DR:
- Smart dunning management retries failed recurring charges on a decline-aware schedule, refreshes card details, and messages customers before revenue is lost for good.
- Retry by decline type: soft declines get scheduled retries inside Visa and Mastercard limits, while hard declines and authentication failures need a new payment method or customer action.
- Failed payments and chargebacks are different problems: dunning fixes technical declines; consent, descriptors, and clean cancellation prevent disputes, and evidence wins the rest.
- Measure both sides: track recovery rate next to dispute rate, because a retry that succeeds on an unexpected charge can end as a chargeback.
- Chargeflow covers the dispute side with Alerts to deflect chargebacks and Automation for evidence and submission.
Smart dunning management is the automated process of retrying failed recurring payments and prompting customers to fix billing problems before revenue is lost for good. It sits on top of your recurring payments stack and runs three layers: retry the charge at a better time, refresh the card details behind it, and message the customer in escalating steps.
The cost of skipping it is easy to calculate. Zoho Billing Academy puts the average monthly payment failure rate at about 2%, and if those failures go unrecovered, a 2% monthly loss compounds to about 22% of subscribers over twelve months (1 minus 0.98^12 = 21.5%). Recurly's July 2026 churn benchmarks show the exposure grows as plans get cheaper: annual median involuntary churn is 1.30% at $10 to $25 average revenue per customer and 0.18% at $250 and above.
Most failures come from expired cards, insufficient funds, and outdated billing details, and every one left unrecovered becomes involuntary churn. Choosing a recurring payment service provider with automated dunning built in decides how much of that revenue you keep. Not every failed renewal is a billing problem, though: some are disputes that retries will never fix, and this guide separates the two.
What Is a Dunning Management System?
Dunning management is a preset payment recovery process businesses use to manage overdue or failed payments. It identifies customers who missed a payment or are likely to default, then sends automated reminders (email, text, in-app) to update payment details before the failure becomes permanent revenue loss.
Dunning management software is the tool that runs this process: a standalone product or a module inside your billing platform that schedules retries, updates card details, and sends the customer messages. In accounts receivable and credit management, "dunning" means a sequence of overdue-invoice letters sent to business customers. In subscriptions and ecommerce it means automated retries on a saved card plus prompts to update it, which is the version this guide covers.
How Does Dunning Management Work?
A dunning sequence has three working parts: a retry schedule, customer messages, and an end state when recovery fails. It escalates from a gentle first reminder to a more urgent notice so you recover the payment without damaging the relationship. The same sequence sits on top of whatever billing platform you run, whether that is Stripe recurring payments with Smart Retries, Shopify recurring payments through a subscription app such as Loop Subscriptions, Square recurring payments, or PayPal recurring payments.
1) Effortless Failed Payment Recovery
If a customer's payment does not go through, the dunning engine retries the charge on a schedule instead of waiting for a person to notice. Stripe's recommended Smart Retries default is 8 tries within 2 weeks, and the window can be set to 1 week, 2 weeks, 3 weeks, 1 month, or 2 months; a custom schedule allows up to three retries, each a set number of days after the previous attempt. Smart Retries picks each moment using signals such as how many devices have recently presented the payment method and time-of-day success patterns.
More attempts are not always better: Stripe's card decline guidance warns that card issuers can read extra retries as potential fraud and decline legitimate charges. The system should also flag high-risk accounts, such as expired cards or a history of defaulted payments, so your team can reach out before the account escalates.
2) Retry Rules by Decline Type
Read the decline response before you schedule the next attempt. Issuers return a decline code with advice on whether a retry can ever succeed, and the card networks police the answer. Decline codes split into soft declines you can retry and hard declines you cannot.
| Decline Type | Typical Causes | What to Do |
|---|---|---|
| Soft decline | Insufficient funds, issuer temporarily unavailable, generic issuer decline | Retry on a schedule and message the customer if the retry also fails. Some soft declines are false declines from issuer fraud filters, so a later attempt can clear them. |
| Hard decline | Lost or stolen card, incorrect card number, invalid account | Stop retrying and request a new payment method. Stripe cannot execute retries after codes such as lost_card, stolen_card, or incorrect_number until a new payment method is on file. |
| Authentication required | A saved-card charge that needs a strong customer authentication challenge | A retry alone will not clear it. Send the customer a link to complete 3D Secure authentication. |
| Expired or replaced card | Card reissued or past its expiry date | Rely on automatic card updates first, then ask the customer to update the card. |
Card networks also cap how often you can retry. Visa allows up to 15 reattempts per card in 30 days for Category 2, 3 and 4 declines, with a per-attempt fee from the 16th, and any reattempt after a Category 1 (never approve) decline is chargeable, as Adyen's Visa documentation and Visa's merchant business news digest describe.
Mastercard limits retries on the same card and merchant to 10 in 24 hours and 35 in 30 days, and reattempts after merchant advice code 03 (do not try again) or 21 (payment cancellation) carry a separate fee, per Checkout.com merchant guidance. Fees vary by region and type, so confirm current limits and fees with your acquirer and keep your schedule well inside them.
3) Automatic Card Updates
Expired and replaced cards are the most preventable failure. Stripe works with card networks and automatically attempts to update saved card details when a customer receives a new card, including replacements for expired, lost, or stolen cards. Coverage is wide in the United States, where most American Express, Visa, Mastercard, and Discover cards can be updated, but it varies by country, and you cannot tell in advance which cards support updates. Treat card updates as a reduction in failures, not a guarantee, and keep pre-expiry reminders running for the cards that do not update.
4) Grace Periods and End States
A grace period is the window in which a customer keeps access while retries and reminders run. It is a billing-platform setting, not a card network rule, so set it deliberately. On Stripe Billing, when the retry schedule ends the subscription can be canceled, marked unpaid, left past due, or paused if it is eligible, per the Stripe Billing documentation.
Match the end state to plan value: pause or leave past due for high-value accounts you want to win back personally, and cancel cleanly on low-value plans so a stale card is not charged months later.
Failed Payment or Chargeback? What Dunning Can and Cannot Fix
Involuntary churn is a technical decline: the charge did not go through, and dunning is built to fix exactly that. A dispute is a decision the customer made about a charge that did go through, and no retry logic reverses it. Voluntary churn is a deliberate cancellation, a retention problem addressed with cancel flows such as founder-led video in the cancellation flow, not a billing one.
The two meet at one point: a recovered charge the customer did not expect. A retry that succeeds days later can look unauthorized if the customer never saw clear terms on their card on file, if the billing descriptor does not match your storefront name, or if they already cancelled. Much of what then looks like fraud is friendly fraud: a real customer disputing a charge they do not recognize or no longer want, which ends as a chargeback instead of a retry.
Disclose price, frequency, retry policy, and cancellation terms at signup, send a notice before the final retry, log every retry with its decline code, and sync every cancellation to billing immediately. Chargeflow's guide to preventing chargebacks on subscription renewals covers the full checklist. Stripe's dispute categories show where each failure lands:
| What the Customer Says | Dunning Failure Behind It | Visa and Mastercard Code | Evidence That Helps |
|---|---|---|---|
| "I cancelled" | Charge collected after cancellation, or a cancellation that never reached billing | Visa 13.2 Canceled Recurring; Mastercard 4841 | Signup page with recurring terms and cancellation path, proof the subscription was still active, any refund already issued |
| "I do not recognize this charge" | Weak consent capture, descriptor mismatch, or a surprise retry | Visa 10.4 Other Fraud, Card Absent; Mastercard 4837 or 4863 | Timestamped consent record, matching descriptor, earlier successful charges on the same card |
| "I was charged twice" | A retry that looks like a second capture | Visa 12.6.1 Duplicate Processing; Mastercard 4834 | Retry log showing one captured charge and failed attempts that were never captured |
Our guide to recurring billing chargebacks covers the full reason-code playbook, and subscription chargebacks covers the program-level view.
Best Dunning Strategies to Reduce Customer Churn
These strategies cut failed-payment churn and, done well, reduce the disputes that follow it:
- Match the first message to the decline type. Soft declines such as insufficient funds often clear on their own, so retry before messaging. Hard declines, expired cards, and authentication failures cannot be fixed by a retry, so message the customer right away.
- Keep the tone calm and the next step clear. An aggressive first message about a missed payment can cost you the customer. Say a retry is coming, and link straight to a payment-update page that shows exactly what to do.
- Automate and personalize. Consistently timed automated messages recover more revenue with less staff time than manual chasing, and using the customer's name and account history keeps a one-time miss from reading like a pattern of defaults.
- Offer multiple payment options. Letting customers pay with a card, digital wallet, or ACH signals flexibility instead of a punitive collections process.
How to Choose Dunning Management Software
Dunning management software ranges from the retry settings inside your billing platform to dedicated recovery tools. Compare options on how they handle the failure, not on feature counts:
| Criterion | What to Check | Why It Matters |
|---|---|---|
| Decline-aware retries | Does it read decline and advice codes, or follow a fixed calendar? | Retrying hard declines wastes attempts and can trigger network fees. |
| Network retry limits | Are attempts capped per card inside Visa and Mastercard limits? | Excess retries are fined by the networks. |
| Card update coverage | Which countries and card brands receive automatic updates? | Fixes expired cards before the customer is contacted. |
| Messaging control | Channels, timing, templates, sender domain, and whether a notice can precede the final retry | Clear notice reduces surprise-charge disputes. |
| Access rules | Configurable grace period and end state: cancel, unpaid, past due, or pause | Controls revenue risk and win-back options. |
| Reporting | Recovery rate, retry success rate, and authorization rate at renewal | You cannot tune what you do not measure. |
| Dispute handoff | Cancellations synced to billing and retry and consent logs you can export | Supplies evidence for disputes that dunning cannot prevent. |
No dunning tool contests a dispute once it is filed. That is the layer the last section adds.
How to Measure Dunning: Recovery Rate and Dispute Rate
Watch two numbers together every week: dunning recovery rate (the share of failed charges recovered through retries and reminders) and dispute rate (disputes as a share of transactions). To size the opportunity, take 5,000 subscribers at $40 a month with a 2% monthly failure rate: that is 100 failed charges and $4,000 of billings at risk each month, and every 10 points of recovery rate returns $400 of it.
Add two diagnostics to find where recovery leaks: retry success rate by decline type, and authorization rate at renewal compared with first purchase. A wide gap between them points to stale saved credentials rather than customer intent. If recovery climbs while disputes climb too, retries are succeeding on charges customers did not expect, which is a consent and notice problem, not a dunning setting.
Keep the dispute rate under network limits: Visa's Visa Acquirer Monitoring Program rates a merchant Excessive at a 1.5% ratio (effective April 2026), and Mastercard runs its own chargeback monitoring programs.
Where Dunning Stops and Chargeflow Starts
Dunning alone recovers technical declines. It was never built to fight a dispute, so pair it with prevention and evidence layers, each with a clear owner:
| Stage | Layer | Typical Owner |
|---|---|---|
| 1. Recover the decline | Smart dunning: decline-aware retries, automatic card updates, and pre-billing reminders | Finance / RevOps |
| 2. Deflect the dispute | Real-time chargeback prevention alerts resolve flagged transactions with a fast refund before they post; Chargeflow Alerts deflects up to 90% of chargebacks, with refunds within 24 hours | Customer Support / Ops |
| 3. Recover the rest | Chargeflow Automation assembles evidence and fights every remaining chargeback, backed by a 4X ROI guarantee | Finance |
Fraud checks belong in the same stack, not only at signup: see our ecommerce fraud prevention guide, and note that Chargeflow Prevent scans orders after checkout and before fulfillment. Chargeflow integrates with Stripe, Shopify, and PayPal, among 100+ integrations.
Frequently Asked Questions
What is dunning management?
Dunning management is the automated process of retrying failed recurring payments and messaging customers to fix billing issues, using a sequence of reminders that escalate from gentle to urgent. To "dun" someone is to repeatedly ask them for payment, so dunning is the automated version of that. It reduces involuntary churn caused by expired cards, insufficient funds, or outdated billing details.
What is the dunning process and how does it work?
The dunning process starts when a charge fails. The system classifies the decline, retries soft declines on a schedule, sends reminders that escalate from gentle to urgent, tries to refresh the card automatically, and ends either in recovery or in an end state such as cancel, unpaid, or pause when the retry window closes.
How is a failed payment different from a chargeback?
A failed payment is a technical decline that never charges the customer, and dunning fixes it through retries. A chargeback is a dispute over a charge that did succeed, filed by the customer or their bank, and it requires evidence rather than a retry to resolve.
How many times should you retry a failed payment?
Stripe's recommended default is 8 tries within 2 weeks, and its card guidance warns that extra retries can raise declines. Card networks set ceilings: Visa allows up to 15 reattempts per card in 30 days for Category 2, 3 and 4 declines (fee from the 16th) and none on Category 1 hard declines, and Mastercard allows 10 in 24 hours and 35 in 30 days. Never retry hard declines; ask the customer for a new payment method instead.
What is dunning management software?
Dunning management software automates retries, card updates, and customer messages for failed recurring payments. It can be a module in your billing platform or a standalone tool. Look for decline-aware retries, card update coverage, control over message timing, configurable grace periods, and recovery reporting.
What is the difference between dunning and collections?
Dunning is the automated, retention-focused sequence that recovers a failed or overdue payment while the customer is still active. Collections starts later, when an account stays unpaid, and relies on manual follow-up, payment plans, or third-party recovery. Dunning aims to keep the customer; collections aims to recover the debt.
Does good dunning management reduce chargebacks?
Indirectly, yes. Dunning reduces the failed-payment volume that can turn into confused or surprise-charge disputes, especially when paired with clear retry disclosure and accurate billing descriptors. It does not address disputes from customers who recognize the charge but want it reversed anyway, which require prevention alerts and evidence.
Put failed-payment recovery and dispute handling on autopilot instead of chasing each one by hand. Start for free.
Chargebacks?
No longer your problem.
Recover 4x more chargebacks and prevent up to 90% of incoming ones, powered by AI and a global network of 20,000 merchants.
.png)
.webp)