Visa Chargeback Reason Codes: Every Category Explained
Visa chargeback reason codes explained by category: what each dispute type claims, the evidence that answers it and how to prevent it.
Photo: Pixabay
On this page 8 sections
Key takeaways
- Visa dispute reason codes fall into four families: fraud, authorization, processing errors and consumer disputes.
- The reason code tells you what the issuer is claiming, so match your evidence to that claim instead of sending a generic rebuttal.
- Many chargebacks can be prevented upstream through chip reads, authentication, correct authorizations, clean batching and clear refund policies.
- Visa revises its dispute rules, so look up your exact code, deadline and evidence requirements in current Visa guidance and with your processor.
When a Visa chargeback hits your account, the reason code tells you what the cardholder's bank is claiming and what you need to prove. This guide organizes Visa chargeback reason codes into their four families: fraud, authorization, processing errors and consumer disputes. For each type of dispute you'll learn what usually triggers it, what evidence tends to answer it and which habit prevents it. It applies whether you sell online, at a counter, at a bar or at a hotel front desk.
If you're new to the dispute process, start with our walkthrough of the full chargeback dispute lifecycle, then use this page as a reference.
A note on code numbers: Your dispute notice will show a specific numeric code and name. This guide describes each dispute type by what it claims rather than reprinting Visa's code list, because Visa revises code names, conditions, time limits and evidence requirements over time. Look up the exact code on your notice in Visa's current published guidance, and confirm the details with your processor before you respond.
How Visa Chargeback Reason Codes Are Organized
Visa assigns every dispute a reason code, and those codes fall into four broad families. Knowing the family tells you, before you read anything else, what kind of proof will matter.
| Family | What the Issuer Is Claiming | Where Merchants Are Most Exposed |
|---|---|---|
| Fraud | The cardholder didn't authorize the transaction | Online and phone orders, keyed entries, in-person sales where the chip wasn't read |
| Authorization | The sale lacked a valid approval for the amount charged | Bar tabs, hotel stays, offline sales, forced or re-run transactions |
| Processing Errors | Something went wrong in how the sale was entered or settled | Late batches, wrong amounts, duplicate charges |
| Consumer Disputes | The cardholder made the purchase but has a problem with it | Shipping, cancellations, refunds, subscriptions, product quality |
Response windows are short. Your processor sets the deadline you have to meet, and it is usually tighter than the cardholder's window to file. Open every dispute notice the day it arrives.
Fraud Codes: What Triggers Them and How to Respond
Fraud codes mean the cardholder or their bank says the purchase wasn't authorized. Some cases are true third-party fraud, such as a stolen card number. Others are friendly fraud, where the cardholder made the purchase but disputes it anyway.
| Dispute Type | Common Trigger | Best Evidence | Prevention |
|---|---|---|---|
| Counterfeit card used in person | A chip card was swiped or keyed instead of read by chip | Terminal data showing the chip was read | Read the chip on every card-present sale |
| Lost or stolen card used in person | A stolen card was used without strong cardholder verification | Records of chip and PIN or other verification | Use current, PIN-capable terminals |
| Other in-person fraud | The cardholder denies a counter sale, often one that was keyed | Chip read data, signed receipt, ID check notes | Avoid keying cards at the counter |
| Card-not-present fraud | The cardholder denies an online, phone or mail order | Authentication results, AVS and CVV matches, delivery and account history | 3-D Secure, AVS and CVV checks |
Card-Not-Present Fraud Claims
For e-commerce stores and businesses that take card numbers over the phone, the card-not-present fraud claim is the one you'll face most directly. The cardholder's message is simple: "I didn't make this purchase."
Evidence that can help:
- 3-D Secure results. Successful authentication may shift fraud liability to the issuer for eligible transactions. Confirm eligibility for your transactions with your processor.
- AVS and CVV match results from the authorization
- IP address, device data and login history for the customer's account
- Proof of delivery to the cardholder's billing address or a verified shipping address
- Prior undisputed purchases by the same customer. Ask your processor whether this history can be submitted for your dispute and what form it needs to take.
Prevention starts with authentication. Our guide to 3D Secure for online stores explains how to add it without hurting conversion, and MannyPay supports 3-D Secure authentication for card-not-present payments.
Keyed Transactions Deserve Special Attention
When a customer is standing in front of you but you key the card number because the reader failed, the sale loses the chip data that helps you defend it. That can make an in-person fraud dispute harder to win. Ask your processor how entry method affects your liability.
If keyed entry is becoming routine at a register or front desk, fix or replace the terminal. Our explainer on card-present vs. card-not-present rules covers why keyed sales are treated differently.
Authorization Codes
Authorization disputes claim the transaction didn't carry a valid approval for the amount charged. These cases usually come down to what your terminal or POS logged.
| Dispute Type | Common Trigger | Best Evidence | Prevention |
|---|---|---|---|
| Card flagged for recovery | The card was on a list of cards to be recovered, and the sale wasn't properly authorized | A valid authorization record | Authorize every transaction |
| Declined authorization | A sale was completed after a decline, often by forcing it through | Proof the approval was valid | Never force or re-run a declined card |
| No authorization | No approval was obtained, or the final amount exceeded what was approved | An authorization covering the full amount | Re-authorize when totals rise |
These disputes hit restaurants and hotels hardest because the final amount is often unknown when the card is first run:
- Bars and restaurants: A tab that grows well past the original hold can lead to a no-authorization claim. Our guide to bar tab preauthorization and closing tabs safely walks through the setup.
- Hotels and lodging: Room charges, incidentals, minibar items and late checkout fees can push the folio past the amount approved at check-in. Ask your processor whether your setup supports incremental authorizations during a stay. For background, read how credit card authorization holds work.
- Any business using offline mode: Sales captured while a terminal was offline may not have a live approval. Process them as soon as connectivity returns.
Processing Error Codes
Processing error disputes claim a mistake in how the transaction was entered, batched or settled. Because they come from your own procedures, they are often the most preventable.
| Dispute Type | Common Trigger | Best Evidence | Prevention |
|---|---|---|---|
| Late presentment | The batch settled later than network time limits allow | Proof of timely settlement | Close batches daily |
| Incorrect transaction type | A refund was run as a sale, or the reverse | Corrected transaction record | Train staff on refund workflows |
| Incorrect currency | The sale was charged in a currency other than the one agreed | Receipt showing the agreed currency | Check currency settings |
| Incorrect account number | The charge posted to the wrong card | Card data captured at the sale | Avoid manual entry |
| Incorrect amount | The amount charged differs from the receipt | Signed receipt or itemized invoice | Reconcile tips and adjustments |
| Duplicate processing | The same sale was charged twice | Proof the charges were separate purchases | Void, don't re-run |
| Paid by other means | The customer says they paid with cash, check or another card | Records showing no alternate payment | Match payments to invoices |
| Invalid data | Authorization data was incorrect or incomplete | A correct authorization record | Keep terminal software current |
Industry patterns to watch:
- Restaurants: A tip adjustment that doesn't match the signed slip is a classic incorrect-amount trigger. So is a server who re-runs a card after an apparent timeout and creates a duplicate charge.
- Retail: A cashier who rings a return as a sale creates an incorrect-transaction-type dispute.
- Hotels: A guest who prepaid through a booking channel and was charged again at checkout can file a paid-by-other-means claim.
Settlement timing ties directly to late-presentment disputes. If you're unsure how your batches flow, see how batching affects credit card deposits.
Consumer Dispute Codes
Consumer disputes cover the widest range of situations. The cardholder agrees they made the purchase but says something went wrong with it. Your documentation and written policies decide most of these cases.
| Dispute Type | Common Trigger | Best Evidence | Prevention |
|---|---|---|---|
| Not received | The item never arrived or the service wasn't provided | Delivery confirmation, check-in records, signed work orders | Ship with tracking and confirm service dates |
| Cancelled recurring charge | The customer was billed after cancelling a subscription | Terms accepted at signup, records showing no cancellation request | Easy cancellation and renewal reminders |
| Not as described or defective | The item differs from the listing or arrived damaged | Product photos, listing copy, records of return offers | Accurate descriptions |
| Counterfeit goods | The customer says the goods are fake | Supplier invoices, authenticity documentation | Buy from authorized suppliers |
| Misrepresentation | The customer says the offer or terms were misleading | Clearly disclosed terms the customer accepted | Plain-language terms at checkout |
| Credit not processed | A promised refund never posted | Refund record, or a policy showing no refund was owed | Process refunds promptly |
| Cancelled merchandise or services | The customer cancelled but was still charged | Cancellation policy and proof the customer accepted it | Show policies before payment |
Not-Received Disputes Beyond E-Commerce
The not-received claim is familiar to online stores, but it reaches other businesses too. A hotel guest may say the room wasn't provided as booked. A restaurant customer may say a delivery order never showed up.
Strong evidence includes:
- Carrier tracking showing delivery to the address the customer provided, with signature confirmation for higher-value orders
- Customer emails or messages acknowledging receipt
- For services: check-in records, folios, signed work orders or reservation logs
- For digital goods: download or login records tied to the customer's account
Hotel and Restaurant Cancellation Disputes
Cancellation disputes are where lodging businesses and restaurants that take reservation deposits win or lose on paperwork. If your cancellation or no-show policy wasn't clearly shown and accepted at booking, the dispute is hard to fight. Display the policy before payment, repeat it in the confirmation email and keep a record that the guest agreed to it.
Which Visa Dispute Reason Codes Are Most Winnable
Every dispute turns on its own facts, and outcomes are never guaranteed. Still, some patterns hold across most Visa dispute reason codes.
Often winnable with good records:
- Not-received claims when you have delivery confirmation to the cardholder's address
- Credit-not-processed claims when the refund was already issued or your policy didn't promise one
- Duplicate-processing claims when the two charges were genuinely separate purchases
- Cancellation claims when the customer accepted a clearly disclosed policy
- Card-not-present fraud claims when the order carried successful authentication or strong account history
Often hard to win:
- Authorization claims when no valid approval covered the full amount
- Late-presentment claims when the batch really did settle late
- In-person fraud claims when the chip wasn't read
- Not-as-described claims when your listing didn't match what shipped
When you have a case worth fighting, organize the evidence around the specific reason code. Our chargeback rebuttal letter template shows how to structure a response. If a refund costs less than the time and fees of a dispute, accepting the chargeback can be a reasonable business decision.
A Quick Response Checklist
- Read the reason code on your notice and look up its current definition.
- Pull the transaction record: authorization code, entry method, amount and settlement date.
- Gather only the evidence that answers the specific claim.
- Write a short, factual summary that ties each piece of evidence to the claim.
- Submit before your processor's deadline, and log the outcome so you can spot patterns.
Where to Find Visa's Current Official Rules
Visa publishes its operating rules and merchant dispute guidance on its website. These documents define each reason code, the conditions that apply and the remedies available. They are long and technical, and they change, so make sure you're reading the current edition.
For any live dispute, your processor or acquiring bank is the practical source of truth. They see the exact code, the deadline and the evidence formats the issuer will accept. When you evaluate a merchant service provider, ask how disputes are reported to you, how much time you'll have to respond and what support you'll get.
This article is general information, not legal advice. For questions about card network rules or your contractual obligations, consult your processor and a qualified professional.
Next Steps
Chargebacks are easier to prevent than to win. Read the chip on every in-person card, authenticate card-not-present orders, authorize the full amount, close batches daily and publish clear refund and cancellation policies.
If disputes keep tracing back to keyed entries or aging equipment, it may be time for modern smart terminals. MannyPay offers payment processing, POS systems and terminals, online gateways and merchant accounts for online, retail, restaurant and lodging businesses. To review your setup, request a free quote from MannyPay, and a specialist will respond within one business day.
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.
