The invention relates to a method and an arrangement for transmitting transaction data using a public data network. In essence, it relates to a method and system for authorizing online payments.
Online shops today often have several methods of authentication from among which to choose when authorizing an online payment:
In unpublished European patent application No. 16204208.9, the applicant proposes a user-friendly and yet ultra-secure method and system of the cited type which functions reliably with high-quality mobile devices.
A suitable smartphone therein assumes the function of a debit/credit card point-of-sale terminal capable of wireless short-range data transmission (NFC). With respect to meeting the standard security requirements for payment transactions, of importance are the security features of the respective user terminal as implemented by the manufacturer.
The present invention addresses the object of disclosing a further user-friendly and yet concurrently secure method and system for authorizing online payments which can be implemented using mid-range and low-priced terminals and thus be accessible to a wider audience.
As far as the method aspect, this object is solved by a method having the features of claim 1 and as far as the apparatus aspect, by an arrangement having the features of claim 10. Advantageous further developments of the inventive concept constitute the subject matter of the respective dependent claims.
The present invention thereby creates a secure and user-friendly method and system for authorizing an online transaction using an NFC-enabled smart card and a simple smartphone.
The invention solves the object as posed in particular by the fact that the card PIN, which is required for EMV-compliant activation of the debit/credit card (card) signature function, is not input via a user interface of the user terminal (smartphone), which would require protective measures against PIN phishing, but is instead automatically sent to the card from a server secured end-to-end (from the server to the card) via the user terminal.
For data protection reasons, the server, which according to the invention must at least occasionally provide the card PIN in plain text, needs to remain at the card's issuing bank. When the NFC-enabled smart card and smartphone need to communicate with the card-issuing bank for the given reason, it is particularly suitable for an online payment to be made via transfer, e.g. subject to the FinTS (formerly known as HBCI) or MasterCard CAP standards, and not subject to a payment transaction standard such as for example ec-Cash.
Used in online banking, the inventive method replaces the TAN (international: one-time code) by a signature on the card which until now could only be activated via special contact-based card readers (Secoder) and not via a commercially available smartphone.
Alternatively to a card PIN as an authorization data set, which the server communicates to the card to activate the signature function, the authorization data set can also consist of other useful data (payload) which is or is to be associated with a verification of originating from an authorized source.
The server can either encrypt the payload to this end with a symmetric key, which is also stored in the card, or sign with an asymmetric public key, the complementary public key to which is stored in the card.
The authorization data set can for example consist of the transaction file which is to ultimately sign the card.
The user terminal can communicate the authorization data set to the server together with previously collected user authentication data, for example a PIN arranged between user terminal and server or the result of a fingerprint comparison, protected by a TLS channel authenticated on both sides. After the server verifies the user authentication data with a positive result, it transmits the authorization data set, e.g. the transaction file, to the card signed or respectively encrypted end-to-end via the user terminal. By linking NFC-enabled debit and credit cards to a customer's NFC-enabled terminal (smartphone), the inventive method and system achieves the following advantages:
In one possible application, the user's main bank issues the user an NFC-enabled card, expands a pre-existing mobile banking app with the inventive functions of the mobile app, and operates an online banking server. In this case, all three essential communication elements (card, app and server data set) are already logically connected so that the user no longer has to manually assign them.
The main bank could provide its customer with a private key and public key protected pursuant to the white-box cryptography principle for trustworthy communication with the online banking server and an NFC and EMV compatible communication interface to the NFC card during a mobile banking app upgrade.
This arrangement enables using a suitable signature function on the NFC-enabled card in line with the German FinTS standard or other electronic banking standards for the user to confirm a money transfer to the server.
The input of a static password or preferably a finger being placed on a fingerprint sensor on the user's smartphone or other biometric authentication methods could serve as the second authentication factor.
From the user's perspective, enabling a transfer can ensue as follows:
1. In an online banking situation using a desktop computer, the transaction data is loaded onto the smartphone by scanning a QR code or by Google or Apple Push Notification. In a mobile banking situation, this step is omitted.
2. The transfer data is checked on the smartphone screen.
3. The NFC card is held up to the NFC-interface of the smartphone, and
4. A finger is pressed onto the smartphone's fingerprint sensor.
The order of steps 3 and 4 can be switched, particularly when the transaction file, before being signed on the card, is communicated to the server together with the user authentication data so that an authorization data set can be created from the transaction file which activates the card for the signature of the transaction file.
The user authentication data expresses the intent (act of will) of the user wishing to make the transaction.
There are different ways in which the transaction file can be provided in step a) of the proposed method. In a first, so to speak “direct” alternative, this step comprises the following sub-steps:
a0′) transmitting initial transaction data from a web server to the user terminal via the data network and mobile network or WLAN and generating an initial transaction file in the user terminal,
a1′) processing the initial transaction file on the user terminal so as to extract at least some of the transaction data.
In another alternative, in which the user uses a further device (for instance a laptop or tablet) in addition to his smartphone, step a) comprises for example the following sub-steps:
a0) transmitting initial transaction data from a web server to a display unit connected to the data network via said data network, and
a01) local visual and/or acoustic displaying of the initial transaction data thereon, particularly visually displaying as bar code or QR code on a provider website, or
a02) forwarding the initial transaction data via Google or Apple Push Notification service to the user terminal,
a11) receiving the display and generating an initial transaction file in the user terminal or
a12) receiving the display and generating an initial transaction file in a receiver device and thereafter transmitting same to the user terminal via wireless close-range data transmission,
a2) processing the initial transaction file on the user terminal to extract at least some of the transaction data.
In one preferred implementation from the current perspective, a mobile app installed in the user terminal authorizes the authorization data service to the online banking server in step b) by means of a private key, which is in particular fragmented pursuant to the white-box cryptography principle and stored in distributed fashion by the program code of the mobile app. This reduces the chances of phishing attack success to almost zero.
It appears further preferential for the mobile app to be uniquely assigned an NFC card of wireless close-range data transmission during installation on the user terminal and this assignment to be stored in the online banking server of the authorization data service. This further increases the security of the entire process insofar as virtually eliminating fraudulent interference at the connection point between the NFC card and the mobile app.
With the same objective of further increasing security, a further implementation provides for the mobile app being authenticated to the online banking server by a public key procedure and/or the mobile app and online banking server communication being subject to encryption. According to a further implementation of the invention, a user biometric authentication step is additionally carried out on the user terminal, in particular via a fingerprint sensor. Although this implementation does require the user terminal to have a sensor for biometric user characteristics, it then provides an easily realizable further security advantage.
For the essential data exchange between user terminal and smart card, one advantageous implementation is in which the user terminal and the smart card communicate bi-directionally via the near-field communication (NFC) protocol and the EMV standard for chip-based payment cards.
It is furthermore provided for the authorization data set to in practice comprise the encrypted transaction file or a PIN of the credit card or debit card such as for example the Girocard (bank card) in step c. Alternatively, a data set of physiological user data (fingerprint, retinal image, voice profile, etc.) can in principle also be used, although it carries a higher latent risk of rejection for the desired transaction.
Device and/or system aspects of the present invention largely ensue from the method aspects described above and will insofar not be repeated at this point. It is noted that configurations which make use of a smart card separate from the user terminal or a smart card component incorporated into the user terminal are also included herein.
However, it is also pointed out that in one expedient implementation the user terminal has a device key to authenticate in particular a private key in terms of a public key infrastructure (PKI), at least with respect to an app loading system and with respect to the online banking server of the authorization data service.
In a further advantageous implementation of the user terminal, the user terminal comprises a biometric sensor for detecting a user's biometric data, in particular a fingerprint sensor, and the mobile app for processing a biometric data set is formed by a biometric sensor.
Advantages and functionalities of the invention are additionally yielded by the following description of an example embodiment and from design aspects of the invention based on the figures, which show:
The invention solves the object by a method for authorizing and executing a transaction which comprises the following steps in one advantageous implementation and simplified formulation in accordance with
As
When the method according to the invention is embedded into a mobile commerce process, the use of a computer 1 is dispensed with and inventive step a), in which the transaction data 3 is graphically displayed on the website 2, is visualized as e.g. QR code. Step b) changes in this case to the effect of the smartphone 4 no longer needing to scan in the transaction file 3 but it instead being rendered as part of a data communication from the web server to a browser on the smartphone.
If the online merchant does not wish to make the inventive payment method conspicuously selectable for all buyers, because only some of the buyers are equipped with smartphones 4 and smart cards 9 according to the invention, the mobile commerce variant of the inventive payment method can also be integrated into an already established payment system.
In this case, the homepage of the established payment system can include a JavaScript which is loaded into the smartphone browser and detects the user-agent string there and, if it indicates an Android-based Chrome browser, directs the browser to a new web page where the user needs to confirm the further process by pressing a menu button. The new web page thereafter returns a URL to the Chrome browser which is configured to either allow an inventive mobile app 7 installed on the smartphone to open by Android Intent Call or, if this is not possible, redirect to the homepage of the established payment system.
The established payment process is likewise used when the JavaScript of the homepage concludes, based on the detected user-agent string, that the connected browser is not an Android-based Chrome browser.
The embodiment of the invention is not limited to these examples but is rather also possible in a plurality of variations which lie within the scope of skill in the art.
Number | Date | Country | Kind |
---|---|---|---|
102017106295.5 | Mar 2017 | DE | national |
102017122799.7 | Sep 2017 | DE | national |
Number | Date | Country | |
---|---|---|---|
Parent | 15934376 | Mar 2018 | US |
Child | 16791458 | US |