JP2021111264A - Settlement system - Google Patents

Abstract

To execute an appropriate settlement process.SOLUTION: A settlement system using a settlement device for settlement based on transaction information about commodity registered with a mobile terminal includes: first identification means for identifying the transaction information to be settled; second identification means, different from the first identification means, for identifying the transaction information to be settled; and settlement means for settlement based on the transaction information identified by the first identification means or the second identification means.SELECTED DRAWING: Figure 1

Description

The present invention relates to a settlement system.

At a store, a sales system has been introduced in which a customer can operate a mobile terminal device to register a product by himself / herself (see, for example, Patent Document 1). In such a system, since the product is registered in advance, the settlement process is smoothly performed.

Japanese Patent No. 5056161

However, in the mode in which the customer himself / herself also performs the settlement process, it is necessary to appropriately realize the settlement process in consideration of various situations.

The present invention has been made in view of such circumstances, and an object of the present invention is to provide a technique for appropriately performing a settlement process.

In order to solve the above-mentioned problems, the settlement system according to one aspect of the present invention is a settlement system that uses a settlement device to settle based on transaction information about a product registered using a mobile terminal. By a first specific means capable of specifying transaction information to be settled, a second specific means different from the first specific means capable of specifying transaction information to be settled, and the first specific means or the second specific means. It is characterized by providing a settlement means for settlement based on the specified transaction information.

It is a conceptual diagram of a network for explaining a sales system. It is explanatory drawing explaining the settlement apparatus. It is a figure which shows an example of customer information, store information, and cart information. This is a display example in the display unit of a mobile terminal. This is a display example in the display unit of a mobile terminal. This is a display example in the display unit of the settlement device. This is a display example in the display unit of the settlement device. It is explanatory drawing explaining the process progress information. It is a sequence diagram explaining the outline of the flow of product purchase. It is a sequence diagram explaining the flow of product purchase. It is a sequence diagram explaining the flow of product purchase. It is a sequence diagram explaining the flow of product purchase. It is a sequence diagram explaining the flow of product purchase. It is a sequence diagram explaining the flow of product purchase. It is a sequence diagram explaining the flow of product purchase.

FIG. 1 is a conceptual diagram of a network for explaining the sales system 1. The sales system 1 shown in FIG. 1 includes a management device (for example, a store controller) 10, a cloud server 20, a registered settlement device 30, a settlement device 40, a monitoring device 50 (for example, a personal computer, etc.), and a mobile terminal 60 (for example, a smartphone). Etc.) including. Although one registered settlement device 30 is shown in FIG. 1, the number of registered settlement devices 30 in one store may be two or more. Further, although the two settlement devices 40 are shown in FIG. 1, the number of settlement devices 40 in one store may be one or three or more. Further, although one monitoring device 50 is shown in FIG. 1, the number of monitoring devices 50 in one store may be two or more. Further, the number of management devices 10 is basically one per store, but two or more may be used. The sales system 1 can be introduced in various stores (supermarkets, convenience stores, drug stores, home centers, home appliance mass retailers, other specialty stores, etc.).

The sales system 1 shown in FIG. 1 is a service corresponding to a mode in which a clerk registers a product using a registration settlement device 30, and a service corresponding to a mode in which a customer himself registers a product using a mobile terminal 60 (a service corresponding to a mode in which a customer himself / herself registers a product using a mobile terminal 60. Hereinafter, various services such as (hereinafter referred to as service A) will be provided. The portion of the sales system 1 that provides the service A may be referred to as a specific sales system. In other words, the specific sales system is a subsystem of the sales system 1 and provides the service A. In the following description, among the customers, the customer who uses the service A may be particularly referred to as a member.

The management device 10, the registration settlement device 30, the settlement device 40, and the monitoring device 50 are installed in the store and are communicably connected via LAN 19 (which may be wired or wireless). The management device 10 can communicate with the cloud server 20.

The management device 10 is a device that mainly manages various devices in the LAN 19. For example, the management device 10 has a communication function with an external device (for example, a server at the headquarters (not shown), a cloud server 20, etc.). The management device 10 receives, for example, a product master (product file) from an external device and supplies it to the registered settlement device 30 or the like, or receives transaction information from the settlement device 40 or the like and transmits it to the external device. ..

The product master (product file) is, for example, a file that stores a product name, a selling price, and the like in association with product identification information (product code) that identifies individual products.

The cloud server 20 is a server that provides various services. For example, the cloud server 20 provides a service A (a service corresponding to a mode in which a customer who is a member himself / herself registers a product using a mobile terminal 60). For example, the cloud server 20 manages (stores) transaction information (also referred to as cart information, basket information, etc.) in service A by a member. In addition to the cart information, the cloud server 20 also contains various information related to the service A (for example, a customer master (customer file) that stores customer information, a store master (store file) that stores store information, a product master, etc.). Manage (remember).

The registration settlement device 30 is a device that executes registration processing and settlement processing. The registration settlement device 30 is used by a clerk (the registration process and the settlement process are executed by the operation of the clerk).

The settlement device 40 is an apparatus that executes a settlement process. The settlement device 40 is basically used by the customer (the customer executes the settlement process by an operation). The settlement device 40 is used by at least a customer (member) who uses the service A.

The monitoring device 50 is a device that mainly monitors various devices in the LAN 19. The monitoring device 50 monitors the operating status of other devices (for example, the registered settlement device 30, the settlement device 40, etc.), displays various information in the other device, and outputs various commands to the other device. do.

The mobile terminal 60 is operated by a customer who is a member. The mobile terminal 60 is used when using the service A. The mobile terminal 60 has a recognition function for recognizing various codes (bar code, two-dimensional code, etc.) in addition to a communication function and an imaging function (camera). For example, the mobile terminal 60 recognizes a barcode attached to a product. For example, the mobile terminal 60 may extract feature points in an captured image (an image acquired as a through image) captured by the imaging function and recognize an object (various codes).

The mobile terminal 60 is basically assumed to be the property of each member, but may be lent by the store. The number of mobile terminals 60 (number in operation) changes according to the number of visitors and the like, and FIG. 1 shows two mobile terminals 60 as an example to the effect that a plurality of mobile terminals 60 can be used. Shown.

The mobile terminal 60 displays various screens related to the service A. For example, by installing an application program (hereinafter, also referred to as a specific application) for using the service A on the mobile terminal 60, the mobile terminal 60 may display various screens related to the service A. ..

In addition, a part or all of the sales system 1 (or the specific sales system) may be referred to as another name (for example, a product registration system, a settlement system, a product sales data processing system, etc.).

Further, in the above description, the cloud server 20, the settlement device 40, and the mobile terminal 60 are used for the service A, but the management device 10 is also used for the service A (for example, the settlement device 40 and the cloud server 20). Used to send and receive information with). Other devices (registration settlement device 30, monitoring device 50, headquarters server (not shown), etc.) may be used for the service A.

FIG. 2 is an explanatory diagram illustrating the settlement device 40. FIG. 2A is a diagram showing an example of the appearance of the settlement device 40 (a perspective view seen from the customer side). FIG. 2B is a diagram showing a configuration example of the settlement device 40. In FIGS. 2 (A) and 2 (B), the same parts are designated by the same reference numerals. The settlement device 40 is basically operated by the customer.

Hereinafter, a configuration example of the settlement device 40 shown in FIG. 2B will be described with reference to FIG. 2A. The settlement device 40 includes a CPU 401, a ROM 402, a RAM 403, a hard disk 404, a display unit 405, a scanner unit 406, a card payment unit 408, a change machine 409, a printing unit 413, an audio output unit 414, and the like. It is provided with a communication unit 415. These can communicate with each other via the bus. The settlement device 40 may be further provided with a key operation unit, an imaging unit (camera), and a notification unit (a lamp such as a barber's pole).

The CPU 401 is a central processing unit, and controls the operation of the settlement device 40 by reading and executing a program stored in the ROM 402.
The ROM 402 is a read-only memory, and stores various information used by the CPU 401 including a program.

The RAM 403 is a read / write memory and stores various information. For example, the RAM 403 stores information read from the ROM 402 or the hard disk 404, information acquired from the outside, information generated in the process, and the like.

The hard disk 404 stores various information. The hard disk 404 may store, for example, a program executed by the CPU 401 instead of the ROM 402. Further, instead of the RAM 403, the information read from the ROM 402, the information acquired from the outside, the information generated in the processing, and the like may be stored.

The display unit 405 is a touch display, displays various information, and accepts various inputs.

The scanner unit 406 optically reads various information. For example, the scanner unit 406 scans a code (a two-dimensional code for settlement, which may be a one-dimensional code (bar code), etc.) displayed on the display unit of the mobile terminal 60, and is required for the settlement process. Read the information. Further, the scanner unit 406 scans a code (bar code, two-dimensional code, etc.) printed on another device (for example, a checkout ticket (registered trademark) issued by the registered payment device 30) and is required for the payment process. Information may be read. Further, the scanner unit 406 may scan the bar code attached to the product and read the product code. The scanner unit 406 may read the bar code attached to the name tag of the clerk. You may scan the code etc. and read the clerk code.

The card payment unit 408 is a payment mechanism using various cards (prepaid cards such as credit cards and transportation cards, cash cards at the time of debit payment, point cards at the time of point payment, etc.). The card payment unit 408 includes a card recognition unit (reading unit), a display unit, and an operation unit, but at least it may be provided with a card recognition unit. The card recognition unit may recognize various cards (for example, point cards, membership cards, shareholder cards, etc.) for granting benefits, discounts, and the like.

The change machine 409 (cash settlement unit) is a cash settlement mechanism, has a bill / coin slot and a bill / coin outlet, calculates the amount to be inserted into the slot, and determines the amount to be inserted and the purchase amount. The difference amount of change is calculated, and the change is discharged from the discharge port. When bills or coins are inserted into the slot, they are detected by a sensor (detection that there was insertion, detection of the number of coins by denomination, etc.).

The printing unit 413 prints and issues various media (receipt, checkout ticket, etc.).
The audio output unit 414 outputs audio. For example, the voice output unit 414 outputs voice guidance and the like.
The communication unit 415 transmits / receives information to / from other devices (management device 10, registered settlement device 30, other settlement device 40, monitoring device 50, mobile terminal 60, etc.).

Further, although not shown, the settlement device 40 is provided with a proximity sensor (human sensor) capable of detecting whether or not there is a human (customer, clerk, etc.) in the surroundings (specifically, the front surface).

Although the appearance and hardware configuration of the settlement device 40 have been described above, the description of the appearance and hardware configuration of the registered settlement device 30 and the like will be omitted. As described with reference to FIG. 1, the registration settlement device 30 is basically used by a clerk (the registration process and the settlement process are executed by the operation of the clerk).

The registration settlement device 30 is provided with a display unit and a scanner unit on both sides (clerk side and customer side), and a payment unit (card payment unit, cash payment unit) on one side (customer side). May be good. The registration settlement device 30 having the configuration has a plurality of operation modes (a mode in which the registration process is executed by the operation of the clerk and the settlement process is executed by the operation of the customer, and the registration process is performed by the operation of the customer, for example, depending on the operating status and the like. It may be a device that can be switched to any one of the mode of executing the settlement process, the mode of executing the registration process by the operation of the clerk and the customer, and the mode of executing the settlement process by the operation of the customer). .. Further, the registered settlement device 30 can be used for the service A as long as the settlement process is executed by the operation of the customer. That is, the customer can execute the registration process on the mobile terminal 60 and execute the settlement process on the registration settlement device 30.

FIG. 3 is a diagram showing an example of customer information, store information, and cart information. FIG. 3A shows an example of customer information (customer master) stored in the cloud server 20. FIG. 3B shows an example of store information (store master) stored in the cloud server 20. FIG. 3C is an example of cart information stored in the cloud server 20.

(Customer information)
The customer information illustrated in FIG. 3A includes customer identification information, customer name, customer registration date, cancellation information, customer rank, number of points, and the like.

The customer identification information is identification information that uniquely identifies a customer. The customer name is a customer's name, nickname, or the like. The customer registration date is the date and time of customer registration. The cancellation information is information regarding the cancellation of the registered product after registration (for example, the number of cancellations for each past visit). The customer rank is a rank according to the purchase record of the customer.

The cloud server 20 uses, for example, customer information (customer identification) of the customer based on the information entered by the customer in the input form at the time of customer registration (for example, when the mobile terminal 60 downloads or installs a specific application). Information, customer name, customer registration date, etc.) may be newly generated and stored. Further, the cloud server 20 may refer to the cart information and update the customer information (cancellation information, customer rank, number of points, etc.) as appropriate (for example, at a predetermined time every day).

The cloud server 20 may acquire and store customer information from the outside (a server at the headquarters (not shown), etc.). Further, the cloud server 20 stores a part or all of the customer information in another device (a file server or the like accessible to the cloud server 20) instead of or in addition to storing the customer information in the storage unit in the own device. You may remember.

(store information)
The store information illustrated in FIG. 3B includes store identification information, store name (branch name), store identification information 1, and store identification information 2.

The store identification information is identification information that uniquely identifies a store. The store identification information shown in FIG. 3B is composed of a store (store name) or company code and a branch code. The store name is the name of the store. The store name shown in FIG. 3B is composed of a store (store name) or a company and a branch name.

The store identification information 1 is information on a two-dimensional code (QR code (registered trademark), etc.) for specifying a store (a store where products are bought and sold) to be traded. The store identification information 2 is store location information (GPS information) for identifying a store with which a transaction is made. In the example shown in FIG. 3B, the store identification information and the store identification information 1 are different, but the store identification information and the store identification information 1 may be the same.

The cloud server 20 may acquire store information or the like from an outside (headquarters server (not shown) or the like) and store it. Further, the cloud server 20 stores a part or all of the store information in another device (a file server or the like accessible to the cloud server 20) instead of or in addition to storing the store information in the storage unit in the own device. You may remember.

(Cart information)
Cart information is information for managing individual transactions. The cloud server 20 generates cart information at the start of a transaction. In addition, the cloud server 20 updates the cart information according to the progress of the transaction (for example, every time a product is registered).

The cart information illustrated in FIG. 3C includes cart identification information, transaction start date and time, transaction end date and time, customer identification information, registered product information, pending product information, cancellation information, processing progress information, and the like.

The cart identification information is identification information that uniquely identifies the cart information. The cart identification information shown in FIG. 3C is composed of store identification information, a date, and a serial number (for example, a serial number for each store date).

The transaction start date and time is the transaction start date and time. The transaction start date and time may be, for example, the generation date and time of the cart information. The transaction start date and time may be the registration date and time of one product (the date and time when the registered product information (registered product 1) in FIG. 3C is stored). Both the generation date and time of the cart information and the registration date and time of the product of one item may be stored separately. The transaction end date and time is the transaction end date and time. For example, the transaction start date and time may be the settlement date and time.

The customer identification information is customer identification information that identifies the customer of the transaction. When the cart information is generated, the cart identification information, the transaction start date and time, and the customer identification information are generated, but since it is before the actual transaction (product registration) starts, other information (transaction end date and time, etc.) is generated. Not done. The settlement date and time may be the settlement start date and time or the settlement end date and time. As the transaction end date and time, both the settlement start date and time and the settlement end date and time may be stored separately.

The registered product information (total) is information that is updated every time a product is registered. The registered product information (total) includes the number of products (number of products), the estimated subtotal amount (for example, the subtotal amount before the discount etc. is reflected), the subtotal amount, and the like.

The registered product information (N; N is an integer) is the registered product information of the product of N items, and includes the product code, product name (product name), price, etc. of the product of one item. In the example shown in FIG. 3C, the registered product information (3) to the registered product information (5) are not shown.

The registered product information (N) may include the registration date and time of the product of the N item. That is, the cloud server 20 may store the registration date and time of the registered product as the registered product information. The registration date and time of each product may also be used as a material for determining the necessity of applying a service such as a time service and the effect after application.

Next, the reserved product will be described. A reserved product is a product that is purchased, but is not normally registered and registration is suspended. That is, if the product code is successfully scanned and the product can be identified based on the product code, it will be stored as registered product information, but if the product code scan is not successful, or If the product code is successfully scanned but the product cannot be identified based on the product code, it will be stored as pending product information.

The reserved products include a reserved product (reading NG) and a reserved product (inquiry NG). The reserved product (reading NG) is a reserved product that could not be registered because the scanning of the product code failed (scanning by the scanner became NG). For example, if the barcode of the product cannot be recognized due to wrinkles on the package, blurring or dirt on the barcode printing, the product is pretended to be read and the product is put into the basket. For example. That is, it can be said that the reserved product (reading NG) is a reserved product for confirming illicit operation, which requires confirmation of illicit operation because there is a possibility of illicit operation.

The mobile terminal 60 includes a sensor (for example, a gyro sensor, an acceleration sensor, a distance sensor, etc.) and is tilted to read a barcode (specifically, to read the barcode). It is possible to detect a state in which an object (commodity) is imaged within a certain range (for example, a distance of several centimeters to several tens of centimeters). If the mobile terminal 60 cannot read the barcode within a predetermined time (for example, within a predetermined time after the detection of the barcode reading operation), the mobile terminal 60 determines that the reading is NG as a timeout process.

For the pending product (inquiry NG), although the product code was successfully scanned (although the reading was not NG), the product master was inquired about the product with the product code, but the product identification failed (the product inquiry was made). It is a pending product that could not be registered due to (became NG).

The pending product information (total) is the number of reserved products (reading NG, inquiry NG) (number of products), the number of reserved products (reading NG) (confirmation of unauthorized operation), and the number of reserved products (inquiry NG). include.

The reserved product information (pending product N; N is an integer) is information on the reserved product of N items, and includes the reserved product type of the reserved product of N items. The reserved product type is information indicating whether the reserved product is a reserved product (reading NG) or a reserved product (inquiry NG). In this example, the reserved product type "1" is read NG, and the reserved product type "2" is inquiry NG.

Further, the reserved product information of the reserved product (reading NG) includes the image data (image data captured at the time of reading NG) of the reserved product (reading NG) in addition to the reserved product type "1 (reading NG)". For example, the reserved product information (3) includes the reserved product type "1 (reading NG)" and image data.

Further, the reserved product information of the reserved product (inquiry NG) includes the product code of the reserved product (inquiry NG) in addition to the reserved product type "2 (inquiry NG)". For example, the reserved product information (1) includes the reserved product type "2 (inquiry NG)" and the product code.

The cancellation information (total of this time) is the number of cancellations in this visit. The cancellation information (cancellation N; N is an integer) is information on the canceled product of N items, and includes the product code and quantity of the canceled product of N items.

Processing progress information (also referred to as accounting status information) is information for managing the current progress of individual transactions. The processing progress information is updated according to the progress of processing (transaction). Details of the processing progress information will be described later.

In addition, the cloud server 20 stores a part or all of the cart information in another device (a file server or the like accessible to the cloud server 20) instead of or in addition to storing the store information in the storage unit in the own device. You may remember.

4 and 5 are display examples and the like in the display unit of the mobile terminal 60. FIG. 4A is an example of the start screen of the service A. The mobile terminal 60 acquires information for identifying a store (store-specific information) and displays a start screen. For example, a customer who visits a store by displaying a two-dimensional code, which is a two-dimensional code of store identification information, near the entrance of the store (outputting the two-dimensional code on the display screen, pasting a medium on which the two-dimensional code is printed, etc.). The mobile terminal 60 may acquire the store identification information by scanning (reading) the two-dimensional code with the mobile terminal 60 by the (member). When a customer who visits the store activates a specific application, a screen instructing the customer to scan the two-dimensional code may be displayed, or when the customer who visits the store scans the two-dimensional code with the mobile terminal 60, the two-dimensional code may be scanned. A specific application may be started and the start screen may be displayed.

As shown in FIG. 4A, various buttons are arranged on the start screen. For example, the shopping start button 600 is a button for starting shopping. When the shopping start button 600 is operated, the mobile terminal 60 displays the registration screen shown in FIGS. 4B and later instead of the start screen.

FIG. 4B is a display in a scene following FIG. 4A. Specifically, FIG. 4B is a registration screen (initial registration screen) displayed after the shopping start button 600 is operated on the start screen of FIG. 4A. The upper side of the registration screen is the captured image display area 601 that mainly displays the captured image. The lower side of the registration screen is a registration information display area 602 that mainly displays product registration information.

FIG. 4C is a display in the scene following FIG. 4B. Specifically, FIG. 4 (C) captures the barcode attached to "○○ bread" as one item of the product on the registration screen (initial registration screen) of FIG. 4 (B). This is the registration screen for the time. That is, when registering a desired product (product to be purchased), the customer captures an image of a barcode attached to the product as shown in FIG. 4 (C).

FIG. 4 (D) is a display in the scene following FIG. 4 (C). Specifically, FIG. 4D is a display in the scene where the registration of one item of product (○○ bread) is completed. Note that FIG. 4D is a display example immediately after the product is specified (that is, when the barcode is still being imaged). Therefore, in the display example of FIG. 4D, the barcode of the product is displayed in the captured image display area 601.

The mobile terminal 60 displays the registration information and the like of the product specified by imaging the barcode in the registration information display area 602. For example, as shown in FIG. 4D, the mobile terminal 60 displays registration information (product name, quantity, amount of money) of a product (○○ bread) identified by imaging a barcode (reference numeral a). ). The mobile terminal 60 displays a part (quantity) of the registration information as a quantity button 603. The quantity button 603 is a button for changing the quantity. In addition, the mobile terminal 60 displays total information (total points, total amount of money) (reference numeral b). In addition, the mobile terminal 60 displays the accounting button 604 to be operated when proceeding to settlement (accounting) (when completing the registration of the product).

FIG. 5A is a display in a scene following FIG. 4D. Specifically, FIG. 5A is a two-dimensional code display screen displayed after the checkout button 604 is operated on the registration screen of FIG. 4D. The two-dimensional code 605 for settlement is displayed on the two-dimensional code display screen. Further, on the two-dimensional code display screen, a display field 606 for the approximate total, a back button 607, and an inquiry code button 608 (described later) are arranged. The back button 607 is a button for returning to shopping (restarting shopping). When the back button 607 is operated, the mobile terminal 60 displays a registration screen (a registration screen immediately before the operation of the checkout button 604) instead of the two-dimensional code display screen. FIG. 5B shows how the settlement device 40 reads the two-dimensional code 605 for settlement. 5 (C) and 5 (D) will be described later.

6 and 7 are display examples on the display unit 405 of the settlement device 40. FIG. 6A is a settlement screen (initial settlement screen). FIG. 6B is a display in the scene following FIG. 6A. Specifically, FIG. 6B is a settlement screen (payment type selection screen) displayed after the two-dimensional code 605 for settlement is read on the settlement screen (initial settlement screen) of FIG. 6A. Is. That is, when the settlement device 40 reads the settlement two-dimensional code 605 displayed by the mobile terminal 60 as shown in FIG. 5 (B) on the settlement screen (initial settlement screen) shown in FIG. 6 (A). Instead of the settlement screen (initial settlement screen) shown in FIG. 6 (A), the settlement screen (payment type selection screen) shown in FIG. 6 (B) is displayed.

FIG. 6C is a display in the scene following FIG. 6B. Specifically, FIG. 6C is a settlement screen (cash insertion screen) displayed after the "cash" button is operated on the settlement screen (payment type selection screen) of FIG. 6B. Hereinafter, the cash will be inserted, the necessary change and receipt will be issued, and the settlement will be completed, but the explanation of the settlement screen after the cash is inserted will be omitted.

The settlement device 40 may display a settlement screen (initial settlement screen) based on the operation of the customer. For example, the settlement device 40 displays an initial screen as shown in FIG. 6 (D), and when the "payment start" button on the initial screen is operated, the initial screen is replaced with the initial screen shown in FIG. 6 (D). The registration screen (initial settlement screen) shown in FIG. 6A may be displayed. That is, the initial screen of FIG. 6 (D) may be changed to the registration screen (initial settlement screen) of FIG. 6 (A).

Further, when the settlement device 40 reads the settlement two-dimensional code 605, it is a transaction that requires a clerk to call for the transaction specified by the settlement two-dimensional code 605 (for example, the settlement two-dimensional code). When the cart information specified by 605 includes the pending product information and the cancellation information), the clerk call process (for example, the monitoring device 50, the registration settlement device 30, the clerk's call to a mobile terminal (not shown) used by the clerk, etc. (Notification, etc.) may be executed, and for example, as shown in FIG. 6 (E), the customer may be notified that the clerk is being called.

FIG. 7A is a settlement screen (payment input screen) displayed on the display unit 405 of the settlement device 40 when the settlement two-dimensional code 605 cannot be read. That is, when the settlement device 40 can read the two-dimensional code 605 for settlement on the settlement screen (initial settlement screen) shown in FIG. 6A, the settlement screen as shown in FIG. 6B (Payment type selection screen) is displayed, but if the two-dimensional code 605 for settlement cannot be read, the settlement screen (input screen for settlement) as shown in FIG. 7A is displayed. The details of FIG. 7 (A) and FIGS. 7 (B) to 7 (F) will be described later.

FIG. 8 is an explanatory diagram illustrating processing progress information. As described above, the processing progress information in the cart information is updated according to the progress of processing (transaction).

FIG. 8A shows a first method (Example 1: described later) in which a customer inputs an inquiry code on the settlement device 40 when the two-dimensional code 605 for settlement cannot be read, and for settlement. It is explanatory drawing explaining the processing progress information in the 1st method (Example 3: later) which causes a customer to select an inquiry code on the settlement apparatus 40 when the 2D code 605 cannot be read.

The processing progress information of FIG. 8A can take five values (“0”, “10”, “20”, “40”, “50”). The value of the processing progress information in FIG. 8 (A) is 0 → 10 → 20 regardless of whether the two-dimensional code 605 for settlement can be read (in the case of OK) or not (in the case of NG). → 40 → 50.

Each value of the processing progress information of FIG. 8A will be described.
The value "0" corresponds to "cart information generation". When the current progress status is after the cart information is generated and before the product registration of one item, the value of the processing progress information is "0 (cart information generation)". Alternatively, when the processing progress information has a value of "0 (cart information generation)", the current progress status is after the cart information is generated and before the product registration of one item.
The value "10" corresponds to "in shopping". If the current progress status is after the product registration of one item and before the receipt of the accounting instruction, the value of the processing progress information is "10 (in shopping)". Alternatively, when the processing progress information has a value of "10 (in shopping)", the current progress status is after the product registration of one item and before the receipt of the accounting instruction. The accounting instruction means that the mobile terminal 60 receives an operation of the accounting button 604 from the customer.
The value "20" corresponds to "accounting instruction reception". If the current progress status is after the receipt of the accounting instruction and before the display of the settlement screen, the value of the processing progress information is "20 (accounting instruction acceptance)". Alternatively, when the processing progress information has the value "20 (accounting instruction reception)", the current progress status is after the receipt of the accounting instruction and before the display of the settlement screen.
The value "40" corresponds to "payment screen display". When the current progress status is after the settlement screen is displayed and before the settlement is completed, the value of the processing progress information is "40 (settlement screen display)". Alternatively, when the processing progress information has a value of "40 (settlement screen display)", the current progress status is after the settlement screen is displayed and before the settlement is completed.
The value "50" corresponds to "payment completed".

FIG. 8B shows a second method (Example 2: described later) in which a customer inputs an inquiry code on the settlement device 40 when the two-dimensional code 605 for settlement cannot be read, and for settlement. It is explanatory drawing explaining the processing progress information in the 2nd method (Example 4: later) which makes a customer select an inquiry code on the settlement apparatus 40 when the 2D code 605 cannot be read.

The processing progress information of FIG. 8B can take six values (“0”, “10”, “20”, “30”, “40”, “50”). Comparing the processing progress information of FIG. 8 (A) with the processing progress information of FIG. 8 (B), the processing progress information of FIG. 8 (B) has a value of "30" with respect to the processing progress information of FIG. 8 (A). Is added. The value of the processing progress information in FIG. 8B changes in the order of 0 → 10 → 20 → 40 → 50 when the two-dimensional code 605 for settlement can be read (in the case of OK), and cannot be read. In the case of NG (in the case of NG), the transition is 0 → 10 → 20 → 30 → 40 → 50.

Each value of the processing progress information of FIG. 8B will be described.
The value “0” of the processing progress information in FIG. 8 (B) is the same as the value “0” of the processing progress information in FIG. 8 (A), and corresponds to “cart information generation”.
The value “10” of the processing progress information in FIG. 8 (B) is the same as the value “10” of the processing progress information in FIG. 8 (A), and corresponds to “in shopping”.
The value "20" of the processing progress information of FIG. 8 (B) is the same as the value "20" of the processing progress information of FIG. 8 (A), and corresponds to "accounting instruction reception". However, in the processing progress information of FIG. 8B, when the current progress status is after the receipt of the accounting instruction and before the display of the settlement screen or before the reception of the inquiry code display instruction, the value of the processing progress information. Is "20 (accounting instruction reception)". Alternatively, when the processing progress information has the value "20 (accounting instruction reception)", the current progress status is after the receipt of the accounting instruction and before the display of the settlement screen or the reception of the inquiry code display instruction. ..
The value "30" of the processing progress information in FIG. 8B corresponds to the "inquiry code display instruction reception". When the current progress status is after receiving the inquiry code display instruction and before displaying the settlement screen, the value of the processing progress information is "30 (inquiry code display instruction reception)". Alternatively, when the processing progress information has the value "30 (inquiry code display instruction reception)", the current progress status is after the reception of the inquiry code display instruction and before the display of the settlement screen.
The value “40” of the processing progress information in FIG. 8 (B) is the same as the value “40” of the processing progress information in FIG. 8 (A), and corresponds to the “payment screen display”.
The value “50” of the processing progress information in FIG. 8 (B) is the same as the value “50” of the processing progress information in FIG. 8 (A), and corresponds to “payment completed”.

9 and 10 are sequence diagrams illustrating a flow of product purchase by the sales system 1 (specifically, service A provided by the specific sales system). Specifically, in FIGS. 9 and 10, a customer (a member who owns a mobile terminal 60 in which a specific application is installed) visits a store (a store in which service A operates) and uses the mobile terminal 60. It is installed outside the mobile terminal 60, the payment device 40 installed in the store, the data center, etc. until the product displayed in the store is registered by using it and the payment for the registered product is completed. An example of the processing flow in each of the cloud servers 20 is shown. The left side of FIG. 6 is the processing of the mobile terminal 60, the center is the processing of the settlement device 40, and the right side is the processing of the cloud server 20. FIG. 10 is a continuation of FIG.

The sequence diagram of FIG. 11 (described later) and the like shows the flow of product purchase when the settlement device 40 does not recognize the two-dimensional code 605 for settlement, but the sequence diagrams of FIGS. 9 and 10 show the flow of product purchase. The flow of product purchase when the settlement apparatus 40 recognizes the two-dimensional code 605 for settlement is shown.

Further, since the sequence diagrams of FIGS. 9 and 10 show the flow when the settlement device 40 can recognize (when the reading is OK), any of the ones shown in FIGS. 8 (A) and 8 (B). Even with the processing progress information, the value of the processing progress information changes in the order of 0 → 10 → 20 → 40 → 50 according to the progress of the processing (transaction). In the description of the sequence diagram of FIGS. 9 and 10, it is assumed that the processing progress information of any one of FIGS. 8 (A) and 8 (B) is applied.

Step S1: The mobile terminal 60 of FIG. 10 acquires store identification information. For example, a customer who visits a store scans a two-dimensional code displayed near the entrance of the store with the mobile terminal 60, so that the mobile terminal 60 acquires store identification information.

Step S2: The mobile terminal 60 that has acquired the store identification information transmits the store identification information to the cloud server 20 together with the customer identification information (user ID).

(Address of cloud server 20)
At the time of executing step S2, the address (destination information) of the cloud server 20 is stored in the mobile terminal 60. Specifically, the mobile terminal 60 stores the address of the cloud server 20 at the time of customer registration (for example, when installing a specific application on the mobile terminal 60). For example, the address of the cloud server 20 is held in the specific application, and when the customer registration is completed, the address of the cloud server 20 may be the storage unit of the mobile terminal 60 (the user storage area of the specific application may be used). It may be stored in a storage area common to all applications).

(About customer identification information)
At the time of executing step S2, the customer identification information is stored in the mobile terminal 60. Specifically, the mobile terminal 60 stores customer identification information at the time of customer registration. In customer registration, the information entered in the registration form is stored in the cloud server 20 as customer information using the mobile terminal 60, but the mode in which the customer identification information is entered in the registration form (the customer specifies the customer identification information). In this case, the customer identification information entered in the registration form is stored in the storage unit of the mobile terminal 60, transmitted to the cloud server 20, and stored as customer information in the cloud server 20. On the other hand, in the case where the customer identification information is not input to the registration form (the cloud server 20 generates the customer identification information), the customer identification information generated by the cloud server 20 is stored in the cloud server 20 as customer information. , Is transmitted to the mobile terminal 60, and is also stored in the storage unit of the mobile terminal 60.

Step S3: The cloud server 20 that has received the customer identification information and the store identification information from the mobile terminal 60 generates the cart information of the transaction. The cloud server 20 stores "0 (cart information generation)" as the value of the processing progress information in the cart information.

Step S4: The cloud server 20 that generated the cart information of the transaction generates screen information (screen information of the start screen, screen information of the initial registration screen), and transmits the generated screen information to the mobile terminal 60 together with the cart identification information. do.

Step S5: The mobile terminal 60 that has received the cart identification information and the screen information from the cloud server 20 stores the cart identification information and displays the start screen on the display unit as shown in FIG. 4A.

Step S6: In response to the operation of the shopping start button 600, the mobile terminal 60 displays a registration screen (initial registration screen) on the display unit as shown in FIG. 4 (B).

In the sequence diagram of FIG. 9, the screen information of the initial registration screen is transmitted and received together with the screen information of the start screen, but the screen information of the initial registration screen may be transmitted and received after the screen information of the start screen is transmitted and received. .. That is, the step S6 may operate as described in (1) to (3) below, for example. (1) The mobile terminal 60 transmits information to the effect that the shopping start button has been operated to the cloud server 20 together with the customer identification information. (2) The cloud server 20 that has received the information that the shopping start button has been operated and the customer identification information from the mobile terminal 60 generates screen information (screen information of the initial registration screen), and the generated screen information is used as the mobile terminal. Send to 60. (3) The mobile terminal 60 that has received the screen information from the cloud server 20 displays the initial registration screen on the display unit.

Step S7: In response to the customer's reading operation, the mobile terminal 60 scans the barcode attached to the product and reads the product code.

Step S8: The mobile terminal 60 transmits the read product code together with the cart identification information to the cloud server 20.

Step S9: The cloud server 20 that has received the cart identification information and the product code from the mobile terminal 60 updates the cart information identified by the cart identification information. For example, when the cloud server 20 receives the product code as an N item, the cloud server 20 stores the product code as the product code of the registered product information (registered product N), and stores the product name and price corresponding to the product code in the product information. Obtained from, and stored as the product and price of the registered product information (registered product N). In addition, the cloud server 20 updates the registered product information (total). Further, the cloud server 20 updates the value of the processing progress information from "0 (cart information generation)" to "10 (during shopping)".

Step S10: The cloud server 20 that has updated the cart information generates screen information (screen information of the registration screen corresponding to the updated cart information), and transmits the generated screen information to the mobile terminal 60 together with the cart identification information.

Step S11: The mobile terminal 60 that has received the cart identification information and the screen information from the cloud server 20 confirms whether it matches the stored cart identification information (the cart identification information stored in step S5), and then the screen information. The registration screen based on is displayed on the display unit. That is, the product is added to the registration screen of the mobile terminal 60.

Although simplified in FIG. 9 for convenience of explanation, the processes of steps S7 to S11 are repeatedly executed every time the product code is read in step S7 until the accounting instruction is received in the following step S12. That is, after step S11, there are a case where the accounting instruction is accepted (when proceeding to the following step S12) and a case where the product code is read again (when returning to the above step S7). When the product code is read again (when returning to step S7), the value of the processing progress information is maintained as "10 (during shopping)" in step S9 to be executed again (same value "10"). You may overwrite it with "10 (during shopping)").

Step S12: The mobile terminal 60 receives an accounting instruction as a customer operation. Specifically, the mobile terminal 60 accepts the operation of the checkout button 604.

Step S13: The mobile terminal 60 that has received the accounting instruction transmits the accounting instruction acceptance notification to the cloud server 20 together with the cart identification information.

Step S15: The cloud server 20 that has received the cart identification information and the accounting instruction acceptance notification from the mobile terminal 60 updates the cart information identified by the cart identification information. Specifically, the cloud server 20 updates the value of the processing progress information in the cart information from "10 (during shopping)" to "20 (accounting instruction reception)".

Step S15: Further, the mobile terminal 60 that has received the accounting instruction generates and displays the two-dimensional code 605 for settlement. That is, the mobile terminal 60 has information necessary for executing the settlement process for the purchased product by the mobile terminal 60 (for example, the cart identification information of the cart information, the inquiry code for inquiring (identifying) the cart information). , URL for accessing the cart information, etc.) is two-dimensionally coded to generate and display a two-dimensional code 605 for settlement. For example, the mobile terminal 60 generates a two-dimensional code 605 for settlement in which the cart identification information is two-dimensionally coded, and displays the generated two-dimensional code 605 for settlement in, for example, the two-dimensional code shown in FIG. 5 (A). Display on the screen.

(About inquiry code)
As shown in FIG. 3C, the cart identification information is composed of store identification information, a date, and a serial number (for example, a serial number for each store date). Of the store identification information, the date, and the serial number, at least the store identification information and the date can be recognized by the settlement device 40 that reads the two-dimensional code 605 for settlement. That is, the settlement device 40 can recognize (generate) the cart identification information by acquiring the serial number from the settlement two-dimensional code 605. As described above, the serial number constituting a part of the cart identification information may be used as the inquiry code, and in the sequence diagrams of FIGS. 9 and 10 (the same applies to other sequence diagrams such as FIG. 11 (described later)). As the inquiry code, the serial number that forms part of the cart identification information shall be used.

Step S20 of FIG. 10: The settlement device 40 senses the presence of a customer by means of a proximity sensor (presence sensor).

Step S21: The settlement device 40 determines that the reading operation by the customer has been detected. For example, the checkout device 40 has a square (or, for example, a white background in which fine black dots are arranged) as an object within a predetermined time (for example, within a predetermined time after detecting the presence of a customer). When a substantially square) or a figure having the same or similar feature points as the feature points of the two-dimensional code) is recognized, it is determined that the reading operation by the customer is detected.

That is, as shown in FIG. 5B, when the customer performs an operation of causing the settlement device 40 (scanner unit 406) to read the two-dimensional code 605 for settlement, the settlement device 40 actually causes the two-dimensional code for settlement. Before recognizing 605, it recognizes what seems to be a two-dimensional code as an object. Therefore, it is determined that the settlement device 40 has detected the reading operation by the customer by recognizing what seems to be a two-dimensional code as an object. If the settlement device 40 does not recognize what seems to be a two-dimensional code as an object within a predetermined time (for example, within a predetermined time after detecting the existence of the customer), the settlement device 40 does not detect the reading operation by the customer. Judge.

Step S23: The settlement device 40 recognizes (reads) the two-dimensional code 605 for settlement. If the settlement device 40 does not recognize the two-dimensional code 605 for settlement within a predetermined time (for example, within a predetermined time after recognizing what seems to be a two-dimensional code), the settlement device 40 recognizes the two-dimensional code. Judge that it was not.

Step S50: The settlement device 40 that has read the two-dimensional code requests the cloud server 20 for a settlement screen (for example, a payment type selection screen). For example, the settlement device 40 transmits the information requesting the settlement screen (settlement screen request information) to the cloud server 20 via the management device 10 together with the cart identification information acquired from the two-dimensional code.

Step S55: The cloud server 20 that has received the cart identification information and the settlement screen request information from the settlement device 40 updates the cart information identified by the cart identification information. Specifically, the cloud server 20 calculates a subtotal amount (final subtotal amount reflecting various discounts and the like) and stores it as a subtotal amount (calculated subtotal amount). Further, the cloud server 20 updates the value of the processing progress information from "20 (accounting instruction reception)" to "40 (payment screen display)".

Step S57: The cloud server 20 that has updated the cart information displays screen information (screen information of the settlement screen including the subtotal amount. For example, screen information of the settlement screen (payment type selection screen) as shown in FIG. 6B). The generated screen information is transmitted to the settlement device 40 together with the cart identification information via the management device 10.

Step S58: The settlement device 40, which has received the cart identification information and the screen information from the cloud server 20, displays the settlement screen (for example, the payment type selection screen displaying the subtotal amount as shown in FIG. 6B) on the display unit 405. indicate.

Step S59: The settlement device 40 displaying the settlement screen executes payment (settlement). Specifically, the settlement device 40 accepts the selection of the payment type. In the case of cash, the deposit is accepted, the amount of change is calculated, and if there is change, the change is released and a receipt is issued.

Step S60: The settlement device 40 for which payment (settlement) has been completed transmits a settlement completion notification together with the cart identification information to the cloud server 20 via the management device 10.

Step S61: The cloud server 20 that has received the cart identification information and the settlement completion notification from the settlement device 40 updates the cart information identified by the cart identification information. For example, the cloud server 20 stores the transaction end date and time (settlement date and time). Further, the cloud server 20 updates the value of the processing progress information in the cart information from "40 (settlement screen display)" to "50 (settlement completed)".

11 to 14 are sequence diagrams illustrating a flow of product purchase by the sales system 1 (specifically, service A provided by the specific sales system). Specifically, the sequence diagram of FIG. 11 shows a first aspect (implementation) in which a customer is required to input an inquiry code on the settlement device 40 when the settlement device 40 does not recognize the two-dimensional code 605 for settlement. It is a sequence diagram explaining the flow of Example 1). The sequence diagram of FIG. 12 shows the flow of the second aspect (Example 2) in which the customer is made to input the inquiry code on the settlement device 40 when the settlement device 40 does not recognize the two-dimensional code 605 for settlement. It is a sequence diagram explaining. The sequence diagram of FIG. 13 shows the flow of the first aspect (Example 3) in which the customer is made to select the inquiry code on the settlement device 40 when the settlement device 40 does not recognize the two-dimensional code 605 for settlement. It is a sequence diagram explaining. The sequence diagram of FIG. 14 shows the flow of the second aspect (Example 4) in which the customer is made to select the inquiry code on the settlement device 40 when the settlement device 40 does not recognize the two-dimensional code 605 for settlement. It is a sequence diagram explaining.

If the settlement device 40 does not recognize the two-dimensional code 605 for settlement, the clerk may perform the operation. That is, in FIG. 11 (Example 1) and FIG. 12 (Example 2), the clerk may input the inquiry code instead of the customer. In FIG. 13 (Example 3) and FIG. 14 (Example 4), the clerk may select the inquiry code instead of the customer. However, in the following description, it is assumed that the customer performs the operation when the settlement device 40 does not recognize the two-dimensional code 605 for settlement.

(Example 1)
Using the sequence diagram of FIG. 11, a first method for causing the customer to input the inquiry code on the settlement device 40 when the two-dimensional code 605 for settlement cannot be read will be described as the first embodiment. In the first embodiment, the processing progress information of FIG. 8A is applied.

The flow until the mobile terminal 60 generates and displays the two-dimensional code 605 for settlement is the same as the flow when the two-dimensional code 605 for settlement can be read (FIG. 9), and is therefore omitted. In step S15 of FIG. 9, it is assumed that the mobile terminal 60 is displaying the two-dimensional code display screen shown in FIG. 5 (A).

Step S20 of FIG. 11: The settlement device 40 senses the presence of a customer by a proximity sensor (human sensor) as in step S20 of FIG.

Step S21: The settlement device 40 determines that the reading operation by the customer has been detected, as in step S21 of FIG. That is, when the settlement device 40 recognizes what seems to be a two-dimensional code as an object within a predetermined time (for example, within a predetermined time after detecting the existence of the customer), it determines that the reading operation by the customer has been detected.

Step S24: The settlement device 40 determines that the settlement device 40 has not recognized the two-dimensional code 605 for settlement. For example, if the settlement device 40 does not recognize the two-dimensional code 605 for settlement within a predetermined time (for example, within a predetermined time after recognizing what seems to be a two-dimensional code), the settlement device 40 recognizes the two-dimensional code. Judge that it was not. That is, if the settlement device 40 detects the reading operation by the customer (step S21) but does not recognize the settlement two-dimensional code 605 within a predetermined time, the settlement device 40 performs the settlement two-dimensional code 605 as a time-out process. Judge that it did not recognize.

Step S30: The settlement device 40, which has detected that the two-dimensional code 605 for settlement cannot be recognized, displays an input screen for settlement including an input field for the inquiry code. For example, the settlement device 40 displays a settlement input screen as shown in FIG. 7A. On the settlement input screen shown in FIG. 7 (A), the fact that a reading error has occurred (reference numeral a) and the instruction to the customer (reference numeral b) are displayed, and the inquiry code input field (reference numeral c) is displayed. ) Is provided.

Step S32: The mobile terminal 60 receives an inquiry code display instruction as a customer operation. Specifically, the mobile terminal 60 displays the two-dimensional code display screen shown in FIG. 5 (A) in step S15 of FIG. 9, but the two-dimensional code display screen shown in FIG. 5 (A). In, the operation (touch) of the inquiry code button 608 displayed as "display the inquiry code" is accepted. In other words, the customer operates the mobile terminal 60 according to the settlement input screen displayed on the settlement device 40 (for example, the instruction (reference numeral b) on the settlement input screen of FIG. 7A) (for example, FIG. 5). (A) Operate the inquiry code button 608 on the two-dimensional code display screen).

Step S35: The mobile terminal 60 that has received the inquiry code display instruction displays the inquiry code. For example, the mobile terminal 60 displays the serial number forming a part of the stored cart identification information as an inquiry code on the two-dimensional code display screen as shown in FIG. 5C.

Step S36: The settlement device 40 accepts the input of the inquiry code via the settlement input screen. That is, the customer inputs the inquiry code displayed on the mobile terminal 60 in step S35 in the inquiry code input field on the settlement input screen of the settlement device 40.

Step S51: The settlement device 40 that has received the input of the inquiry code requests the cloud server 20 for the settlement screen (for example, the payment type selection screen). For example, the settlement device 40 together with the information requesting the settlement screen (settlement screen request information) together with the cart identification information (store identification information, the date, the inquiry code input in step S36, and the cart identification information). , The information is transmitted to the cloud server 20 via the management device 10.

Step S53: Whether or not the cart identification information acquired from the settlement device 40 is valid for the cloud server 20 that has received the cart identification information and the settlement screen request information from the settlement device 40 (that is, the input of the inquiry code by the customer is valid). Whether or not) is judged. Specifically, if the value of the processing progress information in the cart information identified by the cart identification information acquired from the settlement device 40 is "20 (accounting instruction reception)", the cloud server 20 acquires from the settlement device 40. It is determined that the cart identification information (inquiry code) obtained is valid, and if it is not "20 (accounting instruction reception)", it is determined that the cart identification information (inquiry code) acquired from the settlement device 40 is not valid.

If the cloud server 20 determines that the cart identification information (inquiry code) acquired from the settlement device 40 is not valid, the inquiry code has resulted in an input error, the inquiry code needs to be re-entered, and the like. The message may be displayed on the settlement device 40 (payment input screen). The cloud server 20 may display the above message on the mobile terminal 60 in place of or in addition to the payment device 40.

Step S55: The cloud server 20 that determines that the cart information identified by the cart identification information acquired from the checkout device 40 is appropriate updates the cart information in the same manner as in step S55 of FIG. That is, the cloud server 20 calculates the subtotal amount (final subtotal amount reflecting various discounts and the like) and stores it as the subtotal amount (calculated subtotal amount). Further, the cloud server 20 updates the value of the processing progress information from "20 (accounting instruction reception)" to "40 (payment screen display)".

Since the following flow is the same as that in FIG. 10, the description thereof will be omitted.

In the first embodiment, when the customer operates on the mobile terminal 60 (such as the operation of the inquiry code button 608) after the settlement input screen is displayed on the settlement device 40, the mobile terminal 60 is operated. An example of displaying the inquiry code has been described (steps S30, S32, S35), but even if there is no customer operation on the mobile terminal 60 after the settlement input screen is displayed on the settlement device 40, the mobile terminal 60 May display the inquiry code. For example, the mobile terminal 60 may display the inquiry code from the stage of step S15 in FIG. 9 (for example, the two-dimensional code display screen as shown in FIG. 5C may be displayed). In the mode in which the mobile terminal 60 displays the inquiry code from the stage of step S15 of FIG. 9, when the settlement device 40 detects that the two-dimensional code 605 for settlement cannot be recognized, the settlement is as shown in FIG. 7 (A). Instead of the input screen for payment, the input screen for settlement as shown in FIG. 7B is displayed. In the settlement input screen shown in FIG. 7 (A), the operation on the mobile terminal 60 is instructed to the customer (reference numeral b in FIG. 7 (A)), but the settlement input shown in FIG. 7 (B). On the screen, the operation on the mobile terminal 60 is not instructed to the customer (reference numeral d in FIG. 7A).

(Example 2)
Subsequently, using the sequence diagram of FIG. 12, as the second embodiment, a second method of causing the customer to input the inquiry code on the settlement device 40 when the two-dimensional code 605 for settlement cannot be read will be described. do. In the second embodiment, the processing progress information of FIG. 8B is applied.

Note that steps S20, S21, S24, S30, S32, S35, S36, and S51 in FIG. 12 are the same as steps S20, S21, S24, S30, S32, S35, S36, and S51 in FIG. The description in is omitted.

Step S33 of FIG. 12: The mobile terminal 60 that has received the inquiry code display instruction sends the inquiry code display instruction acceptance notification to the cloud server 20 together with the cart identification information.

Step S34: The cloud server 20 that has received the cart identification information and the inquiry code display instruction reception notification from the mobile terminal 60 updates the cart information identified by the cart identification information. Specifically, the cloud server 20 updates the value of the processing progress information in the cart information from "20 (accounting instruction reception)" to "30 (inquiry code display instruction reception)".

Step S54: The cloud server 20 that has received the cart identification information and the settlement screen request information from the settlement device 40 is whether or not the cart identification information acquired from the settlement device 40 is valid (that is, the input of the inquiry code by the customer is valid). Whether or not) is judged. Specifically, if the value of the processing progress information in the cart information identified by the cart identification information acquired from the checkout device 40 is "30 (inquiry code display instruction reception)", the cloud server 20 setstle the checkout device 40. It is judged that the cart identification information (inquiry code) obtained from is valid, and if it is not "30 (inquiry code display instruction reception)", the cart identification information (inquiry code) obtained from the settlement device 40 is judged to be invalid. do.

If the cloud server 20 determines that the cart identification information (inquiry code) acquired from the settlement device 40 is not valid, the inquiry code has resulted in an input error, the inquiry code needs to be re-entered, and the like. The message may be displayed on the settlement device 40 (payment input screen). The cloud server 20 may display the above message on the mobile terminal 60 in place of or in addition to the payment device 40.

Step S56: The cloud server 20 that determines that the cart information identified by the cart identification information acquired from the checkout device 40 is appropriate updates the cart information. Specifically, the cloud server 20 calculates a subtotal amount (final subtotal amount reflecting various discounts and the like) and stores it as a subtotal amount (calculated subtotal amount). Further, the cloud server 20 updates the value of the processing progress information from "30 (inquiry code display instruction reception)" to "40 (payment screen display)".

(Example 3)
Subsequently, using the sequence diagram of FIG. 13, as Example 3, a first method of causing the customer to select an inquiry code on the settlement device 40 when the two-dimensional code 605 for settlement cannot be read will be described. do. In the third embodiment, the processing progress information of FIG. 8A is applied.

Since steps S20, S21, S24, and S55 in FIG. 13 are the same as steps S20, S21, S24, and S55 in FIG. 11, the description in FIG. 13 will be omitted.

Step S41: The settlement device 40, which has detected that the two-dimensional code 605 for settlement cannot be recognized, requests the cloud server 20 for a settlement selection screen that displays a candidate for the inquiry code so that it can be selected. For example, the settlement device 40 transmits information requesting the settlement selection screen (settlement selection screen request information) to the cloud server 20 via the management device 10.

Step S42: The cloud server 20 that has received the settlement selection screen request information from the settlement device 40 extracts the corresponding cart information. Specifically, the cloud server 20 extracts cart information in which the value of the processing progress information is "20 (accounting instruction reception)".

Step S44: The cloud server 20 from which the cart information has been extracted is the screen information (screen information of the settlement selection screen that displays the candidate of the inquiry code corresponding to the extracted cart information in a selectable manner. For example, it is shown in FIG. 7C. The screen information of the settlement selection screen that displays the candidate of the inquiry code so as to be selectable) is generated, and the generated screen information is transmitted to the settlement device 40 via the management device 10.

Step S45: The settlement device 40, which has received screen information from the cloud server 20, displays a settlement screen (for example, a settlement selection screen that displays inquiry code candidates in a selectable manner as shown in FIG. 7C). Display on 405. In addition, on the settlement selection screen shown in FIG. 7C, the fact that a reading error has occurred (reference numeral a) and the instruction to the customer (reference numeral e) are displayed, and the inquiry code selection button (reference code e) is displayed. Reference numeral f) is provided.

Step S46: The settlement device 40 accepts the selection of the inquiry code via the settlement selection screen.

Step S52: The settlement device 40 that has received the selection of the inquiry code requests the cloud server 20 for the settlement screen (for example, the payment type selection screen). For example, the settlement device 40 includes information requesting the settlement screen (settlement screen request information) together with cart identification information (store identification information, date, and cart identification information obtained from the inquiry code selected in step S46). It is transmitted to the cloud server 20 via the management device 10.

Step S55: The cloud server 20 that has received the cart identification information and the settlement screen request information from the settlement device 40 updates the cart information in the same manner as in step S55 of FIG. That is, the cloud server 20 calculates the subtotal amount (final subtotal amount reflecting various discounts and the like) and stores it as the subtotal amount (calculated subtotal amount). Further, the cloud server 20 updates the value of the processing progress information from "20 (accounting instruction reception)" to "40 (payment screen display)".

Although the example in which the inquiry code is not displayed on the mobile terminal 60 has been described in the third embodiment, the inquiry code may be displayed on the mobile terminal 60. For example, the mobile terminal 60 may display the inquiry code from the stage of step S15 in FIG. 9 (for example, the two-dimensional code display screen as shown in FIG. 5C may be displayed). In the mode in which the mobile terminal 60 displays the inquiry code from the stage of step S15 of FIG. 9, when the settlement device 40 detects that the two-dimensional code 605 for settlement cannot be recognized, the settlement is as shown in FIG. 7 (C). Instead of the input screen for payment, the input screen for settlement as shown in FIG. 7 (D) is displayed. The settlement input screen shown in FIG. 7 (C) does not notify that the inquiry code is displayed on the mobile terminal 60 (reference numeral e in FIG. 7 (C)), but is shown in FIG. 7 (D). On the settlement input screen, it is notified that the inquiry code is displayed on the mobile terminal 60 (reference numeral g in FIG. 7D).

(Example 4)
Subsequently, using the sequence diagram of FIG. 14, as the fourth embodiment, a second method of causing the customer to select the inquiry code on the settlement device 40 when the two-dimensional code 605 for settlement cannot be read will be described. do. In the fourth embodiment, the processing progress information of FIG. 8B is applied.

Since steps S20, S21, and S24 in FIG. 14 are the same as steps S20, S21, and S24 in FIG. 11, the description in FIG. 14 will be omitted. Further, since steps S32, S33, S34, and S35 in FIG. 14 are the same as steps S32, S33, S34, and S35 in FIG. 12, the description in FIG. 14 will be omitted. Further, since steps S41, S44, S45, S46, and S52 in FIG. 14 are the same as steps S41, S44, S45, S46, and S52 in FIG. 13, a part or all of the description in FIG. 14 will be omitted.

Step S31: The settlement device 40 that has detected the unrecognizable two-dimensional code 605 for settlement displays a message instructing a predetermined operation. For example, the settlement device 40 displays an operation instruction screen as shown in FIG. 7 (E). On the operation instruction screen shown in FIG. 7 (E), a reading error (reference numeral a) and an instruction to the customer (reference numeral h) are displayed, and an extraction button (reference numeral i) is provided. ing.

Step S40: The settlement device 40 receives a display instruction on the settlement selection screen via the operation instruction screen. For example, the settlement device 40 accepts the operation (touch) of the extraction button (reference numeral i) on the operation instruction screen shown in FIG. 7 (E).

Step S43: The cloud server 20 that has received the settlement selection screen request information from the settlement device 40 extracts the corresponding cart information. Specifically, the cloud server 20 extracts cart information in which the value of the processing progress information is "30 (inquiry code display instruction reception)".

Step S45: The settlement device 40, which has received screen information from the cloud server 20, displays a settlement screen (for example, a settlement selection screen that displays inquiry code candidates in a selectable manner as shown in FIG. 7D). Display on 405.

Examples 1 to 4 have been described above with reference to FIGS. 11 to 14, but in each of the sequence diagrams of FIGS. 11 to 14, the settlement device 40 has detected the reading operation by the customer. However, the flow when the two-dimensional code 605 for settlement is not recognized is explained. Even if the settlement device 40 detects the reading operation by the customer, for example, the display unit (display screen) of the mobile terminal 60 displaying the two-dimensional code 605 for settlement is dirty or cracked, or the sheet attached to the display unit. , The darkness of the display unit may affect the recognition of the two-dimensional code 605 for settlement, but each of the sequence diagrams of FIGS. 11 to 14 is for purchasing a product in such a situation described above. It explains the flow.

Due to problems on the mobile terminal 60 side (dirt and cracks on the display unit of the mobile terminal 60 described above) and problems on the payment device 40 side (for example, malfunction of the scanner unit 406), the payment device 40 is two-dimensional for payment. It is also possible that the code 605 cannot be recognized.

FIG. 15 is a sequence diagram illustrating a flow of product purchase by the sales system 1 (specifically, service A provided by the specific sales system).

The sequence diagram of FIG. 15A shows the respective examples (Example 1 shown in FIG. 11, Example 2 shown in FIG. 12, and FIG. 13) in the case where the settlement device 40 does not detect the reading operation by the customer. It shows a part of the flow of product purchase of Example 3 shown in FIG. 14 and Example 4) shown in FIG. Specifically, steps S22, S25, and S26 of the sequence diagram of FIG. 15A are parts that replace steps S21 and S24 of the sequence diagram of FIGS. 11 to 14.

Step S20 of FIG. 15A: The settlement device 40 senses the presence of a customer by a proximity sensor (presence sensor) as in step S20 of FIGS. 10 to 14.

Step S22: The settlement device 40 determines that the reading operation by the customer has not been detected. For example, if the settlement device 40 does not recognize what seems to be a two-dimensional code as an object within a predetermined time (for example, within a predetermined time after detecting the existence of the customer), the checkout device 40 does not detect the reading operation by the customer. Judge.

Step S25: The settlement device 40 notifies the customer that the clerk is calling (for example, the clerk is called by the monitoring device 50, the registered settlement device 30, a mobile terminal (not shown) used by the clerk, or the like. (Notification of the fact, etc.) is executed.

Step S26: The checkout device 40 accepts a predetermined operation of a clerk (for example, login, operation of a hidden button, etc.).

The following flow is the same as in each embodiment. That is, in the first embodiment (FIG. 11), the process proceeds to step S30 of FIG. 11 following step S26 of FIG. 15 (A). In the second embodiment (FIG. 12), the process proceeds to step S30 of FIG. 12 following step S26 of FIG. 15 (A). In the third embodiment (FIG. 13), the process proceeds to step S41 of FIG. 13 following step S26 of FIG. 15 (A). In the fourth embodiment (FIG. 14), the process proceeds to step S31 of FIG. 14 following step S26 of FIG. 15 (A).

Although Examples 1 to 4 have been described above, the contents described in each Example can be changed as appropriate. For example, the inquiry code is displayed on the selection button (reference numeral f) on the settlement selection screen of FIGS. 7 (C) and 7 (D), but the total amount (approximate total) is displayed in addition to the inquiry code. It may be done. For example, the settlement device 40 may display the settlement selection screen as shown in FIG. 7 (F) instead of the settlement selection screen as shown in FIG. 7 (C). Alternatively, the total amount (approximate total) of each may be displayed in association with each of the selection buttons (reference numeral f) for displaying the inquiry code. As a result, the inquiry code can be selected on the settlement selection screen while also checking the approximate total (see FIGS. 5A and 5C) displayed on the mobile terminal 60.

Further, in the above, when the settlement device 40 cannot recognize the two-dimensional code 605 for settlement, the inquiry code (serial number constituting a part of the cart identification information) is used as the information to be input or selected by the settlement device 40. Although the example to be used has been described, if the information to be input or selected in the settlement device 40 is information that can specify one cart information, other information (information different from the inquiry code) is added in place of or in addition to the inquiry code. May be used.

For example, customer identification information may be used, or information that is temporarily (when necessary) numbered may be used instead of existing information such as an inquiry code or customer identification information. In Example 2 (FIG. 12), a case where the information temporarily numbered is used will be described with reference to FIG. 15 (B).

The sequence diagram of FIG. 15B shows a part of the flow of product purchase of Example 2 (FIG. 12) when the settlement device 40 does not detect the reading operation by the customer. Specifically, steps S30A to S54A in the sequence diagram of FIG. 15B are parts that replace steps S30 to S54 in the sequence diagram of FIG.

Step S30A of FIG. 15B: The settlement device 40 that has detected the unrecognizable two-dimensional code 605 for settlement displays a settlement input screen (not shown) including a reference number input field.

(About reference number)
The reference number in FIG. 15B is a number that can identify the cart information. The reference number is numbered by the cloud server 20 that has received the reference number display instruction (described later), and is stored in association with the cart information. Although it has been explained that the serial number included in the cart identification information shown in FIG. 3C is, for example, a serial number for each store date, the reference number may also be a store-specific date serial number. The serial number included in the cart identification information is numbered each time the cart information is generated, whereas the reference number is numbered each time a reference number display instruction (described later) is received. Therefore, the number of reference numbers is smaller (that is, the number of digits to be input is likely to be smaller, so that it is easier to input correctly on the settlement input screen). The reference number may be information that constitutes a part of the cart information, like the serial number included in the cart identification information, and is associated with the cart information (for example, the cart identification information) separately from the cart information. It may be the information to be stored.

Step S32A: The mobile terminal 60 receives a reference number display instruction as a customer operation. For example, the mobile terminal 60 displays a button displayed as "display a reference number" on the two-dimensional code display screen, and the customer receives a reference number display instruction by the button.

Step S33A: The mobile terminal 60 that has received the reference number display instruction receives the reference number display instruction reception notification, and transmits the reference number display instruction reception notification to the cloud server 20 together with the cart identification information.

Step S34: The cloud server 20 that has received the cart identification information and the inquiry code display instruction reception notification from the mobile terminal 60 updates the cart information identified by the cart identification information.

Step S34A: The cloud server 20 assigns a reference number and stores the numbered reference number in association with the cart information.

Step S34B: The cloud server 20 transmits the reference number assigned in step S34A to the mobile terminal 60 together with the cart identification information.

Step S35A: The mobile terminal 60 that has received the cart identification information and the reference number from the cloud server 20 confirms whether the cart identification information and the reference number match the stored cart identification information, and then displays the reference number on the display unit.

Step S36A: The settlement device 40 accepts the input of the reference number via the settlement input screen. That is, the customer inputs the reference number displayed on the mobile terminal 60 in step S35A in the reference number input field on the settlement input screen of the settlement device 40.

Step S51A: The settlement device 40 that has received the input of the reference number requests the cloud server 20 for a settlement screen (for example, a payment type selection screen). For example, the settlement device 40 transmits the information requesting the settlement screen (settlement screen request information) together with the reference number to the cloud server 20 via the management device 10.

Step S53A: Whether or not the reference number acquired from the settlement device 40 is valid for the cloud server 20 that has received the reference number and the settlement screen request information from the settlement device 40 (that is, the input of the reference number by the customer is valid). Whether or not) is judged. Specifically, if the value of the processing progress information in the cart information corresponding to the reference number acquired from the settlement device 40 is "20 (accounting instruction reception)", the cloud server 20 arranges the arrangement acquired from the settlement device 40. It is judged that the number is valid, and if it is not "20 (accounting instruction reception)", it is judged that the reference number obtained from the settlement device 40 is not valid.

When the cloud server 20 determines that the reference number obtained from the settlement device 40 is not appropriate, the cloud server 20 sends a message to the effect that the reference number has entered an input error and that the reference number needs to be re-entered. It may be displayed on (payment input screen).

The following flow is the same as in FIG. The same applies to the case where the information (reference number, etc.) that is temporarily assigned is used in the fourth embodiment (FIG. 14).

In the above, the settlement device 40 detects the existence of the customer by the proximity sensor (presence sensor), but the existence of the customer may be detected by the operation of the customer. For example, when transitioning from the initial screen of FIG. 6 (D) to the registration screen (initial settlement screen) of FIG. 6 (A), the "payment start" button of the initial screen of FIG. 6 (D) is operated. Therefore, it may be determined that the customer exists. That is, the settlement device 40 does not have to include the proximity sensor.

Further, the settlement device 40 senses (detects) the existence of the customer prior to reading the two-dimensional code for settlement (step S20 in FIGS. 10 to 15 (A)), but does not detect the existence of the customer. You may. That is, the settlement device 40 does not need to be provided with a proximity sensor, and for example, as described above, it is not necessary to determine that a customer exists based on the transition of the screen. In other words, the settlement device 40 does not perform the process of detecting the existence of the customer prior to reading the settlement two-dimensional code, and simply fails to read the settlement two-dimensional code, the settlement input. A screen (or a selection screen for settlement) may be displayed.

Further, in the above, when the settlement device 40 cannot recognize the two-dimensional code 605 for settlement displayed on the mobile terminal 60, the inquiry code (or reference number) is input and selected on the screen of the settlement device 40. Although the example of completing the settlement process has been described above, the settlement process may be completed by another method.

(Displays a two-dimensional code on the payment device 40 side)
When the settlement device 40 cannot recognize the two-dimensional code 605 for settlement displayed on the mobile terminal 60, the mobile terminal recognizes the two-dimensional code in which the information that can identify the settlement device 40 is two-dimensionally coded. The settlement process may be completed by performing (reading). For example, the flow may be as follows (1) to (5). (1) When it is determined that the settlement device 40 has not recognized the two-dimensional code (the same applies when it is determined that the reading operation by the customer has not been detected), the information that can identify the settlement device 40 (the settlement device identification information). ) Is displayed as a two-dimensional code. (2) The mobile terminal 60 recognizes the two-dimensional code displayed by the settlement device 40. (3) The mobile terminal 60 acquires the settlement device identification information from the two-dimensional code and transmits it to the cloud server 20 together with the cart identification information. (4) The cloud server 20 that has received the cart identification information and the settlement device identification information from the mobile terminal 60 updates the cart information identified by the cart identification information. Specifically, the cloud server 20 calculates a subtotal amount (final subtotal amount reflecting various discounts and the like) and stores it as a subtotal amount (calculated subtotal amount). Further, the cloud server 20 updates the value of the processing progress information from "20 (accounting instruction reception)" to "40 (payment screen display)". (5) The cloud server 20 that has updated the cart information generates screen information (screen information of the payment type selection screen), and the generated screen information together with the cart identification information is passed through the management device 10 to the settlement device 40 ( It is transmitted to the settlement device 40) identified by the settlement device identification information.

In relation to the above (1), a two-dimensional code in which the settlement device identification information capable of identifying the settlement device 40 may be posted in the vicinity of the settlement device 40. In the mode of posting the two-dimensional code, the settlement device 40 reads the two-dimensional code posted in the vicinity instead of the two-dimensional code in which the settlement device identification information that can identify the settlement device 40 is two-dimensionally coded. A message to the effect may be displayed.

Further, in relation to the above (5), the cloud server 20 may transmit screen information or the like to the settlement device 40 based on the request from the settlement device 40. For example, when it is determined that the settlement device 40 has not recognized the two-dimensional code (the same applies when it is determined that the reading operation by the customer has not been detected), the information that can identify the settlement device 40 (settlement device identification information). Is displayed (or a message indicating that the 2D code posted in the vicinity should be read) is displayed, but after the display, at a predetermined interval (for example, every 3 to 10 seconds), Request the settlement screen from the cloud server 20. On the other hand, the cloud server 20 that has received the cart identification information and the settlement device identification information from the mobile terminal 60 is requested to settle the settlement screen by the settlement device 40 (the settlement device 40 identified by the settlement device identification information) after the screen information is generated. Based on the fact, or based on the fact that the screen information is generated after the settlement device 40 (the settlement device 40 identified by the settlement device identification information) requests the settlement screen, the screen information or the like is displayed on the settlement device 40. May be sent.

(Communication between mobile terminal 60 and checkout device 40)
When the settlement device 40 cannot recognize the two-dimensional code 605 for settlement displayed on the mobile terminal 60, the settlement process may be completed by communication between the mobile terminal 60 and the settlement device 40. For example, short-range wireless communication (Bluetooth (registered trademark), infrared communication, etc.) is enabled between the two, and information (inquiry) that can identify cart information from the mobile terminal 60 to the checkout device 40 by short-range wireless communication. A code (reference number) may be sent to complete the settlement process. The payment device 40 can recognize the non-contact IC chip built in the mobile terminal 60, and by recognizing the non-contact IC chip, the mobile terminal 60 can identify the cart information from the mobile terminal 60 to the payment device 40 (inquiry code, inquiry code, A reference number) may be sent to complete the settlement process.

As an example, short-range wireless communication (Bluetooth communication, etc.) is started by operating the mobile terminal 60 (for example, pressing the inquiry code button 608 (FIG. 5)), and communication between the mobile terminal 60 and the checkout device 40. May be established.

When the settlement device 40 cannot recognize the two-dimensional code 605 for settlement displayed on the mobile terminal 60, the clerk or the customer may be able to select how to deal with it. For example, when it is determined that the settlement device 40 has not recognized the two-dimensional code (the same applies when it is determined that the reading operation by the customer has not been detected), the selection screen is displayed, and the inquiry code (arrangement) is displayed on the selection screen. The clerk may be able to select the method of inputting the number) (that is, displaying the settlement input screen) and the method of selecting the inquiry code (reference number) (that is, displaying the settlement selection screen). Further, on the selection screen, it may be possible to select a method of inputting (selecting) an inquiry code (reference number) or a method of communication.

Further, in the above description, the settlement device 40 is basically a device that executes the settlement process by the operation of the customer, but the device that setstles the product registered by the mobile terminal 60 is in addition to the settlement process. The device may also be capable of performing registration processing. For example, a device for paying for products registered by the mobile terminal 60 is operated from both sides (for example, the clerk side and the customer side) of a device whose operation mode is switched according to a mode switching operation by a clerk or a mode switching instruction from another device. As the operation mode, for example, an operation mode in which the clerk executes the registration process and the customer executes the settlement process, an operation mode in which the customer executes both the registration process and the settlement process, and an operation mode in which the clerk executes the registration process. It may be (a mode in which the settlement processing function is turned off), an operation mode in which the customer executes the settlement processing (a mode in which the registration processing function is turned off), or the like).

Hereinafter, a summary of the embodiments will be described.
[Technical field]
The present invention relates to a settlement system.
[Background technology]
At a store, a sales system has been introduced in which a customer can operate a mobile terminal device to register a product by himself / herself (see, for example, Patent Document 1). In such a system, since the product is registered in advance, the settlement process is smoothly performed.
[Prior art literature]
[Patent Document 1] Japanese Patent No. 5056161 [Summary of Invention]
[Problems to be solved by the invention]
However, in the mode in which the customer himself / herself also performs the settlement process, it is necessary to appropriately realize the settlement process in consideration of various situations.
The present invention has been made in view of such circumstances, and an object of the present invention is to provide a technique for suitably realizing a settlement process.
[Means to solve problems]
(1) In order to solve the above-mentioned problems, the settlement system according to one aspect of the present invention uses a settlement device based on transaction information (for example, cart information) related to a product registered using a mobile terminal. A first specific means capable of specifying transaction information to be settled, a second specific means different from the first specific means capable of specifying transaction information to be settled, and the first specific means. It is characterized by including a specific means or a settlement means for settlement based on the transaction information specified by the second specific means.
According to the settlement system of the above (1), the settlement process can be preferably executed. That is, depending on the situation, it is possible to specify the transaction information by the first specific means and settle by the settlement means, or to specify the transaction information by the second specific means and settle by the settlement means. Depending on the situation, the settlement process can be preferably executed.
(2) In the settlement system of (1) above, the first specific means is displayed on the display unit of the mobile terminal as code information that can identify transaction information related to a product registered using one mobile terminal. By recognizing the code information (for example, two-dimensional code 605 for settlement), the transaction information related to the product registered using the mobile terminal can be specified as the transaction information to be settled (for example, the specific means (for example). In step S23 of FIG. 10 and the like), the second specific means accepts the input of information that can identify one transaction information, and the transaction information identified by the information for which the input is received is to be settled. According to the settlement system of (2) above, which is a specific means that can be specified as transaction information (for example, step S36 of FIG. 11, step S36 of FIG. 12, etc.), the settlement process is preferably executed. Can be done.
(3) The settlement system of the above (1) or (2) further includes a switching means for switching between the identification of the transaction information by the first specific means and the specification of the transaction information by the second specific means, and the switching. The means is characterized in that, when the transaction information cannot be specified by the first specific means, the specification of the transaction information by the first specific means is switched to the specification of the transaction information by the second specific means.
According to the settlement system of (3) above, the settlement process can be preferably executed. That is, when the transaction information cannot be specified by the first specific means, the transaction information is switched to the second specific means, so that the situation where the transaction information to be settled is not specified is reduced. It is possible to settle in a stable manner based on transaction information.
Further, in relation to the above (2) and (3), when the switching means cannot recognize the code information within a predetermined time (for example, step S24 in FIG. 11, step S24 in FIG. 12, and FIG. 15). (A), step S22, etc.), the specification of the transaction information by the first specific means may be switched to the specification of the transaction information by the second specific means. Thereby, for example, when the code information (for example, the two-dimensional code 605 for settlement) cannot be read, the settlement can be performed without delay (smoothly).
(4) The settlement system of (2) above further includes a management means for managing the progress of individual transactions and an error notification means for notifying an input error, and the error notification means is provided by the second specific means. It is determined that the transaction information identified by the input-accepted information is not the transaction information to be settled based on the progress status (reference: step S53 in FIG. 11, step S54 in FIG. 12, step S54A in FIG. 15 (B)). Etc.), it is characterized by notifying an error.
According to the settlement system of (4) above, the settlement process can be preferably executed. For example, since an inappropriate input causes an error, it is possible to prevent a situation in which improper processing is performed due to an input error or the like.
(5) In the settlement system of (3) above, the first specific means is displayed on the display unit of the mobile terminal as code information that can identify transaction information related to a product registered using one mobile terminal. By recognizing the code information, the transaction information related to the product registered using the mobile terminal can be specified as the transaction information to be settled, and the second specific means is one transaction information. Is a specific means that can selectably display identifiable information, and the transaction information identified by the selected information can be specified as the transaction information to be settled, and the switching means is the code information within a predetermined time. When the above is not recognized, the transaction information is switched from the specification of the transaction information by the first specific means to the specification of the transaction information by the second specific means.
According to the settlement system of (5) above, the settlement process can be preferably executed. For example, even if the code information (for example, the two-dimensional code 605 for settlement) cannot be read, the settlement can be performed without delay (smoothly).
(6) The settlement system of the above (5) further includes a management means for managing the progress of each transaction, and the second specific means is transaction information (processing progress information) to be settled based on the progress. = 20, 30 cart information) is displayed in a selectable manner.
According to the settlement system of (6) above, the settlement process can be preferably executed. For example, since only suitable candidates are displayed in a selectable manner, they can be efficiently selected.

The program for realizing the sales system 1, the management device 10, the cloud server 20, the registered settlement device 30, the settlement device 40, the mobile terminal 60, etc. described above is recorded on a computer-readable recording medium, and the program thereof is recorded. The program may be loaded into a computer system and executed. The term "computer system" as used herein includes hardware such as an OS and peripheral devices. Further, the "computer-readable recording medium" refers to a portable medium such as a flexible disk, a magneto-optical disk, a ROM, or a CD-ROM, or a storage device such as a hard disk built in a computer system. Furthermore, a "computer-readable recording medium" is a volatile memory (RAM) inside a computer system that serves as a server or client when a program is transmitted via a network such as the Internet or a communication line such as a telephone line. In addition, it shall include those that hold the program for a certain period of time. Further, the program may be transmitted from a computer system in which this program is stored in a storage device or the like to another computer system via a transmission medium or by a transmission wave in the transmission medium. Here, the "transmission medium" for transmitting a program refers to a medium having a function of transmitting information, such as a network (communication network) such as the Internet or a communication line (communication line) such as a telephone line. Further, the above program may be for realizing a part of the above-mentioned functions. Further, it may be a so-called difference file (difference program) that can realize the above-mentioned function in combination with a program already recorded in the computer system.

1 ... Sales system (including specific sales system)
10 ... Management device (store controller, etc.)
20 ... Cloud server 30 ... Registered settlement device 40 ... Settlement device 60 ... Mobile terminal 401 ... CPU
402 ... ROM
403 ... RAM
404 ... Hard disk 405 ... Display unit 406 ... Scanner unit 408 ... Card payment unit 409 ... Change machine 413 ... Printing unit 414 ... Audio output unit 415 ... Communication unit

Claims (6)

It is a settlement system that uses a settlement device to settle based on transaction information about products registered using a mobile terminal.
The first specific means that can specify the transaction information to be settled,
A second specific means different from the first specific means that can specify the transaction information to be settled, and
A settlement system including the first specific means or a settlement means for settlement based on transaction information specified by the second specific means. The first specific means is
By recognizing the code information displayed on the display of the mobile terminal as code information that can identify the transaction information related to the product registered using one mobile terminal, the product was registered using the mobile terminal. It is a specific means that can identify transaction information related to products as transaction information to be settled.
The second specific means is
A claim characterized in that, by accepting input of information that can identify one transaction information, the transaction information identified by the input-accepted information is a specific means that can be specified as transaction information to be settled. The settlement system according to 1. Further provided with a switching means for switching between the identification of the transaction information by the first specific means and the specification of the transaction information by the second specific means.
The switching means is
Claim 1 or claim 2 characterized in that when the transaction information cannot be specified by the first specific means, the transaction information is specified by the first specific means and the transaction information is specified by the second specific means. Settlement system described in. Management measures to manage the progress of individual transactions,
Further equipped with an error notification means for notifying an input error,
The error notification means is
The second aspect of claim 2, wherein an error is notified when it is determined that the transaction information identified by the information received by the second specific means is not the transaction information to be settled based on the progress. Settlement system. The first specific means is
By recognizing the code information displayed on the display of the mobile terminal as code information that can identify the transaction information related to the product registered using one mobile terminal, the product was registered using the mobile terminal. It is a specific means that can identify transaction information related to products as transaction information to be settled.
The second specific means is
It is a specific means that displays one transaction information in a selectable manner and can identify the transaction information identified by the selected information as the transaction information to be settled.
The switching means is
The settlement according to claim 3, wherein when the code information cannot be recognized within a predetermined time, the identification of the transaction information by the first specific means is switched to the specification of the transaction information by the second specific means. system. With additional controls to manage the progress of individual transactions
The second specific means is
The settlement system according to claim 5, wherein transaction information to be settled is selectively displayed based on the progress.

Images