- Breaking changes
- Public preview
Adds new error code for missing verification data from connected accounts Breaking changes Public preview
What’s new
This change adds verification_data_not_found as a new error code in the requirements.errors array for Accounts.
This indicates that we were unable to look up some data based on the information entered about a connected account.
Why is this a breaking change?
This is a breaking change because it adds a new enum value, verification_data_not_found, to the requirements error code enumeration list.
If your integration validates against a fixed set of expected error codes, you might need to update your error handling to account for this new value. Learn more about error handling best practices.
Impact
We generate this error code when Stripe couldn’t find information about a business or person using the provided data. For example, we couldn’t find a registered business given a tax ID and legal entity name. This can happen because the information isn’t available or because the provided data was incorrectly entered. Before proceeding, you need to first confirm that the data you provided is correct. If the data is correct and isn’t available in a registry, alternative verification methods are always provided.
When this error code is present, prompt your connected accounts to confirm the information they have already entered.
Changes
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-10-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 .
- In Workbench, perform the upgrade . You can roll back the version for 72 hours.
Learn more about Stripe API upgrades.