What Discover Reason Code UA05 Means
Discover reason code UA05, Fraud — Card-Present Transaction, is filed when a cardholder disputes a point-of-sale transaction as unauthorized fraud. It applies in card-present scenarios where the terminal’s processing method — magnetic stripe swipe, manual key entry, or non-EMV capture — leaves the merchant exposed under Discover’s EMV liability shift rules.
The central issue is always whether the transaction was processed via EMV chip. Without a chip read record, the merchant bears full liability for card-present fraud.
UA05 is card-present fraud. UA06 covers card-not-present fraud. UA01 is Discover’s primary card-present fraud code. All three require different evidence strategies.
Cross-Network Equivalent Codes
| Network | Code | Title | Notes |
|---|---|---|---|
| Discover | UA05 | Fraud – Card-Present Transaction | This page |
| Visa | 10.1 | EMV Liability Shift Counterfeit Fraud | Visa’s card-present EMV liability shift code |
| Mastercard | 4870 | Chip Liability Shift | Mastercard’s card-present chip liability shift |
| Amex | F10 | Missing Imprint | Amex’s card-present fraud code |
Common Trigger Scenarios
- Chip card swiped instead of dipped. A chip-capable Discover card was processed via magnetic stripe. Discover’s EMV liability shift places full fraud liability on the merchant.
- Non-EMV terminal in use. A terminal incapable of reading EMV chips processes a counterfeit or stolen card. Full merchant liability.
- Manual key-entry transaction. A card number was typed manually rather than read by the terminal, with no chip authentication protection.
- Counterfeit card at stripe-only terminal. A fraudster’s cloned magnetic stripe card was processed on a terminal that never attempted a chip read.
- Fallback without documentation. A chip read failed and the fallback to stripe was not documented, leaving no justification for stripe processing.
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 transaction record — electronic record showing the chip was read, including cryptographic authentication data (ARQC/TC)
- Terminal receipt showing chip-read mode — receipt indicating “Chip Read” or “EMV” rather than “Swipe” or “Manual Entry”
- Signed transaction receipt — cardholder signature as supplementary evidence of physical presence
- Fallback documentation — if a chip read failed and stripe was used, document the failed chip read attempts
- Terminal compliance records — documentation that your terminal is EMV-certified and properly configured
Learn Exactly How to Package and Present This Evidence
The Fraud Defense Guide covers the evidence format for UA05 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
- Non-EMV terminals still in use. UA05 is almost unwinnable if your terminal did not attempt a chip read. Replace stripe-only terminals.
- No EMV transaction record. Asserting you have chip terminals is not evidence. You need the specific record showing chip mode was used for the disputed transaction.
- Chip card swiped without documented fallback. Swiping after a chip failure without documenting it leaves stripe liability and no defense.
- Signed receipt without EMV data. A signature proves presence but not chip authentication. Insufficient against a fraud claim alone.
Get the Step-by-Step Winning Strategy
Our Fraud Defense Guide covers the complete UA05 representment structure and cross-network defense approach.
Get the step-by-step winning strategy →Response Framework Overview
- Pull the EMV chip transaction record immediately. Without it, evaluate whether the dispute is better accepted.
- Confirm terminal mode on the receipt — look for “Chip Read” or “EMV” on the disputed transaction.
- Document any fallback circumstances: failed chip read attempts and the fallback log if available.
- Submit signed receipt as supplementary evidence only — chip data leads.
Prevention Tips
- Ensure all terminals are EMV chip-capable. Every Discover card should be processed via chip. Replace any stripe-only terminals immediately.
- Train staff to require chip reads. Cashiers who swipe chip cards create full fraud liability on every such transaction.
- Formalize fallback procedures. When a chip read fails, attempt it multiple times, note the failure, and only then proceed with documented stripe fallback.
- Audit terminal compliance regularly. Confirm all terminals are EMV-certified and no configuration drift has disabled chip processing.
Frequently Asked Questions
What is the difference between Discover UA05 and UA01?
Both are card-present fraud codes. UA01 is Discover’s primary card-present fraud code. UA05 applies in specific terminal compliance scenarios. Both require EMV chip evidence and similar defense strategies.
Can I win UA05 if my terminal is chip-capable but the receipt shows Swipe?
Very difficult. If the terminal was chip-capable but the transaction was swiped, Discover’s liability shift applies. The exception is documented fallback with failed chip read attempts on file.
How long does a cardholder have to file a UA05 dispute?
120 days from the transaction date. The merchant response window is 30 days from Discover’s notification.