FedNow — Federal Reserve Instant Payments
Overview
FedNow is the Federal Reserve's instant payment service, launched in July 2023. It enables financial institutions of all sizes — from the largest national banks to the smallest community banks and credit unions — to offer their customers real-time account-to-account payment capabilities, 24 hours a day, 7 days a week, 365 days a year.
FedNow is built natively on ISO 20022 from the ground up — unlike Fedwire, which migrated to ISO 20022 in 2025, FedNow has used the standard since inception. Payments settle in seconds with immediate finality. Like RTP, FedNow is a credit-push only system — no pull/debit transactions.
Why FedNow? The Federal Reserve's Role
The Federal Reserve entered the instant payments market because TCH's RTP, while effective, is privately owned by the largest US banks. Community banks and credit unions expressed concern about reliance on a competitor-owned infrastructure. FedNow provides a neutral, Fed-operated alternative that directly leverages existing Federal Reserve master account relationships — simplifying settlement for smaller institutions.
System Architecture
| Attribute | Detail |
|---|---|
| Settlement model | Gross, real-time, instant. Settled directly through participating institution's Federal Reserve master account (or pass-through settlement via a correspondent). |
| Message standard | ISO 20022 — pacs.008 (Credit Transfer), pacs.028 (Status Request), pain.013 (RfP) |
| Connectivity | FedLine network (same secure connection used for Fedwire). Institutions connecting via a correspondent use their correspondent's FedLine connection. |
| Participant types | Send-and-receive participants (full), or receive-only participants (accept FedNow credits but cannot originate) |
| Operating hours | 24/7/365 — mandatory for all participants |
| Request for Payment | Supported via pain.013 message |
Participate via Direct Connection or Correspondent
| Participation Type | How It Works | Best For |
|---|---|---|
| Direct Participant | Institution has its own Federal Reserve master account and FedLine connection. Connects to FedNow directly. | Mid-to-large institutions with existing Fed infrastructure |
| Correspondent / Agent Access | Institution connects to FedNow through a correspondent bank or a FedNow-certified payment processor (e.g., core banking vendor). The correspondent holds the Fed account; settlement flows through the correspondent. | Community banks, credit unions, smaller institutions that do not maintain direct Fed master accounts |
Processing Flow
Sender
Initiates
Initiates
→
Sending Bank
Submits pacs.008
Submits pacs.008
→
FedNow
Routes
Routes
→
Receiving Bank
Accepts
Accepts
→
Settlement
(Fed Accounts)
(Fed Accounts)
- Sender Initiates: Customer initiates a credit transfer through the bank's channel (mobile, online banking, corporate payments portal). Specifies: receiving institution routing number, beneficiary account, amount, remittance information, and purpose (optional).
- Sending Bank Processing: The bank validates the payment instruction, performs OFAC screening, checks sender's account balance, confirms the Receiving Bank participates in FedNow, and constructs the ISO 20022 pacs.008 message.
- Submission to FedNow: The pacs.008 message is submitted to the FedNow service via FedLine. FedNow validates the message format and the Sending Bank's credit limit (available liquidity cap).
- Routing to Receiving Bank: FedNow routes the payment message to the designated Receiving Bank's FedLine connection.
- Receiving Bank Response: The Receiving Bank has a defined window (seconds) to accept the payment. If accepted: the bank posts the credit to the beneficiary account and sends a pacs.002 acceptance. If rejected: returns with reason code.
- Real-Time Settlement: FedNow simultaneously debits the Sending Bank's Federal Reserve master account and credits the Receiving Bank's Federal Reserve master account. Settlement is immediate, gross, and final.
- Confirmation: FedNow sends payment confirmation to the Sending Bank. The Sending Bank notifies the sender that the payment is complete.
Transaction Limits
| Limit | Amount | Notes |
|---|---|---|
| Default maximum per transaction | $500,000 | The Federal Reserve set a default cap of $500,000 per transaction. Institutions can set lower limits for their customers. |
| Elevated limit | Up to $1,000,000 | Eligible participants may request an elevated limit from the Fed for specific use cases (e.g., mortgage funding, large business payments) |
| Minimum | $0.01 | No practical minimum |
| Liquidity cap | Institution-defined | Each FedNow participant configures a liquidity management transfer (LMT) cap — a ceiling on FedNow outgoing volume relative to their Federal Reserve account balance. |
Liquidity Management
Because FedNow settles directly through Federal Reserve master accounts in real time, institutions must actively manage their intraday liquidity. Unlike ACH (which nets at end of cycle), every FedNow payment immediately moves funds in the Fed account.
Liquidity Management Transfer (LMT)
FedNow includes an automated Liquidity Management Transfer (LMT) feature. When a participating institution's FedNow balance (subset of Fed master account allocated for FedNow) falls below a defined threshold, an LMT automatically moves funds from the institution's Federal Reserve master account to the FedNow balance — ensuring continuous availability without manual intervention.
Operations Recommendation
Configure LMT thresholds conservatively during initial FedNow rollout. Monitor actual payment volume patterns over 30–60 days before optimizing thresholds. Insufficient liquidity results in FedNow payments being declined at submission — a poor customer experience that is avoidable.
Weekend and After-Hours Liquidity
- FedNow is 24/7/365, but Fedwire (used to pre-fund or move liquidity) is not. Pre-fund your FedNow liquidity position before Fedwire close on Friday (6:30 PM ET) to cover weekend payment volume.
- Monitor weekend transaction patterns and build a liquidity buffer based on historical weekend peak volumes.
- FedNow's LMT feature can be configured to draw from Federal Reserve account balances automatically — ensure this is enabled and tested before going live.
Compliance Requirements
OFAC Screening
- Mandatory pre-submission screening for all FedNow outgoing payments.
- Real-time screening must be integrated into the payment workflow — FedNow's speed (seconds) requires automated OFAC decisions, not manual review queues.
- Configure auto-hold rules for potential matches and ensure Compliance can access the hold queue 24/7/365 (or establish escalation procedures for after-hours holds).
FedNow Service Rules
- All FedNow participants must execute a FedNow Service Agreement with their Federal Reserve Bank.
- Participants are bound by the FedNow Service Terms and Conditions, which govern: message standards, response time requirements, dispute resolution, and settlement obligations.
- Receive-only participants must be capable of receiving and posting FedNow credits within the network's SLA window (typically under 20 seconds end-to-end).
Fraud Controls (24/7 Requirement)
- FedNow operates at all hours — including 2:00 AM Sunday. Fraud monitoring systems must be active 24/7/365.
- Automated rules-based fraud decisions (not manual reviews) are required for real-time payment approval.
- Implement velocity controls: maximum number of FedNow payments per customer per hour/day, maximum cumulative amount per day.
- First-time beneficiary controls: flag or step-up authenticate payments to first-time FedNow recipients above defined thresholds.
FedNow Adoption Status — 2026
As of early 2026, FedNow adoption has accelerated significantly from its July 2023 launch. Key milestones:
- Over 900 financial institutions connected to FedNow (vs. ~35 at launch)
- Community banks and credit unions represent a significant share of FedNow participants — consistent with the Fed's design intent
- Core banking vendors (Fiserv, FIS, Jack Henry) have all released FedNow integrations, enabling smaller institutions to participate via their existing core banking platform
- RTP and FedNow interoperability remains an industry goal but is not yet implemented — payments must be routed to the correct rail based on the Receiving Bank's participation
Dual-Rail Strategy
Most large US financial institutions participate in both RTP and FedNow. Payment routing logic in the core banking system must determine which rail to use for a given transaction based on: whether the Receiving Bank participates in RTP, FedNow, or both; customer preferences; and transaction amount (FedNow $500K default vs. RTP $1M).