Chargeback Management: Reason Codes, Representment, and Ratios

Effective chargeback management comes down to three habits: identify the reason code the moment a dispute arrives, match your evidence to that specific allegation, and file inside the card network’s response window. Everything else, from 3D Secure to arbitration strategy, is built on top of those three moves. Merchants who treat every dispute the same way lose winnable cases; merchants who tie their response to the code recover revenue that would otherwise be written off.

Start With the Reason Code

Reason codes are how the card networks tell you why a cardholder’s bank is pulling funds from your account. Each code points to a specific allegation, and the evidence that wins depends entirely on which code you’re facing. Submitting a delivery receipt against a duplicate-charge dispute guarantees a loss, no matter how clean the receipt is.

Visa organizes its reason codes into four categories, each processed through a different workflow:1Visa. Visa Optimizes Dispute Rules for Card-Not-Present Merchants

  • Fraud (10.x): The cardholder claims the transaction wasn’t authorized. Codes run from 10.1 (EMV liability shift for counterfeit fraud) through 10.5 (Visa Fraud Monitoring Program). Processed through Visa’s Allocation workflow, which automatically assigns liability.
  • Authorization (11.x): Something went wrong at authorization, such as a charge on a declined card or late presentment. Also handled through Allocation.
  • Processing Errors (12.x): Duplicate charges, wrong amounts, wrong currency. Handled through Visa’s Collaboration workflow, giving you a chance to respond before a formal chargeback.
  • Consumer Disputes (13.x): Goods not received, defective, or not as described. Also Collaboration. Includes canceled recurring transactions (13.2) and credits not processed (13.6).

Mastercard uses a parallel system with categories for Fraud, Authorization, Point-of-Interaction Errors, and Cardholder Disputes.2Mastercard. Chargebacks Made Simple Guide The specific numbers differ, but the logic is identical: identify the allegation, then match evidence to it. A fraud dispute demands proof the real cardholder made the purchase. A not-received dispute demands delivery confirmation. A processing-error dispute demands transaction records showing the charge was correct.

Friendly Fraud Is Most of What You’re Fighting

Friendly fraud happens when a legitimate cardholder makes a real purchase and then disputes it through their bank instead of asking you for a refund. Sometimes it’s buyer’s remorse. Sometimes a family member used the card. Sometimes the cardholder doesn’t recognize the billing descriptor and assumes fraud.

Industry data suggests friendly fraud drives roughly 75% of chargeback volume in e-commerce and an estimated 70% in digital goods and subscription services. First-party fraud became the leading fraud type globally in 2024, with continued growth projected through 2026. Repeat behavior is the sting: nearly half of consumers who file a friendly fraud chargeback do it again within 60 days.

The strategic problem is that these disputes usually arrive under fraud reason codes such as Visa 10.4, even though the cardholder actually made the purchase. Your rebuttal has to prove the cardholder is either lying or mistaken, which calls for a different evidence package than a genuine fraud case. Login records, device fingerprints, shipping address matches, and prior undisputed transactions from the same customer become the primary tools.

Prevent What You Can, Shift Liability on the Rest

Fighting a chargeback after it lands is more expensive than preventing it. Three tools do the prevention work.

3D Secure Authentication

3D Secure adds an identity verification step at online checkout, typically a one-time code or biometric prompt from the cardholder’s bank. The value isn’t the authentication itself; it’s the liability shift. When a transaction passes 3DS and the cardholder later files a fraud dispute, liability moves from you to the issuing bank. The shift applies to fraud reason codes (Visa 10.1 through 10.5) but does not cover not-as-described or services-not-received disputes. If your chargebacks skew toward fraud codes, 3DS is the highest-impact tool available.

Visa Compelling Evidence 3.0

Compelling Evidence 3.0 lets you overturn fraud disputes under reason code 10.4 by proving the same customer has a history of legitimate purchases with you. To qualify, you must supply at least two previous undisputed transactions from the same payment card that meet each of these criteria:3Visa. Compelling Evidence 3.0 Merchant Readiness

  • Age: At least 120 days old but no older than 365 days from the dispute date.
  • Clean history: No active fraud reports or fraud disputes on those transactions.
  • Data matching: At least two of these must match between prior transactions and the disputed one — user ID, IP address, shipping address, or device ID/fingerprint.
  • Required element: At least one of the two matching elements must be either the IP address or the device ID/fingerprint.

When valid CE 3.0 data is submitted, Visa assigns liability to the issuer. You get one attempt; if the data is incorrect or incomplete, Visa declines the submission and resubmission isn’t allowed.4Visa. Compelling Evidence 3.0 Acquirer Readiness That means you need to be capturing user IDs, IP addresses, and device fingerprints on every transaction well before any dispute arrives. If you’re not logging that data now, CE 3.0 can’t help you later.

Chargeback Alert Services

Alert networks like Ethoca (Mastercard) and Verifi’s Cardholder Dispute Resolution Network notify you the moment an issuer receives a dispute, before it becomes a formal chargeback. That window lets you refund and stop the chargeback from hitting your record. You lose the transaction amount but avoid the chargeback fee, the representment work, and the damage to your ratio. One caveat: even when you refund through an alert, issuers may still file TC40 fraud reports that count against you under Visa’s monitoring programs.

Building the Rebuttal Package

When a dispute does formalize, the response package has to be built around the specific reason code. Every document should directly counter the cardholder’s allegation.

For fraud disputes (10.x codes), gather evidence that the real cardholder made the purchase: AVS and CVV match results, IP address logs, device fingerprints, login activity showing the customer’s own account was used, and prior purchase history that was never disputed. For not-received disputes such as Visa 13.1, a carrier tracking number showing delivery to the cardholder’s confirmed address is the anchor. For not-as-described disputes like Visa 13.3, product photos, listing screenshots, and any communication where the customer acknowledged the product matched expectations help carry the case.

Digital products and subscription services are harder because there’s no shipping receipt. Server logs showing the customer downloaded content, accessed the service, or logged in after the transaction date become your delivery proof. IP addresses and timestamps that match the customer’s known activity pattern strengthen the record.

Your terms and refund policy matter more than most merchants realize. A clearly displayed refund policy the customer accepted at checkout, through a signed order form or a checkbox, can neutralize disputes where the cardholder simply didn’t like what arrived. For online sales, the FTC’s Mail Order Rule requires shipment within the promised timeframe or within 30 days if none was stated (50 days if the buyer applied for credit through you).5eCFR. 16 CFR Part 435 – Mail, Internet, or Telephone Order Merchandise If you miss that deadline, you must notify the customer and offer a full refund including shipping, with no substitution of store credit or vouchers. Refunds have to go out within seven working days of cancellation. Violating the rule makes a not-received chargeback essentially unwinnable.

Communication records finish the package. Email threads or chat logs showing the customer tried to resolve the issue with you first demonstrate responsiveness. Their absence often signals friendly fraud. The rebuttal letter itself should state the transaction details, explain why the charge was valid, and list every attached document in a single, navigable file. A bank reviewer working through a disorganized submission will not hunt for evidence in your favor.

Deadlines, Representment, and Arbitration

The clock starts the moment the chargeback notification lands. Visa gives merchants 30 calendar days to respond with a representment package. Mastercard allows 45 days. Missing those deadlines means automatic loss and permanent forfeiture of the disputed funds.

Representment is the formal act of re-presenting the original transaction to the issuing bank with new evidence, usually through your payment processor’s portal. Your acquiring bank reviews the package for completeness, then forwards it through the card network to the issuer, who decides whether to reverse or uphold the chargeback.

If the issuer rejects the representment, the dispute can escalate. Mastercard’s process allows pre-arbitration, where either party can try to resolve the case before a final ruling.2Mastercard. Chargebacks Made Simple Guide Visa’s process works similarly, with pre-arbitration as the last negotiation stage before arbitration.

Arbitration is the end of the road. The card network reviews all evidence and issues a binding ruling. The losing party pays the disputed amount plus administrative fees, and those fees are steep: Visa’s case filing fee runs $600 as of 2025, absorbed by the loser on top of any other assessments. Mastercard charges its own case filing fees and may add technical violation fees.6Mastercard. Chargebacks Made Simple Guide – Section: 5.4 The math is unforgiving. On a $75 dispute, losing arbitration costs you $75 plus $600. Arbitration only makes sense when the transaction amount is high enough to justify the risk, or when a precedent against a repeat-offender cardholder matters.

Watch Your Chargeback Ratio

Individual disputes aren’t the whole picture. Card networks monitor merchant chargeback ratios and penalize businesses that stay above threshold.

Visa consolidated its separate fraud and dispute programs into VAMP, the Visa Acquirer Monitoring Program. Under VAMP, Visa calculates a combined ratio: total fraud reports plus disputes divided by settled transactions. For U.S. merchants, the “Excessive Merchant” threshold is a VAMP ratio of 220 basis points (2.2%) with at least 1,500 monthly fraud reports and disputes. That threshold drops to 150 basis points (1.5%) on April 1, 2026.7Visa. Visa Acquirer Monitoring Program Fact Sheet 2025

Mastercard runs its own monitoring with separate thresholds. Both networks impose escalating consequences: warnings, monthly fines that grow with each consecutive month above threshold, and ultimately termination of your merchant account. Termination lands you on the MATCH list (Member Alert to Control High-Risk Merchants), which makes it extremely difficult to open a new account with any processor for five years.

Track every dispute internally by reason code, transaction date, product category, and outcome. Aggregate ratios hide the patterns that matter. A spike in not-received chargebacks from one shipping carrier points to a fulfillment fix. A cluster of fraud disputes from a specific region calls for tighter screening on those orders. Turning dispute data into operational changes is what moves the ratio; winning individual cases doesn’t.

The Federal Laws Behind the System

Chargebacks run mostly on card network rules, but two federal statutes create the consumer rights that make the system function.

The Fair Credit Billing Act governs credit card disputes. It gives cardholders 60 days after their billing statement is transmitted to send written notice of a billing error.8Office of the Law Revision Counsel. 15 USC 1666 – Correction of Billing Errors For undelivered-goods disputes, the creditor cannot simply declare the charge correct — it must determine that the goods were actually delivered and give the cardholder a statement of that determination. That statutory language is precisely why delivery confirmation is so decisive in fighting not-received chargebacks.

Debit card disputes fall under the Electronic Fund Transfer Act and Regulation E, which set tiered consumer liability based on how quickly the cardholder reports an unauthorized transfer.9eCFR. 12 CFR Part 1005 – Electronic Fund Transfers (Regulation E) The practical effect for merchants is that debit disputes tend to arrive faster than credit disputes, and provisional credits to the cardholder often move more quickly than under the FCBA timeline.

The Real Cost and the Tax Treatment

The direct cost of a chargeback extends well past the transaction amount. Payment processors charge a per-chargeback fee whether you win or lose, typically $15 to $100 depending on processor and risk category. Add lost merchandise, staff time to prepare rebuttals, and any network fines from an elevated ratio, and the true cost of a single chargeback runs two to three times the original transaction value.

On the tax side, chargeback-related expenses are generally deductible as ordinary and necessary business costs. Processor fees, network fines, and administrative costs qualify. Unrecovered losses from chargebacks you couldn’t overturn are treated as business bad debts, but the deduction depends on your accounting method. Accrual accounting: you likely already reported the sale as income, so you can deduct the loss as a bad debt. Cash accounting: you generally reported income only when you received payment, and if the chargeback clawed it back, there’s no prior inclusion to offset.10Internal Revenue Service. Publication 535 – Business Expenses Confirm the treatment with your accountant, because the difference between accrual and cash catches small businesses off guard.