What Is an Evidence Due Date?

Evidence Due Date The deadline by which a merchant must submit evidence to challenge a payment dispute. This deadline is the single-point time limit that governs when a merchant's response package (invoices, tracking, communications, proof of delivery, refund records, etc.) must arrive with the acquirer, payment service provider (PSP), or card network to be considered during dispute resolution.

Merchants encounter Evidence Due Date routines most often with card-not-present chargebacks, payment disputes raised through gateways, and marketplace claim processes. The due date is not a suggestion: missing it usually means the issuer rules in favor of the cardholder and the merchant loses the funds (plus fees). Understanding what the date covers, who sets it, and how to meet it is central to chargeback management.

What The Deadline Typically Covers

The evidence due date applies to the merchant’s response package for a single dispute. That package commonly includes transaction receipts, shipping and tracking data, customer communications, proof of returns or refunds, and any device or system logs that support the merchant’s case. Submission channels include the merchant’s acquirer portal, PSP dispute interface, or directly through card-network tools when the acquirer pushes the request.

Why It Matters

Card networks and issuers use time-bound windows to keep the dispute life cycle predictable. A merchant who meets the evidence due date can often avoid a chargeback, recover funds through representment, and protect their merchant score with the acquirer. Missing the deadline usually ends the merchant’s ability to present facts during that stage, increasing the likelihood of a lost dispute and higher chargeback/processing costs.

How The Deadline Is Set And How It Varies

The Evidence Due Date is set by the card network’s rules and the acquirer’s operational process. Timelines vary by: the payment method (Visa, Mastercard, AMEX), the dispute reason code, and whether the dispute is managed by a PSP or a large acquirer. Common windows are 7–30 calendar days from when the acquirer notifies the merchant; some networks allow longer for specific merchant-initiated recovery steps.

Typical Evidence Types

• Transaction records: Signed receipts, invoice numbers, SKU details showing sale legitimacy and amount charged.
• Fulfillment proof: Carrier tracking numbers, delivery confirmation, signature images, timestamps from WMS/WMS reports.
• Customer communications: Emails, chat transcripts, refund confirmations, authorization forms.
• Technical logs: Authorization codes, IP address logs, device fingerprinting, 3-D Secure authentication results.
• Return and refund proof: Return tracking, restocking notifications, partial refund receipts.

Consequences Of Missing The Deadline

When a merchant does not submit evidence by the due date the issuer typically rules in the cardholder’s favor automatically. Financial consequences include the chargeback amount, retrieval and dispute fees, possible increased processing reserves, and elevated chargeback ratios that can trigger fines or termination by the acquirer. Re-presentment or arbitration options may still exist but are more onerous and expensive.

Practical Example

A merchant sells a $1200 electronics item. A buyer files a chargeback for 'unauthorized transaction.' The acquirer notifies the merchant and sets an evidence due date 10 days out. The merchant compiles the signed delivery receipt, carrier tracking showing delivery to the billing address, transaction authorization code, and a copy of the order confirmation email — and uploads them via the PSP dispute portal before the due date. The issuer evaluates the evidence and reverses the chargeback, returning funds to the merchant.

Tips To Meet Evidence Due Dates

• Automate collection: Integrate WMS, OMS, and PSP systems to tag and store order, shipping, and communication artifacts automatically.
• Centralize disputes: Use a single dispute management portal or connect your PSP to ensure a quick reaction when notifications arrive.
• Standardize packages: Keep a templated evidence package format with prioritized documents mapped to common reason codes.
• Assign ownership: Designate a dispute owner to monitor inboxes and acquirer portals daily so nothing slips past the due date.

In short, the Evidence Due Date is the merchant’s last operational window to present facts that can overturn a payment dispute. Treat it as an operational SLA: prepare evidence before disputes occur, automate capture, and respond within the network and acquirer timelines to protect revenue and merchant status.