Discover UA02 — Fraud: Card-Not-Present Transaction
Discover UA02: the cardholder denies making an online purchase
By Byron Kiriibwa · Updated
Checked by three automated reviewers (facts against the playbook, search, and our rules), then approved by the author on .
In a Discover UA02, the cardholder denies an online or other card-not-present purchase. The bank checks whether the payment passed 3D Secure, whether a history ties this cardholder to you (earlier undisputed payments, IP address, device or account), whether the order went to their billing address, email or login, and whether they used it. With no link, accept.
What decides a Discover UA02
- 3D Secure, which Discover calls ProtectBuy
- An authenticated payment usually puts liability on the bank, and for a payment that shifts liability Stripe adds the result to the evidence itself. Secondary sources say UA02 still applies after a ProtectBuy authentication for some merchant category codes, listed under Discover's rules below. If yours is one of them, don't count on authentication alone.
- The link between the account and earlier orders
- Delivery proof alone isn't enough: delivery to an address not linked to the cardholder doesn't help on its own, and sending delivery proof without the link between the account and earlier orders is a common mistake on UA02. Show the same account, IP address or device on earlier undisputed orders.
- The payment's AVS and CID results
- Send the address check (AVS) and card code (CID) results with the response; leaving them out is the other common mistake. Secondary sources (Discover's rules aren't public) say an issuer may file a UA02 when AVS wasn't used properly or the CID was left out of the authorization.
The bank's test
The bank checks:
- Was the payment authenticated (3D Secure)? If so, liability usually sits with the bank (secondary sources list merchant category codes where it doesn't; see Network rules), and for liability-shift cases Stripe adds the 3DS result to the evidence automatically.
- Is there a history linking this cardholder to the seller — earlier undisputed payments from the same customer, IP address, device, or account?
- Did the purchase go somewhere the cardholder controls — their billing address, their email, their login?
- Did the cardholder use what was bought after the charge?
Evidence that answers it
“Where it goes” uses the names Stripe's and Square's APIs give each piece of evidence, which are the names Upheld uses in your packet. Nothing is sent without your approval; where Upheld can't send it for you, you submit it yourself. In Stripe's Dashboard, choose the matching type for each file or text field. In Square's, add it when Square asks you to “upload any additional evidence specific to your service type”.
| Evidence | When it counts | How to show it | Where it goes | For |
|---|---|---|---|---|
| 3D Secure authentication | The cardholder completed their bank's identity check at checkout. | State that the payment was authenticated with 3D Secure and the result. For fraud disputes this usually moves liability to the bank. | Stripe: Uncategorized text. There's no field of its own: for a payment that shifts liability, Stripe adds the 3D Secure result itself, so mention it in your letter.Square: Authorization documentation | Every seller |
| Earlier payments from the same customer | The same customer paid before without disputing, linking this purchase to a known buyer. | List each earlier payment with date and amount, and which identifiers match the disputed one (email, IP, device, shipping address, account). | Stripe: Uncategorized textSquare: Related transaction documentation | Every seller |
| Customer IP address and device | The purchase came from an IP address or device linked to the cardholder's other activity. | Give the purchase IP and show the same IP or device on logins or earlier orders. | Stripe: Customer purchase IPSquare: Cardholder information | Every seller |
| Customer account history | The buyer has an account with the seller — created on a known date, used repeatedly, tied to the cardholder's email. | Account creation date, email, login count and dates, earlier orders. A screenshot or export from the seller's platform. | Stripe: Uncategorized file or Uncategorized textSquare: Cardholder information | Every seller |
| Address and security-code checks | The billing postcode and card security code entered matched the bank's records, as supporting evidence only. | Report the check results as Stripe recorded them. Supporting evidence only, never the main argument. | Stripe: Uncategorized text. There's no field of its own: mention the address and card code results in your letter.Square: Authorization documentation | Every seller |
| Messages with the customer | Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix. | The relevant messages only, dated, with the key lines highlighted or quoted in the response. | Stripe: Customer communicationSquare: Cardholder communication | Every seller |
| Proof of delivery | Showing delivery to the billing address or an address used on the cardholder's earlier undisputed orders, with the order confirmation. | The carrier's delivery record showing date, address, and any signature or photo. | Stripe: Shipping documentationSquare: Proof of delivery documentation | Online stores |
| Access and usage log | Showing the cardholder used what was bought after the charge, with the checkout and terms records. | Dated list of activity tied to the customer's account: first and last login, count of sessions, what was viewed or downloaded. A short summary first, then the export. | Stripe: Access activity logSquare: Online or app access log | Courses, memberships, digital products |
| Service delivered | Showing the service was delivered after the charge, with the invoice. | Dates of service with proof: calendar invites and attendance, call records, delivered files, project sign-off. | Stripe: Service date or Service documentationSquare: Service received documentation | Services |
What doesn't help
- Delivery to an address not linked to the cardholder (not the billing address, nor one used on their earlier undisputed orders), on its own: the issuer checks the purchase went somewhere the cardholder controls (above). This follows from that check; it isn't a Discover rule.
Discover's rules for UA02
- UA02: fraud: card-not-present transaction. Unverified: the title, and the number 7030 that Stripe's list gives it, are from secondary sources read 2026-10-15 (merchantcostconsulting.com, chargeflow.io), not Discover's own dispute rules.
- Unverified (secondary sources; Discover's dispute rules aren't public): Stripe's category list gives "7030 Fraud Card Not Present Transaction" (Stripe docs, read 2026-11-02). An issuer may file a UA02 when the seller didn't use the Address Verification Service (AVS) properly or left the card's CID out of the authorization request, and UA02 still applies after a ProtectBuy "Authentication Successful" or "Authentication Attempted" response for merchant category codes 4829, 5967, 6051, 6540, 7801, 7802 and 7995 (Chargebacks911, Discover UA02, updated 2025-04-01). The seller's time to respond is given as 20 days by one source and 30 days by another; the seller's own deadline is the one the processor shows.
Common mistakes with Discover UA02
- Sending delivery proof without the link between the account and earlier orders, or without the payment's AVS and CID results (secondary sources say a UA02 may be filed over AVS or the CID; see Network rules).
Should you fight it?
Fight it when the payment passed 3D Secure (unless your merchant category code is one of those listed under Discover's rules above), or when the order traces back to a cardholder who has bought from you before, through the same account, IP address or device, with the order going to their billing address, email or login. Accept it when this is true:
- Nothing links the cardholder to the purchase, or the seller suspects real fraud.
If you accept, don't refund as well: once it's a chargeback the money has already gone back to the customer, so a refund would pay them twice.
A dispute counts against your account whether you win or lose. To see the chance of winning at which fighting pays on your amount, try the fight-or-accept calculator; to compare what you keep with each tool, the fee calculator.
How to prevent the next one
- Use 3D Secure (Discover ProtectBuy) on risky card-not-present payments, send AVS and CID with every authorization (secondary sources say a UA02 may be filed without them), and keep the IP address, device and account record for each order.
Deadlines and fees
| Platform | Deadline | Fees |
|---|---|---|
| Stripe (US)Checked 2026-10-21 | Respond by the due date on the dispute in your Stripe Dashboard. It's usually 7 to 21 days, depending on the card network. | $15 when the dispute arrives, which isn't returned. $15 more when you respond, returned only if you win in full.Stripe's Smart Disputes waives the $15 response fee and takes 30% of the disputed amount when you win. |
| SquareChecked 2026-10-21 | Seven days from Square's first email about the dispute. | No fees for dispute management on chargebacks: Square covers the fee for disputes you challenge together. |
| Shopify Payments (US)Checked 2026-10-21 | Respond by the evidence due date in your Shopify admin. It's usually 7 to 21 days. | $15 per chargeback, returned if you win. |
A worked example (made up)
A customer has bought from your kitchenware store twice before on the same Discover card, through the same store account, and disputed neither. On February 11, signed in to that account on the same device, they buy a $118 set of cast-iron pans. The payment passes 3D Secure, the billing address and card code match the bank's records, and the order is delivered on February 14 to the card's billing address. On February 15 they email from the account's address asking how to season the pans. On March 6 they file a UA02 dispute denying the purchase.
The response would attach:
- Exhibit A: the 3D Secure result for the February 11 payment; for a payment that shifts liability, Stripe adds it to the evidence itself.
- Exhibit B: the two earlier orders on the same card and account, with dates and amounts, neither disputed.
- Exhibit C: the account record, and the IP address and device of the February 11 order, matching the earlier orders.
- Exhibit D: the address check (AVS) and card code (CID) results for the February 11 payment, as Stripe recorded them.
- Exhibit E: the carrier's record of delivery to the billing address on February 14.
- Exhibit F: the customer's February 15 email about seasoning the pans.
A sample response letter (made up)
For the example above. It's laid out the way Upheld drafts a response: one part for each thing the bank checks, strongest evidence first, each pointing to its exhibit. Yours should state only what your own records show.
We contest this dispute, Discover reason code UA02, for $118.00 charged on February 11 for a set of cast-iron pans. The payment was authenticated with 3D Secure, and the cardholder ordered from their own account, and wrote to us about the pans after they arrived.
The payment passed 3D Secure authentication at checkout, and the result is attached (Exhibit A).
This cardholder has bought from us before. Two earlier orders on the same Discover card, from the same store account, were never disputed (Exhibit B), and the February 11 order was placed from the IP address and device used for those orders (Exhibit C). The billing address and card code entered at checkout matched the bank's records (Exhibit D).
The order went to the cardholder's billing address. The carrier delivered it there on February 14 (Exhibit E).
The cardholder had the pans after the charge. On February 15 they emailed us from the address on their account asking how to season them (Exhibit F).
3D Secure, the cardholder's own account and device, delivery to their billing address and their own email about the pans all link this purchase to the cardholder. We ask that the dispute be decided in our favor.
Questions people ask
What does Discover reason code UA02 mean?
The cardholder denies an online or other card-not-present purchase. Secondary sources title it "Fraud: Card-Not-Present Transaction"; that title hasn't been checked against Discover's own dispute rules.
Is UA02 the same as Discover 7030?
Secondary sources list UA02 as Discover's 7030, and Stripe's category list gives "7030 Fraud Card Not Present Transaction". That hasn't been checked against Discover's own dispute rules, which aren't public, so go by the code and the claim on your notice.
Do I need to upload the 3D Secure result for a Discover UA02?
On Stripe, for a payment that shifts liability, Stripe adds the result to the evidence itself; mention it in your letter either way. On Square, include it as authorization documentation. If the payment was authenticated, liability usually sits with the bank, though secondary sources list exceptions for some kinds of business (next question).
Does a ProtectBuy authentication stop a UA02?
Not for every business, according to secondary sources: they say UA02 still applies after a ProtectBuy "Authentication Successful" or "Authentication Attempted" response for a handful of merchant category codes, listed under Discover's rules above. If yours is one of them, don't count on authentication alone.
Can a UA02 be filed because of how our checkout handled AVS or the CID?
Secondary sources say yes: an issuer may file a UA02 when the seller didn't use the Address Verification Service properly or left the card's CID out of the authorization request. Discover's own rules aren't public, so this isn't confirmed. Either way, send the AVS and CID results from your payment record; on Stripe they're on the payment.
Draft yours free
Answer a few questions and get a draft, an evidence checklist and an honest read on whether to fight. Free account, no card.
Not sure what your notice says? Decode it first.