JP2023129532A - Checkout system, settlement device, input processor and control program - Google Patents

Abstract

To negate the need of an information analysis function by which an input processor monitors a state of each settlement device.SOLUTION: A checkout system is constituted by connecting an input processor and a plurality of settlement devices via a network. The input processor waits for input of data related to commodity sales and generates settlement information with respect to the commodity sales on the basis of the data input. The input processor transmits the settlement information to one settlement device set out of the plurality of settlement devices via the network. Each of the settlement devices stores the settlement information in a storage area when being capable of performing settlement processing of the settlement information, and transfers the settlement information to the other settlement devices when not being capable of performing the settlement processing of the settlement information. Each settlement device performs processing of settlement of the settlement information stored in the storage area.SELECTED DRAWING: Figure 10

Description

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

As a checkout system for mass retailers, there is a type in which a product data input processing device and a transaction settlement device are separated. The input processing device waits for input of data related to product sales. When data is input by the operator, the input processing device generates payment information based on the data and transmits this payment information to the payment device. The payment device waits for input of payment data for payment information. Then, when the payment data is input by the operator, the payment device processes the payment based on the payment information and the payment data. Such a checkout system in which the input processing device and the payment device are separated can employ a so-called semi-self system in which the input processing device is operated by a store clerk and the payment device is operated by the shopper.

If we adopt a semi-self-service system, we want to eliminate as much as possible the situation where shoppers have to wait to make payments because they have to take time to operate the payment device. Therefore, conventionally, the number of payment devices is greater than the number of input processing devices. In this case, the input processing device monitors the status of each payment device, automatically selects an available payment device, and sends payment information to that payment device, and the input processing device monitors the status of each payment device. The payment information is displayed on the display, and the clerk selects an available payment device and sends the payment information to that payment device.

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

Japanese Patent Application Publication No. 2013-242839

The problem to be solved by the embodiments of the present invention is to provide a checkout system that can eliminate the need for an information analysis function for an input processing device to monitor the status of each payment device.

In one embodiment, the checkout system is configured by connecting an input processing device having a generating means and a transmitting means, and a plurality of payment devices having a receiving means, a storing means, a transferring means, and a payment means through a network. . The generating means waits for input of data related to the transaction, and generates payment information for the transaction based on the input data. The transmitting means transmits the payment information to one payment device set among the plurality of payment devices via the network. The receiving means receives payment information transmitted via the network. The storage means stores the received payment information in the storage area when the payment processing of the received payment information is possible. The transfer means transfers the received payment information to another payment device connected to the network when payment processing of the received payment information is impossible. The payment means processes payment of payment information stored in the storage area.

FIG. 1 is a schematic diagram of a checkout system in this embodiment. FIG. 2 is a block diagram showing the main circuit configurations of a product registration device and a payment device in this embodiment. FIG. 3 is a schematic diagram showing main memory areas formed in the RAM of the product registration device. FIG. 3 is a schematic diagram showing main memory areas formed in the RAM of the payment device. 5 is a flowchart showing the main steps of control processing executed by the CPU of the product registration device according to a control program. 5 is a flowchart showing the main steps of main processing executed by the CPU of the product registration device according to a control program. FIG. 3 is a schematic diagram showing an example of a registration screen displayed on a touch panel of a product registration device. FIG. 3 is a schematic diagram showing an example of a transmission screen displayed on the touch panel of the product registration device. 2 is a flowchart showing the main steps of main processing executed by the CPU of the payment device according to a control program. 2 is a flowchart showing the main steps of reception interrupt processing executed by the CPU of the payment device according to a control program. The schematic diagram which shows an example of the payment screen displayed on the touch panel of a payment registration device. FIG. 3 is a schematic diagram showing an example of a guidance screen displayed on the touch panel of the product registration device.

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

FIG. 1 is a schematic diagram of a checkout system 10 in this embodiment. The checkout system 10 includes a plurality of product registration devices 11 and a larger number of payment devices 12 than the product registration devices 11. The product registration device 11 and the payment device 12 are arranged in each checkout lane of the store.

FIG. 1 shows a case where two product registration devices 11 and six payment devices 12 are arranged in two checkout lanes. In FIG. 1, one product registration device 11 and three payment devices 12 are arranged for one checkout lane. The number of product registration devices 11 and payment devices 12 included in the checkout system 10 is arbitrary. Furthermore, the ratio of the number of product registration devices 11 and payment devices 12 arranged in the checkout lane is arbitrary.

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

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

The product registration device 11 has the functions of registering purchased products, generating payment information, processing payment, and transmitting payment information to the payment device 12. The registration process is a process for registering a product brought by the shopper 22 who has entered the aisle as a purchased product. The payment process is a process for settling a transaction, which is an act of buying and selling products. Payment information is information required for payment processing.

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

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

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

The CPU 11a, ROM 11b, RAM 11c, and auxiliary storage unit 11d are connected by a transmission system 11k to form a computer.
The CPU 11a corresponds to the central part of the computer. The CPU 11a controls each unit to realize various functions of the product 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 above operating system. The ROM 11b may also store the above-mentioned middleware and application programs. The ROM 11b may also store data that the CPU 11a refers to when performing various processes.

The RAM 11c corresponds to the main memory portion of the computer. The RAM 11c stores data that the CPU 11a refers to when performing various processes. Further, the RAM 11c is used as a so-called work area in which data temporarily used by the CPU 11a is stored when 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 processing by the CPU 11a. As the auxiliary storage unit 11d, for example, an EEPROM (electric erasable programmable read-only memory), an HDD (hard disk drive), or an SSD (solid state drive) can be used.

The application programs stored in the ROM 11b or the auxiliary storage unit 11d include a control program that describes control processing to be described later. Generally, the product registration device 11 is transferred with the control program stored in the ROM 11b or the auxiliary storage unit 11d. However, the product registration device 11 may be transferred without the control program being 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, etc. and transferred. Alternatively, the control program may be transferred via a network, and this control program may be written into the auxiliary storage unit 11d of the separately transferred product registration device 11.

The drawer opening unit 11e automatically opens a drawer for storing coins. The scanner 11f reads product information and obtains 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, the scanner 11f may include a fixed or handheld two-dimensional code scanner. Further, the scanner 11f may include a type that identifies a product from an image of the product using image recognition technology.

The touch panel 11g includes a display device and a touch sensor. The display device uses an arbitrary screen such as a GUI screen as its display screen. As the display device, for example, a well-known device such as a color LCD can be used. The touch sensor is arranged 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 printer 11h issues a receipt by printing various character strings, images, etc. on receipt paper. As this type of printer 11h, 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 a card and a function of writing data to the card. Cards may include payment cards such as credit cards, debit cards, electronic money cards, and prepaid cards, as well as membership cards called membership cards, point cards, and the like. A membership card records at least information for identifying the member who owns the card. The card reader/writer 11i may be a magnetic type, a contact type, or a non-contact type device, and may include multiple 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 other product registration devices 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 11g, printer 11h, card reader/writer 11i, and communication unit 11j. As the transmission system 11k, a well-known system including various buses such as a system bus and various interface circuits that connect these buses and various parts can be used.

As the hardware of such product registration device 11, it is possible to use, for example, a POS terminal compatible with the existing face-to-face sales method.

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 CPU 12a, ROM 12b, RAM 12c, and auxiliary storage unit 12d are connected by a transmission system 12k to form a computer.

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

The ROM 12b corresponds to the main memory portion of the computer. The ROM 12b stores the above operating system. The ROM 12b may also store the above-mentioned middleware and application programs. The ROM 12b may also store data that the CPU 12a refers to when performing various processes.

The RAM 12c corresponds to the main memory portion of the computer. The RAM 12c stores data that the CPU 12a refers to when performing various processes. Further, the RAM 12c is used as a so-called work area in which data temporarily used by the CPU 12a is stored when performing various processes.

The auxiliary storage unit 12d corresponds to the auxiliary storage portion of the computer. The auxiliary storage unit 12d stores data used by the CPU 12a to perform various processes, or data generated by processing by the CPU 12a. As the auxiliary storage unit 12d, for example, an EEPROM, HDD, or SSD can be used.

The application programs stored in the ROM 12b or the auxiliary storage unit 12d include a control program that describes control processing to be described later. Generally, the payment device 12 is transferred with the control program stored in the ROM 12b or the auxiliary storage unit 12d. However, the payment device 12 may be transferred without the control program being 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, etc. and transferred. Alternatively, the control program may be transferred via a network and written into the auxiliary storage unit 12d of the separately transferred payment device 12.

The automatic change machine 12e receives coins and banknotes that are inserted. The automatic change machine 12e also discharges coins and banknotes as change.

The scanner 12f reads product information and obtains the product code of the product. As the scanner 12f, various known types can be used as is. The scanner 12f may be compatible with only one of various known types, or may be compatible with multiple types. That is, the scanner 12f may include a fixed or handheld two-dimensional code scanner. Further, the scanner 12f may include a type that identifies a product from an image of the product using image recognition technology.

The touch panel 12g includes a display device and a touch sensor. The display device uses an arbitrary screen such as a GUI screen as its screen. As the display device, for example, a well-known device such as a color LCD can be used. The touch sensor is arranged 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 12a. A well-known device can be used as the touch sensor.

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

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

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

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

As the hardware of such a payment device 12, it is possible to use, for example, a POS terminal compatible with an existing self-pay method.

FIG. 3 is a schematic diagram showing the main memory areas formed in the RAM 11c of the product registration device 11. In FIG. 3, a memory area 31 is an area that stores a plurality of records each including data on a product code, product name, unit price, quantity, and amount. The product code is a unique code for individually identifying each product. Each product has a product code represented by a barcode, for example. The product name and unit price are the product name and price per item specified by the product code of the same record. The quantity and price are sales data of the product specified by the product code of the same record, that is, the number of products sold and the sales amount for the number of products.

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

The memory area 32 is an area for storing the total number and total amount. The total number of products is the total number of products shown in each record stored in the registered product table 31. The total amount is the sum of the amounts shown in each record stored in the registered product table 31. Hereinafter, the memory area 32 will be referred to as a total table 32.

The memory area 33 is an area that stores a destination ID for specifying the payment device 12 to which payment information is to be sent. The product registration device 11 transmits payment information generated based on the registration process of the purchased product to the payment device 12 via the LAN 13. At this time, the product registration device 11 transmits payment information via the LAN 13 to one payment device 12 set in advance. Specifically, the product registration device 11 transmits payment information to one payment device 12 determined from among a plurality of payment devices 12 (three in FIG. 1) arranged in the same checkout lane. do. That is, in the memory area 33, an ID for identifying this determined one payment device 12 is stored as a destination ID.

FIG. 4 is a schematic diagram showing the main memory areas formed in the RAM 12c of the payment device 12. In FIG. 4, a memory area 41 is an area where payment information received from the product registration device 11 is temporarily stored. Hereinafter, the memory area 41 will be referred to as a payment buffer 41.

The memory area 42 is an area of the processing flag F. The processing flag F is information that identifies whether or not payment processing based on payment information is being executed. In this embodiment, the processing flag F is reset to "0" when payment information is not being executed, and is set to "1" when it is being executed.

The memory area 43 is an area that stores a transfer destination ID for specifying another payment device 12 to which payment information is transferred. When the payment device 12 is executing payment processing based on the payment information stored in the payment buffer 41, it cannot perform the payment processing even if it receives different payment information. At this time, the payment device 12 transfers the payment information received during the payment process to the other payment device 12 via the LAN 13. Specifically, the payment device 12 sends payment information to another preset payment device 12 from among the plurality of payment devices 12 (three in FIG. 1) arranged in the same checkout lane. Transfer. That is, in the memory area 43, an ID for identifying this other set payment device 12 is stored as a transfer destination ID.

Note that among the plurality of payment devices 12 arranged in the same checkout lane, the payment device 12 to which the payment information is transferred last has no transfer destination ID stored in the memory area 43. Alternatively, information indicating that the transfer destination ID has not been set is stored. Further, in an area different from the memory area 43, the communication address of the product registration device 11 placed in the same checkout lane is stored.

5 and 6 are flowcharts showing the main steps of the main process executed by the CPU 11a of the product registration device 11 according to the control program. 7, 8, and 12 are schematic diagrams showing various examples of screens displayed on the touch panel 11g of the product registration device 11 through the main processing. FIG. 9 is a flowchart showing the main steps of the main process executed by the CPU 12a of the payment device 12 according to the control program, and FIG. It is a flowchart showing a procedure. FIG. 11 is a schematic diagram showing an example of a payment screen displayed on the touch panel 12g of the payment device 12 in the main process. The operation of the checkout system 10 will be described below using these figures. Note that the content of the processing described below is an example, and various processing that can obtain similar results can be used as appropriate.

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

The registration screen SC1 shows the contents of the registered product table 31a and the total table 32a, and allows the store clerk 21 to check the implementation status of the registration process. FIG. 7 shows an example of the registration screen SC1. Registration screen SC1 includes display areas R1 and R2. Display area R1 displays the product name, quantity, and unit price of the most recently registered product, and the total number and total price of the purchased products after the product is registered. The display area R2 displays a list of product names, quantities, unit prices, and amounts of products for which purchase registration was made before the product shown on the registration screen SC1.

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

With the registration screen SC1 displayed, the store clerk 21 sequentially inputs the product codes of the products purchased by the shopper 22, for example, by operating the scanner 11f or product buttons. After inputting the product codes of all purchased products, the clerk 21 touches the subtotal button.

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

After updating the registration screen SC1, the CPU 11a checks whether the product code of the product to be registered for purchase has been acquired (Act 6). If the product code has not been acquired (NO in Act 6), the CPU 11a checks whether the subtotal button has been touched (Act 7). If the subtotal button is not touched (NO in Act 7), the CPU 11a checks again whether the product code has been acquired (Act 6). Therefore, the CPU 11a waits for the product code to be acquired or the subtotal button to be touched in Acts 6 and 7. Note that during the standby mode, the CPU 11a may check the occurrence of other events such as other operations being performed, and then proceed to processing in accordance with the occurring event.

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

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

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

After displaying the transmission screen SC2, the CPU 11a checks whether the return button B3 has been operated (Act 10). If the return button B3 has not been operated (NO in Act 10), the CPU 11a checks whether the send button B4 has been operated (Act 11). If the send button B4 has not been operated (NO in Act 11), the CPU 11a checks again whether the return button B3 has been operated (Act 10). Therefore, the CPU 11a waits for the return button B3 or the send button B4 to be operated in Act10 and Act11. Note that in this standby state, the CPU 11a may check the occurrence of another event such as another operation being performed, and then proceed to processing in accordance with the event. For example, when either button B1 or B2 is touched by the clerk 21, the CPU 11a changes the total amount included in the payment information according to a subsequent instruction from the clerk 21.

When the return button B3 is operated in the standby state of Act10 and Act11 (YES in Act10), the CPU 11a returns a partial area of the screen of the touch panel 11g to the registration screen SC1 (Act12). Thereafter, the CPU 11a proceeds to the process in Act 6 and repeats the subsequent processes in the same manner as described above.

When the send button B4 is operated in the standby state of Act10 and Act11 (YES in Act11), the CPU 11a proceeds to the process of Act13 in FIG. That is, the CPU 11a obtains the destination ID set in the memory area 33 (Act 13). Then, the CPU 11a transmits the payment information generated in the process of Act 8 to one payment device 12 identified by this destination ID (Act 14: transmission means).

Specifically, the CPU 11a sends the payment information to the LAN 13 using the communication address set for one payment device 12 identified by the destination ID as the destination address and the communication address set for itself as the source address. The communication unit 11j is controlled to transmit. Thereby, the payment information is transmitted via the LAN 13 to one payment device 12 identified by the destination ID. In this way, the destination ID is associated with the communication address set in the payment device 12. Alternatively, the destination ID may be the communication address itself set in the payment device 12.

The payment information transmitted via the LAN 13 is received by the payment device 12 whose destination address matches the communication address. The payment device 12 that has received the payment information can identify the product registration device 11 that is the sender of the payment information by storing the sender address of the payment information.

After transmitting the payment information, the CPU 11a waits for a response signal from the payment device 12 (Act 15). As will be described later, the payment device 12 that has received the payment information may return an acceptance response signal to the product registration device 11, or may return an error response signal. When the CPU 11a receives the response signal via the communication unit 11j (YES in Act 15), the CPU 11a identifies whether the response signal is an acceptance response or an error response (Act 16). In the case of an acceptance response (YES in Act 16), the CPU 11a displays a guide screen SC4 (see FIG. 12) on a part of the screen of the touch panel 11g (Act 17: notification means).

The guide screen SC4 allows the store clerk 21 to confirm the payment device 12 to which the payment information is to be sent. An example of the guide screen SC4 is shown in FIG. 12. The guide screen SC4 includes a display area R5 and a button B5. The display area R5 displays a message together with the total number and total amount of the total table 32a. The message is for the clerk 21 to recognize the payment device 12 to which the payment information is to be sent, such as, for example, "Please make payment using payment device B." Note that the content of the message is not particularly limited. For example, it may be "sent to payment device B" or simply "payment device B" or "B". Button B5 is used by clerk 21 to specify closing of guide screen SC4. When this button B5 is operated, the CPU 11a closes the guide screen SC4 and ends the information processing for one transaction. After that, the CPU 11 restarts the process from Act1.

On the other hand, if the response signal is not an acceptance response but an error response (NO in Act 16), the CPU 11a executes transmission prohibition processing (Act 18). The transmission impossible process is a process that notifies the store clerk 21 that the payment information transmitted in the process of Act 14, for example, has not been stored in all the payment devices 12 arranged in the same checkout lane. Furthermore, it includes, for example, notifying the store clerk 21 that the product registration device 11 will perform payment processing for the payment information, and executing the payment processing. Note that the transmission prohibition process is not limited to a payment process performed by the product registration device 11. For example, a payment device shared by each checkout lane may be installed at a service counter in a store, and payment information that cannot be sent to this payment device may be sent via the LAN 13.

When the transmission prohibition process ends, the CPU 11a ends the information processing for one transaction. After that, the CPU 11 restarts the process from Act1.

Upon receiving the acceptance response signal from the payment device 12 and checking the guidance screen SC4 displayed on the touch panel 11g, the store clerk 21 informs the shopper 22 that he should make the payment using the payment device 12 guided by the guidance screen SC4. Notice. The shopper 22 who receives this notification moves to the payment device 12 and performs an operation for payment.

Therefore, next, the operation of the payment device 12 will be explained.
When the payment device 12 is activated, the CPU 12a starts main processing of the procedure shown in the flowchart of FIG. First, the CPU 12a initializes the processing flag F in the memory area 42 to "0" (Act 21). Further, the CPU 12a sets the screen of the touch panel 12g as a standby screen (Act 22). The standby screen indicates that there is no situation for payment processing, and any information may be displayed on the standby screen. For example, the standby screen may display a message indicating that payment processing is not possible, or an arbitrary image representing an advertisement as a screen saver.

Note that the processing procedures of Act21 and Act22 are not limited to the procedure shown in FIG. For example, the process in Act 22 may be executed first, and the process in Act 21 may be executed later.

On the other hand, the CPU 12a that has started the main processing can execute the reception interrupt processing shown in FIG. 10 in parallel with the main processing. The reception interrupt process is started when the communication unit 12j receives information whose destination address is the communication address set for itself.

When the reception interrupt process is started, the CPU 12a first identifies whether or not the received information is payment information (Act 31). The received information includes a type code indicating the type of information. The CPU 12a identifies whether or not the received information is payment information based on this type code. If the received information is other than payment information (NO in Act 31), the CPU 12a executes information processing according to the type of the received information.

If the received information is payment information (YES in Act 31), the CPU 12a checks the processing flag F (Act 32). Here, if the processing flag F is reset to "0" (NO in Act 32), that is, when the payment processing is not executed in the payment device 12, the CPU 12a sends a message indicating that the payment information has been received. Notify the process (Act 33).

On the other hand, when the processing flag F is set to "1" (YES in Act 32), that is, when the payment processing is being executed in the payment device 12, the CPU 12a stores the transfer destination ID in the memory area 43. Check whether it is set (Act 34). If the transfer destination ID is not stored in the memory area 43 (NO in Act 34), the CPU 12a transmits an error response signal to the product registration device 11 located in the same checkout lane (Act 35).

Specifically, the CPU 12a causes the communication unit 12j to send the error response signal to the LAN 13 using the communication address set in the product registration device 11 as the destination address and the communication address set for itself as the source address. control. As a result, an error response signal is transmitted to the product registration device 11 via the LAN 13.

On the other hand, if the transfer destination ID is stored in the memory area 43 (YES in Act 34), the CPU 12a acquires the transfer destination ID from the memory area 43 (Act 36). Then, the CPU 12a transfers the payment information to another payment device 12 identified by this transfer destination ID (Act 37: transfer means).

Specifically, the CPU 12a sets the communication address set for one payment device 12 identified by the transfer destination ID as the destination address, and the communication address set for itself as the source address, and receives the information via the LAN 13. The communication unit 12j is controlled to transmit the payment information as is to the LAN 13. As a result, the payment information is transmitted via the LAN 13 to one payment device 12 identified by the transfer destination ID. In this way, the transfer destination ID is associated with the communication address set in the payment device 12. Alternatively, the transfer destination ID may be the communication address itself set in the payment device 12.

Returning to the explanation of FIG. 9.
After completing the processing in Acts 21 and 22, the CPU 12a waits to receive payment information (Act 23). When the CPU 12a receives a notification that the payment information has been received through the process of Act 33 of the reception interrupt process, the CPU 12a stores the payment information received by the communication unit 12j, which is the receiving means, in the payment buffer 41 (Act 24: Storage). means). Further, the CPU 12a sets the processing flag F to "1" (Act 25).

Note that the processing procedures of Act24 and Act25 are not limited to the procedure shown in FIG. For example, the process in Act 25 may be executed first, and the process in Act 24 may be executed later.

After completing the processing in Acts 24 and 25, the CPU 12a transmits a receipt response signal to the product registration device 11 located in the same checkout lane (Act 26: notification means).

Specifically, the CPU 12a causes the communication unit 12j to send the receipt response signal to the LAN 13 using the communication address set in the product registration device 11 as the destination address and the communication address set for itself as the source address. control. As a result, a receipt response signal is transmitted to the product registration device 11 via the LAN 13.

After that, the CPU 12a displays a payment screen SC3 (see FIG. 11) on a part of the screen of the touch panel 12g (Act 27).

An example of the payment screen SC3 is shown in FIG. 11. Payment screen SC3 includes display areas R6 and R7 and buttons B6, B7 and B8. Display area R6 displays operation guidance for shopper 22 operating payment device 12. Display area R7 displays the total number and total amount included in the payment information stored in payment buffer 41. Button B6 is for the shopper 22 to specify that the payment method is cash. Button B7 is for the shopper 22 to specify that the payment method is electronic money. Button B8 is used by the shopper 22 to specify that the store clerk 21 be called. In the following description, button B6 will be referred to as cash button B6, button B7 will be referred to as electronic money button B7, and button B8 will be referred to as clerk call button B8.

After checking the payment screen SC3, the shopper 22 decides whether to pay with cash or electronic money. When paying in cash, touch the cash button B6 and insert cash equal to or greater than the total amount into the automatic change machine 12e. On the other hand, when paying with electronic money, the user touches the electronic money button B7 and causes the card reader/writer 12i to read the data on the electronic money card.

The CPU 12a that has displayed the payment screen SC3 waits for the cash button B6 or the electronic money button B7 to be touched (Act 28: reception means). When the cash button B6 or electronic money button B7 is touched, the CPU 12a executes payment processing using the payment method selected by the touched button (Act 29: payment method). That is, when the cash button B6 is touched, the CPU 12a executes payment processing for cash payment. When the electronic money button B7 is touched, the CPU 12a executes payment processing for electronic money payment. Since these payment processes are well known in existing self-POS terminals, their explanation will be omitted here.

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

When the payment process is completed, the CPU 12a executes a receipt issuing process (Act30). That is, the CPU 12a edits the print data of the receipt based on the payment information stored in the payment buffer 41. The CPU 12a then operates the printer 12h to issue a receipt. When the receipt is issued, the CPU 12a returns to the process of Act4. Then, the CPU 12a repeats the subsequent processing in the same manner as described above.

In this way, in the checkout system 10 of the present embodiment, when the clerk 21 finishes registering the purchased product in the product registration device 11 and the clerk 21 touches the send button B4 on the send screen SC2, the purchased product is Payment information including sales data is sent to one payment device 12 identified by the transmission ID set in the memory area 33 among the plurality of payment devices 12 arranged in the same checkout lane as the product registration device 11. sent to.

For convenience of explanation, the number of payment devices arranged in the same checkout lane as the product registration device 11 is three, as shown in FIG. shall be identified by Further, it is assumed that the destination ID stored in the memory area 33 of the product registration device 11 identifies the payment device 12-1. In this case, the payment information is first sent to the payment device 12-1.

If the payment processing is not being executed in the payment device 12-1, that is, if the processing flag F is reset to “0”, the payment information is stored in the payment buffer 41 of the payment device 12-1. . Further, a receipt response signal is transmitted from the payment device 12-1 to the product registration device 11. As a result, a guide screen SC4 is displayed on the touch panel 11g of the product registration device 11 to inform that the destination of the payment information is the payment device 12-1. The store clerk 21 then tells the shopper 22 to make a payment using the payment device 12-1.

Shopper 22 heads to payment device 12-1. At this time, since the payment screen SC3 is displayed on the touch panel 12g of the payment device 12-1, the shopper 22 makes the payment using cash, electronic money, or the like.

On the other hand, when the payment processing is being executed in the payment device 12-1, that is, when the processing flag F is set to "1", the transfer destination ID is stored in the memory area 43 of the payment device 12-1. The processing is divided depending on whether or not it is stored. Here, it is assumed that an ID that identifies the payment device 12-2 is stored as the transfer destination ID. In this case, the memory area 43 of the payment device 12-2 stores a transfer destination ID that identifies the payment device 12-3. Further, the transfer destination ID is not stored in the memory area 43 of the payment device 12-3.

Since the transfer destination ID that identifies the payment device 12-2 is stored in the memory area 43 of the payment device 12-1, the payment information sent from the product registration device 11 to the payment device 12-1 is transferred via the LAN 13. It is transferred to the payment device 12-2.

If the payment processing is not being executed in the payment device 12-2, that is, if the processing flag F is reset to “0”, the payment information is stored in the payment buffer 41 of the payment device 12-2. . Further, a receipt response signal is transmitted from the payment device 12-2 to the product registration device 11. As a result, a guidance screen SC4 is displayed on the touch panel 11g of the product registration device 11 to inform that the destination of the payment information is the payment device 12-2. The store clerk 21 then tells the shopper 22 to make a payment using the payment device 12-2.

Shopper 22 heads to payment device 12-2. At this time, since the payment screen SC3 is displayed on the touch panel 12g of the payment device 12-2, the shopper 22 makes the payment using cash, electronic money, or the like.

On the other hand, when the payment processing is being executed in the payment device 12-2, that is, when the processing flag F is set to "1", the transfer destination ID is stored in the memory area 43 of the payment device 12-2. The processing is divided depending on whether or not it is stored. Here, since the transfer destination ID that identifies the payment device 12-3 is set in the memory area 43, the payment information transferred from the payment device 12-1 is further transferred to the payment device 12-3 via the LAN 13. be transferred.

If the payment processing is not being executed in the payment device 12-3, that is, if the processing flag F is reset to “0”, the payment information is stored in the payment buffer 41 of the payment device 12-3. . Further, a receipt response signal is transmitted from the payment device 12-3 to the product registration device 11. As a result, a guidance screen SC4 is displayed on the touch panel 11g of the product registration device 11 to inform that the destination of the payment information is the payment device 12-3. The store clerk 21 then tells the shopper 22 to make a payment using the payment device 12-3.

Shopper 22 heads to payment device 12-3. At this time, since the payment screen SC3 is displayed on the touch panel 12g of the payment device 12-3, the shopper 22 makes the payment using cash, electronic money, or the like.

On the other hand, when the payment processing is being executed in the payment device 12-3, that is, when the processing flag F is set to "1", the transfer destination ID is stored in the memory area 43 of the payment device 12-3. The processing is divided depending on whether or not it is stored. Here, since the transfer destination ID is not stored in the memory area 43, an error response signal is transmitted from the payment device 12-3 to the product registration device 11. As a result, the product registration device 11 executes the transmission prohibition process. Due to this transmission prohibition process, for example, the store clerk 21 operates the product registration device 11 to process the payment for the shopper 22.

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

Payment information sent from the product registration device 11 to one payment device 12 is transferred to another payment device 12 set in advance as a forwarding destination when the payment information cannot be processed by that payment device 12. be done. Therefore, the clerk 21 who operates the product registration device 11 does not have to search for a vacant payment device 12, so the work efficiency of the clerk 21 can be improved. Furthermore, there is no longer a mistake in which a store clerk mistakenly sends payment information to an unintended payment device 12.

In this embodiment, the payment device 12 to which the product registration device 11 sends payment information is determined by the destination ID stored in the memory area 33. Similarly, another payment device 12 to which the payment device 12 that is unable to perform payment processing transfers payment information is determined by the transfer destination ID stored in the memory area 43. Therefore, depending on the settings of the destination ID and transfer destination ID stored in the memory areas 33 and 43, respectively, the product registration device 11 sends payment information to which payment device 12 with priority, and by what route. There is an advantage that it is possible to easily set and change the transfer between payment devices 12.

Note that the present invention is not limited to the above embodiments.
For example, in the embodiment described above, a case has been described in which it is determined whether or not payment processing of received payment information is possible based on whether or not payment processing is being executed in payment device 12 . The factors for determining whether payment processing is possible are not limited to these. For example, even if an error has occurred that impedes payment, such as a lack of receipt paper in the printer 12h, it can be determined that the payment processing of the received payment information is impossible.

Furthermore, in the embodiment, one checkout lane is defined as one unit, and the product registration device 11 placed in that lane transmits payment information to one payment device 12 placed in the same lane. The case where the payment device 12 transfers the payment information to another payment device 12 arranged in the same lane when the payment processing is not possible with the payment device 12 is shown. In this regard, the transfer destination ID stored in the memory area 43 of the payment device 12 may include, for example, one that identifies the payment device 12 installed in the adjacent checkout lane. By doing so, even if all the payment devices 12 arranged in the same lane are occupied, if the payment device 12 in the adjacent lane is vacant, it becomes possible to make a payment using that payment device 12.

Furthermore, in the embodiment described above, a case has been described in which the transfer destination ID is not stored in the memory area 43 in the payment device 12 to which payment information is transferred last. In this regard, the destination ID stored in the memory area 33 of the product registration device 11 may be stored in the memory area 43 of the payment device 12 to which payment information is finally transferred. By doing this, even if all the payment devices 12 arranged in the same lane are temporarily occupied, the shopper can be guided to the vacant payment device 12 once the payment for one shopper is completed. become.

Further, in the embodiment described above, a case has been described in which the guidance screen SC4 is displayed to the store clerk 21 in the product registration device 11. Regarding this point, for example, a display device for the shopper may be connected to the product registration device 11, and the guide screen SC4 may be displayed on the display device to provide guidance to the shopper 22. Alternatively, it is also possible to inform the shopper 21 by voice of the payment device 22 that performs payment by using notification means such as voice synthesis means.

Further, in the above embodiment, the act of buying and selling a product is described as a transaction, but the transaction may not involve the act of buying or selling a product. For example, the checkout system of the present invention can also be applied to transactions in which fees are charged for providing services such as facility usage fees and rental item rental fees.

Although several other embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be implemented in various other forms, and various omissions, substitutions, and changes can be made without departing from the gist of the invention. These embodiments and their modifications are included within the scope and gist of the invention, as well as within the scope of the invention described in the claims and its equivalents.

10...Checkout system, 11...Product registration device, 11a...CPU, 11b...ROM, 11c...RAM, 11d...Auxiliary storage unit, 11e...Drawer opening unit, 11f...Scanner, 11g...Touch panel, 11h...Printer, 11i... Card reader/writer, 11j...Communication unit, 11k...Transmission system, 12...Payment device, 12a...CPU, 12b...ROM, 12c...RAM, 12d...Auxiliary storage unit, 12e...Automatic change machine, 12f...Scanner, 12g...Touch panel , 12h...Printer, 12i...Card reader/writer, 12j...Communication unit, 12k...Transmission system, 31...Registered product table, 32...Total table, 33...Destination ID memory area, 41...Payment buffer, 42...Processing in progress Memory area for flag, 43...Memory area for transfer destination ID.

Claims (6)

An input processing device and multiple payment devices are connected via a network,
The input processing device includes:
generation means that waits for input of data related to a transaction and generates payment information for the transaction based on the input data;
Transmitting means for transmitting the payment information to one payment device set among the plurality of payment devices via the network;
Equipped with
Each of the above payment devices is
receiving means for receiving the payment information transmitted via the network;
storage means for storing the payment information in a storage area when payment processing of the payment information received by the receiving means is possible;
a transfer unit that transfers the payment information to another payment device connected to the network when the payment information received by the reception unit cannot process the payment;
a payment means for processing payment of the payment information stored in the storage area;
A checkout system featuring: Each of the above payment devices is
Notifying means for notifying the input processing device that payment processing is possible when payment processing of the payment information received by the receiving means is possible;
further comprising;
The input processing device includes:
Notifying means for making a notification to guide the shopper to the payment device that has notified that the payment processing is possible;
The checkout system according to claim 1, further comprising the following. a generation unit that waits for input of data related to a transaction and generates payment information for the transaction based on the input data; A payment device that constitutes an input processing device and a checkout system, the payment device comprising a transmission means for transmitting the payment information to the payment device,
receiving means for receiving the payment information transmitted via the network;
storage means for storing the payment information in a storage area when payment processing of the payment information received by the reception means is possible;
a transfer unit that transfers the payment information to another payment device connected to the network when the payment information received by the reception unit cannot process the payment;
a payment means for processing payment of the payment information stored in the storage area;
A payment device characterized by comprising: Notifying means for notifying the input processing device that payment processing is possible when payment processing of the payment information received by the receiving means is possible;
4. The payment device according to claim 3, further comprising: When payment processing of the payment information received by the receiving means is possible, storage means stores the payment information in a storage area; when payment processing of the payment information received by the receiving means is not possible, the payment information is stored on the network. a transfer means for transferring the payment information to another payment device connected to the storage area, a payment means for processing the payment of the payment information stored in the storage area, and a payment processing for the payment information received by the receiving means. , a notification means for notifying that payment processing is possible, and an input processing device that is connected via a network to a plurality of payment devices to form a checkout system,
generation means that waits for input of data related to a transaction and generates payment information for the transaction based on the input data;
Transmitting means for transmitting the payment information to one payment device set among the plurality of payment devices via the network;
Notifying means for making a notification to guide the shopper to the payment device that has notified that the payment processing is possible;
An input processing device comprising: a generation unit that waits for input of data related to a transaction and generates payment information for the transaction based on the input data; A computer of the payment device that constitutes a checkout system and an input processing device that includes a transmission device that transmits the payment information to the payment device, and that includes a reception device that receives the payment information that is transmitted via the network. To,
a function of storing the payment information in a storage area when payment processing of the payment information received by the receiving means is possible;
a function of transferring the payment information to another payment device connected to the network when payment processing of the payment information received by the receiving means is impossible;
a function of processing payment of the payment information stored in the storage area;
A control program to realize this.