What Happens When a Buyer Disputes a Charge: A Step-by-Step Walkthrough

The subject line usually says something like "A charge was disputed" or "You have a new chargeback," and it lands in your inbox at the worst possible moment — right before you were about to check sales for the day. Your stomach drops. Did you do something wrong? Is your account about to get suspended? Here's the truth: a dispute is a normal, survivable part of running a payments business, and it follows a predictable script inside both Stripe and PayPal. Once you know the timeline — what triggers it, what you're asked to submit, and how long it takes to resolve — the panic evaporates and it becomes a checklist you knock out in twenty minutes. This walkthrough covers exactly what happens, in order, so the next time that email lands you already know what to click.

Step 1: The buyer contacts their bank, not you

A dispute almost never starts with a message to you. It starts when a customer looks at their card or bank statement, doesn't recognize a charge, feels the product didn't match expectations, or simply wants their money back faster than waiting on a reply — and calls their bank instead of you. The bank (or PayPal, acting in a similar role) opens a formal claim on the buyer's behalf and asks the payment processor to freeze that amount. This is why the first sign of trouble is often a notification, not a support ticket: by the time you hear about it, the money has typically already been pulled back out of your available balance.

It's worth sitting with that for a second, because it reframes the whole process. This isn't a negotiation between you and the customer anymore — it's a formal review between the processor and the card network, and you're submitting evidence into that review. That's exactly why a real storefront setup matters so much here: when a buyer purchases through a connected Stripe account or PayPal on store.fan, every transaction is timestamped and tied to a specific product, email, and delivery event, which becomes the raw material for your response.

Step 2: The notification and the reason code

Both Stripe and PayPal will notify you almost immediately — Stripe through the dashboard and email, PayPal through its Resolution Center — and both will attach a reason code explaining why the buyer disputed the charge. This code matters more than people realize, because it tells you exactly what kind of evidence will actually move the needle. "Product not received" needs delivery proof. "Unauthorized transaction" needs proof the purchase matches the account holder's activity. "Product not as described" needs your listing description and any support conversation. Read the reason code first, every time — submitting delivery logs against an unauthorized-transaction claim wastes your window and doesn't answer the actual question being asked.

Step 3: The evidence window — and why speed beats perfection

This is the part creators most often get wrong: treating the dispute like an open-ended inbox item instead of a countdown. Once a dispute opens, you're given a fixed window to respond — commonly somewhere in the range of 7 to 21 days depending on the card network and processor, though PayPal and Stripe each display the exact deadline directly in the case. Miss it, and the dispute is decided automatically against you, full stop, no appeal on the missed deadline itself. So the first move isn't crafting the perfect explanation — it's opening the case the moment you see it and confirming the actual due date.

Step 4: Building your evidence packet

Both platforms give you a structured form to fill out rather than a blank text box, which is a gift — it tells you exactly what they're looking for. Stripe's evidence form has fields for things like a receipt, delivery confirmation, and customer communication. PayPal's Resolution Center works similarly, walking you through uploading documentation tied to the specific claim type. The single strongest category of evidence for a digital-product business is delivery proof, because it's objective and timestamped rather than a matter of opinion.

1. 1Pull the order confirmation email showing exactly what was purchased and when.
2. 2Grab the delivery log or download timestamp — proof the buyer actually received or accessed the file, course, or booking link.
3. 3Screenshot your product page as it appeared at the time of purchase, especially price and description.
4. 4Attach any support messages or inbox replies, particularly if the buyer previously asked a question or acknowledged receipt.
5. 5Note the billing descriptor shown on statements — this heads off "I didn't recognize this charge" confusion before it starts.
6. 6Fill in every field the platform offers, even ones that feel repetitive — incomplete submissions are graded as weaker.

This is exactly where automatic delivery earns its keep. Because store.fan delivers a secure download link on-screen and by email the instant payment clears — and does the same for course access and meeting links — you already have a timestamped delivery record for every sale without building anything extra. That single log entry often does more to win a dispute than a paragraph of explanation ever could.

You're not trying to convince the buyer. You're trying to give a reviewer who's never heard of you a reason to trust the timestamp over the complaint.— A useful frame while writing your response

Step 5: Submission, review, and the waiting period

Once you submit, the evidence goes to the card network or bank for review — not back to Stripe or PayPal for a final call, since they're relaying the case rather than deciding it outright in most disputes. This review period can take anywhere from a few days to several weeks, and there's genuinely nothing to do during it except keep running your business. Checking the dashboard every hour won't speed up a bank's internal queue. What you can control is making sure the funds hold in your account are accounted for in your own math, since the disputed amount (plus a dispute fee charged by the processor regardless of outcome) is typically deducted from your balance the moment the case opens, not after it's decided.

That fee is worth sitting with for a second, because it's the real reason prevention beats fighting: even a dispute you win usually still costs you a flat fee, on top of the time spent building the evidence packet. This is part of why plans and payment setups matter beyond the headline platform fee — a clean checkout with clear branding, an accurate billing descriptor, and instant automatic delivery all reduce how often a buyer feels confused enough to dispute in the first place.

Step 6: The verdict — and what happens next either way

Eventually the case resolves one of two ways. If you win, the disputed funds are returned to your available balance, though the dispute fee itself is sometimes non-refundable depending on the processor's policy — check the specifics in your dashboard. If you lose, the charge stays reversed and you don't get a second appeal on that same case through the standard flow. Either outcome, the smart move is the same: log what the reason code was, note whether your delivery record was airtight, and use it to tighten your process. A pattern of disputes for the same reason — say, buyers not recognizing your statement descriptor — is a fixable process problem, not bad luck.

It's also worth remembering that disputes are a normal cost of doing real business, not a sign you shouldn't be selling. Every creator who accepts cards will see one eventually; the ones who handle it smoothly are the ones with clean records already sitting in a dashboard rather than scattered across screenshots and old emails. That's the whole case for running sales through one connected setup instead of ad hoc invoices — when you open your store.fan, every purchase, delivery, and customer message lives in one place, ready the moment a dispute notification lands. Want to see what that looks like day to day? Browse a live example store to see the storefront and delivery flow in action.

Preventing the next one

The cheapest dispute is the one that never opens. A surprising share of chargebacks trace back to buyers simply not recognizing a charge on their statement, which is solved by making sure your billing descriptor and business name are clearly configured with your processor. Beyond that, responsive support closes the loop before a buyer feels frustrated enough to call their bank — a quick reply through a built-in inbox often heads off a dispute a generic "contact us" page never would. And because instant, automatic delivery is your best evidence if a dispute does happen anyway, it's worth confirming your delivery emails are actually landing (check spam-safe sending) rather than assuming they are.

The bottom line

A dispute notification feels like an emergency the first time it lands, but it's really just a form to fill out on a deadline, using evidence you likely already have if you're running your sales through one clean system. Know the reason code, respond fast, lean on delivery timestamps, and treat the fee as a normal cost of doing business rather than a verdict on your store. Creators who let a single chargeback shake their confidence usually stop pricing boldly or stop selling altogether — don't be that story. For more playbooks like this one, the blog covers everything from checkout psychology to payout mechanics, and there's no better time than now to make sure your own setup is dispute-ready.