ACH (the Automated Clearing House) is the US batch network run under Nacha's rules, and Fedwire (the Federal Reserve's same-day wire system) sends each payment as its own message, final once credited. ACH suits routine payments that can wait a day or two. Fedwire is for money due today.
ACH vs Fedwire: what is the difference?
Both rails move US dollars between US bank accounts. They differ in how the money travels, how fast it settles and how hard a mistake is to fix.
Item | ACH | Fedwire |
Who runs it | Nacha writes the rules; the Federal Reserve and The Clearing House are the ACH Operators | The Federal Reserve Banks, as the Fedwire Funds Service |
How money moves | Banks batch payment instructions into files and send them through an ACH Operator | A payment message between participants, settled across their Federal Reserve accounts |
Speed | Same day, next banking day or two banking days | Same day |
Per-payment ceiling | Same Day ACH is capped at $1 million per payment | No cap on the Federal Reserve pages read |
After the credit | Can come back as a return with a reason code | Final once credited; a return is a request |
Closed on | Weekends and Federal Reserve holidays | Weekends and Federal Reserve holidays |
ACH and Fedwire side by side, from Nacha and Federal Reserve Financial Services pages, checked November 16, 2026.
How an ACH payment moves from sender to receiver
The sender is the Originator, and its bank is the ODFI (Originating Depository Financial Institution). The ODFI sends the file to an ACH Operator, which sorts the entries and passes each one to the receiver's bank, the RDFI (Receiving Depository Financial Institution). The RDFI posts the money to the Receiver. Nacha names two ACH Operators: the Federal Reserve and The Clearing House.
ACH carries both credits, where the sender pushes money, and debits, where the Originator pulls it with the payer's authorization. Nacha puts credits at just under half of all payments and debits at just over half.
That scale makes it the default: 35.2 billion payments worth $93 trillion in 2025, per Nacha's volume statistics. Nacha estimates 80% of them settle in one banking day or less.
Two details matter to a receiver. Same Day ACH leaves out international entries (IAT) and payments above $1,000,000, though a Nacha rule raises that limit to $10 million on September 17, 2027. And since September 18, 2026, the receiver's bank must make a non-same-day ACH credit available by 9:00 a.m. its local time on the settlement date.
How a Fedwire transfer works and why it is final
Fedwire Funds Service participants send and receive payments for their own accounts or for corporate and individual clients. The Federal Reserve describes the benefit as finality of payments credited to participants' master accounts at the Federal Reserve Banks. You reach the rail through your bank.
A sent wire carries identifiers, the IMAD and OMAD, which the Federal Reserve lists as the way to confirm a message was processed. To confirm the beneficiary was credited, a participant sends an investigation message. To ask for the money back, it sends a return request message. The Federal Reserve's FAQ calls that second message a request, and the pages read describe no rule that sends the funds back on demand.
ACH and Fedwire cutoffs and operating hours
The Federal Reserve sets the hours of the rails, and your provider sets its own deadline on top.
Item | ACH (FedACH) | Fedwire Funds Service |
Opens | Nacha: open 23¼ hours every business day | 9:00 p.m. ET on the evening before the business day |
Last deadline | Same Day ACH files by 4:45 p.m. ET | Customer transfers by 6:45 p.m. ET, bank transfers by 7:00 p.m. ET |
Closes | Federal Reserve settlement is closed 6:30 p.m. to 7:30 a.m. ET on business days | 7:00 p.m. ET |
Settles | Same Day at 1:00, 5:00 and 6:00 p.m. ET; other items at 8:30 a.m. ET on the next banking day | Same day |
Not a business day | Saturdays, Sundays, Federal Reserve holidays | Saturdays, Sundays, Federal Reserve holidays |
Rail hours from the FedACH Processing Schedule (effective September 12, 2022), the Fedwire operating hours page and Nacha, checked November 16, 2026.
Read the ACH row with care. The three Same Day deadlines are 10:30 a.m., 2:45 p.m. and 4:45 p.m. ET, and they apply to the file a bank transmits to the Federal Reserve. They do not tell you when your own bank stops accepting your payment, which the bank sets itself. Convert every cutoff to the sender's time zone before promising a date: the clock is Eastern Time.
What ACH and Fedwire cost
Three layers sit in the price of a US dollar payment, and the public sources show only one of them.
Layer | What the sources say |
Federal Reserve fee to the bank, Fedwire | $0.97 per transfer for up to 14,000 transfers a month, falling to $0.30 and $0.195 in higher tiers; an incentive discount applies above 60% of a bank's historic volume (2026 schedule) |
Network fee to the bank, ACH | Annual and per-entry fees to Nacha, set by its board at cost; no amount on the page read |
Fee to you | Set by your bank or provider; not on any Federal Reserve or Nacha page |
Where the cost of a payment comes from, per the Federal Reserve Fedwire 2026 fee schedule and Nacha's network administration fees page, checked November 16, 2026.
The Federal Reserve's fee is what a bank pays, not what a customer is charged. What a business pays is in its bank's fee schedule. On the ACH side, Nacha cites the 2025 AFP Digital Payments Survey, which found a median cost of 26 to 50 cents to initiate and receive an ACH payment for a business, against $2.01 to $4 for issuing a check. It compares ACH with checks and says nothing about a wire.
Returns, recalls and wrong account numbers
A wrong account number is the failure both rails share, and they handle it differently. On ACH, the receiver's bank can return a payment, and each return carries a reason code. R16, for example, is defined as "Account Frozen/Entry Returned Per OFAC Instruction", and from March 17, 2028 sanctions returns move to a new code, R90, per Nacha.
For consumers, Regulation E (12 CFR 1005.11) gives a notice window of 60 days after the statement that first shows an error. That is a consumer rule. The sources read give no matching window for a business receiver, so a company paying or collecting by ACH should read its bank agreement and ask the bank.
On Fedwire, a credited wire is final, and the only route back the Federal Reserve describes is the return request message above.
I would send a small first payment to any new US supplier, by ACH, before a large wire. Fedwire is final once credited, so the cheap place to catch a wrong routing or account number is a first payment small enough to lose. I would take the numbers from a signed invoice or a bank letter, never from an email that says the details changed.
Which rail for which payment
Three questions decide it: when the money has to land, how large the payment is and how bad a mistake would be. A supplier invoice with a few days of slack and a recurring payment to a known payee fit ACH. An invoice due today, a large one-off payment, or anything above the Same Day ACH ceiling of $1 million fits Fedwire, with the details verified first.
The same logic holds for a payout from a stablecoin balance: the off-ramp to a US bank guide has the fields, and paying US suppliers the whole flow.
When ACH and Fedwire are the wrong rails
Both are domestic. A payer outside the United States usually reaches a US dollar account by SWIFT, where an intermediary bank can add hours or days and deduct fees you did not set. How that compares with settling in a stablecoin is in stablecoins vs SWIFT.
They are the wrong rails when the money has to move at night or on a Sunday, because both close with the Federal Reserve. The Federal Reserve lists a separate FedNow Service among its payment services; this guide does not cover it, and Lumx's Coverage page lists no FedNow rail.
They are also the wrong rails when the recipient is in Latin America and expects local currency. Those corridors use their own domestic systems: the Pix guide for businesses for Brazil, the SPEI guide for Mexico and the Bre-B guide for Colombia.
How ACH and Fedwire work on a Lumx USD account
A USD account on Lumx is a virtual account issued by a banking partner. Lumx works in the United States through a sponsor bank model: the partner holds the funds and runs the rails, and Lumx is not a bank. The account supports ACH, Fedwire and SWIFT, with ACH running as credits (push) in both directions, and on ACH and Fedwire the recipient's bank statement shows your customer as the sender, because the account is named. A named virtual account is a local account number issued in the customer's own name, and the product page shows it across currencies.
Lumx is stablecoin payments infrastructure for businesses that move money between Latin America and the rest of the world: one API to collect, hold, convert, and pay out in BRL, MXN, COP, USD, EUR, and GBP or in USDC and USDT, over local rails such as PIX, SPEI, PSE, Bre-B, ACH, FEDWIRE, SEPA, and Faster Payments, with SWIFT and on-behalf-of payments and collections (POBO and COBO) in USD, EUR, and GBP, plus named virtual accounts, custodial wallets, and KYB/KYC built in.
You request USD in the accounts array when you create the customer. The customer first passes KYB (know your business, the verification of a company and its owners) or KYC (know your customer, the verification of an individual), and a USD account then takes up to one business day to become active while the banking partner reviews it. A webhook says when it can receive funds.
To collect, you create an autoconversion rule on the account, once. The rule returns the bank details to share with the payer: account number, routing number or BIC, and bank name, for ACH, Fedwire and SWIFT. The payer sends by whichever rail it prefers, every deposit converts to USDC or USDT in the customer's wallet, and a webhook fires when it finishes. A USD account holds one active rule at a time.
To pay, you register the recipient as a destination: rail ACH or Fedwire, currency USD, account type, account and routing numbers, the bank's name and address, and the holder's details. The destination is verified before it can receive a payout. The off-ramp then runs from the stablecoin balance, and the destination fixes the rail.
Timing follows the Lumx cut-off page, whose figures are processing targets and not contractual guarantees:
Rail | Cut-off (ET) | Settlement | Operating days |
ACH | 2:00 PM | 1 to 2 business days | US business days |
Fedwire | 3:00 PM | Same business day, typically within hours | US business days |
Lumx cut-offs for USD rails, from the Lumx payment rail cut-off times page, read November 16, 2026.
These are deadlines for a request to Lumx, not the Federal Reserve's hours, so they sit earlier than the table above. A request after the cutoff, on a weekend or on a Federal Reserve holiday goes out on the next business day. A compliance review can hold a transaction: an RFI (request for information, a compliance hold that asks for a document before a transaction clears) pauses it until the document arrives. Lumx considers an off-ramp complete when the funds leave its banking partner, and the recipient's bank can still hold them for its own review.
Limits attach to the customer, in the USD equivalent of each transaction: a KYB customer at standard verification has a daily and a monthly limit of $100,000, and Enhanced verification raises them. The rates are on the USDC to USD page, and every currency and rail is on the payment coverage page and in global payments.
Methodology and sources
Rail facts come from the Federal Reserve and Nacha, all read on November 16, 2026. From Federal Reserve Financial Services: the Fedwire Funds Service page, the Fedwire operating hours, the FedACH processing schedule, the FedACH SameDay Service page and the Fedwire 2026 fee schedule.
From Nacha: How ACH Payments Work, The ABCs of ACH, ACH Network Volume and Value Statistics, Business-to-Business (B2B), Network Administration Fees, and the rules on the $10 million Same Day ACH limit, funds availability and the sanctions return code. The consumer error window is in 12 CFR 1005.11 on eCFR.
Three negatives were checked: the Federal Reserve pages read give no per-wire ceiling, the Nacha pages read give no return window for a business receiver, and no page read gives what a bank charges a business for a wire. If any of them publishes a figure, this post is out of date.
Lumx facts come from our public documentation: Payment rail cut-off times, Accounts, Sender of record, Autoconversion rules, Global accounts, Destinations, Transaction limits and Coverage, all read November 16, 2026.
Verified on November 16, 2026. Operational context, not legal, tax, or investment advice.
Cover photo: Isis França on Unsplash.
ACH vs Fedwire: which should a business use?
Use ACH for routine payments that can wait one to two business days. Use Fedwire when the payment must land the same business day or you want it final once credited. On Lumx, one USD account runs both, and the rail is set on the recipient's destination.
How long does an ACH payment take compared with a Fedwire?
ACH settles the same day through Same Day ACH, or on the next banking day or two banking days later, and Nacha estimates 80% of payments settle in one banking day or less. Fedwire settles the same day, with the Federal Reserve's customer-transfer cutoff at 6:45 p.m. ET. On Lumx the targets are 1 to 2 business days for ACH and the same business day for Fedwire, with cut-offs of 2:00 PM and 3:00 PM ET.
Can an ACH or Fedwire payment be reversed?
An ACH payment can come back as a return with a reason code, through the receiving bank. A Fedwire payment is final once credited, and the only route back the Federal Reserve describes is a return request message. Confirm the routing and account numbers before the first payment.
Do ACH and Fedwire work on weekends and holidays?
No. Both treat Saturdays, Sundays and Federal Reserve holidays as non-business days, and a request sent then waits for the next business day. Lumx follows the same calendar for ACH and Fedwire, and a request after its cut-off goes out the next business day.
How does a stablecoin fit with ACH and Fedwire?
A stablecoin balance sits behind the dollar rails on both ends. On Lumx, a USD deposit that arrives over ACH or Fedwire converts automatically to USDC or USDT in the customer's wallet, and a payout converts the stablecoin back to dollars and sends it over ACH or Fedwire to a verified destination. The recipient receives dollars at their own bank.





