- Breaking changes
- Public preview
Adds support for disabling payout methods Breaking changes Public preview
What’s new
Adds the ability to disable a v2 Payout Method for use in outbound money movement, which labels the usage_status as disabled for payments and transfers.
Why is this a breaking change?
A payout method can now show disabled as the usage_status for payments and transfers. If your integration doesn’t handle payment methods with this value, you might experience unexpected failures.
Impact
You can now disable a v2 Payout Method to prevent using that payout method for outbound money movement. The resulting status is non-terminal, and you can re-enable the payout method by creating a new Outbound Setup Intent.
Changes
| Endpoint | Change | Resource |
|---|---|---|
| disable | Added | V2. MoneyManagement. PayoutMethod |
| Value | Change | Enums |
| disabled | Added | V2. MoneyManagement. PayoutMethod. usage_status. payments V2. MoneyManagement. PayoutMethod. usage_status. transfers V2. MoneyManagement. PayoutMethod#list. usage_status. payments + 1 more V2. MoneyManagement. PayoutMethod#list. usage_status. transfers |
| Code | Change | |
| default_payout_method_cannot_be_disabled | Added | cannot_proceed |
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-08-26. 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.