Your subscribers did not cancel. Their cards expired, got reissued after a breach, or hit a limit on renewal day, and your billing system marked them as gone. That is involuntary churn, and it leaks revenue from customers who still wanted what you sell.
The fix is not just "retry the card." Done carelessly, retries break card network rules, raise decline rates, and make your processor nervous. Done well, dunning recovers revenue and keeps your merchant account healthy at the same time.
What involuntary churn actually is
Voluntary churn is a decision. A customer clicks cancel. Involuntary churn is an accident. The payment fails and nobody fixes it before access ends.
The common causes are mundane: expired cards, replaced card numbers, insufficient funds, issuer fraud filters, and banks that block recurring charges they do not recognize. None of these mean the customer is unhappy. They mean your billing process failed to keep pace with their wallet.
Most failed renewals are not lost customers. They are lost card numbers, and lost card numbers can be found.
Why processors care about how you handle failed payments
This is the part most dunning guides skip. Your processor sees every declined authorization you send, not just the approvals. A billing system that hammers dead cards produces a decline ratio that looks like card testing or a broken integration.
Card networks also track retries directly. Visa and Mastercard both have rules about which declines may be retried and how often. Breaking them can generate network fees that your acquirer passes to you, and repeated problems invite a closer review of your account.
Subscription merchants already carry extra scrutiny because recurring billing produces disputes when customers forget they signed up. Our separate guide on reducing chargebacks in subscription businesses covers that side. This post is about the payments that never went through in the first place.
Step one: stop the failure before it happens
Account updater services
Visa Account Updater and Mastercard Automatic Billing Updater let participating merchants receive updated card details when an issuer reissues a card. New expiration dates, replaced numbers, and closure notices flow back to you so the stored credential stays current.
Updaters are accessed through your processor or gateway, not signed up for directly by most merchants. Issuer participation varies, so they will not catch every change. Ask your provider whether updater is included, how often it runs, and whether it checks cards before your billing date or only after a decline.
Network tokens
Many gateways now store network tokens instead of raw card numbers. A network token is tied to the card account rather than the plastic, and it can stay valid when the physical card is replaced. Where available, tokens reduce the number of renewals that fail simply because a card was reissued.
Pre-dunning emails
Pre-dunning means contacting customers before the charge fails. The most useful trigger is an upcoming card expiration. A short note a few weeks ahead that says "your card ends this month, update it here" prevents a decline instead of chasing one.
Pre-dunning also includes renewal reminders. A clear notice before an annual renewal or a trial conversion reduces surprise charges, which reduces both refund requests and disputes. Visa has specific rules for free trials and introductory offers, so confirm your renewal notices meet current network requirements with your processor.
Step two: read the decline before you retry
Every declined authorization comes back with a response code. Some say "try again later." Others say "never try again." Treating them the same is the most common and most expensive dunning mistake.
Visa's decline categories
Visa groups decline responses into categories. Category 1 means the issuer will never approve the transaction, for example because the card is closed or reported lost or stolen. Merchants should not reattempt these at all.
Category 2 means the issuer cannot approve right now, such as insufficient funds or a temporary limit. The older Visa limit was 15 reattempts in 30 days. Checkout.com's current implementation guidance reports an increase to 20 from May 19, 2025, with separate counters for customer- and merchant-initiated transactions. Confirm the limit, region, and response-code treatment your processor applies before configuring retries. Exceeding the limits, or retrying Category 1 declines, can trigger fees.
Mastercard's merchant advice codes
Mastercard attaches merchant advice codes to many declines. Some point you to update the card details, some say try again later, and codes 03 and 21 mean do not try again. Mastercard monitors excessive authorization attempts on the same card and can assess fees when merchants retry too often or ignore do-not-retry signals.
The exact limits and fees can change, so build your retry logic on your processor's current guidance rather than a number you read once in a blog post, including this one.
Step three: retry smarter, not more often
A smart retry schedule uses the decline reason, the card type, and timing to pick the moments most likely to succeed. A fixed schedule of "retry every day for a week" ignores all of that.
- Hard declines: do not retry. Move straight to customer outreach and an account updater check.
- Insufficient funds: space retries out and consider timing them near common paydays rather than at random hours.
- Issuer unavailable or system errors: a quick retry later the same day often succeeds.
- Suspected fraud blocks: ask the customer to confirm the charge with their bank before retrying, since repeated attempts can deepen the block.
Cap total attempts well inside network limits. Fewer, better-timed retries usually recover more and generate less decline noise than a long string of blind attempts.
Mark recurring transactions correctly
Retries and renewals should be flagged as merchant-initiated, credential-on-file transactions, linked to the original customer-initiated payment. Correct flags tell the issuer this is an expected recurring charge, which can improve approvals and keeps you aligned with network stored-credential rules. Your gateway handles the flags, but you should confirm they are set.
Step four: dunning emails that people answer
When retries cannot fix the payment, the customer has to. Good dunning communication is short, specific, and easy to act on.
- Immediately after the first failure: say the payment did not go through, name the plan, and link to a secure page to update the card. No login maze.
- A few days later: a reminder with the date access will pause.
- Just before access ends: a final notice that is direct but not threatening.
- After access pauses: a win-back note that makes reactivation one click.
Use your normal brand name and a billing descriptor customers recognize. Confusing descriptors drive "I don't recognize this" disputes, and a recovered payment that turns into a chargeback is worse than no recovery.
Add a grace period
Cutting off access the instant a card fails punishes customers for their bank's mistakes. A short grace period with in-app notices gives people time to update details while they still value the product. Many subscribers fix their card only when they see a banner inside the product they use.
Make the update page effortless
Every extra step between the email and a working card costs you recoveries. Link straight to a secure, mobile-friendly page with the plan already identified. Offer the payment methods your customers actually use, including a second card or a bank payment where your setup supports it. If someone has to remember a password they created two years ago, many will simply give up.
Annual plans and high-value renewals need extra care
A failed monthly charge is a small problem repeated often. A failed annual renewal is a large problem that happens once, and it carries more risk on both sides.
Large charges are more likely to trip issuer fraud filters, especially when the customer has not seen that amount on their statement in a year. A reminder before the renewal date, sent with enough notice for the customer to update details or cancel, does a lot of work here. It reduces declines, and it reduces the "I forgot about this" disputes that hurt your ratios.
When an annual renewal fails, consider reaching out personally rather than relying on automated emails alone. Offering to split the charge or switch to monthly billing can save a customer who simply hit a limit.
Measure what you recover
Track recovery the way you track sales. Useful numbers include the share of renewals that fail on the first attempt, the share recovered by retries, the share recovered by customer updates, and the share lost. Watch your overall decline ratio as well, since your processor certainly does.
If recovered revenue rises while your decline ratio falls, your dunning program is working for you and for your bank. If both rise together, you are probably retrying too aggressively.
Where the merchant account fits in
Dunning tools only work when the account underneath them is stable. Mainstream processors sometimes freeze subscription merchants after a spike in declines or disputes, which turns a recovery problem into a cash-flow emergency. Our guide to why merchant accounts get frozen explains the triggers.
A provider that understands recurring billing models and their risk profile will ask about your retry logic, updater use, and cancellation flow during underwriting. That is a good sign. It means they expect to keep you, not just approve you. Software companies can also review our payment options for SaaS businesses.
Audit your renewal flow this week
Pull last month's failed renewals and sort them by decline code. You will likely find a group you should never have retried, a group an account updater would have caught, and a group that only needed a timely email. Each group has a different fix, and each one you fix is revenue you keep.
If your current processor treats every failed payment as a red flag, it may be time for an account built around how subscription businesses actually bill. Start your application with Karma Card Payments and we will review your billing setup with you.
Sources and timing
Last reviewed October 5, 2026. Network rules and legal requirements can change; confirm the rules that apply to your account and products.