← All articles

Dunning for Memberships: Recover Failed Payments

Dunning for Memberships: Recover Failed Payments

Member updating payment details on her phone

Dunning is the automated process that chases a failed membership payment until it either succeeds or you stop trying. It combines smart retries, a short sequence of messages, and a grace period that keeps the member’s access alive while the problem gets fixed. Done well, it brings back revenue from people who never meant to leave.

This guide is for creators who run a paid community, coaching membership or recurring program. It covers the retry schedule, what to write, how long to wait before cutting access, and the legal wrinkle that matters if you sell to members in Europe.

Money-plug
Build a Membership That Can Scale
Money Plug Lab helps creators build and launch paid digital products, including membership communities, through a revenue-share partnership.
Explore creator partnerships

TL;DR

  • Involuntary churn, where a payment fails and the member leaves without choosing to, accounts for 20% to 40% of all subscription churn.
  • Use smart retries instead of a fixed rule. Stripe’s recommended default is 8 retries within 2 weeks, and custom policies can run up to 2 months.
  • Write different messages for different decline reasons, and put a one-click card update link in every one.
  • Warn members before their card expires, and keep access on during a grace period.
  • If you sell to EU members, design automatic cancellations around the 14-day withdrawal right.

Table of Contents

Why failed payments are a hidden leak in your membership

When a member cancels on purpose, you get a signal: a survey answer, a message, a complaint. When a card fails, you get nothing. The member usually doesn’t know it happened. Stripe’s guide to failed payments describes involuntary churn as silent, because the customer didn’t intend to cancel and may never notice.

The scale is real. One benchmark report puts the average loss at 9.1% of monthly recurring revenue for subscription businesses. Another analysis calls 2% to 4% of subscribers the industry standard for involuntary churn and anything under 1% of MRR per month healthy. These figures come from SaaS and subscription businesses, not creator communities specifically, so treat them as a yardstick, not a promise.

For a creator, the math is simple. Say you have 1,000 members paying a monthly fee. If 3% of payments fail each month and you do nothing, you lose 30 members a month to a bug in the banking system, not to a bad product. Recovering even half of them is cheaper than winning 15 new members through ads.

Thirty failed payments and fifteen recovered members

Why payments fail (and why it changes your response)

Not every failure is the same, and the response should differ.

  • Soft declines are temporary: insufficient funds, a daily limit, a bank timeout. Many resolve on their own if you try again at a better moment.
  • Hard declines are permanent for that card: a closed account, a lost or stolen card, an expired number. Retrying wastes attempts. Stripe notes it doesn’t retry when the issuer returns a hard decline code.

That split is the core of good dunning. One analysis of creator-style communication says the most common mistake is sending the same generic “your card failed” email for every scenario, and that segmenting by decline reason lifts conversion. A soft decline needs patience and a light touch. A hard decline needs a fast, direct request for a new card.

Step 1: Set up smart retries

The first layer is technical, and it is mostly configuration, not writing.

Smart retry systems use machine learning to pick the moment a card is most likely to go through. Stripe’s Smart Retries use time-dependent signals to choose when to retry instead of following a rigid calendar. The gap in results is large: basic static rules such as three tries over seven days typically recover 5% to 10% of failed payments, while AI-optimized systems can recover up to 40%.

Practical settings:

  1. Turn on smart retries if your payment processor offers them.
  2. Start from the processor’s default window. Stripe’s default is 8 attempts in 2 weeks. Extend toward the 2-month limit only if your members tend to be paid monthly or irregularly.
  3. Treat annual members differently. Stripe’s automation examples show how to grant longer grace periods to annual subscribers, based on billing period, invoice amount or customer segment. Someone who paid a large annual fee deserves more patience than a member on a small monthly plan.
  4. Stop retrying hard declines and move straight to asking for a new card.

If you collect through bank debits in Europe, check how your processor handles them. SEPA debits support automatic billing for subscriptions when the original mandate covered recurring payments, but refunds and disputes work differently from cards.

Step 2: Warn members before the card fails

The cheapest failed payment is the one that never happens. Pre-dunning means contacting members before a card expires or a renewal is due. Paddle’s guidance on churn describes pre-dunning notifications as alerts sent before a card expires that can prevent involuntary churn entirely.

A simple version:

  • 30 days before expiry: a short note asking the member to update their card.
  • 7 days before: a reminder with the same link.
  • Renewal day: nothing, if the card is fine.

Keep the tone helpful, not alarming. “Your card ending in 4242 expires next month. Update it in 30 seconds so your access doesn’t pause” does the job.

Step 3: Write a dunning sequence people actually open

The best-supported advice is to be specific and make the fix effortless. Stripe’s failed payment guide says the most effective tool is a personalized message that explains why the payment failed and gives a direct, one-click link to update the payment method.

Here is a sequence you can adapt.

Timing Channel Purpose What to say
Day 0 (failure) Email Inform, no pressure Payment didn’t go through, here is the reason if known, update link, access continues
Day 3 Email + in-app banner Gentle reminder Same link, remind them what they get inside
Day 7 SMS or messaging app (with consent) Switch channel Short text with the link
Day 12 Email Deadline Access pauses on a specific date unless updated
Day 15 to 21 Email Final notice Access paused, one click to restore everything

A few writing rules:

  • Lead with the fix. The update link goes in the first lines, not the last.
  • Use the member’s name and plan. Generic mass emails get ignored.
  • Never blame. “Looks like your bank declined the payment” beats “You failed to pay.”
  • Make the cost of waiting concrete. Name what they lose: the next live call, the program library, the community chat.

Use more than one channel

Email alone often gets ignored. One analysis of subscription recovery notes that modern systems mix email, SMS and in-app notifications and adjust timing and channel based on how each subscriber has engaged in the past. For a creator, this fits naturally: a member who lives in your community app will see an in-app banner faster than an email sitting in a promotions tab. Only text members who have agreed to receive messages.

Step 4: Design a grace period that builds trust

The moment you cut access is the moment frustration starts. A grace period lets members keep access while they sort out the payment. Paddle’s guidance notes that grace periods foster trust rather than irritation.

How to choose the length:

  • Monthly, low-priced memberships: 7 to 14 days is a reasonable starting point to test.
  • Annual or high-ticket programs: longer, because the relationship is worth more and the member likely has a real reason for the failure.
  • Hard decline with no reply: shorten the window once you’ve sent the new-card request twice.

An alternative to cutting everything: pause premium features first (new content, live sessions) while leaving the community readable. Members see what they’re missing and feel the nudge without being locked out.

Step 5: Stay compliant if you sell to Europe

Many Balkan creators have audiences in the EU and the diaspora in Germany, Austria and Switzerland, so the rules matter. Note that the following describes EU rules, not a global standard, and Switzerland is not covered by it.

Under Directive 2011/83/EU, consumers generally have 14 calendar days to withdraw from an online service contract, counted from the day the agreement is made. If the seller did not tell them about this right, the period is longer. Digital content can be an exception when the buyer gives explicit consent to start immediately and acknowledges losing the right, and that disclosure should be clear at checkout. A separate summary explains that withdrawal and cancellation are two different rights: withdrawal ends the contract within 14 days with a full refund, while cancellation ends an ongoing subscription.

What this means for dunning:

  • Put the withdrawal terms and the consent checkbox at checkout, in plain language.
  • If your workflow automatically cancels access after a failed payment, check that it doesn’t conflict with a member’s rights in their country. Rules differ by country, so for a large EU audience get advice from a consumer-law professional there before you launch.
  • Keep records of consent and of every message you send.

Step 6: Track the numbers that matter

You can’t improve what you don’t measure. Track these monthly:

  • Involuntary churn rate: members lost to failed payments divided by total members. The benchmark above says under 1% of MRR per month is healthy.
  • Recovery rate: failed payments eventually collected divided by failed payments. Basic rules sit around 5% to 10% by one estimate. Another report says well-designed dunning can recover 30% to 50%. Your own number matters more than either.
  • Recovery by decline reason: if hard declines recover poorly, improve the new-card request.
  • Time to recover: if most recoveries happen in the first three days, tighten the early emails. If many arrive on day 10, your later messages are doing the work.

Change one thing at a time, such as the subject line or the grace period length, and give each test a full billing cycle.

Our perspective: dunning is a communication problem, not a plugin

We work with creators across the Balkans and the diaspora who are launching their first paid programs, communities and memberships. The pattern we see is that creators spend weeks on the product and the launch, then treat billing as an afterthought. That is backwards. A launch brings in members, and a weak payment setup quietly takes a slice of them back.

Our view, built from handling payment infrastructure as part of launches:

  • Set it up before the launch, not after. Retries, card-update links and email templates should exist on day one, when the first renewals are still weeks away.
  • Treat a failed payment as a service moment. The member is still a fan. Speak to them like one, in your voice and in their language, whether that is Bosnian, Serbian, Croatian, German or English.
  • Price and payment terms shape churn. A fair price and a clear plan reduce voluntary cancellations, and easier ways to pay reduce failed ones. We cover both sides in our guides on membership pricing and churn testing and payment plan options.
  • Don’t over-automate the relationship. Automation handles the retries. A personal message from you to a high-value member who has gone quiet often wins them back faster than a fourth reminder.

— Money

Launching a membership and want the payment side handled?

If you’re a creator with an engaged audience and no paid product yet, we can build it with you. Money Plug Lab works on a pure revenue share basis with zero upfront cost to the creator, and handles audience research, product architecture, pricing, sales copy, launch campaigns and payment infrastructure. See how it works on the Money Plug Lab site.

A practical checklist before you go live

  1. Smart retries switched on, hard declines excluded from retries.
  2. Pre-expiry emails at 30 and 7 days.
  3. Five-step dunning sequence with a one-click update link in each message.
  4. At least one channel besides email, used only with consent.
  5. A grace period you’ve chosen on purpose, longer for annual plans.
  6. EU withdrawal wording and consent at checkout, if relevant.
  7. A monthly dashboard for involuntary churn and recovery rate.

FAQ

What is dunning in a membership business?

Dunning is the set of automated steps you take when a recurring payment fails: retrying the charge, messaging the member, and eventually pausing or ending access. The goal is to recover the payment without damaging the relationship. Retry rules, message timing and grace periods are all part of it.

How many times should I retry a failed membership payment?

There is no universal number. Stripe’s recommended default is 8 retries within 2 weeks, and custom schedules can stretch to 2 months. Don’t retry hard declines, since the card won’t work, and ask for a new one instead.

How long should the grace period be?

A common starting point for monthly plans is one to two weeks, with longer periods for annual or high-priced memberships. Test the length against your recovery rate. Keeping access on during the window tends to build trust rather than annoyance.

How do I reduce involuntary churn without annoying members?

Send a heads-up before cards expire, explain why the payment failed, and give a one-click link to fix it. Space reminders out and add a second channel instead of sending more emails. Personal, specific messages work better than generic ones.

Sources