Payment guides · Disputes

Stop chargebacks before they start: the prevention playbook.

Won disputes still count against your VAMP ratio. Here is the prevention system — ranked by cost per prevented dispute — for staying under the 2026 thresholds.

A small business owner reviewing order paperwork beside a payment terminal
Preventing chargebacks starts with documentation: clean descriptors, policies, and receipts beat fighting disputes.

Most chargeback advice is really representment advice: how to fight a dispute after it lands. That fight matters, but it misses the 2026 reality — under Visa's VAMP program, a won dispute still counts toward your monitoring ratio. Prevention is the only move that keeps the ratio itself down. This playbook builds prevention in three layers, cheapest and highest-impact first.

Why prevention beats representment in 2026

The math shifted twice. First, Visa's Acquirer Monitoring Program tightened: merchants exceeding a 2.2% VAMP ratio faced monitoring from June 2025, and the threshold drops to 1.5% in April 2026. Second, merchants win only 20–30% of the disputes they fight, and the $20–$50 dispute fee is typically not returned even when you win.

Meanwhile, up to 75% of chargebacks come from friendly fraud — legitimate customers disputing valid charges because they forgot a subscription or didn't recognize the descriptor. You cannot representment your way out of a ratio problem built on friendly fraud. You prevent it.

The three layers, in the order to build them

Layer 1 — operational fixes (free, fastest). Clear billing descriptors that match your storefront name. Published refund and cancellation policies, acknowledged before purchase. Fast refunds when a legitimate issue is confirmed — every confirmed refund is a dispute that never happens. Proactive shipping communication and tracking. These cost nothing and move the needle fastest.

Layer 2 — technical controls (cheap, targeted). AVS and CVV on every card-not-present order. 3D Secure where it fits — it shifts liability and directly improves the metrics the networks measure. Velocity rules and card-testing detection to stop enumeration attacks before they generate hundreds of small authorizations. Device and IP signals on risky orders.

Layer 3 — monitoring and interception (the ongoing system). Chargeback alerts (Ethoca/Verifi) that flag disputes early enough to refund before a formal chargeback posts. Rapid Dispute Resolution (RDR) to auto-resolve qualifying disputes. A weekly KPI review: dispute ratio, alert volume, and refund-before-dispute rate.

Prevention tools compared: what each stops and what it costs

ToolWhat it stopsTypical cost signalBest for
Ethoca / Verifi alertsDisputes intercepted pre-chargeback via refundPer-alert fee, provider-quotedMerchants with any card-not-present volume
Visa Rapid Dispute Resolution (RDR)Qualifying disputes auto-resolved before chargebackEnrolled via processor; low per-dispute costSubscription and digital-goods merchants
Compelling Evidence 3.0 captureVisa 10.4 fraud disputes — liability shifts to issuer when criteria metFree if built into checkout data captureEvery online merchant (the highest-ROI layer)
3D SecureFraud disputes via liability shiftUsually bundled by gatewayHigh-risk or cross-border checkout
Stripe Radar for Fraud TeamsScored screening per transaction$0.02 per screened transaction (checked 2026-10-11)Stripe merchants wanting per-order screening

The standout is CE 3.0 evidence capture: full CE 3.0 evidence overturns 40–60% of eligible disputes, versus 15–20% with receipts alone — and capturing it costs nothing beyond building it into checkout.

Hands organizing file folders and receipts beside a laptop
Build the evidence file at checkout: tracking numbers, IP data, and timestamps decide disputes.

The 7-step evidence-capture procedure

  1. Fix the billing descriptor first. It must read as your storefront name, not a holding company. Mismatched descriptors are the top self-inflicted cause of “I don't recognize this charge” disputes.
  2. Capture AVS + CVV on every online order and store the match results with the order record — this is the core of the fraud-reason-code evidence set.
  3. Log device and IP signals (device fingerprint, IP geolocation, email/phone match) alongside billing data. Two or more prior undisputed transactions with matching data points is what qualifies for CE 3.0.
  4. Publish refund and cancellation policies before purchase and require acknowledgment at checkout — the policy doubles as representment evidence later.
  5. Send order, shipping, and delivery confirmations with tracking, and keep the customer's replies. Delivery proof plus the customer's own words wins “not as described” cases.
  6. Enroll in alerts and RDR through your processor so incoming disputes can be refunded before they post as chargebacks.
  7. Respond to any dispute within 48 hours. Late responses forfeit automatically on most networks — speed is part of the evidence.

What success looks like: every order record carries descriptor, AVS/CVV results, device/IP signals, policy acknowledgment, and delivery tracking in one place; your weekly review shows dispute ratio trending down and refunds-before-dispute trending up; no dispute ages past 48 hours without a response.

The prevention ROI

The setup: one lost $100 dispute costs roughly $132.50 all-in — the sale, the ~$20 CAD dispute fee, and ~30 minutes of representment labour. Practitioner data puts the true cost multiplier at 4.61x per dollar disputed.

The prevention spend: Layer 1 is free. CE 3.0-grade checkout capture is free to build. Per-transaction screening at $0.02 adds about $20/month at 1,000 transactions.

The verdict: preventing one $100 dispute every few months pays for the entire prevention stack. Prevention is the cheapest line item in the dispute budget — representment is the most expensive.

Merchant experience backs the systems view. A widely shared practitioner playbook notes that disputes must be matched to their reason code — delivery proof for “not as described,” IP and device data for fraud — and that having the evidence kit ready before the dispute email arrives is the whole game. Small-store buyers on G2 land on the same shortlist — Sift for AI scoring, SEON for pay-as-you-go device fingerprinting, Riskified and Signifyd where a chargeback guarantee is wanted — the scoring-vs-liability-shift split this playbook is built on.

FAQ

What is Visa's VAMP threshold in 2026?
From June 2025, merchants exceeding a 2.2% VAMP ratio face monitoring and fines; the threshold tightens to 1.5% in April 2026. Won disputes still count toward the ratio — which is why prevention outranks representment.

What is Compelling Evidence 3.0?
Visa's framework for 10.4 (fraud) disputes: show two or more prior undisputed transactions with matching data points (device, IP, shipping address), and liability shifts to the issuer. Capturing that data at checkout is the highest-ROI prevention step.

Should I refund a customer who threatens a chargeback?
Usually yes, if the complaint is legitimate. A refund costs you the sale; a chargeback costs the sale plus the fee plus the ratio hit.