PayDriftWooCommerce payment settings monitoring, compared (2026)
A gateway update just enabled Stripe Link, PayPal “Pay in 3” or an express button on your store — without asking. Checkout still works, so no monitor fired. Here’s an honest look at every way to catch it: activity logs, checkout health monitors, settings-freeze plugins, doing it by hand — and where PayDrift fits.
The problem in one sentence
Payment gateway plugins (Stripe, PayPal Payments, WooPayments, Mollie, Square) periodically switch payment methods on during an update or migration, as a default. It doesn’t break checkout, so uptime and health monitors never fire — it just quietly changes how you get paid, adds unexpected pay-later fees, and skews your tax/accounting until revenue dips. WooCommerce itself acknowledged the behaviour in 2026. So the real question isn’t “is my checkout up?” — it’s “did my payment configuration quietly change?”
The options at a glance
| Activity log | Checkout health monitor | Settings freeze / backup | PayDrift | |
|---|---|---|---|---|
| Catches a silently-enabled payment method | only if you read the log | ✗ checkout still “works” | ✗ (freeze must be armed) | ✓ automatic |
| Triggered automatically after an update | ✗ generic logging | on a schedule | ✗ manual | ✓ on every update + daily |
| Shows the exact “was → now” diff | partial (raw log line) | ✗ | ✗ | ✓ plain-language |
| One-click revert to known-good | ✗ log has no revert | ✗ | restore whole backup | ✓ per setting |
| Payment-method focused | ✗ everything | ✗ uptime | ✗ all settings | ✓ gateways + checkout |
| Auto-revert without you clicking | ✗ | ✗ | ✗ | ✓ Guard-Mode (Pro) |
| Self-hosted, no account | varies | ✗ mostly SaaS | usually | ✓ always |
| Price | free–$ | $/month SaaS | free–$ | free core · Pro $99 once |
Categories describe how each type of tool generally works; individual products vary. PayDrift is an independent third-party plugin.
Why each alternative misses it
Activity logs (WP Activity Log, Simple History)
They record that a setting changed and who changed it — useful for audits. But an update that flips a payment method isn’t a person, the entry is buried among hundreds of others, and there is no revert. You still have to spot it and fix it by hand. Good for forensics, not for catching payment drift in time.
Verdict: records the change, can’t catch or undo it.
Checkout health monitors (uptime / synthetic checkout)
They answer “does checkout load / can a test order complete?” A silently-enabled Stripe Link or PayPal Pay-Later doesn’t break checkout — so the monitor stays green while your configuration has quietly changed. Wrong question for this problem, and usually a monthly SaaS.
Verdict: tests whether checkout runs, not whether its config drifted.
Settings freeze / settings backup
A “freeze” blocks changes only while it’s armed — but you can’t stay frozen, because you have to run updates. A settings backup lets you restore, but it’s a manual, all-or-nothing restore of everything, not a targeted revert of the one payment toggle that moved. Neither is update-triggered or payment-focused.
Verdict: manual, coarse, and off by default.
Doing nothing / checking by hand
The most common “tool”. It works right up until the day a customer asks about a “Pay in 3” button you never added, or your accountant flags fees on a method you didn’t know was live. By then it’s been running for weeks.
Verdict: free, until it isn’t.
Where PayDrift fits
PayDrift does the one job none of the above do: after every plugin/theme update (and once a day) it diffs your payment-method and checkout settings against your last known-good baseline, alerts you with the exact change, and reverts any WooCommerce-controlled setting in one click. It’s honest about limits — Stripe Link on OAuth accounts is platform-locked, so PayDrift alerts and deep-links you to Stripe instead of faking a revert. It’s self-hosted, has no account and no phone-home, and the free core fully covers detect-and-fix for one store.
Pro (Lifetime, pay once) adds Guard-Mode — pin the methods you never want enabled and PayDrift auto-reverts them the instant an update flips them — plus Slack/webhook alerts, a multi-site dashboard and an extended gateway watchlist (Mollie, Square).
FAQ
Why did Stripe Link / PayPal Pay Later turn on by itself?
Gateway plugins enable new payment methods during updates/migrations as a default; WooCommerce acknowledged this in 2026. Because checkout still works, nothing alerts you until you notice the new method live.
Can an activity log revert a payment setting?
No — activity logs record the change but have no revert and aren’t tied to updates. PayDrift diffs after every update and reverts in one click.
Don’t checkout health monitors catch this?
No. They test whether checkout runs; a silently-enabled method doesn’t break checkout, so they stay green. PayDrift watches the configuration itself.
How do I stop methods being enabled after updates?
Install PayDrift; pin the methods with Pro Guard-Mode to auto-revert them the moment an update flips them.
Is it self-hosted and free?
Yes — free core, self-hosted, no phone-home. Pro is a one-time Lifetime licence.
Catch the change your monitors miss.
PayDrift diffs your payment & checkout config after every update and reverts drift in one click. Self-hosted, pay once. Launching soon on WordPress.org.
See PayDrift plans