VMSS removal / By payment processor
VMSS removal by payment processor
The acquirer that added you to the Visa Merchant Screening Service (VMSS) is the only one that can request your removal from Visa. 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 VMSS reporting is triggered by Stripe Radar before a human reviewer is involved. Their risk team evaluates whether the underlying data pattern has materially changed — not just whether you've written a polite letter.
What Stripe's risk team evaluates
- →Updated fraud or dispute metrics showing a clear downward trend since the listing.
- →Specific changes to tooling, policies, or product that directly address the root cause.
- →PCI DSS compliance status and any third-party verification.
Our approach: Stripe's reviewers think in data. A submission that speaks their language — metrics, root cause, evidence — outperforms a narrative appeal every time.
Start your Stripe removal request →AdyenEnterprise compliance process+
Adyen holds its own banking licence in several jurisdictions and runs formal compliance review cycles. Their risk team expects structured, evidence-backed submissions. 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 with documented evidence — not a summary.
- →Updated internal controls relevant to the specific VMSS reason code.
Our approach: Adyen benchmarks submissions against financial services compliance standards. Tone, structure, and regulatory alignment matter as much as the underlying content.
Start your Adyen removal request →PayPalMulti-layer escalation+
PayPal's tiered support structure means VMSS removal requests often land with general seller support before reaching the risk reviewer who can action them. Getting routed correctly from the start is half the battle.
What PayPal's risk team evaluates
- →Clear identification of the VMSS listing as the subject — not a general account dispute.
- →Root cause and remediation evidence attached at first contact to avoid re-routing loops.
- →Professional framing that signals a compliance matter, not a support ticket.
Our approach: PayPal's routing challenge is unique to their structure. We know how to frame submissions so they escalate directly to the risk team without multiple bounces.
Start your PayPal removal request →Checkout.comFormal review cycles+
Checkout.com's compliance team runs structured review cycles and expects requests that demonstrate awareness of Visa's VMSS framework and the specific programme rules relevant to your reason code.
What Checkout.com's risk team evaluates
- →Explicit reference to the VMSS reason code and the Visa rules that apply.
- →A structured remediation plan, not a description of past events.
- →Evidence of corrective action — updated policies, PCI status, new operational controls.
Our approach: Checkout.com responds well to submissions that show familiarity with the VMSS framework itself, not just the merchant's own situation.
Start your Checkout.com removal request →WorldpayHigh-volume compliance team+
Worldpay handles one of the largest case volumes in the industry. Their compliance team deprioritises submissions that require follow-up for missing information — incomplete requests go to the back of the queue.
What Worldpay's risk team evaluates
- →A self-contained submission that anticipates every question their team might raise.
- →Clear identification of the specific Worldpay entity that held your account.
- →Complete evidence attached upfront — no follow-up assumptions.
Our approach: Completeness is the most important single factor with Worldpay. A thorough, well-organised submission moves faster than a partial one regardless of the underlying merits.
Start your Worldpay removal request →ElavonBank-standard compliance+
Elavon is a US Bancorp subsidiary and applies banking-sector compliance standards to VMSS removal reviews. Their review cycles are slower and more methodical than fintech processors.
What Elavon's risk team evaluates
- →A formal written request addressed to the Merchant Risk department.
- →BSA/AML and KYC compliance evidence where relevant to the reason code.
- →Language and structure consistent with financial services communication norms.
Our approach: Elavon's bank-owned structure means their compliance reviewers are conservative. A formally structured request that mirrors financial services norms significantly outperforms informal approaches.
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 — faster escalation, but first impressions carry more weight.
What Mollie's risk team evaluates
- →GDPR-compliant documentation and updated data processing policies where applicable.
- →A clear, concise remediation narrative — Mollie's team values directness.
- →Evidence of corrective action specific to the EU regulatory context.
Our approach: Mollie's lean team reads submissions carefully. A professionally written, complete request lands better here than at larger volume processors where cases are routed by committee.
Start your Mollie removal request →SquareData-driven risk review+
Square uses automated risk monitoring and VMSS reporting is triggered programmatically when Visa thresholds are crossed. Their risk team looks for evidence that the data signal behind the listing has materially changed.
What Square's risk team evaluates
- →Current dispute or fraud rate metrics showing improvement since the listing date.
- →Specific operational changes that directly address the automated risk trigger.
- →Evidence that the change is structural and sustained, not temporary.
Our approach: Like Stripe, Square's reviewers think in data. A request that addresses the algorithmic trigger directly — with updated numbers — outperforms 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 daily.
- →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 is deeply integrated with financial institutions and their compliance team applies standards consistent with banking sector norms. Review cycles are measured in weeks and expect formal, complete submissions.
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 since the listing.
Our approach: FIS compliance teams operate like a bank's internal compliance department. Regulatory language 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 VMSS reporting flows through Stripe's Visa relationship. The challenge is that you interact with Shopify's support layer first — getting to the actual risk reviewer requires explicit escalation.
What Shopify Payments's risk team evaluates
- →A submission clearly labelled as a VMSS removal request from the first contact.
- →The same data-driven evidence Stripe's risk team evaluates — since they are the underlying acquirer.
- →An explicit escalation request to the Payments Risk team at first contact.
Our approach: The Shopify/Stripe routing layer slows many merchants down unnecessarily. We know how to frame submissions to cut through it and reach the right reviewer.
Start your Shopify Payments removal request →SumUpSME-focused, lean compliance team+
SumUp is an EU-licensed acquirer primarily serving small businesses. Their lean compliance team means faster escalation — but also that your submission needs to be complete and well-framed on first contact.
What SumUp's risk team evaluates
- →A concise, direct remediation narrative without unnecessary padding.
- →Evidence of the specific change that addresses the VMSS reason code.
- →Acknowledgement of the business context — SumUp's team understands SME constraints.
Our approach: SumUp's reviewers 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 VMSS removal requests against UK financial regulatory standards alongside Visa's programme rules.
What Trust Payments's risk team evaluates
- →Current PCI DSS certification and evidence of FCA compliance obligations met.
- →A formal request addressed specifically to the Risk or Compliance team.
- →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 in their review.
Start your Trust Payments removal request →Frequently asked questions
- Can I contact Visa directly to be removed from VMSS?
- No. Only the acquirer that reported you to VMSS can submit a removal request to Visa. Visa does not remove listings on direct merchant request.
- 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 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 questions about your situation and the VMSS reason code. Based on your processor, we draft a removal letter that addresses the specific criteria their risk team evaluates. Start here.