Skip to content
Create account
or
Sign in
The Stripe Docs logo
/
Ask AI
Create account
Sign in
Get started
Payments
Finance automation
Platforms and marketplaces
Money management
Developer tools
Get started
Payments
Finance automation
Get started
Payments
Finance automation
Platforms and marketplaces
Money management
Overview
Versioning
Changelog
    Overview
    Basil
    Acacia
    Previous versions
Upgrade your API version
Upgrade your SDK version
Developer tools
SDKs
API
Testing
Workbench
Event Destinations
Workflows
Stripe CLI
Stripe Shell
Developers Dashboard
Agent toolkit
Stripe health alertsBuild with LLMsStripe for Visual Studio CodeFile uploads
Security
Security
Extend Stripe
Stripe Apps
Stripe Connectors
Partners
Partner ecosystem
Partner certification
HomeDeveloper toolsChangelogAcacia2024-09-30.acacia

Adds risk verification details for connected accountsBreaking changes

What’s new

Upgrading to this version helps you better understand the causes of supportability verification issues for your connected accounts. You can see the verification error in the requirements.errors.code enum.

The new error includes text that describes the requirement for the following risk requirements:

  • supportability_rejection_appeal
  • business_model_verification
  • restricted_or_prohibited_industry_diligence
  • other_supportability_inquiry

For example, if a verification fails because your connected account is selling alcohol, this message is shown in the reason field: “We can’t accept payments for age-restricted goods such as alcohol under the Stripe Services Agreement, as mentioned in the prohibited and restricted businesses list.”

{ "id": "{{CONNECTED_ACCOUNT_ID}}", // ... "requirements": { "disabled_reason": "other", "past_due": ["interv_abc123.restricted_or_prohibited_industry_diligence.form"], "pending_verification": [], "errors": [ { "code": "verification_supportability", "reason": "We can't accept payments for age-resticted goods such as alcohol under the Stripe Services Agreement, as mentioned in the restricted businesses list.", "requirement": "interv_abc123.restricted_or_prohibited_industry_diligence.form" } ], "alternatives": [] // ... } }

Learn more about handling risk verifications.

Why is this a breaking change?

This is a breaking change because it adds the new verification_supportability value to the requirements error code enumeration.

Impact

You can use the details to send notifications to connected accounts and guide them to a form where they can address the requirements.

Changes

ValueChangeEnums
verification_supportabilityAdded
Account.future_requirements.errors[].codeAccount.requirements.errors[].codeBankAccount.future_requirements.errors[].code
 + 1 more
BankAccount.requirements.errors[].code

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: 2024-09-30.acacia
  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.

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