Discover's primary CNP fraud code, with the same evidence package the other networks expect for CNP fraud.
UA is Discover's primary CNP fraud code, parallel to Visa 10.4, Mastercard 4837, and Amex F24. Discover covers a smaller share of total chargebacks than the Visa and Mastercard equivalents because Discover's US market share is smaller. Merchants who treat Discover disputes as a low-priority afterthought lose them by default. The evidence package is the same shape as for the other networks; the procedural details are what change.
How the dispute actually arrives
Discover, like Amex, is both an issuer and a network. The cardholder files with Discover directly, and Discover's own dispute team reviews the merchant's response. The notification arrives through the merchant's processor or directly through Discover's merchant portal. The merchant has 20 days to respond, the shortest window of any major network alongside Amex.
Discover follows a two-cycle dispute process: an initial cycle and a re-presentment cycle. A merchant whose first response is rejected can re-represent with additional evidence, which is a structural advantage compared to Visa and Mastercard, where pre-arbitration is more procedurally demanding.
What the issuer is looking for
Discover reviewing a UA asks the same question as the other networks: was the legitimate cardholder responsible for the transaction. The answer is built from the same kinds of evidence, with one network-specific consideration.
ProtectBuy is Discover's 3D Secure implementation. Where ProtectBuy was used at checkout and the cardholder was authenticated, liability shifts away from the merchant, and the merchant should cite it explicitly. ProtectBuy adoption is lower than SafeKey, Visa Secure, or Mastercard Identity Check, which means more Discover transactions clear without authentication and carry more merchant liability.
AVS and CVV2 matches at the time of the transaction show the buyer had the billing address and the printed security code. Device fingerprint, IP geolocation, and session history matter where the cardholder claims they were not at their computer. Prior order history from the same Discover card, to the same shipping address, builds the same picture as for the other networks.
Common scenarios merchants see
A cardholder spots a Discover charge they do not recognize on a months-old statement and files a UA without first contacting the merchant. The full session history, including the email confirmation the buyer received and the delivery to their billing address, often resolves the case at initial response.
A buyer used the card, received the goods, and is now claiming the transaction was unauthorized. The textbook friendly fraud case. Login records to the buyer's account and any post-delivery communication carry the case.
A family member placed the order. Under Discover rules, the cardholder is generally responsible for transactions made by household members with access to the card. The defense is evidence the order shipped to the cardholder's address and was retained.
A true account takeover. These cases are usually unwinnable, and the right move is to issue the refund rather than fight at representment.
What this code is not
Reason code UA is not a dispute about whether the merchandise arrived or matched the description. Discover uses RG and RM codes for non-receipt and quality disputes respectively. Submitting non-receipt evidence on a UA misses the question Discover is asking.
Where this fits in our service
Discover reason code UA is a code we draft rebuttal letters against on the same evidence shape as Visa 10.4 and Mastercard 4837, with Discover-specific rule citations and ProtectBuy posture where relevant. The shorter response window and the two-cycle structure mean we prioritize UA cases when they arrive. If you are reading this because you just received one, you can start with a free first letter.
Official source: Discover rules. Last reviewed 2026-05-11.