
⏱ 2-minute read · open “Read more” for the details
Money can now move between US banks in seconds, any time of day, any day of the year. Two networks make this happen: RTP and FedNow. Both can now send up to $10 million in a single payment.
Customers always ask one question: when will my money arrive? For years the answer was “tomorrow, if you send it before the cut-off.” Now it can be “in a few seconds.” But making that safe takes a lot of work behind the scenes.
In this post, I explain the two networks, how a payment moves through a bank, the steps every payment goes through, and the key lessons for building it.
The two instant payment networks
Acme Supplies needs to pay Maria Lopez $2,500 for invoice 4471 today, even though it is Sunday. Two US networks can do it in seconds.
- RTP, run by The Clearing House.
- FedNow, run by the Federal Reserve.
- Both work 24/7, settle each payment on its own, and take up to $10 million.
Read more: The two instant payment networks
The US has two networks that move money between banks instantly. They work in a similar way: each payment is settled on its own, in seconds, and it is final.
| Feature | RTP | FedNow |
|---|---|---|
| Run by | The Clearing House, a company owned by large US banks | The Federal Reserve, the US central bank |
| Most you can send at once | $10 million | $10 million |
| When it works | 24 hours a day, every day | 24 hours a day, every day |
| How money moves | The sender pushes the money. The receiver can send a “request for payment,” but the sender must approve it. | Same as RTP |
| Message format | ISO 20022 (a newer, richer format for payment messages), a global standard | ISO 20022, a global standard |
RTP is the busiest. About $195 billion a month now moves on RTP, up from about $28 billion a month just over a year earlier. On its record day, it handled 2.27 million payments worth $8.62 billion.
FedNow reaches the most banks. More than 1,500 banks and credit unions in all 50 states use it. But many of them can only receive payments, not send them, so check before you rely on it.
Read the six boxes from left to right. The customer starts the payment. For a business payment, the company’s payments manager (or another authorized approver) approves it. The bank checks for fraud, money laundering, sanctions and balance, and sets the money aside. Then it sends the payment (a pacs.008 message) to RTP or FedNow, and the receiving bank credits it in seconds. The dashed line is the answer coming back (pacs.002). If accepted, the debit becomes final. If rejected, the money is released back to the customer.
For technical readers:
Sending a payment: your bank does the work first
Before RTP or FedNow sees Acme’s payment, its bank does the work.
- It confirms who is paying.
- It runs fraud, sanctions and balance checks at the same time.
- It sets the money aside, picks the network and sends the payment.
Read more: Sending a payment: your bank does the work first
When your customer sends money, the bank checks it, sets the money aside and picks the network, all before RTP or FedNow sees it.
- The customer pays. They use their banking app and enter the other person’s account and routing number. Businesses can also upload a file with many payments at once.
- The bank confirms who they are. For business payments, the company’s payments manager (or another authorized approver) must also approve.
- The bank runs its checks, all at the same time. Is this fraud? Is anyone on a sanctions list? Is there enough money?
- The bank sets the money aside. This makes sure it never sends money the customer does not have.
- The bank picks the network. It checks whether the other bank can be reached on RTP, FedNow or both.
- The bank sends the payment to the network.
- The network passes it on to the other bank, which puts the money in the receiver’s account.
- The network confirms the payment went through, or says why it failed.
- The bank finishes the job. It takes the money from the customer’s account, or releases it if the payment failed, and tells the customer.
Receiving a payment: only seconds to decide
When the payment reaches Maria’s bank, a clock starts.
- The bank must say yes or no within seconds.
- If it is too slow, the payment fails, even if nothing was wrong.
Read more: Receiving a payment: only seconds to decide
When money arrives from another bank, a clock starts. Your bank must say “yes” or “no” within seconds.
FedNow has this clock built in, so that no payment is ever left waiting. If the bank is too slow, the payment fails, even if nothing was wrong with it.
In those few seconds, the bank checks for fraud and sanctions and finds the right customer account, all at the same time. Then it sends its answer back, records every step, and puts the money in the customer’s account, ready to use right away. Any slow step means failed payments and unhappy customers.
What happens to a payment: the statuses
Every payment moves through clear statuses.
- Initiated, screening, sent, completed.
- Side paths: on hold, rejected or returned.
- Shared statuses help customers and support speak the same language.
Read more: What happens to a payment: the statuses
Every payment moves through clear steps. Knowing them helps customers, support teams, and operations teams speak the same language.
Read the blue boxes from left to right. This is the normal life of a payment, from started to completed. The dashed arrows lead down to the gray boxes, the side paths. A payment can be cancelled before it’s sent, held for a person to check, rejected, or left with an unknown status until the bank asks the network. After it settles, the only way back is a return request, as the bar at the bottom says.
For technical readers:
| Status | What it means |
|---|---|
| Scheduled | The customer set the payment for a later date. The bank keeps it and sends it on that day. |
| Initiated | The customer has created the payment. |
| Pending approval | A business payment is waiting for the company’s payments manager to approve it. |
| Screening | The bank is checking for fraud, money laundering and sanctions, and confirming there is enough money. |
| On hold | Something needs a person to look at it before it can go on. |
| Funds held | The money is set aside in the customer’s account. |
| Sent | The bank has sent the payment to RTP or FedNow. |
| Status unknown | No answer came back in time, so the bank asks the network what happened. |
| Settled | The network confirms the money has moved. It is final and cannot be taken back. |
| Completed | The bank has finished its own work: the account is updated and the customer is told. |
| Rejected | The payment did not go through, and the held money is released. |
| Cancelled | The customer or approver stopped it before it was sent. |
| Return requested | The sender asks for the money back after it settled. |
| Returned / Return refused | The receiving bank either sends the money back or says no. |
The most important point: once a payment is settled, it cannot be cancelled. The only way back is to ask the other bank to return it, and they can refuse.
The messages behind each step
Behind each step is a short ISO 20022 message.
- pacs.008: the payment itself.
- pacs.002: “yes, done” or “no”.
- pacs.028: “what happened to my payment?”
Read more: The messages behind each step
RTP and FedNow both speak ISO 20022, a global standard for payment messages. Each message has a short name. The first part tells you the family: pacs moves money between banks, pain carries customer requests, camt handles questions and fixes, remt carries invoice details, and admi is admin from the network.
To make it easy to follow, picture one payment: Acme Supplies pays Maria Lopez $2,500 for invoice 4471.
| Message | In plain words | In my example |
|---|---|---|
| The payment itself | ||
| pacs.008 | The payment | Acme’s bank sends $2,500 to Maria’s bank through RTP or FedNow. |
| pacs.002 (accepted) | “Yes, done.” | Maria’s bank accepts it and the money settles. Acme’s debit becomes final. |
| pacs.002 (rejected) | “No.” | Maria’s bank refuses it, for example because the account number is wrong. Acme’s money is released. |
| When no answer comes back | ||
| pacs.028 | “What happened to my payment?” | No reply arrived in time, so Acme’s bank asks for the status instead of sending the payment again. |
| Getting money back after it settled | ||
| camt.056 | “Please send it back.” | Acme paid the same invoice twice, so its bank asks Maria’s bank to return the money. |
| camt.029 | “We won’t return it.” | Maria’s bank says no. Acme must sort it out with Maria directly. |
| pacs.004 | “Here’s your money back.” | Maria’s bank agrees and returns the $2,500. (FedNow uses this message. On RTP, the bank sends a new payment that points to the original.) |
| Request for Payment | ||
| pain.013 | “Please pay me.” | Maria’s bank asks Acme to pay invoice 4471. No money moves yet. |
| pain.014 | The answer to the request | Acme accepts (a payment will follow) or declines. |
| Questions about a payment | ||
| camt.026 | “I need more details.” | Maria’s bank cannot tell what the money is for and asks for the invoice number. |
| camt.028 | “Here are the details.” | Acme’s bank replies: invoice 4471, October services. |
| camt.035 | “Got your message.” | Confirms a non-payment message arrived (used on RTP). |
| Invoice details | ||
| remt.001 | The invoice breakdown | Invoice 4471 was $2,600, minus a $100 discount, so $2,500 paid. Useful when one payment covers many invoices. |
| Admin messages from the network | ||
| admi.998 | The daily list of banks | Shows which banks can be reached and what they can do. For example, Maria’s credit union can receive but not send. |
| admi.004 | A notice to all banks | “Maria’s bank is offline for maintenance.” Payments to it will be rejected until it is back. |
| admi.002 | “We couldn’t read your message.” | The network itself rejects a badly formed message. This is different from Maria’s bank saying no. |
The key point: a payment that goes well needs only two messages, pacs.008 and pacs.002. All the others are for when something goes wrong or more information is needed. That is where most of the work goes.
FedNow and RTP: same language, different dialect. Both use these ISO 20022 messages, but each has its own rules for versions, required fields, codes and the message envelope. One clear difference: FedNow has its own return message (pacs.004). On RTP, the money goes back as a new payment that points to the original.
Download the sample files
Matching FedNow and RTP sets for the Acme → Maria example, one XML file per message, with a README that compares the two networks.
⬇ Download sample XML files (ZIP)
Simplified learning samples with made-up data. They show the structure and purpose of each message, but they are not certified FedNow or RTP messages and some codes are placeholders. For real builds, use the official usage guidelines from the Federal Reserve and The Clearing House.
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 moment | Where it matters in this runbook |
|---|---|
| API request and idempotency key | Sending a payment: your bank does the work first |
| pacs.008 and pacs.002 | The messages behind each step |
| Receiving in seconds | Receiving a payment: only seconds to decide |
| camt.056, camt.029, pacs.004 | What happens to a payment: the statuses |
Five lessons for building it
Five lessons from building instant payments.
- Run checks side by side.
- Hold first, send second, post last.
- Plan for “we don’t know yet”.
- Keep a team on watch around the clock.
Read more: Five lessons for building it
- Use the network’s language at the edge. FedNow connects banks through IBM MQ (software that passes messages between systems), a message queue, over the Fed’s private network. The bank cannot choose something else there. Inside the bank, a modern event system like Kafka works well. A payment gateway connects the two.
- Run checks side by side. Fraud, sanctions and balance checks must happen at the same time. One after another is too slow for a deadline of a few seconds.
- Hold first, send second, post last. Set the money aside, send the payment, and make the debit final only after the network confirms. If the payment fails, release the hold.
- Plan for “we don’t know yet”. Sometimes no answer comes back. The bank must ask the network for the status instead of guessing, and must never send the same payment twice.
- Build a global team that never sleeps. A payment sent on a Sunday night needs someone who can fix a problem on Sunday night, so you need a globally distributed support team working 24/7/365.
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