Discover Chargeback Guide: Time Limits and Thresholds

A Discover chargeback lets a cardholder reverse a charge within 120 days, and merchants get 20 days to respond. Unlike Visa or Mastercard, Discover has no formally named monitoring program.

Merchants often treat Discover chargebacks as an afterthought. It's the smallest of the four networks in most mixes. Then a shared descriptor or a lapsed alert lets a dispute slip past the deadline unnoticed.

The rules are simpler than Visa's or Mastercard's. Simpler still leaves you exposed, because your Discover coverage is thinner to begin with.

Key takeaways

• Discover gives cardholders 120 days to file a chargeback, merchants 20 days to respond.
• A retrieval request carries a tighter 5-calendar-day deadline, before any chargeback exists.
• Discover has no named monitoring program, just an informal 1% ratio guideline.
• More than 100 chargebacks in a month can also flag your account as excessive.
• Reason codes RG, RM, and RN2 stretch the filing window to 540 days.
• Ethoca and CDRN each cover Discover through a single reason code only.

How are Discover chargebacks different?

A Discover chargeback runs on the same mechanics as a Visa or Mastercard one, but Discover uses its own reason codes and deadlines. The cardholder disputes a charge, the bank reverses it, and you get a window to respond. The rulebook underneath is what changes.

Discover often plays two roles at once. It runs the card network, and for many of its cardholders it's also the bank that issued the card.

Visa and Mastercard route a dispute through a separate issuing bank they don't own. Because Discover sits on both sides of its own disputes, it can move a case along without a third party. That's part of why its deadlines work differently.

One narrow case sits outside the pattern. Discover handles some transit disputes, aggregated small-dollar charges under reason code AC, differently from a single-purchase dispute. If you don't sell transit fares, you'll almost never see it.

How long do you have to respond to a Discover chargeback?

Discover cardholders have 120 days from the transaction date to file a dispute, and you then have 20 days to respond. If the case escalates, you get 30 days for a second chargeback and 30 to 45 days for arbitration. Each deadline starts from a different trigger.

Here are the windows that matter:

The cardholder's clock runs from the purchase date. Your clock runs from the date Discover notifies you. That gap is where merchants get caught.

A dispute can arrive months after the sale. Count your 20 days from the purchase, and you'll think you have less time than you do. Start counting the day the notice lands.

The 5-day retrieval-request window catches merchants off guard. Discover can send it before any chargeback is filed, and Chargeback Gurus notes that merchants generally have 5 calendar days to respond. A merchant watching only for chargebacks can miss it.

Some disputes can arrive well past 120 days and still be valid. Reason codes RG, RM, and RN2 extend the filing window to 540 days. A good faith fraud investigation can push it to two years.

How does Discover's chargeback threshold compare?

Discover has no formally named monitoring program, unlike Visa's Acquirer Monitoring Program (VAMP) or Mastercard's Excessive Chargeback and Excessive Fraud programs. Instead, Discover treats a chargeback ratio above roughly 1%, or more than 100 chargebacks a month, as excessive.

That contrast matters, because a named program comes with published rules and Discover's guideline doesn't.

Visa and Mastercard publish their thresholds as tiered programs with defined chargeback ratio triggers and fees. A merchant can see the escalation path in advance.

Discover's guideline is a general line, so crossing it leaves the consequences to its discretion. You might face increased monitoring, fines, or termination, decided case by case, with less warning than the other two give.

Here is how the three line up:

Each network tracks its threshold on its own. Clean standing on Visa or Mastercard says nothing about where you stand with Discover.

Retrieval requests: Discover's step before a chargeback

A retrieval request is Discover asking you for transaction records before it decides on a chargeback, and it has its own 5-calendar-day deadline. That window is shorter than the 20 days a chargeback gives you. Think of it as a question the issuer wants answered first.

Discover uses the retrieval request to clear up ambiguity without going straight to a dispute. Maybe a receipt is illegible, or a cardholder doesn't recognize a charge. A prompt, complete answer here can stop the dispute from ever becoming a chargeback.

This is also where a clear billing descriptor helps. Most "I don't recognize this" requests trace back to a statement line the customer couldn't place.

Missing the 5-day deadline costs you the chance to settle the question before the case turns into a formal dispute. It doesn't create a chargeback by itself, but a non-response skips the cheapest place to win.

Discover chargeback reason codes

Discover sorts its chargeback reason codes into three categories, and each one needs different evidence to contest. The category tells you what actually defeats the dispute. One evidence packet for every chargeback is how merchants lose winnable cases. The three groups are:

• Service disputes: the cardholder says the goods or services weren't delivered as described.
• Fraud: the cardholder says they didn't authorize the transaction.
• Authorization and processing errors: a technical or procedural mistake handling the charge.

Our Discover chargeback reason codes guide lists every code and the evidence it needs.

You can also look up any reason code across all four networks in our free tool.

Service dispute codes

Service dispute codes cover charges where the cardholder got the product but says it wasn't what they were promised. Winning means proving delivery matched the offer, with order confirmations, tracking, agreed terms, and messages showing the goods arrived.

Fraud codes

Fraud codes cover charges the cardholder says they never authorized. The evidence that wins proves the cardholder made the purchase. Think AVS and CVV matches, 3D Secure, device or IP data, and a delivery address tied to them.

Authorization and processing error codes

Authorization and processing error codes flag a technical or procedural problem, not a customer complaint. These turn on whether the transaction was authorized and processed correctly. The winning evidence is the authorization record, the processing logs, and proof the charge followed the rules.

The Discover coverage stack

Closing the Discover dispute gap takes two layers working together, and neither covers it alone. The first is alert-based prevention from Ethoca and CDRN. The second is descriptor and matching accuracy that keeps a Discover charge from looking unfamiliar. The two layers are:

• Ethoca and CDRN alerts: partial Discover coverage that catches some disputes early.
• Descriptor and matching accuracy: the fix that stops a dispute before an alert is needed.

Neither alert network was built with Discover as its home brand. Ethoca is Mastercard's own vendor. CDRN is a product of Verifi, which Visa owns. Each one added Discover coverage on top of a system built for another brand.

So if you lean on either network alone for Discover, you're covered against only a narrow slice of disputes. If Discover is a small part of your mix, that thinner coverage can be a fair tradeoff. Both layers matter most when Discover volume is large enough to move your ratio.

What Ethoca and CDRN actually cover on Discover

Ethoca and CDRN each reach Discover through a single reason code, so their coverage there is thin.

Ethoca Alerts guide puts its Mastercard coverage at about 95%, with only limited Discover coverage through one code. CDRN guide puts its US-based Visa coverage at about 95%, with the same single-code limit on Discover.

That is easy to miss. A merchant who set up alerts for Visa and Mastercard often assumes the coverage carries to Discover. It doesn't.

That guide has the full mechanism behind how Ethoca Alerts work.

The second layer covers what the alerts leave open. The CDRN guide above shows why its single-code Discover reach isn't enough alone.

Closing the gap with descriptor accuracy

A clear billing descriptor and accurate transaction matching close the part of the Discover gap that alerts can't reach. Alerts intercept a dispute the customer already started. Descriptor accuracy stops it from starting, because a cardholder who recognizes the charge doesn't call their bank.

This is the cheaper layer, and the one merchants skip most. On my own stores, fixing what customers saw on their statement did more for my chargeback rate than any single alert.

For a Discover-heavy merchant, tightening the descriptor closes the disputes single-code alerts leave open.

Our chargeback prevention stack pairs both layers so your Discover disputes get the same protection as the rest of your mix.

FAQ

Does Discover favor merchants in chargeback disputes?

Discover applies the same threshold and evidence standard to every merchant. Stories about Discover siding with merchants describe a single case, while the rule stays the same for everyone.

What happens if you go over Discover's chargeback threshold?

Crossing Discover's excessive line can trigger increased monitoring, fines, or account termination. Discover decides the consequence case by case rather than through a published escalation schedule.

Can you dispute a Discover chargeback after the deadline?

Once your 20-day response window closes, you generally lose the right to contest that chargeback. The deadline is firm, which is why tracking the notification date matters more than the transaction date.

Do Discover chargebacks count against other networks?

No, each network tracks your chargeback ratio on its own. A Discover problem won't raise your Visa or Mastercard standing, though the root cause often hits every network at once.