Key takeaways
- These are illustrative case notes about how we approach adding ACH, not a named client or a promised result.
- Merchants usually want to accept ACH payments online for large or recurring bank-to-bank payments where card fees add up.
- ACH runs through the same Flux platform and API as cards, so it is one integration, not a separate system.
- Plan for ACH specifics: capture authorization, consider bank verification, and build a process for returns that arrive days later.
- With Flux, cards settle in about 1-2 business days and ACH in about 1-3, while stablecoins settles to the merchant wallet instantly.
The situation: a merchant who needed to accept ACH payments online
These are case notes, which means they describe how we approach a problem rather than a specific named client or any promised result. The pattern is common enough to be worth walking through: a merchant comes to us wanting to accept ACH payments online, usually because card fees on large or repeat invoices have started to sting, and they want a bank-to-bank option that customers will actually use.
The details below are illustrative. What stays constant is the shape of the problem and the questions we work through with a merchant in this position.
Why ACH, and why not only cards
The merchant in this kind of case typically sells at higher ticket sizes or bills the same customers repeatedly: think wholesale orders, professional services, or subscriptions with real dollar amounts. On those, a percentage-based card fee adds up, and many of their customers would happily pay from a bank account instead. ACH, the network that moves money directly between US bank accounts, fits that behavior.
We are careful not to frame ACH as a replacement for cards. Cards win on speed and on customer expectation for smaller or one-off purchases. The goal is usually to offer both and let the payment method match the transaction.
How does accepting ACH payments online work?
To accept ACH payments online, the customer authorizes a debit from their bank account, providing their account and routing numbers or authorizing through their bank. The merchant submits that as an ACH transaction, and the funds move from the customer's bank to the merchant. In our setup, this runs through the same platform and API the merchant already uses for cards, so it is one integration rather than a separate system to maintain.
We wire it into the merchant's existing checkout or invoice flow, so from their side accepting a bank payment is another method on the same page, and from the customer's side it is a familiar bank-account entry.
What we weigh in the setup
A few decisions come up every time. First, authorization and record-keeping: ACH requires the customer's authorization, so we make sure the flow captures and stores that cleanly. Second, verification: we discuss how much bank-account validation the merchant wants up front to reduce failed or returned payments. Third, returns: unlike a card decline at the moment of sale, an ACH payment can be returned days later for insufficient funds or a closed account, so the merchant needs a process for handling a return after the fact.
We talk through these openly rather than hiding them, because a merchant who understands ACH returns will build their fulfillment and dunning around the timing instead of being surprised by it.
Settlement timing and cash flow
Timing is the biggest mindset shift from cards. With Flux, card payments settle in roughly one to two business days and ACH bank transfers settle in roughly one to three business days. ACH trades a little speed for a lower-friction bank payment, so we help the merchant set expectations: do not treat an ACH payment as cleared the instant it is submitted, and plan fulfillment or access around the settlement window.
For merchants who also want an instant option, we point out that Flux settles stablecoins to the merchant wallet instantly, which some customers prefer for exactly that reason. The point is to match timing to the situation rather than force one rhythm on every sale.
Where ACH fits alongside cards and stablecoins
The setup we usually land on offers cards, ACH, and stablecoins through one platform, so the merchant can present the right option per transaction: cards for speed and everyday purchases, ACH for large or recurring bank-to-bank payments where saving on card fees matters, and stablecoins where a customer wants it and instant settlement is a bonus. It is one integration, one API, and one place to reconcile.
On pricing, Flux keeps it simple with a flat 2.9% plus 30 cents and no monthly fees or contracts, and higher-volume merchants can discuss volume-based custom pricing. That predictability is part of why merchants in this situation add ACH with us: they can offer the method their customers want without taking on a second vendor. A merchant weighing this can reach our team at sales@fluxpayments.com or (813) 402-8244, or apply at /apply.html.
Frequently asked questions
How long does an ACH payment take to settle?
With Flux, ACH bank transfers settle in roughly one to three business days, compared with about one to two for cards. Plan fulfillment around that window rather than treating an ACH payment as cleared immediately.
Can an ACH payment fail after it looks successful?
Yes. Unlike a card decline at checkout, an ACH transaction can be returned days later for reasons like insufficient funds or a closed account, so you need a process to handle a return after the sale.
Do I need a separate provider to accept ACH online?
No. Flux supports cards, ACH, and stablecoins through one platform and API, so you can add bank payments to your existing checkout without onboarding a second vendor.
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