KR102644953B1 - Payment interface apparatus - Google Patents

Abstract

The present invention relates to a payment interface device and system, which receives payment information of a payer who purchased a product, generates a payment information identifier, which is identification information of the payment information, and then uses the generated payment information identifier by a payment terminal owned by the payer. A payment interface device that recognizes and outputs a payment information identifier so that payment for the payer can be requested to a payment server. The payment interface device acquires first time information about the time of generating the payment information identifier to authenticate the payer's payment. Authentication information is generated for the payment request for the payer made through the payment terminal, and whether or not to proceed is determined according to the result of comparison between the first time information identified from the authentication information and the reference time information. .

Description

Payment interface device {PAYMENT INTERFACE APPARATUS}

The present invention relates to a payment interface device and system, and more particularly, to a payment interface device and system that can improve payment security.

Generally, a payment system through a credit card consists of a vendor terminal (i.e. POS terminal), a VAN relay server, and a credit card payment server. When the credit card is recognized by the vendor terminal, credit card information is transferred to the VAN relay server for credit card payment. It is sent to the server and payment is requested, and the VAN relay server verifies the credit card information and transmits the payment approval information received from the credit card payment server to the seller's terminal to approve the payment.

Conventional payment systems based on such vendor terminals have the following limitations.

First, there is a limitation in that the cashier at the sales outlet directly confirms the payment method with the purchaser, determines the payment method, and then provides the purchaser with a payment interface according to the determined payment method. In other words, there is the inconvenience of having to personally check the payment method or payment service used by each purchaser at each purchase, which increases the time required for payment and causes inconvenience during payment processing.

In addition, the current sales terminal has a limitation in that it cannot operate in conjunction with a mobile communication terminal such as a smartphone or tablet carried by the sales clerk, or its universal operating system (OS), so it is not possible to improve payment convenience through the linkage. There is a need, and furthermore, when the payment method is a P2P (Peer to Peer) remittance method between the seller and the purchaser, the seller is not provided with the convenience of confirming the deposit for the payment amount.

Meanwhile, unlike the conventional payment request method from the seller's terminal, the payer's terminal recognizes the identification code (e.g. QR code) printed from the seller's terminal, obtains the information necessary for payment, and then the payer's terminal directly makes the payment to the payment server. There is a trend of applying the payment request method to the payer terminal.

In the case of this payer terminal payment request method, after the payer's terminal acquires the identification code printed from the seller's terminal, the acquired identification code is not the seller's identification code, but the payer's (i.e. malicious thief's) identification code or other By requesting payment by changing the seller's identification code, you are exposed to a security incident where payment is transferred to the thief's account or another seller's account.

Since these security incidents are due to the absence of a system that verifies whether the vendor identification code transmitted from the purchaser corresponds to the actual identification code printed from the vendor terminal, a system that eliminates the security risk during payment is required. .

The background technology of the present invention is disclosed in Republic of Korea Patent Publication No. 10-2015-0042385 (published on April 21, 2015).

The present invention was created to solve the above-described problem, and the purpose of one aspect of the present invention is to eliminate the inconvenience of having the sales clerk have to directly check the payment method with the purchaser when making a payment at the store, and at the same time, The aim is to provide a payment interface device and system to improve payment convenience by providing a method for linking a mobile communication terminal held by a cashier with a seller's terminal.

Another object of the present invention is to provide a payment interface device and system that can improve payment security by eliminating security incidents in which payment is made due to an identification code output from a merchant terminal being changed by a malicious thief.

The payment interface device according to one aspect of the present invention receives payment information of a payer who purchased a product, generates a payment information identifier that is identification information of the payment information, and then uses a payment terminal owned by the payer to make the generated payment. A payment interface device that recognizes the information identifier and outputs the payment information identifier so that payment for the payer can be requested to a payment server, wherein the payment interface device includes first time information about the time of generating the payment information identifier. is acquired to generate authentication information for payment authentication of the payer, and a payment request for the payer made through the payment terminal is based on a comparison result between the first time information identified from the authentication information and the reference time information. It is characterized by the decision whether to proceed or not.

In the present invention, the payment interface device modulates the first time information to generate modulation information of a predefined type as the authentication information, and the first time information identified to determine whether to proceed with the payment request is, It is characterized in that it is identified through demodulation of the modulation information.

In the present invention, the reference time information is second time information about the time when the authentication information is obtained by the payment terminal, and the payment request for the payer made through the payment terminal includes the first time information and Characterized in that the process is performed only when the error between the second time information is less than or equal to a preset standard value.

The payment interface system according to one aspect of the present invention is a mobile communication terminal for a seller including one or more mobile communication terminals, and can be combined with each of the mobile communication terminals, and is capable of purchasing a product entered into each of the mobile communication terminals. and a payer interface unit that provides the payer's payment information to the payer, wherein each mobile communication terminal, in a state coupled to the payer interface unit, receives the payer's payment information, and each mobile communication terminal Authentication information for validating the terminal is inputted from the payer interface unit, and a payment information identifier for the payer's payment is generated using the input payment information and authentication information, which is then transmitted to the payer interface unit. , the interface unit for the payer outputs the payment information identifier so that the payment terminal owned by the payer can recognize the payment information identifier and request payment for the payer to the payment server. Payment is made, but the payment is made to the payer only when the validity of each mobile communication terminal is verified based on authentication information extracted from the payment information identifier received from each mobile communication terminal.

In the present invention, the authentication information is characterized in that it includes a seller identifier, which is identification information for the seller, stored in the interface unit for the payer, or a unique authentication identifier, which is identification information for the interface unit for the payer.

In the present invention, the payer interface unit includes authentication information transmitted to each mobile communication terminal while stored in the payer interface unit, and authentication information extracted from the payment information identifier received from the mobile communication terminal. If there is a match, the validity of each mobile communication terminal is determined to be authenticated.

The payment interface system according to one aspect of the present invention is a mobile communication terminal for a seller including one or more mobile communication terminals, can be combined with each mobile communication terminal, and provides payment information of the payer who purchased the product to the payer. an interface unit for a payer, and a payment server, wherein each mobile communication terminal generates authentication information for payment authentication of the payer when coupled to the interface unit for the payer, and the generated authentication information It is output so that the payment terminal owned by the payer recognizes the authentication information, and a payment information identifier for the payer's payment is generated and output based on the payment information of the payer. The payment information identifier is sent to the payment terminal. performs a function of allowing the payment terminal to request payment for the payer to the payment server, and the payment server receives authentication information recognized by the payment terminal and the payment information by the payment terminal. It is characterized by determining whether to approve a payment request from the payment terminal according to a comparison result between authentication information extracted from the identifier.

In the present invention, each mobile communication terminal is characterized in that it generates the authentication information using one or more of a seller identifier, which is identification information for the seller, and a seller identifier, which is identification information for each mobile communication terminal.

In the present invention, each mobile communication terminal receives the vendor identifier stored in the payer interface unit from the payer interface unit, modifies it, generates and outputs modulated information of a predefined type as the authentication information, The payment information identifier is generated and output based on the payer's payment information and the vendor identifier stored in the payer interface unit, and the payment server determines it through demodulation of the modulation information recognized by the payment terminal. If the seller identifier and the seller identifier extracted from the payment information identifier match, the payment request from the payment terminal is approved.

In the present invention, each mobile communication terminal modulates a seller identifier stored in each mobile communication terminal to generate and output modulation information of a predefined type as the authentication information, and the payment information identifier is the payment information. It is generated and output based on the user's payment information and the seller identifier stored in the payer interface unit, and the payment server provides a seller identifier identified through demodulation of the modulation information recognized by the payment terminal, and the payment information. The payment request from the payment terminal is approved when the relationship between the vendor identifiers extracted from the identifier satisfies a predefined correspondence relationship.

In the present invention, each mobile communication terminal further uses first time information about the current time to generate the authentication information, and a payment request for the payer made through the payment terminal is made by the payment terminal. Characterized in that the process is performed only when the error between first time information determined based on the recognized authentication information and second time information about the time when the authentication information was acquired by the payment terminal is less than or equal to a preset standard value.

In the present invention, each mobile communication terminal generates the authentication information using first time information about the current time, and the payment server determines the authentication information based on the authentication information recognized by the payment terminal. Characterized in that the determination of whether to approve the payment request from the payment terminal is initiated only when the error between the first time information and the second time information for the current time is less than or equal to a preset standard value.

The payment interface system according to one aspect of the present invention is a mobile communication terminal for a seller including one or more mobile communication terminals, and can be combined with each of the mobile communication terminals, and receives payment information of the payer who purchased the product and receives the payment information from the payer. An interface unit for a payer, and a payment server provided to the payer, wherein each mobile communication terminal, while coupled to the interface unit for the payer, transmits authentication information for payment authentication of the payer from the interface unit for the payer. Using the received payment information of the payer, a payment information identifier for the payer's payment can be generated, and the payment terminal owned by the payer can recognize the payment information identifier and request payment for the payer to the payment server. The payment information identifier is output so that the payment server determines whether to approve the payment request from the payment terminal according to an analysis result of authentication information extracted from the payment information identifier by the payment terminal. do.

In the present invention, each mobile communication terminal uses the payment information as well as a seller identifier, which is identification information for the seller, as the authentication information, and a seller identifier, which is identification information for each mobile communication terminal, to determine the payment information identifier. It is characterized by generating.

In the present invention, the payment server approves a payment request from the payment terminal when the relationship between the vendor identifier and the seller identifier extracted from the payment information identifier by the payment terminal satisfies a predefined correspondence relationship. Do it as

The payment interface system according to one aspect of the present invention is a mobile communication terminal for a seller including one or more mobile communication terminals, and can be combined with each of the mobile communication terminals, and receives payment information of the payer who purchased the product and receives the payment information from the payer. An interface unit for a payer provided to the payer, and an external server, wherein each mobile communication terminal transmits authentication information for authentication of combination validity required for performing payment for the payer to the external server, The combination validity includes one or more of a first combination validity between the seller and the vendor and a second combination validity between each mobile communication terminal and the payer interface unit, and the external server determines that the received authentication information is predefined. If the specified authentication relationship is satisfied, the combination validity is determined to be authenticated, and each mobile communication terminal operates as an authentication terminal that performs payment for the payer only when the combination validity is certified by the external server. It is characterized by:

In the present invention, the authentication information transmitted by each mobile communication terminal to the external server is a first identifier including at least one of a seller identifier, which is identification information for the seller, and a terminal identifier, which is an identifier for each mobile communication terminal. , and a second identifier stored in the payer interface unit, including at least one of a seller identifier, which is identification information for the seller, and a unique authentication identifier, which is identification information for the payer interface unit. .

In the present invention, the external server determines that the first combination validity is authenticated when the seller identifier and the seller identifier satisfy a predefined authentication relationship, and the terminal identifier and the unique authentication identifier are predefined. When the authentication relationship is satisfied, the validity of the second combination is determined to be certified.

In the present invention, after an authentication communication link for authentication of the validity of the combination is established between each mobile communication terminal and the payer interface unit, the second identifier is transmitted from the payer interface unit to each mobile communication terminal. Accordingly, when the authentication information including the first and second identifiers is transmitted from each mobile communication terminal to the external server, and the validity of the combination is certified by the external server, each mobile communication terminal and the payment Characterized in that a payment communication link for performing payment for the payer is established between user interface units.

In the present invention, when the payment communication link is established, each mobile communication terminal receives the payment information of the payer and transmits it to the payer interface unit along with the first identifier, and the payer interface unit is configured to: A payment information identifier for the payer's payment is generated using the payer's payment information, the first identifier, and the second identifier, and the payment terminal owned by the payer recognizes the payment information identifier to provide information to the payer. The payment information identifier is output so that payment can be requested from the payment server.

In the present invention, the external server further includes a payment server that determines whether to approve the payment request from the payment terminal and feeds back the approval result, and the payment server extracts the payment information identifier from the payment terminal by the payment terminal. It is characterized by determining whether to approve the payment request from the payment terminal by verifying authentication between the first and second identifiers.

According to one aspect of the present invention, the convenience of payment can be improved by implementing the sales terminal provided at the sales office by dividing it into an interface device for the sales office cashier and the purchase payer, and the identification of the seller transmitted from the purchase payer. Payment security can be improved by adopting a system that verifies whether the code corresponds to the actual identification code printed from the seller's terminal.

1 is a block diagram illustrating a payment interface device according to a first embodiment of the present invention.
Figure 2 is an exemplary diagram showing the sub-configuration of the payment interface device according to the first embodiment of the present invention.
Figure 3 is a block diagram for explaining the operation of the payment interface device according to the first embodiment of the present invention.
Figure 4 is a block diagram for explaining the payment interface system according to the second embodiment of the present invention.
Figure 5 is an exemplary diagram showing an implementation example of a payment interface system according to a second embodiment of the present invention.
Figure 6 is an example diagram for explaining the operation of the payment interface system according to the second embodiment of the present invention.
7 to 12 are exemplary diagrams for explaining the operation of the payment interface system according to the third embodiment of the present invention.
Figure 13 is an example diagram for explaining the operation of the payment interface system according to the fourth embodiment of the present invention.

1 is a block diagram for explaining a payment interface device according to a first embodiment of the present invention, and FIG. 2 is an exemplary diagram showing a sub-configuration of a payment interface device according to a first embodiment of the present invention. 3 is a block diagram for explaining the operation of the payment interface device according to the first embodiment of the present invention.

Referring to FIG. 1, the payment interface device 100 according to the first embodiment of the present invention may include a seller interface unit 110 and a payer interface unit 120, and a payment terminal 200 and a payment Payment can be made to the payer through communication with the server 300.

When explaining the sub-configuration of the seller interface unit 110 and the payer interface unit 120 with reference to FIG. 2, first, the seller interface unit 110 includes payment information (order details and payment amount) of the payer who purchased the product. ) from the seller, and a first input unit 111 for outputting the payment information input through the first input unit 111 and the payer identifier received from the payer interface unit 120, which will be described later, to the seller. 1 may include an output unit 112. The first input unit 111 may include a keyboard, a scanner (e.g., QR code scanner, barcode scanner, etc.), and a voice/sound wave recognition device (e.g., microphone, etc.) to input payment information, and a first output unit ( 112) may include a display device (eg, LCD, etc.) and a voice/sound wave output device for outputting payment information and payer identifier to the seller.

The payer interface unit 120 provides a second input unit 121 for receiving a payer identifier from the payment terminal 200, which will be described later, and allows the payer to confirm the payment information entered into the seller interface unit 110. It may include a second output unit 122 for doing this. The second input unit 121 may include a keyboard, a scanner (e.g., QR code scanner, barcode scanner, etc.), and a voice/sound wave recognition device (e.g., microphone, etc.) to receive the payer identifier from the payment terminal 200. The second output unit 122 may include a display device (eg, LCD, etc.) and a voice/sound wave output device for outputting payment information to the payer. Meanwhile, the payment information (order details and payment amount) of the payer who purchased the product is received not only through the first input unit 111 of the seller interface unit 110 but also through the second input unit 121 of the payer interface unit 120. Can be entered..

The seller's interface unit 110 and the payer's interface unit 120 can be designed in a structure that can be combined and separated, and when installed separately and apart from each other at a seller, they can transmit and receive information through wired and wireless communication. For example, the seller's interface unit 110 may be installed at a location where a seller's cashier resides, such as a checkout counter, and the payer's interface unit 120 may be installed at a table (e.g., a restaurant table) where the payer is located. The seller interface unit 110 and the payer interface unit 120, which are installed spaced apart from each other, can transmit and receive information through wired and wireless communication.

Based on the sub-configurations of the seller interface unit 110 and the payer interface unit 120 described above, the operations of the seller interface unit 110 and the payer interface unit 120 will be described in detail below.

The seller interface unit 110 acquires the payer identifier (QR code, barcode, or near-field communication (NFC, Bluetooth) data, etc.), which is the payer's identification information, from the payment terminal 200 owned by the payer who purchased the product. , the payer's payment information is input to match the obtained payer identifier, and payment for the payer can be requested to the payment server 300 based on the input payment information.

First, to describe an embodiment in which the seller interface unit 110 acquires a payer identifier, the seller interface unit 110 acquires the payer identifier output to the payment terminal 200. ) You can receive the payer identifier from.

That is, the payer interface unit 120 can acquire the payer identifier output on the payment terminal 200 through the second input unit 121 (e.g., QR code scanner or barcode scanner), and the seller interface unit 110 ) may receive the payer identifier from the payer interface unit 120 through wired or wireless communication and output it through the first output unit 112. This case may be applied when the payment terminal 200 can only generate a payer identifier in the form of a QR code or barcode due to limitations in the protocol.

In addition, the seller interface unit 110 may receive and obtain the payer identifier directly from the payment terminal 200 without going through the payer interface unit 120 and output it through the first output unit 112. In this case, it can be applied when the payment terminal 200 supports a short-range wireless communication protocol and can generate a payer identifier in the form of short-range wireless communication data.

After obtaining the payer identifier, the seller interface unit 110 may receive the payer's payment information to match the acquired payer identifier, and perform payment to the payer based on the input payment information to the payment server ( 300).

That is, after the payer transmits the payer identifier to the seller interface unit 110 (via the payer interface unit 120 or directly) through the payment terminal 200, the output is output through the first output unit 112. When the cashier at the store scans the payer identifier and inputs the payment information by matching it with the payer identifier, the seller interface unit 110 can request payment for the payer to the payment server 300 based on the entered payment information. there is. Accordingly, the inconvenience of having to individually scan and recognize payer identifiers such as QR codes or barcodes printed on the payment terminal 200 can be eliminated from the point of view of the sales clerk, and from the payer's point of view, the payment terminal 200 There is no need to present it directly to the sales clerk, and the payer identifier is entered into the seller interface unit 110 in a simple manner by tagging the payer identifier in the first input unit 111 of the payer interface unit 120 installed at the table where the payer is located. ) can be passed on.

Meanwhile, in this embodiment, the seller interface unit 110 outputs the payer identifier obtained from the payment terminal 200 and receives payment information to match the output payer identifier, or receives payment information from the payment terminal 200. Payment information can be input by converting the obtained payer identifier into a predetermined type of payer identifier, outputting it, and receiving payment information to match the converted payer identifier.

That is, the seller interface unit 110 may receive the payer identifier from the payer interface unit 120, which has obtained the payer identifier from the payment terminal 200, and output it as is through the first output unit 112. , When there are multiple payers, considering the case where the payer identifier generation protocol supported by each payment terminal owned by each payer is different, the seller interface unit 110 receives the payer identifier from the payment terminal 200. The payer identifier may be received from the payer interface unit 120 that has acquired the payer identifier, converted into a payer identifier of a predetermined type, and output through the first output unit 112.

For example, even if the payment terminal 200 possessed by the payer transmits a heterogeneous payer identifier such as a QR code, bar code, or data for short-range wireless communication (NFC, Bluetooth, etc.), the seller interface unit 110 The payer identifier may be converted into a predetermined type of payer identifier (e.g., barcode) and output through the first output unit 112. Accordingly, the sales clerk can input payment information by tagging the payer identifier for various payer identifiers using one type of scanning equipment.

Meanwhile, the seller interface unit 110 generates one or more service-linked payer identifiers for linking with one or more payment services based on the acquired payer identifier, and selects one or more service-linked payer identifiers for the seller among the generated one or more service-linked payer identifiers. The payer's payment information can be input to match the service-linked payer identifier selected.

For example, if the seller interface unit 110 obtains a payer identifier according to the A Pay (e.g. card company) payment service from the payment terminal 200, the seller interface unit 110 may use the service-linked payer identifier. A payer identifier according to the Pay payment service, B Payer identifier according to Bank (e.g. bank) payment service, C Payer identifier according to the payment integrated relay service, Payer identifier according to the electronic payment agency service, VAN A payer identifier according to the service and a payer identifier according to the electronic financial auxiliary business service are generated and output through the first output unit 112, and a service-linked payer identifier selected by the sales clerk among the output service-linked payer identifiers You can input the payer's payment information to match. Accordingly, the seller's cashier can make payment to the payer according to the desired payment method.

Through the first embodiment, the payment interface device 100 provided at the seller is divided into a seller interface unit 110 for the seller's cashier and a payer interface unit 120 for the payer, thereby performing payment at the seller. Convenience of payment can be improved by eliminating the inconvenience of city sales cashiers having to check the payment method directly with the purchaser.

In the above, the process of making payment to the payer, focusing on the linked operation of the seller interface unit 110 and the payer interface unit 120 included in the payment interface device 100, has been described in the seller terminal payment request method. Based on the configuration of the payment interface device 100 described above, the configuration adopted in this embodiment will be described below with reference to FIG. 3 to prevent the above-described security incident that occurs in the case of the payer terminal payment request method. .

The payment interface device 100 of this embodiment receives the payment information of the payer who purchased the product from the sales clerk, generates a payment information identifier (e.g., QR code, barcode, string, etc.) that is identification information of the payment information, and then makes the payment. The payment terminal 200 owned by the person may recognize the generated payment information identifier (by scanning or tagging) and output the payment information identifier so that payment for the payer can be requested from the payment server 300.

That is, the seller interface unit 110 of the payment interface device 100 receives the payer's payment information from the seller's cashier through the first input unit 111, generates a payment information identifier, and then sends it to the payer interface unit 120. The payer interface unit 120 transmits the payment information identifier to the second output unit 122 so that the payment terminal 200 can recognize the payment information identifier and request payment for the payer to the payment server 300. It can be printed through . Accordingly, the payment terminal 200 may recognize the payment information identifier output through the second output unit 122 of the payer interface unit 120 and request payment for the payer to the payment server 300.

At this time, the payment interface device 100 may obtain first time information about the time of generating the payment information identifier and generate authentication information for payment authentication of the payer, and specifically, modulate the first time information. Thus, a predefined type of modulation information (e.g., subaudible band modulated sound wave) can be generated as authentication information. Authentication information (i.e., falsification information) reflects the first time information about the time of generating the payment information identifier, so it has a one-time characteristic, so if you try to make a payment by copying it with malicious intent, the payment can be invalidated. It has characteristics that are If the modulation information is generated in the form of a sub-audible band modulated sound wave, the directionality and intensity of the sub-audible band modulated sound wave may be determined so that the payment terminal can detect (scan or tag) the payment information identifier. It may be set to receive blue band modulated sound waves.

Accordingly, whether to proceed with a payment request for the payer made through the payment terminal 200 may be determined based on a comparison result between the first time information identified from the authentication information and the reference time information. Since the authentication information is modulation information generated by modulating the first time information, the first time information identified to determine whether to proceed with the payment request can be identified through demodulation of the modulation information. In addition, the above reference time information may be second time information about the time when authentication information is obtained by the payment terminal 200, and accordingly, the payment request for the payer made through the payment terminal 200 is the first time information. It can proceed only when the error between the time information and the second time information is less than or equal to a preset standard value (that is, the payment terminal 200 sends the payment server 300 to the payment server 300 only when the error between the first time information and the second time information is less than the standard value. Payment may be requested).

In other words, there may be a predetermined time difference between the time when the payment information identifier is generated (first time information) and the time when the payment terminal 200 acquires authentication information (second time information), so taking that time difference into consideration After preparing the above reference value, the payment terminal 200 can request payment to the payment server 300 only when the error between the first time information and the second time information is less than or equal to the reference value.

Accordingly, it is possible to make it impossible to make a payment through a payment information identifier output through a medium other than the payment interface device 100 of this embodiment provided at the relevant store.

Figure 4 is a block diagram for explaining a payment interface system according to a second embodiment of the present invention, and Figure 5 is an exemplary diagram showing an implementation example of a payment interface system according to a second embodiment of the present invention. 6 is an example diagram for explaining the operation of the payment interface system according to the second embodiment of the present invention.

Referring to FIG. 4, the payment interface system 1000 according to the second embodiment of the present invention may include a mobile communication terminal 130 for a seller and an interface unit 120 for a payer, and a mobile communication terminal for a seller. Unit 130 may include one or more mobile communication terminals for payment processing at a merchant. The mobile communication terminal 130 for the seller and the interface unit 120 for the payer can perform payment for the payer through communication with the payment terminal 200 and the payment server 300.

The second embodiment is an embodiment in which the seller interface unit 110 in the first embodiment is replaced with each mobile communication terminal included in the seller mobile communication terminal unit 130, and through the second embodiment, the seller terminal (The second embodiment presents a method of operating the payer interface unit 120) in conjunction with a mobile communication terminal such as a smartphone or tablet carried by a sales clerk, or its universal operating system (OS).

As a premise for this, the payment service application distributed in the form of software running on the OS (e.g. Android OS) installed on each mobile communication terminal can be installed and operated in the payer interface unit 120, the payer interface unit (120) may have the same OS installed as the mobile communication terminal. For example, the same OS as the OS installed in the mobile communication terminal is installed in the payer interface unit 120, so that the A Bank application, B Bank application, or C Pay application running on the OS installed in the mobile communication terminal is installed in the payer interface unit. It can be operated in conjunction with (120).

Furthermore, in the second embodiment, it is indicated as 'mobile communication terminal' to clarify the entity that replaced the seller interface unit 110 of the first embodiment, and an application that provides the functions performed by the mobile communication terminal described below Any installed terminal can function as a mobile communication terminal of the second embodiment (e.g., not only a dedicated terminal manufactured by a terminal manufacturer, but also a general-purpose terminal (e.g., an Android smartphone) can function as a mobile communication terminal of the second embodiment if the application is installed. can function as a terminal).

Based on the foregoing, the operation of the payment interface system 1000 according to the second embodiment will first be described in terms of a payment request method from a merchant terminal.

The payer interface unit 120 can be combined with each mobile communication terminal included in the seller mobile communication terminal 130, and provides the payer with the payment information of the payer who purchased the product entered into each mobile communication terminal. can do.

Each mobile communication terminal included in the seller's mobile communication terminal 130, while coupled to the payer's interface unit 120, receives the payer identifier, which is the payer's identification information, from the payment terminal 200 held by the payer. The payment information of the payer may be obtained and input to match the acquired payer identifier, and payment for the payer may be requested to the payment server 300 based on the input payment information.

As a specific example with reference to FIG. 5, when there are a plurality of sales clerks, each mobile communication terminal 131, 132 possessed by each sales clerk constitutes a mobile communication terminal unit 130 for the seller, and the first sales clerk When the first mobile communication terminal 131 carried by the cashier is combined with the payer interface unit 120, it can perform the same function as the payment interface device 100 described in the first embodiment. Accordingly, the first mobile communication terminal 131 is coupled to the payer interface unit 120, and the payer receives the payment (via the payer interface unit 120 or directly) from the payment terminal 200 possessed by the payer. Obtain an identifier, receive the payer's payment information through an input unit (input button or touch panel, etc.) provided in the first mobile communication terminal to match the acquired payer identifier, and send the payer's payment information to the payer based on the entered payment information. Payment may be requested to the payment server 300.

Next, the operation of the payment interface system 1000 according to the second embodiment will be described in terms of the payer terminal payment request method.

Each mobile communication terminal included in the mobile communication terminal 130 for a seller, while coupled to the interface unit 120 for a payer, receives payment information of the payer and uses a payment information identifier, which is identification information of the input payment information. It can be generated (a dedicated application for generating a payment information identifier may be installed in each mobile communication terminal) and transmitted to the payer interface unit 120. In addition, the payer interface unit 120 may output a payment information identifier so that the payment terminal 200 owned by the payer can recognize the payment information identifier and request payment for the payer from the payment server 300. Accordingly, the payment terminal 200 obtains the payment information identifier output by the payer interface unit 120 (e.g., a barcode output by the second output unit 122 of the payer interface unit 120 or Payment can be requested from the payer to the payment server 300 (obtained by tagging a QR code).

In the above case, the mobile communication terminal that is invalid due to hacking, etc. transmits a forged payment information identifier to the payer interface unit 120, so the forged payment information identifier is output from the payer interface unit 120 and the payer A security incident may occur during payment. The configuration of this embodiment adopted to solve this problem will be described with reference to FIG. 6.

Referring to FIG. 6, each mobile communication terminal in this embodiment is coupled to the payer interface unit 120, receives the payer's payment information, and sends authentication information for validating the validity of each mobile communication terminal to the payer interface. It receives input from the unit 120 (the time-series order of receiving payment information and authentication information may vary depending on the actual implementation), and uses the input payment information and authentication information to create a payment information identifier for the payer's payment. After being created, it can be delivered to the payer interface unit 120. Here, the authentication information may include a seller identifier, which is identification information for the seller, stored in the interface unit 120 for the payer, or a unique authentication identifier, which is identification information for the interface unit 120 for the payer.

Accordingly, the payer interface unit 120 can proceed with payment to the payer only when the validity of each mobile communication terminal is authenticated based on authentication information extracted from the payment information identifier received from each mobile communication terminal (i.e. , the payment information identifier received from each mobile communication terminal can be output only when the validity of the mobile communication terminal is certified).

Specifically, the payer interface unit 120 includes authentication information transmitted to each mobile communication terminal while stored in the payer interface unit 120, and authentication information extracted from the payment information identifier received from the mobile communication terminal. If they match, it can be determined that the validity of each mobile communication terminal has been authenticated.

That is, each mobile communication terminal generates a payment information identifier so that the vendor identifier or unique authentication identifier stored in the payer interface unit 120 is reflected in the payment information identifier, and the payer interface unit 120 receives the payment information from the mobile communication terminal. A vendor identifier or unique authentication identifier is extracted from the feedback payment information identifier, and if the extracted vendor identifier or unique authentication identifier matches the vendor identifier or unique authentication identifier stored by the user, the validity of each mobile communication terminal is certified. After determining, the payment information identifier can be output. If the extracted vendor identifier or unique authentication identifier is different from the vendor identifier or unique authentication identifier stored by the customer, it is determined that the payment information identifier was created by an invalid mobile communication terminal, and payment is processed for the payer. can be stopped.

7 to 12 are exemplary diagrams for explaining the operation of the payment interface system in the third embodiment of the present invention.

The payment interface system 1000 described in the third embodiment maintains the operation of the seller mobile communication terminal 130 and the payer interface unit 120 of the second embodiment, which operate in the payer terminal payment request method, However, there are differences in who and how the payer performs payment authentication. The following will focus on the subject and method of payment authentication.

As in the second embodiment, the seller's mobile communication terminal 130 may include one or more mobile communication terminals, and the payer's interface unit 120 may be combined with each mobile communication terminal, and the payer's interface unit 120 may be combined with each mobile communication terminal. Payment information can be provided to the payer. The payer's payment information may be input through the seller interface unit 110 and transmitted to the payer interface unit 120, or may be input through the payer interface unit 120 and transmitted to the seller interface unit 110. It may be possible.

In addition, in the third embodiment, each mobile communication terminal is coupled to the payer interface unit 120, generates authentication information for payment authentication of the payer, and outputs the generated authentication information to enable payment held by the payer. The terminal 200 can recognize authentication information. And, the payment information identifier (i.e., a payment information identifier that is recognized by the payment terminal 200 and performs a function of allowing the payment terminal 200 to request payment for the payer from the payment server 300) is the payment information identifier of the payer. It can be generated and output based on the information.

Accordingly, the payment server 300 processes the payment from the payment terminal 200 according to a comparison result between the authentication information recognized by the payment terminal 200 and the authentication information extracted from the payment information identifier by the payment terminal 200. You can decide whether to approve the request.

That is, in the third embodiment, the function of generating and outputting authentication information and the function of generating and outputting payment information identifier are configured to be performed by sharing the mobile communication terminal and the payer interface unit 120, and the payment terminal ( Only when the combination of the mobile communication terminal and the payer interface unit 120 is valid by performing authentication by comparing the authentication information recognized by 200 and the authentication information extracted from the payment information identifier by the payment terminal 200 Security can be improved because payment authentication can be performed.

When generating authentication information, each mobile communication terminal may generate authentication information using one or more of a vendor identifier and a seller identifier. As described above, the seller identifier refers to identification information about the seller. Additionally, the seller identifier refers to identification information for a mobile communication terminal, and when there are multiple seller cashiers at one seller, it can function as information to identify each seller. Furthermore, each mobile communication terminal may generate authentication information by further using the first time information about the current time.

With reference to FIGS. 7 to 9 , operations when a mobile communication terminal generates authentication information using a vendor identifier and first time information will be described.

Each mobile communication terminal can receive the vendor identifier stored in the payer interface unit 120 from the payer interface unit 120, modulate it, and generate and output modulated information of a predefined type as authentication information. At this time, as described above, first time information about the current time may also be reflected in the modulation information. Afterwards, each mobile communication terminal receives the payer's payment information (the time-series order in which the generation of the falsification information and the input of the payment information takes place may vary depending on the actual implementation).

Thereafter, a payment information identifier may be generated based on the payer's payment information input through the mobile communication terminal and the vendor identifier stored in the payer interface unit 120. The entity that generates the payment information identifier may be a mobile communication terminal or a payer interface unit 120. That is, as shown in FIG. 7, the mobile communication terminal receives the payer's payment information from the seller's cashier, generates a payment information identifier based on the payment information and the seller identifier, and then transmits the payment information to the payer interface unit 120 to make the payment. A payment information identifier may be output through the user interface unit 120, and as shown in FIG. 8, the mobile communication terminal receives the payer's payment information from the store cashier, transmits it to the payer interface unit 120, and makes the payment. The payment information identifier may be generated and output based on the payment information of the payer received by the user interface unit 120 and the store identifier stored. As shown in FIG. 9, the interface unit 120 for the payer may make the payment. The user's payment information may be input from the sales clerk and transmitted to the mobile communication terminal, and a payment information identifier may be generated and output based on the payment information and the vendor identifier received by the mobile communication terminal.

Thereafter, the payment server 300 requests payment from the payment terminal 200 when the seller identifier identified through demodulation of the modulated information recognized by the payment terminal 200 matches the seller identifier extracted from the payment information identifier. can be approved.

That is, the payment server 300 receives the seller identifier identified as a result of the payment terminal 200 recognizing and demodulating the modulated information output through the mobile communication terminal, and sends it to the mobile communication terminal or the payer interface. After the payment terminal 200 recognizes the payment information identifier output through the unit 120, the extracted vendor identifier is transmitted from the payment terminal 200, and if the two received vendor identifiers match, the payment terminal 200 Payment request can be approved.

Meanwhile, as a step before whether or not the payment request is approved by the payment server 300, as shown in FIGS. 7 to 9, a payment request to the payer made through the payment terminal 200 is made through the payment terminal. It may proceed only when the error between the first time information recognized based on the authentication information recognized by 200 and the second time information about the time when the authentication information was acquired by the payment terminal 200 is less than or equal to a preset standard value. . That is, like the first embodiment, the payment terminal 200 includes first time information determined as a result of demodulating the authentication information (i.e., modulation information) output through the mobile communication terminal, and information about the time when the authentication information was obtained. Payment can be requested from the payment server 300 only when the error between the second time information is below the standard value.

Next, with reference to FIG. 10, the operation when the mobile communication terminal generates authentication information using the seller identifier and first time information will be described.

Each mobile communication terminal can modulate the seller identifier stored in each mobile communication terminal to generate and output falsification information of a predefined type as authentication information. At this time, as described above, first time information about the current time may also be reflected in the modulation information. Afterwards, each mobile communication terminal receives the payer's payment information (the time-series order in which the generation of the falsification information and the input of the payment information takes place may vary depending on the actual implementation).

Thereafter, a payment information identifier may be generated based on the payer's payment information input through the mobile communication terminal and the vendor identifier stored in the payer interface unit 120. FIG. 10 shows an example in which the entity that generates the payment information identifier is the payer interface unit 120. However, as described above, the entity that generates the payment information identifier may be a mobile communication terminal.

Thereafter, the payment server 300 determines whether the relationship between the seller identifier identified through demodulation of the modulated information recognized by the payment terminal 200 and the seller identifier extracted from the payment information identifier satisfies a predefined correspondence relationship. A payment request from the payment terminal 200 may be approved.

In other words, as mentioned above, the seller identifier refers to identification information for a mobile communication terminal, and considering that it functions as information to identify each seller when there are multiple seller cashiers at one seller, multiple seller identifiers are used. A 1:N mapping relationship (N is the number of seller identifiers) that is dependently linked to one seller identifier can be defined. Therefore, with the correspondence relationship between this seller identifier and the seller identifier dependent thereon defined in the payment server 300, the payment server 300 provides a plurality of seller identifiers linked to the seller identifier extracted from the current payment information identifier. Among them, if there is a seller identifier identified through demodulation of the modulated information recognized by the payment terminal 200, it is determined that the above correspondence relationship is satisfied, and the payment request from the payment terminal 200 can be approved.

As a step before whether or not the payment request is approved by the payment server 300, as shown in FIG. 10, a payment request to the payer made through the payment terminal 200 is processed by the payment terminal 200. It may proceed only when the error between the first time information determined based on the recognized authentication information and the second time information about the time when the authentication information was acquired by the payment terminal 200 is less than or equal to a preset standard value, and the configuration is as described above. Since this is the case, detailed explanation will be omitted.

Meanwhile, Figure 10 shows an example in which the entity that generates and outputs the authentication information is the mobile communication terminal. However, depending on the embodiment, after the mobile communication terminal generates the authentication information as shown in Figure 11, the interface unit for the payer It may be implemented in an embodiment in which the payment terminal 200 recognizes the authentication information by transmitting it to 120 and the payer interface unit 120 outputting the authentication information. In an example where the authentication information is an inaudible band modulated sound wave, the authentication information may be output through the voice/sound wave output device of the second output unit 122 of the payer interface unit 120.

In addition, in Figure 10, the first payment authentication, that is, the process of determining whether the error between the first time information and the second time information is less than or equal to the standard value, which is performed prior to determining whether to approve the payment request from the payment terminal 200, is performed. Although an example of being performed by the payment terminal 200 as a condition of a payment request is shown, primary payment authentication may be implemented by being performed by the payment server 300 as shown in FIG. 11 . In this case, the payment server 300 provides first time information determined based on the authentication information recognized by the payment terminal 200, and the current time (i.e., the current time when the payment server 300 performs the first payment authentication). ) Only when the error between the second time information is less than or equal to a preset standard value, the secondary payment authentication process that determines whether to approve the payment request from the payment terminal 200 can be initiated.

In the above, it has been described as a configuration in which the mobile communication terminal generates authentication information by selectively using the vendor identifier and the seller identifier. Depending on the embodiment, the mobile communication terminal uses both the vendor identifier and the seller identifier as authentication information to provide payment information identifier. A payment authentication process may be accomplished by being generated, output, and analyzed by the payment server 300 (as in the embodiment described above, the authentication information is modulated information generated by modulating the seller identifier or seller identifier together with the first time information). Rather than meaning, the vendor identifier and seller identifier themselves function as authentication information used to create a payment information identifier).

In this case, each mobile communication terminal is coupled to the payer interface unit 120 and uses the authentication information for payment authentication of the payer and the payer's payment information received from the payer interface unit 120 to make the payer's payment. A payment information identifier may be generated, and the payment information identifier may be output so that the payment terminal 200 owned by the payer can recognize the payment information identifier and request payment for the payer from the payment server 300. In addition, the payment server 300 may determine whether to approve the payment request from the payment terminal 200 according to the analysis result of the authentication information extracted from the payment information identifier by the payment terminal 200.

To be described in detail with reference to FIG. 12 , the mobile communication terminal transmits the vendor identifier stored in the payer interface unit 120 and the payment information input through the payer interface unit 120 from the payer interface unit 120. You can receive it. Accordingly, the mobile communication terminal can generate a payment information identifier using the seller identifier stored in the mobile communication terminal, the seller identifier and payment information received from the payer interface unit 120, and then output the payment information identifier.

Thereafter, the payment server 300 may approve the payment request from the payment terminal 200 if the relationship between the seller identifier and the seller identifier extracted from the payment information identifier by the payment terminal 200 satisfies a predefined correspondence relationship. You can.

That is, in the above case, since both the vendor identifier and the seller identifier are reflected in the payment information identifier, the vendor identifier and the seller identifier can be extracted through the payment terminal 200 that recognizes the payment information identifier, and the extracted vendor identifier and If the seller identifier satisfies a predefined correspondence relationship, the payment request from the payment terminal 200 may be approved. Since the explanation for this has been described above, detailed explanation will be omitted.

Figure 13 is an example diagram for explaining the operation of the payment interface system according to the fourth embodiment of the present invention.

The payment interface system 1000 described in the fourth embodiment includes the operations of the seller mobile communication terminal 130 and the payer interface unit 120 of the second and third embodiments that operate in the payer terminal payment request method. It also presents a configuration that improves payment security by performing pre-authentication in stages before the payment terminal 200 makes a payment request to the payment server 300.

Meanwhile, separately from the terms used in the first to third embodiments described above, the terms used in the fourth embodiment will first be defined. In the fourth embodiment, the seller identifier is defined to mean identification information about the seller (e.g., a seller logged in to a payment application running on a mobile communication terminal to make a payment to the payer), and the terminal identifier is It is defined to mean the unique identifier of a mobile communication terminal. In addition, the first identifier indicated below is defined as including one or more of a seller identifier and a terminal identifier. The seller identifier and the unique authentication identifier are used in the same sense as in the previously described embodiment, and the second identifier hereinafter is defined as including one or more of the seller identifier and the unique authentication identifier. Based on these term definitions, the operation of the payment interface system 1000 of the fourth embodiment will be described.

The mobile communication terminal 130 for the seller may include one or more mobile communication terminals, and the interface unit 120 for the payer may be combined with each mobile communication terminal, and may transmit the payment information of the payer who purchased the product to the mobile communication terminal. It can be input from and provided to the payer.

In the fourth embodiment, each mobile communication terminal may transmit authentication information for authentication of combination validity, which is required for performing payment to the payer, to the external server 300. Here, the combination effectiveness may include one or more of the first combination effectiveness between the seller and the vendor, and the second combination effectiveness between each mobile communication terminal and the payer interface unit 120. The first combination validity indicates whether the combination between the seller and the vendor is a previously registered valid combination, and the second combination validity indicates whether the combination between the mobile communication terminal and the payer interface unit 120 is a previously registered valid combination ( Specific explanation will be provided later). The external server 300 functions as a separate server provided for authentication of the validity of the combination described above, and may store information about the authentication relationship required to authenticate the validity of the combination. Accordingly, the external server 300 may determine that the combination validity is authenticated when the authentication information received from the mobile communication terminal satisfies a predefined authentication relationship. This external server 300 may be implemented independently from the payment server 300, or may be implemented in an embodiment in which the payment server 300 performs the functions of the external server 300 in an integrated manner, and the external server 300 ) may be implemented in a configuration that includes the payment server 300. For convenience, in FIG. 13, the payment server and external server are indicated using the same reference numerals.

The mobile communication terminal can operate as an authentication terminal that performs payment to the payer only when the validity of the combination is certified by the external server 300. Operating as an authentication terminal that performs payment for the payer means that, for example, the function of receiving the payer's payment information from the sales clerk and transmitting it to the payer interface unit 120 is activated, so that the payer's payment can be made normally. It can mean.

The operation of the payment interface system 1000 described above will be described in detail with reference to FIG. 13.

First, before the payment process for the payer proceeds, an authentication communication link for authentication of combination validity may be established between each mobile communication terminal and the payer interface unit 120. The authentication communication link is a lower layer communication link through which a second identifier is transmitted from the payer interface unit 120 to the mobile communication terminal for authentication of combination validity, such as a short-range wireless communication link such as Bluetooth or a short-range wired communication link according to a USB connection. It can be implemented as a P2P communication link, such as a communication link. After the authentication communication link is established, as the second identifier is transferred from the payer interface unit 120 to the mobile communication terminal, authentication information including the first and second identifiers is transferred from the mobile communication terminal to the external server 300. It can be.

Accordingly, the external server 300 may determine that the combination validity is authenticated when the received authentication information satisfies a predefined authentication relationship. In the case of an embodiment in which the first and second identifiers are a seller identifier and a seller identifier, respectively, the external server 300 may determine that the first combination validity is authenticated when the seller identifier and the seller identifier satisfy a predefined authentication relationship. there is. At this time, the pre-defined authentication relationship may mean information already registered in the external server 300 as a correspondence relationship between the seller and the seller to determine whether the seller is an authorized seller to sell products or services at the relevant seller. there is.

Meanwhile, in the case of an embodiment in which the first and second identifiers are a terminal identifier and a unique authentication identifier, respectively, the external server 300 determines the validity of the second combination when the terminal identifier and the unique authentication identifier satisfy a predefined authentication relationship. It can be judged that At this time, the predefined authentication relationship is a correspondence relationship between the mobile communication terminal and the payer interface unit 120 to determine whether the combination of the mobile communication terminal and the payer interface unit 120 is valid, and is sent to the external server 300. It may mean already registered information.

When the validity of the combination is authenticated by the external server 300, the authentication result may be transmitted to the mobile communication terminal, thereby performing payment for the payer between each mobile communication terminal and the payer interface unit 120. A payment communication link may be established for The payment communication link may refer to a higher layer communication link through which payment information input to the mobile communication terminal is transmitted to the payer interface unit 120 so that the actual payment process for the payer can proceed.

When the payment communication link is established through the above-described process, each mobile communication terminal can receive the payer's payment information from the store's cashier and transmit it to the payer interface unit 120 along with the first identifier. In addition, the payer interface unit 120 uses the payer's payment information, the first identifier, and the second identifier to generate a payment information identifier for the payer's payment, and the payment terminal 200 held by the payer uses the payment information identifier. By recognizing the payment information identifier, a payment information identifier can be output so that payment for the payer can be requested from the payment server 300. Accordingly, the payment terminal 200 can request payment to the payment server 300 by recognizing the payment information identifier output to the payer interface unit 120.

Thereafter, the payment server 300 may determine whether to approve the payment request from the payment terminal 200 by verifying whether the first and second identifiers extracted from the payment information identifier by the payment terminal 200 are authenticated. That is, the payment server 300 verifies whether the validity of the combination of the first and second identifiers has been certified by the external server 300, and then approves the payment request from the payment terminal 200 only when verified. Payment can be completed to the payer.

Meanwhile, as a method for the payment server 300 to verify authentication between the first and second identifiers, the authentication relationship defined in the external server 300 described above is also defined in the payment server 300, and the first and second identifiers are A method in which the payment server 300 secondarily determines whether the identifier satisfies the authentication relationship may be applied. As another embodiment, when the external server 300 determines that the first and second identifiers satisfy the authentication relationship, the external server 300 adds a predetermined authentication flag to the authentication result transmitted to the mobile communication terminal. Then, the payer interface unit 120 generates a payment information identifier using the payment information, the first and second identifiers, and an authentication flag, and then uses the authentication flag extracted from the payment information identifier by the payment terminal 200. The payment server 300 may verify authentication between the first and second identifiers.

In this way, this embodiment can improve payment convenience by dividing the vendor terminal provided at the vendor into an interface device for the vendor cashier and the purchase payer, and the vendor identification code transmitted from the purchase payer is stored in the vendor terminal. Payment security can be improved by adopting a system that verifies whether the printed identification code corresponds to the actual identification code.

The present invention has been described with reference to the embodiments shown in the drawings, but these are merely illustrative, and those skilled in the art will recognize that various modifications and other equivalent embodiments can be made therefrom. You will understand. Therefore, the true technical protection scope of the present invention should be determined by the scope of the patent claims below.

1000: Payment interface system
100: Payment interface device
110: Interface unit for seller
111: first input unit
112: first output unit
120: Interface unit for payer
121: second input unit
122: second output unit
130: Mobile communication terminal for seller
131, 132: first and second mobile communication terminals
200: Payment terminal
300: Payment server, external server

Claims (3)

After receiving the payment information of the payer who purchased the product and generating a payment information identifier, which is identification information of the payment information, the payment terminal owned by the payer recognizes the generated payment information identifier and makes payment for the payer. A payment interface device that outputs the payment information identifier so that it can be requested from a payment server,
The payment interface device generates authentication information for payment authentication of the payer, and generates the authentication information by reflecting first time information about the current point in time at which the authentication information is generated,
A payment request for the payer made through the payment terminal is approved based on the results of a comparison process between the first time information identified from the authentication information and the reference time information performed by the payment server. become,
The reference time information is second time information about the current time when the payment server performs the comparison process.
According to paragraph 1,
The payment interface device modulates the first time information to generate modulation information of a predefined type as the authentication information,
The payment interface device characterized in that the first time information identified in the comparison process is determined through demodulation of the modulation information.
According to paragraph 1,
A payment interface, characterized in that the payment request for the payer made through the payment terminal can be approved by the payment server only when the error between the first time information and the second time information is less than or equal to a preset standard value. Device.