Chargeback vs Dispute: Who Decides, and When

The claim came in on a Tuesday afternoon and I answered it before dinner. Amazon closed the platform case in my favor. I moved the order to the "done" tab of my spreadsheet and stopped thinking about it.

Seven weeks later the same order came back as a chargeback.

Not an appeal. Not a reopened case. A separate proceeding, run by a bank I had never spoken to, with a response window measured in days, and no acknowledgment anywhere in the notice that Amazon had already looked at this exact order and sided with me.

The two clocks explain the seven weeks without any mystery in it. Amazon Pay's seller policy gives you five business days to answer an A-to-z claim ("You have 5 business days to respond to Amazon's notification, but best practice is to reply immediately" — A-to-z Guarantee Policy for Sellers, read 2026-08-18), so the platform side of an order can open, argue and close inside a single week. The card behind that same order stays available to the buyer for months: Stripe puts the ordinary filing window at 120 days from the payment, and the network rules stretch it further when the complaint is about delivery. Closing the platform case does not shorten either number by a day.

That gap is the whole point of this post. If you treat a chargeback like "the platform case, round two," you will miss the deadline, submit the wrong evidence, and in the worst version, refund the same buyer twice.

Different judge, not a different form

When you answer an A-to-z claim or an eBay Money Back Guarantee case, the marketplace is the referee. It wrote the rules, it holds the money, and it decides. You are arguing to the same company that runs the marketplace.

A chargeback is nothing like that. Visa describes a dispute as "the reversal of the value (or partial value) of a transaction by the card issuer to the acquirer, and usually, by the merchant bank to the merchant" (Dispute Resolutions, Visa, read 2026-08-17). Read that chain of parties again and notice who is missing. You are not in it. Neither, technically, is the marketplace — it sits in the acquirer's position, passing your evidence along.

Stripe, which processes disputes for a very large slice of card commerce, states the consequence plainly in its merchant documentation: Stripe "facilitates your case, but doesn't have influence over the outcome, which is at the sole discretion of the account owner's bank" (How disputes work, Stripe Docs, read 2026-08-17).

So the sequence of questions changes. In a platform case you ask "what does the policy say about item-not-received." In a chargeback you ask "what does an underwriter at a bank in another state, who has never seen my listing, need to see to reverse a decision they already made in their own customer's favor."

Visa sorts disputes into four categories — 10 (Fraud), 11 (Authorization), 12 (Processing Errors), and 13 (Consumer Disputes) — and the specific condition inside those categories decides what evidence is even admissible. The authoritative text is the Visa Core Rules and Visa Product and Service Rules, 18 April 2026 edition, with a shorter merchant-facing summary in Visa's Dispute Management Guidelines for Visa Merchants, June 2024. Mastercard's equivalent is its Chargeback Guide, Merchant Edition.

I am not printing an edition date for that one. Mastercard's document host turned away every request I made for the file, on 2026-08-17 and again on 2026-08-18, so I have never had its cover in front of me. If the guide does not download for you either, it is reachable through the rules section of Mastercard's business site.

Both rulebooks are free and both are enormous, and between them they are the actual law of this fight. Bookmark them and write the edition date into the filename, because these documents are reissued roughly twice a year and the previous edition is not what your case is judged under.

I am deliberately not printing a list of reason code numbers here. The codes that reach a marketplace seller are a small subset, they differ by network, and quoting a stale one is worse than quoting none. The code will be in the notice you receive. Look it up in the guide above for that specific code and only then decide what to send.

Different clock, and it is not the one you're used to

Here is the part that catches people who are good at platform cases.

The 120 / 7–21 / 60–75 day figures come from Stripe's dispute lifecycle documentation (read 2026-08-17). The eBay figure is eBay's own: sellers must respond "within 5 calendar days," or "the payment institution is likely to find in your buyer's favor" (Handling payment disputes, eBay, read 2026-08-17). The Amazon figure was the weak one here until 2026-08-20, when it stopped being second-hand. It is stated by Amazon itself, on the public Seller Forums, in the Account Health Dashboard walkthrough posted under the community manager account Quincy_Amazon: "You must respond to any chargeback claim within seven calendar days of the email date." (Account Health Dashboard intro series (1 of 3): Customer Service Performance, read 2026-08-20.) The same post assigns responsibility: you carry chargebacks filed for service reasons such as non-receipt, and Amazon carries payment-fraud ones such as a stolen card. The Seller Central help page titled "Chargeback claims" is the canonical version and still sits behind the seller login, so what happens to your funds if you miss the seven days is not something this page can quote — check that in your own account.

The delivery-date variant on the buyer's window is not folklore; it is in the rulebook. A dispute under condition 13.1 must be processed no later than 120 calendar days from the transaction processing date, or 120 calendar days from the last date the cardholder expected to receive the merchandise (Visa Core Rules, 18 April 2026 edition, section 11.10.2.4, Table 11-92). For a slow-shipping order, those two dates are nowhere near each other.

Two asymmetries matter more than the exact numbers.

First, the buyer's window is enormous and yours is tiny. Four months to file, one week to answer. An order you shipped in April can surface in August, by which time your carrier tracking detail may have already rolled off the carrier's website.

Second, your real deadline is earlier than the network's. The network gives the acquirer a window to present your rebuttal; your marketplace or processor has to compile and file inside that window, so their internal cutoff comes first. Nobody extends it. If the notice says seven days, seven days is the number, not the 30 or 45 days you may have read about in a network rulebook.

When both land on the same order

Buyers do try both. The platforms have written rules for this, and they are worth memorising because they determine what you should do in the first hour.

eBay closes the platform case. "Buyers can't use more than one resolution method to get a refund. If a buyer opens a dispute, any open order cancellations, reports that an item hasn't arrived, return requests, or eBay Money Back Guarantee cases for the same transaction are immediately closed" (Handling payment disputes, eBay, read 2026-08-17). Any work you had in progress in the MBG case evaporates. Re-upload the evidence into the payment dispute; do not assume it carried over.

Amazon denies the claim and takes over the card fight. Amazon Pay's A-to-z Guarantee Policy for Sellers (read 2026-08-17) states that Amazon "denies an A-to-z claim under review when we receive a chargeback from the credit card issuing bank," and that where the claim had already been granted, "Amazon will represent the chargeback to the issuing bank." That page governs Amazon Pay rather than the marketplace, and the marketplace's own A-to-z page is login-gated — but the design logic is the same one you'll see on Seller Central: one order, one proceeding, and the card network's proceeding wins.

The practical rule I now follow: when a chargeback notice arrives, I stop working the platform case entirely and rebuild the evidence packet for the card. Different audience, different packet — and what belongs in the card packet, in what order, and at what file size is its own piece of work.

The way I lost money twice

This is the mistake I would most like back.

An order went sideways, the buyer was unpleasant about it, and I decided the fastest way out was to refund from the seller dashboard and be done. What I did not know was that a dispute had already been filed on the card. The refund went out of my balance. The chargeback then also came out of my balance. One order, two payments, no item.

Stripe spells out the guardrail that exists on its own platform — "you can't issue a refund outside the dispute process while the dispute is open" — but marketplace dashboards do not always stop you the same way, and the timing gap between the buyer contacting their bank and you receiving notice is where the hole lives.

There's a nastier variant. Stripe's documentation notes that a buyer can dispute the full amount of a charge you already partially refunded. Your $22 goodwill credit does not shrink the disputed amount; it just becomes $22 you will never see again.

What I do now, every time, before any voluntary refund on a problem order: check the payment status in the marketplace's payments or disputes view first, and if anything says a dispute is open or pending, I do not touch the refund button. I answer the dispute instead. If I genuinely want the buyer to have their money, I accept the dispute, which costs me the order but not twice the order.

It helps to know what the ledger looks like when this does go wrong, because the debits never arrive as one line. Stripe sets out the order of operations: the card network debits Stripe for the disputed payment and its fees, and Stripe "in turn debits your Stripe balance for the disputed amount plus a dispute fee." The fee is a separate charge from the amount, and Stripe states that for businesses outside Mexico the fee for receiving a dispute is non-refundable — win the case and you get the disputed amount and the countered fee back, never that one. A refund you issued yourself is a third debit against the same order, and nothing in the sequence nets it out.

What each one does to your numbers

Losing the money is the visible cost. The metric is the one that compounds.

Amazon counts chargebacks in Order Defect Rate. Amazon's published definition is "the percentage of orders that have received negative feedback, an A-to-z Guarantee claim, or a service credit card chargeback," measured against a target of under 1% (Your merchant performance, Amazon Pay, read 2026-08-17). The same page adds a detail that quietly helps you: "An order can only be 'defective' once." A claim and a chargeback on the same order is one defect, not two. It also warns that defects are "reported several weeks after orders are placed," and that waiting 90 days "gives the most accurate view" — put plainly, the ODR on your screen today does not yet contain the chargebacks already in flight.

On eBay, the money mechanic is a dispute fee charged when you're found responsible for the disputed amount, and eBay's policy states it "will waive the dispute fee if the dispute is eligible for payment dispute seller protections," with no more than one dispute fee per order (Payment dispute seller protections, eBay, read 2026-08-17). eBay's protection rules also carry a hard evidence threshold worth writing on the wall: for orders totalling $750 or more, protection requires proof that signature confirmation was purchased. Note that eBay's protection page does not spell out how a protected dispute lands on your seller performance; check Seller Standards for that rather than assuming.

The fee is published rather than estimated. eBay's fee page states that "when you list an item on ebay.com, the Dispute fee is $20.00 (before sales taxes)" and that "if you accept the payment dispute and issue a refund, eBay will waive the Dispute fee" (Selling fees, read 2026-08-18). Fighting a $30 order and losing costs the item plus $20; conceding the same order costs the item and nothing else, so the arithmetic turns over at a lower price than most sellers assume. eBay also says the amount "will generally be deducted from the total of your Available, Processing, and On hold funds" — the debit can land against money you had already counted as a payout.

The quiet week is when this gets done

Pull one shipped order from four months ago — the far end of the buyer's filing window — and see how much of its tracking detail the carrier will still show you. If the delivery scan and address are already gone, that is your evidence-retention problem and not a hypothetical one. Save the record at the time you ship, not at the time you're accused, and be fussy about which record: what an issuer will accept as proof of delivery is narrower than what a marketplace accepts.

Find the dispute or chargeback notification setting in each marketplace you sell on and make sure it goes to an address you read daily. A seven-day window that starts on an email you open on day six is a two-day window. When the notice does arrive, the chargeback response deadline calculator turns the window into a date you can put in a calendar.

Download the current Visa Core Rules and Mastercard Chargeback Guide PDFs today and put the edition date in the filename. When a notice arrives with a reason code, you'll search your own copy instead of a blog's summary of a two-year-old edition.

---

Policy and rules as of 2026-08-17, every citation re-opened on 2026-08-18; the Amazon chargeback deadline re-sourced 2026-08-20. Verify at: Visa Core Rules and Visa Product and Service Rules (18 April 2026 edition); Mastercard Chargeback Guide, Merchant Edition (edition date not verified — see above); eBay "Handling payment disputes," "Payment dispute seller protections" and "Selling fees"; Stripe's "How disputes work"; Amazon Pay "A-to-z Guarantee Policy for Sellers" and "Your merchant performance"; Amazon Seller Central "Chargeback claims" (login required) and, for the seven-day figure quoted above, the public Seller Forums post "Account Health Dashboard intro series (1 of 3): Customer Service Performance" by Quincy_Amazon. Card network reason codes and evidence requirements are on a 180-day recheck here; the network rulebooks are reissued roughly twice a year, so confirm you are reading the current edition before you rely on any figure above.

I'm a seller, not a lawyer and not a chargeback-recovery firm. Nothing here predicts how any individual bank will decide your case.