VMSS removal / PayPal
VMSS removal through PayPal
If PayPal terminated your merchant account and added you to the Visa Merchant Screening Service (VMSS), PayPal is the only party that can submit a removal request to Visa. This guide explains the distinction between PayPal's internal dispute systems and a VMSS listing, what their merchant risk team looks for, and how to approach the process.
Why PayPal adds merchants to the VMSS list
PayPal operates as a Visa acquirer for many of its merchant accounts. A VMSS listing through PayPal is distinct from PayPal's own buyer protection dispute process — it is a report submitted to Visa's network-level risk database. Common reasons PayPal submits VMSS listings include:
- Excessive disputes — dispute rates crossing Visa's programme thresholds, which at PayPal can accumulate quickly given PayPal's dispute-friendly buyer policies (VMSS code 22).
- Excessive fraud — fraud levels reported through Visa's fraud monitoring programmes (VMSS code 21).
- Transaction laundering — processing payments for undisclosed businesses or third parties through a PayPal account (VMSS code 23).
- Violation of agreement — breaches of PayPal's acceptable use policy or Visa's operating rules (VMSS code 30).
It is important to understand that the dispute rates which drive a VMSS listing at PayPal are separate from PayPal's own internal dispute resolution system. For full definitions, see our VMSS reason codes page.
What PayPal's risk team looks for
PayPal's merchant risk team reviews VMSS removal requests separately from general merchant support. To advance a removal request, your submission needs to clearly address each of the following:
- Root cause — a specific, honest account of what drove the metrics that led to the VMSS listing. Dispute rates at PayPal often reflect product or fulfilment issues — be direct about the origin.
- Corrective actions — what you changed operationally, technically, or in your product offering since the termination. Vague commitments to improve are not sufficient.
- Evidence — supporting documents showing the changes implemented: updated return policies, fulfilment process changes, revised product descriptions, lower dispute metrics, or similar.
- No recurrence — a credible explanation of the structural changes that prevent the root cause from recurring.
Only PayPal, as the acquirer that listed you, can submit a removal request to Visa. The request must be directed to PayPal's merchant risk team, not general customer support.
How to submit a VMSS removal request to PayPal
The process is:
- Confirm that PayPal was the acquiring entity that submitted the VMSS listing — not another PSP you may also have used.
- Identify the VMSS reason code from your account termination notice or PayPal's account closure communications.
- Prepare a structured removal request addressing root cause, corrective actions, and evidence specific to your situation.
- Contact PayPal's merchant risk team directly — this requires escalation beyond standard PayPal support to their risk or compliance department.
- Follow up consistently if you do not receive a substantive response; PayPal handles high volumes of merchant escalations.
We help you build and submit that request. Our questionnaire extracts the specific facts of your situation, and we draft a tailored letter directed to PayPal's merchant risk team. Start your removal request.
Frequently asked questions
- Can PayPal remove me from the VMSS list?
- Yes — if PayPal submitted the VMSS listing, only PayPal can request removal from Visa. Visa does not remove listings on direct merchant request.
- Is a VMSS listing the same as a PayPal dispute?
- No. PayPal's internal buyer protection disputes are separate from a VMSS listing. A VMSS listing is a report to Visa's network-level risk database and affects your ability to obtain merchant accounts elsewhere, not just your PayPal account status.
- How long does PayPal take to review?
- Timelines vary. A well-structured request that directly addresses the VMSS reason code and demonstrates real corrective actions is more likely to be reviewed efficiently than a generic submission.