Discover · Chargeback reason codes
Discover 4550 chargeback: Credit/Debit Posted Incorrectly explained
Checked
Discover reason code 4550, Credit/Debit Posted Incorrectly (older letter code CD), means a refund was posted as a sale or the reverse. Fiserv's guide gives the issuer 120 days and says the chargeback can be for double the transaction amount. Answer with a record showing the transaction was posted correctly. Refunding through the original charge prevents it.
- Category
- Processing error
- Time limit for the bank to file
- 120 calendar days from the processing date for most Discover codes (Fiserv guide, 2016)
- Time limit to respond
- Your processor's deadline: Stripe says usually 7–21 days depending on the network; Adyen gives 25 days for Discover
- Typical evidence
- Record showing the transaction was posted correctly
- Can it be prevented?
- Yes: refund through the original charge
- Who usually wins
- The merchant when records show correct posting
What PlatformDTC does
PlatformDTC refunds by refunding the original charge through the processor, with one idempotency key per order so a refund cannot be sent twice. For a "refund not received" dispute, PlatformDTC reads the refund history from Stripe: if the money was already returned it sends each refund's amount, date and acquirer reference number (ARN) and asks the bank not to pay twice; if not, it quotes the store's published refund policy. With "Answer a chargeback automatically" switched on, it sends the response to the bank for you before the deadline.
What it means
A credit and a sale were confused when posting.
Older Discover documentation pairs 4550 with the letter code CD.
Why customers file it
Manual refunds keyed as sales.
Evidence that wins
Respond to every Discover chargeback, even small ones, as Discover itself advises. Send:
- A record showing the sale was posted correctly
How to prevent it
- Refund through the original charge rather than keying a new transaction
For developers
On Stripe the dispute object arrives with reason "general" and the card network's own code in payment_method_details.card.network_reason_code; listen for charge.dispute.created and read evidence_details.due_by for the deadline.
Discover does not publish its dispute rules publicly; the codes and names here are the ones Stripe reports, and the defences come from processor guides.
Frequently asked questions
- Why can a 4550 be for double?
- Fiserv's guide says it is valid for double the amount, because a credit posted as a sale both misses the refund and adds a charge.
- Which Stripe category is it?
- General.
Sources
- Dispute categories and network reason codes — Stripe
- Dispute Management Guide, Discover chapter (Rev 04/16) — First Data (Fiserv)
- Dispute reason codes: Discover — Adyen
Related
- 8002 — The cardholder says a refund they were owed was never processed.
- 4586 — The amount charged differs from the amount the cardholder agreed to.
- 4542 — The sale was submitted more than 10 days after the transaction (30 for travel).
- 4863 — The sale was not properly authorized, or was made on an expired card.
- 4753 — The charge was posted to an invalid card number.
- 4757 — Discover itself initiated the dispute for a breach of its operating rules.
- 4762 — A late dispute raised after the normal chargeback window, within 2 years of processing.
- 7030 — The cardholder says they did not make an online, phone or mail order purchase.