Starting constraint
The vendor mailed a mandatory security release for shops below a stated plugin version. The client forwarded the notice the same morning. Checkout had to keep working; no config rewrite was in scope.
The commercial risk was a silent checkout break after the bump, not a store redesign.
Diagnosis
This was a security fix on the payment plugin path. The changelog and vendor notice named the minimum safe version and warned against side-loaded packages.
Staging was not required for a patch-level bump with a known changelog when a recent backup and a post-update test payment were available.
Architecture decision
Stay on the official WordPress.org package. Refuse any plugin zip attached to email, even when the vendor brand appears in the message. The vendor itself warns that it never sends plugin files by email or asks for shop credentials.
No payment settings rewrite. Update in place, then verify the installed version in Plugins.
Delivery model
Client forwards vendor mail. Backup first. Live update from WordPress.org to the required version. One test payment. Reply the same morning with the installed version and confirmation that the shop works.
Elapsed time from forward to confirmation was under an hour.
Outcome band
Plugin at the required security version the same day. Checkout confirmed working. No downtime reported by the client.
Reusable lesson: care retainers earn their keep on vendor security notices. The value is the same-day patch plus a real checkout smoke test, not a ticket sitting in a queue.