Breaking changes

Adds rejected status for Accounts v2 capabilitiesBreaking changes

What’s new

Adds a rejected value to the status property of account capabilities on Accounts v2. This status appears alongside the existing values active, pending, restricted, and unsupported.

The status_details property now provides specific codes that describe the reason for rejection:

rejected_fraud
rejected_incomplete_verification
rejected_listed
rejected_other
rejected_platform_fraud
rejected_platform_other
rejected_platform_terms_of_service
rejected_terms_of_service

These codes can appear in the capability status for merchant, recipient, and storer configurations.

For rejected accounts, API versions before 2026-09-30.endive return:

restricted instead of rejected for status
restricted_other instead of a specific rejected_* code in status_details

Why is this a breaking change?

Previously, rejected accounts provided a status of restricted with a status_details code of requirements_past_due.

When an account rejected, we now return more specific error codes that describe the rejection reason. If your integration uses the restricted status to identify rejected accounts, you must update your code to handle the rejected status and the associated detail codes.

Impact

If your integration reads capability status or status_details values from Accounts v2 Account objects, you can now understand and handle the specific reasons a capability configuration was rejected.

These events also now include the rejected status for rejected accounts:

Changes

Values	Change	Enums
rejected	Added	V2.Core.Account.configuration.customer.capabilities.automatic_indirect_tax.status V2.Core.Account.configuration.merchant.capabilities.ach_debit_payments.status V2.Core.Account.configuration.merchant.capabilities.acss_debit_payments.status + 46 more
rejected_fraudrejected_incomplete_verificationrejected_listedrejected_otherrejected_platform_fraudrejected_platform_otherrejected_platform_terms_of_servicerejected_terms_of_service	Added	V2.Core.Account.configuration.customer.capabilities.automatic_indirect_tax.status_details[].code V2.Core.Account.configuration.merchant.capabilities.ach_debit_payments.status_details[].code V2.Core.Account.configuration.merchant.capabilities.acss_debit_payments.status_details[].code + 46 more

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: 2026-09-30.endive
Upgrade the API version used for webhook endpoints.
Test your integration against the new version.
If you use Connect, test your Connect integration.

Learn more about Stripe API upgrades.