Trusted service manager (TSM) architectures and methods

• US 8,417,643 B2
• Filed: 12/20/2011
• Issued: 04/09/2013
• Est. Priority Date: 06/06/2008
• Status: Active Grant

• Current Assignee: PayPal, Inc. (PayPal Holdings, Inc.)
• Original Assignee: eBay Inc.
• Inventors: Mardikar, Upendra
• Primary Examiner(s): OBEID, MAMON A
• Application Number:
  US13/331,801
• Publication Number:
  US 20120089520A1
• Time in Patent Office: 476 Days
• Field of Search: 705 64- 67, 705/78, 713/182, 713/185, 713/186, 726 27- 30, 235/379, 235/380
• US Class Current: 705/67
• CPC Class Codes: G06Q 20/1085 involving automatic teller machines [ATMs]
• CPC Class Codes: G06Q 20/20 Point-of-sale [POS] network systems
• CPC Class Codes: G06Q 20/204 comprising interface for record bearing medium or carrier for electronic funds transfer or payment credit
• CPC Class Codes: G06Q 20/3223 Realising banking transactions through M-devices
• CPC Class Codes: G06Q 20/3227 using secure elements embedded in M-devices
• CPC Class Codes: G06Q 20/3265 characterised by personalisation for use
• CPC Class Codes: G06Q 20/3278 RFID or NFC payments by means of M-devices
• CPC Class Codes: G06Q 20/367 involving electronic purses or money safes
• CPC Class Codes: G06Q 20/3674 involving authentication
• CPC Class Codes: G06Q 20/382 insuring higher security of transaction
• CPC Class Codes: G06Q 20/3821 Electronic credentials
• CPC Class Codes: G06Q 20/3829 involving key management
• CPC Class Codes: G06Q 20/40 Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
• CPC Class Codes: G06Q 20/4012 Verifying personal identification numbers [PIN]
• CPC Class Codes: G06Q 20/40145 Biometric identity checks
• CPC Class Codes: G06Q 40/00 Finance; Insurance; Tax strategies; Processing of corporate or income taxes
• CPC Class Codes: G07C 9/257 electronically G07C9/26 takes precedence
• CPC Class Codes: G07F 7/0826 Embedded security module
• CPC Class Codes: H04L 2209/56 Financial cryptography, e.g. electronic payment or e-cash
• CPC Class Codes: H04L 2209/80 Wireless network architectures or network communication protocols for wireless network security H04W12/00
• CPC Class Codes: H04L 63/0823 : using certificates cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263
• CPC Class Codes: H04L 63/0861 : using biometrical features, e.g. fingerprint, retina-scan cryptographic mechanisms or cryptographic arrangements for entity authentication using biological data H04L9/3231
• CPC Class Codes: H04L 9/3231 : Biological data, e.g. fingerprint, voice or retina network architectures or network communication protocols for supporting authentication of entities using biometrical features in a packet data network H04L63/0861
• CPC Class Codes: H04W 12/069 : using certificates or pre-shared keys
• CPC Class Codes: H04W 4/80 : Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication

Abstract

A client device comprises a first secure element and a second secure element. The first secure element comprises a first computer-readable medium having a payment application comprising instructions for causing the client device to initiate a financial transaction. The second secure element comprises a second computer-readable medium having a security key, a payment instrument, stored authentication data and instructions for generating a secure payment information message responsive to the payment application. The secure payment information message comprises the payment instrument and is encrypted in accordance with the security key.

Claims

1. A client device for making a contactless payment at a point of sale (POS), comprising:

a first secure element comprising a first computer-readable medium containing instructions for causing the client device to securely download a payment application to the first secure element from a trusted service manager (TSM), wherein;

the first secure element is programmed to download the payment application in response to determining that the payment application is signed by the TSM;

a second secure element, physically separate from the first secure element, comprising a second computer-readable medium having;

instructions for registering the client device with the TSM only through the second secure element, exclusive of the first secure element, wherein;

the client device is registered with the TSM for authentication by registering an authentication data that is obtained using a user authentication input device of the client device;

instructions for storing the authentication data in the second secure element of the registered client device, wherein the stored authentication data is excluded from the first secure element;

instructions for storing a security key in the second secure element of the registered client device, wherein the security key is excluded from the first secure element;

instructions for storing a payment instrument in the second secure element of the registered client device, wherein the payment instrument is excluded from the first secure element; and

a secure tunnel circuit for secure input of the user authentication data directly to the second secure element;

a memory storage device, comprising a third computer-readable medium containing instructions, that when executed by the client device, cause the client device to;

execute the payment application resident on the first secure element;

signal, by the payment application, the user authentication input device of the client device to input a user authentication data obtained from the user of the registered client device;

input, by the user authentication input device in response to the signal from the payment application, the obtained user authentication data;

send the obtained user authentication data to the second secure element via the secure tunnel circuit; and

wherein the stored authentication data is excluded from the first secure element;

wherein the second computer-readable medium of the second secure element includes instructions for;

comparing the obtained user authentication data to the stored authentication data in response to signaling by the payment application and

generating the secure payment information message in response to an authentication including a match of the obtained user authentication data with the stored authentication data;

wherein the generated secure payment information message comprises the payment instrument and is encrypted in accordance with the security key; and

transmitting the generated secure payment information message to a POS reader by one of near field communication (NFC), infrared, short range wireless connectivity, secure short message service (SMS), or direct secure communication from the second secure element to the POS.

2. The client device of claim 1, wherein the user authentication input device comprises a biometric sensor and the authentication data comprises a biometric signature corresponding to a biometric feature of a user.

3. The client device of claim 2, wherein the biometric sensor comprises one of a finger/thumb-print sensor, a voice recognition sensor or a retina scanner.

4. The client device of claim 1, wherein the user authentication input device comprises a keyboard and the authentication data comprises a personal identifying number (PIN).

5. The client device of claim 2, further comprising a keyboard for entering a PIN, the keyboard being connected to the second secure element by a second secure tunnel circuit.

6. The client device of claim 1, further comprising a payment mode button for switching the client device into a secure payment mode, wherein the second secure tunnel circuit is enabled when the client device is in the secure payment mode.

7. The client device of claim 1, further comprising a communication chip for communicating the secure payment information message responsive to the payment application, wherein the message is transmitted in one of NFC, infrared, Bluetooth or SMS.

8. The client device of claim 1, wherein the secure payment information message is a secure SMS message addressed to a trusted service manager (TSM) and comprising an address for a financial service provider (SP) to which the TSM is to forward the secure payment information message.

9. The client device of claim 8, wherein the payment information is encrypted using AES-256, and an SHA-512 HMAC is attached.