The complete guide to ACH vs card processing cost

Why ACH vs card processing cost is worth understanding

Every time a customer pays you, a small slice of that payment goes to moving the money. The size of that slice depends heavily on the rail you use. Comparing ACH vs card processing cost is one of the quickest ways to find money you are quietly leaving on the table, especially if you handle large invoices or recurring billing.

The confusion is understandable. Card pricing and ACH pricing are built on completely different foundations, so a straight number-to-number comparison rarely tells the whole story. This guide walks through how each is priced, when one clearly beats the other, and why settlement speed belongs in the same conversation.

How is card processing priced?

Card pricing is layered. At the bottom sits interchange, the fee set by the card networks and paid to the bank that issued your customer's card. On top of that are network assessments, and then your processor's margin. Most small and midsize businesses never see those layers broken out. They see a blended rate instead.

A common, transparent way to quote cards is a flat rate. Flux, for example, charges 2.9% plus 30 cents per transaction with no setup fees, monthly fees, minimums, or contracts. The percentage matters because card cost scales with ticket size: a 2.9% rate on a 50 dollar order is about 1.75 dollars, but the same rate on a 5,000 dollar invoice is 145 dollars plus the flat 30 cents.

For higher volume, that percentage is negotiable. Flux offers volume discounts and custom interchange-plus pricing once you are processing enough to justify it, which unbundles interchange from margin so you can see each layer.

How is ACH priced, and why is it flatter?

ACH moves money directly between bank accounts over the automated clearing house network. It never touches the card networks, so there is no interchange to pay. In the wider market that usually shows up as a small flat fee per transfer rather than a percentage, which is why ACH cost tends to stay steady no matter how large the payment is.

That single difference reshapes the math. On a large invoice, a percentage-based card fee grows with the ticket, while a flat ACH fee does not move. For B2B invoicing, rent, tuition, wholesale, or any high-ticket recurring charge, that gap compounds fast across a year.

When does each rail win?

Cards win on convenience and immediacy. Customers expect to type a card number at checkout, and card rails support instant authorization, which matters for e-commerce, in-person sales, and anything impulse-driven. Cards also carry familiar dispute and chargeback protections that some buyers value.

ACH wins on cost for large and predictable payments. If you send invoices, collect memberships, or bill the same customers month after month, steering those payments to ACH can meaningfully lower your blended processing cost. The tradeoff is that ACH is slower to settle and clear.

Many businesses do not pick one. They offer both and let the transaction decide: cards for small or one-time purchases, ACH for large or recurring ones. Running both on a single platform, as Flux does with cards, ACH, and stablecoins together, keeps that from becoming an operational headache.

Settlement speed is part of the cost

Price per transaction is only half the picture. How fast the money lands affects your cash flow, and cash flow has its own cost. Cards on Flux settle in 1 to 2 business days. ACH settles in 1 to 3 business days. Stablecoins, a third option, settles to the merchant wallet instantly.

If you are choosing a rail partly to protect working capital, weigh the fee against the wait. A slightly cheaper rail that ties up funds longer is not always the better deal for a business with tight cash cycles.

A quick way to decide

Start by segmenting your payments by size. Anything small, one-time, or impulse-driven usually belongs on cards. Anything large, recurring, or invoice-based is a strong ACH candidate. Then layer in speed: if you need money fast on a specific payment type, factor settlement timing into the comparison.

Finally, look at whether you can pass the fee along. Flux lets you pass the processing fee to the customer at checkout where local surcharging rules allow, which changes who absorbs the cost rather than what it is. Model your real transaction mix before committing, because the right answer is specific to your ticket sizes and billing patterns.