Import Real-Time Payments


How to Import Real-Time Payments Request for Payment File

Real-Time instant payments, are defined simply as: Irrevocably collected funds in a bank account and usable immediately by the owner of the account. Our "Good Funds" payment gateway allows for instant real-time digital payments that are immediate, irrevocable, intra-bank and/or interbank account-to-account (A2A) transfers that utilize a real-time messaging system connected to every transaction participant through all U.S.-based financial institutions.

To import a Real-Time Payments (RTP) Request for Payment (RFP) file into your Bank or Credit Union’s dashboard, you need to follow certain steps based on the file format (ISO 20022 XML, CSV, JSON, or XML) and your institution’s dashboard capabilities. The process involves securely uploading the file into the institution’s system, validating the data, and monitoring the status of the request. Here is a general guide to help you import an RTP Request for Payment file into your bank or credit union’s dashboard.

Step-by-Step Guide to Importing RTP Request for Payment File into Your Financial Institution's Dashboard

1. Obtain the Request for Payment (RFP) File

Ensure you have the correct Request for Payment (RFP) file ready for import. This file may be in different formats, including:

  • ISO 20022 XML: The most common format for real-time payment systems like FedNow.
  • CSV: A more simplified text file format.
  • JSON: Often used in modern web-based APIs and systems.
  • XML (Non-ISO 20022): A custom XML format that may be used by your system.

The file should include the necessary details such as:

  • Debtor (Payer) Information
  • Creditor (Payee) Information
  • Amount
  • Payment Date
  • Payment Reference (e.g., an invoice or payment request ID)

2. Log Into Your Financial Institution’s Dashboard

  • Open the bank or credit union’s online banking dashboard or business portal.
  • Ensure you have the necessary permissions (e.g., admin or finance-level access) to import payment files.

3. Navigate to the Payment Section or File Upload Section

  • Look for sections such as Real-Time Payments, Request for Payments, or FedNow in the dashboard.
  • In some institutions, this option may be listed under File Uploads, Payments, or Transfers.

4. Upload the Request for Payment (RFP) File

Depending on the format of the RFP file you have, follow these instructions:

For ISO 20022 XML Format:

  1. Select ISO 20022 XML as the file type from the upload options in your bank’s dashboard.
  2. Upload the XML file from your local storage.
  3. The system will validate the XML schema (in this case, pain.013.001.07 for Request for Payments) and extract the relevant fields, such as payer, payee, amount, and payment reference.
  4. Ensure that the XML follows the correct structure for the institution's real-time payment request system.

Example: ISO 20022 XML Request for Payment (pain.013.001.07)

xml

<?xml version="1.0" encoding="UTF-8"?>

<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.013.001.07">

  <FIToFIPmtReq>

    <GrpHdr>

      <MsgId>RFP-123456789</MsgId>

      <CreDtTm>2024-09-13T10:30:00</CreDtTm>

      <NbOfTxs>1</NbOfTxs>

    </GrpHdr>

    <PmtReq>

      <ReqdColltnDt>2024-09-14</ReqdColltnDt>

      <PmtTpInf>

        <SvcLvl>

          <Cd>URGP</Cd>

        </SvcLvl>

      </PmtTpInf>

      <Dbtr>

        <Nm>Jane Smith</Nm>

        <PstlAdr>

          <Ctry>US</Ctry>

        </PstlAdr>

      </Dbtr>

      <DbtrAcct>

        <Id>

          <IBAN>US987654321098765432</IBAN>

        </Id>

      </DbtrAcct>

      <Cdtr>

        <Nm>Acme Corporation</Nm>

        <PstlAdr>

          <Ctry>US</Ctry>

        </PstlAdr>

      </Cdtr>

      <CdtrAcct>

        <Id>

          <IBAN>US123456789012345678</IBAN>

        </Id>

      </CdtrAcct>

      <Amt>

        <InstdAmt Ccy="USD">1500.00</InstdAmt>

      </Amt>

      <RmtInf>

        <Ustrd>Invoice Payment Request for Invoice-98765</Ustrd>

      </RmtInf>

    </PmtReq>

  </FIToFIPmtReq>

</Document>

For CSV Format:

  1. If your bank supports CSV uploads, select CSV as the file format.
  2. Upload the CSV file, ensuring it has the required fields, such as:
    • Transaction ID
    • Payee Information
    • Payer Information
    • Amount
    • Payment Date
    • Reference

Example: CSV File Format for Request for Payment

csv

RequestID,CreditorName,CreditorAccountNumber,DebtorName,DebtorAccountNumber,Amount,Currency,DueDate,Reference

RFP-12345,Acme Corporation,123456789,Jane Smith,987654321,1500.00,USD,2024-09-14,Invoice Payment Request for Invoice-98765

  1. Some systems may require field mapping where you align your CSV columns to the system’s required fields (e.g., "Amount" in your CSV maps to the "Amount" field in the system).

For JSON Format:

  1. Select JSON as the file format, if supported.
  2. Upload the JSON file, which should include all payment details in a structured format.

Example: JSON File Format for Request for Payment

json

{

  "RequestForPayment": {

    "RequestID": "RFP-12345",

    "Amount": {

      "currency": "USD",

      "value": "1500.00"

    },

    "Creditor": {

      "Name": "Acme Corporation",

      "AccountNumber": "123456789"

    },

    "Debtor": {

      "Name": "Jane Smith",

      "AccountNumber": "987654321"

    },

    "DueDate": "2024-09-14",

    "Reference": "Invoice Payment Request for Invoice-98765"

  }

}

For Custom XML (Non-ISO 20022):

  1. Select XML as the file format if the bank accepts non-ISO 20022 XML files.
  2. Ensure the XML structure is aligned with the required schema by your institution.
  3. Upload the XML file and proceed to map the fields as necessary.

5. Validate and Review the File

  • After uploading, most systems will validate the file to check for errors.
  • Ensure the following fields are validated:
    • Payer Information (e.g., account number, name)
    • Payee Information
    • Amount (should match the expected payment)
    • Payment Reference (ensure it links to the correct invoice or payment request)

If there are errors in validation (e.g., missing fields, incorrect format), correct them and re-upload the file.

6. Confirm and Submit the Request

Once the validation is complete:

  • Review the payment request details to ensure all data is correct (e.g., amount, payer, and payee info).
  • Submit the request to the bank’s system for processing.

Most banks allow you to track the status of your Request for Payment after submission, so check the status page in the dashboard.

7. Monitor the Payment Status

  • Once submitted, you can monitor the status of the payment request through the bank’s portal.
  • The status may be updated to:
    • Pending: Waiting for approval or authorization from the payer.
    • Completed: The payment has been successfully processed.
    • Failed: There was an error processing the request, and it needs to be addressed.

8. Reconcile and Track Payment

After the payer completes the request, ensure the payment is reconciled within your accounting or ERP system. The bank’s system may also provide detailed reports that you can download for record-keeping.

Common Scenarios for RFP Uploads

B2B (Business-to-Business) Example:

  • Scenario: A company submits a request for payment to a business client using the ISO 20022 XML format.
  • Process: The file is uploaded, validated, and submitted through the bank’s dashboard. The payment request is linked to an invoice, and the client approves the payment through their bank.

B2C (Business-to-Consumer) Example:

  • Scenario: A service provider submits a payment request to a customer for a subscription fee.
  • Process: The CSV file is uploaded through the financial institution’s dashboard. The customer receives the payment request, reviews it, and authorizes the payment.

Key Considerations:

  1. File Format Compatibility: Make sure your bank or credit union supports the file format you're using (ISO 20022 XML, CSV, JSON, etc.).
  2. Field Mapping: For CSV and custom XML files, ensure the fields are correctly mapped to the bank’s system.
  3. Validation: Review the data after uploading to avoid errors.
  4. Security: Ensure the payment request is securely uploaded using SSL encryption or other secure methods offered by the bank.

Conclusion

Uploading and processing a Real-Time Payments Request for Payment (RFP) file into your bank or credit union’s dashboard involves ensuring the file format matches their system requirements, uploading the file through the payment section, and validating the information before submission. Whether using ISO 20022 XML, CSV, JSON, or custom XML, following the steps outlined will help ensure smooth processing of payment requests.

Let us at TodayPayments.com know if you need further details or help with a specific platform!

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" in Open Banking with Real-Time Payments to work with Billers 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", will be the RtP Hub will be The Clearing House, with messaging to the Debtor's (Payer's) bank. Request for Payment

... 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.

Pricing with our Request For Payment Professionals

hand shake

 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 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) Payer Routing Transit and Deposit Account Number is NOT required to import with your bank. We add your URI for each separate Payer transaction.

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.



Activation Dynamic RfP Aging and Bank Reconciliation worksheets - only $49 annually

1. Worksheet Automatically Aging for Requests for Payments and Explanations

- Worksheet to determine "Reasons and Rejects Coding" readying for re-sent Payers.
- Use our solution yourself. Stop paying accountant's over $50 an hour. So EASY to USE.
- No "Color Cells to Match Transactions" (You're currently doing this. You won't coloring with our solution).
- One-Sheet for Aging Request for Payments (Merge, Match and Clear over 100,000 transactions in less than 5 minutes!)
- Batch deposits displaying Bank Statements are not used anymore. Real-time Payments are displayed "by transaction".
- Make sure your Bank displaying "Daily FedNow and Real-time Payments" reporting for "Funds Sent and Received". (These banks have Great Reporting.)

2. Bank Reconciliation with as Payee FedNow & Real-Time Payments for Accrual, Cash and Hybrid Basis and QBO - Undeposited Funds


Contact Us for Request For Payment payment processing