Pre-Dispute Alert Reason Codes
This comprehensive reference guide provides detailed information about chargeback alert reason codes across major card networks. Understanding these codes is essential for merchants to quickly assess dispute risks, prioritize responses, and implement effective prevention strategies.
Usage Guide
This document serves as a detailed reference for specific reason codes. For response strategies and priority guidelines, see Pre-Dispute Notification.
Card Network Comparison
| Feature | VISA | MasterCard | Discover |
|---|---|---|---|
| Code Format | Hierarchical numeric (10.1, 11.2) | Mixed alphanumeric (FR4, C02, 37) | Primarily alphabetic (UA01, RG) |
| Organization | 4 main categories (10-13) | Series-based (FR, C, P, R + numeric) | Function-based groups |
| Fraud Indicators | 10.x series | FR series + 37 | UA series |
| Common Codes | 10.4, 13.1, 13.2 | C02, C08, FR4 | UA02, RG, AA |
| Complexity | Systematic hierarchy | Multiple classification systems | Descriptive abbreviations |
Detailed Reason Codes by Network
VISA Code System Overview
VISA employs a hierarchical numeric system with clear categorical organization, making it the most structured approach among major card networks.
Key Characteristics:
- Systematic Organization: 4 main categories (10-13) with decimal subcategories
- Clear Hierarchy: Easy to identify dispute type from code structure
- Wide Coverage: Comprehensive coverage of fraud, authorization, processing, and consumer issues
- Global Standard: Consistent worldwide implementation
Most Critical Codes:
10.4- Card-absent fraud (highest volume)13.1- Merchandise/services not received13.2- Cancelled recurring transactions
| Code | Description |
|---|---|
0 | Other / Unspecified |
10 | Fraud Category |
10.1 | EMV Liability Shift Counterfeit Fraud |
10.2 | EMV Liability Shift Non-Counterfeit Fraud |
10.3 | Other Fraud-Card Present Environment |
10.4 | Other Fraud-Card Absent Environment |
10.5 | Visa Fraud Monitoring Program |
11 | Authorization Category |
11.1 | Card Recovery Bulletin |
11.2 | Declined Authorization |
11.3 | No Authorization |
12 | Processing Errors Category |
12.1 | Late Presentment |
12.2 | Incorrect Transaction Code |
12.3 | Incorrect Currency |
12.4 | Incorrect Account Number |
12.5 | Incorrect Amount |
12.6 | Duplicate Processing/Paid by Other Means |
12.6.1 | Duplicate Processing |
12.6.2 | Paid by Other Means |
12.7 | Invalid Data |
13 | Consumer Disputes Category |
13.1 | Merchandise/Services Not Received |
13.2 | Cancelled Recurring Transaction |
13.3 | Not as Described or Defective Merchandise/Services |
13.4 | Counterfeit Merchandise |
13.5 | Misrepresentation |
13.6 | Credit Not Processed |
13.7 | Cancelled Merchandise/Services |
13.8 | Original Credit Transaction Not Accepted |
13.9 | Non-Receipt of Cash or Load Transaction Value |
30 | Service Not Provided or Merchandise Not Received |
41 | Cancelled Recurring Transaction |
53 | Not as Described or Defective Merchandise |
57 | Fraudulent Multiple Transactions |
60 | Requested Copy Illegible or Invalid |
71 | Declined Authorization |
72 | No Authorization |
73 | Expired Card |
74 | Late Presentment |
75 | Cardholder Does Not Recognize Transaction |
76 | Incorrect Currency or Transaction Code or Domestic Processing Violation |
77 | Non-Matching Account Number |
79 | Requested Transaction Information Not Received |
80 | Incorrect Transaction Amount or Account Number |
82 | Duplicate Processing |
83 | Fraudulent Transaction |
85 | Credit Not Processed |
86 | Paid by Other Means |
Advanced Code Analysis
Code Usage Patterns and Trends
Understanding how different reason codes manifest in real-world scenarios helps merchants prioritize their prevention efforts:
High-Volume Codes (Most Frequent)
- VISA
10.4(Card-absent fraud) - ~25% of all VISA alerts - VISA
13.1(Merchandise not received) - ~20% of consumer disputes - MasterCard
C02(Credit not processed) - ~30% of MasterCard service disputes - Discover
UA02(CNP fraud) - ~40% of Discover fraud alerts
High-Impact Codes (Highest Risk)
- MasterCard
FR4(Immediate chargeback) - Bypass dispute resolution - VISA
10.1(EMV liability shift) - Significant liability exposure - Discover
UA01(Card-present fraud) - Terminal security issues
Cross-Network Code Correlation
Many dispute scenarios have equivalent codes across different networks:
| Dispute Type | VISA | MasterCard | Discover |
|---|---|---|---|
| Card-Not-Present Fraud | 10.4 | 37, FR4 | UA02 |
| Goods Not Received | 13.1 | C08, 55 | RG |
| Credit Not Processed | 13.6 | C02, 60 | RN2 |
| Cancelled Recurring | 13.2 | C28, 41 | AP |
| Authorization Issues | 11.2, 11.3 | 8, 42 | AT |
Industry-Specific Code Patterns
Different merchant categories see distinct reason code distributions:
E-Commerce & Digital Goods
Common Codes: VISA 10.4, 13.1; MasterCard C02, C08; Discover UA02, RG
Prevention Focus: Fraud screening, delivery confirmation, customer communication
Subscription Services
Common Codes: VISA 13.2; MasterCard C28; Discover AP
Prevention Focus: Clear billing descriptors, cancellation policies, proactive communication
Travel & Hospitality
Common Codes: VISA 13.7; MasterCard C05; Discover CR
Prevention Focus: Flexible cancellation policies, clear terms, weather/emergency protocols
Seasonal and Market Variations
Reason code patterns often vary by:
- Holiday Seasons: Increased
13.1(non-receipt) due to shipping delays - Economic Conditions: Higher fraud codes during economic stress
- Regulatory Changes: Shifts in authorization-related codes
- Technology Updates: Changes in EMV and fraud detection patterns
Best Practices for Chargeback Prevention
Prevention Strategies
- Monitor high-risk codes: Pay special attention to fraud-related reason codes
- Improve authorization processes: Ensure proper authorization for all transactions
- Enhance customer communication: Clear billing descriptors and responsive support
- Maintain transaction records: Keep detailed documentation for dispute resolution
- Implement fraud detection: Use advanced fraud screening tools
Integration with Onerway Services
When using Onerway's chargeback alert services, these reason codes will be provided in webhook notifications and API responses to help you quickly identify the nature of potential disputes and take appropriate action.
For more information about implementing chargeback alert handling, see: