Skip to content
Create account
or
Sign in
The Stripe Docs logo
/
Ask AI
Create account
Sign in
Get started
Payments
Revenue
Platforms and marketplaces
Money management
Developer resources
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
HomeDeveloper resourcesChangelogClover2025-09-30.clover

Adds new error codes for failures when creating Payment Methods from Financial Connections Accounts

What’s new

When you create a us_bank_account Payment Method from a Financial Connections Account using the financial_connections_account parameter, the account might not yet have account or routing numbers, or Stripe might still be retrieving them. In these cases, Stripe returns one of the following error codes:

  • financial_connections_account_pending_account_numbers: If you receive this error, retry the request later.
  • financial_connections_account_unavailable_account_numbers: If you receive this error, prompt your user to link a different bank account.

Impact

Previously, this error didn’t include a specific error code and appeared as an invalid request. Use the new error code to decide whether to retry creating the PaymentMethod.

Changes

CodesChange
financial_connections_account_pending_account_numbersfinancial_connections_account_unavailable_account_numbersAdded
Invoice.last_finalization_errorPaymentIntent.last_payment_errorSetupAttempt.setup_error
 + 2 more
SetupIntent.last_setup_errorStripeError

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-09-30.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.
  • Join our early access program.
  • Check out our changelog.
  • Questions? Contact Sales.
  • LLM? Read llms.txt.
  • Powered by Markdoc