JP7200314B2 - Payment 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 this system, and a control program for causing a computer to function 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 each transaction for each transaction and a settlement device that processes settlement of the transaction based on the accounting data are separated. . The registration device waits for input of data relating to product sales. Then, when data is input by the operator, the registration device generates accounting data based on the data, and transmits this accounting data to the settlement device. The settlement device waits for input of payment data for accounting data. Then, when the payment data is entered by the operator, the payment device processes settlement of the transaction based on the accounting data and the payment data. Such a checkout system 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 staff, and a checkout system in which the registration device is operated by the staff and the payment device is operated by the shopper. There is a so-called semi-self system, a division system operated by

In the case of the semi-self system, if a shopper takes time to operate the payment device, the following shoppers will have to wait for the payment. In order to avoid such a situation, a plurality of settlement devices are usually connected to one registration device. Then, the registration device monitors the status of each payment device, automatically selects an available payment device, and transmits payment information to that payment device. Alternatively, the registration device displays the status of each payment device on the display, and the clerk selects an available payment device and transmits the payment information to that payment device.

However, in any case, the registration device needs an information analysis function for collecting and analyzing status information (status) from the payment devices so that the registration device can monitor the status of each payment device.

JP 2013-242839 A

The problem to be solved by the embodiments of the present invention is to provide a registration device and its control program that can eliminate the information analysis function for the registration device to monitor the status of each settlement device.

In one embodiment, the payment device comprises first receiving means, responding means, second receiving means, determining means and processing means . The first receiving means receives accounting data via a network from a registration device that generates accounting data necessary for settlement of transactions . The response means transmits a response to the registration device as to whether or not settlement processing is possible . The second receiving means receives from the registration device data including the priority set for each of the plurality of payment devices and information indicating whether or not the payment transmitted from the plurality of payment devices to the registration device can be processed . The judging means judges , based on the data received from the registration device, whether the settlement device is the highest-priority settlement device that has responded that it is possible to process settlement . When the processing means determines that it is the settlement device with the highest priority that responds that the settlement processing is possible, it notifies the registration device that the settlement processing will be executed and puts it into a state where the settlement can be started.

1 is a schematic diagram of a checkout system in one embodiment; FIG. FIG. 2 is a block diagram showing the main circuit configurations of a registration device and a payment device included in the checkout system; FIG. 4 is a schematic diagram showing main data memory areas formed in RAMs of the registration device and the settlement device; FIG. 4 is a schematic diagram showing main data memory areas formed in a RAM and an auxiliary storage device of the registration device; 4 is a flowchart showing main procedures of information processing executed by the CPU of the registration device according to the control program; 4 is a flowchart showing main procedures of information processing executed by the CPU of the registration device according to the control program; 4 is a flow chart showing main procedures of information processing executed by the CPU of the settlement apparatus according to the control program; FIG. 4 is a schematic diagram showing an example of a registration screen displayed on the touch panel of the registration device; 4 is a schematic diagram showing an example of an accounting confirmation screen displayed on the touch panel of the registration device; FIG. FIG. 11 is a schematic diagram showing an example of a checkout confirmation screen when a checkout possible response is received; FIG. 10 is a schematic diagram showing an example of a checkout confirmation screen when a checkout non-acceptable response is received; FIG. 3 is a schematic diagram showing an example of a payment method selection screen displayed on the touch panel of the settlement device; FIG. 4 is a schematic diagram showing an example of a payment screen displayed on the touch panel of the payment device; 4 is a schematic diagram showing an example of a completion screen displayed on the touch panel of the payment device; FIG. FIG. 10 is a flowchart showing main procedures of information processing executed by the CPU of the registration device according to the control program in the second embodiment; FIG. FIG. 10 is a flow chart showing main procedures of information processing executed by the CPU of the payment apparatus according to the control program in the second embodiment; FIG.

An embodiment of a checkout system in which an information analysis function for the registration device to monitor the status of each payment device is unnecessary will be described below with reference to the drawings. In this embodiment, a semi-self checkout system is exemplified in which the registration device is operated by the store clerk and the payment device is operated by the shopper.

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

In FIG. 1, two registration devices 11 (11-1, 11-2) and six settlement devices 12 (12-1, 12-2, 12-3, 12-4, 12-5, 12- 6) and are arranged in two checkout lanes. One registration device 11 (11-1) and three settlement devices 12 (12-1, 12-2, 12-3) are arranged in one checkout lane. Three settlement devices 12 (12-1, 12-2, 12-3) arranged in the same checkout lane are grouped for 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. Three settlement devices 12 (12-4, 12-5, 12-6) arranged in the same checkout lane are grouped for the registration device 11 (11-2). Incidentally, between one registration device 11 and a plurality of settlement devices 12 grouped by grouping, it is possible to simultaneously transmit data from the registration device 11 to each settlement device 12 . Data transmitted from each settlement device 12 is received by the registration device 11 or the settlement device 12 in the same group.

The number of registration devices 11 and settlement devices 12 included in the checkout system 10 is arbitrary. Also, the ratio between the number of registration devices 11 and the number of settlement devices 12 arranged in the checkout lane is arbitrary.

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

The registration device 11 is attached to the work table 23 in FIG. The work table 23 has a rectangular top plate. A passage (checkout lane) for shoppers 22 is formed by arranging a plurality of work tables 23 such that the longitudinal directions of the top plates are substantially parallel.

The registration device 11 has functions of registering products for sale, generating accounting data, transferring the accounting data to the settlement device 12, and settlement processing. The registration of the merchandise for sale means registering the merchandise to be purchased by the shopper 22 in the registration device 11 as the merchandise for sale. For example, by scanning a barcode attached to a product with a scanner, the product is registered in the registration device 11 as a product for sale. Accounting data is data relating to accounting for sales products registered as one transaction. Accounting data includes a product code, which is an identification code of the product to be sold, product name, unit price, number of products, amount of money, and the like. Settlement processing is to process the settlement of transactions, which are commodity trading actions, based on accounting data. For settlement, cash, credit card, electronic money, etc. are used as payment.

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

FIG. 2 is a block diagram showing main circuit configurations of the registration device 11 and the settlement device 12. As shown in FIG. Both the registration device 11 and the settlement device 12 are connected to a LAN (local area network) 13, which is a network. A server (not shown) 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.

Registration device 11 and settlement device 12 exchange information via LAN 13 . As for the network, another communication network such as the Internet or a wireless LAN may be used instead of the LAN 13 . Further, a configuration may be adopted in which information is exchanged between the registration device 11 and the settlement 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 and 11g2. , a printer 11h, a card reader/writer 11i, a communication unit 11j and a transmission system 11k.

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

The ROM 11b corresponds to the main memory portion of the computer. The ROM 11b stores the operating system. The ROM 11b may store the above middleware or application programs. The ROM 11b may store data referred to when the CPU 11a performs various processes.

The RAM 11c corresponds to the main memory portion of the computer. The RAM 11c stores data referred to when the CPU 11a performs various processes. The RAM 11c is also used as a so-called work area for storing data temporarily used when the CPU 11a performs various processes.

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

The application programs stored in the ROM 11 b or the auxiliary storage unit 11 d include control programs describing information processing executed by the registration device 11 . The registration device 11 is generally transferred with the control program stored in the ROM 11b or the auxiliary storage unit 11d. However, the registration device 11 may be transferred without the control program stored in the ROM 11b or the 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, or the like and transferred. Alternatively, the control program may be transferred via a network and written in the auxiliary storage unit 11d of the separately transferred registration device 11 described above.

The drawer opening unit 11e automatically opens a drawer for storing money.
The scanner 11f reads the barcode attached to the product to obtain the product code of the product. As the scanner 11f, various known types can be used as they are. The scanner 11f may be compatible with only one of various known types, or may be compatible with a plurality of types. That is, scanner 11f may include a fixed or handheld two-dimensional code scanner. The scanner 11f may also include a scanner of the type that identifies products from product images using image recognition technology.

Of the two touch panels 11g1 and 11g2, one touch panel 11g1 is for store employees and the other touch panel 11g2 is for customers. Each of touch panels 11g1 and 11g2 includes a display device and a touch sensor. The display device has a display screen of any screen such as a GUI screen. A well-known device such as a color LCD can be used as the display device. The touch sensor is arranged over the display surface of the display device. The touch sensor detects the operator's touch position 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 clerk's touch panel 11g1 is provided on the work table 23 so that the display screen faces the clerk's 21 work space side. 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 receipts by printing various character strings or images on receipt paper. For example, a thermal printer or a dot impact printer can be used as this type of printer 11h.

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

The communication unit 11j performs data communication with a plurality of settlement devices 12 connected via the LAN13. The communication unit 11j can also perform data communication with other registration devices 11 via the LAN 13. FIG.

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

For example, an existing POS terminal can be used as hardware for such a registration device 11 .

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 automatic change dispenser 12e receives inserted coins and bills. Also, the automatic change dispenser 12e ejects 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 functions of the CPU 11a, ROM 11b, RAM 11c, and auxiliary storage of the registration device 11. It is equivalent to the unit 11d, the touch panels 11g1 and 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. The CPU 12a controls each part to realize various operations as the settlement apparatus 12 based on the operating system, middleware, and application programs stored in the ROM 12b and RAM 12c.

The application programs stored in the ROM 12b or the auxiliary storage unit 12d include a control program describing information processing executed by the settlement device 12. FIG. The transfer of payment device 12 is generally performed with the control program stored in ROM 12b or auxiliary storage unit 12d. However, the settlement apparatus 12 may be transferred without the control program stored in the ROM 12b or the auxiliary storage unit 12d. 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, or the like and transferred. Alternatively, the control program may be transferred via a network, and this control program may be written in the auxiliary storage unit 12d of the separately transferred settlement apparatus 12 described above.

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

The checkout system 10 including the registration device 11 and the settlement device 12 having such configurations forms the data memory areas 31 and 32 shown in FIG.

The data memory area 31 is an area for storing data of sales products in one transaction. The data includes items such as product code, product name, unit price, quantity, and price. A product code is a unique code for individually identifying each product. Each product has a product code represented by a barcode, for example, and the registration device 11 can acquire the product code by scanning the barcode with the scanner 11f. The product name and unit price are the name of the product identified by the corresponding product code and the price per item. The number is the number of sales of the same product, and the amount is the amount (sales amount) for the number of sales. The data memory area 31 is hereinafter referred to as transaction memory. The transaction memory 31a for the registration device 11 and the transaction memory 31b for the settlement device 12 are used.

The data memory area 32 is an area for storing the total number of items and the total amount of money. The total number is the total number of sales stored in transaction memory 31 . The total amount is the sum of the sales amounts stored in the transaction memory 31 . The data memory area 32 is hereinafter referred to as total memory. The memory for the registration device 11 is represented by a total memory 32a, and the memory for the settlement device 12 is represented by a total memory 32b.

Also, the checkout system 10 forms the data memory area 41 shown in FIG.

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

The data memory area 42 is an area for storing information regarding a plurality of settlement 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 three settlement devices 12 (12-1, 12-2, 12-3). The data memory area 42 of the registration device 11 (11-2) stores information about the three settlement devices 12 (12-4, 12-5, 12-6).

Information about the settlement device 12 includes a priority number, a settlement device ID, an identification name and response data. The priority number is an integer starting from "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 settlement device ID is a unique ID assigned to each settlement device 12 to individually identify each settlement device 12 and stored in the ROM 12b, for example. Incidentally, the same registration device ID is stored in the ROM 11b for each registration device 11 as well. The identification name is a unique name individually set for each settlement 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 payment processing is possible in the payment device 12 identified by the corresponding payment device ID. For example, response data "OK" indicates that payment processing is possible. Response data "NG" indicates that settlement processing is impossible. Note that the response data "OK" or "NG" is written for convenience of explanation, and the actual data is not limited to this. For example, the response data may be 1-bit flag data, where "1" indicates that the settlement process is possible and "0" indicates that the settlement process is impossible. The data memory area is hereinafter referred to as group table 42 .

The group table 42 stores in advance the settlement device IDs and identification names of the settlement devices 12 grouped with respect to the registration device 11 having the group table 42 . At this time, for the priority number “1”, the settlement device ID and the identification name of the settlement device 12 whose priority is set to the first with respect to the registration device 11 are stored. Similarly, for the priority number "2", the settlement device ID and identification name of the settlement device 12 whose priority is set to the second place are stored. The settlement device ID and identification name of the settlement device 12 set in the first place are stored. For example, the shorter the distance from the registration device 11, the higher the priority is set. Note that the method of setting the priority order is not limited to the distance between the registration device 11 and the settlement device 12 .

5 and 6 are flowcharts showing 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 main procedures of information processing executed by the CPU 12a of the settlement apparatus 12 according to the control program. 8 to 11 are schematic diagrams showing various screen examples displayed on the touch panels 11g1 and 11g2 of the registration device 11. FIG. 12 to 14 are schematic diagrams showing various examples of screens displayed on the touch panel 12g of the settlement device 12. FIG. The operation of the checkout system 10 will be described below with reference to these figures. Note that the contents of the processing described below are only examples, and various processing that can obtain similar results can be used as appropriate.

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

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

The registration screen SC1 displays the contents of the temporary buffer 41, the transaction memory 31a and the total memory 32a, and allows the store clerk 21 to confirm the progress 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 field r11 for displaying the product name and unit price of the most recently registered product for sale, a display field r12 for displaying the quantity, and a display field r13 for displaying the price are displayed. A display field r14 is formed in which the total number of products registered for sale and the total price are displayed. In the display area R2, a list of product names, quantities, unit prices, and prices of products registered for sale prior to the product shown in the display area R1 is formed.

Although not shown, the CPU 11a displays a product button for the store clerk 21 to specify a product and a subtotal output command for the store clerk 21 outside the registration screen SC1 area of the screen of the touch panel 11g. Various function buttons such as a subtotal button are also displayed.

When the store clerk 21 confirms that the registration screen SC1 is displayed on the touch panel 11g, he/she recognizes that the product to be purchased by the shopper 22 can be registered. Then, when the shopper 22 comes to the work table 23 with the purchased product, the store clerk 21 operates the scanner 11f or the product button, for example, and sequentially inputs the product code of the product. When the product codes of all the products have been entered, the store clerk 21 touches the subtotal button. By the above operations, the registration of the product to be purchased by one shopper (sale registration for 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 input of a product code (Act 3). When the product code is input via the scanner 11f or the product button (YES in Act 3), the CPU 11a acquires product information such as the product name and unit price associated with the product code and set in the product database. . Further, the CPU 11a multiplies the unit price by the number of pieces to calculate the amount of money for the number of pieces. The number is the numerical value when the number is entered with the numeric keypad or the like before the product code is entered, and is "1" when the number is not entered. When the CPU 11a thus generates the product sales data including the product code, product name, unit price, quantity and price, it stores the product sales data in the temporary buffer 41 (Act 4). At this time, if merchandise sales data has already been stored in the temporary buffer 41, the CPU 11a moves the stored merchandise sales data to the transaction memory 31, and then transfers new merchandise sales data to the temporary buffer 41. store in

The CPU 11a adds the number and amount 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 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 has not been input (NO in Act 6), the CPU 11a confirms whether or not 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 or not the product code has been input (Act 6). Thus, the CPU 11a waits for the input of the product code or the touch of the subtotal button as Act6 and Act7. Note that 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 processing corresponding to the occurrence event. Such an operation is the same in other waiting states.

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

In the waiting state of Act6 and Act7, if the subtotal button is touched (YES in Act7), the CPU 11a executes the processes of Act8 and Act9. Note that the processing procedures of Act8 and Act9 are not limited to this order. The order may be changed.

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

An example of the accounting confirmation screen SC2 is shown in FIG. The payment confirmation screen SC2 includes a display area R3 and buttons B1, B2, B3 and B4. The display area R3 displays the total number of items in the total memory 32a, the total amount of money, and the like. The buttons B1 and B2 are a subtotal discount button B1 and a subtotal discount button B2 for the store clerk 21 to specify that a discount or discount should be applied to the total amount. The button B3 is a return button B3 for the store clerk 21 to specify to return a partial area of the screen of the touch panel 11g to the registration screen SC1. The button B4 is a checkout button B4 for the store clerk 21 to instruct the transition to checkout after the product registration for one transaction is completed.

The CPU 11a that displays the checkout confirmation screen SC2 confirms whether or not the checkout button has been pressed (Act 10). If the checkout button has not been pressed (NO in Act 10), the CPU 11a checks whether the return button B3 has been pressed (Act 11). If the return button B3 is not pressed (NO in Act11), the CPU 11a checks again whether the checkout button is pressed (Act10). Thus, the CPU 11a waits for an input from the checkout button B4 or an input from the return button B3 as Act10 and Act11.

After confirming the accounting confirmation screen SC2, the store clerk 21 confirms whether or not the merchandise purchased by the shopper 22 remains registered. If it remains, the store clerk 21 touches the return button B3. If not, the store clerk 21 touches the checkout button B4.

In the standby state of Act10 and Act11, when the return button B3 is input (YES in Act11), the CPU 11a returns the partial area of the screen of the touch panel 11g to the registration screen SC1 (Act12). After that, the CPU 11a proceeds to the processing of Act 6, and repeats the subsequent processing in the same manner as described above.

In the standby state of Act10 and Act11, when the payment button B4 is touched (YES in Act10), the CPU 11a proceeds to the processing 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 settlement devices 12 (Act 13). In response to this command, the communication unit 11j sends the accounting data in the text file format to the LAN 13 with each settlement device ID set in the group table 42 as the transmission destination and the registered device ID stored in the ROM 11b as the transmission source. Send to This accounting data is received by a plurality of settlement devices 12 whose destination settlement device IDs match the settlement device IDs stored in the ROM 12b. Here, the CPU 11a constitutes first transmission means in cooperation with the communication unit 11j.

When the CPU 12a of each settlement device 12 receives the accounting data in the text file format via the communication unit 12j, it determines whether the settlement device ID added to the data as the destination matches the settlement device ID stored in the ROM 12b. Check whether 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 reception interrupt processing specifically shown in FIG. Here, the CPU 12a constitutes receiving means in cooperation with the communication unit 12j.

When the reception interrupt process is started, the CPU 12a first checks the busy flag F (Act 31). The busy flag F is 1-bit data which is set to "1" while the CPU 12a is processing settlement of transactions based on accounting data, and is reset to "0" when the processing is completed, and is stored in the RAM 12c. there is Thus, while the busy flag F is set, the settlement device 12 is executing settlement processing. Therefore, the settlement device 12 cannot process settlement of new transactions.

If the busy flag F has been reset (YES in Act 31), that is, if the settlement device 12 is ready to execute settlement processing for a new transaction, the CPU 12a notifies that settlement processing is possible. The communication unit 12j is instructed to transmit an accountable (OK) response to the registration device 11 which is the source of the accounting data (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 registered device ID set as the transmission source of the transaction data as the transmission destination and the payment 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 Act 31), that is, when the settlement apparatus 12 is in a state where settlement processing for new transactions cannot be executed, the CPU 12a indicates that settlement processing is impossible. The communication unit 12j is instructed to transmit a notifying accounting failure (NG) response to the registration device 11 which is 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 LAN 13 with the registered device ID set as the transmission source of the accounting data as the transmission destination and the payment 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.
Here, the CPU 12a constitutes response means in cooperation with the communication unit 12j.

In Act 13 of FIG. 6, the CPU 11a of the registration device 11 that has transmitted the accounting data checks in Act 14 whether or not it has received command data indicating that the transaction is possible or not. If command data has not been received (NO in Act14), the CPU 11a checks in Act15 whether or not the elapsed time from the transmission of accounting data has reached a preset timeout period. The timeout period is set to a time sufficient to receive the command data. From the plurality of settlement devices 12 that have received the accounting data, command data of accounting possible response or accounting impossible response are transmitted respectively. At this time, data collision may occur, so the timeout period is set in consideration of data collision.

If the elapsed time has not reached the timeout time (NO in Act 15), the CPU 11a checks again whether or not command data has been received (Act 14). Thus, in Act14 and Act15, the CPU 11a waits until the command data of the accountable response or the accountable non-response is received or the elapsed time reaches the timeout time.

Upon receiving the command data of the accountable response or the accountable response (YES in Act14), the CPU 11a writes the response data to the group table 42 in Act16 based on the command data. That is, the CPU 11a detects the payment device ID, which is the transmission source, from the received command data. Then, the CPU 11a writes "OK" to the response data associated with the settlement apparatus ID in the group table 42 when the command data indicates that the transaction is possible, and writes "NG" if the command data indicates that the transaction is not possible. write.

After writing the response data to the group table 42, the CPU 11a determines in Act 17 whether or not the response has been completed. When the command data of the transaction-enabled response or the transaction-impossible response is received from all the settlement devices 12 that have sent the transaction data, the CPU 11a recognizes that the response has been completed. When the command data of the transaction-enabled response or the transaction-impossible response is not received from at least one payment device 12, the CPU 11a recognizes that the response has not been completed.

If the response has not been completed (NO in Act 17), the CPU 11a returns to Act 14 and waits until the command data is received or the elapsed time reaches the timeout time.

If the response is completed (YES in Act 17) or if the elapsed time reaches the timeout period (YES in Act 15), the CPU 11a creates data indicating the response result from the settlement device 12 in Act 18. Specifically, the CPU 11a reads the priority number, settlement device ID, and response data as a set from the group table 42 in ascending order of the priority number, and arranges each set in descending order of the priority number, for example, as 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 settlement devices 12. FIG. Upon receiving this command, the communication unit 11j transmits data indicating the response result on the LAN 13 with all settlement device IDs set in the group table 42 as the transmission destinations and the registered device IDs stored in the ROM 11b as the transmission sources. Send. Data indicating the result of this response is received by a plurality of settlement devices 12 whose destination settlement device ID matches the settlement device ID stored in the ROM 12b. Here, the CPU 11a constitutes second transmission means in cooperation with the communication unit 11j.

The CPU 12a of the settlement device 12 that has transmitted the command data of the transaction-enabled response or the transaction-impossible response as the processing of Act32 or Act33 waits for data indicating the response result from the registration device 11 in Act34. When the data indicating the response result is received (YES in Act34), the CPU 12a searches the data in Act35 for a settlement apparatus ID that satisfies the conditions for executing the settlement process.

Specifically, the CPU 12a first detects the set with the lowest priority number from the data indicating the response result. Then, the CPU 12a confirms whether or not this set of response data is the data "OK" of the transaction-enabled response. If the data of the accountable response is "OK", the CPU 12a sets the set of settlement device IDs as the settlement device IDs that satisfy the conditions for executing the settlement process. On the other hand, in the case of the data "NG" indicating that the accounting is not possible, the CPU 12a detects the group with the next lowest priority number. Then, the CPU 12a confirms whether or not this set of response data is the data "OK" of the transaction-enabled response. If the data of the accountable response is "OK", the CPU 12a sets the set of settlement device IDs as the settlement device IDs that satisfy the conditions for executing the settlement process. On the other hand, in the case of the data "NG" indicating that the accounting is not possible, the CPU 12a detects the group with the next lowest priority number.

In this way, the CPU 12a examines the response data for each set in ascending order of the priority number, and selects the settlement device ID of the set that first detects the accountable response data "OK" as the settlement device ID that satisfies the execution conditions for the settlement process. and Note that if all of the set of response data with the highest priority number is "NG", the CPU 12a cannot detect a payment device ID that satisfies the conditions for executing payment processing.

After retrieving a payment apparatus ID that satisfies the conditions for executing payment processing, the CPU 12a checks in Act 36 whether the payment apparatus ID matches the payment apparatus ID stored in the ROM 12b. If the settlement device IDs do not match, or if a settlement device ID that satisfies the conditions for executing the settlement processing cannot be detected (NO in Act 36), the CPU 12a terminates the reception interrupt processing.

On the other hand, if the settlement device ID that satisfies the conditions for executing the settlement process matches the settlement device ID stored in the ROM 12b (YES at Act36), the CPU 12a executes the processes of Act37, Act38, Act39, Act40 and Act41. do. Note that the processing procedure from Act37 to Act39 is not limited to this order. The order may be changed.

In Act37, the CPU 12a sets the busy flag to "1".
In Act 38, the CPU 12a instructs the communication unit 12j to transmit a command notifying execution of accounting to the registration device 11, which is the transmission source of the data indicating the response result. Receiving this command, the communication unit 12j sends the command data of the accounting execution notification with the registered device ID set as the transmission source of the data indicating the response result as the transmission destination and the settlement device ID stored in the ROM 12b as the transmission source. It transmits 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 accounting data in the text file format stored in the predetermined area of the RAM 12c into accounting data in the file format used in the settlement process. Specifically, the CPU 12a converts the accounting data in the text file format into data in the DAT file format (data file with extension ".dac"). By converting the accounting data into data in the DAT file format, the settlement device 12 is ready to start settlement.

Thus, in this embodiment, the DAT file format is defined as a file format used in settlement processing, and the text file format is defined as a file format other than the file format used in settlement processing. The file format used in settlement processing is not limited to the DAT file format. Also, it goes without saying that the file format other than the file format used in the settlement process is not limited to the text file format.
Here, the CPU 12a constitutes determination means and processing means by the processing of Act35 to Act38.

In Act 40, the CPU 12a executes settlement processing based on the accounting data converted into the DAT file format. Payment processing will be described later.
In Act41, the CPU 12a resets the busy flag F to "0". With this, the CPU 12a terminates the reception interrupt process.

In Act 18 of FIG. 6, the CPU 11a of the registration device 11 that has transmitted the data indicating the response result checks in Act 19 whether or not the command data of the accounting execution notification has been received. If the command data has not been received (NO in Act 19), the CPU 11a checks in Act 20 whether or not the elapsed time from the transmission of the data indicating the response result has reached a preset timeout period. The timeout period is set long enough to receive the accounting execution notification command data. A plurality of settlement devices 12 that have received the data indicating the response results determine whether or not to carry out settlement processing. After this determination, one of the payment devices 12 that carry out the payment processing transmits command data for notification of execution of payment. The time-out period is set in consideration of the time required until the settlement device 12 that performs settlement processing is determined.

If the elapsed time has not reached the timeout time (NO in Act 20), the CPU 11a again confirms whether or not the command data of the accounting execution notification has been received (Act 19). Thus, in Act19 and Act20, the CPU 11a waits until the command data of the accounting execution notification is received or the elapsed time reaches the timeout time.

When the command data of the accounting execution notification is received (YES in Act 19), the CPU 11a searches the group table 42 in Act 21, and finds the identification name stored in association with the settlement device ID that is the transmission source of the command data. read out. Then, as shown in FIG. 10, the CPU 11a displays a message indicating that the settlement apparatus 12 with this identification name is ready for settlement processing in a partial region R4 of the checkout confirmation screen SC2. Here, the CPU 11a constitutes notification means by the processing of Act21.

On the other hand, if the elapsed time has reached the timeout period (YES in Act20), there is not even a single payment device 12 that performs payment processing. In this case, as Act22, the CPU 11a displays a message indicating that the transaction data could not be transmitted in a partial region R5 of the transaction confirmation screen SC2, as shown in FIG. After that, the CPU 11a executes a transmission disabling process.

The transmission disapproval process waits for, for example, the payment button B4 to be input again, and if the input is received, the processes after Act 13 are executed again. In this case, the clerk who confirmed the message touches the checkout button B4.

In the transmission prohibition processing, for example, a unique identification code is attached to the accounting data and transmitted to the server, and the printer 11h is driven to issue an accounting ticket on which a bar code indicating the identification code is printed. In this case, the store clerk confirms the message and gives the checkout ticket to the shopper. The shopper has the scanner 12f of the settlement device 12 prepared at a place other than the checkout lane, for example, to read the barcode of the checkout ticket. Then, the CPU 12a of the settlement device 12 acquires the accounting data attached with the identification code obtained from the bar code from the server. Then, the CPU 12a executes the processing of Act37, Act39, Act40 and Act41 in FIG. 7 based on this accounting data.

In this manner, the store clerk 21 registers the product to be purchased by the shopper 22 in the registration device 11 . After completing the registration, the store clerk 21 touches the payment button B4 on the payment confirmation screen SC2. Then, accounting data necessary for settlement of transactions with this shopper 22 is created in the form of a text file. Then, this accounting data is transmitted from the registration device 11 to the grouped plural settlement devices 12 .

The settlement device 12 that has received the accounting data in the text file format determines whether or not settlement processing is possible. Then, the settlement device 12 capable of settlement processing transmits a transaction-capable response to the registration device 11 . A settlement device 12 that cannot process a settlement transmits a transaction impossibility response to the registration device 11 .

In the registration device 11 , the response data in the group table 42 is updated based on the transaction-enabled response or the transaction-impossible response from the settlement device 12 . Data representing the response result created from the priority number, settlement device ID, and response data in the group table 42 is transmitted from the registration device 11 to the grouped settlement devices 12 . Based on the data indicating the result of this response, one of the settlement devices 12 that satisfies the conditions for executing settlement processing is determined. Specifically, the settlement device 12 with the lowest priority number among the settlement devices 12 that have transmitted the accountable response when receiving the transaction data is determined as the one that satisfies the conditions for executing the settlement process.

For example, in the example of the group table 42 shown in FIG. 4, if settlement processing is possible when settlement device A receives accounting data, even if other settlement devices B and C are capable of settlement processing, , it is the payment device A that satisfies the conditions for execution of the payment processing. On the other hand, if settlement device A is unable to perform settlement processing, and settlement device B is capable of settlement processing, settlement device B is the one that satisfies the execution conditions for settlement processing. In addition, if the settlement device B is also unable to perform the settlement processing, and if the settlement device C can perform the settlement processing, then the settlement device C satisfies the execution conditions for the settlement processing. If the settlement apparatus C is also unable to perform the settlement process, no settlement apparatus that satisfies the conditions for executing the settlement process is determined. In this case, a timeout occurs in the registration device 11, so transmission disapproval processing is executed.

When the payment device 12 that satisfies the conditions for execution of payment processing is determined, the payment device 12 transmits a command to notify the registration device 11 of execution of payment. By this command, the registration device 11 displays the identification name of the payment device 12 and a message indicating that the payment is ready in a partial region R4 of the payment confirmation screen SC2. Therefore, the store clerk guides the shopper to checkout with the payment device 12 specified by the identification name.

A shopper 22 who is guided by a store clerk 21 to pay with one of the settlement devices 12 moves to the location of the settlement device 12 . At this time, payment processing has started in the payment device 12 . When the settlement process starts, the settlement device 12 displays a payment method selection screen SC3 (see FIG. 12) on part of the screen of the touch panel 12g.

An example of the payment method selection screen SC3 is shown in FIG. 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 settlement device 12. FIG. The display area R12 displays the total number and total price stored in the total memory 32b. The button B11 is a payment method button B11 for the shopper to specify one of a 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 this embodiment, cash, credit card, and electronic money are exemplified as payment methods, but payment methods are not limited to these. Other payment methods may be added. Also, one of the payment methods may be omitted.

After confirming the payment method selection screen SC3, the shopper 22 determines the payment method and touches the payment method button B11. When the payment method button B11 is touched, the payment screen SC4 (see FIG. 13) of the payment method selected by the payment method button B11 is displayed on part of the screen of the touch panel 12g of the payment device 12.

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

A shopper who selects cash as a payment method inserts cash into the automatic change dispenser 12e. Then, when the cash amount equal to or more than the total amount is thrown in, the user touches the settlement button B13. When the payment button B13 is touched, the payment device 12 executes payment processing by the selected payment method. Since such settlement processing is well known, a detailed description thereof will be omitted.

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

An example of the completion screen SC5 for cash payment is shown in FIG. 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. FIG. The display area R16 displays a guidance image. The guide image is an image that guides the shopper 22 to the receipt issuing port and the change dispensing port. Therefore, the shopper can easily know the place where the receipt is issued and the place where the change is paid out from the guidance image. The display area R16 displays the amount of change. Therefore, the shopper can know the amount of change from the data in the display area R16.

After confirming the completion screen SC5 , the shopper receives the receipt and change according to the guidance image. In response to this, in the settlement device 12, the busy flag F is reset to "0", and the settlement device 12 enters the accounting standby state.

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 registration device 11 does not need an information analysis function for monitoring the status of each settlement device 12 .

[Second embodiment]
Next, a second embodiment will be described.
1 to 5 and 8 to 14 used in the first embodiment are also applied to the second embodiment as they are, and the description is omitted except for the points 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 settlement device 12. FIG. A priority number assigned to the settlement apparatus 12 is stored in the priority number memory. For example, taking the group table 42 shown in FIG. 4 as an example, a priority number "1" is stored in the priority number memory of settlement apparatus A, and a priority number "2" is stored in the priority number memory of settlement apparatus B. A priority number "3" is stored in the priority number memory of the settlement apparatus 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 Act10 and Act11, and the accounting data in text file format as Act13. is collectively transmitted to a plurality of grouped settlement devices 12. FIG. The processing procedure from Act1 to Act13 is the same as in the first embodiment. Part of the reception interrupt processing executed by the CPU 12a of the settlement device 12 that has received the accounting data also differs from that in the first embodiment. Differences from the first embodiment will be described below with reference to FIGS. 15 and 16. FIG.

FIG. 15 is a flowchart showing main procedures of information processing executed after the checkout button B4 is touched in the second embodiment. That is, after instructing the communication unit 11j to transmit accounting data in Act 3, the CPU 11a omits the processes of Act 14 to Act 18. FIG. In other words, the CPU 11a waits until the elapsed time from receiving command data of accounting execution notification from any of the settlement devices 12 in Act 19 or transmitting the accounting data in Act 20 reaches a preset timeout time. When the command data of the accounting execution notification is received, the CPU 11a executes the process of Act21 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 processing of Act22 as in the first embodiment.

FIG. 16 is a flowchart showing main procedures of reception interrupt processing executed by the CPU 12a of the settlement device 12 that has received accounting data according to the control program in the second embodiment. In addition, the same code|symbol is attached|subjected to the part which is common in 1st Embodiment.

That is, when the reception interrupt process is started, the CPU 12a checks the busy flag F in Act31. Here, if the busy flag F is set (NO in Act 31), that is, if the settlement device 12 is in a state where settlement processing for new transactions cannot be executed, the CPU 12a terminates this reception interrupt processing. do.

On the other hand, if the busy flag F has been reset (YES in Act 31), that is, if the settlement device 12 is ready to execute settlement processing for a new transaction, the CPU 12a performs Act 51, priority number memory Reads the priority number stored in Then, the CPU 12a instructs the communication unit 12j to transmit to the other settlement device 12, together with this priority number, a transaction possible response notifying that settlement processing is possible.

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

The CPU 12a of the payment device 12 that has transmitted the transaction-enabled response confirms in Act 52 whether or not it has received a transaction-enabled response from another payment device 12 or not. If the transaction ready response is not received (NO in Act 52), the CPU 12a checks in Act 53 whether or not the elapsed time since receiving the transaction data has reached a preset timeout time. The time-out period is set to a time sufficient for the settlement device 12 that has received the transaction data to transmit a transaction ready response to the other settlement devices 12 . From a plurality of settlement devices 12 that have received the accounting data, there is a possibility that the command data of the accounting ready response will be transmitted substantially at the same time. Therefore, the timeout period is set in consideration of data collision.

If the elapsed time has not reached the timeout time (NO in Act 53), the CPU 11a checks again whether or not command data has been received (Act 52). Thus, in Acts 52 and 53, the CPU 11a waits until the command data of the accountable response is received or the elapsed time reaches the timeout time.

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

On the other hand, if the priority number included in the command data is smaller than the priority number stored in the priority number memory (NO in Act 54), the payment device 12 that sent the command data High priority. In this case, the CPU 12a terminates this reception interrupt process.

When the elapsed time reaches the timeout time without receiving the command data of the accountable response including the priority number smaller than the priority number stored in the priority number memory (YES in Act 53), the CPU 12a The processing of Act37 to Act41 described in the embodiment is executed.

Thus, in the second embodiment as well, the registration device 11 simultaneously transmits accounting data to the plurality of grouped settlement devices 12 . On the other hand, each settlement device 12 that has received the accounting data determines whether or not settlement processing is possible. Then, the command data of the transaction-capable response is transmitted from the settlement device 12 capable of settlement processing to the other settlement devices 12 . This command data includes the priority number stored in the priority number memory of the settlement device 12 . On the other hand, no command data is transmitted from the settlement device 12 that cannot process settlement.

Therefore, if there is only one payment apparatus 12 capable of payment processing, the payment apparatus 12 is determined to be the one that satisfies the execution conditions for payment processing because it times out at Act 53 .

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

The settlement device 12 that satisfies the conditions for executing the settlement process transmits a command to notify the registration device 11 of execution of the settlement. By this command, the registration device 11 displays the identification name of the payment device 12 and a message indicating that the payment is ready in a partial region R4 of the payment confirmation screen SC2. Therefore, the store clerk guides the shopper to checkout with the payment device 12 specified by the identification name. A shopper 22 guided by a store clerk 21 to make a payment with one of the payment devices 12 moves to the place 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 status of each settlement device 12 can be eliminated.

In addition, this invention is not limited to the said embodiment.
For example, in the above embodiment, the settlement devices 12 arranged in the same checkout lane are grouped for the registration device 11, but the settlement devices 12 arranged in other checkout lanes are also grouped. good too.

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

Further, the screens SC1, SC2, SC3, SC4, and SC5 illustrated and described in the above embodiment are merely examples, and needless to say, the layouts are not limited to those illustrated.

Additionally, while several embodiments of the invention have been described, these embodiments have been presented by way of example and are not intended to limit the scope of the invention. These novel embodiments can be implemented in various other forms, and various omissions, replacements, and modifications can be made without departing from the scope of the invention. These embodiments and modifications thereof are included in the scope and gist of the invention, and are included in the scope of the invention described in the claims and equivalents thereof.
The invention described in the original claims of the present application is appended below.
[1] A checkout system in which a registration device that generates accounting data necessary for settlement of each transaction and a plurality of settlement devices that process the settlement of the transaction based on the accounting data are connected via a network. In the system, whether the registration device is capable of processing the payment from the two or more payment devices that have transmitted the accounting data, and a first transmitting means that transmits the accounting data to at least two or more of the payment devices a second transmission means for waiting for a response indicating whether or not the payment is accepted and transmitting data indicating the result of the response to the two or more settlement devices; notification means for waiting for a notification to the effect that a process will be executed, and for notifying the payment apparatus that received the notification when the notification is received from any one of the payment apparatuses, wherein the payment apparatus is the registration apparatus response means for returning a response as to whether or not the settlement processing is possible to the registration device in response to receiving the accounting data from the registration device; , determination means for determining whether or not to execute the payment processing based on the data; A checkout system, comprising: a processing means for making it ready to start.
[2] The first transmitting means transmits the accounting data in a file format other than the file format used in the settlement process to the two or more settlement devices, and the processing means transmits the file used in the settlement process. Supplementary note [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 processing of the payment, so that the payment can be started. Stated checkout system.
[3] A generating means for generating accounting data necessary for settlement of each transaction for each transaction; a transmitting means for waiting for responses as to whether or not said settlement processing is possible from said two or more settlement devices that have transmitted said accounting data, and transmitting data indicating the response results to said two or more settlement devices; 2, and waits for a notification to the effect that the settlement process will be executed from the two or more settlement devices that have transmitted the data indicating the response result, and receives the notification from any one of the settlement devices. and notification means for notifying the settlement apparatus that has received the notification.
[4] Receiving means for receiving the accounting data via a network from a registration device that generates accounting data necessary for settlement of each transaction; Response means for returning a response to the registration device as to whether or not processing is possible, and whether or not to execute the settlement processing based on the data indicating the response result received from the registration device. and processing means for notifying the registration device of the decision to execute the payment processing and placing the payment in a state where the payment can be started. payment device.
[5] In response to receiving the accounting data from a registration device that generates the accounting data necessary for settlement of each transaction to a computer equipped with receiving means for receiving the accounting data via a network , a function of returning a response as to whether or not the payment processing is possible to the registration device, and executing the payment processing based on the data in response to receiving data indicating a response result from the registration device. a control program for realizing a function of determining whether or not the settlement process is to be executed, and a function of notifying the registration device of the decision to execute the settlement process so that the settlement can be started. .

11 registration device 12 settlement device 11a, 12a CPU 11b, 12b ROM 11c, 12c RAM 11d, 12d auxiliary storage unit 11e drawer opening unit 12e automatic change dispenser 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 (5)

a first receiving means for receiving accounting data via a network from a registration device that generates accounting data necessary for settlement of transactions;
response means for transmitting a response to the registration device as to whether the payment processing is possible;
a second receiving means for receiving, from the registration device, data including an order of priority set for each of a plurality of payment devices and information indicating whether the payment processing transmitted from the plurality of payment devices to the registration device is possible; ,
determination means for determining, based on the data received from the registration device, whether the settlement device has the highest priority and responded that the settlement processing is possible;
When it is determined that the settlement device has the highest priority and responded that the settlement processing is possible, processing to notify the registration device to the effect that the settlement processing will be executed and to make the settlement ready to start. means and
payment device. a first receiving means for receiving accounting data via a network from a registration device that generates accounting data necessary for settlement of transactions;
a first storage unit that stores a priority;
a transmitting means for transmitting to another payment device that the payment can be processed together with the priority;
a third receiving means for receiving data including the priority of the other payment device from the other payment device;
determining means for determining, based on the data received from the other payment apparatus, whether the payment apparatus has the highest priority that has responded that the payment can be processed;
When it is determined that the settlement device has the highest priority and responded that the settlement processing is possible, processing to notify the registration device to the effect that the settlement processing will be executed and to make the settlement ready to start. means and
payment device. a second storage unit that stores the accounting data when the accounting data is received and the identification information of the payment device included in the accounting data matches the identification information of the payment device that received the accounting data. 3. The settlement device according to claim 1 or 2 . 4. The settlement apparatus according to any one of claims 1 to 3, wherein said settlement apparatus having a shorter distance from said registration apparatus has higher priority. on the computer of the payment device,
a first receiving function for receiving accounting data via a network from a registration device that generates accounting data necessary for settlement of transactions;
a function of transmitting a response to the registration device as to whether the payment processing is possible;
a second receiving function for receiving from the registration device data including priority set for each of a plurality of payment devices and information indicating whether the payment processing transmitted from the plurality of payment devices to the registration device is possible;
A function of determining, based on the data received from the registered device, whether the payment device has the highest priority and responded that the payment can be processed;
A function of notifying the registration device to the effect that the payment processing is to be executed and putting the payment into a state where the payment can be started when it is determined that the payment device has the highest priority and responded that the payment processing is possible. ,
A control program for realizing

Images