Discover Reason Code RN2: Credit Not Received

What Discover reason code RN2 means

RN2 is a cardholder dispute about a missing refund. The cardholder says you agreed to give them a credit, or owed them one, and it never showed up. The usual story: they returned an item or cancelled an order or booking, and nothing came back.

Sometimes the refund really is missing. Often it was issued but hadn’t posted yet when the cardholder checked, or the cardholder expected a refund your policy didn’t promise.

Common causes

• A refund issued but not yet visible on the statement when the cardholder disputed
• A return received at the warehouse but never matched to the order, so no refund was triggered
• A return that was never sent, or arrived outside the return window
• Non-refundable items, restocking fees or store credit that the cardholder expected as cash back
• A cancellation confirmed by support that never reached billing

Evidence that wins an RN2 dispute

1. Refund already processed: the refund transaction with date, amount and reference number (an acquirer reference number if your processor provides one), dated before the dispute.
2. Return status: if no refund was owed, show the return was never received, using the return label tracking or warehouse log.
3. Return policy and disclosure: the policy the cardholder accepted, including windows, condition requirements, restocking fees and non-refundable items.
4. Store credit or exchange records: if the cardholder accepted store credit or an exchange instead of a refund, show it.
5. Communications: the support thread showing exactly what you promised. If you promised a refund on return and the return never came, the thread proves it.

A dated timeline is often the whole case. Refunds can take several business days to appear on a statement, so a dispute filed shortly after you refunded is answered by the dates alone:

How to prevent RN2 chargebacks

• Email a refund confirmation with the amount and reference number the moment you process it, and tell customers it can take several business days to appear.
• Match returns to orders automatically on receipt, and alert on returns sitting unprocessed.
• State non-refundable items and restocking fees at checkout, not only in the policy page footer.
• Make sure cancellations promised by support trigger the refund the same day.

Should you fight or accept?

Fight when you already issued the refund before the dispute, or when your disclosed policy meant no refund was owed and you can show it. Don’t refund again after the chargeback arrives. See chargeback after a refund.

Accept when the cardholder returned the item under your policy and the refund was never processed. The dispute is valid and accepting it returns the money. DisputeDash can fight disputes on already-refunded orders automatically, attaching refund-confirmation evidence to the rebuttal.