Discover · Chargeback reason codes
Discover 7010 chargeback: Fraud Card Present explained
Checked
Discover reason code 7010, Fraud Card-Present Transaction (older letter code UA01), means the cardholder denies an in-person purchase. Fiserv's Discover guide gives the issuer 120 days from the processing date. Win with a signed, swiped or imprinted receipt, a keyed sale with the card security code sent at authorization, or compelling evidence such as signed work orders or a store-pickup signature. Adyen lists a card-present fraud code as not defendable.
- Category
- Fraud (card 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
- Signed, swiped or imprinted receipt; compelling evidence
- Can it be prevented?
- Yes: read every card electronically
- Who usually wins
- The merchant with a card read and signature
What PlatformDTC does
PlatformDTC's in-store point of sale sends every card payment to a Stripe Terminal card reader on the store's own Stripe account; the till cannot key a card number in, and online orders are card-not-present. PlatformDTC answers this kind of dispute with its standard evidence pack built from the order: customer name, email, IP address, billing and shipping address, items bought, carrier, tracking and ship date, the refund policy, and any refund already issued. With "Answer a chargeback automatically" switched on, it sends the response to the bank for you before the deadline.
What it means
The cardholder says an in-person transaction was not theirs.
Older Discover documentation pairs 7010 with the letter code UA01.
Why customers file it
Lost or stolen cards used at a counter, or keyed-in sales after a failed read.
Evidence that wins
Respond to every Discover chargeback, even small ones, as Discover itself advises. Send:
- A signed, swiped or imprinted receipt
- For a keyed sale: the CID sent in the authorization
- Compelling evidence: correspondence, signed work orders, store-pickup signature, proof of delivery
How to prevent it
- Read cards with a chip or contactless reader
- Avoid keyed entry at the counter
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
- Can an online store get a 7010?
- Only for in-person sales. Online fraud claims are 7030.
- Is 7010 defendable?
- Fiserv's guide lists defences; Adyen marks its card-present fraud code (4537) as not defendable through Adyen.
Sources
- Dispute categories and network reason codes — Stripe
- Dispute Management Guide, Discover chapter (Rev 04/16) — First Data (Fiserv)
- Dispute reason codes: Discover — Adyen
Related
- 7030 — The cardholder says they did not make an online, phone or mail order purchase.
- 4866 — A counterfeit chip card was used where the chip was not read.
- 4867 — A lost or stolen chip-and-PIN card was used where chip and PIN were not used.
- 4752 — The cardholder does not recognize the charge on their statement.
- 4755 — The cardholder says the goods or services never arrived.
- 4553 — The cardholder says the goods or services were defective, not as described or poor quality.
- 4541 — The cardholder says a recurring charge was billed after they cancelled.