PayPal Standard Sunset: What WooCommerce Stores Do Now

Every few years a payment rail that quietly powered thousands of WooCommerce checkouts goes from “still works if you leave it alone” to “you are now the last person on the boat.” PayPal Standard hit that line this week. The announcement is calm, the migration path is reasonable, and the stores that will get hurt are the ones that ignore it for another six months.

I have been carrying PayPal Standard out of legacy WooCommerce builds for years. It is the gateway people configured in 2018, never touched again, and forgot was even there until a chargeback dispute landed in the inbox. The PayPal Payments plugin has been the official answer for a while, but the deprecation always felt soft. As of last week, it is no longer soft.

Here is what actually changed, why it matters more than the calm tone suggests, and what I am telling clients to do this week.

What is actually new

On June 24, 2026, WooCommerce published PayPal Standard is Sunsetting: What WooCommerce merchants need to know on the developer blog. The core message is that PayPal Standard, the redirect-based gateway that has been part of WordPress e-commerce lore since the early WP e-Commerce days, is being formally retired in favor of the modern PayPal Payments extension.

The mechanical change ships in PayPal Payments 4.1.0, released June 23, 2026. The relevant changelog line is short: “Disable legacy ‘PayPal Standard’ gateway when merchant account is connected to PayPal Payments.” In practice, the moment you successfully connect a PayPal merchant account through PayPal Payments, the old Standard gateway is disabled and hidden from your checkout. Customers stop seeing it. You do not have to remove it manually.

This is not a hard cutoff. There is no “PayPal Standard stops accepting transactions on date X” announcement. The retirement is staged, and stores that ignore it will not break tomorrow. But the direction of travel is now explicit, and the historical timeline backs it up:

• In 2021, with WooCommerce 5.5, PayPal Standard was hidden for new installations. Stores already using it kept it; stores spun up after that point never saw it as an option. The current PayPal Standard documentation page still carries the deprecation notice.
• In WooCommerce 8.9 (May 2024), the bundled gateway and the filter that allowed opting back in were removed from core entirely. After that, PayPal Standard only continued to exist on stores carrying legacy configuration from before that release.
• With PayPal Payments 4.1.0, the legacy gateway gets actively disabled the moment the modern plugin successfully connects to a merchant account. Subscriptions are the documented exception.

The subscriptions carve-out is the part most people will miss. If your store has active or pending-cancel subscriptions still running on PayPal Standard, PayPal Payments detects them and leaves Standard in place rather than disabling it. The reasoning is correct: billing agreements created against PayPal Standard cannot be silently re-pointed at the new integration without merchant action, and breaking recurring billing would be a worse outcome than carrying a deprecated gateway for a while longer. WooCommerce explicitly recommends contacting support to plan a subscription migration rather than pulling the plug yourself.

The replacement is the PayPal Payments extension, which is not just “PayPal but newer.” It bundles Pay Later, Venmo, Apple Pay, Google Pay, advanced card processing, Fastlane, local payment methods, and subscriptions support, all under a single connection. That is a meaningful gap with Standard, which was always a single button that redirected away from your site.

Why it matters for WooCommerce stores

Three reasons this is more than housekeeping.

First, redirect checkouts are a conversion tax. PayPal Standard sends the customer off your domain to log in, then bounces them back. Every additional page in a checkout flow leaks buyers, and on mobile the leak is worse. The modern PayPal Payments integration keeps the buyer on your store using the Smart Payment Buttons and Fastlane, with the redirect happening only when the customer chooses it. If you have been blaming a checkout abandonment problem on traffic quality, and you are still on Standard, you have been blaming the wrong thing.

Second, the WooCommerce checkout has moved on. WooCommerce 10.9 shipped block-based Cart and Checkout as the default a while ago, and the block-based checkout works hand-in-glove with the PayPal Payments integration: Pay Later messaging renders inside the block editor, ACDC card fields integrate as a payment block, and the Smart Payment Buttons sit natively in the payment method list. PayPal Standard does not participate in that. If you are running a block checkout with Standard wedged into it, your customer is seeing a slightly broken-looking payment row.

Third, and this is the underrated one: the modern integration is the one that keeps getting fixes. The 4.1.0 changelog alone covers vault management for saved PayPal accounts, OXXO and Pay upon Invoice in Block Checkout, tax rounding fixes, and a long list of subscription edge cases. PayPal Standard is in maintenance-only mode and has been for years. Every new compliance change, every new alternative payment method, every new fraud signal lands in PayPal Payments. Standard receives none of it.

What I would do (or not do) about it

If you operate or run a WooCommerce store, this is a fifteen-minute audit and, for most stores, a one-hour migration.

The audit: open WooCommerce, Settings, Payments. If you see “PayPal Standard” or “PayPal” listed with an enabled toggle and no separate PayPal Payments entry, you are on the legacy gateway. Cross-reference Orders for the last 90 days and filter by payment method. If PayPal Standard is taking real revenue, treat this as a P1 task for the next maintenance window. If it has not produced an order in six months but is still enabled, disable it now.

The migration, for stores without subscriptions on Standard: install PayPal Payments from the WordPress.org repository, run the connection wizard, sign in with the same PayPal business account, and let the plugin disable Standard for you. Test a real checkout in a private browser, then check the order in PayPal’s dashboard end-to-end. Confirm refunds work from the WooCommerce order screen. Done.

For stores with active subscriptions on Standard: do not yank the gateway. PayPal Payments 4.1.0 is designed to detect this and leave Standard in place, which is exactly the right behavior. Contact WooCommerce support to scope a subscription migration; do not assume you can flip a switch and have billing agreements re-bind to the new integration. If you manage a portfolio of stores, this is the cohort that needs a written plan and a calendar.

What I would not do: rip out PayPal entirely “because we’ll just use Stripe.” The PayPal wallet still converts on a meaningful slice of carts, particularly cross-border and for older buyers, and you give that up the moment you remove it from checkout. The right move is migrating to the modern integration, not abandoning the brand.

The PayPal Standard era was good for WordPress commerce. It made “accept payments on a WordPress site” a checkbox at a moment when that was genuinely hard. The replacement is better, the timing is reasonable, and the only real failure mode here is doing nothing.