Breaking changes
Public preview

Adds future requirements field to Accounts v2 Breaking changes Public preview

What’s new

Adds future_requirements to the Accounts v2 API as a new includable property. Accounts now have two properties that specify any required information that must be collected from the company, individual, or business:

The future_requirements property specifies what information Stripe will eventually be required to collect.
The requirements property specifies what information Stripe currently is required to collect.

Why is this a breaking change?

Any requirements previously included in the requirements hash with a requested reason code of future_requirements are now included in the future_requirements hash.

Impact

You no longer need to review all individual requirements to determine whether they’re required to unblock capabilities on an account. If requirements.entries is empty, all requested capabilities are active.

Changes

Parameter	Change	Resources or endpoints
future_requirements	Added	V2. Core. Account V2. Core. Account. requirements. entries[]. requested_reasons[] V2. Core. Account#create + 2 more V2. Core. Account#retrieve V2. Core. Account#update

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: 2025-11-17. preview

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.