Mastercard BRAM program (Business Risk Assessment and Mitigation) investigates merchants referred to Mastercard as potentially engaging in illegal or brand-damaging transactions. Mastercard then works with the acquirer to make the merchant stop (Security Rules and Procedures, Merchant Edition, 4 Aug 2026, section 8.8).
Run it: website cloaking checker captures what a merchant URL shows a reviewer and a customer, dated. Figures as of 20 Nov 2026.
Rules it enforces
- 3.7 Integrity of Brand and Network
- 5.12.7 Illegal or Brand-damaging Transactions
Other rules that BRAM cases most often turn up: the Merchant Agreement Rule (5.1, transactions must be submitted under a merchant agreement with the seller), disclosure of merchant name and location (5.5.1, 5.6.1), MCC information (5.8.1), unregistered service providers (7.10), MATCH Pro use (11.5, 11.6). See transaction laundering, merchant descriptor, MATCH list.
Mastercard publishes the categories of concern to customers in the Technical Resource Center of Mastercard Connect.
How a case runs
| step | what happens |
|---|---|
| referral | from law enforcement, IP holders and anti-piracy referrals, industry groups, complaints, or Mastercard’s own identifications |
| notice | Mastercard confirms the entity accepts Mastercard, opens a BRAM case, notifies the acquirer’s security contact |
| response | 5 business days (2 for law enforcement or government cases, or at Mastercard’s discretion): remediation plan, merchant application and agreement, business overview with website URLs, proof of how the violating URL relates to the approved merchant |
| decision | Mastercard rules whether a Standard was violated and sets the assessments |
The fine
For each merchant, entity, affiliate, agent or person on whose behalf the acquirer submits illegal or brand-damaging transactions: USD 200,000, or USD 2,500 per day, retroactive to the first day of the practice if the acquirer shows clear and convincing evidence it began less than 80 days before notice (8.8.3). The acquirer must keep every approved merchant URL in the merchant record.
Mitigation (8.8.4) can count: stopping within 2 business days of notice, the merchant’s Mastercard volume in the last 12 months, and the volume of the violating activity. Under the Merchant Monitoring Program a registered MMSP changes the share: Mastercard MMSP list.
Documents a response must hold (rule 8.8.2)
Twelve items, among them: a remediation plan; the merchant application and signed agreement with legal name, DBA, address and owners; the business overview with URLs; proof linking the violating URL to the approved merchant; first-transaction date per URL; monthly count and USD volume per URL (up to 12 months); the MATCH Pro inquiry and listing; MMSP screen prints. An incomplete answer is itself a violation of rule 3.9 and draws escalating Category C assessments until it is complete.
How to spot a BRAM risk
The acquirer’s answer to Mastercard must show how the violating URL relates to the approved merchant and its approved URL (8.8.2). So the work is mapping every URL a merchant sells from, and seeing what each one shows to a stranger. Load the merchant URL as different visitors and compare: website cloaking checker. Hub: merchant monitoring.
Related
Excessive chargeback program · MMSP · GRIP letter · MATCH list · Mastercard SMMP explained
See also: prohibited merchants list · for acquirers and PayFacs