BRAM monitoring is the work that happens before the BRAM notice. A case starts from a referral: police, rights holders, anti-piracy groups, industry groups, complaints, or Mastercard’s own finds. You want to be the first to see the URL.
Run it: website cloaking checker shows what one merchant URL serves to a reviewer and to a customer. Rules and fines as of 20 Nov 2026.
The numbers
| answer a BRAM notice | 5 business days; 2 for law enforcement or government cases, or at Mastercard’s discretion (8.8.2) |
| assessment per merchant | USD 200,000, or USD 2,500 per day, retroactive if the practice began under 80 days before notice (8.8.3) |
| stop the activity | generally within 2 business days of notice, to count for mitigation (8.8.4) |
| found and stopped before Mastercard identified it | 100% mitigation (8.9.3) |
| MMSP found it, Mastercard identified it, stopped within 2 business days | 75% with MMSP, 25% without |
| incomplete answer | rule 3.9 violation, escalating Category C assessments |
What to watch
| watch | why |
|---|---|
| every URL tied to a merchant: approved, linked, redirected to | the BRAM answer must show how the violating URL relates to the approved one |
| what each URL sells, against the declared business and MCC | illegal or brand-damaging sales hide behind a harmless MCC |
| what the site shows to different visitors | a clean page for reviewers, another for customers: website cloaking |
| new URLs and domains the merchant starts using | a second storefront is how transaction laundering starts |
| the name of the seller on each checkout | the descriptor and the site name should agree: merchant descriptor |
What a BRAM case asks you to produce
From rule 8.8.2 of Mastercard’s Security Rules and Procedures, Merchant Edition, 4 Aug 2026, within five business days:
- a remediation plan
- the merchant application and signed agreement
- the business overview approved at onboarding, with the website URLs
- documents showing how the violating URL relates to the approved merchant and its URL
- the date of the first transaction from the merchant, per approved URL and the violating URL
- monthly volume per URL for up to the last 12 months
- the MATCH Pro inquiry, and the listing if you terminated
- MMSP reports showing the monitoring of all URLs, if you have one
Records you made on your own before the notice make this list faster to fill.
What it saves
Rule 8.9.3 lists 100% mitigation, whether or not you have an MMSP, where you or your MMSP found the activity first and it stopped before Mastercard identified it. Without monitoring you rely on luck. The program and fine: Mastercard BRAM program.
Who does it
| route | note |
|---|---|
| your own risk team | rule 6.2.2.8 asks for periodic reviews of merchant activity, including illegal and brand-damaging activity |
| an approved MMSP | needed to join the Merchant Monitoring Program: Mastercard MMSP list |
| extra evidence | what the site shows to different visitors, dated: website cloaking checker |
What we 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. We are not a Mastercard MMSP: for acquirers and PayFacs.
Related
Merchant monitoring · Excessive chargeback program · KYB website verification · Visa merchant monitoring
Want your merchant URLs checked on a schedule? Contact us.
See also: for merchant monitoring providers · prohibited merchants list