Stripe Connect is the part of Stripe built for platforms and marketplaces that need to pay out other businesses or individuals, not just collect their own payments. It lets you onboard a seller, contractor, or vendor as a 'connected account,' route a share of each payment to them, and let Stripe handle the payout. It doesn't handle what happens on your side once dozens or hundreds of connected accounts are live: who's stuck mid-onboarding, whose payout looks wrong, and what your own books should show for each one.
1. Pick an account type. Stripe gives you three: Standard (the connected business has its own full Stripe dashboard and relationship with Stripe directly, you just route payments to them), Express (a faster, Stripe-hosted onboarding flow with a stripped-down dashboard, and your platform takes on more of the support burden), and Custom (you build the entire interface yourself; the connected account may never see Stripe's name at all). Most marketplaces that want sellers self-serving quickly land on Express.
2. Onboard each connected account. Standard and Express both use a hosted onboarding flow, or an embedded version of it, to collect the identity and bank details Stripe needs before it will pay anyone out. Custom means you collect and submit all of that yourself through the API.
3. Add the 'Connect with Stripe' OAuth button if you're using Standard. This is how a connected account authorizes your platform to interact with their existing or new Stripe account instead of you creating it on their behalf.
4. Route the money. Each charge can split automatically between your platform and the connected account, with your cut taken as an application fee. Stripe handles the actual transfer and payout scheduling once that split is defined.
5. Give the connected account visibility. Express accounts see their payouts and update their bank details through the limited Express Dashboard. Standard accounts use their own full Stripe dashboard. Custom accounts see whatever you decide to show them, since you own the entire interface.
Connect handles the plumbing: onboarding, the split, the payout. It doesn't watch your connected accounts for you. Someone still has to notice when an account is stuck in 'pending verification' for two weeks, or when a connected account's payout amount doesn't match what your own order records say it should be once your platform fee comes out.
The Express Dashboard is deliberately limited, by design, since Stripe built it to keep onboarding light. That's good for the seller, but it means your platform often can't get at the fine-grained data or actions you actually need for support or reporting through that dashboard, or sometimes through the API either, if it's a feature Stripe hasn't exposed for Connect accounts specifically. When that's the real blocker, we've built headless-browser automation that works through the dashboard itself to get at what the API won't give us, rather than telling a platform to just live without it.
Every connected account's onboarding and verification status pulled into one view automatically, with the ones stuck mid-setup or missing a required document flagged for a person, instead of someone scrolling the Connect dashboard account by account to find them.
Each transfer and application fee matched back to the order or invoice that generated it and synced into your own accounting, broken out by connected account, so the platform's books don't depend on someone rebuilding that math from a payouts CSV.
Tell us what you're currently checking by hand across your connected accounts, onboarding status, payout mismatches, dispute exposure, and we'll look at what Connect's own tools already cover versus what needs custom automation on top.
Tell us how many connected accounts you're managing and what you're checking on them manually right now, and we'll map out what's worth automating. Connect is just this page's example. The same question applies anywhere else your business still relies on someone checking a dashboard instead of a system flagging the exception.
Let's talk →Stripe's product for platforms and marketplaces that need to pay other businesses or individuals, not just accept payments for themselves. It handles onboarding a connected account, splitting a payment between your platform and that account, and paying both sides out.
Standard, Express, and Custom. Standard gives the connected account its own full Stripe relationship and dashboard. Express gives them a fast, Stripe-hosted onboarding flow and a limited dashboard, with your platform handling more of the support. Custom puts you in charge of the entire interface; the connected account may never interact with Stripe directly.
A simplified dashboard Stripe gives to Express connected accounts so they can see their payouts and update their own bank details, without the full feature set of a standard Stripe dashboard. It's deliberately light, which keeps onboarding fast but limits what the connected account (and sometimes your platform) can see or do through it.
A regular Stripe account belongs to a business accepting its own payments. A connected account sits underneath a platform's Stripe Connect setup, created so the platform can route payments and payouts to it, with the platform typically taking a fee on each transaction.
Yes. The Connect API exposes account status, verification requirements, and transfer and payout data, which is what we use to build the monitoring and reconciliation most platforms are still doing by hand. When a specific detail isn't exposed through the API or Express Dashboard, there's usually still a way to get at it; worth asking before assuming it's not possible.