Through Connect, your platform can interact with both standalone and managed Stripe accounts—each provides different levels of customizability for your platform’s user experience.
If you’d like to get started as quickly as possible, you should let your users create standalone accounts via the Connect OAuth flow. (Stripe will take care of the entire onboarding experience.)
A standalone Stripe account is a normal Stripe account that is controlled directly by the account holder (i.e. your platform’s user). A user with a standalone account will have a relationship with Stripe, be able to log in to the dashboard, can process charges on their own, and can disconnect their account from your platform.
You can prompt your users to create Stripe accounts, or allow anyone who has an existing Stripe account to connect to your platform.
You’re probably most interested in standalone accounts if you:
- Want to get started as quickly as possible. (Platforms that don’t manage accounts are much easier to set up and require far less custom code.)
- Have users who are already existing Stripe users.
- Prefer that Stripe handles communication for account issues directly with the user (e.g., to request identity verification).
- Have a “read only” platform, such as an analytics dashboard.
To get started with standalone accounts, read more about the onboarding flow.
Managed accounts Beta
A managed Stripe account will be almost completely invisible to the account holder and you will be responsible for all interactions with your user or collecting any information that Stripe needs. You will also have the ability to change most of the account’s settings, including the destination bank account, programmatically.
Managed users do not have access to Stripe’s dashboard (or app ecosystem), and Stripe will not contact them directly.
Managed accounts are appropriate if you:
- Want complete control over the connected user’s experience.
- Want to handle all communication with your users, rather than having your users contact Stripe directly.
- Have a setup where you are ultimately willing to be responsible for losses by the user. For example, a ride sharing service is generally responsible for chargebacks and the overall experience, and it’s usually difficult for the service to be used fraudulently. However, a shopping cart provider generally does not know their users well enough to absorb this kind of risk. Such a provider may not be able to police every use of their service, and as such may prefer that Stripe decides which users may be fraudulent.
Since creating and managing Stripe accounts is a more involved integration, we’ve dedicated an entire section of the guide to it.
Choose your account type
Figured out what type of integration you'd like to have? Read more about standalone and managed account integration steps.