The US payments landscape at a glance

The United States runs its domestic payments on a mix of old and new systems, and the mix can confuse anyone who expects a single national design like the one India built around NPCI. In the US, the Federal Reserve operates Fedwire and FedNow and also operates the FedACH service, while a private organisation called Nacha governs the ACH network rules, and a private company called The Clearing House operates CHIPS and the RTP network. Commercial banks connect to several of these systems at once, and a payment can travel through more than one of them before it reaches the beneficiary. A business analyst working on US payments must learn which operator runs each system, because the operator decides the rules, the hours and the support model. The four systems in this chapter serve different needs, and the differences are sharper than they first appear. Fedwire is the Federal Reserve's real time gross settlement system for high value, time critical payments, and it has been running since 1918 in various forms. FedNow is the Federal Reserve's newer instant payment service, launched in July 2023, which lets banks send and receive payments in seconds around the clock. ACH is the batch network that moves payroll, direct debits, bill payments and government benefits in files, and it is the highest volume system in the country. CHIPS is the private sector system that settles large value payments, many of them connected to international business, by netting them through the day. A single US dollar payment can legitimately touch two of these systems, for example a cross border payment that arrives through CHIPS and is then sent onward by Fedwire, so the analyst must trace the full path rather than assuming one system does the whole job. One feature of the US system that surprises analysts from other countries is that there is no single national account identifier like an IBAN or a VPA. US payments are addressed with a routing number, which identifies the bank, and an account number, which identifies the account at that bank. The routing number is nine digits long and is managed by the American Bankers Association. This addressing is simple but it creates its own risks. A wrong routing number sends the payment to the wrong bank, and a wrong account number sends it to the wrong customer. Validation of routing numbers and account numbers, and the use of services that confirm the account holder name, is therefore a standard part of US payment design. There is no check digit algorithm on a US account number comparable to the IBAN MOD 97 check, so a mistyped account number can pass format validation and still be wrong. The regulatory split is the second thing an SME must grasp. The Federal Reserve is both an operator and a regulator for Fedwire, FedNow and FedACH, Nacha writes the rules that every ACH participant must follow and can fine a bank that breaks them, and The Clearing House writes the rules for CHIPS and RTP as a private operator. A payment that crosses from ACH to Fedwire crosses a regulatory boundary as well as a technical one, and the exception handling, the return timelines and the liability rules change at that boundary. When a business asks for a payment product that works across systems, the analyst must map which rulebook governs each leg, because a return that is valid on ACH may be impossible on Fedwire once settlement has happened. Volumes put the systems in perspective. ACH moves tens of billions of transactions a year and is the workhorse for payroll and bills. Fedwire moves around 800,000 payments a day worth around 4 trillion dollars, and CHIPS moves around 500,000 payments a day worth around 1.8 trillion dollars. FedNow is small by comparison today but growing, because it is the only Federal Reserve system that settles instantly at any hour. The lesson for the analyst is that volume and value point in opposite directions: the system that moves the most payments is the cheapest and slowest, and the system that moves the most money is the most expensive and the fastest. Designing a payment flow means choosing deliberately between those two poles. The message standard is now common across the large value systems, which is a recent and important change. Both Fedwire and CHIPS have completed their ISO 20022 migrations, Fedwire in July 2025 and CHIPS in April 2024, so a large value payment now carries structured party information, structured remittance data and the same pacs.008 and pacs.009 message definitions as a cross border payment. ACH still runs on its own file format with batches and SEC codes, and FedNow runs on ISO 20022 from birth. An analyst who designs a US payment product today should assume ISO 20022 for the real time and large value legs, and the ACH file format for the batch leg, and must design the translation between them where a payment crosses from one to the other. The practical skill this chapter teaches is routing. For every payment an analyst should be able to answer four questions in order: how large is it, how fast must it settle, what will it cost, and what happens if it fails. A 50,000 dollar supplier payment that must arrive today goes through FedNow if both banks participate, or Same Day ACH if it is submitted before the window, or Fedwire if neither of those works. A payroll of 1,000 employees goes through ACH as a file, because no other system can move that many payments that cheaply. A 2 million dollar securities settlement goes through Fedwire, because only gross settlement in central bank money gives the finality the trade needs. The rest of this chapter walks through each system end to end, then shows how to choose between them and what to do when a payment goes wrong. A final point on time. Every US cut off in this chapter is expressed in US Eastern Time, and the analyst must state that explicitly in every requirement, every screen and every operations manual. A payment submitted at 5pm in California is submitted at 8pm in New York, and that three hour difference is the difference between settling today and settling tomorrow. Business days are also US business days, so a payment instructed on a Friday evening may not settle until Monday, and a payment instructed before a US federal holiday waits until the next business day. The calendar is part of the product design, not an afterthought.