A customer's bank statement shows the charge. Stripe's dashboard shows the payment as succeeded. But your WooCommerce orders list shows nothing — no Pending order, no Failed order, nothing at all. The sale simply doesn't exist on your end.
This is almost always a webhook failure. Stripe successfully processed the payment and tried to tell your WooCommerce store about it — but that notification never arrived, or arrived and failed to process. The money moved. Your store just doesn't know it happened.
Why this happens: how Stripe and WooCommerce actually talk to each other
WooCommerce doesn't watch your Stripe account continuously. Instead, Stripe sends your store a webhook — an automated HTTP request — every time something happens: a payment succeeds, fails, gets refunded, and so on. Your WooCommerce store listens for these requests and creates or updates orders based on what they say.
If that webhook never arrives, or arrives but your server rejects it, WooCommerce has no way of knowing the payment happened. From Stripe's side, everything worked perfectly. From your store's side, nothing happened at all.
The most common causes
If your SSL certificate expired or is misconfigured, Stripe's webhook delivery will fail outright. Stripe requires a valid HTTPS endpoint to deliver webhooks.
Firewall or security plugins like Wordfence sometimes block incoming requests that look automated — including legitimate Stripe webhooks — especially after a plugin update changes its default rules.
If your site moved from http to https, changed domains, or the Stripe plugin was reconfigured, the webhook endpoint registered in your Stripe dashboard may be pointing at an outdated URL.
If your server takes too long to respond to the webhook request — often due to slow hosting or a heavy plugin stack — Stripe may consider the delivery failed even though your server eventually processed it.
Stripe signs every webhook with a secret key. If the signing secret in your WooCommerce Stripe settings doesn't match what's in your Stripe dashboard, your server will reject the webhook as invalid.
How to diagnose it right now
Go to your Stripe Dashboard → Developers → Webhooks and click on the webhook endpoint connected to your store. Stripe logs every single delivery attempt, whether it succeeded, and the exact HTTP response code your server returned.
- If you see failed attempts with a 4xx response — usually a security plugin or authentication issue blocking the request.
- If you see failed attempts with a 5xx response or timeout — usually a server performance or hosting issue.
- If you see no delivery attempts at all — the webhook URL is likely misconfigured or pointing somewhere that no longer exists.
Cross-check this against WooCommerce → Status → Logs, filtered to your Stripe log. If webhook entries simply stop appearing at a certain point, that confirms the delivery is failing before it reaches WooCommerce at all.
If you have a customer with a confirmed charge in Stripe but no WooCommerce order, manually create the order so they get what they paid for — don't make them wait while you debug the underlying webhook issue. Fix the cause separately so it doesn't happen to the next customer.
The real risk: this can run for days unnoticed
The dangerous part of webhook failures isn't any single missed order — it's that they tend to fail silently and consistently once broken. If your SSL certificate lapses or a security plugin update blocks Stripe's requests, every single payment from that point forward creates this exact problem, and there's no alert anywhere telling you it's happening.
Most store owners discover this days later — either a customer emails asking where their order is, or they notice their order count looks unusually low for the revenue they're seeing in Stripe directly.
This is exactly the gap ZextaPay is built to close. It monitors the actual transaction flow between your gateway and your store in real time, so a webhook failure shows up as a flagged issue within minutes — not days later when a customer notices first.
Catch webhook failures before customers do
Free WooCommerce plugin. Live dashboard, gateway health monitoring, plain-English error explanations.
Install ZextaPay freeFrequently asked questions
Why did Stripe charge my customer but WooCommerce shows no order?
This is almost always a webhook delivery failure. Stripe processes the payment successfully and tries to notify your WooCommerce store via a webhook, but the notification never arrives or fails to process — so WooCommerce never creates the order even though the customer was charged.
How do I check if my Stripe webhooks are failing?
Go to your Stripe Dashboard, then Developers → Webhooks, and click on the endpoint connected to your WooCommerce store. Stripe shows every delivery attempt and whether it succeeded or failed, along with the HTTP response code your server returned.
What should I do with a customer who paid but has no order?
First confirm the charge in your Stripe Dashboard under Payments. If it shows as succeeded, manually create the WooCommerce order for that customer so they receive their product or service, then fix the underlying webhook issue so it doesn't happen again.