Adds support for disabling Stripe user authentication for certain embedded components

What’s new

Adds support for disable_stripe_user_authentication on several AccountSession components.

Impact

Previously, when using the Account Sessions API with external_account_collection set to true for an embedded component, the account would be required to authenticate through Stripe before using the component. Now, for accounts where you’re responsible for collecting requirements (such as Custom accounts), you can disable Stripe user authentication by setting the disable_stripe_user_authentication feature to true.

Changes

Parameter	Change	Resources or endpoints
disable_stripe_user_authentication	Added	AccountSession#create.components.account_management.features AccountSession#create.components.account_onboarding.features AccountSession#create.components.balances.features + 7 more AccountSession#create.components.notification_banner.features AccountSession#create.components.payouts.features AccountSession.components.account_management.features AccountSession.components.account_onboarding.features AccountSession.components.balances.features AccountSession.components.notification_banner.features AccountSession.components.payouts.features

Upgrade

View your current API version in Workbench.
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-10-28.acacia
Upgrade the API version used for webhook endpoints.
Test your integration against the new version.
If you use Connect, test your Connect integration.
In Workbench, perform the upgrade. You can roll back the version for 72 hours.

Learn more about more about Stripe API upgrades.