Accéder directement au contenu
Créez un compte ou connecter-vous
Logo de la documentation Stripe
/
Créez un compteConnectez-vous

Remarque

Cette page n'est pas encore disponible dans cette langue. Nous faisons tout notre possible pour proposer notre documentation dans davantage de langues et nous vous fournirons la version traduite dès qu'elle sera disponible.

Adds new error codes for the crypto wallet payout methodVersion bêta publique

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

CodesModifier
blocked_payout_method_crypto_walletunsupported_payout_method_crypto_walletAjouté
blocked_by_stripe
limit_payout_method_crypto_walletAjouté
quota_exceeded

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: 2025-10-29.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.