
Webhooks that keep trying when the other end is down.
Find the orders your customers paid for that WooCommerce still calls Pending payment.
Log in as demo / OrderWardenDemo!. The demo runs in demo mode: its orders and the gateway answers are bundled samples, every one labelled “Demo data”, and the store resets every hour.
Why it exists
A customer is charged in Stripe or PayPal, but the order stays on Pending payment. The webhook never arrived, failed or was blocked, and nobody notices until the customer writes to ask where their order is.
How OrderWarden handles it
OrderWarden checks recent unpaid orders against the gateway in the background and shows exactly which ones were paid, with the gateway’s own evidence beside each. One click asks the gateway again and completes the payment the way WooCommerce would have.
It also watches the things that go quiet before anyone complains: no orders during business hours, a jump in failed payments, a gateway whose webhooks stopped arriving.
How it works
Settings shows “API keys found” for each gateway you use. If not, paste a read-only key.
Email, Slack, Discord or any webhook URL, with a test button so you know they arrive.
Each mismatch comes with the gateway’s own evidence. Mark as paid in one click, or dismiss it.
Features
In the box
Everything in the box, so there is nothing to discover after checkout.
Runs on your own WordPress and asks your own Stripe, PayPal or Mollie account, with the keys your gateway plugin already holds. Nothing routes through us.
OrderWarden, $39 once.
A year of updates, 30-day refund, invoice from Paddle.
The gateway took the money but WooCommerce never heard about it. That news normally arrives by webhook, and if the webhook URL is wrong, the signing secret changed, a firewall or caching plugin blocks it, or the site was down at that moment, the order stays on Pending payment. OrderWarden asks the gateway directly and puts those orders in its inbox.
It asks the gateway again, and if the payment is still there, it calls WooCommerce’s own payment completion with the gateway’s transaction id. WooCommerce then updates the status, reduces stock and sends its usual emails, and an order note records the evidence and who clicked. Clicking twice does nothing the second time.
Only if you switch on auto-fix, which is off by default — and then only for Pending payment or Failed orders where the gateway captured exactly the order total, in the same currency, with no refund. Everything else waits for your click.
An amount or currency that does not match the gateway; refunded at the gateway but still paid in WooCommerce; paid in WooCommerce but never captured at the gateway, which is an order not to ship; and authorised but not captured while the order is still unpaid.
Three monitors. No new orders for a number of hours during your business hours, compared with your store’s own pace over the last 14 days, so a quiet store is not spammed. A spike in the share of failed orders. And a gateway whose orders keep coming in while its webhooks have stopped reaching your site.
Every 10, 15, 30 or 60 minutes, on Action Scheduler, which ships with WooCommerce. It looks back over a window you set, from 1 to 30 days, and can also check Processing and Completed orders for refunds and amount differences.
Yes, both. Orders are read and updated only through WooCommerce’s own order API.
Everything else is in the OrderWarden documentation, and anything it does not answer goes to support@webkoding.com.
So you know before you buy, not after.
OrderWarden, $39 once.
A year of updates, 30-day refund, invoice from Paddle.

Webhooks that keep trying when the other end is down.

What your WooCommerce store actually made, after everything.

Send WooCommerce orders to Teamleader Focus as invoices and deals, and get paid invoices back.
We will write when there is a new plugin, or a release worth knowing about. A few emails a year, each about something we actually shipped — no offers, no sequence, and your address goes nowhere else.
One click to leave, from any of them. What we do with it.