# Adds specific descriptions for risk requirements during legal, PEP, and sanctions review ## What’s new Adds two new requirements, resolution paths, and a new error code for [risk requirements](https://docs.stripe.com/connect/handling-api-verification.md#handle-risk-verifications) related to legal holds, PEP reviews, and sanctions reviews. These were previously categorized as `other_supportability_inquiry` or `other_compliance_inquiry` requirements. [Risk verification requirements](https://docs.stripe.com/connect/handling-api-verification.md#handle-risk-verifications) follow the `..` format. This update adds the: - `external_hold` error code to the `requirements.errors` array in the [Accounts API](https://docs.stripe.com/api/accounts/object.md?api-version=2025-09-30.clover#account_object-requirements-errors). - `notice` resolution path to [risk verification requirements](https://docs.stripe.com/connect/handling-api-verification.md#handle-risk-verifications). This update also adds the following new descriptions to [risk verification requirements](https://docs.stripe.com/connect/handling-api-verification.md#handle-risk-verifications): - `legal_hold`: We must hold funds for legal reasons. Fulfilling the requirement can involve remitting funds to a third party. - `pep_review`: We need to verify that the business isn’t involved with a person of interest or a politically exposed person. - `sanctions_review`: We need to verify that the business isn’t involved with a sanctioned person or jurisdiction. Requirements with a description of `sanctions_review` or `pep_review` show up in `pending_verification` to indicate that the requirement is pending review by Stripe and doesn’t require any user action to resolve. ## Why is this a breaking change? This change will break existing integrations that aren’t updated to explicitly handle these new requirements. Sanctions, PEP review, and legal hold requirements were previously represented by the less-specific `other_supportability_inquiry` requirement description. | Requirement | Previous API requirement | New API requirement | | -------------------------------------------------------------------------------------------- | ---------------------------------------------------- | ---------------------------------------- | | Account under sanctions review | `interv_abc123.other_supportability_request.support` | `interv_abc123.sanctions_review.support` | | Account under PEP review | `interv_abc123.other_supportability_request.support` | `interv_abc123.pep_review.support` | | Account has a legal hold with additional information in the associated `external_hold` error | `interv_abc123.other_supportability_request.support` | `interv_abc123.legal_hold.notice` | | Account has a legal hold without additional information | `interv_abc123.other_supportability_request.support` | `interv_abc123.legal_hold.support` | The following example shows a truncated response from the v1/accounts API for an account with payouts disabled due to a legal hold ```json { "id": "acct_123", // ... "requirements": { "alternatives": [], "current_deadline": null, "currently_due": [ "interv_def789.legal_hold.notice" ], "disabled_reason": "requirements.past_due", "errors": [{ "requirement": "interv_def456.legal_hold.notice", "code": "external_request", "reason": "There is an active levy on this account. Ask the account to have the government agency, Llama Revenue Services, send a signed release to llg-notices@stripe.com." }], "eventually_due": [ "interv_def789.legal_hold.notice" ], "past_due": [ "interv_def789.legal_hold.notice" ], "pending_verification": [] }, "payouts_enabled": false, // ... } ``` This example shows a truncated response from the [Accounts v1](https://docs.stripe.com/api/accounts.md?api-version=2025-09-30) API for an account that has payouts disabled due to both a pending sanctions and a pending PEP review ```json { "id": "acct_456", // ... "requirements": { "alternatives": [], "current_deadline": null, "currently_due": [], "disabled_reason": "requirements.pending_verification", "errors": [], "eventually_due": [], "past_due": [], "pending_verification": [ "interv_def123.sanctions_review.support", "interv_def456.pep_review.support", ] }, "payouts_enabled": false, // ... } ``` ## Impact You will gain a better understanding of capability limitations caused by sanctions reviews, PEP reviews, and legal holds and whether any action is required from you to resolve the requirement. ## Changes #### REST API #### Ruby This change does not affect the Ruby SDK. #### Python #### PHP #### Java This change does not affect the Java SDK. #### Node.js #### Go #### .NET This change does not affect the .NET SDK. ## Upgrade #### REST API 1. [View your current API version](https://docs.stripe.com/upgrades.md#view-your-api-version-and-the-latest-available-upgrade-in-workbench) in Workbench. 1. 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](https://docs.stripe.com/api/versioning.md) to include `Stripe-Version: 2025-09-30.clover` 1. Upgrade the API version used for [webhook endpoints](https://docs.stripe.com/webhooks/versioning.md). 1. [Test your integration](https://docs.stripe.com/testing.md) against the new version. 1. If you use Connect, [test your Connect integration](https://docs.stripe.com/connect/testing.md). 1. In Workbench, [perform the upgrade](https://docs.stripe.com/upgrades.md#perform-the-upgrade). You can [roll back the version](https://docs.stripe.com/upgrades.md#roll-back-your-api-version) for 72 hours. Learn more about [Stripe API upgrades](https://docs.stripe.com/upgrades.md). #### Ruby 1. [View your current API version](https://docs.stripe.com/upgrades.md#view-your-api-version-and-the-latest-available-upgrade-in-workbench) in Workbench. 1. Upgrade your Ruby SDK to [v16.0.0](https://github.com/stripe/stripe-ruby/releases/tag/v16.0.0) 1. Upgrade the API version used for [webhook endpoints](https://docs.stripe.com/webhooks/versioning.md). 1. [Test your integration](https://docs.stripe.com/testing.md) against the new version. 1. If you use Connect, [test your Connect integration](https://docs.stripe.com/connect/testing.md). 1. In Workbench, [perform the upgrade](https://docs.stripe.com/upgrades.md#perform-the-upgrade). You can [roll back the version](https://docs.stripe.com/upgrades.md#roll-back-your-api-version) for 72 hours. Learn more about [Stripe API upgrades](https://docs.stripe.com/upgrades.md). #### Python 1. [View your current API version](https://docs.stripe.com/upgrades.md#view-your-api-version-and-the-latest-available-upgrade-in-workbench) in Workbench. 1. Upgrade your Python SDK to [v13.0.1](https://github.com/stripe/stripe-python/releases/tag/v13.0.1) 1. Upgrade the API version used for [webhook endpoints](https://docs.stripe.com/webhooks/versioning.md). 1. [Test your integration](https://docs.stripe.com/testing.md) against the new version. 1. If you use Connect, [test your Connect integration](https://docs.stripe.com/connect/testing.md). 1. In Workbench, [perform the upgrade](https://docs.stripe.com/upgrades.md#perform-the-upgrade). You can [roll back the version](https://docs.stripe.com/upgrades.md#roll-back-your-api-version) for 72 hours. Learn more about [Stripe API upgrades](https://docs.stripe.com/upgrades.md). #### PHP 1. [View your current API version](https://docs.stripe.com/upgrades.md#view-your-api-version-and-the-latest-available-upgrade-in-workbench) in Workbench. 1. Upgrade your PHP SDK to [v18.0.0](https://github.com/stripe/stripe-php/releases/tag/v18.0.0) 1. Upgrade the API version used for [webhook endpoints](https://docs.stripe.com/webhooks/versioning.md). 1. [Test your integration](https://docs.stripe.com/testing.md) against the new version. 1. If you use Connect, [test your Connect integration](https://docs.stripe.com/connect/testing.md). 1. In Workbench, [perform the upgrade](https://docs.stripe.com/upgrades.md#perform-the-upgrade). You can [roll back the version](https://docs.stripe.com/upgrades.md#roll-back-your-api-version) for 72 hours. Learn more about [Stripe API upgrades](https://docs.stripe.com/upgrades.md). #### Java 1. [View your current API version](https://docs.stripe.com/upgrades.md#view-your-api-version-and-the-latest-available-upgrade-in-workbench) in Workbench. 1. Upgrade your Java SDK to [v30.0.0](https://github.com/stripe/stripe-java/releases/tag/v30.0.0) 1. Upgrade the API version used for [webhook endpoints](https://docs.stripe.com/webhooks/versioning.md). 1. [Test your integration](https://docs.stripe.com/testing.md) against the new version. 1. If you use Connect, [test your Connect integration](https://docs.stripe.com/connect/testing.md). 1. In Workbench, [perform the upgrade](https://docs.stripe.com/upgrades.md#perform-the-upgrade). You can [roll back the version](https://docs.stripe.com/upgrades.md#roll-back-your-api-version) for 72 hours. Learn more about [Stripe API upgrades](https://docs.stripe.com/upgrades.md). #### Node.js 1. [View your current API version](https://docs.stripe.com/upgrades.md#view-your-api-version-and-the-latest-available-upgrade-in-workbench) in Workbench. 1. Upgrade your Node SDK to [v19.1.0](https://github.com/stripe/stripe-node/releases/tag/v19.1.0) 1. Upgrade the API version used for [webhook endpoints](https://docs.stripe.com/webhooks/versioning.md). 1. [Test your integration](https://docs.stripe.com/testing.md) against the new version. 1. If you use Connect, [test your Connect integration](https://docs.stripe.com/connect/testing.md). 1. In Workbench, [perform the upgrade](https://docs.stripe.com/upgrades.md#perform-the-upgrade). You can [roll back the version](https://docs.stripe.com/upgrades.md#roll-back-your-api-version) for 72 hours. Learn more about [Stripe API upgrades](https://docs.stripe.com/upgrades.md). #### Go 1. [View your current API version](https://docs.stripe.com/upgrades.md#view-your-api-version-and-the-latest-available-upgrade-in-workbench) in Workbench. 1. Upgrade your Go SDK to [v83.0.0](https://github.com/stripe/stripe-go/releases/tag/v83.0.0) 1. Upgrade the API version used for [webhook endpoints](https://docs.stripe.com/webhooks/versioning.md). 1. [Test your integration](https://docs.stripe.com/testing.md) against the new version. 1. If you use Connect, [test your Connect integration](https://docs.stripe.com/connect/testing.md). 1. In Workbench, [perform the upgrade](https://docs.stripe.com/upgrades.md#perform-the-upgrade). You can [roll back the version](https://docs.stripe.com/upgrades.md#roll-back-your-api-version) for 72 hours. Learn more about [Stripe API upgrades](https://docs.stripe.com/upgrades.md). #### .NET 1. [View your current API version](https://docs.stripe.com/upgrades.md#view-your-api-version-and-the-latest-available-upgrade-in-workbench) in Workbench. 1. Upgrade your .NET SDK to [v49.0.0](https://github.com/stripe/stripe-dotnet/releases/tag/v49.0.0) 1. Upgrade the API version used for [webhook endpoints](https://docs.stripe.com/webhooks/versioning.md). 1. [Test your integration](https://docs.stripe.com/testing.md) against the new version. 1. If you use Connect, [test your Connect integration](https://docs.stripe.com/connect/testing.md). 1. In Workbench, [perform the upgrade](https://docs.stripe.com/upgrades.md#perform-the-upgrade). You can [roll back the version](https://docs.stripe.com/upgrades.md#roll-back-your-api-version) for 72 hours. Learn more about [Stripe API upgrades](https://docs.stripe.com/upgrades.md). ## Related changes - [Adds a new error code for business type validations](https://docs.stripe.com/changelog/clover/2025-09-30/business-type-error-code.md) - [Adds account balance and payout settings with the Balance Settings API](https://docs.stripe.com/changelog/clover/2025-09-30/balance-settings-ga.md)