WooCommerce Subscription Charged the Customer Twice? Causes & Fix

Two charges, same amount, same customer, same renewal. Before anything else: confirm it's genuinely a duplicate, then refund one today — a refund you make is a customer you keep; a chargeback they raise is a customer you lose plus a fee. Here's how to tell, and why it happened.

Last updated: 16 Jul 2026 · ~7 min read

What a duplicate renewal charge actually is

A renewal is meant to be exactly one thing happening once: the scheduler fires a payment hook for a subscription, a renewal order is created, the gateway is asked for one charge. A duplicate means two processes both believed they owned that renewal at the same moment. WooCommerce guards against this with a short-lived lock on the order — if that lock is released, missing, or expires early, the guard is gone.

You'll usually see it as two paid renewal orders for one period, or one order with two "payment complete" notes and two charges against it at the gateway. Your customer sees two identical debits on their statement and, quite reasonably, assumes you're the problem. Speed matters more than elegance here.

The most common causes (most likely first)

1. The order lock was released too early and two processes ran the same renewalTwo charges at the gateway seconds apart, same amount, same customer. The gateway's synchronous charge and the payment_intent.succeeded webhook both handled the renewal — each confirming its own intent, each calling payment_complete(). Look for two "payment complete" notes on the order within the same minute. The #1 cause.
2. The store recorded a successful charge as failed, then retried itTwo charges hours or days apart, not seconds. The first one shows Succeeded at the gateway but its renewal order is marked Failed — the confirmation never came back, so the retry rules charged again. Check the webhook log around the first charge for a timeout or non-200.
3. The same scheduled action ran twiceWooCommerce → Status → Scheduled Actions shows two scheduled_subscription_payment entries with identical arguments, or one action that ran twice. Overlapping queue runners — WP-Cron and a server cron both hitting wp-cron.php — will do this, as will a claim that was never released.
4. Someone processed the renewal by hand while the automatic one was in flightOne charge lines up with the scheduled renewal time; the other lines up with an admin action, and an order note names a user. Common when a renewal looks stuck and gets "helped along".
5. It isn't a duplicate — there are two subscriptionsThe two charges belong to two different subscription IDs. The customer checked out twice, or an old subscription was never cancelled when they resubscribed. Rule this out first: it takes thirty seconds and changes the whole answer.

Where to look first

• Open the gateway dashboard and find both charges. Note the exact timestamps — seconds apart points to concurrent processing (cause 1 or 3); hours or days apart points to a retry after a mis-recorded failure (cause 2).
• Check the subscription IDs behind each charge. Two different subscriptions means two real purchases (cause 5) — not a bug, and refunding is a business decision, not a repair.
• Open the renewal order and read its notes. Two "payment complete" entries within the same minute confirms cause 1. A note naming an admin user confirms cause 4.
• Check WooCommerce → Status → Scheduled Actions for two identical scheduled_subscription_payment actions for this subscription — that's cause 3, and it will happen again next cycle unless you fix the runner.
• Then refund one charge — through the duplicate renewal order, not the gateway. Refunding in the gateway alone leaves WooCommerce believing it still holds the money, and your reports wrong.

How to know you fixed it

Frequently asked