KR100420181B1 - Electronic payment method and apparatus thereof - Google Patents

Abstract

The present invention minimizes the costs incurred to the biller and the paying customer (payer) when making electronic payments for invoices that occur regularly or irregularly, and ensures that the billing or paying customer (payer) can trust each other. Disclosed are an electronic payment method and apparatus capable of payment processing. The method according to the present invention comprises the steps of: (a) respectively registering a payer agency account capable of acting on behalf of a payer and a billing agent proxy account on behalf of a payer on each bank server within a bank server group; (b) the payment agent server receiving information related to at least one payment issued from at least one billing terminal or billing server; (c) The payment to be paid by the user of the payer terminal or payer server connected on the basis of the payment-related information received in step (b) from the paying account to the paying agent account in the bank where the paying account is opened. Transferring; (d) The amount transferred to the payer agency account through step (c) for the first period of time is divided by the billing party, and the transfer amount corresponding to the billing agency account in the bank where the corresponding billing account is opened. (E) collectively transferring the amount transferred to the billing agent proxy account for the second predetermined period for each billing account registered in the same bank server.

Description

Electronic payment method and apparatus

The present invention relates to an electronic payment method and apparatus, and more particularly, to an electronic payment method and apparatus for bills that are periodically or irregularly generated through electronic commerce or commerce via the Internet.

With the development of information and communication technology and the commercialization of the Internet, electronic commerce or commerce through the Internet is actively progressing. This type of electronic commerce or commerce via the Internet is classified into business-business, business-consumer, and consumer-administration according to the trading entity. The exchange of goods or services through various electronic media between independent organizations or between organizations and individuals is called electronic commerce.

Such e-commerce and commerce via the Internet amounted to US $ 210 million in 1994, US $ 4 trillion through TV home shopping, US $ 4 million through the World Wide Web, and US $ 1 million in the CD-ROM market. The 2000 forecast is $ 2.4 trillion for online services, $ 3.4 trillion for TV home shopping, $ 4.4 trillion for World Wide Web (WWW), $ 84 million for the CD-ROM market, and 7 for the Interactive TV market. Electronic transactions over the Internet are growing rapidly at $ 39 million. As a result, the number of bills and bills is attempting to be issued through a communication network such as the Internet, and the electronic payment market is rapidly increasing.

Currently used electronic payment methods are electronic money, account transfer, credit card transfer. Although these methods are more advanced than the existing payment methods that could only be made through bank windows using Giro paper, they still have not significantly reduced costs or improved quality of service.

In other words, the method of using electronic money not only hassle to purchase an integrated circuit (IC) card similar to a digital coin or credit card through a company that provides electronic money, but also separately installs a program for each company that provides each currency. shall. The bank transfer method requires customers to visit banks or use bank banking or PC banking in which banks have transferable accounts. If such transfers are made between different banks, the payer must pay the transfer fee. In addition, the transfer method using credit card is the most widely used, but the fee charged to the claimant is expensive, and there is a disadvantage in that it is suitable for dealing with a considerable amount of money. From the standpoint, strong encryption technology must be involved to prevent fake credit card holders from trading.

SUMMARY OF THE INVENTION An object of the present invention is to provide an electronic payment method and apparatus that can minimize the costs incurred on the biller and the paying customer (payer) when the electronic payment is made for a bill that is periodically or irregularly generated.

Another object of the present invention is to provide an electronic payment method and apparatus that enables secure payment processing by which a biller or a paying customer (payer) can trust each other when making electronic payments for bills that occur periodically or irregularly.

1 is a schematic block diagram of an electronic payment device according to the present invention.

2 is a flowchart illustrating the operation of the electronic payment method according to the present invention.

Figure 3 is an embodiment of a detailed flowchart of the transfer process between the payer and the payment agent in performing the electronic payment method according to the present invention.

Figure 4 is another embodiment of a detailed flowchart of the transfer process between the payer and the payment agent in performing the electronic payment method according to the present invention.

Figure 5 is another embodiment of a detailed flowchart of the transfer process between the payer and the payment agent in performing the electronic payment method according to the present invention.

6 is an example for explaining the process of transferring funds by the electronic payment method according to the present invention.

7 is another example for explaining the process of transferring funds by the electronic payment method according to the present invention.

<Description of the symbols for the main parts of the drawings>

100: payer group 100_1 to 100_n: payer terminal 1 to n

110: billing party group 110_1 to 110_o: billing terminal 1 to O

120: payment agent server 130: bank server

130_1 to 130_m: Bank server 1 to m

In order to achieve the above object, the electronic payment method according to the present invention, a payer group consisting of at least one payer terminal or payer server, a billing group consisting of at least one billing terminal or billing server, a paying agent server And an electronic payment method from at least one payer to at least one biller in a network environment in which a bank server group having at least one bank server allocated to each bank is connected, the method comprising: (a) paying each bank server in the bank server group; Registering a payer surrogate account capable of acting on behalf of the payer and a billing surrogate account capable of acting on behalf of the claimant; (b) the payment agent server receiving information related to at least one payment issued from at least one billing terminal or billing server; (c) the payment agent account in the bank in which the payment account is opened from the payment account for the payment to be paid by the user of the payer terminal or the payer server connected based on the information related to the payment received in step (b). Transferring to; (d) classify the amounts transferred to the payer agency account by the biller through step (c) for the first period, and transfer the amount of the transfer to the billing agency account in the bank where the account of the biller is opened. Batch transfer step; (e) It is preferable to include a step of transferring the amount transferred to the billing agent proxy account for the second predetermined period for each billing account registered in the same bank server.

In order to achieve the above objects, another electronic payment device according to the present invention is an electronic payment device from at least one payer to at least one biller in a network environment, wherein the regularly charged charge is paid through one payment account. A payer group comprising at least one payer terminal or payer server capable of making a payment request over a network; A bank server group having at least one bank server allocated to each bank; A billing group comprising at least one billing terminal or billing server capable of collectively collecting billing billed through one billing account; When a payment request is received from the payer terminal or the payer server based on the payment related information provided from the billing terminal or billing server through the network, the paying account is transferred from the paying account to the paying account registered in the bank server where the paying account is opened. Request that the appropriate payment be made to the bank server, and after the first period of time has elapsed, the amount transferred to the payment agency account will be transferred to the billing agency account registered on the bank server on which the billing account is registered. Requesting a banking server, and requesting a payment agent server to transfer the amount transferred to the billing agent account after the second predetermined period to the corresponding banking server in a batch for each billing account registered in the same banking server. It is preferable to include.

Another electronic payment device according to the present invention for achieving the above objects, in the network environment, in the electronic payment device from at least one payer to at least one biller, requesting the collection of irregularly generated charges, A billing group comprising at least one billing terminal or billing server capable of collecting said billing through a billing account; A payer group comprising at least one payer terminal or payer server capable of making a payment request over the network for which the billed charge is paid through one payment account; A bank server group having at least one bank server allocated to each bank; When a request is made for the billing incurred irregularly from the billing terminal or billing server through the network, the payer code for the requested billing is allocated and sent to the corresponding payer terminal or payer server, When a payment is requested from a payer terminal or a payer server, a request is made to the bank server so that the corresponding payment is transferred from the paying account to the paying account registered in the bank server on which the paying account is registered. After considering the bank in which the biller account is registered, the bank server requires that the amount transferred to the paying account is transferred to the corresponding billing agency account in a batch, and after the second period of time passes, the biller Payments transferred to your agency account will be eligible for bulk transfer by biller account. It includes a server that requires paying agents to the bank server is preferred.

Hereinafter, with reference to the accompanying drawings will be described in detail the present invention.

1 is a schematic block diagram of an electronic payment apparatus according to the present invention, wherein a payer group 100 composed of payer terminals 1 to n (100_1 to 100_n), and billing terminals 1 to o ( It consists of a billing group 110 comprised of 110_1-110_o, the payment agent server 120, and a bank server group 130 comprised of bank servers 1-m (130_1-130_m).

In the above-described configuration, the payer terminals 1 to n (100_1 to 100_n) and the billing terminal 1 to o (110_1 to 110_o) may be configured as a system operated as a server, and may be individual, corporate, or governmental agencies, respectively. . Bank servers 1 to m (130_1 to 130_m) provided in the bank server group 130 are regarded as servers for each bank. That is, bank server 1 130_1 and bank server 2 (not shown) are servers of different banks.

In addition, the payer group 100, the billing group 110, the payment agent server 120 and the bank server group 130 is an environment that can send and receive information with each other over a network such as the Internet.

2 is a flowchart illustrating the operation of the electronic payment method according to the present invention.

Then, an embodiment according to the present invention will be described with reference to FIGS. 1 and 2 as follows.

First, payer terminals 1 to n (100_1 to 100_n) in the payer group 100 and billing terminals 1 to o (110_1 to 110_o) in the biller group 110 each have one account registered with the bank. Should be At this time, the accounts of payer terminals 1 to n (100_1 to 100_n) become payment accounts according to the present invention, and the accounts of biller terminals 1 to o (110_1 to 110_0) become collection accounts (or biller accounts). .

In this way, with payment and collection accounts (or billing account) open at any bank, the paying agent (not shown) has a payer attended account and biller attended at each bank. Each account must be registered. In this case, the registration method may be registered by accessing one-to-one through the network with the bank servers 1 to m (130_1 to 130_m) in the bank server group 130 using the payment agent server 120 or may register by visiting the corresponding bank. . The payer agency account is an account registered in the same bank as the bank in which the above-described paying account is opened, and the billing agent account is an account registered in the same bank as the bank in which the above-mentioned collection account (or billing account) is opened.

At this time, the bank servers 1 to m (130_1 to 130_m) in the bank server group 130 should be able to process an agent transaction code (AgentTranCode: Agent Transaction Code) when depositing or transferring through the payment agent. The payer management code is assigned to a paying agent identifier (agent ID) that indicates that the account is associated with the paying agent, the billing party's code (AgentClientCode) assigned when registering with the paying agent, the billing unit provided by the billing party, or It is configured to include a payer code (PayCode or AgentPayerCode) assigned at the time of billing registration and an extra code (IndexCode) for assigning any code related to the payer, the payment agent server for the electronic payment processing according to the present invention ( Code managed in 120).

In this way, after registering the payer agency account and the billing agency account in the bank server 1 to m (130_1 to 130_m), in step 203, the payment agent server 120 is provided with the billing terminal of the billing party group 110. Payment related information is received from 1 to o (110_1 to 110_o), respectively. In the case of invoices that are generated periodically, detailed payment information such as the payer's AgentTranCode and the amount of payment is sent out in batches for multiple payers. The payment related information about the invoice generated at irregular intervals is sent with the corresponding billing information and information for requesting the payment agent management code assignment. In the case of infrequently generated invoices, one payment information is sent per transaction.

Then, in step 205, the payment agent server 120 is present in the payer group 100, the payment from the payment account of any payer terminal connected among the payment terminals 1 to n (100_1 to 100_n) to the payer agency account. Perform the transfer process.

3 to 5 are exemplary diagrams of detailed flowcharts of the payment transfer process in step 205, and FIG. 3 shows an electronic bill sent from a corresponding billing terminal to a corresponding payer terminal for a bill generated periodically. 4 is a case where a payer terminal is performed through a direct connection with a paying agent server 120 regardless of whether a bill is periodically generated, and FIG. 5 is a process for billing that is generated at irregular intervals. .

That is, when the payer terminal 1 (100_1) in the payer group 100 receives the electronic bill from the billing terminal 1 (110_1) through the network, the payment agent server 120 using the electronic bill received in step 301 Connect with. That is, the payer terminal 1 100_1 is connected to the paying agent server 120 only by clicking the icon of the electronic bill. At this time, payment information including payment agent management code (AgentTranCode) and billing information included in the electronic bill is automatically sent to the payment agent server 120.

In step 303, it is checked whether a user code has been input from the payer terminal 1 100_1 according to the guidance message of the paying agent server 120 which has received this. The user code is a unique code used when the payer terminal 1 100_1 is registered in the paying agent server 120 and is the same as the ID used when accessing the site. At this time, not only a user code but also a password may be considered. This password is also information set by the payer terminal 1 (100_1) when registering with the paying agent server (102).

If the user code is received as a result of the check in step 303, the payment agent server 120 checks whether the payer terminal 1 100_1 is a registered user using the received user code in step 305. If the result of the check is not a registered user, authentication retries are requested in step 307, and control returns to step 303. FIG.

However, if the result of the check is a registered user, the flow proceeds to step 309 to check whether the corresponding payment account information is registered or entered through the current connection. If the check result is not registered or entered, in step 311 a registration or input of the corresponding payment account information is requested and the process returns to step 309.

As a result of checking in step 309, when the corresponding payment account information is registered or entered, in step 313, the payment agent server 120 checks whether the user code and the payment amount match the information previously received from the billing terminal 1 110_1. Check it. That is, the agent obtains the payment agent management code (AgentTranCode) and the billing information received in step 301 through the user code, and the same payment agent management code and the same payment agent management code among the payment information received from the billing terminal 1 (110_1) in advance using this information. Check if it matches the billing information attached to it.

In operation 315, the payer terminal 1 (100_1) is notified of the confirmation result. The notification method may be in the form of providing information such as a paying customer name, a paying customer code, and a payment amount. When receiving the information that confirmed the notification in step 317, the payment agent server 120 connects to the corresponding bank server in step 319 and transfers the payment corresponding to the payer agent account from the payment account. If it is determined in step 321 that the above transfer process is normally performed, the payment agent server 120 notifies the payer terminal 1 (100_1) in step 325. The notification may be performed, for example, by presenting a customer name, a customer code, a payment amount, etc., which amount is paid for a certain purpose, and providing balance information to a current payment account. However, if it is checked in step 321 that normal processing has not been performed, in step 323, the payer terminal 1 (100_1) is notified of the reason for the processing impossible, and returned to step 309 to register or input the payment account information. You will be confirmed.

On the other hand, as a result of checking in step 303, when no user code is received, the payment agent server 120 checks whether information indicating a guest is input in step 327. If it is not checked, it returns to step 303 and repeats the above-described process. However, if the check result is entered, the process proceeds to step 309 to perform the operation as described above.

In addition, if the payer terminal 1 100_1 directly connects to the paying agent server 120 regardless of whether the invoice is delivered in step 401 of FIG. 4, the paying agent server 120 determines whether a user code has been received in step 403. Check it. As a result of the check, if it is received, the flow proceeds to step 405 to check whether the user is registered with the payment agent server.

If the result of the check is not a registered user, the process proceeds to step 407 and requests for authentication retries are returned to step 403. However, if it is a registered user, it is checked in step 409 whether a payment agent management code (AgentTranCode) has been received. If the check result is not received, the payment agent server 120 transmits the corresponding payment list to the payer terminal 1 (100_1) in step 411. In this case, the user of the payer terminal 1 (100_1) to which the access is currently concerned does not know at all the details of the invoice to be paid. The payment list that is sent is information received from the billing terminals 110_1 to 110_o existing in the billing group 110, and is information reorganized so that the paying agent server 120 can search for it based on a user code. . Therefore, the payer terminal 1 (100_1) can check all the details of the bills not yet paid.

If the user of payer terminal 1 (100_1) selects a payment item through the sent payment list, the payment agent server 120 receives information on the payment item selected in step 413. It is then checked in step 415 whether the account information has been registered or entered. If it is checked in step 409 that the payment agent management code is received, the payment agent server 120 immediately proceeds to step 415 to perform the above-described operation.

If the check result of step 415, the account information is not registered or entered, the payment agent server 120 proceeds to step 417 to request the registration or input of the account information and return to step 415.

However, when the check result of step 415, the corresponding account information is registered or entered in step 419 the payment agent server 120 checks whether the user code and the payment amount is the same as in step 313 of FIG. Then, the result of the check in step 421 is notified to the payer terminal 1 (100_1), and when the information indicating that the information checked in step 423 is received, in step 425 is connected to the corresponding bank server in the payer account in the payer account Perform the transfer process to. If this process is successful, the process proceeds from step 427 to step 431 where the result is notified to the payer terminal 1 (100_1) and the primary account transfer operation is completed. However, if the result of the check in step 427 is abnormally made, in step 429 a notification of the inability to proceed and proceeds to step 415.

On the other hand, if it is checked in step 403 that the user code is not received, the payment agent server 120 checks whether the information indicating the guest is received in step 433. As a result of the check, if the information indicating the guest has not been received, the process returns to step 403 to repeat the above-described process. However, if the information indicating the guest is received, the payment agent management code, billing information, corresponding account information, etc. are requested to the payer terminal 1 100_1 in step 435. Accordingly, when these information is received in step 437, the payment agent server 120 checks whether there is a matching billing information using the payment agent management code in step 439, and proceeds to step 421 to perform as described above. .

In addition, an occasional bill is issued when, for example, the payer terminal 1 100_1 purchases an item at a shopping mall connected through a network such as the Internet. When the occasional bill is issued in this way, the billing terminal 1 (110_1) will send a signal requesting the payment agent management code assignment with the billing information to the payment agent server 120 side.

When the payment agent server 120 receives the above-mentioned information from the billing terminal 1 (110_1), and transmits the paying agent management code and billing information assigned to the corresponding payer terminal 1 (100_1). Accordingly, the payer terminal 1 (100_1) based on the payment agent management code and the billing information received in step 501, the payment agent management code and billing, such as when attempting to access or direct access in the same way as issuing electronic bills. The payment agent server 120 may be connected by directly inputting and sending information.

When payer terminal 1 100_1 and payment agent server 120 are connected, payment agent server 120 checks in step 503 if a user code has been received. As a result of the check, if the user code is received, the payment agent server 120 checks whether the payer terminal 1 100_1 is a registered user using the received user code in step 505. If the result of the check is not a registered user, authentication retries are requested in step 507, and control returns to step 503.

However, if the result of the check is a registered user, the flow proceeds to step 509 to check whether the corresponding payment account information is registered or entered through the current connection. As a result of the check, if neither registered nor entered, a request for registration or input of the payment account information is requested in step 511 and the process returns to step 509.

As a result of checking in step 509, when the corresponding payment account information is registered or entered, in step 513, the payment agent server 120 checks whether the user code and the payment amount match the information previously received from the billing terminal 1 110_1. Check it. That is, the agent obtains the payment agent management code (AgentTranCode) and billing information received in step 501 through the user code, and the same payment agent management code and the same payment agent management code received from the billing terminal 1 (110_1) in advance using this information. Check if it matches the billing information attached to it.

In operation 515, the payer terminal 1100_1 is notified of the verification result. The notification method may be in the form of providing information such as a paying customer name, a paying customer code, and a payment amount. When the information indicating that the information is confirmed in step 517 is received, the payment agent server 120 connects to the corresponding bank server in step 519 and transfers the payment corresponding to the payment agent account from the payment account. If it is determined in step 521 that the above transfer process is normally performed, the payment agent server 120 notifies the payer terminal 1 (100_1) in step 525. The notification may be performed, for example, by presenting a customer name, a customer code, a payment amount, etc., which amount is paid for a certain purpose, and providing balance information to a current payment account. However, if it is checked in step 521 that the normal processing has not been performed, in step 523 the payer terminal 1 (100_1) is notified of the reason for the processing impossible, and returned to step 509 to register or input the payment account information. You will be confirmed.

On the other hand, as a result of checking in step 503, when no user code is received, the payment agent server 120 checks whether information representing a guest has been entered in step 527. If it is not checked, it returns to step 503 and repeats the above-described process. However, if the check result is entered, the process proceeds to step 509 to perform the above operation.

When the payment is transferred from the payment account to the payer agent account in various ways described above, the payer terminal 1 (100_1) recognizes that the payment for the corresponding bill is completed. However, the payment agent server 120 proceeds to step 207 to request the corresponding bank server to perform the transfer process from the payer agency account to the billing agency account for the transfer. Accordingly, the corresponding bank server performs a batch transfer process on a plurality of payments transferred to the payer agency account. That is, the payment corresponding to the billing terminal 1 (110_1) of the plurality of payments transferred to the payer agency account is transferred to the corresponding billing agency account once.

When the transfer process is completed, the payment agent server 120 requests that the appropriate amount of the amount transferred to the billing agency account to the corresponding billing server in step 209 to be transferred to the billing account in bulk. The bank server performs the transfer process.

In this way, the payer agency account accumulates the amount transferred from each paying account for a certain period of time, and transfers it to the billing agent account in bulk. The billing agent account is also transferred from each payer agency account for a certain period of time. And accumulate the funds and transfer them in bulk to the billing account. The period described above takes at least one day.

6 and 7 are flow charts of the transfer of funds between the bank servers (130_1 ~ 130_m) by the request of the payment agent server 120 as described above, Figure 6 is a payment account and the billing account is in a different bank 7 shows a case where a payment account and a billing account exist in the same bank.

As can be seen through FIG. 6, there is one payer agency account of the payment agent server 120 in each bank, and a transfer from a plurality of payer accounts existing in the bank is made to the payer agency account. . At this time, the transfer is made not only for one biller's bill but also for the bills of multiple billers. Therefore, the amount of money that a plurality of payers intend to pay to a plurality of billers is transferred to a payer agency account existing in a bank.

In this way, the amount transferred to the payer agency account is divided by biller, and the bulk transfer is made to the billing agency account registered in the bank in which the corresponding biller account exists. In other words, the payers of multiple payers are transferred at one time. For example, of the payments transferred to Payer Account 1, the payments that must be transferred to Billing Account 1 are collectively transferred to Billing Account 1.

Accordingly, the billing agency 1 is to deposit only payments corresponding to the billing accounts 1 to i from the paying agency accounts 1 to m registered in the banks 1 to m. In addition, the payments collectively transferred in this way are separated for each billing person and collectively transferred to the corresponding billing account.

7 illustrates a case where a payment account and a biller account exist in the same bank as described above. As shown in FIG. 7, even if a payment account and a billing account exist in the same bank, payments are transferred from a plurality of payment accounts 701_1 to 701_l in the payer agency account 703, respectively. Only the amount to be deposited in the biller accounts 1 to p (707_1 to 707_p) among the transferred payments is collectively transferred to the billing agency account 705.

6 and 7 described above are performed at the request of the payment agent server 120. That is, the transfer from the paying account to the payer agency account, the transfer from the payer agency account to the billing agency account, and the transfer from the billing agency account to the billing account (or collection account) is performed by the paying agent server 120. Is made by request.

According to the present invention described above, a payer account is divided into a payer agent account and a biller agent account and registered and operated in each bank, so that the payer does not have to pay a transfer fee when the payer pays the billed amount. In addition, the claimant also has an effect that can be easily collected at a much lower cost than the conventional collection method through issuing Jiro land.

In addition, it is impossible to withdraw out of the bank during the transfer period from the payment account to the collection account, thereby maximizing the stability of the transfer of funds between the payer and the claimant. In the case of banks, the money of the claimant can be concentrated and the interest income will be generated because the funds do not flow out of the bank for a certain period for batch processing.

In addition, the payment processing is performed using the payment agent management code as much as possible, thereby preventing the leakage of the personal information of the payer as much as possible, and the invoice for the irregular purchase is immediately sent to the payer through the payment agent, and the processing of the payment is performed. By doing so, it is possible to prevent the damage caused by the fraudulent buyer, thereby increasing the trust between the payer and the claimant.

Claims (12)

A payer group consisting of a plurality of payer terminals or payer servers, a billing group consisting of a plurality of billing terminal or billing server servers, a bank server group having a plurality of bank servers assigned to each bank, and a network connected to the paying agent server In an electronic payment method from a plurality of payers to a plurality of billers in an environment, (a) registering a payer agency account capable of acting on behalf of the payer and a billing agent agent account capable of acting on behalf of the billing party at each bank server in the bank server group; (b) the payment agent server receiving information relating to a plurality of payments sent from a plurality of billing terminal or billing server; (c) the payment agent server connects to the payer terminal or the bank server on which the payment account of the payer server is registered based on the information related to the plurality of payments received in step (b). Transferring a plurality of payments to be paid by a user of a payer server from the paying account to a paying agency account registered with the bank server; (d) The paying agent server divides the amounts transferred to the paying agent account for each payer through the step (c) for a first period, and registers the corresponding billing account in the bank server in which the billing account is registered. Requesting a corresponding bank server to collectively transfer the transfer amount corresponding to the billing agency account; (e) the payment agent server requesting the corresponding bank server to collectively transfer the amount transferred to the billing agency account for the second billing period for a second predetermined period. The method of claim 1, wherein step (c) comprises: (c1) When the payer terminal or the payer server is connected to the paying agent server by using the electronic bill received from the billing terminal or the billing server, the paying agent server is connected to the paying terminal or the paying terminal server. Analyzing information received from a payer server to check whether the payer terminal or the user of the payer server is a registered user in the payer server; (c2) if the user of the payer terminal or the payer server is a registered user as a result of performing step (c1), the payment agent server checks whether information related to the payment account is registered or input; (c3) If the information related to the payment account is registered or input as a result of performing the step (c2), the payment agent server connects to the corresponding bank server and transfers the payment corresponding to the payment agent account from the payment account. Requesting an electronic payment method. The method of claim 1, wherein step (c) (c1) When the payer server or the payer server that has received the payment related information is connected to the payer server, the payer server receives from the payer terminal or payer server. Checking whether the user of the payer terminal or the payer server is a registered user with the paying agent server by analyzing the information; (c2) if the user of the payer terminal or the payer server is a registered user as a result of performing step (c1), checking whether information related to the payment account is registered or input; (c3) If as a result of performing the step (c2), information related to the payment account is registered or entered in the payment agent server, the payment server transfers the payment from the payment account to the payer agency account by connecting to a corresponding bank server. Electronic payment method comprising the step of. The method of claim 2 or 3, wherein step (c) (c4) checking whether the user is connected as a guest if the user of the payer terminal or the payer server is not a user registered in the paying agent server as a result of performing the step (c1); (c5) checking whether information related to a payment account corresponding to the case where the user is connected as the guest is checked as a result of the checking in step (c4); (c6) If as a result of performing the step (c5), information related to the payment account is input, the payment agent server is connected to the bank server where the guest's payment account is opened and the guest's payment account in the guest's payment account; The electronic payment method further comprises the step of transferring a payment corresponding to the payer agency account registered in the bank server opened. The method of claim 1, wherein step (c) (c1) When the payer terminal or the payer server is connected to the paying agent server without using an electronic bill, the paying agent server analyzes the information received from the paying terminal or payer server and the Checking whether a user of a payer terminal or payer server is a registered user with the payer server; (c2) checking that the payment agent management code (AgentTranCode) is received if the user is a user registered in the payment agent server as a result of performing the step (c1); (c3) if the payment agent management code is received, checking whether information related to a payment account has been registered or entered into the payment agent server; (c4) if information related to the payment account is registered or entered in the payment agent server, accessing a corresponding bank server and transferring a payment corresponding to the payment agent account from the payment account registered with the bank server; ; (c5) if the payment agent management code has not been received, the payment agent server transmitting the payment list collected for the user of the payer terminal or payer server to the payer terminal or payer server; (c6) When the payment item information selected from the payer terminal or the payer server is received after performing (c5), the paying agent server checks whether information related to the payment account is registered or entered in the paying agent server. Proceeding to the step (c4); (c7) if the payer terminal or the payer server user is a guest as a result of performing step (c1), the paying agent server requesting transmission of corresponding payment information; (c8) if the corresponding payment information is received as a result of performing step (c7), the payment agent server checking whether the payment information matches the received payment information in step (b); (c9) if the received payment information matches the payment information received in step (b) as a result of performing step (c8), the payment agent server includes the step of proceeding to step (c4); Electronic payment method to do. The method according to any one of claims 2, 3 and 5, wherein step (c) comprises: Before transferring the payment from the payment account to the payer agency account, the paying agent server checks whether the payment amount known by the payer matches the amount charged by the billing claimant, and confirms the result of the check with the payer terminal or Notifying the payer server; And transferring a payment from the payment account to the payment agency account, and notifying the payer terminal or the payer server. The payment agent management code according to any one of claims 2, 3, and 5, is assigned in a payment agent identifier (Agent ID), a billing party code (AgentClientCode) assigned when registering with the paying agent, and a billing unit provided by the billing party. Payer code (PayCode) and an extra code (IndexCode) that can be assigned by the paying agent for the payer. According to claim 1, wherein the step (b) is a periodic billing, the payment agent server, the electronic payment, characterized in that the payment information for all the payers to be billed by the biller is collectively received Way. The electronic payment method of claim 8, wherein the payment information includes a payment agent management code (AgentTranCode) and billing information for each payer. According to claim 1, Wherein (b) is the occasional billing, the payment agent server assigns the payment information and the payment agent management code for the billing information from the billing terminal or the billing server. And receiving the requested information as the information related to the payment. In an electronic payment device from a plurality of payers to a plurality of billers in a network environment, A payer group comprising a plurality of payer terminals or payer servers capable of making payment requests for a plurality of charges periodically billed through a payment account through a network; A bank server group having a plurality of bank servers allocated to each bank; A billing group consisting of a plurality of billing terminal or billing server capable of collecting a plurality of billings billed through one billing account; When the payment request is received from the payer terminal or the payer server based on the payment related information provided from the billing terminal or billing server through the network, the paying account is registered with the bank server registered in the paying account. Request the bank server to transfer the corresponding payment to the payment account, and after the first period of time passes, the amount transferred to the payment account is divided by the billing party, and the corresponding billing account is registered. A request is made to the corresponding bank server to collectively transfer to the billing agency account registered in the bank server, and after the second predetermined period has elapsed, the amount transferred to the billing agency account is registered in the bank where the billing agency account is registered. Even if the transfer is made in bulk for each billing account registered on the server, Electronic payment system comprising a payment agent as a server to request that the bank server. In an electronic payment device from a plurality of payers to a plurality of billers in a network environment, A billing group consisting of a plurality of billing terminal or billing server that can collect money through a single billing account by requesting billing for a plurality of billings that occur at irregular intervals; A payer group comprising a plurality of payer terminals or payer servers capable of making payment requests for a plurality of charges billed through one payment account through a network; A bank server group having a plurality of bank servers allocated to each bank; When a request for collection of a plurality of charges generated at random from the billing terminal or billing server through the network is requested, the payment agent code for the requested billing is allocated and sent to the corresponding payer terminal or payer server. When a payment is requested from the corresponding payer terminal or the payer server, the bank server is requested to transfer the corresponding payment from the paying account to the paying account registered in the bank server in which the paying account is registered. After the first period of time, the corresponding bank server to divide the amount transferred to the billing agent account by the billing party and to transfer the billing account to the billing agency account registered in the registered bank server And after the second period of time has passed, Electronic payment system comprising a payment agent server transfers the amount to the account Ja agency that requests to the appropriate server bank so that bulk transfer payment by the claimant account.