Failed payment recovery: what actually moves the number

A meaningful slice of subscription churn is not customers deciding to leave. It is cards failing while the customer fully intends to pay. The industry calls it involuntary churn, and the difference between handling it well and badly is measured in whole points of revenue.

Why payments fail

Most failures land in a few buckets:

• Expired or replaced cards. The card on file simply is not valid anymore. Common after banks reissue cards in bulk.
• Insufficient funds. Often temporary. The same charge can succeed three days later, which is why retries work at all.
• Soft declines. The bank says no this time, for reasons that may not repeat: risk checks, velocity limits, a bank outage.
• Hard declines. The bank says this card will never work: stolen, closed, invalid. Retrying a hard decline is pointless and, at volume, hurts your standing with the card networks.

Your recovery process should treat these differently, because they are different problems.

Retry, but with a schedule and a reason

Blind daily retries are the naive approach and they underperform. What works better:

• Space the retries out. Insufficient funds resolves around paydays and deposits, not four hours later. Spacing attempts over one to two weeks beats hammering the card in the first 48 hours.
• Stop on hard declines. When the decline code says the card is dead, move straight to asking for a new card instead of burning attempts.
• Keep a record of every decision. When a customer asks why their card was charged on a Thursday, you want the timeline: attempt, outcome, decline reason, next scheduled step. This also keeps you honest about what your own process is doing.

yRecurring ships retry schedules with smart timing, classifies declines so hard failures stop the retry train early, and records a decision trace on every step of a recovery campaign, so the whole story is on one timeline.

The email matters more than the retry

Retries recover the temporary failures. Everything else needs the customer to act, which means the recovery email is doing the heavy lifting. The good ones do three jobs:

1. Say what happened plainly. The payment for their subscription did not go through, here is the amount, nothing is broken yet.
2. One link, straight to the fix. A page where they can update the card and settle the open amount in one sitting, without logging in through three screens. yRecurring gives every recovery campaign a hosted page for exactly this.
3. A humane schedule. A note when it fails, a reminder a few days later, a final notice before anything is suspended. More than that reads as harassment and trains customers to ignore you.

Fix cards before they fail

The cheapest failed payment is the one that never happens. Cards carry expiry dates, which means you can see a chunk of next month's failures coming. yRecurring watches for cards expiring ahead of a renewal and notifies the customer before the charge, not after it fails. Catching even a fraction of those turns recovery work into a non event.

Decide the ending in advance

Some payments will not be recovered. Decide, as policy, what happens at the end of a campaign: keep the subscription and alert a human, write the invoice off, or cancel the subscription. Any of the three can be right depending on your product and margins. What is not right is having no policy and letting unpaid subscriptions drift. In yRecurring the terminal action is part of the dunning configuration, so the ending is a decision you made once, not an accident per customer.

Measure one number

Recovery rate: of the invoices that entered recovery, how many ended up paid. Track it monthly. It tells you whether schedule changes and email edits are working, and it is the number that justifies the whole effort. If you have never measured it, the first month's number is usually the whole argument for fixing the process.

Payment recovery is included on every yRecurring plan, retry traces and hosted recovery pages included. The trial is free to poke at: set up a retry schedule, fail a test payment, and watch the timeline record every decision.