Chargeback Reason Code

What a chargeback reason code is

A chargeback reason code is a number or short alphanumeric label attached to a cardholder’s dispute. The issuer assigns it based on the reason the cardholder gives, such as an unauthorized transaction, an item not received, or a processing error. Visa and Mastercard maintain separate code systems, so the same dispute category does not always use the same code across networks.

The code records the stated reason for the dispute. It does not prove that the cardholder’s claim is accurate. A customer who received an order but no longer wants it, for example, could still report the payment as unauthorized. Treat the code as a guide to the claim you need to answer, not as a finding about what happened.

The code tells you what claim to answer, not whether the claim is true.

How the code guides your response

The code points you toward the evidence that matters. For an item-not-received dispute, gather tracking, delivery confirmation, and order records. For an unauthorized-payment claim, look for authorization details, AVS or card security code results, and records linking the purchase to the customer. A signed agreement or customer messages can also address the specific claim.

Send a written rebuttal that connects each piece of evidence to the reason code. A receipt alone will not answer a delivery complaint, and proof of delivery will not establish that a customer authorized a card-not-present transaction. As of 2026, cardholders generally have 120 calendar days to dispute under Visa and Mastercard rules, while your response window is shorter, often 20 to 30 days as set by your processor.

What it means for your costs and risk

The reason code itself does not carry a separate fee. The dispute attached to it can cost you the transaction amount, a chargeback fee, staff time, and, if you lose, the goods or services you already provided. The fee amount depends on your processing arrangement, so compare the chargeback fee on your statement with the fee listed in your agreement.

A strong response can recover the disputed sale, but winning does not remove the chargeback from your chargeback ratio. All chargebacks count, whether you contest them successfully or not. That makes prevention and quick, code-specific responses important even when you expect to win.

Read the code before you gather evidence

Start with the network, code, and plain-language description shown in your dispute notice. Then check that the order date, amount, customer, and claimed problem match your records. Network codes distinguish between issues such as fraud, authorization, processing, and customer disputes, so responding to the wrong category wastes time and can leave the actual claim unanswered.

Keep records organized by transaction and dispute reason. That makes it easier to spot repeat problems, such as unclear billing descriptors, late fulfillment, or recurring-payment cancellations. If several disputes share one reason code, fix the underlying customer or operational issue instead of treating each case as an isolated paperwork task.

What you can actually change

1. 01
   Read the full notice. Record the network, reason code, description, and response deadline. Confirm the transaction details before building your case.
2. 02
   Match evidence to the claim. Use delivery records for non-receipt claims, and authorization or customer records for unauthorized-payment claims. Explain how each document addresses the code.
3. 03
   Track repeat codes. Review disputes by reason code and sales channel. Repeated delivery, billing, or cancellation complaints point to a fix that can prevent future chargebacks.

Frequently asked questions