What Discover Reason Code UA20 Means
Discover reason code UA20, Fraud — Chip Card, No PIN, is filed when a cardholder disputes a card-present transaction where the chip was read but no PIN was required — the transaction was completed with a signature or contactless tap instead. This is Discover’s chip-and-signature fraud code.
EMV compliance still provides liability shift protection in most cases where the chip was properly processed. If the merchant’s terminal read the chip and transmitted full EMV data, liability typically shifts to the issuer. Fallback to magnetic stripe or failure to transmit EMV data eliminates this protection.
UA20 is chip-and-signature (no PIN) fraud. UA18 covers chip-and-PIN fraud. UA21 is keyed-entry fraud with no imprint. The presence or absence of PIN verification is the key differentiator between UA18 and UA20.
Cross-Network Equivalent Codes
| Network | Code | Title | Notes |
|---|---|---|---|
| Discover | UA20 | Fraud – Chip Card, No PIN | This page |
| Visa | 10.5 | Visa Fraud Monitoring Program | Visa card-present fraud |
| Mastercard | 4870 | Chip Liability Shift | Mastercard EMV chip fraud |
| Amex | F24 | No Cardmember Authorization | Amex general fraud code |
Common Trigger Scenarios
- Stolen chip card used at signature-based terminal. A fraudster uses a stolen chip card at a terminal that accepts signature instead of PIN, completing the transaction without knowing the PIN.
- Contactless tap with stolen card. A stolen NFC-enabled chip card is tapped at a contactless reader, completing the transaction without any cardholder verification.
- Counterfeit chip card with no PIN required. A cloned chip card is used at a signature-based terminal where PIN verification is not enforced.
- Merchant terminal fallback to magnetic stripe. The terminal fell back to stripe despite the chip card being present, creating a non-EMV transaction without a liability shift record.
- Friendly fraud. A legitimate cardholder claims chip-card fraud on a transaction they actually made, denying the purchase after the fact.
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
- EMV chip read confirmation (ARQC/TC) — cryptographic proof the chip was successfully read at the terminal
- Terminal EMV compliance certification — documentation confirming your POS terminal is certified for EMV chip processing
- Authorization response with EMV data elements — the issuer auth record showing EMV chip data was transmitted
- Signed sales receipt — cardholder signature on the transaction receipt where signature was the verification method
- Terminal transaction log — full POS record confirming chip read rather than magnetic stripe fallback
Learn Exactly How to Package and Present This Evidence
The Fraud Defense Guide covers the evidence format for UA20 representments, EMV 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
- Non-EMV terminal. Without chip read capability, there is no EMV liability shift. The merchant bears full card-present fraud liability.
- Magnetic stripe fallback. If the terminal fell back to stripe despite the chip card, the liability shift does not apply regardless of whether signature was captured.
- No chip data in representment. Submitting only a signature receipt without the underlying EMV chip data does not substantiate the liability shift defense.
- Lapsed terminal certification. An expired EMV terminal certification can negate the liability shift even when the chip was physically read.
Get the Step-by-Step Winning Strategy
Our Fraud Defense Guide covers the complete UA20 representment structure and EMV liability shift documentation requirements.
Get the step-by-step winning strategy →Response Framework Overview
- Confirm EMV chip read — verify the transaction record shows chip processing, not magnetic stripe fallback.
- Pull the full EMV transaction data — ARQC and TC are the core evidence establishing the liability shift.
- Include the signed receipt — even without PIN, a cardholder signature is supporting evidence.
- Include terminal certification — demonstrate your POS system is fully EMV-certified and current.
Prevention Tips
- Ensure all POS terminals are EMV-certified and current. Lapsed certifications eliminate the liability shift at the worst possible time.
- Disable magnetic stripe fallback where possible. Fallback transactions carry no EMV protection and increase fraud exposure significantly.
- Capture cardholder signature for signature-based transactions. A signed receipt is supporting evidence even when it does not shift liability by itself.
- Consider requiring PIN for high-value transactions. PIN verification provides a stronger authentication record than signature alone.
Frequently Asked Questions
Does chip-and-signature provide the same liability shift as chip-and-PIN?
In most cases yes — EMV chip read without PIN still triggers the liability shift as long as the chip was properly processed and the terminal is certified. PIN is a stronger authentication factor but is not required for the EMV liability shift on its own.
What is the difference between UA20 and UA18?
UA18 covers chip transactions where a PIN was entered. UA20 covers chip transactions where no PIN was required — typically signature or contactless. Both can qualify for the EMV liability shift if the chip was properly processed.
How long does a cardholder have to file a UA20 dispute?
120 days from the transaction date. The merchant response window is 30 days from Discover’s notification.