The Mastercard Alert To Control High-risk Merchants (MATCH) system, previously known in the industry as the Terminated Merchant File, is a risk database that acquiring banks and authorized payment providers check before approving a new merchant account. A listing doesn't automatically prevent you from ever processing cards again, but it does make the road significantly harder.
Many business owners don't understand why they landed on the list or what steps come next. This article breaks down the common triggers, the warning signs that precede termination, and the practical steps that protect your processing relationship before a problem escalates.
Key Takeaways
- MATCH placement follows a qualifying account termination by an acquirer, not a routine application denial.
- Major risk categories include chargebacks, fraud, PCI-DSS violations, and financial or legal misconduct.
- No public self-service lookup tool exists; confirm status with your prior processor or acquiring bank.
- Listings remain on file under Mastercard rules; removal depends on reason code and evidence.
- Chargeback controls, fraud screening, and accurate disclosures are your best long-term protection.
Common Causes of MATCH List Placement
MATCH is Mastercard's shared database of terminated merchants, reported by "Authorized Users", including acquiring banks and Mastercard-approved network partners such as registered payment facilitators. Acquirers are required to check MATCH before onboarding a new merchant.
A MATCH entry is not the same thing as:
- An acquirer's internal risk file, which is that institution's own underwriting notes
- A card-network monitoring program, like Mastercard's Excessive Chargeback Program, which tracks ongoing merchants monthly rather than reporting a termination
- A simple application decline, which reflects one processor's decision and doesn't confirm a MATCH record exists either way
Mastercard actually permits an acquirer to onboard a MATCH-listed merchant if it chooses to take on the risk. Some large payment aggregators note that their own banking-partner restrictions generally prevent them from processing MATCH-listed businesses except in unusual circumstances. That's a company-specific policy, not a universal network rule.
Excessive Chargebacks and Unresolved Disputes
Persistent dispute activity signals financial risk to an acquirer, especially when the disputes stem from unclear billing, slow fulfillment, or weak refund practices.
Mastercard's manual specifically defines a chargeback-related MATCH reason tied to aggregate Mastercard chargebacks over a three-month window exceeding 1.5% of Mastercard sales transactions, combined with a minimum dollar threshold, according to the Mastercard Security Rules and Procedures manual.
That's distinct from Mastercard's separate monthly Excessive Chargeback Program monitoring — don't assume one universal ratio applies everywhere.
Common patterns that push businesses toward this territory:
- Ecommerce and subscription merchants: unclear recurring-billing terms customers don't remember agreeing to
- Event and high-ticket sellers: cancellation or refund confusion after a large deposit
- Card-not-present businesses generally: slow customer support that pushes buyers straight to their bank instead of the merchant
Fraud, Account-Data Compromise, or Identity Theft
Unauthorized transactions, stolen payment credentials, or a compromised point-of-sale system can trigger account review, even when the merchant is also a victim. Mastercard separates these situations by reason code, including categories for account-data compromise, excessive fraud, and identity theft where someone unlawfully used a business identity to open an account.
The distinction matters because the corrective path differs:
- Merchant-controlled weaknesses (poor terminal security, weak checkout fraud rules) point to remediation on your end
- Third-party compromise (a breached vendor, stolen credentials used against you) may require different documentation to dispute the record
PCI-DSS, Network, or Processing-Agreement Violations
Missed PCI validation, insecure card-data handling, or undisclosed business changes all raise termination risk. So does processing transactions outside your approved business model.
Keep your processor informed about:
- Ownership changes
- New products or sales channels
- Shifts in average ticket size or transaction volume
- Expansion into new geographic markets
A compliance gap can often be corrected, but fixing it later doesn't guarantee removal from a listing or reapproval with the same processor.
Financial, Legal, or Operational Problems
Insolvency, bankruptcy, unpaid processing balances, suspected laundering, and material misrepresentation round out the remaining risk categories. In these cases, the specific reason code and supporting evidence matter more than assumptions drawn from a generic closure letter. If the allegation touches fraud, identity theft, illegal activity, or disputed ownership, get qualified legal or compliance advice before responding.
What Happens If a Merchant Account Is Terminated or Listed
Account termination and MATCH placement aren't identical. An account can close for dozens of reasons — only certain qualifying circumstances get reported to MATCH.
If you do land on the list, expect:
- Difficulty opening a conventional merchant account elsewhere
- More intensive underwriting, including requests for financial and compliance records
- Possible reserves or modified settlement terms
- Higher costs in some cases (terms vary by provider and aren't guaranteed)
While investigating a prior termination, some merchants turn to alternative payment methods or specialist processors. Not every provider approves every listed merchant, so this is a case-by-case conversation, not a guaranteed fallback.
Warning Signs You're at Risk of Termination or MATCH Placement
Most merchants get signals before a final closure, though processors don't always disclose a planned report in advance. Watch for:
- Dispute-related red flags — rising chargebacks, fraud alerts, refund complaints, retrieval requests, or customers claiming they don't recognize a transaction
- Funding and underwriting friction — sudden reserve increases, delayed funding, transaction holds, or repeated requests for bank statements and sales records
- Compliance and security flags — PCI-DSS notices, a security incident, requests to re-verify ownership, or warnings about prohibited transaction types
Raise these signals with your processor early, before a final decision is made. An early conversation leaves more room to address the real reason before it becomes a closure.
How to Prevent MATCH Listing
Prevention comes down to five habits:
- Dispute reduction
- Fraud controls
- PCI-DSS compliance
- Transparent operations
- Prompt processor communication
Monitor and Reduce Chargebacks Before They Escalate
Track disputes by reason code, product, channel, and billing descriptor. Use what you find to fix fulfillment delays, rewrite unclear refund policies, and clean up recurring-billing communication.
Practical steps that make a measurable difference:
- Send clear receipts and order confirmations with a recognizable statement descriptor
- Keep shipping or service-completion evidence on file
- Respond to disputes within the applicable deadline every time
Clearwater's guidance on minimizing ecommerce chargebacks notes that almost any business accepting cards will face disputes at some point. The goal is keeping them isolated instead of letting them cluster.
Strengthen Fraud and Transaction Controls
Match your controls to your sales channel. Card-present businesses need solid EMV procedures; card-not-present sellers need AVS, CVV checks, authentication tools, and velocity rules that flag unusual order patterns.
Set escalation triggers for:
- Unusually large orders relative to your typical ticket
- Mismatched billing and shipping details
- Rapid repeat purchases from the same card
- Sudden activity outside your normal footprint
Document your fulfillment and customer-verification process so you can explain an unusual transaction quickly if your processor asks.
Maintain PCI-DSS and Payment-Security Compliance
Map where card data enters, moves through, and gets stored in your systems. Minimize what you store, and use compliant gateways and tokenization wherever possible. PCI DSS applies regardless of merchant size, according to the PCI Security Standards Council — outsourcing your processing doesn't remove your own obligations.
Complete your required validation on schedule, fix findings promptly, and keep your certificates, scan results, and vendor documentation organized.
Clearwater Processing's PCI Compliance Program builds these controls into eligible merchants' payment environments, including $100,000 breach protection insurance. That support helps keep security workflows organized and documented.
Keep the Processor Informed and the Business Accurately Represented
Your application, website, invoices, and marketing claims should match what your business actually does. Contact your processor before:
- Launching a new product line
- Adding recurring billing (Clearwater can automatically update customers' cards that are about to expire, which saves time and retains revenue)
- Changing fulfillment methods
- Experiencing a major shift in volume or average ticket
Keep a written record of every processor communication, approval, and policy update. That paper trail becomes valuable if your account ever comes under review.
Tips for Long-Term Prevention and Control
Beyond the immediate steps above, these ongoing habits help keep merchant accounts stable for years:
- Review trends routinely: Assign someone to check chargeback, refund, fraud, and PCI compliance data monthly, not only when a problem surfaces
- Train your team: Cover terminal security, refund approvals, and escalation procedures, and update training whenever payment channels change
- Keep organized records: Maintain transaction evidence, customer communications, delivery confirmations, and remediation logs
- Check statements and funding reports: Watch for unexpected reserves, fees, or settlement changes. Clearwater Processing's merchant statement analysis catches these surprises and reports average client savings of 10%–30%
- Test your continuity plan: Rehearse a payment hold, gateway outage, or processor termination using compliant backup methods only. Never conceal ownership or activity from a provider
How Clearwater Processing Can Help After an Account Disruption
If your business is facing account disruption, Clearwater Processing can walk you through transparent, tailored processing options, with PCI compliance built into every account in its portfolio. You also get a single point of contact: a representative you can call directly on their personal cell phone, with U.S.-based backend support available every hour of the year. Options are subject to standard underwriting and eligibility review. Call 973-715-5416 to start that conversation.
Conclusion
MATCH placement and merchant-account termination have identifiable causes rooted in risk, compliance, and financial history. The exact reason code and reporting institution ultimately determine what response is available to you.
Act before a closure becomes final:
- Control your disputes
- Secure your payment data
- Keep your processor informed
- Preserve detailed records of everything
Frequently Asked Questions
How long do you stay on the MATCH list?
Under current Mastercard rules, a MATCH record is retained for five years before automatic purge. The clock starts from the qualifying termination or reporting event, so confirm the exact date with the reporting acquirer.
How do I get off the MATCH list?
You generally can't remove a listing yourself. Identify the reporting acquirer, request the reason code and supporting details, then challenge factual errors or submit remediation evidence. Removal is only possible in specific circumstances defined by Mastercard's rules.
How do you know if you're on the MATCH list?
There's no public self-service lookup. Ask your prior processor, acquiring bank, or a new provider reviewing your application for confirmation and the specific reason code, rather than relying on repeated declines as proof.
