Discover Chargeback Reason Codes
Updated July 2026
Discover chargeback reason codes are two-letter abbreviations — UD, RG, AP, RM — that identify what a cardmember is disputing. Because Discover is a closed-loop network (both the card issuer and the network), it uses its own code set and dispute rules, separate from Visa and Mastercard. For merchants, the key practical difference is the code format: where Visa uses decimal codes like 10.4 and Mastercard uses four-digit codes like 4837, Discover uses short letter codes. The response deadline is 30 days — the same as Visa.
How the Discover dispute process works
When a cardmember disputes a charge, Discover sends the merchant a chargeback notice through the acquiring bank or processor. The notice identifies the reason code, the dispute amount, and a response deadline. Merchants submit evidence through their processor — Stripe, Square, Shopify Payments, or a direct acquirer — before that date.
Discover handles disputes as the network and as the card issuer, meaning it has access to both sides of the transaction. Match your evidence to the specific code rather than sending a generic packet.
Check your processor dashboard for the exact deadline. The 30-day window is measured from the chargeback date, but your processor may show a shorter internal cut-off. Submit well before the date shown on your dispute screen.
Common Discover chargeback reason codes
These are the codes most merchants encounter. Verify the exact code and its current requirements in your processor dashboard, since Discover updates its dispute rules over time. For per-code evidence details, see the reason code library.
| Code | What the cardmember is claiming | Evidence that answers it |
|---|---|---|
| UD | Did not authorize or recognize the transaction | AVS/CID match, device and IP records, delivery confirmation, clear billing descriptor |
| AA | Does not recognize the charge on their statement | Merchant name on billing descriptor, order details tying the charge to the cardmember |
| UA | Transaction was fraudulent or unauthorized (sub-variants: UA01 card present, UA02 card not present, UA05/UA06 chip) | For UA02: AVS/CID match, device/IP evidence. For UA01/UA05/UA06: EMV chip or PIN acceptance records |
| RG | Did not receive the goods or services | Carrier tracking with delivery confirmation, or timestamped access/download logs for digital goods |
| RM | Received goods or services that were not as described | Product listing as shown at checkout, proof the delivered item matched, return policy and any resolution offered |
| AP | Cancelled a recurring or subscription charge | Subscription terms accepted at sign-up, no-cancellation-received records, login or usage activity during the billed period |
| CD | Expected a credit or refund that did not post | Refund confirmation and settlement date, or the accepted policy showing no refund was owed |
| DP | Transaction was charged more than once | Distinct order IDs and authorization codes proving each charge was a separate purchase; refund any genuine duplicate first |
For per-code detail, see the reason code library — including UD, RG, AP, and UA.
The 30-day deadline: respond promptly
Discover gives merchants 30 days to respond — the same window as Visa and shorter than Mastercard's 45 days. The deadline is strict. Missing it means the dispute resolves against you regardless of your evidence.
Start gathering documents as soon as the notice arrives. For a side-by-side comparison of every network's timeline, see the chargeback response deadlines guide.
Your processor may show a shorter cut-off. Stripe, Square, and Shopify Payments each add processing time before your response reaches Discover. Respond at least a few days before the date shown in your processor dashboard.
How to respond to a Discover reason code
Match your evidence to the specific code. A UD fraud dispute needs authentication data; an RG non-receipt dispute needs delivery proof. Sending the wrong evidence wastes your one chance to respond.
Identify the exact code
The reason code in your processor dashboard determines what evidence to gather. UD and UA are fraud disputes; RG is non-delivery; RM is quality or description; AP is a recurring billing dispute.
For UA, check the sub-variant
UA splits into UA01 (card-present), UA02 (card-not-present), and UA05/UA06 (chip-transaction). Each calls for different evidence: chip-and-PIN records for card-present; authentication and delivery data for card-not-present.
Write a focused rebuttal
A short cover letter that references the reason code, maps each exhibit to the cardmember's claim, and asks for reversal reads better than a long, general argument. See the rebuttal letter guide for structure and tips.
Submit before the deadline
Upload your complete evidence through your processor's dispute portal. You cannot add documents after submission, so include everything the code requires the first time.
Frequently Asked Questions
How long do I have to respond to a Discover chargeback?↓
What is Discover reason code UD?↓
How are Discover reason codes different from Visa and Mastercard?↓
What is Discover reason code UA?↓
What are the most common Discover chargeback reason codes?↓
Build a Code-Specific Evidence Pack
ChargebackKit assembles your evidence into an organized pack — rebuttal letter, labeled exhibits, and submission checklist — matched to your specific Discover reason code.
Run the Free Evidence-Readiness CheckRelated Resources
- Discover UD: Unauthorized / Disputed — Evidence & How to Win
- Discover RG: Non-Receipt of Goods or Services
- Discover AP: Recurring Payments — Evidence & How to Win
- Discover UA: Fraud Sub-Variants (UA01/UA02/UA05/UA06)
- Chargeback Reason Code Library — All Networks
- American Express Chargeback Reason Codes: Merchant Guide
- Chargeback Response Deadlines by Card Network
- Chargeback Rebuttal Letter: How to Write One That Wins
- How to Win a Chargeback: The Complete Guide
- Preview a Sample Evidence Pack