VMSS removal / Elavon
VMSS removal through Elavon
If Elavon terminated your merchant account and added you to the Visa Merchant Screening Service (VMSS), Elavon is the only party that can submit a removal request to Visa. As a subsidiary of US Bank, Elavon operates with bank-level formality. This guide explains what their risk team expects and how to approach the process correctly.
Why Elavon adds merchants to the VMSS list
Elavon is a direct Visa acquirer and a subsidiary of US Bancorp. It operates with the compliance standards expected of a large US bank, including mandatory VMSS reporting when certain termination criteria are met. Common reasons Elavon 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).
- Illegal transactions — processing payments for goods or services unlawful under applicable law (VMSS code 24).
- Violation of agreement — material breaches of Elavon's merchant processing agreement or Visa's programme rules (VMSS code 30).
Elavon's account closure documentation will typically reference the category of termination. For full definitions, see our VMSS reason codes page.
What Elavon's risk team looks for
Elavon's compliance and risk review process reflects its bank-level ownership. Requests are reviewed formally and require a high standard of documentation. Your submission must address each of the following:
- Root cause — a specific, honest explanation of what caused the metrics or conduct that led to the VMSS listing. Elavon's reviewers expect directness and precision.
- Corrective actions — documented, implemented changes to your operations, compliance structure, or business model. Each action should be specific, dated, and verifiable.
- Evidence — formal supporting documentation appropriate to the reason code: compliance audits, updated policies, improved performance data, or restructured operations.
- No recurrence — a credible argument, backed by structural changes, that the root cause cannot repeat.
Only Elavon, as the acquirer that listed you, can submit a removal request to Visa. Given Elavon's bank-level processes, the request must be a formal written submission addressed to their risk or compliance department.
How to submit a VMSS removal request to Elavon
The process is:
- Confirm that Elavon was the acquirer that terminated your account and submitted the VMSS listing.
- Identify the VMSS reason code from your account termination notice or Elavon's formal correspondence.
- Prepare a comprehensive, structured written removal request addressing root cause, corrective actions, and evidence.
- Submit the request formally to Elavon's risk or compliance department — a written document with attachments, not a support call or informal email.
- Follow up through formal written channels if you do not receive a response within the expected timeframe.
We help you build and submit that request. Our questionnaire extracts the facts of your specific situation, and we draft a formally structured letter meeting the standards Elavon's compliance team expects. Start your removal request.
Frequently asked questions
- Can Elavon remove me from the VMSS list?
- Yes — if Elavon submitted the listing, only Elavon can request removal from Visa. Visa does not remove VMSS listings on direct merchant request.
- What does Elavon need to review a VMSS removal request?
- A formal written request with a specific root cause explanation, documented corrective actions, supporting evidence, and a no-recurrence argument. Elavon's bank-level compliance standards require the same quality of documentation expected in formal financial institution submissions.
- How long does Elavon take to review?
- Several weeks to a few months, reflecting Elavon's thorough, bank-level review process. A well-prepared formal submission is essential to progressing efficiently.