VMSS removal / Square
VMSS removal through Square
If Square terminated your merchant account and added you to the Visa Merchant Screening Service (VMSS), Square is the only party that can submit a removal request to Visa. Square's risk decisions are often algorithm-driven, but their risk team can review and process removal requests. This guide explains what they need and how to reach them.
Why Square adds merchants to the VMSS list
Square primarily serves small and micro-businesses and uses automated risk models to monitor merchant performance at scale. Despite its SMB focus, Square holds direct Visa acquiring relationships and is required to submit VMSS reports when programme thresholds are breached. Common listing reasons include:
- Excessive disputes — dispute ratios crossing Visa's programme thresholds, which can occur rapidly for smaller merchants operating in dispute-prone categories (VMSS code 22).
- Excessive fraud — fraud levels detected through Square's automated risk monitoring (VMSS code 21).
- Violation of agreement — breaches of Square's seller agreement or Visa's operating rules, including selling prohibited items (VMSS code 30).
- Transaction laundering — processing payments for undisclosed or third-party businesses through a Square account (VMSS code 23).
Square's account deactivation notice may not always be specific about the VMSS reason code. For full definitions, see our VMSS reason codes page.
What Square's risk team looks for
While Square's initial termination decisions are often automated, removal requests are reviewed by human risk analysts. A credible submission needs to address each of the following in plain, specific terms:
- Root cause — an honest, direct explanation of what drove the metrics or behaviour that triggered the listing. For Square merchants, this often involves dispute patterns, product category issues, or fulfilment practices.
- Corrective actions — specific changes made since the termination: updated fulfilment processes, revised return policies, adjusted product categories, or improved customer communication.
- Evidence — documentation supporting the changes: updated policies, new business processes, or other verifiable evidence appropriate to the reason code.
- No recurrence — a credible explanation of the changes that structurally prevent the root cause from recurring.
Only Square, as the acquirer that listed you, can submit a removal request to Visa. The escalation path within Square goes through their risk team, reachable via their merchant support channels with appropriate escalation.
How to submit a VMSS removal request to Square
The process is:
- Confirm that Square was the acquirer that terminated your account and submitted the VMSS listing.
- Identify the VMSS reason code — if Square's communication was not specific, review your transaction and dispute history to identify the likely basis.
- Prepare a structured removal request covering root cause, corrective actions, and evidence in clear, plain language appropriate for Square's SMB-oriented review process.
- Submit the request through Square's merchant support, explicitly escalating to their risk team and referencing the VMSS listing.
- Follow up consistently — Square's support volume can mean initial requests need re-escalation.
We help you build and submit that request. Our questionnaire gathers the specific facts of your case and we draft a tailored letter suited to Square's review process. Start your removal request.
Frequently asked questions
- Can Square remove me from the VMSS list?
- Yes — if Square submitted the listing, only Square can request removal from Visa. Visa does not remove VMSS listings on direct merchant request.
- Why did Square's algorithm terminate my account?
- Square uses automated risk models that flag accounts when performance metrics cross defined thresholds. The initial decision is algorithmic, but removal requests are reviewed by a human risk team and must address the specific underlying cause.
- How long does Square take to review?
- Timelines vary depending on escalation path and case complexity. A specific, well-structured request submitted through the correct channel is more likely to receive a prompt and substantive review.