vs Cards on $50K+
Settlement
Supported
Integrated
Timeline
ACH and eCheck, a first-class Payment Hub method
ACH (Automated Clearing House) is the U.S. network that moves money directly between bank accounts, the same rails used for payroll direct deposit, tax refunds, and recurring utility bills. When a merchant accepts a payment via the ACH network rather than a credit card, the transaction typically costs 10–50x less per dollar on large tickets, doesn't expire like a card does, and settles in 1–3 business days (or same day, for a small fee). "eCheck" is the informal name for the web-initiated flavor of the same underlying rails.
For AR teams in B2B distribution, manufacturing, healthcare, nonprofit, education, government, professional services, and subscription businesses, that difference is one of the largest unit-economics levers available. But ACH only pays off if it's presented to customers cleanly, authorized correctly, tokenized securely, and wired into the ERP the same way card payments are. Most of what goes wrong with ACH acceptance comes from treating it as a separate off-to-the-side process rather than a first-class payment method in the checkout.
Clarity Payment Hub treats ACH / eCheck as one option among many in the same branded portal and checkout. Customers see a single "Bank Account" payment method, enter their routing and account number once (or pick from a saved token on repeat visits), and Payment Hub handles the NACHA SEC code selection, the authorization capture, the tokenization at your gateway's vault, the ERP posting, and the return-code handling, consistently across every supported gateway underneath.
The economics, ACH vs Card vs Net 30
Three ways to get paid on an invoice: the customer pays with a card, the customer pays via ACH, or you extend Net 30 terms and wait. The honest comparison by dimension:
| Dimension | Credit Card | ACH / eCheck | Net 30 Terms |
|---|---|---|---|
| Per-transaction cost (typical) | 2.0%–3.5% + ~$0.25 | ~$0.25–$1.00 + 0%–0.75% | 0% direct, but carrying cost, chase cost, write-off risk |
| Cost on $50,000 invoice | ~$1,000–$1,750 | ~$5–$380 | ~$200–$400 in carrying + chase cost (and potential default) |
| Time to funds | 1–2 business days | 1–3 business days (Same-Day available) | 30 days, if paid on time |
| Customer friction | Card number + CVV + expiration | Bank routing + account number (one-time, then tokenized) | None upfront, then invoice chase |
| Reversal / dispute risk | Chargeback exposure (120+ days) | Return codes, shorter window (60 days for consumer, 2 days for unauthorized business) | Bad debt / write-off risk |
| Recurring durability | Cards expire every 3–4 years. Account-updater services help but don't eliminate churn | Bank accounts rarely change. Recurring ACH runs for years without intervention | N/A (one-and-done collection) |
| Commercial-card Level 3 savings | Yes, with Payment Hub pulling line-item data from the ERP | N/A (ACH has flat pricing regardless of line-item data) | N/A |
| Best-fit use case | Small-ticket consumer flows, commercial cards with L3 on B2B up to a threshold | High-dollar B2B invoices, long-term recurring (tuition, memberships, sustaining gifts, enterprise SaaS) | Large-tenured B2B relationships where the customer won't accept ACH |
The card column isn't empty of wins, for smaller consumer flows and commercial cards where Level 3 interchange savings apply, cards are the right call. Payment Hub's routing policies let you express "cards up to $X, ACH above $X, with a surcharging option where permitted" in one configuration and apply it across every invoice automatically.
Replacing Net terms with authorized auto-debit
Net 30 is the most expensive payment method in B2B, not because of fees, but because of everything around it. The replacement pattern is simple: keep the timing, remove the chase.
Keep the 30-day timing
Customers used to Net 30 don't lose the 30 days. Payment Hub schedules the ACH debit for the invoice due date, 30 days out, or whatever your terms specify. The customer's cash flow doesn't change, yours does.
One-time authorization
At contract signing or first invoice, the customer authorizes ACH auto-debit on due date, electronic signature, click-to-authorize, or written mandate. Payment Hub stores the authorization audit trail to NACHA standards. Every subsequent invoice debits automatically.
DSO drops, AR staff time drops
Days Sales Outstanding compresses from "whenever the customer pays" to "due date + 1–3 business days." Collections calls drop to exception-only (NSF returns, not "where's my payment?"). Most Clarity customers see 30–50% reduction in AR labor on converted accounts.
Write-off risk falls significantly
The biggest hidden cost of Net 30 isn't carrying, it's the 2–5% of revenue that eventually writes off as bad debt. Authorized ACH auto-debit doesn't eliminate it entirely (NSF returns still happen), but because the customer pre-authorized the timing and amount, the collections story is much shorter and the recovery rate is much higher.
The customers most receptive to this conversion are typically your best customers: the ones with predictable payment patterns who already pay every invoice but hate getting chased. For the holdouts, customers who genuinely need flexibility month-to-month, Payment Hub can keep the customer portal open for them to pay manually by card or ACH on their own schedule, while everyone else runs on auto-debit.
The Missing LinkBetween Paymentsand Your ERP
Clarity Payment Hub closes that gap, connecting your orders, invoices, and payment channels into one flow.
Speak to a Platform ArchitectIndustries where ACH wins
ACH economics matter everywhere, but they matter most in verticals where invoice sizes are large or recurring relationships span multiple years. Payment Hub applies the right ACH pattern per vertical.
B2B Distribution &, Wholesale
High-dollar invoices on Net 15 / Net 30 / Net 45 terms, the single biggest ACH opportunity in the Clarity book. Convert Net terms to authorized auto-debit and reclaim the card-processing economics on the B2B ticket.
- ACH as default above a configurable dollar threshold
- Net 30 → auto-debit on due date
- CCD / CTX SEC codes for B2B transactions
- Real-time ERP posting on debit confirmation
Manufacturing
Milestone and progress billing with large deposits, balance-on-delivery payments, and dealer network invoicing, ACH dominates on every ticket above a few thousand dollars.
- Deposits and milestone payments via ACH
- Authorized auto-debit for service contracts
- Same-Day ACH for expedited delivery terms
- CTX for high-value B2B with addenda records
Healthcare &, Life Sciences
Patient payment plans (often 12–36 months) where a card-on-file will likely expire during the payment term. ACH durability keeps the plan running without re-authorization.
- Multi-year patient payment plans on ACH
- Practice-to-payer B2B reimbursement flows
- PPD SEC code for consumer-patient recurring
- Posting to practice management / ERP
Nonprofit &, Fundraising
Sustaining (recurring) giving on ACH has meaningfully lower attrition than on card, because bank accounts don't expire. The highest-lifetime-value donor cohorts are typically ACH sustainers.
- Recurring ACH for sustaining gifts (monthly / quarterly)
- Lower attrition vs card-on-file over multi-year horizons
- WEB SEC code for online donation authorization
- Fund-accounting GL posting with designation tracking
Education
Tuition payment plans, continuing-ed programs, and annual institutional fees, ACH for monthly auto-debit tuition plans especially avoids card expirations over a multi-year degree program.
- Monthly tuition auto-debit on ACH
- Annual institutional fee collection
- PPD / WEB SEC codes depending on origin
- Posting to SIS / ERP balance systems
Government &, Public Sector
Government suppliers invoicing municipalities on Net 30 (or longer), ACH is the default method, and Payment Hub handles the CCD / CTX B2B SEC codes plus CEDP Level 3 on the card portion where applicable.
- CCD / CTX for government-paid B2B
- Utility billing auto-debit (PPD for consumer utilities)
- Permit and citation payments
- Posting to Tyler / Oracle / SAP government financials
Professional Services &, Agencies
Retainers, project invoices, and hourly bills, especially large-ticket enterprise engagements. Authorized monthly retainer ACH debits replace the "did you pay yet?" cycle on ongoing relationships.
- Authorized monthly retainer auto-debit
- Large project balance payments via ACH
- Trust / IOLTA segregation for legal workflows
- Real-time posting to PSA / ERP
Subscription, SaaS &, Membership
Annual and enterprise plans where the subscription value justifies ACH's lower cost and durability. Consumer-small-ticket subscriptions typically stay on card. Enterprise and annual plans benefit most from ACH.
- Enterprise annual billing on ACH
- High-value B2B subscription tiers
- CCD SEC for corporate subscriber authorization
- Lower involuntary churn vs card-only recurring
We can typically go live in 48 hours once ERP sandbox credentials and gateway API credentials are shared. Skip the reading and book a 30-minute walkthrough, we can also pull a rough before/after economics model during discovery.
How Payment Hub processes ACH
From a merchant's perspective, ACH in Payment Hub works identically to card acceptance, the method appears in the portal, the customer authorizes, the transaction happens, the ERP posts. Underneath, Payment Hub handles the NACHA-specific work.
One method in the checkout
Customers see a single "Bank Account" or "ACH / eCheck" option alongside card and wallet methods. Same branded portal, same checkout component, Payment Hub routes the transaction to your gateway's ACH rail under the hood.
Tokenization at the gateway vault
Routing and account number are tokenized immediately at your gateway's PCI-scoped vault, the same infrastructure that holds card tokens. Subsequent charges reference the token, not the account number. Your servers and Clarity's never store raw bank credentials.
Authorization capture (NACHA)
Every ACH debit requires NACHA-compliant customer authorization. Payment Hub captures the authorization, electronic signature, click-to-authorize with timestamp and IP, or imported written mandate, and stores the audit trail so you can produce it in a return dispute.
Real-time ERP posting + return-code sync
When the ACH submits successfully, Payment Hub posts the cash receipt to your ERP immediately, like a card authorization. If the transaction returns (NSF, account closed, authorization revoked), Payment Hub receives the return code from the gateway and updates the ERP automatically, re-opening the invoice and alerting AR.
Payment Hub handles the operational details you normally don't want to think about: same-day ACH cutoff times, holiday calendars, CCD vs CTX addenda records for corporate transactions, NSF re-presentment rules (up to two attempts within 180 days per NACHA), and return-code-driven workflow updates. Your AR team sees clean cash application and exception queues. The NACHA mechanics stay under the hood.
NACHA compliance and SEC codes
NACHA (the National Automated Clearing House Association) sets the rules for how ACH transactions must be authorized, formatted, and classified. The classification is called a Standard Entry Class (SEC) code, and choosing the wrong one is one of the more common ACH implementation mistakes. Payment Hub picks the right SEC code per transaction based on origin and type.
Web-initiated consumer
A consumer enters their bank details on your website and authorizes the debit online. Used for most one-time and recurring consumer payments via the customer portal.
Telephone-initiated consumer
A consumer gives bank details over the phone to your AR staff. Used for MOTO consumer flows (healthcare front-desk calls, education late enrollment, nonprofit phone-in gifts).
Prearranged Payment / Deposit
Consumer recurring with written or electronic authorization on file. Used for subscription, membership, tuition, and healthcare payment plans.
Corporate Credit / Debit
Business-to-business ACH transactions between corporate entities. Used for B2B distribution, manufacturing, and government-supplier AR.
Corporate Trade Exchange
B2B ACH with structured addenda records carrying remittance data (invoice numbers, amounts). Used for high-value B2B where the corporate customer needs machine-readable remittance info.
Check-conversion codes
Used when a paper check is converted to ACH at the point of receipt. Less common for Payment Hub customers today, but supported where paper check acceptance still exists.
The practical implication: you don't need to know any of this in day-to-day use. Payment Hub picks WEB for portal payments, TEL for MOTO entries through your AR staff, CCD for confirmed corporate debits, CTX for large B2B transactions that need addenda remittance data, and PPD for recurring consumer, all automatically based on the context of the transaction. The SEC code shows up in the transaction record for audit and return-code reference, but it's not something AR staff manage per invoice.
Security, returns, and risk management
ACH acceptance has a specific risk profile. Some of it is lower than card risk (no chargeback exposure, no PCI scope on the bank-account side beyond the bank's own vault). Some of it is different (NSF returns, unauthorized-debit reversals). Payment Hub handles both sides.
- Tokenization at the gateway vault. Bank account credentials tokenize immediately at the gateway's PCI-scoped vault. Raw routing + account number never touch Payment Hub or your servers after tokenization. The same vaults that hold card tokens hold ACH tokens.
- NACHA-compliant authorization storage. Every recurring and one-time debit captures an audit trail meeting NACHA's authorization requirements, electronic signature or click-to-authorize with timestamp and IP, retained for the 2 years NACHA requires after the last transaction.
- Return code handling. ACH transactions can return for insufficient funds (R01), account closed (R02), authorization revoked (R07), unauthorized debit (R10), and dozens of other reasons. Payment Hub ingests return codes from the gateway in real time, updates the ERP to re-open the invoice, and routes exception alerts to your AR team automatically.
- NSF re-presentment. NACHA permits up to two representments of an NSF-returned transaction within 180 days. Payment Hub handles the representment schedule, default is two retries at 5 and 10 business days, with configurable rules per vertical.
- Account validation. Where the gateway supports it (most do), Payment Hub can perform account validation at the moment of tokenization, checking that the routing + account number combination is valid before the first debit submits. Reduces first-debit NSF returns materially.
- Velocity and threshold controls. Configurable daily / weekly / monthly debit caps per customer, per invoice dollar threshold, and per authorization, to prevent accidental duplicate debits or abuse of stored tokens.
- SOC 2 Type II. Clarity Ventures operates to SOC 2 Type II standards. Security, availability, confidentiality, and data-handling controls are independently audited on an ongoing basis.
ACH's risk profile is notably smaller than card's for most B2B customers, no chargeback exposure up to 60 days out, no PCI audit implications on the bank-account side, and authorization requirements that are generally easier to meet and harder to dispute. The main operational overhead is NSF handling, and that's a process Payment Hub automates.
ACH / eCheck in Payment Hub FAQ
The questions B2B AR, IT, and finance teams ask before turning on ACH acceptance in Clarity Payment Hub.
What's the difference between ACH and eCheck?
For merchant acceptance purposes, ACH and eCheck are essentially the same thing, both move money between U.S. bank accounts over the ACH network governed by NACHA. "eCheck" typically refers to the web-initiated flow where the customer enters their bank routing and account number directly, while "ACH" can also include backend batch processing, recurring debits, and corporate-initiated transactions.
Clarity Payment Hub supports both as a single payment method in the checkout and portal, customers see one option labeled "Bank Account" or "ACH / eCheck" and enter credentials once. Payment Hub handles the SEC code selection and NACHA formatting underneath based on the transaction type.
When is ACH cheaper than accepting a credit card?
Almost always on invoices over about $500, and dramatically cheaper as invoices grow. ACH is typically priced as a flat fee (often $0.25–$1.00 per transaction) plus a small percentage (often 0.25%–0.75%), while card processing is typically 2–3% for consumer cards and higher for commercial cards.
On a $50,000 invoice, that difference is often $1,000–$1,500 of margin saved per transaction. Clarity Payment Hub lets you set a configurable invoice-dollar threshold above which ACH becomes the default method, protecting card-processing economics on large tickets while keeping card acceptance for small, fast consumer flows.
How does ACH replace Net 30 terms?
Net 30 is essentially giving a customer 30 days of free credit, plus the cost of chasing them, plus the cost of carrying the receivable on your books. Authorized ACH auto-debit replaces that with a pre-authorized, tokenized pull from the customer's bank account on a scheduled date.
The customer keeps payment timing flexibility (you can bill Net 15, Net 30, or Net 45, still with auto-debit on the due date), but you eliminate the chase cycle, the write-off risk, and the AR staff time spent on collections calls. Clarity Payment Hub posts the ACH result back to the ERP in real time, so the customer's account and aging report clear the moment the bank confirms the debit.
Is ACH secure? How does Payment Hub protect bank account details?
ACH is secure when the right architecture is in place. Clarity Payment Hub tokenizes the customer's bank routing and account number at your gateway's PCI-scoped vault, the same tokenization pattern used for cards, so your servers and Clarity's servers never store raw bank credentials. Subsequent charges reference the token, not the account number.
Payment Hub also applies NACHA-required authorization capture for every recurring or one-time debit (electronic signature or audit-trailed click-to-authorize), enforces SEC code rules per transaction type, and posts return codes back to the ERP in real time if a transaction is returned for insufficient funds, account closed, or authorization disputed.
Which industries benefit most from ACH acceptance?
All eight Clarity verticals benefit, but the biggest wins are where invoice sizes are high or recurring relationships are long-term. B2B distribution and manufacturing commonly route 60–90% of high-dollar AR through ACH to protect unit economics. Nonprofits see significantly lower attrition on recurring ACH gifts versus recurring card gifts (no card expirations).
Education programs and healthcare practices use ACH for tuition payment plans and patient payment plans because the multi-year horizon makes card-on-file fragile. Subscription / SaaS businesses with annual or enterprise plans see the same economics advantage as B2B. Payment Hub applies the right industry pattern per vertical automatically.
What gateways does Clarity Payment Hub support ACH on?
Every gateway in the Payment Hub library that supports ACH natively, which includes virtually all of them: Worldpay, Adyen, Cybersource, Fortis, Elavon, PNC Merchant Services, PayTrace, Nuvei, Authorize.Net, Braintree, Stripe, Global Payments, NMI, USAePay, and more.
Payment Hub is gateway-agnostic, so your ACH configuration travels with you if you change processors. Some gateways have specific ACH products with their own brand names, Authorize.Net's eCheck.Net, Stripe's ACH Direct Debit, Adyen's SEPA Direct Debit for Europe, but Payment Hub presents them as one unified "Bank Account" method in the checkout regardless of which gateway is routing underneath.
How long does ACH take to settle?
Standard ACH settles in 1–3 business days. Same-Day ACH is available for faster settlement at a slightly higher fee, with same-business-day funding on transactions submitted before NACHA's same-day submission deadlines.
Clarity Payment Hub supports both standard and Same-Day ACH through whichever gateway is underneath, and the ERP cash receipt is posted immediately when the transaction is authorized, so your AR system shows the invoice as paid before the bank funds actually clear, the same way a credit-card transaction posts before card settlement lands.
What happens if an ACH transaction is returned (NSF, authorization revoked, etc.)?
Payment Hub ingests the return code from the gateway in real time and updates the ERP automatically, the invoice re-opens, the customer record shows the return reason, and an alert routes to your AR team. Common return codes include R01 (insufficient funds / NSF), R02 (account closed), R07 (authorization revoked), and R10 (unauthorized debit).
For NSF returns specifically, Payment Hub can automatically re-present the transaction up to two times within 180 days (NACHA's allowed representment window), typical schedule is retry at 5 and 10 business days. For authorization-revoked or unauthorized-debit returns, Payment Hub stops further debits on that authorization and flags the customer record for AR review.
Does ACH work for international payments?
ACH is specifically the U.S. bank-transfer network. For international bank-debit payments, Payment Hub supports SEPA Direct Debit across the Eurozone (via gateways like Adyen and Stripe), BACS Direct Debit in the UK, BECS in Australia, and local bank-transfer methods in other regions, surfaced as the same unified "Bank Account" method in the checkout but routed to the correct regional rail based on the customer's country.
For U.S. merchants with occasional international B2B customers, ACH is typically paired with international wire as a second option for the cross-border flows where SEPA / BACS / BECS don't apply.
Can customers save their bank account for one-click re-use?
Yes, that's the default experience. Once a customer's bank account is tokenized at your gateway's vault, it appears in the customer's portal as a saved payment method alongside any saved cards. Repeat payments are one-click, and the authorization-on-file carries forward. AR staff can also charge a saved bank token on the customer's behalf through Virtual Terminal or admin views where enabled.
For B2B customers with accounting contacts and purchase-order workflows, Payment Hub can store the ACH token at the customer-account level (not just the individual purchaser) so any authorized contact at the customer can initiate payment against the same bank account.
How does Payment Hub handle surcharging on ACH?
ACH is not subject to the same card-network surcharging rules, credit card surcharging is governed by Visa / Mastercard / Amex / Discover network rules, which don't apply to ACH. Merchants can charge a convenience fee on ACH where state law permits, or can surcharge cards only while keeping ACH at the base price (a common pattern in B2B distribution, where ACH as the non-surcharged default nudges high-ticket customers toward the lower-cost method).
Payment Hub makes this configurable per vertical, per customer segment, and per invoice threshold, ACH base price with card surcharge on small tickets, ACH as primary method with no surcharge on large tickets, or other combinations depending on your pricing strategy.
What's the integration cost and timeline?
ACH is a capability of Clarity Payment Hub, there's no separate ACH product to purchase. If you're already implementing Payment Hub with a supported gateway, ACH turns on with a configuration change. Typical go-live takes 48 hours once ERP sandbox credentials and gateway ACH capability are confirmed. Your gateway's ACH fees (flat per-transaction + small percentage) apply directly, Clarity doesn't insert a transaction markup.