Discover chargebacks are the ones Shopify stores lose by default
A Discover dispute shows up on most Shopify stores a handful of times a year, which is exactly why it gets written off. The code on it reads AA or RG instead of a Visa-style 13.1, nobody on the team recognizes it, and by the time someone looks properly the window has closed. Worse: on Discover, the case is often already unwinnable by the time the chargeback lands, because of a stage Visa and Mastercard mostly stopped using.
What is actually different about a Discover chargeback
Discover issues its own cards and runs its own network, and since Capital One completed its acquisition on 18 May 2025 (Capital One's investor newsroom, checked 23 July 2026), issuing, network, and acquiring sit under one corporate roof. That structural fact gets a lot of airtime in vendor explainers.
It changes less than you would think. Worldpay's eComm Chargeback Process Guide (V3.1, checked at docs.worldpay.com on 23 July 2026) puts it flatly: "from a process flow standpoint, the Discover Chargeback and Representment process is virtually identical to that of Visa or MasterCard." Its own flow diagram still shows an issuing bank. You still get a debit, you still represent through your acquirer, and the evidence that wins is the evidence that wins a Visa case.
The real difference sits one step earlier.
Why the retrieval request decides the case before the chargeback exists
Stripe's dispute documentation names Discover and American Express as "the networks that most often use" the inquiry phase, and says Mastercard and Visa no longer use it (docs.stripe.com, checked 23 July 2026). Then it adds the part that matters: "Inquiries for Discover cards can turn into unchallengeable disputes if you don't submit evidence for the inquiry." Amex runs the same inquiry stage, so a store seeing both is running one habit, not two.
Three other processors document the same trapdoor in their own wording. Adyen gives you 18 days to answer a Request for Information and warns that if you do not respond before the issuer files, "you might not be able to defend the chargeback." Worldpay gives you 20 days and says that for retrieval codes 6005, 6021, 6029, and 6041, failure to respond "will likely result in a Chargeback for which you do not have representment rights." Chase's guide says the same under reason code AA: the chargeback "will have no representment rights."
Worldpay calls the retrieval "the only opportunity for you to resolve the issue before the movement of funds from your account." Treat it as the case, not as a warm-up to the case.
Which Discover reason codes a Shopify store actually sees
Shopify will not show you the code. Its help documentation lists eight reason labels of its own (fraudulent, unrecognized, duplicate, subscription canceled, product not received, product unacceptable, credit not processed, general) and does not mention Discover anywhere on the page. The Discover code lives in your processor's dispute record, usually rendered as a two-letter code, a four-digit number, or both.
| Shopify label | Discover code | What the cardholder alleges | Evidence that answers it |
|---|---|---|---|
| Fraudulent | UA02 / 7030 | Card-not-present fraud: someone other than the cardholder made the purchase | AVS and CVV match results, 3-D Secure or equivalent authentication data, purchase IP and device data, prior undisputed orders on the same card |
| Unrecognized | AA / 4752 | Cardholder does not recognize the transaction | The billing descriptor as shown at checkout, an itemized bill, bill-to and ship-to addresses, and proof of delivery |
| Product not received | RG / 4755 | Goods never arrived, the order was cancelled and still charged, or delivery was refused | Carrier tracking with a delivery scan, proof no valid cancellation was filed, or download logs with IP, email and timestamp for digital goods |
| Product unacceptable | RM / 4553 | Quality of the goods or services did not match what was agreed | The product page and images as they stood on the purchase date, and documentation that the cardholder refused an offer to correct the problem |
| Subscription canceled | AP / 4541 | Billed after the plan was cancelled or expired | Signup terms, the cancellation log showing nothing filed before the renewal, the renewal notice sent |
| Duplicate | DP / 4534 | The same transaction was processed more than once | Settlement logs showing a single successful charge, or receipts distinguishing two separate purchases |
| Credit not processed | RN2 / 8002 | A promised refund never posted | The refund record with its posting date, or the policy showing no refund was owed |
| General | AT / 4863, AW / 4586, DC / 4757 | Authorization noncompliance, an amount that differs from the record, or an operating-regulation violation | Authorization records, the amount the cardholder agreed to, and the rule your processor says was missed |
Pairings above come from Chase's chargeback timeframes and reason codes user guide (last revised September 2021), Worldpay's V3.1 guide, and Braintree's current reason-code reference, all checked 23 July 2026.
One trap worth naming. Discover's 4863 is authorization noncompliance. Mastercard's 4863, before it disappeared from the current guide, was cardholder does not recognize. Same four digits, unrelated allegations, and if you are working from the Mastercard chargeback reason codes a Shopify store actually sees you will build the wrong packet.
Assembling one of these packets by hand takes 20 to 45 minutes, which is the real reason a $70 Discover case gets abandoned rather than any principled decision. Reclaim files the representment on a connected Shopify store at no install cost and no cut of the recovery, which removes the arithmetic that makes small disputes look not worth answering.
How long you actually have
Two clocks, and only one of them is Discover's.
The cardholder's clock. Most Discover codes carry 120 calendar days from the transaction date. RG and RM are the exceptions: both run 120 calendar days from the scheduled delivery date, capped at 540 days from the transaction. Good-faith cases under code 05 reach back 730 days. Those figures are from Chase's user guide, checked 23 July 2026.
Your clock. This one is set by your processor, not by Discover, and the numbers genuinely differ. Shopify puts the response window at 7 to 21 days and shows it as a due date on the dispute in your admin. Adyen documents 18 days for a Request for Information and 40 days to defend a first chargeback. Worldpay documents 20 days for a retrieval and 35 days for a representment. There is no single correct number to memorize. The date on your own dispute record is the one that counts.
Two operational limits worth building around: Discover's own Dispute System Interface for Merchants accepts up to three images per representment, TIFF or PDF (its merchant help guide at servicecenter.discovernetwork.com, checked 23 July 2026), and Adyen caps Diners and Discover defense files at 3 MB. A twelve-page bundle assembled for Visa will not fit. Consolidate before you submit.
If the issuer disagrees with your representment, it has 30 days to open pre-arbitration, and Adyen documents a USD 500 arbitration filing fee charged to the losing party.
The honest part
Discover does not publish its Dispute Rules Manual the way Visa publishes its Dispute Management Guidelines and Mastercard publishes its Chargeback Guide. I looked. Every code and timeframe in this article therefore comes from processor documentation rather than from the network itself, and those processors do not fully agree with each other. Chase renders card-not-present fraud as U02, First Data as 7030-UA02, Worldpay as 7030, and Braintree files 4863 under "fraud" while Worldpay calls it authorization noncompliance. Some of these guides are old: First Data's dispute guide is dated April 2016.
Build your response off the allegation, not off the digits. The allegation is stable. The rendering is not.
The other honest thing: your Discover disputes do not touch your VAMP ratio. VAMP is a Visa program, counting Visa fraud and dispute records against Visa settled transactions. A Discover chargeback is a revenue question and a standing question with Discover, not a Visa monitoring question. That makes the case for fighting them narrower than the case for fighting Visa disputes, and it is worth being precise about rather than borrowing urgency that does not apply. The evidence discipline is identical either way, which is the approach in how to win a Shopify chargeback with evidence that answers the reason code.
Frequently asked questions
What are the Discover chargeback reason codes?
Discover uses two-letter codes, usually paired with a four-digit number in processor records. The ones a Shopify store sees most are AA (4752) cardholder does not recognize, UA02 (7030) card-not-present fraud, RG (4755) non-receipt of goods or services, RM (4553) cardholder disputes quality, AP (4541) recurring payments, DP (4534) duplicate processing, and RN2 (8002) credit not received. Processors render these inconsistently, so match the written allegation rather than the number.
How long do I have to respond to a Discover chargeback?
That window is set by your processor, not by Discover, and it varies. Shopify shows a due date 7 to 21 days out on the dispute record in your admin. Adyen documents 40 days to defend a first chargeback and 18 days to answer a Request for Information. Worldpay documents 35 days for a representment and 20 days for a retrieval request. Use the date on your own dispute record.
What happens if I ignore a Discover retrieval request?
You lose the ability to represent the chargeback that follows. Stripe says inquiries on Discover cards can become unchallengeable disputes if you do not submit evidence at the inquiry stage. Worldpay says failure to respond to retrieval codes 6005, 6021, 6029 and 6041 will likely produce a chargeback with no representment rights, and Chase's guide says the same under reason code AA. A retrieval moves no money, so it is easy to deprioritize and expensive to skip.
How long does a Discover cardholder have to file a chargeback?
Most Discover reason codes allow 120 calendar days from the transaction date, per Chase's chargeback user guide. Non-receipt (RG) and quality disputes (RM) run 120 calendar days from the scheduled delivery date instead, capped at 540 days from the transaction. Good-faith cases under code 05 can reach back 730 days. Discover chargebacks also sit outside Visa's VAMP program, so they cost you revenue and standing with Discover without moving your Visa ratio.
What to do on your next Discover dispute
Filter last quarter's Shopify disputes by card brand and count the Discover ones. If the count is small, that is the argument for answering all of them rather than none, because a handful of cases is a couple of hours of work, not a program. Then check whether any of them arrived with no representment window at all. If so, an unanswered retrieval request is sitting upstream in your processor's queue, and that is the alert to fix before the next code lands.