Dunning and Failed Payment Recovery: How the Process Works

Dunning is what you do between a failed payment and a lost customer. In a subscription business, most failed renewals come from customers who never decided to leave: the card expired, the account was short that day, the bank said no. A good dunning process gets those payments back without annoying anyone, and knows when to stop. This guide covers the whole process, from the retry rules to the emails and the end of the sequence. For supplement, skincare and other subscription brands, see By industry.

What is dunning?

Dunning is the process of collecting a payment that failed or is overdue, through a set sequence of retries and reminders. The word comes from the old English verb "to dun", to press someone for payment. It is used in two different contexts, and search results mix them up:

In subscriptions, dunning fights involuntary churn: customers lost because a payment failed, not because they canceled. Why renewals fail in the first place (decline codes, expired cards, insufficient funds) is covered in subscription payment failures, and the short definition is in the glossary entry on dunning. This guide picks up once the payment has failed, or is about to. Churn as a whole, voluntary and involuntary, is covered in our guide to subscription churn.

The dunning process, step by step

A complete dunning process has five stages. The first one happens before anything fails.

1. Pre-dunning. Warn the customer before a payment is likely to fail: card about to expire, trial ending, annual renewal coming up.
2. Failure notice. As soon as the renewal is declined, tell the customer and give them a link to fix it.
3. Retries and reminders. Retry the card on a schedule the card networks allow, and send reminders that get more specific over time.
4. Grace period. Decide how long the customer keeps access, or keeps receiving orders, while the payment is open.
5. Final outcome. If nothing works, apply the rule you chose in advance: pause, cancel, leave the balance open, or write it off.

Pre-dunning: stop failures before they happen

The cheapest failed payment is the one that never fails. Pre-dunning covers the messages and tools that run before the renewal date.

• Expiring card emails. Stripe, for example, can email the customer one month before the default card on file expires.2Stripe Docs, Automate customer emails
• Renewal reminders. A reminder a few days before the charge gives the customer time to switch cards or top up their account. Stripe lets you set how many days before the renewal it goes out.2Stripe Docs, Automate customer emails
• Automatic card updates. Card networks can pass new card details to your processor when a bank replaces a card. More on this, and on wallets, in the next section.
• Trial and promotion endings. For Visa cards this one isn't optional:

A customer who forgets a trial and gets charged doesn't become a dunning case. They become a dispute. The full set of Visa and legal rules for recurring billing is in our guide to negative option billing.

Expired and replaced cards: account updater, network tokens and wallets

A card that expired or was replaced is the most preventable failure in dunning: the customer still wants the product, and the bank would approve a valid card. Three mechanisms keep a stored card working.

Account updaters. Stripe works with the card networks and "automatically attempts to update saved card details whenever a customer receives a new card", for example after an expiry or a card reported lost or stolen. It depends on the issuer: support is wide for cards issued in the United States, "international support varies from country to country", and "it isn't possible to identify cards that support automatic updates".7Stripe Docs, How cards work (automatic card updates) See the glossary entry on the card account updater.

Network tokens. A processor token only means something to that processor. A network token is issued by the card network itself and replaces the card number in the payment, so a reissued card can keep working under the same token. How Visa and Mastercard tokens work, and where they're required, is in our guide to saved payment methods.

Wallets. A subscription started with Apple Pay adds a trap. By default, Apple Pay creates a Device Primary Account Number (DPAN) tied to one device. "If a customer replaces their device or removes the card from it, the DPAN might no longer work." That doesn't affect one-time payments, "but it can cause failures for future merchant-initiated transactions". The fix is an Apple Pay Merchant Token (MPAN), linked to the customer, the card and your business instead of the device.11Stripe Docs, Apple Pay merchant tokens, read November 3, 2026

How the wallet payment was taken matters as much. A wallet charge on a one-time cart may leave nothing to charge later. In Tagada's documentation, an Apple Pay or Google Pay payment through Stripe's Express Checkout is kept for renewals only when the cart has a subscription item; on a one-time cart, "nothing is kept: the instrument settles that order only". And the wallet's cryptogram "is single-use": later charges are merchant-initiated and carry the stored credential and the network transaction ID from the first payment.12Tagada Docs, Wallets (Apple Pay, Google Pay), read November 3, 2026

When the new card does arrive through the customer, the update should do the rest. In Tagada's customer portal, for example, the card set as default "also becomes the card of every live subscription", and a past-due subscription can be charged again right away with retryPayment.15Tagada Docs, Customer portal, read November 3, 2026 Whatever the tool, check both: a customer with three subscriptions shouldn't have to update the card three times.

How often to retry a failed payment

Retries do most of the recovery work, because many declines are temporary: the money arrives the next day, the bank's system comes back up. But you can't retry as often as you like. Visa sorts every decline code into four categories, each with a retry limit:6Visa Core Rules and Visa Product and Service Rules, April 18, 2026

Visa also forbids changing data in the request to get a different answer on the retry: the acquirer, merchant country, MCC, POS fields and e-commerce indicator must stay as they were.6Visa Core Rules and Visa Product and Service Rules, April 18, 2026 A Category 1 decline needs a new card from the customer, so for those codes dunning is only messages. The difference between the two kinds of declines is in the glossary entry on the hard decline.

How a billing tool applies this. In Stripe Billing, Smart Retries picks the retry times with a model that uses signals such as the best time to pay, and you choose a number of tries within 1 week, 2 weeks, 3 weeks, 1 month or 2 months. The recommended default is 8 tries within 2 weeks. If you build a custom schedule instead, you get up to three retries, each a set number of days after the previous one.1Stripe Docs, Automate payment retries (Smart Retries)

Stripe doesn't execute retries after hard declines such as lost_card, stolen_card, pickup_card, incorrect_number, transaction_not_allowed or authentication_required. The scheduled attempts still count, but a charge only runs once the customer adds a new payment method.1Stripe Docs, Automate payment retries (Smart Retries)

Bank debits follow their own, much tighter limits. Stripe only retries them for insufficient funds, and only if you turn it on:1Stripe Docs, Automate payment retries (Smart Retries)

For monthly plans, keep the whole sequence shorter than the billing cycle. Recurly's documentation suggests limiting monthly dunning to 27 days to avoid overlapping the next bill in February.9Recurly Docs, Dunning campaigns For the decline codes behind each category, see how to improve your payment acceptance rate.

Smart retries or a fixed schedule

There are two ways to time retries. A fixed schedule waits a set delay after each failure. A smart retry picks each attempt's time from data: the decline code, past approvals, the day of the week. Both have to stay inside the same network cap.

There is no published, independent test that settles which recovers more, and vendors measure recovery differently. Two points hold either way. A spaced schedule beats repeated attempts on the same day. And a smart retry is only as good as the rules around it: Tagada describes its smart retry, available on request, as using "failure codes (e.g. 'insufficient funds'), velocity limits, and even payroll-day heuristics to pick the optimal retry time".13Tagada Docs, Subscriptions and rebilling, read November 3, 2026 More on how these models work in the glossary entry on smart retries.

Manual retries count too. A support agent who clicks "retry now", or a script that charges every past-due subscription, sends real authorization requests on the same card. They belong to the same count. Some systems enforce it: TagadaPay's Payments API can refuse a "try now" request on a renewal cycle with the reason try_refused_by_law, for "scheme limits, minimum wait".14TagadaPay Payments API, Ask for a try now (renewal cycles), read November 3, 2026

Retrying on another processor

If you bill renewals through more than one processor, a failed renewal can be retried through another one: a cascade to the next processor on your list, a weighted split, or a backup processor. That's useful against processor-side failures, such as a processor that is down or times out. It is not a way to retry a decline from the issuer, and it doesn't change the card network rules.

Source: Visa Core Rules and Visa Product and Service Rules, April 18, 2026.6Visa Core Rules and Visa Product and Service Rules, April 18, 2026

The rule is written for the card, not for the processor: a second acquirer doesn't reset the count. Keep one attempt counter per card, shared by every processor, and make sure your cascade excludes every issuer decline. Visa's rule on not changing request data also covers the acquiring identifier, so a renewal the issuer declined is retried on the route that sent it, not on another acquirer. How a cascade works and where it goes wrong is in the glossary entry on cascading payments, and declines in general in our guide to declined payments.

Dunning emails and SMS: what to send and when

Retries work without the customer. Messages are for everything retries can't fix: an expired or replaced card, a closed account, a payment that needs authentication. Stripe can send an email after each failed payment, with a link to a page where the customer updates their payment method and pays the open invoice.2Stripe Docs, Automate customer emails

The sequence below is a starting point for a monthly physical subscription. Adjust the days to your own retry schedule.

What every message needs:

• Who you are and what failed. Brand name in the sender and subject, the amount, the order or plan.
• One action. A single link to a page where the card can be updated and the open invoice paid. No login if you can avoid it.
• A date. When the next retry runs, and when access or shipments stop.
• A plain reason, or none. "Your bank declined the payment" is enough. Never echo a fraud-related reason such as a lost or stolen card.
• An exit. A link to pause or cancel. A customer who wanted to leave and can't will dispute the charge instead.

Send texts only to customers who agreed to receive them, and keep the update link valid for the whole sequence. In Stripe, the hosted update link stops working when the subscription becomes canceled or unpaid, or when the current renewal period ends.2Stripe Docs, Automate customer emails

Three dunning email templates

Short, plain and with one link. Replace the brackets, keep the structure. These are illustrative texts, not tested benchmarks.

Whatever tool sends them, check what each template can contain before writing it. A failed-payment email without a card-update link is just a notice. In Tagada's email list, for example, the upcoming-renewal notice has a customer portal link variable, while the failed-payment template lists only the plan name and amount.16Tagada Docs, Emails, read November 3, 2026 The rest of the transactional emails around a payment are covered in payment confirmation email.

Grace period: what happens to access

The grace period is the time between the failed payment and the moment you cut access or stop shipping. There is no rule on its length: it's a business choice. What the network rules do fix is the retry window above, and your grace period shouldn't be longer than the time you're still trying to collect.

Billing tools model this with subscription statuses. Here is how Stripe defines them:3Stripe Docs, How subscriptions work (subscription statuses)

How to set the grace period by product type:

• Physical subscriptions (boxes, refills). Don't ship an unpaid order. Hold it, say so in the message, and ship the day the payment clears.
• Digital access. Keep access during the retry window: the customer who logs in and sees a "payment failed" banner is the one most likely to fix it.
• Annual plans. The amount is larger and the card is older. Start pre-dunning earlier and allow a longer grace period. Stripe's automation recipes include a custom dunning flow for annual subscribers.10Stripe Docs, Revenue recovery

What to do when dunning ends: pause, cancel or write off

When the last retry fails, something has to happen to the subscription and to the unpaid balance. Pick the rule before you need it. Stripe offers four outcomes after the final retry:1Stripe Docs, Automate payment retries (Smart Retries)

The pause option has conditions in Stripe: only eligible subscriptions on flexible billing mode can pause, and if Stripe can't pause after the final attempt, it cancels instead.4Stripe Docs, Pause subscriptions after payment failure Canceling, by default, also stops automatic collection of all outstanding invoices.3Stripe Docs, How subscriptions work (subscription statuses)

Writing off. The open balance doesn't disappear with the subscription. Most tools let you mark the invoice uncollectible or void it. Recurly, by default, marks the invoice as failed at the end of the dunning cycle and writes it off as bad debt.9Recurly Docs, Dunning campaigns For a single missed box, chasing the debt after the subscription ends usually costs more than it brings back.

Stopping dunning early. Sometimes you want to end the process before it runs its course: the customer opened a dispute, agreed a payment plan, or called support. In Chargebee, a manually stopped invoice is marked Not Paid, the subscription stays active, and dunning can't be restarted for that invoice. When retries simply run out, the status is "Exhausted" and the invoice follows your dunning settings.8Chargebee Docs, Difference between dunning status stopped and exhausted A customer who disputes a renewal is telling you they want out: stop dunning and handle the dispute. Subscription disputes are covered in our guide to chargeback prevention.

How to measure dunning recovery

A dunning process you don't measure drifts. Stripe's revenue recovery dashboard uses four core indicators, all calculated on subscription payment volume:5Stripe Docs, Revenue recovery analytics

Two breakdowns make these numbers useful. Recovered volume by method splits retries, emails and other methods (API charges, third-party emails, in-app flows), so you see which part of the sequence earns its place. Failed volume by decline reason shows the top decline codes, which tells you whether to work on pre-dunning (expired cards) or on retry timing (insufficient funds).5Stripe Docs, Revenue recovery analytics

There is no official benchmark for recovery rates. Card networks don't publish one, and billing vendors each count retries, first payments and trial conversions differently. Track your own rate over time, split by decline reason, plan length and first versus later renewals. To turn recovered payments into churn and revenue figures, see how to calculate churn rate.

Common dunning mistakes

Dunning for B2B invoices, in short

If you also sell on invoice, to retailers or wholesale buyers, dunning looks different. There's no card to retry. The process is a series of reminders that get firmer as the invoice ages: a friendly note before the due date, a reminder shortly after, a firmer notice citing the terms, a formal letter about late fees or a credit hold, and a final demand before an agency or a write-off. Pause reminders while a dispute about the invoice is open. The metric that matters is days sales outstanding (DSO): how long it takes, on average, to turn an invoice into cash.

By industry

How Tagada helps

Subscriptions that keep charging

• A retry schedule out of the box: a declined renewal moves to past_due and retries after 24, 48, 96, 168 and 168 hours, then cancels; smart retry, based on failure codes and payroll days, is available on request (subscriptions and rebilling).
• Network rules enforced: a "try now" on a renewal can be refused with try_refused_by_law (scheme limits, minimum wait) (ask for a try now).
• Charge right after a card update: trigger a rebill on an active or past_due subscription instead of waiting for the next retry, one by one or for every past-due subscription (manual rebill).
• A customer portal that fixes the payment: the customer updates the card, retries the past-due payment with retryPayment, and the new default card applies to every live subscription; pause and cancel are there too (customer portal).
• Subscription emails: subscription_past_due goes out when a renewal is declined. subscription_rebill_upcoming goes out 3 days before the next billing cycle and carries a customer portal link (emails). That reminder is not the 7-day Visa notice before a trial or promotion ends: plan that one on its own.
• Wallet renewals that work: Apple Pay and Google Pay on a cart with a subscription keep a payment method for renewals; later charges are merchant-initiated (wallets).
• TagadaPay underneath: "Your PCI-tokenized cards, your customer profiles, your subscription data, all portable." Switch processors without re-onboarding customers, so running subscriptions keep charging when you change processor.
• Onboarding in one KYC: most merchants are live on TagadaPay in under 24 hours. "If you sell something real, we will get you paid."
• 24/7 human support on Slack Connect: "The person who reviews your application has a name, and so does the one who picks up when something breaks."

It runs standalone, on Shopify, on WooCommerce or headless. Plans are on the pricing page. Tagada follows Visa and Mastercard rules and the laws that apply to payments.

Apply today · Go live in under 24 hours

Start free

Whatever tool you use, the method doesn't change: warn before the renewal, retry within the network limits, send one clear link, and decide in advance how the sequence ends. If you're comparing tools, our guide to dunning management software lists what to check, and the payment side of renewals is in subscription payment processing.