E-commerce

WooCommerce Checkout Not Working on Mobile: How to Fix It

WooCommerce checkout not working on mobile? Match the symptom (grey button, spinner, missing Apple Pay) to its cause and test fixes safely on a phone.

Table of contents
  1. Quick triage: match the mobile checkout symptom to its cause
  2. Rule out caching and JavaScript optimization first
  3. Exclude cart, checkout and My Account
  4. Turn off minify, combine and delay on checkout
  5. Purge every layer
  6. Payment gateway script conflicts (Stripe, PayPal, Square)
  7. Apple Pay and Google Pay buttons not showing
  8. Theme template overrides and the missing checkout form
  9. Block checkout vs classic shortcode: conflicts and how to switch
  10. Check which one you use
  11. Switch back to classic checkout
  12. Hidden required fields, autofill and iPhone quirks
  13. Test safely on a real phone
  14. Use staging, or troubleshooting mode with care
  15. Remote debug on iPhone
  16. Remote debug on Android
  17. What to look for
  18. Server-side causes: memory, outdated software and firewalls
  19. Checklist to keep mobile checkout working after updates

Desktop orders keep coming in. Then a customer sends you a screenshot. They tapped Place Order on their iPhone and nothing happened, or the button stayed grey, or the spinner never stopped.

When WooCommerce checkout is not working on mobile, the phone is rarely the real cause. Most cases come down to one of six things: a cached or over-optimized checkout page, a payment script that fails to load, a theme template that breaks the checkout form, an extension that doesn’t work with block checkout, a required field the shopper can’t see, or a server or firewall rule blocking the checkout request. Phones make these problems show up sooner. Mobile shoppers are usually logged out and use Safari’s autofill and privacy settings, and they see a different layout than you do in wp-admin.

This guide sorts the fixes by symptom. The steps come from WooCommerce and Stripe’s own documentation, and the guide ends with a safe way to test on a real phone.

Quick triage: match the mobile checkout symptom to its cause

Start by finding out exactly what the shopper saw. Each symptom points somewhere different.

Symptom on the phone Most likely causes Where to start
Place Order button greyed out Card fields never finished loading, payment script blocked by a consent banner or “delay JS” setting, theme rendering a duplicate button Caching, then payment scripts
Button does nothing when tapped Theme template missing the checkout form, JavaScript error from minify/combine, error message hidden off-screen Theme overrides, hidden fields
Endless spinner after tapping A failed checkout request: cached page, firewall block (403), PHP error (500) Caching, then server
Layout broken, button hidden Theme mobile CSS, page-builder checkout template, sticky bars covering the button Theme overrides
Apple Pay / Google Pay missing Domain not registered with Stripe, HTTPS issues, product type or tax settings Express checkout section
“There are no payment methods available” Payment gateway not compatible with the Checkout block Block vs classic section

Two questions help a lot here. Was the shopper logged out? Did it happen on Safari, Chrome or both? A problem that only hits logged-out visitors almost always points to caching or a consent banner.

Rule out caching and JavaScript optimization first

Caching is the cheapest thing to rule out, and it’s a frequent cause of the endless spinner.

Exclude cart, checkout and My Account

WooCommerce’s caching guide says the Cart, Checkout and My Account pages must stay dynamic because they show data specific to each customer. Many caching plugins exclude them by default, but check your settings rather than assuming.

The same guide lists cookies that shouldn’t be cached:

  • woocommerce_cart_hash
  • woocommerce_items_in_cart
  • wp_woocommerce_session_

Check your host’s server cache and your CDN too. WooCommerce’s endless spinner guide says your CDN, firewall and reverse proxy must let WooCommerce AJAX and Store API requests through without serving stored responses. If a checkout request returns only -1, the security token (nonce) check probably failed. A cached, expired or altered nonce is the usual reason.

Turn off minify, combine and delay on checkout

WooCommerce specifically advises WP Rocket users to avoid JavaScript minification. Store owners in WooCommerce theme forums often report checkout and cart breakage when “Delay JavaScript execution” or similar settings are on. Mobile visitors often get hit first, because these features are tuned for mobile speed scores.

Exclude the cart and checkout pages from minify, combine, defer and delay, or switch those features off and retest.

Purge every layer

Clear the plugin cache, the host cache and the CDN cache, then test in a private tab on the phone. If checkout works now, turn optimizations back on one at a time to find the one that breaks it.

Payment gateway script conflicts (Stripe, PayPal, Square)

Stripe, PayPal and Square all load their card fields and buttons with JavaScript from their own servers. If that script is blocked or delayed, the card fields don’t appear and Place Order can stay disabled.

Common causes that come up in WordPress.org support threads:

  • Cookie consent plugins. Some store owners found that the Stripe card fields only appeared after the shopper accepted cookies. Make sure your consent tool treats payment scripts as essential.
  • Problems for logged-out shoppers only. The fields work for you as an admin but not for logged-out shoppers, which usually means caching or optimization.
  • Custom code that removes scripts. One reported case traced it to a single line in a child theme’s functions.php that removed a WordPress core script.
  • A recent gateway update. Several threads describe card fields disappearing right after a payment plugin update.

For the WooCommerce Stripe extension, its troubleshooting doc recommends turning on “Log error messages” in the extension’s Advanced settings before you test. Then reproduce the problem and read the logs under WooCommerce > Status > Logs. Search the log for the order number to follow a single attempt. Other gateways have similar logging options, so check their documentation.

Apple Pay and Google Pay buttons not showing

Express buttons disappear for reasons that have nothing to do with the rest of checkout. According to WooCommerce’s Stripe express checkout documentation, work through these in order:

  1. Go to WooCommerce > Settings > Payments > Stripe > Payment Methods, scroll to Express checkouts, select the methods and click Save changes. Apple Pay and Google Pay can’t be enabled separately.
  2. Confirm the credit/debit card payment method is enabled. The doc says express methods generally don’t work without it.
  3. Confirm your whole site runs on HTTPS with a valid SSL certificate. For Apple Pay, your server also needs port 443 open and TLS 1.2 or later. Your host can confirm both.
  4. Register your domain in Stripe. Open the Payment method domains page, click Add a new domain, enter it and save. Stripe’s domain registration guide says every domain and subdomain must be registered, so add both example.com and www.example.com if shoppers can reach both.
  5. After saving, open the Preview and eligibility section in the Stripe settings. It lists any requirement that isn’t met.
  6. Check the product. The buttons are hidden for some product types, including composite products, products with file upload fields, free products and pre-orders charged on release.
  7. Check your tax settings. On products that don’t need shipping, the buttons are hidden when tax is based on the customer’s billing address. Talk to your accountant before you change how tax is calculated just to show a button.
  8. Check custom required checkout fields. The doc notes that required fields added in code can block express payments on the shortcode checkout.

Also make sure the test phone has a card in Apple Wallet or Google Wallet. Wallet buttons generally only show when the device and browser can actually use them.

Theme template overrides and the missing checkout form

If the button does nothing and the console shows no payment error, look at your theme next.

Go to WooCommerce > Status and scroll to the Templates section. According to WooCommerce’s System Status Report guide, it lists every file your theme overrides, such as checkout/form-checkout.php, and flags outdated ones. An outdated checkout template is a strong lead.

A pattern seen in theme support forums: some themes and page builders build checkout from separate template pieces and never output the main checkout <form> with the checkout woocommerce-checkout class. WooCommerce’s classic checkout script relies on that form. Without it, Place Order has nothing to submit. On some sites this only breaks in the theme’s mobile layout.

To confirm, switch to a default theme such as Storefront or Twenty Twenty-Five on a staging copy and retest on the phone. If checkout starts working, the theme is the cause. Update the theme or contact its developer. WooCommerce’s developer docs explain how to fix outdated templates if you or a developer maintain the overrides yourselves.

For layout problems, check whether a sticky “add to cart” bar, chat widget or cookie banner sits over the Place Order button on small screens.

Block checkout vs classic shortcode: conflicts and how to switch

WooCommerce now offers two checkouts: the Checkout block and the classic [woocommerce_checkout] shortcode. Some extensions only work with one of them.

Check which one you use

WooCommerce’s spinner guide says WooCommerce > Settings > Advanced shows whether your Checkout page uses the block or the classic shortcode. In the page editor, select the Checkout block or one of its inner blocks. If an active extension has declared itself incompatible, you’ll see a warning that names it. According to WooCommerce’s blocks status doc, an incompatible payment gateway may simply not appear. If only incompatible gateways are active, shoppers see “There are no payment methods available.”

Switch back to classic checkout

  1. With a classic theme, go to Pages > All Pages and edit Checkout. With a block theme, go to Appearance > Editor > Pages and edit Checkout.
  2. Open List View and select the Checkout block.
  3. Click Transform in the block toolbar and choose Classic Shortcode.
  4. Click Save.
  5. Repeat on the Cart page, because WooCommerce says the Cart and Checkout blocks work together.

Hidden required fields, autofill and iPhone quirks

On the classic checkout, WooCommerce checks fields when the shopper taps Place Order and shows errors in a notice area. On a phone, that message can end up off-screen or hidden by theme CSS, so the shopper thinks the button is broken.

Things to check:

  • Custom field plugins that hide a field on small screens but still mark it required.
  • Address autocomplete or postcode lookup scripts that fill fields in a way the checkout doesn’t register. Run one test with Safari autofill and one typing by hand. If only the autofill run fails, look at those scripts first.
  • Content blockers and private browsing. WooCommerce’s spinner guide lists ad blockers, consent tools and browser extensions among things that can block checkout scripts.
  • A greyed-out button that never becomes active. Some forum reports trace this to a theme rendering a second, disabled Place Order button. Remote debugging (below) lets you see which button is actually on the page.

Test safely on a real phone

Use staging, or troubleshooting mode with care

The safest place to test is a staging copy. WooCommerce warns that a staging copy can still charge payments and send emails, so put gateways in test mode there.

The Health Check & Troubleshooting plugin’s troubleshooting mode gives you a clean session with plugins disabled and a default theme. It only affects your own login until you turn it off or log out. To use it on mobile, log in to wp-admin on the phone itself. The WordPress.org listing shows the plugin hasn’t been updated in a while and hasn’t been tested with recent WordPress releases, so staging is the better choice when you have it. Tools > Site Health, which is built into WordPress, is still useful for checking PHP and server warnings.

Remote debug on iPhone

Apple’s Web Inspector guide covers the full setup. You need a Mac.

  1. On the iPhone, go to Settings > Apps > Safari > Advanced and turn on Web Inspector (on older iOS: Settings > Safari > Advanced).
  2. On the Mac, open Safari > Settings > Advanced and enable “Show features for web developers.”
  3. Connect the phone by cable and tap Trust if asked.
  4. In Safari on the Mac, open the Develop menu, choose your iPhone, then choose the checkout page.

Remote debug on Android

Per Chrome’s remote debugging docs: turn on USB debugging in the phone’s Developer options. Then open chrome://inspect#devices on your computer, keep “Discover USB devices” checked, connect the phone, accept the prompt and click Inspect next to the tab.

What to look for

In the Console, find the first error, since later ones are often side effects. In the Network tab, filter by Fetch/XHR. Classic checkout uses wc-ajax=update_order_review and wc-ajax=checkout. The Checkout block uses /wp-json/wc/store/ routes. WooCommerce’s spinner guide explains what each response means:

Response What it usually means
Pending / timeout Slow PHP, database, external API or email
403 Firewall or security rule, or expired/missing nonce
404 Wrong URL, rewrite or proxy configuration
500 PHP fatal error; check logs at the same time
HTML or login page instead of JSON Cache, maintenance or security layer, or a redirect
Mixed-content / cross-origin error HTTPS, hostname or www mismatch

If the spinner appears after Place Order, check WooCommerce > Orders before you retry. The order may already exist.

Server-side causes: memory, outdated software and firewalls

Look at the server if the checkout request itself fails:

  • Memory. The WP Memory Limit row under WooCommerce > Status shows your limit. WooCommerce says raising it only helps if the logs show memory exhaustion. Check WooCommerce > Status > Logs, including fatal-errors, for the time of the failure.
  • Outdated software. The status report lists your WooCommerce, WordPress and plugin versions. Update on staging first.
  • Security plugins and firewalls. A 403 on wc-ajax or the Store API often means a rule is blocking it. Ask your host to check web server, firewall and proxy logs.
  • Site address mismatch. Under Settings > General, compare WordPress Address and Site Address with the URL in the failing request, and look for an old domain, a www mismatch or http:// calls. Ask your host before changing these.
  • Slow emails. WooCommerce offers a Deferred emails option under WooCommerce > Settings > Advanced > Features. Only use it if your host confirms transactional email is slowing the request.

Checklist to keep mobile checkout working after updates

  • Cart, Checkout and My Account excluded from page, host and CDN caching
  • Minify, combine and delay JS disabled or excluded on cart and checkout
  • Payment scripts treated as essential in your cookie consent tool
  • Gateway logging switched on before you test changes
  • Every domain variant (www and non-www) registered in Stripe’s Payment method domains
  • No outdated checkout templates under WooCommerce > Status
  • No incompatible extension warnings on the Checkout block
  • Updates applied on staging, with gateways in test mode
  • After every update, one logged-out test order on an iPhone (Safari) and one on Android (Chrome), with autofill and without
  • WooCommerce > Orders checked for duplicates after any failed test

Frequently asked questions

Why does my WooCommerce checkout work on desktop but not on mobile?

Usually the cause isn't the phone itself. It's something that loads differently for mobile visitors, such as a cached mobile version of the page, a delayed or minified script, a theme's mobile layout or a consent banner that blocks payment scripts. Shoppers on phones are also usually logged out and using Safari or Chrome with autofill, which you may not test from your admin account. Test on a real phone while logged out and check the browser console for the first error.

Can caching plugins break WooCommerce checkout?

Yes. WooCommerce's own documentation says the Cart, Checkout and My Account pages must stay dynamic and be excluded from page caching. A cached checkout can serve expired security tokens (nonces), which makes checkout requests fail. JavaScript minification and delay features can also stop checkout scripts from running.

Why is Apple Pay not showing on my WooCommerce checkout?

With the WooCommerce Stripe extension, Apple Pay needs your whole site on HTTPS, card payments enabled and your domain registered on Stripe's Payment method domains page. Stripe says each domain and subdomain has to be registered, including www. The button is also hidden for some product types and for virtual products when tax is based on the billing address. Check the Preview and eligibility section in the Stripe settings to see which requirement is missing.

How do I switch from block checkout back to the classic checkout in WooCommerce?

Edit your Checkout page, open List View, select the Checkout block, click Transform in the block toolbar and choose Classic Shortcode, then save. WooCommerce says you should do the same on the Cart page, because the Cart and Checkout blocks work together. With a block theme, you edit these pages under Appearance > Editor > Pages.

Is it safe to troubleshoot checkout on my live store?

Staging is safer. WooCommerce warns that a staging copy can still charge payments and send emails, so disconnect live gateways or switch them to test mode there. If you must test on the live site, the Health Check plugin's troubleshooting mode only affects your own logged-in session, but test orders can still go through real gateways.

Sources