The latest WooCommerce PayPal Payments update just landed, and if your inbox is full of “Payment Gateway Enabled” notifications, you are not the only one. Normally that pattern means a compromised site or somebody testing in production. This time it is a structural migration the PayPal team shipped in v4.0.0, and it changes how Alternative Payment Methods (APMs) are registered in your store.
So if you are staring at ten emails about Blik, iDEAL, and Bancontact being enabled, nothing was hacked. The change was deliberate, just loud about it, and it comes down to an old plugin development tradeoff: break the buyer’s journey to keep the settings tidy, or keep the sales flowing and eat the notification noise.
What changed in the WooCommerce PayPal Payments architecture
In the v2 and v3 branches, APMs lived inside the “smart button” stack rather than existing as standalone gateways. They sat behind the main PayPal button and appeared based on the buyer’s IP address, so a Dutch shopper got iDEAL and a Belgian shopper got Bancontact. Most merchants had no idea any of it was active, because none of it showed up as a separate entry under WooCommerce > Settings > Payments.
Turning one of them off meant writing a filter, which is why most people left them alone. For the curious, the old workaround looked like this:
/**
* Legacy way to disable specific APMs in WooCommerce PayPal Payments
*/
add_filter( 'woocommerce_paypal_payments_gateways_apm_disabled_methods', 'bbioon_disable_legacy_apms' );
function bbioon_disable_legacy_apms( $methods ) {
$methods[] = 'blik'; // Example: Disabling Blik manually
return $methods;
}Why the emails went out
In v4.0.0 the WooCommerce PayPal Payments team turned each of those APMs into an individual WooCommerce gateway, with its own toggle and its own settings page. That is the better design. The catch is that the migration carried over the “enabled” state from the hidden stack, so WooCommerce core saw a dozen gateways get registered and switched on at once and sent a notification for every one of them. The emails were accurate and still alarming.
If you want the wider context on release timing and what it does to a store during heavy traffic, I wrote about why the new WooCommerce update schedule matters.
What to do now
Your checkout has not changed. Buyers who saw those buttons yesterday still see them today, and now you have control over each method separately. Go to WooCommerce > Settings > Payments and actually read the list. If you don’t sell to the Netherlands, iDEAL has no reason to sit in your settings. The official PayPal local payment methods documentation covers which methods are eligible where.
If this WooCommerce PayPal Payments cleanup is eating your dev hours, I can take it off your hands. I have been working with WordPress since the 4.x days.
My take on the rollout
The developers had to pick between continuity and communication. Defaulting to the state you already had meant no merchant woke up to lost sales from local customers, and for a plugin running in production that is the right call. Shipping an architectural change this size with no admin notice beforehand was the miss. With integrations this tangled, or with official API updates, an opt in default, or at least a heads up banner in the dashboard, costs almost nothing and saves everyone a round of support tickets.
If the notifications keep coming or something else still looks off, the original support thread on WordPress.org is worth reading. The team has been answering people there, which bodes reasonably well for the rest of the v4.x line.
