JP7617167B2 - Payment device and control program - Google Patents

Description

Embodiments of the present invention relate to a checkout system, a payment device and an input processing device that constitute the system, and a control program for causing a computer to function as the payment device.

One type of checkout system for mass retailers is one in which the input processing device for product data and the payment device for transactions are separate. The input processing device waits for the input of data related to product sales. When an operator inputs data, the input processing device generates payment information based on the data and transmits this payment information to the payment device. The payment device waits for the input of payment data for the payment information. When the operator inputs the payment data, the payment device processes the payment based on the payment information and payment data. This type of checkout system in which the input processing device and the payment device are separated can adopt a so-called semi-self-service system in which a store clerk operates the input processing device and a shopper operates the payment device.

When adopting the semi-self-service system, it is desirable to avoid situations where a shopper has difficulty operating a payment device, causing subsequent shoppers to wait to make a payment. For this reason, traditionally, the number of payment devices is greater than the number of input processing devices. In this case, there are two configurations: the input processing device monitors the status of each payment device, automatically selects an available payment device, and transmits payment information to that payment device, and the status of each payment device is displayed on the display of the input processing device, and a store clerk selects an available payment device and transmits payment information to that payment device.

In either form, the input processing device needs to have an information analysis function that collects and analyzes status information (status) from the payment devices so that the input processing device can monitor the status of each payment device.

JP 2013-242839 A

The problem that the embodiment of the present invention aims to solve is to provide a checkout system that eliminates the need for an information analysis function for the input processing device to monitor the status of each payment device.

In one embodiment, an input processing device that generates payment information required for settlement of a transaction based on data related to the transaction and transmits the payment information to two or more payment devices and a payment device that constitutes a checkout system include a receiving means, a storage means, a payment means, and a shifting means. The receiving means receives payment information. The storage means has a storage area capable of storing multiple pieces of payment information received by the receiving means. When an instruction to start a payment is input, the payment means processes a payment based on the payment information that was received earliest among the payment information stored in the storage area. The shifting means processes a payment based on the payment information that was received earliest by the payment means, or, when a payment is processed by the payment means of another payment device, shifts the multiple pieces of payment information stored in the storage area so that the payment information that was received second earliest becomes the earliest payment information.

1 is a schematic diagram of a checkout system according to an embodiment of the present invention. FIG. 2 is a block diagram showing the main circuit configuration of the merchandise registration device and the settlement device according to the embodiment. FIG. 2 is a schematic diagram showing main memory areas formed in a RAM of the product registration device. FIG. 2 is a schematic diagram showing main memory areas formed in a RAM of the payment device. 4 is a flowchart showing main steps of a control process executed by a CPU of the merchandise registration device according to a control program. FIG. 4 is a schematic diagram showing an example of a registration screen displayed on a touch panel of the product registration device. FIG. 6 is a schematic diagram showing an example of a transmission screen displayed on a touch panel of the product registration device. 4 is a flowchart showing main procedures of a control process executed by a CPU of the settlement device according to a control program. FIG. 13 is a schematic diagram showing an example of a start acceptance screen displayed on a touch panel of the payment registration device. FIG. 4 is a schematic diagram showing an example of a payment screen displayed on a touch panel of the payment registration device.

Hereinafter, an embodiment of a checkout system in which the input processing device does not need to collect status information of each payment device will be described with reference to the drawings.
This embodiment illustrates a semi-self-service checkout system installed in a store such as a mass retailer, etc. In this system, a store clerk operates a product registration device, which is one aspect of an input processing device, and a shopper operates a payment device.

Figure 1 is a schematic diagram of a checkout system 10 in this embodiment. The checkout system 10 includes multiple product registration devices 11 and a greater number of payment devices 12 than the product registration devices 11. The product registration devices 11 and the payment devices 12 are arranged for each checkout lane in the store.

Figure 1 shows a case where two product registration devices 11 and six payment devices 12 are arranged in two checkout lanes. In Figure 1, one product registration device 11 and three payment devices 12 are arranged for one checkout lane. The checkout system 10 can include any number of product registration devices 11 and any number of payment devices 12. In addition, the ratio of the number of product registration devices 11 and payment devices 12 arranged in the checkout lanes can also be any number.

The product registration device 11 is operated by a store clerk 21 who plays the role of a checker. The payment device 12 is operated by a shopper 22 who purchases products sold in the store. Note that the payment device 12 may also be operated by the store clerk 21.

In FIG. 1, the product registration device 11 is attached to a work table 23. The work table 23 has a rectangular top plate. By arranging multiple work tables 23 so that the longitudinal directions of the top plates are approximately parallel, an aisle (checkout lane) for shoppers 22 is formed.

The product registration device 11 has the functions of registering products for purchase, generating payment information, processing payments, and transmitting the payment information to the payment device 12. The registration process is a process for registering products brought by shoppers 22 who have entered an aisle as purchased products. The payment process is a process for settling transactions, which are the buying and selling of products. The payment information is information required for the payment process.

When the payment device 12 receives payment information from the product registration device 11, it performs payment processing based on the payment information.

Figure 2 is a block diagram showing the main circuit configuration of the product registration device 11 and the payment device 12. Both the product registration device 11 and the payment device 12 are connected to a network, LAN (local area network) 13. Instead of LAN 13, the network can be another communication network such as the Internet or a wireless LAN. Alternatively, information can be exchanged between the product registration device 11 and the payment device 12 via a server.

The product registration device 11 includes a CPU (central processing unit) 11a, a ROM (read-only memory) 11b, a RAM (random-access memory) 11c, an auxiliary memory unit 11d, a drawer opening unit 11e, a scanner 11f, a touch panel 11g, a printer 11h, a card reader/writer 11i, a communication unit 11j, and a transmission system 11k.

The CPU 11a, the ROM 11b, the RAM 11c and the auxiliary storage unit 11d are connected by a transmission system 11k to form a computer.
The CPU 11a corresponds to the central part of the computer. The CPU 11a controls each part to realize various functions of the product registration device 11 based on an operating system, middleware, and application programs stored in the ROM 11b and RAM 11c.

ROM 11b corresponds to the main memory of the computer. ROM 11b stores the operating system. ROM 11b may also store the middleware and application programs. ROM 11b may also store data referenced by CPU 11a when performing various processes.

RAM 11c corresponds to the main memory portion of the computer. RAM 11c stores data that CPU 11a references when performing various processes. Furthermore, RAM 11c is used as a so-called work area that stores data that CPU 11a uses temporarily when performing various processes.

The auxiliary memory unit 11d corresponds to the auxiliary memory portion of the computer. The auxiliary memory unit 11d stores data used by the CPU 11a when performing various processes, or data generated by the processes in the CPU 11a. For example, the auxiliary memory unit 11d can be an EEPROM (electrical erasable programmable read-only memory), a HDD (hard disk drive), or an SSD (solid state drive).

The application programs stored in ROM 11b or auxiliary storage unit 11d include the control program described in relation to the control processing described below. The product registration device 11 is generally transferred with the control program stored in ROM 11b or auxiliary storage unit 11d. However, there are also cases where the product registration device 11 is transferred without the control program being stored in ROM 11b or auxiliary storage unit 11d. In this case, the control program is recorded on a removable recording medium such as a magnetic disk, magneto-optical disk, optical disk, semiconductor memory, etc. and transferred. Alternatively, the control program may be transferred via a network, and this control program may be written to the auxiliary storage unit 11d of the product registration device 11 that was transferred separately.

The drawer opening unit 11e automatically opens the drawer for storing currency. The scanner 11f reads product information and obtains the product code of the product. Any of various well-known types can be used as the scanner 11f. The scanner 11f may be compatible with only one of the various well-known types, or may be compatible with multiple types. In other words, the scanner 11f may include a fixed or handheld two-dimensional code scanner. The scanner 11f may also include a type that identifies products using image recognition technology from images of the products.

The touch panel 11g includes a display device and a touch sensor. The display device has a display screen of any type, such as a GUI screen. The display device may be a well-known device, such as a color LCD. The touch sensor is disposed over the display surface of the display device. The touch sensor detects the position of the operator's touch on the display surface of the display device, and sends this position information to the CPU 11a. The touch sensor may be a well-known device.

The printer 11h issues receipts by printing various characters and images on receipt paper. For example, a thermal printer or a dot matrix printer can be used as this type of printer 11h.

The card reader/writer 11i has the function of reading data recorded on a card and the function of writing data to the card. Cards may include payment cards such as credit cards, debit cards, electronic money cards, and prepaid cards, as well as membership cards such as member's cards and point cards. Membership cards record at least information to identify the member who owns the card. The card reader/writer 11i may be a magnetic, contact, or non-contact device, or may include multiple types of devices.

The communication unit 11j performs data communication with multiple payment devices 12 connected via the LAN 13. The communication unit 11j can also perform data communication with other product registration devices 11 via the LAN 13.

Transmission system 11k transmits data between CPU 11a, ROM 11b, RAM 11c, auxiliary memory unit 11d, drawer opening unit 11e, scanner 11f, touch panel 11g, printer 11h, card reader/writer 11i, and communication unit 11j. Transmission system 11k can use well-known systems including various buses such as a system bus and various interface circuits that connect these buses to each unit.

As hardware for such a product registration device 11, for example, a POS terminal that supports existing face-to-face sales methods can be used.

The payment device 12 includes a CPU 12a, a ROM 12b, a RAM 12c, an auxiliary memory unit 12d, an automatic change dispenser 12e, a scanner 12f, a touch panel 12g, a printer 12h, a card reader/writer 12i, a communication unit 12j, and a transmission system 12k.

The CPU 12a, ROM 12b, RAM 12c and auxiliary memory unit 12d are connected via a transmission system 12k to form a computer.

The CPU 12a corresponds to the central part of the computer. The CPU 12a controls each part to realize various operations of the payment device 12 based on the operating system, middleware, and application programs stored in the ROM 12b and RAM 12c.

ROM 12b corresponds to the main memory of the computer. ROM 12b stores the operating system. ROM 12b may also store the middleware and application programs. ROM 12b may also store data referenced by CPU 12a when performing various processes.

RAM 12c corresponds to the main memory portion of the computer. RAM 12c stores data that CPU 12a references when performing various processes. Furthermore, RAM 12c is used as a so-called work area that stores data that CPU 12a uses temporarily when performing various processes.

The auxiliary memory unit 12d corresponds to the auxiliary memory portion of the computer. The auxiliary memory unit 12d stores data used by the CPU 12a when performing various processes, or data generated by the processes in the CPU 12a. For example, an EEPROM, HDD, or SSD can be used as the auxiliary memory unit 12d.

The application programs stored in ROM 12b or auxiliary storage unit 12d include the control program described in relation to the control processing described below. The transfer of the payment device 12 is generally performed with the control program stored in ROM 12b or auxiliary storage unit 12d. However, there are also cases where the payment device 12 is transferred without the control program being stored in ROM 12b or auxiliary storage unit 12d. In this case, the control program is recorded on a removable recording medium such as a magnetic disk, a magneto-optical disk, an optical disk, or a semiconductor memory and transferred. Alternatively, the control program may be transferred via a network, and this control program may be written to the auxiliary storage unit 12d of the separately transferred payment device 12.

The automatic change machine 12e receives coins and bills that are inserted. The automatic change machine 12e also dispenses coins and bills as change.

Scanner 12f reads product information and obtains the product code of the product. As scanner 12f, various well-known types can be used as they are. Scanner 12f may be compatible with only one of various well-known types, or may be compatible with multiple types. In other words, scanner 12f may include a fixed or handheld two-dimensional code scanner. Scanner 12f may also include a type that identifies products from images of the products using image recognition technology.

The touch panel 12g includes a display device and a touch sensor. The display device can display any screen, such as a GUI screen. The display device can be a well-known device, such as a color LCD. The touch sensor is disposed over the display surface of the display device. The touch sensor detects the position of the operator's touch on the display surface of the display device, and sends the position information to the CPU 12a. The touch sensor can be a well-known device.

The printer 12h issues receipts by printing various characters and images on receipt paper. Examples of printers that can be used include thermal printers and dot-matrix printers.

The card reader/writer 12i has the function of reading data recorded on a card and the function of writing data to the card. Cards may include payment cards such as credit cards, debit cards, electronic money cards, and prepaid cards, as well as membership cards such as member's cards and point cards. Membership cards record at least information to identify the member who owns the card. The card reader/writer 12i may be a magnetic, contact, or non-contact device, or may include multiple types of devices.

The communication unit 12j performs data communication with multiple product registration devices 11 connected via the LAN 13. The communication unit 12j can also perform data communication with other payment devices 12 via the LAN 13.

The transmission system 12k transmits data between the CPU 12a, ROM 12b, RAM 12c, auxiliary memory unit 12d, automatic change machine 12e, scanner 12f, touch panel 12g, printer 12h, card reader/writer 12i, and communication unit 12j. The transmission system 12k can be a well-known system including various buses such as a system bus and various interface circuits that connect these buses to each unit.

As hardware for such a payment device 12, for example, a POS terminal that supports an existing self-service system can be used.

Figure 3 is a schematic diagram showing the main memory areas formed in the RAM 11c of the product registration device 11. In Figure 3, memory area 31 is an area that stores multiple records consisting of data on product code, product name, unit price, quantity, and amount. The product code is a unique code for identifying each product individually. Each product is assigned a product code represented by, for example, a barcode. The product name and unit price are the name and price per unit of the product identified by the product code in the same record. The quantity and amount are sales data of the product identified by the product code in the same record, i.e., the number of units sold and the sales amount for that number of units.

Although not shown, the checkout system 10 is connected to a database server via the LAN 13. This database server has a product database for setting product information such as product name and unit price in association with the product code of each product. When a product code is acquired in the product registration device 11, the CPU 11a queries the database server for product information using the product code. Upon receiving this query, the database server accesses the product database, reads out product information associated with the product code from the product database, and notifies the product registration device 11 via the LAN 13. The CPU 11a of the product registration device 11 stores the product information notified from the database server in a memory area 31. Hereinafter, the memory area 31 is referred to as a registered product table 31.

Memory area 32 is an area for storing the total number of items and the total price. The total number is the sum of the numbers of items shown in each record stored in registered product table 31. The total price is the sum of the prices shown in each record stored in registered product table 31. Hereinafter, memory area 32 is referred to as total table 32.

Figure 4 is a schematic diagram showing the main memory areas formed in the RAM 12c of the payment device 12. In Figure 4, memory area 41 is an area that temporarily stores payment information received from the product registration device 11. Memory area 41 is divided into an area called processing payment buffer 41-0 and N (N>1) areas called waiting payment buffers 41-1 to 41-N, each of which is assigned identification data from waiting 1 to waiting N. Processing payment buffer 41-0 and each of waiting payment buffers 41-1 to 41-N are both capable of storing the payment information.

Memory area 42 is the area for standby counter n. The initial value of standby counter n is "0" and it counts up or down by "1" by the action of CPU 12a.

Figure 5 is a flow chart showing the main steps of the control process executed by the CPU 11a of the product registration device 11 according to the control program. Figures 6 and 7 are schematic diagrams showing various screen examples displayed on the touch panel 11g of the product registration device 11 by the control process. Figure 8 is a flow chart showing the main steps of the control process executed by the CPU 12a of the payment device 12 according to the control program. Figures 9 and 10 are schematic diagrams showing various screen examples displayed on the touch panel 12g of the payment device 12 by the control process. The operation of the checkout system 10 will be explained below using these figures. Note that the contents of the process explained below are just an example, and various processes that can achieve similar results can be used as appropriate.

First, the operation of the product registration device 11 will be described.
When the product registration device 11 is started in a mode for registering purchased products, the CPU 11a starts a control process according to the procedure shown in the flowchart of Fig. 5. First, the CPU 11a clears the registered product table 31 and the total table 32 (Act 1). Next, the CPU 11a displays a registration screen SC1 (see Fig. 6) on a part of the screen of the touch panel 11g (Act 2).

The registration screen SC1 shows the contents of the registered product table 31a and the total table 32a, and allows the store clerk 21 to check the status of the registration process. An example of the registration screen SC1 is shown in Figure 6. The registration screen SC1 includes display areas R1 and R2. Display area R1 displays the product name, quantity, and unit price of the product most recently registered as purchased, and the total quantity and total amount of the products purchased after that product was registered. Display area R2 displays a list of the product names, quantities, unit prices, and amounts of products registered as purchased before the product shown on the registration screen SC1.

Although not shown in the figure, the CPU 11a displays various function buttons, such as a product button that allows the store clerk 21 to specify a product and a subtotal button, outside the area of the screen of the touch panel 11g that is designated as the registration screen SC1.

With the registration screen SC1 displayed, the store clerk 21 operates, for example, the scanner 11f or the product button to sequentially input the product codes of the products purchased by the shopper 22. Then, when the store clerk 21 has finished inputting the product codes of all the purchased products, he or she touches the subtotal button.

After displaying the registration screen SC1, the CPU 11a waits for the acquisition of the product code of the product to be registered (Act 3). When the product code input via the scanner 11f or the product button is acquired (Act 3: YES), the CPU 11a detects product information such as the product name and unit price associated with the product code and set in the product database. The CPU 11a also calculates the sales amount by multiplying this unit price by the number of units sold. The CPU 11a then registers the product sales data including the product code, product name, unit price, number of units sold, and sales amount as one record in the registered product table 31a (Act 4). The CPU 11a also adds the number of units sold and the sales amount to the total table 32a. The CPU 11a then updates the registration screen SC1 to conform to the contents of the registered product table 31a and the total table 32a (Act 5).

After updating the registration screen SC1, the CPU 11a checks whether the product code of the product to be registered has been acquired (Act 6). If the product code has not been acquired (No in Act 6), the CPU 11a checks whether the subtotal button has been touched (Act 7). If the subtotal button has not been touched (No in Act 7), the CPU 11a checks again whether the product code has been acquired (Act 6). Therefore, in Act 6 and Act 7, the CPU 11a waits for the product code to be acquired or the subtotal button to be touched. Note that while waiting here, the CPU 11a may check the occurrence of another event, such as the performance of another operation, and transition to processing according to the event that has occurred.

When the product code is acquired during the standby state of Act 6 and Act 7 (YES in Act 6), the CPU 11a returns to the processing of Act 4. The CPU 11a then repeats the subsequent processing in the same manner as described above.

If the subtotal button is touched during the standby state of Act 6 and Act 7 (YES in Act 7), the CPU 11a generates payment information based on the contents of the registered product table 31a and the total table 32a at this time (Act 8: generation means). Then, the CPU 11a displays the transmission screen SC2 (see FIG. 7) on a portion of the screen of the touch panel 11g (Act 9).

An example of the send screen SC2 is shown in FIG. 7. The send screen SC2 includes display areas R3 and R4, and buttons B1, B2, B3, and B4. Display area R3 displays the total quantity and total amount in the total table 32a. Display area R4 displays various messages. Buttons B1 and B2 allow the store clerk 21 to specify that a discount should be applied to the total amount. Button B3 allows the store clerk 21 to specify that a partial area of the screen of the touch panel 11g should be returned to the registration screen SC1. Button B4 allows the store clerk 21 to specify that the payment information should be sent to the payment device 12. In the following description, button B3 will be referred to as the back button B3, and button B4 will be referred to as the send button B4.

When the transmission screen SC2 is displayed, the CPU 11a checks whether the back button B3 has been operated (Act 10). If the back button B3 has not been operated (Act 10: No), the CPU 11a checks whether the send button B4 has been operated (Act 11). If the send button B4 has not been operated (Act 11: No), the CPU 11a checks again whether the back button B3 has been operated (Act 10). Therefore, the CPU 11a waits for the back button B3 or the send button B4 to be operated in Act 10 and Act 11. In addition, the CPU 11a may check the occurrence of another event, such as another operation, during this standby state and transition to a process according to the event that has occurred. For example, when either the button B1 or B2 is touched by the store clerk 21, the CPU 11a changes the total amount included in the payment information according to the subsequent instruction by the store clerk 21.

When the back button B3 is operated in the standby state of Act 10 and Act 11 (YES in Act 10), the CPU 11a returns a portion of the screen of the touch panel 11g to the registration screen SC1 (Act 12). After that, the CPU 11a proceeds to the processing of Act 6 and repeats the subsequent processing in the same manner as described above.

When the send button B4 is operated in the standby state of Act 10 and Act 11 (YES in Act 11), the CPU 11a transmits payment information in parallel to all payment devices 12 located in the same checkout lane as the product registration device 11 in which it is installed (Act 13: distribution means).

Specifically, the CPU 11a controls the communication unit 11j to transmit payment information to the LAN 13 using the communication addresses set for all payment devices 12 arranged in the same checkout lane as the product registration device 11 in which the CPU 11a is installed as the destination address and the communication address set for the CPU 11a as the source address. This results in payment information with a destination address and a source address set for each payment device 12, and each payment information is transmitted via the LAN 13. At this time, the CPU 11a may transmit the payment information to each payment device 12 simultaneously, or may transmit the payment information in chronological order with a time lag for each payment device 12. The payment information is received by the payment device 12 whose destination address matches the communication address. The payment device 12 that receives the payment information can identify the product registration device 11 that is the source of the payment information by storing the source address of the payment information.

When the payment information has been sent, the CPU 11a displays a notification screen on a portion of the screen of the touch panel 11g (Act 14). The notification screen is a screen that notifies the store clerk that the payment information has been sent to the payment device 12. The notification screen displays a button that allows the store clerk 21 to instruct the store clerk 21 to close the screen, and when this button is touched, the CPU 11a ends the information processing for one transaction. The CPU 11a then resumes processing from Act 1.

After checking the notification screen, the store clerk 21 informs the shopper 22 that payment can be made at any of the three payment devices 12 installed in the same checkout lane. Upon receiving this notification, the shopper 22 moves to an available payment device 12 and performs the operation to make the payment.

Next, the operation of the settlement device 12 will be described.
When the payment device 12 is started, the CPU 12a starts the control process of the procedure shown in the flow chart of FIG. 8. First, the CPU 12a initializes the standby counter n in the memory area 42 to "0" (Act 21). The CPU 12a also sets the screen of the touch panel 12g to a standby screen (Act 22). The standby screen indicates that the payment process is not being performed, and any information may be displayed on the standby screen. For example, the standby screen may display a message indicating that the payment process cannot be performed, or any image such as an advertisement as a screen saver.

The processing procedure of Act 21 and Act 22 is not limited to the procedure shown in Fig. 8. For example, the processing of Act 22 may be executed first, and then the processing of Act 21 may be executed.
After completing the processes of Act 21 and Act 22, the CPU 12a waits for reception of payment information (Act 23).

As described above, in the processing of Act 13 in FIG. 5, the CPU 11a of the product registration device 11 transmits payment information from the communication unit 11j to the LAN 13. This payment information is received by the communication units 12j provided in all payment devices 12 located in the same checkout lane as the product registration device 11 that transmitted the payment information.

When the payment information is received (YES in Act 23), the CPU 12a counts up the waiting counter n by "1" (Act 24). Then, the CPU 12a stores the received payment information in the waiting payment buffer 41-n, which uses waiting n (n is the value of the waiting counter n) as identification data (Act 25: storage means). After that, the CPU 12a displays the start reception screen SC3 (see FIG. 9) on a part of the screen of the touch panel 12g (Act 26).

An example of the start reception screen SC3 is shown in FIG. 9. The start reception screen SC3 includes display areas R5 and R6, and buttons B5 and B6. Display area R5 displays operation guidance for the shopper 22 operating the payment device 12. Display area R6 displays the total number and total amount included in the payment information stored in the waiting payment buffer 41-1, which has waiting 1 as its identification data. Button B5 is used by the shopper 22 to specify the start of payment. Button B6 is used by the shopper 22 to specify the call of a store clerk. In the following description, button B5 is referred to as the start payment button B5, and button B6 is referred to as the call store clerk button B6.

When the start reception screen SC3 is displayed, the CPU 12a checks whether the payment start button B5 has been operated (Act 27: reception means). If the payment start button B5 has not been operated (Act 27: NO), the CPU 12a checks whether a clear command has been received from another payment device 12 connected via the network 13 (Act 28). If the clear command has not been received (Act 28: NO), the CPU 12a checks again whether the payment start button B5 has been operated (Act 27). Therefore, in Act 27 and Act 28, the CPU 12a waits for the payment start button B5 to be operated or for the clear command to be received. In this standby state, the CPU 12a may check the occurrence of another event, such as another operation, and transition to a process according to the event that has occurred. For example, when the store clerk call button B6 is touched by the shopper 22, the CPU 12a controls the communication unit 12j to send a store clerk call command to the product registration device 11 installed in the same checkout lane as the payment device 12.

When the payment start button B5 is operated in the standby state of Act 27 and Act 28 (YES in Act 27), the CPU 12a moves the payment information stored in the standby payment buffer 41-1, which has standby 1 as its identification data, to the processing payment buffer 41-0 (Act 29). The CPU 12a also controls the communication unit 12j to send a clear command to other payment devices 12 installed in the same checkout lane as the payment device 12 on which it is installed (Act 30: command means).

Specifically, the CPU 12a controls the communication unit 12j to send a clear command to the LAN 13 with the communication addresses set in each of the other payment devices 12 as the destination address and the communication address set in the CPU 12a as the source address. As a result, a clear command with a destination address and a source address set for each of the other payment devices 12 is constructed, and each clear command is sent via the LAN 13. These clear commands are received by the payment device 12 whose destination address matches the communication address. The payment device 12 that receives the clear command can identify the payment device 12 that sent the clear command by storing the source address of the clear command.

The processing procedures of Act 29 and Act 30 are not limited to the procedures shown in Fig. 8. For example, the processing of Act 30 may be executed first, and then the processing of Act 29 may be executed.
When the processes of Act 29 and Act 30 are completed, the CPU 12a displays a settlement screen SC4 (see FIG. 10) on a part of the screen of the touch panel 12g (Act 31).

An example of the payment screen SC4 is shown in FIG. 10. The payment screen SC4 includes display areas R7 and R8, and buttons B7, B8, and B9. Display area R7 displays operation guidance for the shopper 22 who operates the payment device 12. Display area R8 displays the total number and total amount included in the payment information stored in the processing payment buffer 41-0. Button B7 allows the shopper 22 to specify that the payment method is cash. Button B8 allows the shopper 22 to specify that the payment method is electronic money. Button B9 allows the shopper 22 to specify that the store clerk 21 should be called. In the following description, button B7 will be referred to as the cash button B7, button B8 will be referred to as the electronic money button B8, and button B9 will be referred to as the store clerk call button B9.

After checking the payment screen SC4, the shopper 22 decides whether to pay with cash or electronic money. If paying with cash, the shopper touches the cash button B7 and inserts cash equal to or greater than the total amount into the automatic change machine 12e. On the other hand, if paying with electronic money, the shopper touches the electronic money button B8 and has the card reader/writer 12i read the data on the electronic money card.

The CPU 12a, which has displayed the payment screen SC4, waits for the cash button B7 or the electronic money button B8 to be touched. When the cash button B7 or the electronic money button B8 is touched, the CPU 12a executes the payment process using the payment method selected by the touched button (Act 32: Payment method). That is, when the cash button B7 is touched, the CPU 12a executes the payment process for cash payment. When the electronic money button B8 is touched, the CPU 12a executes the payment process for electronic money payment. These payment processes are well known in existing self-service POS terminals, so a description of them will be omitted here.

The payment method is not limited to cash or electronic money. For example, the payment device 12 can also support payment methods using credit cards, gift certificates, and other vouchers.

When the payment process is complete, the CPU 12a executes the receipt production process (Act 33). That is, the CPU 12a edits the print data for the receipt based on the payment information stored in the processing payment buffer 41-0. The CPU 12a then operates the printer 12h to produce a receipt. Once the receipt has been produced, the CPU 12a proceeds to the process of Act 35.

On the other hand, when a clear command is received by the communication unit 12j in the standby state of Act 27 and Act 28 (YES in Act 28), the CPU 12a clears the payment information stored in the standby payment buffer 41-1, which has standby 1 as its identification data (Act 34: clearing means). Therefore, the total number and total amount displayed in the display area R6 of the start reception screen SC3 are erased. After that, the CPU 12a proceeds to the processing of Act 35.

In Act 35, the CPU 12a checks whether payment information is stored in the waiting payment buffer 41-2, which has standby 2 as its identification data. If payment information is not stored (NO in Act 35), the CPU 12a proceeds to processing Act 37. If payment information is stored (YES in Act 35), the CPU 12a sequentially shifts the payment information stored in the waiting payment buffers 41-2 to 41-N, which have standby 2, standby 3, ..., standby N as their identification data, to the waiting payment buffers 41-1 to 41-(N-1) whose identification data numbers are "1" smaller (Act 36). The CPU 12a then proceeds to processing Act 37.

In Act 37, the CPU 12a counts down the standby counter n by "1". Then, the CPU 12a checks whether the standby counter n has become the initial value "0" (Act 38). If the standby counter n is not the initial value "0", that is, if the standby counter n is "1" or greater (NO in Act 38), the CPU 12a proceeds to the processing of Act 26 and repeats the subsequent processing as described above. If the standby counter n is the initial value "0" (YES in Act 38), the CPU 12a proceeds to the processing of Act 22 and repeats the subsequent processing as described above.

In this manner, in the checkout system 10 of this embodiment, when the store clerk 21 finishes registering the purchased items on the product registration device 11 and touches the send button B4 on the send screen SC2, payment information including sales data for the purchased items is sent to all payment devices 12 located in the same checkout lane as the product registration device 11. Therefore, a shopper 22 who has finished registering the items he or she will purchase can pay for the purchased items at all payment devices 12 to which the payment information was sent. The shopper then operates any available payment device 12 among the payment devices 12 located in the same checkout lane to make the payment. This operation is explained below with a specific example.

First, we will consider a checkout lane where no shoppers are currently making a payment. We will also assume that this checkout lane has three payment devices 12 (12-1, 12-2, 12-3).

When the first shopper 22-1 comes to pay at the checkout lane, the store clerk 21 operates the product registration device 11 to register the products that the shopper 22-1 will purchase. Once registration is complete, the store clerk 21 touches the send button B4. This causes the product registration device 11 to transmit payment information for the shopper 22-1 to each of the payment devices 12-1, 12-2, and 12-3.

In each of the payment devices 12-1, 12-2, and 12-3, the payment information is stored in the standby payment buffer 41-1, which has standby 1 as its identification data. In addition, in each of the payment devices 12-1, 12-2, and 12-3, a start reception screen SC3 is displayed on the touch panel 12g, and the total points and total amount included in the payment information are displayed in the display area R6 of this screen.

The store clerk 21 instructs the shopper 22-1 to operate the payment devices 12-1, 12-2, and 12-3 to make the payment. At this time, the store clerk tells the shopper that he or she may operate any of the available payment devices 12-1, 12-2, and 12-3.

Having received the payment instruction, the shopper 22-1 moves to an available payment device, for example, payment device 12-1, and touches the payment start button B5 displayed on the touch panel 12g. At this time, the shopper 22-1 can confirm that the total number of items and total price of the items he or she will purchase are displayed in the display area R6. In other words, the shopper 22-1 can recognize that payment for his or her transaction is possible.

When the shopper 22-1 touches the payment start button B5, the payment information stored in the waiting payment buffer 41-1, which has the identification data "wait 1", is transferred to the processing payment buffer 41-0 in the payment device 12-1. As a result, the payment device 12-1 is able to carry out the payment process related to this payment information, issue a receipt, etc. The shopper 22-1 makes the payment using cash, electronic money, etc.

In addition, when shopper 22-1 touches payment start button B5, payment device 12-1 sends a clear command to the other payment devices 12-2, 12-3 installed in the same checkout lane. When the other payment devices 12-2, 12-3 receive this clear command, the payment information stored in the standby payment buffer 41-1, which has standby 1 as its identification data, is cleared. Therefore, the other payment devices 12-2, 12-3 will not make payment for the items purchased by shopper 22-1.

Next, when the second shopper 22-1 comes to pay, the store clerk 21 operates the product registration device 11 to register the products that the shopper 22-2 will purchase. After completing the registration, the store clerk 21 touches the send button B4. The product registration device 11 then transmits payment information for the shopper 22-2 to each of the payment devices 12-1, 12-2, and 12-3. In each of the payment devices 12-1, 12-2, and 12-3, this payment information is stored in the standby payment buffer 41-1, which has standby 1 as its identification code.

Now, let's assume that the shopper 22-1 is still operating the payment device 12-1 to make a payment. In this case, the start reception screen SC3 is displayed on the touch panel 12g of the payment devices 12-2 and 12-3 where payment processing is not in progress, and the total points and total amount included in the payment information stored in the waiting payment buffer 41-1 are displayed in the display area R6 of this screen. The start reception screen SC3 is not displayed on the touch panel 12g of the payment device 12-1 where payment is in progress.

The store clerk 21 instructs the shopper 22-2 to operate the payment devices 12-1, 12-2, and 12-3 to make the payment. At this time, the store clerk tells the shopper that he or she may operate any of the available payment devices 12-1, 12-2, and 12-3.

Having received the payment instruction, the shopper 22-2 moves to an available payment device, for example, in front of payment device 12-2, and touches the payment start button B5 displayed on the touch panel 12g. At this time, the shopper 22-2 can confirm that the total number of items and the total price of the items he or she will purchase are displayed in the display area R6.

When the shopper 22-2 touches the payment start button B5, the payment information stored in the waiting payment buffer 41-1, which has the identification data "wait 1", is transferred to the processing payment buffer 41-0 in the payment device 12-2. As a result, the payment device 12-2 is able to carry out the payment process related to this payment information, issue a receipt, etc. The shopper 22-1 makes the payment using cash, electronic money, etc.

When the shopper 22-2 touches the payment start button B5, the payment device 12-2 sends a clear command to the other payment devices 12-1, 12-3 installed in the same checkout lane. When the other payment devices 12-1, 12-3 receive this clear command, the payment information stored in the standby payment buffer 41-1, which has standby 1 as its identification data, is cleared. Therefore, the other payment devices 12-1, 12-3 will not make payment for the items purchased by this shopper 22-2.

However, if the store clerk 21 finishes the registration of the products to be purchased by the third shopper 22-3 and touches the send button B4 before the second shopper 22-2 touches the payment start button B5, the payment information for this shopper 22-3 is sent to each of the payment devices 12-1, 12-2, and 12-3. This payment information is stored in the standby payment buffer 41-2, which has standby 2 as an identification code, in each of the payment devices 12-1, 12-2, and 12-3. At this time, the start reception screen SC3 for the second shopper 22-2 is displayed on the touch panel 12g of the free payment device 12-3, so the shopper 22-3 waits for the screen to change. Whether the start reception screen SC3 for the second shopper 22-2 is displayed can be identified by the contents of the display area R6.

After that, when the second shopper 22-2 touches the payment start button B5 on the payment device 12-2, as described above, the payment device 12-2 sends a clear command to the other payment devices 12-1 and 12-3. Also, in the payment device 12-2, the identification code "wait 1" and the payment information in the waiting payment buffer 41-1 are moved to the processing payment buffer 41-0. As a result, in each of the payment devices 12-1, 12-2, and 12-3, the payment information for the third shopper 22-3 is moved from the waiting payment buffer 41-2, which has the identification code "wait 2," to the waiting payment buffer 41-1, which has the identification code "wait 1."

If the first and second shoppers 22-1 and 22-2 have not yet completed their payments, the only one for which payment processing has not yet commenced is the payment device 12-3. Therefore, the start reception screen SC3 is displayed on the touch panel 12g only in the payment device 12-3. The display area R6 of this screen SC3 displays the total points and total amount included in the payment information for the third shopper 22-3.

The store clerk 21 instructs the shopper 22-3 to operate the payment devices 12-1, 12-2, and 12-3 to make the payment. At this time, the store clerk tells the shopper that he or she may operate any of the available payment devices 12-1, 12-2, and 12-3.

Having received the payment instruction, the shopper 22-3 moves to an available payment device 12-3 and touches the payment start button B5 displayed on the touch panel 12g. At this time, the shopper 22-3 can confirm that the total number of items and the total price of the items he or she is purchasing are displayed in the display area R6.

When the shopper 22-3 touches the payment start button B5, the payment information stored in the standby payment buffer 41-1 of standby 1 is transferred to the processing payment buffer 41-0 in the payment device 12-3. As a result, the payment device 12-2 becomes able to carry out the payment process related to this payment information, issue a receipt, etc. The shopper 22-3 makes the payment using cash, electronic money, etc.

In this way, according to the checkout system 10 of this embodiment, the product registration device 11 transmits payment information to all payment devices 12 regardless of the status of each payment device 12. Therefore, in order for the product registration device 11 to monitor the status of each payment device 12, there is no need for an information analysis function that collects and analyzes status information (status) from the payment devices 12.

In addition, the store clerk 21 who operates the product registration device 11 does not have to go through the trouble of searching for an available payment device 12, which improves the work efficiency of the store clerk 21. In addition, the store clerk will not make the mistake of accidentally sending payment information to an unintended payment device 12.

It should be noted that the present invention is not limited to the above-described embodiment.
For example, in the above embodiment, one checkout lane is treated as one unit, and the product registration device 11 arranged in that lane distributes payment information to all payment devices 12 arranged in the same lane. In this regard, for example, two adjacent checkout lanes may be treated as one unit, and the product registration device 11 arranged in each lane may distribute payment information to all payment devices 12 arranged in the adjacent lanes.

In this case, the waiting payment buffers 41-1 to 41-N formed in the RAM 12c of each payment device 12 are divided into two types, one for the first lane and one for the second lane. In addition, the start reception screen SC3 is made to display a payment start button B5 for the first lane and a payment start button B5 for the second lane. Then, the CPU 12a of each payment device 12 stores the payment information distributed from the product registration device 11 of one of the two adjacent checkout lanes (assumed to be the first lane) in the waiting payment buffers 41-1 to 41-N for the first lane, and stores the payment information distributed from the product registration device 11 of the other lane (assumed to be the second lane) in the waiting payment buffers 41-1 to 41-N for the second lane. Then, when the payment start button B5 for the first lane is touched, the CPU 12a transfers the payment information in the waiting payment buffer 41-1, which has the identification code of waiting 1 for the first lane, to the processing payment buffer 41-0. When the payment start button B5 for the second lane is touched, the CPU 12a transfers the payment information in the waiting payment buffer 41-1, which has the identification code waiting 1 for the second lane, to the processing payment buffer 41-0.

By adopting this type of configuration, it is possible to operate in a way that treats two adjacent checkout lanes as one unit.

In the above embodiment, the payment device 12 accepts an instruction to start payment from an operator (shopper) by the shopper 22 making the payment touching the payment start button B5. The means for accepting the instruction input is not limited to this. For example, in the process of Act 26 in FIG. 8, the CPU 12a displays the payment screen SC4 on the touch panel 12g instead of the start reception screen SC3. Then, in the process of Act 27, when the cash button B7 or the electronic money button B8 is touched, the CPU 12a executes the processes of Act 29, Act 30, Act 32, and Act 33. The control program may be modified in this way. In this case, there is an advantage in that the operation of the shopper 22 is simplified because the operation of touching the payment start button B5 is not required.

In the above embodiment, the transaction was described as the buying and selling of goods, but the transaction may not involve the buying and selling of goods. For example, the checkout system of the present invention can also be applied to transactions in which a fee is incurred for the provision of a service, such as a fee for using a facility or a rental fee for a loaned item.

In addition, several embodiments of the present invention have been described, but 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 an input processing device and a plurality of payment devices connected via a network, the input processing device comprising: a generation means for awaiting input of data related to a transaction and generating payment information for the transaction based on the input data; and a distribution means for distributing the payment information in parallel to two or more of the payment devices via the network, and each of the payment devices comprises: a storage means for receiving the payment information distributed from the input processing device via the network and storing it in a memory area; a reception means for receiving an instruction input from an operator to start a payment; a payment means for processing the payment of the payment information stored in the memory area in response to receiving the instruction input; a command means for commanding other payment devices connected via the network to clear the payment information in response to receiving the instruction input; and a clearing means for clearing the payment information stored in the memory area when the clearing command is received from the other payment devices connected via the network.
[2] The checkout system described in appendix [1], characterized in that the storage means stores the payment information in the memory area in order of the earliest time of reception, the payment means processes the payment of the payment information that was received the earliest among the payment information stored in the memory area, and the clearing means clears the payment information that was received the earliest among the payment information stored in the memory area.
[3] A payment device that constitutes a checkout system by being connected via a network to an input processing device having a generation means for awaiting input of data related to a transaction and generating payment information for the transaction based on the input data, and a distribution means for distributing the payment information in parallel to two or more payment devices, the payment device comprising: a storage means for receiving the payment information distributed from the input processing device via the network and storing it in a memory area; a reception means for receiving an instruction input from an operator to start a payment; a payment means for processing the payment of the payment information stored in the memory area in response to receiving the instruction input; a command means for commanding other payment devices connected via the network to clear the payment information in response to receiving the instruction input; and a clearing means for clearing the payment information stored in the memory area when the clear command is received from another payment device connected via the network.
[4] The payment device according to appendix [3], characterized in that the storage means stores the payment information in the memory area in order of earliest reception, the payment means processes the payment of the payment information received earliest among the payment information stored in the memory area, and the clearing means clears the payment information received earliest among the payment information stored in the memory area. [5] An input processing device that is connected to a plurality of payment devices according to appendix [3] or appendix [4] via a network to form a checkout system, comprising: a generation means for waiting for input of data related to a transaction and generating payment information for the transaction based on the input data, and a distribution means for distributing the payment information in parallel to two or more of the payment devices via the network.
[6] A control program for causing an input processing device and a computer of a payment device constituting a checkout system, the control program having a generation means for awaiting input of data related to a transaction and generating payment information for the transaction based on the input data, and a distribution means for distributing the payment information in parallel to two or more payment devices connected via a network, to realize the following functions: receiving the payment information distributed from the input processing device via the network and storing it in a memory area, processing the payment of the payment information stored in the memory area in response to receiving an instruction input from an operator to start payment, instructing other payment devices connected via the network to clear the payment information in response to receiving the instruction input, and clearing the payment information stored in the memory area when the instruction to clear is received from another payment device connected via the network.

10...checkout system, 11...product registration device, 11a...CPU, 11b...ROM, 11c...RAM, 11d...auxiliary memory unit, 11e...drawer opening unit, 11f...scanner, 11g...touch panel, 11h...printer, 11i...card reader/writer, 11j...communication unit, 11k...transmission system, 12...payment device, 12a...CPU, 12b...ROM, 12c...RAM, 12d...auxiliary memory unit, 12e...automatic change machine, 12f...scanner, 12g...touch panel, 12h...printer, 12i...card reader/writer, 12j...communication unit, 12k...transmission system, 31...registered product table, 32...total table, 41-0...processing payment buffer, 41-1 to 41-N...waiting payment buffer.

Claims (6)

An input processing device and a payment device constituting a checkout system, the input processing device generating payment information required for payment of a transaction based on data related to the transaction and transmitting the payment information in parallel to two or more payment devices,
A receiving means for receiving the payment information;
a storage means having a storage area capable of storing a plurality of pieces of the payment information received by the receiving means;
a payment means for processing a payment based on the payment information that was received the earliest among the payment information stored in the storage area when a payment start instruction is input;
a command means for commanding the other payment devices to clear the payment information when a command to start the payment is input;
a shift means for processing a payment based on the payment information that is received with the earliest time by the payment means, or, when a command to clear the payment information is received from another payment device, shifting the multiple payment information stored in the memory area so that the second earliest payment information received becomes the earliest payment information, thereby making the payment information that is received with the earliest time stored in the memory means of each payment device the same payment information;
A payment device comprising: The payment device according to claim 1, wherein when the shifting means is instructed by the other payment device to clear the payment information , the shifting means clears the payment information stored in the storage means that was received earliest, and then shifts the payment information that was received second earliest so that it becomes the earliest payment information. a display means for displaying, on a display unit, a start reception screen including a payment start button for allowing a customer to specify the start of payment in response to receiving the payment information;
Further comprising:
3. The payment device according to claim 1, wherein the input of the payment start button is an instruction input to start the payment. The payment device according to claim 3, wherein the display means switches the screen of the display unit from the start reception screen to a payment screen for the customer to select a payment method when the payment start button is input. a display means for displaying, on a display unit, a payment screen including a payment method designation button for allowing a customer to designate a payment method in response to receiving the payment information;
Further comprising:
3. The payment device according to claim 1, wherein the input of the payment method designation button is an instruction input for starting the payment. A checkout system and an input processing device that generates payment information required for a transaction based on data related to the transaction and transmits the payment information in parallel to two or more payment devices, the checkout system and the payment device include a receiving means that receives the payment information, and a storage means having a storage area capable of storing a plurality of pieces of the payment information received by the receiving means,
a function of processing the payment based on the payment information that was received earliest among the payment information stored in the storage area when a command to start payment is input;
A function of instructing other payment devices to clear the payment information when an instruction to start the payment is input; and
a function of processing payment based on the payment information that was received the earliest, or, when a command to clear the payment information is received from another payment device, shifting the multiple payment information stored in the memory area so that the second earliest payment information received becomes the earliest payment information, thereby making the payment information that was received the earliest and stored in the memory means of each payment device the same payment information;
A control program to achieve this.