JP2006196019A - Order processing method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To carry out order processing by a computer on the shop side for executing on-line sale of, e.g., a commodity. <P>SOLUTION: Upon receiving an order request of a customer terminal, the shop computer registers the information on the content of the order made by a customer and transmits the identification number of the order of the customer and a tenant code to a settlement system. Upon receiving the identification number of the order of the customer and a session key from the settlement system, the computer extracts the information on the content of the order of the customer by using the identification number of the order of the customer and transmits the information on the content of the order, the session key, and the information for shop authentication to the settlement system. Upon receiving the information representing the feasibility of acceptance of the order of the customer from the settlement system, the information representing the acceptance of the order is stored. The information representing the feasibility of acceptance of the order of the customer is transmitted to the customer terminal according to the information received from the settlement system. In addition, upon receiving the information representing the acceptance of the order of the customer, processing for shipment of the commodity or the like may be requested to a physical distribution system or the like. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a technique for order processing in a store computer that performs online sales of products and the like.

  Various homepages of stores that sell products etc. are opened on the Internet. In such online sales, payment of goods and the like may be credit card payment in addition to payment by bank transfer, postal transfer, or cash on delivery, for example. Usually, in the case of credit card payment, communication between the store server and the customer's terminal is encrypted by SSL (Secure Socket Layer) etc., so it should not be seen by others, but the general consumer is credit card I don't like to enter a number for each product order. However, if bank transfers and postal transfers have to be carried out one by one, there is a problem that it takes time and bears a remittance fee. Especially in the case of cash on delivery, the cash on delivery fee is expensive.

Therefore, a mechanism is used to avoid sending a credit card number on the Internet for each order. For example, when a customer registers a credit card number in advance with a company that performs a settlement business by mail or the like and purchases a product etc. on a homepage of a store that is affiliated with the company that performs the settlement business, The company that performs the settlement business cooperates with the company that performs the settlement business, and performs the payment process for the order price by performing customer authentication and credit processing for the customer.
International Publication No. 98/40809 Pamphlet JP-A-11-31126

  As described above, the cooperation between the server of the company that performs the settlement business and the server of the store is very important.

  An object of the present invention is to provide a novel technique for performing processing for confirming an order from a customer in a store computer.

  The order processing method according to the first aspect of the present invention is executed by a store system that performs communication between a customer terminal and a payment system. When an order request is received from a customer terminal, A step of registering content information in the order storage device, and an address of the customer terminal and at least identification information of the customer order in order to perform customer authentication processing related to the order request between the customer terminal and the payment system, Sending the store identification information to the payment system, or sending the payment system information, at least the identification information of the customer order, and the store identification information to the customer terminal, and the customer order from the payment system Credit request pre-processing step for receiving the identification information of the client and the session key generated in the payment system when the customer authentication process is successful, and ordering to the payment system In order to perform credit processing related to the request, at least identification information of the customer's order, store identification information, and a session key which is data confirmed in the settlement system before the credit processing related to the order request is performed, Information indicating that the customer's order can be received as a result of confirming that the session key is correct in the payment system and that the credit processing has been successful. Is received from the payment system, the order storage device stores information indicating an order received for the customer's order.

  In the credit request preprocessing step described above, a predetermined process may be performed after receiving the session key.

  When the store system according to the second aspect of the present invention receives an order request from a customer's terminal, the customer's order content information is registered in the order storage device, and at least identification information (for example, implementation of the customer's order) is registered. Management number in the form) and store information (for example, the store child code in the embodiment and / or the address of the store computer) to the customer terminal or the payment system, and identification information of the customer order from the payment system And a request key preprocessing means for retrieving the contents information of the customer order from the order storage device using the identification information of the customer order when the session key (for example, the operation key KEY02 in the embodiment) is received, and the order storage device A credit request means for transmitting the contents of the customer's order taken out from the customer, the session key, and the authentication information for the store to the payment system; If the payment system receives the information indicating the order possible customer orders, and a credit result processing means for storing information indicating an order for an order of the customer in the order storage device.

  As a result, when the store system of the present invention receives a session key indicating that customer authentication or the like has been normally completed in the payment system, the store system automatically sends the information as described above to the payment system and makes a credit request. Do. Therefore, it is possible to save labor and speed up processing in the store.

  The credit result processing means described above may be configured to further receive identification information (for example, an acceptance number in the embodiment) in the payment system for the customer order from the payment system and store it in the order storage device. Is possible.

  The credit result processing means described above may be configured to transmit information indicating whether or not the customer can accept an order according to the information received from the payment system to the customer terminal. In addition to the payment system, the processing result is notified from the store computer.

  When the credit result processing means described above receives the customer order identification information and the information indicating that the customer order cannot be received from the payment system, the customer receives an order in the order storage device using the customer order identification information. A configuration in which information indicating impossibility is stored is also possible.

  Further, when the credit result processing means described above receives information indicating that the customer's order can be received, the system related to the shipment of the product related to the customer's order is requested to process the product for shipment. Such a configuration is also possible. In addition, when the credit result processing means receives information indicating that the order of the customer can be received, the information indicating that the data distribution is permitted is transmitted to a system related to the data distribution related to the customer order. Such a configuration is also possible. When the credit result processing means described above receives information indicating that a customer's order can be received, the configuration is such that a collection request for the product is transmitted to a logistics system related to the collection of the product related to the customer's order. Is also possible. As described above, the store-side computer according to the present invention can be linked with various systems.

  Furthermore, the credit request pre-processing means described above may be configured to perform inventory check processing for commodities related to customer orders. The same applies to the receiving means and the credit result processing means.

  In the order processing method according to the third aspect of the present invention, when an order request is received from a customer terminal, the customer order content information is registered in the order storage device, and at least identification information of the customer order and store information To the customer terminal or the payment system, and when the customer order identification information and the session key are received from the payment system, the customer order content information from the order storage device using the customer order identification information And a step of transmitting the customer order content information, session key and store authentication information retrieved from the order storage device to the payment system, and information indicating that the customer order can be received from the payment system. If received, the order storage device stores information indicating an order received for the customer's order.

  The store system according to the fourth aspect of the present invention performs communication between a customer terminal and a payment system, and when receiving an order request from the customer terminal, stores the order information of the customer order. And at least identification of customer terminal information (for example, the IP address of the terminal) and the customer order in order to perform customer authentication processing related to the order request between the customer terminal and the payment system. Customer authentication request means for transmitting information and store identification information to a payment system, or payment system information, at least identification information of a customer order, and store identification information to a customer terminal, and payment When the customer order identification information and the session key generated in the payment system when the customer authentication process is successful are received from the system, the customer order identification information is used. Credit request pre-processing means for retrieving customer order content information from the storage device, and customer order content information and store authentication retrieved from the order storage device to cause the payment system to perform credit processing for the order request Credit request means for transmitting a credit request including information for use and a session key to the payment system, and when receiving information about the order request from the payment system indicating that the customer can accept an order, the customer is stored in the order storage device. And a credit result processing means for storing information indicating the order received.

  The modification according to the second aspect of the present invention can be applied to the modification according to the first, third, or fourth aspect of the present invention.

  It is also possible to create a program that causes a computer to execute the method according to the first or third aspect of the present invention, and the program includes, for example, a flexible disk, a CD-ROM, a magneto-optical disk, a semiconductor memory, It is stored in a storage medium such as a hard disk or a storage device. The intermediate processing result is temporarily stored in the memory.

  According to the present invention, it has been possible to provide a novel technique for performing processing for confirming an order from a customer in a store computer.

  FIG. 1 shows a system outline in one embodiment of the present invention. For example, in the network 1 that is the Internet, one or a plurality of customer terminals 3 including a web browser, a store server 5 that is a web server that sells products and the like online, and an order according to an embodiment of the present invention A payment server 7 that performs payment processing for the price is connected.

  The store server 5 includes, for example, a payment server command interface (IF) program 53 distributed from an administrator of the payment server 7 and a store side processing unit 55 for other processing in the store server 5. Further, the store server 5 includes a database of products sold, an order information database (DB) 51 for storing information related to orders received from customers, and the like, and a store terminal 11 operated by store staff is provided. It is connected. Further, the store server 5 may be connected to, for example, an inventory management system 13 or a server (not shown) that performs processing for shipping other products. In some cases, the store server 5 itself has a function of a server that performs processing for shipping these stock management system 13 and products. Further, in the store server 5, when a business of obtaining a price by downloading a program or content data to the customer terminal 3 via the network 1, for example, for download storing the program or content data. In some cases, the server 17 is connected to the network 1 and linked to the store server 5. The store server 5 may have the function of the download server 17 in some cases.

  Connected to the network 1 is, for example, a logistics system 15 of a logistics department of a company that operates a shipping company or a store server 5. This distribution system 15 may be connected to the store server 5 by another network or a dedicated line. In addition, a number of servers and the like are connected to the network 1.

  In this embodiment, the payment server 7 is a member of a predetermined Internet service provider (ISP) and purchases products and the like by the customer for a customer who has registered credit card information in advance. The payment processing is performed. Accordingly, the settlement server 7 can refer to a member information database (DB) 71 storing member ID and password information and credit card information. In this embodiment, the store server 5 that is determined to satisfy a predetermined condition in advance is permitted to use the settlement server 7. Accordingly, the settlement server 7 can refer to a store information database (DB) 73 that stores store information including the ID and password of each store or each store server 5. In this embodiment, since payment is performed by credit card, the payment server 7 is connected to a credit online system CAFIS (Credit And Finance Information Switching system) 9 and can communicate with a credit card company computer. It is like that. Since the settlement server 7 also needs to process, for example, a credit card company, it is necessary to receive order information from the store server 5 and store the order information. Accordingly, the settlement server 7 uses a settlement order information database (DB) 75 for registering order information and the like. Further, the settlement server 7 also uses a billing file 77 that stores information for billing the credit company.

  The processing in the system shown in FIG. 1 will be briefly described. The customer operates the customer terminal 3 to access the store server 5 via the network 1 and searches for products to be purchased. When a product or the like to be purchased is found, the customer transmits an order for the product or the like from the customer terminal 3 to the store server 5. At this time, the customer instructs to use the payment system according to the present embodiment for payment. The store server 5 registers the order information received from the customer terminal 3 in the order information DB 51, and the order information, information of the store server 5 (for example, store authentication information or store identification information or the address of the store server 5) and the customer The address of the terminal 3 is added and transferred to the settlement server 7. The settlement server 7 confirms / authenticates the store using the information of the store server 5 and temporarily registers the order information. If there is no problem with the information of the store server 5 and the order information, the settlement server 7 generates an operation key KEY01 and prompts the customer terminal 3 to input the customer (member) ID and password, and hidden parameters. The operation key KEY01 is transmitted.

  The customer terminal 3 displays a screen prompting the customer to input an ID and password. Then, the customer inputs the customer's (member) ID and password, and the customer terminal 3 transmits the ID and password and the operation key KEY01 of the hidden parameter to the settlement server 7. In this embodiment, the settlement server 7 determines whether the operation key KEY01 is a valid operation key, whether the ID / password pair is correct, and whether the customer with the received customer (member) ID is a normal member in the ISP. Inspect whether you are eligible to use such a payment system. If all the inspections are normally completed, the settlement server 7 generates an operation key KEY02. Then, if all the inspections are normally completed, the settlement server 7 has sent the operation key KEY02, the inspection result, and the order information included in the order information or the order information as the hidden parameters to the settlement server 7 separately. Then, the identification information of the order in the store server 5 (hereinafter referred to as a management number, but may be a symbol as well as a number) is transmitted to the store server 5. If an error occurs in any of the inspections, the operation key KEY02 is not generated, and the store server 5 is notified that an error has occurred in any of the inspections. If the ID / password pair is not correct, the customer terminal 3 is also notified. For example, an ID / password pair entry may be retried up to two times. At this point, the customer authentication process and the system use qualification confirmation process are completed.

  If the inspection result indicates a successful inspection, the store server 5 extracts the order information from the order information DB 51 using the received management number, and stores the order information, the management number, and the operation key KEY02 as the store server. 5 is output to the settlement server command interface (IF) program 53 executed in step 5. The settlement server command IF program 53 is a program that provides an interface for the settlement server 7 and the store server 5 to exchange, for example, an administrator of the settlement server 7 provides the store. If an error occurs in the check whether the customer ID is a normal member in the ISP or is qualified to use the payment system according to this embodiment, the store server 5 Notification is made that the payment system according to the present embodiment cannot be used.

  The payment server command IF program 53 that has received the order information, the management number, and the operation key KEY02 transmits the information to the payment server 7 together with the store authentication information. The settlement server 7 performs an authentication process on the store, compares the temporarily registered order information with the currently received order information, and confirms the validity of the received operation key KEY02. If these processing results are affirmative, credit processing is performed. The credit process is a process of making a credit inquiry to the CAFIS 9 using the customer's credit card number registered in advance in the settlement server 7. When the payment server 7 obtains information from the CAFIS 9 that payment can be made with the credit card of the customer, the payment server 7 registers the order information in the payment order information database (DB) 75 in the payment server 7 and stores the order information in the payment server 7. A reception number that is identification information (a symbol may be used instead of a number) is generated. When the order information is registered in the settlement order information DB 75 of the settlement server 7, an order registration notification mail for notifying that the order has been registered is transmitted to the customer.

  The settlement server 7 transmits to the settlement server command IF program 53 information indicating whether or not order information can be registered, and if registered, a reception number and a management number. The settlement server command IF program 53 outputs the received information to a processing unit that performs order management of the store server 5. Then, the store server 5 transmits screen information indicating that the order has been accepted by the payment system to the customer terminal 3. The customer terminal 3 displays a screen indicating that the order has been accepted by the payment system. Further, the store server 5 registers information indicating an order in the order information DB 51. On the other hand, if any one of the results of the store authentication process, the validity check process of the operation key KEY02, and the credit process is negative, the store server 5 accepts the order from the customer terminal 3 to the payment system. Send screen information indicating that it was not successful. Further, when the result of processing other than the store authentication processing is negative, “impossible to accept an order” is registered in the order information DB 51. Then, the customer terminal 3 is notified that the order cannot be received. This completes the order processing.

  The staff of the store who operates the store terminal 11 connected to the store server 5 refers to an order in which information indicating an order in the order information DB 51 of the store server 5 is registered, for example, and performs work for shipping the product. . When the order information is registered in the database of the settlement server 7, the store server 5 moves or copies the order information as order information from the order information DB 51 to the order information DB, and refers to the order information DB. Configuration is also possible. In addition, when the information indicating an order is registered in the order information DB 51, the store server 5 can automatically output a collection request to the physical distribution system 15. Further, in the case of downloading programs and contents / data, it is possible to output a download permission from the store server 5 to the download server 17 when information indicating an order is registered in the order information DB 51. is there. Furthermore, when there is a system related to other product shipment, a configuration in which a processing request is automatically output from the store server 5 to the system after information indicating an order is registered in the order information DB 51 is also possible. It is. In any case, processing for shipping products etc. is performed to the customer who has placed the order. The completion of shipping / delivery is also registered in the order information DB 51.

  When shipping / delivery is completed and the order price is charged, for example, the store staff who operates the store terminal 11 refers to the order information DB 51 to manage the order management number or the reception number for the order price request. To extract. If the distribution system 15 and the store server 5 are linked, the store server 5 receives a delivery completion notification from the distribution system 15. A management number or a reception number is extracted from this delivery completion notice. Furthermore, when the download server 17 and the store server 5 cooperate, the store server 5 receives a download completion notification from the download server 17. Then, the management number or the reception number is extracted from the download completion notification. When the management number or the reception number of the order to be charged for the order price is output as an order price billing request to the payment server command IF program 53 of the store server 5, the payment server command IF program 53 together with the store authentication information is output. The management number or the reception number is transmitted to the settlement server 7.

  The settlement server 7 performs authentication processing on the store using the store authentication information. If the result of the authentication process is affirmative, information indicating the final sales is registered in the order corresponding to the reception number or management number registered in the settlement server 7, and the order price request process is performed. The order price billing process is to add billing information for the order price to the information for billing the credit card company of the credit card registered by the customer. The information for billing is given to a credit card company once a month, for example. The credit card company charges each customer based on this information. When the order price billing process is completed, the processing result is transmitted to the settlement server command IF program 53, and the settlement server command IF program 53 outputs the processing result to the sales confirmation processing unit of the store server 5. In the store server 5, if the result of the order price billing process is affirmative, for example, the sales confirmed or billed for the order corresponding to the management number or the reception number in the order information DB 51 is registered. On the other hand, if the result of the order price billing process is negative, the management number or the reception number is not correct, and so on, and a notification prompting them to confirm them is output to the store terminal 11. This completes the settlement.

  Details of the system operation in this embodiment will be described below with reference to FIGS.

1. Customer authentication process and system usage qualification confirmation process [Example 1]
FIG. 2 shows a flow of customer authentication processing and system use qualification confirmation processing according to the first embodiment. For example, the customer operates the customer terminal 3 to access the store server 5 (step S1). For example, the store server 5 transmits product information and an order form to the customer terminal 3 (step S3). There are various forms of processing in steps S1 and S3, and only a simple case is shown here. The customer terminal 3 displays product information and an order form with a Web browser. The customer inputs the order contents into the Web browser, presses a send button included in the order form, and sends the order information to the store server 5 (step S5). The order information includes a product name, product number, quantity, amount, address, name, telephone number, e-mail address, and the like. Further, the order information may include information that the payment system according to the present embodiment is selected as the payment method. Further, it may include an ISP customer (member) ID related to the payment system according to the present embodiment. It is assumed that the store server 5 and the customer terminal 3 recognize each other's address.

  Upon receiving the order information from the customer terminal 3, the store server 5 confirms the order information format and the like, and registers the order information in the order information DB 51 (step S7). It is also possible to make an inventory inquiry to the inventory management system 13 before registration, for example. Then, the store server 5 receives address information (for example, URL (Uniform Resource Locator)) and store identification of a processing unit (for example, CGI (Common Gateway Interface)) that receives the received order information and results of customer authentication in the store server 5 and the like. Including information (for example, a store code) and identification information (management number) of the customer's order, and the customer terminal 3 receives screen information of a settlement request for requesting to perform an authentication procedure for settlement of the order information. Transmit (step S9). It is also possible to ask whether to select the payment system according to the present embodiment as the payment means in the screen information transmitted here. The customer terminal 3 displays the received screen information in the Web browser. When the customer approves the authentication procedure for the payment using the payment system according to the present embodiment, the “OK” button is clicked. Push. Then, a settlement request is transmitted from the customer terminal 3 to the store server 5 (step S11).

  Upon receiving the settlement request, the store server 5 transfers the settlement request to the settlement server 7 (Step S13). When transferring, the address information of the customer terminal 3 is transferred to the payment server 7 together with the payment request. In addition, store authentication information (for example, store ID and password) may be transferred separately from the store identification information or in place of the store identification information. The settlement server 7 that has received the settlement request confirms the store such as at least whether the store identification information is an actual code. If store authentication information is received, it is checked whether the store ID / password pair is correct. When the store can be confirmed by these, the order information, the address information of the store server 5, the store identification information, the management number, etc. included in the received settlement request are temporarily registered in the temporary order acceptance file. Then, the settlement server 7 generates an operation key KEY01, and an authentication confirmation screen for causing the customer terminal 3 to confirm that the customer terminal 3 will perform customer authentication from now on using the operation key KEY01 as a hidden parameter in communication with the settlement server 7. Information is transmitted (step S15). The reason why the operation key KEY01 is used is to make it possible to confirm later that this processing step has been passed.

  The customer terminal 3 displays an authentication confirmation screen in the Web browser, and the customer presses an “OK” button included in the authentication confirmation screen. Then, the authentication confirmation is transmitted from the customer terminal 3 to the settlement server 7 together with the operation key KEY01 which is a hidden parameter (step S17). The settlement server 7 confirms the validity of the received operation key KEY01. If the validity is confirmed, the settlement server 7 transmits screen information that prompts the customer ID and password to be input to the customer terminal 3 (step S19). If the validity of the operation key KEY01 is not confirmed, a problem may occur if the processing is continued as it is. For example, the store server 5 and the customer terminal 3 are notified that an error has occurred.

  The customer terminal 3 displays a screen prompting the customer ID and password to be entered in the web browser. In at least communication below this, it is necessary to protect the secret of communication using SSL (Secure Socket Layer) technology, for example. SSL may also be used in communication prior to this. In response to the request, the customer inputs the customer ID and password into the web browser and presses a send button provided on the screen in the web browser. Then, the customer terminal 3 transmits the input customer ID and password to the settlement server 7 (step S21). Here, the customer ID and password are used for the authentication process for the customer. However, when customer authentication is performed by another method, necessary information is transmitted from the customer terminal 3 to the settlement server 7. To do. If the customer ID and password are output to the settlement server 7 in this manner, the customer ID and password pair is not transmitted to the store server 5, and the customer ID and password are stored in the store that is malicious or malicious. It is possible to prevent the password from being abused.

  When the settlement server 7 receives the customer ID and password, it first determines whether the customer ID and password pair is the same as the customer information registered in the member information DB 71 in advance. If they are not the same, the process returns to step S21 to input again. For example, if the customer ID and the password are not confirmed to be the same even after checking the customer ID and password three times, the settlement server 7 transmits authentication error screen information to the customer terminal 3. The settlement server 7 may notify the store server 5 of an authentication error.

  If the received customer ID / password pair is the same as the customer information registered in advance, the authentication of the customer is completed. However, in this embodiment, it is not possible to make a payment with the payment system according to this embodiment only by customer authentication. Next, the settlement server 7 checks the system usage qualification. In this embodiment, confirmation of system use qualification is performed in two stages. First, it is confirmed whether or not the member is a normal member in a predetermined ISP. That is, even an ISP member cannot be said to be a normal member if payment for ISP usage fees is delayed. Next, it is confirmed whether the payment system according to the present embodiment is registered because it can be used. In this embodiment, since it is assumed that payment is made with a credit card, a credit card number must be registered in advance. It is also possible to set a standard so that only those who satisfy the standard can use the payment system according to the present embodiment. If the results of such customer authentication processing and system usage qualification confirmation processing are affirmative, the settlement server 7 generates an operation key KEY02 (sometimes called a session key) (step S23). It is also possible to store the operation key KEY02, order information, management number, etc. as a session file and use it for later processing.

  Then, the settlement server 7 transmits the processing result of the customer authentication processing and the system use qualification confirmation processing, and the operation key KEY02 and the management number when the processing result is affirmative to the store server 5 (step S25). . The store server 5 receives the information from the settlement server 7 (step S27). If there is an error in the system usage qualification confirmation process, the store server 5 notifies the customer terminal 3 that there is no system usage qualification, and the customer terminal 3 displays that there is no system usage qualification. (Step S29). In addition, it is registered that the order of the management number in the order information DB 51 cannot be settled.

  Thus, the customer authentication and system use qualification confirmation process, which is the previous stage of the credit process, is completed. Note that the processing flow shown in FIG. 2 can be variously modified. For example, instead of the configuration in which the store server 5 transfers the payment request in step S13, a configuration in which the payment request is directly transmitted from the customer terminal 3 to the payment server 7 is also possible. In this case, the store server 5 does not need to add the address information of the customer terminal 3 to the settlement request. In addition, the address of the settlement server 7 is embedded in the screen display of the settlement request transmitted to the customer terminal 3.

  In the above description, the processing flow is such that the system usage qualification is also confirmed, but the system usage qualification may not be specified separately. In this case, this processing flow is a customer authentication processing flow. In the case of a simple customer authentication processing flow, it is possible to adopt a form in which the order information and the management number that is the identification information of the order information are not transmitted to the settlement server 7.

  Note that the operation keys KEY01 and KEY02 may be regarded as errors in the operation key confirmation process if an expiration date is provided and the operation keys KEY01 and KEY02 do not return to the settlement server 7 within the expiration date.

[Example 2]
Next, a second embodiment of the customer authentication process and the system use qualification confirmation process will be described with reference to FIG. For example, the customer operates the customer terminal 3 to access the store server 5 (step S31). For example, the store server 5 transmits product information and an order form to the customer terminal 3 (step S33). There are various forms of processing in steps S1 and S3, and only a simple case is shown here. The customer terminal 3 displays product information and an order form with a Web browser. The customer inputs the order contents into the Web browser, presses a send button included in the order form, and sends the order information to the store server 5 (step S35). The order information includes a product name, product number, quantity, amount, address, name, telephone number, e-mail address, and the like. Further, the order information may include information that the payment system according to the present embodiment is selected as the payment method. Further, it may include an ISP customer (member) ID related to the payment system according to the present embodiment. Upon receiving the order information from the customer terminal 3, the store server 5 confirms the order information format and the like, and registers the order information in the order information DB 51 (step S37). It is also possible to make an inventory inquiry to the inventory management system 13 before registration, for example. Then, the store server 5 receives the received order information, the address information (for example, URL) of the processing unit (for example, CGI) that receives the result such as customer authentication in the store server 5, the store identification information (for example, the store child code), and the order information. The screen information of the settlement request including the management number and requesting to perform the authentication procedure for settlement of the order information is transmitted to the customer terminal 3 (step S39). It is also possible to ask whether to select the payment system according to the present embodiment as the payment means in the screen information transmitted here. The customer terminal 3 displays the received screen information in the Web browser. When the customer approves the authentication procedure for the payment using the payment system according to the present embodiment, the “OK” button is clicked. Push. Then, a settlement request is transmitted from the customer terminal 3 to the store server 5 (step S41).

  Upon receiving the settlement request, the store server 5 transfers the settlement request to the settlement server 7 (step S43). When transferring, the address information of the customer terminal 3 is transferred to the payment server 7 together with the payment request. In addition, store authentication information (for example, store ID and password) may be transferred separately from the store identification information or in place of the store identification information. The settlement server 7 that has received the settlement request confirms the store such as at least whether the store identification information is an actual code. If store authentication information is received, it is checked whether the store ID / password pair is correct. When the store can be confirmed by these, the order information, the address information of the store server 5, the store identification information, the management number, etc. included in the received settlement request are temporarily registered in the temporary order acceptance file. Then, the settlement server 7 generates an operation key KEY01, and transmits to the customer terminal 3 screen information that prompts the customer terminal 3 to input the customer ID and password, using the operation key KEY01 as a hidden parameter (step S45). . The reason why the operation key KEY01 is used is to make it possible to confirm later that this processing step has been passed.

  The customer terminal 3 displays a screen prompting the customer ID and password to be entered in the web browser. In at least communication below this, it is necessary to protect the secret of communication using SSL (Secure Socket Layer) technology, for example. SSL may also be used in communication prior to this. In response to the request, the customer inputs the customer ID and password into the web browser and presses a send button provided on the screen in the web browser. Then, the customer terminal 3 transmits the input customer ID and password to the settlement server 7 (step S47). If the customer ID and password are output to the settlement server 7 in this manner, the customer ID and password pair is not transmitted to the store server 5, and the customer ID and password are stored in the store that is malicious or malicious. It is possible to prevent the password from being abused. Further, the customer terminal 3 transmits an operation key KEY01 to the settlement server 7.

  The settlement server 7 confirms the validity of the received operation key KEY01. If the validity is not confirmed, a problem may occur if the processing is continued as it is, so that, for example, the store server 5 and the customer terminal 3 are notified that an error has occurred. Further, the settlement server 7 determines whether or not the received customer ID and password pair is the same as customer information registered in advance. If they are not the same, the process returns to step S47 to input again. For example, if the customer ID and the password are not confirmed to be the same even after checking the customer ID and password three times, the settlement server 7 transmits authentication error screen information to the customer terminal 3. The settlement server 7 may notify the store server 5 of an authentication error.

  If the received customer ID / password pair is the same as the customer information registered in advance, the authentication of the customer is completed. However, in this embodiment, it is not possible to make a payment with the payment system according to this embodiment only by customer authentication. Next, the settlement server 7 checks the system usage qualification. Also in this embodiment, confirmation of system use qualification is performed in two stages. First, it is confirmed whether or not the member is a normal member in a predetermined ISP. That is, even an ISP member cannot be said to be a normal member if payment for ISP usage fees is delayed. Next, it is confirmed whether the payment system according to the present embodiment is registered because it can be used. Since this embodiment also presupposes that payment is made with a credit card, the credit card must be registered in advance. It is also possible to set a standard so that only those who satisfy the standard can use the payment system according to the present embodiment. If the results of such customer authentication processing and system usage qualification confirmation processing are affirmative, the settlement server 7 generates an operation key KEY02 (also called a session key) (step S49). It is also possible to store the operation key KEY02, order information, management number, etc. as a session file and use it for later processing.

  Then, the settlement server 7 transmits the processing result of the customer authentication processing and the system usage qualification confirmation processing, and the operation key KEY02 and the management number if the processing result is affirmative to the store server 5 (step S51). . The store server 5 receives the information from the settlement server 7 (step S53). If there is an error in the system usage qualification confirmation process, the store server 5 notifies the customer terminal 3 that there is no system usage qualification, and the customer terminal 3 displays that fact (step S55). . In addition, it is registered that the order of the management number in the order information DB 51 cannot be settled.

  Thus, the customer authentication and system use qualification confirmation process, which is the previous stage of the credit process, is completed. Note that the processing flow shown in FIG. 3 can be variously modified. For example, instead of the configuration in which the store server 5 transfers the payment request in step S43, a configuration in which the payment request is directly transmitted from the customer terminal 3 to the payment server 7 is also possible. In this case, the store server 5 does not need to add the address information of the customer terminal 3 to the settlement request. In addition, the address of the settlement server 7 is embedded in the screen display of the settlement request transmitted to the customer terminal 3.

  Further, as described in the first embodiment, the processing flow is such that the system usage qualification is also confirmed. However, the system usage qualification may not be specified separately. In this case, this processing flow is a customer authentication processing flow. In the case of a simple customer authentication processing flow, it is possible to adopt a form in which the order information and the management number that is the identification information of the order information are not transmitted to the settlement server 7.

  Note that the operation keys KEY01 and KEY02 may be regarded as errors in the operation key confirmation process if an expiration date is provided and the operation keys KEY01 and KEY02 do not return to the settlement server 7 within the expiration date.

2. Credit Processing FIG. 4 shows a flow of credit processing for a customer in which no error has occurred in the customer authentication processing and the system use qualification confirmation processing. As described above with reference to FIG. 1, the store server 5 performs processing on the functional part of the store server 5 (hereinafter referred to as store-side processing unit 55 (for example, CGI)) prepared by the store side and the settlement server 7. A settlement server command interface (IF) program 53 is provided. In the present embodiment, these will be described separately.

  First, the store side processing unit 55 of the store server 5 searches the order information DB 51 with the management number (step S27 or S53) received from the settlement server 7 and extracts the order information related to the management number (step S61). For example, at this point in time, the store-side processing unit 55 can check the stock of the product related to the order with respect to the stock management system 13 (step S63). Since this step may be performed if cooperation with the inventory management system 13 is possible, this step S63 is surrounded by a dotted line in FIG. If it is determined that the item is out of stock, the store side processing unit 55 notifies the customer terminal 3 that the item is out of stock, and the customer terminal 3 displays a notification of out of stock (step S65).

  When not cooperating with the inventory management system 13 or when the inventory is confirmed, the store side processing unit 55 outputs the operation key KEY02, the management number, and the order information received from the settlement server 7 to the settlement server command IF program 53. (Step S67). It is also possible to adopt a configuration in which information on the credit card expiration date obtained separately from the customer is also output. The settlement server command IF program 53 transmits store authentication information to the settlement server 7 in addition to the information received from the store side processing unit 55 (step S69).

  The settlement server 7 checks the validity of the received operation key KEY02 using, for example, a session file that stores the transmitted operation key KEY02. If the operation key has an expiration date, it is also checked whether it has been received within the expiration date. Further, the continuity of processing and the validity of the information are confirmed by comparing the order information and management number stored in the session file with the order information and management number received this time. If an error is detected in these confirmations, the subsequent processing is not performed, and the process proceeds to step S77. Further, the settlement server 7 performs store authentication processing using the received store authentication information, that is, a pair of store ID and password (step S71). If the store authentication fails, the process also proceeds to step S77. If the store authentication is successful, the credit card number of the customer determined to be a legitimate customer in the customer authentication process and the system use qualification confirmation process is taken out from the database storing the customer information, and the credit card is properly used using CAFIS9. A credit process for confirming whether it is correct is performed (step S73). For example, if it can be confirmed that the credit card is appropriate, an approval number can be obtained from CAFIS9. If the credit process fails, that is, if there is a problem with the credit card credit limit or expiration date, the process proceeds to step S77.

  If the credit processing is successful in step S73, the received order information is registered in the settlement order information DB 75 of the settlement server 7. And the receipt number (it may be a symbol instead of a number) which is the identification information of the said order information in the payment server 7 is issued (step S75). As a result, the order is confirmed as an order in the settlement server 7. In the payment server 7, the reception number, the management number, and the order information are associated with each other and stored in the payment order information DB 75.

  Then, the settlement server 7 transmits the processing results up to steps S71 and S73, and if the order information can be registered, the reception number and the management number to the settlement server command IF program 53 of the store server 5 (step S77). ). The settlement server command IF program 53 outputs the received information to the store side processing unit 55 (step S79). When the received processing result indicates that the processing up to steps S71 and S73 is successful, the store side processing unit 55 stores the received receipt number and management number in the order information DB 51 and the corresponding order. Information is registered in association with each other. If the receipt number is registered, the order has been confirmed. It is also possible to register an order confirmation separately. Further, it is possible to adopt a configuration in which information (order information, reception number and management number) related to an order for which an order has been confirmed is moved or copied to another order information database (DB) and used for later processing. If the received processing result indicates that any of the processings has failed, the order information DB 51 registers in the order information DB 51 that the settlement is impossible. In either case of success or failure, the store side processing unit 55 transmits a part of the processing result received to the customer terminal 3 that can be disclosed to the customer (step S81). For example, information such as “Payment registration completed. Order registration completion notification will be sent separately from the payment server via e-mail” or “Payment registration failed because the credit card has expired” is sent. The customer terminal 3 displays the received processing result in the web browser (step S83). When an error occurs in the store authentication process, the store server 5 may request the payment server 7 for the credit process again.

  Further, the settlement server 7 transmits an order registration notification mail for notifying the customer that the order information has been registered in the settlement server 7 (step S85). On the other hand, the customer terminal 3 receives the order registration notification mail (step S91). The order registration notification mail is transmitted for confirmation to the customer. In addition, the reception of the mail at the customer terminal 3 may not be performed immediately after the transmission.

  Further, the store-side processing unit 55 of the store server 5 can also check the inventory of the product related to the order with respect to the inventory management system 13 for the shipment of the next product to be performed. (Step S87). Whether or not to check the inventory is arbitrary. If the stock is confirmed at this stage and it is found that the stock is out of stock, the store-side processing unit 55 of the store server 5 sends an out-of-stock email to the customer, for example, and cancels the order described later. Implement the process. The customer terminal 3 receives an out-of-stock mail (step S89). Further, the store side processing unit 55 registers the order cancellation in the order information DB 51.

  Whether the inventory check process is performed for the inventory management system 13 and the inventory check process is not performed, a predetermined process for shipping is requested or executed by another system, or the distribution system 15 is informed. On the other hand, a collection request is transmitted, or permission for downloading the program and content data to the customer terminal 3 is output to the download server 17 (step S93). Whether or not to execute step S93 also depends on the configuration of the store system including the store server 5. Therefore, step S93 may not be performed at all.

  By performing such processing, credit processing and order confirmation processing are performed.

3. Order Cancellation / Return Processing In FIG. 5, for example, as described above, when an order is canceled due to out of stock, when a product is returned from a customer, or when a customer cancels an order after receiving an order registration notification email, etc. Processing to be performed will be described.

  The store side processing unit 55 of the store server 5 first specifies the receipt number or the management number of the order for which the order has been canceled or returned (step S101). This is performed, for example, by the store staff operating the store terminal 11 and searching the order information DB 51. For example, when the store staff instructs using the store terminal 11 to perform the cancellation process using the specified reception number or management number, the store side processing unit that receives the instruction from the customer terminal 3 55 outputs the cancellation request and the reception number or management number to the settlement server command IF program 53 (step S103). It is also possible to send the reason for cancellation together.

  The payment server command IF program 53 transmits the store authentication information and the reception number or the management number to the processing unit for canceling the order of the payment server 7 (step S105). It is also possible to send the reason for cancellation together. The settlement server 7 performs an authentication process for the store using the received store authentication information (step S107). If an error occurs in the authentication process, the process proceeds to step S117. If the store authentication is successful, a credit cancellation process is performed (step S109). For example, when an approval number is obtained from the CAFIS 9, the credit cancellation process is performed on the CAFIS 9 with respect to the approval number. Credit cancellation processing may fail for some reason. In this case, the process proceeds to step S117.

  If the credit cancellation process is successful, the credit cancellation is registered for the order information corresponding to the management number or the reception number registered in the settlement order information DB 75 of the settlement server 7 (step S111). As a result, it is possible to prevent the billing process from being performed later for an order related to cancellation. Then, a credit cancellation registration notification e-mail for notifying that the credit cancellation has been registered is transmitted to the customer who has placed the credit canceled order (step S113). The customer receives the credit cancellation registration notification mail at the customer terminal 3 (step S115). As a result, the customer can also confirm that the order has been officially canceled in the settlement server 7.

  Thereafter, the settlement server 7 transmits the processing result to the settlement server command IF program 53 of the store server 5 (step S117). The settlement server command IF program 53 receives the processing result and outputs it to the store side processing unit 55 (step S119). For example, the store side processing unit 55 registers the processing result in the order information DB 51 (step S121). Moreover, the structure which notifies a process result to the shop terminal 11 is also possible. If credit revocation fails, credit revocation processing must be performed until revocation is possible.

4). Search processing The order information stored in the order information DB 51 of the store server 5 and the order information stored in the settlement order information DB 75 of the settlement server 7 are collated, and the order information is retrieved from the store server 5 to the settlement server 7. May be requested. The search process will be described with reference to FIG. The search process includes an order status list reference process and an order status detail reference process. In the order status list reference process, it is possible to specify an acceptance number, a management number, a processing state, a customer ID, a search condition for a period, etc., and obtain an output that enumerates corresponding order information. On the other hand, in the order status detail reference process, when the reception number or management number is input as a search condition, the details of the corresponding order information can be acquired.

  For example, when a store staff operating the store terminal 11 determines and inputs a search condition and instructs the store terminal 11 to execute a search, the store terminal 11 transmits a search command including the search condition to the store server 5. The store side processing unit 55 of the store server 5 that has received the search command outputs the search request and the input search condition to the payment server command IF program 53 (step S131). The payment server command IF program 53 transmits the store authentication information and the received search condition to the processing unit that performs the search processing of the payment server 7 (step S133). The settlement server 7 performs a store authentication process using the received store authentication information (step S135). If an error occurs in the authentication process, the process proceeds to step S139. When the store is authenticated by the authentication process, the order information registered in the settlement order information DB 75 of the settlement server 7 is searched under the received search condition. Then, order information that matches the search condition is extracted (step S137).

  The settlement server 7 transmits the order information extracted in step S137 to the settlement server command IF program 53 of the store server 5 (step S139). If the store authentication fails, information indicating the failure is transmitted instead of the extracted information. The settlement server command IF program 53 receives the extracted order information and outputs it to the store side processing unit 55 (step S141). The store side processing unit 55 outputs the received order information and the like to the store terminal 11 (step S143). The store terminal 11 displays the received order information and the like to store staff.

  Thereby, not only the order information DB 51 of the store server 5 but also the order information and the processing status can be confirmed by the order information registered in the settlement order information DB 75 of the settlement system 7.

5. Customer confirmation processing Apart from customer authentication processing and system usage qualification confirmation processing, only the system usage qualification of the payment system according to this embodiment or only the membership qualification of ISP is confirmed before receiving an order, for example. It is convenient that customer confirmation can be easily performed when a special service or the like is provided only to a person who has the system use qualification of the payment system. FIG. 7 shows a processing flow for customer confirmation.

  First, the store side processing unit 55 of the store server 5 outputs screen information prompting the customer ID to be input to the customer terminal 3 after some processing (step S151). The customer terminal 3 displays the received screen information in the Web browser, and the customer inputs the customer ID in response to a request for inputting the customer ID, and presses the “SEND” button in the Web browser. Then, the customer terminal 3 transmits a customer ID to the store server 5 (step S153).

  Upon receiving the customer ID from the customer terminal 3, the store side processing unit 55 of the store server 5 outputs the customer ID to the payment server command IF program 53 (step S155). The settlement server command IF program 53 transmits the store authentication information and the received customer ID to the customer confirmation processing section of the settlement server 7 (step S157). The settlement server 7 performs store authentication processing using the received store authentication information (step S159). If the store authentication fails, the process proceeds to step S163. If the store authentication is successful, the settlement server 7 performs a customer confirmation process using the customer ID (step S161). Here, in the customer confirmation process, as described above, it is confirmed whether or not the customer is a normal member of a predetermined ISP, and in addition, the settlement system according to the present embodiment can be used. It is also possible to adopt a configuration in which only whether or not the member is a normal member of a predetermined ISP is confirmed.

  In any case, the payment server 7 transmits the processing result of the customer confirmation process to the payment server command IF program 53 (step S163). When an error occurs in the store authentication process, a result that the error has occurred in the store authentication process is transmitted to the command IF program 53 for payment server. The settlement server command IF program 53 receives the processing result and outputs it to the store side processing unit 55 (step S165). The store side processing unit 55 refers to the received processing result and performs the following predetermined processing. For example, if the customer can be confirmed, the customer terminal 3 is prompted to input order information, or screen information for presenting a special product is output (step S167). If the customer cannot be confirmed, the customer terminal 3 is prompted to input the customer ID again, or screen information including a display indicating that the order cannot be received is transmitted to the customer terminal 3. If the store authentication fails, the payment command IF program 53 may be instructed to execute the customer confirmation process again.

  As described above, it is possible to cause the settlement server 7 to perform customer confirmation separately from the customer authentication process and the system use qualification confirmation process.

6). Sales confirmation processing In response to customer orders, for example, after delivering products or providing services, or downloading programs or content data, you must perform processing to finalize sales. . FIG. 8 shows a flow of the sales confirmation process.

  First, the store side processing unit 55 of the store server 5 receives, for example, a delivery completion notification from the distribution system 15, for example, when a delivery completion input is made from the store terminal 11, for example, a download completion notification from the download server 17. When received, the reception number or management number to be determined for sales is specified from the notification or input. For example, if information related to delivery, such as a delivery request number, is input to the order information DB 51, the order can be specified by the delivery request number included in the delivery completion notification, so that the management number or the reception number can be extracted from the order information DB 51. . It is also possible to always include a reception number or a management number in a delivery completion notification or the like. In any case, the receipt number or management number of the order to be determined for sales is output from the store side processing unit 55 to the payment server command IF program 53 (step S171).

  The settlement server command IF program 53 transmits the store authentication information and the reception number or the management number to the sales confirmation processing section of the settlement server 7 (step S173). The settlement server 7 performs store authentication processing using the store authentication information (step S174). The store authentication information is, for example, a store ID and a password, and the settlement server 7 determines whether or not the store ID and password of the store information registered in the store information DB 73 in advance are the same. If the store authentication fails, the process proceeds to step S179. On the other hand, when the store authentication is successful, the settlement server 7 specifies the order information in the settlement server 7 from the received reception number or management number, and registers the sales confirmation for the order information (step S175). Since the management number or the reception number may be input incorrectly, the order information cannot be specified in the settlement server 7 in some cases. In this case, the process proceeds to step S179.

  Next, the settlement server 7 performs an order price billing process (step S177). The order price billing process is, for example, a process of writing order information in a billing file 77 for a credit card company that settles the order. For example, the billing file 77 is sent to a credit card company once a month. Credit card companies charge customers for money. Further, the settlement server 7 registers information indicating that the order has been charged in the settlement order information DB 75.

  If implemented so far, the settlement server 7 transmits the processing results of steps S174 to S177 to the settlement server command IF program 53 (step S179). The settlement server command IF program 53 receives the processing result from the settlement server 7 and outputs it to the store side processing unit 55 (step S181). If the processing result indicates success, the store side processing unit 55 registers billed or sales confirmed with respect to the order information of the transmitted management information or reception information in the order information DB 51 (step S183). If the processing result indicates failure, for example, the processing result can be output to the store terminal 11 to ask for confirmation of the reception number or the management number, or to automatically retry.

  This completes the sales confirmation process. The price of the order whose sales are confirmed is paid to the store from the credit card company, and the credit card company charges the customer and receives the price from the customer.

  The embodiment of the present invention has been described above. The above description is based on the assumption that the customer is a member of the ISP, but it is also possible to make it a condition that the customer is a member of another group.

  In the present embodiment, the store server 5 is provided with the store side processing unit 55 and the settlement server command IF program 53. However, whether or not to divide such functions is arbitrary. The payment server command IF program 53 can also be divided into a plurality of functional modules.

  Further, for the store side processing unit 55 and the settlement server 7 of the store server 5, it is possible to provide a separate processing unit (for example, CGI) for each of the processes 1 to 6 described above, and the same processing It is also possible to adopt a configuration in which a unit (for example, CGI) performs processing. It is also possible to perform processing by providing a plurality of processing units in each of the processes 1 to 6 described above.

  In addition, the store server 5 may be physically implemented by a single computer, or may be implemented by a plurality of computers. The same applies to the settlement server 7.

(Appendix 1)
When receiving an order request from a customer terminal, register the customer order content information in an order storage device, and send at least identification information and store information of the customer order to the customer terminal or payment system Means,
Credit request pre-processing means for retrieving content information of the customer order from the order storage device using the customer order identification information when receiving the customer order identification information and session key from the payment system; ,
Credit request means for transmitting the content information of the customer's order retrieved from the order storage device, the session key, and authentication information of the store to the payment system;
And a credit result processing means for storing, in the order storage device, information indicating an order received for the customer's order when information indicating that the customer's order can be received is received from the payment system.

(Appendix 2)
The computer system according to claim 1, wherein the credit result processing means further receives identification information in the payment system for the customer's order from the payment system and stores it in the order storage device.

(Appendix 3)
2. The computer system according to claim 1, wherein the credit result processing means transmits information indicating whether or not the customer can accept an order in accordance with information received from the payment system to the customer terminal.

(Appendix 4)
When the credit result processing means receives information indicating that the customer's order can be received, the system related to the shipment of the product related to the customer's order is requested to process the shipment of the product. The computer system according to appendix 1, wherein:

(Appendix 5)
When the credit result processing means receives information indicating that the customer's order can be received, information indicating that the data distribution related to the customer order is permitted to be distributed. The computer system according to appendix 1, wherein transmission is performed.

(Appendix 6)
When the credit result processing means receives information indicating that the customer's order can be accepted, the credit result processing means transmits a collection request for the product to a logistics system related to the collection of the product related to the customer's order. The computer system according to appendix 1.

(Appendix 7)
The computer system according to appendix 1, wherein the accepting unit performs an inventory confirmation process for commodities related to the customer's order.

(Appendix 8)
2. The computer system according to claim 1, wherein the credit request pre-processing means performs an inventory check process for commodities related to the customer order.

(Appendix 9)
The computer system according to appendix 1, wherein the credit result processing means performs inventory confirmation processing for commodities related to the customer order.

(Appendix 10)
When receiving an order request from a customer terminal, registering the customer order content information in an order storage device, and transmitting at least identification information and store information of the customer order to the customer terminal or payment system When,
Retrieving the customer order content information from the order storage device using the customer order identification information upon receipt of the customer order identification information and session key from the payment system;
Transmitting the customer order content information retrieved from the order storage device, the session key, and store authentication information to the payment system;
When receiving information indicating that the customer's order can be received from the payment system, storing information indicating the order for the customer's order in the order storage device;
Including order processing methods.

(Appendix 11)
When receiving an order request from a customer terminal, registering the customer order content information in an order storage device, and transmitting at least identification information and store information of the customer order to the customer terminal or payment system When,
Retrieving the customer order content information from the order storage device using the customer order identification information upon receipt of the customer order identification information and session key from the payment system;
Transmitting the customer order content information retrieved from the order storage device, the session key, and store authentication information to the payment system;
When receiving information indicating that the customer's order can be received from the payment system, storing information indicating the order for the customer's order in the order storage device;
A program that causes a computer to execute.

It is a block diagram which shows the outline | summary of the whole system in this invention. It is a flowchart of the customer authentication process and system use qualification confirmation process which concern on Example 1. FIG. 12 is a flowchart of customer authentication processing and system usage qualification confirmation processing according to the second embodiment. It is a flowchart of a credit process. It is a flowchart of order cancellation / return processing. It is a flowchart of a search process. It is a flowchart of a customer confirmation process. It is a flowchart of a sales decision process.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Network 3 Customer terminal 5 Store server 7 Settlement server 9 CAFIS 11 Store terminal 13 Inventory management system 15 Logistics system 17 Download server

Claims (2)

An order processing method executed by a store system that performs communication between a customer terminal and a payment system,
When receiving an order request from the customer terminal, registering the customer order content information in the order storage device;
In order to perform customer authentication processing related to the order request between the customer terminal and the payment system, an address of the customer terminal, at least identification information of the customer order, and identification information of the store Transmitting to the payment system, or transmitting the payment system information, at least identification information of the customer order, and identification information of the store to the customer terminal;
Credit request pre-processing step of receiving identification information of the customer order from the payment system and a session key generated in the payment system when the customer authentication process is successful;
In order for the payment system to perform credit processing related to the order request, at least the identification information of the customer order, the identification information of the store, and the payment system before the credit processing related to the order request is performed. Transmitting a credit request including the session key, which is the data confirmed in step 1, to the settlement system;
When the session key is confirmed to be correct in the payment system and credit processing is successful, indicating that the customer can receive an order for the order and receiving information related to the order request from the payment system, Storing information indicating an order for the customer's order in the order storage device;
Including order processing methods.   The order processing method according to claim 1, wherein in the credit request pre-processing step, a predetermined process is performed after the session key is received.

Images