JP7846064B2 - Payment system - Google Patents

Description

Embodiments of this invention relate to a payment system.

For large retail stores such as supermarkets and home improvement stores, there is a two-person payment system. This system consists of an input device operated by a store employee, called a "checker," and a transaction processing device operated by a store employee, called a "cashier." The input device is used to input information about purchased items, such as barcodes attached to the products. The transaction processing device processes the sales data of purchased items based on the information entered via the input device and settles the transaction with the customer. Because the input device and transaction processing device are separate in the two-person payment system, while processing the payment for the first customer with the transaction processing device, the input device can begin inputting information about the second customer's purchased items. Therefore, it allows for efficient customer processing.

On the other hand, in recent years, there has been a demand to allow customers to perform the deposit operations necessary for transaction settlement themselves, from the perspective of reducing labor costs and preventing infectious diseases. Even in a two-person settlement system, customers are allowed to perform the deposit operations on the transaction processing device 3 themselves. This eliminates the need for a cashier, thus reducing labor costs. Furthermore, since cashiers do not touch cash, ATM cards, etc., it can also serve as a measure against infectious diseases.

Japanese Patent Publication No. 2018-152133

The problem that the embodiments of this invention aim to solve is to provide a payment system that reduces labor costs by having customers perform the payment operations themselves, and that also has excellent effects in terms of infectious disease control.

In one embodiment, the settlement system includes a transaction processing device, a settlement device, and a display device.
The transaction processing device comprises a first settlement means and a transaction information output means. The first settlement means settles the transaction with the customer acting as the operator, based on transaction information obtained via an input device. The transaction information output means outputs transaction information to a holding device when settlement of the transaction is not possible.
The display device includes a display means. The display means displays transaction identification information, which identifies a transaction for which transaction-related information has been output to the holding device, in a manner readable by a reading device.
The settlement device comprises an input means and a second settlement means. The input means retrieves transaction information identified by transaction identification information read by a reader from a holding device. The second settlement means settles the transaction based on the transaction information retrieved by the input means, with the customer acting as the operator.

Figure 1 is a block diagram showing a schematic configuration of a payment system according to one embodiment. Figure 2 is a schematic diagram showing the positional relationship between the input device, transaction processing device, settlement device, display device, and reader device that are present in one settlement lane. Figure 3 is a block diagram showing the main circuit configuration of the main unit of the transaction processing device. Figure 4 is a schematic diagram showing the main memory areas formed in the main memory of the transaction processing unit. Figure 5 is a block diagram showing the main circuit configuration of the payment device. Figure 6 is a schematic diagram showing the main storage areas formed in the main memory of the payment device. Figure 7 is a block diagram showing the main circuit configuration of the hold server. Figure 8 is a schematic diagram showing the data structure of the lane table held by the holding server. Figure 9 is a schematic diagram showing the main functional configurations of the holding server, input device, transaction processing device, settlement device, display device, and reader device, respectively. Figure 10 is a flowchart showing the essential steps of the first information processing performed by the processor of the transaction processing device according to the first business program. Figure 11 is a flowchart showing the essential steps of the first information processing performed by the processor of the transaction processing device according to the first business program. Figure 12 is a flowchart showing the essential steps of the first information processing performed by the processor of the transaction processing device according to the first business program. Figure 13 is a flowchart showing the essential steps of the first information processing performed by the processor of the transaction processing device according to the first business program. Figure 14 is a flowchart showing the essential steps of the second information processing performed by the processor of the transaction processing device in accordance with the first business program. Figure 15 is a flowchart showing the essential steps of the third information processing that the processor of the transaction processing device executes according to the first business program. Figure 16 is a flowchart showing the essential steps of the fourth information processing that the hold server's processor executes according to the second business program. Figure 17 is a flowchart showing the essential steps of the fourth information processing that the holding server's processor executes according to the second business program. Figure 18 is a flowchart showing the essential steps of the fourth information processing that the holding server's processor executes according to the second business program. Figure 19 is a flowchart showing the essential steps of the fifth information processing performed by the payment device's processor in accordance with the third business program. Figure 20 is a flowchart showing the essential steps of the sixth information processing that the payment device's processor executes according to the third business program. Figure 21 is a flowchart showing the essential steps of the seventh information processing that the payment device's processor executes according to the third business program. Figure 22 shows an example of a registration screen displayed on the touch panel of an input device. Figure 23 shows an example of a registration screen displayed on the input device's display. Figure 24 shows an example of a subplan view displayed on the touch panel of an input device. Figure 25 shows an example of a subplan view displayed on the input device's screen. Figure 26 shows an example of a payment method selection screen displayed on the touch panel of an input device. Figure 27 shows an example of a payment screen displayed on the touch panel of an input device. Figure 28 shows an example of a pop-up displayed on the payment screen of an input device's touch panel while waiting for payment. Figure 29 shows an example of text displayed on the subplan screen of the input device's display while waiting for payment. Figure 30 is an example of a pop-up displayed on the payment screen of the input device's touch panel when payment is possible using the transaction processing device. Figure 31 is an example of the text displayed on the subplan screen of the input device's display when payment is available in the transaction processing device. Figure 32 shows an example of a payment method selection screen displayed on the second touch panel of the transaction processing device. Figure 33 shows an example of a payment notification screen displayed on the second touch panel of the transaction processing device. Figure 34 shows an example of a payment screen displayed on the second touch panel of the transaction processing device. Figure 35 shows an example of a payment completion screen displayed on the second touch panel of the transaction processing device. Figure 36 shows an example of a reading screen displayed on a display device. Figure 37 shows an example of an instruction screen displayed on a display device. Figure 38 is an example of a pop-up displayed on the payment screen of the input device's touch panel when payment is possible using the payment device. Figure 39 is an example of text displayed on the subplanar screen of the input device's display when payment is possible at the payment device. Figure 40 is an example of a pop-up that notifies a store clerk to specify the payment destination displayed on the registration screen of the input device's touch panel. Figure 41 shows an example of a transaction details confirmation screen displayed on the touch panel of a payment device. Figure 42 shows an example of a payment method selection screen displayed on the touch panel of a payment device. Figure 43 shows an example of a payment notification screen displayed on the touch panel of a payment device. Figure 44 shows an example of a payment screen displayed on the touch panel of a payment device. Figure 45 shows an example of a payment completion screen displayed on the touch panel of a payment device. Figure 46 is a flowchart showing the essential steps of the eighth information processing that the payment device's processor executes according to the third business program in the second embodiment. Figure 47 is a flowchart showing the essential steps of the ninth information processing that the processor of the hold server executes according to the second business program in the second embodiment. Figure 48 shows an example of a confirmation screen displayed on a display device. Figure 49 is a flowchart showing the essential steps of the tenth information processing that the processor of the hold server executes according to the second business program in the third embodiment. Figure 50 is a flowchart showing the essential steps of the tenth information processing that the hold server's processor executes according to the second business program in the third embodiment. Figure 51 is a flowchart showing the essential steps of the 11th information processing performed by the payment device's processor in accordance with the third business program in the third embodiment. Figure 52 is a block diagram showing the schematic configuration of a payment system according to the fourth embodiment.

The following describes an embodiment of a payment system in which the customer performs the payment process, using diagrams.
[Explanation of the payment system configuration]
Figure 1 is a block diagram illustrating the schematic configuration of the payment system 100 according to this embodiment. The payment system 100 includes a holding server 1. The payment system 100 also includes an input device 2, a transaction processing device 3, a payment device 4, a display device 5, and a reader device 9 for each payment lane L. The payment lane L is a passage where customers line up to settle transactions. When this payment system 100 is introduced in a retail store, the customers are the buyers of goods. When this payment system 100 is introduced in a paid facility such as an amusement park, art museum, or museum, the customers are the users of the facility. Each payment lane L is assigned a unique lane identification information, for example, a three-digit lane number.

The settlement system 100 connects the holding server 1 and the transaction processing units 3, settlement devices 4, and display devices 5 of each settlement lane L via a communication network 6 such as a LAN (Local Area Network), enabling bidirectional communication. The settlement system 100 also connects the input device 2 and the transaction processing unit 3 of each settlement lane L with a transmission cable, and connects the settlement device 4 and the reader device 9 with a transmission cable. The input device 2 and the transaction processing unit 3, and the settlement device 4 and the reader device 9 may be connected by short-range wireless communication. Details of the holding server 1, input device 2, transaction processing unit 3, settlement device 4, display device 5, and reader device 9 will be described later.

Figure 2 is a schematic diagram showing the positional relationship of the input device 2, transaction processing device 3, payment device 4, display device 5, and reader device 9 in a single payment lane L. Figure 2 shows a payment lane L in a retail store such as a supermarket or home improvement store. The payment lane L is located in a checkout area (cash register) separate from the sales floor where goods are displayed.

The input device 2 is attached to the checkout counter 20. The checkout counter 20 is positioned along the aisle PA, where customers (purchasers) walk in the direction indicated by the arrows in the diagram. The input device 2 is mounted approximately in the center of the top surface of the checkout counter 20. The area upstream of the input device 2 in the aisle PA is designated as space for placing purchased items before registration, while the area downstream is designated as space for placing purchased items after registration.

The input device 2 includes a stationary scanner 21, a handheld scanner 22, a touch panel 23, a keyboard 24, and a display 25 as input/output devices. The input device 2 positions the stationary scanner 21 so as to protrude upward from the top surface of the checkout counter 20, and the handheld scanner 22, touch panel 23, keyboard 24, and display 25 are arranged around the stationary scanner 21.

In detail, the input device 2 has a fixed scanner 21 fixed to the top surface of the checkout counter 20. The fixed scanner 21 is vertical, and is fixed so that the barcode reading window is on the side opposite to the aisle PA. The input device 2 has a handheld scanner 22 attached to one side of the fixed scanner 21. A touch panel 23 is attached to the top of the fixed scanner 21 so that its operation panel surface faces the same direction as the reading window of the fixed scanner 21. A keyboard 24 is attached to one side of the touch panel 23 so that its key surface faces the same direction as the operation panel surface of the touch panel 23. Furthermore, a display 25 is attached to one side of the fixed scanner 21 so that its display screen faces the aisle PA. Note that the display 25 may be a touch panel.

With this arrangement of input/output devices, an employee standing in space SP on the opposite side of aisle PA from the checkout counter 20—a so-called store clerk—can operate a stationary scanner 21, a handheld scanner 22, a touch panel 23, or a keyboard 24 to input information related to the transaction with the customer, that is, information related to the purchased items, such as product code, quantity purchased, discount amount, etc. At this time, the clerk can confirm the product name, unit price, etc. of the purchased items using the information displayed on the touch panel 23. The customer can confirm the product name, unit price, etc. of the purchased items using the information displayed on the display 25. The input device 2 can be rephrased as a scanner device, etc.

The transaction processing device 3 is a computer device that functions as a terminal for a POS (Point of Sales) system. The transaction processing device 3 includes a keyboard 31 and a first touch panel 32 as an integrated device with the main unit 30, and external devices attached to the main unit 30, including a handheld scanner 33, a second touch panel 34, a printer 35, an automatic change dispenser 36, a cashless payment terminal 37, etc. The transaction processing device 3 is mounted on the top surface of a cash register counter 38, located on the opposite side of the aisle PA near the downstream end of the checkout counter 20.

In detail, the transaction processing device 3 is mounted on the cash register counter 38 such that the key surface of the keyboard 31 and the operation panel surface of the first touch panel 32 face the space SP where the store clerk stands. Around this device 30 are the handheld scanner 33, the second touch panel 34, the printer 35, the automatic change dispenser 36, and the cashless payment terminal 37. The handheld scanner 33 is positioned so that it can be operated by the store clerk standing in space SP. The second touch panel 34 is positioned so that its display screen can be seen by customers standing in the aisle PA. The printer 35 is positioned so that customers standing in the aisle PA can easily receive their receipts. The automatic change dispenser 36 is positioned so that customers standing in the aisle PA can easily insert cash and take out the dispensed change. The cashless payment terminal 37 is positioned so that customers standing in the aisle PA can easily operate it when making cashless payments such as credit card payments, electronic money payments, and code payments.

With this device configuration, customers standing in the aisle PA can immediately check the information displayed on the second touch panel 34, such as payment information. Customers can also receive a receipt issued from the printer 35 on the spot. Customers paying with cash can insert cash into the automatic change dispenser 36 and collect the change while standing in the aisle PA. Customers paying with cashless payment can operate the cashless payment terminal 37 while standing in the aisle PA to make a cashless payment. Thus, the transaction processing device 3 functions as a self-service payment device, allowing customers to perform payment operations themselves. The transaction processing device 3 can also be referred to as a POS terminal, electronic cash register, sales processing device, etc.

Payment device 4 is also a self-service payment device that allows customers to perform payment operations themselves. Payment device 4 is used by customers who cannot pay using transaction processing device 3 because it is in use. Therefore, payment device 4 is installed downstream of transaction processing device 3 in the direction of customer movement indicated by the arrow in the diagram. Payment device 4 may also be installed on the opposite side of passage PA from transaction processing device 3.

The payment device 4 has a box-shaped casing 40, with one side facing the customer. Hereafter, this side facing the customer will be referred to as the front. The payment device 4 has a basket rest 41 attached to its right side when viewed from the front. The basket rest 41 is a space for customers using the payment device 4 to place their shopping baskets containing purchased items.

The payment device 4 is equipped with a touch panel 42 as a man-machine interface with the customer. The touch panel 42 is mounted in a position that is easy for the customer, who is the operator, to operate. In this embodiment, the touch panel 42 is mounted on the top of the housing 40 with the display screen facing forward. The payment device 4 has a printer 77 (see Figure 5) for printing receipts built into the housing 40, and a receipt issuing slot 43 for issuing receipts printed by the printer 77 is formed on the front of the housing 40. The payment device 4 also has an automatic change dispenser 78 (see Figure 5) built into it, and a coin slot 44, a coin outlet 45, and a banknote slot 46 are formed on the front of the housing 40. With this arrangement, a customer paying in cash inserts banknotes into the banknote slot 46 and coins into the coin slot 44. The device then collects banknotes dispensed from the banknote slot 46 as change, or coins dispensed from the coin slot 45 as change, and receives receipts issued from the receipt issuing slot 43. Although not shown in Figure 1, the payment device 4 is also equipped with a cashless payment terminal 79 (see Figure 5), enabling it to support cashless payments.

The payment device 4 has a warning light 47 mounted on the top of its casing 40. The warning light 47 is a lamp that notifies the store staff in space SP of the operating status of the payment device 4. The operating status of the payment device 4, as notified by the warning light 47, includes "payment in progress" and "standby." "Payment in progress" refers to the period from when the customer starts paying until the payment is completed. Any other period is considered "standby." The payment device 4 can also be referred to as an accounting machine, self-service POS terminal, payment machine, etc.

The display device 5, as will be described in detail later, is a device that displays transaction identification information, which identifies a transaction, in a way that it can be read by the reader device 9. The display device 5 also receives instructions from the store clerk regarding whether the settlement device 4 or the transaction processing device 3 should retrieve the transaction information held on the holding server 1. One example of a display device 5 is a tablet. A tablet is a device equipped with a flat liquid crystal screen that can be operated by touching the screen with a finger or pen. The display device 5 is operated by a store clerk in space SP. Therefore, there are no particular restrictions on the installation location, but the display device 5 should be placed in a location that is easy for the store clerk to operate.

The reader 9 is a device for reading transaction identification information displayed on the screen of the display device 5. The reader 9 outputs the read transaction identification information to the settlement device 4. The reader 9 is installed in a location where it can read the transaction identification information displayed on the screen of the display device 5. The transaction identification information is displayed on the display device 5 in the form of a machine-readable code, such as a barcode or a two-dimensional code. The reader 9 is an optical input device that reads machine-readable codes, such as barcodes or two-dimensional codes, by scanning them with light. The reader 9 may also be an imaging input device that reads machine-readable codes from images captured by a camera.

[Description of the Transaction Processing Unit's Configuration]
Figure 3 is a block diagram showing the main circuit configuration of the main unit 30 of the transaction processing device 3. As shown in the figure, the main unit 30 includes a processor 61, main memory 62, auxiliary storage device 63, clock 64, communication interface 65, scanner interface 66, touch panel interface 67, printer interface 68, change machine interface 69, payment terminal interface 610, input device interface 611, and system transmission path 612, etc. The system transmission path 612 includes an address bus, data bus, control signal lines, etc. The system transmission path 612 connects the processor 61 to the other parts and transmits data signals exchanged between them.

The main unit 30 constitutes a computer by connecting the processor 61, main memory 62, auxiliary storage device 63, clock 64, communication interface 65, scanner interface 66, touch panel interface 67, printer interface 68, change machine interface 69, payment terminal interface 610, and input device interface 611 via a system transmission path 612. The main unit 30 then connects the keyboard 31 and the first touch panel 32 to this computer via the system transmission path 612.

The processor 61 corresponds to the central part of the computer described above. The processor 61 controls various parts to realize various functions as a transaction processing device 3, according to the operating system or application program. The processor 61 is, for example, a CPU (Central Processing Unit). The processor 61 is a multi-core processor that includes multiple processor cores and is capable of executing multiple processes in parallel.

Main memory 62 corresponds to the main memory portion of the computer described above. Main memory 62 includes both non-volatile and volatile memory areas. In the non-volatile memory area, main memory 62 stores the operating system or application programs. Main memory 62 may also store data necessary for the processor 61 to perform control operations in either the non-volatile or volatile memory area. Main memory 62 uses the volatile memory area as a work area where data is rewritten as needed by the processor 61. The non-volatile memory area is, for example, ROM (Read Only Memory). The volatile memory area is, for example, RAM (Random Access Memory).

The auxiliary storage device 63 corresponds to the auxiliary storage portion of the computer described above. For example, an EEPROM (Electric Erasable Programmable Read-Only Memory), HDD (Hard Disk Drive), or SSD (Solid State Drive) can serve as the auxiliary storage device 63. The auxiliary storage device 63 stores data used by the processor 61 for various processing tasks, data created by the processing performed by the processor 61, and so on. The auxiliary storage device 63 may also store the application program described above.

The clock 64 measures the date and time. The processor 61 processes the date and time measured by the clock 64 as the current date and time.

The communication interface 65 is an interface for data communication with the holding server 1 connected to the communication network 6. The communication interface 65 is also an interface for data communication with other servers, such as the POS server, or with the payment device 4, display device 5, etc., also connected to the communication network 6. The POS server is a computer that stores product data such as the product name and unit price of each product sold in the store, and collects and aggregates product sales data of purchased products processed by the transaction processing device 3 to manage sales, inventory, etc., at the point of sale.

The scanner interface 66, touch panel interface 67, printer interface 68, change dispenser interface 69, and payment terminal interface 610 are all interfaces for data communication with devices externally attached to the main unit 30. Specifically, the scanner interface 66 communicates data with the handheld scanner 33. The touch panel interface 67 communicates data with the second touch panel 34. The printer interface 68 communicates data with the printer 35. The change dispenser interface 69 communicates data with the automatic change dispenser 36. The payment terminal interface 610 communicates data with the cashless payment terminal 37.

The input device interface 611 is an interface for data communication with the input device 2 connected by the transmission cable 7. Specifically, the input device interface 611 communicates data with the stationary scanner 21, the handheld scanner 22, the touch panel 23, the keyboard 24, and the display 25, respectively.

Figure 4 is a schematic diagram showing the main memory areas formed in the main memory 62. The transaction processing device 3 uses a portion of the volatile memory area in the main memory 62 as the area for the first transaction file 621, the second transaction file 622, the status memory 623, the first flag memory 624, the second flag memory 625, and the transaction identification information memory 626. The first transaction file 621 and the second transaction file 622 are areas for storing product sales data, which is information related to purchased goods processed as a single transaction. The product sales data includes items such as the product code, product name, unit price, purchase quantity, and sales amount of the purchased goods. The sales amount is the amount obtained by multiplying the unit price by the purchase quantity. The product sales data only needs to include at least the product code and purchase quantity of the purchased goods. The status memory 623 is an area for storing the payment status ST. The first flag memory 624 is an area for storing the payment in progress flag Fa. The second flag memory 625 is an area for storing the pending flag Fb. The transaction identification information memory 626 is an area for storing transaction identification information to identify a transaction.

The payment status ST is identification information representing the status of payment. There are two payment statuses: a first status where the payment method is not specified in the input device 2, and a second status where the payment method is specified in the input device 2. In this embodiment, the payment status ST representing the first status is set to "10," and the payment status ST representing the second status is set to "20."

The payment flag Fa is a one-bit data value used by the transaction processing device 3 to identify whether or not payment is in progress. In this embodiment, the payment flag Fa is set to "1" to indicate that payment is in progress, and to "0" to indicate that payment is not in progress.

The pending flag Fb is a 1-bit data value used to identify whether the transaction information processed by the transaction processing device 3 is pending on the pending server 1. In this embodiment, the pending flag Fb is set to "1" to indicate that the transaction is pending, and the pending flag Fb is set to "0" to indicate that the transaction is not pending.

Transaction identification information is unique information formed by concatenating the unique information of the transaction processing device 3 with the date (year, month, day) and time (hour, minute, second) of the transaction. Transaction identification information may also be a series of numbers issued each time a transaction is initiated. Transaction identification information only needs to be unique information that can identify a transaction.

[Description of Payment Device Configuration]
Figure 5 is a block diagram showing the main circuit configuration of the payment device 4. As shown, the payment device 4 includes a processor 71, main memory 72, auxiliary storage device 73, clock 74, communication interface 75, and system transmission path 76, etc. The system transmission path 76 includes an address bus, data bus, control signal lines, etc. The system transmission path 76 connects the processor 71 to the other parts and transmits data signals exchanged between them.

The payment device 4 is configured as a computer by connecting the processor 71, main memory 72, auxiliary storage device 73, clock 74, and communication interface 75 via a system transmission path 76. The payment device 4 then connects the touch panel 42, warning light 47, printer 77, automatic change dispenser 78, and cashless payment terminal 79 to this computer via the system transmission path 76.

The processor 71 corresponds to the central part of the computer described above. The processor 71 controls various parts to realize various functions as a payment device 4, according to the operating system or application program. The processor 71 is, for example, a CPU. The processor 71 is a multi-core processor that includes multiple processor cores and is capable of executing multiple processes in parallel.

The main memory 72 corresponds to the main memory portion of the computer described above. The main memory 72 includes both non-volatile and volatile memory areas. The non-volatile memory area of the main memory 72 stores the operating system or application programs. The main memory 72 may also store data necessary for the processor 71 to perform processing to control various parts, in either the non-volatile or volatile memory areas. The volatile memory area of the main memory 72 is used as a work area where data is rewritten as needed by the processor 71. The non-volatile memory area is, for example, ROM. The volatile memory area is, for example, RAM.

The auxiliary storage device 73 corresponds to the auxiliary storage portion of the computer described above. For example, an EEPROM, HDD, or SSD could serve as the auxiliary storage device 73. The auxiliary storage device 73 stores data used by the processor 71 for various processing tasks, data created by the processing performed by the processor 71, and so on. The auxiliary storage device 73 may also store the application program described above.

Clock 74 measures the date and time. Processor 71 processes the date and time measured by clock 74 as the current date and time.

The communication interface 75 is an interface for data communication with the holding server 1, which is connected to the communication network 6. The communication interface 75 also serves as an interface for data communication with other servers, such as a POS server, or with the transaction processing device 3, display device 5, etc., which are also connected to the communication network 6.

Figure 6 is a schematic diagram showing the main storage areas formed in the main memory 72. The payment device 4 uses a portion of the volatile storage area in the main memory 72 as the area for the third transaction file 721 and the third flag memory 722. The third transaction file 721, like the first transaction file 621 and the second transaction file 622, is an area for storing product sales data, which is information related to purchased goods processed as a single transaction.

The third flag memory 722 is an area for storing the payment in progress flag Fc. The payment in progress flag Fc is a 1-bit data value used to identify whether or not payment is in progress at the settlement device 4. In this embodiment, the payment in progress flag Fc is set to "1" to indicate that payment is in progress, and the payment in progress flag Fc is set to "0" to indicate that payment is not in progress.

[Explanation of the configuration of the holding server]
Figure 7 is a block diagram showing the main circuit configuration of the hold server 1. As shown in the figure, the hold server 1 includes a processor 11, main memory 12, auxiliary storage device 13, clock 14, communication interface 15, and system transmission path 16, etc. The system transmission path 16 includes an address bus, data bus, control signal lines, etc. The system transmission path 16 connects the processor 11 to the other parts and transmits data signals exchanged between them.

The hold server 1 is configured as a computer by connecting the processor 11, main memory 12, auxiliary storage device 13, clock 14, and communication interface 15 via a system transmission path 16.

The processor 11 corresponds to the central part of the computer described above. The processor 11 controls various components to realize various functions as a pending server 1, according to the operating system or application program. The processor 11 is, for example, a CPU. The processor 11 is a multi-core processor that includes multiple processor cores and is capable of executing multiple processes in parallel.

Main memory 12 corresponds to the main memory portion of the computer described above. Main memory 12 includes both non-volatile and volatile memory areas. In the non-volatile memory area, main memory 12 stores the operating system or application programs. Main memory 12 may also store data necessary for the processor 11 to perform processing to control various parts, in either non-volatile or volatile memory areas. Main memory 12 uses the volatile memory area as a work area where data is rewritten as needed by the processor 11. The non-volatile memory area is, for example, ROM. The volatile memory area is, for example, RAM.

The auxiliary storage device 13 corresponds to the auxiliary storage portion of the computer described above. For example, an EEPROM, HDD, or SSD could be the auxiliary storage device 13. The auxiliary storage device 13 stores data used by the processor 11 for various processing tasks, data created by the processing performed by the processor 11, and so on. The auxiliary storage device 13 may also store the application program described above.

Clock 14 measures the date and time. Processor 11 processes the date and time measured by clock 14 as the current date and time.

The communication interface 15 is an interface for data communication between the transaction processing device 3, settlement device 4, and display device 5, which are connected to the communication network 6.

In this configuration, the holding server 1 uses a portion of the storage area of the auxiliary storage device 13 as the area for the lane table 131. The data structure of the lane table 131 is schematically shown in Figure 8. As shown, the lane table 131 has a column Ca for lane number, a column Cb for transaction processing device ID, a column Cc for settlement device ID, a column Cd for display device ID, and a column Ce for transaction identification information. Column Ca contains the lane number of each settlement lane L. Columns Cb, Cc, and Cd contain the IDs of the transaction processing device 3, settlement device 4, and display device 5 located in the settlement lane L corresponding to the lane number described in column Ca of the same row. Each transaction processing device 3 constituting the settlement system 100 has a different transaction processing device ID set as identification information. Similarly, each settlement device 4 has a different settlement device ID as identification information, and each display device 5 has a different settlement device ID as identification information.

For example, by concatenating a three-digit number "XXX" with the lane number "nnn," a unique ID "XXXnnn" can be created for each lane. Therefore, by using different three-digit numbers "XXX" for the transaction processing device 3, the settlement device 4, and the display device 5, unique identification information (device ID) can be created for each device.

Column Ce is cleared by default. When a transaction is executed in the transaction processing device 3 located in the settlement lane L corresponding to the lane number, the transaction identification information for that transaction is recorded in column Ce. After the transaction is settled, the transaction identification information is cleared.

Furthermore, the holding server 1 allocates a portion of the storage area in the auxiliary storage device 13 to the lane-specific folders 132. The lane-specific folders 132 are data folders, with a number corresponding to the number of settlement lanes L. The lane-specific folders 132 are areas for storing, or holding, transaction-related information output from the transaction processing device 3. The holding server 1 stores transaction-related information in the lane-specific folders 132 of the transaction processing device 3 that output that information. The holding server 1 can be rephrased as a holding device.

[Description of Payment System Functions]
Figure 9 is a schematic diagram showing the main functional configurations of the holding server 1, input device 2, transaction processing device 3, settlement device 4, display device 5, and reader device 9. Below, the functions of each device will be explained in the following order: input device 2, transaction processing device 3, display device 5, holding server 1, settlement device 4, display device 5, and reader device 9.

The input device 2 functions as an input means 201, a completion acceptance means 202, and a first payment acceptance means 203. The input means 201 has the function of inputting transaction information, that is, information related to the purchased goods that the customer buys. The input means 201 inputs information related to purchased goods, such as product codes and purchase quantities, via input devices such as a stationary scanner 21, a handheld scanner 22, a touch panel 23, and a keyboard 24. For example, the input means 201 inputs the product code of the purchased goods from a barcode read by the stationary scanner 21 or the handheld scanner 22. For example, the input means 201 inputs the purchase quantity of the purchased goods from a numerical value entered via a numeric keypad operation on the touch panel 23 or the keyboard 24.

The termination reception means 202 is a function that receives an instruction to complete the input of transaction-related information, that is, information related to the purchased goods that the customer is buying. The termination reception means 202 receives the instruction to complete the input of information related to purchased goods via an input device such as a touch panel 23 or a keyboard 24. For example, the termination reception means 202 receives a signal generated by a predetermined key operation on the touch panel 23 or keyboard 24 as an input completion instruction.

The first payment acceptance means 203 is a function that accepts the selection input of a payment method via a device operated by a store employee. The device operated by the store employee is, for example, a touch panel 23. The first payment acceptance means 203 displays a payment method selection screen on the touch panel 23. The first payment acceptance means 203 then accepts the payment method selected by the touch operation on the screen as the selected payment method. The type of device is not particularly limited; for example, it could be a keyboard 24. Payment methods include cash, credit cards, electronic money, and code payments. Payment methods may also include monetary vouchers such as gift certificates.

The transaction processing device 3 has the functions of an input information acquisition means 301, a first amount output means 302, a second payment acceptance means 303, a first settlement means 304, a transaction information output means 305, a guidance means 306, and an execution means 307. The input information acquisition means 301 has the function of acquiring information from the input device 2 connected by the transmission cable 7. The input information acquisition means 301 acquires information related to purchased goods received by the input means 201 from the input device 2. The input information acquisition means 301 acquires the input termination instruction signal received by the termination acceptance means 202 from the input device 2. The input information acquisition means 301 acquires information on the payment method received by the first payment acceptance means 203 from the input device 2.

The first amount output means 302 is a function that outputs the amount required for settlement based on transaction information input via the input device 2. Transaction information includes, for example, information about purchased goods. This information includes the price and quantity sold. The first amount output means 302 calculates and outputs the amount required for settlement based on the price and quantity sold for each purchased item. The amount required for settlement can be rephrased as settlement amount, total amount, total amount including tax, invoice amount, etc. The first amount output means 302 outputs the amount required for settlement by displaying it on a display device. The display device is either the touch panel 23 or the display 25 of the input device 2. The display device may also be the first touch panel 32 or the second touch panel 34 of the transaction processing device 3.

The second payment acceptance means 303 is a function that accepts input of a payment method selection via a device operated by the customer. The device operated by the customer is, for example, a second touch panel 34. The second payment acceptance means 303 displays a payment method selection screen on the second touch panel 34. The second payment acceptance means 303 then accepts the payment method selected by touch operation on the screen as the selected payment method. The type of device is not particularly limited. The device operated by the customer may be a pointing device that moves a pointer displayed on the display. Payment methods include cash, credit card, electronic money, code payment, etc. The second payment acceptance means 303 accepts input of a payment method selection if the first payment acceptance means 203 has not accepted input of a payment method selection at the time the completion acceptance means 202 receives an input completion instruction. Whether or not input of a payment method selection has been accepted at the time the input completion instruction is received can be identified by the payment status ST. Specifically, when the payment status ST is "10," that is, when the first state is reached where no payment method is specified in the input device 2, the second payment receiving means 303 accepts the selection and input of one of the payment methods via the second touch panel 34.

The first settlement means 304 is a function that settles transactions with customers according to the payment method accepted by the first payment acceptance means 203 or the second payment acceptance means 303. The first settlement means 304 settles transactions with customers when settlement is possible at the time the termination acceptance means 202 receives the input termination instruction. That is, the first settlement means 304 determines that settlement is possible when the payment in progress flag Fa stored in the first flag memory 624 is "0". For example, if the first settlement means 304 accepts cash as the payment method, it settles the transaction with the customer in cooperation with the automatic change dispenser 36. For example, if the first settlement means 304 accepts cashless payment as the payment method, it settles the transaction with the customer in cooperation with the cashless payment terminal 37.

The transaction information output means 305 has the function of outputting transaction-related information to the holding server 1. When the input device 2 issues an instruction to end the input of transaction-related information while the transaction settlement is impossible, the transaction information output means 305 outputs the transaction-related information to the holding server 1. The transaction-related information is, for example, information related to purchased goods. Information related to purchased goods is stored as product sales data in the first transaction file 621 or the second transaction file 622. When the input information acquisition means 301 receives an input completion instruction signal while the payment in progress flag Fa in the first flag memory 624 is "1", the transaction information output means 305 controls the communication interface 65 to output the product sales data from the first transaction file 621 or the second transaction file 622 to the holding server 1.

The guidance means 306 is a function that guides the user to the output destination of information related to transactions held on the holding server 1. The output destination of the information related to transactions held on the holding server 1 is either the settlement device 4 or the transaction processing device 3. If the output destination of the transaction information is the settlement device 4, the guidance means 306 guides the user to pay the amount at the settlement device 4. If the output destination of the transaction information is the transaction processing device 3, the guidance means 306 guides the user to pay the amount at the transaction processing device 3. For example, guidance is provided to the store clerk or customer by displaying an image for guidance on a display device. The display device could be the touch panel 23 or display 25 of the input device 2, or the first touch panel 32 or second touch panel 34 of the transaction processing device 3, etc.

The execution means 307 is a function that executes settlement of transactions with customers based on information related to transactions held in the holding server 1. When the holding server 1 commands the execution of settlement, the execution means 307 operates the first amount output means 302 and the first settlement means 304 to execute the settlement of transactions with customers. Once the transaction processing device 3 determines the output destination for the transaction information held in the holding server 1, the transaction information is output from the holding server 1 to the transaction processing device 3 and stored, for example, in the second transaction file 622. When the holding server 1 commands the execution of settlement, the execution means 307 executes the settlement based on the transaction information stored in the second transaction file 622.

The display device 5 functions as a receiving means 501 and an instruction means 502. The receiving means 501 has the function of receiving the output destination for transaction information held by the holding server 1. As mentioned above, the output destination for transaction information is either the settlement device 4 or the transaction processing device 3. The receiving means 501 includes a first operator that declares that the output destination for transaction information is the settlement device 4, and a second operator that declares that the output destination for transaction information is the transaction processing device 3. When a tablet is used as the display device 5, the first and second operators are soft keys displayed on the tablet's LCD screen. When the first operator is input, the receiving means 501 accepts the settlement device 4 as the output destination for transaction information. When the second operator is input, the receiving means 501 accepts the transaction processing device 3 as the output destination for transaction information.

The instruction means 502 has the function of instructing the holding server 1 to output transaction-related information to the output destination received by the receiving means 501. If the output destination received by the receiving means 501 is the settlement device 4, the instruction means 502 instructs the holding server 1 to output transaction-related information to the settlement device 4. Specifically, the instruction means 502 outputs a signal to the holding server 1 instructing it to output transaction-related information to the settlement device 4. If the output destination received by the receiving means 501 is the transaction processing device 3, the instruction means 502 instructs the holding server 1 to output transaction-related information to the transaction processing device 3. Specifically, the instruction means 502 outputs a signal to the holding server 1 instructing it to output transaction-related information to the transaction processing device 3.

Furthermore, the display device 5 also functions as a display means 503. The display means 503 has the function of displaying transaction identification information, which identifies transactions for which transaction information has been output to the holding server 1 by the transaction information output means 305 of the transaction processing device 3, in a format readable by the reader device 9. Specifically, the display means 500 converts the transaction information into machine-readable codes such as barcodes and two-dimensional codes and displays them on the screen of the display device 5.

The reader device 9 includes a reading means 901. The reading means 901 has the function of reading transaction identification information displayed on the screen of the display device 5. For example, if the transaction identification information is displayed as a machine-readable code such as a barcode or a two-dimensional code, the reading means 901 scans and reads the machine-readable code with light. Alternatively, the reader device 9 reads the machine-readable code from an image captured by the camera.

The holding server 1 functions as a recognition means 101, a transaction information input means 102, a holding means 103, and a holding information output means 104. The recognition means 101 has the function of recognizing the output destination instructed by the display device 5. When the recognition means 101 receives a signal from the instruction means 502 of the display device 5 instructing it to output transaction-related information to the transaction processing device 3, it recognizes the transaction processing device 3 as the output destination. When the recognition means 101 receives a signal from the instruction means 502 of the display device 5 instructing it to output transaction-related information to the settlement device 4, it recognizes the settlement device 4 as the output destination.

The transaction information input means 102 is a function for inputting transaction-related information output from the transaction processing device 3. The transaction information input means 102 includes a process for identifying which transaction processing device 3 the input transaction-related information originated from. The transaction-related information includes the transaction processing device ID of the transaction processing device 3 that output the information. The transaction information input means 102 identifies the transaction processing device 3 identified by the transaction processing device ID as the source of the transaction-related information output.

The holding means 103 is a function for holding transaction-related information output from the transaction processing device 3. The holding means 103 holds the transaction-related information input by the transaction information input means 102 separately for each transaction processing device 3 identified as the source of that information output. Specifically, the holding means 103 stores the transaction-related information in lane-specific folders 132 of the settlement lane L where the transaction processing device 3 identified as the source of the transaction-related information is installed, thereby holding the transaction-related information separately for each transaction processing device 3.

The pending information output means 104 is a function that outputs transaction information to the settlement device 4 in response to an import request from the settlement device 4. Specifically, when the pending information output means 104 receives an import request from the settlement device 4, it identifies the settlement lane L where the settlement device 4 is installed and outputs the transaction information that was held in the lane-specific folder 132 of that settlement lane L to the settlement device 4.

The pending information output means 104 also has the function of outputting information related to transactions pending by the pending means 103 to an output destination indicated by the display device 5. The pending information output means 104 outputs the transaction information stored in the lane-specific folder 132 to the output destination indicated by the display device 5 if settlement is possible at that output destination. For example, if the output destination indicated by the display device 5 is the settlement device 4, the pending information output means 104 outputs the transaction information to the settlement device 4 if the payment in progress flag Fc of the settlement device 4 is "0". For example, if the output destination indicated by the display device 5 is the transaction processing device 3, the pending information output means 104 outputs the transaction information to the transaction processing device 3 if the payment in progress flag Fa of the transaction processing device 3 is "0".
Incidentally, the former reserved information output means 104 may be referred to as the first reserved information output means, and the latter reserved information output means 104 may be referred to as the second reserved information output means.

The settlement device 4 has the functions of an input means 401, a second amount output means 402, a third payment acceptance means 403, and a second settlement means 404. The input means 401 has the function of acquiring information relating to transactions held in the holding server 1. Specifically, the input means 401 has the function of acquiring information relating to transactions identified by transaction identification information read by the reading device 9 from the holding server 1. The input means 401 also has the function of acquiring information relating to transactions that the settlement device 4 has been instructed to output to by the display device 5. The input means 401 stores the transaction information acquired from the holding server 1 in the third transaction file 721.
Incidentally, the former intake means 401 may be referred to as the first intake means, and the latter intake means 401 may be referred to as the second intake means.

The second amount output means 402 is a function that outputs the amount required for settlement based on the transaction information held on the holding server 1. The second amount output means 402 outputs the amount required for settlement based on the transaction information acquired by the acquisition means 401. The second amount output means 402 outputs the amount required for settlement by displaying it on a display device. The display device is the touch panel 42 of the settlement device 4, etc.

The third payment acceptance means 403 is a function that accepts the selection input of a payment method via a device operated by the customer. The device operated by the customer is, for example, a touch panel 42. The third payment acceptance means 403 displays a payment method selection screen on the touch panel 42. The third payment acceptance means 403 then accepts the payment method selected by the customer via touch operation on the screen as the selected payment method. The type of device is not particularly limited. The device operated by the customer may also be a pointing device that moves a pointer displayed on the screen. Payment methods include cash, credit cards, electronic money, and code payments.

The second settlement means 404 is a function that settles transactions with customers according to the payment method accepted by the first payment acceptance means 203 or the third payment acceptance means 403. The second settlement means 404 settles transactions with customers when the amount equivalent to the amount output by the second amount output means 402 is paid using the payment method accepted by the first payment acceptance means 203 or the third payment acceptance means 403. For example, if cash is accepted as the payment method, the second settlement means 404 settles the transaction with the customer in cooperation with the automatic change dispenser 78. For example, if cashless payment is accepted as the payment method, the second settlement means 404 settles the transaction with the customer in cooperation with the cashless payment terminal 79.

The functions of the transaction processing device 3 as input information acquisition means 301, first amount output means 302, second payment acceptance means 303, first settlement means 304, transaction information output means 305, guidance means 306, and execution means 307 are all realized by information processing executed by the processor 61 according to the first business program.

The first business program is a type of application program stored in the main memory 62 or the auxiliary storage device 63. The method of installing the first business program in the main memory 62 or auxiliary storage device 63 is not particularly limited. The first business program can be installed in the main memory 62 or auxiliary storage device 63 by recording it on a removable recording medium or by distributing it via network communication. The recording medium can be of any form as long as it can store a program and is readable by the device, such as a CD-ROM or memory card.

The functions of the hold server 1 as recognition means 101, transaction information input means 102, hold means 103, and hold information output means 104 are realized by information processing executed by the processor 11 according to the second business program.

The second business program is a type of application program stored in the main memory 12 or the auxiliary storage device 13. The method of installing the second business program in the main memory 12 or auxiliary storage device 13 is not particularly limited. The second business program can be installed in the main memory 12 or auxiliary storage device 13 by recording it on a removable recording medium or by distributing it via network communication. The recording medium can be of any form as long as it can store a program and is readable by the device, such as a CD-ROM or memory card.

The functions of the payment device 4 as an input means 401, a second amount output means 402, a third payment acceptance means 403, and a second payment means 404 are realized by information processing executed by the processor 71 according to the third business program.

The third business program is a type of application program stored in the main memory 72 or the auxiliary storage device 73. The method of installing the third business program in the main memory 72 or auxiliary storage device 73 is not particularly limited. The third business program can be installed in the main memory 72 or auxiliary storage device 73 by recording it on a removable recording medium or by distributing it via network communication. The recording medium can be of any form as long as it can store a program and is readable by the device, such as a CD-ROM or memory card.

[Explanation of Payment System Operation]
Next, the main operations of the payment system 100 will be explained using the flowcharts in Figures 10 to 21 and the screen examples in Figures 22 to 48. Note that the content and procedures of the operations explained using the flowcharts are examples only. The content and procedures can be modified as appropriate if similar effects can be achieved. Similarly, the screen examples are also examples only. The content of the output text, the placement of images, the type and layout of software keys, etc., can be modified as appropriate.

Figures 10 to 13 are flowcharts showing the essential steps of the first information processing performed by the processor 61 of the transaction processing device 3 according to the first business program. A customer who has collected their purchased items from the sales floor moves to the checkout area. The customer then places their purchased items on the checkout counter 20 in an empty aisle PA. A store employee standing in space SP commands the customer to begin registration when they arrive at the checkout area. For example, the employee touches the start button displayed on the touch panel 23. This operation constitutes the command to begin registration. Upon receiving this command, the processor 61 begins the first information processing. The processor 61 uses the touch panel 23 and the display 25 screens of the input device 2 as the registration screen, designated as ACT 101.

Figure 22 shows an example of the registration screen SAa displayed on the touch panel 23. The registration screen SAa is divided into the current area AAa, the details area AAb, and the total area AAc. The current area AAa displays the product name, purchase quantity, and sales price of the most recently purchased items. The details area AAb displays the product name, purchase quantity, unit price, discount amount, and sales price of the purchased items in a single transaction in a list format, in sequential order. The total area AAc displays the total purchase quantity and total sales price of the purchased items in a single transaction. The registration screen SAa includes a subtotal button BAa. The subtotal button BAa is a software key. The subtotal button BAa is an operator used to command the output of the subtotal of the purchased items registered as a single transaction.

Figure 23 shows an example of the registration screen SBa displayed on the display 25. The registration screen SBa divides the screen into multiple rows (seven rows in the example in Figure 23). The rows from the first to the second-to-last row are designated as detail area ABa, and the last row is designated as total area ABb. Each row in detail area ABa displays the product name, unit price, purchase quantity, and sales amount for each purchased item. In total area ABb, the total purchase quantity and total sales amount are displayed on a single row.

After confirming the registration screen SAa, the store clerk registers the purchased items placed at the checkout counter 20. Specifically, the clerk scans the barcode attached to the purchased item using the stationary scanner 21 or handheld scanner 22 of the input device 2. By scanning the barcode, the product code of the purchased item is entered into the transaction processing device 3 via the input device interface 611. If the purchased item does not have a barcode, the clerk displays a list of barcode-less items on the touch panel 23 of the input device 2. The clerk then selects the purchased item from this list. Through this operation, the product code of the barcode-less purchased item is entered into the transaction processing device 3 via the input device interface 611.

The processor 61, with the touch panel 23 and display 25 screens set to registration screen SAa and registration screen SBa, proceeds to ACT 102. As ACT 102, the processor 61 awaits registration of purchased items. When a product code is entered from the input device 2 via the input device interface 611, the processor 61 determines that a purchased item has been registered. The processor 61 proceeds from ACT 102 to ACT 103. As ACT 103, the processor 61 processes the product sales data. This process reads the product name, unit price, etc., of the product identified by the entered product code from the product master, and generates product sales data for the purchased item, including the product code, product name, unit price, purchase quantity, sales amount, etc. Having generated the product sales data for the purchased item, the processor 61 proceeds to ACT 104. As ACT 104, the processor 61 writes and stores the product sales data for the purchased item in the first transaction file 621.

The processor 61, which has stored the product sales data for the purchased items, proceeds to ACT 105. As ACT 105, the processor 61 updates registration screens SAa and SBa.

Regarding the registration screen SAa, the processor 61 displays the product name, purchase quantity, and sales amount of the sales data written to the first transaction file 621 in the current area AAa. If the sales data for the previously registered purchase item is displayed in the current area AAa, the processor 61 displays the product name, purchase quantity, unit price, discount amount, and sales amount of the sales data in the details area AAb. Furthermore, the processor 61 displays the total purchase quantity and sales amount of all sales data stored in the first transaction file 621 in the total area AAc.

Regarding the registration screen SBa, the processor 61 displays the product name, unit price, purchase quantity, and sales amount of the sales data written to the first transaction file 621 on the first line of the detail area ABa. If sales data is already displayed on the first line of the detail area ABa, the processor 61 shifts the data from the first line onward to the second line and then displays the sales data written to the first transaction file 621 on the first line. The processor 61 also displays the total purchase quantity and sales amount of all product sales data stored in the first transaction file 621 in the total area AABb.

After updating registration screens SAa and SBa, processor 61 proceeds to ACT 106. As ACT 106, processor 61 checks whether the next purchase item has been registered. If the next purchase item has not been registered, processor 61 proceeds to ACT 107. As ACT 107, processor 61 checks whether the subtotal button BAa has been entered. If the subtotal button BAa has not been entered, processor 61 returns to ACT 106. In this way, processor 61 waits for the next purchase item to be registered or for the subtotal button BAa to be entered as ACT 106 and ACT 107.

When a purchased item is registered while ACT106 and ACT107 are in standby mode, processor 61 returns from ACT106 to ACT103. Processor 61 then executes the processing of ACT103 through ACT105 in the same manner as described above. Thus, each time a store clerk operates the stationary scanner 21, handheld scanner 22, or touch panel 23 of the input device 2 to input data for a purchased item placed on the checkout counter 20, processor 61 generates product sales data for that purchased item based on the product code and stores it in the first transaction file 621. Processor 61 also updates registration screens SAa and SBa. After completing the registration of the purchased items, the store clerk touches the subtotal button BAa.

When the subtotal button BAa is input via touch operation while ACT106 and ACT107 are in standby mode, the processor 61 proceeds to ACT108. As ACT108, the processor 61 uses the touch panel 23 and display 25 screens of the input device 2 as the subtotal screen.

Figure 24 shows an example of the subtotal plan area SAb displayed on the touch panel 23. The subtotal plan area SAb includes a total area AAd, which displays the total purchase quantity and total sales amount for a single transaction. The subtotal plan area SAb also includes a subtotal discount button BAb, a subtotal discount button BAc, a payment method selection button BAd, a payment button BAe, and a back button BAf. Each of the buttons BAb, BAc, BAe, and BAf is a software key. The subtotal discount button BAb is an operator used to command a discount on the total amount. The subtotal discount button BAc is an operator used to command a discount on the total amount. Incidentally, by pressing the subtotal discount button BAb and entering the discount amount using the numeric keypad on the keyboard 24, the total amount is discounted. Similarly, by pressing the subtotal discount button BAc and entering the discount rate using the numeric keypad on the keyboard 24, the total amount is discounted.

The payment method selection button BAd is an operator used to instruct the user to select a payment method. The payment button BAe is an operator used to instruct the user to complete the registration of purchased items and proceed to payment. The back button BAf is an operator used to instruct the user to return to the item registration screen.

Figure 25 shows an example of a subplanning screen SBb displayed on the display 25. The subplanning screen SBb includes area ABC, which displays information related to payment. Area ABC displays the total quantity and total price of purchased goods, the amount received, and the remaining balance. At this point, since no amount has been received, the amount received is 0 yen, and the remaining balance is the total amount minus the amount received.

After reviewing the sub-planning page SAb, the store clerk checks whether any unregistered purchased items remain at checkout counter 20. If there are unregistered items, the clerk touches the back button BAF. If there are no unregistered items, the clerk decides whether or not to confirm the payment method with the customer. For example, during busy hours, the clerk will confirm the payment method, while during off-peak hours, they will not. If the clerk decides to confirm the payment method, they touch the payment method selection button BAD. If the clerk decides not to confirm the payment method, they touch the payment button BAE.

The processor 61, with the touch panel 23 screen as subplanning plane SAb and the display 25 screen as subplanning plane SBb, proceeds to ACT 109. As ACT 109, the processor 61 checks whether the back button BAF has been input. If the back button BAF has not been input, the processor 61 proceeds to ACT 110. As ACT 110, the processor 61 checks whether the payment method selection button BAD has been input. If the payment method selection button BAD has not been input, the processor 61 proceeds to ACT 111. As ACT 111, the processor 61 checks whether the payment button BAE has been input. If the payment button BAE has not been input, the processor 61 returns to ACT 109. Thus, the processor 61, displaying the subplan plane SAb, waits for input from either the back button BAf, the payment method selection button BAd, or the payment button BAe in ACTs 109 to 111.

In the standby state of ACT 109 to ACT 111, when the back button BAf is pressed via touch operation, the processor 61 proceeds from ACT 109 to ACT 112. As ACT 112, the processor 61 returns the touch panel 23 and display 25 screens to the previous registration screen SAa and registration screen SBa. Then the processor 61 enters the standby state for ACT 106 and ACT 107. Thus, the store clerk can input data for unregistered purchased items by operating the stationary scanner 21, handheld scanner 22, or touch panel 23 of the input device 2.

In the standby state of ACTs 109 through 111, when the payment method selection button BAd is input via touch operation, the processor 61 proceeds from ACT 110 to ACT 121 as shown in Figure 11. For ACT 121, the processor 61 sets the touch panel 23 screen to the payment method selection screen SAc (see Figure 26). The display 25 screen remains the subplan screen SBb.

Figure 26 shows an example of the payment method selection screen SAc displayed on the touch panel 23. The payment method selection screen SAc includes a total area AAd, similar to the subplan area SAB. The payment method selection screen SAc also includes a group of selection buttons BAg for each payment method. The selection button group BAg includes a cash button, a credit button, an electronic money button, and a code payment button.

The cash button is for instructing cash payment. The credit button is for instructing credit card payment. The electronic money button is for instructing electronic money payment. The code payment button is for instructing code payment. The cash button, credit button, electronic money button, and code payment button are all software keys. The payment method selection screen SAc may also include a button for instructing payment with gift certificates or other monetary vouchers.

After the cashier checks the payment method selection screen (SAc), they confirm the payment method with the customer. The cashier then touches the button corresponding to the customer's chosen payment method. For example, if the customer wishes to pay with cash, the cashier touches the cash button in the selection button group (BAg). Similarly, if the customer wishes to pay with a credit card, the cashier touches the credit button in the selection button group (BAg). Likewise, if the customer wishes to pay with electronic money or code payment, the cashier touches the corresponding button in the selection button group (BAg).

The processor 61, with the touch panel 23 screen set to the payment method selection screen SAc, proceeds to ACT 122. The processor 61 waits for a payment method to be selected in ACT 122. When a payment method is selected via a touch operation on the selection button group Bag, the processor 61 proceeds to ACT 123. The processor 61 obtains the payment code for the selected payment method in ACT 123. In this embodiment, unique payment codes are pre-set for each payment method, such as cash payment, credit card payment, electronic money payment, and code payment. For example, if the cash button is touched, the processor 61 obtains the payment code corresponding to cash payment, for example, "11". For example, if the credit button is touched, the processor 61 obtains the payment code corresponding to credit card payment, for example, "22". The same applies when the other electronic money and code payment buttons are touched.

The processor 61, having obtained the payment code, proceeds to ACT 124. As ACT 124, the processor 61 sets the touch panel 23 screen to the payment screen SAd (see Figure 27). The display 25 screen remains the subplaning screen SBb.

Figure 27 shows an example of the payment screen SAd when cash payment is selected as the payment method. The payment screen SAd includes a total area AAd, similar to the subplan area SAb and the payment method selection screen SAc. The payment screen SAd also includes a payment button BAh. The payment button BAh is an operator used to command the customer to proceed to payment. The payment button BAh is a software key. After viewing the payment screen SAd, the store clerk touches the payment button BAh.

The processor 61, with the touch panel 23 displaying the payment screen SAd, proceeds to ACT 125. The processor 61 waits for the payment button BAh to be input as ACT 125. Once the payment button BAh is input via touch operation, the processor 61 proceeds to ACT 126.

On the other hand, in the standby state of ACTs 109 to 111 in Figure 10, when the payment button BAe is input via touch operation, the processor 61 proceeds from ACT 111 to ACT 126 in Figure 11. Similarly, when the payment button BAe on the subplanning screen SAb or the payment button BAh on the payment screen SAd is input, the processor 61 proceeds to ACT 126.

Processor 61 checks the payment flag Fa as ACT 126. If payment has not been made by the transaction processing unit 3, the payment flag Fa is "0". When the payment flag Fa is "0", processor 61 proceeds from ACT 126 to ACT 131 in Figure 12. The processing from ACT 131 onwards will be described later.

In ACT 126, if the payment flag Fa is "1," meaning that payment is being processed by the transaction processing unit 3, the processor 61 proceeds to ACT 127. In ACT 127, the processor 61 checks the pending flag Fb. If no information related to the previous customer's transaction settled in the same settlement lane L is being held by the holding server 1, the pending flag Fb is "0." When the pending flag Fb is "0," the processor 61 proceeds from ACT 128 to ACT 141 in Figure 13. The processing from ACT 141 onwards will be described later.

If the pending flag Fb in ACT 127 is "1," meaning that information related to the transaction of the previous customer who settled in the same settlement lane L is being held in the pending server 1, the processor 61 proceeds to ACT 128. As ACT 128, the processor 61 displays a pop-up PUa (see Figure 28) on the subplanning screen SAb or payment screen SAd of the touch panel 23, informing the user that payment is impossible. The processor 61 also displays text TXa (see Figure 29) on the subplanning screen SBb of the display 25, instructing the user to wait because payment is impossible.

Figure 28 shows an example of a pop-up PUa displayed on the payment screen SAd of the touch panel 23. Upon seeing the pop-up PUa, the store clerk will wait until the previous customer has finished paying.

Figure 29 shows an example of text TXa displayed on the subplanning surface SBb of display 25. Customers who view text TXa will wait until they are able to pay.

The processor 61, having received notification via the touch panel 23 and display 25 that payment is impossible, returns to ACT 125. The processor 61 waits for the payment button BAe or BAh to be pressed again. Once BAe or BAh is pressed, the processor 61 proceeds to ACT 126. The processor 61 then executes the processes from ACT 126 onward in the same manner as described above. Therefore, if the payment in progress flag Fa has been changed to "0", the processor 61 proceeds to ACT 131 in Figure 12. If the payment in progress flag Fa remains "1" but the pending flag Fb has been changed to "0", the processor 61 proceeds to ACT 141 in Figure 13.

Conversely, if the payment in progress flag Fa and the pending flag Fb remain at "1", the processor 61 proceeds to ACT 128. Therefore, the pop-up PUa continues to be displayed on the subplanning surface SAb or payment screen SAd of the touch panel 23, and the text TXa continues to be displayed on the subplanning surface SBb of the display 25.

When the payment flag Fa is "0," meaning that payment has not yet been made in the transaction processing device 3, and the payment button BAe on the subplanning screen SAb or the payment button BAh on the payment screen SAd is pressed, the processor 61 proceeds to ACT 131 in Figure 12. As ACT 131, the processor 61 displays a pop-up PUb (see Figure 30) on the subplanning screen SAb or payment screen SAd of the touch panel 23, informing the user that payment is possible in the transaction processing device 3. The processor 61 also displays text TXb (see Figure 31) on the subplanning screen SBb of the display 25, indicating that payment is possible.

Figure 30 shows an example of a pop-up Pub displayed on the payment screen SAd of the touch panel 23. Upon seeing the pop-up Pub, the store clerk will know that payment is possible using the transaction processing device 3, and will then guide the customer to the area where the transaction processing device 3 is located.

Figure 31 shows an example of text TXb displayed on the subplanning surface SBb of the display 25. After viewing the text TXb, the customer will follow the instructions of the store clerk to the area where the transaction processing device 3 is located and make the payment.

Having notified the user that payment is possible using the touch panel 23 and display 25, the processor 61 proceeds to ACT 132. As ACT 132, the processor 61 controls the second transaction file 622 to store the data stored in the first transaction file 621—that is, the product sales data of the purchased goods registered as a single transaction.

Once the product sales data for the purchased items registered as a single transaction in the second transaction file 622 has been stored, the processor 61 proceeds to ACT 133. The processor 61 then checks whether or not it has obtained a payment code as ACT 133.

If the payment code has not been obtained, processor 61 proceeds from ACT 133 to ACT 134. Processor 61 sets the payment status ST stored in status memory 623 as "10" in ACT 134. Conversely, if the payment code was obtained during the processing of ACT 123, processor 61 proceeds from ACT 133 to ACT 135. Processor 61 adds the payment code to the second transaction file 622 as ACT 135. Processor 61 also sets the payment status ST stored in status memory 623 as "20" in ACT 136.

After completing ACT 134 or ACT 136, processor 61 proceeds to ACT 137. As ACT 137, processor 61 rewrites the payment flag Fa in the first flag memory 624 to "1". Also, as ACT 138, processor 61 clears the first transaction file 621. With this, processor 61 completes the first information processing.

On the other hand, if the payment in progress flag Fa is "1" but the pending flag Fb is "0", and the payment button BAe on subplan screen SAb or the payment button BAh on payment screen SAd is input, the processor 61 proceeds to ACT 141 in Figure 13. The processor 61 checks whether a payment code has been obtained as ACT 141. If a payment code has not been obtained, the processor 61 proceeds from ACT 141 to ACT 142. The processor 61 sets the payment status ST stored in the status memory 623 as "10" as ACT 142. Conversely, if a payment code was obtained during the processing of ACT 123, the processor 61 proceeds from ACT 141 to ACT 143. The processor 61 adds that payment code to the first transaction file 621 as ACT 143. The processor 61 also sets the payment status ST stored in the status memory 623 as "20" as ACT 144.

After completing ACT142 or ACT144, the processor 61 proceeds to ACT145. As ACT145, the processor 61 generates transaction identification information. For example, the processor 61 generates unique transaction identification information by concatenating the transaction processing unit ID, which is unique information of the transaction processing unit 3, with the date (year, month, day) and time (hour, minute, second) of the transaction. Alternatively, the processor 61 may increment a counter that generates a serial number by "1" and concatenate that serial number to the transaction processing unit ID to generate unique transaction identification information.

The processor 61, which generated the transaction identification information, proceeds to ACT 146. As ACT 146, the processor 61 sends a hold event to the hold server 1 via the communication interface 65. The hold event is an event requesting the hold of the first transaction file 621. The hold event includes the transaction processing unit ID of the transaction processing unit 3.

As will be explained in detail later, the pending server 1, upon receiving the pending event, sends back an acceptance response. The processor 61 then waits for the acceptance response as ACT 147. Upon receiving the acceptance response via the communication interface 65, the processor 61 proceeds to ACT 148. As ACT 148, the processor 61 outputs the data stored in the first transaction file 621—that is, the product sales data, which is information related to the purchased goods to be processed as a single transaction—along with the transaction identification information generated in ACT 145, to the pending server 1.

Subsequently, processor 61 sets the pending flag Fb to "1" as ACT 149. Processor 61 also clears the first transaction file 621 as ACT 150. With this, processor 61 completes the first information processing.

As explained using Figure 12, when the payment button BAe or payment screen SAd is pressed, if the payment flag Fa is "0," meaning there are no customers currently paying at the transaction processing device 3, the system notifies that payment is possible at the transaction processing device 3. The payment flag Fa then becomes "1," and the first transaction file 621 is cleared. Therefore, the customer proceeds to the location where the transaction processing device 3 is installed to make the payment.

On the other hand, as explained using Figure 13, when the payment button BAe or payment screen SAd is pressed, if the payment flag Fa is "1," that is, if a customer is paying using the transaction processing device 3, the data in the first transaction file 621 is output to the hold server 1 along with unique transaction identification information. Also, the hold flag Fb becomes "1," and the first transaction file 621 is cleared. At this point, it is not yet determined whether the customer will pay using the transaction processing device 3 or the settlement device 4.

As explained using Figures 12 and 13, once the first information processing is complete, the first transaction file 621 is cleared by the processing of ACT 138 or ACT 150. Therefore, the processor 61 of the transaction processing device 3 can then begin the first information processing. That is, when the next customer arrives at the checkout counter and the cashier commands the start of registration, the processor 61 executes the first information processing from ACT 101 onwards in the same manner as described above. Therefore, the screen of the touch panel 23 becomes the registration screen SAa.

Here, the processor 61 functions as an input information acquisition means (first input information acquisition means) 301, acquiring information related to purchased goods received by the input means 201 from the input device 2 by executing the processing of ACT 102 and ACT 106 via the input device interface 611. Furthermore, the processor 61 functions as an input information acquisition means (second input information acquisition means) 301, acquiring input termination instruction signals received by the termination reception means 202 from the input device 2 by executing the processing of ACT 111 and ACT 125 via the input device interface 611. Finally, the processor 61 functions as an input information acquisition means (third input information acquisition means) 301, acquiring payment method information received by the first payment reception means 203 from the input device 2 by executing the processing of ACT 121 to ACT 123 via the input device interface 611.

The processor 61, in cooperation with the touch panel 23 and the display 25, executes the processing of ACT 108 and ACT 124, thereby realizing the function of the first monetary amount output means 302. The processor 61, in cooperation with the communication interface 65, executes the processing of ACT 145 to ACT 147, thereby realizing the function of the transaction information output means 305.

Figure 14 is a flowchart showing the essential steps of the second information processing performed by the processor 61 of the transaction processing device 3 according to the first business program. The processor 61 performs the second information processing in parallel with the first information processing described above.

Processor 61 waits for the payment flag Fa to become "1" as ACT 151. When the payment flag Fa becomes "1" in ACT 137 of the first information processing, processor 61 proceeds to ACT 152. Processor 61 checks the payment status ST as ACT 152. If the payment status ST is "10," meaning no payment method was selected in the first information processing, processor 61 proceeds from ACT 152 to ACT 153. Processor 61 sets the screen of the second touch panel 34 to the payment method selection screen SCa (see Figure 32) as ACT 153.

Figure 32 shows an example of the payment method selection screen SCa displayed on the second touch panel 34. The payment method selection screen SCa includes a group of selection buttons BCa for each payment method. The selection button group BCa includes a cash button, a credit button, an electronic money button, and a code payment button. The payment method selection screen SCa also includes a total area ACa that displays the total purchase quantity and total sales amount for a single transaction. The total area ACa displays the total purchase quantity and total sales amount calculated based on the product sales data of the purchased items stored in the second transaction file 622.

After viewing the payment method selection screen SCa, the customer touches the button corresponding to their desired payment method. For example, a customer wishing to pay with cash touches the cash button in the selection button group BCa. A customer wishing to pay with a credit card touches the credit button in the selection button group BCa. A customer wishing to pay with electronic money touches the electronic money button in the selection button group BCa. A customer wishing to pay with QR code payment touches the QR code payment button in the selection button group BCa.

The processor 61, with the second touch panel 34 screen set to the payment method selection screen SCa, proceeds to ACT 154. As ACT 154, the processor 61 waits for a payment method to be selected. Once a payment method is selected via touch operation on the selection button group BCa, the processor 61 proceeds to ACT 155. As ACT 155, the processor 61 obtains the payment code for the selected payment method, similar to the processing in ACT 123 of the first information processing.

On the other hand, if the payment status ST in ACT 152 is "20," meaning that the payment method was selected in the first information processing, the processor 61 proceeds from ACT 152 to ACT 156. As ACT 156, the processor 61 extracts the payment code from the second transaction file 622.

After completing ACT 155 or ACT 156, the processor 61 proceeds to ACT 157. For ACT 157, the processor 61 sets the screen of the second touch panel 34 to the payment notification screen SCb (see Figure 33). The payment notification screen SCb is a screen based on the payment code obtained through the processing of ACT 155 or ACT 156.

Figure 33 shows an example of the payment notification screen SCb displayed on the second touch panel 34. Figure 33 shows the payment notification screen SCb when a payment code for cash payment is obtained through the processing of ACT 155 or ACT 156. The payment notification screen SCb includes a change dispenser information area ACb. The change dispenser information area ACb displays the total amount, the total amount of cash inserted into the automatic change dispenser 36 (i.e., the inserted amount), and the remaining amount after subtracting the inserted amount from the total amount.

After confirming the payment notification screen SCb, the customer pays using their chosen payment method. For example, a customer who chooses cash payment inserts cash into the automatic change dispenser 36. A customer who chooses credit card payment has their credit card data read by the reader of the cashless payment terminal 37. A customer who chooses electronic money payment has their electronic money data read by the reader of the cashless payment terminal 37. A customer who chooses QR code payment has their barcode or QR code for QR code payment read by the scanner of the cashless payment terminal 37.

When the second touch panel 34 displays the payment notification screen SCb, the processor 61 proceeds to ACT 158. The processor 61 waits for the payment to begin as ACT 158. For example, if cash payment is selected, the processor 61 waits for cash to be inserted into the automatic change dispenser 36. For example, if credit card payment is selected, the processor 61 waits for the credit card data to be read by the cashless payment terminal 37. For example, if electronic money payment is selected, the processor 61 waits for the electronic money data to be read by the cashless payment terminal 37. For example, if code payment is selected, the processor 61 waits for the barcode or two-dimensional data code for code payment to be read by the cashless payment terminal 37.

When payment begins, processor 61 proceeds from ACT 158 to ACT 159. Processor 61 issues a transaction number as ACT 159. The transaction number is a seven-digit number, for example, a three-digit transaction processing unit ID followed by a four-digit serial number. The serial number is incremented by "1" each time a transaction is settled in transaction processing unit 3. After issuing the transaction number, processor 61 proceeds to ACT 160. As ACT 160, processor 61 sets the screen of the second touch panel 34 to the payment progress screen SCc (see Figure 34).

Figure 34 shows an example of the payment screen SCc displayed on the second touch panel 34. Figure 34 shows the payment screen SCc when a cash payment code is obtained through the processing of ACT 155 or ACT 156. The payment screen SCc has the same layout as the payment notification screen SCb. The information displayed in the cash payment screen SCc, in the change dispenser information area ACb, is updated according to the amount of cash inserted into the automatic change dispenser 36. The payment screen SCc also includes a payment button BCb. The payment button BCb is a software key. The payment button BCb is an operator used to signal the completion of payment. A customer who has finished paying using their selected payment method touches the payment button BCb.

When the second touch panel 34 screen is set to the payment screen SCc, the processor 61 proceeds to ACT 161. As ACT 161, the processor 61 waits for the payment button BCb to be input. When the payment button BCb is input by touch operation, the processor 61 proceeds to ACT 162. As ACT 162, the processor 61 executes the transaction settlement process based on the payment code. That is, if the payment code is a cash payment code, the processor 61 executes the transaction settlement process with the cash inserted into the automatic change dispenser 36. If the payment code is a credit card payment code, the processor 61 executes the transaction settlement process with the credit card data read by the cashless payment terminal 37. If the payment code is an electronic money payment code, the processor 61 executes the transaction settlement process with the electronic money data read by the cashless payment terminal 37. If the payment code is a code for code-based payment, the processor 61 executes the transaction settlement process using the barcode or two-dimensional data code read by the cashless payment terminal 37. Since these settlement processes are well-known, a detailed explanation is omitted.

Once the payment processing is complete, processor 61 proceeds to ACT 163. As ACT 163, processor 61 drives printer 35 to issue a receipt. Processor 61 also sets the screen of the second touch panel 34 to the payment completion screen SCd (see Figure 35) as ACT 164. The receipt is a sheet recording details such as the product name, price, quantity, and total amount of the purchased items. The receipt also records the transaction date, time, and transaction number.

Figure 35 shows an example of the payment completion screen SCd displayed on the second touch panel 34. Figure 35 shows the payment completion screen SCd when a payment code for cash payment is obtained through the processing of ACT 155 or ACT 156. The payment completion screen SCd includes a change dispenser information area ACb, similar to the payment notification screen SCb and the payment in progress screen SCc. After confirming the payment completion screen SCd, the customer takes their receipt and change and leaves the store.

The processor 61, displaying the payment completion screen SCd, proceeds to ACT 165. As ACT 165, the processor 61 saves the data stored in the second transaction file 622—that is, the data of the goods purchased by the customer who completed the payment. The data is saved to, for example, the auxiliary storage device 63. Alternatively, the data may be saved to the main memory 62. Or, the data from the second transaction file 622 may be sent to the POS server via the communication interface 65 and saved on the POS server. Alternatively, the data may be saved on the hold server 1 instead of the POS server.

The processor 61, having saved the data from the second transaction file 622, proceeds to ACT 166. As ACT 166, the processor 61 clears the second transaction file 622. Then, as ACT 167, the processor 61 rewrites the payment flag Fa to "0". With this, the processor 61 terminates the second information processing.

Here, the processor 61, in cooperation with the second touch panel 34, executes the processing of ACT 157, thereby realizing the function of the first amount output means 302. The processor 61, in cooperation with the second touch panel 34, executes the processing of ACTs 153 to ACT 154, thereby realizing the function of the second payment acceptance means 303. The processor 61, by executing the processing of ACT 162, realizes the function of the first settlement means 304.

Thus, when the payment flag Fa is "0" and the payment button BAe on the subplan screen SAb or the payment button BAh on the payment screen SAd is pressed, and the payment flag Fa becomes "1", the processor 61 executes the processes of ACT 152 to ACT 167. Based on this process, the transaction processing device 3 operates, allowing the customer to settle the transaction by operating the transaction processing device 3 themselves.

Figure 15 is a flowchart showing the essential steps of the third information processing performed by the processor 61 of the transaction processing device 3 according to the first business program. The processor 61 performs the third information processing in parallel with the first information processing described above.

Processor 61 waits for the pending flag Fb to become "1" as ACT 171. In ACT 148 of the first information processing, when the pending flag Fb becomes "1", processor 61 proceeds to ACT 172. Processor 61 checks whether a release event has been received from the pending server 1 as ACT 172. If a release event has not been received, processor 61 proceeds to ACT 173. Processor 61 checks whether a confirmation event has been received as ACT 173. If a confirmation event has not been received, processor 61 returns to ACT 172. Thus, in ACT 172 and ACT 173, processor 61 of the transaction processing unit 3, when the pending flag Fb becomes "1", waits to receive either a release event or a confirmation event from the pending server 1 that sent the pending event.

To clarify the release and confirmation events, we will temporarily suspend the explanation of Figure 15 and first explain the information processing performed by the processor 11 of the hold server 1 using Figures 16 to 18.

Figures 16 to 18 are flowcharts showing the essential steps of the fourth information processing performed by the processor 11 of the hold server 1 according to the second business program. The processor 11 is waiting for a hold event as ACT 201. Upon receiving a hold event via the communication interface 15, the processor 11 proceeds to ACT 202. The processor 11 replies with an acceptance response as ACT 202. That is, the processor 11 replies with an acceptance response to the transaction processing device 3 identified by the transaction processing device ID included in the hold event.

As explained using Figure 13, when the processor 61 of the transaction processing device 3 that sent the hold event receives the acceptance response, it outputs the data of the first transaction file 621 along with the transaction identification information to the hold server 1. The processor 11 that sent the acceptance response then waits for the data of the first transaction file 621 as ACT 203. Upon receiving the data of the first transaction file 621 via the communication interface 15, the processor 11 proceeds to ACT 204. As ACT 204, the processor 11 obtains the transaction processing device ID set for the transaction processing device 3 that sent the data. The transaction processing device ID is included in the hold event. The transaction processing device ID may also be included in the data of the first transaction file 621.

The processor 11, having detected the transaction processing unit ID, proceeds to ACT 205. As ACT 205, the processor 11 obtains the lane number of the settlement lane L where the data-sending transaction processing unit 3 is located. Specifically, the processor 11 refers to the lane table 131 and obtains the lane number described in column Ca on the same row as the transaction processing unit ID.

The processor 11, having obtained the lane number, proceeds to ACT 206. The processor 11 saves the data of the first transaction file 621 received from the transaction processing unit 3 to the lane-specific folder 132, which is identified by the lane number obtained as ACT 206.

Next, processor 11 acquires transaction identification information received along with the data from the first transaction file 621 as ACT 207. Then, processor 11 stores this transaction identification information in the transaction identification information memory 626 as ACT 208. Furthermore, processor 11, as ACT 209, refers to the lane table 131 and acquires the settlement device ID described in column Cc on the same row as the transaction processing device ID. Then, processor 11 sends a first execution event as ACT 210 to the settlement device 4 identified by that settlement device ID. The first execution event is an event requesting the execution of settlement processing.

As will be explained later using Figure 20, the settlement device 4, upon receiving the first execution event, sends back either an acceptance response or a rejection response. An acceptance response is sent back if the settlement device 4 can settle the transaction. A rejection response is sent back if the settlement device 4 cannot settle the transaction.

The processor 11, which sent the first execution event, proceeds to ACT 211. The processor 11 checks whether it received an acceptance response as ACT 211. If an acceptance response is received, the processor 11 proceeds to ACT 221 in Figure 17. The processor 221 generates a machine-readable code representing the transaction identification information stored in the transaction identification information memory 626 as ACT 221. For example, the processor 11 generates a barcode representing the transaction identification information. The barcode's code system is not particularly limited. Essentially, any barcode with a code system readable by the reader 9, i.e., a machine-readable code, is acceptable.

The processor 11, having generated the machine-readable code, proceeds to ACT 222. As ACT 222, the processor 11 refers to the lane table 131 and obtains the display device ID described in column Cd of the same row as the transaction processing device ID. Then, as ACT 223, the processor 11 outputs the data for the display screen to the display device 5 identified by that display device ID.

When the display device 5 receives the data from the reading screen, the reading screen SDa (see Figure 36) is displayed on the tablet's LCD screen.
Figure 36 shows an example of the display on the reading screen SDa. As shown in the figure, the machine-readable code BC created by the processing of ACT221 is displayed on the reading screen SDa. In this embodiment, the machine-readable code BC is a barcode. The machine-readable code BC is not limited to a barcode. For example, it may be a two-dimensional code. The display device 5, which displays such a reading screen SDa, realizes the function of a display means 503.

Incidentally, when the reading screen SDa is displayed on the display device 5, the machine-readable code is read by the reader 9. The reader 9 then outputs the read machine-readable code data to the settlement device 4. As will be explained in detail later using Figure 19, when the machine-readable code of the transaction identification information is read by the reader 9, the processor 71 of the settlement device 4 sends a request event to the holding server 1. The request event is an event requesting the acquisition of transaction-related information. The request event includes the transaction identification information reconstructed from the machine-readable code read by the reader 9.

Therefore, the processor 11 of the holding server 1, which output the data from the reading screen, waits for a request event as ACT 224. Upon receiving a request event from the payment device 4, the processor 11 proceeds to ACT 225. As ACT 225, the processor 11 erases the reading screen SDa displayed on the display device 5. The processor 11 also obtains transaction identification information from the request event as ACT 226. Furthermore, as ACT 227, the processor 11 obtains the payment device ID of the payment device 4 that sent the request event. The request event includes the payment device ID set in the payment device 4 that sent the event. Note that the timing of erasing the reading screen SDa is not limited to the timing of ACT 225 processing. It is sufficient to erase it after receiving the request event from the payment device 4.

The processor 11, having obtained the payment device ID, proceeds to ACT 228. As ACT 228, the processor 11 obtains the lane number of the payment lane L where the payment device 4, identified by the payment device ID, is installed. Specifically, the processor 11 refers to the lane table 131 using the payment device ID obtained in ACT 227 and retrieves the lane number described in column Ca on the same row as the payment device ID. The payment device ID is included in the request event.

The processor 11, having obtained the lane number, proceeds to ACT 229. As ACT 229, the processor 11 selects a pending file. Specifically, the processor 11 selects the data of the first transaction file 621 stored in the lane-specific folder 132 corresponding to the lane number obtained in ACT 228. Then, as ACT 230, the processor 11 transmits the pending file to the settlement device 4. That is, the processor 11 transmits the data of the first transaction file 621 obtained in ACT 229 to the settlement device 4, which is identified by the settlement device ID obtained in the processing of ACT 227.

The processor 11, which sent the pending file, proceeds to ACT 231. As ACT 231, the processor 11 sends a release event to the transaction processing unit 3, which is the data source of the first transaction file 621. That is, the processor 11 sends a release event to the transaction processing unit 3, which is identified by the transaction processing unit ID obtained in the processing of ACT 204. The release event is an event that commands the pending state to be released.

The processor 11, having sent the release event, proceeds to ACT 232. As ACT 232, the processor 11 clears the pending files. Specifically, the processor 11 clears the data from the first transaction file 621, which was saved in the lane-specific folder 132 corresponding to the lane number obtained in ACT 227. With this, the processor 11 completes the fourth information processing step.

On the other hand, if a negative response is received in ACT 211 in Figure 16, the processor 11 proceeds to ACT 212. As ACT 212, the processor 11 sends a confirmation event to the transaction processing unit 3, which is the data source of the first transaction file 621. That is, the processor 11 sends a confirmation event to the transaction processing unit 3 identified by the transaction processing unit ID obtained in the processing of ACT 204. The confirmation event prompts the store clerk to confirm the payment recipient. Furthermore, as ACT 213, the processor 11 refers to the lane table 131 and obtains the display device ID described in column Cd on the same row as the transaction processing unit ID. Then, as ACT 214, the processor 11 outputs instruction screen data to the display device 5 identified by that display device ID.

When the display device 5 receives the data from the instruction screen, the instruction screen SDb (see Figure 37) is displayed on the LCD screen of the tablet.
Figure 37 shows an example of the display of the instruction screen SDb. The instruction screen SDb displays an import button BDa and a return button BDb. The import button BDa and the return button BDb are soft keys. The import button BDa functions as a first operator that declares that the destination for outputting transaction information is the settlement device 4. The return button BDb functions as a second operator that declares that the destination for outputting transaction information is the transaction processing device 3. The display device 5, displaying such an instruction screen SDb, realizes the function of a reception means 501.

The employee who has decided on the payment recipient operates the display device 5 based on that decision. Specifically, an employee who has decided on the payment device 4 as the payment recipient inputs the "Save" button BDa. When the "Save" button BDa is input, the display device 5 outputs a first signal to the hold server 1. The first signal is a signal output in response to the input of the "Save" button BDa. The first signal indicates that the payment device 4 has been selected as the payment recipient. An employee who has decided on the transaction processing device 3 as the payment recipient inputs the "Return" button BDb. When the "Return" button BDb is input, the display device 5 outputs a second signal to the hold server 1. The second signal is a signal output in response to the input of the "Return" button BDb. The second signal indicates that the transaction processing device 3 has been selected as the payment recipient. The display device 5 that outputs such a first or second signal functions as an instruction means 502.

The processor 11, having output the data from the instruction screen SDb, proceeds to ACT 241 in Figure 18. As ACT 241, the processor 11 checks whether the capture button BDa has been input. If the capture button BDa has not been input, the processor 11 proceeds to ACT 242. As ACT 242, the processor 11 checks whether the return button BDb has been input. If the return button BDb has not been input, the processor 11 returns to ACT 241. In this way, the processor 11 waits for either the capture button BDa or the return button BDb on the instruction screen SDb to be input in ACT 241 and ACT 242.

When the processor 11 receives the first signal from the display device 5 while in the standby state of ACT241 and ACT242, it recognizes that the capture button BDa has been pressed. The processor 11 then proceeds to ACT243. As ACT243, the processor 11 sends a second execution event to the payment device 4. Specifically, the processor 11 sends the second execution event to the payment device 4 identified by the payment device ID obtained in the processing of ACT209. The second execution event is also an event requesting the execution of payment processing.

As will be explained later using Figure 20, the settlement device 4, upon receiving the second execution event, sends back either an acceptance response or a rejection response. An acceptance response is sent back if the settlement device 4 can settle the transaction. A rejection response is sent back if the settlement device 4 cannot settle the transaction.

The processor 11, having sent the second execution event, proceeds to ACT 244. As ACT 244, the processor 11 checks whether or not it received an acceptance response. If an acceptance response is received, the processor 11 proceeds to ACT 245. As ACT 245, the processor 11 sends the pending file to the settlement device 4. That is, the processor 11 sends the data from the first transaction file 621, stored in the lane-specific folder 132 corresponding to the lane number obtained in ACT 205, to the settlement device 4, identified by the settlement device ID obtained in the processing of ACT 209.

The processor 11, which sent the pending file, proceeds to ACT 246. As ACT 246, the processor 11 sends a release event to the transaction processing unit 3, which is the data source of the first transaction file 621. That is, the processor 11 sends a release event to the transaction processing unit 3, which is identified by the transaction processing unit ID obtained in the processing of ACT 204. The release event is an event that commands the pending state to be released.

The processor 11, having sent the release event, proceeds to ACT 247. As ACT 247, the processor 11 clears the pending files. Specifically, the processor 11 clears the data of the first transaction file 621, which was saved in the lane-specific folder 132 corresponding to the lane number acquired in ACT 205. The processor 11 also erases the instruction screen SDb displayed on the display device 5 as ACT 248. With this, the processor 11 completes the fourth information processing step.

Meanwhile, in the standby state of ACT241 and ACT242, upon receiving the second signal from the display device 5, the processor 11 recognizes that the back button BDb has been pressed. The processor 11 then proceeds to ACT249. As ACT249, the processor 11 sends a third execution event to the transaction processing device 3, which is the data source of the first transaction file 621. That is, the processor 11 sends the third execution event to the transaction processing device 3 identified by the transaction processing device ID obtained in the processing of ACT204. The third execution event is also an event requesting the execution of settlement processing.

As will be explained later using Figure 15, the transaction processing unit 3, upon receiving the third execution event, sends back either an acceptance response or a rejection response. An acceptance response is sent back by the transaction processing unit 3 if settlement of the transaction is possible. A rejection response is sent back by the transaction processing unit 3 if settlement of the transaction is not possible.

The processor 11, which sent the third execution event, proceeds to ACT 250. As ACT 250, the processor 11 checks whether or not it received an acceptance response. If an acceptance response is received, the processor 11 proceeds to ACT 251. As ACT 251, the processor 11 sends the pending file to the transaction processing unit 3. That is, the processor 11 sends the data of the first transaction file 621, which was stored in the lane-specific folder 132 corresponding to the lane number obtained in ACT 205, to the transaction processing unit 3, which is identified by the transaction processing unit ID obtained in the processing of ACT 204.

The processor 11, having sent the pending file, proceeds to ACT 252. As ACT 252, the processor 11 clears the pending file. Specifically, the processor 11 clears the data of the first transaction file 621, which was saved in the lane-specific folder 132 corresponding to the lane number acquired in ACT 205. The processor 11 also erases the instruction screen SDb displayed on the display device 5 as ACT 253. With this, the processor 11 completes the fourth information processing step.

If a negative response is received in ACT244 or ACT250, the processor 11 proceeds to ACT254. The processor 11 outputs error screen data to the display device 5 as ACT254. Specifically, the processor 11 outputs screen data indicating that the operation on the instruction screen is incorrect to the display device 5, which is identified by the display device ID obtained in the processing of ACT213. This screen includes an operator (soft key) to command the error clearing. The store clerk, upon seeing the error screen, inputs the operator commanding the error clearing.

The processor 11, having output the error screen data, proceeds to ACT 255. The processor 11 waits for an error clearing command as ACT 255. Upon receiving a signal from the display device 5 resulting from the input of an error clearing command, the processor 11 recognizes that an error clearing command has been issued. The processor 11 then proceeds to ACT 256. As ACT 256, the processor 11 outputs the instruction screen SDb data to the display device 5 that issued the error clearing command. That is, the processor 11 outputs the instruction screen SDb data to the display device 5 identified by the display device ID obtained in the processing of ACT 213. Thereafter, the processor 11 returns to the waiting state for ACT 241 and ACT 242.

For example, a store clerk might press the import button BDa to instruct the payment device 4 as the output destination for transaction information, but the payment device 4 might not yet have finished processing the previous customer's payment. In such cases, the display device 5 screen will show an error screen, and the store clerk will perform an error clearing operation. The display device 5 screen will then return to the instruction screen SDb, and the store clerk can wait for the previous customer to finish processing the payment before pressing the import button BDa again. Alternatively, if the customer processing the payment using the transaction processing device 3 finishes the payment first, the store clerk can press the return button BDb.

Here, the processor 11 functions as a transaction information input means 102 by cooperating with the communication interface 15 to execute the processing of ACT 201 and ACT 203. The processor 11 functions as a holding means 103 by cooperating with the lane-specific folders 132 to execute the processing of ACT 204 to ACT 206. The processor 11 functions as a holding information output means (first holding information output means) 104 by executing the processing of ACT 223 to ACT 230. The processor 11 functions as a recognition means 101 by cooperating with the communication interface 15 to execute the processing of ACT 241 and ACT 242. The processor 11 functions as a holding information output means (second holding information output means) 104 by cooperating with the communication interface 15 to execute the processing of ACT 243 to ACT 245 and ACT 249 to ACT 251.

Let's return to the explanation of Figure 15.
When the processor 61 receives a release event while in the waiting state for ACT 172 and ACT 173, it proceeds to ACT 174. As ACT 174, the processor 61 displays a pop-up PUc (see Figure 38) on the subplanning surface SAb or payment screen SAd of the touch panel 23 to guide the customer to make a payment at the payment device 4. The processor 61 also displays text TXc (see Figure 39) on the subplanning surface SBb of the display 25 to instruct the customer to make a payment at the payment device 4.

Figure 38 shows an example of a pop-up PUc displayed on the payment screen SAd of the touch panel 23. Upon seeing the pop-up PUdc, the store clerk guides the customer to the payment device 4, where the warning light 47 is illuminated.

Figure 39 shows an example of the text TXc displayed on the subplanar surface SBb of the display 25. After viewing the text TXc, the buyer will follow the store clerk's instructions and proceed to the payment device 4, where the warning light 47 is illuminated, to make the payment.

After completing ACT174, processor 61 proceeds to ACT175. As ACT175, processor 61 sets the pending flag Fb to "0". With this, processor 61 terminates the third information processing.

Meanwhile, when processor 61 receives a confirmation event while in the waiting state of ACT 172 and ACT 173, it proceeds to ACT 176. As ACT 176, processor 61 displays a pop-up PUD (see Figure 40) on the touch panel 23 screen informing the store clerk of the payment destination.

Figure 40 shows an example of a pop-up PUd displayed on the registration screen SAa of the touch panel 23. Upon reviewing the pop-up PUd, the store clerk determines the payment recipient for the customer whose transaction information is being held on the holding server 1. Specifically, if another customer is paying at the transaction processing device 3, but no customer is paying at the payment device 4, the clerk determines payment device 4 as the payment recipient. However, if an abnormality occurs at payment device 4, such as a shortage of receipts or insufficient change, the clerk determines transaction processing device 3 as the payment recipient. Based on this determination, the clerk operates the display device 5.

As explained in Figure 16 for the processing of ACT212 and ACT214, the processor 11 of the holding server 1, which output a confirmation event to the transaction processing device 3, outputs the data for the instruction screen SDb to the display device 5. As a result, the instruction screen SDb is displayed on the display device 5.

In ACT 176, the processor 61, which controlled the display of the pop-up PUD (see Figure 40), proceeds to ACT 177. The processor 61 checks whether it received a release event in ACT 177. If it did not receive a release event, the processor 61 proceeds to ACT 178. The processor 61 checks whether it received a third execution event in ACT 178. If it did not receive a third execution event, the processor 61 returns to ACT 177. In this way, the processor 61 waits for either a release event or a third execution event in ACT 177 and ACT 178.

As explained using Figure 18, when the transaction processing device 3 receives a confirmation event, the hold server 1 sends either a release event or a third execution event. Specifically, if the import button BDa is pressed on the instruction screen SDb displayed on the display device 5, and the information related to the pending transaction is output to the settlement device 4, a release event is sent from the hold server 1 to the transaction processing device 3 as part of ACT 246. Conversely, if the return button BDb is pressed on the instruction screen SDb, and the transaction processing device 3 is specified as the output destination for the transaction information, a third execution event is returned as part of ACT 251.

If processor 61 receives a release event while in the waiting state for ACT 177 and ACT 178, it proceeds to ACT 174 as described above. Thereafter, processor 61 executes the processing of ACT 174 and ACT 175 in the same manner as described above. Specifically, processor 61 displays a pop-up PUc (see Figure 38) on the subplanning screen SAb or payment screen SAd of the touch panel 23 to guide the customer to payment at the payment device 4. Processor 61 also displays text TXc (see Figure 39) on the subplanning screen SBb of the display 25 to instruct the customer to pay at the payment device 4. Afterward, processor 61 sets the pending flag Fb to "0". With this, processor 61 terminates the third information processing.

On the other hand, if processor 61 receives a third execution event while in the waiting state of ACT 177 and ACT 178, it proceeds to ACT 179. As ACT 179, processor 61 checks the payment flag Fa. If the payment flag Fa is "1," meaning the previous customer is completing payment in the transaction processing unit 3, processor 61 proceeds to ACT 180. As ACT 180, processor 61 sends a negative response signal to the hold server 1. With this, processor 61 completes the third information processing.

In response to this, if the payment flag Fa is "0" in ACT 179, meaning there are no customers currently settling transactions in the transaction processing unit 3, the processor 61 proceeds to ACT 181. The processor 61 then sends an acceptance response signal to the holding server 1 as ACT 181.

As explained using Figure 18, the hold server 1, having received an acceptance response from the transaction processing device 3 that sent the third execution event, sends a hold file (ACTs 249 to 251). The processor 61, which sent the acceptance response signal, then waits for the hold file to be received as ACT 182. Upon receiving the hold file via the communication interface 65, the processor 61 proceeds to ACT 183. As ACT 183, the processor 61 expands the data from the hold file into the second transaction file 622 and stores it. Incidentally, the data in the hold file is the same as the data in the first transaction file 621 that was output to the hold server 1 in ACT 148 of Figure 13.

After storing the data from the pending file in the second transaction file 622, the processor 61 proceeds to ACT 184. As ACT 184, the processor 61 displays a pop-up PUb (see Figure 30) on the subplanning screen SAb or payment screen SAd of the touch panel 23, informing the user that payment is possible using the transaction processing device 3. The processor 61 also displays text TXb (see Figure 31) on the subplanning screen SBb of the display 25, indicating that payment is possible.

Thus, having notified the transaction processing device 3 that payment is possible using the touch panel 23 and display 25, the processor 61 proceeds to ACT 185. In ACT 185, the processor 61 sets the payment in progress flag Fa to "1" and the pending flag Fb to "0". Afterward, the processor 61 proceeds to ACT 152 in Figure 14. The processor 61 then executes the processes of ACT 152 through ACT 167 in the same manner as described above.

In this manner, when the transaction information held in the holding server 1 is returned to the transaction processing device 3, the processor 61 of the transaction processing device 3 executes the processes of ACT 152 to ACT 167 in Figure 14 in the same manner as described above. That is, the processor 61 sets the screen of the second touch panel 34 to the payment notification screen SCb. If no payment method has been selected in the input device 2, the processor 61 displays the payment method selection screen SCa before the payment notification screen SCb. When a payment method is selected by the customer, the processor 61 displays the payment notification screen SCb. After payment is started, the processor 61 sets the screen of the second touch panel 34 to the payment in progress screen SCc. The processor 61 also issues a transaction number. When the customer presses the payment button BCb on the payment in progress screen SCc, the processor 61 executes the settlement process and issues a receipt. The processor 61 also sets the screen of the second touch panel 34 to the payment completed screen SCd. Thus, the customer can settle the transaction by operating the transaction processing device 3 themselves and paying the amount due.

Here, the processor 61 functions as a guidance means 306 by cooperating with the touch panel 23 and the display 25 to execute the processes of ACT 174 and ACT 184. The processor 61 also functions as an execution means 307 by executing the processes of ACT 183 to ACT 185, and further, the processes of ACT 152 to ACT 167.

Figure 19 is a flowchart showing the essential steps of the fifth information processing performed by the processor 71 of the payment device 4 according to the third business program.

Processor 71 awaits the first execution event as ACT 301. As explained using Figure 16, when transaction information is held in the lane-specific folder 132 of the holding server 1 and transaction identification information is stored in the transaction identification information memory 626, the first execution event is sent from the holding server 1 to the settlement device 4 as ACT 210. Upon receiving the first execution event, processor 71 proceeds to ACT 302. Processor 71 checks the payment in progress flag Fc as ACT 302. If the payment in progress flag Fc is "1", meaning the previous customer is still performing the settlement at the settlement device 4, processor 71 proceeds to ACT 303. Processor 71 sends a negative response signal to the holding server 1 as ACT 303. With this, processor 71 completes the fifth information processing.

In response to this, if the payment flag Fc in ACT 302 is "0," meaning the customer has not yet made a payment at the payment device 4, the processor 71 proceeds to ACT 304. The processor 61 then sends an acceptance response signal to the hold server 1 as ACT 304.

Upon receiving the acceptance response signal, the processor 11 of the holding server 1 executes the processes shown in the flowchart of Figure 17, specifically ACTs 221 to 232. Thus, the reading screen SDa is displayed on the display device 5. The processor 71 then waits for the machine-readable code BC to be read by the reader 9 as ACT 305. Once the machine-readable code BC is read, the processor 71 proceeds to ACT 306. The processor 71 analyzes the data of the machine-readable code BC as ACT 306. Then, as ACT 307, the processor 71 confirms whether the machine-readable code BC of the transaction identification information was read. If a machine-readable code other than transaction identification information is read, the processor 71 returns to ACT 305. The processor 71 then waits for the machine-readable code BC to be read by the reader 9.

When the machine-readable code of the transaction identification information is read by the reader 9, the processor 71 proceeds to ACT 308. The processor 71 sends a request event to the holding server 1 as ACT 308. As mentioned above, the request event is an event requesting the acquisition of transaction-related information.

As explained using Figure 17, the hold server 1, upon receiving the request event, transmits the data of the hold file, i.e., the first transaction file 621. The processor 71, which sent the request event, then proceeds to ACT 309. As ACT 309, the processor 71 awaits the hold file. Upon receiving the hold file via the communication interface 75, the processor 71 proceeds to ACT 310. As ACT 310, the processor 71 expands and stores the data from the hold file in the third transaction file 721. Incidentally, the data in the hold file is the same data stored in the first transaction file 621 of the transaction processing device 3 installed in the same settlement lane L.

After storing the data from the pending file in the third transaction file 721, processor 71 proceeds to ACT 311. In ACT 311, processor 71 sets the payment flag Fc to "1". With this, processor 71 completes the fifth information processing step.

Thus, when the payment flag Fc of the payment device 4 is set to "0," meaning the customer is not yet making a payment at the payment device 4, and the machine-readable code of the transaction identification information is read by the reader 9 located in the same payment lane L, the processor 71 of the payment device 4 requests information related to the transaction identified by that transaction identification information from the hold server 1. Upon receiving the data from the hold server 1 in response to this request, the processor 71 stores the data from the hold file in the third transaction file 721. The processor 71 also sets the payment flag Fc to "1."

Here, the processor 71, in cooperation with the communication interface 75, executes the processing of ACTs 305 to 310, thereby realizing the function of the data acquisition means (first data acquisition means) 401.

Figure 20 is a flowchart showing the essential steps of the sixth information processing performed by the processor 71 of the payment device 4 according to the third business program. The processor 71 performs the sixth information processing in parallel with the fifth information processing described above.

Processor 71 awaits the second execution event as ACT 321. As explained using Figure 18, when transaction information is held in the lane-specific folder 132 of the holding server 1, and the capture button BDa on the instruction screen SDb displayed on the display device 5 is input, and the settlement device 4 is instructed as the output destination for transaction information, an execution event is sent from the holding server 1 to the settlement device 4 as processing ACT 243. Upon receiving the execution event, processor 71 proceeds to ACT 322. Processor 71 checks the payment in progress flag Fc as ACT 322. If the payment in progress flag Fc is "1", that is, if the previous customer is still performing the settlement at the settlement device 4, processor 71 proceeds to ACT 323. Processor 71 sends a negative response signal to the holding server 1 as ACT 323. With this, processor 71 completes the sixth information processing.

In response to this, if the payment flag Fc in ACT323 is "0," meaning the customer has not yet made a payment at the payment device 4, the processor 71 proceeds to ACT324. The processor 61 then sends an acceptance response signal to the hold server 1 as ACT324.

As explained using Figure 18, the hold server 1, having received an acceptance response from the settlement device 4 that sent the second execution event, sends the hold file to the settlement device 4. The processor 71, which sent the acceptance response signal, then waits for the hold file to be received as ACT 325. Upon receiving the hold file via the communication interface 75, the processor 71 proceeds to ACT 326. As ACT 326, the processor 71 expands and stores the data from the hold file in the third transaction file 721. Incidentally, the data in the hold file is the same data stored in the first transaction file 621 of the transaction processing device 3 installed in the same settlement lane L.

After storing the data from the pending file in the third transaction file 721, processor 71 proceeds to ACT 327. In ACT 327, processor 71 sets the payment flag Fc to "1". With this, processor 71 completes the sixth information processing step.

Thus, when the payment in progress flag Fc is "0," meaning the customer has not yet made a payment, the processor 71 of the payment device 4 receives a second execution event from the hold server 1. It then retrieves the data from the hold file output by the hold server 1 and stores it in the third transaction file 721. The processor 71 also sets the payment in progress flag Fc to "1."

Here, the processor 71, in cooperation with the communication interface 75, executes the processing of ACT 325 and ACT 326, thereby realizing the function of the data acquisition means (second data acquisition means) 401.

Figure 21 is a flowchart showing the essential steps of the seventh information processing performed by the processor 71 of the payment device 4 according to the third business program. The processor 71 performs the seventh information processing in parallel with the fifth and sixth information processing described above.

Processor 71 waits for the payment flag Fc to become "1" as ACT 331. When the payment flag Fc becomes "1" in the fifth information processing step ACT 311 or the sixth information processing step ACT 327, processor 71 proceeds to ACT 332. As ACT 332, processor 71 sets the touch panel 42 screen to the details confirmation screen SEa (see Figure 41). Processor 71 also illuminates the warning light 47.

Figure 41 shows an example of the details confirmation screen SEa displayed on the touch panel 42. The details confirmation screen SEa is divided into a details area AEa and a total area AEb. The details area AEa displays the product names, purchase quantities, unit prices, discount amounts, and sales amounts of purchased items in a single transaction in a list format, in sequential order. The total area AEb displays the total purchase quantities and total sales amounts of purchased items in a single transaction. The processor 71 displays the product names, purchase quantities, unit prices, discount amounts, and sales amounts of purchased items in a single transaction in the details area AEa based on the product sales data stored in the third transaction file 721. The processor 71 also displays the total purchase quantities and total sales amounts of purchased items in the total area AEb based on the product sales data stored in the third transaction file 721.

The item confirmation screen SEa includes a confirmation button BEa and a staff call button BEb. Both the confirmation button BEa and the staff call button BEb are software keys. The confirmation button BEa is an operator used to signal that the customer has confirmed that the details of the purchased items are displayed on the item confirmation screen SEa. The staff call button BEb is an operator used to signal that the customer is calling a staff member.

The processor 71, displaying the details confirmation screen SEa, proceeds to ACT 333. The processor 71 waits for the confirmation button BEa to be input as ACT 333. If the staff call button BEb is input during this waiting state, the processor 71 performs the staff call operation. For example, the processor 71 flashes the warning light 47. After the called staff member completes the call, the processor 71 returns to the waiting state for ACT 333.

When the confirmation button BEa is pressed while ACT333 is in standby mode, processor 71 proceeds to ACT334. Processor 71 checks whether the data stored in the third transaction file 721 contains a payment code as ACT334. If a payment code is present, processor 71 proceeds to ACT335. Processor 71 extracts the payment code from the third transaction file 721 as ACT335.

If no payment code is included, the processor 71 proceeds to ACT 336. As ACT 336, the processor 71 sets the touch panel 42 screen to the payment method selection screen SEb (see Figure 42).

Figure 42 shows an example of the payment method selection screen SEb displayed on the touch panel 42. The payment method selection screen SEb includes a group of selection buttons BEc for each payment method. The selection button group BEc includes buttons for cash, credit, electronic money, and code payment. However, there are no buttons for payment using gift certificates or other monetary instruments. The payment method selection screen SEb also includes a total area AEc that displays the total purchase quantity and total sales amount for a single transaction. The total area AEc displays the total purchase quantity and total sales amount calculated based on the product sales data of the purchased items stored in the third transaction file 721. The staff call button BB is also displayed on the payment method selection screen SEb, allowing the customer to call a staff member.

After viewing the payment method selection screen SEb, the customer touches the button corresponding to their desired payment method. For example, a customer wishing to pay with cash touches the cash button in the selection button group BEc. A customer wishing to pay with a credit card touches the credit button in the selection button group BEc. A customer wishing to pay with electronic money touches the electronic money button in the selection button group BEc. A customer wishing to pay with QR code payment touches the QR code payment button in the selection button group BEc.

The processor 71, with the touch panel 42 screen set to the payment method selection screen SEb, proceeds to ACT 337. As ACT 337, the processor 71 waits for a payment method to be selected. Once a payment method is selected via touch operation on the selection button group BEc, the processor 71 proceeds to ACT 338. As ACT 338, the processor 71 obtains the payment code for the selected payment method, similar to the processing in ACT 123 of the first information processing.

After completing the processing in ACT335 or ACT338, the processor 71 proceeds to ACT339. As ACT339, the processor 71 sets the touch panel 42 screen to the payment notification screen SEC (see Figure 43). The payment notification screen SEC is a screen based on the payment code obtained through the processing in ACT335 or ACT339.

Figure 43 shows an example of the payment notification screen SEC displayed on the touch panel 42. Figure 43 shows the payment notification screen SEC when a payment code for cash payment is obtained through processing by ACT 335 or ACT 338. The payment notification screen SEC includes a total area AEc, similar to the payment method selection screen SECb. The payment notification screen SEC also includes a change dispenser information area AEd. The change dispenser information area AEd displays the total amount, the total amount of cash inserted into the automatic change dispenser 78 (i.e., the inserted amount), and the remaining amount after subtracting the inserted amount from the total amount. The staff call button BEb is also displayed on the payment notification screen, allowing the customer to call a staff member.

After confirming the payment notification screen SEC, the customer pays using their chosen payment method. For example, a customer who chooses cash payment inserts cash into the automatic change dispenser 78. A customer who chooses credit card payment has their credit card data read by the reader of the cashless payment terminal 79. A customer who chooses electronic money payment has their electronic money data read by the reader of the cashless payment terminal 79. A customer who chooses QR code payment has their barcode or QR code for QR code payment read by the scanner of the cashless payment terminal 79.

The processor 71, having set the touch panel 42 screen to the payment notification screen SEC, proceeds to ACT 340. The processor 71 waits for the payment to begin as ACT 340. For example, if cash payment is selected, the processor 71 waits for cash to be inserted into the automatic change dispenser 78. For example, if credit card payment is selected, the processor 71 waits for the credit card data to be read by the cashless payment terminal 79. For example, if electronic money payment is selected, the processor 71 waits for the electronic money data to be read by the cashless payment terminal 79. For example, if code payment is selected, the processor 71 waits for the barcode or two-dimensional data code for code payment to be read by the cashless payment terminal 79.

When payment begins, processor 71 proceeds to ACT 341. As ACT 341, processor 71 issues a transaction number. The transaction number is a seven-digit number, for example, a three-digit payment device ID followed by a four-digit serial number. The serial number is incremented by "1" each time a transaction is settled at payment device 4. Having issued the transaction number, processor 71 proceeds to ACT 342. As ACT 342, processor 71 sets the touch panel 42 screen to the payment screen SEd (see Figure 44).

Figure 44 shows an example of the payment screen SEd displayed on the touch panel 42. Figure 44 shows the payment screen SEd when a cash payment code is obtained through processing by ACT 335 or ACT 338. The payment screen SEd is a screen with the payment notification screen SCb with the addition of a checkout button BEd. The information displayed in the change dispenser information area AEd on the payment screen SCc is updated according to the amount of cash inserted into the automatic change dispenser 78. The checkout button BEd is a software key. The checkout button BEd is an operator used to signal the completion of payment. A customer who has finished paying using the selected payment method touches the checkout button BEd. Note that the staff call button BEb remains displayed on the payment screen SEd, allowing the customer to call a staff member.

When the touch panel 42 screen is set to the payment screen SEd, the processor 71 proceeds to ACT 343. As ACT 343, the processor 71 waits for the payment button BEd to be input. When the payment button BEd is input by touch operation, the processor 71 proceeds to ACT 344. As ACT 344, the processor 71 executes the transaction settlement process based on the payment code. That is, if the payment code is a cash payment code, the processor 71 executes the transaction settlement process with the cash inserted into the automatic change dispenser 78. If the payment code is a credit card payment code, the processor 71 executes the transaction settlement process with the credit card data read by the cashless payment terminal 79. If the payment code is an electronic money payment code, the processor 71 executes the transaction settlement process with the electronic money data read by the cashless payment terminal 89. If the payment code is a code payment code, the processor 71 executes the transaction settlement process with the barcode or two-dimensional data code read by the cashless payment terminal 79. Since these payment processing procedures are all well-known, detailed explanations will be omitted.

Once the payment processing is complete, processor 71 proceeds to ACT 345. As ACT 345, processor 71 drives printer 87 to issue a receipt. Processor 71 also sets the touch panel 42 screen to the payment completion screen SEe (see Figure 45) as ACT 346. The receipt is identical to the receipt issued by transaction processing device 3 in ACT 163. However, the receipt issued by transaction processing device 3 includes a transaction number with the transaction processing device ID, while the receipt issued by payment device 4 includes a transaction number with the payment device ID.

Figure 45 shows an example of the payment completion screen SEe displayed on the touch panel 42. Figure 45 shows the payment completion screen SEe when a payment code for cash payment is obtained through processing by ACT 335 or ACT 338. The payment completion screen SEe includes a change dispenser information area AEd, similar to the payment notification screen SEc and the payment in progress screen SEd. The store clerk can determine that a customer who selected cash payment has completed payment based on the information displayed in the change dispenser information area AEd. Since customers who have completed payment do not call a store clerk, the store clerk call button BEb is not displayed on the payment completion screen SEe. After confirming the payment completion screen SEe, the customer takes a receipt and leaves the store.

The processor 71, displaying the payment completion screen SEe, proceeds to ACT 347. As ACT 347, the processor 71 saves the data stored in the third transaction file 721, that is, the data of the goods purchased by the customer who completed the payment. The data is saved to, for example, the auxiliary storage device 73. The data may also be saved to the main memory 72. Alternatively, the data from the third transaction file 721 may be sent to the POS server via the communication interface 75 and saved on the POS server. Alternatively, the data may be saved on the hold server 1 instead of the POS server.

The processor 71, having saved the data from the third transaction file 721, proceeds to ACT 348. As ACT 348, the processor 71 clears the third transaction file 721. Then, as ACT 349, the processor 71 sets the payment flag Fc to "0". Finally, the processor 71 turns off the warning light 47. With this, the processor 71 completes the seventh information processing step.

As described above, when the transaction information held in the holding server 1 is received by the settlement device 4, the processor 71 of the settlement device 4 executes the processes of ACT332 to ACT349 in Figure 21. Specifically, the processor 71 sets the touch panel 42 screen to the details confirmation screen SEa. When the confirmation button BEa is pressed by the customer, the processor 71 sets the touch panel 42 screen to the payment notification screen SEC. If no payment method has been selected in the input device 2, the processor 71 displays the payment method selection screen SEb before the payment notification screen SEC. When a payment method is selected by the customer, the processor 71 sets the touch panel 42 screen to the payment notification screen SEC. After payment has started, the processor 71 sets the touch panel 42 screen to the payment in progress screen SEd. The processor 71 also issues a transaction number. When the accounting button BEd on the payment in progress screen SEd is pressed by the customer, the processor 71 executes the settlement process and issues a receipt. Furthermore, the processor 71 sets the touch panel 42 screen to the payment completion screen SEe. Thus, the customer can complete the transaction by operating the payment device 4 themselves and paying the amount due.

Here, the processor 71, in cooperation with the touch panel 42, executes the processing of ACT 336, thereby realizing the function of a third payment acceptance means 403. The processor 71, in cooperation with the touch panel 42, executes the processing of ACT 339, thereby realizing the function of a second amount output means 402. The processor 71, in cooperation with the touch panel 42, executes the processing of ACT 344, thereby realizing the function of a second settlement means 404.

[How the product sales system works]
Next, the operation of the payment system 100, which operates as described above, will be explained.
First, let's assume that the customer has not yet made a payment at the transaction processing device 3 and the payment device 4. In this state, once the first customer has finished registering the items to be purchased and has pressed the payment button BAe on the subplanning screen SAb or the payment button BAh on the payment screen SAd, a pop-up PUb (see Figure 30) will appear on the subplanning screen SAb or payment screen SAd of the touch panel 23, informing the customer that payment is possible at the transaction processing device 3. In addition, text TXb (see Figure 31) indicating that payment is possible will be displayed on the subplanning screen SBb of the display 25. Then, the payment in progress flag Fa will become "1". Thus, the first customer will settle the transaction by operating the transaction processing device 3 themselves.

Next, let's consider the case where the second customer has finished registering the items they wish to purchase and has pressed either the payment button BAe or BAh. If the first customer, who is operating the transaction processing device 3, has not yet completed the payment, then the transaction information for the second customer, along with the transaction identification information, is sent to the holding server 1 and held. That is, the transaction information is stored in the lane-specific folder 132 of the payment lane L where the item registration has been completed. The holding flag Fb then becomes "1".

The holding server 1, which holds transaction information transmitted from the transaction processing device 3, sends a first execution event to the settlement device 4, which is installed in the same settlement lane L as the transaction processing device 3. At this time, if the payment flag Fc of the settlement device 4 is "0," meaning there are no customers operating the settlement device 4 to complete a settlement, the holding server 1 generates a machine-readable code BC indicating transaction identification information, which is displayed on the display device 5 in the same settlement lane L. When the machine-readable code BC is displayed on the display device 5, the reader 9 reads the machine-readable code BC.

The payment device 4 receives the machine-readable code BC read by the reader 9. When the machine-readable code BC of the transaction identification information is read by the reader 9, it sends a request event to the holding server 1. In response to this request event, the holding server 1 sends information regarding the second customer's transaction to the payment device 4. Also, the holding flag Fb becomes "0". Thus, the second customer settles the transaction by operating the payment device 4 themselves.

On the other hand, when the holding server 1 sends the first execution event to the payment device 4, if the payment flag Fc of the payment device 4 is "1," meaning there is a customer operating the payment device 4 to complete a payment, the instruction screen SDb (see Figure 37) is displayed on the display device 5.

The store clerk then determines the output destination for the transaction information held on the hold server 1. The clerk waits for the transaction processing device 3 or the settlement device 4 to become available and then inputs either the "Import" button BDa or the "Return" button BDb. That is, if the settlement device 4 becomes available first, the clerk inputs the "Import" button BDa. This input allows the transaction information of the second customer to be imported into the settlement device 4. A pop-up PUc (see Figure 38) is then displayed on the subplanning screen SAb or payment screen SAd of the touch panel 23, guiding the customer to make the payment at the settlement device 4. Additionally, text TXc (see Figure 39) instructing the customer to pay at the settlement device 4 is displayed on the subplanning screen SBb of the display 25. The "Holding" flag Fb also becomes "0". Thus, the second customer settles the transaction by operating the settlement device 4 themselves.

On the other hand, if the transaction processing unit 3 becomes available first, the store clerk presses the return button BDb. This input returns the transaction information for the second customer to the transaction processing unit 3. A pop-up PUb (see Figure 30) is then displayed on the subplanning screen SAb or payment screen SAd of the touch panel 23, informing the customer that payment is possible using the transaction processing unit 3. Additionally, text TXb (see Figure 31) indicating that payment is possible is displayed on the subplanning screen SBb of the display 25. Furthermore, the pending flag Fb becomes "0". Thus, the second customer completes the transaction by operating the transaction processing unit 3 themselves.

Incidentally, when the transaction information for the second customer is held on the holding server 1, i.e., the holding flag Fb is "1", and the third customer has finished registering the items they wish to purchase and has pressed the payment button BAe or BAh, a pop-up PUa (see Figure 28) will appear on the subplanning screen SAb or payment screen SAd of the touch panel 23, informing the customer that payment is not possible. Also, text TXa (see Figure 29) will appear on the subplanning screen SBb of the display 25, instructing the customer to wait because payment is not possible. Therefore, the third customer will wait. Then, when the transaction processing device 3 or settlement device 4 becomes available, the store clerk will press the take button BDa or the return button BDb. Thus, the third customer will operate the transaction processing device 3 or settlement device 4 themselves to settle the transaction.

As detailed above, this embodiment provides a payment system 100 that allows customers to efficiently perform payment operations by appropriately selecting the transaction processing device 3 and the payment device 4. Therefore, it is possible to reduce labor costs. Furthermore, it can also provide excellent benefits in terms of infectious disease control.

In this embodiment, when transaction information is held in the holding server 1, a machine-readable code BC indicating transaction identification information is displayed on the display device 5. The machine-readable code BC displayed on the display device 5 is then automatically read by the reader 9. Once the reader 9 reads the machine-readable code BC, the settlement device 4 analyzes it. The settlement device 4 then retrieves the transaction information identified by the transaction identification information indicated by the machine-readable code BC from the holding server 1. Having retrieved the transaction information, the settlement device 4 becomes capable of settling the transaction. Thus, the customer can operate the settlement device 4 to make the payment.

However, if a transaction is in the process of being settled in the settlement device 4, the settlement device 4 will not take in the machine-readable code being read by the reader 9. In this case, the instruction screen SDb will be displayed on the display device 5. The store clerk can easily select, with a single touch on the instruction screen SDb, whether to output the transaction information held in the holding server 1 to the settlement device 4 or the transaction processing device 3.

Furthermore, the reader 9 does not necessarily need to be connected to the settlement device 4 by a transmission cable. For example, the reader 9 may be connected to the communication network 6, and the holding server 1 may analyze the machine-readable code read by the reader 9 to recognize the transaction identification information. The holding server 1 may then transmit information related to the transaction identified by that transaction identification information to the settlement device 4.

Transaction information is not limited to information about purchased goods, such as product sales data. Transaction information should be information that, when processed, allows for the calculation of the amount required for settlement. For example, transaction information may consist only of the product code and sales quantity of the purchased goods.

In the holding server 1, the storage area for holding transaction-related information is not limited to the lane-specific folders 132. A single data folder that holds the holding files chronologically may also be used, as long as it is possible to identify which settlement lane L the holding file originated from.

[Second Embodiment]
The first embodiment described above does not mention the process of returning transaction information received by the payment device 4 to the holding server 1. However, if transaction information is received by the payment device 4, but an abnormality occurs in the payment device 4, such as running out of receipts or insufficient change, the customer will not be able to operate the payment device 4 to settle the transaction. Furthermore, for payment methods that require confirmation by a store employee, such as gift certificates, self-payment is prohibited. Therefore, a second embodiment, which includes a process to return transaction information received by the payment device 4 to the holding server 1, will be described using Figures 46 to 47, taking such events into consideration. Note that in the second embodiment as well, the configuration of the payment system 100 is the same as in the first embodiment, so its explanation will be omitted here.

For example, if a customer attempts to initiate a payment using payment device 4 but an error occurs in payment device 4, the customer will press the staff call button BEb on the details confirmation screen SEa to summon a staff member. Similarly, if the desired payment method is not available on the payment method selection screen SEb, the customer will also press the staff call button BEb on the payment method selection screen SEb to summon a staff member. Therefore, in the second embodiment, when the staff call button BEb is pressed, the processor 71 of payment device 4 begins the information processing procedure shown in the flowchart of Figure 46.

Figure 46 is a flowchart showing the essential steps of the eighth information processing that the processor 71 executes according to the third business program. The processor 71 executes the eighth information processing in parallel with the fifth through seventh information processing described above.

Processor 71 waits for the input of the staff call button BEb as ACT 341. When the staff call button BEb is input on the details confirmation screen SEa or the payment method selection screen SEb, processor 71 proceeds to ACT 342. Processor 71 sends a call event to the hold server 1 as ACT 342. The call event is an event to notify the hold server 1 that the staff call button BEb has been input. The call event includes the payment device ID of payment device 4.

As will be explained in detail later, the pending server 1, upon receiving the call event, returns either a continuation event or a payment cancellation event. The processor 71 that sent the call event then proceeds to ACT 343. The processor 71 checks whether it received a continuation event as ACT 343. If it did not receive a continuation event, the processor 71 proceeds to ACT 344. The processor 71 checks whether it received a payment cancellation event as ACT 344. If it did not receive a payment cancellation event, the processor 71 returns to ACT 333. In this manner, the processor 71 waits for either a continuation event or a payment cancellation event to be received in ACT 343 and ACT 344. During this waiting state, an image such as "Calling" is displayed on the touch panel 42.

When ACT343 and ACT344 are in standby mode and a continuation event is received, the processor 71 terminates the eighth information processing step.

In response to this, if a settlement cancellation event is received while ACT343 and ACT344 are in the waiting state, processor 71 proceeds to ACT345. Processor 71 clears the third transaction file 721 as ACT345. Processor 71 also rewrites the payment in progress flag Fc to "0" as ACT346. With this, processor 71 terminates the eighth information processing step.

Thus, when the processor 71 of the payment device 4 receives a continuation event in response to a call event, it terminates the eighth information processing step. In this case, the processor 71 continues the seventh information processing step from the processing step immediately preceding the input of the staff call button BEb.

If a payment cancellation event is received in response to a call event, processor 71 clears the third transaction file 721. It also sets the payment in progress flag Fc to "0". Therefore, processor 61 terminates the seventh information processing step when the clerk call button BEb is pressed and begins processing from the fifth information processing step.

Figure 47 is a flowchart showing the ninth essential procedure executed by the processor 11 of the hold server 1 according to the second business program. The processor 11 executes the ninth information processing in parallel with the fourth information processing described above.

Processor 71 is waiting for a call event as ACT271. Upon receiving a call event from payment device 4, processor 11 proceeds to ACT272. Processor 11 obtains the payment device ID from the call event as ACT272. Processor 11 obtains the lane number of the payment lane L where the data-sending payment device 4 is located as ACT273. Specifically, processor 11 refers to the lane table 131 and obtains the lane number described in column Ca on the same row as the payment device ID.

The processor 11, having obtained the lane number, proceeds to ACT 274. As ACT 274, the processor 11 refers to the lane table 131 and obtains the display device ID described in column Cd on the same row as the payment device ID. Then, as ACT 275, the processor 11 outputs the confirmation screen data to the display device 5 identified by that display device ID.

Upon receiving the data from the confirmation screen, the display device 5 displays the confirmation screen SDc (see Figure 48) on the tablet's LCD screen.
Figure 48 shows an example of the display of the confirmation screen SDc. The confirmation screen SDc displays a re-hold button BDc and a continue button BDd. The re-hold button BDc and the continue button BDd are soft keys. The re-hold button BDc functions as a third operator that declares acceptance of returning the transaction information output to the settlement device 4 to the hold server 1. The continue button BDd functions as a fourth operator that declares continuing the settlement at the settlement device 4 without returning the transaction information output to the settlement device 4 to the hold server 1.

Upon checking the confirmation screen SDc, the store clerk recognizes that they have received a call from a customer who was operating the payment device 4 themselves. The clerk goes to the location of the payment device 4 to confirm the reason for the call. For example, if the receipt paper is out of stock or there is insufficient change, and the receipt paper or change can be replenished immediately, the clerk presses the continue button BDd. The clerk then replenishes the receipt paper or change in the payment device 4. However, if the receipt paper or change cannot be replenished immediately, or if the customer requests a payment method that requires clerk verification, such as a gift certificate, the clerk presses the re-hold button BDc.

When the re-hold button BDc is pressed, the display device 5 outputs a third signal to the hold server 1. The third signal is output in response to the input of the re-hold button BDc. When the continue button BDd is pressed, the display device 5 outputs a fourth signal to the hold server 1. The fourth signal is output in response to the input of the continue button BDd.

After outputting the data for the confirmation screen SDc, processor 11 proceeds to ACT 276. As ACT 276, processor 11 checks whether the re-hold button BDc has been pressed. If the re-hold button BDc has not been pressed, processor 11 proceeds to ACT 277. As ACT 277, processor 11 checks whether the continue button BDd has been pressed. If the continue button BDd has not been pressed, processor 11 returns to ACT 276. In this way, processor 11 waits in ACT 276 and ACT 277 for either the re-hold button BDc or the continue button BDd to be pressed on the confirmation screen SDc.

In the standby state of ACT276 and ACT277, upon receiving the fourth signal from the display device 5, the processor 11 recognizes that the continue button BDd has been pressed. The processor 11 then proceeds to ACT278. As ACT278, the processor 11 sends a continue event to the settlement device 4, the source of the call event. The continue event is an event instructing the settlement device 4 to continue the transaction. Having sent the continue event, the processor 11 proceeds to ACT279. As ACT279, the processor 11 clears the confirmation screen SDc that was displayed on the display device 5. With this, the processor 11 completes the ninth information processing step.

In the standby state of ACT276 and ACT277, upon receiving the third signal from the display device 5, the processor 11 recognizes that the re-hold button BDc has been pressed. The processor 11 then proceeds to ACT280. As ACT280, the processor 11 retrieves the data of the third transaction file 721 from the settlement device 4. The data in the third transaction file 721 is the data of the hold file output by the hold server 1 to the settlement device 4. That is, it is the data saved in the lane-specific folder 132 in ACT206 of the fourth information processing described using Figure 16, i.e., the data of the first transaction file 621 received from the transaction processing device 3.

Processor 11 again holds the data of the third transaction file 721, which was taken in from the settlement device 4 as ACT 281. Specifically, processor 11 stores the data of the third transaction file 721 in the lane-specific folder 132 corresponding to the lane number obtained in the processing of ACT 273.

The processor 11, having held the data from the third transaction file 721, proceeds to ACT 282. As ACT 282, the processor 11 sends a settlement cancellation event to the settlement device 4, the source of the call event. The settlement cancellation event is an event that instructs the settlement device 4 to cancel the settlement.

The processor 11, which sent the payment cancellation event, proceeds to ACT 283. As ACT 283, the processor 11 outputs instruction screen data to the display device 5. That is, the processor 11 outputs instruction screen data to the display device 5 identified by the display device ID obtained in the processing of ACT 274. As a result, the display device 5, upon receiving the instruction screen data, displays instruction screen SDb (see Figure 37) on the tablet's LCD screen.

Subsequently, the processor 11 executes the processing of ACTs 241 to 256 of the fourth information processing, as described using Figure 18, in the same manner as previously described.

In this second embodiment, when a customer operating the payment device 4 presses the staff call button BEb, a confirmation screen SDc is displayed on the display device 5. If the staff member then presses the continue button BDd, the data stored in the third transaction file 721 of the payment device 4 remains unchanged. The customer can then continue operating the payment device 4 and settle the transaction themselves.

In response, if the store clerk presses the re-hold button BDc, the data stored in the third transaction file 721 is held again on the hold server 1. The display device 5 then displays the instruction screen SDb. If the store clerk then presses the return button BDb, the re-held data is sent to the transaction processing device 3. Thus, the customer can settle the transaction by operating the transaction processing device 3. At this point, if the customer is paying with, for example, a gift certificate, they should ask the store clerk in space SP for confirmation.

As detailed above, according to the second embodiment, the transaction information received by the payment device 4 can be returned to the hold server 1 and held again by an employee's operation on the display device 5. The information related to the again-held transaction can then be output to the transaction processing device 3 or the payment device 4, again by an employee's operation on the display device 5. Therefore, for example, if a malfunction occurs in the payment device 4 and a customer attempting to operate the payment device 4 is unable to settle the transaction, the output destination of the customer's transaction information can be changed to the transaction processing device 3 with a simple operation on the display device 5.

[Third Embodiment]
Next, a third embodiment will be described with reference to Figures 49 to 51.
In the first embodiment, the payment device 4 takes in the machine-readable code BC read by the reader 9 when the payment in progress flag Fc is "0", that is, when the customer has not made a payment. In the third embodiment, the payment device 4 takes in the machine-readable code BC read by the reader 9 regardless of the payment in progress flag Fc.

Figures 49 and 50 are flowcharts showing the essential steps of the tenth information processing performed by the processor 11 of the hold server 1 according to the second business program in the third embodiment. The tenth information processing is a modification of the fourth information processing described using Figures 16 to 18 in the first embodiment. Therefore, the same reference numerals are used for processing steps common to Figures 16 to 18.

In Figure 49, the processor 11 is waiting for a pending event as ACT 201. Upon receiving a pending event via the communication interface 15, the processor 11 executes the processing of ACTs 202 to 208, as described using Figure 16. That is, the processor 11 sends an acceptance response. Specifically, the processor 11 sends an acceptance response to the transaction processing unit 3, the source of the pending event, and accordingly saves the data of the first transaction file 621 output from the transaction processing unit 3 to the lane-specific folder 132. The processor 11 also stores the transaction identification information received along with the data of the first transaction file 621 in the transaction identification information memory 626.

Subsequently, the processor 11 proceeds to ACT 221 in Figure 50. The processor 11 similarly executes the processes described in ACTs 221 to 223 using Figure 17. That is, the processor 11 generates a machine-readable code representing the transaction identification information stored in the transaction identification information memory 626. The processor 11 also refers to the lane table 131 and obtains the display device ID described in column Cd of the same row as the transaction processing device ID. Then, the processor 11 outputs the data for the display screen to the display device 5 identified by that display device ID.

By outputting the data from the reading screen to the display device 5, the reading screen SDa (see Figure 36) is displayed on the display device 5. When the reading screen SDa is displayed, the reading device 9 reads the machine-readable code BC displayed on the reading screen SDa. Once the machine-readable code is read by the reading device 9, the processor 71 of the payment device 4 begins the information processing procedure shown in the flowchart of Figure 51.

Figure 51 is a flowchart showing the essential steps of the 11th information processing step executed by the processor 71 of the payment device 4 according to the third business program in the third embodiment. Specifically, in the third embodiment, the processor 71 waits for the machine-readable code BC to be read as ACT 351. Once the machine-readable code BC is read, the processor 71 proceeds to ACT 352. As ACT 352, the processor 71 analyzes the data of the machine-readable code BC. Then, as ACT 353, the processor 71 checks whether the machine-readable code BC of the transaction identification information was read. If a machine-readable code other than transaction identification information is read, the processor 71 terminates the 11th information processing step.

When the machine-readable code of the transaction identification information is read by the reader 9, the processor 71 proceeds to ACT 354. As ACT 354, the processor 71 checks the payment flag Fc. If the payment flag Fc is "0," meaning the customer has not yet made a payment at the payment device 4, the processor 71 proceeds to ACT 352. As ACT 352, the processor 61 sends a request event to the holding server 1. The request event is an event requesting the retrieval of transaction-related information.

The processor 71 that sent the request event proceeds to ACT 356. As ACT 356, the processor 71 waits for the pending file. Upon receiving the pending file via the communication interface 75, the processor 71 proceeds to ACT 357. As ACT 357, the processor 71 expands and stores the data from the pending file in the third transaction file 721. Incidentally, the data from the pending file is the same data that was stored in the first transaction file 621 of the transaction processing unit 3 installed in the same settlement lane L.

After storing the data from the pending file in the third transaction file 721, processor 71 proceeds to ACT 358. In ACT 358, processor 71 sets the payment flag Fc to "1". With this, processor 71 completes the 11th information processing step.

In response to this, if the payment flag Fc in ACT 354 is "1," meaning the customer is making a payment at the payment device 4, the processor 71 proceeds to ACT 359. The processor 71 sends a failure event to the hold server 1 as ACT 359. The failure event notifies that it is not possible to retrieve transaction-related information. With this, the processor 71 terminates the 11th information processing step.

Thus, when the machine-readable code BC of the transaction identification information is read by the reader 9, the settlement device 4 determines whether or not it is currently processing the settlement of the transaction. If settlement is not currently in progress, it sends a request command to the holding server 1. Conversely, if settlement is currently in progress, it sends a rejection command to the holding server 1.

Returning to the explanation of Figure 50.
In ACT223, the processor 11 of the holding server 1, which output the data on the read screen, proceeds to ACT290. The processor 11 checks whether it has received a request event as ACT290. If it has not received a request event, the processor 11 proceeds to ACT291. The processor 11 checks whether it has received a rejection event as ACT291. If it has not received a rejection event, the processor 11 returns to ACT290. In this way, the processor 11 waits to receive either a request event or a rejection event.

When a request event is received in the waiting state of ACT290 and ACT291, the processor 11 proceeds to ACT225. The processor 11 executes the processing of ACT225 through ACT231 in the same manner as described above. Specifically, the processor 11 clears the read screen SDa displayed on the display device 5. The processor 11 also obtains transaction identification information from the request event. Furthermore, the processor 11 obtains the settlement device ID of the settlement device 4 that sent the request event, and obtains the lane number of the settlement lane L where the settlement device 4 identified by that settlement device ID is installed. The processor 11 selects the data of the first transaction file 621 stored in the lane-specific folder 132 for the obtained lane number, and transmits the data of the first transaction file 621 to the settlement device 4 identified by the settlement device ID. The processor 11 also sends a release event to the transaction processing device 3, which is the data source of the first transaction file 621. Afterward, the processor 11 clears the pending files and terminates the tenth information processing step.

On the other hand, when an invalid event is received while in the waiting state of ACT290 and ACT291, the processor 11 proceeds to ACT212. The processor 11 executes the processing of ACT212 to ACT214 in the same manner as described above. That is, the processor 11 sends a confirmation event to the transaction processing device 3, which is the data source of the first transaction file 621. The processor 11 also refers to the lane table 131 and obtains the display device ID described in column Cd on the same row as the transaction processing device ID. Then, the processor 11 outputs the instruction screen data to the display device 5 identified by that display device ID. Thus, when the display device 5 receives the instruction screen data, the instruction screen SDb (see Figure 37) is displayed on the tablet's LCD screen. From this point onward, the processor 11 executes the processing of ACT241 to ACT256 of the fourth information processing, as described using Figure 18, in the same manner as described above.

In this third embodiment, which operates in this manner, a payment system 100 can be provided that allows customers to efficiently perform payment operations by appropriately selecting the transaction processing device 3 and the payment device 4.

[Fourth Embodiment]
Figure 52 is a block diagram showing the schematic configuration of a payment system 200 according to the fourth embodiment. In the first embodiment, a payment system 100 was exemplified in which each payment lane L is equipped with an input device 2, a transaction processing device 3, a payment device 4, a display device 5, and a reader device 9. In the fourth embodiment, an input device 2 and a transaction processing device 3 are provided for one payment lane L, while the payment device 4, display device 5, and reader device 9 are shared by two adjacent payment lanes L. For example, the payment device 4 is installed near two payment lanes L. Also, the display device 5 is placed near each space SP of the two payment lanes L. The reader device 9 is then placed in a location where it can read the machine-readable code displayed on the reader device 9. In this way, a customer in one payment lane L can settle a transaction by operating the transaction processing device 3 of that payment lane L or the shared payment device 4 themselves. Similarly, a customer in the other payment lane L can settle a transaction by operating the transaction processing device 3 of that payment lane L or the shared payment device 4 themselves.

[Fifth Embodiment]
In the first embodiment, the transaction processing device 3 outputs transaction information to the holding server 1 when settlement of the transaction is impossible, and the holding server 1 holds the information. In the fifth embodiment, the transaction processing device 3 outputs transaction information to the holding server 1 regardless of whether settlement of the transaction is possible or impossible, and the holding server 1 holds the information. At this time, the reading screen SDa is displayed on the display device 5. If the settlement of the transaction has not been performed at the settlement device 4 and a request event is output from the settlement device 4, the holding server 1 sends the information relating to the held transaction to the settlement device 4. That is, the customer operates the settlement device 4 to make the payment. On the other hand, if the settlement of the transaction has been performed at the settlement device 4 and the instruction screen SDb is displayed on the display device 5, the information relating to the held transaction is sent to the settlement device 4, i.e., the settlement device 4 or transaction processing device 3, as instructed by the store clerk. That is, the customer operates the transaction processing device 3 or settlement device 4 to make the payment. Even with such a configuration, the effect of reducing labor costs by having the buyer perform the operations related to payment can be achieved.

In addition, several embodiments of the present invention have been described, but these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be carried out in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their variations are included within the scope of the invention, as well as within the scope of the invention and its equivalents as described in the claims.
The invention described in the original claims of this application is listed below.
[1] A settlement system comprising a transaction processing device, a settlement device, and a display device, wherein the transaction processing device comprises a first settlement means for settling a transaction based on transaction information acquired via an input device, and a transaction information output means for outputting transaction information to a holding device when settlement of the transaction is impossible, the display device comprises a display means for displaying transaction identification information that identifies a transaction for which transaction information has been output to the holding device in a manner readable by a reader, and the settlement device comprises an acquisition means for acquiring transaction information identified by the transaction identification information read by the reader from the holding device, and a second settlement means for settling a transaction based on the transaction information acquired by the acquisition means.
[2] The settlement system as described in Appendix [1], wherein the transaction information output means of the transaction processing device generates the transaction identification information when it receives an instruction to terminate the input of information relating to the transaction via the input device in a state where settlement of the transaction is impossible, and outputs the information relating to the transaction together with the transaction identification information to the holding device.
[3] The payment system as described in Appendix [1], wherein the display means of the display device displays the transaction identification information in a readable manner by the reader when the payment device is able to settle the transaction.
[4] The display device further comprises a second display means for displaying an instruction screen that receives an instruction for the destination of the information relating to the transaction that has been held in the holding device when the settlement device is unable to settle the transaction, and the settlement system described in Appendix [3].
[5] The settlement system as described in Appendix [4], wherein the second display means of the display device displays an instruction screen having a first operator for accepting that the output destination of the information relating to the transaction be the settlement device, and a second operator for accepting that the output destination of the information relating to the transaction be the transaction processing device.
[6] The settlement system according to Appendix [4], further displaying a third display means which displays a confirmation screen that receives an instruction to return the transaction information output to the settlement device back to the holding device.
[7] The settlement device, when the transaction identification information is read by the reader when settlement of the transaction is not possible, performs a process to display the instruction screen on the display device, as described in Appendix [4].
[8] A settlement system comprising a transaction processing device, a settlement device, and a display device, wherein the transaction processing device comprises a transaction information output means for outputting transaction information acquired via an input device to a holding device, and a first settlement means for settling a transaction based on the transaction information held in the holding device, the display device comprises a display means for displaying transaction identification information that identifies a transaction for which transaction information has been output to the holding device in a manner readable by a reader, and the settlement device comprises an acquisition means for acquiring transaction information identified by the transaction identification information read by the reader from the holding device, and a second settlement means for settling a transaction based on the transaction information acquired by the acquisition means.

1...Holding server, 2...Input device, 3...Transaction processing device, 4...Settlement device, 5...Display device, 6...Communication network, 9...Reading device, 100, 200...Settlement system, 101...Recognition means, 102...Transaction information input means, 103...Holding means, 104...Holding information output means, 131...Lane table, 132...Lane-specific folder, 201...Input means, 202...Termination acceptance means, 203...First payment acceptance means, 301...Input information acquisition means, 302...First amount output means, 303...Second payment acceptance means 304...First settlement means, 305...Transaction information output means, 306...Guidance means, 307...Execution means, 401...Input means, 402...Second amount output means, 403...Third payment acceptance means, 404...Second settlement means, 501...Acceptance means, 502...Instruction means, 503...Display means, 621...First transaction file, 622...Second transaction file, 623...Status memory, 624, 625, 722...Flag memory, 626...Transaction identification information memory, 721...Third transaction file, 901...Reading means.

Claims (8)

It includes a transaction processing device, a settlement device, a display device , a holding device, and a reading device .
The aforementioned transaction processing device is
A first settlement means that settles a transaction based on transaction information obtained via an input device,
Transaction information output means that, when settlement of the transaction is impossible, outputs information relating to the transaction, along with transaction identification information that identifies the transaction, to the holding device;
It is equipped with,
The aforementioned holding device,
A holding means for holding the transaction information output by the transaction information output means along with the transaction information,
A display control means that causes the transaction identification information output by the transaction information output means along with the transaction information to be displayed on the display device in a form that can be read by the reader,
It is equipped with,
The aforementioned display device is
Display means for displaying transaction identification information that identifies a transaction for which information relating to the transaction has been output to the holding device, in a manner readable by the reading device.
It is equipped with,
The aforementioned reading device,
A reading means for reading the transaction identification information displayed on the display device,
An output means for outputting the transaction identification information read by the reading means to the settlement device,
It is equipped with,
The aforementioned payment device is
An acquisition means for acquiring information relating to a transaction identified by the transaction identification information read by the reading device from the holding device,
A second settlement means that settles a transaction based on the transaction information acquired by the acquisition means,
A payment system equipped with the following features. The transaction information output means of the transaction processing device is:
The settlement system according to claim 1, wherein when an instruction to stop inputting information relating to the transaction is received via the input device while the settlement of the transaction is impossible, the system generates the transaction identification information and outputs the information relating to the transaction together with the transaction identification information to the holding device. The display means of the aforementioned display device is
When the settlement device is capable of settling a transaction, it displays the transaction identification information in a way that can be read by the reader.
The payment system according to claim 1. The aforementioned display device is
When the settlement device is unable to settle the transaction, a second display means displays an instruction screen that accepts an instruction for the output destination of the information relating to the transaction that has been held in the holding device.
The settlement system according to claim 3 further comprises the following: The second display means of the aforementioned display device is
The settlement system according to claim 4, which displays an instruction screen having a first operator for accepting that the output destination of the information relating to the transaction be the settlement device, and a second operator for accepting that the output destination of the information relating to the transaction be the transaction processing device. The aforementioned display device is
A third display means that displays a confirmation screen that accepts an instruction to return the transaction information output to the settlement device back to the holding device.
The payment system according to claim 4, further displaying The aforementioned payment device is
The settlement system according to claim 4, wherein when the transaction identification information is read by the reader when settlement of the transaction is impossible, the system performs a process to display the instruction screen on the display device. It includes a transaction processing device, a settlement device, a display device , a holding device, and a reading device .
The aforementioned transaction processing device is
A transaction information output means that outputs information relating to a transaction obtained via an input device , along with transaction identification information that identifies the transaction, to the holding device.
A first settlement means that settles a transaction based on the transaction information output from the holding device,
It is equipped with,
The aforementioned holding device,
A holding means for holding the transaction information output by the transaction information output means along with the transaction information,
A display control means that causes the transaction identification information output by the transaction information output means along with the transaction information to be displayed on the display device in a form that can be read by the reader,
A first output means that outputs information relating to the transaction that has been held by the holding means to the transaction processing device or the settlement device,
It is equipped with,
The aforementioned display device is
Display means for displaying transaction identification information that identifies a transaction for which information relating to the transaction has been output to the holding device, in a manner readable by the reading device.
It is equipped with,
The aforementioned reading device,
A reading means for reading the transaction identification information displayed on the display device,
An output means for outputting the transaction identification information read by the reading means to the settlement device,
It is equipped with,
The aforementioned payment device is
An acquisition means for acquiring information relating to a transaction identified by the transaction identification information read by the reading device from the holding device,
A second settlement means that settles a transaction based on the transaction information acquired by the acquisition means,
A payment system equipped with the following features.