Mobile terminal device for store, mobile terminal device for customer, system, method, and program

Abstract

To provide a mobile terminal device for a store, a system, a method and a program that enable a customer to make an electronic payment even when the mobile terminal device for the store does not have a reading means for electronic payment. [Solution] A mobile terminal device for a store comprises a product information acquisition unit that acquires product information for products purchased by a customer, an output unit that operates on the customer's mobile terminal device and displays a screen that can accept input on whether or not a specific application that can set the customer's payment information is being used, and an app presence / absence acceptance unit that accepts whether or not the application is being used via the screen, and the output unit displays settlement information based on the product information, depending on whether or not the accepted application is being used, in a manner that can be read by the customer's mobile terminal device that makes an electronic payment using the settlement information and payment information.

Description

[Technical Field]

[0001] The present invention relates to a mobile terminal device for use in a store. [Background technology]

[0002] There is a self-scan shopping system in which a customer registers products while shopping using a portable terminal device.

[0003] For example, in the technology described in Patent Document 1, a customer registers products while shopping using their mobile terminal device. Also, in the technology described in Patent Document 1, at the time of payment, the settlement device reads the shopping basket identification information from the customer's mobile terminal device using a two-dimensional code. Then, in the technology described in Patent Document 1, the settlement device executes payment by obtaining the basket transaction from the server using the basket identification information. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Publication No. 2020-107122 [Patent Document 2] Japanese Patent Application Laid-Open No. 2015-082249 Summary of the Invention [Problem to be solved by the invention]

[0005] If a store's mobile terminal device does not have a means for reading electronic payments, electronic payments may not be possible. For example, if a card reader is not connected to the mobile terminal device, the mobile terminal device may not be able to read electronic payments.

[0006] An example of an object of the present invention is to provide a mobile terminal device for use in a store that allows customers to make electronic payments even if the mobile terminal device for use in the store does not have a means for reading electronic payments. [Means for solving the problem]

[0007] In one aspect of the present invention, a mobile terminal device for use in a store includes: a product information acquisition means for acquiring product information of products purchased by customers; an output means that operates on the customer's mobile terminal device and displays a screen that can accept input regarding whether or not a predetermined application that can set the customer's payment information is being used; an application presence / absence receiving means for receiving, via the screen, whether or not the application is being used; Equipped with The output means displays settlement information based on the product information, depending on whether the accepted application is being used, in a manner that can be read by the customer's mobile terminal device that makes electronic payment using the settlement information and the payment information.

[0008] In one aspect of the present invention, a customer's mobile terminal device a reading means for reading the settlement information displayed on the mobile terminal device for the store, the settlement information being based on the product information of the product purchased by the customer; a payment means for performing electronic payment using the payment information of the customer and the read settlement information; Equipped with The store's mobile terminal device acquires the product information, operates on the customer's mobile terminal device, and displays a screen that can accept input on whether or not a specific application that can set the payment information is being used.The store's mobile terminal device accepts input on whether or not the application is being used via the screen, and displays the settlement information based on the product information, which is in accordance with whether or not the application is being used.

[0009] In one aspect of the present invention, a system includes: a mobile terminal device for a store; a customer's mobile terminal device; Equipped with The store-use mobile terminal device a product information acquisition means for acquiring product information of products purchased by customers; an output means that operates on the customer's mobile terminal device and displays a screen that can accept input regarding whether or not a predetermined application that can set the customer's payment information is being used; an application presence / absence receiving means for receiving, via the screen, whether or not the application is being used; Equipped with the output means displays payment information based on the product information in accordance with the accepted use of the application in a readable manner by the customer's mobile terminal device; The customer's mobile terminal device a reading means for reading the settlement information displayed on the mobile terminal device for the store; a payment means for performing electronic payment using the payment information and the read settlement information; Equipped with.

[0010] In one aspect of the present invention, a method comprises: Obtain product information for products purchased by customers, a screen that operates on the customer's mobile terminal device and can accept input as to whether or not a predetermined application that can set the customer's payment information is used; Accepting whether or not the application is being used via the screen; and displaying settlement information based on the product information according to whether the accepted application is being used or not, in a readable manner on the mobile terminal device of the customer who makes an electronic payment using the settlement information and the payment information. Execute the process.

[0011] In one aspect of the present invention, the program Obtain product information for products purchased by customers, a screen that operates on the customer's mobile terminal device and can accept input as to whether or not the customer is using a predetermined application for which payment information can be set; Accepting whether or not the application is being used via the screen; and displaying settlement information based on the product information according to whether the accepted application is being used or not, in a readable manner on the mobile terminal device of the customer who makes an electronic payment using the settlement information and the payment information. The processing is executed by a computer in a portable terminal device for the store. [Effects of the Invention]

[0012] According to the present invention, even if the mobile terminal device for the store does not have a reading means for electronic payment, the customer can make electronic payment. [Brief explanation of the drawings]

[0013] [Figure 1] FIG. 1 is an explanatory diagram showing a comparative example of product registration operations in each mode. [Figure 2] FIG. 2 is an explanatory diagram showing a comparative example of cash payment in each mode. [Figure 3] FIG. 3 is an explanatory diagram showing a comparison example of electronic payment in each mode. [Figure 4] FIG. 4 is an explanatory diagram illustrating an example of a system according to the first embodiment. [Figure 5] FIG. 5 is a block diagram showing an example of the configuration of a mobile terminal device for use in a store. [Figure 6] FIG. 6 is a block diagram showing an example of the configuration of a POS server. [Figure 7] FIG. 7 is a block diagram showing an example of the configuration of a customer's mobile terminal device. [Figure 8] FIG. 8 is a block diagram showing an example of the configuration of a settlement device. [Figure 9] FIG. 9 is an explanatory diagram showing a first example of mode reception. [Figure 10] FIG. 10 is an explanatory diagram (part 1) showing a second example of mode reception. [Figure 11] FIG. 11 is an explanatory diagram (part 2) showing a second example of mode reception. [Figure 12] FIG. 12 is an explanatory diagram showing an example of accepting store information using a store code. [Figure 13] FIG. 13 is an explanatory diagram showing an example of accepting store information using a pull-down menu. [Figure 14] FIG. 14 is a flowchart illustrating an example of an operation of the system according to the first embodiment. [Figure 15] FIG. 15 is an explanatory diagram showing an example of reading a product code. [Figure 16] FIG. 16 is an explanatory diagram showing an example of a display of a purchased product list. [Figure 17] FIG. 17 is a flowchart showing an example of a product registration process. [Figure 18] FIG. 18 is an explanatory diagram showing an example of selection of a payment method. [Figure 19] FIG. 19 is an explanatory diagram showing an example of accepting the selection of a device for performing payment. [Figure 20] FIG. 20 is an explanatory diagram showing an example of a display of a settlement code that can be read by the settlement device. [Figure 21] FIG. 21 is an explanatory diagram showing an example of reception of information on whether or not a store app is available. [Figure 22] FIG. 22 is an explanatory diagram showing an example of a display of the settlement code. [Figure 23] FIG. 23 is an explanatory diagram showing an example of a display page on which payment information can be input. [Figure 24] FIG. 24 is an explanatory diagram showing an example of a display indicating that payment has been completed. [Figure 25] FIG. 25 is a flowchart showing an example of a payment process in the self-scan mode. [Figure 26] FIG. 26 is a flowchart (part 1) showing the credit card payment process. [Figure 27] FIG. 27 is a flowchart (part 2) showing the credit card payment process. [Figure 28] FIG. 28 is an explanatory diagram showing an example of a purchase product list in the emergency mode. [Figure 29] FIG. 29 is an explanatory diagram showing an example of selection of a payment method. [Figure 30] FIG. 30 is an explanatory diagram (part 1) showing an example of cash payment in emergency mode. [Figure 31] FIG. 31 is an explanatory diagram (part 2) showing an example of cash payment in emergency mode. [Figure 32] FIG. 32 is a flowchart showing the payment process in emergency mode. [Figure 33] FIG. 33 is an explanatory diagram showing an example of a purchase product list in the front-end handling mode. [Figure 34] FIG. 34 is a flowchart showing settlement process example 1 in the front-end handling mode. [Figure 35] FIG. 35 is a flowchart showing a second example of a settlement process in the front-end handling mode. [Figure 36] FIG. 36 is a flowchart showing settlement process example 3 in the front-end handling mode. [Figure 37] FIG. 37 is a block diagram of a configuration example of a mobile terminal device for use in a store according to the second embodiment. [Figure 38] FIG. 38 is a block diagram of a configuration example of a customer's mobile terminal device according to the second embodiment. [Figure 39] FIG. 39 is a flowchart illustrating an operation example of the mobile terminal device for a store according to the second embodiment. [Figure 40] FIG. 40 is a flowchart illustrating an example of the operation of the customer's mobile terminal device according to the second embodiment. [Figure 41] FIG. 41 is an explanatory diagram illustrating an example of the hardware configuration of a mobile terminal device for use in a store. [Figure 42] FIG. 42 is an explanatory diagram illustrating an example of the hardware configuration of a customer's mobile terminal device. [Figure 43] FIG. 43 is an explanatory diagram illustrating an example of the hardware configuration of a POS server. [Figure 44] FIG. 44 is an explanatory diagram illustrating an example of the hardware configuration of the settlement device. DETAILED DESCRIPTION OF THE INVENTION

[0014] Hereinafter, with reference to the drawings, embodiments of a store-use mobile terminal device, a customer's mobile terminal device, a system, a method, a program, and a recording medium for recording a program according to the present invention will be described in detail. The disclosed technology is not limited to these embodiments.

[0015] (Embodiment 1) In the first embodiment, a mobile terminal device for use in a store that can be switched between three modes, namely, a self-scan mode as a customer mode, and a front-end handling mode and an emergency mode as store clerk modes, will be described.

[0016] FIG. 1 is an explanatory diagram showing a comparison example of product registration operations in each mode. The mobile terminal device for use in a store according to the first embodiment has a self-scan mode, an emergency mode, and a front-end handling mode. The self-scan mode is a customer mode. In the self-scan mode, product registration is performed by an operation by a customer. Details of product registration will be described later.

[0017] The emergency mode and the front-end handling mode are store clerk modes. In the emergency mode and the front-end handling mode, product registration is performed by the store clerk.

[0018] The emergency mode is used as a measure for a business continuity plan (BCP). For example, the emergency mode is a store clerk mode in which a mobile terminal device for a store is used as an emergency product registration device. In the emergency mode, it is assumed that, for example, the checkout device installed in the store cannot be used.

[0019] The front-end handling mode is used to improve work efficiency or as a countermeasure for waiting for the product registration device that registers products. The front-end handling mode is a store clerk mode in which a store mobile terminal device is used as a front-end handling product registration device that registers products up until payment. The emergency mode and the front-end handling mode have in common the fact that product registration is performed by the operation of a store clerk. However, the emergency mode and the front-end handling mode are used in different situations, and therefore the payment methods are different.

[0020] FIG. 2 is an explanatory diagram showing a comparison example of cash payments in each mode. First, cash payments in self-scan mode will be described. In self-scan mode, the settlement device makes cash payments. The settlement device may be manned or unmanned. Alternatively, the settlement device may be a device that can switch between being manned and unmanned. In self-scan mode, when the settlement device is manned, the settlement device makes cash payments in response to operation by a store clerk. When the settlement device is unmanned, the settlement device makes cash payments in response to operation by a customer.

[0021] Next, cash settlement in the emergency mode will be described. In the emergency mode, the store mobile terminal device performs cash settlement by operation of a store clerk.

[0022] Next, cash settlement in the front-handling mode will be explained. As described above, the front-handling mode is used to improve operational efficiency or as a countermeasure for waiting times for the product registration device that registers products. For this reason, in the front-handling mode, the settlement device performs cash settlement. The settlement device may be manned or unmanned. In the front-handling mode, if the settlement device is manned, the settlement device performs cash settlement by operation of a store clerk. If the settlement device is unmanned, the settlement device performs cash settlement by operation of a customer.

[0023] FIG. 3 is an explanatory diagram showing a comparative example of electronic payments in each mode. The type of electronic payment is not particularly limited. Examples of electronic payments include at least one of credit card payments, debit card payments, electronic money payments, points payments, and virtual currency payments. Examples of electronic money payments include payments using a short-range wireless communication type IC (Integrated Circuit) card, one-dimensional barcode payments, and Quick Response code (QR Code (registered trademark)) payments.

[0024] The following describes electronic payments in self-scan mode. For example, in self-scan mode, the settlement device performs electronic payments. When the settlement device is manned, the settlement device performs electronic payments in response to operations by a store clerk. Note that operations such as reading a credit card are performed by operations by the customer. When the settlement device is unmanned, the settlement device performs electronic payments in response to operations by the customer.

[0025] In the self-scan mode, the customer's mobile terminal device may perform electronic payment. Note that the customer's mobile terminal device performs electronic payment by operating the customer.

[0026] In self-scan mode, if the store's portable terminal device can accept input of customer payment information, the store's portable terminal device may perform electronic payment in response to a customer's operation. Here, customer payment information refers to information related to the customer's electronic payment for making the electronic payment. More specifically, the payment information is, for example, information for making electronic payment by card. Take the case of credit card payment as an example. The payment information is credit information such as the credit card payment number, the expiration date of the credit card payment, and the name registered for the credit card payment. If the store's portable terminal device can accept credit card information, the store's portable terminal device performs the credit card payment in response to a customer's operation.

[0027] Electronic payment in emergency mode will now be described. In emergency mode, for example, a customer's mobile terminal device performs electronic payment. A detailed example will be described later. Also, in emergency mode, if the store's mobile terminal device is capable of accepting input of the customer's payment information, for example, the store's mobile terminal device may perform electronic payment. For example, in the case of credit card payment, if the store's mobile terminal device is capable of accepting credit information such as a credit number as the customer's payment information through operation by the customer, the credit card payment will be performed.

[0028] We will now explain electronic payments in front-handling mode. As mentioned above, front-handling mode is used to improve operational efficiency or as a way to deal with waiting times at the product registration device that registers products. For this reason, in front-handling mode, the settlement device performs electronic payments. When the settlement device is manned, the settlement device performs electronic payments through operation by a store clerk. Note that operations such as reading a credit card are performed through operation by the customer. When the settlement device is unmanned, the settlement device performs electronic payments through operation by the customer.

[0029] In this way, the store-use portable terminal device according to the first embodiment can switch the use of the device depending on the accepted mode, thereby enabling the store-use portable terminal device to use the device more effectively.

[0030] 4 is an explanatory diagram showing an example of a system according to the first embodiment. System 1 includes, for example, a store-use mobile terminal device 10, a POS (Point Of Sale) server 11, a customer-use mobile terminal device 12, a printer 13, a checkout device 14, and a payment server 15. Store-use mobile terminal device 10, POS server 11, customer-use mobile terminal device 12, a printer 13, a checkout device 14, and a payment server 15 may be connected to each other via, for example, a communication network 16.

[0031] The store-use mobile terminal device 10 has, for example, a function for registering products purchased by customers. The store-use mobile terminal device 10 can switch between the three modes described above. The type of the mobile terminal device is not particularly limited, and may be a smartphone, tablet, or the like. Furthermore, although not shown, the number of store-use mobile terminal devices 10 is not particularly limited. For example, the multiple store-use mobile terminal devices 10 may have the same function. Alternatively, the multiple store-use mobile terminal devices 10 may have different functions.

[0032] The POS server 11 is a server that manages various sales information such as product information including prices of products sold in a store and sales information of the store. The POS server 11 may collectively manage the sales information of multiple stores. Alternatively, a POS server 11 may exist for each store. The POS server 11 may also manage the sales information of a single store.

[0033] Furthermore, the POS server 11 may perform processing in response to a request from the store-use mobile terminal device 10. The POS server 11 may, for example, transmit information necessary for display control of the store-use mobile terminal device 10 to the mobile terminal device. For example, the POS server 11 may transmit to the store-use mobile terminal device 10 screen information that displays a list of products to be purchased registered by the store-use mobile terminal device 10 together with their selling prices. This list will be hereinafter referred to as a "purchased product list." The POS server 11 may also manage information about members. Various types of information held by the POS server 11 will be described later.

[0034] Here, an example is shown in which the POS server 11 is realized by one device. However, there are no particular limitations on the implementation of the POS server 11. The POS server 11 may be realized by different devices for different functions or databases (DBs).

[0035] The customer's mobile terminal device 12 is, for example, a terminal device that the customer possesses. The type of the customer's mobile terminal device 12 is not particularly limited, and may be a smartphone, tablet, or the like. The customer's mobile terminal device 12 may not be used depending on the payment method. Although not shown, the number of the customer's mobile terminal devices 12 is not particularly limited.

[0036] The printing device 13 prints, for example, various printed materials. The printing device 13 prints, for example, receipts. Alternatively, the printing device 13 prints, for example, printed materials including payment information. The printed materials may include, for example, a code in which the payment information is encoded. The details of the payment information vary depending on the mode or the device used to make the payment. Details of the payment information will be explained for each mode. The type of printing device 13 is not particularly limited. The printing device 13 may be, for example, a thermal printer.

[0037] The settlement device 14 is a store device capable of performing various types of payments, such as electronic payments and cash payments. The settlement device 14 has a reading device that reads codes, such as one-dimensional codes like barcodes and two-dimensional codes. The settlement device 14 then performs various types of payments based on the read codes. The settlement device 14 may also have a function that allows it to print receipts, for example. The settlement device 14 may also be an attended checkout machine with a store clerk present. The settlement device 14 may also be an unattended checkout machine without a store clerk present. The settlement device 14 may also be a checkout machine that can be switched between attended and unattended modes. Specifically, the settlement device 14 may be a checkout machine that can be switched between an attended mode with a store clerk present and an unattended mode without a store clerk present. In other words, in the attended mode, payments are made by operation by a store clerk. Furthermore, multiple settlement devices 14, such as settlement device 14-1 and settlement device 14-2, may be installed in a store. Furthermore, multiple switchable mode settlement devices 14 may each operate in a different mode.

[0038] 5 to 8, an example of the configuration of each device according to the first embodiment will be described. FIG. 5 is a block diagram showing an example of the configuration of a store-use mobile terminal device 10. The store-use mobile terminal device 10 includes a mode reception unit 101, a store reception unit 102, a product information acquisition unit 103, a quantity reception unit 104, a payment method reception unit 105, and an application presence / absence reception unit 106. The store-use mobile terminal device 10 further includes a settlement information management unit 107, a payment unit 108, an output unit 109, and a storage unit 110. The output unit 109 may include, for example, a display unit 1010 and an issuance control unit 1011. The storage unit 110 stores, for example, data used for processing by each unit of the store-use mobile terminal device 10. The storage unit 110 stores, for example, processing results by each unit of the store-use mobile terminal device 10. Examples of the storage unit 110 include a read-only memory (ROM), a random access memory (RAM), a semiconductor memory, a hard disk drive (HDD), and a solid state drive (SSD). The storage unit 110 may be a combination of these. The mobile terminal device 10 for use in a store may not have some of the functional units. Alternatively, the mobile terminal device 10 for use in a store may have functional units that are not shown.

[0039] FIG. 6 is a block diagram showing an example of the configuration of the POS server 11. The POS server 11 includes a settlement information generation unit 111, a list generation unit 112, a sales management unit 113, and a storage unit 114. The POS server 11 may not include some of the functional units. The POS server 11 may include functional units not shown. The functional units of the POS server 11 shown in FIG. 6 may be implemented by multiple devices. For example, each functional unit may be implemented by two devices: one device including the settlement information generation unit 111 and the list generation unit 112, and another device including the sales management unit 113. Alternatively, each functional unit may be implemented by three devices: one device including the settlement information generation unit 111, one device including the list generation unit 112, and another device including the sales management unit 113. Alternatively, for example, the settlement information generation unit 111 may be implemented by different devices depending on the content of the settlement information.

[0040] The storage unit 114 stores, for example, data used for processing by each unit of the POS server 11. Examples of storage units include ROM, RAM, semiconductor memory, HDD, and SSD. The storage unit 114 may be a combination of these. The storage unit 114 has a member DB 115, a store clerk DB 116, a product DB 117, a sales DB 118, and a purchased product list DB 119.

[0041] Member DB 115 stores member information for each member (customer), for example. The member information may be, for example, at least one of a member ID (identifier), the member's name, the member's gender, the member's age or age group, and the member's notification destination. The member ID is, for example, an identifier that uniquely identifies a member. The type of member ID is not particularly limited. The member ID may be represented by a membership number. The notification destination may be an email address, a telephone number, or the like. Member DB 115 may also store information such as a password, past purchase history, and points for each member. Member DB 115 may also store biometric information for each member. The biometric information is not particularly limited. Examples of biometric information include facial feature data, facial image data, fingerprint data, iris data, and vein data.

[0042] Member DB 115 may not include some of the above-mentioned information about members, and may also include information about members other than the above-mentioned information.

[0043] The clerk DB 116 stores clerk information for each clerk, for example. The clerk information is, for example, at least one of a clerk ID and a clerk name. The clerk ID is, for example, an identifier that uniquely identifies a member. The clerk ID is not particularly limited. The clerk ID may be represented by a clerk number. The clerk DB 116 may further store information such as a password, work schedule, and biometric information for each clerk. The biometric information is as described above for the member DB 115.

[0044] The store clerk DB 116 may not include all of the above-mentioned information about store clerks. Also, the store clerk DB 116 may include information about store clerks other than the above-mentioned information.

[0045] Product DB 117 stores product information about products handled by a store or affiliated stores including the store. Specifically, product DB 117 stores product information, for example, by product. Product information includes, for example, product ID, product name, product category, product price, and product features. Product ID is an identifier that can identify a product. Product ID is not particularly limited. Product ID is, for example, a product code (hereinafter referred to as product code). More specifically, product ID may be, for example, at least one product code such as a JAN (Japanese Article Number) code, an EAN (European Article Number) code, or a UPC (Universal Product Code). Alternatively, product ID may be a product name. Product category is not particularly limited. For example, product category may be broad categories such as food, stationery, etc. Product category may also be categories such as confectionery, meat, and vegetables. Product price is the price of the product. Product features are not particularly limited. Product features may include a best-before date, a use-by date, a manufacturer, etc.

[0046] Furthermore, the product information may include information for identifying the product in addition to the product ID information. For example, the product information may include image data of the product, information on features obtained from the image data of the product, etc.

[0047] The product DB 117 may not include some of the above-mentioned information about products, and may also include information about products other than the above-mentioned information.

[0048] The purchase item list DB 119 stores the latest purchase item list for which payment has not yet been completed, by transaction or by customer. The purchase item list stores, for example, information identifying a transaction or customer, product information on products the customer plans to purchase, and purchase quantity information, in association with each other, by transaction or by customer. The information identifying a transaction may be, for example, uniquely identifying a transaction, and is not particularly limited. The information identifying a customer may be, for example, uniquely identifying a customer, and is not particularly limited. Here, an example will be described in which information identifying a customer is stored and a customer ID is assigned as the information identifying the customer. For example, a customer ID is assigned to a customer before product registration for a new customer begins. "Before product registration begins" may be any time between when the mode is accepted and when the display unit 1010 displays an initial screen for a new purchase item list with no product information registered. The specific timing at which a customer ID is assigned may vary depending on the mode or the payment method used in each mode. The purchase item list can be uniquely identified by the customer ID. If a member ID is accepted, the accepted member ID may be used as the customer ID. Alternatively, in addition to the customer ID, the purchased item list may store information on the received member ID in association with each customer. The product information here may be any information that can uniquely identify a product. For example, the product information may be product ID information. As a result, the purchased item list is associated with product DB 117 using the product ID information. Therefore, by referencing the purchased item list, each device can obtain product price information, product name, etc. from product DB 117 using the product ID information registered in the purchased item list. Furthermore, the purchased item list may store product price information including tax as product information based on this product price information. Furthermore, the purchased item list may further include information on the total purchase price and total purchase quantity for each customer.

[0049] The purchase item list DB 119 may not include some of the above-mentioned information about the purchase item list, and may also include information about the purchase item list other than the above-mentioned information.

[0050] The sales DB 118 stores, for example, information related to the sales of each store. The sales DB 118 may manage, for example, information corresponding to each payment for each store. Specifically, the sales DB 118 stores, in association with each other, information such as a store ID, an ID of the mobile terminal device 10 for the store, an ID of the user, an ID of the settlement device 14, an ID of the operator of the settlement device 14, an item ID of the purchased item, a purchase quantity, and a purchase date and time. The store ID is an identifier that uniquely identifies a store. The ID of the mobile terminal device 10 for the store is an identifier that uniquely identifies the mobile terminal device 10 for the store. The ID of the mobile terminal device 10 for the store registered in the sales DB 118 is the ID of the terminal device that registered the item. The ID of the settlement device 14 is an identifier that uniquely identifies the settlement device 14. The ID of the settlement device 14 registered in the sales DB 118 is the ID of the settlement device 14 that performed the payment. The ID of the user (operator) registered in the sales DB 118 is the store clerk ID or member ID of the user who uses the store mobile terminal device 10. The sales DB 118 may also include information indicating the mode of the store mobile terminal device 10 at the time of operation. The sales DB 118 may also include other information such as information contained in each receipt, which will be described later.

[0051] The sales DB 118 may not include some of the above-mentioned information about sales, and may also include information about sales other than the above-mentioned information about sales.

[0052] The sales management unit 113 updates the sales DB 118, for example, according to the details of the payment. Also, for example, the sales DB 118 and the product DB 117 are associated with each other by product ID, etc. The price of each product in the sales DB 118 is registered as the price at the time of payment.

[0053] For ease of explanation and understanding, an example is shown in which the POS server 11 has various DBs, but this is not limiting. For example, the various DBs may be held by different devices. For example, the server managing the sales DB 118, the server managing the member DB 115, and the server managing the purchased item list DB 119 may be different servers. In such a case, the server managing the sales DB 118 and the server managing the member DB 115 function as database servers. The server managing the purchased item list DB 119 functions as, for example, an application server. Each server passes information used for the process assigned to it via, for example, the communication network 16.

[0054] The POS server 11 may also handle various types of information not shown. For example, the POS server 11 may acquire information regarding changes in selling prices, such as discount amounts, bundle discounts, set discounts, and discount rates, and use that information to calculate the purchase price at the time of payment. Alternatively, the POS server 11 may use that information to update the purchase product list. A bundle discount is a discount given when multiple units of a specific product are purchased. A set discount is a discount given for a specific combination of products.

[0055] FIG. 7 is a block diagram showing an example configuration of the customer's mobile terminal device 12. The customer's mobile terminal device 12 includes, for example, a reading unit 121, a payment unit 122, an output unit 123, a payment information receiving unit 125, and a memory unit 126. The memory unit 126 stores, for example, data used for processing by each unit of the customer's mobile terminal device 12. The memory unit 126 may store, for example, the processing results of each unit of the customer's mobile terminal device 12. Examples of the memory unit 126 include ROM, RAM, semiconductor memory, HDD, and SSD. The memory unit 126 may also be a combination of these. The output unit 123 includes, for example, a display unit 1210. The customer's mobile terminal device 12 may not include some of the functional units. The customer's mobile terminal device 12 may include functional units not shown.

[0056] FIG. 8 is a block diagram showing an example configuration of the settlement device 14. The settlement device 14 has a reading unit 141, a settlement unit 142, an issuance control unit 143, a display unit 144, and a memory unit 145. The memory unit 145 stores, for example, data used for processing by each unit of the settlement device 14. The memory unit 145 may also store, for example, processing results by each unit of the customer's mobile terminal device 12. Examples of the memory unit 145 include ROM, RAM, semiconductor memory, HDD, and SSD. The memory unit 145 may also be a combination of these. The settlement device 14 may have functional units not shown.

[0057] Next, a detailed description will be given of each functional unit shown in Figures 5 to 8. Here, the reception of modes and examples of operation in various modes will be described.

[0058] <Mode reception> First, the reception of a mode will be described. The mode reception unit 101 receives the input of a mode. More specifically, the mode reception unit 101 receives a self-scan mode, which is a customer mode, an emergency mode, which is a store clerk mode, and a front-end handling mode, which is a store clerk mode. The method of receiving a mode is not particularly limited. The mode reception unit 101 may receive a mode by a selection button displayed on the screen.

[0059] FIG. 9 is an explanatory diagram showing a first example of mode reception. For example, the display unit 1010 displays a screen d001 on a display or the like, from which each mode can be selected. The screen d001 has, for example, a selection button d002 from which the self-scan mode can be selected, a selection button d003 from which the emergency mode can be selected, and a selection button d004 from which the front-hand handling mode can be selected. Each button is, for example, a GUI (Graphical User Interface) button. The type of button is not particularly limited. Note that in the following description, the buttons displayed on each screen are GUI buttons.

[0060] For example, the user (operator) taps a selection button corresponding to a desired mode. In this way, the user selects a mode. Then, when the selection button is tapped, the mode accepting unit 101 accepts the mode corresponding to the tapped selection button. This concludes the explanation of Figure 9.

[0061] Here, when the selection button d002 for selecting the self-scan mode is tapped, the list generation unit 112 of the POS server 11 assigns a customer ID to the customer and generates a new purchase product list.

[0062] Alternatively, the mode acceptance unit 101 may accept a mode based on information about the ID of a user (operator). For example, the mode acceptance unit 101 may function as an identification information acceptance unit that accepts information about the ID of a user (operator). There are no particular limitations on the method by which the mode acceptance unit 101 accepts information about the ID of a user. The mode acceptance unit 101 may accept an ID input on a screen such as that shown in FIG. 10, which will be described later. Alternatively, the mode acceptance unit 101 may accept an ID by extracting the ID written on a store clerk card, such as an employee ID card, from an image of the store clerk card captured by an imaging device.

[0063] 10 and 11 are explanatory diagrams showing a second mode reception example. For example, the display unit 1010 displays a screen d010 on which information such as an ID (identifier) ​​and a password can be input. In FIG. 10, the screen d010 has, for example, an ID input field d011, a password input field d102, and a login button d013. For example, when the button d013 is tapped, the mode reception unit 101 receives the ID information input in the ID input field d011 and the password information input in the password input field d012. The mode reception unit 101 then transmits the received ID information and password information to the POS server 11. For example, a query unit (not shown) of the POS server 11 queries the member DB 115 for the input ID information and password information. The query unit of the POS server 11 queries the store clerk DB 116 for the input ID information and password information.

[0064] For example, the mode reception unit 101 is assumed to have accepted the self-scan mode when the input ID information and password information are in the member DB 115, or when there is no matching ID information and password information in the store clerk DB 116. For example, the mode reception unit 101 is assumed to have accepted the store clerk mode (front-end handling mode or emergency mode) when the input ID information and password information are in the store clerk DB 116.

[0065] If the entered ID information and password information are in the member DB 115, the list generation unit 112 of the POS server 11 assigns a customer ID to the customer and generates a new purchase item list.

[0066] 11, in the case of the clerk mode, the display unit 1010 displays a screen d020 that accepts either a front-end handling mode or an emergency mode. The screen d020 here has, for example, a selection button d021 that can select the emergency mode and a selection button d022 that can select the front-end handling mode. When either of the selection buttons is tapped, the mode accepting unit 101 accepts the mode corresponding to the tapped selection button.

[0067] Next, the store reception unit 102 will be described. For example, a company may have multiple stores. Sales and the like are recorded on a store-by-store basis. For this reason, the store reception unit 102 receives store information. Store information (hereinafter referred to as store information) is not particularly limited as long as it can uniquely identify a store. The method of receiving store information is not particularly limited. The store reception unit 102 may receive store information by reading a code for the store (hereinafter referred to as store code). The store code is represented, for example, by a one-dimensional code such as numbers, letters, or a barcode, or a two-dimensional code, or a combination of these. Alternatively, for example, the store reception unit 102 may receive store information by inputting a store name or selecting from store name candidates.

[0068] FIG. 12 is an explanatory diagram showing an example of accepting store information using a store code. For example, the display unit 1010 displays a screen d030 for reading the store code. The store code includes, for example, identification information that can uniquely identify the store. In FIG. 12, the store code is a two-dimensional code. The screen d030 has a store code reading portion d031. The type of store code is not particularly limited, for example. The store code reading portion d031 is realized by a reading device of the store-use mobile terminal device 10. Examples of the reading device include an imaging device. A printed material including a store code that can be read by the store-use mobile terminal device 10 may be posted, for example, near the entrance of the store. The store reception unit 102 reads the store code, for example, via the reading device of the store-use mobile terminal device 10. As a result, the store reception unit 102 accepts the store that is the target store for shopping based on the store information included in the store code.

[0069] 13 is an explanatory diagram showing an example of accepting store information using a pull-down menu. For example, the display unit 1010 may display a screen d040 that allows a user to select a store name from a pull-down menu. For example, the screen d040 has a pull-down menu d041 that allows a user to select a store name, and a confirm button d042 that confirms the store selection. When the user selects the name of the target store from the pull-down menu d041 and presses the confirm button d042, the store reception unit 102 accepts the input of store information.

[0070] Furthermore, if a store selection has already been accepted in the past, the screen d040 may be displayed with the name of the previously selected store selected in the pull-down menu d041. This allows the user to select a store by checking the store name and tapping the confirm button d042.

[0071] As described above, the method of accepting store information is not particularly limited. However, different store information acceptance methods may be implemented depending on the mode. There is no particular limit to which store information acceptance method is implemented in each mode. For example, a customer may not know the name of the store, etc. Therefore, in the self-scan mode operated by the customer, a store information acceptance method using a store code as described with reference to FIG. 12 may be used. On the other hand, it is highly likely that the store clerk knows the store name. For example, in the front-end handling mode and the emergency mode, a store information acceptance method in which the store name is selected from a pull-down menu as described with reference to FIG. 13 may be used. Note that store information acceptance may not be performed. Alternatively, store information may not be accepted in some of the multiple modes.

[0072] Furthermore, the store information reception process by the store reception unit 102 is not limited to being performed after the mode reception process by the mode reception unit 101. For example, before the mode reception process by the mode reception unit 101, the store may be in a state where a store has been selected in advance by an operation by a store clerk in the store mobile terminal device 10. Furthermore, once a store has been selected, the store reception unit 102 may not receive a new store selection unless a predetermined trigger occurs. Examples of the predetermined trigger include restarting or starting up the store mobile terminal device 10, or moving a predetermined distance or more from the store.

[0073] Next, for example, in the self-scan mode, after receiving the store information, the display unit 1010 may display, as an initial screen, a screen (not shown) in which no product information is registered in the product registration list.

[0074] In the store clerk mode (front-end handling mode or emergency mode), the list generation unit 112 of the POS server 11 assigns a customer ID to a new customer and generates a new purchased item list. Then, the display unit 1010 may display, as an initial screen, a screen (not shown) in which no product information is registered in the product registration list. Note that, in the customer mode, as in the store clerk mode, the list generation unit 112 may assign a customer ID to a new customer and generate a new purchased item list just before the display unit 1010 displays the initial screen, rather than at the time when the customer ID information is received.

[0075] <Flowchart for mode reception> Here, the flow of processing up to the product registration processing and the payment processing will be described in detail with reference to FIG. 14. The product registration processing is processing for registering product information of products that a customer plans to purchase in a purchase product list. The payment processing is processing for making a payment based on the product information registered in the purchase product list. The flow shown in FIG. 14 includes steps of the product registration processing and the payment processing, and a detailed description of each step will be given later. FIG. 14 is a flowchart showing an example of operation of the system 1 according to the first embodiment. In FIG. 14, the mode acceptance unit 101 accepts a mode based on information about the ID of an operator (user) (step S101). Next, the mode acceptance unit 101 determines whether the accepted user ID information is information about a store clerk ID or information about a member ID (step S102). In step S102, if the information is information about a member ID (step S102: member ID), it is assumed that the mode acceptance unit 101 accepts a customer mode. In the case of information on a store clerk ID (step S102: store clerk ID), the mode receiving unit 101 is assumed to have received the store clerk mode.

[0076] If the customer mode is accepted (step S102: member ID), the system 1 performs product registration processing in the self-scan mode (step S103), and then performs payment processing in the self-scan mode (step S104). After step S104, the system 1 ends the operation of the flow. Note that in the case of the customer mode (self-scan mode), the system 1 may return to step S101 after step S104.

[0077] If the clerk mode is accepted (Step S102: clerk ID), the mode acceptance unit 101 accepts either the front-end handling mode or the emergency mode (Step S105). The mode acceptance unit 101 determines whether the mode is the front-end handling mode or the emergency mode (Step S106). If the mode is the emergency mode (Step S106: emergency mode), the system 1 performs product registration processing for the emergency mode (Step S107). Then, the system 1 performs payment processing for the emergency mode (Step S108). After Step S108, the system 1 ends the operation of the flow. Note that, in the emergency mode, after Step S108, the system 1 may return to Step S101 or to Step S107. Note that if returning to Step S107, the list generation unit 112 assigns a customer ID to the new customer and generates a new purchase product list. Then, the display unit 1010 may display, as an initial screen, a screen (not shown) in which no product information is registered in the product registration list.

[0078] In the front-end handling mode (Step S106: Front-end handling mode), the system 1 performs product registration processing for the front-end handling mode (Step S109). The system 1 performs payment processing for the front-end handling mode (Step S110). After Step S110, the system 1 ends the operation of the flow. In the front-end handling mode, after Step S110, the system 1 may return to Step S101 or to Step S109. When returning to Step S109, the list generation unit 112 assigns a customer ID to the new customer and generates a new purchased product list. Then, the display unit 1010 may display, as an initial screen, a screen (not shown) in which no product information is registered in the product registration list. In the front-end handling mode, the timing of assigning a customer ID to a new customer is not limited to this and can be changed in various ways depending on the payment processing described below.

[0079] Furthermore, the method of accepting the mode is not particularly limited. For example, in step S101, the mode acceptance unit 101 accepts the mode based on ID information, but this is not limiting. For example, the mode acceptance unit 101 may accept a selection of whether to be a store clerk or a customer using a selection screen or the like. Then, in step S102, the mode acceptance unit 101 may determine which selection has been accepted. For example, if a customer selection is accepted in step S102, the mode acceptance unit 101 accepts the customer mode (step S102: member ID). For example, if a store clerk selection is accepted in step S102, the mode acceptance unit 101 accepts the store clerk mode (step S102: store clerk ID).

[0080] Also, instead of steps S101, S102, and S105, the mode receiving unit 101 may receive a mode from a screen d001 as shown in Fig. 9. If the customer mode is received, the system 1 proceeds to step S103. If the emergency mode is received, the system 1 proceeds to step S107. If the front-end handling mode is received, the system 1 proceeds to step S109.

[0081] As mentioned above, the flowcharts of the product registration process and the payment process in each mode in FIG. 14 will be explained in detail for each mode.

[0082] Next, product registration and payment in each mode will be explained.

[0083] <Product registration process in self-scan mode> In the self-scan mode, the product information acquisition unit 103 acquires product information of the product to be purchased by the customer in response to an operation by the customer. The acquired product information may be product ID information. The acquired product information may also be image data of the product or information on features obtained from the image data of the product. The acquired product information is not limited to this. The acquired product information may be any information that can uniquely identify the product that the customer wishes to purchase. There are various examples of methods for acquiring product information, such as reading a product code, which is product ID information, identifying by image, or reading a tag. The acquisition method is not particularly limited.

[0084] The product information acquisition unit 103 acquires product information by, for example, reading a product code via a reading device. The reading device is not particularly limited. For example, the reading device is an imaging device included in the mobile terminal device 10 for a store. The product code may be the above-mentioned JAN code or the like. The product code may be represented by, for example, numbers, letters, or a combination thereof. When displayed, the product code may be encoded into a one-dimensional code such as a barcode, a two-dimensional code, or the like. When reading an encoded code such as a one-dimensional code or a two-dimensional code, the product information acquisition unit 103 may decode the encoded code after reading it. The product information acquisition unit 103 may then transmit the combined product code to the list generation unit 112 of the POS server 11. Alternatively, the product information acquisition unit 103 may transmit the read product code to the list generation unit 112 of the POS server 11. The list generation unit 112 may then combine the received product code.

[0085] The product information acquisition unit 103 acquires product information by, for example, identifying a product from an image of the product captured by an imaging device included in the store-use mobile terminal device 10. The product information acquisition unit 103 also identifies a product by reading a pre-captured image of the product or an image of a picture of the product via the imaging device. In this way, the acquisition unit acquires product information of the product. Note that these images may include encoded codes such as one-dimensional codes or two-dimensional codes.

[0086] Furthermore, the product information acquiring unit 103 may acquire product information by reading a tag to which an RFID (Radio Frequency Identifier) ​​is attached via a reading device. When an RFID is used, the reading device is an RFID reader.

[0087] Furthermore, the product information acquisition unit 103 may acquire product information by selecting product information from the results of a product search. For example, the method of product search is not particularly limited. Product search may be performed by text. Product search may be performed by image. More specifically, for example, the product information acquisition unit 103 may acquire product information by selecting the product that the customer wants to purchase from the displayed product images.

[0088] The product information acquisition unit 103 may also acquire product information by accepting input of a product code represented by numbers or letters via an input device. Examples of the input device include a touch panel display and a keyboard that can input numbers and letters.

[0089] Here, the product information registration process will be described in detail using an example of reading a product code attached to a product. FIG. 15 is an explanatory diagram showing an example of reading a product code. When the product information acquisition unit 103 reads a product code (product ID information) via the imaging device of the mobile terminal device 10, for example, the display unit 1010 displays a screen d050 on which the product code can be read. For example, the screen d050 has a reading portion d051, a display field d052 that displays information about the read product, and a button d053 that displays "Add to Cart" for registering the product information.

[0090] The display field d052 displays the product name, price, etc. The display content of the display field d052 differs before and after the product ID information is read. Before the product ID information is read, the display field d052 displays nothing. After the product ID information is read, the display field d052 displays the product name and price corresponding to the read display ID information. Here, we will explain the processing from when the product ID information is read to when the product name and price are displayed in the display field d052 and the product information is registered in the purchase product list. When the product ID information is read by the reading unit d051, the product information acquisition unit 103 transmits the read product ID information to the POS server 11. The list generation unit 112 of the POS server 11 may transmit the product name and price corresponding to the received product ID information to the customer's mobile terminal device 12. The display unit 1010 then displays the product name, price, etc. in the display field d052. The display field d052 shown in FIG. 15 displays the product name "Biscuits" and the product price "252 yen."

[0091] When the button d053 is tapped, the product information acquisition unit 103 transmits a product information registration request to the POS server 11. For example, the registration request may include, in addition to the product information, information on the customer's ID and information on the ID of the mobile terminal device 10 for the store. The list generation unit 112 of the POS server 11 updates the purchased product list based on the received information. In other words, the list generation unit 112 functions as a registration unit that registers product information. The display unit 1010 may then display the product information registered in the purchased product list together with information indicating the customer mode.

[0092] FIG. 16 is an explanatory diagram showing an example display of a purchased item list. The display unit 1010 displays a screen d060 corresponding to the received purchased item list. The screen d060 includes, for example, a summary field d061 of the purchased item list, a details field d062, an add item button d064, a payment button d065, a cancel transaction button d066, and an operator's name display field d067. The summary field d061 displays information such as the total quantity of items registered in the purchased item list, the total purchase price including tax, and the store name. The details field d062 displays information such as the name, purchase quantity, unit price, discount rate, and discount amount of each item registered in the purchased item list. For example, the details field d062 may include a purchase quantity input field d063 for each item. Furthermore, the details field d062 may display product information in reverse chronological order, for example, based on the most recently registered item. The details field d062 may also allow the user to specify the display order of the product information, for example.

[0093] Furthermore, when the purchase quantity input field d063 is tapped, the display unit 1010 may display a screen (not shown) on which a number can be selected, superimposed on part or all of the screen d060. The quantity receiving unit 104 then receives the selected number as the purchase quantity. The quantity receiving unit 104 then transmits the received purchase quantity to the POS server 11. The list generation unit 112 of the POS server 11 then updates the purchase item list according to the received purchase quantity. The list generation unit 112 then transmits the updated purchase item list to the store-use mobile terminal device 10. The display unit 1010 then displays the purchase item list with the updated purchase quantity. The method for changing the purchase quantity is not particularly limited. For example, although not shown, an input field for inputting the purchase quantity may be provided on the screen d060 from which a product code can be read, as shown in FIG. 15.

[0094] When the add product button d064 is pressed on the screen d060 of FIG. 16, the display unit 1010 may display a screen d050 as shown in FIG. 15 that allows the product code to be read.

[0095] When the transaction cancel button d066 is pressed, the transaction is canceled, and the display unit 1010 may display a screen d001 for accepting a mode as shown in FIG. 9, or a screen d010 for accepting an ID and password as shown in FIG.

[0096] 16, when the payment button d065 is pressed, the store-use mobile terminal device 10 proceeds to payment processing, which will be described later.

[0097] The name display field d067 displays the name of the customer who is the user. Note that, when a member ID (identification information of the customer) is accepted, the customer's name can be displayed in the name display field d067. For example, when a member ID is accepted as in the screen d010 shown in FIG. 10, the name display field d067 may be provided. When a member ID is not accepted as in the screen d001 shown in FIG. 9, the name display field d067 may not be included in the screen d060, or the name display field d067 may be blank. The customer's name is identified from the member DB 115 using the member ID information described above. To enable a store clerk to immediately recognize that the store-use mobile terminal device 10 is in the self-scan mode, a title that is not used in the store clerk mode may be added to the name in the name display field. For example, the display unit 1010 may add a title such as "Mr." or "Dear." Note that, when a name or the like is entered without accepting a member ID, the entered name may be displayed in the name display field d067.

[0098] Furthermore, to make it possible to determine that the self-scan mode is being used, the display unit 1010 may change the background color of the screen d060 to be different from the background color of the purchase item list screen in the store clerk mode. The display unit 1010 may also display information indicating the self-scan mode on the screen d060. The type of information indicating the self-scan mode is not particularly limited. For example, the information indicating the self-scan mode may be a picture, a letter, a number, a color, or a combination of these. Similarly, the display unit 1010 may also display information indicating the self-scan mode on each screen subsequently used in the self-scan mode.

[0099] The screen d060 may also include point information contained in the member DB 115. The screen d060 may also include information such as the remaining battery level and the time.

[0100] <Flowchart of product registration process in self-scan mode> FIG. 17 is a flowchart showing an example of a product registration process. In FIG. 17, the operator of each process is a customer. The product registration process here is the product registration process in the self-scan mode in step S103 shown in FIG. 14. The product information acquisition unit 103 determines whether product information has been acquired (step S1101). In step S1101, the product information acquisition unit 103 acquires product information by reading a product code using an imaging device or the like. As described above, the product information here is not particularly limited. The acquired product information may be product ID information. Alternatively, the product information may be product image data or feature information obtained from the product image data. Note that in step S1101 in FIG. 17, the product information acquisition unit 103 may acquire product information and determine whether the button d053 displaying "Add to Cart" shown in FIG. 15 has been tapped. If the product information has been acquired (step S1101: Yes), the product information acquisition unit 103 transmits the product information to the POS server 11 (step S1102). Next, the list generation unit 112 of the POS server 11 updates the purchased product list based on the received product information (step S1103). The list generation unit 112 transmits the purchased product list to the store-use mobile terminal device 10 (step S1104). The display unit 1010 displays the purchased product list (step S1105).

[0101] After step S1105 or step S1101 (No), the quantity receiving unit 104 determines whether a change in quantity has been received (step S1106). If a change in quantity has been received (step S1106: Yes), the quantity receiving unit 104 transmits the received quantity in association with the product information of the product whose quantity will be changed (step S1107). The list generation unit 112 updates the purchased product list based on the product information and quantity (step S1108). The list generation unit 112 transmits the updated purchased product list (step S1109). The display unit 1010 displays the purchased product list (step S1110).

[0102] If step S1110 or step S1106 is No, the settlement information management unit 107 determines whether or not a payment is being made (step S1111). In step S1111, for example, the settlement information management unit 107 accepts a payment process when the payment button d065 on the screen d060 shown in FIG. 16 is tapped. That is, in step S1111, the settlement information management unit 107 determines that a payment is being made when the payment button d065 on the screen d060 shown in FIG. 16 is tapped (step S1111: Yes). In step S1111, the settlement information management unit 107 determines that a payment is not being made when the payment button d065 on the screen d060 shown in FIG. 16 is not tapped (step S1111: No). If a payment is not being made (step S1111: No), the store-use mobile terminal device 10 returns to step S1101. On the other hand, if payment is required (step S1111: Yes), the store-use mobile terminal device 10 ends the product registration process and returns. This causes the system 1 to proceed to payment processing, which follows the product registration process shown in Fig. 14. As shown in Fig. 14, in the case of the self-scan mode, the system 1 proceeds to payment processing in the self-scan mode (step S104).

[0103] 17 is an example. For example, the step of acquiring product information and the step of changing the purchase quantity may be different flowcharts.

[0104] <Payment processing in self-scan mode> Next, the payment process in self-scan mode will be described. In self-scan mode, the payment method acceptance unit 105 accepts a payment method. For example, the payment method acceptance unit 105 accepts a payment method from among cash payment and electronic payment. For example, the payment methods include cash payment and electronic payment. As described above, the type of electronic payment is not particularly limited. Furthermore, the payment method acceptance unit 105 may accept an electronic payment method from among a plurality of electronic payment methods. The method of accepting a payment method is not particularly limited. For example, the payment method acceptance unit 105 may accept a payment method by an operator selecting the payment method from a selection button on the screen. An example of accepting a payment method will be described using Figure 18. In the example of Figure 18, credit card payment will be described as an example of electronic payment.

[0105] FIG. 18 is an explanatory diagram showing an example of selection of a payment method. The display unit 1010 displays a screen d070 that can accept selection of a payment method between cash payment and credit card payment. The screen d070 has a cash payment button d071-1 that allows selection of cash payment, and a credit card payment button d071-2 that allows selection of credit card payment. Furthermore, the screen d070 may have a confirmation button d073 that confirms the payment method. The screen d070 may also have a display field d072 for displaying the customer's name.

[0106] Furthermore, for example, the display unit 1010 may control the display of the screen d070 so that the color of the tapped button differs from the color of the button before it was tapped.

[0107] For example, if the cash payment button d071-1 is tapped and then the confirm button d073 is tapped, the payment method acceptance unit 105 accepts cash payment. On the other hand, if the credit payment button d071-2 is tapped and then the confirm button d073 is tapped, the payment method acceptance unit 105 accepts credit payment.

[0108] Next, in the self-scan mode, for example, in the case of credit card payment, the payment method acceptance unit 105 further accepts the selection of the device that will perform the payment. Note that in the self-scan mode, in the case of cash payment, the settlement device 14 performs the payment.

[0109] FIG. 19 is an explanatory diagram showing an example of accepting the selection of a device for performing payment. The display unit 1010 displays a screen d080 that can accept the selection of a device for performing payment. The screen d080 has, for example, a button d081-1 that can select the settlement device 14 and a button d081-2 that can select the customer's mobile terminal device 12. Furthermore, the screen d080 may have a confirmation button d083 that can confirm the selection of the device for performing payment. The screen may also include a display field d082 for the customer's name.

[0110] When the button d081-1, which allows the selection of the settlement device 14, is tapped and then the confirmation button d083 is tapped, the payment method acceptance unit 105 accepts the payment using the settlement device 14. When the button d081-2, which allows the selection of the customer's mobile terminal device 12, is tapped and then the confirmation button d083 is tapped, the payment method acceptance unit 105 accepts the payment using the customer's mobile terminal device 12.

[0111] <<Settlement by settlement device 14>> First, we will explain payment by the settlement device 14. The output unit 109 outputs settlement information based on the acquired product information so that it can be read by the settlement device 14. More specifically, the settlement information management unit 107, for example, notifies the POS server 11 of a payment request to execute payment by the settlement device 14. For example, upon receiving the payment request, the settlement information generation unit 111 of the POS server 11 generates settlement information based on a list of products purchased by the customer. For example, the settlement information may be encoded when displayed so that it can be read by other devices. The encoded settlement information is called, for example, a settlement code. The settlement code is not particularly limited. The settlement code may be represented by a one-dimensional code such as a barcode or a two-dimensional code. The settlement information management unit 107 passes the generated settlement information to the output unit 109 of the store-use mobile terminal device 10.

[0112] The settlement information includes at least information identifying a customer's purchase list. The information identifying the purchase list is, for example, customer ID information. In addition to the information identifying the customer's purchase list, the settlement information may also include purchase price information. The purchase price information includes, for example, information on the total purchase price of the products to be purchased.

[0113] Here, there are two different payment procedures for settlement by the settlement device 14, depending on the information contained in the settlement information. We will explain payment procedure A when the settlement information includes purchase price information, and payment procedure B when the settlement information does not include purchase price information. First, we will briefly explain payment procedure A. After the settlement device 14 reads the settlement code, it makes the settlement based on the purchase price information included in the settlement information. After decoding the settlement code to determine the settlement information, the settlement device 14 makes the settlement based on the purchase price information included in the settlement information. Then, the settlement device 14 notifies the completion of the settlement for the purchased item list based on information identifying the purchased item list. Then, the POS server 11 records sales based on the purchased item list for which the settlement has been completed. Furthermore, the POS server 11 may delete the purchased item list from the purchased item list DB. This concludes the explanation of payment procedure A.

[0114] Next, a brief description of payment procedure B will be given. The settlement device 14 reads a settlement code, which is encoded settlement information, from the store-use mobile terminal device 10 and obtains information identifying the purchase list. The settlement device 14 then decodes the settlement code to determine the settlement information, thereby obtaining the information identifying the purchase list. The settlement device 14 then transmits a payment request based on the information identifying the purchase list to the POS server 11. Upon receiving the payment request, the POS server 11 transmits information on the purchase list or purchase prices to the settlement device 14. The settlement device 14 then performs payment based on the information identifying the purchase list or purchase price information. The settlement device 14 then notifies the settlement device 14 of the completion of payment for the purchase list based on the information identifying the purchase list. The POS server 11 then notifies the settlement device 14 of the completion of payment for the purchase list based on the information identifying the purchase list. The POS server 11 then records sales based on the purchase list for which payment has been completed. The POS server 11 may also delete the purchase list from the purchase list DB. This concludes the explanation of payment procedure B.

[0115] In the following description, payment procedure A will be used, but payment procedure B may also be used.

[0116] Here, the settlement information for payment by the settlement device 14 may include other information in addition to information identifying the purchased item list and information on the purchase price. For example, the settlement information may include information included in the purchased item list. The information included in the purchased item list is product information and purchase quantity information for the products. The product information included in the settlement information may be, for example, a product ID, product name, and unit price of the product. Furthermore, if the purchased item list includes member ID information, the settlement information may also include member information (such as member name) obtained from the member ID information. The settlement information may also include information on the ID of the store-use mobile terminal device 10 that performed the product registration process. The settlement information may also include, for example, store information for the store to which payment is made. Alternatively, the settlement information may also include information on a transaction ID. The settlement information may also include information indicating the mode of the store-use mobile terminal device 10. Here, the information indicating the mode indicates that it is self-scan mode. In this way, by including in the settlement information information indicating the operator of the store-use mobile terminal device 10, information on the ID of the store-use mobile terminal device 10, information indicating the mode, etc., it is possible to facilitate analysis of the cause when a problem occurs during payment due to the details of product registration, etc. Note that the settlement information does not need to include some of the above-mentioned information. Furthermore, the settlement information may include information other than the above-mentioned information.

[0117] The output unit 109 outputs the settlement information so that it can be read by the settlement device 14. The output method is not particularly limited. As described above, for example, the display unit 1010 may display a settlement code that encodes the settlement information.

[0118] FIG. 20 is an explanatory diagram showing an example of a display of a settlement code that can be read by the settlement device 14. The display unit 1010 displays a screen d090 that includes a settlement code that encodes settlement information. For example, the screen d090 includes a settlement code display field d091, a total quantity display field d093, and a purchase price display field d094. The total quantity display field d093 displays the total purchase quantity of the products purchased by the customer. The purchase price display field d094 displays, for example, the total price, including tax, of the products purchased by the customer. The screen d090 also includes a complete button d092 that is tapped after payment is completed.

[0119] For example, a customer takes a store-use mobile terminal device 10, on which a settlement code is displayed, to a settlement device 14. Then, in the case of a manned settlement device 14, the reading unit 141 of the settlement device 14 reads the settlement code through operation by a store clerk. In the case of an unmanned settlement device 14, the reading unit 141 of the settlement device 14 reads the settlement code through operation by the customer. Then, the settlement unit 142 makes the settlement based on the read settlement code. Because the payment is made by the settlement device 14, there are no particular limitations on the payment method.

[0120] After the payment is completed, the issuance control unit 143 causes the printer to print a receipt. This printer may be, for example, included in the settlement device 14. Alternatively, this printer may be, for example, a device connected to the settlement device 14 via the communication network 16, like the printer 13.

[0121] A receipt may include, for example, purchase price information, membership information, and store information. The purchase price information included in a receipt includes product information, the quantity purchased, the discount amount, the discount rate, whether a coupon was used, the total purchase price, the deposit amount, and the change amount. Product information included in a receipt includes, for example, the product's product code, product name, and unit price. Membership information included in a receipt includes, for example, the customer's membership ID, member name, and points. Store-related information included in a receipt includes, for example, the store name, store ID, store address, and store contact information. Although not shown, a database managing store information may be pre-stored in the POS server 11 or the like. The receipt may also include the ID of the mobile terminal device 10 for the store where the product was registered and the ID of the settlement device 14. If the settlement device 14 is staffed, the receipt may also include staff information about the staff who operated the settlement device 14. Here, staff information includes the staff ID and name. The receipt may also include information such as the date and time the payment was completed. The receipt may also include receipt ID information. The receipt may also include transaction ID information. The receipt may also include information indicating that the payment was made in cash. The information indicating a cash payment may be, for example, text or a picture indicating a cash payment, the deposit amount, the amount of change, etc. The receipt may also include information indicating the mode of the store's mobile terminal device 10. In this case, the information indicating the mode indicates that it is in self-scan mode. In this way, by including information indicating the operator of each device and information indicating the mode, etc., the receipt can facilitate analysis of the details of product registration and the cause of any payment problems that may occur. Note that the receipt does not need to include some of the above information. The receipt may also include information other than the above information.

[0122] After completing the payment, the customer taps a completion button d092 included in the screen d090 of the store-use mobile terminal device 10 shown in Fig. 20. When the completion button d092 is tapped, the display unit 1010 may again display the screen d001 shown in Fig. 9 or the screen d010 shown in Fig. 10.

[0123] Electronic Payment Using Customer's Mobile Terminal Device 12 Next, an example of electronic payment using a customer's mobile terminal device 12 will be described. Portable store-use mobile terminal devices, such as smartphones and tablets, may not be connected to a device capable of reading cards such as credit cards, debit cards, and point cards, or a device capable of reading near-field communication IC cards. This electronic payment method allows customers to make electronic payments even if the store-use mobile terminal device 10 does not have a reading device for electronic payments. The output unit 109 outputs payment information based on the purchase list so that it can be read by the customer's mobile terminal device 12. The payment information for electronic payments using the customer's mobile terminal device 12 includes at least store information about the store to which payment is made and information about the purchase price based on the purchase list. The payment information for payments using the customer's mobile terminal device 12 includes store information about the store to which payment is made in addition to information identifying the purchase list. Therefore, the payment information for electronic payments using the customer's mobile terminal device 12 differs from the payment information for payments using the aforementioned payment device 14.

[0124] The settlement information may also include product information and purchase quantity information, as described in the settlement by the settlement device 14. The settlement information may also include member information, such as the member ID information of the customer who operated the product registration process. The settlement information may also include ID information of the store-use mobile terminal device 10 that performed the product registration process. The settlement information may also include transaction ID information. The settlement information may also include information indicating the mode of the store-use mobile terminal device 10. Here, the information indicating the mode indicates that it is self-scan mode. The settlement information may not include some of the above-mentioned information. The settlement information may also include information other than the above-mentioned information. For example, the settlement information may also include other information depending on whether or not a specific application is installed.

[0125] The method for outputting the settlement information is not particularly limited. For example, the display unit 1010 may display a settlement code that encodes the settlement information as described above. Then, the reading unit 121 of the customer's mobile terminal device 12 reads the settlement code. When the settlement code is displayed on the screen, the reading unit 121 of the customer's mobile terminal device 12 reads the settlement code using an imaging device.

[0126] A more detailed example will be described. Processing differs depending on whether or not a specific application program is present. The specific application program will be referred to hereinafter as a store app (store application). The store app runs on the customer's mobile terminal device 12. The store app is, for example, an application program that can set customer payment information. As described above, customer payment information is information related to the customer's electronic payment used for electronic payment. More specifically, the payment information is, for example, information used for electronic payment by card. In the case of credit card payment, the payment information is, for example, information such as the credit card payment number, expiration date, name, and security code. In the case of point payment, the payment information is, for example, information such as the point payment number. In the case of debit payment, the payment information is, for example, information such as the debit card number, name, and PIN, similar to credit card payment. In the case of electronic money payment, the payment information is, for example, information such as a number or ID that can be linked to electronic money. For example, the store app can perform registered electronic payments other than cash payments.

[0127] The application presence / absence reception unit 106 receives the presence or absence of a store application. Fig. 21 is an explanatory diagram showing an example of reception of the presence or absence of a store application. The display unit 1010 displays a screen d100 that can receive the presence or absence of a store application. For example, the screen d100 has a Yes button d101-1 for receiving the presence or absence of a store application, and a No button d101-2 for receiving the presence or absence of a store application.

[0128] For example, when the Yes button d101-1 is tapped, the application presence / absence receiving unit 106 receives that the store app is installed on the customer's mobile terminal device 12. For example, when the No button d101-2 is tapped, the application presence / absence receiving unit 106 receives that the store app is not installed on the customer's mobile terminal device 12.

[0129] <<When the store app is not installed on the customer's mobile terminal device 12>> First, a case will be described in which the store app is not installed on the customer's mobile terminal device 12.

[0130] If the store app is not installed on the customer's mobile terminal device 12, the settlement information further includes information for the customer's mobile terminal device 12 to accept input of the customer's payment information. This information is, for example, information about the URL of a page that has an input field into which payment information can be input. This information is called link information. The page here is, for example, an HTML page.

[0131] The display unit 1010 displays, for example, settlement information so that it can be read by the customer's mobile terminal device 12. The reading unit 121 of the customer's mobile terminal device 12 reads, for example, the settlement information. When the settlement information is read, the settlement unit 122 accepts input of the customer's payment information based on the read settlement information. The settlement unit 122 performs electronic payment with the payment server 15 using the input customer's payment information and the settlement information.

[0132] Here, a detailed explanation will be given using credit card payment as an example. FIG. 22 is an explanatory diagram showing an example of how a payment code is displayed. Specifically, the display unit 1010 displays a screen d110 that includes, for example, a payment code (a two-dimensional code in FIG. 22) that encodes payment information. The screen d110 includes a display field d111 for the payment code (two-dimensional code), a display field d114 for the total purchase quantity, a display field d115 for the total purchase price, and a display field d116 for the payment method. The screen d110 also has a complete button d112 that is pressed after payment is completed, and a button d113 that displays "Add to Cart" to abort payment and return to the product registration process.

[0133] The reading unit 121 of the customer's mobile terminal device 12 reads, for example, the settlement code (two-dimensional code) displayed in the display field d111. This causes the payment information receiving unit 125 to launch a browser where payment information can be input and a page where payment can be requested from the payment server 15 can be viewed. Then, the payment information receiving unit 125 uses the browser to open the page of the URL based on the link information.

[0134] FIG. 23 is an explanatory diagram showing an example of a page display on which payment information can be entered. The display unit 1210 of the customer's mobile terminal device 12 displays a screen d120 of a page based on the link information. The screen d120 includes, for example, a display field d121 for transaction details and a display field d122 for payment procedures. The display field d121 for transaction details displays, for example, the name of the store to which payment is made and the total purchase price. The display field d122 for payment procedures includes an input field d123 for the credit card number, an input field d124 for the name printed on the credit card, an input field d125 for the credit card expiration date, an input field d126 for the security code, and an input field d127 for the number of payments. The input field d127 for the number of payments may be a pull-down menu. The screen d120 also includes a confirm button d128 for confirming the credit card payment and a cancel button d129 for canceling the credit card payment procedure midway.

[0135] The payment information receiving unit 125 receives input into each input field. When the Confirm button is tapped, the payment unit 122 performs electronic payment with the payment server 15 based on the received payment information and settlement information. Here, performing electronic payment by the payment unit 122 means, for example, requesting electronic payment from the payment server 15.

[0136] The method for accepting payment information is not limited to the example using the input field on the screen d120. For example, the payment information accepting unit 125 may accept credit information (payment information) by extracting the credit information written on the credit card from an image of the credit card captured by an imaging device.

[0137] FIG. 24 is an explanatory diagram showing an example of a payment completion display. The display unit 1210 of the customer's mobile terminal device 12 displays a payment completion screen d130. The screen d130 has, for example, a display field d131 for transaction details and a display field d132 for payment procedures. As in the example of FIG. 23, the display field d131 for transaction details displays the name of the store to which payment is made, the total purchase price, etc. The display field d132 for payment procedures displays the name of the credit card company, the number of payments, the credit card number, etc.

[0138] The screen d130 also has an end button d134 for ending the display of the screen d130. When the end button d134 is tapped, the page of the screen d130 is ended in the browser.

[0139] Furthermore, when the payment is completed, the customer taps the complete button d112 shown on the screen d110 of the store mobile terminal device 10 shown in FIG. 22. This completes the electronic payment in the absence of a store app. This allows the customer to make an electronic payment even if the store mobile terminal device 10 does not have a reading means for electronic payment.

[0140] Furthermore, once the electronic payment is completed, the issuance control unit 1011 of the store-use portable terminal device 10 may cause the printing device 13 to issue a receipt. In detail, the receipt may include, for example, purchase price information, member information, and store-related information. The purchase price information, member information, and store-related information included in the receipt may be the same as those included in receipts issued for cash payments. The receipt may also include the ID information of the store-use portable terminal device 10 that registered the product. The receipt may also include information such as the date and time the payment was completed. The receipt may also include the receipt ID information. The receipt may also include transaction ID information. The receipt may also include information indicating that the payment was made electronically. The information indicating the electronic payment may be, for example, text or pictures indicating the payment method, such as the name of the payment method, or part of the payment information. The receipt may also include information indicating the mode of the store-use portable terminal device 10. In this case, the information indicating the mode indicates that the mode is self-scan mode. Note that the receipt does not necessarily include some of the above-described information. The receipt may also include information other than the above-described information.

[0141] <<When the store app is on the customer's mobile terminal device 12>> Next, an example in which a store app is present on the customer's mobile terminal device 12 will be described. The output unit 109 of the store mobile terminal device 10 outputs payment information so that it can be read by the store app. As described above, the payment information includes store information about the store that is the payment recipient and information about the purchase price. The payment information may also include other information as described above. However, if the store app is present on the customer's mobile terminal device 12, payment information is set or can be registered in the store app, so the payment information does not need to include information for the customer's mobile terminal device 12 to accept input of the customer's payment information. This information is the link information described above. Note that, as described above, if the store app is not present on the customer's mobile terminal device 12, the payment information includes link information. The payment information may be output as a payment code or the like that encodes the payment information, as in the example in which the store app is not present. Note that an example screen may be similar to screen d110 shown in FIG. 22.

[0142] The reading unit 121 of the customer's mobile terminal device 12 reads the settlement information using the store app. That is, the store app is launched on the customer's mobile terminal device 12. The store app then reads the settlement information using the imaging device. The payment unit 122 then performs electronic payment via the payment server 15 using the customer's payment information set in the store app and the read settlement information. Although not shown, the display unit 1210 may display a screen indicating that the electronic payment has been completed by the store app. This concludes the description of electronic payment using the customer's mobile terminal device 12.

[0143] Once the electronic payment is completed, the issuance control unit 1011 of the store mobile terminal device 10 may cause the printer 13 to print a receipt. In detail, the receipt may include the same information as a receipt without a store app. The receipt may also include information indicating that the electronic payment was made using the store app.

[0144] Furthermore, if the store app can use the printer 13 in the store, an issuance control unit (not shown) of the customer's mobile terminal device 12 may cause the printer 13 to print a receipt.

[0145] In addition, in some cases, the customer's payment information can be input into the store-use mobile terminal device 10 in electronic payment. In such cases, the store-use mobile terminal device 10 may perform the same processing as when the customer's mobile terminal device 12 does not have a store app. For example, the payment unit 108 of the store-use mobile terminal device 10 accepts the customer's payment information. The display unit 1010 displays the page of the link information described above, for example, via a browser. For example, the display unit 1010 may display a screen similar to screen d120 shown in FIG. 23. Then, the payment unit 108 performs electronic payment via the payment server 15 based on the payment information and settlement information accepted via the browser. Furthermore, the display unit 1010 may display a screen similar to screen d130 of FIG. 24 as a screen after payment is completed.

[0146] <Flowchart of payment processing in self-scan mode> The payment process in self-scan mode will be described using Figs. 25 to 27. The payment process in self-scan mode is the payment process in self-scan mode in step S104 shown in Fig. 14. Fig. 25 is a flowchart showing an example of the payment process in self-scan mode. The display unit 1010 displays a selection screen for the device to be used for payment (step S1201). In step S1201, for example, the display unit 1010 may display information about the purchase price on the selection screen for the payment method.

[0147] Next, the payment method acceptance unit 105 determines whether the device used for payment is the settlement device 14 (step S1202). If the device used for payment is the settlement device 14 (step S1202: Yes), the settlement information management unit 107 transmits a request to generate a settlement code (payment request) to the POS server 11 (step S1203). As described above, the settlement code is an encoded version of the settlement information. Here, the explanation will be given using the above-mentioned payment procedure A in which the settlement information includes information on the purchase price. Therefore, the settlement information includes at least information identifying the purchased product list and information on the purchase price, for example. In addition to these, the settlement information may also include information on the ID of the mobile terminal device 10 for the store and information on the operator's membership ID. As described above, the settlement information may also include other information. The settlement information generation unit 111 generates a settlement code (step S1204). In step S1204, the settlement information generation unit 111 calculates the total purchase price based on the purchased item list. Then, in step S1204, the settlement information generation unit 111 generates settlement information. In step S1204, the settlement information generation unit 111 encodes the settlement information to generate a settlement code. The settlement information generation unit 111 transmits the settlement code to the mobile terminal device 10 for the store (step S1205). The display unit 1010 displays a screen including the settlement code (step S1206). The customer moves around with the mobile terminal device 10.

[0148] The reading unit 141 of the settlement device 14 reads the settlement code (step S1207). Next, the display unit 144 displays a payment screen based on the read settlement code (step S1208). In reality, processing such as decoding the settlement code is required, but since this is existing technology, explanation will be omitted. The screen here is not particularly limited as long as it uses existing functions of the settlement device 14. Then, the settlement unit 142 performs payment (step S1209). In step S1209, the payment method may be any payment method available in the settlement device 14, and is not particularly limited to cash payment, electronic payment, etc. The issuance control unit 143 issues a receipt (step S1210), ending the operation of the flow. The information included in the receipt is as described above. After step S1209, the display unit 144 may display a payment completion screen.

[0149] Furthermore, although not shown, once payment is complete, the sales management unit 113 of the POS server 11 updates the sales information based on the payment details. More specifically, the payment unit 142 notifies the POS server 11 of the purchased item list for which payment has been completed, based on the information identifying the purchased item list included in the settlement information and the payment details. The payment details may be information such as which payment method was used. The sales management unit 113 then updates the sales DB 118 based on the purchased item list for which payment has been completed and the payment details. Furthermore, the list generation unit 112 may delete the purchased item list for which payment has been completed from the purchased item list DB 119.

[0150] Furthermore, in step S1209, the settlement unit 142 may perform the aforementioned settlement procedure B when the settlement information does not include information on the purchase price. That is, the settlement information includes at least information that identifies the purchase item list. In step S1209, for example, the settlement unit 142 transmits a settlement request based on the information that identifies the purchase item list. Then, in step S1209, upon receiving the settlement request, the settlement information generation unit 111 transmits the purchase item list or purchase price information to the settlement device 14. In step S1209, the settlement device 14 performs settlement based on the purchase item list or purchase price information. The processing in the settlement device 14 and the processing in the POS server 11 after the settlement is completed are the same as in payment procedure A, and therefore will not be described again.

[0151] On the other hand, if the device used for payment is not the settlement device 14 (step S1202: No), the store's mobile terminal device 10 performs credit card payment processing (step S1211). If it is not the settlement device 14, for example, the customer's mobile terminal device 12 is used for payment. Payment using the customer's mobile terminal device 12 is electronic payment. In step S1211, credit card payment is given as an example of electronic payment.

[0152] 26 and 27 are flowcharts showing the credit card payment process. The credit card payment process shown in FIGS. 26 and 27 is a detailed explanation of the credit card payment process in step S1211 shown in FIG. 25. The display unit 1010 displays a selection screen for determining whether or not a store app is available (step S1301). The app availability reception unit 106 determines whether or not a store app is available (step S1302). If a store app is available (step S1302: Yes), the settlement information management unit 107 sends a request to generate a settlement code (payment request) (step S1303). The settlement information generation unit 111 generates a settlement code by encoding the settlement information (step S1304). The settlement code is readable by the customer's mobile terminal device 12. In step S1304, the settlement information generation unit 111 calculates the purchase price based on the purchased item list. Then, in step S1304, the settlement information generation unit 111 generates settlement information. In step S1304, the settlement information generation unit 111 generates a settlement code by encoding the settlement information. The settlement information includes, for example, at least information on the purchase price and information on the payee. In addition to this information, the settlement information may also include membership information such as information on the operator's membership ID and information on the ID of the mobile terminal device 10 for the store. Next, the settlement information generation unit 111 transmits the generated settlement code (step S1305). The display unit 1010 displays a payment screen including the settlement code (step S1306).

[0153] The customer's mobile terminal device 12 starts the store app in response to an operation by the customer. The reading unit 121 reads the settlement code from the store mobile terminal device 10 using the store app (step S1307). The payment unit 122 performs credit card payment using the store app (step S1308). More specifically, in step S1308, the payment unit 122 performs credit card payment via the payment server 15 based on the payment information set in the store app and the settlement code (settlement information).

[0154] Next, the display unit 1210 displays a payment completion screen (step S1309). When the credit card payment is completed, the issuance control unit 1011 of the store mobile terminal device 10 causes the printer 13 to issue a receipt (step S1310). The information included in the receipt is as described above. The system 1 then ends the operation of the flow when the store app is present. Although not shown, when the payment is completed, the sales management unit 113 of the POS server 11 updates the sales information based on the payment details.

[0155] On the other hand, if there is no store app (step S1302: No), the explanation will move to FIG. 27, where the settlement information management unit 107 sends a request to generate a settlement code (payment request) (step S1401). The settlement information generation unit 111 generates a settlement code (step S1402). In step S1402, the settlement information generation unit 111 calculates the purchase price. Then, in step S1402, the settlement information generation unit 111 generates the settlement code by encoding the settlement information. The settlement code is readable by the customer's mobile terminal device 12. The settlement information when there is no store app includes at least information on the purchase price, information on the payee, and link information, for example. In addition to this information, the settlement information may also include information on the member ID and information on the mobile terminal device ID. Next, the settlement information generation unit 111 sends the generated settlement code (step S1403). The display unit 1010 displays a screen including the settlement code (step S1404).

[0156] The reader 121 of the customer's mobile terminal device 12 reads the settlement code from the store's mobile terminal device 10 (step S1405). The payment information accepting unit 125 uses a browser to open a page where payment information can be entered based on link information included in the read settlement code. The payment information accepting unit 125 accepts the payment information via the page (step S1406). The settlement unit 122 makes a credit card payment to the payment server 15 (step S1407). More specifically, in step S1407, the settlement unit 122 makes a credit card payment via the payment server 15 based on the accepted payment information and settlement code. The display unit 1210 displays a payment completion screen (step S1408). When the credit card payment is completed, the issuance control unit 1011 causes the printer 13 to issue a receipt (step S1409). The information included on the receipt is as described above. The system 1 then ends the operation of the flow when the store app is installed. Although not shown, once the payment is completed, the sales management unit 113 of the POS server 11 updates the sales information based on the information indicating the purchased product list and the payment details.

[0157] According to this electronic payment method, even if the store's mobile terminal device 10 does not have a means for reading electronic payments, customers can make electronic payments depending on whether or not their mobile terminal device 12 has a store app.

[0158] This concludes the explanation of the payment process in the self-scan mode.

[0159] <Product registration process in emergency mode> Next, the product registration process in the emergency mode will be described. In the emergency mode, the product information acquisition unit 103 acquires information about the product purchased by the customer through operation by a store clerk. The method of acquiring the product information may be the same as the product registration process in the self-scan mode, except that the operator is a store clerk. This allows the store-use mobile terminal device 10 to be used as an emergency product registration device operated by a store clerk, such as for BCP measures. The list generation unit 112 of the POS server 11 may also update the purchased product list. The display unit 1010 may then display the product information registered in the purchased product list together with information indicating the emergency mode. The type of information indicating the emergency mode is not particularly limited. For example, the information indicating the emergency mode may be information in the form of pictures, letters, numbers, colors, or a combination of these. The display unit 1010 may also display information indicating the emergency mode on each screen in other emergency modes.

[0160] FIG. 28 is an explanatory diagram showing an example of a purchased item list in emergency mode. The display unit 1010 displays a screen corresponding to the purchased item list. The screen d150 includes, for example, a purchase item list summary field d151 and a details field d152, similar to the screen in self-scan mode. The screen d150 also includes an add item button d154, a payment button d155, a cancel transaction button d156, a name display field d157 for the store clerk who is the operator, and a mode summary field d158. Details other than the store clerk name display field d157 and the mode summary field d158 may be similar to those of the screen in self-scan mode.

[0161] The name of the clerk is displayed in the name display field d157. When a clerk ID (identification information of the clerk) is accepted, the name of the clerk can be displayed in the name display field d157. For example, when a clerk ID is accepted as in the screen d010 shown in FIG. 10, the name display field d157 may be displayed. When a clerk ID is not accepted as in the screen d001 shown in FIG. 9, the name display field d157 may not be included in the screen d150, or the name display field d157 may be blank. The presence or absence of a title is not limited. Furthermore, the screen d150 of the purchased item list in emergency mode differs from the screen of the purchased item list in self-scan mode in that information indicating the emergency mode is displayed. To distinguish from the self-scan mode, the name of the clerk in the name display field d157 may not have a title. Alternatively, to distinguish from the self-scan mode, a title different from the title assigned to the customer's name in self-scan mode may be used.

[0162] Furthermore, information indicating the emergency mode is displayed in the mode summary field d158 on the screen d150. In Fig. 28, the word "emergency" is displayed in the mode summary field d18. Furthermore, for example, the background color of the screen d150 may be set so that it is possible to distinguish that the mode is emergency mode.

[0163] <Flowchart of product registration process in emergency mode> The product registration process in emergency mode is the product registration process shown in FIG. 17 (step S107 in FIG. 14). The flowchart of the product registration process in emergency mode may be the same as the flowchart of the product registration process in self-scan mode shown in FIG. 17, although the operator is different. Therefore, detailed explanation using figures will be omitted. Note that if the answer is Yes in step S1111 shown in FIG. 17, in the case of emergency mode, the store-use mobile terminal device 10 ends the product registration process and returns. Therefore, in the case of emergency mode, the system 1 proceeds to the emergency mode payment process (step S108) that follows the product registration process (step S107) shown in FIG. 14.

[0164] <Payment processing in emergency mode> Next, the payment process in emergency mode will be described. As described above, emergency mode is a BCP measure, and assumes that the settlement device 14 cannot be used. However, the process of generating settlement information may be performed by the POS server 11.

[0165] In the emergency mode, the payment method acceptance unit 105 accepts the selection of a payment method. Specifically, the payment method acceptance unit 105 accepts the selection of a payment method between cash payment and electronic payment. As in the self-scan mode, the electronic payment method is not particularly limited. Furthermore, the payment method acceptance unit 105 may accept a payment method from multiple types of electronic payment.

[0166] FIG. 29 is an explanatory diagram showing an example of a payment method selection. In FIG. 29, credit card payment will be explained as an example of electronic payment. The display unit 1010 displays a screen that can accept a selection of a payment method between cash payment and credit card payment. The screen d160 has a cash payment button d161-1 that can select cash payment, and a credit card payment button d161-2 that can select credit card payment. Furthermore, the screen d160 may have a confirmation button d164 that can confirm the payment method.

[0167] The screen d160 may include a display field d162 for the store clerk's name and a mode summary field d163 indicating that the mode is emergency. The mode summary field d163 may be similar to the mode summary field d158 on the purchase item list screen d150 shown in FIG.

[0168] For example, when the confirm button d164 is tapped after the cash payment button d161-1, which allows cash payment to be selected, is tapped, the payment method acceptance unit 105 accepts cash payment. On the other hand, when the confirm button d164 is tapped after the credit payment button d161-2, which allows credit payment to be selected, is tapped, the payment method acceptance unit 105 accepts credit payment.

[0169] Cash payments in emergency mode First, an example of cash payment in emergency mode will be described. In the case of cash payment, the display unit 1010 displays cash settlement information based on the purchased item list. For example, the cash settlement information includes information on the purchase price of the items. In addition to the purchase price information, the cash settlement information may also include information on the total quantity of items, the price of each item, etc.

[0170] The cash settlement information may be generated by the POS server 11. The settlement information management unit 107, for example, notifies the POS server 11 of a settlement request to perform cash settlement using a mobile terminal device. For example, upon receiving the settlement request, the settlement information generation unit 111 of the POS server 11 generates cash settlement information based on a list of purchased items by the customer. The settlement information management unit 107 passes the generated settlement information to the output unit 109 (display unit 1010) of the mobile terminal device 10 for the store.

[0171] 30 and 31 are explanatory diagrams showing an example of cash payment in emergency mode. The display unit 1010 displays a screen d170 for cash payment. The screen d170 includes, for example, a display field d171 for the total purchase quantity, a display field d172 for the total purchase price, an input field d175 for the deposit amount, and a display field d176 for the change amount.

[0172] The total purchase quantity display field d171 displays the total purchase quantity of the products the customer will purchase. The total purchase price display field d172 displays, for example, the total price including tax of the products the customer plans to purchase. In FIG. 30, the display field d172 displays the price including tax, but this is not limited to this. For example, the display field d162 may display both the price excluding tax and the price including tax. The deposit amount input field d175 allows the amount received from the customer to be input. The change amount display field d176 displays the change amount, which is the result of subtracting the total purchase price from the deposit amount. In FIG. 30, the deposit amount has not been input, so nothing is displayed in the change amount display field.

[0173] The screen d170 also includes a button d173 for canceling the cash payment process and returning to the product registration process, and a completion button d174 for completing the cash payment. The screen d170 may also include a mode display field d177 and a display field d178 for the name of the store clerk. The mode display field d177 displays information indicating emergency mode. The display field d178 displays the name of the store clerk in charge. The display field d178 may also display the ID of the store clerk.

[0174] For example, when the settlement unit 108 accepts input of the deposit amount in the deposit amount input field d175, it calculates the amount of change. Then, in Fig. 31, the display unit 1010 displays the calculated amount of change in the change amount display field d176 on the screen d170. Furthermore, when the complete button d174 is tapped, the settlement unit 108 completes the cash settlement.

[0175] Furthermore, once the cash payment is completed, the issuance control unit 1011 of the store mobile terminal device 10 may cause the printing device 13 to issue a receipt. The receipt may include information similar to that included on a receipt issued in self-scan mode. Specifically, the receipt may include, for example, purchase price information, store information, and store clerk information. The purchase price information and store information included on the receipt may be similar to the information on a receipt issued in self-scan mode. The store clerk information may include information such as the store clerk ID and name of the store clerk who operates the store mobile terminal device 10. The receipt may also include the ID of the store mobile terminal device 10 that registered the product. The receipt may also include information such as the date and time the payment was completed. The receipt may also include the receipt ID. The receipt may also include information indicating that the payment was made in cash. The information indicating that the payment was made in cash may include, for example, text or a picture indicating the payment method, such as the name of the payment method, the deposit amount, and the amount of change to be given. Furthermore, if input of a member ID or the like is accepted to award points or the like, the receipt may include member information. The member information included in the receipt may be the same as the information on a receipt issued in self-scan mode. The receipt may also include transaction ID information. The receipt may also include information indicating the mode of the store mobile terminal device 10. In this case, the information indicating the mode indicates emergency mode. Note that the receipt does not need to include some of the above information. The receipt may also include information other than the above information.

[0176] When the cash payment is completed, the payment unit 108 may notify the POS server 11 of the completion of the cash payment. When notifying, information on the customer ID for which the payment has been completed, information on the store, information on the ID of the mobile terminal device 10 for the store, etc. may also be notified. The sales management unit 113 of the POS server 11 updates the sales information. The list generation unit 112 may also delete the purchased product list for which sales have been recorded.

[0177] Furthermore, when the cash payment is completed, the list generation unit 112 may assign a customer ID to the new customer and generate a new purchase item list. More specifically, when the Complete button d174 is tapped, the store-use mobile terminal device 10 may request the POS server 11 to assign a new customer ID. Then, the list generation unit 112 may assign a customer ID to the new customer and generate a new purchase item list. Then, the display unit 1010 may display, as an initial screen, a screen (not shown) in which no product information is registered in the product registration list. This allows the store-use mobile terminal device 10 to perform new product registration processing for the next customer in emergency mode.

[0178] This concludes the explanation of cash settlement in emergency mode.

[0179] Electronic Payments in Emergency Mode Next, the electronic payment process in emergency mode will be described. The electronic payment process in emergency mode is the same as the electronic payment process by the customer's mobile terminal device 12 in self-scan mode. Therefore, a detailed description will be omitted. However, emergency mode differs from self-scan mode in that information indicating emergency mode may be displayed on each screen so that it can be determined that the mode is emergency. As described above, the type of information indicating emergency mode is not particularly limited. Furthermore, the settlement information may be the same as the settlement information in the electronic payment process by the customer's mobile terminal device 12 in self-scan mode. However, if the settlement information includes information indicating the mode, the information indicating the mode indicates that the mode is emergency mode. Furthermore, if the store clerk ID information is received, the store clerk ID information may be included in the settlement information.

[0180] In the electronic payment process in the emergency mode, even if the store's mobile terminal device 10 does not have a means for reading electronic payments and the checkout device 14 cannot be used in the store, the customer can still make electronic payments.

[0181] When the electronic payment is completed, the issuance control unit 1011 of the store-use portable terminal device 10 may cause the printing device 13 to issue a receipt. More specifically, as described in the self-scan mode, when the electronic payment is completed, the Complete button d112 shown on the screen d110 of the store-use portable terminal device 10 in FIG. 22 is tapped. When the Complete button d112 is tapped, the issuance control unit 1011 of the store-use portable terminal device 10 may cause the printing device 13 to issue a receipt. The receipt may include information similar to that included in a receipt issued in the self-scan mode. Specifically, the receipt may include, for example, purchase price information, store information, and store clerk information. The purchase price information and store information included in the receipt may be similar to the information included in a receipt issued in the self-scan mode. The store clerk information included in the receipt may be similar to the information included in a receipt for cash payment in the emergency mode. The receipt may also include the ID information of the store-use portable terminal device 10 that registered the product. The receipt may also include information such as the date and time the payment was completed. The receipt may also include receipt ID information. The receipt may also include information indicating that the payment is electronic. If input of a member ID or the like is accepted to award points or the like, the receipt may also include member information. The member information included in the receipt may be the same as the information on a receipt issued in self-scan mode. The receipt may also include transaction ID information. The receipt may also include information indicating the mode of the store mobile terminal device 10. In this case, the information indicating the mode indicates that it is in emergency mode. Note that the receipt does not need to include some of the above information. The receipt may also include information other than the above information.

[0182] In the emergency mode, when the electronic payment is completed, the list generation unit 112 may assign a customer ID to the new customer and generate a new purchase item list. More specifically, when the complete button d112 shown on the screen d110 of the store-use mobile terminal device 10 shown in FIG. 22 is tapped, the store-use mobile terminal device 10 may request the POS server 11 to assign a new customer ID. Then, the list generation unit 112 may assign a customer ID to the new customer and generate a new purchase item list. Then, the display unit 1010 may display, as an initial screen, a screen (not shown) in which no product information is registered in the product registration list. This allows the store-use mobile terminal device 10 to perform new product registration processing for the next customer in the emergency mode.

[0183] This concludes the description of the electronic payment process in emergency mode.

[0184] <Flowchart of payment processing in emergency mode> The payment process in emergency mode will be described with reference to FIG. 32. The payment process in emergency mode is the emergency mode payment process of step S108 shown in FIG. 14. FIG. 32 is a flowchart showing the payment process in emergency mode. The display unit 1010 of the store-use mobile terminal device 10 displays a payment method selection screen (step S1501). Then, the payment method acceptance unit 105 accepts the payment method. The payment method acceptance unit 105 determines whether the accepted payment method is cash payment (step S1502). If it is cash payment (step S1502: Yes), the settlement information management unit 107 transmits a payment request (step S1503). Upon accepting the payment request, the settlement information generation unit 111 calculates the purchase price (step S1504). The settlement information generation unit 111 transmits settlement information (cash settlement information) including the calculation result (step S1505).

[0185] The display unit 1010 then displays a cash settlement screen based on the settlement information (cash settlement information) (step S1506). The settlement unit 108 performs the cash settlement (step S1507). In step S107, the settlement unit 108 inputs the deposit amount received by the store clerk into the cash settlement screen. The display unit 1010 then displays a screen including the change amount obtained by subtracting the purchase price from the deposit amount. The issuance control unit 1011 then causes the printing device 13 to issue a receipt (step S1508). The store mobile terminal device 10 then completes the cash settlement. Although not shown, once the settlement is complete, the sales management unit 113 of the POS server 11 may update the sales information based on the payment details.

[0186] On the other hand, if the payment is not cash (step S1502: No), the store mobile terminal device 10 performs credit card payment processing (step S1509). A detailed flowchart of the credit card payment processing in emergency mode (step S1509) may be the same as the flowchart of the credit card payment processing in self-scan mode (step S1211 in FIG. 25) shown in FIGS. 26 and 27. Therefore, a detailed description of step S1509 will be omitted.

[0187] 32, the payment method is accepted after the payment request is sent to the POS server 11, but this is not limiting. For example, the store-use mobile terminal device 10 may transmit the payment request after accepting the payment method.

[0188] <Product registration process in front-end handling mode> The product registration process in the front-end handling mode will be described. In the front-end handling mode, the product information acquisition unit 103 acquires information about the products purchased by the customer through operation by a store clerk. The method of acquiring the product information may be the same as the product registration process in the self-scan mode, except that the operator is a store clerk. The list generation unit 112 of the POS server 11 may update the purchased product list. The display unit 1010 may then display the product information registered in the purchased product list together with information indicating the front-end handling mode. The type of information indicating the front-end handling mode is not particularly limited. For example, the information indicating the front-end handling mode may be information in the form of pictures, letters, numbers, colors, or a combination of these. The display unit 1010 may also display information indicating the front-end handling mode on each screen in other front-end handling modes.

[0189] FIG. 33 is an explanatory diagram showing an example of a purchase item list in the front-end handling mode. The display unit 1010 displays a screen d180 corresponding to the purchase item list. The screen d180 includes, for example, information similar to that of the screen d060 in the self-scan mode shown in FIG. 16. The screen d180 includes, for example, a purchase item list summary field d181, a details field d182, an add item button d184, a payment button d185, a transaction cancel button d186, an operator name display field d187, and a mode summary field d188. Details other than the operator name display field d187 and the mode summary field d188 may be similar to those of the screen d060 in the self-scan mode and the screen d150 in the emergency mode described above.

[0190] The name display field d187 displays the name of the clerk. Note that, if a clerk ID (identification information of the clerk) is accepted, the name display field d187 can display the name of the clerk. For example, if a clerk ID is accepted as in the screen d010 shown in FIG. 10, the name display field d187 may be displayed. If a clerk ID is not accepted as in the screen d001 shown in FIG. 9, the name display field d187 may not be included in the screen d180, or the name display field d187 may be blank. The presence or absence of a title is not limited. Furthermore, the purchase item list screen d180 in the front-end handling mode differs from the screen d060 in the self-scan mode and the screen d150 in the emergency mode in that information indicating the front-end handling mode is displayed. To distinguish from the self-scan mode, the clerk's name may not have a title. Alternatively, to distinguish from the self-scan mode, a title different from the title used for the customer's name in the self-scan mode may be used. Furthermore, the screen d180 may be the same as the screen d060 in the self-scan mode and the screen d150 in the emergency mode, except for the mode summary section d188.

[0191] Furthermore, information indicating the front handling mode is displayed in the mode summary field d188. In Fig. 33, the word "front handling" is displayed in the mode summary field d188.

[0192] Also, for example, the background color of the screen d180 may be displayed so that it is possible to distinguish that it is in the front handling mode. For example, the background color in the front handling mode and the background color in the emergency mode may be displayed so as to be different.

[0193] <Flowchart of product registration process in front-hand handling mode> The product registration process in the front-end handling mode is the product registration process shown in FIG. 17 (step S109 in FIG. 14). The detailed flowchart of the product registration process in the front-end handling mode may be the same as the flowchart of the product registration process in the self-scan mode, except that the operator is a store clerk. Therefore, a detailed explanation of the flowchart using figures will be omitted. Note that, if the front-end handling mode is selected as the "Yes" in step S1111 shown in FIG. 17, the store-use mobile terminal device 10 ends the product registration process and returns. Therefore, in the front-end handling mode, the system 1 proceeds to the front-end handling mode payment process (step S110) that follows the product registration process (step S109) shown in FIG. 14.

[0194] This concludes the description of the product registration process in the front handling mode.

[0195] <Payment processing in pre-clearance mode> Next, the payment process in front-end handling mode will be explained. As explained in Figures 2 and 3, in front-end handling mode, the settlement device 14 performs the final payment. There are three types of payment processes for having the settlement device 14 read the payment information. The first payment process (payment process example 1) is a method in which the settlement device 14 reads the payment information from the store's mobile terminal device 10. The second payment process (payment process example 2) is a method in which the settlement device 14 reads the payment information from the store's mobile terminal device 10 via the customer's mobile terminal device 12. The third payment process (payment process example 3) is a method in which the settlement device 14 reads the payment information from the store's mobile terminal device 10 via printed matter.

[0196] There is no particular limitation on which of payment processing examples 1 to 3 is performed. For example, which of payment processing examples 1 to 3 is performed may be fixed. Alternatively, for example, the system may be configured so that which of payment processing examples 1 to 3 is performed is selectable. For example, after receiving the input of the store clerk ID, the store clerk may select which payment processing to perform.

[0197] Next, the settlement information in the front-end handling mode will be described. The settlement information in the front-end handling mode includes, for example, at least information identifying the purchase item list and information on the accepted store clerk ID. As explained in the payment by the settlement device 14 in the self-scan mode, the information identifying the purchase item list is customer ID information. This store clerk ID information is included on the receipt issued by the settlement device 14. The settlement information in the front-end handling mode differs from the settlement information for payments by the settlement device 14 in the self-scan mode in that it includes information on the accepted store clerk ID. The settlement information also includes, for example, information on at least the purchase price of the items purchased by the customer. As with payments by the settlement device 14 in the self-scan mode, the settlement device 14 can perform either payment procedure A or payment procedure B depending on the content of the settlement information. As explained above, in the case of payment procedure A, the settlement information includes at least information identifying the purchase item list and information on the purchase price. In the case of payment procedure B, the settlement information includes at least information identifying the purchase item list. Here, payment procedure A will be used for explanation.

[0198] The settlement information may include other information in addition to information identifying the purchased item list, purchase price information, and store clerk ID information. For example, the settlement information may include product information and purchase quantity information for the items. Product information included in the settlement information may be, for example, the product ID, product name, and unit price of the item. The settlement information may include member information such as the member ID information of the customer who is the operator of the product registration process. The settlement information may include information on the ID of the mobile terminal device 10 for the store that performed the product registration process. The settlement information may include, for example, store information. The settlement information may also include information indicating the mode. Here, the information indicating the mode indicates that it is the front-handling mode.

[0199] <Payment Processing Example 1> Payment processing example 1 will now be described. The settlement information management unit 107, for example, notifies the POS server 11 of a settlement request to perform settlement using the settlement device 14. For example, upon receiving the settlement request, the settlement information generation unit 111 of the POS server 11 generates settlement information based on a list of items purchased by the customer. The settlement information management unit 107 passes the generated settlement information to the output unit 109 of the store-use mobile terminal device 10. The settlement information is as described above. In payment processing example 1, the settlement information is read directly from the store-use mobile terminal device 10 to the settlement device 14.

[0200] The output unit 109 outputs settlement information that can be read by the settlement device 14. Specifically, the display unit 1010 displays this settlement information to the settlement device 14. More specifically, for example, the display unit 1010 displays a screen including a settlement code that encodes the settlement information. An example of the display of the settlement code may be similar to screen d090 shown in FIG. 20 used to explain the self-scan mode. Note that the customer carries the store-use mobile terminal device 10 to the settlement device 14.

[0201] The reading unit 141 of the checkout device 14 reads the settlement information from the store's mobile terminal device 10. In the case of a manned checkout device 14, the reading unit 141 may read the settlement information in response to an operation by a store clerk. In the case of an unmanned checkout device 14, the reading unit 141 reads the settlement information in response to an operation by a customer. The settlement unit 142 performs settlement using the read settlement information. The settlement here is not limited to cash settlement, electronic settlement, or the like.

[0202] The issuance control unit 143 causes the printing device of the settlement device 14 to issue a receipt including the clerk ID information included in the settlement information. The receipt may include clerk information such as the clerk name in addition to the clerk ID. This allows the customer or clerk to identify the clerk who registered the product. For example, if a customer or clerk finds a problem with the registration information after settlement, they can easily identify the clerk who registered the product by looking at the receipt. The receipt may also include information included in receipts issued in the self-scan mode or emergency mode described above. The receipt may include, for example, purchase price information and store information. The purchase price information and store information included in the receipt may be the same as the information on receipts issued in the self-scan mode. The receipt may also include the ID information of the mobile terminal device 10 for the store that performed the product registration process. The receipt may also include the ID information of the settlement device 14 that performed the payment process. The receipt may also include information such as the date and time the payment was completed. The receipt may also include the receipt ID information. The receipt may also include information indicating the payment method and information related to the payment. If input of a member ID or the like is accepted to award points or the like, the receipt may also include member information. The member information included in the receipt may be the same as the information on a receipt issued in self-scan mode. The receipt may also include information indicating the mode. Here, the information indicating the mode indicates that it is the front-handling mode.

[0203] According to the first payment processing example, communication between the store clerk who registered the product and the customer is easy, which can save the store clerk time and effort in registering the product.

[0204] In payment processing example 1 in the front-end handling mode, when payment is completed, the list generation unit 112 may assign a customer ID to the new customer and generate a new purchase item list. More specifically, when the complete button d092 on the screen d090 shown in FIG. 20, which was used to explain the self-scan mode, is tapped, the store-use mobile terminal device 10 may request the POS server 11 to assign a new customer ID. Then, the list generation unit 112 may assign a customer ID to the new customer and generate a new purchase item list. Then, the display unit 1010 may display, as an initial screen, a screen (not shown) in which no product information is registered in the product registration list. This allows the store-use mobile terminal device 10 to perform new product registration processing for the next customer in the emergency mode.

[0205] <Payment Processing Example 2> Next, payment processing example 2 will be described. As described above, payment processing example 2 is a method in which the settlement device 14 reads settlement information from the store's mobile terminal device 10 via the customer's mobile terminal device 12. As with payment processing example 1, the settlement information management unit 107, for example, notifies the POS server 11 of a payment request from the settlement device 14. For example, upon receiving the payment request, the settlement information generation unit 111 of the POS server 11 generates settlement information based on the customer's purchase item list. The settlement information management unit 107 passes the generated settlement information to the output unit 109 (display unit 1010) of the mobile terminal device. The settlement information is as described above. Therefore, either payment procedure A or payment procedure B described above may be performed. Here, payment procedure A will be used for explanation.

[0206] The output unit 109 outputs the settlement information, which includes the received store clerk ID information and is readable by the settlement device 14, to the customer's mobile terminal device 12. More specifically, the display unit 1010 displays the settlement information on the customer's mobile terminal device 12. More specifically, for example, the display unit 1010 displays a screen including a settlement code that encodes the settlement information. An example of the display of the settlement code may be the same as screen d090 shown in FIG. 20, which was used to explain the self-scan mode.

[0207] The reading unit 121 of the customer's mobile terminal device 12 reads the settlement information from the store's mobile terminal device 10. Then, the output unit 123 outputs the read settlement information to the settlement device 14. Specifically, the display unit 1210 displays a settlement code that encodes the settlement information. The customer carries the customer's mobile terminal device 12 to the settlement device 14.

[0208] The reading unit 141 of the payment device 14 reads the payment information from the customer's mobile terminal device 12. In the case of a manned payment device 14, the reading unit 141 may read the payment information in response to an operation by a store clerk. In the case of an unmanned payment device 14, the reading unit 141 reads the payment information in response to an operation by the customer. The settlement unit 142 performs the payment using the read payment information. The payment here is not limited to cash payment, electronic payment, or the like.

[0209] The issuance control unit 143 then causes the printer of the settlement device 14 to print a receipt including the clerk ID information included in the settlement information. The receipt printed here may be the same as the receipt described in payment processing example 1.

[0210] In payment processing example 2 in the front-end handling mode, after the reading unit 121 of the customer's mobile terminal device 12 reads the settlement information from the store-use mobile terminal device 10, the list generation unit 112 may assign a customer ID to the new customer and generate a new purchase item list. Although not shown, a screen including a settlement code that encodes the settlement information may have a reading end button. When the reading end button is tapped after the reading unit 121 of the customer's mobile terminal device 12 finishes reading, the store-use mobile terminal device 10 may request the POS server 11 to assign a new customer ID, as in payment processing example 1. Then, the list generation unit 112 may assign a customer ID to the new customer and generate a new purchase item list. Then, the display unit 1010 may display, as an initial screen, a screen (not shown) in which no product information is registered in the product registration list.

[0211] According to the payment processing example 2, the store-use mobile terminal device 10 can immediately register a product for a new customer after completing the product registration, thereby enabling the store-use mobile terminal device 10 to be used more effectively.

[0212] <Payment Processing Example 3> Finally, payment processing example 3 will be described. In payment processing example 3, the settlement device 14 reads settlement information from the store-use mobile terminal device 10 via printed material. Note that other portable media may be used instead of printed material. As in payment processing examples 1 and 2, the settlement information management unit 107 of the store-use mobile terminal device 10, for example, notifies the POS server 11 of a payment request from the settlement device 14. For example, upon receiving the payment request, the settlement information generation unit 111 of the POS server 11 generates settlement information based on a list of products purchased by the customer. The settlement information is as described above. Therefore, either payment procedure A or payment procedure B described above may be performed. Here, payment procedure A will be used for the description. The settlement information management unit 107 passes the generated settlement information to the output unit 109 (issuance control unit 1011) of the store-use mobile terminal device 10.

[0213] The issuance control unit 1011 issues a printed material on which payment information that can be read by the payment device 14 is printed. The payment information may be a payment code represented by numbers, letters, a one-dimensional code, a two-dimensional code, or a combination thereof. For example, a printed material (not shown) includes this payment code. The customer carries the printed material to the payment device 14.

[0214] The reading unit 141 of the payment device 14 reads the payment information from the printed material. In the case of a manned payment device 14, the reading unit 141 may read the payment information through operation by a store clerk. In the case of an unmanned payment device 14, the reading unit 141 reads the payment information through operation by a customer. The settlement unit 142 performs payment using the read payment information. The payment here is not limited to cash payment, electronic payment, etc.

[0215] The issuance control unit 143 causes the printer of the settlement device 14 to print a receipt including the clerk ID information included in the settlement information. The receipt printed here may be similar to the receipts described in payment processing example 1 and payment processing example 2.

[0216] Here, in payment processing example 3 in the front-end handling mode, after a printed matter including settlement information is issued, the list generation unit 112 may assign a customer ID to the new customer and generate a new purchase item list. More specifically, after the printed matter is issued, as in payment processing example 1, the store mobile terminal device 10 may request the POS server 11 to assign a new customer ID. Then, the list generation unit 112 may assign a customer ID to the new customer and generate a new purchase item list. Then, the display unit 1010 may display, as an initial screen, a screen (not shown) in which no product information is registered in the product registration list.

[0217] According to the settlement processing example 3, the store-use mobile terminal device 10 can immediately register a new product for a customer after completing the product registration. In addition, since the communication between the store clerk who registered the product and the customer is easy, the time and effort of the store clerk who registered the product can be saved.

[0218] <Flowchart of each settlement process in pre-clearance mode> The payment process in the front-end handling mode is the payment process in the front-end handling mode (step S110) in Figure 14. Here, flowcharts corresponding to the above-mentioned payment process examples 1 to 3 will be described using Figures 34, 35, and 36, respectively.

[0219] <<Flowchart of payment processing example 1>> FIG. 34 is a flowchart showing payment processing example 1 in front-end handling mode. The payment information management unit 107 transmits a payment request (step S1601). Upon receiving the payment request, the payment information generation unit 111 calculates the purchase price (step S1602). After generating the payment information, the payment information generation unit 111 generates a payment code by encoding the payment information (step S1603). The payment code can be read by the payment device 14. Here, the above-mentioned payment procedure A will be used as an example. The payment information includes at least information identifying the purchased item list, purchase price information, and store clerk ID information. In addition to these pieces of information, the payment information also includes the ID information of the mobile terminal device 10 for the store and information about the store to which payment is made. The payment information generation unit 111 transmits the generated payment code (step S1604). When the display unit 1010 receives the settlement code, it displays the settlement code (step S1605).

[0220] For example, a customer carries a store-use mobile terminal device 10 to the settlement device 14. The reading unit 141 of the settlement device 14 reads the settlement code (step S1606). The display unit 144 displays a payment screen based on the read settlement code (step S1607). The settlement unit 142 performs the payment (step S1608). In step S1608, the payment may be made by cash, electronic payment, or any other method. The issuance control unit 143 then issues a receipt (step S1609). The system 1 then ends the operation of the flow. The contents of the receipt are as described above. At least the store clerk ID and the purchase price are printed on the receipt. After step S1608, the display unit 144 may display a screen indicating that the payment has been completed.

[0221] Although the explanation has been given using payment procedure A, the above-mentioned payment procedure B may also be used. An example of using payment procedure B is as explained in the payment process by settlement device 14 in self-scan mode.

[0222] <<Flowchart of payment processing example 2>> FIG. 35 is a flowchart showing payment processing example 2 in front-end handling mode. The payment information management unit 107 sends a payment request (step S1701). Upon receiving the payment request, the payment information generation unit 111 calculates the purchase price (step S1702). After generating the payment information, the payment information generation unit 111 generates a payment code by encoding the payment information (step S1703). The payment code can be read by the customer's mobile terminal device 12. Here, the above-mentioned payment procedure A will be used as an example. The payment information includes at least information identifying the purchased item list, purchase price information, and store clerk ID information. In addition to this information, the payment information may also include, for example, the mobile terminal device ID information and information about the store where payment is to be made. The payment information generation unit 111 sends the payment code (step S1704). When the display unit 1010 receives the settlement code, it displays the settlement code, which can be read by the customer's mobile terminal device 12, to the customer's mobile terminal device 12 (step S1705).

[0223] The reading unit 121 of the customer's mobile terminal device 12 reads the settlement code from the store's mobile terminal device 10 (step S1706). Then, the display unit 1210 displays the settlement code to the settlement device 14 based on the read settlement code (step S1707). The read settlement code and the displayed settlement code may be encoded in the same or different ways. For example, the settlement code read by the reading unit 121 may be a barcode, and the settlement code displayed by the display unit 1210 may be a two-dimensional code.

[0224] The reading unit 141 of the settlement device 14 reads the settlement code from the customer's mobile terminal device 12 (step S1708). The display unit 144 displays a settlement screen based on the read settlement code (step S1709). The settlement unit 142 performs the settlement (step S1710). In step S1710, the settlement may be by cash, electronic payment, or other means, and is not limited to this. The issuance control unit 143 then issues a receipt (step S1711), ending the flow. The contents of the receipt are as described above. At least the store clerk ID and the purchase price are printed on the receipt. The display unit 144 may display a settlement completion screen after step S1711.

[0225] Although the above description uses payment procedure A, the above-described payment procedure B may also be used. An example of using payment procedure B is as described in the payment process by settlement device 14 in self-scan mode.

[0226] <<Flowchart of payment processing example 3>> FIG. 36 is a flowchart showing a third example of a payment process in the front-end handling mode. The payment information management unit 107 transmits a payment request (step S1801). Upon receiving the payment request, the payment information generation unit 111 calculates the purchase price (step S1802). The payment information generation unit 111 generates payment information including the calculation result, and generates a payment code by encoding the payment information (step S1803). The payment code is readable by the payment device 14. This payment information includes information on the store clerk ID and information on the purchase price. The payment information further includes, for example, information on the ID of the mobile terminal device and information on the store to which payment is made. The payment information generation unit 111 transmits the payment code to the mobile terminal device 10 for the store (step S1804). Upon receiving the payment code, the issuance control unit 1011 causes the printing device 13 to print a printed matter including the payment code (step S1805).

[0227] The customer takes the printed material to the payment device 14. The reading unit 141 of the payment device 14 reads the payment code on the printed material (step S1806). Then, the display unit 144 displays a payment screen based on the read payment code (step S1807). The payment unit 142 performs the payment (step S1808). In step S1808, the payment may be made by cash, electronic payment, or any other method. The issuance control unit 143 then issues a receipt (step S1809), ending the flow. The contents of the receipt are as described above. At least the store clerk ID and the purchase price are printed on the receipt. The display unit 144 may display a payment completion screen after step S1808.

[0228] Although the explanation has been given using payment procedure A, the aforementioned payment procedure B may also be used. An example of using payment procedure B is as explained in the payment processing by settlement device 14 in self-scan mode. This concludes the explanation of the front-end handling mode.

[0229] The first embodiment is not limited to the above-described examples, and various modifications are possible. For example, the layout, characters, color, and other fonts of each button, input field, display field, and text on each screen are not particularly limited. For example, the colors of each button may be different. Furthermore, each screen may have display fields, buttons, etc. that are not shown. Furthermore, each screen may not have some of the display fields shown in the drawings.

[0230] Here, a modification of the first embodiment will be described.

[0231] <First Modification of First Embodiment (Mode Acceptance)> In the above example, either the self-scan mode or the clerk mode is accepted based on the user's identification information (user ID information). For example, biometric information may be used as the user's identification information. For example, the mode acceptance unit 101 may accept either the self-scan mode or the clerk mode (front-end handling mode) based on the biometric information. For example, it is assumed that the mode acceptance unit 101 accepts the self-scan mode if the newly acquired biometric information is the biometric information of a customer. It is assumed that the mode acceptance unit 101 accepts the clerk mode if the newly acquired biometric information is the biometric information of a clerk. The mode acceptance unit 101 may then accept input of either the front-end handling mode or the emergency mode in response to a tap on a button displayed on the above-described screen. If the biometric information is facial features, the mode acceptance unit 101 may accept the self-scan mode by authenticating, for example, facial features extracted from a newly captured face image and facial features registered in the member DB 115. For example, the mode acceptance unit 101 may accept the clerk mode by authenticating a facial feature extracted from a newly captured face image with a facial feature registered in the clerk DB 116. Alternatively, the mode acceptance unit 101 may accept the self-scan mode if the user is not a clerk, for example, by authenticating a facial feature extracted from a newly captured face image with a facial feature registered in the clerk DB 116. Furthermore, in cases where biometric information is registered in both the clerk DB 116 and the customer DB, the mode acceptance unit 101 may accept the mode by inputting the above-mentioned ID information.

[0232] <Modification 2 of Embodiment 1> In the first embodiment, an example has been described in which any one of the self-scan mode, the emergency mode, and the front-handling mode is accepted. The store-use mobile terminal device 10 is not limited to an example having three modes. For example, the store-use mobile terminal device 10 may have two modes, the emergency mode and the front-handling mode. The mode acceptance unit 101 may accept either the emergency mode or the front-handling mode. For example, the store-use mobile terminal device 10 may have two modes, the self-scan mode and the emergency mode. The mode acceptance unit 101 may accept either the self-scan mode or the emergency mode. For example, the mobile terminal device may have two modes, the self-scan mode and the front-handling mode. The mode acceptance unit 101 may accept either the self-scan mode or the emergency mode.

[0233] When there is only one clerk mode, such as two modes, a self-scan mode and a front-end handling mode, the mode receiving unit 101 can distinguish the mode by the ID.

[0234] Furthermore, the mobile terminal device 10 for use in a store may be a device that has a single function for each mode. The mobile terminal device 10 for use in a store may be a device that has a self-scan mode but does not have an emergency mode or a front-end handling mode. Alternatively, for example, the mobile terminal device 10 for use in a store may be a device that has an emergency mode but does not have a self-scan mode or a front-end handling mode. Alternatively, for example, the mobile terminal device 10 for use in a store may be a device that has a front-end handling mode but does not have a self-scan mode or an emergency mode.

[0235] In the case of a mobile terminal device 10 for use in a store that has a self-scan mode, for example, the system 1 may not include any of the illustrated devices that are not used in the self-scan mode. For example, the mobile terminal device 10 for use in a store that has a self-scan mode may not include any of the functional units other than those used in the self-scan mode.

[0236] In the case of a store-use portable terminal device 10 that has an emergency mode, for example, the system 1 may not have devices that are not used in emergency mode among the devices shown in the figure. For example, the checkout device 14 may not be used in emergency mode, so the system 1 may not have the checkout device 14. The store-use portable terminal device 10 may not have functional units other than those used in emergency mode. For example, the store-use portable terminal device 10 may not have the mode reception unit 101.

[0237] In the case of a mobile terminal device 10 for use in a store that has a front-end handling mode, for example, the system 1 may not have any of the illustrated devices that are not used in the front-end handling mode. Also, for example, the mobile terminal device 10 for use in a store may not have any functional units other than those used in the front-end handling mode. For example, the mobile terminal device 10 for use in a store may not have the mode reception unit 101. Or, for example, the mobile terminal device 10 for use in a store may not have the app presence / absence reception unit 106.

[0238] <Third Modification of First Embodiment> In the first embodiment, an example has been described in which a mode is accepted based on information about a user's ID. Information about a user's ID may be input to identify a user regardless of the acceptance of a mode. For this reason, the mobile terminal device 10 for use in a store may have an identification information accepting unit (not shown) separate from the mode accepting unit 101. For this reason, as described in the second modification, when the mobile terminal device 10 for use in a store is realized as a device having the functions of each mode individually, the identification information accepting unit may accept information about a user's ID.

[0239] <Fourth Modification of First Embodiment (Self-Scan Mode)> The example is not limited to selecting a device to be used for payment after selecting a payment method. For example, in self-scan mode, the device to be used for payment may be selected without selecting a payment method. For example, the display unit 1010 may display on the screen for accepting the selection of the device to be used for payment shown in FIG. 19 that the settlement device 14 can accept credit card payment and cash payment, and that the customer's mobile terminal device 12 can accept credit card payment.

[0240] <Fifth Modification of First Embodiment> Although not shown, age verification processing and coupon issuance processing may also be performed. The store-use mobile terminal device 10 may perform different age verification processing in each mode. Also, the store-use mobile terminal device 10 may perform different coupon issuance processing in each mode.

[0241] For example, in the self-scanning mode, the product registration process is performed by the customer's operation. Therefore, the store-use mobile terminal device 10 may perform age verification processing when performing the product registration process in the customer mode. For example, in the self-scanning mode or the front-end handling mode, when payment is made by a manned checkout device 14 operated by a store clerk, the customer's mobile terminal device 12 may output payment information including information indicating that age verification processing will be performed by the checkout device 14.

[0242] <Sixth Modification of First Embodiment> In each mode, the display unit 1010 displays a settlement code as an example of how the output unit 109 of the store mobile terminal device 10 outputs settlement information. However, the output example is not limited to this. For example, short-range wireless communication such as RFID may be used as the output method. The output unit 109 may have a communication unit that performs short-range wireless communication such as RFID. This communication unit may then transmit the settlement information to the customer's mobile terminal device 12 or the settlement device 14. The reading unit 121 of the customer's mobile terminal device 12 or the reading unit 141 of the settlement device 14 may read the settlement information by receiving it using an RFID reading device.

[0243] Further, short-range wireless communication such as RFID may be used as a method of transmitting and receiving information between the customer's mobile terminal device 12 and the settlement device 14. In the settlement processing example 2 in the front-end handling mode, the output unit 123 of the customer's mobile terminal device 12 may output settlement information to the settlement device 14 by a communication unit that performs short-range wireless communication such as RFID. The reading unit 141 of the settlement device 14 may read the settlement information by receiving it using an RFID reading device.

[0244] Alternatively, the output method may be to output the settlement information to the customer's mobile terminal device 12 by sending an electronic message or email. The customer's mobile terminal device 12 has a settlement information acquisition unit (not shown). The settlement information acquisition unit may acquire the settlement information by receiving the settlement information.

[0245] <Seventh Modification of First Embodiment> In the first embodiment, the receipt is a printed material, but is not limited to this. For example, the receipt may be an electronic receipt. The electronic receipt is notified to the customer by, for example, an electronic message or email. The email address, telephone number, etc. may be acquired from the member DB 115. Alternatively, the settlement device 14 and the store mobile terminal device 10 may have a notification destination receiving unit (not shown). Taking the settlement device 14 as an example, the notification destination receiving unit may receive information on the notification destination, such as an address for an electronic message or a telephone number. The issuance control unit may notify the customer of the electronic receipt based on the received information on the notification destination. Alternatively, the electronic receipt may be viewable as a purchase history using a store app.

[0246] <Eighth Modification of First Embodiment> In each mode, the POS server 11 updates the purchase item list, calculates purchase prices, generates settlement information, updates the sales DB 118, and so on. For example, at least one of these processes of the POS server 11 may be performed by the store-use mobile terminal device 10. For example, the POS server 11 may transmit information necessary for settlement information to the store-use mobile terminal device 10, and the store-use mobile terminal device 10 may generate the settlement information and generate a settlement code that encodes the settlement information. The information necessary for the settlement information transmitted from the POS server 11 may be information that the store-use mobile terminal device 10 does not have, for example.

[0247] For example, in an emergency such as a disaster, it may be impossible to connect to other devices such as the POS server 11. To prepare for such a case, the store-use portable terminal device 10 may store various information stored in the POS server 11 and perform processing of the POS server 11. For this reason, the store-use portable terminal device 10 may have functional units similar to the settlement information generation unit 111, list generation unit 112, and sales management unit 113 of the POS server 11. The store-use portable terminal device 10 may store a member DB 115, a store clerk DB 116, a product DB 117, sales information, and a purchase product list DB 119. Furthermore, the store-use portable terminal device 10 may have the function of a query unit (not shown) that queries received ID information and password information. The store-use portable terminal device 10 may have some of the functional units of the POS server 11.

[0248] <Modification 9 of First Embodiment (Store Clerk Mode)> In the store clerk mode, if the store mobile terminal device 10 can accept input of the customer's member ID information in addition to the clerk ID information of the operator, the store clerk, it may display member information such as point information on a purchased item list screen such as screen d150 shown in FIG. 28 or screen d180 shown in FIG. 33.

[0249] <Modification 10 of First Embodiment> When making a payment using a settlement device 14, the store-use mobile terminal device 10 may be able to specify the settlement device 14. For example, the settlement information may be information that can be read by the specified settlement device 14 but cannot be read by other settlement devices 14. Alternatively, the settlement information may be information that can be used for payment by the specified settlement device 14.

[0250] <Eleventh Modification of First Embodiment (Self-Scan Mode)> In the first embodiment, an example has been described in which the payment method acceptance unit 105 accepts a payment method in self-scan mode. Also, in the first embodiment, an example has been described in which the payment method acceptance unit 105 accepts a selection of a device to perform payment. For example, the settlement device 14 may perform payment in self-scan mode without accepting a selection of a payment method or a device to perform payment in the store-use mobile terminal device 10. When the settlement device 14 performs payment without accepting a selection of a payment method or a device to perform payment, when the payment button d065 on the screen d060 shown in FIG. 16 is tapped, the display unit 1010 may display the screen d090 of FIG. 20 including a settlement code that encodes settlement information.

[0251] This concludes the description of the modified example. Next, the effects of the first embodiment will be described. Portable store-use mobile terminal devices such as smartphones and tablets may not be connected to a device capable of reading cards such as credit cards, debit cards, and point cards. Therefore, the store-use mobile terminal device 10 acquires product information for the product purchased by the customer, and outputs payment information based on the acquired product information in a manner that can be read by the customer's mobile terminal device 12. The customer's mobile terminal device 12 then reads the payment information and performs electronic payment via the payment server 15 based on the payment information and the settlement information. This allows the customer to perform electronic payment even if the store-use mobile terminal device 10 does not have a means for reading electronic payments.

[0252] Furthermore, the store's mobile terminal device 10 outputs settlement information including information for the customer's mobile terminal device 12 to accept input of the customer's payment information. After the customer's mobile terminal device 12 reads the settlement information, it accepts the customer's payment information based on the settlement information and performs electronic payment based on the payment information and the settlement information. This allows the customer to perform electronic payment using their own payment information even if the store's mobile terminal device 10 does not have a means for reading electronic payments.

[0253] Furthermore, the store mobile terminal device 10 outputs settlement information that can be read by a store app that has customer payment information set therein and that runs on the customer's mobile terminal device 12. The store app on the customer's mobile terminal device 12 then performs electronic payment using the customer's payment information set in the store app and the read settlement information. This allows the customer to perform electronic payment using the payment information in the store app that runs on the customer's mobile terminal device 12, even if the store mobile terminal device 10 does not have a means for reading electronic payments.

[0254] The store-use mobile terminal device 10 also receives a request for a store app on the customer's mobile terminal device 12. If the store app is present, the store-use mobile terminal device 10 outputs settlement information that can be read by the store app. The store app running on the customer's mobile terminal device 12 reads the settlement information and performs electronic payment based on the payment information and the settlement information set in the store app. On the other hand, if the store app is not present, the store-use mobile terminal device 10 outputs settlement information including information that allows the customer's mobile terminal device 12 to accept input of the customer's payment information. After reading the settlement information, the customer's mobile terminal device 12 accepts the customer's payment information based on the settlement information and performs electronic payment based on the payment information and the settlement information. In this way, the store-use mobile terminal device 10 outputs settlement information depending on whether or not a store app with payment information set is present. As a result, even if the store-use mobile terminal device 10 does not have a means for reading electronic payment, the customer can perform electronic payment depending on whether or not the store app is present on their mobile terminal device 12.

[0255] Furthermore, there may be cases where the settlement device 14 is unavailable due to a disaster or other reason. In such cases, the store-use mobile terminal device 10 acquires product information through operation by a store clerk. The store-use mobile terminal device 10 then outputs settlement information based on the product information readable by the customer's mobile terminal device 12 to the customer's mobile terminal device 12. The customer's mobile terminal device 12 reads the settlement information and performs electronic payment via the payment server 15 based on the settlement information and payment information. In this way, the store-use mobile terminal device 10 can be used as an emergency product registration device operated by a store clerk, such as for BCP measures. Therefore, even if the store-use mobile terminal device 10 does not have an electronic payment reading means and the settlement device 14 is unavailable at the store, the customer can still make electronic payments.

[0256] Furthermore, the store-use mobile terminal device 10 accepts the selection between electronic payment and cash payment when a product is registered by a store clerk. In the case of cash payment, the store-use mobile terminal device 10 outputs cash settlement information including purchase price information. On the other hand, in the case of electronic payment, the store-use mobile terminal device 10 outputs settlement information that can be read by the customer's mobile terminal device 12. This allows the customer to make both cash and electronic payments even if the store-use mobile terminal device 10 does not have a reading means for electronic payment and the store is unable to use the settlement device 14.

[0257] (Embodiment 2) Next, a second embodiment will be described in detail with reference to the drawings. In the second embodiment, the basic configuration of the content described in the first embodiment will be described.

[0258] Fig. 37 is a block diagram showing a configuration example of a store-use mobile terminal device according to embodiment 2. Fig. 38 is a block diagram showing a configuration example of a customer-use mobile terminal device according to embodiment 2. The store-use mobile terminal device 20 has a product information acquisition unit 203 and an output unit 209. The customer-use mobile terminal device 22 has a reading unit 221 and a payment unit 222.

[0259] The product information acquisition unit 203 of the store-use mobile terminal device 20 acquires product information of a product purchased by a customer through an operation by the customer or a store clerk. The product information may be any information that can identify the product. For example, the product information may be product identification information, product image data, or product feature information extracted from the image data. The method of acquiring the product information is not particularly limited.

[0260] The output unit 209 then outputs payment information based on the product information so that it can be read by the customer's mobile terminal device 22. There are no particular limitations on the output method. Examples of output methods include displaying a payment code such as a one-dimensional code or two-dimensional code that encodes the payment information, or using near-field wireless communication using RFID. The payment information may include, for example, information on the purchase price of the product. The payment information may further include identification information of the store's mobile terminal device 20.

[0261] The reading unit 221 of the customer's mobile terminal device 22 reads the settlement information from the store's mobile terminal device 20. The settlement unit 222 performs electronic settlement via the settlement server using the customer's payment information and the read settlement information. The settlement information is information related to the customer's electronic payment for performing electronic settlement. Take the case of credit card payment as an example. The settlement information is credit information such as the credit card payment number, the expiration date of the credit card payment, and the name registered for the credit card payment. If the credit card information can be accepted, the store's mobile terminal device performs the credit card payment in response to the customer's operation.

[0262] 39 is a flowchart showing an example of the operation of the store-use mobile terminal device 20 according to the second embodiment. The operation of the flow ends. The product information acquisition unit 203 acquires product information of the product purchased by the customer through an operation by the customer or a store clerk (step S201). Then, the output unit 209 outputs payment information to the customer's mobile terminal device 22 (step S202). Then, the store-use mobile terminal device 20 ends the operation of the flow.

[0263] 40 is a flowchart showing an example of the operation of the customer's mobile terminal device 22 according to the second embodiment. The reading unit 221 reads the settlement information from the store's mobile terminal device 20 (step S211). The settlement unit 222 performs electronic settlement via the settlement server using the customer's settlement information and the read settlement information (step S212). Then, the customer's mobile terminal device 22 ends the operation of the flow.

[0264] Next, the effects of the second embodiment will be described. For example, the store-use mobile terminal device 20 acquires product information through an operation by a customer or a store clerk, and outputs payment information based on the product information to the customer's mobile terminal device 22. The customer's mobile terminal device 22 then reads the payment information from the customer's mobile terminal device 22 and performs electronic payment based on the read payment information and the customer's payment information. This allows the customer to perform electronic payment with the store-use mobile terminal device 20 even if the store-use mobile terminal device does not have a means for reading electronic payments.

[0265] This concludes the description of each embodiment. Next, the hardware configurations of the store mobile terminal devices 10, 20, the customer mobile terminal devices 12, 22, the POS server 11, and the settlement device 14 will be described. Fig. 41 is an explanatory diagram showing an example of the hardware configuration of a store mobile terminal device. Fig. 42 is an explanatory diagram showing an example of the hardware configuration of a customer mobile terminal device. Fig. 43 is an explanatory diagram showing an example of the hardware configuration of the POS server. Fig. 44 is an explanatory diagram showing an example of the hardware configuration of the settlement device.

[0266] First, an example of the hardware configuration of the store-use mobile terminal device 30 shown in Fig. 41 will be described. The store-use mobile terminal device 30 is, for example, an example in which the store-use mobile terminal devices 10 and 20 according to the first and second embodiments are realized by a computer. The store-use mobile terminal device 30 includes, for example, a processor 301, a ROM 302, a RAM 303, a storage device 304, a communication interface 305, an input / output device 306, and a camera 307. Each component is connected to each other via a bus 308.

[0267] The processor 301 controls the entire store-use mobile terminal device 30. Examples of the processor 301 include a CPU (Central Processing Unit) and a DSP (Digital Signal Processor). The store-use mobile terminal device 30 has a storage unit including a ROM 302, a RAM 303, and a storage device 304. Examples of the storage device 304 include semiconductor memory such as a flash memory, an HDD, and an SSD. For example, the storage device 304 stores an OS program, an application program, and the like. Alternatively, the ROM 302 stores an application program. The RAM 303 is used as a work area for the processor 301.

[0268] The processor 301 also loads programs stored in the storage device 304, ROM 302, etc. The processor 301 then executes each process coded in the program. The processor 301 may also download various programs via the communication network 36. The processor 301 also functions as a part or all of the store-use mobile terminal device 30. The processor 301 may then execute the processes or instructions in the illustrated flowchart based on the program.

[0269] The communication interface 305 is connected to a communication network 36, such as a LAN (Local Area Network) or WAN (Wide Area Network), via a wireless or wired communication line. As a result, the store-use mobile terminal device 30 is connected to external devices and external computers via the communication network 36. The communication interface 305 serves as an interface between the communication network 36 and the inside of the store-use mobile terminal device 30. The communication interface 305 controls the input and output of data from external devices and external computers. The input / output device 306 also accepts inputs from operations by customers or store clerks. The input / output device 306 also outputs data. The input / output device 306 may display images. The input / output device 306 is, for example, a touch panel display.

[0270] The hardware configuration of the store-use portable terminal device 30 shown in FIG. 41 is an example. The store-use portable terminal device 30 may not have some of the components shown in FIG. 41. The store-use portable terminal device 30 may have components other than those shown in FIG. 41. For example, the store-use portable terminal device 30 may have a drive device or the like. The processor 301 may read programs and data from a recording medium attached to the drive device or the like and store them in the RAM 303. Examples of recording media include optical disks, flexible disks, magneto-optical disks, and USB (Universal Serial Bus) memories. For example, the store-use portable terminal device 30 may have input devices such as a keyboard and a mouse. The store-use portable terminal device 30 may have an output device such as a display. The store-use portable terminal device 30 may have both an input device and an output device like a PC. The store-use portable terminal device 30 may also have various sensors. Examples of sensors include an acceleration sensor, a gyro sensor, a magnetic sensor, a GPS (Global Positioning System) sensor, and the like. In addition, sensors include a fingerprint sensor, LiDAR (Light, Detection and Ranging), a proximity sensor, and an ambient light sensor.

[0271] Next, an example of the hardware configuration of the customer's mobile terminal device 32 shown in FIG. 42 will be described. The customer's mobile terminal device 32 is an example in which the customer's mobile terminal device 12 described in the first embodiment is realized by a computer. Like the store-use mobile terminal device 30, the customer's mobile terminal device 32 has a processor 321, a ROM 322, a RAM 323, a storage device 324, a communication interface 325, an input / output device 326, and a camera 327. Each component is connected to each other via a bus 328. Like the store-use mobile terminal device 30, each component of the customer's mobile terminal device 32 is also connected to each other via a bus 328. The functions of each component of the customer's mobile terminal device 32 may be similar to those of the store-use mobile terminal device 30, and therefore detailed description thereof will be omitted.

[0272] As with the store-use mobile terminal device 30, the hardware configuration of the customer's mobile terminal device 32 shown in Fig. 42 is an example. The customer's mobile terminal device 32 may not include some of the components shown in Fig. 42. The customer's mobile terminal device 32 may have components other than those shown in Fig. 42.

[0273] 43, an example of the hardware configuration of the POS server 31 will be described. The POS server 31 is an example in which the POS server 11 described in the first embodiment is realized by a computer. The POS server 31 includes, for example, a processor 311, a ROM 312, a RAM 313, a storage device 314, and a communication interface 315.

[0274] The processor 311 controls the entire POS server 31. Examples of the processor 311 include a CPU and a DSP. The POS server 31 has a storage unit including a ROM 312, a RAM 313, and a storage device 314. Examples of the storage device 314 include semiconductor memory such as a flash memory, an HDD, and an SSD. For example, the storage device 314 stores an OS program, an application program, and the like. Alternatively, the ROM 312 stores the application program. The RAM 313 is used as a work area for the processor 311.

[0275] The processor 311 also loads programs stored in the storage device 314, ROM 312, etc. The processor 311 then executes each process coded in the program. The processor 311 may also download various programs via the communication network 36. The processor 311 also functions as a part or all of the POS server 31. The processor 311 may then execute the processes or instructions in the illustrated flowchart based on the program.

[0276] The communication interface 315 is connected to a communication network 36 such as a LAN or WAN via a wireless or wired communication line. This allows the POS server 31 to be connected to external devices and external computers via the communication network 36. The communication interface 315 serves as an interface between the communication network 36 and the inside of the POS server 31. The communication interface 315 also controls the input and output of data from external devices and external computers.

[0277] Furthermore, the hardware configuration of the POS server 31 shown in Fig. 43 is an example. The POS server 31 may not include some of the components shown in Fig. 43. The POS server 31 may have components other than those shown in Fig. 43.

[0278] Next, an example of the hardware configuration of the settlement device 34 shown in Figure 44 will be described. The settlement device 34 is an example in which the settlement device 14 described in embodiment 1 is realized by a computer. The settlement device 34 has, for example, a processor 341, a ROM 342, a RAM 343, a storage device 344, and a communication interface 345. The settlement device 34 further has the communication interface 345, an input / output device 346, a reading device 347, a light 348, a speaker 349, and a printing device 350. Each component is connected by a bus 351.

[0279] The processor 341 controls the entire settlement device 34. Examples of the processor 341 include a CPU and a DSP. The settlement device 34 has a storage unit including a ROM 342, a RAM 343, and a storage device 344. Examples of the storage device 344 include semiconductor memory such as a flash memory, an HDD, and an SSD. For example, the storage device 344 stores an OS program, an application program, and the like. Alternatively, the ROM 342 stores an application program. The RAM 343 is used as a work area for the processor 341.

[0280] The processor 341 also loads programs stored in the storage device 344, ROM 342, etc. The processor 341 then executes each process coded in the program. The processor 341 may also download various programs via the communication network 36. The processor 341 also functions as part or all of the settlement device 34. The processor 341 may then execute the processes or instructions in the illustrated flowchart based on the program.

[0281] The communication interface 345 is connected to a communication network 36 such as a LAN or WAN via a wireless or wired communication line. This connects the settlement device 34 to external devices and external computers via the communication network 36. The communication interface 345 serves as an interface between the communication network 36 and the inside of the settlement device 34. The communication interface 345 also controls the input and output of data from external devices and external computers.

[0282] The input / output device 346 also receives inputs from customers or store staff. The input / output device 346 also outputs data. The input / output device 346 may display images. The input / output device 346 is, for example, a touch panel display.

[0283] The reading device 347 is a device capable of reading a settlement code such as a one-dimensional code or a two-dimensional code. For example, the reading device 347 may be a barcode reader or an imaging device. The reading device 347 may also be an RFID reader capable of reading RFID.

[0284] The light 348 is, for example, an output device that lights up. The light 348 lights up when an abnormality occurs in the payment device 34 or when a store clerk needs to be called. The speaker 349 is, for example, an output device that outputs operation sounds, voice messages, etc. The printer 350 is, for example, an output device that can print receipts.

[0285] Furthermore, the hardware configuration of the settlement device 34 shown in FIG. 44 is one example. Components other than those shown in FIG. 44 may be added, or some components may not be included. For example, the settlement device 34 may have input devices such as a keyboard, mouse, or physical buttons. Furthermore, the settlement device 34 may not have the printing device 350. For example, the printing device 350 may be external. Alternatively, the printing device 350 may be connected via the communication network 36.

[0286] This concludes the description of the hardware configuration of each device. There are various variations in the method of implementing each device. For example, the system may be implemented by any combination of different computers and programs for each component. Furthermore, multiple components included in each device may be implemented by any combination of a single computer and program.

[0287] Furthermore, some or all of the components of the system may be realized by application-specific circuits. Alternatively, some or all of the system may be realized by general-purpose circuits including a processor such as an FPGA (Field Programmable Gate Array). Alternatively, some or all of the system may be realized by a combination of application-specific circuits and general-purpose circuits. These circuits may be a single integrated circuit. Alternatively, these circuits may be divided into multiple integrated circuits. These multiple integrated circuits may be connected via a bus or the like.

[0288] Furthermore, when some or all of the components of each device are realized by a plurality of computers, circuits, etc., the plurality of computers, circuits, etc. may be centrally located or distributed.

[0289] The methods described in each embodiment are realized by execution by a store mobile terminal device, a customer mobile terminal device, or a checkout device. Furthermore, the methods are realized by execution of a prepared program by a computer, such as a store mobile terminal device, a customer mobile terminal device, or a checkout device. The programs described in each embodiment are recorded on a computer-readable recording medium, such as an HDD, SSD, flexible disk, optical disk, flexible disk, magneto-optical disk, or USB memory. The programs are then read from the recording medium and executed by a computer. Furthermore, the programs may be distributed via a communications network 36.

[0290] The functions of each component of the system in each embodiment described above may be realized by hardware, as in the computer systems shown in Figures 41 to 44. Alternatively, each component may be realized by a computer device or firmware under program control.

[0291] Although the present invention has been described above with reference to various embodiments, the present invention is not limited to the above embodiments. The configurations and details of each invention may include various modifications that would be apparent to those skilled in the art within the scope of the present invention. The present invention may also include embodiments in which the features described herein are appropriately combined or substituted as necessary. For example, features described using a particular embodiment may also be applied to other embodiments to the extent that no inconsistency arises. For example, although multiple operations are described in sequence in the form of a flowchart, the order of description does not limit the order in which the multiple operations are performed. Therefore, when implementing each embodiment, the order of the multiple operations may be changed as long as it does not interfere with the content.

[0292] Some or all of the above-described embodiments can be described as follows: However, some or all of the above-described embodiments are not limited to the following.

[0293] (Appendix 1) a product information acquisition means for acquiring product information of a product to be purchased by the customer through an operation by the customer or a store clerk; an output means for outputting payment information based on the product information in a manner readable by a mobile terminal device of the customer who makes an electronic payment using the payment information and the customer's payment information; A mobile terminal device for use in a store.

[0294] (Appendix 2) the output means outputs the settlement information, which includes information for the customer's mobile terminal device to accept input of the customer's payment information; When the customer's mobile terminal device reads the settlement information, the mobile terminal device accepts input of the customer's payment information based on the read settlement information, and performs the electronic settlement using the input customer's payment information and the settlement information. 10. A mobile terminal device for use in a store according to claim 1.

[0295] (Appendix 3) the output means outputs the settlement information in which the customer's payment information is set and which can be read by a predetermined application running on the customer's mobile terminal device; The application running on the customer's mobile terminal device performs the electronic payment using the customer's payment information set in the application and the settlement information read by the application. 10. A mobile terminal device for use in a store according to claim 1.

[0296] (Appendix 4) an application presence / absence reception means for receiving a reception request for reception of a predetermined application that operates on the mobile terminal device of the customer, to which payment information of the customer is set; If the application is not present, the output means outputs the settlement information, which includes information for the customer's mobile terminal device to accept input of the customer's payment information; When the customer's mobile terminal device reads the settlement information, it accepts input of the customer's payment information based on the settlement information, and performs the electronic settlement using the input customer's payment information and the settlement information; If said application exists, the output means outputs the settlement information that can be read by the application; the application running on the customer's mobile terminal device performs the electronic payment using the payment information set in the application and the settlement information read by the application; 10. A mobile terminal device for use in a store according to claim 1.

[0297] (Appendix 5) the product information acquisition means acquires the product information through an operation by the store clerk. A mobile terminal device for use in a store according to any one of Supplementary Notes 1 to 4.

[0298] (Appendix 6) a payment method accepting means for accepting a selection between cash payment and the electronic payment; Equipped with The output means outputs cash settlement information including information on the purchase price of the product based on the product information in the case of the cash payment, and outputs the settlement information in the case of the electronic payment. 6. A mobile terminal device for use in a store according to claim 5.

[0299] (Appendix 7) The payment information is information for making the electronic payment by card. A mobile terminal device for use in a store according to any one of Supplementary Notes 1 to 6.

[0300] (Appendix 8) The output means includes a display means for displaying the settlement information. A mobile terminal device for use in a store according to any one of Supplementary Notes 1 to 7.

[0301] (Appendix 9) a reading means for reading, from the store's portable terminal device, payment information based on product information of the product purchased by the customer, which information is acquired by operation of the customer or a store clerk; a payment means for performing electronic payment using the payment information of the customer and the read settlement information; A customer's mobile terminal device comprising:

[0302] (Appendix 10) the reading means reads the settlement information, which includes information for the customer's mobile terminal device to accept input of the customer's payment information; when the settlement information is read, the settlement means accepts input of the customer's settlement information based on the read settlement information, and performs the electronic settlement using the input customer's settlement information and the settlement information; 10. A customer's mobile terminal device as described in Appendix 9.

[0303] (Appendix 11) The reading means reads the settlement information by a predetermined application running on the customer's mobile terminal device, in which the customer's payment information is set; The payment means performs the electronic payment by using the payment information set in the application and the settlement information read by the application. 10. A customer's mobile terminal device as described in Appendix 9.

[0304] (Appendix 12) a mobile terminal device for a store; a customer's mobile terminal device; Equipped with The store-use mobile terminal device a product information acquisition means for acquiring product information of a product to be purchased by the customer through an operation by the customer or a store clerk; an output means for outputting payment information based on the product information in a manner readable by the customer's mobile terminal device; Equipped with The customer's mobile terminal device reading means for reading the settlement information; a payment means for performing electronic payment using the payment information of the customer and the read settlement information; Equipped with system.

[0305] (Appendix 13) Mobile terminal devices for stores Acquire product information by an operation of the customer or a store clerk to acquire product information of a product to be purchased by the customer; outputting payment information based on the product information in a readable manner to a mobile terminal device of the customer that performs electronic payment using the payment information and the customer's payment information; method.

[0306] (Appendix 14) Acquire product information by an operation of the customer or a store clerk to acquire product information of a product to be purchased by the customer; outputting payment information based on the product information in a readable manner to a mobile terminal device of the customer that performs electronic payment using the payment information and the customer's payment information; A non-transitory computer-readable recording medium that stores a program for causing a computer in a store-use mobile terminal device to execute processing.

[0307] (Appendix 15) Acquire product information by an operation of the customer or a store clerk to acquire product information of a product to be purchased by the customer; outputting payment information based on the product information in a readable manner to a mobile terminal device of the customer that performs electronic payment using the payment information and the customer's payment information; A program that causes a computer in a mobile terminal device for a store to execute processing. [Explanation of symbols]

[0308] 1 System 10. Mobile terminal devices for stores 11 POS Server 12 Customer's mobile terminal device 13 Printing device 14 Payment device 15 Payment Server 101 Mode Reception 102 Store Reception 103 Product information acquisition department 104 Quantity Reception Department 105 Payment Method Reception Department 106 App Availability Reception Department 107 Settlement Information Management Department 108 Payment Department 109 Output section 110 Storage section 111 Settlement information generation section 112 List Generation Unit 113 Sales Management Department 114 Storage section 121 Reading unit 122 Payment Department 123 Output section 125 Payment Information Reception Department 126 Storage section 141 Reading unit 142 Payment Department 143 Issuance control unit 144 Display section 145 Storage section 1010 Display section 1011 Issuance control unit 1210 Display section 115 Member DB 116 Clerk DB 117 Product DB 118 Sales DB 119 Purchased Product List DB 20. Mobile terminal equipment for stores 22 Customer's mobile terminal device 203 Product Information Acquisition Department 209 Output section 221 Reading unit 222 Payment Department

Claims

1. a product information acquisition means for acquiring product information of products purchased by customers; an output means that operates on the customer's mobile terminal device and displays a screen that can accept input regarding whether or not a predetermined application that can set the customer's payment information is being used; an application presence / absence receiving means for receiving, via the screen, whether or not the application is being used; Equipped with the output means displays payment information based on the product information according to whether the accepted application is being used, in a manner readable by a mobile terminal device of the customer who makes an electronic payment using the payment information and the payment information. Mobile terminal device for stores.

2. If the application is not used, the output means displays the settlement information, including information for the customer's mobile terminal device to accept input of the payment information; The mobile terminal device for use in a store according to claim 1.

3. If you use the application, the output means displays the settlement information that can be read by the application in which the payment information is set.

3. The mobile terminal device for use in a store according to claim 1 or 2.

4. a reading means for reading the settlement information displayed on the mobile terminal device for the store, the settlement information being based on the product information of the product purchased by the customer; a payment means for performing electronic payment using the payment information of the customer and the read settlement information; Equipped with The store's mobile terminal device acquires the product information, operates on the customer's mobile terminal device, displays a screen capable of accepting input of whether or not a predetermined application capable of setting the payment information is being used, accepts the input of whether or not the application is being used via the screen, and displays the settlement information based on the product information, the settlement information corresponding to whether or not the application is being used. Customer's mobile terminal device.

5. a payment information receiving means for receiving input of the payment information; Furthermore, If the application is not used, the reading means reads the settlement information, which includes information for the customer's mobile terminal device to accept input of the settlement information; the payment information receiving means, when reading the settlement information, receives input of the payment information based on the read settlement information; The payment means performs the electronic payment using the input payment information and the settlement information.

5. A customer's mobile terminal device according to claim 4.

6. If you use the application, The reading means reads the settlement information using the application, The payment means performs the electronic payment by using the payment information set in the application and the settlement information read by the application.

6. A customer's mobile terminal device according to claim 4 or 5.

7. a mobile terminal device for a store; a customer's mobile terminal device; Equipped with The store-use mobile terminal device a product information acquisition means for acquiring product information of products purchased by customers; an output means that operates on the customer's mobile terminal device and displays a screen that can accept input regarding whether or not a predetermined application that can set the customer's payment information is being used; an application presence / absence receiving means for receiving, via the screen, whether or not the application is being used; Equipped with the output means displays payment information based on the product information in accordance with the accepted use of the application in a readable manner by the customer's mobile terminal device; The customer's mobile terminal device a reading means for reading the settlement information displayed on the mobile terminal device for the store; a payment means for performing electronic payment using the payment information and the read settlement information; Equipped with system.

8. The customer's mobile terminal device a payment information receiving means for receiving input of the payment information; Equipped with If the application is not used, the output means displays the settlement information, including information for the customer's mobile terminal device to accept input of the payment information; the payment information receiving means, when reading the settlement information, receives input of the payment information based on the read settlement information; The payment means performs the electronic payment using the input payment information and the settlement information, If you use the application, the output means displays the settlement information that can be read by the application; The payment means performs the electronic payment by using the payment information set in the application and the settlement information read by the application. The system of claim 7.

9. Mobile terminal devices for stores Obtain product information for products purchased by customers, a screen that operates on the customer's mobile terminal device and can accept input as to whether or not a predetermined application that can set the customer's payment information is used; Accepting whether or not the application is being used via the screen; and displaying settlement information based on the product information according to whether the accepted application is being used or not, in a readable manner on the mobile terminal device of the customer who makes an electronic payment using the settlement information and the payment information. Execute the process, method.

10. Obtain product information for products purchased by customers, a screen that operates on the customer's mobile terminal device and can accept input as to whether or not the customer is using a predetermined application for which payment information can be set; Accepting whether or not the application is being used via the screen; and displaying settlement information based on the product information according to whether the accepted application is being used or not, in a readable manner on the mobile terminal device of the customer who makes an electronic payment using the settlement information and the payment information. causing a computer of a mobile terminal device for a store to execute the processing; program.

Images