Discover · Chargeback reason codes
Discover 4753 chargeback: Invalid Cardholder Number explained
Checked
Discover reason code 4753, Invalid Cardholder Number (older letter code IN), means the charge was posted to a card number that is not valid. Fiserv's guide gives the issuer 120 days. Answer with a legible signed and swiped draft, or accept the chargeback and reprocess with the correct number. Having the customer enter the card and authorizing every 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
- Signed, swiped draft; or reprocess with the right number
- Can it be prevented?
- Yes: authorize every charge; never key numbers
- Who usually wins
- The merchant with a card read
What PlatformDTC does
Every PlatformDTC card payment is entered by the shopper in the processor's own card field and authorized before the order completes. PlatformDTC answers this kind of dispute with its standard evidence pack built from the order: customer name, email, IP address, billing and shipping address, items bought, carrier, tracking and ship date, the refund policy, and any refund already issued. With "Answer a chargeback automatically" switched on, it sends the response to the bank for you before the deadline.
What it means
The account number on the charge is invalid.
Older Discover documentation pairs 4753 with the letter code IN.
Why customers file it
Keying errors.
Evidence that wins
Respond to every Discover chargeback, even small ones, as Discover itself advises. Send:
- A legible signed and swiped draft
- Or accept and reprocess with the correct number
How to prevent it
- Avoid manual card entry
- Authorize every charge
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
- Can I reprocess?
- Fiserv's guide allows accepting the chargeback and reprocessing with the correct number.
- Why does Adyen show 4512?
- Adyen lists invalid card numbers under 4512.
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
- 4863 — The sale was not properly authorized, or was made on an expired card.
- 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.
- 7010 — The cardholder denies an in-person purchase.
- 4866 — A counterfeit chip card was used where the chip was not read.
- 4867 — A lost or stolen chip-and-PIN card was used where chip and PIN were not used.