Marketplace refunds and chargebacks: the platform pays first, so decide how you claw it back

For marketplace refunds and chargebacks on Stripe Connect, destination charges and separate charges and transfers both debit the money from your platform's balance first, not the seller's. You get it back only if you reverse the transfer, and when you do that depends on whether you accept or fight the dispute. This is the runbook, as the docs read on October 28, 2026.

It covers marketplaces that charge the buyer on the platform account (Stripe calls these indirect charges), plus the extra steps if you build on Sharetribe. As of October 2026, Upfynd lists 152 marketplace and on-demand products and 124 payments and banking tools; in our view most of what follows applies whichever one you pick, because the money flow is set by the charge type, not the storefront.

Marketplace refunds and chargebacks land on your platform balance first

Stripe's marketplace refunds and disputes guide states that for indirect charges, Stripe always debits refunds, disputed amounts and the associated fees from your platform balance. It adds that in most cases you can recover the money from the connected account by reversing the transfer. In our reading, the key word is "can": the docs describe reversal as a step your platform takes, not something Stripe does for you.

The same guide says your platform is ultimately liable for chargebacks and related costs for both destination charges and separate charges and transfers. When the platform is the merchant of record, Visa and Mastercard monitor your dispute rate, and exceeding their thresholds could put you into monitoring programs that might impose fines.

Stripe's integration recommendations give the reason: Stripe applies a refund or dispute to the account where the original charge was made. On a platform charge, that account is yours, and the page warns that your platform can't easily recover those funds from connected accounts.

Direct charges, where the charge is created on the seller's own account, work the other way. The same page says direct-charge refunds reduce the connected account's balance, and it recommends assigning negative-balance responsibility to Stripe. This post does not cover direct charges.

Sharetribe says the same about its own marketplaces. Its payout troubleshooting article says the platform account is responsible for all disputed payments, plus a chargeback fee that varies by country, though the platform can debit the connected account if the dispute looks genuinely fraudulent.

Which charge type you use decides how a refund reaches the seller

The refund mechanics differ by charge type, and in our view it is a choice teams make once, early, without thinking about refunds. Here is how Stripe's docs describe each, as read on October 28, 2026.

Sources: destination charges, separate charges and transfers, and the refunds and disputes guide above.

How to refund a Stripe Connect destination charge, step by step

Stripe's destination charge page and the marketplace guide describe the same sequence. If you have already read how to reconcile Stripe payouts against bank deposits, this is the refund side of that matching.

1. Issue the refund from your platform, through the Dashboard or the Refunds API. Regardless of the charge type, Stripe says refunds come from your platform's balance.
2. Decide whether the seller bears it. By default the destination account retains the funds, leaving your platform to cover the negative balance. To pull the funds back, set reverse_transfer to true on the refund.
3. For a partial refund, pass an amount. If the refund covers the whole charge, the entire transfer is reversed; otherwise Stripe reverses a proportional amount.
4. Decide what happens to your commission. Refunds don't return the application fee by default. Setting refund_application_fee to true returns it in proportion; Stripe's example is a $100 payment with a $5 fee, where a $40 refund returns $2. For a destination charge you must also reverse the transfer if you refund the fee.
5. Check the platform balance. If it is too low when you refund, Stripe sets the refund to pending and processes it once funds arrive.

With separate charges and transfers, step 2 changes. Refunding the charge has no effect on the transfers, so it is your platform's job to reduce later transfers or reverse the transfer. Stripe's separate charges page adds a limit: a reversal is only possible if the connected account's available balance is greater than the reversal amount, or has connected reserves enabled.

One refund cost does not come back. Stripe says the original processing fee isn't returned on a refund, and Sharetribe says the same. In our view, budget for it as a cost of every refund you grant.

Marketplace chargebacks: time the reversal to the dispute outcome

Chargebacks add a deadline and a waiting period. Stripe's guide tells you to set up a webhook for dispute-created events, then reverse the transfer through the Dashboard or with a transfer reversal. In our view the timing rule is the easiest part to get wrong:

• Accept the dispute: reverse the transfer immediately.
• Challenge the dispute: wait for the outcome. If you win, don't reverse. If you lose, reverse.
• Reverse and then win: Stripe warns that sending the funds back to the seller can have unexpected results, including a failed transfer if your platform balance is too low and cross-border transfer restrictions.

In our view the waiting is long. Stripe's how disputes work page says cardholders can typically open a dispute within 120 days of payment, and that when someone pays for a future event or appointment, the window starts on the event date instead. After a chargeback you usually have 7 to 21 days to respond, depending on the card network, and if you submit evidence, the issuer's decision usually takes 60 to 75 days. The full lifecycle can take two to three months.

In our view, that timeline is the real hazard for a marketplace. A seller can be paid out, spend the money and still be the right party to repay it three months later. The routine in the next section is built around that gap.

The fees are separate from the principal. Stripe charges a flat dispute fee, adds a countered fee if you contest, and returns the countered fee if you win; unless your contract says otherwise, it never returns the received fee. If you run a marketplace in a category with many disputes, Chargeblast and Riskified are listed on Upfynd as dispute and fraud tools. We have not compared them, so check their sites for what they cover.

What to do when the seller has already been paid out

A transfer reversal needs money to take. Stripe's guide says that if a connected account's balance goes negative because of a dispute or refund, Stripe holds a reserve on its available balance. For accounts in the US or Canada, if payments.debit_negative_balances is set to true, Stripe automatically tries to debit the connected account's external account.

Outside those countries the safety net is thinner. Sharetribe's article says that where Stripe can't withdraw from the seller's bank account, negative or insufficient funds from disputes can make the seller's forthcoming payouts fail.

Stripe's own best-practice list for platforms includes these preventive steps:

• Delay payouts for new businesses for a set period; its example is two weeks.
• Run a balance check before you issue a refund, to confirm the connected account has enough funds.
• Charge the stored payment method to cover the refund first, if needed.
• Keep sellers informed about how disputes work and encourage them to hold adequate balances.

We'd start with the payout delay. It costs nothing to build and gives every later step something to reverse against. The trade-off is seller cash flow, so say so in your onboarding rather than in a support reply.

On Sharetribe, cancel through Console, not the Stripe Dashboard

If your marketplace runs on Sharetribe, the tool sets the order of operations. Its refund help article says that by default only operators can cancel a transaction and start a refund, and that a refund can only happen before the transaction is marked complete. After that, the money can only be refunded from your own Stripe balance, not the seller's.

The windows depend on the transaction process. Per that article, calendar bookings complete automatically 2 days after the booking period ends, purchases 14 days after the provider marks them shipped, and digital downloads 7 days after purchase. Buyers or operators can raise a dispute within 14 days on purchases and within 7 days on digital downloads.

Sharetribe strongly advises against refunding from the Stripe Dashboard, because refund data flows from Sharetribe to Stripe and not back. Its worked example uses two 100 euro orders with 10 percent commission on each side. The operator refunds one manually and keeps the buyer commission as a penalty, which leaves the provider with 70 euros. The other order's 90 euro payout then fails, even though nothing is wrong with it.

Partial refunds aren't supported out of the box either. Sharetribe says they need code customization, and that a partial refund issued in the Stripe Dashboard leaves Sharetribe's records out of sync. Its fix for the failed payout is to compare the connected account's balance with the transaction's PayoutTotalConverted value in the CSV export, then create the payout manually from the Stripe Dashboard.

A refund policy to write before the first dispute

Everything above is mechanics. These five decisions are ours, not Stripe's or Sharetribe's, and each one removes a step from a bad week.

1. Who decides. State in your seller terms whether you or the seller approves a refund, and who pays return shipping if relevant.
2. Permission to recover. Say you may reverse transfers and offset refunds or disputed amounts against future payouts. Without it, you are recovering from a seller who never agreed to repay.
3. Your commission. Choose in advance whether a refund returns it. Sharetribe's example shows how a case-by-case choice can break a later payout.
4. Payout delay. Pick a hold period for new sellers and publish it.
5. An owner for the clock. Someone must see the dispute-created webhook and meet the 7 to 21 day response deadline. Stripe warns that missing it can lead to an automatic loss.

If you are still choosing a stack, browse the marketplaces and on-demand category and the payments and banking category, then read the refund and dispute pages of whichever processor you pick before you sign. Makers building a marketplace tool can list it for free on Upfynd.

What we read, and what this is not

We read the Stripe and Sharetribe pages linked above on October 28, 2026. This is a summary of their documentation, not a test of either product, and we did not run a marketplace through it. Vendor documents change, so confirm the current wording before you build on it.

This is not legal advice. Your liability to buyers and sellers depends on your terms, the countries you sell in and local consumer law, none of which this post covers. Where real money rests on it, read the current Stripe terms for your country and take advice.