WooCommerce Subscription Payment Method Not Set? Causes & Fix
A subscription with a blank payment method — or one showing Manual renewal — will never charge on its own. The schedule still ticks, the renewal order still gets created, and then nothing happens. Here's why the card went missing and how to get it back.
Last updated: 16 Jul 2026 · ~6 min read
The most common cause is that the subscription has no saved gateway token any more — the _stripe_source_id and _stripe_customer_id meta are empty, which is typical after a gateway migration or an account switch. When the scheduled payment hook fires, it hands the gateway an empty payment method and gives up. The fix is to get the customer to re-save a card, which re-attaches a live token to the subscription.
What "payment method not set" actually means
An automatic subscription is really two things: a schedule, and a token — a reference to a card stored at the gateway, saved against the subscription. WooCommerce Subscriptions owns the schedule. The gateway owns the money. The token is the only thing joining them. Payment method not set means the schedule survived and the token didn't.
To you it looks like a subscription that's still Active with a blank payment column. To the customer it looks like a free ride, right up until the renewal fails and their access is pulled. Nothing here is a billing error — the store is doing exactly what it's told, and it's been told to charge nobody.
The most common causes (most likely first)
- The saved token is gone — the gateway meta is emptyThe subscription's
_stripe_source_idand_stripe_customer_idare blank or missing. Classic after migrating gateways, switching to a new Stripe account, or restoring a database that predates the card being saved. The IDs from the old account mean nothing to the new one. The #1 cause by a distance. - Manual renewals are switched on store-wideIt's not one subscription — it's all of them. Check
WooCommerce → Settings → Subscriptionsfor the option that turns off automatic payments. If that's on, every subscription is manual by design, whatever token is saved. - The gateway the subscription was bought through is gone or disabledThe subscription's payment method names a gateway that no longer appears under
WooCommerce → Settings → Payments. Subscriptions can't find a gateway to charge with, so it falls back to manual renewal. - The customer deleted their own cardOnly some subscriptions are affected, and the customer's
My Account → Payment methodsscreen is empty. Removing a saved card there strips the token from their subscriptions too. - Live/test mode mismatch on the customer IDThe token exists but the gateway rejects it as not found. A customer or source ID created in test mode is meaningless in live mode (and vice versa) — common after testing on a copy of the live database.
- The subscription is flagged as requiring manual renewalJust this one subscription is manual while its neighbours are automatic — the
_requires_manual_renewalflag is set, usually by an import, a bulk edit, or a failed automatic switch.
Where to look first
- Open
WooCommerce → Subscriptionsand look at the payment method column across the whole list — is it blank on every subscription, or just some? All of them points at a store-wide setting (cause 2); some points at missing tokens (cause 1). - Open one affected subscription and check whether the gateway meta (
_stripe_customer_id,_stripe_source_id) has values. Empty = cause 1, and no amount of editing the schedule will fix it. - Check
WooCommerce → Settings → Payments— is the gateway this subscription was bought through still installed and enabled? If it's gone, that's cause 3. - Look up the customer at the gateway. If the customer record or its cards don't exist there, the token can't be recovered — the customer has to re-enter a card. There's no server-side repair for this.
- Confirm the gateway's mode. Live keys with test-mode customer IDs (cause 5) will fail the same way as no token at all.
How many of your subscriptions are quietly missing a card?
One subscription with a blank payment method is a five-minute fix. Finding out that forty of them lost their tokens in last year's gateway migration — and only discovering it as each one silently fails to renew — is a much worse afternoon. DiagnosticIQ's free dashboard scans your subscriptions for missing gateway tokens, manual-renewal flags and dead gateways in one pass, and tells you which renewals are going to fail before their dates come round.
Get the free plugin →Made by Prima Digital — the team behind this guide. Free forever; no card to install.
How to know you fixed it
After the customer re-saves a card, the subscription's payment method column should name the gateway (not Manual renewal), and the next renewal should charge on its own and move the renewal order straight to Processing.
Frequently asked
Can I just type the card in myself?
No — and you shouldn't. The card lives at the gateway, not in WooCommerce, and re-authorising it needs the cardholder. Send the customer their My Account payment methods page, or the pending renewal order's payment link, and let them enter it.
Will the subscription cancel itself?
Not by itself. It'll create a renewal order, fail to charge it, and drop to On-hold — where it will sit indefinitely. The customer's access usually goes at that point.
Was the customer charged?
No. An empty payment method means the charge was never attempted, so there's nothing to refund and nothing in dispute. The revenue is simply missing.
Can I switch a manual subscription back to automatic?
Only once a valid token is attached. Clearing the manual-renewal flag on a subscription with no saved card just moves the failure one step later.