# What Is ACH Payment? A Complete Guide for SaaS Founders

> ACH payments explained for SaaS - how they work, why they cost 10x less than cards, settlement timelines, and how to accept them without your own merchant account.
- **Author**: Ayush Agarwal
- **Published**: 2026-05-27
- **Category**: Payments, SaaS, ACH
- **URL**: https://dodopayments.com/blogs/what-is-ach-payment-saas-guide

---

ACH stands for Automated Clearing House, the network that moves money between US bank accounts. If you have ever been paid by direct deposit, paid a utility bill from your bank app, or set up an autopay for a streaming service that pulled directly from your checking account, you have used ACH.

For SaaS founders selling in the United States, ACH matters because it is the cheapest way to collect recurring payments at scale. A typical card transaction costs 2.9% + $0.30. A typical ACH transaction costs a flat $0.20-$1.50 regardless of size. On a $5,000 annual subscription, that is the difference between $145 in card fees and $1 in ACH fees - a 99% reduction in payment costs.

This guide explains what ACH payments are, how the network actually moves money, what the real settlement timelines look like, what can go wrong, and how SaaS companies can accept ACH without taking on the compliance overhead of running their own merchant account.

## What ACH Stands For and How the Network Works

ACH is governed by Nacha (the National Automated Clearing House Association), a private organization that sets the rules under which US banks exchange electronic payments. The network processes more than 30 billion transactions per year totaling over $80 trillion in value, including payroll, government benefits, business-to-business payments, and consumer bill pay.

Unlike card networks (Visa, Mastercard, American Express), ACH does not authorize transactions in real time. Instead, it batches transactions throughout the business day and settles them through the Federal Reserve. This batch architecture is why ACH is cheap but slow - the absence of real-time authorization removes a layer of cost and complexity that card networks charge for.

Every ACH transaction has two sides:

- The **Originating Depository Financial Institution (ODFI)** is the bank that initiates the payment on behalf of the business or person sending money
- The **Receiving Depository Financial Institution (RDFI)** is the bank where the recipient holds their account

The ODFI submits batches to one of two ACH operators - the Federal Reserve (FedACH) or The Clearing House (EPN) - which sort and forward the transactions to the appropriate RDFI. Settlement happens on a scheduled basis, typically the next business day for standard ACH and within hours for Same Day ACH.

## ACH Credit vs ACH Debit

Every ACH transaction is either a credit or a debit, and the distinction matters for SaaS billing.

**ACH credit** is a push payment. The payer's bank initiates the transfer and pushes funds to the payee's account. Direct deposit of payroll is the most common example - your employer's bank sends funds to your bank.

**ACH debit** is a pull payment. The payee's bank initiates the transfer and pulls funds from the payer's account, with the payer's prior authorization. Subscription billing, autopay utility bills, and SaaS recurring charges all use ACH debit.

For SaaS, ACH debit is what you almost always want. The customer authorizes you to pull a specific amount on a specific schedule (or a variable amount up to a cap), and your processor initiates the pull through the ACH network on each billing cycle. The customer does not need to do anything on each renewal date.

The authorization itself must be captured in writing or through an equivalent electronic record - typically a checkbox at checkout that says something like "I authorize [Company] to debit $X from my bank account on the 1st of each month." Nacha rules require this authorization to be revocable, retrievable, and proof of consent in the event of a dispute.

## How ACH Compares to Card and Wire Payments

| Payment Method | Typical Cost | Settlement Time | Best For |
| --- | --- | --- | --- |
| ACH (standard) | $0.20-$1.50 flat | 1-3 business days | Recurring subscriptions, B2B invoicing |
| ACH (Same Day) | $0.50-$5.00 flat | Same business day | Urgent recurring payments |
| Credit card | 2.9% + $0.30 | 1-2 business days | Consumer checkout, one-time purchases |
| Wire transfer | $15-$50 flat | Same day (domestic) | Large one-time B2B payments |
| RTP / FedNow | $0.25-$1.00 flat | Real-time | Instant payouts, urgent transfers |

For SaaS subscriptions where the average customer pays $50 or more per month, ACH delivers materially better economics than cards. The trade-off is settlement speed and failure handling - which we cover next.

## ACH Settlement Timelines in Practice

Standard ACH settles in 1-3 business days. The exact timing depends on when the ODFI submits the batch and which window (morning, midday, afternoon, evening) it lands in. A transaction submitted before the morning cutoff on Monday typically settles Tuesday. A transaction submitted after Friday afternoon settles the following Tuesday.

Same Day ACH settles within hours but costs more and has a per-transaction cap of $1 million. It runs in three windows on each business day, with funds typically available to the receiving account within a few hours of submission.

For SaaS billing operations, the practical implication is that ACH revenue is not real revenue until it settles. A customer authorizing payment on the 1st of the month is not actually paid until the 2nd, 3rd, or later. If the customer's bank rejects the debit, you may not know for 2-5 business days. Cash flow forecasting for ACH-heavy SaaS businesses needs to account for this delay.

```mermaid
flowchart LR
    A[Customer authorizes
recurring debit] -->|"Day 0"| B[ODFI submits
ACH batch]
    B -->|"Day 0-1"| C[ACH operator
routes to RDFI]
    C -->|"Day 1-2"| D[RDFI debits
customer account]
    D -->|"Day 1-3"| E[Funds settle
to merchant]
    D -.->|"Day 2-5"| F[Possible
ACH return]
```

## ACH Return Codes Every SaaS Founder Should Know

When an ACH debit fails, the RDFI returns it to the ODFI with a numeric reason code. The most common return codes for SaaS are:

- **R01 - Insufficient Funds**: The customer's account does not have enough money. This is the single most common ACH failure for SaaS. Standard practice is to retry after 3-5 days
- **R02 - Account Closed**: The customer closed the bank account. The card-on-file equivalent of `card_declined`. Reach out to the customer for new payment details
- **R03 - No Account / Unable to Locate**: The account number does not exist. Usually a data-entry error at signup
- **R07 - Authorization Revoked**: The customer told their bank to stop the recurring debit. Treat this as an immediate cancellation; do not retry
- **R08 - Payment Stopped**: The customer placed a stop-payment order on this specific charge. Investigate before retrying
- **R10 - Customer Advises Unauthorized**: The customer claims they did not authorize the debit. This is the ACH equivalent of a chargeback and counts against your return rate
- **R29 - Corporate Customer Advises Not Authorized**: B2B equivalent of R10

Nacha enforces return rate thresholds. Total returns must stay below 15%, administrative returns (R02, R03, R04) below 3%, and unauthorized returns (R05, R07, R10, R29, R51) below 0.5%. Crossing these thresholds triggers monitoring from your originating bank and, in severe cases, suspension of ACH origination privileges.

Healthy SaaS ACH operations typically run R01 retries at 3 and 7 days after the initial failure, then escalate to email and in-app prompts asking the customer to update their bank account or switch to a card.

## What ACH Costs SaaS Companies

ACH processing in the United States is dramatically cheaper than card processing, but the pricing structure varies by processor.

**Per-transaction fee**: Most processors charge a flat fee per ACH transaction, typically $0.20-$1.50. Some processors cap the fee at a fixed maximum (for example, $5 or $25) on very large transactions; others charge a small percentage (0.5%-0.8%) up to a cap.

**Monthly minimum and platform fees**: Some processors charge $25-$200 per month in platform or gateway fees for ACH origination access. These are flat fees regardless of volume.

**Return fees**: Failed ACH debits typically incur a $2-$5 return fee charged by the originating bank. Frequent returns also damage your account standing.

For a SaaS business processing 1,000 ACH transactions per month at an average of $200 each ($200,000 in monthly volume), total processing costs are typically $200-$500 - compared to $5,800-$6,100 for the same volume processed on cards.

From our experience at Dodo Payments working with B2B SaaS teams: ACH is one of the most underused tools in subscription billing. The friction of bank verification is real, but for any business with annual or quarterly contracts, the per-transaction savings versus card processing compound every renewal cycle - and that math typically outweighs the verification friction once a customer is past their first invoice.

## When SaaS Should Offer ACH Alongside Cards

Not every SaaS business needs ACH. The economics depend on average transaction size, customer type, and renewal frequency.

**Strong candidates for ACH**:

- B2B SaaS with annual contracts over $500
- Enterprise products with multi-thousand-dollar invoices
- Consumer subscriptions over $50/month where the savings on payment fees justify the slower settlement
- Any SaaS where the customer base is US-based and has US bank accounts

**Weak candidates for ACH**:

- B2C SaaS under $20/month - card processing is cheap enough at small ticket sizes
- Products with high churn in the first 30 days - settlement delays expose you to giving service before payment confirmation
- Global products where customers do not have US bank accounts - international equivalents like SEPA (EU), BACS (UK), and PAD (Canada) exist but require separate setup

Most SaaS businesses that benefit from ACH offer it as an option alongside cards, with the customer choosing at checkout. Some offer a discount for ACH (typically 1-2%) to nudge customers toward the cheaper rail.

## How to Accept ACH Without Running Your Own Merchant Account

Setting up direct ACH origination requires an account with an ODFI bank, Nacha rule certification, transaction monitoring infrastructure, return handling automation, and ongoing compliance reporting. For most SaaS companies, this is overkill - the operational cost of building and maintaining ACH infrastructure exceeds the savings on the payment fees themselves.

Two paths sidestep this overhead:

**Use a payment processor that supports ACH**: Processors like Stripe ACH, Plaid for bank verification, and ACH-specific gateways let you accept ACH debit payments by integrating an API. You still hold the merchant account, but the processor handles the bank relationship and Nacha compliance.

**Use a Merchant of Record (for international coverage, not ACH)**: A [Merchant of Record](https://dodopayments.com/blogs/what-is-a-merchant-of-record) like Dodo Payments is the named seller on every transaction and handles global tax compliance, chargeback liability, and payment localization across 220+ countries. Most MoRs - Dodo Payments included - currently focus on cards, digital wallets, BNPL, and 30+ local payment methods (UPI, Pix, iDEAL, Bancontact, and similar) rather than ACH. ACH is a US-domestic rail with a narrower use case, so if ACH specifically is what you need, a US-focused processor like Stripe is the closer fit. If the goal is broader international payment-method coverage with tax and chargeback compliance bundled in, an MoR is the cleaner path.

## When to Use What

For SaaS that needs to accept ACH from US business customers, integrate Stripe ACH or GoCardless. For SaaS selling digital products globally, the higher-leverage move is usually broader payment-method coverage and tax compliance through an MoR rather than adding ACH. Read more about [accepting recurring payments](https://dodopayments.com/blogs/accept-recurring-payments-without-stripe) and review the [subscription billing docs](https://docs.dodopayments.com/features/subscription) for the recurring-billing patterns that work across both setups.

## Nacha Rule Updates SaaS Founders Should Track

Nacha updates its operating rules annually. Two recent changes affect SaaS:

**WEB Debit Account Validation (effective March 2022)**: Originators of consumer ACH debit authorized over the internet must use a "commercially reasonable" method to validate that the account is open and authorized for ACH. Plaid-based bank linking satisfies this requirement automatically. Manual entry of routing and account numbers without validation does not.

**Same Day ACH Limit Increase (effective March 2022, expanded annually)**: The per-transaction limit for Same Day ACH was raised to $1 million. This makes Same Day ACH viable for large B2B SaaS invoices that previously had to be split or sent via wire.

If you build directly against ACH, you need to track these updates. If you use an MoR or modern processor, the platform handles the compliance updates for you.

## FAQ

### How long do ACH payments take to settle?

Standard ACH settles in 1-3 business days. Same Day ACH settles within hours but costs more and has a $1 million per-transaction cap. For SaaS billing, plan cash flow assuming 2 business days from authorization to settled funds, with up to 5 business days before potential returns surface.

### What is the difference between ACH and direct deposit?

Direct deposit is a specific use case of ACH credit, typically referring to employer-to-employee payroll deposits. ACH is the underlying network; direct deposit is one application of it. Other ACH credit applications include government benefit payments and B2B disbursements.

### Can ACH payments be reversed?

Yes, but the rules differ from card chargebacks. Consumer ACH debits can be returned by the customer's bank for up to 60 days after settlement for unauthorized debits, and up to 2 business days for stop-payment requests. Business ACH debits have a much shorter return window of 1-2 business days. Once outside the return window, ACH debits are effectively final.

### Is ACH only available in the United States?

The ACH network is US-specific, but every developed economy has an equivalent system. The EU has SEPA Direct Debit, the UK has BACS Direct Debit, Canada has PAD (Pre-Authorized Debit), Australia has BECS Direct Debit, and India has NACH. The mechanics are similar - bank-to-bank pull payments with multi-day settlement and return codes - but each requires separate integration.

### What does ACH mean on my bank statement?

When you see "ACH" on a bank statement, it indicates the transaction was processed through the Automated Clearing House network rather than a card network. The descriptor next to it (the company name and transaction reference) identifies who initiated the payment and what it was for. ACH descriptors are typically less standardized than card descriptors, which is why some SaaS customers do not recognize the charge and contact support thinking it is fraud.

## Conclusion

ACH is the cheapest scalable payment rail in the United States, and for any SaaS company with average transaction sizes above $50, the cost savings versus card processing are substantial. The trade-off is slower settlement and a different set of failure modes than cards - return codes instead of declines, multi-day reconciliation instead of real-time confirmation, and a Nacha rulebook that originating banks expect you to follow.

For SaaS founders focused on US B2B billing, integrating Stripe ACH or GoCardless is the cleanest path. For SaaS selling digital products globally, an MoR like [Dodo Payments](https://dodopayments.com) is usually a better tradeoff: ACH is not in the supported payment-method set, but cards, digital wallets, BNPL, UPI, Pix, iDEAL, and 30+ other local methods are, along with global tax compliance and chargeback liability transfer.

Compare Dodo's supported payment methods and fee structure on the [pricing page](https://dodopayments.com/pricing), or read the [recurring payments guide](https://dodopayments.com/blogs/accept-recurring-payments-without-stripe) for a deeper look at subscription billing infrastructure.
---
- [More Payments articles](https://dodopayments.com/blogs/category/payments)
- [All articles](https://dodopayments.com/blogs)