What Is MATCH List?

How MATCH List Works

The MATCH List operates as a shared intelligence layer between acquiring banks. When an acquirer terminates a merchant relationship for one of Mastercard's 14 defined reasons, they are obligated to submit a record to the database within three business days. That record then becomes visible to every other Mastercard-member acquirer during underwriting. Understanding the mechanics of each step helps merchants know where they stand — and where the leverage points are.

Why MATCH List Matters

For any e-commerce merchant, the MATCH List represents one of the most severe operational risks in payment processing. Being listed can effectively cut off access to mainstream payment infrastructure overnight, forcing costly workarounds that erode margins and damage customer trust.

Mastercard's own data indicates that merchants listed under Reason Code 4 (excessive chargebacks) had an average chargeback rate of 2.4% in the months preceding termination — more than double the 1% threshold that most acquirers treat as a hard ceiling. Industry research from the Merchant Risk Council estimates that recovering from a MATCH listing costs the average SMB between $15,000 and $50,000 in lost revenue, compliance remediation, and higher processing fees during the first year after finding an alternative processor. A 2023 survey by the Electronic Transactions Association found that 68% of acquirers cited MATCH hits as an automatic disqualifier in their underwriting workflows, underscoring how little discretion most traditional banks apply once a listing is found.

MATCH List vs. Chargeback Monitoring Programs

Both MATCH and chargeback-monitoring-programs respond to high chargeback volumes, but they operate at very different stages of the risk lifecycle and carry distinct consequences.

The critical difference is timing. Chargeback monitoring programs are a warning system with structured remediation; the MATCH List is a consequence applied after remediation has failed or the relationship has irreparably broken down.

Types of MATCH List Reason Codes

The MATCH List is not a single undifferentiated blacklist — each record carries one of 14 reason codes that signal the severity and nature of the termination. Acquirers and processors weigh these codes differently during risk assessments.

High-severity codes (virtually no path to mainstream acquiring):

• Reason Code 7 – Fraud Conviction: Merchant or principal convicted of fraud-related criminal activity.
• Reason Code 8 – Mastercard Fraud: Merchant identified in a Mastercard fraud investigation.
• Reason Code 9 – Bankruptcy / Insolvency: Significant unpaid chargeback liability at time of insolvency.
• Reason Code 12 – PCI Non-Compliance: Merchant failed to maintain PCI DSS standards, especially following a data breach.

Moderate-severity codes (some high-risk processors may still onboard):

• Reason Code 4 – Excessive Chargebacks: Chargeback rate exceeded network thresholds for two or more consecutive months. Most common code for e-commerce.
• Reason Code 5 – Excessive Fraud: Fraud-to-sales ratio exceeded acceptable thresholds.
• Reason Code 6 – Fraud Conviction (Third Party): A third-party agent or ISO connected to the merchant was convicted.

Lower-severity codes (more recoverable with documentation):

• Reason Code 1 – Account Data Compromise: Data breach exposing cardholder data, without evidence of ongoing fraud.
• Reason Code 2 – Common Point of Purchase: Card data stolen through merchant's environment.
• Reason Code 3 – Laundering: Processing transactions for an undisclosed merchant.

Understanding which reason code applies is the first step in any remediation strategy, as it directly determines which acquirers — if any — will consider an application.

Best Practices

For Merchants

Preventing MATCH listing is categorically easier than recovering from one. The most effective controls target the leading causes — chargebacks and fraud — before they escalate to termination thresholds.

• Monitor chargeback ratios weekly, not monthly. By the time a monthly statement flags a problem, you may already be in a monitoring program. Use your acquirer's reporting portal or a third-party chargeback analytics tool to track ratios in near real-time.
• Respond to every chargeback dispute, even small ones. Many merchants ignore low-value disputes; acquirers and networks track dispute volume, not just lost amounts.
• Know your current status before applying for a new account. Authorized representatives can sometimes request an informal MATCH check through their current acquirer. Third-party compliance firms also offer MATCH screening services.
• Structure contracts carefully. If you are adding a business partner or acquiring a company, check all principals against MATCH before signing. A listed individual becoming a principal at your entity can contaminate your application.
• If listed, document the root cause resolution. Any high-risk processor willing to onboard a listed merchant will require evidence that the underlying problem has been addressed — chargeback rate data, fraud tool implementations, or legal clearance as applicable.

For Developers and Payment Engineers

Developers building payment integrations or managing merchant onboarding workflows carry responsibility for controls that can directly prevent MATCH-triggering events.

• Implement fraud scoring at checkout, not just at authorization. Pre-authorization signals (velocity checks, device fingerprinting, proxy detection) reduce fraud-driven chargebacks more effectively than post-authorization tools alone.
• Build refund-first logic for dispute prevention. Many chargebacks are filed because customers cannot easily reach customer service. An automated refund trigger for high-risk transaction patterns (unusual shipping address, first-time high-value order) can lower chargeback rates before they become a problem.
• Log and expose chargeback reason codes from your payment-processor to internal dashboards. Grouping codes by root cause (friendly fraud vs. service not received vs. unauthorized) enables targeted remediation rather than blanket policy changes.
• Test PCI compliance continuously, not just at annual assessment cycles. Automated scanners integrated into CI/CD pipelines catch configuration drift that can lead to data compromises.
• Use 3D Secure 2.x for liability shift. Properly authenticated transactions shift chargeback liability back to the card issuer for fraud disputes, directly reducing your chargeback rate exposure.

Common Mistakes

Even experienced merchants and payment operations teams make avoidable errors around MATCH exposure.

1. Assuming a new legal entity resets the clock. Incorporating a new company does not protect listed principals. MATCH records include individual owner details, and acquirers query both entity and principal data. If a listed individual owns more than 25% of the new entity, the record will surface during underwriting.

2. Ignoring low chargeback volumes because rates look fine. A merchant processing $50,000/month with 10 chargebacks has a 0.02% rate — apparently healthy. But if processing volume drops to $20,000/month while disputes stay flat, that rate jumps to 0.05%. Rate calculations are volatile for lower-volume merchants; absolute dispute counts also matter to acquirers.

3. Applying to multiple acquirers simultaneously after a denial. Each MATCH query is logged. A burst of inquiries from multiple acquirers in a short window flags the merchant as a risk, making each subsequent acquirer more cautious even before reviewing the application.

4. Conflating the MATCH List with the Terminated Merchant File. These are two separate databases maintained by two separate card networks. Clearing a Visa TMF record does not clear a Mastercard MATCH record and vice versa. Both must be addressed independently.

5. Delaying contact with the adding acquirer. The only path to early removal runs through the acquirer who submitted the record. Many merchants wait months — or years — before making contact. Early, documented outreach to resolve the underlying cause (repaying chargeback losses, for example) is the single most important step toward potential early removal.

MATCH List and Tagada

Tagada's payment orchestration layer helps high-risk and scaling merchants manage the operational risks that can lead to MATCH listing in the first place. Because Tagada routes transactions across multiple acquiring relationships simultaneously, a merchant experiencing chargeback pressure with one acquirer does not have all their volume — and all their risk — concentrated in a single account that could be terminated for cause.

For merchants already navigating a MATCH listing and working with a high-risk acquirer, Tagada's orchestration layer provides the redundancy and reporting infrastructure needed to demonstrate improved risk controls — a key requirement for any future mainstream acquiring relationship.