Skip to content
Create account
or
Sign in
The Stripe Docs logo
/
Ask AI
Create account
Sign in
Get started
Payments
Revenue
Platforms and marketplaces
Money management
Developer resources
Overview
Versioning
Changelog
    Overview
    Clover
    Basil
    Acacia
    Previous versions
Upgrade your API version
Upgrade your SDK version
Essentials
SDKs
API
Testing
Stripe CLI
Sample projects
Tools
Stripe Dashboard
Workbench
Developers Dashboard
Stripe Shell
Stripe for Visual Studio Code
Features
Workflows
Event destinations
Stripe health alertsFile uploads
AI solutions
Agent toolkit
Model Context ProtocolBuild agentic AI SaaS Billing workflows
Security and privacy
Security
Stripebot web crawler
Privacy
Extend Stripe
Build Stripe apps
Use apps from Stripe
Partners
Partner ecosystem
Partner certification
HomeDeveloper resourcesChangelogClover2025-09-30.clover

Adds a new error code for business type validationsBreaking 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.

// Correct approach for new accounts curl -X POST https://api.stripe.com/v1/accounts \ -u sk_test_123: \ -d "country=NL" \ -d "type=custom" \ -d "business_type=company" \ -d "company[structure]=sole_proprietorship"

If you encounter the error on existing accounts, update the accounts to resolve the error.

// Update existing accounts curl -X POST https://api.stripe.com/v1/accounts/acct_123 \ -u sk_test_123: \ -d "business_type=company" \ -d "company[structure]=sole_proprietorship" \ // Successful response { "id": "acct_123", "business_type": "company", "company": { "structure": "sole_proprietorship", ... }, "requirements": { "currently_due": [], // business_type requirement resolved "errors": [] } ... }

Changes

ValueChangeEnums
unsupported_business_typeAdded
BankAccount.future_requirements.errors[]BankAccount.requirements.errors[]Account.future_requirements.errors[]
 + 5 more
Account.requirements.errors[]Capability.future_requirements.errors[]Capability.requirements.errors[]Person.future_requirements.errors[]Person.requirements.errors[]

Upgrade

  1. View your current API version in Workbench.
  2. 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
  3. Upgrade the API version used for webhook endpoints.
  4. Test your integration against the new version.
  5. If you use Connect, test your Connect integration.
  6. In Workbench, perform the upgrade. You can roll back the version for 72 hours.

Learn more about Stripe API upgrades.

Related changes

  • Adds specific descriptions for risk requirements during legal, PEP, and sanctions review
  • Adds account balance and payout settings with the Balance Settings API
Was this page helpful?
YesNo
  • Need help? Contact Support.
  • Join our early access program.
  • Check out our changelog.
  • Questions? Contact Sales.
  • LLM? Read llms.txt.
  • Powered by Markdoc