Skip to content
Create account
 or
Sign in
The Stripe Docs logo
/
Create account
Sign in

Adds indicator for connected accounts that must log in before using embedded components

What’s new

The value of disable_stripe_user_authentication is now always present in the Account Sessions API response for components that support this feature.

This feature defaults to false for all accounts, and can be true for accounts where you’re responsible for collecting updated information when requirements are due or change, like Custom accounts.

Impact

Connect platforms can pass in disable_stripe_user_authentication to the Account Sessions API to allow connected accounts to use certain embedded components without authenticating through Stripe.

Now, the value of disable_stripe_user_authentication is always returned in the response from the Account Sessions API for these embedded components.

Changes

FieldsChangeFrom → to
AccountSession.components.account_management.features.disable_stripe_user_authenticationAccountSession.components.account_onboarding.features.disable_stripe_user_authenticationAccountSession.components.balances.features.disable_stripe_user_authenticationAccountSession.components.notification_banner.features.disable_stripe_user_authenticationAccountSession.components.payouts.features.disable_stripe_user_authenticationChanged
optional → required

Upgrade

  1. View your current API version in Workbench.
  2. If you use an SDK, upgrade to the corresponding SDK version for this API version.
    • If you don’t use an SDK, update your API requests to include Stripe-Version: 2024-11-20.acacia
  3. Upgrade the API version used for webhook endpoints.
  4. Test your integration against the new version.
  5. If you use Connect, test your Connect integration.
  6. In Workbench, perform the upgrade. You can roll back the version for 72 hours.

Learn more about Stripe API upgrades.

Was this page helpful?
YesNo