Stripe Connect: Standard vs Express vs Custom Accounts Compared
Compare Stripe Connect Standard, Express, and Custom accounts by control, compliance burden, and integration effort to choose the right type for your platform.
A marketplace payment design needs decisions about seller onboarding, account control, payouts, fees, and disputes. Stripe Connect’s Standard, Express, and Custom account types bundle different responsibilities and interfaces.
What Stripe Connect Is and Why the Account Type Matters
Stripe Connect supports payments involving connected accounts. Account configuration and charge model together determine onboarding, Dashboard access, controls, and platform responsibilities.
This article compares legacy account-type bundles. For a new integration, review Stripe’s current Accounts v2 and controller-property configuration. The diagram below simplifies those bundles; responsibilities and controls depend on the integration.
Stripe Connect Standard vs Express vs Custom: A Direct Comparison
Standard Accounts
Who owns the Stripe relationship: The connected user.
Standard is the lightest lift for you as a platform. Users onboard directly with Stripe using their own credentials, manage their own dashboard, and handle their own disputes and compliance. You get an OAuth-style flow that connects their existing Stripe account to your platform.
Best for: Platforms where your users are businesses or professionals who likely already have Stripe accounts. SaaS tools that integrate with other businesses' payment flows. Cases where you have no need to control payout timing or branding.
Tradeoffs:
- Minimal integration effort — no custom onboarding UI required
- You have very limited visibility into the connected account's transactions
- Users can disconnect from your platform at any time
- Payment customization and payout controls depend on the integration; Standard accounts can support payout timing through Platform controls
Express Accounts
Who owns the Stripe relationship: Shared — Stripe manages compliance and identity verification, you control the experience.
Express gives you a Stripe-hosted onboarding flow that you embed or redirect into. Stripe handles KYC, identity verification, and legal agreements. You control payout scheduling and can apply some branding. The connected user gets a limited Stripe-hosted dashboard.
Best for: Gig economy platforms, delivery networks, and service marketplaces with high seller volume. Any platform where you want consistent onboarding without building and maintaining it yourself. Situations where you need payout control but not full UX ownership.
Tradeoffs:
- Faster to ship than Custom — Stripe handles compliance UI
- Stripe charges a per-account fee on top of processing fees
- You cannot fully white-label the experience
- Users see Stripe branding during onboarding
Custom Accounts
User experience: The platform controls the interface; Custom accounts do not include a Stripe Dashboard for the connected user.
Custom accounts give you complete control over the onboarding flow, the user experience, and the payment surface. You collect identity and banking information through your own UI and pass it to Stripe via the API. The connected user never sees Stripe unless you choose to show it.
Best for: Large platforms that need a fully branded experience. Platforms in verticals where the Stripe-hosted flow does not meet regulatory or product requirements. Teams with the engineering capacity to own compliance UI and edge cases.
Tradeoffs:
- Highest integration effort — you own every screen of onboarding
- You are responsible for collecting and passing compliant identity data
- Stripe's liability for connected account compliance shifts significantly toward you
- Requires ongoing maintenance as Stripe's requirements change
Charge Models Work Independently of Account Type
Check supported charge models for the selected account configuration and geography:
- Direct charges — customer pays the connected account directly; your platform takes an application fee
- Destination charges — customer pays your platform account; you transfer funds to the connected account
- Separate charges and transfers — you collect payment and transfer independently, useful for splitting across multiple recipients
Charge type changes where payments and disputes are recorded and which balance is debited. Verify that responsibility before choosing a model.
How to Choose
Compare onboarding effort, Dashboard access, required controls, and operational responsibilities. Test the current configuration options before selecting a legacy account type.
Compare Standard with the other options when connected businesses want their own Stripe Dashboard and account relationship. Confirm the required payout and dispute controls for the charge model.