Mastercard SPME §11.10 · Sep 2024 → May 2025

MATCH Pro Record Retention

substantive

New requirements added for removing a MATCH Merchant listed under reason code 12, mandating an acquirer's attestation of PCI DSS compliance and a certified forensic examiner's validation letter. Merchants can also request removal if the acquirer does not.

Sources Mastercard SPME · Sep 2024 PDF Mastercard SPME · May 2025 · page 146 PDF ATO Detection current
Also in §11.x this release breaking §11.2.3 "Inquiring about a Merchant" (regarding the use of MATCH Pro) substantive §11 It is the Acquirer's obligation to confirm that the results from MATCH Pro are relevant to the substantive §11.1.1 System Features substantive §11.13 MATCH Merchant Removal from MATCH Pro substantive §11.14 MATCH Pro Reason Codes substantive §11.14.1 Reason Codes for MATCH Merchants Listed by an Authorized User substantive §11.3 MATCH Pro Standards substantive §11.4 Acquirer Requirements substantive §11.5 When to Add a Merchant to MATCH Pro substantive §11.5.1 Acquirer Responsibility: Requests for Removal from MATCH Pro substantive §11.6 Inquiring about a MATCH Merchant substantive §11.6.1 How does MATCH Pro search when conducting an inquiry? substantive §11.6.3 Phonetic Possible Matches
Why these edits? The new requirements in section 11.10 pertain to the removal of a MATCH Merchant listed under reason code 12, which involves an acquirer's attestation of PCI DSS compliance and validation by a Mastercard certified forensic examiner, directly impacting the Account-Takeover (ATO) Detection policy that cites section 6.2 and involves MATCH listings.
Mastercard SPME §11.10
This section was substantively restructured between versions (0% text overlap). Compare the texts directly below.
Before · Sep 2024
After · May 2025 · page 146

Security Rules and Procedures—Merchant Edition • 11 February 2025

  1. PO's Country of Residence Any request relating to a MATCH Merchant listed for reason code 12 must contain:
  • The Acquirer's attestation that the MATCH Merchant is in compliance with the Payment Card Industry Data Security Standard, and
  • A letter or certificate of validation from a Mastercard certified forensic examiner, certifying that the MATCH Merchant has become compliant with the Payment Card Industry Data Security Standard. If an Acquirer is unwilling or unable to submit a request to Mastercard with respect to a MATCH Merchant removal from a MATCH listing as a result of the Merchant obtaining compliance with the Payment Card Industry Data Security Standard, the MATCH Merchant itself may submit a request to Mastercard for this reason. The Merchant must follow the same process as described above for Acquirers to submit the MATCH Pro removal request.
Halyard Pay · 2 files
program: ATO Detection
- authority: Mastercard SPME 10.6.2.1, 10.6.4
+ authority: Mastercard SPME 10.6.2.1, 10.6.4, 11.10
risk_threshold_for_3ds_challenge: 0.5
risk_score_range: [0.0, 1.0]
signals:
- geo_anomaly
- device_fingerprint_change
- velocity_breach
- credential_stuffing
challenge_method: 3ds_v2
persistent_risk_escalation_threshold: 3
persistent_risk_lookback_days: 7
agent_owner: ato_agent
 
# This ATO Detection policy incorporates Mastercard SPME .6.4 updates that affect Account Data Compromise (ADC) event mitigation. It adjusts risk evaluation processes by recognizing that merchants in the U.S. and Canada with high tokenization rates and e-commerce transaction volumes may benefit from reduced or waived reimbursement requirements during such events. This complements detection signal thresholds by informing downstream operational decisions on ADC events, ensuring alignment with Mastercard's revised criteria for operational reimbursement and event assessment.
+ #
+ # Per Mastercard SPME §11.10, any request to remove a MATCH Merchant listed under reason code 12 must now include an acquirer's attestation of PCI DSS compliance and a validation letter from a Mastercard certified forensic examiner certifying such compliance. If the acquirer cannot or will not submit the request, the merchant may submit it directly following the same process. This affects the ATO Detection policy by reinforcing compliance and validation requirements for MATCH listings tied to Account Takeover risk management.

Account-Takeover (ATO) Detection

Account-takeover fraud occurs when a malicious actor gains unauthorized access to a cardholder's account and initiates transactions without the cardholder's consent. Halyard Pay implements real-time risk scoring on authentication events and enforces a mandatory 3DS (3-D Secure) challenge for any session where the computed risk score meets or exceeds the defined threshold.

Detection signals

The risk model incorporates multiple behavioral signals: geographic anomalies inconsistent with a cardholder's established pattern, changes to device fingerprint, transaction velocity breaches, and indicators of credential-stuffing activity.

Required actions

  1. Evaluate each authentication event against the defined signal list in real time.

  2. Compute a normalized risk score between 0.0 and 1.0.

  3. If the risk score is 0.5 or greater, trigger a mandatory 3DS challenge before authorizing the transaction.

  4. Log all ATO signals and outcomes in the case management system.

  5. Escalate persistent high-risk accounts to the ATO response team for manual review.

  6. In the event of an Account Data Compromise (ADC), ensure that any Terminal Servicer (TS) involved promptly initiates a forensic investigation by a PCI Forensic Investigator (PFI) within 72 hours, and completes it as soon as practical.

  7. Confirm that all involved Terminal Servicers revalidate PCI DSS compliance within 90 calendar days after the conclusion of the forensic investigation and demonstrate compliance with the PCI DSS Data Encryption and Software Validation (DESV) appendix within 12 months, per Mastercard SPME §10.6.2.1.

  8. Assure registration of any Terminal Servicer(s) associated with the ADC Event through Mastercard Connect within 10 calendar days of awareness, and confirm full cooperation with Mastercard and law enforcement authorities.

  9. Verify timely receipt by Mastercard of unedited forensic examination findings.

  10. Ensure that all required containment actions identified in forensic reports are completed by the Terminal Servicers involved.

11. For any MATCH Merchant listed under reason code 12, ensure that removal requests include the Acquirer's attestation of the merchant's PCI DSS compliance and a certificate from a Mastercard certified forensic examiner verifying compliance, or allow the Merchant to submit this request directly following the same process, as mandated by Mastercard SPME §11.10.

These enhanced controls reinforce Halyard Pay’s adherence to Mastercard’s strengthened ADC event and MATCH Merchant removal protocols, supporting minimized risk and financial exposure through compliance and timely remediation.

Source authority: Mastercard SPME §6.2, §10.6.2.1.§10.6.2.1, §11.10.

policies/ato_detection/policy.md — after applying change

Account-Takeover (ATO) Detection

Account-takeover fraud occurs when a malicious actor gains unauthorized access to a cardholder's account and initiates transactions without the cardholder's consent. Halyard Pay implements real-time risk scoring on authentication events and enforces a mandatory 3DS (3-D Secure) challenge for any session where the computed risk score meets or exceeds the defined threshold.

Detection signals

The risk model incorporates multiple behavioral signals: geographic anomalies inconsistent with a cardholder's established pattern, changes to device fingerprint, transaction velocity breaches, and indicators of credential-stuffing activity.

Required actions

  1. Evaluate each authentication event against the defined signal list in real time.

  2. Compute a normalized risk score between 0.0 and 1.0.

  3. If the risk score is 0.5 or greater, trigger a mandatory 3DS challenge before authorizing the transaction.

  4. Log all ATO signals and outcomes in the case management system.

  5. Escalate persistent high-risk accounts to the ATO response team for manual review.

  6. In the event of an Account Data Compromise (ADC), ensure that any Terminal Servicer (TS) involved promptly initiates a forensic investigation by a PCI Forensic Investigator (PFI) within 72 hours, and completes it as soon as practical.

  7. Confirm that all involved Terminal Servicers revalidate PCI DSS compliance within 90 calendar days after the conclusion of the forensic investigation and demonstrate compliance with the PCI DSS Data Encryption and Software Validation (DESV) appendix within 12 months, per Mastercard SPME §10.6.2.1.

  8. Assure registration of any Terminal Servicer(s) associated with the ADC Event through Mastercard Connect within 10 calendar days of awareness, and confirm full cooperation with Mastercard and law enforcement authorities.

  9. Verify timely receipt by Mastercard of unedited forensic examination findings.

  10. Ensure that all required containment actions identified in forensic reports are completed by the Terminal Servicers involved.

11. For any MATCH Merchant listed under reason code 12, ensure that removal requests include the Acquirer's attestation of the merchant's PCI DSS compliance and a certificate from a Mastercard certified forensic examiner verifying compliance, or allow the Merchant to submit this request directly following the same process, as mandated by Mastercard SPME §11.10.

These enhanced controls reinforce Halyard Pay’s adherence to Mastercard’s strengthened ADC event and MATCH Merchant removal protocols, supporting minimized risk and financial exposure through compliance and timely remediation.

Source authority: Mastercard SPME §6.2, §10.6.2.1.§10.6.2.1, §11.10.

Source authority: Mastercard SPME §11.10.

--- a/policies/ato_detection/rules.yaml
+++ b/policies/ato_detection/rules.yaml
@@ -1,5 +1,5 @@
 program: ATO Detection
-authority: Mastercard SPME 10.6.2.1, 10.6.4
+authority: Mastercard SPME 10.6.2.1, 10.6.4, 11.10
 risk_threshold_for_3ds_challenge: 0.5
 risk_score_range: [0.0, 1.0]
 signals:
@@ -12,4 +12,6 @@
 persistent_risk_lookback_days: 7
 agent_owner: ato_agent
 
-# This ATO Detection policy incorporates Mastercard SPME .6.4 updates that affect Account Data Compromise (ADC) event mitigation. It adjusts risk evaluation processes by recognizing that merchants in the U.S. and Canada with high tokenization rates and e-commerce transaction volumes may benefit from reduced or waived reimbursement requirements during such events. This complements detection signal thresholds by informing downstream operational decisions on ADC events, ensuring alignment with Mastercard's revised criteria for operational reimbursement and event assessment.+# This ATO Detection policy incorporates Mastercard SPME .6.4 updates that affect Account Data Compromise (ADC) event mitigation. It adjusts risk evaluation processes by recognizing that merchants in the U.S. and Canada with high tokenization rates and e-commerce transaction volumes may benefit from reduced or waived reimbursement requirements during such events. This complements detection signal thresholds by informing downstream operational decisions on ADC events, ensuring alignment with Mastercard's revised criteria for operational reimbursement and event assessment.
+#
+# Per Mastercard SPME §11.10, any request to remove a MATCH Merchant listed under reason code 12 must now include an acquirer's attestation of PCI DSS compliance and a validation letter from a Mastercard certified forensic examiner certifying such compliance. If the acquirer cannot or will not submit the request, the merchant may submit it directly following the same process. This affects the ATO Detection policy by reinforcing compliance and validation requirements for MATCH listings tied to Account Takeover risk management.
--- a/policies/ato_detection/policy.md
+++ b/policies/ato_detection/policy.md
@@ -18,7 +18,8 @@
 8. Assure registration of any Terminal Servicer(s) associated with the ADC Event through Mastercard Connect within 10 calendar days of awareness, and confirm full cooperation with Mastercard and law enforcement authorities.
 9. Verify timely receipt by Mastercard of unedited forensic examination findings.
 10. Ensure that all required containment actions identified in forensic reports are completed by the Terminal Servicers involved.
+11. For any MATCH Merchant listed under reason code 12, ensure that removal requests include the Acquirer's attestation of the merchant's PCI DSS compliance and a certificate from a Mastercard certified forensic examiner verifying compliance, or allow the Merchant to submit this request directly following the same process, as mandated by Mastercard SPME §11.10.
 
-These enhanced controls reinforce Halyard Pay’s adherence to Mastercard’s strengthened ADC event protocols, supporting minimized risk and financial exposure through compliance and timely remediation.
+These enhanced controls reinforce Halyard Pay’s adherence to Mastercard’s strengthened ADC event and MATCH Merchant removal protocols, supporting minimized risk and financial exposure through compliance and timely remediation.
 
-Source authority: Mastercard SPME §6.2, §10.6.2.1.+Source authority: Mastercard SPME §6.2, §10.6.2.1, §11.10.