- Breaking changes
- Public preview
Shows errors for eventually due requirements Breaking changes Public preview
What’s new
In the Accounts, Persons, and Capabilities APIs, validation and verification errors can now appear in the requirements.errors and future_requirements.errors arrays for eventually_due requirements. The account.updated, person.updated, and capability.updated webhook events can also include these errors in their Account, Person, and Capability payloads.
Why is this a breaking change?
Previously, requirements.errors and future_requirements.errors only included errors for requirements that were currently due or overdue. If your integration assumes that eventually_due requirements don’t have corresponding errors, update your code to handle errors for those requirements.
Impact
If your integration reads requirements.errors or future_requirements.errors from Accounts, Persons, Capabilities, or related webhook events, handle errors whose requirement value is also listed in eventually_due.
Changes
| Parameters | Change | Resources or endpoints |
|---|---|---|
| requirements. errors future_requirements. errors | Changed | Account.requirements.errors[] Account.future_requirements.errors[] Capability.requirements.errors[] + 3 more Capability.future_requirements.errors[] Person.requirements.errors[] Person.future_requirements.errors[] |
| Change | Event type | |
| account. updated capability. updated person. updated | Changed | Event |
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. 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.