Resources

Pre-Dunning: Stop Failures Before They Happen

Dunning starts after a payment fails. Pre-dunning starts before it — in the days and weeks when the failure is still preventable. A card that is about to expire, an annual plan about to renew at a price the customer has forgotten, a bank that will want an extra authentication step: none of these have failed yet, and that is exactly why they are cheap to fix.

Pre-dunning will not save every subscription. What it does is shrink the pile of failures that were never really failures at all — the expired card nobody asked about, the renewal nobody expected — so your recovery effort goes to the cases that actually need it.

What pre-dunning is, and what it is not

Pre-dunning is any customer contact, silent refresh, or account check that happens before a scheduled charge is attempted and declined. It has three jobs: warn the customer about a problem you can already see, remind them about a charge they may have forgotten, and quietly refresh payment details that have changed behind the scenes.

It is not a replacement for dunning. Dunning — the retries and messages after a decline — handles the failures pre-dunning cannot prevent. Think of the two as sequential, not competing: pre-dunning reduces how many payments enter recovery; dunning recovers the ones that enter anyway. An operator who only runs dunning works the hardest version of every saveable case, because the first message the customer gets is about a problem instead of a heads-up.

It is also not nagging. Every pre-dunning touch has to earn its place by pointing at something specific and fixable: the card ending in a stated set of digits expires this month, here is one link to update it. A generic "check your payment details" email with nothing wrong just teaches customers to ignore you.

The first job: card-expiry warnings

An expired card is the most predictable failure in subscription billing. You can see the expiry date months in advance, the customer usually has a replacement card already, and the fix takes under a minute.

Timing matters more than copy here. A workable pattern looks like this:

• First warning, well before expiry. Send it while the current card still works, framed as housekeeping, not urgency. The customer can update in their own time, and most will, because there is no pressure and no embarrassment attached.
• Second warning, close to expiry. If the card on file still shows the same expiry date as the month turns, send a shorter, more direct note: the next charge will fail unless the card is updated, and here is the link.
• Final check, just before the charge. If nothing has changed by the last days before renewal, one last brief reminder is justified. After this point the failure belongs to dunning, and the messaging should switch to that sequence instead of repeating the warning.

Two discipline points. First, stop warning the moment the card is updated — nothing erodes trust faster than an expiry email sent to someone who fixed it last week. Second, the update has to land on a secure, branded card-update page that works well on a phone, never a request to reply with card details.

Before you write the warning yourself, give the silent route its chance. Card networks and issuers can refresh many replaced cards automatically, and our guide to card updater services explains how that enrollment works and which cards it can and cannot refresh. The warning email is for the cards the silent route could not fix — which is why the two belong in the same system, checked in order.

The second job: pre-renewal notices for annual plans

Annual plans fail differently. The card may be perfectly valid, but the customer has not thought about your product's price in eleven months. The charge lands as a surprise, and a surprised customer disputes, refunds, or calls their bank.

A pre-renewal notice fixes the surprise, not the card. Send it early enough that the customer can make a real decision: update a card, talk to whoever approves spend on their side, or cancel cleanly if they no longer want the plan. A cancellation made calmly before renewal is a better outcome than a forced save followed by a refund and a chargeback — you keep the relationship and the door stays open.

Keep the notice plain. Name the product, the amount that will be charged, and the date it will be charged, and link to the same secure update page you use everywhere else. Do not bury the price or dress the notice up as a newsletter. The point is informed consent for a large, infrequent charge.

Monthly plans rarely need this treatment at full strength; the charge is recent memory and the amount is familiar. Save the formal notice for annual and other long-cycle plans, where the gap between charges is long enough for cards, budgets, and minds to change.

The third job: authentication heads-ups

Some charges need the customer to confirm they are really the customer — an extra authentication step with their bank before the payment can complete. When that requirement arrives unannounced at renewal time, it looks to the customer like a broken checkout or a suspicious charge, and many will simply abandon it.

You cannot complete that step for the customer, and you should not try to script it in detail, because the exact screens belong to their bank. What pre-dunning can do is set the expectation in general terms: a renewal is coming, their bank may ask them to approve it, and approving it is normal and expected.

Keep this generic and honest. Name the upcoming charge and the date, say an approval request from their bank is possible, and give them one place to go if something goes wrong. Do not imitate the bank's language, ask for any code or credential, or link to anything that looks like a bank login.

How pre-dunning and dunning fit together

The handoff is the part most operators get wrong. Pre-dunning ends the moment a charge is attempted. If it succeeds, the warnings stop. If it fails, the failure enters dunning with its decline code attached, and everything the customer hears from that point should be written for a payment that has already failed — not a warmed-up repeat of the warning.

That distinction shapes the copy. Pre-dunning language is prospective: "will be charged," "expires this month," "update before your renewal." Dunning language is factual: "did not go through," "is on hold," "update to keep your plan active." Mixing the two confuses customers and makes both sequences easier to ignore. Our guide to dunning emails that work covers the post-failure side of that line in detail.

The two also share plumbing: the secure card-update page, the sender domain, and the brand voice should be identical on both sides of the line. And both sit inside the wider discipline of preventing avoidable failures, which our guide to reducing failed payments works through tactic by tactic.

Where Swipe Again fits

To be precise about the boundary: Swipe Again is failed-payment recovery software for subscription businesses, not a separate pre-dunning product, and nothing here should be read as a pre-dunning feature claim. Pre-dunning is a practice you run with the tools in this guide — warnings, notices, and updater enrollment before the charge.

Where Swipe Again supports that practice is the destination every warning points to. Its branded dunning emails and branded card-update pages give the customer one secure, familiar place to fix a card — the same page and the same branding whether they arrived from an expiry warning before a failure or from a dunning email after one. The customer never sees the recovery provider's name on that page; they see yours.

And for the failures pre-dunning could not prevent, the recovery side is decline-code-aware: smart retries run up to 6 attempts over about 16 days, hard declines are never retried, and email and SMS work the sequence together. On connect, Swipe Again also runs a 90-day backfill over your existing backlog of failed payments, so the failures that predate the new routine get worked instead of written off. It connects to Stripe, Recharge, Seal Subscriptions, Skio, Loop Subscriptions, Chargebee, Recurly, Braintree, and Paddle, is priced at $179/mo flat ($1,799/yr) with no percentage of recovered revenue, and starts with a 14-day trial with connect in about 2 minutes. The guarantee is: Recover $179 in 30 days, guaranteed — or Swipe Again is free the next 30 days.

The bottom line

Pre-dunning is the cheapest recovery work you will ever do, because it happens before there is anything to recover. Warn about the expiring card while it still works, give annual customers a fair look at a charge they have forgotten, set expectations for a bank approval step, and let card updater services silently fix what they can. Whatever still fails, fails into a proper dunning sequence — with honest copy, one secure update page, and no repeated warnings pretending the failure has not happened yet.

Frequently asked questions

What is pre-dunning?

Pre-dunning is everything you do before a scheduled charge fails to prevent that failure: warning a customer that the card on file is about to expire, reminding an annual customer that a renewal is coming, setting expectations for a bank authentication step, and keeping card details refreshed through updater services. Dunning, by contrast, starts after a decline.

How early should a card-expiry warning go out?

Early enough that the customer can act without pressure, then again closer to expiry if the card on file has not changed, and once more just before the charge if needed. The exact days matter less than the discipline: each warning checks whether the card was already updated, and the warnings stop the moment it is.

Does pre-dunning replace dunning?

No. Pre-dunning prevents the predictable failures, such as expired cards and surprise annual renewals. It cannot prevent insufficient funds, lost cards, or bank blocks, so a full retry and outreach sequence after a failure is still necessary. The two are halves of one system, with the attempted charge as the line between them.

Should monthly subscribers get pre-renewal notices too?

Usually not at full strength. A monthly charge is recent and familiar, so a formal notice adds inbox noise without adding information. Expiry warnings still apply to monthly plans, because a card can expire in any month. Save formal pre-renewal notices for annual and other long-cycle plans, where the amount and the gap make the charge easy to forget.

What should a pre-dunning message never ask for?

It should never ask the customer to reply with card details, share a code or credential, or sign in through a link that imitates their bank. Every message should point to one secure, branded card-update page where the customer enters new details directly, and authentication steps should only ever be completed with the customer's own bank.

Related reading: Pre-dunning email templates