How Stripe Connect Marketplace Payouts Work (and How to Design Them)

How does Stripe Connect work for marketplaces?

Stripe Connect is the part of Stripe built for multi-party businesses: a marketplace accepts a payment from a buyer and routes the seller share to a connected account, a Stripe account that belongs to the seller but is attached to the platform, as described in Stripe’s How Connect works documentation. A marketplace payout is the last step: the connected account balance is deposited to the seller’s bank on a schedule.

The short version of how Stripe Connect works for marketplaces is two stages: a charge collects the buyer’s payment, then a transfer moves the seller share into the connected account and a payout moves it to the bank. Every decision about Stripe Connect marketplace payouts sits inside those stages: which account the charge lands on, how much is transferred, what the platform keeps, and when the payout leaves Stripe.

• Stripe Connect has three charge types, direct, destination, and separate charges and transfers, and the choice fixes which account Stripe debits for refunds and disputes, per Stripe’s charge documentation.
• Standard, Express and Custom are the legacy account types; Stripe now recommends controller properties or Accounts v2, with the same tradeoffs of effort and liability, per Stripe’s account documentation.
• A platform that sets its own seller pricing pays Stripe $2 per monthly active connected account plus 0.25% and 25 cents per payout, per Stripe’s Connect pricing page.
• Connected accounts pay out daily by default; a platform that carries dispute liability can set weekly, monthly or manual schedules and delay payouts by up to 31 days, per Stripe’s payout schedule documentation.
• Under the second Payment Services Directive (PSD2), a European marketplace acting for both buyer and seller must hold a payment license or never possess the funds, per Stripe’s PSD2 guide.
• Sigi Technologies has shipped both patterns: Busy Bean Coffee splits each settled order into partner and supplier transfers and holds payouts until an offline check clears; ServiPR has every provider connect their own Stripe account so the platform never holds provider funds.

Which Stripe Connect account type should a marketplace use: Standard, Express or Custom?

A connected account is the Stripe account a seller receives payouts into, created or linked through the platform. The Express vs Standard vs Custom accounts question is three axes: integration effort, who the seller deals with, and who carries fraud and dispute liability. Stripe’s account type documentation has the full table and now points new platforms to controller properties or Accounts v2, which express the same choices as settings rather than a fixed type. Two facts on that page matter most: an account’s type cannot be changed after creation, and Standard and Express accounts update automatically when a country’s compliance requirements change while Custom accounts do not.

• Standard: the seller holds a full Stripe account and dashboard, connects by OAuth or API, and Stripe handles onboarding and support. With direct charges the seller carries liability. Best when sellers already run online businesses, such as on store builders like Shopify.
• Express: Stripe runs onboarding and identity verification, the seller gets a lighter dashboard, and the platform sets charge types and payout schedules by API. The platform carries liability. Stripe names home-rental and ride-hailing platforms. The default for most marketplaces.
• Custom: the seller never sees Stripe. The platform builds onboarding, the dashboard and support at significantly higher effort, and if it collects identity documents itself it holds government IDs and tax numbers.

Destination charges vs separate charges and transfers: which marketplace payment flow fits?

A charge type is the rule for which account a buyer’s payment is created on and how the seller share moves afterward. Stripe’s charge documentation defines three, and the choice is the most consequential in a marketplace payment flow because it fixes liability.

• Direct charges: the payment is created on the seller’s connected account and the platform takes an application fee. Refunds and chargebacks reduce the seller’s balance. Stripe recommends this for software platforms whose sellers’ customers may not know the platform exists.
• Destination charges: the payment is created on the platform and a portion transfers immediately to one connected account. Refunds, chargebacks and Stripe fees hit the platform balance. Stripe names ride-hailing apps and contractor marketplaces: one buyer, one seller, one transaction.
• Separate charges and transfers: the payment is created on the platform, which later creates one or more transfers, possibly before the seller is known. Stripe’s example is a delivery platform splitting one payment between a store and a courier, and it advises using this only when the business needs it.

The decision rule: one seller per order and a buyer paying your brand means destination charges. One order paying several parties, or money arriving before you know who will fulfil it, means separate charges and transfers. Sellers who own their customers means direct charges.

On Busy Bean Coffee, a multi-partner ordering platform Sigi Technologies built for an office coffee service in South Carolina, card and subscription revenue lands in Busy Bean’s own Stripe account and Stripe Connect splits each settled order into partner and supplier transfers according to commission rules configured in the admin panel. That is the one-to-many shape Stripe documents under separate charges and transfers: one charge on the platform, then split payments driven by the platform’s own rules.

How do platform fees and application fees work in Stripe Connect?

An application fee is the amount a platform keeps from a payment before the seller share is transferred. On a destination charge the platform can transfer a reduced amount and keep the difference, or transfer the full amount and collect the fee afterward; Stripe’s charge documentation shows both flows.

How much to take is a product decision. Andreessen Horowitz defines the marketplace take rate as the percentage of gross merchandise value the marketplace captures and says it usually runs from a low single-digit percent to the mid-30s, driven by fragmentation, substitutes and the operational value added, in its marketplace glossary. Sharetribe’s study of the top 100 online marketplaces found an average take rate between 10% and 30%, with individual marketplaces ranging from a few percent to 95%, per its commission and take rate guide.

Two costs sit under the take rate: Stripe’s processing fee, assessed on the platform for indirect charges, and Connect fees. On Stripe’s published Connect pricing, a platform handling its own seller pricing pays $2 per monthly active connected account and 0.25% plus 25 cents per payout; platforms that let Stripe set seller pricing pay no platform fees. Model the take rate on the net after those fees, and decide before launch whether a refund reverses the seller transfer or comes out of platform margin. On Busy Bean, commission rules are set per partner and per supplier in the admin panel and drive the Stripe Connect transfers; the case study publishes no percentages.

How should you design payout schedules, and when should a payout be held?

A payout schedule is the rule that decides when a connected account’s available balance is sent to the bank. By default, charges made on behalf of a connected account accumulate in its balance and pay out on a daily rolling basis, per Stripe’s payouts documentation for connected accounts. Platforms that carry dispute liability can set the interval to daily, weekly, monthly or manual and add a delay of up to 31 days, per Stripe’s payout schedule guide.

Stripe typically schedules a new account’s first payout to complete within 7 to 14 days of its first live payment, per Stripe’s payouts overview; a standard payout then reaches the bank 1 to 2 business days after submission and an instant payout typically arrives within 30 minutes at a 1% fee, per Stripe’s connected account payouts page. Listen for the payout.failed event, because a failed payout disables the seller’s bank account until the platform updates it.

The design principle is that a payout should follow the business event that makes the money final, not the calendar: delivery confirmed for goods, the job marked complete for services, and for a platform that still accepts offline payment, the moment the cash actually arrives.

How does KYC onboarding for sellers work with Stripe Connect?

Know Your Customer (KYC) onboarding is the identity and business verification a seller must pass before a connected account can receive payouts. Stripe offers three ways to collect it, per its onboarding configuration guide: a Stripe-hosted form with the platform’s branding, an embedded component inside the platform’s own app, and API onboarding where the platform builds every screen. Stripe recommends the first two because they update automatically when requirements change, and says a platform choosing API onboarding must review its requirements at least every six months.

The product design on top is a state machine for the seller: listings and bookings open only when your database says the connected account exists, has passed verification and has payouts enabled, with those flags set from Stripe’s account events. Requirements can reappear when volume crosses a threshold, so the state machine also has to handle a seller falling back to restricted.

On ServiPR, linking a Stripe account is a step inside the provider app and identity and payout checks sit with Stripe, while the admin panel owns provider onboarding and verification for the marketplace’s own vetting. Marketplace vets quality, Stripe vets identity.

Who is legally responsible for marketplace funds?

A marketplace that collects a buyer’s money and later pays a seller is moving money for third parties, which is regulated in most jurisdictions. In Europe, PSD2 narrowed the commercial agent exemption to platforms that act for either the payer or the payee, not both; since most marketplaces act for both, a platform avoids a license only if it does not possess or control the funds, per Stripe’s guide to PSD2 for marketplaces. Stripe Connect is built so the platform never takes possession; Stripe, as a licensed provider, does.

In the United States, money transmission is licensed state by state. Some states provide an agent of the payee exemption, under which receiving money from a buyer for goods or services owed to a third party does not require a money transmitter license; the Conference of State Bank Supervisors keeps a state-by-state map of the exemption, and Modern Treasury counts 22 states allowing it plus 3 case by case in its agent of the payee overview. None of this is legal advice. The design conclusion is the same in both regions: keep the funds in Stripe, keep your own ledger as a record, and never build a wallet you top up and drain yourself unless you intend to be licensed. If the product will hold balances or lend, read how to build a fintech app.

What does it typically cost to build Stripe Connect payouts into a marketplace?

Cost follows the number of parties in a payout, how much payout logic operators can edit, and how much reconciliation is automated at launch. Sigi Technologies attaches no figure to Busy Bean or ServiPR. The ranges below are typical-scope planning estimates for the whole marketplace build, using the bands in Sigi’s guide to how much it costs to build a mobile app; the payments layer is a slice of each.

Ongoing cost is Stripe’s processing and Connect fees, which scale with volume rather than with the build. For the budget beyond payments, see how much it costs to build a marketplace.

Should you build on Stripe Connect or use a hosted marketplace platform?

Hosted marketplace products such as Sharetribe, CS-Cart and Yo!Kart ship split payouts out of the box, and for a simple catalog with one commission rate they are the right choice. A custom Stripe Connect integration earns its keep when the money rules are the business: Busy Bean was built custom because each order pays a territory partner and a shipping supplier on rules that differ per party, with check settlement that holds payouts until the check clears, as the Busy Bean case study sets out against the hosted options.

How do you build Stripe Connect marketplace payouts step by step?

This is the sequence Sigi Technologies follows for a marketplace payout flow. Each step fixes something the next depends on.

1. Write the money flow on one page before any screen: who pays, who is paid, what the platform keeps, and what event makes each amount final.
2. Choose the charge type from that page, then the account configuration, knowing it cannot be changed later. Default to Express-style accounts with hosted or embedded onboarding.
3. Define the seller state machine: created, verification pending, payouts enabled, restricted. Drive it from Stripe account events and gate listings on it.
4. Model money as ledger entries against order stages with pending and released states, so every transfer traces to an order event and a rule.
5. Set the payout schedule to follow the finality event, and build the hold path first: refund windows, disputes, and any offline payment that has to clear.
6. Wire webhooks for charges, transfers and payouts, and post every fee and payout to accounting so month-end is a report, not a reconciliation project.
7. Test the unhappy paths before launch: a refund after transfer, a dispute, a failed payout, a seller who never finishes onboarding, and a payment that never clears.

A related single-merchant pattern, charging an upfront amount and settling it against a final invoice, is covered in how to build an on-demand laundry app.

Related reading

For the architecture around the payments layer, start with the pillar guide to how to build a multi-vendor marketplace, then size the budget with how much it costs to build a marketplace. If the product will hold balances or move money outside a marketplace sale, read how to build a fintech app. The two builds cited here are documented in the Busy Bean Coffee multi-partner platform case study and the ServiPR services marketplace case study. Sigi’s e-commerce development practice scopes marketplace and payout builds like these, or contact Sigi to walk through your money flow on one page.