Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Troubleshooting · Troubleshooting

How to Fix Orders Stuck on Pending Payment in WooCommerce

Short answer

Pending payment means WooCommerce has the order but no payment confirmation yet, so first check whether the customer actually paid in your gateway dashboard. If they paid, the gateway's webhook or callback never reached your store, so check the order notes, the gateway logs, and the webhook delivery list. If they never paid, the order will cancel itself once the Hold stock timer runs out.

Key takeaways

  • Pending payment means the order arrived but no payment has been confirmed yet.
  • Check the gateway dashboard first: if the money is there, the webhook never arrived.
  • Missing order notes are a clue that the gateway failed to report back.
  • WooCommerce recommends a 60-minute Hold stock timer for unpaid orders.
  • Stripe for WooCommerce needs webhooks configured by hand.

What does “Pending payment” mean in WooCommerce?

Pending payment means WooCommerce received the order but payment has not yet been confirmed.

WooCommerce's order troubleshooting guide defines the status this way. It is the normal first step for every online order: the customer places the order, WooCommerce creates it as Pending payment, and the gateway then confirms the money.

Most gateways move the order to Processing on their own once payment clears. If the order sits on Pending payment for hours, either the customer never finished paying or the confirmation never reached your store. Those two cases need very different fixes, so find out which one you have before changing anything.

Offline methods are the exception. Orders paid by Direct Bank Transfer (BACS) or check stay On Hold until you verify the money arrived and move the order yourself, as WooCommerce's order troubleshooting guide explains. That is expected behaviour, not a fault.

Did the customer actually pay?

Open your payment gateway dashboard and search for the order number, amount, and customer email before doing anything else.

If no payment exists there, the customer never finished paying. They may have closed the payment page, had a card declined, or hit a failed 3D Secure check. The order is safe to leave alone, and WooCommerce will cancel it when the Hold stock timer ends.

If a payment does exist, do not ask the customer to pay again. You already have their money, and a second charge creates a refund job. The problem is the message that should have told your store about the payment, which is covered in the webhook section below.

Check the order's General details section too, since it shows the payment method and transaction ID after the order number. WooCommerce's order troubleshooting guide points to this section first when working out which gateway handled an order.

What should I check in the order notes?

Read the order notes panel on the order screen, since it records every status change, gateway message, and error with a timestamp.

WooCommerce's order troubleshooting guide says order notes can reveal insufficient funds, expired cards, authentication failures, and gateway timeouts. Look for entries with error codes or decline reasons from your gateway.

Missing notes are a clue on their own. If a paid order has no payment notes at all, the gateway most likely failed to talk back to your store, or the payment process stopped before it finished. WooCommerce's order troubleshooting guide states this directly.

Also check whether the notes show an authorization without a capture. Some gateways can be set to Authorize only, which places a hold on funds but moves no money until you capture the charge. WooCommerce's order troubleshooting guide warns that Authorize and Capture must both be set, or the order stays unpaid.

What the notes showWhat it meansNext step
Decline reason or error codeBank or gateway refused the paymentTell the customer the reason and let them retry
Authorized but not capturedFunds held, money not takenCapture the charge in the gateway dashboard
No payment notes at allGateway never reported backCheck webhooks and gateway logs
Payment confirmed, status unchangedConfirmation lost on the way backCheck webhook delivery and update the status by hand

How do I fix a missed webhook?

Open the webhook or event delivery list in your gateway dashboard and look for the failed delivery for that payment.

A webhook is a real-time message your gateway sends your store when a payment status changes. WooCommerce's order troubleshooting guide explains that some gateways need webhooks set up by hand, while others handle it automatically. Stripe for WooCommerce is the named example that needs manual webhook configuration.

Stripe's webhook documentation explains that Stripe sends event notifications to an endpoint URL your store registers. In the Stripe dashboard, open Developers > Webhooks, pick the endpoint, and check the delivery list for the payment. A 403, 404, or 500 response tells you where to look next.

A 403 usually means a firewall is blocking the gateway, such as a security plugin, a host firewall, or a Cloudflare rule. A 404 means the endpoint URL is wrong or the store moved.

Fix the cause, then reconfigure the webhook in the gateway settings. WooCommerce's order troubleshooting guide links to the Stripe webhook setup steps for stores that need to reconfigure.

If you use WooPayments, check its connection status in WooCommerce > Settings > Payments first. Our guide What Is WooPayments? explains how the built-in gateway connects to your store.

For a side-by-side look at the two main options, see WooPayments vs Stripe for WooCommerce.

What if I still use PayPal Standard?

If PayPal shows the payment but the order stays pending, your PayPal IPN setup is failing.

PayPal Standard is deprecated and hidden by default in WooCommerce. It confirms payments through PayPal Instant Payment Notifications (IPN), and WooCommerce's order troubleshooting guide is direct about the symptom: if you are getting payments but orders stay pending, the IPN is failing.

In your PayPal account, set the IPN URL to https://example.com/?wc-api=WC_Gateway_Paypal, with your own domain in place of example.com, and make sure receiving IPN messages is switched on. Then place a test order and watch the order notes for the payment confirmation.

The better fix is to move to the current PayPal Payments plugin, since PayPal Standard will not be supported forever. Migrate on a staging site first and confirm a test payment updates the order status before switching the live store.

How do I stop paid orders from being cancelled while I investigate?

Raise the Hold stock timer at WooCommerce > Settings > Products > Inventory so unpaid orders are not cancelled before you finish checking them.

WooCommerce recommends 60 minutes for the Hold stock setting, according to WooCommerce's order troubleshooting guide. When the limit is reached, WooCommerce cancels eligible pending orders and releases their stock. That is useful for abandoned carts, but it can cancel a paid order whose confirmation is stuck.

Set the timer to 120 minutes or more while you work through a webhook problem, then put it back when the fix is in. The setting only holds stock for orders in Pending payment status, not for orders On hold.

The cancellation runs as a background job in Action Scheduler, the queue bundled with WooCommerce. If the queue itself is stuck, unpaid orders pile up instead of cancelling.

Our guide on how to fix past-due actions in the WooCommerce Action Scheduler covers that case. WP-Cron runs scheduled events when the site gets visits, so a quiet store can also run the sweep late.

How do I move a paid order to Processing by hand?

Once you confirm the money in the gateway dashboard, change the order status to Processing in the order screen and add a private note explaining why.

Do this only after you confirm the payment exists. Changing the status does not take money, so it cannot fix an unpaid order. It only corrects the record for an order that is already paid.

Open the order, use the Status dropdown in the top-right box, pick Processing, and click Update. Add a note such as "Payment confirmed in Stripe, webhook failed, status updated by hand" so your team knows what happened. Then fulfil the order as normal.

Note that Processing does not move to Completed on its own. WooCommerce's order troubleshooting guide states that you update the status to Completed after shipping, except for orders with only virtual and downloadable products, which complete automatically.

How do I confirm the fix worked?

Place a test order with the gateway in test mode, then confirm the order moves from Pending payment to Processing without help.

Turn on logging in the gateway settings first, place the test order, then read the new entries at WooCommerce > Status > Logs. WooCommerce's order troubleshooting guide notes that logging only captures new transactions, so old failures will not appear there.

Check three things on the test order: the payment appears in the gateway dashboard, the order notes show the confirmation, and the status changes to Processing. If all three happen, the webhook link is fixed. Repeat the test with a small live payment before telling customers the problem is solved.

Read the System Status report too, since it lists your WooCommerce version and server setup in one place. Our guide on how to read the WooCommerce Status Report explains what each section means.

What mistakes should you avoid?

The most common mistake is asking a customer to pay again before checking the gateway dashboard.

  • Asking a customer to pay twice when the first payment already went through.
  • Shipping an order that is still Pending payment without confirming the money first.
  • Changing the status to Processing for an order with no payment record.
  • Turning the Hold stock timer off entirely, which lets unpaid orders hold stock forever.
  • Editing gateway credentials on the live store without testing in test mode first.
  • Ignoring missing order notes, which are themselves evidence that the gateway never reported back.

Frequently asked questions

Is an order stuck on Pending payment always a bug?

No. Pending payment means no payment has been confirmed, so it is the normal state for an unpaid order. It only becomes a problem when the customer paid and the order still does not move, which points to a missed webhook or callback.

Why do some orders stay on Pending payment for days?

The customer may have abandoned checkout, or the card was declined. If the payment never happened, WooCommerce cancels the order when the Hold stock timer ends. You can also cancel it by hand from the order screen.

Can I change a paid order from Pending payment to Processing myself?

Yes, if you confirmed the payment in your gateway dashboard. Change the status to Processing in the order screen and add a private note explaining that the webhook failed. Do not change the status for an order with no payment record.

How long does WooCommerce wait before cancelling an unpaid order?

Check the Hold stock setting under WooCommerce > Settings > Products > Inventory. WooCommerce recommends 60 minutes. When the timer ends, eligible pending orders are cancelled and their stock is released.

What is the difference between Pending payment and On hold?

They are different. Pending payment means the order was received and no payment has been confirmed. On hold means payment is waiting for confirmation, such as a bank transfer you must verify by hand, or an authorization that still needs to be captured.

Sources

  1. Troubleshooting Orders WooCommerce
  2. Troubleshoot payment errors WooCommerce
  3. Webhooks Stripe
  4. Action Scheduler WordPress.org
  5. WP-Cron WordPress Developer Resources

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test