Discover · Chargeback reason codes
Discover 4542 chargeback: Late Presentation explained
Checked
Discover reason code 4542, Late Presentation (older letter code LP), means the sale was submitted too long after the transaction: more than 10 calendar days, or 30 days for lodging, car rental and travel, according to Fiserv's guide. Answer with a receipt showing timely processing, an authorization within 10 days of the ship date for delayed delivery, or the cardholder's signed approval to post late.
- 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
- Proof of timely processing; authorization within 10 days of shipping
- Can it be prevented?
- Yes: capture promptly after shipping
- Who usually wins
- The merchant with proof of timely submission
What PlatformDTC does
PlatformDTC captures each card payment through the processor at checkout and charges subscription renewals when they are due. 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 transaction reached Discover after the allowed time.
Older Discover documentation pairs 4542 with the letter code LP.
Why customers file it
Delayed capture for pre-orders or backorders.
Evidence that wins
Respond to every Discover chargeback, even small ones, as Discover itself advises. Send:
- A receipt showing timely processing
- For delayed delivery: an authorization within 10 days of the ship date
- The cardholder's signed approval to post late
How to prevent it
- Capture within 10 days, or re-authorize at shipment
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
- How late is too late on Discover?
- Fiserv's guide says more than 10 calendar days after the transaction, or 30 days for travel merchants.
- Is 4542 defendable?
- Adyen marks it as not defendable through Adyen; Fiserv lists defences.
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.
- 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.
- 7010 — The cardholder denies an in-person purchase.