Mastercard SPME §11.4 · Jun 2022 → May 2023

Merchant Removal from MATCH

substantive

The updated section adds specific reasons Mastercard may remove a Merchant listing from MATCH, including when the Acquirer reports an error in adding the Merchant or confirms PCI DSS compliance for a reason code 12 listing, requiring a written removal request on the Acquirer's letterhead.

Sources Mastercard SPME · Jun 2022 · page 136 PDF Mastercard SPME · May 2023 · page 146 PDF ECP Thresholds current

Also in §11.x this release substantive §11.1.1 System Features substantive §11.2 MATCH Standards substantive §11.2.1 Certification substantive §11.2.6 MATCH Record Retention substantive §11.5 MATCH Reason Codes

Why these edits? The update clarifies conditions under which a Merchant may be removed from MATCH, specifically adding requirements for written removal requests by the Acquirer when confirming PCI DSS compliance or correcting errors in listing, affecting the obligations around merchant removal under the Excessive Chargeback Program.

Mastercard SPME §11.4

This section was substantively restructured between versions (27% text overlap). Compare the texts directly below.

Before · Jun 2022 · page 136

Mastercard may remove a Merchant listing from MATCH for the following reasons: MATCH System

After · May 2023 · page 146

Mastercard may remove a Merchant listing from MATCH for the following reasons:

The Acquirer reports to Mastercard that the Acquirer added the Merchant to MATCH in error.
The Merchant listing is for reason code 12 (Payment Card Industry Data Security Standard Noncompliance) and the Acquirer has confirmed that the Merchant has become compliant with the Payment Card Industry Data Security Standard. The Acquirer must submit the request to remove a MATCH reason code 12 Merchant listing from MATCH in writing on the Acquirer’s letterhead to MATCH System

Halyard Pay · 2 files

ECP Thresholds · rules.yaml

program: ECP
- authority: Mastercard SPME §11.4
+ authority: Mastercard SPME  MasterCard SPME section 11.4, updated to clarify conditions for Merchant removal from MATCH, specifically requiring Acquirer's written request for removal of reason code 12 listings upon PCI DSS compliance confirmation or error correction.
chargeback_to_transaction_ratio_threshold: 0.015
min_chargeback_count: 100
program_tiers:
  - standard
  - excessive
tier_thresholds:
  standard: 0.015
  excessive: 0.030
merchant_notification_business_days: 5
monitoring_cadence: monthly
agent_owner: ecp_ops_agent

ECP Thresholds · policy.md

Excessive Chargeback Program (ECP) Thresholds

Mastercard's Excessive Chargeback Program (ECP) identifies merchants whose chargeback

activity exceeds defined monthly ratios relative to their transaction volume. Halyard Pay

monitors merchant chargeback-to-transaction ratios on a monthly basis and escalates

merchants that breach program tiers to the appropriate remediation track.

Program tiers

Two tiers define the escalation ladder:

Standard: chargeback-to-transaction ratio of 1.5% (0.015) or greater and at

least 100 chargebacks in the month.

Excessive: ratio of 3.0% (0.03) or greater in the same measurement period.

Required actions

Calculate each merchant's chargeback-to-transaction ratio at month close.
Assign the merchant to the applicable tier if thresholds are met.
Open an ECP case and notify the merchant within five business days.
Track the merchant's progress on a monthly basis until they exit the program.
Escalate to chargeback agent for automated case management.

6. When removing a Merchant listing from MATCH for ECP reasons, ensure that requests,

especially for listings related to PCI DSS compliance (reason code 12), are submitted

in writing on the Acquirer's letterhead as required by Mastercard.

Source authority: Mastercard SPME ~~§11.4.~~11.4.

policies/ecp_thresholds/policy.md — after applying change

Excessive Chargeback Program (ECP) Thresholds

Mastercard's Excessive Chargeback Program (ECP) identifies merchants whose chargeback

activity exceeds defined monthly ratios relative to their transaction volume. Halyard Pay

monitors merchant chargeback-to-transaction ratios on a monthly basis and escalates

merchants that breach program tiers to the appropriate remediation track.

Program tiers

Two tiers define the escalation ladder:

Standard: chargeback-to-transaction ratio of 1.5% (0.015) or greater and at

least 100 chargebacks in the month.

Excessive: ratio of 3.0% (0.03) or greater in the same measurement period.

Required actions

Calculate each merchant's chargeback-to-transaction ratio at month close.
Assign the merchant to the applicable tier if thresholds are met.
Open an ECP case and notify the merchant within five business days.
Track the merchant's progress on a monthly basis until they exit the program.
Escalate to chargeback agent for automated case management.

6. When removing a Merchant listing from MATCH for ECP reasons, ensure that requests,

especially for listings related to PCI DSS compliance (reason code 12), are submitted

in writing on the Acquirer's letterhead as required by Mastercard.

Source authority: Mastercard SPME ~~§11.4.~~11.4.

Source authority: Mastercard SPME §11.4.

--- a/policies/ecp_thresholds/rules.yaml
+++ b/policies/ecp_thresholds/rules.yaml
@@ -1,5 +1,5 @@
 program: ECP
-authority: Mastercard SPME §11.4
+authority: Mastercard SPME  MasterCard SPME section 11.4, updated to clarify conditions for Merchant removal from MATCH, specifically requiring Acquirer's written request for removal of reason code 12 listings upon PCI DSS compliance confirmation or error correction.
 chargeback_to_transaction_ratio_threshold: 0.015
 min_chargeback_count: 100
 program_tiers:

--- a/policies/ecp_thresholds/policy.md
+++ b/policies/ecp_thresholds/policy.md
@@ -19,5 +19,8 @@
 3. Open an ECP case and notify the merchant within five business days.
 4. Track the merchant's progress on a monthly basis until they exit the program.
 5. Escalate to chargeback agent for automated case management.
+6. When removing a Merchant listing from MATCH for ECP reasons, ensure that requests,
+   especially for listings related to PCI DSS compliance (reason code 12), are submitted
+   in writing on the Acquirer's letterhead as required by Mastercard.
 
-Source authority: Mastercard SPME §11.4.
+Source authority: Mastercard SPME 11.4.