ACH and
credit card
processing.

01 / Understand the two rails

ACH and credit card processing.
Two ways to get paid. Different jobs to do.

A customer wants to pay a $5,000 invoice. Another wants to buy a $50 product on their phone. Offering both bank payments and cards can make sense—but the economics and operating rules are different.

ACH processing moves money between bank accounts through the Automated Clearing House network. Credit card processing handles a purchase through a card issuer, card network, and the merchant’s acquiring relationship. You may see the phrase “ACH credit card processing,” but ACH is not a type of credit card. It is a separate payment method that a business can offer alongside cards.

ACH payments can be credits, where the payer initiates a payment to the recipient, or debits, where a business initiates a collection with the account holder’s authorization. Nacha governs the network’s operating rules; banks, providers, and ACH operators carry out the payment process. This guide focuses mainly on merchant collections through ACH debits. [1]

A debit card purchase is also distinct from an ACH debit. Even though both can ultimately draw on a bank account, entering or tapping a debit card routes a card payment. Entering bank details in an ACH checkout uses bank-payment infrastructure. Likewise, a processor may pay out your card sales to your bank through ACH; that does not turn the original customer purchases into ACH payments.

For the account relationship behind bank collections, start with our ACH merchant accounts guide. Here, we compare ACH with cards so you can design the payment mix around your business.

02 / The side-by-side view

ACH vs. credit card processing at a glance

Neither method wins every purchase. Compare the experience and the obligations together.

Payment terminology varies between providers. Ask for an example transaction showing what each dashboard status means and when you can safely move to your next operational step. A “submitted” status is not the same promise as money available for payroll. The timing differences below are grounded in network and provider documentation. [2] [3]

03 / Follow the full cost

ACH processing fees vs. credit card fees

The transaction price matters. So do the costs around the transaction.

ACH quotes may use a fixed fee, a percentage, a capped percentage, or a combination. A cap can make a large difference on larger invoices, but it is a contractual feature—not a rule of the ACH network. Provider schedules can also include monthly minimums and charges for returned items. Authorize.net’s published eCheck pricing illustrates why reviewing several fee categories is necessary. [4]

For cards, the merchant’s total price depends on the agreement and transaction characteristics. A flat-rate quote bundles costs differently from an interchange-plus quote. Visa distinguishes the interchange exchanged between participating financial institutions from the merchant discount negotiated with the merchant’s financial institution. A published interchange table therefore is not your complete processing quote. [5]

What a cap changes: an illustrative comparison

Assume a hypothetical card price of 2.9% + $0.30 and a hypothetical ACH price of 0.8%, capped at $5 per payment. These inputs explain the arithmetic. They are not market averages, a NUMUS offer, or a prediction of your approved terms.

The larger invoice produces a larger modeled difference because the example ACH fee stops increasing at its cap. Without that cap, the $5,000 ACH fee at 0.8% would be $40. Change the assumptions and the conclusion changes.

Compare the monthly operation, not one ideal transaction

Include the monthly account and software charges, bank-validation costs, unsuccessful payment fees, refund treatment, return or dispute charges, and any faster-funding service. Then account for collection work: a lower fee does little for an invoice that remains unpaid or a customer who abandons an unfamiliar checkout.

Separate processing expense from cash held in reserve. A reserve affects working capital; it is not automatically a permanently lost fee. Ask how it is calculated, when it may be released, and what obligations can extend it. Compare proposals for the same transaction mix and fulfillment model.

Use the comparison calculator below for a planning scenario. For your existing card statement, our credit card processing fee calculator and processing fees guide help you examine the broader cost picture.

04 / Know which clock is running

Authorization, settlement, and payout are different milestones

“How fast do I get paid?” needs a more precise answer than “ACH takes days” or “cards are instant.” There are several clocks between checkout and money you can use.

1. Permission and initiation. The customer agrees to pay, and the payment instruction is accepted. For a card, issuer authorization commonly reserves available spending capacity; capture completes the merchant’s request to collect. Authorization can expire if capture does not occur in the applicable window. [3]
2. Network processing and settlement. Instructions and funds move through the relevant financial system. Eligible Same Day ACH transactions can settle on the processing day when deadlines and requirements are met. This is a network service, not a blanket promise that every merchant receives spendable money that day. [6]
3. Provider availability and payout. Your provider determines when proceeds are available under your agreement and sends a payout on its schedule. For example, Stripe documents ACH balance-availability timing separately from the payout that subsequently reaches the merchant’s bank. Its timetable is a provider example, not a universal ACH rule. [2]
4. Later adjustments. A payment can still produce a return, dispute, refund, or contractual debit after proceeds have appeared. Settlement alone does not remove all future payment risk.

Before promising delivery, ask your provider which milestone your system uses. A wholesale seller might hold a new buyer’s shipment pending its agreed payment review. A recurring service might have a documented grace period. An instant digital product needs a different risk decision.

05 / Make permission explicit

Bank validation and payment authorization do different things

A working account number does not, by itself, give a merchant permission to collect. Nor does a customer’s agreement guarantee an adequate balance on the collection date.

For consumer ACH debits initiated online, Nacha’s WEB debit rule requires account-number validation before first use and after an account-number change, as part of a commercially reasonable fraud-detection system. Validation methods differ in what they establish. Do not assume every account check also proves ownership or verifies available funds. [7]

The authorization must match the collection arrangement. Is it one payment, a recurring schedule, or a later payment the customer separately initiates? Is the account a consumer or business account? Was permission collected online, by telephone, or in writing? These details affect the appropriate Standard Entry Class code and supporting records. Nacha’s developer guide explains the distinctions among common entry types. [8]

Recurring payments deserve a complete customer experience

Show what is being charged, how the amount is determined, the timing, and how the customer can cancel or change the arrangement. Make receipts and support easy to find. For covered preauthorized transfers from consumer accounts, Regulation E requires written or similarly authenticated authorization and a copy for the consumer. Your provider should help implement the applicable requirements for your payment flow. [9]

For card subscriptions, explain the recurring terms and use the provider’s supported stored-credential setup. Keep cancellation instructions as accessible as enrollment. A merchant should be able to reconstruct why a particular customer was billed on a particular date.

A useful operational record connects the invoice or order, authorization, payment reference, customer communication, and any later change. Restrict access to sensitive data and use the provider’s supported collection and storage tools. Avoid turning a shared spreadsheet or ordinary email inbox into your payment-data vault.

If a representative collects instructions by phone, use the approved telephone workflow. A rep typing a customer’s information into a website does not automatically make the authorization appropriate for that website’s self-service flow.

06 / Plan for exceptions

ACH returns and card chargebacks need different playbooks

ACH can reduce modeled transaction expense without eliminating collection risk. Incorrect account information, insufficient funds, account restrictions, and authorization problems can all interrupt a payment. Cards bring their own declines and dispute processes.

There is no universal “ACH is final after two days” rule

Timeframes depend on the account, return reason, and applicable rules. Nacha describes an extended network return timeframe for unauthorized consumer debits tied to 60 calendar days after settlement, while unauthorized non-consumer debit returns generally must be made available to the originating bank by the opening of the second banking day after settlement. The same source distinguishes automated returns from warranty claims. Treating either window as the end of every possible claim would be misleading. [10]

Card disputes follow the relevant network and acquiring procedures. Evidence requirements and response options vary by dispute condition. Visa’s merchant guidance discusses transaction documentation and dispute management; an approval code alone is not a substitute for evidence that the merchant fulfilled the purchase as agreed. [11]

Build a return queue, not an automatic retry loop

Assign someone to review failures daily, identify the reason, contact the customer appropriately, and record the resolution. An insufficient-funds return, a closed account, and a revoked authorization should not trigger identical actions. Reinitiation is subject to specific rules; configure retries with the provider rather than repeatedly resubmitting every failed collection. [12]

Fraud monitoring also deserves an explicit owner. Nacha’s 2026 Phase 2 expansion requires covered non-consumer originators, third-party service providers, and third-party senders to implement risk-based procedures relevant to their roles and review them at least annually. Nacha identifies June 22, 2026 as the practical effective date because June 19 was a federal holiday. [13]

For a merchant, sensible discussion points include unusual ticket sizes, sudden volume changes, bank-detail changes, multiple attempts, and fulfillment delays. Confirm which controls the provider operates and which your team owns. Businesses with complex fulfillment, elevated returns, or restricted products should review our high-risk ACH processing guide before selecting an arrangement.

07 / Match the method to the sale

When ACH, cards, or both make business sense

The examples below are planning scenarios. Suitability depends on customer preferences, provider acceptance, transaction history, and your ability to manage payment exceptions.

B2B and larger invoices

ACH is worth evaluating for established customers paying larger invoices, especially where a quoted fee cap changes the economics. Some businesses prefer initiating an ACH credit from their own accounts-payable system; others approve a merchant-initiated debit. Confirm the method rather than labeling both “bank transfer” and assuming the workflow is identical.

Keep cards available where buyers need purchasing-card controls or prefer that checkout. For a $5,000 order, compare the complete cost, the buyer’s ability to pay, and the shipment decision. Saving a processing fee is not helpful if the payment method delays an otherwise profitable purchase.

Subscriptions and repeat services

An ongoing customer relationship can support a deliberate bank-payment enrollment process. ACH avoids card expiration as a credential issue, but bank accounts can close or change and authorizations can be revoked. Build reminders, a cancellation process, and a path to update payment details.

Offer the appropriate alternative when a customer cannot use the first method. Do not silently charge a different saved method without the necessary agreement. Evaluate successful collection over the whole billing cycle, including support effort and recoveries, rather than comparing the first attempt alone.

Ecommerce and immediate fulfillment

Cards can fit a fast retail checkout, while ACH may suit repeat buyers or larger planned orders. The important design question is what the store does while a bank payment is pending. Keep payment, order, and shipping states distinct so warehouse staff do not interpret “order received” as unrestricted approval to ship.

Our ecommerce merchant account guide explores the surrounding checkout and scaling decisions. Test the complete journey on mobile, including a failed payment and a refund, before offering a new method broadly.

Nonprofits and recurring donors

Bank payments can be a useful option for donors who choose ongoing contributions, alongside cards for other giving preferences. Make authorization, acknowledgment, cancellation, and donor support part of the experience. Compare the full fundraising platform and processing arrangement; a low payment fee can coexist with other platform costs. See our nonprofit ACH guide for a more specific planning worksheet.

08 / Build a setup that can operate

How to accept ACH and credit card payments together

You may be able to use one customer-facing platform for both methods, but ask whether ACH requires separate underwriting, activation, limits, or terms. One login does not necessarily mean one agreement or one payout.

1. Describe the actual business. Prepare the legal entity, website, products, customer locations, average and largest tickets, expected monthly volume, recurring activity, and time between payment and delivery.
2. Confirm acceptance and limits. Get written confirmation that the proposed arrangement supports your business model, payment channels, and expected transaction sizes. Disclose future-delivery obligations and existing processing problems.
3. Compare the complete terms. Review fees, funding, reserve provisions, return handling, support, termination terms, and any separate software agreement. Use the same assumptions for each proposal.
4. Build authorization and security into checkout. Use approved payment components and configure the correct collection flow. Outsourcing card handling can reduce applicable PCI requirements, but it does not remove the merchant’s responsibility to manage provider compliance and shared responsibilities. [14]
5. Test the operating exceptions. Walk through pending ACH, failed verification, card decline, duplicate submission, cancellation, refund, return, and interrupted checkout. Confirm that each reaches the right person.
6. Reconcile and expand deliberately. Match sales to payments, fees, adjustments, and actual deposits. Review early results before moving a large recurring customer base or increasing ticket sizes.

A useful reconciliation report keeps gross sales, payment status, processing fees, refunds, returns or disputes, reserve movements, and net payouts in separate fields. Combining those into a single “revenue” number makes problems harder to diagnose.

09 / Bring better questions

Ask a provider these questions before you sign

• Business fit: Can you support our exact products, sales channels, delivery timing, and customer locations on both methods?
• Approval: Are ACH and cards reviewed separately, and what volume or ticket limits apply?
• Real cost: What will this transaction mix cost after monthly fees, validation, refunds, failed payments, and disputes?
• Cash flow: What are the cutoffs, payout schedule, reserve provisions, and possible funding holds?
• Customer permission: Who provides the authorization language, stores evidence, and handles revocation?
• Failures: Which statuses should stop fulfillment, and who reviews returns, retries, and disputes?
• Operations: Can our team reconcile both methods to invoices and deposits without manual guessing?
• Future changes: What happens to saved payment credentials and authorizations if we change providers?

Ask the provider to demonstrate the answers with your billing scenario. A monthly subscription, a phone order, and a large invoice are three different workflows even when the same payment button appears on the screen.

11 / Common questions

ACH and credit card processing FAQs