BACKGROUND

Field

[0001] This disclosure relates generally to systems, methods, and products that are used for lending, and in one particular non-limiting embodiment, to a system, method, and product for real-time, anonymous peer-to-peer lending.

Technical Considerations

[0002] Existing lending systems and/or payment transfer systems do not allow for a lendee to find a lender in an efficient and/or real-time manner (e.g., during a transaction at a merchant, etc.), for example, by requiring a full credit application cycle or process (e.g., a loan origination process, etc.) to be performed before providing a loan, and do not allow for a lendee and a lender to remain anonymous with respect to one another. Therefore, it would be desirable to improve lending between lendees and lenders.

SUMMARY

[0003] Accordingly, provided are improved systems, methods, and products for lending between lendees and lenders.

[0004] According to some non-limiting embodiments or aspects, provided is a computer-implemented method for real-time, anonymous peer-to-peer lending, the method comprising: receiving, with at least one processor, request data including a request for a loan amount associated with a lendee account, wherein the request data is associated with at least one transaction at a merchant system; determining, with at least one processor, a lender account from a plurality of lender accounts based on the request data and at least one lender preference associated with the lender account; and providing, with at least one processor, an anonymous payment of the loan amount from a payment account associated with the lender account to the lendee account during processing of the at least one transaction at the merchant system.

[0005] In some non-limiting embodiments or aspects, the lender account is further determined from the plurality of lender accounts based on at least one of the following: a lendee risk score associated with the lendee account, a merchant risk score associated with the merchant system, or any combination thereof. [0006] In some non-limiting embodiments or aspects, the method further comprises: determining, with at least one processor, the lendee risk score associated with the lendee account based on transaction data associated with at least one prior transaction of a lendee associated with the lendee account and social media data associated with at least one social media account of the lendee.

[0007] In some non-limiting embodiments or aspects, the method further comprises: determining, with at least one processor, a rate associated with the loan amount based on at least one of the following: the loan amount, the lendee risk score, the merchant risk score, or any combination thereof.

[0008] In some non-limiting embodiments or aspects, the at least one lender preference includes one or more of the following: at least one threshold for the loan amount, at least one threshold for the rate of the loan amount, at least one threshold for the lendee risk score, at least one threshold for the merchant risk score, at least one threshold for a number of transactions associated with the lendee account, at least one constraint associated with a type of products or services included in the at least one transaction, at least one constraint associated with a location of the at least one transaction, or any combination thereof.

[0009] In some non-limiting embodiments or aspects, the method further comprises: providing, with at least one processor, an approval request for the loan amount and the rate to a lender device associated with the lender account without identifying the lendee account to the lender device; and receiving, with at least one processor, a response including an approval of the request for the loan amount and the rate from the lender device, wherein the anonymous payment of the loan amount from the payment account associated with the lender account to the lendee account is provided based on receiving the response including the approval from the lender device.

[0010] In some non-limiting embodiments or aspects, the method further comprises: determining, with at least one processor, based on at least one of the following: the loan amount, the rate, the at least one lender preference, the lendee risk score associated with the lendee account, the merchant risk score associated with the merchant system, or any combination thereof, an automatic approval of the of the loan amount and the rate for the lender account without providing the loan amount, the rate, the at least one lender preference, the lendee risk score associated with the lendee account, the merchant risk score associated with the merchant system, or any combination thereof to a lender device associated with the lender account, wherein the anonymous payment of the loan amount from the payment account associated with the lender account to the lendee account is provided based on determining the automatic approval for the lender account.

[0011] In some non-limiting embodiments or aspects, the method further comprises: providing, with at least one processor, an approval request for the rate associated with the loan amount to a lendee device associated with the lendee account; and receiving, with at least one processor, a response including an approval of the request for the rate associated with the loan amount from the lendee device, wherein the anonymous payment of the loan amount from the payment account associated with the lender account to the lendee account is provided based on receiving the response including the approval from the lendee device.

[0012] In some non-limiting embodiments or aspects, the method further comprises: receiving, with at least one processor, a transaction authorization request associated with the at least one transaction from the merchant system, wherein the transaction authorization request is associated with the lendee account, and wherein the anonymous payment of the loan amount from the payment account associated with the lender account to the lendee account is provided based on receiving the transaction authorization request associated with the lendee account from the merchant system.

[0013] In some non-limiting embodiments or aspects, the transaction authorization request includes transaction data associated with the at least one transaction at the merchant system, and the method further comprises: comparing, with at least one processor, at least one parameter of the request data to at least one parameter of the transaction data, wherein the anonymous payment of the loan amount from the payment account associated with the lender account to the lendee account is provided based on a result of the comparison; and determining, with at least one processor, a transaction authorization response to the transaction authorization request based on providing the anonymous payment of the loan amount to the lendee account.

[0014] According to some non-limiting embodiments or aspects, a system for real-time, anonymous peer-to-peer lending comprises: at least one processor programmed and/or configured to: receive request data including a request for a loan amount associated with a lendee account, wherein the request data is associated with at least one transaction at a merchant system; determine a lender account from a plurality of lender accounts based on the request data and at least one lender preference associated with the lender account; and provide an anonymous payment of the loan amount from a payment account associated with the lender account to the lendee account during processing of the at least one transaction at the merchant system.

[0015] In some non-limiting embodiments or aspects, the lender account is further determined from the plurality of lender accounts based on at least one of the following: a lendee risk score associated with the lendee account, a merchant risk score associated with the merchant system, or any combination thereof.

[0016] In some non-limiting embodiments or aspects, the at least one processor is further programmed and/or configured to: determine the lendee risk score associated with the lendee account based on transaction data associated with at least one prior transaction of a lendee associated with the lendee account and social media data associated with at least one social media account of the lendee.

[0017] In some non-limiting embodiments or aspects, the at least one processor is further programmed and/or configured to: determine a rate associated with the loan amount based on at least one of the following: the loan amount, the lendee risk score, the merchant risk score, or any combination thereof.

[0018] In some non-limiting embodiments or aspects, the at least one lender preference includes one or more of the following: at least one threshold for the loan amount, at least one threshold for the rate of the loan amount, at least one threshold for the lendee risk score, at least one threshold for the merchant risk score, at least one threshold for a number of transactions associated with the lendee account, at least one constraint associated with a type of products or services included in the at least one transaction, at least one constraint associated with a location of the at least one transaction, or any combination thereof.

[0019] In some non-limiting embodiments or aspects, the at least one processor is further programmed and/or configured to: provide an approval request for the loan amount and the rate to a lender device associated with the lender account without identifying the lendee account to the lender device; and receive a response including an approval of the request for the loan amount and the rate from the lender device, wherein the anonymous payment of the loan amount from the payment account associated with the lender account to the lendee account is provided based on receiving the response including the approval from the lender device.

[0020] In some non-limiting embodiments or aspects, the at least one processor is further programmed and/or configured to: determine, based on at least one of the following: the loan amount, the rate, the at least one lender preference, the lendee risk score associated with the lendee account, the merchant risk score associated with the merchant system, or any combination thereof, an automatic approval of the of the loan amount and the rate for the lender account without providing the loan amount, the rate, the at least one lender preference, the lendee risk score associated with the lendee account, the merchant risk score associated with the merchant system, or any combination thereof to a lender device associated with the lender account, wherein the anonymous payment of the loan amount from the payment account associated with the lender account to the lendee account is provided based on determining the automatic approval for the lender account.

[0021] In some non-limiting embodiments or aspects, the at least one processor is further programmed and/or configured to: provide an approval request for the rate associated with the loan amount to a lendee device associated with the lendee account; and receive a response including an approval of the request for the rate associated with the loan amount from the lendee device, wherein the anonymous payment of the loan amount from the payment account associated with the lender account to the lendee account is provided based on receiving the response including the approval from the lendee device.

[0022] In some non-limiting embodiments or aspects, the at least one processor is further programmed and/or configured to: receive a transaction authorization request associated with the at least one transaction from the merchant system, wherein the transaction authorization request is associated with the lendee account, and wherein the anonymous payment of the loan amount from the payment account associated with the lender account to the lendee account is provided based on receiving the transaction authorization request associated with the lendee account from the merchant system.

[0023] In some non-limiting embodiments or aspects, the transaction authorization request includes transaction data associated with the at least one transaction at the merchant system, and the at least one processor is further programmed and/or configured to: compare at least one parameter of the request data to at least one parameter of the transaction data, wherein the anonymous payment of the loan amount from the payment account associated with the lender account to the lendee account is provided based on a result of the comparison; and determine a transaction authorization response to the transaction authorization request based on providing the anonymous payment of the loan amount to the lendee account.

[0024] According to some non-limiting embodiments or aspects, provided is a computer program product for real-time, anonymous peer-to-peer lending, comprising at least one non-transitory computer-readable medium including program instructions that, when executed by at least one processor, cause the at least one processor to: receive request data including a request for a loan amount associated with a lendee account, wherein the request data is associated with at least one transaction at a merchant system; determine a lender account from a plurality of lender accounts based on the request data and at least one lender preference associated with the lender account; and provide an anonymous payment of the loan amount from a payment account associated with the lender account to the lendee account during processing of the at least one transaction at the merchant system.

[0025] Further embodiments or aspects are set forth in the following numbered clauses:

[0026] Clause 1. A computer-implemented method for real-time, anonymous peer-to-peer lending, the method comprising: receiving, with at least one processor, request data including a request for a loan amount associated with a lendee account, wherein the request data is associated with at least one transaction at a merchant system; determining, with at least one processor, a lender account from a plurality of lender accounts based on the request data and at least one lender preference associated with the lender account; and providing, with at least one processor, an anonymous payment of the loan amount from a payment account associated with the lender account to the lendee account during processing of the at least one transaction at the merchant system.

[0027] Clause 2. The computer-implemented method of clause 1 , wherein the lender account is further determined from the plurality of lender accounts based on at least one of the following: a lendee risk score associated with the lendee account, a merchant risk score associated with the merchant system, or any combination thereof. [0028] Clause 3. The computer-implemented method of clauses 1 or 2, further comprising: determining, with at least one processor, the lendee risk score associated with the lendee account based on transaction data associated with at least one prior transaction of a lendee associated with the lendee account and social media data associated with at least one social media account of the lendee.

[0029] Clause 4. The computer-implemented method of any of clauses 1-3, further comprising: determining, with at least one processor, a rate associated with the loan amount based on at least one of the following: the loan amount, the lendee risk score, the merchant risk score, or any combination thereof.

[0030] Clause 5. The computer-implemented method of any of clauses 1-4, wherein the at least one lender preference includes one or more of the following: at least one threshold for the loan amount, at least one threshold for the rate of the loan amount, at least one threshold for the lendee risk score, at least one threshold for the merchant risk score, at least one threshold for a number of transactions associated with the lendee account, at least one constraint associated with a type of products or services included in the at least one transaction, at least one constraint associated with a location of the at least one transaction, or any combination thereof.

[0031] Clause 6. The computer-implemented method of any of clauses 1-5, further comprising: providing, with at least one processor, an approval request for the loan amount and the rate to a lender device associated with the lender account without identifying the lendee account to the lender device; and receiving, with at least one processor, a response including an approval of the request for the loan amount and the rate from the lender device, wherein the anonymous payment of the loan amount from the payment account associated with the lender account to the lendee account is provided based on receiving the response including the approval from the lender device.

[0032] Clause 7. The computer-implemented method of any of clauses 1-6, further comprising: determining, with at least one processor, based on at least one of the following: the loan amount, the rate, the at least one lender preference, the lendee risk score associated with the lendee account, the merchant risk score associated with the merchant system, or any combination thereof, an automatic approval of the of the loan amount and the rate for the lender account without providing the loan amount, the rate, the at least one lender preference, the lendee risk score associated with the lendee account, the merchant risk score associated with the merchant system, or any combination thereof to a lender device associated with the lender account, wherein the anonymous payment of the loan amount from the payment account associated with the lender account to the lendee account is provided based on determining the automatic approval for the lender account.

[0033] Clause 8. The computer-implemented method of any of clauses 1-7, further comprising: providing, with at least one processor, an approval request for the rate associated with the loan amount to a lendee device associated with the lendee account; and receiving, with at least one processor, a response including an approval of the request for the rate associated with the loan amount from the lendee device, wherein the anonymous payment of the loan amount from the payment account associated with the lender account to the lendee account is provided based on receiving the response including the approval from the lendee device.

[0034] Clause 9. The computer-implemented method of any of clauses 1-8, further comprising: receiving, with at least one processor, a transaction authorization request associated with the at least one transaction from the merchant system, wherein the transaction authorization request is associated with the lendee account, and wherein the anonymous payment of the loan amount from the payment account associated with the lender account to the lendee account is provided based on receiving the transaction authorization request associated with the lendee account from the merchant system.

[0035] Clause 10. The computer-implemented method of any of clauses 1-9, wherein the transaction authorization request includes transaction data associated with the at least one transaction at the merchant system, the method further comprising: comparing, with at least one processor, at least one parameter of the request data to at least one parameter of the transaction data, wherein the anonymous payment of the loan amount from the payment account associated with the lender account to the lendee account is provided based on a result of the comparison; and determining, with at least one processor, a transaction authorization response to the transaction authorization request based on providing the anonymous payment of the loan amount to the lendee account.

[0036] Clause 11. A system for real-time, anonymous peer-to-peer lending, the system comprising: at least one processor programmed and/or configured to: receive request data including a request for a loan amount associated with a lendee account, wherein the request data is associated with at least one transaction at a merchant system; determine a lender account from a plurality of lender accounts based on the request data and at least one lender preference associated with the lender account; and provide an anonymous payment of the loan amount from a payment account associated with the lender account to the lendee account during processing of the at least one transaction at the merchant system.

[0037] Clause 12. The system of clause 11 , wherein the lender account is further determined from the plurality of lender accounts based on at least one of the following: a lendee risk score associated with the lendee account, a merchant risk score associated with the merchant system, or any combination thereof.

[0038] Clause 13. The system of clauses 11 or 12, wherein the at least one processor is further programmed and/or configured to: determine the lendee risk score associated with the lendee account based on transaction data associated with at least one prior transaction of a lendee associated with the lendee account and social media data associated with at least one social media account of the lendee.

[0039] Clause 14. The system of any of clauses 11 -13, wherein the at least one processor is further programmed and/or configured to: determine a rate associated with the loan amount based on at least one of the following: the loan amount, the lendee risk score, the merchant risk score, or any combination thereof.

[0040] Clause 15. The system of any of clauses 11-14, wherein the at least one lender preference includes one or more of the following: at least one threshold for the loan amount, at least one threshold for the rate of the loan amount, at least one threshold for the lendee risk score, at least one threshold for the merchant risk score, at least one threshold for a number of transactions associated with the lendee account, at least one constraint associated with a type of products or services included in the at least one transaction, at least one constraint associated with a location of the at least one transaction, or any combination thereof.

[0041] Clause 16. The system of any of clauses 11 -15, wherein the at least one processor is further programmed and/or configured to: provide an approval request for the loan amount and the rate to a lender device associated with the lender account without identifying the lendee account to the lender device; and receive a response including an approval of the request for the loan amount and the rate from the lender device, wherein the anonymous payment of the loan amount from the payment account associated with the lender account to the lendee account is provided based on receiving the response including the approval from the lender device.

[0042] Clause 17. The system of any of clauses 11 -16, wherein the at least one processor is further programmed and/or configured to: determine, based on at least one of the following: the loan amount, the rate, the at least one lender preference, the lendee risk score associated with the lendee account, the merchant risk score associated with the merchant system, or any combination thereof, an automatic approval of the of the loan amount and the rate for the lender account without providing the loan amount, the rate, the at least one lender preference, the lendee risk score associated with the lendee account, the merchant risk score associated with the merchant system, or any combination thereof to a lender device associated with the lender account, wherein the anonymous payment of the loan amount from the payment account associated with the lender account to the lendee account is provided based on determining the automatic approval for the lender account.

[0043] Clause 18. The system of any of clauses 11 -17, wherein the at least one processor is further programmed and/or configured to: provide an approval request for the rate associated with the loan amount to a lendee device associated with the lendee account; and receive a response including an approval of the request for the rate associated with the loan amount from the lendee device, wherein the anonymous payment of the loan amount from the payment account associated with the lender account to the lendee account is provided based on receiving the response including the approval from the lendee device.

[0044] Clause 19. The system of any of clauses 11 -18, wherein the at least one processor is further programmed and/or configured to: receive a transaction authorization request associated with the at least one transaction from the merchant system, wherein the transaction authorization request is associated with the lendee account, and wherein the anonymous payment of the loan amount from the payment account associated with the lender account to the lendee account is provided based on receiving the transaction authorization request associated with the lendee account from the merchant system.

[0045] Clause 20. The system of any of clauses 11-19, wherein the transaction authorization request includes transaction data associated with the at least one transaction at the merchant system, and wherein the at least one processor is further programmed and/or configured to: compare at least one parameter of the request data to at least one parameter of the transaction data, wherein the anonymous payment of the loan amount from the payment account associated with the lender account to the lendee account is provided based on a result of the comparison; and determine a transaction authorization response to the transaction authorization request based on providing the anonymous payment of the loan amount to the lendee account.

[0046] These and other features and characteristics of the present disclosure, as well as the methods of operation and functions of the related elements of structures and the combination of parts and economies of manufacture, will become more apparent upon consideration of the following description and the appended claims with reference to the accompanying drawings, all of which form a part of this specification, wherein like reference numerals designate corresponding parts in the various figures. It is to be expressly understood, however, that the drawings are for the purpose of illustration and description only and are not intended as a definition of limits. As used in the specification and the claims, the singular form of“a,”“an,” and “the” include plural referents unless the context clearly dictates otherwise.

BRIEF DESCRIPTION OF THE DRAWINGS

[0047] Additional advantages and details are explained in greater detail below with reference to the exemplary embodiments or aspects that are illustrated in the accompanying schematic figures, in which:

[0048] FIG. 1 is a diagram of a non-limiting embodiment or aspect of an environment in which systems, devices, products, apparatus, and/or methods, described herein;

[0049] FIG. 2 is a diagram of a non-limiting embodiment or aspect of components of one or more devices and/or one or more systems of FIG. 1 ;

[0050] FIG. 3 is a flowchart of a non-limiting embodiment or aspect of a process for real-time, anonymous peer-to-peer lending;

[0051] FIG. 4 is a flowchart of a non-limiting embodiment or aspect of a process for real-time, anonymous peer-to-peer lending;

[0052] FIG. 5 is a flowchart of a non-limiting embodiment or aspect of a process for real-time, anonymous peer-to-peer lending; and

[0053] FIG. 6 is flow diagram of an implementation of a non-limiting embodiment or aspect of one or more of the processes shown in FIGS. 3-5. DESCRIPTION

[0054] It is to be understood that the present disclosure may assume various alternative variations and step sequences, except where expressly specified to the contrary. It is also to be understood that the specific devices and processes illustrated in the attached drawings, and described in the following specification, are simply exemplary and non-limiting embodiments or aspects. Hence, specific dimensions and other physical characteristics related to the embodiments or aspects disclosed herein are not to be considered as limiting.

[0055] No aspect, component, element, structure, act, step, function, instruction, and/or the like used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles“a” and“an” are intended to include one or more items, and may be used interchangeably with“one or more” and“at least one.” Furthermore, as used herein, the term“set” is intended to include one or more items (e.g., related items, unrelated items, a combination of related and unrelated items, etc.) and may be used interchangeably with“one or more” or“at least one.” Where only one item is intended, the term“one” or similar language is used. Also, as used herein, the terms“has,”“have,”“having,” or the like are intended to be open-ended terms. Further, the phrase“based on” is intended to mean“based at least partially on” unless explicitly stated otherwise.

[0056] As used herein, the terms“communication” and“communicate” refer to the receipt or transfer of one or more signals, messages, commands, or other type of data. For one unit (e.g., any device, system, or component thereof) to be in communication with another unit means that the one unit is able to directly or indirectly receive data from and/or transmit data to the other unit. This may refer to a direct or indirect connection that is wired and/or wireless in nature. Additionally, two units may be in communication with each other even though the data transmitted may be modified, processed, relayed, and/or routed between the first and second unit. For example, a first unit may be in communication with a second unit even though the first unit passively receives data and does not actively transmit data to the second unit. As another example, a first unit may be in communication with a second unit if an intermediary unit processes data from one unit and transmits processed data to the second unit. It will be appreciated that numerous other arrangements are possible. [0057] As used herein, the term“transaction service provider” may refer to an entity that receives transaction authorization requests from merchants or other entities and provides guarantees of payment, in some cases through an agreement between the transaction service provider and an issuer institution. The terms “transaction service provider” and“transaction service provider system” may also refer to one or more computer systems operated by or on behalf of a transaction service provider, such as a transaction processing system executing one or more software applications. A transaction processing system may include one or more server computers with one or more processors and, in some non-limiting embodiments or aspects, may be operated by or on behalf of a transaction service provider.

[0058] As used herein, the term“account identifier” may include one or more primary account numbers (PAN), tokens, or other identifiers (e.g., a globally unique identifier (GUID), a universally unique identifier (UUID), etc.) associated with a customer account of a user (e.g., a customer, a consumer, a lendee, a lender, and/or the like). The term“token” may refer to an identifier that is used as a substitute or replacement identifier for an original account identifier, such as a PAN. Account identifiers may be alphanumeric or any combination of characters and/or symbols. Tokens may be associated with a PAN or other original account identifier in one or more databases such that they can be used to conduct a transaction without directly using the original account identifier. In some examples, an original account identifier, such as a PAN, may be associated with a plurality of tokens for different individuals or purposes.

[0059] As used herein, the terms“issuer institution,”“portable financial device issuer,”“issuer,” or“issuer bank” may refer to one or more entities that provide one or more accounts to a user (e.g., a customer, a consumer, an entity, an organization, and/or the like) for conducting transactions (e.g., payment transactions), such as initiating credit card payment transactions and/or debit card payment transactions. For example, an issuer institution may provide an account identifier, such as a PAN, to a user that uniquely identifies one or more accounts associated with that user. The account identifier may be embodied on a portable financial device, such as a physical financial instrument (e.g., a payment card), and/or may be electronic and used for electronic payments. In some non-limiting embodiments or aspects, an issuer institution may be associated with a bank identification number (BIN) that uniquely identifies the issuer institution. As used herein“issuer institution system” may refer to one or more computer systems operated by or on behalf of an issuer institution, such as a server computer executing one or more software applications. For example, an issuer institution system may include one or more authorization servers for authorizing a payment transaction.

[0060] As used herein, the term“merchant” may refer to an individual or entity that provides products and/or services, or access to products and/or services, to customers based on a transaction, such as a payment transaction. The term “merchant” or“merchant system” may also refer to one or more computer systems operated by or on behalf of a merchant, such as a server computer executing one or more software applications. A“point-of-sale (POS) system,” as used herein, may refer to one or more computers and/or peripheral devices used by a merchant to engage in payment transactions with customers, including one or more card readers, near-field communication (NFC) receivers, RFID receivers, and/or other contactless transceivers or receivers, contact-based receivers, payment terminals, computers, servers, input devices, and/or other like devices that can be used to initiate a payment transaction.

[0061] As used herein, the term “mobile device” may refer to one or more portable electronic devices configured to communicate with one or more networks. As an example, a mobile device may include a cellular phone (e.g., a smartphone or standard cellular phone), a portable computer (e.g., a tablet computer, a laptop computer, etc.), a wearable device (e.g., a watch, pair of glasses, lens, clothing, and/or the like), a personal digital assistant (PDA), and/or other like devices. The terms“client device” and“user device,” as used herein, refer to any electronic device that is configured to communicate with one or more servers or remote devices and/or systems. A client device or user device may include a mobile device, a network- enabled appliance (e.g., a network-enabled television, refrigerator, thermostat, and/or the like), a computer, a POS system, and/or any other device or system capable of communicating with a network.

[0062] As used herein, the term“computing device” may refer to one or more electronic devices that are configured to directly or indirectly communicate with or over one or more networks. The computing device may be a mobile device, a desktop computer, or the like. Furthermore, the term“computer” may refer to any computing device that includes the necessary components to receive, process, and output data, and normally includes a display, a processor, a memory, an input device, and a network interface. An“application” or“application program interface” (API) refers to computer code or other data sorted on a computer-readable medium that may be executed by a processor to facilitate the interaction between software components, such as a client-side front-end and/or server-side back-end for receiving data from the client. An“interface” refers to a generated display, such as one or more graphical user interfaces (GUIs) with which a user may interact, either directly or indirectly (e.g., through a keyboard, mouse, touchscreen, etc.).

[0063] As used herein, the terms “electronic wallet” and “electronic wallet application” refer to one or more electronic devices and/or software applications configured to initiate and/or conduct payment transactions. For example, an electronic wallet may include a mobile device executing an electronic wallet application, and may further include server-side software and/or databases for maintaining and providing transaction data to the mobile device. An “electronic wallet provider” may include an entity that provides and/or maintains an electronic wallet for a customer, such as Google Wallet™, Android Pay®, Apple Pay®, Samsung Pay®, and/or other like electronic payment systems. In some non-limiting examples, an issuer bank may be an electronic wallet provider.

[0064] As used herein, the terms“peer-to-peer payment transfer service” and “peer-to-peer payment transfer application” refer to one or more electronic devices and/or software applications configured to initiate and/or conduct person-to-person (e.g., account-to-account, etc.) transfers of payments or funds. For example, a peer- to-peer payment transfer service may include mobile devices executing a peer-to- peer payment transfer application, and may further include server-side software and/or databases (e.g., a lendee database, a lender database, etc.) for maintaining and providing request data and transaction data to the mobile devices. A“peer-to- peer payment transfer service provider” may include an entity that provides and/or maintains a peer-to-peer payment transfer service for customers, such as Visa Direct ^® , and/or other like peer-to-peer payment transfer services. In some nonlimiting examples, a transaction service provider may be a peer-to-peer payment transfer service provider.

[0065] As used herein, the term “portable financial device” may refer to a payment card (e.g., a credit or debit card), a gift card, a smartcard, smart media, a payroll card, a healthcare card, a wrist band, a machine-readable medium containing account information, a keychain device or fob, an RFID transponder, a retailer discount or loyalty card, a mobile device executing an electronic wallet application, a PDA, a security card, an access card, a wireless terminal, and/or a transponder, as examples. The portable financial device may include a volatile or a non-volatile memory to store information, such as an account identifier and/or a name of the account holder.

[0066] As used herein, the term“server” may refer to or include one or more processors or computers, storage devices, or similar computer arrangements that are operated by or facilitate communication and processing for multiple parties in a network environment, such as the Internet, although it will be appreciated that communication may be facilitated over one or more public or private network environments and that various other arrangements are possible. Further, multiple computers, e.g., servers, or other computerized devices, such as POS devices, directly or indirectly communicating in the network environment may constitute a “system,” such as a merchant’s POS system.

[0067] As used herein, the term“acquirer” may refer to an entity licensed by the transaction service provider and/or approved by the transaction service provider to originate transactions using a portable financial device of the transaction service provider. Acquirer may also refer to one or more computer systems operated by or on behalf of an acquirer, such as a server computer executing one or more software applications (e.g.,“acquirer server”). An“acquirer” may be a merchant bank, or in some cases, the merchant system may be the acquirer. The transactions may include original credit transactions (OCTs) and account funding transactions (AFTs). The acquirer may be authorized by the transaction service provider to sign merchants of service providers to originate transactions using a portable financial device of the transaction service provider. The acquirer may contract with payment facilitators to enable the facilitators to sponsor merchants. The acquirer may monitor compliance of the payment facilitators in accordance with regulations of the transaction service provider. The acquirer may conduct due diligence of payment facilitators and ensure that proper due diligence occurs before signing a sponsored merchant. Acquirers may be liable for all transaction service provider programs that they operate or sponsor. Acquirers may be responsible for the acts of its payment facilitators and the merchants it or its payment facilitators sponsor. [0068] As used herein, the term“payment gateway” may refer to an entity and/or a payment processing system operated by or on behalf of such an entity (e.g., a merchant service provider, a payment service provider, a payment facilitator, a payment facilitator that contracts with an acquirer, a payment aggregator, and/or the like), which provides payment services (e.g., transaction service provider payment services, payment processing services, and/or the like) to one or more merchants. The payment services may be associated with the use of portable financial devices managed by a transaction service provider. As used herein, the term“payment gateway system” may refer to one or more computer systems, computer devices, servers, groups of servers, and/or the like, operated by or on behalf of a payment gateway.

[0069] Provided are systems, methods, and products for improving lending between lendees and lenders by providing real-time, anonymous peer-to-peer lending. For example, existing computer systems have no mechanism for matching a lendee and a lender (e.g., lendees and lenders that are remote from each other, etc.) in an efficient and/or real-time manner (e.g., during lendee interaction with a merchant, during processing of a transaction at a merchant system, during processing of a transaction in a transaction processing network, etc.) and no mechanism for enabling the lendee and the lender to remain anonymous with respect to one another.

[0070] Non-limiting embodiment or aspects of the present disclosure are directed to systems, methods, and computer program products for real-time, anonymous peer-to-peer lending that receive request data including a request for a loan amount associated with a lendee account, the request data being associated with at least one transaction at a merchant system; determine a lender account from a plurality of lender accounts based on the request data and at least one lender preference associated with the lender account; and provide an anonymous payment of the loan amount from a payment account associated with the lender account to the lendee account during processing of the at least one transaction at the merchant system. For example, a centralized system (e.g., a transaction service provider system, etc.) can alter an existing transaction processing network for processing a transaction by communicating with a lendee and/or a lender device and/or providing an anonymous payment from a payment account or instrument associated with a lender account (e.g., from a payment account or instrument that is outside an existing transaction flow or communication channel of the transaction processing network, etc.) to a lendee account during processing of the transaction.

[0071] In this way, embodiments or aspects of the present disclosure may provide for the following: (i) more efficient and/or real-time matching of a lendee and a lender (e.g., matching a lendee and a lender during processing of a transaction of the lendee at a merchant, providing an anonymous payment from a lender to a lendee account during processing of the transaction, etc.), (ii) providing a payment from a lender for a loan amount of a loan before and/or without performing a full credit application cycle or process for the loan, (iii) enabling a lendee and a lender to remain anonymous with respect to one another, (iv) setting more flexible loan terms (e.g., transaction amounts, transaction numbers, transaction types, loan interest rates, credit scores, etc.) between lenders and lendees, and/or the like. Accordingly, lenders can lend money for specific amounts (e.g., relatively smaller amounts, such as $50, $100, and/or the like, etc.) for specific products or services in real-time to remote lendees for specific fees (e.g., relatively smaller fees, etc.) without recurring penalties for credit cards and/or the like, and lendees that might otherwise be incapable of securing a loan (e.g., lendees that request smaller loan amounts, underprivileged lendees, lendees without sufficient credit scores, etc.) can be served by lenders that are taking a relatively smaller risk to help these lendees improve their credit standings and/or financial lives.

[0072] Referring now to FIG. 1 , FIG. 1 is a diagram of an example environment 100 in which devices, systems, methods, and/or products described herein, may be implemented. As shown in FIG. 1 , environment 100 includes transaction processing network 101 , which can include merchant system 102, payment gateway 104, acquirer system 106, transaction service provider system 108, and/or issuer system 110, lendee device 112, lender device 114, and/or communication network 116. Transaction processing network 101 , merchant system 102, payment gateway 104, acquirer system 106, transaction service provider system 108, issuer system 110, lendee device 112, and/or lender device 114 may interconnect (e.g., establish a connection to communicate) via wired connections, wireless connections, or a combination of wired and wireless connections.

[0073] Merchant system 102 may include one or more devices capable of receiving information from payment gateway 104, acquirer system 106, transaction service provider system 108, issuer system 110, lendee device 112, and/or lender device 114 via communication network 116 and/or communicating information to payment gateway 104, acquirer system 106, transaction service provider system 108, issuer system 110, lendee device 112, and/or lender device 114 via communication network 116. Merchant system 102 may include a device capable of receiving information from lender device 112 via a communication connection (e.g., an NFC communication connection, an RFID communication connection, a Bluetooth® communication connection, and/or the like) with lendee device 112, and/or communicating information to lendee device 112 via the communication connection. For example, merchant system 102 may include a computing device, such as a server, a group of servers, a client device, a group of client devices, and/or other like devices. In some non-limiting embodiments or aspects, merchant system 102 may be associated with a merchant as described herein. In some non-limiting embodiments or aspects, merchant system 102 may include one or more devices, such as computers, computer systems, and/or peripheral devices capable of being used by a merchant to conduct a payment transaction with a user. For example, merchant system 102 may include a POS device and/or a POS system.

[0074] Payment gateway 104 may include one or more devices capable of receiving information from merchant system 102, acquirer system 106, transaction service provider system 108, issuer system 110, lendee device 112, and/or lender device 114 via communication network 116 and/or communicating information to merchant system 102, acquirer system 106, transaction service provider system 108, issuer system 110, lendee device 112, and/or lender device 114 via communication network 116. For example, payment gateway 104 may include a computing device, such as a server, a group of servers, and/or other like devices. In some non-limiting embodiments or aspects, payment gateway 104 is associated with a payment gateway as described herein.

[0075] Acquirer system 106 may include one or more devices capable of receiving information from merchant system 102, payment gateway 104, transaction service provider system 108, issuer system 110, lendee device 112, and/or lender device 114 via communication network 116 and/or communicating information to merchant system 102, payment gateway 104, transaction service provider system 108, issuer system 110, lendee device 112, and/or lender device 114 via communication network 116. For example, acquirer system 106 may include a computing device, such as a server, a group of servers, and/or other like devices. In some non-limiting embodiments or aspects, acquirer system 106 may be associated with an acquirer as described herein.

[0076] Transaction service provider system 108 may include one or more devices capable of receiving information from merchant system 102, payment gateway 104, acquirer system 106, issuer system 110, lendee device 112, and/or lender device 114 via communication network 116 and/or communicating information to merchant system 102, payment gateway 104, acquirer system 106, issuer system 110, lendee device 112, and/or lender device 114 via communication network 116. For example, transaction service provider system 108 may include a computing device, such as a server (e.g., a transaction processing server), a group of servers, and/or other like devices. In some non-limiting embodiments or aspects, transaction service provider system 108 may be associated with a transaction service provider as described herein. In some non-limiting embodiments or aspects, transaction service provider system 108 may be a peer-to-peer payment transfer service provider.

[0077] Issuer system 110 may include one or more devices capable of receiving information from merchant system 102, payment gateway 104, acquirer system 106, transaction service provider system 108, lendee device 112, and/or lender device 114 via communication network 116 and/or communicating information to merchant system 102, payment gateway 104, acquirer system 106, transaction service provider system 108, lendee device 112, and/or lender device 114 via communication network 116. For example, issuer system 110 may include a computing device, such as a server, a group of servers, and/or other like devices. In some non-limiting embodiments or aspects, issuer system 110 may be associated with an issuer institution as described herein. For example, issuer system 110 may be associated with an issuer institution that issued a payment account or instrument (e.g., a credit account, a debit account, a credit card, a debit card, etc.) to a user (e.g., a lendee associated with lendee device 112, a lender associated with lender device 114, etc.).

[0078] In some non-limiting embodiments or aspects, transaction processing network 101 includes a plurality of systems in a communication path for processing a transaction. For example, transaction processing network 101 can include merchant system 102, payment gateway 104, acquirer system 106, transaction service provider system 108, and/or issuer system 110 in a communication path (e.g., a communication path, a communication channel, a communication network, etc.) for processing an electronic payment transaction. As an example, transaction processing network 101 can process (e.g., initiate, conduct, authorize, etc.) an electronic payment transaction via the communication path between merchant system 102, payment gateway 104, acquirer system 106, transaction service provider system 108, and/or issuer system 110.

[0079] Lendee device 112 may include one or more devices capable of receiving information from merchant system 102, payment gateway 104, acquirer system 106, transaction service provider system 108, issuer system 110, and/or lender device 114 via communication network 116 and/or communicating information to merchant system 102, payment gateway 104, acquirer system 106, transaction service provider system 108, issuer system 110, and/or lender device 114 via communication network 116. For example, lendee device 112 may include a client device and/or the like. In some non-limiting embodiments or aspects, lendee device 112 may be capable of receiving information (e.g., from merchant system 102) via a short range wireless communication connection (e.g., an NFC communication connection, an RFID communication connection, a Bluetooth® communication connection, and/or the like), and/or communicating information (e.g., to merchant system 102) via a short range wireless communication connection. In some nonlimiting embodiments or aspects, lendee device 112 may include an application associated with lendee device 112, such as an application stored on lendee device 112, a mobile application (e.g., a mobile device application, a native application for a mobile device, a mobile cloud application for a mobile device, an electronic wallet application, a peer-to-peer payment transfer application, and/or the like) stored and/or executed on lendee device 112. In some non-limiting embodiments or aspects, a lendee is a user associated with lendee device 112 and/or a lendee account in a peer-to-peer payment transfer service (e.g., an account identifier that uniquely identifies a lendee account in the peer-to-peer payment transfer service, etc.). For example, a lendee may be a user that seeks to receive a loan.

[0080] Lender device 114 may include one or more devices capable of receiving information from merchant system 102, payment gateway 104, acquirer system 106, transaction service provider system 108, issuer system 110, and/or lendee device 112 via communication network 116 and/or communicating information to merchant system 102, payment gateway 104, acquirer system 106, transaction service provider system 108, issuer system 110, and/or lendee device 112 via communication network 116. For example, lender device 114 may include a client device and/or the like. In some non-limiting embodiments or aspects, lender device 114 may include an application associated with lender device 114, such as an application stored on lender device 114, a mobile application (e.g., a mobile device application, a native application for a mobile device, a mobile cloud application for a mobile device, an electronic wallet application, a peer-to-peer payment transfer application, and/or the like) stored and/or executed on lender device 114. In some non-limiting embodiments or aspects, a lender is a user associated with lender device 114 and/or a lender account in a peer-to-peer payment transfer service (e.g., an account identifier that uniquely identifies a lender account in the peer-to-peer payment transfer service, etc.). For example, a lender may be a user that provides a loan to a lendee based on certain criteria and/or parameters.

[0081] Communication network 116 may include one or more wired and/or wireless networks. For example, communication network 116 may include a cellular network (e.g., a long-term evolution (LTE) network, a third generation (3G) network, a fourth generation (4G) network, a code division multiple access (CDMA) network, etc.), a public land mobile network (PLMN), a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), a telephone network (e.g., the public switched telephone network (PSTN)), a private network, an ad hoc network, an intranet, the Internet, a fiber optic-based network, a cloud computing network, and/or the like, and/or a combination of these or other types of networks.

[0082] The number and arrangement of devices, systems, and networks shown in FIG. 1 are provided as an example. There may be additional devices, systems, and/or networks, fewer devices, systems, and/or networks, different devices, systems, and/or networks, or differently arranged devices, systems, and/or networks than those shown in FIG. 1. Furthermore, two or more devices and/or systems shown in FIG. 1 may be implemented within a single device and/or system, or a single device and/or system shown in FIG. 1 may be implemented as multiple, distributed devices and/or systems. Additionally or alternatively, a set of devices and/or systems (e.g., one or more devices or systems) of environment 100 may perform one or more functions described as being performed by another set of devices or systems of environment 100.

[0083] Referring now to FIG. 2, FIG. 2 is a diagram of example components of a device 200. Device 200 may correspond to one or more devices of transaction processing network 101 , one or more devices of merchant system 102, one or more devices of payment gateway 104, one or more devices of acquirer system 106, one or more devices of transaction service provider system 108, one or more devices of issuer system 110, one or more devices of lendee device 112, one or more devices of lender device 114, and/or one or more devices of communication network 116. In some non-limiting embodiments or aspects, one or more devices of transaction processing network 101 , one or more devices of merchant system 102, one or more devices of payment gateway 104, one or more devices of acquirer system 106, one or more devices of transaction service provider system 108, one or more devices of issuer system 110, one or more devices of lendee device 112, one or more devices of lender device 114, and/or one or more devices of communication network 116 can include at least one device 200 and/or at least one component of device 200. As shown in FIG. 2, device 200 may include a bus 202, a processor 204, memory 206, a storage component 208, an input component 210, an output component 212, and a communication interface 214.

[0084] Bus 202 may include a component that permits communication among the components of device 200. In some non-limiting embodiments or aspects, processor 204 may be implemented in hardware, firmware, or a combination of hardware and software. For example, processor 204 may include a processor (e.g., a central processing unit (CPU), a graphics processing unit (GPU), an accelerated processing unit (APU), etc.), a microprocessor, a digital signal processor (DSP), and/or any processing component (e.g., a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), etc.) that can be programmed to perform a function. Memory 206 may include random access memory (RAM), read only memory (ROM), and/or another type of dynamic or static storage device (e.g., flash memory, magnetic memory, optical memory, etc.) that stores information and/or instructions for use by processor 204.

[0085] Storage component 208 may store information and/or software related to the operation and use of device 200. For example, storage component 208 may include a hard disk (e.g., a magnetic disk, an optical disk, a magneto-optic disk, a solid state disk, etc.), a compact disc (CD), a digital versatile disc (DVD), a floppy disk, a cartridge, a magnetic tape, and/or another type of computer-readable medium, along with a corresponding drive. [0086] Input component 210 may include a component that permits device 200 to receive information, such as via user input (e.g., a touch screen display, a keyboard, a keypad, a mouse, a button, a switch, a microphone, etc.). Additionally or alternatively, input component 210 may include a sensor for sensing information (e.g., a global positioning system (GPS) component, an accelerometer, a gyroscope, an actuator, etc.). Output component 212 may include a component that provides output information from device 200 (e.g., a display, a speaker, one or more light- emitting diodes (LEDs), etc.).

[0087] Communication interface 214 may include a transceiver-like component (e.g., a transceiver, a separate receiver and transmitter, etc.) that enables device 200 to communicate with other devices, such as via a wired connection, a wireless connection, or a combination of wired and wireless connections. Communication interface 214 may permit device 200 to receive information from another device and/or provide information to another device. For example, communication interface 214 may include an Ethernet interface, an optical interface, a coaxial interface, an infrared interface, a radio frequency (RF) interface, a universal serial bus (USB) interface, a Wi-Fi® interface, a cellular network interface, and/or the like.

[0088] Device 200 may perform one or more processes described herein. Device 200 may perform these processes based on processor 204 executing software instructions stored by a computer-readable medium, such as memory 206 and/or storage component 208. A computer-readable medium (e.g., a non-transitory computer-readable medium) is defined herein as a non-transitory memory device. A memory device includes memory space located inside of a single physical storage device or memory space spread across multiple physical storage devices.

[0089] Software instructions may be read into memory 206 and/or storage component 208 from another computer-readable medium or from another device via communication interface 214. When executed, software instructions stored in memory 206 and/or storage component 208 may cause processor 204 to perform one or more processes described herein. Additionally or alternatively, hardwired circuitry may be used in place of or in combination with software instructions to perform one or more processes described herein. Thus, embodiments or aspects described herein are not limited to any specific combination of hardware circuitry and software. [0090] Memory 206 and/or storage component 208 may include data storage or one or more data structures (e.g., a database, a lendee database, a lender database, etc.). Device 200 may be capable of receiving information from, storing information in, communicating information to, or searching information stored in the data storage or one or more data structures in memory 206 and/or storage component 208.

[0091] The number and arrangement of components shown in FIG. 2 are provided as an example. In some non-limiting embodiments or aspects, device 200 may include additional components, fewer components, different components, or differently arranged components than those shown in FIG. 2. Additionally or alternatively, a set of components (e.g., one or more components) of device 200 may perform one or more functions described as being performed by another set of components of device 200.

[0092] Referring now to FIG. 3, FIG. 3 is a flowchart of a non-limiting embodiment or aspect of a process 300 for real-time, anonymous peer-to-peer lending. In some non-limiting embodiments or aspects, one or more of the steps of process 300 may be performed (e.g., completely, partially, etc.) by transaction service provider system 108 (e.g., one or more devices of transaction service provider system 108). In some non-limiting embodiments or aspects, one or more of the steps of process 300 may be performed (e.g., completely, partially, etc.) by another device or a group of devices separate from or including transaction service provider system 108, such as merchant system 102 (e.g., one or more devices of merchant system 102), payment gateway 104 (e.g., one or more devices of payment gateway 104), acquirer system 106 (e.g., one or more devices of acquirer system 106), issuer system 110 (e.g., one or more devices of issuer system 110), lendee device 112, and/or lender device 114.

[0093] As shown in FIG. 3, at step 302, process 300 includes providing a lendee account. For example, transaction service provider system 108 provides (e.g., determines, registers, generates, creates, opens, stores, maintains, updates, etc.) a lendee account associated with a lendee. As an example, transaction service provider system 108 provides an account identifier that uniquely identifies a lendee account associated with a lendee. In such an example, the account identifier can include a GUID and/or a PAN that identifies the lendee account.

[0094] In some non-limiting embodiments or aspects, transaction service provider system 108 can provide a plurality of lendee accounts associated with a plurality of lendees. For example, one or more lendee accounts of the plurality of lendee accounts can be different from one or more other lendee accounts of the plurality of lendee accounts and/or one or more lendees of the plurality of lendees can be different from one or more other lendees of the plurality of lendees. As an example, transaction service provider system 108 can provide a plurality of different account identifiers that uniquely identifier a plurality of different lendee accounts.

[0095] In some non-limiting embodiments or aspects, transaction service provider system 108 provides a lendee account in response to a request for a lendee account from lendee device 112. For example, transaction service provider system 108 can receive, from lendee device 112 (e.g., via a peer-to-peer payment transfer service application executed by lendee device 112, etc.), a request for a lendee account that includes user data, such as personally identifiable information (Pll) or data (e.g., a name, a social security number, etc.) that can be used to uniquely identify, contact, and/or locate a single person or user (e.g., a lendee, etc.), debts, balances, or the like, and provide a lendee account associated with the lendee in response to the request. As an example, transaction service provider system 108 can store an account identifier that identifies the lendee account associated with the lendee in a lendee database and/or provide the account identifier to lendee device 112. In such an example, lendee device 112 (e.g., a peer-to-peer payment service application executed by lendee device 112, etc.) can use an account identifier (e.g., a PAN, etc.) associated with the lendee account with an electronic wallet, which may be implemented by and/or integrated with the peer-to-peer transfer service application on lendee device 112.

[0096] In some non-limiting embodiments or aspects, transaction service provider system 108 can associate a lendee risk score with a lendee account. For example, a lendee risk score (e.g., a prediction of a riskiness of providing a loan to a lendee, a prediction of a probability or likelihood of a lendee associated with the lendee account defaulting on repayment of a loan amount, etc.) can be determined based on a third party credit score of the lendee (e.g., a FICO credit score, etc.) and/or a social media score of the lendee, and transaction service provider system 108 can store (e.g., in a lendee database, etc.) an account identifier of the lendee account in association with the lendee risk score of the lendee account. As an example, transaction service provider system 108 can determine a lendee risk score of a lendee based on user data associated with the lendee and/or transaction data associated with at least one prior transaction of the lendee. Further details regarding non-limiting embodiments or aspects of determining a lendee risk score are provided below with regard to step 402 of FIG. 4.

[0097] In some non-limiting embodiments or aspects, transaction service provider system 108 associates one or more payment accounts or instruments (e.g., a checking account, a savings account, a credit account, a portable financial device, an electronic wallet, etc.) with a lendee account. For example, transaction service provider system 108 can receive, from lendee device 112 (e.g., via a peer-to-peer payment transfer service application executed by lender device 112, etc.), an authorization to link and/or use the one or more payment accounts or instruments, which can be external to transaction service provider system 108 and/or transaction processing network 101 , for withdrawing payments and/or funds from the one or more payment accounts or instruments to the lendee account, one or more lender accounts, and/or one or more payment accounts or instruments associated with the one or more lender accounts. As an example, transaction service provider system 108 can periodically (and/or in response to one or more loan repayment due dates, etc.) provide one or more anonymous repayments of one or more loan amounts to one or more lender accounts (and/or one or more payment accounts associated with one or more lender accounts, etc.) from which one or more anonymous payments of the one or more loan amounts were provided to the lendee account.

[0098] As further shown in FIG. 3, at step 304, process 300 includes providing a lender account. For example, transaction service provider system 108 provides (e.g., determines, registers, generates, creates, opens, stores, maintains, updates, etc.) a lender account associated with a lender. As an example, transaction service provider system 108 provides an account identifier that uniquely identifies a lender account associated with a lender. In such an example, the account identifier can include a GUID and/or a PAN that identifies the lender account.

[0099] In some non-limiting embodiments or aspects, transaction service provider system 108 can provide a plurality of lender accounts associated with a plurality of lenders. For example, one or more lender accounts of the plurality of lender accounts can be different from one or more other lender accounts of the plurality of lender accounts and/or one or more lenders of the plurality of lenders can be different from one or more other lenders of the plurality of lenders. As an example, transaction service provider system 108 can provide a plurality of different account identifiers that uniquely identify a plurality of different lender accounts.

[0100] In some non-limiting embodiments or aspects, transaction service provider system 108 provides a lender account in response to a request for a lender account from lender device 114. For example, transaction service provider system 108 can receive, from lender device 114 (e.g., via a peer-to-peer payment transfer service application executed by lender device 114, etc.), a request for a lender account that includes user data, such as Pll or data that can be used to uniquely identify, contact, and/or locate a single person or user (e.g., a lender, etc.), debts, balances, or the like, and provide a lender account associated with the lender in response to the request. As an example, transaction service provider system 108 can store an account identifier that identifies the lender account in a lender database and/or provide the account identifier to lender device 114. In such an example, lender device 114 (e.g., a peer-to-peer payment service application executed by lender device 114, etc.) can use an account identifier associated with the lender account to configure the lender account for use with one or more payment accounts or instruments and/or according to one or more lender preferences.

[0101] In some non-limiting embodiments or aspects, transaction service provider system 108 associates one or more payment accounts or instruments (e.g., a checking account, a savings account, a credit account, a portable financial device, an electronic wallet, etc.) with a lender account. For example, transaction service provider system 108 can receive, from lender device 114 (e.g., via a peer-to-peer payment transfer service application executed by lender device 114, etc.), an authorization to link and/or use the one or more payment accounts or instruments, which can be external to transaction service provider system 108 and/or transaction processing network 101 , for withdrawing payments and/or funds from the one or more payment accounts or instruments to the lender account and/or one or more lendee accounts.

[0102] In some non-limiting embodiments or aspects, transaction service provider system 108 associates at least one lender preference with a lender account. For example, transaction service provider system 108 can receive, from lender device 114 (e.g., via lender input to a GUI of a peer-to-peer payment transfer service application provided by lender device 114, etc.), the at least one lender preference associated with the lender account. As an example, a lender preference can include one or more of the following: at least one threshold for a loan amount, at least one threshold for a rate of a loan amount, at least one threshold for a lendee risk score, at least one threshold for a merchant risk score, at least one threshold for a number of transactions associated with a lendee account, at least one constraint on a type of products or services associated with a transaction, at least one constraint on a location of a transaction, an indication to automatically approve (or deny) a loan request associated with a specified account identifier (e.g., an account identifier of a lendee with whom the lender has previously approved loans that have been sufficiently repaid, etc.), or any combination thereof. In such an example, transaction service provider system 108 can store a lender preference of a lender account in association with an account identifier that identifies the lender account in a lender database.

[0103] As further shown in FIG. 3, at step 306, process 300 includes receiving request data including a request for a loan amount associated with a lendee account. For example, transaction service provider system 108 receives request data including a request for a loan amount associated with a lendee account. As an example, transaction service provider system receives request data including a request for a loan amount associated with a lendee account from lendee device 112 (e.g., via a peer-to-peer payment transfer service application executed by lendee device 112, etc.) via communication network 116. In such an example, request data may include parameters associated with a request for a loan amount, such as a loan amount, an account identifier of a lendee account, and/or the like and/or user data associated with the lendee.

[0104] In some non-limiting embodiments or aspects, request data is associated with at least one transaction at a merchant system. For example, a transaction may be initiated (and/or intended to be initiated) with an account identifier of the lendee account (e.g., with a PAN associated with the lendee account, with an electronic wallet implemented by and/or integrated with the peer-to-peer payment service application on lendee device 112, etc.). As an example, request data can include transaction data including parameters associated with a transaction, such as an account identifier (e.g., a PAN, etc.), a transaction amount, a transaction date and time, a type of products and/or services associated with the transaction, a conversion rate of currency, a type of currency, a merchant type, a merchant name, a merchant location, and/or the like. In such an example, lendee device 112 can receive the transaction data via user input to lendee device 112 (e.g., via lendee input to a GUI of a peer-to-peer payment transfer service application provided by lendee device 112, etc.) and/or from merchant system 102 (e.g., in response to initiating a transaction with an electronic wallet implemented by and/or integrated with the peer-to-peer payment service application on lendee device 112, etc.).

[0105] In some non-limiting embodiments or aspects, a type of products and/or services associated with the transaction may include the following transaction data categories: travel and entertainment transactions, retail transactions, dining transactions,“everyday” spending transactions, or any combination thereof. Travel and entertainment category transactions may include transactions related to airlines, lodging, vehicle rental, entertainment and travel services, and the like. Retail category transactions may include transactions related to apparel and accessories, department stores, discount stores, general retail products, electronics and home improvement stores, and the like. Dining category transactions may include transactions related to restaurants and quick service restaurants, and the like. Everyday spending category transactions may include transactions related to food and groceries, fuel, transportation, drugstores and pharmacies, and the like. Travel and entertainment transactions, retail transactions, and dining transactions may be defined as discretionary spending. Everyday spending transactions may be defined as non-discretionary spending. Any other metric may be included that is determined to be relevant for defining a type of products and/or services associated with the transaction. In some non-limiting embodiments or aspects, a type of products and/or services associated with the transaction may include more narrowly defined transaction data categories, such as transaction data categories defined based at least partially on Merchant Category Classification (MCC) codes. MCC is used to classify a merchant by the type of products or services the merchant provides. MCC codes can be assigned by merchant type, (e.g., one for hotels, one for office supply stores, one for coffee merchants, etc.), or by merchant name (e.g., 3000 for United Airlines). In some non-limiting embodiments or aspects, a type of products and/or services associated with the transaction may include more narrowly defined transaction data categories, such as an identifier of a specific product or service (e.g., an SKU, etc.).

[0106] As further shown in FIG. 3, at step 308, process 300 includes determining a lender account from a plurality of lender accounts based on the request data and at least one lender preference associated with the lender account. For example, transaction service provider system 108 determines a lender account from a plurality of lender accounts based on the request data and at least one lender preference associated with the lender account. As an example, transaction service provider system 108 determines an account identifier of a lender account from a plurality of account identifiers of a plurality of lender accounts in a peer-to-peer payment transfer service provided by transaction service provider system 108 based on the request data including a request for a loan amount associated with a lendee account.

[0107] In some non-limiting embodiments or aspects, a lender account is further determined from the plurality of lender accounts based on at least one of the following: a lendee risk score associated with the lendee account, a merchant risk score associated with a merchant system, a rate associated with the loan amount, or any combination thereof. For example, transaction service provider system 108 can determine a lender account from the plurality of lender accounts based on at least one of the following: a loan amount, a lendee risk score associated with a lendee account, a merchant risk score associated with a merchant system, a rate associated with the loan amount, or any combination thereof.

[0108] Further details regarding non-limiting embodiments or aspects of step 308 of process 300 are provided below with regard to FIG. 4.

[0109] As further shown in FIG. 3, at step 310, process 300 includes providing an anonymous payment of the loan amount from a payment account associated with the lender account to the lendee account during processing of the at least one transaction at the merchant system. For example, transaction service provider system 108 provides an anonymous payment of the loan amount from a payment account associated with the lender account to the lendee account during processing of the at least one transaction at merchant system 102. As an example, transaction service provider system 108 can withdraw payments and/or funds for the loan amount from one or more payment accounts or instruments, which can be external to transaction service provider system 108 and/or transaction processing network 101 , that are associated with the lender account and anonymously transfer the payments and/or funds for the loan amount to the lendee account.

[0110] In some non-limiting embodiments or aspects, transaction service provider system 108 can provide the anonymous payment of the loan amount directly to the lendee account from the payment account associated with the lender account. In some non-limiting embodiments or aspects, transaction service provider system 108 can provide the anonymous payment of the loan amount through the lender account (e.g., by transferring the anonymous payment of the loan amount to the lender account from the payment account associated with the lender account and, subsequently, transferring the anonymous payment of the loan amount from the lender account to the lendee account, etc.).

[0111] In some non-limiting embodiments or aspects, an anonymous payment is provided in at least one of the following manners: the lendee and the lender remain anonymous with respect to each other, lendee device 112 and lender device 114 remain anonymous with respect to each other, or any combination thereof. For example, user data of the lendee, Pll of the lendee, an account identifier of the lendee, user data of the lender, Pll of the lender, an account identifier of the lender, and/or the like are not exchanged between the lendee and lender and/or between lendee device 112 and lender device 114. In some non-limiting embodiments or aspects, the lendee (e.g., user data of the lendee, Pll of the lendee, an account identifier of the lendee, etc.) and/or the lender (e.g., user data of the lender, Pll of the lender, an account identifier of the lender, etc.) are revealed to one another (e.g., via lendee device 112 and/or lender device 114, etc.), for example, before anonymous payment of the loan amount, after anonymous payment of the loan amount, after processing of the at least one transaction at the merchant system (e.g., after authorization of the transaction, etc.), and/or the like. For example, the account identifier of the lendee may be revealed to the lender, which the lender can use in determining future lending decisions for that same lendee.

[0112] Further details regarding non-limiting embodiments or aspects of step 310 of process 300 are provided below with regard to FIG. 5.

[0113] Referring now to FIG. 4, FIG. 4 is a flowchart of a non-limiting embodiment or aspect of a process 400 for real-time, anonymous peer-to-peer lending. In some non-limiting embodiments or aspects, one or more of the steps of process 400 may be performed (e.g., completely, partially, etc.) by transaction service provider system 108 (e.g., one or more devices of transaction service provider system 108). In some non-limiting embodiments or aspects, one or more of the steps of process 400 may be performed (e.g., completely, partially, etc.) by another device or a group of devices separate from or including transaction service provider system 108, such as merchant system 102 (e.g., one or more devices of merchant system 102), payment gateway 104 (e.g., one or more devices of payment gateway 104), acquirer system 106 (e.g., one or more devices of acquirer system 106), issuer system 110 (e.g., one or more devices of issuer system 110), lendee device 112, and/or lender device 114.

[0114] As further shown in FIG. 4, at step 402, process 400 includes determining a lendee risk score. For example, transaction service provider system 108 determines a lendee risk score associated with a lendee account based on transaction data associated with at least one prior transaction of the lendee and/or social media data associated with at least one social media account of the lendee. As an example, a lendee risk score (e.g., a prediction of a riskiness of providing a loan to a lendee, a prediction of a probability or likelihood of a lendee associated with the lendee account defaulting on repayment of a loan amount, etc.) can be determined based on a third party credit score of the lendee (e.g., a FICO credit score, etc.) and/or a social media score of the lendee. In such an example, transaction service provider system 108 can determine a third party credit score of the lendee by retrieving the third party credit score from a third party entity (e.g., FICO, etc.) using request data associated with the lendee and/or applying an existing credit score function or model to transaction data associated with at least one prior transaction of a lendee to calculate the third party credit score associated with the lendee.

[0115] In some non-limiting embodiments or aspects, transaction service provider system 108 uses a social media harvesting tool (e.g., Social Harvest, etc.) that mines social media information (e.g., images, text, etc.) associated with a lendee and analyzes the social media information associated with the lendee to determine a social media credit score for the lendee. For example, machine learning techniques or modeling techniques (e.g., a pattern recognition technique, a data mining technique, a heuristic technique, a supervised learning technique, an unsupervised learning technique, etc.) can be used to analyze the social media information to determine the social media credit score for the lendee.

[0116] In some non-limiting embodiments or aspects, transaction service provider system 108 can determine the lendee risk score as the third-party credit score, as the social media credit score, or as a combination (e.g., an average, a sum, a weighted adjustment of one score based on the other score, etc.) of the third-party credit score and the social media credit score. [0117] In some non-limiting embodiments or aspects, transaction service provider system 108 can determine and/or update the lendee risk score periodically, concurrently with providing the lendee account, and/or during processing of a transaction associated with the lendee account (e.g., in real-time in response to a request for a loan amount associated with the lendee account, etc.).

[0118] As further shown in FIG. 4, at step 404, process 400 includes determining a merchant risk score associated with the merchant system based on transaction data associated with the merchant system. For example, transaction service provider system 108 can determine a merchant risk score (e.g., a prediction of a riskiness of providing a loan for transactions at a merchant, a prediction of a probability or likelihood of a lendee defaulting on repayment of a loan amount for a transaction at a merchant, etc.) associated with merchant system 102 based on transaction data (e.g., a merchant name, a merchant location, etc.) associated with the merchant system. As an example, transaction service provider system 108 can determine a merchant risk score associated with merchant system 102 from a merchant risk score look-up table that stores merchant risk scores in association with transaction data (e.g., merchant names, merchant locations, etc.) associated with merchant systems. In some examples, transaction service provider system 108 can apply an existing risk function or model to transaction data associated with the merchant to calculate the merchant risk score. As an example, machine learning techniques or modeling techniques (e.g., a pattern recognition technique, a data mining technique, a heuristic technique, a supervised learning technique, an unsupervised learning technique, etc.) can be used to analyze the transaction data associated with the merchant system to determine the merchant risk score for the merchant system.

[0119] As further shown in FIG. 4, at step 406, process 400 includes determining a rate associated with the loan amount based on at least one of the following: the loan amount, the lendee risk score, the merchant risk score, or any combination thereof. For example, transaction service provider system 108 can calculate a rate (e.g., an interest rate, etc.) associated with the loan amount based on at least one of the following: the loan amount, the lendee risk score, the merchant risk score, or any combination thereof. As an example, transaction service provider system 108 can calculate a range of interest rates associated with the loan amount based on at least one of the following: the loan amount, the lendee risk score, the merchant risk score, or any combination thereof.

[0120] In some non-limiting embodiments or aspects, the rate associated with the loan amount can be determined by adjusting a predetermined interest rate (e.g., a current interest rate, a market interest rate, an average interest rate, a base interest rate set by a peer-to-peer payment transfer service, etc.) based on a rate adjustment amount determined from a rate adjustment look-up table storing rate adjustment amounts associated with loan amounts, lendee risk scores, and/or merchant risk scores. In some non-limiting embodiments or aspects, machine learning techniques or modeling techniques (e.g., a pattern recognition technique, a data mining technique, a heuristic technique, a supervised learning technique, an unsupervised learning technique, etc.) can be used to analyze the loan amount, the lendee risk score, the merchant risk score, or any combination thereof to determine the rate associated with the loan amount.

[0121] As further shown in FIG. 4, at step 408, process 400 includes selecting the lender account from the plurality of lender accounts. For example, transaction service provider system 108 can compare at least one parameter of the request data (e.g., a loan amount, a rate of the loan amount, a lendee risk score, a merchant risk score, an account identifier of the lendee account, a type of products or services included in the transaction, a location of the transaction, etc.) to at least one lender preference of the plurality of lender accounts (e.g., at least one threshold for a loan amount, at least one threshold for a rate of a loan amount, at least one threshold for a lendee risk score, at least one threshold for a merchant risk score, at least one threshold for a number of transactions associated with a lendee account, at least one constraint on a type of products or services associated with a transaction, at least one constraint on a location associated with a transaction, an indication to automatically approve (or deny) a loan request associated with a specified account identifier, etc.) to determine lender accounts associated with the at least one lender preference that match or satisfy the at least one parameter of the request data. As an example, transaction service provider system 108 can rank the plurality of lender accounts according to a number of the at least lender preference that match or satisfy the at least one parameter of the request data and/or a distance (e.g., a closeness, etc.) of a numerical value of the at least lender preference to a numerical value of the at least one parameter of the request data. In such an example, transaction service provider system 108 can select the lender account from the plurality of lender accounts that is ranked the highest or is a closest match among the plurality of lender accounts. In some non-limiting embodiments or aspects, for subsequent requests from a same lendee account, a different lender account (e.g., a next highest ranked lender account, etc.) than was selected for previous requests from the same lendee account may be automatically selected to avoid repeatedly matching a same lendee and lender.

[0122] As further shown in FIG. 4, at step 410, process 400 includes determining a lender approval of the loan amount and the rate for the lender account. For example, transaction service provider system 108 determines a lender approval of the loan amount and the rate for the lender account from the plurality of lender accounts. As an example, transaction service provider system 108 determines a lender approval of the loan amount and the rate for the lender account selected as the highest ranked or closest matched lender account in step 408.

[0123] In some non-limiting embodiments or aspects, transaction service provider system 108 can provide an approval request for the loan amount and the rate to lender device 114 associated with the lender account without identifying the lendee account to the lender device and receive a response including an approval of the request for the loan amount and the rate from lender device 114. For example, the anonymous payment of the loan amount from the payment account associated with the lender account to the lendee account can be provided based on receiving the response including the approval from lender device 114.

[0124] In some non-limiting embodiments or aspects, transaction service provider system 108 can determine based on at least one of the following: the loan amount, the rate, the at least one lender preference, the lendee risk score associated with the lendee account, the merchant risk score associated with the merchant system, or any combination thereof, an automatic approval of the of the loan amount and the rate for the lender account without providing the loan amount, the rate, the at least one lender preference, the lendee risk score associated with the lendee account, the merchant risk score associated with the merchant system, or any combination thereof to lender device 114 associated with the lender account. For example, a lender account can be associated with a lender preference that indicates that a request for a loan amount associated with request data including one or more parameters and/or one or more combinations of parameters be automatically approved for the lender account. As an example, the anonymous payment of the loan amount from the payment account associated with the lender account to the lendee account is provided based on determining the automatic approval for the lender account.

[0125] In some non-limiting embodiments or aspects, if transaction service provider system 108 determines a denial of the loan amount and the rate for the lender account or a timer for receipt of a response including an approval of the loan amount and the rate from lender device 114 expires, processing can return to step 408 in which transaction service provider system 108 can select a next highest ranked or closest matched lender account and, in step 410, transaction service provider system 108 determines a lender approval of the loan amount and the rate for the lender account selected as the next highest ranked or closest matched lender account.

[0126] As further shown in FIG. 4, at step 412, process 400 includes determining a lendee approval of the rate. For example, transaction service provider system 108 can provide an approval request for the rate associated with the loan amount to lendee device 112 associated with the lendee account and receive a response including an approval of the request for the rate associated with the loan amount from the lendee device. As an example, the anonymous payment of the loan amount from the payment account associated with the lender account to the lendee account can be provided based on receiving the response including the approval from lendee device 112.

[0127] Referring now to FIG. 5, FIG. 5 is a flowchart of a non-limiting embodiment or aspect of a process 500 for real-time, anonymous peer-to-peer lending. In some non-limiting embodiments or aspects, one or more of the steps of process 500 may be performed (e.g., completely, partially, etc.) by transaction service provider system 108 (e.g., one or more devices of transaction service provider system 108). In some non-limiting embodiments or aspects, one or more of the steps of process 400 may be performed (e.g., completely, partially, etc.) by another device or a group of devices separate from or including transaction service provider system 108, such as merchant system 102 (e.g., one or more devices of merchant system 102), payment gateway 104 (e.g., one or more devices of payment gateway 104), acquirer system 106 (e.g., one or more devices of acquirer system 106), issuer system 110 (e.g., one or more devices of issuer system 110), lendee device 112, and/or lender device 114. [0128] As further shown in FIG. 5, at step 502, process 500 includes receiving a transaction authorization request associated with the at least one transaction from the merchant system, and the transaction authorization request is associated with the lendee account. For example, transaction service provider system 108 can receive a transaction authorization request associated with a transaction from merchant system 102, and the transaction authorization request can be associated with a lendee account. As an example, a lendee can initiate a transaction at merchant system 102 with an account identifier of the lendee account (e.g., with the PAN associated with the lendee account via a merchant website, with an electronic wallet implemented by and/or integrated with the peer-to-peer payment service application on lendee device 112 via the merchant website or in store using lendee device 112 with an NFC enabled POS terminal, etc.). In some non-limiting embodiment or aspects, the anonymous payment of the loan amount from the payment account associated with the lender account to the lendee account is provided based on receiving the transaction authorization request associated with the lendee account from merchant system 102. In some non-limiting embodiments or aspects, the transaction authorization request can include transaction data associated with the at least one transaction at merchant system 102.

[0129] As further shown in FIG. 5, at step 504, process 500 includes comparing, with at least one processor, at least one parameter of the request data to at least one parameter of the transaction data. For example, transaction service provider system 108 can compare at least one parameter of the request data (e.g., a transaction amount (and/or a loan request amount), a type of products and/or services associated with the transaction, a merchant type, a merchant name, a merchant location, etc.) received from lendee device 114 to at least one parameter of the transaction data (e.g., a transaction amount, a type of products and/or services associated with the transaction, a merchant type, a merchant name, a merchant location, etc.) received from merchant system 102.

[0130] As further shown in FIG. 5, at step 506, process 500 includes providing the anonymous payment of the loan amount from the payment account associated with the lender account to the lendee account can be provided based on a result of the comparison. For example, transaction service provider system 108 can provide the anonymous payment of the loan amount from the payment account associated with the lender account to the lendee account if the result of the comparison indicates that the at least one parameter of the request data matches the at least one parameter of the transaction data. As an example, transaction service provider system 108 can ensure that a transaction amount, a type of products and/or services associated with the transaction, a merchant type, a merchant name, a merchant location, and/or the like for which the lendee sought the loan is the same as a transaction amount, a type of products and/or services associated with the transaction, a merchant type, a merchant name, a merchant location, and/or the like approved by the lendee.

[0131] As further shown in FIG. 5, at step 508, process 500 includes providing a transaction authorization response to the transaction authorization request based on providing the anonymous payment of the loan amount to the lendee account. For example, transaction service provider system 108 can determine a transaction authorization response to the transaction authorization request based on providing the anonymous payment of the loan amount to the lendee account (e.g., transaction service provider system 108 can authorize the transaction and/or provide the anonymous payment of the loan amount from the lendee account to an account associated with merchant system 102, etc.). Accordingly, transaction service provider system 108 can ensure that a lendee uses a loan amount for a specific transaction (e.g., for a specific type of products and/or services, etc.) for which the lender approved payment of the loan amount, while maintaining the anonymity of the lendee and the lender with respect to each other.

[0132] Referring now to FIG. 6, FIG. 6 is a flow diagram of a non-limiting embodiment or aspect of an implementation 600 relating to a process for real-time, anonymous peer-to-peer lending. As shown in FIG. 6, implementation 600 includes merchant system 602, transaction service provider system 608, lendee device 612 associated with a lendee, and/or lender device 614 associated with a lender. In some non-limiting embodiments or aspects, merchant system 602 can be the same as or similar to merchant system 102. In some non-limiting embodiments or aspects, transaction service provider system 608 can be the same as or similar to transaction service provider system 108. In some non-limiting embodiments or aspects, lendee device 612 can be the same as or similar to lendee device 112. In some non-limiting embodiments or aspects, lender device 614 can be the same as or similar to lender device 114. [0133] As shown by reference number S1 in FIG. 6, transaction service provider system 608 can receive request data including a request for a loan amount associated with a lendee account from lendee device 612, and the request data can be associated with a transaction at a merchant system 602 (e.g., include one or more parameters associated with a transaction at merchant system 602, etc.). In some non-limiting embodiments or aspects, the lendee can initiate can initiate the transaction at merchant system 602 with an account identifier of the lendee account (e.g., with the PAN associated with the lendee account via a merchant website, with an electronic wallet implemented by and/or integrated with a peer-to-peer payment service application on lendee device 612 via the merchant website or in store using lendee device 612 with an NFC enabled POS terminal, etc.) before or concurrently with providing the request data including the request for the loan amount associated with the lendee account from lendee device 612 to transaction service provider system 608 in reference number S1. In some non-limiting embodiments or aspects, the transaction can be a transaction intended to be initiated by the lendee with merchant system 602 at a time after providing the request data including the request for the loan amount associated with the lendee account from lendee device 612 to transaction service provider system 608 in reference number S1 , for example, in response to receiving an indication that the request for the loan amount and the rate has been approved by an anonymous lender in reference number S5 as described below with respect to reference number S6.

[0134] As shown by reference number S2 in FIG. 6, transaction service provider system 608 can determine a lender account from a plurality of lender accounts based on the request data and at least one lender preference associated with the lender account.

[0135] As shown by reference number S3 in FIG. 6, transaction service provider system 608 can provide an approval request for the loan amount and a rate for the loan amount to lender device 614 associated with the lender account without identifying the lendee account and the lendee to lender device 614 and the lender.

[0136] As shown by reference number S4 in FIG. 6, transaction service provider system 608 can receive a response including an approval of the request for the loan amount and the rate from lender device 614. [0137] As shown by reference number S5 in FIG. 6, the lendee can receive an indication that the request for the loan amount and the rate has been approved by an anonymous lender.

[0138] As shown by reference number S6 in FIG. 6, the lendee can initiate can initiate the transaction at merchant system 602, for example, in response to receiving the indication that the request for the loan amount and the rate has been approved by an anonymous lender in reference number S5.

[0139] As shown by reference number S7 in FIG. 6, transaction service provider system 608 can receive a transaction authorization request associated with the transaction from merchant system 102, and the transaction authorization request can be associated with the lendee account and include transaction data associated with the transaction at merchant system 602 (e.g., the account identifier of the lendee account, such as a PAN, etc.).

[0140] As shown by reference number S8 in FIG. 6, transaction service provider system 108 can compare at least one parameter of the request data received from lendee device 114 to at least one parameter of the transaction data received from merchant system 102.

[0141] As shown by reference number S9 in FIG. 6, transaction service provider system 108 can provide the anonymous payment of the loan amount from the payment account associated with the lender account to the lendee account if the result of the comparison indicates that the at least one parameter of the request data matches the at least one parameter of the transaction data.

[0142] As shown by reference number S10 in FIG. 6, transaction service provider system 608 can authorize the transaction and/or provide the anonymous payment of the loan amount from the lendee account to an account associated with merchant system 602.

[0143] Although the above methods, systems, and computer program products have been described in detail for the purpose of illustration based on what is currently considered to be the most practical and preferred embodiments or aspects, it is to be understood that such detail is solely for that purpose and that the present disclosure is not limited to the described embodiments or aspects; but, on the contrary, is intended to cover modifications and equivalent arrangements that are within the spirit and scope of the appended claims. For example, it is to be understood that the present disclosure contemplates that, to the extent possible, one or more features of any embodiment or aspect can be combined with one or more features of any other embodiment or aspect.