What Discover Reason Code UA38 Means
Discover reason code UA38, titled Fraud — Other, is a catch-all fraud category used when the specific fraud mechanism does not fit within Discover's other UA fraud codes. Like NC (Not Classified) for non-fraud disputes, UA38 requires investigation to understand the actual underlying claim before a defense can be constructed.
UA38 disputes can involve any fraud channel — card-present, card-not-present, or hybrid scenarios. The defense strategy is entirely dependent on the actual transaction type and the specific fraud mechanism the cardholder has identified in their dispute narrative.
Never respond to UA38 with a generic evidence package. Request the complete dispute details from your acquirer, including the cardholder's narrative and any issuer notes. The actual fraud scenario determines the evidence strategy. Submitting the wrong evidence type is worse than submitting nothing.
Cross-Network Equivalent Codes
| Network | Code | Title | Notes |
|---|---|---|---|
| Discover | UA38 | Fraud – Other | This page |
| Visa | 10.4 | Other Fraud – Card Absent Environment | Visa catch-all fraud code |
| Mastercard | 4853 | Cardholder Dispute | Mastercard fraud code |
| Amex | F24 | No Cardmember Authorization | Amex fraud code |
Common Trigger Scenarios
- Emerging or novel fraud scenario. New fraud types that don't fit existing UA code definitions may be filed as UA38 while Discover evaluates whether to create a specific code.
- Hybrid channel fraud. Transactions involving multiple payment channels (e.g., in-person card presented but billing address used for delivery fraud) may be filed under UA38 if they don't fit a specific category.
- Fraud involving compromised credentials or account data. Account takeover scenarios that don't neatly fit CNP or card-present categories may be classified as UA38.
- Complex multi-transaction fraud schemes. Fraud involving multiple transactions or accounts as part of a coordinated scheme may be filed as UA38 when the mechanism spans multiple code categories.
Key Deadlines & Timeframes
| Milestone | Timeframe | Notes |
|---|---|---|
| Cardholder Filing Window | 120 days | From the transaction date |
| Merchant Response Window | 30 days | From Discover dispute notification; confirm with your processor for internal deadlines |
| Pre-Arbitration | 30 days | If Discover rejects representment, 30 days to escalate |
Evidence You Will Need
- Transaction-specific authentication data — For card-present transactions: EMV chip record; for CNP: 3DS authentication, AVS, CVV
- Complete dispute narrative from acquirer — Request the full dispute details including cardholder's specific claim before assembling evidence
- Device and session data — IP address, device fingerprint, geolocation for any CNP component of the disputed transaction
- Delivery documentation — Carrier tracking and delivery confirmation for any physical goods component
- Account activity and login history — Account access records showing the transaction was consistent with normal account activity patterns
Learn Exactly How to Package and Present This Evidence
The Fraud Defense Guide covers the complete evidence format for UA38 representments, how to structure your response letter, and when a dispute is better accepted than contested given your authentication data.
Learn exactly how to package and present this evidence →How Merchants Lose This Dispute
- Submitting a generic fraud defense package. UA38 requires investigation of the specific claim. A generic package covering every possible fraud type is less effective than a targeted response to the actual claimed scenario.
- Not requesting the dispute narrative. The cardholder's specific claim in a UA38 dispute is essential information. Not obtaining this before responding means building a defense without knowing what you're defending against.
- Ignoring UA38 because it seems unusual. The response window is 30 days regardless of how unusual the code is. Delay while investigating still costs response time.
- Treating UA38 as lower priority. UA38 is a full fraud chargeback with the same financial impact as any other UA code. Prioritize accordingly.
Get the Step-by-Step Winning Strategy
Our Fraud Defense Guide covers the complete UA38 representment structure and the cross-network approach for equivalent fraud codes across Visa, Mastercard, and Amex.
Get the step-by-step winning strategy →Response Framework Overview
- Obtain the full dispute narrative immediately. Contact your acquirer and request the complete dispute documentation including the cardholder's stated reason and any issuer notes.
- Identify the actual transaction type and fraud mechanism. Determine whether this is a card-present or CNP transaction and what specific fraud scenario the cardholder is describing.
- Assemble the appropriate evidence for the identified scenario. Once the fraud type is identified, apply the evidence strategy for that specific type: EMV data for card-present, 3DS/AVS/CVV for CNP.
- Respond within 30 days of the dispute notification. Do not let the investigation delay the response. If the fraud type cannot be determined quickly, submit whatever authentication data is available within the window.
Prevention Tips
- Maintain comprehensive transaction records. Given the unpredictable nature of UA38 disputes, maintaining detailed records for every transaction — regardless of channel — ensures evidence is available for whatever scenario arises.
- Implement 3DS, AVS, CVV, and EMV across all channels. Comprehensive authentication controls across all transaction types ensure evidence is available regardless of which fraud category a dispute falls under.
- Monitor for unusual dispute patterns. A cluster of UA38 disputes on similar transaction types may indicate an emerging fraud pattern that warrants investigation and specific preventive measures.
- Train staff to document unusual transaction circumstances. For card-present transactions with any unusual circumstances, documenting these in real time provides evidence for potentially unusual dispute scenarios.
Frequently Asked Questions
Why would Discover use UA38 instead of a specific code?
Discover uses UA38 when the dispute scenario doesn't match any specific fraud code definition, when the fraud type is under investigation, or when a new fraud type doesn't yet have a dedicated code. It's also used when the cardholder's claim spans multiple fraud categories.
Is UA38 harder or easier to win than specific fraud codes?
Generally comparable to other fraud codes (~10% win rate) but with added complexity: you must first determine what the actual claim is before you can defend against it. The investigation step adds time pressure within the 30-day response window.
What if I can't determine the specific fraud mechanism in UA38?
Submit the best available authentication evidence for the transaction type within the response window. For card-present: EMV data and signed receipt. For CNP: 3DS, AVS, CVV, device data. Explain in your response that you are presenting authentication evidence pending full fraud detail review.