# Nacha Rules Explained: What Businesses Accepting ACH Must Follow

> Nacha rules govern every ACH debit. Learn the operating rules for merchants: SEC codes, authorizations, return rate limits and 2026 fraud monitoring updates.
- **Author**: Deepak Jangir
- **Published**: 2026-11-10
- **Category**: Payments, Compliance
- **URL**: https://dodopayments.com/blogs/en/nacha-rules

---

Nacha rules are the operating rules that govern every payment on the US Automated Clearing House (ACH) network, and any business that pulls money from a customer's bank account by ACH debit is bound by them. They define how to get a valid authorization, which transaction type (SEC code) to use, how long to keep records, how to protect account data, how often your debits may be returned and how to monitor for fraud.

You never sign a contract with Nacha directly. You agree to the rules through your bank or payment provider, and if you break them, the bank can be fined, which it passes on to you or treats as a reason to stop processing for you. This guide covers the Nacha requirements for merchants that matter most to online businesses and SaaS companies. For network basics, start with our [ACH payment guide for SaaS](https://dodopayments.com/blogs/what-is-ach-payment-saas-guide).

## What Are the Nacha Operating Rules?

Nacha manages the governance of the ACH network in the United States. Its rulebook, the Nacha Operating Rules and Guidelines, is updated every year and sets the framework for how ACH entries are authorized, formatted, settled and returned. Federal rules such as Regulation E (for consumer accounts) sit alongside it, and your bank agreement makes it binding on you.

### Who must follow Nacha rules

Every party that touches an ACH entry has defined obligations:

- **Originator:** the business that initiates the debit or credit. If you charge customers by ACH, you are the Originator, unless a platform originates on your behalf.
- **ODFI:** the Originating Depository Financial Institution, the bank that submits entries into the network and is liable for them.
- **RDFI:** the Receiving Depository Financial Institution, the customer's bank, which posts the debit or returns it.
- **Receiver:** the customer whose account is debited or credited.
- **Third-Party Sender:** a payment provider that holds the banking relationship and originates entries for many businesses.
- **Third-Party Service Provider:** a vendor that performs processing functions, such as file creation, for others.

The ODFI warrants that every entry it sends is properly authorized, so it pushes those obligations down to Originators and Third-Party Senders by contract.

```mermaid
flowchart LR
    A["Customer (Receiver)
authorizes debit"] --> B["Merchant (Originator)"]
    B --> C["Payment platform
(Third-Party Sender)"]
    C --> D["ODFI
(originating bank)"]
    D --> E["ACH Operator
(Fed / EPN)"]
    E --> F["RDFI
(customer's bank)"]
    F -->|"Debit posted or
returned"| E
    E --> D
```

ACH differs from wires and card rails in how authorization and returns work. Our comparison of [EFT vs ACH vs wire transfer](https://dodopayments.com/blogs/eft-vs-ach-vs-wire-transfer) explains where each fits.

## SEC Codes Online Merchants Need to Know

Every ACH entry carries a Standard Entry Class (SEC) code that tells the network how the payment was authorized. The code determines the authorization format, the customer's return rights and some of the risk controls you must apply. Using the wrong code is a rules violation, even if the customer genuinely agreed to pay.

| SEC code | Full name | Account type | How authorization is obtained | Typical online use |
| --- | --- | --- | --- | --- |
| WEB | Internet-Initiated/Mobile Entry | Consumer | Online or via a mobile device | Checkout pages, in-app payments |
| PPD | Prearranged Payment and Deposit | Consumer | Written and signed (or similarly authenticated) | Recurring bills set up with a signed form, payroll |
| CCD | Corporate Credit or Debit | Business | Agreement between the two businesses | B2B invoices, business customers paying SaaS fees |
| TEL | Telephone-Initiated Entry | Consumer | Spoken over the phone, recorded or confirmed in writing | Phone sales and support-assisted payments |

For most SaaS and digital product businesses, consumer debits collected at an online checkout are WEB entries and business debits are CCD. Check conversion codes also exist, covered in our guide to [eCheck payment processing](https://dodopayments.com/blogs/echeck-payment-processing). Since March 20, 2026, Nacha also requires the Company Entry Description "PURCHASE" for online purchases of goods and services paid by WEB debit, which your provider usually sets for you.

## Nacha Authorization Requirements

Authorization is the foundation of Nacha compliance. A debit without a valid authorization is unauthorized, whether or not the customer owed you the money, and the customer's bank can return it.

### What a valid authorization must include

- **Clear, readily understandable terms** stating that the customer is authorizing an ACH debit from their bank account.
- **The amount, or how it is determined,** plus the date or frequency of the debit.
- **The account to be debited,** using routing and account numbers the customer provides.
- **A revocation method** that is reasonable, such as contacting support or changing account settings.
- **Authentication** appropriate to the channel. For WEB entries, you must use commercially reasonable methods to verify the customer's identity.
- **Evidence of assent,** such as a checkbox or submit button tied to the authorization text, or a recording for TEL.

For recurring debits, the customer must receive a copy of the authorization or its terms. For sample wording, see our guide to the [ACH authorization form](https://dodopayments.com/blogs/ach-authorization-form). The idea mirrors card-on-file consent in a [credit card authorization form](https://dodopayments.com/blogs/credit-card-authorization-form), but Nacha is stricter about revocation and retention.

### Record retention

Originators must keep the authorization, or a readily producible copy, for two years from the termination or revocation of the authorization. Your bank can request it at any time, and it is your main evidence when a customer claims a debit was unauthorized. Store the timestamp, IP or device details, the exact text shown and the customer's identity, but keep full account numbers out of these logs.

### WEB debit account validation

Originators of WEB debits must use a commercially reasonable fraudulent transaction detection system. Since 2021, that system must include account validation for the first use of an account number and whenever the customer changes it. Validation confirms the account is open and can accept entries, typically through:

- Real-time account verification services
- Micro-entries the customer confirms
- A prenotification (zero-dollar entry) followed by a waiting period
- A provider that already holds a verified status for that account

A routing number check confirms the bank exists, not that the customer's account is open, so it usually sits alongside other controls.

## Nacha Compliance for Returns and Return Rates

An ACH return is the RDFI sending a debit back because it could not or should not be posted. The individual reason codes are covered in our guide to [ACH return codes](https://dodopayments.com/blogs/ach-return-codes), so this section focuses on the rules around them.

### Return timeframes

Most returns must reach the ODFI within two banking days of settlement. The major exception is unauthorized debits to consumer accounts, which the RDFI can return for up to 60 calendar days after settlement. That long tail is why an ACH payment that "succeeded" can still come back weeks later, a risk explained in our guide to [payment reversals](https://dodopayments.com/blogs/payment-reversal). Business accounts (CCD) generally get only the two-banking-day window.

### Return rate thresholds

Nacha monitors return rates at the Originator level. Exceeding these thresholds triggers inquiries to your ODFI and potentially enforcement.

| Return category | Threshold | What counts | Typical causes |
| --- | --- | --- | --- |
| Unauthorized returns | 0.5% | Unauthorized debits, revoked authorizations and similar | Weak authorization flows, friendly fraud, stolen account details |
| Administrative returns | 3.0% | Account closed, no account, invalid account number | Poor account validation, typos, stale data |
| Overall returns | 15.0% | All debit returns for any reason (excluding RCK) | All of the above plus insufficient funds |

Rates are measured on debit entries over a 60-day or two-calendar-month period. An illustrative example: if you originate 4,000 WEB debits in two months and 24 come back as unauthorized, your unauthorized rate is 0.6%, over the limit, even if your overall rate is a comfortable 4%.

Unauthorized returns also carry an Unauthorized Entry Fee paid by the ODFI to the RDFI, which providers often pass through. Reinitiation is limited too: you may retry an insufficient-funds return up to two more times within 180 days of settlement, but retrying an unauthorized return without a new authorization is a violation.

## Data Security and Fraud Monitoring Rules

### Protecting account data

Every non-consumer participant must protect ACH data with commercially reasonable security, including policies on how account information is stored, transmitted and destroyed. Account numbers sent over unsecured networks such as the internet must be encrypted in transit.

Originators, Third-Party Service Providers and Third-Party Senders that originate more than 2 million ACH entries a year must also render account numbers unreadable when stored electronically, through encryption, tokenization or truncation. Below that volume, treating account numbers like card data is still the safe default. Our [PCI compliance checklist for SaaS](https://dodopayments.com/blogs/pci-compliance-checklist-saas) covers many of the same controls, and privacy laws still apply, as described in our post on [payment compliance under GDPR and PSD2](https://dodopayments.com/blogs/payment-compliance-gdpr-psd2).

### The 2026 risk management rules

The biggest recent change to the Nacha Operating Rules is a risk management package phased in during 2026. Previously, Originators only had to run fraud detection on WEB debits and micro-entries. Now each ODFI, non-consumer Originator, Third-Party Sender and Third-Party Service Provider must establish risk-based processes reasonably intended to identify entries suspected of being unauthorized or authorized under false pretenses, and review them at least annually.

"False pretenses" covers credit-push frauds like business email compromise, vendor impersonation and payroll diversion, where the payer authorizes the payment but has been deceived. The rollout came in two phases:

- **Phase 1, March 20, 2026:** all ODFIs, plus non-consumer Originators, Third-Party Service Providers and Third-Party Senders with 2023 origination volume of 6 million entries or more.
- **Phase 2, June 2026:** all remaining non-consumer Originators, Third-Party Service Providers and Third-Party Senders. The formal date of June 19, 2026 was a federal holiday, so the practical deadline was June 22, 2026.

A parallel rule requires RDFIs to monitor incoming credits for fraud on the same timeline. For online businesses, the takeaway is that fraud obligations no longer stop at the checkout page. If you send ACH credits such as partner payouts or vendor payments, verify who you are paying, as described in our guide to [KYB verification](https://dodopayments.com/blogs/kyb-verification).

### Same Day ACH and penalties

Same Day ACH lets eligible entries settle the same banking day if submitted before the cutoff windows, with a per-entry limit of $1 million. Return and authorization rules do not change, so faster settlement does not shorten the 60-day unauthorized return window. For timelines and cutoffs, see [how long an ACH transfer takes](https://dodopayments.com/blogs/how-long-does-ach-transfer-take).

Nacha enforces the rules through its National System of Fines, which applies to financial institutions rather than merchants. Fines escalate with the severity and repetition of violations, and Nacha can direct an ODFI to suspend an Originator or Third-Party Sender. Banks contractually pass costs down to the business responsible, and many will terminate a relationship rather than absorb repeated return rate problems.

## Nacha Compliance Checklist for Merchants

- **Pick the right SEC code:** WEB for consumer online checkout, CCD for business accounts, TEL only for phone authorizations.
- **Write clear authorization language** that says "ACH debit", states amount and timing and explains how to revoke.
- **Capture proof of assent** with timestamp, device data and the exact text accepted.
- **Retain authorizations for two years** after termination or revocation.
- **Validate accounts** on first use and on account changes for WEB debits.
- **Track return rates monthly** against the 0.5%, 3% and 15% thresholds.
- **Respect reinitiation limits** and never retry unauthorized returns without new authorization.
- **Encrypt account numbers** in transit and make them unreadable at rest.
- **Document a risk-based fraud monitoring process** for debits and credits and review it annually.
- **Use a recognizable statement descriptor** so customers contact you instead of their bank.
- **Wait for settlement** before fulfilling high-value orders or issuing refunds.

## How a Merchant of Record Changes Your Nacha Obligations

If you run ACH directly on a bank relationship, your business is the Originator and every checklist item is yours to design, document and defend. That suits high-volume billers with dedicated payments and risk teams. For most SaaS and digital product companies, it is a lot of compliance surface area for one payment method.

A [merchant of record](https://dodopayments.com/blogs/what-is-a-merchant-of-record) is the legal seller, so it holds the banking relationships, originates the entries and carries the network-facing obligations: authorization format, account validation, data security, return monitoring and fraud controls. You still need to describe your product honestly, deliver what you sold and keep disputes low.

With [Dodo Payments](https://dodopayments.com), ACH Direct Debit is a checkout option for US customers paying in USD. Per the [ACH Direct Debit documentation](https://docs.dodopayments.com/features/payment-methods/ach), the customer enters the account holder name, routing number, account number, account type and email, checkout validates the routing number, and submitting the form authorizes the debit under a mandate. Dodo is the seller of record, as described in the [merchant of record overview](https://docs.dodopayments.com/features/mor-introduction).

```mermaid
sequenceDiagram
    participant C as Customer
    participant K as Dodo Checkout
    participant D as Dodo (MoR)
    participant N as ACH Network
    participant M as Your app
    C->>K: Choose ACH, enter bank details
    K->>K: Validate routing number
    C->>K: Accept mandate and submit
    K->>D: Create payment
    D->>N: Submit debit
    D->>M: payment.processing webhook
    N-->>D: Clears or returns (up to 4 business days)
    D->>M: payment.succeeded or payment.failed
    M->>M: Fulfill only on payment.succeeded
```

A few operational points stay with you. ACH settles in up to 4 business days, so read the final status from [webhooks](https://docs.dodopayments.com/developer-resources/webhooks) rather than the checkout redirect, and fulfill only on `payment.succeeded`. Because consumers can return unauthorized debits for up to 60 days, do not refund an ACH payment before it has succeeded. Disputes and refunds use the same flows as cards, per the [disputes documentation](https://docs.dodopayments.com/features/transactions/disputes).

ACH on Dodo costs a flat 1.5% capped at $15 per payment, replacing the card fee, per the [pricing page](https://dodopayments.com/pricing). The minimum payment amount is $0.50. It supports one-time payments, not subscriptions, so recurring plans use the other options in the [payment methods overview](https://docs.dodopayments.com/features/payment-methods). For setup tips, see how to [accept ACH payments from customers](https://dodopayments.com/blogs/accept-ach-payments-from-customers), or compare [pay by bank](https://dodopayments.com/blogs/pay-by-bank) and [direct debit](https://dodopayments.com/blogs/what-is-direct-debit).

## FAQ

### Do small businesses have to follow Nacha rules?

Yes. Any business that originates ACH entries agrees to the Nacha Operating Rules through its bank or payment provider, regardless of size. Some requirements scale with volume, such as storing account numbers unreadable above 2 million entries a year, but authorization, retention, return rate and fraud monitoring rules apply to everyone.

### How long do Nacha rules require you to keep ACH authorizations?

Originators must retain the authorization, or a copy that can be readily produced, for two years from the termination or revocation of the authorization. For one-time debits, keep the record for at least two years after the payment.

### What happens if my ACH unauthorized return rate goes above 0.5%?

Nacha can open an inquiry with your bank, which will ask you to explain the cause and bring the rate down within a set period. Continued violations can lead to fines against the bank, usually passed on to you, and possible suspension from originating entries.

### Is a routing number check enough for Nacha account validation?

No. A routing number check confirms the bank exists, but the WEB debit rule requires validating that the account itself is open and legitimate on first use. Most businesses meet this with account verification services, micro-entries or a provider that validates accounts as part of its fraud detection.

### Do the 2026 Nacha fraud monitoring rules apply to merchants?

They apply to non-consumer Originators, which includes businesses that originate their own ACH entries, as well as banks and third-party processors. Large originators had to comply from March 20, 2026, and all others from June 22, 2026. If a merchant of record originates the entries, it carries most of that monitoring work.

## Final Thoughts

Nacha rules come down to a handful of disciplines: get a clear authorization, use the right SEC code, validate accounts, keep records for two years, protect account data, watch return rates and monitor for fraud on debits and credits. If you would rather offer ACH as one checkout option and let the legal seller carry the network obligations, see how [Dodo Payments handles payments as a merchant of record](https://dodopayments.com/payments).
---
- [More Payments articles](https://dodopayments.com/blogs/category/payments)
- [All articles](https://dodopayments.com/blogs)