ACH and Credit Card Processing: Run Both With One Provider
Payment Processing Fundamentals

ACH and Credit Card Processing: Taking Both With One Provider

ACH and credit card processing can share one provider. See how underwriting, return windows, pricing and reconciliation differ, with a worked cost example.

Wicker basket overflowing with paper receipts beside a calculator, pen and grid notebook on a dark desk

Photo: Pixabay

On this page 8 sections
  1. Why Keep Cards When ACH Costs Less
  2. How One Provider Handles ACH and Credit Card Processing
  3. The ACH Rule Owners Get Wrong: How Long a Debit Can Come Back
  4. Two Risk Reviews on One Application
  5. Steer Big Invoices to ACH Without Losing Card Payers
  6. What Each Rail Costs at Your Invoice Sizes
  7. Reconciling Card Batches and ACH Settlements in One Report
  8. Questions to Ask Before You Sign

Key takeaways

  • The account being debited sets the ACH return window. If a "business" customer pays from a personal checking account, a disputed debit can come back weeks later.
  • Visa's commercial-card discounts now depend on CEDP data quality, and Level 2 data alone no longer earns a lower Visa rate. Check this before you assume cards are cheap on B2B invoices.
  • Set your ACH-first threshold from your own invoice history. Each large invoice that moves to ACH saves close to the full card fee.
  • ACH payments that customers push from their own bank never pass through your processor, so plan to match them by hand in accounting.

Yes, you can run ACH and credit card processing through one provider, with one application, one gateway and one payment page for your customers. The provider can't make the two rails follow the same rules, though. Card payments run under Visa and Mastercard network rules. ACH debits run under the Nacha Operating Rules. Each gets its own underwriting review, pricing model and settlement schedule. A combined setup works when you plan around those differences and causes trouble when you assume one account means one set of rules.

Firms that bill by invoice get the most out of it: law offices, IT consultancies, wholesale distributors and roofing contractors. They keep cards open for customers who want them and steer large invoices to ACH, where the fee stays flat as the invoice grows. If you're still deciding which rail is better, start with our comparison of ACH vs. credit card payments on cost, speed and risk. The rest of this piece covers how to run both well.

Why Keep Cards When ACH Costs Less

Card fees are mostly a percentage of the sale, so a card payment costs more as the invoice grows. ACH, the Automated Clearing House network that moves bank-to-bank transfers in the U.S., is usually priced as a flat fee per payment or a small percentage with a cap. Collecting a five-figure invoice by ACH costs about the same as collecting a small one.

Your customers are the reason to keep cards. Many wholesale buyers pay suppliers through a corporate card program. Homeowners paying a contractor's deposit may want card protections or rewards. Members on a monthly plan often won't hand over a routing number. If you drop cards, some of those customers will pay late or grudgingly. If you offer both, the customer still chooses, and you decide which choice is easiest.

The mix depends on the business. Professional services firms bill a steady run of mid-size retainers. Construction and contracting businesses bill deposits and progress draws that reach five figures. Subscription businesses collect many small recurring charges. Contractors gain the most from ACH's flat cost. Subscription businesses gain the most from having both rails in one recurring-billing system.

How One Provider Handles ACH and Credit Card Processing

A combined provider is really two products under one gateway. Card transactions run through a merchant account sponsored by an acquiring bank and travel over the Visa, Mastercard, American Express and Discover networks. ACH debits go out through a bank that sponsors you on the ACH network. That bank is called the originating depository financial institution (ODFI), and it answers to the rules written by Nacha, the network's governing body.

The provider adds the layer on top: one gateway that stores card and bank details as tokens, plus the hosted payment page and reporting that run off it. You can also use two separate providers. Then you have two logins, two deposit streams and saved payment methods in two places, and you reconcile between them every month. For a closer look at that software layer, see our guide to the types of payment processing software and which one you need.

For most small and midsize businesses, integration decides the question. If your invoicing or accounting software connects to one ACH and card payment processor for both rails, use that one. Our guide on how to choose a payment gateway provider covers what to check, and MannyPay's payment gateway options list the platforms it works with.

The ACH Rule Owners Get Wrong: How Long a Debit Can Come Back

Owners hear that ACH has no chargebacks and assume a bank payment is final once it lands. It isn't. Under Nacha rules, most returns must be sent within two banking days of settlement, including returns for insufficient funds and closed accounts. Unauthorized debits from consumer accounts are different. They can come back up to 60 calendar days after settlement. The unauthorized-return code for business accounts keeps the two-day window.

What decides the window is whose account you debit, not what you sold. Suppose a sole proprietor pays your $8,000 invoice from a personal checking account and later tells the bank they never authorized it. That payment falls under the consumer timeline, even though the sale was B2B. A return pulls the money back out of your account, and providers usually charge a return fee as well. Our explainer on ACH settlement, funding and return timelines walks through the full schedule.

Nacha also watches return rates. According to Oscilar's summary of the rules, unauthorized returns have a 0.5% threshold, and going over it can lead to Nacha's enforcement process. Administrative returns (bad account data) have a 3% level, and returns for any reason have a 15% level. Going over those two triggers an inquiry rather than a violation. Your sponsoring bank tracks all three, so sloppy authorizations put the whole ACH relationship at risk.

Monitoring is tightening in 2026. Nacha's fraud-monitoring rules took effect for all ODFIs and the largest originators on March 20, 2026. On June 19, 2026, they extend to all other non-consumer originators and third-party processors. That second phase covers ordinary businesses that send ACH debits. Expect your provider to ask more questions about how you collect and verify bank details.

Two Risk Reviews on One Application

Even on a single application, expect two reviews. The card review looks at what you sell, your ticket sizes, your refund and chargeback history, and how much of your volume is keyed or recurring. The ACH review focuses on exposure, because of the return windows above. ACH approvals usually come with:

  • A per-transaction limit, which needs to cover your largest normal invoice.
  • Daily and monthly volume caps.
  • A funding delay or reserve on new accounts while return windows are open.
  • Ongoing return-rate monitoring against the Nacha thresholds.

Card approvals carry limits too. If your card account was approved for a modest high ticket and a customer pays a much larger invoice by card, expect that payment to be reviewed or held. Our article on why large card transactions get held explains why. Put your real invoice range on the application for both rails. Merchants who understate it to get approved faster are the ones who end up with frozen funds.

Steer Big Invoices to ACH Without Losing Card Payers

The invoice and payment page are where you steer customers. Make bank payment the easiest option on large invoices and keep cards available.

  1. Show ACH first above a set amount. Most invoicing tools let you choose which methods appear and in what order.
  2. Let customers save their bank account. With authorization on file, the second invoice is a one-click payment, and repeat convenience is what keeps customers on ACH.
  3. Capture and store authorization. Every ACH debit needs the customer's authorization. Your portal should record it so you can produce it if a debit is disputed inside that 60-day consumer window.
  4. Pass card costs only where permitted. Visa caps a credit card surcharge at 3% or your actual cost of acceptance, whichever is lower, and debit and prepaid cards can't be surcharged. Mastercard's merchant surcharge FAQ ties the cap to your cost of Mastercard acceptance and requires 30 days' advance written notice to Mastercard and your acquirer. Some states add their own limits. Read our breakdown of Visa and Mastercard surcharge caps, signs and registration, see how to pass credit card fees to customers on B2B invoices, and review MannyPay's compliant surcharging program. Confirm state law with a qualified professional before you turn it on.

Recurring billing gains the most from a shared portal. When a member's card expires, they can switch to bank payment on the same page, and you keep one schedule instead of rebuilding it with a second provider. Phone payments need their own plan, because card numbers keyed in by staff cost more and draw scrutiny, as covered in keyed transaction fees and reviews. Ask whether your virtual terminal also accepts bank details so staff can offer ACH during the call.

What Each Rail Costs at Your Invoice Sizes

Card pricing on a combined account works the same as anywhere else. The networks set interchange and network fees, and your provider adds its markup. B2B sellers should check their commercial-card assumptions. Visa launched its Commercial Enhanced Data Program (CEDP) on April 12, 2025, with a 0.05% participation fee on CEDP transactions. Legacy Level 3 interchange ended October 17, 2025, and Level 2 ended in April 2026, so Level 2 data alone no longer earns a lower Visa rate. Our explainer on Level 3 processing after Visa's CEDP covers what still qualifies.

ACH pricing is set by each provider, not by a network rule. Common structures are a flat fee per payment or a capped percentage, plus monthly and return fees. Compare total cost at your actual invoice sizes rather than the advertised rate.

The example below is illustrative. The fees are assumptions chosen for the arithmetic, not quotes from MannyPay or any other provider. Assumptions: 240 invoices a year, of which 60 average $10,000 and 180 average $2,000. Cards cost 3% all-in. ACH costs $1 per payment plus a $180 annual fee. Returns are left out.

ScenarioCard feesACH feesTotal cost
Every invoice paid by card$28,800$0$28,800
The 60 large invoices move to ACH$10,800$240$11,040

Moving the largest quarter of invoices to ACH saves $17,760, about 62% of the all-card cost. The savings track how many customers switch: each $10,000 invoice that moves saves $299 in card fees ($300 minus the $1 ACH fee), before the annual fee. The other 180 customers keep paying however they like.

The example doesn't count return risk. If one of those $10,000 debits came back as unauthorized from a personal account seven weeks later, the cost would be the $10,000 plus a return fee, not the $1. That's why the authorization step above matters more on large invoices. Set your ACH-first threshold where card fees become meaningful, and leave small payers alone.

Reconciling Card Batches and ACH Settlements in One Report

The two rails fund on different schedules. Card transactions are grouped into batches, usually closed daily, and each batch arrives as one deposit. Depending on your setup, it comes in net of fees or gross, with fees billed monthly. ACH settles per payment or per day on its own schedule, and a return can show up weeks later as a debit against an invoice you already marked paid.

A useful combined report shows each payment with the invoice number, customer, rail, gross amount, fees, net amount and deposit date. It should tie each bank deposit to the payments inside it and flag returns against the original invoice. If your books are in QuickBooks, check MannyPay's QuickBooks integration first.

One gap stays open whichever provider you choose. Larger customers often push an ACH credit from their own bank. That money goes straight into your account and never passes through your processor, so it won't appear in the processor's report. Ask those customers to put the invoice number in the remittance details, match those payments in accounting, and reopen any invoice hit by a return right away so your accounts receivable aging report stays accurate.

Questions to Ask Before You Sign

Get written answers from any ACH and credit card processing company you're considering:

  1. Is ACH under the same agreement and gateway as cards, or is it a partner's product?
  2. What per-transaction and monthly ACH limits will I get, and do they cover my largest invoice?
  3. How many days until ACH funds reach my account, and is there a reserve for new accounts?
  4. What does each return cost, how am I notified, and how do you validate bank accounts entered online?
  5. What will you need from me under Nacha's 2026 fraud-monitoring rules?
  6. Does one report show both rails, with returns linked to the original payment and synced to my accounting software?

Before you call anyone, export last year's invoices and sort them by amount. Count how many fall above the point where a 3% card fee starts to hurt. That number sets your ACH-first threshold and the limits you need to ask for. If you haven't set up bank payments yet, start with how to start accepting ACH payments. To have a specialist review your card setup against that invoice data, request a free quote from MannyPay. A specialist responds within one business day.

Sources

  1. ACH return codes: A complete guide for businesses (Plaid)
  2. ACH Return Codes Explained: R01, R02, R10 and More (Oscilar)
  3. Risk Management Topics: Fraud Monitoring Phase 2 (Nacha)
  4. MAY-19 U.S. Merchant Class Settlement: Mastercard Frequently Asked Questions
  5. Visa Surcharge Rules (Stax Payments)
  6. Everything You Need to Know About Visa CEDP (NMI)
  7. Visa CEDP Explained (Evolve Payment)

About the author

Adrian Reyes

Adrian Reyes is Senior Payments & Fintech Editor for Beyond the Swipe, covering credit card processing, merchant accounts, payment technology and processing fees.

This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.

Related reading