Recurring membership or course payments failing usually comes down to one of three points in the chain — whether the renewal attempt fires at all, whether the payment method is still valid, and whether the gateway can process an unattended charge — each of which fails for a different reason.
Check your payment gateway dashboard for the failed attempt
Look at your gateway’s dashboard for the specific renewal. Was a payment actually attempted and declined, or does it show no attempt at all? That distinction narrows this down to either a payment-method problem or a scheduling problem, which are fixed differently.
Recurring payment failure diagnosis
Recurring membership payments traced through scheduling, tokens, and webhooks to the actual failure.
- Full backup taken before we start
- If we can’t fix it, you get your money back
- We never ask for your own password
This or something else?
| Recurring membership or course payments are failing | This fix covers it |
| This is specifically a WooCommerce Subscriptions product, not membership or course access | Subscription renewal failure diagnosis, in the WooCommerce Extended & Marketplace bucket, the commerce-specific version |
| Payment is taken but access isn’t extended despite a successful charge | Worth confirming — likely a webhook delivery issue between the payment and the access system |
| One-off, non-recurring payments are also failing | A broader payment gateway integration issue, worth describing directly |
What you are seeing
- Members losing access when a recurring payment should have renewed it
- A renewal attempted and declined by the gateway
- No renewal attempt showing at all, despite the due date passing
- The issue possibly affecting only members who joined through a specific plan or promotion
Common causes
- A scheduled task not firing, so the renewal attempt never happens
- A payment token invalidated by a card expiry or gateway-side change
- Strong authentication requirements the gateway can’t satisfy without the member present
- A webhook failing to deliver, so a successful payment doesn’t actually extend access
- A pricing or currency mismatch between the original signup and a later plan change, causing the gateway to reject the renewal amount
What we do
- Confirm whether the renewal attempt fires and whether payment is attempted
- Check scheduled tasks, payment tokens, and webhook delivery in turn
- Fix the specific failing layer identified
- Verify the full renewal chain end to end with a test cycle
- Identify any members who lapsed and can be recovered
What is included
- The failing layer identified and corrected
- A verified, working renewal chain
- A list of affected members and which can be recovered
- The pre-fix backup, kept for 30 days
Not included
- Contacting members directly to update expired payment details
- Recovering revenue from memberships that already lapsed and cancelled
- WooCommerce Subscriptions-specific renewal issues — a separate, commerce-focused fix
- Building custom recurring billing logic, quoted separately if needed
Questions about this fix
How is this different from the WooCommerce subscription renewal fix?
This covers membership or course access specifically, which often runs through a different plugin and payment integration entirely than a WooCommerce Subscriptions product — worth confirming which system is actually involved before ordering.
What if the payment succeeds but the member still loses access?
That points at a webhook delivery problem rather than a payment problem — the charge went through, but the system granting access was never correctly notified.
Can lapsed memberships be automatically recovered once this is fixed?
We identify which lapsed memberships can be recovered and how, though recovering revenue from ones that already cancelled outright isn't something a technical fix alone can undo.
Will this affect members whose payments are working fine?
No, this specifically targets the identified failure — members already renewing successfully are unaffected.
How urgent is this if it's actively cutting off paying members?
Genuinely worth prioritising, since ongoing failures compound the longer they run, both in lost access and lost revenue.
Related fixes
If this is the second time this year
A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.
Your access, your rules
Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.
We back up first, always
Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.
If it is not what you bought
If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.
If we cannot fix it
You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.
If it comes back
Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.
What we are responsible for
If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.