Get MATCHed, Go Broke

Five years. That is how long one terminated processing account can shadow your business through a registry you were never shown and cannot search yourself. An acquiring bank can close your account and add you to it the same afternoon.

It is hard to know whether you are on MATCH, and no one is required to tell you. You usually find out only when it surfaces in an acquirer's check, either as a rejected application or as a disruption to an account you already run.

It's called MATCH: Mastercard Alert to Control High-risk Merchants. Older operators still call it the TMF, the Terminated Merchant File. Either way, it is the single most consequential list in payments that merchants almost never see coming.

The list acquirers see and you can't

MATCH is a shared registry of merchants who have had a payment processing account terminated. When an acquiring bank shuts a merchant down for cause, it reports that business to MATCH. When any other acquirer runs underwriting on a new application, they check MATCH first.

Mastercard operates it as the MATCH Pro system, governed by its own Security Rules and Procedures manual, where an entire chapter defines who gets listed, under which codes, and for how long. Acquirers screen prospective merchants against it during underwriting to gauge the risk of boarding a business another bank has already terminated.

A hit doesn't legally ban an acquirer from boarding you. In practice, it functions as one. An underwriter who sees a MATCH listing will usually decline rather than take on a merchant another bank already cut loose.

A listing attaches to the identifiers behind the business:

• Legal entity name and DBA
• The principal owner's name
• Tax ID or Social Security number
• Business and home address
• Website URL

Spinning up a fresh store name on the same entity, the same owner, and the same tax ID does not shake it.

Fourteen ways to get filed

An acquirer files you under one of fourteen reason codes. The ones that catch eCommerce operators most often:

• Code 04 (Excessive Chargebacks): the most common listing for online sellers. A chargeback ratio drifting toward or past roughly 1% is where acquirers start to act.
• Code 05 (Excessive Fraud): fraud-to-sales volume above the acquirer's tolerance.
• Code 12 (PCI-DSS Non-Compliance): a data-security failure on your checkout.
• Code 03 (Laundering) and Code 13 (Illegal Transactions): transaction-laundering or prohibited-product findings, common in miscoded high-risk categories.

Here is the part that stings: you are filed without warning. The termination and the MATCH report land in one motion, and to find out which of the fourteen codes you were filed under, you have to go back to the acquirer that terminated you and ask, because that is the only place the answer lives.

Five years, no time off for good behavior

A MATCH entry stays active for five years from the date it was added, then drops off automatically. There is no early "good behavior" removal for most codes.

Removal is narrow by design. An acquirer will generally only pull a listing in three situations: it was filed in error, it was the result of identity theft, or it was a PCI-DSS listing (code 12) and you have since proven compliance. And only the acquirer that listed you can remove it. Mastercard runs the database but does not adjudicate individual entries.

That means the clock matters more than almost anything else. A store terminated in a chargeback spike this year is still explaining itself to underwriters in 2031.

One owner, every store exposed

This is the part that catches operators running a portfolio. Because a MATCH listing attaches to the principal owner's name and tax ID, not only the store that was terminated, it does not stay contained to that one business.

Say you run four stores across four LLCs, which is a normal setup for a scaling dropshipper or reseller. One of them breaches its chargeback threshold and gets terminated and MATCHed. When you apply for a new merchant account for any of the other three, the underwriter runs your name and tax ID, and your listing surfaces. The clean businesses inherit the record of the one that failed.

A new legal entity does not solve it either, as long as you are the principal behind it. The listing follows the operator, so the exposure follows every business that operator owns. For sellers who deliberately spread volume across multiple MIDs and entities to reduce single-point-of-failure risk, a single MATCH listing can undo the entire structure at once.

Worse than a freeze

A reserve freezes a slice of your money. A processor review pauses your payouts. Both are painful and both are temporary. A MATCH listing is different in kind, because it attacks your ability to get paid at all.

Locked out of standard acquiring, a listed merchant usually ends up in one of two places. Either you cannot accept card payments at all while you scramble for a new processor, or you get boarded by a high-risk processor who knows you are on MATCH and prices accordingly: higher rates, a heavier rolling reserve, tighter volume caps. You keep processing, but on terms set by the fact that you had nowhere else to go.

For a scaling eCommerce operator, that is the difference between funding next month's inventory and ad spend on your own settlement, and financing it out of pocket while a reserve builds.

How to stay off it, and how to fight it

Protect the ratio before it protects itself. MATCH is downstream of termination, and termination is usually downstream of chargebacks. Watch your dispute ratio against the ~1% line, wire up chargeback alerts so disputes get resolved before they post, and fix the descriptor and refund gaps that quietly generate "I don't recognize this charge" claims.

Read the termination notice like a legal document. If a processor is closing your account, find out whether they are filing you to MATCH and under which code. That single detail decides whether you are dealing with a fixable dispute or a five-year listing.

If you are already listed, work the code, not the symptom. A listing filed in error or on a resolved PCI issue can be challenged directly with the acquirer that filed it. The other codes call for a different play: a clean processing history, corrected compliance, and an acquiring relationship built to underwrite a merchant with a MATCH record on file, rather than one that will bounce the application on sight.

MATCH is far easier to stay off than to get removed from, which is why the work that matters happens before a processor ever moves to terminate you.

Staying off MATCH comes down to staying compliant: keeping your chargeback ratio in range, your billing descriptors clean, your business category coded correctly, and your processing relationships built to hold up under a review.

That is the work Compaytence does. Our payment stack audit pinpoints where your compliance gaps and MATCH exposure sit, and our team helps you close them and get placed with processors built to keep your accounts in good standing, before an acquirer makes the decision for you.

Book a payment stack audit with Compaytence and find out where you stand while it is still your decision to make.