# US 2023/0306419 A1 · Payment system

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2023/0306419 A1
- Document ID: US20230306419A1
- Status: Published application
- Kind: A1
- Application number: 18/320,103
- Filed: 2023-05-18
- Published: 2023-09-28
- Earliest claimed: 2011-04-05
- Assignees: Visa Europe Limited
- Applicants: Visa Europe Limited
- Inventors: Stuart Fiske
- Web page: https://patentgrep.com/patent/US20230306419A1

## CPC

- G06Q 20/3829: {involving key management}
- G06Q 20/322: {Aspects of commerce using mobile devices [M-devices]}
- G06Q 20/3263: {characterised by activation or deactivation of payment capabilities}
- G06Q 20/3265: {characterised by personalisation for use}
- G06Q 20/3278: {RFID or NFC payments by means of M-devices}
- G07F 7/122: {Online card verification}
- G07F 7/127: {in which both online and offline card verification can take place}
- H04L 9/083: {involving central third party, e.g. key distribution center [KDC] or trusted third party [TTP]}
- H04L 9/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)}
- H04L 2209/56: Financial cryptography, e.g. electronic payment or e-cash
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G07F: COIN-FREED OR LIKE APPARATUS (coin sorting G07D3/00; coin testing G07D5/00; {handling coins or paper currencies apart from payment activated apparatus G07D; payment architectures, schemes or protocols G06Q20/00})
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## 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.

## Claims

### Claim at position 1

-20. (canceled).

### Claim 21

A method comprising:
generating, by a server computer, a session key based on a Master Key;
transmitting, by the server computer, the session key to a user device comprising a payment application, the payment application having a first state wherein the payment application is enabled to conduct a payment transaction, and a second state, different to the first state, wherein the user device generates an application cryptogram on the basis of the received session key, and provides the application cryptogram to a terminal after the terminal sends a cryptogram request to the user device;
receiving, by the server computer, from the terminal, the application cryptogram in an authorization request for a transaction;
verifying, by the server computer, the application cryptogram by identifying the session key using the identified session key to verify the application cryptogram; and
responsive verifying the cryptogram, transmitting, by the server computer to the terminal, an authorization response.

### Claim 22 (depends on 21)

The method of claim 21, wherein the server computer is an issuing bank server.

### Claim 23 (depends on 21)

The method of claim 21, wherein verifying the cryptogram also comprises determining if a time since the session key was sent to the user device by the server computer exceeds a threshold.

### Claim 24 (depends on 21)

The method of claim 21, wherein the user device if a mobile phone.

### Claim 25 (depends on 21)

The method of claim 21, wherein the Master Key is an ICC Master Key.

### Claim 26 (depends on 21)

The method of claim 21, wherein the terminal is a POS terminal.

### Claim 27

A server computer comprising:
a processor; and
a non-transitory computer readable medium, the non-transitory computer readable medium comprising code executable by the processor, for performing a method comprising:
generating a session key based on a Master Key;
transmitting the session key to a user device comprising a payment application, the payment application having a first state wherein the payment application is enabled to conduct a payment transaction, and a second state, different to the first state, wherein the user device generates an application cryptogram on the basis of the received session key, and provides the application cryptogram to a terminal after the terminal sends a cryptogram request to the user device;
receiving from the terminal, the application cryptogram in an authorization request for a transaction;
verifying the cryptogram by identifying the session key using the identified session key to verify the cryptogram; and
responsive verifying the cryptogram, transmitting to the terminal, an authorization response.

### Claim 28 (depends on 27)

The server computer of claim 27, wherein the server computer is an issuing bank server computer.

### Claim 29 (depends on 27)

The server computer of claim 27, wherein verifying the cryptogram also comprises determining if a time since the session key was sent to the user device by the server computer exceeds a threshold.

### Claim 30 (depends on 27)

The server computer of claim 27, wherein the application cryptogram is an ARQC.

### Claim 31 (depends on 27)

The server computer of claim 27, wherein the method comprises:
transmitting another session key derived from the Master Key after transmitting the authorization response.

### Claim 32

A method comprising:
generating, by a terminal in a transaction, a request for an application cryptogram;
transmitting, by the terminal to a user device, the request for the application cryptogram, wherein the user device comprises a payment application, the payment application having a first state wherein the payment application is enabled to conduct a payment transaction, and a second state, different to the first state, and wherein the payment application stores a session key generated using a Master Key;
receiving, by the terminal, the application cryptogram from the user device, the application cryptogram generated by the user device using the session key;
analyzing the application cryptogram to determine a cryptogram type; and
responsive to determining the cryptogram type, transmitting an authorization request comprising the application cryptogram to a server computer, wherein the server computer verifies the cryptogram by identifying the session key using the identified session key to verify the cryptogram.

### Claim 33 (depends on 32)

The method of claim 32, wherein the user device is a mobile phone.

### Claim 34 (depends on 32)

The method of claim 32, wherein the terminal is a POS terminal.

### Claim 35 (depends on 32)

The method of claim 32, therein the Master Key is an ICC Master Key.

### Claim 36 (depends on 32)

The method of claim 32, further comprising:
performing, by the terminal, a terminal action analysis, and then determining that that the transaction requires the application cryptogram.

### Claim 37 (depends on 32)

The method of claim 32, wherein the second state is that the payment application is inoperative.

### Claim 38 (depends on 32)

The method of claim 32, wherein the server computer verifies the cryptogram also by determining if a time since the session key was sent to the user device by the server computer exceeds a threshold.

### Claim 39 (depends on 32)

The method of claim 32, wherein the server computer is an issuing bank server.

### Claim 40 (depends on 32)

The method of claim 32, wherein the session key is usable to create only one application cryptogram for one transaction.
