Can I write my own MATCH removal letter?

Yes. There is no rule preventing a merchant from writing their own removal letter. The question is whether a self-written letter will be credible and persuasive to the PSP's risk team. Risk teams read many removal requests and can identify letters that are generic, evasive, or miss the point of the specific reason code. A well-written, specific, evidence-backed letter is what matters — whether you write it yourself or get professional help.

Will a template letter work?

In most cases, no. PSP risk teams read many removal requests and are experienced at identifying boilerplate. A template that was written for a different merchant, a different reason code, or a different PSP will not address your specific situation. If the letter does not clearly explain your root cause, your corrective actions, and your evidence, it will not advance your case — and may actively signal that you do not understand your own situation.

What does a removal letter actually need to include?

A strong MATCH removal letter needs four things: a specific, honest explanation of the root cause of the listing; documented corrective actions that have been implemented (not proposed); supporting evidence appropriate to the reason code; and a credible no-recurrence argument backed by structural changes. Everything should be addressed to the specific PSP and specific reason code on your listing.

MATCH list removal letter: why there is no universal template

If you searched for a MATCH list removal letter template, you are not alone. It is one of the first things merchants look for after discovering a listing. The instinct makes sense — find something that worked, fill in the gaps, send it. But the reality of how MATCH removal requests are reviewed means that approach consistently fails. Here is why.

What people mean when they search for a template

Merchants searching for a MATCH removal letter template are looking for a starting point: a structure to follow, a tone to match, a set of sections to fill in. That is a reasonable place to start. Writing a formal letter to a payment processor's risk department is unfamiliar territory for most business owners, and it is natural to want a model.

The problem is not the search — it is what templates actually are. A template written for a merchant terminated for excessive chargebacks will structure arguments around dispute ratios and chargeback prevention. A merchant terminated for identity issues or policy violations has a fundamentally different case to make. If you use the wrong template, you are not just starting from the wrong place — you are making arguments that do not apply to your situation, which signals to the risk team that you do not understand why you were listed.

Every MATCH listing has a specific reason code, a specific PSP that submitted it, and a specific set of facts behind it. A letter that does not address all three is not a removal request — it is correspondence that the risk team will set aside.

Why a MATCH removal letter cannot be templated

PSP risk teams are specialists. They review removal requests regularly, and they are experienced at identifying submissions that were written without a clear understanding of the merchant's actual situation. A generic letter has several recognisable characteristics: it does not name the specific reason code; it makes broad assurances about improvements rather than describing specific, dated changes; it omits evidence; and it uses language that could have been written for any merchant.

When a risk reviewer sees those characteristics, they draw a conclusion: the merchant did not take the time to understand their own listing, which suggests they may not have genuinely addressed the underlying problem. That conclusion undermines the entire purpose of the removal request.

Beyond credibility, there is a structural reason templates fail. A strong removal letter needs to address:

The specific MATCH reason code — each code has different criteria, and the letter must speak directly to what that code measures.
The specific PSP — different acquirers have different risk cultures, review processes, and documentation expectations. What works at a developer-focused fintech is different from what works at a traditional bank-owned acquirer.
The merchant's actual root cause — a letter must explain what specifically happened in this business, not what might have happened in a hypothetical business.
Concrete, verifiable corrective actions — the letter must describe changes that are in place and can be evidenced, not intentions.

None of those elements can be templated. They are the specific facts of your case, and they are what the removal letter exists to convey.

What a strong removal request looks like

A strong MATCH removal request is written in the language of a risk analyst: specific, factual, and structured. It does not argue that the listing was unfair or that the merchant is a good business. It addresses what happened, what changed, and why it cannot happen again.

The structure that works is consistent across PSPs, even if the content varies:

Root cause — a specific, honest explanation of the factor or combination of factors that caused the listing. This should name what happened, when it started, and why it was not caught earlier.
Corrective actions — a list of specific changes implemented since termination, named and dated. Each action should connect directly to the root cause.
Evidence — attached or referenced documents that demonstrate the corrective actions are real: updated policies, compliance certifications, system changes, lower dispute data, restructured product lines, or other relevant evidence.
No-recurrence argument — a clear, operational explanation of why the root cause cannot repeat. This should be grounded in the specific changes made, not a general assurance of intent to comply.

The letter should be addressed to the specific PSP's risk department by name, should reference the MATCH reason code, and should be written in a professional but direct tone. It is not a legal document and should not read like one. It is a communication from one professional to another.

How we approach it

We do not use templates either. A template-based letter is not something we produce, because it would not serve merchants well.

What we do instead is use a structured questionnaire to extract the specific facts of your situation: the reason code, the PSP, what actually caused the listing, what has changed since, what evidence exists, and how your business operates now. From those facts, we build a letter that addresses your specific case — written in the language that PSP risk teams recognise and find credible.

The result reads like it was written by someone who understands both your business and how PSP risk teams think. Because it is. Every element of the letter connects to the facts of your case and the expectations of the specific acquirer reviewing it.

Start your removal request — no template, just a letter built for your case.

Frequently asked questions

Can I write my own MATCH removal letter?: Yes — there is no rule against it. The question is whether it will be credible and persuasive to the PSP's risk team. A self-written letter can work if it is specific, honest about root cause, backed by evidence, and addresses the correct reason code. Generic, vague, or legally defensive language tends to weaken a case rather than strengthen it.
Will a template letter work?: In most cases, no. PSP risk teams are experienced at identifying boilerplate. A template written for a different merchant, reason code, or PSP will not address your specific situation and may signal to reviewers that you do not understand your own listing.
What does a removal letter actually need to include?: Four things: a specific root cause explanation, documented corrective actions that are already in place, supporting evidence appropriate to the reason code, and a credible no-recurrence argument backed by structural changes — all addressed to the specific PSP and reason code on your listing.