High-risk payments guide
ACH vs Credit Card Processing: Cost, Speed, and Risk
One rail is cheap and slow, the other is instant and expensive. Most high-risk businesses need both, and knowing which payment belongs on which is where the money is.
ACH processing debits a customer’s bank account directly, while credit card processing runs the payment across the Visa and Mastercard networks. That single difference sets everything else. Cards confirm in seconds and cost a percentage of every sale. Bank debit costs far less on a big ticket but takes days to tell you whether the money is really there. For most high-risk businesses the honest answer is not one rail or the other. It is knowing which payments belong on each.
Key takeaways
- Cards authorize in real time. ACH has no live approval step, so a debit can fail days after you thought it cleared.
- ACH pricing is usually capped, card pricing is usually a percentage, so the cost gap grows with the size of the sale.
- ACH returns are not chargebacks. There is no representment process, and a disputed debit gives consumers 60 calendar days while business accounts get two business days.
- The ACH Network handled 35.2 billion payments worth $93 trillion in 2025, including close to 8.1 billion business-to-business payments (Nacha, 2026).
What is ACH processing?
ACH processing pulls money straight out of a customer’s bank account using their routing and account number. ACH stands for Automated Clearing House, the shared network that moves direct deposits, bill payments, and business-to-business transfers between US banks. You may hear the same thing called e-check, bank debit, or e-debit. They all describe one rail.
This is not a niche option. The ACH Network moved 35.2 billion payments worth $93 trillion in 2025, up nearly 5% in volume and almost 8% in value over the year before, and business-to-business volume alone grew close to 10% to roughly 8.1 billion payments (Nacha, 2026). Same Day ACH is growing faster still, reaching 1.4 billion payments worth $3.9 trillion.
The mechanics are simpler than card processing, and that is both the strength and the catch. There is no card network in the middle taking a cut. There is also no real-time approval. You collect a written authorization from the customer, called a mandate, then submit the debit and wait.
What is credit card processing?
Credit card processing sends the sale to the customer’s card issuer for a live decision. The issuer checks the account in real time and returns an approval or a decline in a couple of seconds. That instant answer is what lets you ship a product or unlock an account the moment someone clicks buy.
You pay for that certainty. Card pricing is built on interchange, the fee the issuing bank keeps on every transaction, plus network fees and your processor’s margin. Published card rates make the shape clear. Stripe lists 2.9% plus 30 cents for a standard domestic card sale against 0.8% capped at $5.00 for bank debit (Stripe, 2026). Those are one platform’s public numbers, not a quote, but the structure holds across the industry.
The other cost is dispute exposure. A card sale can come back as a chargeback months later, with a fee attached and a mark against the ratio your processor watches. That risk is a large part of why some businesses get labeled high risk in the first place.
ACH vs credit card processing: the differences that matter
Side by side, the two rails trade off speed, cost, and how much control you keep after the money has moved.
| ACH / bank debit | Credit card | |
|---|---|---|
| How it moves | Debit against a bank account | Authorization on the card networks |
| Confirmation | Days, not seconds | Real time at checkout |
| Typical settlement | Up to 4 business days, or 2 where eligible | Next business day to a few days |
| Pricing shape | Often a low percentage with a cap | A percentage of every sale, plus a fixed fee |
| Reversal type | Return, under Nacha rules | Chargeback, under card network rules |
| Can you dispute a reversal? | No appeal process | Yes, through representment |
| Customer dispute window | 60 calendar days for consumers, 2 business days for businesses | Commonly 120 days |
| Best fit | Invoices, payment plans, high tickets, recurring pulls | Impulse buys, instant fulfillment, unfamiliar buyers |
Neither column is the winner. A rail that confirms in two seconds is worth its fee when you are shipping a $60 order to a stranger. A rail that caps its fee is worth the wait when you are collecting a $4,000 installment from a customer you already know.
Which rail costs less to run?
Bank debit almost always costs less per dollar collected, and the gap widens as the ticket grows. That is a pricing structure difference, not a discount. Card pricing scales with the sale because interchange is a percentage. Bank debit pricing is commonly capped, so the fee stops growing once the payment passes a certain size.
Run the published Stripe numbers on a single $2,000 invoice. At 2.9% plus 30 cents, the card fee is $58.30. At 0.8% capped at $5.00, the bank debit fee is $5.00 (Stripe, 2026). On a $40 order the two land much closer together, which is exactly why the rail you pick should follow your average ticket rather than a blanket rule.
Two honest caveats belong here. Bank debit has its own costs, including per-return fees when a debit fails, and a business with sloppy authorizations can spend the savings on returns. And what you actually pay depends on your account, not on a public rate card, which is why high-risk pricing gets quoted from your real processing numbers instead of a published table. On our own accounts, the bank-debit rail runs at $0 monthly fees, while card accounts carry low monthly fees and often none at all.
How fast does each rail actually pay you?
Cards give you certainty first and money shortly after. Bank debit gives you money later and certainty later still. That second point is the one that catches businesses out.
ACH settlement commonly runs up to four business days from when the payment is created, with a two-business-day option available to some merchants (Stripe, 2026). Same Day ACH compresses that further and can carry payments of up to $1 million in a single transaction, settling in a matter of hours (Nacha, ACH Payments Fact Sheet). Even then, a debit can fail after the fact. If the account was short, the return arrives days later and the funds come back out.
Cards behave the opposite way. The authorization tells you at checkout whether the money is available, and funding follows on your settlement schedule. What can reverse later is a dispute, not a failed pull. So the real question is not which rail is faster. It is which kind of uncertainty your business can absorb. A subscription box shipping same day needs the live approval. A B2B invoice due in 30 days does not.
ACH returns are not chargebacks
This is the single most misunderstood part of the comparison, and getting it wrong costs merchants real money. When an ACH debit fails, the bank sends back a return, not a chargeback. The two run on different rules, different clocks, and different consequences.
A return is a coded rejection of the debit. The common ones are plain facts about the account, such as not enough money, a wrong account number, a closed account, or the customer saying they never authorized the pull. On an ordinary return there is no evidence to submit and no panel to convince, though your bank can ask you for proof that the customer authorized the debit. The debit either stands or it does not.
The dispute windows are much tighter than cards, and they cut both ways. A consumer generally has up to 60 calendar days after the debit to dispute it, and a business account has only two business days. Inside those windows the decision is final, with no appeal process on the ACH network (Stripe, 2026). Compare that to a card chargeback, where cardholders typically get 120 days but you get a formal chance to respond with evidence (Stripe, How disputes work).
So bank debit removes the chargeback fee and the whole dispute apparatus, and replaces it with a shorter, blunter reversal you cannot argue. The difference between a bank reversal and a merchant-issued credit matters here in the same way the split between a chargeback and a refund matters on cards.
There is a ratio to watch on this rail too. Nacha sets an unauthorized return rate threshold of 0.5%, calculated over the trailing 60 days or two calendar months (Nacha, 2024). Cross it and your bank starts asking questions about how you collect authorizations. It is the bank rail’s version of a dispute ratio, and it deserves the same monitoring.
What customers expect at each checkout
Card is the default habit, and habits are hard to move. A shopper who wants something now reaches for a card without thinking about it. Asking that same shopper for a routing number, or sending them through a bank login, adds friction at the worst possible moment.
Bank debit works best where the buyer is not expecting instant gratification. Paying an invoice, funding a deposit, or setting up an installment plan all feel like bank transactions already, so the extra step reads as normal rather than suspicious. That is why bank debit converts well on B2B and payment-plan flows and poorly on impulse purchases.
Refunds feel different too. A card refund reverses the original charge, so the customer sees it tied to the purchase. A bank debit refund is a separate credit sent to their account, which does not show up as a reversal and can be genuinely hard for them to spot. Refund windows are long, commonly up to 180 days, and the credit takes a few business days to arrive (Stripe, 2026). Tell the customer when you send one, or you will get a support ticket asking where their money is.
Which rail should your business run?
Most businesses in this category should run both, and route each payment to the rail that fits it. Cards carry the front door, where speed and familiarity decide whether a sale happens. Bank debit carries the payments where fees compound, such as invoices, deposits, installments, and any pull that repeats against the same customer month after month.
Recurring revenue is where the split pays off most clearly. Cards expire, get reissued, and decline, which is why recurring billing needs a failed-payment recovery process behind it. Bank accounts change far less often, so a scheduled bank pull can be steadier than a card on file. Running both gives a customer a fallback when one fails.
There is one more reason bank debit matters for businesses in this space. Card acceptance is gated by the card networks, so a prior termination that put a business on the MATCH list blocks the card rail while the bank rail stays open. An ACH merchant account can keep revenue moving while card placement is still under review, which turns a shutdown from a full stop into a detour.
Two rails, one checkout
ACH and credit card processing are not competitors so much as different tools for different payments. Cards buy you a real-time yes at a percentage of every sale. Bank debit buys you a much lower cost on large and repeating payments, in exchange for waiting days to learn whether the money was there. Price both against your actual mix of ticket sizes and payment schedules, keep your authorizations clean so returns stay low, and put each payment on the rail that suits it. That is the version of this decision you control.
Frequently asked questions
- Is there an authorization step for ACH the way there is for a card?
- Not in the same sense. A card runs a real-time authorization, and the issuing bank approves or declines it in seconds. ACH has no live check against the account. You hold a written authorization from the customer, called a mandate, and you submit the debit. The bank tells you days later whether it went through.
- Do ACH returns count toward the chargeback ratio card networks watch?
- No. Visa and Mastercard measure disputes on card transactions, and an ACH return never enters that count. Bank debit has its own scoreboard instead. Nacha sets an unauthorized return rate threshold of 0.5%, so a business that debits accounts carelessly gets flagged on the bank rail rather than the card rail.
- Which rail is better for high-ticket sales?
- Bank debit usually wins on a large ticket, because card pricing is mostly a percentage of the sale while bank debit pricing is often capped. The gap widens as the invoice grows. The tradeoff is that you wait days for confirmation, so high-ticket bank debit suits invoices and payment plans more than it suits instant fulfillment.
- Will offering bank debit at checkout cost me card sales?
- It should not, because the two options sit side by side rather than replacing each other. Card stays the default for shoppers who want to buy in seconds. Bank debit appeals to buyers paying an invoice, a deposit, or a scheduled installment, where nobody expects instant fulfillment anyway.
- How do refunds work differently on ACH than on a card?
- A card refund reverses the original charge. A bank debit refund is a brand new credit sent to the customer account, so it does not appear as a reversal on their statement and can be hard for them to recognize. Refund windows are long, commonly up to 180 days, and the credit takes a few business days to land.