Discover chargeback reason codes

How Discover disputes work

Discover operates its own card network. Many merchants still receive Discover disputes through their acquirer or processor (for example Stripe, Shopify Payments or Chase), because those providers accept and settle Discover on the merchant's behalf. Verdikx is a fraud, chargeback and dispute platform for e-commerce and SaaS merchants; this guide covers the Discover codes your processor will show.

A Discover dispute usually moves through these stages:

1. Ticket Retrieval Request (inquiry). The issuer asks for transaction documents. Stripe's documentation lists Discover among the networks that most often use an inquiry phase, and warns that Discover inquiries left unanswered can turn into disputes you cannot challenge.
2. Chargeback. The disputed amount is debited, with a reason code such as UA02 or RG.
3. Representment. You answer with evidence. Chase's guide notes that Discover reviews a representment before accepting it, so merchants are not credited immediately.
4. Arbitration. Possible in some cases, but many processors (Stripe included) do not support escalating that far.

For fraud codes UA01 and UA02, Chase's guide states the issuer must process a ticket retrieval request before initiating the chargeback, and if that request was not answered the chargeback has no representment rights. Answering inquiries quickly is the single most useful habit on Discover.

Time limits

• Cardholder filing window: 120 calendar days from the transaction date for most codes in Chase's Discover table. Non-receipt (RG) and quality (RM) disputes run 120 days from the scheduled delivery, capped at 540 days from the transaction.
• Recurring payments (AP): the cancellation must have happened at least 15 calendar days before the disputed charge posted.
• Merchant response: processor documentation such as Solidgate's lists 20 days on the acquirer and merchant side for fraud disputes. Your processor's deadline is usually shorter, so use the date on the case.

The code families

• Fraud (UA01, UA02, UA05, UA06, UA10, UA11): UA02 card-not-present fraud is the one online stores see most. Defending it requires positive AVS, CID and delivery to the AVS address.
• Authorization (AT, DA, EX, NA): the sale was not properly authorized, was declined, used an expired card or skipped authorization.
• Processing errors (IN, LP, DC): invalid card number, late presentment, or a Discover operating regulations violation.
• Service / cardholder disputes (AA, AP, AW, CD, DP, PM, RG, RM, RN2, 05): recognition, recurring billing, amounts, duplicates, non-receipt, quality and credits.
• Not classified (NC): claims that fit no other code.

How Verdikx helps with Discover disputes

• Discover disputes from Shopify Payments and Stripe are imported automatically; Braintree, Adyen and Checkout.com are in beta, and notices from any processor can be forwarded by email or CSV.
• Each case gets a reason-code playbook and evidence checklist, AVS and CVV results where your processor shares them, delivery proof, and an AI draft you review before submitting.
• Customer conversations (helpdesks, beta), subscription records (Recharge, Skio, Bold, Recurly, Chargebee, beta) and Loop returns (beta) fill in the evidence for AP, RG, RM and RN2.

Verdikx does not decide outcomes: Discover and the issuer do. See chargeback management.