Chargeback Reason Code
Alphanumeric code indicating why cardholder disputed transaction (fraud, product not received, etc.). Critical for representment strategy.
Overview
What is Chargeback Reason Code?
Chargeback reason codes are standardized alphanumeric identifiers assigned by card networks (Visa, Mastercard, Amex, Discover) that indicate why a cardholder disputed a transaction. Each code represents a specific dispute category - from fraud claims to product delivery issues to processing errors - and determines what evidence merchants must provide to win the chargeback dispute. For high-risk merchants, analyzing reason code patterns is essential for identifying whether chargebacks stem from fraud (requiring better fraud screening), friendly fraud (requiring stronger customer authentication and policies), or operational issues (requiring fulfillment improvements).
Major reason code categories include: Fraud (10.4 for Visa, 4837 for Mastercard: cardholder claims unauthorized transaction), Authorization Issues (11.1/4831: transaction processed without authorization or after authorization expired), Point-of-Interaction Errors (12.1/4834: duplicate processing, incorrect amount charged), Consumer Disputes (13.1-13.7 for Visa, 4853-4855 for Mastercard: product not received, not as described, services cancelled), and Processing Errors (12.6/4842: late presentment, incorrect currency). Each category has 10-15 specific sub-codes with precise definitions.
Reason code analysis drives prevention strategies. If 65% of your chargebacks are Code 10.4 (fraud) but you know the transactions were legitimate, that's friendly fraud - customers falsely claiming they didn't authorize purchases. Solution: implement 3D Secure authentication, maintain detailed transaction logs, collect delivery signatures. If 50% are Code 13.3 (product not as described), your marketing claims don't match product reality - fraud tools won't help, you need better quality control and advertising compliance. Merchants who implement blanket "chargeback prevention" without analyzing reason codes waste resources solving wrong problems.
Representment requirements vary dramatically by code. Fraud chargebacks (10.4/4837) require: AVS/CVV match evidence, 3D Secure authentication logs, IP address and device fingerprint data, delivery confirmation with signature, customer communication showing they received product. Consumer dispute chargebacks (13.1/4853) require: detailed product descriptions matching marketing, shipping tracking showing delivery, customer service records demonstrating resolution attempts, terms of service acceptance records, refund policy disclosures. Using wrong evidence for the reason code results in automatic representment loss.
In depth
Everything you need to know.
When a cardholder disputes a transaction with their issuing bank, the bank assigns a reason code from the card network's standardized list. Visa uses numeric codes (10.1-13.9), Mastercard uses alphanumeric codes (4802-4999), Amex has proprietary codes (A01-P23), and Discover mirrors Visa's coding structure. The issuer selects the code based on the cardholder's complaint: "I didn't make this purchase" triggers fraud codes (10.4/4837), "product never arrived" triggers 13.1/4855, "quality doesn't match description" triggers 13.3/4853.
Once assigned, the reason code determines the representment process. Each code has specific time limits (7-45 days for merchant response), evidence requirements, and liability rules. For example, Code 10.4 (fraud) requires you to prove the cardholder authorized the transaction through 3D Secure logs, device fingerprinting, IP address data, delivery signatures, and communications. Code 13.1 (product not received) requires shipping tracking showing delivery to cardholder's address, signature confirmation for high-value items, and proof the address was verified at purchase.
Your PSP provides reason codes in chargeback notifications - typically via email and dashboard alerts. The notification includes: original transaction ID, chargeback amount, reason code, cardholder's dispute description (often vague like "fraud" or "did not receive"), response deadline, and evidence requirements. You have 7-21 days (code-dependent) to compile matching evidence and submit representment through your PSP's portal.
Reason code analysis is the difference between wasting money fighting unwinnable chargebacks and recovering $20K-100K annually through strategic representment. Merchants who fight all chargebacks indiscriminately win only 15-25% due to poor evidence matching. Merchants who analyze codes and target high-win scenarios (fraud with strong authentication, not-received with delivery proof) win 40-55%, doubling recovery rates while reducing wasted effort.
Prevention strategies depend entirely on reason codes. A merchant with 70% fraud chargebacks (10.4) needs 3D Secure authentication, AVS/CVV verification, and device fingerprinting - not better customer service. A merchant with 60% not-as-described chargebacks (13.3) needs product quality improvements and accurate marketing - fraud tools won't help. Without reason code analysis, merchants implement expensive fraud solutions that don't address actual chargeback drivers, wasting $10K-50K annually.
Illustrative example — not a specific client engagement.
- A $4M supplement merchant analyzed codes and found 68% were Code 13.3 (not as described). Root cause: exaggerated before/after photos in ads. After updating marketing to realistic expectations, not-as-described chargebacks dropped 54%, reducing rate from 1.8% to 1.0%.
- An online course platform had 58% Code 10.4 (fraud) but knew transactions were legitimate - students claimed purchases unauthorized after completing courses. Implementing 3D Secure with usage tracking reduced fraud chargebacks 62%, improving rate from 1.6% to 0.9%.
- A gaming merchant segmented codes by traffic source and found affiliate X generated 85% Code 10.4 fraud while organic showed 12% fraud. Cutting that affiliate reduced fraud chargebacks $28K annually while losing only $8K in legitimate revenue.
- Implement automated tracking dashboard showing monthly distribution, win rates by code, and 6-12 month trends
- Segment analysis by product SKU, traffic source, and customer segment to identify specific drivers
- Create code-specific templates: fraud includes 3DS logs, service includes tracking and communications
- Set thresholds: if any code exceeds 40% of total, launch dedicated prevention initiative
- Target win rates by code: 60%+ on fraud with 3DS, 40%+ on not-received with tracking, 20-30% on not-as-described
- Monthly reviews with operations and marketing teams - collaborative problem-solving based on patterns
- Fighting all chargebacks with generic evidence instead of customizing by reason code - automatic losses on 70%+ cases
- Not tracking reason code distribution over time - missing fraud spikes from 20% to 60% after marketing changes
- Using fraud tools when 75% of chargebacks are service disputes (not-received, not-as-described) - wrong solution
- Ignoring sub-categories - treating all "not received" chargebacks identically when different codes require different evidence
- Not segmenting by product or channel - missing that specific products drive specific dispute types
- Relying solely on codes without reading descriptions - codes are standardized, descriptions reveal actual issues
Keep exploring
Related terms
Put this to work
for your business.
MIDs structures high-risk acquiring across 30+ banks — smart routing, fraud and chargeback control built in. Tell us your category and volume and we'll build the setup around it.