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 for Visual Studio Code
Terraform
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 States)
HomeDeveloper resourcesChangelogClover2026-02-25.clover

Adds transaction purpose to PaymentIntents for US bank account payments

What’s new

Adds the transaction_purpose parameter to the payment_method_options.us_bank_account hash in the PaymentIntents API. This optional parameter allows you to specify the purpose of ACH debit transactions as goods, services, other, or unspecified. The parameter defaults to unspecified when not provided.

Impact

You can now specify a transaction purpose for US bank account payments when creating or updating PaymentIntents. While this parameter is optional, providing accurate transaction purpose information helps ensure compliance with ACH network requirements, including Nacha regulations that require certain ACH debit transactions to be explicitly identified as e-commerce purchases. You might not need to specify a transaction purpose to ensure compliance—learn more about ACH Direct Debit.

If you process ACH debit payments for goods or services, consider updating your integration to include the appropriate transaction_purpose value when creating PaymentIntents.

Changes

ParameterChangeResources or endpoints
transaction_purposeAdded
PaymentIntent#confirm.payment_method_options.us_bank_accountPaymentIntent#create.payment_method_options.us_bank_accountPaymentIntent#update.payment_method_options.us_bank_account
 + 1 more
PaymentIntent.payment_method_options.us_bank_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: 2026-02-25.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.

Related changes

  • Adds display name and service user number to Bacs Direct Debit mandates
  • Adds events for reserve holds, releases, and plans
  • Makes Boleto tax ID nullable in payment method details for Payment Records
Was this page helpful?
YesNo
  • Need help? Contact Support.
  • Check out our changelog.
  • Questions? Contact Sales.
  • LLM? Read llms.txt.
  • Powered by Markdoc