The short answer
Start by testing the checkout yourself in a private window, on a phone, with a real card if you can. Then check the four usual causes in order: a caching or speed plugin interfering with the checkout, a payment method in test mode or disconnected, a plugin clash since the last update, and payment webhooks failing so paid orders stay “Pending payment”. WooCommerce → Status → Logs usually shows which one it is.
A broken checkout is the most expensive WordPress problem a shop can have, and it’s often invisible to the owner. You’re logged in, your browser has everything cached, and it works for you. So the first step is always to see what your customers see. After that, it’s a matter of working through the usual causes in a sensible order, rather than switching things off at random.
Is this what you’re seeing?
- Customers say they can’t complete their order, or orders have suddenly stopped coming in.
- The Place order button does nothing, or spins and never finishes.
- The checkout page is blank, won’t load, or shows “There has been a critical error”.
- Your payment methods, such as card or PayPal, have disappeared from the checkout.
- Customers are charged, but the order says “Pending payment” or “Failed”, or there’s no order at all.
- The checkout works on a computer but not on a phone, or in one browser but not another.
- Customers see “No shipping options were found”, or an error about a field.
What usually causes it
Caching or a speed plugin interfering with the checkout
The basket, checkout and account pages must never be cached, because they’re different for every customer. Most caching plugins know this, but a host’s cache, a Cloudflare “cache everything” rule or a plugin that combines and shrinks JavaScript can still break them. How to tell: it works for you logged in, but not in a private window. Or open your browser’s developer tools (F12, then Console) on the checkout page and look for red errors that mention a minified or combined file.
The payment method is in test mode, or disconnected
Stripe, PayPal and WooPayments all have a test mode, and keys or connections that can expire, be changed or be revoked. A payment account with a problem, such as missing verification details, can also stop taking payments. How to tell: check WooCommerce → Settings → Payments. Open each payment method’s settings and look for “test mode” or “sandbox” switched on, or a message asking you to reconnect. Then check your Stripe or PayPal dashboard for warnings.
A clash after an update
An update to WooCommerce, a payment plugin, your theme or a checkout-related plugin can break the checkout while the rest of the shop looks fine. Themes that override WooCommerce’s templates are a common cause. How to tell: the problem started straight after an update. WooCommerce → Status shows whether your theme has outdated copies of WooCommerce templates, and the fatal error logs under WooCommerce → Status → Logs name the plugin.
Paid orders stuck because webhooks are failing
When a customer pays by card, the payment provider tells your site the payment went through by sending a “webhook”, a message to your site in the background. If your site doesn’t receive or accept it, the payment succeeds but the order stays “Pending payment”. This happens after a move to a new domain or host, when keys are changed, or when a security plugin or firewall blocks the provider. How to tell: the Stripe dashboard shows the payment as successful, but the WooCommerce order doesn’t. Stripe’s webhook pages show each delivery to your site and whether it failed.
The block checkout and an older plugin
New WooCommerce shops use the Checkout block, and older ones often use the classic checkout shortcode. Some payment, delivery and custom-field plugins still only work with the classic one. Then a payment method or an extra field simply doesn’t appear. How to tell: check WooCommerce → Settings → Advanced to see which page is your checkout, then edit that page. If it holds a Checkout block, the plugin’s documentation will say whether it supports blocks.
Shipping, required fields or an address problem
If no delivery method covers the customer’s address, the checkout can’t finish. A custom required field, a postcode check or a VAT number field can also stop the order. How to tell: customers see a message about shipping or a particular field, and it only affects some addresses or countries.
Security warnings and mixed content
If part of the checkout loads over plain http, browsers may block it, and payment fields won’t load. How to tell: the browser shows “Not secure” on the checkout page, or the Console shows “mixed content” warnings.
What you can safely try
Take a backup first. Every step here can be undone.
- Test the checkout as a customer would: in a private window, on your phone using mobile data, and in a second browser. Note exactly where it fails and what it says.
- Look at WooCommerce → Orders for recent orders stuck on “Pending payment” or “Failed”, and compare them with the payments in your Stripe or PayPal dashboard.
- Check WooCommerce → Status → Logs, especially any log with “fatal-errors” in its name, and your payment plugin’s own log if it has one.
- Check each payment method under WooCommerce → Settings → Payments for test mode and connection warnings.
- Clear your caching plugin, host cache and Cloudflare. Check that the basket, checkout and account pages are excluded from caching and from JavaScript combining or delay.
- If it started after an update, check whether that plugin offers a rollback to its previous version, or ask your host to restore just that plugin from last night’s backup. Don’t roll back WooCommerce itself without a backup of the database, because updates can change it.
- Check the shipping zones under WooCommerce → Settings → Shipping cover the addresses that are failing.
When to stop and get help
- Customers are being charged, but orders aren’t being created or completed. You need to know who has paid for what.
- You see lots of small failed payments, often from different names, in a short time. That’s card testing: criminals using your checkout to check stolen card numbers. Your payment provider may block your account if it goes on.
- The fix would mean rolling back WooCommerce or editing the database.
- You’re losing sales right now and can’t afford a day of trial and error.
- The checkout has been customised, and you don’t know what by.
A real example
The checkout on an events site that sells tickets through WooCommerce looked fine. Customers could pay, and orders came through. But one order for two tickets created four attendee records, which threw out the event’s capacity figures and raised the question of whether anyone had been sold, or charged for, the wrong tickets.
The cause I found was timing. More than one step of the order processing could start creating tickets before the site had recorded that they already existed, so two processes could each create a set. I wrote a small must-use plugin that puts a database lock around ticket creation, so only one process can create an order’s tickets at a time. It loaded correctly, and I tested that the lock works.
It’s a good example of why checkout problems aren’t always about the checkout page. The customer’s part worked. What went wrong happened afterwards, in the background.
Getting it fixed
I’ll test your checkout as a customer, work through the logs and your payment provider’s records, and fix what’s actually broken, whether that’s a setting, a clash, a webhook or custom code. I’ll also check whether any customers were affected while it was broken. See WooCommerce support for what I cover. A WordPress repair is a fixed £119, which covers finding the problem and up to 90 minutes of fixing it. Most repairs fit in that, and you’re never charged more without agreeing first.
If customers can’t check out or pay right now, there’s a fixed-price emergency fix for exactly that. See emergency WordPress support.
Questions
The checkout works on desktop but not on mobile. Why?
Usually a JavaScript error that only happens on mobile browsers, a pop-up or cookie banner covering the Place order button, or a payment method like Apple Pay or Google Pay that’s set up differently. Test on a real phone with mobile data, and look at what covers the button.
Customers get a critical error at checkout. What does that mean?
A plugin or theme hit a fatal error while building the checkout. The WooCommerce fatal error log, or the steps in finding what caused a critical error, will usually name it.
Customers were charged but there’s no order. Have I lost the money?
No. The payment is in your Stripe or PayPal account. What’s missing is the order in WooCommerce, usually because a webhook failed. The payments can be matched up with customers, and the webhook fixed so it doesn’t happen again.
My payment methods have disappeared from the checkout. What happened?
The payment plugin may be switched off or disconnected, it may not support the block checkout, or it may be hiding itself because of the basket’s currency, total or the customer’s country. Check WooCommerce → Settings → Payments first.
Should I switch from the block checkout back to the classic one?
Only if something you rely on doesn’t support blocks. It’s reversible, but the block checkout is where WooCommerce is heading, so it’s worth checking whether your plugins have been updated to support it first.
I updated WooCommerce and the checkout broke. Can I just undo it?
Sometimes, but carefully. A WooCommerce update can change the database, so rolling back the plugin alone can cause new problems. Restore from a backup taken before the update, or find the plugin or theme that clashes with the new version.
Written by Peter Claridge, who fixes WordPress sites for businesses across the UK from Reading. Last checked on WordPress 7.1, November 2026.