Transaction processing system

Abstract

To easily deal with incomplete electronic payment in response to an operation on a mobile terminal.SOLUTION: A transaction processing system according to an embodiment comprising a mobile terminal equipped with acquisition means for acquiring a product code that identifies a product subject to a transaction, comprises requesting means, output means, detection means, and instruction means. The requesting means requests electronic payment for the transaction from a payment apparatus. The output means outputs transaction data relating to the transaction and including at least first identification data for identifying an electronic payment matter requested by the requesting means from other electronic payment matters, for storage in a storage apparatus. The detection means detects that it has become unclear whether the requested electronic payment has been completed. The instruction means instructs the mobile terminal to output second identification data for identifying the transaction data stored in the storage apparatus for the transaction that is the subject of the electronic payment that has been detected to be unclear.SELECTED DRAWING: Figure 15

Description

Technical Field

[0001] Embodiments of the present invention relate to a transaction processing system Mu .

Background Art

[0002] A transaction processing system that registers transaction details according to operations on a mobile terminal by a customer is known, for example, as a cart POS system or the like In such a system, if electronic payment such as credit card payment or barcode payment is used, the payment process itself can be completed according to the customer's operation on the mobile terminal. And if the payment can be completed in this way, the customer can easily complete the transaction without operating another device such as a cash register

[0003] However, in electronic payment, on the side that requested the payment, there may be a state called "unfinished" where it is unclear whether the payment has been completed. And when it becomes unfinished, the processing on the mobile terminal for the transaction cannot be terminated Due to such circumstances, a countermeasure when it becomes unfinished has been demanded

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] The problem to be solved by the present invention is to provide a transaction processing system that can easily cope with the case where electronic payment according to an operation on a mobile terminal becomes unfinished Mu .

Means for Solving the Problems

[0006] The transaction processing system of the embodiment identifies the product code that is the subject of the transaction. Depending on the customer's actions means of acquisition And the display device and A transaction processing system including a mobile terminal equipped with a request means, First Output means, detection means 、 means of instruction , acquisition means and second output means It includes the following: The requesting means requests electronic settlement of the transaction from the settlement device. First The output means is , take The transaction data related to the withdrawal is output for storage in a memory device. The first output means includes in the output transaction data a second identification data for distinguishing the transaction data from other transaction data stored in the storage device, and a first identification data for distinguishing the electronic settlement request by the request means from other request requests received by the settlement device with respect to the transaction. The detection means detects that it has become unclear whether the electronic payment requested by the requesting means has been completed. The instruction means, in response to the detection means detecting that it has become unclear, The mobile terminal is instructed to display a screen containing the code symbol on the display device. The instruction means uses the code symbol to... Stored by memory Regarding the electronic payment transactions that have become unavailable in the transaction data Second identification data for identifying transaction data What to represent do. The acquisition means reads the code symbol and retrieves transaction data containing the second identification data represented by the code symbol from the storage device. The second output means outputs the first identification data contained in the transaction data acquired by the acquisition means so that it can be viewed by the store clerk. [Brief explanation of the drawing]

[0007] [Figure 1] A schematic diagram of a transaction processing system according to one embodiment. [Figure 2] A schematic diagram showing an example of a store layout that incorporates the transaction processing system according to the embodiment. [Figure 3] A schematic diagram showing the main data structure of data records included in the contact database in the embodiment. [Figure 4] A schematic diagram showing the main data structure of data records included in the member database managed by the member server in the embodiment. [Figure 5] A schematic diagram showing the main data structure of data records included in the product master database in the embodiment. [Figure 6] A block diagram showing the main circuit configuration of the cart terminal in the embodiment. [Figure 7] A perspective view showing an example of the appearance of the cart in the embodiment. [Figure 8]Block diagram showing the main circuit configuration of the virtual POS server in the embodiment. [Figure 9] Schematic diagram showing the main data structure of the data records included in the cart management database in the embodiment. [Figure 10] Schematic diagram showing the main data structure of the data records included in the purchased goods database in the embodiment. [Figure 11] Flowchart showing the procedure of information processing executed by the processor of the cart terminal in the embodiment. [Figure 12] Flowchart showing the procedure of information processing for transaction processing by the processor of the virtual POS server in the embodiment. [Figure 13] Flowchart showing the procedure of information processing for transaction processing by the processor of the virtual POS server in the embodiment. [Figure 14] Flowchart showing the procedure of information processing for transaction processing by the processor of the virtual POS server in the embodiment. [Figure 15] Flowchart showing the procedure of information processing for transaction processing by the processor of the virtual POS server in the embodiment. [Figure 16] Diagram showing an example of the registration screen. [Figure 17] Diagram showing an example of the selection screen in the embodiment. [Figure 18] Diagram showing an example of the specification screen in the embodiment. [Figure 19] Diagram showing an example of the settlement screen when barcode settlement is specified in the embodiment. [Figure 20] Diagram showing an example of the second confirmation screen in the embodiment. [Figure 21] Diagram showing an example of the scanning screen in the embodiment. [Figure 22] Flowchart showing a modification example of information processing by the processor of the virtual POS server in the embodiment.

Mode for Carrying Out the Invention

[0008] An example of an embodiment will be described below with reference to the drawings. The transaction processing system of this embodiment processes transactions involving the buying and selling of goods through display sales in stores.

[0009] Figure 1 is a schematic diagram of the store system 1 according to this embodiment. Figure 2 is a schematic diagram showing an example of a store layout in which the store system 1 has been introduced. As shown in Figure 1, the store system 1 includes a shopping cart terminal 10, a store server 20, a virtual POS server 30, a manned checkout machine 40, a self-checkout machine 50, a beacon transmitter 60, and a store employee terminal 70. The shopping cart terminal 10, store server 20, virtual POS server 30, manned checkout machine 40, self-checkout machine 50, and store employee terminal 70 are able to communicate with each other via a communication network 2. However, the shopping cart terminal 10 is connected to the communication network 2 via wireless communication with an access point 2a. It is desirable that the access point 2a is positioned so that any shopping cart terminal 10 located anywhere in the store where customer access is permitted can communicate with any of the access points 2a. The virtual POS server 30 can use the payment services and electronic receipt services provided by the payment server 3 and the electronic receipt server 4 directly via the communication network 2, or via the store server 20. The virtual POS server 30 can also access the member database managed by the member server 5 via the communication network 2. The payment server 3 processes information for electronic payment in response to payment requests received via the communication network 2. In other words, the payment server 3 is an example of a payment device.

[0010] The store server 20, virtual POS server 30, manned cashier 40, or self-checkout machine 50 may be connected to the communication network 2 via wireless communication with the access point 2a. Communication network 2 transmits various types of data exchanged between connected devices. Communication network 2 can utilize the internet, VPN (virtual private network), LAN (local area network), public communication network, mobile communication network, etc., either individually or in appropriate combinations.

[0011] The electronic receipt server 4 includes a storage device 4a. The storage device 4a stores a contact database for providing electronic receipt services. Figure 3 is a schematic diagram showing the main data structure of data record DR1 included in the contact database. The contact database is a collection of data records DR1 associated with each user of the electronic receipt service. Each data record DR1 contains fields F11 and F12. Field F11 contains the electronic receipt ID (identifier), which serves as an identifier to distinguish the associated user from other users. Field F12 contains contact information for various communications regarding the electronic receipt service for the associated user. The contact information is, for example, an email address.

[0012] The member server 5 includes a storage device 5a. The storage device 5a stores a member database for managing members of the services provided by the store system 1. Figure 4 is a schematic diagram showing the main data structure of data record DR2 included in the member database managed by member server 5. The member database is a collection of data records DR2 associated with each member. Each data record DR2 contains fields F21, F22, and F23. Field F21 is set with the member code, which serves as an identifier to distinguish the associated member from other members. Field F22 is set with the electronic receipt ID of the associated member, if the associated member is also a user of the electronic receipt service. If the associated member is not a user of the electronic receipt service, Field F22 will be left blank or set with predetermined invalid data. Field F23 is set with the number of points the associated member holds regarding the point reward service.

[0013] The cart terminal 10 is an information processing terminal that functions as a user interface for operations related to registering purchased items. The cart terminal 10 is attached to a shopping cart (hereinafter referred to as "cart") C, for example, as shown in Figure 2. The cart terminal 10 is operated by a customer M1 using the cart C. However, the cart terminal 10 may also be carried by the customer. A store system 1 typically includes a number of cart terminals 10. A customer uses one cart terminal 10 exclusively while shopping. The cart terminal 10 may be fixed to the cart C or may be detachable from the cart C. When the cart terminal 10 is used by customer M1, it is moved by customer M1. In other words, the cart terminal 10 is an example of a mobile terminal that can be moved by the customer.

[0014] The store server 20 performs information processing to support all aspects of store operations. The store server 20 is equipped with a storage device 20a. The storage device 20a stores various databases, including a product master database. Figure 5 is a schematic diagram showing the main data structure of data record DR3 included in the product master database. The product master database is a collection of data records DR3 associated with each individual product that may be sold in a store. Each data record DR3 includes fields F31, F32, F33, and F34. Field F31 contains the product code, which serves as an identifier to distinguish the associated product from other products. Field F32 contains the product name, which is a name designated to make the associated product easily identifiable by humans. Field F33 contains the price to be applied when selling the associated product to a customer. Field F34 contains issuance confirmation information. The issuance confirmation information may include flag information indicating whether or not it is necessary to issue a certificate such as a discount coupon or warranty when selling the product. The issuance confirmation information may also include flag information indicating whether or not it is necessary for a store employee to handle the sale of products such as alcohol, tobacco, or certain pharmaceuticals. For example, this flag information may be set to "0" if it is not necessary and to "1" if it is necessary. The issuance confirmation information may also include information on the type of certificate that needs to be issued. The issuance confirmation information may also include identification information to identify the items to be confirmed by the store employee. Thus, a flag indicating whether or not a certificate needs to be issued means that it does not need to be printed on the medium. Therefore, this flag information corresponds to information indicating that it does not need to be printed on the medium. In addition, alcohol and tobacco are products with age restrictions, and the store clerk's response during the sale is to verify the purchaser's age. Thus, a flag indicating whether or not the store clerk's response is necessary when selling such products that require age verification corresponds to information indicating that there is no age restriction for the purchaser if it is "0".

[0015] The virtual POS server 30 works in cooperation with the cart terminal 10 to perform information processing to achieve various functions as a POS terminal. In this embodiment, the cart terminal 10 often functions as a user interface device. More specifically, the cart terminal 10 functions as the user interface for the virtual POS server 30. The virtual POS server 30 and the cart terminal 10 work together to perform information processing to realize various functions as a POS terminal, thereby making the cart terminal 10 appear to the customer as a POS terminal. Some of the various functions as a POS terminal are related to transaction processing. Thus, the cart terminal 10 and the virtual POS server 30 realize the functions of a transaction processing system.

[0016] The manned checkout terminal 40 is a payment terminal that allows store employees to perform operations related to the settlement of purchased items that have been registered by the virtual POS server 30. The manned checkout terminal 40 then performs accounting processing to determine the price of the purchased items. The manned checkout terminal 40 also performs settlement processing to settle the price determined by the above accounting processing, under the operation of the store employee. The manned checkout terminal 40 may also have the function of registering purchased items in response to operations by the store employee and further processing the settlement of those purchased items in response to operations by the store employee. In other words, the manned checkout terminal 40 may have the functions of a well-known face-to-face POS terminal.

[0017] Therefore, as shown in Figure 2, the manned checkout machine 40 is installed in the face-to-face zone ZO11 of the checkout zone ZO1. When the manned checkout machine 40 is in operation, a store employee M2 is assigned to operate the manned checkout machine 40 exclusively while facing the customer M1. A scanner SC1 is provided in the face-to-face zone ZO11. The scanner SC1 is connected to the manned checkout machine 40. The scanner SC1 may be either a stationary or handheld type. When the customer M1 brings an item to the face-to-face zone ZO11 without registering it using the cart terminal 10, the scanner SC1 scans the barcode or two-dimensional data code or other code symbol displayed on the item under the operation of store employee M2.

[0018] The self-checkout machine 50 is a payment terminal that allows customers to perform operations related to the payment of purchased items that have been registered by the virtual POS server 30. The self-checkout machine 50 then performs accounting processing to determine the price of the purchased goods. The self-checkout machine 50 is equipped with a printer 50a and issues receipts and other documents by printing them onto a medium for the customer to take home.

[0019] Therefore, as shown in Figure 2, the self-checkout machine 50 is installed in the self-checkout zone ZO12 of the checkout zone ZO1. No employee M2 is assigned to operate the self-checkout machine 50 exclusively.

[0020] In Figure 2, two manned checkout machines 40 and three self-checkout machines 50 are shown, but the number of manned checkout machines 40 and self-checkout machines 50 is arbitrary and depends on the circumstances of the store operator. Furthermore, manned checkout machines 40 do not have to be provided.

[0021] The beacon transmitter 60 transmits a predetermined beacon signal. Multiple beacon transmitters 60 may be deployed. The number of beacon transmitters 60, their locations, and transmission strength are adjusted so that the reception range is roughly within the accounting zone ZO1 shown in Figure 2.

[0022] The employee terminal 70 is an information processing terminal that performs information processing to support the work of employee M2. For example, employee terminal 70 is a portable information terminal carried by employee M2, who is in charge of maintaining cart C. Alternatively, employee terminal 70 may be a monitoring terminal for monitoring the operational status of store system 1. Multiple employee terminals 70 may be included in store system 1. In this case, multiple types of employee terminals 70 may be included.

[0023] Figure 6 is a block diagram showing the main circuit configuration of the cart terminal 10. The cart terminal 10 includes a tablet computer 11, a scanner 12, a reader 13, a camera 14, a beacon receiver 15, and an external battery 16.

[0024] The tablet computer 11 includes a processor 11a, main memory 11b, auxiliary storage unit 11c, wireless unit 11d, touch panel 11e, sound unit 11f, interface unit 11g, transmission line 11h, power supply unit 11i, and battery unit 11j. The processor 11a, main memory 11b, auxiliary storage unit 11c, wireless unit 11d, touch panel 11e, sound unit 11f, and interface unit 11g are capable of communicating via the transmission line 11h. The processor 11a, main memory 11b, and auxiliary storage unit 11c are connected by the transmission line 11h, thereby forming a computer for controlling the cart terminal 10.

[0025] The processor 11a corresponds to the central part of the computer described above. The processor 11a performs information processing to realize various functions as a cart terminal 10, according to information processing programs such as the operating system and application programs. The processor 11a is, for example, a CPU (central processing unit).

[0026] Main memory 11b corresponds to the main memory portion of the computer described above. Main memory 11b includes a non-volatile memory area and a volatile memory area. In the non-volatile memory area, main memory 11b stores the above-mentioned information processing program. Main memory 11b may also store data necessary for the processor 11a to perform information processing in either a non-volatile or volatile memory area. Main memory 11b uses the volatile memory area as a work area where data is rewritten as needed by the processor 11a. The non-volatile memory area is, for example, ROM (read-only memory). The volatile memory area is, for example, RAM (random access memory).

[0027] The auxiliary storage unit 11c corresponds to the auxiliary storage portion of the computer described above. As the auxiliary storage unit 11c, a storage unit using a well-known storage device such as EEPROM (electric erasable programmable read-only memory), HDD (hard disk drive), or SSD (solid state drive) can be used. The auxiliary storage unit 11c stores data used by the processor 11a in performing various processes, or data created by the processing performed by the processor 11a. The auxiliary storage unit 11c may also store the information processing program described above.

[0028] The wireless unit 11d exchanges data with the access point 2a via wireless communication in accordance with a wireless communication protocol. The touch panel 11e includes a display device and a touch sensor. The display device displays any screen, such as a GUI (graphical user interface) screen, under the control of the processor 11a. As the display device, a well-known device such as a color LCD (liquid crystal display) can be used. The touch sensor is positioned on top of the display surface of the display device. The touch sensor detects the operator's touch position on the display surface of the display device and sends the position information to the processor 11a. As the touch sensor, a well-known device can be used.

[0029] The sound unit 11f outputs various sounds, including voice and melody. The interface unit 11g is connected to the scanner 12, reader 13, camera 14, and beacon receiver 15. The interface unit 11g interfaces the exchange of data between the scanner 12, reader 13, camera 14, and beacon receiver 15 and the processor 11a. An existing USB (universal serial bus) controller or the like can be used as the interface unit 11g. The transmission path 11h includes an address bus, a data bus, control signal lines, etc., and transmits data and control signals exchanged between the processor 11a, the main memory 11b, the auxiliary storage unit 11c, the wireless unit 11d, the touch panel 11e, and the interface unit 11g.

[0030] The power supply unit 11i receives power from the battery unit 11j or the external battery 16 and supplies operating power to the electrical elements in the tablet computer 11. When the power supply unit 11i is powered by the external battery 16, it consumes the power supplied by the external battery 16, and when it is not powered by the external battery 16, it consumes the power supplied by the battery unit 11j. The battery unit 11j is charged by power supplied from the external battery 16. When the battery unit 11j is not being powered by the external battery 16, it supplies the power it is charging to the power supply unit 11i. The battery unit 11j has a function to measure its own remaining charge.

[0031] Scanner 12 reads code symbols such as barcodes or two-dimensional data codes. Scanner 12 is primarily used to read code symbols displayed on products that represent product codes, etc. Scanner 12 may also be used to read code symbols displayed on membership cards or on mobile devices that represent membership codes, etc. Scanner 12 outputs the data represented by the read code symbol. Scanner 12 may be a type that reads code symbols by scanning with a laser beam, or a type that reads code symbols from images captured by an imaging device.

[0032] Reader 13 reads and outputs data recorded on the recording medium. Reader 13 is a magnetic card reader if the recording medium is a magnetic card, and an IC card reader if it is a contact-type IC card. In the case of a contactless IC card or a recording medium using RFID (radio frequency identification) such as a smartphone, an RFID reader is used as Reader 13. Camera 14 takes an overhead shot of the inside of the shopping basket placed on cart C. Camera 14 then outputs image data representing the captured image.

[0033] The beacon receiver 15 receives the beacon signal transmitted by the beacon transmitter 60. When the beacon receiver 15 has received the beacon signal, it outputs notification data to notify the processor 11a of this. The external battery 16 is detachable from the tablet computer 11. When the external battery 16 is attached to the tablet computer 11, it supplies the stored power to the tablet computer 11.

[0034] Figure 7 is a perspective view showing an example of the appearance of cart C. Cart C comprises a caster section C1, a handle frame section C2, and a basket support section C3. The caster section C1 has four wheels C11 for smoothly moving the cart C on the floor. The wheels C11 are mounted on the frame C12 so as to be rotatable around a vertical axis. The handle frame section C2 includes a pair of vertical frames C21, C21 and a handlebar C22. The vertical frames C21, C21 are erected above the two wheels of the caster section C1. The handlebar C22 connects the upper ends of the vertical frames C21, C21. The basket support section C3 is provided horizontally from the middle of the handle frame section C2. The basket support section C3 holds the shopping basket SB for storing goods. The caster section C1 also holds the shopping basket SB on top of it.

[0035] The customer M1 using the cart C is typically positioned in front of the handle frame C2 in Figure 7. The customer M1 then pushes the cart C while gripping the handlebar C22. In this case, the direction in which the basket support C3 protrudes relative to the handle frame C2 is the direction in which the cart C moves forward.

[0036] A scanner 12 is attached to the middle of the handlebar C22. A pole C4 is attached to one of the vertical frames C21 such that its tip is positioned above the handlebar C22. The aforementioned tablet computer 11 is attached to the tip of this pole C4 with the touch panel 11e screen facing away from the direction of travel. A camera 14 is attached to the middle of the pole C4, facing the shopping basket SB held by the basket support C3. A reader 13 is attached to the tablet computer 11. In Figure 7, the reader 13 is a magnetic card reader. The card slot of the reader 13 is oriented in the same direction as the touch panel 11e screen. A battery case BC is attached between the vertical frames C21, C21 at the lower end of the handle frame C2. The battery case BC houses an external battery 16.

[0037] Figure 8 is a block diagram showing the main circuit configuration of the virtual POS server 30. The virtual POS server 30 includes a processor 31, main memory 32, auxiliary storage unit 33, communication interface 34, and transmission path 35. The processor 31, main memory 32, auxiliary storage unit 33, and communication interface 34 are able to communicate with each other via the transmission path 35. The connection of the processor 31, main memory 32, and auxiliary storage unit 33 via the transmission path 35 constitutes a computer for controlling the virtual POS server 30. The general functions of the processor 31, main memory 32, auxiliary storage unit 33, and transmission path 35 are equivalent to those of the processor 11a, main memory 11b, auxiliary storage unit 11c, and transmission path 11h, so their explanation is omitted. The communication interface 34 performs data communication with each part connected to the communication network 2 according to a predetermined communication protocol.

[0038] The auxiliary storage unit 33 stores the transaction processing program AP1, which is one of the information processing programs. The transaction processing program AP1 is an application program that describes the sales processing described later. A portion of the storage area of ​​the auxiliary storage unit 33 is used as the cart management database DB1 and the purchased product database DB2.

[0039] Figure 9 is a schematic diagram showing the main data structure of data record DR4 included in the cart management database DB1. The cart management database DB1 is a collection of data records DR4 associated with each cart C used by customer M1. Each data record DR4 contains fields F41, F42, F43, F44, and F45. Field F41 contains a terminal code to distinguish the cart terminal 10 attached to the associated cart C from other cart terminals 10. Field F42 contains a membership code to distinguish customer M1 using the associated cart C from other customers. Field F43 contains a transaction code to distinguish transactions conducted using the associated cart C from other transactions. Field F44 contains the electronic receipt ID of customer M1 using the associated cart C. Field F45 contains the number of points held by customer M1 using the associated cart C. Note that data record DR4 may also contain other fields that contain data different from fields F41 to F45.

[0040] Figure 10 is a schematic diagram showing the main data structure of data record DR5 included in the purchased product database DB2. The purchased items database DB2 is a collection of data records DR5 associated with each purchase currently underway in the store. Each data record DR5 contains fields F51 and F52. A data record DR5 may also contain fields F53, F54, ... Field F51 is set with the transaction code defined for the associated purchase. This transaction code is the same as the transaction code set in field F42 of data record DR4, which is associated with cart C used for the associated purchase. Field F52 is set with product data for the products registered as purchased items for the associated purchase. The product data includes the product code, unit price, product name, quantity, and cancellation flag. The product code is an identification code defined to identify products by SKU (stock keeping unit), and for example, the JAN (Japanese article number) code is used. The cancellation flag is flag data used to identify products that were initially registered as purchased items but were subsequently canceled.

[0041] Data record DR5 includes fields F53 and beyond if two or more purchased items are registered for the associated purchase. These fields, like field F52, are then filled with product data. Thus, each field from F52 onwards represents a list of purchased items for the associated purchase. This list of purchased items will be referred to as the product list below.

[0042] Now, as the hardware for the virtual POS server 30, for example, a general-purpose network server can be used. Generally, the transfer of the virtual POS server 30 is carried out with the transaction processing program AP1 stored in the auxiliary storage unit 33, but the cart management database DB1 and the purchased product database DB2 not stored therein. However, the hardware in which the transaction processing program AP1 is not stored in the auxiliary storage unit 33, or in which a different version of the same transaction processing program AP1 is stored in the auxiliary storage unit 33, may be transferred along with the transaction processing program AP1 separately. The virtual POS server 30 may then be configured by writing the transaction processing program AP1 to the auxiliary storage unit 33 in response to an operation by any worker. The transfer of the transaction processing program AP1 can be carried out by recording it on a removable recording medium such as a magnetic disk, magneto-optical disk, optical disk, or semiconductor memory, or by communication over a network. The cart management database DB1 and the purchased product database DB2 are configured in the auxiliary storage unit 33 by the processor 31 executing information processing based on the transaction processing program AP1. Furthermore, at least a portion of the transaction processing program AP1, the cart management database DB1, and the purchased product database DB2 may be stored in main memory 32.

[0043] Next, the operation of the store system 1 configured as described above will be explained using Figures 11, 12, 13, 14, and 15. Note that the details of the various processes described below are examples, and it is possible to change the order of some processes, omit some processes, or add other processes as appropriate. When the cart terminal 10 is started up, the processor 11a executes the information processing described below according to the information processing program stored in the main memory 11b or the auxiliary storage unit 11c. Figure 11 is a flowchart showing the information processing procedure performed by the processor 11a in the cart terminal 10.

[0044] (Starting to use Cart C) As ACT1, processor 11a waits for the user to initiate use. At this time, processor 11a is waiting for shopping to begin using the cart C to which it is attached. For example, in this waiting state, processor 11a displays a screen representing the start button on the touch panel 11e. Customer M1 takes one of the carts C placed in the cart area and performs the predetermined operation to initiate use on the cart terminal 10 attached to that cart C. If customer M1 is a member, they have the scanner 12 or reader 13 read the member code recorded on their member card. If customer M1 is not a member, they operate the start button mentioned above. Then, if these operations are performed, processor 11a determines that the operation to initiate use has been performed and proceeds to ACT2.

[0045] As ACT2, processor 11a notifies the virtual POS server 30 of the terminal code and member code of the cart terminal 10 on which it is installed. This is a login request notification. If the start button is touched, processor 11a also notifies the virtual POS server 30 of a predetermined member code for non-members. The member code for non-members may be the same for multiple customers or may be different for each customer. Specifically, processor 11a transmits notification data containing the terminal code and member code from the wireless unit 11d to the access point 2a addressed to the virtual POS server 30. This notification data is transmitted to the virtual POS server 30 via the access point 2a and the communication network 2. The communication interface 34 of the virtual POS server 30 then receives the notification data. The communication interface 34 provides the received notification data to processor 31. This notifies processor 31 of a login request. In subsequent explanations of other notifications, such detailed explanations as described above will be omitted.

[0046] When processor 31 receives notification of a login request, it begins processing information for transaction processing as described below. Processor 31 executes this information processing according to the transaction processing program AP1.

[0047] Figures 12, 13, 14, and 15 are flowcharts showing the information processing procedure for transaction processing by the processor 31. The processor 31 starts this information processing each time it receives a login request notification and executes multiple information processing tasks in parallel. In other words, the processor 31 executes the following information processing tasks in parallel for multiple cart terminals 10. The following describes the information processing for one cart terminal 10 that has received a login notification as described above. Therefore, when simply referred to as "cart terminal 10," it refers to the one cart terminal 10 mentioned above. Also, when simply referred to as "customer M1," it refers to customer M1 using the one cart terminal 10 mentioned above.

[0048] In Figure 12, as ACT20, processor 31 checks whether the member requesting login is already logged in. For example, if the member code included in the login request notification data is not for non-members and does not match any of the member codes set in field F42 of data record DR4 in the cart management database DB1, processor 31 determines that the member is not logged in. Processor 31 also determines that the member is not logged in if the member code included in the login request notification data is for non-members. If the member is not logged in in this way, processor 31 determines NO and proceeds to ACT21.

[0049] As ACT21, processor 31 makes a member inquiry to member server 5. For example, processor 31 queries member server 5 with the member code included in the notification data of the login request mentioned above. Member server 5 finds a data record DR2 in the member database in which the member code set in field F21 matches the notified member code. Member server 5 then notifies virtual POS server 30 of the electronic receipt ID and point count set in fields F22 and F23 of the relevant data record DR2.

[0050] As ACT22, processor 31 updates the cart management database DB1 to add a new data record DR4. Processor 31 sets the terminal code and member code included in the notification data into fields F41 and F42 of the data record DR4 to be added. Processor 31 also determines the transaction code using a predetermined algorithm so that it is different from the transaction code used in transaction processing targeting at least another cart terminal 10. This transaction code is then set into field F43 of the data record DR4 to be added. Processor 31 also sets the electronic receipt ID and point count notified by the member server 5 into fields F44 and F45, respectively, of the data record DR4 to be added. If the electronic receipt ID notified by the member server 5 is not provided, processor 31 leaves field F44 of the data record DR4 blank or sets it with predetermined invalid data. After completing the update, processor 31 notifies the cart terminal 10 that the login is complete.

[0051] As ACT23, processor 31 instructs cart terminal 10 to display a completion screen. The completion screen is a screen that notifies the customer that login is complete. The completion screen may also display guidance to the customer, such as that they can start registering their purchased items. For example, processor 31 sends instruction data containing screen data representing the completion screen to cart terminal 10 via communication interface 34. This instruction data is transmitted to cart terminal 10 via communication network 2 and access point 2a. The wireless unit 11d of cart terminal 10 then receives the instruction data. The wireless unit 11d provides the received instruction data to processor 11a. This instructs processor 11a to display the completion screen. Various instructions from virtual POS server 30 to cart terminal 10 are given in the same manner as the instruction to display the completion screen described above. For this reason, detailed explanations of other instructions will be omitted in subsequent explanations.

[0052] (Registering purchased items) After the processor 11a in the cart terminal 10 notifies the login request in ACT2 in Figure 11, it waits for notification of login completion from the virtual POS server 30 before proceeding to ACT3. In ACT3, processor 11a checks whether a screen change was instructed by the virtual POS server 30 as described below. If processor 11a cannot confirm that such an instruction was given, it determines NO and proceeds to ACT4. In ACT4, processor 11a checks whether any operation has been performed by the operator. The operator is usually customer M1, but store employee M2 may temporarily become the operator. If processor 11a cannot confirm that the operation has been performed, it determines NO and proceeds to ACT5.

[0053] In ACT5, processor 11a checks whether or not a beacon signal has been received. If it cannot confirm that the beacon receiver 15 has notified it that a beacon signal has been received, it determines NO and proceeds to ACT6. As ACT6, processor 11a checks whether or not logoff has been permitted from the virtual POS server 30. If processor 11a cannot confirm that permission has been granted, it determines NO and returns to ACT3. Thus, in ACT3 through ACT6, the processor 11a waits for one of the following to be given: an instruction or operation to change the screen, reception of a beacon signal, or permission to log off.

[0054] When various display instructions are given, such as the instruction to display the completion screen as described above, the processor 11a determines YES in ACT3 and proceeds to ACT7. As ACT7, processor 11a changes the display screen on touch panel 11e according to the display instruction. For example, processor 11a controls touch panel 11e to display the screen represented by the screen data included in the instruction data. If the screen data included in the instruction data represents the aforementioned completion screen, the display screen on touch panel 11e is changed to the completion screen. This allows customer M1 to know that they can start the operation to register the purchased product. After this, processor 11a returns to the standby state of ACT3 to ACT6.

[0055] Customer M1 moves around the store, pushing cart C, searching for the items they wish to purchase. Once they find the items, they take them from the display and place them in cart C. At this time, customer M1 performs an operation to designate the items as purchase items. This operation may be, for example, an operation of scanner 12 to read the code symbol displayed on the items. Alternatively, this operation may be, for example, an operation of touch panel 11e to select the items. If customer M1 wishes to register multiple items with the same product code as purchase items, they may specify the quantity and then have scanner 12 read the code symbol only once.

[0056] If any operation, including such an operation, is performed by the operator, processor 11a determines YES in ACT4 and proceeds to ACT8. As ACT8, processor 11a notifies processor 31 of virtual POS server 30 of the operation details. If the scanner 12 is operated to read a code symbol displayed on a product, processor 11a obtains the data of the code symbol read by scanner 12 from scanner 12. The code symbol data includes a product code for identifying the product. If the touch panel 11e is operated to specify a product, processor 11a obtains the product code for the product specified by that operation, for example by referring to a data table. The data table represents the product code in relation to the content of the operation and is stored in the auxiliary storage unit 11c in advance, for example. In other words, processor 11a obtains the product code in these ways and has the function of an acquisition means. When processor 11a notifies of an operation to specify a product as a purchase product, it notifies the product code and quantity of the specified product. If no operation to specify the quantity is performed, processor 11a sets the quantity to "1". After this, processor 11a returns to the waiting state of ACT3 to ACT6.

[0057] Now, in the virtual POS server 30, the processor 31 checks whether the operation details have been notified, as ACT24 in Figure 12. If the processor 31 cannot confirm that the relevant notification has been made, it determines NO and proceeds to ACT25. As ACT25, processor 31 checks whether or not a notification of beacon signal reception has been received. If processor 31 cannot confirm that the notification has been made, it determines NO and proceeds to ACT26. As ACT26, processor 31 checks whether accounting data has been requested. If processor 31 cannot confirm that the request has been made, it determines NO and returns to ACT24. Thus, in ACT24 to ACT26, the processor 31 awaits notification of operation details, notification of beacon reception, or request for accounting data.

[0058] As mentioned above, once the operation details are communicated, the processor 31 determines YES in ACT24 and proceeds to ACT27 in Figure 13. As ACT27, processor 31 checks whether the notified operation is to specify a product to purchase. If it is to specify a product to purchase, processor 31 determines it is YES and proceeds to ACT28.

[0059] As ACT28, processor 31 updates the product list to add the specified purchase item. For example, processor 31 finds a data record DR4 in the cart management database DB1 whose terminal code set in field F41 matches the terminal code of cart terminal 10. Then processor 31 retrieves the transaction code set in field F43 of the corresponding data record DR4. Next, processor 31 finds a data record DR5 in the purchase item database DB2 whose transaction code set in field F51 matches the transaction code retrieved above. If the corresponding data record DR5 does not exist, processor 31 adds a new data record DR5 to the purchase item database DB2, setting the retrieved transaction code in field F51 and the product data containing the product code of the specified purchase item in field F52. If the corresponding data record DR5 is found, processor 31 adds a new field after the field located at the end of the corresponding data record DR5 and sets the product data containing the product code of the specified purchase item in this field. The processor 31 sets the cancellation flag for the newly set product data to indicate that it has not been canceled. The processor 31 also includes the product name, price, and issuance confirmation information obtained from the product master database of the store server 20 using the product code as the key, as well as the quantity notified from the cart terminal 10 along with the product code, in the product data to be set in field F52 or the new field.

[0060] By the way, if customer M1 wishes to cancel the purchase of the items registered as described above, they perform an operation to instruct the cancellation of those items, for example, on the touch panel 11e. When the contents of this operation are notified from the cart terminal 10 to the virtual POS server 30, the processor 31 determines NO in ACT27 and proceeds to ACT29. As ACT29, processor 31 checks whether the notified operation is a cancellation instruction. If it is a cancellation instruction as described above, it determines YES and proceeds to ACT30. As ACT30, processor 31 updates the product list to exclude the purchased product for which cancellation has been instructed. For example, processor 31 changes the cancellation flag in the product data for the purchased product for which cancellation has been specified to indicate that it has been canceled.

[0061] In addition, in ACT28 or ACT30, processor 31 calculates the price of the purchased goods based on the product data included in the updated product list. When calculating this price, processor 31 applies various well-known discount or reduction processes as necessary. If processor 31 has completed either ACT28 or ACT30, it proceeds to ACT31 in either case. As ACT31, processor 31 checks whether the system is in a state where through checkout is permitted. Through checkout means paying using the procedures at the cart terminal 10 without using the manned checkout machine 40 or the self-checkout machine 50. Processor 31 checks whether the predetermined permitting conditions are met. If the permitting conditions are met, processor 31 determines that the system is in a state where through checkout is permitted and proceeds to ACT32. The acceptable conditions may be arbitrarily determined by the creator of the transaction processing program AP1 or the administrator of the virtual POS server 30. The acceptable conditions are expected to be, for example, when none of the following conditions apply. However, it is not mandatory to consider all of the following conditions. For example, if there is no need to print a receipt, the acceptable condition may be met. Also, for example, if the purchased items do not include any products with age restrictions, the acceptable condition may be met. Alternatively, if customer M1 is an electronic receipt member, the acceptable condition may be met.

[0062] (1) When it is necessary to provide customer M1 with proof of purchase. Proof of purchase may be a receipt, proof of purchase, warranty, coupon, discount voucher, or other. Proof of purchase is typically printed at the time of payment by a printer 50a provided in the manned checkout machine 40 or self-checkout machine 50. Proof of purchase may be a pre-prepared printed document. Proof of purchase may also be formed by handwriting some information on pre-prepared paper by a store employee. In principle, a receipt should be issued for all transactions. However, if customer M1 is a member of the electronic receipt service, the issuance of a receipt can be omitted by using the electronic receipt service. Therefore, in this embodiment, when customer M1 is not a member of the electronic receipt service, it is necessary to provide customer M1 with proof of purchase. Regarding this condition, for example, if a valid electronic receipt ID is not set in field F44 of the data record DR4 associated with the cart terminal 10, the processor 31 determines that it is necessary to provide customer M1 with proof of purchase. Furthermore, the processor 31 determines, for example, that a certificate needs to be given to customer M1 if any of the product data in the data record DR5 associated with a transaction related to the cart terminal 10 contains issuance confirmation information that includes flag information indicating whether or not a certificate needs to be issued.

[0063] (2) When the purchased items include products that require the attention of staff member M2. In this case, the attention of staff member M2 may include, for example, confirming whether customer M1 meets the restrictions, such as age restrictions, for products that are included in the purchased items. Another example of staff member M2 may include explaining to customer M1 about products that require explanation by a qualified person before purchase. Another example of staff member M2 may include handing over a gift to customer M1 if the purchased items include products for which it is stipulated that a gift will be given to the purchaser. Another example of staff member M2 may include verbally explaining the product to customer M1. With regard to this condition, the processor 31 may determine that the purchased items include products that require the attention of staff member M2 if, for example, any of the product data included in the data record DR5 associated with the transaction related to the cart terminal 10 contains issuance confirmation information that includes flag information indicating that confirmation by a staff member is required before sale.

[0064] (3) When there is a possibility that an item requiring verification by store employee M2 is placed in cart C. In this case, verification by store employee M2 means, for example, verification when an item may have been placed in cart C without being registered as a purchase item.

[0065] (4) When a payment method requiring staff assistance is specified. A payment method requiring staff assistance is one that is not permitted to be handled by the self-checkout machine 50, such as payment with gift certificates, and is required to be handled by a staff member. One example of the above case is when the applicable payment method is designated as the default payment method for customer M1. Alternatively, one example of the above case is when the applicable payment method is designated as the payment method for a purchase being registered before the registration of the purchase is completed.

[0066] As ACT32, processor 31 instructs cart terminal 10 to display the registration screen. The registration screen is a screen that displays a list of registered purchased items. Figure 16 shows an example of the registration screen SC11. The registration screen SC11 represents areas AR1, AR2, AR3, buttons BU1, BU2, BU3, and icon IC1. Area AR1 displays the product names of the products shown in the product list after updating in ACT28 or ACT30, arranged in rows. Area AR1 also displays the number of units registered as purchased items and the selling price of the product, arranged in columns for the above product names. Area AR1 has strikethrough lines applied to the product names, units, and selling prices of products that are shown in the product list but whose cancellation flag has been removed. In other words, the registration screen SC11 shows that products with product names "AAA", "BBB", "DDD", and "EEE" are registered products, and products with product names "CCC" were once registered products but have since been canceled.

[0067] Area AR2 is arranged in order of each row in Area AR1. Although not shown in Figure 16, Area AR2 displays icons corresponding to the associated products as needed. The icons displayed in Area AR2 indicate, for example, that the product is eligible for various discounts such as set discounts, or that it is an age-restricted product. Area AR3 displays the total number of items and the total amount for registered purchased items. Processor 31 displays the total amount calculated in ACT28 or ACT30 in Area AR3.

[0068] Button BU1 is placed in each row of area AR1 that represents a purchased item. Button BU1 is an operation button used by the operator to instruct the operator to cancel the purchased items displayed in that row. In other words, when button BU1 is touched and this is notified from the cart terminal 10 to the virtual POS server 30, the processor 31 determines in ACT29 that a cancellation has been instructed. Button BU2 is an operation button used by the operator to indicate that the registration of purchased items has been completed and the user is proceeding to checkout. Button BU3 is an operation button used by the operator to direct the user to a screen for registering items that do not display a code symbol as purchased items. Icon IC1 is used to inform guest M1 that through checkout is permitted.

[0069] The processor 31 generates screen data for the registration screen SC11, which displays information based on the updated product list in areas AR1, AR2, and AR3, and transmits this screen data to the cart terminal 10. The processor 11a then displays the registration screen SC11 on the touch panel 11e of the cart terminal 10 based on this screen data.

[0070] On the other hand, if the predetermined tolerance conditions are not met, the processor 31 determines NO in ACT 31 and proceeds to ACT 33. As ACT33, processor 31 instructs cart terminal 10 to display registration screen SC11. However, the icon IC1 is not displayed in the registration screen SC11 generated by processor 31 as ACT33.

[0071] Thus, on the registration screen SC11, the information displayed in areas AR1, AR2, and AR3, the display state of button BU1, and the presence or absence of icon IC1 may change from the state shown in Figure 16, while other display elements will generally not change. The processor 31 then changes whether or not to display icon IC1 on the registration screen SC11, depending on whether or not through checkout is permitted. When processor 31 completes ACT32 or ACT33, it returns to the standby state of ACT24 to ACT26 in Figure 12.

[0072] (Replacement of Cart C) Incidentally, customer M1, who is a member, can change the cart C they are using if the battery level of the cart C they are currently using becomes low. In this case, customer M1 will start using a cart C that is different from the cart C they are currently using and that is not being used by another customer M1.

[0073] When a login request is sent from cart terminal 10 of cart C (referred to here as new terminal 10) to the virtual POS server 30 in response to this activation operation, the processor 31 begins processing information for new terminal 10. At this time, the member code included in the login request notification data matches the member code set in field F42 of data record DR4 associated with cart terminal 10 of cart C currently in use (referred to here as old terminal 10). Therefore, the processor 31 determines YES in ACT20 of the information processing for new terminal 10 and proceeds to ACT34.

[0074] As ACT34, processor 31 updates the cart management database DB1 to change it. For example, processor 31 finds a data record DR4 in the cart management database DB1 in which the member code set in field F42 matches the member code included in the login request notification data. Then processor 31 rewrites the terminal code set in field F41 of the corresponding data record DR4 to the terminal code of the new terminal 10. As a result, the product list, which was previously subject to updates in the information processing of the old terminal 10, is now subject to updates in the information processing of the new terminal 10. After completing the update, processor 31 notifies the new terminal 10 that the login is complete.

[0075] As ACT35, the processor 31 instructs the new terminal 10 to display the screen currently displayed on the touch panel 11e of the old terminal 10. After this, the processor 31 transitions to the standby state of ACT24 to ACT26. Customer M1 can continue registering purchased items using the new terminal 10. In this case, the processor 31 remains in a waiting state for ACT24 to ACT26 when processing information for the old terminal 10. When the processor 31 receives any notification from the old terminal 10, it confirms that there is no data record DR4 associated with the old terminal 10, and then terminates the information processing for the old terminal 10.

[0076] (accounting) Once customer M1 has finished registering all the items they wish to purchase, they move to the checkout zone ZO1. When the cart terminal 10 enters the receivable range of the beacon signal transmitted by the beacon transmitter 60, the beacon receiver 15 receives the beacon signal. When this is notified from the beacon receiver 15 to the processor 11a, the processor 11a determines YES in ACT5 in Figure 11 and proceeds to ACT9. As ACT9, processor 11a notifies the virtual POS server 30 of the beacon reception. After this, processor 11a returns to the waiting state for ACT3 through ACT6.

[0077] When the virtual POS server 30 is notified of beacon reception in this way, the processor 31 determines YES in ACT25 in Figure 12 and proceeds to ACT36. As ACT36, processor 31 instructs cart terminal 10 to display the first confirmation screen. The first confirmation screen is a screen for confirming whether or not to start the checkout process. The first confirmation screen may, for example, display a button to specify that the checkout process should begin and a button to specify that the user should return to the sales floor and continue registering the purchased items. After this, processor 31 returns to the standby state for ACT24 to ACT26.

[0078] The cart terminal 10 displays a first confirmation screen on the touch panel 11e in response to the above instructions. Customer M1 indicates on the first confirmation screen whether to start the checkout process or return to the sales floor to continue registering the purchased items. In response, the cart terminal 10 notifies the virtual POS server 30 of the details of the operation on the first confirmation screen.

[0079] When the content of the operation on the first confirmation screen is notified in this manner, the processor 31 determines YES at ACT24 in Figure 12, NO at ACT27 and ACT29 in Figure 13, and proceeds to ACT37 in Figure 14. As ACT37, processor 31 checks whether the content of the operation on the first confirmation screen has been notified. Thus, if the above is the case, processor 31 determines YES and proceeds to ACT38.

[0080] As ACT38, processor 31 checks whether it has been instructed to begin checkout. If it has been instructed to continue registering the purchased items, processor 31 determines NO and returns to the waiting state of ACT24 to ACT26 in Figure 12. At this time, processor 31 does not determine YES in ACT25 until a predetermined amount of time has elapsed since returning to the waiting state of ACT24 to ACT26. As a result, even if the instruction to continue registering the purchased items on the first confirmation screen is given while customer M1 is in the checkout zone ZO1, subsequent beacon receptions will be ignored for a while.

[0081] Incidentally, if customer M1 decides to proceed with payment during the period when beacon reception is ignored as described above, they will have the scanner 12 of the cart terminal 10 read the payment barcode BC1 installed in the payment zone ZO1, for example, as shown in Figure 2. Also, if the beacon receiver 15 fails to receive the beacon signal for some reason, and the first confirmation screen is not displayed even when moving into the payment zone ZO1, customer M1 will operate the scanner 12 of the cart terminal 10 to read the payment barcode BC1. In response, the cart terminal 10 will notify the virtual POS server 30 that the scanner 12 has been operated, along with a notification of the payment barcode.

[0082] In this case, the processor 31 determines YES at ACT24 in Figure 12, NO at ACT27, ACT29 in Figure 13, and ACT37 in Figure 14, and proceeds to ACT39. In ACT39, processor 31 checks whether or not it is an operation to read an accounting barcode. If, as described above, it is notified that it is an operation to read an accounting barcode, processor 31 determines YES and proceeds to ACT40. If, in the first confirmation screen, processor 31 is instructed to start accounting, it determines YES in ACT38 and proceeds to ACT40.

[0083] As ACT40, processor 31 checks whether or not the system is in a state where through checkout is permitted, similar to ACT31. If processor 31 determines that the system is in a state where through checkout is permitted, it determines YES and proceeds to ACT41. As ACT41, processor 31 instructs cart terminal 10 to display a selection screen. The selection screen allows customer M1 to choose whether or not to apply through checkout. After this, processor 31 returns to the standby state of ACT24 to ACT26 in Figure 12. Figure 17 shows an example of the selection screen SC12. The selection screen SC12 represents area AR21, buttons BU21, BU22, BU23, and message ME21. Area AR21 represents the amount that customer M1 should pay. Button BU21 is an operation button for the operator to specify that through checkout be applied. Button BU22 is an operation button for the operator to specify that the self-checkout machine 50 be used. Button BU23 is an operation button for the operator to instruct the cart terminal 10 to return to the screen that was displayed before this selection screen SC12 was displayed. Message ME21 is a text message that guides the operator to choose whether to apply through checkout and pay at the cart terminal 10, or to pay using the self-checkout machine, by using buttons BU21 or BU22. Thus, on the selection screen SC12, the amount displayed in area AR21 may change from the state shown in Figure 17 depending on the registration status of the purchased items, while other display elements generally remain unchanged.

[0084] The cart terminal 10 displays the selection screen SC12 on the touch panel 11e in response to the above instructions. Customer M1 indicates on the selection screen SC12 whether to apply through checkout or use the self-checkout machine 50. In response, the cart terminal 10 notifies the virtual POS server 30 of the operation on the selection screen SC12. In other words, the processor 11a will select whether to apply through checkout or use the self-checkout machine 50 in response to customer M1's operation. When the content of the operation on the selection screen SC12 is notified in this manner, the processor 31 determines YES at ACT24 in Figure 12, NO at ACT27 and ACT29 in Figure 13, and NO at ACT37 and ACT39 in Figure 14, respectively, and proceeds to ACT42.

[0085] As ACT42, processor 31 checks whether the content of the operation on selection screen SC12 has been notified. Thus, if the above is the case, processor 31 determines YES and proceeds to ACT43. As ACT43, the processor 31 checks whether through checkout is specified based on the notification from the cart terminal 10. If through checkout is specified, the processor 31 determines YES and proceeds to ACT44 in Figure 15.

[0086] As ACT44, processor 31 requests payment from payment server 3. Specifically, processor 31 instructs cart terminal 10 to display a specified screen. The specified screen is a screen that allows the operator to specify the payment method to be used for through checkout. Figure 18 shows an example of the specified screen SC13. The designated screen SC13 represents area AR31, buttons BU31, BU32, BU33, BU34, and message ME31. Area AR31 represents the amount that customer M1 should pay. Button BU31 is an operation button for the operator to specify barcode payment as the payment method to be used. Button BU32 is an operation button for the operator to specify credit card payment as the payment method to be used. Button BU33 is an operation button for the operator to specify electronic money payment as the payment method to be used. Button BU34 is an operation button for the operator to instruct the cart terminal 10 to return to the screen that was displayed before this designated screen SC13 was displayed. Message ME31 is a text message that guides the operator to specify which payment method to use using buttons BU31, BU32, and BU33. Thus, on the designated screen SC13, the amount displayed in area AR31 may change from the state shown in Figure 18 depending on the registration status of the purchased items, while other display elements will not change in principle.

[0087] The cart terminal 10 displays the designated screen SC13 on the touch panel 11e in accordance with the above instructions. Customer M1 specifies the payment method on the designated screen SC13. The cart terminal 10 then notifies the virtual POS server 30 of the specified payment method.

[0088] If the processor 31 receives notification of a specified payment method from the cart terminal 10, it instructs the cart terminal 10 to display a payment screen corresponding to that notified payment method. The payment screen is a screen that guides the user through the steps required to complete the payment. Figure 19 shows an example of the payment screen SC14 when barcode payment is selected. The payment screen SC14 consists of area AR41, buttons BU41, BU42, BU43, BU44, BU45, messages ME41, ME42, and image IM41. Area AR41 represents the amount that customer M1 should pay. Buttons BU41 to BU44 are operation buttons for the operator to specify the barcode payment service to be used. Each of the buttons BU41 to BU44 is associated with an available barcode payment service. Button BU45 is an operation button for the operator to instruct the cart terminal 10 to return to the screen that was displayed before this payment screen SC14 was displayed. Message ME41 is a text message that guides the operator to first specify which barcode payment service to use using buttons BU41, BU42, BU43, and BU44. Message ME42 is a text message that guides the operator to scan the payment barcode displayed on the smartphone held by customer M1. Image IM41 is an image that, in conjunction with message ME42, guides the operator to the barcode that should be canceled. Thus, on the payment screen SC14, the amount displayed in area AR41 may change from the state shown in Figure 19 depending on the registration status of the purchased items, while other display elements will not change in principle. Note that payment screen SC14 is an example where the use of four barcode payment services is permitted. The number of buttons corresponding to buttons BU1 to BU4 will change depending on the number of barcode payment services that are permitted. If only one barcode payment service is permitted, buttons corresponding to BU1 to BU4 will not be displayed on payment screen SC14.

[0089] The cart terminal 10 displays the payment screen SC14 on the touch panel 11e in accordance with the above instructions. Customer M1 specifies the barcode payment service to be used by operating one of the buttons BU41 to BU44. Customer M1 also has the scanner 12 read the payment barcode displayed on their smartphone using the application software for the barcode payment service to be used. In response, the processor 11a in the cart terminal 10 notifies the virtual POS server 30 of a payment method code to distinguish barcode payment from other payment methods, a service code to distinguish the specified barcode payment service from other services, and the payment data represented by the payment barcode. If the use of only one barcode payment service is permitted, the processor 11a may notify the virtual POS server 30 of the service code of that one barcode payment service, or it may omit the notification of the service code. In the case of credit card payment, data such as the credit card number recorded on the credit card becomes the payment data. When credit card payment is specified, processor 11a notifies the virtual POS server 30 of a payment method code to distinguish credit card payment from other payment methods, and the credit card number read from the credit card by reader 13. In the case of electronic money payment, data such as the electronic money ID recorded on the electronic money card becomes the payment data. When electronic money payment is specified, processor 11a notifies the virtual POS server 30 of the payment method code to distinguish electronic money payment from other payment methods, and the electronic money ID read by reader 13 from the electronic money recording medium. If the use of multiple electronic money payment services is permitted, processor 11a receives the electronic money payment service specification from customer M1 via a screen similar to the selection screen SC12, and also notifies the virtual POS server 30 of the service code of the specified electronic money payment service. If the use of only one electronic money payment service is permitted, processor 11a may notify the virtual POS server 30 of the service code of that one electronic money payment service, or may omit the notification of the service code. Furthermore, if a credit card number or electronic money ID is stored in the payment server 3 or virtual POS server 30 in association with a management code, and the management code is notified to the payment server 3 or virtual POS server 30 when a payment request is made, then that management code becomes the payment data.

[0090] When the processor 31 receives a notification from the cart terminal 10 as described above, it requests payment from the payment server 3, along with the payment data notification. The processor 31 uses the most recently calculated amount in ACT28 or ACT30 in Figure 13 as the payment amount for which it requests payment. If payment server 3 supports each payment method, processor 31 also notifies payment server 3 of the payment method code when requesting payment. If payment server 3 supports each payment service, processor 31 also notifies payment server 3 of the service code when requesting payment. If there are multiple payment servers 3 depending on the payment method or payment service, processor 31 selects the payment server 3 corresponding to the payment method and payment service to be used based on the payment method code and service code notified from cart terminal 10, and requests payment from that payment server 3. Thus, by having the processor 31 execute information processing based on the transaction processing program AP1, the computer with the processor 31 as its central component functions as a request mechanism.

[0091] When a payment is requested, payment server 3 checks whether the requested payment is possible. If payment is possible, payment server 3 executes the processing required for the requested payment. If payment server 3 can complete the payment, it sends a result code indicating completion to virtual POS server 30. If payment server 3 aborts the payment processing for any reason, it sends a result code indicating failure to virtual POS server 30. If payment server 3 successfully performed the payment processing but it is unclear whether the payment was completed, it sends a result code indicating incomplete to virtual POS server 30. The details of the above processing in payment server 3 may be the same as those in existing payment servers.

[0092] In the virtual POS server 30, after the processor 31 requests payment in ACT44 in Figure 15, it transitions to the waiting state for ACT45 and ACT46. As ACT45, processor 31 checks whether this waiting state has timed out. If it has not timed out, processor 31 determines NO and proceeds to ACT46. As ACT46, processor 31 checks whether or not a notification of the payment result has been sent from payment server 3. If processor 31 cannot confirm that the notification has been sent, it determines NO and returns to ACT45. Thus, when ACT45 and ACT46 are in a waiting state, the processor 31 waits for a timeout to occur or for the result to be notified. Then, if the processor 31 receives the result code sent from the payment server 3 via the communication interface 34 as described above, it determines that the result has been notified and verifies YES in ACT 46, and proceeds to ACT 47.

[0093] As ACT47, processor 31 checks whether the payment has been completed. If the received result code indicates completion, processor 31 determines it is YES and proceeds to ACT48. As ACT48, processor 31 transmits transaction data to store server 20. Transaction data is data relating to the transaction being processed. Processor 31 includes first identification data and second identification data in the transaction data. The first identification data is data used to distinguish the request to settlement server 3 regarding the settlement of the transaction from other requests received by settlement server 3. When requesting settlement from settlement server 3, if the requesting virtual POS server 30 notifies settlement server 3 of an identification code to identify the settlement case related to that request, that identification code can be used as the first identification data. Alternatively, data that does not overlap with other requests to settlement server 3 can be used as the first identification data, such as an identification code for settlement server 3 to identify virtual POS server 30, the date and time the settlement was requested, and the settlement amount. The second identification data is data used to distinguish the transaction data from other transaction data included in the journal database. For example, a combination of transaction code, register code, and date can be used as the second identification data. The register code is a code used to identify each POS terminal, which is realized through the cooperation of the cart terminal 10 and the virtual POS server 30. The register code may be the terminal code, or it may be defined separately from the terminal code. The processor 31 may also include settlement data for settling transactions in the transaction data. The settlement data may be, for example, the product code and quantity of the purchased items, and at least one of the payment amount. The processor 31 may also include other arbitrary data related to the transaction in the settlement data, such as the member code, date and time, payment method, and payment processing code. When the store server 20 receives transaction data, it updates the journal database to include that transaction data. The journal database is a database that represents the history of past transactions. The journal database is stored, for example, in a storage device 20a. Thus, the processor 31 outputs the transaction data for storage in the memory device 20a, which acts as a memory device. In other words, by executing information processing based on the transaction processing program AP1, the computer with the processor 31 as its central component functions as an output means.

[0094] As ACT49, processor 31 performs a process to register the electronic receipt data for the completed transaction in the electronic receipt server 4 so that customer M1 can view it. This process may be the same as the process performed by existing electronic receipt services.

[0095] As ACT50, the processor 31 instructs the cart terminal 10 to display the completion screen. The completion screen is a screen that notifies the operator that payment has been completed. The cart terminal 10 displays a completion screen on the touch panel 11e in response to the above instructions. Once customer M1 confirms that payment is complete via the completion screen, they instruct the cart terminal 10 to end its use, for example, by operating a button displayed on the completion screen. In response, the processor 11a in the cart terminal 10 notifies the virtual POS server 30 that an end-of-use instruction has been given. On the virtual POS server 30, the processor 31 instructs the system to display the completion screen, and then proceeds to ACT 51. As ACT51, processor 31 waits for a completion instruction. If processor 31 is notified by the cart terminal 10 that a completion instruction has been given, as described above, it determines YES and proceeds to ACT65 in Figure 12.

[0096] On the other hand, if the received result code does not indicate completion, processor 31 determines NO in ACT47 and proceeds to ACT52. As ACT52, processor 31 checks whether the payment failed or not. If the received result code indicates failure, processor 31 determines it is YES and proceeds to ACT53. As ACT53, processor 31 instructs cart terminal 10 to display an error screen. The error screen is a screen that notifies the operator that the payment has failed. The cart terminal 10 displays an error screen on the touch panel 11e in response to the above instructions. If customer M1 confirms from the error screen that the payment has failed, they instruct the customer to retry the payment, for example by operating a button displayed on the error screen. In response, the processor 11a in the cart terminal 10 notifies the virtual POS server 30 that a retry instruction has been given.

[0097] On the virtual POS server 30, the processor 31 instructs the display of an error screen, and then proceeds to ACT54. As ACT54, processor 31 awaits a retry instruction. If processor 31 receives notification from cart terminal 10 that a retry instruction has been made, as described above, it determines that the instruction is YES and returns to ACT41 in Figure 14. In other words, processor 31 returns cart terminal 10 to the state where the selection screen SC12 is displayed on the touch panel 11e, and repeats the subsequent processing as described above. Processor 31 may also return to ACT44 in Figure 15.

[0098] If the received result code indicates incomplete, the processor 31 determines NO for both ACT47 and ACT52 in Figure 15 and proceeds to ACT55. Furthermore, if no result code is received, it is unclear whether the payment has been completed or not. Therefore, if the waiting state of ACT45 and ACT46 times out, processor 31 determines YES in ACT45 and proceeds to ACT55. In other words, the processor 31 detects that it is unclear whether the settlement has been completed or not when it is notified by the settlement server 3 that the settlement is incomplete, or when a timeout occurs without a result code being received. Thus, by having the processor 31 perform information processing based on the transaction processing program AP1, the computer with the processor 31 as its central component functions as a detection means. As ACT55, processor 31 sends transaction data to store server 20. The transaction data sent here may be the same as the transaction data sent in ACT48. However, the transaction data sent here includes data indicating that the settlement is not yet completed.

[0099] As ACT56, processor 31 instructs cart terminal 10 to display a second confirmation screen. The second confirmation screen is a screen that allows store employee M2 to perform confirmation work regarding any pending payments. Figure 20 shows an example of the second confirmation screen SC15. The second confirmation screen SC15 displays a code symbol CS51, a message ME51, and a button BU51. The code symbol CS51 represents the second identification data included in the transaction data transmitted in ACT55. In the example in Figure 20, a barcode is used as the code symbol. Message ME51 is a text message informing customer M1 that they need to contact store clerk M2 to confirm the payment status. Button BU51 is an operation button used by store clerk M2 to instruct the second confirmation screen SC15 to be dismissed. Thus, in the second confirmation screen SC15, the code symbol CS51 may change from the state shown in Figure 20 depending on the identification data, while other display elements generally remain unchanged. Displaying the second confirmation screen SC15 is equivalent to outputting the second identification data represented by the code symbol CS51. Thus, instructing the cart terminal 10 to display the second confirmation screen is the same as instructing it to output the second identification data. In other words, by having the processor 31 execute information processing based on the transaction processing program AP1, the computer with the processor 31 as its central component functions as an instruction means.

[0100] The cart terminal 10 displays a second confirmation screen SC15 on the touch panel 11e in accordance with the above instructions. Customer M1 makes a request to store clerk M2, following the instructions in message ME51. Upon receiving this request, store clerk M2, for example, activates the journal search function of the manned checkout machine 40 and has the cart terminal 10 read the code symbol CS51 displayed on the touch panel 11e. When the manned checkout machine 40 reads the code symbol CS51, it determines the second identification data that the code symbol CS51 represents. The manned checkout machine 40 obtains transaction data containing the determined second identification data from the store server 20. The manned checkout machine 40 outputs the first identification data included in the obtained transaction data by displaying or printing it. Employee M2 contacts a predetermined number by phone or other means to inquire about the status of the electronic payment for the request identified by the first identification data. Once Employee M2 confirms that the payment has been completed, they perform a predetermined operation to confirm completion at the manned checkout machine. 40 This is done. The manned cashier 40 then requests the store server 20 to either delete the transaction data in the journal database that includes the second identification data determined above, indicating that the settlement is incomplete, or to rewrite the data to indicate that the settlement has been completed. The store server 20 updates the journal database in response to this request.

[0101] If employee M2 confirms that the payment has not been completed, they operate the cashier machine 40 to perform the payment based on the payment data included in the acquired transaction data. If the payment is completed through the processing in response to this operation, the cashier machine 40 requests the store server 20 to rewrite the transaction data in the journal database, which includes the second identification data determined above, to reflect the result of the payment. The cashier machine 40 also requests the store server 20 to either delete the data indicating that the payment is incomplete in the transaction data in the journal database, which includes the second identification data determined above, or to rewrite the data indicating that the payment has been completed. The store server 20 updates the journal database in response to these requests. Furthermore, the process of confirming the payment status and the process of re-processing any incomplete payments may be performed using separate devices. The device used for these operations may also be the employee terminal 70.

[0102] Now, in the virtual POS server 30, after the processor 31 displays the second confirmation screen SC15 on the cart terminal 10 in ACT56 in Figure 15, it transitions to the standby state of ACT57. In ACT57, processor 31 waits for a release operation to be performed. The release operation is a predetermined operation to be performed by employee M2 after the above-mentioned procedures have been carried out by employee M2. For example, the release operation involves customer M1 operating button BU51 displayed on the second confirmation screen SC15, accompanied by a hidden operation that is not normally known to the customer M1. When the cart terminal 10 notifies that such a release operation has been performed, processor 31 determines it to be YES and proceeds to ACT65 in Figure 12.

[0103] On the other hand, if the processor 31 is instructed to use the self-checkout machine 50 for payment, for example by operating button BU21 on the selection screen SC12, it determines NO at ACT43 in Figure 14 and proceeds to ACT58. The processor 31 also proceeds to ACT58 if it determines NO at ACT40 because through checkout is not permitted. In other words, the processor 31 proceeds to ACT58 when it is necessary to start payment using the self-checkout machine 50.

[0104] As ACT58, the processor 31 sends accounting data to the communication network 2 so that one of the self-checkout machines 50 in standby mode can acquire it. For example, the processor 31 finds a self-checkout machine 50 that is in standby mode and sends the accounting data to that machine. Alternatively, for example, the processor 31 sends accounting data to one of the self-checkout machines 50, regardless of whether that machine is in standby mode or not. In this case, the self-checkout machine 50 designated as the recipient of the accounting data accepts the accounting data if it is in standby mode. However, if the self-checkout machine 50 is not in standby mode, it forwards the accounting data to another self-checkout machine 50. Alternatively, for example, the processor 31 broadcasts the accounting data to multiple self-checkout machines 50. In this case, one of the multiple self-checkout machines 50 that is in standby mode accepts the accounting data. Furthermore, as long as the accounting data is accepted by one of the self-checkout machines 50 in standby mode, the accounting data may be transmitted by any other method.

[0105] The accounting data is necessary for settling the payment for purchased items registered in the cart terminal 10 at the self-checkout machine 50. Specifically, the processor 31, for example, finds a data record DR4 in the cart management database DB1 whose terminal code set in field F41 matches the terminal code of the cart terminal 10. The processor 31 then retrieves the transaction code set in field F43 of the corresponding data record DR4. Next, the processor 31 finds a data record DR5 in the purchased items database DB2 whose transaction code set in field F51 matches the transaction code retrieved above. The processor 31 then generates accounting data by combining the data set in each field of the found data record DR4 and the product data contained in the found data record DR5. The processor 31 may also calculate the settlement amount related to the sale of purchased items based on the product data contained in the found data record DR5 and include it in the accounting data.

[0106] As ACT59, processor 31 instructs cart terminal 10 to display a guidance screen. The guidance screen informs customer M1 of the self-checkout machine 50 that has received the payment data and instructs customer M1 to complete the payment at that self-checkout machine 50.

[0107] The cart terminal 10 displays a guidance screen on the touch panel 11e in accordance with the above instructions. Customer M1 operates the self-checkout machine 50 as instructed on the guidance screen to pay for the purchased items. The operation of the self-checkout machine 50 may be the same as, for example, the operation of a checkout machine in an existing semi-self-checkout system. Once the payment is complete, the self-checkout machine 50 notifies the virtual POS server 30 of the completion of the payment.

[0108] As ACT60, processor 31 waits for notification of payment completion from self-checkout machine 50, which received the accounting data transmitted in ACT58. If completion is notified, processor 31 determines it is YES and proceeds to ACT65 in Figure 12.

[0109] Incidentally, customer M1 can also find a self-checkout machine 50 that is in standby mode and use that machine to make a payment. In this case, customer M1 first operates button BU2 displayed on the registration screen SC11. In response, the cart terminal 10 notifies the virtual POS server 30 that the payment button has been operated. When notified that the accounting button has been operated in this manner, the processor 31 determines YES at ACT24 in Figure 12, NO at ACT27 and ACT29 in Figure 13, and NO at ACT37, ACT39, and ACT42 in Figure 14, and proceeds to ACT61 in Figure 14.

[0110] As ACT61, processor 31 checks whether the operation is an operation of the accounting button. Thus, processor 31 determines YES in the above case and proceeds to ACT62. If the notified operation is not an operation of the accounting button, processor 31 determines NO in ACT61 and proceeds to the processing corresponding to the operation.

[0111] As ACT62, processor 31 instructs cart terminal 10 to display the scan screen. The scan screen is used to instruct self-checkout machine 50 to acquire accounting data. After this, processor 31 returns to the standby state of ACT24 to ACT26 in Figure 12. Figure 21 shows an example of the SC16 scanning screen. The scanning screen SC16 represents area AR61, code symbol CS61, message ME61, and button BU61. Area AR61 represents the amount that customer M1 should pay. Code symbol CS61 contains data necessary for the self-checkout machine 50 to obtain accounting data related to the cart terminal 10 from the virtual POS server 30. The data contained in this code symbol includes, for example, a transaction code. In the example in Figure 21, a barcode is used as the code symbol. Message ME61 is a text message that instructs the operator to scan code symbol CS61 with the scanner SC2 of the self-checkout machine 50. Button BU61 is an operation button that allows the operator to instruct themselves to log off to finish shopping. Thus, on the scanning screen SC16, the amount and code symbol CS61 displayed in area AR61 may change from the state shown in Figure 21 depending on the registration status of the purchased product and the transaction code, while other display elements generally remain unchanged.

[0112] The cart terminal 10 displays the scan screen SC16 on the touch panel 11e in accordance with the above instructions. Customer M1 uses the scanner SC2 of the standby self-checkout machine 50 to read the code symbol CS61 displayed on the scan screen SC16. When the scanner SC2 reads the code symbol CS61, the self-checkout machine 50 requests accounting data related to the cart terminal 10 from the virtual POS server 30 based on the transaction code contained in the code symbol CS61. The transaction code may be output using a method other than display, such as wireless transmission using short-range wireless communication technology. The scanned product code may be stored in the cart terminal 10, in which case the product code may be output as information for accounting.

[0113] When the processor 31 in the virtual POS server 30 receives a request for accounting data in this manner, it determines YES at ACT26 in Figure 12 and proceeds to ACT63. As ACT63, processor 31 sends accounting data similar to ACT58 to the requesting self-checkout machine 50. Customer M1 operates the self-checkout machine 50 to settle the payment for the purchased goods. The operation of the self-checkout machine 50 may be similar to, for example, the operation of an accounting machine in an existing semi-self-checkout system. Once the self-checkout machine 50 has completed the payment, it notifies the virtual POS server 30 of the completion of the payment.

[0114] As ACT64, processor 31 waits for notification of payment completion from self-checkout machine 50, which is the destination of the accounting data in ACT63. If completion is notified, processor 31 determines it is YES and proceeds to ACT65. Thus, if the processor 31 is notified of the completion of the settlement in either the waiting state of ACT60 in Figure 14 or ACT64 in Figure 12, it proceeds to ACT65. Also, as described above, the processor 31 proceeds from ACT51 or ACT57 in Figure 15 to ACT65 in Figure 12.

[0115] As ACT65, processor 31 performs termination processing to end the transaction that is the subject of this information processing. For example, processor 31 sends transaction data representing the details of the transaction to store server 20. The transaction data represents the details of the transaction and the accounting results. The transaction data may be similar to the data stored in an existing POS system for managing completed transactions. Processor 31 also deletes data records DR4 and DR5 that were included in the cart management database DB1 and the purchased product database DB2 for the current transaction. In other words, processor 31 deletes data record DR4, in which the terminal code of the cart terminal 10 is set in field F41, and data record DR5, in which the same transaction code as the transaction code set in field F43 of data record DR4 is set in field F51, from cart management database DB1 and purchased product database DB2, respectively. As ACT66, processor 31 notifies cart terminal 10 that it is permitted to log off. Then processor 31 terminates information processing for cart terminal 10.

[0116] When the processor 11a in the cart terminal 10 receives a notification from the virtual POS server 30 to allow logoff, it determines YES in ACT6 in Figure 11 and proceeds to ACT10. As ACT10, processor 11a displays the logoff screen on touch panel 11e. The logoff screen is a screen that shows a logoff button for the user to initiate logoff.

[0117] As ACT11, processor 11a waits for an operation to log off to be performed. Then, if, for example, the log off button is pressed, processor 11a determines it to be YES and proceeds to ACT12. As ACT12, processor 11a executes the logoff process. The logoff process is the process of transitioning to a standby state that is not being used by customer M1.

[0118] As ACT13, processor 11a checks whether the battery unit 11j is low on charge. For example, processor 11a obtains the remaining charge value measured by battery unit 11j and compares this value with a predetermined threshold. Then processor 11a determines that the battery is low if the remaining charge value is below the threshold. Alternatively, processor 11a may determine that the battery is low if the remaining charge value of battery unit 11j is below a predetermined threshold. The threshold is assumed to be "35%" as an example. However, the threshold may be arbitrarily determined by the creator of the transaction processing program AP1 or the administrator of the virtual POS server 30. The threshold is stored, for example, in the auxiliary storage unit 11c. Then processor 11a determines YES if the battery unit 11j is low on charge and proceeds to ACT14.

[0119] As ACT14, processor 11a performs a warning action. This warning action is to alert store clerk M2 that the battery unit 11j is low. The warning action may be, for example, a notification to the store clerk terminal 70. The warning action may be, for example, the display of a predetermined warning screen on the touch panel 11e. The warning action may be, for example, the output of a predetermined voice message or warning sound from the sound unit 11f. The warning action may be performed as a single action or as multiple actions in parallel.

[0120] In response to the warning, employee M2, who is responsible for maintaining cart C, replaces the external battery 16 connected to cart terminal 10 with another fully charged external battery 16. Once the fully charged external battery 16 is connected to cart terminal 10, the power unit 11i will operate using power supplied from the external battery 16, allowing cart terminal 10 to operate stably regardless of the remaining charge of battery unit 11j. In addition, battery unit 11j is charged by the power supplied from the external battery 16. After employee M2 has finished replacing the external battery 16, they perform a predetermined release operation, for example, on the touch panel 11e.

[0121] As ACT15, processor 11a waits for the release operation to be performed. If the release operation is performed as described above, processor 11a determines it to be YES and returns to the standby state of ACT1. If the battery unit 11j is not low on charge, processor 11a determines it to be NO in ACT13, skips ACT14 and ACT15, and returns to the standby state of ACT1.

[0122] As described above, store system 1 can easily handle situations where electronic payment for through checkout is not completed, as previously stated.

[0123] This embodiment can be modified as follows: Figure 22 is a flowchart showing a modified example of information processing by processor 31. Note that Figure 22 only shows the differences from the information processing shown in Figures 12 to 15, and the same reference numerals are used for processes that are the same as those shown in Figures 12 to 15.

[0124] If processor 31 determines NO in ACT40 because through checkout is not permitted, it proceeds to ACT71. As ACT71, the processor 31 checks whether customer M1 is a member of the electronic receipt service. If customer M1 is not a member of the electronic receipt service, the processor 31 determines NO and proceeds to ACT58. In other words, if customer M1 is not a member of the electronic receipt service, the processor 31 processes the case in the same manner as in the previously described embodiment, except for the check in ACT71.

[0125] However, if the customer M1 is a member of the electronic receipt service, the processor 31 determines YES in ACT71 and proceeds to ACT72. As ACT72, processor 31 instructs cart terminal 10 to display a transfer screen. The transfer screen is a screen that instructs customer M1 to transfer the accounting data to self-checkout machine 50. The transfer screen also displays a message that if customer M1 wishes to perform a through checkout, they should ask store employee M2 for confirmation.

[0126] The cart terminal 10 displays a transfer screen on the touch panel 11e in accordance with the above instructions. If customer M1 decides to pay at the self-checkout machine 50 instead of performing a through checkout, they perform an operation on the transfer screen to instruct the self-checkout machine 50 to transfer the payment data. In response, the cart terminal 10 notifies the virtual POS server 30 that a transfer has been instructed.

[0127] When notified that a transfer has been instructed in this manner, the processor 31 determines YES at ACT24 in Figure 12, NO at ACT27 and ACT29 in Figure 13 and ACT39 and ACT42 in Figure 14, respectively, and then determines NO again at ACT61 before proceeding to ACT73. As ACT73, processor 31 checks whether it is a transfer instruction or not. Thus, processor 31 determines that in the above case it is YES and proceeds to ACT58.

[0128] On the other hand, if customer M1 wishes to perform a through checkout, they follow the instructions on the transfer screen and request confirmation from store clerk M2. In response to this request, store clerk M2 checks for situations where through checkout is not permitted and takes measures to resolve the situation. For example, if the purchased items include products with age restrictions or other restrictions for the purchaser, store clerk M2 confirms that customer M1 meets the restrictions. Store clerk M2 also confirms, for example, that all items on cart C are registered as purchased items. In such cases, store clerk M2 performs a special operation for store clerk M2, for example on the touch panel 11e, to instruct that the checkout be permitted. In response, cart terminal 10 notifies the virtual POS server 30 that it has been instructed to allow the checkout.

[0129] When notified that it has been instructed to allow this, the processor 31 determines YES at ACT24 in Figure 12, NO at ACT27 and ACT29 in Figure 13 and ACT39 and ACT42 in Figure 14, respectively, and then determines NO at ACT61 and ACT73, respectively, before proceeding to ACT74. As ACT74, processor 31 checks whether it has been instructed to allow through checkout. Thus, if the above is the case, processor 31 determines YES and proceeds to ACT44. In other words, processor 31 moves on to processing for through checkout.

[0130] If employee M2 confirms that there are items in cart C that are not registered as purchase items, employee M2 will either instruct customer M1 to register those items as purchase items, or employee M2 will perform the operation to register those items as purchase items with customer M1's consent. Once all items in cart C are registered as purchase items, the situation may become such that through checkout is permitted. And once the situation becomes such that through checkout is permitted, customer M1 can start the through checkout process.

[0131] If employee M2 confirms that through checkout is not possible, they will inform customer M1 and instruct them to pay at self-checkout machine 50. Therefore, although it requires verification by staff member M2, if the situation allows for through checkout after that verification, customer M1 can use through checkout.

[0132] In addition to the above, this embodiment can be implemented in various other ways, such as the following. If the processor 31 determines NO in ACT40 or ACT43 in Figure 14, it may instruct the cart terminal 10 to display the scan screen SC16. Then, depending on whether accounting data has been requested based on the code symbol CS61 displayed on the scan screen SC16, it may process ACT63 and subsequent steps. In this case, contrary to the above embodiment, the processor 31 may proceed to ACT58 in response to the operation of button BU2 displayed on the registration screen SC11.

[0133] The information processing shown in Figures 12 to 15 may be executed by processor 11a on the cart terminal 10. In this case, the cart terminal 10 will function as a transaction processing device on its own. Alternatively, the information processing shown in Figures 12 to 15 may be divided and executed by processor 11a and processor 31. Note that processor 11a does not execute processing for managing multiple cart terminals 10, such as ACT20, ACT34, and ACT35 in Figure 12.

[0134] The functions of the virtual POS server 30 may be assigned to the store server 20 or another server. Alternatively, the functions of the virtual POS server 30 may be implemented through distributed processing by multiple servers.

[0135] Customer M1 may use a smartphone or other information terminal that they brought into the store instead of the shopping cart terminal 10.

[0136] At least one of the scanner 12, reader 13, camera 14, beacon receiver 15, and external battery 16 may be attached externally as an optional device, rather than being a component of the cart terminal 10.

[0137] The tablet computer 11 may have a built-in camera, and the symbol code may be captured using this camera. In this case, the processor 11a extracts the product code from the image obtained by the capture, and the processor 11a functions as an acquisition means.

[0138] Each function realized by processor 11a or processor 31 through information processing can also be partially or entirely realized by hardware that performs non-program-based information processing, such as logic circuits. Furthermore, each of the above functions can also be realized by combining the above-mentioned hardware, such as logic circuits, with software control.

[0139] While several embodiments of the present invention have been described, these embodiments are presented as examples only and are not intended to limit the scope of the invention. These novel embodiments can be carried out in a variety of 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 in the scope and spirit of the invention, as well as in the claims of the invention and its equivalents. The invention described in the original claims of this application is listed below. [Note 1] A transaction processing system including a mobile terminal equipped with means for obtaining a product code that identifies the product subject to the transaction, A request means for requesting electronic settlement of the aforementioned transaction from a settlement device, Output means for outputting transaction data relating to the transaction, which includes at least first identification data for distinguishing the electronic payment case requested by the request means in relation to the transaction from another electronic payment case requested to the payment device, and for storing the transaction data relating to the transaction in a storage device. A detection means for detecting whether or not the electronic payment requested by the request means has been completed is unknown. In response to the detection means detecting that the transaction has become unknown, the instruction means instructs the mobile terminal to output a second identification data for identifying the transaction data stored in the storage device with respect to the transaction that is the subject of the unknown electronic payment, A transaction processing system equipped with the following features. [Note 2] The output means includes settlement data for settling the transaction in the transaction data. The transaction processing system described in Appendix 1. [Note 3] The mobile terminal further comprises a display device, The instruction means instructs the mobile terminal to display a screen on the display device showing a code symbol representing the second identification data. The transaction processing system described in Appendix 1. [Note 4] A transaction processing device that constitutes a transaction processing system together with a mobile terminal equipped with means for obtaining a product code that identifies the product subject to the transaction, A request means for requesting electronic settlement of the aforementioned transaction from a settlement device, Output means for outputting transaction data relating to the transaction, which includes at least first identification data for distinguishing the electronic payment case requested by the request means in relation to the transaction from another electronic payment case requested to the payment device, and for storing the transaction data relating to the transaction in a storage device. A detection means for detecting whether or not the electronic payment requested by the request means has been completed is unknown. In response to the detection means detecting that the transaction has become unknown, the instruction means instructs the mobile terminal to output a second identification data for identifying the transaction data stored in the storage device with respect to the transaction that is the subject of the unknown electronic payment, A transaction processing device equipped with the following. [Note 5] A computer installed in a transaction processing device that constitutes a transaction processing system together with a mobile terminal equipped with means for obtaining a product code that identifies the product subject to the transaction, A request means for requesting electronic settlement of the aforementioned transaction from a settlement device, Output means for outputting transaction data relating to the transaction, which includes at least first identification data for distinguishing the electronic payment case requested by the request means in relation to the transaction from another electronic payment case requested to the payment device, and for storing the transaction data relating to the transaction in a storage device. A detection means for detecting whether or not the electronic payment requested by the request means has been completed is unknown. In response to the detection means detecting that the transaction has become unknown, the instruction means instructs the mobile terminal to output a second identification data for identifying the transaction data stored in the storage device with respect to the transaction that is the subject of the unknown electronic payment, An information processing program that enables a function to work. [Explanation of symbols]

[0140] 1...Store system, 2...Communication network, 2a...Access point, 3...Payment server, 4...Electronic receipt server, 5...Member server, 10...Cart terminal, 11...Tablet computer, 11a...Processor, 11b...Main memory, 11c...Auxiliary storage unit, 11d...Wireless unit, 11e...Touch panel, 11f...Sound unit, 11g...Interface unit, 11h...Transmission path, 11i...Power supply unit, 11j...Battery unit, 12...Scanner, 13...Reader, 14...Camera, 15...Beacon receiver, 16...External battery, 20...Store server, 30...Virtual POS server, 31...Processor, 32...Main memory, 33...Auxiliary storage unit, 34...Communication interface, 35...Transmission path, 40...Manned checkout machine, 50...Self-checkout machine, 60...Beacon transmitter, 70...Employee terminal.

Claims

1. A transaction processing system including a mobile terminal equipped with an acquisition means for acquiring a product code that identifies the product subject to a transaction in response to customer operation, and a display device, A request means for requesting electronic settlement of the aforementioned transaction from a settlement device, A first output means that outputs transaction data relating to the said transaction for storage in a storage device, wherein the transaction data includes a second identification data for distinguishing the said transaction data from other transaction data stored in the storage device, and a first identification data for distinguishing the electronic settlement request by the request means relating to the said transaction from other request requests received by the settlement device. A detection means for detecting whether or not the electronic payment requested by the request means has been completed is also included. In response to the detection means detecting that the aforementioned information has become unknown, the mobile terminal is instructed to display a screen containing a code symbol on the display device, wherein the code symbol represents a second identification data for identifying transaction data related to the transaction that is the subject of the unknown electronic payment among the transaction data stored in the storage device, An acquisition means for reading the code symbol and obtaining transaction data including the second identification data represented by the code symbol from the storage device, A second output means that outputs the first identification data included in the transaction data acquired by the acquisition means in a way that can be confirmed by a store employee, A transaction processing system equipped with the following features.

2. The first output means includes settlement data for settling the same transaction in the transaction data to be output. The transaction processing system according to claim 1.

Images