Payment gateways fail silently more often than store owners realize \u2014 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.<\/p>\n\n
Checkvane watches for the real, specific causes of this and emails you when one happens:<\/p>\n\n
What this plugin deliberately does not do<\/strong>: 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 \u2014 nothing synthetic, nothing that could itself put a live store at risk.<\/p>\n\n\n No. All monitoring runs on scheduled background checks (WP-Cron) or passively observes existing WooCommerce hooks\/logs \u2014 nothing runs synchronously in the checkout request path except a small error listener script, which only reports errors and never blocks page load.<\/p><\/dd>\n No. This is intentional \u2014 automatically toggling a live store's gateway into test mode is the kind of automated production-config change that can fail open and itself block real customer payments, which is exactly the problem this plugin exists to prevent.<\/p><\/dd>\n Bank transfer, cheque, and Cash on Delivery orders are excluded by default since they're expected to sit in Pending\/On-hold until manually confirmed. If you see a false positive for another manual method, it can be excluded via the \n
\n
Does this slow down my checkout?<\/h3><\/dt>\n
Will this ever submit a test payment or change my gateway settings?<\/h3><\/dt>\n
Why did I get an alert about \"stuck\" orders when I use bank transfer?<\/h3><\/dt>\n
chkv_manual_payment_methods<\/code> filter.<\/p><\/dd>\n\n<\/dl>\n\n\n0.1.0<\/h4>\n\n
\n