Skip to content

Chargebacks explained: the dispute process, reason codes, timelines, and how to prevent them

What a chargeback is, how the dispute process works step by step, Visa reason codes and VAMP thresholds, and how merchants prevent and fight disputes.

A chargeback is a reversal of a card payment that the cardholder starts through their issuing bank. The issuer raises the dispute under card scheme rules, the acquirer passes it to the merchant, and the merchant can accept it or send evidence to defend the sale. Prevention depends on clear billing descriptors, fast refunds, strong authentication and good evidence.

This guide walks through the process, the reason codes, the monitoring thresholds and the steps that lower your dispute rate. It reflects Visa's public rules and merchant guides, Visa's monitoring fact sheet and published industry research as of October 2026. Network rules change often, so confirm each deadline with your acquirer.

Key takeaways

  • A chargeback is forced, a refund is voluntary. The cardholder's bank starts a chargeback, and the card network's rules decide the outcome.
  • Volume is growing. Datos Insights research for Mastercard forecast 261 million chargebacks globally in 2025 and 324 million in 2028.
  • Visa groups disputes into four categories: fraud, authorization, processing errors and consumer disputes.
  • Monitoring programs have hard thresholds. Visa's excessive merchant threshold dropped to 150 basis points in several regions on April 1, 2026.
  • Evidence wins disputes. A response works only when it answers the specific reason code.

What is a chargeback?

A chargeback is a forced reversal of a card payment. The cardholder contacts the issuer, the bank that issued the card, and says a charge is wrong. The issuer then pulls the money back from the merchant's side through the card network.

Chargebacks exist to protect cardholders from fraud and from merchants that do not deliver. The card networks write the rules, and the banks on both sides follow them. The acquirer, the merchant's payment provider, is the merchant's contact in every dispute.

Card networks often use the word "dispute" for the whole process and "chargeback" for the reversal itself. This guide uses both. For the stages a payment goes through before a dispute can happen, see how card payments work.

How does the chargeback process work step by step?

The process moves in a fixed order: cardholder, issuer, network, acquirer, merchant, and back again. Each step has a deadline set by the network, and your acquirer sets a shorter one for you inside it.

StepWho actsTypical deadline (verify per network)Merchant action
1. The cardholder questions a chargeCardholderInside the issuer's dispute window. Under Visa's rules the issuer has 120 calendar days from the transaction processing date for an other-fraud, card-absent dispute, and the limit varies by conditionAnswer support requests fast and refund valid claims
2. The issuer raises the disputeIssuerSet by network rulesNone yet. The issuer assigns a reason code
3. The network routes the disputeCard networkSet by network rulesNone
4. The acquirer debits and notifies the merchantAcquirerSet by network rules and your acquirerRead the reason code and note your response deadline
5. The merchant accepts or respondsMerchant, through the acquirerSet by network rules and your acquirer. Visa's rules give the acquirer 30 calendar days from the dispute processing date in the processing error and consumer dispute categoriesAccept the loss, or send evidence that answers the reason code
6. The issuer reviews the responseIssuerSet by network rulesWait. The funds return if the issuer accepts the evidence
7. Pre-arbitration and arbitrationIssuer, acquirer, then the networkSet by network rulesDecide with your acquirer whether the amount justifies the extra fees

The day counts in the table come from the Visa Core Rules. Visa's own Dispute Management Guide for Merchants does not give merchants a day count. It tells them to check timelines with their acquirer, because the acquirer needs part of the window for its own work.

Other networks run a similar sequence with their own deadlines and names. Ask your acquirer for the current figures for each network you accept.

What do the common reason codes mean?

A reason code tells you what the cardholder or issuer claims. It also tells you what evidence can answer the claim. Visa's merchant guide groups its dispute conditions into four categories.

Visa categoryWhat the claim saysCommon exampleEvidence that helps
10 FraudThe cardholder did not authorize the paymentA stolen card number used online. Condition 10.4 covers other fraud in a card-absent environmentAuthentication results, address and security code checks, prior purchase history
11 AuthorizationThe payment was processed without a valid authorizationA sale completed after a declineAuthorization records with dates and amounts
12 Processing errorsThe payment was processed incorrectlyA duplicate charge or a wrong amountProof of two separate sales, or of the correct amount
13 Consumer disputesThe cardholder did not get what they paid forGoods not received, not as described, or a cancelled subscription still billedDelivery proof, product description, accepted terms and cancellation records

Each category contains several numbered conditions. Other card networks use their own code lists, so always read the code on the dispute notice and look it up in that network's guide.

Fraud and consumer disputes make up most of what online merchants see. Fraud disputes are harder to defend unless the payment was authenticated. 3-D Secure matters here because a successful authentication generally shifts fraud liability to the issuer.

How do a chargeback, a refund and a retrieval request differ?

They differ in who starts them and what they cost. A refund is the cheapest outcome for a valid complaint. A chargeback is the most expensive.

RefundRetrieval requestChargeback
Who starts itThe merchantThe issuerThe cardholder, through the issuer
Does money move?Yes, back to the cardNoYes, pulled from the merchant
Fee to the merchantUsually none beyond the original processing costDepends on the merchant agreementA per-dispute fee set in the merchant agreement
Counts toward monitoring ratiosNoNoYes
What to doIssue it quickly when the claim is validSend the requested transaction details before the deadlineAccept, or respond with evidence

A retrieval request, sometimes called an inquiry, is an issuer's request for information about a transaction. It is a warning sign. A clear and prompt answer can stop it from becoming a chargeback.

For purchases paid by bank transfer, where no card network sits in the middle, see refunds and chargebacks when shoppers pay by bank transfer.

Why are chargebacks rising?

Chargebacks are rising because online card volume is growing and because more cardholders dispute purchases they made themselves. Three sets of figures show the trend.

  • Volume. Datos Insights research for Mastercard (March 2025), as reported by Tearsheet and PayPal, forecast 261 million chargebacks globally in 2025 and 324 million in 2028. The forecast value rises from $33.79 billion to $41.69 billion over the same period.
  • Fraud share. The same research puts fraudulent chargebacks, first-party and third-party combined, at 45% of merchant chargeback volume globally.
  • Network caseload. Visa says it handled 105 million disputes in 2025, on its dispute resolution page.

Two causes stand out. The first is first-party misuse, often called friendly fraud, where a cardholder disputes a purchase they actually made. In the 2026 Global eCommerce Payments and Fraud Report from Visa and the Merchant Risk Council (March 2026), 64% of respondents reported a meaningful increase in first-party misuse. Our guide to friendly fraud covers it in depth.

The second is subscriptions. A quarter of Mastercard chargebacks are linked to recurring transactions, according to Mastercard data cited by PayPal (September 2026). Customers forget a renewal, cannot find the cancel button, or do not recognize the descriptor. Recurring card payments explains how to reduce those disputes.

What is Visa VAMP and what are the monitoring thresholds?

The Visa Acquirer Monitoring Program (VAMP) is Visa's program for tracking fraud and disputes across acquirers and their merchants. It uses one combined ratio for card-not-present transactions, per Visa's VAMP fact sheet (2025):

VAMP ratio = (reported fraud + disputes) ÷ settled transactions

Visa's fact sheet excludes two things from the ratio: disputes resolved through pre-dispute solutions, and fraud that qualifies for Compelling Evidence 3.0. Both exclusions depend on the timing of Visa's data extract.

Who is measuredLevelThreshold (Visa fact sheet, 2025)
AcquirerAbove Standard50 basis points or more
AcquirerExcessive70 basis points or more
Merchant in Asia Pacific, Canada, the EU and the USExcessive220 basis points or more with at least 1,500 monthly fraud and dispute counts, reduced to 150 basis points on April 1, 2026
Merchant in Latin America and the CaribbeanExcessive150 basis points or more with at least 1,500 monthly counts

A basis point is one hundredth of a percentage point, so 150 basis points is 1.5%. The updated thresholds took effect on June 1, 2025, and Visa's advisory period ended on September 30, 2025. PayPal (September 2026) describes the program as in active enforcement since October 1, 2025.

Mastercard runs its own program. Its Excessive Chargeback Program flags a merchant at 100 to 299 chargebacks with a ratio of 1.50% to 2.99%, and puts it in a higher tier at 300 or more chargebacks with a ratio of 3.00% or more. Both conditions must be met. These figures come from PayPal's Braintree documentation, not from a Mastercard document, so confirm them with your acquirer.

A merchant that crosses a threshold can face fees, remediation plans and, in the end, loss of card acceptance. The acquirer is measured too, so acquirers act on risky merchants before the network does.

How do you prevent chargebacks?

Most chargebacks can be prevented before the cardholder calls the bank. These nine steps cover the main causes.

  1. Use a billing descriptor customers recognize. Match the name on the statement to the name on your site, and add a support phone number or URL where the network allows it.
  2. Make refunds and cancellations easy. A customer who gets a quick refund has no reason to call the issuer. A refund does not count toward monitoring ratios.
  3. Authenticate online payments. 3-D Secure adds an issuer check at checkout, and a successful authentication generally shifts fraud liability to the issuer.
  4. Run address and security code checks. They do not stop every fraudster, but a match strengthens your evidence.
  5. Send clear confirmations. Email the order, the price, the delivery date and the cancellation terms at the time of sale.
  6. Remind subscribers before renewals. Send a notice before each renewal and after every price change.
  7. Keep delivery and usage records. Save tracking numbers, signatures, download logs and login history.
  8. Use pre-dispute tools. Alerts and automated resolution services let you refund a case before it becomes a chargeback. Visa excludes disputes resolved through pre-dispute solutions from the VAMP ratio.
  9. Answer customer support quickly. A slow reply is one of the most common reasons a cardholder turns to the bank.

How do you fight a chargeback?

You fight a chargeback by sending evidence that answers the reason code, through your acquirer, before the deadline. The response is called representment.

  1. Read the reason code first. It defines what you have to prove. Delivery proof does not answer a fraud claim.
  2. Decide whether to respond. Accept disputes that are valid or too small to justify the work.
  3. Collect evidence that matches the code. For fraud, use authentication results and prior purchase history. For consumer disputes, use delivery proof and the terms the customer accepted.
  4. Write a short cover summary. State the claim, the facts and the evidence in a few lines. The reviewer handles many cases.
  5. Submit through your acquirer's portal before its deadline. Late responses lose by default.
  6. Track the outcome. Record wins and losses by reason code, so you can fix the cause and not only the case.

For fraud disputes in card-absent sales, Visa's Compelling Evidence 3.0 rules let a merchant show that the same customer made earlier, undisputed purchases with matching device or network details. The friendly fraud guide lists the exact requirements.

If the issuer rejects your response, the case can go to pre-arbitration and then arbitration. The network decides, and the losing side pays extra fees. Go that far only for large amounts with strong evidence.

How do chargebacks compare with stablecoin payments?

Stablecoin transfers have no card-network chargeback process. Once a transfer confirms on-chain, no issuer can pull it back. Montague Law puts it this way: "card-network dispute rights do not exist on-chain, so your terms of sale have to do that work".

That removes chargeback fraud for the merchant. It also removes a protection the buyer is used to. Refund terms, identity checks and monitoring have to carry more weight.

BlindPay is a stablecoin payout and collection API, and its controls sit in the payment flow. KYC, KYB, sanctions screening, travel rule checks and compliance review run inside the API, before money moves. If a payout cannot be delivered after the stablecoins are collected, BlindPay refunds them to the quote's refund wallet, or to the sending wallet when none is set.

Cards keep their rules even when stablecoins are involved. BlindPay accepts cards as one payin method, and a chargeback received later moves that payin to refunded, per the card payins docs. Stablecoin payins vs cards vs SWIFT wires compares the dispute risk of each method.

What changed recently?

  • April 2023. Visa introduced Compelling Evidence 3.0 for card-absent fraud disputes, per PayPal.
  • March 2025. Datos Insights research for Mastercard forecast 324 million chargebacks in 2028.
  • June 1, 2025. Updated VAMP thresholds took effect, with an advisory period that ended on September 30, 2025 (Visa fact sheet).
  • October 1, 2025. VAMP entered active enforcement, per PayPal.
  • March 2026. The Visa and Merchant Risk Council report found that 64% of respondents saw a meaningful increase in first-party misuse.
  • April 1, 2026. Visa's excessive merchant threshold dropped from 220 to 150 basis points in Asia Pacific, Canada, the EU and the US (Visa fact sheet).

Sources

  • Visa, Visa Acquirer Monitoring Program fact sheet (2025): corporate.visa.com
  • Visa, Dispute Management Guide for Merchants (2026): usa.visa.com
  • Visa, Visa Core Rules and Visa Product and Service Rules (2026): usa.visa.com
  • Visa, "Resolve issues earlier to help avoid chargebacks" (2026): visa.com
  • Visa and Merchant Risk Council, 2026 Global eCommerce Payments and Fraud Report (March 2026): visaacceptance.com
  • Tearsheet, on the Datos Insights research for Mastercard (April 2025): tearsheet.co
  • PayPal, dispute management and chargeback prevention (September 2026): paypal.com
  • PayPal Braintree, Mastercard Excessive Chargeback Program (2026): developer.paypal.com
  • Montague Law, accepting stablecoin payments (2026): montague.law

What to do next

Pull last quarter's disputes, group them by reason code, and fix the largest group first. Then read friendly fraud explained for the evidence rules and 3-D Secure explained for the liability shift. If you also collect by bank transfer or stablecoin, how card payments work shows where each method differs, and you can test BlindPay payins on a free development instance.

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.