Treat them as two lists that touch only where a documented dependency says so. WordPress separates switching themes from activating plugins: both are administrator capabilities, and doing one does not do the other. A checkout redesign can still break a payment extension. WooCommerce Checkout Add-ons, for example, is documented as not yet compatible with Cart and Checkout blocks. The WooCommerce Stripe extension shows Apple Pay and Google Pay only when HTTPS, domain registration, and its other stated conditions are met, and those buttons still require the underlying card method. Stage the work when you have no written provider deadline. The provider decides whether the new site must be reviewed and whether the account can change. Prism does not set that deadline or approve the account. Describe the work you need. Prism will confirm scope, responsibilities, fees, and terms before work begins.
For: An owner or authorized representative of a research-use-only peptide business that has both a store redesign and a processing change in progress.
Updated 2026-09-21
A theme change is not a processor change
WordPress gives a single-site Administrator both switch_themes and activate_plugins, and documents them as different capabilities. A redesign that only switches the theme is not, by that fact, a change of payment plugin or payment account. Confirm on the live site which of the two the project actually includes. A proposal that says redesign can still include a new checkout plugin. Read the task list.
WooCommerce payment providers are enabled on their own settings tab. Shipping zones are on another. A visual redesign that does not open those screens leaves the provider list and the shipping methods where they were. A redesign that replaces the checkout does not.
The payment account itself is the provider's. Connecting the WooCommerce Stripe extension attaches a Stripe.com account. WooCommerce says questions about that account's onboarding and Dashboard settings go to Stripe. Redesigning the theme does not submit a new application, and it does not preserve an account the provider has decided to close.
Checkout behavior is the dependency that forces a sequence
WooCommerce's Checkout Add-ons documentation says that, as of WooCommerce 8.3, Cart and Checkout blocks are the default experience, and that this extension has not yet been updated for those blocks. It tells merchants to revert to shortcode checkout until compatibility exists. A redesign that moves a store using that extension onto blocks can remove those fields even though the processor account did not change. Other extensions need their own current page. One extension's block status is not every extension's status.
If the store uses the WooCommerce Stripe extension's express checkouts, the site must be served entirely over HTTPS with a valid certificate. Apple Pay additionally needs port 443, TLS 1.2 or later, and the domain enabled on the Stripe payment-method domains page. The extension creates the Apple domain-association file. Apple Pay and Google Pay cannot be enabled separately in that extension. The card method generally has to be enabled before those wallets show. A redesign that drops HTTPS, changes the domain, or switches checkout can remove the buttons without any decision by the provider about the business.
Those are rendering and compatibility facts. They are not eligibility facts. A button that disappears is a checkout defect to diagnose. A button that appears is not an approval.
A written deadline is the other dependency
Prism's solutions page tells a merchant who is answering a provider to bring the provider's website questions and any stated deadline. The deadline is the provider's date. Prism does not publish one. If the notice requires the site to change before a date, the redesign tasks that the notice names have to finish before that date. Tasks the notice does not name can wait.
If there is no written deadline, you can keep the current checkout running while the new presentation is built, then change payment methods in a separate step. You can also do them together when the same checkout screen is the thing both projects edit. The reason to combine them is a shared file or a shared setting, not a preference for one launch.
Test the payment path you intend to keep before you remove the old one. This page does not claim that WooCommerce provides a staging host. If you have a copy of the site, use it. If you do not, the production sequence has to leave one working checkout until the replacement has taken a test order you can find in the order list.
Who decides the order
You can decide the sequence when no provider deadline names a page, using the extension constraints you have verified on your version. You can assign each task to the person who can actually change that setting: theme, plugin, or provider dashboard.
The provider decides whether a redesigned site needs a new review, whether an account can be opened or kept, and what the fees and reserves are. Prism can discuss the storefront and help connect a provider's website questions to the pages involved. Scope, fees, and terms for that work are discussed before it begins. Confirm any provider-selection assistance separately; staging the work does not guarantee that a provider’s requirements are satisfied.
Unknown without the notice and the plugin list: whether your checkout extension survives the block editor, whether the provider's date applies to the whole site or to one page, and whether the new design changes the domain the wallet registration uses.
Redesign and processing sequence
Put each real task on one row. Do not invent a deadline the provider has not written. Worksheet entries are not submitted by this worksheet or saved by this site. Use only non-sensitive summaries; do not enter credentials, government identifiers, card or bank-account numbers, private receipt links, or customer details.
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.
Redesign and processing sequence. The last column is for temporary notes.
Dependency
Why it picks the sequence
What to read
Your record
Provider deadline in writing
Why it picks the sequenceA stated deadline applies to the pages the provider named. Prism does not add a date.
What to readThe provider's notice. Leave blank if it states no date.
Theme change versus plugin change
Why it picks the sequenceWordPress documents theme switching and plugin activation as separate administrator capabilities.
What to readThe redesign task list, then Appearance and Plugins on the live site.
Checkout type
Why it picks the sequenceCheckout Add-ons is documented as not yet compatible with Cart and Checkout blocks. Another extension may differ. Check the extension you run.
What to readThe checkout screen type and that extension's current compatibility note.
Wallet and domain requirements
Why it picks the sequenceThe WooCommerce Stripe extension requires HTTPS and a registered domain before Apple Pay or Google Pay can display. The buttons are not a processing approval.
What to readWooCommerce, Settings, Payments, Stripe, and one browser that meets the extension's device notes.
Payment provider screen
Why it picks the sequenceProviders are enabled on their own settings tab. A theme-only redesign does not switch them.
What to readWooCommerce, Settings, Payments. Note any provider the project would add or remove.
Account questions versus site questions
Why it picks the sequenceStripe account onboarding and Dashboard settings are Stripe's, not a theme setting.
What to readThe provider dashboard, opened by someone who already has access.
Working checkout until the replacement is proven
Why it picks the sequenceRemoving the current method before a test order exists leaves no documented path to take payment.
What to readA test order you can open in WooCommerce, Orders. Do not use a real customer's card.
Responsible party
Why it picks the sequenceOnly the person with the relevant login can finish the row. A designer login may not be a provider login.
What to readName the person for the theme, the plugin, and the provider account.
These are temporary notes. Leaving or reloading this page may clear them. The consultation form does not include these entries.
Limits
A Prism consultation can help you organize the facts and discuss the website or processing question. The payment provider decides eligibility, pricing, reserves, and whether an account is opened or closed.
Confirm any work schedule and fee in the agreed scope. Project sequencing does not establish processing approval.
A visible wallet button, a new theme, or a research-use-only label does not decide the payment account.
WordPress roles and capabilities — checked 2026-09-21. switch_themes and activate_plugins are separate capabilities. A single-site Administrator has both. Switching themes is not the same capability as activating plugins.
WooCommerce Checkout Add-ons — checked 2026-09-21. As of WooCommerce 8.3, Cart and Checkout blocks are the default. This extension is not yet compatible with those blocks, and the page points merchants to shortcode checkout until it is.
WooCommerce Stripe express checkouts — checked 2026-09-21. Express checkouts require HTTPS and a valid SSL certificate. Apple Pay also requires port 443, TLS 1.2 or later, and the domain on Stripe's payment-method domains page. Apple Pay and Google Pay cannot be enabled separately. The card method generally must be enabled.
WooCommerce settings overview — checked 2026-09-21. Payment providers and shipping zones are configured on separate settings tabs.
Connecting WooCommerce to Stripe — checked 2026-09-21. The extension connects a Stripe.com account. Account onboarding and Dashboard settings are Stripe account questions.
Prism solutions — checked 2026-09-21. A provider follow-up starts from the provider's questions and any stated deadline. The provider decides whether the response meets its requirements. Scope, fees, and terms are discussed before Prism work.
Request a consultation
Describe the business and this specific question. Prism follows up by email to discuss fit and scope. An inquiry is not a processing application or an approval.