There is no single chargeback percentage that makes every merchant account safe. Visa VAMP, Mastercard monitoring, and your provider’s account controls can measure different events and periods. Keep the program name, transaction population, numerator, denominator, and reporting date beside every ratio you use.
Your first task is to reproduce the acquirer’s report. A dashboard percentage without its definition can hide the cause of a change or give false reassurance. This guide explains the main distinctions and a practical review process for businesses that need more stable processing.
Visa VAMP includes fraud reports and disputes
Visa’s public fact sheet defines VAMP using reported fraud and disputes divided by settled transactions for the applicable card-not-present VisaNet activity. This is not simply all chargebacks divided by all sales. Certain pre-dispute resolutions and fraud qualifying for Compelling Evidence 3.0 can be excluded, depending on data-extract timing.
For the United States, Canada, Europe, and Asia-Pacific, the fact sheet lowers the excessive-merchant ratio to at least 150 basis points, or 1.5%, from April 1, 2026, alongside a monthly minimum of 1,500 fraud-and-dispute events. The merchant table is expressly conditioned on the acquirer not already being Above Standard or Excessive. Regions and portfolio-level requirements differ.
Confirm the current treatment with your acquirer, including exclusions and its own intervention levels. Being below one published merchant threshold is not permission to ignore fraud, customer complaints, or a provider’s tighter account controls.
Mastercard uses a different reporting period
Mastercard’s August 4, 2026 rules describe ECP basis points using current-month chargebacks and the preceding month’s Mastercard transactions, multiplied by 10,000. They refer detailed categories and thresholds to separate program materials. Ask your acquirer for the current requirements it applies.
For illustration, 30 disputes divided by 10,000 transactions equals 0.3%, or 30 basis points. Dividing the same 30 disputes by 5,000 transactions gives 0.6%, or 60 basis points. These are arithmetic examples, not network thresholds. A changed denominator can move the result even when the dispute count stays constant.
Build a report you can explain
- Separate card networks and merchant accounts rather than blending every payment into one percentage.
- Record event counts and sales counts with the exact reporting periods used by the provider.
- Track fraud reports, disputes, refunds, alerts, and final case decisions as separate events.
- Group complaints by product, subscription offer, fulfillment issue, sales channel, and reason.
- Mark incomplete periods and pending decisions so a weekly snapshot is not mistaken for a final result.
Choose an owner for each recurring issue. A useful review ends with a dated action, such as correcting an unclear renewal screen or investigating orders from a particular campaign. Recheck the same measure after the change instead of assuming the new tool or policy worked.
Prevent the problem before it becomes a dispute
Visa’s merchant guidance emphasizes clear transaction handling and customer communication, including avoiding duplicate processing and helping customers recognize their purchases. Review what customers actually see: the product promise, delivery estimate, checkout disclosure, receipt, statement descriptor, refund path, and cancellation process.
- Use a descriptor customers can connect to the purchase and give them a reachable support channel.
- Make delivery promises that your fulfillment process can meet; investigate missed promises.
- Show recurring billing terms clearly and retain the customer’s consent record.
- Make cancellation and refund requests easy to find and track them to completion.
- Apply fraud controls appropriate to the transaction and review legitimate orders rejected by those controls.
Authentication and alerts have specific limits
Visa describes fraud-dispute liability protection for eligible properly authenticated or attempted-authentication transactions. Confirm the applicable conditions and returned authentication data with your provider. Do not treat enabling 3-D Secure as protection against every dispute, including complaints about delivery or product quality.
Before paying for a dispute-alert service, request a written explanation of its coverage, chargeable events, response window, refund handling, and reporting effects. Measure matched alerts, actions completed in time, resulting disputes, and total cost in your own account. A quoted deflection percentage is not your measured result.
Choose the right response to an open case
Read the reason and deadline in the provider’s case record. Match evidence to the customer’s actual claim: authorization information, delivery records, terms accepted, cancellation history, or refund records. Ask the provider how to handle a refund once a dispute is open so your team does not create a duplicate reimbursement.
Measure both operational and financial outcomes. Stripe’s dispute analytics, for example, distinguishes overall and challenged win rates and explains how pending decisions affect reporting. Use the definitions in your own system. Submitting evidence, winning a dispute, recovering money, and improving a monitoring metric are different outcomes.
Review your processing options with Cybin
Bring recent statements, the provider’s monitoring notice, and a summary of the underlying complaints to Cybin. We can help organize the processing discussion and compare available provider requirements. Approval, reserves, service availability, and account terms depend on underwriting; a new account does not resolve the causes of the old account’s disputes.