Single sign-on with a SAML identity provider

Learn how to set up single sign-on in the Dashboard with a SAML identity provider.

Stripe supports single sign-on (SSO), allowing you to manage your team’s access and roles through your identity provider (IdP). This means your team can access Stripe without needing separate passwords. When SSO is configured, users (team members) are automatically redirected to your IdP for authentication when they sign in to Stripe.

Your IdP verifies that the user has a valid role assignment to your Stripe accounts or organization, and generates a SAML assertion that Stripe uses to assign the proper roles in the Stripe Dashboard. When your account requires SSO, you must update team roles through your IdP for security. Changes to a team member’s roles only appear in Stripe after they sign in to the Dashboard again using the updated SAML assertion.

Set up SSO

To integrate your Stripe account with your IdP, complete three steps:

Prove ownership of the domains that your team uses to sign in to the Dashboard.
Configure your SAML identity provider to work with Stripe.
Configure Stripe to work with your SAML identity provider.

Prove domain ownership

A domain is the portion of an email address after the @ symbol (such as kavholm.com). You must configure SSO for each of your business’s email domains. To verify domain ownership:

Go to Single sign-on (SSO) in the Stripe Dashboard, and click + Add domain to view your account’s unique verification code. stripe-verification=4242424242424242424242
Add the verification code as a TXT record to your Domain Name System (DNS) provider.
Return to the Stripe Dashboard, and click Save and verify . Depending on your DNS provider, it can take 24 hours or more to verify your domain.
After successful verification, don’t delete the TXT record from your DNS provider. If you delete it, you might lose access to the Dashboard because Stripe frequently checks the DNS records of your domain.

Multiple Stripe accounts support

If you’re configuring SSO for multiple Stripe accounts, we recommend creating an organization to centrally configure SSO across all of your accounts.

Configure your SAML identity provider

Caution

Stripe supports SSO with the SAML 2.0 protocol. Any identity provider that supports SAML 2.0 should work with Stripe.

To configure your identity provider, create an application (wording might vary by identity provider) to represent the relationship between your identity provider and Stripe.

Within this application, set the following values.

Security settings: Configure your signature algorithm to RSA-the related setting, and your digest algorithm to the related setting. We enforce this for security reasons because SHA-256 is the industry-standard hashing algorithm.
SSO URL or Assertion Consumer Service URL: This value represents which URL your identity provider redirects your team back to after they authenticate. Set this to https://dashboard.stripe.com/login/saml/consume.
Audience URI or Entity ID: This value represents an ID for the Stripe Dashboard within your identity provider. Set this to https://dashboard.stripe.com/saml/metadata.
RelayState: This value represents where to redirect the team member after they authenticate. The URL must be relative (for example, /payments) and is only set in IdP-initiated login.
Name ID: This value represents the team member that’s authenticating (that is, the subject of the SAML assertion), and it must be the team member’s email address.

<saml2:NameID Format="urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress">{{ USER_EMAIL }}</saml2:NameID>

You can assign Stripe roles to your users through your identity provider using SAML attribute statements, or directly in the Stripe Dashboard. The steps below cover the identity provider approach. To use the Stripe Dashboard instead, see Assign roles in the Stripe Dashboard.

Attribute statements for team roles : You can send multiple roles in the SAML assertion as either a semicolon-separated list in a single SAML attribute or as a multi-value SAML attribute.

<saml2:AttributeStatement>
 <saml2:Attribute Name="Stripe-Role-" NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:basic">
 <saml2:AttributeValue>role_id_1; role_id_2</saml2:AttributeValue>
 </saml2:Attribute>
</saml2:AttributeStatement>

<saml2:AttributeStatement>
 <saml2:Attribute Name="Stripe-Role-" NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:basic">
 <saml2:AttributeValue>role_id_1</saml2:AttributeValue>
 <saml2:AttributeValue>role_id_2</saml2:AttributeValue>
 </saml2:Attribute>
</saml2:AttributeStatement>

The Name attribute of the saml2:Attribute element identifies which Stripe account to authenticate your team member to.

The value of role_id represents the Dashboard role of the team member. The team member’s role per account must be included as an attribute statement in any assertion that you send to Stripe.

Include a saml2:Attribute element per Stripe account to authenticate a team member for multiple Stripe accounts.

Stripe supports the following roles. Some of these roles are only available if your account uses the applicable Stripe product. For more information, see User roles supported by Stripe.

Role	Value
Administrator	`admin`
Analyst	`analyst`
Cardholder	`cardholder`
Connect Onboarding Analyst	`connect_onboarding_analyst`
Connect Risk Analyst	`connect_risk_analyst`
Data Migration Specialist	`data_migration_specialist`
Developer	`developer`
Dispute Analyst	`dispute_analyst`
Financial Connections Specialist	`financial_connections_specialist`
IAM Admin	`iam_admin`
Identity Analyst	`identity_analyst`
Identity View only	`identity_view_only`
Issuing Support Agent	`issuing_support_agent`
Opal View only	`opal_view_only`
Refund Analyst	`refund_analyst`
Sandbox Administrator	`sandbox_admin`
Sandbox User	`sandbox_user`
Super Administrator	`super_admin`
Support Associate	`support_associate`
Support Communications	`support_communications`
Support Specialist	`support_specialist`
Tax Analyst	`tax_analyst`
Terminal Specialist	`terminal_specialist`
Top-up Specialist	`topup_specialist`
Transfer Analyst	`transfer_analyst`
View only	`view_only`

To support multiple Stripe accounts, add a saml2:Attribute element per account.

<saml2:AttributeStatement>
 <saml2:Attribute Name="Stripe-Role-account-token-1" NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:basic">
 <saml2:AttributeValue>view_only
 </saml2:AttributeValue>
 </saml2:Attribute>
 <saml2:Attribute Name="Stripe-Role-account-token-2" NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:basic">
 <saml2:AttributeValue>view_only
 </saml2:AttributeValue>
 </saml2:Attribute>
</saml2:AttributeStatement>

You can find the list of account tokens in the Accounts section of your Personal details settings.

Assign roles in the Stripe Dashboard

You can manage Dashboard roles directly in Stripe instead of through your identity provider. Existing role assignments carry over when you switch. No users lose access.

In the Stripe Dashboard, go to Settings > Team and security > Single sign-on (SSO) .
Click Configure role assignment .
Change the role assignment preference from Identity provider to Stripe Dashboard .

After switching, manage team roles from Settings > Team and security > Team.

If you use the related setting, you can also sync groups from your identity provider to Stripe and assign Dashboard roles to those groups. When group membership changes in your IdP, Stripe access updates automatically. See Set up group-based role assignment.

Configure Stripe

Enter values from your identity provider

Next, configure your Stripe account to connect to your identity provider from the Single sign-on (SSO) page.

To configure Stripe to connect to your identity provider, you need:

Issuer ID : An identifier of your identity provider.
Identity provider URL : The URL of your identity provider that your team members are redirected to, so they can authenticate.
Identity provider certificate : The X.509 certificate that your identity provider uses to sign assertions.

Test your configuration

Before saving your settings, a test runs to validate your SSO integration. After you click Test, a window opens in your browser that redirects to your identity provider to sign in. After you sign in, the window automatically closes and test results display on the original page.

If the test succeeds, you can save the settings and select an enforcement mode. If the test fails, modify your configuration to address the issues reported and test the integration again.

Select an enforcement mode for SSO

When using SSO, you can choose from three enforcement modes. These affect which methods of authentication your team members can use.

Mode	SSO authentication allowed	Regular authentication allowed
Off	No	Yes
Optional	Yes	Yes
Required	Yes	No

Authenticate with SSO

After you finish configuring SSO, inform your users that they can sign in with any of these methods:

Users can go to the Stripe sign-in page, enter their email, then select Sign in with SSO.

If a user has access to multiple accounts, Stripe authenticates them with the default account connected to the user. If a user only has access to SAML accounts, or doesn’t have access to any accounts, Stripe redirects them to the IdP, regardless of the contents in the password field.

To use IdP-initiated login, your IdP needs to support service provider-initiated login. Verify whether this is possible in your IdP’s documentation.

SSO URL

Use the following login URL with your domain to directly sign in to your account with SSO. This URL includes the domain and account you want to use for SSO authentication. If you change the account token at the end of the URL, it authenticates you against a different account.

Support for multiple Stripe accounts

If you’re configuring SSO for multiple Stripe accounts, first create an organization to centrally configure SSO across all of your accounts. You can change the account token at the end of the SSO URL to authenticate against another account. You can find the list of account tokens in the Accounts section of your Personal details settings.

Multiple IdP connections: If you have multiple Stripe businesses with multiple IdP settings (for example, different SAML endpoints or issuer IDs) but share the same domain, we recommend using login URLs.

Revoke team member access

You can revoke a team member’s access using either active or passive methods.

Actively revoke access with an assertion

Send Stripe an assertion from your identity provider to grant a team member access to specific Stripe accounts. This also lets you revoke a team member’s access. To revoke access for a team member, assign them a role of none for the Stripe account whose access you want to revoke. For example:

<saml2:Attribute Name="Stripe-Role-STRIPE-ACCOUNT-ID" NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:basic">
 <saml2:AttributeValue>none
 </saml2:AttributeValue>
</saml2:Attribute>

Caution

You can’t revoke access for the owner of a Stripe account.

Passively revoke access with enforcement mode

When enforcement mode is set to Required, only team members who can authenticate with your identity provider can access your Stripe account. In Required mode, you can revoke a team member’s access to a Stripe account by preventing your identity provider from authenticating them. In the Stripe Dashboard, set SSO to Required in Single sign-on (SSO).