Planning a voluntary provider switch while the account is healthy
Start with the current agreement’s notice method and renewal provisions, then choose a provisional cutover date that can move until the replacement is approved for the disclosed business and actually ready. Keep the last day for new payments, contractual termination and eventual account closure as separate milestones. Export needed records while access is normal and assign someone to old refunds, disputes and balances after the checkout changes. If a contract window arrives before replacement readiness, record the conflict and decide what to defer or clarify; do not manufacture an approval date to make the calendar fit.
For: An owner of a research-only business considering a voluntary provider change while the current account continues to work.
Find the dates your current agreement actually creates
A voluntary switch begins with a choice, not a closure notice. Write down why you want to leave and what operational condition the replacement must meet. This prevents a preferred date from becoming a deadline simply because it appeared on an internal calendar.
Locate the agreement that applies to the existing account, its service terms, regional terms and any relevant written amendments. Extract the term end, any renewal window, any notice period, the required notice channel and the rule for when notice is treated as received. If the agreement does not state a renewal window, mark that fact as unconfirmed rather than importing one from another merchant’s contract.
The Stripe Services Agreement checked on September 29, 2026 combines general, service and incorporated terms, with regional terms depending on account country. Its notice provisions distinguish channels and deemed receipt. That is a reason to read the applicable documents together. It is not a universal notice period, nor a reason to use a fee-change period as the deadline for a voluntary termination. If a clause’s meaning is disputed, identify it for qualified advice before relying on your interpretation.
Make readiness a condition of the chosen cutover
Keep your desired switch date labeled provisional. Before treating it as the day new orders change providers, require the new provider’s written approval for the actual business and the specific payment service, plus evidence that the intended store connection is ready. A sales estimate of onboarding time is neither approval nor a verified store milestone.
Have the person responsible for the real integration identify the installed platform and gateway, the account connection and the remaining acceptance checks. Record what has actually been verified and what is still open. A configured plugin does not establish underwriting approval; written approval does not establish that the checkout connection works.
If readiness is incomplete as the notice window approaches, put both facts on the ledger. Options to evaluate include moving the discretionary cutover, retaining the existing arrangement under its actual terms, or asking whether the provider will agree to a different date. Record any charges only from the agreement or written quote. Do not describe an overlap, an extension or uninterrupted acceptance as agreed until its dependencies are established.
Schedule the old account’s continuing work
The day you stop sending new payments to the old account need not be its closure date. Identify the person who will still monitor its balance, refunds, disputes and correspondence. Record the access that person needs and the next review date based on actual open items. A blank register today does not prove no later dispute or refund request can arrive.
Stripe’s owner-closure guidance says an account cannot be closed with an existing balance. Its refund and dispute guidance says the owner remains responsible after closure and suggests leaving the account dormant when further activity may need attention. The current Stripe agreement also describes debit authorization that can survive account closure until amounts are paid. These are separate reasons not to treat a checkout cutover as proof the financial relationship has finished. Other providers’ conditions must come from their own documents.
Export needed records while access is normal, then note any later activity that requires an additional export. Assign a separate decision for final closure after reviewing balances, access and remaining duties. No fixed number of days on this page ends that responsibility.
Separate hiding an old method from removing its plugin
For a WooCommerce store switching to WooPayments, WooCommerce’s guide says to keep the old gateway plugin active while refunds and other actions on its old orders are still needed. The guide distinguishes disabling the old payment method at checkout from deactivating the plugin. That allows the switch in what new buyers see to be considered separately from the administrative dependency of existing orders.
The guide’s suggestion to keep the plugin for at least a few months is not a removal date for your calendar. Record the outstanding old-order actions and the account access they need. For a different destination gateway or platform, obtain the matching vendor instructions instead of copying this WooPayments procedure.
Keep the final decision in three parts: the documented contractual route, the readiness condition for new payments, and the continuing owner of the old account. A scoped Prism processing consultation can help organize the business facts and provider questions. Identify the transition assistance you want so scope, responsibilities, fees and terms can be confirmed; Prism’s public material supplies no transition calendar or uninterrupted-access guarantee.
Voluntary-switch date ledger
For each row, record the document or real observation, date and time zone if stated, responsible person, and whether the milestone is confirmed or provisional. Keep contractual dates separate from dates you choose. A missing dependency leaves the affected milestone open.
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.
Voluntary-switch date ledger. The last column is for temporary notes.
Milestone
Evidence and who controls it
What prevents confirmation
Your date, owner and status
Current notice period and renewal window
Evidence and who controls itThe applicable agreement and amendments; capture the clause, notice method and receipt rule.
What prevents confirmationAn assumed period, missing regional term or unresolved meaning. Do not substitute another provider’s deadline.
Notice preparation and submission
Evidence and who controls itThe merchant controls preparation; the agreement supplies the channel and effect of notice. Preserve the actual sent record.
What prevents confirmationAn internal reminder or draft is not sent notice, and sending alone does not establish receipt under every agreement.
Replacement approval
Evidence and who controls itThe new provider’s written decision for the legal entity, complete catalog, countries, channel and service.
What prevents confirmationA general sales estimate or an open condition does not confirm account readiness.
Chosen cutover for new payments
Evidence and who controls itThe merchant chooses the target with the responsible implementer after approval and actual readiness are established.
What prevents confirmationAn incomplete connection or unverified acceptance behavior keeps this date provisional.
Record export while access is normal
Evidence and who controls itThe authorized account user exports and opens the required files; note the period covered.
What prevents confirmationA download not checked for coverage, or subsequent activity not yet included, leaves an archive gap.
Old refund and dispute work
Evidence and who controls itThe old provider’s records, access conditions and assigned merchant owner.
What prevents confirmationNew checkout availability does not close old cases or set a final date for later activity.
Gateway retention and eventual account closure
Evidence and who controls itThe actual gateway dependencies, account balance and applicable closure terms.
What prevents confirmationFor a WooPayments switch, checkout visibility and old-plugin activation are separate; Stripe closure requires balance conditions to be addressed.
Date conflict or gap
Evidence and who controls itCompare the contract window with the replacement’s still-open dependencies and any written extension.
What prevents confirmationDo not fill the gap with a hoped-for approval. Record the decision to defer, clarify terms or plan for the unresolved interruption.
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.
Limits
This is planning from records, not an instruction to submit notice, close an account or change a live checkout.
No cure period, regional notice period or plugin-retention interval is presented as a universal switch deadline.
Stripe closure rules concern Stripe’s owner-close flow. WooCommerce’s cited procedure concerns switching to WooPayments and does not establish merchant eligibility.
Keep credentials, bank details, card data and customer records out of the worksheet and public consultation form.
Stripe Services Agreement general terms — checked 2026-09-29. The agreement combines general, service and incorporated terms with account-country regional terms. Notice channels and deemed receipt are distinct; debit authorization can survive closure until amounts are paid. The clauses do not establish this merchant’s switch deadline.
Stripe: Close an account with an existing balance — checked 2026-09-21. Stripe’s owner-close flow does not allow closure with an existing balance; negative and positive balances must be addressed, and scheduled payouts continue.
Stripe: Refunds and disputes after closing — checked 2026-09-21. Stripe says the owner remains responsible for refunds and disputes after closure and suggests leaving the account dormant when activity may remain.
WooCommerce: Switching to WooPayments — checked 2026-09-21. For a WooCommerce switch to WooPayments, keep the old gateway plugin active for old-order actions and disable the method at checkout instead; the retention guidance supplies no calendar removal date.
Prism solutions — checked 2026-09-21. The provider decides eligibility and account terms. Prism agrees scope, fees and terms before work and publishes no transition calendar or uninterrupted-access guarantee.
Discuss my processing options
Want to talk through your own processing situation?