Do not remove an old gateway while old orders still depend on it

Separate the checkout choice from the installed extension

A payment method no longer offered to new buyers can still have a job in the administration of earlier orders. In its guide for switching to WooPayments, WooCommerce tells merchants not to deactivate the old gateway plugin while refunds and other actions on orders placed through it are still needed. It describes disabling the old method at checkout instead, preserving the plugin for those administrative operations.

Use that guidance only for the transition it documents. Identify the old gateway extension and the destination setup before applying it. Another gateway or platform needs its own instructions. Do not turn a general cleanup task into permission to delete software merely because the replacement checkout appears to work. Equally, do not infer that keeping a plugin active requires continuing to offer its method to new buyers.

Build the dependency list from the old orders

Locate the real order cohort that used the old gateway and compare it with outstanding refund requests and support cases. Use the payment method recorded on each order or the associated provider record to establish the cohort. The date of the store change can help locate records, but a date alone does not prove which gateway took a particular order.

For each remaining operation, record where staff would perform it, which extension supplies that action and which authorized account role is needed. Distinguish an action in the store from access to the provider’s own records. Mark dependencies unconfirmed when nobody has checked the installed extension’s documentation or the actual order. The aim is to explain exactly what a deactivation would remove from the team’s workflow.

Record whether a provider-side alternative is documented and available to the authorized owner, but do not assume that one exists or that it reproduces every store action. An old-order case is not resolved simply because its handling might be possible elsewhere. If another route is established, retain the association between the order, its original payment and the responsible person.

Use system status as an installation record

WooCommerce’s system status report lists site addresses, WordPress and WooCommerce versions, plugins and their versions, template overrides and the assigned cart and checkout pages. Use a dated report to identify the installation and extension being discussed. This prevents a retirement decision from referring only to a plugin name that might exist on several sites or in different versions.

The report is a snapshot of configuration. An active-plugin entry does not establish that a particular refund is available, that the provider account remains accessible or that all old-order cases are closed. Compare the report with the real dependency list and the applicable gateway guidance. Record role ownership and access availability without copying credentials or a complete system report into a public inquiry.

Define the condition that would permit retirement

WooCommerce advises keeping the old plugin active for at least a few months in the documented WooPayments transition. That wording does not supply an exact calendar removal day and does not resolve your remaining orders. Set a condition that identifies the operations still dependent on the plugin, how each will be completed or handled through a verified route, and who is responsible for checking the condition before the change.

Keep the proposed retirement pending while any necessary operation still relies on the extension or has no confirmed owner. An empty queue today is evidence about known cases today; it is not proof that no later support need will arise. Retain the relevant order history and provider guidance as part of the decision, and make clear which future access assumptions remain unresolved. Plugin retirement and closure of the processing account require separate decisions.

A Prism checkout-review consultation can start from the website, research-only products, exact extension and unresolved old-order dependency. Describe the requested assistance so scope, responsibilities, fees and terms can be confirmed before work. The provider decides account terms; leaving a plugin installed does not preserve account rights or establish approval. The public form starts an inquiry with email follow-up, not a purchase, appointment or processing application.

Gateway retirement dependency

Complete this for the old gateway and repeat the affected-order and operation checks for each distinct dependency. Keep order details in authorized systems; enter cohort descriptions, roles, availability and conclusions here. Retirement remains pending wherever an operation lacks a confirmed route.

Worksheet entries are not submitted by Prism’s worksheet and are not saved by the site. Use record types, availability, anonymized observations, or match/mismatch results. Do not enter government identifiers, customer names or addresses, customer messages, receipt-access links, card or bank details, passwords, or keys. Send sensitive documents only through the provider’s verified secure channel.

These are temporary notes. Leaving or reloading this page may clear them. Worksheet entries are not sent automatically. If you copy notes into the consultation message and submit the form, Prism receives them as part of your request.