← Back
Stripe
Stripe adds transaction_purpose parameter to PaymentIntents for ACH compliance

New Transaction Purpose Parameter

The Stripe PaymentIntents API now includes an optional transaction_purpose parameter within the payment_method_options.us_bank_account hash. This parameter allows you to specify the purpose of ACH debit transactions with one of four values: goods, services, other, or unspecified (the default).

Compliance Benefits

While the parameter is optional, providing accurate transaction purpose information helps ensure compliance with ACH network requirements, particularly Nacha regulations that mandate certain ACH debit transactions—specifically those related to e-commerce purchases—to be explicitly identified. This addition simplifies regulatory compliance for merchants processing goods and services payments via ACH.

Implementation Across SDKs

The feature is available across all major Stripe SDKs and the REST API, including Ruby, Python, PHP, Java, Node.js, Go, and .NET. Developers should upgrade to API version 2026-02-25.clover to access this functionality.

Upgrade Path

To adopt this feature, developers should:

  • Upgrade to the latest SDK version for their language
  • Update the API version in their integration to 2026-02-25.clover
  • Test the integration thoroughly, including Connect integrations if applicable
  • Update webhook endpoints to use the new API version

The upgrade can be rolled back within 72 hours if needed.