Real-Time Payments Request for Payment Files

Supported File Formats: ISO 20022, Excel, XML, and JSON

We support a wide array of secure, modern formats for RfP message uploads:

• ISO 20022 Rich Messaging – Standardized for clarity, compliance, and data-rich invoicing
• .XLS / .XLSX – Spreadsheet formats for batch RfP uploads
• .XML / JSON – Machine-readable formats ideal for API and software integrations

Whether it’s B2B or C2B, your payment request can originate from mobile, be processed instantly, and complete with funding certainty.

Upload RfP files once or on a recurring schedule to automate your receivables like never before.

Batch Uploads to All Credit Unions & Financial Institutions—Instantly

TodayPayments.com makes it easy to submit batches of Request for Payment (RfP) files to any U.S. credit union or financial institution that supports FedNow® or RTP®. You can import RfP messages for single transactions or large batches, ensuring:

• Fast approval
• Real-time credit to recipient accounts
• Guaranteed confirmation of funds

Supported payment flows include:

• B2B – Business-to-Business transactions
• C2B – Consumer-to-Business invoices
• Recurring subscription billing
• On-demand one-time payments

Creating Real-Time Payments (RTP) Request for Payment (RfP) files for use with all financial institutions typically involves following standardized formats and methods to ensure interoperability across banks. The standard for these files is generally based on the ISO 20022 messaging format, which enables consistent data exchange for payment instructions. The specific requirements for generating these files can vary slightly depending on the financial institution's system, but the core attributes remain similar.

Key Attributes for Creating RTP Request for Payment (RfP) Files:

1. ISO 20022 Standard:

• Most financial institutions that support Real-Time Payments use the ISO 20022 format, particularly the PAIN.013 message format for RfPs.
• The file is structured in XML format, making it machine-readable and standardized for electronic data interchange.

2. Mandatory Fields in the File:

• Message Identification (MsgID): A unique identifier for each payment request.
• Creditor (Payee) Information: Name, address, and bank account details (IBAN, BIC, or routing number).
• Debtor (Payer) Information: The payer’s name, account details, and bank identifier.
• Transaction Amount: Specifies the payment amount along with the currency (e.g., USD, EUR).
• Payment Date: The date by which the payment is expected (due date).
• Remittance Information: A detailed explanation of the payment, including invoice number, reference details, or customer number.

3. File Types and Structure:

• .XML: This is the most common file format for RTP systems and is required by most financial institutions for real-time payment requests.
• .CSV: Some banks or financial institutions may also accept CSV files, particularly for batch processing, although they generally prefer XML for structured data exchange.

4. Interoperability Across Financial Institutions:

• Most financial institutions, including those participating in systems like FedNow and The Clearing House RTP, require files to be formatted according to ISO 20022 specifications. This allows interoperability between different payment systems and financial institutions globally.
• The PAIN.013 file format ensures that banks, credit unions, and payment hubs can process the files without issue, regardless of their internal system.

5. Authentication and Security:

• Digital Signatures: Files must often include digital signatures to ensure authenticity and to verify that the data has not been tampered with.
• Encryption: To protect sensitive financial information, files must be encrypted, particularly when transmitted between systems. Common encryption methods include SFTP and HTTPS.

6. File Validation:

• Files must pass validation checks for compliance with ISO 20022 schema rules. Each bank may also have additional validations for specific fields such as customer identifiers, invoice numbers, or unique message IDs.

Steps for Creating RTP Request for Payment Files:

1. Data Collection: Collect the required data, such as payer and payee details, transaction amounts, due dates, and remittance information.
2. File Generation: Use an RTP-compliant platform, like SecureQBPlugin (for QuickBooks users), or a bank's provided API to generate the RfP file in ISO 20022 XML format.
3. File Transmission: Send the file through a secure channel, such as SFTP, to the bank for processing. The bank’s RTP system will then deliver the RfP to the payer’s institution.
4. Payment Confirmation: Once the payer approves the request, the payment is processed in real-time, and both payer and payee receive confirmation messages.

Tools for RfP File Creation:

• SecureQBPlugin for QuickBooks: This tool helps QuickBooks users generate RTP Request for Payment files, making the process simple and ensuring compliance with ISO 20022 standards

Real-Time Request Payment

Real-Time Wire

• Bank APIs: Many financial institutions provide APIs for creating and transmitting RTP files, often with detailed specifications on the required XML structure.

By adhering to the ISO 20022 format and ensuring secure transmission methods, you can generate RfP files that are compatible with any financial institution's RTP system.

Tap Into Real-Time Invoicing with TodayPayments.com

Say goodbye to waiting for checks to clear, delayed ACH, or untracked wire transfers.

With TodayPayments.com, you gain the power to invoice instantly, securely, and from the palm of your hand—whether you're using a smartphone, API, or batch upload.

Send an invoice. Get paid. In real time.

From ISO 20022 support to mobile-ready delivery, our platform is built for fintechs, credit unions, and high-risk merchants who need speed and certainty.

👉 Join the real-time payment revolution.
Visit TodayPayments.com and start sending smarter invoices now.