Merchant Onboarding Website Check (Free)

Merchant onboarding website check: enter a merchant's URL and get a pass, warn or fail checklist with the evidence, plus one line: normal shop, thin or new shop, or red flags.

Ready. Enter the merchant's website, tick the box, press the button.

Merchant onboarding website check: enter a shop’s address, get a checklist an acquirer, PSP or shopper can read in a minute. Background: merchant monitoring.

What we check

check pass when
Reachable, HTTPS the home page answers 2xx on https and stays on its domain
Domain age the first public certificate is 90 or more days old
Same page for bots and ads Chrome, Googlebot and an ad click get the same page (cloaking)
Bot protection no challenge page blocks the read
Looks like a shop cart or checkout wording, and prices
Policy pages home page links refund, terms, privacy, contact (and shipping for a shop)
Policy text up to 3 pages load, none is a copy of another or of the home page, no template placeholder such as [Your Store Name]
Contact details email, phone and street address in the text (free-mail only is a warning)
Company name and number a legal name and a registration or VAT number
Payment brands Visa, Mastercard, PayPal and similar named; crypto, Zelle or bank transfer only is a fail
Checkout stays on the site no cart, pay or order link leaves the domain, known payment providers aside
Title matches the domain the name in the title is in the address; a big brand plus “official” on another domain is a fail

What comes back

  • One line: looks like a normal shop, thin or new shop (check by hand), or red flags.
  • A table: each check with pass, warn, fail or skipped, and what we saw.

On a site that sells: two fails give red flags. On any site: a cloaking diff, a template placeholder or a fake-brand title do too. One fail, three warnings, or an unreadable site give thin or new.

Limits

  • One datacenter location, no JavaScript run, home page plus up to 3 policy pages.
  • A shop built in the browser looks thin. Look at the warnings, not only the verdict.
  • Domain age is the first public certificate, not the registration date.
  • 5 checks per visitor per day, 6 per site per hour. Public addresses only.

Need every merchant in a portfolio reviewed, with owners, products and history? Ask for a full review.

Questions

What is merchant onboarding?

It is the checks an acquirer or payment facilitator runs on a business before it may take card payments: who owns it, what it sells, and what its website shows. This tool covers the website part.

How do I verify a merchant's website before onboarding?

Check that the site loads over HTTPS, has refund, terms, privacy and contact pages, names the company with a registration or VAT number, shows real contact details, sells what was declared, and shows the same page to everyone. The table does these checks in one run.

Is this online store legit?

The result says if the site looks like a normal shop, a thin or new one, or has red flags. It cannot prove a shop is real. For a shopper's version of the same checks, read how to spot a fake online store.

How old is the domain?

We read the first certificate issued for the name in public certificate logs. It is a floor, not the registration date: the name can be older than its first certificate.

Why does a good shop show warnings?

The checks read only the home page and up to 3 linked policy pages, with no JavaScript run. A shop built in the browser, or with its policies in a pop-up, looks thin to a plain fetch. Open the warnings by hand.

Can I use it as my only check?

No. It is a first look at the site from one datacenter. It does not check owners, sanctions lists, transactions or the products behind the cart.

How often can I run it?

5 checks per visitor per day, and 6 per site per hour.