If you’re building a marketplace, course platform with affiliate payouts, or any business that splits revenue between multiple parties, you’ve probably implemented Stripe Connect. And if you’ve watched sellers or partners try to onboard, you’ve seen how often they get stuck.
The problem isn’t Stripe’s reliability—it’s that Connect has two completely different onboarding paths, and choosing the wrong one for your use case creates friction you can’t fix from your dashboard.
Custom vs. Express: the split that matters
Stripe Connect offers two main account types: Custom and Express. Custom accounts let you control the entire onboarding UI and branding, but you inherit full responsibility for collecting tax forms, verifying identity documents, and handling compliance. Express accounts hand that work to Stripe—your sellers see Stripe-branded onboarding, and Stripe manages verification.
Most solo operators and small teams pick Express because it’s faster to implement. You redirect the seller to a Stripe-hosted form, they fill it out, and Stripe emails them when something’s missing. That works—until it doesn’t.
The bottleneck shows up when a seller enters information that triggers manual review. Stripe’s automated checks flag certain patterns: mismatched business addresses, high-risk industry codes, or account details that don’t align with public records. When that happens, the seller sees a vague “under review” message, and you see nothing in your Connect dashboard except a pending status.
Express accounts route all communication through Stripe’s support system, not yours. The seller waits for an email. You wait for the seller to resolve it. If they don’t check spam or if Stripe requests a document they don’t have on hand, onboarding stalls indefinitely. You can’t intervene, because you don’t own the relationship during verification.
When Custom accounts make sense
Custom accounts flip the script. You collect every data point yourself—legal business name, tax ID, bank details, beneficial ownership—and send it to Stripe via API. Stripe still runs the same fraud and compliance checks, but all communication routes through your platform.
That means when a seller’s information gets flagged, you receive the webhook. You decide how to surface the error, what language to use, and whether to let them retry or escalate to support. You control the timeline.
The tradeoff: you’re building the entire onboarding form. That includes file upload flows for identity documents, logic to handle different entity types (sole proprietor vs. LLC vs. corporation), and state management for multi-step verification. Stripe provides client libraries and examples, but you’re writing and maintaining the UI.
For a solo operator launching a small marketplace, that’s often overkill. But if your sellers are high-value—coaches charging $2,000 per course sale, affiliates earning four-figure monthly commissions—the ability to unblock them yourself justifies the build time.
The fields that fail most often
Three data points cause the majority of Connect onboarding blocks:
Business address mismatch. If a seller registers as a business entity but enters a residential address that doesn’t match their state’s business registry, Stripe flags it. This happens constantly with sole proprietors using their home address. The fix: let sellers clarify “doing business as” vs. registered entity name before they hit submit, or prompt them to choose “individual” instead of “company” as their account type.
Bank account ownership. Stripe verifies that the bank account name matches the Connect account’s legal name. If someone registers their business as “Jane Doe Consulting LLC” but links a personal checking account under “Jane Doe,” verification fails. You can’t override this. The seller has to update their bank account or re-register the Connect account with a matching name.
Missing beneficial ownership data. For any business entity, Stripe requires details on anyone who owns 25% or more of the company. If your onboarding form doesn’t explicitly ask for this upfront, the seller submits, gets approved provisionally, then hits a block weeks later when Stripe’s compliance review catches up. Custom accounts let you enforce this field before submission; Express accounts surface it late.
What you can do today
If you’re already using Express accounts and onboarding is slow, audit your redirects. Stripe’s account_onboarding link expires after the seller completes it once. If they need to update information later, you have to generate a fresh link and send it manually. Automate that: listen for account.updated webhooks with requirements.currently_due populated, and email a new onboarding link immediately.
If you’re starting fresh or rebuilding, evaluate whether your sellers justify Custom accounts. A course platform with 12 high-ticket instructors? Build Custom. A marketplace with 300 low-margin sellers? Stick with Express and accept that 10–15% will get stuck in verification.
Either way, monitor your capabilities status in the Stripe API. Every Connect account has a transfers capability that can be active, pending, or inactive. If it’s pending for more than 48 hours, surface that in your seller dashboard with specific next steps, not just “contact support.”
Running a paid newsletter, course, or membership with complex payouts? Reply with your current setup—I’ll cover payout scheduling and transfer timing in an upcoming piece.