Discover · Processing Errors
Reason code LP: Late Presentation
The merchant submitted the transaction for settlement too long after the transaction date, outside the window Discover's rules allow. By the time the charge posted, the account may have been closed or the cardholder no longer expected it. The dispute is about timing of presentment, not the legitimacy of the underlying sale.
Issuer filing window
typically 120 days from the processing date
Merchant response window
typically 30 days to respond
Why LP chargebacks happen
- A settlement batch sat unsubmitted for weeks due to a terminal fault, integration outage, or operational oversight.
- Delayed-capture workflows, such as charging on shipment, stretched past the presentment window during a fulfillment backlog.
- Offline or store-and-forward transactions from an connectivity outage were recovered and submitted long after the fact.
- A disputed internal hold, compliance review, or reserve release delayed the capture of an already-authorized sale.
- Reprocessing of a failed batch was done manually weeks later without checking presentment limits.
How to fight a LP chargeback
- Verify the actual dates; if the transaction was presented within the allowed window, submit settlement records proving the timeline and the dispute fails on its facts.
- Show the account was in good standing and open when the transaction posted, since late presentation harm typically requires the account to have closed in the interim.
- Document any Discover-recognized exception that applies to your delayed submission, such as national holidays or system outages acknowledged by your acquirer.
- Provide the authorization record with its date to anchor when the transaction actually occurred.
- If presentment genuinely fell outside the window and the account closed, accept the loss and fix the settlement pipeline; representment cannot cure late timing.
How to prevent LP chargebacks
- Settle batches daily on an automated schedule and alert on any batch older than 48 hours.
- Monitor the gap between authorization and capture for delayed-capture orders and force capture before the window closes.
- Reconcile authorization counts against settlement counts daily so orphaned transactions surface immediately.
- Build presentment-age checks into any manual reprocessing tooling so stale items require explicit review.
- After outages, prioritize recovered offline transactions for immediate settlement rather than queuing them normally.
Frequently asked questions
- How long do I have to present a Discover transaction for settlement?
- Discover's operating regulations set specific presentment windows measured from the transaction date, and your acquirer agreement reflects them. As a working rule, settle within days, not weeks; merchants who batch daily essentially never see LP disputes.
- The sale was legitimate and the customer got the goods. Why am I losing money over timing?
- Presentment deadlines are a network compliance obligation independent of the sale's merits. Late posting harms cardholders who budget around statements or close accounts, so the rules put timing risk on the merchant. The remedy is operational: fix whatever let the batch go stale.
- Can I re-submit a transaction that was charged back for late presentation?
- Re-presenting the same stale item generally fails for the same reason. If the account remains open, talk to your acquirer about permissible paths, or arrange payment directly with the customer. Prevention is the only reliable answer to LP.
Related Discover codes