Cardholder
Initiates the dispute by contacting their issuer, typically by phone, in-app, or via online banking. Provides transaction details and any evidence to support their claim.
Chargeback reason codes: the complete guide for issuing banks
When a cardholder contacts their bank saying "I didn't make this charge" or "I never got what I paid for," behind every disputed transaction is a reason code that carries implications for how the dispute gets resolved, who pays, and what evidence is needed.
Introduction
This guide is a complete reference: definitions for the chargeback codes most relevant to issuers, time limits, evidence requirements, the parties involved in every dispute, and best practices for managing each category.
Key takeaways:
- Visa organises codes into four categories: Fraud (10), Authorisation (11), Processing Errors (12), and Consumer Disputes (13).
- Mastercard uses an equivalent four-category structure with four-digit codes (e.g., 4837 No Cardholder Authorisation, 4853 Cardholder Dispute).
- Most codes carry a 120-day deadline from the transaction date, with some extending to 540 days for specific scenarios.
- The code dictates the evidence the issuer must gather to defend the chargeback through representment, pre-arbitration, and arbitration.
- Reading reason code data at portfolio level surfaces actionable patterns: fraud trends, merchant-specific problems, and customer-education gaps.
What are chargeback reason codes?
A chargeback reason code is a standardised identifier card networks use to classify why a transaction is being disputed. Each network maintains its own set:
- Visa uses dispute condition codes formatted as [category].[condition] (e.g., 10.4 is "Other Fraud, Card-Absent Environment" within category 10 (Fraud)). Visa's dispute condition codes are published in the Visa Core Rules and Visa Product and Service Rules.
- Mastercard uses four-digit chargeback reason codes (e.g., 4837 (No Cardholder Authorisation) or 4853 (Cardholder Dispute)). Mastercard's reason codes are published in the Mastercard Chargeback Guide.
The code determines the issuer's deadline to raise the dispute, the evidence required, and which party bears liability. Each payment network publishes their reason codes in their respective dispute rulebooks, updated multiple times per year through scheme bulletins.
A chargeback (Mastercard's term) or dispute (Visa's preferred label) happens when a cardholder questions a transaction on their statement. Maybe they don't recognise the charge, never received their order, or noticed they were billed twice. The reason code is the shorthand that captures the specific problem, and more importantly, determines who's responsible for making it right.
For issuing banks, these codes are your roadmap telling you:
- What evidence you need to gather: each code dictates the exact documentation that wins or loses the case.
- How much time you have to respond: deadlines vary by category, miss one and the dispute is gone, regardless of merit.
- Whether you have a strong case for shifting liability to the merchant: the code signals where the merchant's actions (or inactions) have already conceded liability.
- What patterns might be emerging across your portfolio: aggregated code data surfaces fraud trends, problem merchants, and product vulnerabilities.
Without standardised reason codes, every disputed transaction would require custom communication between banks worldwide. Instead, a code like "10.4" instantly tells everyone "this is a card-not-present fraud claim," triggering specific procedures and timelines.
The key players in every dispute
Before we dive into specific codes, let's clarify who does what when a dispute happens.
Issuer
The cardholder's bank. Investigates the claim, determines validity, and raises the chargeback with the card network on the cardholder's behalf. Bound by scheme rules and deadlines.
Acquirer
The merchant's bank or payment processor. Defends valid transactions on the merchant's behalf and manages any financial adjustments to the merchant's account.
Merchant
Provides evidence to the acquirer to prove the transaction was legitimate. They're often the ones who can resolve disputes fastest by issuing refunds directly.
Card Network
Operates the infrastructure for dispute resolution, defines the rules and reason codes, and makes binding decisions when disputes escalate to arbitration.
Visa dispute reason codes 101
Visa organises its dispute codes into four main categories, each addressing different types of problems.
Category 10: Fraud Disputes – Your first line of defence
Fraud disputes are triggered when cardholders deny making or authorising a transaction. These are often your most time-sensitive cases, and getting them right protects both your customers and your bottom line.
10.1 EMV Liability Shift Counterfeit Fraud
This applies when a counterfeit chip card is used at a terminal that should have read the chip but didn't. If you've invested in issuing EMV chip cards but the merchant hasn't upgraded their terminals, the liability shifts to them. It's a powerful incentive for merchants to adopt secure technology.
10.2 EMV Liability Shift Non-Counterfeit Fraud
Similar principle, but for lost, stolen, or never-received cards. If a PIN-preferring chip card is used at a terminal that can't process PINs properly, the merchant bears the liability. This protects you when merchants fail to use available security features.
10.3 Other Fraud – Card-Present Environment
Watch for patterns here. This code applies when merchants manually key in card numbers instead of using the chip or magnetic stripe. High volumes of 10.3 disputes from specific merchants often signal training issues or deliberate security bypasses.
10.4 Other Fraud – Card-Absent Environment
Your bread and butter for online, phone, and mail-order fraud. Success here depends on using tools like Address Verification Service (AVS), CVV2 verification, and 3D Secure during authorisation. When merchants provide "compelling evidence," you'll need to carefully review it with your cardholder before accepting liability.
10.5 Visa Fraud Monitoring Program
Your safety net. When Visa identifies a merchant with excessive fraud and you can't dispute under other conditions, this code lets you recover funds from systemically problematic merchants.
Category 11: Authorisation disputes – Keeping merchants honest
These disputes ensure merchants follow proper authorisation procedures. They're often your strongest cases because the rules are clear-cut.
11.1 Card recovery bulletin
Less common today, but still relevant for transactions below floor limits where merchants should have checked the Card recovery bulletin but didn't.
11.2 Declined authorisation
This is as straightforward as it gets. If you declined a transaction and the merchant forced it through anyway, they're fully liable. Monitor for these closely: they indicate serious merchant compliance issues.
11.3 No Authorisation/Late presentment
Now includes what used to be code 12.1. Covers missing authorisations, expired authorisations, and late-presented transactions.
Category 12: Processing errors – Getting the details right
These disputes fix technical mistakes in how transactions were processed. They're usually straightforward but require attention to detail.
12.2 Incorrect Transaction Code
When credits are processed as debits or vice versa.
12.3 Incorrect Currency
Dynamic Currency Conversion gone wrong.
12.4 Incorrect Account Number
Transaction posted to the wrong account.
12.5 Incorrect Amount
Simple math or data entry errors.
12.6 Duplicate Processing/Paid by Other Means
Double charges or alternate payment scenarios. For 12.6 disputes where cardholders paid another way, you'll need proof of the alternate payment. Educate your customers to keep those receipts.
12.7 Invalid Data
Wrong merchant category code or transaction date.
Category 13: Consumer disputes – Managing customer satisfaction
These are often your most complex cases, requiring detailed evidence and usually an attempt at direct merchant resolution first.
13.1 Merchandise/Services Not Received
Rising volumes from specific merchants can signal financial distress or operational problems. Require cardholders to attempt merchant resolution first, but watch for patterns.
13.2 Cancelled Recurring Transaction
Straightforward but common. Ensure you're educating cardholders about proper cancellation procedures.
13.3 Not as Described or Defective
May require neutral third-party opinions. Guide cardholders through evidence collection—photos, expert assessments, and documentation matter.
13.4 Counterfeit Merchandise
No return required, but starting April 2025, formal notification from an authority will be needed. Simplifies your process significantly.
13.5 Misrepresentation
Covers deceptive practices in timeshares, debt consolidation, tech support scams, and more. Watch for patterns by merchant category.
13.6 Credit Not Processed
When promised refunds don't appear. Usually easy to win, but causes significant customer frustration.
13.7 Cancelled Merchandise/Services
Focus on whether cancellation policies were clearly disclosed. Non-disclosure strengthens your case significantly.
13.9 Non-Receipt of Cash at ATM
High-priority customer service issue. Usually easily verified through ATM logs.
Mastercard chargeback reason codes 101
While Mastercard's system parallels Visa's, there are important distinctions you need to know.
Fraud-related chargebacks
4837 No Cardholder Authorisation
Similar to Visa's 10.4, but may have different evidence requirements.
4870/71 Chip Liability Shift
Matches Visa's EMV fraud principles, but be aware of regional timeframe differences.
Authorisation chargebacks
4808 Authorisation-Related
Comprehensive code covering missing, expired, or invalid authorisations with region-specific variations.
Processing errors
4834 Duplicate Processing
Nearly identical to Visa's approach.
4831 Transaction Amount Incorrect
Same concept, potentially different evidence requirements.
Consumer disputes
4853 Cardholder Dispute
Mastercard consolidates many scenarios under this broader category.
4850 Instalment Billing Dispute
Specific to instalment payment issues.
Visa vs. Mastercard: Quick comparison
Visa and Mastercard cover similar dispute scenarios under different code structures. The following side-by-side mapping shows the rough equivalents at a glance (note: evidence requirements and time limits can differ).
Fraud (card-present, EMV)
Counterfeit chip card used at a terminal that should have read the chip. Time limit (issuer): 120 days. Key difference: Visa and Mastercard align closely; Mastercard applies regional timeframe variations.
- Visa code: 10.1
- Mastercard code: 4870
Fraud (card-present, non-counterfeit)
Lost, stolen, or never-received chip card used at a non-PIN-capable terminal. Time limit (issuer): 120 days. Key difference: Mastercard 4871 has tighter PIN-handling requirements in some regions.
- Visa code: 10.2
- Mastercard code: 4871
Fraud (card-present, other)
Card details manually keyed in instead of read via chip or stripe. Time limit (issuer): 120 days. Key difference: Visa-only; Mastercard handles the same scenarios under 4837.
- Visa code: 10.3
- Mastercard code: –
Fraud (card-absent)
Card-not-present fraud when a cardholder denies an online, phone, or mail-order transaction. Time limit (issuer): 120 days. Key difference: Visa requires explicit compelling-evidence formats; Mastercard accepts a broader evidence set.
- Visa code: 10.4
- Mastercard code: 4837
Fraud monitoring
Recovery code for transactions tied to merchants in Visa's fraud monitoring program. Time limit (issuer): 120 days. Key difference: Visa-only; Mastercard manages equivalent recoveries through its Excessive Fraud Merchant program.
- Visa code: 10.5
- Mastercard code: –
Authorisation
Missing, declined, expired, or late-presented authorisations. Time limit (issuer): 75–120 days. Key difference: Visa splits this into three specific codes; Mastercard consolidates all scenarios under 4808.
- Visa code: 11.1 / 11.2 / 11.3
- Mastercard code: 4808
Processing – amount
Transaction posted for the wrong amount. Time limit (issuer): 120 days. Key difference: Functionally identical; Mastercard requires the disputed amount to be quantified at filing.
- Visa code: 12.5
- Mastercard code: 4831
Processing – duplicate
Same transaction processed more than once, or paid through another method. Time limit (issuer): 120 days. Key difference: Visa 12.6 explicitly covers "paid by other means"; Mastercard 4834 narrows to duplicates only.
- Visa code: 12.6
- Mastercard code: 4834
Consumer – not received
Goods or services were not delivered or rendered. Time limit (issuer): 120 days. Key difference: Visa uses a dedicated code; Mastercard routes through container code 4853.
- Visa code: 13.1
- Mastercard code: 4853
Consumer – recurring
Merchant continued to bill after the cardholder cancelled a subscription or recurring service. Time limit (issuer): 120 days. Key difference: Visa isolates recurring billing as its own code; Mastercard handles it as a 4853 sub-scenario.
- Visa code: 13.2
- Mastercard code: 4853
Consumer – defective
Goods or services received were defective or not as described. Time limit (issuer): 120 days. Key difference: Visa may require third-party expert evidence; Mastercard relies on cardholder statement plus merchant response.
- Visa code: 13.3
- Mastercard code: 4853
Consumer – credit not processed
Promised refund or credit never appeared on the cardholder's account. Time limit (issuer): 120 days. Key difference: Visa requires proof the merchant agreed to the credit; Mastercard accepts broader cardholder evidence under 4853.
- Visa code: 13.6
- Mastercard code: 4853
Consumer – instalment
Dispute over the terms or processing of an instalment payment. Time limit (issuer): 120 days. Key difference: Mastercard-only; Visa handles equivalent scenarios under 13.2 or 13.6 depending on the issue.
- Visa code: –
- Mastercard code: 4850
Time limits: Your critical deadlines
Missing a deadline means losing the dispute, regardless of merit. Here's what you need to remember.
Issuer time limits for raising a chargeback
Missing the deadline means losing the chargeback regardless of merit. Deadlines run from the transaction date unless the reason code specifies otherwise (e.g., delivery date for goods).
Visa disputes:
- Fraud (Category 10): 120 days (from transaction date)
- Authorisation (Category 11): 75-120 days (varies by specific code)
- Processing Errors (Category 12): 75-120 days
- Consumer Disputes (Category 13): 120 days, some up to 540 (extended windows for delayed delivery, recurring services)
Mastercard chargebacks:
- Fraud: 120 days (from transaction date)
- Authorisation: 90 days (varies by specific code)
- Processing Errors: 120 days
- Consumer Disputes: 120 days, some up to 540 (extended windows for delayed delivery, recurring services)
If the issuer misses the chargeback deadline, the dispute is forfeited regardless of merit and the issuer can't recover the funds through the chargeback process. The loss falls to either the issuer or the cardholder depending on the cardholder agreement.
Turning reason codes into strategic intelligence
Here's where you move beyond just processing disputes to actually improving your portfolio.
→ Proactive prevention
Use your dispute data to identify vulnerabilities. High 10.4 volumes? Time to enhance your fraud detection capabilities. Seeing lots of 13.2 recurring billing disputes? Consider improving your payment processing systems to better handle cancellations.
→ Merchant intelligence
Share insights with your acquirer partners. When you identify problematic merchant behaviours, collaborative solutions benefit everyone.
→ Customer education
Use dispute trends to create targeted education. If you're seeing lots of DCC-related disputes (12.3), teach cardholders how to spot and avoid unwanted currency conversions.
Best practices for issuing banks
Here's where you move beyond just processing disputes to actually improving your portfolio.
→ For fraud disputes:
- Report to Visa/Mastercard fraud databases within required timeframes
- Maintain comprehensive authorisation logs
- Review compelling evidence thoroughly before accepting liability
- Use Account Status Anti-Fraud Service (ASAF) and similar tools to list compromised accounts
→ For authorisation disputes:
- Train staff on MCC-specific variance allowances
- Monitor for forced transactions immediately
- Verify all authorisation records before disputing
→ For processing errors:
- Ask detailed questions during intake to identify the exact error
- Cross-reference internal records meticulously
- Educate cardholders about keeping receipts and documentation
→ For consumer disputes:
- Enforce merchant resolution attempts where required
- Guide cardholders through evidence collection
- Document merchandise disposition carefully
Where are chargeback reason codes heading?
Staying current means more than memorising codes. It means understanding the strategic implications of dispute trends, investing in the right technology, and building processes that protect your cardholders while managing operational costs.
Reason code structures are simplifying, not expanding:
Reason code structures are simplifying, not expanding. The payment networks have been consolidating codes into high-level categories that cover many scenarios at once. The trend is fewer, broader codes interpreted contextually, which raises the importance of evidence quality and consistent issuer judgement.
At the same time, the underlying dispute landscape is shifting. EMV adoption has pushed fraud online, generating more sophisticated card-not-present schemes. Tokenisation and biometric authentication are creating new dispute scenarios. Consumer protection regulation is expanding globally.
The combined effect is three shifts in how issuers should approach disputes:
- From code memorisation to evidence quality: Knowing the code is necessary but no longer sufficient. The win rate depends on what documentation the issuer brings to the case.
- From rule-based decisioning to judgement-based decisioning: When a single code covers multiple scenarios, automation has to make a judgement call. This is where agentic dispute resolution starts to matter (see our dispute management guide).
- From per-code best practices to portfolio-level intelligence: As individual codes lose specificity, the value moves to aggregate pattern detection across the dispute portfolio.
To act on these shifts, issuers can take four steps:
- Audit your current dispute processes against reason codes: a documented map of which codes your team handles well and which it doesn't.
- Analyse your dispute data for patterns: an ongoing review of which codes appear most frequently, by merchant category and channel.
- Invest in training for your dispute team: deep knowledge of reason codes and the evidence requirements behind them pays dividends as codes broaden.
- Enhance your technology stack: automation absorbs routine cases and applies consistent judgement where codes cover multiple scenarios, freeing analysts for genuinely complex disputes.
Understanding chargeback and dispute reason codes is not only about winning individual cases, but also about building a stronger, more resilient card portfolio. When you master these codes, you're protecting your bottom line while also protecting the trust your cardholders place in you every time they use their card. Every dispute is an opportunity to demonstrate your value as an issuer. Make sure you're equipped to make the most of it.
How does automation change reason code handling?
Great dispute management happens when banks know the codes and have the right tools. Consider how automated dispute management systems can streamline your processes. Rivero's Amiko is built for issuers running this workflow at scale. It acts as an agentic dispute platform that guides cardholders through intelligent intake, automates filings and case-state alerts in line with Visa and Mastercard rules, uses dispute data and patterns to guide agents to better decisions, and integrates directly with Visa Resolve Online (VROL) and Mastercom.
