JP2015075947A - Information processing system, selling/buying support server, seller terminal and purchaser terminal - Google Patents

Abstract

PROBLEM TO BE SOLVED: To effectively support customer services in a shop on the basis of the action of a purchaser declaring a future visit to the shop of a seller.SOLUTION: A selling/buying support server 14 acquires visit information that indicates a visit of a purchaser to a shop of a seller and is inputted by the seller or the purchaser. The selling/buying support server 14 provides an image indicating a look of the purchaser shown in the visit information and customer service support information relating to the purchaser to a shop terminal 12. The shop terminal 12 displays a selection screen in which images of purchasers provided from the selling/buying support server 14 are displayed side by side, for the seller to select the image of the purchaser, and displays customer service support information relating to the purchaser selected on the selection screen. The shop terminal 12 notifies the selling/buying support server 14 of a settlement request designating the purchaser selected on the selection screen and on the basis of information of the purchaser designated in the settlement request, the selling/buying support server 14 executes an electronic settlement of payment of goods or services.

Description

  The present invention relates to a data processing technique, and more particularly to an information processing technique for supporting the buying and selling of goods or services.

  The rapid spread of smartphones and tablet terminals has a major impact in the payment field. In recent years, solutions that apply smartphones and tablet terminals to credit card payment terminals have also appeared.

  In addition, a credit card settlement service using the user's “face (photo)” and “name” has also appeared using the same terminal. In this service, when a check-in operation for designating an actual store is performed on the user's terminal, the user's information is notified to the store side, and the user's face photo and name are displayed on the store terminal. After that, when the user actually visits the store and purchases a product, the payment is completed by confirming the user's “face” and “name”.

“PayPal Here”, which allows easy card payment on smartphones, is fully introduced in July, [online], May 9, 2012, URL, http://www.itmedia.co.jp/mobile/articles/1205/ 09 / news121.html

  The act of check-in by the purchaser (user) of the product or service can be said to be an expression of intention that the purchaser will visit the store of the seller in the future. In Non-Patent Document 1, the purchaser's act of check-in is used for a settlement service using the purchaser's face and name. On the other hand, the present inventor considered that the idea of utilizing the purchaser's act of check-in for customer service support at the store of the seller and the specific method thereof have not been sufficiently proposed so far.

  The present invention has been made on the basis of the above-mentioned problem recognition by the inventor, and its main purpose is effective customer service at the store based on the purchaser's act expressing that he will visit the seller's store in the future. It is to provide the technology to support.

  In order to solve the above problems, an information processing system according to an aspect of the present invention includes a seller terminal of a product or service and a server connected to the seller terminal via a communication network. The server includes a customer service support information holding unit that stores customer service support information for each purchaser of the product or service, and information indicating that the purchaser plans to visit the seller's store in the future. A visit information acquisition unit for acquiring visit information input by the buyer, a purchaser image providing unit for providing an image showing the appearance of the purchaser indicated by the visit information to the seller's terminal, and a customer service regarding the purchaser indicated by the visit information And a customer service support information providing unit that provides support information to the seller's terminal. The seller's terminal is a screen in which the images of the buyers provided from the server are arranged, and a selection screen display unit for displaying a selection screen for allowing the seller to select an image of the customer who is serving customers, and a selection screen The customer support information display unit that displays the customer service support information provided from the server for the purchaser whose image is selected in step 1, and the payment request that notifies the server of the payment request that specifies the purchaser whose image is selected on the selection screen And a notification unit. The server includes a payment information holding unit that holds payment information for each purchaser necessary for electronic payment of goods or services, and purchaser payment information specified by a payment request notified from the seller's terminal. And a payment processing unit that executes electronic payment for the price of goods or services.

  Another aspect of the present invention is a trade support server. This sales support server is a server connected to a terminal of a merchandise or service seller via a communication network, a customer support information holding unit that holds customer support information for each purchaser of the product or service, and a sales Information indicating that the purchaser intends to visit the store in the future, the visit information acquisition unit for acquiring the visit information input by the seller or the purchaser, and the appearance of the purchaser indicated by the visit information A purchaser image providing unit that displays a selection screen on the seller's terminal for the seller to select an image of the purchaser who serves customers at the seller's store by providing the image shown to the seller's terminal; Providing customer support information related to the purchaser indicated by the information to the seller's terminal, providing customer support information related to the purchaser whose image is selected on the selection screen to be displayed on the seller's terminal And, equipped with a. The seller's terminal notifies the server of a payment request specifying the purchaser whose image has been selected on the selection screen, and payment information for each purchaser required for electronic payment of the price of goods or services. A payment information holding unit that holds the payment information, and a payment processing unit that executes electronic payment for the price of the product or service using the payment information of the purchaser specified in the payment request notified from the seller's terminal, Further prepare.

  Yet another embodiment of the present invention is a seller terminal. This merchant terminal is a terminal of a merchandise or service merchant and is information indicating that the purchaser of the merchandise or service is planning to visit the merchant's store in the future. Purchaser image acquisition unit that acquires an image showing the appearance of the purchaser indicated by the visit information provided from the server that acquired the input visit information, and customer service support for the purchaser provided by the visit information provided from the server Selection screen display that displays a customer support information acquisition unit for acquiring information and a purchaser image provided by the server, and displays a selection screen for allowing the seller to select the purchaser image to be received The customer support information display unit that displays the customer service support information provided from the server and the purchaser whose image is selected on the selection screen. Was by notifying the settlement request to the server, it includes a settlement request notification unit to execute the electronic payment of the price of the product using the information of the buyer or service to the server, the.

  Yet another aspect of the present invention is a purchaser terminal. The purchaser terminal is a purchaser terminal of a product or service, a reception unit that receives a predetermined operation input by the purchaser for registering a future visit to the store of the seller of the product or service, and a predetermined unit The first verification to be notified to the purchaser by notifying the server of visit information indicating that the purchaser intends to visit the seller's store in the future when the operation input is received. The second collation information that can identify information is recorded in association with the purchaser, and an image showing the appearance of the purchaser indicated by the visit information and customer service support information regarding the purchaser indicated by the visit information are displayed by the seller. A screen that displays images of buyers provided from the server on the seller's terminal, and displays a selection screen that allows the seller to select a customer's customer image to serve. Information on the visitor information that displays the customer service support information provided by the server for the purchaser with the image selected, and information on the purchaser with the image selected on the selection screen on the seller's terminal and acquired from the purchaser The server is notified of the settlement request designating the designated first collation information, and the server records the first collation information designated by the settlement request and the purchaser designated by the settlement request. The first verification information newly generated as a response to a predetermined operation input in order to determine whether or not the electronic payment of the price of the goods or services is permitted based on the presence or absence of the matching with the second verification information Is displayed on the screen, and a verification information notification unit that notifies the purchaser of the first verification information is provided.

  Note that any combination of the above-described constituent elements and a representation of the present invention converted between a method, a program, a recording medium storing the program, and the like are also effective as an aspect of the present invention.

  According to the present invention, it is possible to support effective customer service at a store based on the purchaser's act expressing that he or she will visit the store in the future.

It is a figure which shows the structure of the goods trading system of 1st Embodiment. It is a block diagram which shows the function structure of the purchaser terminal of FIG. It is a block diagram which shows the function structure of the shop terminal of FIG. It is a figure which shows the structure of the check-in information for stores. It is a block diagram which shows the structure of the sales support server of FIG. FIG. 6A shows the configuration of user registration information, and FIG. 6B shows the configuration of user check-in information. It is a figure which shows a store detail screen. It is a figure which shows a check-in screen. It is a figure which shows a goods selection screen. It is a figure which shows an accounting screen. It is a figure which shows a face pass payment screen. It is a figure which shows the structure of the goods trading system of 2nd Embodiment. It is a block diagram which shows the function structure of the buyer terminal of FIG. It is a block diagram which shows the function structure of the salesclerk operation terminal of FIG. It is a block diagram which shows the function structure of the reception terminal in a shop of FIG. It is a block diagram which shows the function structure of the sales assistance server of FIG. It is a figure which shows the structure of queue information. It is a figure which shows the structure of waiting time information. It is a figure which shows a check-in store confirmation screen. It is a figure which shows a reception screen. It is a figure which shows an order waiting management screen. It is a block diagram which shows the function structure of the purchaser terminal of FIG. It is a block diagram which shows the function structure of the sales support server of FIG. It is a block diagram which shows the function structure of the shop terminal of FIG. It is a figure which shows a purchaser selection screen. It is a figure which shows a purchaser selection screen. It is a figure which shows the structure of the goods trading system of 6th Embodiment. It is a block diagram which shows the function structure of the purchaser terminal of FIG. It is a block diagram which shows the function structure of the sales assistance server of FIG. FIG. 30 is a block diagram illustrating in detail a customer service support unit in FIG. 29. It is a block diagram which shows the function structure of the shop terminal of FIG. It is a figure which shows the one aspect | mode of a customer service support screen. It is a figure which shows the one aspect | mode of a customer service support screen. It is a figure which shows the one aspect | mode of a customer service support screen. It is a figure which shows the one aspect | mode of a customer service support screen. It is a figure which shows the one aspect | mode of a customer service support screen. It is a figure which shows the one aspect | mode of a customer service support screen. It is a figure which shows the one aspect | mode of a customer service support screen. It is a figure which shows the one aspect | mode of a customer service support screen. It is a figure which shows the one aspect | mode of a customer service support screen. It is a figure which shows the one aspect | mode of a customer service support screen. It is a figure which shows the one aspect | mode of a customer service support screen.

  Hereinafter, a plurality of embodiments relating to a card payment service using the face and name of a purchaser of a product or service, that is, “face pass payment” will be described. Specifically, as a first embodiment, a merchandise trading system for supporting both convenience and safety of settlement by face pass settlement will be described. As a second embodiment, a merchandise buying and selling system that further improves the convenience of service purchase by providing a user with a highly accurate waiting time will be described. As a third embodiment, a merchandise trading system that provides convenience of face pass settlement for merchandise sales at a mobile sales store will be described.

  As a fourth embodiment, a merchandise trading system that supports face pass settlement at a store where a purchaser of a merchandise or service designates a visit date in advance and reserves a visit will be described. As a fifth embodiment, a commodity trading system that realizes automatic check-in using acoustic communication will be described. As a sixth embodiment, a merchandise trading system that supports not only face pass settlement but also effective customer service at a store based on a check-in or a visit reservation of a seller will be described. The technology described in each embodiment may be realized on the premise of the technology described in the other embodiments and modifications, in other words, any technology with the technology described in the other embodiments and modifications. Of course, combinations and substitutions are possible.

(First embodiment)
In the first embodiment, a merchandise trading system in which identity verification using a one-time code (in other words, a one-time password) is added while maintaining a face pass settlement using “face (photo)” and “name” Propose. According to this system, the accuracy of identity verification can be improved while maintaining the simplicity and convenience of settlement by face pass settlement, and fraud on the user side and the store side can be suppressed.

  FIG. 1 shows a configuration of a commodity trading system 100 according to the first embodiment. The merchandise sales system 100 includes a purchaser terminal 10a, a purchaser terminal 10b, and a purchaser terminal 10c, which are collectively referred to as the purchaser terminal 10, and a store terminal 12a, a store terminal 12b, and a store terminal 12c, which are collectively referred to as the store terminal 12. A trading support server 14 and a settlement server 16 are provided. 1 are connected via wireless and wired communication networks including LAN, WAN, and the Internet.

  The purchaser terminals 10a to 10c are users who are in a position to purchase products, and are information processing terminals held by a plurality of users who use face pass settlement (hereinafter referred to as “users”) when purchasing the products. . The purchaser terminal 10 is preferably a portable information terminal that a user carries when moving, for example, a smartphone. As a modification, a stationary PC installed in a user's house may be used.

  The store terminals 12a to 12c are information processing terminals that are installed in each of a plurality of stores that actually exist in the real world and are operated by salespersons (employees) of each store. The store terminal 12 of the present embodiment is assumed to be a tablet terminal (tablet computer). The store terminal 12 is installed with an application for executing accounting processing and settlement processing related to product sales, that is, an application for realizing a cash register function.

  The trading support server 14 is an information processing apparatus that transmits and receives data to and from the purchaser terminal 10, the store terminal 12, and the settlement server 16 via a communication network. The buying and selling support server 14 provides a service for the user that supports the act of the user actually visiting the store and purchasing the product, and a service for the store for supporting the act of selling the product at the store. .

  The settlement server 16 is an information processing apparatus installed in a financial institution such as a credit card company or a bank, and executes electronic settlement processing in accordance with a settlement instruction from the trading support server 14. In this embodiment, credit card settlement is executed.

Next, the configuration of the purchaser terminal 10, the store terminal 12, and the buying and selling support server 14 will be described in detail.
FIG. 2 is a block diagram showing a functional configuration of the purchaser terminal 10 of FIG. The purchaser terminal 10 includes a touch panel 20 and a control unit 24. The control unit 24 includes an operation detection unit 26, a display control unit 28, a communication processing unit 30, and a product purchase support unit 32.

  Each block shown in the block diagram of the present specification can be realized in terms of hardware by an element such as a CPU and a memory of a computer or a mechanical device, and in terms of software, it can be realized by a computer program or the like. , Depicts functional blocks realized by their cooperation. Therefore, those skilled in the art will understand that these functional blocks can be realized in various forms by a combination of hardware and software. The same applies to the subsequent block diagrams.

  For example, a program module corresponding to each functional block in the control unit 24 is stored in a storage such as a flash memory of the purchaser terminal 10, and the CPU of the purchaser terminal 10 reads the program module into the main memory and executes it. Thus, the function of the control unit 24 may be realized. Further, the control unit 24 may store various data in a storage area such as a storage or a main memory, and execute data processing related to each functional block with reference to the data. In addition, application software corresponding to the product purchase support unit 32 may be distributed in a recording medium or a download format and installed in the purchaser terminal 10.

  The touch panel 20 is a display device (for example, a liquid crystal panel) integrally formed with an input device (for example, a touch pad). The operation detection unit 26 provides a function as a touch panel driver. For example, the operation detection unit 26 detects a user operation input to the touch panel 20 and passes the operation content to the product purchase support unit 32. The display control unit 28 also provides a function as a touch panel driver, and displays text data and image data passed from the product purchase support unit 32 on the touch panel 20, for example.

  The communication processing unit 30 controls wireless communication with an external device. In the embodiment, the communication processing unit 30 transmits the data passed from the product purchase support unit 32 to the trading support server 14. In addition, the data transmitted from the sales support server 14 is received, and the data is passed to the product purchase support unit 32.

  The product purchase support unit 32 provides a function of a product purchase support application, specifically, a user side application for using the face pass settlement service. The product purchase support unit 32 includes a user information registration unit 34, a purchase support screen display unit 36, a service information acquisition unit 38, a check-in notification unit 40, and a one-time code generation unit 42.

  The user information registration unit 34 registers attribute information related to a user necessary for using the face pass settlement in the trading support server 14. This attribute information includes a user ID, a user's name, a face photo, and credit card information necessary for credit card payment (for example, credit card type, card number, date of birth, expiration date, etc.). The user information registration unit 34 may cause the touch panel 20 to display a registration screen for allowing the user to input his / her attribute information.

  The purchase support screen display unit 36 causes the touch panel 20 to display a screen for the user in the face pass settlement service (hereinafter also referred to as “product purchase support screen”). The product purchase support screen includes (1) a login screen to the trading support server 14 as an initial screen, (2) a selection screen for a service provider (brand) that provides a face pass settlement service, and (3) a service provider A screen for selecting a store to be operated, (4) a store detail screen for displaying detailed information of the store, and (5) a check-in screen when checking in to the store are included. The purchase support screen display unit 36 displays these plural types of product purchase support screens by sequentially switching them according to the operation of the user.

  The service information acquisition unit 38 acquires information to be displayed on each of a plurality of types of product purchase support screens from the sales support server 14. For example, (2) Service provider or brand ID, name, logo, description, etc. are acquired as information for the service provider selection screen. Further, as information for (3) store selection screen and (4) store detail screen, the store ID, store name, business hours, address, etc. of each of the plurality of stores operated by the service provider are acquired. The service information acquisition unit 38 may periodically acquire the service provider information and the store information from the sales support server 14 and store them in a predetermined storage area. When the product purchase support screen is displayed, the service information acquisition unit 38 You may acquire from the support server 14. FIG.

  The operation detection unit 26 performs (4) a predetermined operation (hereinafter also referred to as “check-in operation”) indicating that the user checks in the store displaying the detailed information on the store detail screen. Detect that. In the present embodiment, “check-in” is positioned as a user's schedule for a visit to a specific store, in other words, a user's intention to visit a specific store that has not yet been confirmed. When a check-in operation is detected, the check-in notification unit 40 transmits check-in information indicating that to the trading support server 14. This check-in information includes a user ID, a service provider ID to be checked in, and a store ID.

  The one-time code generation unit 42 acquires a random number sequence transmitted from the trading support server 14 as a response to the check-in information notification. The one-time code generation unit 42 inputs a random number sequence acquired from the trading support server 14 to a predetermined confirmation code generation function, and generates a confirmation code based on the random number sequence. This confirmation code is verification information that is temporarily valid only for this check-in, and is a so-called one-time password. In the present embodiment, it is assumed that the confirmation code is a 4-digit numeric string (0000 to 9999). The purchase support screen display unit 36 displays the confirmation code generated by the one-time code generation unit 42 on the (5) check-in screen. The purchaser terminal 10 may notify the user of the confirmation code by a method other than the screen display. For example, the purchaser terminal 10 may output the confirmation code by voice.

  FIG. 3 is a block diagram showing a functional configuration of the store terminal 12 of FIG. The store terminal 12 includes a touch panel 50, a check-in information holding unit 54, and a control unit 56. The control unit 56 includes an operation detection unit 58, a display control unit 60, a communication processing unit 62, and a product sales support unit 64.

  As described above, program modules corresponding to each functional block in the control unit 56 are stored in a storage such as a flash memory of the store terminal 12, and the CPU of the store terminal 12 reads these program modules into the main memory. By executing the function, the function of the control unit 56 may be realized. The control unit 56 may store various data in a storage device such as a storage or a main memory, and execute data processing related to each functional block with reference to the data. Further, application software corresponding to the merchandise sales support unit 64 may be distributed in a recording medium or a download format and installed in the store terminal 12. Further, the function of the check-in information holding unit 54 may be realized by a storage device such as a storage of the store terminal 12 or a main memory.

  The functions of the touch panel 50, the operation detection unit 58, the display control unit 60, and the communication processing unit 62 are the same as the functions of the touch panel 20, the operation detection unit 26, the display control unit 28, and the communication processing unit 30 of the purchaser terminal 10. Description is omitted.

  The check-in information holding unit 54 holds attribute information (hereinafter also referred to as “store check-in information”) regarding a user who has checked in to the own store, that is, a user who plans to visit the own store. FIG. 4 shows the structure of store check-in information. The store check-in information includes the user ID, name, face photo image, and credit card information (part). This credit card information is obtained by limiting the user's credit card information registered in the trading support server 14 to a range that can be disclosed to the store salesperson, and may be, for example, the type and expiration date of the credit card. .

  Returning to FIG. 3, the merchandise sales support unit 64 provides a function of a merchandise sales support application, specifically, a store-side application for using the face pass settlement service. The product sales support unit 64 includes a sales support screen display unit 66, a product information acquisition unit 68, a check-in information update unit 70, a one-time code acquisition unit 72, a settlement request notification unit 74, and a result acquisition unit 76. Including.

  The sales support screen display unit 66 displays a screen for a store in the face pass settlement service (hereinafter also referred to as “product sales support screen”) on the touch panel 50. The product sales support screen includes (1) a menu selection screen (accounting menu, management menu, etc.) as an initial screen, (2) a product selection screen for selecting a user's purchased product, and (3) a payment method. (4) a face pass settlement screen for performing face pass settlement, and (5) a settlement result screen showing the result of settlement. The sales support screen display unit 66 displays the plurality of types of product sales support screens by sequentially switching them according to the operation of the store salesperson.

  The product information acquisition unit 68 acquires product information to be displayed on the (2) product selection screen of the product sales support screen from the sales support server 14. This product information includes the product name, product image, and sales price. The product information acquisition unit 68 may periodically acquire product information from the sales support server 14 and store it in a predetermined storage area, or may acquire it from the sales support server 14 when the product selection screen is displayed. Good.

  The check-in information update unit 70 acquires store check-in information (FIG. 4) that is attribute information related to the user who checked in to the store from the trading support server 14 and stores it in the check-in information holding unit 54. . In the present embodiment, the buying and selling support server 14 provides store check-in information to the store terminal 12 by a known push notification mechanism. The check-in information update unit 70 may acquire the store check-in information notified by push from the trading support server 14 via a mediation server (not shown).

  The one-time code acquisition unit 72 acquires a confirmation code notified in advance to the user. In the present embodiment, the store salesperson who has received the verification code verbal declaration by the user acquires the confirmation code input to the (4) face pass settlement screen of the product sales support screen. The settlement request notifying unit 74 displays the ID, service provider ID, store ID, settlement amount, payment conditions, one-time of the user whose face photograph is selected when the store salesperson performs the face pass settlement execution operation. The settlement request including the confirmation code acquired by the code acquisition unit 72 is transmitted to the trading support server 14. As will be described later, by confirming the confirmation code in the settlement request to the trading support server 14, the trading support server 14 confirms whether or not the confirmation code reported by the user matches the confirmation code expected by the trading support server 14 side. The validity of the confirmation code reported by the user is determined.

  The result acquisition unit 76 acquires the settlement result information provided from the trading support server 14 as a response to the settlement request. The sales support screen display unit 66 displays the settlement result information provided from the trading support server 14 on the (5) settlement result screen of the product sales support screen. The check-in information update unit 70 is a user who has made a payment from the check-in information holding unit 54, typically when the result acquisition unit 76 accepts the payment result, and typically when the payment for the product price is completed. Delete the record. The store salesperson is in a position to know the declaration code after receiving a confirmation code from the user when purchasing the product. By deleting the check-in information for the store for which the settlement process after check-in is completed, the store salesperson can be prevented from being fraudulent.

  FIG. 5 is a block diagram showing a configuration of the trading support server 14 of FIG. The trading support server 14 includes a service information holding unit 110, a user information holding unit 111, a store information holding unit 112, and a control unit 114. The control unit 114 includes a user information recording unit 116, a product information recording unit 118, a check-in reception unit 120, a random number acquisition unit 122, a random number provision unit 124, a check-in information provision unit 126, and a settlement request reception. A unit 128, a settlement permission / rejection determination unit 130, a settlement processing unit 132, and a result notification unit 134.

  As described above, program modules corresponding to the respective functional blocks in the control unit 114 are stored in a storage such as a hard disk of the trading support server 14, and the CPU of the trading support server 14 appropriately transfers these program modules to the main memory. The function of the control unit 114 may be realized by reading and executing. The control unit 114 may store various data in a storage device such as a storage or a main memory, and execute data processing related to each functional block with reference to the data. Further, the functions of the service information holding unit 110, the user information holding unit 111, and the store information holding unit 112 may be realized by a storage device such as a storage of the trading support server 14 or a main memory.

  The service information holding unit 110 is a storage area that holds, as service information, information related to a service provider that provides a face pass settlement service and information about a store operated by the service provider. This service information is also information to be displayed on the product purchase support screen of the purchaser terminal 10 and is set in advance by the administrator of the product trading system 100.

  The user information holding unit 111 includes user information in the face pass payment service (hereinafter also referred to as “user registration information”), and information on the user's check-in (hereinafter referred to as “user check-in information”). It is also a storage area that holds “. FIG. 6A shows the configuration of user registration information. The user registration information includes the user ID registered by the purchaser terminal 10, name, face photo image, and all credit card information necessary for settlement. FIG. 6B shows the structure of user check-in information. The user check-in information includes a user ID notified from the purchaser terminal 10, a service provider ID to be checked in, a store ID, a random number sequence to be described later, and a face pass expiration date.

  Returning to FIG. 5, the store information holding unit 112 holds information related to individual stores (hereinafter also referred to as “store individual information”). The store individual information includes a service provider ID, a store ID, store terminal information, and product information. The store terminal information includes information of the store terminal 12 necessary for push notification of check-in information. For example, it may be the IP address of the store terminal 12 or an individual identification number (UID). The product information includes the name, image, and sales price of the product sold at the store.

  Although not shown in FIG. 5, the trading support server 14 provides service information held in the service information holding unit 110 to the purchaser terminal 10 periodically or in response to a request from the purchaser terminal 10. You may further provide a provision part. The sales support server 14 may further include a product information providing unit that provides the product information held in the store information holding unit 112 to the store terminal 12 periodically or in response to a request from the store terminal 12.

  The user information recording unit 116 stores the user attribute information registered from the purchaser terminal 10 in the user information holding unit 111 as user registration information (FIG. 6A). The merchandise information recording unit 118 accepts merchandise information registered from a service provider or a store information terminal (for example, the store terminal 12), and updates the merchandise information in the store information holding unit 112.

  The check-in reception unit 120 receives the check-in information notified from the purchaser terminal 10 and stores it in the user information holding unit 111 as user check-in information (FIG. 6B). At that time, the check-in reception unit 120 sets the date and time when the predetermined time has elapsed from the reception date and time of the check-in information (for example, the date and time after one hour) as the face pass expiration date in the user check-in information.

  The random number acquisition unit 122 acquires a random number sequence generated by a predetermined random number generator when the check-in information is received. The value of this random number sequence does not have to be a mathematically generated random number, but may be a pseudo random number generated by a hardware random number, a software random number, or the like. The random number acquisition unit 122 sets the acquired random number sequence data in the user check-in information of the user information holding unit 111. The random number providing unit 124 transmits the random number sequence data acquired by the random number acquiring unit 122 to the purchaser terminal 10 as a response to the notification of the check-in information.

  When the check-in information is received, the check-in information providing unit 126 provides the store terminal 12 with the ID of the user who performed the check-in as a key from the user registration information of the user information holding unit 111. The check-in information for the store (FIG. 4) to be extracted is extracted. The check-in information providing unit 126 transmits the set store check-in information to the store terminal 12 by a known push notification method.

  The settlement request accepting unit 128 accepts a settlement request transmitted from the store terminal 12. The settlement approval / disapproval determination unit 130 refers to the user check-in information in the user information holding unit 111, and the random number sequence and face associated with the user ID, service provider ID, and store ID specified in the settlement request. Identify the pass expiration date. If the settlement request acceptance date and time (typically current date and time) has passed the face pass expiration date, the settlement permission determination unit 130 refuses to execute the settlement.

  If the settlement request acceptance date / time is within the face pass validity period, the settlement permission / rejection determination unit 130 divides the confirmation code specified in the settlement request (referred to herein as the “first code”) and the specified random number sequence. Judgment is made on the basis of settlement. Specifically, a random number sequence is input to the same function as the confirmation code generation function used in the purchaser terminal 10, and a confirmation code based on this random number sequence (referred to herein as a “second code”) is generated. Then, the first code and the second code are collated, and if they match, the execution of the settlement is permitted as having received the valid confirmation code, and if they are different, the execution of the settlement is rejected.

  The settlement processing unit 132 executes the settlement process when the settlement permission determination unit 130 permits the settlement. Specifically, the credit card information held in the user registration information of the user information holding unit 111 and the payment instruction data specifying the payment amount and payment conditions (number of payments, etc.) specified in the payment request are sent to the payment server. 16 to send. The payment processing unit 132 acquires information indicating the success or failure of the credit card payment by the payment server 16 from the payment server 16.

  The result notification unit 134 transmits, to the store terminal 12 as payment result information, information indicating whether or not the payment is permitted and the payment process is successful. For example, if the face pass has expired, it is information that the payment is rejected because the face pass has expired, and information for prompting the user to perform a new check-in operation is provided to the store terminal 12 as payment result information To do. If the confirmation code reported by the user is invalid (that is, does not match the second code), information indicating that the confirmation code is invalid is provided to the store terminal 12 as settlement result information. As a modification, the result notification unit 134 may include information including the name of the store where the payment has failed, and may transmit information for prompting the user to perform a new check-in operation to the purchaser terminal 10.

The operation of the commodity trading system 100 having the above configuration will be described below.
Before using the face pass settlement service, the user registers necessary information for face pass settlement in the trading support server 14. This necessary information includes a user ID, a user name, a face photo, and credit card information (for example, credit card type, card number, date of birth, expiration date, etc.) necessary for credit card payment. The user information recording unit 116 of the trading support server 14 stores the user registration information in the user information holding unit 111. In addition, the service provider registers the product information to be sold at the store in the sales support server 14, and the product information recording unit 118 of the sales support server 14 stores the product information in the store information holding unit 112.

  When the user thinks of stopping at a store (for example, while going out), the product purchase support application is activated on the purchaser terminal 10. The service information acquisition unit 38 of the purchaser terminal 10 acquires data to be displayed on the product purchase support screen from the sales support server 14. The purchase support screen display unit 36 of the purchaser terminal 10 sequentially displays a login screen, a service provider selection screen, and a store selection screen as the product purchase support screen, and then displays detailed information on the store selected on the store selection screen. The store detail screen shown is displayed. FIG. 7 shows a store detail screen. The store detail screen 140 includes a face pass settlement selection field 142. When face pass payment is desired, the user inputs a predetermined check-in operation (for example, a tap operation or a flick operation in a predetermined direction) to the face pass payment selection field 142. This check-in operation indicates that the user has an intention to visit the store at a future time point, and the user information is notified to the store to be visited as will be described later.

  When a check-in operation is detected on the store detail screen 140, the check-in notification unit 40 of the purchaser terminal 10 transmits check-in information to the trading support server 14. The check-in reception unit 120 of the trading support server 14 stores the received check-in information in the user information holding unit 111 as user check-in information. The random number acquisition unit 122 of the trading support server 14 acquires a newly generated random number sequence when the check-in reception unit 120 receives the check-in information, and records it in the user check-in information. The random number providing unit 124 of the trading support server 14 transmits the data of the random number sequence to the purchaser terminal 10.

  When the random number sequence is received as a response of the trading support server 14 to the check-in information notification, the one-time code generation unit 42 of the purchaser terminal 10 newly generates a confirmation code according to the random number sequence provided from the trading support server 14. . Then, the sales support screen display unit 66 displays a check-in screen indicating that the check-in to the store has been accepted. FIG. 8 shows a check-in screen. The check-in screen 150 includes a user information area 152 that displays information related to the user who has checked in. In the user information area 152, the user's photo image 154, name 156, and confirmation code 158 generated by the one-time code generation unit 42 are displayed. The user confirms (for example, stores) the confirmation code 158 displayed on the check-in screen 150 and visits the store.

  The check-in information providing unit 126 of the trading support server 14 extracts the check-in information for the store from the user registration information stored in the user information holding unit 111 when the check-in receiving unit 120 receives the check-in information. The store check-in information is transmitted to the store terminal 12. The check-in information update unit 70 of the store terminal 12 acquires the store check-in information provided from the trading support server 14 and stores it in the check-in information holding unit 54.

  When a user visits a store that has been checked in in advance, decides a product desired to be purchased and speaks to the store salesperson, the store salesperson operates the store terminal 12 to select a menu screen for the product sales support application Select the accounting menu with. The product information acquisition unit 68 of the store terminal 12 acquires the product information sold at the store from the sales support server 14, and the sales support screen display unit 66 of the store terminal 12 displays a product selection screen in which the product information is arranged.

  FIG. 9 shows a product selection screen. The product name and product image are arranged in the product selection area 162 of the product selection screen 160. In the detail area 164, the product name and the sales price selected by the store sales person in the product selection area 162 are displayed. The detail area 164 includes a check-in status field 166. The sales support screen display unit 66 sets the number of users currently checked in at the own store in the check-in status field 166, for example, sets the number of records in the check-in information holding unit 54 in the check-in status field 166.

  The sales support screen display unit 66 also receives new store check-in information from the trading support server 14 while the product selection screen 160 is displayed (when a new record is inserted into the check-in information holding unit 54). ), The pop-up 168 temporarily displays the user name and face photo image indicated by the check-in information for the store. That is, when there is a check-in to the store, the information of the user who performed the check-in is displayed in a pop-up on the product selection screen 160. When selection of the product to be purchased is completed and the store sales person presses the accounting button 170, the sales support screen display unit 66 displays the accounting screen next.

  FIG. 10 shows an accounting screen. The accounting screen 180 can also be said to be a screen for selecting a payment method. The accounting screen 180 includes a cash settlement designation area 182, a face pass settlement designation area 184, and a card settlement designation area 188. The cash settlement designation area 182 is an area for inputting a payment amount in the case of cash settlement. The face pass settlement designation area 184 is an area for selecting a face photograph 186 of a purchaser (that is, a user who is going to purchase a product at a store) in the case of face pass settlement. The card payment designation area 188 is an area selected in the case of credit card payment by reading a credit card held by the user.

  In this embodiment, face pass settlement is selected. The user declares his / her name (here “Hanako Nomura”) to the store salesperson. The store salesperson checks each item (combination of name and face photo) of a plurality of checked-in users displayed in the face pass settlement designation area 184. The store salesperson looks at the appearance of the user and confirms that it matches the face photo 186 of “Hanako Nomura” displayed in the face pass payment designation area 184, and then the face photo 186 of “Hanako Nomura” is displayed. A selection operation (for example, a tap operation) is input. Next, the sales support screen display unit 66 displays a face pass settlement screen.

  FIG. 11 shows a face pass settlement screen. On the face pass settlement screen 190, a face photograph 192 and name 194 of the user selected on the accounting screen 180, a confirmation code input field 196, and a decision button 198 are displayed. Here, the user declares the confirmation code confirmed at the time of check-in to the store salesperson. The store sales person inputs the reported confirmation code into the confirmation code input field 196. Note that payment conditions (such as the number of payments) can be changed on the face pass settlement screen 190. When the store salesperson confirms that the user's appearance matches the face photograph 192, and the name declared by the user matches the name 194, and the confirmation code input field 196 completes the input of the confirmation code, The store sales clerk inputs a selection operation to the decision button 198 to execute a settlement process.

  When the selection operation of the determination button 198 is detected on the face pass settlement screen 190, the one-time code acquisition unit 72 of the store terminal 12 confirms the confirmation code (herein referred to as “declaration code”) entered in the confirmation code input field 196. .) The settlement request notifying unit 74 of the store terminal 12 transmits a settlement request including a declaration code to the buying and selling support server 14. When the settlement request receiving unit 128 of the trading support server 14 receives the settlement request, the settlement permission determination unit 130 of the trading support server 14 specifies the user check-in information by the user ID specified in the settlement request. Then, a confirmation code (in this case, a “collation code”, which is newly generated upon receipt of a payment request in accordance with a random number sequence of the user check-in information when the face pass expiration date of the user check-in information has not passed. ) And the return code specified in the settlement request are permitted, the credit card settlement of the product price is permitted.

  When the credit card settlement is permitted by the settlement permission determination unit 130, the settlement processing unit 132 transmits a settlement instruction to the settlement server 16, and executes a settlement process for the commodity price. The result notifying unit 134 transmits information indicating the result of the settlement process in the sales support server 14 and the settlement server 16 to the store terminal 12. The sales support screen display unit 66 of the store terminal 12 displays the result of the settlement process on the screen. The store sales person confirms the result of the settlement process, and if the content indicates that the settlement has been completed normally, the store sales person delivers the product to the user on the assumption that the sale of the product has been completed normally. If the transaction support server 14 or the settlement server 16 indicates that the settlement process is rejected or has failed, the store salesperson informs the user and prompts the user for a new check-in operation, for example.

  According to the product trading system 100 of the first embodiment, after a user checks in at a store and actually visits the store to purchase the product, the user pays for the product by declaring his name and confirmation code. Can be completed. In other words, a product can be purchased with a “face pass” without taking out a physical payment medium such as cash or a credit card at a store. As a result, convenience related to product purchase is enhanced. In addition, even when visiting a store for the first time or when the number of visits is small, it is possible to purchase products with simple procedures as if they were regular customers, making it easier for the user to have a sense of superiority and satisfaction.

  Further, according to the commodity trading system 100, a one-time confirmation code is presented to the user at the time of check-in to the store. Then, on the condition that the confirmation code declared by the user at the time of product purchase matches the confirmation code generated on the buying and selling support server 14 side at the time of product purchase, the person who checked in tries to purchase the product at the store. It is determined that the person is the same, and the face pass settlement is permitted. In this way, in addition to the store salesperson visually confirming the purchaser's appearance and facial photograph, the use of the verification code collation processing by the buying and selling support server 14 together makes it possible to make an illegal settlement. It can be effectively suppressed.

  For example, even when a malicious third party impersonates another user, it is difficult for the third party to know the confirmation code, so that illegal acts on the user side can be effectively prevented. In addition, if a store salesperson misidentifies or misoperates a purchaser, for example, if the selection of a face photo is wrong, an inconsistency in the confirmation code is detected, preventing incorrect payments. it can. Further, since the store salesperson cannot know the confirmation code until the user declares it, fraudulent acts by the store salesperson can be effectively prevented. For example, it is possible to prevent unauthorized payment of a product that is not actually purchased by specifying a facial photograph of a user who does not visit the store.

  Further, according to the merchandise trading system 100, after the check-in by the user, the face pass settlement is permitted on the further condition that the settlement request is made within a predetermined valid period (that is, while the face pass validity period has not passed). . As time elapses after the confirmation code is presented to the user, the possibility that the confirmation code is leaked to a third party increases. In the present embodiment, by providing the face pass expiration date, it is possible to suppress a decrease in the accuracy of checking the identity between the person who checked in and the person who intends to purchase the product at the store.

  The first embodiment has been described above. This embodiment is an exemplification, and it will be understood by those skilled in the art that various modifications can be made to combinations of the respective constituent elements and processing processes, and such modifications are also within the scope of the present invention. is there. A modification is shown below.

A first modification example of the first embodiment will be described.
In the above embodiment, the buying and selling support server 14 holds the random number sequence as the generation data of the confirmation code, not the confirmation code itself as the user check-in information. As a modification, at the time of a check-in operation by the user, the random number acquisition unit 122 of the trading support server 14 generates a confirmation code based on the random number sequence, and the trading support server 14 uses the confirmation code as user check-in information. It may be held. In addition, a confirmation code may be provided instead of providing a random number sequence from the trading support server 14 to the purchaser terminal 10. In the above embodiment, the buying and selling support server 14 transmits the random number sequence to the purchaser terminal 10 when the user performs a check-in operation. As a modification, the purchaser terminal 10 may generate a random number sequence and include it in the check-in information and transmit it to the trading support server 14. Further, the purchaser terminal 10 may generate a confirmation code based on the random number sequence and transmit the confirmation code to the trading support server 14. Thus, the “first collation information” and the “second collation information” described in the claims may have the same content.

A second modification of the first embodiment will be described.
In the above embodiment, the confirmation code notified to the user is a 4-digit number string. As a modification, the confirmation code may be data in a form other than a numeric string, and may be, for example, a barcode or a QR code (registered trademark). In this case, the user presents the purchaser terminal 10 displaying the confirmation code at the store, and the one-time code acquisition unit 72 of the store terminal 12 passes through a predetermined reader such as a barcode reader or a QR code reader. The content of the confirmation code may be acquired.

A third modification of the first embodiment will be described.
The purchaser terminal 10 may have an automatic check-in function. In this modification, the buying and selling support server 14 holds position information (for example, latitude / longitude values) indicating the position of the store on the map. The service information acquisition unit 38 of the purchaser terminal 10 further acquires store location information from the trading support server 14. The purchaser terminal 10 further includes a GPS device and a position determination unit. The GPS device receives GPS positioning information from a GPS satellite, and outputs information (for example, latitude / longitude values) indicating the current position of the purchaser terminal 10 from the received information.

  The position determination unit determines whether or not the purchaser terminal 10 exists in the vicinity of a store designated in advance by the user (hereinafter also referred to as “designated store”). Specifically, when the current position of the purchaser terminal 10 output by the GPS device is included within a predetermined range (for example, a radius of 100 meters) from the location of the designated store, the purchaser terminal 10 is located near the designated store. It is determined that it exists. When it is determined that the purchaser terminal 10 exists in the vicinity of the designated store, the check-in notification unit 40 automatically transmits check-in information designating the designated store to the trading support server 14. The purchase support screen display unit 36 may display the confirmation code generated in the automatic check-in on the automatic check-in screen similar to the check-in screen 150 in FIG.

The 4th modification about 1st Embodiment is demonstrated.
The purchaser terminal 10 and the store terminal 12 may be implemented as a thin client. For example, the purchaser terminal 10 obtains input data to the touch panel 20 via the operation detection unit 26 and displays the screen data obtained from the trading support server 14 on the touch panel 20 via the display control unit 28. It may be the composition provided only with. Similarly, the store terminal 12 acquires input data to the touch panel 50 via the operation detection unit 58 and displays the screen data acquired from the trading support server 14 on the touch panel 50 via the display control unit 60. It may be the composition provided only with. The screen display units of the purchaser terminal 10 and the store terminal 12 may be realized by a web browser.

  In this modification, the buying and selling support server 14 collectively executes data processing for realizing functions corresponding to the product purchase support unit 32 in FIG. 2 and the product sales support unit 64 in FIG. Further, the buying and selling support server 14 may have a function of a web server and may provide screen data indicating a result of data processing to the purchaser terminal 10 and the store terminal 12 as structured documents (HTML, XML, etc.).

A fifth modification of the first embodiment will be described.
The trading support server 14 may further include a confirmation code lockout function. In this modification, the buying and selling support server 14 receives a payment request for designating the same user ID, service provider ID, and store ID a plurality of times. A confirmation code (second code) based on a random number sequence specified by a combination of the confirmation code (first code) specified in each settlement request and the above-described user ID, service provider ID, and store ID is provided. When the number of mismatches reaches a predetermined threshold value (three times in this case), the random number sequence specified by the combination of the user ID, the service provider ID, and the store ID is invalidated. In other words, the confirmation code provided to the user by the prior user check-in is invalid.

  For example, the user check-in information in the user information holding unit 111 may further include a verification failure frequency column (initial value: 0) and an invalid flag column (initial value: off). When the first code and the second code are inconsistent, the payment permission determination unit 130 checks the user check-in specified by the combination of the user ID, the service provider ID, and the store ID specified in the payment request. For information, the number of matching failures is incremented. When the number of collation failures reaches 3, the user check-in information invalid flag is set to ON. The settlement permission / rejection determination unit 130 first confirms the invalid flag of the user check-in information based on the combination of the user ID, the service provider ID, and the store ID specified in the settlement request. If the invalid flag is on, the verification code verification process is skipped, that is, the settlement is rejected regardless of whether the first code and the second code match. The result notification unit 134 is information indicating that the confirmation code has been invalidated, and provides the store terminal 12 or the purchaser terminal 10 with information for prompting the user to perform a new check-in operation. When a new check-in is performed, a new random number sequence (confirmation code) is generated and new user check-in information is generated.

  In this modified example, when the number of verification code verification failures reaches a predetermined number, electronic settlement using the verification code issued at the time of check-in by the user is rejected. This makes it easy to prevent spoofing of a user by a malicious third party and execution of unauthorized payment due to an unauthorized payment request on the store side.

  Next, in relation to the above modification, a further modification for suppressing impersonation of a malicious third party to a user and an illegal settlement request on the store side will be described. The trading support server 14 may further include a check-in determination unit that rejects check-in when a predetermined condition is satisfied. The check-in determination unit may temporarily stop the use of the face pass settlement when the check-in is repeated a predetermined number of times or more on the same day as the first fraud prevention process. The check-in determination unit may temporarily stop the face pass settlement by the terminal when the re-check-in is repeated from the same terminal as the second fraud prevention process.

  The first fraud prevention process of the check-in determination unit will be described in detail. The user information holding unit 111 further holds a check-in history associated with the number of check-ins (initial value: 0) using the date of the day, the user ID, the service provider ID, and the store ID as keys. The number of check-ins records the number of check-ins to the same store by the same user on a specific date. When the check-in reception unit 120 receives check-in information, the check-in reception unit 120 checks if the history corresponding to the user ID, the service provider ID, and the store ID specified in the check-in information has not been recorded. A new check-in history indicating the number of ins “1” is newly recorded, and if recorded, the number of check-ins is incremented.

  When the check-in reception unit 120 receives the check-in information, the check-in determination unit specifies the check-in history corresponding to the date of the day, the user ID specified by the check-in information, the service provider ID, and the store ID. If the number of check-ins is 5 or less, check-in is permitted. Thereafter, the process of providing the random number sequence and the store check-in information is continued. On the other hand, if the number of check-ins is 6 or more, the check-in determination unit rejects the check-in. In this case, the check-in determination unit rejects the check-in from the user whose check-in count exceeds the specified count until a predetermined operation by the user, for example, a predetermined identity verification operation, is performed, and a confirmation code The face pass settlement is temporarily stopped by skipping the issuance process.

  The second fraud prevention process of the check-in determination unit will be described in detail. The user information holding unit 111 holds a check-in history obtained by adding a terminal ID to the check-in history of the first configuration. The check-in information from the purchaser terminal 10 further includes a terminal ID (for example, an individual identification number) of the purchaser terminal 10. The check-in reception unit 120 increments the number of check-ins using the terminal ID, user ID, service provider ID, and store ID specified by the check-in information as keys.

  When the check-in receiving unit 120 receives check-in information, the check-in determining unit checks the check-in corresponding to the date of the day, the terminal ID, the user ID, the service provider ID, and the store ID specified by the check-in information. A history is specified, and check-in is permitted when the number of check-ins is 5 or less. On the other hand, if the number of check-ins is 6 or more, the check-in is rejected. In this case, the check-in determination unit rejects check-in from the purchaser terminal 10 in which the number of check-ins exceeds the specified number of times until a predetermined operation by the user, for example, a predetermined identity verification operation is performed, By skipping the verification code issuing process, the face pass settlement is temporarily stopped. Each of the first fraud prevention process and the second fraud prevention process is not limited to the fifth modification example, and may be combined with the structure of the embodiment and the structure of another modification example.

A sixth modification of the first embodiment will be described.
The trading support server 14 may further include a function for eliminating duplication of confirmation codes issued to users. As described above, the user check-in information of the user information holding unit 111 stores a random number sequence in association with the user ID. In this modified example, the check-in date and time is further stored. Specifically, the check-in reception unit 120 records the user check-in information at the current date and time, in other words, from the purchaser terminal 10. The date information when the information is received is further recorded. The random number acquisition unit 122 suppresses issuing the same confirmation code as the confirmation code issued to the same person on the same day with the user and the confirmation code as a set. By assuring the uniqueness of the confirmation code, the confidentiality of the confirmation code is enhanced, and it becomes easy to prevent fraudulent acts by malicious third parties and stores.

  Specifically, when the random number acquisition unit 122 acquires a random number sequence from the random number generator, the combination of the acquired random number sequence and the user ID specified by the check-in information is associated with the current date. Check if the existing user check-in information has been set. If the existing user check-in information is not set, that is, if the combination of the acquired random number sequence and the user ID is unique, the random number acquisition unit 122 executes the subsequent processing using the acquired random number sequence. On the other hand, if the combination of the acquired random number sequence and the user ID is already set in the existing user check-in information, that is, if the acquired random number sequence is the same value as the random number sequence issued to the user The random number acquisition unit 122 acquires the random number sequence from the random number generator again, and executes the comparison process with the existing user check-in information again.

  Note that the random number acquisition unit 122 may exclude, from the comparison target, existing user check-in information associated with the current date whose face pass expiration date has expired. In other words, only existing user check-in information that is associated with the current date and whose face pass expiration date has not elapsed may be extracted as a comparison target. Further, as already described in the first modification, when the trading support server 14 generates a confirmation code based on the random number sequence, the confirmation code may be stored in the user check-in information. In this case, the random number acquisition unit 122 may execute a comparison process between the generated confirmation code and the existing user check-in information.

  Although related to the fifth modified example, also in the sixth modified example, when the check-in information is received, the buying and selling support server 14 checks to reject check-in when a predetermined condition is satisfied. An in determination unit may be further provided. The random number acquisition unit 122 may execute the random number sequence acquisition / comparison process on condition that the check-in determination unit permits (does not reject) check-in in both of the following two determination processes. Good. As a first determination process, the check-in determination unit determines whether a user who performs check-in does not exceed a specified distance within a specified time, and as a second determination process, one user is in a short period of time. Determine if you have a large number of check-ins.

  The first determination process of the check-in determination unit will be described in detail. Although related to the third modification, the trading support server 14 holds position information (for example, latitude / longitude values) indicating the position of the store on the map. The check-in determination unit recognizes the check-in date and time of the check-in information received this time (hereinafter also referred to as “the check-in information”) and the store position specified by the store ID. Further, the check-in date and time of the existing user check-in information associated with the user ID specified by the check-in information (hereinafter also referred to as “existing check-in information”) and the store ID are specified. Recognize store location.

  The check-in determination unit checks the distance between the allowed stores (the magnitude of the divergence of each store position) between the target store in the check-in information and the target store in the existing check-in information by checking the check-in information. It is determined according to the difference between the in date and time and the check in date and time of the existing check in information. Typically, the larger the difference between the check dates, the greater the allowed inter-store distance, and the two are determined to have a positive correlation. For example, if the difference in check-in date is 1 hour, the allowable inter-store distance is determined as 60 kilometers, and if the difference in check-in date is 2 hours, the allowable inter-store distance is determined as 120 kilometers. Also good.

  The check-in determination unit calculates the inter-store distance from the position information of each of the target stores in the check-in information and the target stores in the existing check-in information. When the calculated inter-store distance is larger than the allowable inter-store distance, the check-in determination unit rejects check-in. For example, if the same user performs a check-in operation on the store A in Shibuya at 10:00 and then performs a check-in operation on the store B in Hakata at 10:40, the check-in determination unit performs the latter check-in. I refuse. According to the first determination process, when a check-in that is actually difficult to visit is accepted, the face-pass settlement preparation process that is assumed to be wasted is suppressed, and the number of check-in information to be managed is reduced. This can reduce the waste of system resources of the trading support server 14. In addition, it is possible to suppress notification of a substantially meaningless check-in to the store side.

  The second determination process of the check-in determination unit will be described in detail. The check-in determination unit refers to the existing user check-in information associated with the user ID specified by the check-in information. Then, when there are a predetermined number or more (for example, 20 or more) of user check-in information recorded within a predetermined time (for example, the latest 5 minutes), it is determined that a large amount of check-in has been performed and the check-in is rejected. .

  The user information holding unit 111 holds a history of check-in time and check-off time using the user ID, service provider ID, and store ID as keys. Each time the check-in reception unit 120 receives check-in information, the check-in reception unit 120 sequentially records the check-in information reception date and time in the check-in time history as the check-in time. In addition, every time check-in information is received, the check-in reception unit 120 sequentially records the reception date and time of the check-off information as the check-off time in the check-off time history. The check-off information is information requesting cancellation of check-in. Upon receiving the check-off information, the trading support server 14 may delete the corresponding user check-in information, or may send a request for canceling the store check-in information to the store terminal 12.

  The check-in determination unit refers to the history of check-in time and check-off time using the user ID, service provider ID, and store ID specified in the check-in information as keys. When it is detected that the check-in and check-off are repeated a predetermined number of times or more for the same store, it is determined that a large amount of check-in has been performed and the check-in is rejected.

  Once the check-in is rejected in the second determination process, the check-in determination unit continues until a predetermined check-in permission condition is satisfied, and checks with the check-in information in which the user ID to be rejected is specified. Reject in. The check-in permission condition may be, for example, that 30 minutes have passed since the last check-in, or that 30 minutes have elapsed since the check-in rejection was determined. According to the second determination process, it is possible to prevent the number of check-ins that cannot be actually visited on the day or a large number of check-ins in a short time, prevent the system resources of the trading support server 14 from being wasted, and to prevent DoS attacks. Resistance can be improved. Each of the first determination process and the second determination process is not limited to the sixth modified example, and may be combined with the configuration of the embodiment and the configuration of another modified example.

A seventh modification of the first embodiment will be described.
The trading support server 14 issues coupons that can be used in the store, such as discount coupons and vouchers, to a user who uses face pass settlement for the first time at a specific store (hereinafter also referred to as “first customer”). May be. In this modification, the buying and selling support server 14 accepts registration of coupon information that each store provides to the first customer. The user information holding unit 111 of the buying and selling support server 14 further holds a check-in history that associates the user, the store, and the number of check-ins. When the check-in reception unit 120 of the trading support server 14 receives the check-in information, the check-in reception unit 120 increments the number of check-ins in the check-in history corresponding to the user ID and the store ID.

  The sales support server 14 further includes a coupon providing unit. When the check-in receiving unit 120 receives the check-in information, the coupon providing unit checks the number of check-ins in the check-in history corresponding to the user ID and the store ID. When the number of check-ins is “1” (that is, the first customer), the coupon providing unit provides information on coupons provided by the check-in target store to the purchaser terminal 10 in accordance with the provision of the random number sequence. Thereby, coupon information is displayed on the check-in screen 150 (FIG. 8) of the purchaser terminal 10, for example, and the user's willingness to purchase is increased. Moreover, a coupon provision part provides the information of the coupon provided to the first time customer to the store terminal 12 according to provision of the check-in information for stores to the check-in target store. Thereby, coupon information can be displayed on the face pass settlement screen 190 of the store terminal 12, for example, and the store salesperson can be notified that the customer is a coupon application target customer.

An eighth modification of the first embodiment will be described.
The user may register a plurality of credit card information of different card types in the trading support server 14 as his / her attribute information. In this case, the sales support server 14 provides a plurality of credit card information to the store terminal 12 as store check-in information, and the sales support screen display unit 66 of the store terminal 12 displays the face pass settlement screen 190 in FIG. A plurality of credit card information associated with the purchaser may be displayed in a list so as to be selectable / switchable. The store sales person accepts the type of credit card to be used in the settlement based on the oral declaration from the purchaser, and selects the credit card from the list.

  Next, a description will be given of a configuration in which when a user has already registered a plurality of pieces of credit card information, which credit card is used is automatically determined as to which the merit is great, and a card having a large merit is displayed by default.

  When the specific facial photograph 186 is selected on the accounting screen 180 of FIG. 10, the store terminal 12 displays the user ID corresponding to the selected facial photograph 186, the purchase target product, and the payment amount as the service provider ID. And a customer information notification unit that notifies the sales support server 14 together with the store ID. The trading support server 14 further includes a reward information holding unit and a reward determination unit. The reward information holding unit holds information of a reward program determined for each credit card, for example, the type of reward (electronic point provision, cashback, coupon provision, etc.) and the provision condition of the reward.

  The reward determination unit refers to the service information holding unit 110 and identifies the service provider name and the store name corresponding to the service provider ID and the store ID notified from the store terminal 12. In addition, referring to the user registration information in the user information holding unit 111, a plurality of credit card information associated with the user ID notified from the store terminal 12 is specified. In addition, the reward provision condition of each credit card is specified with reference to the reward information holding unit.

  The reward determination unit compares the reward provision condition with the service provider name, the store name, the purchase target product, and the payment amount for each credit card, and identifies the content of the reward satisfying the provision condition. Then, according to a predetermined evaluation function, the size of the reward for each credit card, in other words, the size of the merit for the purchaser is determined. For example, if the reward is provision of electronic points or cashback, it may be determined that the reward is larger as the provision amount is larger. If a discount coupon is provided, it may be determined that the reward is larger as the discount amount is larger. The reward determination unit provides the store terminal 12 with reward information indicating the size of the reward for each credit card held by the purchaser.

  When the sales support screen display unit 66 of the store terminal 12 displays a list of a plurality of credit card information on the face pass settlement screen 190 in FIG. 11, the reward is the largest in the reward information notified from the trading support server 14. The credit card is displayed in a mode as a default card used for settlement. For example, the face pass settlement screen 190 may be displayed in a selected state during initial display, or may be displayed in the payment condition column of the face path settlement screen 190 as a default. Further, the sales support screen display unit 66 may display a list in which information on a plurality of credit cards is arranged in descending order of the reward size on the face pass settlement screen 190. In addition, the reward determination unit of the sales support server 14 may notify the store terminal 12 of the content of the reward, and the sales support screen display unit 66 of the store terminal 12 displays the content of the reward in a manner associated with each credit card. It may be displayed.

A ninth modification of the first embodiment will be described.
The period from the check-in date and time to the face pass expiration date (hereinafter also referred to as “face pass validity period”) may not be a fixed period, and the length of the period may be dynamically changed according to the positional relationship between the user and the store. It may be determined. While maintaining the face pass effective period, the convenience of the user can be further improved while maintaining the fraud prevention effect by flexibly adjusting the length.

  For example, the purchaser terminal 10 or the buying and selling support server 14 may further include an effective period determining unit that determines a face pass effective period at the time of a check-in operation. When the purchaser terminal 10 includes an effective period determination unit, the purchaser terminal 10 includes the determined face pass effective period in the check-in information and notifies the purchase support server 14, and the purchase support server 14 is notified. The face pass validity period based on the face pass validity period may be stored in the user check-in information. Further, when the sales support server 14 includes an effective period determination unit, the purchaser terminal 10 may notify the sales support server 14 by including the position information of the own terminal in the check-in information.

  The valid period determining unit determines that the face pass valid period is within a range where the upper limit is a predetermined period (for example, 12 hours) considering leakage risk, as the location of the check-in target store and the current position of the purchaser terminal 10 are further away May be lengthened. In addition, the time required for the user to move to the store may be estimated according to the location of the store to be checked in and the current position of the purchaser terminal 10. The period may be lengthened. Further, the result obtained by adding a predetermined time such as one hour to the required time for movement may be determined as the face pass effective period. In addition, in order to accurately estimate the time required for movement, the user may select a moving means such as walking, bicycle, or car, and the required moving speed may be required according to the average moving speed associated with the selected moving means in advance. The time may be estimated.

A tenth modification of the first embodiment will be described.
If the user is a regular customer at a specific store, specifically, if the user has experienced face pass payments at a specific store a predetermined number of times or more than a predetermined amount, the facial pass validity period at that store is not a regular customer It may be determined to be longer than the user's face pass valid period. This is because regular customers are accustomed to face pass payments, so the risk of leaking confirmation codes is expected to be relatively low, and because they are regular customers, it is also expected that fraudulent acts on the store side will be suppressed. . In this way, regular customers are treated specially, and it becomes easier for users who are regular customers to have a sense of superiority and satisfaction.

  Also in this modification, the purchaser terminal 10 or the buying and selling support server 14 further includes an effective period determining unit. Further, the purchaser terminal 10 or the buying and selling support server 14 further includes a payment history holding unit for holding a payment history in which the user is associated with the store where the user purchased the product by face pass payment, the number of purchases, and the payment amount. Prepare. When the purchaser terminal 10 includes a settlement history holding unit, the sales support server 14 may provide the settlement history to the purchaser terminal 10 every time face pass settlement is performed.

  When the user checks in to a specific store, the valid period determining unit refers to the payment history and specifies the number of face pass payments and / or the face pass payment amount of the user at the store. When the number of face pass settlements is a predetermined number (for example, 3 times) or more and / or the face pass settlement amount is a predetermined amount (for example, 10,000 yen) or more, the user is a regular customer at the check-in target store. Judge that there is. When it is determined that the validity period determination unit is not a regular customer, the face pass validity period is determined by a normal method as described in the above embodiment or the ninth modification, while when it is determined as a regular customer, A period longer than the face pass effective period determined by the normal method is determined as the face pass effective period to be given to the regular customer. For example, it may be a period obtained by adding a predetermined time such as 2 hours to the face pass effective period determined by a normal method.

An eleventh modification of the first embodiment will be described.
The sales support screen display unit 66 of the store terminal 12 selects a user item (for example, an icon including a name and a face photo) whose face pass has expired on the sales support screen (for example, an accounting screen). You may make it display in the mode which cannot. For example, it may be displayed grayed out, or may be displayed with the selection operation invalid (for example, with the disable attribute added). In addition, the item of the user whose face pass expiration date has expired may be hidden on the sales support screen. According to this modified example, since the users who are candidates for selection on the sales support screen can be limited to users within the face pass expiration date, the number of users who are candidates for selection can be suppressed, and the labor of selection by the store sales staff can be reduced. Can be reduced. In addition, it is possible to suppress the selection of a user whose face pass expiration date has expired, for example, to support the store salesperson to prompt the user to check in again, and to suppress the occurrence of errors during face pass settlement .

  In this modification, the trading support server 14 may further notify the store terminal 12 of the user's face pass expiration date as the store check-in information. Further, the buying and selling support server 14 periodically refers to the face pass expiration date of each user stored in the user information holding unit 111, periodically detects the user whose face pass expiration date has expired, and The user information may be notified to the store terminal 12 of the check-in target store. The specific subject of the user whose face pass has expired is the store terminal 12 in the former case, and the buying and selling support server 14 in the latter case.

A twelfth modification example related to the eleventh modification example of the first embodiment will be described.
The sales support screen display unit 66 of the store terminal 12 displays the information of the user whose face pass expiration date has expired (for example, an item including the name and face photo) separately from the information display area of the user within the face pass expiration date. It may be displayed in the area. For example, information on the user whose face pass has expired is not displayed in the information display area of the user within the face pass validity period, while the expiration information display area on each of the menu screen, product selection screen, and accounting screen is displayed. You may make it display newly. According to this modification, users who are selection candidates on the accounting screen can be limited to users within the face pass expiration date. Thereby, the number of users who become selection candidates can be suppressed, and the labor of selection by the store sales staff can be reduced. In addition, by always displaying the information of users whose face pass has expired on the sales support screen, when the user visits the store, the store salesperson calls for prompting check-in again. This makes it easier to suppress the occurrence of errors during face pass settlement.

  Note that the sales support screen display unit 66 displays, on the sales support screen, in an emphasized manner, the information of the user whose face pass expiration date is newer among the users whose face pass expiration date has expired. Also good. For example, in the expiration information display area, it may be displayed above the information of other users, or may be displayed with an emphasis color or object added. It is assumed that users who have recently expired their face pass are more likely to visit the store. When the user visits the store, the store salesperson is urged to check in again. It becomes easy to carry out.

A thirteenth modification of the first embodiment will be described.
The sales support screen display unit 66 of the store terminal 12 responds to the scheduled visit times of a plurality of users who have checked in on a face photo selection screen (for example, face pass settlement designation area 184 in FIG. 10) as a sales support screen. In this manner, an item including the name and face photo of each user may be displayed. Preferably, the item of the user whose current time is relatively close to the scheduled visit time is displayed in a manner that emphasizes the item of the user whose current time is relatively far from the planned visit time. For example, a color or object for emphasis may be added and displayed. In addition, the items of the user whose current time is closer to the scheduled visit time may be displayed in the upper part of the face pass settlement designation area 184. Since the user whose current time is close to the planned visit time is assumed to be a user who is highly likely to visit the store, the user item can be easily selected on the face photo selection screen.

  In this modification, the purchaser terminal 10, the store terminal 12, or the sales support server 14 further includes a store visit time estimation unit. Similar to the validity period determination unit of the ninth modification, the store visit time estimation unit calculates the time required to move from the current location to the store according to the location of the store to be checked in and the current location of the purchaser terminal 10. presume. The store visit time estimation unit specifies the time when the required travel time has elapsed from the check-in time as the scheduled store visit time. Even when any of the purchaser terminal 10, the store terminal 12, and the sales support server 14 includes a store visit time estimation unit, information (for example, check-in time, current location of the purchaser terminal 10, The location of the store, the moving means, etc.) may be transmitted by notification of check-in information from the purchaser terminal 10 to the sales support server 14 and notification of store check-in information from the sales support server 14 to the store terminal 12. The planned visit time specified by the visit time estimation unit may be transmitted in the same manner.

A fourteenth modification of the first embodiment will be described.
The sales support screen display unit 66 of the store terminal 12 displays a confirmation code input screen before displaying a face photo selection screen (for example, the display screen of the face pass settlement designation area 184 in FIG. 10) as the sales support screen. You may let them. On the face photo selection screen, only the face photo that matches the partial data of the confirmation code may be displayed. In addition, a face photo that matches a part of the data of the confirmation code may be displayed in a manner that emphasizes the inconsistent face photo (upper area, large size, emphasized color, a predetermined object added). . The partial data of the confirmation code may be the first digit of the confirmation code or the first and second digit strings, and is referred to as a “limited code” here. In this case, the trading support server 14 may hold the confirmation code, extract the limited code from the confirmation code, and provide the store terminal 12 with the store check-in information including the limited code. According to this modification, it is possible to suppress the number of users that are selection candidates while maintaining the fraud prevention effect, and to reduce the labor of selection by the store salesperson.

A fifteenth modification of the first embodiment will be described.
In the embodiment described above, the settlement permission determination unit 130 of the buying and selling support server 14 prohibits the settlement of the commodity price when the user's face pass expiration date related to the settlement request has expired. As a modification, even if the user's face pass expiration date related to the payment request has expired, the payment may be permitted if the payment amount is a predetermined amount (for example, 10,000 yen) or less. Further, in relation to the tenth modification, when the user related to the payment request is a regular customer at the payment target store, the payment permission determination based on the face pass expiration date may be skipped. In other words, when the user associated with the payment request is not a regular customer at the payment target store, the payment acceptance / rejection determination based on the face pass expiration date may be executed.

A sixteenth modification of the first embodiment will be described.
In the above embodiment, the user registers his / her face photo in the trading support server 14, the trading support server 14 provides the user's face photo to the store terminal 12 upon check-in, and the store salesperson We decided to compare the product buyer with the face photo on the selection screen. As a modified example, an image other than a face photograph may be used to identify a user (purchaser), that is, any image that can recognize a specific user by distinguishing them from others. Any image that shows appearance characteristics may be used. For example, it may be a character reflecting the appearance characteristics of the user, or image data of a portrait modeled on the user.

A seventeenth modification of the first embodiment will be described.
At present, electronic payment means are diversified. For example, in addition to credit card payment, prepaid card payment, debit card payment, communication carrier collective payment, remittance service, and the like exist. In this modification, a merchandise trading system 100 is proposed that further enhances the convenience for the user by realizing face pass settlement corresponding to various means of electronic settlement.

  The user inputs information necessary for payment using each payment method (hereinafter referred to as “payment required information”) to the purchaser terminal 10 for a plurality of payment methods that can be used by the user. The user information registration unit 34 of the purchaser terminal 10 transmits the input information to the trading support server 14, and the trading support server 14 holds the payment information of each of a plurality of payment methods that can be used by the user as user information. Store in the unit 111.

  In addition, the user inputs information indicating the order of settlement by each settlement means (hereinafter referred to as “settlement order information”) to the purchaser terminal 10. The user information registration unit 34 of the purchaser terminal 10 transmits the input information to the trading support server 14, and the trading support server 14 stores the settlement order information input by the user in the user information holding unit 111. As in the above embodiment, the settlement processing unit 132 of the trading support server 14 performs the following processing for supporting electronic settlement of purchase price on condition that settlement is permitted by the settlement permission determination unit 130. Execute.

  The payment processing unit 132 refers to the payment order information of the user who should perform electronic payment stored in the user information holding unit 111, and requests electronic payment in the order determined by the payment order information (requires payment of the payment means to be used). A telegram in which information is set) is transmitted to a predetermined settlement server 16 corresponding to each settlement means. For example, if the order of prepaid card payment → debit card payment → credit card payment is registered, the payment processing unit 132 first attempts a prepaid card payment. If the purchase amount exceeds the prepaid card charge amount, then debit card settlement is attempted. If the balance of the account used for debit card payment is insufficient, the credit card payment is tried next.

  According to this modification, electronic payment by a plurality of payment means that can be used by the user can be executed in the order desired by the user. In addition, by controlling to make electronic payment as successful as possible, the failure of electronic payment due to insufficient account balance is suppressed, and the convenience of the user is improved.

  There may be a plurality of settlement methods among the individual settlement methods. For example, in the case of debit card settlement, an account opened in bank A and an account opened in bank B can be selected. In such a case, the user inputs payment order information including payment order within individual payment means, for example, selection order of a plurality of holding accounts in debit card payment, to the purchaser terminal 10. The user information holding unit 111 of the trading support server 14 stores settlement order information including a settlement order within each settlement means. The settlement processing unit 132 of the trading support server 14 sequentially selects settlement means in the order determined by the settlement order information, and further sequentially selects settlement methods within the individual settlement means according to the settlement order information. Then, to the settlement server 16 corresponding to the settlement means in accordance with the settlement order information, a message in which settlement necessary information for designating the settlement method in the settlement means (for example, designating an account from which the purchase price should be deducted) is set is transmitted. To do.

An eighteenth modification of the first embodiment will be described.
The face pass settlement proposed in the embodiment requires the user to perform a check-in operation on a store to be visited. In other words, it imposes an additional operation on the user, check-in before visiting the store. Therefore, in order to make the check-in “use” by the user in order to spread the face-pass settlement business, this modification proposes a technique for providing incentives and convenience for check-in. Of course, in the following 1) to 7), all or a part of them may be arbitrarily combined.

1) Check-in with coupon selected:
The user pre-selects a coupon to be used at the store at the time of check-in. Information on the coupon selected by the user is notified to the store side, and at the time of face pass settlement at the store, settlement is executed with the accounting amount automatically applied by the coupon selected by the user at check-in.

  An example of the system configuration will be described. The store information holding unit 112 of the sales support server 14 stores in advance information on one or more coupons that each store provides to the user. When the purchaser terminal 10 should display the store detail screen 140, the purchaser terminal 10 acquires the coupon information together with the store information from the trading support server 14 and displays the coupon information on the store detail screen 140. On the store detail screen 140, the user performs a check-in operation after selecting a desired coupon.

  Subsequently, the purchaser terminal 10 adds information indicating the coupon selected by the user (hereinafter referred to as “selected coupon information”) to the check-in information transmitted to the trading support server 14. The buying and selling support server 14 transmits the selected coupon information (including the discount amount) to the store terminal 12 of the check-in destination store along with the user's face photo. The store terminal 12 displays the selected coupon information on the face pass settlement screen 190. Further, the store terminal 12 determines an amount obtained by subtracting the discount amount indicated by the selected coupon information from the original sales price of the product or service as the accounting amount, and displays the amount on the face pass settlement screen 190. At the time of executing the settlement, the store terminal 12 transmits a settlement request designating the discounted accounting amount to the trading support server 14 to execute the electronic settlement.

2) Coupon issue:
Coupons are issued at predetermined timings such as check-in, first visit, and tenth visit. At the time of payment by face pass, settlement is executed with the accounting amount to which the coupon issued at the previous check-in is automatically applied.

  As an example of the system configuration, a configuration similar to the above 1) may be used. However, the buying and selling support server 14 holds the check-in history described in the fifth modification and the settlement history described in the tenth modification. Furthermore, it is a reference for determining whether or not it is time to issue a coupon. In other words, a condition for executing a coupon issue event (hereinafter referred to as “coupon issue condition”) is held. When the check-in information is received from the purchaser terminal 10, the trade support server 14 refers to the check-in history and settlement history of the user and determines whether the coupon issue conditions are satisfied. When the coupon issue condition is satisfied, the buying and selling support server 14 provides the coupon information together with the store information to the purchaser terminal 10, and the purchaser terminal 10 displays the coupon information on the store detail screen 140. The subsequent processing is the same as in 1) above.

3) Timed coupon:
At the time of check-in, a time coupon with a predetermined valid period (for example, 1 hour) is issued for the purpose of promoting user visits. At the time of payment by face pass, the timed coupon issued at the time of check-in in advance performs settlement with the accounting amount automatically applied according to the expiration date.

  As an example of the system configuration, a configuration similar to the above 1) may be used. However, the coupon held by the buying and selling support server 14 and provided to the purchaser terminal 10 and the store terminal 12 is a timed coupon, that is, the coupon information includes data indicating an effective period such as one hour after check-in. It is. The purchaser terminal 10 displays the coupon validity period as coupon information and presents it to the user. The sales support server 14 provides the store terminal 12 with the user's check-in time together with the user's face photo and coupon information. The store terminal 12 determines whether or not the time coupon is valid based on the time from the user's check-in time to the accounting time (for example, the current time). If the validity period has not passed, in other words, if the accounting timing is within the validity period of the timed coupon, the store terminal 12 subtracts the discount amount indicated by the timed coupon from the original sales price of the product or service. Determine the amount as the accounting amount.

4) Check-in with comments:
Before entering the store, information such as matters to be communicated to the store clerk in advance (hereinafter referred to as “comments”) is entered in the comment field, and check-in is performed. This comment is notified to the store side. The store clerk can check the comments along with the photo of the check-in person and prepare for the customer's hospitality in advance. For example, a user's purchase history etc. can be confirmed and the product recommended this time can be checked in advance. In addition, it is possible to prepare such as arranging desired products of the user specified by the comments in the store and checking the product information.

  An example of the system configuration will be described. The purchaser terminal 10 displays a store detail screen 140 provided with a comment field where the user can input an arbitrary comment. The number of characters in the comment may be limited. For example, the comment field may be set so that the maximum number of characters that can be input is 100. The purchaser terminal 10 transmits the check-in information including the comment input in the comment field to the trading support server 14, and the trading support server 14 transmits the store check-in information including the comment to the store terminal 12. The sales support screen display unit 66 of the store terminal 12 displays the name and face photo of the user who has already checked in to the store on an initial screen (for example, a menu selection screen) displayed as a default as a sales support screen. A comment input by the user at the time of check-in is displayed in association with the user (for example, in the vicinity of the user's face photo).

5) Select the purpose of visit and check in:
The user checks in after selecting the purpose of visiting this store in advance. Information indicating the purpose of visit (hereinafter referred to as “visit purpose information”) is notified to the store side, and the store terminal 12 displays the purpose of the store visit along with the name and face photo of the check-in person. As a result, the store clerk can grasp the purpose of the user in advance and can appropriately call out and introduce the product to the user who has visited the store. In addition, if the purpose of visiting the store is, for example, “I want to browse the product by myself”, it is possible to dare to suppress the call to the user and allow the user to browse the product freely.

  The configuration of the merchandise trading system 100 of this modification is similar to the above 4). The store detail screen 140 of the purchaser terminal 10 is provided with a store visit purpose selection field instead of the comment field. Then, the contents selected by the user are added to the check-in information and transmitted to the store terminal 12.

6) Clerk's face photo response:
At the timing when the user checks in, a response message with a photograph of the face of the clerk at the check-in destination is presented to the user. 6-1) Each time a check-in is made, the store clerk may create a comment and reply, or 6-2) a fixed word may be returned. Supporting communication between the user and the store clerk, it is possible to promote the visit of the user.

  First, an example of the system configuration of 6-2) will be described. The trading support server 14 holds the store employee's face photograph registered in advance by the store and a fixed response comment in the store information holding unit 112. When the purchase support server 14 receives a check-in from the purchaser terminal 10, the transaction support server 14 acquires, as a response, the face photo of the clerk associated with the check-in destination store and the response comment from the store information holding unit 112. Provide to the purchaser terminal 10. The purchaser terminal 10 displays a face photograph of the clerk at the check-in destination and a response comment. Note that the buying and selling support server 14 may provide the purchaser terminal 10 with the face photograph of the clerk and the response comment together with the random number sequence data. The purchaser terminal 10 may cause the check-in screen 150 to display the clerk's face photo and response comment together with the confirmation code.

  Next, a system configuration example of the above 6-1) will be described. The store terminal 12 displays a comment input screen provided with a comment input field for inputting a response comment for a user who has checked in to the store. The store clerk inputs a response comment corresponding to the user in the comment input field of the comment input screen. The response comment is, for example, “△△ is prepared as a recommended product for XXX”. The store terminal 12 transmits a response comment to the buying and selling support server 14, and the buying and selling support server 14 sends the response comment to the purchaser terminal 10 together with the face photograph of the store clerk registered in advance by the store. The purchaser terminal 10 displays a face photo of the check-in shop assistant and a response comment on a predetermined screen after check-in.

7) Acquisition of cards and medals At the time of check-in, for example, a card of a famous talent group is issued at random. Acquired cards and medals can be stored in the holder.

  An example of the system configuration will be described. The buying and selling support server 14 holds check-in privilege information such as a card, a medal, and a predetermined premium image in advance. The trading support server 14 transmits the check-in privilege information to the purchaser terminal 10 when receiving the check-in information from the purchaser terminal 10. Check-in privilege information may be transmitted to the purchaser terminal 10 together with the data of the random number sequence. The purchaser terminal 10 displays the check-in privilege information provided from the trading support server 14 on the screen. Further, check-in privilege information is permanently stored in a local storage area in accordance with a user operation.

A nineteenth modification of the first embodiment will be described.
As shown in the embodiment, the check-in for face pass settlement is based on manually performing a check-in operation on a store page where the user wants to visit. In this modification, in order to further improve the convenience for the user, a technique for supporting check-in by the ICT technique is proposed. In any of the following 1) to 3), confirmation (verification) of the confirmation code at the time of settlement is necessary. Any combination of 1) to 3) is possible.

1) Auto check-in:
By turning on the auto check-in function and the GPS function in the purchaser terminal 10, when the user comes near the store, the check-in is automatically performed at the store. That is, automatic check-in is executed according to the current position of the purchaser terminal 10. Since this system configuration example has already been described as the third modification, it will be omitted.

2) Check-in at a fixed time:
Check in automatically by specifying the day of the week and time. This system configuration example is similar to the third modification. When the purchaser terminal 10 detects that the date and time when the user has previously registered in the purchaser terminal 10 is detected, the purchaser terminal 10 described in the third modification example for the store registered in the purchaser terminal 10 in advance. Perform automatic check-in processing.

3) Faster check-in:
As described above, in the embodiment, after the login screen, the service provider selection screen, and the store selection screen are displayed, the store detail screen for performing the check-in operation is displayed. In this modification, a technique for reducing the number of user operations is proposed while assuming manual check-in. Specifically, a transition is made directly from “favorites” to the check-in page.

  An example of the system configuration will be described. The purchaser terminal 10 further includes a favorite screen holding unit and a favorite registration unit. When the user inputs a registration operation that indicates that a store detail screen that presents information on a specific store and accepts a check-in operation to the store is used as a favorite screen, the favorite registration unit stores the data on the store detail screen. Store in favorite screen holding part. When the user selects a specific store name on the favorite selection screen of the purchaser terminal 10, the purchase support screen display unit 36 skips the display of the previous screen such as the store selection screen and is stored in the favorite screen holding unit. The store detail screen corresponding to the selected store name is displayed on the touch panel 20. When the store detail screen is provided as a web page from the trading support server 14, the favorite registration unit displays the store detail screen page designated by the user in the favorite function of the web browser installed on the purchaser terminal 10. Of course, you may register.

(Second Embodiment)
In the second embodiment, in addition to the face pass settlement function proposed in the first embodiment, a product that realizes a function of presenting an estimated value of waiting time until service provision to a service purchaser Propose a trading system.

  There has been a system that presents an approximate waiting time to the customer so far, but in the past, the system determined the waiting time per customer set uniformly as a given value in advance, "(Number of customers waiting) x waiting time per customer pair" determines the waiting time of the customer, or it is difficult to obtain the average service time while using queuing theory. In the same way as above, the average service time is set as a given value, and it remains at a level that determines the waiting time of the customer. As a result, the difference between the waiting time presented to the customer and the actual waiting time may become large.

  Therefore, in the merchandise trading system proposed as the second embodiment, in the flow of face pass settlement utilizing the mobile terminal proposed as the first embodiment, actions related to merchandise sales such as entry to a queue and accounting Measure the time and number of occurrences. And it is the measured value of those actions, in other words, the waiting time of a store is estimated based on the actual service provision condition with respect to the user who enjoyed the service in the past in the store. Then, when the user tries to check in, an estimated value of the waiting time is provided. Moreover, the accuracy of the estimated value of the waiting time is maintained by repeating the estimation of the waiting time periodically using the latest measured value (service provision status).

  The user in the second embodiment is typically a person who visits a service seller's store, enjoys the service and pays the consideration, that is, a person who purchases the service. The service includes, for example, a restaurant providing service at a restaurant, a window service at a bank, a monopoly store, a mass retailer, and a medical service at a hospital. The waiting time is, for example, the time from check-in to a restaurant using the purchaser terminal 10 until guidance to a seat at the restaurant (that is, until service provision is started at the restaurant). Further, it is the time from when the purchaser terminal 10 is used to check in to a mobile phone exclusive store until the response starts at the window of the exclusive store.

  Note that the purchase of a service is a concept including the purchase of a product. The waiting time for purchasing a product can be defined as the time from when a user checks in to a store until the purchase of the desired product is completed at the store.

  FIG. 12 shows a configuration of the commodity trading system 100 according to the second embodiment. Hereinafter, the description already described in the first embodiment is omitted as appropriate. In FIG. 12 and subsequent drawings, members that are the same as or correspond to members (for example, devices and functional blocks) in the first embodiment are denoted by the same reference numerals.

  The store terminal 12 includes a store clerk operation terminal 17 and an in-store reception terminal 18. The store clerk operation terminal 17 corresponds to the store terminal 12 of the first embodiment, and is typically a tablet terminal operated by a store employee. The store clerk operation terminal 17 executes the face pass settlement support process in the same manner as the store terminal 12 of the first embodiment, further displays information on the user waiting for service provision, and indicates the service provision status to the user. The input is accepted and notified to the trading support server 14. The in-store reception terminal 18 is an information processing terminal that registers information of customers who have visited the store directly without check-in in a queue, and is operated by the customer or store employee. The in-store reception terminal 18 may issue a reception slip on which a waiting number is written to a customer.

  The trading support server 14 executes face pass settlement support processing as in the first embodiment, and further manages queue information and waiting time information of a plurality of stores participating in face pass settlement. Moreover, the buying and selling support server 14 estimates the current waiting time at each store, and provides an estimated value of the waiting time to a user who wants to check in to the store.

  FIG. 13 is a block diagram showing a functional configuration of the purchaser terminal 10 of FIG. The purchaser terminal 10 further includes a queue input notification unit 44. Similar to the first embodiment, when the user performs a check-in operation on the store detail screen, the check-in notification unit 40 is also referred to as a store selected as a check-in destination (hereinafter also referred to as “selected store”). .) Is sent to the buying and selling support server 14.

  The service information acquisition unit 38 also functions as a waiting time information acquisition unit. Specifically, the service information acquisition unit 38 uses an estimated value (hereinafter also referred to as “estimated waiting time”) of the current waiting time at the selected store provided from the buying and selling support server 14 as a response to the check-in information. get. The service information acquisition unit 38 also acquires the current estimated waiting time at one or more other stores (hereinafter also referred to as “group stores”) belonging to the same group as the selected store.

  The purchase support screen display unit 36 also functions as a waiting time display unit. Specifically, when the user performs a check-in operation on the store detail screen, a check-in store confirmation screen that displays the waiting time of the selected store acquired by the service information acquisition unit 38 and the waiting time of the group store side by side. It is displayed on the touch panel 20. A specific example of the check-in store confirmation screen will be described later.

  The queue input notification unit 44 executes processing for adding a user to the queue of the store designated by the user. Specifically, when the user performs a store visit operation for either the selected store or the group store on the check-in store confirmation screen, the queue input notification unit 44 sends the queue input information to the trading support server 14. Send.

  The queue input information may have the same configuration as the check-in information in the first embodiment. For example, the queue input information may specify a user ID and a store ID that is a target of the store registration operation. The queue input information can be said to be information declaring that the user is queued (entered) in the queue of a specific store. The trading support server 14 determines the store designated by the queue input information as the store for the user's check-in destination, and determines the store for providing the check-in information for the store indicating the visit of the user.

  FIG. 14 is a block diagram showing a functional configuration of the clerk operation terminal 17 of FIG. The salesclerk operation terminal 17 further includes a queue information acquisition unit 80, a queue information display unit 82, and a service status notification unit 84. The queue information acquisition unit 80 acquires the queue information of the own store managed by the trading support server 14 via the communication network. In the embodiment, when the trading support server 14 updates the queue information, the updated queue information is provided to the store clerk operation terminal 17 of the store associated with the information. As a modification, every time a predetermined time such as 30 seconds elapses, the queue information acquisition unit 80 may access the trading support server 14 to acquire the latest queue information.

  The queue information display unit 82 causes the touch panel 50 to display a turn waiting management screen indicating the queue information acquired by the queue information acquisition unit 80. A specific example of the turn waiting management screen will be described later.

  The service status notification unit 84 obtains input information when information indicating a change in the service provision status (hereinafter also referred to as “service status update information”) is input to the waiting management screen. And the queue information of the own shop which the trading support server 14 manages is updated by transmitting the acquired service status update information to the trading support server 14. Specifically, the service status notifying unit 84, when information indicating the start of service provision for the user (customer) is input to the waiting management screen, the user ID, the store ID, the service start date and time, the service provision The service status update information associated with the place is transmitted to the trading support server 14.

  FIG. 15 is a block diagram showing a functional configuration of the in-store reception terminal 18 of FIG. The in-store reception terminal 18 is similar to the structure of the clerk operation terminal 17 and includes corresponding functional blocks (denoted with the same reference numerals). However, the in-store reception terminal 18 provides a user interface function for customers who have visited the store in an unchecked state, and specifically provides a display function of queue information and a queue entry function. . The in-store reception terminal 18 includes a queue information acquisition unit 90, a queue information display unit 92, and a queue input notification unit 94.

  The queue information acquisition unit 90 corresponds to the queue information acquisition unit 80 of the clerk operation terminal 17 and acquires the queue information of the own store managed by the trading support server 14 via the communication network. The queue information display unit 92 causes the touch panel 50 to display a reception screen indicating the queue information acquired by the queue information acquisition unit 80. A specific example of the reception screen will be described later.

  The queue input notification unit 94 executes a process for adding a user to the queue of the store where the in-store reception terminal 18 is installed. The target user is a customer who has visited the store directly without prior check-in by the purchaser terminal 10. When the user performs a registration operation on the reception screen, the queue input notification unit 94 transmits queue input information specifying a predetermined store ID to the trading support server 14.

  FIG. 16 is a block diagram showing a functional configuration of the buying and selling support server 14 of FIG. The trading support server 14 includes a queue information holding unit 200, a waiting time information holding unit 201, a waiting time information providing unit 202, a queue input receiving unit 204, a queue information updating unit 206, and a queue information providing. It further includes a unit 208, a service status reception unit 210, and a waiting time estimation unit 212.

  The queue information holding unit 200 is a storage area that stores queue information of each of a plurality of stores participating in face pass settlement. The waiting time information holding unit 201 is a storage area that stores waiting time information indicating the current estimated waiting time of each of a plurality of stores participating in face pass settlement.

  FIG. 17 shows a configuration of queue information stored in the queue information holding unit 200. The queue information includes a management ID, a store ID, a waiting number, a check-in date and time, a service start date and time, and a service providing place. The queue information holding unit 200 holds a record of the queue information for each store and for each checked-in (stored) user. The queue information can be said to be information indicating users who are queued for each store.

  The management ID is a unique ID of an entry in the queue, and here is the ID of a user who has already checked in to the store. The waiting number is a reference number for each store that is presented to a user who has already checked in or visited the store. The service start date and time is information indicating the date and time when service provision to the user is started at the store. For example, in a restaurant, the date and time when a user is guided to a seat may be used. The service start location is information indicating a location where the service is provided to the user at the store. For example, in a restaurant, an identification number of a seat that guides a user may be used.

  FIG. 18 shows a configuration of waiting time information stored in the waiting time information holding unit 201. The waiting time information includes a group ID, a store ID, and an estimated waiting time. The waiting time information holding unit 201 holds a record of waiting time information for each store. When a store belongs to the same group as other stores, the same group ID is set in advance in the records of those stores. Of the waiting time information, the group ID and the store ID are fixed in principle, while the waiting time is updated as needed.

  Regarding grouping of a plurality of stores, for example, the same group ID may be set for a plurality of stores where the manager is the same, a plurality of stores belonging to the same company group, a plurality of stores in business partnership, and the like. . Further, the same group ID may be given to a plurality of stores that are geographically adjacent, in other words, a plurality of stores whose distances between stores are within a predetermined range. Moreover, you may set the group of a store by arbitrary combinations of these conditions.

  Returning to FIG. 16, when the check-in reception unit 120 receives the check-in information transmitted from the purchaser terminal 10, the wait time information providing unit 202 waits for the wait time of the selected store designated by the check-in information. Obtained from the time information holding unit 201. At the same time, the waiting time of the group store having the same group ID as the selected store is also acquired from the waiting time information holding unit 201. The waiting time information providing unit 202 transmits both the waiting time of the selected store and the waiting time of the group store to the purchaser terminal 10 that is the transmission source of the check-in information.

  The queue input reception unit 204 receives queue input information transmitted from the purchaser terminal 10 and the in-store reception terminal 18. The queue information update unit 206 updates the queue information stored in the queue information holding unit 200 based on the queue input information received by the queue input reception unit 204.

  Specifically, the queue information update unit 206 adds a new record in which the user ID and store ID specified by the queue input information are set to the queue information holding unit 200, and further adds the following information to the record. Record. In other words, the queue information update unit 206 assigns and records the waiting number according to a predetermined waiting number system for the store specified by the store ID. The date and time when the queue input information is received is recorded as the check-in date and time.

  The queue information providing unit 208 monitors the update status of the queue information held by the queue information holding unit 200, and when the queue information of a store is updated, the store clerk operation terminal 17 of the store and the store information The updated queue information is transmitted to the reception terminal 18. For example, when the queue information of a certain store ID is updated, one or more queue information associated with the store ID is provided. At this time, the waiting time of the store stored in the waiting time information holding unit 201 is also transmitted. As a result, the turn waiting management screen (store clerk operation terminal 17) and the reception screen (in-store reception terminal 18) reflecting the latest queue information and waiting time are displayed.

  The service status reception unit 210 receives service status update information transmitted from the clerk operation terminal 17. The queue information update unit 206 updates the queue information stored in the queue information holding unit 200 based on the service status update information received by the service status reception unit 210. Specifically, the queue information update unit 206 starts the service specified by the service status update information for the record specified by the user ID (management ID) and store ID specified by the service status update information. Add date and time and service location to record. As described above, the updated queue information is provided to the clerk operation terminal 17 and the in-store reception terminal 18 by the queue information providing unit 208.

  The waiting time estimation unit 212 estimates the current waiting time of each store based on the latest service provision results of each store, and stores each store stored in the waiting time information holding unit 201 until that time based on the estimated current waiting time. Update the wait time value. The waiting time estimation unit 212 periodically repeats the waiting time estimation process and the update process for each store, for example, every time a predetermined time such as 1 hour or 30 minutes elapses from the previous estimation process. The updated waiting time information is provided to the purchaser terminal 10 by the waiting time information providing unit 202.

  Here, a method for calculating the waiting time for a certain store (referred to as “specific store”) will be described. The waiting time estimation unit 212 refers to the queue information holding unit 200 and selects a predetermined number of records for which service provision has been started most recently from one or more queue information records in which the ID of a specific store is set. Extract. The number of records to be extracted may be determined based on the knowledge and experience of the administrator of the commodity trading system 100. For example, five records may be extracted from the newer service start date and time.

  The waiting time estimation unit 212 obtains the time from the check-in date and time to the service start date and time recorded in each extracted record as a waiting time, and sets the average waiting time of the extracted records as the current waiting time in a specific store. decide. That is, the moving average value of the waiting time based on a predetermined number of queue information records for which service provision has been started recently is determined as the current waiting time. However, there is no limit to the method for calculating the average value. For example, the waiting time of each record is obtained, and the weighted average value calculated by assigning a greater weight to the service start date / time may be determined as the current waiting time. .

  In the embodiment, the check-in date and time is used as the starting point of the waiting time. Specifically, the date and time when the trading support server 14 receives the queue input information transmitted from the purchaser terminal 10 is used. In a modification, the date and time when the buying and selling support server 14 receives the check-in information transmitted from the purchaser terminal 10 may be used as the starting point of the waiting time, and the buying and selling support server 14 may use the check-in information for the store. The date and time transmitted to the clerk operation terminal 17 may be used. That is, the waiting time estimation unit 212 may estimate the waiting time based on the time related to the check-in operation by the user and the service provision start time at the store.

  The operation of the commodity trading system 100 having the above configuration will be described below. The operation of the commodity trading system 100 according to the second embodiment is premised on the operation of the commodity trading system 100 described in the first embodiment. The same operations as those of the commodity trading system 100 of the first embodiment will not be described as appropriate, and differences will mainly be described. The store in the following example is a restaurant.

  When a check-in operation is detected on the store detail screen 140 in FIG. 7, the check-in notification unit 40 of the purchaser terminal 10 transmits check-in information to the trading support server 14. The check-in reception unit 120 of the trading support server 14 receives the check-in information transmitted from the purchaser terminal 10. The waiting time information providing unit 202 acquires the estimated waiting time of the selected store indicated by the check-in information and the estimated waiting time of the group store associated with the selected store from the waiting time information holding unit 201 to acquire the purchaser terminal 10. Send to. The service information acquisition unit 38 of the purchaser terminal 10 receives the waiting time information as a response of the trading support server 14 to the check-in information notification. The purchase support screen display unit 36 displays a check-in store confirmation screen that presents estimated waiting times of the selected store and the group store.

  FIG. 19 shows a check-in store confirmation screen 220 displayed on the purchaser terminal 10. The selected store information area 222 displays the current estimated waiting time of the selected store, and the group store information area 224 displays the current estimated waiting time of the group store. FIG. 19 illustrates an example in which the Shibuya store, the Harajuku store, and the Ebisu store that are close to each other on the map are set as the same group in the trading support server 14. The user considers the waiting time of the selected store and the group store, selects a store to be registered, and taps the store registration button 226 (referred to as “registration operation”). When a registration operation for a specific store is detected on the check-in store confirmation screen 220, the queue input notifying unit 44 transmits queue input information specifying a registration operation target store to the trading support server 14. The trading support server 14 adds a user to the queue of the registration operation target store.

  Here, the addition of the user to the queue may be performed via the in-store reception terminal 18. FIG. 20 shows a reception screen 230 displayed on the in-store reception terminal 18. The queue information acquisition unit 90 of the in-store reception terminal 18 acquires the queue information of the own store provided from the trading support server 14. The queue information display unit 92 extracts the number of users waiting for service provision and the estimated waiting time from the queue information of the own store. For example, the number of records in the queue information provided from the trading support server 14 may be specified as the number of users waiting for service provision. The users waiting for service provision include both users who have checked in via the purchaser terminal 10 and users who have registered via the in-store reception terminal 18. The queue information display unit 92 displays the number of users waiting for service provision and the estimated waiting time in the waiting time information area 232 of the reception screen 230.

  A user who has visited the store directly without checking in with the purchaser terminal 10 confirms the waiting time displayed on the reception screen 230 and taps the registration button 234 (referred to as “registration operation”). When a registration operation is detected on the reception screen 230, the queue input notification unit 94 of the in-store reception terminal 18 transmits queue input information designating the own store to the trading support server 14. At that time, the user ID may not be set, or a predetermined value indicating information from the in-store reception terminal 18 may be set.

  The queue input reception unit 204 of the trading support server 14 receives the queue input information transmitted from the purchaser terminal 10 and the store reception terminal 18. When the sender is the purchaser terminal 10, the queue input reception unit 204 sets user check-in information (FIG. 6B) based on the queue input information and stores it in the user information holding unit 111. . The random number acquisition unit 122 acquires a random number sequence, and the random number providing unit 124 provides the random number sequence to the purchaser terminal 10. As a result, the confirmation code is provided to the user as in the first embodiment. The check-in information providing unit 126 transmits store check-in information to the store clerk operation terminal 17.

  Regardless of whether the sender of the queue input information is the purchaser terminal 10 or the in-store reception terminal 18, the queue information update unit 206 determines whether the check-in destination store or the in-store reception terminal 18 is installed. Update the queue information. The queue information providing unit 208 provides the updated queue information to the store clerk operation terminal 17 and the store reception terminal 18 of the store associated with the queue information. Thereby, the turn waiting management screen of the clerk operation terminal 17 and the reception screen 230 of the in-store reception terminal 18 are switched to contents reflecting the updated queue information.

  FIG. 21 shows a turn waiting management screen 240 displayed on the clerk operation terminal 17. The queue information acquisition unit 80 of the clerk operation terminal 17 receives the queue information of the own store transmitted from the trading support server 14. The queue information display unit 82 displays the queue information of the own store in the turn waiting list 242. At that time, the check-in date and time is displayed in the store visit time field. Further, a plurality of records provided as queue information are displayed side by side on the waiting list 242 in ascending order of visit times, that is, in ascending order of check-in date / time or visit date / time.

  The store employee confirms the turn waiting management screen 240, gives priority to the customers displayed on the turn waiting list 242 and guides them to the seat, and starts providing services to the customers. At that time, the employee confirms the waiting number of the customer to be guided to the seat, taps a record in the waiting list 242 indicating the waiting number, inputs information on the guiding seat, and then taps the guidance button 244. . The guidance button 244 can be said to be a button for registering the start of service provision. When the guidance button 244 is tapped, the service status notification unit 84 of the clerk operation terminal 17 transmits service status update information indicating that service provision to the user has started to the trading support server 14.

  The service status reception unit 210 of the trading support server 14 receives the service status update information transmitted from the clerk operation terminal 17. The queue information update unit 206 identifies the record of the customer whose service has been started from the queue information of the store indicated by the service status update information. Then, the service start date / time and the service providing location value indicated by the service status update information are recorded in the specified record. The waiting time estimation unit 212 periodically refers to the latest queue information of each store, and estimates the current waiting time of each store based on the difference between the check-in date and the service start date. Then, by storing the estimated waiting time data for each store in the waiting time information holding unit 201, the latest estimated waiting time is provided to the check-in person.

  The operation of the system after the start of service provision at the store is the same as in the first embodiment. That is, at the time of transaction at the store, a face pass settlement process is executed using the user's photo previously notified to the store with the user's prior check-in operation and the confirmation code previously notified to the user. .

  According to the commodity trading system 100 of the second embodiment, the entry time for the store queue formed by the user waiting for service provision and the service start time for the user are measured, and based on these measured values. Estimate store waiting time. In other words, the waiting time of the user in the past past is actually measured, and the waiting time of the user who is going to check in to the store is estimated based on the waiting time. In addition, the waiting time is reestimated periodically based on the latest service provision results, and the estimated value is updated. As a result, in addition to the effects described in the first embodiment, a highly accurate estimated value is presented to the user as the current waiting time of the store to be checked in at the time of advance check-in that is essential in face pass settlement. it can. In addition, it is possible to support the decision making of check-in and effective use of the waiting time, thereby improving the convenience for the user.

  In addition to the estimated waiting time of the selected store selected on the store detail screen 140, the estimated waiting time of other stores belonging to the same group as the selected store is also presented to the user. Thereby, the choice of the store selection according to waiting time can be shown to a user. In addition, even for the seller, even when the waiting time of the selected store is long, it is possible to facilitate attracting customers to the group store, so that it is easy to avoid loss of sales opportunities.

  The second embodiment has been described above. This embodiment is an exemplification, and it will be understood by those skilled in the art that various modifications can be made to combinations of the respective constituent elements and processing processes, and such modifications are also within the scope of the present invention. is there. A modification is shown below.

A first modification of the second embodiment will be described.
In the above embodiment, the waiting time is estimated based on the difference between the check-in date and the service start date and time. As a modified example, the waiting time may be estimated based on the measured values of the average arrival rate and average service time of the user by using a known queuing theory. The configuration of this modification also has the same effect as that of the second embodiment.

  In this modification, the queue information holding unit 200 of the buying and selling support server 14 further holds a service end date and time, which is a date and time when service provision to the user (customer) is ended in the store, in the queue information record. Further, when the service status notifying unit 84 of the clerk operation terminal 17 detects the input of information indicating that the service provision to the customer has ended, the service status update information including the current date and time as the service end date and time is supported. Send to server 14.

  For example, the service status notifying unit 84 associates the user ID, the store ID, and the service end date when information indicating that the service price (product price) has been successfully settled is received from the trading support server 14. The situation update information may be transmitted to the trading support server 14. Further, when the determination button 198 is tapped on the face pass settlement screen 190 shown in FIG. 11, similar service status update information may be transmitted to the buying and selling support server 14. The service status reception unit 210 of the trading support server 14 records the service end date and time in the queue information record specified by the user ID and the store ID.

  Also in this modification, the waiting time estimation unit 212 of the trading support server 14 periodically estimates the waiting time of each store and updates the waiting time information of the waiting time information holding unit 201. Here, a method for calculating the waiting time for a certain store (referred to as “specific store”) will be described. The waiting time estimation unit 212 refers to the queue information holding unit 200 and extracts a predetermined number of records for which service provision has been completed most recently from one or more queue information records in which specific store IDs are set. To do. The number of records to be extracted may be determined based on the knowledge and experience of the administrator of the commodity trading system 100. For example, five records may be extracted from the newest service end date and time.

  The waiting time estimation unit 212 obtains the time from the service start date and time to the service end date and time recorded in each extracted record as the service time, and calculates the average service time of the extracted records as the current average service time at the specific store. Determine as. That is, the moving average value of the service time based on a predetermined number of queue information records for which service provision has been completed most recently is estimated as the current average service time.

  In addition, the waiting time estimation unit 212 refers to the queue information holding unit 200 and estimates the latest waiting time, for example, the previous waiting time from one or more queue information records in which the ID of the specific store is set. Then, the number of check-ins within the period from now on (including the number of registrations from the in-store reception terminal 18) is specified. Specifically, the number of records whose check-in date / time is within the latest fixed period is specified as the number of check-ins. Then, the average arrival rate of the user is estimated based on the number of check-ins. In other words, the frequency of check-in to a specific store per unit time is estimated as the average arrival rate.

  The waiting time estimation unit 212 calculates the average waiting time of a specific store by applying the average arrival rate of the user and the average service time obtained above to the M / M / S queuing model. Is recorded as the current estimated waiting time. The value of “S” in the above model may be predetermined for each store, or may be the number of spaces serving as a unit for guiding a set of customers. For example, if the specific store is a restaurant, the value of S may be set as the number of seats, the number of tables, the number of boxes, or the like as a unit of customer guidance. The M / M / S queue model may be a known model, for example, a known calculation formula.

  The service hours may be calculated by the clerk operation terminal 17 instead of the trading support server 14. Specifically, the clerk operation terminal 17 may further include a service start time holding unit that stores a service start date and time for a customer, and a service time calculation unit. When the service time calculation unit detects an input of information indicating that the service provision to the customer has ended (for example, accepts a notification of successful settlement from the trading support server 14), the current date and time at that time is used as the service end date and time The time from the service start date to the service end date to the customer is calculated as the service time. Then, the service status notification unit 84 of the clerk operation terminal 17 may transmit the service time, user ID, and store ID calculated by the service time calculation unit to the trading support server 14 as service status update information.

  Thus, the clerk operation terminal 17 may notify the trading support server 14 of the service start time and the service end time, or may notify the service time itself. That is, the store clerk operation terminal 17 may provide the trading support server 14 with information that can specify the service time provided by the store to the customer. The trading support server 14 identifies the service time based on the information provided from the clerk operation terminal 17, while identifying the customer arrival rate from the information managed by itself, and applies this to the queuing model for averaging Estimate waiting time.

  Further, the buying and selling support server 14 may estimate the waiting time of the store by using both the method described in the second embodiment and the method described in the first modification. Then, the shorter waiting time may be presented to the user as the estimated waiting time. According to this aspect, it is easy to increase the certainty that the user exists in the store at the time of starting the service, and it is easy to prevent the provision of the service from being routed behind others due to the absence of the user. In addition, when the service can be provided at the store, the possibility that the customer is visiting the store increases, and it becomes easy to realize efficient service provision. Conversely, the longer waiting time may be presented to the user as the estimated waiting time. According to this aspect, it becomes easy to prevent a user who has checked in beforehand from waiting for a long time exceeding the estimated waiting time.

A second modification of the second embodiment will be described.
In the above embodiment, the buying and selling support server 14 1) stores the service start time for each user (customer) at the store, 2) estimates the current waiting time at the store, and 3) estimates of waiting time. Is provided to the purchaser terminal 10. As a modification, an apparatus on the store side, for example, the clerk operation terminal 17 may execute at least a part of the above 1) to 3). The configuration of this modification also has the same effect as that of the second embodiment.

  For example, the clerk operation terminal 17 may include a waiting time estimation unit 212 that the trading support server 14 includes in the embodiment, and may estimate the waiting time of the own store based on the service status update information. That is, the store clerk operation terminal 17 may execute the above 1) and 2) to notify the trading support server 14 of the estimated waiting time of the store. The trading support server 14 stores the estimated waiting time provided from the clerk operation terminal 17 and provides it to the purchaser terminal 10 when check-in to the store (or another store belonging to the same group as the store) is performed. May be.

A third modification of the second embodiment will be described.
Although not mentioned in the above embodiment, the buying and selling support server 14 may further include a provision condition determination unit that determines whether or not a predetermined provision condition is satisfied. The waiting time information providing unit 202 of the trading support server 14 provides the purchaser terminal 10 with an estimated waiting time of the group store in addition to the selected store when the providing condition determining unit detects that the providing condition is satisfied. On the other hand, if the provision condition is not satisfied and the satisfaction of the provision condition is not detected, only the estimated waiting time of the selected store may be provided to the purchaser terminal 10.

  The provision condition determination unit of the sales support server 14 may determine that the provision condition is satisfied when the waiting time of the selected store is equal to or greater than a predetermined threshold. This threshold value may be a fixed time (for example, one hour) predetermined by the administrator of the trading support server 14 or may be an arbitrary time registered in the trading support server 14 by the user.

  Further, the waiting time information providing unit 202 of the buying and selling support server 14 may temporarily provide only the estimated waiting time of the selected store to the purchaser terminal 10 as a response to the check-in information. Upon receiving an operation input for instructing display of group store information on the store detail screen 140 of the purchaser terminal 10, the purchaser terminal 10 may transmit a waiting time provision request for the group store to the buying and selling support server 14. . Upon receiving this request, the provision condition determining unit of the purchaser terminal 10 determines that the provision condition is satisfied, and the waiting time information providing unit 202 further provides the estimated waiting time of the group store to the purchaser terminal 10. Also good.

A fourth modification of the second embodiment will be described.
Although not mentioned in the above embodiment, the buying and selling support server 14 is registered in advance in the buying and selling support server 14 at a timing when the remaining waiting time of the user reaches a predetermined time. A message indicating that service provision will start soon (hereinafter referred to as “service start alert”) may be notified to the contact address. According to this modification, it is possible to improve the certainty that the user visits the store at the start of service provision and to support the user to enjoy the desired service.

  For example, the queue information update unit 206 of the trading support server 14 waits for the estimation of the check-in target store from the current date and time when the queue information should be recorded in the queue information holding unit 200 with a certain user's check-in. The estimated value of the service start date and time over time (hereinafter referred to as “estimated service start date and time”) may be included in the queue information and recorded. The trading support server 14 further includes an alert notification unit, and when the alert notification unit detects that the interval between the current date and time and the estimated service start date and time is less than or equal to a specified time, the alert notification unit transmits a service start alert to a specified contact. May be.

  This specified time may be a time predetermined in the trading support server 14 or may be a time registered by the user in the trading support server 14 in advance, and may be set to 15 minutes, for example. The specified contact information is typically an information device that receives a service start alert, and may be, for example, the address of the purchaser terminal 10 registered in advance in the trading support server 14 by the user. The transmission method of the service start alert may be an e-mail or a known push notification for the smartphone.

  In addition, when the waiting time estimation unit 212 updates the waiting time of the store, the queue information updating unit 206 of the buying and selling support server 14 calculates the estimated service start date and time recorded in advance based on the updated waiting time. It may be updated. Specifically, the difference between the estimated waiting time before update and the estimated waiting time after update may be reflected in the estimated service start date and time recorded in advance. For example, when the estimated waiting time after the update is shorter than the estimated waiting time before the update, the estimated service start date and time may be updated earlier by the shortened time. According to this aspect, the service start alert can be notified to the user at a timing reflecting the latest estimated waiting time.

A fifth modification example of the second embodiment will be described.
Although partly described as a modification of the first embodiment, the store check-in information provided from the trading support server 14 to the clerk operation terminal 17 is not limited to the user's face photo, but the user It is information that can be distinguished from others, and various identification information regarding the user may be set. This identification information does not necessarily need to be information indicating the appearance characteristics of the user. For example, words (a secret word, a note, etc.) decided in advance between a store (employee) and a user may be used. In this case, the user declares the secret word and name to the store employee, and if they are correct, the store employee may proceed with the settlement process. Further, only the user's name may be provided from the sales support server 14 to the clerk operation terminal 17. In this case, the user declares the name to the store employee, and if the name exists in the list on the store clerk operation terminal 17, the store employee may cause the settlement process to proceed.

(Third embodiment)
In the third embodiment, the face pass settlement proposed in the first and second embodiments is applied when the seller's store is a mobile sales store such as a mobile sales vehicle (for example, “mobile supermarket”). A product trading system 100 is proposed.

  In the third embodiment, the check-in operation to the seller store in the first and second embodiments is replaced with a visit instruction operation for instructing the seller store to visit a desired area. . Specifically, in accordance with an input of a visit instruction operation on a predetermined screen (for example, the store detail screen 140) of the purchaser terminal 10, the purchaser terminal 10 transmits visit instruction information indicating the visit instruction to the trading support server 14. . The trading support server 14 transmits the visit instruction information to the store terminal 12 in addition to the user's face photograph.

  The structure of the visit instruction information is the same as the store check-in information in the first and second embodiments, but includes information indicating the region and date / time to which the seller store should visit. The visiting area specified by the visiting instruction information may be a living area of a consumer. For example, it may be a region near the user's address, a region near the user's workplace, or a region convenient for the user to purchase products. Thereby, the seller can recognize the visit destination and the visit date and time together with the user's face photograph at the store terminal 12.

  The user may designate the area and date / time for instructing the visit of the seller store on the input screen for the visit instruction operation (for example, the store detail screen 140). As for the visiting area, the area desired to be visited for the mobile sales store may be registered in the buying and selling support server 14 at the timing of user registration or the like, and the user information holding unit 111 of the buying and selling support server 14 may store it. In addition, the region and the date and time that the seller store can visit may be determined in advance, and may be displayed on the store detail screen 140 of the purchaser terminal 10 so as to be selectable. The user may input a visit instruction operation for a desired seller store (mobile store) while selecting a region and date / time convenient for the user.

Other configurations of the commodity trading system 100 according to the third embodiment are the same as those of the commodity trading system 100 according to the first or second embodiment. For example, the strength of security may be further enhanced by combining with the verification code verification processing described in the first embodiment. According to the third embodiment, face pass settlement can be realized even when a purchaser purchases a product at a mobile sales store, in other words, when the seller store is a mobile sales store. For example, the convenience of face pass settlement can be provided for a product sales service by a mobile sales vehicle in a depopulated area.
The technical idea of the third embodiment can also be expressed as a configuration appended below.

(Appendix 1)
A purchaser terminal used by the purchaser of the product;
A merchant terminal used by the merchant of the product,
A server connected to the purchaser terminal and the seller terminal via a communication network;
With
The seller ’s store is a mobile store,
The buyer terminal
A reception unit that receives a visit instruction operation from the purchaser to instruct the seller's store to visit a desired area;
The server
A payment information holding unit for holding payment information, which is information necessary for the purchaser to electronically pay for the product price;
A purchaser information providing unit for providing purchaser identification information for identifying a purchaser to the seller terminal when the visit instruction operation is performed at the purchaser terminal;
The merchant terminal is
When a purchaser purchases a product at the store of the seller, a selection screen for allowing the seller to select information on the purchaser who purchases the product from the purchaser identification information notified from the server is displayed. A selection screen display section to be
A payment request notifying unit for notifying the server of a payment request specifying the purchaser selected on the selection screen,
The information processing system, wherein the server further includes a payment processing unit that executes electronic payment for a product price using payment information of a purchaser specified by the payment request.

(Fourth embodiment)
In the first and second embodiments, a user who uses the product trading system 100 for purchasing a product or service (hereinafter referred to as a “user”, but can also be referred to as a purchaser or a customer) is an actual store. A check-in operation for designating was performed at the purchaser terminal 10. This act of check-in can be said to be a statement of intention indicating that the customer intends to visit a store that provides the desired product or service, but does not promise a date and time for visiting the store. Therefore, the systems described in the first and second embodiments are particularly suitable for stores that do not require visiting reservations.

  On the other hand, there are stores where a user should make a visit reservation specifying a visit date and time, and there are stores that accept both reserved users and users without reservations. These stores are also collectively referred to as “reservation-type stores”. Reservation-type stores include various industries and business types such as restaurants, boutiques, and medical institutions. Reservation-type stores accept visit reservations from users, but imposing a separate check-in operation on reserved users can be troublesome for the user and reduce user convenience. The inventor has conceived that there are cases.

  Therefore, in the fourth embodiment, a face pass settlement mechanism suitable for a reservation-type store is proposed. The configuration of the commodity trading system 100 of the fourth embodiment is the same as that of the commodity trading system 100 of the first embodiment, that is, as shown in FIG.

  FIG. 22 is a block diagram showing a functional configuration of the purchaser terminal 10 of FIG. The purchaser terminal 10 according to the fourth embodiment further includes a reservation screen display unit 250 and a reservation information notification unit 252. In the drawings subsequent to FIG. 22, the same or corresponding functional blocks as those described in the first to third embodiments are denoted by the same reference numerals, and redundant description will be omitted as appropriate.

  Similar to the purchase support screen display unit 36, the reservation screen display unit 250 causes the touch panel 20 to display a store visit reservation screen that is a user side screen in the face pass payment service. Similar to the product purchase support screen displayed by the purchase support screen display unit 36, the store visit reservation screen provides (1) a login screen to the trading support server 14 as an initial screen, and (2) a face pass settlement service. Service provider (brand) selection screen, (3) Store selection screen operated by the service provider, (4) Store detail screen displaying detailed information of the store, (5) Reservation when making a store visit reservation A completion screen is included. The reservation screen display unit 250 sequentially displays these multiple types of screens according to user operations. Of course, in an actual implementation, some of these multiple types of screens may be displayed. For example, when a face pass settlement solution is provided for each company, the brand selection screen (2) may not be provided, and the store selection screen (3) may be displayed as a top screen after login.

  When the user selects a reservation-type store and selects the face pass settlement selection field 142 on the store detail screen 140 illustrated in FIG. 7, the reservation screen display unit 250 includes an input field for a visit date and a visit time, a reservation A reservation input screen including an execution button is displayed. When a reservation-type store that accepts both check-in and reservation is selected, the reservation screen display unit 250 simply checks in without specifying a visit date or time, or specifies a visit date and time to make a visit reservation. A selection screen may be further displayed. The reservation input screen may be displayed by the purchase support screen display unit 36 as a part of the product purchase support screen.

  When the operation detection unit 26 inputs a predetermined operation (for example, pressing operation of a reservation execution button, hereinafter referred to as “reservation execution operation”) indicating that the user makes a store visit reservation on the reservation input screen, Detect that fact. The reservation information notification unit 252 is input information for the reservation input screen when a reservation execution operation is detected, and reservation information indicating the reservation contents of the user for the store for which the user has selected face pass settlement on the store detail screen Is transmitted to the trading support server 14. This reservation information includes a user ID, a reservation service provider ID and a store ID, and a date and time (hereinafter referred to as “reservation visit date and time”) that promises to visit the store.

  The one-time code generation unit 42 acquires a random number sequence transmitted from the trading support server 14 as a response to the notification of the reservation information, and generates a confirmation code based on the acquired random number sequence, as in the first embodiment. . The confirmation code of the fourth embodiment is also verification information that is temporarily valid only for this visit reservation, and is a so-called one-time password. The reservation screen display unit 250 displays the confirmation code generated by the one-time code generation unit 42 on a reservation completion screen similar to the check-in screen 150 of FIG. The reservation screen display unit 250 displays on the reservation completion screen the reservation visit date and time input by the user during the reservation execution operation.

  FIG. 23 is a block diagram showing a functional configuration of the trading support server 14 of FIG. The trading support server 14 according to the fourth embodiment further includes a reservation information receiving unit 260 and a reservation information providing unit 262. The reservation information reception unit 260 operates in the same manner as the check-in reception unit 120. Specifically, the reservation information notified from the purchaser terminal 10 is received, and the user reservation information based on the reservation information is stored in the user information holding unit 111.

  The user check-in information stored in the user information holding unit 111 in the fourth embodiment further includes an item “acceptance category” in addition to the items shown in FIG. Is set. In addition, the user reservation information stored in the user information holding unit 111 in the fourth embodiment further includes the items “reception category” and “reservation visit date and time” in addition to the items shown in FIG. , “Reservation” is set as each value, and the store visit date and time input by the user is set.

  When the reservation information reception unit 260 receives the reservation information, the reservation information reception unit 260 sets the face pass expiration date based on the reservation visit date and time indicated by the reservation information. Typically, the face pass expiry date is set in consideration of the expected lag between the reservation visit date and the actual visit date and the estimated time from when the user visits the store until payment is made. . In addition, the face pass expiration date may be set according to a face pass expiration date setting rule predetermined for each store. For example, a one-hour period before and after the reserved visit date may be set as the face pass expiration date.

  The random number acquisition unit 122 acquires a random number sequence generated by a predetermined random number generator when the reservation information is received, similarly to the case where the check-in information is received. The random number acquisition unit 122 sets the acquired random number sequence data in the user reservation information of the user information holding unit 111. The random number providing unit 124 transmits the random number sequence data acquired by the random number acquiring unit 122 to the purchaser terminal 10 as a response to the notification of the reservation information.

  When the reservation information is accepted, the reservation information providing unit 262 generates store reservation information, and transmits the generated store reservation information to the store terminal 12 by a known push notification method. In addition to the items of the store check-in information in FIG. 4, the store reservation information includes an item “acceptance classification” (value is “reservation”) and an item “store reservation date / time” (value is the store reservation date and time indicated by the reservation information). including. In addition to the items of the store check-in information in FIG. 4, the item “reception classification” (value is “check-in”) is also included in the store check-in information that the check-in information providing unit 126 transmits to the store terminal 12. To be included.

  FIG. 24 is a block diagram showing a functional configuration of the store terminal 12 of FIG. The store terminal 12 according to the fourth embodiment further includes a reservation information holding unit 270 and a reservation information update unit 272. The reservation information holding unit 270 holds attribute information related to a user who has made a store visit to the store, that is, the above-described store reservation information. As described above, the store reservation information includes, in addition to the items of the store check-in information in FIG. 4, the item “reception category” (value is “reservation”) and the item “visit date / time” (value is the user). Store reservation date and time set by.

  The reservation information update unit 272 corresponds to the check-in information update unit 70, accepts store reservation information transmitted from the trading support server 14, and stores it in the reservation information holding unit 270. In other words, the face photograph of the user who made a visit reservation for the store and the reservation visit date and time are acquired from the trading support server 14 and recorded in the reservation information holding unit 270.

  The sales support screen display unit 66 according to the fourth embodiment displays a purchaser selection screen on the touch panel 50 as a product sales support screen. The purchaser selection screen is a screen that allows a store salesperson to select a facial photograph of a purchaser who purchases a product or service from among the facial photographs of a purchaser who has already been checked in or reserved for visiting the store. In the fourth embodiment, the purchaser selection screen is displayed after the login screen to the trading support server 14 is displayed and before the menu selection screen is displayed. In other words, after logging into the trading support server 14, the purchaser selection screen is displayed as the top screen of the product sales support screen. As a modification, it may be displayed in the face pass settlement designation area 184 of the accounting screen 180 as in the first embodiment.

  25 and 26 show the purchaser selection screen. The sales support screen display unit 66 displays both the store check-in information stored in the check-in information holding unit 54 and the store reservation information stored in the reservation information holding unit 270 side by side on the purchaser selection screen 280. . Specifically, in the case of store check-in information, the character string “check-in” is set in the reception section field, and the face photo image and name of the checked-in user are set in the planned visitor field. In the case of store reservation information, the character string “Reservation” is set in the reception section, the face photo image and name of the user who has made a reservation are set in the photo column, and the reservation visit time is set in the reservation visit time column. . Here, both the information on the users who have been reserved for the store visit and the information on the users who have already been checked in are displayed, but only the former is displayed if the store reservation is required in advance.

  The sales support screen display unit 66 arranges the user information that has been reserved for the store (that is, the reservation information for the store) in ascending order of the reserved visit date and time, and the period near the reserved visit date and time (in the embodiment, before and after the store reservation date and time). 1 hour) only on the purchaser selection screen 280. In other words, the face photograph of the user who has made a reservation for visiting the store is displayed on the purchaser selection screen 280 at least for a predetermined period including the reservation visit date and time, and is switched to be hidden after that period.

  The timing of starting and ending the display of the user information reserved for visiting the store on the purchaser selection screen 280 may be arbitrarily determined by the store authority and input to the store terminal 12. The sales support screen display unit 66 of the store terminal 12 makes the store visit reservation according to the start timing (for example, one hour before the reservation visit date and time) and the end timing (for example, one hour after the reservation visit date and time) designated by the store authority. The display start and display end of the used user information may be controlled.

  In addition, it is desirable that the display of the user information reserved for visiting the store on the purchaser selection screen 280 starts and ends at a timing corresponding to the face pass expiration date set by the trading support server 14. For example, the store terminal 12 may upload the information to the buying and selling support server 14 when accepting the input of the start timing and the end timing by the store authority. The trading support server 14 stores the period from the start timing to the end timing in association with the store of the upload source as a setting criterion for the face pass expiration date, and subsequently stores the face pass expiration date of the user who made a reservation at the store. The criteria may be applied when setting.

  Further, the sales support screen display unit 66 displays the checked-in user information (that is, the check-in information for the store) in ascending order of the check-in date and time (that is, the order in which the check-in information for the store is notified from the trading support server 14). Display them side by side. Also, unlike user information that has been reserved for store visits, it is not hidden as time passes. As a modification, as described in the eleventh modification and the twelfth modification of the first embodiment, purchased check-in user information is also purchased with the elapse of a predetermined period (for example, the face pass has expired). It may be hidden on the person selection screen 280. Of course, the setting criteria for the face pass expiration date for the checked-in user may be determined by the authorized person in the store as described above.

  FIG. 25 shows the display content of the purchaser selection screen 280 at 11:45 on a certain day. In the figure, among the reserved users, “Jiro Hoshino” and “Hanako Nomura” are displayed with a reservation visit time of 10:45 to 12:45 on that day. Checked-in user “Sakura Ueno” is a user who checked in before “Jiro Hoshino” is displayed. In other words, the check-in date and time is “Jiro Hoshino” 's reserved visit time -1 hour earlier Therefore, it is displayed higher than “Jiro Hoshino”. In addition, the checked-in user “Taro Nogami” is a user who checked in after “Hanako Nomura” is displayed. In other words, the check-in date and time is “1 hour later than the reservation visit time of“ Hanako Nomura ”. Because of this, it is displayed below “Hanako Nomura”.

  FIG. 26 shows the display content of the purchaser selection screen 280 at 13:15 after the display of FIG. In the figure, “Hanako Nomura”, whose reserved visit time is within the range of 12:15 to 14:15 of the day among the reserved users, is displayed, but one hour or more has passed since the reserved visit time. “Jiro Hoshino” is not displayed. Two of the checked-in users continue to display.

  The operation of the commodity trading system 100 having the above configuration will be described. Hereinafter, characteristic operations in the fourth embodiment will be described, and description of the operations described above in the description of the first to third embodiments will be omitted as appropriate.

  The user activates a product purchase support application on the purchaser terminal 10 and selects a store visit reservation function. The service information acquisition unit 38 of the purchaser terminal 10 acquires data to be displayed on the store visit reservation screen, for example, data related to a reservation type store, from the sales support server 14. The reservation screen display unit 250 of the purchaser terminal 10 sequentially displays a log-in screen, a service provider selection screen, and a store selection screen as store visit reservation screens, and then stores the detailed information of the stores selected on the store selection screen. Display the details screen.

  When face pass settlement is desired, the user inputs a reservation execution operation (for example, a tap operation or a flick operation with respect to the reservation execution button) after entering the store visit date and time in a predetermined field. By this reservation execution operation, the user promises to visit the store at the designated store visit date and time, and the user information is notified to the store to be visited as will be described later. When the reservation execution operation is detected, the reservation information notifying unit 252 of the purchaser terminal 10 transmits the reservation information to the trading support server 14. The reservation information receiving unit 260 of the trading support server 14 stores the received reservation information in the user information holding unit 111 as user reservation information.

  The random number acquisition unit 122 of the trading support server 14 acquires a new random number sequence when the reservation information is received and records it in the user reservation information, and the random number providing unit 124 purchases the data of the random number sequence. To the person terminal 10. When a random number sequence is received from the trading support server 14 as a response to the reservation information notification, the one-time code generation unit 42 of the purchaser terminal 10 generates a confirmation code according to the random number sequence. The reservation screen display unit 250 displays a reservation completion screen indicating that the store visit reservation has been completed, and displays a confirmation code in the screen. The user looks at the reservation completion screen displayed as a response to the reservation execution operation, recognizes the confirmation code, and visits the store in the period near the reservation visit time.

  Further, when the reservation information is received from the purchaser terminal 10, the reservation information providing unit 262 of the sales support server 14 reserves the store based on the user registration information and the user reservation information stored in the user information holding unit 111. Generate information. Then, the store reservation information is transmitted to the store terminal 12. The reservation information update unit 272 of the store terminal 12 acquires the store reservation information provided from the trading support server 14 and stores it in the reservation information holding unit 270.

  The store salesperson activates the product sales support application at the store terminal 12 and completes the login to the sales support server 14. The sales support screen display unit 66 of the store terminal 12 typically uses a purchaser selection screen 280 that includes a list of face photos and names of users who have made reservations at the store and checked-in users as a top screen after login. Always display. The sales support screen display unit 66 causes the purchaser selection screen 280 to display only information on users who satisfy the condition that the current time is within a predetermined period before and after the reservation visit time, for users who have already made a visit reservation. The store salesperson sees the purchaser selection screen 280, recognizes a customer who has a high possibility of coming to the store, and prepares for hospitality optimized for each customer, so-called individual customer correspondence.

  The subsequent steps are the same as those described in the first embodiment. For example, if a user who has made a reservation for a store visit or a user who has already checked in visits a store, decides the product or service to be purchased and declares the name to the store salesperson, the store salesperson confirms the user's face and name. Then, the user image matching the face and name is selected on the purchaser selection screen 280. The store salesperson selects an accounting menu on the menu selection screen, selects a product or service to be purchased by the user on the product selection screen, and selects face pass settlement on the accounting screen. The store sales person accepts the confirmation code declaration from the user, inputs the reported confirmation code to the face pass settlement screen, and instructs execution of the settlement process. The store terminal 12 transmits a settlement request including the confirmation code and the store ID to the trading support server 14. Based on the reservation information received from the purchaser terminal 10, the sales support server 14 stores information for collating the confirmation code and the store ID in association with each other. The trading support server 14 performs a matching process based on the combination of the confirmation code and the store ID specified in the settlement request, and permits or rejects the credit card settlement of the product or service price according to the matching result. . If permitted, the trading support server 14 executes credit card settlement in cooperation with the external settlement server 16.

According to the commodity trading system 100 of the fourth embodiment, in addition to the effects exhibited by the commodity trading system 100 of the first to third embodiments, the following effects are exhibited.
That is, in the case of a reservation-type store that accepts a store visit reservation by a user, the merchandise sales system 100 executes a face pass settlement preparation process when the store visit reservation is made by the purchaser. Thereby, the face pass settlement in the reservation type store can be realized without deteriorating the convenience of the user who has reserved the store visit. In other words, the application range of face pass settlement can be suitably extended to reservation-type stores.

  Moreover, according to the merchandise sales system 100, the display period of the user information that has been reserved for the store visit on the purchaser selection screen 280 of the store terminal 12 is limited to a predetermined period including the reserved visit time. This makes it easy to present only the users who have a high possibility of coming to the store at the present time among the plurality of users who have made reservations for the store visit to the store salesperson. For example, it is possible to support the provision of hospitality optimized for individual customers by a store salesperson, and it is possible to support easy selection of a facial photograph on the purchaser selection screen 280 even if there are many reserved users.

  The fourth embodiment has been described above. This embodiment is an exemplification, and it will be understood by those skilled in the art that various modifications can be made to combinations of the respective constituent elements and processing processes, and such modifications are also within the scope of the present invention. is there. A modification is shown below.

A first modification regarding the fourth embodiment will be described.
In the above embodiment, the reservation information of the user is transmitted in the order of purchaser terminal 10 → purchase support server 14 → store terminal 12. As a modification, the user reservation information may be transmitted from the store terminal 12 to the buying and selling support server 14. For example, when a user makes a reservation for a store visit by calling the store, or when a user makes a store reservation by accessing the store website, the store reservation is made by offline means such as a letter or face-to-face This is the case.

  In this modification, the store terminal 12 further includes a reservation information acquisition unit and a reservation information notification unit corresponding to the reservation information notification unit 252 of the purchaser terminal 10 of the embodiment. The reservation information acquisition unit acquires the user's reservation information input by the person in charge of the store to the terminal, or acquires the user's reservation information from the store's web server or database, and stores it in the reservation information holding unit 270. Record. The reservation information notifying unit transmits the reservation information acquired by the reservation information acquiring unit to the trading support server 14.

  Also in this modified example, the random number providing unit 124 of the buying and selling support server 14 provides the purchaser terminal 10 by providing the purchaser terminal 10 with a random number sequence from which the user confirmation code is generated (such as a push notification). It is desirable to present a confirmation code to the user via The sales support screen display unit 66 of the store terminal 12 uses the reservation information stored in advance in the reservation information holding unit 270 to display the user information that has been reserved for the store visit on the purchaser selection screen 280.

A second modification example related to the fourth embodiment will be described.
In the above embodiment, the display start of the reserved user information on the purchaser selection screen 280 of the store terminal 12 and the display end, in other words, the update of the content of the purchaser selection screen 280 is controlled by the store terminal 12 itself. did. As a modification, the buying and selling support server 14 may control the display start and display end of the reserved user information on the purchaser selection screen 280.

  For example, the sales support server 14 may further include a purchaser information display instruction unit. The purchaser information display instructing unit constantly manages the relationship between the reserved visit time of the reserved user and the current time, and displays the reserved user information on the purchaser selection screen 280 which is one hour before the reserved visit time. Data for instructing to start may be transmitted to the store terminal 12. In addition, data indicating that the reserved user information that has passed one hour from the reserved visit time is not displayed on the purchaser selection screen 280 may be transmitted to the store terminal 12.

  As another aspect, as mentioned in the fourth modification of the first embodiment, the sales support server 14 generates the data of the web page of the sales support screen by itself and provides it to the store terminal 12. It may be displayed. In this case, the buying and selling support server 14 may update the content of the purchaser selection screen 280 as the sales support screen based on the reservation visit times of the plurality of reserved users. Specifically, the buying and selling support server 14 adjusts the reserved user information to be displayed on each of the plurality of store terminals 12 according to the current time, so that the data on the purchaser selection screen 280 for each store is obtained. You may update sequentially. Then, the latest purchaser selection screen 280 data for each store may be provided to each store terminal 12.

  Although related to the first modification and the second modification described above, the visit reservation of the user may be registered using a known web. For example, the store web server or the buying and selling support server 14 may provide the purchaser terminal 10 with a web page showing a reservation screen for store visit reservation to a store (hotel, restaurant, etc.). The user completes the reservation by inputting the store visit date / time, the number of customers and the like to the web page and transmitting it to the store web server or the sales support server 14. Here, “Face Pass” can be selected as a payment method on the web page of the reservation screen. When the user selects a face path and inputs a reservation operation to the purchaser terminal 10, the store terminal 12 is a face that is a list of face photographs of the user for the period of the reservation visit time ± 1 hour by the mechanism described above. Display the pass payment list.

A third modification regarding the fourth embodiment will be described.
In the above-described embodiment, both store reservation user information and check-in user information are mixedly displayed in the same list on the purchaser selection screen 280 at stores that accept both store visits and check-ins. However, various display modes of user information are conceivable and are not limited to the display modes of the embodiments. For example, the user information that has been reserved for visiting the store and the user information that has been checked in may be displayed in a separate list, arranged in ascending order of the reserved store visit date and time, and in ascending order of the check-in date.

  In general, it is considered that a user who has made a reservation to visit a store is more likely to visit the store than a user who has checked in. Therefore, when both the visit reservation reserved user information and the checked-in user information are displayed in the same list on the purchaser selection screen 280, the store is visited at a position that is assumed to have higher visibility, for example, at the top of the list. Reserved user information may be displayed. In other words, the checked-in user information may always be displayed at the bottom of the list regardless of the check-in date and time. In addition, when displaying the visitor reserved user information and the checked-in user information in different lists, the list of the user who has reserved the store visit is assumed to be relatively highly visible on the screen. In addition, it may be displayed in a mode (size, color, etc.) with relatively high visibility.

A fourth modification regarding the fourth embodiment will be described.
In the above embodiment, user information that has passed a predetermined period from the reservation visit date and time is not displayed on the purchaser selection screen 280. As a modified example, the sales support screen display unit 66 continues to display the user information that has passed a predetermined period from the reservation visit date and time, and displays the display position in another list in the purchaser selection screen 280. (Slice list) or a screen different from the purchaser selection screen 280. According to this modification, although the store is not visited at the reservation visit time, it is easy for the store salesperson to identify at least the user who made the store visit reservation, and the response to the user can be supported. In addition, it is desirable to display the information of the user whose detection date and time that the predetermined period has elapsed from the reservation visit date and time is in a position or mode that is assumed to have relatively high visibility. This is because the possibility that the user visits will decrease with the passage of time.

A fifth modification example related to the fourth embodiment will be described.
In the above embodiment, in order to improve the safety of the face pass settlement triggered by the visit reservation to the store, a confirmation code that can only be known by the user is paid out as in the first embodiment. As a modification, the store that accepts the reservation may pay out the reservation number to the user, and this reservation number may be used instead of the confirmation code. The store terminal 12 (or the store web server) may directly notify the purchaser terminal 10 of the reservation number, or may notify the purchaser terminal 10 of the reservation number via the sales support server 14. The purchaser terminal 10 may display the accepted reservation number instead of the confirmation code. As described above, it is also suitable when the web page of the reservation screen is provided to the purchaser terminal 10, and even if the reservation number is notified to the user as a response to the reservation registration specifying the face pass settlement. Good.

  The store terminal 12 may display the reservation number of each user together with the list of user face photos. When the user declares the name and the reservation number at the store, the store salesperson may input a settlement instruction if the user's face / name / reservation number matches the list on the store terminal 12. Similarly to the case of the confirmation code, the store salesperson selects the user's face photo and inputs the reservation number to the store terminal 12, and sends a settlement request including the reservation number from the store terminal 12 to the sales support server 14. You may send it. The trading support server 14 may acquire the reservation number from the store apparatus in advance and store it in association with the user. The transaction support server 14 performs a matching process between the reservation number stored in advance and the reservation number specified in the settlement request. May be executed. As a further modification, face pass settlement using only a face photo and a name may be executed without using either a confirmation code or a reservation number. In other words, face pass settlement may be executed in which the store salesperson confirms the face and name of a user who has already been checked in or reserved, and completes identity verification. The reservation number only needs to be information that can uniquely identify a specific reservation by a specific user among a plurality of reservations by a plurality of users, and may be any combination of numbers, letters, symbols, and the like.

A sixth modification example related to the fourth embodiment will be described.
The product purchase or service receipt patterns proposed in the first to fourth embodiments are as follows: 1) store reservation or check-in (declaration of visit), 2) product purchase or service receipt at the store, 3) It was face pass settlement. However, the technical idea described in the present specification is not limited to this pattern, and can be applied to other patterns. Hereinafter, two deformation patterns will be described. Of course, even if not specifically mentioned below, it is a matter of course that the confirmation code is paid out and collated in the same manner as in each embodiment by the mechanism described above.

Deformation pattern 1:
1) Store reservation and / or check-in, 2) Face pass settlement (authorization only), 3) Product purchase or service receipt, 4) Face pass settlement (payment). Here, an example of application to a hotel company is shown.

  The user registers an accommodation reservation (for example, the start date and the departure date are specified) to the hotel via the web reservation screen or the application of the purchaser terminal 10. Then, a check-in operation is input at the purchaser terminal 10 before arrival at the hotel on the accommodation start date, and a store visit is declared. Conventionally, this is made to correspond to the check-in that the front man and the guest face each other at the front of the hotel on the accommodation start date. For example, when a check-in operation at the purchaser terminal 10 is notified via the buying and selling support server 14, a hotel frontman or a hotel terminal performs some work / processing when a guest checks in face-to-face. Execute manually or automatically in advance. For example, reservation confirmation, credit card authorization, and room assignment confirmation similar to those in the past may be executed. When the reservation support is accepted or when the check-in is accepted, the buying and selling support server 14 transmits the photograph of the guest's face together with the reservation information to the store terminal 12 (for example, the front terminal of the hotel).

  When the user arrives at the hotel, the reservation confirmation, credit card authorization, and room assignment confirmation have been completed. Therefore, after confirming the user's face and name in the list on the hotel terminal, the hotel frontman only works on the premise of meeting with the guest, such as guidance to the room, distribution of entrance cards and breakfast tickets, etc. Should be implemented. Thereby, the procedure at the time of user arrival can be simplified and the time can be shortened. When the user checks out, the purchaser terminal 10 displays a list of the user's face photos and names corresponding to the departure date, and thereafter executes credit card payment by face pass according to the mechanism described above.

Deformation pattern 2:
1) Store reservation and / or check-in, 2) Face pass settlement, 3) Purchase of goods or receipt of service, 4) Payment of difference (difference) as required. Here, an example of application to a rental car company is shown.

  The user registers a rental car reservation (for example, a use start date and a use end date (return date) are specified) via the web reservation screen or the application of the purchaser terminal 10. Then, before arrival at the rental car office, a check-in operation is input at the purchaser terminal 10 and a store visit is declared. Although this check-in operation is optional, the person in charge at the rental car office will notify the check-in operation at the purchaser terminal 10 via the buying and selling support server 14 until the rental car rental time when the user arrives. You may implement the work for shortening. For example, a check-in user's rental car may be moved to the front of the store, and a check-in user's rental document may be prepared before the user arrives. When the user visits the store, the person in charge confirms the driver's license, and causes the credit card settlement using the face pass to be executed via the store terminal 12 by the mechanism described above.

  When returning the rental car, the user pays a difference (for example, gasoline fee or non-operation charge) as necessary. This differential payment may be a conventional method, but may use face pass settlement. In this case, the purchaser terminal 10 displays a list of the user's face photos and names corresponding to the return date, and executes credit card payment by face pass payment according to the mechanism described above. When a confirmation code is paid out at the time of reservation reception or check-in, and the verification process is executed at the time of face pass settlement, the transaction support server 14 also confirms the confirmation code (transaction and purchase) until the return date even after the credit card settlement at the time of rental car rental. It is desirable that the random number value stored in association with the user by the support server 14 is valid. As a result, the user can use the face pass settlement if the same confirmation code as when the rental car is started is returned at the time of return, thereby improving the convenience of the user.

(Fifth embodiment)
In the fifth embodiment, a commodity trading system that realizes automatic check-in using a known acoustic communication technique will be described. In the third modification of the first embodiment, a configuration has been described in which automatic check-in is performed at a store existing near the purchaser's current location based on GPS positioning information. However, GPS positioning may be difficult in buildings such as shopping malls. Automatic check-in via acoustic communication solves this problem. In addition, it allows automatic check-in to a specific store even if the stores are crowded, and furthermore, the range of sound can be controlled by volume and speaker directivity, so the geographical range of automatic check-in There is also an effect that the control is easy.

  The configuration of the product trading system 100 of the fifth embodiment is the same as that of the product trading system 100 (FIG. 1) of the first embodiment, but further includes an acoustic output device and a conversion server. The sound output device includes a speaker, and the speaker is installed at any indoor or outdoor position, for example, at an elevator hall, an escalator elevator, a shopping street entrance, or the like. The conversion server is connected to the purchaser terminal 10 via a communication network. The conversion server may be implemented as the same server as the sales support server 14.

  The sound output device provides digital information (herein referred to as “acoustic ID”) necessary for acquiring information for automatic check-in from the conversion server via a speaker in a high sound range that is difficult for humans to hear. Outputs a modulated acoustic signal. The acoustic ID includes, for example, identification information of a store that is an automatic check-in destination and an address of the conversion server. A known modulation technique may be used for the modulation of the acoustic ID.

  The conversion server holds the store identification information included in the acoustic ID, the service provider ID for uniquely identifying the store in the face pass payment service, and the store ID in association with each other. When receiving the store identification information from the purchaser terminal 10, the conversion server transmits the service provider ID and the store ID associated with the store identification information to the purchaser terminal 10.

  The purchaser terminal 10 according to the fifth embodiment further includes a microphone and an acoustic analysis unit. The acoustic analysis unit demodulates the acoustic signal detected by the microphone, and acquires an acoustic ID that is digital information included in the sound. A known demodulation technique may be used for this demodulation processing. The acoustic analysis unit transmits the store identification information indicated by the acoustic ID to the conversion server indicated by the acoustic ID, and acquires the service provider ID and the store ID as a response from the conversion server. Then, these pieces of information are passed to the check-in notification unit 40. The check-in notification unit 40 transmits the check-in information specifying the service provider ID and the store ID output by the acoustic analysis unit to the trading support server 14. Thereafter, a series of face pass settlement processes is executed in the same manner as when the user manually performs the check-in operation.

  In addition, if the information required for automatic check-in, for example, the service provider ID and the store ID is a size that fits in the data capacity of the acoustic ID, the acoustic ID itself may include these pieces of information. In this case, access from the purchaser terminal 10 to the conversion server is unnecessary, and the acoustic analysis unit may pass the service provider ID and the store ID directly indicated by the acoustic ID to the check-in notification unit 40.

  In addition, when automatic check-in is performed based on GPS or acoustic communication, processing regarding issuance and verification of confirmation codes may be skipped. For example, the check-in notification unit 40 of the purchaser terminal 10 sets a flag indicating automatic check-in in the check-in information specifying the service provider ID and the store ID output by the acoustic analysis unit, and sends the check-in information to the trading support server 14. You may send it. Further, the one-time code generation unit 42 of the purchaser terminal 10 may skip the issuance of the confirmation code. Further, the trading support server 14 that has detected the flag may skip the random number sequence issuance process and the confirmation code consistency determination process. The manager of the merchandise trading system 100 and the authority of the store decide whether or not to issue / verify the confirmation code in the case of automatic check-in by comparing the convenience of the user and the safety of face pass settlement. May be.

(Sixth embodiment)
In recent years, with the spread of tablet terminals, the use of tablet terminals has begun in the area of corporate activities. As an example of its use, it is conceivable to perform customer service while referring to a customer's purchase history or customer visit history, which is called a customer chart, using a tablet terminal. However, in the past customer service, while maintaining the medical chart information for each customer, it is necessary to have the customer himself / herself identify the customer who actually visited the store or rely on the store clerk's memory. In other words, the present inventor has recognized that there is a situation in which the customer himself is burdened, or it is easy to remain uncertain, and it cannot be said that there is sufficient customer service using the customer chart.

  The inventor of the present invention has focused on the fact that it is possible to identify in advance a user who is scheduled to visit the store by check-in (including store visit reservation) by the user (purchaser, customer). And in addition to using check-in to the store by the user for face pass settlement, he thought there was room to use the check-in for customer service. Specifically, as a sixth embodiment, a merchandise trading system is proposed that provides various information for supporting customer service to the store terminal 12 triggered by a check-in by the user. Also, we propose a merchandise trading system that realizes message exchange between users and sellers, with check-in by users as a trigger for communication between users and sellers.

  FIG. 27 shows a configuration of a commodity trading system according to the sixth embodiment. The merchandise sales system 100 of 6th Embodiment is the structure similar to the merchandise sales system 100 of 1st Embodiment shown in FIG. 1 substantially.

  The trading support server 14 is connected to the database 300. The database 300 stores various information of service providers (for example, product information, store information, customer service memos, etc.) and various types of information of users (for example, face images, authentication history, purchase history). Such information is periodically acquired from the database 302 and the database 304 of an existing EC site (for example, a mail order site of a store on the Internet) or a system for an existing store (for example, a sales management system or a form creation system). 300 may be stored. Moreover, you may refer the data stored in the database 302 and the database 304 in real time as needed. The database 300 corresponds to various data holding units of the trading support server 14 described later.

  The sales support server 14 includes an analysis engine 306. The analysis engine 306 is a software module that refers to the information of each user stored in the database 300 and determines a product or service that should be recommended for purchase to each user in the store. The analysis engine 306 corresponds to a recommended product determination unit 326 of the sales support server 14 described later.

  In the sixth embodiment, the trading support server 14 pays an ID (hereinafter referred to as “check-in ID”) for uniquely identifying a plurality of check-ins and visit reservations by a plurality of users. I will put it out. Upon receiving the check-in information and the visit reservation information from the purchaser terminal 10 or the store terminal 12, the sales support server 14 gives the newly paid-out check-in ID to the user information holding unit 111 (the user of FIG. 6B). In the check-in information) and notifies the purchaser terminal 10 and the store terminal 12 of the check-in ID. The check-in ID may be configured as a combination of a service provider ID, a store ID, and a user ID.

  FIG. 28 is a block diagram showing a functional configuration of the purchaser terminal 10 of FIG. The purchaser terminal 10 of the sixth embodiment includes a message reception unit 310, a message notification unit 312 and a talk information acquisition unit 314 in addition to the functional blocks of the purchaser terminal 10 of the fourth embodiment. In the drawings subsequent to FIG. 28, functional blocks that are the same as or correspond to the functional blocks described in the first to fifth embodiments are denoted by the same reference numerals, and redundant descriptions are omitted as appropriate.

  The purchase support screen display unit 36 is a screen that shows a list of stores that the user has checked in or reserved for visiting, and a message for selecting a store to which a message should be transmitted from among the stores that have been checked in or reserved for visiting. A transmission destination selection screen is displayed on the touch panel 20. When the purchase support screen display unit 36 detects that a specific store has been selected by the user on the message transmission destination selection screen, the purchase support screen display unit 36 displays an input screen for a message to be transmitted on the touch panel 20. The message receiving unit 310 acquires a message character string input by the user on the input screen via the touch panel 20 and the operation detecting unit 26. The message notification unit 312 associates the message character string acquired by the message reception unit 310 with the check-in ID in association with the check-in ID for identifying the check-in selected on the message transmission destination selection screen, and the sale support server. 14 to send.

  The talk information acquisition unit 314 is the latest talk information transmitted from the trading support server 14 and acquires talk information including at least one of the user's message and the store salesperson's message. Record for each store you enter. The purchase support screen display unit 36 causes the touch panel 20 to display the talk information acquired by the talk information acquisition unit 314. Talk information is a message that shows a user's message and a store salesperson's message in chronological order, and is information that shows the conversation contents and conversation history by exchanging message strings between the user and the store salesperson. . The talk information will be described later with reference to FIG.

  FIG. 29 is a block diagram showing a functional configuration of the buying and selling support server 14 of FIG. The sales support server 14 according to the sixth embodiment includes a service support information holding unit 320 and a service support unit 322 in addition to the functional blocks of the sales support server 14 according to the fourth embodiment.

  The customer service support information holding unit 320 stores various types of information (hereinafter collectively referred to as “customer service support information”) for supporting customer service for users who have already been checked in or reserved for visiting a service provider. . The customer service support information can be said to be information indicating the past visits to the store by the user and the past purchases by the user at the store. Based on these results, the information manually recorded by the store salesperson is used. Including. For example, medical record information and customer service memos. It also includes information automatically recorded by the system. For example, purchase history and talk information.

  Furthermore, the customer service support information includes personal information (attribute information) of the user interviewed and recorded by the store salesperson, and the user's personal information (attribute) registered in advance in the sales support server 14 by the user. Information). As mentioned previously, customer support information includes basic user attribute information (name, date of birth, address, occupation, etc.), medical record information (size, preferred style, contraindications, etc.) Purchase history, customer service memo, coupon information, and talk information are included. The customer service support information in the embodiment is information necessary for check-in, information for notifying the store of check-in, for example, user registration information held in the user information holding unit 111, user check-in information Is independent information.

  The customer service support information holding unit 320 holds customer service support information for each service provider and for each user. In the embodiment, customer service support information is held using a service provider ID and a user ID as keys. Therefore, even for the same user, the service support information differs for each service provider. However, the same customer service support information is shared among a plurality of stores operated by the same service provider. The talk information is held in units of check-in (visit reservation), that is, the service provider ID, user ID, and check-in ID are held as keys. Therefore, even if it is the same user and the same store, if the check-in (visit reservation) timing is different, it is held as different talk information.

  The customer service support unit 322 refers to the customer service support information held in the customer service support information holding unit 320 and executes various processes for supporting customer service in the store of the service provider. FIG. 30 is a block diagram showing in detail the customer service support unit 322 of FIG. The customer service support unit 322 includes a customer service support information acquisition unit 324, a recommended product determination unit 326, a customer service support information provision unit 328, a customer service support information update unit 330, a message acquisition unit 332, a talk information update unit 334, A talk information providing unit 336 is included.

  When receiving the check-in information from the purchaser terminal 10, the check-in receiving unit 120 determines a unique check-in ID. Then, by transmitting the check-in ID, the service provider ID indicated by the check-in information, and the user ID to the customer service support unit 322, the customer service support unit 322 is notified that the check-in has been accepted. Reservation information reception part 260 will determine unique reservation ID, if reservation information is received from purchaser terminal 10 or store terminal 12. Then, the reservation ID, the service provider ID indicated by the reservation information, and the user ID are transmitted to the customer service support information holding unit 320 to notify the customer service support unit 322 that the reservation has been accepted. Hereinafter, the reservation ID will be described as a check-in ID.

  Upon receiving notification from the check-in reception unit 120 and the reservation information reception unit 260 that check-in or reservation has been received, the customer service support information acquisition unit 324 is identified by the notified service provider ID and user ID. Support information is acquired from the customer service support information holding unit 320. The customer service support information acquisition unit 324 transmits the acquired customer service support information to the recommended product determination unit 326 and the customer service support information provision unit 328.

  The recommended product determination unit 326 refers to customer service support information for a user who has made a check-in to the store or made a store reservation, and determines a product or service to be recommended for purchase by the user at the store. For example, according to a user's past purchase history, a product or service that is likely to be purchased by the user this time may be estimated. In the recommended product determination / estimation process, a known recommended product determination logic (recommendation engine) may be used. The recommended product determination unit 326 acquires product information indicating a product or service to be recommended to the user from the store information holding unit 112 and transmits the product information to the customer service support information providing unit 328 as recommended product information.

  The customer service support information providing unit 328 transmits customer service support information including the recommended product information received from the recommended product determination unit 326 to the store terminal 12. The customer service support information provision unit 328 transmits customer service support information to the store terminal 12 in association with the service provider ID, user ID, and check-in ID. In the embodiment, the customer service support information providing unit 328 passes the customer service support information to the check-in information providing unit 126 or the reservation information providing unit 262, and receives the customer service support information together with the user check-in information or the store reservation information. Will be provided.

  The customer service support information update unit 330 receives update information for the customer service support information from the store terminal 12. The customer service support information updating unit 330 specifies the customer service support information to be updated from the customer service support information stored in the customer service support information holding unit 320 according to the service provider ID and the user ID specified in the update information. The update information is recorded in the specified customer service support information. The update information indicates, for example, the update contents of the user's basic information, medical chart information, customer service memo, and the like, and includes, for example, newly added contents and the correction results of the previous contents. As described above, the service support information update unit 330 specifies the service support information related to a specific user when the content of the service support information related to the specific user is changed by the service provider, for example, a store salesperson. . Then, the service support information so far is updated so that the service support information reflecting the change contents on the service provider side is obtained.

  The settlement processing unit 132 notifies the customer service support information providing unit 328 of information (including service provider ID and user ID) indicating a product or service newly purchased by the user. The customer service support information updating unit 330 updates the purchase history of the customer service support information according to the information notified from the settlement processing unit 132. That is, by adding information indicating a product or service newly purchased by a certain user to the previous purchase history, the purchase history of the user is automatically updated.

  The message acquisition unit 332 acquires the message character string and the check-in ID transmitted from the purchaser terminal 10 and the store terminal 12. The talk information update unit 334 updates the talk information stored in the customer service support information holding unit 320 based on the message character string received by the message acquisition unit 332. For example, the message character string received by the message acquisition unit 332 is added as the latest message in time series to the talk information specified by the check-in ID among the talk information stored in the customer service support information holding unit 320. .

  The talk information providing unit 336 is updated by receiving a notification that the talk information has been updated from the talk information updating unit 334 or by monitoring the update status of the talk information stored in the customer service support information holding unit 320. Talk information is detected. The talk information providing unit 336 transmits the updated talk information data to the purchaser terminal 10 and the store terminal 12. Thereby, the talk information is displayed on the product purchase support screen of the purchaser terminal 10 and the product sales support screen of the store terminal 12. Note that whether the entire talk information is transmitted or whether an update difference is transmitted may be appropriately designed.

  FIG. 31 is a block diagram showing a functional configuration of the store terminal 12 of FIG. In addition to the functional blocks of the store terminal 12 of the fourth embodiment, the store terminal 12 of the sixth embodiment includes a customer service support information holding unit 340, a customer service support information acquisition unit 342, and a customer service support information update unit. 346, a message reception unit 348, a message notification unit 350, and a talk information acquisition unit 352. The sales support screen display unit 66 includes a customer service support information display unit 344.

  The customer service support information holding unit 340 holds the customer service support information including the recommended product information transmitted from the trading support server 14 in association with the service provider ID, the user ID, and the check-in ID. In other words, customer service support information is held for each user who has checked in to the store. The customer service support information acquisition unit 342 acquires the service provider ID, user ID, check-in ID, and customer service support information transmitted from the trading support server 14, and stores them in the customer service support information holding unit 340.

  The customer service support information display unit 344 causes the touch panel 50 to display a customer service support screen, which is a store-oriented screen for supporting customer service for users who have made a check-in or store visit reservation, as one of the product sales support screens. As will be described in detail later, the customer service support information display unit 344 displays a list of face photos and names of users who have been reserved for check-in and store visits on the check-in list of the customer service support screen. The customer service support information display unit 344 acquires customer service support information for the customer serving user selected by the store sales person in the check-in list from the customer service support information holding unit 340 and displays it on the customer service support screen.

  When the store salesperson edits the customer service support information on the customer service support screen, the customer service support information update unit 346 transmits update information indicating the content of the customer service support information after the editing is completed to the transaction support server 14 to support the transaction. The edited contents are reflected in the customer service support information held by the server 14. The customer service support information update unit 346 transmits update information to the trading support server 14 in association with the service provider ID and the user ID.

  The customer service information display unit 344 causes the touch panel 50 to display talk information indicating messages exchanged between the user and the store salesperson for the user selected by the store salesperson in the check-in list. Further, the customer service support information display unit 344 causes the touch panel 50 to display an input screen for a message to be transmitted to the user. The message receiving unit 348 acquires the message character string input by the store salesperson via the touch panel 50 and the operation detecting unit 58 on the input screen.

  The message notification unit 350 identifies the check-in ID of the user who is the message transmission destination. For example, the check-in ID of the user who is the display target on the customer service support screen on which an operation for instructing the display of the message input screen has been performed is specified as the check-in ID of the user as the message transmission destination. The message notification unit 350 transmits the message character string acquired by the message reception unit 348 to the trading support server 14 in association with the specified check-in ID. The talk information acquisition unit 352 is the latest talk information transmitted from the trading support server 14 and acquires talk information including at least one of a user message and a store salesperson message. The customer service support information display unit 344 causes the touch panel 50 to display the talk information acquired by the talk information acquisition unit 352.

  The operation of the commodity trading system 100 having the above configuration will be described. Hereinafter, characteristic operations in the sixth embodiment will be described, and description of the operations described above in the description of the first to fifth embodiments will be omitted as appropriate. Here, an example of check-in is shown, but the same operation is performed in the case of store visit reservation as described in the fourth embodiment. Here, the user manually inputs a check-in operation. However, as described in the modification of the first embodiment, the fifth embodiment, etc., the current position, sound, etc. The same operation is executed when triggered by the original automatic check-in.

  The user activates the product purchase support application on the purchaser terminal 10 and selects a store to be checked in. The check-in notification unit 40 of the purchaser terminal 10 transmits check-in information to the sales support server 14. Similarly to the other embodiments, the purchase support screen display unit 36 of the purchaser terminal 10 displays the confirmation code generated by the one-time code generation unit 42 on the screen as a response to the check-in operation by the user. Let

  When the trading support server 14 receives the check-in information, the customer service support information acquisition unit 324 acquires the customer service support information for the user who has checked in the store from the customer service support information holding unit 320. The recommended product determination unit 326 determines a recommended product for the checked-in user. When the check-in information providing unit 126 transmits the check-in information for the store indicating the checked-in user to the store terminal 12, the customer service support information providing unit 328 includes the service support information including recommended products for the checked-in user. Is transmitted to the store terminal 12. The check-in information update unit 70 of the store terminal 12 stores the check-in information for the store provided from the sales support server 14 in the check-in information holding unit 54, and the customer service support information acquisition unit 342 of the store terminal 12 The service support information provided from the server 14 is acquired and stored in the service support information holding unit 340. The customer service support information holding unit 340 stores customer service support information for each user in such a manner that each user who has checked in can be identified.

  The customer service support information display unit 344 of the store terminal 12 causes the touch panel 50 to display a customer service support screen as a sales support screen. Hereinafter, a plurality of types of customer service support screens for presenting a plurality of types of customer service support information to a store sales person will be described with reference to each of FIGS.

  FIG. 32 shows one aspect of the customer service support screen. This figure shows the top screen of the customer service support screen 360 that is displayed first after the store sales person logs in to the sales support server 14. The customer service support screen 360 includes a menu icon 362 for the store salesperson to select a desired menu. The customer service support information display unit 344 displays on the customer service support screen 360 a check-in list 364 that displays a list of face images and names of users who are currently checking in at the store. Each time the store check-in information is notified from the sales support server 14, the customer service support information display unit 344 sequentially adds and displays the user's face photo and name indicated by the store check-in information to the check-in list 364. Let

  The check-in list 364 corresponds to the face pass settlement designation area 184 of the first embodiment, but is displayed on the customer service support screen before settlement in the present embodiment. The store salesperson uses a specific use from the check-in list 364 in order to examine the manner of customer service (for example, the content of the voice call or precautions) before or when the user actually visits the store. (Hereinafter referred to as “selected user”). Therefore, it can be said that the customer service support screen 360 of FIG. 32 is a selection screen for causing the seller to select an image of the customer who purchases the customer.

  In the check-in list 364, the customer service support information display unit 344 refers to the customer service support information (basic information and talk information) for the user, and determines the presence / absence of characteristic attribute information and events related to the user. Then, an additional image indicating the presence of characteristic attribute information or an event is displayed in association with each user. The additional image includes a cake image indicating that the birthday is close, a ring image indicating that the wedding anniversary is close, and a letter image indicating that a new message has arrived. For example, the customer service support information display unit 344 accepts a notification from a talk information acquisition unit 352 described later, or monitors the update status of the talk information in the customer service support information holding unit 340, whereby the customer service support information display unit 344 It may be detected that the talk information has been updated, and a letter image may be displayed in association with the user. In addition, the purchase support server 14 may execute the necessity determination and setting processing of the additional image.

  The customer service support information display unit 344 displays a customer information screen as one aspect of the customer service support screen when a store sales person taps a display location of a specific user in the check-in list 364 of FIG. Specifically, the customer service support screen 360 of FIG. 33 is displayed as the top screen of the customer information screen regarding the selected user. As shown in FIG. 33, the customer service support information display unit 344 displays a summary of a plurality of types of attribute information related to the selected user on the top screen of the customer information screen. Also, recommended product information for the selected user is extracted from the customer service support information, and the recommended product information is also displayed. Note that a category icon 366 for the store salesperson to select a category of customer information is displayed on the customer information screen.

  34 to 37 also show customer information screens as one aspect of the customer service support screen. When “basic information” of the category icon 366 is selected, the customer service support information display unit 344 displays the customer service support screen 360 of FIG. That is, a customer information screen showing basic information in the customer service support information is displayed. When the “karte” of the category icon 366 is selected, the customer service support information display unit 344 displays the customer service support screen 360 of FIG. That is, the customer information screen showing the chart information in the customer service support information is displayed. When the “purchasing history” of the category icon 366 is selected, the customer service support information display unit 344 displays the customer service support screen 360 of FIG. That is, a customer information screen showing purchase history information in the customer service support information is displayed. When “customer memo” is selected in the category icon 366, the customer service support information display unit 344 displays the customer service support screen 360 of FIG. That is, the customer information screen showing the customer service memo in the customer service support information is displayed.

  Although not shown, when “My Page” of the category icon 366 is selected, the customer service support information display unit 344 displays coupon information held by the selected user and customer information indicating recommended products for the selected user. Display the screen. When “talk” of the category icon 366 is selected, the customer service support information display unit 344 displays the talk information between the selected user and the store salesperson.

  The customer service support screen 360 of FIGS. 34, 35, and 37 is provided with an edit icon 368 for the store sales person to edit the contents of the basic information, the chart information, and the customer service memo, respectively. When the store salesperson taps the edit icon 368, the customer service support information display unit 344 displays an edit screen of customer service support information (customer information corresponding to the screen). When the store salesperson edits the customer information and performs a predetermined confirmation operation, the customer service support information update unit 346 of the store terminal 12 records update information indicating the editing result by the store salesperson in the customer service support information holding unit 340. , The edited result is reflected in the customer service support information so far. At the same time, the customer service support information update unit 346 transmits the update information to the sales support server 14 and reflects the edited result by the store sales staff in the service support information held by the sales support server 14.

  As described above, in the merchandise sales system 100 according to the present embodiment, in addition to the user's face photo and name, the customer service is triggered by the check-in for personal identification (and store reservation), which is the premise of face pass settlement. Support information is provided to the store terminal 12. The store terminal 12 displays the information of the checked-in user on the customer service support screen at the previous stage of product purchase. In addition to the combination of the face photo and name of the user who has already been checked in, customer service support information regarding the user is displayed.

  As a result, the store salesperson can learn in advance the relevant information of the user who has checked in, without having to give the user the store visitor, and without relying on the store salesperson's past memories, It can support the realization of effective “individual customers” such as product recommendations. In addition, the customer service support screen always displays a combination of the face photo and name of a user who has already checked in, making it easier for store sales staff to remember the user's face and name as a pair. It can further support the improvement of strength. The customer service support screen may be displayed on the POS terminal of the store or may be displayed on a general-purpose tablet terminal installed in the store. In other words, the customer service support screen is not limited to the screen displayed on the POS terminal of the store.

  As shown in FIGS. 36 and 37, customer information can be shared among a plurality of stores in the same service provider, and customer information edited in one store can be referred to in another store. Thereby, information sharing among a plurality of stores in the same service provider can be promoted, and effective customer service to the same user can be further supported by collective intelligence. Note that, even for different service providers, for a plurality of service providers that have a cooperative relationship such as business alliances, the buying and selling support server 14 provides information indicating association for information sharing, for example, a plurality of service provider IDs. You may hold | maintain the matched information. In this case, it is possible to provide the same customer service support information to the stores of each of the plurality of service providers associated with the service provider ID, thereby supporting the sharing of customer information.

  As described above, the same operation is performed when the user makes a reservation to the store, but in this case, the user may be displayed in the check-in list immediately after the store reservation, Like a form, you may make it display a user on a check-in list in the predetermined period before and behind a reservation visit date. In the case of a store visit reservation, the date and time when the reservation is applied may be significantly different from the actual store visit date and time, but in this case as well, it is easy to suppress an increase in the number of people displayed in the check-in list. In addition, when a store accepts both check-in and store visits, when displaying users in the check-in list for a predetermined period before and after the visit date, the users who have made a store reservation are given priority over the check-in users. May be. For example, the user who has made a reservation to visit the store may be displayed in a relatively high position on the check-in list, or may be highlighted so that the user can stand out and be easy to see. This is because it is considered that the store visitor is more likely to visit the store.

  FIG. 38 also shows an aspect of the customer service support screen. The customer service support information display unit 344 displays the talk list 370 when “communication” of the menu icon 362 is selected on the top screen of the customer service support screen shown in FIG. The customer service support information display unit 344 causes the talk list 370 to display a link to talk information including a face photo / name / message of the user who sent the message to the store among the checked-in users.

  FIG. 39 also shows an aspect of the customer service support screen. When a specific user is selected in the talk list 370 of FIG. 38, the customer service support information display unit 344 displays a talk screen 372 that shows talk information between the user and the store salesperson. In addition, when “communication” of the menu icon 362 is selected on the customer information screen shown in FIG. 33 to FIG. 37, the user who is the display target of the customer information, in other words, the check-in list of FIG. The talk screen 372 of the user selected in 364 is displayed. Although not shown, a message creation icon may be further arranged on the talk screen 372. When the icon is selected, the customer service support information display unit 344 allows the store sales person to input a new message to the user. The message creation screen may be displayed.

Here, the operation of sending and receiving messages between the purchaser terminal 10 and the store terminal 12 will be described.
When a user who has already checked in to the store inputs an operation for instructing the creation of a message to the store, the purchase support screen display unit 36 of the purchaser terminal 10 displays a message input screen. The message reception unit 310 acquires the message character string input by the user, and the message notification unit 312 transmits the message character string to the trading support server 14. The message acquisition unit 332 of the trading support server 14 receives the message character string transmitted from the purchaser terminal 10, and the talk information update unit 334 adds the message character string to the talk information specified by the check-in ID. Then, the talk information providing unit 336 transmits the updated talk information to the purchaser terminal 10 and the store terminal 12.

  The talk information acquisition unit 352 of the store terminal 12 receives the talk information transmitted from the trading support server 14. The received talk information is recorded in the customer service support information specified by the check-in ID among the customer service support information stored in the customer service support information holding unit 340, that is, the customer service support information related to the user of the message transmission source. In other words, new talk information is overwritten and saved. The customer service information display unit 344 of the store terminal 12 displays the selected user's talk information on the selected user's talk screen 372 in the check-in list. When the store sales person inputs a reply message on the message creation screen, the message reception unit 348 receives the reply message, and the message notification unit 350 transmits the reply message to the trading support server 14. Thereafter, the reply message is reflected in the talk information in the same manner as described above, and the updated talk information is transmitted to the purchaser terminal 10 and the store terminal 12 for viewing by the user and the store salesperson.

  As described above, in the product trading system 100 according to the present embodiment, the check-in and the store visit reservation by the user are regarded as the start of communication between the user and the store, and message transmission / reception is realized between the two. In the talk list 370 and the talk screen 372, the face photograph and name of the user provided to the store terminal 12 upon check-in are displayed. Thereby, before the user who has already checked in actually visits the store, the user and the store salesperson can interact with each other, promote mutual communication, and support the improvement of customer service at the store. In addition, since messages (talk information) are managed in units of check-in, even when a service provider operates a plurality of stores, the user can directly exchange information with a person in charge at a store scheduled to visit.

  40 to 42 also show customer service support screens. Each of FIG. 40 to FIG. 41 corresponds to FIG. 9 to FIG. 11 described in the first embodiment. The customer service information display unit 344 displays the cart screen 374 of FIG. 40 when the menu icon 362 “sale” is selected while a specific user is selected in the check-in list 364 or the talk list 370. . For example, this is a case where “sales” of the menu icon 362 is selected on the customer service support screen 360 of FIGS. 33 to 37 and 39.

  In addition, the customer service information display unit 344 displays the accounting screen 376 of FIG. 41 when a product or service to be purchased is selected on the cart screen 374 and an accounting procedure is selected. Further, when “Face Pass Payment” is selected from the payment method icons 378 on the transaction screen 376, the customer service support information display unit 344 displays the face pass payment screen 380 in FIG. The store sales person inputs the confirmation code reported by the user in the confirmation code input field 382 of the face pass payment screen 380. When the confirmation button 384 is tapped, electronic payment of merchandise price / service price is executed in cooperation with the store terminal 12 and the buying and selling support server 14 as in the other embodiments.

  The sixth embodiment has been described above. This embodiment is an exemplification, and it will be understood by those skilled in the art that various modifications can be made to combinations of the respective constituent elements and processing processes, and such modifications are also within the scope of the present invention. is there. A modification is shown below.

A first modification of the sixth embodiment will be described.
In the above embodiment, the cake image, the ring image, and the letter image are exemplified as the additional images in the check-in list 364 of the customer service support screen 360. However, other image objects indicating the presence of characteristic attribute information and events related to the user. May be displayed. As an example, an additional image indicating a user's loyalty level (platinum customer, gold customer, silver customer, etc.) for a specific store or a specific service provider may be displayed. In this case, the store terminal 12 or the sales support server 14 may determine the loyalty level of the user based on the user's past purchase record or store visit record. For example, the user's loyalty level is determined by comparing one or more items such as store visit frequency, the number of products purchased in the past, the total amount of product purchases, the purchase frequency, etc. with a predetermined threshold for each loyalty level. May be.

A second modification of the sixth embodiment will be described.
In the above embodiment, the customer service support information related to the user is provided from the trading support server 14 to the store terminal 12 at the time of user check-in, but the customer service support information may be provided at another timing. For example, only the check-in information for a store (for example, a face photo and a name) may be provided at the time of user check-in, and the check-in list 364 may be displayed on the store terminal 12. Then, when a specific user is selected in the check-in list 364, customer support information of the selected user may be provided on demand. Specifically, the customer service support information acquisition unit 342 of the store terminal 12 transmits a request for providing customer service support information specifying the service provider ID of the store and the user ID of the selected user to the trading support server 14. May be. The customer service support information providing unit 328 of the sales support server 14 may transmit the customer service support information specified by the service provider ID and the user ID specified in this request to the store terminal 12.

A third modification of the sixth embodiment will be described.
Here, a process for supporting customer service to a user who has never visited the store in the past will be described. For example, the customer service support information acquisition unit 324 of the buying and selling support server 14 determines that the customer service support information specified by the service provider ID and the user ID is not stored in the customer service support information holding unit 320, that is, the customer service support information holding unit. If the customer service support information is not hit in the search of 320, the customer service support information providing unit 328 may be notified that the customer is a user of the first store with no record of visiting the store. The recommended product determination unit 326 may skip the recommended product determination process because there is no past purchase history of the user. However, the recommended product determination unit 326 selects a recommended product predetermined in the store and does not depend on the past purchase history. Recommended products may be determined according to user attributes such as gender and age.

  The customer service support information providing unit 328 of the sales support server 14 provides the customer service support information for the user of the first visit to the store terminal 12. This customer service support information includes a first visit flag indicating that this is the first visit (the number of past visits is 0). Further, when the recommended product determination unit 326 determines the recommended product, the product information is included. Furthermore, customer information that does not depend on past visits to the store, such as basic information shown in FIG. 34, may also be included.

  When the customer service information display unit 344 of the store terminal 12 detects the first store flag added to the customer service support information, an additional image indicating the first store may be displayed in the check-in list 364 of FIG. When the first visitor is selected in the check-in list 364, the customer service support information display unit 344 displays other types of information (displaying the user information shown in FIGS. 33 and 34 on the customer service support screen). For example, medical record information, purchase history, customer service memos, etc.) may be displayed. As another aspect, for the first visitor, the check-in list 364 may indicate that this is the first visit, while the customer service support information may be displayed as unrecorded.

  Note that the buying and selling support server 14 may hold the number of visits to each store (for example, the number of check-ins, the number of reservations, or the total of these) as information on each of the registered users. The number of visits may be held for each service provider, or the number of visits may be held for each store. It may be incremented at every check-in or reservation. Even if the product purchase support unit 32 refers to the number of visits to each store recorded for the user who made the check-in or reservation, the product purchase support unit 32 determines whether the user is the first visitor to the service provider or the store. Good. Further, when providing the check-in information to the store, the sales support server 14 may provide customer support information including the number of visits of the user to the store. The customer service support information display unit 344 of the store terminal 12 may display the number of visits of each user to the store on the check-in list 364 and the customer service support screen.

  Any combination of the above-described embodiments and modifications is also useful as an embodiment of the present invention. For example, the modification of the first embodiment can be combined with the second embodiment and any modification of the second embodiment. Of course, any combination with the third to sixth embodiments is also possible. The new embodiment generated by the combination has the effects of the combined embodiment and the modified examples.

  In addition, the functions to be fulfilled by the constituent elements described in the claims may be realized by the individual constituent elements shown in the first to sixth embodiments and their modifications, or by their cooperation. It will be understood by contractors. For example, the visit information acquisition unit described in the claims may be realized by one or both of the check-in reception unit 120 and the reservation information reception unit 260 described in the embodiment. The selection screen display unit described in the claims may be realized by cooperation of the sales support screen display unit 66 and the customer service support information display unit 344 described in the embodiment.

  DESCRIPTION OF SYMBOLS 10 Purchaser terminal, 12 Store terminal, 14 Sales support server, 36 Purchase support screen display part, 42 One time code generation part, 66 Sales support screen display part, 74 Settlement request notification part, 100 Merchandise sales system, 132 Settlement processing part 310 message receiving unit, 312 message notifying unit, 314 talk information acquiring unit, 320 customer service support information holding unit, 324 customer service support information acquiring unit, 328 customer service support information providing unit, 330 customer service support information updating unit, 342 customer service support information acquisition 344, customer service information display unit, 346 customer service support information update unit, 348 message reception unit, 350 message notification unit, 352 talk information acquisition unit.

Claims (6)

The device of the merchandise or service seller,
A server connected to the seller's terminal via a communication network;
With
The server
A customer service support information holding unit that stores customer service support information for each purchaser of a product or service;
Information indicating that the purchaser intends to visit the seller's store in the future, and a visit information acquisition unit for acquiring visit information input by the seller or the purchaser;
A purchaser image providing unit that provides an image indicating the appearance of the purchaser indicated by the visit information to the terminal of the seller;
A customer service support information providing unit that provides customer service support information related to the purchaser indicated by the visit information to the seller's terminal, and
The merchant terminal is
A selection screen display unit for displaying a selection screen for causing a seller to select an image of a purchaser who serves as a customer, and is a screen on which images of purchasers provided from the server are arranged.
For a purchaser whose image is selected on the selection screen, a customer service information display unit for displaying customer service information provided from the server;
A payment request notifying unit for notifying the server of a payment request designating a purchaser whose image has been selected on the selection screen,
The server
A payment information holding unit for holding payment information for each purchaser required for electronic payment of goods or services;
A payment processing unit for executing electronic payment for the price of goods or services using the payment information of the purchaser specified in the payment request notified from the seller's terminal. Processing system.   The information processing system according to claim 1, wherein the customer service support information includes information indicating a past record of a purchaser of a product or service visiting a store of a seller. It also has a device for the purchaser of the product or service,
The purchaser's terminal includes a message notification unit that accepts an input of a message for the seller designated by the visit information from the purchaser and notifies the seller's terminal of the message,
3. The service support information display unit of the seller's terminal further displays a message input by the purchaser on a screen displaying the service support information of a specific purchaser. The information processing system described. A server connected to a terminal of a merchandise or service seller via a communication network,
A customer service support information holding unit that stores customer service support information for each purchaser of a product or service;
Information indicating that the purchaser intends to visit the seller's store in the future, and a visit information acquisition unit for acquiring visit information input by the seller or the purchaser;
By providing an image indicating the appearance of the purchaser indicated by the visit information to the seller's terminal, a selection screen for allowing the seller to select an image of the purchaser who is serving at the seller's store is displayed on the seller's screen. A buyer image provider to be displayed on the terminal;
Service support information for displaying on the seller's terminal customer service support information related to the purchaser whose image is selected on the selection screen by providing the customer's terminal with customer service support information indicated by the visit information. A providing department;
With
The seller's terminal notifies the server of a settlement request specifying the purchaser whose image is selected on the selection screen,
A payment information holding unit for holding payment information for each purchaser required for electronic payment of goods or services;
A transaction processing unit, further comprising: a payment processing unit that executes electronic payment for the price of goods or services using the payment information of the purchaser specified in the payment request notified from the seller's terminal. Support server. A device of a merchandise or service seller,
Information indicating that the purchaser of the product or service is planning to visit the seller's store in the future, and the visit information provided from the server that acquired the visit information input by the seller or the purchaser is A purchaser image acquisition unit for acquiring an image indicating the appearance of the purchaser to be displayed;
A customer service support information acquisition unit for acquiring customer service support information regarding a purchaser provided by the visit information provided by the server;
A selection screen display unit for displaying a selection screen for causing a seller to select an image of a purchaser who serves as a customer, and is a screen on which images of purchasers provided from the server are arranged.
For a purchaser whose image is selected on the selection screen, a customer service information display unit for displaying customer service information provided from the server;
A payment request notification that causes the server to execute electronic payment for the price of goods or services using the purchaser's information by notifying the server of a payment request specifying the purchaser whose image has been selected on the selection screen And
A merchant terminal comprising: The device of the purchaser of the product or service,
A reception unit that receives a predetermined operation input by a purchaser for registering a future visit to a store of merchandise or service sellers;
When the predetermined operation input is accepted, the server should be notified of the visit information indicating that the purchaser intends to visit the seller's store in the future. Second matching information that can identify one matching information is recorded in association with the purchaser, and an image showing the appearance of the purchaser indicated by the visit information, and customer service support information regarding the purchaser indicated by the visit information To the seller's terminal, and the seller's terminal is arranged to display the images of the buyers provided from the server, and the selection for causing the seller to select the images of the buyers to serve A visit information notification unit that displays a screen and displays customer service support information provided from the server for a purchaser whose image is selected on the selection screen;
Causing the seller's terminal to notify the server of a payment request specifying the information of the purchaser whose image has been selected on the selection screen and the first matching information acquired from the purchaser; Based on whether or not there is a match between the first verification information specified in the payment request and the second verification information recorded by the server in association with the purchaser specified in the payment request. In order to determine whether the electronic payment of the price is permitted or not, as a response to the predetermined operation input, the first verification information newly generated is displayed on the screen to notify the purchaser of the first verification information. A collation information notification unit
A purchaser terminal characterized by comprising:

Images