Server device and transaction processing system

Abstract

To provide a server device and a transaction processing system that can improve the convenience of electronic payments made in a shop.SOLUTION: A server device which can communicate with a terminal device operated by a customer visiting a shop includes: first reception means for accepting input of a one-time code related to the use of an electronic payment service from the terminal device; acquisition means for transmitting the one-time code accepted by the first reception means to a payment server that authenticates a user of the electronic payment service based on the one-time code and acquiring user information on the user related to the one-time code from the payment server; and transmission means for transmitting the user information acquired by the acquisition means to the terminal device.SELECTED DRAWING: Figure 20

Description

Technical Field

[0001] Embodiments of the present invention relate to a server device and a transaction processing system.

Background Art

[0002] In a storefront of a store 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 himself / herself to input (also referred to as register) data related to the product to be purchased.

[0003] In addition, in a store, an accounting device for accounting for products input by the above system may be provided. Conventionally, a technique for transmitting accounting data from a mobile terminal to an accounting device has been proposed.

[0004] In addition, some stores provide a prepaid payment service as one of the payment methods. For example, a prepaid account is held in a card medium such as a membership card, and by using the card medium, electronic money recharge and prepaid payment are performed by a device in the store.

[0005] By the way, recently, in order to improve the security related to electronic money, an authentication method using a one-time code may be used. However, in the conventional configuration using the above card medium, it is not possible to support the authentication method using a one-time code, and there is room for improvement in terms of convenience and security.

Summary of the Invention

Problems to be Solved by the Invention

[0006] The problem to be solved by the embodiments of the present invention is to provide a server device and a transaction processing system capable of improving the convenience related to electronic settlement performed in a store.

Means for Solving the Problems

[0007] The server device according to the embodiment is a server device capable of communicating with a terminal device operated by a customer who has visited a store, and includes a first reception unit that receives an input of a one-time code related to the use of an electronic payment service from the terminal device, and a payment server that authenticates a user of the electronic payment service based on the one-time code. A transmission unit that transmits the one-time code received by the first reception unit to the server and acquires user information of the user related to the one-time code from the payment server; and a transmission unit that transmits the user information acquired by the acquisition unit to the terminal device.

Brief Description of Drawings

[0008]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

Figure 22

Figure 23

Figure 24

Figure 25

Figure 26

Figure 27

Figure 28

Figure 29

Figure 30

Figure 31

Figure 32

Figure 33

Figure 34

Figure 35

Figure 36

[0009] Hereinafter, embodiments of the server device and the transaction processing system will be described in detail with reference to the accompanying drawings. In this embodiment, when a customer purchases a product at a sales floor where the products are displayed, the customer operates a mobile terminal to input data related to the purchased product and performs accounting by himself / herself using an accounting machine. An example of a transaction processing system is illustrated. Note that the embodiment described below is an embodiment of a transaction processing device and a program, and does not limit the configuration, specifications, and the like thereof.

[0010] FIG. 1 is a diagram showing a schematic configuration of a transaction processing system 1 according to an embodiment. The transaction processing system 1 includes a server device 10, an accounting device 20, an attendant terminal 30, a user terminal 40, a cart terminal 50, and a payment server 60. The accounting device 20, the attendant terminal 30, the user terminal 40, the cart terminal 50, and the payment server 60 are configured to be communicable with the server device 10 via a network N.

[0011] The network N can be used alone or in an appropriate combination, such as the Internet, a VPN (virtual private network), a LAN (local area network), a public communication network, a mobile communication network, etc. As an example, the Internet and a mobile communication network are used in combination as the network N. Note that the server device 10, the accounting device 20, the attendant terminal 30, the user terminal 40, the cart terminal 50, and the payment server 60 may each be included in the transaction processing system 1 in any number, but only one of each is shown in FIG. 1.

[0012] The server device 10 is an example of a server device. The server device 10 uses the user terminal 40 and the cart terminal 50 as user interface terminals, and performs information processing for providing a transaction processing service that processes a merchandise buying and selling transaction according to an operation by a user at a store where the user interface terminal is used. That is, typically, a customer who purchases merchandise at a store becomes a user of the transaction processing service.

[0013] The server device 10 is realized as, for example, a cloud server and provides a transaction processing service at a plurality of stores. Note that the server device 10 may be realized as, for example, a local server and may be configured to provide a transaction processing service at only one store.

[0014] The accounting device 20 is installed in the store and executes accounting processing related to the accounting of transactions processed by the server device 10. The accounting device 20 receives operations by an operator during the accounting processing. That is, the accounting device 20 is a terminal device that receives operations by users related to accounting. The operator of the accounting device 20 is mainly a user of the store. Note that in some cases, a store clerk may be the operator of the accounting device 20.

[0015] The attendant terminal 30 is an information processing terminal operated by, for example, a store clerk. The attendant terminal 30 is a terminal device for a user interface related to information processing for supporting the work of the store clerk regarding transactions processed by the transaction processing system 1. Note that in this embodiment, the attendant terminal 30 is used for the cooperation of the prepaid ID described later.

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

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

[0018] The settlement server 60 is an example of a settlement server. It is a server device that performs electronic settlement based on data transmitted from the accounting device 20 or the like. Specifically, the settlement server 60 performs prepaid settlement using the balance of electronic money (hereinafter also referred to as the charge balance) prepaid by a user who uses the transaction processing service.

[0019] The settlement server 60 manages by associating the user identification information (hereinafter also referred to as the prepaid card ID) of the user related to the prepaid settlement service at each store with the charge balance that the user has deposited (hereinafter also referred to as charging) into the prepaid settlement service. Here, the prepaid card ID is information for identifying and managing the user who uses the prepaid settlement service. In addition, the settlement server 60 authenticates the user (prepaid card ID) of the prepaid settlement service based on a one-time code (also referred to as a one-time password or one-time key).

[0020] Here, the one-time code is a password that is issued (generated) at regular intervals such as every several tens of seconds to several minutes, and can only be used within this fixed time. The settlement server 60 generates a unique one-time code for each prepaid card ID. In other words, the one-time code is generated corresponding to the prepaid card ID and is also used as information for identifying the prepaid card ID. In addition, the one-time code is provided to the user corresponding to the prepaid card ID by various methods. The settlement server 60 authenticates the user based on the one-time code notified via the server device 10 or the like.

[0021] Next, the hardware configuration of each of the above-described devices will be described.

[0022] FIG. 2 is a diagram showing an example of the hardware configuration of the server device 10. As shown in FIG. 2, the server device 10 includes a CPU (Central Processing Unit) 11, a ROM (Read Only Memory) 12, a RAM (Random Access Memory) 13, a storage unit 14, a communication unit 15, and the like.

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

[0024] The CPU 11, ROM 12, and RAM 13 are connected via a bus or the like and constitute a control unit 100 of a computer configuration. The control unit 100 functions as an example of a first reception means, acquisition means, transmission means, management means, second reception means, reception means, second transmission means, etc. when the CPU 11 operates according to a program (such as the server device program 141) stored in the ROM 12 or the storage unit 14 and expanded in the RAM 13.

[0025] The storage unit 14 has a storage medium such as an HDD (Hard Disk Drive) or a flash memory and maintains the stored content even when the power is turned off. The storage unit 14 stores a server device program 141 that can be executed by the CPU 11 and various setting information. Here, the server device program 141 is a program in which procedures for causing the CPU 11 of the server device 10 to execute various processes are described. The CPU 11 executes various processes described later by cooperating with the server device program 141.

[0026] Also, the storage unit 14 stores a store management DB 142, a store-specific product master 143, a point management DB 144, a user management DB 145, a check-in management DB 146, a transaction management DB 147, and the like.

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

[0028] The point management DB 144 is a database for managing users of the point service provided at each store. Such a point service grants points corresponding to the purchase amount, etc. to users who have registered as members at the store, and provides various benefits according to the accumulated points. Also, in the point service, a member ID is issued for each member, and the number of points assigned in association with the member ID is managed. That is, the member ID is information for identifying and managing users who use the point service.

[0029] The user management DB 145 is a database for managing users who use the transaction processing service. The check-in management DB 146 is a database for managing users who have checked in at each store. The transaction management DB 147 is a database for managing the products purchased by users who have checked in at the store as purchase targets in a single transaction.

[0030] The communication unit 15 is a wired or wireless communication interface connectable to the network N. The communication unit 15 communicates with external devices such as the accounting device 20 via the network N.

[0031] FIG. 3 is a diagram showing an example of the data configuration of the store management DB 142. As shown in FIG. 3, the store management DB 142 stores the company ID, the store ID, and the store information in association with each other. The company ID is identification information for identifying the company that operates the stores using the transaction processing system 1. The store ID is identification information for identifying each store that provides the transaction processing service by the server device 10. Also, when a plurality of stores in one company are using the transaction processing system 1, a plurality of store IDs are associated with the company ID.

[0032] Store information stores information related to the store. For example, information such as the store name is registered in the store information. Also, store setting information for each store defined by the store is registered in the store information. For example, in the store setting information, settings for enabling or disabling functions that can be executed on the user terminal 40 and the cart terminal 50 used in each store are registered. Note that the functions subject to the enable / disable settings may be functions realized by the hardware configuration of the user terminal 40 and the cart terminal 50, or may be functions realized by programs (user terminal program 441 and cart terminal program 541 described later) introduced into the user terminal 40 and the cart terminal 50. Also, for example, the number of times of transmitting insufficient balance information described later may be registered in the store setting information. Note that the store setting information may be blank.

[0033] FIG. 4 is a diagram showing an example of the data configuration of the store-specific product master 143. As shown in FIG. 4, the store-specific product master 143 stores the company ID, the store ID, the product ID, and the product information in association with each other. The company ID is identification information for identifying the company that operates the stores using the transaction processing system 1, and corresponds to the company ID in the store management DB 142. The store ID is identification information for identifying each of the stores that provide the transaction processing service by the server device 10, and corresponds to the store ID in the store management DB 142. The product ID is identification information for identifying the products sold in the store corresponding to the store ID. Since generally there are a plurality of products sold in a store, a plurality of product IDs are registered in association with the store ID. The product information is information related to the product corresponding to the product ID. For example, the product name, price, etc. are registered in the product information. Note that in the case where the types and prices of the products sold are common in a plurality of stores operated by one company, a configuration that does not use the store ID may be adopted by leaving the store ID blank or the like.

[0034] FIG. 5 is a diagram showing an example of the data configuration of the point management DB 144. As shown in FIG. 5, the point management DB 144 stores information in association with a company ID, a store ID, a member ID, and the number of points. The company ID is identification information for identifying a company that operates stores using the transaction processing system 1, and corresponds to the company ID in the store management DB 142. The store ID is identification information for identifying each store that provides a point service, and corresponds to the store ID in the store management DB 142. The member ID is identification information for identifying a member of the point service provided at the store corresponding to the store ID. Generally, since the number of members of the point service is plural, a plurality of member IDs are registered in association with the store ID. The number of points is the cumulative value of the points given to the user corresponding to the member ID.

[0035] When points are given to a user at the corresponding store, the point management DB 144 is configured such that the given number of points is added to the number of points associated with the member ID of the user. Also, when a user uses points at the corresponding store, the point management DB 144 is configured such that the used number of points is subtracted from the number of points associated with the member ID of the user. Note that when a common member ID is applied to a plurality of stores operated by one company, the store ID may be left blank or the like so that the store ID is not used.

[0036] FIG. 6 is a diagram showing an example of the data configuration of the user management DB 145. As shown in FIG. 6, the user management DB 145 stores information in association with a user terminal ID, user information, and store-specific information. The user terminal ID is identification information for identifying each of the user terminals 40. In this embodiment, the user terminal ID of the user terminal 40 held by the user is used as information for identifying the user, but it is not limited to this. For example, instead of the user terminal ID, an ID of the user himself / herself or an account (or user ID of the application) issued to an application such as a user terminal program installed and operating on the user terminal 40 may be used as information for identifying the user.

[0037] User information stores information about the user. For example, the user's name and the like are registered in the user information. Also, for each-store information, information about the user at each store used by the user is registered. Specifically, the per-store information has items such as a company ID, a store ID, a member ID, and store setting information. The company ID is identification information for identifying the company that operates the store using the transaction processing system 1 and corresponds to the company ID in the store management DB 142. The store ID is identification information for the store used by the user and corresponds to the store ID in the store management DB 142. The member ID is identification information for identifying a member of the point service provided at the store used by the user and corresponds to the member ID in the point management DB 144.

[0038] In the present embodiment, since a form in which a unique point service is provided for each store is assumed, different member IDs are registered for each store ID. When using a common member ID for a plurality of stores, the same member ID may be registered in association with the store ID of the store. Also, in the case of using a common member ID in a plurality of stores operated by one company, the store ID may be left blank or the like so that the store ID is not used. Also, the member ID may be blank, for example, it may be in a form in which the member ID is registered by the ID linking process described later.

[0039] User setting information stores setting information for each store defined by the user. For example, a character string (password) for authentication when using the member ID is registered in the user setting information. Also, for example, the payment method (e.g., prepaid payment) used at each store and the like are registered in the user setting information. Also, for example, the number of times of sending the balance shortage information described later may be registered in the user setting information. Note that the user setting information may be blank.

[0040] FIG. 7 is a diagram showing an example of the data configuration of the check-in management DB 146. As shown in FIG. 7, the check-in management DB 146 stores by associating a transaction ID, a company ID, a store ID, a terminal ID, a check-in date and time, a member ID, a prepaid card ID, and a notification flag. The transaction ID is identification information for identifying a user who has checked in (visited) a store. Further, the transaction ID also functions as identification information for identifying each transaction performed in the transaction processing service by the server device 10.

[0041] The company ID is identification information for identifying a company that operates the store where the user has checked in, and corresponds to the company ID in the store management DB 142. The store ID is identification information for identifying the store where the user has checked in, and corresponds to the store ID in the store management DB 142. The terminal ID is identification information for identifying the terminal used by the user who has checked in. For example, when the user uses the user terminal 40, the user terminal ID of the user terminal 40 is registered in the item of the terminal ID. Further, for example, when the user uses the cart terminal 50, identification information (hereinafter, cart terminal ID) capable of identifying each of the cart terminals 50 is registered in the item of the terminal ID. The check-in date and time is date and time information indicating the date and time when the user has checked in at the store.

[0042] In the item of the member ID, the member ID of the user who has checked in at the store is registered. Further, in the item of the prepaid card ID, the prepaid card ID of the user who has checked in at the store is registered. Note that when either one or both of the member ID and the prepaid card ID are not registered, the corresponding item becomes a blank. The notification flag is flag information for limiting the number of notifications performed when the total amount of products registered in one transaction exceeds the recharge amount of the prepaid payment. For the notification flag, for example, information (on, off) for identifying whether or not the notification has been made is registered. Note that the initial state of the notification flag is set to "off" indicating unnotified.

[0043] Hereinafter, among the various types of information registered in the check-in management DB 146 in association with the transaction ID, the information excluding the notification flag is also referred to as check-in data. The check-in data may also include information other than the above-described information. For example, the check-in data may include user information corresponding to the store ID, store setting information, and user setting information corresponding to a set of the store ID and the terminal ID.

[0044] FIG. 8 is a diagram showing an example of the data configuration of the transaction management DB 147. As shown in FIG. 8, the transaction management DB 147 stores the transaction ID, the product ID, the registration date and time, and the product information in association with each other. The transaction ID is identification information for identifying each transaction performed in the transaction processing service by the server device 10 and corresponds to the transaction ID of the check-in management DB 146.

[0045] The product ID is identification information of a product registered as a purchase target in a transaction corresponding to the transaction ID and corresponds to the product ID of the store-specific product master 143. When a plurality of products are registered, a plurality of product IDs are registered in association with the transaction ID. The registration date and time is date and time information indicating the date and time when the product ID was registered. The product information is product information of the product corresponding to the product ID.

[0046] In addition, the transaction management DB 147 may store other information in association with the transaction ID. For example, the transaction management DB 147 may be configured to hold the total amount of the products registered in association with the transaction ID in association with the transaction ID. Further, when a plurality of the same product IDs are registered for the same transaction ID, the transaction management DB 147 may be configured to combine the product IDs into one and register the number of the duplicate product IDs in association therewith.

[0047] FIG. 9 is a diagram showing an example of the hardware configuration of the accounting device 20. As shown in FIG. 9, the accounting device 20 includes a CPU 21, a ROM 22, a RAM 23, a storage unit 24, a display unit 25, an operation unit 26, a code reading unit 27, and a communication unit 28, and the like.

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

[0049] The CPU 21, ROM 22, and RAM 23 are connected via a bus or the like and constitute a control unit 200 of a computer configuration. In the control unit 200, the CPU 21 operates according to a program (such as the accounting device program 241) stored in the ROM 22 or the storage unit 24 and expanded in the RAM 23, thereby realizing various functions.

[0050] The storage unit 24 has a storage medium such as an HDD or a flash memory and maintains the stored content even when the power is turned off. The storage unit 24 stores the accounting device program 241 that can be executed by the CPU 21 and various setting information. Here, the accounting device program 241 is a program in which procedures and the like for causing the CPU 21 of the accounting device 20 to execute various processes related to the transaction processing service are described. The CPU 21 executes various processes described later by cooperating with the accounting device program 241.

[0051] 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 input via the input device to the CPU 21. Note that the operation unit 26 may be a touch panel provided on the display unit 25.

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

[0053] 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 server device 10 via the network N.

[0054] FIG. 10 is a diagram showing an example of the hardware configuration of the attendant terminal 30. As shown in FIG. 10, the attendant terminal 30 includes a CPU 31, a ROM 32, a RAM 33, a storage unit 34, a display unit 35, an operation unit 36, a card reader 37, and a communication unit 38, etc.

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

[0056] The CPU 31, the ROM 32, and the RAM 33 are connected via a bus or the like and constitute a control unit 300 of a computer configuration. In the control unit 300, various functions are realized by the CPU 31 operating according to programs (such as the attendant terminal program 341) stored in the ROM 32 or the storage unit 34 and expanded in the RAM 33.

[0057] The storage unit 34 has a storage medium such as an HDD or a flash memory and maintains the stored content even when the power is turned off. The storage unit 34 stores an attendant terminal program 341 that can be executed by the CPU 31 and various setting information. Here, the attendant terminal program 341 is a program in which procedures for causing the CPU 31 of the attendant terminal 30 to execute various processes related to the transaction processing service are described. The CPU 31 executes various processes described later by cooperating with the attendant terminal program 341.

[0058] The display unit 35 is a display device such as an LCD. Under the control of the CPU 31, the display unit 35 displays various kinds of information. The operation unit 36 is an input device such as a keyboard or a pointing device. The operation unit 36 outputs the operation content input via the input device to the CPU 31. Note that the operation unit 36 may be a touch panel provided on the display unit 35.

[0059] The card reader unit 37 is a reading device capable of reading information from a card medium. The specification of the card reader unit 37 is not particularly limited and can be changed according to the card medium used in the store. For example, in a store that uses a magnetic card as the card medium, a card reader unit 37 capable of reading a magnetic card can be used. Also, for example, in a store that uses a card with a code symbol attached as the card medium, a card reader unit 37 capable of reading the code symbol attached to the card can be used. Further, in a store that uses a card with a wireless tag attached as the card medium, a card reader unit 37 capable of reading the wireless tag can be used.

[0060] The communication unit 38 is a wired or wireless communication interface connectable to the network N. The communication unit 38 communicates with an external device such as the server device 10 via the network N.

[0061] Note that the attendant terminal 30 may be provided with a code reader unit similar to the code reader unit 27 described above. In this case, the attendant terminal 30 may be configured to read the user's membership ID and prepaid card ID from the code symbol displayed and output by the store application program introduced into the user's mobile terminal by using the code reader unit.

[0062] FIG. 11 is a diagram showing an example of the hardware configuration of the user terminal 40. As shown in FIG. 11, the user terminal 40 includes a CPU 41, a ROM 42, a RAM 43, a storage unit 44, a display unit 45, an operation unit 46, an imaging unit 47, and a communication unit 48, etc.

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

[0064] The CPU 41, ROM 42, and RAM 43 are connected via a bus or the like and constitute a control unit 400 of a 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 the storage unit 44 and expanded in the RAM 43, thereby functioning as an example of a reception unit and a first transmission unit, etc.

[0065] The storage unit 44 has a storage medium such as an HDD or a flash memory and maintains the stored content even when the power is turned off. The storage unit 44 stores a user terminal program 441 that can be executed by the CPU 41 and various setting information. Here, the user terminal program 441 is a program in which procedures for causing the CPU 41 of the user terminal 40 to execute various processes related to the transaction processing service are described. For example, the user terminal program 441 includes a dedicated application program related to the use of the transaction processing system 1 (hereinafter also referred to as an application program for stores). The CPU 41 executes various processes described later by cooperating with the application program for stores.

[0066] Note that the application program for stores may be prepared for each store, for example. In this case, by starting the application program for the store at the store where the user has checked in, it becomes possible to perform operations such as registering products and linking prepaid IDs at the store where the user has checked in.

[0067] 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. Note that the operation unit 46 may be a touch panel provided on the display unit 45.

[0068] The imaging unit 47 is a digital camera having an imaging element such as a CCD (Charge Coupled Device) or a CMOS (Complementary MOS), and acquires an image by imaging. In this embodiment, the imaging unit 47 is used for reading a code symbol attached to a product, a check-in detection code symbol displayed at an entrance of a store, a code symbol displayed on the attendant terminal 30, etc.

[0069] The communication unit 48 is a wired or wireless communication interface connectable to the network N. The communication unit 48 communicates with external devices such as the server device 10 and the payment server 60 via the network N.

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

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

[0072] The CPU 51, the ROM 52, and the RAM 53 are connected via a bus or the like and constitute a control unit 500 of a computer configuration. In the control unit 500, the CPU 51 operates according to a program (such as the cart terminal program 541) stored in the ROM 52 or the storage unit 54 and developed in the RAM 53, thereby functioning as an example of a reception means and a first transmission means, etc.

[0073] The storage unit 54 has a storage medium such as an HDD or a flash memory, and maintains the stored content even when the power is turned off. The storage unit 54 stores a cart terminal program 541 that can be executed by the CPU 51 and various setting information. Here, the cart terminal program 541 is a program in which procedures for causing the CPU 51 of the cart terminal 50 to execute various processes related to the transaction processing service are described. The user terminal program 441 is, for example, an application program for a store. The CPU 51 executes various processes described later by cooperating with the cart terminal program 541.

[0074] 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. Note that the operation unit 56 may be a touch panel provided on the display unit 55.

[0075] The code reading unit 57 is a reading device capable of reading the same code symbol as the code reading unit 27. The card reading unit 58 is a reading device capable of reading information from the same card medium as the card reading unit 37. In this embodiment, the code reading unit 27 is used to read the code symbol attached to the product. The card reading unit 58 is used to read the above-described card medium.

[0076] Note that in the case of a configuration in which the member ID of the user is managed by the application program of the store introduced into the user's mobile terminal, the code reading unit 57 may read the member ID or the like from the code symbol displayed and output by the application program.

[0077] The communication unit 59 is a wired or wireless communication interface connectable to the network N. The communication unit 59 communicates with an external device such as the server device 10 via the network N.

[0078] FIG. 13 is a diagram showing an example of the hardware configuration of the settlement server 60. As shown in FIG. 13, the settlement server 60 includes a CPU 61, a ROM 62, a RAM 63, a storage unit 64, a communication unit 65, and the like.

[0079] The CPU 61 is an example of a processor and comprehensively controls the operation of the settlement server 60. The ROM 62 stores various programs. The RAM 63 is a workspace for expanding programs and various data.

[0080] The CPU 61, the ROM 62, and the RAM 63 are connected via a bus or the like and constitute a control unit 600 of a computer configuration. In the control unit 600, the CPU 61 operates according to a program (such as a settlement server program 641) stored in the ROM 62 or the storage unit 64 and expanded in the RAM 63, thereby realizing various functions.

[0081] The storage unit 64 has a storage medium such as an HDD or a flash memory and maintains the stored content even when the power is turned off. The storage unit 64 stores a settlement server program 641 that can be executed by the CPU 61 and various setting information. Here, the settlement server program 641 is a program in which procedures and the like for causing the CPU 61 of the settlement server 60 to execute various processes related to the transaction processing service are described. The CPU 61 executes various processes described later in cooperation with the settlement server program 641.

[0082] In addition, the storage unit 64 stores a prepaid ID management DB 642 and the like. The prepaid ID management DB 642 is a database for managing users of a prepaid settlement service provided at each store. Here, the prepaid settlement service is a settlement service that can pay for the price of goods using an amount (electronic money) prepaid using a card medium such as a prepaid card issued by a store. Also, in the prepaid settlement service, for example, by causing an electronic money charging terminal placed in the store to read the card medium, it is possible to make a deposit linked to the prepaid ID.

[0083] The communication unit 65 is a wired or wireless communication interface that can be connected to the network N. The communication unit 65 communicates with external devices such as the server device 10 and the user terminal 40 via the network N.

[0084] FIG. 14 is a diagram showing an example of the data configuration of the prepaid ID management DB 642. As shown in FIG. 14, the prepaid ID management DB 642 stores by associating a prepaid ID, a remaining charge amount, and related information.

[0085] The prepaid ID is identification information for identifying users of the prepaid payment service provided at each store. The remaining charge amount is information indicating the remaining amount of the money charged by the user corresponding to the prepaid ID. Various types of information related to the prepaid ID are stored in the related information. For example, information such as a seed value and an algorithm related to the generation of a one-time code corresponding to the prepaid ID is stored in the related information.

[0086] Also, for example, static passwords (hereinafter also referred to as PIN codes) related to the use of the prepaid ID may be stored in the related information. The PIN code can be used, for example, when additional authentication of the user is required when a predetermined process such as prepaid payment is requested after authentication of the one-time code. Note that it is assumed that the user corresponding to the prepaid ID has grasped the PIN code in advance.

[0087] When a charge is made by the user, the control unit 600 of the payment server 60 adds the charged amount to the remaining charge amount of the prepaid ID management DB 642 associated with the prepaid ID of the user. Also, when the amount charged by the user at the store is used for payment, the control unit 600 of the payment server 60 subtracts the payment amount from the remaining charge amount of the prepaid ID management DB 642 associated with the prepaid ID of the user.

[0088] Next, the operation of the transaction processing system 1 configured as described above will be explained. The content of each of the various processes described below is an example, and it is possible to appropriately change the order of some processes, omit some processes, or add other processes. For example, in the following description, in order to explain the characteristic operations of the present embodiment clearly, the explanation of some processes is omitted. For example, when some error occurs, there may be a process for dealing with the error, but the description of such a process is omitted.

[0089] Hereinafter, the operations performed by the transaction processing system 1 will be explained by dividing them into each stage 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 described as "registration terminal". Also, when explaining 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 explanation.

[0090] First, an example of the operation at the time of check-in when a user who has come to the store operates the user terminal 40 or the cart terminal 50 to start using the transaction processing service will be explained.

[0091] The control unit 400 of the registration terminal transmits a check-in instruction to the server device 10 in response to the operation of the user, and performs check-in processing in cooperation with the server device 10. Specifically, the control unit 400 transmits a check-in instruction including the terminal ID of its own registration terminal and the store ID of the store to the server device 10.

[0092] Here, the characteristics of the terminal IDs transmitted by the user terminal 40 and the cart terminal 50 are different. Specifically, in the user terminal 40, it is a unique user terminal ID that can be uniquely identified, but in the cart terminal 50, it is a shared cart terminal ID used by an unspecified number of users. Therefore, the content of the check-in process is different between the user terminal 40 and the cart terminal 50.

[0093] First, with reference to FIG. 15, the check-in process performed by the control unit 400 of the user terminal 40 will be described. FIG. 15 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 the user terminal 40 is used.

[0094] First, the control unit 400 of the user terminal 40 acquires the company ID and store ID of the store where the user has entered (step S11). Here, various methods can be adopted for acquiring the store ID. For example, a code symbol for check-in processing that holds the company ID and store ID of the store may be posted at the entrance of the store or the like, and the company ID and store ID may be acquired 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 reads the information held in the code symbol to acquire the company ID and store ID. In this case, the connection destination address of the server device 10 and the like may also be held in the code symbol for check-in processing.

[0095] As another acquisition method, when the user terminal 40 is equipped with a positioning function such as GPS (Global Positioning System), the company ID and store ID of the store corresponding to the current position of the own terminal may be acquired by using the positioning function. In this case, for example, the user terminal 40 acquires the company ID and store ID corresponding to the position information indicating the current position of the own terminal based on the setting information associating the position information of each store with the company ID and store ID. Also, for example, the user terminal 40 transmits the position information acquired by the positioning function to the server device 10, and the server device 10 identifies a store that matches or is close to the position information transmitted from the user terminal 40, and stores the company ID and store ID of the identified store in the check-in management DB 146 in association with a transaction ID or the like.

[0096] Next, the control unit 400 of the user terminal 40 transmits a check-in instruction including the company ID and store ID acquired in step S11 and the user terminal ID of its own user terminal 40 to the server device 10 (step S12).

[0097] In response to the check-in instruction transmitted from the user terminal 40, the control unit 100 of the server device 10 manages the users who enter the store using the check-in management DB 146. Specifically, when receiving the check-in instruction, the control unit 100 issues a unique transaction ID (step S13). Next, the control unit 100 associates the issued transaction ID with the company ID, store ID, and user terminal ID indicated by the check-in instruction and the current date and time (check-in date and time), and registers them in the check-in management DB 146.

[0098] Also, the control unit 100 of the server device 10 refers to the user management DB 145 and determines whether a member ID exists in the data entry of the store-specific information corresponding to the company ID, store ID, and user terminal ID indicated by the check-in instruction (step S14). Here, if the member ID does not exist, the process proceeds to step S16.

[0099] When the member ID exists (step S14; Yes), the control unit 100 of the server device 10 reads out the member ID, associates it with the transaction ID issued in step S13, and registers it in the check-in management DB 146. Also, the control unit 100 reads out the number of points stored in association with the set of the company ID and store ID indicated by the check-in instruction and the read member ID from the point management DB 144 (step S15), and proceeds to step S16.

[0100] In this process, the membership ID registered in the user management DB 145 is read, but it is not limited to this, and it may also be in a form notified from the user terminal 40. For example, the control unit 400 of the user terminal 40 may transmit the membership ID acquired via the operation unit 46, the imaging unit 47, etc. to the server device 10 included in the check-in instruction. In this case, as will be described later, the user terminal 40 may read the membership ID displayed in a code symbolized state on the attendant terminal 30 via the imaging unit 47. Further, the control unit 100 of the server device 10 may register the membership ID notified in the check-in instruction in the check-in management DB 146 together with the transaction ID, etc. Furthermore, when the membership ID is not registered in the store-specific information of the membership ID in the user management DB 145, it may be configured to register the membership ID notified in the check-in instruction in the user management DB 145. Note that, in this case, the control unit 100 of the server device 10 may transmit the check-in completion notification including the membership ID, or may transmit the check-in completion notification without including the membership ID.

[0101] In step S16, the control unit 100 of the server device 10 transmits a check-in completion notification including the transaction ID issued in step S13 to the user terminal 40 (step S16).

[0102] Further, when the control unit 100 registers the membership ID in the check-in management DB 146, it transmits the number of points corresponding to the membership ID to the user terminal 40 included in the check-in completion notification. In addition, the check-in completion notification may include, for example, the store information of the store management DB 142 corresponding to the company ID and store ID indicated in the check-in instruction, and the user setting information of the user management DB 145 corresponding to the company ID, store ID, and user terminal ID indicated in the check-in instruction. Further, for the communication between the server device 10 and the user terminal 40 performed after the issuance of the transaction ID, that is, after the completion of the check-in process, information such as the transaction ID, company ID, store ID, and terminal ID registered in the check-in management DB 146 at the time of the check-in process may be included.

[0103] Note that the control unit 100 of the server device 10 may be configured to send a check-in completion notification after authenticating the user. For example, before sending the check-in completion notification, the control unit 100 of the server device 10 may instruct the user terminal 40 to input authentication information such as a password. In this case, the control unit 400 of the user terminal 40 that has received the instruction causes the display unit 45 to display an input screen (not shown) for inputting the authentication information, and transmits the input authentication information to the server device 10.

[0104] The control unit 100 of the server device 10 compares the authentication information transmitted from the user terminal 40 with the authentication information (password) held in the user setting information of the store-specific information corresponding to the company ID, store ID, and user terminal ID instructed by, for example, the check-in instruction. Then, the control unit 100 of the server device 10 sends a check-in completion notification including the member ID only when the user can be confirmed. Note that when the user cannot be confirmed, it may be configured to prohibit the use of the transaction processing service by notifying an error instead of the check-in completion notification, or it may be configured to permit the use of the transaction processing service by sending a check-in completion notification that does not include the member ID or the like.

[0105] On the other hand, when the control unit 400 of the user terminal 40 receives the check-in completion notification from the server device 10, it holds the information included in the check-in completion notification in the RAM 43 or the like. Then, the control unit 400 causes the display unit 45 to display a screen (hereinafter also referred to as a purchase support screen) for assisting shopping at the store based on the information included in the check-in completion notification (step S17).

[0106] Note that when the control unit 400 of the user terminal 40 receives the store setting information from the server device 10, it controls the functions and operations of its own terminal based on the settings of the store setting information. In addition, when the control unit 400 of the user terminal 40 receives the user setting information from the server device 10, it controls operations such as the payment method based on the settings of the user setting information. It is assumed that the settings of the user setting information can be changed at any timing.

[0107] Here, FIG. 16 is a diagram showing an example of a purchase support screen A displayed on the user terminal 40. As shown in FIG. 16, the purchase support screen A has a first region Aa, a second region Ab, a third region Ac, and a fourth region Ad.

[0108] In the first region Aa, the store name of the store where the check-in process was performed, information indicating the current operation mode, and the like are displayed. In addition, in the first region Aa, a member button Aaa for displaying information about the user at the store where the check-in process was performed is provided. The operation when the member button Aaa is operated will be described later.

[0109] In the second region Ab, information regarding the remaining charge associated with the user's prepaid card ID is displayed. Specifically, the remaining charge associated with the user's prepaid card ID is displayed in the second region Ab. Note that in FIG. 16, since the purchase support screen A in a state where the association of the prepaid card ID described later is not performed is shown, the second region Ab is blank. Also, the information displayed in the second region Ab may not be limited to the remaining charge, but may be in a form of displaying the number of points associated with the user's member ID.

[0110] The third region Ac has a total display region Aca and a registered product region Acb. In the total display region Aca, the total points and total amount of the products registered in the registration process described later are displayed. Also, in the registered product region Acb, information about the products registered in the registration process described later is displayed in the order of registration. Note that the arrangement positions of the total display region Aca and the registered product region Acb in the third region Ac are not limited to the illustrated example, and may be arranged with the top and bottom reversed or the like.

[0111] In the fourth area Ad, an operator for switching the operation mode is displayed. Specifically, in the fourth area Ad, a registration button Ada and a checkout button Adb are displayed. Here, the registration button Ada is an operator for instructing to perform a product registration process. In the example of FIG. 16, the state where this registration button Ada is operated is shown, and "Registering" indicating the current operation mode is displayed in the first area Aa. The checkout button Adb is an operator for instructing the start of a checkout process described later.

[0112] Further, when the control unit 400 of the user terminal 40 receives an operation on the member button Aaa in the first area Aa, the member information screen B shown in FIG. 17 is pop-up displayed, for example, superimposed on the purchase support screen A.

[0113] FIG. 17 is a diagram showing an example of the member information screen B displayed on the user terminal 40. As shown in FIG. 17, on the member information screen B, information of the user regarding the point service provided by the store and information of the user regarding the prepaid payment service provided by the store are displayed.

[0114] Specifically, the user's member ID and the number of points are displayed in association. Note that FIG. 17 shows an example where the member ID is input during the check-in process, and an example where the member ID and the number of points notified in the check-in completion notification are displayed in association. Also, the state where the linking of the prepaid card ID has not been implemented is shown, and the information of the user regarding the prepaid payment service is blank. As described later, the information of the user regarding the prepaid payment service will be displayed when the linking of the prepaid card ID is performed.

[0115] Note that the display method of the member information screen B is not limited to pop-up display, and it may be displayed in other forms. For example, the member information screen B may be displayed in a form where the screen is switched with the purchase support screen A. Also, the member information screen B may be displayed while sliding in a form where it is replaced with the purchase support screen A that becomes non-displayed by sliding in any of the up, down, left, or right directions.

[0116] On the other hand, the check-in process for the cart terminal 50 follows, for example, the sequence shown in FIG. 18. Here, FIG. 18 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 the cart terminal 50 is used.

[0117] First, the control unit 500 of the cart terminal 50 waits until a check-in operation is performed by the user (step S21; No). Here, the check-in operation may be, without particular limitation, for example, a button operation for instructing the start of a transaction, or a reading operation of a card medium that holds the store member ID.

[0118] When the control unit 500 determines that a check-in operation has been performed (step S21; Yes), it transmits a check-in instruction including the company ID and store ID of its own store and the cart terminal ID of its own terminal to the server device 10 (step S22). Here, the store ID can be stored in advance in the storage unit 54, for example. Also, when a card medium is read as the check-in operation, the control unit 500 may include the information (member ID) read from the card medium in the check-in instruction and transmit it.

[0119] The control unit 100 of the server device 10 manages the users who have visited the store using the check-in management DB 146 in response to the check-in instruction transmitted 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 S23). Next, the control unit 100 associates the issued transaction ID with the company ID, store ID, and user terminal ID indicated in the check-in instruction and the current date and time (check-in date and time), and registers them in the check-in management DB 146.

[0120] Subsequently, the control unit 100 of the server device 10 determines whether a member ID is included in the check-in instruction (step S24). Here, if the member ID does not exist (step S24; No), the process proceeds to step S26.

[0121] When the member ID exists (step S24; Yes), the control unit 100 of the server device 10 registers the member ID in the check-in management DB 146 in association with the transaction ID issued in step S23. Next, the control unit 100 reads out the number of points associated with the pair of the store ID and the member ID indicated by the check-in instruction from the point management DB 144 (step S25). Then, the control unit 100 of the server device 10 transmits a check-in completion notification to the cart terminal 50 in the same manner as in the case of the user terminal 40 (step S26).

[0122] Note that in the check-in process of FIG. 18, user authentication may also be performed, and a check-in completion notification including the member ID etc. may be transmitted only when the user can be confirmed.

[0123] Further, when the control unit 500 of the cart terminal 50 receives a check-in completion notification from the server device 10, based on the information included in the check-in completion notification, it causes the display unit 55 to display a purchase support screen having the same screen configuration as in FIG. 16 (step S27).

[0124] Note that when the control unit 500 of the cart terminal 50 receives store setting information from the server device 10, it controls the functions and operations of its own terminal based on the setting of the store setting information in the same manner as the user terminal 40. Further, when the control unit 500 of the cart terminal 50 receives user setting information from the server device 10, it controls operations such as the payment method based on the setting of the user setting information in the same manner as the user terminal 40. Also, it is assumed that the setting of the user setting information can be changed at an arbitrary timing.

[0125] Next, an operation example at the time of linking the prepaid ID to the registration terminal by a user having the prepaid ID will be described. Note that below, an example of linking the prepaid ID to the cart terminal 50 using a one-time code provided to the user terminal 40 will be described.

[0126] First, prior to linking the prepaid ID, the user obtains a one-time code via the user terminal 40. For example, when an application program (hereinafter also referred to as a software token) capable of obtaining a one-time code is introduced into the user terminal 40, the user instructs the acquisition of the one-time code by activating the software token.

[0127] When the activation of the software token is instructed, the control unit 400 of the user terminal 40 cooperates with the software token to obtain a one-time code and causes the display unit 45 to display a screen representing the obtained one-time code. Specifically, the control unit 400 presents a screen to the user that enables selection of one store from among the pre-registered stores, and obtains and displays the one-time code related to the user's prepaid ID at the selected store.

[0128] Here, the one-time code may be displayed in a state visible to the user, or may be displayed in a state encoded into a code symbol such as a barcode. Also, the method for obtaining the one-time code is not particularly limited, and known authentication techniques can be applied.

[0129] For example, in the case of "timestamp authentication", the software token has an algorithm for generating a one-time code and a seed value (e.g., a random number). Since the algorithm includes a calculation formula related to time, it is possible for the user terminal 40 alone to obtain a unique one-time code. Also, in this case, since the algorithm and seed value of the software token are the same as those of the one-time code held by the payment server 60, it is possible to synchronize the one-time code between the user terminal 40 and the payment server 60 in an offline state. Specifically, the payment server 60 manages the association between the one-time code and the prepaid card ID, and can identify the corresponding prepaid card ID by comparing (authenticating) with the one-time code generated by the software token. Also, when using "counter synchronization authentication" that generates based on the number of times the one-time code is issued instead of time, it is possible for the user terminal 40 alone to obtain a unique one-time code.

[0130] For example, in the case of "challenge-response authentication", the control unit 400 of the user terminal 40 accesses the payment server 60 in cooperation with the software token to obtain a random string called a challenge from the payment server 60. Also, the control unit 400 of the user terminal 40 generates (also called a response) a one-time code using an algorithm for generating a predetermined one-time code based on the obtained challenge, thereby obtaining and displaying the one-time code. Also, in this case, the payment server 60 generates a one-time code based on the challenge provided to the user terminal 40 and authenticates the user by comparing with the one-time code.

[0131] Note that the software token may be included in the application program for the store, or may be an independent application program. Also, instead of the software token, a hardware token may be used.

[0132] Then, the user inputs the one-time code displayed on the user terminal 40 into the cart terminal 50, thereby instructing the cart terminal 50 to link with the prepaid ID. Here, the control unit 500 of the cart terminal 50 causes the display unit 55 to display a screen on which the one-time code can be input in response to an operation via the operation unit 56. For example, the control unit 500 of the cart terminal 50 may provide an input field for the one-time code on a screen (hereinafter also referred to as a check-in screen) for receiving the above-described check-in operation.

[0133] Here, FIG. 19 is a diagram showing an example of the check-in screen C displayed on the cart terminal 50. As shown in FIG. 19, the check-in screen C has a member ID input field Ca and a one-time code input field Cb.

[0134] The member ID input field Ca is where the member ID of the store where the check-in process is performed is input. The member ID may be manually input via the operation unit 56. Alternatively, the member ID may be input by reading a card medium such as a membership card via the card reader 58.

[0135] The one-time code input field Cb is an area for inputting the one-time code displayed on the user terminal 40 held by the user. Here, instead of directly inputting the prepaid ID, the one-time code is to be input into the one-time code input field Cb. The one-time code may be manually input via the operation unit 56. Further, when the one-time code is displayed in the form of a code symbol on the user terminal 40, the one-time code may be input by reading the code symbol displayed on the user terminal 40 with the code reader 57.

[0136] Note that on the check-in screen C, either one or both of the member ID and the one-time code may be input, or the check-in operation may be performed without inputting any information. Also, it is assumed that the member ID and the one-time code can identify each other's code types, for example, due to differences in code systems.

[0137] In addition, the check-in screen C is provided with a check-in button Cc for instructing check-in. The user inputs information into the member ID input field Ca and the one-time code input field Bb, and operates the check-in button Cc, thereby realizing the check-in operation to the cart terminal 50. For example, when neither the member ID nor the one-time code is input, or when only the member ID is input, the check-in process is the same as the process described in FIG. 18.

[0138] It is assumed that the input of the member ID and the one-time code is not limited to the time of check-in, but can be input at any time after check-in. For example, during the product registration process described later, the member ID and the one-time code may be input. When the one-time code is input to the cart terminal 50, as shown in FIG. 20, a process for associating the prepaid card ID is performed on the cart terminal 50.

[0139] Here, FIG. 20 is a sequence diagram showing an example of the first cooperation process performed by the transaction processing system 1. It is assumed that the check-in process is completed as a premise of this process.

[0140] First, the control unit 500 of the cart terminal 50 receives the input of the one-time code via the operation unit 56, the code reading unit 57, etc. (step S31). Next, the control unit 500 of the cart terminal 50 transmits a first cooperation instruction including the one-time code input in step S31, the company ID, the store ID, the transaction ID, and the cart terminal ID of its own cart terminal 50 to the server device 10 (step S32).

[0141] The control unit 100 of the server device 10 cooperates with the settlement server 60 in response to the first cooperation instruction transmitted from the cart terminal 50, and acquires user information regarding the user of the prepaid card ID related to the one-time code from the settlement server 60. Here, the user information includes information such as the prepaid card ID specified by the one-time code and the remaining charge amount associated with the prepaid card ID.

[0142] Specifically, when the control unit 100 receives a first cooperation instruction from the user terminal 40, it transmits the one-time code included in the first cooperation instruction to the settlement server 60 (step S33).

[0143] When the control unit 600 of the settlement server 60 receives the one-time code from the server device 10, it performs authentication processing on the user (prepaid card ID) of the prepaid settlement service based on the one-time code (step S34). Specifically, the control unit 600 of the settlement server 60 performs authentication by comparing the received one-time code with the one-time code generated by its own device, and determines that the authentication is successful when they match. When the authentication is successful, the control unit 600 of the settlement server 60 identifies the prepaid card ID corresponding to the one-time code, and reads out the charge balance associated with the prepaid card ID and the user information from the prepaid card ID management DB 642 (step S35). Next, the control unit 600 of the settlement server 60 transmits the read user information to the server device 10 (step S36).

[0144] Here, the control unit 600 of the settlement server 60, for example, activates the prepaid card ID authenticated by the one-time code for a predetermined period, and after the predetermined period has elapsed, sets it to an invalidated state where authentication by the one-time code is required. In this way, the control unit 600 of the settlement server 60 ensures security in the event of a leakage of the prepaid card ID by not keeping the prepaid card ID permanently usable. Note that the prepaid card ID may be temporary information generated dynamically.

[0145] Also, in the case where the prepaid ID is managed in association with the company ID or store ID in the prepaid ID management DB 642, the control unit 100 of the server device 10 may transmit the company ID or store ID included in the first cooperation instruction to the settlement server 60 together with the one-time code. As a result, the settlement server 60 can easily narrow down the prepaid ID to be verified against the one-time code, so that the efficiency of the authentication-related process can be improved. When the authentication based on the one-time code fails, the control unit 600 of the settlement server 60 transmits information indicating the authentication failure to the server device 10.

[0146] When the control unit 100 of the server device 10 acquires the user information from the settlement server 60, based on the transaction ID specified in the first cooperation instruction, it registers the prepaid ID acquired as the user information in the check-in management DB 146 in association with the transaction ID (step S37). Next, the control unit 100 transmits the user information acquired from the settlement server 60 to the cart terminal 50 that has transmitted the first cooperation instruction (step S38).

[0147] When the control unit 500 of the cart terminal 50 receives the user information from the server device 10, it displays the prepaid ID and the remaining charge amount included in the user information on the display unit 55 (step S39). For example, the control unit 500 causes the remaining charge amount to be displayed in the second area Ab of the above-described purchase support screen A. As a result, the user of the cart terminal 50 can confirm the amount charged to his / her prepaid ID by looking at the display unit 55.

[0148] When the control unit 100 of the server device 10 acquires information indicating authentication failure from the settlement server 60, it notifies the cart terminal 50 that has transmitted the first cooperation instruction of the failure in linking the prepaid ID. In this case, the control unit 500 of the cart terminal 50 causes the display unit 55 to display a message notifying the failure in linking the prepaid ID and a message prompting re-entry of the one-time code or the like.

[0149] Further, when a member ID is entered in the member ID input field Ca, the control unit 500 of the cart terminal 50 may transmit the member ID included in the first cooperation instruction. In this case, the control unit 100 of the server device 10 reads out the number of points associated with the pair of the store ID and the member ID indicated by the first cooperation instruction from the point management DB 144, and transmits the read number of points to the cart terminal 50 together with user information and the like. Thereby, for example, the member ID held in a member card or the like can be linked to the transaction processing system 1.

[0150] In the above description, the prepaid ID is linked using the cart terminal 50, but the user terminal 40 can be linked in the same manner. For example, when the function of the software token mounted on the user terminal 40 is included in the application program for the store, when the control unit 400 executes the first cooperation process in cooperation with the application program for the store, the one-time code acquired by the function of the software token may be transmitted to the server device 10 in the first cooperation instruction.

[0151] Further, when the software token is an independent application program separate from the application program for the store, the control unit 400 of the user terminal 40 can perform the first cooperation process described above by delivering the one-time code acquired by the software token to the application program for the store. Here, it is assumed that various methods can be adopted for the method of delivering the one-time code to the application program for the store.

[0152] For example, the application program for the store may share the one-time code obtained by the software token between software in the form of using technologies such as API (Application Programming Interface). Also, as another method, it may be configured to transfer the one-time code obtained by the software token to the application program for the store via an external device such as the attendant terminal 30. In this case, for example, the control unit 300 of the attendant terminal 30 receives the input of the one-time code by displaying a screen (hereinafter referred to as the ID linking support screen) as shown in FIG. 21.

[0153] FIG. 21 is a diagram showing an example of the linking support screen D displayed on the attendant terminal 30. As shown in FIG. 21, the linking support screen D has a one-time code input field Da.

[0154] The one-time code obtained by the software token is input into the one-time code input field Da. The one-time code may be manually input via the operation unit 36. Also, when the one-time code is displayed in the form of a code symbol on the user terminal 40, the one-time code may be input by the code reading unit provided in the attendant terminal 30 reading the code symbol.

[0155] In addition, the linking support screen D is provided with an issuance button Db for instructing to convert the one-time code into a form that can be received by the application program for the store of the user terminal 40. When the one-time code is input into the one-time code input field Da and the issuance button Db is operated by the operator of the attendant terminal 30, the control unit 300 of the attendant terminal 30 generates a code symbol by encoding the one-time code input into the one-time code input field Da into a two-dimensional code or the like. Then, the control unit 300 of the attendant terminal 30 causes the display unit 35 to display a screen (hereinafter also referred to as the issuance screen) representing the generated code symbol.

[0156] FIG. 22 is a diagram showing an example of an issuance screen displayed on the attendant terminal 30. As shown in FIG. 22, the issuance screen E has a first area Ea for displaying a code symbol. As described above, the code symbol displayed in the first area Ea holds a one-time code. By imaging the code symbol displayed in the first area Ea with the imaging unit 47 of the user terminal 40, the one-time code is input into the user terminal 40.

[0157] Specifically, the control unit 400 of the user terminal 40 acquires the one-time code included in the code symbol by decoding the code symbol. Then, the control unit 400 of the user terminal 40 cooperates with the store application program and transmits the above-described first cooperation instruction including the acquired prepaid ID to the server device 10. Thereby, based on the one-time code uniquely acquired by the software token, the prepaid ID corresponding to the one-time code can be linked to the transaction processing system 1.

[0158] In FIG. 21, a screen configuration that allows input of a one-time code is shown, but it is not limited to this. Similar to FIG. 19, a screen configuration that also allows input of a member ID may be used. In this case, the control unit 300 of the attendant terminal 30 generates a code symbol including both pieces of information by encoding the input one-time code and member ID in response to an operation of the issuance button Db. Further, the control unit 400 of the user terminal 40 acquires the one-time code and member ID included in the code symbol by decoding the code symbol. Then, by transmitting a first cooperation instruction including the one-time code and member ID to the server device 10, the member ID and prepaid ID can be linked to the transaction processing system 1 in the same manner as in the case of the cart terminal 50 described above.

[0159] FIG. 23 is a sequence diagram showing another example of the first cooperation process performed by the transaction processing system 1. In FIG. 23, a processing example in the case of inputting a one-time code to the user terminal 40 via the attendant terminal 30 will be described. Further, as a premise of this process, it is assumed that the check-in process has been completed.

[0160] First, the control unit 300 of the attendant terminal 30 receives the input of the one-time code via the above-described one-time code input field Da or the like (step S41). Next, the control unit 300 encodes the one-time code received in step S41 into a code symbol (step S42), and causes the display unit 35 to display the generated code symbol (step S43).

[0161] The user who operates the user terminal 40 inputs the one-time code held in the code symbol to the user terminal 40 by imaging the code symbol displayed on the display unit 35 of the attendant terminal 30 using the imaging unit 47.

[0162] Specifically, the control unit 400 of the user terminal 40 reads the one-time code held in the code symbol by decoding the code symbol imaged by the imaging unit 47 (step S44). Next, the control unit 400 transmits a first cooperation instruction including the one-time code read in step S44, the user terminal ID of its own terminal, the company ID and store ID of the store during check-in to the server device 10 (step S45). The subsequent processing in steps S46 to S51 is the same as the processing in steps S33 to S39 described in FIG. 20, and the control unit 400 of the user terminal 40 receives the user information transmitted from the server device 10.

[0163] When the control unit 400 of the user terminal 40 receives the user information from the server device 10, it causes the display unit 45 to display a screen based on the user information (step S51). For example, the control unit 400 displays the remaining charge in the second area Ab of the above-described purchase support screen A (step S52).

[0164] Here, FIG. 24 is a diagram showing an example of the purchase support screen A displayed on the user terminal 40, and shows the state after the prepaid card ID has been linked. As shown in FIG. 24, when the linking of the prepaid card ID is completed, the remaining charge amount associated with the user's prepaid card ID is displayed in the second area Ab. As a result, the user of the user terminal 40 can easily check the remaining charge amount that can be used in the store by looking at the purchase support screen A.

[0165] Also, in this case, when the control unit 400 of the user terminal 40 receives an operation on the member button Aaa in the first area Aa, it displays the member information screen B shown in FIG. 25.

[0166] FIG. 25 is a diagram showing an example of the member information screen B displayed on the user terminal 40. As shown in FIG. 25, in addition to the user's information regarding the point service shown in FIG. 17, the user's information regarding the prepaid payment service is displayed on the member information screen B.

[0167] Specifically, when the prepaid card ID is linked, the user's prepaid card ID and the remaining charge amount are displayed in association. As a result, the user of the user terminal 40 can easily check the remaining charge amount that can be used in the store by looking at the member information screen B.

[0168] Also, an update button Ba is displayed on the member information screen B after the prepaid card ID is linked. The update button Ba is an operator for instructing an update of the remaining charge amount. When the update button Ba is operated, the control unit 400 of the user terminal 40 cooperates with the server device 10 or the like and executes a process (update process) for updating the remaining charge amount to the latest state.

[0169] Here, FIG. 26 is a sequence diagram showing an example of the update process performed by the transaction processing system 1. It is assumed that the linking of the prepaid card ID has been completed as a prerequisite for this process.

[0170] When the control unit 400 of the user terminal 40 receives an operation of the update button Ba from the membership information screen B (step S61), it transmits a balance inquiry request for requesting an inquiry of the remaining balance to the server device 10 (step S62).

[0171] Here, the balance inquiry request includes information that can identify the prepaid card ID in the server device 10. For example, in the present embodiment, in the check-in management DB 146, the prepaid card ID is stored in association with a set of a company ID, a store ID, and a terminal ID, or a transaction ID. Therefore, by including the set of the company ID, the store ID, and the terminal ID and / or the transaction ID in the balance inquiry request, the server device 10 can identify the prepaid card ID. Alternatively, by including the prepaid card ID in the balance inquiry request, it may be in a form that can directly identify the prepaid card ID.

[0172] When the control unit 100 of the server device 10 receives the balance inquiry request, it identifies the prepaid card ID instructed in the balance inquiry request (step S63). For example, when the balance inquiry request includes a set of a company ID, a store ID, and a terminal ID and / or a transaction ID, the control unit 100 of the server device 10 identifies the prepaid card ID corresponding to the conditions of the balance inquiry request from the check-in management DB 146. Also, for example, when the balance inquiry request includes the prepaid card ID, the control unit 100 of the server device 10 identifies the prepaid card ID included in the balance inquiry request.

[0173] Subsequently, the control unit 100 of the server device 10 transmits a balance request including the identified prepaid card ID to the settlement server 60 (step S64). When the control unit 600 of the settlement server 60 receives the balance request from the server device 10, it reads out the remaining balance associated with the prepaid card ID instructed in the balance request from the prepaid card ID management DB 642 (step S65). Next, the control unit 600 transmits the read remaining balance to the server device 10 (step S66).

[0174] When the control unit 100 of the server device 10 receives the remaining charge amount from the settlement server 60, it transmits this remaining charge amount to the user terminal 40 that sent the remaining balance reference request (step S67). Then, the control unit 400 of the user terminal 40 updates and displays the remaining charge amount on the membership information screen B based on the remaining charge amount transmitted from the server device 10 (step S68).

[0175] As a result, the user of the user terminal 40 can easily check the latest status of the remaining charge amount at the store where they checked in by viewing the membership information screen B. For example, when the user charges their prepaid card ID, they can easily check whether the charged amount is reflected. Therefore, in the transaction processing system 1, the convenience related to the use of the prepaid settlement service provided at the store can be improved.

[0176] Note that the result of the update process described above shall be reflected not only on the membership information screen B but also on the purchase support screen A (second area Ab).

[0177] Also, the display method of the membership information screen B is not limited to pop-up display and may be displayed in other forms. For example, the membership information screen B may be displayed in a form where it switches screens with the purchase support screen A. Also, the membership information screen B may be displayed while sliding in a form where it slides and switches with the purchase support screen A that becomes non-displayed by sliding in any of the up, down, left, or right directions.

[0178] Next, an example of the operation at the time of product registration will be described, where the user who has performed the check-in process uses a registration device (user terminal 40 or cart terminal 50) to register a product sold at the store as a product to be transacted (purchased).

[0179] When the control unit 400 of the registration terminal reads the product ID from the code symbol attached to the product in response to the user's operation, it transmits a registration instruction including the product ID to the server device 10, and performs the product registration process in cooperation with the server device 10.

[0180] Figure 27 is a sequence diagram showing an example of product registration processing performed by the transaction processing system 1. First, the control unit 400 of the registration terminal reads the product ID from the code symbol attached to the product to be purchased according to the user's operation (step S71). For example, when the registration terminal is the user terminal 40, the control unit 400 detects the code symbol from the image of the product captured by the imaging unit 47 and decodes the code symbol to read the product ID. Also, for example, when the registration terminal is the cart terminal 50, the control unit 500 reads the product ID from the code symbol attached to the product in cooperation with the code reading unit 57.

[0181] Subsequently, the control unit 400 of the registration terminal transmits a registration instruction including at least the product ID read in step S41 to the server device 10 (step S72).

[0182] Here, the registration request includes information that can identify the transaction ID in the server device 10. For example, in the present embodiment, in the check-in management DB 146, the transaction ID is stored in association with the combination of the company ID, store ID, and terminal ID. Therefore, the transaction ID can be identified in the server device 10 by including the combination of the company ID, store ID, and terminal ID and / or the transaction ID in the remaining high-reference request.

[0183] When the control unit 100 of the server device 10 receives a registration instruction from the registration terminal, it identifies the company ID and store ID from the check-in data in the check-in management DB 146 corresponding to the transaction ID indicated in the registration instruction. Next, the control unit 100 reads the product information of the product corresponding to the combination of the identified company ID and store ID and the product ID indicated in the registration instruction from the store-specific product master 143 (step S73).

[0184] When the registration instruction is transmitted including the company ID and store ID, the control unit 100 of the server device 10 can efficiently read the product information of the corresponding product from the store-specific product master 143 based on the combination of the company ID and store ID indicated in the registration instruction and the product ID.

[0185] Subsequently, the control unit 100 of the server device 10 associates the product information read in step S73 with the transaction ID and product ID indicated by the registration instruction, and registers it in the transaction management DB 147 (step S74). Further, the control unit 100 transmits the product information registered in the transaction management DB 147 as a registration completion notice to the registration terminal that sent the registration instruction (step S75). Hereinafter, information indicating the breakdown of products such as product IDs and product information registered in association with the transaction ID is also referred to as "transaction data". Note that the control unit 100 of the server device 10 may transmit the transaction data of all products registered in association with the specified transaction ID to the registration terminal in step S75.

[0186] Further, the control unit 100 of the server device 10 may be configured to calculate the total amount of products based on all the transaction data associated with the destination transaction ID at the timing of registering the product in the transaction management DB 147, and register the total amount in association with the transaction ID. In this case, the transaction ID can also be rephrased as specific information capable of specifying the total amount of the registered products.

[0187] On the other hand, when the control unit 400 of the registration terminal receives product information as a response to the registration instruction, it causes the display unit 45 to display the product information (step S76). Specifically, as shown in FIG. 28, the control unit 400 causes the product information of the product for which registration has been completed to be displayed in the third area Ac of the purchase support screen A.

[0188] FIG. 28 shows an example of the purchase support screen A displayed on the user terminal 40. When a product ID is registered in the transaction management DB 147 by a registration instruction from the user terminal 40, the control unit 400 of the user terminal 40 causes information about the product with the product ID to be displayed in the third area Ac of the purchase support screen A.

[0189] Specifically, the control unit 400 of the user terminal 40 causes the registered product area Acb in the third area Ac to display information about the registered products in the order of registration. Here, a rectangular small area Acc is provided for each registered product, and in addition to product information such as the product name and price, the registered points are displayed within the small area Acc. Note that FIG. 28 shows an example where three products are registered.

[0190] Also, in the total display area Aca of the third area Ac, the total points and total amount of the registered products are displayed. Note that 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 prices and points of the registered products, or may be calculated by the server device 10.

[0191] Note that in FIG. 28, the purchase support screen A displayed on the display unit 45 of the user terminal 40 is illustrated, but it is assumed that information about the registered products is also displayed in the same form in the case of the cart terminal 50.

[0192] Returning to FIG. 27, subsequently, the control unit 100 of the server device 10 executes a balance confirmation process of checking the magnitude relationship between the total amount of the products and the remaining charge for the transaction in which the product was registered in step S74 (step S77).

[0193] Hereinafter, the balance confirmation process in step S77 will be described with reference to FIG. 29. Here, FIG. 29 is a flowchart showing an example of the balance confirmation process performed by the server device 10.

[0194] First, the control unit 100 of the server device 10 refers to the check-in management DB 146 and determines whether a pre-paid ID exists in the check-in data related to the transaction ID in which the product was registered in step S74 (step S81). Here, if the pre-paid ID does not exist (step S81; No), the control unit 100 ends this process.

[0195] When it is determined in step S81 that the prepaid ID exists (step S81; Yes), the control unit 100 of the server device 10 obtains the remaining charge amount from the settlement server 60 by transmitting a remaining amount request including the prepaid ID to the settlement server 60 (step S82).

[0196] Subsequently, the control unit 100 of the server device 10 refers to the transaction management DB 147 and calculates the total amount of the products registered so far in the transaction based on all the transaction data associated with the transaction ID in which the product was registered in step S74 (step S83). In the case where the total amount is registered in the transaction management DB 147 in accordance with the registration of the product, a configuration may be adopted in which the registered total amount is read instead of step S83.

[0197] Subsequently, the control unit 100 of the server device 10 compares the remaining charge amount with the total amount and determines whether the total amount exceeds the remaining charge amount (step S84). When it is determined that the total amount exceeds the remaining charge amount (step S84; Yes), the control unit 100 determines whether the notification flag in the check-in management DB 146 associated with the transaction ID of the transaction is off (step S85).

[0198] When the notification flag is on (step S85; No), the control unit 100 of the server device 10 determines that the insufficient balance information has been transmitted and ends this process. When the notification flag is off (step S85; Yes), the control unit 100 of the server device 10 transmits insufficient balance information instructing the registration terminal that sent the registration instruction of insufficient balance (step S86). Here, the control unit 100 of the server device 10 may include, for example, the insufficient amount obtained by subtracting the total amount from the remaining charge amount in the insufficient balance information. Then, the control unit 100 of the server device 10 switches the notification flag to the on state (step S87) and ends this process.

[0199] Also, when the control unit 100 of the server device 10 determines in step S84 that the total amount is less than or equal to the remaining charge amount (step S84; No), it determines whether the notification flag is in the on state (step S88). Here, when the notification flag is in the off state (step S88; No), the control unit 100 of the server device 10 ends this process.

[0200] Also, when it is determined in step S88 that the notification flag is in the on state (step S88; Yes), the control unit 100 of the server device 10 transmits remaining balance shortage resolution information instructing the registration terminal that sent the registration instruction that the state of insufficient remaining balance has been resolved (step S89). Here, the control unit 100 of the server device 10 may transmit, for example, including the current remaining charge amount in the remaining balance shortage information. Then, the control unit 100 of the server device 10 switches the notification flag to the off state (step S90) and ends this process.

[0201] On the other hand, when the control unit 400 of the registration terminal receives the remaining balance shortage information transmitted in step S86, it notifies the user by displaying a notification screen that notifies of the insufficient remaining balance.

[0202] Here, FIG. 30 is a diagram showing an example of the notification screen displayed on the user terminal 40. Such a notification screen is pop-up displayed, for example, superimposed on the purchase support screen A.

[0203] As shown in FIG. 30, on the notification screen F, a message notifying that the total amount exceeds the remaining charge amount is displayed. Also, on the notification screen F, a message prompting additional charging is displayed. Also, an OK button Fa is provided on the notification screen F. When the control unit 400 of the user terminal 40 receives an operation of the OK button Fa, it erases the notification screen F.

[0204] As a result, by looking at the notification screen F, the user operating the registration terminal can easily confirm that the total amount of the registered products exceeds the remaining balance associated with their prepaid card ID, indicating a shortage of balance. In FIG. 30, the notification screen F displayed on the display unit 45 of the user terminal 40 is illustrated, but the notification screen is also displayed in the same manner for the cart terminal 50.

[0205] By the way, since the display of the notification screen F is performed according to the insufficient balance information, if the insufficient balance information is transmitted every time a new product is registered, the notification screen F will be displayed each time. Such a specification is troublesome for the user and may instead reduce the operability. In this regard, in the present embodiment, by using a notification flag, the number of transmissions of the insufficient balance information, that is, the number of times the notification screen F is displayed, is limited to once per transaction.

[0206] As a result, in the transaction processing system 1, even when the total amount exceeds the recharge amount due to the registration of a product, the insufficient balance is notified only for the first time, and no further notification is made even if additional products are registered later. Therefore, in the transaction processing system 1, it is possible to prevent a situation where the notification screen F is displayed multiple times during a single transaction.

[0207] In the present embodiment, the number of transmissions of the insufficient balance information is set to once, but it is not limited to this, and a configuration that allows two or more transmissions may be adopted. In this case, for example, the notification flag may be configured to hold multi-valued information, and each time an insufficient balance notification is made, it is incremented by 1, so that the insufficient balance information is transmitted up to the allowable number of notifications set as a threshold value.

[0208] Also, a configuration may be adopted to control the number of transmissions of the insufficient balance information according to the user's settings. Specifically, when the transmission number (or notification number) is set in the store setting information or user setting information included in the check-in data, the control unit 100 of the server device 10 may limit the number of transmissions of the insufficient balance information according to this setting. For example, when the transmission number is set to zero, a configuration may be adopted not to transmit the insufficient balance information.

[0209] Furthermore, in the balance confirmation process, in steps S84 → S88 to S90, when the total amount is less than or equal to the charge balance and the notification flag is in the on state, the control unit 100 of the server device 10 switches the notification flag to the off state. As a result, in the server device 10, for example, when the insufficient balance information has been transmitted and then the insufficient balance state is resolved by executing additional charging, the insufficient balance information can be transmitted again. Therefore, in the registration terminal, for example, for a transaction in which the insufficient balance has been resolved by executing additional charging and then the insufficient balance state occurs again due to additional registration of products, the notification screen F can be displayed again. Note that even if the insufficient balance state is resolved by canceling the registered products or executing additional charging after the insufficient balance information has been transmitted, it may be configured to notify only once for the entire transaction so that the insufficient balance information is not transmitted again. Also, the user terminal 40 may be configured to notify the server device 10 of the start of the settlement process at the timing when the settlement button Adb is operated. In the server device 10, when the insufficient balance state has not been resolved at the time when the start of the settlement process is notified, it may be configured to transmit the insufficient balance information regardless of the state of the notification flag.

[0210] Note that in the registration terminal, even after the notification screen F is erased, the user may be notified of the state by indicating that the insufficient balance state exists on the purchase support screen A or the member information screen B. For example, as shown in FIG. 31, the control unit 400 of the user terminal 40 may notify that the insufficient balance state exists by highlighting the insufficient amount in red or the like in the second area Ab of the purchase support screen A. Here, FIG. 31 is a diagram showing an example of the purchase support screen A displayed on the user terminal 40.

[0211] Also, when representing the state of insufficient balance on the member information screen B, as shown in FIG. 31, control may be performed to prompt the display of the member information screen B by attaching an emphasis mark Aab such as an exclamation mark to the member button Aaa provided in the first area Aa of the purchase support screen A. When the member button Aaa is operated in this state, the control unit 400 of the user terminal 40 notifies the user that the balance is insufficient by displaying, for example, the member information screen B shown in FIG. 32.

[0212] FIG. 32 is a diagram showing an example of the member information screen B displayed on the user terminal 40. As shown in FIG. 32, on the member information screen B displayed in the state of insufficient balance, the shortage amount is highlighted in red characters or the like after the remaining recharge balance.

[0213] Thereby, even after the user of the registration terminal deletes the notification screen F, by viewing the purchase support screen A or the member information screen B, the user can recognize that the remaining recharge balance is in a state of insufficient balance. Also, in this case, since the user of the registration terminal can easily recognize the shortage amount, it becomes easy to perform a recharge according to the shortage amount.

[0214] Note that the shortage amount displayed on the purchase support screen A or the member information screen B may be notified from the server device 10 included in the insufficient balance information, or may be calculated by the control unit 400 of the registration terminal by subtracting the total amount from the remaining recharge balance.

[0215] Also, in the registration terminal in a state of insufficient balance, when insufficient balance resolution information is transmitted from the server device 10, the control unit 400 of the registration terminal cancels (deletes) the notification display of the shortage amount displayed on the purchase support screen A or the member information screen B. Thereby, the user of the registration terminal can easily recognize that the state of insufficient balance has been resolved by viewing the purchase support screen A or the member information screen B.

[0216] Note that the timing for determining the shortage amount is not limited to the time of product registration. For example, when a charge balance acquisition request is sent from the registration terminal, the control unit 100 of the server device 10 may perform the above-described balance confirmation process together. As a result, when the user of the registration terminal, for example, makes an additional charge, the user can easily confirm whether the updated charge balance is in a state of insufficient balance by operating the update button Ba on the membership information screen B.

[0217] Next, an operation example related to the accounting of the product registered in the above-described product registration process will be described.

[0218] When the control unit 400 of the registration terminal receives an operation of the accounting button Adb provided in the fourth area Ad of the purchase support screen A, for example, it performs an accounting process for accounting for the products registered so far by cooperating with the server device 10 and the accounting device 20.

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

[0220] Therefore, in the present embodiment, a form will be described in which the registration device outputs a transaction ID as an example of specific information that can identify the charge destination of the electronic money and the breakdown or total amount of the products registered as purchase targets, and inputs the transaction ID into the accounting device 20. Further, in the present embodiment, a form will be described in which a method that does not involve electrical communication is used as an example of a method for inputting specific information into the accounting device 20 to the accounting device 20.

[0221] FIG. 33 is a sequence diagram showing an example of the accounting process performed by the transaction processing system 1. First, when the control unit 400 of the registration terminal receives an instruction to start accounting from the user by operating the accounting button Adb or the like (step S101), it encodes the transaction ID held in the RAM 43 or the like into a code symbol (step S102). Next, the control unit 400 of the registration terminal causes the generated code symbol to be displayed (output) on the display unit 45 (step S103). The user inputs the transaction ID, which is specific information, into the accounting device 20 by having the code symbol displayed on the registration terminal read by the code reading unit 27 of the accounting device 20.

[0222] When the control unit 200 of the accounting device 20 reads the transaction ID from the code symbol displayed on the registration terminal via the code reading unit 27 (step S104), it transmits an accounting data acquisition instruction including the transaction ID to the server device 10 (step S105).

[0223] When the control unit 100 of the server device 10 receives the accounting data acquisition instruction from the accounting device 20, it reads out the transaction data associated with the transaction ID indicated by the transaction data acquisition instruction from the transaction management DB 147 (step S106). Also, the control unit 100 reads out the check-in data of the check-in management DB 146 corresponding to the transaction ID indicated by the transaction data acquisition instruction (step S107). That is, when the member ID and the prepaid card ID exist in the check-in data, the control unit 100 of the server device 10 reads out those IDs.

[0224] Subsequently, the control unit 100 of the server device 10 reads out the corresponding number of points from the point management DB 144 based on the company ID, store ID, and member ID included in the check-in data read in step S107 (step S108). Next, the control unit 100 of the server device 10 transmits the accounting data including the transaction data read in step S106, the check-in data read in step S107, and the number of points read in step S108 to the accounting device 20 that transmitted the accounting data acquisition instruction (step S109).

[0225] Here, the accounting data is a data set related to the accounting (settlement) of the products registered in the transaction corresponding to the transaction ID, and includes at least transaction data and check-in data. Here, the check-in data includes information such as the transaction ID, company ID, store ID, terminal ID, member ID, prepaid card ID, and check-in date and time as described above. In addition, when the member ID and prepaid card ID are empty, information indicating that they are empty may be included in the transaction data, or the member ID and prepaid card ID may not be included in the transaction data.

[0226] In addition, when the prepaid card ID exists in the check-in data, the charge balance may be included in the accounting data and transmitted. In this case, the control unit 100 of the server device 10 may transmit a balance request including the prepaid card ID to the settlement server 60, obtain the charge balance associated with the prepaid card ID from the settlement server 60, and include the obtained charge balance in the accounting data and transmit it to the accounting device 20.

[0227] Also, when the prepaid card ID exists in the check-in data, the control unit 100 of the server device 10 may include the prepaid card ID in the accounting data and transmit it without obtaining the charge balance. In this case, the control unit 200 of the accounting device 20 may transmit a balance request including the prepaid card ID to the settlement server 60 to obtain the charge balance stored in association with the prepaid card ID from the settlement server 60.

[0228] When the control unit 200 of the accounting device 20 receives the accounting data from the server device 10, based on the accounting data, it causes the display unit 25 to display the details of the registered products and transaction details such as the total amount (step S110). Subsequently, the control unit 200 executes accounting processing (step S111) based on the accounting data. Here, the total amount to be displayed may be calculated by the control unit 200 of the accounting device 20, or may be in a form using the total amount included in the accounting data.

[0229] FIG. 34 is a flowchart showing an example of the accounting process performed by the accounting device 20. First, the control unit 200 of the accounting device 20 causes the display unit 25 to display a selection screen (not shown) for allowing the user to select a payment method (step S121).

[0230] For example, the control unit 200 of the accounting device 20 causes a selection screen including an operator for selecting a payment method that the accounting device 20 can handle to be displayed. However, when the prepaid ID is included in the accounting data, it is preferable that the control unit 200 of the accounting device 20 causes a selection screen including an operator for selecting prepaid payment to be displayed. In other words, when the prepaid ID is not included in the accounting data, a selection screen not including an operator for selecting prepaid payment may be displayed. Further, for example, when user setting information is included in the accounting data and a payment method is specified in the user setting information, a selection screen including an operator for selecting the specified payment method may be displayed. Note that when the specified payment method is single, the control unit 200 of the accounting device 20 may shift to step S123 without displaying the selection screen.

[0231] After the selection screen is displayed in step S121, the control unit 200 of the accounting device 20 waits until a payment method is selected (step S122; No). When a payment method is selected (step S122; Yes), the control unit 200 of the accounting device 20 determines whether the selected payment method is prepaid payment (step S123).

[0232] When a payment method other than prepaid payment (for example, cash payment, credit card payment, other electronic money payment other than prepaid payment) is selected (step S123; No), the control unit 200 executes an accounting process for paying the price of the product by the selected payment method (step S124) and shifts to step S130.

[0233] On the other hand, when it is determined in step S123 that prepaid settlement has been selected (step S123; Yes), the control unit 200 of the accounting device 20 acquires the remaining charge amount from the settlement server 60 based on the prepaid card ID included in the accounting data (step S125). Specifically, the control unit 200 of the accounting device 20 transmits a remaining amount request including the prepaid card ID to the settlement server 60, and acquires the remaining charge amount stored in association with the prepaid card ID from the settlement server 60. In addition, when the remaining charge amount is included in the accounting data, it may be configured to acquire this remaining charge amount.

[0234] Subsequently, the control unit 200 of the accounting device 20 compares the total amount of the goods with the remaining charge amount, and determines whether the total amount exceeds the remaining charge amount (step S126). When the total amount exceeds the remaining charge amount (step S126; Yes), the control unit 200 of the accounting device 20 notifies the insufficient balance by causing the display unit 25 to display information for notifying the insufficient balance (step S127), and returns the process to step S121. For example, the control unit 200 of the accounting device 20 notifies the user of the insufficient balance by causing the display unit 25 to display the insufficient amount calculated by subtracting the total amount from the remaining charge amount.

[0235] In addition, when the accounting device 20 has a charging function, instead of returning the process to step S121, an operator for performing additional charging of the electronic money may be displayed to prompt the user for additional charging. Further, when it is allowed to pay by combining prepaid settlement with other settlement methods, the control unit 200 of the accounting device 20 may be configured to return the process to step S121 after performing payment for the remaining charge amount by prepaid settlement in step S128 described later, so that the remaining amount is paid using another settlement method.

[0236] When it is determined in step S126 that the total amount is less than or equal to the remaining prepaid balance (step S126; No), the control unit 200 of the accounting device 20 executes an accounting process (prepaid settlement) for paying the price of the product with the remaining prepaid balance of the prepaid electronic money (step S128). Specifically, the control unit 200 of the accounting device 20 transmits a charge amount subtraction instruction including the prepaid card ID and the payment amount to the settlement server 60, and cooperates with the settlement server 60 to execute an accounting process based on the remaining prepaid balance (step S129).

[0237] Thereby, the control unit 600 of the settlement server 60 performs a prepaid settlement process of subtracting the amount used for payment at the store from the remaining prepaid balance of the user based on the charge amount subtraction instruction transmitted from the accounting device 20. Specifically, the control unit 600 of the settlement server 60 specifies the remaining prepaid balance corresponding to the prepaid card ID indicated in the charge amount subtraction instruction from the prepaid card ID management DB642. Then, the control unit 600 of the settlement server 60 subtracts the payment amount indicated in the charge amount subtraction instruction from the specified remaining prepaid balance.

[0238] Note that, prior to the prepaid settlement, the control unit 200 of the accounting device 20 may display a screen for inputting the PIN code to prompt the user to input the PIN code. In this case, the control unit 200 of the accounting device 20 may include the input PIN code in the charge amount subtraction instruction and transmit it to cause the settlement server 60 to authenticate the user based on the PIN code. Specifically, the control unit 600 of the settlement server 60 collates the PIN code included in the transmitted charge amount subtraction instruction with the PIN code stored in association with the prepaid card ID, and performs the prepaid settlement process when they match. Also, when the PIN codes do not match, the control unit 600 of the settlement server 60 notifies the accounting device 20 of the authentication failure and causes the PIN code to be input again.

[0239] Also, in this process, although the prepaid settlement is performed in such a form that the accounting device 20 directly communicates with the settlement server 60, it is not limited to this. For example, the accounting device 20 may perform prepaid settlement by communicating with the settlement server 60 via the server device 10.

[0240] Subsequently, the control unit 200 of the accounting device 20 determines whether or not the member ID is included in the accounting data (step S130). If the member ID is not included in the accounting data (step S130; No), the control unit 200 of the accounting device 20 ends this process.

[0241] On the other hand, if the member ID is included in the accounting data (step S130; Yes), the control unit 200 of the accounting device 20 issues the number of points corresponding to the payment amount (step S131). Then, the control unit 200 of the accounting device 20 transmits a point addition instruction including the company ID and store ID of its own store, the member ID, and the number of points to the server device 10 (step S132), and ends this process.

[0242] Thereby, the control unit 100 of the server device 10 performs a point granting process of adding the points issued at the store to the user's number of points based on the point addition instruction transmitted from the accounting device 20. Specifically, the control unit 100 of the server device 10 specifies the number of points corresponding to the company ID, store ID, and member ID indicated in the point addition instruction from the point management DB 144. Then, the control unit 100 of the server device 10 adds the number of points indicated in the point addition instruction to the specified number of points.

[0243] As described above, when the server device 10 receives the input of the one-time code related to the use of the electronic payment service from the registration terminal, it transmits the received one-time code to the payment server 60, thereby obtaining the user information of the user related to the one-time code from the payment server 60. Then, the server device 10 transmits the obtained user information to the registration terminal, thereby realizing the cooperation between this system and the prepaid ID. As a result, in the transaction processing system 1, since it can support the authentication method using the one-time code, the security related to the use of the prepaid payment service can be improved. Also, thereby, the user operating the registration terminal can register the products sold in the store while checking the remaining recharge amount, so that the convenience related to prepaid payment (electronic payment) can be improved.

[0244] Also, in the transaction processing system 1, when the accounting of the product is performed by the accounting device 20, together with the information related to the registered product, the prepaid ID of the user is delivered to the accounting device, so that the accounting device can perform the prepaid payment of the product based on the transaction ID. Therefore, in the transaction processing system 1, since the prepaid payment of the product registered by the registration device can be smoothly performed using the accounting device 20, the convenience related to prepaid payment (electronic payment) can be improved. Also, in the transaction processing system 1, after the prepaid ID is linked, the prepaid payment of the product registered by the registration device can be performed using the accounting device 20 without re-entering the one-time code, so that the convenience related to prepaid payment can be improved.

[0245] Note that the above-described embodiment can be appropriately modified and implemented by changing a part of the configuration or function of each of the above-described devices. Therefore, below, some modification examples according to the above-described embodiment will be described as other embodiments. Note that below, mainly the points different from the above-described embodiment will be described, and detailed descriptions of the points common to the already described content will be omitted. Also, the modification examples described below may be implemented individually or in appropriate combination.

[0246] (Modification Example 1) In the above-described embodiment, after the cooperation of the Precure ID, the server device 10 manages the Precure ID. However, the present invention is not limited to this, and the Precure ID may be managed on the registration terminal side. In this case, when the control unit 400 of the registration terminal exchanges various information with the server device 10, the Precure ID is transmitted to the server device 10. For example, when the control unit 400 of the registration terminal performs the above-described update process (see FIG. 26), the Precure ID is included in the balance inquiry request and transmitted to the server device 10. Thereby, the server device 10 can execute processing based on the Precure ID in the same manner as in the above-described embodiment.

[0247] Also, in this case, before accounting at the accounting device 20, the control unit 400 of the registration terminal causes the display unit 45 to display a code symbol including the Precure ID together with the transaction ID. Thereby, the accounting device 20 can execute processing based on the Precure ID in the same manner as in the above-described embodiment.

[0248] (Modification Example 2) In the above-described embodiment, the form in which the user terminal 40 independently acquires the one-time code by the function of the software token mounted on the user terminal 40 has been described. On the other hand, it is also assumed that the user terminal 40 acquires the Precure ID from the settlement server 60 using another application program (hereinafter also referred to as a Precure application) different from the above-described application program for the store based on the one-time code acquired by the software token. Therefore, in this modification example, a form in which the Precure ID can be linked to the application program for the store even when the Precure ID is acquired by the Precure application will be described.

[0249] When the Precure app independently obtains a Precure ID, for example, the application program for the store may use technologies such as APIs to share the Precure ID obtained by the Precure app between software, similar to the case of the software token described above. In this case, the control unit 400 of the user terminal 40 cooperates with the application program for the store to send a second cooperation instruction including the shared Precure ID, the company ID, the store ID, the transaction ID, and the user terminal ID of its own user terminal 40 to the server device 10. Further, when the control unit 100 of the server device 10 receives the second cooperation instruction, it registers the Precure ID in the data entry of the check-in management DB 146 corresponding to the transaction ID included in the second cooperation instruction. Thereby, the Precure ID independently obtained by the software token can be linked to the transaction processing system 1.

[0250] Also, as another method, it may be configured to transfer the Precure ID obtained by the Precure app to the application program for the store via an external device such as the attendant terminal 30. In this case, for example, the control unit 300 of the attendant terminal 30 displays an ID cooperation support screen as shown in FIG. 35 to accept the input of the Precure ID.

[0251] FIG. 35 is a diagram showing an example of the cooperation support screen G displayed on the attendant terminal 30 of Modification 2. As shown in FIG. 35, the cooperation support screen G has a Precure ID input field Ga.

[0252] The Precure ID obtained by the Precure app is input into the Precure ID input field Ga. The Precure ID may be manually input via the operation unit 36 or input via a code reader or the like.

[0253] In addition, on the cooperation support screen D, an issuance button Gb is provided for instructing to convert the prepaid card ID into a form that can be received by the application program for the store of the user terminal 40. When the operator of the attendant terminal 30 inputs the prepaid card ID into the prepaid card ID input field Ga and operates the issuance button Gb, the control unit 300 of the attendant terminal 30 generates a code symbol by encoding the prepaid card ID input into the prepaid card ID input field Ga into a two-dimensional code or the like. Then, the control unit 300 of the attendant terminal 30 causes the display unit 35 to display an issuance screen representing the generated code symbol. Note that the issuance screen may have the same screen configuration as that of FIG. 22 described above.

[0254] The user inputs the prepaid card ID into the user terminal 40 by imaging the code symbol displayed in the first area Ea with the imaging unit 47 of the user terminal 40. Specifically, the control unit 400 of the user terminal 40 obtains the prepaid card ID included in the code symbol by decoding the code symbol. Further, the control unit 400 of the user terminal 40 transmits a second cooperation instruction including the obtained prepaid card ID, the company ID, the store ID, the transaction ID, and the user terminal ID of its own user terminal 40 to the server device 10. Then, when receiving the second cooperation instruction, the control unit 100 of the server device 10 registers the prepaid card ID in the data entry of the check-in management DB 146 corresponding to the transaction ID included in this second cooperation instruction. Thereby, the prepaid card ID uniquely obtained by the software token can be linked to the transaction processing system 1.

[0255] FIG. 36 is a sequence diagram showing an example of the second cooperation process performed by the transaction processing system 1 of this modification. Note that in FIG. 36, a processing example in the case of inputting the prepaid card ID into the user terminal 40 via the attendant terminal 30 will be described. Also, as a premise of this process, it is assumed that the check-in process has been completed.

[0256] First, the control unit 300 of the attendant terminal 30 accepts the input of the prepaid ID via the above-described prepaid ID input field Ga or the like (step S141). Next, the control unit 300 encodes the prepaid ID received in step S41 into a code symbol (step S142), and causes the display unit 35 to display the generated code symbol (step S143).

[0257] The user who operates the user terminal 40 inputs the prepaid ID held in the code symbol into the user terminal 40 by imaging the code symbol displayed on the display unit 35 of the attendant terminal 30 using the imaging unit 47.

[0258] Specifically, the control unit 400 of the user terminal 40 decodes the code symbol imaged by the imaging unit 47 to read the prepaid ID held in the code symbol (step S144). Next, the control unit 400 transmits a second cooperation instruction including the prepaid ID read in step S44, the user terminal ID of its own terminal, the company ID and store ID of the store during check-in, to the server device 10 (step S145).

[0259] When the control unit 100 of the server device 10 receives the second cooperation instruction from the user terminal 40, it registers the prepaid ID in the data entry of the check-in management DB146 corresponding to the transaction ID included in this second cooperation instruction (step S146). Next, the control unit 100 transmits a balance request including the prepaid ID to the settlement server 60 (step S147).

[0260] When the control unit 600 of the settlement server 60 receives the balance request from the server device 10, it reads out the charge balance associated with the prepaid ID indicated in the balance request from the prepaid ID management DB642 (step S148). Next, the control unit 600 transmits the read charge balance to the server device 10 (step S149).

[0261] When the control unit 100 of the server device 10 receives the charge balance from the payment server 60, it transmits this charge balance to the user terminal 40 that sent the second cooperation instruction (step S150). Note that the control unit 100 of the server device 10 may transmit the charge balance to the user terminal 40 together with the prepaid card ID.

[0262] When the control unit 400 of the user terminal 40 receives the charge balance from the server device 10, it displays it on the display unit 45 as user information together with the prepaid card ID (step S151). For example, the control unit 400 causes the charge balance to be displayed in the second area Ab of the purchase support screen A described above. Thereby, in the transaction processing system 1, the prepaid card ID uniquely acquired by the prepaid card application can be linked to the transaction processing system 1.

[0263] Note that in the cart terminal 50, when a prepaid card ID is input in the one-time code input field Cb of the check-in screen C, the input prepaid card ID is linked to the transaction processing system 1 by performing the same processing as the above-described user terminal 40. However, it is assumed that the one-time code and the prepaid card ID can be distinguished due to differences in the code system and the like.

[0264] (Modification Example 3) In the above-described embodiment, the server device 10 and the payment server 60 are different server devices, but the present invention is not limited to this, and the server device 10 and the payment server 60 may be realized by the same server device (or cloud).

[0265] (Modification Example 4) In the above-described embodiment, the form using the member ID and the prepaid card ID has been described, but a configuration using only the prepaid card ID and not using the member ID, that is, a form not using the point service may be used.

[0266] Also, in the above-described embodiment, the member ID and the prepaid card ID have been described as being different. However, the present invention is not limited to this, and for example, by using the same ID, the member ID may also serve as the prepaid card ID (or the prepaid card ID may also serve as the member ID). In this case, for example, the payment server 60 only performs authentication of the prepaid card ID, and the server device 10 performs point management for the prepaid card ID for which authentication has been successful.

[0267] As a result, since the member ID and the prepaid card ID can be made common to provide a point service and a prepaid payment service, it is possible to efficiently manage the ID related to the user.

[0268] (Modification Example 5) In the above-described embodiment, the server device 10 determines whether or not the total amount of the products registered by the operation of the user at the registration terminal exceeds the remaining recharge amount of the user. However, the present invention is not limited to this, and the determination may be made on the registration terminal side.

[0269] In this case, the control unit 400 of the registration terminal may determine whether or not the total amount of the products registered at its own terminal exceeds the remaining recharge amount by comparing the total amount of the products registered at the registration terminal with the remaining recharge amount based on the recharge amount transmitted from the server device 10. Then, when the control unit 400 of the registration terminal determines that the total amount exceeds the remaining recharge amount, the control unit 400 performs various displays related to the above-described notification screen F (see FIG. 30) and the notification of insufficient balance.

[0270] In this case as well, it is preferable to limit the number of times the notification screen is displayed to, for example, the first time. For example, the control unit 400 of the registration terminal may refer to the check-in management DB 146 and control the number of times the notification screen F is displayed while switching the notification flag of the corresponding transaction ID. Also, for example, the control unit 400 of the registration terminal may control the number of times the notification screen F is displayed and the like based on the notification method (number of transmissions, etc.) set in the store setting information or user setting information of the corresponding store ID.

[0271] (Modification Example 6) 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 thereto, and the form of performing accounting processing using the user terminal 40 or the cart terminal 50 may also be used. In this case, for example, the control unit 400 of the user terminal 40 may be configured to display a selection screen on the display unit 45 that can select a payment method, and perform payment for the product using the payment method selected from the selection screen, similar to the accounting device 20.

[0272] Also, in this case, the selection screen for the payment method may be provided with an option for instructing to perform payment using the accounting device 20. When such an option is operated, the user terminal 40 can perform accounting for the product in the same procedure as the above-described accounting processing sequence by displaying a code symbol including the transaction ID on the display unit 45.

[0273] (Modification Example 7) In the above-described embodiment, the form in which the user performs the linkage of the prepaid card ID at the stage of operating the registration device before operating the accounting device 20 has been described. However, the present invention is not limited thereto, and the linkage of the prepaid card ID may be performed at the stage of operating the accounting device 20.

[0274] In this case, the control unit 200 of the accounting device 20, similar to the registration device, displays a screen on the display unit 25 where a one-time code can be input, and transmits a linkage instruction including the input one-time code, the company ID, the store ID, the transaction ID, etc. to the server device 10 to perform the linkage of the prepaid card ID. Note that the control unit 100 of the server device 10 transmits the one-time code to the payment server 60 in response to the linkage instruction from the accounting device 20, and transmits the prepaid card ID and the remaining charge obtained from the payment server 60 to the accounting device 20.

[0275] Thereby, since the linkage of the prepaid card ID can be performed at the stage of operating the accounting device 20, similar to the registration device, it is possible to improve the convenience of the prepaid payment service.

[0276] (Modification Example 8) In the above-described embodiment, a form in which a plurality of settlement methods can be selected has been described. However, the present invention is not limited to this, and accounting processing may be performed in a form limited to a specific settlement method. For example, accounting processing may be performed in a form limited to a prepaid settlement service provided by the store at the check-in destination.

[0277] (Modification Example 9) In the above-described embodiment, a form in which a code symbol is used to transmit a transaction ID from a registration terminal to the accounting device 20 has been described. However, the present invention is not limited to this form, and it may be a form of transmission 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.

[0278] (Modification Example 10) In the above-described embodiment, an example in which a transaction ID is used as specific information that can identify the recharge destination where electronic money is recharged and the breakdown of the registered products has been shown. However, the present invention is not limited thereto.

[0279] For example, the registration terminal may output, in the form of a code symbol or the like, specific information that can identify the corresponding transaction ID in the check-in management DB 146 and the transaction management DB 147. Specifically, the specific information can be realized by combining all the information of the company ID, store ID, terminal ID (user terminal ID, cart terminal ID), and check-in date and time, or by combining any of the information.

[0280] Further, for example, the registration terminal may acquire check-in data and transaction data corresponding to the transaction ID from the server device 10 and output these data as specific information in the form of a code symbol or the like.

[0281] (Modification Example 11) In the above-described embodiment, the server device 10 is configured to manage the number of points. However, the present invention is not limited to this, and another server device different from the server device 10 (hereinafter also referred to as an external server) may be configured to manage the number of points.

[0282] In this case, for example, the external server uses the above-described point management DB 144 to manage the number of points and the remaining recharge amount for each user for each store. Further, when the external server receives an inquiry specifying a member ID together with a store ID from the server device 10 or the accounting device 20, the external server is configured to reply with the number of points corresponding to the specified set to the inquirer.

[0283] Thereby, in the transaction processing system 1 according to this modification example, the server device 10 can achieve the same effects as those of the above-described embodiment without managing the member ID of each user. Note that the external server may be configured by different server devices for each store.

[0284] (Modification Example 12) In the above-described embodiment, the server device 10 is configured to control the display times of the notification screen (see FIG. 30) displayed when the total amount exceeds the remaining recharge amount. However, the present invention is not limited to this, and the registration terminal may be configured to perform the control.

[0285] For example, the registration terminal may control the display / non-display, the display times, etc. of the notification screen based on the store setting information and the user setting information received from the server device 10 at the time of check-in. As an example, when it is set in the store setting information and the user setting information to make the notification screen non-displayed, the control unit 400 of the registration terminal makes the notification screen non-displayed even when receiving the insufficient balance information from the server device 10. Further, as an example, when it is set in the store setting information and the user setting information that the display times of the notification screen are unlimited, the control unit 400 of the registration terminal displays the notification screen every time it receives the insufficient balance information from the server device 10. Note that when the registration terminal controls the display of the notification screen, the management of the notification flag by the server device 10 may not be necessary.

[0286] As a result, the settings related to the display of the notification screen can be customized for each user, thereby improving convenience.

[0287] Note that the programs executed by the respective devices in the above-described embodiments are provided in a state pre-installed in a ROM, a storage unit, or the like. The programs executed by the respective devices in the above-described embodiments may be configured to be recorded on a computer-readable recording medium such as a CD-ROM, a flexible disk (FD), a CD-R, or a DVD (Digital Versatile Disk) in an installable format or an executable format file and provided.

[0288] Furthermore, the programs executed by the respective devices in the above-described embodiments may be configured to be stored on a computer connected to a network such as the Internet and provided by being downloaded via the network. Also, the programs executed by the respective devices in the above-described embodiments may be configured to be provided or distributed via a network such as the Internet.

[0289] As described above, the embodiments of the present invention have been described. However, these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments and their modifications can be implemented in various other forms, and various omissions, replacements, changes, and combinations can be made without departing from the gist of the invention. These embodiments and their modifications are included in the scope and gist of the invention and are included in the invention described in the claims and its equivalent scope.

Explanation of Reference Numerals

[0290] 1 Transaction Processing System 10 Server Device 20 Accounting Device 30 Attendant Terminal 40 User Terminal 50 Cart Terminal 60 Settlement Server 100 Control Unit 200 Control Unit 300 Control Unit 400 Control Unit 500 Control Unit 600 Control Unit

Prior Art Documents

Patent Documents

[0291]

Patent Document 1

Claims

1. A server device capable of communicating with a terminal device operated by a customer who has visited a store, comprising: first receiving means for receiving an input of a one-time code related to the use of an electronic payment service from the terminal device; acquiring means for transmitting the one-time code received by the first receiving means to a payment server that authenticates a user of the electronic payment service based on the one-time code, and acquiring user information of the user related to the one-time code from the payment server; transmitting means for transmitting the user information acquired by the acquiring means to the terminal device; A server device comprising:

2. The acquiring means acquires user identification information capable of identifying the user from the payment server as the user information. The server device according to claim 1.

3. The acquiring means acquires balance information indicating the balance of electronic money charged by the user to the electronic payment service from the payment server as the user information. The server device according to claim 1 or 2.

4. The server device further comprises management means for managing the user identification information acquired by the acquiring means in association with specific information capable of identifying the terminal device or specific information capable of identifying a transaction performed using the terminal device. The server device according to claim 2.

5. The server device further comprises second receiving means for receiving a request for referring to the balance of electronic money charged by the user to the electronic payment service from the terminal device, the acquiring means acquires balance information indicating the balance of the electronic money from the payment server using the user identification information associated with the specific information of the terminal device that transmitted the reference request among the user identification information managed by the management means, and the transmitting means transmits the balance information acquired by the acquiring means to the terminal device that transmitted the reference request. The server device according to claim 4.

6. A transaction processing system having a terminal device operated by a customer who has visited a store and a server device capable of communicating with the terminal device, wherein the terminal device comprises: receiving means for receiving an input of a one-time code related to the use of an electronic payment service; first transmitting means for transmitting the one-time code received by the receiving means to the server device; and the server device comprises: receiving means for receiving the one-time code from the terminal device; ​ A settlement server that authenticates users of the electronic payment service based on a one-time code, a transmission means for transmitting the one-time code received by the reception means, and an acquisition means for acquiring user information of the user related to the one-time code from the settlement server; A second transmission means for transmitting the user information acquired by the acquisition means to the terminal device; Comprising: A transaction processing system.

Images