● Launching soon on WordPress.org

Stop gateway updates from silently reconfiguring your checkout.

Payment plugin updates quietly switch methods on — Stripe Link, PayPal “Pay in 3”, express buttons — without asking. It doesn’t break checkout, so nothing alerts you; it just costs you trust, margin and clean books. PayDrift catches every change after an update, shows you the exact diff, and reverts it in one click.

After every update — automatic Exact diff + one-click revert Self-hosted — no account, no cloud
yourstore.com/wp-admin › PayDrift
PayDrift admin screen: 3 payment settings changed after an update — Stripe Payment Request, Stripe Link and PayPal Pay Later all flipped from no to yes, each flagged HIGH, with a one-click Revert (and Fix in Stripe dashboard for the platform-locked Link), plus an audit log.

The real PayDrift screen — the exact settings a gateway update changed, each with one-click revert, and the honest “Fix in Stripe dashboard” for platform-locked Link.

3 caught
payment methods silently enabled by one update — flagged the moment it happened
1 click
to revert each WooCommerce-controlled change back to known-good
0 cloud
self-hosted, no account, no phone-home — your config never leaves your site
The problem

A routine update just changed how you get paid — and nobody told you.

This is one of the most-reported, least-solved WooCommerce problems. In store owners’ own words, from public reviews and threads:

  • “Payment options enabled without consent!” A gateway update turns Stripe Link or PayPal Pay-Later on by itself — and it won’t switch off from the UI.
  • Silent by design. Checkout still works, so uptime and health monitors never fire. You find out when a customer asks about a “Pay in 3” button you never added.
  • It costs real money. Unexpected pay-later fees, a broken tax/accounting setup, and in the worst cases a white-screen on disable — quietly, until revenue dips.
  • WooCommerce itself acknowledged it (2026 “gateways have always been enabled” debrief) — a structural migration was treated as a batch of new gateway activations. It’s not going away on its own.
Why PayDrift

Built to catch exactly this — and nothing you don’t need.

📸

Snapshot & diff after every update

PayDrift records a known-good baseline of your payment-method and checkout settings, and re-checks it after every plugin/theme update and once a day — so a silent change is caught immediately.

🔔

Plain-language alert + one-click revert

You get the exact diff (“PayPal update enabled Pay Later — was off”) as an admin notice and email, and revert the change to known-good with one click. Every action is logged.

🔒

Self-hosted & honest

No cloud, no account, no phone-home. And where a setting is platform-locked (Stripe Link on OAuth), PayDrift alerts and deep-links you to Stripe instead of faking a revert.

How it works

Install once. It watches from then on.

No configuration required — no cloud account, no checkout code, nothing to maintain.

Install & activate

PayDrift takes a baseline snapshot of your current payment-method enable-states and checkout-critical settings. That’s your known-good.

An update changes something

After every plugin/theme update — and on a daily background check — PayDrift diffs the live config against the baseline and classifies each change by severity.

You’re alerted — then revert or accept

Get the exact diff by admin notice + email. Revert any WooCommerce-controlled change in one click, or accept the new state as your baseline. Everything is written to the audit log.

Everything in the box

A focused payment-config watchdog.

Snapshot engine — a known-good baseline of every watched payment & checkout setting, re-taken after each update.
Update-triggered diff — hooks upgrader_process_complete plus a daily check; classifies changes by severity.
Plain-language alerts — admin notice + email with the exact “was → now”. No telemetry, no phone-home.
One-click revert — restores just the drifted setting to known-good, without clobbering neighbouring settings.
Stripe, PayPal & a generic fallback — curated watchlists for the big gateways, plus enabled-state watching for any registered gateway.
Honest on platform locks — Stripe Link on OAuth is alert-only with a Stripe deep-link, never a fake revert.
Audit log — every snapshot, alert and revert recorded for compliance and traceability.
Self-hosted & HPOS-compatible — reads only settings, never order data; your config stays on your server.
Pricing

Free core. Pro is pay-once, for life.

The free plugin fully solves detect-and-fix for a single store. Pro adds automatic prevention and multi-site — pay once, no monthly SaaS.

● Launching soon — Free on WordPress.org, Pro right after

Free

$0
  • Snapshot + diff after every update
  • Admin-notice & email alerts
  • One-click manual revert
  • Audit log, single site
Get notified at launch →
LIFETIME — PAY ONCE

PayDrift Pro

$99 one-time · single site
  • Everything in Free, plus:
  • Guard-Mode — auto-revert pinned methods
  • Multi-site dashboard
  • Slack / webhook alerts
  • Extended gateway watchlist · Lifetime updates
Notify me about Pro
Running multiple stores? Agency covers unlimited sites. Agency — $249 →
Why not just…

The tools you already have don’t catch this.

 Checkout health monitorsSettings backup / activity logPayDrift
Catches a silently-enabled payment method✗ checkout still “works”✗ log only / manual
Triggered automatically after an update
Shows the exact was → now diffpartial
One-click revert to known-good✗ log has no revert
Self-hosted, no account✗ mostly SaaS

Health monitors test whether checkout runs, not whether its config quietly changed. Activity logs record a change but can’t revert it. PayDrift does the update-triggered payment-config diff → alert → revert. · PayDrift is an independent third-party plugin.

FAQ

Questions, answered.

What exactly does PayDrift detect?

Payment- and checkout-critical settings that change without you doing it — most importantly payment methods a gateway update silently enables (Stripe Link, Stripe Payment Request / Apple & Google Pay, PayPal Pay Later / Pay-in-3), plus core checkout settings like the default gateway, guest checkout and tax calculation. It compares against your last known-good baseline after every update and once a day.

Does it phone home or use a cloud service?

No. Everything runs on your own server, alerts go through your own WordPress email, and nothing about your store leaves the site. No account, no subscription, no telemetry.

Will it slow down my checkout?

No. PayDrift never runs on the storefront or checkout — only on settings, after updates and on a daily background check. Zero impact on shoppers.

Can it revert Stripe Link?

On OAuth-connected Stripe accounts, Link is platform-locked and can’t be changed from WordPress. PayDrift is honest: it alerts you and deep-links to your Stripe dashboard instead of faking a revert. Everything WooCommerce-controlled is reverted in one click.

What does the one-click revert change?

Only the single setting that drifted, back to your known-good value — without touching neighbouring settings. Every revert is written to the audit log.

Know the moment your checkout changes.

PayDrift catches every payment & checkout setting a gateway update flips — with the exact diff and a one-click revert. Self-hosted, pay once. Launching soon on WordPress.org.