A failed renewal payment is the quietest way to lose a subscriber. Nobody clicks cancel. Nobody writes in. The card is declined, the order doesn't ship, and unless something happens next the subscription simply ends. These are customers who wanted to stay, which makes them the easiest ones to keep.
This guide explains why subscription payments fail, which failures are worth retrying, how to set up retries and messages, what to do when the retries run out, and how to measure what you recover. It replaces our older post on dunning for DTC brands.
Why subscription payments fail
A renewal charge is made without the customer at checkout, using a card they saved weeks or months ago. A lot can change in that time:
- The card expired: The most predictable failure. You know the expiry date in advance.
- Not enough money: The balance or credit limit was too low on the day of the charge.
- The bank declined it: A generic decline, often with no detail. Sometimes the bank is unsure about a charge the customer didn't make in person.
- Suspected fraud: The bank's fraud checks flagged the charge.
- The bank wants the customer to confirm: Some banks, especially in Europe, ask the cardholder to approve the payment (for example with 3-D Secure). The renewal waits until they do.
- The card was replaced: Lost, stolen or reissued cards get a new number, and the old one stops working.
- The payment method was removed: The customer deleted a saved card or wallet, or the billing agreement ended.
- Something on the store side: A payment provider that isn't turned on, a setting your team needs to check, or an item out of stock. These aren't the customer's fault and shouldn't be messaged as if they were.
Soft declines and hard declines
Every decline comes back with a code from the bank or payment processor (a decline code). The codes fall into two broad groups, and they need different handling:
| Type | Examples | Retry? | What the customer needs to do |
|---|---|---|---|
| Soft decline | Insufficient funds, a temporary bank or network error, a generic "do not honor" | Yes, a few days later | Often nothing; sometimes add funds |
| Hard decline | Expired card, invalid card number, lost or stolen card, closed account | No, it will fail again | Update the card |
| Customer action needed | Bank asks the cardholder to confirm the payment | Not until they confirm | Approve the payment |
| Store-side | Payment provider not enabled, item out of stock | After you fix it | Nothing; your team acts |
The point of sorting is to stop wasting retries on cards that can't succeed and to send the right message. Telling a subscriber to "update your card" when the real problem was an out-of-stock item, or a bank outage, damages trust.
Set a retry schedule
For soft declines, try again. A sensible starting schedule is three or four retries spread over one to three weeks, with a few days between each. Space them out: a balance that was low on Monday may be fine by Friday, while retrying every hour just piles up declines.
- Spread the tries: More time between later retries gives the subscriber time to act on your messages.
- Think about timing: Some brands retry around common paydays such as the 1st and 15th. Test whether it helps your customers.
- Don't retry hard declines: An expired or closed card won't work no matter how often you try. Ask for a new card instead.
- Respect the limits: Card networks set rules on how often a declined card can be retried, and your payment processor applies them. A shorter list of well-spaced tries is better than many fast ones.
- Decide the next-order date: After a recovery, should the next charge count from the original date or from the day the payment went through? Pick one and keep it consistent.
Tell the subscriber, in plain words
Retries recover some payments on their own. Messages recover many more, because the subscriber can fix what the retry can't. Each stage gets its own short message, by email and by text for subscribers who agreed to texts:
| When | Message | Tone |
|---|---|---|
| First decline | "Your order didn't go through. Update your card in one tap and we'll ship it." | Friendly, no blame |
| After each retry | "We tried again and it still didn't work. Here's the link." | Helpful |
| Before the last try | "This is our last try on [date]. Update your card to keep your subscription." | Clear |
| Final notice | What happened (paused, skipped, canceled or kept open) and how to restart | Plain and kind |
| Recovered | "You're all set. Your order is on its way." | Thank them |
- Link straight to the fix: One tap to update the payment method. No password, no hunting through an account page.
- Remind them what's at stake: Their subscriber price, unused credits or a reward coming up make updating the card feel worth a minute.
- Warn before the card expires: A week or so before a renewal, tell subscribers whose card is expiring. This is the cheapest failure to prevent.
- Handle bank confirmations: When a bank asks the subscriber to approve a payment, send them the step to approve it right away.
- Let them reply: Some subscribers will text back a question. Answer it, by a person or an AI agent that can see their subscription.
Decide what happens when the tries run out
When the last retry fails, something has to happen. There are four common choices:
- Keep it open: The subscription stays active and the next renewal tries again. Good for loyal subscribers; risky if failures pile up.
- Skip this order: Move on to the next scheduled order. The subscriber misses one delivery but stays subscribed.
- Pause: Stop billing until the subscriber updates their card. Easy to restart, and it doesn't count as a cancellation.
- Cancel: End the subscription. Clean, but you lose the subscriber unless a win-back brings them back.
Whatever you choose, the final notice should say exactly what happened and how to restart in one click. Subscriptions that end this way are a great audience for a win-back campaign, because they never chose to leave.
When to involve a person
- A high-value or long-time subscriber whose payment keeps failing.
- A fraud flag on a customer you know well.
- The same store-side error across many renewals, such as a payment provider setting.
- A subscriber who replied confused or upset.
- Payments that keep failing for one product, which may point to a stock or setup problem.
Backup cards, account updaters and network tokens
You'll see three other recovery ideas in payment industry guides. They're useful to understand, and whether you can use them depends on your payment processor and billing setup:
- Backup payment methods: The customer saves a second card, and the billing system charges it if the first one fails.
- Card account updaters: Services run by card networks that pass new card numbers and expiry dates to merchants when a bank reissues a card.
- Network tokens: A token from the card network stands in for the card number and can stay valid when the physical card is replaced.
Ask your payment processor which of these it supports for subscription renewals on your store. Retries, clear reminders and expiry warnings help whatever your processor offers.
Measure your recovery rate
Recovery rate = failed renewal payments that were later paid ÷ all failed renewal payments, for the same period. Example: 200 renewals fail in a month and 130 are paid after a retry or a card update. Your recovery rate is 65%.
- Recovered revenue: The value of the payments you got back.
- Recovery by decline type: Soft declines should recover far more often than hard ones. If they don't, check your retry schedule.
- Recovery by message: Which reminder led to the card update. Test the wording.
- Time to recover: How many days from first decline to payment.
- Passive cancellation rate: Subscriptions lost to failed payments ÷ active subscriptions. This is the number your recovery work should lower.
See our subscription metrics guide for the other numbers worth tracking.
A failed payment checklist
- Declines are sorted into soft, hard, customer action and store-side.
- Soft declines get three or four well-spaced retries; hard declines get a card-update request instead.
- Each stage has its own short email and text, with a one-tap card update link.
- Subscribers hear about expiring cards before the renewal.
- Bank confirmation requests reach the subscriber right away.
- There is a clear rule for what happens when retries run out, and a final notice to match.
- Store-side errors alert your team, not the customer.
- Recovery rate and recovered revenue are reviewed every month.
How Chargezen recovers failed payments
Failed payment recovery is part of Chargezen Subscriptions:
- Retries on your schedule: Choose how many tries and how far apart, or keep the default of four retries.
- Knows why it failed: Each decline is sorted: a card the subscriber needs to fix, a short hiccup worth another try, or a store setting your team should check.
- Reminders by email and text: A message for each stage, a direct card-update link, warnings up to 7 days before a renewal when a card is expiring, and the step to approve a payment when a bank asks.
- Your rule when tries run out: Cancel, pause, skip that order or keep the subscription open, with a final notice that matches.
- Editable automations: Every reminder is a workflow you can edit, test or extend, and failed payment events can go to Klaviyo if you'd rather send from there.
- Help by text or chat: Subscribers with a question can ask Concierge, the same AI that handles their other subscription changes.
- Reports: Recovered revenue and failure reasons in subscription analytics.
Subscriptions is $199 a month or $1,990 a year for Shopify Advanced and Shopify Plus stores, with no commission on recovered payments. See pricing and churn prevention. Terms: dunning management, involuntary churn, payment method.
Frequently asked questions
What is the difference between a soft and a hard decline?
A soft decline is temporary, such as low funds or a brief bank error, and a retry later can succeed. A hard decline, such as an expired or closed card, will fail every time until the subscriber gives you a new card.
How many times should I retry a failed subscription payment?
Three or four retries over one to three weeks is a common starting point for soft declines. Test against your own recovery data, and don't retry hard declines.
Should I cancel a subscription after the last failed retry?
Not necessarily. Pausing or skipping the order keeps the subscriber easy to restart. Cancel when you'd rather start fresh, and follow up with a win-back.
Is failed payment recovery the same as dunning?
Yes. Dunning is the older term for chasing payments that didn't go through; for subscriptions it means retries plus reminders.
