Using Connect embedded components to streamline your Connect onboarding flow

Summary

Furever, a test Connect platform for pet grooming, needs to onboard connected accounts and keep them compliant and activated while reducing friction. It first creates Custom accounts with card_payments and transfers requested, then contrasts Stripe-hosted account links with an embedded flow built from Account Sessions, loadConnectAndInitialize, and ConnectAccountOnboarding. The integration supports appearance variables for branding, disable_stripe_user_authentication when the platform owns losses and requirement collection, and onStepChange analytics for onboarding progress. A shared connectInstance can also render ConnectPayments, which provides payment listing, refunds, and dispute management without building that interface; the source also notes localization, framework support beyond React, and additional components.

Context

Connect platforms need to onboard connected accounts and keep them compliant and activated while maximizing conversion and minimizing user friction. The initial account-link approach sends users to a separate Stripe window and requires Stripe authentication, which the walkthrough seeks to replace with a more integrated experience.

Approach / What changed

Create Custom connected accounts with the required capabilities, expose Account Session and account-link API endpoints, and initialize Connect embedded components with Stripe's JavaScript packages. Render onboarding inside the platform, customize it with appearance variables, optionally disable Stripe user authentication when the platform controls losses and requirement collection, track progress with onStepChange, and add components such as ConnectPayments through the same connect instance.

Takeaways

• Account Sessions enable ConnectAccountOnboarding to render within the platform instead of sending users to a separate Stripe-hosted account-link flow.
• The disable_stripe_user_authentication feature can remove the extra Stripe login when the platform owns payments losses and requirement collection and has its own secure authentication.
• Multiple embedded components should generally reuse one connectInstance and initialize it once; ConnectPayments adds payment lists, refunds, and dispute management.

Related reading