Merchant monitoring for payment processors starts with what the merchant’s site really shows. We load each merchant URL as different visitors and flag the sites that change depending on who asks. A merchant that shows the underwriter a clean shop and customers something else is website cloaking.
Two rules that put this on the desk
| source | what it says | read it |
|---|---|---|
| FTC v. Humboldt Merchant Services, order filed 8 Sep 2026 (E.D. Mich., 2:26-cv-13303) | Humboldt must regularly review covered clients’ websites “from an IP address that is not associated with” Humboldt, may use third-party monitoring tools and crawlers, and must save copies of the sites (Section IV.B.1). A chargeback investigation must also review the client’s sites from such an IP (IV.E.4) | order PDF |
| Mastercard Security Rules and Procedures, Merchant Edition, 4 Aug 2026, rule 7.2.1 | Within 72 hours of a trigger, an acquirer or payment facilitator must start an investigation of a potential scam merchant (card-not-present). If confirmed, it must block authorization. One trigger is an alert from a Merchant Monitoring Service Provider (MMSP) | rules PDF |
Details:
- Humboldt: the FTC says it will pay $12 million, and its complaint alleges it processed payments for more than 1,000 merchants that were shell entities, fronts for fraudulent companies (FTC case page). The case page lists the order as entered by the court. It binds Humboldt, not the industry. It does not say why the IP matters; the reason is the pattern in IP-based cloaking.
- Mastercard: other triggers in 7.2.1 are an approval-rate collapse (down 50 points in 72 hours, or below 30%, with at least 25 purchases), a GRIP letter, and for entities with six months or less of history, scam reports from two issuers, scam chargebacks, or more than 5% refunds and chargebacks over 500 purchases. Mastercard also recommends acquirers use a merchant monitoring tool. The rule is introduced in Mastercard’s own words: “requiring acquirers and payment facilitators to actively monitor merchant behavior and to initiate an investigation within 72 hours” (Mastercard).
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, and where they 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 | [TODO: report / CSV / API] |
| price from | [TODO: price per merchant per month; confirm with operator] |
We are not a Mastercard MMSP. We produce website evidence your risk team, or your MMSP, can work from.
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, scheduled re-checks, or country and residential views? Contact us.