Discover Reason Code UA02: Fraud, Card Not Present

What Discover reason code UA02 means

UA02 is Discover’s fraud code for card-not-present transactions: ecommerce orders, phone orders, mail orders, and recurring charges where no physical card was presented. The cardholder tells their issuer they did not authorize the purchase and did not take part in it. It is the Discover counterpart of Visa 10.4 and Mastercard 4837.

Two very different situations end up under UA02:

• True fraud: a criminal used stolen card details on your checkout. The real cardholder never saw your site.
• Friendly fraud: the cardholder, or someone in their household, made the purchase and then reported it as fraud. See first-party vs friendly vs true fraud.

Your response has to show which one this is. If the evidence links the cardholder to the order, the fraud claim falls apart.

UA02 differs from AA. An AA cardholder says “I don’t recognize this.” A UA02 cardholder says “I didn’t do this.” AA rebuttals lead with identifying the transaction; UA02 rebuttals lead with proving authorization.

Common causes

• Stolen card details used on your store, often after a card-testing run
• Account takeover, where a fraudster logs into a real customer’s account
• A purchase by a family member who had access to the card
• Buyer’s remorse or non-delivery frustration reframed as fraud
• A subscription renewal the cardholder now says they never agreed to

The ProtectBuy liability shift

Discover’s 3-D Secure program is branded ProtectBuy. When a card-not-present transaction is successfully authenticated through 3-D Secure, fraud liability generally shifts from you to the issuer. That can prevent a UA02 or give you a strong defense against one.

How “attempted” authentications are treated varies, so check your processor’s documentation. And 3-D Secure covers fraud claims only: a cardholder can still file RG or RM on an authenticated order.

Evidence that wins a UA02 dispute

1. 3-D Secure / ProtectBuy result: the authentication value and status for the transaction, if it was authenticated.
2. AVS and CID results: a full address match and a CID (Discover’s card security code) match at authorization.
3. Delivery to the cardholder: carrier tracking showing delivery to the billing address, with a signature for high-value orders.
4. IP and device data: an IP address whose location fits the billing address, and a device fingerprint that matches the customer’s earlier orders.
5. Account and order history: when the customer account was created, login history, and earlier orders on the same card or account that were never disputed. Visa’s Compelling Evidence 3.0 is a Visa-only rule, so on Discover this history is persuasive evidence rather than an automatic win.
6. Digital goods usage: logins, downloads, license activations or streaming activity after the purchase, tied to the cardholder’s email or IP.
7. Post-purchase contact: emails or support tickets where the customer asked about shipping, sizing or a return. Someone who didn’t place the order rarely asks where it is.

Lead the rebuttal with the strongest single link, such as delivery to the verified billing address or a prior undisputed order from the same device, then stack the rest behind it.

How to prevent UA02 chargebacks

• Turn on 3-D Secure for risky orders: high values, AVS mismatches, new accounts, or shipping that differs from billing.
• Require CID on every card-not-present order and review AVS mismatches before shipping.
• Add velocity limits and bot protection to stop card testing.
• Ship high-value orders signature-required.
• Flag customers with a prior fraud dispute before you ship to them again.

More in preventing disputes at checkout.

Should you fight or accept?

Fight when the evidence ties the cardholder to the order: an AVS and CID match plus delivery to the billing address, prior undisputed history, or post-purchase contact. Friendly-fraud UA02s with that evidence are winnable.

Accept when the signals point to true fraud: AVS mismatch, shipping to a freight forwarder or unrelated address, a brand-new account, and no prior history. Fighting those usually costs more than it recovers. If the order hasn’t shipped, cancel it and refund.

Either way, fraud disputes count toward your dispute ratio, and your acquirer watches it. See what is a good chargeback ratio.

DisputeDash pulls order, AVS/CID, tracking and customer-history evidence for UA02 automatically, maps it to a UA02-specific rebuttal template, and can run each brand fully automatically or with manual review before submission.