The Quiet Rail: When ACH Belongs in Your Payment Integration and When It Doesn’t

Despite the fact that ACH processed over $93 trillion in 2025, many ISV platforms are still treating ACH as an afterthought. 

That gap between volume and platform priority reflects a persistent misconception: that ACH is a fallback for merchants without card access rather than the standard infrastructure of B2B invoice environments, healthcare billing systems, property management platforms, and subscription businesses where bank transfers outperform other payment methods. 

The payment rails an Independent Software Vendor (ISV) supports are, in practice, a statement about which merchants the platform was built for. What follows is the case for ACH — where it belongs, where it falls short, and what it actually takes to implement it well.

More Payment Options Mean More Revenue Captured

There are two durable arguments for ACH: first, the more payment types and channels a merchant can offer—where they make sense for the vertical—the easier it is to get paid. And second, ACH is more cost-effective and predictable to process than card payments because it is typically a flat transaction fee. 

Customers want to pay the way they prefer. Merchants who can accommodate that preference capture revenue that would otherwise be lost or delayed at the point of friction, because the payment method the customer expected was unavailable. For merchants processing high volumes of recurring or invoice-driven payments, the gap between what a customer prefers and what the platform supports is a gap in collected revenue.

For ISVs, payment optionality is a platform decision with consequences for every merchant in the portfolio. A platform that supports only card rails has made that decision on behalf of its merchants, regardless of what those merchants’ customers actually prefer. In verticals where ACH is expected, the cost of that decision accumulates over time.

ACH Belongs in Specific Verticals (Not All of Them)

ACH serves specific merchant categories well. The verticals where it belongs share a recognizable set of characteristics: invoice-driven payment flows, high average transaction values, recurring billing relationships, and customer bases that treat bank transfer as a standard option rather than an alternative one. Those verticals include:

• B2B invoice environments, where businesses reach for bank transfer when it is available, faster to reconcile, and free of the interchange cost that moves through the supply chain. B2B payments via ACH have grown consistently year over year. 
• Healthcare billing, in an environment of high deductible plans, post visit billing, and large patient balances, ACH offers a convenient way for patients to pay online while reducing  processing costs for the provider.
• Property management, where monthly recurring payments at amounts that make card processing fees material are a natural fit for ACH. A landlord collecting several thousand dollars a month in rent has a different cost sensitivity to fees than a retailer processing smaller transactions.
• Subscription and recurring billing businesses, where card expiration cycles create the kind of churn that bank transfers eliminate. For merchants whose revenue depends on consistent recurring collection, ACH removes a structural variable that card rails cannot.

Verticals where ACH is not a good fit share an equally recognizable set of characteristics: immediate fulfillment expectations, one-time or unestablished customer relationships, and checkout environments where any delay between authorization and settlement creates operational or trust problems. Those verticals include:

• Ecommerce checkout, where customers expect instant payment confirmation and merchants depend on authorization speed to trigger fulfillment. The settlement lag in ACH transactions carries risk to ship products before the payment has been processed.
• Time-sensitive product fulfillment, where the window between purchase and shipment is short enough that unresolved payment status creates downstream problems. 
• One-time or impulse purchases, where the transaction is disconnected from any ongoing billing relationship and the customer has no established pattern of bank transfer with that merchant. 
• New or unestablished customer relationships, where the absence of payment history increases return risk and makes the slower dispute resolution process of ACH a meaningful liability. Card networks offer protections that matter more when the merchant cannot yet assess the customer’s reliability.

ACH Removes the Variable Created By Card Expiration

Card decline rates and expiration cycles create a category of revenue loss or delay that is easy to underestimate. A subscription payment that fails because a card expired creates a non-event, then potential churn. Involuntary churn driven by failed payments accounts for a significant share of subscription revenue loss, with estimates across the industry ranging from 20 to 40 percent of total churn depending on the merchant category and billing model. 

The card expiration cycle is a structural contributor to that figure: cards renew on two-to-five year cycles, and every renewal event is an opportunity for a payment to fail before the updated credentials reach the billing system. 

ACH addresses this by removing the expiration variable. For ISVs serving SaaS platforms, subscription businesses, or any merchant with a significant recurring revenue component, fewer failed payments mean fewer involuntary cancellations.

The Limitations Are Specific Enough to Matter Operationally

An honest account of ACH requires treating its limitations with the same precision as its advantages. Platforms that present ACH accurately to its merchants build credibility. Platforms that minimize its constraints leave merchants to discover them through return events and settlement gaps that were avoidable with better preparation. Here’s what you want to know about the challenges and limitations of ACH:

• Slower settlement. ACH funds typically clear in one to three business days. While same-day ACH is now available and has seen increased adoption, it comes with higher transaction costs and its limits are determined by individual financial institutions rather than a standardized network. Merchants with sensitive cash flow needs will notice the difference compared to card payments.
• Higher return risk. NSF events, closed accounts, and unauthorized transaction claims create a return exposure profile that requires risk controls calibrated specifically to ACH. ACH return rates vary by transaction type, with unauthorized returns carrying the highest operational and reputational cost. This is why customers must explicitly approve payments to be taken from their account. ISVs that integrate ACH without maintaining those customer authorizations or building return workflows specifically for these categories will encounter the gap between merchant expectation and operational reality.
• Transaction caps. Standard ACH carries per-transaction limits that require structuring in high-value environments, and those limits are set by the merchant’s financial institution rather than a uniform network standard. Merchants whose transaction profiles push against those limits need to understand the structuring requirements before they encounter them mid-payment.
• No international scope. Standard ACH is restricted to the United States, which means cross-border payment needs require a different solution. Global ACH allows payments to move from U.S. accounts across borders using local rails, but it carries its own constraints around coverage, settlement timing, and availability that make it a distinct consideration rather than a straightforward extension of domestic ACH.

ACH Is a Decision About Fit

ACH earns its place when the underlying business model supports it. When payment behavior, transaction size, and billing structure align with the rail’s strengths, ACH saves the merchant on processing fees, stabilizes recurring revenue, and gives merchants more predictability around costs. When that alignment is absent, the limitations surface quickly. Settlement timing creates tension, return handling becomes reactive, and a strategic addition turns into operational overhead.

For ISVs, the decision is less about expanding coverage and more about knowing which merchants the platform was built for. Supporting ACH signals an understanding of how certain businesses actually operate. The platforms that perform best in those verticals are the ones that chose their rails deliberately, designing around the way money moves in the environments they serve.