Focus area guide

Real-time payments for community banks

FedNow, RTP, receive-only, send, fraud, liquidity. A plain-English guide to the decisions in front of you, and the questions to ask before you sign anything.

Last reviewed November 2026

Why it matters now

Customers already expect money to move instantly. They see it in consumer payment apps and they increasingly expect it from their bank, for paychecks, transfers between their own accounts, and payments to and from businesses.

For community banks, instant payments are less about a single product and more about staying in the flow of money. When an employer, insurer, or marketplace sends funds instantly, your bank needs to be able to receive them, or the customer notices.

The good news: you do not have to do it all at once. Most community banks start by receiving, learn how 24/7 operations really work, then add sending.

FedNow vs. RTP

The U.S. has two instant payment networks. They do the same basic job and look similar to customers. The differences show up in operations and cost.

FedNow ServiceRTP network
OperatorFederal ReserveThe Clearing House
LaunchedJuly 2023November 2017
Availability24/7/36524/7/365
Payment typeCredit push, irrevocableCredit push, irrevocable
SettlementIn Federal Reserve master accounts, directly or through a correspondentThrough a prefunded joint account held at the Federal Reserve
MessagingISO 20022ISO 20022
Request for paymentSupportedSupported

Transaction limits, fees, and features change. Confirm current details with each operator and your provider.

In practice, the network decision is often made by your core provider or payment processor. The more useful question is which networks the people sending money to your customers are on, and how easily your provider lets you add the other one later.

Receive-only or send?

Receive-only

  • Customers can accept instant payments from anyone on the network.
  • Lower fraud exposure, since nothing leaves the bank instantly.
  • Fewer changes to online and mobile banking.
  • Still requires 24/7 posting and someone watching settlement balances.

Send and receive

  • Customers can pay others instantly, including business payouts and payroll.
  • Opens request for payment use cases like bill pay.
  • Needs real-time fraud screening, limits, and clear customer confirmation steps.
  • Needs a plan for weekend and holiday liquidity.

Questions to ask providers

Bring these to every demo. The answers separate providers that are truly ready from the ones that are ready on a slide.

  1. Does it really post in real time on our core?

    Instant payments arrive at 2 a.m. on Sunday. Ask how and when balances update, and what happens if the core is in a batch window.

  2. FedNow, RTP, or both?

    Ask which networks are supported today, which are on the roadmap, and whether adding the second one later is a configuration change or a new project.

  3. Can we start receive-only and add sending later?

    Confirm the upgrade path, what it costs, and what changes for staff and customers when you turn sending on.

  4. How is fraud handled on outgoing payments?

    Look for real-time screening, configurable limits by customer and channel, and clear alerts. Ask what other banks on the platform have seen.

  5. How do 24/7 liquidity and settlement work for us?

    Understand how settlement is funded, who monitors balances on weekends and holidays, and what happens when a limit is hit.

  6. What is the full cost?

    Get per-transaction fees, monthly minimums, implementation costs, and network fees in writing. Then compare with what peers actually pay.

  7. What will customers see?

    Ask for the online and mobile banking experience, and whether business use cases like payroll, payouts, and request for payment are supported.

Where banks stall

Most real-time payment projects do not fail. They stall. The usual reasons:

  • The core is not ready. Real-time posting, overnight batch windows, and balance updates are the most common blockers, and they are outside the bank's direct control.
  • Nobody owns weekends. Exceptions, fraud alerts, and settlement monitoring do not wait for Monday. Staffing and procedures need a plan.
  • Fraud fears freeze the send decision. Irrevocable payments raise the stakes. Clear limits and screening rules make the decision manageable.
  • No clear business case. Start with a specific use case your customers already ask for, such as instant payouts for business customers or account-to-account transfers.

How Innovation Magnet helps

We are not a vendor and we do not sell a real-time payments product. We help TBA member banks make the decision well:

  • Peer references. Talk with community banks already live on FedNow or RTP, ideally on your core.
  • Vendor fit assessments. See which providers actually work with your core and processor before you commit.
  • Pricing intel. Know what other banks pay, so you can negotiate from facts.

Start a conversation

Frequently asked questions

What is the difference between FedNow and RTP?

Both are instant payment networks that move money between U.S. bank accounts in seconds, 24/7/365, with final settlement. FedNow is operated by the Federal Reserve and launched in July 2023. The RTP network is operated by The Clearing House and launched in November 2017. They differ mainly in how settlement is funded, pricing, and which institutions are already reachable.

Does a community bank need to join both networks?

Not necessarily. Many banks start on one network, usually the one their core or payment processor supports best, and add the other later. What matters most is whether your customers can receive the payments they are being sent, and that depends on which networks the senders use.

What does receive-only participation mean?

A receive-only bank can accept instant payments into customer accounts but cannot originate them. It is the most common starting point because it carries less fraud and liquidity risk and requires fewer changes to online banking. Sending can be added once operations are ready.

Can an instant payment be reversed?

No. Instant payments on both networks are irrevocable once settled. Mistakes and fraud are handled through return requests that the receiving bank may or may not honor, which is why fraud controls and customer confirmation steps matter before a bank turns on sending.

How long does implementation take?

It depends mostly on your core provider and processor. Banks whose providers already support real-time posting can move quickly. Banks that need core changes, new 24/7 procedures, or a new connection provider take longer. Talking to a peer bank on the same core is the fastest way to get a realistic timeline.

Planning a real-time payments project?

Tell us where you are. We will connect you with vetted providers and peers who have already gone live.