How Does WooCommerce Retry a Failed Renewal Payment?

Why This Happens

A declined card is rarely permanent — a temporary hold, a bank's fraud check, or a card simply being over its limit for a day can all resolve themselves without the customer doing anything. Rather than suspending a subscription the moment one payment attempt fails, WooCommerce Subscriptions' Failed Payment Retry system gives the card a few more chances over several days before treating the subscription as genuinely lapsed.

The retry schedule is deliberately spread out rather than immediate, because retrying the same declined card seconds later almost never changes the outcome — spacing attempts across days gives whatever caused the decline time to actually clear.

Common Causes

• Retry system disabled for the gateway. It's a per-gateway setting, not global — a store using multiple gateways can have it enabled for one and not another without anyone noticing.
• All retries exhausted. After the final scheduled retry also fails, the subscription moves to "On hold" (manual renewal) or is cancelled outright, depending on the configured behavior.
• Gateway doesn't support stored-card retries. Some gateway integrations only support charging a token once per renewal cycle and don't expose a way to retry the same token on a different day.
• Retry schedule too short for the customer's bank. The default 1/3/5-day spacing works for most cases, but a slow-to-clear hold can outlast even the final retry.

How to Fix It

1. Check the setting is on. WooCommerce → Settings → Subscriptions → Recurring Payments, per gateway — confirm "Enable Automatic Recurring Payments" and retry settings are both active for the gateway actually in use.
2. Review the retry rules. The schedule and the final action (suspend vs. cancel) are both configurable. A store with a strongly loyal customer base might want a longer retry window before giving up.
3. Trigger a manual retry. From the subscription's admin screen, an admin can force an immediate retry rather than waiting for the next scheduled attempt — useful once a customer confirms their card issue is resolved.
4. Ask the customer to update their payment method proactively. If a card is known to be expiring, prompting an update before the next renewal avoids the retry cycle altogether.

If retries are failing across many different customers' cards at the same time, the cause usually isn't the customers' banks — it's the gateway integration itself, and worth checking against a manual test charge outside the subscription system.