A chargeback against a marketplace payment is a small accounting crisis: the buyer's money is pulled back from a transaction that was already split, fee'd, and possibly paid out. Who eats the loss is decided either by your design, in advance — or by default, which means the platform eats everything. Having built the ledger and payout side of this in production, here is the design.
What actually happens when a split payment is disputed
The processor debits the disputed amount (plus a fee) from the platform's side immediately — card networks do not wait for your seller to respond. If the seller was already paid, the money is in three places at once: gone from your processor balance, sitting in a seller's bank account, and recorded in your ledger as settled. Everything that follows is unwinding that contradiction in a controlled way:
- The ledger reverses first. A dispute posts balancing entries — buyer-side reversal, seller-side receivable, fee expense — the moment it arrives. The books reflect the dispute before anyone decides anything; decisions then move money between accounts that already exist. This is the corrections-as-entries discipline doing its real job.
- Reserves make recovery real. A receivable against a seller with a zero balance and no future earnings is a write-off with paperwork. Reserves sized to your dispute window — held in the ledger, visible to sellers, tiered by risk — are the difference between a policy and a wish. The payouts guide covers where they sit in the flow.
- Liability follows fault, in writing. Seller misdescription or non-delivery: seller's loss, from reserve. Stolen-card fraud your screening should have caught: platform's loss. Ambiguous: split by policy. The worst version is the unwritten one, renegotiated per incident with your highest-GMV seller.
- Evidence is assembled at order time, not dispute time. Delivery confirmations, acceptance timestamps, message threads, terms versions — captured automatically per order into a dispute-ready bundle. Fourteen-day response windows are generous for a system and impossible for a scramble.
Prevention pays better than defense
- Clear descriptors and receipts — a recognizable charge prevents the "what is this?" dispute, the most common and least necessary kind.
- Friction proportional to risk at checkout; your fraud screening is defending sellers' money too, and they should know it.
- Refund-before-dispute paths: a buyer who can get a refund in-app rarely calls their bank. A refund costs the item; a dispute costs the item, the fee, and the ratio.
- Watch the ratio itself: platform-level dispute rates are a compliance metric with real consequences, which makes prevention an infrastructure concern, not a support metric.
The design work is once; the disputes are forever. I build this into marketplace engagements as ledger machinery, not policy documents. Existing platform with rising disputes? The independent review audits how losses actually flow today.
Frequently asked questions
Who pays for a chargeback on a marketplace: the platform or the seller?
Contractually, whoever your seller agreement says — which is why the agreement must say it before the first dispute, not after. Mechanically, the processor debits the platform side first, so without a reserve or recovery mechanism the platform fronts every loss and then tries to collect from sellers. The workable pattern: liability follows fault (seller misdelivery vs. platform fraud-screening failure), enforced through reserves rather than invoices sellers ignore.
How do reserves for marketplace sellers work?
A slice of seller earnings — rolling percentage, fixed days-held, or risk-tiered — stays in the ledger past payout eligibility, sized against your dispute window and that seller's history. New and high-risk sellers carry bigger reserves that relax with track record. The reserve is a ledger account like any other: visible to the seller, released on schedule, drawn against for finalized disputes.
Can a marketplace win chargeback disputes?
Yes, at meaningfully higher rates than most platforms achieve — because winning is an evidence-logistics problem. The platform holds delivery confirmation, messaging history, and terms acceptance; the seller holds fulfillment detail. Platforms that pre-assemble evidence per order (automatically, at order time, not scrambling at dispute time) and submit within the deadline win the winnable ones. Platforms that forward emails to sellers and hope, lose by default.
Written by Andrej Dragojevic, Stripe Certified Professional Billing Architect.