KR100444372B1 - System and method for paying money electric commerce - Google Patents

Abstract

end. The technical field to which the invention described in the claims belongs

The present invention relates to a system and method for performing payment in an electronic commerce system.

I. The technical problem to be solved by the invention

The present invention provides a system and a method for preventing an external intrusion during electronic money distribution such as electronic commerce or payment of various payments.

All. Summary of Solution of the Invention

The system according to an embodiment of the present invention is a system for providing data for payment and payment processing in electronic commerce, and a network connection unit for accessing a user terminal, a financial institution server, and a product providing server online to perform data interface. And a tag file memory for generating payment data upon payment request by configuring a sales information display area for a product to be provided, and storing data for generation and encryption of data structure information about the product, and request for payment request. A sales information memory for storing the received payment information and the payment result information, and controlling the provision of data in the tag file memory when data for payment is requested, and storing the sales information for payment request information and payment result information when payment is requested. Control and perform a control for payment with the financial institution server, The first result is characterized in that at least a control unit for performing control for delivering the goods providing server.

la. Important uses of the invention

It is used when you want to set up security for money distribution online.

Description

Payment system and method in e-commerce system {SYSTEM AND METHOD FOR PAYING MONEY ELECTRIC COMMERCE}

The present invention relates to a payment system and method of payment, and more particularly to a payment system and method of payment in an electronic commerce system.

Commerce is usually accomplished by delivering goods and paying the delivery price for the purpose of trading the goods. Such commerce has been developed to be made online through the development of communication network and the development of Internet communication, and the concept of electronic commerce has been derived. Looking at the development of such electronic commerce as follows.

Electronic commerce has been developed in the form of buying and selling goods between companies, thanks to the development of Electronic Data Interchange (EDI). These e-commerce initially developed from one-to-one or one-to-one (N) to one-to-one (N: N) trading relationships. In recent years, e-commerce has developed into a complex trading relationship of N: N. Electronic commerce is actively being conducted for a large number of unspecified buyers or between individuals. As the electronic commerce is vigorous, various kinds of products are being sold in the form of selling only specific items.

That is, as well as the basic goods, there are so many kinds of products are distributed such that there is no sale of information, education via the Internet, telemedicine, and products that cannot be distributed online. Then, the basic sales method of the goods or goods among these products will be described below with two representative examples.

First, a buyer visits a site that sells a product such as a shopping mall or a specific purchase site online, checks the price of the product and information about the product, and then orders the product online. This can be accepted by an internet shopping mall or a specific purchase site. In this way, when the purchase intention is confirmed, payment is made automatically or at the site where the purchase intention is received. At this time, the payment is made by using a credit card or a giro paper or e-money. When the payment is made in this way, the goods are supplied and the receiver purchases the desired goods.

Another method of providing a product is to distribute it to an unspecified number of buyers by using various devices including a list of goods, such as a CD or a diskette, and the buyer having the product confirms it offline and then purchases the product online. There is a case. In this case, the procedure after the purchase of the product is the same.

Therefore, when a product is purchased as described above, the user informs the site that provides the product of various information such as a destination for receiving the product, details of the product to be purchased, and credit card information of the buyer. This is also a feature of electronic commerce.

However, there is a possibility that the information may be forged or altered by a person having an impure purpose. This is because the information in the above description is almost defenseless online. In addition, there is almost no way to protect the user's information when hacking the site for impure purposes. Therefore, the leakage of personal information in electronic commerce is intensifying and becoming a social problem. In addition, when the payment is made online via the Internet when the payment is made, there is a risk that the buyer and the product supplier may cause a great loss if the information is forged or altered by a person with impure intention.

Accordingly, an object of the present invention is to provide a system and method that can provide security when payment is made in an electronic commerce system.

Another object of the present invention is to provide a system and method capable of maintaining security of information of a buyer in an electronic commerce system.

It is still another object of the present invention to provide a system and method capable of maintaining security of a buyer's information and a database stored in a site in an electronic commerce system.

According to an embodiment of the present invention for achieving the above object, a security providing server for providing payment tag file generation data for payment to the product providing server and receiving payment request information from the user terminal to perform the payment; And a payment request information having the product providing server for generating a payment tag file with the generated data from the security providing server and transmitting the product to the user terminal with product description information, and the payment tag file from the product providing server. In the electronic commerce system comprising the user terminal to generate and transmit to the security providing server, the security providing server device is connected to the user terminal, the financial institution server and the product providing server network connection unit for performing data interface And, for the payment of goods sold in the product providing server A tag file memory for storing generated data for generating a payment tag file, a sales information memory for storing payment request information received from the user terminal and payment result information received from the financial institution server, and the product providing server Read the payment tag file generated data from the tag file memory when the data request for payment is received from the tag file memory and transmits the generated data to the product providing server, and receives the payment request information from the user terminal to the financial institution server. And a control unit for performing payment by access, receiving payment result information from the financial institution server, storing the payment result information in the sales information memory, and transmitting the payment result information to the product providing server and the user terminal. .

In addition, according to an embodiment of the present invention for achieving the above object, a security providing server for providing the payment tag file generation data for the payment to the product providing server, and the payment with the generated data from the security providing server A product providing server for generating a tag file and transmitting the product description information to the user terminal, and generating the payment request information with the payment tag file from the product providing server and transmitting the generated payment request information to the security providing server. In the e-commerce system comprising a, the payment method of the security providing server, when receiving a data request for payment from the product providing server, the process of checking whether the normal subscriber, and the product providing server is registered as a normal subscriber If so, for the payment of goods sold in the product providing server Transmitting data for generating a payment tag file to the product providing server, requesting payment processing by accessing a financial institution server with the payment request information when receiving payment request information from the user terminal; Receiving payment approval information from a financial institution server, storing the result data for the payment, and transmitting the result data for the payment to the product providing server and the user terminal.

1 is a configuration diagram of a schematic connection for explaining a payment processing procedure in an electronic commerce system according to the present invention;

2 is a block diagram of a security providing server according to an embodiment of the present invention;

3 is a view showing an example of contents posted for sale in an electronic mail or distribution CD or server in the product providing server 20 according to an embodiment of the present invention,

4 is a diagram illustrating an example of information included in a tag file provided corresponding to a sales information display area according to the present invention;

FIG. 5 is a flowchart illustrating a process of reading and paying a sales file having security tag information according to an exemplary embodiment of the present invention; FIG.

FIG. 6 is a view illustrating an example of a screen displayed for listing details required for payment to a user when a purchase of goods is required according to an embodiment of the present disclosure;

7 is a view showing the configuration of a tag file consisting of payment information according to a preferred embodiment of the present invention;

8A to 8B are flowcharts illustrating a process of providing encryption information and a tag file and receiving payment information and processing according to a security providing server according to an exemplary embodiment of the present invention.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. First of all, in adding reference numerals to the components of each drawing, it should be noted that the same reference numerals have the same reference numerals as much as possible even if displayed on different drawings.

In addition, in the following description, there are many specific matters such as the configuration of a specific circuit, which are provided to help a more general understanding of the present invention, and the present invention may be practiced without these specific matters. It will be self-evident to those of ordinary knowledge. In the following description of the present invention, if it is determined that a detailed description of a related known function or configuration may unnecessarily obscure the subject matter of the present invention, the detailed description thereof will be omitted.

1 is a schematic diagram of a connection for explaining a payment processing procedure in an electronic commerce system according to the present invention. Hereinafter, a process of performing payment in an electronic commerce system and an operation of each system will be described in detail with reference to FIG. 1.

First, the security providing server 100 performs the payment of the product according to the present invention, and provides the result. In addition, the security providing server 100 to the product providing server 20, which is a product provider, information necessary for payment of goods, for example, encryption information and information for composing various data necessary for payment (payment tag file generation data) To provide. In addition, according to the present invention, the security providing server 100 provides viewers or product providers with viewer information for displaying on the screen information for payment at the time of purchase. When the payment request is made, the security providing server 100 provides the financial institution server 30 with information necessary for financial settlement, receives the payment result, and delivers the result to the buyer terminal and the product providing server 20 to supply the product. Informs the result of the sale. Trading of the product is an embodiment of the present invention. Therefore, even if the non-sale price of other goods, which will be described later payment of the price is made and informs it to the server or terminal.

The connection 35 between the security providing server 100 and the financial institution server 30 may be connected through a dedicated line or a dedicated network or an internet network capable of performing data communication. In addition, the connection 25 between the security providing server 100 and the product providing server 20 may also be connected through a dedicated line or a dedicated network or an internet network capable of performing data communication. The product providing server 20 may be a server that provides a product to various sites such as a general shopping mall site or an auction or stock information trading site. Therefore, the product providing server 20 is connected to a plurality of unspecified buyers through the Internet or wired communication network through a dedicated line or a wireless communication network. In addition, the purchaser terminal 10 generally becomes a personal computer connected by wire or various terminals such as a personal digital assistant (PDA) and a mobile phone connected through a wireless network. Through this, the purchaser terminal 10 becomes a terminal capable of performing data communication. As described above, the method of connecting to the security providing server 100 also depends on the type of the purchaser terminal 10. The construction method of such a network will not be discussed in the present invention. In addition, the purchaser terminal 10 should be able to store viewer data provided according to the present invention.

When performing payment in the security providing server 100 according to the present invention can be classified as follows according to the flow of goods.

First of all, this is a case where an actual product or information, such as a shopping mall site, an auction or a securities sale, information sale, etc., is performed. As described above, when the actual goods or securities and bonds or auction or the sale of information is performed, the product providing server 20 is operated.

Secondly, membership fees such as alumni, clubs or small groups, or Electronic Bill Presentment Payment (EBPP). This is a case where it is difficult to see that the actual goods are sold or the goods and information are distributed on / offline.

In the first case, the payment of the payment is described. In the first case, two methods can be used for payment. First, the seller provides a payment method for logging in whenever necessary in a state in which the seller is registered in the security providing server 100. Alternatively, there is a method of selling a program, a viewer, and the like for generating encrypted data and payment data by contract or the like in the same way as selling software. In other words, it is sold under a license agreement. At this time, the company information for purchasing the program and the viewer for generating the encrypted data and the payment data should be registered in the security providing server 100.

In this case, we look at the payment and distribution of goods for the actual goods. The manager of the product providing server 20 requests a payment means (payment tag file generation data) to the security providing server 100 when a new product to be sold is configured. Then, the security providing server 100 provides a payment means only when authentication is performed through the product providing server 20 and the authentication process. After acquiring the payment method as described above, the product providing server 20 generates data for sale of the product by using the payment means and posts it on the product providing server 20 or posts an advertisement such as an electronic catalog or e-mail. Distributed to buyers. In the case of the electronic catalog, it may be distributed through a CD or the like. That is, it can be distributed offline. Detailed description of this process will be described in more detail with reference to the accompanying drawings.

As described above, the secured catalog or posted product information is confirmed at the purchaser terminal 10 through the purchaser's access or confirmation of mail and CD. At this time, if the purchaser intends to purchase through his terminal 10, the purchaser writes data requesting a purchase. Then, the created purchase data is transferred to the security providing server 100 according to the present invention. The security providing server 100 receives this and performs a task related to payment with the financial institution server 30. Then, when receiving payment information from the financial institution server 30 stores it, and notifies the payment result to the buyer terminal. The order information is then notified to the product providing server 20 via email or other means.

In the first method, the license agreement is made. In the case where the license agreement is made, the company providing the product performs a packing operation without online information about the product. The packed product information is then posted or distributed in the manner described above. In this case, a payment tag file for payment is attached to the packed product information. The processing procedure is then performed as described above.

Next, we explain the process by which settlements such as alumni, clubs, small groups, or EBPP are made. In this case, the product providing server 20 illustrated in FIG. 1 may be a personal terminal instead of a server providing a product, or alternatively, a financial institution. That is, in the case of EBPP, it may be a financial institution, and in other cases, it may be a personal terminal or a server of the group.

In this case, the product providing server 20 logs in to the security providing server 100 and inputs a billing detail in a predetermined form. Then, the security providing server 30 packs it, generates it as a billing mail, and sends it to an e-mail address of a predetermined terminal. When the personal terminal 10 receives the request for payment of the request, the security providing server 100 performs the payment processing through the financial institution server 30 according to the information input by the user. After receiving the data on the payment result from the financial institution server 30 stores it and informs the result to the terminal. E-mail or the like can also be used at this time. After reporting the result as described above, the payment data is transmitted to the product providing server 20. At this time, if there is a predetermined server, such as the product providing server 20, and delivers to the server, otherwise the result is notified to the e-mail address of the requesting terminal.

2 is a block diagram of a security providing server according to a preferred embodiment of the present invention. Hereinafter, with reference to Figure 2 will be described in detail the configuration of the security providing server 100 according to the present invention and the operation of each configuration.

The controller 111 controls the overall operation of the security providing server 100 according to the present invention. Each operation performed by the control unit 111 according to the present invention will be described in detail with reference to a control flowchart to be described later. The network connection unit 112 interfaces with the product providing server 20, the financial institution server 30, and the user terminals of FIG. 1 through a predetermined network to transmit and receive data. Such a network may be various networks such as an internet network or a dedicated line network or a mobile communication network network.

The memory 113 stores various data necessary for controlling the control unit 111 and data according to an operating system. In addition, in the present invention, the memory 113, the tag file DB (Database) 114, and the sales information DB (Database) 115 are separately shown for convenience of understanding. The tag file DB 114 is configured to configure data for performing the encryption of the information of the goods sold according to the present invention and encryption of the payment information at the time of payment, and structure information of the generated data. Save the data. That is, when generating a file for sale, the tag file DB 114 stores data (payment tag file generation data) of a portion necessary for payment of the price. The payment tag file generation data is provided to the product providing server 20, the product providing server 20 generates a payment tag file with the generated data, and attaches the generated payment tag file to the product sales file Transmit to the user terminal 10.

Next, an embodiment of a file generated and provided by the product providing server 20 according to the present invention will be described with reference to FIG. 3. 3 is a diagram illustrating an example of contents posted for sale in an e-mail or a distribution CD or a server in a product providing server 20 according to an embodiment of the present invention.

The file configured for the sale of a certain product may be shown to buyers as shown in FIG. 3. Reference numeral 200 is a display area on which various details can be displayed on one screen configured for the sale of goods. In the display area, an image information display area 210 for displaying information of the merchandise on sale is formed at a predetermined position. In addition, the display area 200 includes a text information display area 220 for displaying information of goods in text. This may be configured to display voice information in addition to text information. In addition, according to the present invention is provided with a sales information display area 230 for generating information provided at the time of sale. In addition, the sales information display area 230 displays simple payment information in the case of an alumni association, a fellowship or a small group such as the membership fee and EBPP. That is, it becomes a payment information display area.

The tag file DB 114 stores data for configuring the sales information display area 230 or data for configuring all data included in the display area 200. Through this, the product providing server 20 provides it when requested.

On the other hand, the sales information display area 230 is linked to the payment tag file, when the data constituting the payment tag file can be shown in Figure 4 as shown in the figure. 4 is an example of information included in a tag file corresponding to a sales information display area according to the present invention.

The tag file includes an area for storing structure management information 310, an area for storing product information 320, an area for storing payment information 330, an area for storing product purchase information 340, and a seller. And an area for storing the information 350, an area for storing the delivery information 360, and an area for storing the data verification information 370. If necessary, the storage areas may be further provided or configured to be provided less than the details shown.

Then, when the goods sale information is composed of a single file such as an e-mail, it may be shown in Table 1 below.

Kinds Contents Header Sender information, recipient information,… Contents Encrypted Product History tag Encrypted Tag Information

Table 1 shows an example of a file composed of an e-mail according to the present invention. In the header, sender information, receiver information, and the like are input. In addition, as shown in FIG. 3, the data of the image information display area 210 of the display area 200, the data of the text information display area 220, and the respective areas 200, 210, 220, and 230 are shown. The constituent data is encrypted. In the tag, data of the payment tag file is stored as encrypted as shown in FIG. 4. In this way, the product providing server 20 constructs a file and provides it by e-mail or posts it on the product providing server 20 or distributes it using a distribution CD.

This will be described again with reference to FIG. 2.

The sales information DB 115 is an area for storing data according to sales details of a product. That is, when the purchase request data (or payment request data) is received from the purchaser terminal 10, the payment request is made to the financial institution server 30, and when the payment is normally completed, the memory area stores the payment request data.

The operator interface 116 connects with an operator of the security providing server 100 according to the present invention to perform interfacing. Therefore, an operator terminal may be connected or an input device such as a keyboard or a mouse may be directly connected. The graphic processor 117 converts the details processed by the security providing server 100 into graphic data and outputs the graphic data to the monitor. Through this, the operator checks the process processed by the security providing server 100 or grasps the state of the security providing server 100.

FIG. 5 is a flowchart illustrating a process of reading and paying a sales file with a secured payment tag file according to an exemplary embodiment of the present invention. 1 to 5 will be described in detail the process of viewing the sales file and the payment payment with the information of the tag file is secured according to the present invention in detail. In addition, in the following description, a file is received by a user terminal through an e-mail or a distribution CD, and a method of checking and performing the same will be described.

When the user executes the payment tag file by clicking the sales information display area 230 while the information of the sales information file is displayed (for example, while the contents of the e-mail are displayed) as shown in FIG. 3, the security provision server The program provided from (20) requests confirmation of user authority in step 400. That is, a process for checking whether a user is allowed to view a file through a general login screen or the like. If the user inputs data, the process proceeds to step 402 to check whether the user is allowed to read. Such data may be configured using the data verification information 370 shown in FIG. 4 among the tags of Table 1 or through a separate data area. As a result of checking the data input by the user, if the user is allowed to read, the process proceeds to step 406; otherwise, the process proceeds to step 404 to display an error. That is, step 402 is to check the read permission of the payment tag file attached to the sales file.

Steps 400, 402 and 404 may be configured to perform this only when security is required for the document or file. In other words, when security is not required, it may be configured to proceed directly to step 406 without configuring the above-described steps.

When the payment tag file can be read, as shown in FIG. 6, the encrypted information of the payment tag file is decrypted and displayed by using a predetermined viewer. This is performed in a processor of the user terminal. In this case, the key is received according to the user's key input and the display is changed. The change of the display and the reception of the key are generally control processes performed in the user terminal and thus will not be described in detail. As described above, the process proceeds to step 410 while performing the display and key reception to check whether payment is required. That is, it is checked whether the purchase button is input in FIG. If payment is required as a result of the inspection, the process proceeds to step 414; otherwise, the process proceeds to step 412 to check whether the end of the file is required. That is, it is checked whether the cancel button is input in FIG. 6. If the end of the inspection file is required, the opening of the file is terminated. However, if the end of the file is not required, continue with step 408.

FIG. 6 is a diagram illustrating an example of a screen displayed to input details required for payment to a user when a purchase of a product is required according to an embodiment of the present disclosure. The information input for the purchase is a user name, a social security number, and information such as issuer, purchase price, product name, expiration date, etc. are input, and payment information is input at the same time. Payment information is credit card information is entered when using the card, if the bankbook is a variety of information according to the receipt of the bankbook.

When the file is a security-required file, that is, configured to be accessible only to a specific user, the user information among the details shown in FIG. 6 may be configured to automatically display the details stored in the file. In other words, if the file is only viewable by the user, the file may be automatically displayed because the user's information is encrypted and stored in the file. Alternatively, even when encryption is set, the user information may be configured to be described. When the user information is not stored, the user information may be inputted through a key input in the user information area of FIG. 6.

In addition, the product information may be configured using the product information stored in the tag file. Therefore, in the case of product information, the user may be configured and illustrated in advance without directly inputting it. In addition to these matters, it is also possible to configure various additional details such as usage purposes, and in this case, a configuration change of the tag file shown in FIG. 4 may be required. If all of the payment information is described, the file proceeds to step 414 and the payment information is encrypted by the user terminal in advance through an encryption method. An example of data in which purchase information is encrypted as shown in FIG. 7 is shown. 7 is a diagram showing the configuration of a payment request file composed of payment information according to a preferred embodiment of the present invention. First, the payment request file will be described with reference to FIG. 7.

The payment request file 500 includes a structure management information 510 area, a billing history 520 area, a payment information 530 area, a claimant information 540, and data verification information 550. When the payment request file configured as described above is shown in a table, it may be shown in Table 2 below.

Kinds Contents Header Sender (buyer) information, receiver (security provision server) information, product provision server information… Contents Encrypted Product History tag Encrypted Tag Information

As shown in Table 2, the header displays the information of the buyer, the information of the receiver, and the information of the product providing server. However, the information of the product providing server may be configured to be included in the contents. In addition, when there is no special content in the above configuration, it may be configured so as not to leave the area of the content. This may allow the configuration of payment information to be selectively made by placing information on the configuration in advance when generating a file.

If the payment information is encrypted as described above, the user terminal requests the online connection of the product sales file in step 416. At this time, the online connection is to request a connection with the security providing server 100. Thereafter, the process proceeds to step 418 to check whether the connection with the security providing server 100 was successful. If the connection is successful, the process proceeds to step 422, and if not, proceeds to step 420. If the connection fails, in step 420, an error message according to the failure is displayed. If the connection is successful, the process proceeds to step 422 to transmit the encrypted payment information (payment request file) and terminates the routine. At this time, the payment request file may be configured to wait until the result data is received and then receive and end the result data. This is optional for configuration.

8A to 8B are flowcharts illustrating a process of providing encryption information and a tag file, receiving payment information, and processing according to a security providing server according to an exemplary embodiment of the present invention. Hereinafter, a process performed by the security providing server 100 according to the present invention will be described in detail with reference to FIGS. 1 to 8A and 8B.

The control unit 111 of the security providing server 100 maintains the standby state in step 600. This waiting state is a generic term for waiting for a connection of another computer, waiting for payment information or a request for an encrypted file, or waiting for an operator's connection. If a predetermined signal is received while maintaining the standby state, the controller 111 proceeds to step 602 and checks whether the payment information is received. If payment information is received as a result of the inspection, the flow proceeds to step 630, and if not, proceeds to step 604. In step 604, the controller 111 checks whether the received signal is a signal for requesting encryption generation data (payment tag file generation data). If the encryption result data is requested, the process proceeds to step 608; otherwise, the process proceeds to step 606 to perform the corresponding function. In this control flowchart, only a case where encryption generation data is required and a case where payment information is received are described. Therefore, description of other operations is omitted.

In step 608, the control unit 111 generates data of login and new subscription information and transfers the generated data to the terminal or server that has requested the encryption generation data through the network connection unit 112. Thereafter, the process proceeds to step 610 to check whether login data is received. If the log-in data is received as a result of the test, the process proceeds to step 616; otherwise, the process proceeds to step 612. If the login data is not received, the process proceeds to step 612 to check whether the data according to the new subscription is received. If a signal according to the new subscription is received as a result of the test, the process proceeds to step 614 to process the new subscription.

When the login data is received, the process proceeds to step 618 and the login data is checked. In step 618, the subscriber checks whether the subscriber is a normal subscriber. Here, "normal subscriber" refers to a subscriber whose ID exists and whose password exactly matches. In case of such a normal subscriber, the process proceeds to step 622; otherwise, the process proceeds to step 620 and an error message is output. In step 622, the control unit 111 reads out the requested data from the data stored in the tag file DB 114 and delivers the requested data to the requesting terminal or server through the network connection unit 112.

On the contrary, when the payment information is received from the user terminal 10 in step 602, the control unit 111 proceeds to step 630 to inspect the payment information. At this time, the inspection of the payment information is to inspect the financial institution server, etc. which requested the user's confirmation and payment. After checking the details, data generated for payment is generated, and the process proceeds to step 622 to request payment to the corresponding financial institution server using the data required for payment through the network connection unit 112. Thereafter, the control unit 111 proceeds to step 624 to check whether payment approval information is received from the corresponding financial institution server through the network connection unit 112. If the payment result is received as a result of the inspection, that is, if normally processed proceeds to step 636, otherwise proceeds to step 640.

If it is not normally received first, the control unit 111 proceeds to step 640 to check whether payment failure information has been received. If the check result of the payment failure information is received in step 642, otherwise proceeds to step 634. That is, the routine is continued until a predetermined signal is received from the financial institution server. In this case, a timer may be configured to perform error processing when there is no response for a predetermined time. If the payment fails in step 640 and proceeds to step 642, the control unit 111 stores the result data in the sales information DB 115 and returns the result of the payment to the corresponding terminal through the network connection unit 112. To pass.

If the terminal does not check the connection request file in the connected state when transmitting to the terminal, that is, when the terminal transmits the payment request signal, the terminal is online or offline thereafter. Create and deliver it to the terminal. However, it can be configured to deliver the results directly when online. It can also be configured to deliver result data via e-mail even when online.

In addition, when the payment approval information is received in step 634, the process proceeds to step 636 and stores the payment result data in the sales information DB 115, and generates the e-mail again to generate the payment result in the network connection unit 112. Transfer to the terminal through. The report of the result of the payment can be made by using an e-mail as described above, or can be configured to immediately check online. This is a problem with the implementation of the program, so there is no special limitation. If the payment is successful, the controller 111 transmits the product information and the payment result data on the file in which the payment was made to the corresponding product providing server. In this way, even when the payment information is delivered to the product providing server can use the e-mail. Alternative arrangements may be used. In this case, the transmitted data is encrypted data.

In FIG. 8A to FIG. 8B, the description has been focused on the case where the product is provided by the server selling the product. That is, the case in which the product providing server 20 requests data necessary for generating the payment tag file encryption and the case in which the product is settled are described. Except that the encrypted data is not required when the encrypted tag is sold through program sales, the payment process is the same.

However, the settlement process in general alumni, fellowships, small groups, EBPP, etc. is not the sale of goods. At this time, the product providing server 20 may not exist. In this case, therefore, it can be configured to notify the user through an e-mail service. In addition to the electronic mail, it may be configured to access and check the security providing server 100 through a user authentication process. In this case, the security provision server 100 may be configured to perform an e-mail for sending a bill. In addition, the security providing server 100 may be configured to confirm the email address of the representative who performs the payment without confirming the result of the payment to the product providing server.

As described above, only those who can view the information traded in the e-commerce system can be configured. Also, since security is established and distributed at the time of payment, the information can be prevented from being forged or altered by persons with impure intentions. There is an advantage to this.

Claims (11)

A security tag server providing payment tag file generation data for payment to a product providing server and receiving payment request information from a user terminal and performing payment, and a payment tag file having the generated data from the security providing server. An electronic product including the product providing server for generating and transmitting the product description information to the user terminal, and the user terminal generating payment request information with the payment tag file from the product providing server and transmitting the generated payment request information to the security providing server. In the commerce system, in the security providing server device, A network connection unit for accessing the user terminal, the financial institution server, and the product providing server to interface data; A tag file memory for storing data for generating a payment tag file for payment of goods sold in the product providing server; A sales information memory for storing payment request information received from the user terminal and payment result information received from the financial institution server; Upon receipt of a data request for payment from the product providing server, the payment tag file generation data is read from the tag file memory and transmitted to the product providing server, and the payment request information is received with the payment request information from the user terminal. A control unit for accessing a financial institution server to perform a payment, receiving payment result information from the financial institution server, storing the payment result information in the sales information memory, and transmitting the payment result information to the product providing server and the user terminal. Device characterized in that. The method of claim 1, And an operator interface for an operator to access and perform data update, deletion, storage, and transmission and reception of data confirmation information. A security providing server for providing payment tag file generation data for payment to a product providing server, and generating a payment tag file with the generated data from the security providing server and transmitting the product to the user terminal together with product description information; In the electronic commerce system comprising a product providing server and the user terminal to generate payment request information with the payment tag file from the product providing server to the security providing server, payment method of the security providing server To When receiving a data request for payment from the product providing server, checking whether the subscriber is a normal subscriber; When the product providing server is registered as a normal subscriber, transmitting data for generating a payment tag file for payment of a product sold by the product providing server to the product providing server; Receiving payment request information from the user terminal, requesting payment processing by accessing a financial institution server with the payment request information; Storing the result data for payment and transmitting the result data for the payment to the product providing server and the user terminal when receiving the payment approval information from the financial institution server. delete delete The method of claim 3, And storing the information about the payment failure when receiving the payment failure information from the financial institution server, and transmitting the information about the payment failure to the user terminal. A security providing server for generating a payment tag file for payment according to a subscriber's request and transmitting the payment tag file to a user terminal, and generating payment request information with the payment tag file from the security providing server and transmitting the payment request information to the security providing server. In the electronic commerce system comprising a user terminal, In the security providing server device, A network connection unit for accessing the user terminal, the subscriber terminal, and a financial institution server to interface data; A tag file memory for storing a file requiring payment and a payment tag file attached to the file; A payment information memory for storing payment request information received from the user terminal and payment result information received from the financial institution server; When the payment request is received from the subscriber terminal, the payment request file and the payment tag file are read from the tag file memory, and the payment tag file is attached to the file requesting the payment to the user terminal. Transmit the payment request information from the user terminal to the financial institution server with the payment request information, perform the payment, receive the payment result information from the financial institution server, and store the payment information in the memory; And a controller for transmitting payment result information to the subscriber and the user terminal. The method of claim 7, wherein And an operator interface for an operator to access and perform data update, deletion, storage, and transmission and reception of data confirmation information. A security tag server providing payment tag file generation data for payment to a product providing server and receiving payment request information from a user terminal and performing payment, and a payment tag file having the generated data from the security providing server. And a product providing server for generating and transmitting the product description information to the user terminal and generating the payment request information with the payment tag file from the product providing server and transmitting the generated payment request information to the security providing server. In the electronic commerce system, in the payment request method of the user terminal, Displaying the product description information received from the product providing server; Determining whether the payment tag file can be read by checking the user's authority when a click of the payment information display area is detected in the product description information display area; If it is possible to read, decoding the payment tag file received with the product description information by the algorithm provided from the security providing server, and displaying the payment information constituting the payment tag file using a predetermined viewer (viewer) and, Modifying payment information displayed on the viewer when a key input is detected to correct the payment information while the viewer is displayed; Generating a payment request information by encrypting payment information displayed on the viewer by an algorithm provided from the security providing server when a payment button is input while the viewer is displayed; And transmitting the generated payment request information to the security providing server. The method of claim 9, wherein the payment tag file data structure, An area where information for structure management is stored, an area where product information is stored, an area where payment information is stored, an area where product purchase information is stored, an area where seller information is stored, and an area where shipping information is stored And an area in which information for data verification is stored. The method of claim 9 or 10, wherein the generated payment request information, And a region in which information for structure management is stored, a region in which billing information is stored, a region in which payment information is stored, a region in which billing information is stored, and a region in which information for data verification is stored. How to.