Customers can’t pay at checkout? How to find the cause

Place order spins, cards fail, or Apple Pay refuses? A calm, step-by-step way to find out whether the problem is the shopper’s bank, your payment provider or your site.

“Something went wrong.” “Error processing payment.” A Place order button that spins forever. When checkout breaks, every hour costs sales, so it’s tempting to start switching things off. Don’t. Work out where the payment stops first. That usually takes ten minutes.

New to fixing things yourself? Read the 10 rules we follow before touching a live store first.

1. See it for yourself

  1. Open a private or incognito window and stay logged out.
  2. Add a cheap product to the cart and go all the way to the last step.
  3. Write down the exact error message, word for word, and the time.

2. Read the failed order

  1. Go to WooCommerce → Orders and open a failed or pending order.
  2. Read the Order notes on the right-hand side.
  • A note like “declined” or “insufficient funds” means the shopper’s bank said no. That’s normal and not a fault on your site.
  • No payment note at all means the attempt never reached your payment provider.

3. Check your payment provider’s dashboard

  • The attempt isn’t there: the problem is on your site, usually a plugin, cache or script.
  • The attempt is there and succeeded: the money was taken but the order wasn’t updated. This is usually a webhook problem. Check your provider’s webhook or event log for failed deliveries.

4. Check the payment settings

Go to WooCommerce → Settings → Payments and confirm:

  • The method is enabled and connected.
  • It’s in live mode, not test mode.
  • Only one plugin handles each provider. Two Stripe plugins active at the same time can break both.

5. Read the logs

Go to WooCommerce → Status → Logs. Use Filter by log source to open the log named after your payment plugin, and the fatal-errors log if there is one, around the time of the failed attempt.

6. Think about what changed

Most checkout failures follow a recent change. The usual suspects:

  • A new CAPTCHA, anti-fraud or security plugin
  • A multi-currency plugin that hides payment methods for some currencies
  • A page builder or theme customisation of the checkout page
  • A discount, quantity or order-status plugin
  • Caching or “optimise JavaScript” settings

7. Rule out caching

Make sure the cart, checkout and my-account pages are never cached, and that payment scripts are excluded from any “combine”, “defer” or “delay JavaScript” settings.

8. Only Apple Pay or Google Pay fails?

Look for extra required checkout fields. Wallet payment sheets can’t fill custom required fields, so the last step gets refused. Make the field optional or remove it.

9. Find a plugin conflict safely

Install the free Health Check & Troubleshooting plugin and turn on troubleshooting mode. Leave only WooCommerce and your payment plugin active, try a test order, then add the others back one at a time. Customers are not affected while you do this.

A related one: customer charged twice

This is almost always a shopper paying again while the first attempt was still processing, often on a slow site. Find both charges in the provider dashboard and refund the one that isn’t linked to an order. Then look at your site speed.

Stop and get help if

  • Payments were taken but the orders show as failed. Reconcile with your provider before refunding anything.
  • You’d need to edit payment plugin code or share API keys.
  • You suspect unfamiliar code on your checkout page. Card-skimming scripts are real, and need a proper clean-up.