•

Customer paid, but the order is missing or stuck on pending

This is one of the most stressful shop problems, because a customer has paid and you can’t see what for. They email asking where their order is, and you have nothing to show them. The order usually does exist somewhere, or can be pieced together from the payment, so nothing is lost. But it needs sorting out properly, because while the cause is there, it will keep happening.

Is this what you’re seeing?

  • Customers are being charged, but no WooCommerce order is created.
  • Your WooCommerce order status isn’t updating after payment: it stays on “Pending payment”.
  • Orders are marked “Failed” or “Cancelled”, but Stripe or PayPal shows the payment as successful.
  • Customers say they paid and never got a confirmation email.
  • The connection between WooCommerce and Stripe webhooks seems to be broken, or Stripe has emailed you about failed webhook deliveries.
  • It only happens to some customers, often those paying by PayPal or with a card that asks for extra security checks.

What usually causes it

The payment provider’s webhooks aren’t getting through

A webhook is a message your payment provider sends to your site in the background to say “this payment succeeded”. WooCommerce relies on it, especially when the customer leaves your site to approve a payment. If the message is sent to the wrong address, rejected because the secret key that signs it doesn’t match, or blocked by a firewall, the payment succeeds and the order never hears about it. This often starts after a move to a new domain or host, a switch to https, a change of keys, or a new security plugin. How to tell: in the webhooks section of the Stripe dashboard, look at the endpoint for your site. Check that its address is your live site, exactly, and look at recent deliveries for failures and the error each one got. PayPal has its own webhook settings in its developer area.

The webhooks are going to another copy of your site

A staging or development copy that uses your live payment keys can take over the webhook settings, or a webhook can still point at an old domain. Payments are confirmed to the wrong site, and the live one waits forever. How to tell: the webhook address in Stripe isn’t your live domain, or there’s more than one endpoint and you don’t recognise them all.

The customer didn’t come back to your site

With PayPal, and with cards that ask for a security check from the bank, the customer pays on another page and is then sent back to your site. If they close the tab before that, the order relies entirely on the webhook. When webhooks are working, nobody notices. When they aren’t, only these orders get stuck, which is why it can look random. How to tell: the stuck orders are mostly PayPal, or card payments that needed an extra check, and the rest are fine.

WooCommerce gave up waiting and cancelled the order

WooCommerce cancels unpaid orders after the “Hold stock” time in its inventory settings. If the payment confirmation arrives late, the order may already be cancelled, or it may be marked Failed after a payment that went through on a second attempt. How to tell: the order notes say “Unpaid order cancelled – time limit reached”, or show a failed attempt followed by nothing.

Something crashed just after the payment

Once a payment is confirmed, WooCommerce updates the order, reduces stock and sends emails, and other plugins join in. If one of them hits a fatal error at that moment, the payment is taken but the order is left half updated. How to tell: customers saw an error page after paying. Check WooCommerce → Status → Logs for a fatal error at the time of a stuck order.

What you can safely try

Take a backup first. Don’t refund, delete or recreate orders until you’ve matched everything up.

  1. List the payments in Stripe or PayPal for the affected period, with each customer’s email and amount. Then find the matching order in WooCommerce → Orders. Note any payment with no order, and any order whose status doesn’t match its payment.
  2. Open a few stuck orders and read the order notes. They show what WooCommerce last heard and when.
  3. Check the webhook endpoint and recent deliveries in your Stripe dashboard, or PayPal’s webhook settings. The date failures started is a strong clue to what changed.
  4. Open your payment plugin’s settings under WooCommerce → Settings → Payments. Many, including recent versions of the WooCommerce Stripe plugin, show whether webhooks are set up. Turn on the plugin’s logging if it has a setting for it.
  5. Check WooCommerce → Status → Logs for your payment plugin’s log and any fatal errors around the times of stuck orders.
  6. If you use a security plugin or Cloudflare, check its log for blocked requests at those times.
  7. Once you’re sure an order really has been paid, you can change its status to Processing yourself, and add an order note with the payment reference. Do it once: changing statuses back and forth can send repeat emails and, on some ticketing setups, create duplicate tickets.

When to stop and get help

  • Webhooks are failing and you can’t see why, or fixing the address didn’t help.
  • You have more than a handful of payments you can’t match to orders.
  • Customers may have paid twice because their first attempt looked as if it failed.
  • The orders are for subscriptions, memberships or tickets, where a stuck order also means someone can’t get in. Subscription renewals have their own causes, covered in subscriptions not renewing.
  • It’s happening now, on most orders, and you’re taking money you can’t account for.

A real example

What I find most often is that something changed on the site weeks before anyone noticed: a move to a new host or domain, new payment keys, a staging copy, or a firewall rule. From that day, the payment provider’s messages stopped being accepted.

The shop seemed fine, because most card payments are confirmed while the customer is still on the checkout page. Only the orders that depended on the webhook got stuck, usually PayPal and cards with extra security checks, so it looked random and was easy to put down to customers. The payment provider’s delivery history usually shows the day it started, and that points to the change that caused it.

The fix itself is often small. The careful part is the tidying up: matching every payment to an order, completing the ones that were paid, and making sure nobody was charged twice or missed out on what they bought.

Getting it fixed

I’ll match your payments to your orders, find out why the confirmations aren’t getting through, fix it, and test it with a real payment. You’ll get a list of the orders affected, so you can tell those customers where they stand. See WooCommerce support for the other shop problems I fix. 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 pay or orders aren’t coming through right now, see emergency WordPress support for a faster start.

Questions

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. The payments can be matched up with customers, and the cause fixed so it doesn’t happen again.

An order says Failed, but the customer was charged. Can I fix that order?

Yes. Check the payment in your provider’s dashboard first, including the amount. If it’s genuinely paid, change the order to Processing and add a note with the payment reference. Check the stock levels afterwards, because a failed or cancelled order may have put its stock back.

Stripe says my webhook is failing. What does that mean?

Stripe tried to tell your site about a payment, and your site didn’t accept the message. The error on each delivery says why: the address may not exist, a firewall may have blocked it, or the signing secret may not match what your Stripe plugin expects. Stripe keeps retrying for a while, so once it’s fixed, some of the stuck orders may update by themselves.

Will the customer get their confirmation email if I change the status myself?

Usually, yes. Moving an order to Processing sends the customer’s “processing order” email if it’s switched on under WooCommerce → Settings → Emails. If your emails aren’t arriving at all, that’s a separate problem: see why WordPress emails don’t arrive.

Is this the same as the checkout not working?

Not quite. Here, customers can pay, and the problem is afterwards. If they can’t get through the checkout at all, see WooCommerce checkout not working.

Written by Peter Claridge, who fixes WordPress sites for businesses across the UK from Reading. Last checked on WordPress 7.1, November 2026.