Responding to a processor's website request

Start from the sentence the provider wrote

A usable response follows the notice, not a guess about what the provider meant. Copy each distinct issue into its own row: a product description, a policy, a missing contact detail, a page that will not load, or a claim the provider named. Keep the deadline if the notice states one. Do not add a deadline the notice does not contain.

Prism's solutions page says to start with the provider's exact request and to bring the website questions, any stated deadline, and the links to the pages involved. That is the shape of the work. It is not a finding that any particular change will satisfy the provider. The same page says to agree whether follow-up review is included before work begins, and that the provider decides whether the response meets its requirements.

Tie the issue to one URL and one owner

Each issue needs the public URL a reviewer can open without a password, plus the person who can edit that page. If the notice names a banner, a policy, and a product page, those are three issues even when they share a theme. A homepage disclaimer does not change the product page the notice named.

Stripe's business-website article says that if you use a website to sell, Stripe reviews it to understand what is sold, and that you must keep a functioning site with the required information. It says the business name and the descriptions of the goods or services must align with the information given to Stripe. It also lists customer-service contact details, a return policy when physical goods are sold, a refund and dispute policy, a cancellation policy if applicable, legal or export restrictions if applicable, and promotion terms. Use that list only to understand a Stripe request that names those items. If your notice asks for something else, the notice controls.

The same Stripe article says a page must load without a password, and that an under-construction site may not activate an account until the products being sold are listed. Those are Stripe's activation examples. They do not tell you to hide a product that is for sale.

Evidence is the page a reviewer can open

Before a change, save the URL and a description of the words or image the notice is about. After the change, save the same URL and the date the new version was public. The evidence is the published page, not an intention to edit it later. If a developer, a theme, or a policy page also has to change, the issue is not finished when only one of them changes.

Prism's features page says a website review can look at product descriptions, marketing claims, store policies, and business disclosures, including statements that conflict with the product description. The pages and questions are agreed before work begins. Findings, when reporting is included, are informational. They are not a legal opinion or a compliance certification, and a website review does not guarantee approval or continued processing.

A research-only sentence does not erase a conflicting claim on the same page. If the notice is about that conflict, the response has to show the conflict is gone, not that a new sentence was added beside it.

What you can close, and what the provider still decides

You can decide whether the notice is specific enough to act on, who will edit the page, and whether the published page now matches the change you intended. If the notice is too vague to point at a URL, the next step is a written question to the provider, not a broad rewrite.

You cannot decide that the provider will accept the change. Stripe says it regularly checks the website it was given and, if it detects an issue, you need to update the site or provide another site that meets the requirements. That is Stripe's process. Another provider's acceptance rule is whatever that provider wrote. Confirm who will implement the change and who will send the response; the provider decides whether the response meets its requirements.

Whether a later consultation includes a follow-up look at the published pages is agreed before work, not assumed from this guide. There is no published Prism response time.

Website-request register

Use one row for each distinct issue in the notice. Leave a cell blank when the notice, the page, or the provider's later reply does not answer it. Do not paste account credentials or customer records.

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.