Request for Payment (RfP) via the RTP network [(RTP)] you to be able to receive funds by requesting funds from a sender, who can then initiate a payment for you.

This request therefore results in a ‘pull’ from the payer’s account, and provides a fast and convenient way to move money, with the payer having full control over the transaction.

Unlike a traditional payment where the payer initiates the transaction, with RTP RFP, the payee (the person owed money) sends a request for payment to the payer to complete the payment.

Clients can enable RfP as part of a request to receive-only model, or alongside other RTP capabilities.

📘

Instant vs Not.

While the request to the payer's bank account is instant or real-time via the RTP network, the rest of the flow i.e. instructions to the payer by the payer's bank or the payer's approval to the request or the subsequent push payment instruction from the payer's bank to the payee are not.

However, once the final push payment rails ride on the RTP network, the money movement at that point is instant.

Use Cases

The current list of permitted use cases for RfP by RTP includes:

• Consumer Bill Pay: Companies that provide recurring consumer services, such as utilities, can use RfP to request payment for their services;
• Business to Business Payments:
  • Businesses can pay suppliers, business partners, contractors, freelancers or other third parties using RfP;
  • Payroll providers can send RfPs to its corporate customers so they can fund payroll on the same day that employees are paid, rather than 2-4 days prior to payday;
• Account to Account (A2A): RfPs can be used by individuals to request transfers between bank or brokerage accounts that are owned by the same person. For example, brokers can send an RfP to customers so they can transfer money from their bank account to their brokerage account instantly to enable immediate trading;

How RfP Works

1. User initiates a request for payment through TabaPay Client’s application by providing the details of the payer
2. TabaPay Client reaches out to TabaPay to request for a payment (“Pull” request to the Payer while providing Payer’s bank account details) via Create Transaction API.
3. TabaPay sends the request to The Clearing House TCH.
4. TCH will forward instructions to the Payer's bank, to notify the payer and response to the instructions back to TCH.
5. TCH sends the RfP response back to TabaPay.
6. TabaPay returns the response back to TabaPay Client. Check this page for the possible RTP Return Codes

📘

TabaPay Response to RfP Request

The real-time response by TabaPay to the TabaPay Client will provide a response code listed on this page.

The two possibilities comes down to a Yes or No to the request for payment instruction (again, just the request at this time, and nothing further).

• A "yes, the receiving bank consumed the RFP without error and yes, the debtor account is enabled for RFP" OR
• A "no, the receiving bank did not consume the RFP without error, and /or the debtor account is not enabled for RFP"

7. TabaPay Client displays the RfP status to the user.

Note: The TabaPay Client Sponsor Bank must ensure that the creditor DDA in the RfPis RTPenabled.

Not shown in diagram and not in scope:

If the transaction is successful (i.e. payer receives the request and approves the request), then:

• The payer receives the request and approves/declines
• If approved, the payer bank originates a payment to the payee's account at TabaPay Client
• The payer’s bank is debited, and the TabaPay Client’s sponsor bank receives funds.

TabaPay Client’s Sponsor Bank Obligations

To participate in RfP, the Client’s Sponsor Bank must ensure that the “Creditor” DDA in the Request For Payment message, is an open, RTP-enabled account. This means that the Client can receive funds instantly when the payer accepts the request for funds via RFP.

Request for Payment (RfP) Transaction Flow

TabaPay enables you to check if the Routing Number of a bank is enabled for RTP. Once you confirm eligibility, proceed to process the RTP RFP transaction using TabaPay's Unified API.

1. Query Bank API

TabaPay Client to use the Query Bank API and provide the payer bank’s Routing Number to check for TCH eligibility.

2. Create Transaction API

RTP RfP will use the Create Transaction API. The fields achOptions: R and type: pull will designate the transaction to be RTP RfP.

Note: pulloptions.expirationDate is required on all RTP RfP (pull) Transactions.

3. Response Codes for RfP by RTP

Please refer to [RTP Return Codes](Transaction forbidden on this account) for the possible values that will be returned by TabaPay upon sending the request for payment instruction.

4. Recipe

If you’re interested in integrating with RTP Request for Payment, please use this recipe:

Sample Customer Flows

The following are examples of customer workflows on a platform that uses RfP.

1. Sample Illustration of Request for Payment (RFP)

2. Sample Illustration of Response to Request for Payment (RFP)

📘

Up to the Payer's Bank!

Remember, the user experience for a Request for Payment is completely up to the payer’s bank.