Electronic transaction process and computer system

The described method addresses the need for secure and user-friendly electronic transactions by using an ID token and ID provider system authentication with end-to-end encryption, facilitating seamless transactions in eCommerce and eGovernment applications.

DE102013022444B4Active Publication Date: 2024-11-14BUNDESDRUCKEREI GMBH

Patent Information

Application Number
DE102013022444
Authority / Receiving Office
DE · DE
Patent Type
Patents
Current Assignee / Owner
Filing Date
2013-06-28
Publication Date
2024-11-14
Estimated Expiration
2033-06-28

AI Technical Summary

Technical Problem

Existing electronic transaction processes lack a secure, flexible, and user-friendly method for eCommerce and eGovernment applications that ensures the confidentiality and integrity of user data while facilitating seamless transactions.

Method used

A computer-implemented payment method utilizing an ID token for user authentication and an ID provider computer system authentication, combined with end-to-end encryption and secure session management, to facilitate transactions through a terminal, user computer system, and service computer system.

Benefits of technology

Enables secure, flexible, and user-friendly transactions by ensuring data confidentiality and integrity, allowing for universal application in eCommerce and eGovernment scenarios.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 00000000_0000_ABST
    Figure 00000000_0000_ABST
Patent Text Reader

Abstract

Electronic transaction procedure using an ID token (106) assigned to a user (102), wherein the ID token has an electronic memory (118) with a protected memory area (124) in which one or more attributes are stored, wherein access to the protected memory area is only possible via a processor (128) of the ID token, and wherein the ID token has a communication interface (108) for communication with a reader of a user computer system (100), comprising the following steps: - Display of an optically readable pattern on a screen (188) of a terminal (186), wherein the optically readable pattern contains encoded information which includes at least a logical address of a service computer system (150) and transaction data, - Detection of the pattern using an optical sensor (190) of the user computer system and decoding of the pattern by the user computer system, - Transmission of a transaction request (158) from the user computer system to the logical address of the service computer system over the network, wherein the transaction request includes the transaction data, - Transmission of a request (166) from the service computer system via the user computer system (100) to an ID provider computer system (136), wherein the transmission takes place over the network, wherein the request includes an attribute specification of the attributes to be read from the ID token for the execution of the transaction, - User authentication against the ID token, - Authentication of the ID provider computer system to the ID token over the network, - provided that the user and the ID provider computer system are successfully authenticated to the ID token, the ID provider computer system reads the attribute(s) from the ID token according to the attribute specification over the network with end-to-end encryption, - Transmission of a response (174) from the ID provider computer system via the user computer system to the service computer system, wherein the transmission of the response takes place over the network, wherein the response includes the read attribute(s), and wherein the response is signed by the ID provider computer system, execution of the transaction using the transaction data and the attribute(s) by the service computer system, wherein the terminal is a mobile electronic device, in particular a smartphone, wherein the optically readable pattern includes an account connection of the smartphone owner, wherein the service computer system initiates the financial transaction to transfer the payment amount to the account of the smartphone owner, whereupon the service computer system transmits a confirmation signal to the smartphone, which is output by the smartphone via a user interface,to inform the smartphone owner of the payment.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] The invention relates to an electronic transaction method and a computer system.

[0002] Various transaction methods are used in electronic commerce, also known as eCommerce. These include traditional payment methods such as paper-based bank transfers or cash on delivery, as well as electronic payment methods such as credit card payments, online banking, collection / billing systems, factory systems, direct debit, prepaid methods, payment via telephone bill, and mobile payment systems. Some of these payment methods are also used for eGovernment applications.

[0003] In contrast, the invention is based on the objective of creating an improved electronic transaction method and a corresponding computer system.

[0004] The problem underlying the invention is fulfilled by the features of the independent claims. Embodiments of the invention are specified in the dependent claims.

[0005] The following are known from the prior art: an information processing device with an optical data reader, a server, and a method for electronic commerce (US 2003 / 0120555 A1), a technical guideline on a server for simplifying electronic identity verification in web applications (BSI TR-03130, Technical Guideline eID Server, Federal Office for Information Security, Ver. 1.6, 20.04.2012), and a technical guideline on an API framework for providing an interface that enables the standardized use of smart cards (Technical Guideline TR-03112-7 eCard API Framework - Protocols, Federal Office for Information Security, Ver. 1.1.2, 28.02.2012).

[0006] The German Federal Office for Information Security's technical guideline TR-03110, version 2.05, describes enhanced security mechanisms for machine-readable travel documents. Publication US 2012 / 0290415 A1 discloses a mobile payment system in which merchant data is encoded in scannable images.

[0007] In this context, a "transaction" refers to a financial transaction, such as the payment of an amount by making a bank transfer, direct debit or credit card charge, an order process for ordering and delivering a physical good or data, as well as other logistical, commercial and / or financial transactions and / or a database transaction, e.g. for storing a value, such as a consumption value, a credit balance or a payment amount.

[0008] In this context, a "terminal" is understood to be a device that has a display, i.e., a screen, for showing an optical pattern. The terminal can simply acquire information and output it via the display, or it can have a user interface for inputting a user selection.

[0009] For example, the terminal can be configured as an ATM or vending machine. The user can enter a request into the terminal, such as withdrawing cash, topping up a debit card, or purchasing a specific product, like a beverage. In response to this user request, the machine displays an optically recognizable pattern, such as a QR code, on its screen. This pattern contains information to initiate the transaction, such as the desired withdrawal amount or the purchase price of the product.

[0010] According to the invention, the terminal is designed as a smartphone with a fee collection function.

[0011] Here, a "pattern" is understood to be a static optical pattern displayed on the terminal's screen, in which information is encoded, for example, a barcode, in particular a one-dimensional, two-dimensional, high-capacity color barcode, MaxiCode, QR code, or DataMatrix code, or a temporal sequence of several patterns, where information is encoded through the patterns and their temporal sequence, as is the case, for example, with a flicker code. The "flicker code" is known for the so-called chipTAN-comfort or Smart-TAN-optic online banking procedures of savings banks and cooperative banks, respectively.

[0012] Here, a "session" refers to a temporary communication connection, i.e., a so-called communication session, which, according to the OSI model, can refer to the transport layer or the application layer. Specifically, a session can be an HTTP session or an HTTPS session, the latter using symmetric encryption to protect the transport layer.

[0013] In this context, an "ID token" is understood to be, in particular, a portable electronic device that has at least one data storage device for storing at least one attribute and a communication interface for reading the attribute. Preferably, the ID token has a secure storage area for storing the at least one attribute in order to prevent the attribute stored in the storage area from being modified in an unauthorized manner or read without the necessary authorization.

[0014] In particular, the ID token can be a USB stick or a document, especially a document of value or security. According to the invention, a "document" is understood to be a paper-based and / or plastic-based document, in particular electronic official documents, such as electronic identification documents, especially passports, identity cards, visas, as well as driver's licenses, vehicle registration documents, vehicle titles, company ID cards, health insurance cards or other ID documents, as well as chip cards, means of payment, especially banknotes, bank cards and credit cards, waybills or other proofs of authorization, such as an admission ticket, into which a data storage device for storing at least one attribute is integrated.

[0015] The ID token can be a hardware token or a soft token if it is cryptographically bound to a hardware token, for example a so-called Secure Element.

[0016] In particular, such a soft token cryptographically bound to a Secure Element can be generated in accordance with DE 10 2011 082 101.

[0017] An "ID provider computer system" is understood here to be a computer system that is designed to read at least one attribute from a user's ID token. Preferably, the ID provider computer system is operated in a so-called trust center to ensure the highest possible level of security.

[0018] In this context, a "service computer system" is understood to be a computer system that has a network interface for connecting to the network, allowing access to web pages stored or generated by the service computer system using an internet browser or other application program. In particular, the service computer system may be an internet server providing an e-commerce or e-government application, especially an online shop or a government server.

[0019] A "user computer system" is understood here to be a computer system to which the user has access. This could be, for example, a personal computer (PC), a tablet PC, or a mobile device, especially a smartphone, with a standard internet browser such as Microsoft® Internet Explorer, Safari®, Google Chrome®, Firefox®, or another application program for accessing the service computer system. The user computer system has an interface for connecting to the network, which can be a private or public network, especially the internet.

[0020] According to one embodiment of the invention, the request to the service computer system is a SAML request and the response to this by the ID provider computer system is a SAML response (see Security Assertion Markup Language (SAML) V2.0 Technical Overview, OASIS, Committee Draft 02, March 25, 2008).

[0021] According to one embodiment of the invention, the ID provider computer system has a certificate in which the read rights for carrying out the read access are specified.

[0022] Here, "certificate" refers to a digital certificate, also known as a public-key certificate. A certificate consists of structured data used to associate a public key of an asymmetric cryptosystem with an identity, such as a person or a device. For example, the certificate may conform to the X.509 standard or another standard. Preferably, the certificate is a Card Verifiable Certificate (CVC).

[0023] The certificate can specify which user attribute(s) stored in the protected memory area of ​​the ID token the ID provider's computer system is authorized to read. These attributes can be personal user attributes, such as name, address, and age. These attributes, in combination, can be used as user identification to access the registered user's payment information. Alternatively or additionally, a pseudonym of the user, which is stored at least temporarily by the ID token, can also be used as user identification.

[0024] Embodiments of the invention are particularly advantageous because they create a universally applicable, computer-implemented payment method suitable for e-commerce and e-government applications, which is simultaneously flexible, user-friendly, and secure. This is made possible in particular by the fact that the payment method is based on an ID token, whereby the execution of a payment transaction requires both the authentication of the user to the ID token and the authentication of the ID provider's computer system to the ID token.

[0025] In one example, the terminal is a device, for example for paying out cash, for topping up a debit card, for selling a product such as a ticket, an admission ticket, or a food or beverage.

[0026] For example, the terminal could be an ATM. In this case, the user enters a desired withdrawal amount via the ATM's user interface. This withdrawal amount is then displayed by the ATM as an optically readable pattern on its screen, and this pattern is captured by the user using an optical sensor, such as the camera of the user's computer system, which could be a smartphone. The pattern displayed on the screen can also contain a logical address of the service computer system, such as a URL. Furthermore, the pattern can contain additional information, such as the account information of the ATM operator.

[0027] The user's computer system decodes the pattern captured by the terminal's screen using the optical sensor and then generates a transaction request specifying the payout amount and any other transaction data contained in the pattern. This transaction request is then transmitted from the user's computer system to the service computer system over the network.

[0028] The service computer system then generates a request containing an attribute specification. This specification includes at least one attribute to be read from the ID token, which is required for the transaction to be carried out and / or which must meet a predefined verification criterion for the transaction to be processed. For example, the attribute could be the user's bank account details stored in the ID token, or a user pseudonym that serves as an access key for the service computer system to pseudonymized account information of registered users stored in a database. Alternatively or additionally, the attribute could be an age indication to verify whether the user has the legal capacity required to complete the transaction.

[0029] The service computer system then sends the request to the ID provider computer system. After authentication of the user against their ID token and after authentication of the ID provider computer system against the ID token via the network, the ID provider computer system then reads at least one attribute from the ID token via the network with end-to-end encryption.

[0030] The ID provider computer system then generates a response containing at least one attribute read from the ID token. The attributes and / or the response are signed by the ID provider computer system and sent to the service computer system.

[0031] The service computer system then uses the attributes to carry out the transaction, for example, debiting the user's account with the payout amount, and / or to check whether a predefined criterion, e.g., legal capacity, is met.

[0032] Once the account has been debited, the service computer system generates a confirmation signal, which is transmitted to the bank terminal. For example, the terminal, i.e., the ATM, is connected to the network so that the confirmation signal is transmitted from the service computer system to the terminal via the network. Preferably, the confirmation signal is digitally signed by the service computer system to prevent manipulation. Upon receipt of a valid confirmation signal, the cash is then dispensed in the requested amount, or alternatively, the user's debit card is topped up.

[0033] According to the invention, the terminal is a third party's smartphone, which the third party uses to sell a product to the user. The smartphone has an app that the third party launches. The third party enters the purchase price and, for example, their bank details into the app. This information, along with the logical address of the service computer system, is then displayed on the smartphone's screen as an optical pattern.

[0034] The corresponding transaction request then includes the purchase price and the third party's bank account details. The attribute specification in this case can, for example, relate to the user's personal information, which the service computer system uses to access the user's previously registered bank account. Upon receiving the response, the service computer system then executes the transaction—that is, the payment of the purchase price—using the account information of both the third party and the user. The service computer system then sends a confirmation signal to the third party's smartphone, informing them of the successful payment and enabling them to deliver the product to the user.

[0035] Instead of a smartphone, this can also be implemented in another mobile electronic device, such as a laptop or notebook computer, or in a stationary electronic system, such as the electronic cash register system of a supermarket.

[0036] It is particularly advantageous if the terminal has a network interface for communication over the network. In this case, the acknowledgment signal can be transmitted over the network. Another possibility is that the acknowledgment signal is sent from the service computer system to the user computer system. The user computer system can then display an optical pattern on its screen, in which this acknowledgment is encoded. This optical pattern can then be detected by the terminal, which also has an optical sensor. This embodiment has the advantage that the terminal does not need to be connected to the network, which offers security benefits.

[0037] According to a further embodiment of the invention, the service computer system is connected to the terminal via a communication channel different from the network, such as an internal company network or a Virtual Private Network, through which the confirmation signal is transmitted from the service computer system to the terminal.

[0038] According to embodiments of the invention, a first session is established between the internet browser of the user's computer system and the service computer system via the internet. This first session can be either an HTTP session or an HTTPS session. The user can enter a transaction request into the internet browser, for example, to initiate a payment transaction. For instance, the user has previously ordered goods via the service computer system and wishes to pay for these goods. To do this, the user enters the corresponding transaction request into the internet browser, which is then transmitted to the service computer system via the first session.

[0039] The service computer system then generates a request, i.e., a request in a request-response protocol. The request can have a predefined or standardized structure. For example, the request can be text-based, have an XML, ASN.1, or binary structure, or be formatted as a SAML request. The request, such as the SAML request, includes an attribute specification that defines the attributes to be read from the ID token to execute the transaction. These attributes can identify the user associated with the ID token and / or provide payment information, such as bank account or credit card details, and / or relate to the ID token itself, such as its expiration date, issue date, and / or the issuing organization or authority.

[0040] According to embodiments of the invention, the request is transmitted from the service computer system via the user computer system to the ID provider computer system. Upon receipt of the request by the user computer system, the subsequent process for generating the response, including the authentication of the user and the ID provider computer system, is triggered.

[0041] In particular, the attribute specification can include the user's date of birth, for example, if the service computer system needs to verify the user's legal age as a prerequisite for carrying out the transaction. The request also includes transaction data to specify the transaction, such as a payment amount and account information, especially the service computer system's bank account details to which the payment is to be made. Furthermore, the request includes a Uniform Resource Locator (URL) of the ID provider computer system, which is to read the attributes from the ID token, as well as a URL of the service computer system to specify a recipient for the response that the ID provider computer system is to generate based on the request.

[0042] The service computer system generates an identifier for the request that uniquely identifies it, such as a globally unique identifier (GUID). The request includes this identifier.

[0043] The request is signed by the service computer system using a private key from a cryptographic key pair assigned to the service computer system.

[0044] Due to the transaction request, a web page is transmitted from the service computer system to the user computer system during the first session and displayed by the internet browser or application program, in particular an app. The request itself is transmitted along with the web page, but is not displayed.

[0045] The website has at least one input field for entering additional information required to complete the transaction. This additional information could be, for example, the user's bank account or credit card information, and / or authentication information to verify the user's identity with the service computer system. For example, the authentication information could be a one-time password (OTP). Preferably, the additional information is encrypted by the user's computer system using the public key of the service computer system, so that only the encrypted additional information is subsequently transmitted via the network from the internet browser or application program to the ID provider computer system in a second session.

[0046] The request is also forwarded via this second session. The second session is established by calling the URL of the ID provider's computer system, which is included in the request. This second session is established as a secure communication connection using an encrypted transport layer, specifically Transport Layer Security (TLS), also known as Secure Sockets Layer (SSL), and in particular as an HTTPS session.

[0047] According to embodiments of the invention, the ID provider computer system generates an identifier for a third session yet to be established, i.e., a so-called session ID, based on the receipt of the request via the second session. The ID provider computer system stores the request and the additional information received along with the request via the second session, together with the session ID for the third session.

[0048] The ID provider computer system then sends a message about the second session, which includes a logical address of the ID provider computer system and, for example, the session ID of the third session. The web browser or application program can later retrieve the response to the previously forwarded request from this logical address. The logical address can be a uniform resource locator (URL) through which the response can be retrieved.

[0049] The third session is then established at the application layer between a program on the user's computer system and the ID provider's computer system, using the secure transport layer of the second session. This program could be, for example, a browser plug-in for the internet browser or an application program separate from the internet browser.

[0050] The ID provider computer system then transmits the information required to read the attribute(s) from the ID token to the program during the third session. This information includes at least a certificate from the ID provider computer system, which specifies the ID provider computer system's read permissions to access one or more attributes.

[0051] The user's computer system then checks whether the read permissions specified in the certificate are sufficient to allow the ID provider's computer system to read the attribute(s) to be read according to the request's attribute specification. If the ID provider's computer system has sufficient read permissions, the following steps are performed: a) A local connection is established between the user's computer system's reader and the ID token. For an ID token with a contact-based interface, such as a chip card interface, this can be done by inserting the ID token into the reader. For an ID token with a contactless interface, such as RFID or NFC, this can be done by placing the ID token on the reader. Tokens with USB, Bluetooth, or microSD cards, as well as virtual smart cards, are also possible. b) The user authenticates themselves to the ID token, for example by entering their Personal Identification Number (PIN) or by entering other information, such as capturing a biometric characteristic of the user. During user authentication to the ID token, a session key is agreed upon. In particular, the agreement of a session key can be done using a Diffie-Hellman protocol. c) Subsequently, a fourth session is established on the application layer between a program of the ID token and the ID provider computer system, whereby this fourth session runs over the local connection and the third session and additional end-to-end encryption is carried out on the application layer using the session key agreed in step b. d) The fourth session then involves mutual authentication of the ID token and the ID provider computer system, for example using a challenge-response protocol. e) The attribute(s) according to the attribute specification, which the ID provider computer system received with the request, are now read from the ID token by the ID provider computer system via the fourth session. This requires the successful authentication of the user in step b) and the successful mutual authentication of the ID token and the ID provider computer system in step d), and is encrypted via the fourth session, thus ensuring maximum security and trustworthiness with regard to the read attribute(s).

[0052] The ID provider computer system then generates a response containing the retrieved attribute(s), the request identifier, and / or additional information, according to the request-response protocol to which the request is subject. For example, a SAML request generates a corresponding SAML response. The request identifier, which is also included in the response, establishes the logical association between the request and response, i.e., the binding.

[0053] The response is signed by the ID provider computer system and stored for retrieval from the logical address previously communicated to the user computer system via the message.

[0054] The user's computer system then reads this response from the ID provider's computer system using the logical address, for example, the URL, and forwards the response to the service computer system via the first session. Using the response's identifier, it is assigned to the request and thus to the requested transaction. The service computer system then executes the transaction, meaning the payment process is initiated, if the response's content allows it.

[0055] According to one embodiment of the invention, the user computer system program is a browser plug-in for the internet browser, wherein the internet browser can be a standard browser program such as Microsoft Internet Explorer®, Safari®, Google Chrome®, or Firefox®. Alternatively, the user computer system program can be a separate application program from the internet browser.

[0056] According to one embodiment of the invention, the additional information entered by the user is payment information, such as the user's bank account details from which the payment amount specified in the request is to be debited or collected.

[0057] The so-called clearing process, meaning the verification of the customer's creditworthiness and the initiation of the payment transaction, can then be handled by the ID provider's computer system, which confirms the payment to the service provider's computer system via a response. This has the advantage that the service provider's computer system does not need to obtain any information regarding the user's payment details, particularly their bank account information.

[0058] Alternatively, the user can encrypt their payment information with the public key of the service computer system, so that only the encrypted payment information is transmitted to the ID provider computer system. The ID provider computer system then forwards the encrypted payment information along with the response to the service computer system, which decrypts the payment information, clears the payment, and collects the payment amount from the user's account according to the payment information. This has the advantage that the ID provider computer system does not gain access to the user's payment information.

[0059] According to a further embodiment of the invention, the computer system includes a terminal, which, according to the invention, is designed as a smartphone with a fee recording function. For example, the URL of the service computer system, the payment amount, and the payee can be displayed on a seller's smartphone in the form of an optically captured pattern and recorded with the camera of the user's computer system, which can also be designed as a smartphone. In this way, everyday payment transactions can be processed securely and conveniently.

[0060] In the following, embodiments of the invention will be explained in more detail with reference to the drawings.

[0061] They show: Fig. 1. A block diagram of an ID token, Fig. 2 an arrangement of a computer system for carrying out a method according to the invention.

[0062] Elements of the following figures that are identical or correspond to each other are each marked with the same reference symbols.

[0063] The Fig. Figure 1 shows an ID token 106, which could be, for example, an electronic identity card.

[0064] The protected memory area 120 of the ID token 106 serves to store a reference value required for authenticating a user 102 to the ID token 106. This reference value is, for example, an identifier, in particular a so-called Personal Identification Number (PIN), or reference data for a biometric characteristic of the user 102, which can be used to authenticate the user to the ID token 106.

[0065] The protected area 122 is used to store a private key, and the protected storage area 124 is used to store attributes, for example, of the user 102, such as their name, place of residence, date of birth, gender, and / or attributes relating to the ID token itself, such as the institution that created or issued the ID token, the validity period of the ID token, an identifier of the ID token, such as a passport number or a credit card number.

[0066] The electronic storage device 118 may also include a storage area 126 for storing a certificate. The certificate contains a public key that is associated with the private key stored in the protected storage area 122. The certificate may have been created according to a Public Key Infrastructure (PKI) standard, for example, the X.509 standard.

[0067] The certificate does not necessarily have to be stored in the electronic storage location 118 of the ID token 106. Alternatively or additionally, the certificate can also be stored in a public directory server.

[0068] The ID token 106 has a processor 128. The processor 128 is used to execute program instructions 130, 132, and 134. The program instructions 130 are used for user authentication, i.e., to authenticate the user 102 to the ID token.

[0069] When using a PIN, user 102 enters their PIN into the ID token 106 for authentication, for example, via the user's computer system 100. By executing the program instructions 130, the protected memory area 120 is then accessed to compare the entered PIN with the PIN reference value stored there. If the entered PIN matches the PIN reference value, user 102 is considered authenticated.

[0070] Alternatively, a biometric characteristic of user 102 is recorded. For example, the ID token 106 has a fingerprint sensor for this purpose, or a fingerprint sensor is connected to the user's computer system 100. The biometric data recorded from user 102 is compared with the biometric reference data stored in the protected memory area 120 by executing the program instructions 130. If the biometric data recorded from user 102 matches the biometric reference data sufficiently, user 102 is considered authenticated.

[0071] The program instructions 134 serve to execute the steps of a cryptographic protocol relating to the ID token 106 for authenticating an ID provider computer system 136 to the ID token 106. The cryptographic protocol can be a challenge-response protocol based on a symmetric key or an asymmetric key pair.

[0072] For example, the cryptographic protocol implements an Extended Access Control (EAC) procedure as specified by the International Civil Aviation Organization (ICAO) for machine-readable travel documents (MRTDs). Successful execution of the cryptographic protocol authenticates the ID provider computer system 136 to the ID token, thereby proving its read authorization to access the attributes stored in the protected memory area 124. Authentication can also be reciprocal, meaning the ID token 106 must also authenticate itself to the ID provider computer system 136 using the same or a different cryptographic protocol.

[0073] The program instructions 132 are used for end-to-end encryption between the ID token 106 and an ID provider computer system 136 (see Fig. 2) transmitted data, or at least the attributes read from the protected memory area 124 by the ID provider computer system 136. A symmetric key can be used for end-to-end encryption, which is agreed upon, for example, during the execution of the cryptographic protocol between the ID token 106 and the ID provider computer system 136.

[0074] The ID token 106 has an interface 108 for communication with a corresponding interface 104 of a user computer system 100 (compare Fig. 2) The interface can be contactless or contact-based. In particular, it can be an RFID or NFC communication interface.

[0075] Access to the protected memory area 124 for reading one or more of the attributes can only be achieved via processor 128 of the ID token 106, since protected memory area 124, as well as the other protected memory areas 120 and 122, are not directly connected to interface 108 via a bus system, but only to processor 128. This means that direct access to protected memory area 124 via interface 108 is inherently impossible due to the circuit design. Therefore, only processor 128 can access protected memory area 124 for reading, and then, if necessary, output the read attributes via interface 108.

[0076] The Fig. Figure 2 shows a user computer system 100 of user 102. The user computer system 100 can be a personal computer (PC), a portable computer such as a laptop, notebook or tablet computer, a mobile telecommunications device, in particular a smartphone.

[0077] The user computer system has at least one processor 110 for executing an application program 112. The application program 112 is configured to communicate via a network interface 114 of the user computer system 100 over a network 116. For example, the application program is an internet browser or another specialized application program that can communicate over the network 116, in particular an HTML-capable application program.

[0078] The processor 110 is used to execute another program 113, which may be, for example, a plug-in for the application program 112, such as a browser plug-in if the application program 112 is designed as an internet browser, or a program separate from the application program.

[0079] The network in question can be a computer network, such as the internet. Specifically, network 116 can also include a mobile network.

[0080] The ID provider computer system 136 has a network interface 138 for communication over the network 116. The ID provider computer system 136 also has a memory 140 with a protected memory area 141 in which a private key 142 of the ID provider computer system 136 is stored, as well as the corresponding certificate 144. This certificate can also be, for example, a certificate based on a PKI standard, such as X.509.

[0081] The ID provider computer system 136 also has at least one processor 145 for executing program instructions 146 and 148. The execution of program instructions 146 carries out the steps of the cryptographic protocol pertaining to the ID provider computer system 136. In total, the cryptographic protocol is implemented by executing program instructions 134 by processor 128 of the ID token 106 and by executing program instructions 146 by processor 145 of the ID provider computer system 136.

[0082] The program instructions 148 serve to implement end-to-end encryption on the ID provider computer system 136, for example, based on the symmetric key agreed upon between the ID token 106 and the ID provider computer system 136 during the execution of the cryptographic protocol. In principle, any known method for agreeing on the symmetric key for end-to-end encryption can be used, such as a Diffie-Hellman key exchange.

[0083] The ID provider computer system 136 is preferably located in a particularly protected environment, especially in a so-called trust center, so that the ID provider computer system 136, in combination with the need to authenticate the user 102 to the ID token 106, forms the anchor of trust for the authenticity of the attributes read from the ID token 106.

[0084] A service computer system 150 can be configured to receive an order or commission for a service or product, particularly an online service. For example, the user 102 can open an account with a bank online via the network 116 or access other financial or banking services. The service computer system 150 can also be configured as an online store, allowing the user 102 to purchase a mobile phone or similar item online. Furthermore, the service computer system 150 can also be configured to deliver digital content, such as downloading music and / or video data.

[0085] The service computer system 150 has a network interface 152 for connecting to the network 116. Furthermore, the service computer system 150 has at least one processor 154 for executing program instructions 156. By executing the program instructions 156, dynamic HTML pages are generated, for example, through which the user 102 can enter their order or request, and transactions are carried out.

[0086] Depending on the type of product or service requested or ordered, the service computer system 150 must verify one or more attributes of the user 102 and / or their ID token 106 against one or more predefined criteria. Only if this verification is passed will the order or request from the user 102 be accepted and / or processed.

[0087] To carry out an electronic transaction, the following procedure can be used: User 102 starts the application program 112 of the user's computer system, which, for the sake of simplicity, will be assumed to be an internet browser. User 102 enters a URL of the service computer system 150 into the internet browser, thereby establishing an initial session 201 between the internet browser 112 and the service computer system 150 via the network 116. The user can then use this initial session 201 to request a service offered by the service computer system 150, such as ordering a product, requesting data for download, or initiating a financial transaction. For this purpose, the internet browser 112 sends a corresponding transaction request 158 ​​to the service computer system 150, signaling this request. - The service computer system therefore receives a transaction request 158 ​​from user 102 via the internet browser during the first session. - Upon receiving transaction request 158 ​​via the first session 201, the service computer system 150 generates a request 166. Request 166 contains (i) an attribute specification of the attributes to be read from the ID token for the execution of the transaction. These attributes may include personal information about user 102 and / or data relating to the ID token 106 itself, or a pseudonym of user 102 available from the ID token 106. The request also contains (ii) the transaction data to specify the transaction, such as a payment amount to be made to the service computer system 150 or a third party for the purchase of the ordered product or the execution of the ordered service, and / or other transaction data that specify the transaction to be carried out.The request further includes (iii) an identifier 180 of the request, for example, a GUID, which is required for the so-called binding of the request and a subsequently received response 174. The service computer system 150 may have a GUID generator for generating the identifier. The request further includes (iv) a URL of the ID provider computer system 136 and (v) a URL of the service computer system 150 itself. The request is signed by the service computer system 150 using a private key of the service computer system 150. The request 166 may be a SAML request or another request of a request-response protocol. In response to transaction request 158, the service computer system 150 sends a web page 160 via the first session 201 to the user computer system 100. Web page 160 includes an input field 162 for user 102 to enter additional information for the transaction, and an input element 164 that user 102 can select, for example by clicking on it, when web page 160 is displayed by the internet browser 112, in order to allow the forwarding of request 166. Along with web page 160, request 166 is also transmitted via the first session 201 to the internet browser 112. - Upon receiving webpage 160 and request 166, webpage 160 is rendered by internet browser 112, allowing user 102 to enter the additional information into input field 162. This additional information might include, for example, user 102's bank account details, credit card number, or other supplementary transaction data, and / or authentication information to verify user 102's authorization to carry out the transaction. For this purpose, user 102 might enter a one-time password (OTP) into input field 162. Preferably, the additional information 168 entered by user 102 is encrypted by user computer system 100 using the public key of the service computer system 150 to obtain a corresponding ciphertext. - Subsequently, a second session 202 is established between the internet browser 112 and the ID provider computer system 136 via the network 116, using the URL of the ID provider computer system 136, which the user computer system 100 received with request 166. The second session 202 is established using a secure transport layer, for example, as an https session. - Via the second session 202, the request 166 and the additional information 168, or only the ciphertext of the additional information 168 obtained with the help of the public key of the service computer system 150, are forwarded from the user computer system 100 to the ID provider computer system 136. - Upon receiving request 166, the ID provider computer system 136 generates a session ID for a third session 203 yet to be established by executing its program instructions 170. Request 166 and the additional information 168 are stored in the memory 140 of the ID provider computer system 136. The ID provider computer system 136 then generates a message 172 containing the session ID for establishing the third session 203 and a logical address. Using this logical address, the response 174 generated by the ID provider computer system 136 in response to request 166 can be retrieved. Specifically, the logical address can be in the form of a URL. The message 172 is sent by the ID provider computer system 136 to the internet browser 112 via the second session 202. Due to the receipt of message 172, the third session 203 is established between program 113 of the user computer system 100 and the ID provider computer system 136 via the secure transport layer of the second session 202. For example, program 113 could be a browser plug-in for the internet browser 112. Alternatively, program 113 could also be another application program. It is also possible to implement the functionalities of the internet browser 112 and those of program 113 in a single program. - During the third session 203, at least certificate 144 is then transferred to program 113. - Program 113 then checks whether the read permissions specified in certificate 144 are sufficient to allow the ID provider computer system 136 to read the attribute(s) to be read according to the attribute specification included in request 166. Only if these read permissions are sufficient are the following steps carried out: a) A local connection 176 is established between interfaces 104 and 108. For example, a prompt appears on the screen of the user computer system 100 for the user 102 to insert the ID token 106 into a reader of the user computer system 100, which has interface 104, or to place the ID token 106 on a contactless interface 104. b) User 102 then authenticates themselves to the ID token, for example, by entering their PIN into the user's computer system 100 or its reader. User authentication can be performed using a cryptographic protocol, such as a challenge-response protocol or a Diffie-Helman key exchange, whereby a session key is agreed upon during user authentication. c) Assuming successful user authentication, a fourth session 204 is established between the ID token 106 and the ID provider computer system 136, via the local connection 176 and the third session 203. The fourth session 204 is protected with end-to-end encryption using the session key agreed upon during user authentication in step b). d) During the fourth session, mutual authentication of the ID token 106 and the ID provider computer system 136 takes place using their respective private keys, that is, the private key of the ID token 106 stored in the protected memory area 122 and the private key 142 of the ID provider computer system 136. For this mutual authentication, the certificates of the ID token 106 from memory area 126 (compare Fig. 1) and the certificate 144 of the ID provider computer system 136 will be exchanged via the fourth session. e) Provided that the user is successfully authenticated to the ID token and that the ID token 106 and the ID provider computer system 136 are successfully mutually authenticated, the ID provider computer system 136 then reads the attribute(s) from the ID token 106 according to the attribute specification. The attributes are protected by end-to-end encryption during transmission from the ID token 106 to the ID provider computer system 136. For this purpose, the ID provider computer system sends a read command to the ID token 106 via the fourth session 204. The read command 182 contains the attribute specification, i.e., the selection of the attributes to be read from the protected memory area 124 of the ID token 106. By executing the program instructions 178, the ID provider computer system 136 then generates the response 174, for example a SAML response, on the request 166.Response 178 contains the attributes previously read from ID token 106 via the fourth session 240, the additional information 168, or alternatively, not the additional information 168 but only its ciphertext, as well as the identifier 180, which the service computer system 150 initially assigned to request 166. Response 174 is signed by the ID provider computer system 136 using the private key 142 and then stored in memory 140, so that request 166 can be retrieved from the logical address. - The user computer system 100, such as its internet browser 112, then reads the response 174, for example via the second session 202, from memory 140 using the logical address. Response 174 is then forwarded from the user's computer system 100, for example, the internet browser 112, via the first session 201 to the service computer system 150. It may be stipulated that the user 102 is prompted by the internet browser 112 to enter confirmation before the response 174 is forwarded to the service computer system. Furthermore, it may be stipulated that the internet browser displays all or part of the content of response 174, in particular the attributes read from the ID token and / or the additional information 168, so that the user 102 can verify the accuracy of this data before it is forwarded to the service computer system 150 for the execution of the transaction. - The service computer system 150 assigns the received response 174 to the request 166 based on the matching identifiers 180 of the request 166 and the response 174. The service computer system 150 then checks the signature of response 166 and reads the required attribute(s) from response 174. Based on these attributes, it is then checked whether the requested transaction can be carried out by comparing the attribute(s) with one or more predefined criteria. These criteria could be, for example, the age or creditworthiness of user 102. The attribute could also be a pseudonym of user 102, which the service computer system 150 then uses to retrieve an attribute of user 102 stored in a database of the service computer system 150, such as a delivery address. The verification criterion here is whether a user with the pseudonym contained in response 174 is registered with the service computer system 150. If the check by the service computer system 150 shows that the transaction is feasible, the transaction is carried out using the transaction data and the additional information 168.

[0088] For example, program 113 is a browser plug-in registered in the registry of the user's computer system's operating system with a plug-in identifier. This operating system could be, for example, Windows, Android, or iOS. In this case, message 172 from the ID provider's computer system to the internet browser 112 contains this plug-in identifier 184, so that plug-in 113 is started upon receipt of the message.

[0089] In another example, program 113 is a separate application program from internet browser 112, such as a citizen app or ID card app. This application program 113 is started by internet browser 112 by calling a local URL, where the local URL includes a fixed port number according to the TCP protocol. This local URL, along with the web page 160, is transmitted from the service computer system 150 to the user computer system 100 via the first session 201, in order to trigger the start of application program 113 by internet browser 112 using the local URL.

[0090] If only the ciphertext of the additional information 168, but not the additional information 168 itself, is transmitted via the second session 202 from the user computer system 100 to the ID provider computer system 136, then response 174 also contains only this ciphertext, but not the additional information 168 itself. In this case, the service computer system 150 decrypts the ciphertext using its own private key in order to then carry out the requested transaction using the additional information 168. This could, for example, involve carrying out a financial transaction, such as making a transfer for the amount specified in the additional information 168.

[0091] Alternatively, the payment can also be initiated by the ID provider computer system 136. This can be done by the ID provider computer system 136 receiving the necessary transaction data via request 166 and the additional information 168, and then executing or initiating the payment. Response 174 then contains confirmation from the ID provider computer system 136 that the payment has been made.

[0092] The transmission of the additional information 168 to the service computer system 150 can then be omitted, which is advantageous for protecting the confidentiality of this additional information 168, since this additional information 168 then only needs to be disclosed to the trusted ID provider computer system 136. The actual transaction, e.g., the delivery of the ordered product, is then initiated by the service computer system 150 after receipt of the payment confirmation contained in the response 174.

[0093] For example, the additional information 168 contains an OTP. The service computer system 150 then checks, as an additional requirement for executing the transaction, whether the OTP is valid. Preferably, the OTP is encrypted by the user computer system 100 using the public key of the service computer system 150 and then decrypted by the service computer system 150 after receiving the additional information, in order to verify its validity.

[0094] The computer system includes a terminal 186, which could be, for example, a vending machine, particularly an ATM or a vending machine. For instance, user 102 can enter an amount of money into terminal 186 to withdraw cash from their account. A visually detectable pattern, such as a QR code, is then displayed on a screen 188 of the machine, containing a URL of the service computer system 150 and the amount of money requested by user 102.

[0095] This optical pattern is captured by the display 188 using a camera 190 of the user computer system 100. The user computer system 100 then generates the transaction request 158, which specifies this amount of money. The first session 201 is established here using the URL of the service computer system 150, which was captured from the optical pattern, and the transaction request 158 ​​with the desired amount of money is transmitted to the service computer system 150 via this first session 201. The service computer system 150 then generates a corresponding request 166 to query the attributes and additional information 168 required for the disbursement of the desired amount of money.

[0096] Then, either the ID provider computer system 136 or the service computer system 150 initiates the debiting of an account belonging to user 102, which the user has specified, for example, in the additional information 168. Upon receiving the response 174 and initiating the payment, terminal 186 then receives a signal to dispense the requested amount of money, for example, in cash or to top up a cash card belonging to user 102. This can occur either if terminal 186 is directly connected to the service computer system 150 or via the network 116.

[0097] Alternatively, Terminal 186 may also be a vending machine, in which case not cash, but a desired product, such as a can of beverage or a pack of cigarettes, is dispensed by the vending machine after the execution of the payment has been signaled by the service computer system 150.

[0098] In another application, Terminal 186 could be a mobile telecommunications device, particularly a smartphone. If User 102 wants to buy something from the owner of Terminal 186, the owner enters the corresponding purchase price into the terminal. The display 188 then shows this purchase price as the payment amount, along with the URL of the service computer system 150, in the form of an optically detectable pattern. After the transaction is completed, Terminal 186 receives a signal from the service computer system 150 indicating that the payment has been processed, and the owner of Terminal 186 then hands over the goods to User 102. This could also be implemented in the point-of-sale system of, for example, a supermarket.Another application is a taximeter, which records taxi fares, or another consumption meter, such as a consumption meter for the electricity or gas consumption of a household, in particular a so-called smart meter. Reference symbol list 100 user computer systems 102 users 104 Interface 106 ID tokens 108 Interface 110 processor 112 Application program / Internet browser 113 Program / Application program 114 Network interface 116 Network 118 electronic storage 120 protected storage area 122 protected memory area 124 protected memory area 126 memory area 128 processor 130 program instructions 132 program instructions 134 program instructions 136 ID Provider Computer System 138 Network interface 140 storage 141 protected storage area 142 private key 144 Certificate 145 processor 146 program instructions 148 program instructions 150 service computer systems 152 Network interface 154 processor 156 program instructions 158 Transaction request 160 website 162 Input field 164 Input element 166 Request 168 Additional Information 170 program instructions 172 Message 174 Response 176 local connection 178 program instructions 180 identifier 182 Reading Command 184 identifier Terminal 186 188 Display 190 camera

Claims

[1] An electronic transaction method using an ID token (106) assigned to a user (102), wherein the ID token has an electronic memory (118) with a protected memory area (124) in which one or more attributes are stored, wherein access to the protected memory area is only possible via a processor (128) of the ID token, and wherein the ID token has a communication interface (108) for communication with a reader of a user computer system (100), comprising the following steps: - displaying an optically readable pattern on a screen (188) of a terminal (186), wherein the optically readable pattern encodes information which includes at least a logical address of a service computer system (150) and transaction data, - detecting the pattern using an optical sensor (190) of the user computer system and decoding the pattern by the user computer system, - transmitting a transaction request (158) from the user computer system to the logical address of the service computer system via the network, the transaction request containing the transaction data, - transmitting a request (166) from the service computer system via the user computer system (100) to an ID provider computer system (136), the transmission being carried out via the network, the request containing an attribute specification of the attributes to be read from the ID token for carrying out the transaction, - Authentication of the user against the ID token, - Authentication of the ID provider computer system to the ID token over the network, - provided that the user and the ID provider computer system have been successfully authenticated against the ID token, the ID provider computer system reads the attribute(s) according to the attribute specification from the ID token over the network with end-to-end encryption, - Transmission of a response (174) from the ID provider computer system via the user computer system to the service computer system, wherein the transmission of the response takes place via the network, wherein the response contains the read attribute(s), and wherein the response is signed by the ID provider computer system, execution of the transaction using the transaction data and the attribute(s) by the service computer system, wherein the terminal is a mobile electronic device, in particular a smartphone, wherein the optically readable pattern contains an account connection of a smartphone owner, wherein the service computer system initiates the financial transaction in order to transfer the payment amount to the smartphone owner's account, whereupon the service computer system transmits a confirmation signal to the smartphone, which is output by the smartphone via a user interface,to inform the smartphone owner of the payment. [2] A method according to claim 1, comprising the further step of checking whether the attribute(s) satisfy a predetermined criterion by the service computer system, wherein the transaction is only carried out if the criterion is satisfied. [3] A method according to any one of the preceding claims, wherein the confirmation signal is sent over the network from the service computer system. [4] The method according to claim 3, wherein the confirmation signal is sent to the user computer system and output by the user computer system as an optical pattern, wherein the terminal is configured to detect the optical pattern from the user computer system. [5] Method according to one of the preceding claims, comprising the following steps: - establishing a first session (201) between an application program (112) of the user computer system and the service computer system (150) via the network (116), - receipt of the transaction request (158) via the first session by the service computer system from the application program (112), - generation of a request (166) by the service computer system upon receipt of the transaction request, wherein the request is signed by the service computer system and the request includes an attribute specification of the attributes to be read from the ID token for executing the transaction, transaction data for specifying the transaction, an identifier (180) of the request, a URL of an ID provider computer system, and a URL of the service computer system, - transmission of a web page (160) and the request via the first session from the service computer system to the user computer system, wherein the web page has an input field (162) for entering additional information (168) for carrying out the transaction, - Display of the web page by the application program and input of additional information by the user in the input field, - establishing a second session (202) between the application program (112) and the ID provider computer system via the network using the URL of the ID provider computer system, wherein the second session is established with a secure transport layer, - Forwarding the request and the additional information from the application program to the ID provider computer system via the second session, - upon receipt of the request, generation of a session ID for a third session (203) by the ID provider computer system and storage of the request and the additional information by the ID provider computer system, - sending a message from the ID provider computer system to the application program (112) with the session ID of the third session and a logical address via the second session, - establishing the third session between a program (113) of the user computer system and the ID provider computer system via the secure transport layer of the second session, wherein the program may be different from the application program (112), - transmission of at least one certificate (144) of the ID provider computer system to the program (113), wherein the certificate contains an indication of read rights of the ID provider computer system for reading one or more of the attributes stored in the ID token, wherein the transmission of the certificate takes place via the third session, - checking by the program (113) whether the read rights specified in the certificate are sufficient to allow read access by the ID provider computer system to the attribute(s) to be read according to the attribute specification, and only if the read rights are sufficient: a) establishing a local connection (176) between the reader of the user computer system and the ID token, b) Authentication of the user against the ID token, whereby a session key is agreed upon, c) establishing a fourth session (204) between the ID token and the ID provider computer system via the local connection and the third session with end-to-end encryption using the session key, d) Mutual authentication of the ID token and the ID provider computer system via the fourth session, e) Reading the attribute(s) according to the attribute specification by the ID provider computer system via the fourth session from the ID token. - generating the response (174) which contains the read attribute(s) and at least the identifier (180) of the request, and which is signed by the ID provider computer system, - Storage of the response for retrieval using the logical address, - Reading the response from the ID provider computer system by the user computer system by retrieving the response using a read command from the logical address via the network, - Forwarding of the response by the user computer system via the first session to the service computer system, - Assignment of the response to the request using the identifier contained in the response by the service computer system, - Execution of the transaction using the response from the ID provider computer system. [6] The method according to claim 5, wherein the application program is an Internet browser, and the further program is a plug-in of the Internet browser, the plug-in being registered in a registry of an operating system of the user computer system with a plug-in identifier (184), the message from the ID provider computer system to the Internet browser including the plug-in identifier, so that the plug-in is started upon receipt of the message. [7] Method according to claim 5 or 6, wherein the program is a further application program which can be started by the Internet browser by calling a local URL, wherein the local URL includes a fixed port number according to the TCP protocol, wherein the local URL is transmitted together with the web page from the service computer system to the user computer system in order to start the further application program using the local URL by the Internet browser. [8] Method according to claim 5, 6 or 7, wherein the additional information is payment information of the user. [9] Method according to claim 8, wherein the additional information is encrypted by the user computer system using the public key of the service computer system and only the encrypted additional information is forwarded to the ID provider computer system via the second session, wherein the encrypted additional information is included in the response and the encrypted additional information is decrypted after receipt of the response by the service computer system using the private key of the service computer system. [10] Method according to one of the preceding claims 5 to 9, wherein the request contains payment information of the service computer system and wherein the additional information contains payment information of the user, and wherein the transaction data of the request contains a payment amount, wherein the payment is initiated by the ID provider computer system, and the response does not contain the payment information of the user. [11] Method according to one of the preceding claims 5 to 10, wherein the request contains payment information of the service computer system and wherein the additional information contains payment information of the user, and wherein the transaction data of the request contains a payment amount, wherein the payment is initiated by the service computer system, and the response contains the payment information of the user encrypted with the public key of the service computer system. [12] Method according to one of the preceding claims, wherein the pattern is a one-dimensional, two-dimensional, high capacity color barcode, maxicode, QR code or data matrix code or a chronological sequence of several such codes. [13] Method according to one of the preceding claims, wherein the ID token is a value or security document. [14] Method according to one of the preceding claims, wherein the response also includes the additional information. [15] The method of claim 14, wherein the additional information includes an OTP and the service computer system (150) checks the validity of the OTP, wherein the transaction is only performed if the OTP is valid. [16] A computer system comprising a terminal (186), a service computer system (150), a user computer system (100), an ID provider computer system (136), and an ID token (106) assigned to a user (102), wherein the ID token comprises an electronic memory (118) with a protected memory area (124) in which one or more attributes are stored, wherein access to the protected memory area is only possible via a processor (128) of the ID token, and wherein the ID token comprises a communication interface (108) for communication with a reader of a user computer system (100), wherein the terminal, the service computer system, the user computer system, the ID provider computer system, and the ID token are configured to carry out the following steps: - displaying an optically readable pattern on a screen (188) of a terminal (186), wherein the optically readable pattern encodes information which includes at least a logical address of a service computer system (150) and transaction data, - detecting the pattern using an optical sensor (190) of the user computer system and decoding the pattern by the user computer system, - transmitting a transaction request (158) from the user computer system to the logical address of the service computer system via the network, the transaction request containing the transaction data, - transmission of a request (166) from the service computer system via the user computer system (100) to an ID provider computer system (136), the transmission being carried out via the network, the request containing an attribute specification of the attributes to be read from the ID token for carrying out the transaction, - Authentication of the user against the ID token, - Authentication of the ID provider computer system to the ID token over the network, - provided that the user and the ID provider computer system have been successfully authenticated against the ID token, the ID provider computer system reads the attribute(s) according to the attribute specification from the ID token over the network with end-to-end encryption, - transmission of a response (174) from the ID provider computer system via the user computer system to the service computer system, wherein the transmission of the response takes place via the network, wherein the response contains the read-out attribute(s), and wherein the response is signed by the ID provider computer system, - carrying out the transaction using the transaction data and the attribute(s) by the service computer system, wherein the terminal is a mobile electronic device, in particular a smartphone, wherein the optically readable pattern contains an account number of a holder of the smartphone, wherein the service computer system initiates the financial transaction in order to transfer the payment amount to the account of the holder of the smartphone, whereupon the service computer system transmits a confirmation signal to the smartphone, which is issued by the smartphone via a user interface in order to inform the holder of the smartphone of the payment.

Citation Information

Patent Citations

  • Method for generating a soft token, computer program product and service computer system

    DE102011082101A1

  • Information processing apparatus with optical data reader, servers, and electronic commerce method

    US20030120555A1

  • Mobile image payment system

    US20120290415A1

Cited By

  • PROVIDING DIGITAL PROOF OF IDENTITY

    DE102024115072A1