• Breaking changes
• Public preview

Adds a failure reason for received debits when the debit capability is inactive Breaking changes Public preview

What’s new

Adds capability_inactive as a new enum value for the status_details.failed.reason of the ReceivedDebit object. When a received debit fails because the associated capability is inactive, status_details.failed.reason now returns capability_inactive explicitly, instead of a generic failure reason.

Why is this a breaking change?

Previously, if a received debit failed because the associated capability was inactive, no explicit capability_inactive enum value existed on status_details.failed.reason. If your integration switches on or otherwise evaluates status_details.failed.reason for a ReceivedDebit, update your code to handle capability_inactive.

Impact

You can now identify received debit failures caused by an inactive capability through the new capability_inactive value in status_details.failed.reason.

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: 2026-06-24. preview

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.

Related changes

• Replaces the related setting code with BIC in Financial Addresses
• Replaces the status filter with statuses on the List Financial Accounts endpoint
• Adds the originating account holder name to Received Credit bank transfers