Skip to main content
Commerce Security Authority
Category: Chargebacks and Disputes

Visa Dispute Monitoring Program

Also known as: VDMP, Visa Dispute Monitoring Program (VDMP)
Simply put

The Visa Dispute Monitoring Program (VDMP) is a framework Visa uses to track the rate of disputes and chargebacks tied to each of its merchants. Merchants who exceed Visa's chargeback thresholds may be placed into the program and face additional scrutiny or requirements. According to the evidence, VDMP is being replaced by the broader Visa Acquirer Monitoring Program (VAMP), which consolidates dispute and fraud monitoring.

Formal definition

VDMP is a Visa network monitoring program that measures merchant-level dispute (chargeback) activity against thresholds defined by Visa, identifying merchants whose chargeback ratios exceed those limits. It is distinct from the Visa Fraud Monitoring Program (VFMP), which addresses fraud activity rather than disputes. Per the cited evidence, VDMP and VFMP are being consolidated into and replaced by the Visa Acquirer Monitoring Program (VAMP). Specific threshold values, timing, and enforcement actions are governed by Visa's own program rules, which vary by region and change over time; practitioners should confirm current criteria against Visa's published program documentation rather than relying on fixed figures.

Why it matters

Chargeback ratios are a core health metric that Visa uses to identify merchants whose dispute activity exceeds acceptable levels. The Visa Dispute Monitoring Program (VDMP) exists to flag merchants whose chargeback ratios cross Visa's defined thresholds, which can trigger additional scrutiny, remediation requirements, or enforcement actions imposed through the merchant's acquirer. For merchants and acquirers, understanding where a portfolio stands against these thresholds is important because exceeding them can carry commercial and operational consequences that vary by region and change over time.

VDMP is specifically a dispute (chargeback) monitoring program and should not be conflated with the Visa Fraud Monitoring Program (VFMP), which addresses fraud activity rather than disputes. The two measure different signals: high disputes may reflect friendly or first-party fraud, unclear billing descriptors, or service issues, whereas fraud metrics reflect confirmed fraudulent transactions. Treating a dispute problem as a fraud problem, or vice versa, can lead teams to apply the wrong controls.

According to the cited evidence, VDMP and VFMP are being consolidated into and replaced by the broader Visa Acquirer Monitoring Program (VAMP), described by the Merchant Risk Council as a significant reinvention of the existing fraud and dispute monitoring programs with potentially serious implications. Practitioners tracking VDMP should therefore also monitor the transition to VAMP, because thresholds, measurement methods, and enforcement may differ under the consolidated program. Exact threshold values, timing, and effective dates are governed by Visa's own published program rules and should be confirmed against current Visa documentation rather than assumed.

Who it's relevant to

Merchants and Merchant Risk Teams
Merchants whose chargeback ratios approach or exceed Visa's thresholds are the primary subjects of VDMP. Risk teams need to track dispute ratios against program limits, understand potential remediation requirements, and distinguish dispute drivers such as friendly or first-party fraud from confirmed fraud that would fall under a separate program. With VDMP being replaced by VAMP, these teams should prepare for consolidated dispute and fraud monitoring.
Acquirers and Payment Processors
Because Visa administers monitoring program consequences through the acquiring side, acquirers and processors are responsible for identifying flagged merchants in their portfolios and managing remediation. The transition from VDMP and VFMP to the Visa Acquirer Monitoring Program, which by its name centers on the acquirer, is directly relevant to how these organizations assess and manage portfolio risk.
Chargeback and Dispute Analysts
Analysts managing chargeback workflows rely on precise program definitions to interpret ratio trends and prioritize remediation. They must keep the dispute-focused VDMP separate from the fraud-focused VFMP and confirm current thresholds against Visa's published rules, since these change over time and are being reshaped under VAMP.
Compliance and Payments Program Managers
Teams responsible for card brand compliance need to track program transitions, such as the consolidation of VDMP and VFMP into VAMP, and assess the operational and commercial implications. Industry bodies such as the Merchant Risk Council have flagged the VAMP transition as a significant change warranting impact assessment.

Inside VDMP

Dispute (Chargeback) Monitoring
VDMP is a Visa program that tracks the volume and ratio of disputes (chargebacks) attributed to a merchant, measured against the merchant's transaction activity over a defined monitoring period. The exact thresholds, timeframes, and program tiers are defined by Visa's published rules and are subject to change and regional variation; practitioners should confirm current values against Visa's operating regulations rather than relying on fixed figures.
Program Tiers or Levels
The program typically distinguishes merchants that exceed monitoring thresholds into escalating categories (for example, standard and excessive designations). Placement in a tier can trigger remediation expectations, monitoring, and potential financial assessments. The precise names, thresholds, and consequences are governed by Visa's rules and may differ by region and over time.
Dispute Ratio Metric
A core measurement is the ratio of disputes to transactions (and, in some cases, an absolute dispute count) that determines whether a merchant is identified under the program. Because the numerator, denominator, and qualifying period are defined by Visa, the calculation should be validated against Visa's current documentation and not assumed.
Relationship to Fraud Monitoring
VDMP addresses disputes/chargebacks, which is distinct from fraud-specific monitoring programs that track reported fraud. A single transaction can contribute to fraud metrics, dispute metrics, or both depending on how it is reported, so the two monitoring mechanisms should not be conflated.
Remediation and Assessment Framework
Merchants identified under the program are generally expected to implement corrective action to reduce disputes, and may be subject to fees or assessments while in the program. The specific remediation obligations and any charges are set by Visa's network rules and administered through the merchant's acquirer.
Acquirer Involvement
Because merchants do not connect directly to the network, the acquirer (and any payment processor) is typically the party notified of program identification and is responsible for communicating requirements and supporting remediation. Roles and responsibilities follow the acquirer-merchant agreement and Visa's rules.

Common questions

Answers to the questions practitioners most commonly ask about VDMP.

Is the VDMP part of PCI DSS or a PCI standard I need to validate against?
No. The Visa Dispute Monitoring Program is a card brand program governed by Visa's own network rules, not a PCI Security Standards Council standard such as PCI DSS, PA-DSS, the PCI Software Security Framework, PCI PIN, PCI P2PE, or PCI 3DS. PCI DSS addresses the protection of cardholder data and the security of the cardholder data environment, while the VDMP addresses dispute (chargeback) volume and ratios for merchants operating under Visa's rules. Meeting PCI DSS requirements does not exempt a merchant from VDMP thresholds, and being within VDMP thresholds says nothing about PCI DSS compliance. Confirm program specifics against Visa's current published rules, as these are set and revised by the network rather than by the PCI SSC.
Does being enrolled in or breaching the VDMP mean the same thing as a fraud monitoring program?
Not exactly. The VDMP focuses on disputes, which are commonly referred to as chargebacks, and their ratios relative to transaction volume. Visa also operates separate monitoring focused on fraud activity. Disputes and fraud are related but distinct: a dispute may arise from many causes, including friendly or first-party fraud, chargeback fraud, service or product complaints, or genuine unauthorized use, while fraud monitoring is oriented toward reported fraudulent transactions. A merchant can face attention under one program without breaching the other. Treating dispute ratios and fraud ratios as interchangeable can lead to the wrong remediation. Consult Visa's current rules to see which program and which metric applies to a given situation, as thresholds and definitions may change and can vary by region.
What metric determines whether a merchant is identified under the VDMP?
The program is generally driven by a merchant's dispute count and dispute-to-transaction ratio measured over a defined period. Because the specific thresholds, calculation windows, and any distinction between standard and excessive tiers are set by Visa and may change over time and vary by region, you should confirm the exact figures and definitions against Visa's current published rules rather than relying on a fixed number. Track your own dispute count and ratio internally so you can compare against the current thresholds Visa publishes.
What practical steps can help reduce dispute ratios before they approach program thresholds?
Approaches that may help reduce disputes include clarifying billing descriptors so cardholders recognize the charge, improving refund and cancellation handling, providing responsive customer service to resolve issues before they become disputes, and retaining transaction evidence to support representment where appropriate. For card-not-present transactions, authentication approaches such as 3-D Secure and layered fraud screening may reduce certain unauthorized-use disputes, though they address different risks and none eliminates disputes entirely; each involves false-positive and false-negative trade-offs. The right mix depends on your dispute drivers, so analyze dispute reason categories before selecting controls.
How should a merchant respond after being notified of identification under the program?
Common practice is to acknowledge the notification through your acquirer, since acquirers typically administer the relationship and communicate program status, and then diagnose the underlying dispute drivers by reason category. From there, implement targeted remediation, document the actions taken, and monitor whether your dispute count and ratio move back within current thresholds over the relevant measurement window. Because timelines, remediation expectations, and any associated fees or consequences are defined by Visa's rules and administered through your acquirer, confirm the specific requirements and deadlines with your acquirer and against Visa's current published program terms.
Who owns responsibility for monitoring and remediation, the merchant, the acquirer, or a service provider?
The merchant is ultimately accountable for its dispute activity, but the acquirer generally serves as the point of contact for program notifications and may set expectations or requirements on the merchant. Third-party service providers, such as gateways, fraud tools, or chargeback management vendors, may support monitoring and representment, but using them does not transfer accountability for outcomes. Clarify roles in your contracts and confirm reporting responsibilities with your acquirer, since program administration and any escalation are governed by Visa's rules and may vary by region.

Common misconceptions

VDMP is a fraud monitoring program.
VDMP focuses on disputes (chargebacks), which are distinct from reported fraud. Fraud is tracked under separate monitoring mechanisms, and a merchant can be affected by dispute metrics, fraud metrics, or both. The two should not be treated as the same measurement.
The dispute thresholds and consequences are fixed values that stay the same everywhere.
The thresholds, monitoring periods, tier names, and any assessments are defined by Visa's network rules, which change over time and can vary by region. Practitioners should confirm the current values against Visa's published operating regulations rather than assuming a specific number.
VDMP is a PCI DSS or compliance-validation requirement.
VDMP is a Visa card brand/network program governing dispute activity and is separate from PCI DSS and related PCI standards. Meeting PCI DSS obligations does not by itself address dispute-ratio monitoring, and vice versa.

Best practices

Monitor your own dispute-to-transaction ratio continuously against Visa's currently published thresholds, and confirm the exact metric definition and monitoring period with your acquirer rather than relying on assumed figures.
Maintain clear communication with your acquirer or processor, since they are typically the party notified of program identification and are responsible for relaying requirements and supporting remediation.
Track dispute metrics separately from fraud metrics so that program identification is diagnosed correctly, and address root causes specific to disputes such as unclear billing descriptors, unrecognized recurring charges, or fulfillment issues.
Combine authentication and detection controls (for example, 3-D Secure and fraud screening) where appropriate to help reduce disputes, while recognizing these tools have false-positive and false-negative trade-offs and do not eliminate disputes on their own.
Document a remediation plan and evidence of corrective action if identified under the program, aligning it with the specific obligations set out in Visa's rules and your acquirer agreement.
Periodically re-verify program thresholds, tier definitions, and any assessment terms against Visa's current operating regulations, since these are subject to change and regional variation.