- Breaking changes
- Public preview
Removes requested field from Accounts v2 capabilities hashes Breaking changes Public preview
What’s new
Removes the requested field from the capabilities hash, which is used in many parts of Accounts v2. For example, the capabilities.card_payments.requested field is no longer returned.
Instead, you can review the capability’s status field, which displays one of the following: active, pending, restricted, or unsupported. For example, you can review capabilities.card_payments.status to understand the status. Capabilities that haven’t been requested or were unrequested return a null value.
This is a breaking change for users on the existing public preview for Accounts v2, which became available in our GA channel as of 2025-12-15.clover.
Why is this a breaking change?
If your existing integration relies on the requested field, you must update your integration to use the status field or rely on the capability being present.
Impact
If your integration relies on the requested field in the capabilities hash in the Accounts v2 API, you must update your code to remove references to this field. Removing this field doesn’t affect any capability management functionality. This change improves the succinctness of the API response, as you can still use the status field to check the current state of each capability. You can also check the corresponding capability to see if it’s present and has a non-null value.
Changes
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: 2025-12-15. preview
- Upgrade the API version used for webhook endpoints .
- Test your integration against the new version.
- If you use Connect, test your Connect integration .
- In Workbench, perform the upgrade . You can roll back the version for 72 hours.
Learn more about Stripe API upgrades.