Discover UA06 — Fraud: Chip and PIN Transaction
Discover UA06: a lost or stolen chip-and-PIN card was used in person
By Byron Kiriibwa · Updated
Checked by three automated reviewers (facts against the playbook, search, and our rules), then approved by the author on .
Discover UA06 means the cardholder denies an in-person purchase made with their card after it was lost, stolen or never received. The bank checks whether the chip was read at a chip-reading terminal and whether the PIN was entered at a terminal that takes one. A card-reader record showing both decides it; no PIN on a PIN card, accept.
What decides a Discover UA06
- The chip read and the PIN, together
- UA06 asks for two things: the chip read at a chip-reading terminal, and the PIN entered at a terminal that takes one. Your provider's transaction record shows the entry mode, the PIN verification and the terminal.
- Let the reader prompt for the PIN
- If your reader takes PINs, let it ask for one on every chip card: a PIN skipped at the sale is a UA06 you'll have to accept.
- Keep the card-reader provider's records
- With no record of how the card was read or verified, and none the provider can supply, accept. A recollection that the sale happened in person, however clear, doesn't answer what the bank checks on a UA06.
- Online fraud proof has no place on a UA06
- For a purchase made with the card in hand, 3D Secure, address checks and delivery proof answer the wrong question. Leave them out of the response and lead with the reader's record.
The bank's test
The bank checks:
- Was the card read by its chip at a chip-reading terminal, not swiped or keyed?
- Was the PIN entered, at a terminal that can take one?
- Has the payment already been refunded, or does the cardholder no longer dispute it?
Evidence that answers it
“Where it goes” uses the names Stripe's and Square's APIs give each piece of evidence, which are the names Upheld uses in your packet. Nothing is sent without your approval; where Upheld can't send it for you, you submit it yourself. In Stripe's Dashboard, choose the matching type for each file or text field. In Square's, add it when Square asks you to “upload any additional evidence specific to your service type”.
| Evidence | When it counts | How to show it | Where it goes | For |
|---|---|---|---|---|
| Card reader or processor record (chip, PIN, imprint) | Showing the chip read, the PIN verified, and the terminal. | The terminal's receipt or the processor's transaction record, showing the entry mode, the verification result, the terminal ID, and the authorization code. Point to the lines that show how the card was read and how the cardholder was verified. | Stripe: Uncategorized fileSquare: Authorization documentation | Every seller |
| Receipt or invoice | Showing the sale: what was bought and the amount. | The receipt or invoice sent to the customer. | Stripe: ReceiptSquare: Receipt | Every seller |
| Refund or credit already issued | If the payment was already refunded. | Refund date, amount, and reference. | Stripe: Uncategorized fileSquare: Generic evidence | Every seller |
| Messages with the customer | If the cardholder has withdrawn the dispute. | The relevant messages only, dated, with the key lines highlighted or quoted in the response. | Stripe: Customer communicationSquare: Cardholder communication | Every seller |
What doesn't help
- 3D Secure, address checks, or delivery proof. They answer online fraud, not a card-present sale.
- A receipt that shows only the amount and card ending, with no entry mode or verification result.
Discover's rules for UA06
- UA06 (Discover's 4867) covers an in-person sale with a lost or stolen chip-and-PIN card where the PIN wasn't taken. Unverified against Discover's own dispute rules. Inferred from the shared EMV liability shift and the matching Visa conditions (Visa, Dispute Management Guidelines for Visa Merchants, June 2024).
- The same EMV liability shift as Visa 10.1 and 10.2: the seller carries the loss when the sale wasn't done the secure way, and not when it was. See Visa 10.1 and Visa 10.2, which are checked against Visa's guide.
Common mistakes with Discover UA06
- Showing the chip read without the PIN verification on a lost or stolen card.
- Arguing the sale was in person or that the card checks passed, without the card reader's record.
Should you fight it?
Fight it when your card-reader provider's record shows the chip read, the PIN verified, and the terminal it happened on. If you already refunded the charge, or the cardholder has told you they've dropped the UA06, that answers the bank's third check instead. Accept it when any of these is true:
- The card was swiped or keyed, or the PIN wasn't taken on a PIN card.
- There is no record of how the card was read or verified, and the card-reader provider can't supply one.
If you accept, don't refund as well: once it's a chargeback the money has already gone back to the customer, so a refund would pay them twice.
A dispute counts against your account whether you win or lose. To see the chance of winning at which fighting pays on your amount, try the fight-or-accept calculator; to compare what you keep with each tool, the fee calculator.
How to prevent the next one
- Use a card reader that reads chips and takes PINs, and let it prompt for the PIN.
- Don't fall back to swiping or keying when a chip read fails; ask for another card.
- Keep the card-reader provider's transaction records.
Deadlines and fees
| Platform | Deadline | Fees |
|---|---|---|
| Stripe (US)Checked 2026-10-21 | Respond by the due date on the dispute in your Stripe Dashboard. It's usually 7 to 21 days, depending on the card network. | $15 when the dispute arrives, which isn't returned. $15 more when you respond, returned only if you win in full.Stripe's Smart Disputes waives the $15 response fee and takes 30% of the disputed amount when you win. |
| SquareChecked 2026-10-21 | Seven days from Square's first email about the dispute. | No fees for dispute management on chargebacks: Square covers the fee for disputes you challenge together. |
| Shopify Payments (US)Checked 2026-10-21 | Respond by the evidence due date in your Shopify admin. It's usually 7 to 21 days. | $15 per chargeback, returned if you win. |
A worked example (made up)
You run a mobile dog-grooming van and take cards on a reader that reads chips and prompts for a PIN. On March 8 you groom a customer's two dogs outside their home for $130; the customer inserts a Discover card and enters the PIN, and the payment is approved. In April the cardholder files a UA06 dispute saying their card had been stolen.
The response would attach:
- Exhibit A: the card-reader provider's transaction record for March 8: entry mode chip, and the PIN verified.
- Exhibit B: the terminal named in that record, which the provider lists as reading chips and taking PINs.
- Exhibit C: the receipt for the sale: grooming for two dogs, $130.00.
A sample response letter (made up)
For the example above. It's laid out the way Upheld drafts a response: one part for each thing the bank checks, strongest evidence first, each pointing to its exhibit. Yours should state only what your own records show.
We contest this dispute, Discover reason code UA06, for $130.00 charged on March 8 for grooming two dogs at the customer's home. Outside the customer's home the card went into our reader, which read the chip, and the PIN typed on it was verified.
Nobody swiped or keyed the card: its chip was read, at a terminal built to read chips. Our card-reader provider's record shows the entry mode as chip (Exhibit A), on a terminal the provider lists as reading chips (Exhibit B).
The customer typed the PIN on the reader, and it was verified. The same record shows the PIN verified (Exhibit A), and the provider lists that terminal as taking PINs (Exhibit B).
The receipt shows the sale: grooming for two dogs, $130.00, on March 8 (Exhibit C).
The chip was read and the PIN verified, at a terminal that reads chips and takes PINs. We ask that the dispute be decided in our favor.
Questions people ask
What does a Discover UA06 dispute mean?
The cardholder says their card was lost, stolen or never received and then used for an in-person purchase. As we read it, UA06 (listed as Discover's 4867) covers a lost or stolen chip-and-PIN card used where the PIN wasn't taken. That reading is unverified: Discover's dispute rules aren't public, and it's inferred from the EMV liability shift the networks share and the matching Visa conditions.
Is Discover UA06 the same as reason code 4867?
We pair UA06 with 4867, but that is unverified: Discover doesn't publish its dispute rules, so read the code and the claim on the notice you received.
Our reader took the chip but skipped the PIN. Can we fight a Discover UA06?
Not on a PIN card. When the PIN wasn't taken on a PIN card, accept.
How is Discover UA06 different from UA05?
UA05 is about a counterfeit copy of the card; UA06 is about the real card used after it was lost, stolen or never received. For UA06 the bank checks the PIN as well as the chip read.
Our card-reader provider has no record of the UA06 sale. What now?
If there is no record of how the card was read or verified, and the provider can't supply one, accept the dispute. Arguing the sale was in person without the reader's record doesn't answer the bank's checks.
Draft yours free
Answer a few questions and get a draft, an evidence checklist and an honest read on whether to fight. Free account, no card.
Not sure what your notice says? Decode it first.