Skip to content
Create account
or
Sign in
The Stripe Docs logo
/
Ask AI
Create account
Sign in
Get started
Payments
Finance automation
Platforms and marketplaces
Money management
Developer tools
Get started
Payments
Finance automation
Get started
Payments
Finance automation
Platforms and marketplaces
Money management
OverviewExplore all products
Start building
Start developing
Sample projects
About the APIs
Build with LLMs
Use Stripe without code
Set up Stripe
Create an account
    Overview
    Activate your account
    Add funds to your balance
    Account checklist
    Acceptable verification documents
    Account structure
    Start a team
    Organizations
    Multiple separate accounts
    Linked external accounts
    Settings
    Branding
    Statement descriptors
    Custom email domain
    Custom domain
    Single sign-on
      Setup SSO
        Auth0
        Entra ID
        Google Workspace
        Okta
        OneLogin
        Other
      Consolidate SSO
      Troubleshoot SSO
    Stripe Verified
Web Dashboard
Mobile Dashboard
Migrate to Stripe
Manage fraud risk
Understand fraud
Radar fraud protection
Manage disputes
Verify identities
HomeGet startedCreate an accountSingle sign-onSetup SSO

Single sign-on with Entra IDPublic preview

Learn how to setup single sign-on in the Dashboard with Entra ID.

Copy page

Use Microsoft Entra ID (formerly known as Azure Active Directory) to verify domain ownership, create user role groups, configure single sign-on (SSO), and assign roles to manage access to your Stripe account.

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 if they have a valid role assignment to your Stripe accounts or organization, and generates a SAML assertion used by Stripe to assign the proper roles in the Stripe Dashboard. When your account requires SSO, you must update team roles through your Identity Provider (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.

Verify domain ownership

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

  1. Navigate to User authentication in the Stripe Dashboard, and click + New domain to view your account’s unique verification code.
    stripe-verification=4242424242424242424242
  2. Add the verification code as a TXT record to your Domain Name System (DNS) provider.
  3. 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.
  4. 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, you must create an organization to centrally configure SSO across all of your accounts. Alternatively, contact Stripe support to verify your domain across separate accounts with one shared verification code.

Create groups of users in Entra ID

Create groups for Stripe roles and assign your team members (users) to these groups. Users can belong to only one group per Stripe account. For example, if you want a user to have an admin role, assign them to the administrator group. However, if you want a user to have multiple roles, such as view only and analyst, create a separate group specifically for those combined roles.

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.

RoleValue
Administratoradmin
Analystanalyst
Cardholdercardholder
Connect Onboarding Analystconnect_onboarding_analyst
Connect Risk Analystconnect_risk_analyst
Data Migration Specialistdata_migration_specialist
Developerdeveloper
Dispute Analystdispute_analyst
Financial Connections Specialistfinancial_connections_specialist
IAM Adminiam_admin
Identity Analystidentity_analyst
Identity View onlyidentity_view_only
Issuing Support Agentissuing_support_agent
Opal View onlyopal_view_only
Sandbox Administratorsandbox_admin
Sandbox Usersandbox_user
Super Administratorsuper_admin
Support Associatesupport_associate
Support Communicationssupport_communications
Support onlysupport_only
Support Specialistsupport_specialist
Refund Analystrefund_analyst
Tax Analysttax_analyst
Terminal Specialistterminal_specialist
Topups onlytopups_only
Top-up Specialisttopup_specialist
Transfer Analysttransfer_analyst
View onlyview_only
  1. Log in to the Entra ID Dashboard.
  2. In the left navigation pane, click Groups.
  3. Click Add new group:
    • For Group type, select Security.
    • For Group name, enter the name of the group (for example, View only users in Stripe).
  4. Click No members added, and add users to the group.

Create an Entra ID application

Caution

In most cases, you should create only one application for Stripe in Entra ID, even if you have multiple Stripe accounts. You can assign users access to multiple accounts or your organization by adding multiple claims (one per account) to your application. If you have more than 50 accounts, see how to set up multiple applications in Entra.

To configure Entra ID, create a new application to represent the relationship between Entra ID and the Stripe Dashboard:

  1. In the left navigation pane, click Applications > Enterprise applications.
  2. Click Create your own application, enter the name your application, select Integrate any other application you don’t find in the gallery, and click Create.
  3. Under Getting Started, click 1. Assign users and groups.
  4. Click Add user/group, and select the groups you previously created.
  5. In your app’s left navigation page, click Overview > 2. Set up single sign on.
  6. Select SAML to open the SAML-based Sign on page.
  7. Click Basic SAML Configuration, enter the following values, and click Save.
    • Identifier: https://dashboard.stripe.com/saml/metadata
    • Reply URL: https://dashboard.stripe.com/login/saml/consume

Add attributes and claims

You must assign attributes and claims to the groups you created.

  1. On the SAML-based Sign on page, click Attributes and claims.
  2. Click Add new claim. You must create a new claim for each Stripe account you’re configuring SSO for.
  3. Click Claim conditions to create the mapping between the group and the role you want to the group for this Stripe account.
    1. Set the Name to Stripe-Role-{{STRIPE_ACCOUNT_ID}}. This identifies which Stripe account you authenticate your team member to (and is set to whichever Stripe account you’re signed in to while viewing this page, currently: )
    2. For Source, select Attribute.
    3. For User type, select Members.
    4. For Group, select the group you want.
    5. For Source, select Attribute.
    6. For Value, enter the Dashboard role you want to assign (for example, developer), and click Enter. This means you’ve assigned this role to any members in this group.
  4. Assign Stripe roles you want to the groups you created. If you want a user to have multiple roles (such as view only and analyst), you must create a separate group that exists specifically for those combined roles.
  5. Click Save.

Set up multiple applications

If you have more than 50 Stripe accounts and add a separate claim for each account, you will likely exceed the claim limit in Entra. To manage access to a large number of accounts in Stripe, there are two options:

  1. (Recommended) Consolidate your SSO settings into an Organization, and reduce the number of claims by using organization-level roles.
  2. Set up multiple Stripe applications (one per account). For every account, set the Identifier (Entity ID) to https://dashboard.stripe.com/saml/metadata/{STRIPE_ACCOUNT_ID}. We refer to this as an Account ID-based custom issuer.

Verify certificates

On the SAML-based Sign on page, click SAML certificates to verify if the signing algorithm configuration is correct. Ensure the following values match:

  • Signing Option: Sign SAML assertion
  • Signing Algorithm: SHA-256

Configure Stripe

To configure Stripe with SSO:

Retrieve values from Entra ID

Retrieve the values for Login URL, Microsoft Entra Identifier, and PEM SAML Certificate from your app in Entra ID.

  1. Open the Entra ID Dashboard.
  2. In your app’s left navigation pane, click Single sign-on.
  3. On the SAML-based Sign on page, navigate to Set up Stripe, and retrieve the following values for:
    • Login URL
    • Microsoft Entra Identifier
  4. On the SAML-based Sign on page, click SAML Certificates.
  5. Next to your certificate, click the overflow button (), and click PEM certificate download
  6. Open the .pem file in a basic text editor. This is your Identity provider certificate.

Configure your Stripe account to connect to Entra ID

Enter the values you retrieved from your app in Entra ID in Stripe:

  1. In the Stripe Dashboard, navigate to Settings > Team and security > User authentication.
  2. Next to the domain name, click the overflow button () > Manage SSO settings.
  3. Click Test your configuration > Next.
  4. Provide info for your identity provider:
    • For Issuer ID, enter the value for Microsoft Entra Identifier in Entra ID.
    • For Identity provider URL, enter the value for Login URL in Entra ID.
    • For Identity provider certificate, enter the certificate value from the .pem file you downloaded in Entra ID (include the begin certificate and end certificate text).
  5. Click Continue.
  6. If you set up an Account ID-based custom issuer earlier, select the By Account ID advanced settings option. Otherwise, continue with the default selected option.
  7. Click Test configuration to open a new window to test your configuration. Exit this window, and return to the original window.
  8. If you pass the test, click Done.

If the test fails, refer to Troubleshoot SSO, and address the reported issues in your Stripe app in Okta.

  1. Select SSO enforcement. You can choose between Off, Optional, or Mandatory. You can change enforcement type in the future.
  2. Click Save settings > Done.

Authenticate with SSO

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

Stripe’s sign in page

Users can navigate to the Stripe sign in page, enter their email, then select Use single sign-on (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 merchants, or doesn’t have access to any merchants, Stripe redirects them to the IdP, regardless of the contents in the password field.

IdP-initiated login

To use IdP-initiated login, your IdP needs to support Service Provider-initiated login. Verify if this is possible using 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.

https://dashboard.stripe.com/login/saml_direct/domain/{{YOUR_DOMAIN}}/merchant/{{STRIPE_ACCOUNT_ID}}

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’s 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 User authentication.

Was this page helpful?
YesNo
Need help? Contact Support.
Join our early access program.
Check out our changelog.
Questions? Contact Sales.
LLM? Read llms.txt.
Powered by Markdoc