ACH Payments vs. Credit Card Billing: Which Should Your Business Accept?

If most of your revenue comes from one-time purchases, accept credit cards first. If most of it comes from subscriptions, memberships, or installment plans, push customers toward ACH after the first payment. The two methods solve different problems, and almost every business that bills repeatedly ends up running both at once.

For recurring billing specifically, ACH usually wins on cost and retention. Credit cards usually win on speed and customer comfort at signup. The right answer depends on transaction size, how often you bill the same customer, and how much involuntary churn is costing you right now, not on which method is “better” in the abstract.

I’m Brant Pallazza, and I work on the billing side at ReliaBills, where we process both card and ACH payments for small businesses every day. This isn’t a theoretical comparison. It’s what I see in account data week after week.

ACH vs Credit Card Billing at a Glance

Factor	ACH (Bank Debit)	Credit Card
Typical cost per transaction	Flat fee, often $0.20 to $1	Percentage-based, typically 2.5% to 3.5% plus a flat fee
Settlement time	1 to 3 business days (Same Day ACH available)	1 to 2 business days after instant authorization
Failure pattern	Returns, usually from insufficient funds or closed accounts	Declines, often from expired or replaced cards
Dispute process	Returns, limited to specific authorized reasons	Chargebacks, easy for the customer to file
Best fit	Recurring billing, large invoices, B2B	First-time purchases, retail, anything under $50
Customer comfort at signup	Lower, requires bank details	Higher, familiar checkout flow

How ACH and Credit Card Payments Actually Move Money

A credit card payment runs through the card networks. The customer’s card details pass to the issuing bank, which approves or declines the charge in seconds, and funds typically land in your account within one to two business days.

An ACH payment moves differently. The customer authorizes you to pull funds directly from their bank account through the ACH Network, governed by Nacha. There’s no card network in the middle. The request goes into a batch and clears between banks, which is why it usually takes one to three business days to settle (faster with Same Day ACH). In 2025, the ACH Network processed 35.2 billion payments valued at $93 trillion, a 7.9% increase over 2024, so this is mainstream infrastructure, not a niche rail.

The practical difference: credit cards tell you immediately if a payment will work. ACH tells you a few days later whether it actually did.

The Real Cost Difference (With Our Own Numbers)

Most comparison articles quote industry averages. Here’s what we actually charge, which illustrates the gap concretely.

On ReliaBills, a credit or debit card transaction costs 3.0% plus $0.30 (4.0% plus $0.30 for American Express). An ACH/eCheck transaction costs a flat $0.99, regardless of invoice amount.

Run that against a $500 invoice:

• Paid by card: $500 × 3.0% + $0.30 = $15.30
• Paid by ACH: $0.99 flat

That’s a 94% reduction in processing cost on one invoice. Scale it: a business billing the same client $500 monthly pays roughly $183.60 a year in card fees versus $11.88 in ACH fees, over $170 in savings on a single customer. Across dozens of recurring clients, that gap becomes one of the largest line items most businesses never budgeted for.

This matches what other processors report. Helcim prices ACH around 0.5% plus 25 cents per transaction, capped at $6, while card processing commonly runs 2.5% to 3%. Exact numbers vary by processor, but the shape of the gap holds everywhere: flat-fee ACH beats percentage-based cards as invoice size or volume increases.

Where card fees claw it back is at the low end. On a $15 invoice, the card fee ($0.75) beats the ACH fee ($0.99). Below roughly $30 to $40 per transaction, credit cards are usually cheaper, depending on your processor’s exact rates. That threshold is the single most useful number in this comparison, and the one most guides skip entirely.

Despite that gap, credit cards still win at the point of signup. Customers are far more comfortable handing over a card number than bank and routing numbers to a business they haven’t paid yet, and instant authorization removes the multi-day uncertainty ACH carries. The tradeoff shows up later: cards expire and get replaced after fraud, while bank accounts rarely change, which is the real reason ACH performs better for retention over time, not just the lower fee.

What I Got Wrong at First

Early on, I assumed cost savings alone would get customers to switch from card to ACH. They don’t.

I pushed ACH adoption as a cost play, framing it around the business’s savings, and adoption stayed flat. What actually moved the number was reframing it for the customer: “no more worrying about an expired card interrupting your service.” Convenience messaging outperformed cost messaging by a wide margin in every account we tracked. People don’t care that you save 2.7% in fees. They care that their gym membership won’t randomly cancel because their card got replaced after a fraud alert.

The second mistake was rolling out ACH requests in the same email as a price increase. Customers conflate the two and assume you’re bundling in a sneaky way to extract more money. Separate the messages by at least one billing cycle.

Chargebacks vs. Returns: The Dispute Risk Nobody Budgets For

This is the part most comparison articles gloss over, and it’s where the real operational pain lives.

A credit card chargeback can be filed for almost any reason: fraud, dissatisfaction, or simply not recognizing a charge on a statement, and it’s easy for the customer to do. You’re often notified after the fact, with little time to respond, plus a fee on top of losing the disputed amount.

An ACH return is more constrained, generally limited to insufficient funds, a closed account, or an unauthorized debit claim under Nacha rules. On ReliaBills, a chargeback or eCheck return both carry a $20 fee, but the frequency differs sharply: card chargebacks happen noticeably more often, mostly because the bar for filing a card dispute is so much lower for the cardholder. If your business has any exposure to “friendly fraud,” cards carry meaningfully more of that risk than ACH does.

How I’d Decide for a New Business (Decision Checklist)

After watching this play out across hundreds of merchant accounts, here’s the decision tree I use when someone asks which to set up first:

• If your average transaction is under $40 and mostly one-time, start with credit cards only. ACH’s flat fee won’t beat card percentage fees at that size.
• If you bill the same customer monthly or send invoices over $100, add ACH and actively offer it as the default at signup, not as a buried option in settings.
• If you’re already seeing failed payments from expired cards disrupting recurring revenue, that’s your clearest signal to migrate existing recurring customers to ACH, even with some pushback.
• If you take B2B payments over a few thousand dollars, default to ACH. Card networks often surcharge large transactions (ReliaBills adds an extra 0.15% on card transactions over $1,000), and a five-figure chargeback isn’t something you want exposed on a card.

Most businesses end up running neither permanently rather than picking one. That’s not indecision; it’s correctly matching the payment method to the moment in the customer relationship.

Common Mistakes Businesses Make With This Decision

• Treating it as either/or. The businesses with the cleanest cash flow accept both and let the customer’s situation dictate which gets used, rather than forcing one method company-wide.
• Not retrying failed ACH the same way they retry failed cards. Returns need their own retry and notification logic. Treating a return identically to a declined card gets worse results because the underlying reasons differ.
• Underestimating settlement time in cash flow planning. If working capital is tight, a 3-day ACH window versus a 1-day card window is a real difference, not a rounding error.
• Ignoring the large-transaction card surcharge. Several processors, including ours, add a percentage on card transactions over $1,000. If your invoices routinely exceed that, this alone can justify pushing customers toward ACH.

How This Applies to Recurring and Installment Billing

If your business runs on recurring billing rather than one-off sales, this decision compounds every cycle. A 3% card fee on a $200/month client isn’t a one-time cost, it’s $72 a year for as long as that customer stays. That’s why platforms like ReliaBills let you store both card and bank payment methods on file and switch a customer’s default without re-running the signup flow.

The same logic applies to installment billing for larger purchases. When collecting a fixed total across several payments, say a $3,000 service split into six $500 installments, ACH’s flat fee protects your margin in a way a percentage fee can’t, since that fee gets paid six separate times either way.

For more on how recurring billing logic and failed-payment handling fit together, our subscription and recurring billing guide covers the setup side in detail.

Frequently Asked Questions

1. Is ACH cheaper than credit cards for every business?

Not at every transaction size. ACH’s flat fee usually beats a card’s percentage fee above roughly $30 to $40 per transaction. Below that, card fees can come out cheaper.

2. Can I require ACH instead of offering a credit card option?

Yes, especially for B2B and recurring contracts, but expect some friction at signup. Conversion is usually lower if ACH is the only option from the first payment.

3. What happens if an ACH payment is returned?

The funds aren’t deposited, and you’re typically charged a return fee (on ReliaBills, $20). Unlike a chargeback, a customer can’t dispute an ACH debit over buyer’s remorse, only for specific reasons like an unauthorized debit or insufficient funds.

4. Should new businesses start with credit cards or ACH?

Start with cards for acquisition, since customers are more comfortable handing over a card than bank details upfront. Layer in ACH once you have repeat customers or recurring billing, where the cost and retention benefits outweigh the signup friction.

Bottom Line

There’s no universal winner here, and any article that tells you there is hasn’t looked at enough merchant accounts. Credit cards win at the point of acquisition because customers trust them and authorization is instant. ACH wins over the life of a recurring relationship because the fee structure is flat, bank accounts don’t expire the way cards do, and the dispute process is narrower. The businesses that protect their margins best aren’t the ones that pick a side. They accept both, default new customers to cards, and migrate recurring and high-ticket accounts to ACH once trust is established. That single shift, timed correctly, is usually worth more to your bottom line than any other billing decision you’ll make this year.

Recent Articles:

• How to Automate Installment Payments and Eliminate Manual Follow-Ups
• How to Automate Rent Collection and Save Hours Every Month