November 2026
WooCommerce: the kinds of plugins that most often break payment, and how to know before the client does
Payment gateways, caching, security, checkout fields: some WooCommerce plugins touch payment. Which ones to watch, and how to know before the client.
A plugin updates without an error. The site opens, the Ping stays green. Two days later, the client calls: no orders since Tuesday. On WooCommerce, payment depends on several plugins at once. One of them changes, and the last step stops working.
The families of plugins that touch payment
- Payment gateways (Stripe, PayPal, Mollie and the rest): a new version changes the card form or the redirect to the provider.
- Caching and optimisation: a payment script gets deferred, merged or cached, and the Place order button stops responding.
- Security and firewall: a rule blocks the payment provider’s callback, or the checkout page token.
- Checkout fields and steps: a required field is added, and the theme does not display it.
- Shipping: no method offered for a zone, and the order can no longer be placed.
- Theme and page builder: the checkout page moves to blocks, and a plugin built for the old form no longer shows.
- Coupons and loyalty: a discount is rejected, or a rule blocks the order.
Why the client sees it before you do
None of these failures returns a 500 error. The server responds, the home page loads, an uptime tool stays green. The shopper clicks Place order and nothing happens. They leave without a word. The client sees sales drop, then calls you.
After each update: the manual check
- Update one plugin at a time, and start with a copy of the site if you have one.
- Clear the optimisation plugin’s cache and the host’s cache.
- Add a product to the cart, then go all the way to the provider’s payment page.
- Check that every payment method is still offered, in live mode.
- Open WooCommerce > Status > Logs: a new gateway error shows up there.
Know before the client: a Flow and its screenshot
The manual check says everything worked right after the update. Flow then repeats it, at the frequency you set. A real browser opens the shop, adds a product, checks that the total is above zero and goes all the way to the payment page. It pays nothing and only enters test values. If a step breaks, the alert comes with a screenshot of the failing step. You see at once whether it is the button, the field or the gateway.
Lumi, the Pathly assistant, recognises WooCommerce and builds this Flow in under two minutes. Every suggested Flow is replayed before you see it, and you approve each step. The Pathly module for WordPress also replays the Flow after each update. The possible frequency depends on the plan: the Pricing page gives it.
- Does Flow place a real order?
- No. It stops at the payment page. It pays nothing and only enters test values. Each run leaves a test cart: exclude it from your abandoned-cart reminders.
- Do I need to install a plugin on the shop?
- No. Flow opens the shop from the outside, like a visitor. The Pathly module for WordPress is optional: it adds the replay after each update and the site’s state in the dashboard.
- What does the alert show?
- The step that broke and a screenshot of the page at that moment. You can pass it to the client or to the plugin vendor without rebuilding anything.
- What if the payment provider is the problem?
- Flow sees that too: the provider’s page does not open, or not in time. The screenshot helps tell the shop and the provider apart.