Dunning Management Best Practices for Subscription Businesses
Dunning management is the process of recovering failed subscription payments and is a critical growth lever for recurring revenue businesses, essential for minimising involuntary churn and protecting revenue.
Merchant accounts, acquiring routes, and chargeback controls, matched to your risk profile.
Dunning management is the process of recovering failed subscription payments from customers. For any business built on recurring revenue, this process is not just an operational task, it is a critical growth lever. An effective dunning strategy minimises involuntary churn, protects revenue, and maintains positive customer relationships. Without it, even a successful acquisition funnel will leak customers and revenue at an unsustainable rate.
Understanding Why Subscription Payments Fail
Subscription payments fail for many reasons, broadly categorised as hard declines and soft declines. Hard declines are permanent and indicate a fundamental problem with the payment method. Soft declines are temporary and often resolvable with a retry.
Common causes of hard declines include:
- Invalid Card Number: The card number does not exist or has a typo.
- Stolen or Lost Card: The customer has reported their card as stolen or lost, and the issuer has blocked it.
- Closed Account: The bank account associated with the card has been closed.
- Invalid Expiry Date: The card's expiry date has passed.
Attempting to retry a hard-declined card is futile and can harm your standing with payment networks. These failures require direct customer intervention to update their payment details.
Soft declines, on the other hand, are often temporary issues:
- Insufficient Funds: The most common reason for a soft decline. The customer's account does not have enough money to cover the transaction at the time of the attempt.
- Do Not Honour: A generic decline from the issuing bank. The reason is not specified, but it can be due to their fraud filters, unusual spending patterns, or a temporary system issue.
- Transaction Not Allowed: The issuer has blocked the transaction, sometimes because the card type (e.g., a prepaid gift card) is not authorised for recurring payments.
- Processor Declined: The payment processor's own risk rules have flagged the transaction.
- Card Activity Limit Exceeded: The card has reached its single transaction limit or daily spending limit.
Analysing your decline codes is the first step in building a dunning strategy. Grouping failures into these categories helps you decide whether to automatically retry the payment or immediately contact the customer.
Building a Smart Payment Retry Strategy
Not all retries are created equal. A naive retry strategy, such as attempting the payment every day for a week, can be counterproductive. It can lead to higher processing costs and may even trigger acquirer penalties for excessive authorisation attempts. A smart retry strategy uses data to inform when and how to re-attempt a failed payment.
Your retry logic should be tailored to the specific decline code. For an "Insufficient Funds" decline, retrying makes sense. But when should you retry? Consider common paydays. Retrying a day or two after the 1st or 15th of the month might have a higher success rate. Some payment platforms can even use machine learning to predict the optimal time to retry a specific card based on historical data.
For a "Do Not Honour" decline, the approach should be different. An immediate retry is unlikely to succeed. It is better to wait 24 to 48 hours. Sometimes, the customer's bank just needs to see the initial attempt to whitelist future transactions from your business. If a second attempt fails, it may be time to contact the customer.
A sophisticated decline recovery system can automate this logic. Here is a sample retry schedule based on decline type:
| Decline Reason | Recommended Retry Schedule |
|---|---|
| Insufficient Funds | Retry in 3 days, then 5 days, then on the 1st of the next month. |
| Do Not Honour | Retry in 24 hours, then again in 72 hours. |
| Processor Declined | Retry immediately via a different acquirer if possible. |
| Activity Limit Exceeded | Retry after 24 hours. |
Using a platform with multi-acquirer processing capabilities can also enhance your retry strategy. If a transaction is declined by one acquirer, you can automatically re-route it through another. This is particularly effective for "Processor Declined" or generic technical failure codes, as the issue may lie with the initial processor's systems or risk rules, not the customer's card itself.
Proactive Measures: Card Updaters and Network Tokenisation
The best way to handle a failed payment is to prevent it from happening in the first place. Many declines occur simply because a customer's card has expired or been reissued. Relying on the customer to remember to update their details is a recipe for churn.
Automatic card updaters are a vital tool for subscription businesses. Services like Visa's Account Updater (VAU) and Mastercard's Automatic Billing Updater (ABU) allow merchants to receive updated card information directly from the card schemes. When a customer's card is reissued, the schemes automatically provide the new card number and expiry date to participating merchants, ensuring the next billing attempt succeeds.
This process is typically managed by your payment gateway or acquirer. Ensure your provider supports it. The impact on revenue retention can be significant, often reducing passive churn by several percentage points.
Network tokenisation is another powerful proactive tool. Instead of storing the raw 16-digit card number (the PAN), you store a network token provided by the card scheme. This token is specific to your merchant account and the customer's card. If the underlying card number changes, the token remains valid as the scheme links it to the new card details automatically. This provides the same benefit as card updaters but with added security and often higher approval rates, as issuers tend to view tokenised transactions more favourably.
Crafting Effective Dunning Emails and In-App Notifications
When automated retries fail, you need to contact the customer. The goal of this communication is to make it as easy as possible for them to update their payment information and resolve the issue. Your messaging should be clear, helpful, and aligned with your brand voice.
Email Communication
Your dunning email sequence should be carefully planned. Do not send a single, generic "payment failed" email and hope for the best. A typical sequence might look like this:
- Email 1 (Immediately after first failed retry): A soft notification. Let them know there was an issue and that you will try again. Do not immediately demand they update their card. The tone should be helpful, assuming a temporary glitch.
- Email 2 (After a second failed retry): A more direct request. Explain that the payment failed again and provide a clear, one-click link to a secure page where they can update their details. Reinforce the value of the subscription.
- Email 3 (Before subscription suspension): An urgent but polite notice. Inform them that their service will be suspended if the payment information is not updated. Remind them of what they will lose.
- Email 4 (After subscription suspension/cancellation): A final attempt to win them back. Confirm the cancellation and offer a simple way to reactivate their subscription.
Test your subject lines, email copy, and the design of your card update page. Small changes can have a big impact on recovery rates. Always send these emails from a recognisable address that customers trust.
In-App and SMS Notifications
Do not rely solely on email. If a customer is actively using your app or website, in-app notifications are often more effective. A persistent, non-intrusive banner at the top of the interface that says "Please update your payment information" with a link can be very effective. This catches the user when they are already engaged with your product.
For some business models, SMS can also be a powerful channel. A simple text message alerting a user to a payment failure can have high open and action rates, but you must have explicit consent (opt-in) to communicate with customers via SMS for this purpose.
Managing Grace Periods and Subscription Pauses
How long should you keep trying to collect payment before cancelling a subscription? This is the role of a grace period. During this time, the customer retains access to your service while you execute your dunning process. Cutting off access immediately after the first failed payment creates a poor customer experience and can lead to angry support tickets and voluntary churn.
The length of your grace period depends on your business model and customer base. For a B2B SaaS product with an annual contract, a 30-day grace period might be appropriate. For a monthly consumer subscription, a 7 to 14-day grace period is more common. The key is to balance the cost of providing the service for free against the opportunity to recover the customer.
Another customer-friendly option is to offer a subscription pause. Instead of forcing a cancellation, allow customers to pause their subscription for one to three months. This is an excellent alternative for customers facing temporary financial difficulty or who are travelling. It keeps them within your ecosystem and makes it much easier to reactivate them later, as their payment details are still on file.
Dunning Management and Payment Orchestration
Managing a sophisticated dunning process across multiple payment providers, regions, and payment methods can become complex. This is where a payment orchestration layer adds significant value. It centralises your dunning logic, allowing you to build and manage rules in one place, regardless of the underlying acquirer.
An orchestration platform can:
- Automate retry logic: Implement custom retry schedules based on decline codes, customer lifetime value, or subscription plan.
- Route retries intelligently: Automatically send a retry attempt to a different acquirer if the first one fails, a core function of smart routing.
- Centralise reporting: Get a unified view of decline reasons and recovery rates across all your payment service providers.
- Manage customer communications: Trigger emails, webhooks, or other notifications from a central rules engine.
By abstracting the dunning process away from individual PSPs, you gain flexibility and control. You can optimise your recovery workflow without being limited by the features of any single provider, ultimately recovering more revenue and reducing involuntary churn.
Frequently asked questions
What is dunning management?
Dunning management is the process businesses use to communicate with customers and attempt to collect payments after a recurring subscription payment has failed. The goal is to recover the owed revenue and prevent involuntary customer churn due to payment issues like expired cards or insufficient funds.
How do you create a payment retry strategy?
A smart payment retry strategy is based on the reason for the payment failure. For soft declines like "Insufficient Funds", retrying on likely paydays can be effective. For generic declines like "Do Not Honour", waiting 24-48 hours before the next attempt is better. Hard declines, such as a stolen card, should not be retried at all; instead, you should immediately ask the customer to provide a new payment method.
What are dunning emails?
Dunning emails are a sequence of automated messages sent to a customer after their subscription payment fails. The emails inform the customer of the issue, explain the consequences (like service suspension), and provide a simple, secure way for them to update their payment information. The tone and timing of these emails are critical for successfully recovering the customer.
How can I reduce involuntary churn from failed payments?
You can reduce involuntary churn by implementing a multi-faceted dunning strategy. This includes using proactive tools like automatic card updaters and network tokenisation to prevent failures, employing a smart retry logic based on decline codes, and sending a clear, helpful series of dunning emails and in-app notifications to prompt customers to update their payment details.
Does payment orchestration help with dunning?
Yes, a payment orchestration platform can significantly improve dunning management. It allows you to centralise your retry logic, automatically route failed payments to different acquirers for a higher chance of success, and get a unified view of your payment recovery performance across all your payment providers. This central control helps you build a more effective and adaptable dunning process.
What is a grace period in subscriptions?
A grace period is a set amount of time after a subscription payment fails during which the customer can still access the service. This gives the business time to execute its dunning process (retrying the card, sending emails) without creating a negative customer experience by immediately revoking access. The length of the grace period typically ranges from a few days to a month, depending on the business model.
