A WooCommerce checkout can fail in the browser, during session handling, at payment authorisation, on a webhook, or while creating the order. Capturing the exact failing step keeps you from changing unrelated settings while sales are already at risk.
Step 1 — Watch the failing request
Open the browser developer tools, go to the Console and Network tabs, and attempt the checkout. A red JavaScript error usually points at a script conflict or a broken minification setting. A failed AJAX request — the ?wc-ajax=checkout call returning 500 or timing out — points at the server, and its response often contains the PHP error itself.
Step 2 — Check the usual layer suspects
- Caching: the checkout page must never be cached; a stale page carries an expired security nonce that blocks submission.
- JavaScript optimisation: aggressive minify/combine settings frequently break checkout scripts — exclude them.
- Session: a lost cart or a nonce mismatch usually traces back to caching or a session-handling plugin.
- Gateway: an authorisation that succeeds without a confirmation leaves the order stuck.
Is your website affected right now?
Send the URL and the symptom you can see. Jordi Ensenyat reviews the case personally and defines the scope and quote before anything is changed. This form never asks for passwords.
Step 3 — Read the WooCommerce logs
Under WooCommerce › Status › Logs you will find gateway logs and fatal errors with timestamps. Match the time of a failed test against the log to see whether the order was created, whether payment was attempted, and where the chain broke.
Step 4 — Test safely, end to end
Use the gateway’s test mode or a controlled low-value order. Walk product → cart → checkout → payment → confirmation, then verify the order status, stock movement, confirmation email and webhook. A checkout is only repaired when the full cycle completes coherently, not when the visible error disappears.
When to escalate
If payments are involved, orders are affected, or the failure is intermittent and hard to reproduce, a specialist can trace it without risking real transactions. Send the failing step, the payment method, the device and any error text and the case can be assessed before access is requested.
EVIDENCE-LED WORDPRESS RECOVERY
Diagnose the exact point where WooCommerce checkout fails
In hacked WordPress containment and recovery, the visible symptom may be far from the cause. The objective is to contain the incident, recover authorised access and remove persistence without erasing useful evidence. A checkout can fail in the browser, during session handling, at payment authorisation, on a webhook or while creating the order. Capturing the failing step and gateway response prevents unrelated settings from being changed while sales are already at risk.
What we verify
- The complete journey, not only the screen where the error appears
- External dependencies, logs and evidence before configuration changes
- Browser errors, network requests and server logs at the failing step
- Cart session, customer data, shipping, tax and coupon calculations
- Gateway status, credentials, callbacks, webhooks and order notes
- Successful order creation, payment state, email and stock adjustment
What a verified outcome means
Close-out documents the cause found, the change applied and the tests performed. The result must be observable and repeatable—not a feeling that it “seems to work”.
BEFORE THE ASSESSMENT
Common questions about this WordPress incident
How do you verify that the problem is genuinely resolved?+
The affected journey is reproduced, its dependencies are checked and post-change evidence is recorded.
Why does checkout fail for some customers but not others?+
Device, browser, payment method, location, cached scripts or session state can create a conditional failure. Those dimensions help reproduce it.
Can a payment succeed when WooCommerce shows an error?+
Yes. A delayed callback or order-creation failure can leave payment and order states out of sync, which must be reconciled carefully.
What should I avoid during a checkout incident?+
Avoid repeated live tests with real cards, broad plugin updates and deleting failed orders before gateway and server evidence is captured.