Skip to main content
Metrics type: Key Metrics • Category: Payment Gateway

​
At a glance

Threshold-watch alert that fires when 30D rolling chargeback rate crosses 0.9%. 90% of the Visa Dispute Monitoring Program (VDMP) enrolment ceiling at 1.0%. The Nerve Centre’s “regulatory clock is starting” alert: by the time this fires, the merchant has 30-90 days of clean runway to identify cause and remediate before VDMP enrolment becomes likely. Slowest-moving but highest-stakes alert in the CyberSource set.

​
Calculation

Calculated automatically from your CyberSource data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.

​
Worked example

A US-based digital subscription merchant. The merchant has been gradually shipping product changes that affected billing-descriptor clarity over Q1; the dispute rate has been creeping up. On 12 Apr 26 the alert fires for the first time. State at fire time: The merchant’s payments + compliance leads receive the alert. The remediation playbook activates: Five things worth noticing for an enterprise compliance lead:
  1. The alert is the start of a 30-90 day regulatory clock. From the moment the 30D rate crosses 0.9%, the merchant has roughly 30-90 days before VDMP enrolment becomes likely (depending on whether the rate is climbing fast or stabilising). This is the merchant’s last clean off-ramp; once VDMP starts, exit takes 6-9 months minimum and costs 250k−250k-500k+.
  2. Drilling into Chargeback Reason Codes is the first action. For this merchant, the top reason is Visa 4863 (“doesn’t recognise”), 38% of disputes, points to a billing-descriptor problem. The fix is mechanical: refresh the descriptor (clear brand name, support phone, format BRAND.COM 800-555-0100), email all active subscribers showing the new descriptor, and watch the 4863 share over the next 30-60 days.
  3. The 90D rate at 0.83% lags but is still rising. The 90D is what Visa actually uses for VDMP enrolment decisions. With 30D at 0.91%, the 90D will cross 0.9% within ~30 days if the 30D doesn’t drop. The compliance team has roughly that long to ship remediation that drops the 30D before the 90D crosses.
  4. CyberSource account-management gets involved automatically. When the alert fires, the merchant’s CS account-manager is typically copied (depending on contract terms) and may schedule a review call to discuss remediation plans. CS has a strong incentive to help: if Visa enrols the merchant in VDMP, CS as the gateway carries some reputational and operational impact.
  5. The remediation playbook should target dropping the 30D rate by 0.15pp within 60 days. That brings 30D to ~0.76% and ensures 90D never crosses 0.9%. Specific tactics for this merchant: (a) Visa 4863 reason-code-targeted fixes (descriptor refresh) → expected 30-60% reduction in 4863 share; (b) Decision Manager rule tightening on the highest-fraud-risk customer cohorts → expected 5-10% reduction in 4853 disputes; (c) faster customer-service response on cancellation requests → expected 10-15% reduction in 4855 disputes (customer-can’t-cancel-so-disputes pattern is common in subscription).
If the merchant successfully ships these fixes and the 30D drops to 0.76% within 60 days, the alert auto-resolves at 0.85% (after sustained drop for 7 days). The 90D follows ~30 days behind. Total avoided cost: VDMP enrolment fees (250k−250k-500k over 12 months) plus avoided merchant-account-termination risk plus preserved processing-volume growth flexibility.

​
Sibling cards merchants should reference together

​
Reconciling against the vendor’s own dashboard

Where to look in CyberSource Business Center (EBC2): CyberSource’s own account-management team monitors merchants approaching VDMP thresholds and reaches out 30-60 days in advance; this Vortex IQ alert is typically the merchant’s earlier internal signal. EBC2 views during an active alert: Why our alert may legitimately fire when EBC2 looks fine (or vice versa): Cross-connector reconciliation:

​
Known limitations / merchant FAQs

The alert fired. What’s my first 7-day priority? Three actions in parallel: (1) Open Chargeback Reason Codes and identify the top 1-2 reasons driving the rate; ship reason-targeted fixes (descriptor refresh for 4863, fulfilment-flow audit for 4855, fraud-screening tightening for 4853). (2) Schedule a meeting with your CyberSource account-manager to discuss the alert; CS often has insight into similar merchants’ remediation patterns and can fast-track service options like 3DS opt-in or Decision Manager rule reviews. (3) Brief your CFO and / or compliance lead on the 30-90 day regulatory clock; this is a P0 incident, not a P2 monitoring item. My 30D rate just crossed 0.9% but my 90D is still at 0.83%. Am I in VDMP? Not yet, but on the path. Visa typically requires sustained 90D breach (or a single very-high month plus elevated trend) before formally enrolling. With 90D at 0.83% you have roughly 30-45 days before the 90D crosses 0.9%, and another 30-60 days after that before VDMP enrolment becomes likely. This is the runway the alert exists to give you. Will the alert fire on Visa’s metric or my metric? Slight differences. The alert uses our 30D dispute-rate calculation which matches Visa’s regulatory definition (excludes refund-resolved disputes, includes pre-arb). The 90D regulatory-window companion (Chargeback Rate (90D)) is what Visa actually uses for VDMP enrolment decisions. The alert fires on the 30D leading edge to give you runway before the 90D regulatory rate crosses. Can I tune the threshold up if I know I’ll be at 0.9% for a season? Tactically yes (manifest setting), but generally no. The 0.9% is the headroom-before-VDMP threshold; raising it loses your runway. If a known seasonal effect is driving up the rate (e.g. Q4 holiday + return-window-driven Q1 disputes), use the alert’s “scheduled known-elevation” suppression instead, which keeps the alert active for unexpected spikes while masking the known seasonal one. Auto-resolution at 0.85%, why the 5pp hysteresis? To prevent the alert from re-firing on small fluctuations once remediation is underway. A merchant who drops from 0.91% to 0.87% has made progress; we want the alert to stay quiet while they continue work. Re-firing immediately would generate noise and undermine the team’s confidence that fixes are working. Multi-acquirer enterprises, does VDMP apply per-MID or merchant-wide? Per merchant ID. Visa’s VDMP rules apply to a specific MID. A multi-acquirer enterprise might have CS MID at 0.91% and Stripe MID at 0.6%, the CS MID is in alert territory but Stripe is fine. Routing volume away from the in-VDMP MID can buy time but doesn’t fix the underlying dispute pattern (the customers will still dispute regardless of which gateway they routed through). My alert keeps re-firing each month even though I’m under remediation. What’s wrong? Three possibilities: (1) Remediation isn’t actually working, the rate keeps creeping back above 0.9% after a brief drop. Check if the fixes you’ve shipped are truly reducing dispute volume in the relevant reason buckets. (2) New reason buckets are emerging, old fixes worked, but something new is driving disputes. (3) Auto-resolution threshold is too tight, small fluctuations keep crossing 0.85% / 0.9%; loosen the hysteresis manually if needed. Does this alert mean I should pause processing? Almost never. Pausing processing doesn’t reduce disputes (the customers who are disputing will still dispute on the transactions already authorised). The right action is fix the cause, not stop the symptom. If you’re in true crisis (dispute rate >1.5%), the conversation shifts to working with CyberSource and your acquirer to manage the regulatory exposure, not to pausing. My multi-currency global merchant, does the alert apply per-currency? No. VDMP applies per merchant ID globally. A merchant ID processing USD + EUR + GBP that has 0.91% disputes globally fires the alert regardless of which currency the disputes are in. Per-currency views are useful for diagnosing the cause (e.g. EU dispute rate is higher than US) but the alert itself is currency-aggregated. My alert just resolved (auto). Am I safe? For now. Sustained drop to <0.85% for 7 days indicates the trajectory is good. But the alert’s auto-resolve doesn’t mean Visa stopped watching; if the rate creeps back above 0.9%, the alert re-fires. Compliance teams should keep monitoring monthly even after auto-resolution and treat re-firing as a serious signal.

​
Tracked live in Vortex IQ Nerve Centre

Dispute Threshold Watch is one of hundreds of KPI pulses Vortex IQ tracks across CyberSource and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English. Start for free or book a demo to see this metric running on your own data.