This application claims priority to and the benefit of the filing date of U.S. Patent Application No. 62/207,511 filed on August 20, 2015, which is hereby incorporated by reference in its entirety.

FIELD

The present disclosure relates to the crediting of user accounts and processing of transactions involving user accounts, specifically associating controlled payment numbers with user accounts of a non-financial institution entity, verification of user identities, and use thereof in person to person transactions.

BACKGROUND

Non-financial institution (NFI) entities, particularly those with a heavy presence on the Internet and other types of communication networks mat involve computing devices, may be associated with a significant number of users. Each of these users may have an account with the NFI entity, which may be used to engage in various services offered by the entity. For example, a social network may have users numbering in the hundreds of thousands, if not millions, and may provide the users with various tools for connecting with others, interacting socially, etc.

As part of the services provided to users, NFI entities may sometimes interact with, or provide for an avenue for users to interact with, a third party. For example, the NFI entity may make a deal with a merchant to offer discounts to the entity's users, which may be of mutual benefit to the NFI entity, the merchant, and the users that enjoy the discount. However, it may be difficult and cumbersome for a merchant to verify that a customer is a user of the NFI entity and eligible for a discount, which may dissuade both the merchant and users from taking advantage of the deal, thereby negating any benefit attempted by the NFI entity.

Some methods for providing users with such a service may involve collecting user payment information, and enabling the user to conduct transactions via the NFI entity. However, users may be wary of providing such sensitive data to the NFI entity. In addition, many NFI entities may lack the technical hardware and system security necessary to both store such information and communicate such

information, which may require specialized protocols and communication technology. Another method may involve the establishing of payment accounts with the NFI entity, using a traditional fiat currency or a specialized currency. However, this may require the entity to operate as a financial entity and regularly process payment transactions, which may be costly and require the entity to significantly modify their technical systems, business practices, licensing, etc.

Thus, there is a need for a technical system that can provide an NFI entity with the ability to enable users to conduct payment transactions, particularly person to person transactions, but without requiring the NFI entity to operate as a financial institution or to regularly conduct transactions using traditional payment systems. Some NFI entities have established virtual currencies in order to enable transactions among users. However, these currencies often may be unable to be used outside of the NFI entity, which may be limiting for users, and has historically resulted in low adoption and usage by users. Thus, there is a need for not only enabling users to conduct user to user transactions, but also to enable users to conduct transactions with outside entities, but without requiring the NFI entity to operate as a financial institution.

In addition, in some instances it may be beneficial, or in some jurisdictions even required, to verify a user that is to conduct transactions with outside entities. Limitations in existing NFI entity systems prevent NFIs from verifying the identity of a user to whom currency is provided for use in transactions with outside entities. As such, there is also a need for a technical solution where the identity of a user that conducts user to user and outside entity transactions can be verified.

SUMMARY

The present disclosure provides a description of systems and methods for verification of user identities.

A method for verification of user identity includes: storing, in an account database, a plurality of account profiles, each account profile including data related to a user account of a non-financial institution (NFI) entity, said data including at least an account identifier and an address; receiving, by a receiving device, a transaction request, wherein the transaction request includes at least a specific account identifier and a transaction amount; identifying, by a processing device, an account profile stored in the account database where the included account identifier

corresponds to the specific account identifier; generating, by the processing device, a controlled payment number, wherein the controlled payment number is associated with a transaction account of the NFI entity; transmitting, by a transmitting device, a notification to a third party entity, wherein the notification includes at least the specific account identifier; transmitting, by the transmitting device, the generated controlled payment number for distribution to a user associated with the user account related to the specific account profile; receiving, by the receiving device, a data message from the third party entity, wherein the data message includes at least the specific account identifier and identification data associated with the user, and updating, by the processing device, the specific account profile in the account database to include at least the generated controlled payment number, the

identification data, and a spending limit, wherein the spending limit is based on the transaction amount and where payment transactions involving the controlled payment number are subject to the spending limit

A system for verification of user identity includes an account database, a receiving device, a processing device, and a transmitting device. The account database is configured to store a plurality of account profiles, each account profile including data related to a user account of a non-financial institution (NFI) entity, said data including at least an account identifier and an address. The receiving device is configured to receive a transaction request, wherein the transaction request includes at least a specific account identifier and a transaction amount The processing device is configured to: identify an account profile stored in the account database where the included account identifier corresponds to the specific account identifier; and generate a controlled payment number, wherein the controlled payment number is associated with a transaction account of the NFI entity. The transmitting device is configured to transmit a notification to a third party entity, wherein the notification includes at least the specific account identifier; and the generated controlled payment number for distribution to a user associated with the user account related to the specific account profile. The receiving device is further configured to receive a data message from the third party entity, wherein the data message includes at least the specific account identifier and identification data associated with the user. The processing device is further configured to update the specific account profile in the account database to include at least the generated controlled payment number, the identification data, and a spending limit, wherein the spending limit is based on the transaction amount and

where payment transactions involving the controlled payment number are subject to the spending limit

BRIEF DESCRIPTION OF THE DRAWING FIGURES

The scope of the present disclosure is best understood from the following detailed description of exemplary embodiments when read in conjunction with the accompanying drawings. Included in the drawings are the following figures:

FIG. 1 is a block diagram illustrating a high level system architecture for processing transactions involving user accounts with a non-financial institution entity using controlled payment numbers in accordance with exemplary embodiments.

FIG. 2 is a block diagram illustrating the processing server of FIG. 1 for crediting user accounts and processing transactions involving user accounts in accordance with exemplary embodiments.

FIGS. 3 A and 3B are a flow diagram illustrating a processing flow for the crediting of a user account associated with a controlled payment number in accordance with exemplary embodiments.

FIGS. 4A and 4B are a flow diagram illustrating a processing flow for processing a transaction involving a user account and a third party merchant in accordance with exemplary embodiments.

FIG. 5 is a flow diagram illustrating a processing flow for processing a user to user transaction involving controlled payment numbers in accordance with exemplary embodiments.

FIG. 6 is a flow diagram illustrating the processing of transactions using the processing server of FIG. 2 in accordance with exemplary embodiments.

FIGS. 7A and 7B are a flow diagram illustrating a processing flow for verifying user identities in accordance with exemplary embodiments.

FIG. 8 is a flow chart illustrating an exemplary method for providing credit for a user account in accordance with exemplary embodiments.

FIG. 9 is a flow chart illustrating an exemplary method for processing transactions in user accounts in accordance with exemplary embodiments.

FIG. 10 is a flow chart illustrating an exemplary method for verification of user identity in accordance with exemplary embodiments.

FIG. 11 is a flow diagram illustrating the processing of a payment transaction in accordance with exemplary embodiments.

FIG. 12 is a block diagram illustrating a computer system architecture in accordance with exemplary embodiments.

Further areas of applicability of the present disclosure will become apparent from the detailed description provided hereinafter. It should be understood that the detailed description of exemplary embodiments are intended for illustration purposes only and are, therefore, not intended to necessarily limit the scope of the disclosure.

DETAILED DESCRIPTION

Glossary of Terms

Payment Network - A system or network used for the transfer of money via the use of cash-substitutes for thousands, millions, and even billions of transactions during a given period. Payment networks may use a variety of different protocols and procedures in order to process the transfer of money for various types of transactions. Transactions that may be performed via a payment network may include product or service purchases, credit purchases, debit transactions, fund transfers, account withdrawals, etc. Payment networks may be configured to perform transactions via cash-substitutes, which may include payment cards, letters of credit, checks, transaction accounts, etc. Examples of networks or systems configured to perform as payment networks include those operated by MasterCard®, VISA®, Discover*, American Express*, PayPal*, etc. Use of the term "payment network" herein may refer to both the payment network as an entity, and the physical payment network, such as the equipment, hardware, and software comprising the payment network.

Transaction Account - A financial account that may be used to fund a transaction, such as a checking account, savings account, credit account, virtual payment account, etc. A transaction account may be associated with a consumer, which may be any suitable type of entity associated with a payment account, which may include a person, family, company, corporation, governmental entity, etc. In some instances, a transaction account may be virtual, such as those accounts operated by PayPal* etc.

Merchant - An entity that provides products (e.g., goods and/or services) for purchase by another entity, such as a consumer or another merchant A merchant may be a consumer, a retailer, a wholesaler, a manufacturer, or any other type of entity that may provide products for purchase as will be apparent to persons having skill in the relevant art. In some instances, a merchant may have special knowledge in the goods and/or services provided for purchase. In other instances, a merchant may not have or require and special knowledge in offered products. In some embodiments, an entity involved in a single transaction may be considered a merchant.

Controlled Payment Number - Controlled payment numbers may be payment numbers associated with a payment account that are subject to one or more rules. In many cases, these rules may be set by a cardholder, such as spending limits, limits on days and/or times of a transaction, limits on merchants or industries, transaction spending or frequency limits, etc. Controlled payment numbers may offer an account holder an opportunity to give payment cards tied to the account to others for use, but subject to rules set by the cardholder, such as an employer distributing cards to employees, or a parent distributing cards to children. Additional detail regarding controlled payment numbers may be found in U.S. Patent No. 6,636,833, issued October 21, 2003; U.S. Patent No. 7,136,835, issued November 14, 2006; U.S. Patent No. 7,571,142, issued August 4, 2009; U.S. Patent No. 7,567,934, issued July 28, 2009; U.S. Patent No. 7,593,896, issued September 22, 2009; U.S. Patent Application No. 12/219,952, filed July 30, 2008; U.S. Patent Application No.

12/268,063, filed November 10, 2008; and U.S. Patent Application No. 12/359,971, filed January 26, 2009; each of which is herein incorporated by reference in its entirety.

Payment Rails - Infrastructure associated with a payment network used in the processing of payment transactions and the communication of transaction messages and other similar data between the payment network and other entities interconnected with the payment network that handles thousands, millions, and even billions of transactions during a given period. The payment rails may be comprised of the hardware used to establish the payment network and the interconnections between the payment network and other associated entities, such as financial institutions, gateway processors, etc. In some instances, payment rails may also be affected by software, such as via special programming of the communication hardware and devices that comprise the payment rails. For example, the payment rails may include specifically configured computing devices that are specially configured for the routing of transaction messages, which may be specially formatted data messages that are electronically transmitted via the payment rails, as discussed in more detail below.

System for Processing Transactions wife User Accounts

FIG. 1 illustrates a system 100 for the crediting of user accounts and use thereof in user-to-merchant and user-to-user payment transactions via the use of controlled payment numbers for users of a non-financial institution entity.

The system 100 may include a processing server 102. The processing server 102, discussed in more detail below, may be configured to credit user accounts, assist in the processing of transactions involving user accounts, manage user accounts, and otherwise provide for assistance with associations between user accounts and controlled payment numbers for users of a non-financial institution (NFI) entity 104 using the methods discussed herein. The NFI entity 104 may be, for example, a social network, a gaming platform, an entertainment website, a news service, or any other entity mat may not be a financial institution, but may have users that may benefit from being involved in payment transactions.

The NFI entity 104 may have a transaction account established with a financial institution 106. The financial institution 106 may be, for instance, an issuing bank, or other suitable type of financial institution configured to establish and operate transaction accounts. The transaction account associated with the NFI entity 104 may be used by the NFI entity 104 to conduct payment transactions using traditional methods and systems. Payment transactions involving the NFI entity 104 may be conducted via a payment network 108 using traditional methods and systems.

The financial institution 106, payment network 108, and/or processing server 102 may be configured to provide the NFI entity 104 with controlled payment number (CPNs) associated with their transaction account. CFNs may be subject to one or more limits set forth by the NFI entity 104 and/or financial institution 106, but, when used, may draw on the associated transaction account Each CPN may have a different number mat may be different from the primary account number associated with the transaction account that, when used in a transaction, may trigger the checking of the transaction against limits set on the CPN. For instance, a CPN may be established that has a spending limit of $50 per transaction. When the CPN is used in a transaction, the payment network 108 may identify that a CPN is used, identify its associated limits, and may evaluate limits as applied to the transaction. If the transaction is whhin the $50 limit, it may be processed, with payment being drawn from the associated transaction account. If the transaction exceeds the $50 limit, it may be declined, and the NFI entity 104 and/or financial institution 106 may be identified.

The processing server 102 may be configured to provide the NFI entity 104 with CPNs for users of the NFI entity 104. The processing server 102 may be configured to communicate with the payment network 108 and/or financial institution 106 to request issuance of new CPNs and to adjust spending limits on CPNs using methods and systems that will be apparent to persons having skill in the relevant art In some instances, the processing server 102 may be a part of the payment network 108 or financial institution 106 and may manage CPNs through internal

communications as applicable. In some cases, the processing server 102 may be a part of the NFI entity 104.

In the system 100, a payer 110 may be a user of the NFI entity 104.

The payer 110 may communicate with the NFI entity 104 via a payer device 112. The payer device 112 may be any suitable type of computing device, such as a desktop computer, laptop computer, notebook computer, tablet computer, cellular phone, smart phone, smart watch, smart television, wearable computing device, implantable computing device, etc. The payer 110 may use the payer device 112 to register as a user of the NFI entity 104, such as by signing up for services offered by the NFI entity 104 via a webpage, application program, etc. For example, if the NFI entity 104 is a social network, the payer 110 may use an application program associated with the social network on the payer device 112 to register as a user of the social network and access the services provided thereby.

As one of the services, the NFI entity 104 may provide the payer 110 with the ability to conduct payment transactions using their user account In order to conduct payment transactions, the payer 110 may first be required to buy currency to be associated with their user account Using the payer device 112, the payer 110 may initiate a payment transaction for the purchase of currency from the NFI entity 104. Details for the payment transaction may be provided to the processing server 102. The processing server 102 may identify that the transaction is for the purchase of currency based on data included in the transaction details. For example, the transaction details may include an indication mat the transaction is for the purchase of currency, such as a data value indicative of the type of transaction, or the inclusion of the account number associated with the NFI entity's transaction account, which may be used only in the purchase of currency, for example.

The processing server 102 may identify a user account associated with the payer 110. In some instances, the payer 110 may provide their account information, such as an account identifier, as part of the transaction process. In other instances, the NFI entity 104 may provide the payer's account information during the submission of the transaction data, such as included in a data element of a transaction message or in a separate, accompanying message. The processing server 102 may identify a CPN associated with the user account of the payer 110. If the payer 110 is not already associated with a CPN, the processing server 102 may request a CPN be issued by the payment network 108 or financial institution 106 as applicable. The CPN may be issued with a spending limit corresponding to the amount of currency being purchased by the payer 110. In instances where the payer 110 already has a CPN associated thereto, the processing server 102 may request that the spending limit of the CPN be increased based on the amount of currency being purchased. The result is that the payer 110 may have a CPN that is associated with the NFI entity's transaction account that has a spending limit commiserate with the amount of currency purchased by the payer 110.

The spending limit of CPNs associated with users may represent currency available for spending by users of the NFI entity 104. In some instances, the actual spending limit may be represented to users directly. For example, if a user is associated with a CPN with a spending limit of $100, the user's account may reflect a balance of $100. In other instances, an alternative currency may be used, such as a different flat currency, a virtual, non-fiat currency, a cryptocurrency, etc. For example, the NFI entity 104 may have a transaction account mat is established in U.S. dollars, and thus a user may have a spending limit of $100, but may be represented to the user as the equivalent amount in a different currency, such as one local to the user, such as in Euros. In another example, the NFI entity 104 may establish a currency unique to the NFI entity, such as "credits," and may represent a user's spending limit in an equivalent amount of credits based on their spending limit. For instance, if the NFI entity 104 establishes mat 100 credits is equivalent to $1, a user with a $100 spending limit may have their account reflect a balance of 10,000 credits.

Users of the NFI entity 104 may be able to use their user account in conducting payment transactions with third parties, such as an outside merchant 114. The payer 110 may initiate a payment transaction with a merchant 114 for the purchase of goods or services and may present their CPN associated with their user account for payment. In some instances, the transaction may be an e-commerce transaction, with the CPN provided to the merchant 114 electronically. In other instances, the payer 110 may be issued a physical card encoded with payment credentials associated with the CPN, which may be presented to the merchant 114 similar to a traditional payment card. The merchant 114 may then process the payment transaction using the CPN. A transaction message may be submitted to the payment network 108 that includes the CPN as the primary account number used to fund the transaction. The payment network 108 may then process the transaction using traditional methods and systems for processing of transactions involving CPNs.

The processing server 102 may adjust the spending limit of the payer's CPN as a result of the transaction with the merchant 114. For example, if the payer 110 spends $50 at the merchant 114, the processing server 102 may request the financial institution 106 or payment network 108 to reduce the spending limit of the CPN by $50. The resulting spending limit may be reflected in the user's account when accessing the NFI entity 104, showing their reduced balance. Thus, users of the NFI entity 104 may be able to conduct payment transactions with outside merchants 114 using their user account, without requiring the NFI entity 104 to operate as a financial institution, and without the NFI entity 104 possessing or obtaining any payment information from users. Instead, CPNs are issued on the transaction account of the NFI entity 104, with their spending limit indicated to the user as being an available balance.

User CPNs may also be advantageous for use in the conducting of user-to-user transactions for users of the NFI entity 104. The payer 110 may conduct a payment transaction to make a payment to the payee 116 with the payee 116 using a payee device 118. Like the payer device 112, the payee device 118 may be any suitable type of computing device, such as a desktop computer, laptop computer, notebook computer, tablet computer, cellular phone, smart phone, smart watch, smart television, wearable computing device, implantable computing device, etc.

Traditionally, a person-to-person payment transaction may require the submission of a transaction message to the payment network 108 mat includes payment credentials for a transaction account associated with each of the payer 110 and the payee 116. Such transaction processing often involves specific technical hardware configured to generate transaction messages, which are often specially formatted, and to communicate with payment networks 108, which involves specialized communication paths and protocols. However, many payers 110, payees 116, and NFI entities 104 may lack the technical hardware able to perform such processes.

Using the system 100, in order to make a payment from the payer 110 to the payee 116, the payer 110 may use their user account via the payer device 112 to initiate a transaction for the payment of currency to the payee 116 via the NFI entity 104. The NFI entity 104 may receive the transaction request and may forward the transaction request to the processing server 102. The processing server 102 may submit a request to the financial institution 106 or payment network 108 as applicable to increase the spending limit for the CPN associated with the payee 116 by the transaction amount, and decrease the spending limit for the CPN associated with the payer 110 by the transaction amount

As a result, the payer 110 and payee 116 may participate in a user-to-user transaction where the available spending for each of the users has been adjusted accordingly, but without requiring the processing of a payment transaction using the payment network 108. By using CPNs and adjusting their spending limits to represent a transaction, the NFI entity 104 may provide for user-to-user payments without requiring the NFI entity 104 or user devices to be modified to generate transaction message or configured to use specialized communication protocols to perform communications with the payment network 108. Thus, the processing server 102 may provide for significant technical advantages over traditional systems by enabling the NFI entity 104 to provide users with user-to-user payment transactions without requiring processing by traditional payment networks 108, while still enabling users to conduct payment transactions with outside merchants 114 using the same accounts.

In some embodiments, the processing server 102 may also be configured to verify the identity of a payer 110 or payee 116. For example, in instances where a payee 116 may be a user of the NFI entity 104 without a known transaction account, the identity of the payee 116 may be verified prior to the payee 116 being provided access to the funds (e.g., before the spending limit is increased or the user CPN is provided to the payee 116). For instance, some jurisdictions may

require that a recipient of a payment instrument is identified prior to issuance of that payment instrument to the recipient. In such instances, the processing server 102 may verify the identity of the payee 116 rather than providing the CPN to the payee 116 or for enabling the CPN for usage in transactions involving merchants 114 or other entities outside of user-to-user transactions via the NFI entity 104. For example, the payee 116 may be able to transact with the payer 110 using credits, but may be unable to use their CPN in transactions at merchants 114 prior to providing identification data.

In some embodiments, the processing server 102 may utilize a third party to gather identification data for the payee 116. For example, when a transaction request is received by the processing server 102, the processing server 102 may identify the user account for the payee 116 at the NFI entity 104 and may provide data indicative of the user account (e.g., an account identifier) to a third party. The third party may then contact the payee 116 and may request identification from the payee 116. The third party may return the identification data to the processing server 102. Once the identification data is received, it may be stored in a profile associated with the payee 116, and then the spending limit for the CPN associated with the payee's user account may be increased and/or the CPN may be provided to the payee 116 for use.

In some embodiments, the third party may be identified for use in collecting identification of the payee 116 based on a geographic location of the payee 116. For example, the third party may be a financial institution, such as the financial institution 106, that includes one or more branches or services that operate in proximity to the payee 116, such as in a city associated with the payee's user account with the NFI entity 104. In some instances, the payee 116 may indicate on or more third parties the payee 116 may be willing to interact with to provide identification data. For example, when the payee 116 is sent funds by a payer 110, the processing server 102 (e.g., directly to the payee device 118 or via the NFI entity 104) may notify the payee 116 of the transfer and the necessity to provide identification. The payee 116 may then (e.g., using the payee device 118) select one or more third party entities and/or methods for providing identification data to the processing server 102.

In some cases, the processing server 102 may generate or otherwise identify a CPN for the payee 116 and may provide the CPN to the payee 116 in conjunction with the collection of identification data. For example, the third party entity may be a mail delivery service that may deliver a physical payment card encoded with the CPN to the payee 116 and collect identification data in exchange for the payment card. In such an example, the payment card may be sent in a package requiring the payee 116 to present a government-issued identification card and a signature to accept the package. The third party entity may then provide the identification card and signature or data associated therewith to the processing server 102 for association with the payee's user account. Upon receipt of the identification data, the spending limit for the CPN may be increased based on the funds paid to the payee 116, and the processing server 102 may inform the payee 116 that their new funds are available for use via the payment card. Other third party entities may include, for example, government agencies, credit bureaus, identity services, law enforcement agencies, etc. Identification data may include name, identification number, date of birth, age, gender, signature, image, biometric data, or any other suitable identification data such as may be required by rules or regulations or suitable for use in performing the functions discussed herein.

In some embodiments, the processing server 102 may be configured to provide the identification data to the financial institution 106 or another entity for additional verification. For example, the financial institution 106 may perform further verification of the identification data provided by the payee 116, such as to ensure that the identification data is genuine and/or to verify mat the payee 116 is who they purport to be. For instance, the financial institution 106 may check an identification number provided by the payee 116 with a name and date of birth provided by the payee 116 to ensure mat the information matches. In such embodiments, the financial institution 106 or other entity may transmit a notification to the processing server 102 that indicates if the payee 116 was successfully verified or not. In some cases, the processing server 102 may wait to receive a notification from the financial institution 106 that the payee 116 was successfully verified prior to increasing the spending limit for the CPN or otherwise making the CPN available for use by the payee 116.

Processing Server

FIG. 2 illustrates an embodiment of the processing server 102 of the system 100. It will be apparent to persons having skill in the relevant art that the embodiment of the processing server 102 illustrated in FIG. 2 is provided as

illustration only and may not be exhaustive to all possible configurations of the processing server 102 suitable for performing the functions as discussed herein. For example, the computer system 900 illustrated in FIG. 9 and discussed in more detail below may be a suitable configuration of the processing server 102.

The processing server 102 may include a receiving unit 202. The receiving unit 202 may be configured to receive data over one or more networks via one or more network protocols. In some embodiments, the receiving unit 202 may be configured to receive data over the payment rails, such as using specially configured infrastructure associated with payment networks 108 for the transmission of transaction messages mat include sensitive financial data and information. In some instances, the receiving unit 202 may also be configured to receive data from computing devices such as payer device 112 and payee device 118, NFI entities 104, financial institutions 106, and other entities via alternative networks, such as the Internet. In some embodiments, the receiving unit 202 may be comprised of multiple units, such as different receiving units for receiving data over different networks, such as a first receiving unit for receiving data over payment rails and a second receiving unit for receiving data over the Internet The receiving unit 202 may receive data signals that are electronically transmitted, where data may be superimposed on the data signal and decoded, parsed, read, or otherwise obtained via receipt of the data signal by the receiving unit 202. In some instances, the receiving unit 202 may include a parsing module for parsing the received data signal to obtain the data superimposed thereon.

The receiving unit 202 may receive data communications from the NFI entity 104, payer device 112, payee device 118, etc., which may utilize the Internet, local area networks, or other suitable networks and associated protocols. The receiving unit 202 may also be configured to receive transaction messages.

Transaction messages may be formatted pursuant to one or more standards, such as the International Organization for Standardization's ISO 8583 standard, and may include a plurality of data elements. Each data element in the transaction message may be configured to store data based on me associated standards. In some instances, transaction messages may also include additional data, such as message type indicators.

The processing server 102 may also include an account database 208. The account database 208 may be configured to store a plurality of account profiles 210 using a suitable data storage format and schema. The account database 208 may be a relational database mat utilizes structured query language for the storage, identification, modification, updating, accessing, etc. of structured data sets sored therein. Each account profile 210 may be a structured data set configured to store data related to a user account associated with the NFI entity 104. Each account profile 210 may include at least a CPN associated with the related user account and a spending limit for the CPN. The spending limit may be represented in the currency of the transaction account associated with the CPN, or may be represented in a different currency as established by the NFI entity 104. The spending limit may be such mat transactions conducted involving the CPN may be subject to the spending limit, or an equivalent amount in a related fiat currency, and may not be conducted if the transaction amount exceeds the spending limit. The spending limit may be adjusted as a result of payment transactions, including user-to-merchant transactions, user-to-user transactions, and transactions involving the purchase of additional currency by the related user. In some instances, an account profile 210 may include an account identifier and an address, such as in instances where the related user account has not had the associated user identity verified. In such instances, a CPN may not be included in the account profile 210, or the account profile 210 may include a CPN that has not been provided to the related user or for which the spending limit is at zero or otherwise inaccessible.

The processing server 102 may also include a communication module. The communication module may be configured to transmit data between modules, engines, databases, memories, and other components of the processing server 102 for use in performing the functions discussed herein. The communication module may be comprised of one or more communication types and utilize various communication methods for communications within a computing device. For example, the communication module may be comprised of a bus, contact pin connectors, wires, etc. In some embodiments, the communication module may also be configured to communicate between internal components of the processing server and external components of the processing server 102, such as externally connected databases, display devices, input devices, etc.

The processing server 102 may further include a processing unit 204. The processing unit 204 may be configured to perform the functions of the processing server 102 as discussed herein as will be apparent to persons having skill in the relevant art In some embodiments, the processing unit 204 may include and/or be comprised of a plurality of engines and/or modules specially configured to perform one or more functions of the processing unit 204. For example, the processing unit 204 may include a querying module configured to query databases, such as the account database 208, included in the processing server 102 to identify information stored therein. In some instances, the processing unit 204 may include a parsing module or engine configured to parse data from data signals electronically received by die receiving unit 202, an encryption module or engine configured to decrypt received data or data signals or to encrypt data or data signals received or transmitted by die processing server 102, and any other modules suitable for performing the functions discussed herein. The processing unit 204 may be configured to process transactions involving users of the NFI entity 104 based on transaction messages and transaction requests received by the receiving unit 202.

For example, if the receiving unit 202 receives a transaction message for the purchase of currency by a user, the processing unit 204 may be configured to initiate a payment transaction for payment from the user to the NFI entity's transaction account and for the increase and/or establishment of a spending limit for a CPN associated with the user based on the transaction amount. The transaction message may be forwarded to the payment network 108 for processing of payment from the user. In some instances, the processing unit 204 may generate a new transaction message for submission to the payment network 108 for payment from die user to the NFI entity 104.

The processing unit 204 may also generate a request to submit to the financial institution 106 or payment network 108 as applicable (e.g., depending on which entity may control usage of the CPN) to increase the spending limit of a CPN associated with the user. The CPN may be identified in the transaction message, or may be identified in a separate message provided by the user or the NFI entity 104. In some instances, an account identifier associated with the user account may be provided, which may be used by the processing unit 204 to identify an account profile 210 stored in the account database 208, which may be used to identify the CPN for which the spending limit is to be increased. In instances where a user may purchase currency without having a previously established CPN, the processing unit 204 may generate a request for issuance of a CPN for use by the user, with the spending limit being based on the transaction amount. In some cases, the spending limit may be

adjusted by an amount different from the transaction amount, such as due to processing fees.

The processing unit 204 may be configured to identify such a transaction via data included in the received transaction message. For instance, a data element in the transaction message may be configured to store an indication that the transaction is for the purchase of currency. In another instance, if the payee account number included in a corresponding data element in the transaction message is an account number associated with the transaction account of the NFI entity 104 for which CPNs are to be associated, then the transaction may be indicative of one for the purchase of currency by a user.

In another example, the receiving unit 202 may receive a transaction message from a merchant 114 for a user-to-merchant transaction. In some instances, the receiving unit 202 may receive a copy of a transaction message used in a user-to-merchant transaction from the payment network 108. In yet another instance, the financial institution 106 and/or NFI entity 104 may provide the processing server 102 with data associated with a user-to-merchant transaction (e.g., which was drawn on the transaction account of the NFI entity 104 via a CPN). The processing unit 204 may be configured to submit a request to the financial institution 106 or payment network 108 as applicable to decrease the spending limit associated with the CPN used in the payment transaction.

In yet another example, the receiving unit 202 may receive a transaction request from a payer device 112, payee device 118, and/or NFI entity 104 for a user-to-user transaction. The processing unit 204 may generate a request for submission to the applicable entity to decrease the spending limit of the CPN associated with the payer 110 by the transaction amount, and a request for submission to increase the spending limit of the CPN associated with the payee 116 by the transaction amount.

The processing unit 204 may also be configured to verify a user identity for a user associated with a user account related to an account profile 210. For example, if the receiving unit 202 receives a transaction request to in a user-to-user transaction, the processing unit 204 may identify an account profile 210 associated with the payee 116 using an account identifier or a CPN included in the transaction request The processing unit 204 may identify that the identity of die payee 116 has not been verified, such as based on an account flag, a lack of

identification data, a lack of a CPN, an inaccessible spending limit, etc. The processing unit 204 may then initiate a process for verifying the identity of the payee 116 using the methods discussed herein, which may include providing the account identifier to a third party entity and receiving, by the receiving unit 202, identification data for the payee 116. The processing unit 204 can then update the account profile 210 to include the identification data. In some embodiments, the processing unit 204 may first await receipt (e.g., by the receiving unit 202) of a notification that the identification data has been successful verified, such as by the financial institution 106 or other entity.

The processing unit 204 may also be configured to perform any additional functions of the processing server 102 suitable for performing the methods and systems discussed herein. For example, the processing unit 204 may be configured to perform currency conversions, generate account alerts, generate notifications, etc.

The processing server 102 may also include a transmitting unit 206.

The transmitting unit 206 may be configured to transmit data over one or more networks via one or more network protocols. In some embodiments, the transmitting unit 206 may be configured to transmit data over the payment rails, such as using specially configured infrastructure associated with payment networks 108 for the transmission of transaction messages that include sensitive financial data and information, such as identified payment credentials. In some instances, the transmitting unit 206 may be configured to transmit data to computing devices, such as payer device 112 and payee device 118, payment networks 108, NFI entities 104, financial institutions 106, and other entities via alternative networks, such as the Internet In some embodiments, the transmitting unit 206 may be comprised of multiple units, such as different transmitting units for transmitting data over different networks, such as a first transmitting unit for transmitting data over the payment rails and a second transmitting unit for transmitting data over the Internet. The transmitting unit 206 may electronically transmit data signals that have data superimposed that may be parsed by a receiving computing device. In some instances, the transmitting unit 206 may include one or more modules for superimposing, encoding, or otherwise formatting data into data signals suitable for transmission.

The transmitting unit 206 may be configured to transmit transaction messages to the payment network 108 using associated communication protocols, may be configured to transmit data requests to the financial institution 106 and/or payment network 108 requesting issuance of CPNs and adjustments of spending limits for CPNs, may be configured to transmit notifications to the NFI entity 104 regarding transactions and CPN adjustments, may be configured to transmit notifications to payer devices 112 and payee devices 118 regarding transactions, etc. The transmitting unit 206 may also be configured to transmit CPNs to users (e.g., via payer and payee devices 112 and 118) or to third parties for use in issuing physical payment cards or other payment instruments to users and/or verification of user identities. The transmitting unit 206 may also transmit notifications to third parties that include account identifiers and other account information suitable for use in the verification of user identities. In such instances, the transmitting unit 206 may also be configured to transmit received identification data to financial institutions 106 and other entities for use in further verification of user identities.

The processing server 102 may further include a memory 212. The memory 212 may be configured to store data for the processing server 102 suitable for performing the functions disclosed herein. The memory 212 may be configured to store data using suitable data formatting methods and schema and may be any suitable type of memory, such as read-only memory, random access memory, etc. For example, the memory 212 may be configured to store data formatting rules and algorithms (e.g., associated with transaction messages standards), communication protocol data, currency exchange rates and algorithms, encryption keys and algorithms, program code for modules and application programs of the processing unit 204, etc. Additional data that may be stored in the memory 212 will be apparent to persons having skill in the relevant art. In some embodiments, the memory 212 may be comprised of or may otherwise include a relational database that utilizes structured query language for the storage, identification, modifying, updating, accessing, etc. of structured data sets stored therein.

Process for Crediting a User Account

FIGS. 3A and 3B illustrate a process for the crediting of a user account via increase of a spending limit of a CPN associated with the user account with the NFI entity 104.

In step 302, the payer 110 may utilize the payer device 112 to register a user account with the NFI entity 104. As part of the registration, registration data may be submitted by the user to the NFI entity 104, which may receive the data in step 304. The registration data may include a usemame, password, e-mail address, and any other data mat may be suitable dependent on the NFI entity 104 and the services provided to the payer 110. In step 306, the NFI entity 104 may generate a user account, which may include the storage of user registration data in an internal or external database.

In step 308, the NFI entity 104 may request a CPN from the financial institution 106 or payment network 108 (not shown), as applicable, and register the CPN as being associated with the new user account. In step 310, the NFI entity 104 may transmit account information associated with the user account to the processing server 102, which may be received by the receiving unit 202. The account information may include at least the CPN associated with the account, and may also include any other data that may be suitable for performing the functions disclosed here, such as a user identifier (e.g., usemame, e-mail address, user identification number, etc.). In some embodiments, the CPN may be requested by the processing server 102. In such an embodiment, the processing server 102 may request the CPN following receipt of the user account information, and may provide the CPN to the NFI entity 104 for registration.

In step 312, the processing unit 204 of the processing server 102 may generate an account profile 210 to be associated with the new user account and store the account profile 210 in the account database 208. The account profile 210 may include at least the CPN and a spending limit associated thereto. In some instances, the CPN, as initially requested, may have a zero spending limit.

In step 314, the payer 110 may initiate a purchase to credit their user account via the payer device 112. The purchase may be initiated via use of the platform provided by the NFI entity 104 (e.g., such as a social network) and may be for the purchase of a specified amount of currency. In step 316, the NFI entity 104 may receive purchase information submitted by the payer 110 via the payer device 112 in the initiation of the transaction, which may include at least the currency amount to be purchased and payment credentials for funding of the payment transaction. In step 318, the NFI entity 104 may submit to the processing server 102 an authorization request for the payment transaction from the payer 110 to the NFI entity 114. In some embodiments, the authorization request may be submitted by a third party, such as the financial institution 106 or other third party configured to process transactions on behalf of the NFI entity 104. In such instances, the purchase information submitted by the payer 110 in step 316 may be submitted to the third party, such that the NFI entity 104 may not possess or come into contact with payer payment credentials.

In step 320, the receiving unit 202 of the processing server 102 may receive the authorization request The authorization request may be a transaction messages formatted pursuant to one or more standards and include a plurality of data elements. The data elements may include at least a data element configured to store a primary account number and a data element configured to store a transaction amount In some embodiments, the authorization request may also include a data element configured to store a user identifier or CPN, which may be provided by the payer 110 or the NFI entity 104. In some instances, the CPN may be included as a payee of the transaction, such that payment may be made to the transaction account associated with the NFI entity 104 via the association of the CPN with the transaction account.

In step 322, the processing unit 204 of the processing server 102 may process the payment transaction. Processing of the payment transaction may include forwarding, by the transmitting unit 206 of the processing server 102, the transaction message to a payment network 108. In some embodiments, the processing unit 204 may be required to generate a transaction message to forward to the payment network 108, such as in instances where the data may come to the processing server 102 in a format not suitable for transmission to the payment network 108.

In step 324, the transmitting unit 206 may transmit a request to the financial institution 106 or payment network 108, as applicable, to increase the spending limit of the CPN based on the transaction amount In some instances, the spending limit may be increased based on the transaction amount on a 1:1 basis. In other instances, the spending limit may be increased by an amount less than the transaction amount, and/or may be increased by an amount of a different currency based on a currency exchange rate. In embodiments where the authorization request may not include the CPN, step 324 may also include identification of an account profile 210 associated with the user involved in the transaction for identification of the CPN to be included in the request to increase the spending limit. In such embodiments, the transaction message may include a user identifier or other suitable value, which may be included in a query ran on the account database 208 by the processing unit 204 to identify the account profile 210 associated with the user involved in the transaction.

In step 326, the receiving unit 202 of the processing server 102 may receive an authorization response from the payment network 108 for the payment transaction, and the transmitting unit 206 of the processing server 102 may forward the authorization response on to the NFI entity 104 (e.g., or other third party acting on behalf of the NFI entity 104). In step 328, the NFI entity 104 may receive the authorization response, which may indicate successful or unsuccessful processing of the payment transaction.

In step 330, the NFI entity 104 may transmit a notification to the payer 110 via the payer device 112 indicating the balance of their account following receipt of the authorization response. For example, if the authorization response indicates that the transaction was successful, then the spending limit for the CPN will have been increased. In some embodiments, the processing server 102 may provide an additional message (e.g., separate from and/or accompanying the authorization response) indicative of the increasing of the spending limit of the CPN. In step 332, the payer device 112 may receive the notification of account credit, which may be displayed to the payer 110 to notify the payer 110 of their current amount of currency available for use via their user account.

Process for User-to-Merchant Transactions

FIGS. 4A and 4B illustrate a process for a user-to-merchant transaction involving a user account with the NFI entity 104 and an external merchant 114 via the CPN associated with the user account

In step 402, the payer 110 may initiate a payment transaction with a merchant 114 using their payer device 112, which may include the transmission of payment credentials associated with the CPN to the merchant 114. In some embodiments, the payment transaction may be an in-person transaction, which may be initiated by the payer 110 providing payment credentials associated with the CPN to the merchant 114 at a point of sale, such as via a physical card encoded with payment credentials associated with the CPN or via the payer device (e.g., using near field communication). In step 404, the merchant 114 may receive the payment credentials, which may include at least the CPN associated with the user account

In step 406, the merchant 114 (e.g., or a third party entity acting on behalf of the merchant, such as a financial institution, such as an acquiring bank, the financial institution 106, etc.) may generate an authorization request for the payment transaction. The authorization request may be a transaction message formatted pursuant to one or more standards, which may include a message type indicator indicative of an authorization request, and may include a plurality of data elements including at least a data element configured to store a primary account number that includes the CPN and a data element configured to store a transaction amount. In step 408, the merchant 114 (or a third parry entity) may submit the authorization request to the processing server 102.

In step 410, the receiving unit 202 of the processing server 102 may receive the authorization request In step 412, the processing unit 204 of the processing server 102 may identify the account profile 210 associated with the payer 110 involved in the transaction. The account profile 210 may be identified via querying of the account database 208 using the CPN stored in the data element of the authorization request configured to store a primary account number. In step 414, the payment transaction may be processed, which may be performed via the forwarding of the authorization request to the payment network 108 by the transmitting unit 206 of the processing server 102. In step 416, an authorization response may be received from the payment network 108 and may be forwarded on to the merchant 114. In step 418, the merchant 114 may receive the authorization response. In some

embodiments, the authorization request may be initially submitted to the payment network 108, which may forward the authorization request, a copy thereof, and/or transaction data included therein to the processing server 102, which may be received by the processing server 102 in step 410. In such embodiments, the authorization response and/or an indication included therein may be forwarded to both the merchant 114 and the processing server 102 by the payment network 108.

In step 420, the merchant 114 may finalize the payment transaction based on the received authorization response. For example, if the authorization response indicates that the transaction was approved, the merchant 1 14 may provide the payer 110 with the transacted-for goods or services, which may be received by the payer 110 in step 422. If the authorization response indicates that the transaction was denied, the merchant 114 may inform the payer 110 and may withhold providing any goods or services to the payer 110.

In step 424, the processing unit 204 of the processing server 102 may generate a request, which may be submitted to the financial institution 106 or payment network 108, as applicable, requesting decrease of the spending limit associated with the CPN used in the payment transaction. The request may include at least the CPN and the transaction amount for the payment transaction. The spending limit for the CPN may be adjusted accordingly, and, in step 426, the transmitting unit 206 may transmit a notification to the payer 110, via the payer device 112. In some embodiments, the notification may be transmitted to the NFI entity 104, which may, in turn, transmit a notification to the payer 110, via the payer device 112. In step 428, the payer device 112 may receive the notification and display it to the payer 110, which may notify the payer of the credit (e.g., currency amount) still available for use via their user account, which may correspond to the spending limit still available with the associated CPN.

Process for User-to-User Transactions

FIG. 5 illustrates a process for a user-to-user transaction involving user accounts with the NFI entity 104 via the use of CPNs such that funds may be transferred without the use of the payment network 108.

In step 502, the payer 110 may, via the payer device 112, initiate a transaction for payment of credits (e.g., or other currency associated with the NFI entity 104) to the payee 116. The transaction may be initiated using the payer device 112 via a website, application program, or other suitable method provided by the NFI entity 104 or on behalf of the NFI entity 104. In step 504, the receiving unit 202 of the processing server 102 may receive a transaction request for the transaction. The transaction request may include at least the CPN associated with the payer 110, the CPN associated with the payee 116, and the transaction amount In some

embodiments, the transaction request may be a transaction message formatted pursuant to one or more applicable standards, with the included data being comprised in one or more data elements.

In step 506, the processing unit 204 of the processing server 102 may identify a payer account profile 210 in the account database 208 and a payee account profile 210 in the account database 208. The account profiles 210 may be identified by inclusion of the CPNs included in the received transaction request In step S08, the processing unit 204 may decrease the account spending limit for the payer account profile 210, which may be accomplished by transmitting, via the transmitting unit 206, an instruction to the financial institution 106 or payment network 108, as applicable, to decrease the spending limit of the corresponding CPN. In step 510, the processing unit 204 may increase the account spending limit for the payee account profile 210, such as by transmitting, via the transmitting unit 206, a corresponding instruction to me relevant entity.

In step 512, the transmitting unit 206 may transmit a notification to the payer 110 via the payer device 112, to inform the payer 110 of the remaining credits (e.g., available spending limit) in the user account. In step 514, the payer 110 may receive the notification via the payer device 112, which may be displayed to the payer 110 using known methods. In step 516, the transmitting unit 206 of the processing server 102 may transmit a notification to the payee 116, via the payee device 118, to inform the payee 116 of their available credits in their user account. In step 518, the payee 116 may receive the notification via the payee device 118, which may be displayed to the payee 116 using known methods.

Processing of User Account Transactions

FIG. 6 illustrates a process 600 for the processing of transactions involving user accounts with. the NFI entity 104 by the processing server 102 via the use of CPNs.

In step 602, the processing server 102 may store a plurality of account profiles 210 in the account database 208. Each account profile 210 may include at least a CPN and a spending limit, and may also include additional account information associated with a related user account with the NFI entity 104, such as a user identifier. In step 604, the receiving unit 202 of the processing server 102 may receive a transaction request The transaction request may be a transaction message formatted pursuant to one or more standards, or may be another suitable type of data message. In step 606, the processing unit 204 of the processing server 102 may determine what type of transaction the received transaction request is for.

The determination may be based on the type of transaction request received, data stored in the transaction request, one or more entities involved m the request, etc. For instance, if the transaction request includes a user identifier and a transaction account and/or the transaction account corresponds to the transaction account associated with the NFI entity 104, the transaction may be a credit transaction. If the transaction is a credit transaction, then, in step 608, the processing unit 204 may process the payment transaction for the purchase of currency with the NFI entity 104. Processing of the payment transaction may include forwarding an authorization request to the payment network 108 for processing.

In step 610, the processing unit 204 may determine if the transaction was successful. The determination may be made based on an authorization response received from the payment network 108 and a response code or other data included therein, which may be stored in one or more data elements of the authorization response as based on associated standards. If the transaction is unsuccessful, then, in step 612, the transmitting unit 206 of the processing server 102 may transmit a notification to the NFI entity 104 and/or user involved in the transaction that the transaction was unsuccessful. In some instances, the notification may include a reason, which may be included in the received authorization response.

If the transaction is successful, men, in step 614, the processing unit 204 may increase the spending limit associated with the user account involved in the transaction. This may include the identification of a corresponding account profile 210 using the CPN and/or user identifier included in the received authorization request, and then submitting (e.g., via the transmitting unit 206) a request to the financial institution 106 or payment network 108, as applicable, to increase the spending limit for the CPN. In step 616, the transrnming unit 206 may transmit a notification to the NFI entity 104 and/or user (e.g., via a corresponding user device) indicating that the transaction was approved, and that the spending limit has been increased.

If, in step 606, it is determined that the transaction is for the transfer of funds from the user to another parry, then, in step 618, the processing unit 204 may identify an account profile 210 stored in the account database 208 associated with a payer 110 involved in the transaction. The account profile 210 may be identified via a CPN included in a data element of the received transaction message configured to store a personal account number. In step 620, the spending limit for the CPN

included in the identified account profile 210 may be decreased. The spending limit may be decreased via the transmission of a request by the transmitting unit 206 to the financial institution 106 or payment network 108, as applicable, for reduction in the spending limit by a transaction amount included in the transaction request, such as included in a data element configured to store a transaction amount in the transaction message.

In step 622, the processing unit 204 may determine if the payee for the transaction is another user (e.g., the payee 116) or a merchant 114. The payee may be determined based on the recipient included in the received transaction request, and/or the type of request For example, if the transaction request is not a message, and/or the recipient is a CPN or user identifier, then the payee may be determined to be another user of the NFI entity 104. If the payee is determined to be a merchant 114, then, in step 624, the processing unit 204 may process a payment transaction for payment to the merchant 114. The payment transaction may be drawn on the transaction account of the NFI entity 104, as a result of use of the CPN associated with the payer 110, which may be tied to the NFI entity's transaction account. In step 626, an authorization response may be received by the receiving unit 202 from the payment network 108 due to processing of the payment transaction, which may be forwarded on to the merchant 114, an acquiring bank, the NFI entity 104, and/or to the payer 110 via the payer device 112 by the transmitting unit 206.

If, in step 622, the processing unit 204 determines that the payee is not a merchant 114 but another user of the NFI entity 104, then, in step 628, the processing unit 204 may identify an account profile 210 in the account database 208 associated with the payee 116 based on inclusion of a CPN included as the recipient in the received transaction request, and may submit a request to the financial institution 106 or payment network 108, as applicable, to increase the spending limit of the CPN. In step 630, the transmitting unit 206 may transmit a notification to the payer 110 and payee 116 to notify the respective users of the adjustments to their spending limit based on the transaction. In some instances, the processing server 102 may notify the NFI entity 104, which may notify the users of the transaction and resulting account balances.

Process for Verifying User Identities

FIGS. 7A and 7B illustrate a process for the verification of a user identity for a payee 116 associated with a user account of the NFI entity 104.

In step 702, the receiving unit 202 of the processing server 102 may receive a transaction request for a user-to-user or other payment transaction where the payee 116 is to receive currency of the NFI entity 104 that may be usable in user-to-merchant transactions. The transaction request may include at least an account identifier associated with the user account corresponding to the payee 116 and a transaction amount. The transaction amount may be or may be used to identify the value of currency to be provided to the payee 116.

In step 704, the processing unit 204 of the processing server may identify an account profile 210 in the account database 208 related to the user account corresponding to the payee 116. The account profile 210 may include the account identifier that is included in the received transaction request. In step 706, the processing unit 204 may generate a CPN for use by the payee 116 in future transactions. The CPN may be associated with the transaction account of the NFI entity 104 and may have a spending limit that is zero or is otherwise inaccessible or unusable by the payee 116 prior to identity verification. In some embodiments, the account profile 210 related to the payee 116 may already include a CPN. In such instances, step 706 may include verification by the processing unit 204 that the account profile 210 does not include identification data for the payee 116 and/or that identification data for the payee 116 is required.

In step 708, the transmitting unit 206 of the processing server 102 may transmit at least the account identifier to a third party 700 for use in verification of the identity of the payee 116. In some embodiments, the transmitting unit 206 may also transmit the CPN to the third party 700 or other data associated with the CPN, such as a payment card encoded with the CPN or information associated therewith. For example, the processing server 102 may initiate the encoding of a physical payment card with the CPN, which may be sent to the third party 700 along with the account identifier, to provide to the payee 116 in exchange for the identification information. In step 710, the third party 700 may receive the account information from the processing server 102.

In step 712, the transmitting unit 206 of the processing server 102 may transmit the CPN for distribution to the payee 116. In some embodiments, the CPN

may be directly transmitted to the payee 116, such as in an electronic transmission to the payee device 118 (e.g., for storage in an electronic wallet application program). In other embodiments, the CPN may be encoded in a physical payment card or other payment instrument that may be distributed to the payee 116. It will be apparent to persons having skill in the relevant art that in embodiments where the CPN may have been provided to the third party 700 in step 708, then step 712 may be performed by the third party 700. In step 714, the payee 116 may receive the controlled payment number and, if applicable, any payment instrument associated therewith.

In step 716, the payee 116 may provide identification to the third party 700. Identification may include a name, identification number, date of birth, age, gender, signature, image, biometric data, or any other suitable data. For example, the payee 116 may sign for a payment instrument, may allow the third party 700 to make a photo of the payee 116, may provide the third party 700 with a government-issued picture identification card, may provide the third party 700 with a fingerprint scan, etc. In step 718, the third party 700 may receive or otherwise obtain the identification data from the payee 116.

In step 720, the third party 700 may provide the identification data to the processing server 102. The identification data may also include the account identifier included in the account profile 210 associated with the payee 116. In step 722, the receiving unit 202 of the processing server 102 may receive the identification data and included account identifier, such as for the processing unit 204 to use to ensure that the identification data is associated with the correct account profile 210. In step 724, the processing server 102 may perform further verification with an issuing financial institution, such as the financial institution 106 associated with the transaction account of the NFI entity 104 (e.g., from which the CPN draws funds). The further verification may include the transmitting of the identification data to the financial institution 106, who may perform additional verification, and the receipt of a notification from the financial institution 106 indicating of the additional verification was successful. The additional verification may include the checking of the identification data against publicly available data or other data, such as public records, government agency data, credit bureau data, account data for customers of the financial institution 106, etc. For example, the financial institution 106 may verify that a name included in the identification data matches a government-issued identification number also included in the identification data, with agency records. In some embodiments, the identification data may be transmitted directly to the financial institution 106 (e.g., in step 720), with the processing server 102 receiving the notification from the financial institution 106 in step 724.

In step 726, the processing unit 204 may increase the spending limit included in the account profile 210 for the CPN provided to the payee 116 based on the transaction amount. The payee 116 may then be able to use the CPN in user-to-merchant transactions based on the spending limit. In some instances, the transmitting unit 206 of the processing server 102 may transmit a notification to the payee 116 (e.g., to the payee device 118 associated with the payee 116) indicating mat the CPN is available for use and/or that the spending limit is increased.

Exemplary Method for Providing Credit for a User Account

FIG. 8 illustrates a method 800 for the providing of credit to a user account with an NFI entity 104 via the spending limit of a CPN.

In step 802, a plurality of account profiles (e.g., account profiles 210) may be stored in an account database (e.g., the account database 208), wherein each account profile 210 includes data related to a user account corresponding to a non-financial institution (NFI) entity (e.g., the NFI entity 104) including at least a controlled payment number (CPN) and a spending limit, wherein the CPN is associated with a transaction account associated with the corresponding NFI entity 104 and is subject to the spending limit when used to fund a payment transaction. In some embodiments, payment transactions involving a CPN included in a stored account profile 210 may be drawn against the associated transaction account

In step 804, a transaction message for a payment transaction may be received by a receiving device (e.g., the receiving unit 202), wherein the transaction message is formatted based on one or more standards and includes a plurality of data elements including at least a first data element configured to store a transaction account number associated with the transaction account associated with the corresponding NFI entity 104 and a second data element configured to store a transaction amount. In one embodiment the transaction message may further include a message type indicator indicative of an authorization request

In step 806, a specific account profile 210 stored in the account database 208 may be identified by a processing device (e.g., the processing unit 204). In one embodiment the transaction message may further include a third data element configured to store a CPN, and the specific account profile 210 may be identified based on inclusion of a CPN that corresponds to the CPN stored in the third data element included in the received transaction message. In step 808, the spending limit included in the identified specific account profile 210 may be increased by the processing device 204 based on the transaction amount stored in the second data element included in the received transaction message.

In one embodiment, the transaction message may further include a third data element configured to store a transaction account number associated with a payer (e.g., the payer 110), and the method 800 may further include processing, by the processing device 204, the payment transaction for payment of the transaction amount from a transaction account associated with the transaction account number associated with the payer 110 to the transaction account associated with the corresponding NFI entity 104. In a further embodiment, the method 800 may even further include transmitting, by a transmitting device (e.g., the transmitting unit 206), a response message formatted based on the one or more payment network standards in response to the received transaction messaged based on a result of the processing of the payment transaction.

In some embodiments, the method 800 may also include receiving, by the receiving device 202, an account adjustment request from an NFI entity 104, wherein the account adjustment request includes at least a specific CPN associated with a transaction account associated with the NFI entity, and wherein the specific account profile 210 is identified based on inclusion of the specific CPN included in the received account adjustment request In a further embodiment, the account adjustment request may further include an adjustment amount based on the transaction amount stored in the second data element included in the received transaction message, and the spending limit included in the identified specific account profile 210 may be increased by the adjustment amount included in the received account adjustment request In an even further embodiment, the adjustment amount and the spending limit may be associated with a virtual, non-fiat currency.

Exemplary Method for Processing Transactions in User Accounts

FIG. 9 illustrates a method 900 for the processing of user-to-user transactions for user accounts of an NFI entity 104 using CPNs.

In step 902, a plurality of account profiles (e.g., account profiles 210) may be stored in an account database (e.g., the account database 208), wherein each account profile 210 includes data related to a user account corresponding to a non-financial institution (NFI) entity (e.g., the NFI entity 104) including at least a controlled payment number (CPN) and a spending limit, and wherein the CPN is associated with a transaction account associated with the corresponding NFI entity and is subject to the spending limit when used to fund a payment transaction. In one embodiment, payment transactions involving a CPN included in a stored account profile 210 may be drawn against the associated transaction account

WHAT IS CLAIMED IS:

1. A method for verification of user identity, comprising:

storing, in an account database, a plurality of account profiles, each account profile including data related to a user account of a non-financial institution (NFI) entity, said data including at least an account identifier and an address;

receiving, by a receiving device, a transaction request, wherein the transaction request includes at least a specific account identifier and a transaction amount;

identifying, by a processing device, a specific account profile stored in the account database where the included account identifier corresponds to the specific account identifier;

generating, by the processing device, a controlled payment number, wherein the controlled payment number is associated with a transaction account of the NFI entity;

transmitting, by a transmitting device, a notification to a third party entity, wherein the notification includes at least the specific account identifier;

transmitting, by the transmitting device, the generated controlled payment number for distribution to a user associated with the user account related to the specific account profile;

receiving, by the receiving device, a data message from the third party entity, wherein the data message includes at least the specific account identifier and identification data associated with the user; and

updating, by the processing device, the specific account profile in the account database to include at least the generated controlled payment number, the

identification data, and a spending limit, wherein the spending limit is based on the transaction amount and where payment transactions involving the controlled payment number are subject to the spending limit

2. The method of claim 1, wherein the specific account profile is updated to include the controlled payment number and the spending limit prior to receiving the data message from the third party entity and updating the specific account profile to include the identification data.

3. The method of claim 2, wherein the spending limit in the specific account profile cannot be increased until the specific account profile is updated to include the identification data associated with the user.

4. , The method of claim 1, wherein transmitting the generated controlled payment number includes electronically transmitting the generated controlled payment number to a mobile device associated with the address included in the specific account profile.

5. The method of claim 1, wherein the generated controlled payment number is transmitted to a payment card engine configured to encode the generated controlled payment number in a physical payment card for distribution to the user using the address included in the specific account profile.

6. The method of claim 1 , wherein the identification data includes at least one of: an identification number, name, date of birth, age, gender, signature, image, and biometric data.

7. The method of claim 1 , further comprising:

transmitting, by the transmitting device, at least the identification data and the specific account identifier to a financial institution associated with the transaction account of the NFI entity.

8. The method of claim 7, further comprising:

receiving, by the receiving device, a verification from the financial institution, wherein the verification includes at least the specific account identifier and an indication of verification of the identification data.

9. The method of claim 8, wherein the verification is received prior to updating the specific account profile.

10. The method of claim 1, wherein

the address included in the specific account profile is associated with a geographic area, and

the third party entity is associated with the geographic area.

11. A system for verification of user identity, comprising:

an account database configured to store a plurality of account profiles, each account profile including data related to a user account of a non-financial institution (NFI) entity, said data including at least an account identifier and an address;

a receiving device configured to receive a transaction request, wherein the transaction request includes at least a specific account identifier and a transaction amount;

a processing device configured to

identify a specific account profile stored in the account database where the included account identifier corresponds to the specific account identifier, and generate a controlled payment number, wherein the controlled payment number is associated with a transaction account of the NFI entity; and

a transmitting device configured to transmit

a notification to a third party entity, wherein the notification includes at least the specific account identifier, and

the generated controlled payment number for distribution to a user associated with the user account related to the specific account profile, wherein

the receiving device is further configured to receive a data message from the third party entity, wherein the data message includes at least the specific account identifier and identification data associated with the user, and

the processing device is further configured to update the specific account profile in the account database to include at least the generated controlled payment number, the identification data, and a spending limit, wherein the spending limit is based on the transaction amount and where payment transactions involving the controlled payment number are subject to the spending limit

12. The system of claim 11 , wherein the specific account profile is updated to include the controlled payment number and the spending limit prior to receiving the data message from the third party entity and updating the specific account profile to include the identification data.

13. The system of claim 12, wherein the spending limit in the specific account profile cannot be increased until the specific account profile is updated to include the identification data associated with the user.

14. The system of claim 11 , wherein transmitting the generated controlled payment number includes electronically transmitting the generated controlled payment number to a mobile device associated with the address included in the specific account profile.

15. The system of claim 11, wherein the generated controlled payment number is transmitted to a payment card engine configured to encode the generated controlled payment number in a physical payment card for distribution to the user using the address included in the specific account profile.

16. The system of claim 11, wherein the identification data includes at least one of: an identification number, name, date of birth, age, gender, signature, image, and biometric data.

17. The system of claim 11, wherein the transmitting device is further configured to transmit at least the identification data and the specific account identifier to a financial institution associated with the transaction account of the NFI entity.

18. The system of claim 17, wherein the receiving device is further configured to receive a verification from the financial institution, wherein the verification includes at least the specific account identifier and an indication of verification of the identification data.

19. The system of claim 18, wherein the verification is received prior to updating the specific account profile.

20. The system of claim 11, wherein

the address included in the specific account profile is associated with a geographic area, and

the third party entity is associated with the geographic area.