Get PayDrift

Payment methods keep enabling themselves after WooCommerce updates — what's going on?

A new button appeared at your checkout — "Pay in 3", Link, Apple Pay — and you're certain you didn't add it. You're right: gateway plugin updates re-enable payment methods on their own. It's not a one-off bug; it's a pattern across Stripe, PayPal and others. Here's why it happens, which methods to watch, how to audit your checkout, and how to stop finding out weeks too late.

Short version: Payment gateways switch their promoted methods (Stripe Link, PayPal Pay Later, express buttons) on by default during updates and migrations. Checkout still works, so nothing warns you. WooCommerce acknowledged the pattern in 2026. The only real defense is being alerted when a payment method changes — which is what PayDrift does.

Why gateway updates re-enable methods

Payment methods like Stripe Link and PayPal Pay Later are revenue features for the gateway — they want them on. So when a plugin updates or migrates its settings model, the safe-for-them default is to (re-)enable them. From the merchant side that looks like a method turning on by itself. Because it doesn't break checkout, uptime monitors and health checks stay green while your configuration quietly changed. WooCommerce's own 2026 debrief described a structural migration being treated as "a batch of new gateway activations".

Which methods to watch

How to audit your checkout now

  1. Open WooCommerce → Settings → Payments and expand each active gateway. Note exactly which methods and express buttons are on.
  2. Place a test order (or open checkout in an incognito window) and compare what's actually shown to what you intended.
  3. Check each gateway's own settings screen for method-level toggles (Stripe Link, PayPal Pay Later messaging locations, Square digital wallets).
  4. Write down your intended, "known-good" set — so after the next update you can tell what changed.
💡 The manual audit works once. The problem is repeating it after every plugin update — which is exactly the part that doesn't scale, and why silent changes slip through.

Guides for the specific methods

Stripe Link keeps turning on in WooCommerceWhy it re-enables, how to keep it off, and the OAuth-lock catch. PayPal "Pay in 3" / Pay Later won't turn offWhy the setting won't save and how to remove it in all three places. How to monitor payment settings (tools compared)Activity logs vs health monitors vs settings freeze vs PayDrift.

Stop auditing by hand. Get alerted instead.

PayDrift records a known-good snapshot of your payment-method and checkout settings and diffs it after every update — then alerts you with the exact change ("PayPal Pay Later: was off → now on") and reverts WooCommerce-controlled toggles in one click. Self-hosted, no account, no cloud. The audit runs itself.

See how PayDrift works

FAQ

Why do methods appear after an update?

Gateways enable their promoted methods by default during updates/migrations. Checkout still works, so nothing warns you.

Which ones most often re-enable?

Stripe Link, Stripe Payment Request (Apple/Google Pay), and PayPal Pay Later messaging — the methods gateways actively push.

Why does it matter if it still works?

It damages trust, adds pay-later fees, skews tax/accounting and can cause a WSOD on disable — quietly, until revenue or a customer flags it.

How do I get alerted?

WooCommerce has no native setting; PayDrift diffs your payment config after every update and alerts you with the exact change.