Dunning management: how to recover failed subscription payments

Dunning management is the process of recovering subscription payments that fail, by retrying the charge on a schedule, notifying the customer and deciding what happens to their access if the payment stays unpaid. A good dunning process recovers a large share of failed payments automatically, without your team chasing anyone by hand.

Below is a practical framework: why payments fail, how to design retries, what to say to customers and how to handle debit orders, which work differently from cards.

Why subscription payments fail

Most failed renewals are not customers trying to avoid paying. They are ordinary problems:

• Insufficient funds at the moment of the charge, often timing relative to payday.
• Expired or replaced cards, for example after a card is lost or reissued.
• Bank or issuer declines for fraud checks, limits or technical reasons.
• Closed accounts or changed bank details for debit orders.
• Disputed debit orders, where the account holder reverses a collection.

The first three are often temporary, which is why retrying works. The last two need the customer to act. Our guide to card declined reasons goes through decline types in more detail.

The three parts of dunning management

1. Retries

Retrying a failed card charge a few days later often succeeds, because the customer has been paid, has raised their limit or has unblocked the card. A retry schedule should:

• Space attempts out over days, not minutes.
• Avoid retrying hard declines (such as a reported stolen card) that will never succeed.
• Consider paydays. In South Africa, many people are paid around the 25th of the month or on the last working day, so a retry just after that can be more successful than one on the 20th.
• Stop after a fixed number of attempts.

2. Communication

Every failed attempt should trigger a clear message. Customers can only fix what they know about.

3. Consequences

You need a written policy on what happens while the account is past due: full access during a grace period, then limited access or suspension, then cancellation.

A sample 21-day dunning schedule

This is an illustrative starting point for a monthly card subscription. Adjust the timings for your customers.

On every successful retry, send a receipt and stop the sequence immediately.

Writing dunning emails that get results

Good dunning emails are short, specific and easy to act on.

• Subject line: plain and factual, such as "Payment for your Growth plan didn't go through".
• What happened: the amount, the plan and the date, for example R799.00 on 1 August.
• One action: a button to update the payment method or pay the invoice now. The link should work without the customer remembering a password.
• Tone: assume good faith. "This happens sometimes" works better than threatening language.
• Support: a way to reply or reach a person.

Avoid putting full card numbers or bank details in email. Mentioning the last four digits of the card is enough.

Example first email

Subject: Your payment of R799.00 didn't go through

Hi Thandi, we tried to collect R799.00 for your Growth plan on 1 August, but the payment was declined by your bank. You still have full access. To keep things running, please update your card or pay the invoice using the link below. We'll try again automatically on 4 August.

Dunning for debit orders

Debit orders work differently from card retries, so treat them separately.

• Unpaids arrive later. You learn that a collection failed when the unpaid comes back from the bank, not instantly as with a card decline.
• Re-presenting has rules. You can resubmit an unpaid collection, but how often and when is governed by your debit order provider's rules and your mandate. Check with your provider before re-presenting.
• Reversals are different from unpaids. A customer disputing a debit order is a customer-service conversation, not something to retry blindly.
• Consider a fallback. Offering a pay-now link by card or instant EFT for the missed amount often resolves the issue faster than waiting for the next batch.

See how debit orders work in South Africa for the underlying process.

Measuring your dunning process

Track these monthly:

• Failure rate: failed renewals as a share of all renewal attempts.
• Recovery rate: failed renewals that were eventually paid.
• Recovery by step: which retry or email recovered the payment.
• Time to recovery: average days from failure to payment.
• Involuntary churn: subscriptions cancelled because payment was never recovered.

Worked example

In a month you attempt 1,000 renewals. 80 fail. Over the dunning period, 52 are recovered and 28 are cancelled.

• Failure rate: 80 ÷ 1,000 = 8%.
• Recovery rate: 52 ÷ 80 = 65%.
• Involuntary churn: 28 subscriptions, or 2.8% of the base you tried to renew.

Improving the recovery rate from 65% to 75% would save eight more subscriptions every month. Our article on how to reduce involuntary churn covers the preventive side.

Common mistakes

• Retrying too fast. Several attempts in one day rarely help and can trigger issuer fraud rules.
• Silence. Retrying without telling the customer means they only find out when access stops.
• Cutting access on day one. Instant suspension punishes loyal customers for a bank problem.
• No end point. Subscriptions that stay "past due" forever distort your MRR and your receivables.
• Ignoring the debit order side. Cards and debit orders need different rules.

How CentraPoint helps

CentraPoint's subscriptions include automatic dunning retries and past-due handling, whether a subscription is collected by saved card token, debit order or invoice. Email templates are editable, so your reminders sound like you, and can be sent from your own SMTP server. For Netcash debit orders, unpaids can be re-presented, and statement import matches collections and unpaids to the right invoices. Customers can pay outstanding invoices from the self-service portal. The subscriptions docs explain the set-up.

Frequently asked questions

What is dunning management?

Dunning management is the process of recovering failed recurring payments: retrying the charge, notifying the customer and managing their access until the payment is made or the subscription is cancelled.

How many times should I retry a failed payment?

Three or four retries spread over two to three weeks is a common starting point. Stop earlier for hard declines such as stolen or closed cards, and test different timings against your own recovery data.

Should I suspend access as soon as a payment fails?

Usually not. Most failures are temporary, so a grace period with full or limited access keeps goodwill while you retry. Suspend only after several failed attempts and clear warnings.

Is dunning different for debit orders?

Yes. Debit order failures come back as unpaids after the collection date, and re-presenting is governed by your provider's rules. Pair re-presentation with a pay-now link so the customer can settle the amount another way.