KR20230021549A - Method and appartus for supproting transactions of commodites - Google Patents

Abstract

Provided are a method and apparatus for supporting transactions of products to easily trade products without face-to-face contact. According to one embodiment of the present invention, the method for supporting transactions of products comprises the steps of, by a second terminal: receiving information on a seller selling a product from a first terminal; requesting verification of the seller's information to a server; in response to successful verification of the seller's information, acquiring a transaction identifier for the product from the server; measuring the distance from the first terminal; generating transaction data including the measured distance and the transaction identifier; requesting verification of the transaction data to the server; and in response to receiving a message from the server indicating successful verification of the transaction data, performing a payment routine for the product.

Description

Commodity transaction support method and device {METHOD AND APPARTUS FOR SUPPROTING TRANSACTIONS OF COMMODITES}

The present invention relates to a product transaction support method. More specifically, it relates to a product transaction support method and apparatus for verifying a product transaction based on a distance between a buyer and a seller.

In addition to the payment method using a real credit card, various payment methods are being used. For example, a payment method through scanning a QR (Quick Response) code, a payment method through short-range communication such as Magnetic Secure Transmission (MST) or Near Field Communication (NFC), etc. are being used.

However, the payment method using the QR code shooting has inconvenience in that the user has to shoot the QR code through a camera. In addition, the payment method through QR code shooting is accompanied by the inconvenience of having to directly input the purchase amount by the buyer.

In addition, the MST or NFC-based payment method requires close contact between terminals, and unnecessary contact, such as a buyer having to transfer his terminal to a seller for transaction authentication, may occur. In addition, a seller with malicious intent may attempt to hack the buyer's terminal when performing MST or NFC-based payment.

Therefore, there is a demand for a simple payment method while enhancing security.

Korean Patent Registration No. 10-1996798 (2019.06.29)

The technical problem to be solved by the present invention is to provide a transaction support method and apparatus that can conveniently trade products without face-to-face contact.

Another technical problem to be solved by the present invention is to provide a transaction support method and apparatus capable of blocking external hacking in a data exchange process between terminals.

Another technical problem to be solved by the present invention is to provide a transaction support method and apparatus capable of preventing deception occurring in a transaction process by authenticating a buyer and a seller of a product.

Another technical problem to be solved by the present invention is to provide a transaction support method and apparatus that allows a transaction to be concluded when a seller and a buyer are located within a predetermined distance.

The technical problems of the present invention are not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art from the description below.

A product transaction support method according to an embodiment for solving the technical problem includes receiving, by a second terminal, information of a seller selling a product from a first terminal, and, by the second terminal, information of the seller. requesting verification to the server; obtaining, by the second terminal, a transaction identifier for the product from the server in response to the successful verification of the seller's information; , measuring a distance to the first terminal, generating, by the second terminal, transaction data including the measured distance and the transaction identifier; Requesting verification to the server, and performing, by the second terminal, a payment routine for the product in response to receiving a message indicating the success of verification of the transaction data from the server. can

In one embodiment, the generating of the transaction data may include performing, by the second terminal, user authentication in response to the measured distance being within a threshold distance, and performing, by the second terminal, the user authentication. In response to succeeding, it may include generating the transaction data.

In one embodiment, the step of performing the payment routine for the product, in response to a distance included in the transaction data within a threshold distance and a transaction identifier included in the transaction data matching a pre-stored transaction identifier, the and receiving a message indicating success of the transaction data from the server.

In one embodiment, the information on the seller includes an electronic signature generated based on a first token assigned to the first terminal and a private key of the first terminal, and verification of the seller's information is performed by the server. The requesting may include requesting verification of the electronic signature to the server.

A product transaction support method according to another embodiment for solving the technical problem includes transmitting, by a first terminal, information on a product on sale to a second terminal, and the first terminal from the second terminal. Receiving a purchase request for the product; Forming, by the first terminal, a radio channel for distance measurement with the second terminal; Receiving a token from the second terminal, and generating, by the first terminal, transaction data including a distance between the first terminal and the second terminal measured through a signal of the radio channel and the second token and requesting, by the first terminal, verification of the transaction data to a server.

In another embodiment, in response to the fact that the distance included in the transaction data is within a threshold distance and the second token matches the token allocated to the second terminal, a payment routine for the product may proceed.

In another embodiment, the product transaction support method may further include acquiring, by the first terminal, a transaction identifier for the product before generating the transaction data, and generating the transaction data. The doing may include generating, by the first terminal, the transaction data further including the transaction identifier, and encrypting the generated transaction data with a private key of the first terminal.

In another embodiment, the receiving of the second token from the second terminal may include receiving, by the first terminal, the encrypted second token and the distance from the second terminal through the wireless channel; - the distance is measured by the second terminal based on the signal of the radio channel -, decrypting, by the first terminal, the distance with the encrypted second token using the transaction identifier as a decryption key can include

A computing device according to another embodiment for solving the technical problem includes one or more processors, a memory for loading a computer program executed by the processor, and a storage for storing the computer program, The computer program includes an operation of receiving information of a seller selling a product from a first terminal, an operation of requesting verification of the information of the seller to a server, and in response to successful verification of the information of the seller, the An operation of obtaining a transaction identifier for a product from the server, an operation of measuring a distance to the first terminal, an operation of generating transaction data including the measured distance and the transaction identifier, Instructions for performing an operation of requesting verification to the server and an operation of performing a payment routine for the product in response to receiving a message indicating the success of verification of the transaction data from the server ) may be included.

According to another embodiment for solving the above technical problem, a computer-readable non-transitory recording medium containing instructions, when the instructions are executed by a processor, causes the processor to store information about a product on sale as a second Transmitting to a terminal; receiving a purchase request for the product from the second terminal; forming a radio channel for distance measurement with the second terminal; Receiving a token from the second terminal, generating transaction data including a distance between the second terminals measured through a signal of the radio channel and the second token, and verifying the transaction data It may include making a request to the server.

1 is a diagram illustrating a product transaction support system according to an embodiment of the present invention.
2 is a signal flow diagram illustrating a method of registering a user according to another embodiment of the present invention.
3 is a signal flow diagram illustrating a method for verifying seller information according to another embodiment of the present invention.
4A and 4B are signal flow diagrams for explaining a method of verifying transaction data according to another embodiment of the present invention.
5 is a diagram illustrating a user interface displayed in a purchaser terminal.
6 and 7 are signal flow diagrams for explaining a payment routine performed when transaction data is successful.
8 is an exemplary hardware configuration diagram in which a computing device may be implemented in various embodiments of the present invention.

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. Advantages and features of the present invention, and methods of achieving them, will become clear with reference to the detailed description of the following embodiments taken in conjunction with the accompanying drawings. However, the technical idea of the present invention is not limited to the following embodiments and can be implemented in various different forms, only the following embodiments complete the technical idea of the present invention, and in the technical field to which the present invention belongs It is provided to fully inform those skilled in the art of the scope of the present invention, and the technical spirit of the present invention is only defined by the scope of the claims.

In adding reference numerals to components of each drawing, it should be noted that the same components have the same numerals as much as possible even if they are displayed on different drawings. In addition, in describing the present invention, if it is determined that a detailed description of a related known configuration or function may obscure the gist of the present invention, the detailed description will be omitted.

Unless otherwise defined, all terms (including technical and scientific terms) used in this specification may be used in a meaning commonly understood by those of ordinary skill in the art to which the present invention belongs. In addition, terms defined in commonly used dictionaries are not interpreted ideally or excessively unless explicitly specifically defined. Terminology used herein is for describing the embodiments and is not intended to limit the present invention. In this specification, singular forms also include plural forms unless specifically stated otherwise in a phrase.

In addition, in describing the components of the present invention, terms such as first, second, A, B, (a), and (b) may be used. These terms are only used to distinguish the component from other components, and the nature, order, or order of the corresponding component is not limited by the term. When an element is described as being “connected,” “coupled to,” or “connected” to another element, that element is directly connected or connectable to the other element, but there is another element between the elements. It will be understood that elements may be “connected”, “coupled” or “connected”.

As used herein, "comprises" and/or "comprising" means that a stated component, step, operation, and/or element is the presence of one or more other components, steps, operations, and/or elements. or do not rule out additions.

Hereinafter, some embodiments of the present invention will be described with reference to the drawings.

1 is a diagram illustrating a product transaction support system according to an embodiment of the present invention.

As shown in FIG. 1, the service cost calculation system according to this embodiment includes an authentication server 30, a credit card server 40, a VAN server 50, a PG 60, a first terminal 10 and A second terminal 20 may be included.

The credit card server 40 may be a server managed by a credit card company. The credit card server 40 may authenticate whether the credit card requested for payment is a usable card. Also, the credit card server 40 may issue a payment token for credit card payment. The payment token may be a one-time token, and may be generated each time a payment is requested. The credit card server 40 may interwork with one or more of the authentication server 30, the VAN server 50, and the PG 60 to process the purchase amount.

A value added network (VAN) server 50 may be a payment relay server for relaying payment between an affiliated store and the credit card server 40 . The VAN server 50 may perform a routine for processing a payment for a purchase amount in association with one or more of the PG 60 and the credit card server 40 .

The PG (Payment Gateway) 60 may be a device that acts as a payment agent for a financial institution (eg, a credit card company server). The PG 60 may perform a routine for paying the purchase price in association with one or more of the credit card server 40 and the VAN server 50 . The PG 60 may process online payment generated in an online shopping mall or the like.

The authentication server 30 may be a computing device for authenticating a user and verifying transaction data when a product transaction is performed between the first terminal 10 and the second terminal 20 . The authentication server 30 may store subscriber information for which a member has been registered. The subscriber information may include a user name, e-mail address, user address, phone number, and the like. The authentication server 30 may generate a transaction identifier based on product transaction, and may perform verification of transaction data received from the first terminal 10 or the second terminal 20 .

The first terminal 10 and the second terminal 20 may be capable of wireless communication with each other. The first terminal 10 may be a terminal possessed by the seller, and the second terminal 20 may be a terminal possessed by the buyer. The first terminal 10 may be a Point Of Sale (POS) terminal installed in a store or a communication device capable of mobile communication such as a smart phone. The second terminal 20 may be a communication device capable of communicating while moving.

Each of the first terminal 10 and the second terminal 20 may include a plurality of communication modules supporting different protocols. For example, each of the first terminal 10 and the second terminal 20 may include two or more communication modules among a Bluetooth communication module, a Wi-Fi communication module, and an Ultra Wideband (UWB) communication module.

The first terminal 10 transmits seller information and a list of products on sale to the second terminal 20 , and the second terminal 20 may proceed with purchasing any one of the product lists.

The first terminal 10 and the second terminal 20 may exchange data with each other, generate transaction data necessary for a transaction, and request verification of the generated transaction data to the authentication server 30 . In response to the authentication server 30 successfully verifying the transaction data, at least one of the first terminal 10 and the second terminal 20 may perform a routine for product payment.

In one embodiment, the first terminal 10 and the second terminal 20 form a radio channel for distance measurement, and the first terminal 10 and the second terminal based on a signal generated through the radio channel The distance between (20) can be measured. The first terminal 10 or the second terminal 20 may transmit transaction data including the measured distance to the authentication server 30 .

Hereinafter, a product transaction support method according to an embodiment of the present invention will be described with reference to FIGS. 2 to 7 .

First, referring to FIG. 2 , a method for registering a seller and a buyer in the authentication server 30 will be described.

In the embodiments to be described below, it is assumed that the first user is a seller and the second user is a buyer.

In step S101 , the first terminal 10 may transmit a first user registration request including an identifier (eg, login ID) of the first user to the authentication server 30 . In one embodiment, when receiving a registration request from a first user, the authentication server 30 transmits seller information including seller name, business name, location, and identifier of the first terminal 10 to the first terminal 10. can be received and stored.

Subsequently, in step S103 , the authentication server 30 may generate a first token to be allocated to the first terminal 10 . In one embodiment, the authentication server 30 may generate the first token using the current date and time, an identifier of the first user, a random key, and the like, and match the first token with the identifier of the first user. can be saved The first token may be later used to verify transaction data or seller information.

In step S105 , the authentication server 30 may transmit the generated first token to the first terminal 10 .

In step S107, the first terminal 10 may perform first user authentication by requesting authentication information from the first user. The first terminal 10 receives biometric information (eg, a fingerprint, face image, etc.) or password from the first user, and determines whether the biometric information or password matches pre-stored biometric information or password, Users can be authenticated. When authentication of the first user fails, the first terminal 10 may display a message requesting re-input of authentication information of the first user.

In response to successful authentication of the first user, step S109 is performed, and the first terminal 10 may generate a first private key and a first public key.

In step S111, the first terminal 10 may generate a first electronic signature based on the first private key and the first token. In one embodiment, the first terminal 10 uses one or more of the identifier of the first terminal, the identifier of the first user, and the first token as original data, and based on the original data and the first private key, the first electronic device 10 signature can be created. In some embodiments, the first terminal 10 may encrypt the original data with a first private key and generate a first electronic signature including the encrypted original data.

In step S113, the first terminal 10 may transmit the first electronic signature and the first public key to the authentication server 30.

In step S115, the authentication server 30 may verify the authenticity of the first electronic signature using the first public key. In one embodiment, the authentication server 30 decrypts the original data included in the first electronic signature using the first public key, and the identifier of the first terminal constituting the original data, the identifier of the first user, the first The first electronic signature may be verified by determining whether one or more of the tokens matches an identifier or token received and stored from the first terminal 10 .

In response to the successful verification of the first electronic signature, step S117 proceeds, and the authentication server 30 allocates the first token to the first terminal 10 to register the first user. In one embodiment, the authentication server 30 may associate and store the identifier of the first user, the identifier of the first terminal 10, the first token, and the first public key.

In step S119 , the authentication server 30 may transmit a user registration notification message indicating that user registration has been completed to the first terminal 10 .

Through the above steps S101 to S119, the seller may be registered in the authentication server 30.

In step S121 , the second terminal 20 may transmit a second user registration request including an identifier (eg, ID) of the second user to the authentication server 30 . In one embodiment, when receiving the second user's registration request, the authentication server 30 provides seller information including the second user's name, address, identifier of the second user, identifier of the second terminal 20, and the like. It may be received from the second terminal 10 and stored. Here, the identifier of the second terminal may be an identifier of the short-range communication module of the second terminal 20 .

Subsequently, in step S123 , the authentication server 30 may generate a second token to be allocated to the second terminal 20 . In one embodiment, the authentication server 30 may generate a second token using the current date and time, an identifier of the second user, a random key, and the like, and store the second token in association with the second user identifier. there is.

In step S125 , the authentication server 30 may transmit the generated second token to the second terminal 20 .

In step S127, the second terminal 20 may perform second user authentication by requesting authentication information from the second user. The second terminal 20 receives biometric information (eg, a fingerprint, face image, etc.) or password from the second user, and determines whether the biometric information or password matches pre-stored biometric information or password, Users can be authenticated. When authentication of the second user fails, the second terminal 20 may display a message requesting re-input of authentication information of the second user.

In response to successful authentication of the second user, step S129 proceeds, and the second terminal 20 may generate a second private key and a second public key.

In step S131, the second terminal 20 may generate a second electronic signature based on the second private key and the second token. In one embodiment, the second terminal 20 uses one or more of the identifier of the second terminal, the identifier of the second user, and the second token as original data, and based on the original data and the second private key, the second electronic data signature can be created. In some embodiments, the second terminal 20 may encrypt the original data using the second private key and generate a second electronic signature including the encrypted original data.

In step S133, the second terminal 20 may transmit the second electronic signature and the second public key to the authentication server 30.

In step S135, the verification server 30 may verify the authenticity of the second electronic signature by using the second public key and original text data. In one embodiment, the authentication server 30 decrypts the original data included in the second electronic signature using the second public key, and the identifier of the second terminal constituting the original data, the identifier of the second user, the second The second electronic signature may be verified by determining whether one or more of the tokens matches an identifier or token received and stored from the second terminal 20 .

In response to the successful verification of the second electronic signature, step S137 proceeds, and the authentication server 30 allocates the second token to the second terminal 20 to register the second user. In one embodiment, the authentication server 30 may associate and store the identifier of the second user, the identifier of the second terminal 20, the second token, and the second public key.

In step S139 , the authentication server 30 may transmit a user registration notification message indicating that user registration has been completed to the second terminal 20 .

Through the above-described steps S131 to S139, the purchaser may be registered in the authentication server 30.

Referring to FIGS. 3 to 4B , a method for verifying a transaction between a first user (eg, a seller) and a second user (eg, a buyer) will be described.

In step S201, the first terminal 10 accesses the authentication server 30 and successfully logs in, and then transmits a transaction identifier (ie, transaction ID) request to the authentication server 30. In one embodiment, the first terminal 10 may transmit product information including product names and product prices to the authentication server 30 . In some embodiments, when a plurality of products are on sale, the first terminal 10 may request a transaction identifier for each product from the authentication server 30 .

In step S203, the authentication server 30 may generate a transaction identifier and store the generated transaction identifier in association with seller information (ie, first user information) and product information. As described above with reference to FIG. 2, in one embodiment, when the authentication server 30 performs registration of the first user, the seller information including the seller name, business name, address, etc. is sent to the first terminal 10 ) and stored in advance. In some embodiments, when a transaction identifier for a plurality of products is requested, the authentication server 30 may generate a transaction identifier for each product.

In step S205 , the authentication server 30 may acquire a first token associated with the identifier of the first user and transmit a response message including the first token and the transaction identifier to the first terminal 10 . As already described, the first token may be generated and stored by the authentication server 30 during the registration process of the first user.

In step S207, the first terminal 10 may broadcast seller information including shop name and location information. In one embodiment, the first terminal 10 may broadcast the seller information using a wireless communication module.

The second terminal 20 may display a plurality of seller information received, and when the seller information transmitted from the first terminal 10 is selected, step S209 is performed to display the second terminal 20. may form a first channel with the first terminal 10. In one embodiment, the second terminal 20 may form a first channel with the first terminal 10 by requesting the first terminal 10 to form a first channel. In one embodiment, the first channel may be a wireless communication-based channel. In some embodiments, the first channel may be a short-distance wireless communication-based channel such as Bluetooth or Wi-Fi.

When the first channel is formed, step S211 is performed so that the first terminal 10 may transmit sales product information including product name, product price, etc. to the second terminal 20 through the first channel. there is.

In step S209, the second terminal 20 may display product sales information including one or more products. Accordingly, the second user can recognize products on sale in the corresponding store. In another embodiment, the second terminal 20 may broadcast a product information request including an identifier of the second user. In this case, in response to the product information request received from the second terminal 20, the first terminal 10 transmits product information for sale, including product name, product price, seller information, etc., to the second terminal 20. can transmit

In step S213, the second terminal 20 may receive purchase input information on any one product included in the sale product information from the second user (ie, the buyer). That is, the second user may input information desired to purchase one of the products included in the sale information.

In response to receiving product purchase information from the second user, in step S215, the second terminal 20 may transmit an identifier of a product selected to be purchased to the first terminal 10 through the first channel. .

In step S217, the first terminal 10 may generate a third electronic signature using the first token allocated to the first terminal 10 and the first private key of the first terminal 10. . In one embodiment, the first terminal 10 may generate a third electronic signature by setting the first token as original text data. That is, the first terminal 10 may encrypt the first token using the first private key and generate a third electronic signature including the encrypted first token.

In operation S219 , the first terminal 10 may transmit product information selected by the second user and vendor information including the third electronic signature and the first token to the second terminal 20 . In one embodiment, the seller information may be transmitted to the second terminal 20 through the first channel.

In step S221, the second terminal 20 may transmit a verification request for the seller information to the authentication server 30 in response to receiving the seller information. In one embodiment, the second terminal 20 may include the first token, the third electronic signature, the second user's identifier, and the product information in the verification request.

In step S223 , the authentication server 30 may verify seller information received from the second terminal 20 . In one embodiment, the authentication server 30 obtains the first public key of the first terminal associated with the first token, and verifies the authenticity of the third electronic signature using the first public key and the first token, thereby verifying the merchant. information can be verified. In some embodiments, the authentication server 30 decrypts the encrypted first token included in the third electronic signature using the first public key, and the decrypted first token is used to decrypt the first token included in the verification request. Authenticity of the third electronic signature can be verified by determining whether the tokens match.

The authentication server 30 may transmit a verification failure message for the seller information to the second terminal 20 in response to the failure of verification of the seller information, and the second terminal 20 responds to the verification failure of the seller information. The transaction of goods may be suspended.

On the other hand, in response to successful verification of the seller information, step S225 proceeds, and the authentication server 30 may obtain a second token related to the second user identifier from the pre-stored second user information. A transaction identifier corresponding to the second token and product information may be obtained from the stored transaction identifier list.

In step S227, the authentication server 30 may transmit a verification response message including the acquired transaction identifier and the second token to the second terminal 20, and the second terminal 20 is responsible for verifying the seller information. Upon success, the transaction identifier can be obtained.

In response to acquiring the transaction identifier, step S229 of FIG. 4A proceeds, and a second channel between the second terminal 20 and the first terminal 10 may be formed. In one embodiment, the second terminal 20 may form a second channel with the first terminal 10 by requesting establishment of a second channel to the first terminal 10 when the transaction identifier is obtained. In one embodiment, the second channel may be a wireless communication-based channel to which a protocol different from that of the first channel is applied. In some embodiments, the second channel may be a UWB-based wireless communication channel. In one embodiment, the second channel may be created using the transaction identifier. In one embodiment, the transaction identifier is used as an encryption key so that encrypted data can be transmitted or received over the second channel.

In step S231, the second terminal 20 may measure the distance to the first terminal 10 using the second channel. In one embodiment, the second terminal 20 measures the delay time of the no-go signal transmitted from the first terminal 10 through the second channel, and based on the delay and the already known speed of the radio signal, A distance to the first terminal 10 may be measured. In another embodiment, the second terminal 20 measures the strength of the radio signal transmitted from the first terminal 10 through the second channel, and communicates with the first terminal 10 based on the strength of the wireless signal. distance can be measured.

In steps S233 and S235, the second terminal 20 may perform second user authentication by requesting authentication information from the second user. In one embodiment, the second terminal 20 sends a message requesting authentication information of the second user when the measured distance (ie, the distance to the first terminal) is within a threshold distance. can display. The second terminal 20 receives biometric information (eg, a fingerprint, face image, etc.) or password from the second user, and determines whether the biometric information or password matches pre-stored biometric information or password, Users can be authenticated.

In response to successful authentication of the second user, step S237 proceeds, and the second terminal 20 receives the second token, the measured distance to the first terminal 10, the transaction identifier, and the product to be traded. One or more of the pieces of information may be encrypted with the private key of the second terminal 20 to generate transaction data. Here, information on a product to be traded may include a product identifier and a product sales price, and may further include a seller identifier (ie, a first user identifier) and buyer information (a second user identifier).

In step S239, the second terminal 20 may transmit a verification request including encrypted transaction data to the authentication server 30. In one embodiment, the second terminal 20 may include the identifier of the second token or the second user in the transaction data verification request. In some embodiments, the second terminal 200 may generate an electronic signature including the encrypted transaction data and request verification of the electronic signature to the authentication server 30 .

In step S241, the authentication server 30 obtains the second public key of the second terminal 20 stored in association with the second token or the second user identifier, and the encrypted transaction data using the second public key. After decrypting, the decrypted transaction data can be verified. In one embodiment, the authentication server 30 compares the transaction identifier, product information, and the second token included in the transaction data with pre-stored data to first verify whether the transaction data is correct. In addition, the authentication server 30 may perform secondary verification on the transaction data by determining whether the distance included in the transaction data is within a preset threshold distance. The authentication server 30 may fail verification of the transaction data when the distance exceeds the threshold distance, and may successfully process verification of the transaction data when the distance is less than or equal to the threshold distance.

In response to the successful verification of the transaction data, step S243 proceeds, and the authentication server 30 connects the second terminal 20, the first terminal 10, the VAN server 50, and the PG 60 In conjunction with one or more of them, a payment processing routine may be performed.

According to this embodiment, data necessary for a transaction can be transmitted and received through a communication channel without contact between the first terminal 10 and the second terminal 20 . In addition, according to this embodiment, the distance between the first terminal 10 and the second terminal 20 is included in the transaction data, and the distance acts as a major factor in verifying the transaction data, thereby making the illegal transaction can be accurately detected. In other words, when the distance between the first terminal 10 and the second terminal 20 exceeds the threshold distance, a transaction that occurs between the first terminal 10 and the second terminal 20 is not permitted. can be treated as

In the embodiment described above with reference to FIG. 4A, the second terminal generates transaction data, but in some other embodiments, the first terminal may generate transaction data.

4B is a signal flow diagram illustrating a method in which the first terminal generates transaction data. In the description with reference to FIG. 4B, steps having the same reference numerals as those in FIG. 4A are the same as the corresponding steps described with reference to FIG. 4A, and thus, in the description with reference to FIG. 4B, different parts from those in FIG. 4A are described.

In response to successful authentication of the second user, step S337 proceeds, so that the second terminal 20 obtains a distance to the first terminal 10 and uses the transaction identifier as an encryption key to obtain a second token. and the distance to the first terminal 10 may be encrypted. Here, the transaction identifier may be an identifier received from the authentication server 30 in step S227.

In step S339, the second terminal 20 may transmit the encrypted second token and the distance to the first terminal 10 through the second channel.

In step S341, the first terminal 10 may decrypt the encrypted second token and distance by using the transaction identifier as a decryption key. Here, the transaction identifier may be an identifier received from the authentication server 30 in step S205 of FIG. 3 . The transaction identifier can be used as a symmetric key to encrypt and decrypt the second token and distance. In some embodiments, instead of receiving the distance from the first terminal 10, the first terminal 10 transmits a radio signal transmitted from the second terminal 20 through a second channel formed with the second terminal 20. The distance to the second terminal 20 may be measured based on the signal.

In step S343, the first terminal 10 includes at least one of the decrypted second token, information on a product to be traded, a distance between the first terminal 10 and the second terminal 20, and a transaction identifier. Transaction data may be generated, and the transaction data may be encrypted using the private key of the first terminal 10 .

In step S345, the first terminal 10 may transmit a transaction data verification request to the authentication server 30. In one embodiment, the second terminal 20 may include the identifier of the first token or the first user in the transaction data verification request.

In step S347, the authentication server 30 acquires the first public key of the first terminal 10 previously stored in relation to the first token or the first user identifier, and uses the first public key to obtain an encrypted transaction. After decrypting the data, the decrypted transaction data can be verified. In one embodiment, the authentication server 30 may first verify whether the transaction identifier, product information, and the second token included in the transaction data match pre-stored data. In addition, the authentication server 30 may perform secondary verification on the transaction data by determining whether the distance included in the transaction data is within a preset threshold distance. The authentication server 30 may fail verification of the transaction data when the distance exceeds the threshold distance, and may successfully process verification of the transaction data when the distance is less than or equal to the threshold distance.

In response to the successful verification of the transaction data, step S349 proceeds, and the authentication server 30 connects the second terminal 20, the first terminal 10, the VAN server 50, and the PG 60 In conjunction with one or more of them, a payment processing routine may be performed.

5 illustrates a user interface displayed on a purchaser terminal (ie, a second terminal).

Referring to FIG. 5 , when different sales information is received from a plurality of seller terminals, the second terminal 20 may display seller information as shown in (a) of FIG. 4 . Subsequently, when selection information about “Shop A” is input from among a plurality of seller information, the second terminal 20 may display a plurality of products sold in “Shop A”. When the second user inputs a purchase for any one of the displayed products, the second terminal 20 may display a message requesting to approach the seller in (c) of FIG. 4 . Subsequently, when the distance between the first terminals 10 is within the threshold distance, the second terminal 20 displays a message requesting user authentication information in order to generate transaction data, and receives authentication information from the user. can If authentication of the authentication information is successful, the second terminal 20 may generate transaction data and transmit it to the authentication server 30 .

Hereinafter, referring to FIGS. 6 and 7 , a payment routine performed when transaction data is successfully verified will be described.

First, with reference to FIG. 6 , a method of processing payment for product purchase by interlocking the credit card server, the PG 60 and the VAN server 50 will be described. The payment processing method according to FIG. 6 may be a routine processed when using an online market.

In response to the successful verification of the transaction data, in step S401, the authentication server 30 may transmit a verification request of the second user (ie, the purchaser) to the credit card server 40. In one embodiment, the authentication server 30 transmits information about the second user, eg, date of birth, name, mobile phone number, etc. to the credit card server 40 to request verification of the second user.

In step S403, the credit card server 40 may verify the second user by determining whether the second user information received from the authentication server 30 is correct.

In response to successful verification of the second user, step S405 may be performed to generate a third token for credit card payment.

In step S407, the credit card server 40 transmits the third token to the authentication server 30, and in step S409, the authentication server 30 sends the received third token to the second terminal 20. can be conveyed

In step S411, the second terminal 20 transmits a payment request including a third token and credit card information to PG 60, and in step S413, PG 60 transmits the received payment request It can be transmitted to the VAN server (50). The credit card information is payment information for paying for a product, and may include a serial number of a credit card, an expiration date, and the like.

In step S415, the VAN server 50 may transmit the payment request to the credit card server 40.

The credit card server 40 first verifies whether the third token included in the received payment request is a token issued to the second user, and whether the payment information (ie, credit card information) included in the payment request is correct. can be verified secondarily.

When the credit card server 40 verifies both the first and second verifications in step S417, it may transmit a payment completion response message indicating that the payment has been successfully processed to the VAN server 50.

When the payment completion response message is received, in step S419, the VAN server 50 may transmit the payment completion response message to the PG 60, and in step S421, the PG 60 notifies that the payment has been completed normally A payment completion notification message may be transmitted to the second terminal 20 .

When the payment is normally completed in step S423, product purchase is completed, and the second terminal 20 may release at least one of the first channel and the second channel formed with the first terminal 10.

Referring to FIG. 7 , a method according to another embodiment in which a credit card server and a VAN server 50 work together to process payment for product purchase will be described. The payment processing method according to FIG. 7 may be used in a routine in which product payment is processed in conjunction with a POS (Point Of Sale) terminal of an offline store.

In the description with reference to FIG. 7 , since steps having the same reference numerals as those in FIG. 6 are the same as the description with reference to FIG. 6 , only steps having reference numerals different from those in FIG. 6 will be described below.

In step S511, the second terminal 20 may encrypt the third token and credit card information. In one embodiment, the second terminal 20 may encrypt the third token and credit card information by using a transaction identifier of a product being purchased as an encryption key.

In step S513, the second terminal 20 may transmit the encrypted third token and credit card information to the first terminal 10. In one embodiment, the second terminal 20 may transmit the encrypted third token and credit card information to the first terminal 10 through the second channel.

In step S515, the first terminal 10 may decrypt the encrypted third token and credit card information. In one embodiment, the first terminal 10 may decrypt the third token and credit card information by using a transaction identifier of a product being purchased as a decryption key.

In step S517, the first terminal 10 may transmit a payment request including the decrypted third token and credit card information to the VAN server 50. The credit card information is payment information for paying for a product, and may include a serial number of a credit card, an expiration date, and the like.

In step S519, the VAN server 50 may transmit the payment request to the credit card server 40.

The credit card server 40 may firstly verify whether the third token included in the received payment request is a token issued to the second user, and secondly verify whether the credit card information included in the payment request is correct. there is.

When the credit card server 40 verifies both the first and second verifications in step S521, it may transmit a payment completion response message indicating that the payment has been successfully processed to the VAN server 50.

When the payment completion response message is received, in step S523, the VAN server 50 may transmit a payment completion notification message notifying that the payment is normally completed to the first terminal 10.

When the payment is normally completed in step S525, product sales processing is completed, and the first terminal 10 may release at least one of the first channel and the second channel formed with the second terminal 20.

A hardware configuration of an exemplary computing device according to some embodiments of the present invention will now be described with reference to FIG. 8 . The computing device described with reference to FIG. 8 may be, for example, a hardware configuration of at least one of the authentication server 30, the first terminal 10, and the second terminal 20 described with reference to FIGS. 1 to 7 . .

8 is an exemplary hardware configuration diagram in which a computing device may be implemented in various embodiments of the present invention. The computing device 1000 includes one or more processors 1100, a system bus 1600, a communication interface 1200, a memory 1400 for loading a computer program 1500 executed by the processor 1100, A storage 1300 for storing the computer program 1500 may be included.

The processor 1100 controls the overall operation of each component of the computing device 1000 . The processor 1100 may include at least one of a Central Processing Unit (CPU), a Micro Processor Unit (MPU), a Micro Controller Unit (MCU), a Graphic Processing Unit (GPU), or any type of processor well known in the art. can be configured to include Also, the processor 1100 may perform an operation for at least one application or program for executing a method/operation according to various embodiments of the present disclosure. Computing device 1000 may include two or more processors.

Memory 1400 stores various data, commands and/or information. Memory 1400 may load one or more computer programs 1500 from storage 1300 to execute methods/actions according to various embodiments of the present invention. An example of the memory 1400 may be RAM, but is not limited thereto. The system bus 1600 provides a communication function between components of the computing device 1000 .

The system bus 1600 may be implemented as various types of buses such as an address bus, a data bus, and a control bus. The communication interface 1200 supports wired and wireless Internet communication of the computing device 1000 . The communication interface 1200 may support various communication methods other than Internet communication. To this end, the communication interface 1200 may include a communication module well known in the art. Storage 1300 may non-temporarily store one or more computer programs 1500 . The storage 1300 may include a non-volatile memory such as a flash memory, a hard disk, a removable disk, or any type of computer-readable recording medium well known in the art.

Computer program 1500 may include one or more instructions in which methods/operations according to various embodiments of the invention are implemented. When the computer program 1500 is loaded into the memory 1400, the processor 1100 may execute the one or more instructions to perform methods/operations according to various embodiments of the present invention.

In one embodiment, the computer program 1500 includes an operation of receiving information of a seller selling a product from a first terminal, an operation of requesting verification of the information of the seller to a server, and information of the seller In response to the verification success, an operation of obtaining a transaction identifier for the product from the server, an operation of measuring a distance to the first terminal, and transaction data including the measured distance and the transaction identifier An operation of generating, an operation of requesting verification of the transaction data to the server, and an operation of performing a payment routine for the product in response to receiving a message indicating success of the transaction data from the server. It may contain instructions to perform.

So far, various embodiments of the present invention and effects according to the embodiments have been described with reference to FIGS. 1 to 8 . Effects according to the technical idea of the present invention are not limited to the effects mentioned above, and other effects not mentioned will be clearly understood by those skilled in the art from the description below.

The technical idea of the present invention described with reference to FIGS. 1 to 11 so far can be implemented as computer readable code on a computer readable medium. The computer-readable recording medium may be, for example, a removable recording medium (CD, DVD, Blu-ray disc, USB storage device, removable hard disk) or a fixed recording medium (ROM, RAM, computer-equipped hard disk). can The computer program recorded on the computer-readable recording medium may be transmitted to another computing device through a network such as the Internet, installed in the other computing device, and thus used in the other computing device.

In the above, even though all the components constituting the embodiment of the present invention have been described as being combined or operated as one, the technical spirit of the present invention is not necessarily limited to these embodiments. That is, within the scope of the object of the present invention, all of the components may be selectively combined with one or more to operate.

Although actions are shown in a particular order in the drawings, it should not be understood that the actions must be performed in the specific order shown or in a sequential order, or that all shown actions must be performed to obtain a desired result. In certain circumstances, multitasking and parallel processing may be advantageous. Moreover, the separation of the various components in the embodiments described above should not be understood as requiring such separation, and the described program components and systems may generally be integrated together into a single software product or packaged into multiple software products. It should be understood that there is

Although the embodiments of the present invention have been described with reference to the accompanying drawings, those skilled in the art can implement the present invention in other specific forms without changing the technical spirit or essential features. can understand that there is Therefore, the embodiments described above should be understood as illustrative in all respects and not limiting. The protection scope of the present invention should be construed according to the claims below, and all technical ideas within the equivalent range should be construed as being included in the scope of the technical ideas defined by the present invention.

Claims (20)

Receiving, by a second terminal, information on a seller selling a product from the first terminal;
requesting, by the second terminal, verification of the seller's information to a server;
obtaining, by the second terminal, a transaction identifier for the product from the server in response to successful verification of the seller's information;
measuring, by the second terminal, a distance to the first terminal;
generating, by the second terminal, transaction data including the measured distance and the transaction identifier;
requesting, by the second terminal, verification of the transaction data to the server; and
In response to receiving, by the second terminal, a message indicating success of verification of the transaction data from the server, performing a payment routine for the product,
How to support commodity trading. According to claim 1,
Generating the transaction data,
performing, by the second terminal, user authentication in response to the fact that the measured distance is within a threshold distance; and
In response to the second terminal succeeding in the user authentication, generating the transaction data,
How to support commodity trading. According to claim 1,
The step of performing the payment routine for the product,
In response to the fact that the distance included in the transaction data is within a threshold distance and the transaction identifier included in the transaction data matches a pre-stored transaction identifier, receiving a message indicating success for the transaction data from the server. doing,
How to support commodity trading. According to claim 1,
Receiving the information about the seller from the first terminal,
forming, by the second terminal, a first wireless communication channel with the first terminal; and
Receiving, by the second terminal, information about the seller through the first wireless communication channel;
The step of measuring the distance to the first terminal,
forming, by the second terminal, a second wireless communication channel with the first terminal; and
Measuring, by the second terminal, a distance to the first terminal based on a radio signal generated through the second wireless communication channel,
How to support commodity trading. According to claim 4,
The first wireless communication channel and the second wireless communication channel use different wireless protocols,
How to support commodity trading. According to claim 4,
Forming the second wireless communication channel,
Forming the second wireless communication channel through which encrypted data is transmitted or received based on the transaction identifier.
How to support commodity trading. According to claim 4,
Forming a first wireless communication channel with the first terminal,
Forming, by the second terminal, the first wireless communication channel with the first terminal in response to selection of the product or the seller;
Forming a second wireless communication channel with the first terminal,
In response to the second terminal obtaining the transaction identifier from the server, forming the second wireless communication channel with the first terminal.
How to support commodity trading. According to claim 1,
The information on the seller includes an electronic signature generated based on a first token assigned to the first terminal and a private key of the first terminal,
The step of requesting verification of the seller's information to the server,
Including the step of requesting verification of the electronic signature to the server,
How to support commodity trading. According to claim 1,
Prior to generating the transaction data,
Acquiring, by the second terminal, a second token allocated to the second terminal,
Generating the transaction data,
generating, by the second terminal, the transaction data further including the second token; and
Encrypting the generated transaction data with a private key of a second terminal,
The step of requesting verification of the transaction data to the server,
Including the step of requesting verification of the encrypted transaction data to the server,
How to support commodity trading. According to claim 9,
Prior to the step of obtaining the transaction identifier for the product from the server,
Transmitting, by the second terminal, a user registration request to the server; and
Further comprising, by the second terminal, being allocated the second token in response to successful user registration.
How to support commodity trading. According to claim 9,
Obtaining the transaction identifier from the server,
Receiving, by the second terminal, the second token from the server in response to successful verification of the seller's information,
How to support commodity trading. According to claim 1,
The step of performing the payment routine for the product,
receiving, by the second terminal, a third token issued by a credit card server from the server; and
Transmitting, by the second terminal, the third token and payment information to a Payment Gateway (PG) or Value Added Network (VAN) server,
How to support commodity trading. Transmitting, by a first terminal, information about a product on sale to a second terminal;
receiving, by the first terminal, a purchase request for the product from the second terminal;
forming, by the first terminal, a radio channel for distance measurement with the second terminal;
receiving, by the first terminal, a second token allocated to the second terminal from the second terminal;
generating, by the first terminal, transaction data including a distance between the first terminal and the second terminal measured through a signal of the radio channel and the second token; and
Requesting, by the first terminal, verification of the transaction data to a server;
According to the successful verification of the transaction data, the payment routine for the product proceeds,
How to support commodity trading. According to claim 13,
In response to the fact that the distance included in the transaction data is within a threshold distance and the second token matches the token allocated to the second terminal, a payment routine for the product proceeds.
How to support commodity trading. According to claim 13,
Prior to generating the transaction data,
Further comprising, by the first terminal, acquiring a transaction identifier for the product;
Generating the transaction data,
generating, by the first terminal, the transaction data further including the transaction identifier; and
Encrypting the generated transaction data with a private key of a first terminal;
The step of requesting verification of the transaction data to the server,
Including the step of requesting verification of the encrypted transaction data to the server,
How to support commodity trading. According to claim 15,
Receiving the second token from the second terminal,
Receiving, by the first terminal, the encrypted second token and the distance from the second terminal through the wireless channel, wherein the distance is measured by the second terminal based on a signal of the wireless channel; ; and
Decrypting, by the first terminal, the encrypted second token and the distance using the transaction identifier as a decryption key,
How to support commodity trading. According to claim 13,
Transmitting the information about the product to the second terminal,
generating, by the first terminal, seller information based on a first token allocated to the first terminal and a private key of the first terminal; and
Transmitting, by the first terminal, the seller information to the second terminal;
Forming the radio channel with the second terminal,
In response to successful verification of the seller information, the first terminal further comprising generating the radio channel for distance measurement with the second terminal,
How to support commodity trading. According to claim 13,
After the server succeeds in verifying the transaction data,
receiving, by the first terminal, a third token issued by a credit card server from the second terminal; and
Transmitting, by the first terminal, the third token and payment information to a Payment Gateway (PG) or Value Added Network (VAN) server,
How to support commodity trading. one or more processors;
a memory for loading a computer program executed by the processor; and
Including a storage for storing the computer program,
The computer program,
receiving information on a seller selling a product from the first terminal;
requesting verification of the seller's information to a server;
obtaining a transaction identifier for the product from the server in response to successful verification of the seller's information;
measuring a distance to the first terminal;
generating transaction data including the measured distance and the transaction identifier;
requesting verification of the transaction data to the server; and
In response to receiving a message from the server indicating success of verification of the transaction data, instructions for performing an operation of performing a payment routine for the product,
computing device. A computer-readable non-transitory recording medium containing instructions,
When executed by a processor, the instructions cause the processor to:
Transmitting information about products on sale to a second terminal;
receiving a purchase request for the product from the second terminal;
forming a radio channel for distance measurement with the second terminal;
receiving a second token allocated to the second terminal from the second terminal;
generating transaction data including the distance between the second terminals and the second token measured through the signal of the radio channel; and
Including the step of requesting verification of the transaction data to the server,
According to the successful verification of the transaction data, the payment routine for the product proceeds,
Computer-readable non-transitory recording medium.

Images