Checkvane for WooCommerce

Payment gateways fail silently more often than store owners realize — a webhook signing-secret mismatch after a plugin update, an expired API key, a plugin conflict that quietly breaks the “Place Order” button. The checkout page looks fine. WooCommerce shows nothing wrong. Customers just leave, and the store owner finds out days later, if at all.

Checkvane watches for the real, specific causes of this and emails you when one happens:

• Webhook signing-secret mismatches — orders stuck as “Pending” while your gateway silently retries and gives up.
• Expired or revoked gateway API keys — generic “Payment failed” with no visible cause, only found in WooCommerce’s own logs.
• Broken checkout JavaScript — a plugin/theme update silently breaking the Place Order button, detected from real customer sessions (not simulated).
• SSL/certificate issues — an expiring certificate, or checkout accidentally served without HTTPS, both of which can hide the card-entry field.
• Orders stuck in Pending/On-hold past a sensible threshold, excluding manual payment methods (bank transfer, cheque, COD) that are expected to sit there.
• Unusual drops in completed-order volume, using multi-baseline comparison (same hour last week, four weeks ago, and a rolling average) rather than a single flat threshold — this only activates after a 3-week learning period so a new store’s normal noise doesn’t cause false alarms.

What this plugin deliberately does not do: it never submits test payments through your checkout, never toggles your gateway into test mode, and never modifies orders or payment settings. Everything is passive, in-process monitoring of your store’s own order data and logs — nothing synthetic, nothing that could itself put a live store at risk.