Website risk check for merchants starts with one question: does the site show a stranger what it showed your underwriter? We load each merchant URL as different visitors and flag the sites that change. A merchant that shows the underwriter a clean shop and customers something else is website cloaking.
Run it: website cloaking checker for one merchant URL, SMMP trigger checker for Mastercard’s 72-hour triggers. Rules as of 20 Nov 2026.
What an audit or a case asks you to show
| ask | proof | source |
|---|---|---|
| onboarding done right | entity and owner verification, MATCH Pro inquiry with URL, MCC assigned, records kept 2 years after the agreement ends | Mastercard 7.1.1, 7.1.2 |
| ongoing review | periodic review of volume, refunds, fraud, chargebacks, transaction laundering | Mastercard 6.2.2.8 |
| re-screen on change | ownership, country, activities, program cases | Mastercard 7.2 |
| web evidence | web crawling, regular site verification, name and MCC checks | Visa AACQ.C8 |
| BRAM answer | all approved URLs in the merchant record, proof linking a violating URL to the merchant, within 5 business days | Mastercard 8.8.2, 8.8.3 |
Rules that put this on your desk
| rule | what it asks | read it |
|---|---|---|
| Mastercard 6.2.2.8 | periodic reviews of each merchant, including transaction laundering and illegal or brand-damaging activity | Mastercard rules |
| Mastercard 7.2.1 | investigation within 72 hours of a trigger; confirmed scam merchants get blocked: Mastercard SMMP explained | same manual |
| Mastercard 8.8.2 | on a BRAM notice, prove how the violating URL relates to the approved merchant and its URL: BRAM | same manual |
| Visa VARS | use web crawling tools, verify merchant websites regularly, check for name and MCC mismatches | Visa Acceptance Risk Standards |
PayFacs are named in the 72-hour rule and answer for their sponsored merchants: PayFac.
What we deliver
| input | merchant website URLs, one by one or as a list |
| output | per site: the page as each visitor type sees it, with time of capture, and where the views differ |
| views | Googlebot, desktop Chrome, iPhone Safari, Facebook crawler; direct vs ad-click referrer; JavaScript on vs off |
| exit | one datacenter IP (checker). Country and residential views: deep scan |
| format | CSV, API or report. You pick |
| price | on request |
How a check runs, and what it never does (no logins, no personal data): method.
What we are not
We are not a Mastercard MMSP, and a report from us does not replace one. Use our evidence next to your approved MMSP’s, or in your own file: Mastercard MMSP list.
Try it
Run one merchant site through the free website cloaking checker. Same engine.
Sample
[TODO: one real redacted sample report; none published yet]
Want a batch run on your portfolio, scheduled re-checks, or country and residential views? Contact us.
Related: merchant monitoring · transaction laundering · for payment processors
See also: G2 Risk Solutions alternative · merchant descriptor