VMSS removal / Fiserv
VMSS removal through Fiserv
If Fiserv terminated your merchant account and added you to the Visa Merchant Screening Service (VMSS), Fiserv is the only party that can submit a removal request to Visa. As one of the largest US financial technology and payment processing companies, Fiserv operates a formal, institution-level compliance process. This guide explains what their risk team expects and how to approach a removal request.
Why Fiserv adds merchants to the VMSS list
Fiserv is a large US financial technology company providing payment processing and acquiring services to a wide range of businesses. It holds direct Visa acquiring relationships and is subject to Visa's mandatory VMSS reporting requirements. Common reasons Fiserv submits VMSS listings include:
- Excessive fraud — fraud ratios crossing Visa's programme thresholds over a defined measurement period (VMSS code 21).
- Excessive disputes — dispute ratios and volumes exceeding Visa's operating limits (VMSS code 22).
- Transaction laundering — processing transactions for undisclosed businesses through a Fiserv-acquiring merchant account (VMSS code 23).
- Violation of Visa rules — breaches of Visa's operating regulations or Fiserv's processing agreement (VMSS code 31).
Your account termination notice from Fiserv will typically reference the reason category. For full definitions, see our VMSS reason codes page.
What Fiserv's risk team looks for
Fiserv's compliance and risk review operates at institutional scale. Removal requests are reviewed formally and require comprehensive documentation. Your submission must address each of the following:
- Root cause — a detailed, specific account of the factors that led to the VMSS listing. Institutional risk reviewers expect precision and honesty, not generalised explanations.
- Corrective actions — specific, documented changes implemented since the termination. Each corrective measure should be named, dated where possible, and verifiable through evidence.
- Evidence — comprehensive supporting documentation: compliance audits, updated policies, improved performance metrics, PCI DSS certificates, or operational restructuring relevant to the reason code.
- No recurrence — a credible structural argument for why the root cause cannot repeat, backed by demonstrable operational changes.
Only Fiserv, as the acquirer that listed you, can submit a removal request to Visa. Given Fiserv's scale, the request must be routed to the correct internal compliance or risk team — generic support channels are unlikely to reach the relevant reviewers.
How to submit a VMSS removal request to Fiserv
The process is:
- Confirm that Fiserv was the acquiring entity that terminated your account and submitted the VMSS listing.
- Identify the VMSS reason code from your termination notice or Fiserv's account closure correspondence.
- Prepare a comprehensive, structured written removal request addressing root cause, corrective actions, and evidence — at the level expected of a formal institutional compliance submission.
- Submit the request to Fiserv's risk or compliance department through the appropriate formal channel, not general merchant support.
- Follow up formally if you do not receive a substantive response within the expected timeframe.
We help you build and submit that request. Our questionnaire extracts the specific facts of your case, and we draft a formally structured letter suited to Fiserv's institutional review process. Start your removal request.
Frequently asked questions
- Can Fiserv remove me from the VMSS list?
- Yes — if Fiserv submitted the listing, only Fiserv can request removal from Visa. Visa does not remove VMSS listings on direct merchant request.
- What does Fiserv need to review a VMSS removal request?
- Comprehensive written documentation: a specific root cause analysis, documented corrective actions with evidence, and a credible structural no-recurrence argument. Requests must meet the documentation standard expected in institutional compliance submissions.
- How long does Fiserv take to review?
- Several weeks to several months, reflecting Fiserv's scale and formal review process. A comprehensive, well-structured submission routed to the correct team is essential to progressing efficiently.