Not every customer who stops paying wants to leave. Some of them are happy with your product, fully intend to keep using it and don't even know their last payment failed.
A card expired. A bank declined the charge. The account didn't have enough balance on the billing date. The mandate limit was too low for this month's invoice. Each of these ends the same way: an unpaid invoice, a paused account and eventually a lost customer.
This is involuntary churn and for many subscription businesses it's one of the easiest revenue leaks to fix. This guide explains why payments fail, how to prevent failures in the first place, and how to recover the ones that still slip through.
Churn is the rate at which customers stop paying you. It comes in two forms and they need very different fixes.
| Voluntary churn | Involuntary churn |
|---|---|
| What happensThe customer decides to cancel | What happensThe customer's payment fails and the subscription lapses |
| Common causesPrice, missing features, poor fit, a competitor | Common causesExpired cards, insufficient funds, bank declines, mandate issues |
| Customer intentWants to leave | Customer intentUsually wants to stay |
| How to fix itImprove the product, pricing and support | How to fix itBetter payment methods, retries and reminders |
Voluntary churn takes months of product and service work to improve. Involuntary churn can often be cut significantly with changes to your billing process alone. That makes it one of the fastest wins available to any subscription business.
Most failed payments come from a small set of causes. Knowing which one you're dealing with tells you how to respond.
| Cause | What's happening | Best response |
|---|---|---|
| Insufficient funds | The account or card limit can't cover the charge on the billing day | Retry after a few days, ideally after common salary dates |
| Expired or replaced card | The saved card is no longer valid | Ask the customer to update their payment method |
| Mandate limit exceeded | The invoice is higher than the maximum amount the customer approved | Ask the customer to approve a higher limit, or collect the difference manually |
| Bank or issuer decline | The bank blocked the charge, often as a fraud precaution | Retry later, or ask the customer to approve it with their bank |
| Cancelled mandate | The customer revoked their UPI AutoPay or e-mandate | Contact the customer to set up a new one |
| Technical or network error | A gateway, bank server, or network issue interrupted the payment | Retry automatically within a few hours |
Some failures are temporary and fix themselves with a well-timed retry. Others, like an expired card or a cancelled mandate, need the customer to take action. Good recovery treats the two differently.
The cheapest failed payment to recover is the one that never fails. These steps stop many failures before the billing date.
Send pre-billing reminders: Notify customers a few days before each charge, especially for annual renewals or larger amounts. It gives them time to top up their account or update their card.
Warn about expiring cards early: Contact customers 30 days before their saved card expires and ask them to update it.
Offer multiple payment methods: Support UPI AutoPay, cards, net banking e-mandates, and bank transfers. If one method fails, the customer has a backup.
Set mandate limits with room to grow: If your invoice can vary, for example with usage or seats, ask customers to approve a maximum amount above their usual bill.
Choose billing dates wisely: Billing shortly after typical salary dates, or letting customers pick their own billing day, reduces insufficient-funds failures.
Make updating payment details easy: A single link in an email that takes the customer straight to a secure payment page removes most of the friction.
Collect a backup payment method: For high-value B2B accounts, a secondary method can be charged if the primary one fails.
When a payment does fail, a structured recovery process brings most of that revenue back. It has two parts: automatic retries and a dunning sequence.
Smart retries: Don't retry a failed payment every hour. Space retries out over several days and match them to the reason for failure. A technical error can be retried within hours. Insufficient funds are better retried a few days later. An expired card shouldn't be retried at all until the customer updates it.
Dunning: Dunning is the series of messages you send to let customers know a payment failed and help them fix it. A typical sequence looks like this:
| When | Message | Tone |
|---|---|---|
| Day 0 | Your payment didn't go through. Here's a link to pay or update your details. | Friendly, informative |
| Day 3 | Reminder: your invoice is still unpaid. | Helpful |
| Day 7 | Your account is at risk. Please update your payment to avoid interruption. | Clear, direct |
| Day 14 | Final notice: your subscription will be paused on a specific date. | Firm but polite |
| After pause | Your account is paused. Pay now to restore access instantly. | Welcoming |
A few tips make dunning more effective:
Recurring payments in India work differently from many other markets, because RBI rules require customer consent and notification for automatic debits. Building your billing around these rules prevents a large share of failures.
E-mandates are required: To charge a card, UPI account, or bank account automatically, the customer must first register an e-mandate, approving the merchant, the frequency and a maximum amount.
Pre-debit notifications: Customers must be notified before each automatic debit, at least 24 hours in advance, with the option to cancel. Your billing system and payment gateway should handle this for you.
Limits on debits without extra authentication: Recurring debits up to a set limit (₹15,000 for most categories) can go through automatically. Above that, the customer usually has to approve each debit, such as by entering a UPI PIN or OTP. If your invoices exceed this limit, plan for manual approval or a different payment method.
UPI AutoPay: UPI AutoPay lets customers set up recurring payments from any UPI app. It's widely used, quick to set up and a strong option for small and mid-sized subscriptions.
Card tokenisation: Saved cards are now stored as tokens rather than card numbers. When a customer's card is reissued, the token may need to be refreshed, so prompt customers to update their details when a card changes.
These limits and rules are updated from time to time, so check the latest RBI and NPCI guidelines and confirm details with your payment gateway.
You can't reduce what you don't measure. Track these four numbers every month.
| Metric | How to calculate it | What it tells you |
|---|---|---|
| Payment failure rate | Failed payments ÷ total payment attempts | How often charges fail on the first try |
| Recovery rate | Recovered payments ÷ failed payments | How well your retries and dunning work |
| Involuntary churn rate | Customers lost to failed payments ÷ total customers at the start of the month | How much churn your billing process causes |
| Revenue recovered | Total value of failed payments later collected | The money your recovery process brings back |
For example, if 60 of 1,000 payments fail in a month and you recover 42 of them, your failure rate is 6% and your recovery rate is 70%.
Watch the trend over time. A rising failure rate often points to a payment method or gateway issue. A falling recovery rate usually means your dunning messages need work.
Mocha QuickBill is built to keep recurring revenue flowing, so fewer customers slip away because of a payment problem.
Automated payment reminders: Send reminders before the due date, on the due date and after a payment fails.
Online payment links: Every invoice includes a link customers can use to pay instantly by UPI, card, or net banking.
Automatic invoice generation: Invoices go out on time, every cycle, so no customer is billed late.
Customer management: See each customer's payment history, overdue invoices and outstanding balance in one place.
Reports on dues and collections: Track outstanding amounts and collections to spot problems early.
With QuickBill, your billing process works as hard to keep customers as your product does.
Involuntary churn is revenue you lose from customers who never meant to leave. With reminders before billing, multiple payment options, smart retries and a friendly dunning sequence, you can recover most of it.
Fixing failed payments is one of the fastest ways to grow recurring revenue, without winning a single new customer.
Ready to stop losing customers to failed payments? Try Mocha QuickBill free and automate your reminders, payment links, and follow-ups.
Involuntary churn is when a customer's subscription ends because a payment fails, not because they chose to cancel.
Dunning is the process of contacting customers about failed or overdue payments and helping them pay, usually through a series of reminders.
Three to four retries spread over one to two weeks works for most businesses. Match the timing to the reason for the failure.
No. Give customers a grace period with reminders, then pause the account before cancelling it. Most failed payments can be recovered.
Common reasons include insufficient balance, a revoked mandate, an amount above the approved limit, or a temporary bank or network issue.
Yes. Pre-billing reminders, card expiry alerts, better retry timing, and clear dunning emails all work with your existing setup.