Import Real-Time Payments File

To import a Real-Time Payments (RTP) Request for Payment (RFP) file using https://Real-TimePayments.com into your Bank or Credit Union’s dashboard, you will need to follow the steps outlined by your financial institution’s platform. Most institutions that support Real-Time Payments will allow you to upload payment request files in formats such as ISO 20022 XML, CSV, or JSON via their online portal. Below is a general guide to importing a Request for Payment (RFP) using Real-Time Payments.com into your financial institution.

Step-by-Step Guide to Importing RTP Request for Payment File into Your Bank or Credit Union

1. Obtain the Request for Payment (RFP) File

Make sure you have the Request for Payment (RFP) file ready. It can be in various formats:

• ISO 20022 XML (standard for financial messages)
• CSV (comma-separated value files used for data exchange)
• JSON (JavaScript Object Notation, typically used in API integrations)
• XML (a custom XML file structure used in payment systems)

Your RFP file should include:

• Debtor (Payer) Information
• Creditor (Payee) Information
• Amount
• Currency
• Payment Date
• Payment Reference (such as an invoice number)

2. Log Into Your Financial Institution’s Dashboard

• Navigate to your bank or credit union’s online portal.
• Log in with the necessary credentials (you may need admin-level access to upload files).

3. Navigate to the Payment or File Upload Section

• Look for the Payments section, Request for Payment options, or File Upload area.
• Depending on your institution, you may find sections labeled Real-Time Payments, FedNow, or similar.

4. Upload the Request for Payment (RFP) File

The process varies depending on the format of the RFP file you’re using:

For ISO 20022 XML Format:

1. Select ISO 20022 XML as the file type in the bank’s dashboard.
2. Upload the ISO 20022 XML file from your local storage.
3. The bank system will validate the XML schema and fields, ensuring that it complies with the required structure (pain.013.001 for Request for Payment).
4. The XML will contain the following key fields:
   • Payer Information (debtor)
   • Payee Information (creditor)
   • Payment Amount
   • Payment Reference

Example: ISO 20022 XML Request for Payment File

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-987654321</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. Select CSV as the file type in the dashboard.
2. Upload the CSV file from your local computer.
3. Make sure the CSV contains the necessary fields:
   • Transaction ID
   • Debtor Information (payer)
   • Creditor Information (payee)
   • Amount
   • Payment Date
   • Payment Reference (invoice number)

Example: CSV File 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

4. Field Mapping: If necessary, map the CSV columns to the relevant fields in the bank’s system (e.g., map "Amount" to the bank’s Amount field).

For JSON Format:

1. Select JSON as the file type if your bank supports JSON.
2. Upload the JSON file that includes the relevant payment request data.

Example: JSON File 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) Format:

1. Select XML as the file format if your bank uses a custom XML format.
2. Upload the XML file and map the fields as necessary to ensure the system recognizes the payer, payee, amount, and payment date.

5. Validate and Review the Upload

After uploading, your bank’s system will likely validate the file for:

• Payer Information (correct account details, names)
• Payee Information
• Amount (ensure it matches the expected payment)
• Payment Reference (match it to the correct invoice or request ID)

If the validation detects errors, correct the issues (e.g., missing fields or invalid data) and re-upload the file.

6. Confirm and Submit the Request

Once the file passes validation:

• Review the Request for Payment details such as amount, payee, and payment reference.
• Submit the file to the bank’s system for processing.

7. Monitor Payment Status

After submission, track the status of the payment request:

• Pending: The payment request is awaiting action by the payer.
• Completed: The payment has been successfully processed by the payer.
• Failed: There was an issue processing the request (e.g., insufficient funds or invalid data).

Most financial institutions will provide a Transaction History or Payment Status section where you can monitor the progress.

8. Reconcile Payment (Optional for Businesses)

Once the payment is processed:

• Reconcile the payment in your accounting or ERP system by matching it with the corresponding invoice or transaction.
• If needed, download the payment confirmation or transaction report from the bank’s dashboard for your records.

Common Use Cases for RTP RFP Uploads

B2B (Business-to-Business) Example:

• Scenario: A supplier sends a Request for Payment to a client for goods delivered. The client processes the payment via their financial institution.
• File: The supplier uploads an ISO 20022 XML file to their bank’s dashboard, initiating a payment request linked to an invoice.

B2C (Business-to-Consumer) Example:

• Scenario: A service provider sends a payment request to a customer for a subscription service.
• File: The service provider uploads a CSV file through their credit union’s dashboard, and the customer receives the payment request for review and authorization.

Key Considerations:

1. File Format Compatibility: Ensure the format (ISO 20022 XML, CSV, JSON, XML) is supported by your bank or credit union’s system.
2. Field Mapping: Properly map file fields (e.g., payer, payee, amount) to your bank’s required fields.
3. Validation: Review the file post-upload to avoid errors in processing.
4. Monitoring: Keep track of the payment request’s status until the payment is completed.

Conclusion

Importing a Real-Time Payments Request for Payment (RFP) file via https://Real-TimePayments.com into your Bank or Credit Union’s dashboard involves uploading the appropriate file format, validating the data, and tracking the status. The steps outlined above provide a comprehensive guide to ensure the smooth processing of payment requests in both B2B and B2C contexts.

Would you like assistance with a specific bank platform, or need help preparing the file for upload? Let us know!