When a US business collects a recurring payment from a customer’s bank account (a subscription, a membership, a monthly utility bill), it usually uses an ACH debit. This is the pull side of the ACH network: with the customer’s authorisation, the business pulls the money on a schedule. This page explains how ACH debit works for recurring billing and how it compares with newer instant-rail approaches.
ACH debit is a pull payment, where the business collects, rather than the customer sending. For the general concept, see push vs. pull payments. For the push side of ACH, see ACH credit transfers.

How ACH debit works for recurring billing

1

Customer authorises the debit

The customer gives the business permission to debit their account, for example by agreeing to terms at signup and providing their bank account and routing numbers.
2

Business initiates each debit

On the agreed schedule, the business submits an ACH debit to pull the payment. Because ACH is batch-based, these are processed in windows rather than instantly.
3

Funds settle

The payment settles over standard ACH (typically 1–3 business days) or same-day ACH for eligible, time-sensitive collections.
4

Handling returns

If a payment fails (for example, insufficient funds), ACH provides a return process. This reversibility is part of what makes ACH debit workable for recurring billing.

Why ACH debit suits recurring payments

Low cost at volume

ACH is inexpensive per payment, which matters when you are billing many customers every month.

Familiar and widely supported

Almost every US bank account can be debited via ACH, so it reaches nearly all customers.

Built-in returns

The return process gives a way to handle failed or disputed debits, which is useful for ongoing billing relationships.

Good for predictable amounts

Fixed subscriptions and memberships map neatly onto scheduled ACH debits.

ACH debit vs. instant-rail recurring approaches

The instant rails (FedNow and RTP) are credit-push by design; the sender initiates. That means they do not offer a traditional pull debit in the way ACH does. Newer approaches such as request-for-payment (where the business asks and the customer approves) and variable recurring payments aim to bring instant rails into recurring billing, but adoption is still early.
Because instant payments are credit-push and irrevocable, they change how recurring billing works: the customer approves each payment or a variable agreement, rather than the business simply pulling. Expect this area to evolve over the next few years.
For most US recurring billing today, ACH debit remains the practical default: cheap, familiar, and supported everywhere. Keep an eye on request-for-payment and variable recurring payments as instant-rail options mature.