Insights Contact

Payment Rails

Instant Payments Runbook: RTP and FedNow, From Requirements to 24/7 Support

By SP Sankar

Instant payments move money in seconds, any time, every day of the year. That speed changes how you build, test, release and support a product. This is how I take an RTP or FedNow change from idea to live, safely.

New here? Start with How a US Payment Works: 15 Steps Inside a Bank, then come back for the detail.

How an instant payment moves

How an instant payment movesCredit push only, 24/7/365, final in secondsStep 1PayerSends from app,online or APIStep 2Sending bankFraud, OFAC,limits, liquidityStep 3RTPor FedNowRoutes and settlesin secondsStep 4Receiving bankAccepts or rejectswithin secondsStep 5PayeeMoney availableat onceEverything happens in seconds, every day of the yearReal-time fraud scoring · payee confirmation · limits · liquidity alerts · 24/7 support
How an instant payment moves

Read from left to right. Each box is one step of a single instant payment, and the whole trip takes seconds, day or night. The band at the bottom shows what must work in real time. Once the receiving bank accepts, the payment is final.

RTP and FedNow in one minute

The US has two instant payment networks, and most large banks connect to both. In both, only the sender can start a payment, so nobody can pull money from you. Both run every hour of every day, and both use ISO 20022 messages.

TopicRTP networkFedNow Service
OperatorThe Clearing HouseFederal Reserve Banks
Launched2017July 2023
Limit per payment$10 million (since February 2025)$10 million network limit (since November 2025)
2025 activityMore than $1.3 trillionAbout 8.4 million payments, $853.4 billion
ParticipantsAbout 1,135 (January 2026)More than 1,500

Sources: The Clearing House and Federal Reserve Financial Services announcements.

Two things that change everything

It never closes. There is no quiet night, weekend or holiday for a release or a fix. Releases must happen without switching anything off. Support must be there around the clock. And the bank’s balance must cover payments at 3 a.m. on a Sunday, when Fedwire is closed.

It is final in seconds. Once the receiving bank accepts, the money is gone. You can only ask for it back. So fraud checks, payee checks and limits must all run in a split second, before sending.

The main risk is a scam where a criminal tricks the customer into sending the money themselves. This is called an authorized push payment, or APP, scam. The defense: clear “this can’t be undone” warnings, showing the payee’s name before sending, and instant fraud checks.

Building it: short cycles, firm checkpoints

  • Receive first, then send. Most banks go live receiving payments first, then add sending once fraud checks and funding (liquidity) are proven.
  • Test speed as hard as accuracy. Run load tests for hours at twice your busiest traffic, with every fraud and OFAC check switched on.
  • Pass the network’s tests. Both networks make you pass their own tests before go-live.
  • Prove it live, day and night. Receive and send $1 pilot payments, complete a return request, and repeat on a weekend to prove 24/7 support.
GateDone when
E2E exitNetwork tests passed, 95% or more of our tests passed, fast enough at the busiest time, every message type works
UAT exitBusiness scenarios signed; 24/7 operations tested, including a weekend shift
Go-livePilot payments checked, fraud checks and limits on, low-funds alerts live, switch to the backup site (DR failover) tested

Running it live

L1 is a 24/7 operations team. L2 and L3 are on call. Send alerts to Slack or Teams when the network link drops, rejections or time-outs rise, responses slow down, funds run low, or a certificate is about to expire. Recovery must take minutes, not hours, with no lost payments. So run two live sites, or switch over automatically, from day one.

Download the full runbook (PDF, 13 pages)

Every phase in detail, with RTP and FedNow facts, ISO 20022 messages, rules, exit criteria and sign-off, a live pilot plan, real-time controls, liquidity, 24/7 support, incident runbooks, disaster recovery and audit checklists.

Download the PDF

The files behind this runbook

Every part of this runbook touches the same handful of files. Here is where each one shows up. For what is inside each file, with samples and a step-by-step checklist, see RTP, file by file and FedNow, file by file.

File or momentWhere it matters in this runbook
API request with an idempotency keyHow an instant payment moves
pacs.008 and pacs.002RTP and FedNow in one minute
Fraud checks in secondsTwo things that change everything
camt.056, camt.029 and pacs.004Running it live: return requests
Settlement reports, 24/7Running it live: reconciliation

More payment runbooks

What I’d tell any team going live on RTP or FedNow

Instant payments reward teams that plan for always-on from day one: releases with no downtime, fraud checks in milliseconds, funds that never run dry, and a support rota that covers every hour.

Working on a payments project?

I help banks and fintechs deliver real-time payments, ISO 20022, and AI-driven AML and compliance change, from strategy to go-live.

Connect on LinkedInSee how I can help