The quiet case for ACH: why service businesses are moving away from card rails
Card rails were built for retail. Service businesses look nothing like that. Here's the math, the trade-offs, and the rollout playbook for switching to ACH-first invoicing.
Why a growing number of service businesses are quietly moving away from card rails, and what changes when you do.
Most owners I talk to start with the same instinct: cards are easy, customers are used to them, and the fees feel like a cost of doing business. That instinct made sense for a decade. It is starting to make less sense every quarter.
Card rails were built for a different kind of commerce: coffee shops, retail counters, $40 transactions where speed at the till matters more than basis points. Service businesses look nothing like that. Many service businesses send invoices well over $1,000, get paid a handful of times a month, and run on margins that flinch at every percent. That is the world where ACH stops being a back-office curiosity and starts being a real lever.
The math nobody runs on the day they sign up
Here is the spread that surprises people. On a $2,500 invoice, a typical card processor takes about $73. That same payment over ACH on VezmoPay costs $10, because ACH is 0.9% + $1.00, capped at $10.00 per payment. Multiply that by the 60–80 invoices a small agency or contractor sends in a year and you are looking at four figures of pure margin sitting on the table.
It gets larger as you grow. Take a service business with $480,000 in annual collections, averaging $1,800 per invoice (about 267 invoices a year):
- On cards at 2.9% + $0.30, they would pay roughly $14,000 in fees.
- On VezmoPay ACH at 0.9% + $1.00, capped at $10.00, they would pay about $2,670.
That is a swing of more than $11,000. For a 4-person service team that is a real new hire, a real ad budget, a real bonus pool. It does not feel exciting at sign-up because each invoice only saves $40 to $60. It compounds quietly until you look at year-end.
The "but my clients hate ACH" myth
I hear this constantly. It usually is not true any more. Three things changed in the last few years:
- Bank logins replaced routing numbers. Customers no longer dig out a paper check to type 17 digits. They click their bank's logo, sign in, and they are done in under 30 seconds.
- Settlement got faster. Instant account verification and same-day ACH have made bank payments quicker to set up and settle than they used to be. For most service work, a few business days is fine.
- Clients started preferring it. Especially B2B. CFOs of mid-market companies actively ask whether you accept ACH because their finance teams hate reconciling card statements.
The friction left in ACH is mostly UX friction, not rail friction. Build the checkout right and clients pay it the same way they pay a card.
What changes when you switch
I want to be honest about the trade-offs, because it is not a free lunch.
You give up some speed. Card auth happens in milliseconds. ACH takes a few business days to settle. If you are running a flash sale or a digital download where the customer expects instant fulfillment, keep cards as an option.
Disputes work differently. With cards, you can answer a dispute with evidence. With ACH, a customer can report a debit as unauthorized (up to 60 days for personal accounts, much less for business accounts), and there is usually no evidence process to win it back. Signed contracts, clear invoices and paying by bank login keep these rare for service work.
You gain margin, predictability, and reconciliation. ACH posts as a single line item with a clear sender. Card payments arrive as net deposits two days later, after fees, in batches that take time to match. Bookkeeping gets quieter the moment you switch.
How to roll it out without scaring anyone
The mistake I see most often is "I am turning off cards next Monday." Do not do that. The pattern that works:
- Make ACH the default on new invoices. Leave card as a backup option. Most clients pick the path of least resistance: if ACH is presented first, that is what they use.
- Explain the choice. One line on the invoice, such as "Paying by bank transfer helps us keep our prices down", nudges clients toward ACH without adding a fee.
- Let existing clients stay on whatever rails they prefer. Migrating accounts that already work is rarely worth the friction.
In Vezmo, ACH is one of the payment methods your invoices can offer. It is the kind of change that takes minutes to make and shows up in your P&L months later.
Where ACH still loses
I will not pretend it is the right answer for everyone. ACH is a worse fit when:
- You bill micro-transactions ($1–$50 range). The fixed fee per ACH transfer eats the difference.
- You serve consumers who do not have a checking account, or who pay impulsively from a phone wallet.
- You are international and your customers are not US-domiciled. ACH is a US rail.
- Your customers expect rewards on every transaction (think travel agencies billing high-end clients who want miles).
For everyone else (agencies, contractors, consultants, B2B service businesses, recurring retainers), the math leans toward ACH harder than people realize.
The quiet shift
The owners who make the switch rarely announce it. They turn ACH on, watch the savings for a couple of months, and keep it.
Cards are not going anywhere. They remain the right tool for a long list of jobs. But for invoiced service work, a default of "ACH first, card as a backup" is the trade most people regret not making sooner.
If you are running invoices through Vezmo today and have not flipped that default, it is worth ten minutes of your week. Worst case, you turn it off again. Best case, you find a few thousand dollars a year that was always yours.