Patent Publication Number: US-2023142487-A1

Title: Identification and verification for provisioning mobile application

Description:
RELATED APPLICATIONS 
     This application is a continuation application of U.S. patent application Ser. No. 17/307,861, filed May 4, 2021, and entitled “IDENTIFICATION AND VERIFICATION FOR PROVISIONING MOBILE APPLICATION,” which is a continuation application of U.S. patent application Ser. No. 14/732,458, filed Jun. 5, 2015 and entitled “IDENTIFICATION AND VERIFICATION FOR PROVISIONING MOBILE APPLICATION,” which claims the benefit of and priority to U.S. Provisional Application No. 62/008,399, filed Jun. 5, 2014 and entitled “IDENTIFICATION AND VERIFICATION FOR PROVISIONING MOBILE APPLICATION,” the entire disclosure of which is incorporated herein by reference for all purposes. 
    
    
     BACKGROUND 
     In a traditional electronic payment transaction, a consumer&#39;s primary account number (PAN) information is exposed to various entities involved during the transaction lifecycle. The PAN is passed from a merchant terminal, to an acquirer system, a payment processing network, payment gateways, etc. Because the PAN can be exposed at various points in the transaction lifecycle, some have suggested that payment “tokens” be used to conduct payment transactions. A token serves as an additional security layer to the PAN and in effect becomes a proxy/surrogate to the PAN and may be used in place of PAN while submitting transactions. 
     While conventional efforts to use payment tokens have been useful, a number of additional problems need to be solved. For example, when a user device is used to conduct payment transactions, it is difficult to accurately identify the user and bind the user&#39;s identity to the user device via a token, particularly in environments where it is not possible to obtain a static or a unique device ID. 
     Embodiments of the invention address these and other problems, individually and collectively. 
     BRIEF SUMMARY 
     In some embodiments of the invention, a token ecosystem is provided. The token ecosystem provides a platform that can be leveraged by various entities such as third party wallet providers, merchants, acquirers, payment processors, etc. that use tokens to facilitate payment transactions. In the token ecosystem, a token provider, such as a cloud based payment service, may issue tokens based on requests from a token requestor. The token requestor may be a mobile application, such as a merchant mobile application provisioned on a user device. The token provider may receive identifying data from the token requestor. The token provider may issue tokens with varying status based on a confidence level determined in light of the data received from the token requestor. 
     According to some embodiments, a method includes receiving, by a server computer, a first set of user information from at least one of a first mobile application or an authorizing server. The first mobile application may be installed/provisioned on a user device, such as a mobile phone of the user. In some embodiments, the authorizing server may have provisioned the first mobile application on the user mobile device. The first set of user information may include one or more of a device identifier, an account number, an address, a zip code, a name, a username, a telephone number or an identity assertion. The server computer may store the received first set of user information at a storage. The server computer may receive a request for a token from a second mobile application, the request comprising at least a second set of user information. The second mobile application may be installed/provisioned on a user device. In some embodiments, the first mobile application and the second mobile application may be provisioned on the same user device. Alternatively, the first mobile application and the second mobile application may be installed/provisioned on separate user devices accessible, for example, with a same username and password. The second mobile application may be a merchant application. The second set of user information may include at least a portion of the first set of user information. The second set of user information may include one or more of a device identifier, an account number, an address, a zip code, a name, a username, a telephone number, user credentials or a user authentication verification value. 
     The server computer may compare the first set of information with the second set of information. That is, the server computer may try to correlate the second set of information with the first set of information. The server computer may determine a confidence level based on the comparison of the first set of user information to the second set of user information. The server computer may generate a token based on the comparison. A status (e.g., an assurance level) of the token may be based at least in part on the confidence level. The status of the token may be indicative of a level of restriction associated with the token. The server computer may transmit the generated token to the second mobile application. 
     In some embodiments, after receiving the token and performing one or more transactions with the token, the second mobile application may send a transaction history to the server computer. Based on the transaction history, the server computer may change the status of the token. For example, if a token with low assurance level is provided to the second mobile application, the status of the token may be increased to high assurance level based on at least the transaction history. 
     According to various embodiments, the first set of information may include an authentication indicator generated by the authorizing server, an identity assertion as part of the first set of user information or an indication of an XML-based security layer validation associated with a user of the second mobile application. The status of the token may be based at least in part in the received information. 
     In some embodiments, a method includes receiving, by a server computer, a request for a token from a mobile application. The mobile application may be a merchant mobile application installed/provisioned on a user device. The request may include identifying information associated with an account and a value assigned to a user of the account. Upon receipt of the identifying information and the value, the server computer may validate the value assigned to the user of the account. The value assigned to the user may include a cryptogram assigned to a user device associated with the account. For example, the user device may be a payment card including a near field communications (NFC) chip. The cryptogram may be unique to the payment card and the account number associated with the payment card. In some embodiments, the value assigned to the user may include a receipt code associated with a prior transaction carried out using the account. For example, the user may complete a purchase at the merchant location. The merchant may provide the user a receipt with a unique receipt code. The server computer may determine a confidence level based on validating the value assigned to the user of the account. The server computer may generate a token. A status (e.g., an assurance level) of the token may be based at least in part on the confidence level. The status of the token may be indicative of a level of restriction associated with the token. The server computer may transmit the generated token to the second mobile application. 
     Another embodiment of the invention is directed to a computer comprising a processor, and a computer readable medium coupled to the processor. The computer readable medium comprises code, executable by the processor, for implementing the above-described methods. 
     These and other embodiments of the invention are described in further detail below. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         FIG.  1    shows a diagram providing an overview of the various roles involved in a token ecosystem, in accordance with some embodiments of the invention. 
         FIG.  2    shows a block diagram for implementing an exemplary token assurance method using device fingerprinting and authentication of user data, in accordance with some embodiments of the invention. 
         FIG.  3    shows a block diagram for implementing an exemplary token assurance method using device fingerprinting and authorization platform provided information of user data, in accordance with some embodiments of the invention. 
         FIG.  4    shows a block diagram for implementing an exemplary token assurance method using an XML-based security layer to authenticate a new device, in accordance with some embodiments of the invention. 
         FIG.  5 A  shows a block diagram for implementing an exemplary token assurance method that uses authentication based on parameters configured by the authorization platform, in accordance with some embodiments of the invention. 
         FIG.  5 B  shows a block diagram for modifying an assurance level associated a token based on the transaction history, in accordance with some embodiments of the invention. 
         FIG.  6    shows a block diagram for implementing an exemplary token assurance method that uses data obtained from a near field communication (NFC) interaction at a merchant location, in accordance with some embodiments of the invention. 
         FIG.  7    shows a block diagram for implementing an exemplary token assurance method that uses a receipt code generated at a merchant location, in accordance with some embodiments of the invention. 
         FIG.  8    is a flowchart of an exemplary method for generating a token with an assurance level based on information received at least from a mobile application, in accordance with some embodiments of the invention. 
         FIG.  9    is a flowchart of another exemplary method  900  for generating a token with an assurance level based on information received at least from a mobile application, in accordance with some embodiments of the invention. 
         FIG.  10    illustrates a block diagram of a mobile device. 
         FIG.  11    illustrates a block diagram of a portable consumer device. 
         FIG.  12    illustrates a block diagram of a computer apparatus. 
     
    
    
     DETAILED DESCRIPTION 
     Embodiments of the invention provide a platform (e.g., a token ecosystem) that can be leveraged by various entities such as third party wallet providers, merchants, acquirers, payment processors and the like that use tokens to facilitate payment transactions. In the token ecosystem, a token provider, such as a cloud based payment service, may issue tokens based on requests from a token requestor. The token requestor may be a mobile application, such as a merchant mobile application provisioned on a user device. The merchant mobile application may be a mobile application (or a mobile wallet application) developed by a merchant for a user mobile device (e.g., mobile phone) to be used during transactions at merchant locations (e.g., point-of-sale (POS) devices of the merchant). 
     In response to a token request from the merchant, the token provider issues tokens with varying status based on a confidence level determined in light of the data received from the token requestor. For example, the status of the token may indicate that the token is a trusted token associated with a high assurance level. Such token may be used without restrictions by the merchant mobile application. Alternatively, the status of the token may indicate that the token is an untrusted token associated with a low assurance level. Such token may have restrictions imposed thereupon. For example, a token with a low assurance level may be used for transactions below a pre-determined value (e.g., money amount) or may be used only with proper user identifying information (e.g., showing user ID card, providing a PIN and/or a card verification value (e.g., CVV), user biometrics and the like). 
     Accordingly, embodiments of the invention relate to the generation of a token, wherein the token can be associated with a status. The status of the token may affect how the token is treated and the types of restrictions placed on the token. For example, the status of the token may indicate that the token is generated based on verification of secure user data. In some embodiments, the status of the token may indicate that the token is generated based on insufficient user data and, as such, restrictions may be imposed on the token. 
     Prior to discussing embodiments of the invention, description of some terms may be helpful in understanding embodiments of the invention. 
     A “user device” is an electronic device that may be transported and/or operated by a user. A user device may provide remote communication capabilities to a network. The user device may be configured to transmit and receive data or communications to and from other devices. In some embodiments, the user device may be portable. Examples of user devices may include mobile phones (e.g., smart phones, cellular phones, etc.), PDAs, portable media players, wearable electronic devices (e.g., smart watches, fitness bands, ankle bracelets, rings, earrings, etc.), electronic reader devices, and portable computing devices (e.g., laptops, netbooks, ultrabooks, etc.). Examples of user devices may also include automobiles with remote communication capabilities. 
     An “application” may include any software module configured to perform a specific function or functions when executed by a processor of a computer. For example, a “mobile application” may include a software module that is configured to be operated by a mobile device. Applications may be configured to perform many different functions. For instance, a “payment application” may include a software module that is configured to store and provide account credentials for a transaction. A “wallet application” may include a software module with similar functionality to a payment application that has multiple accounts provisioned or enrolled such that they are usable through the wallet application. 
     A “payment application” or “wallet application” may store credentials (e.g., account identifier, expiration date, card verification value (CVV), etc.) for accounts provisioned onto the user device. The account credentials may be stored in general memory on the mobile device or on a secure trusted execution environment (e.g., a secure element) of the user device. Further, in some embodiments, the account credentials may be stored by a remote computer and the payment/wallet application may retrieve the credentials (or a portion thereof) from the remote computer before/during a transaction. Any number of different commands or communication protocols may be used to interface with the payment application and/or wallet application in order to obtain and use stored credentials associated with each application. 
     The payment application or wallet application may be configured to provide credentials to an authorized software application or module on a user device. For example, a payment application may be configured to interface with a master applet in order to provide credentials to a mobile application for a transaction. For instance, the payment application may provide a software development kit (SDK) or application programming interface (API) that the master wallet applet may use to interface with the payment application and/or wallet application. The payment application and/or wallet application may be configured to provide the sensitive information in encrypted form using stored encryption keys. Thus, each payment application and/or wallet application may have different commands and/or instructions for accessing the associated credentials stored by the payment/wallet application. For instance, each payment application and/or wallet application may have a different application program interface (API) with different commands, data requirements, authentication processes, etc., for interacting with other applications operating on the user device. Accordingly, a master wallet applet may include a number of different APIs, one for each of the different payment applications and/or wallet applications that the master wallet applet is configured to interface with. 
     “User information” may include any information that is associated with a user. For example, the user information may include a device identifier of a device that the user owns or operates and/or account credentials of an account that the user holds. A device identifier may include a unique identifier assigned to a user device that can later be used to verify the user device. In some embodiments, the device identifier may include a device fingerprint. The device fingerprint may an aggregation of device attributes. The device fingerprint may be generated by a software development kit (SDK) provided on the user device using, for example, a unique identifier assigned by the operating system, an International Mobile Station Equipment Identity (IMEI) number, operating system (OS) version, plug-in version, and the like. 
     “Account credentials” may include any information that identifies an account and allows a payment processor to verify that a device, person, or entity has permission to access the account. For example, account credentials may include an account identifier (e.g., a PAN), a token (e.g., account identifier substitute), an expiration date, a cryptogram, a verification value (e.g., card verification value (CVV)), personal information associated with an account (e.g., address, etc.), an account alias, or any combination thereof. Account credentials may be static or dynamic such that they change over time. Further, in some embodiments, the account credentials may include information that is both static and dynamic. For example, an account identifier and expiration date may be static but a cryptogram may be dynamic and change for each transaction. Further, in some embodiments, some or all of the account credentials may be stored in a secure memory of a user device. The secure memory of the user device may be configured such that the data stored in the secure memory may not be directly accessible by outside applications and a payment application associated with the secure memory may be accessed to obtain the credentials stored on the secure memory. Accordingly, a mobile application may interface with a payment application in order to gain access to payment credentials stored on the secure memory. 
     A “merchant application” may include any application associated with a relying party to a transaction. For example, a merchant mobile application may be associated with a particular merchant or may be associated with a number of different merchants. In some embodiments, the merchant mobile application may store information identifying a particular merchant server computer that is configured to provide a sales environment in which the merchant server computer is capable of processing remote transactions initiated by the merchant application. Further, the merchant mobile application may also include a general purpose browser or other software designed to interact with one or more merchant server computers. In some cases, the merchant mobile application may be installed in the general purpose memory of a user device and thus, may be susceptible to malicious attacks. 
     A “token” may include any identifier for a payment account that is a substitute for an account identifier. For example, a token may include a series of alphanumeric characters that may be used as a substitute for an original account identifier. For example, a token “4900 0000 0000 0001” may be used in place of a primary account identifier or primary account number (PAN) “4147 0900 0000 1234.” In some embodiments, a token may be “format preserving” and may have a numeric format that conforms to the account identifiers used in existing payment processing networks (e.g., ISO 8583 financial transaction message format). In some embodiments, a token may be used in place of a PAN to initiate, authorize, settle or resolve a payment transaction or represent the original credential in other systems where the original credential would typically be provided. In some embodiments, a token value may be generated such that the recovery of the original PAN or other account identifier from the token value may not be computationally derived. Further, in some embodiments, the token format may be configured to allow the entity receiving the token to identify it as a token and recognize the entity that issued the token. According to various embodiments, a token may be associated with a token status. The token status may indicate, for example, that the token is a high quality token or a low quality token. The status of the token may be indicative of a level of restriction associated with the token. For example, no restrictions may be imposed on a high quality token whereas restrictions such as further identification requirements may be imposed on a low quality token. The status of the token may be based at least in part on the confidence level with which the token is generated. 
     “Provisioning” may include a process of providing data for use. For example, provisioning may include providing, delivering, or enabling a token or a mobile application on a device. 
     “Tokenization” is a process by which data is replaced with substitute data. For example, a payment account identifier (e.g., a primary account number (PAN)) may be tokenized by replacing the primary account identifier with a substitute number that may be associated with the payment account identifier. Further, tokenization may be applied to any other information which may be replaced with a substitute value (i.e., a card verification value (CVV)). 
     “Token exchange” or “de-tokenization” is a process of restoring the data that was substituted during tokenization. For example, a token exchange may include replacing a payment token with an associated primary account number (PAN) that was associated with the payment token during tokenization of the PAN. Further, de-tokenization or token exchange may be applied to any other information. In some embodiments, token exchange may be achieved via a transactional message, such as an ISO message, an application programming interface (API), or another type of web interface (e.g., web request). 
     “Authentication” is a process by which the credential of an endpoint can be verified to ensure that the endpoint is who they are declared to be. 
     A “requestor” may be an entity that can request an item or action. For example, a requestor can request registration with a network token system, request token generation, token activation. token de-activation, token exchange, other token life-cycle management related processes, and/or any other token related processes. A requestor may interface with a network token system through any suitable communication networks and/or protocols (e.g., using HTTPS, SOAP and/or an XML interface). Some non-limiting examples of a requestor may include third party wallet providers, issuers, acquirers, merchants, and/or payment processing networks. A requestor may be referred to as a token requestor when requesting generation of a new token or requesting a new use of an existing token from a network token system. In some embodiments, a token requestor can request tokens for multiple domains and/or channels. Token requestors may include, for example, card-on-file merchants, acquirers, acquirer processors, and payment gateways acting on behalf of merchants, payment enables (e.g., original equipment manufacturers, mobile network operators, etc.), digital wallet providers, and/or card issuers. 
     The term “server computer” may include a powerful computer or cluster of computers. For example, the server computer can be a large mainframe, a minicomputer cluster, or a group of servers functioning as a unit. In one example, the server computer may be a database server coupled to a Web server. The server computer may be coupled to a database and may include any hardware, software, other logic, or combination of the preceding for servicing the requests from one or more client computers. The server computer may comprise one or more computational apparatuses and may use any of a variety of computing structures, arrangements, and compilations for servicing the requests from one or more client computers. In some embodiments, the server computer may provide and/or support payment network cloud service. 
     An “authorization platform” (i.e., an “issuer”) may be a system that can authorize a transaction. 
     A “merchant” is typically an entity that engages in transactions and can sell goods or services, or provide access to goods or services. 
       FIG.  1    shows a diagram providing an overview of the various roles involved in a token ecosystem, in accordance with some embodiments of the invention. The token ecosystem  100  comprises a token vault  110  which may be in communication with one or more of a token requestor  115 , a merchant  130 , an acquirer  135 , a payment processing network  140 , and an authorization platform  150  (i.e., issuer). The consumer  120  (i.e. user) may be in communication with the token requestor  115 , the authorization platform  150 , and the merchant  130 . Any one of the consumer  120 , the authorization platform  150 , the merchant  130 , the acquirer  135  or the payment network  140  may be the token requestor. Furthermore, the merchant  120 , the acquirer  130 , the payment processing network  140 , the authorization platform  150 , and a token network  145  may all be in operative communication with each other (i.e., one or more communication channels may exist between each of the entities, whether or not these channels are used in conducting a financial transaction). In some embodiments, one or more of the entities or functionalities may be implemented via a cloud based payment (CBP) service. For example, a CBP service may provide token vault  110  functionality and/or token network  145  functionality. In addition, the payment network  140  may be implemented via a server computer providing a cloud based payment service. 
     The token vault  110  may be associated with the payment processing network  140 , the authorization platform  150 , the acquirer  135 , or the merchant  130 . For example, in some embodiments, a token service provider may comprise an associated token vault  110  and payment processing network  140 . The token vault  110  may be able to receive a token request from the token requestor  115 . The token vault  110  may be able to issue a token that can be used as surrogate payment account information, and a status of the token may depend on information provided in the token request. For example, in some embodiments, the token may be valid for a certain token domain and may have a certain token assurance level. The token vault  110  may store a record of the token, a token assurance level, a token status, a token expiration date, associated payment account information, token domain information, or any other suitable information. 
     The token vault  110  may also allow the token requestor  115  to register at the token vault  110 . The token vault  110  may receive a request to register from the token requestor  115 . The request may include information about the token requestor  115 , information about how tokens will be used, a desired token assurance level, or any other suitable information. The token vault  110  may approve or reject the registration request. 
     The token vault  110  may also be capable of de-tokenizing and providing payment account information in response to receiving a token. For example, the token vault  110  may receive a request for payment account information from the payment processing network  140 , authorization platform  150 , acquirer  135 , and/or merchant  130 . The request may include a token. The token vault  110  may locate a token record and identify the payment account information that is associated with the token. The token vault  110  may provide the payment account information to the de-tokenization requestor. 
     In some embodiments, the de-tokenization requestor may be the payment processing network  140 , which may request the payment account information for authorization purposes. In some embodiments, the de-tokenization requestor may be the merchant  130  which may wish to have the payment account information for consumer identification purposes. 
     The token requestor  115  may request a token on behalf of the consumer  120 . The token requestor  115  may be a digital wallet provider, a merchant  130 , a payment processing network  140 , a token aggregator, or any other suitable entity. A token requestor  115  may have a business relationship with a merchant  130  and/or acquirer  135 . The consumer  120  may wish to purchase a good and/or service from the merchant  130 , and the token requestor  115  may retrieve a token from the token vault  110  for the consumer  120  to use for the purchase. 
     In some embodiments, the token requestor  115  may be a token aggregator. For example, the token aggregator may request tokens on behalf of one or more digital wallet providers. A digital wallet provider may prefer not to register with a token vault  110  and instead receive tokens from the token aggregator. Digital wallet providers may receive tokens from a token aggregator and then provide the tokens to consumers  110  that use a digital wallet. In some embodiments, a token requestor  115  may be able to request and collect tokens from multiple token vaults  110  or token service providers, and may request tokens that are valid for multiple payment processing networks  140 . The token requestor  115  may register with each token vault  110  separately. 
     The merchant  130  may be capable to sell goods and/or services to the consumer  120 . The merchant  130  may receive payment information comprising a token from the consumer  120 . The merchant  130  may send the token to the acquirer  135  for payment authorization. 
     The acquirer  135  may be associated with the merchant  130 , and may manage authorization requests on behalf of the merchant  120 . The acquirer  130  may receive an authorization request message from the merchant  130  and send the authorization request message to a payment processing network  140 . The payment processing network  140  may be associated with the token and may be identified by one or more fields within the token 
     The payment processing network  140  may be disposed between the acquirer  130  and the authorization platform  150 . The payment processing network  140  may include data processing subsystems, networks, and operations used to support and deliver authorization services, exception file services, and clearing and settlement services. For example, the payment processing network  140  may comprise a server computer, coupled to a network interface (e.g., by an external communication interface), and a database(s) of information. The server computer may provide cloud based payment services for the payment processing network  140 . An exemplary payment processing network may include VisaNet™. Payment processing networks such as VisaNet™ are able to process credit card transactions, debit card transactions, and other types of commercial transactions. VisaNet™, in particular, includes a VIP (Visa Integrated Payments) system which processes authorization requests and a Base II system which performs clearing and settlement services. The payment processing network  140  may use any suitable wired or wireless network, including the Internet. 
     The payment processing network  140  may be capable to de-tokenize an authorization request message. For example, the payment processing network  140  may receive an authorization request message including a token, send the token to the token vault  110 , receive associated payment account information from the token vault  110 , and forward the authorization request message to the authorization platform  150  with the payment account information. 
     The authorization platform  150  may manage a payment account of the consumer  120 . The authorization platform  150  may be able authorize transactions that involve the payment account. 
     A typical token transaction flow is described next. The consumer  120  may provide a PAN to the token requestor  115  to request a token for a transaction. For example, the consumer  120  can access an application, a mobile application or a website on the consumer device to interact with the token requestor  115 . In some embodiments, the consumer  120  participates in a cardholder verification and authentication (ID&amp;V) process using one or more authentication schemes to utilize the network token services. The token requestor  115  may communicate with the token vault  110  to request an exchange of the PAN with a token. The token vault  110  may provide a token as a substitute for the PAN. The token requestor  115  may provide the token to the consumer  120  for the transaction. In one embodiment, if the token is a static token, the token may be stored in a secure location on the consumer device, e.g., a secure element of the mobile device. 
     For conducting a transaction using the token, the consumer  120  may provide the token to the merchant computer  130 . In one embodiment, the token may be presented as part of the transaction using any suitable token presentment mode such as contactless, ecommerce, stream/proximity (e.g., optical, sound, etc.), etc. For example, the token requestor  115  may provide the token in the form of a QR code that may be displayed on the consumer device  120 . A merchant can scan the QR code including the payment token into the merchant computer  130 . Alternatively, the consumer  120  can wave the consumer device in the vicinity of a contactless reader coupled to the merchant computer  130  to transfer the payment token in the contactless mode. In some embodiments, if the token requestor  115  is a payment enabler (e.g., a digital wallet provider), the token requestor  115  can orchestrate the population of the token requestor identifier into a transaction message before passing it to the merchant computer  130 . 
     The merchant computer  130  may provide an authorization request message including the token to the acquirer computer  135  for the transaction initiated by the consumer  120 . For example, in some embodiments, the authorization request message may include some token based values such as a token value, a token requestor identifier, an assurance level code in addition to some PAN based values. The acquirer computer  135  may forward the authorization request message including the token to the payment processing network computer  140 . The payment processing network computer  140  may provide the token to the token network system  145  to receive a PAN in exchange. 
     The token network system  145  may provide the PAN to the payment processing network computer  140 . The payment processing network computer  140  may modify the authorization request message to include the PAN in place of the token and provide the modified authorization request message to the authorization platform  150 . The authorization platform  150  may provide an authorization response message to the payment processing network computer  140 . For example, the authorization platform  150  may determine if the transaction can be authorized based on the consumer account information (e.g., available balance, transaction history, etc.). 
     The payment processing network computer  140  may modify the authorization response message received from the authorization platform  150  to replace the PAN information with the token information. For example, in one embodiment, the payment processing network computer  140  may interact with the token network system  145  to perform the PAN/token mapping. The payment processing network computer  140  may send the modified authorization response message including the token to the acquirer computer  135 . The acquirer computer  135  may forward the modified authorization response message to the merchant computer  130 . The merchant computer  135  may indicate the authorization response to the consumer  120 . For example, the merchant computer  135  may send a message to the consumer device indicating if the transaction is approved or declined. 
     Upon understanding the typical transaction flow involving a token, as described above with respect to  FIG.  1   , one may appreciate the improvements in token handling described throughout this specification, below. 
     As provided above in connection with  FIG.  1   , based on a request from the token requestor  115 , the token provider issues a token. According to various embodiments, the token may be assigned a status. For example, the token status may identify the token having a high assurance level indicating that the token is generated based on verified, authenticated user information. In some embodiments, the token status may identify the token having a low assurance level indicating that the token is generated based on insufficient or unreliable user information. A low assurance level token status may have restrictions imposed thereon. For example, the token associated with the low assurance level may be used for transactions up to a pre-determined amount (e.g. for transactions worth less than $50) or may only be used when accompanied by a user identification (e.g. presentment of the payment device, user ID, a PIN code and the like). Embodiments discussed below provide various techniques for determining the status of the token based on provided information. The status of the token determines how the token will be treated when presented for transactions. 
       FIG.  2    shows a block diagram  200  for implementing an exemplary token assurance method using device fingerprinting and authentication of user data, in accordance with some embodiments of the invention. As illustrated in  FIG.  2   , a first mobile application (e.g., an issuer application)  202  and a second mobile application (e.g. a merchant application)  204  may be provisioned on a user device such that each mobile application may be used to conduct payment transactions using the user device. In some embodiments, both the first mobile application  202  and the second mobile application  204  may be executed by an operating system of the user device. For simplicity of illustration, the first mobile application and/or the second mobile application are illustrated in  FIGS.  2 - 7   . The mobile applications are provided on a mobile device, such as the applications  1012  provided on the mobile device  1002 , illustrated in  FIG.  10   . 
     Additionally, the first mobile application  202  and the second mobile application  204  may be in communication via a payment processing server  206 . The payment processing server  206  may support and/or provide cloud based payment (CBP) service capabilities. In some embodiments, the first mobile application  202  and the second mobile application  204  may be provisioned on the same user device. Alternatively, the first mobile application  202  may be provisioned on a first user device (e.g. a mobile phone) and the second mobile application  204  may be provisioned on a second user device (e.g. a tablet computer) such that the first user device and the second user device may be accessible via a common username and password. 
     The first mobile application  202  may be associated with an authorization entity (e.g., an issuer) and the second mobile application  204  may be associated with a merchant. That is, the first mobile application  202  may be a trusted application and the second mobile application  204  may be an untrusted application. The second mobile application  204  may allow users to enroll account information (e.g., payment card information) on their user devices through the second mobile application  204  that can be used to pay for purchases made at the merchant. The merchant may not validate the account of the user with an issuer before adding the payment account to the second mobile application  204 . As such, the second mobile application  204  is “untrusted” because the account credentials associated with the second mobile application  204  has not been validated by the authorizing entity. These account credentials may be categorized as “untrusted accounts” when added through the second mobile application  204  and may have additional access restrictions than trusted accounts (i.e., issuer validated accounts). 
     Further, the authorization entity may incorporate a software development kit (SDK)  208  associated with the payment processing server  206  in the first mobile application  202 . Similarly, the merchant may incorporate a second SDK  210  associated with the payment processing server  206  in the second mobile application  204 . The SDKs  208  and  210  may enable the first mobile application  202  and the second mobile application  204 , respectively, to properly communicate with the payment processing server  206 . 
     The user may log into the first mobile application  202  using his/her user credentials associated with the authorization entity. Upon successful login to the first mobile application  202 , the first SDK  208  may use a device identifier associated with the user device or generate a device fingerprint unique to the user device that can later be used to verify the user device. Data used to generate the device fingerprint may include, but is not limited to, a unique identifier assigned by the operating system, an International Mobile Station Equipment Identity (IMEI) number, OS version, plug-in version, etc. It can be appreciated that the data used to generate the device fingerprint may not require any active participation from the user, aside from successfully logging into the first mobile application  202 . The first mobile application  202  may send, via the first SDK  208 , a first set of user information to the payment processing server  206  (step 1). For example, the first set of user information may include the generated device fingerprint and data associated with a user account including, for example, a primary account number (PAN), zip code, a cardholder verification value (CVV2), and the like. In some embodiments, the payment processing server  206  may access a database to make sure that the received device fingerprint is not among blacklisted device fingerprints associated with devices known to have been used for fraudulent transactions. 
     Upon receiving the first set of user information and confirming that the user device has not been used for fraudulent transactions, the payment processing server  206  may register the user device and the first mobile application  202 . The payment processing server  206  may generate a token and send it to the first mobile application  202 . The token may have a status of a high quality token (i.e. the token may be associated with a high assurance level) indicating that the token is generated with a high level of trust due to the first mobile application  202  being associated with an authorizing entity. 
     After successful login with the first mobile application  202  and optional registration with the payment processing server  206 , the user may download and open the second mobile application  204  on his/her user device. The second mobile application  204  may prompt the user to load his/her payment card information into the second mobile application  204 . The user may proceed to enter account identifying information such as the account number, CVV2, zip code and/or any other identifying information into the second mobile application  204 . The second mobile application  204  may then, via the second SDK  210 , transmit a second set of user information to the payment processing server  206  (step 2). The second set of user information may include the user entered account identifying information and a device identifier or a device fingerprint generated by the second SDK  210 . Data used to generate the device fingerprint may include, but is not limited to, a unique identifier assigned by the operating system, an International Mobile Station Equipment Identity (IMEI) number, OS version, plug-in version, etc. It can be appreciated that the data used to generate the device fingerprint may not require any active participation from the user, aside from providing the account identifying information to the second mobile application  204 . 
     The payment processing server  206  may verify whether the account information provided by the user through the second mobile application  204  has previously been provisioned to the payment processing server  206  by the authorization entity. Additionally, the payment processing server  206  may determine whether the device fingerprint provided by the first mobile application  202  matches the device fingerprint provided by the second mobile application  204 . A token with an assurance level may be generated based upon how well the first set of user information and the second set of user information correlate. The assurance level may be indicative of an amount of confidence that the user attempting to load the payment card is the genuine user and that the user device where the payment card is being loaded onto is the genuine user device used by the user. 
     A token associated with the account number may then be provisioned for the second mobile application  206  (step 3). The token may have a status based on the confidence level (or level of trust). For example, a token with a high assurance level may be provisioned if a high confidence level exists (e.g., all or most of the user information provided by the second mobile application  204  matches the user information provided by the first mobile application  202 ). Conversely, a token with a low assurance level may be provisioned if a low confidence level exists (e.g., some of the user information provided by the second mobile application  204  matches the user information provided by the first mobile application  202 ). The status of the token (i.e., assurance level associated with the token) may determine the amount of restrictions imposed on the token and treatment of the token. For example, a token with a low assurance level may have more restrictions than a token with a high assurance level. When using the token with the low assurance level, the user (via a mobile application) may be asked for additional identification (e.g., provide identifying information and/or PIN, CVV2, user biometrics) or may only be allowed a predetermined transaction amount (e.g. token with the low assurance level may be used for transactions worth less than $50). In some embodiments, if none or only a small portion of the user information provided by the second mobile application  204  matches the user information provided by the first mobile application  202 , no token may be provided to the second mobile application  204 . 
     In some embodiments, the token sent to (i.e., provisioned on) the first mobile application  202  may be the same as the token sent to the second mobile application  204 . Alternatively, a first token may be sent to (i.e., provisioned on) the first mobile application  202  and a second, different, token may be sent to the second mobile application  204 . The first token and the second token may have different status associated with each of them. 
     The token assurance flow described above may be further explained via an illustrative example. A husband and a wife may share a payment account while they both own their own individual mobile devices. The husband may have completed registration as described above and the merchant mobile application running on his mobile device may have been provisioned with a high assurance level token (e.g. the status of the token indicates that the token is a trusted token). The wife may download a mobile application to her mobile device and attempt to enroll the same PAN on her mobile device. However, the device fingerprint obtained from her mobile device may not match the device fingerprint originally obtained from the husband&#39;s device at the time of registration because the wife is using a different mobile device. However, the PAN and other card data (e.g., CVV2, zip code, etc.) may match. As a result, a token may still be provisioned for the wife&#39;s device but the token may be a low assurance level token (e.g. the status of the token indicates that the token is an untrusted token). 
     It can be appreciated that the provisioned token may be a static token or may be a dynamic token that may only be used a predetermined number of times before provisioning of a new token is required. If a new token needs to be provisioned, the registration process may need to be completed again and an updated device fingerprint may be provided to the payment processing server  206 . In some embodiments, the device fingerprint may also change due to changes on the mobile device (e.g., OS upgrade, etc.). In such instances, the registration process may need to be completed again. In some embodiments, the provisioned token may be used for use with NFC payments or other contactless payments (e.g., QR code payments). 
     In some embodiments, the authorization platform may be in direct communication with the payment service provider server.  FIG.  3    illustrates such an embodiment. 
       FIG.  3    is a block diagram  300  for implementing an exemplary token assurance method using device fingerprinting and authorization platform provided information of user data, in accordance with some embodiments of the invention. In the embodiment illustrated in  FIG.  3   , the authorization platform  312  may actively provision user data into the payment processing server  306 , for example, when the user enrolls for online banking service with the authorization platform  312 . This provisioning may occur for a number of user devices. In some embodiments, the authorization platform  312  may provision the user information (e.g., PAN, zip code, address, etc.) into a digital payment service account from within their online banking service. The user may then establish a user name and password to subsequently conduct online transactions. During this process, the authorization platform  312  may also provide an identity assertion in the form of a Security Assertion Markup Language (SAML) assertion to the payment processing server  306  (step 1). The identity assertion may indicate that the user&#39;s identity has been verified and authenticated by the authorization platform  312 . 
     The user may then log into the first mobile application  302 , as described above with respect to  FIG.  2   . In some embodiments, the first mobile application  302  (e.g. issuer application) may generate an identity assertion upon the user identifying themselves to the first mobile application  302 . The first SDK  308  may also generate a device fingerprint. The first mobile application  302  may send the first set of user information including at least the device fingerprint and, if generated, the identity assertion (e.g. SAML assertion), via the first SDK  308 , to the payment processing server  306  (step 2). In some embodiments, the user data may have already been provided to the payment processing server  306  through the provisioning service. 
     When the user activates the second mobile application  304 , he/she may be prompted to load a new payment card into the second mobile application  304 . However, instead of typing the payment card number, the user may choose to load a payment card via the digital payment service associated with the payment processing server  306 . Accordingly, the user may enter his/her username and password into the digital payment service portal. The second SDK  310  within the second mobile application  304  may send the login credentials along with a device fingerprint (generated by the second SDK  310 ) to the payment processing server  306  (step 3). Based upon a successful match of the account login and strong correlation of the user information (including the device fingerprints, user data, identity assertion) received from the first mobile application  302 , the second mobile application  304  and the authorization platform  312 , the payment processing server  306  may provision a token to the second mobile application  304  (step 4). 
     In other words, the embodiment shown in  FIG.  3    illustrates the authorization platform  312  providing an identity assertion (i.e., SAML assertion) for the user to the payment processing server  306 . The payment processing server  306  may then issue a token with a high assurance level based on the identity assertion because the authorization platform  312  is a trusted entity. The identity assertion may be based on the user&#39;s successful login to the first mobile application  302  using the same credentials that he/she uses for online banking. The provisioning of the token may be based on a correlation between the data received from the second mobile application  304  with data received from the first mobile application  302  and information previously received from the authorization platform  312 . 
     In some embodiments, the token assurance method may not include a first mobile application provisioned by the authorization platform. That is, the user device may not have the issuer mobile application.  FIG.  4    illustrates such an embodiment. 
       FIG.  4    a block diagram  400  for implementing an exemplary token assurance method using an XML-based security layer to authenticate a new user device, in accordance with some embodiments of the invention. When the user downloads and activates the mobile application  404  (e.g. merchant mobile application), the user may be prompted to load new payment account information to the mobile application  404 . As described above, the mobile application  404  may have an SDK  408 . The SDK  408  may send a first set of user information including the payment account number, user identifying information and a device fingerprint (generated by the SDK  408 ) to the payment processing server  406  for requesting a token corresponding to the payment account number (step 1). The payment processing server  406  may detect a new user who has not previously registered with the payment processing server  406 . Given the lack of any prior device information, the payment processing server  406  may not automatically validate the information provided by the merchant application  404  in order to provision a token. The payment processing server  406  may try to locate other supporting authentication mechanisms. 
     For example, the payment processing server  406  may detect that the authorization platform  402  supports an XML-based security layer authentication (e.g., 3-D Secure) and may send a prompt to the mobile application  404  requesting the mobile application  404  to perform the XML-based security layer authentication process with the authorization platform  402  (step 2). The SDK  408  of the mobile application  404  may include an embedded merchant plug-in that triggers the XML-based security layer authentication process (step 3). Upon successful authentication with the XML-based security layer of the authorization platform  402 , the authorization platform  402  may provide an authentication indicator (e.g., cardholder authentication verification value (CAVV)) to the SDK  408  inside the mobile application  404  (step 4). The SDK  408  may then pass the authentication indicator to the payment processing server  406  (step 5). The payment processing server  406  may validate the authentication indicator. For example, the payment processing server  406  may pass the authentication indicator to an interoperability domain supporting the XML-based security layer authentication for validation. Upon validation of the authentication indicator, the payment processing server  406  may provision a token with a high assurance level to the mobile application  404  (step 6). The payment processing server  406  may store the device fingerprint for future authentication/verification processes. In some embodiments, the payment processing server  406  may use the device fingerprint to ensure that the token and/or the payment account is not affiliated with too many user devices. For example, using the fingerprints of user devices, the payment processing server  406  may determine that a given token and/or payment account is affiliated with a couple of user devices (e.g. user mobile phone, user tablet computer, user laptop), which may be acceptable. However, if the same token and/or payment account are affiliated with too many devices (e.g. 10 devices) or the same device (i.e. same fingerprint) is affiliated with too many payment accounts, the payment processing server  406  may start an inquiry regarding whether fraudulent activity is taking place. If there is suspected fraud, the payment processing server  406  may decrease the status of the token (i.e., drop the assurance level associated with the token) or destroy (e.g., cancel, terminate, deactivate) the token. 
     It can be appreciated that while the XML-based security layer authentication (e.g., 3-D secure authentication) is typically used for e-commerce transactions and is performed each time a transaction is conducted, the use of the XML-based security layer authentication to authenticate a user prior to provisioning a token can provide certain benefits over existing solutions. Such benefits include using the same device and the high assurance level token in future transactions without having to perform validation and/or authentication processes for each transaction. 
     In some embodiments, the token assurance method may not include a first mobile application provisioned by the authorization platform. That is, the user device may not have the issuer mobile application. In addition, the payment processing server may not have access to any of the authorization processes discussed above. Instead, the payment processing server may rely upon authentication based on parameters configured by the authorization platform.  FIG.  5 A  illustrates such an embodiment. 
       FIG.  5 A  shows a block diagram  500  for implementing an exemplary token assurance method that uses authentication based on parameters configured by the authorization platform, in accordance with some embodiments of the invention. In the exemplary embodiment illustrated in  FIG.  5 A , the authorization platform  506  may have previously set parameters within their own systems or within the payment processing server  504  to determine when to issue a token and/or what kind (i.e. status) of token to issue. Exemplary parameters may include, but are not limited to, the age of payment account on user device, the transaction count without chargebacks or lost/stolen status performed using the payment account on the user device, the transaction volume without chargebacks or lost/stolen status performed using the payment account on the user device, a risk score, the number of devices the payment account is associated with and the like). When the user downloads and executes the mobile application  502  (e.g., a merchant mobile application), the user may be prompted to load payment account information to the mobile application  502 . Upon receiving the user information (e.g., account number, expiration date, address, zip code, and the like), the SDK  508  embedded in the mobile application  502  may transmit this information to the payment processing server  504 , along with additional credentials (e.g., account age, assurance levels from wallet provider, etc.) and a device fingerprint (generated by the SDK  508 ) (step 1). The payment processing server  504  may correlate this data along with other risk information, such as the number of devices the payment account has been loaded on, the number of transactions without a chargeback, and the like. 
     Based on this information, the authorization platform  506 , or the payment processing server  504  on behalf of the authorization platform  506 , may decide what type of token to return to the mobile application  502  (steps 2 and 3). Without sufficient authentication as configured by the authorization platform  506 , a token with a low assurance level may be returned to the mobile application  502  (step 4). For example, the low assurance level token can be used for contactless transactions but may not provide the associated card present treatment. In subsequent transactions, the SDK  508  may continue to check with the payment processing server  504  to determine whether parameters are met in order to upgrade the token to a high assurance level token to receive the associated economic benefits and liability protection associated with such tokens. 
     The status of the token provided to the mobile application  502  may be upgraded from a low assurance level to a high assurance level once a predetermined criteria is met. For example, the status may be upgraded when a number of successful transactions are completed with the user device within a predetermined period of time. In some embodiments, the authorization platform  506  may determine these transaction history parameters. The payment processing server  504  may enforce the parameters on behalf of the authorization platform  506 . The transaction history parameters may include, but is not limited to, account age on device, transaction count, transaction volume, risk score, maximum number of devices, a certain amount of total purchase value, and the like. 
       FIG.  5 B  shows a block diagram  520  for modifying an assurance level associated a token based on the transaction history, in accordance with some embodiments of the invention. In  FIG.  5 B , the mobile application  502  is provisioned with a token having a low assurance level, as described above in connection with  FIG.  5 A . After being provisioned with the low assurance level token, the mobile application  502  provides transaction history updates  510  to the payment processing server  504  (step 4). In some embodiments, the mobile application  502  may send periodical updates (e.g., transaction history update messages) to the processing server  504  as transactions are completed. In other embodiments, the mobile application  502  may send transaction updates to the payment processing server  504  when the predetermined criteria (i.e., criteria determined by the authorization platform  506 ) is met. Upon satisfying the predetermined criteria, the payment processing server  504  may upgrade the status of the token previously sent to the mobile application  502  (step 5). 
     Accordingly, in the exemplary embodiment illustrated in  FIGS.  5 A- 5 B , the payment processing server  504  may monitor the paring between the user device and a PAN over time. Based on the transaction history received from the mobile application  502 , the payment processing server  504  may determine that the same PAN is being used by the same mobile application  502  on a same user device. Specifically, the payment processing server  504  may determine that the same user device is being used based on the device fingerprint provided in the transaction history matching the device fingerprint initially provided by the mobile application  502 , as discussed above in connection with  FIG.  5 A . Thus, the payment processing server  504  may determine that the PAN is being used legitimately and upgrade the status of the token provided to the mobile application  502 . In some embodiments, the payment processing server  504  may also consider history of transactions conducted using other mobile applications on the same user device. 
     According to various embodiments, the token assurance method may not include a first mobile application provisioned by the authorization platform. That is, the user device may not have the issuer mobile application. In addition, the payment processing server may not interact with the authorization platform, as described above. Instead, the payment processing server may rely upon authentication based on reliable data obtained by the mobile application, for example at a merchant location. In some embodiments, the reliable data may include a cryptogram (illustrated in  FIG.  6   ) associated with a payment card received from a mobile application or a unique code (illustrated in  FIG.  7   ) provided to the user at the merchant location and received from the mobile application. 
       FIG.  6    shows a block diagram  600  for implementing an exemplary token assurance method that uses data obtained from a near field communication (NFC) interaction at a merchant location, in accordance with some embodiments of the invention. An NFC chip in a mobile device may include both read and broadcast capabilities. Accordingly, the user may tap their payment card against their mobile device to transfer basic information such as the card number along with a unique cryptographic value that is unique to the payment card. The payment card information and the unique cryptographic value can be sent to the payment processing server  604  from the mobile application  602  (e.g. merchant mobile application), via the SDK  606  (step 1). The payment processing server  604  may verify the unique cryptographic value and authenticate the user (i.e., verify that the user has possession of the payment card and is the owner of the account because only the holder of the payment card may have access to the unique cryptographic value). Based on this verification, a token with a high assurance level can be provisioned for the mobile application  602  (step 2). In some cases, if the mobile device is the fifth or sixth mobile device for which the token associated with the account number is being requested, a token with a low assurance level may be provisioned for the mobile application  602 . 
       FIG.  7    shows a block diagram  700  for implementing an exemplary token assurance method that uses a receipt code generated at a merchant location, in accordance with some embodiments of the invention. A user may carry out a traditional transaction at a merchant location using his/her payment card. Upon completion of the transaction, the user may be notified by the merchant to install the mobile application  702  (e.g., merchant mobile application) and register their payment card with the mobile application  702 . For subsequent transactions with the merchant, the user may use their mobile device to pay at the merchant location. The mobile application  702  may request the payment card information from the user along with a unique receipt code. The unique receipt code may be printed on the receipt of the original traditional transaction carried out at the merchant location. The payment card information and the unique receipt code may then be passed on to payment processing server  704 , via the SDK  706  embedded in the mobile application  702  (step 1). The receipt code may indicate that the user successfully completed a transaction at the merchant location, which implies that the user is in possession of the payment device and the merchant checked the user identification prior to approving the transaction. Thus, the receipt code is treated as a trusted piece of information. The payment processing server  704  may verify that the unique receipt code correlates with the payment card information, and may provision a high assurance level token to the mobile application  702  (step 2). 
       FIG.  8    is a flowchart of an exemplary method  800  for generating a token with an assurance level based on information received at least from a mobile application, in accordance with some embodiments of the invention. The method may be performed by a processor in a server computer. The method may include receiving, by the server computer, a first set of user information from at least one of a first mobile application or an authorizing server (step  802 ). The first mobile application may be installed/provisioned on a user device, such as a mobile phone of the user. In some embodiments, the authorizing server may have provisioned the first mobile application on the user mobile device. The first set of user information may include one or more of a device identifier, an account number, an address, a zip code, a name, a username, a telephone number or an identity assertion. The server computer may store the received first set of user information at a storage (step  804 ). 
     At step  806 , the server computer may receive a request for a token from a second mobile application, the request comprising at least a second set of user information. The second mobile application may be installed/provisioned on a user device. In some embodiments, the first mobile application and the second mobile application may be provisioned on the same user device. Alternatively, the first mobile application and the second mobile application may be installed/provisioned on separate user devices accessible, for example, with a same username and password. The second mobile application may be a merchant application. The second set of user information may include at least a portion of the first set of user information. The second set of user information may include one or more of a device identifier, an account number, an address, a zip code, a name, a username, a telephone number, user credentials or a user authentication verification value. 
     The server computer may compare the first set of information with the second set of information. That is, the server computer may try to correlate the second set of information with the first set of information. At step  808 , the server computer may determine a confidence level based on the comparison of the first set of user information to the second set of user information. At step  810 , the server computer may generate a token. A status (e.g., an assurance level) of the token may be based at least in part on the confidence level. The status of the token may be indicative of a level of restriction associated with the token. At step  812 , the server computer may transmit the generated token to the second mobile application. 
     In some embodiments, after receiving the token and performing one or more transactions with the token, the second mobile application may send a transaction history to the server computer. Based on the transaction history, the server computer may change the status of the token. For example, if a token with low assurance level is provided to the second mobile application, the status of the token may be increased to high assurance level based on at least the transaction history. 
     According to various embodiments, the first set of information may include an authentication indicator generated by the authorizing server, an identity assertion as part of the first set of user information or an indication of an XML-based security layer validation associated with a user of the second mobile application. The status of the token may be based at least in part in the received information. 
     In some embodiments, the authorization server may receive information from a single mobile application. That is, the token assurance method may not include a first mobile application provisioned by the authorization platform. In addition, the payment processing server may not interact with the authorization platform, as described above. Instead, the payment processing server may rely upon authentication based on reliable data obtained by the mobile application, for example at a merchant location. In some embodiments, the reliable data may include a cryptogram associated with a payment card received from a mobile application or a unique code provided to the user at the merchant location and received from the mobile application. A flowchart of an exemplary method for such embodiments is illustrated in  FIG.  9   . 
       FIG.  9    is a flowchart of another exemplary method  900  for generating a token with an assurance level based on information received at least from a mobile application, in accordance with some embodiments of the invention. The method may be performed by a processor in a server computer. The method may include receiving, by the server computer, a request for a token from a mobile application (step  902 ). The mobile application may be a merchant mobile application installed/provisioned on a user device. The request may include identifying information associated with an account and a value assigned to a user of the account. Upon receipt of the identifying information and the value, the server computer may validate the value assigned to the user of the account (step  904 ). The value assigned to the user may include a cryptogram assigned to a user device associated with the account. For example, the user device may be a payment card including a near field communications (NFC) chip. The cryptogram may be unique to the payment card and the account number associated with the payment card. In some embodiments, the value assigned to the user may include a receipt code associated with a prior transaction carried out using the account. For example, the user may complete a purchase at the merchant location. The merchant may provide the user a receipt with a unique receipt code. 
     At step  906 , the server computer may determine a confidence level based on validating the value assigned to the user of the account. At step  908 , the server computer may generate a token. A status (e.g., an assurance level) of the token may be based at least in part on the confidence level. The status of the token may be indicative of a level of restriction associated with the token. At step  910 , the server computer may transmit the generated token to the second mobile application. 
     Embodiments discussed above provide the ability to accurately identify a consumer and bind the consumer identity to a user device and a payment instrument via a token. Particularly in environments where it is not possible to obtain a static or a unique device ID, the consumer may be authenticated using above-discussed methods and appropriate token may be generated. Embodiments generate tokens with varying quality or assurance levels based on the user information provided by the software application(s) running on the user device. According to various embodiments, the status of the token generated for a software application may be modified (e.g., upgraded) based on the transaction history provided by that software application. 
       FIG.  10    is a functional block diagram illustrating a portable communication device  1002  that may be used to perform mobile banking operations, such as initiating transactions and receiving and displaying transaction alerts, in accordance with some embodiments of the present invention. Portable communication device  1002  may include circuitry that is used to enable certain device functions, such as telephony. The functional elements responsible for enabling those functions may include a processor  1004  that is programmed to execute instructions that implement the functions and operations of the device. Processor  1004  may access data storage  1012  (or another suitable memory region or element) to retrieve instructions or data used in executing the instructions. Data input/output elements  1008  may be used to enable a user to input data (via a microphone or keyboard, for example) or receive output data (via a speaker, for example). Display  1006  may also be used to output data to a user. Communications element  1010  may be used to enable data transfer between device  1002  and a wireless network (via antenna  1018 , for example) to assist in enabling telephony and data transfer functions. Device  1002  may also include contactless element interface  1014  to enable data transfer between contactless element  1016  and other elements of the device, where contactless element  1016  may include a secure memory and a near field communications data transfer element (or another form of short range communications technology). As noted, a mobile phone or similar device is an example of a portable communication device that may be used to display alerts as described with reference to embodiments of the present invention. However, other forms or types of devices may be used without departing from the underlying concepts of the invention. Further, devices that are used to display alerts may not require the capability to communicate using a cellular network in order to be suitable for use with embodiments of the present invention. 
       FIG.  11    is a diagram of a portable consumer device  1100  in the form of a card that includes a contactless payment element  1102 , and that may be used to initiate a transaction, in accordance with some embodiments of the present invention. The payment device depicted in  FIG.  11    may be a “smart card” or similar device, such as a credit or debit type card in which a chip is embedded. One form of such a device is known as an EMV (Europay™, MasterCard™ and Visa™) card. In the context of the present invention, EMV refers to a standard for interoperation of IC cards (“chip cards”) and IC card capable POS terminals and ATMs, and is used for authenticating credit and debit card payments. The EMV standard defines the interactions at the physical, electrical, data and application levels between IC cards and IC card processing devices for use in financial transactions. 
       FIG.  11    shows a substrate  1104  that provides the form factor for device  1100 . A contactless element  1102  for interfacing with a data access or data transfer device may be present on, or embedded within, substrate  1104 . Contactless element  1102  may include a chip or other form of data storage element. Contactless element  1102  may include the capability to communicate and transfer data using a near field communications (NFC) technology or other short range communications technology. Consumer information  1106  such as an account number, expiration date, and consumer name may be printed or embossed on the card. Although not necessary for operation as a contactless payment device, device  1100  may include a magnetic stripe  1108  on substrate  1104 , where magnetic stripe  1108  permits access to contactless element  1102 . This may be used to provide access to data stored in, or the functions of, the chip that is part of the contactless element by a terminal using a magnetic stripe reader. 
     The various participants and elements described herein with reference to  FIGS.  1 - 11    may operate one or more computer apparatuses to facilitate the functions described herein. Any of the elements in  FIGS.  1 - 11   , including any servers or databases, may use any suitable number of subsystems to facilitate the functions described herein. 
     Examples of such subsystems or components are shown in  FIG.  12   . The subsystems shown in  FIG.  12    are interconnected via a system bus  1202 . Additional subsystems such as a printer  1204 , keyboard  1206 , fixed disk  1208  (or other memory comprising computer readable media), monitor  1210 , which is coupled to display adapter  1212 , and others are shown. Peripherals and input/output (I/O) devices, which couple to I/O controller  1214  (which can be a processor or other suitable controller), can be connected to the computer system by any number of means known in the art, such as serial port  1216 . For example, serial port  1216  or external interface  1218  can be used to connect the computer apparatus to a wide area network such as the Internet, a mouse input device, or a scanner. The interconnection via system bus allows the central processor  1220  to communicate with each subsystem and to control the execution of instructions from system memory  1222  or the fixed disk  1208 , as well as the exchange of information between subsystems. The system memory  1222  and/or the fixed disk  1208  may embody a computer readable medium. 
     Embodiments of the invention are not limited to the above-described embodiments. For example, although separate functional blocks are shown for an issuer, payment processing network, and acquirer, some entities perform all of these functions and may be included in embodiments of invention. 
     Specific details regarding some of the above-described aspects are provided above. The specific details of the specific aspects may be combined in any suitable manner without departing from the spirit and scope of embodiments of the invention. For example, back end processing, data analysis, data collection, and other transactions may all be combined in some embodiments of the invention. However, other embodiments of the invention may be directed to specific embodiments relating to each individual aspect, or specific combinations of these individual aspects. 
     It should be understood that the present invention as described above can be implemented in the form of control logic using computer software (stored in a tangible physical medium) in a modular or integrated manner. Based on the disclosure and teachings provided herein, a person of ordinary skill in the art may know and appreciate other ways and/or methods to implement the present invention using hardware and a combination of hardware and software. 
     Any of the software components or functions described in this application, may be implemented as software code to be executed by a processor using any suitable computer language such as, for example, Java, C++ or Perl using, for example, conventional or object-oriented techniques. The software code may be stored as a series of instructions, or commands on a computer readable medium, such as a random access memory (RAM), a read only memory (ROM), a magnetic medium such as a hard-drive or a floppy disk, or an optical medium such as a CD-ROM. Any such computer readable medium may reside on or within a single computational apparatus, and may be present on or within different computational apparatuses within a system or network. 
     The above description is illustrative and is not restrictive. Many variations of the invention may become apparent to those skilled in the art upon review of the disclosure. The scope of the invention should, therefore, be determined not with reference to the above description, but instead should be determined with reference to the pending claims along with their full scope or equivalents. 
     One or more features from any embodiment may be combined with one or more features of any other embodiment without departing from the scope of the invention. 
     A recitation of “a”, “an” or “the” is intended to mean “one or more” unless specifically indicated to the contrary. 
     All patents, patent applications, publications, and descriptions mentioned above are herein incorporated by reference in their entirety for all purposes. None is admitted to be prior art.