FedNow Message Specification
TodayPayments.com is the all-in-one fintech platform built to support businesses with real-time payment processing via FedNow®, RTP®, ACH, and credit cards. Using modern file formats like ISO 20022, XML, Excel, and JSON, we enable merchants—high-risk or mainstream—to automate, reconcile, and scale their payment operations instantly and securely across the U.S.
What is the FedNow® Message Specification Format?
FedNow® Message Specification Using ISO
20022, Excel, XML & JSON
The Future of Real-Time Payments Requires
Standardization
In today’s fast-paced financial environment,
businesses need a secure and standardized way to transmit payment
data across multiple banks and platforms. The FedNow® Service,
operated by the Federal Reserve, offers real-time, 24/7/365
payments—but it depends on precise message specifications to
ensure interoperability. Whether you're working with ISO 20022
XML, Excel uploads, or JSON APIs, your payment
infrastructure must be built to handle modern messaging standards.
That’s where TodayPayments.com comes in—enabling seamless compatibility with FedNow®, RTP®, ACH, and credit cards across multiple formats and institutions.
FedNow® message specifications define how financial transactions are encoded, validated, transmitted, and confirmed. These formats allow for real-time processing between financial institutions and merchants, using globally recognized data structures. The primary FedNow® message format is ISO 20022, an XML-based financial messaging standard supported worldwide.
FedNow® also supports:
- Excel (.xlsx): Used for batch uploads, invoicing, and manual processing
- XML: For legacy integration and ISO 20022-compliant systems
- JSON: Lightweight format for API integration and cloud-based applications
These formats enable transactions such as:
- Credit Transfers
- Request for Payments (RfP)
- Alias-based transfers (via phone number or email)
- Recurring and batch payments
With TodayPayments.com, businesses can upload any of these formats and automate payment delivery across the FedNow® and RTP® rails.
TodayPayments.com Makes FedNow® Messaging Easy
Why ISO 20022 and JSON Are Key for FedNow®
ISO 20022 is the official data messaging structure of FedNow®, offering:
- Unified structure for all payment types
- Rich metadata to reduce reconciliation errors
- Better fraud detection through standardized fields
- Compatibility with RTP®, ACH, and international SWIFT messaging
JSON is gaining popularity for:
- Lightweight REST API calls
- Real-time notifications and confirmations
- Web and mobile payment applications
- Seamless integration with cloud accounting and ERP platforms
Together, these formats enable high-speed, low-friction, and audit-friendly real-time payment workflows.
Whether you’re using .XLSX files from QuickBooks®, .XML files for system-to-system communication, or JSON via your development team—TodayPayments.com provides everything you need to:
- Process real-time transactions with zero delay
- Use alias-based MIDs (mobile/email instead of bank info)
- Upload 100+ aliases under one consolidated dashboard
- Integrate into QuickBooks® Online (QBO) for real-time reconciliation
- Customize and embed Hosted Payment Pages inside ISO 20022-compatible RfPs
- Track all payments with real-time reporting for your CFO, bookkeeper, or accountant
- Run recurring billing and batch uploads with one click
The FedNow Service provides real-time payment processing, and one of the core messages used in the service is the "Request for Payment" (RfP). Below is a generic outline for a Request for Payment (RfP) Message Specification. This format is inspired by ISO 20022 messaging standards, which are commonly used in the payment industry.
FedNow Request for Payment Message Specification
1. Message Header
- Message Identifier: Unique
identifier for the RfP message.
- Example: MsgId
- Data Type: String (Max length: 35)
- Example Value: RFP-123456789
- Creation Date and Time: The date
and time when the message is created.
- Example: CreDtTm
- Data Type: DateTime (ISO 8601 format)
- Example Value: 2023-12-05T10:15:30Z
- Message Type: Type of message
being sent, i.e., Request for Payment.
- Example: MsgTp
- Data Type: String (Fixed value: RFP)
- Example Value: RFP
2. Initiating Party Information
- Initiating Party Name: Name of
the individual or entity initiating the payment request.
- Example: InitgPtyNm
- Data Type: String (Max length: 140)
- Example Value: ABC Corp
- Initiating Party Identifier:
Unique identifier for the initiating party (e.g., a business
identification number).
- Example: InitgPtyId
- Data Type: String (Max length: 35)
- Example Value: 123456789
- Initiating Party Contact Information:
Optional field for providing contact details.
- Example: InitgPtyCtct
- Data Type: String (Max length: 100)
- Example Value: contact@abccorp.com
3. Creditor Information
- Creditor Name: Name of the
creditor (i.e., the party to whom payment is owed).
- Example: CdtrNm
- Data Type: String (Max length: 140)
- Example Value: XYZ Services Inc.
- Creditor Identifier: Unique
identifier for the creditor (e.g., an account number).
- Example: CdtrId
- Data Type: String (Max length: 35)
- Example Value: 987654321
- Creditor Financial Institution
Identifier: Identifier of the creditor's bank or financial
institution.
- Example: CdtrFinInstnId
- Data Type: String (Max length: 35)
- Example Value: BANK98765
4. Debtor Information
- Debtor Name: Name of the debtor
(i.e., the party from whom the payment is requested).
- Example: DbtrNm
- Data Type: String (Max length: 140)
- Example Value: John Doe
- Debtor Identifier: Unique
identifier for the debtor (e.g., an account number).
- Example: DbtrId
- Data Type: String (Max length: 35)
- Example Value: 654321987
- Debtor Financial Institution
Identifier: Identifier of the debtor's bank or financial
institution.
- Example: DbtrFinInstnId
- Data Type: String (Max length: 35)
- Example Value: BANK12345
5. Payment Details
- Payment Amount: The amount
requested in the payment.
- Example: PmtAmt
- Data Type: Decimal (Precision: 18,2)
- Example Value: 150.00
- Currency: Currency in which the
payment is requested.
- Example: Ccy
- Data Type: String (ISO 4217 Currency Code)
- Example Value: USD
- Payment Due Date: Date by which
the payment is requested to be made.
- Example: DueDt
- Data Type: Date (ISO 8601 format)
- Example Value: 2023-12-20
6. Invoice/Reference Information
- Invoice Number: Reference number
for the payment request (if applicable).
- Example: InvNb
- Data Type: String (Max length: 35)
- Example Value: INV-456789
- Reference Note: Optional field
for any additional reference or memo.
- Example: RfrdDoc
- Data Type: String (Max length: 140)
- Example Value: Payment for services rendered in November.
7. Additional Information (Optional)
- Remittance Information: Details
about the purpose of the payment.
- Example: RmtInf
- Data Type: String (Max length: 140)
- Example Value: Invoice #456 for Consulting Services.
- Payment Terms: Any special
payment terms (e.g., early payment discounts).
- Example: PmtTrms
- Data Type: String (Max length: 140)
- Example Value: 2% discount if paid by 2023-12-15.
This template can be adapted or extended based on specific FedNow or institution requirements, ensuring that any necessary data elements for proper message handling and processing are included. Always refer to the latest FedNow specifications and ISO 20022 guidelines for real-time payments to ensure compliance.
Future-Proof Your Payment Strategy with TodayPayments.com
With FedNow® and RTP®, speed is non-negotiable. But structure matters just as much. If your files don’t comply with ISO 20022—or your API isn’t JSON-ready—you risk payment failure, fraud, or delays.
That’s why TodayPayments.com provides an end-to-end solution for message formatting, delivery, alias routing, reconciliation, and more.
✅ Upload Excel, XML, or JSON
files
✅ Auto-map fields to FedNow®
ISO 20022 specs
✅ Instantly transmit across FedNow®,
RTP®, ACH, and cards
✅ Reconcile and
report in real-time
✅ Get approved—even
if you’re high-risk
👉 Ready to move fast with structured real-time payments?
🚀 Visit www.TodayPayments.com and apply now—100% online. No bank visit. No technical stress. Just instant FedNow®-powered results.
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