Check your homepage claims before someone reviews them

Start with the URL you supplied to the provider

Start with the URL you supplied to the provider, then check the homepage if it is a different page. The page on the application is the one you can check first, on your own schedule. How any given reviewer works through a site is that reviewer's process, and this page does not describe it. The self-check is worth doing either way, because the entry page compresses the store's claims about itself into one place.

Stripe's business-website article says Stripe reviews the website to understand what is sold, that the business name and the descriptions of goods or services must align with the information given to Stripe, and that the site must load without a password. It also says an under-construction site may not activate an account until the products being sold are listed. Those are Stripe's activation statements. They are a useful checklist for any entry page, but they decide nothing for a provider that is not Stripe.

List the claims before you judge them

Open the page and write down every statement that describes the business: the headline, the audience it names, the product or category framing, any banner or promotion, the business identity in the header and footer, and the policy and contact links. Include what images and buttons say, not only paragraphs.

Keep the exact wording, and mark each statement as a factual claim or as ordinary descriptive wording. A paraphrase lets you soften a claim without noticing. If the page says nothing about who buys, write that too: an absent audience statement is a fact about the page. Stripe's prohibited-and-restricted FAQ says peptides sold with no purpose specified are assumed to be sold for human consumption, so a blank purpose is not a neutral description under that Stripe document. The FAQ does not classify your store, and it does not tell you to invent an audience to fill the blank.

Compare each claim with linked content and with records

Linked content is the first place a claim can be checked. The category page behind a product-framing claim, the policy behind a shipping promise, and the about or contact page behind the business name are all places a statement can be confirmed or contradicted. Open each one and ask whether it says what the entry page says it says.

A claim whose link contradicts it is a factual conflict with both URLs on record: a homepage that frames products for research buyers linking to a product page that describes personal use, or a footer naming one company while the contact page names another. A claim with no link is different: the support may sit in the business's own records rather than on a public page, and a missing link alone is not proof a claim is unsupported. The statement that earns a correction is the one that neither linked content nor any record you can produce supports.

A research-only sentence on the entry page does not repair a contradicting sentence at the destination.

Identity and contact details are claims too

The business name, the support channel, and the policies in the footer are part of what anyone verifying the store will look for. Stripe's website article lists customer-service contact details, a return policy when physical goods are sold, a refund and dispute policy, a cancellation policy if applicable, applicable legal or export restrictions, and promotion terms among the items a site can be asked to show. Use that list to understand a Stripe request. For any provider, the underlying point holds: those disclosures should be reachable from the storefront's entry page.

Check that the entity named on the page is the entity on the application, and that the contact path actually works. Do not publish a home address, a government identifier, or a tax number to force the pages to match, and do not rename the public business so it stops matching the application.

What you can fix, and what a review adds

You can correct a contradiction you control: the headline, the banner, the link target, the policy page, the footer identity. You can also decide which claims you cannot yet support and take them down rather than defend them. What you cannot do is decide that the corrected page satisfies a provider. The provider reads the storefront and the application under its own process, and a tidy homepage is not an approval.

Prism's features page describes a review of product descriptions, marketing claims, store policies, and business disclosures within an agreed scope, with findings that are informational and not a legal opinion or a compliance certification. Bring the entry URL and the map you built. The review examines the pages named in the agreed scope; the provider still decides eligibility and account terms.

Homepage-to-destination statement map

One row per claim on the live entry page. Copy the exact wording, open the linked content, and check your own records before judging support. A missing link alone is not proof a claim is unsupported.

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.