How Does Stripe Connect Work for Marketplaces?
Stripe Connect explained by a team running it across seven live marketplaces: account types, fees, payout flows, and the gotchas the documentation undersells.
Stripe Connect is Stripe’s toolkit for platforms that move money between a customer, your marketplace, and one or more connected sellers - onboarding, charges, application fees, payouts and identity checks in one rails system. You need it when vendors must get paid through your product rather than invoicing buyers off-platform. We run Connect across seven live marketplaces we operate ourselves; the documentation explains the APIs, and ops teaches you where onboarding drop-off and refunds across splits actually hurt.
What Stripe Connect is and when a marketplace needs it
What is Stripe Connect used for?
Stripe Connect is used to accept payments on a platform and route funds to connected accounts (sellers, service providers, venues, creators) while your platform takes an application fee or otherwise monetises the flow. Marketplaces, gig platforms and SaaS products with payouts all sit here. Single-merchant shops taking card payments for their own goods usually need ordinary Stripe Payments, not Connect.
What is the difference between Stripe and Stripe Connect?
Stripe Payments is “your business charges your customer”. Stripe Connect is “your platform charges (or facilitates charges) on behalf of many businesses, then pays them out”. Connect adds connected accounts, onboarding/KYC, charge types (direct, destination, separate charges and transfers), application fees, and payout configuration. If you only have one legal seller - you - Connect is usually unnecessary complexity.
Do I need Stripe Connect for a marketplace?
Yes, if sellers receive money through your product and you want card rails, identity verification and payout schedules handled inside Stripe’s ecosystem. Maybe not, if early liquidity is offline (bank transfer after a manual match) while you validate supply - though you will still need a payments plan before scale. Alternatives exist (Adyen for platforms, PayPal Commerce and others); Connect is the default we see in UK SME marketplace builds because of documentation depth and account tooling. Hub: marketplace development.
Standard vs Express vs Custom accounts: the choice that shapes your build
Account type is not a checkbox. It decides who sees Stripe-hosted onboarding, how much UI you build, and how much liability and branding you carry.
| Account type | Onboarding feel | Build effort | Typical fit |
|---|---|---|---|
| Standard | Sellers get a fuller Stripe account experience | Lowest | Platforms happy with Stripe-branded onboarding |
| Express | Stripe-hosted onboarding, lighter account surface | Medium | Most SME marketplaces we ship |
| Custom | You build the onboarding UI; maximum control | Highest | Branded, regulated or unusual KYC flows |
Pick this in Blueprint, before you recruit a hundred sellers into the wrong path. Changing account strategy after supply exists means re-onboarding people who already distrust payouts. Charge type (direct vs destination vs separate charges and transfers) pairs with account type - get both wrong and refund logic becomes a support nightmare.
Money flow: charges, fees, take rates and payouts
Worked example (illustrative numbers):
- Buyer pays £100 for a listing.
- Platform application fee (your take) is £10.
- Connected account is owed £90 before Stripe processing costs, depending on charge type and who pays card fees.
- Stripe later pays the connected account on its payout schedule.
- Your platform balance retains the application fee (minus any costs you agreed to absorb).
What fees does Stripe Connect charge?
Two layers matter. Card processing on Stripe in the UK is commonly 1.5% + 20p for standard UK cards (EU and international cards cost more - check Stripe’s current UK pricing page). Connect platform pricing then depends on whether Stripe handles pricing for connected accounts or you do.
When you handle pricing for users (common marketplace pattern), Stripe’s published UK Connect extras include about £2 per monthly active account (active in months with payouts) and 0.25% + 10p per payout, with further options for risk tools and volume. When Stripe handles pricing, platforms can avoid those account/payout Connect fees and monetise via revenue share arrangements instead. Always verify live figures on stripe.com/gb/connect/pricing before you model unit economics - fee tables change.
Your commercial take rate sits on top of those rails. How to choose commission vs subscription vs listing fees is a separate commercial problem - see how marketplaces make money. Connect is the pipe; take rate is the business model.
The gotchas from seven live integrations
Documentation shows happy paths. Operating Costhetix, Kinurture, BigSleep, WorkVans, Sponsorfy, Away Pubs and Jollee surfaces the rest:
Onboarding drop-off. Every extra KYC field costs completed sellers. Prefill what you can; explain why you need identity checks in plain English; save draft state so a vet practice owner can finish tomorrow.
KYC delays. Payouts wait on verification. Your support queue will fill with “where is my money?” before engineering hears about a webhook. Admin must show verification state without a developer diving the Dashboard.
Refunds across split payments. Partial refunds, application fee refunds, and chargebacks need explicit policy. If product and finance disagree on who eats a dispute, Connect will not save you.
Webhook truth. Treat webhooks as the system of record for payout and account updates. Polling the Dashboard is not an architecture.
Fee copy at signup. Sellers forgive a plain UI. They do not forgive discovering the take rate after their first busy weekend. Surface fees before the first listing goes live.
Express vs Custom regret. Teams pick Custom for brand control, then discover they under-budgeted onboarding UI. Teams pick Standard for speed, then discover sellers bounce on Stripe-heavy UX. Choose against real seller personas.
Build sequencing that puts payments early - before polish - is in how to develop a marketplace. Cost context for the whole platform sits in marketplace build cost.
What a Stripe Connect integration costs to build
In the UK, wiring Connect into a lean marketplace MVP often adds on the order of several thousand pounds of specialist work inside a wider £15,000-£30,000 MVP band; payments-heavy multi-vendor platforms in the £30,000-£75,000+ market band usually include Connect (or equivalent) as a core workstream rather than a bolt-on. Custom onboarding, complex split logic, subscription-plus-commission hybrids and deep admin for disputes push higher. Those are market ranges for the surrounding build - not a standalone Code23 SKU.
What moves the Connect line specifically:
- Account type and charge type complexity
- Seller onboarding UX and saved-state quality
- Refund, dispute and partial-capture rules
- Tax reporting and invoice artefacts vendors expect
- Admin for pause payouts, fee changes and verification review
Our marketplace builds set a fixed band after Blueprint, with fixed change scopes priced before work starts. Agent-assisted implementation speeds the plumbing; KYC policy and fee design still need human judgement.
Connect account type falls out of take rate, seller personas and refund policy - not the other way round. Work that sequence via marketplace development.
