Failed Renewal Payments: Measuring and Recovering Involuntary Churn in WooCommerce Subscriptions

A large share of subscription churn comes from payments that fail, not customers who decide to leave. Here is how to measure failure and recovery rates in WooCommerce Subscriptions, read decline codes under the card network retry rules, and set a retry schedule that recovers more without breaking them.

When a subscriber cancels, you get a reason, a date and sometimes a survey answer. When their card is declined at renewal, you often get nothing: the renewal order sits as failed, the subscription goes on hold, and a month later it is counted with every other lost customer. That second kind of loss is involuntary churn, and it is larger than most store owners expect. Recurly estimates that failed payments account for an estimated 20 to 40 percent of total churn across subscription businesses.

Involuntary churn is also the cheapest churn to fix, because the customer never decided to leave. This guide covers how to measure it in WooCommerce Subscriptions, what the decline codes tell you, how card network rules limit retries, and a schedule and routine that recover more of it.

The renewal funnel

Every renewal that comes due ends in one of three places: paid on the first attempt, paid after a retry or a card update, or lost. Measuring involuntary churn means measuring each step separately.

Renewal payment funnel from renewals due to involuntary churn Renewals due split into paid on first attempt and failed on first attempt. Failed renewals split into recovered by automatic retry, recovered after the customer updates their card, and lost, which is involuntary churn. Renewals due 100% Paid first attempt 1 minus failed-payment rate Failed first attempt failed-payment rate Recovered by automatic retry Recovered after card update or email Lost: involuntary churn
Recovery rate is the share of the orange box that ends up in the two green boxes on the right.

Metabase’s metric guide gives clean definitions for these steps and lists the mistakes that distort them. Its central point is to report failure and recovery together, because a high failure rate with strong recovery is a very different situation from one without.

MetricDefinitionCommon mistake
Failed-payment rateRenewal orders whose first attempt failed, divided by renewal orders dueIncluding one-time orders in the denominator
Recovery rateFailed renewals eventually paid, divided by failed renewalsMeasuring before the retry window has closed
Days to recoveryDays between first failure and payment, for recovered renewalsAveraging instead of looking at the distribution
Involuntary churn rateSubscriptions ended or left on hold after an unrecovered failure, divided by active subscriptionsCounting on-hold subscriptions as active forever
Involuntary share of churnInvoluntary churn divided by all churnMixing it with cancellations in one churn number

Keep the counting unit consistent. Decide whether the denominator is renewal orders or payment attempts, and stick to it; with retries enabled, one failed renewal produces several attempts.

Where the data lives in WooCommerce Subscriptions

Renewal orders are ordinary orders linked to a subscription, so first-attempt failures show up as renewal orders that reached the failed status. The retry history is stored separately. WooCommerce’s developer guide explains that retries live in a custom table, wcs_payment_retries, with statuses of pending, processing, complete, failed and cancelled. A retry that ends complete is a recovery; one that ends failed, with no later payment on the order, is a loss.

The piece most stores are missing is the decline reason. The same developer guide documents the woocommerce_subscription_renewal_payment_failed action, which fires each time a renewal payment fails. Hooking it to save the gateway’s decline code on the renewal order costs a few lines and makes every analysis below possible. Without it, all failures look the same.

Retries are off until you turn them on

This catches many stores. WooCommerce’s documentation states that the automatic retry system is off by default; you enable it under WooCommerce, Settings, Subscriptions, in the Payment recovery section. Once on, the default rules work like this:

RuleWaitEmail to customerSubscription status
112 hours after the failureNoneOn hold
212 more hoursPayment retry emailOn hold
324 more hoursNoneOn hold
448 hoursPayment retry emailOn hold
572 hoursPayment retry emailOn hold
Default retry rules in WooCommerce Subscriptions, about seven days in total. If the last retry fails, the renewal order is marked failed and the renewal invoice email is sent if enabled.

If you also use Stripe, do not assume Stripe’s own retry logic is doing this work. Stripe’s documentation describes Smart Retries as a Stripe Billing feature that retries failed subscription and invoice payments, by default up to 8 times within 2 weeks. With WooCommerce Subscriptions, the store creates the renewal order and asks the gateway to charge a saved payment method, so the schedule that governs retries is normally WooCommerce’s, not Stripe Billing’s.

Read the decline before you retry

Retrying every failure on the same schedule wastes attempts on cards that will never approve, and the card networks charge for that. PayPal’s summary of the rules, updated in May 2026, says Visa allows 20 retries in 30 days on soft declines and none on hard declines, with a per-attempt fee beyond those limits. Mastercard sends a merchant advice code with some declines; code 03 means do not try again, and code 21 means the cardholder cancelled the recurring payment.

Decline typeExamplesRetry?Better action
Insufficient fundsinsufficient_funds, issuer code 51Yes, spaced over daysRetry near common paydays; email after the second failure
Generic or temporarydo_not_honor, try_again_laterYes, a few timesRetry; then ask for another card
Expired or replaced cardexpired_cardOnly after the card changesCard updater service and a card update email
Hard declinelost_card, stolen_card, pickup_card, revocation_of_authorizationNoAsk the customer for a new payment method
Cancelled by cardholderMastercard advice code 21NoTreat as a cancellation and stop billing

The hard decline examples come from Stripe’s list of codes it will not retry automatically. Expired cards are worth separating out because they are partly preventable. Stripe describes its card account updater as a service that updates saved card details when a card expires or is reissued, and notes that some cards still will not be updated in time, which is why an email before the expiry month still matters.

When recoveries happen

Recovery is front-loaded. Recurly reports that 90 percent of recovered transactions occur within the first 10 days after a failed payment. Plot your own cumulative recovery by day since failure and you will usually see the same shape.

Illustrative cumulative recovery of failed renewals by day since first failure A curve rises quickly over the first week and flattens after day 10, reaching about 55 percent of failed renewals recovered by day 30. The default WooCommerce retry window covers roughly the first seven days. default retry window 0 7 10 20 30 Days since first failed attempt 0% 30% 55% about 90% of eventual recoveries by day 10
Illustrative curve. Use it to judge whether extending the retry window would add much, and when a personal email is most likely to help.

What it is worth: a worked example

InputTodayAfter changes
Renewals due per month2,0002,000
Average renewal value$35$35
Failed-payment rate8% (160 renewals)6% (120), after card updater and expiry emails
Recovery rate55% (88 recovered)70% (84 recovered), after retries by decline type
Lost subscriptions per month7236
Monthly recurring revenue lost each month$2,520$1,260
Illustrative figures. Each month’s saved subscribers keep paying in later months, so the annual effect is larger than twelve times the monthly difference.

The improvement comes from two places: fewer failures in the first place, and better recovery of the ones that still happen. Report them separately so you know which change worked.

Keep it out of your churn rate

Split churn into voluntary and involuntary in every report. A product or pricing change cannot fix a failed card, and a dunning change cannot fix an unhappy customer. Metabase lists treating failed payments as voluntary churn as one of the main mistakes for exactly this reason. Track both by signup cohort as well: a blended churn rate can move because the mix of new and old subscribers changed, a trap QuantumLayers explains in its guide to cohort analysis.

A monthly routine

  1. Confirm the retry system is enabled and the decline code is being saved on renewal orders.
  2. Report failed-payment rate and recovery rate for renewals due 30 or more days ago, so the retry window has closed.
  3. Break failures down by decline type and by card brand.
  4. Stop retrying hard declines; send those customers straight to a card update email.
  5. Check how many subscriptions have been on hold for more than 30 days and decide whether to cancel or keep chasing them.
  6. Report involuntary churn next to, not inside, voluntary cancellations.

Sources