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.
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.Cache-Control: no-store on checkout and cart. If orders resume, you found it.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.
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.
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.
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.
Usually a webhook or token problem, not a page problem. Logs show retries. Read the gateway log timestamps against the failing orders.
If the report does not match your case, reply and tell me the exact step where it stops. I answer every message.