Discover Reason Code CD: Credit/Debit Posted Incorrectly

What Discover reason code CD means

CD covers transactions that posted in the wrong direction. The typical case: you meant to refund a customer, but the refund went through as a sale, so the cardholder was charged a second time instead of credited. Less often, a sale posts as a credit, or a correction posts twice.

From the cardholder’s side the statement looks plainly wrong, which is why CD is filed as a cardholder dispute rather than a processing-error code.

Common causes

• A refund keyed as a “sale” in a virtual terminal or POS
• A void and a refund both processed for the same order
• A correction transaction entered with the wrong transaction type
• Errors during a processor or gateway migration, when refunds are re-entered by hand

Evidence for a CD dispute

1. Processing records: the transaction log or batch report showing the transaction type (sale or credit), amount and date for each entry.
2. The offsetting correction: if you already fixed the error, the credit transaction with its date and reference number (an acquirer reference number if your processor provides one).
3. The underlying order: the original sale and the intended refund, so the issuer can see the full sequence.
4. A short reconciliation: one line per transaction showing the net effect on the cardholder is correct.

How to prevent CD chargebacks

• Process refunds from the original transaction in your gateway or platform, not as new keyed entries.
• Restrict manual virtual-terminal access and require a second check on large refunds.
• Reconcile refund batches daily so a misposted refund is caught before the cardholder sees it.
• During processor migrations, freeze manual refunds or audit them closely.

Should you fight or accept?

Accept in most cases. CD disputes usually mean a real processing mistake, and the cardholder is owed the money. Don’t also issue a separate refund after accepting, or you’ll pay twice. See chargeback after a refund.

Fight only when your records show the transaction posted correctly, or you had already issued an offsetting credit before the dispute. In that case the processing log and refund reference are usually all you need.