What Are Chargeback Reason Codes? How to Read Them

On this page 7 sections

1. What a Chargeback Reason Code Is
2. Fraud vs. Dispute Codes: The Four Main Reason Code Categories
3. Common Visa Reason Codes and Mastercard Chargeback Codes
4. Matching Evidence to the Reason Code
5. Example: Responding to a 'Product Not Received' Dispute
6. Using Reason Code Trends to Prevent Future Chargebacks
7. Next Steps

Key takeaways

• A chargeback reason code is the issuer's label for why a cardholder disputed a charge, and it decides which evidence counts in your response.
• Most codes fall into four groups: fraud, authorization, processing errors and consumer disputes. Each group is won with different proof.
• Fraud codes need proof the real cardholder made the purchase. Consumer dispute codes need proof you delivered what you promised and followed your stated policies.
• Tracking reason codes over time shows where chargebacks start, whether in checkout, billing, fulfillment or customer service.

When a chargeback lands, the notice includes a short code that looks like noise: 10.4, 13.1, 4837. These chargeback reason codes are the most useful part of the notice. They tell you what the cardholder's bank says went wrong, which evidence can reverse the dispute, and whether the case is worth fighting. This guide covers what reason codes are, how they group into four categories, the Visa and Mastercard codes merchants see most, and how to match your evidence to each type.

What a Chargeback Reason Code Is

A reason code is a label the card issuer attaches to a dispute when a cardholder asks to reverse a charge. The usual sequence looks like this:

1. The cardholder contacts their bank and disputes a transaction.
2. The issuer classifies the complaint and assigns a reason code.
3. Your processor notifies you and pulls the funds back from your account, usually with a fee.
4. You either accept the chargeback or respond with evidence. That response is called representment.
5. The issuer reviews your evidence and decides the case.

Each card network keeps its own code set. Visa uses numbered categories with decimals, such as 13.1. Mastercard uses four-digit codes, such as 4853. American Express and Discover have their own systems. Your processor's portal may show the network code, its own plain-language label, or both.

Two points matter before you respond:

• The code shows how the issuer framed the dispute, which may not match what happened. A customer who forgot a purchase can end up with a fraud code. That pattern is often friendly fraud that merchants can spot and contest.
• Reason codes are different from decline codes. Decline codes explain why a transaction was refused at the moment of purchase. If those are what you're looking at, see our guide to credit card decline codes and what to do about each one.

Fraud vs. Dispute Codes: The Four Main Reason Code Categories

The networks label things differently, but nearly every reason code falls into one of four groups. Knowing the group tells you what kind of proof you need.

Why the Fraud vs. Dispute Distinction Matters

In a fraud dispute, the question is who made the purchase. Delivery tracking alone rarely settles it, because the issuer is saying the cardholder never placed the order. You need identity and authentication evidence.

In a consumer dispute, the cardholder admits they bought something. The question is whether you delivered what you promised. Login records and IP addresses help less here. Fulfillment records, product pages and policy acceptance help more.

Fraud disputes can also count toward card network monitoring programs, which affects how processors view your account. Our explainer on Visa's fraud and dispute monitoring thresholds covers how that works.

Common Visa Reason Codes and Mastercard Chargeback Codes

Below is a short chargeback reason code list covering the codes online, recurring and in-person merchants see most often. The networks revise their code sets from time to time, so confirm current definitions with your processor or the network's published dispute rules.

Visa Reason Codes

The number before the decimal maps to the category: 10 is fraud, 11 is authorization, 12 is processing errors and 13 is consumer disputes.

Mastercard Chargeback Codes

Mastercard has folded many older codes into 4853, which now covers not received, not as described, cancelled recurring billing and similar complaints. You may still see legacy codes such as 4855 (Goods or Services Not Provided) or 4841 (Cancelled Recurring or Digital Goods) in older reports or some processor portals. Since 4853 covers so much ground, read the dispute details in the notice and don't rely on the code alone.

Matching Evidence to the Reason Code

The most common mistake in representment is sending the same evidence packet for every dispute. Issuers weigh evidence against the specific claim. Build your response around the category.

Fraud Codes

• Card-not-present: AVS and CVV match results, 3-D Secure authentication records, IP address and device data, customer account login history, and prior undisputed orders on the same card or account.
• Card-present: Proof the chip was read (or the card was tapped) rather than swiped or keyed. In-person fraud disputes often turn on how the card was accepted at the terminal.
• For both: Any communication showing the cardholder knew about the purchase, plus a clear billing descriptor.

Authentication can shift fraud liability away from you on eligible online transactions. Our guide to 3D Secure for online stores explains how to get that protection without adding much checkout friction.

Authorization Codes

• The approval code, date and amount from the original authorization
• For hotels, car rentals and travel bookings with incremental or delayed charges, records showing each authorization matched the final amount
• Proof the transaction wasn't forced through after a decline

Processing Error Codes

• Duplicate: Records showing two separate orders, such as different order numbers, items or timestamps, or proof one charge was already voided or refunded
• Incorrect amount: The signed receipt, invoice or checkout record showing the amount the customer agreed to
• Paid by other means: Evidence the customer did not also pay by cash, another card or a voucher for the same purchase

Consumer Dispute Codes

Consumer disputes vary the most by industry:

• E-commerce stores: Carrier tracking with a delivery scan to the address on the order, signature confirmation for higher-value shipments, product page screenshots showing the description at time of sale, and your return policy.
• Subscriptions and memberships: The sign-up page showing renewal terms, proof the customer accepted them, renewal reminders you sent, cancellation records, and login or usage after the disputed billing date. Renewal and cancellation rules vary by state, so review our automatic renewal laws compliance map and confirm requirements with a qualified professional.
• Travel and tourism: The booking confirmation, the cancellation and no-show terms the traveler accepted, supplier confirmations, and check-in or boarding records showing the service was used.
• Events and ticketing: Ticket scan records showing entry, the refund policy shown at purchase, and every customer notice about postponements, venue changes or refund windows. "Credit not processed" disputes often follow a postponed event, so log when and how customers were told their options.

A short written summary that ties each piece of evidence to the claim makes the issuer's review easier. Our chargeback rebuttal letter template gives you a starting structure.

Not every chargeback is worth fighting. If the customer is right, such as an order lost in transit or a refund your team never processed, accepting the dispute and fixing the cause usually makes more sense than a weak response. Refunding a legitimate complaint before it becomes a chargeback is generally better still.

Example: Responding to a 'Product Not Received' Dispute

This scenario is illustrative. It is not a real customer case.

An online store selling outdoor gear receives a Visa 13.1 (Merchandise/Services Not Received) dispute on an order shipped about three weeks earlier. Here is how the merchant works through it:

1. Read the notice. The code is a consumer dispute, not fraud, so the cardholder isn't denying they placed the order. Note the response deadline in the processor notice. Deadlines are strict and often short.
2. Pull the order record. Gather the order date, items, shipping method, and shipping and billing addresses.
3. Check tracking. The carrier shows a delivery scan to the shipping address, which matches the billing address that passed the AVS check.
4. Review customer contact. The help desk shows no message from the customer before the dispute, so they never asked about the package.
5. Build the packet: a one-page summary, the tracking record with the delivery scan, the order confirmation showing the address, the product page with the shipping timeline, and a note that the customer never contacted support.
6. Submit before the deadline, then record the outcome in the dispute log.

The response changes if the facts change. If tracking showed the package stuck in transit, or delivered to an address that differs from what the customer entered, the stronger move is to accept the chargeback, file a claim with the carrier, and review your shipping options.

Using Reason Code Trends to Prevent Future Chargebacks

A single chargeback tells you about one transaction. Twenty chargebacks sorted by reason code show you where your process is breaking. Keep a simple log with the date, network, reason code, category, product or service, sales channel and outcome.

Then look for patterns:

Trends also matter for your account standing. Processors and card networks watch dispute levels, and sustained high volumes can lead to reserves, monitoring programs or account review. Our guide to chargeback ratio thresholds explains how close is too close. Confirm the exact thresholds that apply to your account with your processor.

Next Steps

Reason codes stop being cryptic once you sort them into four groups. Fraud codes call for identity and authentication proof. Authorization and processing codes call for clean transaction records. Consumer dispute codes call for proof you delivered what you promised under policies the customer accepted. Log every code, review the patterns monthly, and fix the root causes behind them.

If disputes are part of daily life in your business, as they often are in subscriptions, travel and ticketing, your processing setup matters. MannyPay offers 3-D Secure authentication for online payments and merchant accounts for high-risk businesses. To talk through your dispute history and processing needs, request a free quote from MannyPay. A specialist will respond within one business day.

ME

About the author

MannyPay Editorial Team

Beyond the Swipe's editorial desk researches the publication's guides and news and cites its sources in every article. Articles reviewed by a named MannyPay editor carry that editor's byline.

This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.