Exchange model utilizing data elements

1 . A method for facilitating real-time payments between a biller and a consumer comprising:

receiving, by a first processing circuit, from a biller computing system of the biller, a data set comprising a consumer digital payment system (DPS) token generated by the biller computing system and associated with a consumer of a second processing circuit that is billed by the biller;

formatting, by the first processing circuit, a request for payment (RFP) message by:

decrypting a token identifier generated by the DPS and associated with the consumer;

generating a new data structure corresponding to the consumer DPS token of the second processing circuit based on encrypting data comprising the token identifier and additional RFP information based on a cryptographic function; and

transforming the RFP request from a first data structure readable by the biller to a second data structure readable by a clearinghouse that facilitates payment between the consumer and the biller, wherein the RFP request comprises product-specific data corresponding to a type of the RFP request, and wherein the product-specific data comprises one or more of: a portion of a balance to pay or a type of payment to be made;

generating a user interface on a provider application on a user device of the consumer, wherein the user interface displays a plurality of options for paying a bill from the biller based on the type of the RFP request, and wherein the plurality of options comprises one or more of: paying a minimum balance, paying a principal amount, paying an escrow amount, paying a full balance, paying a partial balance, or paying a past due amount, and wherein the user interface comprises a field in which the consumer can specify a specific payment amount;

transmitting, by the first processing circuit to the second processing circuit via a real-time payment (RTP) network, the RFP message, wherein transmission of the RFP message is facilitated by a generic data element and an additional data element associated with the RTP network, and wherein transmission of the RFP message improves messaging times between the consumer and the biller computing system by facilitating bidirectional messaging between the consumer and the biller computing system;

receiving, by the first processing circuit from the RTP network, a status message indicating the second processing circuit has detokenized the DPS token and accepted the RFP message;

transmitting, by the first processing circuit to the biller computing system, the RFP message was accepted; and

initiating a payment from a financial account of the consumer to a financial account of the biller.

2 . The method of claim 1 , further comprising:

receiving, by the first processing circuit from the RTP network, a credit transfer message associated with a RTP associated with a second consumer of a third processing circuit;

transmitting, by the first processing circuit, an acceptance status message to the RTP network; and

transmitting, by the first processing circuit, a notification that an account balance of the biller was updated.

3 . The method of claim 2 , further comprising:

receiving, by the first processing circuit from the biller computing system in response to the account balance being updated, a payment acknowledgement;

formatting, by the first processing circuit, an acknowledgement message;

transmitting, by the first processing circuit to the third processing circuit via the RTP network, the acknowledgement message;

receiving, by the first processing circuit from the RTP network, a second status message indicating the third processing circuit accepted the acknowledgement message; and

transmitting, by the first processing circuit to the biller computing system, the acknowledgement message was accepted.

4 . The method of claim 3 , wherein at least one of the RFP message is a code78 International Organization for Standardization (ISO) message, the status message is a code23 ISO message, the acceptance status message is a code7 ISO message, or the acknowledgement message is a code15 ISO message.

5 . The method of claim 1 , wherein prior to receiving the data set comprising the consumer digital payment system (DPS) token the first processing circuit and the second processing circuit establish a RTP relationship via the RTP network.

6 . The method of claim 5 , wherein establishing the RTP relationship comprises exchanging a biller file from the first processing circuit to the second processing circuit and exchanging a consumer pilot from the first processing circuit to the second processing circuit.

7 . The method of claim 6 , wherein the biller file comprises a biller name, a biller address, and a biller identifier, and wherein the consumer pilot comprises a customer account identifier, a consumer account number, and the consumer DPS token.

8 . The method of claim 7 , wherein the consumer DPS token is registered with the first processing circuit and the second processing circuit.

9 . A provider system for facilitating real-time payments between a biller and a consumer comprising:

at least one processing circuit having at least one processor coupled to at least one memory, the at least one processing circuit configured to:

receive, from a biller computing system of the biller, a data set comprising a consumer digital payment system (DPS) token generated by the biller computing system and associated with a consumer of a second processing circuit that is billed by the biller;

format a request for payment (RFP) message by:

decrypting a token identifier generated by the DPS and associated with the consumer;

generating a new data structure corresponding to the consumer DPS token of the second processing circuit based on encrypting data comprising the token identifier and additional RFP information based on a cryptographic function; and

transforming the RFP request from a first data structure readable by the biller to a second data structure readable by a clearinghouse that facilitates payment between the consumer and the biller, wherein the RFP request comprises product-specific data corresponding to a type of the RFP request, and wherein the product-specific data comprises one or more of: a portion of a balance to pay or a type of payment to be made;

generate a user interface on a provider application on a user device of the consumer, wherein the user interface displays a plurality of options for paying a bill from the biller based on the type of the RFP request, and wherein the plurality of options comprises one or more of: paying a minimum balance, paying a principal amount, paying an escrow amount, paying a full balance, paying a partial balance, or paying a past due amount, and wherein the user interface comprises a field in which the consumer can specify a specific payment amount;

transmit, to the second processing circuit via a real-time payment (RTP) network, the RFP message, wherein transmission of the RFP message is facilitated by a generic data element and an additional data element associated with the RTP network, and wherein transmission of the RFP message improves messaging times between the consumer and the biller computing system by facilitating bidirectional messaging between the consumer and the biller computing system;

receive, from the RTP network, a status message indicating the second processing circuit has detokenized the DPS token and accepted the RFP message;

transmit, to the biller computing system, the RFP message was accepted; and

initiate a payment from a financial account of the consumer to a financial account of the biller.

10 . The system of claim 9 , wherein the at least one processing circuit is further configured to:

receive, from the RTP network, a credit transfer message associated with a RTP associated with a second consumer of a third processing circuit;

transmit an acceptance status message to the RTP network; and

transmit a notification that an account balance of the biller was updated.

11 . The system of claim 10 , wherein the at least one processing circuit is further configured to:

receive, from the biller computing system in response to the account balance being updated, a payment acknowledgement;

format an acknowledgement message;

transmit, to the third processing circuit via the RTP network, the acknowledgement message;

receive, from the RTP network, a second status message indicating the third processing circuit accepted the acknowledgement message; and

transmit, to the biller computing system, the acknowledgement message was accepted.

12 . The system of claim 11 , wherein at least one of the RFP message is a code78 International Organization for Standardization (ISO) message, the status message is a code23 ISO message, the acceptance status message is a code7 ISO message, or the acknowledgement message is a code15 ISO message.

13 . The system of claim 9 , wherein prior to receiving the data set comprising the consumer digital payment system (DPS) token the system and the second processing circuit establish a RTP relationship via the RTP network.

14 . The system of claim 13 , wherein establishing the RTP relationship comprises exchanging a biller file from the system to the second processing circuit and exchanging a consumer pilot from the system to the second processing circuit.

15 . The system of claim 14 , wherein the biller file comprises a biller name, a biller address, and a biller identifier, and wherein the consumer pilot comprises a customer account identifier, a consumer account number, and the consumer DPS token.

16 . The system of claim 15 , wherein the consumer DPS token is registered with the system and the second processing circuit.

17 . One or more non-transitory computer-readable storage media having instructions for facilitating real-time payments between a biller and a consumer stored thereon that, when executed by at least one processing circuit, cause the at least one processing circuit to:

receive, from a biller computing system of the biller, a data set comprising a consumer digital payment system (DPS) token generated by the biller computing system and associated with a consumer of a second processing circuit that is billed by the biller;

format a request for payment (RFP) message by:

decrypting a token identifier generated by the DPS and associated with the consumer;

generating a new data structure corresponding to the consumer DPS token of the second processing circuit based on encrypting data comprising the token identifier and additional RFP information based on a cryptographic function; and

transforming the RFP request from a first data structure readable by the biller to a second data structure readable by a clearinghouse that facilitates payment between the consumer and the biller, wherein the RFP request comprises product-specific data corresponding to a type of the RFP request, and wherein the product-specific data comprises one or more of: a portion of a balance to pay or a type of payment to be made;

generate a user interface on a provider application on a user device of the consumer, wherein the user interface displays a plurality of options for paying a bill from the biller based on the type of the RFP request, and wherein the plurality of options comprises one or more of: paying a minimum balance, paying a principal amount, paying an escrow amount, paying a full balance, paying a partial balance, or paying a past due amount, and wherein the user interface comprises a field in which the consumer can specify a specific payment amount;

transmit, to the second processing circuit via a real-time payment (RTP) network, the RFP message, wherein transmission of the RFP message is facilitated by a generic data element and an additional data element associated with the RTP network, and wherein transmission of the RFP message improves messaging times between the consumer and the biller computing system by facilitating bidirectional messaging between the consumer and the biller computing system;

receive, from the RTP network, a status message indicating the second processing circuit has detokenized the DPS token and accepted the RFP message;

transmit, to the biller computing system, the RFP message was accepted; and

initiate a payment from a financial account of the consumer to a financial account of the biller.

18 . The one or more non-transitory computer-readable storage media of claim 17 , having additional instructions stored thereon that, when executed by the at least one processing circuit, cause the at least one processing circuit to:

receive, from the RTP network, a credit transfer message associated with a RTP associated with a second consumer of a third processing circuit;

transmit an acceptance status message to the RTP network; and

transmit a notification that an account balance of the biller was updated.

19 . The one or more non-transitory computer-readable storage media of claim 18 , having additional instructions stored thereon that, when executed by the at least one processing circuit, cause the at least one processing circuit to:

receive, from the biller computing system in response to the account balance being updated, a payment acknowledgement;

format an acknowledgement message;

transmit, to the third processing circuit via the RTP network, the acknowledgement message;

receive, from the RTP network, a second status message indicating the third processing circuit accepted the acknowledgement message; and

transmit, to the biller computing system, the acknowledgement message was accepted.

20 . The one or more non-transitory computer-readable storage media of claim 19 , wherein the RFP message is a code78 International Organization for Standardization (ISO) message, the status message is a code23 ISO message, the acceptance status message is a code7 ISO message, and the acknowledgement message is a code15 ISO message.