Transaction processing system, terminal device, accounting device, and information processing program

Abstract

To enable a user to terminate a transaction.SOLUTION: A transaction processing system of an embodiment is configured to include: a transaction processing device including first generation means; a mobile terminal including requesting means, second generation means, and output means; and an accounting device including determination means and settlement means. The first generation means is included in the transaction processing device, and generates a first list of commodities targeted for one transaction. The requesting means requests the first generation means to update the first list in response to an operation on the mobile terminal. The second generation means generates a second list of commodities targeted for the transaction in response to an operation on the mobile terminal. The output means outputs the second list generated by the second generation means. The determination means determines an amount to be settled based on the first list generated by the first generation means and the second list output from the output means. The settlement means settles the amount determined by the determination means.SELECTED DRAWING: Figure 9

Description

[Technical field]

[0001] An embodiment of the present invention relates to a transaction processing system, a terminal device, an accounting device, and an information processing program. [Background technology]

[0002] A transaction processing system has already been realized in which a user moves around a store with a mobile terminal and performs operations on the mobile terminal to register purchases of products displayed and sold in the store. In this type of transaction processing system, a type is known in which the mobile terminal functions mainly as a user interface device, and the creation of a list of registered purchased transaction products is performed by a separate transaction processing device.

[0003] However, in this type of transaction processing system, if the mobile terminal and the transaction processing device are unable to cooperate due to an abnormality in communication between them, the transaction processing system will be unable to process the transaction properly. In view of these circumstances, it has been desirable for users to be able to complete transactions even if a situation arises in which their mobile terminal cannot link with the transaction processing device. [Prior art documents] [Patent documents]

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

[0005] The problem that the present invention aims to solve is to provide a transaction processing system, terminal device, accounting device, and information processing program that enable a user to complete a transaction even if a situation arises in which the mobile terminal cannot be linked to the transaction processing device. [Means for solving the problem]

[0006] The transaction processing system of the embodiment includes a transaction processing device having a first creation means, a mobile terminal having a request means, a second creation means, and an output means, and an accounting device having a determination means and a settlement means. The first creation means is provided in the transaction processing device and creates a first list of products to be the subject of one transaction. The request means requests the first creation means to update the first list in response to an operation on the mobile terminal. The second creation means creates a second list of products to be the subject of the transaction in response to an operation on the mobile terminal. The output means outputs the second list created by the second creation means. The determination means determines the amount to be settled based on the first list created by the first creation means and the second list output by the output means. The settlement means settles the amount determined by the determination means. [Brief description of the drawings]

[0007] [Figure 1] 1 is a block diagram showing a schematic configuration of a transaction processing system 1 according to an embodiment. [Diagram 2] 2 is a block diagram showing a main circuit configuration of the transaction processing device in FIG. 1. [Diagram 3] FIG. 3 is a diagram showing a schematic configuration of the transaction data in FIG. 2. [Figure 4] 2 is a block diagram showing a main circuit configuration of the user terminal in FIG. 1. [Diagram 5] FIG. 5 is a diagram illustrating a configuration of product code list data in FIG. 4. [Figure 6] FIG. 2 is a block diagram showing the main circuit configuration of the accounting device in FIG. 1. [Figure 7] 13 is a flowchart of a user terminal process. [Figure 8] 13 is a flowchart of a user terminal process. [Figure 9] 13 is a flowchart of a user terminal process. [Figure 10] 13 is a flowchart of a user terminal process. [Figure 11] 13 is a flowchart of a user terminal process. [Figure 12] 13 is a flowchart of a user terminal process. [Figure 13] Flowchart of smartphone POS processing. [Figure 14] Flowchart of smartphone POS processing. [Figure 15] FIG. 13 is a diagram showing a first registration screen. [Figure 16] A diagram showing the product scanning screen. [Figure 17] FIG. 13 is a diagram showing a registration confirmation screen. [Figure 18] FIG. 13 is a diagram showing a first registration screen. [Figure 19] FIG. [Figure 20] FIG. 13 is a diagram showing a second registration screen. [Figure 21] FIG. 13 is a diagram showing a second registration screen. [Figure 22] FIG. 13 is a diagram showing a first registration screen. [Figure 23] FIG. 13 is a diagram showing a second registration screen. [Figure 24] FIG. 13 is a diagram showing a first takeover screen. [Diagram 25] 13 is a flowchart of accounting processing. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] Hereinafter, an example of an embodiment will be described with reference to the drawings. FIG. 1 is a block diagram showing a schematic configuration of a transaction processing system 1 according to this embodiment. Transaction processing system 1 is configured so that transaction processing device 100, user terminal 200, cart terminal 300, in-company server 400, in-store Web client 500, in-store POS 600, accounting device 700 and employee terminal 800 can communicate via communication network 2.

[0009] Transaction processing device 100 is an information processing device that performs information processing to provide a transaction processing service that processes a buying and selling transaction of goods between a store user and a store in accordance with operations performed by the store user at the store using user terminal 200, cart terminal 300, and accounting device 700 as user interface terminals. That is, typically, customers who purchase goods at a store become users of the transaction processing service. Transaction processing device 100 is realized, for example, as a cloud server, and provides the transaction processing service at multiple stores. Transaction processing device 100 may also be realized, for example, as a local server, and provide the transaction processing service at only one store.

[0010] User terminal 200 is an information communication device carried by a user. User terminal 200 is typically owned by a user and brought to a store by the user for use. User terminal 200 is a user interface terminal that receives operations by the user for transaction processing at transaction processing device 100. User terminal 200 may be temporarily lent to the user by the store. User terminal 200 is an example of a mobile terminal.

[0011] Cart terminal 300 is an information processing terminal attached to a shopping cart provided in a store. Cart terminal 300 is loaned to a user together with the shopping cart. Cart terminal 300 is a terminal device operated by a user for transaction processing at transaction processing device 100. Cart terminal 300 is an example of a mobile terminal.

[0012] The in-company server 400 is an information processing device that performs information processing for information management and the like in the company that operates the store in which the in-store system shown in FIG. 1 is installed. The in-store Web client 500, the in-store POS 600, the accounting device 700, and the employee terminal 800 belong to an in-store system established within one store.

[0013] In-store Web client 500 is an information processing device that performs information processing for utilizing Web services, such as cloud services, provided by transaction processing device 100 in an in-store system. The in-store POS 600 is a conventional system that performs transaction processing using store-installed equipment separate from the user terminal 200 or cart terminal 300, such as a face-to-face type, self-service type, or semi-self-service type.

[0014] The transaction device 700 is installed in a store and executes transaction processing related to the transaction processed by transaction processing device 100. The transaction device 700 is operated by an operator during transaction processing. In other words, the transaction device 700 is a terminal device that accepts operations by an operator related to transactions. The operator of the transaction device 700 is primarily a customer. In some cases, the operator of the transaction device 700 is a store clerk.

[0015] Employee terminal 800 is an information processing terminal operated by a store employee. Employee terminal 800 is a terminal device for a user interface related to information processing to support employees who perform the task of replenishing products on display shelves in the store. Employee terminal 800 includes a display device that displays a screen to present information to employees, and an input device for inputting various instructions by employees. Examples of employee terminal 800 that can be used are a GOT (graphic order terminal), an HTL (handy terminal), a smart device, etc.

[0016] Communication network 2 may use the Internet, a virtual private network (VPN), a local area network (LAN), a public communication network, a mobile communication network, etc., either alone or in appropriate combination. As communication network 2, for example, a combination of a LAN, the Internet, and a mobile communication network is used. For communication between transaction processing device 100 and user terminal 200, for example, a mobile communication network and the Internet are used. For communication between transaction processing device 100 and cart terminal 300, for example, a LAN provided within a store and the Internet are used. For communication between transaction processing device 100 and in-house server 400, or between in-house server 400 and in-store Web clients, for example, the Internet is used. For communication in the in-store system, for example, a LAN provided within the store is used.

[0017] Note that any number of transaction processing devices 100, user terminals 200, cart terminals 300, in-company servers 400, in-store Web clients 500, in-store POS 600, accounting devices 700, and employee terminals 800 may be included in transaction processing system 1, but only one of each is shown in Fig. 1. For example, transaction processing system 1 may include multiple in-store systems operated by a single company, and may further include one or more in-company servers 400 related to the company. Also, for example, transaction processing system 1 may include multiple in-store systems operated by different companies, and may further include one or more in-company servers 400 related to each of the multiple companies.

[0018] FIG. 2 is a block diagram showing the main circuit configuration of transaction processing device 100. As shown in FIG. Transaction processing device 100 includes a processor 101, a main memory unit 102, an auxiliary memory unit 103, a communication unit 104, and a transmission path 105. Processor 101, main memory unit 102, auxiliary memory unit 103, and communication unit 104 are capable of communicating with each other via transmission path 105.

[0019] Processor 101 , main memory unit 102 and auxiliary memory unit 103 are connected via transmission line 105 to constitute a computer that performs information processing for controlling transaction processing device 100 . Processor 101 corresponds to the central part of the computer. Processor 101 executes information processing for controlling each part to realize various functions of transaction processing device 100 in accordance with information processing programs such as an operating system and application programs.

[0020] The main memory unit 102 corresponds to the main memory portion of the computer. The main memory unit 102 includes a read-only memory area and a rewritable memory area. The main memory unit 102 stores a part of the information processing program in the read-only memory area. The main memory unit 102 may also store data required for the processor 101 to execute processes for controlling each part in the read-only memory area or the rewritable memory area. The main memory unit 102 uses the rewritable memory area as a work area for the processor 101.

[0021] The auxiliary storage unit 103 corresponds to the auxiliary storage portion of the computer. The auxiliary storage unit 103 may be, for example, an EEPROM (electric erasable programmable read-only memory), a HDD (hard disk drive), an SSD (solid state drive), or any other known storage device. The auxiliary storage unit 103 stores data used by the processor 101 in performing various processes and data generated by the processes in the processor 101. The auxiliary storage unit 103 may also store the information processing program. In this embodiment, the auxiliary storage unit 103 stores a transaction processing program PRA, which is one of the information processing programs. The transaction processing program PRA is an application program in which the procedure of the transaction processing described later is described. A part of the storage area of ​​the auxiliary storage unit 103 is used as an area for storing transaction data DAA. The transaction data DAA is data representing the contents of one transaction. The transaction data DAA is generated by the processor 101 during the processes described later, and is temporarily stored in the auxiliary storage unit 103.

[0022] The communication unit 104 executes communication processing for performing data communication via the communication network 2. For example, an existing wired communication device for the Internet can be used as the communication unit 104. Note that, instead of or in addition to the wired communication device, a wireless communication device connected to the communication network 2 by wireless communication may be used as the communication unit 104. The transmission path 105 includes an address bus, a data bus, and control signal lines, and transmits data and control signals between the connected components.

[0023] FIG. 3 is a diagram showing a schematic configuration of transaction data DAA. The transaction data DAA includes fields FAA, FAB, and FAC. The transaction data DAA may include any number of fields after the field FAD. A transaction code is set in the field FAA as an identifier of the transaction. A terminal code is set in the field FAB as an identifier of the user terminal 200 or cart terminal 300 used by the user who performs the transaction. A user code is set in the field FAC as an identifier of the user who performs the transaction. If there are registered products (hereinafter referred to as transaction products) as the target of the transaction, fields FAD, FAE, ... associated with each of the transaction products are added to the transaction data DAA. Product data related to each separate transaction product is set in the fields FAD, FAE, .... The product data includes a product code and a quantity as an identifier of the transaction product. The product data may include various other information such as product name, unit price, tax category, and discount information.

[0024] The hardware of transaction processing apparatus 100 may be, for example, a general-purpose server device. Transaction processing apparatus 100 is generally transferred in a state in which transaction processing program PRA is stored in auxiliary storage unit 103. However, the hardware in a state in which transaction processing program PRA is not stored in auxiliary storage unit 103, or in a state in which a different version of the same type of application program is stored in auxiliary storage unit 103, and transaction processing program PRA may be transferred separately. Transaction processing apparatus 100 may be configured by writing transaction processing program PRA to auxiliary storage unit 103 in response to an operation by an arbitrary operator. Transaction processing program PRA may be transferred by recording it on a removable recording medium such as a magnetic disk, a magneto-optical disk, an optical disk, or a semiconductor memory, or by communication via a network.

[0025] FIG. 4 is a block diagram showing the main circuit configuration of the user terminal 200. As shown in FIG. The user terminal 200 includes a processor 201, a main memory unit 202, an auxiliary memory unit 203, a touch panel 204, a camera 205, a wireless communication unit 206, a transmission path 207, and the like. The functions of the processor 201 , the main memory unit 202 , the auxiliary memory unit 203 and the transmission path 207 are roughly equivalent to those of the processor 101 , the main memory unit 102 , the auxiliary memory unit 103 and the transmission path 105 .

[0026] However, auxiliary memory unit 203 stores user terminal program PRB instead of transaction processing program PRA. User terminal program PRB is an application program describing the information processing procedures of processor 201 for operating user terminal 200 as a user interface for transaction processing by transaction processing device 100. A part of the memory area of ​​auxiliary memory unit 203 is used as an area for storing product code list data DAB. Product code list data DAB is data representing a list of product codes acquired by user terminal 200 as representing transaction products through operations on user terminal 200. Product code list data DAB is generated by processor 201 during processing described below, and is temporarily stored in auxiliary memory unit 203.

[0027] The touch panel 204 displays a screen for presenting information to the operator, and also inputs instructions by the operator touching the screen through the touch panel 204. The camera 205 includes an optical system and an image sensor, and generates image data representing an image within a field of view formed by the optical system using the image sensor.

[0028] The wireless communication unit 206 executes communication processing for performing data communication via the communication network 2. For example, an existing wireless communication device for wireless LAN can be used as the wireless communication unit 206. Note that instead of or in addition to the wireless communication unit 206, a communication unit connected to the communication network 2 by wire may be used. The basic hardware of the user terminal 200 is assumed to be, for example, the hardware of a smartphone.

[0029] FIG. 5 is a diagram showing a schematic structure of the product code list data DAB. The product code list data DAB includes fields FBA and FBB. The product code list data DAB may include any number of fields after the field FBC. Check-in data or a transaction code, described later, is set in field FBA. Flag data indicating whether or not a failure has occurred in the data exchange between transaction processing device 100 and user terminal 200 during the processing of a transaction related to the relevant product code list data DAB is set as a failure flag in field FBB. In this embodiment, the failure flag indicates that a failure has occurred when it is set. In each field from field FBC onwards, the product code of the product specified as the transaction product is set together with the quantity of the transaction product identified by that product code. Thus, the number of fields from field FBC onwards changes according to the number of product codes already acquired.

[0030] FIG. 6 is a block diagram showing the main circuit configuration of the accounting device 700. The accounting device 700 includes a processor 701, a main memory unit 702, an auxiliary memory unit 703, a touch panel 704, a barcode scanner 705, a credit card reader 706, a near-field communication unit 707, a card reader / writer 708, a change unit 709, a print unit 710, a communication unit 711, and a transmission path 712. The processor 701, the main memory unit 702, the auxiliary memory unit 703, the touch panel 704, the barcode scanner 705, the credit card reader 706, the near-field communication unit 707, the card reader / writer 708, the change unit 709, the print unit 710, and the communication unit 711 are connected to the transmission path 712.

[0031] The processor 701, main memory unit 702, and auxiliary memory unit 703 are connected by a transmission line 712 to constitute a computer for executing information processing relating to the control of the accounting device 700. The functions of processor 701, main memory unit 702, auxiliary memory unit 703, and transmission path 712 are generally the same as those of processor 101, main memory unit 102, auxiliary memory unit 103, and transmission path 105, so a detailed description will be omitted. However, auxiliary memory unit 703 stores accounting processing program PRC instead of transaction processing program PRA. Accounting processing program PRC is an application program that describes the processing procedures for information processing for accepting operations by the user and accounting for a transaction based on transaction information obtained from transaction processing device 100 and request history data obtained from user terminal 200 and cart terminal 300.

[0032] The touch panel 704 displays a screen for presenting information to the operator, and also inputs instructions by the operator touching the screen through the touch panel 704. The barcode scanner 705 optically reads a barcode placed in front of its reading port, and outputs barcode information represented by the read barcode. The credit card reader 706 reads card information from a credit card.

[0033] The near-field communication unit 707 performs near-field communication with a wireless tag that is brought into close proximity to obtain data stored in the wireless tag. The near-field communication unit 707 also writes arbitrary information to the wireless tag through the near-field communication. The card reader / writer 708 reads card data recorded on predetermined cards such as membership cards and prepaid cards, etc. The card reader / writer 708 also writes any data onto the membership card.

[0034] The change unit 709 counts the value of coins inserted through the coin insertion slot and stores them in an internal storage. The change unit 709 discharges coins stored in the storage slot to a coin tray through the coin discharge port. The change unit 709 counts the value of banknotes inserted through the banknote insertion slot and stores them in an internal storage. The change unit 709 discharges banknotes stored in the storage slot from the banknote discharge port. The banknote discharge port holds the discharged banknotes with a portion of them exposed to the outside.

[0035] The print unit 710 prints any image on print paper such as receipt paper under the control of the processor 101. The print unit 710 is primarily used to issue various vouchers such as receipts, invoices, and coupons. The print unit 710 can also be used to output printed matter on which various other information is printed, such as a daily accounting journal. The receipt printer 110 can be a well-known print device such as a thermal printer. Communications unit 711 performs communication processing for processor 701 to transmit and receive various data to and from any device, such as transaction processing device 100, via communications network 2. As communications unit 711, a well-known device conforming to the communication method of communications network 2 can be used.

[0036] The basic hardware of the accounting device 700 may be, for example, the hardware of an accounting device used in an existing POS system. In this case, the accounting device 700 is generally transferred in a state in which the accounting processing program PRC is stored in the auxiliary storage unit 703. However, the accounting device 700 hardware and the accounting processing program PRC may be transferred separately in a state in which the accounting processing program PRC is not stored in the auxiliary storage unit 703. Then, the accounting processing program PRC may be written in the auxiliary storage unit 703 in response to an operation by an arbitrary worker. Alternatively, the accounting device 700 hardware and the accounting processing program PRC may be transferred separately in a state in which an information processing program of the same type as the accounting processing program PRC and a different version are stored in the auxiliary storage unit 703. Then, the accounting processing program PRC may be written in a form that replaces the information processing program already stored in the auxiliary storage unit 703. The accounting processing program PRC may be transferred by recording it on a removable recording medium such as a magnetic disk, a magneto-optical disk, an optical disk, or a semiconductor memory, or by communication via a network. The accounting processing program PRC may be stored in the main storage unit 702.

[0037] The main circuit configuration of cart terminal 300 is substantially the same as that shown in Fig. 4, for example, and therefore illustration and description are omitted. However, it is assumed that the basic hardware of cart terminal 300 will be that of a tablet computer. Also, a cart terminal program is used instead of user terminal program PRB. The cart terminal program is similar to user terminal program PRB in that it is an application program that describes the procedures for information processing for operating as a user interface for transaction processing by transaction processing device 100.

[0038] A general-purpose information processing device for servers can be used as the basic hardware of the in-house server 400. A general-purpose information processing device for clients can be used as the basic hardware of the in-store Web client 500. An existing device can be used as the employee terminal 800. Therefore, illustrations and explanations of the configurations of the in-house server 400, in-store Web client 500, and employee terminal 800 are omitted.

[0039] Next, the operation of the transaction processing system 1 configured as described above will be described. Note that the contents of the various processes described below are merely examples, and it is possible to change the order of some of the processes, omit some of the processes, or add other processes as appropriate. For example, in the following explanation, in order to easily explain the characteristic operations of this embodiment, the explanation of some of the processes is omitted. For example, when some kind of error occurs, a process may be performed to deal with the error, but the description of such a process is omitted.

[0040] As described below, the service provided to the user by the transaction processing system 1 is called a smartphone POS service when the user uses the user terminal 200, and is called a cart POS service when the user uses the cart terminal 300. However, since the characteristic operations of this embodiment are performed in the same way for the smartphone POS service and the cart POS service, the following description will focus on the smartphone POS service.

[0041] To use the smartphone POS service, a user installs the user terminal program PRB on an information processing device such as a smartphone owned by the user, and makes it available as the user terminal 200. The user also registers for the user terminal program PRB and obtains a user code. The user code is stored in the auxiliary storage unit 203 of the user terminal 200, for example, as one of the setting data related to the user terminal program PRB. The user then enters a store that offers the smartphone POS service, carrying the user terminal 200 with the processor 201 executing user terminal processing in accordance with the user terminal program PRB.

[0042] 7, 8, 9, 10, 11 and 12 are flowcharts of user terminal processing. 7, the processor 201 displays a top screen on the touch panel 204. The top screen is a screen for allowing a user to specify a function to be executed from among various functions realized by user terminal processing. The top screen shows soft keys for receiving check-in instructions.

[0043] In stores that offer the smartphone POS service, a check-in code that represents check-in data is posted at the store entrance or inside the store. The check-in code is, for example, a two-dimensional code. The check-in data includes at least the store code. Therefore, the check-in code is different for each store.

[0044] When a user wishes to start using the smartphone POS service at a store, the user performs a predetermined operation, such as tapping a soft key displayed on the top screen, to receive check-in instructions. In ACT 202, the processor 201 waits for some operation by the user while displaying the top screen. If some operation by the user is detected, for example, by the touch panel 204, the processor 201 judges the result as YES and proceeds to ACT 203.

[0045] As ACT203, the processor 201 checks whether the operation performed was an operation for instructing check-in. If the processor 101 cannot confirm the relevant event, it judges NO, checks the content of the operation, and proceeds to other processing for carrying out processing accordingly. One of the other processing is, for example, processing for changing user settings related to the user terminal program PRB in response to an instruction from the user. As the other processing, there may be processing other than the above, or multiple processing may be selectively performed, but a detailed description of such processing will be omitted here.

[0046] If an operation for instructing check-in has been performed as described above, the processor 201 judges YES in ACT203 and proceeds to ACT204. As ACT 204, the processor 201 displays a check-in screen on the touch panel 204. The check-in screen is a screen for guiding the user to have the camera 205 of the user terminal 200 capture a photo of the check-in code.

[0047] In ACT 205, the processor 201 waits for some operation to be performed by the user. If the processor 201 confirms that some operation has been performed by the user, it determines YES and proceeds to ACT 206. The user operates the user terminal 200 according to the check-in screen, and causes the camera 205 of the user terminal 200 to capture a check-in code displayed in the store to be used.

[0048] When the two-dimensional code is photographed by the camera 205 in this way, the processor 201 determines that an operation for reading the two-dimensional code has been performed and determines YES in ACT205, and proceeds to ACT206. In ACT 206, the processor 201 checks whether the check-in code has been read by the above-mentioned operation. If the processor 201 cannot check the event, it judges NO, checks the content of the operation, and proceeds to other processing to perform the corresponding processing. As one of the other processing, the processor 201, for example, checks that the operation to read a two-dimensional code is performed, but the two-dimensional code is not a check-in code, and displays a screen to notify the user of such an operational error. As the other processing, processing other than the above or multiple processing may be selectively performed, but a detailed description thereof will be omitted here.

[0049] If the check-in code has been photographed by the camera 205, the processor 201 determines that the check-in code has been read by the above-described operation and judges YES in ACT206, and proceeds to ACT207. In ACT 207, the processor 201 creates product code list data DAB. That is, the processor 201 sets the check-in code read as described above in field FBA, sets a failure flag indicating a reset state in field FBB, and creates product code list data DAB as data that does not include fields FBC and after.

[0050] As ACT208, processor 201 requests transaction processing device 100 to check in. Processor 201, for example, transmits request data for the check-in request from wireless communication unit 206 to communication network 2, addressed to transaction processing device 100. Processor 201 includes in the request data the check-in data represented by the check-in code photographed by camera 205, the terminal code, and the user code. The terminal code is stored, for example, in auxiliary storage unit 203. As the terminal code, for example, an identifier determined by the operating system of user terminal 200 when installing user terminal program PRB can be used. This identifier is, for example, a 32-digit code including both alphanumeric characters. The user code is stored in auxiliary storage unit 203 as described above. However, the user code may not be stored in auxiliary storage unit 203, but may be designated by the user each time a check-in is performed.

[0051] When request data for a check-in request is transmitted to transaction processing device 100 via communication network 2, the request data is received by communication unit 104 in transaction processing device 100 and temporarily stored in main memory unit 102 or auxiliary memory unit 103. In this way, when the request data sent from user terminal 200 is received by transaction processing device 100, processor 101 starts transaction processing for the smartphone POS service (hereinafter referred to as smartphone POS processing) in accordance with transaction processing program PRA.

[0052] However, such a check-in procedure is merely an example, and various modifications are possible. For example, after starting user terminal program PRB, processor 201 of user terminal 200 may transmit check-in data including location information acquired using a GPS (global positioning system) or other positioning sensor to transaction processing device 100. Then, upon receiving the location information, transaction processing device 100 may, for example, acquire store information of the store where user terminal 200 that transmitted the location information is located from a database that represents store information in association with the location information, and perform check-in processing according to this store information.

[0053] If processor 101 is already executing a smartphone POS process for a transaction related to a different user, processor 101 starts a new smartphone POS process as a process of a different thread from the smartphone POS process. That is, processor 101 may execute multiple smartphone POS processes in parallel. In this case, multiple user terminals 200 used by transaction processing device 100 as user interface terminals exist at the same time. However, the following description focuses only on the processing of a transaction related to one user. Thus, "user terminal 200" in the following description refers to one user terminal 200 used by a user for the smartphone POS process of interest. Also, "transaction" in the following description refers to the transaction that is the subject of the processing of interest.

[0054] 13 and 14 are flowcharts of smartphone POS processing. 13, the processor 101 checks whether the smartphone POS service is available for use by the user terminal 200 attempting to check in. For example, if the smartphone POS service is not available during a time period that is permitted at the store where the user is being checked in, the smartphone POS service cannot be used if the predetermined availability conditions are not met. If the processor 101 cannot determine that the smartphone POS service is available, for example, the result is NO, and the process proceeds to ACT102.

[0055] As ACT102, the processor 101 instructs the user terminal 200 to display an unavailable screen in response to the check-in request. The unavailable screen is a screen for making the user aware that the smartphone POS service cannot be used. For example, the processor 101 transmits instruction data for instructing the user terminal 200 to display the unavailable screen from the communication unit 104 to the communication network 2, addressed to the user terminal 200. Then, the processor 101 ends the smartphone POS processing.

[0056] When instruction data for instructing the screen display is transmitted to the user terminal 200 via the communication network 2, the wireless communication unit 206 in the user terminal 200 receives the instruction data. Upon receiving the instruction data, the wireless communication unit 206 notifies the processor 201 of the reception of the instruction data. The instruction data for instructing a screen display may include screen data representing a screen to be displayed in response to the instruction data, or may not include such screen data and may include data for enabling the user terminal 200 to identify the screen to be displayed. In the former case, the processor 101, for example, generates screen data representing a screen to be displayed on the user terminal 200 and includes the screen data in the instruction data. In the latter case, the processor 101, for example, includes in the instruction data a screen identifier that is predetermined to identify a screen to be displayed on the user terminal 200, or a notification identifier that identifies a notification that triggers the screen display. The notification identifier is, for example, information that is predetermined to identify a notification such as "unavailable."

[0057] After the processor 201 in the user terminal 200 requests check-in in ACT 208 in FIG. In ACT 209, the processor 201 checks whether a response has been made to the check-in request. If the processor 201 cannot check the event, it determines NO and proceeds to ACT 210. In ACT210, the processor 201 checks whether a predetermined waiting period has ended regarding the check-in request in ACT208. If the processor 201 cannot check the event, it determines NO and returns to ACT209. Thus, the processor 201 waits for a response to the check-in request until the waiting period ends in ACT209 and ACT210. If instruction data instructing the wireless communication unit 206 to display a screen is received, the processor 201 determines that a response has been made (YES) in ACT209 and proceeds to ACT211.

[0058] In ACT211, the processor 201 checks whether a command has been issued to display a first registration screen, which will be described later. If a command has been issued to display an unavailable screen as described above, the processor 201 determines NO and proceeds to other processing for performing processing according to the screen commanded to be displayed. As one of the other processing, the processor 201 displays an unavailable screen on the touch panel 204, for example, and returns to ACT201 in response to a predetermined confirmation operation being performed. As the other processing, a processing other than the above processing or a plurality of processing may be selectively performed, but a detailed description thereof will be omitted here.

[0059] If the instruction data instructing to display a screen contains screen data, the processor 201 displays the screen represented by the screen data as is on the touch panel 204. If the received instruction data contains a screen identifier, the processor 201 generates a screen identified by the screen identifier and displays it on the touch panel 204. If the received instruction data contains a notification identifier, the processor 201 determines a screen to be displayed in response to the notification identified by the notification identifier, generates the relevant screen, and displays it on the touch panel 204. The transmission and reception of display instructions for various screens, which will be described below, are performed in the same manner as above, although the contents of the screens to be displayed differ.

[0060] On the other hand, if the processor 101 confirms in ACT101 of FIG. 13 that the device is available, it judges as YES and proceeds to ACT103. As ACT103, the processor 101 creates new transaction data. That is, for example, the processor 101 determines a new transaction code different from the transaction code for identifying other transactions according to a predetermined rule, sets this transaction code in the field FAA, and creates new transaction data DAA in which the terminal code received together with the check-in data is set in the field FAB, and stores the data in the auxiliary storage unit 103. As described above, the user terminal 200 includes a user code in the request data when requesting check-in. Also, when the user authenticates the user when the user starts using the cart terminal 300 and the user code is acquired, the cart terminal 300 includes the user code in the request data when requesting check-in. Thus, in these cases, the processor 101 sets the user code in question in the field FAC of the newly created transaction data DAA. However, when the cart terminal 300 is permitted to be used by a user who has not registered, the cart terminal 300 may not include the user code in the request data when requesting check-in. In this case, the processor 101 sets the field FAC of the newly created transaction data DAA to a predetermined state, such as a null state, which indicates that a user code has not yet been acquired.

[0061] In ACT104, the processor 101 instructs the user terminal 200 to display a first registration screen in response to the check-in request. The first registration screen includes a list of products registered as trading products, and is a screen for allowing the user to recognize the registration status of the trading products. For example, the processor 101 generates screen data representing the first registration screen reflecting the registration status of the trading products, and includes the screen data in instruction data for instructing the user terminal 200 to display the screen. In addition, when the process proceeds from ACT103 to ACT104, the processor 101 includes the transaction code determined in ACT103 in the instruction data. As described above, the processor 101 may include a screen identifier of the first registration screen or a notification identifier for identifying the notification of "check-in confirmation completed" in the instruction data, without including the screen data in the instruction data. The generation of the first registration screen may be performed by the processor 201 in the user terminal 200.

[0062] In the user terminal 200, when the processor 201 judges YES in ACT209 in FIG. 7 in response to receiving instruction data for instructing the display of the first registration screen and proceeds to ACT211, it judges the answer to YES since it is an instruction to display the first registration screen and proceeds to ACT212. In ACT212, the processor 201 displays a first registration screen on the touch panel 204. At this time, if a transaction code is included in the instruction data for instructing to display the first registration screen, the processor 201 rewrites the field FBA of the product code list data DAB to the transaction code.

[0063] FIG. 15 is a diagram showing the first registration screen SCA. The first registration screen SCA has an image showing the registration status arranged in the display area ARA. The first registration screen SCA shows buttons BUA and BUB. In the example of Fig. 15, the image arranged in the display area ARA does not show specific information about the trading product because the trading product has not yet been registered, but shows that the total number of items is 0 and the reference price is 0 yen.

[0064] The button BUA is a soft key for receiving a designation to start scanning a new product. The button BUB is a soft key for receiving a designation to start checkout. Note that the first registration screen SCA and various screens described later illustrate main display objects, and some display objects may be omitted. For example, an image may be included on the screen to allow the user to visualize the operations that the user should perform. The first registration screen SCA and various screens described later are merely examples, and may be appropriately determined by, for example, the creator of the transaction processing program PRA.

[0065] After the processor 201 displays the first registration screen SCA on the touch panel 204 in ACT 212 in FIG. 7, the processor 201 proceeds to ACT 221 in FIG. In ACT 221, the processor 201 waits for some operation by the user. If some operation by the user is detected on the touch panel 204, the processor 201 judges the result as YES and proceeds to ACT 222.

[0066] In ACT 222, the processor 201 checks whether the operation performed was an operation for specifying a transaction. If the processor 201 cannot check the corresponding event, it determines NO and proceeds to ACT 223. In ACT223, processor 201 checks whether the performed operation needs to be notified to transaction equipment 100. If the performed operation is not a predetermined operation to be notified, processor 201 determines NO, checks the content of the operation, and proceeds to other processing for performing processing accordingly. As one of the other processing, processor 201 scrolls the first registration screen in response to a scroll operation, for example. As the other processing, there may be a processing other than the above, or multiple processings may be selectively performed, but a detailed description thereof will be omitted here.

[0067] On the other hand, if the performed operation is an operation that is predetermined as a target for notification, the processor 201 determines YES in ACT223 and proceeds to ACT224. As ACT 224, processor 201 notifies transaction equipment 100 of the operation contents. Processor 201, for example, transmits notification data for notifying transaction equipment 100 of the operation contents from wireless communication unit 206 to communication network 2.

[0068] When notification data for notifying the operation content is transmitted to transaction equipment 100 via communication network 2, communication unit 104 in transaction equipment 100 receives the notification data. Upon receiving the notification data, communication unit 104 notifies processor 101 of the reception of the notification data. The sending and receiving of notifications of operation contents on various screens described below is performed in the same manner as above, although the contents of the operations differ.

[0069] After issuing an instruction to display the first registration screen in ACT104 in FIG. 13, the processor 101 proceeds to ACT105. In ACT 105, the processor 101 checks whether an operation has been performed on the user terminal 200. If the processor 101 cannot check the relevant event, it determines NO and proceeds to ACT 106.

[0070] In ACT 106, the processor 101 checks whether a product code list has been notified, as described below. If the processor 101 cannot check the event, it determines NO and returns to ACT 105. Thus, the processor 101 waits for an operation to be performed or for a product code list to be notified in ACT105 and ACT106. If the processor 101 is notified by the communication unit 104 that notification data for notifying the operation contents has been received as described above, the processor 101 judges YES in ACT105 and proceeds to ACT107.

[0071] In ACT 107, the processor 101 checks whether the operation performed was an operation for specifying the start of a scan. If the processor 101 cannot check the event, it determines NO and proceeds to ACT 108. In ACT 108, the processor 101 checks whether the operation performed was an operation for specifying a transaction. If the processor 101 cannot check the corresponding event, it determines NO and proceeds to ACT 109.

[0072] As ACT109, the processor 101 checks whether accounting data has been requested by the accounting device 700, as described below. If the processor 101 cannot check the relevant event, it judges NO, checks the content of the operation, and proceeds to other processing to perform the corresponding processing. As one of the other processes, the processor 101, for example, checks that an operation to cancel the transaction has been performed, executes processing to cancel the transaction, and then ends the registration processing. As the other process, there may be other processes other than those described above, or multiple processes may be selectively performed, but a detailed explanation of these will be omitted here.

[0073] The user searches the store for the product to be purchased, i.e., the product to be the subject of the transaction. When the user wants to register the relevant product as a new transaction product, the user performs a predetermined operation to specify the start of scanning, such as tapping the button BUA on the first registration screen SCA. This operation is the subject of notification, and the processor 201 of the user terminal 200 judges YES, NO, and YES in ACT221, ACT222, and ACT223 in FIG. 8, respectively, and proceeds to ACT224, where it transmits notification data to notify the user of the operation to specify the start of scanning.

[0074] When an operation for specifying the start of scanning is thus notified from user terminal 200 to transaction equipment 100, processor 101 determines YES in ACT 107 in FIG. 13, and proceeds to ACT 121 in FIG. As ACT 121, the processor 101 instructs the user terminal 200 to display a product scan screen. The product scan screen is a screen for scanning a barcode representing a product code.

[0075] After notifying the operation content in ACT224, the processor 201 in the user terminal 200 proceeds to ACT225. In ACT 225, the processor 201 checks whether the operation notified in ACT 224 was an operation for specifying a product. If the processor 201 cannot check the event, it determines NO and proceeds to ACT 226.

[0076] In ACT 226, the processor 201 checks whether the operation notified in ACT 224 was an operation for specifying a quantity change. If the processor 201 cannot check the event, it judges NO and proceeds to ACT 227. In ACT 227, the processor 201 checks whether the operation notified in ACT 224 was an operation for specifying registration. If the processor 201 cannot check the event, it judges NO and proceeds to ACT 228.

[0077] Thus, if the processor 201 has notified the user of an operation to specify the start of scanning as described above, the processor 201 determines NO in all of ACT225, ACT226, and ACT227, and proceeds to ACT228. In ACT228, processor 201 checks whether a display instruction has been issued from transaction equipment 100. If processor 201 cannot check the relevant event, it determines NO and proceeds to ACT229.

[0078] In ACT 229, the processor 201 checks whether a predetermined waiting period has elapsed regarding the notification of the operation content in ACT 224. If the processor 201 cannot check the event, it determines NO and returns to ACT 228. Thus, in ACT228 and ACT229, the processor 201 waits for a display instruction to be made in response to the notification in ACT224 until the waiting period ends. Then, if instruction data instructing the display of any screen is received by the wireless communication unit 206, the processor 201 judges YES in ACT228 and proceeds to ACT230.

[0079] In response to the instruction as ACT230, the processor 201 updates the display screen on the touch panel 204. That is, in response to the instruction to display the product scan screen, the processor 201 updates the display screen on the touch panel 204 to the product scan screen. Then, the processor 201 returns to the standby state of ACT221.

[0080] FIG. 16 is a diagram showing the product scan screen SCB. The product scan screen SCB includes a display area ARB and a button BUC. The display area ARB is an area for displaying an image obtained by the camera 205. The button BUC is a soft key for the user to declare that the scanning of the product code is to be stopped.

[0081] In displaying commodity scan screen SCB in user terminal 200, processor 201 activates camera 205, and thereby superimposes an image obtained by camera 205 within display area ARB. When a predetermined operation for designating the start of scanning is performed, processor 201 may generate commodity scan screen SCB and display it on touch panel 204 without notifying transaction processing device 100 of the operation. In this case, processor 101 in transaction processing device 100 performs the process of ACT123 described below as ACT107 in Fig. 13, and if YES is determined in ACT107, proceeds to ACT124 described below without performing ACT121 to ACT123 described below.

[0082] When commodity scan screen SCB is displayed on touch panel 204, the user operates user terminal 200 so that the barcode displayed on the commodity to be registered as a transaction commodity is reflected within display area ARB. Processor 201 analyzes the image obtained by camera 205 and attempts to read the barcode. If processor 201 is able to read the barcode, the operation for reading such a barcode is the subject of notification. Processor 201 then determines YES, NO, and YES, respectively, in ACT221, ACT222, and ACT223 in FIG. 8, and proceeds to ACT224, where it notifies transaction processing device 100 that a scan operation has been performed, along with a notification of the data represented by the read barcode (hereinafter referred to as barcode data).

[0083] Furthermore, if the user wishes to temporarily stop registering the traded product and check the registration status of the traded product, the user performs a predetermined operation to specify that scanning should be stopped, such as tapping button BUC on product scan screen SCB. This operation is subject to notification, and processor 201 determines YES, NO, and YES, respectively, in ACT221, ACT222, and ACT223 in Fig. 8, proceeds to ACT224, and notifies transaction equipment 100 that an operation to specify that scanning should be stopped has been performed.

[0084] The user's operation to read the barcode is an example of an operation to specify the transaction product as described above. Thus, when the processor 201 is notified in ACT224 that a scan operation has been performed, it determines that the process should proceed to ACT225 (YES), and proceeds to ACT231. In ACT231, the processor 201 sets the product code of the specified product as the product code of the product to be traded (hereinafter referred to as the candidate product code). That is, the processor 201 extracts the product code included in the barcode data represented by the barcode read as described above, and sets the product code as the candidate product code. Note that the processor 101 may set the product code assigned to the preset button displayed on the touch panel 204 as the candidate product code in response to the product being specified by tapping the preset button. The processor 101 may also set the product code directly inputted on the touch panel 204 as a numeric string as the candidate product code. Then, the processor 201 thereafter proceeds to a standby state in ACT228 and ACT229.

[0085] When processor 101 in transaction processing device 100 finishes instructing display of the commodity scan screen in ACT121 in FIG. 14, it proceeds to ACT122. In ACT122, the processor 101 waits for an operation to be performed on the user terminal 200. If the processor 101 receives a notification of the operation content from the user terminal 200, the processor 101 determines YES and proceeds to ACT123.

[0086] In ACT123, the processor 101 checks whether the operation was an operation for specifying a product. If the processor 101 cannot check the event, it judges NO, checks the content of the operation, and proceeds to other processing for performing processing according to the operation. As one of the other processing, the processor 101 checks that an operation for specifying the stop of scanning, such as tapping the button BUC, for example, has been performed, returns to ACT104 in FIG. 13, and returns the display screen of the touch panel 204 of the user terminal 200 to the first registration screen SCA. As the other processing, processing other than the above or multiple processing may be selectively performed, but detailed description thereof will be omitted here.

[0087] In addition, the operation of specifying the cancellation of scanning is not subject to notification from the user terminal 200, and the process of returning the display screen of the touch panel 204 on the user terminal 200 to the first registration screen SCA as described above may be executed autonomously by the processor 201 on the user terminal 200 after determining NO in ACT223 in Figure 8.

[0088] In transaction processing device 100, processor 101 is notified of barcode data as described above. If the barcode data represents a product code, processor 101 determines that an operation has been performed to specify a product and determines YES in ACT 123 in FIG. 14, and proceeds to ACT 124. As ACT124, the processor 101 determines a commodity to be traded based on the notified barcode data. That is, the processor 101, for example, extracts a commodity code included in the barcode data, and determines a commodity identified by the commodity code as a commodity to be traded (hereinafter referred to as a candidate commodity). The processor 101 may receive a notification from the user terminal 200 that a preset button displayed on the touch panel 204 has been tapped, and determine a commodity assigned to the preset button as a candidate commodity. The processor 101 may also receive a notification from the user terminal 200 of a commodity code that has been directly input on the touch panel 204 as a numeric string, and determine a commodity identified by the commodity code as a candidate commodity.

[0089] As ACT 125, the processor 101 instructs the user terminal 200 to display a registration confirmation screen. The registration confirmation screen is a screen for confirming whether or not to register the candidate product as a trading product. The processor 101 may include screen data representing the registration confirmation screen in instruction data for instructing the display of the registration confirmation screen, or may cause the processor 201 in the user terminal 200 to generate the registration confirmation screen including data of the candidate product. When the processor 201 in the user terminal 200 receives instruction data for instructing to display the registration confirmation screen, the processor 201 judges YES in ACT 228 in FIG. 8 and proceeds to ACT 230, where it updates the display screen of the touch panel 204 to the registration confirmation screen.

[0090] FIG. 17 is a diagram showing the registration confirmation screen SCC. The registration confirmation screen SCC is an example where the candidate product is named "AAAAA" and has a unit price of 300 yen. The registration confirmation screen SCC shows a display area ARC and buttons BUD, BUE, BUF, and BUG. The display area ARC shows the quantity inside. The button BUD is a soft key for receiving a designation to decrease the quantity. The button BUE is a soft key for receiving a designation to increase the quantity. The button BUF is a soft key for receiving a designation not to register as a trading product. The button BUG is a soft key for receiving a designation to register as a trading product.

[0091] After processor 101 in transaction equipment 100 issues an instruction to display the registration confirmation screen in ACT 125, the process proceeds to ACT 126 in FIG. In ACT126, the processor 101 waits for an operation to be performed on the user terminal 200. If the processor 101 receives a notification of the operation content from the user terminal 200, the processor 101 determines YES and proceeds to ACT127. In ACT 127, the processor 101 checks whether a change in quantity has been specified.

[0092] If the user wishes to change the quantity, the user specifies the quantity change by a predetermined operation such as tapping button BUD or button BUE. This operation is the subject of notification, and processor 201 in user terminal 200 judges YES, NO, YES respectively in ACT221, ACT222, ACT223 in FIG. 8, proceeds to ACT224, and notifies transaction equipment 100 that an operation specifying a quantity change has been performed.

[0093] After notifying the designation of the quantity change in ACT224, the processor 201 makes a NO or YES determination in ACT225 and ACT226, respectively, and proceeds to ACT232. In ACT 232, the processor 201 changes the quantity related to the candidate product code in accordance with the specification. Then, the processor 201 thereafter proceeds to a standby state in ACT228 and ACT229.

[0094] In response to the notification that an operation for specifying a quantity change has been performed, processor 101 in transaction equipment 100 determines YES in ACT 127 in FIG. 14 and proceeds to ACT 128. In ACT 128, the processor 101 changes the candidate product quantity in response to the specification. Then, the processor 101 returns to the standby state in ACT 126.

[0095] If the operation performed while the registration confirmation screen SCC is displayed is not a change in the quantity, the processor 101 judges NO in ACT127 and proceeds to ACT129. In ACT129, the processor 101 checks whether a designation has been made to register the candidate product as a trading product. If the processor 101 cannot check the relevant event, it judges NO, checks the contents of the operation, and proceeds to other processing to perform processing accordingly. As one of the other processing, the processor 101 checks that a predetermined operation has been performed to designate the cancellation of registration, such as tapping the button BUF, and returns to ACT121. As the other processing, processing other than the above or multiple processing may be selectively performed, but a detailed description of such processing will be omitted here.

[0096] When the user decides to register the candidate product displayed on registration confirmation screen SCC as the transaction product in the quantity displayed in display area ARC, the user specifies the registration by a predetermined operation such as tapping button BUG. This operation is the subject of notification, and processor 201 in user terminal 200 judges YES, NO, YES respectively in ACT221, ACT222, ACT223 in Fig. 8, proceeds to ACT224, and notifies transaction equipment 100 that the operation specifying registration has been performed.

[0097] After notifying the registration designation in ACT224, the processor 201 makes NO, NO and YES determinations in ACT225, ACT226 and ACT227, and proceeds to ACT233. In ACT 233, the processor 201 updates the product code list to include a field in which the product code currently set as the candidate product code and the quantity shown on the registration confirmation screen are set. In other words, the processor 201 adds a new field after the last field in the product code list data DAB, and sets the product code set as the candidate product code and the quantity in that field.

[0098] The product code list data including fields in which product codes and quantities are set is data that represents a list of product codes. And since the list of product codes is a list of products identified by product codes, it corresponds to a second list. In other words, the processor 201 executes information processing based on the user terminal program PRB, so that the computer with the processor 201 as its central part functions as a second creation means. Then, the processor 201 thereafter proceeds to a standby state in ACT228 and ACT229.

[0099] In response to the notification that an operation for specifying registration has been performed, processor 101 in transaction equipment 100 determines YES in ACT 129 in FIG. 14, and proceeds to ACT 130. In ACT130, the processor 101 registers the candidate commodity as a trading commodity in the quantity shown in the display area ARC. The processor 101 updates the transaction data DAA to include commodity data each representing the commodity code of the candidate commodity and the quantity shown in the display area ARC. Thus, the transaction data DAA represents a list of trading commodities, and the list corresponds to the first list.

[0100] In this way, processor 201 at user terminal 200 makes a request to transaction equipment 100 regarding product registration in response to an operation by a user. Then, processor 101 performs processing such as product registration in response to a notification of the operation from user terminal 200, and generates a product list. In other words, the notification of the operation from user terminal 200 is also a processing request to transaction equipment 100. Thus, processor 201 executes information processing based on user terminal program PRB, so that the computer having processor 201 as its central part functions as a requesting means. Also, processor 101 executes information processing based on transaction processing program PRA, so that the computer having processor 101 as its central part functions as a first creating means. Thereafter, the processor 101 returns to ACT104 in Fig. 13. That is, the processor 101 returns the display on the user terminal 200 to the first registration screen SCA in ACT104, and then repeats ACT105 and subsequent steps in the same manner as described above.

[0101] FIG. 18 is a diagram showing an example of the first registration screen SCA. The first registration screen SCA shown in FIG. 18 is an example in which one product each with the product names "AAAAA" and "BBBBB" and unit prices of 300 yen and 400 yen, respectively, have been registered. Therefore, the display area ARA shows a list of these trading products, and indicates that a total of two items have been registered with a reference price of 700 yen. The reference price is the amount calculated by subtracting discount amounts from various services such as coupon services from the total unit price of all trading products. If the transaction is settled without changing the trading products and the applied services, this reference price will be the payment amount.

[0102] As described above, if there is no problem in the exchange of data between transaction equipment 100 and user terminal 200, transaction products are registered while receiving user designation using user terminal 200 as a user interface terminal, and transaction data DAA showing a list of transaction products is created by transaction equipment 100. Note that transaction processing in this state is hereinafter referred to as normal processing.

[0103] Now, suppose that a communication error occurs in the exchange of request data related to the check-in request and instruction data for the response, and the exchange is not successful. In this case, the user terminal 200 continues to be in a state where no response is obtained for the check-in request in ACT 208 in Fig. 7. Then, when the predetermined waiting period for the check-in request in ACT 208 has ended, the processor 201 judges YES in ACT 210 and proceeds to ACT 241 in Fig. 9.

[0104] The processor 201 records the occurrence of the failure as ACT 241. That is, the processor 201 rewrites the failure flag set in the field FBA of the product code list data DAB to a set state, for example. As ACT242, the processor 201 displays a continuation confirmation screen on the touch panel 204. The continuation confirmation screen is a screen for notifying the user that the price of the transaction product cannot be displayed, and for confirming whether or not to continue using the smartphone POS service.

[0105] FIG. 19 is a diagram showing the continuation confirmation screen SCD. The continuation confirmation screen SCD displays a text message MEA and buttons BUH and BUI. The text message displays the information to the user as a string of characters. The button BUH is a soft key that allows the user to specify whether to continue using the smartphone POS service. The button BUI is a soft key that allows the user to specify whether to cancel using the smartphone POS service.

[0106] The user visually checks the continuation confirmation screen SCD and confirms the information, and if the user wishes to continue using the smartphone POS service, the user designates continuation by a predefined operation, such as tapping the button BUH. Alternatively, the user designates cancellation by a predefined operation, such as tapping the button BUI.

[0107] In ACT243 in Fig. 9, the processor 201 checks whether continuation of use of the smartphone POS service has been designated. If an operation specifying cancellation has been performed, the processor 201 determines NO, and returns to ACT201 in Fig. 7. If an operation specifying continuation has been performed, the processor 201 determines YES in ACT244, and proceeds to ACT243.

[0108] As ACT244, the processor 201 displays a second registration screen on the touch panel 204. The second registration screen includes a list of products already registered as trading products, and is a screen for allowing the user to recognize the registration status of the trading products. In other words, the second registration screen is a screen similar to the first registration screen SCA, but is generated by the processor 201 according to a predetermined form.

[0109] Fig. 20 is a diagram showing the second registration screen SCE. In Fig. 20, the same display elements as those in Fig. 15 are given the same reference numerals and detailed description thereof will be omitted.

[0110] The second registration screen SCE shown in Fig. 20 is an example of the case where the processor 201 has proceeded from ACT243 to ACT244 in Fig. 9, and does not show specific information about the traded product, but shows that the total points are 0. Also, since the second registration screen SCE is in a situation where the information about the traded product cannot be obtained, the reference price is shown as "￥X". Also, the second registration screen SCE shows a text message MEB to inform the user that the information about the traded product cannot be obtained.

[0111] In ACT 245, the processor 201 waits for some operation by the user. If some operation by the user is detected on the touch panel 204, the processor 201 judges the result as YES and proceeds to ACT 246.

[0112] In ACT246, processor 201 checks whether the performed operation needs to be notified to transaction equipment 100. If the performed operation is not a predetermined operation to be notified, processor 201 determines NO, checks the content of the operation, and proceeds to other processing for performing processing accordingly. As one of the other processing, processor 201 scrolls the first registration screen in response to a scroll operation, for example. As the other processing, there may be a processing other than the above, or multiple processings may be selectively performed, but a detailed description thereof will be omitted here.

[0113] On the other hand, if the performed operation is a predetermined operation to be notified, the processor 201 judges YES in ACT246 and proceeds to ACT247. In ACT 247, processor 201 retries the check-in request. That is, processor 201 transmits request data including the check-in data set in field FBA of product code list data DAB from wireless communication unit 206 to communication network 2, addressed to transaction processing device 100.

[0114] In ACT248, the processor 201 checks whether a response has been made to the check-in request. If the processor 201 cannot check the relevant event, it determines NO and proceeds to ACT249. In ACT249, the processor 201 checks whether a predetermined waiting period has ended regarding the check-in request in ACT247. If the processor 201 cannot check the event, it determines NO and returns to ACT248.

[0115] Thus, the processor 201 waits for a response to the check-in request until the waiting period ends in ACT248 and ACT249. Then, when the predetermined waiting period for the check-in request in ACT247 ends, the processor 201 judges YES in ACT249 and proceeds to ACT251 in FIG. The processor 201 records the occurrence of the failure as ACT 251. That is, the processor 201 rewrites the failure flag set in the field FBA of the product code list data DAB to a set state, for example.

[0116] In ACT252, the processor 201 checks whether the operation confirmed to have been performed in ACT245 in Fig. 9 was an operation to specify the start of a scan. If the processor 201 cannot confirm the event, it determines NO and proceeds to ACT253. In ACT253, the processor 201 checks whether the operation performed was an operation to specify a payment. If the processor 201 cannot check the relevant event, it judges NO, checks the content of the operation, and proceeds to other processing to perform the corresponding processing. As one of the other processing, the processor 201 scrolls the first registration screen in response to a scroll operation, for example. As the other processing, there may be other processing other than the above, or multiple processing may be selectively performed, but a detailed description of these will be omitted here.

[0117] The user searches the store for the product to be purchased, i.e., the product to be traded. If the user wants to register the product as a new transaction product, the user performs a predetermined operation to start scanning, such as tapping the button BUA on the second registration screen SCE. If the processor 201 confirms that the start of scanning has been designated by such an operation, it judges YES in ACT252 and proceeds to ACT254. As ACT254, the processor 201 displays the product scan screen SCB on the touch panel 204.

[0118] When the product scan screen SCB is displayed on the touch panel 204, the user operates the user terminal 200 so that the barcode displayed on the product to be registered as a transaction product is reflected in the display area ARB. The processor 201 analyzes the image obtained by the camera 205 and attempts to read the barcode.

[0119] After the processor 201 has finished instructing the display of the product scan screen in ACT254 in FIG. 10, the processor 201 proceeds to ACT255. In ACT 255, the processor 201 waits for an operation by the user. If the operation is performed, the processor 201 judges the result as YES and proceeds to ACT 256.

[0120] In ACT256, the processor 201 checks whether the operation was an operation for specifying a product. If the processor 201 cannot check the event, it judges NO, checks the content of the operation, and proceeds to other processing for performing processing according to the operation. As one of the other processing, the processor 201 checks that an operation for specifying the stop of scanning, such as tapping the button BUC, has been performed, and returns to ACT244 in FIG. 9, and returns the display screen of the touch panel 204 to the second registration screen SCE. As the other processing, processing other than the above or multiple processing may be selectively performed, but detailed explanations thereof will be omitted here.

[0121] The processor 201 can analyze the image obtained by the camera 205 as described above and read the barcode. If the barcode data represents a product code, it determines that an operation to specify a product has been performed and answers YES in ACT256, and proceeds to ACT257. In ACT257, processor 201 updates the display screen of touch panel 204 to a registration confirmation screen. The registration confirmation screen displayed here may be the same as registration confirmation screen SCC shown in Fig. 17. However, processor 201 generates the registration confirmation screen according to a predetermined form, without depending on instructions from transaction processing device 100. In addition, processor 201 displays the product code included in the barcode data in place of the product name shown in Fig. 17 on the registration confirmation screen displayed here, and sets the amount to "￥X". The user performs the same operations as when the registration confirmation screen SCC shown in FIG. 17 is displayed to specify a quantity change or to specify registration.

[0122] 10, the processor 201 waits for an operation to be performed by the user. If the processor 201 can confirm that an operation has been performed, it judges the result as YES and proceeds to ACT 259. In ACT259, the processor 201 checks whether a quantity change has been specified. If a quantity change has been specified, the processor 201 determines YES in ACT259 and proceeds to ACT260. In ACT 260, the processor 201 changes the candidate product quantity in response to the specification. Then, the processor 201 returns to the standby state in ACT 258.

[0123] If the operation performed while the registration confirmation screen is displayed does not specify a change in the quantity, the processor 201 determines NO in ACT259 and proceeds to ACT261. In ACT261, the processor 201 checks whether a designation has been made to register the candidate product as a trading product. If the processor 201 cannot confirm the relevant event, it judges NO, checks the contents of the operation, and proceeds to other processing to perform processing accordingly. As one of the other processing, the processor 201 checks that a predetermined operation has been performed to designate the cancellation of registration, such as tapping the button BUF, and returns to ACT254. As the other processing, processing other than the above or multiple processing may be selectively performed, but a detailed description of such processing will be omitted here.

[0124] If the user decides to register the candidate product displayed on the registration confirmation screen as the trading product in the quantity displayed on the registration confirmation screen, the user specifies the registration by a predetermined operation. If such an operation is confirmed, the processor 201 judges YES in ACT261 and proceeds to ACT262.

[0125] In ACT 262, the processor 201 updates the product code list to include a field in which the product code currently set as the candidate product code and the quantity shown on the registration confirmation screen are set. In other words, the processor 201 adds a new field after the last field of the product code list data DAB, and sets the candidate product code and the quantity in that field. Thereafter, the processor 201 repeats the process from ACT244 in Fig. 9 onwards in the same manner as described above. However, in ACT244, the processor 201 displays the second registration screen SCE that reflects the registration results of the transaction product according to the product code list updated in ACT262 in Fig. 10.

[0126] FIG. 21 is a diagram showing the second registration screen SCE. The second registration screen SCE shown in FIG. 21 is an example of a state in which check-in is not yet completed and registration requests for two trading products are recorded. The second registration screen SCE shown in FIG. 21 is an example when one product each with product codes "49 xxxxxxxxxxx0" and "49 xxxxxxxxxxx1" has already been registered. However, in FIG. 21, some of the numbers in the product codes have been replaced with "x". Therefore, the display area ARA shows a list of the product codes of these trading products, and indicates that a total of two items have been registered. Note that the second registration screen SCE shown in FIG. 21 shows the price of each product as "￥XXX" as it is unknown, and also shows the suggested price as "￥X".

[0127] In this manner, the user can continue to register the transaction item even in a situation where check-in is not yet complete. In this situation, data exchange between transaction equipment 100 and user terminal 200 may return to normal. In this case, when processor 201 requests check-in in ACT247 in Fig. 9, processor 101 in transaction equipment 100 instructs display of the first registration screen or the unavailable screen as described above. If an instruction to display the first registration screen is given, processor 201 determines YES in ACT248 in Fig. 9 as a response, and proceeds to ACT271 in Fig. 11.

[0128] In ACT271, the processor 201 checks whether a product code list is present. If the product code list data DAB does not include a field FBC, the processor 201 determines that the result is NO, and returns to ACT211 in Fig. 7. If the product code list data DAB includes a field FBC, the processor 201 determines that a recorded product code list is present, and proceeds to ACT272.

[0129] As ACT 272, processor 201 notifies transaction processing device 100 of the product code list. Processor 201, for example, transmits notification data including product code list data DAB from wireless communication unit 206 to communication network 2, addressed to transaction processing device 100. Processor 201 may also transmit notification data including each field subsequent to field FBC of product code list data DAB.

[0130] In transaction equipment 100, when processor 101 is notified by communication unit 104 that notification data for notifying the product code list has been received, processor 101 judges YES in ACT 106 in FIG. 13 and proceeds to ACT 110. In ACT110, the processor 101 updates the transaction data DAA according to the notified product code list. That is, the processor 101 rewrites the transaction data DAA, for example, so as to eliminate the difference between the list of transaction products represented by the transaction data DAA and the list of products represented by the notified product code list. The processor 101 then instructs in ACT104 to display the first registration screen SCA based on the updated transaction data DAA, and returns to the standby state in ACT105 and ACT106.

[0131] After the processor 201 in the user terminal 200 notifies the user of the product code list in ACT272 in FIG. In ACT273, processor 201 checks whether a display instruction has been issued from transaction equipment 100. If processor 201 cannot check the relevant event, it determines NO and proceeds to ACT274.

[0132] In ACT274, the processor 201 checks whether a predetermined waiting period has elapsed regarding the notification of the product code list in ACT272. If the processor 201 cannot check the event, it determines NO and returns to ACT273. Thus, in ACT273 and ACT274, the processor 201 waits for a display instruction to be made in response to the notification in ACT272 until the waiting period ends.

[0133] If the predetermined waiting period for the notification of the request history in ACT272 has ended, the processor 201 determines YES in ACT274 and proceeds to ACT275. As ACT 275, processor 201 executes local processing for autonomously performing processing in response to an operation by a user without depending on instructions from transaction equipment 100. This local processing is, for example, similar to the processing shown in FIG.

[0134] As a result, if a product code has been added to product code list data DAB before check-in is completed, processor 201 attempts to notify the product code list represented by that product code list data DAB. If processor 201 cannot confirm that the notification has been accepted by transaction equipment 100, even after check-in, it continues updating the product code list while autonomously performing processing for registering the transacted product in response to the user's operation. Processor 201 attempts to notify the product code list every time an operation that requires notification to transaction equipment 100 is performed.

[0135] On the other hand, if the instruction data transmitted by processor 101 in transaction processing device 100 by executing the processing as described above in response to the notification of the product code list in ACT272 in Figure 11 is received by wireless communication unit 206, processor 201 judges YES in ACT273 and proceeds to ACT276.

[0136] In ACT276, the processor 201 updates the display screen on the touch panel 204 in response to the instruction. That is, the processor 201 updates the display screen on the touch panel 204 to the first registration screen SCA, which shows the registration status of the transaction product updated based on the product code list. Thus, the user can then register the transaction product while referring to the first registration screen SCA. At this time, if the instruction data for instructing the display of the first registration screen contains a transaction code and a check-in code is set in field FBA of the product code list data DAB, the processor 201 rewrites the check-in code to the transaction code contained in the instruction data. Then, the processor 201 thereafter returns to the standby state of ACT 221 in FIG. Thus, processor 201 returns to normal processing operation in response to the fact that the notification of the product code list has been accepted by transaction processing apparatus 100 and thus the instruction to display has been received.

[0137] FIG. 22 is a diagram showing the first registration screen SCA. The first registration screen SCA shown in Fig. 22 is an example in which one product with the product name "CCCCC" and a unit price of 700 yen is registered as a transaction product while the second registration screen SCE shown in Fig. 21 is displayed. The first registration screen SCA shown in Fig. 22 is an example in which products with product codes "49xxxxxxxxxx0" and "49xxxxxxxxxx1" have product names "AAAAA" and "BBBBB" and unit prices of 300 yen and 400 yen, respectively.

[0138] Now, in a situation where transaction equipment 100 and user terminal 200 are performing normal processing, a failure may occur in communication between transaction equipment 100 and user terminal 200, making it impossible to continue the normal processing. In such a case, when the processor 201 is in the standby state in ACT228 and ACT229 in Fig. 8, the standby period ends without receiving a display instruction. Therefore, in this case, the processor 201 judges YES in ACT229 and proceeds to ACT277 in Fig. 11. In addition, if the processor 201 judges YES in ACT229 in FIG. 8, it may perform processing similar to ACT242 and ACT243 in FIG. 9, and if it judges YES in the processing corresponding to ACT243, it may proceed to ACT277 in FIG. 11.

[0139] The processor 201 records the occurrence of the failure in ACT 277. That is, the processor 201 rewrites the failure flag set in the field FBA of the product code list data DAB to a set state, for example. In ACT 278, the processor 201 waits for some operation by the user. If some operation by the user is detected on the touch panel 204, the processor 201 judges the result as YES and proceeds to ACT 279.

[0140] As ACT 279, processor 201 executes local processing for autonomously performing processing in response to an operation by a user without depending on instructions from transaction equipment 100. This local processing is, for example, processing similar to the processing shown in FIG. As ACT280 in FIG. 11, processor 201 notifies transaction equipment 100 of the product code list in the same manner as, for example, ACT272. When processor 101 in transaction processing device 100 is notified by communication unit 104 that it has received notification data for notifying the product code list, processor 101 updates transaction data DAA in ACT110 in FIG. 13 as described above, and then instructs display of the first registration screen SCA in ACT104.

[0141] After the processor 201 in the user terminal 200 notifies the request history in ACT280 in FIG. In ACT281, processor 201 checks whether a display instruction has been issued from transaction equipment 100. If processor 201 cannot check the relevant event, it determines NO and proceeds to ACT282. In ACT282, the processor 201 checks whether a predetermined waiting period has elapsed regarding the notification of the product code list in ACT280. If the processor 201 cannot check the event, it determines NO and returns to ACT281. Thus, in ACT281 and ACT282, the processor 201 waits for a display instruction to be made in response to the notification in ACT280 until the waiting period ends.

[0142] If the failure continues and the waiting period ends without the instruction data sent by transaction processing device 100 to instruct the screen display being received by wireless communication unit 206, processor 201 judges YES in ACT282 and proceeds to ACT283. In ACT283, the processor 201 displays the second registration screen on the touch panel 204. The processor 201 generates the second registration screen by editing the first registration screen SCA that was displayed during the standby state of ACT228 and ACT229, for example. Then, the processor 201 returns to the standby state of ACT278.

[0143] FIG. 23 is a diagram showing the second registration screen SCE. The second registration screen SCE shown in Fig. 23 is an example in which two products with product code "49xxxxxxxxxx2" are registered as trading products when the first registration screen SCA shown in Fig. 22 is displayed. The second registration screen SCE shown in Fig. 23 shows the information shown on the first registration screen SCA shown in Fig. 22 as is, but adds information on the product with product code "49xxxxxxxxxx2". However, in Fig. 23, some of the numbers in the product codes are replaced with "x".

[0144] When the failure is restored and instruction data transmitted by transaction equipment 100 to instruct screen display is received by wireless communication unit 206, processor 201 determines YES in ACT281 in FIG. 8 and proceeds to ACT284. In ACT284, the processor 201 updates the display screen on the touch panel 204 in response to the instruction. That is, the processor 201 updates the display screen on the touch panel 204 to the first registration screen SCA showing the registration status of the transaction product updated based on the product code list. Then, the processor 201 returns to the standby state of ACT221 in FIG. 8. Thus, processor 201 returns to normal processing operation in response to the fact that the notification of the product code list has been accepted by transaction processing apparatus 100 and thus the instruction to display has been received.

[0145] When the user has finished registering all the trading products related to the current transaction, he / she designates the start of accounting by a predetermined operation, such as tapping a button BUB on the first registration screen SCA or the second registration screen SCE. When such an instruction to start accounting is given, the processor 201 judges YES in ACT222 in Fig. 8, ACT253 in Fig. 10, processing equivalent to ACT253 in Fig. 10 within ACT275 in Fig. 11, or processing equivalent to ACT253 in Fig. 10 within ACT279 in Fig. 11, and in either case proceeds to ACT291 in Fig. 12.

[0146] In ACT291, the processor 201 checks whether or not there has been a failure during the registration of the traded product. If the failure flag in the field FBB in the product code list data DAB is reset, for example, the processor 201 determines that there has been no failure and proceeds to ACT292. In ACT292, the processor 201 checks whether smartphone payment is permitted. "Smartphone payment" is a process for settling the payment amount by operation on the user terminal 200 using an online payment service. Smartphone payment means, for example, a payment in which credit card information, financial institution account information, prepaid card information, etc. are linked to the user's user terminal 200 in advance, and the payment amount is set by the user's operation on the user terminal 200. As the smartphone payment process in the user terminal 200, existing processes can be used as they are. For example, the processor 201 refers to settings, for example, appropriately determined by the user as settings related to the use of the smartphone POS service, to determine whether smartphone payment is permitted. If it is confirmed that smartphone payment is permitted, the processor 201 judges YES and proceeds to ACT293.

[0147] As ACT293, processor 201 displays a first selection screen on touch panel 204. The first selection screen is a screen for allowing the user to specify whether to perform smartphone payment or accounting device payment. For example, the first selection screen displays the total number of items transacted and the payment amount as character strings, as well as soft keys for specifying smartphone payment and accounting device payment.

[0148] On the other hand, if the processor 201 cannot confirm that smartphone payment is permitted, it judges NO in ACT292 and proceeds to ACT294. As ACT294, the processor 201 displays a second selection screen on the touch panel 204. The second selection screen is a screen for allowing the user to specify payment via checkout device. For example, the second selection screen is a screen modified from the first selection screen so that the softkey for specifying smartphone payment is not displayed, or the softkey is disabled by being grayed out.

[0149] Upon completing ACT293 or ACT294, the processor 201 proceeds to ACT295 in either case. As ACT295, the processor 201 waits for an operation to be performed to specify either smartphone payment or accounting device payment. When the first selection screen is displayed, the user designates smartphone payment or checkout device payment by a predetermined operation such as tapping a soft key displayed on the first selection screen. When the second selection screen is displayed, the user designates checkout device payment by a predetermined operation such as tapping a soft key displayed on the second selection screen.

[0150] If these operations are performed, the processor 201 judges YES in ACT295 and proceeds to ACT296. In ACT296, the processor 201 checks whether smartphone payment has been designated. If the processor 201 checks that smartphone payment has been designated, the result is YES and the process proceeds to ACT297.

[0151] As ACT297, the processor 201 executes smartphone payment processing. The smartphone payment processing is processing for settling the payment amount by operation on the user terminal 200 using an online payment service. As the smartphone payment processing, existing processing can be used as is. Then, when the processor 201 finishes the smartphone payment processing, it returns to ACT201 in FIG. 7.

[0152] If accounting device payment is specified, the processor 201 determines NO in ACT296 and proceeds to ACT298. In ACT 298, processor 201 notifies transaction processing device 100 that a transaction has been designated.

[0153] When the operation for specifying the transaction is thus notified from user terminal 200 to transaction equipment 100, processor 101 determines YES in ACT108 in FIG. 13, and proceeds to ACT111. As ACT111, the processor 101 instructs the user terminal 200 to display a first takeover screen. The first takeover screen is a screen for taking over the function as a user interface terminal related to the transaction being processed from the user terminal 200 to the accounting device 700.

[0154] After notifying the user of the accounting specification in ACT298 in FIG. 12, the processor 201 in the user terminal 200 proceeds to ACT299. In ACT 299, processor 201 checks whether a display instruction has been issued from transaction equipment 100. If processor 201 cannot check the relevant event, it determines NO and proceeds to ACT 300.

[0155] In ACT 300, the processor 201 checks whether any operation has been performed. If the processor 201 cannot check the relevant event, it determines NO and returns to ACT 299. Thus, in ACT299 and ACT300, the processor 201 waits for a display instruction or operation. If any operation is performed, the processor 201 judges YES in ACT300, confirms the operation, and proceeds to other processing to perform the corresponding processing. As one of the other processes, the processor 201, for example, confirms that the operation is to cancel the transaction, and returns the user terminal 200 to the state it was in before proceeding to ACT291. As the other process, a process other than the above, or multiple processes may be selectively performed, but a detailed explanation of these will be omitted here.

[0156] In response to receiving the instruction data for instructing to display the first transition screen, the processor 201 determines YES in ACT299 and proceeds to ACT301. In ACT 301, the processor 201 causes the touch panel 204 to display a first transition screen.

[0157] FIG. 24 is a diagram showing the first takeover screen SCF. 24 is an example of a first takeover screen SCF for taking over a transaction involving a total of three items with a reference price of 1,400 yen to the accounting device 700, and displays the total number of items and the reference price of the transaction by character strings. The first takeover screen SCF also displays a two-dimensional code COA and a button BUJ. The button BUJ is a soft key that allows the user to cancel the transaction and return to registering the transaction items. In addition, in transaction processing device 100, processor 101 generates a two-dimensional code COA as representing the first handover data for accounting device 700 to request accounting data based on transaction data DAA from transaction processing device 100, and includes it in the first handover screen SCF.

[0158] Now, when the processor 201 receives notification of the accounting designation and proceeds to ACT 291 in FIG. 12, if the fault flag set in field FBB of the product code list data DAB, for example, is set, the processor 201 judges that there is a fault and determines YES, and proceeds to ACT 302. In ACT 302, the processor 201 displays a second takeover screen on the touch panel 204. The second takeover screen is a screen for taking over the accounting related to the transaction being processed using the user terminal 200 to the accounting device 700.

[0159] The second takeover screen may be the same as the first takeover screen SCF shown in Fig. 24. However, if the processor 201 proceeds to ACT291 in response to a designation of starting checkout while the second registration screen SCE is displayed, the processor 201 displays the reference price as "￥X" on the second takeover screen. The processor 201 also generates a two-dimensional code as a representation of the second takeover data including the product code list data DAB, and includes it in the second takeover screen. The processor 201 may also generate a two-dimensional code as a representation of the second takeover data including each field after field FBC of the product code list data DAB, and include it in the second takeover screen.

[0160] Thus, the processor 201 outputs the product code list represented by the product code list data DAB in an optically readable manner by displaying the second transition screen. Thus, the processor 201 executes information processing based on the user terminal program PRB, and the computer having the processor 201 as its central part functions as an output means.

[0161] Upon completing ACT 301 or ACT 302, the processor 201 proceeds to ACT 303 in either case. In ACT 303, processor 201 checks whether a display instruction has been issued from transaction equipment 100. If processor 201 cannot check the relevant event, it determines NO and proceeds to ACT 304. In ACT 304, the processor 201 checks whether any operation has been performed. If the processor 201 cannot check the relevant event, it determines NO and returns to ACT 303.

[0162] Thus, the processor 201 waits for a display instruction or operation in ACT303 and ACT304. If any operation is performed, the processor 201 judges YES in ACT304, checks the operation content, and proceeds to other processing to perform processing accordingly. As one of the other processing, the processor 101, for example, checks that the button BUI has been tapped, and returns the user terminal 200 to the state before proceeding to ACT291. As the other processing, a processing other than the above or multiple processing may be selectively performed, but a detailed description thereof will be omitted here.

[0163] Now, if there are multiple accounting devices 700 installed, the user arbitrarily selects an accounting device 700 that is in standby mode from among them, and has the barcode scanner 705 equipped on that accounting device 700 read the two-dimensional code displayed on the first transition screen or the second transition screen. In the accounting device 700, a processor 701 executes accounting processing based on an accounting processing program PRC.

[0164] FIG. 25 is a flowchart of the accounting process. The processor 701 as ACT 701 displays a standby screen on the touch panel 704. The standby screen is a screen for informing the user that the device is available for transaction. The standby screen may be determined as appropriate by, for example, the designer or administrator of the transaction device 700. It is envisioned that the standby screen will include an image that informs the user to have the barcode scanner 705 read the two-dimensional code displayed on the user terminal 200 or cart terminal 300.

[0165] In ACT 702, the processor 701 waits for some operation to be performed. If the user operates the barcode scanner 705 to read the two-dimensional code displayed on the first takeover screen or the second takeover screen as described above, the processor 701 judges YES and proceeds to ACT 703.

[0166] In ACT 703, the processor 701 checks whether the operation is a designation for handing over the accounting for a transaction being processed using the user terminal 200 or the cart terminal 300. If the processor 701 cannot confirm the relevant event, it judges NO, checks the content of the operation, and proceeds to other processing to perform the corresponding processing. A detailed explanation of the other processing will be omitted here.

[0167] As described above, in order to start a transaction at the transaction device 700, the user has the barcode scanner 705 read the two-dimensional code displayed on the first or second takeover screen. In other words, having the barcode scanner 705 read the two-dimensional code displayed on the first or second takeover screen is an example of an operation for specifying a transaction takeover. When the corresponding operation is performed and the barcode scanner 705 reads the two-dimensional code displayed on the first or second takeover screen, the processor 701 determines YES in ACT 703 and proceeds to ACT 704.

[0168] In ACT 704, the processor 701 confirms whether the data represented by the two-dimensional code read by the barcode scanner 705 is the first handover data. If the processor 701 confirms that the data is the first handover data, it judges that the result is YES and proceeds to ACT 705. As ACT 705, processor 701 acquires accounting data from transaction equipment 100. That is, processor 701 requests the accounting data from transaction equipment 100, for example, based on the first handover data represented by the two-dimensional code read as described above. Then, processor 701 acquires the accounting data transmitted from transaction equipment 100 in response to this request.

[0169] In transaction processing apparatus 100, processor 101 instructs display of the first transition screen in ACT111 in FIG. 13, and then proceeds to ACT112. In ACT 112, the processor 101 waits for a request for accounting data. If a request based on the first takeover data represented by the two-dimensional code included in the first takeover screen instructed to be displayed in ACT 111 is made from the accounting device 700 as described above, the processor 101 judges the result as YES and proceeds to ACT 113.

[0170] As ACT 113, processor 101 causes communication unit 104 to send predetermined accounting data for billing and settlement of products related to the product data set in each field after field FAD of transaction data DAA to the requesting accounting device 700. For example, processor 101 may use transaction data DAA as is as accounting data, or may generate accounting data by omitting part of the information included in transaction data DAA or by adding information not included in transaction data DAA.

[0171] As ACT114, the processor 101 instructs the user terminal 200 to display a completion screen. The completion screen is a screen that guides the user to operate the accounting device 700 to complete the payment, since the handover to the accounting device 700 has been completed. The processor 101 then ends the transaction processing.

[0172] In response to receiving instruction data for instructing to display the completion screen, the processor 201 in the user terminal 200 judges YES in ACT 303 in FIG. 12 and proceeds to ACT 305. In ACT 305, the processor 201 displays a completion screen on the touch panel 204. Then, in response to a predetermined confirmation operation being performed, the processor 201 returns to ACT 201 in FIG.

[0173] In ACT 705 in FIG. 25, when the accounting data sent from transaction processing device 100 as described above is received by communication unit 711, processor 701 in accounting device 700 acquires the data. As ACT 706, the processor 701 performs accounting processing based on the acquired accounting data. That is, the processor 701 determines the settlement amount for the corresponding transaction based on the acquired accounting data. This accounting processing may be the same processing as that performed by another existing accounting device of the same type, for example.

[0174] The processor 701 as the ACT 707 performs a payment process to settle the payment amount determined as described above. The payment process may be performed as is well known, using a payment method that is supported by the accounting device 700 and that is permitted for use by the accounting device 700, among various payment methods such as credit card payment, electronic money payment, code payment, prepaid payment, point payment, gift certificate payment, or cash payment. During this payment process, the processor 701 may also appropriately perform processes such as issuing various vouchers such as receipts, invoices, and coupons using the print unit 710, and requesting the electronic receipt server to record the transaction results. Then, the processor 701 thereafter returns to the standby state of ACT 702 via ACT 701 .

[0175] On the other hand, if the processor 201 cannot confirm that the two-dimensional code read by the barcode scanner 705 represents the first handover data, that is, if it represents the second handover data, it judges NO in ACT 704 and proceeds to ACT 708. In ACT 708, the processor 701 checks whether the data set in the field FBA of the product code list data DAB included in the second handover data is a transaction code. If the processor 701 checks that the data is a transaction code, it determines YES and proceeds to ACT 709.

[0176] In ACT709, processor 701 acquires accounting data from transaction processing device 100. In other words, if transaction data is set in field FBA of product code list data DAB included in the second handover data, it is possible that at least check-in has been completed for the transaction that is the subject of the transaction, and transaction data DAA including product data is held in transaction processing device 100. Processor 701 then attempts to acquire accounting data corresponding to such transaction data DAA. The specific processing of processor 701 in this ACT709 may be similar to that in ACT705.

[0177] After completing ACT709, processor 701 proceeds to ACT710. If processor 701 cannot confirm that the value set in field FBA of product code list data DAB included in the second handover data is a transaction code, it determines NO in ACT708, passes ACT709, and proceeds to ACT710. In other words, if the value set in field FBA of product code list data DAB included in the second handover data is not a transaction code and check-in for the transaction to be transacted has not been completed, processor 701 does not perform ACT709 because transaction data DAA has not been created in transaction processing device 100.

[0178] As ACT710, processor 701 acquires product data relating to a product code set in field FBC and subsequent fields of product code list data DAB included in the second handover data. The product data includes at least a product name and a unit price. The product data may also include various other information such as information regarding discounts. At this time, processor 701 is assumed to acquire the product data from a product database managed by a POS server included in in-store POS 600, for example. However, processor 701 may also inquire of transaction processing device 100, for example, and acquire the product data from a product database managed by transaction processing device 100. Alternatively, processor 701 may acquire the product data from a product database managed by in-company server 400 or an in-store Web client.

[0179] In ACT 711, the processor 701 creates a product list related to the transaction products in the transaction that is the subject of the transaction. That is, the processor 701 creates a product list based on the product data acquired in ACT 710 and the quantities set together with the product codes in fields FBC and after in the product code list data DAB, for example. Then, if the processor 701 has acquired accounting data in ACT 709, for example, it updates the created product list so as to eliminate any differences between the product list represented by the accounting data and the created product list.

[0180] As ACT712, the processor 701 performs accounting processing for the product list created in ACT711. That is, the processor 701 determines the settlement amount for the traded products included in the product list created in ACT711. This accounting processing may be similar to processing performed in another existing accounting device of the same type, for example. Thus, the processor 701 executes information processing based on the accounting processing program PRC, and the computer with the processor 701 as its central part functions as a determination means.

[0181] As ACT713, the processor 701 performs a payment process to settle the payment amount determined as described above. The payment process may be performed as is well known, using a payment method that is supported by the accounting device 700 and that is permitted to be used by the accounting device 700, among various payment methods such as credit card payment, electronic money payment, code payment, prepaid payment, point payment, gift certificate payment, or cash payment. In addition, during this payment process, the processor 701 may appropriately perform processes such as issuing various vouchers such as receipts, receipts, and coupons using the print unit 710, and requesting the electronic receipt server to record the transaction results. Then, the processor 701 returns to the standby state of ACT702 via ACT701. Thus, the processor 701 executes information processing based on the accounting processing program PRC, and the computer with the processor 701 as the core part functions as a payment means.

[0182] As described above, when transaction processing device 100 and user terminal 200 can normally exchange data, transaction processing device 100 creates a product list related to the transaction product while receiving user operation using user terminal 200 as a user interface terminal. Then, transaction processing system 1 creates a list of product codes acquired for specifying the transaction product in user terminal 200 in parallel with the creation of the product list in transaction processing device 100. When transaction processing device 100 and user terminal 200 cannot normally exchange data and user terminal 200 cannot confirm that processing in transaction processing device 100 has been completed in response to the user's operation, transaction processing system 1 continues updating the list of product codes in response to the user's operation in user terminal 200. Then, in transaction processing system 1, accounting device 700 determines the payment amount according to the product list created by transaction processing device 100 and the product code list created by user terminal 200, and settles the payment amount. Therefore, even if a situation occurs in which user terminal 200 cannot cooperate with transaction processing device 100, the user can complete the transaction.

[0183] Furthermore, when any notification to transaction equipment 100 becomes necessary, user terminal 200 notifies transaction equipment 100 of the created product code list along with the notification. As a result, if transaction equipment 100 and user terminal 200 have returned to a state in which data can be normally exchanged, transaction equipment 100 can modify the product list in accordance with the product code list created by user terminal 200, and can transition to a normal processing state.

[0184] The user terminal 200 also outputs the product code list by displaying a two-dimensional code representing the second handover data including the product code list. The accounting device 700 then obtains the two-dimensional code by reading it with a barcode scanner 705. This eliminates the need to provide a special device for notifying the accounting device 700 of the product code list from the user terminal 200.

[0185] This embodiment can be modified in various ways as follows. If the check-in cannot be completed, the user terminal 200 may be configured not to accept any operation for registering the traded product.

[0186] Notification of the product code list from user terminal 200 to transaction equipment 100 may be made when a predetermined amount of time has elapsed since the previous notification of the product code list, instead of or in addition to a time when another notification should be made. Furthermore, notification of the product code list from user terminal 200 to transaction equipment 100 may be made when a predetermined operation specifying notification is performed by the user, instead of or in addition to either or both of the above.

[0187] Notification of the product code list from user terminal 200 to transaction equipment 100 may be performed only when a transaction is specified.

[0188] Notification of the product code list from user terminal 200 to transaction equipment 100 may be performed using a means other than the two-dimensional code, such as near-field wireless communication.

[0189] Each function realized by information processing in various devices can be realized in part or in whole by hardware that executes information processing not based on a program, such as a logic circuit, etc. Also, each of the above functions can be realized by combining the above hardware, such as the logic circuit, with software control.

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

[0191] 1...transaction processing system, 2...communication network, 100...transaction processing device, 200...user terminal, 300...cart terminal, 400...corporate server, 500...in-store web client, 700...accounting device, 600...in-store POS, 800...employee terminal, 101,201,701...processor, 102,202,702...main memory unit, 103,203,703...auxiliary memory unit, 104,711...communication unit, 204,704...touch panel, 205...camera, 206...wireless communication unit, 705...barcode scanner, 706...credit card reader, 707...proximity communication unit, 708...card reader / writer, 709...change unit, 710...print unit.

Claims

1. The system includes a transaction processing device, a mobile terminal, and an accounting device, a first creating means provided in the transaction processing device for creating a first list of products to be the subject of a transaction; a request means provided in the mobile terminal for requesting the first creating means to update the first list in response to an operation on the mobile terminal; a second creation means provided in the mobile terminal and configured to create a second list of the products to be traded in response to an operation on the mobile terminal; an output means provided in the mobile terminal and outputting the second list created by the second creation means; a determination means provided in the accounting device for determining an amount to be settled based on the first list created by the first creation means and the second list output by the output means; a payment means provided in the accounting device for paying the amount determined by the determination means; A transaction processing system comprising:

2. the first creation means creates the first list as a list including identifiers, names, and prices of products; the second creation means creates the second list as a list including identifiers of products but not including names and prices; 2. The transaction processing system of claim 1.

3. A mobile terminal; a transaction processing device including a first creating means for creating a first list of products to be the subject of a transaction; an accounting device comprising: a determination means for determining an amount to be paid based on the first list created by the first creation means and the second list output from the mobile terminal; and a payment means for paying the amount determined by the determination means; A terminal device used as the mobile terminal in a transaction processing system including: a requesting means for requesting the creating means to update the first list in response to an operation on the terminal device; a second creation means for creating a second list of the products to be traded in response to an operation on the terminal device; an output means for outputting the second list created by the second creation means so that the accounting device can acquire the second list; A terminal device equipped with the above.

4. the output means displays a screen on which the second list is optically readable. The terminal device according to claim 3.

5. a transaction processing device including a first creating means for creating a first list of products to be the subject of a transaction; a mobile terminal comprising: a request means for requesting the first creation means to update the list in response to an operation; a second creation means for creating a second list of products to be traded in response to the operation; and an output means for outputting the second list created by the second creation means; Together they make up a transaction processing system. a determination means for determining an amount to be paid based on the first list created by the first creation means and the second list output by the output means; a payment means for paying the amount determined by the determination means; An accounting device equipped with the above.

6. A mobile terminal; a transaction processing device including a first creating means for creating a first list of products to be the subject of a transaction; an accounting device comprising: a determination means for determining an amount to be paid based on the first list created by the first creation means and the second list output from the mobile terminal; and a payment means for paying the amount determined by the determination means; A computer that controls a terminal device used as the mobile terminal in a transaction processing system including: a requesting means for requesting the creating means to update the first list in response to an operation on the terminal device; a second creation means for creating a second list of the products to be traded in response to an operation on the terminal device; an output means for outputting the second list created by the second creation means so that the accounting device can acquire the second list; An information processing program that functions as a

7. a transaction processing device including a first creating means for creating a first list of products to be the subject of a transaction; a mobile terminal comprising: a request means for requesting the first creation means to update the list in response to an operation; a second creation means for creating a second list of products to be traded in response to the operation; and an output means for outputting the second list created by the second creation means; A computer that controls accounting devices that together constitute a transaction processing system, a determination means for determining an amount to be paid based on the first list created by the first creation means and the second list output by the output means; a payment means for paying the amount determined by the determination means; An information processing program that enables the system to function as such.

Images