MATCH List and TMF Removal: How to Get Off the List

How MATCH and TMF work, what a listing means for your next application, and the realistic path from listed to processing again.

  • By the OpenGate underwriting desk
  • Updated
  • 11 min read

The MATCH list, which the industry still calls TMF, is a Mastercard-run database where acquirers record merchants they have terminated. A listing follows you across processors for roughly five years and blocks most standard applications. To get off the MATCH list earlier, the acquirer that added the record has to remove it. This guide explains how listings happen, what one costs you and how removal works.

What MATCH and TMF are

MATCH stands for Mastercard Alert To Control High-risk Merchants. Older documents expand it as Member Alert to Control High-Risk Merchants, and Mastercard now calls the service MATCH Pro. TMF, the Terminated Merchant File, is the name the industry used for decades and never dropped. Both names describe the same system: a Mastercard-operated database that acquiring banks query when they underwrite a new merchant, and that they write to when they terminate one.

A record contains the merchant’s name, the adding acquirer, the termination date and a reason code. A record typically stays in the database for five years. The database is not public, and a merchant cannot browse it. The merchant can, however, learn his status through the banks that query it. The five-year retention is the key fact for planning: most merchants outlive their listing, provided they do not get listed again.

Mastercard operates MATCH, and other card networks run their own terminated-merchant systems with the same function. The mechanics below apply to all of them: a bank records a termination, the record blocks standard applications, and removal goes through the recording bank.

How merchants get listed

The record is created by the acquiring bank, at termination, when the termination meets the network’s criteria for reporting. The reason families most records fall into:

  • Fraud. Excessive fraud, transaction laundering, or transactions obtained under a threat to the cardholder.
  • Card data security. Card data compromised through the business, or a failure to comply with the card data security standard, PCI DSS.
  • Excessive chargebacks. A dispute ratio that stayed above the monitored thresholds until the acquirer terminated the account.
  • Violation of network standards. Noncompliance with card network rules, including prohibited business activity discovered after onboarding.
  • Bankruptcy or financial failure. The merchant filed for bankruptcy, or the business failed with outstanding obligations.
  • Illegal transactions. Processing that broke the law.
  • Identity theft. An account opened with a stolen identity, where the real person or company may not know a record exists.

The reason recorded is the acquirer’s, and it travels with the record. Note what the list is not: a consumer credit report, a public registry, or a court judgment. It is a private risk tool shared among acquiring banks, and it functions exactly like one. You are entitled to know the code: as of the August 2026 edition of Mastercard’s rules, the acquirer has to give a merchant who asks the reason code and the identity of the institution that added the record. Ask in writing. What matters next is the family: fraud, data security, chargebacks, standards, financial or legal. How to check the MATCH list comes down to written requests like that one, because no merchant can query the database directly.

Who sees the list and when

Acquirers query the database during underwriting, before they issue a merchant account. The query happens as a routine step, the same way a bank checks identity documents. When a standard application stalls with no explanation, a database hit is the usual suspect, because acquirers treat a hit as an automatic decline in most cases.

Acquirers are cautious about discussing the database, but a merchant can learn his status in practice. Ask a processor, in writing, whether a database listing is blocking the application, and many will confirm the obstruction even when they do not quote the record itself. The check costs nothing to request, and it belongs in your file before you invest weeks in an application.

The consequences of a listing

The effects are immediate and compound.

  • Standard applications get declined at the underwriting step, often before the underwriter reads the business model.
  • Approvals that do happen come with tighter terms: higher reserves, lower caps, slower settlement.
  • The record follows the business, its principals and sometimes related entities, so renaming the company rarely helps.
  • Time is the main cost. Five years of friction from a record that took minutes to create.

The consequences are serious, and they are not permanent. The rest of this guide covers the two paths out: removal and the five-year clock.

How to get off the MATCH list: the removal process

One rule governs almost everything: removal goes through the acquirer that added the record. As of the August 2026 edition of Mastercard’s rules, Mastercard removes a record in two cases: the adding acquirer reports that it listed the merchant in error, or the record was added for PCI DSS noncompliance and the merchant has since become compliant. In that second case a merchant whose acquirer will not act may send the request to Mastercard itself, with the validation the rules ask for. No other processor and no third party can delete a record from the outside. Work the process below with that rule in mind.

  1. Confirm the listing. Ask a processor to check the database against your business name and principal owners, and request the result in writing where the processor will provide it.
  2. Identify the adding acquirer and the reason. The record names the bank that added it. Ask that acquirer in writing for the reason code: Mastercard’s rules oblige it to answer questions about a listing, within 7 calendar days as of the August 2026 edition. If no answer comes, reconstruct the reason from your termination history: who closed you, and what the termination letter said. A closure by Stripe or PayPal is a different event from a MATCH record, and the guide to a closed Stripe or PayPal account covers it.
  3. Resolve the underlying problem first. The adding acquirer will not remove a record while the cause stands. Pay the outstanding balance, close the dispute wave, document the fix. A removal request that arrives with the cause unresolved goes to the bottom of the pile.
  4. Ask the adding acquirer to remove or correct the record. Write to the acquirer’s risk or merchant services department, state the case, attach the evidence that the cause is resolved, and ask for removal or a correction of the reason code. One clear letter beats a campaign, and it creates the paper trail you need for step 5.
  5. Escalate in writing, then wait. Mastercard’s rules give the acquirer 30 days to answer a removal request, as of the August 2026 edition, and an answer is not a removal. Follow up at intervals, keep every reply, and give the review time. Removal requests that succeed take months.
  6. Verify with a fresh inquiry. After the acquirer confirms removal, have another processor re-run the check and confirm the record is gone before you apply anywhere.

Two cautions. First, never pay a service that promises removal for a fee: no outside party can deliver that, and the money is lost. Second, never hide the listing from a processor you apply to. The underwriter finds it anyway, and the concealment becomes part of the file.

Realistic odds

The odds depend entirely on the reason code, and honest merchants deserve honest numbers.

A record added for fraud is rarely removed before the five-year expiry. The adding acquirer risks its own standing by clearing a fraud record, so it declines the request. The clock, not the appeal, is the path for that code. A record added for excessive chargebacks can be revisited: a merchant who shows a sustained period of clean processing and a fixed operation has a case, but the decision stays with the adding acquirer. A record added for bankruptcy or administrative reasons sits in the middle. A record added for PCI DSS noncompliance has a written route once you are compliant, and a record added in error, which happens, has the best removal odds of all.

Set expectations accordingly. Removal is a negotiation with a bank that ended a relationship. Most merchants succeed through the five-year clock plus a clean new history, and they plan around that reality instead of betting on an appeal. Acquirers also review removal requests on their own calendar, not yours, so start the process early and let the clock run in parallel.

Applying while listed

A listing blocks standard applications. It does not end the industry conversation. Specialized processors review listed files instead of auto-declining them, and those reviews follow a pattern you can prepare for.

  • Disclose the listing before the underwriter finds it. State the reason, the acquirer and the date, and attach the termination letter.
  • Bring the evidence that the underlying problem is fixed: paid balances, clean statements from any channel you still run, policy changes documented.
  • Target processors that review listed files, and skip the ones whose terms auto-decline them.
  • Expect tighter terms at first: a higher reserve, a lower cap, slower settlement. The rolling reserves guide explains what those terms mean in cash, and the pricing guide shows how sector risk lands in a quote.
  • Rebuild with clean volume. The new history is the argument for the next application and the next renegotiation.

OpenGate reads listed files rather than auto-declining them. The underwriting process describes how a file is reviewed, and the desk answers whether your vertical and your listing can be placed. The review separates the record from the merchant: the same reason code on two different files leads to two different answers, because the file, not the label, carries the decision.

Common mistakes with a listing

Listed merchants make the same five errors, and each one extends the problem.

  • Paying a removal service. No third party can delete a record, and the fee buys paperwork.
  • Hiding the listing from the next processor. The underwriter finds it, and the concealment poisons the file.
  • Applying to mainstream processors that auto-decline. Each decline burns weeks and records nothing useful.
  • Renaming the company and hoping. Records attach to principals and patterns, not just names.
  • Ignoring the five-year clock. The clock runs whether you act or not, and the merchants who plan around it rebuild fastest.

Every error has the same root: treating the list as a punishment instead of a risk record. The underwriters who read listed files are looking for merchants who fixed the cause. Be that merchant, and the listing becomes a footnote instead of a wall.

Staying off the list after you are back

A second listing resets the five-year clock, and the acquirer that adds it reads the first record as evidence of a pattern. The habits that keep you off the list are the same habits that keep any high-risk account alive: keep the dispute ratio below the monitored thresholds, tell your processor about changes before they happen, and resolve every warning in its window. The chargeback playbook covers the ratio side. The industries hub shows the verticals where these rules apply in full, starting with CBD and hemp and casino and sportsbook.

What to send if you apply while listed

A listed file gets read on its facts, so gather them first: the termination letter, the name of the acquirer that closed the account, your last three to six months of statements and the proof that the cause is resolved. State the listing in the first lines of your message.

Then send the file for review. A human underwriter reads it within 1 business day and tells you where the file stands: an offer, a list of missing documents, or an honest no. Applying is free, and a no comes with its reasons.

FAQ

Frequently asked questions

How long does a MATCH listing last?

Typically five years from the date the adding acquirer created the record. The clock does not reset unless a new acquirer adds a new record.

Can I check if I am on the MATCH list?

You cannot browse the database yourself, but you can ask a processor to check it during an application. Many will confirm in writing that a database hit is blocking you, which is the practical way to learn your status.

Can a removal service get me off the MATCH list?

No. Mastercard removes a record when the acquirer that added it reports an error, or confirms that a merchant listed for a card data security failure has become compliant. A third party has no access to either route. Any service that sells guaranteed removal is selling paperwork.

Can I open a new company to escape the MATCH list?

Rarely. The record can attach to principals as well as the business, and underwriters trace ownership across entities. A variant company reads as evasion, which worsens the file.

Does a MATCH listing follow me personally?

It can. Records commonly include the names of principals, so the same people opening a new business can carry the hit into the new application. Disclose, fix the underlying cause, and let the clock run.

OpenGate Payments

Prefer to talk it through?

Every guide ends where the desk begins. Send your file and get a written answer.

Free to apply. A human answer within 1 business day.

Apply to start processing