Discover reason code UA05
Discover UA05: Fraud: Chip Card Counterfeit Transaction
What the cardholder is claiming
The cardholder had a chip card and says a counterfeit copy of it was used at your terminal. Because the transaction was swiped or keyed instead of chip-read, Discover shifts the fraud loss to the merchant.
The evidence that actually wins
Bank analysts skim responses in minutes against a checklist for this exact code. Lead with the strongest fact; never make them dig.
- ✓Terminal records showing the transaction was actually chip-read (EMV cryptogram data), which would mean the code was misapplied
- ✓Evidence the terminal was EMV-compliant and any fallback to magnetic stripe was legitimate and issuer-approved
- ✓Authorization records showing Discover approved the transaction exactly as it was presented
- ✓Proof the disputed transaction was already refunded
The honest read
This code exists to enforce the EMV liability shift, not to litigate whether fraud occurred. If a counterfeit chip card was swiped or keyed at your terminal, the loss is yours by design and a rebuttal wastes your response window. The only real defense is proving the code was applied wrongly because the transaction actually went through the chip reader. If your hardware is not EMV-compliant, upgrading the terminal is the fix; no evidence package substitutes for it.
Nobody can promise you a win; the cardholder's bank decides. What you control is submitting the strongest complete case your records support, on time. Our plain-language guarantees say exactly what that means.
Fighting a UA05 right now?
Send us the dispute and a person builds the complete, submission-ready response: the narrative mapped to UA05, your evidence compiled and ordered, and the field-by-field walkthrough. 24-hour rush available. If our review says yours isn't worth fighting, we tell you for free.