Single sign-on (SSO)

Single sign-on (SSO) allows your team to sign in through an identity provider (IdP) using one set of credentials to access multiple applications, such as Stripe. Enabling SSO for your team increases security and centralizes how they sign in to Stripe. Stripe supports Security Assertion Markup Language (SAML) 2.0, so your IdP can manage the creation of user accounts (team members), as well as authentication and authorization during sign-in. Any identity provider that supports SAML 2.0 works with Stripe.

Set up SSO with an identity provider

Additional resources

Supported features

Stripe supports the following SSO features:

• SSO configuration options: Configure Stripe accounts to either mandate SSO for all users or allow sign-in using SSO or email and password.
• Just-in-time account creation: Automatically create new Stripe accounts for users without existing access upon their first SSO sign-in.
• Granular Dashboard roles: Assign granular user roles through your IdP or directly in the Stripe Dashboard.
• IdP-initiated SSO: Authenticate directly from an IdP’s website or browser extension.
• Service provider-initiated SSO: Initiate SSO sign-in directly from the Stripe sign-in page.
• System for Cross-domain Identity Management (SCIM): SCIM is a protocol that an IdP can use to synchronize user identity lifecycle processes (for example, provisioning and deprovisioning access, and populating user details) with the service provider, such as Stripe.

Limitations

Stripe doesn’t support the following SSO features:

• User deletion in SAML: When users aren’t managed through SCIM, Stripe doesn’t receive immediate notifications if user access is revoked in the IdP. If users attempt to sign in through SSO after their session expires, Stripe revokes their access. To remove access immediately, you can delete users from your Team settings or enable SCIM user provisioning.