How to Handle Disputes in Marketplaces: An Operator's Guide

Who this helps: you run a marketplace or membership platform and disputes keep landing on your account, or you sell through one and want to know what you can actually control.

Here is the rule that explains every marketplace dispute: the chargeback goes to whoever charged the customer's card, not to whoever made the sale. That business is called the merchant of record, and it is the one the bank comes after. On Amazon, that's Amazon. On your own platform, that's you.

Who actually eats a marketplace dispute?

Whoever is the merchant of record. That's the business name on the customer's card statement, and it's rarely the seller. When a customer disputes a charge, their bank pulls the money from that account, adds a fee, and counts it against that account's chargeback ratio. Everything else, including deadlines, fees, and appeals, follows from that one fact.

The map, platform by platform:

One clarification that trips people up: Shopify is not a marketplace. A Shopify store charges cards under your own name, so you're the merchant of record with all the risk and all the control.

What can sellers on Amazon or eBay actually do?

Sellers can respond well, and that is about it. How to handle disputes in marketplaces depends entirely on whose name charged the card, and on Amazon or eBay that name isn't yours. Because the marketplace owns the payment, sellers can't use most chargeback tooling. There's no descriptor to fix, because the statement says AMAZON. There are no alerts to buy, because the dispute goes to the platform, not to you. Your ratio isn't on the line, because you don't have one.

What's left is execution. Answer every dispute inside the window with proof of delivery and the customer conversation. Keep the records the platform's form asks for before it asks. And treat refund requests seriously, because a refund you refused often comes back as a dispute you fund anyway.

If that feels like managing a problem you can't prevent, you've understood it correctly. Prevention lives with whoever charges the card, which is why the rest of this guide is about the day that merchant is you.

What if you run the marketplace?

Then you're not reading about someone else's problem anymore. On Stripe Connect, the charge type decides who pays for a dispute, and most platforms are surprised by the answer:

• Standard accounts with direct charges: the seller's account is debited and the seller responds. The platform is mostly insulated.
• Express or Custom accounts, or destination charges: the dispute, the fee, and the ratio damage all land on the platform. The seller might not even know it happened.

And underneath every setup sits one line from Stripe's terms: the platform is always financially liable to Stripe for disputes as the backstop. If the seller's balance can't cover it, yours does.

Why do subscription marketplaces get hit hardest?

Because they inherit subscription risk times the number of sellers. Marketplace chargebacks concentrate wherever the rebills are. A membership platform or creator marketplace charges cards on a schedule, and every rebill is a charge the customer didn't just approve. Weeks later, a statement line reads PLATFORM* SELLERNAME, built from your platform's shortened descriptor plus the seller's suffix. The customer remembers neither half. That's a textbook unrecognized charge, and on Visa it arrives as reason code 10.4, the same code any subscription business fights, except you collect it for sellers you've never met.

The compounding part is the ratio. Card networks judge the merchant of record, so a platform's chargeback ratio is the sum of every seller's behavior. Ninety-five clean sellers and five careless ones share one number, and the five decide it. Cross Visa's threshold and the monitoring program letter is addressed to you, not to them.

So the operator's real job is visibility: disputes broken down per seller, per product, per billing cycle. You want to know which seller's trials convert into disputes, whose rebills go unrecognized, and which contract to end before one seller poisons the account every other seller depends on. Platforms usually discover this the day the ratio letter arrives. The good ones are watching it weekly.

How do operators keep the ratio down?

1. Fix the statement line. Set your Connect descriptor prefix, and make every seller's suffix recognizable. Run the combined line through our descriptor checker the way a confused customer would read it.
2. Watch disputes per seller, not in total. Your total ratio tells you that you have a problem. The per-seller breakdown tells you which contract to end.
3. Turn on chargeback alerts for the platform account. You're the merchant of record; alerts catch disputes across all sellers before they become chargebacks and refund the ones not worth fighting.
4. Check the ratio before it's checked for you. Our VAMP calculator shows where the platform account stands against Visa's threshold.

And if you're a seller planning your escape from marketplace fees to your own checkout: the day you switch, every rule in this guide flips. You gain the margin and the customer relationship, and you inherit the descriptor, the disputes, and the ratio. Set those up before the switch, not after.

FAQ

Facts checked against Stripe's Connect documentation and marketplace seller policies. Last reviewed August 27, 2026.