ACH & eCheck Payments

A card swipe and a bank debit travel through completely different rails. When a customer authorizes an ACH debit, the transaction is queued into a file BSV Solution's gateway submits to the ACH network at a scheduled cutoff, rather than authorized in real time the way a card is. The originating bank routes it to the customer's bank, which has a window to accept or return the item before funds are considered settled.

That difference is why ACH doesn't behave like a terminal sale in daily reporting: instead of an instant approval or decline, you get a same-day or next-day confirmation that the file was accepted, followed a business day or two later by settlement or a return code if the account was closed, the funds were insufficient, or the customer disputed the debit as unauthorized.

For businesses billing five, ten or twenty-thousand-dollar invoices, that batch-based timing is a fair trade for materially different economics than routing the same ticket through card networks — which is the core reason contractors, wholesalers and property managers move big invoices to bank debit in the first place.

ACH tends to fit businesses with predictable, recurring or high-ticket billing: property managers collecting rent, membership and dues organizations, wholesalers invoicing net-30 accounts, clinics billing patient balances, schools collecting tuition, and contractors progress-billing a project. In each case the payer is known, the amount is usually similar month to month, and the relationship continues long enough that a returned payment can be followed up on directly.

It fits less well for one-time retail sales to strangers, low-ticket transactions where a return fee would outweigh the payment, or any business that needs an instant yes/no before releasing goods — a card or digital wallet is the better fit there. Most of the merchants we set up on ACH keep card acceptance running in parallel and simply route the invoices where bank debit makes sense.

Before setting up bank debits, we look at your typical invoice size, how often you bill the same customer, your current return and chargeback history, whether you already collect signed or web authorization for other purposes, and how your accounting software would need to reconcile a settlement that lands a day or two after the transaction date. Underwriting also reviews your business type, since ACH origination is a bank-sponsored service and certain industries carry additional requirements.

The most common setup pitfall is treating ACH authorization casually — verbal-only agreements, no retained record, or debiting an amount the customer didn't clearly agree to. We build the authorization language and retention process into onboarding so a dispute later has something to point to.