Settlement system

Abstract

To reduce the labor cost by making a purchaser perform an operation for payment.SOLUTION: A settlement system includes a transaction processing device, a settlement device, and a display device. The transaction processing device outputs information related to a transaction to a deferring unit in a case where the settlement of the transaction is impossible. The display device displays transaction identification information for identifying the transaction of which information was output to the deferring device, so that a reading device can read the information. The settlement device draws the information related to the transaction identified by the transaction identification information read by the reading device from the deferring device, and settles the transaction on the basis of the information related to the transaction.SELECTED DRAWING: Figure 9

Description

[Technical field]

[0001] FIELD OF THE DISCLOSURE The present invention relates to a payment system. [Background technology]

[0002] There is a two-person system as a payment system for large retail stores such as supermarkets and home improvement centers. The two-person payment system includes an input device operated by a store clerk called a checker, and a transaction processing device operated by a store clerk called a cashier. The input device is a device for inputting information related to purchased items such as barcodes attached to the items. The transaction processing device is a device for processing product sales data of purchased items based on information input via the input device and settling transactions with customers. In the two-person payment system, since the input device and the transaction processing device are separate, input of information related to purchased items of a second customer can start on the input device while the transaction processing device is processing the payment of the first customer. Therefore, customers can be processed efficiently.

[0003] On the other hand, in recent years, from the viewpoint of reducing labor costs and taking measures against infectious diseases, there is a demand to have customers themselves perform operations related to deposits required for settlement of transactions. Even in a two-person settlement system, customers themselves perform operations related to deposits into the transaction processing device 3. This makes it unnecessary to have a store clerk in charge of cashiering, so labor costs can be reduced. In addition, since store clerks do not touch cash, cash cards, etc., this can also be an infectious disease prevention measure. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2018-152133 A Summary of the Invention [Problem to be solved by the invention]

[0005] The problem that an embodiment of the present invention aims to solve is to provide a payment system that reduces labor costs by having customers perform operations related to payment, and that can also be highly effective in terms of infection control. [Means for solving the problem]

[0006] In one embodiment, the payment system includes a transaction processor, a payment device, and a display device. The transaction processing device includes a first settlement means and a transaction information output means. The first settlement means settles a transaction with a customer as an operator based on transaction-related information acquired via an input device. The transaction information output means outputs transaction-related information to a reservation device when settlement of the transaction is impossible. The display device includes a display means for displaying transaction identification information for identifying a transaction whose information relating to the transaction has been output to the reservation device in a manner readable by the reading device. The settlement device includes an import means and a second settlement means. The import means imports information related to a transaction identified by the transaction identification information read by the reading device from the holding device. The second settlement means settles the transaction based on the information related to the transaction imported by the import means, with the customer acting as an operator. [Brief description of the drawings]

[0007] [Figure 1] FIG. 1 is a block diagram showing a schematic configuration of a payment system according to an embodiment. [Diagram 2] FIG. 2 is a schematic diagram showing the positional relationship between an input device, a transaction processing device, a settlement device, a display device, and a reading device provided in one settlement lane. [Diagram 3] FIG. 3 is a block diagram showing the main circuit configuration of the device main body in the transaction processing device. [Figure 4] FIG. 4 is a schematic diagram showing major storage areas formed in the main memory of the transaction processing device. [Diagram 5] FIG. 5 is a block diagram showing a main circuit configuration of the settlement device. [Figure 6]FIG. 6 is a schematic diagram showing main storage areas formed in the main memory of the payment device. [Figure 7] FIG. 7 is a block diagram showing the main circuit configuration of the reservation server. [Figure 8] FIG. 8 is a schematic diagram showing the data structure of a lane table held by the reservation server. [Figure 9] FIG. 9 is a schematic diagram showing the main functional configurations of the reservation server, the input device, the transaction processing device, the settlement device, the display device, and the reading device. [Figure 10] FIG. 10 is a flowchart showing a main procedure of a first information processing operation executed by a processor of the transaction processing device in accordance with a first business program. [Figure 11] FIG. 11 is a flowchart showing a main procedure of a first information processing operation executed by a processor of the transaction processing device in accordance with a first business program. [Figure 12] FIG. 12 is a flowchart showing the main steps of a first information processing operation executed by a processor of the transaction processing device in accordance with a first business program. [Figure 13] FIG. 13 is a flowchart showing a main procedure of a first information processing operation executed by a processor of the transaction processing device in accordance with a first business program. [Figure 14] FIG. 14 is a flowchart showing the main steps of the second information processing executed by the processor of the transaction processing device in accordance with the first business program. [Figure 15] FIG. 15 is a flowchart showing a main procedure of the third information processing executed by the processor of the transaction processing device in accordance with the first business program. [Figure 16] FIG. 16 is a flowchart showing the main steps of a fourth information processing routine executed by the processor of the reservation server in accordance with the second business program. [Figure 17] FIG. 17 is a flowchart showing the main steps of a fourth information processing routine executed by the processor of the reservation server in accordance with the second business program. [Figure 18] FIG. 18 is a flowchart showing the main steps of a fourth information processing routine executed by the processor of the reservation server in accordance with the second business program. [Figure 19] FIG. 19 is a flowchart showing main steps of a fifth information processing operation executed by the processor of the settlement device in accordance with the third business program. [Figure 20] FIG. 20 is a flowchart showing main steps of a sixth information processing operation executed by the processor of the settlement device in accordance with the third business program. [Figure 21] FIG. 21 is a flowchart showing main steps of a seventh information processing procedure executed by the processor of the settlement device in accordance with the third business program. [Figure 22] FIG. 22 is an example of a registration screen displayed on the touch panel of the input device. [Diagram 23] FIG. 23 is an example of a registration screen displayed on the display of the input device. [Figure 24] FIG. 24 is an example of a sub-plan view displayed on the touch panel of the input device. [Diagram 25] FIG. 25 is an example of a sub-plan view displayed on the display of the input device. [Figure 26] FIG. 26 shows an example of a payment method selection screen displayed on the touch panel of the input device. [Figure 27] FIG. 27 is an example of a payment screen displayed on the touch panel of the input device. [Figure 28] FIG. 28 shows an example of a pop-up displayed on the payment screen of the touch panel of the input device while waiting for payment. [Figure 29] FIG. 29 shows an example of text displayed on the small screen of the display of the input device while waiting for payment. [Diagram 30] FIG. 30 shows an example of a pop-up displayed on a payment screen on a touch panel of an input device when payment is possible at a transaction processing device. [Diagram 31] FIG. 31 shows an example of text that is displayed on a small screen on the display of the input device when payment is possible at the transaction processing device. [Diagram 32] FIG. 32 shows an example of a payment method selection screen displayed on the second touch panel of the transaction processing device. [Diagram 33] FIG. 33 shows an example of a payment notification screen displayed on the second touch panel of the transaction processing device. [Diagram 34] FIG. 34 shows an example of a payment in progress screen displayed on the second touch panel of the transaction processing device. [Diagram 35] FIG. 35 shows an example of a payment completion screen displayed on the second touch panel of the transaction processing device. [Diagram 36] FIG. 36 is an example of a reading screen displayed on the display device. [Figure 37] FIG. 37 is an example of an instruction screen displayed on the display device. [Figure 38] FIG. 38 shows an example of a pop-up displayed on the payment screen of the touch panel of the input device when payment is possible at the payment device. [Figure 39] FIG. 39 shows an example of text displayed on the small screen of the display of the input device when payment is possible at the settlement device. [Diagram 40] FIG. 40 shows an example of a pop-up that notifies the store clerk to specify the payment destination for the amount displayed on the registration screen on the touch panel of the input device. [Diagram 41] FIG. 41 shows an example of a statement confirmation screen displayed on the touch panel of the settlement device. [Diagram 42] FIG. 42 shows an example of a payment method selection screen displayed on the touch panel of the payment device. [Diagram 43] FIG. 43 is an example of a payment notification screen displayed on the touch panel of the settlement device. [Diagram 44] FIG. 44 shows an example of a payment in progress screen displayed on the touch panel of the payment device. [Diagram 45] FIG. 45 is an example of a payment completion screen displayed on the touch panel of the payment device. [Figure 46] FIG. 46 is a flowchart showing main steps of an eighth information processing operation executed by the processor of the settlement device in accordance with the third business program in the second embodiment. [Figure 47]FIG. 47 is a flowchart showing the main steps of a ninth information processing procedure executed by the processor of the reservation server in accordance with the second business program in the second embodiment. [Figure 48] FIG. 48 is an example of a confirmation screen displayed on the display device. [Figure 49] FIG. 49 is a flowchart showing the main steps of a tenth information processing procedure executed by the processor of the reservation server in accordance with the second business program in the third embodiment. [Figure 50] FIG. 50 is a flowchart showing the main steps of a tenth information processing procedure executed by the processor of the reservation server in accordance with the second business program in the third embodiment. [Figure 51] FIG. 51 is a flowchart showing main procedures of an eleventh information processing operation executed by the processor of the settlement device in accordance with the third business program in the third embodiment. [Figure 52] FIG. 52 is a block diagram showing a schematic configuration of a payment system according to the fourth embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] Hereinafter, an embodiment of a payment system that allows a customer to perform operations related to payment will be described with reference to the drawings. [Payment system configuration explanation] FIG. 1 is a block diagram showing a schematic configuration of a payment system 100 according to this embodiment. The payment system 100 includes a reservation 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 reading device 9 for each payment lane L. The payment lane L is a passageway where customers who make payment for transactions line up. When the payment system 100 is introduced in a retail store, the customers are purchasers who purchase products. When the payment system 100 is introduced in a paid facility such as an amusement park, art gallery, or museum, the customers are users who use the facility. Each payment lane L is assigned a unique lane identification information, for example a three-digit lane number.

[0009] Payment system 100 connects holding server 1 to transaction processing devices 3, payment devices 4, and display devices 5 of each payment lane L via a communication network 6 such as a LAN (Local Area Network) for free two-way communication. Payment system 100 also connects input device 2 and transaction processing device 3 for each payment lane L via a transmission cable, and connects payment device 4 and reading device 9 via a transmission cable. The input device 2 and transaction processing device 3, and the payment device 4 and reading device 9 may be connected via short-range wireless communication. Details of holding server 1, input device 2, transaction processing device 3, payment device 4, display device 5, and reading device 9 will be described later.

[0010] Fig. 2 is a schematic diagram showing the relative positions of an input device 2, transaction processing device 3, payment device 4, display device 5, and reading device 9 provided in one payment lane L. Fig. 2 shows a payment lane L in a retail store such as a supermarket or home improvement store. The payment lane L is provided in a checkout area (cash register) that is separate from the sales floor where products are displayed.

[0011] The input device 2 is attached to the checkout counter 20. The checkout counter 20 is arranged along the aisle PA along which customers walk in the direction of the arrow in the figure. The input device 2 is attached to approximately the center of the top surface of the checkout counter 20, and the upstream side of the aisle PA from the input device 2 is used as a space for placing purchased products before registration, and the downstream side is used as a space for placing purchased products after registration.

[0012] The input device 2 comprises, as input / output devices, a fixed scanner 21, a handy scanner 22, a touch panel 23, a keyboard 24, and a display 25. The input device 2 has the fixed scanner 21 disposed so as to protrude upward from the top surface of the checkout counter 20, and the handy scanner 22, the touch panel 23, the keyboard 24, and the display 25 disposed around the fixed scanner 21.

[0013] More specifically, the input device 2 has a stationary scanner 21 fixed to the top surface of the checkout counter 20. The stationary scanner 21 is vertical and fixed so that a barcode reading window is located on the surface opposite to the aisle PA. The input device 2 has a handy scanner 22 engaged with one side of the stationary scanner 21. A touch panel 23 is attached to the top of the stationary scanner 21 so that its operation panel surface faces the same direction as the reading window of the stationary 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. A display 25 is attached to one side of the stationary scanner 21 so that its display screen faces the aisle PA. The display 25 may be a touch panel.

[0014] With such an arrangement of input / output devices, an employee standing in space SP on the opposite side of checkout counter 20 from aisle PA, i.e., a store clerk, can operate fixed scanner 21, handheld scanner 22, touch panel 23, or keyboard 24 to input information related to the transaction with the customer, that is, information related to the products purchased by the customer, such as product code, purchase quantity, discount amount, etc. At this time, the store clerk can confirm the product name, unit price, etc. of the purchased product from the information displayed on touch panel 23. The customer can confirm the product name, unit price, etc. of the purchased product from the information displayed on display 25. The input device 2 can be referred to as a scanner device or the like.

[0015] Transaction processing device 3 is a computer device that functions as a terminal of a POS (Point Of Sales) system. Transaction processing device 3 includes keyboard 31 and first touch panel 32 as devices integrated with device main body 30, and includes handheld scanner 33, second touch panel 34, printer 35, automatic change dispenser 36, cashless payment terminal 37, etc. as devices externally attached to device main body 30. Transaction processing device 3 is placed on the top surface of cash register counter 38, which is installed near the downstream end of checkout counter 20 on the opposite side to aisle PA.

[0016] In detail, the transaction processing device 3 has the device body 30 placed on the cash register counter 38 so 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 the device body 30, the handy scanner 33, the second touch panel 34, the printer 35, the automatic change dispenser 36, and the cashless payment terminal 37 are arranged. The handy scanner 33 is arranged at a position where the store clerk standing in the space SP can operate it. The second touch panel 34 is arranged at a position where the display screen is visible to customers standing in the aisle PA. The printer 35 is arranged at a position where the customers standing in the aisle PA can easily receive a receipt. The automatic change dispenser 36 is arranged at a position where the customers standing in the aisle PA can easily insert cash and take out the dispensed change. The cashless payment terminal 37 is arranged at a position where the customers standing in the aisle PA can easily operate it when making a cashless payment such as a credit card payment, an electronic money payment, or a code payment.

[0017] With such an arrangement of devices, a customer standing in the passage PA can immediately check information displayed on the second touch panel 34, for example, information related to the payment of the price. The customer can immediately receive a receipt issued from the printer 35. A customer who pays with cash can insert cash into the automatic change machine 36 while standing in the passage PA and collect the change that is dispensed. A customer who pays by cashless payment can pay the price cashlessly by operating the cashless payment terminal 37 while standing in the passage PA. In this way, the transaction processing device 3 functions as a self-service type payment device that allows the customer to perform operations related to the payment of the price by himself / herself. The transaction processing device 3 can be referred to as a POS terminal, an electronic cash register, a sales processing device, etc.

[0018] Payment device 4 is also a self-service type payment device that allows customers to perform operations related to payment themselves. Payment device 4 is used by customers who cannot pay at transaction processing device 3 because transaction processing device 3 is in use. For this reason, payment device 4 is installed downstream of transaction processing device 3 in the direction of customer movement indicated by the arrow in the figure. Payment device 4 may also be installed on the opposite side of transaction processing device 3 across the aisle PA.

[0019] The payment device 4 has a box-shaped housing 40 with one side facing the customer. In the following, the side facing the customer is referred to as the front. The payment device 4 has a basket stand 41 attached to the right side when viewed from the front. The basket stand 41 is a space for a customer who uses the payment device 4 to pay for a purchase to place a shopping basket or the like containing purchased items.

[0020] The settlement device 4 includes a touch panel 42 as a man-machine interface with a customer. The touch panel 42 is attached at a position where it is easy for the customer, who is an operator, to operate. In this embodiment, the touch panel 42 is attached to the top of the housing 40 with the display screen facing the front. The settlement device 4 includes a printer 77 (see FIG. 5) for printing receipts built into the housing 40, and a receipt issuing port 43 for issuing receipts printed by the printer 77 is formed on the front side of the housing 40. The settlement device 4 also includes an automatic change machine 78 (see FIG. 5), and a coin insertion port 44, a coin ejection port 45, and a bill receiving / exiting port 46 are formed on the front side of the housing 40. With this arrangement, a customer who pays with cash inserts bills into the bill receiving / exiting port 46 and inserts coins into the coin insertion port 44. Then, the payment device 4 collects bills discharged as change from the bill inlet / outlet 46 or coins dispensed as change from the coin outlet 45, and receives a receipt issued from the receipt issuing port 43. Although not shown in Fig. 1, the payment device 4 also includes a cashless payment terminal 79 (see Fig. 5) and is therefore also capable of handling cashless payments.

[0021] The payment device 4 has a patrol lamp 47 attached to the top of the housing 40. The patrol lamp 47 is a lamp for notifying the operating status of the payment device 4 to store clerks in the space SP. The operating status of the payment device 4 notified by the patrol lamp 47 includes "payment in progress" and "standby." "Payment in progress" refers to the period from when the customer starts to pay the fare until it is finished. The other period refers to "standby." The payment device 4 can be referred to as an accounting machine, a self-service POS terminal, a payment machine, etc.

[0022] The display device 5, which will be described in detail later, is a device that displays transaction identification information that identifies a transaction so that it can be read by the reading device 9. The display device 5 is also a device that accepts instructions from a store clerk as to whether the payment device 4 or the transaction processing device 3 should retrieve information related to the transaction that has been reserved in the reservation server 1. One example of the display device 5 is a tablet. A tablet is a device that has a plate-shaped liquid crystal screen and can be operated by touching the screen with a finger or a pen, etc. The store clerk in the space SP is the operator of the display device 5. For this reason, there are no particular restrictions on where it can be installed, but the display device 5 may be placed in a position that is easy for the store clerk to operate.

[0023] The reading device 9 is a device for reading the transaction identification information displayed on the screen of the display device 5. The reading device 9 outputs the read transaction identification information to the payment device 4. The reading device 9 is attached at 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, for example, a barcode, a two-dimensional code, or the like. The reading device 9 is an optical input device that reads machine-readable codes, such as barcodes and two-dimensional codes, by scanning them with light. The reading device 9 may also be an imaging input device that reads machine-readable codes from images captured by a camera.

[0024] [Configuration of transaction processing device] 3 is a block diagram showing the main circuit configuration of device main body 30 in transaction processing device 3. As shown in the figure, device main body 30 includes 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. System transmission path 612 includes an address bus, a data bus, a control signal line, and the like. System transmission path 612 connects processor 61 to each of the other components, and transmits data signals exchanged between them.

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

[0026] Processor 61 corresponds to the central part of the computer. Processor 61 controls each part to realize various functions of transaction processing device 3 according to an operating system or an application program. Processor 61 is, for example, a CPU (Central Processing Unit). Processor 61 is a multi-core processor that includes multiple processor cores and can execute multiple processes in parallel.

[0027] The main memory 62 corresponds to the main storage portion of the computer. The main memory 62 includes a nonvolatile memory area and a volatile memory area. The main memory 62 stores an operating system or an application program in the nonvolatile memory area. The main memory 62 may store data required for the processor 61 to execute processes for controlling each part in the nonvolatile or volatile memory area. The main memory 62 uses the volatile memory area as a work area where data is appropriately rewritten by the processor 61. The nonvolatile memory area is, for example, a ROM (Read Only Memory). The volatile memory area is, for example, a RAM (Random Access Memory).

[0028] The auxiliary storage device 63 corresponds to the auxiliary storage portion of the computer. For example, an EEPROM (Electric Erasable Programmable Read-Only Memory), an HDD (Hard Disk Drive), or an SSD (Solid State Drive) can be the auxiliary storage device 63. The auxiliary storage device 63 stores data used by the processor 61 in performing various processes, data created by the processes in the processor 61, etc. The auxiliary storage device 63 may also store the above-mentioned application programs.

[0029] The clock 64 keeps track of the date and time. The processor 61 processes the date and time kept by the clock 64 as the current date and time.

[0030] Communications interface 65 is an interface for performing data communication with reservation server 1 connected to communications network 6. Communications interface 65 is also an interface for performing data communication with other servers, such as a POS server, which are also connected to communications network 6, or with payment device 4, display device 5, etc. The POS server is a computer that includes a product master that stores product data such as the product name and unit price of each product sold in the store, and collects and tallys product sales data of purchased products processed by transaction processing device 3, and manages sales, inventory, etc. at the time of sale.

[0031] The scanner interface 66, touch panel interface 67, printer interface 68, change machine interface 69, and payment terminal interface 610 are all interfaces for performing data communication with devices externally attached to the apparatus main body 30. That is, the scanner interface 66 performs data communication with the handheld scanner 33. The touch panel interface 67 performs data communication with the second touch panel 34. The printer interface 68 performs data communication with the printer 35. The change machine interface 69 performs data communication with the automatic change machine 36. The payment terminal interface 610 performs data communication with the cashless payment terminal 37.

[0032] The input device interface 611 is an interface for performing data communication with the input device 2 connected via the transmission cable 7. That is, the input device interface 611 performs data communication with the fixed scanner 21, the handy scanner 22, the touch panel 23, the keyboard 24, and the display 25, respectively.

[0033] FIG. 4 is a schematic diagram showing main storage areas formed in the main memory 62. The transaction processing device 3 uses a part of the volatile storage area in the main memory 62 as an area for a first transaction file 621, a second transaction file 622, a status memory 623, a first flag memory 624, a second flag memory 625, and a 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 a purchased product to be processed as one transaction. The product sales data includes items such as a product code, a product name, a unit price, a purchase quantity, and a sales amount of the purchased product. The sales amount is an amount obtained by multiplying the unit price by the purchase quantity. The product sales data may include at least the product code and the purchase quantity of the purchased product. The status memory 623 is an area for storing a payment status ST. The first flag memory 624 is an area for storing a payment in progress flag Fa. The second flag memory 625 is an area for storing a pending flag Fb. The transaction identification information memory 626 is an area for storing transaction identification information for identifying a transaction.

[0034] The payment status ST is identification information that indicates a status related to payment. There are a first status in which a payment method is not specified by the input device 2, and a second status in which a payment method is specified by the input device 2. In this embodiment, the payment status ST indicating the first status is set to "10," and the payment status ST indicating the second status is set to "20."

[0035] The payment in progress flag Fa is 1-bit data for identifying whether or not a payment is being made in transaction processing device 3. In the present embodiment, the payment in progress flag Fa indicating that a payment is being made is set to "1", and the payment in progress flag Fa indicating that a payment is not being made is set to "0".

[0036] The pending flag Fb is one-bit data for identifying whether or not information relating to a transaction processed by transaction processing device 3 is on hold in reservation server 1. In this embodiment, the pending flag Fb indicating that the information is on hold is set to "1", and the pending flag Fb indicating that the information is not on hold is set to "0".

[0037] The transaction identification information is unique information that is, for example, information specific to transaction processing device 3 combined with the date (year / month / day) and time (hour / minute / second) when the transaction was performed. The transaction identification information may be, for example, a series of numbers that are issued each time a transaction is started. The transaction identification information may be any unique information that can identify a transaction.

[0038] [Settlement device configuration explanation] 5 is a block diagram showing the main circuit configuration of the payment device 4. As shown in the figure, the payment device 4 includes a processor 71, a main memory 72, an auxiliary storage device 73, a clock 74, a communication interface 75, and a system transmission path 76. The system transmission path 76 includes an address bus, a data bus, a control signal line, and the like. The system transmission path 76 connects the processor 71 to each of the other parts, and transmits data signals exchanged between them.

[0039] The payment device 4 constitutes a computer by connecting a processor 71, a main memory 72, an auxiliary storage device 73, a clock 74, and a communication interface 75 via a system transmission path 76. The payment device 4 connects the touch panel 42, the patrol lamp 47, the printer 77, the automatic change machine 78, and the cashless payment terminal 79 to the computer via the system transmission path 76.

[0040] The processor 71 corresponds to the central part of the computer. The processor 71 controls each part to realize various functions of the payment device 4 according to an operating system or an application program. The processor 71 is, for example, a CPU. The processor 71 is a multi-core processor that includes multiple processor cores and can execute multiple processes in parallel.

[0041] The main memory 72 corresponds to the main storage portion of the computer. The main memory 72 includes a nonvolatile memory area and a volatile memory area. The main memory 72 stores an operating system or an application program in the nonvolatile memory area. The main memory 72 may store data required for the processor 71 to execute processes for controlling each part in the nonvolatile or volatile memory area. The main memory 72 uses the volatile memory area as a work area where data is appropriately rewritten by the processor 71. The nonvolatile memory area is, for example, a ROM. The volatile memory area is, for example, a RAM.

[0042] The auxiliary storage device 73 corresponds to the auxiliary storage portion of the computer. For example, an EEPROM, a HDD, or an SSD can be the auxiliary storage device 73. The auxiliary storage device 73 stores data used by the processor 71 when performing various processes, data created by the processes in the processor 71, etc. The auxiliary storage device 73 may also store the application programs described above.

[0043] The clock 74 keeps track of the date and time. The processor 71 processes the date and time kept by the clock 74 as the current date and time.

[0044] Communications interface 75 is an interface for performing data communication with reservation server 1 connected to communications network 6. Communications interface 75 is also an interface for performing data communication with other servers, such as a POS server, which are also connected to communications network 6, transaction processing device 3, display device 5, etc.

[0045] 6 is a schematic diagram showing main storage areas formed in the main memory 72. The settlement device 4 uses a part of the volatile storage area in the main memory 72 as an area for a third transaction file 721 and a 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 products processed as one transaction.

[0046] The third flag memory 722 is an area for storing a payment in progress flag Fc. The payment in progress flag Fc is 1-bit data for identifying whether or not a payment is being made in the settlement device 4. In this embodiment, the payment in progress flag Fc indicating that a payment is being made is set to "1", and the payment in progress flag Fc indicating that a payment is not being made is set to "0".

[0047] [Description of reserved server configuration] 7 is a block diagram showing the main circuit configuration of reservation server 1. As shown in the figure, reservation server 1 includes processor 11, main memory 12, auxiliary storage device 13, clock 14, communication interface 15, and system transmission path 16. System transmission path 16 includes an address bus, a data bus, and a control signal line. System transmission path 16 connects processor 11 to each of the other components, and transmits data signals exchanged between them.

[0048] The reservation server 1 constitutes a computer by connecting a processor 11, a main memory 12, an auxiliary storage device 13, a clock 14, and a communication interface 15 via a system transmission line 16.

[0049] The processor 11 corresponds to the central part of the computer. The processor 11 controls each part to realize various functions of the reservation server 1 according to an operating system or an application program. The processor 11 is, for example, a CPU. The processor 11 is a multi-core processor that includes multiple processor cores and can execute multiple processes in parallel.

[0050] The main memory 12 corresponds to the main storage portion of the computer. The main memory 12 includes a nonvolatile memory area and a volatile memory area. The main memory 12 stores an operating system or an application program in the nonvolatile memory area. The main memory 12 may store data required for the processor 11 to execute processes for controlling each part in the nonvolatile or volatile memory area. The main memory 12 uses the volatile memory area as a work area where data is appropriately rewritten by the processor 11. The nonvolatile memory area is, for example, a ROM. The volatile memory area is, for example, a RAM.

[0051] The auxiliary storage device 13 corresponds to the auxiliary storage portion of the computer. For example, an EEPROM, a HDD, or an SSD can be the auxiliary storage device 13. The auxiliary storage device 13 stores data used by the processor 11 when performing various processes, data created by the processes in the processor 11, etc. The auxiliary storage device 13 may also store the above-mentioned application programs.

[0052] The clock 14 keeps track of the date and time. The processor 11 processes the date and time kept by the clock 14 as the current date and time.

[0053] Communications interface 15 is an interface for performing data communication between transaction processing device 3 , settlement device 4 and display device 5 which are connected to communications network 6 .

[0054] In reservation server 1 having such a configuration, a part of the storage area in auxiliary storage device 13 is used as the area of ​​lane table 131. The data structure of lane table 131 is shown in the schematic diagram of FIG. 8. As shown in the figure, lane table 131 has a column Ca of lane numbers, a column Cb of transaction processing device IDs, a column Cc of settlement device IDs, a column Cd of display device IDs, and a column Ce of transaction identification information. The lane numbers of each settlement lane L are described in column Ca. Columns Cb, Cc, and Cd describe the IDs of transaction processing device 3, settlement device 4, and display device 5 arranged in the settlement lane L of the lane number described in column Ca of the same row. All transaction processing devices 3 constituting settlement system 100 are set with transaction processing device IDs as different identification information. Similarly, all settlement devices 4 are described with payment device IDs as different identification information, and all display devices 5 are described with payment device IDs as different identification information.

[0055] For example, by combining a three-digit number "XXX" with a lane number nnn, a different ID "XXXnnn" can be created for each lane. By making the three-digit number "XXX" different for transaction processing device 3, settlement device 4, and display device 5, a different identification information (device ID) can be created for each device.

[0056] Column Ce is cleared by default. When a transaction is conducted at transaction processing device 3 installed in settlement lane L of the corresponding lane number, column Ce describes transaction identification information of the transaction. Thereafter, when the transaction is settled, the transaction identification information is cleared.

[0057] Furthermore, holding server 1 uses a portion of the memory area in auxiliary memory device 13 as an area for lane-specific folders 132. Lane-specific folders 132 are data folders prepared for the number of settlement lanes L. Lane-specific folders 132 are areas for storing, in other words, holding, information related to transactions output from transaction processing device 3. Holding server 1 stores information related to transactions in lane-specific folder 132 of transaction processing device 3 that output the information. Holding server 1 can be referred to as a holding device.

[0058] [Payment system functionality] 9 is a schematic diagram showing the main functional configurations of each of the reservation server 1, input device 2, transaction processing device 3, settlement device 4, display device 5, and reading device 9. Below, the functions of each will be explained in the order of input device 2, transaction processing device 3, display device 5, reservation server 1, settlement device 4, display device 5, and reading device 9.

[0059] The input device 2 has functions as an input means 201, a completion acceptance means 202, and a first payment acceptance means 203. The input means 201 has a function of inputting information related to a transaction, that is, information related to a purchased commodity purchased by a customer. The input means 201 inputs information related to the purchased commodity, such as a commodity code and a purchase quantity, via an input device such as the fixed scanner 21, the handy scanner 22, the touch panel 23, the keyboard 24, etc. For example, the input means 201 inputs a commodity code of the purchased commodity from a barcode read by the fixed scanner 21 or the handy scanner 22. For example, the input means 201 inputs a purchase quantity of the purchased commodity from a numerical value input by operating the numeric keypad on the touch panel 23 or the keyboard 24.

[0060] The completion receiving means 202 is a function for receiving an instruction to end input of information related to a transaction, that is, information related to a purchased product purchased by a customer. The completion receiving means 202 receives an instruction to end input of information related to a purchased product via an input device such as the touch panel 23 or the keyboard 24. For example, the completion receiving means 202 receives a signal generated by a predetermined key operation on the touch panel 23 or the keyboard 24 as an input end instruction.

[0061] The first payment acceptance means 203 is a function that accepts the selection and input of a payment method via a device operated by a store clerk. The device operated by a store clerk is, for example, a touch panel 23. The first payment acceptance means 203 displays a selection screen for a payment method on the touch panel 23. The first payment acceptance means 203 then accepts the payment method selected by touching the screen as the selected and input payment method. There is no particular restriction on the type of device. For example, it may be a keyboard 24. The payment methods include cash, credit card, electronic money, code payment, etc. The payment methods may also include a gift certificate or other voucher.

[0062] Transaction processing device 3 has the functions of input information acquiring means 301, first amount output means 302, second payment accepting means 303, first settlement means 304, transaction information output means 305, guidance means 306 and execution means 307. Input information acquiring means 301 has a function of acquiring information, etc. from input device 2 connected by transmission cable 7. Input information acquiring means 301 acquires information relating to purchased goods input by input means 201 from input device 2. Input information acquiring means 301 acquires an input end instruction signal accepted by end accepting means 202 from input device 2. Input information acquiring means 301 acquires information on the price payment method accepted by first payment accepting means 203 from input device 2.

[0063] The first amount output means 302 is a function that outputs the amount required for settlement based on the information related to the transaction inputted via the input device 2. The information related to the transaction is, for example, information related to purchased goods. The information related to purchased goods includes the price and sales quantity of the goods. The first amount output means 302 calculates and outputs the amount required for settlement based on the price and sales quantity of each purchased goods. The amount required for settlement can be rephrased as the settlement amount, the total amount, the total amount including tax, the billed amount, etc. The first amount output means 302 outputs the amount required for settlement by displaying it on a display device. The display device corresponds to the touch panel 23 or the display 25 of the input device 2. The display device may be the first touch panel 32 or the second touch panel 34 of the transaction processing device 3.

[0064] The second payment acceptance means 303 is a function that accepts the selection input of the payment method via a device operated by the customer. The device operated by the customer is, for example, the second touch panel 34. The second payment acceptance means 303 displays a selection screen of the payment method on the second touch panel 34. The second payment acceptance means 303 accepts the payment method selected by touching the screen as the selected and input 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 a display. The payment method is cash, credit card, electronic money, code payment, etc. The second payment acceptance means 303 accepts the selection input of the payment method when the first payment acceptance means 203 has not accepted the selection input of the payment method at the time when the end acceptance means 202 accepts the input end instruction. Whether or not the selection input of the payment method has been accepted at the time when the input end instruction is accepted can be identified by the payment status ST. Specifically, when the payment status ST is “10”, that is, in the first state in which no payment method has been specified using the input device 2, the second payment acceptance means 303 accepts the selection and input of any one of the payment methods via the second touch panel 34.

[0065] The first payment means 304 is a function of settling a transaction with a customer according to the payment method accepted by the first payment acceptance means 203 or the second payment acceptance means 303. The first payment means 304 settles a transaction with a customer if the transaction can be settled at the time when the end acceptance means 202 accepts the input end instruction. That is, the first payment means 304 determines that the transaction can be settled when the payment in progress flag Fa stored by the first flag memory 624 is "0". For example, when the first payment means 304 accepts cash as the payment method, it settles the transaction with the customer in cooperation with the automatic change machine 36. For example, when the first payment means 304 accepts cashless payment as the payment method, it settles the transaction with the customer in cooperation with the cashless payment terminal 37.

[0066] The transaction information output means 305 is a function that outputs information related to a transaction to the reservation server 1. When the transaction information output means 305 receives an instruction to end input of information related to a transaction from the input device 2 in a state where settlement of the transaction is not possible, the transaction information output means 305 outputs information related to the transaction to the reservation server 1. The information related to the transaction is, for example, information related to a purchased product. The information related to the purchased product is stored in the first transaction file 621 or the second transaction file 622 as product sales data. When the payment in progress flag Fa of the first flag memory 624 is "1" and the input information acquisition means 301 acquires a signal instructing to end input, the transaction information output means 305 controls the communication interface 65 to output the product sales data of the first transaction file 621 or the second transaction file 622 to the reservation server 1.

[0067] Guiding means 306 is a function that provides guidance on the output destination of information related to a transaction held in holding server 1. The output destination of information related to a transaction held in holding server 1 is payment device 4 or transaction processing device 3. When the output destination of information related to a transaction is payment device 4, guidance means 306 provides guidance on payment at payment device 4. When the output destination of information related to a transaction is transaction processing device 3, guidance means 306 provides guidance on payment at transaction processing device 3. For example, guidance is given to a store clerk or a customer by displaying a guidance image on a display device. The display device corresponds to touch panel 23 or display 25 of input device 2, or first touch panel 32 or second touch panel 34 of transaction processing device 3, etc.

[0068] Execution means 307 is a function that executes settlement of a transaction with a customer based on information related to the transaction held by holding server 1. When execution means 307 is instructed to execute settlement from holding server 1, it operates first amount output means 302 and first settlement means 304 to execute settlement of the transaction with the customer. When the output destination of the information related to the transaction held by holding server 1 is determined to be transaction processing device 3, the information related to the transaction is output from holding server 1 to transaction processing device 3 and stored, for example, in second transaction file 622. When execution means 307 is instructed to execute settlement from holding server 1, it executes settlement based on the information related to the transaction stored in second transaction file 622.

[0069] Display device 5 has the functions of reception means 501 and instruction means 502. Reception means 501 has a function of receiving an output destination of information related to a transaction held in holding server 1. As described above, the output destination of the information related to the transaction is settlement device 4 or transaction processing device 3. Reception means 501 includes a first operator declaring that the output destination of the information related to the transaction is settlement device 4, and a second operator declaring that the output destination of the information related to the transaction is transaction processing device 3. When a tablet is used as display device 5, the first operator and the second operator are soft keys displayed on the liquid crystal screen of the tablet. When the first operator is operated and input, reception means 501 accepts payment device 4 as the output destination of the information related to the transaction. When the second operator is operated and input, reception means 501 accepts transaction processing device 3 as the output destination of the information related to the transaction.

[0070] Instructing means 502 is a function that instructs holding server 1 to output information related to the transaction to the output destination accepted by accepting means 501. When the output destination accepted by accepting means 501 is payment device 4, instructing means 502 instructs holding server 1 to output information related to the transaction to payment device 4. Specifically, instructing means 502 outputs a signal to holding server 1 instructing it to output information related to the transaction to payment device 4. When the output destination accepted by accepting means 501 is transaction processing device 3, instructing means 502 instructs holding server 1 to output information related to the transaction to transaction processing device 3. Specifically, instructing means 502 outputs a signal to holding server 1 instructing it to output information related to the transaction to transaction processing device 3.

[0071] Display device 5 also has a function as display means 503. Display means 503 has a function of displaying transaction identification information that identifies a transaction whose information has been output to holding server 1 by transaction information output means 305 of transaction processing device 3 in a manner that can be read by reading device 9. Specifically, display means 500 converts the information related to the transaction into a machine-readable code such as a barcode, a two-dimensional code, or the like, and displays it on the screen of display device 5.

[0072] The reading device 9 includes a reading means 901. The reading means 901 has a function of reading the transaction identification information displayed on the screen of the display device 5. For example, when 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 reading device 9 reads the machine-readable code from an image captured by a camera.

[0073] Reserve server 1 has functions as recognition means 101, transaction information input means 102, reserve means 103, and reserve information output means 104. Recognition means 101 has a function of recognizing an output destination instructed by display device 5. When recognition means 101 receives a signal from instruction means 502 of display device 5 instructing to output information related to a transaction to transaction processing device 3, it recognizes the output destination as transaction processing device 3. When recognition means 101 receives a signal from instruction means 502 of display device 5 instructing to output information related to a transaction to payment device 4, it recognizes the output destination as payment device 4.

[0074] Transaction information input means 102 is a function that inputs transaction-related information output from transaction processing device 3. Transaction information input means 102 includes a process for identifying which transaction processing device 3 output the input transaction-related information. The transaction-related information includes the transaction processing device ID of the transaction processing device 3 that output the information. Transaction information input means 102 specifies the transaction processing device 3 identified by the transaction processing device ID as the output source of the transaction-related information.

[0075] Holding means 103 has a function of holding transaction-related information output from transaction processing device 3. Holding means 103 holds the transaction-related information input by transaction information input means 102 for each transaction processing device 3 identified as the output source of the information. Specifically, holding means 103 holds the transaction-related information for each transaction processing device 3 by storing the transaction-related information in lane-specific folder 132 for settlement lane L in which transaction processing device 3 identified as the sender of the transaction-related information is installed.

[0076] The pending information output means 104 is a function that outputs information related to a transaction to the payment device 4 in response to an import request from the payment device 4. Specifically, when there is an import request from the payment device 4, the pending information output means 104 identifies the payment lane L in which the payment device 4 is installed, and outputs information related to the transaction that has been reserved in the lane-specific folder 132 of that payment lane L to the payment device 4.

[0077] Pending information output means 104 also has a function of outputting information related to the transaction held by holding means 103 to an output destination instructed by display device 5. When payment is possible at the output destination instructed by display device 5, pending information output means 104 outputs information related to the transaction stored in lane-specific folder 132 to the output destination. For example, when the output destination instructed by display device 5 is payment device 4, pending information output means 104 outputs information related to the transaction to payment device 4 when the payment in progress flag Fc of payment device 4 is "0". For example, when the output destination instructed by display device 5 is transaction processing device 3, pending information output means 104 outputs information related to the transaction to transaction processing device 3 when the payment in progress flag Fa of transaction processing device 3 is "0". Incidentally, the former on-hold information output means 104 may be rephrased as a first on-hold information output means, and the latter on-hold information output means 104 may be rephrased as a second on-hold information output means.

[0078] The payment device 4 has the functions of an import means 401, a second amount output means 402, a third payment acceptance means 403, and a second payment means 404. The import means 401 has a function of importing information related to a transaction held in the holding server 1. Specifically, the import means 401 has a function of importing information related to a transaction identified by transaction identification information read by the reading device 9 from the holding server 1. The import means 401 also has a function of importing information related to a transaction for which the payment device 4 is instructed as an output destination by the display device 5. The import means 401 stores the information related to the transaction imported from the holding server 1 in a third transaction file 721. Incidentally, the former capture means 401 may be rephrased as a first capture means, and the latter capture means 401 may be rephrased as a second capture means.

[0079] The second amount output means 402 is a function that outputs the amount required for payment based on information related to the transaction held in the holding server 1. The second amount output means 402 outputs the amount required for payment based on information related to the transaction captured by the capture means 401. The second amount output means 402 outputs the amount required for payment by displaying it on a display device. The display device corresponds to the touch panel 42 of the payment device 4 or the like.

[0080] The third payment acceptance means 403 is a function that accepts the selection and input of a payment method via a device operated by a customer. The device operated by a customer is, for example, a touch panel 42. The third payment acceptance means 403 displays a selection screen for a payment method on the touch panel 42. The third payment acceptance means 403 then accepts the payment method selected by touching the screen as the selected and input payment method. There is no particular limitation on the type of device. The device operated by a customer may be a pointing device that moves a pointer displayed on a display. The payment method may be cash, credit card, electronic money, code payment, etc.

[0081] The second payment means 404 has a function of settling a transaction with a customer according to the payment method accepted by the first payment acceptance means 203 or the third payment acceptance means 403. The second payment means 404 settles a transaction with a customer when the amount equivalent to the amount output by the second amount output means 402 is paid by the payment method accepted by the first payment acceptance means 203 or the third payment acceptance means 403. For example, when cash is accepted as the payment method, the second payment means 404 settles the transaction with the customer in cooperation with the automatic change machine 78. For example, when cashless payment is accepted as the payment method, the second payment means 404 settles the transaction with the customer in cooperation with the cashless payment terminal 79.

[0082] 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 in accordance with the first business program.

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

[0084] The functions of the reservation server 1 as the recognition means 101, the transaction information input means 102, the reservation means 103 and the reservation information output means 104 are realized by the information processing executed by the processor 11 in accordance with the second business program.

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

[0086] The functions of the payment device 4 as the import means 401, the second amount output means 402, the third payment receiving means 403 and the second payment means 404 are realized by information processing executed by the processor 71 in accordance with the third business program.

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

[0088] [Explanation of payment system operation] Next, the main operations of the payment system 100 will be explained using the flowcharts of Figures 10 to 21 and the screen examples of Figures 22 to 48. Note that the content and procedures of the operations explained using the flowcharts are merely examples. The content and procedures can be changed as appropriate as long as similar operational effects can be achieved. The screen examples are also merely examples. The content of the output text, the arrangement of images, the type and layout of the software keys, etc. can be changed as appropriate.

[0089] 10 to 13 are flow charts showing the main steps of the first information processing executed by processor 61 of transaction processing device 3 according to the first business program. After walking around the sales floor and collecting the purchased items, the customer moves to the checkout area. The customer then places the purchased items on checkout counter 20 in an empty aisle PA. When the customer approaches the checkout area, a store clerk standing in space SP issues a command to start registration. For example, the store clerk touches the start button displayed on touch panel 23. This operation is a command to start registration. In response to this command, processor 61 starts the first information processing. Processor 61 sets the screen of touch panel 23 and display 25 of input device 2 as the registration screen as ACT101.

[0090] FIG. 22 is an example of a registration screen SAa displayed on the touch panel 23. The registration screen SAa is divided into a current area AAa, a details area AAb, and a total area AAc. The current area AAa is an area for displaying the product name, purchase quantity, and sales price of the most recently purchased item. The details area AAb is an area for displaying in list form, in sequential numerical order, the product name, purchase quantity, unit price, discount amount, and sales price of the purchased items in one transaction. The total area AAc is an area for displaying the total purchase quantity and total sales price of the purchased items in one 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 for commanding the output of a subtotal of the purchased items registered as one transaction.

[0091] Fig. 23 is an example of registration screen SBa displayed on display 25. Registration screen SBa divides the screen into multiple rows (seven rows in the example of Fig. 23), with the first row through the rows just before the last row being rows of detail area ABa, and the last row being a row of total area ABb. Each row of detail area ABa displays the product name, unit price, purchase quantity, and sales amount of the purchased product. In total area ABb, each row displays the total purchase quantity and total sales amount.

[0092] After checking registration screen SAa, the clerk registers the purchased item placed on checkout counter 20. That is, the clerk scans the barcode attached to the purchased item with fixed scanner 21 or handheld scanner 22 of input device 2. By scanning the barcode, the product code of the purchased item is input to transaction processing device 3 via input device interface 611. If the purchased item does not have a barcode, the clerk causes touch panel 23 of input device 2 to display a list of items without barcodes. The clerk then selects the purchased item from the list. Through this operation, the product code of the purchased item without a barcode is input to transaction processing device 3 via input device interface 611.

[0093] The processor 61, which has set the screens of the touch panel 23 and the display 25 to the registration screen SAa and the registration screen SBa, proceeds to ACT102. The processor 61 waits for the registration of the purchased product in ACT102. When the product code is input from the input device 2 via the input device interface 611, the processor 61 determines that the purchased product has been registered. The processor 61 proceeds from ACT102 to ACT103. The processor 61 processes the product sales data in ACT103. This process is a process of reading the product name, unit price, etc. of the product specified by the input product code from the product master, and generating product sales data of the purchased product including the product code, product name, unit price, purchase quantity, sales amount, etc. The processor 61, which has generated the product sales data of the purchased product, proceeds to ACT104. The processor 61 writes and stores the product sales data of the purchased product in the first transaction file 621 in ACT104.

[0094] After storing the product sales data of the purchased product, the processor 61 proceeds to ACT 105. In ACT 105, the processor 61 updates the registration screen SAa and the registration screen SBa.

[0095] Regarding the registration screen SAa, the processor 61 displays in the current area AAa the product name, purchase quantity, and sales amount of the sales data written in the first transaction file 621. At this time, if the product sales data of the previously registered purchased product is displayed in the current area AAa, the processor 61 displays in the details area AAb the product name, purchase quantity, unit price, discount amount, and sales amount of the product sales data. The processor 61 also displays in the total area AAc the total purchase quantity and sales amount of all the product sales data stored in the first transaction file 621.

[0096] Regarding the registration screen SBa, the processor 61 displays on the first line of the detail area ABa the product name, unit price, purchase quantity, and sales amount of the sales data written in the first transaction file 621. At this time, if the sales data is displayed on the first line of the detail area ABa, the processor 61 shifts the data from the first line onwards to the second line onwards, and then displays on the first line the sales data written in the first transaction file 621. The processor 61 also displays in the total area ABb the total purchase quantity and sales amount of all the product sales data stored in the first transaction file 621.

[0097] After updating the registration screen SAa and the registration screen SBa, the processor 61 proceeds to ACT106. The processor 61 checks whether the next purchased item has been registered in ACT106. If the next purchased item has not been registered, the processor 61 proceeds to ACT107. The processor 61 checks whether the subtotal button BAa has been pressed in ACT107. If the subtotal button BAa has not been pressed, the processor 61 returns to ACT106. In this way, the processor 61 waits for the next purchased item to be registered or the subtotal button BAa to be pressed in ACT106 and ACT107.

[0098] When the purchased goods are registered in the standby state of ACT106 and ACT107, the processor 61 returns from ACT106 to ACT103. Then, the processor 61 executes the processes of ACT103 to ACT105 in the same manner as described above. Thus, every time the store clerk operates the fixed scanner 21, the handy scanner 22, or the touch panel 23 of the input device 2 to input data of the purchased goods placed on the checkout counter 20 one by one, the processor 61 generates product sales data of the purchased goods based on information related to the purchased goods, i.e., the product code, and stores it in the first transaction file 621. The processor 61 also updates the registration screen SAa and the registration screen SBa. Thus, when the registration of the purchased goods is completed, the store clerk touches the subtotal button BAa.

[0099] In the standby state of ACT106 and ACT107, when the subtotal button BAa is input by a touch operation, the processor 61 proceeds to ACT 108. In ACT 108, the processor 61 sets the touch panel 23 and the screen of the display 25 in the input device 2 as a subtotal screen.

[0100] FIG. 24 is an example of a subtotal display screen SAb displayed on the touch panel 23. The subtotal display screen SAb includes a total area AAd in which the total purchase quantity of purchased items in one transaction and the total sales amount are displayed. The subtotal display screen 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 for instructing a discount on the total amount. The subtotal discount button BAc is an operator for instructing a discount on the total amount. Incidentally, the total amount is discounted by inputting the subtotal discount button BAb and inputting the discount amount on the numeric keypad of the keyboard 24. Similarly, the total amount is discounted by inputting the subtotal discount button BAc and inputting a discount rate on the numeric keypad of the keyboard 24.

[0101] The payment method selection button BAd is an operator for instructing the selection of a payment method. The payment button BAe is an operator for instructing the completion of the registration of the purchased item and the transition to the payment of the price. The back button BAf is an operator for instructing the return to the registration of the purchased item.

[0102] 25 is an example of the sub-screen SBb displayed on the display 25. The sub-screen SBb includes an area ABc in which information regarding payment is displayed. Area ABc displays the total quantity and total price of purchased items, the deposit amount, and the remaining balance. At this point, no deposit has been generated, so the deposit amount is 0 yen, and the remaining balance is the total amount minus the deposit amount.

[0103] After checking the small screen SAb, the clerk checks whether any unregistered purchased items remain on the checkout counter 20. If there are unregistered purchased items, the clerk touches the back button BAf. If there are no unregistered purchased items, the clerk decides whether to ask the customer about the payment method. For example, the clerk may ask the customer about the payment method during times when the store is busy, and not ask the customer about the payment method during times when the store is quiet. If the clerk decides to ask the customer about the payment method, the clerk touches the payment method selection button BAd. If the clerk does not decide to ask the customer about the payment method, the clerk touches the payment button BAe.

[0104] The processor 61, which has set the screen of the touch panel 23 to the small plan screen SAb and the screen of the display 25 to the small plan screen SBb, proceeds to ACT109. The processor 61 checks whether the back button BAf has been input in ACT109. If the back button BAf has not been input, the processor 61 proceeds to ACT110. The processor 61 checks whether the payment method selection button BAd has been input in ACT110. If the payment method selection button BAd has not been input, the processor 61 proceeds to ACT111. The processor 61 checks whether the payment button BAe has been input in ACT111. If the payment button BAe has not been input, the processor 61 returns to ACT109. In this way, the processor 61, which has displayed the small plan screen SAb, waits for the back button BAf to be input, the payment method selection button BAd to be input, or the payment button BAe to be input in ACT109 to ACT111.

[0105] When the back button BAf is input by touch operation in the standby state of ACT109 to ACT111, the processor 61 proceeds from ACT109 to ACT112. In ACT112, the processor 61 returns the screens of the touch panel 23 and the display 25 to the previous registration screens SAa and SBa. Then, the processor 61 enters a standby state for ACT106 and ACT107. Thus, the store clerk can operate the fixed scanner 21, the handy scanner 22 or the touch panel 23 of the input device 2 to input data of the purchased product that has not been registered.

[0106] In the standby state of ACT109 to ACT111, when the payment method selection button BAd is input by touch operation, the processor 61 proceeds from ACT110 to ACT121 of Fig. 11. In ACT121, the processor 61 changes the screen of the touch panel 23 to the payment method selection screen SAc (see Fig. 26). The screen of the display 25 remains the sub-screen SBb.

[0107] 26 is an example of a 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 sub-screen SAb. The payment method selection screen SAc also includes a selection button group 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.

[0108] The cash button is a button for commanding a cash payment. The credit button is a button for commanding a credit card payment. The electronic money button is a button for commanding an electronic money payment. The code payment button is a button for commanding a code payment 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 commanding payment with a gift certificate or other voucher.

[0109] After checking the payment method selection screen SAc, the store clerk confirms with the customer the payment method. The store clerk then touches the button for the payment method selected by the customer. For example, if the customer wishes to pay with cash, the store clerk touches the cash button in the selection button group BAg. For example, if the customer wishes to pay with a credit card, the store clerk touches the credit button in the selection button group BAg. Similarly, if the customer wishes to pay with electronic money or code payment, the store clerk touches the appropriate button in the selection button group BAg.

[0110] The processor 61, which has set the screen of the touch panel 23 to the payment method selection screen SAc, proceeds to ACT122. The processor 61 waits for a payment method to be selected in ACT122. When any payment method is selected by touching the selection button group BAg, the processor 61 proceeds to ACT123. The processor 61 acquires a payment code for the selected payment method in ACT123. In this embodiment, a unique payment code is set in advance for each payment method, such as cash payment, credit card payment, electronic money payment, and code payment. For example, when the cash button is touched, the processor 61 acquires a payment code corresponding to cash payment, such as "11". For example, when the credit button is touched, the processor 61 acquires a payment code corresponding to credit card payment, such as "22". The same applies when other electronic money buttons and code payment buttons are touched.

[0111] The processor 61, having acquired the payment code, proceeds to ACT 124. In ACT 124, the processor 61 displays the payment screen SAd (see FIG. 27) on the screen of the touch panel 23. The screen of the display 25 remains the sub-screen SBb.

[0112] FIG. 27 is an example of the payment screen SAd when cash payment is selected as the payment method. The payment screen SAd includes a sub-screen SAb and a total area AAd similar to the payment method selection screen SAc. The payment screen SAd also includes a payment button BAh. The payment button BAh is an operator for instructing the transition to payment of the price. The payment button BAh is a software key. After checking the payment screen SAd, the store clerk touches the payment button BAh.

[0113] The processor 61, which has set the screen of the touch panel 23 to the payment screen SAd, proceeds to ACT 125. The processor 61 waits for the payment button BAh to be input in ACT 125. When the payment button BAh is input by a touch operation, the processor 61 proceeds to ACT 126.

[0114] On the other hand, when the payment button BAe is input by a touch operation in the standby state of ACT109 to ACT111 in Fig. 10, the processor 61 proceeds from ACT111 to ACT126 in Fig. 11. In this way, when the payment button BAe on the sub-screen SAb or the payment button BAh on the payment screen SAd is input, the processor 61 proceeds to ACT126.

[0115] Processor 61 checks the payment in progress flag Fa in ACT126. When no payment has been made in transaction processing device 3, payment in progress flag Fa is "0". When payment in progress flag Fa is "0", processor 61 proceeds from ACT126 to ACT131 in Fig. 12. The process after ACT131 will be described later.

[0116] If the payment in progress flag Fa is "1" in ACT126, i.e., payment is being made at transaction processing device 3, processor 61 proceeds to ACT127. Processor 61 checks the pending flag Fb in ACT127. If information relating to the transaction of the previous customer who made payment in the same settlement lane L is not being held in holding server 1, the pending flag Fb is "0". If the pending flag Fb is "0", processor 61 proceeds from ACT128 to ACT141 in FIG. 13. The processing after ACT141 will also be described later.

[0117] If the pending flag Fb is "1" in ACT127, that is, information related to the transaction of the previous customer who made a payment in the same payment lane L is pending in the pending server 1, the processor 61 proceeds to ACT128. In ACT128, the processor 61 displays a pop-up PUa (see FIG. 28) on the sub-screen SAb or payment screen SAd of the touch panel 23 to notify the user that payment is not possible. The processor 61 also displays text TXa (see FIG. 29) on the sub-screen SBb of the display 25 to instruct the user to wait because payment is not possible.

[0118] 28 shows an example of a pop-up PUa displayed on the payment screen SAd of the touch panel 23. When the store clerk sees the pop-up PUa, he or she waits until the previous customer finishes paying.

[0119] 29 is an example of the text TXa displayed on the sub-screen SBb of the display 25. After checking the text TXa, the customer waits until payment is possible.

[0120] After notifying the user using the touch panel 23 and the display 25 that payment is not possible, the processor 61 returns to ACT125. The processor 61 waits for the payment button BAe or the payment button BAh to be pressed again. When the payment button BAe or the payment button BAh is pressed, the processor 61 proceeds to ACT126. Then, the processor 61 executes the process from ACT126 onwards in the same manner as described above. Therefore, if the payment in progress flag Fa has been rewritten to "0", the processor 61 proceeds to ACT131 in FIG. 12. If the payment in progress flag Fa remains at "1" but the pending flag Fb has been rewritten to "0", the processor 61 proceeds to ACT141 in FIG. 13.

[0121] On the other hand, 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 sub-screen SAb or the payment screen SAd of the touch panel 23, and the text TXa continues to be displayed on the sub-screen SBb of the display 25.

[0122] When payment in progress flag Fa is "0", that is, when payment is not being made at transaction processing device 3, if payment button BAe on sub-screen SAb or payment button BAh on payment screen SAd is pressed, processor 61 proceeds to ACT131 in Fig. 12. In ACT131, processor 61 displays a pop-up PUb (see Fig. 30) on sub-screen SAb or payment screen SAd of touch panel 23 to notify that payment is possible at transaction processing device 3. Processor 61 also displays text TXb (see Fig. 31) on sub-screen SBb of display 25 to indicate that payment is possible.

[0123] 30 is an example of a pop-up PUb displayed on payment screen SAd of touch panel 23. A store clerk who sees the pop-up PUb knows that payment can be made at transaction processing device 3, and will guide the customer to where transaction processing device 3 is installed.

[0124] 31 is an example of text TXb displayed on sub-screen SBb of display 25. After checking text TXb, the customer follows the guidance of the store clerk to where transaction processing device 3 is installed and makes payment.

[0125] After notifying that payment can be made using the touch panel 23 and the display 25, the processor 61 proceeds to ACT 132. The processor 61 controls to store the data stored in the first transaction file 621 in ACT 132, that is, the product sales data of the purchased product registered as one transaction, in the second transaction file 622.

[0126] In this way, when the product sales data of the purchased product registered as one transaction in the second transaction file 622 is stored, the processor 61 proceeds to ACT 133. In ACT 133, the processor 61 checks whether or not a payment code has been acquired.

[0127] If the payment code has not been acquired, the processor 61 proceeds from ACT133 to ACT134. The processor 61 sets the payment status ST stored in the status memory 623 to "10" in ACT134. On the other hand, if the payment code has been acquired in the processing of ACT123, the processor 61 proceeds from ACT133 to ACT135. The processor 61 adds the payment code to the second transaction file 622 in ACT135. The processor 61 also sets the payment status ST stored in the status memory 623 to "20" in ACT136.

[0128] Upon completing the processing of ACT134 or ACT136, the processor 61 proceeds to ACT137. In ACT137, the processor 61 rewrites the payment in progress flag Fa in the first flag memory 624 to "1". In addition, in ACT138, the processor 61 clears the first transaction file 621. With this, the processor 61 ends the first information processing.

[0129] On the other hand, when the payment flag Fa is "1" but the pending flag Fb is "0", if the payment button BAe on the sub-plan screen SAb or the payment button BAh on the payment screen SAd is input, the processor 61 proceeds to ACT141 in FIG. 13. The processor 61 checks whether or not a payment code has been acquired in ACT141. If a payment code has not been acquired, the processor 61 proceeds from ACT141 to ACT142. The processor 61 sets the payment status ST stored in the status memory 623 to "10" in ACT142. On the other hand, if a payment code has been acquired in the processing of ACT123, the processor 61 proceeds from ACT141 to ACT143. The processor 61 adds the payment code to the first transaction file 621 in ACT143. The processor 61 also sets the payment status ST stored in the status memory 623 to "20" in ACT144.

[0130] Upon completing the processing of ACT142 or ACT144, processor 61 proceeds to ACT145. Processor 61 generates transaction identification information in ACT145. For example, processor 61 generates unique transaction identification information by combining the transaction processing device ID, which is unique information of transaction processing device 3, with the date (year, month, day) and time (hour, minute, second) at which the transaction was performed. Alternatively, processor 61 may count up a counter that issues serial numbers by "1" and generate unique transaction identification information by combining the serial number with the transaction processing device ID.

[0131] Having generated the transaction identification information, processor 61 proceeds to ACT 146. Processor 61 transmits a hold event to hold server 1 via communication interface 65 as ACT 146. The hold event is an event requesting the holding of first transaction file 621. The hold event includes the transaction processor ID of the transaction processor 3.

[0132] Although details will be described later, an acceptance response is returned from the reservation server 1 that has received the reservation event, and the processor 61 waits for the acceptance response in ACT147. Then, when the acceptance response is received via the communication interface 65, the processor 61 proceeds to ACT148. In ACT148, 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 product to be processed as one transaction, to the reservation server 1 together with the transaction identification information generated in the processing of ACT145.

[0133] Thereafter, the processor 61 sets the pending flag Fb to "1" in ACT 149. The processor 61 also clears the first transaction file 621 in ACT 150. With this, the processor 61 ends the first information processing.

[0134] 12, if payment in progress flag Fa is "0" when payment button BAe or payment screen SAd is entered, that is, if no customer is paying at transaction processing device 3, a notification is issued that payment can be made at transaction processing device 3. In addition, payment in progress flag Fa becomes "1", and first transaction file 621 is cleared. Therefore, the customer will go to the location of transaction processing device 3 to make payment.

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

[0136] 12 and 13, when the first information processing ends, first transaction file 621 is cleared by the processing of ACT138 or ACT150. Therefore, processor 61 of transaction processing device 3 can continue to start the first information processing. That is, when the next customer comes to the checkout area and the store clerk issues a command to start registration, processor 61 executes the first information processing from ACT101 onwards in the same manner as described above. Therefore, the screen of touch panel 23 becomes registration screen SAa.

[0137] Here, the processor 61 executes the processes of ACT102 and ACT106 via the input device interface 611, thereby realizing the function of the input information acquiring means (first input information acquiring means) 301 that acquires information on the purchased product inputted by the input means 201 from the input device 2. The processor 61 also executes the processes of ACT111 and ACT125 via the input device interface 611, thereby realizing the function of the input information acquiring means (second input information acquiring means) 301 that acquires the input end instruction signal accepted by the end acceptance means 202 from the input device 2. The processor 61 also executes the processes of ACT121 to ACT123 via the input device interface 611, thereby realizing the function of the input information acquiring means (third input information acquiring means) 301 that acquires information on the payment method accepted by the first payment acceptance means 203 from the input device 2.

[0138] The processor 61 cooperates with the touch panel 23 and the display 25 to execute the processes of ACT108 and ACT124, thereby realizing the function of the first amount output means 302. The processor 61 cooperates with the communication interface 65 to execute the processes of ACT145 to ACT147, thereby realizing the function of the transaction information output means 305.

[0139] 14 is a flowchart showing the main steps of the second information processing executed by processor 61 of transaction processing device 3 in accordance with the first business program. Processor 61 executes the second information processing in parallel with the first information processing described above.

[0140] The processor 61 waits for the payment in progress flag Fa to become "1" in ACT151. When the payment in progress flag Fa becomes "1" in ACT137 of the first information processing, the processor 61 proceeds to ACT152. The processor 61 checks the payment status ST in ACT152. If the payment status ST is "10", that is, if a payment method was not selected in the first information processing, the processor 61 proceeds from ACT152 to ACT153. The processor 61 sets the screen of the second touch panel 34 to the payment method selection screen SCa (see FIG. 32) in ACT153.

[0141] 32 is an example of a 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 group of selection buttons 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 in which the total purchase quantity and the total sales amount of the purchased items in one transaction are displayed. The total area ACa displays the total purchase quantity and the total sales amount calculated based on the product sales data of the purchased items stored in the second transaction file 622.

[0142] After checking the payment method selection screen SCa, the customer touches the button for the desired payment method. For example, a customer who wishes to pay by cash touches the cash button in the selection button group BCa. For example, a customer who wishes to pay by credit card touches the credit button in the selection button group BCa. For example, a customer who wishes to pay by electronic money touches the electronic money button in the selection button group BCa. For example, a customer who wishes to pay by code payment touches the code payment button in the selection button group BCa.

[0143] The processor 61, having set the screen of the second touch panel 34 to the payment method selection screen SCa, proceeds to ACT154. The processor 61 waits for a payment method to be selected in ACT154. When any payment method is selected by a touch operation on the selection button group BCa, the processor 61 proceeds to ACT155. In ACT155, the processor 61 acquires the payment code of the selected payment method, similar to the processing in ACT123 of the first information processing.

[0144] On the other hand, if the payment status ST is "20" in ACT152, that is, if the payment method was selected in the first information processing, the processor 61 proceeds from ACT152 to ACT156. The processor 61 extracts a payment code from the second transaction file 622 in ACT156.

[0145] After completing the process of ACT155 or ACT156, the processor 61 proceeds to ACT157. In ACT157, the processor 61 sets the screen of the second touch panel 34 to a payment notification screen SCb (see FIG. 33). The payment notification screen SCb is a screen based on the payment code obtained by the process of ACT155 or ACT156.

[0146] Fig. 33 is an example of the payment notification screen SCb displayed on the second touch panel 34. Fig. 33 shows the payment notification screen SCb when a payment code for cash payment is obtained by processing ACT155 or ACT156. The payment notification screen SCb includes a change machine information area ACb. The change machine information area ACb displays the total amount, the total amount of cash inserted into the automatic change machine 36 (the so-called inserted amount), and the remaining amount obtained by subtracting the inserted amount from the total amount.

[0147] After checking the payment notification screen SCb, the customer pays the amount using the payment method of their choice. For example, a customer who selects cash payment inserts cash into the automatic change machine 36. A customer who selects credit card payment has the credit card data read by the reader of the cashless payment terminal 37. A customer who selects electronic money payment has the data on the electronic money medium read by the reader of the cashless payment terminal 37. A customer who selects code payment has the barcode or two-dimensional data code for code payment read by the scanner of the cashless payment terminal 37.

[0148] The processor 61, having set the screen of the second touch panel 34 to the payment notification screen SCb, proceeds to ACT158. The processor 61 waits for the start of payment in ACT158. For example, if cash payment is selected, the processor 61 waits for cash to be inserted into the automatic change machine 36. For example, if credit card payment is selected, the processor 61 waits for 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 electronic money data to be read by the cashless payment terminal 37. For example, if code payment is selected, the processor 61 waits for a barcode or two-dimensional data code for code payment to be read by the cashless payment terminal 37.

[0149] When payment is initiated, processor 61 proceeds from ACT158 to ACT159. Processor 61 issues a transaction number in ACT159. The transaction number is, for example, a seven-digit number consisting of a three-digit transaction processing device ID plus a four-digit serial number. The serial number is incremented by "1" each time a transaction is settled in transaction processing device 3. After issuing the transaction number, processor 61 proceeds to ACT160. In ACT160, processor 61 displays the payment in progress screen SCc (see FIG. 34) on the screen of second touch panel 34.

[0150] FIG. 34 is an example of the payment in progress screen SCc displayed on the second touch panel 34. FIG. 34 shows the payment in progress screen SCc when a payment code for cash payment is obtained by processing ACT155 or ACT156. The payment in progress screen SCc has the same layout as the payment notification screen SCb. On the cash payment in progress screen SCc, the information displayed in the change machine information area ACb is updated according to the amount of cash inserted into the automatic change machine 36. The payment in progress screen SCc further includes a checkout button BCb. The checkout button BCb is a software key. The checkout button BCb is an operator for instructing the completion of payment. When the customer has finished paying the price using the selected payment method, he or she touches the checkout button BCb.

[0151] The processor 61, which has set the screen of the second touch panel 34 to the payment in progress screen SCc, proceeds to ACT161. The processor 61 waits for the checkout button BCb to be input in ACT161. When the checkout button BCb is input by a touch operation, the processor 61 proceeds to ACT162. The processor 61 executes a settlement process of the transaction based on the payment code in ACT162. That is, if the payment code is a code for cash payment, the processor 61 executes a settlement process of the transaction with the cash inserted into the automatic change machine 36. If the payment code is a code for credit card payment, the processor 61 executes a settlement process of the transaction with the credit card data read by the cashless payment terminal 37. If the payment code is a code for electronic money payment, the processor 61 executes a settlement process of the transaction with the electronic money data read by the cashless payment terminal 37. If the payment code is a code for code payment, the processor 61 executes a settlement process of the transaction with the barcode or two-dimensional data code read by the cashless payment terminal 37. Since all of these payment processes are well known, detailed explanations will be omitted.

[0152] When the payment process is complete, the processor 61 proceeds to ACT163. In ACT163, the processor 61 drives the printer 35 to issue a receipt. In ACT164, the processor 61 displays the payment completion screen SCd (see FIG. 35) on the screen of the second touch panel 34. The receipt is a sheet on which are recorded details such as the product name, price, quantity, and amount of the purchased product. The transaction date, time, transaction number, etc. are also recorded on the receipt.

[0153] Fig. 35 is an example of a payment completion screen SCd displayed on the second touch panel 34. Fig. 35 shows the payment completion screen SCd when a cash payment code is obtained by processing ACT155 or ACT156. The payment completion screen SCd includes a change machine information area ACb similar to the payment notification screen SCb and the payment in progress screen SCc. After checking the payment completion screen SCd, the customer takes the receipt and change and leaves the store.

[0154] After displaying the payment completion screen SCd, the processor 61 proceeds to ACT165. The processor 61 saves the data stored in the second transaction file 622 in ACT165, that is, the data of the product purchased by the customer who has completed the payment. The data is saved in, for example, the auxiliary storage device 63. The data may be saved in the main memory 62. Alternatively, the data in the second transaction file 622 may be sent to the POS server via the communication interface 65 and saved in the POS server. The data may be saved in the reservation server 1 instead of the POS server.

[0155] After saving the data of the second transaction file 622, the processor 61 proceeds to ACT166. In ACT166, the processor 61 clears the second transaction file 622. In addition, in ACT167, the processor 61 rewrites the payment in progress flag Fa to “0”. With this, the processor 61 ends the second information processing.

[0156] Here, the processor 61 cooperates with the second touch panel 34 to execute the process of ACT157, thereby realizing the function of first amount output means 302. The processor 61 cooperates with the second touch panel 34 to execute the processes of ACT153 to ACT154, thereby realizing the function of second payment acceptance means 303. The processor 61 cooperates with the second touch panel 34 to execute the process of ACT162, thereby realizing the function of first settlement means 304.

[0157] In this way, when payment in progress flag Fa is "0", and payment button BAe on sub-screen SAb or payment button BAh on payment screen SAd is pressed, causing payment in progress flag Fa to become "1", processor 61 executes the processes of ACT152 to ACT167. By the operation of transaction processing device 3 based on this process, a customer can operate transaction processing device 3 himself to settle the transaction.

[0158] 15 is a flowchart showing the main steps of the third information processing executed by processor 61 of transaction processing device 3 in accordance with the first business program. Processor 61 also executes the third information processing in parallel with the first information processing described above.

[0159] Processor 61 waits for holding flag Fb to become "1" in ACT171. When holding flag Fb becomes "1" in ACT148 of the first information processing, processor 61 proceeds to ACT172. Processor 61 checks whether a release event has been received from holding server 1 in ACT172. If a release event has not been received, processor 61 proceeds to ACT173. Processor 61 checks whether a confirmation event has been received in ACT173. If a confirmation event has not been received, processor 61 returns to ACT172. In this way, processor 61 of transaction processing device 3 whose holding flag Fb has become "1" waits for a release event to be received from holding server 1 that transmitted the holding event, or a confirmation event to be received, in ACT172 and ACT173.

[0160] Here, in order to clarify the release event and the confirmation event, the explanation of FIG. 15 will be temporarily suspended, and the information processing executed by the processor 11 of the reservation server 1 will be explained first with reference to FIGS.

[0161] 16 to 18 are flow charts showing the main steps of the fourth information processing executed by processor 11 of reservation server 1 in accordance with the second business program. Processor 11 waits for a reserved event in ACT201. When processor 11 receives a reserved event via communication interface 15, it proceeds to ACT202. Processor 11 returns an acceptance response in ACT202. That is, processor 11 returns the acceptance response to transaction processing device 3 identified by the transaction processing device ID included in the reserved event.

[0162] As explained using FIG. 13, when processor 61 of transaction processing device 3 that sent the pending event receives the acceptance response, it outputs the data of first transaction file 621 together with the transaction identification information to holding server 1. Then, processor 11 that returned the acceptance response waits for the data of first transaction file 621 as ACT203. When the data of first transaction file 621 is received via communication interface 15, processor 11 proceeds to ACT204. Processor 11 acquires the transaction processing device ID set for transaction processing device 3 that sent the data as ACT204. The transaction processing device ID is included in the pending event. The transaction processing device ID may be included in the data of first transaction file 621.

[0163] Having detected the transaction processing device ID, processor 11 proceeds to ACT 205. In ACT 205, processor 11 obtains the lane number of settlement lane L in which transaction processing device 3, the data source, is installed. Specifically, processor 11 refers to lane table 131 and obtains the lane number described in column Ca of the same row as the transaction processing device ID.

[0164] Having acquired the lane number, processor 11 proceeds to ACT 206. Processor 11 saves the data of first transaction file 621 received from transaction processing device 3 in lane-specific folder 132 identified by the lane number acquired in ACT 206.

[0165] Next, processor 11 acquires the transaction identification information received together with the data of first transaction file 621 as ACT207. Then, processor 11 stores the transaction identification information in transaction identification information memory 626 as ACT208. Processor 11 also refers to lane table 131 as ACT209 to acquire the payment device ID described in column Cc of the same row as the transaction processing device ID. Then, processor 11 transmits a first execution event to the payment device 4 identified by the payment device ID as ACT210. The first execution event is an event that requests the execution of a payment process.

[0166] Details will be explained later using FIG. 20, but upon receiving the first execution event, the payment device 4 returns an approval response or a negative response. The approval response is returned when the payment device 4 is able to settle the transaction. The negative response is returned when the payment device 4 is unable to settle the transaction.

[0167] After sending the first execution event, the processor 11 proceeds to ACT211. In ACT211, the processor 11 checks whether an acceptance response has been received. If an acceptance response has been received, the processor 11 proceeds to ACT221 in FIG. 17. In ACT221, the processor 221 generates a machine-readable code indicating the transaction identification information stored in the transaction identification information memory 626. For example, the processor 11 generates a barcode indicating the transaction identification information. The code system of the barcode is not particularly limited. In short, it is sufficient that the barcode has a code system that can be read by the reading device 9, i.e., that it is a machine-readable code.

[0168] Having generated the machine-readable code, processor 11 proceeds to ACT 222. In ACT 222, processor 11 refers to lane table 131 to obtain the display device ID described in column Cd of the same row as the transaction processing device ID. Then, in ACT 223, processor 11 outputs the read screen data to display device 5 identified by the display device ID.

[0169] In the display device 5 that has received the data of the read screen, the read screen SDa (see FIG. 36) is displayed on the liquid crystal screen of the tablet. 36 is a display example of the read screen SDa. As shown in the figure, the read screen SDa displays a machine-readable code BC created in the process of ACT221. 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 that displays such a read screen SDa realizes the function of a display means 503.

[0170] When the reading screen SDa is displayed on the display device 5, the machine-readable code is read by the reading device 9. The reading device 9 then outputs the data of the read machine-readable code to the payment device 4. Details will be explained later using FIG. 19, but when the machine-readable code of the transaction identification information is read by the reading device 9, the processor 71 of the payment device 4 sends a request event to the holding server 1. The request event is an event that requests the acquisition of information related to the transaction. The request event includes the transaction identification information reproduced from the machine-readable code read by the reading device 9.

[0171] Therefore, the processor 11 of the reservation server 1 that has output the data of the read screen waits for a request event in ACT224. When the processor 11 receives the request event from the payment device 4, the processor 11 proceeds to ACT225. The processor 11 erases the read screen SDa displayed on the display device 5 in ACT225. The processor 11 also acquires transaction identification information from the request event in ACT226. The processor 11 further acquires the payment device ID of the payment device 4 that sent the request event in ACT227. The request event includes the payment device ID set in the payment device 4 that sent the event. Note that the timing for erasing the read screen SDa is not limited to the timing of processing ACT225. It may be any timing after the request event is received from the payment device 4.

[0172] After acquiring the payment device ID, the processor 11 proceeds to ACT228. In ACT228, the processor 11 acquires the lane number of the payment lane L in which 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 acquired in ACT227, and acquires the lane number described in column Ca of the same row as the payment device ID. The payment device ID is included in the request event.

[0173] After acquiring the lane number, the processor 11 proceeds to ACT229. The processor 11 selects a reserved file in ACT229. That is, the processor 11 selects the data of the first transaction file 621 stored in the lane-specific folder 132 of the lane number acquired in ACT228. Then, the processor 11 transmits the reserved file to the payment device 4 in ACT230. That is, the processor 11 transmits the data of the first transaction file 621 acquired in ACT229 to the payment device 4 identified by the payment device ID acquired in the processing of ACT227.

[0174] After sending the hold file, processor 11 proceeds to ACT231. In ACT231, processor 11 sends a release event to transaction processing device 3 which is the data sender of first transaction file 621. That is, processor 11 sends the release event to transaction processing device 3 identified by the transaction processing device ID acquired in the processing of ACT204. The release event is an event that commands that the hold state has been released.

[0175] After transmitting the release event, the processor 11 proceeds to ACT232. The processor 11 clears the reserved file in ACT232. That is, the processor 11 clears the data of the first transaction file 621 saved in the lane-specific folder 132 of the lane number acquired in ACT227. With this, the processor 11 ends the fourth information processing.

[0176] On the other hand, if a negative response is received in ACT211 of FIG. 16, processor 11 proceeds to ACT212. In ACT212, processor 11 sends a confirmation event to transaction processing device 3 which is the data sender of first transaction file 621. That is, processor 11 sends a confirmation event to transaction processing device 3 identified by the transaction processing device ID acquired in the processing of ACT204. The confirmation event is an event that prompts the store clerk to confirm the payment destination. In ACT213, processor 11 also refers to lane table 131 and acquires the display device ID written in column Cd of the same row as the transaction processing device ID. Then, in ACT214, processor 11 outputs instruction screen data to display device 5 identified by that display device ID.

[0177] When the display device 5 receives the data for the instruction screen, the instruction screen SDb (see FIG. 37) is displayed on the liquid crystal screen of the tablet. FIG. 37 is an example of a display of instruction screen SDb. An Import button BDa and a Return button BDb are displayed on instruction screen SDb. 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 output destination of information related to the transaction is the payment device 4. The Return button BDb functions as a second operator that declares that the output destination of information related to the transaction is the transaction processing device 3. Display device 5 that displays such an instruction screen SDb realizes the function of reception means 501.

[0178] The store clerk who has determined the payment destination operates display device 5 based on that determination. Specifically, the store clerk who has determined payment device 4 as the payment destination inputs take-in button BDa. When take-in button BDa is input, a first signal is output from display device 5 to holding server 1. The first signal is a signal that is output in response to the input of take-in button BDa. The first signal is a signal that indicates that payment device 4 has been determined as the payment destination. The store clerk who has determined transaction processing device 3 as the payment destination inputs return button BDb. When return button BDb is input, a second signal is output from display device 5 to holding server 1. The second signal is a signal that is output in response to the input of return button BDb. The second signal is a signal that indicates that transaction processing device 3 has been determined as the payment destination. Display device 5, which outputs such a first signal or second signal, realizes the function of instruction means 502.

[0179] After outputting the data of the instruction screen SDb, the processor 11 proceeds to ACT241 in Fig. 18. The processor 11 checks whether the import button BDa has been pressed in ACT241. If the import button BDa has not been pressed, the processor 11 proceeds to ACT242. The processor 11 checks whether the return button BDb has been pressed in ACT242. If the return button BDb has not been pressed, the processor 11 returns to ACT241. In this way, the processor 11 waits in ACT241 and ACT242 for the import button BDa of the instruction screen SDb to be pressed or the return button BDb to be pressed.

[0180] In the standby state of ACT241 and ACT242, when the processor 11 receives a first signal from the display device 5, the processor 11 recognizes that the capture button BDa has been input. The processor 11 proceeds to ACT243. The processor 11 transmits a second execution event to the payment device 4 in ACT243. Specifically, the processor 11 transmits the second execution event to the payment device 4 identified by the payment device ID acquired in the processing of ACT209. The second execution event is also an event that requests the execution of a payment process.

[0181] Details will be explained later using Fig. 20, but upon receiving the second execution event, the payment device 4 returns an approval response or a negative response. The approval response is returned when the payment device 4 is able to settle the transaction. The negative response is returned when the payment device 4 is unable to settle the transaction.

[0182] After sending the second execution event, the processor 11 proceeds to ACT244. The processor 11 checks whether an acceptance response has been received in ACT244. If an acceptance response has been received, the processor 11 proceeds to ACT245. The processor 11 sends the reserved file to the payment device 4 in ACT245. That is, the processor 11 sends the data of the first transaction file 621 stored in the lane-specific folder 132 of the lane number acquired in ACT205 to the payment device 4 identified by the payment device ID acquired in the processing of ACT209.

[0183] After sending the hold file, processor 11 proceeds to ACT246. In ACT246, processor 11 sends a release event to transaction processing device 3 which is the data sender of first transaction file 621. That is, processor 11 sends the release event to transaction processing device 3 identified by the transaction processing device ID acquired in the processing of ACT204. The release event is an event that commands that the hold state has been released.

[0184] After transmitting the release event, the processor 11 proceeds to ACT247. The processor 11 clears the reserved file in ACT247. That is, the processor 11 clears the data of the first transaction file 621 stored in the lane-specific folder 132 of the lane number acquired in ACT205. The processor 11 also erases the instruction screen SDb that has been displayed on the display device 5 in ACT248. With this, the processor 11 ends the fourth information processing.

[0185] On the other hand, when a second signal is received from display device 5 in the standby state of ACT241 and ACT242, processor 11 recognizes that the back button BDb has been input. Processor 11 proceeds to ACT249. In ACT249, processor 11 transmits a third execution event to transaction processing device 3 which is the data sender of first transaction file 621. That is, processor 11 transmits the third execution event to transaction processing device 3 identified by the transaction processing device ID acquired in the processing of ACT204. The third execution event is also an event that requests the execution of a settlement process.

[0186] Details will be explained later using Figure 15, but upon receiving the third execution event, transaction processing device 3 returns an approval response or a negative response. An approval response is returned if transaction processing device 3 is able to settle the transaction. A negative response is returned if transaction processing device 3 is unable to settle the transaction.

[0187] After sending the third execution event, processor 11 proceeds to ACT250. Processor 11 checks whether an acceptance response has been received in ACT250. If an acceptance response has been received, processor 11 proceeds to ACT251. Processor 11 sends the reserved file to transaction processing device 3 in ACT251. That is, processor 11 sends the data of first transaction file 621 stored in lane specific folder 132 of the lane number acquired in ACT205 to transaction processing device 3 identified by the transaction processing device ID acquired in the processing of ACT204.

[0188] After transmitting the reserved file, the processor 11 proceeds to ACT252. The processor 11 clears the reserved file in ACT252. That is, the processor 11 clears the data of the first transaction file 621 stored in the lane-specific folder 132 of the lane number acquired in ACT205. The processor 11 also erases the instruction screen SDb that was displayed on the display device 5 in ACT253. With this, the processor 11 ends the fourth information processing.

[0189] 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 in ACT254. That is, the processor 11 outputs screen data indicating that an operation on the instruction screen is an error to the display device 5 identified by the display device ID acquired in the processing of ACT213. This screen includes an operator (soft key) for issuing a command to clear the error. Having checked the error screen, the store clerk inputs the operator for issuing a command to clear the error.

[0190] After outputting the data of the error screen, the processor 11 proceeds to ACT255. The processor 11 waits for a command to clear the error in ACT255. When the processor 11 receives from the display device 5 a signal generated by inputting an operator commanding error clear, the processor 11 recognizes that a command to clear the error has been issued. The processor 11 proceeds to ACT256. The processor 11 outputs data of the instruction screen SDb to the display device 5 that commanded error clear in ACT256. That is, the processor 11 outputs data of the instruction screen SDb to the display device 5 identified by the display device ID acquired in the processing of ACT213. Thereafter, the processor 11 returns to the standby state of ACT241 and ACT242.

[0191] For example, a store clerk may input the capture button BDa to designate the payment device 4 as the output destination for transaction-related information, but the previous customer has not yet completed payment at the payment device 4. In such a case, the screen of the display device 5 will become an error screen, and the store clerk will perform an operation to clear the error. Then, the screen of the display device 5 will return to the instruction screen SDb, and the store clerk can wait for the previous customer to complete payment and then input the capture button BDa. Alternatively, if the customer who was making payment at the transaction processing device 3 has already completed payment, the store clerk can input the return button BDb.

[0192] Here, the processor 11 realizes the function of the transaction information input means 102 by executing the processes of ACT201 and ACT203 in cooperation with the communication interface 15. The processor 11 realizes the function of the holding means 103 by executing the processes of ACT204 to ACT206 in cooperation with the lane-specific folder 132. The processor 11 realizes the function of the holding information output means (first holding information output means) 104 by executing the processes of ACT223 to ACT230. The processor 11 realizes the function of the recognition means 101 by executing the processes of ACT241 and ACT242 in cooperation with the communication interface 15. The processor 11 realizes the function of the holding information output means (second holding information output means) 104 by executing the processes of ACT243 to ACT245 and ACT249 to ACT251 in cooperation with the communication interface 15.

[0193] Returning to the explanation of Figure 15. When the processor 61 receives a release event in the standby state of ACT172 and ACT173, the processor 61 proceeds to ACT174. In ACT174, the processor 61 displays a pop-up PUc (see FIG. 38) on the sub-screen SAb or payment screen SAd of the touch panel 23 to guide the customer to make payment at the payment device 4. The processor 61 also displays text TXc (see FIG. 39) on the sub-screen SBb of the display 25 to instruct the customer to pay the price at the payment device 4.

[0194] 38 is 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 patrol lamp 47 is turned on.

[0195] Fig. 39 is an example of the text TXc displayed on the sub-screen SBb of the display 25. After checking the text TXc, the purchaser follows the guidance of the store clerk to the payment device 4 where the patrol lamp 47 is lit, and makes the payment.

[0196] When the process of ACT 174 ends, the processor 61 proceeds to ACT 175. In ACT 175, the processor 61 sets the pending flag Fb to "0." With this, the processor 61 ends the third information process.

[0197] On the other hand, when the processor 61 receives a confirmation event in the standby state of ACT172 and ACT173, the processor 61 proceeds to ACT176. In ACT176, the processor 61 displays a pop-up PUd (see FIG. 40) on the screen of the touch panel 23 to notify the store clerk to specify the payment destination.

[0198] FIG. 40 is an example of a pop-up PUd displayed on registration screen SAa of touch panel 23. The store clerk who has confirmed the pop-up PUd determines the payment destination of the customer whose transaction-related information has been reserved in reservation server 1. Specifically, if another customer is paying at transaction processing device 3, but no customer is paying at payment device 4, the store clerk determines payment device 4 as the payment destination. However, if an abnormality has occurred in payment device 4, such as running out of receipts or insufficient change, the store clerk determines transaction processing device 3 as the payment destination. After determining the payment destination, the store clerk operates display device 5 based on that determination.

[0199] 16, processor 11 of reservation server 1, which has output a confirmation event to transaction processing device 3, outputs data of instruction screen SDb to display device 5. As a result, instruction screen SDb is displayed on display device 5.

[0200] After controlling the display of the pop-up PUd (see FIG. 40) in ACT176, the processor 61 proceeds to ACT177. The processor 61 checks whether or not a release event has been received in ACT177. If a release event has not been received, the processor 61 proceeds to ACT178. The processor 61 checks whether or not a third execution event has been received in ACT178. If a third execution event has not been received, the processor 61 returns to ACT177. In this way, the processor 61 waits for the reception of a release event or the reception of the third execution event in ACT177 and ACT178.

[0201] 18, a release event or a third execution event is transmitted from holding server 1 to transaction processing device 3 that has received the confirmation event. That is, when the Import button BDa is pressed on instruction screen SDb displayed on display device 5 and information related to the held transaction is output to settlement device 4, a release event is transmitted from holding server 1 to transaction processing device 3 as the processing of ACT246. In contrast, when the Return button BDb is pressed on instruction screen SDb and transaction processing device 3 is designated as the output destination of information related to the transaction, a third execution event is returned as the processing of ACT251.

[0202] When the processor 61 receives a release event in the standby state of ACT177 and ACT178, the processor 61 proceeds to ACT174 described above. Thereafter, the processor 61 executes the processes of ACT174 and ACT175 in the same manner as described above. That is, the processor 61 displays a pop-up PUc (see FIG. 38) on the small screen SAb or the 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 a text TXc (see FIG. 39) on the small screen SBb of the display 25 to instruct the customer to pay the price at the payment device 4. After that, the processor 61 sets the pending flag Fb to "0". With the above, the processor 61 ends the third information processing.

[0203] On the other hand, if processor 61 receives a third execution event while in the waiting state of ACT177 and ACT178, processor 61 proceeds to ACT179. In ACT179, processor 61 checks the payment in progress flag Fa. Here, if the payment in progress flag Fa is "1", that is, if the previous customer is making a payment at transaction processing device 3, processor 61 proceeds to ACT180. In ACT180, processor 61 sends a negative response signal to reservation server 1. With this, processor 61 ends the third information processing.

[0204] On the other hand, if the payment in progress flag Fa is "0" in ACT179, that is, if there is no customer making a payment at transaction processing device 3, processor 61 proceeds to ACT181. Processor 61 transmits an approval response signal to reservation server 1 in ACT181.

[0205] As described with reference to FIG. 18, upon receiving the acceptance response from transaction processing device 3 which transmitted the third execution event, reserve server 1 transmits the reserved file (ACT249 to ACT251). Then, processor 61 which transmitted the acceptance response signal waits to receive the reserved file in ACT182. Upon receiving the reserved file via communication interface 65, processor 61 proceeds to ACT183. Processor 61 expands and stores the data of the reserved file in second transaction file 622 in ACT183. Incidentally, the data of the reserved file is the data of first transaction file 621 output to reserve server 1 in ACT148 of FIG. 13.

[0206] After storing the data of the reserved file in second transaction file 622, processor 61 proceeds to ACT184. In ACT184, processor 61 displays a pop-up PUb (see FIG. 30) on sub-screen SAb or payment screen SAd of touch panel 23 to notify that payment is possible at transaction processing device 3. Processor 61 also displays text TXb (see FIG. 31) on sub-screen SBb of display 25 to indicate that payment is possible.

[0207] Having thus notified the user that payment is possible at transaction processing device 3 using touch panel 23 and display 25, processor 61 proceeds to ACT185. In ACT185, processor 61 sets payment in progress flag Fa to "1" and sets pending flag Fb to "0". Thereafter, processor 61 proceeds to ACT152 in Fig. 14. Processor 61 then executes the processes of ACT152 to ACT167 in the same manner as described above.

[0208] When the information on the transaction that was on hold in the hold server 1 is returned to the transaction processing device 3 in this way, the processor 61 of the transaction processing device 3 executes the processes of ACT152 to ACT167 in FIG. 14 in the same manner as described above. That is, the processor 61 changes the screen of the second touch panel 34 to the payment notification screen SCb. If a payment method is not selected on the input device 2, the processor 61 displays the payment method selection screen SCa before the payment notification screen SCb. Then, when a payment method is selected by the customer's operation, the processor 61 displays the payment notification screen SCb. Thereafter, when the payment is started, the processor 61 changes the screen of the second touch panel 34 to the payment in progress screen SCc. The processor 61 also issues a transaction number. Then, when the customer operates 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 changes the screen of the second touch panel 34 to the payment completion screen SCd. In this way, the customer can settle the transaction by operating the transaction processing device 3 himself to pay the price.

[0209] Here, the processor 61 cooperates with the touch panel 23 and the display 25 to execute the processes of ACT174 and ACT184, thereby realizing the function of the guide means 306. The processor 61 executes the processes of ACT183 to ACT185, and further the processes of ACT152 to ACT167, thereby realizing the function of the execution means 307.

[0210] FIG. 19 is a flowchart showing the main steps of the fifth information processing executed by the processor 71 of the settlement device 4 in accordance with the third business program.

[0211] The processor 71 waits for a first execution event in ACT301. As described with reference to FIG. 16, when the information related to the transaction is reserved in the lane-specific folder 132 of the reservation server 1 and the transaction identification information is stored in the transaction identification information memory 626, the first execution event is transmitted from the reservation server 1 to the payment device 4 as processing in ACT210. When the processor 71 receives the first execution event, the processor 71 proceeds to ACT302. The processor 71 checks the payment in progress flag Fc in ACT302. Here, if the payment in progress flag Fc is "1", that is, if the previous customer is still making a payment in the payment device 4, the processor 71 proceeds to ACT303. The processor 71 transmits a negative response signal to the reservation server 1 in ACT303. With the above, the processor 71 ends the fifth information processing.

[0212] On the other hand, if the payment in progress flag Fc is "0" in ACT302, that is, if the customer has not made a payment at the payment device 4, the processor 71 proceeds to ACT304. The processor 61 transmits an approval response signal to the reservation server 1 in ACT304.

[0213] The processor 11 of the reservation server 1 that has received the acceptance response signal executes the process of ACT221 to ACT232 shown in the flow chart of FIG. 17. Thus, the read 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 reading device 9 in ACT305. When the machine-readable code BC is read, the processor 71 proceeds to ACT306. The processor 71 analyzes the data of the machine-readable code BC in ACT306. Then, the processor 71 checks whether the machine-readable code BC of the transaction identification information has been read in ACT307. If a machine-readable code other than the transaction identification information is read, the processor 71 returns to ACT305. The processor 71 waits for the machine-readable code BC to be read by the reading device 9.

[0214] 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 transmits a request event to the reservation server 1 in ACT 308. As described above, the request event is an event that requests the acquisition of information related to the transaction.

[0215] As explained using FIG. 17, upon receiving the request event, the reservation server 1 transmits the reservation file, that is, the data of the first transaction file 621. Then, the processor 71 that transmitted the request event proceeds to ACT309. The processor 71 waits for the reservation file in ACT309. When the reservation file is received via the communication interface 75, the processor 71 proceeds to ACT310. The processor 71 expands and stores the data of the reservation file in the third transaction file 721 in ACT310. Incidentally, the data of the reservation file is the data that was stored in the first transaction file 621 of the transaction processing device 3 installed in the same settlement lane L.

[0216] After storing the data of the reserved file in the third transaction file 721, the processor 71 proceeds to ACT 311. In ACT 311, the processor 71 sets the payment in progress flag Fc to "1." With this, the processor 71 ends the fifth information processing.

[0217] In this way, when the payment in progress flag Fc is "0", i.e., when the customer has not made 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 reservation server 1. In response to this request, the processor 71 retrieves the reserved file data from the reservation server 1, and stores the reserved file data in the third transaction file 721. The processor 71 also sets the payment in progress flag Fc to "1".

[0218] Here, the processor 71 cooperates with the communication interface 75 to execute the processes in ACT305 to ACT310, thereby realizing the function of the acquisition means (first acquisition means) 401.

[0219] 20 is a flowchart showing the main steps of the sixth information processing executed by the processor 71 of the settlement device 4 in accordance with the third business program. The processor 71 also executes the sixth information processing in parallel with the fifth information processing described above.

[0220] The processor 71 waits for the second execution event as ACT321. As described with reference to FIG. 18, when the acquisition button BDa of the instruction screen SDb displayed on the display device 5 is input and the payment device 4 is instructed as the output destination of the information related to the transaction in the state where the information related to the transaction is reserved in the lane-specific folder 132 of the reservation server 1, an execution event is transmitted from the reservation server 1 to the payment device 4 as processing of ACT243. When the processor 71 receives the execution event, it proceeds to ACT322. The processor 71 checks the payment in progress flag Fc as ACT322. Here, if the payment in progress flag Fc is "1", that is, if the previous customer is still making a payment at the payment device 4, the processor 61 proceeds to ACT323. The processor 71 transmits a negative response signal to the reservation server 1 as ACT323. With the above, the processor 71 ends the sixth information processing.

[0221] On the other hand, if the payment in progress flag Fc is "0" in ACT323, that is, if the customer has not made a payment at the payment device 4, the processor 71 proceeds to ACT324. The processor 61 transmits an approval response signal to the reservation server 1 in ACT324.

[0222] As described with reference to FIG. 18, upon receiving the acceptance response from the payment device 4 that transmitted the second execution event, the reservation server 1 transmits the reserved file to that payment device 4. Then, processor 71, which transmitted the acceptance response signal, waits to receive the reserved file as ACT325. Upon receiving the reserved file via communication interface 75, processor 71 proceeds to ACT326. Processor 71 expands and stores the data of the reserved file in third transaction file 721 as ACT326. Incidentally, the data of the reserved file is data that was stored in first transaction file 621 of transaction processing device 3 installed in the same settlement lane L.

[0223] After storing the data of the reserved file in the third transaction file 721, the processor 71 proceeds to ACT 327. In ACT 327, the processor 71 sets the payment in progress flag Fc to "1." With this, the processor 71 ends the sixth information processing.

[0224] In this way, when processor 71 of settlement device 4 receives the second execution event from reservation server 1 while payment in progress flag Fc is "0", i.e., while the customer has not yet made a payment, processor 71 imports the data of the reservation file output thereafter from reservation server 1 and stores it in third transaction file 721. Processor 71 also sets payment in progress flag Fc to "1".

[0225] Here, the processor 71 cooperates with the communication interface 75 to execute the processes of ACT325 and ACT326, thereby realizing the function of the capture means (second capture means) 401.

[0226] 21 is a flowchart showing the main steps of the seventh information processing executed by the processor 71 of the settlement device 4 according to the third business program. The processor 71 executes the seventh information processing in parallel with the fifth and sixth information processing described above.

[0227] The processor 71 waits for the payment in progress flag Fc to become "1" in ACT331. When the payment in progress flag Fc becomes "1" in ACT311 of the fifth information processing or ACT327 of the sixth information processing, the processor 71 proceeds to ACT332. The processor 71 changes the screen of the touch panel 42 to the statement confirmation screen SEa (see FIG. 41) in ACT332. The processor 71 also turns on the patrol lamp 47.

[0228] FIG. 41 is an example of a statement confirmation screen SEa displayed on the touch panel 42. The statement confirmation screen SEa is divided into a statement area AEa and a total area AEb. The statement area AEa is an area that displays in list form, in sequential numerical order, the product name, purchase quantity, unit price, discount amount, and sales amount of the purchased products in one transaction. The total area AEb is an area that displays the total purchase quantity and total sales amount of the purchased products in one transaction. Based on the product sales data stored in the third transaction file 721, the processor 71 causes the statement area AEa to display the product name, purchase quantity, unit price, discount amount, and sales amount of the purchased products in one transaction. Based on the product sales data stored in the third transaction file 721, the processor 71 causes the total area AEb to display the total purchase quantity and total sales amount of the purchased products in one transaction.

[0229] The statement confirmation screen SEa includes a confirmation button BEa and a store clerk call button BEb. The confirmation button BEa and the store clerk call button BEb are software keys. The confirmation button BEa is an operator for the customer to instruct that he / she has confirmed that the details of the purchased item are displayed on the statement confirmation screen SEa. The store clerk call button BEb is an operator for the customer to instruct to call a store clerk.

[0230] After displaying the statement confirmation screen SEa, the processor 71 proceeds to ACT333. The processor 71 waits for the confirmation button BEa to be input in ACT333. When the store clerk call button BEb is input in this standby state, the processor 71 performs a store clerk calling operation. For example, the processor 71 blinks the patrol lamp 47. Thereafter, when the called store clerk performs an operation to end the call, the processor 71 returns to the standby state in ACT333.

[0231] When the confirmation button BEa is input in the standby state of ACT333, the processor 71 proceeds to ACT334. The processor 71 confirms whether or not a payment code is included in the data stored in the third transaction file 721 in ACT334. If a payment code is included, the processor 71 proceeds to ACT335. The processor 71 extracts the payment code from the third transaction file 721 in ACT335.

[0232] On the other hand, if the payment code is not included, the processor 71 proceeds to ACT 336. In ACT 336, the processor 71 displays the screen of the touch panel 42 as the payment method selection screen SEb (see FIG. 42).

[0233] FIG. 42 is an example of a payment method selection screen SEb displayed on the touch panel 42. The payment method selection screen SEb includes a selection button group BEc for each payment method. The selection button group BEc includes a cash button, a credit button, an electronic money button, and a code payment button. However, no button is provided for payment with a gift certificate or other voucher. The payment method selection screen SEb includes a total area AEc in which the total purchase quantity and the total sales amount of the purchased items in one transaction are displayed. The total area AEc displays the total purchase quantity and the total sales amount calculated based on the product sales data of the purchased items stored in the third transaction file 721. The payment method selection screen SEb also displays a store clerk call button BEb, allowing the customer to call a store clerk.

[0234] After checking the payment method selection screen SEb, the customer touches the button for the desired payment method. For example, a customer who wishes to pay by cash touches the CASH button in selection button group BEc. For example, a customer who wishes to pay by credit card touches the CREDIT button in selection button group BEc. For example, a customer who wishes to pay by electronic money touches the ELECTRONIC MONEY button in selection button group BEc. For example, a customer who wishes to pay by code payment touches the code payment button in selection button group BEc.

[0235] Having set the screen of the touch panel 42 to the payment method selection screen SEb, the processor 71 proceeds to ACT337. The processor 71 waits for a payment method to be selected in ACT337. When any payment method is selected by a touch operation on the selection button group BEc, the processor 71 proceeds to ACT338. In ACT338, the processor 71 acquires the payment code of the selected payment method, similar to the processing in ACT123 of the first information processing.

[0236] After completing the process of ACT335 or ACT338, the processor 71 proceeds to ACT339. In ACT339, the processor 71 displays the payment notification screen SEc (see FIG. 43) on the screen of the touch panel 42. The payment notification screen SEc is a screen based on the payment code obtained by the process of ACT335 or ACT339.

[0237] FIG. 43 is an example of the payment notification screen SEc displayed on the touch panel 42. FIG. 43 shows the payment notification screen SEc when a payment code for cash payment is obtained by processing ACT335 or ACT338. The payment notification screen SEc includes a total area AEc similar to the payment method selection screen SEb. The payment notification screen SEc also includes a change machine information area AEd. The change machine information area AEd displays the total amount, the total amount of cash inserted into the automatic change machine 78 (the so-called inserted amount), and the remaining amount obtained by subtracting the inserted amount from the total amount. Note that the store clerk call button BEb is also displayed on the payment notification screen, allowing the customer to call a store clerk.

[0238] After checking the payment notification screen SEc, the customer pays the amount using the payment method of their choice. For example, a customer who selects cash payment inserts cash into the automatic change machine 78. A customer who selects credit card payment has the credit card data read by the reader of the cashless payment terminal 79. A customer who selects electronic money payment has the data on the electronic money medium read by the reader of the cashless payment terminal 79. A customer who selects code payment has the barcode or two-dimensional data code for code payment read by the scanner of the cashless payment terminal 79.

[0239] The processor 71, having changed the screen of the touch panel 42 to the payment notification screen SEc, proceeds to ACT340. The processor 71 waits for the start of payment in ACT340. For example, if cash payment is selected, the processor 71 waits for cash to be inserted into the automatic change machine 78. For example, if credit card payment is selected, the processor 71 waits for 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 electronic money data to be read by the cashless payment terminal 79. For example, if code payment is selected, the processor 71 waits for a barcode or two-dimensional data code for code payment to be read by the cashless payment terminal 79.

[0240] When payment of the price is started, the processor 71 proceeds to ACT341. The processor 71 issues a transaction number in ACT341. The transaction number is, for example, a seven-digit number consisting of a three-digit payment device ID and a four-digit serial number. The serial number is incremented by "1" each time a transaction is settled in the payment device 4. After issuing the transaction number, the processor 71 proceeds to ACT342. In ACT342, the processor 71 displays the payment in progress screen SEd (see FIG. 44) on the screen of the touch panel 42.

[0241] FIG. 44 is an example of the payment in progress screen SEd displayed on the touch panel 42. FIG. 44 shows the payment in progress screen SEd when a payment code for cash payment is obtained by processing ACT335 or ACT338. The payment in progress screen SEd is a screen in which a checkout button BEd is added to the payment notification screen SCb. On the payment in progress screen SCc, the information displayed in the change machine information area AEd is updated according to the amount of cash inserted into the automatic change machine 78. The checkout button BEd is a software key. The checkout button BEd is an operator for instructing the completion of payment. When a customer has finished paying the price using the selected payment method, he or she touches the checkout button BEd. Note that the store clerk call button BEb continues to be displayed on the payment in progress screen SEd, allowing the customer to call a store clerk.

[0242] The processor 71, which has changed the screen of the touch panel 42 to the payment in progress screen SEd, proceeds to ACT343. The processor 71 waits for the checkout button BEd to be input in ACT343. When the checkout button BEd is input by a touch operation, the processor 71 proceeds to ACT344. The processor 71 executes the settlement process of the transaction based on the payment code in ACT344. That is, if the payment code is a code for cash payment, the processor 71 executes the settlement process of the transaction with the cash inserted into the automatic change machine 78. If the payment code is a code for credit card payment, the processor 71 executes the settlement process of the transaction with the credit card data read by the cashless payment terminal 79. If the payment code is a code for electronic money payment, the processor 71 executes the settlement process of the transaction with the electronic money data read by the cashless payment terminal 89. If the payment code is a code for code payment, the processor 71 executes the settlement process of the transaction with the barcode or two-dimensional data code read by the cashless payment terminal 79. Since all of these payment processes are well known, detailed explanations will be omitted.

[0243] Upon completing the payment process, processor 71 proceeds to ACT345. In ACT345, processor 71 drives printer 87 to issue a receipt. In ACT346, processor 71 causes touch panel 42 to display payment completion screen SEe (see FIG. 45). The receipt is the same as the receipt issued by transaction processing device 3 in the processing of ACT163. However, while a transaction number including the transaction processing device ID is printed on a receipt issued by transaction processing device 3, a transaction number including the payment device ID is printed on a receipt issued by payment device 4.

[0244] FIG. 45 is an example of the payment completion screen SEe displayed on the touch panel 42. FIG. 45 shows the payment completion screen SEe when a payment code for cash payment is obtained by processing ACT335 or ACT338. The payment completion screen SEe includes a change machine information area AEd similar to the payment notification screen SEc and the payment in progress screen SEd. The store clerk can know that the payment of a customer who selected cash payment has been completed from the information displayed in the change machine information area AEd. Note that a customer who has completed payment does not call a store clerk, so the store clerk call button BEb is not displayed on the payment completion screen SEe. After checking the payment completion screen SEe, the customer takes the receipt and leaves the store.

[0245] After displaying the payment completion screen SEe, the processor 71 proceeds to ACT347. The processor 71 saves the data stored in the third transaction file 721 in ACT347, that is, the data of the product purchased by the customer who has completed the payment. The data is saved in, for example, the auxiliary storage device 73. The data may also be saved in the main memory 72. Alternatively, the data in the third transaction file 721 may be sent to the POS server via the communication interface 75 and saved in the POS server. The data may also be saved in the reservation server 1 instead of the POS server.

[0246] After saving the data of the third transaction file 721, the processor 71 proceeds to ACT348. The processor 71 clears the third transaction file 721 in ACT348. The processor 71 also sets the payment in progress flag Fc to "0" in ACT349. The processor 71 also turns off the patrol lamp 47. With this, the processor 71 ends the seventh information processing.

[0247] In this way, when the information on the transaction that was reserved in the reservation server 1 is imported into the settlement device 4, the processor 71 of the settlement device 4 executes the process of ACT332 to ACT349 in FIG. 21. That is, the processor 71 changes the screen of the touch panel 42 to the statement confirmation screen SEa. Then, when the customer operates to input the confirmation button BEa, the processor 71 changes the screen of the touch panel 42 to the payment notification screen SEc. If a payment method is not selected on the input device 2, the processor 71 displays the payment method selection screen SEb before the payment notification screen SEc. Then, when the customer operates to select a payment method, the processor 71 changes the screen of the touch panel 42 to the payment notification screen SEc. Thereafter, when the payment is started, the processor 71 changes the screen of the touch panel 42 to the payment in progress screen SEd. The processor 71 also issues a transaction number. Then, when the customer operates to input the checkout button BEd on the payment in progress screen SEd, the processor 71 executes the settlement process and issues a receipt. Furthermore, the processor 71 displays the payment completion screen SEe on the screen of the touch panel 42. In this way, the customer can settle the transaction by operating the settlement device 4 himself / herself to pay the price.

[0248] Here, the processor 71 cooperates with the touch panel 42 to execute the process of ACT336, thereby realizing the function of third payment acceptance means 403. The processor 71 cooperates with the touch panel 42 to execute the process of ACT339, thereby realizing the function of second amount output means 402. The processor 71 cooperates with the touch panel 42 to execute the process of ACT344, thereby realizing the function of second settlement means 404.

[0249] [Product sales system function] Next, the operation of the settlement system 100 that operates as described above will be described. First, assume that the customer has not yet made payment at transaction processing device 3 and settlement device 4. In this state, when the registration of the product to be purchased by the first customer is completed and payment button BAe on sub-screen SAb or payment button BAh on payment screen SAd is pressed, a pop-up PUb (see FIG. 30) is displayed on sub-screen SAb or payment screen SAd of touch panel 23 to inform that payment at transaction processing device 3 is possible. Also, text TXb (see FIG. 31) is displayed on sub-screen SBb of display 25 to indicate that payment is possible. Then, payment in progress flag Fa becomes "1". Thus, the first customer operates transaction processing device 3 himself to settle the transaction.

[0250] Next, assume that the registration of the product to be purchased by the second customer is completed and the payment button BAe or the payment button BAh is pressed. If the first customer operating transaction processing device 3 has not yet completed payment, information related to the second customer's transaction together with transaction identification information that identifies the transaction is sent to reservation server 1 and reserved. That is, the information related to the transaction is stored in lane-specific folder 132 for the payment lane L for which product registration has been completed. Then, the reservation flag Fb becomes "1".

[0251] Holding server 1, which has held the transaction-related information transmitted from transaction processing device 3, transmits a first execution event to payment device 4 installed in the same payment lane L as transaction processing device 3. At this time, if payment in progress flag Fc of payment device 4 is "0", i.e., if there is no customer operating payment device 4 to make a payment, holding server 1 generates a machine-readable code BC indicating transaction identification information, and displays it on display device 5 in the same payment lane L. When the machine-readable code BC is displayed on display device 5, reader 9 reads the machine-readable code BC.

[0252] The payment device 4 captures the machine-readable code BC read by the reader 9. Then, when the machine-readable code BC of the transaction identification information is read by the reader 9, a request event is sent to the reservation server 1. In response to this request event, information related to the transaction of the second customer is sent from the reservation server 1 to the payment device 4. Also, the reservation flag Fb becomes "0". Thus, the second customer operates the payment device 4 by himself to settle the transaction.

[0253] On the other hand, when the holding server 1 sends the first execution event to the payment device 4, if the payment in progress flag Fc of the payment device 4 is “1”, i.e., if there is a customer operating the payment device 4 to make a payment, the instruction screen SDb (see Figure 37) is displayed on the display device 5.

[0254] The clerk then determines the output destination of the information related to the transaction reserved in the reservation server 1. The clerk waits for the transaction processing device 3 or the settlement device 4 to become available, and then inputs the take-in button BDa or the return button BDb. That is, if the settlement device 4 becomes available first, the clerk inputs the take-in button BDa. With this input, the information related to the transaction of the second customer is taken into the settlement device 4. Then, a pop-up PUc (see FIG. 38) is displayed on the small display area SAb or the payment screen SAd of the touch panel 23 to guide the customer to make a payment at the settlement device 4. Also, a text TXc (see FIG. 39) is displayed on the small display area SBb of the display 25 to instruct the customer to pay the price at the settlement device 4. Also, the reservation flag Fb becomes "0". Thus, the second customer operates the settlement device 4 by himself to settle the transaction.

[0255] On the other hand, if transaction processing device 3 becomes available first, the store clerk inputs return button BDb. With this input, information related to the second customer's transaction is returned to transaction processing device 3. Then, a pop-up PUb (see FIG. 30) is displayed on small screen SAb or payment screen SAd of touch panel 23, notifying that payment at transaction processing device 3 is possible. In addition, text TXb (see FIG. 31) is displayed on small screen SBb of display 25 to indicate that payment is possible. In addition, pending flag Fb becomes "0". Thus, the second customer operates transaction processing device 3 himself to settle the transaction.

[0256] Meanwhile, when the information on the transaction of the second customer is reserved in the reservation server 1, that is, when the reservation flag Fb is "1", the registration of the product to be purchased by the third customer is completed and the payment button BAe or the payment button BAh is input, a pop-up PUa (see FIG. 28) is displayed on the small display area SAb or the payment screen SAd of the touch panel 23 to inform the customer that the payment is impossible. Also, a text TXa (see FIG. 29) is displayed on the small display area SBb of the display 25 to instruct the customer to wait because the payment is impossible. Therefore, the third customer waits. Then, when the transaction processing device 3 or the settlement device 4 becomes available, the store clerk inputs the take-in button BDa or the return button BDb. Thus, the third customer operates the transaction processing device 3 or the settlement device 4 by himself to settle the transaction.

[0257] As described above in detail, this embodiment can provide payment system 100 that allows customers to efficiently perform operations related to payment by appropriately selecting transaction processing device 3 and payment device 4. This can reduce labor costs. In addition, this can be an effective measure against infectious diseases.

[0258] More specifically, in this embodiment, at the time when information relating to a transaction is reserved in the reservation server 1, a machine-readable code BC indicating transaction identification information that identifies the transaction is displayed on the display device 5. The machine-readable code BC displayed on the display device 5 is then automatically read by the reading device 9. When the machine-readable code BC is read by the reading device 9, the payment device 4 analyzes the machine-readable code BC. The payment device 4 then retrieves information relating to the transaction identified by the transaction identification information indicated by the machine-readable code BC from the reservation server 1. Having retrieved the information relating to the transaction, the payment device 4 becomes able to settle the transaction. Thus, the customer can operate the payment device 4 to make payment for the price.

[0259] However, when the settlement of the transaction is in progress at the settlement device 4, the settlement device 4 does not capture the machine-readable code being read by the reading device 9. In that case, an instruction screen SDb is displayed on the display device 5. With a one-touch operation on the instruction screen SDb, the store clerk can easily select whether the output destination of the information related to the transaction held in the holding server 1 is to the settlement device 4 or the transaction processing device 3.

[0260] The reading device 9 does not have to be connected to the payment device 4 by a transmission cable. For example, the reading device 9 is connected to the communication network 6, and the reservation server 1 analyzes the machine-readable code read by the reading device 9 to recognize the transaction identification information. The reservation server 1 may then transmit information related to the transaction identified by the transaction identification information to the payment device 4.

[0261] The transaction information is not limited to information on the purchased product, such as product sales data. The transaction information may be any information that can be processed to calculate the amount required for settlement. For example, the transaction information may be only the product code and sales quantity of the purchased product.

[0262] In the reservation server 1, the storage area for reserving transaction-related information is not limited to the lane-specific folder 132. As long as it is possible to identify which settlement lane L the reserved file is from, it may be a single data folder that reserves the reserved files in chronological order.

[0263] [Second embodiment] In the above-mentioned first embodiment, there is no mention of returning the transaction-related information captured by the payment device 4 to the reservation server 1. However, if the transaction-related information is captured 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 cannot operate the payment device 4 to settle the transaction. In addition, for payment methods that require confirmation by a store clerk, such as gift certificates, self-payment is prohibited. Therefore, assuming such an event, a second embodiment in which a process of returning the transaction-related information captured by the payment device 4 to the reservation server 1 is added will be described with reference to Figs. 46 and 47. Note that the configuration of the payment system 100 in the second embodiment is the same as that in the first embodiment, and therefore a description thereof will be omitted here.

[0264] For example, if a customer attempts to start a payment using the payment device 4 but an abnormality occurs in the payment device 4, the customer will input the clerk call button BEb on the statement confirmation screen SEa to call a clerk. Alternatively, if the customer does not have a desired payment method on the payment method selection screen SEb, the customer will input the clerk call button BEb on the payment method selection screen SEb to call a clerk. In the second embodiment, when the clerk call button BEb is input, the processor 71 of the payment device 4 starts information processing according to the procedure shown in the flowchart of FIG.

[0265] 46 is a flowchart showing the main steps of the eighth information processing executed by the processor 71 according to the third business program. The processor 71 executes the eighth information processing in parallel with the fifth to seventh information processing described above.

[0266] The processor 71 waits for the clerk call button BEb to be pressed as ACT341. When the clerk call button BEb on the statement confirmation screen SEa or the payment method selection screen SEb is pressed, the processor 71 proceeds to ACT342. The processor 71 transmits a call event to the reservation server 1 as ACT342. The call event is an event for notifying the reservation server 1 that the clerk call button BEb has been pressed. The call event includes the payment device ID of the payment device 4.

[0267] Although details will be described later, upon receiving the call event, the reservation server 1 returns a continuation event or a payment cancellation event. Then, the processor 71 that sent the call event proceeds to ACT343. The processor 71 checks whether or not a continuation event has been received in ACT343. If a continuation event has not been received, the processor 71 proceeds to ACT344. The processor 71 checks whether or not a payment cancellation event has been received in ACT344. If a payment cancellation event has not been received, the processor 71 returns to ACT333. In this way, the processor 71 waits in ACT343 and ACT344 to receive a continuation event or a payment cancellation event. In this standby state, an image such as "Calling" is displayed on the touch panel 42.

[0268] When a continuation event is received in the standby state of ACT343 and ACT344, the processor 71 ends the eighth information processing.

[0269] On the other hand, if a settlement cancellation event is received in the standby state of ACT343 and ACT344, the processor 71 proceeds to ACT345. The processor 71 clears the third transaction file 721 in ACT345. The processor 71 also rewrites the payment in progress flag Fc to "0" in ACT346. With this, the processor 71 ends the eighth information processing.

[0270] In this way, when the processor 71 of the payment device 4 receives a continuation event for the call event, the processor 71 ends the eighth information processing. In this case, the processor 71 continues the seventh information processing from the processing step immediately before the store clerk call button BEb is input.

[0271] When a payment cancellation event is received in response to the call event, processor 71 clears third transaction file 721. Also, processor 71 sets payment in progress flag Fc to "0." Therefore, processor 61 ends the seventh information processing at the time when clerk call button BEb is input, and starts processing from the fifth information processing.

[0272] 47 is a flow chart showing a ninth main procedure executed by the processor 11 of the reservation server 1 in accordance with the second business program. The processor 11 executes the ninth information processing in parallel with the above-mentioned fourth information processing.

[0273] The processor 71 waits for a call event in ACT271. When the processor 11 receives the call event from the payment device 4, the processor 11 proceeds to ACT272. The processor 11 acquires the payment device ID from the call event in ACT272. The processor 11 acquires the lane number of the payment lane L in which the payment device 4 that is the data sender is installed in ACT273. Specifically, the processor 11 refers to the lane table 131 and acquires the lane number described in column Ca of the same row as the payment device ID.

[0274] After acquiring the lane number, the processor 11 proceeds to ACT274. In ACT274, the processor 11 refers to the lane table 131 and acquires the display device ID described in column Cd of the same row as the payment device ID. Then, in ACT275, the processor 11 outputs data of a confirmation screen to the display device 5 identified by the display device ID.

[0275] When the display device 5 receives the data for the confirmation screen, the confirmation screen SDc (see FIG. 48) is displayed on the liquid crystal screen of the tablet. FIG. 48 is an example of a display of the confirmation screen SDc. A re-hold button BDc and a continue button BDd are displayed on the confirmation screen SDc. 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 that the information related to the transaction output to the payment device 4 is accepted to be returned to the holding server 1. The continue button BDd functions as a fourth operator that declares that the payment at the payment device 4 will be continued without returning the information related to the transaction output to the payment device 4 to the holding server 1.

[0276] The store clerk, having checked the confirmation screen SDc, realizes that he has been called by a customer who was operating the payment device 4 by himself. The store clerk goes to the location of the payment device 4 to confirm the reason for the call. For example, if the customer is out of receipts or short of change and receipt paper or change can be replenished immediately, the store clerk presses the continue button BDd. The store clerk then replenishes receipt paper or change in the payment device 4. On the other hand, if receipt paper or change cannot be replenished immediately or if the customer requests a payment method that requires confirmation by the store clerk, such as a gift certificate, the store clerk presses the re-hold button BDc.

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

[0278] After outputting the data of the confirmation screen SDc, the processor 11 proceeds to ACT276. The processor 11 checks whether the re-hold button BDc has been pressed in ACT276. If the re-hold button BDc has not been pressed, the processor 11 proceeds to ACT277. The processor 11 checks whether the continue button BDd has been pressed in ACT277. If the continue button BDd has not been pressed, the processor 11 returns to ACT276. In this way, the processor 11 waits in ACT276 and ACT277 for the re-hold button BDc on the confirmation screen SDc to be pressed or for the continue button BDd to be pressed.

[0279] When the processor 11 receives a fourth signal from the display device 5 in the standby state of ACT276 and ACT277, the processor 11 recognizes that the continue button BDd has been input. The processor 11 proceeds to ACT278. The processor 11 transmits a continue event to the payment device 4 that transmitted the call event in ACT278. The continue event is an event for instructing the payment device 4 to continue the transaction. After transmitting the continue event, the processor 11 proceeds to ACT279. The processor 11 erases the confirmation screen SDc that was displayed on the display device 5 in ACT279. With this, the processor 11 ends the ninth information processing.

[0280] In the standby state of ACT276 and ACT277, when the processor 11 receives a third signal from the display device 5, the processor 11 recognizes that the re-hold button BDc has been input. The processor 11 proceeds to ACT280. The processor 11 imports data of the third transaction file 721 from the settlement device 4 in ACT280. The data of the third transaction file 721 is data of the reserved file output by the reservation server 1 to the settlement device 4. That is, the data stored by the processor 11 in the lane-specific folder 132 in ACT206 of the fourth information processing described with reference to FIG. 16, that is, the data of the first transaction file 621 received from the transaction processing device 3.

[0281] The processor 11 again reserves the data of the third transaction file 721 acquired from the settlement device 4 in ACT281. Specifically, the processor 11 stores the data of the third transaction file 721 in the lane-specific folder 132 of the lane number acquired in the processing of ACT273.

[0282] After reserving the data of the third transaction file 721, the processor 11 proceeds to ACT282. In ACT282, the processor 11 transmits a payment cancellation event to the payment device 4 that transmitted the call event. The payment cancellation event is an event that commands the payment device 4 to cancel the payment.

[0283] The processor 11, which has transmitted the payment cancellation event, proceeds to ACT283. The processor 11 outputs data of an instruction screen to the display device 5 in ACT283. That is, the processor 11 outputs data of an instruction screen to the display device 5 identified by the display device ID acquired in the processing of ACT274. As a result, the display device 5 that has received the data of the instruction screen displays the instruction screen SDb (see FIG. 37) on the liquid crystal screen of the tablet.

[0284] Thereafter, the processor 11 executes the processes from ACT241 to ACT256 of the fourth information processing described with reference to FIG. 18 in the same manner as described above.

[0285] Thus, in the second embodiment, when the customer operating the payment device 4 presses the store clerk call button BEb, a confirmation screen SDc is displayed on the display device 5. If the store clerk presses the continue button BDd here, the data stored in the third transaction file 721 of the payment device 4 remains as is. The customer can continue to operate the payment device 4 and settle the transaction by himself.

[0286] On the other hand, if the store clerk presses the re-hold button BDc, the data stored in the third transaction file 721 is again held in the holding server 1. Then, the screen of the display device 5 becomes the instruction screen SDb. If the store clerk presses the return button BDb here, the re-held data is sent to the transaction processing device 3. In this way, the customer can settle the transaction by operating the transaction processing device 3. At this time, if the customer wishes to pay with, for example, a gift certificate, he or she can simply ask the store clerk in the space SP for confirmation.

[0287] As described above in detail, according to the second embodiment, the information relating to the transaction captured by the payment device 4 can be returned to the reservation server 1 and reserved again by a store clerk's operation on the display device 5. The information relating to the transaction that has been reserved again can then be output to the transaction processing device 3 or the payment device 4 by a store clerk's operation on the display device 5. Therefore, for example, if an abnormality occurs in the payment device 4 and a customer who is attempting to operate the payment device 4 is unable to settle the transaction, the output destination of the information relating to the customer's transaction can be changed to the transaction processing device 3 by a simple operation on the display device 5.

[0288] [Third embodiment] Next, a third embodiment will be described with reference to FIGS. In the first embodiment, the payment device 4 captures the machine-readable code BC read by the reader 9 when the payment in progress flag Fc is "0", i.e., when the customer is not making a payment. In the third embodiment, the payment device 4 captures the machine-readable code BC read by the reader 9 regardless of the payment in progress flag Fc.

[0289] Figures 49 and 50 are flow charts showing the main steps of the tenth information processing executed by the processor 11 of the reservation server 1 in accordance with the second business program in the third embodiment. The tenth information processing is a modification of the fourth information processing explained in the first embodiment with reference to Figures 16 to 18. Therefore, the same reference numerals are used for the processing steps common to Figures 16 to 18.

[0290] In Fig. 49, processor 11 waits for a pending event as ACT201. When processor 11 receives a pending event via communication interface 15, processor 11 similarly executes the processes of ACT202 to ACT208 described with reference to Fig. 16. That is, processor 11 returns an acceptance response. That is, processor 11 returns an acceptance response to transaction processing device 3 that has transmitted the pending event, and accordingly saves data of first transaction file 621 output from transaction processing device 3 in lane-specific folder 132. Processor 11 also stores the transaction identification information received together with the data of first transaction file 621 in transaction identification information memory 626.

[0291] Then, processor 11 proceeds to ACT221 in Fig. 50. Processor 11 similarly executes the processes of ACT221 to ACT223 described with reference to Fig. 17. That is, processor 11 generates a machine-readable code indicating the transaction identification information stored in transaction identification information memory 626. Processor 11 also refers to lane table 131 to obtain the display device ID described in column Cd of the same row as the transaction processing device ID. Processor 11 then outputs the data of the read screen to display device 5 identified by that display device ID.

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

[0293] 51 is a flow chart showing the main procedure of the eleventh information processing executed by the processor 71 of the settlement device 4 according to the third business program in the third embodiment. That is, in the third embodiment, the processor 71 waits for the machine-readable code BC to be read in ACT351. When the machine-readable code BC is read, the processor 71 proceeds to ACT352. The processor 71 analyzes the data of the machine-readable code BC in ACT352. Then, the processor 71 checks whether the machine-readable code BC of the transaction identification information has been read in ACT353. When a machine-readable code other than the transaction identification information is read, the processor 71 ends the eleventh information processing.

[0294] When the machine-readable code of the transaction identification information is read by the reader 9, the processor 71 proceeds to ACT354. The processor 71 checks the payment in progress flag Fc in ACT354. If the payment in progress flag Fc is "0", that is, if the customer has not made a payment at the payment device 4, the processor 71 proceeds to ACT352. The processor 61 sends a request event to the reservation server 1 in ACT352. The request event is an event that requests the acquisition of information related to the transaction.

[0295] After sending the request event, processor 71 proceeds to ACT356. In ACT356, processor 71 waits for a reserved file. When processor 71 receives the reserved file via communication interface 75, processor 71 proceeds to ACT357. In ACT357, processor 71 expands and stores the data of the reserved file in third transaction file 721. Incidentally, the data of the reserved file is data that was stored in first transaction file 621 of transaction processing device 3 installed in the same settlement lane L.

[0296] After storing the data of the reserved file in the third transaction file 721, the processor 71 proceeds to ACT 358. In ACT 358, the processor 71 sets the payment in progress flag Fc to "1." With this, the processor 71 ends the eleventh information processing.

[0297] On the other hand, if the payment in progress flag Fc is "1" in ACT354, that is, if the customer is making a payment at the payment device 4, the processor 71 proceeds to ACT359. The processor 71 transmits an impossible event to the reservation server 1 in ACT359. The impossible event is an event that notifies that it is impossible to retrieve information related to the transaction. With this, the processor 71 ends the eleventh information processing.

[0298] In this way, when the reader 9 reads the machine-readable code BC of the transaction identification information, the payment device 4 judges whether or not the payment of the transaction is being processed. If the payment is not being processed, the payment device 4 sends a request command to the reservation server 1. On the other hand, if the payment is being processed, the payment device 4 sends a disallowed command to the reservation server 1.

[0299] Return to the explanation of Figure 50. In ACT223, the processor 11 of the reservation server 1 that has output the data of the read screen proceeds to ACT290. The processor 11 checks whether or not a request event has been received in ACT290. If a request event has not been received, the processor 11 proceeds to ACT291. The processor 11 checks whether or not a non-required event has been received in ACT291. If a non-required event has not been received, the processor 11 returns to ACT290. In this way, the processor 11 waits to receive a request event or a non-required event.

[0300] When a request event is received in the standby state of ACT290 and ACT291, processor 11 proceeds to ACT225. Processor 11 executes the processes of ACT225 to ACT231 in the same manner as described above. That is, processor 11 erases the read screen SDa displayed on display device 5. Processor 11 also acquires transaction identification information from the request event. Processor 11 also acquires the payment device ID of the payment device 4 that transmitted the request event, and acquires the lane number of the payment lane L in which the payment device 4 identified by the payment device ID is installed. Processor 11 selects the data of first transaction file 621 stored in lane-specific folder 132 of the acquired lane number, and transmits the data of first transaction file 621 to payment device 4 identified by the payment device ID. Processor 11 also transmits a release event to transaction processing device 3 that is the data transmission source of first transaction file 621. Processor 11 then clears the reserved file and ends the tenth information processing.

[0301] On the other hand, when a disabling event is received in the standby state of ACT290 and ACT291, processor 11 proceeds to ACT212. Processor 11 executes the process of ACT212 to ACT214 in the same manner as described above. That is, processor 11 transmits a confirmation event to transaction processing device 3 which is the data transmission source of first transaction file 621. Processor 11 also refers to lane table 131 to obtain the display device ID described in column Cd of the same row as the transaction processing device ID. Then, processor 11 outputs data of the instruction screen to display device 5 identified by the display device ID. Thus, in display device 5 which has received the data of the instruction screen, instruction screen SDb (see FIG. 37) is displayed on the liquid crystal screen of the tablet, and thereafter, processor 11 executes the process of ACT241 to ACT256 of the fourth information processing described with reference to FIG. 18 in the same manner as described above.

[0302] Even in the third embodiment that operates in this manner, it is possible to provide a payment system 100 that allows a customer to efficiently perform operations related to payment by appropriately selecting transaction processing device 3 and payment device 4.

[0303] [Fourth embodiment] FIG. 52 is a block diagram showing a schematic configuration of a payment system 200 according to a fourth embodiment. In the first embodiment, a payment system 100 including an input device 2, a transaction processing device 3, a payment device 4, a display device 5, and a reading device 9 for each payment lane L is illustrated. In the fourth embodiment, an input device 2 and a transaction processing device 3 are provided for one payment lane L, and the payment device 4, the display device 5, and the reading device 9 are shared by two adjacent payment lanes L. For example, a payment device 4 is installed near two payment lanes L. A display device 5 is provided near each space SP of the two payment lanes L. Then, a reading device 9 is provided in a location where the machine-readable code displayed on the reading device 9 can be read. In this way, a customer in one payment lane L can operate the transaction processing device 3 or the shared payment device 4 of that payment lane L by himself to settle a transaction. Similarly, a customer in the other payment lane L can operate the transaction processing device 3 or the shared payment device 4 of that payment lane L by himself to settle a transaction.

[0304] [Fifth embodiment] In the first embodiment, when the transaction cannot be settled, transaction processing device 3 outputs information related to the transaction to reservation server 1 and reserves the information in reservation server 1. In the fifth embodiment, transaction processing device 3 outputs information related to the transaction to reservation server 1 and reserves the information in reservation server 1, regardless of whether the transaction can be settled or not. At this time, a read screen SDa is displayed on display device 5. Here, when the transaction has not been settled in payment device 4 and a request event is output from payment device 4, reservation server 1 transmits information related to the reserved transaction to payment device 4. That is, the customer operates payment device 4 to make a payment. On the other hand, when the transaction has been settled in payment device 4 and an instruction screen SDb is displayed on display device 5, the information related to the reserved transaction is transmitted to payment device 4 to an output destination instructed by the operation of a store clerk, that is, payment device 4 or transaction processing device 3. That is, the customer operates transaction processing device 3 or payment device 4 to make a payment. Even if such a configuration is adopted, it is possible to achieve the effect of reducing labor costs by having the purchaser perform an operation related to the payment of the price.

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

[0306] 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 folder, 201...input means, 202...completion acceptance means, 203...first payment acceptance means, 301...input information acquisition means, 302...first amount output means, 303...second payment acceptance means , 304...first payment means, 305...transaction information output means, 306...guidance means, 307...execution means, 401...importing means, 402...second amount output means, 403...third payment accepting means, 404...second payment means, 501...accepting 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

1. A transaction processing device, a payment device, and a display device, The transaction processing device includes: a first settlement means for settling a transaction based on information relating to the transaction acquired via an input device; a transaction information output means for outputting information relating to the transaction to a reservation device when the settlement of the transaction is impossible; Equipped with The display device includes: a display means for displaying, in a readable manner by a reading device, transaction identification information for identifying the transaction for which information relating to the transaction has been output to the holding device; Equipped with The payment device, an acquisition means for acquiring information related to a transaction identified by the transaction identification information read by the reading device from the holding device; a second settlement means for settling the transaction based on the information related to the transaction acquired by the acquisition means; A payment system comprising:

2. The transaction information output means of the transaction processing device includes: A payment system as described in claim 1, which generates the transaction identification information when an instruction to end input of information related to the transaction is received via the input device while settlement of the transaction is impossible, and outputs the information related to the transaction together with the transaction identification information to the holding device.

3. The display means of the display device is When the settlement device is capable of settling the transaction, the transaction identification information is displayed so as to be readable by the reading device. The payment system according to claim 1.

4. The display device includes: a second display means for displaying an instruction screen for receiving an instruction for an output destination of information related to the transaction reserved in the reservation device when the reservation device is unable to settle the transaction; The payment system of claim 3 further comprising:

5. The second display means of the display device is A payment system as described in claim 4, which displays an instruction screen having a first operator for accepting that the output destination of information related to the transaction is to be the payment device, and a second operator for accepting that the output destination of information related to the transaction is to be the transaction processing device.

6. The display device includes: a third display means for displaying a confirmation screen for receiving an instruction to return the information related to the transaction output to the settlement device to the holding device; 5. The payment system according to claim 4, further displaying:

7. The payment device, 5. The payment system according to claim 4, further comprising a process for displaying the instruction screen on the display device when the transaction identification information is read by the reading device when the transaction cannot be settled.

8. A transaction processing device, a payment device, and a display device, The transaction processing device includes: a transaction information output means for outputting information relating to a transaction acquired via an input device to a holding device; a first settlement means for settling the transaction based on the information related to the transaction held in the holding device; Equipped with The display device includes: a display means for displaying, in a readable manner by a reading device, transaction identification information for identifying the transaction for which information relating to the transaction has been output to the holding device; Equipped with The payment device, an acquisition means for acquiring information related to a transaction identified by the transaction identification information read by the reading device from the holding device; a second settlement means for settling the transaction based on the information related to the transaction acquired by the acquisition means; A payment system comprising:

Images