Discover Chargeback Guide for Merchants: Reason Codes, Deadlines & How to Win
Discover processes chargebacks differently from Visa and Mastercard — as both the card network and the issuer for most Discover cards, the company controls the entire dispute lifecycle. This gives merchants fewer escalation opportunities but also means faster, more predictable outcomes. This guide covers every aspect of Discover chargebacks for merchants: reason codes, timelines, evidence requirements, and how to win disputes.
AI-generated Discover dispute responses
Upload your evidence — ChargeMate writes the rebuttal letter for you.
How Discover Chargebacks Work
Unlike Visa and Mastercard, Discover Financial Services acts as both the card network and the primary card issuer. This means there is no separate issuing bank intermediary in most cases — Discover both initiates the dispute and makes the final ruling. For merchants, this has two important implications: the process is faster and more streamlined, but there is no independent third party to appeal to if Discover rules against you.
The dispute cycle begins when a cardholder contacts Discover to dispute a transaction. Discover reviews the claim, determines whether it qualifies as a chargeback, and notifies the merchant via their payment processor. The merchant then has 20 days to submit a rebuttal — shorter than Visa's 30 days or Mastercard's 45 days. This tighter window is one of the most common reasons merchants miss Discover disputes, especially those used to other networks' timelines.
Key facts about the Discover dispute process
- →Discover is both network and issuer — no bank intermediary for most cards
- →Cardholder has 120 days from the transaction date to file
- →Merchant response window is 20 days (shorter than all major networks)
- →Pre-arbitration (appeal) is available within 30 days of the initial decision
- →Discover processes approximately 4% of US card volume — disputes are lower volume but still count toward your chargeback ratio
Discover Chargeback Reason Codes
Discover uses alphanumeric reason codes that map directly to dispute categories. Understanding the code on your chargeback notification tells you exactly what evidence you need to submit. Below is a complete reference table followed by merchant-focused context for each code.
| Code | Category | Description |
|---|---|---|
| UA01 | Fraud | Card Present fraud — card used in-person without authorization |
| UA02 | Fraud | Card Not Present — online/phone transaction disputed as unauthorized |
| UA05 | Fraud | Counterfeit card used at terminal |
| UA06 | Fraud | Chip & PIN transaction disputed |
| UA38 | Fraud | Partial Immediate Chargeback — partial amount dispute |
| AT | Authorization | Authorization non-compliance — transaction processed without proper auth |
| RN1 | Credit | Credit not processed — merchant refund not received by cardholder |
| RN2 | Credit | Credit not processed — second attempt |
| RM | Quality | Merchandise/service quality dispute |
| NF | ATM | Non-receipt of cash at ATM |
| IN | Invalid | Invalid card number used |
| DA | Declined | Declined authorization — transaction processed after decline |
| EX | Expired | Expired card used |
Customer claims they did not make an in-store purchase. Common in card-present environments where EMV chip was not used.
The most common code for eCommerce merchants. Customer claims they did not authorize the online or phone order.
A cloned or counterfeit card was used at your physical terminal. Liability typically shifts to the merchant if chip was not read.
Customer disputes a chip-and-PIN transaction. Terminal logs and PIN verification records are critical evidence.
Only part of the transaction amount is disputed. Often occurs with split shipments or partially delivered services.
Transaction was processed without obtaining a valid authorization, or after an authorization had expired or been declined.
Merchant issued a refund but the credit did not appear on the cardholder's statement within the expected timeframe.
Follow-up to RN1. Filed when the cardholder still has not received credit after the first dispute cycle.
Customer claims goods or services were not as described, defective, or not delivered. Requires documentation of what was sold and delivered.
Cardholder did not receive the full cash amount from an ATM transaction. Primarily affects ATM operators.
Transaction was processed with a card number that does not exist or is invalid. Review your payment gateway logs.
Transaction was completed despite a prior authorization decline. Strong evidence of merchant error; difficult to win without proof of a subsequent approval.
Transaction was processed on an expired card. Review your gateway settings to ensure expired cards are rejected at checkout.
Discover Chargeback Deadlines
The 20-day merchant response window is the most critical deadline to monitor. Missing it means automatic acceptance of the chargeback — Discover will not accept late submissions regardless of how strong your evidence is.
| Milestone | Timeline |
|---|---|
| Cardholder filing window | 120 days from transaction date |
| Merchant response deadlineCritical | 20 days from notification |
| Discover review period | 30–45 days after submission |
| Pre-arbitration filing window | 30 days after initial decision |
| Total resolution time | 60–90 days typically |
Set up automated alerts in your payment processor dashboard so you are notified immediately when a Discover dispute is filed. Many processors allow email or webhook notifications — configure these so you have the full 20 days available to gather evidence.
Evidence Requirements by Reason Code
Discover evaluates evidence based on how directly it refutes the specific claim made by the cardholder. Generic evidence — such as an unsigned receipt submitted for a CNP fraud claim — is routinely rejected. Match your evidence to the code.
| Code(s) | Required Evidence |
|---|---|
| UA01 / UA02 | Signed receipt or cardholder agreement, AVS and CVV match confirmation, IP address logs, device fingerprint, delivery confirmation with recipient signature |
| UA05 / UA06 | Terminal transaction logs showing chip data was read, PIN verification records, EMV transaction receipt |
| UA38 | Itemized transaction breakdown, partial delivery confirmation, cardholder acknowledgment of partial receipt |
| AT | Authorization approval code, transaction records showing auth was obtained, processor authorization log |
| RN1 / RN2 | Credit memo, refund confirmation from your processor, date and amount of refund issued |
| RM | Detailed product or service description, photos, delivery confirmation, written communication with customer, your refund/return policy |
| DA | Proof that a subsequent authorization was obtained, approval code for the final transaction, processor records |
| EX / IN | Transaction logs showing card data accepted, payment processor records, any gateway override records |
How to Win a Discover Chargeback
Winning a Discover dispute requires a methodical approach. Because Discover controls the entire process, your submission needs to be clean, complete, and directly relevant to the reason code. Follow these steps for every dispute.
Review the reason code immediately
Each code requires specific evidence. Do not start gathering documents until you know exactly which code you are responding to. Check the chargeback notification from your processor — the code will be listed there.
Gather your evidence within 48 hours
You have 20 days, but start immediately. Some evidence — like server logs or carrier tracking — can disappear or become harder to access over time. Pull delivery records, payment logs, and any customer communication within two days of receiving the dispute.
Write a concise rebuttal letter
Address the specific reason code directly. State what happened, reference your evidence by document, and explain why the chargeback is not valid. Keep it under two pages — Discover reviewers read many submissions and reward clarity.
Submit via your payment processor's dispute portal
Do not contact Discover directly. All submissions go through your acquiring bank or processor. Follow their file format requirements — PDF is almost universally accepted; some processors have file size limits.
Follow up if you do not receive confirmation within 5 business days
Processor portals can have technical issues. If you do not receive a submission confirmation within five business days, call your processor to verify receipt. A missed confirmation can mean your evidence was never received.
Key tips for Discover disputes
- •Keep delivery confirmation records for at least 180 days after each transaction.
- •For UA02 (CNP fraud), AVS and CVV match data is often the single most important piece of evidence.
- •Irrelevant evidence does not just fail to help — it can make your submission look unfocused and hurt your case.
- •If you issue a refund before responding, document it thoroughly — it can resolve the dispute faster.
Discover vs Visa vs Mastercard
Merchants who handle disputes across multiple networks need to adjust their processes for each one. The differences in response windows and process structure are significant.
| Feature | Discover | Visa | Mastercard |
|---|---|---|---|
| Merchant response deadline | 20 days | 30 days | 45 days |
| Cardholder filing window | 120 days | 120 days | 120 days |
| Issuer / network relationship | Same entity | Separate | Separate |
| US market share (approx) | ~4% | ~47% | ~26% |
| Arbitration | Discover decides | Network arbitrates | Network arbitrates |
| Pre-dispute programs | Limited | RDR (Visa) | Ethoca |
Market share figures are approximate and based on US transaction volume data.
Common Mistakes Merchants Make with Discover Disputes
These mistakes account for the majority of preventable Discover chargeback losses:
✗Missing the 20-day deadline
Merchants accustomed to Visa (30 days) or Mastercard (45 days) often miss Discover's shorter window. An automated alert for every new dispute notification is essential — do not rely on manual monitoring.
✗Submitting generic or irrelevant evidence
Sending a signed receipt in response to a UA02 (Card Not Present) dispute makes no sense — there is no in-person receipt for an online transaction. Review the code and build your evidence package around it specifically.
✗Not providing AVS/CVV match data for CNP disputes
For UA02 cases, gateway-level AVS and CVV match results are among the strongest evidence you can provide. Many merchants have this data but do not think to include it. Pull it from your payment gateway's transaction detail page.
✗Ignoring Discover disputes because of low volume
Discover represents roughly 4% of US card volume, so merchants often see only a handful of Discover disputes per month. But every dispute — regardless of network — counts toward your overall chargeback ratio. Ignoring small-volume networks can push you over the threshold that triggers processor reviews.
Want AI-generated Discover dispute responses?
ChargeMate generates network-compliant rebuttal letters for Discover, Visa, Mastercard, and Amex disputes. Upload your evidence and get a ready-to-submit response in minutes.
Frequently Asked Questions
How long do I have to respond to a Discover chargeback?▾
Does Discover favor merchants or cardholders?▾
What is the most common Discover chargeback reason code?▾
Can I appeal a Discover chargeback decision?▾
ChargeMate
Win more Discover disputes — automatically
AI-generated dispute responses tailored to every Discover reason code. 3 free responses included with every account.
Try free → 3 responses included