← Update Watch

Update Watch: the Stripe update that hid payment methods at checkout

Update Watch · Published 1 October 2026 · 5 min read

Update Watch looks at real WordPress and WooCommerce updates that broke something, using public sources only. The point isn't to blame plugin developers, who usually fix things fast. It's that even well-run plugins ship bad releases sometimes, and your process has to allow for that.

What happened

On 16 April 2025, version 9.4.0 of the WooCommerce Stripe Gateway plugin was released. It was a sizeable update, with changes to the plugin's newer "Smart Checkout" and to how payment methods are shown at checkout.

On some shops, the checkout stopped offering any way to pay. A store owner reported on the plugin's WordPress.org support forum that after updating to 9.4.0, customers saw WooCommerce's "no available payment methods" message, even though Stripe was enabled in the settings. They said it had affected many sites.

The plugin team moved quickly. The next day, 17 April 2025, they released version 9.4.1, which the official changelog describes simply as "Forces rollback of version 9.4.0". In the support thread, the team explained that 9.4.1 put back the previous version's code while they investigated, and that the new features would return in a later release.

Why it matters

A day-long window sounds short. But consider what it means for a shop that updated during it:

If you look after several client shops, that's the uncomfortable part: the update that breaks a checkout is often one you applied yourself, and nothing tells you it happened.

How you'd catch it

This kind of failure is easy to spot if you look in the right place. The checkout page doesn't need to be placed as an order; you only need to check that it offers a way to pay.

  1. Test the checkout straight after every update, not just on a schedule. Add a product to the basket, go to the checkout, and confirm that each payment method you expect is listed and its fields load. Our checkout testing checklist covers the steps.
  2. Update payment plugins on their own. If you apply ten updates at once and the checkout breaks, you have ten suspects. Updating the payment gateway separately, then testing, tells you immediately which update caused it.
  3. Keep the previous version to hand. Rolling back one plugin takes minutes if you have the previous version's files ready. Waiting for the developer's fix can take longer, even when they're as quick as they were here.
  4. Watch the support forum after big updates. For payment plugins, a quick look at the plugin's WordPress.org support forum a day or two after a release shows whether other shops are reporting problems.

An uptime monitor can't do any of this, because it never goes through the checkout. We explain why in why uptime monitoring misses broken WooCommerce checkouts.

This is the kind of failure PatchSure is being built to catch. The plan: after every update, PatchSure runs a checkout test on each WooCommerce shop. If a payment method has disappeared, it rolls back the update that caused it and tells you in plain English. PatchSure is still in development; join the list to hear when the private beta opens.

Join the early-access list

Summary

Sources