When a customer files a chargeback or dispute through their bank, Stripe doesn’t wait for you to respond before pulling money out of your account. The funds are held—or outright reversed—immediately, and you’re racing a clock most operators don’t know exists.
If you run a subscription, sell a course, or process one-time payments for services, you need to understand how Stripe’s dispute process actually works. The timeline is tighter than you think, the evidence requirements are specific, and the outcome often depends on how fast you move in the first 48 hours.
What happens the moment a dispute arrives
Stripe receives the dispute notification from the card network—Visa, Mastercard, Amex—and immediately debits your Stripe balance. If your balance is zero or negative, Stripe pulls from your bank account on the next payout cycle.
You get an email and a dashboard notification. The dispute reason—fraudulent, unrecognized, product not received, product unacceptable, duplicate charge, or credit not processed—determines what evidence Stripe will ask for and how the card network will weigh your response.
The clock starts immediately. You have 7 days to submit evidence for most disputes. Some card networks give you up to 21 days, but Stripe’s default deadline is one week. Miss it, and you forfeit by default.
Even if you submit evidence on time, the card network takes 60 to 75 days to issue a final decision. Your funds stay held during that entire period. If you lose, Stripe charges you a dispute fee—currently $15 for most disputes in the U.S., higher in other regions or for certain card types.
What evidence actually matters
Stripe provides a dispute evidence form in the dashboard. It’s tempting to write a narrative explaining why the customer is wrong. That’s not what wins disputes.
Card networks want documentation that proves the customer received what they paid for and authorized the transaction. The strongest evidence:
- Delivery confirmation: Tracking numbers, delivery signatures, IP logs showing account access after purchase.
- Customer communication: Email threads, support tickets, or messages where the customer acknowledged receipt or asked for help using the product.
- Terms of service acceptance: Timestamped logs showing the customer agreed to your refund policy or terms at checkout.
- Usage logs: For digital products, show login timestamps, downloads, course progress, or API calls after the purchase date.
For “product not as described” disputes, comparison screenshots—what you advertised vs. what you delivered—help, but only if you can show the customer had access and didn’t contact you first.
For “fraudulent” disputes, evidence that the purchase matched the customer’s billing address, IP geolocation, or previous purchase history can swing the decision. But if the cardholder claims the card was stolen, you’ll lose unless you have very strong delivery proof tied to the cardholder’s verified identity.
When to fight and when to refund preemptively
Stripe’s dispute win rate across all merchants hovers around 20 to 30 percent. Some categories—digital goods, services, subscriptions—perform worse because card networks favor cardholders in ambiguous cases.
If the dispute reason is “fraudulent” and you have no delivery confirmation or communication from the customer, you’ll almost certainly lose. In that case, accepting the dispute and treating it as a fraud loss is often faster than spending time gathering evidence that won’t change the outcome.
If the dispute is “product not received” and you have tracking showing delivery to the cardholder’s address, fight it. If it’s “unrecognized” and you have emails from the customer using the product, fight it.
One non-obvious tactic: if you catch the dispute within 24 hours and the customer is reachable, offer a direct refund in exchange for them withdrawing the dispute with their bank. Stripe allows you to issue a refund even after a dispute is filed, and if the customer withdraws, you avoid the dispute fee. This only works if the customer responds quickly—and many won’t.
How to reduce disputes before they happen
Stripe’s Radar tool flags high-risk transactions, but it won’t catch disputes that stem from buyer’s remorse or confusion. The two most effective levers:
- Descriptor clarity: Make sure your Stripe statement descriptor matches your brand name exactly. “XYZ MEDIA LLC” doesn’t help if your customer knows you as “Daily Insights Newsletter.” Mismatched descriptors are the leading cause of “unrecognized” disputes.
- Proactive communication: Send a receipt email immediately after purchase with a clear description of what was bought, when it was delivered, and how to contact you. For subscriptions, send renewal reminders 3 to 7 days before each charge.
If you’re seeing repeat disputes from a specific product or customer segment, that’s a signal that your positioning, pricing, or onboarding needs work—not just your dispute-response process.
Disputes cost you time, money, and cash flow. Stripe doesn’t return the dispute fee even if you win. The best defense is documentation you gather at the point of sale, not evidence you scramble to assemble a week later.
Have a question about payment processors, dispute handling, or monetisation infrastructure? Reply to this email—we cover what solo operators actually run into, not just what the docs say.