Skip to content
Create account or Sign in
The Stripe Docs logo
/
Ask AI
Create accountSign in
Get started
Payments
Revenue
Platforms and marketplaces
Money management
Developer resources
APIs & SDKsHelp
Overview
Versioning
Changelog
    Overview
    Clover
    Basil
    Acacia
    Previous versions
Upgrade your API version
Upgrade your SDK version
Essentials
SDKs
API
Testing
Stripe CLI
Sample projects
Tools
Stripe Dashboard
Workbench
Developers Dashboard
Stripe Shell
Stripe for Visual Studio Code
Features
Workflows
Event Destinations
Stripe health alertsFile uploads
AI solutions
Agent toolkit
Model Context ProtocolBuild agentic AI SaaS Billing workflows
Security and privacy
Security
Stripebot web crawler
Privacy
Extend Stripe
Build Stripe apps
Use apps from Stripe
Partners
Partner ecosystem
Partner certification
United States
English (United Kingdom)
HomeDeveloper resourcesChangelogClover2025-11-17.clover

Adds support for handling tokenised bank account numbers

What’s new

Adds ways to help you manage tokenised 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 tokenised bank account numbers. This includes details about account number expiry dates and whether an account uses a tokenised 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 tokenised account number is approaching its expiry 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 tokenised 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.

Payouts

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 tokenised account numbers and understand their status. This helps you proactively manage payment and payout failures that can occur when tokenised 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 tokenised 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.

Changes

ValuesChangeEnums
tokenized_account_number_deactivatedAdded
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_expiryAdded
EventFinancialConnections.AccountWebhookEndpoint#update
 + 2 more
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.

Was this page helpful?
YesNo
  • Need help? Contact Support.
  • Check out our changelog.
  • Questions? Contact Sales.
  • LLM? Read llms.txt.
  • Powered by Markdoc