Accéder directement au contenu
Créez un compte ou connectez-vous
Le logo de la documentation Stripe
/
Demander à l’IA
Créer un compteConnectez-vous
Commencer
Paiements
Revenus
Plateformes et places de marché
Gestion des fonds
Ressources de développement
API et trousse SDKAide
Aperçu
Contrôle de version
Journal des modifications
    Aperçu
    Clover
    Basil
    Acacia
    Versions précédentes
Mettre à niveau votre version de l'API
Mettre à niveau votre version de la trousse SDK
Essentials
Trousses SDK
API
Test
Interface de ligne de commande Stripe
Exemples de projets
Outils
Dashboard Stripe
Workbench
Dashboard des développeurs
Stripe pour Visual Studio Code
Terraform
Fonctionnalités
Processus
Destinations des événements
Alertes sur la santé de StripeTéléversements de fichier
Solutions d'IA
Boîte à outils des agents
Modèle Contexte ProtocoleCréez des flux de facturation pour les logiciels-service d'IA agentique
Sécurité et confidentialité
Sécurité
Stripebot web crawler
Confidentialité
Étendez Stripe
Créer des applications Stripe
Utiliser les applications de Stripe
Partenaires
Partner ecosystem
Certification des partenaires
États-Unis
Français (Canada)
AccueilRessources de développementChangelogClover2025-11-17.clover

Adds support for handling tokenized bank account numbers

Nouveautés

Adds ways to help you manage tokenized bank account numbers (TANs) through the API. TANs are temporary bank account credentials issued by financial institutions instead of real account numbers, and can be used for ACH payments and payouts while they’re active. When a TAN is deactivated, through expiration or revocation, subsequent transfers using the bank account fail.

Financial Connections

Adds an account_numbers property to the Financial Connections Accounts to provide information about tokenized bank account numbers. This includes details about account number expiration dates and whether an account uses a tokenized account number (TAN).

We also introduce two new events to help you stay informed about account number changes:

  • financial_connections.account.account_numbers_updated: We send this event when the account number information changes for a Financial Connections account.
  • financial_connections.account.upcoming_account_number_expiry: We send this event when a tokenized account number is approaching its expiration date.

Payments and Topups

Adds a new enum value tokenized_account_number_deactivated to the payment_method_us_bank_account_blocked.reason property. When a bank account becomes blocked, its tokenized account number (TAN) has been deactivated by the partner bank. The blocked_reason property provides specific information to help you understand why the bank account can no longer be used as a payment method.

You can listen for the payment_method.automatically_updated event to be notified when this bank account becomes blocked as a payment method.

Virements

Adds a new value tokenized_account_number_deactivated to the bank_account.status.

You can listen for the account.external_account.updated event to be notified when an external bank account’s status changes to tokenized_account_number_deactivated.

Impact

You can now identify when bank accounts connected through Financial Connections use tokenized account numbers and understand their status. This helps you proactively manage payment and payout failures that can occur when tokenized account numbers become deactivated.

If your integration processes ACH payments or payouts using Financial Connections accounts, you can use this information to prompt customers to reconnect their accounts before tokenized numbers expire, helping avoid failed transactions and associated fees.

The new events enable you to build automated workflows that notify customers or update your systems when account number information changes or when expiration is approaching.

Modifications

ValeursModifierEnums
tokenized_account_number_deactivatedAjout
ConfirmationToken.payment_method_preview.us_bank_account.status_details.blockedPaymentMethod.us_bank_account.status_details.blocked
financial_connections.account.account_numbers_updatedfinancial_connections.account.upcoming_account_number_expiryAjout
EventFinancialConnections.AccountWebhookEndpoint#update
 + 2 autre
WebhookEndpoint#createFinancialConnections.Account

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-11-17.clover
  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.

Cette page vous a-t-elle été utile?
OuiNon
  • Besoin d'aide? Contactez le service d'assistance.
  • Consultez notre journal des modifications.
  • Des questions? Contactez l'équipe commerciale.
  • GML? Lire llms.txt.
  • Optimisé par Markdoc