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 Stripe Webhook Errors in WooCommerce

Short answer

To fix Stripe webhook errors in WooCommerce, open WooCommerce > Settings > Payments > Stripe > Settings, then Account details > Configure connection, and confirm both the Live and Test tabs say the webhook status is Configured. If a delivery fails with a 400, copy the signing secret from the endpoint in the Stripe dashboard and paste it into the settings, making sure the test and live secrets are not mixed up. If the status is not Configured, click Reconfigure webhooks in each tab and delete any duplicate endpoint.

Key takeaways

  • Since version 8.6.1, the Stripe extension sets up webhooks automatically when you connect to Stripe.
  • A 400 on every delivery usually means the signing secret does not match the endpoint in the same mode.
  • Orders stuck on Pending payment while Stripe shows a paid charge point to a webhook that never arrived.
  • Reconfiguring webhooks creates a new endpoint and removes the extension's old ones, but not endpoints you added yourself.
  • Stripe retries undelivered events for up to three days, but a secret mismatch will fail on every retry.
  • Versions 11.2.0 and 11.1.2 of the Stripe gateway, released in November 2026, address security issues.

What is a Stripe webhook in WooCommerce?

A Stripe webhook is a message Stripe sends to your site when a payment changes after checkout, so WooCommerce can update the order without the customer staying on the page.

Your store talks to Stripe through its API when a customer pays, while Stripe talks back through webhooks. WooCommerce's Stripe setup guide explains that webhooks confirm payments that finish after the customer leaves checkout, such as 3D Secure checks and Stripe Link payments (Stripe webhooks).

Without a working webhook, a payment can succeed at Stripe while the order stays stuck in WooCommerce. That gap is the most common sign of a webhook problem, and it is also why webhook errors deserve a fix rather than a manual order update.

If you are still choosing a payment gateway, WooPayments vs Stripe for WooCommerce compares the two options side by side.

WooPayments is a separate gateway from the Stripe extension, so its webhook setup works differently. See What Is WooPayments? A Plain Explanation before mixing up the two setups.

What causes Stripe webhook errors in WooCommerce?

Most Stripe webhook errors come from a wrong signing secret, a test-mode secret used on a live endpoint, a blocked endpoint URL, or a PHP error in the webhook handler.

  • Wrong signing secret: the secret saved in WooCommerce does not match the endpoint in the Stripe dashboard, so the signature check fails on every event.
  • Test and live modes mixed up: a test-mode secret sits on a live endpoint, or the reverse, because Stripe objects are scoped to one account and one mode.
  • Blocked endpoint: a security plugin or firewall stops Stripe's POST request before WooCommerce sees it.
  • PHP fatal error: broken code in the webhook handler returns a 500 status, so Stripe marks the delivery as failed.
  • Old extension version: WooCommerce released Stripe gateway versions 11.2.0 and 11.1.2 in November 2026 to address security issues, so update before you chase other causes (security update).

Stripe allows up to 16 event destinations, so a store with several integrations can run out of room and needs to clean up old endpoints (webhook docs).

How do you check your webhook status in WooCommerce?

Open WooCommerce > Settings > Payments > Stripe > Settings, then Account details > Configure connection, and check that both the Live and Test tabs say the webhook status is “Configured”.

Since version 8.6.1 of the Stripe extension, webhooks are set up automatically when you connect to Stripe, so a missing endpoint on a newer install points to a setup problem rather than a missing step (Stripe webhooks).

Each time the extension updates, it checks the live and test webhooks, creates a missing one, and replaces an outdated one. It skips this only when the signing secret was set by hand, or when the saved webhook points to a different site's URL, such as staging.

What does each Stripe delivery error code mean?

The HTTP status on each delivery in the Stripe dashboard points to the cause: 400 means a secret mismatch, 404 means a wrong URL, and 500 means a PHP error on your site.

StatusWhat it meansFirst fix
400Signing secret mismatchMatch the secret to the endpoint in the same mode
401 or 403Secret mismatch or a blocked requestCheck the secret, then check security plugins and the firewall
404Wrong endpoint URLReconfigure webhooks and check the URL format
500PHP fatal error in the handlerCheck WooCommerce logs and wp-content/debug.log
No delivery at allWebhook missing or endpoint not publicCheck webhook status and confirm the URL is public HTTPS

Orders stuck on “Pending payment” while Stripe shows a successful charge mean the webhook never arrived or was rejected. Check the delivery list in the Stripe dashboard before changing settings, since the status there shows whether Stripe even tried.

How do you fix a signing secret mismatch?

Copy the signing secret from the exact endpoint shown in the Stripe dashboard for the same mode, live or test, and paste it into the matching field in the Stripe gateway settings.

Every webhook endpoint has a signing secret that starts with whsec_, and Stripe signs each event and sends the signature in the Stripe-Signature header (webhook docs).

Stripe's webhook docs name the wrong endpoint secret as the most common cause of the “Webhook signature verification failed” error, so check the secret before changing anything else.

Do not mix secrets between endpoints: CLI-forwarded and dashboard-managed endpoints have different secrets, and Stripe's endpoint guide warns against swapping them (manage endpoints).

Test and live objects are scoped to one account and one mode, so a test-mode PaymentIntent is invisible to a live key. Always match the secret, the endpoint, and the mode together, and never paste a test secret into the live field.

How do you reconfigure webhooks in WooCommerce?

On the same Configure connection screen, click “Reconfigure webhooks” in the Live tab and again in the Test tab to make the extension create fresh endpoints with new signing secrets.

Reconfiguring creates a new endpoint and removes endpoints the extension created before, but it does not remove endpoints you or another service added (Stripe webhooks).

If you added your own endpoint at the extension's URL, delete it in the Stripe dashboard after reconfiguring. The extension now uses the new endpoint's signing secret, so events sent to your old endpoint will fail verification.

The extension only uses endpoints in this format: https://www.example.com/?wc-api=wc_stripe, with your own domain in place of the example. Any endpoint with a different path is not the extension's endpoint.

How do you fix a webhook blocked by a security plugin or firewall?

Allow POST requests to /?wc-api=wc_stripe through your security plugin and firewall, and check that the endpoint is a public HTTPS URL, since Stripe cannot reach a local or password-protected address.

Stripe's webhook docs state that endpoints must be publicly accessible HTTPS URLs, and that Stripe supports only TLS 1.2 and 1.3 for webhook deliveries (webhook docs).

Stripe publishes the IP addresses its webhook notifications come from, and the list has 15 addresses as of November 2026. If your firewall blocks by IP, allow that list from Stripe's IP page instead of opening the endpoint to every address.

Security plugins sometimes block the request even when the firewall allows it, so test with the plugin paused for one delivery before changing its rules for good.

How do you confirm the fix worked?

Place a live test order, then check that the order moves to Processing on its own and that the endpoint shows a fresh 200 delivery in the Stripe dashboard.

Turn on “Log debug messages” in the Stripe gateway settings, then open WooCommerce > Status > Logs and read the woocommerce-gateway-stripe log to see what the handler received and returned.

The WooCommerce status report gathers your PHP version, plugin versions, and log paths in one place, which helps when a 500 points to a server problem rather than the gateway. See How Do You Read the WooCommerce Status Report?.

If the order still lags after the webhook returns 200s, check the Action Scheduler queue, since WooCommerce runs background jobs through it. See How to Fix Past-Due Actions in the WooCommerce Action Scheduler.

Stripe retries undelivered events for up to three days, so a short outage can still clear on its own, but a 400 or 500 on every delivery will not fix itself (webhook docs).

Stripe advises handlers to return a 2xx status fast, before running slow work, because a handler that times out looks like a failure even when the payment is fine.

When should you contact your host or Stripe support?

Contact your host when the endpoint returns 500s, the PHP error log shows a fatal error, or the webhook URL is unreachable from outside your network.

Contact Stripe support when the dashboard shows deliveries leaving Stripe with 2xx responses yet WooCommerce never updates, since the fault then sits between delivery and your handler. Give support the event ID and the delivery attempt time from the dashboard.

Update the Stripe extension first: WooCommerce released versions 11.2.0 and 11.1.2 in November 2026 to address security issues, and support will ask whether you run a patched release (security update).

What mistakes should you avoid?

Avoid these six slips, since each one can keep a fixed webhook broken or hide the next failure.

  • Pasting a test secret into the live settings, or the reverse.
  • Deleting the extension's active endpoint in the Stripe dashboard while leaving the old secret in WooCommerce.
  • Adding a second manual endpoint at the same URL after reconfiguring.
  • Marking orders as Processing by hand instead of fixing the webhook, which hides the next failure.
  • Testing only in test mode and never placing a live order.
  • Ignoring 400s because the payment still arrived, since refunds and disputes also depend on webhooks.

Refunds, disputes, and subscription renewals also arrive through webhooks, so a broken endpoint affects more than new orders. Fix the endpoint first, then recheck the orders that were stuck.

Frequently asked questions

Can I mark stuck orders as Processing by hand instead of fixing the webhook?

You can, but it only hides the fault. The webhook stays broken, so the next payment, refund, or dispute will hit the same problem. Fix the endpoint and the signing secret first, then update any orders that were stuck while the webhook was down.

Do I need webhooks if I only take simple card payments?

Simple card payments that finish on the checkout page can work without a webhook, but payments that finish later still need one. That covers 3D Secure checks, Stripe Link, and any payment method where the customer leaves checkout before the charge completes.

Why does my webhook work in test mode but not in live mode?

Test and live modes use separate endpoints and separate signing secrets, and Stripe objects are scoped to one account and one mode. A test secret pasted into the live settings will fail every live delivery, so check the webhook status and the secret in each tab on its own.

How long does Stripe keep retrying a failed webhook delivery?

Stripe retries undelivered events for up to three days. A short outage can clear on its own through retries, but a signing secret mismatch or a 500 error will fail on every retry until you fix the cause, so do not wait out a repeated 400 or 500.

Is it safe to delete a webhook endpoint in the Stripe dashboard?

Delete only endpoints you added yourself, or the extension's old endpoints after reconfiguring. Deleting the active endpoint that the extension uses will stop WooCommerce from hearing about payments, so confirm which endpoint is live in the Configure connection screen before you delete anything.

What should I do if my webhook URL changed after moving my site?

Open WooCommerce > Settings > Payments > Stripe > Settings, then Account details > Configure connection, and click Reconfigure webhooks in the Live tab and the Test tab. The extension creates fresh endpoints at the new domain and removes its old ones, so check that both tabs say Configured afterwards.

Sources

  1. Stripe Webhooks WooCommerce
  2. Webhooks Stripe
  3. Manage webhook endpoints Stripe
  4. Stripe Gateway Security Update WooCommerce Developer Blog
  5. Domains and IP addresses Stripe

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