Biller's login - Hosted Payments Page
Real-Time Payments Gateway


Instant Request for Payment: Real-Time Alias-Based Invoicing for Instant Settlement

TodayPayments.com empowers businesses with cutting-edge instant Request for Payment tools that simplify billing, reduce operational delays, and ensure secure, alias-based real-time settlement across all payment channels.

TodayPayments.com positions Instant Request for Payment (RfP) as a modern invoicing and payment trigger solution, helping organizations replace outdated billing systems with real-time, alias-enabled payment requests that instantly settle through FedNow® and RTP® rails. We bring together secure invoicing, ISO 20022 data, and instant good funds for merchants, enterprises, and platforms.

 

Streamline Invoicing with Instant Payment Requests

Instant Recurring Payment Manual invoicing and delayed collections are liabilities in a digital-first economy. With Instant Request for Payment (RfP), businesses can send secure, real-time payment requests using aliases like mobile numbers, email addresses, or customer IDs—no banking details required.

This forward-looking payment tool lets customers pay in real time, triggering immediate settlement and rich transaction data. Paired with alias-based routing and ISO 20022 messaging, RfP turns invoicing into a frictionless, automated experience that fuels faster cash flow and better financial control.

Instant Recurring Payment and recurring Real-Time instant payments, are defined simply as: Irrevocably collected funds in a Payee bank account and usable immediately by the owner of the account. An upfront on-time 'standing approval' using Instant Recurring Payment is an instruction or set of instructions a Payer uses to pre-authorize their financial institution to pay future Request for Payments, RfPs without requiring the Payer to review and approve each RfP.

Trigger Faster Payments with Alias-Based Instant RfP

Ask Us How:

Instant Request for Payment allows businesses to send aliases for real-time, secure payment requests with instant settlement, streamlining invoicing and accelerating cash flow collection. Customers can receive digital invoice prompts via text or email and pay instantly through a secure payment gateway linked to RTP® or FedNow®.

These RfP messages are formatted with ISO 20022 fields, including payer ID, invoice number, and purpose codes—enabling seamless reconciliation and full audit trails. Businesses can upload RfP messages in Excel, XML, or JSON format for one-time or recurring invoices, whether processing payroll, subscription renewals, or customer collections.

With alias-routing, there's no need for bank account details at the time of the request. TodayPayments.com supports alias-based delivery methods like mobile number, token, or email—making it easier and safer for businesses to get paid instantly, 24/7/365.

Key Parameters of Instant Request for Payment

  • ✅ Payment Type: Credit-push (payer-authorized)
  • ✅ Request Channel: Alias-based (email, phone, tokenized ID)
  • ✅ Network Compatibility: RTP®, FedNow®
  • ✅ Message Standard: ISO 20022
  • ✅ Settlement Speed: Instant (under 10 seconds)
  • ✅ Availability: 24/7/365
  • ✅ Invoicing Medium: Text, Email, API
  • ✅ Batch Upload Ready: Excel, XML, JSON

Core Attributes

  • Alias Support – Send payment requests without needing bank account details
  • Mobile-Optimized – Trigger RfP via text or app push
  • Recurring or One-Time – Supports automated or manual invoices
  • Embedded Messaging – Include invoice notes, due dates, payer ID
  • Bulk Request Capability – Process batch invoice RfPs in real time
  • Security First – Encrypted and tokenized payment channels

Business Benefits

  • Accelerated cash flow through instant settlements
  • Reduced payment friction with alias-based delivery
  • No chargebacks or reversals due to credit-push model
  • Improved billing accuracy with ISO 20022 structured fields
  • Lower operational overhead by automating invoicing
  • Better user experience through mobile-responsive payments

Platform Features

  • ✅ Alias-to-Alias compatibility for secure invoice delivery
  • ✅ ISO 20022 message enrichment for reconciliation
  • ✅ Real-time status updates for every invoice/payment
  • ✅ ERP & accounting integration via API
  • ✅ RfP support across RTP®, FedNow®, and ACH fallback
  • ✅ Batch-ready for enterprise scale

You're specifically interested in the process of instant recurring payments, where the invoicing or request for payment (RfP) might not be real-time, but the funding from the payer to the payee happens instantly at the scheduled time. Here's how you can implement this process:

1.     Set Up Recurring Payment Agreement: The payer and payee establish an agreement for recurring payments. This agreement outlines the payment amount, frequency (e.g., weekly, monthly), duration, and any other terms and conditions.

2.     Initial Invoicing or Request for Payment (RfP): At the start of the recurring payment schedule, the payee sends an invoice or a request for payment (RfP) to the payer. This invoice/RfP may not be instant and could follow a traditional invoicing process with a predetermined billing cycle.

3.     Authorization: The payer authorizes the payee to initiate recurring payments. This authorization can be provided through various means, such as signing a direct debit agreement or setting up automated payments through online banking.

4.     Scheduled Payment Processing: Once the authorization is in place and the initial invoicing/RfP has been sent, the payer's financial institution schedules automatic payments according to the agreed-upon frequency.

5.     Instant Funding: On the scheduled payment date, the payer's financial institution debits the payer's account instantly and transfers the funds to the payee's account in real-time. This ensures that the payee receives the payment on-time, even if the initial invoicing/RfP was not real-time.

6.     Confirmation and Notification: Both the payer and payee receive confirmation and notification of each payment transaction. This ensures transparency and allows for tracking and reconciliation of payments.

7.     Reconciliation: The payer and payee reconcile their accounts periodically to ensure that all payments have been processed correctly. Any discrepancies or issues can be addressed promptly through reconciliation processes.

8.     Error Handling: A robust error handling mechanism is in place to address any payment failures or discrepancies. This may involve retrying failed payments, investigating the root cause of errors, and resolving issues to prevent recurrence.

By implementing instant recurring payments with these steps, you can automate the payment process, ensure timely payments, and improve cash flow management for both the payer and payee.

Real-time payments begin with real-time invoicing. TodayPayments.com’s Instant Request for Payment feature helps you bill faster, reduce reconciliation errors, and get paid instantly—no bank account required.

✅ Alias-based invoicing via text/email
✅ ISO 20022 message fields for clarity and compliance
✅ Instant payment settlement via FedNow® or RTP®
✅ Batch upload support for high-volume collections
✅ Full mobile compatibility and ERP/API integration

Visit https://www.TodayPayments.com now and turn Request for Payment into Real-Time Revenue.

 

Creation Recurring Request for Payment

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-TimePayments.com to work with Billers to create the Request for Payment to upload the Biller's Bank online platform. 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", either FedNow or RTP, will be the RtP Hub will be The Clearing House, with messaging to the Debtor's (Payer's) bank. Request for Recurring Payment

ACH and both Instant and Real-Time Payments Request for Payment ISO 20022 XML Message Versions
The versions that NACHA recommends for the Request for Payment message and the Response to the Request are pain.013 and pain.014 respectively. Version 5 for the RfP messages, which The Clearing House Real-Time Payments system has implemented, may also be utilized as there is no material difference in the schemas. Predictability, that the U.S. Federal Reserve, via the FedNow ® Instant Payments, will also use Request for Payment. The ACH, RTP ® and FedNow ® versions are Credit Push Payments.


Payees ensure the finality of Instant Real-Time Payments (IRTP) and FedNow using recurring Requests for Payments (RfP), Payees can implement certain measures:

1.     Confirmation Mechanism: Implement a confirmation mechanism to ensure that each payment request is acknowledged and confirmed by the payer before the payment is initiated. This can include requiring the payer to provide explicit consent or authorization for each recurring payment.

2.     Transaction Monitoring: Continuously monitor the status of recurring payment requests and transactions in real-time to detect any anomalies or discrepancies. Promptly investigate and resolve any issues that arise to ensure the integrity and finality of payments.

3.     Authentication and Authorization: Implement strong authentication and authorization measures to verify the identity of the payer and ensure that only authorized payments are processed. This can include multi-factor authentication, biometric verification, or secure tokenization techniques.

4.     Payment Reconciliation: Regularly reconcile payment transactions to ensure that all authorized payments have been successfully processed and finalized. This involves comparing transaction records with payment requests to identify any discrepancies or unauthorized transactions.

5.     Secure Communication Channels: Utilize secure communication channels, such as encrypted messaging protocols or secure APIs, to transmit payment requests and transaction data between the payee and the payer. This helps prevent unauthorized access or interception of sensitive payment information.

6.     Compliance with Regulatory Standards: Ensure compliance with relevant regulatory standards and guidelines governing instant payments and recurring payment transactions. This includes adhering to data security requirements, fraud prevention measures, and consumer protection regulations.

By implementing these measures, Payees can enhance the finality and security of Instant Real-Time Payments using recurring Requests for Payments, thereby minimizing the risk of payment disputes, fraud, or unauthorized transactions.

 
Each day, thousands of businesses around the country are turning their transactions into profit with real-time payment solutions like ours.

Contact Us for Request For Payment payment processing