Stripe Connect marketplace: split payouts and fees
The official Stripe Connect documentation gives marketplaces a recommended setup: the customer pays your platform, you keep a platform fee, and the rest goes to each seller's connected account as a split payout. You then pay the Stripe fees and handle refunds and disputes. Two charge types do this work: destination charges for one seller per payment, and separate charges and transfers for a basket spread across several sellers. That choice decides who carries the financial risk, so make it before writing any code.
Everything here comes from Stripe's documentation as read on 1 November 2026. I build web applications and online stores, so I have an interest in this subject. I am not affiliated with Stripe. Have your accountant and lawyer review your final flow.
Stripe Connect marketplace payments: the three charge types
Stripe's page on how charges work in Connect explains that the charge type determines how funds are split, whose name appears on the customer's statement, and which account is debited for a refund or a chargeback. The marketplace guide then narrows the choice down: for a classic marketplace, you are the merchant of record and use one of the two indirect types.
| Charge type | Stripe's typical use | Fees and refunds fall on |
|---|---|---|
| Direct charges | SaaS and store builders, where customers deal with the merchant and often do not know the platform | Refunds and disputes hit the connected account; you choose who pays Stripe fees |
| Destination charges | Customers buy on your platform, one seller per transaction | Your platform balance |
| Separate charges and transfers | One payment for several sellers, or a seller not yet known at payment time | Your platform balance |
Stripe is plain about the third option: it requires a more complex integration, and you should use it only if your business case demands it. A single basket from several sellers is a legitimate reason. A desire to keep your options open is not.
Split payouts and platform fees in practice
With destination charges, the fee is an API parameter. Stripe's guide to platform fees shows application_fee_amount sent with transfer_data[destination]. The full amount goes to the connected account right after capture, then the fee returns to the platform. The fee cannot exceed the charge, and it is expressed in the currency of the transaction.
With separate charges and transfers, there is no such parameter: your commission is simply what you do not transfer. Stripe gives a food delivery example. A customer pays 100 dollars, Stripe takes 3.20, the platform sends 70 to the restaurant and 20 to the driver, and 6.80 stays with the platform. The same page warns that you will usually need an accounting ledger to track funds, especially if you hold money for more than a short period. That ledger is real development work, and it is often missing from early estimates.
Payouts are a separate step. Stripe's payout guide says that by default, funds in a connected account are paid out daily. You can set an automatic schedule, trigger manual payouts, offer Instant Payouts, or keep funds on the platform balance with these charge types. Stripe also lists webhook events such as payout.paid and payout.failed. A failed payout disables the external account until it is updated, so your seller area must show this and tell the seller what to do.
What the fees really look like
Your commission must cover more than your margin. Stripe's guide states that a marketplace pays transaction fees, per account fees and dispute fees, and that you should charge enough to keep your balance from going negative. The Connect pricing page, viewed in its French version, shows two models. When Stripe collects processing fees directly from connected accounts, the platform pays nothing extra. When you manage pricing, it lists 2 euros per active account per month, where an account counts as active in any month it receives a payout, plus 0.25% and 0.10 euros per payout.
The marketplace setup Stripe recommends places the Stripe fees on you, so run the numbers on your actual average basket. Low value orders from many small sellers are where a fixed fee per payout hurts most. Grouping payouts weekly can reduce the number of transfers, but sellers may prefer faster payment, so treat this as a commercial decision.
The risk that surprises new founders
The marketplace guide says clearly that your platform must cover the negative balances of its connected accounts. With both indirect charge types, refunds and disputes are debited from your platform balance. You can reverse the transfer to recover the money, but if the seller's balance is insufficient, a refund request that includes a transfer reversal returns an error instead of a pending refund.
So imagine a seller who ships nothing, receives the funds, and disappears. Your platform repays the customers. Before launch, decide how long you hold funds, which sellers you accept, what your terms allow you to deduct, and who follows up on disputes each week. Stripe suggests Radar for risk detection, but no tool replaces those rules.
What Connect does not build for you
Stripe lists its essential marketplace tasks: create and onboard connected accounts, set up dashboard access, enable payment methods, accept payments, collect fees, pay out and manage refunds and disputes. This is all money and identity. Your catalog, seller product forms, order split per seller, shipping rules, returns and invoices remain your project. Commerce frameworks do not necessarily solve this either: Medusa, for instance, describes a marketplace as a recipe to build, with a custom module, order splitting and a separate vendor dashboard.
European law adds another layer: seller checks, consumer information and tax reporting. If you operate in France, read my article on marketplace legal duties, which is written in French, before you settle your onboarding form.
When not to build this
A marketplace is the wrong first project if you have only three or four suppliers. You could sell their products in a normal shop, pay them by invoice each month, and test demand with far less risk. Direct charges may be a better fit if your merchants run their own businesses and sell under their own names, as with a store builder. And if you need a proven multi-vendor product next week, a specialised marketplace vendor will be faster than custom development from me or from anyone else.
Next step
Write down one real order from start to finish: the basket, the seller or sellers, your commission, the delivery, then a partial refund. If you can describe the money at every stage, your choice of charge type will follow. To check it with a developer before committing, send me that example through my web application page. I reply within 24 working hours, and you will speak directly with the person who writes the code.