|Publication number||US8150772 B2|
|Application number||US 12/414,323|
|Publication date||Apr 3, 2012|
|Filing date||Mar 30, 2009|
|Priority date||Jun 6, 2008|
|Also published as||CN102057386A, CN102057386B, CN105046479A, EP2308014A1, EP2308014A4, US8108318, US8417643, US8554689, US20090307139, US20090307140, US20090307142, US20090307778, US20120089520, US20120173434, US20130198086, US20150056957, WO2010002541A1|
|Publication number||12414323, 414323, US 8150772 B2, US 8150772B2, US-B2-8150772, US8150772 B2, US8150772B2|
|Inventors||Upendra Mardikar, Eric Duprat|
|Original Assignee||Ebay Inc.|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (36), Non-Patent Citations (10), Referenced by (18), Classifications (45), Legal Events (3)|
|External Links: USPTO, USPTO Assignment, Espacenet|
This application claims benefit of U.S. Provisional Application Nos. 61/059,395, filed Jun. 6, 2008, and 61/059,907, filed Jun. 9, 2008, the respective disclosures of which are incorporated herein by reference.
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 may 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 may 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
As will be appreciated, successful implementation of NFC technologies requires cooperation between the many disparate players of the GSMA ecosystem. Each player may 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 may 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'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 may be used for making payments over the Internet, a disadvantage of online credit card usage is that online merchants may 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'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's mobile phone.
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 for authenticating a financial transaction at a point of sale (POS) includes storing an application program in a first secure element (SE) of a mobile phone equipped with a user biometric trait input device. The application program is configured to generate instruction codes to effect the financial transaction upon verification of a user's identity. The credentials of the user are stored in a second SE of the phone, which is operable to verify the user's identity from a biometric trait of the user input to the phone and to generate data authenticating the financial transaction in response to the verification of the user's identity.
At the POS, the user activates the phone, invokes the application program thereon and inputs a biometric trait to the phone, e.g., swipes a thumb on a fingerprint reader of the phone. The second SE verifies the user's identity from the biometric trait input to the phone, and upon such verification, generates data authenticating the transaction. The data of the financial transaction, including the instruction codes therefor and the data authenticating the financial transaction, are then transmitted from the phone to a data communication device at the POS, which in one embodiment, may be effected via a 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's credentials in the second SE, and the generating of the data authenticating the transaction in response to the verification of the user's identity may comprise a value added service performed by a trusted service manager (TSM) on behalf of a third party credit or a payment service provider.
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 may 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.
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.
The client device 130 may 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 may 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 may 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 may be enabled for NFC, Bluetooth, online, infrared communications and/or other types of wireless data communication channels.
The client device 130 may include various applications as may be desired in particular embodiments to provide desired features to the client device 130. Such applications may 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 may further include one or more user identifiers that may 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 may 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 may 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'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's biometric data input to the phone.
The merchant server 110 may 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 may 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 may also be applicable to user-user, merchant-merchant and/or merchant-user transactions.
The merchant server 110 may use a secure gateway 112 to connect to an acquirer 115. Alternatively, the merchant server 110 may connect directly with the acquirer 115 or a processor 120. Once verified, the acquirer 115, which may 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 may 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 may 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 may 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 may be an online payment provider, may 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 may 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 may be provided by PayPal.
Each of the client data communication device 130, the merchant server 110, and the payment service provider 140 may 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 may 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 may 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, may 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 may 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 may already have payment service provider issued certificates and user biometric trait information, such as the user'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 may also be incorporated in the client device 130 in an “application SE,” the users or customers are asked to select a PIN, which may 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 may be a digital signature and may include a time stamp, dollar amount, transaction type, item, and even location, which may be determined from a GPS enabled client device 130. Signature information may 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'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 may also be enabled for, e.g., Bluetooth, infrared or other types of communications and/or transactions.
With reference to
The initial set-up or programming of the Payment/Wallet SE 306 needs to be done only once, and may 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 may 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'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's signature or PIN. In Europe, authentication may also be via “Chip and PIN”. However, as illustrated in
After the initial registration of the user with the TSM is complete, during which step S402, the Payment/Wallet SE 304 of the phone 330 is programmed with the user'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
At S408, the user-purchaser then swipes his or her thumb on the biometric trait input device 302 of the phone 302, and at S410, 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 may 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'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 S412, 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 S414, when the Payment/Wallet SE 304 verifies the user'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 S416, when the user then “taps” the phone 300 on the merchant'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'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'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
Where applicable, various embodiments provided by the present disclosure may 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 may 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 may be implemented as hardware components, and vice-versa.
Software in accordance with the present disclosure, such as program code and/or data, may be stored on one or more computer readable media. It is also contemplated that software identified herein may 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 may 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 may 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.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US6269348||Jan 29, 1999||Jul 31, 2001||Veristar Corporation||Tokenless biometric electronic debit and credit transactions|
|US6581042||May 3, 2001||Jun 17, 2003||Indivos Corporation||Tokenless biometric electronic check transactions|
|US6819219 *||Oct 13, 2000||Nov 16, 2004||International Business Machines Corporation||Method for biometric-based authentication in wireless communication for access control|
|US7016494 *||Mar 26, 2001||Mar 21, 2006||Hewlett-Packard Development Company, L.P.||Multiple cryptographic key precompute and store|
|US7251731 *||Nov 16, 2001||Jul 31, 2007||France Telecom||Call set-up from a mobile radio telephone terminal with biometric authentication|
|US7454194 *||Mar 25, 2004||Nov 18, 2008||Sharp Kabushiki Kaisha||Mobile terminal with personal authentication function and mobile terminal system|
|US7512567||Dec 5, 2006||Mar 31, 2009||Yt Acquisition Corporation||Method and system for providing biometric authentication at a point-of-sale via a mobile device|
|US7543738 *||Jul 28, 2005||Jun 9, 2009||American Express Travel Related Services Company, Inc.||System and method for secure transactions manageable by a transaction account provider|
|US20030163710 *||Dec 17, 2002||Aug 28, 2003||Ortiz Luis Melisendro||Random biometric authentication utilizing unique biometric signatures|
|US20030167207 *||Jan 10, 2003||Sep 4, 2003||Berardi Michael J.||System and method for incenting payment using radio frequency identification in contact and contactless transactions|
|US20050033688 *||Jul 23, 2004||Feb 10, 2005||American Express Travel Related Services Company, Inc.||Methods and apparatus for a secure proximity integrated circuit card transactions|
|US20050171898||Sep 30, 2004||Aug 4, 2005||American Express Travel Related Services Company, Inc.||Systems and methods for managing multiple accounts on a rf transaction device using secondary identification indicia|
|US20050187883 *||May 11, 2005||Aug 25, 2005||American Express Travel Related Services Company, Inc.||Methods and apparatus for conducting electronic transactions using biometrics|
|US20050190912 *||Mar 26, 2001||Sep 1, 2005||Hopkins W. D.||Multiple cryptographic key precompute and store|
|US20050242177 *||Feb 2, 2005||Nov 3, 2005||Dexit Inc.||RFID-based system and method of conducting financial transactions|
|US20050273609||Jun 4, 2004||Dec 8, 2005||Nokia Corporation||Setting up a short-range wireless data transmission connection between devices|
|US20060023486 *||Jul 28, 2005||Feb 2, 2006||Ias L.L.C.||High-assurance processor active memory content protection|
|US20060287004 *||Jun 17, 2005||Dec 21, 2006||Fuqua Walter B||SIM card cash transactions|
|US20070022058||Jul 18, 2006||Jan 25, 2007||Fujitsu Limited||Wireless computer wallet for physical point of sale (POS) transactions|
|US20070052517 *||Oct 25, 2006||Mar 8, 2007||American Express Travel Related Services Company, Inc.||Systems and methods for non-traditional payment using biometric data|
|US20070092114 *||Oct 25, 2006||Apr 26, 2007||Swisscom Mobile Ag||Method, communication system and remote server for comparing biometric data recorded with biometric sensors with reference data|
|US20070136211 *||Dec 30, 2006||Jun 14, 2007||Brown Kerry D||Financial transactions with dynamic card verification values|
|US20070175023 *||Jan 10, 2007||Aug 2, 2007||Heitmann Kjell A||Tamper barrier for electronic device|
|US20070197261 *||Mar 16, 2005||Aug 23, 2007||Humbel Roger M||Mobile Telephone All In One Remote Key Or Software Regulating Card For Radio Bicycle Locks, Cars, Houses, And Rfid Tags, With Authorisation And Payment Function|
|US20070293202 *||May 25, 2007||Dec 20, 2007||Celltrust Corporation||Secure mobile information management system and method|
|US20070295803 *||Jun 22, 2006||Dec 27, 2007||Hip Consult Inc.||Apparatus and method for facilitating money or value transfer|
|US20080064346 *||Sep 11, 2007||Mar 13, 2008||Inside Contactless||Method for connecting a contactless integrated circuit to a nfc component|
|US20080065885||Jul 18, 2007||Mar 13, 2008||Yasushi Nagai||Data processing apparatus|
|US20080129450 *||Dec 4, 2007||Jun 5, 2008||Infineon Technologies Ag||Apparatus for selecting a virtual card application|
|US20080144650 *||Dec 11, 2007||Jun 19, 2008||Infineon Technologies Ag||Apparatus for contactless transmission of data from a memory|
|US20080155268 *||Dec 20, 2006||Jun 26, 2008||Spansion Llc||Secure data verification via biometric input|
|US20080201264 *||Oct 20, 2007||Aug 21, 2008||Brown Kerry D||Payment card financial transaction authenticator|
|US20080207124 *||Jan 5, 2007||Aug 28, 2008||Nokia Corporation||Mobile Device With Near Field Communication Module And Secure Chip|
|US20080230615 *||Mar 19, 2007||Sep 25, 2008||Sony Corporation||Near-field communication card for communication of contact information|
|US20090143104 *||Sep 19, 2008||Jun 4, 2009||Michael Loh||Wireless smart card and integrated personal area network, near field communication and contactless payment system|
|EP2034428A1 *||Sep 7, 2007||Mar 11, 2009||Vodafone Holding GmbH||NFC capable mobile communication device|
|1||*||"Contactless Technology for Secure Physical Access: Technology and Standards Choices", Smart Card Alliance, Oct. 2002, all pages, http://www.smartcardalliance.org/resources/lib/Contactless-Technology-Report.pdf.|
|2||*||"FIPS PUB 140-2", National Institute of Standards and Technology (NIST), May 25, 2001, all pages, http://csrc.nist.gov/publications/fips/fips140-2/fips1402.pdf.|
|3||*||"NFC = Simplicity", Nokia, 2007, all pages, http://www.hccomp.eu/files/NFC-4.pdf.|
|4||*||"Reader Series 4000: S4100 Multi-Function Reader Module RF-MGR-MNMN ISO 14443 Library Reference Guide", Texas Instrument, Oct. 2003, all pages, http://www.ti.com/rfid/docs/manuals/refmanuals/RF-MGR-MNMN-14443-refGuide.pdf.|
|5||*||"Understanding the Requirements of ISO/EIC 14443 for Type B Proximity Contactless Identification Cards", Amtel, Nov. 2005, all pages, http://www.atmel.com/dyn/resources/prod-documents/doc2056.pdf.|
|6||*||"Contactless Technology for Secure Physical Access: Technology and Standards Choices", Smart Card Alliance, Oct. 2002, all pages, http://www.smartcardalliance.org/resources/lib/Contactless—Technology—Report.pdf.|
|7||*||"Understanding the Requirements of ISO/EIC 14443 for Type B Proximity Contactless Identification Cards", Amtel, Nov. 2005, all pages, http://www.atmel.com/dyn/resources/prod—documents/doc2056.pdf.|
|8||*||Baddeley, D., "ISO/IEC 14443-3 Identification cards-Contactless integrated circuit(s) cards-Proximity cards-Part 3: Initialization and anticollision", ISO/EIC, Jun. 11, 1999, all pages, http://www.waazaa.org/download/fcd-14443-3.pdf.|
|9||*||Baddeley, D., "ISO/IEC 14443-3 Identification cards—Contactless integrated circuit(s) cards—Proximity cards—Part 3: Initialization and anticollision", ISO/EIC, Jun. 11, 1999, all pages, http://www.waazaa.org/download/fcd-14443-3.pdf.|
|10||*||U.S. Appl. No. 60/974,424, filed Sep. 21, 2007.|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US8490872 *||Jun 15, 2011||Jul 23, 2013||Moon J. Kim||Light-powered smart card for on-line transaction processing|
|US8571937||Oct 20, 2011||Oct 29, 2013||Playspan Inc.||Dynamic payment optimization apparatuses, methods and systems|
|US8577803||Jun 1, 2012||Nov 5, 2013||Visa International Service Association||Virtual wallet card selection apparatuses, methods and systems|
|US8650628 *||Apr 27, 2010||Feb 11, 2014||Cox Communications, Inc.||Automated user authentication identification for customized converged services|
|US8832800 *||Aug 24, 2010||Sep 9, 2014||Administradora De Proyectos Y Sistemas Avanzados, S.C.||Method for producing an electro-biometric signature allowing legal interaction between and identification of persons|
|US8918855 *||Dec 9, 2011||Dec 23, 2014||Blackberry Limited||Transaction provisioning for mobile wireless communications devices and related methods|
|US9117225||Sep 17, 2012||Aug 25, 2015||Visa International Service Association||Apparatuses, methods and systems for transforming user infrastructure requests inputs to infrastructure design product and infrastructure allocation outputs|
|US9165295||May 9, 2011||Oct 20, 2015||Moon J. Kim||Automated card information exchange pursuant to a commercial transaction|
|US9189723||Jul 22, 2013||Nov 17, 2015||Moon J. Kim||Light-powered smart card for on-line transaction processing|
|US9355393||Mar 13, 2013||May 31, 2016||Visa International Service Association||Multi-directional wallet connector apparatuses, methods and systems|
|US20110265165 *||Oct 27, 2011||Cox Communications, Inc.||Automated User Authentication Identification for Customized Converged Services|
|US20120150741 *||Dec 13, 2011||Jun 14, 2012||Electronics And Telecommunications Research Institute||Mobile device for providing smart wallet service and layer structure for operating smart wallet service|
|US20120192254 *||Aug 24, 2010||Jul 26, 2012||Administradora De Proyesctos Y Sistemas Avanzados, S.C.||Method for producing an electro-biometric signature allowing legal interaction between and identification of persons|
|US20130009756 *||Jul 7, 2011||Jan 10, 2013||Nokia Corporation||Verification using near field communications|
|US20130152185 *||Jun 13, 2013||Research In Motion Limited||Transaction provisioning for mobile wireless communications devices and related methods|
|US20140082569 *||Sep 17, 2012||Mar 20, 2014||Steven Robert Borgman||Security System and Methods For Portable Devices|
|US20150149359 *||Nov 27, 2013||May 28, 2015||At&T Intellectual Property I, L.P.||Out-Of-Band Device Verification of Transactions|
|US20160048840 *||Mar 17, 2015||Feb 18, 2016||Egis Technology Inc.||Fingerprint recognition control methods for payment and non-payment applications|
|U.S. Classification||705/64, 705/76, 713/186|
|Cooperative Classification||H04L63/0861, G06Q20/3227, H04W12/06, G06Q20/3278, H04L63/0823, H04L2209/80, H04L2209/56, G06Q20/3821, G06Q20/382, G06Q20/20, G06Q20/4012, G06Q20/32, G06Q20/1085, G07C9/00087, G06Q20/3674, G07F7/0826, G06Q20/367, G06Q20/40, H04L9/3231, G06Q20/204, G06Q20/3223, G06Q20/3829, G06Q40/00, G06Q20/40145|
|European Classification||G07C9/00B6D4, G06Q20/40, H04L9/32, G06Q20/32, G06Q20/20, G07F7/08A2D, G06Q20/1085, G06Q20/4012, G06Q20/40145, G06Q20/382, G06Q20/204, G06Q20/3829, G06Q20/3674, G06Q20/3821, G06Q20/3223, G06Q20/367, G06Q40/00|
|Apr 13, 2009||AS||Assignment|
Owner name: EBAY, INC., CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:MARDIKAR, UPENDRA;DUPRAT, ERIC;REEL/FRAME:022539/0623;SIGNING DATES FROM 20090319 TO 20090325
Owner name: EBAY, INC., CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:MARDIKAR, UPENDRA;DUPRAT, ERIC;SIGNING DATES FROM 20090319 TO 20090325;REEL/FRAME:022539/0623
|Jul 23, 2015||AS||Assignment|
Owner name: PAYPAL, INC., CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:EBAY INC.;REEL/FRAME:036170/0540
Effective date: 20150717
|Oct 1, 2015||FPAY||Fee payment|
Year of fee payment: 4