JP6754822B2 - Registration device and control program - Google Patents

Description

An embodiment of the present invention relates to a checkout system, a registration device and a payment device included in the system, and a control program for operating a computer as a registration device or a payment device.

As a checkout system for mass retailers, there is a type in which a registration device that generates accounting data necessary for settlement of the transaction for each transaction and a settlement device that processes the settlement of the transaction based on the accounting data are separated. .. The registration device waits for the input of data related to product sales. Then, when the data is input by the operator, the registration device generates accounting data based on the data and transmits the accounting data to the settlement device. The payment device listens for input of payment data for accounting data. Then, when the payment data is input by the operator, the payment device processes the settlement of the transaction based on the accounting data and the payment data. The checkout system of the type in which the registration device and the payment device are separated includes a two-person system in which the registration device and the payment device are operated by separate clerk, and a shopper who operates the registration device and the payment device is a shopper. There is a so-called semi-self system, which is a shared system operated by.

In the case of the semi-self method, if the shopper takes time to operate the payment device, the subsequent shoppers will wait for the payment. In order to avoid such a situation, usually, a plurality of payment devices are connected to one registration device. Then, the registration device monitors the status of each payment device, automatically selects a vacant payment device, and transmits the payment information to the payment device. Alternatively, the registration device displays the status of each payment device on the display, the clerk selects a vacant payment device, and the payment information is transmitted to the payment device.

However, in any case, in order for the registration device to monitor the status of each payment device, the registration device needs an information analysis function that collects and analyzes status information (status) from the payment device.

Japanese Unexamined Patent Publication No. 2013-242839

Problems which an embodiment of the present invention is to solve is to registration device is to provide a registration apparatus and a control program Ru can be eliminated the information analysis function to monitor the status of each payment device.

In one embodiment, the registration device constitutes a plurality of payment devices and a checkout system that perform a product registration process and execute a payment process for the product registered by the registration process. The registration device includes a reception means, a storage means, a transmission means, and a notification means. The reception means accepts the transition from the registration process to the payment process using the payment device. The storage means stores the priority and the information indicating whether or not the payment processing is possible for each of the plurality of payment devices. The transmission means transmits the data stored in the storage means to a plurality of payment devices. Based on the information received from the payment device, the notification means receives a transfer by the reception means , and then notifies the payment device that the payment process is executed from among the plurality of payment devices that have transmitted the stored data. Notify.

The schematic diagram of the checkout system in one Embodiment. A block diagram showing the main circuit configurations of the registration device and the payment device included in the checkout system. The schematic diagram which shows the main data memory area formed in each RAM of the registration apparatus and the payment apparatus. The schematic diagram which shows the main data memory area formed in the RAM of the registration apparatus and the auxiliary storage device. The flow chart which shows the main procedure of the information processing which the CPU of a registration apparatus executes according to a control program. The flow chart which shows the main procedure of the information processing which the CPU of a registration apparatus executes according to a control program. The flow chart which shows the main procedure of the information processing which the CPU of a payment apparatus executes according to a control program. The schematic diagram which shows an example of the registration screen displayed on the touch panel of a registration device. The schematic diagram which shows an example of the accounting confirmation screen displayed on the touch panel of a registration device. The schematic diagram which shows an example of the accounting confirmation screen when the accounting possible response is received. The schematic diagram which shows an example of the accounting confirmation screen when the non-accounting response is received. The schematic diagram which shows an example of the payment method selection screen displayed on the touch panel of a payment device. The schematic diagram which shows an example of the payment screen displayed on the touch panel of a payment device. The schematic diagram which shows an example of the completion screen displayed on the touch panel of a payment device. In the second embodiment, a flow chart showing a main procedure of information processing executed by the CPU of the registration device according to a control program. In the second embodiment, a flow chart showing a main procedure of information processing executed by a CPU of a payment device according to a control program.

Hereinafter, an embodiment of a checkout system in which the registration device can eliminate the information analysis function for monitoring the status of each payment device will be described with reference to the drawings. In this embodiment, a semi-self-type checkout system in which a store clerk operates a registration device and a shopper operates a payment device is illustrated.

[First Embodiment]
FIG. 1 is a schematic diagram of the checkout system 10 according to the first embodiment. The checkout system 10 includes a plurality of registration devices 11 and a payment device 12 having a larger number than the registration devices 11. The registration device 11 and the payment device 12 are arranged in each checkout lane of the store.

In FIG. 1, two registration devices 11 (11-1, 11-2) and six payment devices 12 (12-1, 12-2, 12-3, 12-4, 12-5, 12-) It shows the case where 6) and are arranged in two checkout lanes. In one checkout lane, one registration device 11 (11-1) and three payment devices 12 (12-1, 12-2, 12-3) are arranged. Then, three payment devices 12 (12-1, 12-2, 12-3) arranged in the same checkout lane are grouped with respect to the registration device 11 (11-1). Similarly, one registration device 11 (11-2) and three payment devices 12 (12-4, 12-5, 12-6) are arranged in the other checkout lane. Then, three payment devices 12 (12-4, 12-5, 12-6) arranged in the same checkout lane are grouped with respect to the registration device 11 (11-2). Incidentally, between one registration device 11 and a plurality of payment devices 12 grouped by grouping, data can be simultaneously transmitted from the registration device 11 to each payment device 12. Further, the data transmitted from each payment device 12 is received by the registration device 11 or the payment device 12 in the same group.

It is arbitrary how many checkout systems 10 include the registration device 11 and the payment device 12. Further, the ratio of the number of registration devices 11 and the payment devices 12 arranged in the checkout lane is also arbitrary.

The operator of the registration device 11 is a clerk 21 who plays a role called a checker. The operator of the payment device 12 is a shopper 22 who purchases a product sold at a store. However, the payment device 12 may be operated by the clerk 21.

The registration device 11 is attached to the work table 23 in FIG. The work table 23 has a rectangular top plate. By arranging the plurality of work tables 23 so that the longitudinal directions of the top plates are substantially parallel to each other, a passage (checkout lane) for the shopper 22 is formed.

The registration device 11 includes functions of registering sales products, generating accounting data, transferring accounting data to the settlement device 12, and processing settlement. The registration of the product for sale means that the product purchased by the shopper 22 is registered in the registration device 11 as the product for sale. For example, by scanning the barcode attached to the product with a scanner, the product is registered in the registration device 11 as a product for sale. The accounting data is data related to the accounting of sales products registered as one transaction. The accounting data includes the product code, product name, unit price, quantity, amount, etc., which are the identification codes of the products for sale. The settlement process is to process the settlement of a transaction, which is an act of buying and selling goods, based on accounting data. For payment, cash, credit card, electronic money, etc. are used as payment.

The payment device 12 has a payment processing function. That is, when the accounting data is transferred from the registration device 11, the settlement device 12 processes the settlement of the transaction based on the accounting data.

FIG. 2 is a block diagram showing a main circuit configuration of the registration device 11 and the payment device 12. The registration device 11 and the payment device 12 are both connected to a LAN (local area network) 13 which is a network. Although not shown, a server is connected to the LAN 13. The server has a product database in which product information such as product name and unit price is set in association with the product code of each product.

The registration device 11 and the payment device 12 exchange information via the LAN 13. As the network, another communication network such as the Internet or a wireless LAN may be used instead of the LAN 13. Further, information may be exchanged between the registration device 11 and the payment device 12 via a server.

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

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

The ROM 11b corresponds to the main storage portion of the computer. The ROM 11b stores the operating system. The ROM 11b may store the middleware or application program. The ROM 11b may store data that the CPU 11a refers to when performing various processes.

The RAM 11c corresponds to the main storage portion of the computer. The RAM 11c stores data that the CPU 11a refers to when performing various processes. The RAM 11c is also used as a so-called work area for storing data temporarily used by the CPU 11a for performing various processes.

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

The application program stored in the ROM 11b or the auxiliary storage unit 11d includes a control program described for information processing executed by the registration device 11. The transfer of the registration device 11 is generally performed in a state where the control program is stored in the ROM 11b or the auxiliary storage unit 11d. However, the registration device 11 may be transferred in a state where the control program is not stored in the ROM 11b or the auxiliary storage unit 11d. In this case, the control program is recorded and transferred to a removable recording medium such as a magnetic disk, a magneto-optical disk, an optical disk, or a semiconductor memory. Alternatively, the control program may be transferred via the network, and the control program may be written to the auxiliary storage unit 11d of the separately transferred registration device 11 described above.

The drawer opening unit 11e automatically opens the drawer for accommodating money.
The scanner 11f reads the bar code attached to the product to obtain the product code of the product. As the scanner 11f, various well-known types can be used as they are. The scanner 11f may be compatible with only one of the various well-known types, or may be compatible with a plurality of types. That is, the scanner 11f may include a fixed or handy two-dimensional code scanner. Further, the scanner 11f may include a type of scanner that identifies a product from an image of the product by using an image recognition technique.

Of the two touch panels 11g1 and 11g2, one touch panel 11g1 is for the clerk and the other touch panel 11g2 is for the customer. The touch panels 11g1 and 11g2 both include a display device and a touch sensor. The display device has an arbitrary screen such as a GUI screen. As the display device, a well-known device such as a color LCD can be used. The touch sensor is arranged so as to overlap the display surface of the display device. The touch sensor detects the touch position of the operator on the display surface of the display device and sends the position information to the CPU 11a. A well-known device can be used as the touch sensor.

The touch panel 11g1 for the clerk is provided on the work table 23 so that the display screen faces the work space side of the clerk 21. The customer touch panel 11g2 is provided on the work table 23 so that the display screen faces the aisle side for the shopper 22.

The printer 11h issues a receipt by printing various character strings or images on the receipt paper. As the printer 11h of this type, for example, a thermal printer or a dot impact printer can be used.

The card reader / writer 11i has a function of reading data recorded on the card and a function of writing data to the card. The card may include a membership card called a member's card, a point card, or the like, in addition to a payment card such as a credit card, a debit card, an electronic money card, or a prepaid card. The card reader / writer 11i reads and rewrites the electronic money data (balance, etc.) stored in the electronic money card. The card reader / writer 11i may be a magnetic device, a contact device, or a non-contact device, and may include a plurality of types of devices.

The communication unit 11j performs data communication with a plurality of payment devices 12 connected via the LAN 13. The communication unit 11j can also perform data communication with another registration device 11 via the LAN 13.

The transmission system 11k transmits data exchanged between the CPU 11a, ROM 11b, RAM 11c, auxiliary storage unit 11d, drawer opening unit 11e, scanner 11f, touch panel 11g1, 11g2, printer 11h, card reader / writer 11i, and communication unit 11j. .. As the transmission system 11k, a well-known one including various buses such as a system bus and various interface circuits connecting these buses and each part can be used.

As the hardware of such a registration device 11, for example, an existing POS terminal can be used.

The payment device 12 includes a CPU 12a, a ROM 12b, a RAM 12c, an auxiliary storage unit 12d, an automatic change machine 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 automatic change machine 12e collects the inserted coins and banknotes. Further, the automatic change machine 12e discharges coins and banknotes as change.

Other functions of the CPU 12a, ROM 12b, RAM 12c, auxiliary storage unit 12d, scanner 12f, touch panel 12g, printer 12h, card reader / writer 12i, communication unit 12j, and transmission system 12k are the CPU 11a, ROM 11b, RAM 11c, and auxiliary storage of the registration device 11. It is equivalent to the unit 11d, the touch panel 11g1, 11g2, the printer 11h, the card reader / writer 11i, the communication unit 11j, and the transmission system 11k.

That is, the CPU 12a is connected to the ROM 11b, the RAM 11c, and the auxiliary storage unit 11d via the transmission system 11k to form a computer. Then, the CPU 12a controls each unit in order to realize various operations as the payment device 12 based on the operating system, middleware, and application program stored in the ROM 12b and the RAM 12c.

The application program stored in the ROM 12b or the auxiliary storage unit 12d includes a control program described for information processing executed by the payment device 12. The transfer of the payment device 12 is generally performed with the control program stored in the ROM 12b or the auxiliary storage unit 12d. However, the payment device 12 may be transferred in a state where the control program is not stored in the ROM 12b or the auxiliary storage unit 12d. In this case, the control program is recorded and transferred to a removable recording medium such as a magnetic disk, a magneto-optical disk, an optical disk, or a semiconductor memory. Alternatively, the control program may be transferred via the network, and the control program may be written to the auxiliary storage unit 12d of the separately transferred payment device 12 described above.

As the hardware of such a payment device 12, for example, an existing POS terminal compatible with the self-method can be used.

The checkout system 10 including the registration device 11 and the payment device 12 having such a configuration forms the data memory areas 31 and 32 shown in FIG. 3 in the RAMs 11c and 12c of the registration device 11 and the payment device 12, respectively.

The data memory area 31 is an area for storing data of products sold in one transaction. The data includes each item of product code, product name, unit price, quantity, and amount. The product code is a unique code for individually identifying each product. A product code represented by a bar code is attached to each product, and the registration device 11 can acquire the product code by scanning the bar code with the scanner 11f. The product name and unit price are the product name and the price per item identified by the corresponding product code. The quantity is the number of units sold for the same product, and the amount is the amount of the quantity sold (sales amount). Hereinafter, the data memory area 31 is referred to as a transaction memory. Then, the registration device 11 is represented by the transaction memory 31a, and the payment device 12 is represented by the transaction memory 31b.

The data memory area 32 is an area for storing the total number and the total amount of money. The total number is the total number of units sold stored in the transaction memory 31. The total amount is the total amount of sales stored in the transaction memory 31. Hereinafter, the data memory area 32 is referred to as a total memory. Then, the registration device 11 is represented by the total memory 32a, and the payment device 12 is represented by the total memory 32b.

Further, the checkout system 10 forms the data memory area 41 shown in FIG. 4 in the RAM 11c of the registration device 11, and forms the data memory area 42 in the auxiliary storage unit 11d of the registration device 11.

The data memory area 41 is an area for temporarily storing the product code, product name, unit price, quantity, and amount of one product for sale. Hereinafter, the data memory area 41 is referred to as a temporary buffer 41.

The data memory area 42 is an area for storing information about a plurality of payment devices 12 grouped with respect to the registration device 11. That is, in FIG. 1, the data memory area 42 of the registration device 11 (11-1) stores information about the three payment devices 12 (12-1, 12-2, 12-3). Information about the three payment devices 12 (12-4, 12-5, 12-6) is stored in the data memory area 42 of the registration device 11 (11-2).

The information about the payment device 12 includes a priority number, a payment device ID, an identification name, and response data. The priority number is an integer starting with "1", and the numerical value represents the priority. That is, the priority number "1" represents the first priority, and the priority number "2" represents the second priority. The payment device ID is a unique ID assigned to each payment device 12 in order to individually identify each payment device 12, and is stored in, for example, the ROM 12b. Incidentally, the same registration device ID is stored in the ROM 11b for each registration device 11. The identification name is a unique name set individually for each payment device 12. The operator of the registration device 11 can determine which payment device 12 is indicated from the identification name. The response data indicates whether or not payment processing is possible in the payment device 12 identified by the corresponding payment device ID. For example, the response data "OK" indicates that payment processing is possible. The response data "NG" indicates that the settlement process is impossible. The response data "OK" or "NG" is described for convenience of explanation, and the actual data is not limited to this. For example, the response data is 1-bit flag data, and "1" may indicate that payment processing is possible, and "0" may indicate that payment processing is not possible. Hereinafter, the data memory area is referred to as a group table 42.

In the group table 42, the payment device ID and the identification name of the payment device 12 grouped with respect to the registration device 11 having the group table 42 are stored in advance. At this time, for the priority number "1", the payment device ID and the identification name of the payment device 12 whose priority is set to the first place for the registration device 11 are stored. Similarly, for the priority number "2", the payment device ID and the identification name of the payment device 12 whose priority is set to the second place are stored, and the priority number "3" area has a priority number of 3. The payment device ID and identification name of the payment device 12 set in the place are stored. The priority is set higher as the distance from the registration device 11 is shorter, for example. The priority setting method is not limited to the distance between the registration device 11 and the payment device 12.

5 and 6 are flow charts showing the main procedures of information processing executed by the CPU 11a of the registration device 11 according to the control program. FIG. 7 is a flow chart showing a main procedure of information processing executed by the CPU 12a of the payment device 12 according to the control program. 8 to 11 are schematic views showing various screen examples displayed on the touch panels 11g1 and 11g2 of the registration device 11. 12 to 14 are schematic views showing various screen examples displayed on the touch panel 12g of the payment device 12. Hereinafter, the operation of the checkout system 10 will be described with reference to these figures. The content of the process described below is an example, and various processes capable of obtaining similar results can be appropriately used.

The registration device 11 has a registration mode as one of the operation modes. When the registration device 11 is started in this registration mode, the CPU 11a starts the control process of the procedure shown in the flow chart of FIG. First, the CPU 11a initializes the RAM 11c (Act1). This initialization clears the transaction memory 31a, the total memory 32a, and the temporary buffer 41.

Next, the CPU 11a causes the registration screen SC1 (see FIG. 8) to be displayed on a part of the screen of the touch panel 11g (Act2).

The registration screen SC1 represents the contents of the temporary buffer 41, the transaction memory 31a, and the total memory 32a, and causes the clerk 21 to confirm the implementation status of the registration process. An example of the registration screen SC1 is shown in FIG. The registration screen SC1 includes display areas R1 and R2. In the display area R1, a display column r11 for displaying the product name and unit price of the most recently registered product, a display column r12 for displaying the quantity, and a display column r13 for displaying the amount of money are displayed as one transaction. A display column r14 is formed in which the total number and total amount of each product registered for sale are displayed. In the display area R2, a list of product names, quantities, unit prices, and amounts of products registered for sale prior to the products shown in the display area R1 is formed.

Although not shown, the CPU 11a is a product button for the clerk 21 to specify a product and a subtotal output for the clerk 21 outside the area of the touch panel 11g screen to be the registration screen SC1. It also displays various function buttons such as the subtotal button.

After confirming that the registration screen SC1 is displayed on the touch panel 11g, the clerk 21 recognizes that the product purchased by the shopper 22 can be registered. Then, when the shopper 22 comes to the work table 23 with the purchased product, the clerk 21 operates, for example, the scanner 11f or the product button to sequentially input the product code of the product. Then, when the product codes of all the products have been input, the clerk 21 touches the subtotal button. By the above operation, the registration of the product purchased by one shopper (sales registration of one transaction) is completed.

In response to such a registration operation, the CPU 11a of the registration device 11 executes the following information processing. First, the CPU 11a that displays the registration screen SC1 waits for the input of the product code (Act3). When the product code is input via the scanner 11f or the product button (YES in Act 3), the CPU 11a acquires the product information such as the product name and the unit price associated with the product code and set in the product database. .. Further, the CPU 11a multiplies this unit price by the number of pieces to calculate the amount of money for the number of pieces. The number is a numerical value when the number is placed by the numeric keypad or the like before the product code is input, and is "1" when the number is not placed. In this way, when the CPU 11a generates the product sales data including the product code, the product name, the unit price, the number and the amount of money, the CPU 11a stores the product sales data in the temporary buffer 41 (Act 4). At this time, if the product sales data has already been stored in the temporary buffer 41, the CPU 11a moves the stored product sales data to the transaction memory 31, and then stores the new product sales data in the temporary buffer 41. Store in.

The CPU 11a adds the number and amount of money stored in the temporary buffer 41 to the total memory 32a. Then, the CPU 11a updates the registration screen SC1 so that the contents of the temporary buffer 41 and the total memory 32a are displayed in the display area R1 and the contents of the transaction memory 31a are displayed in the display area R2 (Act 5).

After updating the registration screen SC1, the CPU 11a confirms whether or not the next product code has been input (Act 6). If the product code is not entered (NO in Act 6), the CPU 11a confirms whether or not the subtotal button has been touched (Act 7). When the subtotal button is not touched (NO in Act7), the CPU 11a confirms whether or not the product code has been input again (Act6). Thus, the CPU 11a waits for the product code to be input or the subtotal button to be touched as Act 6 and Act 7. When the CPU 11a confirms the occurrence of another event such as another operation being performed in this standby state, the CPU 11a shifts to the process according to the occurrence event. Such an operation is the same in other standby states.

When the product code is input in the standby state of Act6 and Act7 (YES in Act6), the CPU 11a proceeds to the process of Act4. Then, the CPU 11a repeats the subsequent processing in the same manner as described above.

If the subtotal button is touched in the standby state of Act6 and Act7 (YES in Act7), the CPU 11a executes the processing of Act8 and Act9. The processing procedure of Act8 and Act9 is not limited to this order. The order may be changed.

In Act 8, the CPU 11a moves the product sales data stored in the temporary buffer 41 to the transaction memory 31. Then, the CPU 11a generates accounting data with the data of the transaction memory 31a and the data of the total memory 32a (generation means). At this time, the CPU 11a generates accounting data in a text file format. In Act9, the CPU 11a causes the accounting confirmation screen SC2 (see FIG. 9) to be displayed on a part of the screen of the touch panel 11g.

An example of the accounting confirmation screen SC2 is shown in FIG. The accounting confirmation screen SC2 includes a display area R3 and buttons B1, B2, B3, and B4. The display area R3 displays the total number of the total memory 32a, the total amount, and the like. Buttons B1 and B2 are a subtotal discount button B1 and a subtotal discount button B2 for the clerk 21 to specify that a discount or discount is applied to the total amount. Button B3 is a back button B3 for the clerk 21 to specify that a part of the screen area of the touch panel 11g is returned to the registration screen SC1. Button B4 is an accounting button B4 for the clerk 21 to instruct the clerk 21 to complete the registration of the product for one transaction and shift to accounting.

The CPU 11a displaying the accounting confirmation screen SC2 confirms whether or not the accounting button has been input (Act10). When the checkout button is not input (NO in Act10), the CPU 11a confirms whether or not the return button B3 is input (Act11). When the back button B3 is not input (NO in Act 11), the CPU 11a again confirms whether or not the accounting button has been input (Act 10). Thus, the CPU 11a waits for the accounting button B4 or the back button B3 to be input as Act10 and Act11.

The clerk 21 who confirms the accounting confirmation screen SC2 confirms whether or not the product purchased by the shopper 22 remains registered. If it remains, the clerk 21 touches the back button B3. If there are no remaining items, the clerk 21 touches the checkout button B4.

When the back button B3 is input in the standby state of Act10 and Act11 (YES in Act11), the CPU 11a returns a part of the screen area of the touch panel 11g to the registration screen SC1 (Act12). After that, the CPU 11a proceeds to the process of Act6, and the subsequent processes are repeated in the same manner as described above.

When the accounting button B4 is touched in the standby state of Act10 and Act11 (YES in Act10), the CPU 11a proceeds to the process of Act13 in FIG. That is, the CPU 11a instructs the communication unit 11j to collectively transmit the accounting data in the text file format to the plurality of grouped payment devices 12 (Act 13). In response to this command, the communication unit 11j sends the accounting data in the text file format on the LAN 13 with each payment device ID set in the group table 42 as the transmission destination and the registration device ID stored in the ROM 11b as the transmission source. Send to. This accounting data is received by a plurality of payment devices 12 whose transmission destination payment device ID matches the payment device ID stored in the ROM 12b. Here, the CPU 11a cooperates with the communication unit 11j to form a first transmission means.

When the CPU 12a of each payment device 12 receives the accounting data in the text file format via the communication unit 12j, whether or not the payment device ID added to the data as the transmission destination matches the payment device ID stored in the ROM 12b. Check if. If they do not match, the CPU 12a discards the accounting data. If they match, the CPU 12a takes in the accounting data and stores it in a predetermined area of the RAM 12c in the text file format. Then, the CPU 12a starts the reception interrupt process specifically shown in FIG. 7. Here, the CPU 12a cooperates with the communication unit 12j to form a receiving means.

When the reception interrupt process is started, the CPU 12a first checks the busy flag F (Act31). The busy flag F is 1-bit data that is set to "1" while the CPU 12a processes the settlement of the transaction based on the accounting data and is reset to "0" when the processing is completed, and is stored in the RAM 12c. There is. In this way, while the busy flag F is set, the payment device 12 is executing the payment process. Therefore, the settlement device 12 cannot process the settlement of a new transaction.

When the busy flag F is reset (YES in Act31), that is, when the payment device 12 is in a state where the payment processing of a new transaction can be executed, the CPU 12a notifies that the payment processing is possible. The communication unit 12j is instructed to transmit the accountable (OK) response to the registration device 11 of the accounting data transmission source (Act 32). In response to this command, the communication unit 12j sends the command data of the accountable response on the LAN 13 with the registration device ID set as the source of the accounting data as the transmission destination and the settlement device ID stored in the ROM 12b as the transmission source. Send. This command data is received by the registration device 11 whose transmission destination registration device ID matches the registration device ID stored in the ROM 11b.

When the busy flag F is set (NO in Act31), that is, when the settlement device 12 is in a state where the settlement process of a new transaction cannot be executed, the CPU 12a indicates that the settlement process is impossible. The communication unit 12j is instructed to transmit the non-accounting (NG) response to be notified to the registration device 11 of the accounting data transmission source (Act 33). In response to this command, the communication unit 12j transmits the command data of the non-accounting response to the transmission destination, the registration device ID set as the transmission source of the accounting data, and the payment device ID stored in the ROM 12b as the transmission source, on the LAN 13. Send. This command data is received by the registration device 11 whose transmission destination registration device ID matches the registration device ID stored in the ROM 11b.
Here, the CPU 12a cooperates with the communication unit 12j to form a response means.

In Act 13 of FIG. 6, the CPU 11a of the registration device 11 that has transmitted the accounting data confirms whether or not the command data of the accountable response or the non-accountable response from the settlement device 12 is received as Act 14. When the command data is not received (NO in Act 14), the CPU 11a confirms whether or not the elapsed time since the accounting data is transmitted as Act 15 has reached the preset timeout time. The timeout time is set to a time sufficient to receive the above command data. Command data of an accountable response or an unaccountable response is transmitted from the plurality of settlement devices 12 that have received the accounting data. At this time, data collision may occur, so the timeout time is set in consideration of data collision.

If the elapsed time has not reached the timeout time (NO in Act 15), the CPU 11a confirms whether or not the command data has been received again (Act 14). Thus, as Act 14 and Act 15, the CPU 11a receives the command data of the accountable response or the non-accountable response, or waits for the elapsed time to reach the timeout time.

When the command data of the accountable response or the unaccountable response is received (YES in Act 14), the CPU 11a writes the response data in the group table 42 based on the command data as Act 16. That is, the CPU 11a detects the payment device ID that is the transmission source from the received command data. Then, the CPU 11a writes "OK" to the response data associated with the settlement device ID in the group table 42 when the command data is an accountable response, and "NG" when the command data is an unaccountable response. To write.

The CPU 11a that has written the response data in the group table 42 determines whether or not the response is completed as Act17. When the command data of the accountable response or the non-accountable response is received from all the settlement devices 12 that have transmitted the accounting data, the CPU 11a determines that the response is completed. If the command data of the accountable response or the non-accountable response is not received from at least one payment device 12, the CPU 11a determines that the response is incomplete.

If the response is not completed (NO in Act17), the CPU 11a returns to Act14 and waits for the command data to be received or the elapsed time to reach the timeout time.

When the response is completed (YES in Act17) or when the elapsed time reaches the timeout time (YES in Act15), the CPU 11a creates data indicating the response result from the payment device 12 as Act18. Specifically, the CPU 11a reads the priority number, the settlement device ID, and the response data from the group table 42 in ascending order of priority number, and arranges each group in ascending order of priority number, for example, data indicating the response result. And. The CPU 11a instructs the communication unit 11j to collectively transmit the data indicating the response result to the plurality of grouped payment devices 12. In response to this command, the communication unit 11j uses all the payment device IDs set in the group table 42 as the transmission destination, the registration device ID stored in the ROM 11b as the transmission source, and data indicating the response result on the LAN 13. Send. The data indicating the response result is received by a plurality of payment devices 12 whose transmission destination payment device ID matches the payment device ID stored in the ROM 12b. Here, the CPU 11a cooperates with the communication unit 11j to form a second transmission means.

The CPU 12a of the settlement device 12 that has transmitted the command data of the accountable response or the non-accountable response as the process of Act 32 or Act 33 waits for the data indicating the response result from the registration device 11 as Act 34. When the data indicating the response result is received (YES in Act34), the CPU 12a searches the data as Act35 for the payment device ID that satisfies the execution condition of the payment process.

Specifically, the CPU 12a first detects the set having the smallest priority number from the data indicating the response result. Then, the CPU 12a confirms whether or not the response data of this set is the data of the accountable response "OK". When the data of the accountable response is "OK", the CPU 12a sets the settlement device ID of this set as the settlement device ID that satisfies the execution condition of the settlement process. On the other hand, when the non-accountable response data is "NG", the CPU 12a detects the set having the next smallest priority number. Then, the CPU 12a confirms whether or not the response data of this set is the data of the accountable response "OK". When the data of the accountable response is "OK", the CPU 12a sets the settlement device ID of this set as the settlement device ID that satisfies the execution condition of the settlement process. On the other hand, in the case of non-accountable response data "NG", the CPU 12a detects a set having the next smallest priority number.

In this way, the CPU 12a examines the response data for each group in ascending order of priority number, and sets the payment device ID of the group that first detects the accountable response data "OK" as the payment device ID that satisfies the execution condition of the payment process. And. If all the response data up to the set with the highest priority number is the non-accountable response data "NG", the CPU 12a cannot detect the settlement device ID that satisfies the execution condition of the settlement process.

When the search for the payment device ID satisfying the execution condition of the payment process is completed, the CPU 12a confirms as Act 36 whether the payment device ID matches the payment device ID stored in the ROM 12b. If the payment device IDs do not match, or if a payment device ID that satisfies the payment processing execution conditions cannot be detected (NO in Act36), the CPU 12a ends the reception interrupt processing.

On the other hand, when the payment device ID satisfying the execution condition of the payment processing matches the payment device ID stored in the ROM 12b (YES in Act36), the CPU 12a executes the processing of Act37, Act38, Act39, Act40 and Act41. To do. The processing procedures from Act 37 to Act 39 are not limited to this order. The order may be changed.

In Act37, the CPU 12a sets the busy flag to "1".
In Act38, the CPU 12a instructs the communication unit 12j to transmit a command notifying the accounting execution to the registration device 11 which is the source of the data indicating the response result. In response to this command, the communication unit 12j sends the command data of the accounting execution notification whose transmission destination is the registration device ID set as the transmission source of the data indicating the response result and whose transmission source is the payment device ID stored in the ROM 12b. It is transmitted on LAN13. This command data is received by the registration device 11 whose transmission destination registration device ID matches the registration device ID stored in the ROM 11b.

In Act 39, the CPU 12a converts the text file format accounting data stored in the predetermined area of the RAM 12c into the file format accounting data used in the settlement process. Specifically, the CPU 12a converts the accounting data in the text file format into the data in the DAT file format (data file having the extension ".dac"). When the accounting data becomes DAT file format data, the settlement device 12 is in a state where settlement can be started.

As described above, in the present embodiment, the DAT file format is defined as the file format used in the payment processing, and the text file format is defined as the file format other than the file format used in the payment processing. The file format used in the settlement process is not limited to the DAT file format. Needless to say, file formats other than the file formats used in payment processing are not limited to text file formats.
Here, the CPU 12a constitutes a determination means and a processing means by processing Act35 to Act38.

In Act40, the CPU 12a executes the settlement process based on the accounting data converted into the DAT file format. The payment process will be described later.
In Act41, the CPU 12a resets the busy flag F to “0”. With the above, the CPU 12a ends the reception interrupt processing.

In Act 18 of FIG. 6, the CPU 11a of the registration device 11 that has transmitted the data indicating the response result confirms whether or not the command data of the accounting execution notification has been received as Act 19. When the command data is not received (NO in Act 19), the CPU 11a confirms whether or not the elapsed time from transmitting the data indicating the response result as Act 20 has reached the preset timeout time. The timeout time is set to a time sufficient to receive the command data of the accounting execution notification. The plurality of payment devices 12 that have received the data indicating the response result determine whether or not to carry out the payment processing. Then, after this determination, the command data of the accounting execution notification is transmitted from any one of the settlement devices 12 that executes the settlement process. The time-out time is set in consideration of the time required for the payment device 12 to perform the payment processing to be determined.

When the elapsed time has not reached the timeout time (NO in Act 20), the CPU 11a confirms whether or not the command data of the accounting execution notification has been received again (Act 19). Thus, as Act 19 and Act 20, the CPU 11a waits for the command data of the accounting execution notification to be received or the elapsed time to reach the timeout time.

Upon receiving the command data of the accounting execution notification (YES in Act 19), the CPU 11a searches the group table 42 as Act 21 and sets the identification name stored in association with the settlement device ID that is the source of the command data. read out. Then, as shown in FIG. 10, the CPU 11a causes a part of the area R4 of the accounting confirmation screen SC2 to display a message indicating that the payment device 12 having this identification name is ready for payment processing. Here, the CPU 11a configures the notification means by the processing of Act21.

On the other hand, when the elapsed time reaches the timeout time (YES in Act 20), there is no payment device 12 that executes the payment process. In this case, as Act22, the CPU 11a displays a message indicating that the accounting data could not be transmitted in a part of the area R5 of the accounting confirmation screen SC2 as shown in FIG. After that, the CPU 11a executes the transmission disabling process.

For example, the non-transmission processing waits for the accounting button B4 to be input again, and if it is input, the processing after Act 13 is executed again. In this case, the clerk who confirms the message touches the checkout button B4.

In the non-transmission processing, for example, the accounting data is transmitted to the server with a unique identification code attached, and the printer 11h is driven to issue an accounting ticket on which a barcode indicating the identification code is printed. In this case, the clerk who confirms the message hands the accounting ticket to the shopper. For example, the shopper has the scanner 12f of the payment device 12 prepared at a place other than the chuck out lane read the barcode of the accounting ticket. Then, the CPU 12a of the payment device 12 acquires the accounting data attached with the identification code obtained from the barcode from the server. Then, the CPU 12a executes the processes of Act 37, Act 39, Act 40, and Act 41 of FIG. 7 based on the accounting data.

In this way, the clerk 21 registers the product purchased by the shopper 22 with the registration device 11. Then, when the registration is completed, the clerk 21 touches the checkout button B4 on the checkout confirmation screen SC2. Then, the accounting data necessary for the settlement of the transaction with the shopper 22 is created in the text file format. Then, this accounting data is transmitted from the registration device 11 to the plurality of payment devices 12 grouped together.

The settlement device 12 that has received the accounting data in the text file format determines whether or not the settlement processing is possible. Then, the settlement device 12 capable of the settlement process sends an accountable response to the registration device 11. A non-accounting response is transmitted from the payment device 12 that cannot perform payment processing to the registration device 11.

In the registration device 11, the response data in the group table 42 is updated based on the accountable response or the non-accountable response from the settlement device 12. Then, the data indicating the response result created by the priority number, the payment device ID, and the response data of the group table 42 is transmitted from the registration device 11 to the plurality of payment devices 12 grouped together. Based on the data showing the response result, one of the payment devices 12 that satisfies the payment processing execution condition is determined. Specifically, it is determined that the settlement device 12 having the smallest priority number among the settlement devices 12 that sent the accountable response when the accounting data is received satisfies the execution condition of the settlement process.

For example, in the example of the group table 42 shown in FIG. 4, if the settlement device A can perform the settlement process when receiving the accounting data, even if the other settlement devices B and C can perform the settlement process. It is the payment device A that satisfies the execution conditions of the payment processing. On the other hand, when the payment device A is unable to perform the payment processing, and if the payment device B is capable of the payment processing, it is the payment device B that satisfies the execution condition of the payment processing. Further, when the payment device B is also unable to perform the payment processing, if the payment device C is capable of the payment processing, it is the payment device C that satisfies the execution condition of the payment processing. If the payment device C is also unable to perform the payment processing, the payment device that satisfies the execution conditions of the payment processing is not determined. In this case, since the registration device 11 times out, the transmission disabling process is executed.

When the settlement device 12 that satisfies the execution condition of the settlement process is determined, the settlement device 12 transmits a command for notifying the registration device 11 of the execution of the accounting. By this command, in the registration device 11, along with the identification name of the settlement device 12, a message indicating that the accounting is ready is displayed in a part area R4 of the accounting confirmation screen SC2. Therefore, the clerk guides the shopper to perform the checkout with the payment device 12 specified from the identification name.

The shopper 22 who is instructed by the clerk 21 to perform accounting with any of the payment devices 12 moves to the location of the payment device 12. At this time, the payment device 12 has started the payment process. When the payment process starts, the payment device 12 displays the payment method selection screen SC3 (see FIG. 12) on a part of the screen of the touch panel 12g.

FIG. 12 shows an example of the payment method selection screen SC3. The payment method selection screen SC3 includes display areas R11 and R12 and buttons B11 and B12. The display area R11 displays operation guidance for the shopper 22 who operates the payment device 12. The display area R12 displays the total number and the total amount of money stored in the total memory 32b. The button B11 is a payment method button B11 for the shopper to specify one of the payment methods from the plurality of payment methods. The button B12 is a clerk call button B13 for the shopper 22 to specify to call the clerk 21.

In the present embodiment, cash, credit card, and electronic money are exemplified as payment methods, but the payment methods are not limited to these. Other payment methods may be added. Moreover, any payment method may be omitted.

The shopper 22 who confirms the payment method selection screen SC3 determines the payment method of the price and touches the payment method button B11. When the payment method button B11 is touched, the payment device 12 displays the payment screen SC4 (see FIG. 13) of the payment method selected by the payment method button B11 on a part of the screen of the touch panel 12g.

An example of the payment screen SC4 is shown in FIG. FIG. 13 is a payment screen SC4 when cash is selected as the payment method. The payment screen SC4 includes display areas R13, R14 and button B13. The display area R13 displays operation guidance for the shopper 22 who operates the payment device 12. The display area R14 displays the total amount, the input amount, and the remaining amount. The button B13 is a settlement button B13 for the shopper who has finished inserting cash to specify the execution of the settlement.

A shopper who selects cash as the payment method inserts cash into the automatic change machine 12e. Then, when the total amount of cash or more is inserted, the settlement button B13 is touched. When the settlement button B13 is touched, the settlement device 12 executes the settlement process by the selected payment method. Since such payment processing is well known, detailed description thereof will be omitted.

When the payment process is completed, the payment device 12 displays the completion screen SC5 (see FIG. 14) on a part of the screen of the touch panel 12g.

FIG. 14 shows an example of the completion screen SC5 for cash payment. The completion screen SC5 includes display areas R15, R16, and R17. The display area R15 displays operation guidance for the shopper 22 who operates the payment device 12. The display area R16 displays a guide image. The guide image is an image that guides the shopper 22 to the receipt issuing port and the change payment exit. Therefore, the shopper can easily know the place where the receipt is issued and the place where the change is paid out from this guide image. The display area R16 displays the amount of change. Therefore, the shopper can know the change amount from the data of the display area R16.

The shopper who confirms the completion screen SC8 receives the receipt and the change according to the guide image. In response to this, in the settlement device 12, the busy flag F is reset to "0", and the accounting standby state is set.

As described above, according to the present embodiment, the registration device 11 may transmit accounting data to a plurality of grouped payment devices 12 regardless of the state of each payment device 12. Therefore, the information analysis function for the registration device 11 to monitor the state of each payment device 12 becomes unnecessary.

[Second Embodiment]
Next, the second embodiment will be described.
Note that FIGS. 1 to 5 and 8 to 14 used in the first embodiment are applied as they are to the second embodiment, and the description thereof will be omitted except that they are different from the first embodiment.

One of the differences between the second embodiment and the first embodiment is that a priority number memory is formed in the auxiliary storage unit 12d of each payment device 12. The priority number assigned to the payment device 12 is stored in the priority number memory. For example, in the group table 42 shown in FIG. 4, the priority number "1" is stored in the priority number memory of the payment device A, and the priority number "2" is stored in the priority number memory of the payment device B. The priority number "3" is stored in the priority number memory of the payment device C.

Another difference between the second embodiment and the first embodiment is that the CPU 11a of the registration device touches the accounting button B4 in the standby state of Act 10 and Act 11, and the accounting data in text file format is used as Act 13. Is a procedure of information processing after collectively transmitting the above to a plurality of grouped payment devices 12. The processing procedure from Act 1 to Act 13 is the same as that in the first embodiment. Further, a part of the reception interrupt processing executed by the CPU 12a of the settlement device 12 that has received the accounting data is also different from the first embodiment. Hereinafter, points different from the first embodiment will be described with reference to FIGS. 15 and 16.

FIG. 15 is a flow chart showing a main procedure of information processing executed after the accounting button B4 is touched in the second embodiment. That is, after instructing the communication unit 11j to transmit the accounting data as Act3, the CPU 11a omits the processing of Act14 to Act18. That is, the CPU 11a waits for the elapsed time from receiving the command data of the accounting execution notification from any of the settlement devices 12 as Act 19 or transmitting the accounting data as Act 20 to reach a preset timeout time. When the command data of the accounting execution notification is received, the CPU 11a executes the process of Act 21 as in the first embodiment. Even when the elapsed time from the transmission of the accounting data reaches the timeout time, the CPU 11a executes the process of Act22 as in the first embodiment.

FIG. 16 is a flow chart showing a main procedure of reception interrupt processing executed by the CPU 12a of the settlement device 12 that has received the accounting data according to the control program in the second embodiment. The same reference numerals are given to the parts common to the first embodiment.

That is, when the reception interrupt process is started, the CPU 12a checks the busy flag F as Act31. Here, when the busy flag F is set (NO in Act31), that is, when the settlement device 12 is in a state where the settlement process of a new transaction cannot be executed, the CPU 12a ends this reception interrupt process. To do.

On the other hand, when the busy flag F is reset (YES in Act31), that is, when the settlement device 12 is in a state where the settlement process of a new transaction can be executed, the CPU 12a sets the priority number memory as Act51. Read the priority number stored in. Then, the CPU 12a instructs the communication unit 12j to transmit an accountable response notifying that the settlement process is possible together with this priority number to the other settlement device 12.

In response to this command, the communication unit 12j sets a payment device ID that does not match the payment device ID stored in the ROM 12b among the payment device IDs set as the destination of the accounting data as the transmission destination, and stores the payment device ID in the ROM 12b. The command data of the accountable response with the payment device ID as the transmission source is transmitted on the LAN 13. The command data also includes a priority number stored in the priority number memory. The command data is received by the payment device 12 whose transmission destination payment device ID matches the payment device ID stored in the ROM 12b.
Here, the CPU 12a cooperates with the communication unit 12j to form a third transmission means.

The CPU 12a of the settlement device 12 that has transmitted the accountable response confirms whether or not the accountable response from the other settlement device 12 has been received as Act 52. When the accountable response is not received (NO in Act52), the CPU 12a confirms as Act53 whether or not the elapsed time from receiving the accounting data has reached the preset timeout time. The time-out time is set to a sufficient time for the settlement device 12 that has received the accounting data to send an accountable response to another settlement device 12. From the plurality of payment devices 12 that have received the accounting data, the command data of the accounting response may be transmitted at substantially the same time. Therefore, the timeout time is set in consideration of data collision.

When the elapsed time has not reached the timeout time (NO in Act53), the CPU 11a confirms whether or not the command data has been received again (Act52). Thus, as Act 52 and Act 53, the CPU 11a waits for the command data of the accountable response to be received or the elapsed time to reach the timeout time.

When the command data of the accountable response is received (YES in Act 52), the CPU 12a compares the priority number included in the command data with the priority number stored in the priority number memory as Act 54. As a result, when the priority number included in the command data is larger than the priority number stored in the priority number memory (NO in Act54), the settlement device 12 of the command data transmission source has a higher priority than itself. Low. In this case, the CPU 12a returns to Act 52 and receives the command data of the accountable response again or waits for the elapsed time to reach the timeout time.

On the other hand, when the priority number included in the command data is smaller than the priority number stored in the priority number memory (NO in Act54), the settlement device 12 of the command data transmission source is larger than itself. High priority. In this case, the CPU 12a ends this reception interrupt process.

When the elapsed time reaches the timeout time (YES in Act53) without receiving the command data of the accountable response including the priority number smaller than the priority number stored in the priority number memory, the CPU 12a is set to the first. The processes of Act 37 to Act 41 described in the embodiment are executed.

As described above, also in the second embodiment, the registration device 11 simultaneously transmits the accounting data to the grouped payment devices 12. On the other hand, each payment device 12 that has received the accounting data determines whether or not the payment processing is possible. Then, from the payment device 12 capable of payment processing, command data of the accountable response is transmitted to another payment device 12. This command data includes a priority number stored in the priority number memory of the payment device 12. On the other hand, no command data is transmitted from the payment device 12 that cannot perform payment processing.

Therefore, if there is only one payment device 12 capable of payment processing, the payment device 12 times out in Act 53, so that the payment device 12 is determined as one that satisfies the execution condition of the payment processing.

If there are two or more payment devices 12 capable of payment processing, the payment device 12 having the smallest priority number stored in the priority number memory is one that satisfies the payment processing execution conditions. Is determined as.

A command for notifying the registration device 11 of the execution of accounting is transmitted from the payment device 12 that satisfies the execution conditions of the payment process. By this command, in the registration device 11, along with the identification name of the settlement device 12, a message indicating that the accounting is ready is displayed in a part area R4 of the accounting confirmation screen SC2. Therefore, the clerk guides the shopper to perform the checkout with the payment device 12 specified from the identification name. The shopper 22 who is instructed by the clerk 21 to perform accounting with any of the payment devices 12 moves to the location of the payment device 12 and makes a payment.

Therefore, also in the second embodiment, the information analysis function for the registration device 11 to monitor the state of each payment device 12 can be eliminated.

The present invention is not limited to the above embodiment.
For example, in the above embodiment, the payment devices 12 arranged in the same checkout lane are grouped with respect to the registration device 11, but the payment devices 12 arranged in the other checkout lanes are also grouped. May be good.

Further, when a plurality of payment devices 12 are collectively arranged at a position different from the checkout lane, for example, a plurality of payment devices 12 located within a predetermined distance from the registration device 11 may be grouped.

Further, it goes without saying that the screens SC1, SC2, SC3, SC4, and SC5 illustrated and described in the above embodiment are merely examples and are not limited to the layout shown.

In addition, 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 embodiments, and various omissions, replacements, and changes can be made without departing from the gist of the invention. These embodiments and modifications thereof are included in the scope and gist of the invention, and are also included in the scope of the invention described in the claims and the equivalent scope thereof.
Hereinafter, the inventions described in the claims of the original application of the present application will be added.
[1] Checkout made by connecting a registration device that generates accounting data necessary for settlement of the transaction for each transaction and a plurality of settlement devices that process the settlement of the transaction based on the accounting data via a network. In the system, is the registration device capable of processing the payment from the first transmission means for transmitting the accounting data to at least two or more payment devices and the two or more payment devices that have transmitted the accounting data? A second transmission means that listens for a response of whether or not and transmits data indicating the response result to the two or more payment devices, and the payment from the two or more payment devices that transmit the data indicating the response result. The payment device is provided with a notification means that waits for a notification to execute the process and notifies the payment device that has received the notification when the notification is received from any one of the payment devices. The payment device is the registration device. In response to receiving the accounting data from, a response means for returning a response as to whether or not the settlement can be processed to the registration device, and in response to receiving data indicating the response result from the registration device. , The determination means for deciding whether or not to execute the settlement process based on the data, and when it is decided to execute the settlement process, the registration device is notified to that effect and the settlement is made. A checkout system characterized by having a processing means to get started.
[2] The first transmission means transmits the accounting data to the two or more payment devices in a file format other than the file format used in the payment processing, and the processing means is a file used in the payment processing. Addendum [1], characterized in that the accounting data sent from the registration device in a file format other than the format is converted into a file format used in the settlement processing so that the settlement can be started. The checkout system described.
[3] A first method of transmitting the accounting data to a generation means for generating accounting data necessary for settlement of the transaction for each transaction and at least two or more settlement devices for processing the settlement of the transaction based on the accounting data. Waits for a response from the transmission means of the above and the two or more settlement devices that have transmitted the accounting data as to whether or not the settlement can be processed, and transmits the data indicating the response result to the two or more settlement devices. When the notification of the execution of the payment processing is received from the transmission means 2 and the two or more payment devices that have transmitted the data indicating the response result, and the notification is received from any one of the payment devices, the notification is received. A registration device including a notification means for notifying the payment device that has been notified.
[4] A receiving means for receiving the accounting data via a network from a registration device that generates accounting data necessary for settlement of the transaction for each transaction, and a receiving means for receiving the accounting data, and the settlement A response means that returns a response as to whether or not processing is possible to the registration device, and whether or not to execute the settlement process based on the data indicating the response result received from the registration device. It is characterized in that it is provided with a determination means for determining the above and a processing means for notifying the registration device to that effect when it is determined to execute the settlement process so that the settlement can be started. Payment device.
[5] In response to receiving the accounting data from a registration device that generates accounting data necessary for settlement of the transaction for each transaction to a computer provided with a receiving means for receiving the accounting data via a network. , A function of returning a response as to whether or not the settlement process is possible to the registration device, and executing the settlement process based on the data indicating the response result received from the registration device. A control program for realizing a function of determining whether or not the payment is made, and a function of notifying the registration device to that effect when it is decided to execute the payment processing so that the payment can be started. ..

11 ... Registration device, 12 ... Payment device, 11a, 12a ... CPU, 11b, 12b ... ROM, 11c, 12c ... RAM, 11d, 12d ... Auxiliary storage unit, 11e ... Drawer opening unit, 12e ... Automatic change machine, 11f, 12f ... Scanner, 11g1,11g2,12g ... Touch panel, 11h, 12h ... Printer, 11i, 12i ... Card reader / writer, 11j, 12j ... Communication unit, 11k, 12k ... Transmission system, 13 ... LAN, 31 (31a, 31b) ... transaction memory, 32 (32a, 32b) ... total memory, 41 ... temporary buffer, 42 ... group table.

Claims (4)

It is a registration device that constitutes a checkout system and a plurality of payment devices that perform product registration processing and execute payment processing for products registered by the registration processing.
A reception means that accepts the transition from the registration process to the payment process in the payment device, and
A storage means for storing a priority and information indicating whether or not the payment processing is possible for each of the plurality of payment devices.
A transmission means for transmitting data stored in the storage means to the plurality of payment devices, and
Based on the information received from the payment device, after receiving the transition by the reception means, a notification to the effect that the payment process is executed from among the plurality of payment devices that have transmitted the data stored in the storage means is notified. Notification means to notify the payment device that was there ,
A registration device comprising. The registration device according to claim 1, wherein the receiving means is a means for receiving an input operation of an image displayed on a display unit. The registration device according to claim 2, wherein the notification means notifies by displaying information indicating a payment device that performs the payment processing on the display unit. To the computer of the registration device that configures the checkout system and a plurality of payment devices that perform the product registration process and execute the payment process of the product registered by the registration process.
A function that accepts the transition from the registration process to the payment process in the payment device,
A function of storing a priority and information indicating whether or not the payment processing is possible for each of the plurality of payment devices.
A function of transmitting the stored data to the plurality of payment devices, and
Based on the information received from the payment device, after accepting the transition, the payment device that has been notified to execute the payment process is notified from among the plurality of payment devices that have transmitted the stored data. function,
Control program to realize.