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
| Parameter | Change | Resources or endpoints |
|---|---|---|
| transaction_purpose | Added | PaymentIntent#confirm. payment_method_options. us_bank_account PaymentIntent#create. payment_method_options. us_bank_account PaymentIntent#update. payment_method_options. us_bank_account + 1 more PaymentIntent. payment_method_options. us_bank_account |
Upgrade
- View your current API version in Workbench.
- 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
- Upgrade the API version used for webhook endpoints .
- Test your integration against the new version.
- If you use Connect, test your Connect integration .
Learn more about Stripe API upgrades.