Ontdek de redencodes voor terugboekingen (Gids voor handelaren 2026)

Discover chargeback reason codes are the alpha labels (such as AA, RG or UA02) and four-digit numeric values (such as 4752, 4755 or 7030) that tell a merchant why a Discover cardholder disputed a transaction and which evidence a response needs. The code on the case notice decides the defense, and the processor's reply-by date decides how long you have to submit it.

The card network, issuing bank and merchant processor have different roles. Discover-branded payments use the Discover network, while the merchant's evidence submission follows the applicable processor or acquirer's case process.

Use the allegation, evidence and applicable dispute process to assess a case. The card brand or company ownership alone does not establish how an issuer will decide it.

{{cta}}

Ontdek de uitleg bij de redencodes voor terugboekingen

Discover reason codes identify why a payment is disputed. Code formats and processor mappings can differ, so use the value and evidence requirements on the case notice rather than assuming every case uses the same legacy label.

Discover groups its codes into four families: fraud, processing errors, authorization and cardholder (service) disputes, plus a Not Classified code for cases outside those groups. Tracking which family drives your disputes shows whether the fix sits in fraud screening, payment operations or customer service, and the same main types of chargebacks appear across every card network.

Discover Numeric Reason Codes and Their Alpha Equivalents

Many processors show Discover disputes as four-digit numbers instead of alpha labels, so a merchant can see 4755 on one dashboard and RG in a network document for the same allegation. The table below lists the numeric values that processor documentation publishes for Discover, paired with the alpha code that carries the same reason name. First Data's (now Fiserv) merchant dispute guide pairs 4752 with AA, 7010 with UA01, 7030 with UA02, 4866 with UA05 and 4867 with UA06 directly; the remaining pairs match by reason name.

Sources: numeric values and names from TabaPay's Discover reason code list and Rainforest's dispute reason reference; Braintree's reason code reference notes that its own Discover list, generated September 22, 2025 from codes actively received, can change and may not include every current value. Processors also pass Discover document requests with their own values, such as 6021 (Transaction Documentation Request), 6005 (Transaction Documentation Request Due to Cardholder Dispute), 6041 (Transaction Documentation Request for Fraud Analysis) and 6040 (Good Faith Investigation). These are requests for records, not chargebacks, but an unanswered request can cost you the right to dispute the chargeback that follows.

Ontdek het chargeback-proces ontrafeld

Discover became part of Capital One on May 18, 2025; Capital One's Discover FAQ explains that the brand and accounts continue. Merchant dispute submissions still follow the actual processor or acquirer's case process; do not infer the response channel solely from the card brand.

Follow the case notice for the evidence channel and any restrictions on customer contact. Submit through your processor or acquirer by its reply-by date; do not assume every Discover dispute is handled directly with the issuing bank.

A Discover dispute reaches the merchant in one of two forms: a Ticket Retrieval Request (TRR), which asks for transaction records before any money moves, or an outright chargeback. A TRR works like an inquiry in Visa Resolve Online, and our guide to the retrieval request covers how to answer one. Discover's own consumer guide defines a chargeback as a statement credit the cardholder receives from the card issuer after a dispute, and notes that a merchant that disagrees may appeal it. After a chargeback, the case follows the standard life cycle:

• The merchant accepts the chargeback or responds with evidence (representment).
• The issuer reviews the evidence and decides for the cardholder or the merchant.
• If either side still disagrees, the case can move to pre-arbitration and arbitration under Discover's chargeback rules.

Discover Chargeback Time Limits at Each Stage

Three separate clocks run on a Discover dispute, and only the last one is yours:

• Cardholder to issuer: for US credit cards, Regulation Z requires a billing error notice to reach the card issuer within 60 days after the issuer sent the first statement showing the charge (CFPB, 12 CFR 1026.13). Unauthorized-use claims can follow different rules.
• Issuer to network: First Data's merchant dispute guide lists 120 calendar days for AA, UA01, UA02, UA05 and UA06, counted from the processing date (the central processing date for UA06).
• Merchant to processor: your processor sets the reply-by date. Adyen, for example, lists 25 days from receiving the notification of chargeback for 4752 (Does Not Recognize), and Braintree accepts the dispute on your behalf if you do not respond by the reply-by date.
• Retrieval requests and records: the same First Data guide states that AA, UA01 and UA02 chargebacks cannot be reversed when the merchant failed to answer the ticket retrieval request, and that Discover requires a two-year record retention time frame.

For cardholder-side timing, exceptions and stage-by-stage merchant steps, see our full guide to Discover chargeback time limits and rules.

Ontdek informatie over fraude Chargebacks

Fraud codes mean the cardholder says they did not authorize or take part in the transaction. Discover's fraud codes are:

• Reason Code UA01: Fraud, Card-Present Transaction (numeric 7010; Braintree mapping 4537 from April 17, 2026): the cardholder claims someone used their card for an unauthorized in-person transaction.
• Reason Code UA02: Fraud, Card-Not-Present Transaction (numeric 7030; Braintree mapping 4868 from April 17, 2026): the cardholder alleges a fraudulent online, phone or mail order, the most common form of card-not-present fraud.
• Reason Code UA05: Fraud, Chip Card Counterfeit Transaction (numeric 4866): the cardholder disputes a counterfeit-card transaction, typically where a chip card was processed without a chip read.
• Reason Code UA06: Fraud, Chip and PIN Transaction (numeric 4867): the cardholder denies a transaction made with a lost or stolen chip-and-PIN card at a terminal that was not PIN-capable.
• Reason Code UA10: Request Transaction Receipt (swiped card transactions): the issuer requests documentation for a card-present transaction the cardholder claims was unauthorized.
• Reason Code UA11: Cardholder Claims Fraud (swiped transaction, no signature): the customer claims fraud on a card-present transaction with no signature on record.

How to Respond: Keep detailed records of each transaction: order information, customer communications, delivery confirmation where applicable, and the fraud checks you ran, such as IP address logs or CVV verification results.

How to Prevent: Use Address Verification Service (AVS), CVV checks, 3D Secure for online transactions and monitoring for unusual order patterns, and train staff to spot common fraud signals. Our ecommerce fraud prevention guide covers a fuller set of controls.

Ontdek een fout bij de betalingsverwerking Chargebacks

Processing error chargebacks mean the transaction was submitted with a mistake, regardless of whether the cardholder received what they paid for. These include:

• Reason Code IN: Invalid Card Number (numeric 4753): the card number on the transaction is not associated with a valid cardholder account.
• Reason Code LP: Late Presentation (numeric 4542): the merchant submitted the transaction after the allowed time limit.

Submit completed transactions to your processor promptly, ideally on the day of sale, and check the card number and final amount before settlement. Train staff on correct transaction procedures and keep accurate records so you can show when each sale was presented.

Ontdek autorisatie Chargebacks

Authorization chargebacks mean the merchant processed a transaction without a valid approval, processed it after a decline, or charged more than the approved amount. Discover's authorization codes are:

• Reason Code AT: Authorization Non-Compliance (numeric 4863): the merchant processed the transaction without a valid authorization response, or with an authorization obtained after the card's expiration date.
• Reason Code DA: Declined Authorization: the merchant processed the transaction after the authorization request was declined.
• Reason Code EX: Expired Card: the card had expired at the time of the transaction.
• Reason Code NA: No Authorization: the merchant skipped the authorization request, retried a declined card repeatedly, or tried to override a decline.

Request authorization on every transaction, never force a declined sale through, and re-authorize when the final amount or shipping date changes materially from the original approval.

Ontdek geschillen over dienstverlening

Service dispute codes mean the cardholder has a complaint about the purchase itself: an item that never arrived, arrived not as described, or was billed incorrectly. Discover's cardholder dispute codes are:

• Reason Code AA: Does Not Recognize (numeric 4752): the cardholder does not recognize the transaction on their statement. A clear billing descriptor prevents many of these.
• Reason Code AP: Cancelled Recurring Transaction (numeric 4541): the cardholder disputes a charge tied to recurring payments, claiming they cancelled before you billed them.
• Reason Code AW: Altered Amount (numeric 4586): the cardholder claims the transaction amount differs from the amount they authorized.
• Reason Code CD: Credit/Debit Posted Incorrectly (numeric 4550): the cardholder claims you processed a debit instead of a credit, or a credit instead of a reversal. See the difference between a refund and a reversal to post the right one.
• Reason Code DP: Duplicate Processing (numeric 4534): the customer says you processed one transaction more than once.
• Reason Code IC: Illegible Sales Data: the sales receipt you supplied could not be read, for example because of faded ink, colored paper or a reduced-size scan.
• Reason Code NF: Non-Receipt of Cash from ATM (numeric 4864): the cardholder did not receive the full cash amount from an ATM withdrawal.
• Reason Code PM: Paid by Other Means (numeric 4865): the cardholder says they already paid for the purchase with a different payment method.
• Reason Code RG: Non-Receipt of Goods or Services (numeric 4755): the cardholder claims they did not receive goods or services they paid for.
• Reason Code RM: Quality Discrepancy (numeric 4553): the cardholder alleges the goods or services were defective or not as described.
• Reason Code RN2: Credit Not Received (numeric 8002): the cardholder returned merchandise or cancelled a service, but no credit was issued.

Niet-geclassificeerde Discover-code voor reden van terugboeking

Reason Code NC (Not Classified) covers a dispute that does not fit any category above. It often appears when the circumstances are unclear but the issuer still treats the transaction as invalid, and the cause can be a merchant error, friendly fraud or true fraud.

Prevention depends on the specific circumstances, so read the case notice closely before choosing evidence. Get the full details on the Discover Not Classified reason code.

Evidence to Review for Each Discover Reason Code

The reason code tells you which evidence the issuer will weigh. Match your submission to the allegation rather than sending a generic packet; a chargeback response template helps you structure it.

Before you respond, confirm the code and reply-by date on the actual case notice, and check whether an earlier refund already resolved the dispute. Many of these disputes can be stopped before they become chargebacks with chargeback alerts, which give you a window to refund instead of fight.

{{cta}}

Discover Chargeback Reason Code FAQs

What qualifies as a chargeback on a Discover credit card?

A Discover chargeback qualifies when a cardholder disputes a transaction with the card issuer for a reason covered by Discover's dispute rules, such as fraud (UA01, UA02), a charge they do not recognize (AA), goods not received (RG), goods not as described (RM), a missing credit (RN2) or a processing error (IN, LP). The issuer then reverses the funds from the merchant, and the merchant can accept the loss or respond with evidence by the processor's reply-by date.

Is there a 120-day limit for Discover chargebacks?

There is no single filing limit that applies to every Discover case. The historical guide cited here gives examples for specific codes; confirm current rules and the relevant starting event with your processor. First Data's Discover dispute guide lists 120 calendar days from the processing date for issuers to file AA, UA01, UA02, UA05 and UA06 chargebacks. Separately, US credit cardholders must send a billing error notice within 60 days after the first statement showing the charge under Regulation Z, and the merchant's own deadline is the reply-by date set by its processor.

Can a Discover cardholder dispute a charge from 3 months ago?

A Discover cardholder can sometimes dispute a charge from 3 months ago. The 60-day Regulation Z billing error window runs from the statement date, so a charge on an older statement may fall outside it, but the issuer's network filing window for fraud and "does not recognize" codes is 120 calendar days from processing. The linked historical guide describes a two-year retention period. Confirm current retention requirements, privacy obligations and the applicable case windows with your processor.

What do Discover reason codes 4755, 4866, 7030 and 8002 mean?

Discover numeric reason codes are processor values for the same reasons as Discover's alpha codes: 4755 is Non-Receipt of Goods or Services (RG), 4866 is Fraud, Chip Card Counterfeit Transaction (UA05), 7030 is Fraud, Card-Not-Present Transaction (UA02) and 8002 is Credit Not Processed (RN2). For card-not-present fraud disputes initiated on or after April 17, 2026, Braintree shows 4868 in place of 7030.

Are Discover reason codes the same as Visa or Mastercard reason codes?

Discover reason codes are not the same as Visa or Mastercard reason codes. Visa uses numeric codes such as 10.4 and 13.1, Mastercard uses four-digit codes such as 4837 and 4853, and Discover uses alpha codes such as UA02 and RG, which processors often translate into their own four-digit values. The underlying allegations overlap, so the evidence for a fraud or non-receipt claim is similar across networks even when the code differs.

Match Each Discover Code to Its Evidence Before the Reply-By Date

A useful Discover response starts with reading the exact code on the case notice, mapping it to its alpha or numeric equivalent and submitting evidence that answers that specific allegation before the processor's reply-by date. For every Discover code in one place, use the Chargeflow chargeback reason codes directory.

Contact our sales team for details on recovering chargebacks on autopilot.