What Discover Reason Code UA99 Means
Discover reason code UA99, titled Fraud — Miscellaneous, is a residual fraud category for dispute scenarios that do not fit within Discover's other UA fraud codes. It functions similarly to UA38 (Fraud — Other) and NC (Not Classified): the cardholder has filed a fraud dispute, but the specific mechanism does not align with a standard Discover fraud category.
UA99 disputes require the same response urgency as any other fraud code — the 30-day response window applies regardless of the code's miscellaneous nature. The specific defense strategy is determined by the actual transaction type and fraud claim.
UA99 has the same financial impact and response deadline as any specific fraud code. The miscellaneous designation means the fraud type is unspecified, not that the dispute is minor. Request the full dispute narrative immediately and treat UA99 with the same urgency as UA01 or UA02.
Cross-Network Equivalent Codes
| Network | Code | Title | Notes |
|---|---|---|---|
| Discover | UA99 | Fraud – Miscellaneous | 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
- Complex fraud schemes spanning multiple categories. Fraud involving multiple transaction types, channels, or mechanisms that don't fit cleanly into a single UA category may be filed as UA99.
- New fraud vectors not yet categorized. Emerging fraud methods that don't match existing code definitions may temporarily be filed as UA99 pending code updates.
- Issuer system limitations. In some cases, UA99 is used when an issuer's system cannot precisely categorize the fraud type from the cardholder's dispute submission.
- Investigation pending specific classification. When the cardholder's fraud claim requires investigation before a specific code can be assigned, UA99 may serve as an interim classification.
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
- EMV chip transaction record — For card-present: complete electronic authentication record with cryptographic data
- 3D Secure authentication record — For CNP: 3DS authentication result including CAVV and ECI values
- AVS and CVV match records — Authorization response data confirming billing address and CVV match
- Device fingerprint and IP address — Session data from any CNP component of the transaction
- Delivery confirmation — Carrier tracking and delivery records for physical goods
- Account activity and authorization records — Records showing the transaction was consistent with the account holder's normal patterns
Learn Exactly How to Package and Present This Evidence
The Fraud Defense Guide covers the complete evidence format for UA99 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
- Treating UA99 as lower priority due to 'miscellaneous' label. The 30-day response window is the same. Low prioritization leads to missed deadlines and automatic losses.
- Responding without investigating the actual claim. Submitting a generic fraud package without understanding the specific dispute claim is less effective than a targeted response.
- Not requesting dispute details from acquirer. The acquirer may have access to the cardholder's dispute narrative that provides critical context for the specific fraud claim.
- Failing to preserve transaction data while investigating. Investigation should not delay data preservation. Secure all transaction records, terminal data, and authentication logs immediately.
Get the Step-by-Step Winning Strategy
Our Fraud Defense Guide covers the complete UA99 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
- Request complete dispute details from your acquirer immediately. Obtain the full dispute documentation including cardholder narrative and any issuer notes before building your response.
- Identify the transaction type and likely fraud mechanism. Determine card-present vs. CNP and the most likely fraud scenario based on the dispute details.
- Assemble targeted evidence for the identified scenario. Build the response around the specific identified fraud type, leading with the most probative authentication evidence.
- Submit comprehensive supporting evidence. Include delivery confirmation, account history, and any other supporting data that establishes the legitimacy of the transaction.
Prevention Tips
- Maintain comprehensive transaction records across all channels. Because UA99 can cover any fraud type, having thorough records for every transaction ensures evidence availability regardless of what claim arises.
- Implement universal authentication controls. EMV for card-present, 3DS for CNP, AVS and CVV for all remote transactions. Comprehensive controls ensure evidence is available for any fraud type.
- Monitor dispute reason code distributions. An uptick in UA99 disputes may indicate an emerging fraud pattern worth investigating and addressing proactively.
- Establish documented fraud response procedures. Having a clear internal procedure for investigating and responding to any fraud dispute code reduces response time and improves evidence assembly quality.
Frequently Asked Questions
What is the difference between UA38 and UA99?
Both are miscellaneous/catch-all fraud codes. In practice, UA38 (Fraud – Other) and UA99 (Fraud – Miscellaneous) serve similar purposes. The specific code used may depend on how the issuer categorizes the cardholder's dispute, network rules in effect at the time, or acquirer processing systems. The defense approach is identical: investigate the specific claim and respond with targeted evidence.
How common is UA99?
UA99 is one of the less common Discover reason codes. Most fraud disputes are categorized under more specific UA codes. When UA99 appears, it often indicates an unusual or complex fraud scenario that warrants careful investigation rather than routine representment.
What is the cardholder filing window for UA99?
120 days from the transaction date, consistent with other Discover fraud codes. The merchant response window is 30 days from dispute notification.