Abstract:
In one embodiment, a method comprises storing a biometric trait of a user in a data communication device of the user, comparing a biometric trait input into the device with the biometric trait stored in the device, generating a certificate authenticating the user within the device if the biometric trait input into the device matches the biometric trait stored in the device, and facilitating a financial transaction of the user using the certificate.

Description:
RELATED APPLICATIONS 
     This application is a continuation of U.S. patent application Ser. No. 14/043,614, filed Oct. 1, 2013, which in turn is a continuation of U.S. patent application Ser. No. 13/418,196, filed Mar. 12, 2012, now U.S. Pat. No. 8,554,689, which is a continuation of U.S. application Ser. No. 12/414,323, filed Mar. 30, 2009, now U.S. Pat. No. 8,150,772, and claims the benefit of U.S. Provisional Application Nos. 61/059,395, filed Jun. 6, 2008 and 61/059,907, Jun. 9, 2008, respectively, the entire disclosure of each of which are incorporated herein by reference. 
    
    
     BACKGROUND 
     1. Technical Field 
     This disclosure relates to electronic financial transactions in general, and more particularly, to methods and systems for biometric authentication of financial transactions by a trusted service manager (TSM). 
     2. Related Art 
     “Contactless technology” refers to short distance communications between two devices that are not physically connected. A wide variety of contactless technology exists today. Near Field Communication (NFC) is a specific type of contactless technology that is of high importance to Mobile Network Operators (MNOs) and to Service Providers (SPs), such as banks, credit card issuers and other payment service providers. NFC is a short-range, high frequency, wireless, RF communication technology that enables the exchange of data between devices typically over about a 10 centimeter (or about 4 inches) distance, thus providing a fast, simple and secure way for a user to effect a wide range of contactless services with a mobile device, such as a mobile telephone or personal digital assistant (PDA). 
     One example of an NFC technology application is financial transactions. NFC mobile devices and other types of contactless devices, such as radio frequency-enabled credit/debit cards, key fobs, and the like are experiencing rapid growth worldwide in various industries, including transportation, retail, parking and other industries, that will now accept NFC mobile payments and other types of contactless payments. 
     As an example, wireless mobile devices that include an NFC device and a smart card, which can use radio frequency identification (RFID) technology for identification purposes, can enable a person to effect a simple financial transaction, such as the purchase of a retail item, in a convenient, secure manner. Typically, a consumer waves the wireless mobile NFC device near a “reader” to effect a monetary transfer, and the purchase price of the item is deducted from a total amount that is available and stored on a “smart card” of the wireless mobile device. Optionally, the amount of the item can be forwarded to a server that can identify the purchaser through a unique identification code of the purchaser and then subsequently debit a credit or deposit account of the purchaser appropriately for the purchase of the retail item. Such NFC-based point of sale (POS) transactions provide several advantages, such as eliminating the need to carry cash and enabling faster, more convenient and secure financial transactions. 
     Because customers are interested in being able to use their mobile devices for contactless services, a new mobile NFC “ecosystem,” illustrated in  FIG. 1 , has been defined by the Global System for Mobile communication Association (GSMA), which is a global trade association representing over 700 GSM mobile phone operators throughout the world. (See, e.g., “Mobile NFC Services,” GSMA, Version 1.0, February 2007). As illustrated in  FIG. 1 , such ecosystems involve a variety of different players or entities and new roles for such players, including:
         Customer—the customer is a customer of a merchant and subscribes to a Mobile Network Operator (MNO) and a service provider.   MNO—the MNO provides a full range of mobile services to the Customer, and can also provide Universal Integrated Circuit Cards (UICCs) and NFC terminals, plus Over the Air (OTA) transport mechanisms.   Service Provider (SP)—the SP provides contactless services to the Customer. Examples of SPs include banks, credit card issuers as well as public transport companies, loyalty programs owners, and the like.   Retailer/Merchant—the retailer/merchant can operate an NFC capable point of sale (POS) terminal.   Trusted Service Manager (TSM)—the TSM securely distributes and manages NFC applications and can have, for example, a direct or an indirect relation to the SPs, e.g., via clearing houses, such as the Automated Clearing House (ACH), the Electronic Payment Network (EPN) or the Visa/MasterCard network.   Handset, NFC Chipset and UICC Manufacturers—the Manufacturers produce mobile NFC/communication devices and the associated UICC hardware.   Reader Manufacturer—the reader manufacturer makes NFC reader devices.   Application Developers—the application developers design and develop mobile NFC applications, including financial transaction applications.   Standardization bodies and industry associations—develop global standards for NFC that enable interoperability, backward compatibility and future development of NFC applications and services.       

     As will be appreciated, successful implementation of NFC technologies requires cooperation between the many disparate players of the GSMA ecosystem. Each player can have its own expectations, for example, the Customer expects convenient, friendly and secure services within a trusted environment; the SPs want their applications to be housed and used in as many mobile devices as possible; and the MNOs want to provide new mobile contactless services that are secure, of high quality and consistent with the existing services experienced by the Customer. But although each player can have its own culture and expectations, they all have the same basic requirement, viz., the need for security and confidentiality. 
     The Trusted Service Manager (TSM), in particular, brings trust and convenience to the complex, multi-player NFC ecosystem. The TSM role includes providing a single point of contact for the SPs, e.g., banks, to access their respective customer bases through the MNOs, and to secure download and lifecycle management for mobile NFC applications on behalf of the SPs. It should be understood that the TSM does not disrupt the SP&#39;s business model, as the TSM does not participate directly in the transaction stage of the service, but rather, only indirectly. 
     In addition to NFC based POS payments, there are a number of other payment models currently prevalent in the mobile industry including:
         (i) Short Message Service (SMS)—SMS is a communications protocol that allows the interchange of short text messages between mobile devices; and,   (ii) Mobile Internet-based payments—Customers routinely search for and purchase products and services through electronic communications with online merchants over electronic networks, such as the Internet.       

     Regarding the latter, individual customers may frequently engage in transactions with a variety of merchants through, for example, various merchant websites. Although a credit card can be used for making payments over the Internet, a disadvantage of online credit card usage is that online merchants can be exposed to high fraud costs and “chargeback fees” because there is no credit card authentication signature with an online sale. 
     In the case of in-person POS payments made with payment cards, such as with Master Cards or Visa cards in the U.S., or a “Chip and PIN” card in the U.K., current authentication is by means of the purchaser&#39;s provision of a signature or a personal identification number (PIN). 
     Accordingly, systems and methods are needed for authenticating NFC based POS transactions securely and reliably without the need for signatures or PINs, and more particularly, for authentication of POS transactions using a biometric trait, such as a fingerprint, that can be input via a data communication device of the user, e.g., the user&#39;s mobile phone. 
     SUMMARY 
     In accordance with the present disclosure, methods and apparatus are provided that enable the authentication of financial transactions to be indirectly effected as a value added service by a service provider acting as a TSM for credit/payment provider companies in which biometric authentication data of the transactions is provided directly at the POS via an NFC enabled mobile telephone without the need for the credit/payment providers having to provide it. 
     In one embodiment, a method comprises storing a biometric trait of a user in a data communication device of the user, comparing a biometric trait input into the device with the biometric trait stored in the device, generating a certificate authenticating the user within the device if the biometric trait input into the device matches the biometric trait stored in the device; and facilitating a financial transaction of the user using the certificate. 
     For example, in an embodiment at a point of sale (POS), a user could activate a mobile phone, invoke a application program stored in a first secure element (SE) therein, and then input a biometric trait to the phone, e.g., could swipe a thumb on a fingerprint reader of the phone. A second SE disposed within the phone might then verify the user&#39;s identity from the biometric trait input to the phone, and upon such verification, generate data sufficient to authenticate the transaction without having to contact and obtain authentication from, e.g., a third party credit/payment service provider. The data of the financial transaction, including the instruction codes therefor and the data authenticating the user, can then be transmitted from the phone to a data communication device of, for example, a merchant or vendor at the POS, which transmission, in one embodiment, can be effected via an NFC link between the phone and the POS device. 
     One or more of the storing of the application program in the first SE, the storing of the user&#39;s credentials in the second SE, and the generating of the data authenticating the transaction in response to the verification of the user&#39;s identity can comprise a value added service performed by a trusted service manager (TSM) on behalf of third party credit or a payment service providers. 
     A better understanding of the above and many other features and advantages of the novel TSM transaction authentication systems and methods of the present disclosure can be obtained from a consideration of the detailed description of some example embodiments thereof below, particularly if such consideration is made in conjunction with the several views of the appended drawings, wherein like elements are referred to by like reference numerals throughout. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         FIG. 1  is a schematic representation of a mobile NFC “ecosystem” defined by the Global System for Mobile communication Association (GSMA); 
         FIG. 2  is a schematic representation of the architecture of an example embodiment of an electronic payment system in accordance with the present disclosure; 
         FIG. 3  is a functional block and data flow diagram of an example embodiment of a mobile phone equipped with a POS transaction authenticating Secure Element (SE) architecture in accordance with the present disclosure engaged in transactional communication with a merchant&#39;s Point Of Sale (POS) device in accordance with the present disclosure; and, 
         FIG. 4  is flow diagram of an exemplary embodiment of a method for making a biometrically authenticated NFC based payment at a POS in accordance with the present disclosure. 
     
    
    
     DETAILED DESCRIPTION 
     In accordance with the embodiments described herein, methods and systems are provided that enable financial service providers, such as PayPal, acting in the role of a Trusted Service Manager (TSM), to authenticate NFC based POS transactions using biometric identifier traits, such as a fingerprint, that can be input via a data communication device of the user. 
       FIG. 2  is a schematic representation of an example embodiment of an electronic payment system in accordance with the present disclosure. A financial transaction using, for example, an NFC based Point of Sale (POS) payment system, can be made using a client data communication device  130 , such as an NFC enabled mobile phone, to a retailer or merchant via a retailer or merchant server  110 . It should be appreciated that although an NFC application is illustrated in this embodiment, the system is not limited to NFC applications, but can also apply to other types of applications, for example, video game consoles, DVRs, and other appliances. 
     The client device  130  can be implemented using any appropriate combination of hardware and/or software configured for wired and/or wireless communication over a network. For example, in one embodiment, the client device  130  can be implemented as a personal computer of a user  120  (also referred to herein as a “customer” or “consumer”) in communication with the Internet or another network, such as a public switched telephone network (PSTN) and/or a private data network. In other embodiments, the client device  130  can be implemented as a wireless telephone, personal digital assistant (PDA), key fob, smart card, notebook computer or other type of data communication device. Furthermore, the client device  130  can be enabled for NFC, Bluetooth, online, infrared communications and/or other types of wireless data communication channels. 
     The client device  130  can include various applications as might be desired in particular embodiments to provide desired features to the client device  130 . Such applications could include, for example, security applications for implementing client-side security features, programmatic client applications for interfacing with appropriate application programming interfaces (APIs) over a network, or other types of applications. 
     The client device  130  can further include one or more user identifiers that could be implemented, for example, as operating system registry entries, cookies associated with a browser application, identifiers associated with hardware of client device  130 , or other appropriate identifiers. In one embodiment, a user identifier can be used by a payment service provider  140  to associate the client device  130  or the user  120  with a particular account maintained by a payment service provider  140 , such as PayPal, as described in more detail below. 
     Of importance, the client device  130  can further include a device useful for biometric authentication, such as a integral fingerprint scanner. Increasingly today, mobile phones are being equipped with such devices. When the phone is “flipped,” or activated, the biometric trait reader reads the fingerprint of the user, confirms the identity of the user from the biometric trait, and upon confirmation of the user&#39;s identity, unlocks a credential/payment instrument located in one or more Secure Element(s) incorporated in the phone. As discussed in more detail below, when the phone is then “tapped” on an NFC enabled POS, an authenticated payment is effected via the user&#39;s biometric data input to the phone. 
     The merchant server  110  could be maintained, for example, by a retailer or by an online merchant offering various products and/or services in exchange for payment to be received over a network, such as the Internet. The merchant server  110  can be configured to accept payment information from the user  120  via, for example, the client device  130  and/or from a payment service provider  140  over a network. It should be appreciated that although a user-merchant transaction is illustrated in this particular embodiment, the system can also be applicable to user-user, merchant-merchant and/or merchant-user transactions. 
     The merchant server  110  can use a secure gateway  112  to connect to an acquirer  115 . Alternatively, the merchant server  110  can connect directly with the acquirer  115  or a processor  120 . Once verified, the acquirer  115 , which can also have a relation or subscription with the payment service provider  140 , processes the transaction through the processor  120  or the payment service provider  140 . “Brands”  125 , for example, bank payment card issuers, which also have a relation or subscription with the payment service provider  140 , are then also involved in the payment transaction so as to enable the user  120  to complete the purchase. 
     The payment service provider  140  can have data connections  155 ,  156 ,  157  and  158  with a subscriber client device  130 , a subscriber acquirer  115 , a subscriber processor  120  and/or a subscriber brand  125 , respectively, to communicate and exchange data. Such data connections  155 ,  156 ,  157  and  158  can take place, for example, via the Short Message Service (SMS) or a Wireless Application Protocol (WAP) over a network. In addition, according to one or more embodiments, the payment service provider  140  can have a data connection  160  with subscriber Internet companies, Internet mortgage companies, Internet brokers or other Internet companies  150 . 
     The payment service provider  140 , which can be an online payment provider, can provide payment on behalf of the user  120  to the operator of the merchant server  110  via the network  210 . In this regard, the payment service provider  140  includes one or more payment applications that can be configured to interact with the client device  130  and/or the merchant server  110  over the network  210  to facilitate the purchase of items by the user  120  from the merchant server  110 . In one embodiment, the payment service provider  140  can be provided by PayPal. 
     Each of the client data communication device  130 , the merchant server  110 , and the payment service provider  140  can include one or more processors, memories, and other appropriate components for executing instructions, such as program code and/or data stored on one or more computer readable mediums to implement the various applications, data, and methods described herein. For example, such instructions can be stored in one or more computer readable media, such as memories or data storage devices internal and/or external to various components of the system, and/or accessible over a network, which can be implemented as a single network or a combination of multiple networks, for example, the Internet or one or more intranets, landline networks, wireless networks, and/or other appropriate types of networks. 
     As discussed above, the payment service provider  140  can also serve in the role of a Trusted Service Manager (TSM). In one example embodiment of this, the payment service provider  140 , acting in the role TSM, can work cooperatively with a Mobile Network Operator (MNO) to incorporate an authentication certificate issued by the payment service provider, acting as a Certificate Authority (CA), in a Secure Element (SE) or Subscriber Identity Module (SIM) card  215  of a client device  130 . This SE or SIM card can follow security guidelines, such as The Federal Information Processing Standard (FIPS) Publication 140-2 (FIPS 140-2 Level 2/3), a U.S. government computer security standard issued by the National Institute of Standards and Technology (NIST) and used to accredit cryptographic modules. The client device  130  can already have payment service provider issued certificates and user biometric trait information, such as the user&#39;s digitized fingerprint, stored within it for personalization purposes. When customers or users activate their payment service provider application  225 , such as a PayPal payment application, which can also be incorporated in the client device  130  in an “application SE,” the users or customers are asked to select a PIN, which can be optional or mandatory. The PIN protects the private key of the authenticating certificate. 
     When a transaction, for example a financial transaction using NFC service application  217  of an NFC enabled client device  130 , is made via a payment service provider  140  such as PayPal, the service provider  140  receives signature information in the form of, for example, a X.509 certificate. X.509 is an ITU-T standard for a public key infrastructure (PKI) for single sign-on and Privilege Management Infrastructure (PMI). This X.509 signature information is typically maintained for each registered user of the service provider  140 . The signature information can be a digital signature and can include a time stamp, dollar amount, transaction type, item, and even location, which can be determined from a GPS enabled client device  130 . Signature information can also be preloaded in client device  130  in, for example, other applications, such as EMV (Europay, MasterCard, Visa), a standard for interoperation of IC cards (“Chip cards”) and IC capable POS terminals and ATM&#39;s, for authenticating credit and debit card payments, or Elliptic Curve Cryptography (ECC), another form of public-key cryptography, in addition to X.509. In addition to NFC, the client device  130  can also be enabled for, e.g., Bluetooth, infrared or other types of communications and/or transactions. 
       FIG. 3  is a functional block and data flow diagram of an example embodiment of a client device  120  that comprises an NFC enabled mobile phone  300  engaged in transactional communication with a NFC enabled Point Of Sale (POS) data communication device  120  of, e.g., a merchant, in accordance with the present disclosure. In the particular embodiment of  FIG. 3 , the phone  300  is equipped with a biometric trait data input device  302 , such as a fingerprint scanner, a POS transaction authenticating “Payment/Wallet” Secure Element (SE)  304 , an “Application” SE  306 , and an NFC communication module  308 , as described above. 
     With reference to  FIG. 3 , it can be noted that the two SEs  304  and  306  comprise two separate elements, viz., a Payment/Wallet SE  304 , which can be, e.g., a SIM card, that stores only payment instruments, certificates, keys, user accounts, credentials and biometric trait authentication data, and the like, and an Application SE  306 , which can also be a SIM card, that stores only application programs  310  adapted to, e.g., generate instruction codes to effect final transactions, such as the purchase of goods or services or the transfer of money to or from the user. Thus, no user payment instruments, account data, certificates, keys or credentials reside in the Application SE  306 . In the particular embodiment illustrated, the Payment/Wallet SE  304  supports biometric trait authentication of the user, and the two SEs  304  and  306  are therefore split into two separate devices because, once the Payment/wallet SE  304  is certified by the TSM, such as through MasterCard or VISA, with the user&#39;s biometric trait data and other credential data, the phone  300  is then TSM-certified for use. Then, if it later becomes desirable to modify application programs of or add additional programs to the Application SE  306 , a new or re-certification procedure does not have to be performed each time they are modified or added, because applications do not need to be certified, whereas, Payment/Wallet SEs  306 , containing as they do the user&#39;s TSM-authenticated credentials, must be certified by the TSM before use with the affected payment service providers. 
     The initial set-up or programming of the Payment/Wallet SE  306  needs to be done only once, and can be performed at the premises of the TSM, or alternatively, over the air (OTA). Likewise, new or updated applications can be uploaded to the Applications SE  304  of the phone  300  either locally or OTA. 
     In one advantageous embodiment, the Payment/Wallet SE  306  can also be configured to store a list of transactions or account or receipt management information that can be viewed by the user at will on the phone  300  and/or downloaded to a PC for integration with the user&#39;s money management tools, such as Quicken, Microsoft Money, dedicated toolbars, or other PC software, such as expense management and expense submission tools and flexible spending account submissions. 
     As discussed above, current authentication of transactions via payment cards is typically by way of a user&#39;s signature or PIN. In Europe, authentication can also be via “Chip and PIN”. However, as illustrated in  FIG. 3 , in accordance with the present disclosure, the authentication of financial transactions, such as at a POS  110 , can be indirectly effected as a value added service by a service provider acting as a TSM for credit/payment provider companies, such as MasterCard and Visa, in which POS biometric authentication occurs directly via the mobile phone  300 . This biometric authentication can serve as signature/PIN/Chip and PIN/ARQC-ARPC authentication for all transactions. The authenticated transaction is then submitted to the POS device  110  via the NFC link between the NFC communication module  308  of the phone  300  and the POS device  110 . The POS device  110  receives the transaction as a pre-verified or pre-authenticated request, and in turn, transmits it to the host processor  120  for further processing in the form of an ISO  8583  message containing a Card Verification Value (CVV) code or a Contactless Card and Chip Verification (iCVV) code field, and other information, such as a Stored-Value Card (SVC) code and/or a bank identification number (BIN) code. Thus, a user&#39;s initial input of a biometric trait via the input device  302  can be used both to unlock the phone  300  and to authorize financial transactions without the need for the credit/payment providers having to do so. 
       FIG. 4  is flow diagram of an exemplary embodiment of a method  400  for making a biometrically authenticated NFC based payment at a POS  110  using the NFC and biometric trait data enabled phone  300  of  FIG. 3  in accordance with the present disclosure. With reference to  FIG. 4 , the method  400  begins at S 402  with the one-time setup or user registration procedure with the TSM as described above. 
     After the initial registration of the user with the TSM is complete, during which step S 402 , the Payment/Wallet SE  304  of the phone  330  is programmed with the user&#39;s credentials and the Application SE  306  of the phone  300  is programmed with one or more suitable financial transaction application programs  310 , the phone  300  is then ready for use in making authenticated financial transactions. In an example purchase transaction at a POS  110 , such as illustrated in  FIG. 3 , the user, in the role of a purchaser, can, at S 404 , first activate the phone  300 , e.g., by opening it. At S 406 , the user can then select a “Make Payment” button on the phone  300 . Selecting the Make Payment button invokes a suitable payment application program  310  in the Application SE  306  of the phone  300  that is adapted to, among other things, read a biometric trait of the user, e.g., the user&#39;s thumb-print and request verification of it by the Payment/Wallet SE  304 . 
     At S 408 , the user-purchaser then swipes his or her thumb on the biometric trait input device  302  of the phone  302 , and at S 410 , this biometric trait input is fed directly to the Payment/Wallet SE  304  of the phone  300  via a “tunnel” circuitry  312 . Optionally, the thumb swipe can also be operable to unlock the phone for use. Preferably, a tunnel circuit  312  is used for security purposes because the architecture of the user&#39;s fingerprint is such that it can otherwise be captured by an application on a mobile phone. To prevent this, a tunnel encryption circuitry  312  that is FIPS 140-2 level 3 compliant is incorporated in the phone  300  so that the fingerprint data goes directly to the Payment/Wallet SE  304  of the phone  300  for authentication and unlocking. 
     At S 412 , the payment application  310  that was invoked by pressing the Make Payment button sends a message to the Payment/Wallet SE  304  requesting user verification and payment authentication. At S 414 , when the Payment/Wallet SE  304  verifies the user&#39;s thumbprint, and based thereon, authenticates the payment, the Payment/Wallet SE  304  sends the authenticated payment (or other) instructions back to the payment application  310 , which then sends it to the NFC communication module  308  of the phone  300 . 
     At S 416 , when the user then “taps” the phone  300  on the merchant&#39;s POS device  110 , the pre-authenticated payment instructions are transmitted via an NFC link to the POS device  110 , and thence, to the merchant&#39;s processor device  110 . As above, the payment instructions include not only all of the payment information needed to effect the transaction, such as the user&#39;s account information or credit balance, but also all of the information necessary to authenticate the transaction, including CVV, iCVV, SVC and/or BIN codes, without the need for the credit/payment service providers having to provide it. 
     As those of skill in this art will appreciate, although the foregoing method is described in the context of a transaction involving a purchase of goods or services at a POS, it is evident that it can be made applicable to other types of financial transactions, such as the deposit or withdrawal of cash at an automated teller machine (ATM). 
     Although various components and steps have been described herein as being associated with the client device  130 , merchant server  110 , and payment service provider  140  of  FIGS. 1-3 , it is contemplated that the various aspects of such servers illustrated in  FIGS. 1-3  can be distributed among a plurality of servers, devices, and/or other entities. For example, in one embodiment, transaction record processing application  290  and transaction records  295  can be implemented by an entity separate from payment service provider  140 . Accordingly, in such an embodiment, communications described herein performed in relation to transaction record processing application  290  and transaction records  295  can be provided to a separate entity and need not be routed through payment service provider  140  in all instances. 
     Where applicable, various embodiments provided by the present disclosure can be implemented using hardware, software, or combinations of hardware and software. Also where applicable, the various hardware components and/or software components set forth herein can be combined into composite components comprising software, hardware, and/or both without departing from the spirit of the present disclosure. Where applicable, the various hardware components and/or software components set forth herein can be separated into sub-components comprising software, hardware, or both without departing from the spirit of the present disclosure. In addition, where applicable, it is contemplated that software components can be implemented as hardware components, and vice-versa. 
     Software in accordance with the present disclosure, such as program code and/or data, can be stored on one or more computer readable media. It is also contemplated that software identified herein can be implemented using one or more general purpose or specific purpose computers and/or computer systems, networked and/or otherwise. Where applicable, the ordering of various steps described herein can be changed, combined into composite steps, and/or separated into sub-steps to provide the features described herein. 
     The foregoing disclosure is not intended to limit the present disclosure to the precise forms or particular fields of use disclosed. It is contemplated that various alternate embodiments and/or modifications to the present disclosure, whether explicitly described or implied herein, are possible in light of the disclosure. 
     Although the apparatus and methods of the present invention have been described and illustrated herein with reference to certain specific example embodiments thereof, it should be understood that a wide variety of modifications and variations can be made to these without departing from the spirit and scope of the invention, as defined by the claims appended hereafter and their functional equivalents.