MMSP is short for Merchant Monitoring Service Provider: a vendor Mastercard has approved to do BRAM monitoring, transaction laundering detection, or both, for an acquirer (Security Rules and Procedures, Merchant Edition, 4 Aug 2026, section 8.9).
What the rules say
- The Merchant Monitoring Program (MMP) is optional. An acquirer that joins “must engage one or more” MMSPs.
- Mastercard keeps the approved list. Email MMP@mastercard.com for it.
- The acquirer confirms the approval, registers the MMSP as its service provider, and gives it each merchant’s legal name, DBA, address and all URLs.
- Every participating merchant is scanned. The MMSP then monitors persistently, including the payment page and members-only areas.
- Monthly reports to Mastercard go in as unaltered MMSP copies.
Run it: SMMP trigger checker shows which of the four scam-merchant triggers a merchant hits, MMSP alert included. Rules as of 20 Nov 2026.
Who does what
| step | who | deadline | rule |
|---|---|---|---|
| approve the vendor | Mastercard | n/a | 8.9.1 |
| register it as service provider, send legal name, DBA, address and all URLs | acquirer | before the scan | 8.9.1, 7.10 |
| scan every participating merchant | MMSP | first report must be in hand before mitigation applies | 8.9.1 |
| report each potential violation to the acquirer | MMSP | 5 business days | 8.9.1 |
| investigate, stop the activity, report the resolution to the MMSP | acquirer | 15 calendar days | 8.9.1 |
| send the monthly report to Mastercard | acquirer or MMSP | unaltered MMSP copy | 8.9.2 |
| write the incident report after a BRAM notice | MMSP | with the BRAM answer | 8.9.1 |
An alert from an MMSP is also trigger 4 of the 72-hour scam-merchant rule: Mastercard SMMP explained.
Who is one
Mastercard’s list is not public. Providers that say they are one: Mastercard MMSP list. OCODATA is not an MMSP.
Related
BRAM · Transaction laundering · Merchant monitoring · For merchant monitoring providers
See also: KYB website verification