Patent Publication Number: US-11037121-B2

Title: Secure real-time transactions

Description:
CROSS-REFERENCE TO RELATED APPLICATIONS 
     This application is a continuation-in-part of U.S. patent application Ser. No. 15/170,781, filed Jun. 1, 2016, which is a continuation of U.S. patent application Ser. No. 14/805,214, filed Jul. 21, 2015. This application also is a continuation-in-part of U.S. patent application Ser. No. 14/805,214, filed Jul. 21, 2015. U.S. patent application Ser. Nos. 15/170,781 and 14/805,214 are incorporated herein by reference in their entirety. 
    
    
     TECHNICAL FIELD 
     This disclosure relates generally to secure processing of transactions, and relates more particularly to providing security and real-time transfers for transaction networks. 
     BACKGROUND 
     In a typical payment card transaction, a consumer provides an account number to a merchant to process a payment from the consumer for a transaction, and the merchant processes the payment transaction through the merchant&#39;s bank and/or payment processor (“acquirer”), which requests payment from the consumer&#39;s financial institution (“issuer”) through a payment processing network (e.g., a credit card network). The request initiated by the merchant for payment from the consumer is a pull-based payment model. The pull-based payment model generally involves significant transaction fees paid to various entities, such as the acquirer, the issuer, and the payment processing network. Moreover, the merchant is generally liable for chargebacks when the consumer&#39;s card is used fraudulently. Further, the consumer account information can be subject to theft under this model, as the consumer is providing the consumer&#39;s account information to third parties (i.e., parties other than the consumer&#39;s financial institution). A request initiated by the consumer, instead of the merchant, to send payment from the consumer&#39;s account to the merchant&#39;s account is a push-based payment model. The push-based payment model is often used for recurrent bill-pay transactions, but is generally not used for in-store transactions with merchants. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
       To facilitate further description of the embodiments, the following drawings are provided in which: 
         FIG. 1  illustrates a block diagram of a system that can be employed for a secure real-time payment transaction network, according to an embodiment; 
         FIG. 2  illustrates a flow chart for a method, according to an embodiment; 
         FIG. 3  illustrates a flow chart for a method, according to another embodiment; 
         FIG. 4  illustrates a flow chart for a method, according to another embodiment; 
         FIG. 5  illustrates a flow chart for a method, according to another embodiment; 
         FIG. 6  illustrates a flow chart for a method, according to another embodiment; 
         FIG. 7  illustrates a computer that is suitable for implementing an embodiment of components of the system of  FIG. 1 ; 
         FIG. 8  illustrates a representative block diagram of an example of elements included in circuit boards inside a chassis of the computer of  FIG. 7 ; 
         FIG. 9  illustrates a flow chart for a method, according to another embodiment; 
         FIG. 10  illustrates a flow chart for a method, according to another embodiment; 
         FIG. 11  illustrates a flow chart for a method, according to another embodiment; 
         FIG. 12  illustrates a flow chart for a method, according to another embodiment; 
         FIG. 13  illustrates a flow chart for a method, according to another embodiment; 
         FIG. 14  illustrates a flow chart for a method, according to another embodiment; 
         FIG. 15  illustrates a flow chart for a method, according to another embodiment; 
         FIG. 16  illustrates a flow chart for a method, according to another embodiment; 
         FIG. 17  illustrates an exemplary user interface display to allow the consumer of  FIG. 1  to approve a transaction on the mobile device of  FIG. 1 ; 
         FIG. 18  illustrates an exemplary user interface display to allow the consumer of  FIG. 1  to choose to use another account for the payment transaction when the approved account has insufficient funds or limited funds; 
         FIG. 19  illustrates an exemplary user interface display to allow the consumer of  FIG. 1  to select another account for the payment transaction when the approved account has insufficient funds; 
         FIG. 20  illustrates an exemplary user interface display to allow the consumer of  FIG. 1  to select the amount to pay using the other account selected the user interface display of  FIG. 19 ; 
         FIG. 21  illustrates an exemplary user interface display to confirm that a payment request has been sent from the mobile device of  FIG. 1 ; and 
         FIG. 22  illustrates an exemplary user interface display to confirm that the payment transaction to the merchant of  FIG. 1  has successfully completed. 
     
    
    
     For simplicity and clarity of illustration, the drawing figures illustrate the general manner of construction, and descriptions and details of well-known features and techniques may be omitted to avoid unnecessarily obscuring the present disclosure. Additionally, elements in the drawing figures are not necessarily drawn to scale. For example, the dimensions of some of the elements in the figures may be exaggerated relative to other elements to help improve understanding of embodiments of the present disclosure. The same reference numerals in different figures denote the same elements. 
     The terms “first,” “second,” “third,” “fourth,” and the like in the description and in the claims, if any, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the terms so used are interchangeable under appropriate circumstances such that the embodiments described herein are, for example, capable of operation in sequences other than those illustrated or otherwise described herein. Furthermore, the terms “include,” and “have,” and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, device, or apparatus that comprises a list of elements is not necessarily limited to those elements, but may include other elements not expressly listed or inherent to such process, method, system, article, device, or apparatus. 
     The terms “left,” “right,” “front,” “back,” “top,” “bottom,” “over,” “under,” and the like in the description and in the claims, if any, are used for descriptive purposes and not necessarily for describing permanent relative positions. It is to be understood that the terms so used are interchangeable under appropriate circumstances such that the embodiments of the apparatus, methods, and/or articles of manufacture described herein are, for example, capable of operation in other orientations than those illustrated or otherwise described herein. 
     The terms “couple,” “coupled,” “couples,” “coupling,” and the like should be broadly understood and refer to connecting two or more elements mechanically and/or otherwise. Two or more electrical elements may be electrically coupled together, but not be mechanically or otherwise coupled together. Coupling may be for any length of time, e.g., permanent or semi-permanent or only for an instant. “Electrical coupling” and the like should be broadly understood and include electrical coupling of all types. The absence of the word “removably,” “removable,” and the like near the word “coupled,” and the like does not mean that the coupling, etc. in question is or is not removable. 
     As defined herein, two or more elements are “integral” if they are comprised of the same piece of material. As defined herein, two or more elements are “non-integral” if each is comprised of a different piece of material. 
     As defined herein, “approximately” can, in some embodiments, mean within plus or minus ten percent of the stated value. In other embodiments, “approximately” can mean within plus or minus five percent of the stated value. In further embodiments, “approximately” can mean within plus or minus three percent of the stated value. In yet other embodiments, “approximately” can mean within plus or minus one percent of the stated value. 
     As defined herein, “real-time” can, in some embodiments, be defined with respect to operations carried out as soon as practically possible upon occurrence of a triggering event. A triggering event can include receipt of data necessary to execute a task or to otherwise process information. Because of delays inherent in transmission and/or in computing speeds, the term “real time” encompasses operations that occur in “near” real time or somewhat delayed from a triggering event. In a number of embodiments, “real time” can mean real time less a time delay for processing (e.g., determining) and/or transmitting data. The particular time delay can vary depending on the type and/or amount of the data, the processing speeds of the hardware, the transmission capability of the communication hardware, the transmission distance, etc. However, in many embodiments, the time delay can be less than approximately one second, five seconds, ten seconds, thirty seconds, one minute, or five minutes. 
     DESCRIPTION OF EXAMPLES OF EMBODIMENTS 
     Various embodiments include a system including one or more processing modules and one or more non-transitory memory storage modules storing computing instructions configured to run on the one or more processing modules and perform certain acts. The acts can include receiving, at a first financial institution from a mobile device of a consumer, a first request to pay a merchant for a payment amount from a first account of the consumer maintained by the first financial institution. The first request can include first information including a merchant identifier, a transaction identifier, and the payment amount. The first information can be sent to the first financial institution from a mobile application running on a mobile device used by the consumer at a store of the merchant to pay for one or more items to be purchased from the merchant by the consumer for the payment amount. The merchant identifier can be associated with the merchant. The mobile application can be associated with the first account. The acts also can include determining, at the first financial institution, second information including an account identifier of a second account of the merchant maintained by a second financial institution, at least partially based on the merchant identifier and third information obtained from a first system. The first system can be in data communication with the first financial institution and the second financial institution. The first system can be maintained by an entity that is different from the first financial institution and the second financial institution. The acts additionally can include authorizing, at the first financial institution, a payment from the first account to the second account. The acts further can include sending, from the first financial institution to the first system, payment information regarding a payment to be made to the second account from the first account. The payment information can be routed through the first system to the second financial institution such that the second financial institution, upon receiving the payment information, notifies the merchant to satisfy an expectation of the merchant for payment from the consumer. The payment information can include the transaction identifier, the account identifier of the second account, and the payment amount. 
     A number of embodiments include a method being implemented via one or more processing modules and one or more non-transitory memory storage modules storing computing instructions configured to run on the one or more processing modules. The method can include receiving, at a first financial institution from a mobile device of a consumer, a first request to pay a merchant for a payment amount from a first account of the consumer maintained by the first financial institution. The first request can include first information including a merchant identifier, a transaction identifier, and the payment amount. The first information can be sent to the first financial institution from a mobile application running on a mobile device used by the consumer at a store of the merchant to pay for one or more items to be purchased from the merchant by the consumer for the payment amount. The merchant identifier can be associated with the merchant. The mobile application can be associated with the first account. The method also can include determining, at the first financial institution, second information including an account identifier of a second account of the merchant maintained by a second financial institution, at least partially based on the merchant identifier and third information obtained from a first system. The first system can be in data communication with the first financial institution and the second financial institution. The first system can be maintained by an entity that is different from the first financial institution and the second financial institution. The method additionally can include authorizing, at the first financial institution, a payment from the first account to the second account. The method further can include sending, from the first financial institution to the first system, payment information regarding a payment to be made to the second account from the first account. The payment information can be routed through the first system to the second financial institution such that the second financial institution, upon receiving the payment information, notifies the merchant to satisfy an expectation of the merchant for payment from the consumer. The payment information can include the transaction identifier, the account identifier of the second account, and the payment amount. 
     Additional embodiments include a system including one or more processing modules and one or more non-transitory memory storage modules storing computing instructions configured to run on the one or more processing modules and perform certain acts. The acts can include receiving, at a first system from a first entity, a request including a merchant identifier. The merchant identifier can be associated with a merchant. The first system can be in data communication with a first financial institution and a second financial institution. The first system can be maintained by an entity that is different from the first financial institution and the second financial institution. The first financial institution can maintain a first account of a consumer. The first system can be in data communication with a merchant account database. The acts also can include determining, at the first system, using the merchant account database, first information including an account identifier of a second account of the merchant maintained by a second financial institution. The account identifier can be associated with the merchant identifier in the merchant account database. The acts additionally can include sending the first information from the first system to the first financial institution. The acts further can include receiving, at the first system from the first financial institution, payment information regarding a payment to be made to the second account from the first account to pay the merchant for one or more items to be purchased from the merchant by the consumer for the payment amount. The consumer can use a mobile device at a store of the merchant to pay for the one or more items. The mobile device can run a mobile application associated with the first account. The payment information can include a transaction identifier, the account identifier of the second account, and the payment amount. The acts additionally can include sending, from the first system to the second financial institution, the payment information such that the second financial institution, upon receiving the payment information, notifies the merchant to satisfy an expectation of the merchant for payment from the consumer. 
     Further embodiments include a method being implemented via one or more processing modules and one or more non-transitory memory storage modules storing computing instructions configured to run on the one or more processing modules. The method can include receiving, at a first system from a first entity, a request including a merchant identifier. The merchant identifier can be associated with a merchant. The first system can be in data communication with a first financial institution and a second financial institution. The first system can be maintained by an entity that is different from the first financial institution and the second financial institution. The first financial institution can maintain a first account of a consumer. The first system can be in data communication with a merchant account database. The method also can include determining, at the first system, using the merchant account database, first information including an account identifier of a second account of the merchant maintained by a second financial institution. The account identifier can be associated with the merchant identifier in the merchant account database. The method additionally can include sending the first information from the first system to the first financial institution. The method further can include receiving, at the first system from the first financial institution, payment information regarding a payment to be made to the second account from the first account to pay the merchant for one or more items to be purchased from the merchant by the consumer for the payment amount. The consumer can use a mobile device at a store of the merchant to pay for the one or more items. The mobile device can run a mobile application associated with the first account. The payment information can include a transaction identifier, the account identifier of the second account, and the payment amount. The method additionally can include sending, from the first system to the second financial institution, the payment information such that the second financial institution, upon receiving the payment information, notifies the merchant to satisfy an expectation of the merchant for payment from the consumer. 
     Still further embodiments include one or more non-transitory memory storage units including computer instructions that, when executed by one or more processors, perform various acts. The acts can include receiving, at a first system from a first entity, a request including a merchant identifier. The merchant identifier can be associated with a merchant. The first system can be in data communication with a first financial institution and a second financial institution. The first system can be maintained by an entity that is different from the first financial institution and the second financial institution. The first financial institution can maintain a first account of a consumer. The first system can be in data communication with a merchant account database. The acts also can include determining, at the first system, using the merchant account database, first information including an account identifier of a second account of the merchant maintained by a second financial institution. The account identifier can be associated with the merchant identifier in the merchant account database. The acts additionally can include sending the first information from the first system to the first financial institution. The acts further can include receiving, at the first system from the first financial institution, payment information regarding a payment to be made to the second account from the first account to pay the merchant for one or more items to be purchased from the merchant by the consumer for the payment amount. The consumer can use a mobile device at a store of the merchant to pay for the one or more items. The mobile device can run a mobile application associated with the first account. The payment information can include a transaction identifier, the account identifier of the second account, and the payment amount. The acts additionally can include sending, from the first system to the second financial institution, the payment information such that the second financial institution, upon receiving the payment information, notifies the merchant to satisfy an expectation of the merchant for payment from the consumer. 
     Additional embodiments include a method being implemented via one or more processing modules and one or more non-transitory memory storage modules storing computing instructions configured to run on the one or more processing modules. The method can include performing, at a mobile device, a preliminary identity authentication of a consumer using the mobile device. The method also can include receiving at the mobile device first information from a point-of-sale terminal. The first information can include a merchant identifier, a transaction identifier, and a payment amount. The merchant identifier can uniquely correspond to the point-of-sale terminal at a store of a merchant. The mobile device can run a mobile application that is associated with a first account of the consumer using the mobile device. The first account of the consumer cam ne maintained by a first financial institution. The method further can include sending, from the mobile device to the first financial institution, a first request to pay the merchant for the payment amount from the first account for one or more items to be purchased from the merchant by the consumer. The first request can include the first information, such that the first financial institution, upon receiving the first request, determines second information including an account identifier of a second account of the merchant maintained by a second financial institution, at least partially based on the merchant identifier and third information obtained from a first system, and such that the first financial institution sends to the first system payment information regarding a payment to be made to the second account from the first account. The payment information can be routed through the first system to the second financial institution such that the second financial institution, upon receiving the payment information, can notifies the merchant to satisfy an expectation of the merchant for payment from the consumer. The first system can be in data communication with the first financial institution and the second financial institution. The first system can be maintained by an entity that is different from the first financial institution and the second financial institution. The payment information can include the transaction identifier, the account identifier of the second account, and the payment amount. The payment information further can include one of: (a) a settlement credit push of funds for the payment amount from the first account to the second account, or (b) an irrevocable promise to pay the payment amount from the first account to the second account. 
     The method additionally can include, after sending the first request to pay the merchant and before the payment information is sent to the first system from the first financial institution: receiving, at the mobile device from the first financial institution, an additional authentication request to perform an additional identity authentication of the consumer using the mobile device; performing, at the mobile device, the additional identity authentication of the consumer using the mobile device; and sending, from the mobile device to the first financial institution, a response to the additional authentication request. 
     Performing the additional identity authentication of the consumer can include performing the additional authentication of the consumer based at least in part on at least one of: determining biometrics of the consumer using the mobile device; or requesting the consumer to enter additional information in the mobile device. 
     The method further can include prior to sending the first request to pay the merchant: sending, from the mobile device to the first financial institution, a preliminary request for account information; and receiving, at the mobile device from the first financial institution. The account information can include an account balance and an account status of the first account. 
     Further embodiments include a method being implemented via one or more processing modules and one or more non-transitory memory storage modules storing computing instructions configured to run on the one or more processing modules. The method can include determining, at a point-of-sale terminal at a store of a merchant, a payment amount for one or more items to be purchased from the merchant by a consumer. The method also can include sending first information from the point-of-sale terminal to a mobile device used by the consumer. The first information can include a merchant identifier, a transaction identifier, and the payment amount. The merchant identifier can uniquely correspond to the point-of-sale terminal at the store of the merchant. The mobile device can run a mobile application that is associated with a first account of the consumer using the mobile device. The first account of the consumer can be maintained by a first financial institution. The mobile device, upon receiving the first information, can send a first request to pay the merchant for the payment amount from the first account. The first request can include the first information, such that the first financial institution, upon receiving the first request, determines second information including an account identifier of a second account of the merchant maintained by a second financial institution, at least partially based on the merchant identifier and third information obtained from a first system, and such that the first financial institution sends to the first system payment information regarding a payment to be made to the second account from the first account. The payment information can be routed through the first system to the second financial institution. The first system can be in data communication with the first financial institution and the second financial institution. The first system can be maintained by an entity that is different from the first financial institution and the second financial institution. The payment information can include the transaction identifier, the account identifier of the second account, and the payment amount. The payment information further can include one of: (a) a settlement credit push of funds for the payment amount from the first account to the second account, or (b) an irrevocable promise to pay the payment amount from the first account to the second account. The method further can include receiving, at the point-of-sale terminal from the second financial institution, a notification to satisfy an expectation of the merchant for payment from the consumer. 
     Sending the first information from the point-of-sale terminal to the mobile device can include sending the first information from the point-of-sale terminal to the mobile device using a proximity-based wireless data communication protocol. 
     The method additionally can include receiving, at the point-of-sale terminal from the mobile device, information about the consumer. 
     Still further embodiments include a method being implemented via one or more processing modules and one or more non-transitory memory storage modules storing computing instructions configured to run on the one or more processing modules. The method can include receiving, at a second financial institution from a first system, payment information regarding a payment to be made to a second account of a merchant maintained by the second financial institution from a first account of a consumer maintained by a first financial institution to pay the merchant for one or more items to be purchased from the merchant by the consumer for the payment amount. The payment information can be sent from the first financial institution to the first system and routed through the first system to the second financial institution. The first system can be in data communication with the first financial institution and the second financial institution. The first system can be maintained by an entity that is different from the first financial institution and the second financial institution. The consumer can use a mobile device at a store of the merchant to pay for the one or more items. The mobile device can run a mobile application associated with the first account. The payment information can include a transaction identifier, an account identifier of the second account, and the payment amount. The first financial institution can determine the account identifier of the second account based on a merchant identifier and based on third information obtained from the first system. The merchant identifier can uniquely correspond to a point-of-sale terminal at the store of a merchant. The mobile device can send a request to pay the merchant for the payment amount from the first account. The request can include first information including the merchant identifier, a transaction identifier, and the payment amount. The payment information further can include one of: (a) a settlement credit push of funds for the payment amount from the first account to the second account, or (b) an irrevocable promise to pay the payment amount from the first account to the second account. The acts also can include sending, from the second financial institution to the point-of-sale terminal, a notification to satisfy an expectation of the merchant for payment from the consumer. 
     The method also can include, before sending the notification, crediting the second account with the payment amount. 
     Sending the notification to satisfy the expectation of the merchant for payment from the consumer can include notifying the merchant that funds for the payment amount are immediately available in the second account. 
     Additional embodiments include a system including one or more processors and one or more non-transitory computer-readable media storing computing instructions configured to run on the one more processors and perform various acts. The acts can include determining, at a point-of-sale terminal at a store of a merchant, a payment amount for one or more items to be purchased from the merchant by a consumer in a transaction. The acts also can include generating a transaction code including a merchant public identifier, the payment amount, a transaction identifier for the transaction, and a digital signature. The acts additionally can include providing the transaction code to a mobile device being used by the consumer, such that the mobile device verifies the digital signature and sends a request to pay the merchant for the payment amount from a first account of the consumer maintained by a first financial institution, such that the first financial institution, upon receiving the request to pay, retrieves from a transaction system an account identifier of a second account of the merchant maintained by a second financial institution based on the merchant public identifier, and such that the first financial institution sends to the transaction system payment information regarding a payment to be made to the second account from the first account. The transaction system can be maintained by an entity that is different from the merchant, the first financial institution, and the second financial institution. The payment information can be routed through the transaction system to the second financial institution. The payment information can include the transaction identifier, the account identifier of the second account, and the payment amount. The acts further can include receiving, at the point-of-sale terminal, a notification of payment for the transaction in real-time while the consumer remains at the store of the merchant. 
     Further embodiments include a method being implemented via execution of computing instructions configured to run at one or more processors and stored at one or more non-transitory computer-readable media. The method can include determining, at a point-of-sale terminal at a store of a merchant, a payment amount for one or more items to be purchased from the merchant by a consumer in a transaction. The method also can include generating a transaction code including a merchant public identifier, the payment amount, a transaction identifier for the transaction, and a digital signature. The method additionally can include providing the transaction code to a mobile device being used by the consumer, such that the mobile device verifies the digital signature and sends a request to pay the merchant for the payment amount from a first account of the consumer maintained by a first financial institution, such that the first financial institution, upon receiving the request to pay, retrieves from a transaction system an account identifier of a second account of the merchant maintained by a second financial institution based on the merchant public identifier, and such that the first financial institution sends to the transaction system payment information regarding a payment to be made to the second account from the first account. The transaction system can be maintained by an entity that is different from the merchant, the first financial institution, and the second financial institution. The payment information can be routed through the transaction system to the second financial institution. The payment information can include the transaction identifier, the account identifier of the second account, and the payment amount. The method further can include receiving, at the point-of-sale terminal, a notification of payment for the transaction in real-time while the consumer remains at the store of the merchant. 
     Additional embodiments include a system including one or more processors and one or more non-transitory computer-readable media storing computing instructions configured to run on the one more processors and perform various acts. The acts can include receiving, at a mobile device being used by a consumer, a transaction code from a point-of-sale terminal at a store of a merchant. The transaction code can include a merchant public identifier being associated with the merchant, a payment amount for one or more items to be purchased from the merchant by the consumer in a transaction, a transaction identifier for the transaction, and a digital signature. The acts also can include verifying the digital signature for the transaction code. The acts additionally can include sending, from the mobile device, a request to pay the merchant for the payment amount from a first account of the consumer maintained by a first financial institution, such that the first financial institution, upon receiving the request to pay, retrieves from a transaction system an account identifier of a second account of the merchant maintained by a second financial institution based on the merchant public identifier, such that the first financial institution sends to the transaction system payment information regarding a payment to be made to the second account from the first account, such that the payment information is routed through the transaction system to the second financial institution, and such that the point-of-sale terminal receives a notification of payment for the transaction in real-time while the consumer remains at the store of the merchant. The transaction system can be maintained by an entity that is different from the merchant, the first financial institution, and the second financial institution. The payment information can include the transaction identifier, the account identifier of the second account, and the payment amount. 
     Further embodiments include a method being implemented via execution of computing instructions configured to run at one or more processors and stored at one or more non-transitory computer-readable media. The method can include receiving, at a mobile device being used by a consumer, a transaction code from a point-of-sale terminal at a store of a merchant. The transaction code can include a merchant public identifier being associated with the merchant, a payment amount for one or more items to be purchased from the merchant by the consumer in a transaction, a transaction identifier for the transaction, and a digital signature. The method also can include verifying the digital signature for the transaction code. The method additionally can include sending, from the mobile device, a request to pay the merchant for the payment amount from a first account of the consumer maintained by a first financial institution, such that the first financial institution, upon receiving the request to pay, retrieves from a transaction system an account identifier of a second account of the merchant maintained by a second financial institution based on the merchant public identifier, such that the first financial institution sends to the transaction system payment information regarding a payment to be made to the second account from the first account, such that the payment information is routed through the transaction system to the second financial institution, and such that the point-of-sale terminal receives a notification of payment for the transaction in real-time while the consumer remains at the store of the merchant. The transaction system can be maintained by an entity that is different from the merchant, the first financial institution, and the second financial institution. The payment information can include the transaction identifier, the account identifier of the second account, and the payment amount. 
     Additional embodiments include a system including one or more processors and one or more non-transitory computer-readable media storing computing instructions configured to run on the one more processors and perform various acts. The acts can include receiving, at a first financial institution from a mobile device being used by a consumer, a request to pay a merchant for a payment amount from a first account of the consumer maintained by the first financial institution. The request to pay can include information including a merchant public identifier, a payment amount for one or more items to be purchased from the merchant by the consumer in a transaction, and a transaction identifier for the transaction. The mobile device can be used by the consumer at a store of the merchant to pay for the transaction. The information can be received by the mobile device from a point-of-sale terminal at the store of the merchant as part of a transaction code. The transaction code can be verified by the mobile device using a digital signature of the transaction code. The acts also can include retrieving, at the first financial institution from a transaction system, an account identifier for a second account of the merchant maintained by a second financial institution based on the merchant public identifier. The transaction system can be maintained by an entity that is different from the merchant, the first financial institution, and the second financial institution. The acts additionally can include sending, from the first financial institution to the transaction system, payment information regarding a payment to be made to the second account from the first account. The payment information can be routed through the transaction system to the second financial institution. The point-of-sale terminal can receive a notification of payment for the transaction in real-time while the consumer remains at the store of the merchant. The payment information can include the transaction identifier, the account identifier of the second account, and the payment amount. 
     Further embodiments include a method being implemented via execution of computing instructions configured to run at one or more processors and stored at one or more non-transitory computer-readable media. The method can include receiving, at a first financial institution from a mobile device being used by a consumer, a request to pay a merchant for a payment amount from a first account of the consumer maintained by the first financial institution. The request to pay can include information including a merchant public identifier, a payment amount for one or more items to be purchased from the merchant by the consumer in a transaction, and a transaction identifier for the transaction. The mobile device can be used by the consumer at a store of the merchant to pay for the transaction. The information can be received by the mobile device from a point-of-sale terminal at the store of the merchant as part of a transaction code. The transaction code can be verified by the mobile device using a digital signature of the transaction code. The method also can include retrieving, at the first financial institution from a transaction system, an account identifier for a second account of the merchant maintained by a second financial institution based on the merchant public identifier. The transaction system can be maintained by an entity that is different from the merchant, the first financial institution, and the second financial institution. The method additionally can include sending, from the first financial institution to the transaction system, payment information regarding a payment to be made to the second account from the first account. The payment information can be routed through the transaction system to the second financial institution. The point-of-sale terminal can receive a notification of payment for the transaction in real-time while the consumer remains at the store of the merchant. The payment information can include the transaction identifier, the account identifier of the second account, and the payment amount. 
     Additional embodiments include a system including one or more processors and one or more non-transitory computer-readable media storing computing instructions configured to run on the one more processors and perform various acts. The acts can include receiving, at a transaction system from a first entity, a request including a merchant public identifier associated with a merchant. The transaction system can be in data communication with a first financial institution that maintains a first account of a consumer and a second financial institution that maintains a second account of the merchant. The transaction system can be maintained by an entity that is different from the merchant, the first financial institution, and the second financial institution. The consumer can use a mobile device at a store of the merchant to pay for one or more items in a transaction. The mobile device can receive a transaction code from a point-of-sale terminal at the store. The transaction code can include a transaction identifier, a payment amount for the transaction, the merchant public identifier, and a digital signature. The transaction code can be verified by the mobile device using the digital signature of the transaction code. The acts also can include determining, at the transaction system, an account identifier of the second account based on the merchant public identifier using a merchant account database. The acts additionally can include sending the account identifier to the first financial institution. The acts further can include receiving, at the transaction system from the first financial institution, payment information regarding a payment to be made to the second account from the first account. The payment information can include the account identifier of the second account, the payment amount, and the transaction identifier. The acts additionally can include sending, from the transaction system to the second financial institution, the payment information, such that the point-of-sale terminal receives a notification of payment for the transaction in real-time while the consumer remains at the store of the merchant. 
     Further embodiments include a method being implemented via execution of computing instructions configured to run at one or more processors and stored at one or more non-transitory computer-readable media. The method can include receiving, at a transaction system from a first entity, a request including a merchant public identifier associated with a merchant. The transaction system can be in data communication with a first financial institution that maintains a first account of a consumer and a second financial institution that maintains a second account of the merchant. The transaction system can be maintained by an entity that is different from the merchant, the first financial institution, and the second financial institution. The consumer can use a mobile device at a store of the merchant to pay for one or more items in a transaction. The mobile device can receive a transaction code from a point-of-sale terminal at the store. The transaction code can include a transaction identifier, a payment amount for the transaction, the merchant public identifier, and a digital signature. The transaction code can be verified by the mobile device using the digital signature of the transaction code. The method also can include determining, at the transaction system, an account identifier of the second account based on the merchant public identifier using a merchant account database. The method additionally can include sending the account identifier to the first financial institution. The method further can include receiving, at the transaction system from the first financial institution, payment information regarding a payment to be made to the second account from the first account. The payment information can include the account identifier of the second account, the payment amount, and the transaction identifier. The method additionally can include sending, from the transaction system to the second financial institution, the payment information, such that the point-of-sale terminal receives a notification of payment for the transaction in real-time while the consumer remains at the store of the merchant. 
     Additional embodiments include a system including one or more processors and one or more non-transitory computer-readable media storing computing instructions configured to run on the one more processors and perform various acts. The acts can include performing, at a mobile device being used by a consumer, an identity authentication of the consumer. The acts also can include receiving, at the mobile device, first information from a point-of-sale terminal at a store of a merchant. The first information can include a merchant identifier, a transaction identifier, and a payment amount. The merchant identifier can be associated with the merchant. The payment amount can be for one or more items to be purchased from the merchant by the consumer in a transaction. The transaction identifier can be associated with the transaction. The acts additionally can include sending, from the mobile device, a request to pay the merchant for the payment amount from one or more first accounts of the consumer maintained by a first financial institution, such that the first financial institution, upon receiving the request to pay, retrieves from a transaction system an account identifier of a second account of the merchant maintained by a second financial institution based on the merchant identifier, such that the first financial institution sends to the transaction system payment information regarding a payment to be made to the second account from the one or more first accounts, such that the payment information is routed through the transaction system to the second financial institution, and such that the point-of-sale terminal receives a notification of payment for the transaction in real-time while the consumer remains at the store of the merchant. The one or more first accounts can include at least one non-demand deposit account. The transaction system can be maintained by an entity that is different from the merchant, the first financial institution, and the second financial institution. The payment information can include the transaction identifier, the account identifier of the second account, and the payment amount. 
     Further embodiments include a method being implemented via execution of computing instructions configured to run at one or more processors and stored at one or more non-transitory computer-readable media. The method can include performing, at a mobile device being used by a consumer, an identity authentication of the consumer. The method also can include receiving, at the mobile device, first information from a point-of-sale terminal at a store of a merchant. The first information can include a merchant identifier, a transaction identifier, and a payment amount. The merchant identifier can be associated with the merchant. The payment amount can be for one or more items to be purchased from the merchant by the consumer in a transaction. The transaction identifier can be associated with the transaction. The method additionally can include sending, from the mobile device, a request to pay the merchant for the payment amount from one or more first accounts of the consumer maintained by a first financial institution, such that the first financial institution, upon receiving the request to pay, retrieves from a transaction system an account identifier of a second account of the merchant maintained by a second financial institution based on the merchant identifier, such that the first financial institution sends to the transaction system payment information regarding a payment to be made to the second account from the one or more first accounts, such that the payment information is routed through the transaction system to the second financial institution, and such that the point-of-sale terminal receives a notification of payment for the transaction in real-time while the consumer remains at the store of the merchant. The one or more first accounts can include at least one non-demand deposit account. The transaction system can be maintained by an entity that is different from the merchant, the first financial institution, and the second financial institution. The payment information can include the transaction identifier, the account identifier of the second account, and the payment amount. 
     Additional embodiments include a system including one or more processors and one or more non-transitory computer-readable media storing computing instructions configured to run on the one more processors and perform various acts. The acts can include receiving, at a first financial institution from a mobile device being used by a consumer, a request to pay a merchant for a payment amount from one or more first accounts of the consumer maintained by the first financial institution. The one or more first accounts can include at least one non-demand deposit account. The request to pay can include information including a merchant identifier, a payment amount for one or more items to be purchased from the merchant by the consumer in a transaction, and a transaction identifier for the transaction. The mobile device can be used by the consumer at a store of the merchant to pay for the transaction. The information can be received by the mobile device from a point-of-sale terminal at the store of the merchant. The acts also can include retrieving, at the first financial institution from a transaction system, an account identifier for a second account of the merchant maintained by a second financial institution based on the merchant identifier. The transaction system can be maintained by an entity that is different from the merchant, the first financial institution, and the second financial institution. The acts additionally can include sending, from the first financial institution to the transaction system, payment information regarding a payment to be made to the second account from the one or more first accounts, such that the payment information is routed through the transaction system to the second financial institution, and such that the point-of-sale terminal receives a notification of payment for the transaction in real-time while the consumer remains at the store of the merchant. The payment information can include the transaction identifier, the account identifier of the second account, and the payment amount. 
     Further embodiments include a method being implemented via execution of computing instructions configured to run at one or more processors and stored at one or more non-transitory computer-readable media. The method can include receiving, at a first financial institution from a mobile device being used by a consumer, a request to pay a merchant for a payment amount from one or more first accounts of the consumer maintained by the first financial institution. The one or more first accounts can include at least one non-demand deposit account. The request to pay can include information including a merchant identifier, a payment amount for one or more items to be purchased from the merchant by the consumer in a transaction, and a transaction identifier for the transaction. The mobile device can be used by the consumer at a store of the merchant to pay for the transaction. The information can be received by the mobile device from a point-of-sale terminal at the store of the merchant. The method also can include retrieving, at the first financial institution from a transaction system, an account identifier for a second account of the merchant maintained by a second financial institution based on the merchant identifier. The transaction system can be maintained by an entity that is different from the merchant, the first financial institution, and the second financial institution. The method additionally can include sending, from the first financial institution to the transaction system, payment information regarding a payment to be made to the second account from the one or more first accounts, such that the payment information is routed through the transaction system to the second financial institution, and such that the point-of-sale terminal receives a notification of payment for the transaction in real-time while the consumer remains at the store of the merchant. The payment information can include the transaction identifier, the account identifier of the second account, and the payment amount. 
     Additional embodiments include a system including one or more processors and one or more non-transitory computer-readable media storing computing instructions configured to run on the one more processors and perform various acts. The acts can include receiving, at a transaction system from a first entity, a request including a merchant identifier associated with a merchant. The transaction system can be in data communication with a first financial institution that maintains one or more first accounts of a consumer and a second financial institution that maintains a second account of the merchant. The one or more first accounts can include at least one non-demand deposit account. The transaction system can be maintained by an entity that is different from the merchant, the first financial institution, and the second financial institution. The consumer can use a mobile device at a store of the merchant to authorize paying a payment amount for one or more items in a transaction using the one or more first accounts. The acts also can include determining, at the transaction system, an account identifier of the second account of the merchant maintained by a second financial institution using a merchant account database. The acts additionally can include sending the account identifier from the transaction system to the first financial institution. The acts further can include receiving, at the transaction system from the first financial institution, payment information regarding a payment to be made to the second account from the one or more first accounts. The payment information can include a transaction identifier, the account identifier of the second account, and the payment amount. The acts additionally can include sending, from the transaction system to the second financial institution, the payment information, such that a point-of-sale terminal at the store of the merchant receives a notification of payment for the transaction in real-time while the consumer remains at the store of the merchant. 
     Further embodiments include a method being implemented via execution of computing instructions configured to run at one or more processors and stored at one or more non-transitory computer-readable media. The method can include receiving, at a transaction system from a first entity, a request including a merchant identifier associated with a merchant. The transaction system can be in data communication with a first financial institution that maintains one or more first accounts of a consumer and a second financial institution that maintains a second account of the merchant. The one or more first accounts can include at least one non-demand deposit account. The transaction system can be maintained by an entity that is different from the merchant, the first financial institution, and the second financial institution. The consumer can use a mobile device at a store of the merchant to authorize paying a payment amount for one or more items in a transaction using the one or more first accounts. The method also can include determining, at the transaction system, an account identifier of the second account of the merchant maintained by a second financial institution using a merchant account database. The method additionally can include sending the account identifier from the transaction system to the first financial institution. The method further can include receiving, at the transaction system from the first financial institution, payment information regarding a payment to be made to the second account from the one or more first accounts. The payment information can include a transaction identifier, the account identifier of the second account, and the payment amount. The method additionally can include sending, from the transaction system to the second financial institution, the payment information, such that a point-of-sale terminal at the store of the merchant receives a notification of payment for the transaction in real-time while the consumer remains at the store of the merchant. 
     Additional embodiments include a system including one or more processors and one or more non-transitory computer-readable media storing computing instructions configured to run on the one more processors and perform various acts. The acts can include determining, at a point-of-sale terminal at a store of a merchant, a payment amount for one or more items to be purchased from the merchant by a consumer in a transaction. The acts also can include sending first information from the point-of-sale terminal to a mobile device used by the consumer. The first information can include a merchant identifier, a transaction identifier, and the payment amount, such that the mobile device sends a request to pay the merchant for the payment amount from one or more first accounts of the consumer maintained by a first financial institution, such that the first financial institution, upon receiving the request to pay, retrieves from a transaction system an account identifier of a second account of the merchant maintained by a second financial institution based on the merchant identifier, such that the first financial institution sends to the transaction system payment information regarding a payment to be made to the second account from the one or more first accounts, and such that the payment information is routed through the transaction system to the second financial institution. The one or more first accounts can include at least one non-demand deposit account. The transaction system can be maintained by an entity that is different from the merchant, the first financial institution, and the second financial institution. The payment information can include the transaction identifier, the account identifier of the second account, and the payment amount. The acts additionally can include receiving, at the point-of-sale terminal, a notification of payment for the transaction in real-time while the consumer remains at the store of the merchant. 
     Further embodiments include a method being implemented via execution of computing instructions configured to run at one or more processors and stored at one or more non-transitory computer-readable media. The method can include determining, at a point-of-sale terminal at a store of a merchant, a payment amount for one or more items to be purchased from the merchant by a consumer in a transaction. The method also can include sending first information from the point-of-sale terminal to a mobile device used by the consumer. The first information can include a merchant identifier, a transaction identifier, and the payment amount, such that the mobile device sends a request to pay the merchant for the payment amount from one or more first accounts of the consumer maintained by a first financial institution, such that the first financial institution, upon receiving the request to pay, retrieves from a transaction system an account identifier of a second account of the merchant maintained by a second financial institution based on the merchant identifier, such that the first financial institution sends to the transaction system payment information regarding a payment to be made to the second account from the one or more first accounts, and such that the payment information is routed through the transaction system to the second financial institution. The one or more first accounts can include at least one non-demand deposit account. The transaction system can be maintained by an entity that is different from the merchant, the first financial institution, and the second financial institution. The payment information can include the transaction identifier, the account identifier of the second account, and the payment amount. The method additionally can include receiving, at the point-of-sale terminal, a notification of payment for the transaction in real-time while the consumer remains at the store of the merchant. 
     Turning to the drawings,  FIG. 1  illustrates a block diagram of a system  100  that can be employed for a secure real-time payment transaction network, according to an embodiment. System  100  is merely exemplary and embodiments of the system are not limited to the embodiments presented herein. The system can be employed in many different embodiments or examples not specifically depicted or described herein. In some embodiments, certain elements or modules of system  100  can perform various procedures, processes, and/or activities. In other embodiments, the procedures, processes, and/or activities can be performed by other suitable elements or modules of system  100 . 
     In some embodiments, system  100  can include one or more point-of-sale terminals, such as point-of-sale terminal  110 ; one or more mobile devices, such as mobile device  120 ; two or more financial institutions, such as financial institutions  130  and  150 ; and/or a transaction system  140 . In other embodiments, system  100  also can include a wallet provider  160 . In a number of embodiments, each of the point-of-sale terminals, the one or more mobile devices, the two or more financial institution, and the transaction system can be or include a computer system, such as computer system  700 , as shown in  FIG. 7  and described below, and can be a single computer, a single server, or a cluster or collection of computers or servers, or a cloud of computers or servers. In many embodiments, various components (e.g.,  110 ,  120 ,  130 ,  140 ,  150 ,  160 ) of system  100  can be in data communication with various other components (e.g.,  110 ,  120 ,  130 ,  140 ,  150 ,  160 ) of system  100 , such as through one or more networks. The networks can be the Internet and/or other suitable public and/or private data communication networks. 
     In various embodiments, point-of-sale terminal  110  can be located within a store of a merchant, such as merchant  119 . In several embodiments, the store can be a place of business, which can offer and/or sell items, such as products and/or services. In a number of embodiments, point-of-sale terminal  110  can be used to checkout a consumer  129  using mobile device  120  for one or more items to be purchased by consumer  129 . In many embodiments, point-of-sale terminal  110  can include one or more modules, such as a checkout module  111 , a communication module  112 , a payment module  113 , a consumer information module  114 , a security module  115 , and/or other suitable modules. For example, in various embodiments, checkout module  111  can be used to determine the payment amount, communication module  112  can communicate with other components of system  100 , payment module  113  can determine whether consumer  129  has satisfactorily paid for the one or more items to be purchased, consumer information module  114  can store information regarding consumer  129 , and/or security module  115  can be used to generate a merchant security transaction code, as described below in further detail. In many embodiments, point-of-sale terminal  110  can be a register (e.g., cash register) that includes a card reader and communications with one or more card networks (e.g., STAR network, VISA network, etc.). In other embodiments, point-of-sale terminal  110  can be a register that without a card reader or the ability to communicate with card networks. 
     In a number of embodiments, mobile device  120  can be used by consumer  129  to initiate a payment to merchant  119  for the one or more items to be purchased. In various embodiments, mobile device  120  can run a mobile application  123 , such as a mobile wallet, which can be employed to facilitate paying merchant  119 . In a number of embodiments, mobile device  120  and/or mobile application  123  can include one or more modules, such as an authentication module  121 , an account module  122 , a communication module  124 , a security module  125 , a loan module  126 , and/or other suitable modules. For example, in various embodiments, authentication module  121  can verify the identity of consumer  129 , account module  122  can provide information regarding a consumer account of consumer  129 , communication module  124  can communicate with other components of system  100 , security module  125  can decipher and/or decode the merchant security transaction code and/or verify the digital signature of the merchant security transaction code, and/or loan module can present options and receive instructions regarding processing the transaction at least partially using a loan or credit charge. 
     In several embodiments, when consumer  129  using mobile device  120  is at point-of-sale terminal  110  to checkout, point-of-sale terminal  110  can determine the payment amount for the one or more items, and can communicate information to mobile device  120 , such as the payment amount, a merchant identifier, and/or a transaction identifier. In some embodiments, the merchant identifier can uniquely identify point-of-sale terminal  110 . For example, in some embodiments, each point-of-sale terminal can have a unique merchant identifier. In a number of embodiments, the merchant identifier can uniquely identify the merchant (e.g., merchant  119 ). For example, each merchant (e.g., merchant  119 ) can have a unique merchant identifier. In some embodiments, the merchant identifier can be a token that can be associated with merchant  119  and/or point-of-sale terminal  110 . In many embodiments, when merchant  119  sets up, configures, and/or reconfigures, point-of-sale terminal  110 , the merchant identifier can be created and/or assigned to point-of-sale terminal  110 . In the same or different embodiments, one part of the merchant identifier can uniquely identify merchant  119 , and another part of the merchant identifier can uniquely identify point-of-sale terminal  110 , such that the part of the merchant identifier that uniquely identifies merchant  119  is the same for all point-of-sale terminals owned or used by merchant  119 . 
     In various embodiments, mobile device  120  and point-of-sale terminal  110  can communicate with each other (either one-way or two-way) using a wireless data communication protocol. In some examples, the communication protocol can allow for one-way or two-way communication. For example, the wireless data communication protocol can be a proximity-based wireless data communication protocol, such as Near Field Communication (NFC), Bluetooth, Bluetooth Low Energy (BLE), iBeacon, etc. In other embodiments, mobile device  120  and/or point-of-sale terminal  110  can communicate with each other using another suitable form of communication. For example, in some embodiments, point-of-sale terminal  110  can provide a barcode (such as a QR (Quick Response) code), which can be scanned using a camera of mobile device  120 , and/or mobile device  120  can provide a barcode (such as a QR code), which can be scanned using an optical scanner of point-of-sale terminal  110 . In a number of embodiments, communication module  112  can provide communication functionality for point-of-sale terminal  110 , and/or communication module  124  can provide communication functionality for mobile device  120 . 
     In several embodiments, transaction system  140  can be in data communication with various financial institutions, such as financial institution  130  and/or financial institution  150 , and can provide for interaction, facilitate communications, and/or facilitate transactions between the financial institutions, such as financial institutions  130  and  150 . In a number of embodiments, transaction system  140  can include one or more modules, such as a communication module  143 , an account module  144 , a transaction module  145 , a security module  146 , and/or other suitable modules. In some embodiments, communication module can be used to provide communications with the financial institutions (e.g.,  130 ,  150 ). In many embodiments, transaction system  140  can include a merchant account database  141  and/or a transaction database  142 , as described below in further detail. In some embodiments, account module  144  can interface with merchant account database  141 , and/or transaction module  145  can interface with transaction database  142 . In a number of embodiments, security module  146  can interface with security module  115  to facilitate providing a merchant security code, as described below in further detail. In many embodiments, transaction system  140  can include a network system that facilitates communications between the various financial institutions (e.g., financial institution  130  and financial institution  150 ). This network system can have any suitable topology, such as hub and spoke, peer-to-peer, or another suitable topology. 
     In a number of embodiments, the financial institutions (e.g.,  130 ,  150 ) can be depository financial institutions, such as savings banks, credit unions, savings and loan associations, card issuing financial institutions, or other forms of financial institutions. In a number of embodiments, financial institution  130  can include one or more consumer accounts  131  associated with consumer  129 . In various embodiments, consumer accounts  131  can include one or more demand deposit accounts (e.g., a checking account, savings account, or cash balance account), and non-demand deposit accounts (i.e., an account other than a demand deposit account), such as a lending account (e.g., a loan account or a credit account) or another type of account (e.g., a points account). In some embodiments, financial institution  130  can include one or more modules, such as a communication module  132 , an authorization module  133 , an account module  134 , a loan module  135 , and/or other suitable modules. For example, in some embodiments, account module  134  can interface with consumer account  134  to provide information regarding the status of one or more of consumer accounts  131 , and/or can store and/or determine information regarding other accounts. In a number of embodiments, communication module  132  can communicate with other components of system  100 . In various embodiments, authorization module  133  can authorize payments from one or more of consumer accounts  131 . In a number of embodiments, account module  134  can obtain information, such as balances and statuses, about one or more of consumer accounts  131 . 
     In a number of embodiments, financial institution  150  can be include a merchant account  151  associated with merchant  119 . In various embodiments, merchant account  151  can be a deposit account or another suitable type of account. In some embodiments, financial institution  135  can include one or more modules, such as communication module  152 , account module  153 , and/or other suitable modules, as described below in further detail. For example, in some embodiments, account module  153  can interface with merchant account  151  to provide information regarding the status of merchant account  151 , and/or can store and determine information regarding other accounts. In a number of embodiments, communication module  152  can communicate with other components of system  100 . 
     In several embodiments, merchant account database  141  of transaction system  140  can store information regarding merchants (e.g., merchant  119 ) and merchant accounts. For example, in a number of embodiments, merchant account database  141  can store a mapping between merchant identifiers and merchant accounts. For example, a certain merchant identifier can be associated with merchant  119  and merchant account  151  of merchant  119  maintained by financial institution  150 . When provided with the merchant identifier, account module  144  and merchant account database  141  can be used by transaction system  140  to determine an account identifier (e.g., an account number) of merchant account  151 , the name of merchant  119 , a location of merchant  119 , a location of point-of-sale terminal  110 , and/or other information regarding merchant  119  and/or the merchant account. For example, in some embodiments, transaction system  140  can provide risk information (e.g., a risk score) regarding merchant  119  and/or merchant account  151 . In some embodiments, a merchant can have three point-of-sale terminals, such as point-of-sale terminal  110 , each with a unique identifier, which can each be associated with a single account of merchant  119 , specifically, merchant account  151 . 
     In many embodiments, the merchant identifier can be a public identifier that serves as an alias to identify merchant  119  and/or point-of-sale terminal  110  of merchant  119  among the various components (e.g.,  110 ,  120 ,  130 ,  140 ,  150 ,  160 ) of system  100 . In a number of embodiments, merchant  119  can enroll and/or register with transaction system  140  through financial institution  150 , through a merchant consortium, e.g., Merchant Customer Exchange (MCX), or directly. In several embodiments, the merchant identifier for merchant  119  and or point-of-sale terminal  110  of merchant  119  can be selected and/or assigned at the time of enrollment or registration. In some embodiments, the merchant identifier can be a phone number, an email address, a terminal identifier, or another suitable identifier. As part of enrollment and/or registration transaction system  140  can verify that merchant  119  is a legitimate (e.g., bona fide) merchant, such as by vetting merchant  119  through financial institution  150  and/or another enrollment entity. 
     In several embodiments, upon or after enrolling and/or registering with transaction system  140 , merchant  119  and/or point-of-sale terminal  110  can be provided with a security module  115 , which can be computing instructions that is used to create a merchant security transaction code. In some embodiments, security module  115  of point-of-sale terminal  110  can communicate with security module  146  of transaction system  140 , such as through application programming interface (API) calls. In other embodiments, security module  115  of point-of-sale terminal  110  can be self-contained computing instructions (i.e., that do not call security module  146  of transaction system  140 ) that are provided by transaction system  140  (e.g., at the time of enrollment and/or registration), or are based on instructions and/or a software development kit (SDK) provided by transaction system  140  (e.g., at the time of enrollment and/or registration). 
     In many embodiments, security module  115  can be used by merchant  119  during a transaction to generate a merchant security transaction code. In many embodiments, the merchant security transaction code can include various information, such as the payment amount for the transaction, a transaction identifier that uniquely identifies the transaction to merchant  119  and/or point-of-sale terminal  110 , the merchant identifier, a date and/or time of the transaction, a list of the items purchased, a digital signature, and/or other suitable information. In many embodiments, this information can be encoded in the merchant security transaction code using a suitable data encoding method. In many embodiments, the digital signature can be generated based on the data in the merchant security transaction code. The digital signature can be generated using a suitable digital signature code signing algorithm as part of a digital signature scheme. For example, the code signing algorithm can be public-key cryptography signing algorithm, such as those used in public key infrastructure (PKI), a cryptographic hash function, such as one of the Secure Hash Algorithm (SHA) published by the National Institutes of Standards and Technology (NIST) (e.g., SHA-256), or another suitable signing algorithm. The digital signature can be used to verify that merchant  119  created the merchant security transaction code and/or that the data in the merchant security transaction code has not been corrupted or tampered with after having being created by security module  115 . 
     In several embodiments, the merchant security transaction code can be a data code that can be transmitted between point-of-sale terminal  110  and mobile device  120  using a wireless data communication channel, as described above. In other embodiments, the merchant security transaction code can be encoded as a barcode, such as a one-dimensional (1D), two-dimensional (2D), or three-dimensional (3D) barcode, which can be optically ready by mobile device  120 , such as by using a camera on mobile device  120 , as described above. For example, the merchant security transaction code can be encoded as a matrix barcode, such as a QR code, and displayed on point-of-sale terminal  110  to be scanned by a camera on mobile device  120 . In still other embodiments, the merchant security transaction code can be transferred manually from point-of-sale terminal  110  to mobile device  120  by the merchant security transaction code being displayed on point-of-sale terminal  110  and then being manually entered in mobile application  123  of mobile device  120 . 
     In many embodiments, system  100  can provide a transaction network for secure real-time payments. In several embodiments, mobile application  123  of mobile device  120  can be used by consumer  129  to push a payment from one or more of consumer accounts  131  to merchant account  151  to satisfy an expectation of payment while consumer  129  is waiting at point-of-sale terminal  110 . In a number of embodiments, mobile application  123  can be associated with and/or configured to be associated with financial institution  130  and/or one or more of consumer accounts  131 . For example, account module  122  can associate mobile application  123  with one or more of consumer accounts  131  at financial institution  130 . In some embodiments, mobile application  123  can be provided by financial institution  130  as a mobile application for use on mobile device  120 . In other embodiments, mobile application  123  can be associated with multiple different financial institutions and accounts of consumer  129  at those financial institutions. In some embodiments, mobile device  120  can be in data communication with financial institution  130  directly through a network, such as the Internet, or indirectly through one or more other systems, such as mobile wallet provider  160 . In some embodiments, mobile device  120  can communicate with transaction system  140  directly through a network or through mobile wallet provider  160 . In other embodiments, mobile device  120  cannot communicate with transaction system  140 . 
     In several embodiments, mobile application  123  can provide information to consumer  129  regarding the status of one or more of consumer accounts  131  and availability of funds in one or more of consumer accounts  131 . For example, account module  122  of mobile device  120  can obtain information from account module  134  of financial institution  130  regarding one or more of consumer accounts  131  and provide that information to consumer  129 . For example, if one of consumer accounts  131  has an available balance and/or available credit of $500, mobile application  123  can communicate the amount of the available funds for one or more of consumer accounts  131  to consumer  129 , which can allow consumer  129  to know the amount of the available funds for spending before shopping for items and/or before attempting to purchase items. In a number of embodiments, account module  134  can provide account module  122  with various other information, such as the current status of one or more of consumer accounts  131 , such as whether one or more of consumer accounts  131  is open and in good status (or closed), whether one or more of consumer accounts  131  has had recent not sufficient funds (NSF) activity, whether one or more of consumer accounts  131  has a stop payment order, and/or a buying power index of consumer  129  at least partially based on information about one or more of consumer accounts  131 . 
     In some embodiments, mobile application  123  can be used on mobile device  120  at point-of-sale terminal  110  to conduct a transaction. In several embodiments, mobile device  120  can receive the merchant identifier and other transaction information from point-of-sale terminal  110  of merchant  119 . The merchant identifier can be associated with merchant account  151  of merchant  119 . By receiving the merchant identifier, mobile application  123  can initiate a push payment from one or more of consumer accounts  131  at financial institution  130  to merchant account  151  at financial institution  150  to complete the transaction in real-time before the consumer leaves the store of merchant  119 . In many embodiments, mobile device  120  can receive the merchant identifier and other transaction information from point-of-sale terminal  110  as part of the merchant security transaction code. 
     In various embodiments, authentication module  121  can verify the identity of consumer  129 . For example, authentication module  121  can verify the identity of consumer  129  using a personal identification number (PIN), a password, one or more fingerprints, voice recognition, other biometrics (e.g., mobile phone bio-measurements), and/or other suitable authentication methods, to ensure that consumer  129  is authorized to associate mobile application  123  with one or more of consumer accounts  131  and/or make payments using mobile application  123 . 
     In a number of embodiments, when mobile application  123  is used to conduct a transaction, mobile device  120  can be put in the proximity of point-of-sale terminal  110  to allow communication module  124  to receive information from point-of-sale terminal  110 , such as the payment amount, the merchant identifier, a transaction identifier, and/or other information, such as the merchant name, the date and time, a list of SKUs (stock keeping units) of the one or more items to be purchased, etc. In many embodiments, mobile device  120  can receive the merchant identifier and other transaction information from point-of-sale terminal  110  as part of the merchant security transaction code. In several embodiments, security module  125  of mobile device  120  can verify the digital signature in the merchant security transaction code. For example, security module  125  can verify the digital signature using a signature verifying algorithm that is part of the same digital signature scheme that was used to digitally sign the merchant security transaction code. For example, a public key for merchant  119  can be used to verify the digital signature and the merchant security transaction code. By verifying the digital signature of the merchant security transaction code, security module  125  can verify that the merchant identifier is from point-of-sale terminal  110  of merchant  119  and is accurate, which can advantageously ensure that the funding from consumer accounts  131  will be sent to an account actually associated with the merchant instead of a fraudster. 
     In some embodiments, mobile application  123  can be configured to allow one-click checkout, which can be enabled by selecting a button on mobile application  123  or by placing mobile device  120  in the proximity of a data transmitter on point-of-sale terminal  110 . In some embodiments, mobile application  123  can be configured to scan items and conduct transactions in real-time as items are taken from the shelf and scanned by mobile device  120  or placed within a “smart” shopping cart, such that checkout can take place in an aisle of the store, rather than at point-of-sale terminal  110 . In other embodiments, checkout can take place automatically when consumer  129  exits the store of merchant  119 . In a number of embodiments, mobile application  123  can receive the merchant identifier upon entering the store of merchant  119  or from a shopping cart having data transmitted in the store of merchant  119 . 
     In some embodiments, the mobile application  123  can send information from mobile device  120  to point-of-sale terminal  110 , such as information regarding consumer  129 , such as personally identifiable information, loyalty rewards number(s), shopping patterns, points, buying power index, and/or other suitable information. In several embodiments, consumer information module  114  can process the information provided from mobile application  123  to provide information to merchant  119  regarding consumer  129 . In some embodiments, mobile device  120  can communicate information, such as a buying power index, to point-of-sale terminal  110  and/or merchant  119  upon entering the store of merchant  119 . 
     In several embodiments, consumer  129  can decide whether to authorize the transaction using mobile device  120 . For example, mobile device  120  can ask consumer  129  to approve the transaction in mobile application  123 . In a number of embodiments, mobile application  123  can present the one or more of consumer accounts  131  to consumer  129  to select which of the consumer accounts  131  to use to funds the transaction. In some embodiments, consumer  129  can choose to split the funding of the transaction among multiple accounts. For example, consumer  129  can choose to fund 20% of the transaction from a demand deposit account (e.g., a debit account) and 80% of the transaction from a non-demand deposit account (e.g., by a charge to a credit account). In some embodiments, if an account of the one or more of consumer accounts  131  has an account balance that is less than the amount of the transaction (or the portion of the transaction that consumer  129  has chosen to allocate to the account), loan module  126  of mobile device  120  can determine that there is a deficiency and can present an option to fund the transaction (or a portion of the transaction) using a non-demand deposit account, such as a loan account, a credit account, or a points account. In other embodiments, loan module  126  can present the option for funding the transaction through a non-demand deposit account even if there is no deficiency in the one or more of consumer accounts  129 . 
     In some embodiments, the loan account can be a new account that is created upon consumer  129  choosing to fund the transaction (or portion thereof) with the loan account. In other embodiments, the loan account can be for a previously authorized loan. In some embodiments, the loan account can have a pre-existing loan balance, which can be increased based on the amount of loan used to the fund the transaction. In several embodiments, the loan can be a small loan, and can be labeled a “micro-loan”), but can be treated the same as credit line for a loan instead of an overdraw of an account. 
     In several embodiments, consumer  129  can make the decision from which account or accounts to fund the transaction, and/or to authorize a loan or a credit transaction, while at or near the point-of-sale terminal  110  in the store of merchant  119 . In the same or other embodiments, loan module  126  can allow consumer  129  to choose the one or more accounts from which to fund the transaction after consumer  129  has left the store. In many embodiments, financial institution  130  can fund the transaction temporarily from a shadow account that the bank uses to fund overdraft transaction, which can be reimbursed from the one or more accounts selected by consumer  129 . For example, consumer  129  can authorize a transaction at point-of-sale terminal  110  in the store, and financial institution  130  can authorize transfer of funds to financial institution  150  to pay merchant  119 , and after consumer  129  leaves the store of merchant  129 , loan module  126  can push a message to consumer  129  asking for one or more of consumer accounts  131  that consumer  129  wants to use to fund the transaction. The options of consumer accounts  131  can include the option to open a new loan account, or to add to the balance of an existing loan account. In some embodiments, consumer  129  can setup a list (e.g., prioritized list) of consumer accounts  131  to use for transaction using mobile device  120 , and/or can setup before-hand an amount and/or percentage to use from one or more of the accounts. For example, consumer  129  can choose to use a debit account for the first $50 and then use a credit account for the rest. As another example, consumer  129  can choose to use a debit account for 40% of the transaction, and use a new micro-loan for the rest. 
     In some embodiments, a points account can be used to pay for all or at least a portion of the payment. For example, consumer  129  can have a points account at financial institution  130 , which can have a balance of points earned by consumer  129  at financial institution  130 . In many embodiments, these points can have an exchange value, such that the points can be redeemed to pay for all or at least a portion of the payment. 
     In many embodiments, after mobile device  120  has communicated with point-of-sale terminal  110  using communication module  124  to receive the merchant identifier and other transaction information, and consumer  129  has authorized the transaction, mobile device  120  can communicate with financial institution  130  and/or transaction system  140 , either directly or through mobile wallet provider  160 , to request a payment be made to merchant account  151  of merchant  119  from one or more of consumer accounts  131 . For example, when mobile device  120  communicates with financial institution  130  (either directly or through mobile wallet provider  160 ) to request a payment be made, account module  134  of financial institution  130  can determine account information about merchant account  151 , such as the account identifier of merchant account  151 , at least partially based on the merchant identifier received from mobile device  130 . In some embodiments, financial institution  130  can communicate with transaction system  140  to get the account information about merchant account  151 , which can be stored in merchant account database  141 . In some embodiments, financial institution  130  can save the account information about merchant account  151  so financial institution does not need to query the account information from merchant account database  141  in transaction system  140  for future transaction involving the same merchant identifier. In other embodiments, financial institution  130  can query for the account information from merchant account database  141  in transaction system  140  for each new transaction, or at occasional and/or regular intervals. In other embodiments, when mobile device  120  communicates with transaction system  140  (either directly or through mobile wallet provider  160 ) to request a payment be made, transaction system  140  can provide the account information about merchant account  151  to first financial institution  130 . 
     In many embodiments, having the account information about merchant account  151 , financial institution  130  can initiate a payment to financial institution  150  from one or more of consumer accounts  131  to merchant account  151 . In several embodiments, before initiating payment, authorization module  133  can determine whether to authorize payment from one or more of consumer accounts  131 . For example, financial institution  130  can determine whether the payment amount is within the available funds in one or more of consumer accounts  131 , determine whether one or more of consumer accounts  131  is currently open and in good status (or closed), authenticate the identity of consumer  129  using mobile device  120 , and/or perform other actions. For example, in some embodiments, authentication module  121  can authenticate the identity of consumer  129 , and that information can be communicated from mobile device  120  to financial institution  130 . In some embodiments, mobile device  120  can prompt consumer  129  to authenticate before and/or after mobile device  120  receives the merchant identifier and/or the transaction information from point-of-sale terminal  110 . 
     In some embodiments, authorization module  133  can request additional authentication from authentication module  121  (which can be directly through a network between financial institution  130  and mobile wallet  120 , or can be through mobile wallet provider  160  and/or through transaction system  140 ) after receiving the request for payment from mobile device  120  and/or after receiving the information about merchant  119  and/or merchant account  151 . In a number of embodiments, authorization module  133  of financial institution  130  can perform different and/or varying levels of authentication based on various factors. For example, authentication module  121  and/or authorization module  133  can determine whether mobile device  120  used to send the request for payment has been previously used by consumer  129  for transaction with financial institution  130 , whether biometrics of the consumer match stored biometrics of consumer  129 , whether the requested transaction and associated details (e.g., the identity of merchant  119 , the location of merchant  119 , the payment amount, the one or more items to be purchased (e.g., a list of SKUs), and/or other suitable factors) are consistent with spending patterns of consumer  129 , whether consumer  129  has reported mobile device  120  lost or stolen, whether consumer  129  has reported that credit cards, debit cards, or other information about one or more of consumer accounts  131  have been lost or stolen, and/or other suitable factors. In various embodiments, financial institution  130  can adjust the level of authentication used to verify the identity of consumer  129  based on one or more of these factors, and/or based on the payment amount, the identity of merchant  119 , the location of merchant  119 , historical spending of consumer  129 , and/or other relevant information. 
     In some embodiments, if one or more of consumer accounts  131  chosen by consumer  129  for the transaction is short on funds or otherwise cannot be fully used, loan module  135  can communicate with loan module  126  to present other funding options to consumer  129 , such as the option for a micro-loan to fund all or part of the transaction, as described above. 
     In many embodiments, after receiving authorization from authorization module  133 , financial institution  130  can initiate a payment to financial institution  150  to transfer funds from one or more of consumer accounts  131  to merchant account  151 . In a number of embodiments, the payment can be effected by sending payment information regarding a payment to be made to merchant account  151  from one or more of consumer accounts  131 . In a number of embodiments, the payment information transferred from financial institution  130  to financial institution  150  can effectuate an authenticated credit push, which can irrevocably satisfy payment to the merchant and/or ensure that the merchant has good funds when consumer  129  leaves the store of merchant  119 . For example, the payment can be a settlement credit push of funds for the payment amount from one or more of consumer accounts  131  to merchant account  151 , which can be settled immediately. In various embodiments, the payment information transferred from financial institution  130  to financial institution  150  can effectuate a push promise to pay, which can provide an irrevocable guarantee of payment from financial institution  130  to financial institution  150 . In several embodiments, for example, the payment can be an ACH (Automated Clearing House) credit push, which can provide an irrevocable funding guarantee. 
     In many embodiments, the payment and/or the guarantee of payment can be sent in real-time from financial institution  130  to financial institution  150 , which can happen for each such transaction. In some embodiments, the settlement of the transaction can happen later, such as in a nightly batch fashion, and in some embodiments, can happen through a different network, such as an ACH network or a credit network. In other embodiments, the real-time payment and/or guarantee of payment can be processed through an ACH network or a credit network. In some embodiments, the consumer can provide instructions to financial institution  130  to label the transaction as a debit or a credit transaction in one or more of consumer accounts  131 , and in some embodiments can provide such instructions with the request to pay, or before or after the request to pay. In some embodiments, a credit transaction can be treated as a micro-loan, as described above. In certain embodiments, a debit pull with guaranteed promise to pay can be used, such that financial institution  150  can receive a guaranteed promise to pay from financial institution  130  and pull the funds using a debit pull. 
     In various embodiments, transaction system  140  can store information regarding each transaction in transaction database  142 . In several embodiments, transaction system  140  can serve as a central auditor for transactions between the financial institutions (e.g.,  130 ,  150 ) in data communication with transaction system  142 . In some embodiments, transaction system  140  can receive some or all of the information from the merchant security transaction code. In various embodiments, one or more portions of the merchant security transaction code can be encrypted by security module  115 . For example, the merchant security transaction code can include an encrypted portion that can be decrypted by security module  146  of transaction system  140 , which can be used to ensure that the message has not been tampered. In other embodiments, the merchant security transaction code is not encrypted, but is digitally signed, as described above, and the digital signature can be verified, in some embodiments, by security module  146 , which can advantageously ensure that the merchant identifier correctly identifies merchant  119 , so that the funds are paid to merchant account  151  corresponding to merchant  119 . 
     In a number of embodiments, financial institution  150 , upon receiving payment and/or guarantee of payment, can notify point-of-sale terminal  110  and/or merchant  119  in real-time that merchant  119  has satisfactorily received payment from consumer  129 . For example, the notification can include various information, such as the transaction identifier, the amount received in payment (or guarantee), the merchant identifier, and/or other information. Receiving the notice of good funds can allow merchant  119  to proceed, such as, for example, to allow consumer to leave the store of merchant  119  with the items. In some embodiments, for example, point-of-sale terminal  110  can match the notification to the pending transaction in point-of-sale terminal  110  using the transaction identifier. In certain embodiments, merchant  119  can match the notification to the point-of-sale terminal using the merchant identifier. In some embodiments, consumer  129  can receive a notification on mobile device  120  that the transaction has cleared, such as shown in  FIG. 22  and described below. 
     In several embodiments, system  100  can advantageously provide a number of technological improvements that can overcome technological problems in conventional systems. For example, in several embodiments, system  100  can beneficially allow consumer  129  to send payment directly and/or immediately to merchant  119  when consumer  129  is checking out at point-of-sale terminal  110 . In many embodiments, the payment systems and methods provided by system  100  described herein can eliminate the acquirer model that is conventionally used in payment card transactions. In several embodiments, the payment systems and methods provided by system  100  described herein can advantageously streamline payments by eliminating the need for the financial institution (i.e., the acquirer) of merchant  119  to request payment from the financial institution (i.e., the issuer) of consumer  129 . For example, in many embodiments, financial institution  150  does not need to request payment from financial institution  130 . In many embodiments, the payment systems and methods provided by system  100  described herein can beneficially ensure merchants (e.g., merchant  119 ) are paid by consumers (e.g., consumer  129 ) while eliminating and/or reducing many of the transaction fees paid to various entities in the conventional model. 
     In a number of embodiments, the payment systems and methods provided by system  100  described herein can advantageously eliminate the chargeback liability of merchants for fraudulent transactions. In the conventional acquirer-issuer model, the merchant (e.g.,  119 ) is responsible for verifying the credit or debit card to ensure that the card is not being used fraudulently. In several embodiments, the payment systems and methods provided by system  100  described herein can beneficially place the liability on the financial institution (e.g.,  130 ) of the consumer (e.g.  129 ), which can be in a better position (e.g., with more and/or better information) than the merchant (e.g.,  119 ) to determine if the request to pay is a legitimate, authentic transaction requested by the consumer (e.g.,  129 ) and/or if the consumer&#39;s account is still open and in good status (or closed), has sufficient funds, etc. In various embodiments, the payment systems and methods provided by system  100  described herein can advantageously allow the financial institution (e.g.,  130 ) of the consumer (e.g.,  129 ) to choose how to authenticate the consumer (e.g.,  129 ), and/or can beneficially allow the financial institution (e.g.,  130 ) of the consumer (e.g.,  129 ) to choose the level of authentication, which can be tailored for each consumer (e.g.,  129 ) and/or for each transaction (e.g., the financial institution (e.g.,  130 ) can decide, at least partially based on its risk determination, that a transaction with a higher payment amount warrants a higher level of authentication). In several embodiments, the liability for fraudulent use of one or more of the consumer accounts (e.g.,  131 ) can be placed on the consumer (e.g.,  129 ), and/or the consumer (e.g.,  129 ) can choose the level of authentication used by the financial institution (e.g.,  130 ) of the consumer (e.g.,  129 ). In many embodiments, unauthorized access to one or more of consumer accounts  131  can beneficially be reduced and/or eliminated using the payment method provided by system  100  and described herein. 
     In several embodiments, the payment systems and methods provided by system  100  described herein can beneficially provide the ability for financial institution  130  to communicate directly with consumer  129  at point-of-sale  110  when making a transaction. In many embodiments, the payment systems and methods provided by system  100  described herein can provide information to consumer  129 , such as account balance, insufficient funds, lock/freeze on one or more of consumer accounts  131 , etc., in real-time before consumer  129  requests payments, which can advantageously eliminate and/or reduce negative experiences of consumer  129 , such as attempting to transact with insufficient funds or a freeze on one or more of consumer accounts  131 . In a number of embodiments, the payment systems and methods provided by system  100  described herein can beneficially provide consumer  129  with the ability the ability to split the payment with one or more other accounts or a new loan, such as a micro-loan, which can allow consumer  129  to successfully make the payment and reduce negative experiences of consumer  129 . 
     In some embodiments, account information about one or more of consumer accounts  131  can beneficially be better protected from theft by the payment systems and methods provided by system  100  described herein, because, in a number of embodiments, the account information of one or more of consumer accounts  131  and/or personally identifiable information of consumer  129  can be undisclosed to third parties other than financial institution  130 , which maintains consumer accounts  131 . For example, in some embodiments, the account information of consumer accounts  131  and/or personally identifiable information of consumer  129  can be undisclosed to point-of-sale terminal  110 , merchant  119 , transaction system  140 , and/or financial institution  150 . In many embodiments, the account identifier (e.g., account number) of consumer accounts  131  is not sent across any networks, but resides solely in financial institution  130 , which can beneficially prevent that information from being stolen. For example, the many recent large-scale data breaches of merchant systems that have exposed consumer account information and personally identifiable information of millions of consumers could have been mitigated by using the payment systems and methods provided by system  100  and described herein. 
     In other embodiments, consumer  129  can choose to provide account information of one or more of consumer accounts  131  and/or personally identifiable information of consumer  129  to one or more third parties. For example, in some embodiments consumer  129  can set privacy instructions in mobile device  120  and/or with financial institution  130  regarding what information can be disclosed to third parties. For example, consumer  129  can elect to disclose certain information to merchant  119  in order to receive discounts, point, and/or other perks from merchant  119 . For example, in some embodiments, financial institution  130  can send certain personally identifiable information of consumer  129  through transaction system  140  to financial institution  150  along with the payment information, and financial institution  150  can provide the information to merchant  119 . In the same or other embodiments, mobile device  120  can provide certain personally identifiable information of consumer  129  to merchant  119 , such as through the wireless data communication protocol. Examples of such personally identifiably information can include a name, a home address, a telephone number, a social security number, a tax identification number, an age, an income level, marital status, a number of dependents, a frequent shopper identifier, shopping preferences, etc. 
     In various embodiments, the payment systems and methods provided by system  100  described herein also can beneficially shield the account information about merchant account  151  from being disclosed outside a network of financial institutions (e.g.,  130 ,  150 ) and transaction system  140 , which can beneficially prevent theft and misuse of the account information about merchant account  151 . 
     Turning ahead in the drawings,  FIG. 2  illustrates a flow chart for a method  200 , according to an embodiment. In some embodiments, method  200  can be a method of facilitating secure payment transactions. Method  200  is merely exemplary and is not limited to the embodiments presented herein. Method  200  can be employed in many different embodiments or examples not specifically depicted or described herein. In some embodiments, the procedures, the processes, and/or the activities of method  200  can be performed in the order presented. In other embodiments, the procedures, the processes, and/or the activities of method  200  can be performed in any suitable order. In still other embodiments, one or more of the procedures, the processes, and/or the activities of method  200  can be combined or skipped. In some embodiments, method  200  can be performed by financial institution  130  ( FIG. 1 ). 
     Referring to  FIG. 2 , in some embodiments, method  200  can optionally include one or more preliminary blocks, such as a block  201  and a block  202 , described below. Specifically, method  200  can include block  201  of receiving, at a first financial institution from a mobile device, a preliminary request for account information. The first financial institution can be similar or identical to financial institution  130  ( FIG. 1 ). The mobile device can be similar or identical to mobile device  120  ( FIG. 1 ). 
     In several embodiments, method  200  additionally can include block  202  of sending, from the first financial institution to the mobile device, the account information. In some embodiments, the account include can include an account balance and an account status of a first account. The first account can be similar or identical to one or more of consumer accounts  131  ( FIG. 1 ). 
     In a number of embodiments, method  200  further can include a block  203  of receiving, at a first financial institution from a mobile device of a consumer, a first request to pay a merchant for a payment amount from a first account of the consumer maintained by the first financial institution. The consumer can be similar or identical to consumer  129  ( FIG. 1 ). The merchant can be similar or identical to merchant  119  ( FIG. 1 ). In many embodiments, the first request can include first information, which can include a merchant identifier, a transaction identifier, and/or the payment amount. In several embodiments, the first information can be sent to the first financial institution from a mobile application running on a mobile device used by the consumer at a store of the merchant to pay for one or more items to be purchased from the merchant by the consumer for the payment amount. The mobile application can be similar or identical to mobile application  123  ( FIG. 1 ). In some embodiments, the one or more items to be purchased can include at least one of one or more products or one or more services. In many embodiments, the merchant identifier can be associated with the merchant. In a number of embodiments, the mobile application can be associated with the first account. In some embodiments, the merchant identifier can uniquely correspond to a point-of-sale terminal at the store of the merchant. In various embodiments, the merchant identifier can be obtained by the mobile device from the point-of-sale terminal using a proximity-based wireless data communication protocol. 
     In many embodiments, method  200  additionally can include a block  204  of determining, at the first financial institution, second information. In many embodiments, the second information can include an account identifier of a second account of the merchant maintained by a second financial institution, at least partially based on the merchant identifier and third information obtained from a first system. The second account can be similar or identical to merchant account  151  ( FIG. 1 ). The second financial institution can be similar or identical to financial institution  150  ( FIG. 1 ). The first system can be similar or identical to transaction system  140  ( FIG. 1 ). In a number of embodiments, the account identifier can be or include an account number. In some embodiments, the first system can be in data communication with the first financial institution and the second financial institution. In many embodiments, the first system can be maintained by an entity that is different from the first financial institution and the second financial institution. In some embodiments, the second information further can include a name of the merchant and/or a location of the store of the merchant. 
     In some embodiments, block  204  of determining second information can include a block  205  of determining, at the first financial institution, the second information at least partially based on the merchant identifier and the third information. In a number of embodiments, the third information can be received by the first financial institution from the first system prior to receiving the first request to pay the merchant from the mobile device. For example, the third information can be stored at the first financial institution from a previous query to the first system. In many embodiments, the third information can include the account identifier of the second account. In some embodiments, the second information can include the third information. 
     In other embodiments, block  204  of determining second information can include a block  206  and a block  207 , described below. For example, block  204  can include block  206  of sending, from the first financial institution to the first system, a second request to determine the second information. In several embodiments, the second request can include the merchant identifier. 
     In these same other embodiments, block  204  can include block  207  of receiving, at the first financial institution from the first system, the third information. The third information can include the account identifier of the second account. In many embodiments, the second information can include the third information. 
     In some embodiments, method  200  can continue with a block  208  of authorizing, at the first financial institution, a payment from the first account to the second account. 
     In a number of embodiments, block  208  of authorizing the payment from the first account to the second account can include a block  209  of authenticating an identity of the consumer that used the mobile device to send the first request to pay the merchant from the first account. In some embodiments, block  209  of authenticating the identity of the consumer can include authenticating the identity of the consumer based at least in part on whether the mobile device used to send the first request has previously been used by the consumer in transaction involving the first financial institution, whether biometrics of the consumer using the mobile device match stored biometrics of the consumer, and/or whether at least one of an identity of the merchant, a location of the merchant, or the payment amount is consistent with historical patterns of behavior by the consumer. 
     In a number of embodiments, the first information further can include the one or more items to be purchased, and block  209  of authenticating the identity of the consumer further can include authenticating the identity of the consumer based at least in part on the one or more items to be purchased by the consumer for the payment amount from the merchant. 
     In a number of embodiments, block  209  of authenticating the identity of the consumer further can include adjusting a level of authentication at least partially based on the payment amount to be paid to the merchant, whether the mobile device used to send the first request has previously been used by the consumer in transaction involving the first financial institution, whether biometrics of the consumer using the mobile device match stored biometrics of the consumer, and/or whether at least one of an identity of the merchant, a location of the merchant, the payment amount, or the one or more items to be purchased is consistent with historical patterns of behavior by the consumer. 
     In many embodiments, block  208  of authorizing payment from the first account to the second account additionally can include a block  210  of determining a current status of the first account. For example, the first financial institution can determine whether the first account is open and in good status, or has a freeze or hold status. 
     In several embodiments, block  208  of authorizing payment from the first account to the second account additionally can include a block  211  of determining available funds of the first account. For example, the first financial institution can use the determination of the available funds of the first account to determine whether the payment amount can be covered by the available funds of the first account. 
     In a number of embodiments, method  200  can continue with a block  212  of sending, from the first financial institution to the first system, payment information regarding a payment to be made to the second account from the first account. In several embodiments, the payment information can be routed through the first system to the second financial institution such that the second financial institution, upon receiving the payment information, can notify the merchant in order to satisfy an expectation of the merchant for payment from the consumer. In some embodiments, the payment information can include the transaction identifier, the account identifier of the second account, and/or the payment amount. In a number of embodiments, the payment information can include the merchant identifier. 
     In some embodiments, the payment information further can include a settlement credit push of funds for the payment amount from the first account to the second account. In other embodiments, the payment information further can include an irrevocable promise to pay the payment amount from the first account to the second account. In several embodiments, the payment information further can include a set of personally identifiable information of the consumer. In a number of embodiments, the set of personally identifiable information can be at least partially based on privacy instructions sent by the consumer to the first financial institution. 
     Turning ahead in the drawings,  FIG. 3  illustrates a flow chart for a method  300 , according to an embodiment. In some embodiments, method  300  can be a method of facilitating secure payment transactions. Method  300  is merely exemplary and is not limited to the embodiments presented herein. Method  300  can be employed in many different embodiments or examples not specifically depicted or described herein. In some embodiments, the procedures, the processes, and/or the activities of method  300  can be performed in the order presented. In other embodiments, the procedures, the processes, and/or the activities of method  300  can be performed in any suitable order. In still other embodiments, one or more of the procedures, the processes, and/or the activities of method  300  can be combined or skipped. In some embodiments, method  300  can be performed by transaction system  140  ( FIG. 1 ). 
     Referring to  FIG. 3 , method  300  can include a block  301  of receiving, at a first system from a first entity, a request. The first system can be similar or identical to transaction system  140  ( FIG. 1 ). In some embodiments, the first entity can be a first financial institution. The first financial institution can be similar or identical to financial institution  130  ( FIG. 1 ). In other embodiments, the first entity can be a mobile device being used a consumer. In yet other embodiments, the first entity can be a mobile wallet provider in data communication with the mobile device being used by the consumer. In a number of embodiments, the request can include a merchant identifier. In several embodiments, the merchant identifier can be associated with a merchant. The merchant can be similar or identical to merchant  119  ( FIG. 1 ). In many embodiments, the first system can be in data communication with the first financial institution and a second financial institution. The second financial institution can be similar or identical to financial institution  150  ( FIG. 1 ). In various embodiments, the first system can be maintained by an entity that is different from the first financial institution and the second financial institution. In some embodiments, the first financial institution can maintain a first account of a consumer. The first account can be similar or identical to one or more of consumer accounts  131  ( FIG. 1 ). The consumer can be similar or identical to consumer  129  ( FIG. 1 ). In many embodiments, the first system can be in data communication with a merchant account database. The merchant account database can be similar or identical to merchant account database  141  ( FIG. 1 ). In a number of embodiments, the first system can include the merchant account database In some embodiments, the first system can include a transaction database. The transaction database can be similar or identical to transaction database  142  ( FIG. 1 ). In a number of embodiments, the merchant identifier can uniquely correspond to a point-of-sale terminal at the store of the merchant. In various embodiments, the merchant identifier can be obtained by the mobile device from the point-of-sale terminal using a proximity-based wireless data communication protocol. 
     In many embodiments, method  300  additionally can include a block  302  of determining, at the first system, using the merchant account database, first information. In several embodiments, the first information can include an account identifier of a second account of the merchant maintained by a second financial institution. The second account can be similar or identical to merchant account  151  ( FIG. 1 ). The second financial institution can be similar or identical to financial institution  150  ( FIG. 1 ). In some embodiments, the account identifier can be associated with the merchant identifier in the merchant account database. In a number of embodiments, the first information further can include a name of the merchant and/or a location of a store of the merchant. 
     In many embodiments, method  300  further can include a block  303  of sending the first information from the first system to the first financial institution. 
     In several embodiments, method  300  additionally can include a block  304  of receiving, at the first system from the first financial institution, payment information regarding a payment to be made to the second account from the first account to pay the merchant for one or more items to be purchased from the merchant by the consumer for the payment amount. In a number of embodiments, the consumer can use a mobile device at the store of the merchant to pay for the one or more items. The mobile device can be similar or identical to mobile device  120  ( FIG. 1 ). In some embodiments, the mobile device can be running a mobile application associated with the first account. The mobile application can be similar or identical to mobile application  123  ( FIG. 1 ). In many embodiments, the payment information can include a transaction identifier, the account identifier of the second account, and/or the payment amount. In a number of embodiments, the one or more items to be purchased can include at least one of one or more products or one or more services. 
     In a number of embodiments, method  300  optionally can include a block  305  of storing the payment information in the transaction database. 
     In many embodiments, method  300  can continue with a block  306  of sending, from the first system to the second financial institution, the payment information such that the second financial institution, upon receiving the payment information, notifies the merchant to satisfy an expectation of the merchant for payment from the consumer. 
     In some embodiments, the payment information further can include a settlement credit push of funds for the payment amount from the first account to the second account. In other embodiments, the payment information further can include an irrevocable promise to pay the payment amount from the first account to the second account. In several embodiments, the payment information further can include a set of personally identifiable information of the consumer. In a number of embodiments, the set of personally identifiable information can be at least partially based on privacy instructions sent by the consumer to the first financial institution. 
     Turning ahead in the drawings,  FIG. 4  illustrates a flow chart for a method  400 , according to an embodiment. In some embodiments, method  400  can be a method of facilitating secure payment transactions. Method  400  is merely exemplary and is not limited to the embodiments presented herein. Method  400  can be employed in many different embodiments or examples not specifically depicted or described herein. In some embodiments, the procedures, the processes, and/or the activities of method  400  can be performed in the order presented. In other embodiments, the procedures, the processes, and/or the activities of method  400  can be performed in any suitable order. In still other embodiments, one or more of the procedures, the processes, and/or the activities of method  400  can be combined or skipped. In some embodiments, method  400  can be performed by mobile device  120  ( FIG. 1 ). 
     Referring to  FIG. 4 , method  400  can include a block  401  of performing, at a mobile device, a preliminary identity authentication of a consumer using the mobile device. The mobile device can be similar or identical to mobile device  120  ( FIG. 1 ). The consumer can be similar or identical to consumer  129  ( FIG. 1 ). 
     In many embodiments, method  400  additionally can include a block  402  of receiving at the mobile device first information from a point-of-sale terminal. The point-of-sale terminal can be similar or identical to point-of-sale terminal  110  ( FIG. 1 ). In several embodiments, the first information can include a merchant identifier, a transaction identifier, and/or a payment amount. In some embodiments, the merchant identifier can uniquely correspond to the point-of-sale terminal at a store of a merchant. The merchant can be similar or identical to merchant  119  ( FIG. 1 ). In a number of embodiments, the mobile device can run a mobile application that is associated with a first account of the consumer using the mobile device. The mobile application can be similar or identical to mobile application  123  ( FIG. 1 ). The first account can be similar or identical to one or more of consumer accounts  131  ( FIG. 1 ). In several embodiments, the first account of the consumer can be maintained by a first financial institution. The first financial institution can be similar or identical to financial institution  130  ( FIG. 1 ). 
     In some embodiments, method  400  optionally can include various blocks before or after block  402  of receiving at the mobile device first information from a point-of-sale terminal. In various embodiments, method  400  can include a block  403  of sending, from the mobile device to the first financial institution, a preliminary request for account information. In several embodiments, the account information can include an account balance and an account status of the first account. 
     In a number of embodiments, method  400  further optionally can include, after block  403  of sending the preliminary request for account information, a block  404  of receiving, at the mobile device from the first financial institution, the account information. 
     In many embodiments, method  400  can continue with a block  405  of sending, from the mobile device to the first financial institution, a first request to pay the merchant for the payment amount from the first account for one or more items to be purchased from the merchant by the consumer. In a number of embodiments, the first request can include the first information, such that the first financial institution, upon receiving the first request, can determine second information including an account identifier of a second account of the merchant maintained by a second financial institution, at least partially based on the merchant identifier and third information obtained from a first system, and such that the first financial institution can send to the first system payment information regarding a payment to be made to the second account from the first account. The second account can be similar or identical to merchant account  151  ( FIG. 1 ). The second financial institution can be similar or identical to financial institution  150  ( FIG. 1 ). The first system can be similar or identical transaction system  140  ( FIG. 1 ). 
     In a number of embodiments, the payment information can be routed through the first system to the second financial institution such that the second financial institution, upon receiving the payment information, can notify the merchant to satisfy an expectation of the merchant for payment from the consumer. In several embodiments, the first system can be in data communication with the first financial institution and the second financial institution. In various embodiments, the first system can be maintained by an entity that is different from the first financial institution and the second financial institution. In a number of embodiments, the payment information can include the transaction identifier, the account identifier of the second account, and the payment amount. In some embodiments, the payment information further can include one of: (a) a settlement credit push of funds for the payment amount from the first account to the second account, or (b) an irrevocable promise to pay the payment amount from the first account to the second account. 
     In some embodiments, method  400  optionally can include additional blocks after sending the first request to pay the merchant and before the payment information is sent to the first system from the first financial institution. For example, in a number of embodiments, method  400  optionally can include a block  406  of receiving, at the mobile device from the first financial institution, an additional authentication request to perform an additional identity authentication of the consumer using the mobile device. 
     In various embodiments, method  400  further can include a block  407  of performing, at the mobile device, the additional identity authentication of the consumer using the mobile device. In many embodiments, block  407  can include performing the additional authentication of the consumer based at least in part on determining biometrics of the consumer using the mobile device and/or requesting the consumer to enter additional information in the mobile device. 
     In several embodiments, method  400  additionally can include a block  408  of sending, from the mobile device to the first financial institution, a response to the additional authentication request. 
     Turning ahead in the drawings,  FIG. 5  illustrates a flow chart for a method  500 , according to an embodiment. In some embodiments, method  500  can be a method of facilitating secure payment transactions. Method  500  is merely exemplary and is not limited to the embodiments presented herein. Method  500  can be employed in many different embodiments or examples not specifically depicted or described herein. In some embodiments, the procedures, the processes, and/or the activities of method  500  can be performed in the order presented. In other embodiments, the procedures, the processes, and/or the activities of method  500  can be performed in any suitable order. In still other embodiments, one or more of the procedures, the processes, and/or the activities of method  500  can be combined or skipped. In some embodiments, method  500  can be performed by point-of-sale terminal  110  ( FIG. 1 ). 
     Referring to  FIG. 5 , method  500  can include a block  501  of determining, at a point-of-sale terminal at a store of a merchant, a payment amount for one or more items to be purchased from the merchant by a consumer. The point-of-sale terminal can be similar or identical to point-of-sale terminal  110  ( FIG. 1 ). The merchant can be similar or identical to merchant  119  ( FIG. 1 ). The consumer can be similar of identical to consumer  129  ( FIG. 1 ). 
     In several embodiments, method  500  additionally can include a block  502  of sending first information from the point-of-sale terminal to a mobile device used by the consumer. The mobile device can be similar or identical to mobile device  120  ( FIG. 1 ). In a number of embodiments, the first information can be sent from the point-of-sale terminal to the mobile device using a proximity-based wireless data protocol. In several embodiments, the first information can include a merchant identifier, a transaction identifier, and/or the payment amount. In a number of embodiments, the merchant identifier can uniquely correspond to the point-of-sale terminal at the store of the merchant. In various embodiments, the mobile device can run a mobile application that is associated with a first account of the consumer using the mobile device. The mobile application can be similar or identical to mobile application  123  ( FIG. 1 ). The first account can be similar or identical to one or more of consumer accounts  131  ( FIG. 1 ). In a number of embodiments, the first account of the consumer can be maintained by a first financial institution. The first financial institution can be similar or identical to financial institution  130  ( FIG. 1 ). In several embodiments, the mobile device, upon receiving the first information, can send a first request to pay the merchant for the payment amount from the first account. In a number of embodiments, the first request can include the first information, such that the first financial institution, upon receiving the first request, can determine second information including an account identifier of a second account of the merchant maintained by a second financial institution, at least partially based on the merchant identifier and third information obtained from a first system, and such that the first financial institution sends to the first system payment information regarding a payment to be made to the second account from the first account. The second account can be similar or identical to merchant account  151  ( FIG. 1 ). The second financial institution can be similar or identical to financial institution  150  ( FIG. 1 ). The first system can be similar or identical to transaction system  140  ( FIG. 1 ). 
     In some embodiments, the payment information can be routed through the first system to the second financial institution. In various embodiments, the first system can be in data communication with the first financial institution and the second financial institution. In many embodiments, the first system can be maintained by an entity that is different from the first financial institution and the second financial institution. In several embodiments, the payment information can include the transaction identifier, the account identifier of the second account, and/or the payment amount. in some embodiments, the payment information further can include one of: (a) a settlement credit push of funds for the payment amount from the first account to the second account, or (b) an irrevocable promise to pay the payment amount from the first account to the second account. 
     In various embodiments, method  500  optionally can include a block  503  of receiving at the point-of-sale terminal from the mobile device, information about the consumer. In some embodiments, block  503  can be performed before or after block  501  of determining the payment amount for the one or more items to be purchased from the merchant by the consumer, before or after block  502  of sending the first information from the point-of-sale terminal to the mobile device used by the consumer, or before or after block  504 , described below. 
     In many embodiments, method  500  can continue with a block  504  of receiving, at the point-of-sale terminal from the second financial institution, a notification to satisfy an expectation of the merchant for payment from the consumer. 
     Turning ahead in the drawings,  FIG. 6  illustrates a flow chart for a method  600 , according to an embodiment. In some embodiments, method  600  can be a method of facilitating secure payment transactions. Method  600  is merely exemplary and is not limited to the embodiments presented herein. Method  600  can be employed in many different embodiments or examples not specifically depicted or described herein. In some embodiments, the procedures, the processes, and/or the activities of method  600  can be performed in the order presented. In other embodiments, the procedures, the processes, and/or the activities of method  600  can be performed in any suitable order. In still other embodiments, one or more of the procedures, the processes, and/or the activities of method  600  can be combined or skipped. In some embodiments, method  600  can be performed by financial institution  150  ( FIG. 1 ). 
     Referring to  FIG. 6 , method  600  can include a block  601  of receiving, at a second financial institution from a first system, payment information regarding a payment to be made to a second account of a merchant maintained by the second financial institution from a first account of a consumer maintained by a first financial institution to pay the merchant for one or more items to be purchased from the merchant by the consumer for the payment amount. The second financial institution can be similar or identical to financial institution  150  ( FIG. 1 ). The first system can be similar or identical to transaction system  140  ( FIG. 1 ). The second account can be similar or identical to merchant account  151  ( FIG. 1 ). The first account can be similar or identical to one or more of consumer accounts  131  ( FIG. 1 ). The consumer can be similar or identical to consumer  129  ( FIG. 1 ). The first financial institution can be similar or identical to financial institution  130  ( FIG. 1 ). 
     In a number of embodiments, the payment information can be sent from the first financial institution to the first system and routed through the first system to the second financial institution. In several embodiments, the first system can be in data communication with the first financial institution and the second financial institution. In various embodiments, the first system can be maintained by an entity that is different from the first financial institution and the second financial institution. In many embodiments, the consumer can use a mobile device at a store of the merchant to pay for the one or more items. The mobile device can be similar or identical to mobile device  120  ( FIG. 1 ). In a number of embodiments, the mobile device can run a mobile application associated with the first account. The mobile application can be similar or identical to mobile application  123  ( FIG. 1 ). In several embodiments, the payment information can include a transaction identifier, an account identifier of the second account, and/or the payment amount. In a number of embodiments, the first financial institution can determine the account identifier of the second account based on a merchant identifier and based on third information obtained from the first system. In several embodiments, the merchant identifier can uniquely correspond to a point-of-sale terminal at the store of a merchant. The point-of-sale terminal can be similar or identical to point-of-sale terminal  110  ( FIG. 1 ). 
     In a number of embodiments, the mobile device can send a request to pay the merchant for the payment amount from the first account. In many embodiments, the request can include first information including the merchant identifier, a transaction identifier, and/or the payment amount. In several embodiments, the payment information further can include one of: (a) a settlement credit push of funds for the payment amount from the first account to the second account, or (b) an irrevocable promise to pay the payment amount from the first account to the second account. 
     In several embodiments, method  600  optionally can include a block  602  of crediting the second account with the payment amount. For example, after the second financial institution has received the payment information, the second account can be credited with the payment amount. 
     In many embodiments, method  600  can continue with a block  603  of sending, from the second financial institution to the point-of-sale terminal, a notification to satisfy an expectation of the merchant for payment from the consumer. In some embodiments, block  603  can include notifying the merchant that funds for the payment amount are immediately available in the second account. 
     Jumping ahead in the drawings,  FIG. 9  illustrates a flow chart for a method  900 , according to an embodiment. In some embodiments, method  900  can be a method of facilitating secure payment transactions. Method  900  is merely exemplary and is not limited to the embodiments presented herein. Method  900  can be employed in many different embodiments or examples not specifically depicted or described herein. In some embodiments, the procedures, the processes, and/or the activities of method  900  can be performed in the order presented. In other embodiments, the procedures, the processes, and/or the activities of method  900  can be performed in any suitable order. In still other embodiments, one or more of the procedures, the processes, and/or the activities of method  900  can be combined or skipped. In some embodiments, method  900  can be performed by point-of-sale terminal  110  ( FIG. 1 ). In some embodiments, method  900  and other blocks in method  900  can include using a distributed network including distributed memory architecture to perform the associated activity. This distributed architecture can reduce the impact on the network and system resources to reduce congestion in bottlenecks while still allowing data to be accessible from a central location. 
     Referring to  FIG. 9 , method  900  can include a block  901  of determining, at a point-of-sale terminal at a store of a merchant, a payment amount for one or more items to be purchased from the merchant by a consumer in a transaction. The point-of-sale terminal can be similar or identical to point-of-sale terminal  110  ( FIG. 1 ). The merchant can be similar or identical to merchant  119  ( FIG. 1 ). The consumer can be similar or identical to consumer  129  ( FIG. 1 ). 
     In several embodiments, method  900  also can include a block  902  of generating a transaction code including a merchant public identifier, the payment amount, a transaction identifier for the transaction, and a digital signature. In many embodiments, the transaction code can be similar or identical to the merchant security transaction code described above. In some embodiments, the transaction code can further include one or more SKUs for the one or more items to be purchased in the transaction. In some embodiments, the digital signature can be similar or identical to the digital signature described above. In many embodiments, the merchant public identifier can be similar to the merchant identifier described above. For example, in many embodiments, the merchant identifier can be setup and/or registered through a transaction system, such as transaction system  140  ( FIG. 1 ). 
     In some embodiments, block  902  of generating a transaction code including a merchant public identifier can include point-of-sale terminal  110  ( FIG. 1 ) cryptographically signing the digital signature for the transaction code. In other embodiments, block  902  of generating a transaction code including a merchant public identifier can include point-of-sale terminal  110  ( FIG. 1 ) calling the transaction system, such as transaction system  140  ( FIG. 1 ), to generate the transaction code. 
     In a number of embodiments, method  900  additionally can include a block  903  of providing the transaction code to a mobile device being used by the consumer, such that the mobile device verifies the digital signature and sends a request to pay the merchant for the payment amount from a first account of the consumer maintained by a first financial institution, such that the first financial institution, upon receiving the request to pay, retrieves from a transaction system an account identifier of a second account of the merchant maintained by a second financial institution based on the merchant public identifier, and such that the first financial institution sends to the transaction system payment information regarding a payment to be made to the second account from the first account. The mobile device can be similar or identical to mobile device  120  ( FIG. 1 ). The first account can be similar or identical to one or more of consumer accounts  131  ( FIG. 1 ). The first financial institution can be similar or identical to financial institution  130  ( FIG. 1 ). The second account can be similar or identical to merchant account  151  ( FIG. 1 ). The second financial institution can be similar or identical to financial institution  150  ( FIG. 1 ). The transaction system can be similar or identical to transaction system  140  ( FIG. 1 ). In many embodiments, the transaction system can be maintained by an entity that is different from the merchant, the first financial institution, and the second financial institution. In some embodiments, the payment information can be routed through the transaction system to the second financial institution. In many embodiments, the payment information can include the transaction identifier, the account identifier of the second account, the payment amount, and/or other suitable information. 
     In some embodiments, the payment information can include one of: (a) a settlement credit push of funds for the payment amount from the first account to the second account, or (b) an irrevocable promise to pay the payment amount from the first account to the second account. In many embodiments, the mobile device can send the request to pay after receiving from the consumer an approval for the transaction. For example, the consumer can authorize the transaction, after which the request to pay can be sent from the mobile device. 
     In many embodiments, block  903  of providing the transaction code to a mobile device being used by the consumer can include displaying the transaction code as a matrix barcode on a screen of the point-of-sale terminal. For example, the transaction code can be displayed as a QR code on a screen of the point-of-sale terminal, which can be scanned using a camera of the mobile device. In other embodiments, block  903  of providing the transaction code to a mobile device being used by the consumer can include transmitting the transaction code from the point-of-sale terminal to the mobile device using a proximity-based wireless data communication protocol. In yet other embodiments, the point-of-sale terminal can display the transaction code such that it can be manually input into the mobile device. 
     In certain embodiments, the first financial institution does not have access to a second account number for the second account for the transaction, and the second financial institution does not have access to a first account number for the first account for the transaction. In other embodiments, the first financial institution can have access to a second account number for the second account for the transaction, and/or the second financial institution can have access to a first account number for the first account for the transaction. 
     In several embodiments, method  900  further can include a block  904  of receiving, at the point-of-sale terminal, a notification of payment for the transaction in real-time while the consumer remains at the store of the merchant. In many embodiments, the notification of the payment can be received by the merchant and/or at the point-of-sale terminal from the transaction system. In other embodiments, the notification of the payment can be received by the merchant and/or at the point-of-sale terminal from the second financial institution system. 
     Proceeding to the next drawing,  FIG. 10  illustrates a flow chart for a method  1000 , according to an embodiment. In some embodiments, method  1000  can be a method of facilitating secure payment transactions. Method  1000  is merely exemplary and is not limited to the embodiments presented herein. Method  1000  can be employed in many different embodiments or examples not specifically depicted or described herein. In some embodiments, the procedures, the processes, and/or the activities of method  1000  can be performed in the order presented. In other embodiments, the procedures, the processes, and/or the activities of method  1000  can be performed in any suitable order. In still other embodiments, one or more of the procedures, the processes, and/or the activities of method  1000  can be combined or skipped. In some embodiments, method  1000  can be performed by mobile device  120  ( FIG. 1 ) and/or mobile application  123  ( FIG. 1 ). 
     Referring to  FIG. 10 , method  1000  can include a block  1001  of receiving, at a mobile device being used by a consumer, a transaction code from a point-of-sale terminal at a store of a merchant. The mobile device can be similar or identical to mobile device  120  ( FIG. 1 ). The consumer can be similar or identical to consumer  129  ( FIG. 1 ). In many embodiments, the transaction code can be similar or identical to the merchant security transaction code described above. The point-of-sale terminal can be similar or identical to point-of-sale terminal  110  ( FIG. 1 ). The merchant can be similar or identical to merchant  119  ( FIG. 1 ). 
     In many embodiments, the transaction code can include a merchant public identifier being associated with the merchant, a payment amount for one or more items to be purchased from the merchant by the consumer in a transaction, a transaction identifier for the transaction, and a digital signature. In various embodiments, the transaction code further can include one or more SKUs for the one or more items to be purchased in the transaction. In many embodiments, the merchant public identifier can be similar to the merchant identifier described above. For example, in many embodiments, the merchant identifier can be setup and/or registered through a transaction system, such as transaction system  140  ( FIG. 1 ). In some embodiments, the digital signature can be similar or identical to the digital signature described above. In some embodiments, the digital signature of the transaction code is cryptographically signed by the point-of-sale terminal. In other embodiments, the transaction system can be called by the point-of-sale terminal to generate the transaction code. 
     In some embodiments, block  1001  of receiving, at a mobile device being used by a consumer, a transaction code from a point-of-sale terminal at a store of a merchant can include using a camera of the mobile device to scan the transaction code as a matrix barcode from a screen of the point-of-sale terminal. For example, the transaction code can be displayed as a QR code on a screen of the point-of-sale terminal, which can be scanned using a camera of the mobile device. In other embodiments, block  1001  of receiving, at a mobile device being used by a consumer, a transaction code from a point-of-sale terminal at a store of a merchant can include receiving the transaction code from the point-of-sale terminal using a proximity-based wireless data communication protocol. In yet other embodiments, the mobile device can receive the transaction code through manual input. 
     In several embodiments, method  1000  also can include a block  1002  of verifying the digital signature for the transaction code. For example, the digital signature can be verified using a public-key signature verifying algorithm, as described above, or another suitable verification algorithm. 
     In a number of embodiments, method  1000  optionally can include a block  1003  of receiving an approval for the transaction from the consumer through a user interface on the mobile device. For example, the consumer can authorize the transaction, as described above. The user interface can be similar to user interface display  1700  ( FIG. 17 ), as described below in further detail. 
     In several embodiments, method  1000  further can include a block  1004  of sending, from the mobile device, a request to pay the merchant for the payment amount from a first account of the consumer maintained by a first financial institution, such that the first financial institution, upon receiving the request to pay, retrieves from a transaction system an account identifier of a second account of the merchant maintained by a second financial institution based on the merchant public identifier, such that the first financial institution sends to the transaction system payment information regarding a payment to be made to the second account from the first account, such that the payment information is routed through the transaction system to the second financial institution, and such that the point-of-sale terminal receives a notification of payment for the transaction in real-time while the consumer remains at the store of the merchant. In some embodiments, the payment information including the transaction identifier, the account identifier of the second account, the payment amount, and/or other suitable information. 
     The first account can be similar or identical to one or more of consumer accounts  131  ( FIG. 1 ). The first financial institution can be similar or identical to financial institution  130  ( FIG. 1 ). The transaction system can be similar or identical to transaction system  140  ( FIG. 1 ). In many embodiments, the transaction system can be maintained by an entity that is different from the merchant, the first financial institution, and the second financial institution. The second account can be similar or identical to merchant account  151  ( FIG. 1 ). The second financial institution can be similar or identical to financial institution  150  ( FIG. 1 ). 
     In some embodiments, the payment information can include one of: (a) a settlement credit push of funds for the payment amount from the first account to the second account, or (b) an irrevocable promise to pay the payment amount from the first account to the second account. In many embodiments, the notification of the payment can be received at the point-of-sale terminal from the transaction system. In other embodiments, the notification of the payment can be received at the point-of-sale terminal from the second financial institution system. 
     In certain embodiments, the first financial institution does not have access to a second account number for the second account for the transaction, and the second financial institution does not have access to a first account number for the first account for the transaction. In other embodiments, the first financial institution can have access to a second account number for the second account for the transaction, and/or the second financial institution can have access to a first account number for the first account for the transaction. 
     Turning ahead in the drawings,  FIG. 11  illustrates a flow chart for a method  1100 , according to an embodiment. In some embodiments, method  1100  can be a method of facilitating secure payment transactions. Method  1100  is merely exemplary and is not limited to the embodiments presented herein. Method  1100  can be employed in many different embodiments or examples not specifically depicted or described herein. In some embodiments, the procedures, the processes, and/or the activities of method  1100  can be performed in the order presented. In other embodiments, the procedures, the processes, and/or the activities of method  1100  can be performed in any suitable order. In still other embodiments, one or more of the procedures, the processes, and/or the activities of method  1100  can be combined or skipped. In some embodiments, method  1100  can be performed by financial institution  130  ( FIG. 1 ). In some embodiments, method  1100  and other blocks in method  1100  can include using a distributed network including distributed memory architecture to perform the associated activity. This distributed architecture can reduce the impact on the network and system resources to reduce congestion in bottlenecks while still allowing data to be accessible from a central location. 
     Referring to  FIG. 11 , method  1100  can include a block  1101  of receiving, at a first financial institution from a mobile device being used by a consumer, a request to pay a merchant for a payment amount from a first account of the consumer maintained by the first financial institution. The first financial institution can be similar or identical to financial institution  130  ( FIG. 1 ). The mobile device can be similar or identical to mobile device  120  ( FIG. 1 ). The consumer can be similar or identical to consumer  129  ( FIG. 1 ). The merchant can be similar or identical to merchant  119  ( FIG. 1 ). In many embodiments, the first account can be similar or identical to one or more of consumer accounts  131  ( FIG. 1 ). 
     In some embodiments, the request to pay can include information including a merchant public identifier, a payment amount for one or more items to be purchased from the merchant by the consumer in a transaction, and a transaction identifier for the transaction. In many embodiments, the merchant public identifier can be similar to the merchant identifier described above. For example, in many embodiments, the merchant identifier can be setup and/or registered through a transaction system, such as transaction system  140  ( FIG. 1 ). 
     In various embodiments, the mobile device can be used by the consumer at a store of the merchant to pay for the transaction. In a number of embodiments, the information can be received by the mobile device from a point-of-sale terminal at the store of the merchant as part of a transaction code. The point-of-sale terminal can be similar or identical to point-of-sale terminal  110  ( FIG. 1 ). In many embodiments, the transaction code can be similar or identical to the merchant security transaction code described above. In some embodiments, the transaction code can further include one or more SKUs for the one or more items to be purchased in the transaction. In several embodiments, the transaction code can be verified by the mobile device using a digital signature of the transaction code. In some embodiments, the digital signature can be similar or identical to the digital signature described above. 
     In many embodiments, the mobile device can receive the transaction code by using a camera on the mobile device to scan the transaction code as a matrix barcode from a screen of the point-of-sale terminal. For example, the transaction code can be displayed as a QR code on a screen of the point-of-sale terminal, which can be scanned using a camera of the mobile device. In other embodiments, the mobile device can receive the transaction code using a proximity-based wireless data communication protocol. In yet other embodiments, the mobile device can receive the transaction code through manual input. In some embodiments, the digital signature of the transaction code can be cryptographically signed by the point-of-sale terminal. In other embodiments, the transaction system can be called by the point-of-sale terminal to generate the transaction code. 
     In a number of embodiments, the request to pay can be received at the first financial institution after the mobile device receives from the consumer an approval for the transaction. For example, the consumer can authorize the transaction, as described above. 
     In several embodiments, method  1100  also can include a block  1102  of retrieving, at the first financial institution from a transaction system, an account identifier for a second account of the merchant maintained by a second financial institution based on the merchant public identifier. The transaction system can be similar or identical to transaction system  140  ( FIG. 1 ). In some embodiments, the transaction system can be maintained by an entity that is different from the merchant, the first financial institution, and the second financial institution. The second account can be similar or identical to merchant account  151  ( FIG. 1 ). The second financial institution can be similar or identical to financial institution  150  ( FIG. 1 ). 
     In a number of embodiments, method  1100  additionally can include a block  1103  of sending, from the first financial institution to the transaction system, payment information regarding a payment to be made to the second account from the first account, such that the payment information is routed through the transaction system to the second financial institution, and such that the point-of-sale terminal receives a notification of payment for the transaction in real-time while the consumer remains at the store of the merchant. In many embodiments, the payment information can include the transaction identifier, the account identifier of the second account, the payment amount, and/or other suitable information. In several embodiments, the payment information further can include one of: (a) a settlement credit push of funds for the payment amount from the first account to the second account, or (b) an irrevocable promise to pay the payment amount from the first account to the second account. In some embodiments, the notification of the payment can be received at the point-of-sale terminal from the transaction system. In other embodiments, the notification of the payment can be received at the point-of-sale terminal from the second financial institution system. 
     In certain embodiments, the first financial institution does not have access to a second account number for the second account for the transaction, and the second financial institution does not have access to a first account number for the first account for the transaction. In other embodiments, the first financial institution can have access to a second account number for the second account for the transaction, and/or the second financial institution can have access to a first account number for the first account for the transaction. 
     Proceeding to the next drawing,  FIG. 12  illustrates a flow chart for a method  1200 , according to an embodiment. In some embodiments, method  1200  can be a method of facilitating secure payment transactions. Method  1200  is merely exemplary and is not limited to the embodiments presented herein. Method  1200  can be employed in many different embodiments or examples not specifically depicted or described herein. In some embodiments, the procedures, the processes, and/or the activities of method  1200  can be performed in the order presented. In other embodiments, the procedures, the processes, and/or the activities of method  1200  can be performed in any suitable order. In still other embodiments, one or more of the procedures, the processes, and/or the activities of method  1200  can be combined or skipped. In some embodiments, method  1200  can be performed by transaction system  140  ( FIG. 1 ). In some embodiments, method  1200  and other blocks in method  1200  can include using a distributed network including distributed memory architecture to perform the associated activity. This distributed architecture can reduce the impact on the network and system resources to reduce congestion in bottlenecks while still allowing data to be accessible from a central location. 
     Referring to  FIG. 12 , method  1200  can include a block  1201  of receiving, at a transaction system from a first entity, a request including a merchant public identifier associated with a merchant. The transaction system can be similar or identical to transaction system  140  ( FIG. 1 ). In many embodiments, the merchant public identifier can be similar to the merchant identifier described above. For example, in many embodiments, the merchant identifier can be setup and/or registered through the transaction system. The merchant can be similar or identical to merchant  119  ( FIG. 1 ). In some embodiments, the first entity can be at least one of the first financial institution, a mobile device being used by a consumer, or a mobile wallet provider in data communication with the mobile device being used by the consumer. For example, the first financial institution can be similar or identical to financial institution  130  ( FIG. 1 ), the mobile device can be similar or identical to mobile device  120  ( FIG. 1 ), the consumer can be similar or identical to consumer  129  ( FIG. 1 ), and/or the mobile wallet provider can be similar or identical to mobile application  123  ( FIG. 1 ). 
     In some embodiments, the transaction system can be in data communication with a first financial institution that maintains a first account of a consumer and a second financial institution that maintains a second account of the merchant. The first financial institution can be similar or identical to financial institution  130  ( FIG. 1 ). The first account can be similar or identical to one or more of consumer accounts  131  ( FIG. 1 ). The consumer can be similar or identical to consumer  129  ( FIG. 1 ). The second financial institution can be similar or identical to financial institution  150  ( FIG. 1 ). The second account can be similar or identical to merchant account  151  ( FIG. 1 ). In many embodiments, the transaction system can be maintained by an entity that is different from the merchant, the first financial institution, and the second financial institution. 
     In several embodiments, the consumer can use a mobile device at a store of the merchant to pay for one or more items in a transaction. The mobile device can be similar or identical to mobile device  120  ( FIG. 1 ). In some embodiments, the mobile device can receive a transaction code from a point-of-sale terminal at the store. The point-of-sale terminal can be similar or identical to point-of-sale terminal  110  ( FIG. 1 ). In many embodiments, the transaction code can include a transaction identifier, a payment amount for the transaction, the merchant public identifier, and a digital signature. In many embodiments, the transaction code can be similar or identical to the merchant security transaction code described above. In some embodiments, the transaction code can further include one or more SKUs for the one or more items to be purchased in the transaction. In some embodiments, the digital signature can be similar or identical to the digital signature described above. In some embodiments, the digital certificate of the transaction code can be cryptographically signed. In many embodiments, the transaction system can be called by the point-of-sale terminal to generate the transaction code before the transaction system receives the request. In a number of embodiments, the transaction code can be verified by the mobile device using a digital signature of the transaction code. 
     In some embodiments, the mobile device can receive the transaction code by using a camera on the mobile device to scan the transaction code as a matrix barcode from a screen of the point-of-sale terminal. For example, the transaction code can be displayed as a QR code on a screen of the point-of-sale terminal, which can be scanned using a camera of the mobile device. In other embodiments, the mobile device can receive the transaction code using a proximity-based wireless data communication protocol. In yet other embodiments, the mobile device can receive the transaction code through manual input. 
     In several embodiments, method  1200  also can include a block  1202  of determining, at the transaction system, an account identifier of the second account based on the merchant public identifier using a merchant account database. The merchant account database can be similar or identical to merchant account database  141  ( FIG. 1 ). 
     In a number of embodiments, method  1200  additionally can include a block  1203  of sending the account identifier to the first financial institution. 
     In several embodiments, method  1200  further can include a block  1204  of receiving, at the transaction system from the first financial institution, payment information regarding a payment to be made to the second account from the first account. In some embodiments, the payment information can include the account identifier of the second account, the payment amount, the transaction identifier, and/or other suitable information. In many embodiments, the payment information further can include one of: (a) a settlement credit push of funds for the payment amount from the first account to the second account, or (b) an irrevocable promise to pay the payment amount from the first account to the second account. 
     In a number of embodiments, method  1200  additionally can include a block  1205  of sending, from the transaction system to the second financial institution, the payment information, such that the point-of-sale terminal receives a notification of payment for the transaction in real-time while the consumer remains at the store of the merchant. In many embodiments, the notification of the payment can be received at the point-of-sale terminal from the transaction system. In other embodiments, the notification of the payment can be received at the point-of-sale terminal from the second financial institution system. 
     In certain embodiments, the first financial institution does not have access to a second account number for the second account for the transaction, and the second financial institution does not have access to a first account number for the first account for the transaction. In other embodiments, the first financial institution can have access to a second account number for the second account for the transaction, and/or the second financial institution can have access to a first account number for the first account for the transaction. 
     Turning ahead in the drawings,  FIG. 13  illustrates a flow chart for a method  1300 , according to an embodiment. In some embodiments, method  1300  can be a method of facilitating secure payment transactions. Method  1300  is merely exemplary and is not limited to the embodiments presented herein. Method  1300  can be employed in many different embodiments or examples not specifically depicted or described herein. In some embodiments, the procedures, the processes, and/or the activities of method  1300  can be performed in the order presented. In other embodiments, the procedures, the processes, and/or the activities of method  1300  can be performed in any suitable order. In still other embodiments, one or more of the procedures, the processes, and/or the activities of method  1300  can be combined or skipped. In some embodiments, method  1300  can be performed by mobile device  120  ( FIG. 1 ) and/or mobile application  123  ( FIG. 1 ). 
     Referring to  FIG. 13 , method  1300  can include a block  1301  of performing, at a mobile device being used by a consumer, an identity authentication of the consumer. The mobile device can be similar or identical to mobile device  120  ( FIG. 1 ). The consumer can be similar or identical to consumer  129  ( FIG. 1 ). 
     In several embodiments, method  1300  also can include a block  1302  of receiving, at the mobile device, first information from a point-of-sale terminal at a store of a merchant. The point-of-sale terminal can be similar or identical to point-of-sale terminal  110  ( FIG. 1 ). The merchant can be similar or identical to merchant  119  ( FIG. 1 ). In some embodiments, the first information can include a merchant identifier, a transaction identifier, a payment amount, and/or other suitable information. In many embodiments, the merchant identifier can be associated with the merchant. In some embodiments, the payment amount can be for one or more items to be purchased from the merchant by the consumer in a transaction. The transaction identifier can be associated with the transaction. 
     In a number of embodiments, method  1300  additionally can include a block  1303  of sending, from the mobile device, a request to pay the merchant for the payment amount from one or more first accounts of the consumer maintained by a first financial institution, such that the first financial institution, upon receiving the request to pay, retrieves from a transaction system an account identifier of a second account of the merchant maintained by a second financial institution based on the merchant identifier, such that the first financial institution sends to the transaction system payment information regarding a payment to be made to the second account from the one or more first accounts, such that the payment information is routed through the transaction system to the second financial institution, and such that the point-of-sale terminal receives a notification of payment for the transaction in real-time while the consumer remains at the store of the merchant. The one or more first accounts can be similar or identical to one or more of consumer accounts  131  ( FIG. 1 ). In several embodiments, the one or more first accounts can include at least one non-demand deposit account. The first financial institution can be similar or identical to financial institution  130  ( FIG. 1 ). The transaction system can be similar or identical to transaction system  140  ( FIG. 1 ). In some embodiments, the transaction system can be maintained by an entity that is different from the merchant, the first financial institution, and the second financial institution. The second account can be similar or identical to merchant account  151  ( FIG. 1 ). The second financial institution can be similar or identical to financial institution  150  ( FIG. 1 ). 
     In several embodiments, the payment information can include the transaction identifier, the account identifier of the second account, the payment amount, and/or other suitable information. In some embodiments, the payment information further can include one of: (a) one or more settlement credit pushes of funds that collectively total the payment amount from the one or more first accounts to the second account, or (b) one or more irrevocable promises to pay that collectively total the payment amount from the one or more first accounts to the second account. In many embodiments, the mobile device can send the request to pay after receiving from the consumer an approval for the transaction. For example, the consumer can authorize the transaction, after which the request to pay can be sent from the mobile device, such as shown in user interface displays  1700  ( FIG. 17 ), as shown described below in further detail. 
     In many embodiments, the one or more first accounts can include the loan account, and in some embodiments, the loan account can be created after receiving the first information from the point-of-sale terminal. In several embodiments, the loan account can be used to fund at least a first portion of the payment amount of the transaction, and in various embodiments, a second portion of the payment amount can be funded from a demand deposit account of the consumer maintained at the first financial institution. 
     In certain embodiments, the first financial institution does not have access to a second account number for the second account for the transaction, and the second financial institution does not have access to a first account number for the first account for the transaction. In other embodiments, the first financial institution can have access to a second account number for the second account for the transaction, and/or the second financial institution can have access to a first account number for the first account for the transaction. 
     In many embodiments, method  1300  can include one or more optional blocks  1304 - 1308 , described below. In some embodiments, one or more of blocks  1304 - 1308  can be performed before block  1303 , and in some embodiments, can be performed before block  1302 . In the same or other embodiments, one or more of block  1304 - 1308  can be performed after block  1303 . 
     In several embodiments, method  1300  optionally can include block  1304  of receiving, from the first financial institution, an account balance of a demand deposit account of the consumer maintained by the first financial institution. 
     In a number of embodiments, method  1300  optionally can include block  1305  of displaying the account balance of the demand deposit account to the consumer on a user interface of the mobile device. The user interface can be similar to user interface display  1700  ( FIG. 17 ), as described below in further detail. 
     In several embodiments, method  1300  optionally can include block  1306  of determining that the account balance of the demand deposit account is less than the payment amount of the transaction. In some embodiments, the determining of block  1306  can involve a comparison in the mobile device of the payment account against the account balance. In other embodiments, another system, such as the first financial institution, can perform the comparison of the payment account against the account balance, and the determining of block  1306  can involve receiving, from the other system, such as from the first financial institution, information about, or based on, the results of the comparison. 
     In a number of embodiments, method  1300  optionally can include block  1307  of presenting to the consumer an option on a user interface of the mobile device to at least partially fund the transaction using the at least one non-demand deposit account. The user interface can be similar to user interface display  1800  ( FIG. 18 ), user interface display  1900  ( FIG. 19 ), and/or user interface display  2000  ( FIG. 20 ), as described below in further detail. 
     In several embodiments, method  1300  optionally can include block  1308  of receiving from the consumer through the user interface a selection to at least partially fund the payment amount of the transaction using the at least one non-demand deposit account. The user interface can be similar to user interface display  1800  ( FIG. 18 ), user interface display  1900  ( FIG. 19 ), and/or user interface display  2000  ( FIG. 20 ), as described below in further detail. In some embodiments, the one or more first accounts further can include the demand deposit account. In many embodiments, a first portion of the payment amount of the transaction can be funded from the demand deposit account, and in some embodiments, a second portion of the payment amount of the transaction can be funded from the at least one non-demand deposit account. In other embodiments, the demand deposit account can be devoid of being used to fund the payment amount of the transaction, and the payment amount of the transaction can be funded wholly from the at least one non-demand deposit account. 
     Turning ahead in the drawings,  FIG. 14  illustrates a flow chart for a method  1400 , according to an embodiment. In some embodiments, method  1400  can be a method of facilitating secure payment transactions. Method  1400  is merely exemplary and is not limited to the embodiments presented herein. Method  1400  can be employed in many different embodiments or examples not specifically depicted or described herein. In some embodiments, the procedures, the processes, and/or the activities of method  1400  can be performed in the order presented. In other embodiments, the procedures, the processes, and/or the activities of method  1400  can be performed in any suitable order. In still other embodiments, one or more of the procedures, the processes, and/or the activities of method  1400  can be combined or skipped. In some embodiments, method  1400  can be performed by financial institution  130  ( FIG. 1 ). In some embodiments, method  1400  and other blocks in method  1400  can include using a distributed network including distributed memory architecture to perform the associated activity. This distributed architecture can reduce the impact on the network and system resources to reduce congestion in bottlenecks while still allowing data to be accessible from a central location. 
     Referring to  FIG. 14 , method  1400  can include a block  1401  of receiving, at a first financial institution from a mobile device being used by a consumer, a request to pay a merchant for a payment amount from one or more first accounts of the consumer maintained by the first financial institution. The first financial institution can be similar or identical to financial institution  130  ( FIG. 1 ). The mobile device can be similar or identical to mobile device  120  ( FIG. 1 ). The consumer can be similar or identical to consumer  129  ( FIG. 1 ). The merchant can be similar or identical to merchant  119  ( FIG. 1 ). The one or more first accounts can be similar or identical to one or more of consumer accounts  131  ( FIG. 1 ). The one or more first accounts can include at least one non-demand deposit account. 
     In many embodiments, the request to pay can include information including a merchant identifier, a payment amount for one or more items to be purchased from the merchant by the consumer in a transaction, and a transaction identifier for the transaction. In a number of embodiments, the mobile device can be used by the consumer at a store of the merchant to pay for the transaction. In some embodiments, the information can be received by the mobile device from a point-of-sale terminal at the store of the merchant. The point-of-sale terminal can be similar or identical to point-of-sale terminal  110  ( FIG. 1 ). 
     In various embodiments, the one or more first accounts can include the loan account, and the loan account can be created after receiving the request to pay the merchant. In the same or other embodiments, the loan account can be used to fund at least a first portion of the payment amount of the transaction, and in a number of embodiments, a second portion of the payment amount can be funded from a demand deposit account of the consumer maintained at the first financial institution. 
     In some embodiments, the at least one non-demand deposit account can include a credit account. In a number of embodiments, at least a portion of the payment can be funded from a charge to the credit account. In various embodiments, the at least one non-demand deposit account can include a points account. 
     In several embodiments, method  1400  also can include a block  1402  of retrieving, at the first financial institution from a transaction system, an account identifier for a second account of the merchant maintained by a second financial institution based on the merchant identifier. The second account can be similar or identical to merchant account  151  ( FIG. 1 ). The second financial institution can be similar or identical to financial institution  150  ( FIG. 1 ). The transaction system can be similar or identical to transaction system  140  ( FIG. 1 ). In some embodiments, the transaction system can be maintained by an entity that is different from the merchant, the first financial institution, and the second financial institution. 
     In a number of embodiments, method  1400  additionally can include a block  1403  of sending, from the first financial institution to the transaction system, payment information regarding a payment to be made to the second account from the one or more first accounts, such that the payment information is routed through the transaction system to the second financial institution, and such that the point-of-sale terminal receives a notification of payment for the transaction in real-time while the consumer remains at the store of the merchant. In many embodiments, the payment information can include the transaction identifier, the account identifier of the second account, the payment amount, and/or other suitable include. In some embodiments, the payment information further can include one of: (a) one or more settlement credit pushes of funds that collectively total the payment amount from the one or more first accounts to the second account, or (b) one or more irrevocable promises to pay that collectively total the payment amount from the one or more first accounts to the second account. In many embodiments, the mobile device can send the request to pay after receiving from the consumer an approval for the transaction. For example, the consumer can authorize the transaction, after which the request to pay can be sent from the mobile device, such as shown in user interface display  1700  ( FIG. 17 ), as shown described below in further detail. 
     In certain embodiments, the first financial institution does not have access to a second account number for the second account for the transaction, and the second financial institution does not have access to a first account number for the first account for the transaction. In other embodiments, the first financial institution can have access to a second account number for the second account for the transaction, and/or the second financial institution can have access to a first account number for the first account for the transaction. 
     In many embodiments, method  1400  can include one or more optional blocks  1404 - 1407 , described below. In some embodiments, one or more of blocks  1404 - 1407  can be performed before one or more of blocks  1401 - 1403 . In the same or other embodiments, one or more of blocks  1404 - 1407  can be performed after block  1403 . 
     In several embodiments, method  1400  optionally can include block  1404  of sending, to the mobile device, an account balance of a demand deposit account of the consumer maintained by the first financial institution. For example, the account balance can be displayed on the mobile device on a user interface, such as shown in user interface display  1700  ( FIG. 17 ), as shown described below in further detail. 
     In a number of embodiments, method  1400  optionally can include block  1405  of determining that the account balance of the demand deposit account is less than the payment amount of the transaction. 
     In several embodiments, method  1400  optionally can include block  1406  of sending, to the mobile device, an option to at least partially fund the transaction using the at least one non-demand deposit account. For example, the option can be displayed on the mobile device using a user interface, such as shown in user interface display  1800  ( FIG. 18 ), user interface display  1900  ( FIG. 19 ), and/or user interface display  2000  ( FIG. 20 ), as described below in further detail. 
     In a number of embodiments, method  1400  optionally can include block  1407  of receiving, from the mobile device, a selection to at least partially fund the payment amount of the transaction using the at least one non-demand deposit account. For example, the selection can be received on the mobile device through a user interface, such as shown in user interface display  1800  ( FIG. 18 ), user interface display  1900  ( FIG. 19 ), and/or user interface display  2000  ( FIG. 20 ), as described below in further detail. In many embodiments, the one or more first accounts further can include the demand deposit account. In some embodiments, a first portion of the payment amount of the transaction can be funded from the demand deposit account, and a second portion of the payment amount of the transaction can be funded from the at least one non-demand deposit account. In other embodiments, the demand deposit account can be devoid of being used to fund the payment amount of the transaction, and the payment amount of the transaction can be funded wholly from the at least one non-demand deposit account. 
     Turning ahead in the drawings,  FIG. 15  illustrates a flow chart for a method  1500 , according to an embodiment. In some embodiments, method  1500  can be a method of facilitating secure payment transactions. Method  1500  is merely exemplary and is not limited to the embodiments presented herein. Method  1500  can be employed in many different embodiments or examples not specifically depicted or described herein. In some embodiments, the procedures, the processes, and/or the activities of method  1500  can be performed in the order presented. In other embodiments, the procedures, the processes, and/or the activities of method  1500  can be performed in any suitable order. In still other embodiments, one or more of the procedures, the processes, and/or the activities of method  1500  can be combined or skipped. In some embodiments, method  1500  can be performed by transaction system  140  ( FIG. 1 ). In some embodiments, method  1500  and other blocks in method  1500  can include using a distributed network including distributed memory architecture to perform the associated activity. This distributed architecture can reduce the impact on the network and system resources to reduce congestion in bottlenecks while still allowing data to be accessible from a central location. 
     Referring to  FIG. 15 , method  1500  can include a block  1501  of receiving, at a transaction system from a first entity, a request including a merchant identifier associated with a merchant. The transaction system can be similar or identical to transaction system  140  ( FIG. 1 ). In many embodiments, the merchant identifier can be similar to the merchant identifier described above. For example, in many embodiments, the merchant identifier can be setup and/or registered through the transaction system. The merchant can be similar or identical to merchant  119  ( FIG. 1 ). In some embodiments, the first entity can be at least one of the first financial institution, a mobile device being used by a consumer, or a mobile wallet provider in data communication with the mobile device being used by the consumer. For example, the first financial institution can be similar or identical to financial institution  130  ( FIG. 1 ), the mobile device can be similar or identical to mobile device  120  ( FIG. 1 ), the consumer can be similar or identical to consumer  129  ( FIG. 1 ), and/or the mobile wallet provider can be similar or identical to mobile application  123  ( FIG. 1 ) and/or mobile wallet provider  160  ( FIG. 1 ). 
     In some embodiments, the transaction system can be in data communication with a first financial institution that maintains one or more first accounts of a consumer and a second financial institution that maintains a second account of the merchant. The first financial institution can be similar or identical to financial institution  130  ( FIG. 1 ). The one or more first accounts can be similar or identical to one or more of consumer accounts  131  ( FIG. 1 ). In many embodiments, the one or more first accounts can include one or more of at least one non-demand deposit account. The consumer can be similar or identical to consumer  129  ( FIG. 1 ). The second financial institution can be similar or identical to financial institution  150  ( FIG. 1 ). The second account can be similar or identical to merchant account  151  ( FIG. 1 ). In many embodiments, the transaction system can be maintained by an entity that is different from the merchant, the first financial institution, and the second financial institution. In several embodiments, the consumer can use a mobile device at a store of the merchant to pay a payment amount for one or more items in a transaction using the one or more first accounts. The mobile device can be similar or identical to mobile device  120  ( FIG. 1 ). 
     In several embodiments, the first financial institution can be configured to send to the mobile device an account balance of a demand deposit account of the consumer maintained by the first financial institution. For example, the account balance can be displayed on the mobile device on a user interface, such as shown in user interface display  1700  ( FIG. 17 ), as shown described below in further detail. 
     In some embodiments, the first financial institution can be configured to determine that the account balance of the demand deposit account is less than the payment amount of the transaction. 
     In many embodiments, the first financial institution can be configured to send to the mobile device an option to at least partially fund the transaction using the at least one non-demand deposit account. For example, the option can be displayed on the mobile device using a user interface, such as shown in user interface display  1800  ( FIG. 18 ), user interface display  1900  ( FIG. 19 ), and/or user interface display  2000  ( FIG. 20 ), as described below in further detail. 
     In a number of embodiments, the first financial institution can be configured to receive from the mobile device a selection to at least partially fund the payment amount of the transaction using the at least one non-demand deposit account. For example, the selection can be received on the mobile device through a user interface, such as shown in user interface display  1800  ( FIG. 18 ), user interface display  1900  ( FIG. 19 ), and/or user interface display  2000  ( FIG. 20 ), as described below in further detail. In many embodiments, the one or more first accounts further can include the demand deposit account. In some embodiments, a first portion of the payment amount of the transaction can be funded from the demand deposit account, and a second portion of the payment amount of the transaction can be funded from the at least one non-demand deposit account. In other embodiments, the demand deposit account can be devoid of being used to fund any portion of the payment amount of the transaction, and the payment amount of the transaction can be funded wholly from the at least one non-demand deposit account. 
     In various embodiments, the one or more first accounts can include the loan account, and the loan account can be created after the consumer authorizes paying the payment amount. In the same or other embodiments, the loan account can be used to fund at least a first portion of the payment amount of the transaction, and in a number of embodiments, a second portion of the payment amount can be funded from a demand deposit account or another non-demand deposit account of the consumer maintained at the first financial institution. 
     In some embodiments, the at least one non-demand deposit account can include a credit account. In a number of embodiments, at least a portion of the payment can be funded from a charge to the credit account. In various embodiments, the at least one non-demand deposit account can include a points account. 
     In several embodiments, method  1500  also can include a block  1502  of determining, at the transaction system, an account identifier of the second account of the merchant maintained by a second financial institution using a merchant account database. The merchant account database can be similar or identical to merchant account database  141  ( FIG. 1 ). 
     In a number of embodiments, method  1500  additionally can include a block  1503  of sending the account identifier from the transaction system to the first financial institution. 
     In several embodiments, method  1500  further can include a block  1504  of receiving, at the transaction system from the first financial institution, payment information regarding a payment to be made to the second account from the one or more first accounts. In some embodiments, the payment information can include a transaction identifier, the account identifier of the second account, the payment amount, and/or other suitable information. In many embodiments, the payment information further can include one or more of: (a) one or more settlement credit pushes of funds that collectively total the payment amount from the one or more first accounts to the second account, or (b) one or more irrevocable promises to pay that collectively total the payment amount from the one or more first accounts to the second account. In many embodiments, the mobile device can send the request to pay after receiving from the consumer an approval for the transaction. For example, the consumer can authorize the transaction, after which the request to pay can be sent from the mobile device, such as shown in user interface display  1700  ( FIG. 17 ), as shown described below in further detail. 
     In a number of embodiments, method  1500  additionally can include a block  1505  of sending, from the transaction system to the second financial institution, the payment information, such that a point-of-sale terminal at the store of the merchant receives a notification of payment for the transaction in real-time while the consumer remains at the store of the merchant. The point-of-sale terminal can be similar or identical to point-of-sale terminal  110  ( FIG. 1 ). In many embodiments, the notification of the payment can be received at the point-of-sale terminal from the transaction system. In other embodiments, the notification of the payment can be received at the point-of-sale terminal from the second financial institution system. 
     In certain embodiments, the first financial institution does not have access to a second account number for the second account for the transaction, and the second financial institution does not have access to a first account number for the first account for the transaction. In other embodiments, the first financial institution can have access to a second account number for the second account for the transaction, and/or the second financial institution can have access to a first account number for the first account for the transaction. 
     Proceeding to the next drawing,  FIG. 16  illustrates a flow chart for a method  1600 , according to an embodiment. In some embodiments, method  1600  can be a method of facilitating secure payment transactions. Method  1600  is merely exemplary and is not limited to the embodiments presented herein. Method  1600  can be employed in many different embodiments or examples not specifically depicted or described herein. In some embodiments, the procedures, the processes, and/or the activities of method  1600  can be performed in the order presented. In other embodiments, the procedures, the processes, and/or the activities of method  1600  can be performed in any suitable order. In still other embodiments, one or more of the procedures, the processes, and/or the activities of method  1600  can be combined or skipped. In some embodiments, method  1600  can be performed by point-of-sale terminal  110  ( FIG. 1 ). In some embodiments, method  1600  and other blocks in method  1600  can include using a distributed network including distributed memory architecture to perform the associated activity. This distributed architecture can reduce the impact on the network and system resources to reduce congestion in bottlenecks while still allowing data to be accessible from a central location. 
     Referring to  FIG. 16 , method  1600  can include a block  1601  of determining, at a point-of-sale terminal at a store of a merchant, a payment amount for one or more items to be purchased from the merchant by a consumer in a transaction. The point-of-sale terminal can be similar or identical to point-of-sale terminal  110  ( FIG. 1 ). The merchant can be similar or identical to merchant  119  ( FIG. 1 ). The consumer can be similar or identical to consumer  129  ( FIG. 1 ). 
     In several embodiments, method  1600  also can include a block  1602  of sending first information from the point-of-sale terminal to a mobile device used by the consumer. The mobile device can be similar or identical to mobile device  120  ( FIG. 1 ). In many embodiments, the first information can include a merchant identifier, a transaction identifier, and the payment amount. In many embodiments, the merchant identifier can be similar to the merchant identifier described above. For example, in many embodiments, the merchant identifier can be setup and/or registered through a transaction system, such as transaction system  140  ( FIG. 1 ). In many embodiments, the mobile device can send a request to pay the merchant for the payment amount from one or more first accounts of the consumer maintained by a first financial institution. The first financial institution can be similar or identical to financial institution  130  ( FIG. 1 ). The one or more first accounts can be similar or identical to one or more of consumer accounts  131  ( FIG. 1 ). In many embodiments, the one or more first accounts can include one or more of at least one non-demand deposit account. In a number of embodiments, the first financial institution, upon receiving the request to pay, can retrieve from a transaction system an account identifier of a second account of the merchant maintained by a second financial institution based on the merchant identifier. The second financial institution can be similar or identical to financial institution  150  ( FIG. 1 ). The second account can be similar or identical to merchant account  151  ( FIG. 1 ). The transaction system can be similar or identical to transaction system  140  ( FIG. 1 ). In some embodiment, the first financial institution can send to the transaction system payment information regarding a payment to be made to the second account from the one or more first accounts, such that the payment information can be routed through the transaction system to the second financial institution. In a number of embodiments, the payment information can include the transaction identifier, the account identifier of the second account, the payment amount, and/or other suitable information. In many embodiments, the transaction system can be maintained by an entity that is different from the merchant, the first financial institution, and the second financial institution. 
     In some embodiments, the payment information further includes one or more of: (a) one or more settlement credit pushes of funds that collectively total the payment amount from the one or more first accounts to the second account, or (b) one or more irrevocable promises to pay that collectively total the payment amount from the one or more first accounts to the second account. In many embodiments, the mobile device can send the request to pay after receiving from the consumer an approval for the transaction. For example, the consumer can authorize the transaction, after which the request to pay can be sent from the mobile device. For example, the consumer can authorize the transaction, after which the request to pay can be sent from the mobile device, such as shown in user interface display  1700  ( FIG. 17 ), as shown described below in further detail. 
     In several embodiments, the first financial institution can be configured to send to the mobile device an account balance of a demand deposit account of the consumer maintained by the first financial institution. For example, the account balance can be displayed on the mobile device on a user interface, such as shown in user interface display  1700  ( FIG. 17 ), as shown described below in further detail. 
     In some embodiments, the first financial institution can be configured to determine that the account balance of the demand deposit account is less than the payment amount of the transaction. 
     In many embodiments, the first financial institution can be configured to send to the mobile device an option to at least partially fund the transaction using the at least one non-demand deposit account. For example, the option can be displayed on the mobile device using a user interface, such as shown in user interface display  1800  ( FIG. 18 ), user interface display  1900  ( FIG. 19 ), and/or user interface display  2000  ( FIG. 20 ), as described below in further detail. 
     In a number of embodiments, the first financial institution can be configured to receive from the mobile device a selection to at least partially fund the payment amount of the transaction using the at least one non-demand deposit account. For example, the selection can be received on the mobile device through a user interface, such as shown in user interface display  1800  ( FIG. 18 ), user interface display  1900  ( FIG. 19 ), and/or user interface display  2000  ( FIG. 20 ), as described below in further detail. In many embodiments, the one or more first accounts further can include the demand deposit account. In some embodiments, a first portion of the payment amount of the transaction can be funded from the demand deposit account, and a second portion of the payment amount of the transaction can be funded from the at least one non-demand deposit account. In other embodiments, the demand deposit account can be devoid of being used to fund any portion of the payment amount of the transaction, and the payment amount of the transaction can be funded wholly from the at least one non-demand deposit account. 
     In various embodiments, the one or more first accounts can include the loan account, and the loan account can be created after receiving the request to pay the merchant. In the same or other embodiments, the loan account can be used to fund at least a first portion of the payment amount of the transaction, and in a number of embodiments, a second portion of the payment amount can be funded from a demand deposit account or another non-demand deposit account of the consumer maintained at the first financial institution. 
     In some embodiments, the at least one non-demand deposit account can include a credit account. In a number of embodiments, at least a portion of the payment can be funded from a charge to the credit account. In various embodiments, the at least one non-demand deposit account can include a points account. 
     In certain embodiments, the first financial institution does not have access to a second account number for the second account for the transaction, and the second financial institution does not have access to a first account number for the first account for the transaction. In other embodiments, the first financial institution can have access to a second account number for the second account for the transaction, and/or the second financial institution can have access to a first account number for the first account for the transaction. 
     In several embodiments, method  1600  further can include a block  1603  of receiving, at the point-of-sale terminal, a notification of payment for the transaction in real-time while the consumer remains at the store of the merchant. In many embodiments, the notification of the payment can be received by the merchant and/or at the point-of-sale terminal from the transaction system. In other embodiments, the notification of the payment can be received by the merchant and/or at the point-of-sale terminal from the second financial institution system. 
     Turning ahead in the drawings,  FIG. 17  illustrates an exemplary user interface display  1700  to allow a consumer (e.g.,  129  ( FIG. 1 )) to approve a transaction on a mobile device (e.g.,  120  ( FIG. 1 )). User interface display  1700  is merely exemplary, and embodiments of the user interface display are not limited to the embodiments presented herein. The user interface display can be employed in many different embodiments or examples not specifically depicted or described herein, and can include other suitable elements. In many embodiments, mobile application  123  ( FIG. 1 ) can provide an interface for display on mobile device  120  ( FIG. 1 ), which can include user interface display  1700 . In a number of embodiments, the interface can allow consumer  129  ( FIG. 1 ) to approve or decline a transaction request received from point-of-sale terminal  110  ( FIG. 1 ). 
     In a number of embodiments, user interface display  1700  can include a title bar  1701 , a descriptor  1710 , a payment amount field  1720 , a merchant field  1730 , a transaction identifier field  1740 , a prompt  1750 , an approving selection button  1760 , and/or a declining selection button  1770 . In many embodiments, title bar  1701  can include the name of the mobile wallet or mobile application (e.g., mobile application  123  ( FIG. 1 )). In a number of embodiments, descriptor  1710  can describe that a transaction request was received. For example, after mobile device  120  ( FIG. 1 ) receives information, such as the transaction code, the merchant identifier, the payment amount, the transaction identifier, and/or other information from point-of-sale terminal  110  ( FIG. 1 ), then user interface display  1700  can be displayed on mobile device  120  ( FIG. 1 ) to consumer  129  ( FIG. 1 ). 
     In several embodiments, user interface display  1700  can include a number of fields to display information about the transaction, such as payment amount field  1720 , merchant field  1730 , and/or transaction identifier field  1740 . In many embodiments, payment amount field  1720  can display the payment amount received from point-of-sale terminal  110  ( FIG. 1 ). In several embodiments, merchant field  1730  can display the name of merchant  119  ( FIG. 1 ). In some embodiments, the name of the merchant can be received from point-of-sale terminal  110  ( FIG. 1 ). In other embodiment, the merchant identifier received from point-of-sale terminal  110  ( FIG. 1 ) can be used to retrieve the name of the merchant, such as by mobile device  120  ( FIG. 1 ) querying transaction system  140  ( FIG. 1 ) directly or through mobile wallet provider  160  ( FIG. 1 ) and/or financial institution  130  ( FIG. 1 ). In a number of embodiments, transaction identifier field  1740  can display the transaction identifier received from point-of-sale terminal  110  ( FIG. 1 ). In other embodiments, user interface display  1700  can include additional or other suitable fields to display information about the transaction. 
     In several embodiments, prompt  1750  can ask consumer  129  ( FIG. 1 ) to confirm the transaction using an account (e.g., consumer account  131  ( FIG. 1 )) that has been provisioned to or otherwise associated with mobile application  123  ( FIG. 1 ), such as Checking Account A. When more than one account (e.g., consumer account  131  ( FIG. 1 )) has been provisioned to or otherwise associated with mobile application  123  ( FIG. 1 ), the user interface display (e.g.,  1700 ) can include a request to select one of the accounts (e.g., consumer account  131  ( FIG. 1 )) to use for the payment transaction. In many embodiments, approving selection button  1760  can be selected by consumer  129  ( FIG. 1 ) to approve the transaction using the account. In some embodiments, declining selection button  1770  can be selected by consumer  129  ( FIG. 1 ) to decline the transaction using the account. 
     Proceeding to the next drawing,  FIG. 18  illustrates an exemplary user interface display  1800  to allow a consumer (e.g.,  129  ( FIG. 1 )) to choose to use another account for the payment transaction when the approved account has insufficient funds or limited funds. User interface display  1800  is merely exemplary, and embodiments of the user interface display are not limited to the embodiments presented herein. The user interface display can be employed in many different embodiments or examples not specifically depicted or described herein, and can include other suitable elements. User interface display  1800  can be similar to user interface display  1700  ( FIG. 17 ), and various elements of user interface display  1800  can be similar or identical to various elements of user interface display  1700  ( FIG. 17 ). In many embodiments, mobile application  123  ( FIG. 1 ) can provide an interface for display on mobile device  120  ( FIG. 1 ), which can include user interface display  1800 . In a number of embodiments, the interface can allow consumer  129  ( FIG. 1 ) to choose whether to use another account for the payment transaction when the approved account has insufficient or limited funds. 
     In a number of embodiments, user interface display  1800  can include a title bar  1801 , an account balance field  1810 , a payment amount field  1820 , a prompt  1830 , an account selection button  1840 , and/or a canceling selection button  1850 . In many embodiments, title bar  1801  can include the name of the mobile wallet or mobile application (e.g., mobile application  123  ( FIG. 1 )). Title bar  1801  can be similar or identical to title bar  1701  ( FIG. 17 ). 
     In several embodiments, user interface display  1800  can include a number of fields to display information about the transaction request using the account approved in user interface display  1700  ( FIG. 17 ). For example, the fields can include account balance field  1810  and payment amount field  1820 . In some embodiments, account balance field can show the balance of the account that was approved for payment using user interface display  1700  ( FIG. 17 ). In many embodiments, payment amount field  1820  can display the payment amount. Payment amount field  1820  can be similar or identical to payment amount field  1720  ( FIG. 17 ). In many embodiments, user interface display  1800  can be displayed when the account balance is less than the payment amount. In other embodiments, user interface display  1800  can be displayed when the account balance is more than the payment amount, but the difference between the account balance and the payment amount is less than a threshold amount, such as $10, $50, $100, $500, or another suitable threshold amount. 
     In several embodiments, prompt  1830  can ask consumer  129  ( FIG. 1 ) whether to use another account or loan to pay for the payment amount. In many embodiments, account selection button  1840  can be selected by consumer  129  ( FIG. 1 ) to indicate that another account or loan should be used to at least partially pay for the payment amount. In some embodiments, canceling selection button  1850  can be selected by consumer  129  ( FIG. 1 ) to cancel the transaction. In some embodiments, such as when the account balance is sufficient to cover the payment amount, another selection button (not shown) can be included in the user interface display (e.g.,  1800 ) to authorize proceeding with the payment transaction using the account approved in user interface display  1700  ( FIG. 17 ). 
     Proceeding to the next drawing,  FIG. 19  illustrates an exemplary user interface display  1900  to allow a consumer (e.g.,  129  ( FIG. 1 )) to select another account for the payment transaction when the approved account has insufficient funds. User interface display  1900  is merely exemplary, and embodiments of the user interface display are not limited to the embodiments presented herein. The user interface display can be employed in many different embodiments or examples not specifically depicted or described herein, and can include other suitable elements. User interface display  1900  can be similar to user interface display  1700  ( FIG. 17 ) and/or user interface display  1800  ( FIG. 18 ), and various elements of user interface display  1900  can be similar or identical to various elements of user interface display  1700  ( FIG. 17 ) and/or user interface display  1800  ( FIG. 18 ). In many embodiments, mobile application  123  ( FIG. 1 ) can provide an interface for display on mobile device  120  ( FIG. 1 ), which can include user interface display  1900 . In a number of embodiments, the interface can allow consumer  129  ( FIG. 1 ) to select another account for the payment transaction when the approved account has insufficient or limited funds. 
     In a number of embodiments, user interface display  1900  can include a title bar  1901 , a prompt  1910 , an option  1911 , an option  1912 , an option  1913 , an option  1914 , a proceeding selection button  1920 , and/or a canceling selection button  1930 . In many embodiments, title bar  1901  can include the name of the mobile wallet or mobile application (e.g., mobile application  123  ( FIG. 1 )). Title bar  1901  can be similar or identical to title bar  1701  ( FIG. 17 ) and/or title bar  1801  ( FIG. 18 ). 
     In many embodiments, prompt  1910  can ask consumer  129  ( FIG. 1 ) to select another account or loan to use for the payment transaction. In various embodiments, user interface display  1900  can include one or more options of other accounts or loan options that the user can select, such as options  1911 - 1914 . In some embodiments, the options can include one or more existing accounts, such as Savings Account B displayed in option  1911 , Credit Account C displayed in option  1912 , and Points Account D displayed in option  1914 . For example, Savings Account B, Credit Account C, and/or Points Account D can be others of consumer accounts  131  ( FIG. 1 ) held by consumer  129  ( FIG. 1 ) at financial institution  130  ( FIG. 1 ). In a number of embodiments, the options can include the opportunity to open a new loan, as displayed in option  1913 . For example, the new loan can be a micro-loan to pay at least partially for the payment amount, as described above. In some embodiments, user interface display  1900  can allow consumer  129  ( FIG. 1 ) to select one of options  1911 - 1914 . In other embodiments, user interface display  1900  can allowed consumer  129  ( FIG. 1 ) to select more than one of options  1911 - 1914 . 
     In many embodiments, proceeding selection button  1920  can be selected by consumer  129  ( FIG. 1 ) to indicate that accounts corresponding to the one or more options (e.g.,  1911 - 1914 ) should be used for the payment transaction. In some embodiments, canceling selection button  1930  can be selected by consumer  129  ( FIG. 1 ) to cancel the transaction. 
     Proceeding to the next drawing,  FIG. 20  illustrates an exemplary user interface display  2000  to allow a consumer (e.g.,  129  ( FIG. 1 )) to select the amount to pay using the other account selected in user interface display  1900  ( FIG. 19 ). User interface display  2000  is merely exemplary, and embodiments of the user interface display are not limited to the embodiments presented herein. The user interface display can be employed in many different embodiments or examples not specifically depicted or described herein, and can include other suitable elements. User interface display  2000  can be similar to user interface display  1700  ( FIG. 17 ), user interface display  1800  ( FIG. 18 ), and/or user interface display  1900  ( FIG. 19 ), and various elements of user interface display  2000  can be similar or identical to various elements of user interface display  1700  ( FIG. 17 ), user interface display  1800  ( FIG. 18 ), and/or user interface display  1900  ( FIG. 19 ). In many embodiments, mobile application  123  ( FIG. 1 ) can provide an interface for display on mobile device  120  ( FIG. 1 ), which can include user interface display  2000 . In a number of embodiments, the interface can allow consumer  129  ( FIG. 1 ) to select the amount to pay using the other account selected in user interface display  1900  ( FIG. 19 ). 
     In a number of embodiments, user interface display  2000  can include a title bar  2001 , a prompt  2010 , an option  2011 , an option  2012 , an approving selection button  2020 , and/or a canceling selection button  2030 . In many embodiments, title bar  2001  can include the name of the mobile wallet or mobile application (e.g., mobile application  123  ( FIG. 1 )). Title bar  2001  can be similar or identical to title bar  1701  ( FIG. 17 ), title bar  1801  ( FIG. 18 ), and/or title bar  1901  ( FIG. 19 ). 
     In many embodiments, prompt  2010  can ask consumer  129  ( FIG. 1 ) to select the amount to pay using the other account or payment option selected in user interface display  1900  ( FIG. 19 ), such as a new loan. In various embodiments, user interface display  2000  can include one or more options that consumer  129  ( FIG. 1 ) can select, such as options  2011 - 2012 . For example, option  2011  can include the option to pay the full payment amount using the other account (e.g., new loan) selected in user interface display  1900  ( FIG. 19 ). As another example, option  2012  can include the option to partially pay the payment amount using the other account (e.g., new loan) selected in user interface display  1900  ( FIG. 19 ), and can allow consumer  129  ( FIG. 1 ) to enter the amount to be used for the partial payment from the other account. When more than one account was selected using user interface display  1900  ( FIG. 19 ), the user interface display (e.g.,  2000 ) can include a prompt (e.g.,  2010 ) and options (e.g.,  2011 - 2012 ) for each of the other accounts selected in user interface display  1900  ( FIG. 19 ). In many embodiments, only one of options  2011  and  2012  can be selected, per account, by consumer  129  ( FIG. 1 ) and approved by consumer  129  ( FIG. 1 ) via approving selection button  2020 . 
     In many embodiments, approving selection button  2020  can be selected by consumer  129  ( FIG. 1 ) to indicate that amount selected in one of options  2011 - 2012  should be used to pay for the payment transaction. In some embodiments, canceling selection button  2030  can be selected by consumer  129  ( FIG. 1 ) to cancel the transaction. 
     Proceeding to the next drawing,  FIG. 21  illustrates an exemplary user interface display  2100  to confirm that a payment request has been sent from mobile device  120  ( FIG. 1 ). User interface display  2100  is merely exemplary, and embodiments of the user interface display are not limited to the embodiments presented herein. The user interface display can be employed in many different embodiments or examples not specifically depicted or described herein, and can include other suitable elements. User interface display  2100  can be similar to user interface display  1700  ( FIG. 17 ), user interface display  1800  ( FIG. 18 ), user interface display  1900  ( FIG. 19 ), and/or user interface display  2000  ( FIG. 20 ), and various elements of user interface display  2100  can be similar or identical to various elements of user interface display  1700  ( FIG. 17 ), user interface display  1800  ( FIG. 18 ), user interface display  1900  ( FIG. 19 ), and/or user interface display  2000  ( FIG. 20 ). In many embodiments, mobile application  123  ( FIG. 1 ) can provide an interface for display on mobile device  120  ( FIG. 1 ), which can include user interface display  2100 . In a number of embodiments, the interface can display a confirmation to consumer  129  ( FIG. 1 ) that a request has been sent for the payment authorized in user interface display  1700  ( FIG. 17 ), user interface display  1800  ( FIG. 18 ), user interface display  1900  ( FIG. 19 ), and/or user interface display  2000  ( FIG. 20 ). 
     In a number of embodiments, user interface display  2100  can include a title bar  2101 , a descriptor field  2110 , and/or a selection button  2120 . In many embodiments, title bar  2101  can include the name of the mobile wallet or mobile application (e.g., mobile application  123  ( FIG. 1 )). Title bar  2101  can be similar or identical to title bar  1701  ( FIG. 17 ), title bar  1801  ( FIG. 18 ), title bar  1901  ( FIG. 19 ), and/or title bar  2001  ( FIG. 20 ). 
     In many embodiments, descriptor field  2110  can include information about the payment that was requested, such as the amount that was requested to be paid out of each of the accounts that were authorized for payment by consumer  129  ( FIG. 1 ). For example, if consumer  129  ( FIG. 1 ) choose to partially pay for the payment amount using a new loan in the amount of $83.20, then descriptor field  2110  can display that $60.00 from Account A was used and $83.20 from New Loan was used, as shown in  FIG. 21 . 
     In several embodiments, selection button  2120  can be selected by consumer  129  ( FIG. 1 ) to dismiss the message displayed in user interface display  2100 . 
     Proceeding to the next drawing,  FIG. 22  illustrates an exemplary user interface display  2200  to confirm that payment transaction to merchant  119  ( FIG. 1 ) has successfully completed. User interface display  2200  is merely exemplary, and embodiments of the user interface display are not limited to the embodiments presented herein. The user interface display can be employed in many different embodiments or examples not specifically depicted or described herein, and can include other suitable elements. User interface display  2200  can be similar to user interface display  1700  ( FIG. 17 ), user interface display  1800  ( FIG. 18 ), user interface display  1900  ( FIG. 19 ), user interface display  2000  ( FIG. 20 ), and/or user interface display  2100  ( FIG. 21 ), and various elements of user interface display  2200  can be similar or identical to various elements of user interface display  1700  ( FIG. 17 ), user interface display  1800  ( FIG. 18 ), user interface display  1900  ( FIG. 19 ), user interface display  2000  ( FIG. 20 ), and/or user interface display  2100  ( FIG. 21 ). In many embodiments, mobile application  123  ( FIG. 1 ) can provide an interface for display on mobile device  120  ( FIG. 1 ), which can include user interface display  2200 . In a number of embodiments, the interface can display a confirmation to consumer  129  ( FIG. 1 ) that payment to merchant  119  ( FIG. 1 ) has successfully completed for the payment authorized in user interface display  1700  ( FIG. 17 ), user interface display  1800  ( FIG. 18 ), user interface display  1900  ( FIG. 19 ), and/or user interface display  2000  ( FIG. 20 ). 
     In a number of embodiments, user interface display  2200  can include a title bar  2201 , a descriptor field  2210 , and/or a selection button  2220 . In many embodiments, title bar  2201  can include the name of the mobile wallet or mobile application (e.g., mobile application  123  ( FIG. 1 )). Title bar  2201  can be similar or identical to title bar  1701  ( FIG. 17 ), title bar  1801  ( FIG. 18 ), title bar  1901  ( FIG. 19 ), title bar  2001  ( FIG. 20 ), and/or title bar  2101  ( FIG. 21 ). 
     In many embodiments, descriptor field  2210  can include a message about the success or failure of the payment request, for example, that the payment is complete. If the request failed, the message can indicate that the payment failed. 
     In several embodiments, selection button  2220  can be selected by consumer  129  ( FIG. 1 ) to dismiss the message displayed in user interface display  2200 . 
     Returning again to  FIG. 1 , as described above, point-of-sale terminal  110  can include one or more modules, such as checkout module  111 , communication module  112 , payment module  113 , consumer information module  114 , and/or security module  115 . Point-of-sale terminal  110  and the modules therein are merely exemplary and are not limited to the embodiments presented herein. Point-of-sale terminal  110  can be employed in many different embodiments or examples not specifically depicted or described herein. In some embodiments, certain elements or modules of system  110  can perform various procedures, processes, and/or acts. In other embodiments, the procedures, processes, and/or acts can be performed by other suitable elements or modules. 
     In many embodiments, checkout module  111  can at least partially perform block  501  ( FIG. 5 ) of determining, at a point-of-sale terminal at a store of a merchant, a payment amount for one or more items to be purchased from the merchant by a consumer, block  901  ( FIG. 9 ) of determining, at a point-of-sale terminal at a store of a merchant, a payment amount for one or more items to be purchased from the merchant by a consumer in a transaction, and/or block  1601  ( FIG. 16 ) of determining, at a point-of-sale terminal at a store of a merchant, a payment amount for one or more items to be purchased from the merchant by a consumer in a transaction. 
     In several embodiments, communication module  112  can at least partially perform block  502  ( FIG. 5 ) of sending first information from the point-of-sale terminal to a mobile device used by the consumer, block  503  ( FIG. 5 ) of receiving at the point-of-sale terminal from the mobile device, information about the consumer, block  504  ( FIG. 5 ) of receiving, at the point-of-sale terminal from the second financial institution, a notification to satisfy an expectation of the merchant for payment from the consumer, block  903  ( FIG. 9 ) of providing the transaction code to a mobile device being used by the consumer, block  904  ( FIG. 9 ) of receiving, at the point-of-sale terminal, a notification of payment for the transaction in real-time while the consumer remains at the store of the merchant, block  1602  ( FIG. 16 ) of sending first information from the point-of-sale terminal to a mobile device used by the consumer, and/or block  1603  ( FIG. 16 ) of receiving, at the point-of-sale terminal, a notification of payment for the transaction in real-time while the consumer remains at the store of the merchant. 
     In a number of embodiments, payment module  113  can at least partially perform block  504  ( FIG. 5 ) of receiving, at the point-of-sale terminal from the second financial institution, a notification to satisfy an expectation of the merchant for payment from the consumer, and/or block  904  ( FIG. 9 ) of receiving, at the point-of-sale terminal, a notification of payment for the transaction in real-time while the consumer remains at the store of the merchant. 
     In various embodiments, consumer information module  114  can at least partially perform block  503  ( FIG. 5 ) of receiving at the point-of-sale terminal from the mobile device, information about the consumer. 
     In a number of embodiments, security module  115  can at least partially perform block  902  ( FIG. 9 ) of generating a transaction code including a merchant public identifier, the payment amount, a transaction identifier for the transaction, and a digital signature. 
     Continuing with  FIG. 1 , as described above, mobile device  120  can include one or more modules, such as authentication module  121 , account module  122 , communication module  124 , security module  125 , and/or loan module  126 . Mobile device  120  and the modules therein are merely exemplary and are not limited to the embodiments presented herein. Mobile device  120  can be employed in many different embodiments or examples not specifically depicted or described herein. In some embodiments, certain elements or modules of mobile device  120  can perform various procedures, processes, and/or acts. In other embodiments, the procedures, processes, and/or acts can be performed by other suitable elements or modules. 
     In many embodiments, authentication module  121  can at least partially perform block  401  ( FIG. 4 ) of performing, at a mobile device, a preliminary identity authentication of a consumer using the mobile device, block  407  ( FIG. 4 ) of performing, at the mobile device, the additional identity authentication of the consumer using the mobile device, and/or block  1301  ( FIG. 13 ) of performing, at a mobile device being used by a consumer, an identity authentication of the consumer. 
     In several embodiments, account module  122  can at least partially perform block  403  ( FIG. 4 ) of sending, from the mobile device to the first financial institution, a preliminary request for account information, block  404  ( FIG. 4 ) of receiving, at the mobile device from the first financial institution the account information, and/or block  1304  ( FIG. 13 ) of receiving, from the first financial institution, an account balance of a demand deposit account of the consumer maintained by the first financial institution. 
     In a number of embodiments, communication module  124  can at least partially perform block  402  ( FIG. 4 ) of receiving at the mobile device first information from a point-of-sale terminal, block  403  ( FIG. 4 ) of sending, from the mobile device to the first financial institution, a preliminary request for account information, block  404  ( FIG. 4 ) of receiving, at the mobile device from the first financial institution, the account information, block  405  ( FIG. 4 ) of sending, from the mobile device to the first financial institution, a first request to pay the merchant for the payment amount from the first account for one or more items to be purchased from the merchant by the consumer, block  406  ( FIG. 4 ) of receiving, at the mobile device from the first financial institution, an additional authentication request to perform an additional identity authentication of the consumer using the mobile device, block  408  ( FIG. 4 ) of sending, from the mobile device to the first financial institution, a response to the additional authentication request, block  1001  ( FIG. 10 ) of receiving, at a mobile device being used by a consumer, a transaction code from a point-of-sale terminal at a store of a merchant, block  1003  ( FIG. 10 ) of receiving from the consumer an approval for the transaction, block  1004  ( FIG. 10 ) of sending, from the mobile device, a request to pay the merchant for the payment amount from a first account of the consumer maintained by a first financial institution, block  1302  ( FIG. 13 ) of receiving, at the mobile device, first information from a point-of-sale terminal at a store of a merchant, block  1303  ( FIG. 13 ) of sending, from the mobile device, a request to pay the merchant for the payment amount from one or more first accounts of the consumer maintained by a first financial institution, and/or block  1305  ( FIG. 13 ) of displaying the account balance of the demand deposit account to the consumer. 
     In several embodiments, security module  125  can at least partially perform block  1002  ( FIG. 10 ) of verifying the digital signature for the transaction code. 
     In a number of embodiments, loan module  126  can at least partially perform block  1305  ( FIG. 13 ) of displaying the account balance of the demand deposit account to the consumer, block  1307  ( FIG. 13 ) of presenting to the consumer an option to at least partially fund the transaction using the at least one non-demand deposit account, and/or block  1308  ( FIG. 13 ) of receiving from the consumer a selection to at least partially fund the payment amount of the transaction using the at least one non-demand deposit account. 
     Continuing with  FIG. 1 , as described above, financial institution  130  can include one or more modules, such as communication module  132 , authorization module  133 , account module  134 , and/or loan module  135 . Financial institution  130  and the modules therein are merely exemplary and are not limited to the embodiments presented herein. Financial institution  130  can be employed in many different embodiments or examples not specifically depicted or described herein. In some embodiments, certain elements or modules of financial institution  130  can perform various procedures, processes, and/or acts. In other embodiments, the procedures, processes, and/or acts can be performed by other suitable elements or modules. 
     In many embodiments, communication module  132  can at least partially perform block  201  ( FIG. 2 ) of receiving, at a first financial institution from a mobile device, a preliminary request for account information, block  202  ( FIG. 2 ) of sending, from the first financial institution to the mobile device, the account information, block  203  ( FIG. 2 ) of receiving, at a first financial institution from a mobile device of a consumer, a first request to pay a merchant for a payment amount from a first account of the consumer maintained by the first financial institution, block  206  ( FIG. 2 ) of sending, from the first financial institution to the first system, a second request to determine the second information, block  207  ( FIG. 2 ) of receiving, at the first financial institution from the first system, the third information, block  212  ( FIG. 2 ) of sending, from the first financial institution to the first system, payment information regarding a payment to be made to the second account from the first account, block  1101  ( FIG. 11 ) of receiving, at a first financial institution from a mobile device being used by a consumer, a request to pay a merchant for a payment amount from a first account of the consumer maintained by the first financial institution, block  1102  ( FIG. 11 ) of retrieving, at the first financial institution from a transaction system, an account identifier for a second account of the merchant maintained by a second financial institution based on the merchant public identifier, block  1103  ( FIG. 11 ) of sending, from the first financial institution to the transaction system, payment information regarding a payment to be made to the second account from the first account, block  1401  ( FIG. 14 ) of receiving, at a first financial institution from a mobile device being used by a consumer, a request to pay a merchant for a payment amount from one or more first accounts of the consumer maintained by the first financial institution, block  1402  ( FIG. 14 ) of retrieving, at the first financial institution from a transaction system, an account identifier for a second account of the merchant maintained by a second financial institution based on the merchant identifier, block  1403  ( FIG. 14 ) of sending, from the first financial institution to the transaction system, payment information regarding a payment to be made to the second account from the one or more first accounts, block  1404  ( FIG. 14 ) of sending, to the mobile device, an account balance of a demand deposit account of the consumer maintained by the first financial institution, block  1406  ( FIG. 14 ) of sending, to the mobile device, an option to at least partially fund the transaction using the at least one non-demand deposit account, and/or block  1407  ( FIG. 14 ) of receiving, from the mobile device, a selection to at least partially fund the payment amount of the transaction using the at least one non-demand deposit account. 
     In some embodiments, authorization module  133  can at least partially perform block  208  ( FIG. 2 ) of authorizing, at the first financial institution, a payment from the first account to the second account, and/or block  209  ( FIG. 2 ) of authenticating an identity of the consumer that used the mobile device to send the first request to pay the merchant from the first account. 
     In a number of embodiments, account module  134  can at least partially perform block  201  ( FIG. 2 ) of receiving, at a first financial institution from a mobile device, a preliminary request for account information, block  202  ( FIG. 2 ) of sending, from the first financial institution to the mobile device, the account information, block  204  ( FIG. 2 ) of determining, at the first financial institution, second information, block  205  ( FIG. 2 ) of determining, at the first financial institution, the second information at least partially based on the merchant identifier and the third information, block  209  ( FIG. 2 ) of authenticating an identity of the consumer that used the mobile device to send the first request to pay the merchant from the first account, block  210  ( FIG. 2 ) of determining a current status of the first account, block  211  ( FIG. 2 ) of determining available funds of the first account, block  1102  ( FIG. 11 ) of retrieving, at the first financial institution from a transaction system, an account identifier for a second account of the merchant maintained by a second financial institution based on the merchant public identifier, block  1402  ( FIG. 14 ) of retrieving, at the first financial institution from a transaction system, an account identifier for a second account of the merchant maintained by a second financial institution based on the merchant identifier, and/or block  1404  ( FIG. 14 ) of sending, to the mobile device, an account balance of a demand deposit account of the consumer maintained by the first financial institution. 
     In some embodiments, loan module  135  can at least partially perform block  1405  ( FIG. 14 ) of determining that the account balance of the demand deposit account is less than the payment amount of the transaction, block  1406  ( FIG. 14 ) of sending, to the mobile device, an option to at least partially fund the transaction using the at least one non-demand deposit account, block  1407  ( FIG. 14 ) of receiving, from the mobile device, a selection to at least partially fund the payment amount of the transaction using the at least one non-demand deposit account, and/or creating the loan account. 
     Continuing with  FIG. 1 , as described above, transaction system  140  can include one or more modules, such as communication module  143 , account module  144 , transaction module  145 , and/or security module  146 . Transaction system  140  and the modules therein are merely exemplary and are not limited to the embodiments presented herein. Transaction system  140  can be employed in many different embodiments or examples not specifically depicted or described herein. In some embodiments, certain elements or modules of transaction system  140  can perform various procedures, processes, and/or acts. In other embodiments, the procedures, processes, and/or acts can be performed by other suitable elements or modules. 
     In many embodiments, communication module  143  can at least partially perform block  301  ( FIG. 3 ) of receiving, at a first system from a first financial institution, a request, block  303  ( FIG. 3 ) of sending the first information from the first system to the first financial institution, block  304  ( FIG. 3 ) of receiving, at the first system from the first financial institution, payment information regarding a payment to be made to the second account from the first account to pay the merchant for one or more items to be purchased from the merchant by the consumer for the payment amount, block  306  ( FIG. 3 ) of sending, from the first system to the second financial institution, the payment information such that the second financial institution, upon receiving the payment information, notifies the merchant to satisfy an expectation of the merchant for payment from the consumer, block  1201  ( FIG. 12 ) of receiving, at a transaction system from a first entity, a request including a merchant public identifier associated with a merchant, block  1203  ( FIG. 12 ) of sending the account identifier to the first financial institution, block  1204  ( FIG. 12 ) of receiving, at the transaction system from the first financial institution, payment information regarding a payment to be made to the second account from the first account, block  1205  ( FIG. 12 ) of sending, from the transaction system to the second financial institution, the payment information, block  1501  ( FIG. 15 ) of receiving, at a transaction system from a first entity, a request including a merchant identifier associated with a merchant, block  1503  ( FIG. 15 ) of sending the account identifier from the transaction system to the first financial institution, block  1504  ( FIG. 15 ) of receiving, at the transaction system from the first financial institution, payment information regarding a payment to be made to the second account from the one or more first accounts, and/or block  1505  ( FIG. 15 ) of sending, from the transaction system to the second financial institution, the payment information, such that a point-of-sale terminal at the store of the merchant receives a notification of payment for the transaction in real-time while the consumer remains at the store of the merchant. 
     In some embodiments, account module  144  can at least partially perform block  302  ( FIG. 3 ) of determining, at the first system, using the merchant account database, first information, block  1202  ( FIG. 12 ) of determining, at the transaction system, an account identifier of the second account based on the merchant public identifier using a merchant account database, and/or block  1502  ( FIG. 15 ) of determining, at the transaction system, an account identifier of the second account of the merchant maintained by a second financial institution using a merchant account database. 
     In a number of embodiments, transaction module  145  can at least partially perform block  305  ( FIG. 3 ) of storing the payment information in the transaction database, block  1201  ( FIG. 12 ) of receiving, at a transaction system from a first entity, a request including a merchant public identifier associated with a merchant, block  1203  ( FIG. 12 ) of sending the account identifier to the first financial institution, block  1204  ( FIG. 12 ) of receiving, at the transaction system from the first financial institution, payment information regarding a payment to be made to the second account from the first account, and/or a block  1205  ( FIG. 12 ) of sending, from the transaction system to the second financial institution, the payment information. 
     In some embodiments, account module  146  can at least partially perform generating the transaction code and/or merchant security transaction code. 
     Continuing with  FIG. 1 , as described above, financial institution  150  can include one or more modules, such as communication module  152 , and/or account module  153 . Financial institution  150  and the modules therein are merely exemplary and are not limited to the embodiments presented herein. Financial institution  150  can be employed in many different embodiments or examples not specifically depicted or described herein. In some embodiments, certain elements or modules of financial institution  150  can perform various procedures, processes, and/or acts. In other embodiments, the procedures, processes, and/or acts can be performed by other suitable elements or modules. 
     In many embodiments, communication module  152  can at least partially perform block  601  ( FIG. 6 ) of receiving, at a second financial institution from a first system, payment information regarding a payment to be made to a second account of a merchant maintained by the second financial institution from a first account of a consumer maintained by a first financial institution to pay the merchant for one or more items to be purchased from the merchant by the consumer for the payment amount, and/or block  603  ( FIG. 6 ) of sending, from the second financial institution to the point-of-sale terminal, a notification to satisfy an expectation of the merchant for payment from the consumer 
     In various embodiments, account module  153  can at least partially perform block  602  ( FIG. 6 ) of crediting the second account with the payment amount. 
     Turning ahead in the drawings,  FIG. 7  illustrates a computer  700 , all of which or a portion of which can be suitable for implementing an embodiment of at least a portion of point-of-sale terminal  110  ( FIG. 1 ), mobile device  120  ( FIG. 1 ), financial institution  130  ( FIG. 1 ), transaction system  140  ( FIG. 1 ), financial institution  150  ( FIG. 1 ), and/or the techniques described in method  200  ( FIG. 2 ), method  300  ( FIG. 3 ), method  400  ( FIG. 4 ), method  500  ( FIG. 5 ), method  600  ( FIG. 6 ), method  900  ( FIG. 9 ), method  1000  ( FIG. 10 ), method  1100  ( FIG. 11 ), method  1200  ( FIG. 12 ), method  1300  ( FIG. 13 ), method  1400  ( FIG. 14 ), method  1500  ( FIG. 15 ), and/or method  1600  ( FIG. 16 ). Computer  700  includes a chassis  702  containing one or more circuit boards (not shown), a USB (universal serial bus) port  712 , a Compact Disc Read-Only Memory (CD-ROM) and/or Digital Video Disc (DVD) drive  716 , and a hard drive  714 . A representative block diagram of the elements included on the circuit boards inside chassis  702  is shown in  FIG. 8 . A central processing unit (CPU)  810  in  FIG. 8  is coupled to a system bus  814  in  FIG. 8 . In various embodiments, the architecture of CPU  810  can be compliant with any of a variety of commercially distributed architecture families. 
     Continuing with  FIG. 8 , system bus  814  also is coupled to memory  808  that includes both read only memory (ROM) and random access memory (RAM). Non-volatile portions of memory storage unit  808  or the ROM can be encoded with a boot code sequence suitable for restoring computer  700  ( FIG. 7 ) to a functional state after a system reset. In addition, memory  808  can include microcode such as a Basic Input-Output System (BIOS). In some examples, the one or more memory storage units of the various embodiments disclosed herein can comprise memory storage unit  808 , a USB-equipped electronic device, such as, an external memory storage unit (not shown) coupled to universal serial bus (USB) port  712  ( FIGS. 7-8 ), hard drive  714  ( FIGS. 7-8 ), and/or CD-ROM or DVD drive  716  ( FIGS. 7-8 ). In the same or different examples, the one or more memory storage units of the various embodiments disclosed herein can comprise an operating system, which can be a software program that manages the hardware and software resources of a computer and/or a computer network. The operating system can perform basic tasks such as, for example, controlling and allocating memory, prioritizing the processing of instructions, controlling input and output devices, facilitating networking, and managing files. Some examples of common operating systems can comprise Microsoft® Windows® operating system (OS), Mac® OS, UNIX® OS, and Linux® OS. 
     As used herein, “processor” and/or “processing module” means any type of computational circuit, such as but not limited to a microprocessor, a microcontroller, a controller, a complex instruction set computing (CISC) microprocessor, a reduced instruction set computing (RISC) microprocessor, a very long instruction word (VLIW) microprocessor, a graphics processor, a digital signal processor, or any other type of processor or processing circuit capable of performing the desired functions. In some examples, the one or more processors of the various embodiments disclosed herein can comprise CPU  810 . 
     In the depicted embodiment of  FIG. 8 , various I/O devices such as a disk controller  804 , a graphics adapter  824 , a video controller  802 , a keyboard adapter  826 , a mouse adapter  806 , a network adapter  820 , and other I/O devices  822  can be coupled to system bus  814 . Keyboard adapter  826  and mouse adapter  806  are coupled to a keyboard  704  ( FIGS. 7 and 8 ) and a mouse  710  ( FIGS. 7 and 8 ), respectively, of computer  700  ( FIG. 7 ). While graphics adapter  824  and video controller  802  are indicated as distinct units in  FIG. 8 , video controller  802  can be integrated into graphics adapter  824 , or vice versa in other embodiments. Video controller  802  is suitable for refreshing a monitor  706  ( FIGS. 7 and 8 ) to display images on a screen  708  ( FIG. 7 ) of computer  700  ( FIG. 7 ). Disk controller  804  can control hard drive  714  ( FIGS. 7 and 8 ), USB port  712  ( FIGS. 7 and 8 ), and CD-ROM or DVD drive  716  ( FIGS. 7 and 8 ). In other embodiments, distinct units can be used to control each of these devices separately. 
     In some embodiments, network adapter  820  can comprise and/or be implemented as a WNIC (wireless network interface controller) card (not shown) plugged or coupled to an expansion port (not shown) in computer system  700  ( FIG. 7 ). In other embodiments, the WNIC card can be a wireless network card built into computer system  700  ( FIG. 7 ). A wireless network adapter can be built into computer system  700  ( FIG. 7 ) by having wireless communication capabilities integrated into the motherboard chipset (not shown), or implemented via one or more dedicated wireless communication chips (not shown), connected through a PCI (peripheral component interconnector) or a PCI express bus of computer system  700  ( FIG. 7 ) or USB port  712  ( FIG. 7 ). In other embodiments, network adapter  820  can comprise and/or be implemented as a wired network interface controller card (not shown). 
     Although many other components of computer  700  ( FIG. 7 ) are not shown, such components and their interconnection are well known to those of ordinary skill in the art. Accordingly, further details concerning the construction and composition of computer  700  and the circuit boards inside chassis  702  ( FIG. 7 ) need not be discussed herein. 
     When computer  700  in  FIG. 7  is running, program instructions stored on a USB drive in USB port  712 , on a CD-ROM or DVD in CD-ROM and/or DVD drive  716 , on hard drive  714 , or in memory  808  ( FIG. 8 ) are executed by CPU  810  ( FIG. 8 ). A portion of the program instructions, stored on these devices, can be suitable for carrying out all or at least part of the techniques described herein. In various embodiments, computer  700  can be reprogrammed with one or more modules, applications, and/or databases to convert a general purpose computer to a special purpose computer. 
     Although computer system  700  is illustrated as a desktop computer in  FIG. 7 , there can be examples where computer system  700  may take a different form factor while still having functional elements similar to those described for computer system  700 . In some embodiments, computer system  700  may comprise a single computer, a single server, or a cluster or collection of computers or servers, or a cloud of computers or servers. Typically, a cluster or collection of servers can be used when the demand on computer system  700  exceeds the reasonable capability of a single server or computer. In certain embodiments, computer system  700  may comprise a portable computer, such as a laptop computer. In certain other embodiments, computer system  700  may comprise a mobile device, such as a smartphone. For example, mobile device  120  ( FIG. 1 ) can be a mobile device, such as a smartphone. In certain additional embodiments, computer system  700  may comprise an embedded system. 
     Although secure real-time payment transactions have been described with reference to specific embodiments, it will be understood by those skilled in the art that various changes may be made without departing from the spirit or scope of the disclosure. Accordingly, the disclosure of embodiments is intended to be illustrative of the scope of the disclosure and is not intended to be limiting. It is intended that the scope of the disclosure shall be limited only to the extent required by the appended claims. For example, to one of ordinary skill in the art, it will be readily apparent that any element of  FIGS. 1-14  may be modified, and that the foregoing discussion of certain of these embodiments does not necessarily represent a complete description of all possible embodiments. For example, one or more of the procedures, processes, or activities of  FIGS. 2-6 and 9-14  may include different procedures, processes, and/or activities and be performed by many different modules, in many different orders, and/or one or more of the procedures, processes, or activities of  FIGS. 2-6 and 9-14  may include one or more of the procedures, processes, or activities of another different one of  FIGS. 2-6 and 9-14 . 
     Replacement of one or more claimed elements constitutes reconstruction and not repair. Additionally, benefits, other advantages, and solutions to problems have been described with regard to specific embodiments. The benefits, advantages, solutions to problems, and any element or elements that may cause any benefit, advantage, or solution to occur or become more pronounced, however, are not to be construed as critical, required, or essential features or elements of any or all of the claims, unless such benefits, advantages, solutions, or elements are stated in such claim. 
     Moreover, embodiments and limitations disclosed herein are not dedicated to the public under the doctrine of dedication if the embodiments and/or limitations: (1) are not expressly claimed in the claims; and (2) are or are potentially equivalents of express elements and/or limitations in the claims under the doctrine of equivalents.