WooCommerce Checkout Not Working: Find the Exact Break in 3 Minutes

Checkout failures are silent. Your site loads, your logs look normal, and orders simply stop. This page narrows it to one of five breaks before you change a single setting.

Does this match what you see?

3-minute check, no changes to your live store

1
Open your store in a private window sized like a phoneAdd a variant product to cart, open /cart, then press Checkout from both the drawer and the cart page. If one path fails, the break is in the theme script, not the gateway.
2
Look at the last request before it stopsOpen DevTools Network, filter for wc-ajax. A successful checkout ends with ?wc-ajax=checkout returning 200 and an order key. If that request never fires, the button handler is blocked. If it fires and returns an error, the break is server side.
3
Disable caching for /checkout onlyA cached checkout page serves a stale cart hash. Set Cache-Control: no-store on checkout and cart. If orders resume, you found it.

The five places it breaks

BREAK 1

Dead Buy button

A theme or upsell script fails to bind its click handler. The button renders but never submits. Look for a JS error at the moment of click. Any uncaught error before the handler binds will kill it.

BREAK 2

Gateway approves, WooCommerce never creates the order

The payment provider returns success, but no <code>?wc-ajax=checkout</code> request follows. The customer is charged and gets nothing. Compare the Network sequence: <code>create-order</code> then <code>approve-order</code>. If approve returns 200 and nothing follows, the handoff is broken.

BREAK 3

Session expired on back navigation

No <code>no-store</code> on checkout means the browser reuses a stale copy, then WooCommerce answers an empty cart with a session error. Fix the cache header, not the plugin.

BREAK 4

Plugin conflict on the checkout hook

Two plugins write to the same hook. Classic symptom: works with one gateway, fails with another on the same site. Bisect by deactivating half, not one by one.

BREAK 5

Intermittent failures only on some orders

Usually a webhook or token problem, not a page problem. Logs show retries. Read the gateway log timestamps against the failing orders.

Site Content Guard scans every page for dead buttons, broken links and missing purchase exits, then reports the exact selector to fix.One-time purchase · instant download · commercial use included

If the report does not match your case, reply and tell me the exact step where it stops. I answer every message.