Marketplace Chargebacks: Platform Debits and Recovery

Marketplace chargebacks can debit a platform after the seller has already received its money. Stripe Connect distinguishes direct charges from two indirect models: destination charges and separate charges and transfers. For both indirect models, Stripe debits the platform for the disputed amount and fee, even when the connected account is designated as the business of record. Recovering those funds is a separate operation.

The discussion uses Stripe’s current documentation, checked October 10, 2026. It explains infrastructure behavior rather than promising dispute outcomes or interpreting a marketplace’s legal obligations. Our marketplace payouts guide covers the outgoing-money side.

Identify the charge before assigning the debit

Stripe’s charge model documentation defines three types. Direct charges are created on a connected account. Destination charges are created on the platform and immediately transfer funds to one connected account. Separate charges and transfers let the platform charge first and distribute money through separate transfers, potentially to several recipients.

For a direct charge, Stripe can bill the dispute fee to the platform or connected account depending on configuration. The amount’s debit location therefore does not answer every question about fees or responsibility. Stripe also describes platform responsibility for disputes and fraud with its legacy Express and Custom account types.

For indirect charges, the documentation is explicit: the platform balance is automatically debited for the disputed amount and fee. A settlement record showing that money reached the seller does not move that debit to the seller’s balance.

Business of record and balance liability differ

The on_behalf_of parameter can make the connected account the business of record. Stripe says it affects the settlement country, country-specific fee structure, statement descriptor and other payment details. It does not change which balance is debited for an indirect-charge dispute.

That separation matters when a team reads a seller agreement alongside the processor ledger. A contractual allocation of losses and the processor’s initial debit are different things. The platform needs a documented recovery process even if its commercial terms assign a loss to a seller.

Stripe’s marketplace refunds and disputes guide states that the platform is ultimately liable for chargebacks and related costs for destination charges and separate charges and transfers. This is Stripe’s description of those integration models, not a claim about every payment provider.

Recovery is not automatic reimbursement

Stripe describes reversing a transfer as a way to attempt recovery from the connected account. That does not establish that money will always be available or that every reversal should happen immediately.

The platform should associate each dispute with the original charge and its transfers, then track the dispute debit and each recovery attempt separately. For a multi-recipient payment, one charge can lead to several transfers. A single seller balance is not enough to reconstruct the full flow.

An illustrative separate-charge record might show a $100 customer payment, $70 transferred to a seller, $20 to another recipient and $10 retained by the platform, before processing fees. If $40 is later refunded, the platform’s refund does not automatically reverse either recipient’s transfer. The amounts to recover must be reconciled with the relevant transfers and the marketplace’s allocation rules. These numbers illustrate bookkeeping, not Stripe pricing.

Cross-border reversals need their own rule

Stripe warns that retransferring a previously reversed transfer can be restricted across borders. The platform could win a dispute yet be unable to repay the connected account using that route.

For disputed cross-border destination charges using on_behalf_of, its marketplace guide advises waiting to recover the disputed transfer until the dispute is lost. A policy that reverses every transfer as soon as a dispute arrives would miss that documented exception.

Regional availability also depends on the charge model. The charge documentation says destination charges and separate charges and transfers support cross-region flows only in certain regions, with additional conditions elsewhere. A configuration supported for one pair of accounts cannot be assumed to work worldwide.

Review the supported route before implementing a recovery policy. This guide does not provide a country list because the permitted combinations need to be checked against the current integration’s region and payout documentation.

Refunds have different controls

Refunds and disputes both remove funds, but they are distinct events. A refund is issued by the business; a dispute is raised through the cardholder or issuing bank. In Stripe’s indirect models, both affect the platform’s balance.

For destination charges, the connected account retains its funds by default when a refund is issued. The reverse_transfer refund parameter requests recovery of the transfer. For a partial refund, Stripe describes a proportional reversal. If that request attempts a reversal but the connected account lacks sufficient balance, the charge documentation says it returns an error rather than creating a pending refund.

For separate charges and transfers, refunding the charge does not change associated transfers. The platform must reconcile amounts owed back by reducing subsequent transfers or reversing transfers separately.

A platform’s application fee is another record. Payment refunds do not return it to the connected account by default. Setting refund_application_fee returns a proportional amount. Stripe’s example is a $100 payment with a $5 application fee: refunding $40 returns $2 of that fee when the parameter is used. Those amounts demonstrate proportion, not a published rate.

Keep the dispute decision separate from reconciliation

Stripe recommends listening for dispute-created events and managing cases through its Dashboard or Disputes API. The case has its own evidence deadline. The guide does not provide one universal number of days, so a workflow should use the actual deadline for the case instead of a hard-coded assumption.

At the accounting level, retain the original charge, recipient transfers, dispute amount, dispute fee, reversal attempts and final outcome. If a reversal is later repaid, record that transfer separately too. Otherwise, a dispute that was won can appear to have left a seller unpaid, or a refunded charge can appear to have recovered money it never recovered.

The processor’s live state should be reconciled with the platform’s record. Stripe says pending indirect-charge refunds are processed once sufficient platform funds become available, and that a new transfer after a successful dispute can fail when the platform has insufficient balance. Sending a request is therefore not proof that its monetary effect has completed.

These controls are practical inferences from the documented flows. They do not guarantee recovery, prevent every chargeback or replace the case-specific evidence requirements.