Breaking changes
Adds a new error code for business type validations Breaking changes
What’s new
Adds an unsupported_business_type error code to the requirements.errors array in the Accounts API, Capabilities API, Persons API, and Bank Accounts API.
We return the unsupported_business_type error if the business type isn’t supported in the merchant’s country.
// GET /v1/accounts/{{CONNECTED_ACCOUNT_ID}}
{
...
"requirements": {
"currently_due": ["business_type"],
"errors": [
{
"code": "unsupported_business_type",
"requirement": "business_type",
"reason": "Business type isn't supported in merchant country. 'individual' isn't a supported business type in country NL."
}
],
...
},
...
}
Why is this a breaking change?
Some Connect integrations might require an update to handle the new error codes.
Impact
If you provide a business type that isn’t supported for the merchant’s country, we return the unsupported_business_type error code. You need to update the business type to a valid value.
Create new accounts with the correct business type and company structure
When creating new accounts, make sure to provide a valid business type and company structure for the country. Doing so can prevent you from receiving any errors.
Command Line
If you encounter the error on existing accounts, update the accounts to resolve the error.
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-09-30. clover
- 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.
