Fedwire: the Federal Reserve's RTGS system

Fedwire Funds Service is the real time gross settlement system operated by the Federal Reserve. It is the backbone of high value US dollar payments: when a bank sends a Fedwire payment, the Federal Reserve debits the sending bank's account at the Fed and credits the receiving bank's account at the Fed immediately, and the payment is final at that moment. There is no batching and no netting: each payment settles on its own in central bank money, which is the safest form of settlement available. Fedwire is used for interbank transfers, corporate treasury movements, property settlements, securities transactions, and any customer payment that is large, urgent, and must be final today. It processes around 800,000 payments a day with a value of around 4 trillion dollars. Follow one payment end to end. A corporate treasurer in Chicago needs to settle a 2.5 million dollar securities trade with a counterparty bank in New York, and the trade must settle today. The treasurer instructs the payment through the bank's treasury workstation, giving the beneficiary routing number, account number, amount, value date and reference. The sending bank validates the instruction, checks the account and the authority, and runs sanctions and fraud screening. If every check passes, the bank sends the payment to the Federal Reserve as an ISO 20022 message, a pacs.008 for a customer payment or a pacs.009 for a payment between financial institutions. The message carries the debtor, the creditor, the debtor agent, the creditor agent, the amount, the purpose and the end to end reference. Settlement happens in a single moment. The Federal Reserve checks the sending bank's balance in its master account at the Fed. If the balance is enough, the Fed debits the sending bank and credits the receiving bank in the same instant, and the payment status moves to settled. The receiving bank credits the beneficiary account and returns a pacs.002 payment status report confirming settlement. From instruction to final settlement the elapsed time is measured in seconds, and once the Fed has moved the money the payment is final and irrevocable. No other party can reverse it, and the sending bank cannot recall it. That finality is the reason Fedwire is used for trades and property: the receiving party can rely on the money the moment it arrives. The debit and credit entries are worth writing down, because they show why Fedwire is safe. On the books of the Federal Reserve, the sending bank's account is debited 2.5 million dollars and the receiving bank's account is credited 2.5 million dollars. On the books of the sending bank, the customer's account is debited 2.5 million dollars and its account at the Fed is credited back in the same entry, because the bank has paid out of its own central bank balance. On the books of the receiving bank, its account at the Fed is debited and the beneficiary's account is credited 2.5 million dollars. Every entry balances, and the money never leaves the Federal Reserve's books during settlement, which is why there is no settlement risk between the two banks. Liquidity is the cost of real time settlement, and it is the first thing treasury teams manage. Banks must hold enough balance in their Federal Reserve account to fund the payments they send, and they manage this balance through the day, using incoming payments to fund outgoing ones. A large Fedwire payment can be queued if the sending bank does not have enough balance at that moment, and the queue is managed in the order payments were submitted, so a queued payment is sent, not settled, and its status must be tracked until settlement confirms. The Federal Reserve provides intraday liquidity facilities, and banks also use the discount window in extremis, but the normal discipline is to forecast the day's outflows, hold a buffer, and release large payments only when the balance covers them. An analyst must design the queue view so operations can see a queued payment, its position in the queue, and the exact funding shortfall that is holding it. Operating hours and cutoffs are the hard deadlines that operations teams watch closely. Fedwire operates on business days during extended hours, opening in the evening of the previous day and closing in the evening of the current day in US Eastern Time. A payment sent after the closing cutoff waits until the next operating day, so treasury and operations teams plan around it, and the analyst must show it in the product and in the operations manual in Eastern Time. The messages carry rich information about the originator, the beneficiary and the purpose of the payment, which helps reconciliation and screening, and the analyst must understand the difference between a payment sent and a payment settled, because only settlement gives finality. A customer told that a payment was sent may assume it has arrived; the screen must distinguish sent, queued and settled. Exceptions in Fedwire are reported with ISO 20022 status and return messages, and each one has a distinct handling path. A reject happens before settlement, when the payment fails validation or screening, for example an invalid routing number, a closed account, a sanctions hit, or a missing mandatory field, and it is reported with a pacs.002 status report carrying a reject code. The sending bank must correct the instruction and resubmit it before the cutoff if the payment is still needed that day. A return happens after receipt, when the receiving bank cannot apply the payment, and the funds come back with a pacs.004 payment return message. A recall is a request to cancel a payment, sent before settlement, and once the Federal Reserve has settled the payment it is final and irrevocable, so a recall after settlement will be refused and the only recovery is a new payment from the beneficiary. Duplicates are a real operational risk that the analyst must design against. If the same payment is sent twice, the beneficiary is paid twice, so the sending bank must check for duplicate references, amounts and beneficiaries before release, and must never resend a payment whose status is unknown. The correct procedure when a pacs.002 confirmation has not arrived is to trace the payment first, confirm whether it settled, and only then decide whether to resend. Resending blindly is how a 2.5 million dollar payment becomes a 5 million dollar payment, and the recovery then depends on the goodwill of the beneficiary. The ISO 20022 migration changed the message format but not the settlement model. Fedwire moved to ISO 20022 in July 2025, in a single cutover rather than a phased coexistence, which meant banks had to be ready on the day or stop sending payments. The new messages carry structured party information, structured remittance data, purpose codes and the same field definitions as the cross border pacs.008 and pacs.009 messages. A payment that travels from a US bank through Fedwire and then cross border through SWIFT now carries consistent data throughout, which improves screening, reduces false positives and makes reconciliation faster. The analyst's requirements should reference the Federal Reserve's Fedwire ISO 20022 usage guidelines, not the old proprietary format. A worked example with charges makes the economics concrete. A corporate customer sends a 2.5 million dollar Fedwire payment. The sending bank charges the customer a wire fee, typically 15 to 30 dollars for an outgoing domestic wire, and the receiving bank may charge a smaller incoming wire fee. The liquidity cost is separate and larger: the sending bank must hold 2.5 million dollars in its Federal Reserve account until the payment settles, and that balance earns no return while it sits there. For a payment of this size the fee is trivial and the liquidity is the real cost, which is why Fedwire is reserved for payments that justify both. Sending a 200 dollar retail payment through Fedwire would be expensive and wasteful, and the analyst should make sure the product routes small payments elsewhere. The analyst working on Fedwire must check five things. First, the ISO 20022 message fields, because the migration changed field names, lengths and validation rules. Second, the cutoff times in Eastern Time, stated in the product, the customer journey and the operations manual. Third, the queue and liquidity behaviour, so operations can see a queued payment, its position, and why it is waiting. Fourth, the reject and return paths, so a rejected payment is corrected and resubmitted in time, and a returned payment is reconciled and the customer is told what happened. Fifth, the finality rule, so nobody promises to stop or recall a Fedwire payment after it has settled, and the customer communication says so plainly.