Updates error codes for the Outbound Setup Intents APIBreaking changes

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

Upgrade