Request for Payment on RTP and FedNow: Instant Billing Explained
Learn how a request for payment on RTP and FedNow lets you bill customers and receive final funds in seconds, and what it takes to offer it today.
On this page 7 sections
- What a Request for Payment Message Is
- How Request for Payment Works on RTP and FedNow
- RfP vs. Payment Links and Invoices
- Irrevocability: No Chargebacks, No Pull Debits
- Bank Support for RTP and FedNow Request for Payment Today
- Use Cases: Instant Invoice Payment, Deposits and Service Calls
- How to Start Sending Requests
A request for payment (RfP) on RTP or FedNow is a bill sent over an instant payment network directly into your customer's banking app. The customer taps approve, the money lands in your account within seconds, and it cannot be pulled back. The catch is reach. The customer's bank has to support receiving requests, and plenty of banks don't yet. Treat RfP as one payment option on an invoice, with card and ACH offered beside it.
What a Request for Payment Message Is
The Clearing House's RTP network and the Federal Reserve's FedNow Service are credit-push systems. Money moves only when the payer's bank sends it. Neither lets a business pull funds out of a customer's account the way an ACH debit does. That design is why the payments are fast and final. It also leaves billers with a gap: you can ask to be paid, but you can't collect.
The request for payment fills that gap. It is a non-value message, which means it carries information and no money. The Faster Payments Council has published industry guidance on these messages, and our summary of the Faster Payments Council's non-value message guide walks through what it means for merchants.
The message names your business, states the amount, sets a due date or expiration, and carries your invoice number so the payment matches the bill when it comes back. Other features are set by each network's message standard and by how each bank built its version. These include letting the payer change the amount, pay in parts, or attach a remittance note. Put those questions to your provider before you redesign your invoices around RfP.
How Request for Payment Works on RTP and FedNow
Your bank, or a payment provider connected to one, builds the request from your billing system or a web portal. To address it, you need the payer's account details or an identifier your provider matches to their account. Your bank sends the request across the network to the payer's bank, which displays it in online banking or the mobile app alongside the customer's other alerts. The payer then approves it, declines it, or lets it expire.
On approval, the payer's bank sends an instant credit transfer that references your request. Your bank credits your account, and the invoice reference arrives with the money, so posting the payment takes one step instead of a search through deposits.
Every approval is a separate payment the customer chooses to make. A request grants you no standing permission to charge that customer later. If you bill today through ACH debits or cards on file, this is the biggest change to absorb.
RTP and FedNow are also separate networks. A request reaches your customer only if your bank and theirs sit on the same network. Some banks have joined both, while others have joined only one. Our breakdown of FedNow vs. RTP limits and reach explains how that affects which rail fits your invoices.
RfP vs. Payment Links and Invoices
From your side, an RfP and a payment link look alike: you send something, the customer pays. Your customer experiences them differently. A payment link is a URL that opens a checkout page where the customer picks card or ACH. A request for payment shows up inside the customer's own banking app and is paid only by instant bank transfer.
| Request for Payment | Payment Link | Emailed Invoice (Card or ACH) | |
|---|---|---|---|
| Where the payer sees it | Their own banking app | Text or email that opens a web checkout | Email or mail |
| How they pay | Approve an instant bank transfer | Card, ACH or other methods you enable | Card, ACH, check, wire |
| When funds arrive | Seconds after approval | Card: when your processor funds the batch; ACH: several business days | Depends on the method chosen |
| Can the payer reverse it? | No | Card chargebacks and ACH returns apply | Card chargebacks and ACH returns apply |
| What the payer needs | A bank that receives RfPs | A card or bank account | A card, bank account or checkbook |
These options complement each other. Buyers who pay suppliers by card for float or rewards give that up with an RfP, and some will decline the request for that reason. A well-built invoice offers RfP to customers whose banks support it and keeps a card and ACH link for everyone else. If you don't take bank payments yet, start with ACH payment processing, because ACH reaches nearly every U.S. checking account.
Irrevocability: No Chargebacks, No Pull Debits
A completed RTP or FedNow payment is final. No card-network chargeback process applies, and no ACH return window opens. A customer can't call their card issuer three weeks after a job and claim the work was never done. If you have lost disputes over finished work or forfeited deposits, finality is the main reason to look at RfP.
Finality does not cancel your refund obligations. When your terms or the law require a refund, you send it as a new payment. Both networks also carry a message that lets the payer's bank ask you to return funds, mostly for errors or fraud. Your agreements and the law govern how you answer it, and nothing reverses automatically.
Disputes don't disappear, either. Without a chargeback system, a disagreement over the quality of the work becomes a contract matter between you and the customer. Clear written scopes and signed approvals matter more, not less.
The trade-off is collection. With no pull debit, you can't keep a customer on file and charge them each month. Every recurring bill needs a fresh approval, so RfP suits one-time invoices, deposits and milestone billing better than subscriptions.
Plan for impostors, too. Instant, final payments attract fraudsters, and a fake request dressed up as yours costs your customer money and damages your name. Tell customers in advance exactly what your requests look like: the business name they'll see, your invoice number format, and the fact that you will never text them a different account to pay.
Bank Support for RTP and FedNow Request for Payment Today
Joining a network and supporting RfP are separate decisions for a bank. Many institutions that receive instant payments do not yet display requests to their customers. Others receive requests but don't let business clients send them.
For a FedNow request for payment or an RTP request for pay to reach anyone, three things have to line up. Your bank, or your provider's sponsor bank, must be able to originate requests. Your customer's bank must receive them and show them in its app. And both banks must be on the same network. If any one of those fails, the request goes nowhere, and you fall back to card or ACH for that customer.
Your bank or provider sets the price, and pricing structures differ from bank to bank. Ask about a fee per request sent, a fee per payment received, and any monthly platform charge. Each network sets a per-transaction ceiling, and individual banks set their own lower limits, which matters on large B2B invoices. Get current limits and fees in writing. Our comparison of RTP vs. FedNow vs. ACH covers the broader trade-offs between the rails.
Use Cases: Instant Invoice Payment, Deposits and Service Calls
B2B and wholesale invoices. Real-time payments billing fits best here, because commercial customers bank with institutions that offer treasury tools more often than consumers do. To decide whether it pays off, run the comparison on your own largest invoices. Take what you pay to accept a card on one of them, then compare it with your bank's combined fee to send a request and receive the payment.
Card fees are a percentage, so they grow with the invoice. If your bank prices RfP per item instead, the gap widens with every dollar billed. The saving is real only for customers who would otherwise pay by card. Our look at what a large invoice costs by card versus ACH shows the card side of that math. Your accounts receivable aging report tells you which slow-paying customers to offer RfP first.
Professional services. Accountants, consultants and agencies attach a request to each milestone invoice. Because the reference data arrives with the payment, reconciliation beats matching a check to a client folder. See our page on payment options for professional services firms for the card setups that sit alongside it.
Contractors and deposits. A remodeler ordering custom cabinets wants the deposit cleared before placing the order. A request sent at contract signing and approved in the customer's app settles that day and stays settled. Our construction and contracting payments page covers the card side of the same jobs.
Moving companies. Movers face two pressure points: the booking deposit and the balance on delivery day. A crew lead sends the balance request when the last box comes off the truck and sees it paid before the crew pulls away, instead of accepting a check that bounces a week later. Follow the state and federal rules that apply to moving deposits and estimates. MannyPay's moving company payment processing page covers mobile card acceptance for customers whose banks don't support RfP.
Service calls. A plumber finishing an emergency repair sends the request from a phone, and the homeowner approves it in the driveway. Consumer bank support is less predictable than business bank support, so carry a backup: a virtual terminal for keyed card payments or a mobile card terminal in the truck.
How to Start Sending Requests
- Call your business bank. Ask which networks it is on, whether it originates requests for payment for business clients, and what it charges per request and per payment.
- Map your payers' banks. List the banks your top customers use and ask your provider which of them receive requests. If only a handful do, run a small pilot before changing every invoice.
- Connect it to your books. Confirm the request carries your invoice number and that incoming payments sync to your accounting software, or you'll be matching deposits by hand.
- Write the customer notice. Describe what your request looks like, who it comes from, and how to report a suspicious one.
- Keep card and ACH on every invoice. RfP is an added option, and customers whose banks don't support it still need a way to pay.
Make the bank call this week. Its answers decide whether RfP is available to you now or later. In the meantime, you can set up online card acceptance through MannyPay so every invoice carries a card option today, and the merchant platform MannyPay is building is designed to include text-to-pay and payment links. Request a free quote, and a MannyPay specialist will respond within one business day.
This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.


