Discover UA05 — Fraud: Chip Counterfeit Transaction
Discover UA05: the cardholder says a counterfeit chip card was used
By Byron Kiriibwa · Updated
Checked by three automated reviewers (facts against the playbook, search, and our rules), then approved by the author on .
Discover UA05 means the cardholder denies buying from you in person and claims a forged copy of their card was used. The bank checks whether the card was read by its chip at a chip-reading terminal, and whether the approval request carried the chip's data. Your card reader's record decides it; swiped, keyed, or no chip reader, accept.
What decides a Discover UA05
- The entry mode on your provider's record
- The bank looks first at how the card went into your terminal: inserted and read by its chip, at a reader built for chips. The provider's transaction record names that entry mode. A till receipt that prints only the total and the card's last digits doesn't show it, so request the record from your provider.
- The approval made on the chip read
- Next the bank asks if the chip's data travelled with the approval request. The provider's record puts the authorization beside the chip read, so one document covers both. Saying the customer stood at your counter, without that record, answers neither.
- Why 3D Secure and address checks are left out
- A UA05 concerns a card presented in person. 3D Secure results, address checks and delivery proof are answers to online fraud, so they don't help here; the card reader's record does.
- A chip that wouldn't read
- If the chip failed and the card was swiped or keyed, or your terminal can't read chips, the first check can't be met, so accept. Next time, ask for another card instead of falling back to swiping or keying.
The bank's test
The bank checks:
- Was the card read by its chip at a chip-reading terminal, not swiped or keyed?
- Did the approval request carry the chip's data?
- 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 (entry mode) and the authorization. | 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 UA05
- UA05 (Discover's 4866) covers an in-person sale with a counterfeit chip card that wasn't read by its chip. 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 UA05
- Sending a receipt that doesn't show the entry mode.
- 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 for the sale shows the entry mode as chip, at a terminal that reads chips, and the authorization that went with that read. Already refunded this payment, or has the cardholder told you they've dropped it? Send that refund record or message instead: it answers the bank's third check. Accept it when any of these is true:
- The card was swiped or keyed, or the terminal can't read chips.
- There is no record of how the card was read, 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 tailoring shop and take cards at the counter on a reader that reads chips. On July 19 a customer collects a suit you altered and pays $185; they insert their Discover card, the reader reads the chip, and the payment is approved. In August the cardholder's bank files a UA05, the cardholder claiming the card used was a forgery.
The response would attach:
- Exhibit A: the card-reader provider's transaction record for July 19: entry mode chip, read on the shop's chip-reading terminal.
- Exhibit B: the authorization in the same record: the $185.00 approval made on that chip read, with its authorization code.
- Exhibit C: the receipt for the sale: the suit alterations and $185.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 UA05, for $185.00 charged on July 19 for alterations to a suit, paid at our counter. The card was read by its chip at a chip-reading terminal, and the approval was made on that read.
Our counter terminal reads chips, and it read this card's chip; the card was not swiped or keyed in. The provider's transaction record gives the entry mode as chip (Exhibit A).
The approval was requested with the chip's data: that record also holds the $185.00 authorization made on the chip read, and its code (Exhibit B).
The sale matches the receipt: the alterations, for $185.00, on July 19 (Exhibit C).
The chip was read at a chip-reading terminal, and the approval was made on its data. We ask that the dispute be decided in our favor.
Questions people ask
What is a Discover UA05 chargeback?
Someone, the cardholder says, used a forged copy of their card for an in-person purchase they didn't make. Discover's rules aren't public; our reading, inferred from the shared EMV liability shift and Visa's matching conditions and not checked against Discover's own rules, is that UA05 (given as Discover's 4866) covers a counterfeit chip card that wasn't read by its chip.
Which Discover number goes with UA05?
We list UA05 as Discover's 4866. Like the code's meaning, that number hasn't been checked against Discover's own dispute rules, so rely on what your notice names.
Is Discover UA05 like Visa 10.1?
It rests on the EMV liability shift behind Visa 10.1 and 10.2: a sale done the secure way leaves the loss off the seller, and one done another way leaves it on them. That link is inferred, not checked against Discover's own rules.
Our till receipt shows only the total and card ending. What do we send for a UA05?
Ask your card-reader provider for the transaction record showing the entry mode and the authorization. A receipt with only the amount and card ending doesn't answer the bank's checks, and if the provider can't supply a record, accept.
Do 3D Secure or address checks help with a Discover UA05?
No. They answer online fraud, not a sale made in person with the card. What matters is how the card reader read the card.
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.