Short answer: five families of causes
WooCommerce payments usually fail for one of five reasons: the card issuer declined the payment, authentication was required and not completed, something in the store or checkout blocked the request, the confirmation (webhook) did not reach the store, or the provider restricted the account or payment method. Each has different evidence and a different fix. The ordered route for working through them is in the gateway failure recovery workflow.
1. Declines from the card issuer
When the customer's bank refuses a payment, the gateway dashboard normally shows a decline reason or code. Typical reasons include insufficient funds, a flagged transaction or an incorrect card detail. These are usually not a store fault, but patterns matter: a sudden rise in declines, or declines concentrated in one country, can point to fraud settings or issuer behaviour worth reviewing.
2. Authentication that was not completed
Many cards require additional authentication, such as 3D Secure, under strong customer authentication rules. If the challenge window fails to load, the customer abandons it or a script is blocked, the payment fails or stays incomplete. Compare test payments that require authentication on your Checkout block and, if used, shortcode checkout.
3. Store, plugin or checkout conflicts
If the gateway dashboard shows no attempt at all, the failure happened before the request left your store. Common causes are a plugin conflict, a theme override, a caching rule serving an old checkout, a JavaScript error or an incompatibility between a gateway and the Checkout block. Check the browser console, WooCommerce logs and recent changes, and reproduce on staging.
4. Webhook and order status problems
A customer can be charged while the order stays pending because the webhook never updated it. Security plugins, firewalls, wrong webhook addresses and stalled scheduled tasks are frequent causes. Compare the provider's event log with your order list.
5. Account or payment method limits
Providers can limit currencies, countries, amounts or product types, and may pause an account that needs more information. These show up as clear notices in the provider dashboard or by email. Read them first; they often explain a puzzling pattern immediately.
What to do next, in order
Start with evidence. Gather the order numbers, timestamps, error text and gateway statuses for a handful of failed payments, and mask anything sensitive. Group them by family. If most are declines, review fraud and authentication settings and speak to the provider about issuer patterns. If most never reached the gateway, test on staging with plugins disabled one by one. If payments succeeded but orders are pending, fix the webhook path and scheduled tasks. If the provider has restricted something, resolve it with the provider first.
Do this before changing settings at random. A tidy sample of five or ten cases is usually enough to show which family you are dealing with, and it gives a developer or support agent exactly what they need to help quickly.
How to tell which one you have
Ask three questions in order. Did the payment reach the gateway? If not, look at the store and checkout. If it did, was it declined or incomplete? If it succeeded, did WooCommerce receive the confirmation? Writing the answers down turns a vague "payments are failing" into a specific, checkable statement. For the comparison of gateways that sits behind these causes, see how WooCommerce payment gateways differ. For the full system, see the book overview and the complete book.
Why the same symptom can have different causes
Two stores can both report that customers cannot pay yet have unrelated problems. One may have a conflict after a theme update; another may have a provider that paused card payments pending verification. This is why the book treats diagnosis as its own stage and asks for evidence before suggesting fixes. A calm, evidence-first approach also protects your relationship with the provider: when you contact support with timestamps, order numbers and clear observations, you are far more likely to get a useful answer quickly.
Sources and verification
WooCommerce, its extensions, WordPress and payment providers change their features, countries, fees and screens from release to release. The statements in this guide reflect what WooCommerce and the providers published when it was last reviewed on 4 October 2026, against the WooCommerce 11.1 series, and may change. Check the current pages below before you act, and never test changes on a live store without a backup.
Educational guide only. Not legal, tax, security-audit or financial advice. The Prompt Powerhouse is independent of, and not affiliated with or endorsed by, WooCommerce, Automattic or WordPress. No payment, approval, fee or dispute outcome is guaranteed.