Key takeaways
- Carson's port-adjacent B2B economy runs on invoices, and ACH removes interchange from those payments entirely.
- ACH returns have codes and short windows; there is no representment fight, but NACHA return thresholds still apply.
- Validate accounts on first use, store authorizations, and keep card processing for the retail side.
ACH payments in Carson make more sense than almost anywhere else in Los Angeles County, because Carson does not run on retail. It runs on trucks. Between the 405, the 110, and the Alameda Corridor, Carson hosts drayage companies hauling from the ports of Los Angeles and Long Beach, container yards, freight forwarders, warehouse operators, the refinery workforce, industrial suppliers along Wilmington and Avalon, and a long list of service contractors that keep all of that moving. Those businesses invoice each other. They do not swipe cards. And yet many of them still pay card fees on five-figure invoices because nobody set up a better option.
The math on a freight invoice
Consider a drayage company billing a customs broker $18,000 for a month of moves. On a corporate card, even with Level 2 data, the interchange and markup can run several hundred dollars. On ACH, that same invoice costs a flat per-item fee, sometimes with a modest cap. The customer's accounts-payable team is usually happier too, because their own bank charges them nothing to send an ACH credit and they can schedule it to net terms. The savings are not subtle, and they compound across every invoice you send.
The same logic applies to the container-repair shops, tire and truck-service yards, industrial-cleaning firms, and staffing agencies that serve Carson's logistics base. If your typical receivable is more than a few hundred dollars and you already send invoices, the question is not whether to accept ACH but why you have not.
Debits, credits, and who initiates
There are two ways to get paid by ACH, and Carson businesses use both. An ACH credit is a push: your customer's bank sends money to you, the way a large shipper pays its vendors on a weekly run. You give them your account details, ideally through a secure form, and you wait for the remittance. An ACH debit is a pull: you originate the debit against the customer's account with their authorization. Debits give you control over timing and work well for recurring service contracts; credits require nothing from you but are harder to reconcile without a reference number. An ACH platform that handles both directions and attaches invoice numbers to each item saves your bookkeeper hours a week.
Returns instead of chargebacks
Card disputes can arrive months after a transaction and carry a fee whether you win or lose. ACH returns are different in kind. Each return carries a code: R01 for insufficient funds, R03 for no account found, R04 for an invalid account number, R29 when a corporate customer tells their bank the debit was not authorized. On business accounts, the window to claim an unauthorized debit is generally two banking days, not the months a card dispute can drag on. There is no arbitration, no representment package, and no fee-for-losing structure.
What you get instead is NACHA's return-rate rules. Stay below 0.5 percent unauthorized returns, 3 percent administrative returns, and 15 percent overall, and your originating bank leaves you alone. Most of the administrative returns come from typos and closed accounts, which brings us to validation.
Validating accounts before the first debit
NACHA's WEB debit rule requires you to use a commercially reasonable method to validate a bank account the first time you debit it after collecting the details online. That can be a micro-deposit check, an instant account-verification lookup, or a database screen. Do it. It cuts the R03 and R04 returns that otherwise inflate your administrative ratio, and it catches the occasional fraudster who gives you a stranger's routing and account number. It also protects you on the money side: an item that returns after you have already released the freight or the goods is a collections problem, not a payments problem.
Setting up authorizations that hold up
For recurring debits, whether that is a monthly yard lease, a fleet-maintenance contract, or a subscription to a dispatch service, get a written or electronic authorization that names the amount or the method of calculating it, the frequency, and how to revoke it. Store it with the payment schedule. A recurring billing system that keeps the authorization attached to the customer record is what you will reach for when a customer's new controller asks why their account was debited. If you also sell to consumers on an auto-renewing basis, California's Automatic Renewal Law applies its own consent and cancellation requirements on top of NACHA's.
What to keep on cards
ACH is not a replacement for everything. Walk-in retail at the Carson SouthBay Pavilion, concessions on event days at Dignity Health Sports Park, food trucks serving the warehouse lunch rush, and any transaction where the customer wants to pay now and leave should stay on cards, tap, or wallet. Cards settle in 1-2 business days and carry chargeback rights that consumers expect. The point is to route each payment to the rail that fits it: cards for immediate consumer sales, ACH for invoiced B2B work, and for partners who prefer it, stablecoin settlement that lands instantly in a merchant wallet.
Carson businesses that move to ACH for their invoiced revenue typically keep the same customers, the same terms, and the same software, and simply stop handing a percentage of every invoice to the card networks. For an economy built on thin logistics margins, that is a meaningful line on the income statement.
Ready to get set up with Flux?
Cards, ACH, and stablecoins in one platform, with volume-based pricing. No setup fees or contracts.
Get Started