What Discover Reason Code UA06 Means
Discover reason code UA06, Fraud — Card-Not-Present Transaction, is filed when a cardholder disputes an online, phone, or mail-order transaction as unauthorized. This is Discover’s primary CNP fraud code, applying when the card was not physically present and the cardholder claims they never authorized the charge.
The central defense is 3D Secure (3DS) authentication. When a transaction is authenticated via 3DS, liability shifts to the issuer. Without 3DS data, the merchant bears full fraud liability. CVV matching and address verification support the defense but do not shift liability on their own.
UA06 is card-not-present fraud. UA05 and UA01 cover card-present fraud. UA12 is the cardholder’s explicit CNP fraud claim. Evidence and defense approaches differ significantly across these codes.
Cross-Network Equivalent Codes
| Network | Code | Title | Notes |
|---|---|---|---|
| Discover | UA06 | Fraud – Card-Not-Present Transaction | This page |
| Visa | 10.4 | Other Fraud – Card-Absent Environment | Visa’s CNP fraud code |
| Mastercard | 4853 | Cardholder Dispute | Mastercard CNP fraud |
| Amex | F29 | Card Not Present | Amex’s CNP fraud code |
Common Trigger Scenarios
- Stolen card number used online. A fraudster obtained the cardholder’s card number through phishing or a breach and made an e-commerce purchase.
- Account takeover. A fraudster accesses the cardholder’s online account and purchases with a saved payment method, often shipping to a different address.
- Synthetic fraud. Fraudulently obtained card data used with a synthetic identity for purchases that appear legitimate at authorization.
- No 3DS on high-risk order. A high-value or high-risk transaction was processed without 3D Secure, creating no authentication liability shift record.
- Friendly fraud misclassified as UA06. A legitimate cardholder claims fraud on a purchase they actually made, common for digital goods and subscriptions.
Key Deadlines & Timeframes
| Milestone | Timeframe | Notes |
|---|---|---|
| Cardholder Filing Window | 120 days | From the transaction date |
| Merchant Response Window | 30 days | From Discover dispute notification |
| Pre-Arbitration | 30 days | If Discover rejects representment |
Evidence You Will Need
- 3D Secure authentication record — CAVV/AAV and ECI code showing successful 3DS authentication, which shifts liability to the issuer
- CVV2 match confirmation — evidence the security code was verified at authorization (supporting evidence only)
- AVS match result — address verification result showing billing address matched (supporting evidence)
- IP address and device fingerprint — logs showing the order originated from the cardholder’s known location or device
- Order delivery confirmation — carrier tracking confirming delivery to the billing address
- Account login history — for purchases through an authenticated account, logs showing the cardholder’s credentials were used
Learn Exactly How to Package and Present This Evidence
The Fraud Defense Guide covers the evidence format for UA06 representments, documentation requirements, and when a dispute is better accepted than contested.
Learn exactly how to package and present this evidence →How Merchants Lose This Dispute
- No 3DS on the disputed transaction. Without 3D Secure data, UA06 is extremely difficult to win. The merchant bears full CNP fraud liability without a liability shift record.
- Delivery to a different address than billing. Shipping to an address other than the cardholder’s billing address significantly weakens the merchant’s position.
- No fraud screening documented. High-risk signals ignored and not documented weaken the case substantially.
- Digital goods without access logs. For digital products, without showing the cardholder’s account accessed the goods, the delivery argument is weak.
Get the Step-by-Step Winning Strategy
Our Fraud Defense Guide covers the complete UA06 representment structure and cross-network defense approach.
Get the step-by-step winning strategy →Response Framework Overview
- Check for 3DS authentication record first. If it exists, lead with the CAVV/AAV and ECI code.
- Present all verification results: CVV2 match and AVS. Document both in the representment.
- Show delivery confirmation to the billing address. Carrier tracking is strong corroborating evidence.
- Include account and order context — login history and account activity showing the cardholder’s credentials were used.
Prevention Tips
- Implement 3D Secure on all e-commerce transactions. 3DS is the only mechanism that shifts CNP fraud liability to the issuer.
- Use fraud scoring on high-risk orders. Velocity checks, IP geolocation, device fingerprinting, and shipping address verification catch fraud before it processes.
- Require CVV2 and match AVS on all CNP transactions. These screen out low-effort fraud and provide supporting evidence for representments.
- Flag billing/shipping address mismatches for manual review. The majority of fraud orders ship to a different address than billing.
Frequently Asked Questions
Does 3D Secure guarantee a win on UA06?
3DS authentication shifts liability to the issuer, typically resolving the dispute in the merchant’s favor. Only full authentication provides the liability shift — confirm which ECI codes qualify with your processor.
Does CVV2 matching protect against UA06?
CVV2 matching is supporting evidence but does not shift liability. It shows the fraudster had full card details but does not provide 3DS-level protection.
How long does a cardholder have to file a UA06 dispute?
120 days from the transaction date. The merchant response window is 30 days from Discover’s notification.