The mental model: two systems that must agree
Stripe handles the money. WooCommerce handles the order. Webhooks are the messages that keep those two systems in sync — when a payment completes, Stripe sends an event (like payment_intent.succeeded or checkout.session.completed) to a special URL on your site, and the WooCommerce Stripe plugin listens for it and updates the order. If that message fails to arrive, the money side and the store side disagree.
This is why the symptom is so unsettling: the customer was definitely charged, Stripe shows the payment, but WooCommerce acts like nothing happened. Nothing is lost — the two systems just need to be reconnected.
First, get the order status right
Before assuming something is broken, confirm what the status actually means, because “stuck on processing” is often a misunderstanding. Per WooCommerce’s order-status documentation, “Processing” normally means payment was received and the order is awaiting fulfillment — that is success for most physical-goods stores, not a bug.
The genuine red flags are an order stuck on “Pending payment” or “On hold” after Stripe clearly shows a completed charge, or order-confirmation emails never sending. Those point at a webhook that did not land.
Symptoms that point at webhooks
Check webhooks when you see this pattern of money-succeeded-but-order-didn’t.
- Stripe shows a successful charge, but WooCommerce leaves the order on “Pending payment” or “On hold.”
- Order-confirmation and admin emails do not send after payment.
- Subscription renewals or refunds in Stripe do not sync back to WooCommerce.
- The order status simply does not match what the Stripe dashboard says happened.
Step-by-step fix
Work from evidence, not guesses. Stripe keeps a full log of every webhook it tried to send and the response it got back, so you can usually see exactly what failed before you change a single setting.
- Confirm the real payment in the Stripe dashboard — note whether it was a test or live payment.
- Open the Stripe webhooks log and check delivery attempts to your site. A failed delivery (a 4xx/5xx response or timeout) is the smoking gun.
- Confirm the webhook endpoint exists and is reachable, and that its signing secret matches what the WooCommerce Stripe settings expect.
- Make sure you are not mixing modes — a live order needs a live-mode endpoint, not a test-mode one. Mode mismatches are the single most common cause.
- Rule out a security plugin, firewall, or maintenance-mode rule blocking Stripe’s requests from reaching the endpoint.
- Once fixed, use Stripe’s “resend” to replay the failed event, or place a small live test order, and confirm the order completes end to end.
Where the webhook chain breaks — and how to tell
Most stuck orders trace to one of these failure points. Use the Stripe webhooks log to see which.
| Failure point | What you’ll see | How to confirm |
|---|---|---|
| Mode mismatch (test vs live) | Live charges succeed, orders never update. | Endpoint is in the wrong Stripe mode for the payment. |
| Wrong / missing signing secret | Stripe shows delivery, WooCommerce rejects it. | Endpoint returns a signature-verification error. |
| Endpoint blocked | Stripe logs timeouts or 403/503 responses. | A firewall, security plugin, or maintenance mode is blocking the request. |
| No endpoint configured | Stripe has no delivery attempts at all. | No webhook endpoint exists in the Stripe dashboard for your site. |
| Endpoint reachable, order still stuck | Stripe shows 200 OK, order does not move. | A WooCommerce/plugin conflict — check the store logs. |
A real example
A store owner emails in a panic: three customers say they paid, but the orders show “Pending payment” and no confirmation emails went out. Stripe clearly shows three completed charges. Nothing is broken on the storefront — so it looks like the site is fine while three sales sit invisible.
The Stripe webhooks log tells the story in seconds: every delivery to the site is returning a 403. A security plugin updated the night before and started blocking Stripe’s requests. Whitelist the endpoint, resend the three events, and all three orders complete and email out. The fix takes minutes; the danger was that nobody was watching the gap between “paid” and “order recorded.” Missing confirmation emails often share the same root cause — see WordPress not sending emails.
Mistakes that make webhook problems worse
- Assuming the payment failed and re-charging the customer, creating a duplicate charge.
- Mixing live and test API keys or endpoints — by far the most common root cause.
- A security plugin or firewall silently blocking Stripe’s requests to the webhook URL.
- Manually marking orders complete without confirming the real Stripe payment and customer details first.
- Fixing the webhook but never replaying the failed events, leaving earlier orders stuck.
How we keep webhooks from silently breaking
In our experience, webhook failures are sneaky because nothing on the storefront looks wrong — the customer pays, gets a card confirmation from their bank, and assumes all is well, while the order quietly never reaches you. The only reliable defence is monitoring the gap between payments and orders, not the checkout button alone — which is the heart of our WooCommerce maintenance service.
- Re-verify webhook delivery after every WooCommerce, Stripe plugin, PHP, or security-plugin update.
- Keep live and test environments cleanly separated so modes never cross.
- Watch for orders sitting in “Pending payment” longer than expected as an early warning.
- Confirm confirmation emails send, since a missing email often shares the same webhook root cause.
Frequently asked questions.
Can I fulfil an order if Stripe was paid but WooCommerce is stuck?
Yes, but confirm the real payment and customer details in the Stripe dashboard first, then fix the webhook so the store record catches up. Do not re-charge the customer — the money is already taken.
Does “processing” mean my order is broken?
Usually not. In WooCommerce, “Processing” normally means payment was received and the order is awaiting fulfilment. The real warning sign is an order stuck on “Pending payment” or “On hold” after Stripe shows a completed charge.
Are Stripe webhook issues common?
Yes — they are one of the most common WooCommerce payment support issues, because several systems have to agree. Mode mismatches and blocked endpoints account for most cases.
How do I test a Stripe webhook?
Use the Stripe dashboard to inspect the webhook’s delivery log and resend a recent event, or place a small live test order and confirm the order completes end to end. Stripe records every attempt and the response your site returned.
Research sources.
This guide was checked against current platform and search documentation before publication.