Skip to content
webfixed

Guides / WordPress

WooCommerce checkout not working or payments failing

By Michael Broadbridge. Last checked 14 November 2026 on WordPress 7.1, WooCommerce 11.3.

Short answer

A WooCommerce checkout usually fails because the payment gateway is disconnected or in test mode, the cart or checkout page is cached, an extension does not support the block checkout, a plugin clashes, or no shipping method covers the address. Place a test order in a private window, note the exact message, and read the logs under WooCommerce, then Status.

Symptoms

You may see one of these messages:

There are no payment methods available. Please contact us for help placing your order.

Sorry, it seems that there are no available payment methods. Please contact us if you require assistance or wish to make alternate arrangements.

No shipping options are available for this address. Please verify the address is correct or try a different address.

There are no shipping options available. Please ensure that your address has been entered correctly, or contact us if you need any help.

Something went wrong when placing the order. Check your email for order updates before retrying.

We were unable to process your order, please try again.

Sorry, your session has expired.

  • The basket is empty when customers reach checkout, or shows someone else’s items.
  • No payment methods appear, or a message says none are available.
  • A message says no shipping options are available for the address.
  • The Place order button spins for ever, or an error appears after clicking it.
  • Payments are declined, or orders sit on Pending payment even though the customer paid.

Causes, most likely first

  1. Payment gateway settings or test mode

    In test mode only the provider’s test cards work, so a live shop left in test mode cannot take real payments. A disconnected account, changed keys or broken webhooks cause failures too.

  2. Cached cart and checkout pages

    WooCommerce says the Cart, Checkout and My account pages must be excluded from caching. When they are cached, customers see empty baskets, other people’s details or expired sessions.

  3. An extension that does not work with the block checkout

    New shops use the Checkout block. A payment method or checkout extension that does not support it may be missing from checkout or stop it working.

  4. A plugin, theme or security conflict

    Checkout field editors, discount and shipping plugins, script optimisation plugins and old theme templates are frequent causes. The block checkout also needs the WooCommerce Store API, which a security plugin or firewall can block.

  5. Missing shipping zones or methods

    A zone with no methods, or an address outside every zone, produces the message that no shipping options are available.

How to fix it

Find out exactly where checkout fails

Go through an order yourself in a private browser window, logged out, as a customer would, and note the exact message. The point at which it breaks tells you where to look.

  • The basket is empty at checkout, or shows someone else’s items: caching.
  • No payment methods appear: the gateway settings, the shop currency, or a gateway that does not support the block checkout.
  • No shipping options are available: shipping zones.
  • The Place order button spins for ever, or "Something went wrong when placing the order" appears: a PHP error, a conflict or a blocked request.
  • The card is declined or an error appears after Place order: the gateway’s mode, connection and log.
  • Orders stuck on Pending payment after the customer paid: the gateway’s webhooks.

Check whether the shop uses the block or the classic checkout

WooCommerce has two checkouts. Newer shops use the Checkout block. Older shops, and shops that switched back, use the classic checkout, which is a Shortcode block containing [woocommerce_checkout]. Some fixes apply to only one.

  1. Check which page is set as the Checkout page in the Page setup section.Menu: WooCommerce > Settings > Advanced
  2. Open that page in the editor. On a block theme, open it from Appearance, then Editor, then Pages.Menu: Pages > All Pages
  3. Open the List View. A Checkout block means the block checkout. A Shortcode block with [woocommerce_checkout] means the classic checkout.
  4. On the block checkout, click the Checkout block. If an installed extension has declared that it does not support the block checkout, a warning in the settings sidebar names it and offers a one-click switch to the classic checkout.
  5. To switch by hand, select the Checkout block, click the transform button at the left of the block toolbar, choose Classic Shortcode and save. Do the same for the Cart page, because WooCommerce says the two should match.

Before switching, check the payment plugin’s changelog. Updating it to a version that supports the block checkout is often the better fix.

Check the payment gateway settings and test mode

  1. Check the payment method is switched on, then open its settings.Menu: WooCommerce > Settings > Payments
  2. For the WooCommerce Stripe Payment Gateway, open the General section and make sure Enable test mode is off on a live shop.
  3. In Stripe’s Account details section, click Configure connection. In both the Live and Test tabs, Account should say Connected and Webhooks should say Configured. If a webhook is missing or out of date, click Reconfigure webhooks in each tab.
  4. For WooCommerce PayPal Payments, check the shop is connected to your live PayPal account and not in Sandbox Mode.
  5. Log in to your account with the payment provider and look for notices. Providers pause payments when they need identity or business checks.
  6. Confirm the shop currency is one the gateway supports.Menu: WooCommerce > Settings > General

Changing payment settings on a live shop affects real customers straight away. Note the current settings first, and make changes at a quiet time.

Stop caching the cart, checkout and account pages

WooCommerce says to exclude the Cart, Checkout and My account pages from every caching system. Check each layer. WooCommerce notes that some hosts’ server caching does not exclude the account page, and a Cloudflare rule that caches the whole site does not exclude any of them.

  1. In your caching plugin, find the list of pages that are never cached and make sure the cart, checkout and my-account addresses are on it.
  2. WooCommerce also lists cookies that can be excluded, including woocommerce_cart_hash, woocommerce_items_in_cart and wp_woocommerce_session_. Add them if your caching plugin has a setting for cookies.
  3. Ask your host whether server caching is active and whether it excludes these pages.
  4. If you use Cloudflare, check for any cache rule that applies to the whole site and add exceptions for these pages.
  5. Clear every cache, then click Clear transients.Menu: WooCommerce > Status > Tools

Check shipping zones

  1. Open the list of shipping zones.Menu: WooCommerce > Settings > Shipping
  2. Check every place you deliver to has a zone with at least one shipping method in it, for example a United Kingdom zone with a flat rate.
  3. Test with real postcodes, including Northern Ireland or the Highlands if you restrict by postcode.

Test for a plugin, theme or security conflict

  1. Use a staging site if your host offers one, since a live shop will look wrong while you test.
  2. Deactivate plugins other than WooCommerce and your payment gateway, a few at a time, and retry checkout after each group.
  3. Switch briefly to a default theme, such as Storefront or Twenty Twenty-Five, to rule your theme out.
  4. On the classic checkout, check the Templates section at the bottom of the System status report for outdated templates in your theme.Menu: WooCommerce > Status
  5. On the block checkout, check your security plugin or firewall is not blocking addresses beginning /wp-json/wc/store/v1/. The Checkout block places orders through this WooCommerce Store API.
  6. SSL matters too. Check the WordPress Address and Site Address under Settings, then General, both begin with https, and that the browser shows no security warning on checkout.

Read the logs

WooCommerce keeps a separate log for each source under WooCommerce, then Status, then Logs. The fatal-errors log records PHP crashes, which is the usual reason for a Place order button that spins for ever. Payment gateways write their own logs here, and the log usually holds the exact reason a payment was refused. It is the first thing a developer or the gateway’s support team will ask for.

  1. Open the log list and choose fatal-errors or your gateway’s log. Look at the entries from the time of your failed test.Menu: WooCommerce > Status > Logs
  2. In the Stripe plugin, logging is a setting called Log error messages under Advanced settings. Turn it on while you test, then off again.
  3. Other gateways have a similar debug or logging option in their settings.

Place a test order

  1. Create a product at a low price, set its Catalogue visibility to Hidden in the Publish box, and publish it.
  2. Open the product’s address in a private browser window and add it to the basket.
  3. Complete checkout with a real card and a real UK address, so that shipping is tested too.
  4. Confirm the order appears with a status of Processing, and that the customer email and the New order email both arrive.Menu: WooCommerce > Orders
  5. Refund the order from the order screen. Your payment provider may keep its processing fee.
  6. Delete the test product or set it to Draft.

Gateway test mode with the provider’s test card numbers avoids real charges, but while it is on a live shop cannot take real payments, so it suits a staging site better.

If that didn’t work

  1. Payment confirmations not reaching the site

    Orders stuck on Pending payment mean WooCommerce never heard that the payment succeeded, and WooCommerce sends no order emails for them. For Stripe, check the webhook status in Configure connection. For other gateways, check the webhook or notification settings in the plugin and the provider’s dashboard.

  2. The checkout works for you but not for customers

    Test logged out, on a phone using mobile data, and with a different card. Caching, a firewall that blocks some countries or networks, and a gateway’s fraud rules all affect some customers and not others.

  3. Gateway logging switched off

    Some gateways only write a log when logging or debug mode is on. Turn it on, repeat the test order and read the new entries.

When to get help

Ask for help if the gateway log shows errors you cannot interpret, if checkout fails only for some customers or devices, or if finding the conflict would mean switching off plugins on a live shop with no staging site. A broken checkout stops every sale, so it is reasonable to hand it over early.

What a developer would check

  • The gateway and fatal-errors logs from the time of a failed order.
  • Webhook delivery between the payment provider and the site.
  • Caching rules in the plugin, at the host and at any CDN for the cart, checkout and account pages and WooCommerce cookies.
  • Store API requests on the block checkout, outdated template overrides on the classic checkout, and JavaScript errors on the page.

Describe the problem in your own words and WebFixed gives you an instant fixed quote. Nothing is charged until you accept it.

Related questions

Why does my WooCommerce checkout keep loading and never finish?
An endless spinner normally means an error happened in the background after Place order was clicked. A PHP fatal error, a plugin conflict, caching or a blocked Store API request is the usual cause, and the fatal-errors log under WooCommerce, then Status, then Logs, often shows which.
Should I switch from the block checkout back to the classic checkout?
Only if a payment method or extension you need does not support the block checkout and no update fixes it. WooCommerce shows a one-click switch when an incompatible extension is detected. Switch the Cart page as well, so the two match.
Why are orders stuck on Pending payment?
Pending payment means WooCommerce never heard back that the payment succeeded. The customer may have abandoned payment, or the gateway’s confirmation message, called a webhook, is not reaching the site. Check the webhook status in the gateway plugin and the provider’s dashboard.

Written by Michael Broadbridge, Founder of Webgro. First published 21 September 2026. Last checked 14 November 2026 on WordPress 7.1, WooCommerce 11.3.