Discover · Processing Errors
Reason code CD: Credit/Debit Posted Incorrectly
A transaction posted with the wrong sign: the merchant processed a sale when the cardholder was owed a credit, or processed a credit as a debit. The cardholder's account moved in the opposite direction from what both parties intended. Discover uses CD to force the posting back to what it should have been.
Issuer filing window
typically 120 days from the processing date
Merchant response window
typically 30 days to respond
Why CD chargebacks happen
- A refund was keyed as a new sale in the virtual terminal, charging the customer a second time instead of crediting them.
- A reversal file or batch was submitted with an incorrect transaction type code.
- Staff selected the wrong function on a terminal when processing a return.
- An integration bug in your payment stack mapped refund API calls to purchase transactions.
- A correction attempt for an earlier error compounded it by posting in the wrong direction again.
How to fight a CD chargeback
- First verify your records; if the debit genuinely should have been a credit, process the correcting credit immediately and accept the chargeback or show proof of the correction.
- If the posting was actually correct, submit the sales record demonstrating the transaction was a legitimate purchase, not a refund situation.
- Provide the full transaction history for the account showing every debit and credit with dates and amounts to prove nothing posted incorrectly.
- Show the refund was already issued through another channel if the customer double-dipped by disputing after receiving their credit.
- Include batch and settlement reports that reconcile the disputed item to the intended transaction type.
How to prevent CD chargebacks
- Process refunds only through the original transaction record, never as standalone manual entries.
- Restrict virtual terminal access and require a second review for manually keyed credits and reversals.
- Add automated reconciliation that flags any account with a debit and an expected credit of matching amount within a short window.
- Test refund and reversal paths in your payment integration after every gateway or processor change.
- Audit terminal function usage so a return rung as a sale is caught the same day, before the customer sees their statement.
Frequently asked questions
- What does Discover reason code CD actually mean?
- It means a credit or debit posted in the wrong direction: the customer was charged when they should have been refunded, or a refund was processed as a charge. It is a merchant processing error code, not a fraud claim.
- If I already fixed the posting error, will the CD chargeback still go through?
- Submit proof of the correcting credit with its date and amount in your dispute response. Discover will generally not take the funds twice, but you must document the correction; silence lets the chargeback stand alongside your refund and you lose the amount twice.
- How do I prove a disputed debit was a real sale and not a botched refund?
- Provide the order record, the customer's purchase confirmation, and an account transaction history showing no pending refund obligation. If there was never a return or credit due, demonstrating the debit's independent commercial basis usually resolves CD in your favor.
Related Discover codes