Skip to content
NoChargeback

Discover reason code UA02 and how to win card not present fraud disputes

Discover reason code UA02 (Fraud, Card Not Present Transaction) means the cardholder told the issuer they did not authorize a purchase made online, by phone or by mail. It is the main fraud dispute Discover uses for ecommerce and subscription merchants, and you can often win it by proving the real cardholder made or used the purchase.

Draft my evidence See pricing

Read and dispute permissions only. We never move your money.

What Discover reason code UA02 means

The issuer files UA02 when a cardholder reports a card not present transaction as fraudulent. The review focuses on how you verified the buyer at checkout and whether the order fits the cardholder's earlier behavior. Some UA02 disputes come from stolen card data. Many others are friendly fraud, where the cardholder or someone in the household placed the order and later did not remember it.

Typical triggers for a UA02 chargeback

  • Stolen card numbers used on a checkout without 3D Secure or other strong authentication.
  • A family member used a card saved in the browser or in a customer account.
  • The cardholder does not recognize the statement descriptor and reports the charge as fraud.
  • A forgotten subscription renewal, reported as unauthorized instead of canceled.
  • Account takeover, where an attacker logged in to a genuine customer account and ordered.

Time limits for Discover UA02

The cardholder typically has around 120 days from the processing date to dispute the charge. Your own response window is shorter and is set by your processor, often between 7 and 21 days. In Stripe the exact deadline appears as the evidence due date on the dispute. A missed deadline loses the dispute automatically.

Evidence that wins a UA02 dispute

  • Proof of 3D Secure authentication for the transaction, which in many cases shifts fraud liability away from the merchant.
  • AVS and CVV match results returned at authorization.
  • Customer IP address, device and location, and how they match earlier orders on the same account.
  • Login history showing the account was active after the purchase.
  • Delivery confirmation to the billing address, or download and usage logs for digital goods.
  • Prior undisputed transactions from the same customer with matching identifiers.

What to avoid when you respond

  • Do not send a short letter that only states the order was legitimate. Issuers need data.
  • Do not refund after the dispute is opened, because the funds are already withdrawn and you can lose twice.
  • Do not let the deadline pass while you wait for one more document.

How to prevent Discover UA02 chargebacks

  • Turn on 3D Secure for risky orders, or for all orders when your dispute rate climbs.
  • Use a statement descriptor with your brand name and a support contact.
  • Send renewal reminders before subscription charges.
  • Watch early fraud warnings and refund when a refund costs less than the likely chargeback.

How UA02 appears in Stripe

Stripe usually shows Discover UA02 disputes with the reason fraudulent, and the network reason code field on the dispute carries UA02. NoChargeback reads both, pulls 3D Secure, AVS, CVV, IP and customer history from the charge, and fills the matching Stripe evidence fields for you. Read more on Stripe chargeback protection and fraud prevention for online stores.

Rebuttal letter opening for Discover UA02

We are responding to the dispute filed under Discover reason code UA02. The transaction was authorized by the cardholder: it passed 3D Secure authentication, the AVS and CVV checks matched, and the order came from an IP address and device used in earlier undisputed purchases on the same account. The evidence below confirms the cardholder received and used the purchase.

Draft my evidence

Can a merchant win a Discover UA02 chargeback?

Yes. Merchants win UA02 disputes when they show authentication results, customer data that matches earlier orders and proof that the cardholder received or used the purchase. 3D Secure results and usage logs are the strongest proof.

Does 3D Secure protect me from UA02 chargebacks?

In many cases a successfully authenticated 3D Secure transaction moves fraud liability to the issuer, so the dispute is blocked or easier to win. Check your processor's rules for exemptions.

Should I refund a UA02 dispute?

Not after the dispute is filed, because the funds are already withdrawn. Refunding earlier, when an early fraud warning arrives, can cost less than the chargeback fee and keeps the dispute out of your ratio.