Know when WooPayments stops turning payments into orders.
WooPayments’ own screens show the payments. They don’t tell you when checkouts start failing more than usual, or when paid orders sit at pending.
Operanse reads WooPayments through WooCommerce’s own order events, the same way it reads every gateway. It learns what is normal for your store, at this hour, and tells you when payments start failing, when paid orders stop moving, or when the store can no longer take payment at all.
This page is the WooPayments detail. For orders, payments across every gateway and what an outage costs, see order and payment monitoring.
Failure-rate monitoring, paid-but-pending alerts and revenue estimates are on Monitor ($39/site/month) and Insight ($99). The trial is 14 days of Insight.
- statement
- 7 orders carry a recorded payment and have not moved from pending for more than 15 minutes. Normal for this store is none.
- gateway
- woocommerce_payments
- money waiting
- $914 taken and not fulfilled
- changed before
- a security plugin was updated at 10:31
- what to check
- whether the store’s REST API answers from outside; WooPayments’ own notices in WooCommerce → Payments
The failures that don’t look like failures
A broken payment setup rarely shows an error page. The checkout loads, the button works, and the store takes less than it should.
Paid, and still pending
Some payments are confirmed to the store afterwards by a notification from WooPayments’ service. If that notification stops reaching the site, the customer has paid and the order never moves. Operanse counts orders that carry a recorded payment and are still pending after 15 minutes, by gateway, with the money waiting.
Failure rate above normal
A few declines are ordinary. A checkout where a third of payments fail on their first attempt is not. Rates are judged against this store’s own history, and retries are counted apart so no payment is counted twice.
Orders that stop arriving
When the account is disconnected or the payment form stops loading, nothing fails: orders just stop. A store taking a quarter of its usual orders for half an hour is reported.
No way left to pay
If WooPayments is switched off and no other payment method is on, or the checkout page is unpublished, that is reported on every plan, including the free one.
One cause, one notification
An incident becomes critical when three or more paid orders stay pending 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 WooPayments update, a WooCommerce update, a new security or caching plugin. Thirty more orders failing for the same cause do not produce thirty more notifications.
Operanse does not retry payments, complete orders or change WooPayments’ settings.
Keep the WooPayments dashboard. Add the store’s normal.
WooPayments shows transactions, deposits and disputes. Operanse adds whether today is unusual for this store, which orders were paid and never fulfilled, which attempts are retries, the estimated revenue at stake and what changed on the site before it started.
Clear limits on what Operanse sees
No decline reasons
Operanse reads the reason a payment was refused only from the WooCommerce Stripe Payment Gateway plugin. With WooPayments you get failure counts, rates and retries, not the reason for each. The reason is in the WooPayments transaction list. Stripe gateway detail
Failure rates are for the whole store
Payment failures are counted across every gateway together. If you run WooPayments beside PayPal, a rise shows in the store’s rate; paid-but-pending orders are the part named by gateway.
WooPayments’ own service is not watched by name
WooPayments talks to its service through WordPress.com, the same address many other plugins use, so those calls are not judged as a payment service. An outage there shows as failed payments and pending orders, not as a named outage.
Disputes and deposits are not read
Chargebacks, deposits and fees stay in WooPayments. No card numbers, customer names or email addresses are collected; only counts, totals, order numbers and gateway ids. The agent is read-only. Security
Set it up
Create an account at app.operanse.com and add your store.
Install Operanse Agent from WordPress.org and paste the pairing token.
That is all. Nothing to configure in WooPayments.
Paid-but-pending orders and a store that can no longer take payment need no learned baseline. 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
Frequently asked questions
Why would a paid order stay pending?
Usually because the notification that confirms the payment did not reach the site: the store’s REST API was blocked by a security plugin, a firewall or a maintenance mode, or the site’s connection to WordPress.com broke. The money is taken; the order waits.
Will I get an alert for every declined card?
No. Declines are counted. Operanse alerts when the rate is unusual for this store, not on each one.
Does it work with WooCommerce Subscriptions?
Yes. Renewals paid through WooPayments are watched apart from checkout, with first attempts and retries kept separate. WooCommerce Subscriptions monitoring
Can it complete the stuck orders?
No. It names the gateway, the count and the money waiting. It does not change orders, retry payments or touch WooPayments.
Know when payments stop becoming orders.
See failures against your store’s normal, and the paid orders nobody fulfilled. Start with 14 days of Insight.
WooPayments and WooCommerce are trademarks of Automattic Inc. Operanse is not affiliated with or endorsed by Automattic.