What Discover Reason Code UA12 Means
Discover reason code UA12, Cardholder Claims Fraud — Card Not Present, is filed when a cardholder explicitly claims they did not authorize a CNP transaction — e-commerce, phone order, or mail order. The cardholder asserts active fraud rather than a dispute about goods or services.
UA12 has one of the lowest merchant win rates of any Discover code. Without 3D Secure authentication data proving the cardholder participated in the transaction, the merchant bears full liability.
UA12 is an explicit cardholder fraud claim on a CNP transaction. UA06 is the general CNP fraud code. UA11 covers card-present fraud with a disputed signature. UA12 has the lowest win rate of these codes — 3DS authentication is essential, not optional.
Cross-Network Equivalent Codes
| Network | Code | Title | Notes |
|---|---|---|---|
| Discover | UA12 | Cardholder Claims Fraud (Card Not Present) | This page |
| Visa | 10.4 | Other Fraud – Card-Absent Environment | Visa’s CNP fraud code |
| Mastercard | 4853 | Cardholder Dispute | Mastercard CNP fraud dispute |
| Amex | F29 | Card Not Present | Amex’s CNP fraud code |
Common Trigger Scenarios
- Stolen card data used for online purchase. A fraudster obtained the cardholder’s card number and made an e-commerce purchase. The cardholder files UA12 upon discovering the unauthorized charge.
- Account takeover with saved card. A fraudster accesses the cardholder’s online account and uses the saved Discover card for a purchase.
- Phishing or data breach. Cardholder data obtained through phishing or a third-party breach is used for a CNP transaction.
- Friendly fraud CNP claim. A legitimate cardholder makes an online purchase then files a UA12 fraud claim — common for digital goods, software, and subscriptions.
- No 3DS on the transaction. A high-risk online order processed without 3D Secure creates no authentication record to defend against a UA12 claim.
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 the cardholder completed 3DS authentication, shifting liability to the issuer
- IP address matching cardholder’s location — geolocation data showing the order originated from the cardholder’s known location or device
- Device fingerprint record — evidence showing the order was placed from a device previously associated with the cardholder’s account
- Account login history — for authenticated purchases, logs showing the cardholder’s credentials were used to place the order
- Delivery to billing address — carrier confirmation delivery was made to the cardholder’s billing address
- CVV2 match and AVS result — supporting evidence that verification data was checked at authorization
Learn Exactly How to Package and Present This Evidence
The Fraud Defense Guide covers the evidence format for UA12 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 authentication. UA12 is the hardest Discover code to win without 3DS. Without an authentication record, there is no proof the cardholder participated.
- Digital goods without access logs. Without showing the cardholder’s account accessed and used the digital goods, the delivery argument is weak.
- Shipping to a different address than billing. This significantly weakens the position in a UA12 fraud claim.
- No fraud screening applied. High-risk signals ignored and undocumented leave no evidence of good-faith fraud prevention.
Get the Step-by-Step Winning Strategy
Our Fraud Defense Guide covers the complete UA12 representment structure and cross-network defense approach.
Get the step-by-step winning strategy →Response Framework Overview
- Present 3DS authentication data immediately. If it exists, the CAVV/AAV and ECI code is the only evidence that can shift liability.
- Show device and IP data — geolocation and device fingerprint demonstrating the order came from the cardholder’s known location.
- Document account-based delivery for digital goods: login, access logs, confirmation the cardholder’s account received the product.
- Present all verification results: CVV2 match, AVS result, and any fraud score as supporting evidence.
Prevention Tips
- Implement 3D Secure on all e-commerce transactions. For UA12, 3DS is essential — not optional. It is the only mechanism that shifts CNP fraud liability to the issuer.
- Apply enhanced fraud screening to high-risk CNP orders. New accounts, high-value orders, velocity, and billing/shipping mismatch all warrant additional friction.
- Log all device and IP data at transaction time. Geolocation and device fingerprint data captured at transaction time provides critical UA12 representment evidence.
- Only ship to verified billing addresses. Shipping to confirmed billing addresses eliminates the most common UA12 fraud vector.
Frequently Asked Questions
What is the difference between Discover UA12 and UA06?
Both are CNP fraud codes. UA06 is the general card-not-present fraud code. UA12 is the cardholder’s explicit fraud claim on a CNP transaction. Both require 3DS as the primary defense.
Can I win UA12 without 3D Secure?
Very difficult. Without 3DS authentication data there is no proof the cardholder participated. Device fingerprint and IP data can support the case but rarely overcome a direct UA12 fraud claim.
How long does a cardholder have to file a UA12 dispute?
120 days from the transaction date. The merchant response window is 30 days from Discover’s notification.