Chargeback monitoring

What is an excessive chargeback ratio?

An excessive chargeback ratio means a merchant's measured dispute or fraud activity has crossed a threshold used by a card-network, acquirer, processor, payment facilitator, or internal risk program. There is no single percentage that applies to every merchant, transaction type, region, network, or month.

Direct answer

The calculation and threshold must be named together

A report may divide chargebacks by settled sales, transactions, or another program-specific denominator. It may use disputes received during one month while comparing them with transactions from the same or a different period. Some programs also combine fraud reports and disputes or require a minimum event count. A percentage without the formula, network, region, and measurement period is incomplete.

A useful question is not only “What is our ratio?” Ask which program calculated it, which events are included, which transactions form the denominator, which month is measured, and whether count and volume gates also apply.

Current Visa example

VAMP illustrates why a universal chargeback rule is misleading

Visa's public VAMP fact sheet describes a count-based ratio for qualifying card-not-present VisaNet activity that combines reported fraud and disputes, subject to stated exclusions. The same fact sheet says the Excessive Merchant threshold for the United States, Canada, Europe, and Asia Pacific was reduced to 150 basis points on April 1, 2026, with a minimum monthly count of 1,500 fraud and dispute events. Those details describe that Visa program; they should not be copied onto Mastercard activity, card-present reporting, a processor's internal risk policy, or another region.

Basis points

One hundred basis points equals one percentage point. Therefore, 150 basis points equals 1.50%, but only within the formula and scope attached to that threshold.

Illustrative arithmetic

If a report shows 15 counted events over 1,000 measured transactions, the simple arithmetic is 1.50%. That example does not establish program identification because exclusions, timing, scope, and minimum counts still matter.

Merchant review

Reconcile the source data before reacting

Confirm the numerator

Identify the exact disputes, fraud reports, alerts, or other events counted. Check duplicates, reversals, exclusions, and the date assigned to each item.

Confirm the denominator

Determine whether the report uses settled transactions, sales count, transaction amount, or another base and whether the periods align.

Confirm the authority

Ask the acquirer or processor to name the applicable network program, region, effective date, identification level, and remediation requirement.

Response plan

Focus on root causes and documented remediation

  • Segment disputes by reason, product, channel, fulfillment method, location, and customer-recognition issue.
  • Review billing descriptors, cancellation and refund handling, delivery evidence, customer support, authentication, and fraud controls.
  • Track both gross activity and outcomes without assuming a successfully challenged dispute disappears from every program metric.
  • Request the provider's written action plan, reporting cadence, deadlines, and escalation contact.

Common questions

Chargeback ratio FAQ

Is one percent always excessive?

No. The applicable threshold depends on the program, formula, region, period, transaction scope, and minimum counts.

Does winning a dispute remove it from the ratio?

Not necessarily. Programs can count events differently. Confirm the current program rules and the provider's report rather than assuming the outcome changes the metric.

Who can confirm the applicable threshold?

The merchant's acquirer, processor, or payment facilitator should identify the governing program and provide current reporting and remediation details.

How often should ratios be reviewed?

Review them at least as often as provider reporting and more frequently when activity changes, warnings appear, or a remediation plan requires it.

Last editorial review: August 13, 2026. Monitoring programs can change; verify current thresholds and calculations with the responsible acquirer or processor.

Next step

Ask for the formula behind the warning

Reconcile counted events and measured transactions, identify the governing program, and build a documented root-cause response.

Contact Payments Max

To learn more about how TSYS can help improve the way your organization accepts payments, markets to new customers, or manages its HR responsibilities, get in touch by calling 585-981-8463 to get started.

CONTACT US