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.