FedNow: instant payments around the clock

FedNow Service is the Federal Reserve's instant payment system, launched in July 2023. It is the biggest change to US retail payments in decades: participating banks and credit unions can send and receive payments in seconds, twenty four hours a day, seven days a week, including weekends and holidays. A customer can send money at midnight on a Sunday and the beneficiary account is credited within seconds, with interbank settlement also happening immediately in central bank money. This is a major difference from ACH, where the customer experience can look fast but the underlying settlement takes a day or more, and from Fedwire, which is instant but only during business hours. Follow one payment end to end. A gig worker finishes a shift at 11pm on a Sunday and is owed 850 dollars. The platform instructs the payment from its bank, giving the worker's routing number, account number and the amount. The sending bank checks the balance, the customer limit and the fraud rules in real time, because there is no later window to stop it. If the checks pass, the sending bank sends a pacs.008 customer credit transfer message to the FedNow Service, using ISO 20022. The FedNow Service validates the message and forwards it to the receiving bank. The receiving bank checks the account, credits the worker 850 dollars within seconds, and returns a pacs.002 payment status report confirming acceptance. The sending bank shows the platform a confirmation, and the worker sees the money in the account before midnight. Each step has a clear status, and the payment is only complete when the receiving bank has credited the account and confirmed it back. The time budget is the whole design. From instruction to beneficiary credit the elapsed time is measured in seconds, and the service is built so that every check, fraud screening, sanctions screening, balance check and account validation, completes in real time before the payment is released. A bank that screens in minutes cannot offer instant payments, because the receiving bank will not wait. The analyst must confirm the latency budget with each team that owns a check, and must design the failure behaviour when a check cannot complete in time: the payment is rejected cleanly rather than left pending, and the customer is told immediately. The transaction limit has a history the analyst should know. At launch in July 2023 the FedNow network maximum was 500,000 dollars per payment. The Federal Reserve raised the network maximum to 1 million dollars on 24 June 2025, and then to 10 million dollars effective November 2025 (announced 9 September 2025). The participant default limit stayed at 100,000 dollars; a bank may set a higher limit for its own customers up to the network maximum. The 10 million dollar maximum is high enough for most business use cases while keeping the system focused on retail and commercial payments rather than the largest wholesale transfers that belong on Fedwire. Banks may set lower limits for their own customers, and the limit can vary by channel and by customer segment, so the product must show the applicable limit before the customer types the amount, and must give a clear error with the alternative rail when the amount is above it. Liquidity works differently on FedNow, because settlement never stops. Banks hold a balance in their Federal Reserve master account, and FedNow settlement draws on that balance around the clock, including nights, weekends and holidays. Banks manage this with liquidity management transfers, which move funds into the FedNow settlement position ahead of weekends and holidays, and with alerts that warn operations when the balance runs low. A payment that arrives when the sending bank has insufficient funds is rejected rather than queued for hours. The analyst must design the funding and alerting rules with treasury, because a bank that runs out of FedNow liquidity on a Sunday night cannot wait until Monday morning, and every payment after that point will fail until the balance is topped up. FedNow is designed for a wide range of use cases beyond person to person transfers. Businesses can use it to pay suppliers instantly, to disburse funds to gig workers at the end of a shift, to settle insurance claims quickly, and to move money between their own accounts at different banks. The service supports request for payment, which lets a biller ask a customer to pay and lets the customer approve the payment in their banking app. Request for payment turns a pull into an approved push, which avoids the unauthorised debit disputes that ACH debits attract, and it is the feature an analyst should reach for when the business needs to collect from customers on demand. Exceptions on FedNow move at the same speed as the payments, and the handling must be designed for seconds, not days. A reject happens before settlement, when the payment fails validation, the receiving bank does not participate, the account is closed, or the fraud screen stops it, and it is reported with a pacs.002 status report. 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 get the money back after it was credited, sent as a camt.056 cancellation request, and the receiving bank answers with a camt.029 resolution, which can accept or refuse, because a settled instant payment is final and the beneficiary must consent before the money comes back. A timeout is the exception the analyst must plan for most carefully. If no pacs.002 arrives within seconds, the payment is in an unknown state: it may have settled and the confirmation may have been lost, or it may never have been sent. Operations must trace it before deciding whether to resend, because resending blindly risks a duplicate payment. The correct procedure is to query the FedNow Service for the payment status using the end to end reference, wait for a definitive answer, and only then resend. The product must show the payment as pending investigation, not as failed, until that answer arrives, and the customer communication must say the same. Fraud control and fallback design decide whether a FedNow launch succeeds. A payment that settles in seconds leaves no time to stop it if fraud is detected after the fact, so real time fraud screening before the payment is sent is essential, with limits per customer and per transaction and velocity checks that catch a burst of payments to new payees. Not every bank is on FedNow yet, so a payment flow needs a fallback to ACH or Fedwire when the receiving bank does not participate, and the fallback must be visible to the customer before they confirm, with the timing and the cost stated plainly. A payment that silently falls back to next day ACH when the customer expected seconds is a complaint waiting to happen. A worked example with the full cost makes the trade off concrete. The gig platform pays 850 dollars at 11pm on a Sunday. The sending bank charges the platform a small per payment fee, typically well under a dollar for an instant payment, and there is no separate receiving fee for the worker. The liquidity cost is the balance the bank must hold in its Federal Reserve account overnight to fund instant payments, which treasury manages with a liquidity management transfer on Friday afternoon ahead of the weekend. Compare that with ACH: the fee would be lower, but the worker would not see the money until Tuesday, and the platform would carry the support cost of workers asking where their pay is. For this use case the instant payment is worth the funding cost. The analyst checklist for FedNow is strict: confirm the transaction and customer limits, including the 100,000 dollar participant default, the 10 million dollar network maximum, and any lower bank limit; build real time fraud screening into the flow before release; design the timeout and duplicate handling so no payment is resent blindly; agree the liquidity and alerting rules for nights, weekends and holidays with treasury; build the fallback to ACH or Fedwire for non participating receiving banks; and design the status screens so a payment shows as sent, settled, rejected, returned or under investigation, never as a vague pending.