Discover Chargeback Reason Codes: Time Limits Explained
Discover sorts chargebacks into three categories, fraud, processing errors and authorization issues, and service disputes. Its dispute process also runs differently from Visa and Mastercard. That changes your deadline and what you're allowed to do.
I've disputed chargebacks and built representment evidence for my own stores. I later advised merchants on the same thing. The mistake I see most with Discover is treating its clock and rules like Visa's or Mastercard's. Merchants miss a deadline because of it.
Read this and you'll know your actual response window. You'll also know the two rules that catch merchants who assume every network works the same way.
Key takeaways
- Discover sorts every chargeback into three categories that decide your evidence path.
- Discover is both the card network and the issuing bank.
- Discover can open a dispute with a retrieval request before any chargeback files.
- Cardholders get up to 120 days to file a Discover dispute.
- Some delayed-delivery cases extend a cardholder's filing window to 540 days.
What are Discover chargeback reason codes?
A Discover chargeback reason code is an alphanumeric code that explains why a transaction was reversed. Examples are AA, RG, and UA02. Discover assigns it. You'll see it on the dispute notice your processor forwards.
Each code sorts into one of three Discover categories. The category tells you the dispute type. It might be a fraud claim, a processing or authorization error, or a service complaint.
The category also shapes your evidence. So the category, not the code number, is where your response starts.
A code only exists once Discover has sorted a dispute. Before that, some disputes reach you as a retrieval request. That request arrives before any code. So the process below matters as much as the code.
Look up a specific Discover code
Our reason-code lookup tool answers a single-code question faster than any body list can. Most people searching this are staring at a dispute notice with one code. They just want to know what it means.
The tool covers Visa, Mastercard, American Express, and Discover in one search box. Enter a code. It returns the definition, the category, response guidance, and prevention tips.
So this article skips re-listing all 24 Discover codes. It focuses on the deadlines and the process instead.
Discover's three chargeback categories
Every Discover reason code falls into one of three categories. Those are fraud, processing errors and authorization, or service disputes. The category decides what evidence answers the dispute.
The table below maps each category to what triggers it and the proof that responds:
Most of the common codes you'll meet later sit in the service-disputes row.
Fraud
Fraud codes cover the UA0-series, where the cardholder denies making or authorizing the purchase. Your evidence here is authentication. Address verification, a matching descriptor, and device or IP records answer a fraud code.
An alert can often catch these before the cardholder files. A clear billing descriptor and strong authentication remove the reason someone claims not to recognize the charge.
Processing errors and authorization
Processing and authorization codes flag a charge that was handled or approved incorrectly. Think a duplicate or an authorization mismatch. These are mechanical disputes about how the charge posted. The product itself is beside the point.
You respond with proof the transaction was processed once. Show the right amount and a valid authorization. A clean processor record settles it.
Service disputes
Service-dispute codes are the largest group. They cover goods or service that weren't received, weren't as described, or were poor quality. Merchants see these most often, including AA, RG, and RM.
Your evidence is delivery confirmation and an accurate description of what the customer bought. If tracking shows delivery and the listing matched the item, you have your core response.
How long you have to respond to a Discover chargeback
Discover gives you a short, staged set of deadlines, and each reason code shares the same clock. Miss any one and the dispute can end in the cardholder's favor.
Merchants trained on Visa and Mastercard don't expect Discover's early retrieval-request stage. It's where they get caught.
Our Discover chargeback guide has the full deadline table by stage. It also covers the 540-day and two-year extensions that apply to a narrow set of codes.
Discover's dispute process differs from Visa and Mastercard
Discover is both the card network and the issuing bank. So it opens disputes with a retrieval request and bars cardholder contact. Visa and Mastercard do neither.
Discover is its own issuer, so it holds the cardholder's account and history. It can ask you for information before it files a chargeback. Some disputes get resolved at that stage and never become one.
That's the ticket retrieval request, or TRR. Visa and Mastercard largely retired it.
The no-contact rule comes from the same dual role. Discover owns the whole cardholder tie. So it bars any direct merchant-to-cardholder contact. Visa and Mastercard often expect the opposite.
Assume the wrong rule and you can turn a routine dispute into a compliance problem.
So the useful move on Discover is earlier warning. Both rules mean you want to know about a dispute before it becomes a chargeback. That's the case for chargeback alerts, which flag a dispute early enough to resolve it.
Our team can show you how Chargeback.io's alerts work on your own volume.
This dual role applies to real Discover-branded cards. A co-brand or partner-issuer card can act more like a Visa or Mastercard dispute. So check who issued the card first.
The most common Discover reason codes
Most Discover chargebacks cluster into a handful of codes. Mainly AA, RG, RM, DP, and the UA0-series fraud codes. The rest of the 24 codes exist, but these are the ones a typical merchant runs into.
Each one answers to a different kind of evidence. Service-dispute codes turn on delivery proof. DP turns on proof the charge wasn't a duplicate. The fraud codes turn on authentication and device data. Here's the common set:
- Code AA: the cardholder doesn't recognize the transaction.
- Code RG: goods, services, or cash weren't received.
- Code RM: the cardholder disputes the quality of what they got.
- Code DP: the same charge was processed more than once.
- The UA0-series fraud codes: the cardholder denies authorizing a card-not-present charge.
These are the common ones out of the full 24 codes. For the exact code on your own notice, use the lookup tool above. Our Discover chargeback guide, linked above, covers the full rules.
Another network runs this differently. Mastercard's reason codes use a separate four-digit system.
How we sourced this article
The time-limit and process claims here come from public secondary sources on Discover's published dispute rules.
Our platform alert dataset covers Visa and Mastercard codes. It has no Discover-specific breakdown, because Discover alerts are a small share of coverage. So this article stays qualitative on Discover and cites its sources. The Mastercard and Visa articles here carry a first-party percentage.
Where day-counts conflict across sources, we've flagged it and given the reported range.
FAQ
Can I contact the cardholder about a Discover dispute?
No, Discover prohibits direct merchant-to-cardholder contact during a dispute. Visa and Mastercard often expect the opposite, so a merchant used to them can break the rule.
What if you miss a Discover retrieval request deadline?
Missing the retrieval-request window can forfeit the dispute before it becomes a formal chargeback. It's an early deadline, easy to miss, because a retrieval request doesn't look like a chargeback notice.
Are Discover's codes the same as Visa or Mastercard's?
No, Discover uses its own alphanumeric codes, like AA and UA02. They aren't cross-mapped with Visa's numeric codes or Mastercard's four-digit codes.
Can you win a Discover chargeback without hiring help?
Yes, a merchant can respond alone, since the response is evidence matched to the category. The real limit is time, since gathering proof in a tight window is hard.
