Stripe Connect Explained for Marketplace Founders: The Bits Nobody Tells You

Right. You're building a marketplace. Buyers pay sellers, you take a cut, everyone's happy. Simple, yeah?

It is not simple. It is, in fact, one of the most complex parts of any marketplace build. And if you get it wrong, you're either holding money illegally, pissing off your sellers, or both.

I built TidyLinker with Stripe Connect. Here's everything I wish someone had told me before I started.

What Stripe Connect Actually Is

Stripe Connect is Stripe's solution for platforms and marketplaces that need to move money between multiple parties. Instead of just "customer pays business," it enables "customer pays business A, and platform B takes a fee."

You — the platform — have a Stripe account. Each of your sellers also has a Stripe account (connected to yours). When a buyer pays, the money flows through this connected account system.

The Three Account Types (And Which One You Want)

Stripe Connect offers three account types for your sellers:

Standard accounts — The seller has their own full Stripe dashboard. They control their payout schedule, handle their own disputes, and manage their own account. You have limited control. Best for: platforms where sellers are established businesses who want full control.

Express accounts — The seller gets a simplified Stripe dashboard. You have more control over the experience. Stripe handles most of the onboarding. Best for: most marketplaces. This is probably what you want.

Custom accounts — You build the entire onboarding UI yourself. Maximum control, maximum work. You handle everything: identity verification, bank account collection, the lot. Best for: platforms where you need complete control over the user experience and you have the development budget to build it properly.

For TidyLinker, I went with Express accounts. The onboarding flow is handled by Stripe (so I didn't have to build identity verification from scratch), but I still control the payment flow and platform fees.

How Money Actually Flows

Let's say a buyer pays £100 for a service on your marketplace, and your platform fee is 10%.

Option 1: Direct charges The payment goes directly to the seller's connected account. You specify a platform fee (application fee) at the time of charge.

Buyer pays £100
→ £100 lands in seller's Stripe account
→ £10 (your platform fee) is transferred to your platform account
→ Stripe takes their fee (usually from the seller's portion)
→ Seller receives £100 - £10 (your fee) - £2.90 (Stripe fee) = £87.10

Option 2: Destination charges The payment goes to your platform account first, then a portion is sent to the seller.

Buyer pays £100
→ £100 lands in your platform account
→ £87.10 is transferred to the seller's connected account
→ You keep £10
→ Stripe takes £2.90

Option 3: Separate charges and transfers You charge the buyer and manually transfer funds to the seller later. Most flexible, most complex.

The difference matters for tax, reporting, and who "owns" the customer relationship. Direct charges mean the seller is the merchant of record. Destination charges mean you are. This has implications for disputes, refunds, and legal responsibility.

Get advice on this from someone who understands your specific business model. This is not a "pick whichever seems easier" decision.

Platform Fees: Taking Your Cut

Your platform fee is how you make money. Stripe Connect lets you specify an application_fee_amount on each payment. This is the amount that goes to your platform account.

Things that will catch you out:

Stripe's fee comes out of someone's portion. Make sure you know whose. If you charge a £10 platform fee on a £100 payment, and Stripe takes £2.90, does the seller get £87.10 or does the seller get £90 and you get £7.10? It depends on your charge type.

VAT on platform fees. If you're a UK business charging a platform fee to UK sellers, you probably need to charge VAT on that fee. That means your £10 platform fee is actually £8.33 + £1.67 VAT. Your accountant needs to be involved here. Do not guess.

Different fee structures for different sellers. You might want to charge 10% for new sellers and 8% for high-volume sellers. Stripe Connect supports this — you set the application fee per transaction. But your business logic needs to handle it.

KYC: The Thing That Will Drive Everyone Mad

KYC stands for Know Your Customer, and it's the legal requirement for financial platforms to verify the identity of everyone who receives money through them. Stripe handles the verification, but your sellers have to actually do it.

Here's what happens in practice:

1. Seller signs up on your platform
2. You create a connected Stripe account for them
3. Stripe sends them an onboarding link
4. Seller has to provide: full name, date of birth, address, last four digits of their national insurance number (in the UK), bank account details, and sometimes a photo of their ID
5. Stripe verifies all of this
6. If anything doesn't match, Stripe asks for more information
7. The seller emails you asking why they have to provide all this personal information to some random website
8. You explain it's a legal requirement
9. They don't believe you
10. Eventually, they complete onboarding

This will be your biggest source of seller drop-off. I'm not exaggerating. A significant percentage of sellers will start the onboarding process and not finish it. The ones who do finish will complain about it.

Things to know:

• Onboarding requirements vary by country. UK requirements are different from US requirements.
• Stripe may request additional verification at any time, not just during initial onboarding. A seller who's been happily receiving payments for months might suddenly be asked for a passport photo.
• If a seller's account goes into "restricted" status, their payouts are paused until they provide the requested information. They will blame you.
• You need clear documentation and support flows for this. "Contact Stripe" is not an acceptable answer for your sellers — they signed up on YOUR platform.

Payout Timing

Standard Stripe payout timing in the UK is 7 days for new accounts, dropping to 2 days once the account is established. This means:

• Day 1: Buyer pays £100
• Day 1-7: Money sits in the seller's Stripe balance
• Day 7 (or day 2 for established accounts): Stripe sends money to the seller's bank account
• Day 8-9: Money appears in the seller's bank account

Your sellers will ask "where's my money?" approximately once per hour during this waiting period. Build a dashboard that shows pending payouts, expected payout dates, and completed payouts. Make this information easily accessible. You will save yourself hundreds of support emails.

The Gotchas Nobody Tells You

Refunds come from the seller's pending balance. If a seller has £100 in pending payouts and you refund a £50 transaction, their pending balance drops to £50. If they don't have enough in their balance, you'll need to claw it back from a future payout or cover it yourself. Think about this before it happens.

Disputes (chargebacks) are your problem. Even with connected accounts, dispute management falls on you as the platform. You'll need to provide evidence, respond within deadlines, and potentially eat the cost if you lose. Budget for a 0.5-1% dispute rate.

Stripe Connect pricing is on top of standard Stripe fees. The standard fee is 1.5% + 20p per transaction (UK cards). Connect adds additional fees for payouts to connected accounts. The exact pricing depends on your setup, but expect your total payment processing cost to be 2-4% of transaction volume.

Test mode is your best friend. Stripe's test mode with connected accounts lets you simulate the entire flow without real money. Use it extensively. Test the edge cases: what happens when a seller's account is restricted? What happens when a refund exceeds the seller's balance? What happens when a payout fails because of incorrect bank details?

International payments add complexity. If your marketplace operates across borders, you're dealing with currency conversion, different KYC requirements per country, and varying payout timing. Each country adds complexity.

What It Costs to Build

Building Stripe Connect into a marketplace is not a weekend project. For a senior developer who's done it before (hello), budget:

• Basic integration (one payment flow, platform fees, seller onboarding): 2-3 weeks
• Full integration (multiple payment types, refunds, disputes, reporting, webhook handling): 4-8 weeks
• Polish (seller dashboards, payout tracking, automated communications): 2-4 weeks

That's 2-4 months of development time for a proper implementation. If someone quotes you a week, they either don't understand the requirements or they're going to deliver something that breaks the first time a seller's KYC gets flagged.

Before You Build: Questions to Answer

1. Who is the merchant of record — you or the seller?
2. What's your platform fee structure?
3. Do you need to support refunds? (Yes, you do.)
4. What countries will your sellers operate in?
5. What happens when a seller doesn't complete KYC?
6. How will you handle disputes?
7. Do you need subscription/recurring payments through connected accounts?

Answer all of these before a developer writes a single line of code. These are business decisions that affect architecture, and changing them after the fact is expensive.

---

If this resonates, I work with founders directly — from early MVP planning through to scaling.