Operanse
Sign inSign up
WooCommerce PayPal Payments monitoring

Know when PayPal stops talking to your store.

WooCommerce PayPal Payments takes the payment at checkout, so the store keeps working when PayPal’s webhooks stop arriving. Nothing looks wrong until a held payment, a missed charge or a refund nobody recorded turns up.

Operanse works with WooCommerce PayPal Payments: PayPal, Pay Later, cards, Apple Pay and Google Pay through the same plugin. It checks that PayPal’s webhooks are still reaching your store, watches the store’s own calls to PayPal, and tells you when payments fail more than usual for this hour or orders stop coming in.

This page is the PayPal Payments detail. For orders, payments across every gateway and what an outage costs, see order and payment monitoring.

The webhook check, failure-rate monitoring, calls to PayPal and revenue estimates are on Monitor ($39/site/month) and Insight ($99). The trial is 14 days of Insight.

A PayPal webhooks alert (example store)Example data
CRITICALfirst seen 13:55 · still open
31 PayPal orders paid with no webhook from PayPal since 13:39
statement
31 PayPal orders ($1,606) were paid since the last webhook from PayPal reached the site, 81 min ago. PayPal sends one for every payment; this store usually has none waiting.
what goes missing
payments PayPal holds for review stay On hold; customers who approve and don’t come back are never charged; refunds and disputes made in PayPal don’t reach WooCommerce
changed before
a security plugin was updated at 13:40
what to check
the webhook status and test in the PayPal Payments settings
01

What breaks quietly with PayPal Payments

The checkout loads, customers pay, orders arrive. These are the problems that leave all of that looking normal.

  1. PayPal’s webhooks stop arriving

    A security plugin, a firewall or CDN rule, a site move, or password protection can block PayPal’s messages to your store. PayPal Payments records when it last received one, and Operanse counts the PayPal orders paid since then. PayPal sends a webhook for every payment, so on a working store that count stays at zero.

  2. A webhook registered for the wrong address

    After a move to a new domain, to https, or to or from www, the webhook can still point at the old address. Operanse compares the address PayPal Payments registered with your site’s current one and says so when they differ, before an order proves it.

  3. Calls to PayPal failing

    The store calls PayPal to create and capture each payment. When those calls start timing out or failing, Operanse reports PayPal as a payment service in trouble, with the failures counted, not guessed.

  4. Failures above normal, or orders that stop

    A few failed payments are ordinary. A third of first attempts failing is not, and neither is a store taking a quarter of its usual orders for half an hour. Both are judged against this store’s own history for the hour.

02

Why the webhooks matter

Most PayPal payments are finished at checkout and the order moves to Processing straight away. The webhooks carry what happens afterwards, and that is what goes missing when they stop:

  • A payment PayPal holds for review sits On hold until a webhook says it went through.
  • A customer who approves in PayPal and closes the window before getting back to your store is charged only when the webhook arrives. Without it, the money is never taken.
  • Refunds, reversals and disputes made in PayPal reach WooCommerce by webhook too.

None of these shows as an error, which is why the check looks at the webhooks themselves rather than waiting for orders to look wrong. See a worked example.

03

One cause, one notification

An unusual reading goes to the daily summary first. An incident becomes critical when three or more PayPal orders have been paid with no webhook after them for an hour, when at least twenty payments fail in half an hour, or when 30% of payments fail with at least ten failures behind the figure. Critical alerts go by email and Slack, and by SMS and WhatsApp according to your alert settings and plan limits.

Each alert says what changed shortly before: a PayPal Payments update, a WooCommerce update, a new security or caching plugin. Thirty more orders for the same cause do not produce thirty more notifications.

Operanse does not retry payments, complete orders, resubscribe webhooks or change PayPal Payments’ settings.

04

Clear limits on what Operanse sees

  1. Not which orders were affected

    Operanse tells you the webhooks stopped and how many PayPal orders were paid since. Finding the order that went On hold or the approval that was never charged is a look at your orders and your PayPal account, and the example above says where.

  2. No decline reasons

    Operanse reads the reason a payment was refused only from the two Stripe plugins. With PayPal you get failure counts, rates and retries, not the reason for each. Stripe gateway detail

  3. Failure rates are for the whole store

    Payment failures are counted across every gateway together. If you run PayPal beside a card gateway, a rise shows in the store’s rate; the webhook check is PayPal’s alone.

  4. Your PayPal account is not read

    Operanse has no PayPal login or API key. Disputes, holds, balances and payouts stay in PayPal. The webhook check reads only the time and address PayPal Payments stores on your site; the address is compared there and never sent. No card numbers, customer names or email addresses are collected. The agent is read-only. Security

05

Set it up

  1. Create an account at app.operanse.com and add your store.

  2. Install Operanse Agent from WordPress.org and paste the pairing token.

  3. That is all. Nothing to configure in PayPal Payments.

The webhook check and a store that can no longer take payment need no learned baseline: they work from the first readings. Comparisons with this store’s normal failure rates start once it has about 48 hours of history; a weekly pattern takes about two weeks.

Watch, the free plan, alerts when the store can no longer take payment and when subscription renewals fail; the rest above is on Monitor and Insight. Pricing

06

Frequently asked questions

PayPal Payments already shows a webhook status. Why do I need this?

The status is a page in wp-admin that you have to open. It doesn’t tell anyone when it changes. Operanse checks the webhooks on a schedule and sends an alert when PayPal orders keep being paid with none arriving.

Why would PayPal’s webhooks stop?

Usually a security plugin or firewall rule that blocks requests not coming from a browser, a CDN setting, maintenance mode or password protection, or a site that moved address without resubscribing the webhooks.

Will I get an alert for every failed PayPal payment?

No. Failures are counted. Operanse alerts when the rate is unusual for this store, not on each one.

Does it work with WooCommerce Subscriptions?

Yes. Renewals charged through PayPal are watched apart from checkout, with first attempts and retries kept separate. WooCommerce Subscriptions monitoring

What about the older PayPal Standard gateway?

Orders, failures and orders that stop are watched for every gateway, PayPal Standard included. The webhook check is for WooCommerce PayPal Payments only.

Know when PayPal stops reaching your store.

See PayPal’s webhooks, calls and failures against your store’s normal. Start with 14 days of Insight.

PayPal is a trademark of PayPal, Inc. WooCommerce is a trademark of Automattic Inc. Operanse is not affiliated with or endorsed by either.