Stripe for Marketplaces: Everything You Need to Know in 2026

Payments will make or break your marketplace. You can have the perfect niche. You can have buyers. You can even have sellers. But if money can't move cleanly between them - you don't have a business.

And that's where Stripe Connect comes in. It's the payment infrastructure behind marketplaces like Lyft, Instacart, Kickstarter, and most ecommerce marketplaces. But setting it up yourself is one of the most complex parts of building a marketplace.

In this guide, I'll break down everything you need to know - what Stripe Connect is, why it's hard, which account type to choose, how money flows, and the biggest mistakes to avoid. If you're earlier in the journey and not sure where Stripe Connect fits in the bigger picture, start with our guide on how to start an online marketplace first.

What Stripe Connect Actually Is

First, let's clarify something. Regular Stripe and Stripe Connect are NOT the same thing.

Regular Stripe is for one business taking payments from customers. Stripe Connect is for platforms - applications that move money on behalf of other people.

In a marketplace, you have:

• A platform account - that's you, the marketplace operator
• Multiple connected accounts - those are your sellers

Stripe Connect handles the hard parts:

• Identity verification (KYC) - verifying sellers are who they say they are
• Compliance - handling regulatory requirements across countries
• Payment splitting - automatically dividing payments between you and sellers
• Payouts - sending money to seller bank accounts on schedule
• Tax reporting - generating 1099s and other tax documents

Without Connect, you legally cannot collect payments and distribute them to other people. You'd be acting as an unlicensed money transmitter.

Why Stripe Connect Is So Hard to Set Up

On paper, Stripe Connect sounds simple. In reality - it's one of the hardest parts of building a marketplace.

Here's what you actually have to deal with:

• KYC and onboarding flows - each seller must verify their identity, bank account, and business details
• Country restrictions - Stripe Connect is available in 46+ countries, but rules vary by region
• Split payments vs. destination charges - two different models for how money is routed, each with trade-offs
• Refund logic - when a buyer requests a refund, who pays? The seller? The platform? Both?
• Dispute handling - chargebacks on marketplace transactions are complex because multiple parties are involved
• Testing payouts - you can't just test with fake money; payout flows need real verification
• Webhooks - Stripe sends events for every state change; you need to handle dozens of them
• Edge cases - what happens when a seller fails verification mid-transaction?

The 3 Stripe Connect Account Types

Stripe Connect has three account types. Picking the wrong one can cause serious headaches down the road.

1. Standard Accounts

The seller owns and controls their own full Stripe account. Stripe handles everything - onboarding, compliance, dashboard. You have the least control over the experience. The seller sees the Stripe dashboard directly, and branding is Stripe's, not yours.

2. Express Accounts (Recommended for Most Marketplaces)

Stripe handles compliance and verification, but you control the user experience. Sellers go through a Stripe-hosted onboarding flow, but it's lighter than Standard. This is the sweet spot - you get a good balance of control and simplicity without the compliance burden.

3. Custom Accounts

Full control over everything - onboarding UI, dashboard, communication. But full responsibility too. You're handling compliance, identity verification flows, and regulatory requirements yourself. Massive compliance burden. Only choose this if you have a dedicated engineering and legal team.

The bottom line: if you're building a typical marketplace in 2026, Express is almost always the right choice. It's what Prometora uses, and it's what I recommend to every founder I talk to.

Accounts v2: The New API (December 2025)

In December 2025, Stripe shipped Accounts v2 - a new way to model connected accounts on Connect. The three account types above (Standard / Express / Custom) still exist and aren't going away. But if you're starting a new marketplace in 2026, Stripe now recommends building on Accounts v2 instead of the legacy v1 model.

Two things change with v2:

• Flexible configurations replace fixed account types. Instead of locking a connected account to a single type, you attach configurations - merchant (to accept payments), customer (to be charged as a customer), recipient (to receive transfers). An Account can have multiple configurations at once.
• One Account object replaces separate Account + Customer. In v1, if a connected seller also bought something on your platform, you had to create a separate Stripe Customer object and keep a mapping between Account ID and Customer ID. In v2, the same Account object handles both - no more dual-object bookkeeping.

Should you use Accounts v1 or v2?

• New platforms launching in 2026: start on v2. Simpler identity model, fewer objects to track, and it's the path Stripe is investing in.
• Existing platforms on v1: you don't need to migrate today. v1 isn't deprecated. Stripe does discourage maintaining both versions indefinitely, but offers a migration guide when you're ready.
• OAuth-based integrations: stay on v1. v2 doesn't support OAuth-authenticated connected accounts yet.

For the full v2 reference, see Stripe's Accounts v2 documentation. Most of the rest of this article - payout flows, KYC, webhooks, refunds, disputes - applies identically to both v1 and v2. The API surface changed; the underlying marketplace mechanics didn't.

How Money Actually Flows Through a Marketplace

Let's walk through a real example. Say a buyer purchases something for $100 on your marketplace, and your commission is 10%.

• Buyer pays $100 - the full amount goes to Stripe
• Stripe takes its processing fee - approximately $3.20 (2.9% + $0.30)
• Your platform takes its commission - $10 (your 10% application fee)
• Seller receives $86.80 - the remainder after both fees
• Stripe holds the funds - based on your payout schedule (usually 2-7 days)
• Seller gets paid - directly to their bank account via Stripe

This all happens automatically through Stripe Connect - if it's set up correctly. If you don't understand this flow, you can't debug issues when money goes missing or sellers complain about incorrect payouts.

The Seller Onboarding Problem

Here's the real retention killer. Traditional Stripe onboarding requires sellers to complete a 10-15 minute compliance form BEFORE they can sell anything.

Think about that from the seller's perspective. They just signed up for your marketplace. They haven't made any money yet. There's no emotional investment. And now you're asking them to provide their ID, bank details, tax information, and business documents - before they've experienced any value.

Most drop off. They haven't made money yet, so there's no incentive to push through the friction. And your marketplace loses sellers before they ever list a product.

Deferred Onboarding: The Solution to Seller Drop-Off

This is why I use something called deferred onboarding - and I've open-sourced the full implementation on GitHub.

Instead of forcing sellers to complete full Stripe onboarding upfront, the deferred approach works like this:

• Step 1: Create a minimal Stripe Express account - only the seller's country is required
• Step 2: Let them start listing products and accepting payments immediately
• Step 3: The platform holds the funds safely (manual payouts are enabled)
• Step 4: Track pending earnings in your database as sales come in
• Step 5: After a threshold (e.g., 3 sales), prompt the seller to complete full onboarding
• Step 6: Once verified, automatically transfer all accumulated earnings to the seller

How the Two Payment Modes Work

The deferred onboarding pattern uses two different payment flows depending on the seller's verification status:

For unverified sellers (before full onboarding): The platform creates the charge and holds the funds. The seller's portion is tracked via metadata (seller_amount) and accumulated in a pendingEarnings field in the database. Unverified Express accounts don't have the transfers capability active yet, so Stripe won't allow direct transfers.

For verified sellers (after onboarding): Payments use destination charges with transfer_data.destination pointing to the seller's connected account. Funds flow directly to the seller, and the platform takes its fee via application_fee_amount. This is the standard Stripe Connect flow.

The magic happens in the account.updated webhook. When Stripe reports charges_enabled: true, the system automatically transfers all pending earnings to the seller's newly verified account.

Production Considerations

Deferred onboarding means your platform holds funds initially. That means you carry the dispute risk during the holding period. Before going to production, consider these safeguards:

• Volume caps - limit the number of sales or total dollar amount before requiring onboarding
• Transfer delay - wait 7-14 days after onboarding before transferring funds (covers the dispute window)
• Refund controls - keep refunds platform-controlled until the seller is verified
• Sales threshold - trigger onboarding prompts after a reasonable number of sales (3 is a good starting point)

v1 vs v2 note: The deferred-onboarding pattern works identically on Stripe Accounts v2. You still create an Account with minimal identity (country only), still hold funds until requirements are satisfied, and still trigger payout-release on a state-change webhook. The capability names change (the v1 transfers capability becomes stripe_balance.stripe_transfers, v1 payouts becomes stripe_balance.payouts), and the webhook surface differs slightly, but the six-step flow above is preserved. If you're starting on v2, replace the v1 capability and webhook references with their v2 equivalents and the rest of this section still applies.

The open-source repo demonstrates the full pattern with code examples - but production requires these additional safeguards based on your specific risk tolerance.

How Prometora Handles All of This

Inside Prometora, all of the Stripe Connect complexity - including deferred onboarding - is abstracted away. Here's what that means in practice:

• Stripe Express is pre-configured - no API integration needed
• Deferred onboarding is built-in - sellers can list and sell before completing Stripe verification, with pending earnings tracked automatically
• Automatic payout on verification - when a seller completes onboarding, all accumulated earnings are transferred immediately
• Commission logic is handled - set your percentage and it's automatically collected on every transaction
• Webhooks are already wired - account updates, payout events, dispute notifications, and verification state changes are all handled
• Shipping payout deferral - for physical goods, payouts are held until the seller marks the order as shipped
• Seller retention is optimized - the entire flow is designed to minimize drop-off and maximize completed onboarding

You don't write a single line of payment code. You don't read Stripe API docs. You don't build webhook handlers. You connect your Stripe account, set your commission, and your marketplace handles payments - including deferred onboarding - from day one. Comparing platforms? See the full marketplace software comparison, or specifically Prometora vs Sharetribe side by side.

Common Mistakes to Avoid

After building multiple marketplaces and helping others launch theirs, these are the biggest Stripe Connect mistakes I see:

• Choosing Custom accounts too early - you don't need full control on day one. Start with Express.
• Not testing payouts - test the full flow: buyer pays → seller receives. Don't assume it works.
• Ignoring refund logic - decide upfront who absorbs the cost of a refund. Document it clearly.
• Not handling disputes - chargebacks happen. Have a process before they do.
• Forcing full onboarding too early - this is the seller retention killer. Use deferred onboarding instead.
• Assuming Stripe handles UX - Stripe handles compliance. You handle the product experience.

Remember: Stripe handles compliance. You handle the product experience. The most common failure mode is founders thinking Stripe does more than it actually does.

Calculate Your Marketplace Revenue

Now that you understand how payments flow, model what your marketplace will actually earn. Factor in your commission rate, Stripe's processing fees, and your expected transaction volume.

Want to share projections with co-founders or save scenarios? Open the full Marketplace Revenue Calculator → Export to CSV or Google Sheets, share via link, and switch between plans to compare break-even.

Frequently Asked Questions