RU2566947C1 - System, method and computer-readable medium for performing non-cash transactions - Google Patents

Abstract

FIELD: radio engineering, communication.SUBSTANCE: method comprises the following steps: reading a transaction initiation element using an automated non-cash transaction system on a user device; extracting, by the automated non-cash transaction system, transaction data from the transaction initiation element, wherein said data contain a secure data region indicator on a transaction processing server; using the automated non-cash transaction system, adding a user device identifier to said indicator; generating a request to perform a transaction using the automated non-cash transaction system and transmitting said request to the transaction processing server via a secure data link; identifying, at the transaction processing server, a user device using said identifier in said request and extracting data from said secure region, corresponding to said indicator, sent in said request; transmitting, from the transaction processing server via a secure data link to the automated non-cash transaction system, data of the performed transaction, which contain data from the secure region of the transaction processing server; generating, by the automated non-cash transaction system, and transmitting, via a secure data link, a response to the transaction processing server containing transaction confirmation data; receiving and processing, at the transaction processing server, the response from the automated non-cash transaction system; generating a request to a bank server and transmitting said request via a secure data link; receiving and processing the request from the transaction processing server to the bank server, and sending a response to the transaction processing server, containing data on performing the transaction; transmitting, from the transaction processing server in the automated non-cash transaction system to the user device, information on the transaction and displaying the status of the transaction in the automated non-cash transaction system on the user device.EFFECT: shorter time for performing a transaction owing to access to a secure region on a transaction processing server containing data on the transaction.40 cl, 14 dwg

Description

Technical field

The present invention relates to the field of data transmission and processing, in particular to a system and method for conducting transactions in a communication network using mobile devices of users.

State of the art

There are known payment systems which use generated machine-readable codes printed on some data carrier to effect payment for goods.

One of such systems is known from document RU 2011146890 A (05/27/2013, Vladimir Viktorovich Vorobyov (RU)), which discloses a method for ordering goods (services), characterized in that through an automated public device connected to the issuer’s information center via telecommunications communication channels, the buyer is given a voucher - the right to purchase goods (services) on the basis of an offer - the specified information center contains a database of offers of goods (services), and also stores and (or) generates identification codes , the specified voucher is a print on paper, the voucher is printed by the specified device immediately at the time of its issuance, the specified device allows the buyer to familiarize themselves with the terms of the offer, as well as confirm the fact of acceptance of the offer by paying for the voucher or other action provided for by the offer, the specified voucher contains, at least an identification code and (or) a machine-readable label, while the obligation to ensure that the supplier fulfills the terms of the offer lies with the voucher issuer from the moment of acceptance of the offer by the buyer, and the supplier’s obligations to sell the goods (services) on the terms of the offer arise at the time the buyer presents the voucher.

The disadvantages of the system are its limited functionality due to the need to confirm the transaction by scanning a tangible medium - a voucher, which does not allow confirmation directly in digital form, for example, on the Internet.

Document RU 2008129933 (01/27/2010, Oleg Kuchma (RU)) discloses a cashless payment method in a telecommunications network using a special card containing a machine-readable label in the form of a QR code, while the buyer and the seller use mobile electronic communication devices to make the payment equipped with a means of reading the named machine-readable tag, while, with the consent to payment, the buyer presents the card to the representative of the seller, who reads the identification number of the card through his mobile electronic communication device, or by means of a well-equipped cash register or personal computer, or enters a visually visible token number using a computer keyboard, and then, preferably in automatic mode, forms a request for debiting funds from the cardholder’s personal account and transferring this amount to the seller’s bank account , including information about the product and the seller, necessary for making a remote payment.

This system also has limitations in the functionality of a remote transaction and provides for direct proximity with the seller’s terminal and the manufacture of special media with a machine-readable label, which is used as an additional means of transaction confirmation.

From the patent RU 127973 U1 (05/10/2013, Mobile Money Limited Liability Company (RU)), a payment system is known, which consists in generating a machine-readable label in the form of a QR code on the seller’s terminal and printing it out to provide it to the client on tangible media, which is subsequently used to scan the client device, and to carry out authentication and transaction validation procedures.

The disadvantages of this solution are completely similar to the solutions mentioned above and consist in the manufacture of a material data carrier with a machine-readable character printed on its surface to confirm the transaction and perform many sequential operations to purchase goods or services, which leads to a lengthy process of confirming payment of goods using electronic means of the user .

US 8380177 B2 (02/19/2013, Paydiant Inc.) discloses a method for conducting a transaction using a mobile device between a client and a seller, wherein the seller transmits the seller’s payment authorization message to the transaction management system to initiate the transaction process, the claimed method comprising the steps of which carry out capture (reading) by the mobile device of the settlement token (qr-code), which is presented to the buyer at the point of sale (point), transferring information to the indicated transaction management system, capturing data from the specified settlement token, receiving information associated with the transaction from the transaction management system, and transmitting to the transaction management system a client request for payment authorization containing information about the choice of the payment account to use to complete the transaction.

The known method has a fairly limited set of functions and a complex process of transaction confirmation.

There is a well-known QRPay payment system for goods and services by reading a qr code by a client device (http://www.qrpay.com/), which, using software installed on a user's device, confirms a transaction through a client account opened in PayPal .

However, this method involves the use of only one PayPal settlement system, and also works only with those resources that support payment using the said system, which significantly reduces the functionality of this method of conducting transactions.

The closest analogue of the claimed invention is a transaction method known from WO 2012112822 A2 (08/23/2012, Visa International Service Association), which consists in reading a visually displayed transaction confirmation element using a user device by fixing it using optical capture devices of the user device (camera , video camera), extracting data from the read code by the user device, sending the read data to the transaction server and confirming the transaction using the selected of user payment method.

The disadvantages of the known solution is that when it is read, the code redirects the user to the transaction server, which contains all the necessary information for its implementation, which significantly reduces the security of such data transfer.

Disclosure of invention

The task to which the claimed invention is directed is to create a simple, reliable and quick way to carry out a cashless transaction using a user device and a system for its implementation.

The technical result is to reduce the transaction time by accessing a protected area on a transaction processing server containing transaction data.

The claimed technical result is achieved due to the fact that the method of non-cash transaction using a user device is performed due to the stages in which:

- read the transaction initiation element (EIT) using an automated system of cashless transactions (ASBT) located on the user's device;

- retrieve transaction data from the EIT using the ASBT, the data referred to contain a pointer to a protected data area on the transaction processing server (COT);

- using ASBT add the identifier of the user device to the mentioned index;

- generate a request for a transaction using ASBT and transmit the aforementioned request for COT through a secure data channel;

- identify the user device on the COT using the identifier in said request and extract data from said secure area corresponding to said pointer sent in said request;

- transmit data from the COT via a secure data transmission channel to the ASBT of the ongoing transaction containing data from the protected COT area;

- generate with the help of ASBT and transmit via the secure data channel the response to the COT containing the data confirming the transaction;

- take the response from the ASBT to the COT, process the response, generate a request to the bank server (SB) and transmit it via a secure data channel;

- receive a request from COT to SB, process the request and send a response to COT containing data on the transaction;

- receive a response from the SB containing the data on the transaction to the COT and transmit information about the transaction to the ASBT on the user's device,

- and display the status of the transaction in ASBT on the user's device.

The claimed technical result is also achieved through the use of a cashless transaction system, which contains: COT, SB and a user device containing ASBT, and

- ASBT on the user's device is configured to generate a transaction request, said request being generated by reading an EIT that contains a pointer to a protected area of data on the COT containing transaction data;

- ASBT on the user device is configured to add the identifier of the user device to the indicated pointer and transmit the said request for COT via a secure data channel;

- COT is configured to identify the user device using the added identifier in the said request, retrieve data from the protected area corresponding to the pointer sent in the said request, and transmit the transaction data containing the data extracted via the secure data transmission channel to ASBT on the user device from the protected area of the COT;

- ASBT is configured to generate a response to the COT on the user’s device and transmit via a secure data channel containing transaction confirmation data;

- COT is configured to receive the response data from the user device via the secure data channel, process the response, generate a request and transmit it via the secure data channel to the SB;

- Sat, made with the possibility of receiving the aforementioned request from the COT, processing the request and sending a response to the COT containing data on the transaction;

- COT is configured to receive a response from the SB containing data on the transaction, transmitting transaction information to the ASBT on the user's device;

- ASBT is configured to receive transaction data from the COT and display the status of the transaction.

The claimed technical result is also achieved by using a computer-readable storage medium, which contains machine-readable instructions that, when executed, prompt one or more processors of the user device to perform the steps in which:

- activate ASBT;

- read the EIT using ASBT located on the user's device;

- retrieve transaction data from the EIT using the ASBT, the data referred to containing a pointer to a protected area of data on the COT;

- using ASBT add the identifier of the user device to the mentioned index;

- generate a request for a transaction using ASBT and transmit the aforementioned request for COT through a secure data channel;

- initiate a request processing at the COT, by which the user device is identified and data is extracted from the protected area of the COT corresponding to the indicated pointer sent in the said request;

- initiate the transfer of data from the COT through a secure data channel to ASBT of the data of the transaction containing data from the protected area of the COT;

- generate with the help of ASBT and transmit via the secure data channel the response to the COT containing the data confirming the transaction;

- initiate reception on the COT of the aforementioned response from ASBT, processing the aforementioned response, generating a request for the SB and its transmission via a secure data channel;

- initiate the receipt of the request from the COT to the SB, processing the request and sending a response to the COT containing data on the transaction;

- initiate the reception on the COT of a response from the SB containing data on the transaction, and the transfer to ASBT on the user's device of transaction information,

- receiving ASBT on the user device transaction data and displaying the status of the transaction on the screen of the user device.

Particular embodiments of the claimed invention will be disclosed further in the present application materials.

Brief Description of the Drawings

In FIG. 1 shows the steps of a transaction method.

In FIG. 2 - 8 depict the ASBT functionality.

In FIG. 9-10 illustrate the process of reading an EIT by a user device.

In FIG. 11 shows the process of exchanging ASBT data with COT.

In FIG. 12 depicts a successfully completed transaction ASBT.

In FIG. 13 is a schematic view of a cashless transaction system.

In FIG. 14 is a schematic view of a user device.

The implementation of the invention

Transaction Method

In a preferred embodiment of the claimed invention, according to FIG. 1, when implementing method (100) of a cashless transaction using a user device, in step (101), an ASBT is activated, which allows the reading of an EIT. ASBT is a combination of software running on a user device. ASBT contains a user interface that provides control of the transaction process. EIT can be located on any data carrier, without limitation, such as a signboard, website, electronic device screen, magazine, booklet, etc. An EIT in a preferred embodiment is a computer-readable graphic code, however, in the particular embodiment described later, it can also be an HTML link.

At step (102), the ASBT after reading the EIT extracts transaction data from it, which contains a pointer containing information about the protected data area located on the COT. The mentioned area contains the necessary set of information for conducting a transaction, for example, data of the seller of goods, indicators of bank accounts of the seller (seller, COT), etc. The mentioned area contains data protection, for example encryption (128 bits, 256 bits, etc.), or https (HyperText Transfer Protocol Secure), or SSH.

In step (103), the ASBT adds a user device identifier to the indicated index. The pointer, as a rule, is a link (HTML link), which, when it is read from the EIT, is supplemented by the identifier of the user device. The user device identifier may include, but is not limited to: MAC (Media Access Control) - address, IP (Internet Protocol) - address, IMEI (International Mobile Equipment Identity), IMEISV (International Mobile Terminal Identity & Software Version number), PIN code , transaction confirmation code sent to ASBT by SMS. The identifier may be stored in the ASBT and / or COT memory.

At step (104), ASBT generates a transaction request and transfers it to the COT through a secure data channel. As a rule, in the preferred embodiment, the data channel is protected using SSH (Secure Shell), for the secure transmission of information via wired or wireless data networks such as the Internet, WLAN, WAN, LAN, WiMax, etc. SSH tunneling of data transmission channels is widely known in the art and is widely used to protect private information in transactions.

At step (105), the user device is identified from the ASBT to the COT. A COT after receiving a request from ACBT generated at step (104), extracts pointer data from it to access the desired protected area on the COT containing transaction data and a user device identifier confirming the authentication process of the user device on the COT. The mentioned data area on COT, as mentioned above, contains all the necessary list of data for the implementation of the transaction process. When activating ASBT on his device, the user goes through the registration process on COT, in which the user using ASBT enters data that will be used in the transaction process, for example, data of the ASBT owner (name, phone number, e-mail, etc.), device type, shipping address, etc. Data for payment of goods is also entered into ASBT (payment card number, settlement account number, etc.), however, this data is stored only on the SB, and ASBT uses pointers to the SB, which can be stored both in ASBT and in the protected area COT. The information entered by the user in the ASBT is used to identify the ASBT of the user device when the protected data area of the COT is accessed during the transaction. A more detailed process of registering a user device on a COT will be presented later.

At step (106), the processed request is sent back to the ASBT to the user device for further confirmation. The response to the processed request is displayed on the user's device and contains data about the subject of the transaction, such as, for example, the name of the subject of the transaction, its cost, the name of the seller’s resource, etc. The mentioned data is extracted from the protected area on the COT, which is accessed in the request from ASBT. Using ASBT, the transaction is confirmed (or rejected) on the user's device by activating the corresponding option in the ASBT interface.

At step (107), ASBT, in response to the activation of the option confirming the transaction, transmits a response to the COT containing information about the consent of the ASBT user to further the transaction. If the ASBT user refuses the transaction, the process stops.

At step (108), the COT receives a response from the ASBT generated at step (107) and generates a request to the SB for the process of payment for the subject of the transaction. The said request contains at least data, such as the price of the subject of the transaction and the account number of the ASBT user or credit card number, etc. The aforementioned request from the COT is transmitted via a secure data channel to the SB.

At step (109), the SB receives a request from the COT and processes it. In accordance with the identification data (account or card number of the ASBT user) received in the request from COT, the SB checks the availability of the required amount in the current account of the ASBT user and transfers money from the said SB account to the COT account. When transferring funds from the Security Council to the COT, a response is generated containing data confirming that the funds were debited and confirming the validity of the transaction. Data is transmitted over a secure data channel.

At step (110), the COT receives a response from the SB, which contains data about the transaction and transmits information about the completion of the transaction to the ASBT on the user's device. Data is transmitted via a secure data channel.

At step (111), the ASBT receives the transaction data from the COT and displays the transaction status on the screen of the user device.

In a private embodiment of the claimed invention, the claimed transaction method can be performed after the generation of EIT. EIT can be generated on the seller’s resource or on the seller’s device to perform a cashless transaction.

EIT can be a machine-readable graphic code, which can be a linear or two-dimensional code, or an HTML link. A machine-readable linear code is selected from the group: Codabar, Code 11, Code 128 with subsets A / B / C and UCC, Code 39, Code 93, EAN-13, EAN-8, Industrial 2-of-5, Interleaved 2-of- 5, Logmars, MSI, Planet Code, Plessey, Postnet, RSS (reduced space symbology). Standard 2-of-5, UPC and EAN 2 or 5 digit extensions, UPC-A, UPC-E. A two-dimensional machine-readable code is selected from the group: Aztec, Codablock, Code 49, Data Matrix, MaxiCode, QR Code, PDF417, MicroPDF417, RSS / GS1 DataBar family.

In a private embodiment of the claimed invention, after the transaction data is extracted from the protected area of the COT, a request is generated to the seller’s server (SP), which is sent via the secure data channel and may contain data such as the name of the goods and / or characteristics of the goods and / or the balance of the goods at the time of the request and / or the price of the goods at the time of the request. The joint venture processes the received request from COT and generates a response containing data, such as the name of the product, and / or characteristics of the product, and / or the balance of the product at the time of the request and / or the price of the product at the time of the request. This step is taken to update the information, such as, for example, changing the price of the subject of the transaction, the availability of the required quantity, updating the specification of the subject of the transaction, etc.

ASBT User Registration Process

In FIG. Figure 2 shows the first launch of ASBT (2000) on a user's device (200), which is a smartphone or tablet running Apple iOS or Android or Windows Phone. At the first start of ASBT (2000), the user is asked to indicate the phone number in a special field (2001), which will be used to confirm the transactions. After entering the telephone number of the ASBT user (2000), a data packet is generated that generates a request for COT (300) to register a new ASBT user (2000). In response to the received request, COT (300) generates a reverse request to ASBT (2000) containing the generated code necessary to confirm the registration of a new user of ASBT (2000). The ASBT (2000) interface displays the field (2002) intended for entering the confirmation code received by ASBT (2000) from the COT (300). The confirmation code from COT (300) is sent to ASBT (2000) as an SMS message.

According to FIG. 3 ASBT (2000) after entering the confirmation code, prompts the user to set a PIN code, which is entered in the interface field (2003), which will be used to enter ASBT (2000), and can also be used to authenticate transactions made using ASBT (2000).

In FIG. Figure 4 shows the ASBT section (2000) on the user's device (200) after the successful registration of a new user, the results of which give a status message on the screen of the user device (200). The user can initiate the creation of his profile and carry out the binding of a bank card by activating the card binding area (2004), or skip this step by activating the area (2005) to complete the user's account balance later.

The user profile stores the necessary information for identification during transactions, such as phone number, payment account numbers, payment cards, etc.

In FIG. 5 shows a section of the ASBT interface (2000) for linking a bank card. Fields (2006) are intended to fill in the identification information of the ASBT user bank card (2000). Field (2007) is intended for setting a limit on the total amount of transactions on a card. The user can specify in the field (2007) a parameter that will determine the threshold for the amount of payment transferred from the card. Field (2008) is intended for setting the limit parameter for transaction amounts for a certain period of time - day, day, month, etc. Region (2009) is intended to confirm the entered identification data of the ASBT user bank card (2000).

In accordance with FIG. 6 after activating the area (2009) that confirms the entered data on the ASBT (2000) user card, ASBT (2000) generates a request to the SB (400) to verify the previously entered data in the fields (2006). ASBT (2000) sends the request via a secure data channel to SB (400), which, in turn, checks the data, generates a response and sends it back to ASBT (2000). After receiving a response from SB (400) ASBT (2000) displays the status of the verification of a bank card on the user's device screen.

In FIG. Figure 7 shows the ASBT section (2000), which implements functions for managing a user's wallet. The region (2010) contains information about the phone number used on the device (200), and the amount of funds in the user's account of the mentioned number. The region (2011) contains data on bank cards of the ASBT user (2000) tied to it. Using the option to add cards (2012), the ASBT user (2000) can add new cards. The menu area (2012) contains information sections for navigating through ASBT (2000). Region (2014), when activated by the user, interacts with the camera of the device (200) and puts the ASBT (2000) into the EIT reading mode. The ASBT (2000) user can assign a card to pay for the transaction, which will be used by default, and the ASBT (2000) can carry out the separation of funds on the cards during the transaction, in the case when, for example, there is not enough money on the priority card and there is the possibility of holding funds from another card linked to ASBT (2000), or a current account.

ASBT (2000) provides access to data on completed transactions, in particular, to the history of transactions and the status of orders. These data are stored in the ASBT database (2000). The indicated data can also be stored on COT (300).

In FIG. 8 shows the ASBT section (2000), which contains data on the user of the device (200), in particular, data that contains data on the delivery address of goods and other contact information. The ASBT user (2000) can change the data on the order of goods at any time. The mentioned data is stored in ASBT (2000) and is automatically used when confirming transactions when generating a data packet that is sent to the seller’s server (SP).

EIT reading process

In FIG. Figures 9 and 10 show the process of reading an EIT (3001) by a user device (200) with ASBT (2000). The seller’s resource (3000) associated with the seller’s server (500) contains an EIT (3001) located on it, which can be generated in advance and generated directly for payment using ASBT (2000). ASBT (2000) on the user's device (200) when activating the reading mode EIT (3001) displays on the screen of the device (200) the area for capturing graphic data (2017). EIT (3001) can be read automatically when it is detected by the mentioned area (2017), or the user can interact with the screen of the device (200) and read EIT (3001) in manual mode. When reading the EIT (3001) from the seller’s resource (3000) associated with the seller’s server (500), information from the EIT (3001) is retrieved and generates a request for COT (300), which contains a pointer to the protected data area of COT (300), to to which ASBT (2000) adds the identifier of the user device (200). The mentioned area of SOT (300) contains data on the subject of the transaction, which are transmitted in the response ASBT (2000). Information about the order is displayed by ASBT (2000) on the screen of the user's device (200) along with the area (2016) that activates the function of confirming the process of transaction execution.

In FIG. 11 shows the exchange of ASBT (2000) data with COT (300). After COT (300) receives data confirming the transaction, a request is generated to SB (400) to validate the debit from the user account of ASBT (2000). SB (400) receives a request from COT (300), carries out the withdrawal of the required amount from the client account - user ASBT (2000) and sends a response data packet to COT (300). Funds are transferred to the current account of COT (300). Subsequently, COT (300) transfers the necessary amount for the transaction to the settlement account of the seller’s server (SP) (500).

In FIG. 12 shows the status of a successful transaction. COT (300), after confirming the transfer of funds to the current account, sends to ASBT (2000) data confirming the transaction. ASBT (2000) displays the status of the transaction on the screen of the user device (200). By activating the area (2018) of the ASBT (2000) interface, the user can return to the main ASBT (2000) menu.

In a private embodiment of the claimed invention, in the absence of a connection to a data network - the Internet, ASBT (2000) on a user device (200) after reading an EIT (3001) stores it in the ASBT memory buffer (2000) for subsequent transaction processing. When the ASBT (2000) connection is restored, the buffer area is scanned, which stores the previously read EIT (3001), for which there was no transaction process initiation, and displays on the user device (200) message that the ASBT (2000) contains transaction objects by which their processing can be performed.

ASBT (2000), upon establishing a connection, retrieves the pointer from the EIT (3001) and sends a request to the COT to retrieve data from the protected area in accordance with the EIT pointer (3001). Then ASBT (2000) provides the user with a list of transactions containing information about the subject of transactions and their value. The ASBT user (2000) can initiate the execution of the selected transaction or refusal of processing. If a transaction is refused, information about it is deleted from the ASBT (2000) memory.

System

In FIG. 13 is a schematic view of a cashless transaction system (600) using a user device (200). The system of cashless transactions (600) includes a user device (200) with ASBT (2000), COT (300), SB (400), SP (500), seller’s resource (3000) and data transmission network (610). The operations performed by the functional elements of the system were described in detail above in the present application materials.

The system is characterized by the following. ASBT (2000) on the user's device (200) generates a transaction request, the request being generated by reading an EIT (3000), which contains a pointer to a protected data area on COT (300) containing transaction data. ASBT (2000) adds a user device identifier (200) to the indicated index and transmits a request for COT (300) via the secure data channel, the request containing a pointer to the protected area and the added user device identifier. COT (300) identifies the user device (200) using the added identifier in the above request, extracts data from the protected area corresponding to the pointer sent earlier in the request, and transmits via the secure data channel to ASBT (2000) on the user device (200) transaction data that contains data extracted from the protected area of the COT (300). ASBT (2000) generates a response to the COT (300) containing data confirming the transaction through a secure data channel. COT (300) receives a response on a secure data channel from a user device (200), processes it, generates a request and transmits it on a secure data channel to SB (400). SB (400) receives the aforementioned request from COT (300), processes it and sends a response to COT (300) containing data on the transaction. COT (300) receives a response from SB (400) containing data on the transaction, and transmits transaction information to ASBT (2000) on the user's device (200). ASBT (2000) receives transaction data from COT (300) and displays the transaction status on the screen of the user device (200).

The seller’s resource (3000) can be any suitable storage medium on which an EIT (3000) can be presented for reading, for example, a magazine, signboard, electronic device screen, website, etc. As a rule, a seller’s resource (3000), presented as a web resource, or a terminal for interactive product selection, containing EIT (3001), is connected directly to the joint venture (500). COT (300) can immediately transfer funds from its current account to the settlement account of SP (500).

Each of the servers can be, but is not limited to: one or more computers based on an IBM-PC stationary or portable type (laptop), mainframe, supercomputer, cluster, etc. The devices presented in this system (600) communicate with each other, preferably using an Internet connection via TCP / IP. In private embodiments, various gateways, routers, switches, and other types of network equipment designed to receive / transmit signals between system objects (600) can be included in the system.

It should also be noted that any computing device or set of devices, regardless of its (their) purpose, mentioned in this application may contain one or more processors, means for writing / reading information from external data storage devices, such as 3.5 ″ or 5, 25 ″ FDD drive, CD-ROM, DVD-ROM, Blue-Ray, USB 2.0 or 3.0 interface, memory card slot types - SD, Micro-SD, Mini-SD, Memory Stick, MMC, etc .; the ability to connect one or more information display devices (monitor, projector), any type of RAM (SRAM, DRAM, PRAM) and data input / output modules (I / O), contain a touch type of interaction input (resistive display, capacitive display), contain means for photo and / or video recording of data, means for projecting images on physical surfaces, various options for manipulators for interacting with said devices, etc.

In FIG. 14 is a schematic view of a user device (200). A user device comprises a processor unit (2100) containing one or more processors, a memory (2200), input / output (I / O) modules, a display (2300), a data transmit / receive unit (2400), interconnected via a data bus (2500).

The invention is also carried out using a computer-readable storage medium that contains machine-readable instructions that, when executed, cause one or more processors of a user device (200) to perform the steps of activating ASBT (2000), reading EIT (3001) using ASBT (2000) ) located on the user's device (200), extracting transaction data from the EIT using ASBT (2000), the data mentioned contain a pointer to the protected data area on COT (300), using ASBT (2000) adding to the above the user device identifier (200), generating a transaction request using ASBT (2000), and transmitting the said request to the COT (300) via a secure data channel, initiating the processing of the request by COT (300), which identifies the user device ( 200) and extracting data from the said protected area of COT (300) corresponding to the indicated pointer sent in the said request, initiating the transfer from the COT (300) via the secure data transmission channel to ASBT (2000) of transaction data containing data from the protected area of the COT (300), generation via ASBT (2000) and transmission of the response data to the COT (300) containing data confirming the transaction through the secure channel, initiating the receipt of the response from the ASBT (2000) from the ASBT (2000) processing the said response, generating a request to the SB (400) and transmitting it over the secure data channel, initiating the receipt of the request from the SOT (300) to the SB (400), processing the request and sending a response to the SOT (300) containing the implementation data transactions, the initiation of receiving a response on COT (300) about t SB (400) containing data on the transaction and transmitting transaction information to ASBT (2000) on the user device, receiving ASBT (2000) on the user device of the transaction data and displaying the transaction status on the screen of the user device (200).

The information provided in this application regarding certain hardware capabilities and options for possible devices does not claim any independent legal claims as significant differences of the claimed invention, but is given only on the basis of the possibilities of carrying out the claimed invention using a wide range of technical means known today and suitable for the implementation of certain functions associated with their technical aspects with the present invention, which should be Obvious to those skilled in the art.

The present description of the implementation of the claimed invention demonstrates only its private options for implementation and should not serve to limit the options for implementing the claimed invention, since alternative options for its implementation, not beyond the scope of information disclosure in this application, should be obvious to specialists in this field of technology having the usual qualifications for which the stated solution is designed.

Claims (40)

1. A method of non-cash transaction using a user device, comprising stages in which:
- read the transaction initiation element (EIT) using an automated system of cashless transactions (ASBT) located on the user's device;
- retrieve transaction data from the EIT using the ASBT, the data referred to contain a pointer to a protected data area on the transaction processing server (COT);
- using ASBT add the identifier of the user device to the mentioned index;
- generate a request for a transaction using ASBT and transmit the aforementioned request for COT through a secure data channel;
- identify the user device on the COT using the identifier in said request and extract data from said secure area corresponding to said pointer sent in said request;
- transmit data from the COT via a secure data transmission channel to the ASBT of the ongoing transaction containing data from the protected COT area;
- generate with the help of ASBT and transmit via the secure data channel the response to the COT containing the data confirming the transaction;
- take the response from the ASBT to the COT, process the response, generate a request to the bank server (SB) and transmit it via a secure data channel;
- receive a request from COT to SB, process the request and send a response to COT containing data on the transaction;
- receive a response from the SB containing the data on the transaction to the COT and transmit information about the transaction to the ASBT on the user's device,
- receive transaction data in ASBT on the user's device and display the status of the transaction. 2. The method according to p. 1, characterized in that it further comprises the step of generating an EIT. 3. The method according to p. 1, characterized in that the EIT is selected from the group: linear computer-readable code, two-dimensional computer-readable code or HTML link. 4. The method according to p. 3, characterized in that the linear machine-readable code is selected from the group: Codabar, Code 11, Code 128 with subsets A / B / C and UCC, Code 39, Code 93, EAN-13, EAN-8, Industrial 2-of-5, Interleaved 2-of-5, Logmars, MSI, Planet Code, Plessey, Postnet, RSS (reduced space symbology), Standard 2-of-5, UPC and EAN 2 or 5 digit extensions, UPC- A, UPC-E. 5. The method according to p. 3, characterized in that the two-dimensional machine-readable code is selected from the group: Aztec, Codablock, Code 49, Data Matrix, MaxiCode, QR Code, PDF417, MicroPDF417, RSS / GS1 DataBar family. 6. The method according to p. 1, characterized in that it further performs the step of registering the user device in ASBT. 7. The method according to p. 6, characterized in that during registration generate a user profile containing at least one user’s bank card or account number. 8. The method according to p. 1, characterized in that the secure data channel is SSH (Secure Shell) or HTTPS secure channel. 9. The method according to p. 1, characterized in that the ASBT reads the EIT using the camera of the user device. 10. The method according to p. 9, characterized in that the request is generated automatically when it detects the EMF ASBT on the user's device. 11. The method according to p. 1, characterized in that the pointer is an HTML hyperlink. 12. The method according to p. 1, characterized in that the ASBT contains a database in which the transaction history is stored. 13. The method according to p. 6, characterized in that the user device is registered by means of ASBT on the COT. 14. The method according to p. 13, characterized in that when registering the device on the COT, the device identifier is stored. 15. The method according to p. 1, characterized in that the data located in the protected area on the COT, contain at least the name of the subject of the transaction and its price. 16. The method according to p. 6, characterized in that it further comprises the step of confirming the user device by transmitting from COT a unique code to the user device. 17. The method according to p. 16, characterized in that the unique code is entered by the device user in ASBT. 18. The method according to p. 6, characterized in that the user additionally generates a PIN access code to ASBT. 19. The method according to p. 18, characterized in that said access code is requested by ASBT at each transaction confirmation on the user's device. 20. The method according to p. 1, characterized in that to confirm the transaction, the SB generates a unique code and sends it to the user's device. 21. The method according to p. 20, characterized in that the said code is sent and entered into ASBT. 22. The method according to p. 21, characterized in that the confirmation code is sent via SMS or e-mail. 23. The method according to p. 1, characterized in that it further comprises a step in which the COT after the step of extracting transaction data from the protected area generates a request to the seller’s server (SP). 24. The method according to p. 23, wherein the joint venture, after receiving the request from the COT, processes the request and sends a response to the COT containing transaction data. 25. The method according to any one of paragraphs. 23, 24, characterized in that the transaction data contains the name of the goods, and / or characteristics of the goods, and / or the balance of the goods at the time of the request, and / or the price of the goods at the time of the request. 26. A system for conducting a cashless transaction containing COT, SB and a user device containing ASBT, and
- ASBT on the user's device is configured to generate a transaction request, said request being generated by reading an EIT that contains a pointer to a protected area of data on the COT containing transaction data;
- ASBT on the user device is configured to add the identifier of the user device to the indicated pointer and transmit the said request for COT via a secure data channel;
- COT is configured to identify the user device using the added identifier in the said request, retrieve data from the protected area corresponding to the pointer sent in the said request, and transmit the transaction data containing the data extracted via the secure data transmission channel to ASBT on the user device from the protected area of the COT;
- ASBT is configured to generate a response to the COT on the user’s device and transmit via a secure data channel containing transaction confirmation data;
- COT is configured to receive the response data from the user device via the secure data channel, process the response, generate a request and transmit it via the secure data channel to the SB;
- Sat, made with the possibility of receiving the aforementioned request from the COT, processing the request and sending a response to the COT containing data on the transaction;
- COT is configured to receive a response from the SB containing data on the transaction, transmitting transaction information to the ASBT on the user's device;
- ASBT is configured to receive transaction data from the COT and display the status of the transaction. 27. The system according to p. 26, characterized in that it further comprises a seller’s resource containing EIT. 28. The system of claim 27, wherein the seller’s resource is associated with a joint venture. 29. The system of claim 26, wherein the EIT is selected from the group: a linear computer-readable code, a two-dimensional computer-readable code, or an HTML link. 30. The system of claim 29, wherein the linear machine-readable code is selected from the group: Codabar, Code 11, Code 128 with subsets A / B / C and UCC, Code 39, Code 93, EAN-13, EAN-8, Industrial 2-of-5, Interleaved 2-of-5, Logmars, MSI, Planet Code, Plessey, Postnet, RSS (reduced space symbology). Standard 2-of-5, UPC and EAN 2 or 5 digit extensions, UPC-A, UPC-E. 31. The system of claim 29, wherein the two-dimensional machine-readable code is selected from the group: Aztec, Codablock, Code 49, Data Matrix, MaxiCode, QR Code, PDF417, MicroPDF417, RSS / GS1 DataBar family. 32. The system according to p. 26, characterized in that the ASBT additionally performs the step of registering a user device when it is activated. 33. The system of claim 32, wherein said registration generates a user profile containing at least information about a device user, at least one user bank card or current account number and at least one address delivery of goods. 34. The system of claim 26, wherein the secure data channel is SSH (Secure Shell) or HTTPS secure channel. 35. The system according to p. 26, characterized in that the reading of the EIT ASBT is carried out using the camera of the user device. 36. The system according to p. 26, characterized in that the ASBT contains a database in which the transaction history is stored. 37. The system according to p. 26, characterized in that the user's device is registered by means of ASBT on the COT. 38. The system according to p. 37, characterized in that when registering the device on the COT and ASBT, the device identifier is stored. 39. The system according to p. 26, characterized in that the data located in the protected area on the COT, contain at least information about the product. 40. A computer-readable storage medium comprising computer-readable instructions that, when executed, cause one or more processors of a user device to perform the steps of:
- activate ASBT;
- read the EIT using ASBT located on the user's device;
- retrieve transaction data from the EIT using the ASBT, the data referred to containing a pointer to a protected area of data on the COT;
- using ASBT add the identifier of the user device to the mentioned index;
- generate a request for a transaction using ASBT and transmit the aforementioned request for COT through a secure data channel;
- initiate a request processing at the COT, by which the user device is identified and data is extracted from the protected area of the COT corresponding to the indicated pointer sent in the said request;
- initiate the transfer of data from the COT through a secure data channel to ASBT of the data of the transaction containing data from the protected area of the COT;
- generate with the help of ASBT and transmit via the secure data channel the response to the COT containing the data confirming the transaction;
- initiate reception on the COT of the aforementioned response from ASBT, processing the aforementioned response, generating a request for the SB and its transmission via a secure data channel;
- initiate the receipt of the request from the COT to the SB, processing the request and sending a response to the COT containing data on the transaction;
- initiate the reception on the COT of a response from the SB containing data on the transaction, and the transfer to ASBT on the user's device of transaction information,
- receiving ASBT on the user device transaction data and displaying the status of the transaction on the screen of the user device.

Images