RU2820419C1 - System and method of organizing nfc payments - Google Patents

Abstract

FIELD: mobile payment technologies.

SUBSTANCE: disclosed technical result is achieved in a method for organizing NFC payments, in which a contactless NFC connection of a mobile device of a payer with an intermediate device is established; providing the exchange of commands between the mobile device of the payer and the intermediate device, as a result of which payment data is received from the mobile device of the payer on the intermediate device; storing said payment data in the memory of the intermediate device; establishing contactless NFC-connection or contact connection of intermediate device with external system; providing an exchange of commands between an intermediate device and an external system, as a result of which payment data is received on the external system from the intermediate device for carrying out a payment transaction.

EFFECT: wider field of application of NFC payments with preservation of their characteristics by providing the possibility of transferring payment data in the existing infrastructure for receiving and processing payments using an alternative method, high reliability of data protection and payment security, protection of payment data from unauthorized access.

20 cl, 4 dwg

Description

Technical field

The present invention relates to the field of mobile payment technologies. Recently, NFC technology has found widespread use in this area to establish communication between short-range contactless communication devices.

State of the art

To make mobile payments that use NFC protocols (ISO 14443 standard), mobile devices are used, the operating features of which vary depending on the manufacturer of the mobile device and the operating system installed on the device. One of these features is that not all mobile devices are capable of routing commands received by the mobile device from external systems (for example, from a POS terminal, ATM, self-service terminal or from a device for accepting payment instruments for transport) and intended for mobile applications. stored in the memory of these mobile devices. This imposes some restrictions on NFC payments and requires the implementation of special solutions for organizing NFC payments.

At the moment, payment using NFC technology is carried out in only one way. The payer's mobile device, which supports NFC, is brought to exchange data with an external system (seller's device, for example, a POS terminal), which also supports NFC. Data exchange is carried out according to specific data exchange protocols described in industry (EMV) and international Standards (for example, ISO/IEC 7816-4). The external system operates in Reader Mode (generates commands and receives responses to them), and the payer’s mobile device operates in Card Emulation mode. To exchange data, the payer’s mobile device and the external system exchange commands in the APDU (application protocol data unit) format. The external system sends a Command APDU (C-APDU) command to the mobile application on the payer's mobile device, and the said mobile application sends a response to the Response APDU (R-APDU) command. To ensure data exchange, a mobile application is downloaded to the payer’s mobile device. The mobile application can be located in the security element or in the memory of the payer’s mobile device.

However, there are payer mobile devices where commands cannot be routed to mobile applications hosted on the payer's mobile device. In such mobile devices, said commands from the external system are by default routed exclusively to predefined mobile applications on the payer's mobile device, for example, mobile applications hosted in the security element of the payer's mobile device. Thus, not every payer’s mobile device is capable of routing commands received from an external system to those mobile applications on the payer’s mobile device for which they are intended. At the same time, for such payer mobile devices there are no alternative methods of data transmission to eliminate this drawback.

Thus, there is a need to create a universal system and method for organizing NFC payments from the payer’s mobile device, which is not capable of routing commands received from an external system to the payment application on the payer’s mobile device, resulting in payment using NFC technology using arbitrary payment cards. applications becomes impossible.

To solve this problem, it is possible to configure the payer’s mobile device to work in Reader Mode. Then, on the payer's mobile device, instead of transmitting payment data in responses to commands from an external system, it is possible to initiate the transfer of payment data to an external system. However, this creates an obstacle to using the standard infrastructure for receiving and processing NFC payments, since both the external system and the payer’s mobile device in this case will simultaneously operate in Reader Mode, that is, generate commands and receive a response to them. Obviously, two devices operating in Reader Mode cannot organize a dialogue to exchange data for the purpose of making a payment.

Thus, the known technologies do not allow solving the technical problem, which is to create a system and method for making secure mobile payments from any mobile devices that support NFC, regardless of the features and options for customizing the parameters of such devices.

To solve the problems listed above, it is proposed to use an intermediate device that receives C-APDU commands and responds to them in R-APDU responses (Card Emulation mode). Such an intermediate device, on the one hand, works with the payer’s mobile device, receiving from it C-APDU (Reader Mode) commands containing payment data necessary to complete the payment. On the other hand, such an intermediate device works with an external system, receiving C-APDU (Reader Mode) commands from it, thereby implementing the payment execution protocol.

As the closest analogue to the patented solution, a method for transmitting an electronic check has been adopted (RF patent No. 2733090, G06Q 30/00, published on September 29, 2020), in which an electronic check is transferred from a cash register device to the payer’s mobile device through the mediation of an intermediate device, in this case, the electronic check is stored on the intermediate device temporarily and is deleted from memory after it is sent to the payer’s mobile device. As a result of this organization of interaction between devices, the protection of personal data during trading operations increases.

However, the system components described in the patent are connected via the Internet and are not configured to support NFC technology, including for organizing data exchange between two devices that operate in Reader Mode using an intermediate device operating in Card Emulation mode. In addition, in the method described in the patent, it is impossible to prepare and send payment data from the payer’s mobile device; accordingly, the method described in the closest analogue is not applicable to solve the problem.

Disclosure of the Invention

The technical problem to which the proposed invention is aimed is the creation of a solution that will allow the use, in the standard infrastructure of receiving and servicing mobile payment devices that support NFC technology, of an arbitrary mobile application that is installed on the payer’s mobile device from any manufacturer with any operating system installed on it system.

The technical results are the expansion of the scope of application of NFC payments while maintaining their characteristics by ensuring the possibility of transferring payment data in the existing infrastructure for receiving and processing payments in an alternative way; increasing the reliability of data protection and payment security, ensuring the protection of payment data from unauthorized access.

The declared technical results are achieved in a method for making NFC payments, in which:

- establish a contactless NFC connection between the payer’s mobile device and the intermediate device;

- ensure the exchange of commands between the payer’s mobile device and the intermediate device, as a result of which payment data is received from the payer’s mobile device on the intermediate device;

- storing said payment data in the memory of the intermediate device;

- establish a contactless NFC connection or contact connection between an intermediate device and an external system;

- ensure the exchange of commands between the intermediate device and the external system, as a result of which payment data is received on the external system from the intermediate device to carry out a payment transaction.

In particular, before sending the response to the last command from the external system towards the intermediate device, the payment data is deleted from the memory of the intermediate device.

In particular, before transferring payment data to the intermediate device, the payer’s mobile device authenticates the intermediate device, and also generates a public key for transmitting payment data in encrypted form, and on the intermediate device supports the said authentication, and also organizes secure data exchange with the payer’s mobile device .

In particular, APDU commands are used as commands for exchanging payment data between the payer’s mobile device, the intermediate device and the external system.

In particular, on the payer's mobile device, comprising at least a processor and memory, C-APDU commands are generated containing payment data retrieved from the memory and a response R-APDU is sent for data exchange.

In particular, they provide secure storage of the payer's data on the payer's mobile device using at least one of: a key storage, using a local database, remote device certification, application obfuscation.

In particular, on an intermediate device containing a security element with a trusted execution environment and memory, C-APDU commands are received and R-APDUs are sent in responses for communication with the payer's mobile device and the external system.

In particular, the intermediate device is received and maintained in an external system in a contact and/or non-contact manner.

In particular, at least a bank card number or a token, the validity period of a bank card or token, a transaction counter, a session key for generating a cryptogram or a cryptogram are used as payment data.

The declared technical result is also achieved in a system for organizing NFC payments, containing a payer’s mobile device, an intermediate device and an external system, configured to establish a connection and exchange data, and

the intermediate device is configured to establish an NFC connection with the payer's mobile device for receiving payment data and a contactless NFC connection or contact connection with an external system for sending payment data, and contains a memory configured to store payer data received from the payer's mobile device;

the payer's mobile device is configured to establish a contactless NFC connection with an intermediate device to transfer payment data to the latter;

the external system is configured to establish a contactless NFC connection and/or a contact connection with an intermediate device to receive payment data for conducting a payment transaction.

In particular, the payer's mobile device is an NFC-enabled mobile device, including a processor and memory, and optionally a security element with a trusted execution environment.

In particular, the intermediate device contains a trusted environment security element and memory.

In particular, the external system is a device for accepting and servicing bank cards in a standard infrastructure, which is equipped with contact and/or contactless means of data input and output in card payment systems.

In particular, the intermediate device is configured to delete and/or update payment data.

In particular, the payer's mobile device is configured to authenticate the intermediate device, as well as generate a public key for transmitting payment data in encrypted form, and the intermediate device is configured to support said authentication, as well as organize secure data exchange with the payer's mobile device.

In particular, the external system, intermediate device and mobile device of the payer are configured to establish communication via interaction channels for receiving and/or transmitting payment data in APDU commands containing at least a bank card number or token, the validity period of the bank card or token, transaction counter, session key for generating a cryptogram.

In particular, the payer's mobile device is configured to send C-APDU commands and receive an R-APDU response, the intermediate device is configured to receive C-APDU commands and send an R-APDU response, the external system is configured to send C-APDU commands, and receiving the R-APDU response.

The claimed technical result is also achieved in a payer's mobile device supporting NFC technology, including at least a processor, memory and configured to sequentially

- receive a command from the payer to initiate a payment transaction,

- establish a contactless NFC connection with an intermediate device,

- retrieve payment data from memory;

- prepare commands containing payment data and send payment data to the intermediate device to personalize the latter.

In particular, the payer's mobile device additionally contains a security element with a trusted execution environment.

In particular, the payer's mobile device is configured to retrieve payment data from memory, which includes at least a bank card number or token, the validity period of the bank card or token, a transaction counter, a session key for generating a cryptogram, and transmit said data in C-APDU commands to the intermediate device and receive the R-APDU response.

In particular, the payer's mobile device is configured to perform authentication of the intermediate device before transferring payment data from the payer's mobile device to the intermediate device, as well as generating a public key for transmitting payment data in encrypted form.

In particular, the payer's mobile device is configured to provide secure storage of the payer's data on the payer's mobile device using at least one of: a key store, using a local database, remote device attestation, application obfuscation.

The claimed technical result is also achieved in an intermediate device containing a security element with a trusted execution environment and memory, and by means of this device

establish a contactless NFC connection with the payer’s mobile device for data exchange;

- as a result of data exchange, payment data is received on the intermediate device;

- store payment data received from the payer’s mobile device in the memory of the intermediate device;

- establish a contactless NFC connection or contact connection with an external system for data exchange, as a result of which payment data is transferred from the intermediate device to the external system.

In particular, the intermediate device is configured to delete payment data from the memory of the intermediate device before sending the R-APDU response to the last command from the external system to the intermediate device.

In particular, the intermediate device is configured to support the authentication of the intermediate device, which is carried out by the payer's mobile device, as well as to organize secure data exchange with the payer's mobile device.

In particular, the intermediate device is configured to receive and transmit payment data, which includes at least a bank card number or token, the validity period of the bank card or token, a transaction counter and a transaction cryptogram.

In particular, the intermediate device is configured to establish communication with both the payer's mobile device and an external system for exchanging data in APDU commands, namely, receiving said data in C-APDU commands and sending a response R-APDU.

Payer's mobile device is a mobile device (for example, a smartphone or tablet computer) of any manufacturer and with any operating system (OS) supporting NFC technology. The payer's mobile device includes a processor, memory and, according to one option, additionally includes a security element with a trusted execution environment.

The processor is at least one element in the hardware of the payer's mobile device, configured to execute machine-readable instructions prescribed by the mobile application (software).

The memory is configured to store payment data and machine-readable instructions prescribed by the mobile application.

In some cases, the component referred to is a SIM/eSIM card on which the mobile application is installed. In another embodiment, the payer's mobile device further comprises a Global Platform Trusted Execution Environment (TEE) security element. The mentioned security element is a microcontroller included in the hardware of the payer's mobile device (built-in security element). A feature of the trusted execution environment is that payment data that is loaded and processed within the trusted execution environment is protected in terms of confidentiality and integrity. The payer's mobile device is equipped with at least one antenna for transmitting an NFC signal, which can be located in any part of the payer's mobile device. The mobile application contains machine-readable instructions to provide a user interface and communicate with the intermediate device. A mobile application can be implemented on a web server with user access through a browser, or can be implemented in a trusted execution environment, or in the memory of the payer’s mobile device as an independent payment mobile application, SDK (software development kit - a set of script libraries for integration to another mobile application) for a mobile bank or another mobile application. For example, a mobile application can be used to implement NFC payments using PWA (Progressive Web Application) technology to work with an external system through a smartphone web browser. In the context of the present invention, a payer's mobile device supporting NFC technology is capable of operating in Reader Mode and exchanging data with an intermediate device in APDU commands, including payment data and other necessary data that allows the logic of the mobile application to be implemented. The functionality of the payer's mobile device will also be described in more detail below.

Operating system of the payer's mobile device (OS) is software installed in the processor of the payer's mobile device, designed to organize user interaction with the said device to use the resources of the payer's mobile device.

An intermediate device is a device designed to operate both in contactless mode and, optionally, additionally in contact mode. To operate in contact mode, the intermediate device has a contact pad for interacting with the card reader of the POS terminal via a contact interface. By way of non-limiting examples, the intermediary device may be in the form factor of a microprocessor card (dual card, combination card, or dual interface card), a wearable device of any shape, size and material (key fob, ring, bracelet, watchband), smartphone/tablet , or other NFC-enabled device. The intermediate device can be placed contact or contactlessly on the body of the payer's mobile device or separately from the payer's mobile device and from the external system.

The intermediate device contains a security element with a trusted execution environment and memory. Memory may include, but is not limited to, random access memory, non-volatile memory, rewritable memory, or read-only memory.

The processor is configured to execute machine-readable instructions prescribed by the application (software) of the intermediate device. The memory is configured to receive and record payment data received from the outside (for example, from a payer’s mobile device) and also with the ability to delete the payer’s payment data before sending a response to the last command from the external system to the intermediate device.

A security element with a trusted execution environment is a microcontroller with a middleware application installed on it, which, when a contact or contactless (for example, NFC) connection is established, ensures the execution of machine-readable instructions of the middleware application. An intermediate device supporting NFC technology is designed to operate in Card Emulation mode and exchange data in APDU commands separately with the payer’s mobile device and separately with an external system.

By way of non-limiting examples, other applications such as payment applications (e.g., offline prepaid wallet - offline prepaid wallet, digital rubles, and other cryptocurrencies) and non-financial applications (e.g., identity application) may also operate on the intermediate device. , EDS (electronic digital signature) and others).

External system - a device for receiving and servicing bank cards in a standard infrastructure with contact and/or contactless (for example, NFC technology) data reading technologies in card payment systems. The external system is equipped with contact (card reader) and/or contactless input/output means to accept payment instruments as defined by the protocols operating in the standard infrastructure of card payment systems. As an example, an external system can be represented by including, but not limited to, a stationary, stand-alone or mobile POS terminal, ATM, self-service terminal, or a transport payment acceptance device.

Intermediate device contact to external system - communication in which the intermediary device is inserted into the card reader of a POS terminal or ATM (ISO 7816-3).

Contactless communication is a connection established between devices located at some distance from each other (not mechanical communication). Examples of contactless communication are NFC, bluetooth, etc. technology. Data transmission technology via NFC is standard for non-cash payments. The technology presented in the description does not contradict the principles of data transfer technology via NFC, which means that the technology maintains high speed and security of transferring the payer’s payment data. It follows that expanding the scope of application of NFC payments in the proposed technology is achieved by developing an alternative method of data transfer precisely in the existing infrastructure for receiving and processing payments, which means that data exchange is carried out while maintaining speed and security in accordance with the standards operating within the framework of NFC technology . According to one option, software modifications can be made to the external system to use a contact intermediate device. Improvements involve changing the logic of the external system to requalify a contact transaction as a contactless one (for example, based on a special value of the IAD data object, Issuer Application Data, used to verify the transaction). Such modifications can optionally be implemented in the case of using a contact intermediate device. As a result of these improvements, it will not be necessary to remove and insert an intermediate device into the contact card reader of an external system each time a transaction is performed. In this way, the contact intermediate device can remain permanently installed in the contact card reader of the external system. Before sending the response to the last command from the external system towards the intermediate device, the payer's data is deleted from the memory of the intermediate device. Thus, the payer’s data is used only for one operation and cannot be used by attackers, as a result of which the reliability of data protection and payment security increases.

Data exchange (receiving and sending commands or, in other words, device dialogue) is carried out in standard APDU commands, while the payer’s mobile device and the external system operate in Reader Mode (issue commands), and the intermediate device operates in Card Emulation mode. cards).

Payer data includes a standard set of data used to complete a payment transaction. The mentioned data includes at least a bank card number (Primary Account Number, PAN) or token, validity period of the bank card or token, card transaction counter (Application Transaction Counter, ATC), session key for generating a cryptogram. The listed data is mandatory, but not exhaustive; among the payer’s data, other bank card data and/or transaction data stored in the memory of the payer’s mobile device may additionally be transmitted, for example, bank card data may additionally include the name of the bank card owner, cryptographic transaction data may include data for offline dynamic authentication (Offline Data Authentication, ODA) and others.

For this area of technology, the security issues of storing, using and transmitting payment data are extremely pressing. The payment industry uses various technologies to protect the data of bank card holders in accordance with established security standards. The described technology for organizing NFC payments is designed to comply with and maintain the mentioned standards, which is another factor in maintaining the high security of organizing NFC payments.

As non-limiting examples, data protection mechanisms are applied to payment data stored on the payer's mobile device, such as the use of a key store (KeyStore), the use of a local database, remote device attestation, mobile application obfuscation, etc.

The key store (KeyStore) is designed as a protected memory area (essentially, in the form of a local database) designed to store only encryption keys (namely public keys) and protect them from unauthorized use. The data is securely protected, because only the mobile application on the payer's mobile device contains a password (secret) for retrieving the key to sign the transaction. That is, the password is not with the payer, but is stored in the mobile application of the payer’s mobile device, which also increases the security of the described technology, since payment data is reliably protected.

Remote device certification is a procedure for checking a device’s parameters by a third-party system, allowing one to draw a conclusion about its condition, the presence of malware, and verify the device’s condition.

Obfuscation of a mobile application is the processing of the program code of a mobile application to bring it into a form that is difficult for working with this code. In addition, a limited set of payment data is stored in the payer’s mobile device, only sufficient to perform several payment transactions.

To improve security, the proposed technology also uses mechanisms to provide protection against fraudulent transactions. In particular, when making payments for large transaction amounts, the external system is configured to request the entry of an Online PIN for a transaction amount exceeding a threshold value (bank card holder verification procedure). According to another option, a one-time PIN Offline can be used, generated by a mobile application on the payer’s mobile device, and presented by the user during the operation on the terminal. According to another option, to increase the security of transactions, offline authentication of the payment application (ODA) is carried out, thanks to which the safety of payment data from changes is guaranteed, because The procedure allows you to confirm that the read payment data was signed by the payer’s mobile device.

Brief description of drawings

Rice. 1 - diagram of interaction between the payer’s mobile device, the intermediate device and the external system.

Rice. 2 - options for implementing a payer’s mobile device.

Rice. 3 - embodiments of the intermediate device.

Rice. 4 - external system device.

According to Fig. 1, the proposed technical solution contains a payer's mobile device containing memory and a processor, an intermediate device containing memory, a security element with a trusted execution environment of at least one application, an external system, wherein at least the payer's mobile device and the intermediate device are configured to exchange data using communication channels provided through NFC technology.

The NFC-enabled intermediate device contains memory and a security element with a trusted execution environment.

To organize an alternative method for making NFC payments from the payer’s mobile device, which is not configured to route C-APDU commands from the POS terminal to the memory of the payer’s mobile device, an inverse order of data exchange is used. Instead of receiving C-APDU commands from the POS terminal, the payer's mobile device sends C-APDU commands to the POS terminal, wherein the C-APDU commands contain payment data retrieved from the memory of the payer's mobile device.

Since in this scenario both the external system and the payer’s mobile device operate in Reader Mode (they issue C-APDU commands, but cannot receive them), the external system and the payer’s mobile device cannot exchange data with each other directly. To organize a dialogue between them, an intermediate device is used, which is designed to operate in Card Emulation mode (emulates a card), and therefore with the ability to receive C-APDU commands and respond with R-APDU to these commands when interacting with both an external system and a mobile phone. payer's device.

The payer's mobile device is brought to the intermediate device to establish an NFC connection. On the payer's mobile device, through the user interface, a command/instruction is received from the payer to transfer payment data to the intermediate device.

To improve security, before the first transfer of payment data from the payer's mobile device to the intermediate device, authentication (authentication) of the intermediate device is performed by the payer's mobile device. Authentication is implemented using asymmetric encryption methods. Using a public key stored on the payer’s mobile device (for example, in a key store, KeyStore), data is encrypted, which is then transmitted over an unsecured communication channel to an intermediate device. The private key stored on the intermediate device is then used to decrypt the data that was encrypted using the public key.

Next, after successful completion of the authentication procedure, payment data is retrieved from memory on the payer’s mobile device, which is transmitted in C-APDU commands to the intermediate device, where it is stored for further payment processing. In response to the C-APDU, commands on the payer's mobile device receive R-APDU data that is used to implement the logic of the payment application of the payer's mobile device, and optionally store it in the memory of the payer's mobile device. Thus, the payer’s mobile device does not receive C-APDU commands (as is known from the prior art), but sends them, with payment data located inside.

Thanks to the use of the payer's mobile device, configured to initiate the transfer of the payer's payment data and work in Reader Mode, the described technology eliminates the existing problem of limiting the routing of incoming commands on the payer's mobile device, since the transfer of said payment data from the payer's mobile device is used to organize payment , and not their reception by the payer’s mobile device. At the same time, due to the use of NFC technology, high connection and data transfer speeds are maintained, as well as data transfer reliability.

The intermediate device is brought to the payer's mobile device to establish an NFC connection and payment data is received from the latter. After being received at the intermediate device, the payment data is recorded in the device’s memory, that is, in essence, the intermediate device is personalized. After this, the intermediate device is brought to an external system (for example, to an ATM or POS terminal) to establish contactless NFC communication, or the intermediate device is inserted into the card reader of the external system to establish contact communication, or an intermediate device is used that is permanently located in the card. reader. Next, the intermediate device and the external system, according to the rules defined in industry, international Standards, as well as the standards of the corresponding payment system, exchange APDU commands. The external system sends C-APDU commands to the intermediate device to begin communicating with the latter. The intermediate device, which performs the functions of a bank card, sends an R-APDU response containing payment data received in the previous step from the payer’s mobile device.

After performing the operation on the intermediate device, the memory of payment data received from the payer’s mobile device is optionally cleared (for example, if the intermediate device is not the payer’s personal device). Thus, according to one option, the intermediate device is used to perform only one payment operation, and then is depersonalized and ready to receive payment data from the same or another payer’s mobile device to carry out the payment operation. The next operation requires re-personalization of the data intermediate device to perform a new transaction (at least a new session key to generate the cryptogram and a transaction counter).

Using an intermediate device solves the limitation problem associated with routing commands from an external device to the payer's mobile device. Reception of C-APDU commands, which are essentially a request to obtain payer data, typically (in the prior art) originate from an external system and are received on the payer's mobile device in accordance with specified restrictive instructions. In the described technology, the payer's payment data is initially sent in C-APDU commands from the payer's mobile device, which the external system is not able to receive and process in accordance with the standards existing in the payment acceptance and processing industry. The use of an intermediate device configured to operate in Card Emulation mode allows you to set up a dialogue between the payer’s mobile device and an external system in a scenario in which the payer’s payment data is sent to the external system at the payer’s initiative. Thus, thanks to the use of an intermediate device, a payer’s mobile device from any manufacturer and with any operating system will be able to set up a dialogue with an external system through the said intermediate device.

Despite the fact that both the payer’s mobile device and the intermediate device perform specific functions, the technology nevertheless retains the ability to use standard APDU commands, which means the technology can be used in the standard infrastructure for receiving and processing payments using NFC technology. Thus, the advantages of the declared technology are achieved without compromising the speed and security of payments.

Moreover, security is also achieved because, according to one of the options, the payer’s data is written into the memory of the intermediate device (the intermediate device is personalized) for only one payment transaction, and then the mentioned data is automatically deleted from the memory of the intermediate device upon sending a response to the last APDU command external system. Thus, the possibility of using an intermediate device in fraudulent transactions is eliminated, which is especially important for the security of technology in this field of technology. The payment data necessary to carry out the payment transaction is stored in the memory of the payer’s mobile device and is transferred to the intermediate device at the initiative of the payer (for example, if the intermediate device is not the payer’s personal device). Before each data transfer, the payer's mobile device performs an intermediate device authentication process.

Data exchange between the external system and the intermediate device is carried out contact and/or contactless in accordance with the rules and standards applicable in the field of technology. Since the external system accepts an intermediate device that has been personalized in advance, it is read on the external system as a regular bank card or a tokenized bank card. In this regard, at this stage there is no need to make any additional changes to the external system.

Example 1

The payer activates the mobile banking application on his smartphone. Next, the payer initiates personalization of the key fob (intermediate device). To do this, the smartphone is brought to the key fob and a contactless NFC connection is established. In this case, the intermediate device, represented in this example by a key fob, is not a personal device of the payer, but is located on the side of the seller - the recipient of funds, for example, on the side of the merchant (trade and service enterprise).

The key fob is authenticated on the payer's smartphone. After successful completion of authentication on the payer's smartphone, the payer's payment data, such as the token, the token's expiration date, are retrieved from the memory of the payer's smartphone, and the transaction counter value and the session key are retrieved from the key store (KeyStore) to generate a cryptogram. Next, the mentioned payment data is placed in C-APDU commands and sent to the key fob (intermediate device), which is located on the seller’s side. In response, an R-APDU response is sent from the key fob to the payer’s smartphone via NFC wireless technology, allowing the logic of the payment application to be implemented. The received mentioned data is recorded in the memory of the key fob, as a result the key fob is personalized and ready to exchange data with the POS terminal (external system) as a tokenized bank card to access the payer’s account for the purpose of payment, withdrawal/deposit of cash, checking the account status and other known card transactions.

Next, at the POS terminal with contact and contactless NFC interfaces, the exchange of the mentioned data with the key fob (intermediate device) is initiated via the contactless interface. To do this, the key fob, which after personalization performs the functions of a tokenized bank card (is a digital analogue of a bank card), is brought to the POS terminal at a distance sufficient to establish an NFC connection. After this, the POS terminal sends C-APDU commands containing a request to receive payment data. Next, an R-APDU response containing the mentioned payment data is sent from the key fob towards the POS terminal, thereby implementing the protocol for interaction between the external system and the intermediate device. Data exchange between the POS terminal and the key fob takes place in accordance with current rules and standards.

Before sending the R-APDU response to the last C-APDU command from the POS terminal to the key fob, the payment data is deleted from the key fob's memory. In other words, the key fob (intermediate device) is depersonalized. Thus, the claimed technology ensures high transaction security, since the mentioned payer data is available only for one payment operation (transaction) initiated by the payer.

Example 2

The payer activates the MirPay mobile application on his smartphone. A smartphone with the MirPay mobile application is designed to function in contactless mode (using NFC technology). Next, the payer initiates personalization of the dual microprocessor card (intermediate device).

The microprocessor card is a dual card, that is, the said card is designed to function in both contact and contactless modes (using NFC technology). In this case, the dual microprocessor card is the payer’s personal device.

For personalization, the payer initiates the transfer of payment data through the MirPay mobile application interface on his smartphone and brings the smartphone to the microprocessor card to establish an NFC connection. On the processor of the payer's smartphone, the request entered by the payer is processed and the authentication process (authentication check) of the dual microprocessor card is carried out. After successfully passing the verification, the payer’s payment data is sent in APDU commands. To send the mentioned data on a smartphone with the MirPay mobile application, payment data extracted from the smartphone’s memory is placed in C-APDU commands: token, token expiration date, transaction counter, session key for generating a cryptogram and organizes their transfer to a dual microprocessor card. On the dual microprocessor card, C-APDU commands are received and the payer’s data is written to the memory of the dual microprocessor card. Thus, a smartphone with the MirPay mobile application writes into the memory of the dual microprocessor card the payer’s payment data necessary to complete the payment operation (transaction), that is, personalizes the dual microprocessor card. As a result, the dual microprocessor card is ready to be used, like a bank card or a tokenized bank card, as a tool for accessing the payer's account for the purposes of payment, cash withdrawal/deposit, checking account status and other known card transactions. An R-APDU response is sent from the dual microprocessor card to a smartphone with the MirPay mobile application, which makes it possible to implement the logic of the MirPay mobile application.

Next, the ATM (external system) initiates data exchange in APDU commands with a dual microprocessor card (intermediate device) via a contactless NFC interface. To do this, C-APDU commands are sent from the ATM in accordance with the protocol of the ATM core via a contactless interface. From the dual microprocessor card, in response to the received C-APDU commands, a response R-APDU is sent with the payment data of the payer and the transaction necessary to carry out the transaction.

The payer's payment data is deleted from the memory of the dual microprocessor card before sending a response to the last C-APDU command from the ATM to the dual microprocessor card. In other words, the dual microprocessor card (intermediate device) is depersonalized. This also ensures high security of the presented technology, since the mentioned payer data is available only for one payment operation (transaction) initiated by the payer.

Thus, the proposed solution makes it possible to expand the scope of application of NFC payments while maintaining their characteristics by providing the ability to transfer payment data in the existing infrastructure for receiving and processing payments in an alternative way; and also in the tested solution, an increase in the reliability of data protection and payment security is achieved, ensuring the protection of payment data from unauthorized access.

Claims (48)

1. A method for making NFC payments, in which: - establishing a contactless NFC connection between the payer's mobile device, containing at least a processor and memory, with an intermediate device containing at least a security element with a trusted execution environment and memory; - ensure the exchange of commands between the payer’s mobile device and the intermediate device, as a result of which the intermediate device receives payment data from the payer’s mobile device; - storing said payment data in the memory of the intermediate device; - establish a contactless NFC connection or contact connection between an intermediate device and an external system; - ensure the exchange of commands between the intermediate device and the external system, as a result of which payment data from the intermediate device is transferred to the external system to carry out a payment transaction, wherein C-APDU commands are sent from the payer’s mobile device to the intermediate device, the payer's mobile device receives R-APDU responses from the intermediate device, the intermediate device receives C-APDU commands from the external system, R-APDU responses are sent from the intermediate device to the external system, characterized in that before sending the response to the last command received by the intermediate device from the external system to carry out this payment transaction, the payment data located in the memory of the intermediate device is deleted. 2. The method according to claim 1, in which the payer’s mobile device, before transmitting payment data to the intermediate device, authenticates the intermediate device, and also generates a public key for transmitting payment data in encrypted form, and on the intermediate device supports the said authentication, and also performs organization secure data exchange with the payer’s mobile device. 3. The method according to claim 1, in which secure storage of the payer’s data is provided on the payer’s mobile device using at least one of: a key store, using a local database, application obfuscation. 4. The method according to claim 1, in which the intermediate device is received and serviced on the external system in a contact and/or non-contact manner. 5. The method according to claim 1, in which at least a bank card number or a token, the validity period of a bank card or token, a transaction counter, a session key for generating a cryptogram or a cryptogram are used as payment data. 6. The method according to claim 1, in which the payer's mobile device supporting NFC technology includes at least a processor and memory and is configured to sequentially - receive a command from the payer on the payer’s mobile device to initiate a payment transaction; - establish a contactless NFC connection with an intermediate device; - retrieve payment data from memory; - prepare C-APDU commands containing payment data, and send payment data to the intermediate device to personalize the latter, and receive an R-APDU response from the specified intermediate device. 7. The method according to claim 1, in which the payer’s mobile device additionally contains a security element with a trusted execution environment. 8. The method according to claim 1, in which the payer's mobile device is configured to retrieve payment data from memory, which includes at least a bank card number or token, the validity period of the bank card or token, a transaction counter, a session key for generating a cryptogram, and transmit said data in C-APDU commands to the intermediate device, and receive an R-APDU response. 9. System for making NFC payments, containing a payer's mobile device, an intermediate device and an external system, configured to establish a connection and exchange data, the payer's mobile device includes at least a processor and memory and is configured to establish a contactless NFC connection with the intermediate device to transfer payment data to the latter, the intermediate device is configured to establish an NFC connection with the payer's mobile device for receiving payment data and a contactless NFC connection or contact connection with an external system for sending payment data and contains a memory configured to store payer data received from the payer's mobile device; the external system is configured to establish a contactless NFC connection and/or contact connection with an intermediate device to receive payment data for conducting a payment transaction, wherein the payer's mobile device is configured to send C-APDU commands to the intermediate device and receive R-APDU responses from the intermediate device, the intermediate device is configured to receive C-APDU commands from the payer’s mobile device and send R-APDU responses to the payer’s mobile device, as well as the ability to receive C-APDU commands from an external system and send R-APDU responses to the external system, characterized in that the intermediate device is configured to delete payment data from its memory before sending a response to the last command received by the intermediate device from the external system to carry out a given payment transaction. 10. The system according to claim 9, in which the payer’s mobile device additionally includes a security element with a trusted execution environment. 11. The system of claim 9, wherein the intermediate device comprises a safety element and a memory. 12. The system according to claim 9, in which the external system is a device for accepting and servicing bank cards in a standard infrastructure, which is equipped with contact and/or contactless means of data input/output in card payment systems. 13. The system according to claim 9, in which the payer’s mobile device is configured to authenticate the intermediate device before transmitting payment data to the intermediate device, as well as generating a public key for transmitting payment data in encrypted form, and the intermediate device is configured to support said authentication, as well as organizing secure data exchange with the payer’s mobile device. 14. The system according to claim 9, in which the external system, intermediate device and mobile device of the payer are configured to establish communication via interaction channels for receiving and/or transmitting payment data in APDU commands containing at least a bank card number or token, validity period of a bank card or token, transaction counter. 15. The system according to claim 9, wherein the payer’s mobile device supporting NFC technology includes at least a processor and memory and is configured to sequentially - at the payer’s request, initiate a payment transaction; - establish a contactless NFC connection with an intermediate device; - retrieve payment data from memory; - prepare C-APDU commands containing payment data and send payment data to the intermediate device to personalize the latter, and receive an R-APDU response from the specified intermediate device. 16. The system according to claim 9, in which the payer’s mobile device is configured to retrieve payment data from memory, which includes at least a bank card number or token, the validity period of the bank card or token, a transaction counter, a session key for generating a cryptogram, and transmit the mentioned data in C-APDU commands to the intermediate device and receive the R-APDU response. 17. The system according to claim 9, in which the payer’s mobile device is configured to provide secure storage of the payer’s data on the payer’s mobile device using at least one of: a key store, using a local database, application obfuscation. 18. An intermediate device comprising a security element with a trusted execution environment and a memory configured to receive C-APDU commands from the payer's mobile device and from an external system and send in response to said received R-APDU response commands for the purpose of establishing a contactless NFC connection with the payer’s mobile device for data exchange; receiving payment data on the intermediate device as a result of said data exchange; storing payment data received from the payer’s mobile device in the memory of the intermediate device; establishing a contactless NFC connection or contact connection with an external system for data exchange with subsequent transfer of payment data from the intermediate device to the external system, characterized in that the intermediate device is configured to delete payment data from its memory before sending a response to the last command received by the intermediate device from the external system to carry out a given payment transaction. 19. The intermediate device according to claim 18, characterized in that it is designed to support the authentication of the intermediate device, which is carried out by the payer’s mobile device, as well as organizing secure data exchange with the payer’s mobile device. 20. The intermediate device according to claim 18, characterized in that it is configured to receive and transmit payment data to an external system, which includes at least a bank card number or token, the validity period of the bank card or token, a transaction counter and a transaction cryptogram.

Images