The two charges were actually two separate orders. How do I prove that to Discover?

Submit distinct documentation for each: separate order numbers, itemized invoices, timestamps, and fulfillment records. Anything unique per transaction helps, such as different items, quantities, session IPs, or delivery scans. Identical paperwork for both charges will read as one order billed twice.

Should I refund a duplicate charge or let the chargeback resolve it?

Refund it the moment you find it. A proactive credit usually heads off the dispute entirely, avoids the chargeback fee, and keeps the case out of your Discover dispute ratio. If the chargeback arrives anyway, respond with proof of the refund and its date.

Can a declined-then-retried payment cause a DP chargeback?

Yes. If the first attempt actually authorized despite appearing to fail, the retry creates a genuine duplicate. Idempotency keys and checking authorization status before retrying are the fixes; without them, flaky network conditions convert directly into DP disputes.

Discover · Processing Errors

Reason code DP: Duplicate Processing

The same transaction hit the cardholder's account more than once. Two or more charges share the same card, merchant, amount, and roughly the same date, and the cardholder only authorized one of them. Discover claws back the duplicate while the original charge stands.

Issuer filing window

typically 120 days from the processing date

Merchant response window

typically 30 days to respond

Why DP chargebacks happen

A timeout or gateway error caused your system or the customer to retry a payment that had actually succeeded.
A batch was submitted twice after a settlement failure was retried without deduplication.
The same order was keyed manually after an online attempt appeared to fail.
Two MIDs or two gateways both captured the same order during a routing failover.
The customer double-clicked the pay button and the checkout lacked idempotency protection.

How to fight a DP chargeback

If two charges genuinely posted for one order, refund the duplicate immediately and answer the dispute with proof of that credit.
If the charges are for two distinct purchases, submit separate invoices, order numbers, and delivery records for each transaction.
Show differing order contents, timestamps, ship-to details, or session data that establish two independent authorizations.
Provide your settlement records demonstrating only one capture was submitted if the duplication happened on the issuer side.
Never fight a true duplicate; a representment on an obvious double charge wastes the fee and damages your standing with Discover's dispute analysts.

How to prevent DP chargebacks

Implement idempotency keys on every payment request so retries cannot create a second capture.
Disable or debounce the pay button after first click and show a clear processing state.
Deduplicate batch submissions and alert on any settlement file transmitted more than once.
During gateway failover, reconcile captures across both endpoints before settling.
Run a daily duplicate scan for same-card same-amount charges within 24 hours and refund proactively before the customer notices.

Frequently asked questions

The two charges were actually two separate orders. How do I prove that to Discover?: Submit distinct documentation for each: separate order numbers, itemized invoices, timestamps, and fulfillment records. Anything unique per transaction helps, such as different items, quantities, session IPs, or delivery scans. Identical paperwork for both charges will read as one order billed twice.
Should I refund a duplicate charge or let the chargeback resolve it?: Refund it the moment you find it. A proactive credit usually heads off the dispute entirely, avoids the chargeback fee, and keeps the case out of your Discover dispute ratio. If the chargeback arrives anyway, respond with proof of the refund and its date.
Can a declined-then-retried payment cause a DP chargeback?: Yes. If the first attempt actually authorized despite appearing to fail, the retry creates a genuine duplicate. Idempotency keys and checking authorization status before retrying are the fixes; without them, flaky network conditions convert directly into DP disputes.

Related Discover codes