Website acceptance and provider approval are separate decisions

Keep two completion records

Use the project acceptance record to establish which website deliverables the merchant accepted, on which date and against which scope. Use the provider record to establish what the provider requested and what it has actually decided. These records can have different dates and different owners without either being incorrect.

Compare each claimed account outcome with its evidence. A contractor’s statement that the site is ready describes the contractor’s work unless it points to a separate provider decision. If the provider record contains an unresolved request, keep that request open. If no current provider record is available, describe the account outcome as unconfirmed; do not invent a pending requirement or label the account declined.

Match the website response to the question that was asked

Stripe’s website activation guidance says the business identity and product descriptions must align with information supplied to Stripe. It also addresses the catalog, contact and policy information, and access without a password. Those are concrete website subjects a project can address. They do not establish that Stripe has accepted the resulting response.

For a website request, connect the provider’s wording to the exact public URL, the accepted correction and the version that is currently visible. Then record whether the authorized owner submitted that response through the requested channel and whether a provider reply exists. A published correction, a submitted response and an affirmative provider answer are three different pieces of evidence. Preserve any remaining conditions in the reply rather than reducing the message to a single approved label.

Route the remaining question to the right owner

For the documented WooCommerce Stripe extension, WooCommerce support covers extension installation, connection, webhooks and checkout behavior. Stripe handles account onboarding and verification, business details, compliance requirements, payout settings and Stripe Dashboard questions. A successful connection therefore does not close a question that belongs to Stripe’s account team.

The extension also reports Payment, Payout, Webhook and Sync status separately. Record the specific status relevant to the open question instead of treating one connected indicator as a summary of the account. For a different gateway, use that provider’s account record and support boundary. Give the authorized merchant contact the provider question; give the website maintainer any exact page or integration task that remains within the agreed scope.

Close the handoff with an action the owner can take

The next action should follow the gap: verify the published page when the correction is uncertain, submit the documented response when it has not been sent, or request clarification of the remaining account requirement when the provider’s answer is incomplete. Record the owner and any deadline actually stated by the provider. A desired launch date does not supply an approval date.

For a Prism checkout-review consultation, summarize the accepted website scope, affected public pages and unresolved provider question. Prism’s published support includes storefront review, processing preparation and help with a provider’s website questions; scope, responsibilities, fees and terms are discussed before work. The provider decides eligibility and account terms. The contact form takes the website, products and question, with follow-up by email; leave out passwords, card data and customer records. A request does not book an appointment, buy a service or submit a processing application.

Website-to-provider boundary

Complete this after reading both the accepted project scope and the latest provider record. Use public URLs and non-sensitive document references. Mark an absent provider answer unconfirmed. Website delivery and provider response should each retain their own status.

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.