Payment system

Patent metadata

Field	Value
Publication number	US-11080693-B2
Application number	US-201314046828-A
Country	US
Kind code	B2
Filing date	Oct 4, 2013
Priority date	Apr 5, 2011
Publication date	Aug 3, 2021
Grant date	Aug 3, 2021

Abstract

Methods, apparatus and computer software are provided for authorizing an EMV transaction between a user device and a point of sale terminal, particularly, but not exclusively, in situations where a secure element is not made available for the deployment of a payment application on the user device. The payment application is instead deployed to a processing environment that is outside of any secure element on the user device. An ICC Master Key corresponding to the payment application is held by a trusted authority, such as the issuing bank. The trusted authority is adapted generate time-limited session keys on the basis of the ICC Master Key and distribute session keys to the payment application. Receipt of a session key by the payment application enables the payment application to conduct an EMV payment transaction. The session key is used to authorize a single EMV payment transaction.

First claim

What is claimed is:

1. A method of enhancing security of a payment application installed on a user device, the method comprising:
receiving, by the user device via a communication network, a first session key different from an ICC Master Key from a remote entity, the first session key based on the ICC Master Key stored at the remote entity, the user device comprising a first processing portion and a second processing portion, the first processing portion comprising a first application environment within a secure element and the second processing portion comprising at least a second application environment, the second processing portion storing the payment application, and the payment application not storing the ICC Master Key on the user device, wherein the first session key is usable for a limited number of one or more transactions;
in response to receiving the first session key, storing, by the second processing portion, the first session key;
in response to storing the first session key, provisioning, by the second processing portion, the payment application with the first session key;
receiving, by the user device via the communication network, a second session key from the remote entity, the second session key based on the ICC Master Key stored at the remote entity, the second session key being different from the first session key and the ICC Master Key;
storing, by the second processing portion, the second session key;
receiving, at the payment application, a request for an application cryptogram, wherein the request is from a point-of-sale terminal; and
in response to the receiving, performing, by the payment application, an authorization process, wherein authorization process comprises:
generating, by the payment application, the application cryptogram based on the received first session key; and
transmitting, by the payment application, the generated application cryptogram to the point-of-sale terminal.

2. The method of claim 1 , further comprising discarding, by the user device, the first session key after generating the application cryptogram.

3. The method of claim 1 , further comprising provisioning, by the second processing portion, the second session key to the payment application in response to a predetermined criterion being satisfied.

4. The method of claim 3 , wherein the predetermined criterion comprises a day, month and year maintained by a certificate provisioning entity matching a date corresponding to a predetermined amount of time having elapsed since the provisioning of the first session key to the user device.

5. The method of claim 3 , wherein the predetermined criterion comprises a number of session keys stored by the user device falling below a predetermined value.

6. The method of claim 1 , where in the user device is a mobile communications device, and the secure element is a Subscriber Identity Module.

7. The method of claim 1 , wherein the second application environment is a Trusted Execution Environment, and the method further comprises one or more of:
storing, by the user device, the first session key in the Trusted Execution Environment;
storing, by the user device, at least part of the payment application in the Trusted Execution Environment; or
executing, by the user device, at least part of the payment application in the Trusted Execution Environment.

8. The method of claim 1 , wherein the transmitting of the generated application cryptogram comprises using a radio frequency communications protocol.

9. The method of claim 1 , wherein the first session key is valid only for a payment transaction.

10. The method of claim 1 , further comprising:
storing, by the user device, a plurality of session keys including the first session key, the second session key, and a third session key sent from the remote entity.

11. The method of claim 10 , wherein the plurality of session keys are stored encrypted in the user device.

12. The method of claim 11 , wherein only one of the plurality of session keys are decrypted at a time.

13. The method of claim 11 , further comprising:
receiving, by the user device, user input; and
decrypting, by the user device, one of the plurality of session keys using the user input as a decryption key.

14. The method of claim 1 , further comprising:
periodically receiving, by the user device, new session keys from the remote entity.

15. The method of claim 1 , wherein a payment transaction conducted using first session key is denied in response to an amount of time between provisioning of the first session and the payment transaction exceeding a threshold amount of time.

Assignees

• Visa Europe Ltd

Inventors

• Fiske Stuart

Classifications

• G07F7/122

  Online card verification · CPC title

• G06Q20/3263

  characterised by activation or deactivation of payment capabilities · CPC title

• G07F7/127

  in which both online and offline card verification can take place · CPC title

• H04L9/083

  involving central third party, e.g. key distribution center [KDC] or trusted third party [TTP] · CPC title

• H04L9/3263

  involving certificates, e.g. public key certificate [PKC] or attribute certificate [AC]; Public key infrastructure [PKI] arrangements (network architectures or network communication protocols for supporting authentication of entities using certificates in a packet data network H04L63/0823) · CPC title