Instant payments are becoming the expectation—not the exception. The FedNow Service is one of the major rails making that possible in the U.S., allowing banks and credit unions to offer real-time account-to-account payments that settle within seconds, 24/7/365, with immediate funds availability for the receiver.
This guide breaks down what FedNow is, how the payment flow works, common business use cases, and the operational details that matter when you’re planning adoption.
What FedNow is (and what it isn’t)
FedNow is an interbank instant payment service. It’s built so banks and credit unions can send and receive instant payments on behalf of their customers. Individuals and businesses don’t “sign up for FedNow” directly—your financial institution enables it through its own app, online banking, or business payment tools.
It’s also not a new currency and not an “app.” It’s infrastructure that moves money between financial institutions in real time.
The core promise: speed, certainty, and immediate availability
With instant payments, the receiver can use the funds immediately, which can be a big deal when timing matters (covering a bill on the due date, receiving payroll, or getting paid on an invoice without waiting days).
FedNow launched in July 2023 and is designed to support continuous operation all year long.
How an instant payment moves through FedNow (high level)
A standard FedNow credit transfer generally follows this flow, in seconds:
- A sender initiates a payment using their bank/credit union’s interface.
- The sender’s financial institution (or its service provider) submits the payment message into the service.
- The service validates message format and routing details.
- The receiver’s financial institution confirms it can accept the payment (helping reduce misdirected payments).
- Settlement occurs by debiting/crediting the participants’ Federal Reserve master accounts (or their correspondents).
- The receiver’s financial institution credits the receiver’s account and makes funds available immediately.
A key operational detail: settlement occurs in the participant’s master account and is designed to be complete, final, and irrevocable, which reduces interbank credit risk.
Capabilities and features you should know
Request for Payment (RFP)
Beyond sending a payment, the service supports Request for Payment messaging—useful for scenarios like bill payment, invoicing prompts, and “pay me now” workflows (depending on how your financial institution implements it).
ISO 20022 messaging
The service uses ISO 20022 message standards, which can help with richer payment data (like remittance details) and more consistent processing.
Liquidity and correspondent options
Not every institution settles the same way. The service supports correspondent–respondent settlement relationships and includes liquidity tools designed for a 24/7/365 environment.
Transaction limits: default vs. maximum
FedNow includes limits at the network and participant levels:
- Participants typically start with a default limit of $100,000, adjustable up or down based on risk needs.
- The credit transfer value limit was $1,000,000 and (per official product guidance) increased to $10 million in November 2025, expanding higher-value use cases like certain real estate and corporate payments.
Real-world use cases for businesses and consumers
Because it’s “use-case agnostic,” the service can support a wide range of payment scenarios, including:
- Consumer bill pay (especially last-minute payments)
- Payroll and earned wage access
- Invoice payments and B2B supplier payments
- Real estate-related payments
- Me-to-me transfers across accounts
For businesses, the big operational win is often cash-flow visibility and reconciliation—getting paid instantly with supporting data can simplify tracking and reduce time spent chasing payments.
Risk and fraud controls matter even more with “instant”
Instant settlement is great—until a fraudulent payment slips through, because reversal isn’t as simple as it is with slower rails. That’s why FedNow outlines built-in and configurable risk tools, including:
- participant-defined negative lists
- value and velocity thresholds by customer segment
- a network intelligence API for risk insights before sending
- adjustable limits at both network and participant levels
Your financial institution still plays a major role in screening and policies; the service supports the tooling, but governance and monitoring happen at the participant level.
The “behind-the-scenes” detail teams forget: cycle dates and reporting
Even though payments run 24/7/365, operational reporting has structure. The service’s cycle date can differ from the calendar date for a window of time because it aligns with the Fedwire Funds Service business day (including the typical evening close time). This matters for reconciliation, end-of-day reporting, and internal controls.
A practical checklist to get ready
If you’re evaluating or rolling out instant payments, focus on:
- Customer use cases first (bill pay, payroll, B2B, real estate, etc.).
- Risk policy and limits (segment-based thresholds, default limit strategy).
- Exception handling (returns/requests for status/info using ISO 20022 nonvalue messages).
- Liquidity planning for always-on settlement.
- Ops + reconciliation (how reporting lines up with your accounting day).
- Integration approach (direct participant connection vs. using a service provider).