WooCommerce Duplicate Charge Prevention

Symptoms

• Customers report being charged twice or being asked to pay again after a pending or failed order.
• Provider dashboards show authorizations or captures that WooCommerce did not clearly reflect.
• Support messages or recovery workflows tell customers to retry before payment state is verified.

Most Common Causes

• Provider callbacks, webhook delays, manual capture, timeouts, or order-status drift can hide payment truth from WooCommerce.
• Checkout copy and support replies can encourage a second attempt while the first transaction is unresolved.
• Manual recovery queues often lack a required provider-state check.

How To Confirm The Cause

• For the affected order, compare WooCommerce status, order notes, transaction ID, provider status, capture state, refund state, and customer messages.
• List retry instructions shown at checkout, in emails, and by support for failed or pending orders.
• Identify whether the gateway uses immediate capture, authorization, delayed methods, redirects, or webhook confirmation.

Fixes

• Require provider-state review before asking a customer to retry payment on ambiguous orders.
• Add internal notes or a review status for orders that might have payment evidence but are not safe to recover automatically.
• Rewrite customer-facing messages so they do not imply payment failed when the store has not verified provider state.

How To Verify The Fix

• Review a sample of failed, pending, and customer-charged cases and confirm each has one safe next action.
• Test checkout timeout, failed payment, and provider-return behavior on staging where possible.
• Monitor duplicate-charge complaints, refund corrections, and payment-retry tickets after the workflow change.

When To Contact Support

Escalate when provider records show capture, authorization, dispute, refund, chargeback, or unclear settlement state.