- Breaking changes
- Public preview
Updates error codes for the Outbound Setup Intents API Breaking changes Public preview
What’s new
Updates the error codes returned by the Outbound Setup Intents API to use more generic error types instead of credential-type-specific codes. This change replaces several existing error codes with standardized error types:
- blocked _ payout _ method _ bank _ account , blocked _ payout _ method _ card , and blocked _ payout _ method _ crypto _ wallet errors now return blocked _ payout _ method .
- unsupported _ payout _ method _ bank _ account and unsupported _ payout _ method _ card errors now return unsupported _ payout _ method .
- invalid _ payout _ method _ bank _ account , invalid _ payout _ method _ card , and invalid _ payout _ method _ crypto _ wallet errors now return invalid _ payout _ method .
- limit _ payout _ method _ bank _ account , limit _ payout _ method _ card , and limit _ payout _ method _ crypto _ wallet errors now return limit _ payout _ method .
This standardization improves the consistency of error handling across different Payout Method types and supports future extensibility when adding new credential types to Payout Methods.
Why is this a breaking change?
This is a breaking change because your integration can rely on the specific error code identifiers that this update replaces. If your code checks for type specific error codes like blocked_payout_method_bank_account, unsupported_payout_method_bank_account, invalid_payout_method_bank_account_, or limit_payout_method_bank_account, those checks no longer work and you must update them to handle the generic error types.
Impact
If your integration handles specific error codes from Outbound Setup Intents endpoints, you need to update your error handling logic to use the generic error types. The error messages and underlying reasons remain the same, but the error code identifiers have changed to be more consistent across different Payout Method types.
Changes
| Codes | Change | |
|---|---|---|
| blocked_payout_method unsupported_payout_method | Added | blocked_by_stripe |
| invalid_payout_method_data | Added | invalid_payout_method |
| limit_payout_method | Added | quota_exceeded |
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-01-28. 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.