October 25, 2026 · Muhammad Umar · More by Muhammad Umar
What Stripe's Networked Onboarding Actually Syncs
Stripe lets repeat sellers reuse verified KYC data across connected accounts, but only four fields stay synced, and eligibility has a strict API-version cutoff.
Stripe Connect's networked onboarding lets the owner of an existing connected account reuse their verified legal-entity data when a platform creates a new connected account for them, instead of resubmitting identity and business details from scratch. It's enabled by default for eligible platforms. For any marketplace or platform builder whose sellers end up running more than one connected account — multiple brands, multiple storefronts, re-onboarding after a rejection — it's worth knowing exactly what this reuses, what it doesn't, and who it quietly excludes.
What counts as a shared legal entity
A legal entity, in Stripe's model, is the core identity data of a connected account — business type and company details. During onboarding, if the authenticated account owner has an existing eligible account, Stripe offers the option to reuse its information instead of collecting it again. If multiple existing accounts already share a legal entity, onboarding only ever offers the one created first as the reuse option — a platform can't assume the newest or most complete account is what gets surfaced to the user.
What stays in sync versus what's copied once
Only four fields stay continuously synchronized across every account sharing a legal entity: business_type, country, company, and individual. Update one of these on any synchronized account, and the change propagates to all of them, with the source account's values overriding anything the platform pre-fills. A longer, separate list of fields — external_accounts, business_profile, the payments and card statement descriptors, and branding settings — is copied once, during initial onboarding, and then diverges per account from that point on. For those fields, a platform's pre-filled values override whatever the source account had.
The eligibility rules that quietly exclude API-only platforms
Networked onboarding only applies when Stripe is responsible for collecting requirements, and when the connected account is authenticated through Stripe-hosted onboarding or user-authenticated embedded onboarding. A platform built entirely on API-based onboarding — no Stripe-hosted page, no embedded component — doesn't get this behavior at all, regardless of how it handles everything else. For accounts created through the API, there's also a hard version floor: the platform must be on API version 2019-02-19 or later. Older API versions automatically create a representative at account creation, which permanently disqualifies that account from ever sharing a legal entity with another one. And if a platform prefills a new connected account's country, that account can only reuse legal entities already based in the prefilled country — narrowing the pool of accounts it can match against.
Disabling networked onboarding in the Dashboard only changes what happens for new account creation going forward; accounts that already share synchronized information keep sharing it exactly as before.