Visa’s 2026 Chargeback Threshold (VAMP): What It Means for Your Account

Which number applies to my region?

Visa’s published excessive-merchant table, applicable when the acquirer is neither Above Standard nor Excessive, specifies: AP, Canada, EU and US — at least 1.5% and 1,500 monthly fraud/dispute counts, effective 1 April 2026; LAC — at least 1.5% and 1,500; CEMEA — at least 2.2%, 150 counts and USD 75,000. The fact sheet flags separate announcements for Brazil, Chile and India; obtain current local confirmation.

Ask your acquirer to identify the relevant region and treatment in writing. Your customer’s location, incorporation country and settlement currency are different facts; do not choose a threshold merely because one seems familiar. For example, an offshore business selling to American customers should provide its actual processing structure rather than decide that the US column automatically governs every arrangement.

Why does my chargeback dashboard show something different?

The published count-based VAMP formula is TC40 fraud plus TC15 disputes divided by TC05 settled transactions for card-not-present VisaNet activity. Visa describes exclusions for qualifying pre-dispute resolutions and Compelling Evidence 3.0 fraud, subject to extraction timing. The processor’s operational report must explain how these affect the measured period.

Build a reconciliation with separate columns for the reported numerator, denominator, period and source. An internal report might group cases by order date, while a provider report follows another event date. Another dashboard might combine several card brands. Neither comparison is meaningful until its scope is aligned. Ask the provider to explain whether apparently repeated transaction references represent duplicate imports or separate reportable events; do not delete entries simply to make a ratio match.

For a hypothetical operational check, suppose your internal dashboard shows 900 cases while the provider reports 1,200 counted events. Investigate the 300-event difference by event category and timing. Document the explanation so the next employee can reproduce it without rebuilding the investigation from memory.

Can you show me the calculation?

Consider an illustrative reporting month with 100,000 qualifying settled transactions and a provider-confirmed combined count of 1,500. Dividing 1,500 by 100,000 gives 0.015, or 1.5%. That is arithmetic, not an official determination that a particular merchant has entered monitoring: the applicable conditions and treatment still need confirmation.

Now hold the count constant and reduce the denominator to 80,000. The result becomes 1.875%, even though the number of reported events did not increase. A seasonal decline in genuine sales can therefore make a deteriorating position more visible. Keep both counts in the management report instead of discussing only the percentage.

Do not generate artificial transactions, obscure merchant identities or move problematic activity through an undisclosed account to manipulate the denominator. Such actions create additional underwriting and integrity problems. The useful response is to identify why customers dispute transactions and why fraud is getting through, then change the process producing those outcomes.

Can my processor act before I reach the threshold?

Yes. The merchant agreement and the provider’s assessment of the business matter independently of a public network table. Visa’s Core Rules also permit requirements to deploy remediation tools for unusual activity and contemplate assessment at aggregated or sponsored-merchant level. A merchant should not interpret a network identification criterion as a contractual entitlement to continue processing.

Ask for three separate answers: what the network measurement shows, what your contract permits, and what the provider requires now. A request to improve delivery evidence may be operational; a reserve change affects liquidity; a volume restriction affects sales planning. Treating them all as one vague compliance issue makes it harder to negotiate a workable response.

For example, if a provider requests daily fulfilment reporting for a troubled product line, propose a specific report owner, data source and review meeting. Do not promise an overnight improvement in a monthly measure. Demonstrate actions you can control and clearly label the outcomes that will take time to observe.

What should I fix first?

Start with a small set of concrete causes rather than a broad instruction to reduce chargebacks. Separate unrecognized billing, delivery failures, cancellation problems, product complaints and suspected stolen-card activity in your internal case review. Assign an operational owner to each recurring pattern and record what evidence supports the classification.

A hypothetical subscription business discovers that 40 recent complaints concern renewals after customers thought they had cancelled. The immediate investigation should examine the cancellation journey, confirmation messages and billing scheduler. Buying another fraud tool does not repair a cancellation state that never reaches the renewal system.

Review card-testing activity separately with your provider and technical team; a surge of small authorization attempts is not the same operating problem as dissatisfied customers. Choose controls with the acquirer’s guidance, test legitimate customer impact and monitor false positives. Maintain one change log so a sudden conversion drop can be traced to the control actually introduced.

What should I do today?

• 1. Save the warning, agreement and latest provider reports in one controlled case folder. Record the response deadline stated in the notice; if none is given, request one instead of inventing a grace period.
• 2. Ask the provider for its calculation, reporting period, regional treatment and current requirements. Request a named escalation contact and written confirmation of any restrictions.
• 3. Review a sample of 20 recent cases, if available, and identify the most common operational causes. Use the sample to design a fuller review, not to claim statistically proven conclusions.
• 4. Assign owners for customer remedies, fraud controls and cash forecasting. Reconcile pending refunds before issuing additional credits, and communicate honestly with customers whose orders remain unresolved.
• 5. Send a concise remediation plan with actions, responsible people and evidence dates. Set a follow-up meeting and retain each version of the plan so progress can be compared against what was actually promised.

What else do merchants ask about VAMP?

Is 1.5% a universal chargeback limit? No. Read the regional conditions above and obtain the applicable provider calculation; the phrase chargeback limit is an incomplete description of this metric.

Will winning one dispute fix my number immediately? Do not assume that a case outcome instantly changes a monitoring report. Ask when and how the provider recognizes relevant adjustments.

Does using 3DS mean I cannot receive a warning? No control is a substitute for reviewing the actual warning, transaction pattern and applicable contractual requirements. Assess authentication alongside fulfilment and customer-service issues.

Should I refund every disputed transaction today? First check case status with the provider to avoid a refund and dispute adjustment resolving the same payment twice. Give the customer a clear explanation of the appropriate route.

Can another processor promise I will never enter monitoring? Treat that promise as a reason to investigate further. Request the proposed account’s conditions and reporting responsibilities rather than relying on an absolute assurance.