Mastercard SMMP Example: The 72-Hour Triggers, Worked

Mastercard SMMP example (a model, not a real merchant): a 2-month-old store with 54 of 600 purchases refunded (9%) fires trigger 3. The same store at exactly 5% does not. Ten worked cases below.

Ran
Sample
10
Tools
SMMP Trigger Checker
Method
MODEL run, not a real merchant. Our checker's own logic on 10 labelled scenarios with numbers we chose, against the rule text of 4 Aug 2026.

What we ran

This is a model, not a real merchant. We built 10 scenarios that sit on each side of each threshold and ran them through the logic of the SMMP trigger checker, which implements section 7.2.1 of Mastercard’s Security Rules and Procedures, Merchant Edition, 4 Aug 2026. The shape is the one Mastercard describes (May 2026): a storefront that looks real, takes payments, ships little or nothing, and is gone. Numbers are ours.

What we found

# scenario result
A storefront 2 months old, 600 purchases in 30 days, 54 refunded or charged back (9.0%) trigger 3 fires
B same, 30 of 600 (exactly 5.0%) clear: the rule says more than 5%
C same, 31 of 600 (5.17%) trigger 3 fires
D 499 purchases, 200 refunded (40%) clear: needs 500 purchases
E same 9.0%, merchant 8 months old clear: trigger 3 is for 6 months or less
F 4 months old, two issuers report a scam, refunds 1% trigger 3 fires
G approval rate 95% to 45% over 72 h, 30 purchases trigger 1 fires
H 95% to 46% (49 points), 30 purchases clear
I 95% to 20%, 24 purchases clear: needs 25 purchases
J 95% to 20%, 40 purchases, BIN attack at the acquirer clear: excluded by the rule

Four of ten fire. The cliffs are sharp: one purchase or one point moves a case across the line. When a trigger fires, the acquirer or payment facilitator has 72 hours to start an investigation. Triggers 2 (a GRIP letter) and 4 (an MMSP alert) are yes or no, not numbers.

How you’d use it

  • Acquirer or PayFac: put your own portfolio numbers through the same table each day. The cases that sit near a line are the ones to watch. See for acquirers and PayFacs.
  • Merchant monitoring provider: the website review is what fills the investigation file. Merchant monitoring feeds trigger 4.
  • Risk team: keep this table as the unit test of your alert logic. The checker is not an official Mastercard tool.
Run this on your own list

Send us the sites, domains or ads. We run it, and send back the table.

Get this run

Questions

Is this a real merchant?

No. The scenarios are ours, built to sit on each side of each threshold. We did not take a real merchant's numbers. The pattern follows what Mastercard describes: new storefronts that take payments, ship little or nothing, then disappear.

What counts as the 5% refund trigger?

More than 5% of purchases refunded or charged back in a rolling 30 days, with at least 500 purchases, for an entity with 6 months of history or less. Exactly 5% does not fire. 499 purchases does not fire.

How big must an approval-rate drop be?

At least 50 percentage points against the previous 7 or more days, over 72 hours with at least 25 purchases, or an approval rate under 30%. A 49-point drop does not fire. BIN attacks and acquirer system issues are excluded.