Discover UA01 — Fraud: Card-Present Transaction

Discover UA01: the cardholder denies a purchase made in person

By · Updated

Checked by three automated reviewers (facts against the playbook, search, and our rules), then approved by the author on .

Discover UA01 means the cardholder denies a purchase made in person with their card. The bank checks whether the card was read by its chip and the cardholder verified at the sale, and whether the payment was already refunded. A card-reader record showing the chip read and the verification answers it; swiped or keyed without the chip, accept.

Start a free draft

What decides a Discover UA01

The chip read and the verification, together
The bank's first check has two halves: that the chip was read, and that the cardholder was verified at the sale. Your card-reader provider's transaction record shows both, so send it with the receipt for the sale.
What your UA01 notice names as missing
Check what your UA01 notice says was missing: the chip read, or how the cardholder was verified. Answer that half first, from the card-reader record.
A swiped or keyed sale can't meet the first check
If the chip wouldn't read and the card was swiped or keyed in, the card-reader record shows that entry mode, so the bank's first check can't be met: accept. Next time, ask for another card rather than swiping or keying a chip card.

The bank's test

The bank checks:

  1. Was the card read by its chip, and the cardholder verified, at the sale?
  2. 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 for Discover UA01, by kind of business
EvidenceWhen it countsHow to show itWhere it goesFor
Card reader or processor record (chip, PIN, imprint)Showing the chip read and the verification.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 documentationEvery seller
Receipt or invoiceWhat was bought, the amount, and the date.The receipt or invoice sent to the customer.Stripe: ReceiptSquare: ReceiptEvery seller
Refund or credit already issuedIf the payment was already refunded.Refund date, amount, and reference.Stripe: Uncategorized fileSquare: Generic evidenceEvery seller
Messages with the customerIf 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 communicationEvery seller

Start a free draft

What doesn't help

  • 3D Secure, address checks, or delivery proof. They answer online fraud, not a card-present sale. This follows from the issuer's first check (above); it isn't a Discover rule.
  • A receipt that shows only the amount and card ending, with no entry mode or verification result. It can't show the chip read or the verification the issuer checks.

Discover's rules for UA01

  • UA01 covers a card-present purchase the cardholder says they didn't make.
  • Unverified (secondary sources; Discover's dispute rules aren't public): the title and the number 7010 come from secondary sources (merchantcostconsulting.com, chargeflow.io; read 2026-10-15) and Stripe's category list, which gives "7010 Fraud Card Present Transaction" without naming UA01 (Stripe docs, Dispute reason code categories; read 2026-11-03), not from Discover.

Common mistakes with Discover UA01

  • Sending only the till receipt when the card-reader provider's transaction record shows the entry mode and how the cardholder was verified.
  • Not checking what the notice names as missing (the chip read or the verification): the notice is the surest guide to what the issuer asks.

Should you fight it?

Fight it when your card-reader provider's record shows the chip was read and how the cardholder was verified at the sale, such as by PIN. A refund record for this payment, or the cardholder's message withdrawing the UA01, answers the bank's second check without the card-reader record. Accept it when this is true:

  • The card was swiped or keyed without the chip, or the seller suspects real fraud.

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 swipe or key in a chip card when the chip read fails; ask for another card.
  • Keep the card-reader provider's transaction records, which show the entry mode and verification.

Deadlines and fees

Deadlines and fees by platform
PlatformDeadlineFees
Stripe (US)Checked 2026-10-21Respond 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-21Seven 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-21Respond 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 tune and repair pianos and take cards at the customer's home on a card reader that reads chips and takes PINs. On May 6 you tune a customer's upright piano and replace two hammers for $210; they insert their Discover card and enter the PIN, and the payment is approved. In June the cardholder files a UA01 dispute denying the purchase.

The response would attach:

  1. Exhibit A: the card-reader provider's transaction record for May 6: entry mode chip, cardholder verified by PIN, and the authorization code.
  2. Exhibit B: the receipt for the sale: the date and time, $210, and the card ending.
  3. Exhibit C: the invoice for the visit, listing the tuning and the two replacement hammers.
  4. Exhibit D: your job notes from May 6, recording the work done on the piano.

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 UA01, for $210.00 charged on May 6 for a piano tuning and repair done at the customer's home. The card was read by its chip at the visit, and the cardholder entered their PIN.

The card was read by its chip, and the cardholder was verified, at the sale. Our card-reader provider's transaction record shows the entry mode as chip, the PIN verified, and the authorization code (Exhibit A), for the sale on the May 6 receipt (Exhibit B).

The service the payment was for was delivered at that visit. Our invoice lists the tuning and the two replacement hammers (Exhibit C), and our job notes from May 6 record the work (Exhibit D).

The card was at the visit, its chip was read, and the cardholder was verified by PIN for a service we delivered that day. We ask that the dispute be decided in our favor.

Questions people ask

What is a Discover UA01 chargeback?

Discover's rules aren't public; secondary sources give UA01 as fraud on a card-present transaction (Stripe's list gives that title to 7010): the cardholder denies an in-person purchase made with their card.

Is UA01 the same as Discover reason code 7010?

Stripe's list of Discover codes gives 7010 as "Fraud Card Present Transaction", and secondary sources give 7010 as UA01's number. Discover's own dispute rules aren't public, so neither has been checked against them; read your notice for what Discover asks.

The customer entered their PIN. Does that answer a Discover UA01?

It answers half of the bank's first check: whether the cardholder was verified. Send it on the card-reader provider's record together with the chip read, since the bank checks both.

The chip wouldn't read, so we swiped the card. Should we fight the UA01?

No. When the card was swiped or keyed without the chip, accept the dispute.

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.

Start a free draft