Reason codes, card-network rules, and dispute jargon — explained the way a small business owner actually needs it, not the way a compliance manual writes it.
Representment, retrieval request, friendly fraud, RDR, CE 3.0 — every term defined in one sitting, no jargon left unexplained.
Browse the glossary →Reason code categories, response deadlines, and how Visa's VAMP program changes what "too many disputes" actually means in 2026.
See the rules reference →Practical articles on stopping disputes before they start, told from the perspective of a small operations team, not an enterprise fraud desk.
Read the articles →What's actually changing across Visa, Mastercard, and fraud tactics right now — summarized for merchants, not compliance officers.
See the latest trends →Short, practical reads — written for the person who owns chargebacks part-time, not a dedicated risk department.
Most chargeback prevention advice is written for teams with a dedicated fraud analyst and a six-figure tooling budget. Small and mid-size merchants need the version that fits inside a normal week. These five habits catch the majority of preventable disputes without adding headcount.
A large share of "I don't recognize this charge" disputes are simply confusion — the name on the bank statement doesn't match the brand the customer remembers buying from. Set your statement descriptor to your actual trading name plus a phone number or short URL, and keep it consistent across every payment platform you use.
"Item not received" is one of the most common reason codes across every card network. Whenever possible, use tracked shipping and keep delivery confirmation attached to the order record — it's the single strongest piece of evidence in a representment.
A customer who can't find your refund policy, or who has to email three times to get a response, often disputes instead. A visible refund policy and a fast first response meaningfully reduce "I tried to return this" disputes.
Card networks measure merchants by the ratio of disputes to total transactions, not the raw count. A small spike can look dramatic in percentage terms for a business processing a few hundred transactions a month — so it's worth tracking that ratio monthly, not just revenue.
Missing a response window is an automatic loss regardless of how strong your evidence is. Build a simple recurring reminder (weekly is usually enough for most small merchants) to check for new disputes across every platform you accept payments on.
Not every chargeback is fraud, and not every "fraud" chargeback was actually committed by a criminal. Understanding the difference changes how you should respond.
This is the fraud most people picture: a stolen card number used by someone who was never the account holder. The legitimate cardholder genuinely didn't make the purchase, and in most cases the merchant has limited recourse beyond following standard fraud-prevention practices (AVS/CVV checks, 3-D Secure where appropriate, velocity monitoring).
This happens when the actual cardholder made the purchase, received the goods or service, and disputes the charge anyway — sometimes out of genuine confusion, sometimes because it's faster than requesting a refund, and sometimes deliberately. Industry estimates consistently point to friendly fraud as the larger and faster-growing share of chargebacks for most merchant categories, particularly in e-commerce and subscriptions.
Friendly fraud is winnable. Because the transaction was legitimate, a well-documented representment — clear proof of delivery, terms the customer agreed to, communication history — has a real chance of reversing the dispute. Criminal fraud is generally not winnable through representment; the better investment there is prevention on the front end.
It helps to see the whole path a dispute travels, since most of the deadlines and terminology only make sense in context.
The cardholder contacts their bank (the "issuer"), not the merchant. The issuer assigns a reason code that best fits the cardholder's complaint and provisionally reverses the funds.
The merchant's bank (the "acquirer") or payment processor notifies the merchant, usually through a dashboard or email, with a fixed window to respond — commonly 30 days for Visa and 45 days for Mastercard, though this varies by network and case type.
The merchant submits evidence — proof of delivery, signed terms, communication logs, authentication data — arguing the charge was valid. This is where a specialist partner typically adds the most value, since evidence has to match the specific reason code's requirements.
If the issuer disagrees with the representment, the case can escalate to pre-arbitration, and ultimately arbitration, where the card network itself rules on the case. This stage carries additional fees and is relatively rare for small merchants, but it exists as a final step.
In 2025, Visa began retiring its older Visa Dispute Monitoring Program (VDMP) and Visa Fraud Monitoring Program (VFMP) in favor of a single combined program: the Visa Acquirer Monitoring Program (VAMP). Enforcement began October 1, 2025, with revised thresholds effective April 2026.
The biggest shift is that VAMP measures fraud and disputes together, and monitors risk substantially at the acquirer-portfolio level rather than merchant-by-merchant in isolation. That means the bank or processor underwriting your payments now has a direct stake in your dispute ratio — which is part of why some processors have gotten stricter about onboarding higher-risk small merchants.
Under the April 2026 thresholds, a merchant is generally classified "Excessive" at a combined fraud-plus-dispute ratio of 1.5% (2.2% in the CEMEA region), provided it also crosses a minimum volume of 1,500 combined TC40/TC15 records. See the full Visa & Mastercard rules reference for the complete threshold table.
For a small merchant, the practical takeaway isn't the exact percentage — it's that dispute ratio, not just raw dispute count, is what determines risk classification. A merchant processing a modest volume can cross a threshold faster than a much larger one, because the ratio is what's measured, not the dollar amount or transaction count alone.
