MATCH code 12 is the PCI DSS non-compliance reason code, and it is the only entry on the table with a genuine removal path before the automatic five-year purge. Mastercard’s rules let the acquirer that placed the listing remove it once that acquirer has confirmed the business is compliant. No other code works that way.
Why MATCH code 12 is different from every other code
Every other reason on the table records something that happened and cannot be undone. Excessive chargebacks in a given month either occurred or did not. A bankruptcy filing is a matter of record. A fraud conviction is a fact about the past.
Code 12 records a state rather than an event. A business that was not compliant with the card data security standards can become compliant, and once it has, the thing the listing describes is no longer true. Mastercard’s rules recognise that: a processor may remove a MATCH entry where it added the business in error, or where the listing is code 12 and the processor has confirmed the business is now compliant. Those are the only two removal routes in the whole system.
What removal actually requires
The acquirer that placed the listing has to confirm compliance and then act. Both halves matter, and the second one is where most cases stall.
Confirmation means evidence in the form that acquirer accepts, which in practice means the appropriate self-assessment questionnaire or report on compliance for your merchant level, current rather than historical, plus scan results where your setup requires them. Acting means the acquirer actually submitting the removal. An acquirer that has already ended the relationship has no commercial reason to hurry, so this generally takes persistence and a written record of every exchange.
Where code 12 listings come from
Rarely from a business that decided security did not matter. Far more often from a lapse that nobody was watching: a quarterly scan that stopped running after a hosting change, a self-assessment questionnaire that went unfiled for a year, a storage practice inherited from an old system, or a breach investigation that found the environment out of scope.
The most common of all is simply outgrowing your validation level without noticing. A business that crosses into a higher merchant level takes on heavier validation requirements, and the paperwork that satisfied the old level no longer satisfies the new one.
What to do if you hold a code 12 listing
Fix the underlying issue first, properly, because there is no point requesting removal on the strength of a promise. Then assemble the evidence pack: the current attestation of compliance, scan results if applicable, and a short factual note describing what was wrong and what changed.
Send it to the acquirer that placed the listing, not to Mastercard, which publishes that it does not assess the accuracy of listings and is not the party that can remove one. Ask specifically for removal of the MATCH entry, reference code 12, and ask for written confirmation once it is done. Keep every exchange. If the acquirer declines or goes quiet, the fallback is the same as any other listing, which is finding an acquirer that will board you as listed, covered in getting a merchant account after a MATCH listing.
Being listed while you sort it out
The listing does not stop you looking for an account. Code 12 is among the more placeable codes precisely because it is remediable, and an underwriter who can see current compliance evidence in the file will read it very differently to an open compliance failure.
Bring the attestation to the application rather than waiting to be asked. A file that arrives with proof of current compliance answers the obvious objection before it is raised, which is worth more than any explanation. The wider view of how these files are read is in what underwriting actually looks at, and the full code table is on our MATCH list reference page.
What removal does not do
Removal clears the MATCH entry. It does not reverse the termination, recover held funds, or oblige the original acquirer to take you back. It also does not affect a separate listing under a different code, if one exists, or a Visa Merchant Screening Service entry, which runs on its own rules.
And it does not make the underlying history invisible. An underwriter reading your statements will still see the gap where processing stopped, and will ask about it. Having a clean answer, backed by the removal confirmation, is a strong position rather than an awkward one. What comes next is in what to do when your processor drops you.
Frequently asked questions
How long does removal take once I am compliant? It depends entirely on the acquirer, since it is their submission to make. Persistence and a written trail help more than anything else.
Can a new acquirer remove a code 12 listing for me? No. Only the acquirer that placed the entry can remove it, whatever the code.
If nobody removes it, what happens? MATCH records are purged automatically five years after they are added, with no application needed.
Does becoming compliant help even without removal? Yes. Current compliance evidence in an application file materially changes how a code 12 listing reads to a new underwriter, whether or not the entry itself has been cleared.
Sources: Mastercard Security Rules and Procedures Merchant Edition (SPME manual), and Stripe’s published documentation at docs.stripe.com/disputes/match.