Payment system, instruction device and its program

Abstract

By issuing instructions to output transaction-related information at the appropriate time without burdening store staff, transactions can be settled efficiently. [Solution] The instruction device comprises a status confirmation means and an instruction means. The status confirmation means confirms whether the settlement device is able to settle the transaction. The instruction means instructs the settlement device to take in transaction information if the settlement device is able to settle the transaction. The settlement device comprises an intake means and a settlement means. The intake means takes in transaction information from the holding device in response to the intake instruction from the instruction device. Based on the transaction information taken in by the intake means, the settlement means settles the transaction with the person involved in the transaction acting as the operator.

Description

Technical Field

[0004] , , , , , , , ,

[0005] , , , , ,

[0001] Embodiments of the present invention relate to a settlement system, an instruction device of the system, and a program thereof.

Background Art

[0002] In recent years' retail industry, from the viewpoints of improving processing efficiency and reducing labor costs, a settlement system has been put into practical use in which a store clerk of a retail store performs the registration operation of the goods purchased by a customer, and the customer himself / herself performs the payment operation of the price of the goods. This type of settlement system includes a first device that accepts the registration operation of goods with a store clerk as an operator, a second device that accepts the payment operation with a customer as an operator, and a server that relays between the first device and the second device. The server temporarily stores information related to a transaction created based on the registration operation received by the first device. Then, in response to an output instruction from the outside, the server outputs the stored information related to the transaction to the second device. The second device processes the information related to the transaction based on the payment operation received by the second device and settles the transaction with the customer.

[0003] In this type of conventional settlement system, the output instruction is entrusted to the judgment of the store clerk. Therefore, the store clerk has to give an output instruction of information related to the transaction at an appropriate timing while performing the registration operation of the goods, which has been a burden.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] The problem that the embodiments of the present invention aim to solve is to provide a payment system that can efficiently settle transactions by allowing the output of transaction-related information to be issued at the appropriate time without burdening the store staff. [Means for solving the problem]

[0006] In one embodiment, the payment system includes a payment device that communicates with a holding device that holds transaction information entered by a store employee, and an instruction device that communicates with the payment device. The instruction device comprises a status confirmation means and an instruction means. The status confirmation means confirms whether the settlement device is capable of settling the transaction. The instruction means instructs the settlement device to take in transaction information if the settlement device is capable of settling the transaction. The settlement device comprises an input means and a settlement means. The input means acquires transaction information from a holding device in response to an input instruction from an instruction device. The settlement means settles the transaction based on the transaction information acquired by the input means, with the person involved in the transaction acting as the operator. [Brief explanation of the drawing]

[0007] [Figure 1] Figure 1 is a block diagram showing a schematic configuration of a payment system according to one embodiment. [Figure 2] Figure 2 is a schematic diagram showing the positional relationship between the input device, transaction processing device, settlement device, and instruction device in a single settlement lane. [Figure 3] Figure 3 is a block diagram showing the main circuit configuration of the transaction processing device. [Figure 4] Figure 4 is a schematic diagram showing the main memory areas formed in the main memory of the transaction processing unit. [Figure 5] Figure 5 is a block diagram showing the main circuit configuration of the payment device. [Figure 6] Figure 6 is a schematic diagram showing the main storage areas formed in the main memory of the payment device. [Figure 7]Figure 7 is a block diagram showing the main circuit configuration of the hold server. [Figure 8] Figure 8 is a block diagram showing the main circuit configuration of the indicator device. [Figure 9] Figure 9 is a schematic diagram showing the main functional configurations of the holding server, input device, transaction processing device, settlement device, and instruction device, respectively. [Figure 10] Figure 10 is a flowchart showing the essential steps of information processing performed by the processor of the transaction processing device according to the first business program. [Figure 11] Figure 11 is a flowchart showing the essential steps of the first information processing included in the information processing performed by the processor of the transaction processing device. [Figure 12] Figure 12 is a flowchart showing the essential steps of the first information processing included in the information processing performed by the processor of the transaction processing device. [Figure 13] Figure 13 is a flowchart showing the essential steps of the first information processing included in the information processing performed by the processor of the transaction processing device. [Figure 14] Figure 14 is a flowchart showing the essential steps of the second information processing included in the information processing performed by the processor of the transaction processing device. [Figure 15] Figure 15 is a flowchart showing the essential steps of the third information processing included in the information processing performed by the processor of the transaction processing device. [Figure 16] Figure 16 is a flowchart showing the essential steps of the information processing performed by the hold server's processor according to the second business program. [Figure 17] Figure 17 is a flowchart showing the essential steps of information processing performed by the instruction device's processor according to the third business program. [Figure 18] Figure 18 is a flowchart showing the essential steps of the information processing performed by the payment device's processor according to the fourth business program. [Figure 19] Figure 19 is a flowchart showing the essential steps of the information processing performed by the payment device's processor according to the fourth business program. [Figure 20]FIG. 20 is a sequence diagram of main data signals exchanged between the transaction processing device, the holding server, and the instruction device. [Figure 21] FIG. 21 is a sequence diagram of main data signals exchanged between the instruction device, the settlement device, and the holding server. [Figure 22] FIG. 22 is a block diagram showing a schematic configuration of a settlement system according to another embodiment.

Embodiments for Carrying Out the Invention

[0008] Hereinafter, embodiments of a settlement system that can output an instruction for information related to a transaction at an appropriate timing without burdening a store clerk, and an instruction device included in the settlement system will be described with reference to the drawings.

[0009] [Explanation of the Configuration of the Settlement System] FIG. 1 is a block diagram showing a schematic configuration of a settlement system 100 according to an embodiment. The settlement system 100 includes a holding server 10. The settlement system 100 also includes an input device 20, a transaction processing device 30, a settlement device 40, and an instruction device 50 for each settlement lane L. The settlement lane L includes a passage where customers queuing for transaction settlement line up. When this settlement system 100 is introduced in a retail store, a consumer who purchases goods becomes the customer. When this settlement system 100 is introduced in a paid facility such as an amusement park, an art museum, or a museum, a user who uses the facility becomes the customer. The customer can be referred to as the subject of the transaction. Each settlement lane L is assigned, for example, a three-digit lane number as unique lane identification information for each lane.

[0010] The settlement system 100 connects the reservation server 10, the transaction processing device 30 and the settlement device 40 of each settlement lane L bidirectionally via a communication network 60 such as a LAN (Local Area Network). For each settlement lane L, the input device 20 is connected to the transaction processing device 30 by a transmission cable 70. The settlement system 100 also connects the instruction device 50 of each settlement lane L to the communication network 60 either wired or wirelessly. Details of the reservation server 10, the input device 20, the transaction processing device 30, the settlement device 40 and the instruction device 50 will be described later.

[0011] FIG. 2 is a schematic diagram showing the positional relationship of the input device 20, the transaction processing device 30, the settlement device 40 and the instruction device 50 provided in one settlement lane L. FIG. 2 shows a settlement lane L in a retail store such as a supermarket or a home center. In this type of retail store, the sales floor where goods are displayed and the accounting area called a cash register or the like are separated. The settlement lane L is provided in the accounting area.

[0012] There is a checkout counter 80 in the accounting area. The retail store installs the checkout counter 80 along a passage PA along which customers walk in the direction of the illustrated arrow. The retail store attaches the input device 20 to the top surface 81 of the checkout counter 80. The upstream side of the passage PA from the input device 20 is used as a platform 82 for placing the purchased goods before registration, and the downstream side is used as a platform 83 for placing the purchased goods after registration.

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

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

[0015] With this arrangement of input / output devices, an employee, or store clerk, standing in the space SP opposite the aisle PA across from the checkout counter 80, can input information related to the transaction with the customer by operating the stationary scanner 21, handheld scanner 22, touch panel 23, or keyboard 24. Transaction information includes, for example, information about the products the customer is purchasing. The clerk can confirm the product name, unit price, etc. of the purchased products by looking at the information displayed on the touch panel 23. The customer can confirm the product name, unit price, etc. of the purchased products by looking at the information displayed on the display 25. The input device 20 can be rephrased as a scanner device, etc.

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

[0017] The transaction processing device 30 includes devices such as a keyboard 31, a first touch panel 32, a second touch panel 33, a printer 34, an automatic change dispenser 35, and a cashless payment terminal 36. The transaction processing device 30 is configured so that the keyboard 31 and the first touch panel 32 can be operated by store staff, while the second touch panel 33, printer 34, automatic change dispenser 35, and cashless payment terminal 36 can be operated by customers.

[0018] With this device arrangement, a store employee standing in space SP can operate the keyboard 31 or the first touch panel 32 while viewing the screen of the first touch panel 32. Meanwhile, a customer standing in aisle PA can check the information displayed on the second touch panel 33, such as information related to payment, on the spot. Customers paying with cash can insert cash into the automatic change dispenser 35 and collect the change while standing in aisle PA. Customers paying by cashless payment can operate the cashless payment terminal 36 while standing in aisle PA and pay cashless. Once payment is complete, a receipt is issued from the printer 34, and the customer can receive the receipt on the spot.

[0019] Thus, the transaction processing device 30 functions as a self-service payment device that allows customers to perform payment operations themselves. The transaction processing device 30 can also be referred to as a POS terminal, electronic cash register, sales processing device, etc.

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

[0021] The payment device 40 includes devices such as a touch panel 41, a printer 42, an automatic change dispenser 43, and a cashless payment terminal 44. The operation panel surface of the touch panel 41, the receipt printing slot of the printer 42, the coin input / dispensing slot of the automatic change dispenser 43, and the operation section of the cashless payment terminal 44 are all located on one side of the device body. Retail stores install the payment device 40 so that one side of it faces customers passing in front of the transaction processing device 30.

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

[0023] The instruction device 50 is a device that issues instructions to the settlement device 40 to retrieve transaction information 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 customer transactions processed by the transaction processing device 30. The instruction device 50 issues an instruction to the settlement device 40 to retrieve the transaction information. Upon receiving this instruction, the settlement device 40 retrieves the transaction information that had been held in the holding server 10.

[0024] One example of an instruction device 50 is a tablet terminal. A tablet terminal is an input device equipped with a flat liquid crystal screen that can be operated by touching the screen with a finger or pen. The instruction device 50 is operated by a store employee. Therefore, retail stores install the instruction device 50 in a position that is easy for store employees in 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 opposite side of the payment device 40 from the side operated by the customer, with the screen facing towards space SP.

[0025] [Description of Transaction Processing Unit Configuration] Figure 3 is a block diagram showing the main circuit configuration of the transaction processing device 30. The transaction processing device 30 includes a 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, etc. The system transmission path 311 includes an address bus, data bus, control signal lines, etc. The system transmission path 311 connects the processor 301 to the other parts and transmits data signals exchanged between them.

[0026] The transaction processing unit 30 is configured as a computer by connecting a 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 a system transmission path 311. The transaction processing unit 30 then connects a keyboard 31 and a first touch panel 32 to this computer via the system transmission path 311. The transaction processing unit 30 also connects a second touch panel 33 to the touch panel interface 306, a printer 34 to the printer interface 307, an automatic change dispenser 35 to the change dispenser interface 308, and a cashless payment terminal 36 to the payment terminal interface 309.

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

[0028] Main memory 302 corresponds to the main memory portion of the computer described above. Main memory 302 includes a non-volatile memory area and a volatile memory area. In the non-volatile memory area, main memory 302 stores the operating system or application programs. Main memory 302 may also store data necessary for the processor 301 to perform processing to control each part in the non-volatile or volatile memory area. Main memory 302 uses the volatile memory area as a work area where data is rewritten as needed by the processor 301. The non-volatile 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 described above. For example, EEPROM (Electric Erasable Programmable Read-Only Memory), HDD (Hard Disk Drive), or SSD (Solid State Drive) can be auxiliary storage devices 303. The auxiliary storage device 303 stores data used by the processor 301 in performing various processes, data created by the processing performed by the processor 301, etc. The auxiliary storage device 303 may also store the application programs described above.

[0030] Clock 304 measures the date and time. Processor 301 processes the date and time measured by clock 304 as the current date and time.

[0031] The communication interface 305 is an interface for data communication with the holding server 10 connected to the communication network 60. The communication interface 305 is also an interface for data communication with other servers, such as a POS server, which are also connected to the communication network 60. The POS server is a computer that has 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 aggregates product sales data of purchased products processed by the transaction processing device 30 to manage sales, inventory, etc. at the point of sale.

[0032] The touch panel interface 306, printer interface 307, change dispenser interface 308, and payment terminal interface 309 are all interfaces for data communication with devices externally attached to the transaction processing device 30. Specifically, the touch panel interface 306 communicates data with the second touch panel 33. The printer interface 307 communicates data with the printer 34. The change dispenser interface 308 communicates data with the automatic change dispenser 35. The payment terminal interface 309 communicates data with the cashless payment terminal 36.

[0033] The input device interface 310 is an interface for data communication with the input device 20 connected by the transmission cable 70. Specifically, the input device interface 310 communicates data with the stationary scanner 21, the handheld scanner 22, the touch panel 23, the keyboard 24, and the display 25, respectively.

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

[0035] The first file area 3021 is an area for storing transaction files created for each customer. A transaction file stores information related to a transaction with a customer that is processed as a single transaction, such as information related to purchased goods. 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 set for each product to identify it. The sales amount is the amount obtained by multiplying the unit price by the purchase quantity. The product sales data only needs to include at least the product code and purchase quantity of the purchased goods.

[0036] The second file area 3022 is an area for temporarily storing transaction files of customers who make payments using the transaction processing device 30. The second file area 3022 stores transaction files stored in the first file area 3021, or transaction files that are on hold at the hold server 10.

[0037] The first flag memory 3023 is an area for storing the payment in progress flag Fa. The payment in progress flag Fa is a 1-bit data that identifies whether or not payment is in progress in the transaction processing device 30. In this embodiment, the payment in progress flag Fa is set to "1" to indicate that payment is in progress, and the payment in progress flag Fa is set to "0" to indicate that payment is not in progress.

[0038] The second flag memory 3024 is an area for storing the pending flag Fb. The pending flag Fb is a 1-bit data that identifies whether or not a transaction file containing information related to a transaction processed by the transaction processing device 30 is pending in the pending server 10. In this embodiment, the pending flag Fb indicating that it is pending is set to "1", and the pending flag Fb indicating that it is not pending is set to "0".

[0039] The employee memory 3025 is an area for storing employee codes. The employee code is a unique code assigned to each employee of the store. The employee code functions as employee identification information to identify the employee who is operating the input device 20 and the transaction processing device 30. The employee memory 3025 stores the employee code of the employee who has signed on. Signing on is the process of authenticating the operator and making the input device 20 and the transaction processing device 30 usable. An employee standing in space SP first signs on by entering their employee code and password into the transaction processing device 30. Once the employee code and password are authenticated and the sign-on is approved, the employee code is stored in the employee memory 3025. Thus, the input device 20 and the transaction processing device 30 become usable.

[0040] Incidentally, employees who have finished their duties at the checkout counter sign off. Signing off means returning the input device 20 and the transaction processing device 30 to a state where they cannot be used. Signing off clears the employee code in employee memory 3025. Also, the input device 20 and the transaction processing device 30 become unusable. Sign on can be rephrased as login, sign in, etc. Sign off can be rephrased as logout, sign out, etc. Employee code can be rephrased as employee code, employee ID, employee ID, etc.

[0041] [Description of Payment Device Configuration] Figure 5 is a block diagram showing the main circuit configuration of the payment device 40. As shown, the payment device 40 includes a processor 401, main memory 402, auxiliary storage device 403, clock 404, communication interface 405, and system transmission line 406, etc. The system transmission line 406 includes an address bus, data bus, control signal lines, etc. The system transmission line 406 connects the processor 401 to the other parts and transmits data signals exchanged between them.

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

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

[0044] Main memory 402 corresponds to the main memory portion of the computer described above. Main memory 402 includes a non-volatile memory area and a volatile memory area. In the non-volatile memory area, main memory 402 stores the operating system or application programs. Main memory 402 may also store data necessary for the processor 401 to perform processing to control each part in the non-volatile or volatile memory area. Main memory 402 uses the volatile memory area as a work area where data is rewritten as needed by the processor 401. The non-volatile memory area is, for example, ROM. The volatile memory area is, for example, RAM.

[0045] The auxiliary storage device 403 corresponds to the auxiliary storage portion of the computer described above. For example, an EEPROM, HDD, or SSD could be the auxiliary storage device 403. The auxiliary storage device 403 stores data used by the processor 401 in performing various processes, data created by the processing performed by the processor 401, and so on. The auxiliary storage device 403 may also store the application program described above.

[0046] Clock 404 keeps track of the date and time. Processor 401 processes the date and time kept by clock 404 as the current date and time.

[0047] The communication interface 405 is an interface for data communication between the hold server 10 and the instruction device 50, which are connected to the communication network 60.

[0048] Figure 6 is a schematic diagram showing the main memory areas formed in the main memory 402. The payment device 40 uses a portion of the volatile memory area in the main memory 402 as the area for the third file area 4021 and the third flag memory 4022. The third file area 4021 is an area for temporarily storing transaction files of customers making payments with the payment device 40. The third file area 4021 stores transaction files retrieved from the holding server 10.

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

[0050] [Configuration description of the holding server] Figure 7 is a block diagram showing the main circuit configuration of the hold server 10. As shown, the hold server 10 includes a processor 101, main memory 102, auxiliary storage device 103, clock 104, communication interface 105, and system transmission path 106, etc. The system transmission path 106 includes an address bus, data bus, control signal lines, etc. The system transmission path 106 connects the processor 101 to the other parts and transmits data signals exchanged between them.

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

[0052] The processor 101 corresponds to the central part of the computer described above. The processor 101 controls various parts to realize various functions as a pending server 10 according to the 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 is capable of executing multiple processes in parallel.

[0053] Main memory 102 corresponds to the main memory portion of the computer described above. Main memory 102 includes a non-volatile memory area and a volatile memory area. In the non-volatile memory area, main memory 102 stores the operating system or application programs. Main memory 102 may also store data necessary for the processor 101 to perform processing to control each part in the non-volatile or volatile memory area. Main memory 102 uses the volatile memory area as a work area where data is rewritten as appropriate by the processor 101. The non-volatile memory area is, for example, ROM. The volatile memory area is, for example, RAM.

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

[0055] Clock 104 measures the date and time. Processor 101 processes the date and time measured by clock 104 as the current date and time.

[0056] The communication interface 105 is an interface for data communication between the transaction processing device 30 and the settlement device 40, which are connected to the communication network 60.

[0057] In this configuration, the hold server 10 allocates a portion of the storage area in the auxiliary storage device 103 to the employee master 1031. The employee master 1031 is a database that stores the employee's name, password, etc., associated with each employee's employee code. The password is the sign-on password set by the employee identified by the employee code. Note that the employee master 1031 may also be located on a server other than the hold server 10, such as a POS server.

[0058] The hold server 10 uses a portion of the storage area in the auxiliary storage device 103 as the area for employee-specific folders 1032. Each employee-specific folder 1032 is provided for each employee who can operate the input device 20, and each folder is identified by the employee code of that employee. The employee-specific folder 1032 is an area for storing, or holding, transaction files output from the transaction processing device 30 to the hold server 10. The hold server 10 stores the information from the transaction file, i.e., information related to the transaction with the customer, in the employee-specific folder 1032, which is identified by the employee code of the employee who signed on to the transaction processing device 30 that output the transaction file. The hold server 10 can be rephrased as a hold device.

[0059] [Description of the Indicator Device Configuration] Figure 8 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, main memory 502, auxiliary storage device 503, communication interface 504, touch panel 505, camera 506, and system transmission line 507, etc. The system transmission line 507 includes an address bus, data bus, control signal lines, etc. The system transmission line 507 connects the processor 501 to the other parts and transmits data signals exchanged between them.

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

[0061] The processor 501 corresponds to the central part of the computer described above. The processor 501 controls each part to realize various functions as an instruction device 50 according to the operating system or 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.

[0062] Main memory 502 corresponds to the main memory portion of the computer described above. Main memory 502 includes a non-volatile memory area and a volatile memory area. In the non-volatile memory area, main memory 502 stores the operating system or application programs. Main memory 502 may also store data necessary for the processor 501 to perform processing to control each part in the non-volatile or volatile memory area. Main memory 502 uses the volatile memory area as a work area where data is rewritten as needed by the processor 501. The non-volatile memory area is, for example, ROM. The volatile memory area is, for example, RAM.

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

[0064] The communication interface 504 is an interface for data communication between the settlement device 40, the transaction processing device 30, and the holding server 10, which are connected to the communication network 60.

[0065] In this configuration, the instruction device 50 uses a portion of the storage area of ​​the auxiliary storage device 503 as the area for employee memory 5031. Employee memory 5031 is an area for storing employee codes. Employee memory 5031 stores the employee codes of store employees who have signed on to the transaction processing device 30.

[0066] [Explanation of the Payment System's Functional Configuration] Figure 9 is a schematic diagram showing the main functional configurations of the holding server 10, input device 20, transaction processing device 30, settlement device 40, and instruction device 50. Below, the functions of each device will be described in the following order: input device 20, transaction processing device 30, holding server 10, instruction device 50, and settlement device 40.

[0067] <Functional Configuration of Input Devices> The input device 20 has the functions of an input means 2011 and an end acceptance means 2012. The input means 2011 has the function of inputting information related to transactions with customers, that is, information related to the products that customers purchase. The input means 2011 inputs information related to purchased products, such as product codes and purchase quantities, via input devices such as a stationary scanner 21, a handheld scanner 22, a touch panel 23, and a keyboard 24. For example, the input means 2011 inputs the product code of a purchased product from a barcode read by the stationary scanner 21 or the handheld scanner 22. For example, the input means 2011 inputs the purchase quantity of a purchased product from a numerical value entered by keypad operation on the touch panel 23 or the keyboard 24.

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

[0069] <Functional Configuration of Transaction Processing Equipment> The transaction processing device 30 has the functions of an operator authentication means 3011, an input information acquisition means 3012, a first settlement means 3013, an operator acquisition means 3014, a transaction information output means 3015, a guidance means 3016, a hold release means 3017, and an execution means 3018.

[0070] The operator authentication means 3011 is a function that processes sign-on and sign-off by the operator. The operator authentication means 3011 authenticates the employee identified by the employee code and password entered on the sign-on screen of the first touch panel 32. Once the employee is authenticated, the operator authentication means 3011 approves the sign-on to the transaction processing device 30. The operator authentication means 3011 stores the employee code for which the sign-on has been approved in the employee memory 3025. The operator authentication means 3011 also outputs the employee code for which the sign-on has been approved to the instruction device 50. Incidentally, once the sign-on has been approved, the transaction processing device 30 enables the functions of the input information acquisition means 3012, the first settlement means 3013, the operator acquisition means 3014, the transaction information output means 3015, the guidance means 3016, the hold release means 3017, and the execution means 3018.

[0071] The input information acquisition means 3012 is a function that acquires information from the input device 20 connected by the transmission cable 70. The input information acquisition means 3012 acquires information related to purchased products that has been received as input by the input means 2011 from the input device 20. The input information acquisition means 3012 acquires the input termination instruction signal received by the termination reception means 2012 from the input device 20.

[0072] The first payment method 3013 is a function for settling transactions with customers. The first payment method 3013 calculates the amount required for settlement based on transaction information entered via the input device 20. Transaction information includes, for example, information about purchased goods. Information about purchased goods includes the price and quantity of the goods sold. The first payment method 3013 calculates the amount required for settlement based on the price and quantity of each purchased item. The amount required for settlement can be rephrased as settlement amount, total amount, total amount including tax, invoice amount, etc. The first payment method 3013 settles transactions with customers according to the payment method. Payment methods include cash, credit card, electronic money, code payment, etc. The first payment method 3013 supports at least one payment method. The first payment method 3013 settles transactions with customers when the transaction can be settled at the time the termination reception means 2012 receives the input termination instruction. In other words, the first settlement means 3013 recognizes that a transaction can be settled when the payment flag Fa stored in the first flag memory 3023 is "0". If the first settlement means 3013 accepts cash as the payment method, for example, it settles the transaction with the customer in cooperation with the automatic change dispenser 35. If the first settlement means 3013 accepts cashless payment as the payment method, for example, it settles the transaction with the customer in cooperation with the cashless payment terminal 36.

[0073] The operator acquisition means 3014 is a function that acquires operator identification information to identify the operator. The operator is a store employee who operates the input device 20 to input information related to transactions with customers. Therefore, the operator identification information is the employee code stored in the employee memory 3025. The operator identification information can be rephrased as store employee identification information. The operator acquisition means 3014 acquires the employee code, which is the store employee identification information, from the employee memory 3025.

[0074] The transaction information output means 3015 is a function that outputs transaction-related information to the holding server 10. When the transaction information output means 3015 receives an instruction from the input device 20 to end the input of transaction-related information while the settlement of the transaction is impossible, it outputs the transaction-related information to the holding server 10 along with the employee code acquired by the operator acquisition means 3014. The transaction-related information 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 input information acquisition means 3012 receives an input end instruction signal while the payment in progress flag Fa in the first flag memory 3023 is "1", the transaction information output means 3015 controls the communication interface 305 to output the transaction file along with the employee code to the holding server 10.

[0075] The guidance means 3016 is a function that guides the user to the output destination of the transaction file, which is the information related to the transaction held in the holding server 10. The output destination of the transaction file held in the holding server 10 is the settlement device 40 or the transaction processing device 30. If the output destination of the transaction file is the settlement device 40, the guidance means 3016 guides the user to pay the amount at the settlement device 40. If the output destination of the transaction file is the transaction processing device 30, the guidance means 3016 guides the user to pay the amount at the transaction processing device 30. For example, the guidance is given to the store clerk or customer by displaying an image for guidance on a display device. The display device may be the touch panel 23 or display 25 of the input device 20, or the first touch panel 32 or second touch panel 33 of the transaction processing device 30, etc.

[0076] The hold release means 3017 is a function that commands the hold server 10 to release the hold information related to the transaction that has been held in the hold server 10, that is, the transaction file. The hold release means 3017 has an operator for receiving instructions to release the hold of the transaction file. The operator is a software key displayed on the first touch panel 32. The operator may also be a hardware key provided on the keyboard 31. The hold release button described later is an example of an operator. When the operator is operated, the hold release means 3017 commands the hold server 10 to release the hold of the transaction file. Specifically, the hold release means 3017 outputs a signal to the hold server 10 that commands the hold server 10 to release the hold of the transaction file.

[0077] The execution means 3018 is a function that settles transactions with customers based on information relating to transactions held in the holding server 10. When the holding server 10 is instructed to release the holding of a transaction file, the transaction file is stored in the second file area 3022. Based on the transaction file stored in the second file area 3022, the execution means 3018 operates the first settlement means 3013 to settle the transaction.

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

[0079] The first business program is a type of application program stored in the main memory 302 or the auxiliary storage device 303. The method of installing the first business program in the main memory 302 or the auxiliary storage device 303 is not particularly limited. 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 the first business program via communication over a network. The recording medium can take any form as long as it can store a program and is readable by the device, such as a CD-ROM or memory card.

[0080] <Functional Configuration of the Hold Server> The hold server 10 functions as a transaction information input means 1011, a hold means 1012, and a hold information output means 1013.

[0081] The transaction information input means 1011 is a function that inputs transaction-related information, i.e., a transaction file, from the transaction processing device 30. Along with the transaction file, the transaction information input means 1011 inputs operator identification information, i.e., an employee code.

[0082] The holding means 1012 is a function that holds transaction information, i.e., transaction files, entered by the transaction information input means 1011. The holding means 1012 stores, i.e., holds, the transaction files in employee-specific folders 1032, which are identified by the employee code entered along with the transaction files.

[0083] The pending information output means 1013 has the function of outputting information related to transactions that have been put on hold by the pending means 1012, i.e., transaction files, to an output destination. The output destination is the settlement device 40 or the transaction processing device 30. The pending information output means 1013 outputs the transaction files that have been put on hold in the employee-specific folder 1032 to the settlement device 40. Alternatively, the pending information output means 1013 outputs the transaction files that have been put on hold in the employee-specific folder 1032 to the transaction processing device 30.

[0084] The functions of the transaction information input means 1011, the holding means 1012, and the holding information output means 1013 are realized by information processing performed by the processor 101 of the holding server 10 in accordance with the second business program.

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

[0086] <Functional Configuration of the Indicator Device> The instruction device 50 has the functions of a storage means 5011, a status confirmation means 5012, a hold confirmation means 5013, and an instruction means 5014.

[0087] The storage means 5011 has the function of storing employee identification information to identify store employees. The employee identification information is an employee code. The storage means 5011 stores in the employee memory 5031 employee codes whose sign-on has been approved by the operator authentication means 3011 of the transaction processing device 30.

[0088] The status confirmation means 5012 is a function that confirms whether the settlement device 40 is able to settle a transaction. The settlement device 40 cannot settle a transaction with the next customer while it is settling a transaction with the previous customer. The status confirmation means 5012 checks the payment in progress flag Fc stored in the third flag memory 4022 of the settlement device 40. If the payment in progress flag Fc is "1", that is, payment is in progress, the status confirmation means 5012 recognizes that the settlement device 40 is unable to settle the transaction. On the other hand, if the payment in progress flag Fc is "0", that is, payment is not in progress, the status confirmation means 5012 recognizes that the settlement device 40 is able to settle the transaction.

[0089] The hold confirmation means 5013 is a function that checks whether or not transaction-related information is being held in the hold server 10. The hold confirmation means 5013 checks whether or not a transaction file is being held in the employee-specific folder 1032 identified by the employee code stored in the employee memory 5031. Specifically, the hold confirmation means 5013 sends the employee code to the hold server 10 and queries whether or not a transaction file is being held in the employee-specific folder 1032 identified by that employee code. The response from the hold server 10 to this query confirms whether or not information related to the transaction is being held.

[0090] The instruction means 5014 is a function that instructs the settlement device 40 to import transaction information. The instruction means 5014 instructs the settlement device 40 to import transaction information when the status confirmation means 5012 confirms that the settlement device 40 is capable of settling the transaction. The instruction means 5014 instructs the settlement device 40 to import transaction information when the hold confirmation means 5013 confirms that transaction information is being held in the hold server 10. The instruction means 5014 instructs the settlement device 40 to import transaction files from the employee-specific folders 1032 identified by the employee codes stored in the employee memory 5031.

[0091] The functions of the instruction device 50 as a storage means 5011, a status confirmation means 5012, a hold confirmation means 5013, and an instruction means 5014 are all realized by information processing performed by the processor 501 in accordance with the third business program.

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

[0093] <Functional Configuration of Payment Devices> The payment device 40 has the functions of a receiving means 4011 and a second payment means 4012.

[0094] The data acquisition means 4011 is a function that acquires transaction information from the holding server 10 in response to an acquisition instruction from the instruction device 50. The data acquisition means 4011 acquires transaction files from the employee-specific folders 1032, which are identified by the employee code instructed by the instruction device 50. The data acquisition means 4011 stores the transaction files acquired from the holding server 10 in the third file area 4021.

[0095] The second payment method 4012 is a function that settles a transaction with the customer, who is the subject of the transaction, acting as the operator, based on the transaction information acquired by the acquisition method 4011. The second payment method 4012 calculates the amount required for settlement based on the transaction information acquired from the holding server 10. The second payment method 4012 calculates the amount required for settlement based on the transaction file information stored in the third file area 4021. The second payment method 4012 settles the transaction with the customer when payment is made according to the payment method. Payment methods include cash, credit card, electronic money, and code payment. The second payment method 4012 supports at least one payment method. For example, if cash is accepted as the payment method, the second payment method 4012 settles the transaction with the customer in cooperation with the automatic change dispenser 43. For example, if cashless payment is accepted as the payment method, the second payment method 4012 settles the transaction with the customer in cooperation with the cashless payment terminal 44.

[0096] The functions of the data acquisition means 4011 and the second settlement means 4012 are realized by information processing performed by the processor 401 in accordance with the fourth business program.

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

[0098] [Explanation of information processing in the payment system] Figures 10 to 19 are flowcharts showing the main information processing steps performed by the holding server 10, transaction processing unit 30, settlement unit 40, and instruction unit 50, respectively. The information processing steps will be described below in the order of transaction processing unit 30, holding server 10, instruction unit 50, and settlement unit 40.

[0099] <Information processing for transaction processing equipment> Figure 10 is a flowchart showing the essential steps of information processing performed by the processor 301 of the transaction processing device 30 according to the first business program. The processor 301 is waiting for a sign-on as ACT101. At this time, the sign-on screen is displayed on the first touch panel 32. The employee who wants to sign on enters their employee code and password on the sign-on screen.

[0100] When the employee code and password are entered, the processor 301 recognizes that a sign-on has been performed. The processor 301 proceeds to ACT 102. The processor 301 performs operator authentication as ACT 102. That is, the processor 301 controls the output of the operator authentication event. This control causes the operator authentication event to be output from the communication interface 305. The operator authentication event is sent to the hold server 10 via the communication network 60. The operator authentication event includes the employee code and password entered during the sign-on operation. The hold server 10 searches the employee master 1031. If the combination of employee code and password stored in the employee master 1031 matches the combination of employee code and password included in the operator authentication event, the hold server 10 checks whether the employee identified by the employee code included in the operator authentication event is currently signed on to another transaction processing device 30. If the employee is not currently signed on, the hold server 10 stores information indicating that the employee identified by the employee code included in the operator authentication event is currently signed on. The pending server 10 also returns an acceptance response. The acceptance response signal is output via the communication network 60 to the transaction processing device 30, the source of the operator authentication event.

[0101] The processor 301 of the transaction processing device 30, which has performed operator authentication, waits for an acceptance response as ACT103. If an acceptance response is not received, for example, if the combination of employee code and password entered on the sign-on screen does not match a combination set in the employee master 1031, or if the employee identified by the employee code is currently signing on to another transaction processing device 30, the processor 301 terminates information processing as an error.

[0102] In ACT103, if the processor 301 receives an acceptance response signal from the holding server 10, the processor proceeds to ACT104. In ACT104, the processor 301 stores the employee code entered on the sign-on screen in the employee memory 3025.

[0103] The processor 301, having stored the employee code, proceeds to ACT105. The processor 301 makes a configuration request to the instruction device 50 as ACT105. That is, the processor 301 controls the output of the configuration request event. This control causes the configuration request event to be output from the communication interface 305. The configuration request event is transmitted via the communication network 60 to the instruction device 50 in the same settlement lane L. When the instruction device 50 receives the configuration request event, it returns an acceptance response. The acceptance response signal is output via the communication network 60 to the transaction processing device 30 that sent the configuration request event.

[0104] The processor 301 of the transaction processing device 30, which made the setting request, waits for an acceptance response as ACT106. If an acceptance response is not received, for example, if the power to the instruction device 50 is off, the processor 301 terminates information processing as an error.

[0105] In ACT106, if the processor 301 receives an acceptance response signal from the instruction device 50, it proceeds to ACT107. The processor 301 sets the employee code in the instruction device 50 as ACT107. That is, the processor 301 controls the output of the code setting event. This control causes the code setting event to be output from the communication interface 305. The code setting event is transmitted to the instruction device 50 in the same settlement lane L via the communication network 60. The code setting event includes the employee code stored in the employee memory 3025. The instruction device 50 stores the employee code included in the code setting event in the employee memory 5031.

[0106] Once processor 301 has finished processing ACT101 through ACT107, transaction processing unit 30 enters a state where sign-on has been approved. At this point, processor 301 realizes its function as operator authentication means 3011 through processing ACT101 through ACT107.

[0107] Once the sign-on is approved, the processor 301 proceeds to ACT108. The processor 301 then executes the main information processing as ACT108. The main information processing involves information processing related to the functions of the input information acquisition means 3012, the first settlement means 3013, the operator acquisition means 3014, the transaction information output means 3015, the guidance means 3016, the hold release means 3017, and the execution means 3018. Details of the main information processing will be described later.

[0108] Processor 301, which has started main information processing, checks whether sign-off has been performed as ACT109. If sign-off has not been performed, processor 301 continues main information processing.

[0109] When the processor 301 detects that a sign-off operation has been performed by inputting an operation to the first touch panel 32, it proceeds to ACT 110. The processor 301 makes a clear request to the instruction device 50 as ACT 110. That is, the processor 301 controls the output of the clear request event. This control causes the clear request event to be output from the communication interface 305. The clear request event is transmitted to the instruction device 50 in the same settlement lane L via the communication network 60. When the instruction device 50 receives the clear request event, it clears the employee code stored in the employee memory 5031. The instruction device 50 then returns an acceptance response. The acceptance response signal is output via the communication network 60 to the transaction processing device 30 that sent the clear request event.

[0110] The processor 301 of the transaction processing unit 30 that made the clear request waits for an acceptance response as ACT111. If an acceptance response is not received, for example if the instruction unit 50 is down due to a malfunction, the processor 301 returns to ACT109. In other words, the processor 301 invalidates the sign-off.

[0111] In ACT111, if the processor 301 receives an acceptance response signal from the instruction device 50, it proceeds to ACT112. The processor 301 notifies the hold server 10 of the sign-off as ACT112. That is, the processor 301 controls the output of the sign-off notification event. This control causes the sign-off notification event to be output from the communication interface 305. The sign-off notification event is sent to the hold server 10 via the communication network 60. The sign-off notification event includes the employee code stored in the employee memory 3025. The hold server 10 clears the information indicating that the employee identified by the employee code included in the sign-off notification event is currently signed on.

[0112] The processor 301 of the transaction processing unit 30, which notified the sign-off, proceeds to ACT113. As ACT113, the processor 301 clears the employee code stored in the employee memory 3025. With this, the processor 301 completes the information processing procedure shown in the flowchart of Figure 10.

[0113] Next, the main information processing in ACT108 will be described. The main information processing includes the first information processing, the second information processing, and the third information processing. The processor 301 can execute the first information processing, the second information processing, and the third information processing in parallel.

[0114] Figures 11 to 13 are flowcharts showing the main steps of the first information processing. The processor 301 waits for a command to start registration, as ACT121 in Figure 11. Customers who have gathered their purchased items from the sales floor move to the checkout area. There, customers place their purchased items on the counter 82 of the checkout counter 80 in an empty aisle PA. When a store employee standing in space SP arrives at the checkout area, the employee commands the start of registration. For example, the employee touches the start button displayed on the touch panel 23 of the input device 20. This operation serves as the command to start registration. Upon receiving this command, the processor 301 proceeds to ACT122. As ACT122, the processor 301 sets the screen of the touch panel 23 as the registration screen. The registration screen includes, for example, a detail area that displays the product name, purchase quantity, unit price, discount amount, and sales amount of the purchased items in a single transaction, and a total area that displays the total purchase quantity and total sales amount of the purchased items in a single transaction.

[0115] Once the store clerk confirms that the registration screen is displayed, they begin registering the purchased items placed at the checkout counter 80. Specifically, the clerk scans the barcode attached to the purchased item using the stationary scanner 21 or handheld scanner 22 of the input device 20. By scanning the barcode, the product code of the purchased item is entered into the transaction processing device 30 via the input device interface 310. If the purchased item does not have a barcode, the clerk displays a list of barcode-less items on the touch panel 23 of the input device 20. The clerk then selects the purchased item from this list. Through this operation, the product code of the barcode-less purchased item is entered into the transaction processing device 30 via the input device interface 310.

[0116] The processor 301, using the touch panel 23 as the registration screen, proceeds to ACT123. The processor 301 waits for the registration of purchased items as ACT123. When the product code is entered from the input device 20 via the input device interface 310, the processor 301 determines that the purchased items have been registered. The processor 301 proceeds to ACT124. The processor 301 creates a transaction file in the first file area 3021 as ACT124. Hereafter, the transaction file generated in ACT124 will be referred to as the first transaction file.

[0117] Processor 301, having created the first transaction file, proceeds to ACT125. Processor 301 processes the product sales data as ACT125. This process reads the product name, unit price, etc., of the product identified by the entered product code from the product master, and generates product sales data for the purchased product, including the product code, product name, unit price, purchase quantity, sales amount, etc. After generating the product sales data for the purchased product, Processor 301 proceeds to ACT126. Processor 301 stores the product sales data for that purchased product in the first transaction file as ACT126.

[0118] Processor 301 checks whether the next purchase item has been registered as ACT127. If the next purchase item has not been registered, Processor 301 proceeds to ACT128. Processor 301 checks whether the payment button has been pressed as ACT128. The payment button is, for example, a software key displayed on the registration screen. The store clerk who has registered all of the customer's purchase items touches the payment button.

[0119] If the payment button is not selected in ACT128, the processor 301 returns to ACT127. In this way, the processor 301 waits in ACT127 and ACT128 for the next purchase item to be registered or for the payment button to be selected.

[0120] When a purchased item is registered while in the waiting state of ACT127 and ACT128, the processor 301 returns to ACT125. The processor 301 then performs the processing of ACT125 and ACT126 in the same manner as described above. Thus, each time a store employee operates the stationary scanner 21, handheld scanner 22, or touch panel 23 of the input device 20 to input data for a purchased item placed on the checkout counter 80, the processor 301 generates product sales data for that purchased item based on the information relating to that item, i.e., the product code, and stores it in the first transaction file.

[0121] When the payment button is detected to have been pressed while in the waiting state of ACT127 and ACT128, the processor 301 proceeds to ACT129. As ACT129, the processor 301 checks the payment in progress flag Fa. If payment has not been made in the transaction processing unit 30, the payment in progress flag Fa is "0". When the payment in progress flag Fa is "0", the processor 301 proceeds to ACT141 in Figure 12. The processing from ACT141 onwards will be described later.

[0122] If the payment in progress flag Fa is "1" in ACT129, meaning that payment is being processed in the transaction processing unit 30, the processor 301 proceeds to ACT130. In ACT130, the processor 301 checks the pending flag Fb. If no information related to the transaction of the previous customer that settled in the same settlement lane L is being held in the holding server 10, the pending flag Fb is "0". When the pending flag Fb is "0", the processor 301 proceeds to ACT151 in Figure 13. The processing from ACT151 onwards will be described later.

[0123] If the pending flag Fb in ACT130 is "1", meaning that information related to the transaction of the previous customer who made a payment in the same payment lane L is being held in the pending server 10, the processor 301 proceeds to ACT131. The processor 301 notifies that payment is not possible as ACT131. For example, the processor 301 notifies the store clerk by displaying information indicating that payment is not possible on the touch panel 23 of the input device 20. The store clerk makes the customer wait until payment becomes possible. Then, when the store clerk determines by visual inspection that payment is possible, they press the payment button again.

[0124] Processor 301 waits for the payment button to be pressed again as ACT132. Upon detecting that the payment button has been pressed, processor 301 returns to ACT129. Processor 301 executes the processes from ACT129 onward in the same manner as described above. Therefore, when the payment in progress flag Fa changes from "1" to "0", indicating that payment has not been made in the transaction processing unit 30, processor 301 proceeds to ACT141 in Figure 12. Alternatively, when the pending flag Fb changes from "1" to "0", indicating that information related to the previous customer's transaction is no longer being held in the pending server 10, processor 301 proceeds to ACT151 in Figure 13.

[0125] When the payment flag Fa is "0", meaning that payment has not yet been made in the transaction processing unit 30, if the payment button is pressed, the processor 301 proceeds to ACT141 in Figure 12. The processor 301 retrieves the first transaction file stored in the first file area 3021 as ACT141. Then, the processor 301 saves the first transaction file as ACT142 in the second file area 3022.

[0126] Processor 301, as ACT143, rewrites the payment in progress flag Fa in the first flag memory 3023 to "1". Processor 301 also, as ACT144, displays on the touch panel 23 and display 25 of the input device 20 that payment is possible. Then, as ACT145, processor 301 clears the first file area 3021. With this, processor 301 terminates the first information processing.

[0127] Thus, the customer moves to the area where the transaction processing device 30 is installed. There, they make payment based on the transaction file data stored in the second file area 3022. Hereafter, the transaction file stored in the second file area 3022 will be referred to as the second transaction file.

[0128] On the other hand, if the payment flag Fa is set to "1" but the pending flag Fb is set to "0", and the payment button is pressed, the processor 301 proceeds to ACT151 in Figure 13. The processor 301 retrieves the employee code stored in the employee memory 3025 as ACT151. The processor 301 also retrieves the first transaction file stored in the first file area 3021 as ACT152.

[0129] Processor 301, having obtained the employee code and the first transaction file, proceeds to ACT153. Processor 301 controls the output of the pending event as ACT153. This control causes the pending event to be output from the communication interface 305. The pending event is sent to the pending server 10 via the communication network 60. The pending event includes the employee code and the first transaction file.

[0130] The processor 301 of the transaction processing unit 30, which output the pending event, proceeds to ACT154. Processor 301 sets the pending flag Fb to "1" as ACT154. Processor 301 also clears the first file area 3021 as ACT155. With this, processor 301 terminates the first information processing.

[0131] In ACT143 in Figure 12, when the payment flag Fa becomes "1", the processor 301 performs the second information processing. Figure 14 is a flowchart showing the main steps of the second information processing. Processor 301 waits for the payment flag Fa to become "1" as ACT161. When the payment flag Fa becomes "1", processor 301 proceeds to ACT162. Processor 301 sets the screen of the second touch panel 33 as the payment selection screen as ACT162. The payment selection screen includes a group of selection buttons for each payment method. The selection buttons include a cash button, a credit button, an electronic money button, a code payment button, etc. The payment selection screen also includes a total area that displays the total purchase quantity and the total sales amount of the purchased goods in a single transaction. The total area displays the total purchase quantity and the total sales amount calculated based on the product sales data of the purchased goods stored in the second transaction file.

[0132] After moving to the area where the transaction processing unit 30 is installed and checking the payment selection screen, the customer touches the button for their desired payment method. For example, a customer who wishes to pay with cash touches the cash button. For example, a customer who wishes to pay with a credit card touches the credit button. For example, a customer who wishes to pay with electronic money touches the electronic money button. For example, a customer who wishes to pay with QR code payment touches the QR code payment button.

[0133] Processor 301, with the second touch panel 33 screen set to the payment selection screen, proceeds to ACT163. Processor 301 waits for a payment method to be selected as ACT163. Once a payment method is selected by touch operation on the selection buttons, processor 301 proceeds to ACT164. Processor 301 obtains the payment code for the selected payment method as ACT164. After obtaining the payment code, processor 301 proceeds to ACT165. Processor 301 waits for the payment to be made as ACT165.

[0134] Customers who have selected a payment method pay the amount using that method. For example, a customer who has selected cash payment inserts cash into the automatic change dispenser 35. A customer who has selected credit card payment has the cashless payment terminal 36's reader read the credit card data. A customer who has selected electronic money payment has the cashless payment terminal 36's reader read the data on their electronic money medium. A customer who has selected code payment has the cashless payment terminal 36's scanner read the barcode or two-dimensional data code for code payment.

[0135] Once processor 301 confirms that payment has been made using the payment method identified by the payment code, it proceeds to ACT 166. Processor 301 executes the transaction settlement process as ACT 166. Specifically, if the payment code is a cash payment code, processor 301 settles the transaction with the cash inserted into the automatic change dispenser 35. If the payment code is a credit card payment code, processor 301 settles the transaction with the credit card data read by the cashless payment terminal 36. If the payment code is an electronic money payment code, processor 301 settles the transaction with the electronic money data read by the cashless payment terminal 36. If the payment code is a code payment code, processor 301 settles the transaction with the barcode or two-dimensional data code read by the cashless payment terminal 36. Since all of these settlement processes are well known, detailed explanations are omitted.

[0136] Once the payment processing is complete, processor 301 proceeds to ACT167. As ACT167, processor 301 drives printer 34 to issue a receipt. The receipt records details such as the name, price, quantity, and total amount of the purchased items.

[0137] The processor 301 of the transaction processing device 30, which issued the receipt, proceeds to ACT168. The processor 301 saves the data of the second transaction file, that is, the data of the goods purchased by the customer who completed the payment, as ACT168. The data is saved to, for example, the auxiliary storage device 303. The data may also be saved to the main memory 302. Alternatively, the second transaction file may be sent to the POS server via the communication interface 305 and saved on the POS server. It may also be saved on the hold server 10 instead of the POS server.

[0138] Processor 301, having saved the data in the second transaction file, proceeds to ACT169. Processor 301 clears the second file area 3022 as ACT169. Processor 301 also rewrites the payment in progress flag Fa to "0" as ACT170. With this, Processor 301 terminates the second information processing.

[0139] In ACT154 in Figure 13, when the pending flag Fb becomes "1", the processor 301 executes the third information processing. Figure 15 is a flowchart showing the main steps of the third information processing. Processor 301 waits for the pending flag Fb to become "1" as ACT171. When the pending flag Fb becomes "1", processor 301 proceeds to ACT172. Processor 301 uses the screen of the first touch panel 32 as a guidance screen as ACT172. The guidance screen displays guidance for when the customer is directed to the payment device 40 and guidance for when the transaction processing device 30 is the payment destination. A release button is also displayed as an operator to receive instructions to release the pending transaction file.

[0140] After reviewing the guidance screen, the clerk determines the payment destination for the customer whose transaction file is on hold at the hold server 10. For example, if another customer is paying at the transaction processing device 30, but no customer is paying at the settlement device 40, the clerk will determine the settlement device 40 as the payment destination. For example, if another customer is still paying at the settlement device 40, but the customer who was paying at the transaction processing device 30 has finished paying, the clerk will determine the transaction processing device 30 as the payment destination. If the transaction processing device 30 is determined as the payment destination, the clerk touches the hold release button. In contrast, if the settlement device 40 is determined as the payment destination, the clerk does not perform any special operation.

[0141] The processor 301 of the transaction processing unit 30, which displays the guidance screen, proceeds to ACT173. Processor 301 checks whether or not it has received a release notification event as ACT173. If it has not received a release notification event, processor 301 proceeds to ACT174. Processor 301 checks whether or not the hold release button has been pressed as ACT174. If the hold release button has not been pressed, processor 301 returns to ACT173. In this way, processor 301 waits for a release notification event to be received or for the hold release button to be pressed in ACT173 and ACT174.

[0142] As will be explained in more detail later, the release notification event is sent from the holding server 10 to the transaction processing unit 30 when the transaction file that was being held on the holding server 10 is sent to the settlement device 40. If the processor 301 receives the release notification event while in the waiting state for ACT173 and ACT174, it proceeds to ACT175. As ACT175, the processor 301 displays payment instructions on the touch panel 23. The payment instructions are information that instructs the store clerk to tell the customer to pay the amount at the settlement device 40. After the store clerk confirms the payment instructions, they guide the customer to the settlement device 40. The customer moves to the settlement device 40 according to the store clerk's instructions and makes the payment.

[0143] The processor 301 of the transaction processing unit 30, which displayed the payment instructions, proceeds to ACT176. Processor 301 sets the pending flag Fb to "0" as ACT176. With this, processor 301 terminates the third information processing.

[0144] On the other hand, if the hold release button is pressed while ACT173 or ACT174 is in standby mode, processor 301 proceeds to ACT177. Processor 301 checks the payment in progress flag Fa as ACT177. If the payment in progress flag Fa is "1", meaning that the previous customer is making a payment in the transaction processing unit 30, processor 301 returns to ACT173. Processor 301 invalidates the input of the hold release button and returns to the standby mode for ACT173 and ACT174.

[0145] If the payment flag Fa in ACT177 is "0", meaning there are no customers currently settling in the transaction processing unit 30, the processor 301 proceeds to ACT178. The processor 301 retrieves the employee code from the employee memory 3025 as ACT178. Then, the processor 301 controls the output of the hold release event as ACT179. This control causes the hold release event to be output from the communication interface 305. The hold release event is sent to the hold server 10 via the communication network 60. The hold release event includes the employee code retrieved from the employee memory 3025.

[0146] As will be explained in more detail later, the hold server 10, upon receiving the hold release event, sends the held transaction file to the transaction processing unit 30. The processor 301, which controls the output of the hold release event, then waits to receive the transaction file as ACT180. Upon receiving the transaction file via the communication interface 305, the processor 301 proceeds to ACT181. The processor 301 saves the transaction file as ACT181 in the second file area 3022. Incidentally, the received transaction file is the same transaction file that was output to the hold server 10 in ACT143 in Figure 14.

[0147] After saving the transaction file to the second file area 3022, the processor 301 proceeds to ACT182. As ACT182, the processor 301 displays on the touch panel 23 and display 25 of the input device 20 that payment is possible. Then, as ACT133, the processor 301 sets the payment in progress flag Fa to "1" and the pending flag Fb to "0". After that, the processor 301 proceeds to ACT152 in Figure 14. That is, when the transaction file that was pending in the pending server 10 is returned to the transaction processing device 30, the processor 301 executes the processes of ACT152 to ACT160 in Figure 14 in the same way as described above. The processor 301 sets the screen of the second touch panel 33 to the payment selection screen. Then, when the customer selects a payment method and the payment is made using that method, the processor 301 executes the settlement process and issues a receipt. Thus, the customer can pay the amount by operating the transaction processing device 30 themselves.

[0148] Here, the processor 301 of the transaction processing device 30 realizes the function of input information acquisition means 3012 through the processing of ACT113 to ACT118 in Figure 11. The processor 301 realizes the function of first settlement means 3013 through the processing of ACT152 to ACT156 in Figure 14. The processor 301 realizes the function of operator acquisition means 3014 through the processing of ACT141 in Figure 13. The processor 301 realizes the function of transaction information output means 3015 through the processing of ACT142 and ACT143 in Figure 13. The processor 301 realizes the function of guidance means 3016 through the processing of ACT134 in Figure 12 and ACT175 and ACT182 in Figure 15. The processor 301 realizes the function of hold release means 3017 through the processing of ACT174 to ACT179 in Figure 15. The processor 301 realizes its function as an execution means 3018 through the processing of ACT180 to ACT183 in Figure 15 and ACT152 to ACT156 in Figure 14.

[0149] <Information processing on the holding server> Figure 16 is a flowchart showing the essential steps of the information processing performed by the processor 101 of the hold server 10 according to the second business program. Hereinafter, this information processing will be referred to as the fourth information processing. The processor 101 is waiting for a hold event as ACT201. A hold event is output from the transaction processing device 30 to the hold server 10 when the payment in progress flag Fa of the transaction processing device 30 is "1" and the hold flag Fb is "0", as explained using Figures 11 and 13. The hold event includes the employee code and the transaction file.

[0150] Upon receiving a pending event via the communication interface 105, the processor 101 proceeds to ACT202. As ACT202, the processor 101 retrieves the employee code from the pending event. Then, as ACT203, the processor 101 saves the transaction file contained in the pending event to the employee-specific folder 1032 identified by that employee code.

[0151] The processor 101 of the hold server 10, which has saved the transaction file, proceeds to ACT204. Processor 101 checks whether it has received an import request event as ACT204. If it has not received an import request event, processor 101 proceeds to ACT205. Processor 101 checks whether it has received a hold release event as ACT205. If it has not received a hold release event, processor 101 returns to ACT204. In this way, processor 101 waits to receive either an import request event or a hold release event in ACT204 and ACT205.

[0152] As explained using Figure 15, the hold release event is output from the transaction processing device 30 to the hold server 10 when the hold release button is pressed in the transaction processing device 30 while the payment flag Fa is in the "1" state. The hold release event includes the employee code. On the other hand, the import request event is sent from the settlement device 40 to the hold server 10, as will be described in detail later. The import request event also includes the employee code.

[0153] When ACT204 and ACT205 are in a waiting state and an import request event is received, processor 101 proceeds to ACT206. Processor 101 obtains the employee code from the import request event as ACT206. Then, as ACT207, processor 101 obtains the transaction file held in the employee-specific folder 1032 identified by that employee code. Processor 101 sends the obtained transaction file to the settlement device 40 as ACT208.

[0154] Processor 101, which sent the transaction file, proceeds to ACT209. Processor 101 controls the transmission of a release notification event as ACT209. This control causes a release notification event to be output from the communication interface 105. The release notification event is sent to the transaction processing device 30 via the communication network 60. Processor 101 also deletes the transaction file as ACT210. That is, processor 101 deletes the transaction file that was stored in the employee-specific folder 1032, which is identified by the employee code obtained in ACT206. With this, processor 101 terminates the fourth information processing.

[0155] When a hold release event is received while ACT204 and ACT205 are in standby mode, processor 101 proceeds to ACT211. Processor 101 obtains the employee code from the hold release event as ACT211. Then, as ACT212, processor 101 obtains the transaction file that is on hold in the employee-specific folder 1032 identified by that employee code. Processor 101 sends the obtained transaction file to the transaction processing unit 30 as ACT213.

[0156] Processor 101, which sent the transaction file, proceeds to ACT214. Processor 101 deletes the transaction file as ACT214. That is, processor 101 deletes the transaction file that was stored in the employee-specific folder 1032, which is identified by the employee code obtained in ACT211. With this, processor 101 terminates the fourth information processing.

[0157] Here, the processor 101 of the hold server 10 realizes the function of a transaction information input means 1011 through the processing of ACT201 in Figure 16. The processor 101 realizes the function of a hold means 1012 through the processing of ACT202 and ACT203 in Figure 16. The processor 101 realizes the function of a hold information output means 1013 through the processing of ACT204 to ACT214 in Figure 16.

[0158] <Information processing of the indicator device> Figure 17 is a flowchart showing the essential steps of the information processing performed by the processor 501 of the instruction device 50 according to the fourth business program. Hereinafter, this information processing will be referred to as the fifth information processing. The processor 501 awaits a configuration request event as ACT 501. As explained using Figure 10, the configuration request event is sent from the transaction processing device 30, which has approved sign-on, to the instruction device 50. The configuration request event includes an employee code.

[0159] When processor 501 receives a configuration request event, it proceeds to ACT302. Processor 501 returns an acceptance response as ACT302. Then processor 501 waits for a code configuration event as ACT303. When it receives a code configuration event, processor 501 retrieves the employee code from the code configuration event as ACT304. Then processor 501 stores that employee code in employee memory 5031 as ACT305.

[0160] The processor 501, which has stored the employee code, proceeds to ACT306. The processor 501 controls the output of the status confirmation event as ACT306. This control causes the status confirmation event to be output from the communication interface 504. The status confirmation event is transmitted to the payment device 40 in the same payment lane L via the communication network 60.

[0161] As will be explained in more detail later, the settlement device 40, upon receiving the status confirmation event, sends a response signal including the payment in progress flag Fc to the instruction device 50. The processor 501, which controls the output of the status confirmation event, proceeds to ACT307. The processor 501 checks the payment in progress flag Fc included in the response signal as ACT307. If the payment in progress flag Fc is "1", meaning that the settlement device 40 is in the process of paying the amount, i.e., the transaction is being settled, the processor 501 skips the processing of ACT308 to ACT310 and proceeds to ACT311.

[0162] In contrast, if the payment flag Fc is "0", meaning that payment is not in progress at the settlement device 40, i.e., the transaction is not being settled, the processor 501 proceeds to ACT308. The processor 501 controls the output of the hold confirmation event as ACT308. This control causes the hold confirmation event to be output from the communication interface 504. The hold confirmation event is sent to the hold server 10 via the communication network 60. The hold confirmation event includes the employee code stored in the employee memory 5031.

[0163] Upon receiving a hold confirmation event, the hold server 10 determines whether a transaction file is stored in the employee-specific folder 1032 identified by the employee code included in the hold confirmation event, that is, whether the transaction file is on hold. If the transaction file is not on hold, a hold unresponsive signal is sent to the instruction device 50. If the transaction file is on hold, a hold response signal is sent to the instruction device 50.

[0164] Processor 501, which controlled the output of the pending confirmation event, proceeds to ACT309. Processor 501 checks whether or not it received a pending response signal as ACT309. If it did not receive a pending response signal, processor 301 skips processing in ACT310 and proceeds to ACT311.

[0165] In response to this, if a pending response signal is received, the processor 501 proceeds to ACT310. The processor 501 controls the output of the capture instruction event as ACT310. This control causes the capture instruction event to be output from the communication interface 504. The capture instruction event is transmitted to the settlement device 40 in the same settlement lane L via the communication network 60. After controlling the output of the capture instruction event, the processor 501 proceeds to ACT311.

[0166] Thus, if the payment in progress flag Fc is "1" in ACT307, or if a pending no response signal is received in ACT309, or if the output of the capture instruction event is controlled in ACT310, the processor 501 proceeds to ACT311. The processor 501 checks whether or not a clear request event has been received as ACT311. As explained with reference to Figure 10, a clear request event is output from the transaction processing unit 30 to the instruction unit 50 when a sign-off operation is performed in the transaction processing unit 30 of the same settlement lane L.

[0167] If no clear request event is received, the processor 501 returns to ACT306. Thereafter, the processor 501 executes the processing from ACT306 onwards in the same manner as described above. That is, the processor 501 outputs a status confirmation event to the payment device 40. After confirming that the payment in progress flag Fc of the payment device 40 is "0", the processor 501 outputs a hold confirmation event to the hold server 10. After receiving a hold confirmation signal from the hold server 10 in response to the hold confirmation event, the processor 501 outputs an import instruction event to the payment device 40. If the payment in progress flag Fc of the payment device 40 is "1", or if a hold unresponsive signal is received from the hold server 10, the processor 501 does not output an import instruction event. The processor 501 repeatedly executes the processing from ACT306 to ACT311 described above until a clear request event is received.

[0168] When processor 501 receives a clear request event, it proceeds to ACT312. Processor 501 clears the employee code stored in employee memory 5031 as ACT312. Processor 501 also returns an acceptance response as ACT313 to the transaction processing unit 30, which was the source of the clear request event. With this, processor 501 terminates the fifth information processing.

[0169] Here, the processor 501 of the instruction device 50 realizes the function of a storage means 5011 through the processing of ACT301 to ACT305 in Figure 17. The processor 501 realizes the function of a status confirmation means 5012 through the processing of ACT306 and ACT307 in Figure 17. The processor 501 realizes the function of a hold confirmation means 5013 through the processing of ACT308 and ACT309 in Figure 17. The processor 501 realizes the function of an instruction means 5014 through the processing of ACT310 in Figure 17.

[0170] <Information processing for payment devices> Figures 18 and 19 are flowcharts showing the main steps of the information processing performed by the processor 401 of the payment device 40 according to the third business program. Hereinafter, this information processing will be referred to as the sixth information processing. The processor 401 is waiting for a status confirmation event as ACT401. As explained using Figure 17, the status confirmation event is output periodically from the instruction device 50 to the payment device 40.

[0171] Upon receiving a status confirmation event via the communication interface 405, the processor 401 proceeds to ACT402. As ACT402, the processor 401 checks the payment flag Fc stored in the third flag memory 4022. If the payment flag Fc is "1", meaning the settlement device 40 is in the process of paying, the processor 401 proceeds to ACT403. As ACT403, the processor 401 controls the output of a negative response. This control causes a negative response signal to be output from the communication interface 405. The negative response signal is transmitted via the communication network 60 to the instruction device 50 in the same settlement lane L. The negative response signal contains the value of the payment flag Fc, i.e., "0". Having controlled the output of the negative response, the processor 401 terminates the sixth information processing.

[0172] In ACT402, if the payment in progress flag Fc is "0", meaning the payment device 40 is not currently paying, the processor 401 proceeds to ACT404. The processor 401 controls the output of the acceptance response as ACT404. This control causes the acceptance response signal to be output from the communication interface 405. The acceptance response signal is transmitted via the communication network 60 to the instruction device 50 in the same payment lane L. The acceptance response event includes the value of the payment in progress flag Fc, i.e., "1".

[0173] The processor 401, which controls the output of the permission response, proceeds to ACT405. The processor 401 waits for an import instruction event as ACT405. As explained with reference to Figure 17, the import instruction event is output from the instruction device 50 when the instruction device 50 receives a pending response signal from the pending server 10. The import instruction event includes the employee code. Conversely, if the instruction device 50 receives a pending no response signal from the pending server 10, the import instruction event is not output. If the processor 401 does not receive an import instruction event within a predetermined time after controlling the output of the permission response event, it terminates the sixth information processing step.

[0174] If a capture instruction event is received within a predetermined time after controlling the output of the permission response event, the processor 401 proceeds to ACT406. The processor 401 obtains the employee code from the capture instruction event as ACT406. The processor 401 controls the output of the capture request event as ACT407. This control causes the capture request event to be output from the communication interface 405. The capture request event is sent to the holding server 10 via the communication network 60. The capture request event includes the employee code obtained in ACT406.

[0175] As explained using Figure 16, the holding server 10, upon receiving an import request event, sends the transaction file stored in the employee-specific folder 1032, identified by the employee code included in the import request event, to the settlement device 40. The processor 401 then waits for the transaction file as ACT408. Upon receiving the transaction file via the communication interface 405, the processor 401 proceeds to ACT409. The processor 401 saves the transaction file in the third file area 4021 as ACT409. The processor 401 also sets the payment in progress flag Fc in the third flag memory 4022 to "1" as ACT410.

[0176] Subsequently, the processor 401 proceeds to ACT411 in Figure 19. As ACT411, the processor 401 sets the touch panel 41 screen as the details confirmation screen. The details confirmation screen, like the registration screen, includes a details area and a total area. Based on the product sales data of the transaction file stored in the third file area 4021, the processor 401 displays the product name, purchase quantity, unit price, discount amount, and sales amount of the purchased products in a single transaction in the details area. The processor 401 also displays the total purchase quantity and the total sales amount of the purchased products in the total area. The details confirmation screen displays a confirmation button. The confirmation button is a software key. After confirming the contents of the details confirmation screen, the customer touches the confirmation button.

[0177] After displaying the details confirmation screen, processor 401 proceeds to ACT413. Processor 401 waits for the confirmation button to be pressed as ACT413. Upon detecting that the confirmation button has been pressed via a signal from touch panel 41, processor 401 proceeds to ACT414. Processor 401 sets the touch panel 41 screen to the payment selection screen as ACT414. The payment selection screen is the same as the payment selection screen displayed on the second touch panel 33 of the transaction processing unit 30 in the processing of ACT152 in Figure 14.

[0178] After viewing the payment selection screen, customers touch the button corresponding to their desired payment method. For example, a customer who wishes to pay with cash touches the cash button. A customer who wishes to pay with a credit card touches the credit button. A customer who wishes to pay with electronic money touches the electronic money button. A customer who wishes to pay with QR code payment touches the QR code payment button.

[0179] Once the touch panel 41 screen is set to the payment selection screen, the processor 401 proceeds to ACT 414. Thereafter, the processor 401 performs the same processing as ACT 153 to ACT 158 in Figure 14, as ACT 414 to ACT 419. That is, when a payment method is selected in ACT 414, the processor 401 obtains the payment code for that payment method as ACT 415. Then, as ACT 416, the processor 401 waits for the payment to be made.

[0180] Customers who have selected a payment method pay the amount using that method. For example, a customer who has selected cash payment inserts cash into the automatic change dispenser 43. A customer who has selected credit card payment has the cashless payment terminal 44's reader read the credit card data. A customer who has selected electronic money payment has the cashless payment terminal 44's reader read the data on their electronic money medium. A customer who has selected code payment has the cashless payment terminal 44's scanner read the barcode or two-dimensional data code for code payment.

[0181] Once processor 401 confirms that payment has been made using the payment method identified by the payment code, it proceeds to ACT417. Processor 401 executes the transaction settlement process as ACT417. After completing the settlement process, processor 301 drives printer 42 to issue a receipt as ACT418. Processor 401 also saves the transaction file data stored in the third file area 4021 as ACT419, which is the data of the products purchased by the customer who completed the payment.

[0182] Processor 401, having saved the transaction file data, proceeds to ACT420. Processor 401 clears the third file area 4021 as ACT420. Processor 401 also rewrites the payment in progress flag Fc to "0" as ACT421. With this, Processor 401 completes the sixth information processing.

[0183] Here, the processor 401 of the payment device 40 realizes its function as an input means 4011 through the processing of ACT405 to ACT409 in Figure 18. The processor 401 realizes its function as a second payment means 4012 through the processing of ACT413 to ACT417 in Figure 19.

[0184] [Explanation of the effects and benefits of the payment system] Figure 20 is a sequence diagram of the main data signals exchanged between the transaction processing unit 30, the hold server 10, and the instruction device 50. As mentioned above, when a store employee performs a sign-on operation in the transaction processing unit 30, the transaction processing unit 30 outputs an operator authentication event to the hold server 10 (ACT102). When the hold server 10 returns an acceptance response to this operator authentication event to the transaction processing unit 30, the employee code entered during the sign-on operation is stored in the employee memory 3025 in the transaction processing unit 30. As a result, the store employee who performed the sign-on, i.e., the store employee standing in space SP, is permitted to operate the input device 20 and the transaction processing unit 30. The store employee can input information related to the transaction with the customer, who is the subject of the transaction, by operating the fixed scanner 21, handheld scanner 22, touch panel 23, or keyboard 24 of the input device 20.

[0185] Furthermore, the transaction processing unit 30, which has stored the employee code in the employee memory 3025, outputs a setting request event to the instruction unit 50 (ACT 105). When the instruction unit 50 returns an acceptance response to this setting request event (ACT 302), the transaction processing unit 30 outputs a code setting event to the instruction unit 50 (ACT 107). As a result, the employee code is stored in the employee memory 5031 of the instruction unit 50. This employee code is the same as the employee code stored in the employee memory 3025 of the transaction processing unit 30. In other words, the employee code of the employee who is permitted to operate the input unit 20 and the transaction processing unit 30 is stored in the employee memory 5031 of the instruction unit 50. Thus, when an employee signs on to the transaction processing unit 30, that employee's employee code is stored in the employee memory 5031 of the instruction unit 50. Therefore, the employee does not need to perform any operation to set their own employee code on the instruction unit 50.

[0186] When a sign-off operation is performed in the transaction processing unit 30, a clear request event is output from the transaction processing unit 30 to the instruction unit 50 (ACT 110). In response to this clear request event, the instruction unit 50 clears the employee code stored in the employee memory 5031. The instruction unit 50 also returns an acceptance response to the transaction processing unit 30 (ACT 313). In response to this acceptance response, the transaction processing unit 30 outputs a sign-off notification event to the hold server 10 (ACT 112). The transaction processing unit 30 also clears the employee code stored in the employee memory 3025. Therefore, the employee code of an employee who has signed off and left space SP will not remain in the employee memory 5031 of the instruction unit 50.

[0187] Figure 21 is a sequence diagram of the main data signals exchanged between the instruction device 50, the settlement device 40, and the hold server 10. After the employee code is set in the employee memory 5031 using the procedure described in Figure 20, the instruction device 50 periodically outputs a status confirmation event to the settlement device 40 (ACT306). At this time, if the payment flag Fc in the settlement device 40 is "0", meaning that payment is not in progress, the settlement device 40 returns an acceptance response to the instruction device 50 (ACT404). Upon receiving the acceptance response, the instruction device 50 outputs a hold confirmation event to the hold server 10 (ACT308). The hold confirmation event includes the employee code set in the employee memory 5031. At this time, if the hold server 10 does not have a transaction file on hold in the employee-specific folder 1032 identified by the employee code, the hold server 10 returns a hold no response to the instruction device 50. Upon receiving the hold no response signal, the instruction device 50 does not output an import instruction event to the settlement device 40.

[0188] On the other hand, if a transaction file is held in the employee-specific folder 1032 on the hold server 10, the hold server 10 returns a hold notification to the instruction device 50. Upon receiving this hold notification, the instruction device 50 outputs an import instruction event to the settlement device 40 (ACT310). The transaction instruction event includes the employee code set in the employee memory 5031.

[0189] Upon receiving the transaction instruction event, the settlement device 40 outputs an import request event (ACT407) to the holding server 10. The import request event includes the employee code that was included in the transaction instruction event.

[0190] Upon receiving the import request event, the holding server 10 sends the transaction file held in the employee-specific folder 1032, identified by the employee code included in the import request event, to the settlement device 40 (ACT208). Upon receiving the transaction file, the settlement device 40 initiates settlement based on the data in the transaction file.

[0191] Furthermore, the instruction device 50 periodically sends status confirmation events to the payment device 40 that has initiated the payment process. At this time, the payment device 40 returns a negative response, so the instruction device 50 does not output a hold confirmation event to the hold server 10.

[0192] Once the payment is completed, an acceptance response is returned to the status confirmation event. Therefore, the instruction device 50 again outputs a hold confirmation event to the hold server 10.

[0193] In this manner, the instruction device 50 periodically outputs status confirmation events to the settlement device 40. When the instruction device 50 confirms that the settlement device 40 is not currently settling a transaction, it outputs a hold confirmation event to the hold server 10. When the hold server 10 confirms that the transaction file is being held in the employee-specific folder 1032 identified by the employee code set in the employee memory 5031, the instruction device 50 outputs an import instruction event to the settlement device 40.

[0194] As is clear from the above explanation, the instruction device 50 outputs an import instruction event to the settlement device 40 when the settlement device 40 is not in the process of settling a transaction and when the transaction file is held in the employee-specific folder 1032 identified by the employee code set in the employee memory 5031. Therefore, the timing of outputting the import instruction event can be said to be appropriate.

[0195] Furthermore, the transaction files held in the holding server 10 are created when a store clerk, identified by the employee code set in the employee memory 5031, registers purchased items by operating the input device 20 in the same checkout lane as the instruction device 50. The settlement device 40 receives an import instruction event and imports the transaction file from the holding server 10. Thus, the customer who is the subject of the transaction for which the transaction file was created can settle the transaction by operating the settlement device 40 themselves. Therefore, the store clerk does not need to perform any special operation on the instruction device 50 to import the transaction file into the settlement device 40, and can concentrate on operating the input device 20. Thus, it is possible to provide a settlement system that can efficiently settle transactions by issuing instructions to output transaction-related information at the appropriate time without burdening the store clerk.

[0196] [Other embodiments] In the above embodiment, the instruction device 50 outputs an import instruction event to the settlement device 40 only when the settlement device 40 is not settling a transaction and the transaction file is held in the employee-specific folder 1032 identified by the employee code set in the employee memory 5031. In another embodiment, the instruction device 50 may output an import instruction event to the settlement device 40 when the settlement device 40 is not settling a transaction. That is, the instruction device 50 may output an import instruction event to the settlement device 40 regardless of whether or not a transaction file is held in the holding server 10. In such an embodiment as well, if a transaction file is held in the corresponding employee-specific folder 1032 of the holding server 10, the settlement device 40 can import that transaction file. Therefore, it does not burden the employees and the system provides a settlement system that can settle transactions efficiently.

[0197] In the above embodiment, the employee code of the store clerk was set in the instruction device 50 in conjunction with the store clerk's sign-on operation to the transaction processing device 30. In another embodiment, the employee code of the store clerk may be set by manual operation of the instruction device 50. That is, the store clerk sets their own employee code in the instruction device 50, then stands in space SP and begins inputting information related to the transaction with the customer. Even with this configuration, instructions to output transaction information can be given at the appropriate timing without burdening the store clerk.

[0198] The configuration of the payment system 100 is not limited to that shown in Figure 1. Figure 22 illustrates another payment system 200. In the payment system 200, an input device 20 and a transaction processing device 30 are placed in two adjacent payment lanes La and Lb, respectively, and the payment device 40 and instruction device 50 are shared by the two payment lanes La and Lb. In this payment system 200, the space SP between payment lane La and payment lane Lb is designated as the staff space. That is, the first staff member in charge of payment lane La and the second staff member in charge of payment lane Lb stand, for example, back to back in space SP.

[0199] For such a payment system 200, the instruction device 50 sets the employee code of the first employee and the employee code of the second employee. The instruction device 50 then outputs an import instruction event to the payment device 40 when the payment device 40 is not in the process of settling a transaction and a transaction file is held in the employee-specific folder 1032 identified by at least one of the employee codes. In this way, the same effects as in the above embodiment can be achieved for the payment system 200.

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

[0201] 10...Holding server, 20...Input device, 30...Transaction processing device, 40...Settlement device, 50...Instruction device, 60...Communication network, 100, 200...Settlement system, 1011...Transaction information input means, 1012...Holding means, 1013...Holding information output means, 1031...Employee master, 1032...Employee-specific folders, 2011...Input means, 2012...Termination acceptance means, 3011...Operator authentication means, 3012... Input information acquisition means, 3013... First settlement means, 3014... Operator acquisition means, 3015... Transaction information output means, 3016... Guidance means, 3017... Hold release means, 3018... Execution means, 3025... Employee memory, 4011... Import means, 4012... Second settlement means, 5011... Storage means, 5012... Status confirmation means, 5013... Hold confirmation means, 5014... Instruction means, 5031... Employee memory.

Claims

1. A settlement device that communicates with a holding device that holds transaction information entered by a store employee, and an instruction device that communicates with the settlement device. Includes, The indicator device is, A status confirmation means for confirming whether the settlement device is capable of settling a transaction, An instruction means for instructing the settlement device to take in information relating to the transaction when the settlement device is capable of settling the transaction, It is equipped with, The aforementioned payment device is An acquisition means for acquiring information related to the transaction from the holding device in response to an acquisition instruction from the instruction device, A settlement means that settles a transaction based on the information relating to the transaction acquired by the acquisition means, with the person involved in the transaction acting as the operator. A payment system equipped with the following features.

2. The indicator device is, A holding confirmation means for confirming whether or not information related to the transaction is being held in the holding device, Furthermore, it is equipped with, The payment system according to claim 1, wherein the instruction means of the instruction device instructs the payment device to retrieve the transaction information when the transaction information is being held in the holding device.

3. The indicator device is, A storage means for storing employee identification information to identify employees. Furthermore, it is equipped with, The instruction means of the instruction device instructs the input of transaction information entered by a store employee identified by the store employee identification information, The settlement system according to claim 1, wherein the acquisition means of the settlement device acquires information relating to a transaction entered by an employee identified by the employee identification information from the holding device in response to an acquisition instruction from the instruction device.

4. The payment system according to claim 3, wherein the storage means of the instruction device stores the employee's employee identification information in response to the employee's sign-on operation to a transaction processing device that accepts input of information relating to the transaction.

5. An instruction device that retrieves transaction information from a holding device that holds transaction information entered by a store employee as the operator, and communicates with a settlement device that settles the transaction with the person involved in the transaction as the operator, based on the transaction information, A status confirmation means for confirming whether the settlement device is capable of settling a transaction, An instruction means for instructing the settlement device to take in information relating to the transaction when the settlement device is capable of settling the transaction, An indicator device equipped with the following.

6. A holding confirmation means for confirming whether or not information related to the transaction is being held in the holding device, Furthermore, it is equipped with, The instruction device according to claim 5, wherein the instruction means instructs the settlement device to retrieve the transaction information when the transaction information is being held in the holding device.

7. A computer in an instruction device retrieves transaction information from a holding device that holds transaction information entered by a store employee as the operator, and communicates with a settlement device that settles the transaction based on the transaction information, with the transaction subject as the operator. A status confirmation means for confirming whether the settlement device is capable of settling a transaction, and When the settlement device is capable of settling a transaction, an instruction means for instructing the settlement device to take in information relating to the transaction, A program designed to function as such.

Images