There’s a standing rule on the shops I look after: I don’t update payment gateway plugins on a Friday.
It isn’t superstition. It’s the one change that can stop a shop taking money, at the worst possible moment, when the people who could help you are already finishing for the week.
I wrote earlier about not hitting Update on a Friday afternoon in general. This is the narrower version of that rule. Themes, shipping plugins and most "nice to have" updates can wait. A payment plugin sits on the path that turns a basket into an order. That makes it different.
Why payment plugins are different
Most plugin updates change something you can live without for a weekend if it goes wrong. A payment gateway update can change how the shop talks to Stripe, PayPal, Klarna, or whoever handles the card.
When that talk fails, customers see a vague error, a spinning button, or a checkout that never finishes. They don’t email you a tidy bug report. They leave. Some try again later. Some buy somewhere else. You only find out when Monday’s order list looks thin, or when someone messages to say their card was declined three times and then went through on a competitor’s site.
Payment plugins also sit next to credentials, webhooks, 3D Secure flows and refund paths. A small change in any of those can look fine on a quick glance at wp-admin and still fail for a real customer with a real card.
Why Friday makes it worse
Support is thin over a weekend. Hosting chat slows down. Gateway support queues stretch. Plugin authors don’t usually reply until Monday. You’re more tired than you think at twenty to five on a Friday. So is the shop owner.
If checkout breaks on a Tuesday morning, you’ve got the day. You can roll back, dig into the logs, place test orders, and call people who are still at their desks. If it breaks at 4:40pm on a Friday, you’re choosing between leaving a live shop half-broken for two days, or spending the weekend on it.
In November that choice gets sharper. Black Friday is close. A quiet weekend of lost orders is bad enough in March. Three weeks before the biggest sale of the year, it’s the last thing a client needs.
What the rule actually covers
The rule is about curiosity updates and "while I’m here" clicks. An update notification is not the same as an emergency.
If there’s a real security fix for a payment plugin on a Friday afternoon, we look at it properly. We read what it fixes. We take a backup. We update on staging first where we can. We test checkout with each live payment method. Then we decide whether to go live the same day and stay reachable. Ignoring a known vulnerability because it’s Friday isn’t caution. It’s gambling the other way.
Everything else waits for early in the week.
What I do instead
On a normal week, payment gateway updates go into the same maintenance window as the other careful work:
- Backup first. Files and database, somewhere that isn’t only the same server, with the latest order number noted so I know what came in after.
- Staging before live. Update the payment plugin on a staging copy with gateways in test or sandbox mode, and with emails blocked so no real customer gets a test order.
- One change at a time. I don’t stack a WooCommerce update, a theme update and a gateway update in the same breath. If something breaks, I want to know which change did it.
- Smoke-test the money path. Add to cart, apply a coupon if the shop uses them, choose shipping, and pay with each method that’s switched on. Then check the order email, the thank-you page, and the order in wp-admin. If the shop uses subscriptions, deposits or saved cards, those get a pass too.
- Go live early in the week. Prefer Tuesday or Wednesday mornings. Leave Friday for watching, not tinkering, unless something is actually on fire.
If you’re heading into a sale, this sits next to a feature freeze. I wrote about that in Feature Freeze Before Black Friday. New features wait. Non-urgent payment plugin updates wait with them.
What I tell clients
I say it early, kindly, and in writing. Non-urgent payment updates wait for the next maintenance window. Security patches that are genuinely urgent get done when they’re urgent. "I saw an Update button and felt productive" is not urgent.
Most clients are relieved once they hear it. The Update button feels like progress. A broken checkout over a weekend feels like the opposite.
If a payment method already looks flaky, that’s a different job. I’ll dig into logs and gateway settings rather than hoping a Friday update fixes it. I’ve written before about debugging WooCommerce payment gateways when customers can’t check out and you need visibility.
Wrap Up
I don’t update payment gateway plugins on a Friday. Checkout is the one thing a WooCommerce shop can’t afford to break when support is thin and the weekend is already starting. Batch the careful updates earlier in the week, test the money path properly, and leave Friday alone unless there’s a real security reason not to.
If your payment methods feel fragile going into November, or you want a second pair of eyes before Black Friday, book a quick call and tell me what’s going on. You can also read more about how I work as a WooCommerce developer.
Written by Connie, an AI, from Neil Matthews’ notes, archive, and direction. Neil directed and edited this piece. He did not write these words. Augmented publishing by Neil Matthews.