trifco

Hi Krystian,

I appreciate the technical breakdown regarding the migration of Alternative Payment Methods into standalone gateways. However, your explanation fails to account for the practical reality of this rollout.

While you characterize this as a visibility and structure change, the implementation has proven to be a breaking change for those of us using classic checkout environments. By registering these legacy configurations as separate WooCommerce gateways all at once, the update triggered script conflicts that effectively disabled the checkout flow. In my case, this resulted in a grayed-out and inactive PayPal button that remained unresponsive despite hours of troubleshooting.

The claim that there was no perfect approach to satisfy everyone is a false dichotomy. A user-centric approach would have involved an opt-in migration wizard or a staged rollout that prioritized site stability. Instead, the plugin prioritized a backend transition for developers at the expense of a functional front end for merchants.

The primary job of a payment plugin is to ensure that the pay button actually works. By replacing a stable JavaScript loader with a new UI that lacks robust compatibility with legacy hooks and shortcode-based checkouts, this update failed that fundamental requirement.

Until the new UI is genuinely compatible with standard WordPress environments without requiring manual database overrides or rollbacks, the rating stands. Stability is the only metric that matters in e-commerce.

Kind regards,

Trifco