What Discover Reason Code CD Means
Discover reason code CD — Credit/Debit Posted Incorrectly is a processing error dispute that occurs when a transaction was processed with the wrong polarity — a credit (refund) was posted as a debit (charge), or a debit was posted as a credit, affecting the cardholder's account balance in the wrong direction.
CD disputes are almost always genuine processing errors, not fraud. The most common scenario: a merchant processes a refund but it posts to the cardholder's account as an additional charge. A less common but equally disruptive scenario: a charge is processed as a credit, causing a pricing error that may not be caught until reconciliation. Either way, CD disputes warrant immediate internal investigation.
CD disputes are among the most clear-cut processing error chargebacks. If a refund was processed as a charge, the cardholder is correct and has been double-harmed — once by the original charge and once by the reversed refund posting incorrectly. Fix the underlying posting error, issue the correct refund, and accept the chargeback.
Cross-Network Equivalent Codes
| Network | Code | Title | Notes |
|---|---|---|---|
| Discover | CD | Credit/Debit Posted Incorrectly | This page |
| Visa | 12.7 | Invalid Data | Covers transaction type errors including credit/debit posting issues |
| Mastercard | 4834 | Point of Interaction Error | Mastercard's general processing error code |
| Amex | P08 | Duplicate Charge | Closest Amex equivalent for posting-type errors |
Common Trigger Scenarios
- Refund processed as a charge — The most common CD scenario: a merchant initiates a refund, but a system error causes it to post as an additional charge on the cardholder's account. The cardholder sees a second debit instead of a credit.
- Incorrect transaction type code — The payment gateway or POS submits the wrong transaction type indicator — a debit code for a credit transaction or vice versa — causing the processor to post it incorrectly.
- Batch file formatting error — A batch settlement file contains a formatting error that flips the transaction type for one or more records, causing credits to post as debits in bulk.
- Manual adjustment error — A staff member manually processes a transaction type correction but selects the wrong direction, doubling the incorrect posting rather than fixing it.
- Integration bug after system update — A payment gateway or POS software update introduces a bug that reverses transaction type handling, causing a series of CD errors before the issue is detected.
Key Deadlines & Timeframes
| Milestone | Timeframe | Notes |
|---|---|---|
| Cardholder Filing Window | 120 days | From the transaction date |
| Merchant Response Window | 30 days | From dispute notification; confirm with your processor for internal deadlines |
| Pre-Arbitration | 30 days | If Discover rejects representment, 30 days to escalate |
Evidence You Will Need
- Internal transaction record showing correct type — If the transaction was processed correctly on your end — as a credit — but posted incorrectly due to a processor or network error, provide your internal record showing the correct transaction type was submitted
- Processor confirmation of credit submission — Documentation from your payment processor confirming a credit transaction was submitted, demonstrating the error occurred downstream of your system
- Transaction type code from authorization record — The authorization record showing the correct transaction type code was used, establishing that any posting error was not on the merchant side
- Reconciliation records — Your settlement reconciliation showing the transaction was processed as a credit, with the correct net impact on your merchant account
Access the Processing Errors Guide
Our processing errors guide covers CD audit procedures, how to document transaction type submissions, and how to work with your processor to identify and fix posting errors.
Access the Processing Errors Guide →How Merchants Lose This Dispute
- Contesting a genuine posting error — If your system processed a charge when a refund was intended, there is no valid representment. Accept the chargeback, issue the correct credit, and fix the underlying error.
- No transaction type monitoring — Without monitoring to catch credit/debit reversals, CD errors can persist for multiple billing cycles, creating multiple chargebacks and a significant dispute ratio impact.
- Delayed investigation — CD disputes that are not investigated promptly may result in additional incorrect charges to the same cardholder if the underlying system error is not identified and fixed.
Response Framework Overview
- Audit the transaction type immediately. Pull the transaction record and confirm whether it was submitted as a credit or debit. Identify where the incorrect posting occurred.
- Correct the underlying error. If a refund posted as a charge, process the correct credit immediately. Do not wait for the chargeback dispute process to complete.
- Accept or contest based on findings. If the posting error was on your side, accept the chargeback. If your records show a correct credit was submitted and the error is downstream, present your transaction records and processor documentation.
- Report the error to your processor. Notify your payment processor of the posting error so they can investigate and prevent recurrence, especially if the error may affect other transactions.
Prevention Tips
- Reconcile daily and flag transaction type mismatches — Daily reconciliation that checks for credits posting as debits — or vice versa — catches CD errors before they appear on cardholder statements and escalate to chargebacks.
- Test refund processing thoroughly after system updates — After any POS, gateway, or software update, test the refund flow explicitly. Transaction type handling is a common regression failure in payment system updates.
- Monitor refund confirmation emails — Send cardholders a refund confirmation email immediately when a credit is processed. Cardholders who receive a confirmation but see a charge instead will contact you directly rather than filing a chargeback.
- Implement transaction type alerts — Configure your payment system to alert staff when a credit transaction is processed, providing an additional checkpoint to catch incorrect transaction types before settlement.
Frequently Asked Questions
What is Discover reason code CD?
Discover CD (Credit/Debit Posted Incorrectly) is filed when a transaction was posted to the cardholder's account as the wrong transaction type — most commonly when a refund (credit) is erroneously posted as a charge (debit).
Should I contest a Discover CD chargeback?
Almost never. CD disputes typically involve a genuine posting error where the cardholder was harmed. Audit the transaction, correct the underlying error, and accept the chargeback. Contesting a legitimate CD dispute wastes resources and increases your dispute ratio.
What causes credit/debit posting errors?
Common causes include POS system errors during refund processing, incorrect transaction type codes submitted to the processor, batch file formatting errors, and payment gateway misconfigurations that reverse the transaction direction.
How long does a cardholder have to file a Discover CD chargeback?
120 days from the transaction date. The merchant response window is 30 days from dispute notification.