JP7528186B2 - Payment device and program - Google Patents

Description

Embodiments of the present invention relate to a checkout system, a registration device, a payment device, and a program.

Some checkout systems issue documents such as receipts or invoices. These documents may or may not be required depending on the shopper. For this reason, some checkout systems are provided with a receipt issue button and a receipt issue button. Both the receipt button and the receipt button also serve as buttons to be pressed when instructing the completion of payment, and the operator must press either button when instructing the completion of payment. When the receipt issue button is selected, the checkout system issues a receipt but does not issue a receipt, and when the receipt issue button is selected, the checkout system issues a receipt but does not issue a receipt. However, when there are multiple buttons to instruct the completion of payment like this, an operator who is unfamiliar with the operation may be confused about which button to press. In particular, an operator who needs a receipt is less likely to be confused because there is a clear motivation for pressing the receipt button, but an operator who does not need a receipt is not aware of the motivation for pressing either button and is more likely to be confused.

JP 2016-058109 A

The problem that the embodiments of the present invention aim to solve is to provide a checkout system, a registration device, a payment device, and a program that prevent an operator from becoming confused about how to operate the system.

A payment device according to an embodiment includes a first display control means, a second display control means, and a payment means. The first display control means causes the display unit to display an object for instructing that a receipt will not be issued before the payment for the transaction is completed. The second display control means causes the display unit to display a first button indicating that a receipt will not be issued if the object is operated before the payment amount for the transaction is input. The second display control means causes the display unit to display a second button different from the first button if the payment amount is input without operating the object. The payment means executes the payment when the first button or the second button is operated.

FIG. 2 is a block diagram showing the main circuit configuration of each of devices included in the checkout system according to the first and second embodiments. 5 is a flowchart of a control process in the first and second embodiments by a CPU of the registration device in FIG. 1 . 5 is a flowchart of a control process in the first and second embodiments by a CPU of the settlement device in FIG. 1 . 5 is a flowchart of a control process in the first and second embodiments by a CPU of the settlement device in FIG. 1 . 4 is a diagram showing an example of a screen displayed on a store clerk-side touch panel of the registration device in FIG. 1 . 2 is a diagram showing an example of a screen displayed on a customer-side touch panel of the registration device in FIG. 1 . 4 is a diagram showing an example of a screen displayed on a store clerk-side touch panel of the registration device in FIG. 1 . 2 is a diagram showing an example of a screen displayed on a touch panel of the settlement device in FIG. 1 . 2 is a diagram showing an example of a screen displayed on a touch panel of the settlement device in FIG. 1 . 2 is a diagram showing an example of a screen displayed on a touch panel of the settlement device in FIG. 1 . 2 is a diagram showing an example of a screen displayed on a touch panel of the settlement device in FIG. 1 . 2 is a diagram showing an example of a screen displayed on a touch panel of the settlement device in FIG. 1 . 2 is a diagram showing an example of a screen displayed on a touch panel of the settlement device in FIG. 1 .

Hereinafter, checkout systems according to some embodiments will be described with reference to the drawings.
First Embodiment
FIG. 1 is a block diagram showing the main circuit configuration of each of the devices included in the checkout system 1 according to the first embodiment. The checkout system 1 is installed in a store such as a supermarket for operations such as registering purchases of products to be paid for and making payments. The checkout system 1 includes a registration device 10 and a payment device 20. The checkout system 1 is a semi-self-service checkout system in which a store clerk mainly operates the registration device 10 for registering products for a transaction, and a payment person such as a shopper operates the payment device 20 for paying for the registered products. The registration device 10 and the payment device 20 are connected to a network NW. The network NW is typically a local area network (LAN). The network NW may be a wireless line or a wired line. In addition, the wireless line and the wired line may be mixed. Note that FIG. 1 shows one registration device 10 and two payment devices 20. However, the number of the registration devices 10 and the payment devices 20 is not limited to these, and any number of the registration devices 10 and the payment devices 20 may be installed in the store. Also, in FIG. 1, only the main circuit configuration of one payment device 20 is shown, and the main circuit configurations of the other payment devices 20 are omitted.

The registration device 10 includes a CPU (central processing unit) 11, a main memory 12, an auxiliary storage device 13, a communication interface 14, a store clerk touch panel 15, a customer touch panel 16, a scanner 17, and a bus 18.

The CPU 11 corresponds to the central part of the computer that performs the processing and control required for the operation of the registration device 10. The CPU 11 controls each part to realize the various functions of the registration device 10 based on programs such as the operating system and application software stored in the main memory 12.

The main memory 12 corresponds to the main storage portion of the computer. The main memory 12 stores programs such as the operating system and application software. The main memory 12 also stores data referenced by the CPU 11 when performing various processes. Furthermore, the main memory 12 is used as a so-called work area for storing data that is temporarily used when the CPU 11 performs various processes.

The auxiliary storage device 13 corresponds to the auxiliary storage portion of the computer. The auxiliary storage device 13 is, for example, an EEPROM (electrical erasable programmable read-only memory), a HDD (hard disk drive), or an SSD (solid state drive). The auxiliary storage device 13 stores data used by the CPU 11 in performing various processes or data generated by the processes in the CPU 11. The auxiliary storage device 13 may also store programs such as the operating system or applications described above. The auxiliary storage device 13 also stores a product list, which is a list of products registered as purchased products. Alternatively, the main memory 12 may store the product list. Furthermore, the auxiliary storage device 13 also stores a product database that includes various information such as product codes, product names, and prices for products sold in the store.

The programs stored in the main memory 12 or the auxiliary storage device 13 include a control program described in relation to the control process described below. As an example, the registration device 10 is transferred to an administrator of the registration device 10 with the control program stored in the main memory 12 or the auxiliary storage device 13. However, the registration device 10 may be transferred to an administrator without the control program being stored in the main memory 12 or the auxiliary storage device 13. The control program transferred to the administrator may be written to the main memory 12 or the auxiliary storage device 13 by an administrator or a serviceman. The transfer of the control program in this case may be realized by recording it on a removable recording medium such as a magnetic disk, a magneto-optical disk, an optical disk, or a semiconductor memory, or by downloading it via a network.

The communication interface 14 is an interface that allows the registration device 10 to communicate over a network.

The store clerk touch panel 15 functions as a display device that displays a screen for notifying the store clerk, who is the operator of the registration device 10, of various information. The store clerk touch panel 15 also functions as an input device that accepts touch operations by the operator.

The customer-side touch panel 16 functions as a display device that displays a screen to inform the shopper of various information. The customer-side touch panel 16 also functions as an input device that accepts touch operations by the shopper. As mentioned above, the operator of the registration device 10 is usually a store clerk, but the customer-side touch panel 16 is operated by the shopper.

Scanner 17 reads barcodes displayed on products and outputs the product code represented by the barcode. Scanner 17 may be a type that is held in the hand or a type that is fixed to a cash register or the like.

The bus 18 includes an address bus and a data bus, and transmits signals exchanged between each part of the registration device 10.

The payment device 20 includes a CPU 21, a main memory 22, an auxiliary memory device 23, a communication interface 24, a touch panel 25, a printer 26, and a bus 27.

The CPU 21 corresponds to the central part of the computer that performs the processing and control necessary for the operation of the payment device 20. The CPU 21 controls each part to realize the various functions of the payment device 20 based on programs such as the operating system and application software stored in the main memory 22.

The main memory 22 corresponds to the main storage portion of the computer. The main memory 22 stores programs such as the operating system and application software. The main memory 22 also stores data referenced by the CPU 21 when performing various processes. Furthermore, the main memory 22 is used as a so-called work area for storing data that is temporarily used when the CPU 21 performs various processes.

The auxiliary storage device 23 corresponds to the auxiliary storage portion of the computer. The auxiliary storage device 23 is, for example, an EEPROM, a HDD, or an SSD. The auxiliary storage device 23 stores data used by the CPU 21 when performing various processes, or data generated by the processes in the CPU 21. The auxiliary storage device 23 may also store programs such as the operating system or applications described above.

The programs stored in the main memory 22 or the auxiliary storage device 23 include a control program described in relation to the control process described below. As an example, the payment device 20 is transferred to an administrator of the payment device 20 with the control program stored in the main memory 22 or the auxiliary storage device 23. However, the payment device 20 may be transferred to an administrator without the control program being stored in the main memory 22 or the auxiliary storage device 23. The control program transferred separately to the administrator may be written to the main memory 22 or the auxiliary storage device 23 under the operation of the administrator or a serviceman. The transfer of the control program in this case may be realized by recording it on a removable recording medium such as a magnetic disk, a magneto-optical disk, an optical disk, or a semiconductor memory, or by downloading it via a network.

The communication interface 24 is an interface that allows the payment device 20 to communicate over a network.

The touch panel 25 functions as a display device that displays a screen for notifying the operator of the payment device 20 of various information. The touch panel 25 also functions as an input device that accepts touch operations by the operator.

The printer 26 prints receipts and the like. The printer 26 can use various types of printers, such as a dot matrix printer, inkjet printer, thermal printer, laser printer, or other printers.

Bus 27 includes an address bus and a data bus, and transmits signals exchanged between each part of payment device 20.

The operation of the checkout system 1 according to the first embodiment will be described below with reference to Figures 2 to 4. Note that the contents of the process described below are merely examples, and various processes capable of achieving similar results can be used as appropriate.
In the first embodiment, the main memory 12 or the auxiliary storage device 13 of the registration device 10 stores a control program describing the control process shown in Fig. 2. The main memory 22 or the auxiliary storage device 23 of the payment device 20 stores a control program describing the control process shown in Figs. 3 and 4.
2 is a flowchart of a control process by the CPU 11 of the registration device 10. The CPU 11 executes this control process based on a control program stored in the main memory 12 or the auxiliary storage device 13. When the CPU 11 starts the control process shown in FIG. 2, it assigns a variable F1 to the main memory 12. The variable F1 is used as a flag. When the value of the variable F1 is 0, the flag represented by the variable F1 is considered to be down, and when the value of the variable F1 is 1, the flag represented by the variable F1 is considered to be up.
3 and 4 are flowcharts of the control process by the CPU 21 of the payment device 20. The CPU 21 executes this control process based on a control program stored in the main memory 22 or the auxiliary storage device 23. When the CPU 21 starts the control process shown in Figs. 3 and 4, it allocates a variable F2 to the main memory 22. The variable F2 is used as a flag. When the value of the variable F2 is 0, the flag represented by the variable F2 is considered to be down, and when the value of the variable F2 is 1, the flag represented by the variable F2 is considered to be up.

In Act 1 of FIG. 2, the CPU 11 of the registration device 10 resets the product list stored in the main memory 12 or the auxiliary storage device 13. That is, the CPU 11 instructs the main memory 12 or the auxiliary storage device 13 to put the product list in a state in which no products are stored.

In Act 2, the CPU 11 sets the value of variable F1 to 0 so that the flag represented by variable F1 is not set.

In Act 3, the CPU 11 generates an image corresponding to the registration screen SC1 as shown in FIG. 5. Then, the CPU 11 instructs the store clerk's touch panel 15 to display the generated image. In response to this instruction, the store clerk's touch panel 15 displays the registration screen SC1.

Figure 5 is a diagram showing an example of the registration screen SC1. The registration screen SC1 displays the product name, unit price, number of items, amount, and total amount for each product registered in the product list. The registration screen SC1 also includes a receipt button B11 and a subtotal button B12. The receipt button B11 is operated by the operator of the registration device 10 at the request of the shopper when a receipt is to be issued. The receipt button B11 displays a character string such as "Receipt required" that indicates that this is the button to be pressed when a receipt is required. The receipt button B11 is an example of an object operated by the operator to instruct the issuance of a receipt. The subtotal button B12 is operated by the operator of the registration device 10 when the registration of the product is completed.

In Act 4, the CPU 11 generates an image corresponding to the customer screen SC2 as shown in FIG. 6. Then, the CPU 11 instructs the customer touch panel 16 to display the generated image. In response to this instruction, the customer touch panel 16 displays the customer screen SC2.

Figure 6 is a diagram showing an example of the customer screen SC2. The customer screen SC2 displays the product name, quantity, and price of each product registered in the product list. The customer screen SC2 also includes a receipt button B21. The receipt button B21 is operated when a shopper wants a receipt to be issued. The receipt button B21 displays a character string such as "Touch if you need a receipt" or "Receipt required" to indicate that it is a button to press when a receipt is required. The receipt button B21 is an example of an object that the operator operates to instruct the issuance of a receipt.

In Act 5, the CPU 11 checks whether the product code has been read. That is, the CPU 11 waits for the product code to be input. The product code is input to the CPU 11 as shown below. The operator of the registration device 10 causes the scanner 17 to read the barcode attached to the product. As a result, the product code recorded in the barcode is input to the CPU 11. In addition, buttons associated with products without barcodes are displayed on the store clerk's touch panel 15. The operator of the registration device 10 touches one of the buttons displayed on the store clerk's touch panel 15, which is a product that the operator wishes to register in the product list. As a result, the product code of the product associated with the button is input to the CPU 11. If the product code is not input, the CPU 11 judges No in Act 5 and proceeds to Act 6.

In Act 6, the CPU 11 checks whether an operation has been performed to instruct the issuance of a receipt. That is, the CPU 11 checks whether a predetermined operation has been performed, such as touching the receipt button B11 displayed on the registration screen SC1 or the receipt button B21 displayed on the customer screen SC2. Therefore, by processing Act 6, the computer with the CPU 11 at its core functions as an input means for inputting an instruction to issue a receipt based on an operation on an object. If no operation has been performed to instruct the issuance of a receipt, the CPU 11 judges No in Act 6 and proceeds to Act 7.

In Act 7, the CPU 11 checks whether an operation to complete the registration of the product has been performed. That is, the CPU 11 checks whether a predetermined operation, such as touching the subtotal button B12 displayed on the registration screen SC1, has been performed. Note that an operation to instruct the completion of registration must be performed after at least one product has been registered as an operational rule. The operation of the CPU 11 when an operation to instruct the completion of registration is performed when no product has been registered may be determined by the designer of the control program of the CPU 11. For example, the CPU 11 ignores the operation to instruct the completion of registration. Alternatively, the CPU 11 may not allow the operation to instruct the completion of registration when no product has been registered. If the operation to instruct the completion of registration is not performed, the CPU 11 judges No in Act 7 and returns to Act 5. Thus, the CPU 11 repeats Acts 5 to 7 until a product code is input, an operation to instruct the issuance of a receipt is performed, or an operation to instruct the completion of registration is performed.

The store clerk reads the barcode attached to the product to be paid for using the scanner 17. Alternatively, the store clerk touches one of the buttons displayed on the store clerk's touch panel 15 that indicates the product to be paid for.
If a product code is input during the standby state of Act 5 to Act 7, the CPU 11 determines Yes in Act 5 and proceeds to Act 8.
In Act 8, the CPU 11 adds the product code confirmed to have been read in Act 5 to the product list stored in the main memory 12 or the auxiliary storage device 13. After processing Act 8, the CPU 11 returns to Act 5.

If a customer wants a receipt, the customer tells the store clerk that they would like a receipt. The store clerk, upon receiving the customer's request, touches the receipt button B11 displayed on the registration screen SC1. Alternatively, if a customer wants a receipt, the customer touches the receipt button B21 displayed on the customer side screen SC2.
If an operation to instruct issuance of a receipt is performed while the CPU 11 is in the standby state of Act 5 to Act 7, the CPU 11 judges that the answer is Yes in Act 6 and proceeds to Act 9.
In Act 9, the CPU 11 substitutes a value calculated by the formula (1-F1) into the variable F1 in order to set the flag represented by the variable F1 if the flag is set, and to set the flag if the flag is set. Note that if the flag represented by the variable F1 is set, it indicates that a receipt will be issued.

In Act 10, the CPU 11 changes the appearance of the receipt button B11 and the receipt button B21. That is, when the value of the variable F1 is 1, the CPU 11 changes the appearance of the receipt button B11 and the receipt button B21 so that it is clear that the receipt button B11 or the receipt button B21 has been operated or that a receipt will be issued. When the value of the variable F1 is 0, the CPU 11 returns the appearance of the receipt button B11 and the receipt button B21 to the appearance shown in Fig. 5 or Fig. 6. Note that the state of the receipt button displayed on the clerk-side touch panel 15 or the customer-side touch panel 16 when the value of the variable F1 is 1 is referred to as a selected state, and the state of the receipt button when the value of the variable F1 is 0 is referred to as a non-selected state. In order to change the appearance of the receipt button B11, the CPU 11 generates an image corresponding to a registration screen including the receipt button B11 in a selected or unselected state, and instructs the store clerk touch panel 15 to display this image. In response to this instruction, the store clerk touch panel 15 displays the registration screen. Furthermore, in order to change the appearance of the receipt button B21, the CPU 11 generates an image corresponding to a customer screen including the receipt button B21 in a selected or unselected state, and instructs the customer touch panel 16 to display this image. In response to this instruction, the customer touch panel 16 displays the customer screen.
As described above, the receipt button B11 and the receipt button B21 alternate between the two states, the selected state and the non-selected state, every time they are operated.
After processing Act 10, the CPU 11 returns to Act 5.

When the store clerk has completed the registration of the products to be paid for in one transaction, he or she performs an operation to indicate completion of the product registration.
If an operation to instruct completion of registration is performed while the CPU 11 is in the standby state of Act 5 to Act 7, the CPU 11 judges Yes in Act 7 and proceeds to Act 11.
In Act 11, the CPU 11 generates payment information. The payment information includes information necessary for the payment device 20 to make a payment for the products registered in the product list.

In Act 12, the CPU 11 generates an image corresponding to the subdivision screen SC3 as shown in FIG. 7. Then, the CPU 11 instructs the store clerk touch panel 15 to display the generated image. In response to this instruction, the store clerk touch panel 15 displays the subdivision screen SC3. Meanwhile, the customer touch panel 16 continues to display the customer screen SC2.

7 is a diagram showing an example of the small-scale plan screen SC3. The small-scale plan screen SC3 displays the total price of the products registered in the product list. The small-scale plan screen SC3 also includes a receipt button B31 and a transfer button B32. The receipt button B31, like the receipt button B11 in FIG. 5, is operated by the operator of the registration device 10 in response to a request from the shopper when issuing a receipt. Like the receipt button B11 in FIG. 5, the receipt button B31 displays a character string such as "receipt required" that indicates that it is a button to be pressed when a receipt is required. The receipt button B31 is an example of an object operated by the operator to instruct the issuance of a receipt. Note that the small-scale plan screen SC3 shown in FIG. 7 shows a state when the value of the variable F1 is 0, and the receipt button B31 shown in FIG. 7 is in a non-selected state. When the value of the variable F1 is 1, the receipt button B31 is displayed in a selected state. The transfer button B32 is operated by the operator when sending payment information to the payment device 20. Note that the payment machine in FIG. 7 refers to the payment device 20.

In Act 13, the CPU 11 checks whether an operation has been performed to instruct the issuance of a receipt. That is, the CPU 11 checks whether a predetermined operation has been performed, such as touching the receipt button B31 displayed on the sub-screen SC3. Therefore, by performing the processing of Act 13, the computer with the CPU 11 at its core functions as an input means for inputting an instruction to issue a receipt based on an operation on an object. If an operation to instruct the issuance of a receipt has not been performed, the CPU 11 judges No in Act 13 and proceeds to Act 14.

In Act 14, the CPU 11 checks whether an operation has been performed to instruct the sending of payment information to the payment device 20. That is, the CPU 11 checks whether a predetermined operation has been performed, such as touching the transfer button B32 displayed on the sub-screen SC3. If an operation to instruct the sending of payment information has not been performed, the CPU 11 judges No in Act 14 and returns to Act 13. Thus, the CPU 11 repeats Act 13 and Act 14 until the receipt button is operated or an operation to instruct the sending of payment information is performed. If the receipt button is operated while the CPU 11 is in the standby state of Act 13 and Act 14, the CPU 11 judges Yes in Act 13 and proceeds to Act 15.

In Act 15, the CPU 11 assigns the value calculated by the formula (1-F1) to the variable F1 in the same manner as in Act 9.
In Act 16, the CPU 11 changes the appearance of the receipt button in the same manner as in Act 10. However, the receipt buttons whose appearances are changed by the CPU 11 here are the receipt button B21 and the receipt button B31. After the processing of Act 16, the CPU 11 returns to Act 13.

After performing an operation to instruct the completion of the registration of the product, the store clerk operates the transfer button B32 to transmit the payment information to the payment device 20.
If an operation instructing the transmission of payment information is performed while in the standby state of Act 13 and Act 14, the CPU 11 judges that the answer is Yes in Act 14 and proceeds to Act 17.
In Act 17, the CPU 11 instructs the communication interface 14 to transmit the payment information and the value of the variable F1 generated in Act 11 to the payment device 20. In response to this instruction, the communication interface 14 transmits the payment information and the value of the variable F1 to the payment device 20. At this time, when a plurality of payment devices 20 are installed in the store, the CPU 11 designates, for example, a predetermined payment device 20 among the plurality of payment devices 20 as the transmission destination of the payment information and the value of the variable F1. The transmitted payment information and the value of the variable F1 are received by the communication interface 24 of the payment device 20.

3, the CPU 21 of the payment device 20 waits for the communication interface 24 to receive the payment information and the value of the variable F1. If the CPU 21 receives the payment information and the value of the variable F1, it determines Yes in Act 21 and proceeds to Act 22. The value of the variable F1 is 0 or 1 based on the operation on the receipt button displayed on the registration device 10. If the value of the variable F1 is 1, it indicates that a receipt should be issued. Therefore, by performing the processing of Act 21, the computer centered around the CPU 21 functions as an input unit that inputs an instruction to issue a receipt based on an operation on an object.
In Act 22, the CPU 21 assigns the value of the variable F1, the reception of which was confirmed in Act 21, to a variable F2.

In Act 23, the CPU 21 checks whether the value of the variable F2 is 0. If the value of the variable F2 is 0, the CPU 21 judges Act 23 as Yes and proceeds to Act 24.

In Act 24, the CPU 21 generates an image corresponding to the first checkout screen SC4 as shown in FIG. 8. The CPU 21 then instructs the touch panel 25 to display the generated image. In response to this instruction, the touch panel 25 displays the first checkout screen SC4.

8 is a diagram showing an example of the first checkout screen SC4. The first checkout screen SC4 includes a receipt button B41 and multiple selection buttons B42. The receipt button B41 is operated when the shopper instructs the payment device 20 to issue a receipt. The receipt button B41 displays a character string such as "Receipt required" or "Touch if receipt required" that indicates that it is a button to be pressed when a receipt is required. The receipt button B41 is an example of an object that the operator operates to instruct the issuance of a receipt. Each of the multiple selection buttons B42 corresponds to a payment method such as "cash", "point payment", "credit", or "prepaid card". Each of the multiple selection buttons B42 is operated when the shopper selects a corresponding payment method. Note that the number of selection buttons B42 in FIG. 8 is four, but the number of selection buttons B42 is not limited to four and may be the same as the number of selectable payment methods.

On the other hand, if the value of the variable F2 is 1, the CPU 21 determines No in Act 23 and proceeds to Act 25.
In Act 25, the CPU 21 generates an image corresponding to the second accounting screen SC4-2 as shown in Fig. 9. Then, the CPU 21 instructs the touch panel 25 to display the generated image. In response to this instruction, the touch panel 25 displays the second accounting screen SC4-2.

Figure 9 is a diagram showing an example of the second checkout screen SC4-2. Note that in Figure 9, elements similar to those in Figure 8 are given the same reference numerals as in Figure 8. The second checkout screen SC4-2 includes a receipt button B41-2 instead of the receipt button B41 on the first checkout screen SC4. The receipt button B41-2 is operated when a shopper wants to instruct the payment device 20 to cancel the issuance of a receipt. The receipt button B41-2 displays a character string such as "A receipt will be issued" or "No receipt required" to indicate that a receipt will be issued or that it is a button to be pressed when a receipt is not required.

In Act 26, the CPU 21 checks whether an operation has been performed to instruct the issuance of a receipt or to cancel the issuance of a receipt. That is, the CPU 21 checks whether a predetermined operation has been performed, such as touching the receipt button B41 displayed on the first accounting screen SC4 or the receipt button B41-2 displayed on the second accounting screen SC4-2. As described above, the receipt button B41 displayed on the first accounting screen SC4 is an object. Therefore, by performing the processing of Act 26, the computer centered around the CPU 21 functions as an input means for inputting an instruction to issue a receipt based on an operation on the object. If an operation to issue a receipt has not been performed, the CPU 21 judges No in Act 26 and proceeds to Act 27.

In Act 27, the CPU 21 checks whether an operation to select a payment method has been performed. That is, the CPU 21 checks whether a predetermined operation has been performed, such as touching any of the multiple selection buttons B42 displayed on the first billing screen SC4 or the second billing screen SC4-2. If an operation to select a payment method has not been performed, the CPU 21 judges No in Act 27 and returns to Act 26. Thus, the CPU 21 repeats Acts 26 and 27 until an operation to issue a receipt or to stop issuing a receipt is performed, or an operation to select a payment method is performed. If an operation to issue a receipt or to stop issuing a receipt is performed while the CPU 21 is in the standby state for Acts 27 and 28, the CPU 21 judges Yes in Act 26 and proceeds to Act 28.

In Act 28, the CPU 21 assigns a value calculated by the formula (1-F2) to the variable F2.
In Act 29, the CPU 21 changes the appearance of the receipt button B41 or the receipt button B41-2. That is, when the value of the variable F2 is 1, the CPU 21 changes the screen displayed on the touch panel 25 from the first accounting screen SC4 shown in FIG. 8 to the second accounting screen SC4-2 shown in FIG. 9 so that it is clear that the receipt button B41 has been operated. To this end, the CPU 21 generates an image corresponding to the second accounting screen SC4-2. Then, the CPU 21 instructs the touch panel 25 to display this generated image. In response to this instruction, the touch panel 25 displays the second accounting screen SC4-2. Then, when the value of the variable F2 is 0, the CPU 11 changes the screen displayed on the touch panel 25 from the second accounting screen SC4-2 to the first accounting screen SC4 so that it is clear that the receipt button B41-2 has been operated. To this end, the CPU 21 generates an image corresponding to the first accounting screen SC4. The CPU 21 then instructs the touch panel 25 to display the generated image. In response to this instruction, the touch panel 25 displays the first checkout screen SC4.
After processing Act 29, the CPU 21 returns to Act 26.

The shopper touches the selection button B42 corresponding to the payment method he or she desires.
If an operation to select a payment method is performed while the CPU 21 is in the standby state for Act 26 and Act 27, the CPU 21 determines that the answer is Yes in Act 27 and proceeds to Act 30. Note that the following description will be given assuming that the selection button B42 corresponding to “Cash” has been operated.

In Act 30, the CPU 21 checks whether the value of the variable F2 is 0. If the value of the variable F2 is 0, the CPU 21 judges Act 30 as Yes and proceeds to Act 31.

In Act 31, the CPU 21 generates an image corresponding to the first payment screen SC5 as shown in FIG. 10. Then, the CPU 21 instructs the touch panel 25 to display the generated image. In response to this instruction, the touch panel 25 displays the first payment screen SC5.

FIG. 10 is a diagram showing an example of the first payment screen SC5. The first payment screen SC5 is a screen on which the payment device 20 requests the shopper to pay the price. The first payment screen SC5 includes a receipt button B51. The receipt button B51, like the receipt button B41 in FIG. 8, is operated when the shopper instructs the payment device 20 to issue a receipt. The receipt button B51, like the receipt button B41 in FIG. 8, displays a character string such as "Receipt required" or "Touch if receipt required" to indicate that it is a button to be pressed when a receipt is required. The position where the receipt button B51 is displayed on the touch panel 25 is the same as the position where the receipt button B41 shown in FIG. 8 is displayed on the touch panel 25. The receipt button B51 is an example of an object that the operator operates to instruct the payment device 20 to issue a receipt. The first payment screen SC5 shown in FIG. 10 is an example of the case where "cash" is selected in Act 27. If a payment method other than cash is selected in Act 27, a payment screen corresponding to the selected payment method is displayed on the touch panel 25. Even in this case, a receipt button similar to the receipt button B51 is displayed on the payment screen.

On the other hand, if the value of the variable F2 is 1, the CPU 21 determines No in Act 30 and proceeds to Act 32.
In Act 32, the CPU 21 generates an image corresponding to the second payment screen SC5-2 as shown in Fig. 11. Then, the CPU 21 instructs the touch panel 25 to display the generated image. In response to this instruction, the touch panel 25 displays the second payment screen SC5-2.

Figure 11 is a diagram showing an example of the second payment screen SC5-2. Note that in Figure 11, elements similar to those in Figure 10 are given the same reference numerals as in Figure 10. The second payment screen SC5-2 includes a receipt button B51-2 instead of the receipt button B51 of the first payment screen SC5. Like the receipt button B41-2 in Figure 9, the receipt button B51-2 is operated when the shopper instructs the payment device 20 to cancel the issuance of a receipt. Like the receipt button B41-2 in Figure 9, the receipt button B51-2 displays a character string such as "A receipt will be issued" or "No receipt required" to indicate that a receipt will be issued or that it is a button to be pressed when a receipt is not required.

In Act 33, the CPU 21 checks whether an operation has been performed to instruct the issuance of a receipt or to cancel the issuance of a receipt. That is, the CPU 21 checks whether a predetermined operation has been performed, such as touching the receipt button B51 displayed on the first payment screen SC5 or the receipt button B51-2 displayed on the second payment screen SC5-2. As described above, the receipt button B51 displayed on the first payment screen SC5 is an object. Therefore, by performing the process of Act 33, the computer centered around the CPU 21 functions as an input means for inputting an instruction to issue a receipt based on an operation on the object. If an operation to instruct the issuance of a receipt has not been performed, the CPU 21 judges No in Act 33 and proceeds to Act 34.

In Act 34, the CPU 21 checks whether the amount paid by the shopper (payment amount) is equal to or greater than the total amount of the products registered in the product list. If the payment amount is less than the total amount, the CPU 21 judges No in Act 34 and returns to Act 33. Thus, the CPU 21 repeats Act 33 and Act 34 until an operation is performed to instruct the issuance of a receipt or to cancel the issuance of a receipt, or the payment amount is equal to or greater than the total amount. If an operation is performed to instruct the issuance of a receipt or to cancel the issuance of a receipt while the CPU 21 is in the standby state of Act 33 and Act 34, the CPU 21 judges Yes in Act 33 and proceeds to Act 35.
In Act 35, the CPU 21 assigns the value calculated by the formula (1-F2) to the variable F2, similarly to Act 28.

In Act 36, the CPU 21 changes the appearance of the receipt button B51 or the receipt button B51-2. That is, when the value of the variable F2 is 1, the CPU 21 changes the screen displayed on the touch panel 25 from the first payment screen SC5 shown in FIG. 10 to the second payment screen SC5-2 shown in FIG. 11 so that it is clear that the receipt button B51 has been operated. For this purpose, the CPU 21 generates an image corresponding to the second payment screen SC5-2. Then, the CPU 21 instructs the touch panel 25 to display the generated image. In response to this instruction, the touch panel 25 displays the second payment screen SC5-2. Then, when the value of the variable F2 is 0, the CPU 11 changes the screen displayed on the touch panel 25 from the second payment screen SC5-2 to the first payment screen SC5 so that it is clear that the receipt button B51-2 has been operated. For this purpose, the CPU 21 generates an image corresponding to the first payment screen SC5. Then, the CPU 21 instructs the touch panel 25 to display the generated image. In response to this instruction, the touch panel 25 displays the first payment screen SC5. After processing Act 36, the CPU 21 returns to Act 33.

The shopper makes payment by inserting cash into the settlement device 20 in an amount equal to or greater than the total amount displayed on the first payment screen SC5 or the second payment screen SC5-2. If the shopper selected a payment method other than cash in Act 27, the shopper makes payment using the selected payment method. The payment flow when using each payment method is omitted here because it is possible to use well-known methods.
If the payment amount becomes equal to or greater than the total amount while in the standby state of Act 33 and Act 34, the CPU 21 determines Yes in Act 34 and proceeds to Act 37 in FIG.

In Act 37, the CPU 21 checks whether the value of the variable F2 is 0. If the value of the variable F2 is 0, the CPU 21 judges that the answer is Yes in Act 37 and proceeds to Act 38.

In Act 38, the CPU 21 generates an image corresponding to the first settlement screen SC6 as shown in FIG. 12. Then, the CPU 21 instructs the touch panel 25 to display the generated image. In response to this instruction, the touch panel 25 displays the first settlement screen SC6.

FIG. 12 is a diagram showing an example of the first settlement screen SC6. The first settlement screen SC6 is a screen for allowing the shopper to confirm whether or not to complete the settlement. The first settlement screen SC6 includes a receipt button B61 and a settlement button B62. The receipt button B61, like the receipt button B41 in FIG. 8 and the receipt button B51 in FIG. 10, is operated by the shopper when instructing the settlement device 20 to issue a receipt. The position where the receipt button B61 is displayed on the touch panel 25 is the same as the position where the receipt button B41 in FIG. 8 and the receipt button B51 in FIG. 10 are displayed on the touch panel 25. The receipt button B61 is an example of an object operated by the operator to instruct the payment device 20 to issue a receipt. The settlement button B62 is operated by the shopper when instructing the payment device 20 to complete the settlement. The settlement button B62 displays a character string such as "Settlement" indicating that settlement is being made, i.e., that payment is completed. Alternatively, the settlement button B62 may display a character string such as "Payment Completed" indicating that payment is completed. The settlement button B62 is an example of a second button that does not indicate that a receipt will be issued. Note that the first settlement screen SC6 shown in FIG. 12 is the same as the first payment screen SC5 shown in FIG. 10 when "Cash" is selected in Act 27.

On the other hand, if the value of the variable F2 is 1, the CPU 21 determines No in Act 37 and proceeds to Act 39.
In Act 39, the CPU 21 generates an image corresponding to the second settlement screen SC6-2 as shown in Fig. 13. Then, the CPU 21 instructs the touch panel 25 to display the generated image. In response to this instruction, the touch panel 25 displays the second settlement screen SC6-2.

FIG. 13 is a diagram showing an example of the second settlement screen SC6-2. In FIG. 13, the same elements as those in FIG. 12 are given the same reference numerals as those in FIG. 12. The second settlement screen SC6-2 includes a receipt button B61-2 instead of the receipt button B61 of the first settlement screen SC6. The receipt button B61-2 is operated when the shopper instructs the settlement device 20 to stop issuing a receipt, similar to the receipt button B41-2 in FIG. 9 and the receipt button B51-2 in FIG. 11. The receipt button B61-2 displays a character string such as "Receipt will be issued" or "Receipt not required" to indicate that a receipt will be issued or that the button is to be pressed when a receipt is not required. This is similar to the receipt button B41-2 in FIG. 9 and the receipt button B51-2 in FIG. 11. The second settlement screen SC6-2 also includes a settlement button B62-2 in place of the settlement button B62 of the first settlement screen SC6. The settlement button B62-2, like the settlement button B62, is operated by the shopper when instructing the settlement device 20 to complete the settlement. The settlement button B62-2 displays a character string indicating that a receipt will be issued, such as "receipt issued." The settlement button B62-2 may also display a character string indicating that the settlement is completed, in addition to the character string indicating that a receipt will be issued. The settlement button B62-2 is an example of a first button indicating that a receipt will be issued.
As described above, when the value of the variable F2 is 1, the first button is displayed on the touch panel 25, and when the value of the variable F2 is 0, the second button is displayed. Therefore, by performing the processes of Act 37 to Act 39, the computer centered around the CPU 21 functions as a display control means that displays the first button indicating that a receipt will be issued or the second button indicating that a receipt will not be issued. In addition, the value of the variable F2 is based on the value of the variable F1 transmitted by the registration device in Act 17 of Fig. 2. Therefore, by performing the process of Act 17, the computer centered around the CPU 11 functions as a display control means.

In Act 40 of FIG. 4, the CPU 21 checks whether an operation has been performed to instruct the issuance of a receipt or to cancel the issuance of a receipt. That is, the CPU 21 checks whether a predetermined operation has been performed, such as touching the receipt button B61 displayed on the first settlement screen SC6 or the receipt button B61-2 displayed on the second settlement screen SC6-2. As described above, the receipt button B61 displayed on the first settlement screen SC6 is an object. Therefore, by performing the process of Act 40, the computer with the CPU 21 at its core functions as an input means for inputting an instruction to issue a receipt based on an operation on the object. If an operation to issue a receipt has not been performed, the CPU 21 judges No in Act 40 and proceeds to Act 41.

In Act 41, the CPU 21 checks whether an operation to instruct the completion of the settlement has been performed. That is, the CPU 21 checks whether a predetermined operation, such as touching the settlement button B62 displayed on the first settlement screen SC6 or the settlement button B62-2 displayed on the second settlement screen SC6-2, has been performed. If an operation to instruct the completion of the settlement has not been performed, the CPU 21 judges No in Act 41 and returns to Act 40. Thus, the CPU 21 repeats Act 40 and Act 41 until an operation to instruct the issuance of a receipt or the cancellation of the issuance of a receipt is performed, or an operation to instruct the completion of the settlement is performed. If an operation to instruct the issuance of a receipt or the cancellation of the issuance of a receipt is performed while the CPU 21 is in the standby state of Act 40 and Act 41, the CPU 21 judges Yes in Act 40 and proceeds to Act 42.
In Act 42, the CPU 21 assigns the value calculated by the formula (1-F2) to the variable F2, similarly to Act 28.
In Act 43, the CPU 21 changes the appearance of the receipt button B61 and the settlement button B62, or the receipt button B61-2 and the settlement button B62-2. That is, when the value of the variable F2 is 1, the CPU 21 makes it clear that the receipt button B61 has been operated and that a receipt will be issued. That is, the CPU 21 changes the screen displayed on the touch panel 25 from the first settlement screen SC6 shown in FIG. 12 to the second settlement screen SC6-2 shown in FIG. 13. For this purpose, the CPU 21 generates an image corresponding to the second settlement screen SC6-2. Then, the CPU 21 instructs the touch panel 25 to display this generated image. In response to this instruction, the touch panel 25 displays the second settlement screen SC6-2. Then, when the value of the variable F2 is 0, the CPU 11 changes the screen displayed on the touch panel 25 from the second settlement screen SC6-2 to the first settlement screen SC6 so that it is clear that the receipt button B61-2 has been operated. For this purpose, the CPU 21 generates an image corresponding to the first settlement screen SC6. Then, the CPU 21 instructs the touch panel 25 to display the generated image. In response to this instruction, the touch panel 25 displays the first settlement screen SC6. As described above, when the value of the variable F2 is 1, the first button is displayed on the touch panel 25, and when the value of the variable F2 is 0, the second button is displayed. Therefore, by performing the process of Act 43, the computer centered around the CPU 21 functions as a display control means for displaying the first button indicating that a receipt is to be issued or the second button indicating that a receipt is not to be issued. After the process of Act 43, the CPU 21 returns to Act 40.

If an operation to instruct completion of payment is performed while the CPU 21 is in the standby state of Act 40 and Act 41, the CPU 21 judges Yes in Act 41 and proceeds to Act 44. In Act 44, the CPU 21 performs payment processing. A well-known method can be used for the payment processing, so a description thereof will be omitted. As described above, the processing of Act 44 is performed in response to the operation of the second button, the settlement button B62, or the first button, the settlement button B62-2. Therefore, by performing the processing of Act 44, the CPU 21 functions as a payment means for making a settlement for a transaction in response to the operation of the first button or the second button.

In Act 45, the CPU 21 checks whether the value of the variable F2 is 1. If the value of the variable F2 is 1, the CPU 21 determines Yes in Act 45 and proceeds to Act 46.
In Act 46, the CPU 21 instructs the printer 26 to issue a receipt. In response to this instruction, the printer 26 issues a receipt. Thus, by performing the processing of Act 46, the computer with the CPU 21 as its central portion operates as an issuing means for issuing a receipt in cooperation with the printer 26. As described above, the CPU 21 instructs the printer 26 to issue a receipt when the first button, the settlement button B62-2, is operated. And, the CPU 21 does not instruct the printer 26 to issue a receipt when the second button, the settlement button B62, is operated. Thus, by performing the processing of Act 45 and Act 46, the computer with the CPU 21 as its central portion functions as an issuing control means for controlling the issuing means.
After processing Act 46, the CPU 21 returns to Act 21 of FIG.

In Act 47, the CPU 21 instructs the printer 26 to print a receipt. In response to this instruction, the printer 26 prints a receipt.
After processing Act 47, the CPU 21 returns to Act 21 of FIG.

According to the checkout system 1 of the first embodiment, the payment device 20 displays the settlement button B62-2 when an instruction to issue a receipt before the completion of the payment is given by operating the receipt button displayed on the registration device 10 or the payment device 20. Then, when the settlement button B62-2 is operated, the payment device performs the payment and issues a receipt. On the other hand, when an instruction to issue a receipt before the completion of the payment is given, the payment device 20 displays the settlement button B62. Then, when the settlement button B62 is operated, the payment device performs the payment but does not issue a receipt. In other words, when an instruction to issue a receipt is given, the function and display content of the settlement button are changed. This makes it less likely that a shopper will be confused about how to operate the settlement button compared to when multiple types of settlement buttons are displayed at once. Also, a shopper who does not need a receipt can complete the payment without being concerned with the operation of the receipt button, and will not be confused about the operation of the receipt button.

Furthermore, according to the checkout system 1 of the first embodiment, the registration device 10 displays a receipt button. Therefore, while registering an item, the shopper can instruct the payment device 20 to issue a receipt by operating the receipt button. Also, while registering an item, a store clerk can instruct the payment device 20 to issue a receipt by operating the receipt button at the request of the shopper.

Furthermore, according to the checkout system 1 of the first embodiment, the payment device 20 displays a receipt button. Therefore, the shopper can instruct the payment device 20 to issue a receipt by operating the button displayed on the payment device 20 until the payment is completed.
Furthermore, according to the checkout system 1 of the first embodiment, both the registration device 10 and the payment device 20 display a receipt button. Therefore, by operating the receipt button displayed on the registration device 10 or the receipt button displayed on the payment device 20, a shopper can instruct the payment device 20 to issue a receipt at any timing while the receipt button is displayed, from the time of product registration to the completion of payment.

Furthermore, according to the checkout system 1 of the first embodiment, the receipt button B21 displayed by the registration device 10 is operated by the shopper. Also, the receipt button B41, receipt button B51, and receipt button B61 displayed by the payment device 20 are operated by the shopper. By operating these receipt buttons, the shopper can instruct the payment device 20 to issue a receipt before issuing an instruction to complete the payment, without asking a store clerk to issue a receipt.

Furthermore, according to the checkout system 1 of the first embodiment, the receipt button B11 and receipt button B31 displayed by the registration device 10 are operated by a store clerk. Note that it is possible that a shopper who does not know that they can operate the receipt button B21, or a shopper who finds operating the receipt button B21 troublesome, verbally requests the store clerk to issue a receipt. In such a case, the store clerk can instruct the payment device 20 to issue a receipt by operating the receipt button B11 or receipt button B31.

Furthermore, according to the checkout system 1 of the first embodiment, the registration device 10 displays the receipt button B11 and the receipt button B31 on the store clerk-side touch panel 15 operated by the store clerk. The registration device 10 then displays the receipt button B21 on the customer-side touch panel 16 operated by the shopper. When the receipt button B11 or the receipt button B31 is operated by a store clerk or the like, the appearance of the receipt button B11 or the receipt button B31 is changed. At this time, the appearance of not only the receipt button B11 or the receipt button B31 but also the receipt button B21 is changed. Conversely, when the receipt button B21 is operated by a shopper or the like, the appearance of the receipt button B21 is changed. At this time, the appearance of not only the receipt button B21 but also the receipt button B11 or the receipt button B31 is changed. Therefore, the store clerk can tell that the receipt button B21 has been operated by the customer from the appearance of the receipt button B11 or the receipt button B31 displayed on the store clerk's touch panel 15. Also, the customer can tell that the receipt button B11 or the receipt button B31 has been operated by the store clerk from the appearance of the receipt button B21 displayed on the customer's touch panel 16.

Second Embodiment
The main circuit configuration of the checkout system 1 according to the second embodiment is similar to that of the checkout system 1 according to the first embodiment, and therefore a description thereof will be omitted.
In the second embodiment, the main memory 12 or the auxiliary storage device 13 of the registration device 10 stores a control program describing the control processing shown in Fig. 2, similar to the first embodiment. The main memory 22 or the auxiliary storage device 23 of the payment device 20 stores a control program describing the control processing shown in Fig. 3 and Fig. 4, similar to the first embodiment.
The operation of the checkout system 1 according to the second embodiment will be described below with reference to Figures 2 to 4. Note that the contents of the process described below are merely examples, and various processes capable of achieving similar results can be used as appropriate.
In the following description of the second embodiment, differences from the first embodiment will be mainly described.

In the second embodiment, the CPU 11 performs the same process in Act 3 as in the first embodiment. However, in the second embodiment, the CPU 11 displays a receipt button instead of the receipt button B11. The receipt button is operated by the operator of the registration device 10 at the request of the shopper when a receipt is not to be issued. A character string such as "No receipt required" is displayed on the receipt button to indicate that it is a button to be pressed when a receipt is not required. The receipt button is an example of an object that is operated by the operator to instruct not to issue a receipt.

In the second embodiment, the CPU 11 performs the same process in Act 4 as in the first embodiment. However, in the second embodiment, the CPU 11 displays a receipt button instead of the receipt button B21. The receipt button is operated by a shopper when he does not want a receipt to be issued. A character string such as "Touch if you do not need a receipt" or "No receipt required" is displayed on the receipt button, so that the shopper knows that it is a button to press when a receipt is not required. The receipt button is an example of an object that the operator operates to instruct not to issue a receipt.

In the second embodiment, in Act 6, the CPU 11 checks whether an operation has been performed to instruct not to issue a receipt. That is, the CPU 11 checks whether a predetermined operation has been performed, such as touching the receipt button displayed on the registration screen SC1 or the receipt button displayed on the customer screen SC2. Therefore, by performing the processing of Act 6 in the second embodiment, the computer centered around the CPU 11 inputs an instruction not to issue a receipt based on the operation on the object.

In the second embodiment, in Act 10, the CPU 11 changes the appearance of the receipt button displayed in place of the receipt button B11 and receipt button B21. That is, when the value of the variable F1 is 1, the CPU 11 changes the appearance of the receipt button so that it is clear that the receipt button has been operated or that a receipt will not be issued. When the value of the variable F1 is 0, the CPU 11 returns the appearance of the receipt button to its original state. Note that the state of the receipt button displayed on the clerk touch panel 15 or customer touch panel 16 when the value of the variable F1 is 1 is referred to as the selected state, and the state of the receipt button when the value of the variable F1 is 0 is referred to as the non-selected state.

In the second embodiment, the CPU 11 performs the same process in Act 12 as in the first embodiment. However, in the second embodiment, the CPU 11 displays a receipt button instead of the receipt button B31. Like the receipt button displayed in place of the receipt button B11, this receipt button displays a character string such as "No receipt required" that indicates that this is a button to be pressed when a receipt is not required. This receipt button is an example of an object that the operator operates to instruct not to issue a receipt.

In the second embodiment, in Act 13, the CPU 11 checks whether an operation has been performed to instruct not to issue a receipt. That is, the CPU 11 checks whether a predetermined operation, such as touching the receipt button displayed on the sub-menu screen SC3, has been performed. Therefore, by performing the processing of Act 13 in the second embodiment, the computer centered around the CPU 11 inputs an instruction not to issue a receipt based on the operation on the object.

In the second embodiment, in Act 16, the CPU 11 changes the appearance of the receipt button in the same manner as in Act 10 of the second embodiment. However, the receipt buttons whose appearances are changed by the CPU 11 here are the receipt button displayed in place of the receipt button B21 and the receipt button displayed in place of the receipt button B31.

Meanwhile, in the second embodiment, the CPU 21 of the payment device 20 performs the same process in Act 24 as in the first embodiment. However, in the second embodiment, the CPU 21 displays a first receipt button instead of the receipt button B41. The first receipt button is operated when the shopper instructs the payment device 20 not to issue a receipt. A character string is displayed on the first receipt button, such as "Touch if you do not need a receipt" or "No receipt required", to indicate that this is a button to be pressed when a receipt is not required. The first receipt button is an example of an object that the operator operates to instruct not to issue a receipt.

In the second embodiment, the CPU 21 performs the same process in Act 25 as in the first embodiment. However, in the second embodiment, the CPU 21 displays a second receipt button instead of the receipt button B41-2. The second receipt button is operated when the shopper instructs the payment device 20 to issue a receipt. The second receipt button displays a character string such as "Touch if receipt is required" or "Receipt required" that indicates that the button is to be pressed when a receipt is not required. Alternatively, the second receipt button displays a character string such as "No receipt will be issued" indicating that a receipt will not be issued.

In the second embodiment, in Act 26, the CPU 21 checks whether an operation has been performed to instruct not to issue a receipt or to issue a receipt. That is, the CPU 21 checks whether a predetermined operation has been performed, such as touching the first receipt button displayed on the first checkout screen SC4 or the second receipt button displayed on the second checkout screen SC4-2. As described above, the first receipt button is an object. Therefore, by performing the processing of Act 26 in the second embodiment, the computer centered around the CPU 21 inputs an instruction not to issue a receipt based on the operation on the object.

In the second embodiment, in Act 29, the CPU 21 changes the appearance of the first receipt button displayed in place of the receipt button B41 or the second receipt button displayed in place of the receipt button B41-2. That is, when the value of variable F2 is 1, the CPU 21 changes the appearance so that it is clear that the first receipt button has been operated or that a receipt will not be issued. That is, the CPU 21 changes the screen displayed on the touch panel 25 from the first accounting screen SC4 to the second accounting screen SC4-2. Then, when the value of variable F2 is 0, the CPU 11 changes the screen displayed on the touch panel 25 from the second accounting screen SC4-2 to the first accounting screen SC4 so that it is clear that the second receipt button has been operated.

In the second embodiment, the CPU 21 performs the same process in Act 31 as in the first embodiment. However, in the second embodiment, the CPU 21 displays a first receipt button instead of the receipt button B51. Like the first receipt button displayed in place of the receipt button B41, the first receipt button is operated when the shopper instructs the payment device 20 not to issue a receipt. The first receipt button displays a character string such as "Touch if you do not need a receipt" or "No receipt required" that indicates that the button is to be pressed when a receipt is not required. This is similar to the first receipt button displayed in place of the receipt button B41. The first receipt button is an example of an object that the operator operates to instruct not to issue a receipt.

In the second embodiment, the CPU 21 performs the same process in Act 32 as in the first embodiment. However, in the second embodiment, the CPU 21 displays a second receipt button instead of the receipt button B51-2. Like the second receipt button displayed in place of the receipt button B41-2, the second receipt button is operated when the shopper instructs the payment device 20 to issue a receipt. The second receipt button displays a character string such as "Touch if receipt is required" or "Receipt required" that indicates that the button is to be pressed when a receipt is not required. This is similar to the second receipt button displayed in place of the receipt button B41. Alternatively, the second receipt button displays a character string indicating that a receipt will not be issued, such as "Receipt will not be issued."

In the second embodiment, the CPU 21 checks in Act 33 whether an operation has been performed to instruct not to issue a receipt or to issue a receipt. That is, the CPU 21 checks whether a predetermined operation has been performed, such as touching the first receipt button displayed on the first payment screen SC5 or the second receipt button displayed on the second payment screen SC5-2. As described above, the first receipt button is an object. Therefore, by performing the processing of Act 33 in the second embodiment, the computer centered around the CPU 21 inputs an instruction not to issue a receipt based on the operation on the object.
In the second embodiment, in Act 36, the CPU 21 changes the appearance of the first receipt button displayed in place of the receipt button B51 or the second receipt button displayed in place of the receipt button B51-2, in the same manner as Act 29 in the second embodiment.

In the second embodiment, the CPU 21 performs the same process in Act 38 as in the first embodiment. However, in the second embodiment, the CPU 21 displays a first receipt button instead of the receipt button B61. The first receipt button, like the first receipt button displayed instead of the receipt button B41 and the first receipt button displayed instead of the receipt button B51, is operated when a shopper instructs the payment device 20 not to issue a receipt. The first receipt button is an example of an object that an operator operates to instruct not to issue a receipt. Note that in the second embodiment, a character string indicating that a receipt will be issued, such as "Receipt issued", may be displayed on the settlement button B62 .

In the second embodiment, the CPU 21 performs the same process in Act 39 as in the first embodiment. However, in the second embodiment, the CPU 21 displays a second receipt button instead of the receipt button B61-2. The second receipt button, like the second receipt button displayed instead of the receipt button B41-2 and the second receipt button displayed instead of the receipt button B51-2, is operated when the shopper instructs the payment device 20 to issue a receipt. The second receipt button displays a character string such as "Touch if receipt is required" or "Receipt required" that indicates that the button is to be pressed when a receipt is not required. Alternatively, the second receipt button displays a character string such as "No receipt will be issued" indicating that a receipt will not be issued. This is similar to the second receipt button displayed instead of the receipt button B41 and the receipt button B51-2. Furthermore, in the second embodiment, the settlement button B62-2 displays a character string indicating that a receipt will not be issued, such as "No receipt will be issued." Alternatively, in the second embodiment, the settlement button B62-2 may display a character string indicating that the payment will be completed.

In the second embodiment, in Act 40, the CPU 21 checks whether an operation has been performed to instruct not to issue a receipt or to issue a receipt. That is, the CPU 21 checks whether a predetermined operation has been performed, such as touching the first receipt button displayed on the first settlement screen SC6 or the second receipt button displayed on the second settlement screen SC6-2. As described above, the first receipt button is an object. Therefore, by performing the processing of Act 40 in the second embodiment, the computer centered around the CPU 21 inputs an instruction not to issue a receipt based on the operation on the object.
In the second embodiment, in Act 43, the CPU 21 changes the appearance of the first receipt button and settlement button B62 displayed in place of the receipt button B61, or the appearance of the second receipt button and settlement button B62-2 displayed in place of the receipt button B61-2, in the same manner as Act 29 in the second embodiment.

In the second embodiment, the CPU 21 does not perform the process of Act 46.
In the second embodiment, the CPU 21 instructs the printer 26 to issue a receipt in Act 47. In response to this instruction, the printer 26 issues a receipt. The receipt includes details related to the payment, such as the date and time of the payment, details of the exchanged products, and the paid amount. As described above, by performing the process of Act 47 in the second embodiment, the computer with the CPU 21 as its core works with the printer 26 to issue a receipt. As described above, when the receipt button is operated and the value of the variable F2 is 1, the CPU 21 does not instruct the printer 26 to issue a receipt, and when the value of the variable F2 is 0, the CPU 21 instructs the printer 26 to issue a receipt. When the payment is completed, the value of the variable F2 is 1 because an instruction not to issue a receipt before the completion of the payment has been given, and the value of the variable F2 is 0 because an instruction not to issue a receipt before the completion of the payment has not been given. In other words, the CPU 21 controls the printer 26 not to issue a receipt if it has been instructed not to issue a receipt before the completion of the payment, and to issue a receipt if it has not been instructed not to issue a receipt before the completion of the payment.

According to the checkout system 1 of the second embodiment, the payment device 20 does not issue a receipt if an instruction not to issue a receipt before the payment is completed is given by operating the receipt button displayed on the registration device 10 or the first receipt button displayed on the payment device 20. On the other hand, if an instruction not to issue a receipt before the payment is completed is not given, the payment device 20 issues a receipt when the payment is completed. Therefore, a shopper who does not need a receipt can complete the payment without being concerned with the operation of the first and second receipt buttons, and will not be confused about which to operate the first and second receipt buttons.
Furthermore, according to the checkout system 1 of the second embodiment, the registration device 10 displays a first receipt button. Therefore, even if an item is being registered, a shopper can instruct the payment device 20 not to issue a receipt by operating the first receipt button. Also, even if an item is being registered, a store clerk can instruct the payment device 20 not to issue a receipt by operating the first receipt button at the request of a shopper.

The above first and second embodiments may be modified as follows.
The checkout system 1 of the first and second embodiments is a semi-self-service checkout system that includes a registration device 10 and a payment device 20. However, instead of the checkout system 1, it may also be implemented as a self-service checkout system in which the registration device and the payment device are integrated and operated by a shopper as an operator.

In the first and second embodiments, the receipt button, or the receipt button, or the first and second receipt buttons are displayed on both the registration device 10 and the payment device 20. However, the receipt button, or the receipt button, or the first and second receipt buttons may be displayed on only one of the registration device 10 or the payment device 20.
In the first and second embodiments, a receipt button or a receipt button is displayed on the clerk-side touch panel 15 and the customer-side touch panel 16 of the registration device 10. However, the receipt button or the receipt button may be displayed on only one of the clerk-side touch panel 15 or the customer-side touch panel 16.

In the first embodiment, when issuing a receipt, the payment device 20 may issue a receipt in addition to the receipt. In this case, the payment device 20 may print the receipt and the receipt on the same paper.

In the first embodiment, a button for issuing a receipt was described, and in the second embodiment, a button for issuing a receipt without issuing a receipt was described. However, the present invention can also be applied to issuing or not issuing receipts and documents other than receipts. Such documents are, for example, coupons, discount tickets, lottery tickets, and exchange tickets issued to shoppers who make purchases that meet certain predetermined conditions. In this case, a button for issuing or not issuing these tickets is displayed in place of the receipt button or the first receipt button. Furthermore, a character string indicating whether or not to issue these tickets is displayed on the settlement button. Note that even if a button for issuing these tickets is operated, if the certain conditions are not met, the payment device 20 will not issue these tickets.

The receipt button or the first receipt button may be a hardware element such as a physical button. In this case, the hardware element is an example of an object that the operator operates to instruct whether to issue a receipt or not to issue a receipt. The second receipt button may also be a hardware element such as a physical button.

In the first embodiment, the receipt button B41, the receipt button B51, and the receipt button B61 may be displayed at different positions on the touch panel.

Although some embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be implemented in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their modifications are included in the scope and spirit of the invention, and are included in the scope of the invention and its equivalents described in the claims.
The invention as originally claimed in the present application is set forth below.
[1] A checkout system comprising a registration device that registers details of a transaction, and a payment device operated by a person who makes a payment for the transaction, the checkout system comprising: an issuing means, provided in the payment device, that issues a receipt; an input means, provided in at least one of the registration device and the payment device, that inputs an instruction to issue the receipt based on an operation on an object by an operator; a display control means, provided in at least one of the registration device and the payment device, that causes a first button indicating that a receipt will be issued if the instruction is input by the input means before the payment for the transaction is completed, and that causes a second button not indicating that a receipt will be issued if the instruction is not input before the payment for the transaction is completed; a payment means, provided in the payment device, that makes payment for the transaction in response to the operation of the first button or the second button; and an issuance control means, provided in the payment device, that controls the issuing means to issue the receipt for the payment made by the payment means when the first button is operated, and not to issue the receipt when the second button is operated.
[2] A checkout system as described in Appendix [1], wherein the object is displayed on at least one of a store clerk side display device of the registration device and a customer side display device of the registration device.
[3] A payment device to be operated by a person making a payment for the transaction, comprising: an issuing means for issuing a receipt; an input means for inputting an instruction to issue the receipt based on an operation on an object by an operator; a display control means for causing the input means to display a first button indicating that a receipt will be issued if the instruction is input by the input means before the payment for the transaction is completed, and to display a second button not indicating that a receipt will be issued if the instruction is not input before the payment for the transaction is completed; a payment means for making a payment for the transaction in response to the operation of the first button or the second button; and an issuance control means for controlling the issuing means to issue the receipt for the payment made by the payment means when the first button is operated, and not to issue the receipt when the second button is operated.
[4] A registration device for registering details of a transaction, comprising: an issuing means for issuing a receipt; a payment means for making payment for the transaction in response to the operation of a first button or a second button; and an issuing control means for controlling the issuing means to issue the receipt for the payment made by the payment means when the first button is operated, and not to issue the receipt when the second button is operated. The registration device constitutes a checkout system together with a payment device operated by a person making a payment for the transaction, and comprises: an input means for inputting an instruction to issue the receipt based on an operation on an object by the operator; and a display control means for causing the input means to display a first button indicating that a receipt will be issued if the instruction is input before the payment for the transaction is completed, and a second button indicating that a receipt will not be issued if the instruction is not input before the payment for the transaction is completed.
[5] A program for causing a computer provided in a payment device which constitutes a checkout system together with a registration device which registers details of a transaction and which has an issuing means for issuing a receipt to be operated by a person making a payment for the transaction to function as follows: input means for inputting an instruction to issue the receipt based on an operation on an object by an operator; display control means for causing the input means to display a first button indicating that a receipt will be issued if the instruction is input by the input means before the payment for the transaction is completed, and to display a second button not indicating that a receipt will be issued if the instruction is not input before the payment for the transaction is completed; payment means for making payment for the transaction in response to the operation of the first button or the second button; and issuance control means for controlling the issuing means to issue the receipt for the payment made by the payment means when the first button is operated, and not to issue the receipt when the second button is operated.
[6] A program for configuring a checkout system together with a payment device operated by a person making a payment for a transaction, the checkout system comprising: an issuing means for issuing a receipt; a payment means for making payment for the transaction in response to the operation of a first button or a second button; and an issuing control means for controlling the issuing means to issue the receipt for the payment made by the payment means when the first button is operated, and not to issue the receipt when the second button is operated; and for configuring a checkout system together with a payment device operated by a person making a payment for a transaction, the checkout system comprising: an input means for inputting an instruction to issue the receipt based on an operation on an object by the operator; and a display control means for displaying a first button indicating that a receipt will be issued if the instruction is input by the input means before the payment for the transaction is completed, and displaying a second button not indicating that a receipt will be issued if the instruction is not input before the payment for the transaction is completed.

1: Checkout system, 10: Registration device, 11, 21: CPU, 12, 22: Main memory, 13, 23: Auxiliary storage device, 14, 24: Communication interface, 15: Staff touch panel, 16: Customer touch panel, 17: Scanner, 20: Payment device, 25: Touch panel, 26: Printer.

Claims (6)

a first display control means for causing a display unit to display an object for instructing the user not to issue a receipt before the settlement for the transaction is completed;
a second display control means for causing the display unit to display a first button indicating that a receipt will not be issued or that the settlement will be completed if the object is operated before the payment amount is input when cash is selected as the payment method for the price of the transaction, and for causing the display unit to display a second button indicating that a receipt will be issued if the payment amount is input without operating the object;
a payment means for executing the payment in response to the operation of the first button or the second button;
A payment device comprising: The payment device according to claim 1, wherein the object is displayed on the display unit together with a button for selecting a payment method. The payment device according to claim 1, wherein the first button and the second button are displayed on the display unit together with the payment amount for the price. The payment device according to claim 1 or 3, wherein the second button is displayed on the display unit together with the object. a change means for changing a display form of the object before the payment amount for the transaction is input when the object is operated before the payment amount for the transaction is input,
A payment device as described in any one of claims 1 to 4, wherein the second display control means causes the display unit to display a first button indicating that a receipt will not be issued or that payment will be completed after the payment amount for the transaction is entered, when the object is operated before the payment amount for the transaction is entered. A computer included in a payment device having a display unit,
a first display control means for causing the display unit to display an object for instructing the user not to issue a receipt before the settlement for the transaction is completed;
a second display control means for displaying on the display unit a first button indicating that a receipt will not be issued or that the settlement will be completed if the object is operated before the payment amount is input when cash is selected as the payment method for the price of the transaction, and displaying on the display unit a second button indicating that a receipt will be issued if the payment amount is input without operating the object; and
a payment means for executing the payment in response to the operation of the first button or the second button;
A program to function as a