Prepare the technical handoff from a website agency
The agency can list facts the store already records: the site addresses, the software versions, the active plugins, the theme, any checkout template overrides, the checkout page, and whether that page uses the Checkout block or the classic shortcode. Those facts describe the installation. They do not establish that a provider will process the account. You can ask for this brief and mark every item the agency cannot confirm. The provider decides eligibility. Send a summary in the consultation message. Do not send API keys, a system-status file that you have not reviewed, or a customer list through the public form. Describe the work you need. Prism will confirm scope, responsibilities, fees, and terms before work begins.
For: A research-use-only peptide merchant, or an agency that merchant has authorized, preparing technical facts for a processing conversation.
Updated 2026-09-21
Copy the status report instead of describing the store from memory
WooCommerce's system status report is a configuration snapshot. It includes the WordPress address and the site address as separate fields, the WooCommerce version, the WordPress version, whether multisite is enabled, the active plugins and versions, the theme name and version, whether the theme declares WooCommerce support, template overrides, the currency, and the page identified as checkout. An agency that maintains the site can copy those values. A remembered version number is not the same fact.
The report is for troubleshooting. It can also contain server paths and environment detail. Read it before anyone forwards it. The public consultation form is for a summary of the website, the products, and the question. It is not the place for a raw report, a log, or a credential.
Name the checkout type from the page, not from a plugin slogan
WooCommerce stores started after version 8.3 use the Cart and Checkout blocks by default. An existing store may instead use the classic shortcode. The cart and checkout documentation shows the page editor control that transforms a Checkout block into the classic shortcode, and it says the two pages work as a pair. The agency can say which one is on the live checkout page.
An extension's compatibility with the blocks is marked on its WooCommerce.com product page. If the only enabled payment gateways are incompatible with the Checkout block, no payment method is available. The handoff should name the payment plugin from the active-plugin list and say whether a compatibility warning is visible. It should not say that the plugin 'works with payments' without those two facts.
Customizations are the overrides and extensions the report can show
The status report has a section for files that override WooCommerce templates, and it notes outdated overrides. A checkout template override means the theme, not only a plugin, is part of the checkout. The active-plugin list is the list of extensions actually installed. An agency's description of a customization should point to one of those entries, or be labeled as something the report does not show.
Payment gateways, the status report says, can use cURL to communicate with remote servers to authorize payments. The plugin on the store and the company that receives that communication are different. The handoff names the plugin. The contract or dashboard names the company. If the agency does not have the contract, it leaves the company unconfirmed.
Unresolved items stay unresolved
The brief should include a technical contact and a list of dependencies the agency has not finished: an incompatible extension, an outdated template, a checkout type nobody has checked, or a provider account the agency cannot see. Guessing a version or a provider to make the brief look complete creates the wrong conversation.
You can decide whether the brief is complete enough to send. The agency can confirm only the access it has. The provider decides whether the described store can be considered for processing. Technical compatibility is not that decision. Prism can discuss the storefront and the processing question in a consultation. Scope, fees, and terms come before work. Confirm any agency relationship and implementation scope directly with Prism. A complete handoff does not guarantee a processing account.
Technical handoff brief
The agency fills the last column from the live store. You review it before using any of it in a consultation message. Leave a row blank when it is not confirmed. Do not paste keys or customer data. 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.
Technical handoff brief. The last column is for temporary notes.
Technical fact
What to copy
Why a guess causes the wrong conversation
Confirmed value
Site addresses
What to copyThe WordPress address and the site address from the system status report, kept as two fields.
Why a guess causes the wrong conversationOne remembered domain can hide a difference between the admin address and the public address.
Platform and versions
What to copyThe WordPress version, WooCommerce version, and whether multisite is enabled, copied from the status report.
Why a guess causes the wrong conversationA proposal or an old invoice is not the installed version.
Payment plugin
What to copyThe active payment plugin's name and version from the active-plugin list.
Why a guess causes the wrong conversationThe plugin name is not the legal name of the company that processes payments.
Theme and template overrides
What to copyThe active theme, its version, whether it declares WooCommerce support, and any checkout template overrides.
Why a guess causes the wrong conversationA checkout problem can sit in an override. Omitting the theme makes the checkout look like a plugin-only change.
Checkout page and type
What to copyThe checkout page recorded in the status report, and whether that page uses the Checkout block or the classic shortcode.
Why a guess causes the wrong conversationSaying the store uses WooCommerce checkout does not say which checkout is installed.
Currency shown by WooCommerce
What to copyThe currency field in the status report. The report describes it as the currency in which prices are displayed and payments are processed.
Why a guess causes the wrong conversationThat field is not the bank settlement currency and not a list of customer countries.
Compatibility warning
What to copyWhether the checkout screen warns that an enabled gateway is incompatible with the Checkout block, and the extension named in that warning.
Why a guess causes the wrong conversationA missing warning is not a provider approval. A warning is not a decline of the business.
Technical contact
What to copyThe person who can explain the items above, and whether that person is the merchant or the agency.
Why a guess causes the wrong conversationA company name with no person leaves the next question with nobody.
Unresolved dependency
What to copyAny extension, override, checkout type, or provider account the agency could not confirm.
Why a guess causes the wrong conversationFilling the gap with an assumption sends the processing conversation to the wrong system.
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.
A complete technical brief is not a processing application and does not mean a provider will accept the account.
Do not include API keys, passwords, raw logs, or customer lists.
WooCommerce system status report — checked 2026-09-21. The report lists separate WordPress and site addresses, versions, multisite, active plugins, theme support, template overrides, currency, and the checkout page. Payment gateways can use cURL to reach remote servers. The report is a troubleshooting snapshot.
WooCommerce cart and checkout blocks — checked 2026-09-21. Stores started after WooCommerce 8.3 use the blocks by default. The classic shortcode is a transform of those blocks, and cart and checkout are changed together. Incompatible gateways may leave no payment method. Compatibility is marked on the extension product page.
Prism solutions — checked 2026-09-21. Prism can help prepare for a processing review or connect a provider's website questions to the pages involved. The provider decides eligibility and terms. Scope, fees, and terms are discussed before work.
Prism contact — checked 2026-09-21. The message should include the website, the products, and the question. Card details, passwords, and customer records are left out. The request does not submit a processing application.
Prism features — checked 2026-09-21. A website review does not guarantee approval or continued processing. Findings are informational, not a compliance certification.
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.