FedNow Request for Payment Message Specification
TodayPayments.com delivers real-time RfP messaging tools for businesses ready to accelerate their cash flow. By integrating ISO 20022-rich data, we enable merchants to send invoice-level FedNow® and RTP® payment requests through Excel, XML, or JSON—supported by alias-based routing, multi-bank enrollment, and same-day reconciliation across all 50 states.
What is the FedNow® RfP Message Specification?
FedNow® RfP Message Specification Using ISO
20022 for Real-Time Funding Certainty
The Future of Instant Invoicing Starts
with FedNow® RfP Messaging
In the real-time payments revolution,
Request for Payment (RfP) is the heartbeat of instant invoicing.
Backed by FedNow®, this system lets businesses issue secure,
richly detailed payment requests—triggering immediate responses from
payers and eliminating slow processing.
Powered by ISO 20022 messaging, RfP formats can be deployed through Excel uploads, XML-based systems, or JSON API calls—with delivery via mobile, text, email, or secure digital portals. At TodayPayments.com, we help your organization implement these specs with full compliance, speed, and simplicity.
The FedNow® RfP message is a structured payment request transmitted in real time to a payer using secure ISO 20022 standards. This format allows businesses to issue invoice-level data with actionable payment links—triggering faster settlement and providing funding certainty.
The message specification supports:
- Excel: For batch RfP uploads and bulk requests
- XML: For legacy financial systems and ERP integrations
- JSON: For real-time API integrations through apps or web portals
Every RfP message includes a 140-character summary, a clickable hyperlink to a hosted payment page, and alias-based routing via mobile number or email—no banking credentials needed.
Key Benefits of FedNow® RfP Message Implementation via TodayPayments.com
Why ISO 20022 Matters for Rich Data RfP Messaging
ISO 20022 is the global standard for financial messaging, enabling businesses to transmit structured data between payer and payee. It enables FedNow® to include:
- Invoice details
- Payer references
- Settlement instructions
- Due dates and payment terms
- Integration with ERP and accounting platforms
ISO 20022 is also compatible with Request-for-Payment messages delivered across channels like mobile text, email, POS terminals, or custom checkout links.
This ensures secure, error-free, and fully traceable transactions, even when interacting with multiple banks, aliases, or divisions.
Key Benefits of FedNow® RfP Message Implementation via TodayPayments.com
1. Fast, Secure RfP Deployment
Launch FedNow® and RTP® Request for Payment messaging using Excel,
XML, or JSON files—with no IT team required.
2. Hosted Payment Pages
Insert
hyperlinks in messages directing customers to a secure checkout
experience with pre-filled invoice data.
3. Alias Routing for Privacy & Simplicity
Use mobile numbers or email addresses as identifiers—eliminating
the need for sensitive account info.
4. Multi-Format Compatibility
Send
RfPs through:
- .xlsx batch uploads
- .xml legacy banking formats
- .json REST API integrations
5. Real-Time Invoicing, Real-Time Funding
Payers settle instantly, and your funds are received in
seconds—not days.
6. Multi-Bank, Multi-Alias, Multi-State
Support
Serve all 50 U.S. states and over 100 aliases, all
with unique MIDs—seamlessly managed through one dashboard.
7.
QuickBooks® Integration
Auto-sync payment data with your accounting system for
reconciliation and audit-ready tracking.
8. High-Risk Merchant Friendly
We
accept industries most banks won’t—including merchants with poor
credit or complex structures.
The FedNow Request for Payment (RFP) message specification format is based on the ISO 20022 standard. It supports the exchange of structured financial data for payment requests between parties. Below is an example of a basic FedNow Request for Payment (RFP) message format with corresponding ISO 20022 fields and their lengths.
FedNow Request for Payment (RFP) ISO 20022 Message Specification
| Field Name | ISO 20022 Field | Description | Field Length |
|---|---|---|---|
| Message ID | MsgId |
Unique identifier for the message | Max 35 characters |
| Creation Date Time | CreDtTm |
Date and time when the message is created | ISO DateTime Format |
| Request for Payment Type | RFPType (custom field) |
Type of request (invoice, due bill, etc.) | Max 4 characters |
| Initiating Party | InitgPty |
Information about the party initiating the RFP | Max 70 characters |
| Debtor | Dbtr |
Information about the debtor (payer) | Max 70 characters |
| Debtor Account | DbtrAcct |
Account information of the debtor | Max 34 characters |
| Creditor | Cdtr |
Information about the creditor (payee) | Max 70 characters |
| Creditor Account | CdtrAcct |
Account information of the creditor | Max 34 characters |
| Payment Amount | IntrBkSttlmAmt |
Requested payment amount | Numeric, 18 digits |
| Currency | Ccy |
ISO currency code (e.g., USD, EUR) | 3 characters |
| Requested Execution Date | ReqdExctnDt |
Date on which payment should be executed | ISO Date Format |
| Payment Reference | PmtInfId |
Payment reference provided by the creditor | Max 35 characters |
| Purpose Code | Purp |
Purpose of the payment (business, services, etc.) | Max 4 characters |
| Remittance Information | RmtInf |
Information related to the remittance | Max 140 characters |
| Instruction for Creditor | InstrForCdtrAgt |
Instructions for the creditor agent | Max 210 characters |
| Debtor Agent | DbtrAgt |
Financial institution of the debtor | Max 70 characters |
| Creditor Agent | CdtrAgt |
Financial institution of the creditor | Max 70 characters |
Explanation of Key Fields
- Message ID (MsgId): Unique identifier for tracking and identifying the Request for Payment (RFP).
- Creation Date Time (CreDtTm): ISO 8601 format, capturing the exact time the message was created.
- Initiating Party (InitgPty): Information about the entity initiating the request for payment.
- Debtor and Creditor Information: These fields include details about the payer (debtor) and the recipient (creditor), including names, account information, and financial institutions.
- Payment Amount and Currency (IntrBkSttlmAmt, Ccy): Specifies the amount to be paid and the currency in ISO 4217 code.
- Remittance Information (RmtInf): Optional field for providing details that relate to the purpose of the payment.
This table outlines a basic FedNow Request for Payment message format. Further customization and additional fields may be required based on the specific use case. Let me know if you need further adjustments or additions!
Send Real-Time RfPs. Get Paid with Certainty.
Whether you're a CFO, startup founder, or a merchant turned down by traditional banks, TodayPayments.com lets you modernize your invoicing—and get paid instantly.
✅ Instantly enroll in FedNow®
and RTP®
✅ Send secure RfP messages using
Excel, XML, or JSON
✅ No bank
visits, no paperwork delays
✅ Alias-based IDs via
email or mobile number
✅ Hosted payment page links
embedded in every message
✅ Live reconciliation
and real-time treasury dashboards
✅ All payment
rails: FedNow®, RTP®, ACH, and credit
card supported
✅ High-risk and multi-state
merchants approved
Certainty is priceless. And with TodayPayments.com, it's instant.
👉 Visit https://www.TodayPayments.com now and start sending RfP messages that convert faster, reconcile easier, and put your business ahead.
Creation Request for Payment Bank File
Call us, the .csv and or .xml Request for Payment (RfP) file you need while on your 1st phone call! We guarantee our reports work to your Bank and Credit Union. We were years ahead of competitors recognizing the benefits of RequestForPayment.com. We are not a Bank. Our function as a role as an "Accounting System" with Real-Time Payments to work with Billers / Payees to create the Request for Payment to upload the Biller's Bank online platform. U.S. Companies need help to learn the RfP message delivering their bank. Today Payments' ISO 20022 Payment Initiation (PAIN .013) shows how to implement Create Real-Time Payments Request for Payment File up front delivering a message from the Creditor (Payee) to it's bank. Most banks (FIs) will deliver the message Import and Batch files for their company depositors for both FedNow and Real-Time Payments (RtP). Once uploaded correctly, the Creditor's (Payee's) bank continues through a "Payment Hub", with messaging to the Debtor's (Payer's) bank.
... easily create Real-Time Payments RfP files. No risk. Test with your bank and delete "test" files before APPROVAL on your Bank's Online Payments Platform.
Today Payments is a leader in the evolution of immediate payments. We were years ahead of competitors recognizing the benefits of Same-Day ACH
and Real-Time Payments funding. Our business clients receive faster
availability of funds on deposited items and instant notification of
items presented for deposit all based on real-time activity.
Dedicated to providing superior customer service and
industry-leading technology.
1) Free ISO 20022 Request for Payment File Formats, for FedNow and Real-Time Payments (The Clearing House) .pdf for you manually create "Mandatory" (Mandatory data for completed file) fields, start at page 4, with "yellow" highlighting. $0.0 + No Support
2) We create .csv or .xml formatting using your Bank or Credit Union. Create Multiple Templates. Payer / Customer Routing Transit and Deposit Account Number may be required or Nickname, Alias to import with your bank. You can upload or "key data" into our software for File Creation of "Mandatory" general file.
Fees = $57 monthly, including Support Fees and Batch Fee, Monthly Fee, User Fee, Additional Payment Method on "Hosted Payment Page" (Request for file with an HTML link per transaction to "Hosted Payment Page" with ancillary payment methods of FedNow, RTP, ACH, Cards and many more!) + $.03 per Transaction + 1% percentage on gross dollar file,
3) We add a URI for each separate Payer transaction. Using URI, per transaction, will identify and reconcile your Accounts Receivable.
Fees Above 2) plus $29 monthly additional QuickBooks Online "QBO" formatting, and "Hosted Payment Page" and WYSIWYG
4) Above 3) plus Create "Total" (over 600 Mandatory, Conditional & Optional fields of all ISO 20022 Pain .013) Price on quote.
Each day, thousands of businesses around the country are turning their transactions into profit with real-time payment solutions like ours.
Start using our Bank Reconciliation and Aging of Request for Payments:
Dynamic integrated with FedNow & Real-Time Payments (RtP) Bank Reconciliation: Accrual / Cash / QBO - Undeposited Funds
Contact Us for Request For Payment payment processing
