Discover Chargeback Code UA01: Fraud — Card Present

What Discover Reason Code UA01 Means

Discover reason code UA01, titled Fraud — Card Present, is filed when a cardholder disputes an in-person transaction, claiming the physical Discover card was used fraudulently at a point-of-sale terminal without their authorization. This is Discover's card-present fraud code, applying to transactions at retail locations, restaurants, hotels, and any environment where the physical card was present.

The central issue in a UA01 dispute is whether the merchant's terminal properly captured EMV chip data from the card. Under Discover's EMV liability shift policy (consistent with Visa, Mastercard, and Amex), if a chip card is swiped rather than dipped, the merchant bears full fraud liability. If the chip was properly read, liability shifts to the issuer.

Cross-Network Equivalent Codes

Common Trigger Scenarios

• Counterfeit card used at stripe-only terminal. A fraudster used a counterfeit magnetic stripe card cloned from a legitimate Discover card. If your terminal accepted the stripe swipe on a chip-capable card, Discover's liability shift places full responsibility on the merchant.
• Chip card swiped instead of dipped. The customer presented a chip-capable Discover card and either the cashier or the terminal processed it via magnetic stripe rather than requiring a chip read. This is the most preventable UA01 scenario and results in full merchant liability for any resulting fraud.
• Manual key-entry transaction. A card number was typed in manually rather than read by the terminal. Manual key-entry carries full fraud liability and no EMV protection regardless of whether the card was physically present.
• Stolen physical card used in-store. A stolen Discover card was used at your POS before the cardholder reported it lost or stolen. If EMV chip was used, liability shifts. If swiped, the merchant is liable.
• NFC/contactless dispute. While tap payments generally include electronic card verification, some contactless dispute scenarios on older terminals may result in UA01 if the underlying authentication data is challenged.

Key Deadlines & Timeframes

Evidence You Will Need

• EMV chip transaction record — the electronic record showing the chip was read at the terminal, including the cryptographic authentication data (ARQC/TC) that proves a genuine chip card was used
• Terminal receipt showing chip-read mode — receipts from EMV transactions typically indicate "Chip Read" or "EMV" rather than "Swipe" or "Manual Entry"
• Signed transaction receipt — cardholder signature as supplementary evidence that a person was physically present
• ID verification record — if staff checked government-issued ID at the point of sale, document this as supporting evidence
• Security camera footage — footage showing the cardholder present at the terminal during the transaction window, if available and applicable
• Fallback documentation — if the chip read failed and the transaction fell back to stripe, document the failed chip read attempts and the fallback procedure followed

How Merchants Lose This Dispute

• Non-EMV terminals still in use. Any terminal that cannot read EMV chips exposes the merchant to full liability on every chip card presented. If you have any stripe-only terminals in your fleet, upgrading them is the highest-priority action for reducing UA01 exposure.
• Chip card swiped without following fallback procedures. When a chip read fails, there are specific fallback steps that must be documented. Simply swiping and moving on leaves the merchant fully liable for any resulting fraud and gives them nothing to present in a representment.
• No EMV transaction record to present. Saying "we have a chip terminal" is not evidence. You need the actual transaction record showing chip mode was used for the specific disputed transaction.
• Submitting only the signed receipt. A signature proves someone was present but does not prove the cardholder's chip was read. Against a fraud claim, a signed receipt without EMV data is insufficient on its own.

Response Framework Overview

1. Lead with EMV chip transaction data. Present the chip read record for the specific disputed transaction. This is the central evidence and the primary basis for the liability shift argument.
2. Show terminal mode on the receipt. The transaction receipt should indicate "Chip Read" or "EMV" — present this as corroborating evidence that chip processing was used.
3. Present signed receipt. The cardholder signature establishes physical presence at the terminal as supplementary evidence.
4. Document ID verification if conducted. If staff checked the cardholder's ID, present this as evidence the person matched the card identity.

Prevention Tips

• Ensure all terminals are EMV chip-capable and configured correctly. Every Discover card presented at your POS should be processed via chip. If any terminal in your fleet cannot read chips, replace it. The liability exposure from a single UA01 chargeback exceeds the cost of terminal upgrades many times over.
• Train staff to require chip reads. Cashiers who routinely swipe chip cards "because it's faster" are creating full fraud liability on every such transaction. Staff training is as important as terminal capability.
• Document fallback procedures formally. When a chip read fails, staff should attempt the chip multiple times, note the failure on the receipt, and only then proceed with stripe as a documented fallback. Undocumented fallbacks carry full liability.
• Require ID for manual key-entry. When physical card reading is impossible, requiring and logging ID verification is the best available substitute for chip authentication.

Frequently Asked Questions

What is the difference between Discover UA01 and UA02?

UA01 covers card-present fraud — transactions where the physical Discover card was at the point of sale. UA02 covers card-not-present fraud — e-commerce, phone orders. UA01 requires in-person transaction evidence; UA02 requires CNP authentication evidence.

Does EMV chip processing protect against Discover UA01 chargebacks?

Yes. Discover's EMV liability shift works the same as other networks: if a chip card is properly read via EMV at a chip-capable terminal, fraud liability shifts to the issuer. If you swipe a chip-capable Discover card instead of dipping it, you bear the fraud liability.

How long does a Discover cardholder have to file a UA01 chargeback?

120 days from the transaction date. The merchant response window is typically 30 days from the dispute notification date, though your acquirer may impose a shorter internal deadline.

Can I win a UA01 dispute if the customer signed the receipt?

A signed receipt is supporting evidence but not a complete defense. The signature shows someone was at the POS, but fraud claims assert the person was not the legitimate cardholder. EMV chip transaction data, which cryptographically verifies the card, is much stronger than a signature alone.

Related Codes & Resources