How to Reduce Subscription Churn from Failed Payments

Cardflo Editorial··9 min read

Subscription businesses frequently lose customers due to failed payments, a phenomenon known as involuntary churn, which can be significantly reduced through a systematic approach combining issuer data, smart retries and

Apply for a Merchant Account with Cardflo

Merchant accounts, acquiring routes, and chargeback controls, matched to your risk profile.

Apply now
How to Reduce Subscription Churn from Failed Payments editorial cover image

Subscription businesses lose a significant portion of their customers not to active cancellation, but to failed payments. This is involuntary churn, and it quietly erodes your customer base and recurring revenue. While some payment failures are inevitable, many are recoverable with a systematic approach that combines issuer data, intelligent retries, and proactive customer communication. A well-designed payment recovery strategy can reclaim a substantial percentage of these otherwise lost subscribers.

Analysing the Causes of Involuntary Churn

Failed payments are not a single problem. They stem from a variety of issues, broadly categorised as either hard declines or soft declines. Understanding the difference is critical to building an effective recovery strategy.

Hard declines are permanent failures. Issuing banks use them for definitive rejections where retrying the same transaction is pointless. Common reasons include:

  • Lost or stolen card (Decline Code 04, 07, 41, 43): The card has been reported compromised. The issuer will not authorise any transactions on this number.
  • Invalid card number (Decline Code 14): The card number entered fails the Luhn check or does not exist in the issuer's system. This is common with data entry errors.
  • Closed account: The customer has closed the bank account associated with the card.

Retrying a hard decline on the same payment instrument is a waste of time and can harm your standing with acquirers. The only solution is to secure a new payment method from the customer.

Soft declines are temporary failures. The issuer is indicating a potential issue that might be resolved on a subsequent attempt. These are the primary targets for automated recovery. Reasons include:

  • Insufficient funds (Decline Code 51): The most common reason for a soft decline. The customer's account does not have enough money to cover the transaction at that moment.
  • Do not honour (Decline Code 05): A generic decline from the issuer. It can mean anything from suspected fraud to unusual spending patterns. It is often temporary.
  • Transaction not permitted (Decline Code 57): The card is not configured for this type of transaction, such as a recurring e-commerce payment.
  • Expired card (Decline Code 54): The card's expiry date has passed. While technically a permanent state, automatic card updaters can resolve this without customer intervention.
  • System errors (Decline Code 91, 96): Technical issues at the issuer, processor, or card scheme level that prevent the transaction from being authorised.

A detailed analysis of your decline codes is the first step. If you see a high proportion of soft declines like ‘Insufficient Funds’, your retry strategy will be paramount. If generic codes like ‘Do Not Honour’ are prevalent, your focus might shift towards routing and acquirer performance.

Building a Smarter Dunning and Retry Strategy

Dunning is the process of communicating with customers to collect overdue payments. For subscriptions, this process should be automated, intelligent, and respectful of the customer relationship. A brute-force approach of retrying a failed payment every day is inefficient and can lead to acquirer penalties.

An effective retry strategy, often called "smart dunning", uses data to inform when and how to re-attempt a charge. This involves more than just a fixed schedule. A sophisticated system will consider:

  • Decline Code Logic: The system should not retry hard declines. For soft declines, the logic can vary. An 'Insufficient Funds' decline is best retried a few days later, perhaps aligning with common paydays (e.g., the 1st or 15th of the month). A 'Do Not Honour' might be retried sooner, perhaps in a few hours.
  • Time of Day: Some issuers have system maintenance windows, often overnight in their local time zone. Retrying transactions during peak processing hours for the relevant region can yield better results.
  • Card Scheme Rules: Visa and Mastercard have specific rules about how many times a merchant can retry a declined transaction within a certain period. Exceeding these limits can result in fines. Visa's Stored Credential Transaction framework and Mastercard's Merchant Advice Codes (MACs) provide data to guide these retries.
  • Acquirer Performance: Sometimes a decline is specific to the acquiring bank's relationship with a particular BIN range or issuer. An intelligent system can automatically retry a failed transaction through a different acquirer in your network. This is a core benefit of multi-acquirer processing.

The goal is to maximise authorisation rates without irritating customers or acquirers. Most subscription platforms should see a recovery rate of 10-20% from automated retries alone, before any customer communication begins.

Proactive Card Lifecycle Management

A significant driver of involuntary churn is outdated card information. Cards expire, get lost, or are reissued. Relying on customers to manually update their details is unreliable. Proactive card lifecycle management tools can automate this process, preventing payment failures before they happen.

The two main tools for this are Account Updater services and Network Tokenisation.

Account Updater Services

Visa Account Updater (VAU) and Mastercard Automatic Billing Updater (ABU) are services that acquiring banks and processors provide. They allow merchants to query the card schemes for updated details on cards stored in their vault. Before a subscription renewal is due, your system can check if the card on file is still valid. If the issuer has issued a new card number or expiry date, the service returns the updated details, which you can then use for the upcoming transaction.

This process is invisible to the customer and prevents failures due to expired cards. It is a fundamental tool for any business that stores cards for recurring billing.

Network Tokenisation

While often discussed in the context of security, network tokens from schemes like Visa and Mastercard are also powerful retention tools. When a card is tokenised, the raw card number (PAN) is replaced with a unique token that is specific to your merchant account. This token is tied to the underlying card account, not the physical plastic.

If the customer's card is lost, stolen, or expires, the issuer updates the credential linked to the network token on the scheme's backend. The token itself does not change. This means your recurring billing continues uninterrupted, without you needing to run an Account Updater batch or ask the customer for new details. Network tokens provide a persistent payment credential that survives most card lifecycle events, significantly reducing declines from outdated card data.

Strategic Customer Communication (Dunning Emails)

When automated retries and card updates fail, you must contact the customer. This communication, often called dunning, needs to be carefully managed to avoid coming across as aggressive or spammy. The goal is to make it easy for the customer to update their payment details and continue their subscription.

Best practices for dunning emails include:

  • Clear Subject Lines: Be direct. "Action Required: Your [Service] Subscription Payment" is better than a vague "An issue with your account".
  • Simple, Direct Copy: Explain what happened ("Your recent payment could not be processed") and what the customer needs to do ("Please update your payment details to continue enjoying your service"). Avoid blaming the customer.
  • A Deep Link to the Payment Update Page: Do not just send them to your homepage. Provide a secure, single-click link that takes them directly to a pre-authenticated page where they can enter new card details. The fewer steps, the higher the conversion rate.
  • In-App Notifications: For services with a logged-in experience (like SaaS platforms or mobile apps), in-app banners or modals are highly effective. They catch the user when they are already engaged with your product.
  • Grace Periods: Do not cut off service immediately after the first failed payment. Offer a grace period of a few days to a week. This shows goodwill and gives your automated recovery and dunning emails time to work. Let the customer know their access is at risk to create urgency.

The timing and frequency of these messages matter. A typical flow might be: an email after the first failure, another after a second failed retry a few days later, and a final "cancellation pending" notice before the end of the grace period.

Using Payment Orchestration to Fight Churn

Managing all these moving parts, especially across multiple regions and payment processors, is complex. This is where a payment orchestration layer becomes invaluable for subscription businesses.

An orchestration platform centralises your payment operations, allowing you to implement a comprehensive decline recovery strategy. It can:

  • Route transactions intelligently: If a payment fails with a soft decline at one acquirer, the platform can automatically retry it via another. This is particularly effective for mitigating processor-specific issues or optimising for issuer preferences. Cardflo's decline recovery tools are built around this principle.
  • Consolidate decline data: Instead of pulling reports from multiple gateways, you get a unified view of all your decline codes, helping you spot trends and fine-tune your retry logic.
  • Manage dunning logic: A central platform can manage the entire dunning lifecycle, from triggering smart retries to sending customer emails, based on a unified set of rules.
  • Integrate multiple recovery tools: Orchestration connects Account Updater services and network tokenisation from various providers, ensuring you have the best tools working for you across all your payment methods and regions.

By abstracting the complexity of individual payment service providers, an orchestration platform empowers you to focus on building the most effective strategy to retain the customers you have worked so hard to acquire.

Frequently asked questions

What is involuntary churn?

Involuntary churn, also known as passive churn, is when a customer's subscription is cancelled because their recurring payment fails. This is different from voluntary churn, where a customer actively chooses to cancel. Common causes include expired cards, insufficient funds, or other card issuer declines.

What is a good payment failure rate for a subscription business?

A typical payment failure rate for recurring transactions is between 5% and 15%. The exact number depends heavily on your customer base, price point, and industry. A healthy, well-optimised business should aim for a failure rate in the single digits after recovery efforts.

How do smart retries work?

Smart retries use data from the initial failed transaction to decide when and if to try again. Instead of a fixed schedule, a smart retry system analyses the decline code. For example, it will not retry a hard decline like "Stolen Card", but it might retry a soft decline like "Insufficient Funds" a few days later, perhaps on a date when people are commonly paid.

What is the difference between Account Updater and Network Tokenisation?

Account Updater is a service where you proactively ask the card schemes (Visa, Mastercard) for updated details for cards you have on file. Network Tokenisation replaces the customer's card number with a special token that automatically stays in sync with the underlying account, meaning you do not need to ask for updates when a card expires or is reissued. Network tokens are a more modern and seamless solution.

How can multiple acquirers help reduce failed payments?

Sometimes a payment fails not because of the customer's card, but because of an issue with the acquiring bank processing the transaction. This could be a technical problem or a poor relationship with the customer's issuing bank. By using a multi-acquirer setup, you can automatically retry the failed transaction through a different acquirer, which may have a higher chance of success.

Can I stop involuntary churn completely?

No, it is not possible to eliminate involuntary churn entirely. Some customers will always have insufficient funds, and some cards will be cancelled without a replacement. The goal is not elimination but reduction. A comprehensive strategy combining smart retries, card updaters, and customer communication can significantly reduce involuntary churn and recover a large portion of at-risk revenue.

Apply with Cardflo

Ready to improve your payments setup?

Tell us about your business. We'll match you with the right acquiring partners and the right route, typically inside a week.