A cardholder disputes a charge. Your team pulls the order record, finds the tracking number, and uploads it to the dispute portal. You've submitted evidence, but you've already lost.
Here's what happened: the package was still in transit when you clicked submit. The tracking ID proved the item left your facility, not that it arrived. The issuer ruled for the cardholder. You lost revenue you shouldn't have.
This isn't speculation. Analysis of one million "product not received" disputes on Stripe over 16 weeks revealed that disputes with evidence submitted after delivery was confirmed had a 27 percentage point higher win rate than disputes with no delivery confirmation. Evidence submitted while the package was still in transit? Only a two percentage point lift.
The failure wasn't the evidence itself. It was when you submitted it.
Why Timing Matters
Businesses routinely submit dispute evidence as soon as they receive the dispute notification. The workflow is reactive: dispute arrives, team pulls order data, team uploads whatever's available, team moves to the next ticket.
For physical goods, that usually means a tracking number. For digital goods, it might mean provisioning logs showing the customer had access to a service.
The problem: access doesn't prove consumption. A tracking number showing "in transit" doesn't prove delivery. Issuers can only rule on what they can verify at the time of review.
Timeline of a Failed Response
Day 1: Cardholder files dispute claiming product not received. Package is still in transit.
Day 2: Dispute notification reaches merchant operations team.
Day 3: Team member pulls order record, finds tracking number, uploads to dispute portal. Tracking status: "Out for delivery."
Day 7: Package delivered. Carrier updates tracking system with delivery confirmation, GPS coordinates, recipient signature.
Day 15: Issuer reviews dispute evidence. Evidence shows only that package left merchant facility. No delivery confirmation on record at time of review.
Day 20: Issuer rules for cardholder. Merchant loses dispute and revenue.
The evidence existed. It was submitted seven days too early.
Which Controls Failed
Workflow timing: Most dispute response processes trigger immediately upon notification. There's no hold mechanism to wait for delivery confirmation before submission.
System integration: Shipping data and dispute management systems operate independently. Matching a dispute to delivery status requires manual lookup across platforms.
Evidence verification: Teams submit what's available, not what's verifiable. A tracking number feels like proof, but its value depends entirely on the status it shows when the issuer reviews it.
Digital goods documentation: For digital products, teams submit service provisioning logs proving the customer could access the product. The analysis showed disputes with digital activity and usage logs, JSON telemetry showing a user streamed, downloaded, or accessed the specific product they purchased, had a 10 percentage point higher win rate than disputes without them. Provisioning proves availability. Consumption logs prove use.
What the Standard Requires
The Fair Credit Billing Act gives you 20 or more days to respond to most disputes. That window isn't just a deadline; it's operational space.
You're not required to respond immediately. You're required to respond with evidence the issuer can verify.
For physical goods, verification means delivery confirmation. The analysis found that businesses submitting delivery confirmation, a GPS map, and a signature had a 44 percentage point higher win rate than disputes without them. Each layer adds verifiable proof: confirmation shows arrival, GPS shows location, signature shows receipt.
For digital goods, verification means consumption. Service documentation showing provisioning had an eight percentage point higher win rate than disputes without it. Digital activity logs had a 10 percentage point lift. The difference: one proves access was granted, the other proves the product was used.
For refunds, verification means network visibility. Disputes that included evidence of a full refund issued through Stripe had a 63 percentage point higher win rate than disputes without it. Refunds issued as store credit? Only a six percentage point lift. Issuers can verify a refund processed through the card network. They can't verify store credit.
Lessons and Action Items
Stop submitting evidence the day you receive the dispute. If your dispute window allows 20 days and the package is still in transit, wait. Set a calendar reminder for three days before the deadline. Check delivery status then. If the carrier has confirmed delivery, submit. If not, include documentation showing the order is still within the delivery timeframe the customer agreed to at checkout.
Integrate your shipping and dispute systems. Manual lookups don't scale. Your dispute workflow should pull delivery status automatically. If you can't build that integration, use a payment processor that does it for you. Stripe's Smart Disputes pulls fulfillment history from more than 12 shipping providers, including delivery status, timestamps, and GPS coordinates.
For digital goods, log consumption, not just access. Your analytics platform already tracks user activity. Configure your dispute response workflow to pull telemetry showing the customer streamed, downloaded, or accessed the specific product they purchased. JSON logs from common analytics platforms work. Provisioning records alone don't.
Process refunds through your payment processor. If a customer requests a refund, issue it through the same system that processed the payment. The issuer can verify it on the network. Store credit, manual bank transfers, and check refunds can't be verified the same way.
Audit your current dispute evidence packets. Pull your last 50 "product not received" dispute responses. How many included delivery confirmation? How many were submitted before delivery? How many digital goods disputes included consumption logs versus provisioning records? The gap between what you're submitting and what wins disputes is your revenue leak.
The dispute itself isn't the failure point. It's the seven-day gap between when you submitted evidence and when the carrier confirmed delivery. Close that gap, and you'll recover revenue you're losing today.
