- Breaking changes
- Public preview
Restricts Accounts v2 identity properties for some Global Payouts use cases Breaking changes Public preview
What’s new
Removes access for Global Payouts users to certain identity properties on Accounts that have no configurations or where defaults.responsibilities.requirements_collector is stripe.
Why is this a breaking change?
Certain properties in an Account’s identity hash are no longer accessible to Global Payouts users when those properties aren’t relevant. Attempting to read or write those properties will fail.
Impact
Access to properties of the Account object’s identity hash is now limited for Global Payouts users the same way as it is for other integrations. If your Global Payouts integration reads or writes any identity properties, you might need to update your code to stop attempting to access properties that are no longer available. Review the following changes:
- You can no longer set identity.attestations.terms_of_service on an Account that only requests Global Payouts capabilities. Those Accounts don’t sign the Stripe Terms of Service, so that attestation property doesn’t apply.
- On an Account with no requested capabilities, you can no longer access certain identity properties.
- On an Account where defaults.responsibilities.requirements_collector is stripe , you can no longer access certain identity properties.
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-03-25. preview
- 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 Stripe API upgrades.