What is the EMV liability shift and how does it relate to UA05?

Since the US EMV migration, counterfeit card fraud liability falls on whichever party lacks chip capability. UA05 is Discover's code for enforcing that rule: if a counterfeit copy of a chip card was accepted without chip processing, the merchant absorbs the fraud loss that the issuer would otherwise carry.

Can I win a UA05 dispute if my terminal read the chip successfully?

Yes. A genuine EMV chip read with a valid cryptogram is strong evidence the card was not counterfeit magstripe fraud, and it generally defeats a UA05 claim. Submit the EMV transaction data and your terminal certification records through the retrieval process.

Why do magstripe fallback transactions keep costing me chargebacks?

Fallback strips away the chip evidence that protects you, and counterfeit cards are specifically engineered to force fallback. Networks tolerate occasional legitimate fallback, but each one is a UA05 exposure. Track fallback rate per terminal and treat rising rates as a hardware problem to fix, not a customer inconvenience to accept.

Discover · Fraud

Reason code UA05: Fraud - Chip Counterfeit Transaction

A counterfeit copy of a chip-enabled Discover card was used in person, and the transaction was not processed through EMV chip technology. Under the EMV liability shift, when a chip card is swiped or keyed at a terminal that could not or did not read the chip, counterfeit fraud liability lands on the merchant.

Issuer filing window

typically 120 days from the processing date

Merchant response window

typically 30 days to respond

Why UA05 chargebacks happen

The terminal was not EMV-enabled, so a cloned magstripe copy of a chip card was accepted by swipe.
A chip read failed and staff completed the sale via magstripe fallback that the network flags as avoidable.
Terminal EMV certification lapsed or the chip reader was disabled in configuration.
Skimmed track data from a chip card was written to a counterfeit stripe and used where chip enforcement was weak.
The card number was keyed manually in person, bypassing chip validation entirely.

How to fight a UA05 chargeback

Prove the transaction was processed as a genuine chip read by submitting the EMV data, including the application cryptogram and entry mode.
Show your terminal was EMV-certified and operational on the transaction date via your acquirer's terminal records.
If fallback occurred, document that it was legitimate and network-permitted, initiated by the terminal rather than staff choice.
Verify the disputed card actually was chip-enabled; the liability shift argument fails for genuinely non-chip cards, though these are now rare.
If the transaction was swiped or keyed on a working non-EMV path, the liability shift applies and representment will almost certainly fail; concede and fix the acceptance environment.

How to prevent UA05 chargebacks

Deploy EMV-certified terminals at every point of sale and keep certifications current through your acquirer.
Configure terminals to demand chip insertion for chip cards and to strictly limit magstripe fallback.
Monitor fallback rates per terminal and investigate any lane where fallback exceeds a small fraction of volume.
Prohibit manual key entry for in-person transactions in both policy and terminal configuration.
Replace or repair chip readers immediately when read-failure rates climb, since degraded readers manufacture fallback liability.

Frequently asked questions

What is the EMV liability shift and how does it relate to UA05?: Since the US EMV migration, counterfeit card fraud liability falls on whichever party lacks chip capability. UA05 is Discover's code for enforcing that rule: if a counterfeit copy of a chip card was accepted without chip processing, the merchant absorbs the fraud loss that the issuer would otherwise carry.
Can I win a UA05 dispute if my terminal read the chip successfully?: Yes. A genuine EMV chip read with a valid cryptogram is strong evidence the card was not counterfeit magstripe fraud, and it generally defeats a UA05 claim. Submit the EMV transaction data and your terminal certification records through the retrieval process.
Why do magstripe fallback transactions keep costing me chargebacks?: Fallback strips away the chip evidence that protects you, and counterfeit cards are specifically engineered to force fallback. Networks tolerate occasional legitimate fallback, but each one is a UA05 exposure. Track fallback rate per terminal and treat rising rates as a hardware problem to fix, not a customer inconvenience to accept.

Related Discover codes