WooCommerce Stripe Gateway: worth using, but not version 4.9.0

WooCommerce Stripe Gateway is worth using, but only if you install and maintain the current official release. It connects WooCommerce to Stripe and handles card payments, Apple Pay, Google Pay, Link, buy-now-pay-later options, local payment methods, 3D Secure, refunds, saved payment methods, webhooks, and recurring payments through WooCommerce Subscriptions. Stripe also provides fraud tools through Radar and optional in-person payment support through Terminal and Tap to Pay.

The strongest argument for it is breadth. WooCommerce’s documentation lists no plugin setup cost or monthly plugin fee, while the integration can expose 23 payment methods out of the box, depending on the merchant’s country, currency, and Stripe configuration. That makes it a sensible default for stores selling across borders or offering several checkout options without stitching together multiple gateway extensions. Its hosted Stripe Elements fields also reduce the amount of card data handled directly by the WordPress site.

It is also the safest choice for stores that want the official WooCommerce integration rather than a third-party Stripe connector. The code is publicly maintained by WooCommerce, the documentation covers setup, webhooks, checkout behavior, refunds, logs, payment methods, and customization hooks, and the plugin has a large installed base. The current WordPress.org listing shows more than 700,000 active installations and documents a version-support policy tied to recent WordPress and WooCommerce releases.

The weaknesses are mostly operational. Stripe configuration is not genuinely plug-and-play: you need HTTPS, a supported merchant country, a connected Stripe account, working webhooks, and careful testing of classic checkout and Checkout Blocks. The support forum regularly contains reports involving disappearing gateway settings after updates, JavaScript errors in block checkout, stale Checkout Sessions, Adaptive Pricing payment confirmations, and subscription renewal problems. Those issues are not proof that the plugin is unusable, but they do show why payment testing after updates is non-negotiable. WordPress.org’s rating is also a warning sign rather than a clean endorsement: the listing currently shows 3.1 out of 5 stars, with a notably large one-star minority.

The supplied 4.9.0 version is the biggest concern. The official directory currently lists the plugin in the 11.0 series and requires recent WordPress and PHP versions, so 4.9.0 is several major generations behind. An old gateway can miss security fixes, Stripe API changes, checkout-block compatibility work, and changes to payment-method handling. Do not treat an old package as interchangeable with the current plugin.

How it compares

WooPayments is easier for merchants who want payments, deposits, and reporting inside the WooCommerce admin, but it is more tightly tied to the WooCommerce Payments service. Payment Plugins for Stripe WooCommerce is the obvious alternative if you prioritize a simpler third-party integration and highly rated support, although it is not the official WooCommerce connector. PayPal Payments is better when PayPal, Pay Later, or Venmo demand matters more than Stripe’s card and local-method coverage. For a Stripe-first store, the official gateway remains the sensible baseline; for a store requiring minimal maintenance, test every update and avoid the old 4.9.0 build.