Mastercard SMMP 2026: What the Strategic Merchant Monitoring Programme Means for Your Account

Mastercard operates two merchant monitoring programmes that most merchants confuse: the Mastercard Chargeback Monitoring Programme (MCMP), which is triggered by chargeback ratio, and the Mastercard Strategic Merchant Monitoring Programme (SMMP), which is triggered by fraud volume. They have different thresholds, different fine structures, and different remediation approaches. Understanding the distinction is essential because the operational response to each is different.

If your chargeback ratio is high, you need MCMP remediation. If your TC40 fraud reports are high relative to transaction volume, SMMP is the relevant exposure.

What SMMP Actually Monitors

SMMP monitors fraud rates at the merchant level, using TC40 fraud report data. TC40 reports are filed by issuers when a cardholder reports a transaction as fraudulent — these are the fraud notification records that flow through the Mastercard network. TC40 reports precede formal chargebacks; they represent issuers flagging transactions as fraud regardless of whether a dispute has been filed.

SMMP thresholds are applied to the fraud rate — TC40 reports as a percentage of settled transaction volume. Merchants above the threshold receive a formal notification through their acquirer, and Mastercard begins monitoring the account quarterly.

Unlike MCMP, SMMP does not have a public fine schedule that escalates monthly in a defined table. SMMP remediation pressure is applied through the acquirer relationship: acquirers receiving SMMP notifications for merchants on their portfolio face their own Mastercard compliance requirements, which they pass through to merchants as reserve increases, account restrictions, or processing termination.

How SMMP Differs From MCMP

The distinction matters operationally because the fraud rate (SMMP) and the chargeback ratio (MCMP) are related but different numbers.

Chargeback ratio counts formal disputes filed — transactions where a cardholder went through their bank to initiate a dispute and the bank filed a chargeback. This is the MCMP numerator.

Fraud rate (TC40) counts issuer fraud reports — transactions flagged by issuers as fraudulent, which may or may not have resulted in a formal chargeback yet. TC40 reports often arrive before chargebacks, and some TC40-flagged transactions are resolved without a formal chargeback being filed.

A merchant can have a high TC40 fraud rate (high SMMP risk) while having a low chargeback ratio (no MCMP risk) if issuers are absorbing fraud losses without filing formal chargebacks, or if a high proportion of fraud is being refunded pre-dispute. Conversely, a merchant with a high chargeback ratio driven primarily by consumer disputes (not fraud) may have low TC40 volume and no SMMP exposure.

Tracking only your chargeback ratio tells you your MCMP status but not your SMMP status. You need TC40 report data, available from your acquirer, to know your fraud rate independently.

TC40 Data and How to Access It

TC40 reports are not directly visible in standard payment processor dashboards. Stripe, for example, shows disputes in the dashboard but shows TC40 reports separately under Radar activity — as "early fraud warnings" rather than as TC40 records explicitly.

To get accurate TC40 data for SMMP monitoring purposes:

• Request TC40 reporting from your acquirer directly; most acquirers will provide this on request for merchants with elevated fraud concern
• Review Stripe's early fraud warning data in the Radar section of the dashboard
• Use a third-party dispute and fraud analytics platform that aggregates TC40 data

The gap between what you see in your dashboard and your actual Mastercard SMMP status is a common source of merchant surprises. A merchant whose dashboard shows manageable chargeback volume may have significantly higher TC40 exposure that isn't visible in standard reporting.

SMMP Remediation: What Actually Works

SMMP remediation is fraud prevention, not chargeback representment. The interventions that reduce your chargeback ratio (faster representment, better evidence) do not reduce your TC40 fraud rate. TC40 rates decrease only through prevention — stopping fraudulent transactions before they complete.

3DS2 authentication is the most structurally effective SMMP remedy. Authenticated transactions shift fraud liability to the issuer, meaning TC40 reports on 3DS-authenticated transactions are generally not assessed against the merchant's fraud rate. For merchants with high CNP fraud rates, 3DS2 deployment has an immediate and significant effect on TC40 volume.

Velocity rules and device fingerprinting catch repeat fraud patterns before they generate TC40 reports. A compromised card used for five transactions at the same merchant generates five TC40 reports. Velocity rules that block the third transaction prevent TC40 reports 4 and 5.

High-risk order review — manual or automated review of transactions above a threshold value, orders with shipping/billing mismatch, new devices, or high-risk IP geolocation — reduces fraud rates on the specific transaction segments that generate disproportionate TC40 volume.

The MCMP calculator at chargemate.tech covers the MCMP fine schedule specifically — SMMP fines aren't published on the same schedule, but the SMMP/MCMP distinction is explained in the context of Mastercard's overall fraud monitoring approach.

Acquirer Behaviour Under SMMP

The mechanism of SMMP pressure is different from MCMP. Mastercard does not directly fine merchants under SMMP in the same escalating-table structure as MCMP. Instead, Mastercard fines acquirers for fraud activity on their portfolio, and acquirers respond by managing merchant risk.

An acquirer receiving an SMMP notification for a merchant will typically:

1. Notify the merchant formally (similar to MCMP)
2. Request a fraud remediation plan with specific interventions and timelines
3. Increase reserve requirements on the merchant account
4. Set a timeline for fraud rate improvement with account review at the end

If the fraud rate does not improve within the review period, the next step for most acquirers is processing restrictions or termination. SMMP does not result in merchant placement on MATCH automatically, but processor termination can — and MATCH placement significantly limits future processing options.

The remediation timeline pressure under SMMP is real, but the path is clear: 3DS2 deployment and fraud controls improvement. Merchants with high TC40 rates who have not deployed 3DS2 typically see rapid fraud rate improvement following authentication deployment, because a significant portion of CNP fraud is prevented by authentication-required flows that fraudsters cannot complete.