Guide
WooCommerce duplicate charge or duplicate order
Duplicate charge and duplicate order incidents need careful confirmation before anyone assumes what happened financially.
Problem
When a customer sees two payments, two pending orders, or a retry pattern that looks duplicated, the immediate goal is to confirm whether the issue is a display problem, a retry window, or a true duplicated payment-state event.
Common causes
- Customer retries, refreshes, or back-button behaviour created more than one checkout attempt.
- A timeout or delayed redirect made the original attempt look failed when it actually succeeded.
- Webhook or order-state processing drift created duplicate-looking admin records that still need review.
- Multiple payment flows or custom checkout behaviour introduced a race condition around order creation.
What to check
- Compare the Stripe payment timeline with WooCommerce order creation timestamps and transaction IDs.
- Check whether the events represent one customer action with retry noise or truly separate payment objects.
- Inspect webhook timing, checkout behaviour, and whether duplicate orders share the same cart context.
- Run the free scan to surface unmatched evidence and possible duplicate windows before making manual adjustments.
Need help checking this on a live store?
Start with the free scan. If the findings may need review, request a founder-led human review for manual confirmation and next steps.