MATCH list removal / By payment processor
MATCH list removal by payment processor
The acquirer that added you to MATCH is the only one that can request your removal from Mastercard. Each processor's risk team has different review criteria — a generic letter rarely works. Select your processor below to see what their team evaluates, and how we tailor your request to match.
StripeAutomated risk systems+
Stripe's MATCH decisions are triggered by Stripe Radar before a human reviewer is involved. Their risk team evaluates whether the underlying data pattern has genuinely changed — not just whether you've written a polite letter.
What Stripe's risk team evaluates
- →Updated fraud or dispute metrics that show a clear downward trend.
- →Specific changes to tooling, policies, or product that address the root cause.
- →PCI DSS compliance status and any third-party verification.
Our approach: Stripe's reviewers are technical. A letter that speaks their language — data, root cause, evidence — performs significantly better than a narrative appeal.
Start your Stripe removal request →AdyenEnterprise compliance process+
Adyen operates under its own banking licence and runs a formal compliance review cycle. Their risk team expects structured, evidence-backed submissions — not emails. Incomplete requests are deprioritised without follow-up.
What Adyen's risk team evaluates
- →Formal remediation documentation aligned with AML and KYC standards.
- →A structured root cause analysis, not a summary.
- →Evidence of updated internal controls relevant to the reason code.
Our approach: Adyen serves regulated industries and benchmarks submissions against financial services compliance standards. Tone and structure matter as much as content.
Start your Adyen removal request →PayPalMulti-layer escalation+
PayPal's tiered support structure means removal requests often land with general seller support before reaching the risk reviewer who can actually action them. Getting routed correctly from the start is half the battle.
What PayPal's risk team evaluates
- →Clear identification of the MATCH listing as the specific subject — not a general account dispute.
- →Root cause and remediation evidence attached at first contact to prevent re-routing loops.
- →Professional tone that signals this is a compliance matter, not a support ticket.
Our approach: PayPal's risk team uses the same core review framework as other acquirers, but the routing challenge is unique. We know how to frame submissions so they escalate directly.
Start your PayPal removal request →Checkout.comFormal review cycles+
Checkout.com's compliance team is organised around formal review cycles and expects requests that reference the specific Mastercard MATCH rules relevant to your reason code. They value regulatory awareness in submissions.
What Checkout.com's risk team evaluates
- →Explicit reference to the MATCH reason code and the Mastercard rules that apply.
- →A structured remediation plan, not a description of what happened.
- →Evidence of corrective action — updated policies, PCI status, new operational controls.
Our approach: Checkout.com responds well to submissions that demonstrate familiarity with the MATCH framework, not just the merchant's own situation.
Start your Checkout.com removal request →WorldpayHigh-volume compliance team+
Worldpay handles one of the highest case volumes in the industry. Their compliance team deprioritises incomplete submissions — if your request requires follow-up for missing information, it goes to the back of the queue.
What Worldpay's risk team evaluates
- →A self-contained submission that anticipates every question their team might ask.
- →Clear identification of the Worldpay entity (UK, US, etc.) that held your account.
- →Complete evidence attached upfront — no follow-up assumptions.
Our approach: With Worldpay, completeness is the most important single factor. A well-organised, thorough submission moves faster than a partial one, regardless of merit.
Start your Worldpay removal request →ElavonBank-standard compliance+
Elavon is a US Bancorp subsidiary and applies banking-sector compliance standards to MATCH removal reviews. They run slower, more methodical review cycles than fintech processors and expect formal written requests.
What Elavon's risk team evaluates
- →Formal written request addressed to the Merchant Risk department — not a support submission.
- →BSA/AML and KYC compliance evidence where relevant to the reason code.
- →Language and structure consistent with financial services communication standards.
Our approach: Elavon's bank-owned structure means their compliance team is conservative. A formally structured request that mirrors financial services norms outperforms informal approaches significantly.
Start your Elavon removal request →MollieEU-regulated, accessible team+
Mollie is DNB-licensed and follows Dutch and EU regulatory frameworks. Their compliance team is smaller than enterprise processors, which means faster escalation — but also that first impressions matter more.
What Mollie's risk team evaluates
- →GDPR-compliant documentation and updated data processing policies where relevant.
- →Clear, concise remediation narrative — their team values directness.
- →Evidence of corrective action specific to the EU regulatory context.
Our approach: Mollie's smaller team means your submission gets read carefully. A professionally written, complete request lands better here than at larger volume processors.
Start your Mollie removal request →SquareData-driven risk review+
Square uses automated risk monitoring and MATCH reporting kicks in when Visa thresholds are crossed programmatically. Their risk team is looking for evidence that the data signal that triggered the listing has materially changed.
What Square's risk team evaluates
- →Current dispute or fraud rate metrics showing improvement since the listing.
- →Specific operational changes that directly address the automated risk trigger.
- →Evidence that the change is structural, not temporary.
Our approach: Like Stripe, Square's reviewers think in data. A request that addresses the algorithmic trigger directly — with numbers — is more persuasive than a narrative explanation.
Start your Square removal request →FiservEnterprise volume, formal review+
Fiserv acquires under several brand names including First Data and processes enterprise-scale case volumes. Their compliance team runs formal review processes and expects self-contained, professionally structured submissions.
What Fiserv's risk team evaluates
- →Clear identification of the Fiserv entity or brand that terminated your account.
- →A structured submission with an executive summary — reviewers handle many cases.
- →Complete evidence appendix attached at submission, not referenced externally.
Our approach: Fiserv's scale means cases are routed by teams, not individuals. A submission with a clear executive summary gets processed faster than one that buries the key points.
Start your Fiserv removal request →FISFinancial institution standards+
FIS (Fidelity National Information Services) is deeply integrated with financial institutions and their compliance team applies standards consistent with banking sector norms. Review cycles are measured in weeks, not days.
What FIS's risk team evaluates
- →Formal language and structure consistent with financial services communication.
- →Current PCI DSS and AML compliance evidence.
- →Clear reference to regulatory obligations met — FIS compliance teams benchmark against these.
Our approach: FIS operates like a bank's compliance department. Regulatory language, formal structure, and documented compliance evidence are the strongest signals you can send.
Start your FIS removal request →Shopify PaymentsStripe infrastructure, Shopify routing+
Shopify Payments is built on Stripe's acquiring infrastructure in most markets, so the MATCH reporting flows through Stripe's relationship with Mastercard. The challenge is that you interact with Shopify's support layer first — routing to the actual risk reviewer requires explicit escalation.
What Shopify Payments's risk team evaluates
- →A submission clearly labelled as a MATCH removal request from the first contact.
- →The same data-driven evidence Stripe's risk team evaluates — since they are the underlying acquirer.
- →Explicit escalation request to the Payments Risk team at first contact.
Our approach: The Shopify/Stripe relationship creates a routing layer that slows many merchants down. We know how to frame submissions to cut through it.
Start your Shopify Payments removal request →SumUpSME-focused, lean compliance team+
SumUp is an EU-licensed acquirer primarily serving small businesses. Their compliance team is lean, which means faster escalation — but also that your submission needs to be complete and well-framed on first contact.
What SumUp's risk team evaluates
- →Concise, direct remediation narrative without unnecessary padding.
- →Evidence of the specific change that addresses the reason code.
- →Acknowledgement of the business context — SumUp's team understands SME constraints.
Our approach: SumUp's reviewers read requests carefully and appreciate directness. A clear, honest, and complete submission performs better here than an overly formal one.
Start your SumUp removal request →Trust PaymentsFCA-regulated, UK-focused+
Trust Payments holds FCA authorisation and operates as a Visa acquirer across Europe. Their compliance team evaluates MATCH removal requests against UK financial regulatory standards alongside Mastercard's programme rules.
What Trust Payments's risk team evaluates
- →Current PCI DSS certification and evidence of FCA compliance obligations met.
- →Formal request addressed to the Risk or Compliance team specifically.
- →Documentation showing the regulatory framework has been followed since the listing.
Our approach: FCA regulation shapes how Trust Payments' team evaluates submissions. Regulatory compliance evidence — PCI DSS, AML policies — carries significant weight.
Start your Trust Payments removal request →Frequently asked questions
- Can I contact Mastercard directly to be removed from MATCH?
- No. Only the acquirer that reported you can submit a removal request to Mastercard. You must go back to that specific processor.
- Why does the processor matter for the removal request?
- Each acquirer's risk team has different review criteria, communication standards, and timelines. A request written for Stripe's data-driven review process looks very different from one written for Worldpay's formal compliance team. Generic letters rarely succeed.
- How do you tailor the request to my processor?
- We ask you a set of questions about your situation and the MATCH reason code. Based on your processor, we draft a removal letter that addresses the specific criteria their risk team evaluates — not a generic template. Start here.