Skip to content

Chargebacks explained: reason codes, ratios and the Visa VAMP and Mastercard ECM thresholds

What a chargeback is, how the process and reason codes work, how the ratio is calculated, and the Visa VAMP and Mastercard ECM thresholds as of Nov 2026.

A chargeback is a forced reversal of a card payment that the cardholder starts through their issuer, the bank that issued the card. The merchant loses the sale amount and usually pays a dispute fee. Too many disputes can place the merchant in a card network monitoring program, which adds fines and can end with the card brand refusing to process payments.

This guide explains the process, the reason code families, how the ratio is calculated and the Visa and Mastercard thresholds as of November 2026. BlindPay publishes this guide. It is general education: the networks change thresholds, so check the figures in the table below against Visa's and Mastercard's current documents before you act.

Key takeaways

  • Visa's merchant "Excessive" threshold under VAMP (the Visa Acquirer Monitoring Program) is a ratio of 1.5% or more, with at least 1,500 fraud reports and disputes in a month, in the US, Canada, EU, Asia Pacific and Latin America. It was 2.2% until 1 April 2026.
  • Mastercard's Excessive Chargeback Merchant (ECM) tier starts at 100 chargebacks and 1.5%, and the High tier (HECM) at 300 chargebacks and 3%. A merchant must exceed both the count and the ratio.
  • Cardholders can usually dispute up to 120 days after the payment, and the whole dispute lifecycle can take 2 to 3 months.
  • Refunds do not count toward monitoring ratios, but disputes do, and winning a dispute does not remove it.

What is a chargeback?

A chargeback is a card payment reversal that the cardholder's issuer forces after the cardholder disputes the charge. The disputed amount, and a dispute fee, are debited from the merchant through the acquirer, the bank or provider that processes the merchant's card payments.

It differs from a refund, which the merchant initiates. It also differs from an inquiry, a pre-dispute request for information from the issuer. According to Stripe's documentation, Visa and Mastercard no longer use that pre-dispute phase, while American Express and Discover still do.

Early fraud warnings are a related signal. These are messages from issuers on the Visa, Mastercard and JCB networks that flag a payment as suspected fraud, and the documentation says about 40% of Visa and Mastercard warnings become fraud disputes. They are not disputes themselves, but Visa counts them in its VAMP ratio.

How does the chargeback process work step by step?

The cardholder disputes the payment with the issuer, the issuer files a chargeback through the network, the funds are debited from the merchant, and the merchant either accepts it or submits evidence. The issuer then decides.

The timings below come from Stripe's documentation on how disputes work. They vary by card brand, so confirm them with your own acquirer or processor.

StepTypical deadlineWho acts
1. Cardholder disputes the chargeUsually up to 120 days after the original payment; longer in some situations, for example from the event date for travel or ticketsCardholder and issuer
2. Chargeback opens; disputed amount and fee are debitedAt filingNetwork, acquirer or processor
3. Merchant accepts or responds with evidenceUsually 7 to 21 days, depending on the brandMerchant
4. Issuer reviews the evidence and decidesUsually 60 to 75 days, depending on the brandIssuer
5. OutcomeWhole lifecycle usually 2 to 3 monthsIssuer, then acquirer credits or keeps the debit
6. Pre-arbitration or arbitration, where eligibleDepends on brand and reason codeMerchant and issuer, then the network

If the merchant wins, the issuer returns the amount to the acquirer and then to the merchant. If the merchant loses, no money moves, because the cardholder was already credited when the dispute opened. The dispute fee is generally not returned on a loss, and it depends on your contract.

What are the main reason code families?

Every chargeback carries a reason code from the card network, and the codes fall into four families: fraud, authorization problems, processing errors and consumer disputes. The family tells you what evidence to send. Visa numbers its codes in groups, and Mastercard uses four-digit codes.

FamilyVisa codes (examples)Mastercard codes (examples)What it usually means
Fraud10.1 to 10.5, including 10.4 other fraud, card-absent4837 no cardholder authorizationThe cardholder says they did not make the purchase
Authorization11.2 declined authorization, 11.3 no authorizationnot covered in this guideThe sale was processed without a valid approval
Processing errors12.1 late presentment, 12.5 incorrect amount, 12.6.1 duplicate processing4834 duplicate or incorrect amountThe merchant or acquirer made a data or timing mistake
Consumer disputes13.1 goods or services not received, 13.2 recurring transaction canceled, 13.3 not as described, 13.6 credit not processed4853 not as described or not provided, 4860 credit not processedThe cardholder has a problem with the product or the refund

Code lists come from Stripe's documentation on reason code categories, which groups hundreds of network codes. Rules differ by code, so read the exact reason code on the notice before you gather evidence.

What is a chargeback ratio and how is it calculated?

A chargeback ratio is the number of disputes in a period divided by the number of transactions it is measured against. Each network defines its own formula, so the same merchant can have a different ratio on Visa and on Mastercard.

Visa's VAMP ratio, according to the Visa fact sheet, is the count of fraud reports (TC40) plus disputes (TC15) divided by the count of settled transactions (TC05), on card-not-present transactions, in the same month. A TC40 is a fraud report an issuer files with Visa, and a TC15 is a dispute record. Stripe's documentation adds that a fraudulent transaction that appears in both reports is counted twice.

Mastercard's ratio divides the chargebacks received in the current month by the sales of the prior month, according to the Chase FAQ and Stripe's documentation. Stripe's documentation also notes that Visa divides by payments in the same calendar month and that a dispute is assigned to the month the network receives it, not the month of the original payment.

A worked example makes this concrete. It is illustrative, and every input is stated.

Scenario (illustrative)InputsRatioResult
Visa A, US card-not-present1,100 TC15 + 900 TC40 = 2,000 events; 120,000 settled transactions1.667%Over 1.5% and over 1,500 events: Excessive
Visa B1,000 events; 80,000 settled transactions1.250%Under both: not identified
Mastercard A250 chargebacks this month; 20,000 sales last month1.250%Over 100 chargebacks but under 1.5%: not ECM
Mastercard B150 chargebacks; 8,000 sales last month1.875%Over 100 and over 1.5%: ECM

The ratios were computed as events divided by transactions. The takeaway is that a small merchant can cross the Mastercard threshold with a few hundred disputes, and a larger one needs thousands of Visa events.

What are the Visa VAMP thresholds?

For most regions, Visa classes a merchant as Excessive when its monthly VAMP ratio is 1.5% or higher and it has at least 1,500 combined fraud reports and disputes. These figures come from Visa's own fact sheet, dated 14 May 2025, and from Stripe's monitoring program documentation, which agree.

The table shows the figures as of November 2026. Verify them against the current Visa document before you rely on them.

LevelRegionRatioMonthly minimumSource and date
Merchant ExcessiveUS, Canada, EU, Asia Pacific1.5% or more (reduced from 2.2% on 1 April 2026)1,500 fraud reports and disputesVisa fact sheet, 14 May 2025; Stripe docs
Merchant ExcessiveLatin America1.5% or more1,500Visa fact sheet; Stripe docs
Merchant ExcessiveCEMEA (Central Europe, Middle East and Africa)2.2% or more150 and USD 75,000Visa fact sheet; Stripe docs
Acquirer Above StandardWhole acquirer portfolio0.5% or moreSame minimum countVisa fact sheet
Acquirer ExcessiveWhole acquirer portfolio0.7% or moreSame minimum countVisa fact sheet

Visa's fact sheet says programs for Brazil, Chile and India will be announced later. It also says the updated thresholds took effect on 1 June 2025, with an advisory period that ended on 30 September 2025.

Two details matter in practice. Visa excludes disputes resolved through pre-dispute solutions and fraud reports qualified for Compelling Evidence 3.0, which is a way to show prior undisputed purchases by the same cardholder. And the VAMP also tracks card testing, which Visa calls enumeration, with its own ratio of 20% and a count of 300,000.

Stripe's documentation lists a lower "non-compliant" tier of 0.5% and 5 events that is not in Visa's fact sheet, and says Visa assesses fees on merchants above the Excessive line and may assess them on the lower tier. Fee amounts are not in the Visa fact sheet, so ask your acquirer what it passes through.

What are the Mastercard ECM and HECM thresholds?

Mastercard places a merchant in the Excessive Chargeback Merchant (ECM) program at 100 to 299 chargebacks and a ratio of 1.5% to 2.99%, and in the High Excessive Chargeback Merchant (HECM) program at 300 or more chargebacks and 3% or more. Both the count and the ratio must be met.

These figures come from a Chase Merchant Services FAQ that reproduces Mastercard's rules, created on 9 February 2022, and Stripe's current documentation, which matches them. Mastercard's own rules manual was not publicly readable, so verify with Mastercard or your acquirer.

Months over the thresholdECM fine (USD)HECM fine (USD)Issuer recovery assessment
100No
21,0001,000No
31,0002,000No
4 to 65,00010,000Yes
7 to 1125,00050,000Yes
12 to 1850,000100,000Yes
19 or more100,000200,000Yes

The schedule above is from Stripe's current documentation, and the 2022 Chase FAQ shows the same early steps. The issuer recovery assessment adds USD 5 per chargeback over 300. A merchant leaves the program after 3 consecutive months below the thresholds.

Mastercard also runs a separate fraud program, the Excessive Fraud Merchant program, with its own conditions on e-commerce volume, fraud chargebacks and 3-D Secure use. Stripe's documentation lists them if fraud disputes are your issue.

How do I fight a chargeback (representment)?

Representment is the merchant's response to a chargeback: you send evidence to the issuer that the charge was valid. Answer inside the deadline, send evidence that matches the reason code, and keep it short and organized.

Once a dispute is active, the only way to reverse it is to submit evidence, according to Stripe's documentation. Even if the customer says they withdrew the dispute, you still need to respond.

  1. Read the reason code and the claim. Decide whether to accept or contest. Accepting small disputes can cost less than contesting.
  2. Collect proof that fits the family. For fraud, that is authentication data, device and IP records and delivery details. For not received, it is tracking and signed delivery. For canceled subscriptions, it is the terms, the reminder emails and the cancellation record.
  3. Submit before the deadline, in the processor's dashboard or API.
  4. Record the outcome and the reason, so you can fix the cause.

Some disputes cannot be contested under network or local rules, and the processor closes them as lost when it notifies you.

How do I prevent chargebacks?

Most prevention is clear billing, fast support and fraud screening. Prevent first, because disputes count toward the ratio whether you win or lose. The checklist below follows the practices in Stripe's monitoring program documentation.

  • Use a billing descriptor customers recognize, and a clear receipt.
  • Show total price, delivery time and refund policy before payment.
  • Make cancellation easy for subscriptions, and send renewal reminders about 7 days before an annual renewal and 2 to 3 days before a monthly one.
  • Ship fast, send tracking and require a signature for higher-value goods.
  • Answer customers quickly, and refund when the complaint is fair.
  • Use 3-D Secure (3DS), the extra cardholder authentication step, on risky payments.
  • Separate authorization and capture, so you can reverse a suspicious payment before it is captured and reported.
  • Watch early fraud warnings and consider refunding small flagged payments.
  • Review your monthly ratios against the thresholds above, and watch for card testing.

Stripe's documentation suggests a refund is usually worthwhile when the charge is roughly at or below the dispute fee, and not worth it above about 35% over that fee.

How do chargebacks differ from refunds and from bank-transfer returns?

A refund is the merchant's choice, a chargeback is the issuer's forced reversal, and a bank transfer return follows the rules of the rail rather than the card network. Disputes on card payments run through Visa or Mastercard; on bank transfers each rail has its own return and recovery rules.

Bank transfers are not immune to disputes or reversals. Pix has a recovery mechanism for fraud and operational failures, and ACH payments can be returned in defined cases, but there is no card-style process for buyer's remorse on most instant rails. BlindPay covers these rail-by-rail rules in refunds and chargebacks when shoppers pay by bank transfer. Compare the rails in pay by bank for merchants.

RefundCard chargebackBank transfer return
Started byMerchantCardholder, through the issuerDepends on the rail and the case
Counts in Visa and Mastercard ratiosNoYesNot applicable
Merchant response windowNot applicableUsually 7 to 21 daysRail rules
Typical feeProcessing fee may applyDispute fee plus the lost saleRail and provider fees

For related risk topics, read how merchant underwriting assesses dispute risk, why rolling reserves follow high ratios and how authorization rates tie into declines. The wider acquiring picture is in what merchant acquiring is.

For the dispute process step by step, read chargebacks explained: process, reason codes and prevention; for the fines that follow a breach, read chargeback ratios and the fines that follow.

Methodology and sources

Visa figures come from the Visa Acquirer Monitoring Program fact sheet, document date 14 May 2025, and from Stripe's monitoring programs documentation, which is undated and references Visa changes through October 2026. Mastercard figures come from the Chase Merchant Services FAQ on excessive chargebacks, 9 February 2022, and the same Stripe page. Lifecycle timings come from Stripe on how disputes work, reason code families from Stripe's reason code categories, and the 0.75% line from Stripe on measuring disputes.

All sources were read in November 2026. Network thresholds, fees and deadlines change, and processors may set stricter limits, so confirm every figure with Visa, Mastercard and your acquirer. BlindPay is not a card acquirer and does not process card disputes. The related BlindPay guide is refunds and chargebacks on bank transfer checkouts.

Next, see how to improve card authorization rates, because many disputes start with declines, retries and unclear billing. If you also accept bank transfers, read pay by bank for merchants.

This article is general information, not legal, tax, or financial advice.

FAQ

One API.
Multiple payment rails.

Blind Pay, Inc. (“BlindPay”) is a United States-based financial technology and payments infrastructure company, incorporated in the State of Delaware on May 2, 2024. BlindPay is duly registered as a Money Services Business (“MSB”) with the Financial Crimes Enforcement Network (“FinCEN”) under registration number 31000277566153. BlindPay is not a state-licensed money transmitter and does not, in its own capacity, engage in regulated money transmission services. All such regulated activities are conducted exclusively through, and under the licenses of, duly authorized financial institution partners. BlindPay's role is limited to providing financial technology, virtual account management, payment processing, and related payments infrastructure services that facilitate payment flows and account functionalities. These services are provided in coordination with its licensed partners and in compliance with applicable federal MSB requirements and relevant state regulatory frameworks.

Blind Pay, LLC (“BlindPay”) is a Delaware limited liability company formed on June 24, 2025. BlindPay is duly registered as a Money Services Business (“MSB”) with the Financial Crimes Enforcement Network (“FinCEN”) under registration number 31000318334247 and is listed in the Nationwide Multistate Licensing System (“NMLS”) under NMLS ID #2745309.

BLIND PAY SOCIEDADE PRESTADORA DE SERVIÇOS DE ATIVOS VIRTUAIS LTDA. (“BlindPay”) is a Virtual Asset Service Provider (“VASP”) operating in Brazil. The company is presently completing the regulatory adaptation process required of Virtual Asset Service Provider Companies (SPSAV) under Central Bank of Brazil Resolution No. 520/2025, and remains subject to the transitional regime set forth in Article 88 of that Resolution. Registered address: Avenida Princesa Isabel, nº 15, Sala 1405, Edifício Martinho de Freitas, Centro, Vitória/ES, 29010-361.

BlindPay is a stablecoin API that enables individuals and businesses to move money worldwide.