Adds explicit session configuration options for Financial Connections
What’s new
You can now use explicit, composable configuration parameters to control which accounts are collected and how the Financial Connections authentication flow behaves. Previously, account holder type implicitly determined session behaviour.
The following parameters are now available:
- filters.require_payment_method_support : Restricts account selection to payment-eligible accounts. Set to all to make every linked account payment-eligible, at _ least _ one to make at least one a payment account while allowing others, or none for no restriction.
- limits.accounts : Sets the maximum number of accounts a user can link in a session.
- manual_entry.mode : Controls whether the manual bank account entry fallback is shown during authentication. Set to automatic for Stripe to manage it, or disabled to remove the option entirely.
This change also adds a new property on the returned Session object:
- bank_account_token : Returned when a user completes manual entry.
Impact
Previously, Financial Connections session behaviour was implicitly tied to account holder type, rather than the user’s actual use case. Advanced session configurability replaces this with explicit, composable API parameters, making it easier for platforms to build the exact experience they need without workarounds.
You can also subscribe to financial_connections.account.supported_payment_method_types_updated to be notified when an account’s payment eligibility is confirmed after account number retrieval.
Changes
| Parameters | Change | Resources or endpoints |
|---|---|---|
| limits manual_entry | Added | FinancialConnections. Session FinancialConnections. Session#create |
| require_payment_method_support | Added | FinancialConnections. Session#create. filters FinancialConnections. Session. filters |
| bank_account_token | Added | FinancialConnections. Session |
| Value | Change | Enums |
| financial_connections. account. supported_payment_method_types_updated | Added | Event. type WebhookEndpoint#update. enabled_events WebhookEndpoint#create. enabled_events |
| Change | Event type | |
| financial_connections. account. supported_payment_method_types_updated | Added | FinancialConnections.Account |
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: 2026-07-29. dahlia
- Upgrade the API version used for webhook endpoints .
- Test your integration against the new version.
- If you use Connect, test your Connect integration .
Learn more about Stripe API upgrades.