How to Accept ACH Payments: A Small Business Guide
ACH bank payments usually cost less than cards and suit recurring bills like tuition, retainers and payment plans. Here is how to set them up, get proper authorization and avoid the common mistakes.
To accept ACH payments, you need a payment gateway or processor that supports bank transfers, a way for customers to enter their routing and account numbers securely, and a clear authorization from each customer before you pull money from their account. Once that is in place, ACH is usually cheaper than cards and works especially well for recurring bills.
This guide walks through the setup step by step, explains how ACH compares with credit cards, and covers the rules your bank and processor will expect you to follow. If you already take cards online and want to add bank payments to the same checkout, our payment gateway integration work covers exactly that.
What an ACH payment is
ACH stands for Automated Clearing House, the US network banks use to move money between accounts. When a customer pays you by ACH, they give you permission to debit their checking or savings account, your provider submits the request through the network, and the money settles into your bank account a few business days later.
You will also see ACH payments called eChecks, bank transfers or bank drafts. For a business taking payments online, they all mean roughly the same thing: the customer pays from a bank account instead of a card.
There are two directions an ACH transfer can go. An ACH credit pushes money out (payroll, paying a vendor). An ACH debit pulls money in. When you accept ACH payments from customers, you are almost always originating ACH debits.
ACH vs credit card: which should you offer?
Most businesses that add ACH keep cards too. The two methods suit different situations.
| ACH bank transfer | Credit or debit card | |
|---|---|---|
| Typical cost | Usually a flat fee or a low percentage with a cap | A percentage of each payment plus a per-transaction fee |
| Speed to your bank | A few business days | Often one to two business days |
| Best for | Larger or recurring payments: tuition, retainers, rent, payment plans | One-time and smaller payments, customers who want card rewards |
| Customer effort | Routing and account number, or bank login through a verification service | Card number, expiration and security code |
| Failure mode | Returns for insufficient funds or closed accounts, sometimes days later | Declines usually show up immediately |
The cost difference is the main reason businesses add ACH. As a published example, Stripe lists ACH Direct Debit at 0.8% with a $5.00 cap. On a $2,000 tuition payment that cap matters a lot compared with a card percentage. Your actual ACH processing fees depend on your gateway and merchant account, so get the numbers in writing from your processor before you decide. Our post on Authorize.Net vs Stripe compares how the two gateways price things.
[ROB: add a real-world example of a client who added ACH and what changed (payment mix, fees, late payments), or remove this line.]
How to accept ACH payments, step by step
1. Choose a provider that supports ACH
You need a gateway that can originate ACH debits and a merchant or bank relationship behind it. Authorize.Net offers ACH through its eCheck.Net service, and Stripe, PayPal, CyberSource and Heartland all have bank payment options. If you are not sure which piece does what, our explainer on payment gateways vs payment processors breaks it down.
Our preferred setup is Authorize.Net with an International Bancard merchant account, and we can integrate the other gateways above if you already have one.
Expect an underwriting review. Providers look at your business type, typical payment size and monthly volume before approving ACH, and some set a per-transaction or monthly limit at first.
[ROB: note how long ACH approval usually takes with International Bancard, and anything clients commonly need to provide.]
2. Decide where customers will pay
You have three common options:
- A virtual terminal, where your staff types in bank details the customer gives over the phone or on paper.
- A payment link sent by email or text.
- A payment page or portal on your own website, where customers enter their bank details themselves and can save them for next time.
For anything recurring, the self-service option saves the most office time. A branded customer payment portal on your own subdomain lets customers pay by card or bank account, store a payment method, and see receipts without calling your office.
3. Get proper authorization
Before you debit anyone’s account, you need their authorization. For online payments that usually means a clear checkbox or button with authorization language the customer agrees to before submitting. For paper or phone payments, many businesses use an ACH authorization form that the customer signs.
Whatever the format, the authorization should make clear who is being paid, the amount (or how it is calculated), the timing for recurring debits, and how the customer can cancel. Your processor will usually supply or approve the wording, and you should keep a record of every authorization. If you are unsure what your situation requires, ask your processor or attorney rather than writing your own from a template.
4. Validate the bank account
Nacha, the organization that writes the rules for the ACH network, requires businesses that take ACH debits online to validate a customer’s account before the first time it is used. At a minimum, that means confirming the account is open and can accept ACH entries. Methods include micro-deposits, instant verification services and prenotifications. Most gateways build one of these into the checkout, so you mainly need to make sure it is switched on.
5. Set up recurring billing if you need it
ACH is at its best for payments that repeat. With autopay, the customer authorizes once and the system debits their account on schedule. Pair that with failed-payment alerts and automatic receipts so your staff only touches the exceptions. Our recurring billing page shows how saved bank accounts, payment plans and late fees fit together.
6. Plan for returns
An ACH payment can come back after it looks successful. Common reasons are insufficient funds, a closed account, or the customer telling their bank the debit was unauthorized. Under the Nacha rules, a consumer generally has 60 days from settlement to dispute an unauthorized debit.
Decide ahead of time what happens when a payment is returned: who gets notified, whether you retry, and whether a returned-payment fee applies under your policy. Failed-payment alerts help here because you hear about a return the same day instead of finding it at month-end.
Rules and security to keep in mind
This is general information, not legal or compliance advice. Your processor and your bank set the specific requirements for your account.
- Fraud monitoring. Nacha rules that took effect in 2026 require businesses that originate ACH payments to have risk-based monitoring for unauthorized and fraudulent payments. For most small businesses, much of this is handled by the gateway, but ask your processor what they expect from you.
- Entry descriptions. Since March 2026, consumer online debits use a standard “PURCHASE” description. Your gateway sets this, so it is mainly worth knowing in case customers ask what they will see on their statement.
- Storing bank details. Bank account numbers need the same care as card numbers. With a tokenized setup, the gateway stores the account details and your site keeps only a token. Mobilize Pay never stores card or bank numbers on our servers, and we build to PCI DSS standards. More on that on our payment security page.
- Where the money goes. Mobilize Pay is not a payment processor and never holds client funds. Payments settle from your processor directly into your bank account.
What it costs to add ACH with Mobilize Pay
Your ACH processing fees are set and billed by your processor, not by us. Our side is the portal and checkout your customers use.
A Mobilize Pay customer payment portal is $3,750 one time, or $450 a month for 12 months with hosting and security included in year one. After that, hosting is $100 a month and security is $99.99 a year. Custom checkout, recurring billing builds, integrations and non-preferred processors are quoted to scope. While you are on monthly hosting, if something breaks, we fix it at no charge, and support is available 24/7.
Frequently asked questions
How long do ACH payments take to reach my bank?
Usually a few business days, depending on your provider and when the payment is submitted. Stripe, for example, lists settlement of up to four business days for ACH Direct Debit, with faster settlement for eligible businesses. Ask your processor for your schedule.
Can I accept ACH payments for free?
Some banks and invoicing tools advertise free ACH, but someone pays for the network and the gateway somewhere, often through monthly fees, slower deposits or limits. Compare total cost, not just the per-payment fee.
Do I need a separate merchant account for ACH?
It depends on your provider. Some gateways bundle ACH with card processing, while others require separate approval for bank payments. Your processor can tell you what applies to your account.
Is ACH safer than taking paper checks?
ACH avoids lost or stolen checks and manual deposits, and a tokenized setup keeps bank details off your systems. It still needs authorization records, account validation and a plan for returns.
Can customers pay by ACH and card on the same page?
Yes. A well-built checkout or payment portal can offer both, let customers save either one for autopay, and send the same receipts and alerts regardless of method.
Get a free mockup
If you want customers to pay by bank account or card on your own website, we can show you what that looks like before you commit to anything. Get a free mockup of your branded payment portal. It takes about 15 minutes, and most portals launch within two weeks to a couple of months.
