Merchant Monitoring Providers: White-Label Hard-Target Crawl

Merchant monitoring providers send us the merchant URLs their crawler fails on or sees only clean. We load them as different visitors and return captures and a diff, under your brand.

Merchant monitoring providers own the crawler, the merchant list and the Mastercard report. What breaks is the URL the crawler cannot read, or reads as clean. That is the part we take: a white-label hard-target crawl with evidence, which we call Cloak-Diff.

The gap, in your words and Mastercard’s

  • G2 Risk Solutions: many high-risk industries block crawlers with DDoS protections or restricted member-only areas (G2 Risk Solutions, 2025).
  • Mastercard’s rule: monitoring covers the payment page and restricted members-only areas, unless the law prohibits it (8.9.1, Mastercard rules).
  • A site that serves the monitor a clean page is website cloaking.

Run it: website cloaking checker, free, same engine. Mastercard rule text as of 4 Aug 2026.

What the rules need from the provider’s output

rule (8.9.1, 8.9.2) what that means for a supplier
report each potential violation within 5 business days captures that are ready to use on arrival
monthly report and incident report are unaltered MMSP copies we supply evidence, you write and own the report
incident report: dates, proof of persistent monitoring, why a violation was missed a timestamped log for every check
acquirer sends legal name, DBA, address and all URLs our input is that list

What we deliver

input a list of merchant URLs, with the merchant name and DBA if you have them
output per URL: the page as each visitor type sees it, 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. Country and residential views: deep scan
branding under your name; we do not contact your merchants
format CSV, API or report. You pick
price on request

How a check runs, and what it never does: method. Where we stand: we are not an MMSP, and say so: Mastercard MMSP list.

Try it

Run a URL your crawler fails on through the free website cloaking checker. Same engine.

Sample

[TODO: one real redacted evidence file; none published yet]

Want a pilot on a batch of your hard URLs? Contact us.

Related: merchant monitoring · MMSP · for acquirers and PayFacs

See also: for payment processors · merchant descriptor · MCC mismatch

Questions

Are you a competing MMSP?

No. We are not an approved MMSP and do not sell to acquirers as one. We supply evidence to the provider that is.

Do you replace our crawler?

No. You send only the URLs it cannot read or reads as clean. Everything else stays with your crawler.

Can you cover members-only areas?

Only with test accounts the merchant gives you. We never use credentials we were not given.

What does the 5-business-day rule mean for a crawl supplier?

Mastercard requires the acquirer to have the MMSP report each potential violation within 5 business days (rule 8.9.1). A supplier's captures must arrive early enough for you to write and send that report.

Who owns the monthly report to Mastercard?

The acquirer sends it, or the MMSP on its behalf, as an unaltered MMSP copy (rule 8.9.2). A supplier like us gives you evidence, and you write the report.