ACH vs credit card fees for B2B invoices: the real math.

Is ACH cheaper than credit cards for B2B invoices? Yes — usually by a factor of twenty or more on a typical invoice, because ACH is priced flat or capped while card fees scale with the amount. On a $5,000 invoice, ACH commonly costs between $0.25 and $5, while a commercial card runs roughly $135 in interchange alone before your processor's markup. That gap is the whole reason B2B billing teams care about payment rails. But the cheap rail isn't automatically the right rail for every payment, so let's work the numbers honestly.

The real math on a $5,000 invoice

Start with how each rail is priced. ACH is most often billed as a flat fee per transaction — typically $0.20 to $1.50 — or as a small percentage, roughly 0.5% to 1.5%, usually with a cap. Stripe's published ACH debit pricing, a useful public benchmark, is 0.8% capped at $5. Because of the cap, the fee stops growing with the invoice: a $5,000 payment and a $50,000 payment can both cost $5.

Cards price the opposite way. Interchange — the non-negotiable wholesale cost set by the card networks — is a percentage of the amount, and commercial cards (business, corporate, purchasing) sit at the expensive end. As of mid-2026, a card-not-present commercial transaction without enhanced data commonly carries interchange around 2.7% + $0.10, per Checkout.com's summary of US commercial interchange — and that's before assessments and your processor's markup.

So the $5,000 invoice looks like this:

• ACH, flat-fee pricing: $0.25–$1.50. Effective rate: about 0.01–0.03%.
• ACH, percentage-with-cap pricing: 0.8% would be $40, but the $5 cap kicks in. Effective rate: 0.1%.
• Commercial card, no enhanced data: about 2.7% + $0.10 = $135.10 in interchange alone, before markup.
• Commercial card with Level 2/3 enhanced data: qualifying enhanced-data rates run roughly 1.75–2.5% + $0.10, or about $88–$125 — a real discount, still far above ACH.

The headline: choosing ACH over an unoptimized commercial card on that one invoice saves about $130. Across a hundred invoices like it, that's $13,000 a year — which is why the rail decision belongs in your billing workflow, not in an afterthought. If you want to run your own volume through this math, use the effective rate calculator.

How ACH actually works when you invoice

ACH for invoicing is usually an ACH debit: your customer authorizes you to pull the payment from their bank account. The authorization — a signed form, a checked box on a payment page, or recorded consent — is the legal backbone of the transaction, so store it. Once you submit the debit, the payment moves through the ACH network in batches.

Timing and same-day ACH

A standard ACH debit settles in about one to two banking days. If you need money to move faster, Same Day ACH offers three daily submission windows that settle the same banking day. As of mid-2026 the Same Day ACH per-payment limit is $1 million, which comfortably covers most invoices; Nacha has approved raising it to $10 million effective September 17, 2027. Payments over the limit simply process for next-day settlement.

Returns, NSF, and the finality trap

Here's the part sellers underestimate: ACH settlement is not finality. There is no real-time authorization — the network doesn't check the balance before accepting the debit. If the account is short, the paying bank returns the payment (code R01, insufficient funds), and under Nacha return rules most such returns arrive within two banking days of settlement. So treat an ACH payment as provisionally paid until a few banking days pass — don't release high-value goods the moment the debit is submitted.

Unauthorized-payment claims have longer windows: a business account holder generally has two banking days to return a debit as unauthorized, while a consumer account holder has up to 60 calendar days. Compare that to card chargebacks, where disputes can surface months after the sale and drag through a formal evidence process. In B2B, where both sides are businesses with a paper trail, ACH's return risk is usually smaller and shorter-lived than card dispute risk — one more point in ACH's favor for invoice work.

When cards still win

If ACH were strictly better, every invoice would be bank-to-bank already. Cards persist in B2B for reasons that are rational on the buyer's side of the table:

• Rewards pressure. Corporate and purchasing cards pay rebates and points. An AP team earning 1%+ back has a standing incentive to put your invoice on the card — and some will pay faster if you let them.
• Instant authorization. A card approval tells you now that the payment went through. ACH gives you no such signal — you find out it failed when the return lands days later.
• Buyer cash flow. A card gives the buyer weeks of float before their statement is due. For a cash-tight customer, "put it on the card" may be the difference between paying you today and paying you in 45 days.
• Familiar dispute mechanics. Some buyers simply trust the card networks' dispute process for large purchases from newer vendors.

The compromise that keeps cards viable for B2B is Level 2/3 enhanced data. By passing extra fields — tax amount, customer code, line items — a commercial card transaction qualifies for materially lower interchange, cutting the $135 in our example to roughly $88–$125 depending on the card and data level. (The networks are actively reshaping these programs: Visa began migrating Level 2/3 into its Commercial Enhanced Data Program across late 2025 and 2026, rewarding verified enhanced data with the best rates.) If a buyer insists on a card, enhanced data is how you say yes without eating the full commercial rate — see the full B2B credit card processing guide for how qualification works.

Which rail for which payment: a decision table

The honest answer to "ACH or card?" is "it depends on the payment." Here's the pattern that falls out of the math:

If card fees are eating you on the payments that must stay on card, start with how to lower credit card processing fees — pricing model and data quality move the number more than most merchants expect.

Offer both, route to the cheaper rail

The operational trick is not choosing a rail once — it's putting both on every invoice and letting each payment land on the right one. That usually dies on vendor sprawl: one provider for cards, another for ACH, two portals, two reconciliation exports.

Lifted Payments runs both rails under one merchant relationship: card processing on the Maverick gateway and ACH/eCheck on the NMI gateway, with automatic Level 2/3 data on commercial cards. An invoice can offer bank payment and card side by side, the payment routes to whichever rail the buyer picks, and everything reconciles in one merchant portal — transactions, customers, cards on file, reports. Pricing is interchange-plus, quoted after we read one recent statement, with no application fee — see merchant services for the full picture.