10 Most Common Chargeback Reason Codes and How to Defend Each

Chargebacks are an unavoidable challenge for merchants. When a customer disputes a transaction, the issuing bank assigns a reason code, classifying the complaint. Understanding these codes is paramount to crafting compelling representments. Here we analyze the ten most prevalent chargeback reason codes across major card networks and provide actionable defense tactics for each. **1. Fraud – Unauthorized Transaction (e.g., Visa 83 / Mastercard 4837)** The cardholder claims they did not authorize the purchase. Common scenarios include stolen card data or friendly fraud. Defense: Submit compelling evidence of authorization: AVS/CVV match, IP geolocation consistent with billing address, signed delivery confirmation, and prior transaction history. If you used 3D Secure, provide the authentication proof to shift liability. **2. Product Not Received (e.g., Visa 13.1 / Mastercard 4855)** The customer paid but never received the goods or services. This often arises from shipping delays or miscommunication. Defense: Provide tracking information showing delivery to the address on file, along with carrier proof of delivery. For digital goods, share access logs, IP addresses, and timestamps of download or usage. **3. Product Not as Described or Defective (e.g., Visa 13.3 / Mastercard 4853)** The item received differs materially from the listing, is damaged, or misrepresented. Defense: Present the original product description, photos from the listing, and any correspondence where the buyer acknowledged the condition. If you have a clear return policy that the cardholder ignored, document that. Show evidence of use or benefit if the claim is exaggerated. **4. Duplicate Processing (e.g., Visa 82 / Mastercard 4834)** The cardholder asserts they were charged twice for a single purchase. Defense: Prove that each charge corresponds to a separate transaction (e.g., two distinct orders). If a genuine duplicate occurred, process a refund immediately and submit the credit documentation; if you already credited, provide the transaction ID and date. **5. Recurring Billing Not Cancelled (e.g., Visa 13.2 / Mastercard 4841)** The customer cancelled a subscription but continues to be billed. Defense: Supply the cancellation policy and the cardholder’s explicit sign-up details, including IP, timestamp, and agreement to terms. Prove that no valid cancellation request was received, or that the charge fell within the notice period. If usage logs show activity after the alleged cancellation date, include that. **6. Credit Not Processed (e.g., Visa 13.6 / Mastercard 4860)** The merchant promised a refund or credit but failed to issue it. Defense: Present records confirming the credit was processed—transaction ID, date, and amount. If you offered a replacement instead of a refund and the cardholder agreed, share that communication. **7. Cardholder Does Not Recognize Transaction (e.g., Visa 75 / Mastercard 4831)** The customer doesn’t recall the merchant or the purchase, often due to an unclear billing descriptor. Defense: Ensure your descriptor is clear and recognizable. Provide the transaction receipt, description of goods sold, IP address, and any membership or account linking the cardholder to the purchase. A simple clarification often resolves this. **8. Late Presentment (e.g., Visa 74 / Mastercard 4842)** The transaction was submitted for settlement beyond the allowed timeframe (typically 7–30 days after the transaction date). Defense: Show the transaction and settlement dates to demonstrate compliance with network rules. If a pre-order or delayed delivery was agreed, provide that contract. If you were genuinely late, focus on process improvement—this reason code is difficult to overturn. **9. Invalid Account Number (e.g., Visa 72 / Mastercard 4846)** The account number used does not exist or was entered incorrectly. Defense: Demonstrate that you obtained authorization for the exact account number provided by the cardholder. Supply the authorization log. For recurring payments, provide the original valid authorization. This is often a keying error; having the customer’s consent records helps. **10. Transaction Amount Differs (e.g., Visa 76 / Mastercard 4835)** The billed amount doesn’t match what the cardholder agreed to pay. Defense: Submit the order confirmation or quote showing the agreed total. If additional charges (e.g., shipping or taxes) were added, prove they were disclosed at checkout. For currency conversion discrepancies, provide the prevailing exchange rate at the time of purchase. Winning chargeback disputes requires proactive evidence collection and a thorough understanding of reason codes. By maintaining meticulous records—delivery confirmations, signed agreements, communication logs—you can build a strong representment for every case. Always tailor your response to the specific code, and stay informed on evolving network regulations to protect your revenue.