What happened
With WooCommerce PayPal Payments, the payment is taken while the customer is still at checkout, and the order moves to Processing straight away. PayPal also sends the store a short message about each payment, called a webhook. The order does not wait for it, which is why a store can lose its webhooks and not notice.
The webhooks matter for what happens after checkout. When PayPal holds a payment for review, the order waits On hold until a webhook says it went through. When a customer approves the payment in PayPal but closes the window before getting back to the store, the webhook is how the plugin finishes the order and takes the money. Refunds and disputes made in PayPal also reach WooCommerce by webhook.
At 13:40 one of the owners updated the store’s security plugin from 6.1 to 6.2. The new version blocked requests that do not come from a browser, and PayPal’s webhooks were among them. Every webhook from then on was refused before WordPress could read it.
Customers kept paying, orders kept arriving at the usual rate, and there were no PHP errors, because a refused request never reaches the store’s code. PayPal Payments keeps a record of the last webhook it accepted, and Operanse compares it with the PayPal orders paid since. On this store every payment is followed by a webhook within seconds. At 13:55 two PayPal orders had been paid with no webhook after them: a warning for the daily summary. By 14:00 there were three, and the count kept rising.
The afternoon, replayed. Orders and payments stay inside their band all afternoon; the third lane counts PayPal orders paid since the last webhook, at least fifteen minutes ago.
The PayPal webhooks that stopped arriving. A security plugin update started refusing PayPal’s webhooks. Checkout kept working and orders looked normal, but every PayPal order paid after 13:40 had no webhook behind it. A warning at 13:55, an alert at 15:00 once it had held for an hour.
- 13:40Change recorded: Security plugin 6.1 → 6.2 · by an administrator (wp-admin)
- 13:55PayPal webhooks · Warning: 2 PayPal orders paid since the last webhook from PayPal reached the site, usually none · added to the daily digest, no alert sent
- 15:00PayPal webhooks · Critical: PayPal orders paid with no webhook since, three or more for an hour · alert sent · message sent
31 PayPal orders ($1,606) were paid since the last webhook from PayPal reached the site, about 80 minutes ago. Checkout still works, but what PayPal sends afterwards is not reaching the store: payments it holds for review, customers who approve and do not come back, refunds and disputes. The security plugin update at 13:40 is the only recorded change. - 15:12Change recorded: Security plugin rolled back to 6.1 · by an administrator (wp-admin)
- 15:20PayPal webhooks · Resolved after 85 minutes: webhooks from PayPal are arriving again, and no PayPal order is waiting on one
What happened next
At 15:00, after an hour with three or more, Operanse sent an email and a text to both owners. The alert said that 31 PayPal orders ($1,606) had been paid since the last webhook from PayPal reached the site about 80 minutes earlier, explained what goes missing without webhooks, and named the security plugin update at 13:40 as the only recorded change.
One of the owners opened the PayPal Payments settings, where the webhook status said the webhook could not be received. They rolled the security plugin back at 15:12. The next PayPal payment’s webhook arrived within a couple of minutes, and the incident closed at 15:20.
Then they looked for what the missing webhooks had hidden. One order had been On hold since 14:05: PayPal had held the payment for review and released it twenty minutes later, but the store never heard. They checked it in their PayPal account and moved it to Processing. Two orders were on Pending payment from customers who had approved in PayPal and closed the window. Those payments had never been taken, so the owners sent both customers a link to pay.
The update was installed again the next day on a staging copy first, with PayPal’s webhook address allowed in the security plugin, and tested with a real PayPal order and the plugin’s webhook test before it went live.
If this is happening on your store
None of the checks below need a monitoring tool, only access to WordPress admin and your payment provider’s dashboard.
What to check first
- In the PayPal Payments settings, find the webhook status. It shows the address PayPal sends webhooks to, and has buttons to resubscribe and to send a test webhook. Send a test: if it is not received, PayPal cannot reach your store.
- Compare that address with your site’s address. It should be your site address followed by
/wp-json/paypal/v1/incoming, with the same domain, https, and www or no www. - Look in your security plugin’s or CDN’s log of blocked requests for requests to
/wp-json/paypal/v1/incoming. - In WooCommerce → Status → Logs, open the PayPal Payments log (it needs logging turned on in the plugin’s settings). A “webhook verification failed” line means webhooks arrive but are rejected.
- List what changed when the problem started: security or firewall plugins, CDN or host settings, a site move or domain change, maintenance mode, password protection.
Telling the likely causes apart
- The test webhook never arrives, and the blocked-requests log shows it. A security plugin, firewall or CDN rule is refusing PayPal. Allow requests to the webhook address.
- The webhook address is your old domain, or http. The site moved or changed address and the webhook did not. Resubscribe in the PayPal Payments settings.
- The log says webhook verification failed. The webhooks arrive but do not match the PayPal connection, which can happen after reconnecting or switching between sandbox and live. Resubscribe.
- Nothing arrives and nothing is blocked. Check that the site is publicly reachable at that address: not in maintenance mode, not password protected, and not a staging copy.
Confirming it has recovered
- The webhook test in the PayPal Payments settings reports the webhook as received.
- The next real PayPal payment is followed by a webhook: in the plugin’s log, or in the settings, which show when the last one arrived.
- Check every PayPal order that went On hold while webhooks were missing against your PayPal account, and move the ones PayPal completed to Processing.
- Look at PayPal orders left on Pending payment during the problem. If PayPal shows the payment approved but not completed, the money was never taken; contact the customer with a link to pay.
- Check your PayPal account for refunds or disputes in that time, and record them in WooCommerce by hand.
How to prevent it
- After any change to a security plugin, firewall, CDN or host, use the webhook test in the PayPal Payments settings and check that it reports the webhook as received.
- When you move the site, change its domain, or switch to https or www, resubscribe the webhooks in the PayPal Payments settings so PayPal sends them to the new address.
- If your security plugin or CDN has an allow list, add the PayPal Payments webhook address: your site address followed by
/wp-json/paypal/v1/incoming. - Look at orders On hold now and then. An order paid through PayPal that has been On hold for more than a day is worth checking against your PayPal account.
Related tools and examples
- Payments failing after a gateway update: when payments are refused at checkout and orders stop, rather than checkout working while webhooks go missing.
- Check your WooCommerce system status report: WP-Cron and scheduled actions, which payment plugins rely on for work after checkout.
- PayPal Payments monitoring: what is watched for WooCommerce PayPal Payments, and what is not.
How Operanse catches it
Orders, payments and errors all looked normal, so a monitor that watches those would have stayed quiet. Operanse reads the time PayPal Payments recorded for the last webhook it accepted, and counts the PayPal orders paid since then, at least fifteen minutes ago. PayPal sends a webhook for every payment, so on a working store that count stays at zero, and the alert gives the number of orders and their total.
It also checks that the webhook PayPal Payments registered points at this site’s current address. After a move or a change to https, it can still point at the old one, and every webhook goes there instead.
What it does not tell you is which orders were affected. A payment held for review, a customer who never came back, a refund made in PayPal: those are the things to look for once you know the webhooks stopped, as the steps below describe.
Operanse compares each store’s activity with its own history and groups related anomalies into incidents. Playback, the replay above, is on Monitor and Insight; Insight adds server monitoring and an AI review of the likely cause, with its evidence. How Operanse monitors a WooCommerce store.