Facilitation of real-time payment network transactions

1 . A computing system comprising:

a storage device configured to store a plurality of application programming interfaces (APIs) of a payments computer; and

a payments computer processor of the payments computer configured to:

receive, via a submit Request For Payment (RFP) API of the plurality of APIs from an acquirer server of a payment requestor, transaction data of an electronic payment transaction between the payment requestor and a payer utilizing a payer's device prior to the electronic payment transaction being authorized by a real-time payment network, wherein the real-time payment network does not need to have an RFP message function, and at least one of the payment requestor and the payer do not need to be registered to use the real-time payment network,

generate a unique transaction identifier comprising an alphanumeric string corresponding to the transaction data,

store, in a transaction database of the storage device, a mapping of the generated unique transaction identifier to the transaction data,

transmit the unique transaction identifier to the acquirer server to send to the payment requestor, thus establishing a communication path around the real-time payment computer,

receive, from a payer's bank computer via a retrieve RFP API of the plurality of APIs, a retrieval request prior to the electronic payment transaction being authorized by the real-time payment network, wherein the retrieval request comprises the unique transaction identifier,

retrieve, in response to the retrieval request by using the received unique transaction identifier, the transaction data stored in the transaction database;

transmit the stored transaction data to the payer's bank computer,

receive, from the payer's bank computer via a confirmation RFP API of the plurality of APIs, a confirmation message confirming that the electronic payment transaction has been authorized by the real-time payment network, and

transmit, to the acquirer server via a notification RFP API of the plurality of APIs, a confirmation of payment message.

2 . The computing system of claim 1 , wherein the retrieval request further comprises transaction data provided from the payer's bank computer, and wherein the processor is further configured to recognize the retrieval request based on a similarity between the transaction data stored in the mapping and the transaction data provided from the payer's bank computer.

3 . The computing system of claim 1 , wherein the processor is configured to retrieve a payment account number of the payer from within the transaction data based on the transaction identifier received from the payer's bank computer and transmit the payment account number of the payer to payer's bank computer.

4 . The computing system of claim 1 , wherein the processor is further configured to retrieve a payment account number of the payment requestor based on the merchant identifier included in the transaction data, and store the payment account number of the payment requestor within the transaction data stored in the mapping.

5 . The computing system of claim 4 , wherein the processor is configured to transmit the payment account number of the payment requestor retrieved based on the merchant identifier to the payer's bank computer in response to the retrieval request from the payer's bank computer.

6 . The computing system of claim 1 , wherein the processor is configured to receive the transaction data from a checkout page of a website hosted by the payment requestor during an online session between a computing device of the payment requestor and the payer's device.

7 . A method comprising:

receiving, by a payments computer via a submit Request For Payment (RFP) application programming interface (API) of a plurality of programming interfaces (APIs) from an acquirer server of a payment requestor, transaction data of an electronic payment transaction between the payment requestor and a payer utilizing a payer's device prior to the electronic payment transaction being authorized by a real-time payment network, wherein the real-time payment network does not need to have an RFP message function, and at least one of the payment requestor and the payer do not need to be registered to use the real-time payment network;

generating, by the payments computer, a unique transaction identifier comprising an alphanumeric string corresponding to the transaction data;

storing, by a payments computer in a transaction database of the storage device, a mapping of the generated unique transaction identifier to the transaction data;

transmitting, by the payments computer, the unique transaction identifier to the acquirer server to send to the payment requestor, thus establishing a communication path around the real-time payment computer;

receiving, by the payments computer from a payer's bank computer via a retrieve RFP API of the plurality of APIs, a retrieval request prior to the electronic payment transaction being authorized by the real-time payment network, wherein the retrieval request comprises the unique transaction identifier;

retrieving, by the payments computer in response to the retrieval request by using the received unique transaction identifier, the transaction data stored in the transaction database;

transmitting, by the payments computer, the transaction data to the payer's bank computer;

receiving, by the payments computer from the payer's bank computer via a confirmation RFP API of the plurality of APIs, a confirmation message confirming that the electronic payment transaction has been authorized by the real-time payment network; and

transmitting, by the payments computer to the acquirer server via a notification RFP API of the plurality of APIs, a confirmation of payment message.

8 . The method of claim 7 , wherein the retrieval request further comprises transaction data provided from the payer's bank computer, and the method further comprises recognizing, by the payments computer, the retrieval request based on a similarity between the transaction data stored in the mapping and the transaction data provided from the payer's bank computer.

9 . The method of claim 7 , wherein the transmitting of the transaction data comprises retrieving, by the payments computer, a payment account number of the payer from within the transaction data based on the transaction identifier received from the payer's bank computer and transmitting the payment account number of the payer to the payer's bank computer.

10 . The method of claim 7 , wherein the method further comprises retrieving a payment account number of the payment requestor based on a merchant identifier included in the transaction data, and storing the payment account number of the payment requestor within the transaction data stored in the mapping.

11 . The method of claim 10 , wherein the transmitting of the transaction data further comprises transmitting, by the payments computer, the payment account number of the payment requestor retrieved based on the merchant identifier to the payer's bank computer in response to the retrieval request from the payer's bank computer.

12 . The method of claim 7 , wherein the receiving comprises receiving the transaction data from a checkout page of a website hosted by the payment requestor during an online session between a computing device of the payment requestor and the payer's device.

13 . A non-transitory computer-readable medium comprising instructions which when executed by a processor cause a computer to perform a method comprising:

receiving, via a submit Request For Payment (RFP) application programming interface (API) of a plurality of stored application programming interfaces (APIs) from an acquirer server of a payment requestor, transaction data of an electronic payment transaction between the payment requestor and a payer utilizing a payer's device prior to the electronic payment transaction being authorized by a real-time payment network, wherein the real-time payment network does not need to have an RFP message function, and at least one of the payment requestor and the payer do not need to be registered to use the real-time payment network;

generating a unique transaction identifier comprising an alphanumeric string corresponding to the transaction data;

storing, in a transaction database, a mapping of the generated unique transaction identifier to the transaction data;

transmitting the unique transaction identifier to the acquirer server to send to the payment requestor;

transmitting the unique transaction identifier to the acquirer server to send to the payment requestor, thus establishing a communication path around the real-time payment computer;

receiving, from a payer's bank computer via a retrieve RFP API of the plurality of APIs, a retrieval request prior to the electronic payment transaction being authorized by the real-time payment network, wherein the retrieval request comprises the unique transaction identifier;

retrieving, in response to the retrieval request by using the received unique transaction identifier, the transaction data stored in the transaction database;

transmitting the transaction data to the payer's bank computer;

receiving, from the payer's bank computer via a confirmation RFP API of the plurality of APIs, a confirmation message confirming that the electronic payment transaction has been authorized by the real-time payment network; and

transmitting, by the payments computer to the acquirer server via a notification RFP API of the plurality of APIs, a confirmation of payment message.

14 . The non-transitory computer-readable medium of claim 13 , wherein the retrieval request further comprises transaction data provided from the payer's bank computer, and wherein the method further comprises recognizing the retrieval request based on a similarity between the transaction data stored in the mapping and the transaction data provided from the payer's bank computer.

15 . The non-transitory computer-readable medium of claim 13 , wherein the transmitting comprises retrieving a payment account number of the payer from within the transaction data based on the transaction identifier received from the payer's bank computer, and transmitting the payment account number of the payer to the payer's bank computer.

16 . The non-transitory computer-readable medium of claim 13 , wherein the method further comprises retrieving a payment account number of the payment requestor based on a merchant identifier included in the transaction data, and storing the payment account number of the payment requestor within the transaction data stored in the mapping.

17 . The non-transitory computer-readable medium of claim 16 , wherein the transmitting further comprises transmitting the payment account number of the payment requestor retrieved based on the merchant identifier to the payer's bank computer-in response to the retrieval request from the payer's bank computer.