The MATCH List Explained: Reason Codes, Removal, and How to Process While You Are On It

The termination itself was survivable. You moved the volume, ate the hold, and got back to shipping. Then the next application comes back declined in under a day, with no explanation and no appeal. So does the one after that, and the one after that. Somewhere in a Mastercard database is a row with your business name, your EIN, and every principal who signed the application. Nobody told you it was created, and no processor will read it aloud to you. Here is what MATCH actually is, why your reason code matters more than the listing itself, who can see it, what genuinely gets a row removed, and how merchants keep processing through the five years.

What MATCH actually is

MATCH stands for Member Alert to Control High-Risk Merchants. It is operated by Mastercard, populated by acquiring banks, and queried by acquiring banks during underwriting. Older documents and many sales reps still call it the TMF, or Terminated Merchant File. Visa has no equivalent public list, so "the blacklist" in payments means MATCH.

When an acquirer terminates a merchant for a reason on Mastercard's list, its rules require it to report that merchant to MATCH. The listing records the business, its principals, and a numeric reason code, and it stays five years from the date it was added before ageing off automatically. There is no annual review, no good-behavior credit, and no fee that shortens it.

Two details surprise people. First, the listing follows the humans, not just the entity. Dissolving the LLC and forming a new one does nothing, because the principals' names, addresses, and tax identifiers are in the record. Second, MATCH is a disclosure database, not a verdict: it tells an underwriter that another bank ended a relationship and why it says it did. Nothing forces an acquirer to decline you for being listed, and specialist high-risk acquirers board listed merchants regularly. That gap between "flagged" and "declined" is the entire space you have to work in.

The reason codes, and why yours matters more than the listing

An underwriter's first question is never whether you are on MATCH. It is which code, and what the story behind it is. The codes span ordinary commercial failure at one end and alleged criminality at the other, and they are not treated alike.

Code	Reason	How underwriters generally read it
04	Excessive chargebacks	The most common listing, and the most survivable if you can show what changed
05	Excessive fraud	Serious, but arguable when it traces to a card-testing incident you fixed
12	PCI DSS non-compliance	Remediable, and mechanical to answer with a current attestation
09	Bankruptcy, liquidation, insolvency	Financial rather than behavioral, judged on your balance sheet
01 / 02	Account data compromise, common point of purchase	A breach narrative, answered with the forensic report
10	Violation of standards	Vague by design; the adding acquirer must tell you what it means
03 / 07 / 11 / 13	Laundering, fraud conviction, merchant collusion, illegal transactions	Close to disqualifying domestically
14	Identity theft	The one code with a rules-backed removal path

Codes shift as Mastercard updates its standards, so treat this as the shape of the list rather than a citation, and get your own code in writing.

If you were listed under 04 for excessive chargebacks, you are in the largest and most workable bucket. A dispute problem is a fixable operational problem, and underwriters have seen hundreds of merchants fix it. If you were listed under 03 or 13, you are looking at offshore acquiring or nothing, and no amount of presentation changes that in the near term.

Who can see it, and who cannot

Only Mastercard acquirers and their agents can query MATCH, and only in connection with underwriting a merchant. It is not a credit bureau and has no effect on your personal credit score.

You cannot query it yourself: there is no merchant-facing portal and no self-check. Ask your terminating acquirer directly, in writing, whether it reported you and under which code, or ask a broker submitting your application what came back on the inquiry. Inquiring acquirers are shown contact details for the adding bank precisely so the story can be checked. A surprising number of merchants spend a year believing they are listed when the termination was never reported.

How merchants get listed without knowing

The reporting happens at the acquirer, on its timeline, and nobody is required to call you about it. For merchants on an aggregator it is quieter still: the sponsoring bank makes the report, and your correspondence is with a support queue that has no visibility into it. The sequence that produces most of these listings is covered in why stores get shut down, and the MATCH entry is its longest-lived consequence.

While you still have a working account, exiting voluntarily before a termination is finalized beats being closed, and a second merchant account is worth far more boarded before a listing than applied for after one.

Getting removed: the narrow paths that work

Removal is possible, and narrower than the services advertising it suggest.

The clean path is error. Only the acquirer that added the listing can remove it, and Mastercard's rules require correction of a listing made in error or under the wrong code. If you were listed under identity theft, that is an explicit removal case. If your chargeback ratio never crossed the threshold the acquirer cited, or the entity listed is not the one that processed, that is an error argument with a real chance.

The error-dispute packet

An error argument succeeds on documents, not on tone, so assemble it before you write to anyone. Pull the processing statements for the entire period the acquirer cited, not only the worst month. Pull the dispute detail next: case numbers, dates, amounts, and outcomes, separating disputes you won from disputes that stood. Then recalculate the ratio the way the network calculates it, by count and against the month the dispute was filed rather than the month the sale closed. That distinction is where most self-diagnosis goes wrong: a blended dashboard figure can show a breach the network's own arithmetic never produced. Add the merchant agreement with the termination clause the acquirer relied on, plus the termination notice. State the request in one paragraph: remove the listing, or recode it to the reason the record supports. Send it to the risk or compliance department in writing, keep it factual, and ask for a written response by a specific date. Support queues cannot remove a listing and will close the ticket.

The negotiated path is settlement. Where the listing followed an unpaid balance, chargebacks the acquirer covered, or a disputed reserve, it sometimes agrees to remove the entry once the debt is settled. Get the removal commitment in the settlement document itself, not in an email promising to look at it later.

No lawyer, broker, or "MATCH removal service" can delete a correctly filed listing, because Mastercard acts on the adding acquirer, not on a merchant's request. A five-figure letter-writing campaign against an accurate 04 listing buys you a letter. Processing under a relative's name, a nominee director, or a shell entity is not a workaround either. It is misrepresentation to a bank, and it converts a five-year commercial problem into a legal one.

How to operate while you are listed

Assume the five years and build for them: merchants who plan around a listing do fine, and merchants who re-apply blindly burn the year.

Lead with the listing rather than letting an underwriter discover it. A one-page cover memo stating the code, the date, what happened, what you changed, and what your numbers look like now converts a hard decline into an underwriting conversation. Concealing it guarantees the decline, since the inquiry runs anyway.

Expect worse terms and price them in. Listed merchants typically see higher rates, a larger rolling reserve, and closer monitoring, and the reserve is the part that hurts cash rather than margin. Model the steady-state balance before you sign, using the arithmetic in the rolling reserves guide, and negotiate a cap and a review date on the way in.

Work with acquirers and ISOs that underwrite your vertical deliberately, not with whoever answers first. The document pack that gets a listed merchant boarded is in the high-risk underwriting checklist, and in a supplement-adjacent catalog the claim cleanup that pack asks for is not optional.

Then build so this cannot happen twice. Run more than one merchant account with real volume on each, per the backup processor strategy guide, and hold your card data somewhere you control so no single processor's decision takes your customers with it.

Practical takeaway

The path that fails is treating MATCH as a rumor: never confirming the code, paying a removal service to fight an accurate listing, hiding it on applications, and collecting declines until the record ages off on its own. The path that lasts is unglamorous. Confirm in writing whether you were listed and under which code, challenge it only where there is a real error or a settlement to trade, disclose it up front to acquirers that board your vertical on purpose, absorb the reserve, and use the five years to build the redundancy that makes the next termination a routing change. A listing narrows your options and prices them higher, but it is not what kills most merchants in this position. Refusing to plan around it is. If you want a straight read on what your code means for your approval odds, apply for an architecture review.