Skip to content
Create account or Sign in
The Stripe Docs logo
/
Ask AI
Create accountSign in
  • Get started
  • Payments
  • Revenue
  • Risk
  • Data
  • Money management
  • Stablecoins
  • Embedded finance
  • Developer resources
More
APIs & SDKsHelp
Overview
Versioning
Changelog
    Overview
    Endive
    Dahlia
    Clover
    Basil
    Acacia
    Previous versions
Upgrade your integrationHow API versioning works
Essentials
SDKs
API
Events
Testing
Stripe CLI
Tools
Stripe Dashboard
Stripe Projects
Provisioning
Workbench
Developers Dashboard
Stripe for Visual Studio Code
Terraform
Stripe Discord server
Features
Workflows
Batch jobs
Stripe health alertsFile uploads
AI tools
Agent pluginsModel Context ProtocolAgent skillsStripe Directory
Extend Stripe
Overview
Build Stripe apps
Use apps from Stripe
Build extensions
Custom objects
Security and privacy
Security
Activity logsStripebot web crawler
Privacy
Partners
Partner ecosystem
Partner certification
United States
English (United States)
  1. Home/
  2. Developer resources/
  3. Changelog/
  4. Endive/
  5. 2026-09-30.endive

Exposes ACH return codes on OutboundPayments, OutboundTransfers, and InboundTransfers in v1 Treasury

What’s new

v1 OutboundPayments, v1 OutboundTransfers, and v1 InboundTransfers now include raw ACH return codes and return reasons when an ACH transfer fails or is returned. When available, the ACH return code and reason appear under returned_details.network_details.ach for returned v1 OutboundPayments and v1 OutboundTransfers, and failure_details.network_details.ach for failed or returned v1 InboundTransfers.

Impact

You can use the raw ACH return codes for workflows that require rail-specific information, including fraud investigations, compliance operations, and customer support. Stripe’s existing normalized failure and return codes remain available under returned_details.code for v1 OutboundPayments and OutboundTransfers, and under failure_details.code for v1 InboundTransfers. Integrations that don’t need raw ACH details require no changes.

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-09-30.endive
  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.

Learn more about Stripe API upgrades.

Related changes

  • Renames the Reserve Release reason enum value
  • Adds destination property and new enum values to Reserve Plans, Holds and Releases
  • Adds support for received credits sent via the Real-Time Payments network
Was this page helpful?
YesNo
  • Need help? Contact Support.
  • Chat with Stripe developers on Discord.
  • Check out our changelog.
  • Questions? Contact Sales.
  • LLM? Read llms.txt.
  • Powered by Markdoc
On this page