IP Library Granted Patent US 11,640,596
Granted Patent B2
US 11,640,596 · App. 15/578,085 · Granted May 2, 2023

Terminal and method for mobile payment with trusted execution environment

Inventors: Udo Schwartz (Munich, DE); Kurt Stadler (Oberhaching, DE); Mihai Creanga (Haar, DE)
Assignee: GIESECKE+DEVRIENT MOBILE SECURITY GMBH
G06Q20/3226G06Q20/023G06Q20/326G06Q20/3223G06Q20/3229G06Q20/351G06Q20/352G06Q20/40975
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,640,596
App. No.
15/578,085
Granted
May 2, 2023
Kind
B2
Abstract

A mobile terminal is adapted for mobile payment through payment in accordance with transaction data from the customer to a merchant via a payment service provider, and is adapted for a clearing of the payment between bank servers. The terminal is characterized in that a) in the secure runtime environment access data are stored for an authentication between the payment trust application and the payment service provider; and b) the agent is further adapted b1) upon an authentication between the payment trust application and the payment service provider, to transmit access data, or authentication data generated employing access data, between the secure runtime environment and the payment service provider, and b2) to accept from the payment trust application a transaction instruction for a payment in accordance with the transaction data and to send it to the payment service provider. A corresponding mobile payment method for a terminal is likewise specified.

Claims (40)

1. A mobile terminal of a customer, adapted for mobile payment through a payment in accordance with transaction data from the customer to a merchant via a payment service provider, which is adapted to initiate a clearing of the payment between bank servers of the customer and the merchant,

wherein the mobile terminal comprises:

a normal runtime environment and a secure runtime environment;

an agent which is adapted to accept transaction data from a payment terminal;

an authorization interface implemented in the terminal, which is adapted to present transaction data accepted at the agent to the customer for authorization and to accept and forward an authorization input by the customer at the authorization interface;

a payment application implemented in the terminal, at least one secure portion of which, including a payment trust application, is implemented in the secure runtime environment and which is adapted to accept an authorization forwarded by the authorization interface and, in response to the accepted authorization, to generate and send a transaction instruction;

wherein

a) in the secure runtime environment access data are stored for an authentication between the payment trust application and the payment service provider; and

b) the agent is further adapted to:

b1) upon an authentication between the payment trust application and the payment service provider: to transmit access data or authentication data generated employing access data between the secure runtime environment and the payment service provider; and

b2) to accept from the payment trust application a transaction instruction for a payment in accordance with the transaction data and send to the payment service provider via a secure channel, bypassing interruption of the secure channel at the payment terminal such that no interruption of the secure channel occurs at the payment terminal.

2. The terminal according to claim 1 , wherein the agent is configured as a software emulation of a smart card, including an Android host-based card emulation HCE.

3. The terminal according to claim 1 , wherein the agent is configured as a trust application implemented in the secure runtime environment or integrated in such a trust application.

4. The terminal according to claim 1 , wherein the agent is configured as a payment trust application or integrated in the payment trust application.

5. The terminal according to claim 1 , wherein the access data include a channel key for setting up and operating the secure channel between the secure runtime environment and the payment service provider and the agent is adapted

according to b1) to set up the secure channel employing the channel key and

according to b2) to send the transaction instruction via the secure channel to the payment service provider.

6. The terminal according to claim 1 , wherein the access data include a signature generation key for generating a signature, wherein the transaction instruction can be generated by signing the transaction data by means of the signature generation key, wherein the corresponding signature verification key is stored at the payment service provider, and the agent is adapted

according to b1) and b2) to send a transaction instruction generated by signing the transaction data with the signature generation key to the payment service provider, so that the transaction data are verifiable for the payment service provider.

7. A mobile payment method for a terminal of a customer, adapted for mobile payment through payment in accordance with transaction data from the customer to a merchant via a payment service provider, which is adapted to initiate a clearing of the payment between bank servers of the customer and the merchant,

wherein the mobile terminal includes:

a normal runtime environment and a secure runtime environment;

an agent implemented in the terminal; an authorization interface implemented in the terminal;

and a payment application implemented in the terminal, at least one secure portion of which, including a payment trust application, is implemented in the secure runtime environment;

wherein in the method:

by the agent: transaction data are accepted from a payment terminal;

by the authorization interface: transaction data received at the agent are presented to the customer for authorization and an authorization input by the customer at the authorization interface is accepted and forwarded;

by the payment trust application: an authorization forwarded by the authorization interface is accepted and, in response to the accepted authorization, a transaction instruction is generated and sent;

wherein

a) between the payment trust application and the payment service provider an authentication is carried out employing the access data stored in the secure runtime environment; and

b) by the agent:

b1) upon authentication between the payment trust application and the payment service provider access data or authentication data generated employing access data are transmitted between the secure runtime environment and the payment service provider; and

b2) the transaction instruction sent by the payment trust application is accepted and sent to the payment service provider via a secure channel, bypassing interruption of the secure channel at the payment terminal such that no interruption of the secure channel occurs at the payment terminal.

8. The payment method according to claim 7 , wherein the access data include at least one channel key for setting up and operating the secure channel between the payment trust application and the payment service provider, and wherein the agent

in step b1) establishes the secure channel employing the channel key and

in step b2) sends the transaction instruction via the secure channel to the payment service provider.

9. The payment method according to claim 8 , wherein the agent in step b1) establishes the secure channel directly to the payment service provider.

10. The payment method according to claim 8 , wherein the agent establishes the secure channel to the payment service provider via an NFC payment terminal which does not have the access data, and merely passes on the transaction instruction.

11. The payment method according to claim 7 , wherein the access data include a signature generation key for generating a signature for the verification of the transaction data, wherein the corresponding signature verification key is stored at the payment service provider, and wherein the transaction instruction is generated by the payment trust application, wherein the transaction data are signed with the signature generation key;

and wherein the agent, according to b1) and b2), sends the generated transaction instruction to the payment service provider, so that the transaction data are verifiable for the payment service provider with the signature verification key.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 29, 2017
From: SCHWARTZ, UDO; STADLER, KURT; CREANGA, MIHAI
To: GIESECKE+DEVRIENT MOBILE SECURITY GMBH
Reel/Frame 044252/0019 →
Priority Claims (1)
DE 10 2015 006 907.1 · May 29, 2015 · national
Continuity (1)
Related Publication 20180150826A1 · May 31, 2018