KYB Website Verification: What a Registry Check Misses

KYB website verification is checking what a business's website says and sells, and that it matches the company you verified. A registry proves the company exists. It does not read the site.

Updated

KYB website verification is the part of onboarding that reads the site. The registry says who the company is. The website says what it does.

What each check proves

check proves misses
company registry the entity exists, its owners and status what it sells
owner and sanctions screening the people are who they say the sites they run
bank and credit report the money side the storefront
website verification the site sells what was declared, under the right name, with a checkout who is behind a domain, if no registry link

What to check on the site

From Mastercard’s and Visa’s own lists (Mastercard rules, Visa Acceptance Risk Standards):

  • The site sells only what the application declared, and has a checkout.
  • The merchant name on the site matches the legal entity, and does not belong to another legal entity.
  • The MCC fits what is sold: merchant category code mismatch.
  • Customer contacts work and carry the merchant name.
  • No unrealistic promotions, such as countdown timers.
  • Any other URL that takes payments for the merchant: transaction laundering.

What Mastercard asks at onboarding

Rule 7.1.1 includes: collect and verify information on the entity and each principal owner, and submit a MATCH Pro inquiry that includes the site URL if sales happen on a website or app. Rule 7.1.2 sets the file: keep the records for at least two years after the agreement ends. The list names a site inspection report, date-stamped MATCH Pro records and the merchant’s correspondence.

A dated capture of the live site is the web version of the inspection report. That is our reading, not the rule’s wording.

Where it fails

A site can show the reviewer one page and customers another: website cloaking. Check with the website cloaking checker before you sign.

What we deliver

input the merchant URLs from your applications
output per site: the page as each visitor type sees it, time of capture, where the views differ
format CSV, API or report. You pick
price on request

Details and limits: for acquirers and PayFacs. We are not a Mastercard MMSP.

Merchant monitoring · BRAM monitoring · Shell merchant · How we check websites

Have a batch of applications to check? Contact us.

Questions

What is KYB website verification?

Part of know-your-business onboarding that looks at the merchant's website: does it sell what the application says, does the name match the legal entity, does it have a working checkout and real contact details.

Why is a registry check not enough?

A registry check shows a company exists and who owns it. It says nothing about what the website sells, which other URLs take payments, or whether the site shows reviewers a different page than customers.

What does Mastercard require at onboarding?

Rule 7.1.1 requires the acquirer to collect and verify information about the entity and its principal owners, confirm the business is legal and in the licensed territory, submit a MATCH Pro inquiry that includes the website URL, check merchant names against other legal entities, and assign the right MCC.

How long must onboarding records be kept?

Mastercard rule 7.1.2: at least two years after the merchant agreement ends. The list includes the site inspection report, MATCH Pro inquiry records and the merchant's correspondence.

What do you deliver?

Per merchant URL: the site as different visitors see it, with the time of capture, and where the views differ. CSV, API or report. Price: on request.