Public preview
Adds new error codes for the crypto wallet payout method Public preview
What’s new
Adds three new error codes for the crypto_wallet payout method when creating OutboundSetupIntents API:
- blocked _ payout _ method _ crypto _ wallet : Returned when you can’t use the crypto wallet due to suspicious activity.
- unsupported _ payout _ method _ crypto _ wallet : Returned when Stripe is unable to support this type of crypto wallet.
- limit _ payout _ method _ crypto _ wallet : Returned when the number of crypto wallets exceeds the limit in a given workspace.
Impact
These error codes make crypto_wallet error handling consistent with other payout methods. When these conditions occur, Stripe returns an HTTP 400 error with the specific error code. In earlier API versions, these cases returned a generic HTTP 500 error.
Changes
| Codes | Change | |
|---|---|---|
| blocked_payout_method_crypto_wallet unsupported_payout_method_crypto_wallet | Added | blocked_by_stripe |
| limit_payout_method_crypto_wallet | 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: 2025-10-29. 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.