Stripe Connect Account Types: Choosing Between Custom, Express, and Standard

If you're building a marketplace, gig platform, or any software that pays out to third parties, Stripe Connect is probably on your shortlist. But before you write a single line of integration code, you need to choose between three account types: Custom, Express, and Standard. Each shifts the compliance burden, the user experience, and what you're allowed to control.

The wrong choice here doesn't just mean refactoring your payments code. It means re-onboarding every seller, renegotiating your liability with Stripe, and potentially rebuilding your entire dashboard UI. This post walks through what each account type actually requires from you and your connected accounts, so you can make the right call before you commit.

What Stripe Connect Account Types Actually Control

Stripe Connect account types determine three things: who owns the onboarding UI, who holds the compliance liability, and how much control you have over fund flows and seller data.

Custom accounts put you in full control. You build the entire onboarding form, collect tax IDs and bank details, and submit them to Stripe via API. You can brand every step, control field validation, and integrate identity verification however you want. In exchange, you take on more of the compliance burden. You're responsible for collecting the correct information for KYC (Know Your Customer) and for meeting local requirements in every country you operate in.

Express accounts use Stripe-hosted onboarding. When a seller signs up on your platform, you redirect them to a Stripe-branded form that collects everything Stripe needs: identity, banking, tax info. Stripe handles validation, manages re-verification when details expire, and takes on most of the compliance liability. You give up control over the UI, but you gain speed and reduce legal exposure.

Standard accounts treat each seller as a standalone Stripe user who happens to connect to your platform via OAuth. The seller creates their own full Stripe account, and you request permission to charge customers on their behalf or send them payouts. You have the least control, but also the least liability. This model is rare in modern marketplaces, since it breaks the seamless experience users expect.

Custom Accounts: What You're Signing Up For

Custom accounts are what you pick when you need full design control or you're building features Stripe's default flow doesn't support, like partial onboarding, progressive disclosure, or multi-step seller approval workflows.

What You Must Collect

Stripe publishes a list of required fields for each country. At minimum, for US accounts, you need:

• Legal business or individual name
• Date of birth (for individuals or business representatives)
• Address
• Last 4 digits of SSN or full SSN (depending on account size and state)
• Bank account details (routing and account number, or tokenized via Stripe.js)
• Phone number
• Email

For business accounts, you'll also collect business tax ID (EIN), business type (LLC, corporation, sole proprietor), and details on anyone who owns 25% or more of the company.

You send all of this via the Accounts API. Stripe validates it and may request additional documentation, like a photo ID or proof of address, which you must surface to the seller and upload via the API.

Identity Verification

You're responsible for verifying that the person or business is who they claim to be. Stripe offers an API-based identity verification product (Stripe Identity), but integrating it is your job. You can also use third-party KYC providers, as long as the output meets Stripe's requirements.

If you skip or weaken identity verification, you increase fraud risk, and Stripe may hold you liable for losses or disable your platform's ability to create new accounts.

Ongoing Compliance

Custom accounts require you to monitor for changes in requirements. If a seller crosses a revenue threshold, Stripe may require additional documentation or re-verification. You need to listen for webhooks (e.g., account.updated with requirements metadata), notify the seller, and present a way to submit the new information.

Express Accounts: The Faster, Safer Default

Express is the recommended account type for most platforms. Stripe hosts onboarding, handles compliance, and you still get enough customization to brand the flow and control when it happens.

What Happens Behind the Scenes

When you create an Express account via the API, Stripe returns an onboarding link. You redirect the seller to that link, where Stripe presents a form tailored to their country and business type. Stripe collects identity, banking, and tax information, verifies everything, and redirects the seller back to your platform when they're done (or if they exit early).

You don't collect sensitive info yourself, which means you're not storing tax IDs or raw bank account numbers. That alone shrinks your compliance surface area and simplifies any SOC 2 or PCI audit.

Customization You Keep

Express accounts let you:

• Set the color scheme and logo on the onboarding form (via dashboard settings)
• Pre-fill fields you already collected (like email or business name) by passing them when you create the account
• Control the redirect URLs for success, failure, and exit
• Request specific capabilities (like card payments, transfers, or tax reporting) upfront, so Stripe knows what to collect

You can't change field labels, remove required fields, or split onboarding into multiple steps. If your product needs that, you're back to Custom.

Liability and Updates

With Express accounts, Stripe owns the compliance relationship with the connected account. If requirements change or Stripe needs to re-verify someone, Stripe sends them an email with a new onboarding link. You still get webhooks so you know to disable payouts or flag the account in your dashboard, but you don't have to rebuild the UI or research what the new regulation requires.

Standard Accounts: When You're a Lightweight Integration

Standard accounts are the original Stripe Connect model, and they're rarely the right choice for a modern platform. Each seller must have an existing Stripe account before they connect to you. You use OAuth to request permission to create charges or make payouts on their behalf.

Where This Still Makes Sense

Standard accounts work when:

• You're adding payments to a product that isn't primarily a marketplace (like invoicing software or a fundraising tool)
• Your sellers are established businesses who already use Stripe for other revenue streams
• You want zero involvement in onboarding, compliance, or fund disputes

Standard accounts give you the least data access. You can't see the seller's full balance, full payout history, or personally identifiable information. You see only the transactions you created. That's a feature if you want minimal liability, but a dealbreaker if you're building seller dashboards, analytics, or fraud monitoring.

The Hidden Costs of Switching

Changing account types after launch is painful. If you start with Express and realize you need Custom, you can't convert existing accounts. You have to create new Custom accounts and ask each seller to re-onboard. They'll enter all their details again, re-link their bank account, and Stripe treats it as a brand new entity. If they've built up a payout history, reviews, or reputation in your platform tied to the old account ID, you'll need to migrate that data manually.

Going the other way (Custom to Express) is equally disruptive. Stripe won't automatically trust the onboarding data you collected, so sellers go through Express onboarding as if they're new.

The switching cost is high enough that you should prototype both flows, even if it takes a few extra days upfront. Build a test integration, onboard a few dummy accounts, and see how the UX feels and how your code will look in production.

How to Decide

Choose Custom if:

• You need to brand and control every step of onboarding for product differentiation
• You're building a complex approval workflow (like manual underwriting or phased access)
• You operate in a niche or regulated industry where you need to collect fields Stripe's default flow doesn't ask for
• You have legal and compliance resources to manage KYC and stay current with changing regulations

Choose Express if:

• You want to launch fast and reduce compliance overhead
• You're okay with Stripe-hosted UI and standard onboarding flows
• You're building a typical two-sided marketplace or SaaS platform with payouts
• You'd rather invest engineering time in your core product than in payments forms

Choose Standard if:

• You're not really building a platform, you're just creating charges on behalf of users who already have Stripe
• You only need lightweight access to a seller's account and they manage everything else themselves

For 90% of teams building their first marketplace or gig platform, Express is the right answer. You can always migrate to Custom later if you outgrow it, but starting with Custom before you've proven product-market fit usually means overbuilding.

What This Means for Your Build

Once you've chosen an account type, you're committing to a specific API surface. Custom accounts require you to build form handling, validation, and document upload flows. Express accounts reduce that to a redirect and a webhook listener. Standard accounts require OAuth setup and token management.

Budget time to handle edge cases. Sellers will exit onboarding halfway through, submit documents that get rejected, or try to link bank accounts that fail verification. Stripe's API tells you what went wrong via the requirements object on each account, but surfacing that clearly in your UI and giving sellers a path to fix it is your job.

Test onboarding in multiple countries if you plan to expand internationally. Required fields, verification thresholds, and payout timelines vary. Stripe's API returns different requirements per country, but you need to make sure your UI and email templates make sense everywhere you operate.

If you're evaluating Stripe Connect or building a platform that needs embedded payments, Stardelite's team has integrated marketplace and fintech payment flows across multiple industries. We can help you choose the right account type and build an onboarding flow that balances speed, compliance, and experience.

References

• Stripe Connect Account Types Documentation
• Stripe Connect Onboarding Requirements
• Stripe Identity Verification