Settlement system

Abstract

To cause a customer to perform an operation concerning payment of a price to thereby reduce personnel expenses.SOLUTION: A settlement system includes a first processing device, a second settlement device, and an instruction device. The first processing device includes an input device by which a shop clerk as an operator inputs information related to a transaction with a customer and a first settlement device by which the customer as an operator settles the transaction based on the information related to the transaction input through the input device. The second settlement device acquires the information related to the transaction from a holding device that holds the information related to the transaction input with the input device, and the customer as an operator settles the transaction. The instruction device instructs the shop clerk as an operator to output the information related to the transaction held by the holding device to the second settlement device. The settlement system locates the instruction device on the side opposite to the side of an operation surface of the second settlement device to be operated by the customer.SELECTED DRAWING: Figure 47

Description

[Technical Field]

[0001] FIELD OF THE INVENTION An embodiment of the present invention relates to a payment system. [Background technology]

[0002] Two-person systems are used as payment systems for large retail stores such as supermarkets and home improvement centers. A two-person payment system includes an input device operated by a store clerk known as a checker and a transaction processing device operated by a store clerk known as 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 processes product sales data for the purchased items based on the information input via the input device and settles the transaction with the customer. Because the input device and transaction processing device are separate in a two-person payment system, input of information related to the purchased items of a second customer can begin on the input device while the transaction processing device is processing the payment for the first customer. This allows for efficient handling of customers.

[0003] On the other hand, in recent years, from the perspective of reducing labor costs and preventing infectious diseases, there has been a demand for customers to perform the operations related to depositing money required for transaction settlement themselves. Even in two-person payment systems, customers are required to perform the operations related to depositing money into the transaction processing device themselves. This eliminates the need for a store clerk to act as a cashier, thereby reducing labor costs. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Publication No. 2018-152133 Summary of the Invention [Problem to be solved by the invention]

[0005] The problem to be solved by the embodiments of the present invention is to provide a payment system that reduces labor costs by having customers perform operations related to payment. [Means for solving the problem]

[0006] In one embodiment, the payment system includes a first processing device, a second payment device, and an instruction device. The first processing device includes an input device operated by a store clerk to input information related to a transaction with a customer, and a first payment device operated by the customer to settle the transaction based on the information related to the transaction input via the input device. The second payment device acquires information related to the transaction input via the input device from a holding device that holds the information related to the transaction, and the customer operates the transaction to settle the transaction. The instruction device instructs the second payment device to output information related to the transaction held by the holding device, operated by the store clerk. The payment system also places the instruction device on the opposite side of the second payment device from the operation surface operated by the customer. [Brief explanation of the drawings]

[0007] [Figure 1] FIG. 1 is a block diagram showing a schematic configuration of a payment system according to an embodiment. [Figure 2] FIG. 2 is a schematic diagram showing the relative positions of the input device, transaction processing device, settlement device, and instruction device provided in one settlement lane. [Figure 3] FIG. 3 is a block diagram showing the main circuit configuration of 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. [Figure 5] FIG. 5 is a block diagram showing the 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 settlement 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 the lane table held by the reservation server. [Figure 9] FIG. 9 is a block diagram showing the main circuit configuration of the indicating device. [Figure 10] FIG. 10 is a schematic diagram showing the main functional configurations of the reservation server, input device, transaction processing device, settlement device, and instruction device. [Figure 11] FIG. 11 is a flowchart showing the main steps of a first information processing routine 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 routine executed by a processor of the transaction processing device in accordance with a first business program. [Figure 13] FIG. 13 is a flowchart showing the main steps of a first information processing routine 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 first 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 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 16] FIG. 16 is a flowchart showing the main steps of the third information processing executed by the processor of the transaction processing device in accordance with the first business program. [Figure 17] FIG. 17 is a flowchart showing the main steps of the fourth information processing 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 the fourth information processing executed by the processor of the reservation server in accordance with the second business program. [Figure 19] FIG. 19 is a flowchart showing the main steps of the fifth information processing executed by the processor of the settlement device in accordance with the third business program. [Figure 20]FIG. 20 is a flowchart showing the main steps of the sixth information processing executed by the processor of the settlement device in accordance with the third business program. [Figure 21] FIG. 21 shows an example of a registration screen displayed on the touch panel of the input device. [Figure 22] FIG. 22 is an example of a registration screen displayed on the display of the input device. [Figure 23] FIG. 23 is an example of a small plan screen displayed on the touch panel of the input device. [Figure 24] FIG. 24 is an example of a small plan view displayed on the display of the input device. [Figure 25] FIG. 25 shows an example of a payment method selection screen displayed on the touch panel of the input device. [Figure 26] FIG. 26 is an example of a payment screen displayed on the touch panel of the input device. [Figure 27] FIG. 27 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 28] FIG. 28 shows an example of text displayed on the small screen of the display of the input device while waiting for payment. [Figure 29] FIG. 29 shows an example of a pop-up that is displayed on the payment screen of the touch panel of the input device when payment is possible at the transaction processing device. [Figure 30] FIG. 30 shows an example of text that is displayed on the small screen of the display of the input device when payment is possible at the transaction processing device. [Figure 31] FIG. 31 shows an example of a payment method selection screen displayed on the second touch panel of the transaction processing device. [Figure 32] FIG. 32 shows an example of a payment notification screen displayed on the second touch panel of the transaction processing device. [Figure 33] FIG. 33 shows an example of a payment in progress screen displayed on the second touch panel of the transaction processing device. [Figure 34]FIG. 34 shows an example of a payment completion screen displayed on the second touch panel of the transaction processing device. [Figure 35] FIG. 35 shows an example of a guidance screen displayed on the first touch panel of the transaction processing device. [Figure 36] FIG. 36 shows an example of an instruction screen displayed on the touch panel of the instruction device. [Figure 37] FIG. 37 shows an example of a pop-up that is displayed on the payment screen of the touch panel of the input device when payment is possible at the payment device. [Figure 38] FIG. 38 shows an example of text that is displayed on the small screen of the display of the input device when payment is possible at the payment device. [Figure 39] FIG. 39 shows an example of a statement confirmation screen displayed on the touch panel of the settlement device. [Figure 40] FIG. 40 shows an example of a payment method selection screen displayed on the touch panel of the payment device. [Figure 41] FIG. 41 shows an example of a payment notification screen displayed on the touch panel of the settlement device. [Figure 42] FIG. 42 shows an example of a payment screen displayed on the touch panel of the payment device. [Figure 43] FIG. 43 shows an example of a payment completion screen displayed on the touch panel of the settlement device. [Figure 44] FIG. 44 is a sequence diagram for explaining the operation of the payment system according to the embodiment. [Figure 45] FIG. 45 is a sequence diagram for explaining the operation of the payment system according to the embodiment. [Figure 46] FIG. 46 is a sequence diagram for explaining the operation of the payment system according to the embodiment. [Figure 47] FIG. 47 is a schematic diagram showing a first pattern in the layout of the payment system. [Figure 48] FIG. 48 is a schematic diagram showing a modified example of the first pattern. [Figure 49]FIG. 49 is a schematic diagram showing a modified example of the first pattern. [Figure 50] FIG. 50 is a schematic diagram showing a modified example of the first pattern. [Figure 51] FIG. 51 is a schematic diagram showing a second pattern in the layout of the payment system. [Figure 52] FIG. 52 is a schematic diagram showing a modified example of the second pattern. [Figure 53] FIG. 53 is a schematic diagram showing a third pattern in the layout of the payment system. [Figure 54] FIG. 54 is a schematic diagram showing a fourth pattern in the layout of the payment system. [Figure 55] FIG. 55 is a schematic diagram showing a modification of the fourth pattern. [Figure 56] FIG. 56 is a schematic diagram showing a fifth pattern in the layout of the payment system. [Figure 57] FIG. 57 is a schematic diagram showing a modification of the fifth pattern. [Figure 58] FIG. 58 is a schematic diagram showing a modification of the fifth pattern. [Figure 59] FIG. 59 is an example of an instruction screen displayed on an instruction device of a payment system using the layout of the fifth pattern. DETAILED DESCRIPTION OF THE INVENTION

[0008] Hereinafter, the embodiments will be described with reference to the drawings. First, the basic configuration and operation of the payment system according to the embodiment will be described with reference to FIGS.

[0009] [Payment system configuration explanation] FIG. 1 is a block diagram showing the schematic configuration of a payment system 100 according to an embodiment. The payment system 100 includes a holding server 10. The payment system 100 also includes a first processing device 1, a payment device 40, and an instruction device 50 for each payment lane L. The first processing device 1 includes an input device 20 and a transaction processing device 30. A payment lane L includes an aisle where customers line up to settle transactions. If the payment system 100 is installed in a retail store, the customers are consumers who purchase products. If the payment system 100 is installed 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 number, for example, a three-digit lane number.

[0010] Settlement system 100 connects holding server 10 to transaction processing devices 30 and settlement devices 40 of each settlement lane L via a communication network 60, such as a local area network (LAN), for bidirectional communication. An input device 20 is connected to transaction processing devices 30 for each settlement lane L via a transmission cable 70. Settlement system 100 also connects instruction devices 50 of each settlement lane L to communication network 60 via wired or wireless connections. However, instruction devices 50 only recognize the communication addresses of settlement devices 40 in the same settlement lane L. Therefore, instruction devices 50 can communicate data with settlement devices 40, but cannot communicate data with holding server 10 and transaction processing devices 30. Furthermore, direct data communication does not occur between transaction processing devices 30 and settlement devices 40. Details of holding server 10, input devices 20, transaction processing devices 30, settlement devices 40, and instruction devices 50 will be described later.

[0011] FIG. 2 is a schematic diagram showing the relative positions of input device 20, transaction processing device 30, payment device 40, and instruction device 50 provided in one payment lane L. FIG. 2 shows a payment lane L in a retail store such as a supermarket or home improvement center. This type of retail store is separated into a sales area where products are displayed and a checkout area called a cash register or the like. Payment lane L is provided in the checkout area.

[0012] The checkout area is equipped with a checkout counter 80. The retail store installs the checkout counter 80 along an aisle PA along which customers walk in the direction of the arrow in the figure. The retail store attaches an input device 20 to a top surface 81 of the checkout counter 80. The upstream side of the aisle PA from the input device 20 is a platform 82 on which purchased items can be placed before registration, and the downstream side is a platform 83 on which purchased items can be placed after registration.

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

[0014] More specifically, the input device 20 has a stationary scanner 21 fixed to the top surface of the checkout counter 80. The stationary scanner 21 is vertical, with a barcode reading window located on the surface opposite the aisle PA. The input device 20 has a handheld scanner 22 attached to 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.

[0015] With this arrangement of input / output devices, an employee, or so-called store clerk, standing in space SP on the opposite side of checkout counter 80 from aisle PA can operate stationary scanner 21, handheld scanner 22, touch panel 23, or keyboard 24 to input information related to a transaction with a customer. Information related to a transaction with a customer is, for example, information related to the products purchased by the customer. The store clerk can check the product name, unit price, etc. of the purchased product from the information displayed on touch panel 23. The customer can check the product name, unit price, etc. of the purchased product from the information displayed on display 25. The input device 20 can also be called a scanner device, etc.

[0016] Transaction processing device 30 is a computer device that functions as a terminal of a POS (Point Of Sales) system. A retail store installs transaction processing device 30 at the downstream end of checkout counter 80.

[0017] Transaction processing device 30 includes devices such as keyboard 31, first touch panel 32, second touch panel 33, printer 34, automatic change dispenser 35, and cashless payment terminal 36. Transaction processing device 30 is arranged so that keyboard 31 and first touch panel 32 can be operated by a store clerk, and second touch panel 33, printer 34, automatic change dispenser 35, and cashless payment terminal 36 can be operated by a customer.

[0018] With such an arrangement of devices, a store clerk standing in the space SP can operate the keyboard 31 or the first touch panel 32 while looking at the screen of the first touch panel 32. Meanwhile, a customer standing in the aisle PA can immediately check the information displayed on the second touch panel 33, such as information related to payment. A customer who pays with cash can insert cash into the automatic change machine 35 while standing in the aisle PA and collect the dispensed change. A customer who pays with cashless payment can operate the cashless payment terminal 36 while standing in the aisle PA to make a cashless payment. Once payment is complete, a receipt is printed from the printer 34, so the customer can receive the receipt on the spot.

[0019] In this way, transaction processing device 30 functions as a self-service payment device that allows customers to perform operations related to payment themselves. Transaction processing device 30 can also be referred to as a POS terminal, an electronic cash register, a sales processing device, etc.

[0020] Payment device 40 is also a self-service payment device that allows customers to perform operations related to payment themselves. Payment device 40 is used by customers who cannot pay at transaction processing device 30 because transaction processing device 30 is in use, for example. For this reason, retail stores install payment device 40 downstream of transaction processing device 30 in the direction of customer movement, as indicated by the arrow in the figure. Specifically, payment device 40 is installed along the side of transaction processing device 30 opposite the side that faces a customer standing in aisle PA to operate transaction processing device 30.

[0021] Payment device 40 includes devices such as a touch panel 41, printer 42, automatic change dispenser 43, and cashless payment terminal 44. The operation panel surface of touch panel 41, the receipt issuing port of printer 42, the coin insertion / withdrawal port of automatic change dispenser 43, and the operation section of cashless payment terminal 44 are all located on one side of the device body. A retail store installs payment device 40 so that one side faces a customer who passes in front of transaction processing device 30.

[0022] With this type of installation, customers facing the payment device 40 can immediately check information displayed on the touch panel 41, such as information related to payment. Customers who pay in cash can then insert cash into the automatic change dispenser 43 and collect the change that is dispensed. Customers who pay cashlessly can then operate the cashless payment terminal 44 to make the payment cashlessly. Once payment is complete, a receipt is issued from the printer 42, so the customer can receive the receipt on the spot. The payment device 40 can also be referred to as an accounting machine, a self-service POS terminal, a payment machine, etc.

[0023] The instruction device 50 is a device that instructs the settlement device 40 to call up information related to a transaction that has been held in the holding server 10. As will be described in detail later, the holding server 10 has the function of holding information related to a transaction with a customer through the operation of the transaction processing device 30. When the instruction device 50 receives an instruction to call up information related to a transaction in the settlement device 40, it issues the instruction to the holding server 10.

[0024] As an example, the instruction device 50 is a tablet terminal. A tablet terminal is an input device equipped with a flat LCD screen and can be operated by touching the screen with a finger or a pen. The instruction device 50 is operated by a store clerk. For this reason, the retail store installs the instruction device 50 in a position that is easy for the store clerk in the space SP to operate. The installation position of the instruction device 50 is not particularly limited. Figure 2 shows an example in which the instruction device 50 is installed on the side of the payment device 40 opposite to the side operated by the customer, with the screen facing the space SP.

[0025] [Configuration of transaction processing equipment] 3 is a block diagram showing the main circuit configuration of transaction processing device 30. Transaction processing device 30 includes processor 301, main memory 302, auxiliary storage device 303, clock 304, communication interface 305, touch panel interface 306, printer interface 307, change dispenser interface 308, payment terminal interface 309, input device interface 310, and system transmission path 311. System transmission path 311 includes an address bus, a data bus, control signal lines, and the like. System transmission path 311 connects processor 301 to the other components and transmits data signals exchanged between them.

[0026] Transaction processing device 30 constitutes a computer by connecting processor 301, main memory 302, auxiliary storage device 303, clock 304, communication interface 305, touch panel interface 306, printer interface 307, change dispenser interface 308, payment terminal interface 309, and input device interface 310 via system transmission path 311. Transaction processing device 30 then connects keyboard 31 and first touch panel 32 to this computer via system transmission path 311. Transaction processing device 30 also connects second touch panel 33 to touch panel interface 306, printer 34 to printer interface 307, automatic change dispenser 35 to change dispenser interface 308, and cashless payment terminal 36 to payment terminal interface 309.

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

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

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

[0030] The clock 304 keeps track of the date and time. The processor 301 processes the date and time kept by the clock 304 as the current date and time.

[0031] Communication interface 305 is an interface for communicating data with reservation server 10 connected to communication network 60. Communication interface 305 is also an interface for communicating data with other servers, such as a POS server, also connected to communication network 60. 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 30 to manage sales, inventory, etc. at the time of sale.

[0032] Touch panel interface 306, printer interface 307, change dispenser interface 308, and payment terminal interface 309 are all interfaces for performing data communication with devices externally attached to transaction processing device 30. That is, touch panel interface 306 performs data communication with second touch panel 33. Printer interface 307 performs data communication with printer 34. Change dispenser interface 308 performs data communication with automatic change dispenser 35. Payment terminal interface 309 performs data communication with cashless payment terminal 36.

[0033] Input device interface 310 is an interface for performing data communication with input device 20 connected via transmission cable 70. That is, input device interface 310 performs data communication with each of fixed scanner 21, handheld scanner 22, touch panel 23, keyboard 24, and display 25. In this way, input device 20 is a collection of devices controlled by processor 301 of transaction processing device 30. That is, transaction processing device 30 and input device 20 can be said to be a single device (first processing device 1) controlled by a single processor 301.

[0034] 4 is a schematic diagram showing major storage areas formed in main memory 302. Transaction processing device 30 uses part of the volatile storage area in main memory 302 as areas for first file area 3021, second file area 3022, status memory 3023, first flag memory 3024, second flag memory 3025, and employee memory 3026.

[0035] The first file area 3021 is an area for storing a transaction file created for each customer. The transaction file stores information related to a transaction with a customer that is processed as one transaction, such as information related to purchased items. Specifically, the transaction file stores product sales data including items such as product code, product name, unit price, purchase quantity, and sales amount. The product code is a unique code assigned to each product to identify it. The sales amount is the unit price multiplied by the purchase quantity. The product sales data only needs to include at least the product code and purchase quantity of the purchased product.

[0036] Second file area 3022 is an area for temporarily storing transaction files of customers who make payments at transaction processing device 30. Second file area 3022 stores transaction files stored in first file area 3021 or transaction files reserved by reservation server 10.

[0037] The status memory 3023 is an area for storing the payment status ST. The payment status ST is identification information that indicates the status of the payment. There are two payment statuses: a first status in which no payment method is specified using the input device 20, and a second status in which a payment method is specified using the input device 20. In this embodiment, the payment status ST that indicates the first status is set to "10," and the payment status ST that indicates the second status is set to "20."

[0038] First flag memory 3024 is an area for storing payment in progress flag Fa. Payment in progress flag Fa is 1-bit data for identifying whether or not payment is in progress at transaction processing device 30. In this embodiment, payment in progress flag Fa indicating that payment is in progress is set to "1," and payment in progress flag Fa indicating that payment is not in progress is set to "0."

[0039] Second flag memory 3025 is an area for storing pending flag Fb. Pending flag Fb is one-bit data for identifying whether a transaction file storing information related to a transaction processed by transaction processing device 30 is on hold in reservation server 10. In this embodiment, pending flag Fb indicating that a transaction is on hold is set to "1," and pending flag Fb indicating that a transaction is not on hold is set to "0."

[0040] Employee memory 3026 is an area for storing employee codes. The employee code is a unique code assigned to each store clerk who is an employee of the store. The employee code functions as operator identification information that identifies the clerk who operates input device 20. Employee memory 3026 stores the employee code of the clerk who has signed on to transaction processing device 30. Signing on means authenticating the operator of input device 20 and making input device 20 and transaction processing device 30 available for use. A clerk standing in space SP first signs on by entering his or her employee code and password. Once the employee code and password are authenticated and sign-on is successful, the employee code is stored in employee memory 3026. In this way, input device 20 and transaction processing device 30 are available for use.

[0041] Incidentally, when a store clerk has finished using the device, they sign off. Signing off means returning input device 20 and transaction processing device 30 to an unusable state. By signing off, the employee code in employee memory 3026 is cleared. Furthermore, input device 20 and transaction processing device 30 are placed in an unusable state. Signing on can also be referred to as logging in or signing in. Signing off can also be referred to as logging out or signing out. The employee code can also be referred to as a store clerk code, employee ID, store clerk ID, etc.

[0042] [Settlement device configuration explanation] 5 is a block diagram showing the main circuit configuration of payment device 40. As shown in the figure, payment device 40 includes processor 401, main memory 402, auxiliary storage device 403, clock 404, communication interface 405, and system transmission path 406. System transmission path 406 includes an address bus, a data bus, control signal lines, etc. System transmission path 406 connects processor 401 to each of the other components and transmits data signals exchanged between them.

[0043] The payment device 40 constitutes a computer by connecting a processor 401, a main memory 402, an auxiliary storage device 403, a clock 404, and a communication interface 405 via a system transmission path 406. The payment device 40 then connects a touch panel 41, a printer 42, an automatic change dispenser 43, and a cashless payment terminal 44 to the computer via the system transmission path 406.

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

[0045] The main memory 402 corresponds to the main storage portion of the computer. The main memory 402 includes a nonvolatile memory area and a volatile memory area. The main memory 402 stores an operating system or application programs in the nonvolatile memory area. The main memory 402 may store data required for the processor 401 to execute processes for controlling each unit in either the nonvolatile or volatile memory area. The main memory 402 uses the volatile memory area as a work area where data is rewritten by the processor 401 as appropriate. The nonvolatile memory area is, for example, a ROM. The volatile memory area is, for example, a RAM.

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

[0047] The clock 404 keeps track of the date and time. The processor 401 processes the date and time kept by the clock 404 as the current date and time.

[0048] The communication interface 405 is an interface for performing data communication between the reservation server 10 and the instruction device 50 connected to the communication network 60 .

[0049] 6 is a schematic diagram showing the main storage areas formed in the main memory 402. The settlement device 40 uses part of the volatile storage area in the main memory 402 as an area for a third file area 4021 and a third flag memory 4022. The third file area 4021 is an area for temporarily storing transaction files of customers who make payments using the settlement device 40. The third file area 4021 stores transaction files that have been reserved by the reservation server 10.

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

[0051] [Configuration of reserved server] 7 is a block diagram showing the main circuit configuration of reservation server 10. As shown in the figure, reservation server 10 comprises processor 101, main memory 102, auxiliary storage device 103, clock 104, communication interface 105, and system transmission path 106. System transmission path 106 includes an address bus, a data bus, and control signal lines. System transmission path 106 connects processor 101 to each of the other components and transmits data signals exchanged between them.

[0052] The reservation server 10 is configured as a computer by connecting a processor 101, a main memory 102, an auxiliary storage device 103, a clock 104, and a communication interface 105 via a system transmission line 106.

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

[0054] The main memory 102 corresponds to the main storage portion of the computer. The main memory 102 includes a nonvolatile memory area and a volatile memory area. The main memory 102 stores an operating system or application programs in the nonvolatile memory area. The main memory 102 may store data required for the processor 101 to execute processes for controlling each part in either the nonvolatile or volatile memory area. The main memory 102 uses the volatile memory area as a work area where data can be rewritten by the processor 101 as appropriate. The nonvolatile memory area is, for example, ROM. The volatile memory area is, for example, RAM.

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

[0056] The clock 104 keeps track of the date and time. The processor 101 processes the date and time kept by the clock 104 as the current date and time.

[0057] Communication interface 105 is an interface for performing data communication between transaction processing device 30 and settlement device 40 connected to communication network 60 .

[0058] The reservation server 10 configured as described above uses part of the storage area in the auxiliary storage device 103 as an area for the employee master 1031. The employee master 1031 is a database that stores the name, password, etc. of each store clerk in association with the employee code of that store clerk. The password is a sign-on password set by the store clerk identified by the employee code. The employee master 1031 may be stored in a server other than the reservation server 10, for example, a POS server.

[0059] Reserve server 10 uses a portion of the storage area in auxiliary storage device 103 as the area for lane table 1032. The data structure of lane table 1032 is shown in the schematic diagram of FIG. 8. As shown in the figure, lane table 1032 has a column Ca for lane numbers, a column Cb for transaction processing device IDs, a column Cc for settlement device IDs, a column Cd for instruction device IDs, and a column Ce for employee codes. Lane table 1032 pre-describes the lane number of each settlement lane L in column Ca. Lane table 1032 also describes, in columns Cb, Cc, and Cd, the device IDs of transaction processing devices 30, settlement devices 40, and instruction devices 50 located in the settlement lane L with the lane number described in column Ca in the same row. All transaction processing devices 30 constituting settlement system 100 are assigned a transaction processing device ID as unique identification information. Similarly, a payment device ID is set as different identification information for each of the payment devices 40, and a pointing device ID is set as different identification information for each of the instruction devices 50.

[0060] For example, by combining a three-digit number "XXX" with a lane number nnn, a different ID "XXXnnn" can be created for each lane. Therefore, by making the three-digit number "XXX" different for transaction processing device 30, settlement device 40, and instruction device 50, different identification information (device ID) can be created for each device.

[0061] Column Ce is cleared by default. When a user signs on to transaction processing device 30 installed in settlement lane L with the corresponding lane number, column Ce is filled with the employee code authenticated by the sign-on. When a user subsequently signs off from transaction processing device 30, the employee code in column Ce is cleared.

[0062] Returning to the explanation of Figure 7. Reserve server 10 uses a portion of the storage area in auxiliary storage device 103 as an area for employee-specific folders 1033. Employee-specific folders 1033 are prepared for the number of clerks who can operate input device 20, and are data folders identified by the employee code of each clerk. Employee-specific folders 1033 are areas for storing, or in other words, reserving, transaction files output from transaction processing device 30 to reserve server 10. Reserve server 10 stores transaction files, i.e., information related to transactions with customers, in employee-specific folders 1033 identified by the employee code of the clerk who signed on to transaction processing device 30 that output the transaction file. Reserve server 10 can also be referred to as a reserve device.

[0063] [Indicator device configuration explanation] 9 is a block diagram showing the main circuit configuration of the instruction device 50. As shown in the figure, the instruction device 50 includes a processor 501, a main memory 502, an auxiliary storage device 503, a communication interface 504, a touch panel 505, a camera 506, and a system transmission path 507. The system transmission path 507 includes an address bus, a data bus, a control signal line, etc. The system transmission path 507 connects the processor 501 to each of the other components and transmits data signals exchanged between them.

[0064] The instruction device 50 constitutes a computer by connecting a processor 501, a main memory 502, an auxiliary storage device 503, and a communication interface 504 via a system transmission path 507. The instruction device 50 connects a touch panel 505 and a camera 506 to the computer via the system transmission path 507. Note that the devices included in the instruction device 50 are not limited to the touch panel 505 and the camera 506. The instruction device 50 may also include a keyboard, a pointing device, a barcode scanner, etc.

[0065] The processor 501 corresponds to the central part of the computer. The processor 501 controls each part to realize various functions of the instruction device 50 in accordance with an operating system or an application program. The processor 501 is, for example, a CPU. The processor 501 may be a multi-core processor that includes multiple processor cores and is capable of executing multiple processes in parallel.

[0066] The main memory 502 corresponds to the main storage portion of the computer. The main memory 502 includes a nonvolatile memory area and a volatile memory area. The main memory 502 stores an operating system or application programs in the nonvolatile memory area. The main memory 502 may store data required for the processor 501 to execute processes for controlling each unit in either the nonvolatile or volatile memory area. The main memory 502 uses the volatile memory area as a work area where data is rewritten by the processor 501 as appropriate. The nonvolatile memory area is, for example, a ROM. The volatile memory area is, for example, a RAM.

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

[0068] The communication interface 504 is an interface for performing data communication with the payment device 40 connected to the communication network 60 .

[0069] The instruction device 50 configured as described above uses part of the storage area in the auxiliary storage device 503 as an employee memory 5031 area. The employee memory 5031 is an area for storing employee codes. The instruction device 50 uses the screen of the touch panel 505 as an instruction screen SEa (see FIG. 36). The instruction screen SEa will be described in detail later, but the instruction screen SEa is a screen on which the operator of the instruction device 50, that is, a store clerk who can become an instructor, can be selected. The employee memory 5031 stores the employee code of the clerk selected as an instructor.

[0070] [Explanation of the payment system's functional configuration] 10 is a schematic diagram showing the main functional configurations of reservation server 10, input device 20, transaction processing device 30, settlement device 40, and instruction device 50. Below, the functions of each device will be explained in the order of input device 20, transaction processing device 30, instruction device 50, reservation server 10, and settlement device 40.

[0071] The input device 20 functions as an input means 2011, a payment completion acceptance means 2012, and a first payment acceptance means 2013. The input means 2011 has a function of inputting information related to a transaction with a customer, that is, information related to the purchased goods purchased by the customer. The input means 2011 inputs information related to the purchased goods, such as a product code and a purchase quantity, via an input device such as the fixed scanner 21, the handheld scanner 22, the touch panel 23, or the keyboard 24. For example, the input means 2011 inputs the product code of the purchased goods from a barcode read by the fixed scanner 21 or the handheld scanner 22. For example, the input means 2011 inputs the purchase quantity of the purchased goods from a numerical value input by operating the numeric keypad on the touch panel 23 or the keyboard 24.

[0072] The completion accepting means 2012 is a function that accepts an instruction to end input of information related to a transaction with a customer, that is, information related to the purchased product that the customer purchases. The completion accepting means 2012 accepts the instruction to end input of information related to the purchased product via an input device such as the touch panel 23 or the keyboard 24. For example, the completion accepting means 2012 accepts a signal generated by a predetermined key operation on the touch panel 23 or the keyboard 24 as the input end instruction.

[0073] The first payment accepting means 2013 has a function of accepting a selection 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 accepting means 2013 displays a selection screen for a payment method on the touch panel 23. The first payment accepting means 2013 then accepts the payment method selected by touching the screen as the selected payment method. The type of device is not particularly limited. For example, it may be a keyboard 24. Payment methods include cash, vouchers such as gift certificates, credit cards, electronic money, code payment, etc. Note that the first payment accepting means 2013 does not need to support all of the payment methods described above. For example, it may support only the payment method using vouchers such as gift certificates.

[0074] Transaction processing device 30 has the functions of input information acquiring means 3011, first amount output means 3012, second payment accepting means 3013, first settlement means 3014, operator acquiring means 3015, transaction information output means 3016, guidance means 3017, hold release means 3018, and execution means 3019. Input information acquiring means 3011 has a function of acquiring information, etc. from input device 20 connected via transmission cable 70. Input information acquiring means 3011 acquires information related to the purchased product input accepted by input means 2011 from input device 20. Input information acquiring means 3011 acquires an input end instruction signal accepted by end accepting means 2012 from input device 20. Input information acquiring means 3011 acquires information on the payment method accepted by first payment accepting means 2013 from input device 20.

[0075] First amount output means 3012 has a function of outputting the amount required for settlement based on transaction-related information input via input device 20. The transaction-related information is, for example, information related to purchased items. The information related to purchased items includes the price and sales quantity of the items. First amount output means 3012 calculates and outputs the amount required for settlement based on the price and sales quantity of each purchased item. The amount required for settlement can be referred to as the settlement amount, total amount, total amount including tax, invoice amount, etc. First amount output means 3012 outputs the amount required for settlement by displaying it on a display device. The display device corresponds to touch panel 23 or display 25 of input device 20. The display device may also be first touch panel 32 or second touch panel 33 of transaction processing device 30.

[0076] The second payment acceptance means 3013 has a function of accepting a selection of a payment method via a device operated by a customer. The device operated by the customer is, for example, the second touch panel 33. The second payment acceptance means 3013 displays a selection screen for a payment method on the second touch panel 33. The second payment acceptance means 3013 then accepts the payment method selected by touching the screen as the selected payment method. The type of device is not particularly limited. The device operated by the customer may be a pointing device that moves a pointer displayed on a display. Payment methods include cash, credit card, electronic money, code payment, etc. The second payment acceptance means 3013 accepts a selection of a payment method if the first payment acceptance means 2013 has not accepted a selection of a payment method at the time the completion acceptance means 2012 accepts an input end instruction. Whether or not a selection of a payment method has been accepted at the time the input end instruction is accepted can be determined by the payment status ST. Specifically, when the payment status ST is "10", that is, when the first state is set in which no payment method has been specified using the input device 20, the second payment acceptance means 3013 accepts the selection and input of any one payment method via the second touch panel 33.

[0077] The first payment means 3014 has a function of settling a transaction with a customer in accordance with the payment method accepted by the first payment accepting means 2013 or the second payment accepting means 3013. The first payment means 3014 settles a transaction with a customer if the transaction is possible at the time the completion accepting means 2012 accepts the input completion instruction. That is, the first payment means 3014 determines that the transaction is possible when the payment in progress flag Fa stored in the first flag memory 3024 is "0." For example, if the first payment means 3014 accepts cash as the payment method, it settles the transaction with the customer in cooperation with the automatic change dispenser 35. For example, if the first payment means 3014 accepts cashless payment as the payment method, it settles the transaction with the customer in cooperation with the cashless payment terminal 36.

[0078] The operator acquisition means 3015 is a function for acquiring operator identification information for identifying an operator. An operator is a store clerk who operates the input device 20 to input information related to transactions with customers. Therefore, the operator identification information is an employee code stored in the employee memory 3026. The operator acquisition means 3015 acquires the employee code from the employee memory 3026. The operator identification information for identifying the operator of the input device 20 is not necessarily an employee code. It may be any information that can identify an employee, such as a name or telephone number.

[0079] The transaction information output means 3016 has a function of outputting information related to a transaction to the reservation server 10. When the transaction information output means 3016 receives an instruction to end input of information related to a transaction from the input device 20 while settlement of the transaction is not possible, the transaction information output means 3016 outputs the information related to the transaction together with the operator identification information acquired by the operator acquisition means 3015 to the reservation server 10. The information related to the transaction is, for example, information related to purchased goods. The information related to purchased goods is stored in the transaction file as product sales data. When the payment in progress flag Fa in the first flag memory 3024 is set to "1" and the input information acquisition means 3011 acquires a signal instructing to end input, the transaction information output means 3016 controls the communication interface 305 to output the transaction file together with the operator identification information to the reservation server 10.

[0080] Guidance means 3017 has a function of guiding information related to transactions held in holding server 10, i.e., the output destination of the transaction file. The output destination of the transaction file held in holding server 10 is payment device 40 or transaction processing device 30. If the output destination of the transaction file is payment device 40, guidance means 3017 guides the user to pay the price at payment device 40. If the output destination of the transaction file is transaction processing device 30, guidance means 3017 guides the user to pay the price at transaction processing device 30. For example, guidance is provided to the store clerk or customer by displaying a guidance image on a display device. The display device corresponds to touch panel 23 or display 25 of input device 20, or first touch panel 32 or second touch panel 33 of transaction processing device 30, etc.

[0081] The hold release means 3018 is a function that instructs the hold server 10 to release information related to transactions that have been put on hold in the hold server 10, i.e., the transaction file. The hold release means 3018 has a second operator for receiving an instruction to release the hold of the transaction file. The second operator is a software key displayed on the first touch panel 32. The second operator may also be a hardware key provided on the keyboard 31. When the second operator is operated, the hold release means 3018 instructs the hold server 10 to release the hold of the transaction file. Specifically, the hold release means 3018 outputs a signal to the hold server 10 to instruct the hold server 10 to release the hold of the transaction file.

[0082] The execution means 3019 is a function that executes settlement of a transaction with a customer based on information related to the transaction that has been put on hold in the holding server 10. When the holding server 10 is instructed to release the transaction file from hold, the transaction file is stored in the second file area 3022. The execution means 3019 operates the first amount output means 3012 and the first settlement means 3014 based on the transaction file stored in the second file area 3022 to execute settlement of the transaction.

[0083] The instruction device 50 has the functions of a receiving means 5011 and an instruction means 5012. The receiving means 5011 has a function of receiving an instruction to output information related to transactions held in the holding server 10, i.e., a transaction file, to the settlement device 40. The instruction device 50 has a first operator for receiving an instruction to output the transaction file to the settlement device 40. When a tablet terminal is used as the instruction device 50, the first operator is a software key displayed on the LCD screen of the tablet terminal. When the first operator is operated and input, the receiving means 5011 receives it as an instruction to output the transaction file to the settlement device 40.

[0084] The instruction means 5012 has a function of instructing the reservation server 10 to output information related to the transaction to the settlement device 40 in response to receiving an instruction from the reception means 5011 to output the transaction file to the settlement device 40. The instruction means 5012 outputs a signal to the reservation server 10 via the settlement device 40 to instruct the output of information related to the transaction to the settlement device 40.

[0085] Reserve server 10 has the functions of transaction information input means 1011, reserve means 1012, output destination recognition means 1013, operator recognition means 1014, and reserve information output means 1015. Transaction information input means 1011 has a function of inputting information related to a transaction, that is, a transaction file, from transaction processing device 30. Transaction information input means 1011 inputs operator identification information along with the transaction file. The operator identification information is the employee code of the store clerk who has signed on to transaction processing device 30.

[0086] The holding means 1012 has a function of holding information relating to transactions, i.e., transaction files, input by the transaction information input means 1011. The holding means 1012 stores, i.e., holds, the transaction files in employee-specific folders 1033 identified by the operator identification information input together with the transaction files.

[0087] Output destination recognition means 1013 is a function that recognizes the output destination of transaction information, i.e., the transaction file, that is held by holding server 10. When output destination recognition means 1013 receives a signal from instruction means 5012 of instruction device 50 instructing that transaction information be output to settlement device 40, it recognizes the output destination of the transaction file as settlement device 40. When output destination recognition means 1013 receives a signal from hold release means 3018 of transaction processing device 30 instructing to release the hold, it recognizes the output destination of the transaction file as transaction processing device 30.

[0088] The operator recognition means 1014 is a function that recognizes the operator identification information of the operator who instructed the output destination of the transaction file. The person who instructs the output destination of the transaction file is a store clerk standing in space SP. The operator recognition means 1014 recognizes the employee code of the store clerk who performed an operation on the instruction device 50 or transaction processing device 30. The employee code of the store clerk is stored in column Ce of the lane table 1032. The employee code of the store clerk may be notified from the instruction device 50 or transaction processing device 30.

[0089] Reserved information output means 1015 has a function of outputting information related to transactions reserved by reserve means 1012, i.e., a transaction file, to an output destination recognized by output destination recognition means 1013. Reserved information output means 1015 outputs a transaction file stored in employee-specific folder 1033 specified by an employee code recognized by operator recognition means 1014 to the output destination. If the output destination recognized by output destination recognition means 1013 is settlement device 40, reserve information output means 1015 outputs the transaction file to settlement device 40. If the output destination recognized by output destination recognition means 1013 is transaction processing device 30, reserve information output means 1015 outputs the transaction file to transaction processing device 30.

[0090] The settlement device 40 has functions as an import means 4011, a second amount output means 4012, a third payment acceptance means 4013, and a second settlement means 4014. The import means 4011 has a function of importing information related to a transaction that has been put on hold in the holding server 10. The import means 4011 imports a transaction file output by the holding information output means 1015 of the holding server 10, and stores it in a third file area 4021.

[0091] The second amount output means 4012 is a function that outputs the amount required for settlement based on information related to the transaction held in the holding server 10. The second amount output means 4012 outputs the amount required for settlement based on information in the transaction file stored in the third file area 4021. For example, the second amount output means 4012 displays the amount required for settlement on a display device. The display device corresponds to the touch panel 41 of the payment device 40, etc.

[0092] The third payment acceptance means 4013 has a function of accepting 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 41. The third payment acceptance means 4013 displays a payment method selection screen on the touch panel 41. The third payment acceptance means 4013 then accepts the payment method selected by touching the screen as the selected and input payment method. There are no particular limitations on the type of device. The device operated by a customer may be a pointing device that moves a pointer displayed on a display. Payment methods include cash, credit card, electronic money, code payment, etc.

[0093] The second payment means 4014 has a function of settling a transaction based on transaction-related information held in the holding server 10. The second payment means 4014 settles a transaction with a customer in accordance with the payment method accepted by the first payment acceptance means 2013 or the third payment acceptance means 4013. The second payment means 4014 settles a transaction with a customer when the amount equivalent to the amount output by the second amount output means 4012 is paid using the payment method accepted by the first payment acceptance means 2013 or the third payment acceptance means 4013. For example, when cash is accepted as the payment method, the second payment means 4014 settles the transaction with the customer in cooperation with the automatic change dispenser 43. For example, when cashless payment is accepted as the payment method, the second payment means 4014 settles the transaction with the customer in cooperation with the cashless payment terminal 44. It should be noted that the information relating to the transaction held in the holding server 10 does not necessarily have to include the payment method accepted by the first payment accepting means 2013. If the payment method accepted by the first payment accepting means 2013 is not included, the second settlement means 4014 settles the transaction with the customer in accordance with the payment method accepted by the third payment accepting means 4013, based on the information relating to the transaction held in the holding server 10.

[0094] The functions of transaction processing device 30 as input information acquisition means 3011, first amount output means 3012, second payment acceptance means 3013, first settlement means 3014, operator acquisition means 3015, transaction information output means 3016, guidance means 3017, hold release means 3018 and execution means 3019 are all realized by information processing executed by processor 301 in accordance with the first business program.

[0095] The first business program is a type of application program stored in the main memory 302 or the auxiliary storage device 303. There are no particular limitations on the method for installing the first business program in the main memory 302 or the auxiliary storage device 303. The first business program can be installed in the main memory 302 or the auxiliary storage device 303 by recording it on a removable recording medium or by distributing it via communication over a network. The recording medium can 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.

[0096] The functions of the reservation server 10 as a transaction information input means 1011, reservation means 1012, output destination recognition means 1013, operator recognition means 1014 and reservation information output means 1015 are realized by information processing executed by the processor 101 in accordance with a second business program.

[0097] The second business program is a type of application program stored in the main memory 102 or the auxiliary storage device 103. There are no particular limitations on the method for installing the second business program in the main memory 102 or the auxiliary storage device 103. The second business program can be installed in the main memory 102 or the auxiliary storage device 103 by recording it on a removable recording medium or by distributing it via communication over a network. The recording medium can 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.

[0098] The functions of the payment device 40 as the import means 4011, second amount output means 4012, third payment acceptance means 4013 and second payment means 4014 are realized by information processing executed by the processor 401 in accordance with the third business program.

[0099] The third business program is a type of application program stored in the main memory 402 or the auxiliary storage device 403. There are no particular limitations on the method for installing the third business program in the main memory 402 or the auxiliary storage device 403. The third business program can be installed in the main memory 402 or the auxiliary storage device 403 by recording it on a removable recording medium or by distributing it via communication over a network. The recording medium can 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.

[0100] [Explanation of payment system operation] Next, the main operations of the payment system 100 will be explained using the flowcharts in Figures 11 to 20 and the screen examples in Figures 21 to 43. Note that the content and procedures of the operations explained using the flowcharts are examples. The content and procedures can be changed as appropriate as long as similar effects can be achieved. The screen examples are also 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.

[0101] 11 to 14 are flowcharts showing the main steps of the first information processing executed by processor 301 of transaction processing device 30 in accordance with the first business program. After going around the sales floor and collecting the purchased items, a customer moves to the checkout area. The customer then places the purchased items on table 82 of checkout counter 80 in an empty aisle PA. When the customer arrives at 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. Upon receiving this command, processor 301 starts the first information processing. In ACT101, processor 301 sets the screen of touch panel 23 and display 25 of input device 20 as the registration screen.

[0102] FIG. 21 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 the product name, purchase quantity, unit price, discount amount, and sales price of the purchased items in one transaction in list format in sequential numerical order. 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 the subtotal of the purchased items registered as one transaction.

[0103] Fig. 22 is an example of the registration screen SBa displayed on the display 25. The registration screen SBa is divided into multiple rows (seven rows in the example of Fig. 22), with the first row through the last row being rows of the detail area ABa, and the last row being a row of the total area ABb. Each row of the detail area ABa displays the product name, unit price, purchase quantity, and sales amount of the purchased item. The total area ABb displays the total purchase quantity and total sales amount in one row.

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

[0105] After the touch panel 23 and the display 25 are set to the registration screen SAa and the registration screen SBa, the processor 301 proceeds to ACT102. In ACT102, the processor 301 waits for the registration of the purchased item. When a product code is input from the input device 20 via the input device interface 310, the processor 301 determines that the purchased item has been registered. The processor 301 proceeds from ACT102 to ACT103. In ACT103, the processor 301 creates a transaction file in the first file area 3021. Hereinafter, the transaction file created in ACT103 will be referred to as the first transaction file.

[0106] After creating the first transaction file, the processor 301 proceeds to ACT104. In ACT104, the processor 301 processes the product sales data. This process reads the product name, unit price, etc. of the product identified by the input product code from the product master, and generates product sales data for the purchased product including the product code, product name, unit price, purchase quantity, sales amount, etc. After generating the product sales data for the purchased product, the processor 301 proceeds to ACT105. In ACT105, the processor 301 stores the product sales data for the purchased product in the first transaction file. In ACT106, the processor 301 also updates the registration screen SAa and the registration screen SBa.

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

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

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

[0110] When the purchased items are registered in the standby state of ACT107 and ACT108, the processor 301 returns to ACT104. Then, the processor 301 executes the processes of ACT104 to ACT106 in the same manner as described above. Thus, each time the store clerk operates the fixed scanner 21, handheld scanner 22, or touch panel 23 of the input device 20 to input data for each purchased item placed on the checkout counter 80, the processor 301 generates product sales data for the purchased item based on the information related to the purchased item, i.e., the product code, and stores the data in the first transaction file. The processor 301 also updates the registration screen SAa and the registration screen SBa. When the store clerk has finished registering the purchased items in this manner, he or she touches the subtotal button BAa.

[0111] In the standby state of ACT107 and ACT108, when the subtotal button BAa is input by a touch operation, the processor 301 proceeds to ACT 109. In ACT109, the processor 301 sets the touch panel 23 of the input device 20 and the screen of the display 25 as the subtotal screen.

[0112] FIG. 23 is an example of the subtotal display SAb displayed on the touch panel 23. The subtotal display SAb includes a total area AAd that displays the total purchase quantity and total sales amount of the purchased items in one transaction. The subtotal display 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 pressing the subtotal discount button BAb and inputting a discount amount using the numeric keys on the keyboard 24. Similarly, the total amount is discounted by pressing the subtotal discount button BAc and inputting a discount rate using the numeric keys on the keyboard 24.

[0113] 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 stage. The back button BAf is an operator for instructing the return to the registration of the purchased item.

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

[0115] After checking the small screen SAb, the clerk checks whether any unregistered purchased items remain on the checkout counter 80. If there are any 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 busy times in the store, but not during quiet times. 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.

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

[0117] When the back button BAf is input by touch operation while in the standby state of ACT110 to ACT112, the processor 301 proceeds to ACT113. In ACT113, the processor 301 returns the screens of the touch panel 23 and the display 25 to the previous registration screens SAa and SBa. The processor 301 then enters a standby state for ACT107 and ACT108. In this way, the store clerk can operate the fixed scanner 21, the handheld scanner 22, or the touch panel 23 of the input device 20 to input data of the purchased item that has not been registered.

[0118] In the standby state of ACT110 to ACT112, when the payment method selection button BAd is input by a touch operation, the processor 301 proceeds to ACT121 in Fig. 12. In ACT121, the processor 301 changes the screen of the touch panel 23 to the payment method selection screen SAc (see Fig. 25). The screen of the display 25 remains the sub-screen SBb.

[0119] 25 is an example of the payment method selection screen SAc displayed on the touch panel 23. The payment method selection screen SAc includes a total area AAd similar to the 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, a code payment button, and a voucher button.

[0120] The cash button is a button for instructing cash payments. The credit button is a button for instructing credit card payments. The electronic money button is a button for instructing electronic money payments. The code payment button is a button for instructing code payment payments. The voucher button is a button for instructing payment by voucher. When the voucher button is pressed, a screen is displayed for selecting the type of voucher, such as a gift certificate. The cash button, credit button, electronic money button, code payment button and voucher button are all software keys.

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

[0122] When the screen of the touch panel 23 is the payment method selection screen SAc, the processor 301 proceeds to ACT122. The processor 301 waits for a payment method to be selected in ACT122. When one of the payment methods is selected by touching the selection button group BAg, the processor 301 proceeds to ACT123. The processor 301 acquires a payment code for the selected payment method in ACT123. In this embodiment, unique payment codes are 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 301 acquires a payment code corresponding to cash payment, such as "11." For example, when the credit button is touched, the processor 301 acquires a payment code corresponding to credit card payment, such as "22." The same applies when the other electronic money buttons and code payment buttons are touched.

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

[0124] Figure 26 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 user to proceed to payment. The payment button BAh is a software key. After checking the payment screen SAd, the store clerk touches the payment button BAh.

[0125] The processor 301, which has set the screen of the touch panel 23 to the payment screen SAd, proceeds to ACT 125. The processor 301 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 301 proceeds to ACT 126.

[0126] On the other hand, when the payment button BAe is input by a touch operation in the standby state of ACT110 to ACT112 in Fig. 11, the processor 301 proceeds to ACT126 in Fig. 12. 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 301 proceeds to ACT126.

[0127] Processor 301 checks payment in progress flag Fa in ACT 126. When payment has not yet been made at transaction processing device 30, payment in progress flag Fa is "0". When payment in progress flag Fa is "0", processor 301 proceeds to ACT 131 in Figure 13. The processing from ACT 131 onwards will be described later.

[0128] If the payment in progress flag Fa is "1" in ACT126, that is, if payment is being made at transaction processing device 30, processor 301 proceeds to ACT127. In ACT127, processor 301 checks the pending flag Fb. If information related to the transaction of the previous customer who made payment in the same settlement lane L is not being held in holding server 10, the pending flag Fb is "0." If the pending flag Fb is "0," processor 301 proceeds to ACT141 in FIG. 14. The processing from ACT141 onwards will also be described later.

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

[0130] 27 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 has finished paying.

[0131] 28 is an example of the text TXa displayed on the small screen SBb of the display 25. After checking the text TXa, the customer waits until payment is possible.

[0132] After notifying the user using the touch panel 23 and the display 25 that payment is not possible, the processor 301 returns to ACT125. The processor 301 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 301 proceeds to ACT126. Then, the processor 301 executes the processing 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 301 proceeds to ACT131 in FIG. 13. If the payment in progress flag Fa remains at "1" but the pending flag Fb has been rewritten to "0", the processor 301 proceeds to ACT141 in FIG. 14.

[0133] On the other hand, if the payment in progress flag Fa and the pending flag Fb remain at "1", the processor 301 proceeds to ACT 128. Therefore, the pop-up PUa continues to be displayed on the small print screen SAb or the payment screen SAd of the touch panel 23, and the text TXa continues to be displayed on the small print screen SBb of the display 25.

[0134] When payment in progress flag Fa is "0", that is, when payment has not been made at transaction processing device 30, if payment button BAe on subscreen SAb or payment button BAh on payment screen SAd is pressed, processor 301 proceeds to ACT131 in Figure 13. In ACT131, processor 301 displays a pop-up PUb (see Figure 29) on subscreen SAb or payment screen SAd of touch panel 23 to notify the user that payment at transaction processing device 30 is possible. Processor 301 also displays text TXb (see Figure 30) on subscreen SBb of display 25 to indicate that payment is possible.

[0135] 29 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 30, and will guide the customer to where transaction processing device 30 is installed.

[0136] 30 is an example of text TXb displayed on small screen SBb of display 25. After checking text TXb, the customer follows the instructions of the store clerk to move to where transaction processing device 30 is installed and makes payment.

[0137] After being notified that payment is possible using the touch panel 23 and the display 25, the processor 301 proceeds to ACT 132. In ACT 132, the processor 301 checks whether a payment code has been acquired. If a payment code has not been acquired, the processor 301 proceeds to ACT 133. In ACT 133, the processor 301 sets the payment status ST stored in the status memory 3023 to "10." On the other hand, if a payment code has been acquired in the processing of ACT 123, the processor 301 proceeds to ACT 134. In ACT 134, the processor 301 stores the payment code in the first transaction file. Furthermore, in ACT 135, the processor 301 sets the payment status ST stored in the status memory 3023 to "20."

[0138] After completing the processing of ACT133 or ACT135, the processor 301 proceeds to ACT136. In ACT136, the processor 301 selects the first transaction file stored in the first file area 3021. Then, in ACT137, the processor 301 saves the first transaction file in the second file area 3022. Thereafter, in ACT138, the processor 301 rewrites the payment in progress flag Fa in the first flag memory 3024 to "1." In addition, in ACT139, the processor 301 clears the first file area 3021. With this, the processor 301 ends the first information processing. Hereinafter, the transaction file saved in the second file area 3022 will be referred to as the second transaction file.

[0139] On the other hand, when the payment in progress flag Fa is "1" but the pending flag Fb is "0", if the payment button BAe on the sub-screen SAb or the payment button BAh on the payment screen SAd is pressed, the processor 301 proceeds to ACT141 in FIG. 14. In ACT141, the processor 301 checks whether a payment code has been acquired. If a payment code has not been acquired, the processor 301 proceeds to ACT142. In ACT142, the processor 301 sets the payment status ST stored in the status memory 3023 to "10". On the other hand, if a payment code has been acquired in the processing of ACT123, the processor 301 proceeds to ACT143. In ACT143, the processor 301 stores the payment code in the first transaction file. In ACT144, the processor 301 sets the payment status ST stored in the status memory 3023 to "20".

[0140] After completing the processing of ACT142 or ACT144, processor 301 proceeds to ACT145. In ACT145, processor 301 transmits a hold event to hold server 10 via communication interface 305. The hold event is an event that requests the holding of a transaction file. The hold event includes the transaction processor ID of the transaction processor 30.

[0141] As will be described in detail later, an acceptance response is returned from the reservation server 10 upon receiving the reservation event, and the processor 301 waits for the acceptance response in ACT 146. Then, upon receiving the acceptance response via the communication interface 305, the processor 301 proceeds to ACT 147. In ACT 147, the processor 301 obtains the employee code from the employee memory 3026. Then, in ACT 148, the processor 301 outputs the first transaction file together with the employee code to the reservation server 10.

[0142] Thereafter, in ACT 149, the processor 301 sets the pending flag Fb to "1." In addition, in ACT 150, the processor 301 clears the first file area 3021. With this, the processor 301 ends the first information processing.

[0143] As explained using FIG. 13, if payment in progress flag Fa is "0" when payment button BAe or payment screen SAd is pressed, that is, if no customer is currently paying at transaction processing device 30, a notification is sent that payment is possible at transaction processing device 30. In addition, the first transaction file is saved in second file area 3022, and payment in progress flag Fa becomes "1." Therefore, transaction processing device 30 allows the customer to pay by themselves. The customer then goes to the location where transaction processing device 30 is installed and performs the operation to pay.

[0144] On the other hand, as explained using Figure 14, if payment in progress flag Fa is "1" when payment button BAe or payment screen SAd is input, that is, if a customer is paying at transaction processing device 30, the first transaction file is output to reservation server 10. Also, reservation in progress flag Fb becomes "1", and first file area 3021 is cleared. At this point, it is not yet determined whether the customer will pay at transaction processing device 30 or at settlement device 40.

[0145] As explained with reference to Figures 13 and 14, when the first information processing is completed, first file area 3021 is cleared. Therefore, processor 301 of transaction processing device 30 can continue to start the first information processing. That is, when the next customer arrives at the checkout area and the store clerk issues a command to start registration, processor 301 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.

[0146] Here, the processor 301 executes the processes of ACT102 and ACT106 via the input device interface 310, thereby realizing the function of input information acquiring means 3011 (first input information acquiring means) that acquires information related to the purchased product input accepted by the input means 2011 from the input device 20. The processor 301 also executes the processes of ACT112 and ACT125 via the input device interface 310, thereby realizing the function of input information acquiring means 3011 (second input information acquiring means) that acquires the input end instruction signal accepted by the end accepting means 2012 from the input device 20. The processor 301 also executes the processes of ACT121 to ACT123 via the input device interface 310, thereby realizing the function of input information acquiring means 3011 (third input information acquiring means) that acquires information on the payment method accepted by the first payment accepting means 2013 from the input device 20.

[0147] The processor 301 executes the processes of ACT109 and ACT124 in cooperation with the touch panel 23 and the display 25, thereby realizing the function of first amount output means 3012. The processor 301 executes the processes of ACT145 to ACT148 in cooperation with the communication interface 305, thereby realizing the function of transaction information output means 3016. The processor 301 executes the process of ACT147 in cooperation with the employee memory 3026, thereby realizing the function of operator acquisition means 3015.

[0148] 15 is a flowchart showing the main steps of the second information processing executed by processor 301 of transaction equipment 30 in accordance with the first business program. Processor 301 executes the second information processing in parallel with the first information processing described above.

[0149] In ACT161, the processor 301 waits for the payment in progress flag Fa to become "1". When the payment in progress flag Fa becomes "1" in ACT138 of the first information processing, the processor 301 proceeds to ACT162. In ACT162, the processor 301 checks the payment status ST. If the payment status ST is "10", that is, if no payment method was selected in the first information processing, the processor 301 proceeds to ACT163. In ACT163, the processor 301 displays the payment method selection screen SCa (see FIG. 31) on the screen of the second touch panel 33.

[0150] Figure 31 is an example of a payment method selection screen SCa displayed on the second touch panel 33. 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 that displays the total purchase quantity and total sales amount of the purchased items in one transaction. The total area ACa displays the total purchase quantity and total sales amount calculated based on the product sales data of the purchased items stored in the second transaction file.

[0151] 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.

[0152] The processor 301, which has set the screen of the second touch panel 33 to the payment method selection screen SCa, proceeds to ACT164. In ACT164, the processor 301 waits for a payment method to be selected. When one of the payment methods is selected by a touch operation on the selection button group BCa, the processor 301 proceeds to ACT165. In ACT165, the processor 301 acquires the payment code of the selected payment method, similar to the processing in ACT123 of the first information processing.

[0153] On the other hand, if the payment status ST is "20" in ACT 162, that is, if a payment method was selected in the first information processing, the processor 301 proceeds to ACT 166. In ACT 166, the processor 301 extracts the payment code from the second transaction file.

[0154] After completing the processing of ACT165 or ACT166, the processor 301 proceeds to ACT167. In ACT167, the processor 301 displays the payment notification screen SCb (see FIG. 32) on the screen of the second touch panel 33. The payment notification screen SCb is a screen based on the payment code obtained by the processing of ACT165 or ACT166.

[0155] Fig. 32 is an example of the payment notification screen SCb displayed on the second touch panel 33. Fig. 32 shows the payment notification screen SCb when a cash payment code is obtained by processing ACT165 or ACT166. 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 35 (the so-called inserted amount), and the remaining amount after subtracting the inserted amount from the total amount.

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

[0157] The processor 301, having set the screen of the second touch panel 33 to the payment notification screen SCb, proceeds to ACT168. In ACT168, the processor 301 waits for payment to begin. For example, if cash payment is selected, the processor 301 waits for cash to be inserted into the automatic change dispenser 35. For example, if credit card payment is selected, the processor 301 waits for credit card data to be read by the cashless payment terminal 36. For example, if electronic money payment is selected, the processor 301 waits for electronic money data to be read by the cashless payment terminal 36. For example, if code payment payment is selected, the processor 301 waits for a barcode or two-dimensional data code for code payment to be read by the cashless payment terminal 36.

[0158] When payment of the price is initiated, processor 301 proceeds to ACT169. Processor 301 issues a transaction number in ACT169. The transaction number is, for example, a seven-digit number consisting of a three-digit transaction processing device ID and a four-digit serial number. The serial number is incremented by "1" each time a transaction is settled in transaction processing device 30. After issuing the transaction number, processor 301 proceeds to ACT170. In ACT170, processor 301 displays the payment in progress screen SCc (see Figure 33) on the screen of second touch panel 33.

[0159] FIG. 33 is an example of the payment in progress screen SCc displayed on the second touch panel 33. FIG. 33 shows the payment in progress screen SCc when a cash payment code is obtained by processing ACT165 or ACT166. The payment in progress screen SCc has the same layout as the payment notification screen SCb. On the 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 35. The payment in progress screen SCc also includes a checkout button BCb. The checkout button BCb is a software key. The checkout button BCb is an operator for issuing a command to complete payment. When the customer has finished paying using the selected payment method, they touch the checkout button BCb.

[0160] Having changed the screen of the second touch panel 33 to the payment in progress screen SCc, the processor 301 proceeds to ACT171. In ACT171, the processor 301 waits for the checkout button BCb to be input. When the checkout button BCb is input by a touch operation, the processor 301 proceeds to ACT172. In ACT172, the processor 301 executes the settlement process of the transaction based on the payment code. That is, if the payment code is a cash payment code, the processor 301 executes the settlement process of the transaction with the cash inserted into the automatic change dispenser 35. If the payment code is a credit card payment code, the processor 301 executes the settlement process of the transaction with the credit card data read by the cashless payment terminal 36. If the payment code is an electronic money payment code, the processor 301 executes the settlement process of the transaction with the electronic money data read by the cashless payment terminal 36. If the payment code is a code payment code, the processor 301 executes the transaction settlement process using the barcode or two-dimensional data code read by the cashless payment terminal 36. These settlement processes are all well known, so detailed explanations will be omitted.

[0161] When the payment process is complete, the processor 301 proceeds to ACT 173. In ACT 173, the processor 301 drives the printer 34 to print a receipt. In ACT 174, the processor 301 displays the payment completion screen SCd (see FIG. 34) on the screen of the second touch panel 33. The receipt is a sheet that records details of the purchased items, such as the product name, price, quantity, and amount. The receipt also records the transaction date, time, transaction number, etc.

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

[0163] After displaying the payment completion screen SCd, the processor 301 proceeds to ACT 175. In ACT 175, the processor 301 saves the data of the second transaction file, that is, the data of the products purchased by the customer who has completed payment. The data is saved in, for example, the auxiliary storage device 303. The data may also be saved in the main memory 302. Alternatively, the second transaction file may be sent to the POS server via the communication interface 305 and saved in the POS server. The data may also be saved in the reservation server 10 instead of the POS server.

[0164] After saving the data of the second transaction file, the processor 301 proceeds to ACT 176. In ACT 176, the processor 301 clears the second file area 3022. In ACT 177, the processor 301 rewrites the payment in progress flag Fa to "0". With this, the processor 301 ends the second information processing.

[0165] Here, the processor 301 executes the processing of ACT167 in cooperation with the second touch panel 33, thereby realizing the function of first amount output means 3012. The processor 301 executes the processing of ACT163 to ACT165 in cooperation with the second touch panel 33, thereby realizing the function of second payment acceptance means 3013. The processor 301 executes the processing of ACT172, thereby realizing the function of first settlement means 3014.

[0166] 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 301 executes the processing of ACT 162 through ACT 177. Through the operation of transaction processing device 30 based on this processing, the customer can settle the transaction by operating transaction processing device 30 themselves to pay the price.

[0167] 16 is a flowchart showing the main steps of the third information processing executed by processor 301 of transaction equipment 30 in accordance with the first business program. Processor 301 also executes the third information processing in parallel with the first information processing described above.

[0168] In ACT 181, the processor 301 waits for the pending flag Fb to become "1". When the pending flag Fb becomes "1" in ACT 149 of the first information processing, the processor 301 proceeds to ACT 182. In ACT 182, the processor 301 displays the guidance screen SDa (see FIG. 35) on the screen of the first touch panel 32.

[0169] 35 is an example of guidance screen SDa displayed on first touch panel 32. Guidance screen SDa displays a pop-up PUc that displays guidance for guiding a customer to payment device 40 and guidance for making transaction processing device 30 the payment destination, along with a release hold button BDa. Release hold button BDa is a second operator that instructs hold server 10 to release the hold of the transaction file and send the transaction file to transaction processing device 30.

[0170] After checking guidance screen SDa, the store clerk determines the payment recipient for the customer whose transaction file is on hold in hold server 10. For example, if another customer is paying at transaction processing device 30 but no customer is paying at payment device 40, the store clerk determines payment device 40 as the payment recipient. For example, if another customer is still paying at payment device 40 but the customer who was paying at transaction processing device 30 has finished paying, the store clerk determines transaction processing device 30 as the payment recipient.

[0171] Here, in order to clarify the operation of the store clerk who has been selected as the payment recipient, we will temporarily suspend the explanation of Figure 16 and first explain the information processing performed by processor 101 of reservation server 10 using Figures 17 and 18.

[0172] 17 and 18 are flowcharts showing the main steps of the fourth information processing executed by processor 101 of reservation server 10 in accordance with the second business program. Processor 101 waits for a reservation event in ACT201. Upon receiving the reservation event via communication interface 105, processor 101 proceeds to ACT202. Processor 101 returns an acceptance response in ACT202. That is, processor 101 returns the acceptance response to transaction equipment 30 identified by the transaction equipment ID included in the reservation event.

[0173] As explained using FIG. 14, when processor 301 of transaction processing device 30 that sent the hold event receives the acceptance response, it outputs the transaction file stored in the first file area (first transaction file) to hold server 10 along with the employee code, which is operator identification information. Then, processor 101 that returned the acceptance response waits for the transaction file in ACT 203. Upon receiving the transaction file via communication interface 105, processor 101 proceeds to ACT 204. In ACT 204, processor 101 obtains the transaction processing device ID set for transaction processing device 30 that sent the data. The transaction processing device ID is included in the hold event.

[0174] Having detected the transaction processing device ID, processor 101 proceeds to ACT205. In ACT205, processor 101 acquires the employee code received along with the transaction file. Then, in ACT206, processor 101 stores the employee code in lane table 1032. That is, processor 101 writes the employee code acquired in ACT205 in column Ce of lane table 1032 in the same row as the transaction processing device ID acquired in ACT204.

[0175] Having stored the employee code, processor 101 proceeds to ACT 207. Processor 101 saves the transaction file received from transaction processing device 30 in employee-specific folder 1033 identified by the employee code acquired in ACT 207. Processor 101 also references lane table 1032 in ACT 208 to acquire the instruction device ID described in column Cd of the same row as the transaction processing device ID. Processor 101 then outputs a signal indicating instruction validation to instruction device 50 identified by the instruction device ID in ACT 209. The signal indicating instruction validation is transmitted to instruction device 50 via settlement device 40. The signal indicating instruction validation is a signal that enables the functions of instruction device 50 as reception means 5011 and instruction means 5012. Hereinafter, the transaction file saved in employee-specific folder 1033 will be referred to as the third transaction file.

[0176] The instruction device 50 normally displays an instruction screen SEa (see FIG. 36) on the touch panel 505. FIG. 36 is a display example of the instruction screen SEa. The instruction screen SEa has a pull-down area AEa in which the names of each store clerk are displayed as a pull-down menu. The instruction screen SEa also has a call button BEa. The call button BEa is a software key. The call button BEa is a first operator that instructs the payment device 40 to send a transaction file.

[0177] The call button BEa is normally disabled for input. For example, the call button BEa is grayed out and cannot be input. When the instruction device 50 receives a signal indicating instruction validation from the reservation server 10, it puts the call button BEa into an input-enabled state and validates input of the call button BEa. The instruction device 50 that displays such an instruction screen SEa realizes the function of the reception means 5011. Note that the information displayed in the pull-down area AEa may be an employee code instead of a name. Alternatively, it may be both a name and an employee code.

[0178] A store clerk who signs on to transaction processing device 30 as the operator of input device 20 operates pull-down area AEa to select his or her own name from the pull-down menu. By performing this operation, the employee code of the store clerk is overwritten and saved in employee memory 5031. Note that this operation may be performed immediately after the store clerk signs on, or at any time thereafter.

[0179] Furthermore, the store clerk who has decided on the payment destination operates instruction device 50 or transaction processing device 30 based on that decision. Specifically, the store clerk who has decided on payment device 40 as the payment destination presses call button BEa on instruction device 50. When call button BEa is pressed, an instruction is received from instruction device 50 and a first signal is output from payment device 40. The first signal output from payment device 40 is transmitted to holding server 10. The first signal is a signal output in response to input of call button BEa. The first signal is a signal indicating that payment device 40 has been decided as the payment destination. The first signal includes an employee code stored in employee memory 5031. Instruction device 50 that outputs the first signal realizes the function of instruction means 5012.

[0180] On the other hand, a store clerk who has decided that transaction processing device 30 is the payment destination presses hold release button BDa. When hold release button BDa is pressed, a second signal is output from transaction processing device 30 to hold server 10. The second signal is a signal output in response to the pressing of hold release button BDa. The second signal is a signal indicating that transaction processing device 30 has been selected as the payment destination. The second signal includes an employee code stored in employee memory 3026.

[0181] After outputting the signal indicating the instruction is validated, the processor 101 proceeds to ACT211 in Fig. 18. The processor 101 checks whether the call button BEa has been pressed in ACT211. If the call button BEa has not been pressed, i.e., if the first signal has not been received, the processor 101 proceeds to ACT212. The processor 101 checks whether the hold release button BDa has been pressed in ACT212. If the hold release button BDa has not been pressed, i.e., if the second signal has not been received, the processor 101 returns to ACT211. In this way, the processor 101 waits in ACT211 and ACT212 for the call button BEa on the instruction screen SEa to be pressed or the hold release button BDa on the guidance screen SDa to be pressed.

[0182] In the standby state of ACT211 and ACT212, when processor 101 receives an instruction from instruction device 50 and a first signal output from payment device 40, processor 101 recognizes that call button BEa has been pressed. Processor 101 proceeds to ACT213. In ACT213, processor 101 refers to lane table 1032 and obtains the payment device ID written in column Cc of the same row as the transaction processing device ID. Then, in ACT214, processor 101 transmits an execution event to payment device 40 identified by that payment device ID. The execution event is an event that requests the execution of payment processing.

[0183] Details will be explained later using Figure 19, but upon receiving the execution event, the payment device 40 returns an approval response or a negative response. An approval response is returned if the payment device 40 is able to settle the transaction. A negative response is returned if the payment device 40 is unable to settle the transaction.

[0184] After transmitting the execution event, processor 101 proceeds to ACT215. In ACT215, processor 101 checks whether an acceptance response has been received. If an acceptance response has been received, processor 101 proceeds to ACT216. In ACT216, processor 101 acquires the employee code from the first signal. Processor 101 may also refer to lane table 1032 and acquire the employee code written in column Ce of the same row as the transaction processing device ID acquired in the processing of ACT204.

[0185] Having acquired the employee code, the processor 101 selects the employee folder 1033 for that employee code in ACT217. Then, the processor 101 transmits the third transaction file held in the selected employee folder 1033 to the settlement device 40 in ACT218. That is, the processor 101 transmits the third transaction file stored in the employee folder 1033 for the employee code acquired in ACT216 to the settlement device 40 identified by the settlement device ID acquired in the processing of ACT213.

[0186] After sending the transaction file, processor 101 proceeds to ACT219. In ACT219, processor 101 sends a release notification event to transaction processing device 30, the sender of the third transaction file. That is, processor 101 sends a release notification event to transaction processing device 30 identified by the transaction processing device ID acquired in the processing of ACT204. The release notification event is an event that notifies that the hold state has been released.

[0187] After sending the release notification event, the processor 101 proceeds to ACT 220. In ACT 220, the processor 101 deletes the third transaction file. That is, the processor 101 deletes the third transaction file that was saved in the employee folder 1033 selected in ACT 217. With this, the processor 101 ends the fourth information processing.

[0188] On the other hand, when processor 101 receives a second signal from transaction processing device 30 in the standby state of ACT211 and ACT212, it recognizes that the hold release button BDa has been pressed. Processor 101 proceeds to ACT221. In ACT221, processor 101 acquires the employee code from the second signal. Processor 101 may also refer to lane table 1032 and acquire the employee code written in column Ce of the same row as the transaction processing device ID acquired in the processing of ACT204.

[0189] Having acquired the employee code, processor 101 selects employee folder 1033 for that employee code in ACT222. Then, processor 101 transmits the third transaction file held in employee folder 1033 selected in ACT223 to transaction processing device 30. That is, processor 101 transmits the third transaction file saved in employee folder 1033 selected in ACT222 to transaction processing device 30 identified by the transaction processing device ID acquired in the processing of ACT204.

[0190] After transmitting the third transaction file, the processor 101 proceeds to ACT 224. The processor 101 deletes the third transaction file in ACT 224. That is, the processor 101 deletes the third transaction file that was saved in the employee folder 1033 selected in ACT 222. With this, the processor 101 ends the fourth information processing.

[0191] If a negative response is received in ACT215, the processor 101 proceeds to ACT225. In ACT225, the processor 101 outputs an error signal to the instruction device 50. Upon receiving the error signal, the instruction device 50 displays an error screen on the screen of the touch panel 505. An operator (software key) for issuing a command to clear the error is displayed on the error screen.

[0192] The store clerk, having checked the error screen, inputs an operator to command the cancellation of the error. When this operator is input, an error cancellation signal is output from the instruction device. The error cancellation signal is transmitted to the reservation server 10 via the settlement device 40. The screen of the touch panel 505 also returns to the instruction screen SEa.

[0193] After outputting the error signal, the processor 101 proceeds to ACT 226. The processor 101 waits for an error clear signal in ACT 226. When the processor 101 receives the error clear signal via the communication interface 105, the processor 101 returns to the standby state in ACT 211 and ACT 212.

[0194] For example, a store clerk may press the call button BEa to designate payment device 40 as the output destination for transaction-related information, but the previous customer has not yet completed payment at payment device 40. In such a case, the display of instruction device 50 will display an error screen, and the store clerk must press an operator to clear the error. This causes the display of instruction device 50 to return to instruction screen SEa, so the store clerk can wait for the previous customer to complete payment before pressing the call button BEa. Alternatively, if the customer who was making a payment at transaction processing device 30 completes the payment first, the store clerk can press the hold release button BDa.

[0195] Here, the processor 101 realizes the function of transaction information input means 1011 by executing the processes of ACT201 and ACT203 in cooperation with the communication interface 105. The processor 101 realizes the function of hold means 1012 by executing the processes of ACT204 to ACT207 in cooperation with the employee folder 1033. The processor 101 realizes the function of output destination recognition means 1013 by executing the processes of ACT211 and ACT212 in cooperation with the communication interface 105. The processor 101 realizes the function of operator recognition means 1014 by executing the processes of ACT216 and ACT221 in cooperation with the lane table 1032. The processor 101 realizes the function of hold information output means 1015 by executing the processes of ACT217 and ACT218 and the processes of ACT222 and ACT223 in cooperation with the communication interface 105.

[0196] In this way, the transaction file (first transaction file) output from transaction processing device 30 to holding server 10, i.e., the transaction-related information, is stored, i.e., held, in employee-specific folder 1033 in holding server 10 for each clerk standing in settlement lane L. When the clerk presses call button BEa on instruction device 50, a first signal is transmitted from instruction device 50 to settlement device 40. In response to this first signal, the transaction file (third transaction file) held in holding server 10 is transmitted to settlement device 40. At this time, a release notification event is transmitted from holding server 10 to transaction processing devices 30 in the same settlement lane L. On the other hand, when the clerk presses hold release button BDa on transaction processing device 30, a hold release event is transmitted from transaction processing device 30 to settlement device 40. In response to this hold release event, the transaction file (third transaction file) held in holding server 10 is transmitted to transaction processing device 30.

[0197] Returning to the explanation of FIG. After controlling the display of the guidance screen SDa in ACT182, the processor 301 proceeds to ACT183. The processor 301 checks whether a release notification event has been received in ACT183. If a release notification event has not been received, the processor 301 proceeds to ACT184. The processor 301 checks whether the hold release button BDa has been pressed in ACT184. If the hold release button BDa has not been pressed, the processor 301 returns to ACT183. In this way, the processor 301 waits in ACT183 and ACT184 for a release notification event to be received or for the hold release button BDa to be pressed.

[0198] As described with reference to FIGS. 17 and 18, when the call button BEa is pressed on the instruction screen SEa displayed on the instruction device 50 and the transaction file (third transaction file) that has been reserved in the reservation server 10 is output to the payment device 40, a release notification event is transmitted from the reservation server 10 to the transaction processing device 30. When the processor 301 receives the release notification event in the standby state of ACT183 and ACT184, the processor 301 proceeds to ACT185. In ACT185, the processor 301 displays a pop-up PUd (see FIG. 37) on the subscreen SAb or payment screen SAd of the touch panel 23 to guide the customer to make payment at the payment device 40. The processor 301 also displays text TXd (see FIG. 38) on the subscreen SBb of the display 25 to instruct the customer to make payment at the payment device 40.

[0199] 37 is an example of a pop-up PUd displayed on the payment screen SAd of the touch panel 23. Upon seeing the pop-up PUd, the store clerk guides the customer to the payment device 40.

[0200] 38 is an example of the text TXd displayed on the small screen SBb of the display 25. After checking the text TXd, the customer follows the instructions of the store clerk to go to the payment device 40 and make the payment.

[0201] After completing the process in ACT 185, the processor 301 sets the pending flag Fb to "0" in ACT 186. This completes the third information processing by the processor 301.

[0202] On the other hand, if the hold release button BDa is pressed during the standby state of ACT183 and ACT184, processor 301 proceeds to ACT187. In ACT187, processor 301 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 30, processor 301 returns to ACT183. Processor 301 invalidates the input of the hold release button BDa and returns to the standby state of ACT183 and ACT184.

[0203] If the payment in progress flag Fa is "0" in ACT187, that is, if there is no customer making a payment at transaction processing device 30, processor 301 proceeds to ACT188. Processor 301 obtains an employee code from employee memory 3026 in ACT188. Then, processor 301 sends a hold release event to hold server 10 in ACT189. The hold release event includes the employee code obtained from employee memory 3026.

[0204] As described with reference to FIG. 18, upon receiving a hold release event from transaction processing device 30, holding server 10 transmits the transaction file (third transaction file) that it had been holding to transaction processing device 30. Processor 301, which transmitted the hold release event, waits to receive the transaction file in ACT 190. Upon receiving the transaction file via communication interface 305, processor 301 proceeds to ACT 191. Processor 301 saves the transaction file in second file area 3022 in ACT 191. The received transaction file is the transaction file output to holding server 10 in ACT 148 of FIG. 14. Hereinafter, the transaction file received from holding server 10 and saved in second file area 3022 will be referred to as the fourth transaction file.

[0205] After saving the fourth transaction file in second file area 3022, processor 301 proceeds to ACT 192. In ACT 192, processor 301 displays a pop-up PUb (see FIG. 29) on the subscreen SAb or payment screen SAd of touch panel 23 to notify the user that payment is possible at transaction processing device 30. Processor 301 also displays text TXb (see FIG. 30) on the subscreen SBb of display 25 to indicate that payment is possible.

[0206] In this way, having notified using touch panel 23 and display 25 that payment at transaction processing device 30 is possible, processor 301 proceeds to ACT 193. In ACT 193, processor 301 sets payment in progress flag Fa to "1" and sets pending flag Fb to "0". Thereafter, processor 301 proceeds to ACT 162 in Figure 15. Processor 301 then executes the processes of ACT 162 to ACT 177 in the same manner as described above.

[0207] When the transaction file held in reservation server 10 is returned to transaction processing device 30 in this manner, processor 301 of transaction processing device 30 executes the processing of ACT162 to ACT177 of FIG. 15 in the same manner as described above. Specifically, processor 301 displays payment notification screen SCb on the screen of second touch panel 33. If no payment method has been selected on input device 20, processor 301 displays payment method selection screen SCa before payment notification screen SCb. When a payment method is selected by the customer's operation, processor 301 displays payment notification screen SCb. When payment is initiated, processor 301 displays payment in progress screen SCc on the screen of second touch panel 33. Processor 301 also issues a transaction number. When the customer presses checkout button BCb on payment in progress screen SCc, processor 301 executes settlement processing and issues a receipt. Processor 301 also displays payment completion screen SCd on the screen of second touch panel 33. Thus, the customer can settle the transaction by operating transaction processing device 30 himself / herself and paying the price.

[0208] Here, the processor 301 executes the processing of ACT185 and ACT192 in cooperation with the touch panel 23 and the display 25, thereby realizing the function of guidance means 3017. The processor 301 executes the processing of ACT184 to ACT189, thereby realizing the function of hold release means 3018. The processor 301 executes the processing of ACT190 to ACT193 and the subsequent processing of ACT162 to ACT172, thereby realizing the function of execution means 3019.

[0209] 19 is a flowchart showing the main steps of the fifth information processing executed in accordance with the third business program by the processor 401 of the settlement apparatus 40. The processor 401 waits for an execution event as ACT301.

[0210] As explained using FIG. 18 , when a transaction file is reserved in the employee-specific folder 1033 of the reservation server 10, if the call button BEa on the instruction screen SEa displayed on the instruction device 50 is pressed to instruct the payment device 40 as the output destination of transaction-related information, an execution event is sent from the reservation server 10 to the payment device 40 as processing in ACT214. When the processor 401 receives the execution event, the processor 401 proceeds to ACT302. In ACT302, the processor 401 checks the payment in progress flag Fc. 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 40, the processor 401 proceeds to ACT303. In ACT303, the processor 401 transmits a negative response signal to the reservation server 10. With this, the processor 401 ends the fifth information processing.

[0211] On the other hand, if the payment in progress flag Fc is "0" in ACT 302, that is, if the customer has not made a payment at the payment device 40, the processor 401 proceeds to ACT 304. In ACT 304, the processor 301 transmits an approval response signal to the reservation server 10.

[0212] As explained using FIG. 18, upon receiving an acceptance response from the payment device 40 that sent the execution event, the holding server 10 transmits the transaction file (third transaction file) that was on hold to that payment device 40. Then, the processor 401 that sent the acceptance response signal waits to receive the transaction file in ACT 305. Upon receiving the transaction file via the communication interface 405, the processor 401 proceeds to ACT 306. In ACT 306, the processor 401 saves the transaction file in the third file area 4021. Incidentally, the transaction file is the transaction file that was stored in the first file area 3021 of the transaction processing device 30 installed in the same settlement lane L and output to the holding server 10. Hereinafter, the transaction file saved in the third file area 4021 will be referred to as the fifth transaction file.

[0213] After saving the fifth transaction file in the third file area 4021, the processor 401 proceeds to ACT 307. In ACT 307, the processor 401 sets the payment in progress flag Fc to “1.” With this, the processor 401 ends the fifth information processing.

[0214] In this way, when processor 401 of settlement device 40 receives an execution event from reservation server 10 while payment in progress flag Fc is "0," i.e., while the customer has not yet made a payment, processor 401 subsequently imports the transaction file output from reservation server 10 and saves it in third file area 4021. Processor 401 also sets payment in progress flag Fc to "1."

[0215] Here, the processor 401 cooperates with the communication interface 405 to execute the processes of ACT305 and ACT306, thereby realizing the function of the capture means 4011.

[0216] 20 is a flowchart showing the main steps of the sixth information processing executed by processor 401 of settlement device 40 according to the third business program. Processor 401 executes the sixth information processing in parallel with the fifth information processing described above.

[0217] The processor 401 waits for the payment in progress flag Fc to become "1" in ACT 311. When the payment in progress flag Fc becomes "1" in ACT 307 of the fifth information processing, the processor 401 proceeds to ACT 312. In ACT 312, the processor 401 displays the statement confirmation screen SFa (see FIG. 39) on the screen of the touch panel 41.

[0218] FIG. 39 is an example of a statement confirmation screen SFa displayed on the touch panel 41. The statement confirmation screen SFa is divided into a statement area AFa and a total area AFb. The statement area AFa is an area that displays, in numerical order, the product names, purchase quantities, unit prices, discount amounts, and sales amounts of the purchased products in one transaction in list format. The total area AFb is an area that displays the total purchase quantities and total sales amounts of the purchased products in one transaction. Based on the product sales data of the fifth transaction file stored in the third file area 4021, the processor 401 causes the statement area AFa to display the product names, purchase quantities, unit prices, discount amounts, and sales amounts of the purchased products in one transaction. Based on the product sales data, the processor 401 also causes the total area AFb to display the total purchase quantities and total sales amounts of the purchased products.

[0219] The statement confirmation screen SFa includes a confirmation button BFa and a store clerk call button BFb. The confirmation button BFa and the store clerk call button BFb are software keys. The confirmation button BFa is an operator that indicates that the customer has confirmed that the details of the purchased items are displayed on the statement confirmation screen SFa. The store clerk call button BFb is an operator that indicates that the customer wants to call a store clerk.

[0220] After displaying the statement confirmation screen SFa, the processor 401 proceeds to ACT 313. In ACT 313, the processor 401 waits for the confirmation button BFa to be pressed. When the confirmation button BFa is pressed, the processor 401 proceeds to ACT 314. In ACT 314, the processor 401 checks whether a payment code is included in the transaction file saved in the third file area 4021. If a payment code is included, the processor 401 proceeds to ACT 315. In ACT 315, the processor 401 extracts the payment code from the transaction file.

[0221] On the other hand, if the payment code is not included, the processor 401 proceeds to ACT 316. In ACT 316, the processor 401 displays the payment method selection screen SFb (see FIG. 40) on the screen of the touch panel 41.

[0222] Figure 40 is an example of a payment method selection screen SFb displayed on the touch panel 41. The payment method selection screen SFb includes a group of selection buttons BFc for each payment method. The group of selection buttons BFc includes a cash button, a credit button, an electronic money button, and a code payment button. The payment method selection screen SFb also includes a total area AFc that displays the total purchase quantity and total sales amount of the purchased items in one transaction. The total area AFc displays the total purchase quantity and total sales amount calculated based on the product sales data in the fifth transaction file. The payment method selection screen SFb also displays a store clerk call button BFb, allowing the customer to call a store clerk.

[0223] After checking the payment method selection screen SFb, 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 BFc. For example, a customer who wishes to pay by credit card touches the credit button in selection button group BFc. For example, a customer who wishes to pay by electronic money touches the electronic money button in selection button group BFc. For example, a customer who wishes to pay by code payment touches the code payment button in selection button group BFc. As mentioned above, the information relating to the transaction held in the holding server 10 does not necessarily need to include the payment method accepted by the first payment accepting means 2013. Therefore, in the case of an operation in which the information relating to the transaction does not include the payment method accepted by the first payment accepting means 2013, the processing steps of ACT314 and ACT315 may be omitted.

[0224] The processor 401, having set the screen of the touch panel 41 to the payment method selection screen SFb, proceeds to ACT 317. In ACT 317, the processor 401 waits for a payment method to be selected. When one of the payment methods is selected by a touch operation on the selection button group BFc, the processor 401 proceeds to ACT 318. In ACT 318, the processor 401 acquires the payment code of the selected payment method, similar to the processing in ACT 123 of the first information processing.

[0225] After completing the processing of ACT315 or ACT318, the processor 401 proceeds to ACT319. In ACT319, the processor 401 displays the payment notification screen SFc (see FIG. 41) on the screen of the touch panel 41. The payment notification screen SFc is a screen based on the payment code obtained by the processing of ACT315 or ACT318.

[0226] FIG. 41 is an example of a payment notification screen SFc displayed on the touch panel 41. FIG. 41 shows the payment notification screen SFc when a cash payment code is obtained by processing ACT315 or ACT318. The payment notification screen SFc includes a total area AFc similar to the payment method selection screen SFb. The payment notification screen SFc also includes a change machine information area AFd. The change machine information area AFd displays the total amount, the total amount of cash inserted into the automatic change machine 43 (i.e., the inserted amount), and the remaining amount after subtracting the inserted amount from the total amount. The payment notification screen also displays a store clerk call button BFb, allowing the customer to call a store clerk.

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

[0228] After the processor 401 sets the screen of the touch panel 41 to the payment notification screen SFc, the processor 401 proceeds to ACT320. In ACT320, the processor 401 waits for payment to begin. For example, if cash payment is selected, the processor 401 waits for cash to be inserted into the automatic change dispenser 43. For example, if credit card payment is selected, the processor 401 waits for credit card data to be read by the cashless payment terminal 44. For example, if electronic money payment is selected, the processor 401 waits for electronic money data to be read by the cashless payment terminal 44. For example, if code payment payment is selected, the processor 401 waits for a barcode or two-dimensional data code for code payment to be read by the cashless payment terminal 44.

[0229] When payment of the price is initiated, the processor 401 proceeds to ACT321. The processor 401 issues a transaction number in ACT321. 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 40. After issuing the transaction number, the processor 401 proceeds to ACT322. In ACT322, the processor 401 displays the payment in progress screen SFd (see Figure 42) on the screen of the touch panel 41.

[0230] FIG. 42 is an example of the payment in progress screen SFd displayed on the touch panel 41. FIG. 42 shows the payment in progress screen SFd when a cash payment code is obtained by processing ACT315 or ACT318. The payment in progress screen SFd is a screen in which a checkout button BFd is added to the payment notification screen SCb. On the payment in progress screen SCc, the information displayed in the change machine information area AFd is updated according to the amount of cash inserted into the automatic change machine 43. The checkout button BFd is a software key. The checkout button BFd is an operator for issuing a command to complete payment. When a customer has finished paying using the selected payment method, they touch the checkout button BFd. The store clerk call button BFb remains displayed on the payment in progress screen SFd, allowing the customer to call a store clerk.

[0231] The processor 401, having set the screen of the touch panel 41 to the payment in progress screen SFd, proceeds to ACT 323. In ACT 323, the processor 401 waits for the checkout button BFd to be pressed. When the checkout button BFd is pressed by a touch operation, the processor 401 proceeds to ACT 324. In ACT 324, the processor 401 executes the settlement process for the transaction based on the payment code. That is, if the payment code is a cash payment code, the processor 401 executes the settlement process for the transaction using the cash inserted into the automatic change dispenser 43. If the payment code is a credit card payment code, the processor 401 executes the settlement process for the transaction using the credit card data read by the cashless payment terminal 44. If the payment code is an electronic money payment code, the processor 401 executes the settlement process for the transaction using the electronic money data read by the cashless payment terminal 44. If the payment code is a code payment code, the processor 401 executes the transaction settlement process using the barcode or two-dimensional data code read by the cashless payment terminal 44. These settlement processes are all well known, so detailed explanations will be omitted.

[0232] Upon completing the payment process, processor 401 proceeds to ACT 325. In ACT 325, processor 401 drives printer 42 to issue a receipt. In ACT 326, processor 401 displays payment completion screen SFe (see FIG. 43) on touch panel 41. The receipt is the same as the receipt issued by transaction processing device 30 in the processing of ACT 173. However, while a transaction number including the transaction processing device ID is printed on a receipt issued by transaction processing device 30, a transaction number including the payment device ID is printed on a receipt issued by payment device 40.

[0233] FIG. 43 is an example of the payment completion screen SFe displayed on the touch panel 41. FIG. 43 shows the payment completion screen SFe when a cash payment code is obtained by processing ACT315 or ACT318. The payment completion screen SFe includes a change machine information area AFd, which is similar to the payment notification screen SFc and the payment in progress screen SFd. The information displayed in the change machine information area AFd lets the store clerk know that the payment of a customer who selected cash payment has been completed. Note that a customer who has completed payment does not call a store clerk, so the store clerk call button BFb is not displayed on the payment completion screen SFe. After checking the payment completion screen SFe, the customer takes the receipt and leaves the store.

[0234] After displaying the payment completion screen SFe, the processor 401 proceeds to ACT327. In ACT327, the processor 401 saves the data of the fifth transaction file stored in the third file area 4021, that is, the data of the products purchased by the customer who has completed payment. The data is saved in, for example, the auxiliary storage device 403. The data may also be saved in the main memory 402. Alternatively, the fifth transaction file may be sent to the POS server via the communication interface 405 and saved in the POS server. The data may also be saved in the reservation server 10 instead of the POS server.

[0235] After saving the data of the fifth transaction file, the processor 401 proceeds to ACT 328. In ACT 328, the processor 401 clears the third file area 4021. In ACT 329, the processor 401 sets the payment in progress flag Fc to "0." With this, the processor 401 ends the sixth information processing.

[0236] In this way, when the transaction file (third transaction file) that was reserved in the reservation server 10 is imported into the payment device 40, the processor 401 of the payment device 40 executes the processes of ACT312 to ACT329 in FIG. 20. That is, the processor 401 changes the screen of the touch panel 41 to the statement confirmation screen SFa. Then, when the customer operates the confirmation button BFa, the processor 401 changes the screen of the touch panel 41 to the payment notification screen SFc. If no payment method has been selected on the input device 20, the processor 401 displays the payment method selection screen SFb before the payment notification screen SFc. Then, when the customer operates the payment method, the processor 401 changes the screen of the touch panel 41 to the payment notification screen SFc. Thereafter, when payment is started, the processor 401 changes the screen of the touch panel 41 to the payment in progress screen SFd. The processor 401 also issues a transaction number. When the customer presses the checkout button BFd on the payment screen SFd, the processor 401 executes the payment process and issues a receipt. The processor 401 also displays the payment completion screen SFe on the touch panel 41. The customer can then operate the payment device 40 themselves to pay the price, thereby settling the transaction.

[0237] Here, the processor 401 executes the processing of ACT316 in cooperation with the touch panel 41, thereby realizing the function of third payment acceptance means 4013. The processor 401 executes the processing of ACT319 in cooperation with the touch panel 41, thereby realizing the function of second amount output means 4012. The processor 401 executes the processing of ACT324, thereby realizing the function of second payment means 4014.

[0238] [Explanation of payment system operation] Next, the operation of the settlement system 100 that operates as described above will be described with reference to the sequence diagrams of FIGS. In Figure 44, the clerk begins a transaction with the first customer, A. That is, the clerk operates input device 20 to register the purchased items of customer A (item registration A). Once the purchased items are registered, transaction processing device 30 creates transaction file A. After completing the registration of the purchased items, the clerk presses payment button BAe or payment button BAh (payment input A). Transaction processing device 30 determines whether the transaction can be settled. At this point, the transaction can be settled, so transaction processing device 30 saves transaction file A in second file area 3022. Customer A goes to the location where transaction processing device 30 is installed and begins paying the price (payment start A).

[0239] The clerk begins a transaction with the second customer, B. That is, the clerk operates input device 20 to register the purchased items of customer B (item registration B). Once the purchased items are registered, transaction processing device 30 creates transaction file B. After completing the registration of the purchased items, the clerk presses payment button BAe or payment button BAh (payment input B). Transaction processing device 30 determines whether the transaction can be settled. If customer A has not completed payment at this point, the transaction cannot be settled. Transaction processing device 30 transmits transaction file B to holding server 10. Holding server 10 saves transaction file B. As transaction file B is transmitted to holding server 10, guidance screen SDa is displayed on first touch panel 32 of transaction processing device 30, and the clerk presses call button BEa displayed on touch panel 505 of instruction device 50. When call button BEa is pressed, a first signal is sent from settlement device 40 to holding server 10 in response to an instruction from instruction device 50. Upon receiving this first signal, the reservation server 10 transmits transaction file B to the payment device 40. The payment device 40 stores transaction file B in the third file area 4021. Customer B moves to the location where the payment device 40 is installed and starts paying the price (payment start B).

[0240] The clerk begins the transaction with the third customer C. That is, the clerk operates input device 20 to register the purchased items of customer C (item registration C). Once the purchased items are registered, transaction processing device 30 creates transaction file C. Once registration of the purchased items is complete, the clerk presses payment button BAe or payment button BAh (payment input C). Transaction processing device 30 determines whether settlement of the transaction is possible. At this point, if customer A has completed payment, transaction processing device 30 saves transaction file C in second file area 3022. Customer C proceeds to the location where transaction processing device 30 is installed and begins payment (payment start C).

[0241] The clerk begins the transaction with the fourth customer, D. That is, the clerk operates input device 20 to register the purchased items of customer D (item registration D). Once the purchased items are registered, transaction processing device 30 creates transaction file D. After completing the registration of the purchased items, the clerk presses payment button BAe or payment button BAh (payment input D). Transaction processing device 30 determines whether or not payment for the transaction is possible. If, at this point, neither customer B nor customer C has completed payment, information indicating that payment is not possible is displayed on touch panel 23 and display 25 of input device 20. Customer D waits until payment is possible.

[0242] Here, if customer C's payment is completed first, transaction equipment 30 saves transaction file D in second file area 3022. Customer D moves to the location where transaction equipment 30 is installed and starts paying the price (payment start Da).

[0243] In contrast, as shown in FIG. 45, if customer B's payment is completed first, transaction processing device 30 transmits transaction file D to reservation server 10. Reserve server 10 saves transaction file D. Also, since call button BEa on instruction screen SEa displayed on touch panel 505 of instruction device 50 becomes active, the store clerk presses call button BEa. When call button BEa is pressed, a first signal is sent from payment device 40 to reservation server 10 in response to an instruction from instruction device 50. In response to this first signal, transaction file D is sent from reservation server 10 to payment device 40. Payment device 40 saves transaction file D in third file area 4021. Customer D proceeds to the location where payment device 40 is installed and starts paying the price (payment start Db).

[0244] On the other hand, as shown in FIG. 46, if customer B completes payment first, but customer C then completes payment shortly thereafter, and transaction processing device 30 becomes available, the store clerk may press release hold button BDa on guidance screen SDa displayed on first touch panel 32. When release hold button BDa is pressed, a second signal is sent from transaction processing device 30 to reservation server 10. In response to this second signal, reservation server 10 sends transaction file D to transaction processing device 30. Transaction processing device 30 saves transaction file D in second file area 2022. Customer D proceeds to the location where transaction processing device 30 is installed and begins payment (payment start Dc).

[0245] Because payment system 100 operates as described above, transaction processing device 30 and payment device 40 can be selected as needed to efficiently handle a large number of customers. Furthermore, because customers themselves perform the payment process, labor costs can be reduced. Furthermore, because store clerks do not have to handle cash, cash cards, etc., this system also has an excellent effect in terms of infection control.

[0246] [Payment system layout] 2 shows the layout of input device 20, transaction processing device 30, settlement device 40, and instruction device 50 provided in one settlement lane L, but the layout is not limited to this. Next, several layout patterns will be explained using FIGS. 47 to 59.

[0247] <First pattern> Figure 47 is a schematic diagram showing the layout pattern shown in Figure 2 along with the movement lines of store clerk EM and customers CUa and CUb. Hereinafter, this pattern will be referred to as the first pattern. As described above, payment system 100 includes input device 20, transaction processing device 30, payment device 40, and instruction device 50. In the first pattern, payment system 100 has input device 20 placed above checkout counter 80 arranged along customer aisle PAa, transaction processing device 30 placed at the end of checkout counter 80 on the exit side of aisle PAa, and payment device 40 and instruction device 50 placed behind transaction processing device 30 in aisle PAa.

[0248] The input device 20 is operated by a store clerk EM standing in the space SP and inputs information related to transactions with customers. Therefore, in the first pattern, the input device 20 is arranged so that the operation surface operated by the store clerk EM, that is, the barcode reading window of the fixed scanner 21, the operation panel surface of the touch panel 23, the key surface of the keyboard 24, etc., faces the space SP.

[0249] Transaction processing device 30 is operated by customer CUa standing in aisle PAa to settle transactions based on transaction-related information input via input device 20. Therefore, in the first pattern, transaction processing device 30 is positioned so that the operation surface operated by customer CUa, that is, the operation panel surface of second touch panel 33, the cash deposit section and dispensing section of automatic change machine 35, etc., face toward aisle PAa.

[0250] Payment device 40 is operated by customer CUb standing in aisle PAc leading to the back of transaction processing device 30, and settles transactions based on transaction-related information held in holding server (holding device) 10, which holds transaction-related information when payment cannot be made by transaction processing device 30. Therefore, in a first pattern, payment device 40 is arranged on the back of transaction processing device 30 so that the operation surface operated by customer CUb, i.e., the operation panel surface of touch panel 41, the cash deposit section and dispensing section of automatic change dispenser 43, etc., face toward aisle PAc. Specifically, the surface of payment device 40 opposite the operation surface is arranged so that it is approximately flush with the side of transaction processing device 30 on the input device 20 side.

[0251] Both transaction processing device 30 and settlement device 40 are operated by customers to settle transactions. Therefore, transaction processing device 30 can be referred to as a first settlement device, and settlement device 40 can be referred to as a second settlement device.

[0252] The instruction device 50 is operated by a store clerk EM in the space SP and instructs the payment device 40 to output information related to the transaction that has been put on hold in the holding server 10. Therefore, in the first pattern, the instruction device 50 is placed on the side of the payment device 40 that is closer to the space SP, that is, near the side opposite to the operation surface of the payment device 40. Specifically, the operation surface of the instruction device 50 that is operated by the store clerk EM, that is, the operation panel surface of the touch panel 505, is placed so that it faces opposite to the operation surface of the payment device 40.

[0253] In the first pattern, customer CUa, after inputting transaction-related information, such as information about the purchased product, by a store clerk operating input device 20, walks down aisle PAa as shown by flow line CUaL to a position facing the operation panel of transaction processing device 30. At this time, transaction processing device 30 is ready for payment, so customer CUa operates transaction processing device 30 to pay the amount required to settle the transaction. After completing payment, customer CUa heads toward the exit.

[0254] While customer CUa is making a payment, the next customer CUb, who has finished inputting information related to the transaction through the clerk's operation of the input device 20, moves through aisles PAa and PAc as shown by the flow line CUbL to a position facing the operation screen of the payment device 40. At this time, the clerk moves to the location of the instruction device 50 as shown by the flow line EML and touches the call button BEa. This enables the payment device 40 to make a payment, so customer CUb operates the payment device 40 to pay the amount required to settle the transaction. After completing the payment, customer CUb heads to the exit.

[0255] As shown above, the first customer CUa only needs to move in a generally linear fashion as indicated by the flow line CUaL, which is efficient. Meanwhile, the second customer CUb only needs to move in an "L" shape as indicated by the flow line CUbL, which does not pose a significant burden. At this time, the store clerk EM moves within the space SP as indicated by the flow line EML to touch the call button BEa on the instruction device 50, and can also carry the shopping basket containing customer CUb's registered items from the checkout counter 80 to near the payment device 40. In this case, the side of the payment device 40 on which the instruction device 50 is located is generally flush with the side of the transaction processing device 30 on the input device 20 side. This makes it easy for the store clerk EM to carry the shopping basket. Furthermore, for example, if there is a problem with the transaction processing device 30, the store clerk EM can move within the space SP to the location where the transaction processing device 30 is installed, without the payment device 40 interfering with the store clerk EM's movement.

[0256] In the first pattern, the orientation of the operation surface of the instruction device 50 is not limited to the orientation opposite to that of the operation surface of the payment device 40. For example, as shown in FIG. 48 , the instruction device 50 may be tilted at any angle, for example, about 45 degrees, clockwise from the perspective of the store clerk, as indicated by reference numeral 50-1. This prevents customers walking through the aisle PAa from peeking at the operation surface of the instruction device 50. Alternatively, as shown by reference numeral 50-2, the instruction device 50 may be tilted at any angle, for example, about 45 degrees counterclockwise from the perspective of the store clerk. This allows the store clerk EM operating the input device 20 to easily see the operation surface of the instruction device 50 simply by turning around. In this way, the orientation of the operation surface of the instruction device 50 may be tilted at any angle clockwise or counterclockwise around the orientation opposite to that of the operation surface of the payment device 40.

[0257] Furthermore, the location of the settlement device 40 is not limited to the location shown in the pattern example of FIG. 49 shows an example in which payment device 40 protrudes toward aisle PAc by the width Ha of transaction processing device 30. In other words, payment device 40 is positioned so that the surface opposite the operation surface is approximately flush with the side of transaction processing device 30 opposite input device 20. This positioning has the advantage of making it easier for customers to find payment device 40, which is located behind transaction processing device 30.

[0258] 50 shows an example in which the operation surface of payment device 40 is arranged so as to be substantially flush with the side of transaction processing device 30 opposite input device 20. This arrangement widens the aisle PAc behind the customer facing the operation surface of payment device 40. In addition, since instruction device 50 moves closer to store clerk EM standing in space SP to operate input device 20, the amount of movement of store clerk EM is reduced.

[0259] As described above in detail, the first pattern is a layout pattern in which input device 20 and transaction processing device (first payment device) 30 are arranged side by side so that the operation surface of input device 20 operated by a store clerk and the operation surface of transaction processing device 30 operated by a customer face opposite directions, payment device (second payment device) 40 is arranged behind the operation surface of transaction processing device 30 operated by a customer, and instruction device 50 is arranged on the opposite side of the operation surface of payment device 40 operated by a customer. By adopting such a layout, payment system 100, which aims to reduce labor costs by having customers perform operations related to payment, can be realized without imposing a large burden on store clerks or customers.

[0260] <Second pattern> 51 is a schematic diagram showing the second layout pattern along with the movement lines of store clerk EM and customers CUa and CUb. In the second pattern, as in the first pattern, input device 20 and transaction processing device 30 are arranged side by side along aisle PAa. The operation surface of input device 20 is also arranged facing space SP, and the operation surface of transaction processing device 30 is arranged facing aisle PAa.

[0261] In the second pattern, payment device 40 is placed alongside transaction processing device 30. Specifically, payment device 40 is placed so that the operation surface faces aisle PAa. Instruction device 50 is placed near the surface opposite the operation surface of payment device 40. Preferably, instruction device 50 is placed closer to the adjacent transaction processing device 30. In this case, instruction device 50 is placed at an angle counterclockwise from the direction opposite to the operation surface of payment device 40 so that the operation surface can also be seen by store clerk EM operating input device 20.

[0262] In the second pattern, customer CUa, who operates transaction processing device 30 to make a payment, moves through passage PAa as shown by flow line CUaL to a position facing the operation panel of transaction processing device 30. Since transaction processing device 30 is capable of making payments, customer CUa operates transaction processing device 30 to pay the amount necessary to settle the transaction. After completing the payment, customer CUa heads toward the exit. At this time, if customer CUb is operating payment device 40, customer CUa goes around behind customer CUb and heads toward the exit.

[0263] Meanwhile, customer CUb, who is operating the payment device 40 to make a payment, moves around behind customer CUa standing in aisle PAa, as shown by flow line CUbL, to a position facing the operation panel of the payment device 40. At this time, store clerk EM moves to the location of the instruction device 50, as shown by flow line EML, and touches the call button BEa. At that time, store clerk EM can carry the shopping basket containing customer CUb's registered products from the checkout counter 80 to near the payment device 40. Since the operation on the instruction device 50 enables the payment device 40 to make a payment, customer CUb operates the payment device 40 to pay the amount required to settle the transaction. After completing the payment, customer CUb heads to the exit.

[0264] In this way, the second pattern arranges input device 20 and transaction processing device (first payment device) 30 side by side so that the operation surface of input device 20 operated by the store clerk and the operation surface of transaction processing device 30 operated by the customer face opposite directions, and further arranges payment device (second payment device) 40 next to transaction processing device 30 so that the operation surface of payment device 40 operated by the customer faces the same direction as the operation surface of transaction processing device 30 operated by the customer. With this second layout pattern, not only customer CUa who operates transaction processing device 30 to make a payment, but also customer CUb who operates payment device 40 to make a payment simply move in a substantially straight line down passage PAa toward the exit.

[0265] On the other hand, as shown in Figure 51, the instruction device 50 is positioned at an angle counterclockwise from the direction opposite to the operation surface of the payment device 40, so that the store clerk EM can see the operation surface of the instruction device 50 even while operating the input device 20.

[0266] The orientation of the operation surface of the instruction device 50 is not limited to the orientation shown in FIG. 51. For example, as shown by reference numeral 50-3 in FIG. 52, the instruction device 50 may be attached so that its operation surface faces in the opposite direction to the operation surface of the payment device 40. By doing so, customers in the aisle PAa will not be able to see the operation surface of the instruction device 50 at all. Alternatively, as shown by reference numeral 50-4, the instruction device 50 may be placed with its operation surface facing the side of the store clerk EM who operates the input device 20. By doing so, the store clerk EM can easily see the operation surface of the instruction device 50 while operating the input device 20.

[0267] <Third pattern> FIG. 53 is a schematic diagram showing a third layout pattern along with the movement lines of store clerk EM and customers CUa and CUb. The third pattern swaps the positions of transaction processing device 30 and payment device 40 from the second pattern. Specifically, input device 20 and payment device 40 are arranged side by side along aisle PAa. The operation surface of input device 20 faces space SP, and the operation surface of payment device 30 faces aisle PAa. Transaction processing device 30 is also arranged side by side with payment device 30. Specifically, the operation surface of transaction processing device 30 faces aisle PAa. Furthermore, instruction device 50 is arranged near the surface opposite the operation surface of payment device 40. Preferably, instruction device 50 is arranged closer to the adjacent input device 20. Instruction device 50 is arranged at a counterclockwise angle relative to the direction opposite the operation surface of payment device 40 so that the operation surface can be seen by store clerk EM operating input device 20.

[0268] In the third pattern, customer CUa, who operates transaction processing device 30 to make a payment, moves through passage PAa as shown by flow line CUaL to a position facing the operation panel of transaction processing device 30. At this time, if customer CUb is operating payment device 40, customer CUa moves around behind customer CUb to transaction processing device 30. Since transaction processing device 30 is capable of making payments, customer CUa performs an operation on transaction processing device 30 to pay the amount required to settle the transaction. After completing the payment, customer CUa heads toward the exit.

[0269] Meanwhile, customer CUb, who is operating payment device 40 to make a payment, moves to a position opposite the operation panel of payment device 40, as shown by flow line CUbL. At this time, the store clerk moves to the location of instruction device 50, as shown by flow line EML, and touches call button BEa. This enables payment device 40 to make a payment, so customer CUb operates payment device 40 to pay the amount required to settle the transaction. After completing the payment, customer CUb heads toward the exit. At this time, if customer CUa is operating transaction processing device 30, customer CUb will go around behind customer CUa and head toward the exit.

[0270] In this way, in the third pattern, input device 20 and payment device (second payment device) 40 are arranged side by side so that the operation surface of input device 20 operated by the store clerk and the operation surface of payment device 40 operated by the customer face opposite directions, and transaction processing device (first payment device) 30 is further arranged next to the payment device so that the operation surface of the transaction processing device operated by the customer faces the same direction as the operation surface of payment device 40 operated by the customer. In this third layout pattern, as in the second pattern, not only customer CUa who operates transaction processing device 30 to make a payment, but also customer CUb who operates payment device 40 to make a payment only need to move approximately linearly down aisle PAa toward the exit. Furthermore, because instruction device 50 is located near store clerk EM who operates input device 20, there is the advantage that the amount of movement of store clerk EM is less than in the second pattern, thereby reducing the burden on the store clerk.

[0271] <Fourth pattern> 54 is a schematic diagram showing the fourth layout pattern along with the movement lines of store clerk EM and customers CUa and CUb. In the fourth pattern, transaction processing device 30 and settlement device 40 are separately arranged on either side of checkout counter 80 where input device 20 is arranged. The arrangement of input device 20 is the same as the other first to third patterns. That is, it is arranged above checkout counter 80 with the operation surface facing the space SP where store clerk EM will be standing.

[0272] Transaction processing device 30 and settlement device 40 are both placed with their operation surfaces facing the aisle PA. Instruction device 50 is placed near the surface opposite to the operation surface of settlement device 40. Specifically, instruction device 50 is placed so that its operation surface faces in the opposite direction to the operation surface of settlement device 40.

[0273] In the fourth pattern, the entrance through which customers waiting to pay enter is on the side opposite the operation surface of input device 20. After entering through the entrance and having the store clerk operate input device 20 to input transaction-related information, customer CUa moves through aisle PA, as shown by flow line CUaL, to a position opposite the operation surface of transaction processing device 30. Since transaction processing device 30 is capable of performing payments, customer CUa performs an operation on transaction processing device 30 to pay the amount required to settle the transaction. After completing the payment, customer CUa passes by transaction processing device 30 and heads toward the exit.

[0274] Meanwhile, the next customer CUb, who also enters through the entrance and has finished inputting transaction information through the clerk's operation of the input device 20, walks down the aisle PA in the opposite direction from customer CUa, as shown by the flow line CUbL, until he or she is positioned opposite the operation panel of the payment device 40. At this time, the clerk moves to the location of the instruction device 50, as shown by the flow line EML, and touches the call button BEa. This enables the payment device 40 to make a payment, so customer CUb operates the payment device 40 to pay the amount required to settle the transaction. After completing the payment, customer CUb passes by the payment device 40 and heads toward the exit.

[0275] Thus, in the fourth pattern, the input device 20 and the transaction processing device (first payment device) 30 are arranged side by side so that the operation surface of the input device 20 operated by the store clerk and the operation surface of the transaction processing device 30 operated by the customer face opposite directions. Furthermore, the payment device (second payment device) 40 is arranged next to the input device 20 so that the operation surface of the payment device 40 operated by the customer faces the same direction as the operation surface of the transaction processing device 30 operated by the customer. With this fourth layout pattern, customers will not be able to sneak around behind another customer operating the transaction processing device 30 or the payment device 40 to head toward the exit. Therefore, other customers will not be able to peek at the information of a customer making a payment, thereby protecting privacy. Furthermore, since the instruction device 50 is located near the store clerk EM operating the input device 20, the amount of movement of the store clerk EM is reduced, reducing the store clerk's workload.

[0276] The orientation of the instruction device 50 is not limited to the orientation shown in Fig. 54. For example, as shown in Fig. 55, the instruction device 50 may be disposed so that the operation surface thereof faces the store clerk operating the input device 20. This allows the store clerk EM to see the operation surface of the instruction device 50 while operating the input device 20.

[0277] <Fifth pattern> The first to fourth patterns illustrate a payment system installed in one aisle PAa. The fifth pattern illustrates a payment system installed in two adjacent aisles PAa and PAb, separated by a staff space SP. That is, in the fifth pattern, checkout counter 80-1 on the aisle PAa side and checkout counter 80-2 on the aisle PAb side are arranged facing each other across the staff space SP. An input device 20-1 is installed at checkout counter 80-1, and an input device 20-2 is installed at checkout counter 80-2. Both input devices 20-1 and 20-2 are arranged with their operation surfaces facing the space SP. With this arrangement, staff member EMa on the aisle PAa side operates input device 20-1 to input information related to transactions between customers CUa and CUb using aisle PAa. Staff member EMb on the aisle PAb side operates input device 20-2 to input information related to transactions between customers CUc and CUd using aisle PAb.

[0278] In the fifth pattern, transaction processing device 30-1 is placed at the end of checkout counter 80-1, and transaction processing device 30-2 is placed at the end of checkout counter 80-2. Specifically, in the fifth pattern, transaction processing device 30-1 and transaction processing device 30-2 are placed at the ends of checkout counters 80-1, 80-2 so that the surfaces opposite to the operation surfaces of each device face each other. Transaction processing device 30-1 is the first payment device at which a customer CUa, who has input transaction-related information into input device 20-1, makes a payment. Transaction processing device 30-2 is the first payment device at which a customer CUc, who has input transaction-related information into input device 20-2, makes a payment.

[0279] In the fifth pattern, one payment device 40 is placed between two transaction processing devices 30-1 and 30-2. Payment device 40 is placed with its operation surface facing toward aisle PAc. As in the first pattern, instruction device 50 is placed near the surface opposite the operation surface of payment device 40. Instruction device 50 is placed with its operation surface facing in the opposite direction to the operation surface of payment device 40.

[0280] The settlement device 40 is a second settlement device through which a customer CUb, whose transaction information has been input to the input device 20-1, makes a settlement. The settlement device 40 is also a second settlement device through which a customer CUd, whose transaction information has been input to the input device 20-2, makes a settlement.

[0281] In the fifth pattern, the flow lines CUaL and CUCL of customer CUa operating transaction processing device 30-1 in aisle PAa to make a payment and customer CUc operating transaction processing device 30-2 in aisle PAb to make a payment are approximately linear, similar to that of customer CUa described in the first pattern. Meanwhile, the flow lines CUbL and CUDL of customer CUb passing through aisle PAa to make a payment at payment device 40 and customer CUd passing through aisle PAb to make a payment at payment device 40 are shaped like the letter "L," similar to that of customer CUb described in the first pattern. Therefore, customer movement is not burdensome and is efficient, similar to that of customer CUb in the first pattern. Furthermore, the flow lines EMaL and EMbL of clerk EMa operating input device 20-1 and clerk EMb operating input device 20-2 are similar to those of clerk EM described in the first pattern. Therefore, the amount of movement by clerks is small, and the burden on them is light.

[0282] Thus, the fifth pattern includes two input devices 20-1 and 20-2, two transaction processing devices (first payment devices) 30-1 and 30-2, one payment device (second payment device) 40, and one instruction device 50. One set of input device 20-1 and transaction processing device 30-1 and another set of input device 20-2 and transaction processing device 30-2 are arranged facing each other with a space SP for store clerks in between. Specifically, the operation surfaces of input devices 20-1 and 20-2 operated by store clerks face the space SP, and the operation surfaces of transaction processing devices 30-1 and 30-2 operated by customers face the opposite side of the space SP. Furthermore, a payment device 40 is arranged between the two transaction processing devices 30-1 and 30-2. Specifically, the payment device 40 is arranged so that the operation surface operated by customers faces the opposite side of the space SP. The instruction device 50 is placed on the opposite side of the payment device 40 from the operation surface side operated by the customer. By adopting this layout, the payment system 100, which aims to reduce labor costs by having customers perform operations related to payment for two adjacent aisles, can be realized without placing a heavy burden on store staff or customers. Furthermore, by adopting the fifth layout pattern, the payment device 40 can be shared by two adjacent aisles, which can have the effect of reducing system costs compared to adopting the first to fourth layout patterns.

[0283] In the fifth pattern, as explained with reference to Fig. 48, the operation surface of instruction device 50 may be tilted at any angle, or instruction device 50 may be positioned closer to one of the aisles. The placement of payment device 40 is also not particularly limited. Incidentally, Fig. 56 illustrates a case where the surface opposite the operation surface of payment device 40 is flush with the side surfaces of checkout counters 80-1 and 80-2 of both transaction processing devices 30-1 and 30-2.

[0284] 57 shows an example in which payment device 40 protrudes toward aisle PAc by the width Ha of transaction processing devices 30-1 and 30-2. In other words, payment device 40 is positioned so that the surface opposite the operation surface is flush with the side surfaces of transaction processing devices 30-1 and 30-2 opposite checkout counters 80-1 and 80-2. This positioning has the advantage of making it easier for customers to find payment device 40, which is sandwiched between transaction processing devices 30-1 and 30-2.

[0285] 58 shows an example in which the operation surface of payment device 40 is arranged flush with the side of both transaction processing devices 30-1, 30-2 opposite checkout counters 80-1, 80-2. This arrangement widens the aisle PAc behind the customer facing the operation surface of payment device 40. In addition, since instruction device 50 moves closer to store clerk EM standing in space SP to operate input device 20, the amount of movement of store clerk EM is reduced.

[0286] Incidentally, when the fifth pattern layout is adopted, the instruction device 50 is also shared, so it is necessary to change the layout of the instruction screen displayed on the touch panel 505. FIG. 59 shows an example of the instruction screen SEb of the instruction device 50 when the fifth pattern layout is used. The instruction screen SEb divides the screen of the touch panel 505 into two halves, left and right. On the left side, there are arranged the lane number of the lane L located on the left side as one faces the instruction screen SEb, for example, "001," a pull-down area AEaa, and a call button BEaa. On the right side, there are arranged the lane number of the lane L located on the right side as one faces the instruction screen SEb, for example, "002," a pull-down area AEab, and a call button BEab.

[0287] By setting the screen of the touch panel 505 of the instruction device 50 shared by two adjacent lanes as the instruction screen SEb, the store clerk EMa serving customers in the lane with lane number "001" selects his / her name in the pull-down area AEaa. The store clerk EMb serving customers in the lane with lane number "002" selects his / her name in the pull-down area AEab. By performing these operations, the employee memory 5031 of the instruction device 50 stores the employee code of the store clerk EMa in association with the lane number "001." Also, the employee code of the store clerk EMb in association with the lane number "002."

[0288] Furthermore, the call button BEaa becomes active when the transaction file of the transaction processed in the lane with lane number "001" is reserved in the reservation server 10. Therefore, when the store clerk EMa touches the call button BEaa, the transaction file that has been reserved in the employee folder 1033 in which the employee code of the store clerk EMa is set is output from the reservation server 10 to the payment device 40, provided that the payment device 40 is available. Thus, the customer CMb whose transaction was processed in the lane with lane number "001" can settle the transaction at the payment device 40.

[0289] Similarly, the call button BEab becomes active when the transaction file of the transaction processed in the lane with lane number "002" is reserved in the reservation server 10. Therefore, when the store clerk EMb touches the call button BEab, the transaction file that has been reserved in the employee folder 1033 in which the employee code of the store clerk EMb is set is output from the reservation server 10 to the payment device 40, provided that the payment device 40 is available. Thus, the customer CUd whose transaction was processed in the lane with lane number "002" can settle the transaction at the payment device 40.

[0290] [Variations] In the above embodiment, it has been explained that when the call button BEa of the instruction device 50 is pressed, an instruction is received from the instruction device 50 and the first signal is output from the payment device 40 to the holding server 10. In this regard, when the call button BEa of the instruction device 50 is pressed, the first signal may be output directly from the instruction device 50 to the holding server 10.

[0291] In the above embodiment, the instruction device 50 is set to a state in which the call button BEa can be pressed when it receives a signal indicating instruction validation from the reservation server 10. In this regard, the instruction device 50 may be set to a state in which the call button BEa can be pressed at all times. In other words, the call button BEa may be set to be pressable regardless of whether a transaction file is being reserved on the reservation server 10.

[0292] In the above embodiment, a tablet terminal is used as the instruction device 50. However, the instruction device 50 is not limited to a tablet terminal. For example, a touch panel for clerk operation may be provided as the payment device 40, separate from the touch panel 41 for customer operation. The touch panel for clerk operation is provided in a location where a clerk standing in the space SP can touch and operate it. The processor 401 of the payment device 40 controls the touch panel for clerk operation as well as the touch panel 41 for customer operation. Specifically, the processor 401 sets the screen of the touch panel for clerk operation as an instruction screen SEa. When the call button BEa on the instruction screen SEa is pressed, the processor 401 outputs a signal to the holding server 10 via the payment device 40, instructing that information related to the transaction be output to the payment device 40. In other words, the touch panel for clerk operation controlled by the processor 401 functions as the instruction device 50. By adopting such a configuration, a touch panel rather than a tablet terminal can be used as the instruction device 50, thereby reducing system costs.

[0293] Although several 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 embodied 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 inventions and their equivalents as defined in the claims. [Explanation of symbols]

[0294] 1...first processing device, 10...holding server, 20, 20-1, 20-2...input device, 30, 30-1, 30-2...transaction processing device, 40...settlement device, 50...instruction device, 60...communication network, 100...settlement system.

Claims

1. a first processing device including an input device operated by a store clerk and inputting information related to a transaction with a customer, and a first settlement device operated by the customer and settling the transaction based on the information related to the transaction input via the input device; a second settlement device that acquires information related to the transaction from a holding device that holds information related to the transaction input by the input device, and allows a customer to act as an operator and settle the transaction; an instruction device operated by a store clerk to instruct the second settlement device to output information related to the transaction held in the holding device; Equipped with A payment system in which the instruction device is placed on the opposite side of the second payment device from the operation surface operated by the customer.

2. an input device operated by a store clerk to input information related to a transaction with a customer; a first settlement device in which a customer acts as an operator and settles a transaction based on information related to the transaction input via the input device; a second settlement device that acquires information related to the transaction from a holding device that holds information related to the transaction input by the input device, and allows a customer to act as an operator and settle the transaction; an instruction device operated by a store clerk to instruct the second settlement device to output information related to the transaction held in the holding device; Equipped with A payment system in which the instruction device is placed on the opposite side of the second payment device from the operation surface operated by the customer.

3. 3. The payment system according to claim 1, wherein an operation surface of the instruction device operated by a store clerk faces in a direction opposite to an operation surface of the second payment device operated by a customer.

4. The input device and the first payment device are arranged side by side such that an operation surface of the input device operated by a store clerk and an operation surface of the first payment device operated by a customer are oriented in opposite directions; 3. The payment system according to claim 1, wherein the second payment device is disposed behind an operation surface of the first payment device that is operated by a customer.

5. A payment system as described in claim 1 or 2, wherein the input device and the first payment device are arranged side by side so that the operation surface of the input device operated by the store clerk and the operation surface of the first payment device operated by the customer face opposite directions, and further the second payment device is arranged next to the first payment device so that the operation surface of the second payment device operated by the customer faces the same direction as the operation surface of the first payment device operated by the customer.

6. A payment system as described in claim 1 or 2, wherein the input device and the second payment device are arranged side by side so that the operation surface of the input device operated by the store clerk and the operation surface of the second payment device operated by the customer face opposite directions, and further the first payment device is arranged next to the second payment device so that the operation surface of the first payment device operated by the customer faces the same direction as the operation surface of the second payment device operated by the customer.

7. A payment system as described in claim 1 or 2, wherein the input device and the first payment device are arranged side by side so that the operation surface of the input device operated by the store clerk and the operation surface of the first payment device operated by the customer face opposite directions, and further the second payment device is arranged next to the input device so that the operation surface of the second payment device operated by the customer faces the same direction as the operation surface of the first payment device operated by the customer.

8. 3. The payment system according to claim 1, wherein the input device and the first payment device are a single device controlled by a single processor.

9. two input devices operated by store clerks to input information related to transactions with customers; two first settlement devices provided corresponding to the two input devices, the first settlement devices being operated by a customer to settle a transaction based on information related to the transaction input via the corresponding input devices; a second settlement device that acquires information related to the transaction from a holding device that holds information related to the transaction input by the input device, and allows a customer to act as an operator and settle the transaction; an instruction device operated by a store clerk to instruct the second settlement device to output information related to the transaction held in the holding device; Equipped with one of the input devices and one of the first payment devices corresponding to the input device, and another of the input devices and one of the first payment devices corresponding to the input device, are arranged opposite to each other with a space for a store clerk in between, and the operation surfaces of the two input devices operated by the store clerk face the space, and the operation surfaces of the two first payment devices operated by the customer face the opposite side to the space; The second payment device is disposed between the two first payment devices so that an operation surface of the second payment device operated by a customer faces away from the space; A payment system in which the instruction device is placed on the opposite side of the operation surface of the second payment device that is operated by the customer.

Images