Merchant monitoring is an acquirer or payment facilitator checking its merchants after they are approved. It looks at two things: the payments, and the website.
Run it: SMMP trigger checker for the payment side, website cloaking checker for the website side. Rules and figures below are as of 20 Nov 2026.
Clocks and numbers
| what | number | source |
|---|---|---|
| start an investigation after a scam-merchant trigger | 72 hours | Mastercard 7.2.1 |
| MMSP reports a potential violation to the acquirer | 5 business days | Mastercard 8.9.1 |
| acquirer investigates an MMSP alert | 15 calendar days | Mastercard 8.9.1 |
| answer a BRAM notice | 5 business days, 2 for police or government cases | Mastercard 8.8.2 |
| BRAM assessment | USD 200,000, or USD 2,500 per day | Mastercard 8.8.3 |
| add a terminated merchant to MATCH Pro | 5 calendar days | Mastercard ch. 11 |
| keep onboarding records | 2 years after the agreement ends | Mastercard 7.1.2 |
| Visa VAMP, Excessive merchant (US, EU, Canada, Asia Pacific) | 150 basis points and 1,500 fraud plus dispute cases a month, from 1 Apr 2026 | Visa VAMP fact sheet |
What the rules say
| source | rule | read it |
|---|---|---|
| Mastercard 6.2.2.8 | Acquirers run periodic reviews of each merchant’s activity: monthly volume, refunds, fraud, average ticket, chargebacks, activity that does not fit the business, transaction laundering, illegal or brand-damaging activity | Mastercard rules |
| Mastercard 7.2.1 | 72 hours to start an investigation after a trigger: Mastercard SMMP explained | same manual |
| Mastercard 8.9 | Merchant Monitoring Program: optional. Join it and you must use an approved MMSP: Mastercard MMSP list | same manual |
| Visa VARS | Acquirers use web crawling tools and regularly verify merchant websites | Visa Acceptance Risk Standards |
| Visa VIRP | Controls against illegal activity: Visa Integrity Risk Program | same guide |
| FTC v. Humboldt, 2026 | Review client sites from an IP not tied to the processor, and keep copies. A processor paid $12 million in a settlement over shell merchants: shell merchant | for payment processors |
What gets checked on the website
Mastercard recommends, for e-commerce merchants in its Europe region, checking at onboarding and at regular rescreening for:
- unrealistic promotions, including countdown timers
- products unrelated to the merchant’s business or MCC
- customer service contacts that are unreachable, unanswered or do not carry the merchant name
Visa’s list: the site sells only what was declared, it has a checkout, merchant names and MCCs match, no suspicious links to other URLs. Sources: the two documents above.
A change in ownership, country or activities makes Mastercard require the onboarding screening to be done again (rule 7.2).
Where it breaks
A monitor sees what the merchant’s site shows the monitor. Two ways that fails:
- The site shows a different page to crawlers and reviewers: website cloaking.
- The site blocks the crawler. G2 Risk Solutions writes that many high-risk industries block crawlers, with DDoS protections or member-only areas (G2 Risk Solutions, 2025).
Mastercard’s program text says monitoring must include restricted members-only areas, unless the law prohibits it (rule 8.9.1).
Who does it
| who | when |
|---|---|
| your own risk team | the periodic reviews in rule 6.2.2.8 |
| an approved MMSP | required to join Mastercard’s Merchant Monitoring Program: Mastercard MMSP list |
| a first look at one site | policy pages, contact details, domain age, cloaking in one run: merchant onboarding website check |
| extra evidence from a third party | when you want the site checked as a stranger sees it: website cloaking checker |
The cluster
- Hidden sellers: transaction laundering, shell merchant
- Mastercard: BRAM, excessive chargeback program, GRIP letter, MATCH list, SMMP
- Red flags: transaction laundering red flags, MCC mismatch
- Who is who: PayFac, merchant descriptor
- Monitoring in practice: BRAM monitoring, KYB website verification, Visa merchant monitoring, prohibited merchants list
- Buyers: for acquirers and PayFacs, for merchant monitoring providers
Need a batch of merchant sites checked? Contact us.
See also: card testing attack