Information processing equipment and server equipment

Abstract

To provide an information processing apparatus and a server device that enable training based on actual environment of a store.SOLUTION: An information processing apparatus which is operated by a user in a store and movable in the store includes: registration means which registers commodities designated by the user through their operation; acquisition means which acquires specification information that can specify an object reloaded with electronic money by the user; switching means which selects one of first mode for executing check-out of the registered commodities or second mode for simulating the execution of check-out of the registered commodities in accordance with operation of the user; and output control means which outputs, when receiving an operation to start check-out from the user, the specification information in both first and second modes, to enable a check-out machine which receives the specification information to execute check-out using the electronic money.SELECTED DRAWING: Figure 27

Description

Technical Field

[0001] Embodiments of the present invention relate to an information processing apparatus and a server apparatus.

Background Art

[0002] In a storefront where products are displayed, when a customer shops, there is a known system in which the customer operates a mobile terminal such as a smartphone or a tablet terminal by themselves and inputs (also referred to as registration) data related to the product to be purchased. Also, in a store, an accounting device for accounting for products input by a mobile terminal may be provided.

[0003] In addition, some stores also provide a prepaid payment service as one of the payment methods. In such stores, for example, by holding a prepaid account in a card medium such as a membership card issued by the store, charging and payment of electronic money are also carried out using the card medium. Also, by linking the prepaid account to a mobile terminal, it is possible to check the balance on the mobile terminal or output information necessary for prepaid payment to the accounting device.

[0004] By the way, in a store, training for employees may be carried out for training or the like. For example, conventionally, a technique has been proposed that enables training to be conducted by assuming that payment has been made with the card medium even if the card medium is not at hand.

[0005] However, the conventional technology targets a single accounting device (payment device), and no consideration is given to the cooperation between the mobile terminal related to prepaid payment and the accounting device. Therefore, with the conventional technology, it may not be possible to conduct training that conforms to the actual environment.

Summary of the Invention

Problems to be Solved by the Invention

[0006] The problem that the embodiments of the present invention aim to solve is to provide an information processing device and a server device that can perform training tailored to the actual environment of a store. [Means for solving the problem]

[0007] The information processing device of the embodiment is a movable information processing device operated by a user within a store, and comprises a registration means, an acquisition means, a switching means, and an output control means. The registration means registers products specified by the user's operation. The acquisition means acquires specific information that can identify the destination of the electronic money charged by the user. The switching means switches to either a first mode for executing the accounting of the registered products or a second mode for simulating the accounting of the registered products, in response to the user's operation. When the output control means receives an operation from the user to start accounting, it outputs the specific information in either the first mode or the second mode, thereby enabling the accounting device that receives the specific information to perform accounting using the electronic money. [Brief explanation of the drawing]

[0008] [Figure 1] Figure 1 is a diagram showing the schematic configuration of a transaction processing system according to an embodiment. [Figure 2] Figure 2 shows an example of the hardware configuration of a server device according to this embodiment. [Figure 3] Figure 3 shows an example of the data structure of the store management database according to the embodiment. [Figure 4] Figure 4 shows an example of the data structure of a store-specific product master according to the embodiment. [Figure 5] Figure 5 shows an example of the data structure of the point management DB according to the embodiment. [Figure 6] Figure 6 shows an example of the data structure of the charge balance management DB according to the embodiment. [Figure 7] Figure 7 shows an example of the data structure of the user management database according to the embodiment. [Figure 8] Figure 8 shows an example of the data structure of the check-in management DB according to the embodiment. [Figure 9] Figure 9 shows an example of the data structure of the transaction management DB and the training transaction management DB according to the embodiment. [Figure 10] Figure 10 shows an example of the hardware configuration of the accounting device according to the embodiment. [Figure 11] Figure 11 shows an example of the hardware configuration of an attendant terminal according to this embodiment. [Figure 12] Figure 12 shows an example of the hardware configuration of a user terminal according to this embodiment. [Figure 13] Figure 13 shows an example of the hardware configuration of a cart terminal according to this embodiment. [Figure 14] Figure 14 is a sequence diagram showing an example of the check-in process performed by the transaction processing system of the embodiment. [Figure 15] Figure 15 shows an example of a purchase support screen displayed on the user terminal of the embodiment. [Figure 16] Figure 16 shows an example of a member information screen displayed on the user terminal of the embodiment. [Figure 17] Figure 17 shows an example of a member information screen displayed on the user terminal of the embodiment. [Figure 18] Figure 18 shows an example of a member information screen displayed on the user terminal of the embodiment. [Figure 19] Figure 19 shows an example of a member information screen displayed on the user terminal of the embodiment. [Figure 20] Figure 20 is a sequence diagram showing an example of the check-in process performed by the transaction processing system of the embodiment. [Figure 21] Figure 21 is a sequence diagram showing an example of a mode change process performed by the transaction processing system of the embodiment. [Figure 22] Figure 22 shows an example of a purchase support screen displayed on the user terminal of the embodiment. [Figure 23] FIG. 23 is a sequence diagram showing an example of mode change processing performed by the transaction processing system of the embodiment. [Figure 24] FIG. 24 is a sequence diagram showing an example of ID linking processing performed by the transaction processing system of the embodiment. [Figure 25] FIG. 25 is a sequence diagram showing an example of product registration processing performed by the transaction processing system of the embodiment. [Figure 26] FIG. 26 shows an example of a purchase support screen displayed on the user terminal of the embodiment. [Figure 27] FIG. 27 is a flowchart showing an example of accounting preparation processing performed by the registration terminal of the embodiment. [Figure 28] FIG. 28 is a sequence diagram showing an example of accounting processing performed by the transaction processing system of the embodiment. [Figure 29] FIG. 29 is a flowchart showing an example of transaction determination processing performed by the transaction management server of the embodiment. [Figure 30] FIG. 30 is a flowchart showing an example of accounting processing performed by the accounting device of the embodiment. [Figure 31] FIG. 31 is a flowchart showing an example of confirmation support processing performed by the attendant terminal of the embodiment. [Figure 32] FIG. 32 is a diagram showing an example of a status confirmation screen displayed on the attendant terminal of the embodiment. <000,0099> [Figure 33] FIG. 33 is a diagram showing an example of a registered product confirmation screen displayed on the attendant terminal of the embodiment.

MODE FOR CARRYING OUT THE INVENTION

[0009] The embodiments of the information processing device and server device will be described in detail below with reference to the attached drawings. This embodiment exemplifies a transaction processing system in which, when a customer purchases goods in a sales area where goods are displayed, the customer operates a mobile terminal, which is an information processing device, to input data related to the purchased goods, and then uses an accounting device to complete the payment themselves. The embodiments described below are merely one embodiment of the information processing device and server device, and do not limit their configuration, specifications, etc.

[0010] Figure 1 shows a schematic configuration of the transaction processing system 1 according to this embodiment. The transaction processing system 1 includes a transaction management server 10, an accounting device 20, an attendant terminal 30, a user terminal 40, a cart terminal 50, a settlement server 60, and a training settlement server 70. Each device of the transaction processing system 1 is configured to communicate via a network N.

[0011] Network N can use the Internet, VPN (virtual private network), LAN (local area network), public communication network, mobile communication network, etc., individually or in appropriate combinations. As an example, Network N can be a combination of the Internet and a mobile communication network. Note that any number of transaction management servers 10, accounting devices 20, attendant terminals 30, user terminals 40, cart terminals 50, payment servers 60, and training payment servers 70 may be included in the transaction processing system 1, but only one of each is shown in Figure 1.

[0012] The transaction management server 10 is an example of a server device. The transaction management server 10 uses the user terminal 40 and the cart terminal 50 as user interface terminals and performs information processing to provide a transaction processing service that processes the buying and selling of goods in accordance with the operations of the user at the store where the user interface terminals are used. In other words, typically, a customer who purchases goods at the store becomes a user of the transaction processing service.

[0013] The transaction management server 10 may be implemented as, for example, a cloud server and provide transaction processing services to multiple stores. Alternatively, the transaction management server 10 may be implemented as, for example, a local server and provide transaction processing services to only one store. Furthermore, the transaction management server 10 may include the settlement server 60 and the training settlement server 70.

[0014] The accounting device 20 is an example of an accounting device. The accounting device 20 is installed in the store and performs accounting processing related to transactions processed by the transaction management server 10. For example, the accounting device 20 works in cooperation with the payment server 60 to perform prepaid payments using electronic money. The accounting device 20 receives input from an operator during accounting processing. In other words, the accounting device 20 is a terminal device that accepts user input related to accounting. The operator of the accounting device 20 is mainly the user. However, in some cases, a store employee may also be the operator of the accounting device 20.

[0015] The attendant terminal 30 is an information processing terminal operated, for example, by a store employee. The attendant terminal 30 is a terminal device for a user interface related to information processing, which supports the work of store employees regarding transactions processed by the transaction processing system 1. For example, the attendant terminal 30 is used to read card media issued to users who have registered as members at each store. The attendant terminal 30 is also used to check the status of each transaction performed using the user terminal 40 or the cart terminal 50.

[0016] The user terminal 40 is an example of an information processing device. Typically, the user terminal 40 is owned by the user, brought to the store by the user, and used while moving around the store with the user. The user terminal 40 also functions as a registration terminal that receives user operations for transaction processing on the transaction management server 10. The user terminal 40 can be a mobile device such as a smartphone or tablet.

[0017] The cart terminal 50 is an example of an information processing device. For example, the cart terminal 50 is attached to a shopping cart provided in the store. The cart terminal 50 is lent to the user along with the shopping cart and is used while moving around the store with the user. The cart terminal 50 also functions as a registration terminal that receives operations from the user for transaction processing on the transaction management server 10. The cart terminal 50 may include an information processing device that is lent to the user by the store and carried and used by the user.

[0018] The payment server 60 is a server device that performs electronic payments based on data transmitted from the accounting device 20. Specifically, the payment server 60 performs prepaid payments using the balance of electronic money (hereinafter also referred to as the charge balance) that has been pre-deposited by the user using the transaction processing service.

[0019] Furthermore, the training payment server 70 is a payment server used for training at each store. Here, "training" is a concept that includes not only operational training conducted for store employees, but also tests to verify the operation of the transaction processing system 1.

[0020] The training payment server 70 has the same configuration and functions as, for example, the payment server 60, and performs prepaid payments while maintaining the charge balance by simulating (or virtually) performing electronic payments based on data provided by the accounting device 20. The training payment server 70 may also send an ACK (acknowledgment) of payment completion in response to the data transmitted from the accounting device 20. Alternatively, the payment server 60 and the training payment server 70 may be integrated so that the payment server 60 has the functions of the training payment server 70.

[0021] Next, we will describe the hardware configuration of the transaction management server 10, accounting device 20, attendant terminal 30, user terminal 40, and cart terminal 50 mentioned above.

[0022] Figure 2 shows an example of the hardware configuration of the transaction management server 10. As shown in Figure 2, the transaction management server 10 includes a CPU (Central Processing Unit) 11, ROM (Read Only Memory) 12, RAM (Random Access Memory) 13, a storage unit 14, and a communication unit 15, etc.

[0023] CPU 11 is an example of a processor that comprehensively controls the operation of the transaction management server 10. ROM 12 stores various programs. RAM 13 is a workspace for displaying programs and various data.

[0024] The CPU 11, ROM 12, and RAM 13 are connected via a bus or the like to form a control unit 100 of the computer configuration. In the control unit 100, the CPU 11 operates according to a program (such as a server device program 141) stored in the ROM 12 or memory unit 14 and loaded into the RAM 13, thereby executing various processes. Furthermore, the control unit 100 functions as an example of a first registration means, a second registration means, a setting means, and a transmission control means, based on the CPU 11's operation according to the program stored in the ROM 12 or memory unit 14 and loaded into the RAM 13.

[0025] The storage unit 14 has a storage medium such as an HDD (Hard Disk Drive) or flash memory, and retains its contents even when the power is cut off. The storage unit 14 stores a server device program 141 that the CPU 11 can execute, as well as various setting information. Here, the server device program 141 is a program that describes the procedures for causing the CPU 11 of the transaction management server 10 to execute various processes. The CPU 11 works in cooperation with the server device program 141 to execute check-in processing, mode change processing, ID linkage processing, product registration processing, accounting processing, transaction determination processing, etc., which will be described later.

[0026] Furthermore, the memory unit 14 stores store management DB 142, store-specific product master 143, point management DB 144, charge balance management DB 145, user management DB 146, check-in management DB 147, transaction management DB 148, and training transaction management DB 149, etc.

[0027] The store management DB 142 is a database for managing stores that provide transaction processing services to the transaction management server 10. The store-specific product master 143 is a database for managing the products sold at each store.

[0028] The Point Management DB144 is a database for managing users of point services offered by each store. These point services award points to registered users based on purchase amounts, and provide various benefits based on accumulated points. Furthermore, each member is issued a member ID, and the number of points awarded is managed in conjunction with this member ID.

[0029] The Charge Balance Management DB145 is a database for managing users of prepaid payment services provided by each store. Here, a prepaid payment service is a payment service that allows customers to pay for goods using prepaid amounts (electronic money) using card media such as prepaid cards issued by the store. Furthermore, with prepaid payment services, it is also possible to deposit funds (hereinafter referred to as charging) linked to the user's account (hereinafter also referred to as prepaid card ID) by having the card media read by an electronic money charging terminal placed in the store.

[0030] Furthermore, the charge balance management DB145 will deduct the amount paid by electronic payment from the charge balance of the user who made the electronic payment, in conjunction with the electronic payment performed by the payment server 60. In addition, the charge balance management DB145 will add the amount deposited to the charge balance of the user who made the deposit, in conjunction with the electronic money deposit processing performed by a charging device (not shown) etc.

[0031] Furthermore, in this embodiment, the transaction management server 10 stores the charge balance management DB 145, but it is not limited to this configuration; the settlement server 60 (training settlement server 70) may also store it. In this case, the transaction management server 10 can handle the charge balance management DB 145 stored by the settlement server 60 in the same way as if it were stored locally.

[0032] User Management DB146 is a database for managing users who use the transaction processing service. Check-in Management DB147 is a database for managing users who have checked in at each store.

[0033] Transaction Management DB148 and Training Transaction Management DB149 are databases used to manage the products that users purchase in a single transaction at a store. Specifically, Transaction Management DB148 is a database for managing products purchased in normal mode transactions, which will be described later. Training Transaction Management DB149 is a database for managing products purchased in training transactions, which will also be described later.

[0034] The communication unit 15 is a wired or wireless communication interface that can be connected to the network N. The communication unit 15 communicates with external devices such as the accounting device 20 via the network N.

[0035] Figure 3 shows an example of the data structure of the store management DB 142. As shown in Figure 3, the store management DB 142 stores store IDs and store information in association. The store ID is identification information used to identify each store that provides transaction processing services by the transaction management server 10. Store information stores information about the store. For example, store information stores include information such as the store name.

[0036] Figure 4 shows an example of the data structure of the store-specific product master 143. As shown in Figure 4, the store-specific product master 143 stores store IDs, product IDs, and product information in association with each other. The store ID is identification information used to identify each store that provides transaction processing services by the transaction management server 10, and corresponds to the store ID in the store management DB 142. The product ID is identification information used to identify the products sold at the store corresponding to the store ID. Generally, multiple products are sold at a store, so multiple product IDs are registered in association with the store ID. The product information is information about the product corresponding to the product ID. For example, the product name and price are registered in the product information.

[0037] Figure 5 shows an example of the data structure of the point management DB 144. As shown in Figure 5, the point management DB 144 stores data associated with the store ID, member ID, and point count. The store ID is identification information used to identify each store that provides point services, and corresponds to the store ID in the store management DB 142. The member ID is identification information used to identify members of the point service provided at the store corresponding to the store ID. Generally, there are multiple members of a point service, so multiple member IDs are registered in association with the store ID. The point count is the cumulative value of points awarded to the user corresponding to the member ID.

[0038] Furthermore, the point management DB144 is configured so that when points are awarded to a user at a participating store, the number of points awarded is added to the number of points associated with that user's member ID. Also, when a user uses points at a participating store, the point management DB144 is configured so that the number of points used is subtracted from the number of points associated with that user's member ID.

[0039] Figure 6 shows an example of the data structure of the charge balance management DB145. As shown in Figure 6, the charge balance management DB145 stores the store ID, prepaid card ID, and charge balance in association. The store ID is identification information for identifying each store that provides prepaid payment services and corresponds to the store ID in the store management DB142. The prepaid card ID is identification information for identifying the user of the prepaid payment service provided at the store corresponding to the store ID. Generally, there are multiple users of the prepaid payment service, so multiple prepaid card IDs are registered in association with the store ID. The charge balance is information indicating the balance of the amount charged by the user corresponding to the prepaid card ID.

[0040] Furthermore, the charge balance management DB145 is configured so that when a user charges their card at a participating store, the charged amount is added to the charge balance associated with that user's prepaid card ID. Also, when the amount charged by a user is used for payment at a participating store, the charge balance management DB145 is configured so that the payment amount is deducted from the charge balance associated with that user's prepaid card ID.

[0041] Figure 7 shows an example of the data structure of the user management DB 146. As shown in Figure 7, the user management DB 146 stores user terminal IDs, user information, and store-specific information in association with each other. The user terminal ID is identification information for identifying each user terminal 40. In this embodiment, the user terminal ID of the user terminal 40 owned by the user is used as information to identify the user, but this is not limited to this, and the user's own ID may be used instead of the user terminal ID.

[0042] User information stores register information about the user. For example, user information stores the user's name, etc. Store-specific information stores register information about the user at each store the user uses. Specifically, store-specific information stores include items such as store ID, member ID, prepaid card ID, and store settings information. The store ID is the identification information for the store the user uses and corresponds to the store ID in store management DB142. The member ID is the identification information for identifying members of the point service provided at the store the user uses and corresponds to the member ID in point management DB144. The prepaid card ID is the identification information for identifying users of the prepaid payment service provided at the store the user uses and corresponds to the prepaid card ID in charge balance management DB145.

[0043] In this embodiment, since each store is assumed to provide its own unique point service and prepaid payment service, a different pair of member ID and prepaid card ID is registered for each store ID. If a member ID and / or prepaid card ID is used in common across multiple stores, the same member ID and / or prepaid card ID should be registered in association with the store ID of that store. Furthermore, the member ID and / or prepaid card ID may be left blank, and the member ID and / or prepaid card ID may be registered midway through the process, for example, through the ID linking process described later.

[0044] Store settings information is registered for each store as defined by the user. For example, store settings information may include authentication information (passcode, etc.) used for authentication when using member IDs and prepaid card IDs. Also, store settings information may include the payment methods used at each store (e.g., prepaid payment). Furthermore, store settings information may include settings for enabling or disabling functions that can be executed on the user terminal 40 and cart terminal 50 used at each store. The functions that can be enabled or disabled may be functions implemented by the hardware configuration of the user terminal 40 and cart terminal 50, or functions implemented by programs installed on the user terminal 40 and cart terminal 50 (user terminal program 441 and cart terminal program 541 described later). Store settings information may also be left blank.

[0045] In this embodiment, the users of the user terminal IDs registered in the user management DB146 are not limited to customers who purchase products at the store, but also include users who are trained, such as store employees.

[0046] Figure 8 shows an example of the data structure of the check-in management DB 147. As shown in Figure 8, the check-in management DB 147 stores the transaction ID, store ID, terminal ID, member ID, prepaid card ID, management data, and mode flag in association with each other. The transaction ID is identification information used to identify users who have checked in (visited) the store. The transaction ID also functions as identification information used to identify each transaction performed by the transaction processing service of the transaction management server 10.

[0047] The store ID is identification information used to identify the store where a user checked in, and corresponds to the store ID in the store management DB142. The terminal ID is identification information used to identify the terminal used by the user who checked in. For example, if a user uses user terminal 40, the user terminal ID of user terminal 40 is registered in the terminal ID field. Also, for example, if a user uses cart terminal 50, identification information that can identify each cart terminal 50 (hereinafter referred to as cart terminal ID) is registered in the terminal ID field.

[0048] The Member ID field will register the Member ID of the user who checked in at the store. Similarly, the Prepaid Card ID field will register the Member ID of the user who checked in at the store. If either the Member ID or Prepaid Card ID, or both, are not registered, the corresponding field will be left blank.

[0049] The management data items include various data for managing the status of transactions corresponding to the transaction ID. The management data includes, for example, the start time, the time of the previous operation, the status, the accounting device ID, and the cancellation flag. The start time represents the time when the transaction in question was started. The time of the previous operation represents the time when the most recent operation was performed on the user terminal 40 or cart terminal 50 regarding the transaction in question. The status represents the progress of the transaction in question, divided into several categories. Examples of statuses include "Entering the store," "Shopping," "Checking out," "Leaving the store," and "Cancelled." The accounting device ID is identification information that identifies the accounting device 20 used for settlement related to the transaction in question, or the accounting device 20 that was used. The cancellation flag indicates that the processing related to the transaction in question is in a temporarily suspended state. The control unit 100 of the transaction management server 10 works in cooperation with the accounting device 20, user terminal 40, cart terminal 50, etc., to register and update each piece of management data, thereby managing the status of transactions performed by users or transactions that have been performed by users.

[0050] The mode flag is flag information used to identify whether a transaction corresponding to a transaction ID is a normal transaction for purchasing goods at a store (hereinafter also referred to as normal mode) or a training transaction (hereinafter referred to as training mode). The mode flag registers binary information (on, off) to distinguish between normal mode and training mode. The initial state of the mode flag is set to "off," which indicates normal mode.

[0051] In the following, the information registered in the check-in management DB147 in association with the transaction ID, excluding the mode flag, will also be referred to as check-in data. Furthermore, check-in data may include information other than that described above. For example, user information corresponding to the user terminal ID, or store setting information corresponding to the store ID and user terminal ID pair, may be included in the check-in data.

[0052] Figure 9 shows an example of the data structure of the transaction management DB 148 and the training transaction management DB 149. As shown in Figure 9, the transaction management DB 148 and the training transaction management DB 149 store transaction IDs, product IDs, and product information in association. The transaction ID is identification information used to identify each transaction performed by the transaction processing service of the transaction management server 10, and corresponds to the transaction ID in the check-in management DB 147.

[0053] The Product ID is the identification information for the product registered as the purchase target in the transaction corresponding to the Transaction ID, and corresponds to the Product ID in the store-specific Product Master 143. If multiple products are registered, multiple Product IDs are registered in association with the Transaction ID. The Product Information is the product information for the product corresponding to the Product ID.

[0054] Furthermore, the transaction management DB148 may store other information associated with the transaction ID. For example, the transaction management DB148 may store the total amount of products registered in association with the transaction ID. Also, if multiple identical product IDs are registered for the same transaction ID, the transaction management DB148 may consolidate those product IDs into one and register the points of the duplicate product IDs in association. Hereinafter, information indicating the breakdown of products, such as product IDs and product information, registered in association with the same transaction ID will also be referred to as "transaction data".

[0055] Figure 10 shows an example of the hardware configuration of the accounting device 20. As shown in Figure 10, the accounting device 20 includes a CPU 21, ROM 22, RAM 23, storage unit 24, display unit 25, operation unit 26, code reading unit 27, and communication unit 28, etc.

[0056] The CPU 21 is an example of a processor that comprehensively controls the operation of the accounting device 20. The ROM 22 stores various programs. The RAM 23 is a workspace for displaying programs and various data.

[0057] The CPU 21, ROM 22, and RAM 23 are connected via a bus or the like to form a control unit 200 of the computer configuration. In the control unit 200, the CPU 21 operates according to a program (such as an accounting device program 241) stored in the ROM 22 or memory unit 24 and loaded into the RAM 23, thereby executing various processes.

[0058] The storage unit 24 has a storage medium such as an HDD or flash memory and retains its contents even when the power is cut off. The storage unit 24 stores accounting device programs 241 and various setting information that the CPU 21 can execute. Here, the accounting device program 241 is a program that describes the procedures for causing the CPU 21 of the accounting device 20 to execute various processes. The CPU 21 works in cooperation with the accounting device program 241 to execute accounting processes and the like, which will be described later.

[0059] The display unit 25 is a display device such as an LCD (Liquid Crystal Display). The display unit 25 displays various information under the control of the CPU 21. The operation unit 26 is an input device such as a keyboard or a pointing device. The operation unit 26 outputs the operation content entered via the input device to the CPU 21. The operation unit 26 may also be a touch panel provided on the display unit 25.

[0060] The code reading unit 27 is a reading device capable of reading code symbols such as barcodes and two-dimensional codes. In this embodiment, the code reading unit 27 is used to read code symbols displayed on the user terminal 40 or cart terminal 50, but the reading target is not limited to these.

[0061] The communication unit 28 is a wired or wireless communication interface that can be connected to the network N. The communication unit 28 communicates with external devices such as the transaction management server 10 via the network N.

[0062] Figure 11 shows an example of the hardware configuration of the attendant terminal 30. As shown in Figure 11, the attendant terminal 30 includes a CPU 31, ROM 32, RAM 33, storage unit 34, display unit 35, operation unit 36, card reader unit 37, and communication unit 38, etc.

[0063] The CPU 31 is an example of a processor that comprehensively controls the operation of the attendant terminal 30. The ROM 32 stores various programs. The RAM 33 is a workspace for displaying programs and various data.

[0064] The CPU 31, ROM 32, and RAM 33 are connected via a bus or the like to form a control unit 300 of the computer configuration. In the control unit 300, the CPU 31 operates according to a program (attendant terminal program 341) stored in the ROM 32 or memory unit 34 and loaded into the RAM 33, thereby executing various processes.

[0065] The storage unit 34 has a storage medium such as an HDD or flash memory and retains its contents even when the power is cut off. The storage unit 34 stores the attendant terminal program 341 and various setting information that the CPU 31 can execute. Here, the attendant terminal program 341 is a program that describes the procedures for causing the CPU 31 of the attendant terminal 30 to execute various processes. The CPU 31 works in cooperation with the attendant terminal program 341 to execute the ID linkage process, confirmation support process, etc., which will be described later.

[0066] The display unit 35 is a display device such as an LCD. The display unit 35 displays various information under the control of the CPU 31. The operation unit 36 ​​is an input device such as a keyboard or a pointing device. The operation unit 36 ​​outputs the operation content entered via the input device to the CPU 31. The operation unit 36 ​​may also be a touch panel provided on the display unit 35.

[0067] The card reader unit 37 is a reader capable of reading information from a card medium. The specifications of the card reader unit 37 are not particularly limited and can be changed according to the card medium used in the store. For example, a store that uses magnetic cards as the card medium can use a card reader unit 37 that can read magnetic cards. Also, for example, a store that uses cards with code symbols attached as the card medium can use a card reader unit 37 that can read the code symbols attached to the cards. Furthermore, a store that uses cards with wireless tags attached as the card medium can use a card reader unit 37 that can read wireless tags.

[0068] In this embodiment, it is assumed that stores providing both point services and prepaid payment services distribute card media holding member IDs and prepaid card IDs to users of those stores. Furthermore, users who only use either the point service or the prepaid payment service may be distributed card media holding the ID for the service they use.

[0069] Alternatively, the system may be configured such that member IDs and prepaid card IDs are managed by a dedicated application program (hereinafter also referred to as the store application program) installed on the user's mobile device, such as user terminal 40. In this case, the store application program may be prepared for each store, and by launching the store application program at the store where the user has checked in, the member ID and prepaid card ID for that store become available for use. The store application program also has a function to display and output the user's member ID and prepaid card ID registered at that store in the form of a code symbol or the like, in response to the user's operation.

[0070] The communication unit 38 is a wired or wireless communication interface that can be connected to the network N. The communication unit 38 communicates with external devices such as the transaction management server 10 via the network N.

[0071] The attendant terminal 30 may also be equipped with a code reading unit similar to the code reading unit 27 described above. In this case, the attendant terminal 30 may be configured to read the user's member ID and prepaid card ID from a code symbol displayed and output by a store application program installed on the user's mobile terminal, using the code reading unit.

[0072] Figure 12 shows an example of the hardware configuration of a user terminal 40. As shown in Figure 12, the user terminal 40 includes a CPU 41, ROM 42, RAM 43, storage unit 44, display unit 45, operation unit 46, imaging unit 47, and communication unit 48, etc.

[0073] The CPU 41 is an example of a processor that comprehensively controls the operation of the user terminal 40. The ROM 42 stores various programs. The RAM 43 is a workspace for displaying programs and various data.

[0074] The CPU 41, ROM 42, and RAM 43 are connected via a bus or the like to form a control unit 400 of the computer configuration. In the control unit 400, the CPU 41 operates according to a program (such as a user terminal program 441) stored in the ROM 42 or memory unit 44 and loaded into the RAM 43, thereby executing various processes. Furthermore, the control unit 400 functions as an example of registration means, acquisition means, switching means, and output control means, based on the CPU 41's operation according to the program stored in the ROM 42 or memory unit 44 and loaded into the RAM 43.

[0075] The storage unit 44 has a storage medium such as an HDD or flash memory and maintains its contents even when the power is cut off. The storage unit 44 stores user terminal programs 441 and various setting information that the CPU 41 can execute. Here, the user terminal program 441 is a program that describes procedures for causing the CPU 41 of the user terminal 40 to execute various processes. For example, the user terminal program 441 may include application programs for each store. The CPU 41 works in cooperation with the user terminal program 441 to execute check-in processing, mode change processing, ID linking processing, product registration processing, accounting preparation processing, etc., which will be described later.

[0076] The display unit 45 is a display device such as an LCD. The display unit 45 displays various information under the control of the CPU 41. The operation unit 46 is an input device such as a keyboard or a pointing device. The operation unit 46 outputs the operation content input via the input device to the CPU 41. The operation unit 46 may also be a touch panel provided on the display unit 45.

[0077] The imaging unit 47 is a digital camera having an image sensor such as a CCD (Charge Coupled Device) or CMOS (Complementary MOS), and acquires images by capturing images. In this embodiment, the imaging unit 47 is used to read code symbols attached to products, code symbols for check-in detection displayed at store entrances, code symbols displayed on attendant terminals 30, etc.

[0078] The communication unit 48 is a wired or wireless communication interface that can be connected to the network N. The communication unit 48 communicates with external devices such as the transaction management server 10 via the network N.

[0079] Figure 13 shows an example of the hardware configuration of the cart terminal 50. As shown in Figure 13, the cart terminal 50 includes a CPU 51, ROM 52, RAM 53, storage unit 54, display unit 55, operation unit 56, code reading unit 57, card reading unit 58, and communication unit 59, etc.

[0080] The CPU 51 is an example of a processor that comprehensively controls the operation of the cart terminal 50. The ROM 52 stores various programs. The RAM 53 is a workspace for displaying programs and various data.

[0081] The CPU 51, ROM 52, and RAM 53 are connected via a bus or the like to form a control unit 500 of the computer configuration. In the control unit 500, the CPU 51 operates according to a program (such as a cart terminal program 541) stored in the ROM 52 or memory unit 54 and loaded into the RAM 53, thereby executing various processes. Furthermore, the control unit 500 functions as an example of registration means, acquisition means, switching means, and output control means, based on the CPU 51's operation according to the program stored in the ROM 52 or memory unit 54 and loaded into the RAM 53.

[0082] The storage unit 54 has a storage medium such as an HDD or flash memory and retains its contents even when the power is cut off. The storage unit 54 stores a cart terminal program 541 and various setting information that the CPU 51 can execute. Here, the cart terminal program 541 is a program that describes the procedures for causing the CPU 51 of the cart terminal 50 to execute various processes. The CPU 51 works in cooperation with the cart terminal program 541 to execute processes such as check-in processing, mode change processing, ID linking processing, product registration processing, and accounting preparation processing, which will be described later.

[0083] The display unit 55 is a display device such as an LCD. The display unit 55 displays various information under the control of the CPU 51. The operation unit 56 is an input device such as a keyboard or a pointing device. The operation unit 56 outputs the operation content input via the input device to the CPU 51. The operation unit 56 may also be a touch panel provided on the display unit 55.

[0084] The code reading unit 57 is a reading device capable of reading code symbols similar to those of the code reading unit 27. The card reading unit 58 is a reading device capable of reading information from a card medium similar to those of the card reading unit 37. In this embodiment, the code reading unit 27 is used to read code symbols attached to products. The card reading unit 58 is used to read the aforementioned card medium.

[0085] In addition, if the user's member ID and prepaid card ID are managed by the store's application program installed on the user's mobile device, the code reading unit 57 may read the member ID and prepaid card ID from the code symbol displayed and output by the application program.

[0086] The communication unit 59 is a wired or wireless communication interface that can be connected to the network N. The communication unit 59 communicates with external devices such as the transaction management server 10 via the network N.

[0087] Next, the operation of the transaction processing system 1 configured as described above will be explained. The contents of the various processes described below are examples, and it is possible to change the order of some processes, omit some processes, or add other processes as appropriate. For example, in the following explanation, the explanation of some processes has been omitted in order to clearly explain the characteristic operation of this embodiment. For example, if some error occurs, processing to deal with that error may be performed, but such processing has been omitted from the description.

[0088] The following describes the operations performed by the transaction processing system 1, divided into stages related to the transaction processing service. In the following description, when the user terminal 40 and the cart terminal 50 are not distinguished, they will be referred to as the "registration terminal." Also, when describing the hardware configuration of the user terminal 40 or the cart terminal 50 using the registration terminal, the hardware configuration of the user terminal 40 will be used for the description.

[0089] First, we will explain an example of the check-in process, where a customer who has come to the store operates the user terminal 40 or cart terminal 50 to begin using the transaction processing service.

[0090] The control unit 400 of the registration terminal sends a check-in instruction to the transaction management server 10 in response to user operations and performs check-in processing in cooperation with the transaction management server 10. Specifically, the control unit 400 sends a check-in instruction to the transaction management server 10 that includes the terminal ID of its own registration terminal and the store ID of the store.

[0091] Here, the characteristics of the terminal IDs transmitted differ between the user terminal 40 and the cart terminal 50. Specifically, the user terminal 40 uses a uniquely identifiable user terminal ID, while the cart terminal 50 uses a shared cart terminal ID used by an unspecified number of users. Therefore, the content of the check-in process differs between the user terminal 40 and the cart terminal 50.

[0092] First, with reference to Figure 14, the check-in process performed by the control unit 400 of the user terminal 40 will be explained. Figure 14 is a sequence diagram showing an example of the check-in process performed by the transaction processing system 1, and shows an example of the process when using the user terminal 40.

[0093] First, the control unit 400 of the user terminal 40 obtains the store ID of the store the user has entered (step S11). Here, various methods can be used to obtain the store ID. For example, a code symbol for check-in processing that holds the store ID of the store may be posted at the entrance of the store, and the store ID may be obtained by reading the code symbol. In this case, the control unit 400 of the user terminal 40 decodes the code symbol for check-in processing captured by the imaging unit 47 and obtains the store ID by reading the store ID held in the code symbol. In this case, the code symbol for check-in processing may also hold the connection address of the transaction management server 10, etc.

[0094] Alternatively, if the user terminal 40 is equipped with a positioning function such as GPS (Global Positioning System), it may be configured to use this positioning function to obtain the store ID of the store corresponding to the terminal's current location. In this case, for example, the user terminal 40 obtains the store ID corresponding to the location information representing the terminal's current location based on configuration information that associates the location information of each store with the store ID.

[0095] Next, the control unit 400 of the user terminal 40 sends a check-in instruction to the transaction management server 10, which includes the store ID obtained in step S11 and the user terminal ID of its own user terminal 40 (step S12).

[0096] The control unit 100 of the transaction management server 10 manages users who have entered the store in response to check-in instructions sent from the user terminal 40, using the check-in management DB 147. Specifically, when the control unit 100 receives a check-in instruction, it issues a unique transaction ID (step S13). Next, the control unit 100 associates the issued transaction ID with the store ID and user terminal ID specified in the check-in instruction and registers it in the check-in management DB 147.

[0097] Furthermore, the control unit 100 of the transaction management server 10 refers to the user management DB 146 and determines whether or not a member ID exists in the data entry for store-specific information corresponding to the user terminal ID and store ID specified in the check-in instruction (step S14). If the member ID does not exist, the process proceeds to step S16.

[0098] If a member ID exists (step S14; Yes), the control unit 100 of the transaction management server 10 reads the member ID, associates it with the transaction ID issued in step S13, and registers it in the check-in management DB 147. The control unit 100 also reads the number of points stored in association with the store ID and member ID specified in the check-in instruction from the point management DB 144 (step S15), and proceeds to step S16.

[0099] In step S16, the control unit 100 of the transaction management server 10 refers to the user management DB 146 and determines whether or not a prepaid card ID exists in the data entry for store-specific information corresponding to the user terminal ID and store ID specified in the check-in instruction (step S16). If the prepaid card ID does not exist (step S16; No), the process proceeds to step S18.

[0100] If a prepaid card ID exists (step S16; Yes), the control unit 100 of the transaction management server 10 reads the prepaid card ID, associates it with the transaction ID issued in step S13, and registers it in the check-in management DB 147. The control unit 100 also reads the charge balance stored in association with the store ID and prepaid card ID specified in the check-in instruction from the charge balance management DB 145 (step S17), and proceeds to step S18.

[0101] In this way, the control unit 100 of the transaction management server 10 registers the destination (prepaid card ID) of the electronic money charged by the user, associating it with the transaction ID. In other words, the control unit 100 of the transaction management server 10 functions as an example of a second registration means.

[0102] In step S18, the control unit 100 of the transaction management server 10 sends a check-in completion notification containing the transaction ID issued in step S13 to the user terminal 40 (step S18). Then, the control unit 100 of the transaction management server 10 sets the status of the management data related to the transaction ID of the transaction to "checked in" (step S19).

[0103] Furthermore, if the control unit 100 has registered a member ID or prepaid card ID in the check-in management DB 147, it will send the check-in completion notification to the user terminal 40, including the corresponding number of points and charge amount along with those IDs. The check-in completion notification may also include, for example, store information for the store ID specified in the check-in instruction, or store setting information corresponding to the store ID and user terminal ID specified in the check-in instruction.

[0104] Furthermore, while Figure 14 illustrates an example where a check-in completion notification is sent immediately if a member ID and / or prepaid card ID exist, the system is not limited to this; it may also be configured to send the check-in completion notification after user authentication.

[0105] For example, the control unit 100 of the transaction management server 10 may instruct the user terminal 40 to enter authentication information such as a passcode before sending a check-in completion notification. In this case, the control unit 400 of the user terminal 40, upon receiving the instruction, displays an input screen (not shown) for entering authentication information on the display unit 45 and sends the entered authentication information to the transaction management server 10. The control unit 100 of the transaction management server 10 compares the authentication information sent from the user terminal 40 with the authentication information held in the store setting information of the store-specific information data entry corresponding to the user terminal ID and store ID instructed in the check-in instruction. Then, the control unit 100 of the transaction management server 10 sends a check-in completion notification including the member ID, prepaid card ID, etc., only if the user can be verified. If the user cannot be verified, the system may be configured to prohibit the use of the transaction processing service by notifying an error instead of a check-in completion notification, or to permit the use of the transaction processing service by sending a check-in completion notification that does not include the ID, etc.

[0106] Meanwhile, when the control unit 400 of the user terminal 40 receives a check-in completion notification from the transaction management server 10, it acquires information such as the transaction ID contained in the check-in completion notification and stores it in RAM 43 or the like. Then, based on the information contained in the check-in completion notification, the control unit 400 displays a screen to support shopping at the store (hereinafter also referred to as the purchase support screen) on the display unit 45 (step S20). Here, the transaction ID contained in the check-in completion notification functions as an example of specific information that can identify the charge destination to which the user charged electronic money or the product to be registered in the registration process described later. In other words, the control unit 400 of the user terminal 40 functions as an example of an acquisition means for acquiring specific information.

[0107] Furthermore, when the control unit 400 of the user terminal 40 receives store setting information from the transaction management server 10, it will control the functions and operation of its terminal based on the settings of the store setting information. In addition, the settings of the store setting information can be changed at any time.

[0108] Figure 15 shows an example of a purchase support screen displayed on the user terminal 40. As shown in Figure 15, the purchase support screen A has a first display area Aa, a second display area Ab, a third display area Ac, and a fourth display area Ad.

[0109] The first display area Aa shows the store name of the store that performed the check-in process and the current operating mode Aaa. Figure 15 shows an example where the operating mode Aaa is set to "Registering," meaning that product registration is possible.

[0110] Furthermore, the first display area Aa is equipped with member buttons Aab, which display information about the user at the store where the check-in process was performed. The operation of member buttons Aab will be described later.

[0111] The second display area Ab displays information regarding the charge balance associated with the user's prepaid card ID. Specifically, the charge balance associated with the user's prepaid card ID is displayed in the second display area Ab. Alternatively, the second display area Ab may display the number of points associated with the user's member ID.

[0112] The third display area Ac is an area for displaying information about products registered in the registration process described later (hereinafter also referred to as registered products). The third display area Ac has a total display area Aca and a registered product area Acb. The total display area Aca displays the total number of registered products and the total amount. The registered product area Acb displays information such as the product name, number of products, and price of the registered products in the order they were registered. Note that the arrangement of the total display area Aca and the registered product area Acb in the third display area Ac is not limited to the illustrated example, and they may be arranged upside down, for example.

[0113] The fourth display area, Ad, displays various controls. Specifically, the fourth display area, Ad, displays the Register button Ada and the Checkout button Adb. Here, the Register button Ada is the control used to instruct the system to perform the product registration process. The Checkout button Adb is the control used to instruct the system to start the checkout process, which will be described later.

[0114] In the purchase support screen A described above, the control unit 400 of the user terminal 40, when notified of the charge balance in the check-in completion notification, displays the charge balance in the second display area Ab to inform the user of the charge balance available at that store. In addition, the control unit 400 of the user terminal 40 may also display the number of points in the second display area Ab if notified of the number of points in the check-in completion notification.

[0115] Furthermore, when the control unit 400 of the user terminal 40 receives an operation on the member buttons Aab in the first display area Aa, it displays the member information screen B shown in Figure 16 as a pop-up, for example, superimposed on the purchase support screen A.

[0116] Figure 16 shows an example of a member information screen displayed on the user terminal 40. As shown in Figure 16, the member information screen B displays the user's usage status regarding the point service provided by the store and the user's usage status regarding the prepaid service provided by the store.

[0117] Specifically, the Member Information Screen B displays the user's Member ID and point balance in association. It also displays the user's Prepaid Card ID and charge balance in association. Here, the information displayed on the Member Information Screen B is based on the information notified in the check-in completion notification. In other words, Figure 16 shows an example of the Member Information Screen B when the Member ID and Prepaid Card ID are registered in the User Management DB 146 in association with the store ID and user terminal ID specified in the check-in instruction.

[0118] Furthermore, on the member information screen B, an update button Ba is provided, associated with the prepaid card ID. The update button Ba is an operator used to instruct the user to update the charge balance, and is operated, for example, when an additional amount has been charged. When the update button Ba is operated, the control unit 400 of the user terminal 40 sends a request to the transaction management server 10 to retrieve the charge balance, including the store ID, user terminal ID, and prepaid card ID. When the control unit 100 of the transaction management server 10 receives the request to retrieve the charge balance, it reads the charge balance that matches the conditions of the retrieval request from the charge balance management DB 145 and sends it to the requesting transaction management server 10. The control unit 400 of the user terminal 40 also updates the display on the member information screen B and the purchase support screen A based on the charge amount sent from the transaction management server 10.

[0119] This allows users of the user terminal 40 to easily check the number of points earned at the store where they checked in, as well as the status of their charge balance, by viewing the member information screen B. Therefore, the transaction processing system 1 can improve the convenience of using point services and prepaid payment services offered at stores.

[0120] Furthermore, the display method for member information screen B is not limited to pop-up display; it may be displayed in other forms. For example, member information screen B may be displayed in a form that switches with purchase support screen A. Alternatively, member information screen B may be displayed while sliding in one of the up, down, left, or right directions, replacing purchase support screen A which becomes invisible when slid in that direction.

[0121] Furthermore, if the member ID and prepaid card ID are not registered in the user management DB146 in association with the store ID and user terminal ID specified in the check-in instruction, that is, if the user terminal ID is not linked to the member ID and prepaid card ID, for example, the control unit 400 of the user terminal 40 will display the member information screen B as shown in Figure 17.

[0122] Figure 17 shows an example of a member information screen displayed on the user terminal 40. If the user terminal ID, member ID, and prepaid card ID are not linked, information indicating that member registration has not been completed will be displayed on the member information screen B, as shown in Figure 17. In this case, an operation button Bb for member registration will be displayed on the member information screen B. When the operation button Bb is pressed, the control unit 400 of the user terminal 40 will perform processing to prompt member registration by displaying a screen for member registration for the point service provided by the store, or by accessing the registration site.

[0123] Furthermore, if either the Member ID or the Prepaid Card ID is not linked, the Member Information Screen B, as shown in Figures 18 and 19, will be displayed.

[0124] Figure 18 shows an example of the member information screen displayed on the user terminal 40, illustrating the screen when the prepaid card ID is not linked. In this case, the member information screen B displays the member ID linked to the user terminal ID and the number of points corresponding to that member ID, but information regarding the prepaid payment service is not displayed. If the store where the check-in process was performed offers a prepaid payment service, information encouraging the use of the prepaid payment service may be displayed.

[0125] Figure 19 shows an example of the member information screen displayed on the user terminal 40, illustrating a screen example when the member ID is not linked. In this case, the member information screen B displays the prepaid card ID linked to the user terminal ID, the corresponding charge balance, and the update button Ba, but information regarding the point service is not displayed. If the store where the check-in process was performed offers a point payment service, information encouraging the use of the point payment service may be displayed.

[0126] In the check-in process described above, the member ID and prepaid card ID are registered in the check-in management DB 147 based on the store ID and member ID specified in the check-in instruction. However, other information related to the specified store ID and member ID may also be registered in the check-in management DB 147. For example, the control unit 100 of the transaction management server 10 may read user information corresponding to the member ID specified in the check-in instruction from the user management DB 146 and register it in the check-in management DB 147. Alternatively, the control unit 100 of the transaction management server 10 may read store setting information corresponding to the store ID and member ID specified in the check-in instruction from the user management DB 146 and register it in the check-in management DB 147.

[0127] On the other hand, the check-in process in the case of the cart terminal 50 follows the sequence shown in Figure 20. Here, Figure 20 is a sequence diagram showing an example of the check-in process performed by the transaction processing system 1, and shows an example of the process when using the cart terminal 50.

[0128] First, the control unit 500 of the cart terminal 50 waits until the card medium is read via the card reader 58 (step S31; No). If the user's mobile terminal has a store application program installed, the control unit 500 may wait until the code symbol holding the member ID, prepaid card ID, etc. is read via the code reader 57.

[0129] When the control unit 500 determines that the card medium has been read (step S31; Yes), it sends a check-in instruction to the transaction management server 10 that includes the store ID of its own store, the cart terminal ID of its own terminal, and the information read from the card medium (hereinafter also referred to as card information) (step S32).

[0130] Here, the store ID can be stored in advance, for example, in the memory unit 54. In addition, the card information read from the card medium will include either or both of the member ID and the prepaid card ID, depending on the status of the services provided by the store and the services used by the user.

[0131] The control unit 100 of the transaction management server 10 manages customers who have visited the store using the check-in management DB 147 in response to check-in instructions sent from the cart terminal 50. Specifically, when the control unit 100 receives a check-in instruction from the cart terminal 50, it issues a transaction ID (step S33). Next, the control unit 100 associates the issued transaction ID with the store ID and cart terminal ID specified in the check-in instruction and registers this information in the check-in management DB 147.

[0132] Next, the control unit 100 of the transaction management server 10 determines whether or not the check-in instruction includes a member ID (step S34). If a member ID does not exist, the process proceeds to step S36.

[0133] If a member ID exists (step S34; Yes), the control unit 100 of the transaction management server 10 registers the member ID in the check-in management DB 147 in association with the transaction ID issued in step S33. Next, the control unit 100 reads the number of points associated with the store ID and member ID pair instructed in the check-in instruction from the point management DB 144 (step S35), and proceeds to step S36.

[0134] Furthermore, the control unit 100 of the transaction management server 10 determines whether or not the check-in instruction includes a prepaid card ID (step S36). If a prepaid card ID does not exist, the process proceeds to step S38.

[0135] If a prepaid card ID exists (step S36; Yes), the control unit 100 of the transaction management server 10 registers the prepaid card ID in the check-in management DB 147 in association with the transaction ID issued in step S33. Next, the control unit 100 reads the charge balance associated with the store ID and prepaid card ID pair specified in the check-in instruction from the charge balance management DB 145 (step S37), and proceeds to step S38.

[0136] In this way, the control unit 100 of the transaction management server 10 registers the destination (prepaid card ID) of the electronic money charged by the user, associating it with the transaction ID. In other words, the control unit 100 of the transaction management server 10 functions as an example of a second registration means.

[0137] In step S38, the control unit 100 of the transaction management server 10 sends a check-in completion notification to the cart terminal 50, similar to the case of the user terminal 40 (step S38). Then, the control unit 100 of the transaction management server 10 sets the status of the management data related to the transaction to "checked in" (step S39). Note that in the check-in process shown in Figure 20, the sending of the check-in completion notification may be configured to occur after user authentication.

[0138] When the control unit 500 of the cart terminal 50 receives a check-in completion notification from the transaction management server 10, it acquires information such as the transaction ID contained in the check-in completion notification and stores it in RAM 53 or the like. Then, the control unit 500 displays the purchase support screen on the display unit 55 based on the information contained in the check-in completion notification (step S40). Here, the transaction ID contained in the check-in completion notification functions as an example of specific information that can identify the charge destination to which the user charged electronic money, or the product to be registered in the registration process described later, similar to the case of the user terminal 40. In other words, the control unit 500 of the cart terminal 50 functions as an example of an acquisition means for acquiring specific information.

[0139] If the member ID or prepaid card ID is provided in the check-in completion notification, the purchase support screen displayed on the cart terminal 50 will also display the points and charge balance in the display unit 55, in the same format as the purchase support screen on the user terminal 40. In addition, the cart terminal 50 will also display a member information screen showing the points and charge balance at the store where the check-in was processed, depending on the user's operation.

[0140] As a result, even when using the cart terminal 50, users can easily check the number of points and the status of their charge balance at the store where they checked in by looking at the screen displayed on the display unit 55. Therefore, the transaction processing system 1 can improve the convenience of using point services and prepaid payment services provided by stores.

[0141] Next, we will describe an example of how a user performing training can switch from normal mode to training mode by operating the user terminal 40 or cart terminal 50.

[0142] Users who wish to perform training can declare their intention to perform training by operating a registration terminal at the store where they are checking in, or at the store where they have checked in. Specifically, the control unit 400 of the registration terminal sends a mode change instruction to the transaction management server 10 instructing it to switch to training mode, in response to the user's operation. In response to the mode change instruction from the registration terminal, the transaction management server 10 changes the mode flag of the corresponding transaction to the training mode state.

[0143] Figure 21 is a sequence diagram showing an example of the mode change process performed by the transaction processing system 1.

[0144] First, when the control unit 400 of the registration terminal receives an instruction to switch to training mode (step S51), it sends a mode change instruction to the transaction management server 10, which includes the transaction ID stored in RAM or the like, and information (e.g., a command) instructing the change to training mode (step S52).

[0145] Here, there is no particular limitation on how the instruction to change to training mode is received, and various methods can be employed. For example, a code symbol for training mode that holds information instructing the user to switch to training mode may be prepared, and the user may give the instruction to change to training mode by having the registration terminal read the code symbol. In this case, the control unit 400 of the registration terminal determines that the instruction to change to training mode has been received when it reads the information instructing the user to switch to training mode from the code symbol via the imaging unit 47.

[0146] Alternatively, the check-in code symbol may include information instructing the user to switch to training mode, thereby enabling the check-in process to be performed while the user is in training mode. In this case, the control unit 400 of the registration terminal sends a check-in instruction to the transaction management server 10 during the check-in process described above, which includes the store ID, the terminal ID of the user's own terminal, and information instructing the user to switch to training mode.

[0147] Alternatively, another method of receiving instructions may be to switch to training mode via the operation unit 46. For example, the control unit 400 of the registration terminal displays an operator on the display unit 45 that allows switching between normal mode and training mode, provided that an administrator ID such as a store employee or manager has been entered via the operation unit 46 or by reading a code symbol. The control unit 400 of the registration terminal may then be configured to receive an instruction to switch to training mode via the operation of the operator.

[0148] Transactions in training mode differ from those in normal mode. Specifically, in training mode, a simulated accounting process is performed in which the payment for goods is not actually made. Therefore, it is preferable to restrict access to training mode by requiring user authentication or similar measures to prevent general users from entering training mode.

[0149] Meanwhile, when the control unit 100 of the transaction management server 10 receives a mode change instruction from the registration terminal, it changes the mode flag of the check-in management DB 147 associated with the transaction ID specified in the mode change instruction to the training mode state specified in the mode change instruction (step S53).

[0150] In this way, the control unit 100 of the transaction management server 10 sets the transaction mode to a training mode that simulates accounting for goods, in response to instructions from the registration device. In other words, the control unit 100 of the transaction management server 10 functions as an example of a setting means.

[0151] Next, the control unit 100 of the transaction management server 10 reads the transaction data associated with the transaction ID specified in the mode change instruction from the training transaction management DB 149 (step S54). Then, the control unit 100 sends a change completion notification, which includes the transaction data read in step S54 and information notifying the completion of the change to training mode, to the registered terminal that sent the notification (step S55).

[0152] Furthermore, if the check-in instruction includes information instructing a change to training mode, the control unit 100 of the transaction management server 10 changes the mode flag of the issued transaction ID to the training mode state when registering the transaction ID in the check-in management DB 147. The control unit 100 of the transaction management server 10 then sends a check-in completion notification and a change completion notification to the registration device.

[0153] When the control unit 400 of the registration terminal receives a change completion notification from the transaction management server 10, it switches the screen displayed on the display unit 45 to a screen for training mode (step S56). In this way, the control unit 400 of the registration terminal switches the operation of its own terminal and the mode of transactions performed on the terminal to a training mode for simulating accounting for goods, in response to user operations. In other words, the control unit 400 of the registration terminal functions as an example of a switching means.

[0154] Figure 22 shows an example of a purchase support screen displayed on the user terminal 40, and shows an example of purchase support screen A for training mode.

[0155] As shown in Figure 22, the basic screen configuration is the same as the purchase support screen A described in Figure 15, that is, the purchase support screen A for normal mode. However, the difference from the purchase support screen A for normal mode is that the operation mode Aaa displayed in the first display area Aa has been changed to "Training," which means the state during training.

[0156] This allows users of registered terminals to easily confirm that the trading activity on their registered terminal has been changed to training mode by checking the status displayed as "Operating Mode Aaa".

[0157] Furthermore, if product registration was performed in the preceding training mode, information about the product registered in the preceding training mode will be displayed in the third display area Ac based on the transaction data sent in the change completion notification. In other words, while operating in training mode, products registered in training mode are displayed in the third display area Ac. Note that Figure 22 shows a state where the product is not yet registered.

[0158] Furthermore, the number of points and the remaining balance will continue to be displayed in training mode, just as they are in normal mode. In other words, the number of points and the remaining balance are carried over from normal mode to training mode.

[0159] Next, we will describe an example of how a user performing training can switch from training mode to normal mode by operating the user terminal 40 or cart terminal 50.

[0160] When switching from training mode to normal mode, just as when switching to training mode, the user can declare their return to normal mode by operating their registered device.

[0161] Specifically, the control unit 400 of the registration terminal sends a mode change instruction to the transaction management server 10 in response to the user's operation, instructing it to change to normal mode. In response to the mode change instruction from the registration terminal, the transaction management server 10 changes the mode flag of the corresponding transaction to the normal mode state.

[0162] Figure 23 is a sequence diagram showing an example of a mode change process performed by the transaction processing system 1.

[0163] First, when the control unit 400 of the registration terminal receives an instruction to switch to normal mode (step S61), it sends a mode change instruction to the transaction management server 10, which includes the transaction ID stored in RAM or the like, and information instructing the change to normal mode (step S62).

[0164] Here, the method for receiving instructions to change to normal mode can be varied, similar to the method for receiving instructions to change to training mode. For example, a recovery code symbol containing information to instruct the user to switch to normal mode may be prepared, and the user may give the instruction to change to normal mode by having the registered terminal read this code symbol.

[0165] Furthermore, the control unit 46 may accept instructions to switch to normal mode. For example, the control unit 400 of the registered terminal may be configured to accept instructions to switch to normal mode via an operator that can switch between the normal mode and the training mode as described above.

[0166] Meanwhile, when the control unit 100 of the transaction management server 10 receives a mode change instruction from the registration terminal, it changes the mode flag of the check-in management DB 147 associated with the transaction ID specified in the mode change instruction to the normal mode state specified in the mode change instruction (step S63).

[0167] In this way, the control unit 100 of the transaction management server 10 sets the transaction mode to the normal mode, which executes product accounting as usual, in response to instructions from the registration device. In other words, the control unit 100 of the transaction management server 10 functions as an example of a setting means.

[0168] Next, the control unit 100 of the transaction management server 10 reads the transaction data associated with the transaction ID specified in the mode change instruction from the transaction management DB 148 (step S64). Then, the control unit 100 sends a change completion notification, which includes the transaction data read in step S64 and information notifying the completion of the change to training mode, to the registered terminal that sent the notification (step S65).

[0169] When the control unit 400 of the registration terminal receives a change completion notification from the transaction management server 10, it switches the screen displayed on the display unit 45 to the screen for normal mode (step S66).

[0170] For example, the control unit 400 of the registration terminal switches the purchase support screen A shown in Figure 22 back to the purchase support screen A shown in Figure 15, thereby returning the operation mode Aaa displayed in the first display area Aa to the normal mode notation. This allows the user of the registration terminal to easily confirm that the transaction of the registration terminal they are operating has been changed to the normal mode by checking the status displayed in operation mode Aaa.

[0171] Furthermore, if product registration was performed in the preceding normal mode, information regarding the product registered in the preceding normal mode will be displayed in the third display area Ac based on the transaction data transmitted in the change completion notification. In other words, in this embodiment, the registered products displayed in the third display area Ac are configured to switch between normal mode and training mode. Note that the number of points and the charge balance are carried over even when switching from training mode to normal mode.

[0172] In this way, the control unit 400 of the registration terminal switches the operation of the terminal and the mode of transactions performed on the terminal to a normal mode for executing product accounting as usual, in response to user operations. In other words, the control unit 400 of the registration terminal functions as an example of a switching means.

[0173] Next, we will explain an example of the operation when a user possessing a card links their member ID and / or prepaid card ID to the user terminal ID of user terminal 40.

[0174] The control unit 400 of the user terminal 40 performs ID linking processing in cooperation with the transaction management server 10 by sending an ID linking instruction to the transaction management server 10 that includes the user terminal ID of its own terminal and the member ID and / or prepaid card ID of the linked party, in response to the user's operation.

[0175] Furthermore, if the card medium is provided in the form of a magnetic card or the like, it is assumed that the user terminal 40 cannot directly read the card medium. Therefore, the sequence diagram shown in Figure 24 illustrates an example of how information held by the card medium is input to the user terminal 40, specifically when the attendant terminal 30 is used to input the information to the user terminal 40.

[0176] Figure 24 is a sequence diagram showing an example of the ID linking process performed by the transaction processing system 1. It is assumed that the check-in process has already been completed.

[0177] First, the control unit 300 of the attendant terminal 30 reads information from the card medium via the card reader 37 in response to the operator's input (step S71). Next, the control unit 300 encodes the card information read in step S71 into a code symbol (step S72) and displays the generated code symbol on the display unit 35 (step S73). The control unit 300 may also generate a code symbol that includes the store ID of its own store.

[0178] In this case, the user operating the user terminal 40 inputs the card information held in the code symbol into the user terminal 40 by capturing an image of the code symbol displayed on the display unit 35 of the attendant terminal 30 using the imaging unit 47.

[0179] Specifically, the control unit 400 of the user terminal 40 decodes the code symbol captured by the imaging unit 47 to read the card information held in the code symbol (step S74). Next, the control unit 400 sends an ID linkage instruction to the transaction management server 10, which includes the card information read in step S34, the user terminal ID of its own terminal, and the store ID of the store where the check-in is taking place (step S75).

[0180] When the control unit 100 of the transaction management server 10 receives an ID linkage instruction from the user terminal 40, it registers the member ID and prepaid card ID included in the card information in the user management DB 146, associated with the user terminal ID and store ID specified in the ID linkage instruction (step S76). The control unit 100 of the transaction management server 10 also refers to the check-in management DB 147 and registers the member ID and prepaid card ID included in the card information in association with the transaction ID corresponding to the pair of user terminal ID and store ID, thereby reflecting the ID linkage instruction in the check-in management DB 147 (step S77).

[0181] Next, the control unit 100 of the transaction management server 10 reads information (number of points and charge balance) related to the ID (member ID or prepaid card ID) registered in step S76 from the point management DB 144 and the charge balance management DB 145 (step S78). Then, the control unit 100 sends a linkage completion notification to the user terminal 40, which includes information related to the ID registered in step S76 and the ID read in step S78 (step S79).

[0182] Then, the control unit 400 of the user terminal 40 reflects the information regarding the linked ID on the purchase support screen and the member information screen based on the linking completion notification sent from the transaction management server 10 (step S80).

[0183] As a result, after the ID linking process is completed, users can check information about their linked member ID and prepaid card ID on the purchase support screen or member information screen by performing the check-in process again at the store using the user terminal 40 or cart terminal 50.

[0184] Next, we will explain an example of the operation during product registration, in which a user who has completed the check-in process registers products sold in the store as items to be traded (purchased) using the user terminal 40 or cart terminal 50.

[0185] The control unit 400 of the registration terminal, in response to user operations, reads the product ID from the code symbol attached to the product and sends a registration instruction including the product ID to the transaction management server 10, thereby performing product registration processing in cooperation with the transaction management server 10.

[0186] Figure 25 is a sequence diagram showing an example of the product registration process performed by the transaction processing system 1.

[0187] First, the control unit 400 of the registration terminal reads the product ID from the code symbol attached to the product to be purchased in response to the user's operation (step S91). For example, if the registration terminal is a user terminal 40, the control unit 400 detects the code symbol from the image of the product captured by the imaging unit 47 and reads the product ID by decoding the code symbol. Alternatively, if the registration terminal is a shopping cart terminal 50, the control unit 500 works in cooperation with the code reading unit 57 to read the product ID from the code symbol attached to the product.

[0188] Next, the control unit 400 of the registration terminal sends a registration instruction to the transaction management server 10, which includes the product ID read in step S91 and the transaction ID of the transaction in question (step S92).

[0189] The control unit 400 of the registration terminal may include the store ID in the registration instruction when transmitting it. Furthermore, if the registration terminal is operating in training mode, the control unit 400 may be configured to transmit a registration instruction that includes information indicating that it is in training mode.

[0190] When the control unit 100 of the transaction management server 10 receives a registration instruction from a registration terminal, it identifies the store ID from the check-in data in the check-in management DB 147 corresponding to the transaction ID specified in the registration instruction. Next, the control unit 100 reads the product information of the product corresponding to the pair of the identified store ID and the product ID specified in the registration instruction from the store-specific product master 143 (step S93).

[0191] Furthermore, if the registration instruction includes a store ID, the control unit 100 of the transaction management server 10 can read the product information for the corresponding product from the store-specific product master 143 based on the store ID and product ID pair specified in the registration instruction.

[0192] Next, the control unit 100 of the transaction management server 10 checks the mode flag of the check-in management DB 147 corresponding to the transaction ID specified in the registration instruction (step S94) and determines whether the normal mode state is set or not (step S95). If the normal mode state is set (step S95; Yes), the control unit 100 registers the product information read in step S93 in the transaction management DB 148, associating it with the transaction ID and product ID specified in the registration instruction (step S96).

[0193] On the other hand, if the mode flag is set to training mode (step S95; No), the control unit 100 associates the product information read in step S93 with the transaction ID and product ID specified in the registration instruction and registers it in the training transaction management DB 149 (step S97).

[0194] In this way, the control unit 100 of the transaction management server 10 registers the goods related to a transaction specified by the registration device, associating them with the transaction ID of that transaction. In other words, the control unit 100 of the transaction management server 10 functions as an example of the first registration means.

[0195] Furthermore, if the registration instruction includes information indicating the training mode, the control unit 100 of the transaction management server 10 can skip step S94 and determine in step S95 whether or not the training mode is indicated in the registration instruction.

[0196] Next, the control unit 100 of the transaction management server 10 sends the transaction data registered in step S96 or S97 as a registration completion notification to the registration terminal that sent the registration instruction (step S98). Then, the control unit 100 of the transaction management server 10 sets the status of the management data related to the transaction ID of the transaction to "Shopping" (step S99).

[0197] Meanwhile, when the control unit 400 of the registration terminal receives a registration completion notification in response to a registration instruction, it displays the transaction data notified in the registration completion notification on the display unit 45 (step S100). Specifically, as shown in Figure 26, the control unit 400 displays product information of the registered product in the third display area Ac of the purchase support screen A.

[0198] Figure 26 shows an example of a purchase support screen displayed on the user terminal 40. When the control unit 400 of the user terminal 40 receives a registration completion notification from the transaction management server 10 as a response to a registration instruction, it displays information about the registered product in the third display area Ac of the purchase support screen A, based on the transaction data included in the registration completion notification.

[0199] Specifically, the control unit 400 of the user terminal 40 displays information about the registered products in the registered product area Acb of the third display area Ac, in the order in which they were registered. Here, a small rectangular area Acc is provided for each registered product, and within the small area Acc, product information such as the product name and price, as well as the number of registered items, are displayed. Figure 23 shows an example in which three products have been registered.

[0200] Furthermore, the total display area Aca in the third display area Ac displays the total number of items and the total amount of the registered products. The total amount in the total display area Aca may be calculated by the control unit 400 of the user terminal 40 based on the price and number of items of the registered products, or it may be calculated by the transaction management server 10.

[0201] Note that Figure 26 shows the status of a product registered in training mode (see operation mode Aaa), but the display will be the same in normal mode. Also, Figure 26 shows purchase support screen A displayed on the display unit 45 of the user terminal 40 as an example, but the display will be the same in the case of the cart terminal 50.

[0202] Thus, the control unit 400 of the registration terminal functions as an example of a registration means for registering products specified by the user to the transaction management server 10.

[0203] Next, we will explain an example of the accounting process for products registered through the product registration process described above.

[0204] When the control unit 400 of the registration terminal receives an operation on the accounting button Adb, for example, located in the fourth display area Ad of the purchase support screen A, it works in cooperation with the transaction management server 10 and the accounting device 20 to perform processing for accounting of the products registered up to that point.

[0205] By the way, in order to perform accounting with the accounting device 20, it is necessary to input information that can identify the product registered in the product registration process described above, specifically the product ID, into the accounting device 20. Also, in order to perform accounting using the prepaid payment service provided by the store, it is necessary to input information that can identify the destination to which the user's electronic money has been charged, specifically the user's prepaid card ID, into the accounting device 20.

[0206] Therefore, in this embodiment, a transaction ID is output as an example of identifying information that can identify the destination of the electronic money charge and the breakdown or total amount of the registered items to be purchased, and a configuration in which the transaction ID is input to the accounting device 20 is described. Furthermore, in this embodiment, a configuration using a method that does not involve electrical communication is described as an example of a method for inputting the transaction ID etc. to the accounting device 20. Specifically, a configuration in which the transaction ID etc. is encoded into a code symbol and input to the accounting device 20 by having the accounting device 20 read the code symbol is described.

[0207] Figure 27 is a flowchart showing an example of the accounting preparation process performed by the registration terminal. When the control unit 400 of the registration terminal receives an instruction from the user to start accounting by operating the accounting button Adb (step S111), it determines whether the current operating mode is training mode or not (step S112).

[0208] If the operating mode is normal mode (step S112; No), the control unit 400 encodes the transaction ID of the transaction held in RAM 43, etc., into a code symbol (step S113), and proceeds to step S115.

[0209] Furthermore, if the operating mode is training mode (step S112; Yes), the control unit 400 encodes the transaction ID of the transaction and the mode indication information indicating that it is in training mode into a code symbol (step S114), and then proceeds to step S115.

[0210] Next, the control unit 400 displays the code symbol generated in step S113 or step S114 on the display unit 45 (step S115). The user inputs the transaction ID, etc., into the accounting device 20 by having the code reading unit 27 of the accounting device 20 read the code symbol displayed on the registration terminal. The accounting device 20 and the transaction management server 10 execute the accounting process shown in Figure 28 in response to the information input from the registration terminal.

[0211] Thus, when the control unit 400 of the registration terminal receives an operation to start accounting from a user, it outputs a transaction ID, which is an example of specific information, regardless of whether it is in normal mode or training mode, enabling the accounting device 20 that receives the transaction ID to perform accounting using electronic money. In other words, the control unit 400 of the registration terminal functions as an example of an output control means.

[0212] Figure 28 is a sequence diagram showing an example of accounting processing performed by the transaction processing system 1.

[0213] First, the control unit 200 of the accounting device 20 reads information such as the transaction ID held in the code symbol displayed on the registration terminal via the code reading unit 27 (step S121). Next, the control unit 200 sends an instruction to the transaction management server 10 to acquire accounting data containing the read information (step S122).

[0214] When the control unit 100 of the transaction management server 10 receives an instruction to acquire accounting data from the accounting device 20, it performs a transaction determination process to determine whether the transaction with the transaction ID specified in the instruction is a normal transaction or a training transaction (step S123). Next, the control unit 100 transmits accounting data, including transaction data for the transaction corresponding to the determination result, to the accounting device 20 (step S124).

[0215] When the control unit 200 of the accounting device 20 receives accounting data from the transaction management server 10, it performs accounting processing to pay for the registered goods registered in the transaction based on the accounting data (step S125). Then, when the accounting processing is completed, the control unit 200 of the accounting device 20 notifies the transaction management server 10 of the transaction ID of the completed transaction (step S126).

[0216] When the control unit 100 of the transaction management server 10 receives notification from the accounting device 20 that accounting has been completed, it sets the status of the management data related to the transaction ID instructed in the notification to "exit" (step S127).

[0217] Figure 29 is a flowchart showing an example of the transaction determination process performed by the transaction management server 10. This process corresponds to the process in step S123 shown in Figure 28. For the sake of explanation, the process in step S124 shown in Figure 28 will also be included in the explanation, but this does not mean that accounting data is transmitted twice.

[0218] First, when the control unit 100 of the transaction management server 10 receives an instruction to acquire accounting data (step S131), it determines whether the instruction to acquire accounting data includes mode instruction information indicating that it is in training mode (step S132). If the instruction does not include mode instruction information (step S132; No), the control unit 100 reads the transaction data associated with the transaction ID indicated in the instruction to acquire accounting data from the transaction management DB 148 (step S133). Then, the control unit 100 proceeds to step S139.

[0219] On the other hand, if mode instruction information is included (step S132; Yes), the control unit 100 checks the setting of the mode flag in the check-in management DB 147 associated with the transaction ID instructed in the accounting data acquisition instruction (step S134). Next, the control unit 100 determines whether the mode flag is in the training state or not (step S135).

[0220] If the mode flag is set to normal mode (step S135; No), the control unit 100 determines that the operating mode instructed by the accounting device 20 does not match the operating mode managed by the check-in management DB 147. In this case, the control unit 100 sends error information to the accounting device 20 that sent the accounting data acquisition instruction to notify it of the operating mode mismatch (step S136). Next, the control unit 100 sets the status of the management data related to the transaction ID instructed in the accounting data acquisition instruction to "suspended" (step S137) and terminates the process.

[0221] Furthermore, when a registered terminal receives error information, the control unit 400 controls a screen on the display unit 45 that notifies the user that the accounting process has been interrupted due to a mismatch in operating modes.

[0222] Furthermore, if the mode flag is set to training mode in step S135 (step S135; Yes), the control unit 100 determines that the operating mode instructed by the accounting device 20 matches the operating mode managed by the check-in management DB 147. In this case, the control unit 100 reads the transaction data associated with the transaction ID instructed by the accounting data acquisition instruction from the training transaction management DB 149 (step S138), and proceeds to step S139.

[0223] In step S139, the control unit 100 reads the check-in data from the check-in management DB 147 corresponding to the transaction ID specified in the transaction data acquisition instruction (step S139).

[0224] Next, the control unit 100 of the transaction management server 10 reads the corresponding number of points and charge balance from the point management DB 144 and the charge balance management DB 145 based on the store ID, member ID, and prepaid card ID included in the check-in data read in step S139 (step S140). Then, the control unit 100 sends accounting data, including the transaction data read in step S133 or step S138, the check-in data read in step S139, and the number of points and charge balance read in step S140, to the accounting device 20 that sent the instruction to acquire accounting data (step S141).

[0225] In this way, when a transaction ID is specified by the accounting device 20, the control unit 100 of the transaction management server 10 transmits transaction data for products registered in association with the transaction ID, as well as check-in data including the prepaid card ID, to the accounting device 20, thereby enabling accounting using electronic money to be performed on the accounting device 20. Furthermore, if the mode flag of the transaction ID is in training mode, the control unit 100 of the transaction management server 10 transmits accounting data on the condition that mode instruction information indicating training mode is transmitted from the accounting device 20, thereby controlling the accounting performed on the accounting device 20 to be simulated. In other words, the control unit 100 of the transaction management server 10 functions as an example of a transmission control means.

[0226] If the member ID or prepaid card ID is not present in the check-in data, the control unit 100 reads the points or charge balance associated with any existing IDs and includes them in the accounting data before transmission. If neither the member ID nor the prepaid card ID is present in the check-in data, the control unit 100 only needs to transmit accounting data that does not include the points or charge balance. Furthermore, if the control unit 100 is instructed to be in training mode in the accounting data acquisition instruction, it may also transmit information indicating training mode, information indicating the training payment server 70 to be used for accounting, etc., in the accounting data.

[0227] Next, when the transaction management server 10 receives the accounting data, the control unit 100 sets the status of the management data related to the transaction ID specified in the accounting data acquisition instruction to "Accounting in progress" (step S142), and terminates the process.

[0228] In this manner, the transaction management server 10 switches the transaction data registered in each mode and outputs it to the accounting device 20, depending on whether the transaction for which accounting has been instructed is in normal mode or training mode. Furthermore, if the prepaid card ID of the user performing the transaction is registered, the transaction management server 10 outputs the prepaid card ID along with the corresponding charge balance to the accounting device 20, regardless of the operating mode. As a result, the accounting device 20 can perform accounting processing for the products registered in normal mode and training mode, respectively, based on the charge balance associated with the user's prepaid card ID.

[0229] Furthermore, when the transaction management server 10 receives an instruction from the accounting device 20 to acquire accounting data in training mode, it checks whether the mode flag of the corresponding transaction is in training mode, and only sends accounting data if they match. This prevents the transaction processing system 1 from performing accounting processing for training mode when the operating modes do not match, thus enabling more reliable training.

[0230] Figure 30 is a flowchart showing an example of accounting processing performed by the accounting device 20. This processing corresponds to step S125 shown in Figure 28. For the sake of explanation, the process of step S126 shown in Figure 28 will also be included in the explanation, but this does not mean that the accounting completion notification will be sent twice.

[0231] First, the control unit 200 of the accounting device 20 receives accounting data from the transaction management server 10 in response to an instruction to acquire accounting data (step S151). At this time, the control unit 200 may display information such as the breakdown of registered products, total amount, number of points, and charge amount on the display unit 25 based on the transaction data and check-in data included in the accounting data. Furthermore, if the processing in step S152, which will be described later, determines that the device is in training mode, the display unit 25 may display information indicating that the device is operating in training mode.

[0232] Next, the control unit 200 determines whether the transaction is in training mode or not based on the information read in step S121 of Figure 28 or the received accounting data (step S152).

[0233] If it is determined in step S152 that it is in normal mode (step S152; No), the control unit 200 displays a selection screen on the display unit 25 that includes an operator for selecting a payment method that the accounting device 20 can handle (step S153).

[0234] For example, if the accounting data includes a prepaid card ID, the control unit 200 displays a selection screen that includes an operator for selecting prepaid payment. In other words, if the accounting data does not include a prepaid card ID, the control unit 200 may display a selection screen that does not include an operator for selecting prepaid payment.

[0235] Furthermore, for example, if the accounting data includes store setting information and the store-specific setting information specifies a payment method, a selection screen including an operator for selecting the specified payment method may be displayed. However, if only one payment method is specified in the store setting information, the control unit 200 may proceed to step S155 without displaying the selection screen.

[0236] After displaying the selection screen in step S153, the control unit 200 waits until a payment method is selected (step S154; No). Once a payment method is selected (step S154; Yes), the control unit 200 determines whether the selected payment method is a prepaid payment or not (step S155).

[0237] If a payment method other than prepaid payment (for example, cash payment, credit card payment, or other electronic money payment other than prepaid payment) is selected (step S155; No), the control unit 200 performs accounting processing to pay for the goods using the selected payment method (step S156) and proceeds to step S159.

[0238] Furthermore, if it is determined in step S155 that prepaid payment has been selected (step S155; Yes), the control unit 200 sends data including the total amount of goods to be paid, the store ID and prepaid card ID included in the accounting data to the payment server 60, thereby executing accounting processing based on the charge balance (step S157). Then, when the control unit 200 receives a payment completion response from the payment server 60, it proceeds to step S159.

[0239] On the other hand, if the system determines in step S152 that it is in training mode (step S152; Yes), the control unit 200 proceeds to step S158 and simulates the accounting process related to the transaction. Here, for example, it is predetermined that the training content to be performed in training mode is training related to prepaid payments. In this case, the control unit 200 simulates the accounting process based on the charge balance by sending data including the total amount of goods to be paid, the store ID and prepaid card ID included in the accounting data to the training payment server 70 (step S158). Then, when the control unit 200 receives a payment completion response from the training payment server 70, it proceeds to step S159.

[0240] As described above, in the accounting process of step S158, payment is not actually made from the charge balance associated with the prepaid card ID, but rather a simulated prepaid payment is made while maintaining the charge balance. If other payment methods are to be used for training, a selection screen for selecting a payment method may be displayed as in step S154, but the accounting process will be simulated regardless of which payment method is selected. In addition, in configurations that do not use the training payment server 70, the control unit 200 may perform the accounting process based on the charge balance using the accounting device 20 alone.

[0241] In the following step S159, the control unit 200 notifies the transaction management server 10 of the transaction ID of the transaction for which accounting processing has been completed (step S159), and terminates this process.

[0242] Furthermore, if the accounting data includes the user's member ID, the control unit 200 of the accounting device 20 may issue points corresponding to the total amount of goods (payment amount), etc., and perform a point awarding process by adding the issued points to the number of points in the point management DB 144. However, in training mode, it is preferable to configure the system so that point awarding is also performed in a simulated manner.

[0243] Thus, the transaction processing system 1 can conduct training on the entire process from checking in at a store to payment using the actual charged amount. Furthermore, in training mode, the transaction processing system 1 can link the charge balance related to prepaid payments between the registered terminal and the payment device 20, and simulate payment using that charge balance. As a result, the transaction processing system 1 can conduct training that closely matches the actual store environment.

[0244] Furthermore, in the transaction processing system 1, the transaction management DB 148 used for normal transactions and the training transaction management DB used during training are managed separately. Therefore, training can be performed in a realistic environment without affecting the database used for normal transactions. Consequently, training can be performed safely in the transaction processing system 1.

[0245] Next, we will explain the actions performed by the attendant terminal 30 to support the confirmation of transactions that take place or have taken place within the store.

[0246] Figure 31 is a flowchart showing an example of the confirmation support processing performed by the attendant terminal 30. First, when the control unit 300 of the attendant terminal 30 receives an instruction to display the status confirmation screen from the operator (step S171), it proceeds to step S172. In step S172, the control unit 300 displays a status confirmation screen representing the status of each transaction on the display unit 35 based on the check-in management DB 147, transaction management DB 148, and training transaction management DB 149 stored in the transaction management server 10 (step S172).

[0247] Figure 32 shows an example of a status confirmation screen displayed on the attendant terminal 30. The status confirmation screen C has a first display area Ca, a second display area Cb, and an update button Cc.

[0248] The first display area Ca is provided with operators for setting transaction extraction conditions. The first display area Ca is provided with operators that can be used to set extraction conditions related to the number of items to display, such as "All Items," "10 Minutes Ago," and "30 Minutes Ago." Here, "All Items" instructs that all transaction IDs registered in the check-in management DB 147 be included in the extraction. "10 Minutes Ago" instructs that transaction IDs registered in the check-in management DB 147 whose previous operation time falls within the most recent 10 minutes will be included in the extraction. "30 Minutes Ago" instructs that transaction IDs registered in the check-in management DB 147 whose previous operation time falls within the most recent 30 minutes will be included in the extraction. Figure 32 shows an example where the default state, "All Items," is set.

[0249] Furthermore, the first display area Ca is provided with operators (checkboxes) that allow you to set the following extraction conditions related to status: "Entering the store," "Shopping," "Paying," "Leaving the store," "Cancelled," and "Training." "Entering the store" instructs the system to extract transaction IDs registered in the check-in management DB147 whose management data status is "Entering the store." "Shopping" instructs the system to extract transaction IDs registered in the check-in management DB147 whose management data status is "Shopping." "Paying" instructs the system to extract transaction IDs registered in the check-in management DB147 whose management data status is "Paying." "Leaving the store" instructs the system to extract transaction IDs registered in the check-in management DB147 whose management data status is "Leaving the store." "Cancelled" instructs the system to extract transaction IDs registered in the check-in management DB147 whose management data status is "Cancelled." The "Training" option instructs the system to extract transaction IDs registered in the check-in management DB147 whose mode flag status is "Training". Figure 32 shows an example where all checkboxes are checked, which is the default state.

[0250] Furthermore, the first display area Ca includes an input field where the terminal ID (user terminal ID, cart terminal ID) can be specified as an extraction criterion. Note that the input field is blank by default, indicating that no terminal ID has been set.

[0251] The second display area Cb shows the transaction status corresponding to the transaction ID extracted based on the extraction criteria in the first display area Ca. The list displayed in the second display area Cb has one row representing information about each item for one transaction, such as "Terminal ID," "Transaction ID," "Circulation Time," "Previous Operation Time," "Registered Points," "Status," "Accounting Device ID," and "Cancellation Flag."

[0252] The information in the "Terminal ID" field corresponds to the Terminal ID in the Check-in Management DB147. If the mode flag associated with the Terminal ID is set to training status, the mark Cba will be placed to the left of the Terminal ID to indicate this. The information in the "Transaction ID" field corresponds to the Transaction ID in the Check-in Management DB147. The information in the "Roaming Time" field corresponds to the elapsed time from the start time to the current time, as contained in the management data of the Check-in Management DB147. The information in the "Previous Operation Time" field corresponds to the previous operation time, as contained in the management data of the Check-in Management DB147.

[0253] The information in the "Registered Points" field corresponds to the points of the product registered in the Transaction Management DB148 or Training Transaction Management DB149, associated with the corresponding transaction ID. Here, for transaction IDs with a normal mode flag in Check-in Management DB147, the points of the product registered in Transaction Management DB148 are displayed. Also, for transaction IDs with a normal mode flag in Check-in Management DB147, the points of the product registered in Training Transaction Management DB149 are displayed.

[0254] The information in the "Status" field corresponds to the status included in the management data of the check-in management DB147. The information in the "Accounting Device ID" field corresponds to the accounting device ID if it is included in the management data of the check-in management DB147. The information in the "Cancellation Flag" field corresponds to the status of the cancellation flag included in the management data of the check-in management DB147.

[0255] Furthermore, the update button Cc is an operator for receiving instructions to update the filtering conditions. When the attendant terminal 30 receives an operation of the update button Cc, it updates the display in the second display area Cb based on the extraction conditions set in the first display area Ca. Note that the update timing of the second display area Cb is not limited to the timing of the update button Cc operation, but may also be set to update the status confirmation screen at predetermined time intervals (hereinafter also referred to as the update interval).

[0256] Returning to Figure 31, the control unit 300 determines whether it is time to update the status confirmation screen C (step S173). Specifically, the control unit 300 determines whether it has taken over the operation of the update button Cc or whether the update interval has been reached. If it is determined that it is time to update (step S173; Yes), the control unit 300 updates the transaction status displayed in the second display area Cb to the latest state based on the extraction conditions set in the first display area Ca (step S174), and returns to the process of step S172. As a result, the latest transaction status is displayed on the status confirmation screen C.

[0257] Furthermore, if it is determined in step S173 that it is not time to update (step S173; No), the control unit 300 determines whether or not one of the transactions displayed in the second display area Cb has been selected (step S175). If it is determined that a transaction has been selected (step S175; Yes), the display unit 35 displays a registered product confirmation screen to check the details of the products registered in the selected transaction (step S176).

[0258] Figure 33 shows an example of a registered product confirmation screen displayed on the attendant terminal 30. The registered product confirmation screen D is displayed, for example, superimposed on the status confirmation screen C. The registered product confirmation screen D has a product display area Da and a back button Db.

[0259] The product display area Da shows the product name, quantity, price, etc., of the products registered in association with the transaction ID selected in the second display area Cb of the status confirmation screen C, in the order they were registered. Specifically, if the mode flag of the selected transaction ID is "normal transaction," the product of the corresponding transaction ID registered in the transaction management DB148 will be displayed in the product display area Da. If the mode flag of the selected transaction ID is "training," the product of the corresponding transaction ID registered in the training transaction management DB149 will be displayed in the product display area Da.

[0260] Furthermore, the back button Db is an operator used to return to the status confirmation screen C. When the attendant terminal 30 receives an operation on the back button Db, it clears the registered product confirmation screen D and displays the status confirmation screen C.

[0261] Returning to Figure 31, the control unit 300 determines whether or not it has been instructed to return the display to the status confirmation screen (step S177). If it has not been instructed to return the display (step S177; No), the control unit 300 returns to step S176, thereby continuing to display the registered product confirmation screen. The control unit 300 may also update the display of the registered product confirmation screen at each update interval.

[0262] Furthermore, if instructed to return to the status confirmation screen (step S177; Yes), the control unit 300 returns to step S172 to display the status confirmation screen (step S172).

[0263] Furthermore, if no transaction is selected in step S175 (step S175; No), the control unit 300 determines whether or not the status confirmation screen has been instructed to be terminated (step S178). If termination is not instructed (step S178; No), the control unit 300 returns to step S172 to continue displaying the status confirmation screen. On the other hand, if termination is instructed (step S178; Yes), the control unit 300 clears the status confirmation screen and terminates the process.

[0264] Operators and others monitoring transactions can easily check the status of transactions taking place in stores, or transactions that have taken place in stores, by viewing the status confirmation screen and the registered product confirmation screen. For example, if employee training is being conducted in a store, the supervisor overseeing the training can easily check the status of the training by viewing the status confirmation screen and the registered product confirmation screen.

[0265] In this embodiment, the attendant terminal 30 is described as displaying the status confirmation screen and the registered product confirmation screen. However, a device other than the attendant terminal 30 may also display the status confirmation screen and the registered product confirmation screen. For example, a store employee's terminal may display the status confirmation screen and the registered product confirmation screen.

[0266] As described above, the registration terminal according to this embodiment registers the products specified by the user with the transaction management server 10, and obtains a transaction ID from the transaction management server 10 that can identify the destination of the electronic money charged by the user. Furthermore, the registration terminal switches between normal mode and training mode in response to the user's operation, and when it receives an operation from the user to start accounting, it outputs a transaction ID regardless of whether it is in normal mode or training mode, thereby controlling the accounting device 20 to enable accounting using electronic money when the transaction ID is input.

[0267] Thus, even in training mode, the registration terminal can input the destination of the electronic money charged by the user to the accounting device 20, just as in normal mode. Therefore, since the registration terminal can perform training in conjunction with the accounting device 20, just as in normal mode, training that is tailored to the actual environment of the store can be realized.

[0268] Furthermore, when training mode is set, the registration terminal outputs mode instruction information along with the transaction ID, thereby causing the accounting device 20, which receives this mode instruction information, to operate in training mode. As a result, the accounting device 20 can switch to training mode without the user having to manually instruct it to do so. Therefore, the transaction processing system 1 can efficiently conduct training in cooperation with the registration terminal and the accounting device 20.

[0269] The embodiments described above can also be modified and implemented as appropriate by changing some of the configurations or functions of each of the devices described above. Therefore, several modifications of the embodiments described above will be described below as other embodiments. In the following, we will mainly describe the differences from the embodiments described above, and will omit detailed explanations of points that are common with what has already been described. Furthermore, the modifications described below may be implemented individually or in combination as appropriate.

[0270] (Variation 1) In the above embodiment, the product registration destinations are managed separately in the transaction management DB 148 and the training transaction management DB 149 for normal mode and training mode. However, the system is not limited to this configuration, and products may be registered in the same registration destination (transaction management DB 148) for both normal mode and training mode.

[0271] In addition, in the above-described embodiment, when switching between the normal mode and the training mode, the products registered in the mode before the switch are held, and when the same mode is set again, the registered products are read out and product registration or accounting is continued. However, the present invention is not limited to this configuration. For example, when switching between the normal mode and the training mode, the products registered in the mode before the switch may be deleted.

[0272] (Modification Example 2) In the above-described embodiment, the form of performing accounting processing using the accounting device 20 has been described. However, the present invention is not limited to this, and the accounting processing may be performed by the user terminal 40 or the cart terminal 50. In this case, the registration terminal also functions as an accounting device, and the same processing as that of the accounting device may be performed. In this case, within the registration terminal (accounting device), output and input of specific information are performed.

[0273] (Modification Example 3) In the above-described embodiment, the form of using a code symbol to transmit the transaction ID from the registration terminal to the accounting device 20 has been described. However, the present invention is not limited to this form, and it may be transmitted by electrical communication. For example, when the registration terminal and the accounting device 20 are configured to be capable of performing short-range wireless communication, the registration device may output specific information to the accounting device 20 by short-range wireless communication. Further, for example, the registration terminal may output specific information to the accounting device 20 via the network N.

[0274] (Modification Example 4) In the above-described embodiment, an example of using the transaction ID as specific information capable of specifying the recharge destination of the electronic money has been shown. However, the present invention is not limited thereto.

[0275] For example, the registration terminal may output terminal IDs (user terminal ID, cart terminal ID) that can trace the transaction ID as specific information in the check-in management DB147 and transaction management DB148, in the form of a code symbol or the like. Alternatively, the registration terminal may output the user's prepaid card ID obtained from the transaction management server 10 as specific information, in the form of a code symbol or the like.

[0276] Furthermore, for example, the registration terminal may obtain check-in data and transaction data corresponding to the transaction ID from the transaction management server 10, and output this data as identifying information in the form of a code symbol or the like.

[0277] (Variation 5) In the above embodiment, the transaction management server 10 is configured to manage the number of points and the charge balance. However, the configuration is not limited to this, and other server devices different from the transaction management server 10 (hereinafter also referred to as external servers) may be configured to manage the number of points and the charge balance.

[0278] In this case, the external server manages the number of points and charge balance for each user on a store-by-store basis, for example, using the point management DB144 and charge balance management DB145 mentioned above. The external server is also configured to receive inquiries from the transaction management server 10 or accounting device 20 that specify the store ID along with the member ID and / or prepaid card ID, and then return the number of points and charge balance corresponding to the specified pair to the source of the inquiry.

[0279] As a result, in the transaction processing system 1 according to this modified example, the transaction management server 10 does not need to manage each user's member ID and prepaid card ID, and the same effects as in the embodiment described above can be achieved.

[0280] Furthermore, the external servers may consist of different server devices for the points service and the prepaid payment service. For example, the payment server 60 (training payment server 70) may be configured to manage the charge balance. Also, the external servers may consist of different server devices for each store.

[0281] The programs executed in each of the above-described embodiments are provided pre-installed in ROM, storage units, etc. Alternatively, the programs executed in each of the above-described embodiments may be provided as installable or executable files recorded on a computer-readable recording medium such as a CD-ROM, flexible disk (FD), CD-R, or DVD (Digital Versatile Disk).

[0282] Furthermore, the programs executed by each of the above-described embodiments may be stored on a computer connected to a network such as the Internet and provided by being downloaded via the network. Alternatively, the programs executed by each of the above-described embodiments may be provided or distributed via a network such as the Internet.

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

[0284] 1. Transaction Processing System 10 Transaction Management Server 20 Accounting device 30 Attendant terminals 40 User terminals 50 Cart Terminals 60 Payment Servers 70 Training Payment Server 100 Control Unit 200 Control Unit 300 Control Unit 400 Control Unit 500 Control Unit [Prior art documents] [Patent Documents]

[0285] [Patent Document 1] Japanese Patent Publication No. 2018-85031

Claims

1. A movable information processing device that is operated by a user within the store, A registration means for registering products specified by the aforementioned user operation, A means for obtaining specific information that can identify the destination of the electronic money charged by the user, A switching means that switches between a first mode for executing accounting for the registered product and a second mode for simulating accounting for the registered product, in response to the user's operation. When the user initiates the accounting process, the output control means outputs the specified information in either the first mode or the second mode, thereby enabling the accounting device receiving the specified information to perform accounting using the electronic money. An information processing device equipped with the following features.

2. The output control means, when it receives the operation to start accounting, outputs instruction information indicating the second mode along with the specific information, thereby causing the accounting device that receives the instruction information to operate in the second mode. The information processing apparatus according to claim 1.

3. The output control means encodes the output into a code symbol and displays it. The information processing apparatus according to claim 1 or 2.

4. A server device connected to a mobile information processing device that is operated by a user within the store and to an accounting device, A first registration means that registers a product related to a transaction specified by the information processing device, associating it with a transaction identifier that can identify the transaction, A second registration means for registering the destination of the electronic money charged by the user of the information processing device in association with the transaction identifier, A setting means that sets either a first mode for performing accounting for the goods or a second mode for simulating accounting for the goods to the transaction identifier in response to instructions from the information processing device, When a transaction identifier is specified from the accounting device, a transmission control means transmits the registered product associated with the transaction identifier and the charge destination to the accounting device, thereby enabling the accounting device to perform accounting using the electronic money. Equipped with, The transmission control means controls the accounting performed by the accounting device to be simulated when the second mode is set for the transaction identifier specified by the accounting device. Server device.

5. The transmission control means, when the second mode is set for the transaction identifier specified by the accounting device, transmits the goods registered in association with the specified transaction identifier and the charge destination, provided that the accounting device is operating in the second mode. The server device according to claim 4.

6. The first registration means switches the registration destination of the product between the first mode and the second mode set in the transaction identifier, The transmission control means switches the products subject to accounting according to the first mode and the second mode set in the transaction identifier and transmits them to the accounting device. The server device according to claim 4 or 5.

Images