Quick Diagnosis
Bank holds, authorizations, captures, and failed orders are different states; reconcile them before taking action.
Problem
WooCommerce Customer Charged but Order Failed
Handle WooCommerce cases where a customer appears charged but the order failed by reconciling provider records, authorization/capture state, webhooks, and customer communication.
Problem
The payment provider and WooCommerce order status do not appear to agree.
For: Store owners and support teams handling payment-status disputes.
Workflow
What to review
Customer Communication
Avoid promising refunds or fulfillment until the provider state is verified.
WooCommerce PaymentsSeverity: HighLast reviewed: 2026-09-16
Diagnosis
Symptoms, causes, checks, and fixes
Symptoms
- Customer reports a bank charge.
- WooCommerce order is failed, pending, or missing.
- Provider dashboard shows authorization, capture, or payment intent activity.
Most Common Causes
- Webhook failure after successful authorization.
- Authorization hold mistaken for charge.
- Checkout return failure.
- Duplicate attempt.
- Manual status mismatch.
How To Confirm The Cause
- Search provider dashboard by customer, amount, time, and transaction ID.
- Determine authorization versus captured charge.
- Check WooCommerce order notes and gateway logs.
- Confirm whether duplicate orders exist.
Fixes
- Update order only when provider evidence confirms captured payment.
- Void/refund according to provider status and store policy.
- Fix webhook or checkout return issue before asking customer to retry.
How To Verify The Fix
- Confirm provider and WooCommerce statuses match.
- Document customer communication.
- Run a gateway test after webhook fixes.
When To Contact Support
Escalate to the payment provider when transaction state cannot be confirmed from the merchant dashboard.
References