A new processor approves you, then reverses a few days later. Someone finally says the word: you’re on MATCH. You ask why, and the acquirer that put you there goes quiet. No reason code, no evidence, no explanation. That silence feels like the end of the road. It is not.
On the network’s own terms, the acquirer is supposed to hold a documented, substantiated reason for every listing. When they will not share it, that is often a sign the listing is thin, not that it is airtight. Here is how to pry the reason code loose, and how to read what the refusal is telling you.
Why the acquirer holds the cards
MATCH is Mastercard’s database, but Mastercard takes no merchant appeals. Only the acquirer that placed the listing can amend or remove it, and only they can tell you the reason code behind it. That is the same choke point that makes early removal hard, and we cover the removal mechanics in how merchants actually get off the MATCH list. The difference here is narrower: you are not yet fighting the listing, you are just trying to learn what it says.
An acquirer that will not substantiate a listing often cannot.
Four ways to get the reason code
A support-desk “no” is not the last word. Four routes, roughly in order of speed:
- Demand it in writing, to compliance or legal.Skip the account manager. Send a written request to the acquirer’s risk or legal team for the exact reason code, the listing date, and the supporting evidence, and cite the cause-for-termination clause in your merchant agreement. A paper trail matters if this escalates.
- Read it off a new application.When you apply with another acquirer, their underwriter queries MATCH and sees your reason code and listing details. A high-risk acquirer that knowingly underwrites listed merchants will often simply tell you what they see. That query is one screen inside a much wider file review, which we break down in what high-risk underwriters actually check. This is frequently the fastest route, and it lines up new processing at the same time.
- File a data-subject access request (EU/UK).A MATCH entry holds a principal’s personal data: name, home address, and ID. That makes an EU or UK individual a data subject, and a data-subject access request compels the acquirer to disclose the data it holds, and why, within about a month. US merchants have no equivalent right, because MATCH sits outside consumer-credit law.
- Send a specialist demand letter.A letter from a MATCH attorney lands in the acquirer’s legal department, where an unsubstantiated listing tends to get corrected rather than defended. It is the move that unsticks a truly stonewalling acquirer.
At a glance: the DSAR lever
- Tool
- Data-subject access request (DSAR)
- Who can use it
- An EU or UK individual principal
- Deadline to respond
- About one month, statutory
- What it compels
- The personal data held, and the reason for holding it
- US equivalent
- None, MATCH is outside consumer-credit law
Reconstruct it yourself
You almost always know why the relationship ended. The reason code maps closely to that cause, so you can usually infer it with confidence before anyone confirms it. That tells you whether you are in an early-exit lane or waiting out the five-year clock.
| What you remember | Likely code |
|---|---|
| Chargebacks climbed past the ceiling | 04 Excessive chargebacks |
| Card data was breached or leaked | 01 Account data compromise |
| A PCI audit failed and went unfixed | 10 or 12 Standards / PCI |
| The bank suspected you ran another firm’s volume | 03 Laundering |
| Confirmed fraud ran high against sales | 05 Excessive fraud |
Code meanings: Global Legal Law Firm, Mastercard MATCH reason codes.
When they still won’t budge
If the listing is valid, no amount of pressure removes it early unless it is remediated PCI (code 12) or evidenced identity theft (code 14). You manage the five years and keep trading through a high-risk acquirer that underwrites listed merchants. If the listing is wrong, the refusal to explain is your opening, not your dead end.
The tell
Treat a refusal to substantiate as a reason to push harder. Wrongful and unsupported listings are the ones that come off early, so a DSAR and a specialist demand letter do their best work exactly when an acquirer will not put the evidence on paper.
The bottom line
The reason code is not as secret as a stonewalling acquirer makes it feel. Get it in writing, read it off a fresh application, or compel it through a DSAR. If it turns out to be wrong, a demand letter usually finishes the job. Mastercard is a dead end. The bank that listed you is the lever, even when it is pretending it is not.
Can I find out my MATCH reason code without my old acquirer’s help?
Partly. There is no public self-lookup, but a new acquirer’s underwriter can see your reason code when they run your application, and in the EU or UK a data-subject access request can compel disclosure because the listing holds a principal’s personal data.
Is being refused an explanation a sign the listing is wrong?
Not proof, but a strong hint. Acquirers are expected to hold documented cause for a listing. A refusal to substantiate it is often a sign the listing is weak, and weak listings are the ones most likely to come off before the five-year term expires.
- Global Legal Law Firm, “Understanding Mastercard MATCH Reason Codes,” globallegallawfirm.com.
- Law Offices of Paul A. Rianda, “The MATCH List: A Blackhole,” riandalaw.com.
- Corepay, “The MATCH List & TMF File: Can You Get Unmatched?,” corepay.net.
- Information Commissioner’s Office, “Right of access,” ico.org.uk.
