NewNo plan feeNo plan fee. Just 2.9% + $0.30 per card sale, and signing up is free.Try now →

Discover · Chargeback reason codes

Discover 7030 (UA02) chargeback: Fraud Card-Not-Present Transaction, and how to win it

Checked

Discover reason code 7030, Fraud Card-Not-Present Transaction (older letter code UA02), means the cardholder says they did not make an online, phone or mail order purchase. Fiserv's Discover guide gives the issuer 120 days from the processing date. Win with valid proof of delivery plus a card security code (CID) check and address match at authorization, or compelling evidence such as earlier undisputed payments, matching IP address, device ID and login history.

Category
Fraud (card not present)
Time limit for the bank to file
120 calendar days from the processing date for most Discover codes (Fiserv guide, 2016)
Time limit to respond
Your processor's deadline: Stripe says usually 7–21 days depending on the network; Adyen gives 25 days for Discover
Typical evidence
Proof of delivery with CID and AVS match; prior undisputed payments, IP and device
Can it be prevented?
Largely: 3-D Secure (ProtectBuy), CID and address checks, Discover Fraud Alerts
Who usually wins
The cardholder unless you have delivery plus card checks or compelling evidence

What PlatformDTC does

PlatformDTC writes the product description, delivery address, buyer email and IP address onto every Stripe payment at checkout, then adds the carrier and tracking number when the parcel ships. When a fraud dispute opens it stops the subscription behind the order, and its response states the buyer's IP, billing and shipping address, what was bought and that the customer never asked the store for a refund. With "Answer a chargeback automatically" switched on, it sends the response to the bank for you before the deadline.

What it means

The cardholder denies a card-not-present purchase. If the merchant ignored an earlier documentation request, Fiserv's guide says the issuer may file a final, non-appealable chargeback. Adyen lists the same claim under code 4868.

Older Discover documentation pairs 7030 with the letter code UA02.

Why customers file it

Stolen card numbers used online, a family member's purchase, or a charge the cardholder does not recognise.

Evidence that wins

Respond to every Discover chargeback, even small ones, as Discover itself advises. Send:

  • Valid proof of delivery
  • The card security code (CID) sent with the authorization and a positive address (AVS) match
  • Documentation with the authorization code and a description of the goods
  • Compelling evidence: invoices, emails, signed proof of delivery, earlier undisputed payments; for digital goods, IP address, device ID and login history

How to prevent it

  • Send the CID and billing address with every authorization
  • Use Discover Fraud Alerts to stop shipping orders the cardholder has reported
  • Refund payments flagged as fraud before a chargeback

For developers

On Stripe the dispute object arrives with reason "fraudulent" and the card network's own code in payment_method_details.card.network_reason_code; listen for charge.dispute.created and read evidence_details.due_by for the deadline.

Discover does not publish its dispute rules publicly; the codes and names here are the ones Stripe reports, and the defences come from processor guides.

Frequently asked questions

What happens if I ignore a Discover documentation request?
Fiserv's guide says the issuer may then file a final, non-appealable fraud chargeback. Stripe adds that unanswered Discover inquiries can turn into disputes you cannot challenge.
Why does my processor show 4868 instead of 7030?
Adyen lists card-not-present fraud under 4868. Stripe, Braintree and TabaPay use 7030.

Sources

Related

Payments library