Why is my online store getting UA01 card-present fraud chargebacks?

Your transactions are likely being coded with a card-present POS entry mode somewhere between your gateway and Discover. That miscoding is a processing configuration error to escalate with your acquirer immediately, because it distorts both your dispute defenses and your compliance standing.

Does EMV chip processing protect me from UA01 chargebacks?

Substantially, yes. When a chip card is processed through a working EMV terminal, counterfeit fraud liability generally sits with the issuer, and the chip cryptogram gives you strong evidence the genuine card was present. UA01 losses concentrate in swiped fallback and manually keyed in-person transactions.

What if the fraudster used a stolen card with the real chip and it authorized?

A properly processed chip transaction that Discover authorized is a defensible position; submit the EMV data and the approval. Lost-and-stolen fraud on chip-and-PIN transactions is handled under UA06, and liability there depends on how PIN verification was performed.

Discover · Fraud

Reason code UA01: Fraud - Card Present Transaction

The cardholder denies authorizing a transaction that was processed in a card-present environment, and the merchant cannot show the card was properly presented and verified at the point of sale. It typically means a swiped or keyed in-person transaction lacked the imprint, signature, or chip data needed to prove the genuine card was there.

Issuer filing window

typically 120 days from the processing date

Merchant response window

typically 30 days to respond

Why UA01 chargebacks happen

A counterfeit magstripe card was swiped at a terminal that did not enforce chip processing.
The transaction was keyed manually in person without an imprint or identity verification.
A lost or stolen card was used before the cardholder noticed and reported it.
The transaction record lacks the card-present data elements, so it cannot be proven the card was physically there.
An employee processed a card-not-present order through a card-present terminal, stripping the transaction of its proper evidence trail.

How to fight a UA01 chargeback

Submit the terminal record showing the card was read electronically, including entry mode, and any chip cryptogram data captured.
Provide the signed receipt or PIN verification record for the transaction.
Include an imprint if the transaction was manually keyed with the card physically present.
Add surveillance footage or other point-of-sale evidence placing the cardholder at the terminal, where available.
Show a pattern of prior undisputed transactions by the same cardholder at your location to establish familiarity, as supporting context.

How to prevent UA01 chargebacks

Process every in-person Discover transaction through the chip reader and never fall back to swipe unless the terminal instructs it.
Refuse to key card numbers manually at the counter; a customer with a card that will not read should use another payment method.
Capture signature or PIN per your terminal configuration and retain those records for the full dispute window.
Keep terminals updated and EMV-certified so liability for counterfeit cards stays with the issuer.
Train staff on card acceptance basics: check the card is signed, matches the receipt, and has not been visibly altered.

Frequently asked questions

Why is my online store getting UA01 card-present fraud chargebacks?: Your transactions are likely being coded with a card-present POS entry mode somewhere between your gateway and Discover. That miscoding is a processing configuration error to escalate with your acquirer immediately, because it distorts both your dispute defenses and your compliance standing.
Does EMV chip processing protect me from UA01 chargebacks?: Substantially, yes. When a chip card is processed through a working EMV terminal, counterfeit fraud liability generally sits with the issuer, and the chip cryptogram gives you strong evidence the genuine card was present. UA01 losses concentrate in swiped fallback and manually keyed in-person transactions.
What if the fraudster used a stolen card with the real chip and it authorized?: A properly processed chip transaction that Discover authorized is a defensible position; submit the EMV data and the approval. Lost-and-stolen fraud on chip-and-PIN transactions is handled under UA06, and liability there depends on how PIN verification was performed.

Related Discover codes