Breaking changes
Public preview

Updates requirements collection parameters for Accounts v2 Breaking changes Public preview

What’s new

The defaults.responsibilities.requirements_collector parameter replaces the deprecated requirements.collector parameter. You use the requirements_collector parameter to specify whether Stripe or your platform is responsible for collecting requirements on connected accounts while using Accounts v2.

This change also updates the enum values for requirements.entries[].reference.type, which specify which API resource is related to a given requirement.

Why is this a breaking change?

This is a breaking change because:

The requirements _ collector parameter replaces the collector parameter.
Parameter enum values in requirements. entries[]. reference. type are now more specific (for example, payment _ method and person ). This could cause validation errors if your integration expects the previous generic value of resource .

Impact

The updated parameter enum values for requirements.entries[].reference.type might require changes to how you handle specific requirements in your verification flows.

If your integration relies on the collector parameter or the resource enum value, you need to update your code before upgrading to this API version to avoid integration failures.

Changes

Parameter	Change	Resources or endpoints
requirements_collector	Added	V2. Core. Account. defaults. responsibilities V2. Core. Account. requirements V2. Core. Account. requirements. entries[]. reference + 1 more V2. Core. Account. requirements. entries[]. reference

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.