Breaking changes

Adds risk verification details for connected accounts Breaking 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

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 .

Learn more about Stripe API upgrades.