Why Shopify subscription payments fail — and what actually recovers them

Moorly guides · Updated August 2026 · 7 min read

If you run subscriptions on Shopify, some of your renewals are failing right now. Not because customers decided to leave — because a card expired, a balance was low on billing day, or a bank hiccuped for a second. The industry calls this involuntary churn, and analyses of subscription businesses typically put it somewhere between 5% and 15% of renewals, depending on price point and customer base. For most merchants it is the single largest churn source they have never looked at.

The frustrating part: a failed renewal doesn't announce itself. Your customer might get an automated email. You, the merchant, usually get nothing — no alert, no line on a report. The subscriber just quietly stops being billed.

The three failure families (and why they need different treatment)

Payment failures look identical on a dashboard — a renewal that didn't go through. Underneath, they split into families that behave completely differently:

• Insufficient funds. The card works; the money wasn't there at that moment. These are the most recoverable failures — but timing decides everything. Retrying three times in the same 48 hours asks the same empty account the same question. Spacing attempts around when money tends to arrive (paydays, start of month) converts far better.
• Expired, cancelled, or invalid cards. No retry will ever succeed. Every automatic attempt against a dead card is wasted. The only fix is the customer updating their payment method — which means the job is a well-worded, well-timed card-update request, not a retry schedule.
• Temporary declines. Gateway timeouts, bank risk checks, one-off processing errors. These usually clear on a quick retry — and they're the one case where you should not email the customer, because the problem was never theirs.

This is why a fixed retry schedule — "retry 3 times, 2 days apart", which is what most built-in dunning offers — leaves money behind. It over-retries dead cards, under-times the recoverable ones, and emails people who did nothing wrong.

Why merchants don't notice the leak

Voluntary churn is loud: a customer clicks cancel, and every subscription app counts it. Involuntary churn is silent by design. Three things hide it:

• No merchant-facing alert. Subscription apps focus their dunning on the customer. Merchant notification — "tell me when a payment fails" — has been a recurring public feature request in app-store reviews for years.
• No dollar figure. Failures show up, if at all, as a status in an order list — not as "you lost $2,100 last month", which is the number that changes behavior.
• Retries mask the bleeding. Some failures self-heal on retry, so sampling one week understates the loss; the dead-card failures compound quietly.

A practical checklist

1. Measure before you change anything. Pull last month's renewals and count failures by reason. If your subscription app can't show that, that gap is itself the finding. (Our 30-second calculator gives you a first estimate.)
2. Separate dead cards from soft declines. Their fixes are opposites — card-update requests vs. better-timed retries.
3. Check your dunning settings. How many retries, at what spacing, and what happens on exhaustion? Auto-cancel on exhaustion silently converts recoverable failures into churn.
4. Mind the double-retry trap. If you add recovery tooling on top of your subscription app's own retries, make sure they coordinate — double charging a customer is worse than the failure was.
5. Track recovered dollars, not open rates. The only number that matters is payments that actually cleared after an action — and whether that action can prove it.

Further reading

Running Appstle? See the companion guide: Failed payment recovery for Appstle Subscriptions merchants.