What Discover Reason Code UA11 Means
Discover reason code UA11, Cardholder Claims Fraud — Card Present, Signature, is filed when a cardholder disputes an in-person transaction as unauthorized and a signature was captured at the point of sale. The cardholder asserts they did not make the purchase and that the signature on the receipt is not theirs.
The critical insight: a signed receipt alone is not a complete defense. The cardholder is specifically asserting the signature is not authentic. EMV chip transaction data, which cryptographically authenticates the card, is the stronger evidence here.
UA11 specifically involves a disputed signature. UA05 and UA01 are broader card-present fraud codes. The signature captured in the UA11 transaction is challenged, not accepted — lead with EMV chip data, not the signature.
Cross-Network Equivalent Codes
| Network | Code | Title | Notes |
|---|---|---|---|
| Discover | UA11 | Cardholder Claims Fraud (Card Present, Signature) | This page |
| Visa | 10.1 | EMV Liability Shift Counterfeit Fraud | Visa’s card-present fraud code |
| Mastercard | 4870 | Chip Liability Shift | Mastercard’s card-present fraud code |
| Amex | F10 | Missing Imprint | Amex’s card-present fraud code |
Common Trigger Scenarios
- Stolen physical card used at POS. A stolen Discover card was used in-store and a signature obtained. The legitimate cardholder disputes the transaction and denies the signature.
- Counterfeit card used at a terminal. A cloned card was used and a signature collected. The cardholder denies both the transaction and the signature.
- Family or household fraud. A family member used the card without authorization. The cardholder files a fraud claim denying the signature is theirs.
- Lost card used before report. A lost card was used at a merchant before the cardholder reported it. The resulting signature dispute falls under UA11.
- Friendly fraud with signature. A legitimate cardholder makes a purchase, signs the receipt, then claims fraud. The signature is genuine but disputed.
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, with cryptographic authentication data (ARQC/TC) — stronger than the disputed signature
- Signed transaction receipt — include it, but note the cardholder is disputing the signature; present as supplementary, not primary evidence
- ID verification record — if staff checked government-issued ID at the POS, this directly contradicts the fraud claim by establishing the person matched the card identity
- Security camera footage — footage of the person at the terminal during the disputed transaction window
- Terminal mode confirmation — receipt showing “Chip Read” or “EMV” mode for the disputed transaction
Learn Exactly How to Package and Present This Evidence
The Fraud Defense Guide covers the evidence format for UA11 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
- Relying solely on the signed receipt. In UA11 the cardholder specifically denies the signature. Submitting only the receipt without EMV data or ID verification is insufficient.
- No EMV chip data available. If the transaction was processed via stripe, UA11 is extremely difficult without cryptographic authentication.
- No ID verification conducted. For high-value transactions, missing ID verification means there’s no record that the person matched the card identity.
- No security footage. Without camera evidence of who was at the terminal, the merchant has no independent verification of physical presence.
Get the Step-by-Step Winning Strategy
Our Fraud Defense Guide covers the complete UA11 representment structure and cross-network defense approach.
Get the step-by-step winning strategy →Response Framework Overview
- Lead with EMV chip transaction data. The chip record cryptographically proves the genuine card was present.
- Present ID verification if conducted. Staff checking the cardholder’s ID directly contradicts the fraud claim.
- Include the signed receipt as supplementary evidence, framing it as context rather than primary proof.
- Provide security footage if available — video of the person at the terminal is highly compelling.
Prevention Tips
- Require ID for high-value transactions. ID verification at the POS provides independent verification that goes beyond the signature.
- Ensure all terminals are EMV-capable. EMV chip data is the primary protection against card-present fraud claims, including signature disputes.
- Install and maintain cameras at POS terminals. Footage of the transaction terminal provides independent evidence of who was present during a disputed transaction.
- Document fallback procedures. When a chip read fails, documented procedures protect against signature disputes even on stripe transactions.
Frequently Asked Questions
Does the signed receipt prove I win a UA11 dispute?
No. In UA11 the cardholder is asserting they did not sign the receipt. EMV chip transaction data, which cryptographically verifies the card, is the stronger defense.
What if I have the signed receipt but no EMV record?
You can still submit the receipt, but the dispute is difficult. Evaluate whether to contest or accept based on the transaction context.
How long does a cardholder have to file a UA11 dispute?
120 days from the transaction date. The merchant response window is 30 days from Discover’s notification.