Stamp applying device, stamp applying method, and stamp applying program

Abstract

A stamp giving device, a stamp giving method, and a stamp giving program are provided that can more efficiently execute a process of giving a stamp based on information related to payment. [Solution] In the communication system S, the system control unit of the stamp card management server comprises: a user identification information acquisition means for acquiring user identification information for identifying each user who has applied to use a stamp card; a payment information search means for searching for payment information including payment source identification information for identifying the user identified by the acquired user identification information as the payment source, which indicates that a payment has been made from the user to the provider of the transaction target to pay the transaction price; and a stamp granting means for executing a process of granting a stamp to the user identified by the acquired user identification information, on the condition that corresponding payment information is found.

Description

[Technical Field]

[0001] The present invention relates to a method for applying a stamp to an electronic stamp card. [Background technology]

[0002] It has been known to use electronic stamp cards as a form of promotion. For example, a promotion targets a provider of a product or service, and consumers are given stamps on the stamp card on the condition that they pay the provider electronically. As an example, Patent Document 1 discloses that when a stamp accumulation function is selected, a seller's smartphone recognizes a code displayed on a buyer's smartphone, and after the seller enters the payment amount, the payment amount and stamp information are transmitted to a mobile wallet management system so that stamps corresponding to the payment are accumulated, and stamps are generated upon payment. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2015-176469 A Summary of the Invention [Problem to be solved by the invention]

[0004] However, in conventional technology, the process of applying a stamp is performed each time a payment is made based on information about the payment, which results in low processing efficiency.

[0005] The present invention has been made in consideration of the above points, and one example of its objective is to provide a stamp-application device, a stamp-application method, and a stamp-application program that can more efficiently perform processes related to the application of stamps when applying stamps based on payment information. [Means for solving the problem]

[0006] One aspect of the present application is a stamp granting device characterized by comprising: a user identification information acquisition means for acquiring any of the user identification information from a user identification information storage means that stores user identification information for identifying each user who has applied to use an electronic stamp card; a payment information search means for searching, from a payment information storage means that stores, for each payment, payment information indicating that a payment has been made for payment of a transaction price from a user to a provider of a transaction object, the payment information including payment source identification information for identifying the user who paid the price, for the payment information including payment source identification information for identifying the user identified by the acquired user identification information as the payment source; and a stamp granting means that, on condition that the search by the payment information search means finds the relevant payment information, executes a process of granting a stamp to the user identified by the acquired user identification information.

[0007] According to this aspect, the user identification information acquisition means stores user identification information for identifying a user who has applied to use a stamp card. User identification information is acquired from the user identification information acquisition means. Payment information including payment source identification information for identifying the user identified by the acquired user identification information as the payment source is searched for. The payment information indicates that a payment has been made from the user to the provider of the transaction object to pay the transaction price. A stamp is granted to the user on the condition that corresponding payment information is found. Therefore, there is no need to execute processing related to the granting of a stamp for payment information indicating that a user who did not apply to use a stamp card has made a payment to pay the price. This eliminates the need to execute processing each time a payment occurs, and therefore, when a stamp is granted based on payment information, the processing related to the granting of a stamp can be executed more efficiently.

[0008] Another aspect of the present application is a stamp granting device further comprising request information receiving means for receiving, from a terminal device of either the provider of the transaction object as the source of the stamp grant or the user as the recipient of the stamp, request information indicating a request for granting of a stamp, the request information including user identification information for identifying the user to whom the stamp is to be granted, wherein the user identification information acquisition means searches the user identification information storage means for user identification information for identifying the same user as the user identified by the user identification information included in the received request information, the payment information search means performs a search for the payment information on the condition that the search by the user identification information acquisition means finds the corresponding user identification information, and the stamp granting means does not grant the stamp if the corresponding user identification information is not found.

[0009] According to this aspect, request information is transmitted from the terminal device of either the provider of the transaction object as the source of the stamp or the user as the recipient of the stamp. The request information includes user identification information of the user as the recipient of the stamp. User identification information that identifies the same user as the user identified by the user identification information included in the request information is searched from the user identification information acquisition means. If the corresponding user identification information is found, a search for payment information is executed. If the corresponding user identification information is not found, the search for payment information is not executed and the stamp is not granted. Therefore, the process related to the granting of the stamp can be executed more efficiently by simply searching for payment information indicating that the user who requested the granting of the stamp, among the users who applied to use the stamp card, has made the payment for the price.

[0010] Yet another aspect of the present application is a stamp granting device characterized in that the user identification information storage means stores application information including the user identification information of the user who made the application and stamp card identification information for identifying the applied-for stamp card each time an application is made for the use of any of a plurality of digitized stamp cards, the received request information further includes stamp card identification information for identifying the stamp card corresponding to the stamp card provided by the provider who granted the stamp, the user identification information acquisition means searches for application information including a combination that matches the combination of the user identification information and the stamp card identification information included in the received request information, the payment information search means searches for the payment information on the condition that the user identification information acquisition means finds the corresponding application information, and the stamp granting means does not grant the stamp if the corresponding application information is not found.

[0011] According to this aspect, the user identification information storage means stores application information. The application information includes the user identification information of the user who has applied to use the stamp card and the stamp card identification information of the stamp card for which use has been applied. The request information includes the stamp card identification information of the stamp card corresponding to the provider who issued the stamp. Application information containing a combination that matches the combination of user identification information and stamp card identification information included in the request information is searched for. If there is matching application information, a search for payment information is executed. If there is no matching application information, a search for payment information is not executed and the stamp is not issued. Therefore, even if a user is related to the issuance of a stamp, there is no need to search for payment information for users who have not applied to use the stamp card related to the issuance of a stamp. This makes it possible to execute the process related to the issuance of stamps more efficiently.

[0012] Yet another aspect of the present application is a stamp applying device characterized in that the received request information further includes provider identification information for identifying the provider who has granted the stamp, the stored payment information further includes payee identification information for identifying the provider to whom the fee is to be paid, and the payment information search means searches for the payment information including the payment source identification information for identifying the user identified by the user identification information included in the received request information as the payer, and the payee identification information for identifying the provider identified by the provider identification information included in the received request information as the payee.

[0013] According to this aspect, the request information includes provider identification information of the provider who has granted the stamp. Payment information is searched for, including payment source identification information for identifying the user identified by the user identification information included in the request information as the payment source, and payment recipient identification information for identifying the provider identified by the provider identification information included in the information request information as the payment recipient. If matching payment information is found, the stamp is granted. Therefore, the stamp can be granted on the condition that the user to whom the stamp is to be granted has paid the price to the provider who granted the stamp.

[0014] According to yet another aspect of the present application, there is provided a stamp applying device further comprising code sending means for sending a code indicating information of the other party to a terminal device used by the other of the provider and the user, wherein the terminal device used by the one of the provider and the user reads the code received from the stamp applying device by the terminal device used by the other party and transmits to the stamp applying device request information including the information of the other party indicated by the read code and information of the one party using the terminal device that read the code, wherein information of the user among the information of the one party and the information of the other party included in the request information includes the user identification information, and the terminal device used by the provider displays a screen that accepts an operation to select either a first method in which the terminal device outputs the code indicating the information of the provider or a second method in which the terminal device reads the code indicating the information of the user, as a method of applying the stamp, and when the first method is selected on the screen, the terminal device used by the provider receives the code indicating the information of the provider from the stamp applying device, and when the second method is selected on the screen, reads the code indicating the information of the user and transmits the request information to the stamp applying device.

[0015] According to this aspect, a code indicating information about the other of the provider of the transaction object as the source of the stamp and the user as the recipient of the stamp is transmitted to a terminal device used by the other of the provider and the user. The terminal device used by one of the provider and the user reads the code received by the terminal device used by the other. The terminal device used by the other transmits request information including the information indicated by the read code and information about the other person using the terminal device. Thus, the request information includes information about the provider and the user. The provider information includes stamp card identification information. The user information includes user identification information. The terminal device used by the provider displays a screen accepting an operation for selecting a method for applying the stamp. If the first method is selected, the terminal device used by the provider receives a code indicating information about the provider from the stamp applying device. If the second method is selected, the terminal device used by the provider reads the code indicating information about the user and transmits information about the provider and the user to the stamp applying device. Thus, the provider of the transaction object can select a method for applying the stamp.

[0016] Yet another aspect of the present application is a stamp application device further comprising: transaction service action history information acquisition means for acquiring transaction service action history information indicating a history of actions taken with respect to a transaction service that enables electronic commerce, the history being a history of actions taken by the user identified by the acquired user identification information; and non-transaction service action history information acquisition means for acquiring non-transaction service action history information indicating a history of actions taken with respect to a non-transaction service different from the transaction service, the history being a history of actions taken by the user identified by the acquired user identification information, wherein the stamp application means changes the number of stamps to be applied based on the history of actions with respect to the transaction service indicated by the acquired transaction service action history information and the history of actions with respect to the non-transaction service indicated by the acquired non-transaction service action history information.

[0017] According to this aspect, transaction service behavior history information and non-transaction service behavior history information of the user to whom the stamp is to be granted are obtained. The transaction service behavior history information indicates a history of behaviors taken with respect to transaction services that enable electronic commerce. The non-service behavior history information indicates a history of behaviors taken with respect to non-transaction services that are different from transaction services. The number of stamps granted varies based on these histories. Therefore, the number of stamps granted can be changed depending on the behaviors the user has taken in transaction services and non-transaction services.

[0018] Yet another aspect of the present application is a stamp-application device characterized in that, when the user makes a transaction with the transaction service, the acquired transaction service action history information indicates the content of the transaction, and when the user takes action to sign up for the non-transaction service or to cancel the contract, the acquired non-transaction service action history information indicates the action taken between the action to sign up for the contract and the action to cancel the contract, and the stamp-application means assigns a greater number of stamps when a predetermined condition is met than when the condition is not met, and the predetermined condition is that the content of the transaction meets a predetermined transaction content condition and the non-transaction service is currently under contract.

[0019] According to this aspect, if a user satisfies the conditions that the transaction content in the transaction service meets the predetermined transaction content conditions and that the user is also under contract for a non-transaction service, the number of stamps awarded will be greater than if the conditions were not met, thereby encouraging the use of both transaction services and non-transaction services.

[0020] Yet another aspect of the present application is a stamp-application device characterized in that the stored payment information further includes amount information indicating the amount paid, and the stamp-application means changes the number of stamps to be applied depending on the amount indicated by the amount information included in the payment information searched by the payment information search means.

[0021] According to this aspect, the number of stamps given to the user can be changed depending on the amount paid.

[0022] Yet another aspect of the present application is a stamp granting device further comprising a point granting means for granting points that can be used for payment to a user to whom a stamp is granted when the stamp is granted by the stamp granting means.

[0023] According to this aspect, when a stamp is given to a user, the user is given points in addition to the stamp, which can further encourage the use of the stamp card.

[0024] Yet another aspect of the present application is a stamp-granting device, characterized in that the point-granting means grants points that can be used both for transaction services that enable electronic commerce and for non-transaction services that are different from the transaction services.

[0025] According to this aspect, the awarded points can be used for both transaction services that enable electronic commerce and non-transaction services that are different from transaction services, thereby encouraging the use of both transaction services and non-transaction services.

[0026] Yet another aspect of the present application is a stamp-giving device characterized in that the number of stamps given by the stamp-giving means may vary, and the point-giving means gives points in a number corresponding to the number of stamps given by the stamp-giving means.

[0027] According to this aspect, points can be awarded in a number corresponding to the number of stamps awarded.

[0028] Yet another aspect of the present application is a stamp granting device further comprising: transaction service action history information acquisition means for acquiring transaction service action history information indicating a history of actions taken with respect to a transaction service that enables electronic commerce, the history being a history of actions taken by the user identified by the acquired user identification information; and non-transaction service action history information acquisition means for acquiring non-transaction service action history information indicating a history of actions taken with respect to a non-transaction service different from the transaction service, the history being a history of actions taken by the user identified by the user identification information included in the acquired user information, wherein the point granting means changes the number of points to be granted based on the history of actions with respect to the transaction service indicated by the acquired transaction service action history information and the history of actions with respect to the non-transaction service indicated by the acquired non-transaction service action history information.

[0029] According to this aspect, transaction service behavior history information and non-transaction service behavior history information of the user to whom the stamp is to be awarded are obtained. The transaction service behavior history information indicates a history of behaviors taken with respect to transaction services that enable electronic commerce. The non-service behavior history information indicates a history of behaviors taken with respect to non-transaction services that are different from transaction services. The number of points awarded varies based on these histories. Therefore, the number of points awarded can be changed depending on the behaviors the user has taken in transaction services and non-transaction services.

[0030] Yet another aspect of the present application is a stamp-giving device characterized in that, when the user makes a transaction with the transaction service, the acquired transaction service action history information indicates the content of the transaction, and when the user takes action to sign up for the non-transaction service or to cancel the contract, the acquired non-transaction service action history information indicates the action taken out of the action to sign up or the action to cancel the contract, and the point-giving means awards a greater number of points when a predetermined condition is met than when the condition is not met, and the predetermined condition is that the content of the transaction meets a predetermined transaction content condition and the non-transaction service is currently under contract.

[0031] According to this aspect, if a user's transaction in a transaction service satisfies predetermined transaction content conditions and also satisfies the condition of being under contract for a non-transaction service, the number of points awarded to the user will be greater than if the user does not satisfy these conditions, thereby encouraging the use of both transaction services and non-transaction services.

[0032] Yet another aspect of the present application is a stamp-granting device characterized in that the stored payment information further includes amount information indicating the amount paid, and the point-granting means changes the number of points to be awarded depending on the amount indicated by the amount information included in the payment information searched by the payment information search means.

[0033] According to this aspect, the number of points awarded to the user can be changed depending on the amount paid by the user.

[0034] Yet another aspect of the present application is a stamp-application device, characterized in that the user identification information acquisition means acquires each of the user identification information stored in the user identification information storage means, and the payment information search means searches for the payment information for each of the acquired user identification information.

[0035] According to this aspect, processing related to the granting of stamps can be executed for each user who has applied to use the stamp card.

[0036] In yet another aspect of the present application, the user identification information storage means stores, each time an application is made for use of any one of a plurality of digitized stamp cards, application information including the user identification information of the user who made the application and stamp card identification information for identifying the stamp card applied for, and for each of the plurality of stamp cards, the stamp card identification information for identifying the stamp card and provider identification information for identifying a provider corresponding to the stamp card among providers of the transaction object are associated and stored in the provider identification information storage means, and the stored payment information is stored as a payment address for identifying a provider to whom the fee is to be paid. The stamp application device further includes identification information, wherein the user identification information acquisition means acquires any of the application information from the user identification information storage means and further includes a provider identification information acquisition means for acquiring from the provider identification information storage means the provider identification information associated with the stamp card identification information included in the acquired application information, and the payment information search means searches for the payment information including the payment source identification information for identifying the user identified by the user identification information included in the acquired application information as the payment source, and the payment destination identification information for identifying the acquired provider identification information as the payment destination.

[0037] According to this aspect, payment information including payment source identification information for identifying the provider corresponding to the stamp card that the user has applied to use as the payment source is searched for. If the corresponding payment information is found, a stamp is granted to the user. Therefore, a stamp can be granted on the condition that the user has paid the amount to be paid to the provider corresponding to the stamp card that the user has applied to use.

[0038] Yet another aspect of the present application is a stamp-granting device characterized in that for each user who has applied to use an electronic stamp card, the number of stamps is stored in a stamp number storage means in association with user identification information for identifying the user, and the stamp-granting means increases the number of stamps associated with the acquired user identification information and grants the stamp.

[0039] Yet another aspect of the present application is a stamp granting method executed by a computer, comprising: a user identification information acquisition step of acquiring any of the user identification information from a user identification information storage means that stores user identification information for identifying each user who has applied to use an electronic stamp card; a payment information search step of searching for payment information indicating that a payment has been made for payment of a transaction price from a user to a provider of a transaction object, the payment information including payment source identification information for identifying the user who paid the price, from a payment information storage means that stores, for each payment, payment information including payment source identification information for identifying the user who paid the price; and a stamp granting step of executing a process of granting a stamp to the user identified by the acquired user identification information, on the condition that the relevant payment information is found by the search in the payment information search step.

[0040] Yet another aspect of the present application is a stamp-assigning program that causes a computer to function as: user identification information acquisition means that acquires any of the user identification information from user identification information storage means that stores user identification information for identifying each user who has applied to use an electronic stamp card; payment information search means that searches for payment information indicating that a payment has been made for payment of a transaction price from a user to a provider of a transaction object, the payment information including payment source identification information for identifying the user who paid the price, from payment information storage means that stores, for each payment, payment information including payment source identification information for identifying the user who paid the price; and stamp assignment means that, on condition that the search by the payment information search means finds the relevant payment information, executes a process of assigning a stamp to the user identified by the acquired user identification information. [Effects of the Invention]

[0041] According to the present invention, when a stamp is applied based on payment information, the process for applying the stamp can be executed more efficiently. [Brief explanation of the drawings]

[0042] [Figure 1] 1 is a diagram illustrating an example of a schematic configuration of a communication system S according to an embodiment. [Figure 2] FIG. 10 is a diagram showing an example of a processing flow up to when a store logs in to a stamp presentation tool. [Figure 3] FIG. 10 is a diagram showing an example of a processing flow up to the stamp application. [Figure 4] 1 is a block diagram showing an example of a schematic configuration of a stamp card management server 1 according to an embodiment. [Figure 5] 10 is a diagram showing an example of the contents stored in the database of the stamp card management server 1. FIG. [Figure 6] FIG. 10 is a diagram illustrating an example of an account registration status. [Figure 7]1 is a block diagram showing an example of a schematic configuration of a member information management server 2 according to an embodiment. [Figure 8] 10 is a diagram showing an example of the contents stored in the database of the member information management server 2. FIG. [Figure 9] 2 is a block diagram showing an example of a schematic configuration of a store terminal 5 according to an embodiment. FIG. [Figure 10] 2 is a diagram showing an example of functional blocks of a system control unit 11 of the stamp card management server 1 according to an embodiment. FIG. [Figure 11] FIG. 10 is a diagram illustrating an example of an account registration screen. [Figure 12] 2 is a diagram showing an example of functional blocks of a system control unit 51 of a store terminal 5 according to an embodiment. FIG. [Figure 13] FIG. 10 is a diagram illustrating an example of a login screen. [Figure 14] (a) is a diagram showing an example of a code displaying number of stamps selection screen, (b) is a diagram showing an example of a code display screen for a store terminal, and (c) is a diagram showing an example of a code reading screen for a user terminal. [Figure 15] (a) is a diagram showing an example of a code display screen for a user terminal, (b) is a diagram showing an example of a code reading screen for a store terminal, and (c) is a diagram showing an example of a code reading screen for selecting the number of stamps to be given. [Figure 16] FIG. 10 is a sequence diagram showing an example of the operation of the communication system S when registering a stamp card and a store that is a promotion target. [Figure 17] FIG. 10 is a sequence diagram showing an example of the operation of the communication system S when a user applies for use of a stamp card. [Figure 18] FIG. 10 is a sequence diagram showing an example of the operation of the communication system S when a store logs in to a stamp presentation tool. [Figure 19] FIG. 10 is a sequence diagram showing an example of the operation of the communication system S when the store terminal 5 displays a code and gives a stamp. [Figure 20]FIG. 10 is a sequence diagram showing an example of the operation of the communication system S when the store terminal 5 reads a code and gives a stamp. [Figure 21] 10 is a flowchart showing an example of stamp control processing executed by a system control unit 11 of the stamp card management server 1 according to an embodiment. [Figure 22] 10 is a flowchart showing an example of a stamp giving process executed by a system control unit 11 of the stamp card management server 1 according to an embodiment. [Figure 23] 1 is a diagram illustrating an example of a schematic configuration of a communication system S according to an embodiment. [Figure 24] FIG. 10 is a diagram showing an example of a processing flow up to the stamp application. [Figure 25] 1 is a block diagram showing an example of a schematic configuration of a member information management server 2 according to an embodiment. [Figure 26] 10 is a diagram showing an example of the contents stored in the action history DB 24b of the member information management server 2. FIG. [Figure 27] 1 is a block diagram showing an example of a schematic configuration of a stamp card management server 1 according to an embodiment. [Figure 28] 10 is a diagram showing an example of the contents stored in the database of the stamp card management server 1. FIG. [Figure 29] 2 is a diagram showing an example of functional blocks of a system control unit 11 of the stamp card management server 1 according to an embodiment. FIG. [Figure 30] FIG. 10 is a sequence diagram showing an example of the operation of the communication system S when the store terminal 5 displays a code and gives a stamp. [Figure 31] FIG. 10 is a sequence diagram showing an example of the operation of the communication system S when the store terminal 5 reads a code and gives a stamp. [Figure 32] 10 is a flowchart showing an example of a stamp control loop process executed by a system control unit 11 of the stamp card management server 1 according to an embodiment. [Figure 33]10 is a flowchart showing an example of stamp control processing executed by a system control unit 11 of the stamp card management server 1 according to an embodiment. [Figure 34] FIG. 10 is a diagram showing an example of the number of stamps given. [Figure 35] 10 is a flowchart showing an example of a stamp giving process executed by a system control unit 11 of the stamp card management server 1 according to an embodiment. [Figure 36] FIG. 10 is a diagram showing an example of the number of stamps given. [Figure 37] 10 is a flowchart showing an example of a stamp giving process executed by a system control unit 11 of the stamp card management server 1 according to an embodiment. [Figure 38] 1 is a diagram illustrating an example of a schematic configuration of a communication system S according to an embodiment. [Figure 39] 10 is a diagram showing an example of the contents stored in a behavior history DB 24b of the member information management server 2 according to an embodiment. FIG. [Figure 40] 2 is a diagram showing an example of functional blocks of a system control unit 11 of the stamp card management server 1 according to an embodiment. FIG. [Figure 41] FIG. 10 is a diagram showing an example of the number of stamps given. [Figure 42] 10 is a flowchart showing an example of a stamp giving process executed by a system control unit 11 of the stamp card management server 1 according to an embodiment. [Figure 43] 1 is a diagram illustrating an example of a schematic configuration of a communication system S according to an embodiment. [Figure 44] FIG. 2 is a block diagram showing an example of a schematic configuration of a point management server 7 according to an embodiment. [Figure 45] FIG. 10 is a diagram showing an example of the contents stored in the database of the point management server 7 according to an embodiment. [Figure 46] 2 is a diagram showing an example of functional blocks of a system control unit 11 of the stamp card management server 1 according to an embodiment. FIG. [Figure 47] 10A and 10B are diagrams showing examples of the number of points awarded. [Figure 48] FIG. 2 is a diagram showing an example of functional blocks of a system control unit 71 of a point management server 7 according to an embodiment. [Figure 49] 10 is a flowchart showing an example of stamp control processing executed by a system control unit 11 of the stamp card management server 1 according to an embodiment. [Figure 50] 10 is a flowchart showing an example of a point giving process executed by a system control unit 11 of the stamp card management server 1 according to an embodiment. [Figure 51] FIG. 10 is a diagram showing an example of the number of points awarded. [Figure 52] 10 is a flowchart showing an example of a point giving process executed by a system control unit 11 of the stamp card management server 1 according to an embodiment. [Figure 53] 2 is a diagram showing an example of functional blocks of a system control unit 11 of the stamp card management server 1 according to an embodiment. FIG. [Figure 54] FIG. 10 is a diagram showing an example of the number of points awarded. [Figure 55] 10 is a flowchart showing an example of a point giving process executed by a system control unit 11 of the stamp card management server 1 according to an embodiment. [Figure 56] FIG. 10 is a diagram showing an example of a processing flow up to the stamp application. [Figure 57] 1 is a block diagram showing an example of a schematic configuration of a stamp card management server 1 according to an embodiment. [Figure 58] 10 is a diagram showing an example of the contents stored in the database of the stamp card management server 1. FIG. [Figure 59] 10A is a diagram showing an example of a login screen, and FIG. 10B is a diagram showing an example of a downloadable stamp number selection screen. [Figure 60] FIG. 10 is a sequence diagram showing an example of the operation of the communication system S when the store terminal 5 receives print data for a code and applies a stamp. [Figure 61]10 is a flowchart showing an example of stamp control processing executed by the system control unit 11 when the stamp card management server 1 receives a stamp granting request from the user terminal 6. [Figure 62] 1 is a diagram illustrating an example of a schematic configuration of a communication system S according to an embodiment. [Figure 63] FIG. 10 is a diagram showing an example of a processing flow up to the stamp application. [Figure 64] 1 is a block diagram showing an example of a schematic configuration of a stamp card management server 1 according to an embodiment. [Figure 65] 10 is a diagram showing an example of the contents stored in a promotion target store DB 14j of the stamp card management server 1. FIG. [Figure 66] 2 is a diagram showing an example of functional blocks of a system control unit 11 of the stamp card management server 1 according to an embodiment. FIG. [Figure 67] 10 is a flowchart showing an example of stamp control processing executed by a system control unit 11 of the stamp card management server 1 according to an embodiment. [Figure 68] FIG. 10 is a diagram showing an example of a processing flow up to the stamp application. [Figure 69] 1 is a block diagram showing an example of a schematic configuration of a stamp card management server 1 according to an embodiment. [Figure 70] 10 is a diagram showing an example of the contents stored in a stamp request user DB 14k of the stamp card management server 1. FIG. [Figure 71] 6 is a diagram showing an example of functional blocks of a system control unit 11 of a stamp card management server 1 according to an embodiment. FIG. DETAILED DESCRIPTION OF THE INVENTION

[0043] [1. First embodiment] A first embodiment of the present invention will be described in detail below with reference to the drawings.

[0044] [1-1. Communication System Configuration] First, the configuration and functional overview of a communication system S according to this embodiment will be described with reference to Fig. 1 to Fig. 3. Fig. 1 is a diagram showing an example of the schematic configuration of a communication system S according to this embodiment.

[0045] As shown in Fig. 1, the communication system S may be configured to include a stamp card management server 1, a member information management server 2, an operator terminal 3, multiple promotion main terminals 4, multiple store terminals 5, and multiple user terminals 6. These devices may be connected to a network NW. The network NW is constructed, for example, by the Internet, a dedicated communication line (e.g., a CATV (Community Antenna Television) line), a mobile communication network (including base stations, etc.), a gateway, etc.

[0046] The stamp card management server 1 may be a server device that executes processing related to a predetermined stamp card service. This stamp card service may be a service that allows users to use digitized stamp cards. This stamp card may be used for promotions. The target of a stamp card promotion is called a promotion target. The promotion may include at least one of promoting the use of the promotion target, advertising, and sales promotion. Examples of promotion targets include facilities, places, businesses, organizations, etc. Examples of facilities or places include stores, offices, and public facilities. At least one promotion target may be a provider that offers a trading target. The trading target may be something that can be traded commercially. Examples of trading targets include goods and services. A provider may provide a trading target to a user in exchange for payment from the user. Examples of providers include stores and store operators. Hereinafter, the promotion target is assumed to be a store as an example. Furthermore, the entity that is the subject of a promotion using a stamp card is called a promoter. The promoter may be any of the promotion targets themselves, or may be a person different from the promotion target. For example, the headquarters of a certain restaurant chain may be the promoter, and one or more stores within that restaurant chain may be the promotion targets. Alternatively, for example, a local government in a certain region may be the promoter, and one or more facilities in that region may be the promotion targets. The promoter may pre-designate the facilities, individuals, etc. that will be the promotion targets. In a stamp card service, each promotion target may be able to add a stamp to a user's stamp card. For example, a user may go to a location where the promotion target is located. If the user meets predetermined conditions at that location, the promotion target may add a stamp to the user. Examples of predetermined conditions include using the promotion target, using a service provided by the promotion target, or purchasing a transaction target from the promotion target.The stamp card management server 1 manages information about promotion targets for each stamp card, and may also execute a process of adding stamps to stamp cards in response to requests from promotion targets or users. Adding a stamp may correspond to pressing a stamp on a stamp card.

[0047] The member information management server 2 may be a server device that manages information about members of a predetermined service. The predetermined service may include an online service or a service that can be provided using information and communication technology. The predetermined service may be, for example, a comprehensive Internet service. The comprehensive Internet service may be, for example, a collection of multiple services, with an online service as the primary service. The online service may include a service provided through a website. The online service may include a transaction service. The transaction service may be a service that enables electronic commerce between consumers and businesses or electronic commerce between consumers. At least one transaction service may include a service that enables businesses to operate an online store. The online store may be a virtual online store. Examples of services included in the comprehensive Internet service include an online shopping mall, a flea market service, a facility reservation service, a service reservation service, an online securities company, an online bank, a web search service, video streaming, a point program, a coupon service, a mobile communication service, carrier billing, an optical fiber connection service, credit card payments, app payments, electronic money, an online securities company, an online bank, a social networking service (SNS), a rich communication service (RCS) or instant messaging service, and an email service. The stamp card service described above may also be included in the Internet comprehensive service. For convenience, in this embodiment, the specified service is considered to be the Internet comprehensive service. A user ID may be assigned to each user who becomes a member of the Internet comprehensive service. The user ID is identification information for identifying a member in the Internet comprehensive service. The member information management server 2 may manage information about each member using the user ID. A user who becomes a member of the Internet comprehensive service may be able to use many of the services included in the Internet comprehensive service.In order to use some services, the user may be required to enter into a separate service agreement or register as a member of the Internet comprehensive service.

[0048] The administrator terminal 3 may be a terminal device used by an administrator of a stamp card service. For example, the administrator terminal 3 may be used to set information on each stamp card.

[0049] Each promotion host terminal 4 may be a terminal device used by a promoter. The promotion host terminal 4 may be used to register information about a stamp card used by the promoter for a promotion in the stamp card service.

[0050] Each store terminal 5 may be a terminal device used by a store employee as an example of a promotion target. The store terminal 5 may be used to provide stamps to stamp cards used in the store's promotion. Examples of the store terminal 5 include mobile information terminals such as smartphones and tablet computers, mobile phones, and PDAs (Personal Digital Assistants). A web browser may be installed in each store terminal 5. Each store terminal 5 may also be capable of executing a stamp presentation tool. The stamp presentation tool may be stamp presentation software for providing stamps to stamp cards in a stamp card service. The stamp presentation tool may be a program or an application. The stamp presentation tool may be, for example, a native application or a web application.

[0051] Each user terminal 6 may be a terminal device used by a user who is a member of the Internet comprehensive service. The user terminal 6 may be portable. The user can use the stamp card service by transmitting and receiving information between the user terminal 6 and the stamp card management server 1. Examples of the user terminal 6 include mobile information terminals such as smartphones and tablet computers, mobile phones, and PDAs. A web browser may be installed on each user terminal 6. Furthermore, each user terminal 6 may be capable of executing a stamp card app. The stamp card app may be an application that enables a user to earn stamps by using the stamp card service. The stamp card app may be a native application or a web application.

[0052] FIG. 2 is a diagram showing an example of the processing flow up to when a store logs in to the stamp presentation tool. First, the promoter applies to the operator of the stamp card service for a stamp card to be used in the promotion. For example, the promoter may apply as an applicant for an account for the stamp card presentation tool described above. This account may contain information about the promotion target who will be able to use the stamp card presentation tool. After accepting the application, the operator operates the operator terminal 3 to register the stamp card and the account with the card management server 1, as shown in FIG. 2 (step S1). The operator notifies the promoter of stamp card identification information and authentication information for logging in to the stamp card presentation tool. The stamp card identification information may be identification information for identifying the stamp card to be used in the promotion. Hereinafter, a card URL (Uniform Resource Locator) is used as an example of stamp card identification information. The authentication information may be information used for login authentication of the stamp card presentation tool. The authentication information may include, for example, promotion target identification information and knowledge information. The identification information may be information for identifying the promotion target. The knowledge information may be information that should be known only to the promotion target who is the subject of login authentication, excluding, for example, the operator and the promoter. Examples of knowledge information include a password, a PIN code, and a personal identification number. The promotion target identification information and the knowledge information may be separate pieces of information, or the knowledge information may also serve as the promotion target identification information. Hereinafter, as an example, authentication information will be assumed to include a password. The promoter notifies each store that is the target of the promotion of the stamp card identification information and authentication information. Different authentication information may be notified for each store. Note that at least one of the stamp card registration and account registration may be performed by the promoter himself using the promoter terminal 4.

[0053] The store employee downloads the stamp presentation tool from the stamp card management server 1 to the store terminal 5 (step S2). If the stamp presentation tool is a web application, step S2 can be omitted. The employee launches the stamp presentation tool and inputs stamp card identification information and authentication information. The store terminal 5 sends this stamp card identification information and authentication information to the stamp card management server 1 (step S3). The stamp card management server 1 performs login authentication based on the stamp card identification information and authentication information (step S4). If the login authentication is successful, the store employee logs in to the stamp presentation tool (step S5). This allows the store to use the stamp presentation tool to provide stamps.

[0054] Meanwhile, the user operates the user terminal 6 to enter a campaign for any stamp card registered in the stamp card service (step S6). Entering a stamp card campaign may correspond to applying to use that stamp card. For example, a list of stamp cards available for entry may be displayed on the screen of the stamp card app. The user may select a stamp card to enter from the list. Once the entry is accepted by the stamp card management server 1, the user may be able to use that stamp card.

[0055] FIG. 3 is a diagram showing an example of the processing flow up to stamping. There may be two methods for stamping. In the first method, the store terminal 5 displays a code for stamping, and the user terminal 6 reads the code. Reading the code may involve acquiring the code and obtaining information indicated by the acquired code from the code. In the second method, the user terminal 6 displays the code for stamping, and the store terminal 5 reads the code. The code may be, for example, optically or electrically readable information, a pattern, or a picture. Optically readable codes refer to codes that can be detected using devices such as a CCD (Charge-Coupled Device) sensor, a CMOS (Complementary Metal Oxide Semiconductor) sensor, or other optical or laser sensors. In this embodiment, a camera may be used. The code may include, for example, multiple geometric shapes. Examples of geometric shapes include rectangles, triangles, circles, and lines (thin rectangles). A shape formed by combining multiple such basic geometric shapes is also recognized as a geometric shape. Generally, it is extremely difficult for a human to identify the original information encoded in a code by looking at it. The code may be, for example, a two-dimensional code or a one-dimensional barcode. There are no particular limitations on the code standard. Examples of two-dimensional codes include QR Code (registered trademark), Data Matrix Code, and MaxiCode.

[0056] When the first method is used, as shown in FIG. 3, the store terminal 5 receives image data of the code from the stamp card management server 1 (step S11a). The store terminal 5 displays the code based on this image data (step S12a). The user terminal 6 reads the code displayed on the store terminal 5 (step S13a). The user terminal 6 sends a stamp granting request to the stamp card management server 1 based on information obtained from the read code (step S14a). The stamp granting request may be information indicating a request for granting a stamp. Upon receiving the stamp granting request, the stamp card management server 1 grants a stamp to the stamp card of the user, on the condition that the user of the user terminal 6 that sent the stamp granting request has entered the campaign for the stamp card in question (step S15). Note that the stamp card management server 1 may be configured so that users can use each stamp card without requiring entry.

[0057] When the second method is used, as shown in FIG. 3, the user terminal 6 receives image data of the code from the stamp card management server 1 (step S11b). The user terminal 6 displays the code based on this image data (step S12b). The store terminal 5 reads the code displayed on the user terminal 6 (step S13b). The store terminal 5 transmits a stamp granting request to the stamp card management server 1 based on information obtained from the read code (step S14b). The stamp granting request grants a stamp to the stamp card of the user, on the condition that the user of the user terminal 6 to which the code is sent has entered the campaign for the stamp card in question (step S15). Note that the stamp card management server 1 and the stamp presentation tool may be configured so that only one of the first method and the second method is possible.

[0058] [1-2.Device configuration] [1-2-1. Stamp card management server] Next, the configuration of the stamp card management server 1 will be described with reference to Fig. 4 to Fig. 6. Fig. 4 is a block diagram showing an example of the schematic configuration of the stamp card management server 1 according to this embodiment. As shown in Fig. 4, the stamp card management server 1 includes a system control unit 11, a system bus 12, an input / output interface 13, a storage unit 14, and a communication unit 15. The system control unit 11 and the input / output interface 13 are connected via the system bus 12.

[0059] The system control unit 11 includes a CPU (Central Processing Unit) 11a, a ROM (Read Only Memory) 11b, a RAM (Random Access Memory) 11c, and the like.

[0060] The input / output interface 13 performs interface processing between the storage unit 14 and the communication unit 15 and the system control unit 11 .

[0061] The storage unit 14 is configured, for example, with a hard disk drive or the like. Databases such as a stamp card DB 14a, a tool account DB 14b, an entry DB 14c, a stamp history DB 14d, and a benefit DB 14e may be stored in this storage unit 14. "DB" is an abbreviation for database. At least one database may be stored in a server device different from the stamp card management server 1. The stamp card management server 1 may be able to access the database via that server device.

[0062] FIG. 5 is a diagram illustrating an example of the contents stored in the database of the stamp card management server 1. The stamp card DB 14a may store stamp card information for each of multiple stamp cards registered in the stamp card service. The stamp cards registered in the stamp card service may be stamp cards that users can apply for or enter. For example, as shown in FIG. 5, the stamp card DB 14a may store stamp card information such as a card URL, a card name, a promotion master ID, a campaign period, benefit setting information, and stamp presentation limit information, all of which are associated with one another. The card URL may be identification information for identifying the stamp card. The card name may indicate the name of the stamp card. The promotion master ID may be identification information for identifying the promoter of the stamp card. The campaign period may indicate the period during which a campaign or promotion using the stamp card is implemented. Stamps may be awarded to the stamp card only during the campaign period. Note that a campaign period need not be set. In this case, stamps may be awarded to the stamp card for the period during which the stamp card information is stored in the stamp card DB 14a. The benefit setting information indicates information regarding a benefit that will be granted to a user on the condition that the user acquires a predetermined number of stamps. The benefit to be granted may be a benefit provided physically or electronically by the creator of the stamp card. Alternatively, the benefit to be granted may be a specific benefit provided electronically by the stamp card management server 1 or another server device. Examples of the benefit to be granted include coupons, prizes, points in a point program, electronic money, etc. The benefit setting information may include, for example, the number of benefit stamps, the name of the benefit, terms of use, etc. The number of benefit stamps indicates the number of stamps required to acquire a benefit. The number of benefit stamps may be the same as the number of stamp fields. The number of stamp fields may indicate the number of stamp fields provided on one stamp card. Examples of the number of stamp fields include 5, 10, etc. Each stamp field is an area where a stamp can be pressed.The number of stamp columns may be predetermined and common to all stamp cards. The benefit name indicates the name of the benefit so that the content of the benefit that can be obtained can be identified. The usage conditions indicate the conditions for using the benefit. A benefit may be obtained multiple times with one issued stamp card. In this case, multiple benefit setting information may be stored in the stamp card DB 14a. In this case, the number of benefit stamps may differ between multiple benefits. Here, the number of benefit stamps for any one of the multiple benefits may match the number of stamp columns. The stamp gift limit information is information indicating a stamp gift limit. The stamp gift limit may indicate any restrictions on the multiple stamps that may be awarded to the same user for that stamp card. The stamp gift limit information may be set, for example, to one of "one time per day per user per store," "one time per user per store for the entire period," or "unlimited." "One time per day per user per store" indicates that a stamp can be awarded to one user for one promotion target up to one time per day. "One user, one store, one time for the entire period" indicates that one user can receive stamps for one promotion target up to one time during the campaign period. "Unlimited" indicates that there is no limit on the amount of stamps that can be given. Note that there does not need to be a limit on the amount of stamps that can be given. Alternatively, a limit on the amount of stamps that can be given common to all stamp cards may be set in advance.

[0063] The tool account DB 14b may store stamp card identification information for identifying a stamp card and authentication information for logging in to a stamp presentation tool for awarding stamps to the stamp card, in association with each other. Specifically, the tool account DB 14b may store information related to the point presentation tool account for each stamp card. For example, as shown in FIG. 5, the tool account DB 14b may store a card URL and one or more pieces of account information in association with each other. The card URL may indicate the target stamp card. Each piece of account information may be information related to the account of the stamp card. Each piece of account information may include a store name and a password. The store name may indicate the name of the store that is the promotion target. The password may be authentication information. For example, the password may be knowledge information as well as promotion target identification information. In this case, a different password may be used for each promotion target for the same stamp card.

[0064] FIG. 6 is a diagram showing an example of the account registration status. For example, as shown in FIG. 6, a promoter whose promotion owner ID is "0001" has registered two or two types of stamp cards with the stamp card service. For a first stamp card, accounts for three stores are registered. Specifically, accounts for stores named "AAA Store," "BBB Store," and "CCC Store" are registered. Different passwords are set for these stores. These stores can grant stamps to the first stamp card. For a second stamp card, accounts for two stores are registered. Specifically, accounts for stores named "DDD Store" and "FFF Store" are registered. Different passwords are set for these stores. These stores can grant stamps to the second stamp card. A promoter whose promotion owner ID is "0002" has registered one stamp card with the stamp card service. Two store accounts are registered for this stamp card.

[0065] The entry DB 14c may store entry information indicating an application for use of a stamp card each time an application for use of one of the stamp cards registered with the stamp card service is made. The entry DB 14c may also store user identification information for identifying each user who has applied for use of a stamp card. Here, the entry DB 14c may store the number of stamps associated with the user identification information for identifying each user who has applied for use of a stamp card. For example, the entry DB 14c may store the number of stamps associated with a combination of user identification information for identifying the user who made the application and stamp card identification information for identifying the requested stamp card each time an application for use of one of the stamp cards is made. For example, as shown in FIG. 5, the entry DB 14c may store, as entry information, a card URL, a user ID, the entry date and time, the number of cards, the current number of stamps, and the like, in association with one another. The card URL may be identification information for identifying the stamp card applied for. The user ID may be identification information for identifying the user who has applied for use. The entry date and time may indicate the date and time when the stamp card was applied for use. The number of cards may indicate how many stamp cards have been issued to the user. The current number of stamps may indicate the number of stamps currently on the most recently issued stamp card among the stamp cards indicated by the number of cards.

[0066] The stamp history DB 14d may store a history of stamps being given. For example, the stamp history DB 14d may store a stamp log indicating that a stamp has been given each time a stamp is given. For example, as shown in FIG. 5, the stamp history DB 14d may store, as a stamp log, a card URL, a user ID, the date and time of giving, the number of given stamps, the store name, and the like, in association with one another. The card URL may indicate the stamp card to which the stamp was given. The user ID may indicate the user to whom the stamp was given. The date and time of giving may indicate the date and time when the stamp was given. The number of given stamps may indicate the number of stamps given. The store name may indicate the store that was the promotion target and that gave the stamp.

[0067] The benefit DB 14e may store benefit information regarding the status of a benefit granted to a user who has earned a predetermined number of stamps by using a stamp card, for each combination of a stamp card issued to the user and a benefit set on the stamp card. For example, the benefit DB 14e may store, as benefit information, a card URL, a user ID, the number of cards, the number of benefit stamps, and a benefit status, all associated with one another. The card URL may indicate the stamp card issued to the user. The user ID may indicate the user to whom the stamp card was issued. The number of cards may indicate which stamp card with the benefit set has been issued to the user. The number of benefit stamps may indicate the number of stamps required for the user to earn the benefit. The benefit status may indicate the status of the benefit. The benefit status may be set to, for example, "not earned," "available," or "used." "Not earned" may indicate a state in which the user has not yet earned the benefit. "Available" may indicate a state in which the user has earned the benefit but has not yet used it. "Used" may indicate a state in which the user has already used the benefit. For example, when a user enters a stamp card campaign, the stamp card management server 1 may store the entry information in the entry DB 14c and may store the benefit information in the benefit DB 14e. At this time, the stamp card management server 1 may obtain the number of benefit stamps from the benefit setting information stored in the stamp card DB 14a. For each obtained number of benefit stamps, the stamp card management server 1 may generate benefit information including the same combination of card URL, user ID, and number of cards as the combination included in the entry information, the number of benefit stamps, and a benefit status indicating "unused."

[0068] The storage unit 14 also stores various programs such as an operating system, a DBMS (Database Management System), and a stamp card management program. The stamp card management program is a program that causes the system control unit 11 to execute various processes related to the stamp card service. The stamp card management program may be obtained from another device via the network NW, or may be recorded on a recording medium such as a magnetic tape, optical disk, or memory card and read via a drive device. The storage unit 14 may also store a stamp presentation tool.

[0069] The communication unit 15 is configured by, for example, a network interface card, etc. The communication unit 15 connects to devices different from the stamp card management server 1 via the network NW, and controls the communication state with the connected devices.

[0070] [1-2-2. Membership information management server] Next, the configuration of the member information management server 2 will be described with reference to Figures 7 and 8. Figure 7 is a block diagram showing an example of the general configuration of the member information management server 2 according to this embodiment. As shown in Figure 7, the member information management server 2 includes a system control unit 21, a system bus 22, an input / output interface 23, a storage unit 24, and a communication unit 25. The system control unit 21 and the input / output interface 23 are connected via the system bus 22.

[0071] The system control unit 21 is composed of a CPU 21a, a ROM 21b, a RAM 21c, and the like.

[0072] The input / output interface 23 performs interface processing between the storage unit 24 and the communication unit 25 and the system control unit 21 .

[0073] The storage unit 24 is configured by, for example, a hard disk drive, etc. The storage unit 24 may store databases such as a member DB 24a.

[0074] Fig. 8 is a diagram showing an example of the contents stored in the database of the member information management server 2. The member DB 24a may store member information about each member of the Internet comprehensive service. For example, as shown in Fig. 8, the member DB 24a may store, as member information, user ID, password, name, gender, date of birth, telephone number, address, email address, etc., in association with one another.

[0075] The memory unit 24 also stores various programs such as an operating system, a DBMS, and a member information management program. The member information management program is a program that causes the system control unit 11 to execute various processes related to the management of member information. The member information management program may be obtained from another device via the network NW, or may be recorded on a recording medium such as a magnetic tape, optical disc, or memory card and read via a drive device.

[0076] The communication unit 25 is configured by, for example, a network interface card, etc. The communication unit 25 connects to devices different from the member information management server 2 via the network NW, and controls the state of communication with the connected devices.

[0077] [1-2-3. Store terminal] Next, the configuration of the store terminal 5 will be described with reference to Fig. 9. Fig. 9 is a block diagram showing an example of a schematic configuration of the store terminal 5 according to this embodiment. As shown in Fig. 9, the store terminal 52 includes a system control unit 51, a system bus 52, an input / output interface 53, a storage unit 54, a communication unit 55, an input unit 56, a display unit 57, and an imaging unit 58. The system control unit 51 and the input / output interface 53 are connected via the system bus 52.

[0078] The system control unit 51 is composed of a CPU 51a, a ROM 51b, a RAM 51c, and the like.

[0079] The input / output interface 53 performs interface processing between the storage unit 54 , communication unit 55 , input unit 56 , display unit 57 , and imaging unit 58 and the system control unit 51 .

[0080] The storage unit 54 is configured by, for example, a solid state drive or a hard disk drive, etc. The storage unit 54 stores various programs such as an operating system, a web browser, a stamp presentation tool, etc.

[0081] The communication unit 55 is configured by, for example, a network interface card, etc. The communication unit 55 connects to devices different from the store terminal 5 via the network NW, and controls the state of communication with the connected devices.

[0082] The input unit 56 may be a device that accepts operations by a user. For example, the input unit 56 may be configured with at least one of a touch panel, keys, buttons, switches, etc. The input unit 56 outputs a signal indicating the content of an operation on the input unit 56 by the user to the system control unit 51.

[0083] The display unit 57 may be configured with a display, a GPU (Graphics Processing Unit), a graphic memory, etc. The display unit 57 displays information such as text and images on the display based on the control of the system control unit 51 or the GPU.

[0084] The imaging unit 58 may include a camera for taking still images or videos. The imaging unit 58 outputs data of the captured images to the storage unit 54.

[0085] [1-3. Functional overview of the system control unit] [1-3-1. Stamp card management server] Next, an outline of the functions of the system control unit 11 of the stamp card management server 1 will be described with reference to Fig. 10 and Fig. 11. Fig. 10 is a diagram showing an example of functional blocks of the system control unit 11 of the stamp card management server 1 according to this embodiment. As shown in Fig. 10, the system control unit 11 may function as an account registration screen information transmitting unit 1101, an application authentication information receiving unit 1102, an authentication information storage control unit 1103, an authentication information receiving unit 1104, a login authentication unit 1105, an authentication result information transmitting unit 1106, a code transmitting unit 1107, a stamp granting request receiving unit 1108, a usage application information searching unit 1109, a stamp granting unit 1110, a stamp card screen information transmitting unit 1111, etc., by the CPU 11a reading and executing various program codes included in the stamp card management program.

[0086] The account registration screen information transmitting unit 1101 may transmit screen information showing an account registration screen to either the promotion host terminal 4 or the operator terminal 3. In this case, the promotion host terminal 4 is a terminal device used by a promoter as an applicant who applies to register a store as a promotion target that can use the stamp presentation tool. In this case, the operator terminal 3 is a terminal device used by an operator of a stamp card service who accepts registration applications from the promoter as an applicant. The account registration screen may be a screen for enabling at least the registration of a promotion target, among the registration of a stamp card and the registration of a promotion target. The account registration screen may accept input of stamp card identification information for identifying a stamp card used for the promotion and authentication information used for login authentication of the promotion target to be registered. The screen information may be information for displaying a specific screen on a terminal device. The screen information transmitted by the account registration screen information transmitting unit 1101 is information for displaying the account registration screen. The screen information may be, for example, an HTML (HyperText Markup Language) document. In this case, the screen may be referred to as a web page or a page. Alternatively, the screen information may be information about the content or each element displayed on the terminal device. Alternatively, the screen information may be information instructing the terminal device to display a specific screen. The promotion host terminal 4 and the operator terminal 3 display the account registration screen based on this screen information.

[0087] FIG. 11 is a diagram illustrating an example of an account registration screen. As illustrated in FIG. 11, the account registration screen 100 may include a search condition input field 110, a card name input field 121, a card URL input field 122, a card delete button 123, a stamp presentation restriction checkbox group 130, multiple account information setting areas 140, an add button 150, and a register button 160. The search condition input field 110 may be an input field for accepting input of search conditions for already registered stamp cards. An example of a search condition is a card URL. The card name input field 121 may be an input field for accepting input of the name of the stamp card to be registered or the stamp card for which an account is to be registered. The card URL input field 122 may be an input field for accepting input of a card URL as an example of stamp card identification information for the stamp card to be registered or the stamp card for which an account is to be registered. When a stamp card is searched for by entering search conditions in the search condition input field 110, the card name and card URL of the searched stamp card may be automatically entered in the card name input field 121 and the card URL input field 122. The card deletion button 123 may be an element operable to delete the stamp card indicated in the card name input field 121 and the card URL input field 122 from the stamp card service. The stamp gift restriction checkbox group 130 may be an element operable to select a stamp gift restriction. Each account information setting area 140 may be an area for setting information about the account to be registered. Each account information setting area 140 may include a store name input field 141, a password input field 142, and a delete button 143. The store name input field 141 may be an input field for accepting input of the name of the store to be promoted. The password input field 142 may be an input field for accepting input of a password as an example of authentication information used by the promotion target. The delete button 143 may be an element operable to delete the account information setting area 140 including the delete button 143 from the account registration screen 100. The add button 150 may be an element operable to add the account information setting area 140 to the account registration screen 100.When a stamp card is searched for by entering search criteria in the search criteria input field 110, account information setting areas 140 are displayed for the number of accounts registered for that stamp card, and the registered store name and password may be displayed in the store name input field 141 and password input field 142 included in each account information setting area 140. The register button 160 may be an element that can be operated to register an account with the details entered in the account registration screen 100.

[0088] The application authentication information receiving unit 1102 may receive stamp card identification information and authentication information entered on the account registration screen 100 displayed on the promotion host terminal 4 and the operator terminal 3 based on the screen information sent by the account registration screen information sending unit 1101. For example, the promotion host or the operator of the stamp card service enters a card name and a card URL on the account registration screen 100, and also enters a store name and password for each store that is the target of the promotion. The stamp presentation limit is also selected. Then, the registration button 160 is operated. The promotion host terminal 4 and the operator terminal 3 send the information entered on the account registration screen 100 to the stamp card management server 1. As a result, the application authentication information receiving unit 1102 may receive the card URL as stamp card identification information and the password as authentication information.

[0089] The authentication information storage control unit 1103 may store the authentication information received by the application authentication information receiving unit 1102 in the storage unit 14 in association with the stamp card identification information received by the application authentication information receiving unit 1102. For example, the authentication information storage control unit 1103 may generate account information including the store name and password for each combination of the store name and password entered on the account registration screen 100. The authentication information storage control unit 1103 may store the account information in the tool account DB 14b in association with the received card URL. If the received card URL is not stored in the stamp card DB 14a, the authentication information storage control unit 1103 may store the card URL, card name, and stamp presentation restriction information in the stamp card DB 14a. Note that the promoter or the operator of the stamp card service may be able to input the campaign period, promotion host ID, and benefit setting information on the account registration screen 100 or another screen. The authentication information storage control unit 1103 may store the input information in the stamp card DB 14a in association with the card URL.

[0090] The authentication information receiving unit 1104 may receive the stamp card identification information and authentication information input to the store terminal 5. In this case, the store terminal 5 may be a terminal device used by a store as an example of a promotion target. For example, when the store terminal 5 starts up the stamp presentation tool based on the operation of a store employee, the store terminal 5 may display a login screen. The login screen may be a screen that accepts input of a card URL and a password. The store terminal 5 may transmit the card URL and password input on the login screen to the stamp card management server 1. As a result, the authentication information receiving unit 1104 may receive the card URL as stamp card identification information and the password as authentication information.

[0091] The login authentication unit 1105 may perform login authentication based on the stamp card identification information and authentication information received by the authentication information receiving unit 1104 and the stamp card identification information and authentication information stored in the storage unit 14. For example, the login authentication unit 1105 may search the stamp card DB 14a for a card URL that matches the card URL received as the stamp card identification information. If the corresponding card URL is not found in the stamp card DB 14a, the login authentication unit 1105 may determine that the login authentication has failed. The login authentication unit 1105 may acquire a password associated with the searched card URL as authentication information from the stamp card DB 14a. The login authentication unit 1105 may determine whether the password received as the authentication information matches any of the passwords acquired from the stamp card DB 14a. If a password matching the received password is found, the login authentication unit 1105 may determine that the login authentication has succeeded. If a password matching the received password is not found, the login authentication unit 1105 may determine that the login authentication has failed.

[0092] The authentication result information sending unit 1106 may send authentication result information indicating the result of login authentication by the login authentication unit 1105 to the store terminal 5. The authentication result information may indicate success or failure of login authentication. Here, if login authentication is successful, the authentication result information sending unit 1106 may store login status information in the store terminal 5. The login status information may be information indicating that the store using the store terminal 5 is currently logged in to the stamp presentation tool. The login status information may include stamp card identification information for which login authentication was successful. The stamp card identification information for which login authentication was successful may be stamp card identification information received from the store terminal 5 by the authentication information receiving unit 1104 when login authentication was successful, or stamp card identification information searched for in the stamp card DB 14a as stamp card identification information matching the stamp card identification information. The login status information may also include promotion target identification information for identifying a promotion target store for which login authentication was successful. In this case, the promotion target identification information may be, for example, the store name or a password. The authentication result information sending unit 1106 may send authentication result information including the stamp card identification information and promotion target identification information for which login authentication was successful to the store terminal 5 as authentication result information indicating success of login authentication, thereby causing the store terminal 5 to store login status information including this stamp card identification information and promotion target identification information.

[0093] The code sending unit 1107 may send a code indicating information about either the promotion target as the stamp giver or the user as the stamp recipient to a terminal device used by either one of them. That is, the code sending unit 1107 may send a code indicating information about the one of the stamp giver and stamp recipient who uses the terminal device to which the code is sent. The terminal device used by the promotion target is the store terminal 5. The terminal device used by the user is the user terminal 6. The code indicating the information may be a code generated by encoding the information.

[0094] When the code is sent to the store terminal 5, the transmitted code indicates information about the promotion target. The information about the promotion target indicated by the code may include stamp card identification information for which the login authentication by the login authentication unit 1105 has successfully authenticated the promotion target that issued the stamp. In other words, the transmitted code may indicate stamp card identification information that matches the stamp card identification information entered on the login screen by the promotion target that issued the stamp. This stamp card identification information may be information for identifying a stamp card corresponding to the store that issued the stamp among the stores that provide the transaction target. The stamp card corresponding to the store that issued the stamp may be a stamp card registered with the store as a promotion target. Furthermore, the information about the promotion target indicated by the code may include the date and time the stamp was issued, the number of stamps issued, and the promotion target identification information of the promotion target. In this case, the promotion target identification information may be information for identifying the store that issued the stamp among the stores that provide the transaction target. The promotion target identification information may be, for example, the name of the store. The promotion target identification information may correspond to the provider identification information. Alternatively, the provider identification information may be a combination of the promotion target identification information and the stamp card identification information. The provider identification information may be identification information for identifying the store that is the provider of the transaction object and that has provided the stamps. The date and time of providing may indicate, for example, the date and time when the code sending unit 1107 generated the code. The number of provided stamps may be specified by an employee of the store that is the promotion target using a stamp providing tool.

[0095] If the destination of the code is the user terminal 6, the transmitted code indicates user information. The user information indicated by the code may include user identification information for identifying the user to whom the stamp is to be given. This user identification information may be, for example, a user ID. The user ID may be obtained from the user terminal 6. For example, when a user logs in to the stamp card app, the user inputs a user ID and password. The stamp card management server 1 or the member information management server 2 performs login authentication based on the input user ID and password and the user ID and password stored in the member DB 24a. If the login authentication is successful, the user terminal 6 may store the input user ID as one piece of information indicating that the user is logged in to the stamp card app. This allows the user terminal 6 to obtain the user ID at any time.

[0096] The stamp granting request receiving unit 1108 may receive a stamp granting request from a terminal device used by either the promotion target as the stamp grant source or the user as the stamp grant recipient. The stamp granting request receiving unit 1108 may receive information about the promotion target and the user from a terminal device used by the other of the promotion target as the stamp grant source or the user as the stamp grant recipient, which terminal device reads the code received from the stamp card management server 1 by the terminal device used by one of the promotion target and the user. For example, the stamp granting request receiving unit 1108 may receive a stamp granting request including information about the promotion target and the user. If the terminal device that received the code is the store terminal 5, the terminal device used by the other of the promotion target and the user is the user terminal 6. If the terminal device that received the code is the user terminal 6, the terminal device used by the other of the promotion target and the user is the store terminal 5. The terminal device that receives the code from the stamp card management server 1 displays the code on its screen. The other terminal device may read the code by photographing the code displayed on its screen with a camera provided in the terminal device. The terminal device that reads the code can decode the code to obtain, as the information indicated by the code, information on the promotion target and the user who is using the terminal device that received the code from the stamp card management server 1. Information on the promotion target and the user who is using the terminal device that read the code can be obtained from the terminal device that read the code itself. Therefore, the terminal device that read the code can transmit both information on the promotion target and information on the user to the stamp card management server 1.

[0097] Neither the promotion target information nor the user information transmitted from the store terminal 5 or the user terminal 6, respectively, is accompanied by information regarding the payment from the user to the promotion target. The phrase "first information accompanied by second information" includes cases where either the first information or the second information includes information regarding the other, where the first information and the second information are combined or connected, where the first information is transmitted in association with the second information, or where the first information and the second information are transmitted consecutively. For example, a stamp request may include promotion target information and user information but not information regarding payment. Examples of information regarding payment include payment information, settlement information, and other information indicating the details of settlement, payment, or transaction.

[0098] The application information search unit 1109 may acquire any user identification information from the entry DB 14c. For example, the application information search unit 1109 may search the entry DB 14c for user identification information for identifying the same user as the user identified by the user identification information included in the stamp granting request received by the stamp granting request receiving unit 1108. For example, the application information search unit 1109 may search for user identification information that matches the user identification information included in the stamp granting request received by the stamp granting request receiving unit 1108. In this case, the application information search unit 1109 may search the entry DB 14c for entry information that includes a combination that matches the combination of the user identification information included in the user information included in the stamp granting request and the stamp card identification information included in the promotion target information included in the stamp granting request. For example, the application information search unit 1109 may search for entry information that includes a combination that matches the combination of a card URL as stamp card identification information and a user ID as user identification information.

[0099] The stamp granting unit 1110 may execute a process of granting a stamp based on the promotion target information and user information received by the stamp granting request receiving unit 1108. For example, the stamp granting unit 1110 may grant a stamp to a stamp card used by a user identified by user identification information included in the received user information, among stamp cards identified by stamp card identification information included in the received promotion target information. Specifically, the stamp granting unit 1110 may grant a stamp by increasing the current stamp count stored in the entry DB 14c in association with a combination of a card URL as stamp card identification information included in the promotion target information and a user ID as user identification information included in the user information. The stamp granting unit 1110 may add a predetermined number of granted stamps to the current stamp count. Alternatively, the number of stamps granted by the stamp granting unit 1110 may change. For example, the stamp granting unit 1110 may add the number of granted stamps designated by an employee of the store that granted the stamp to the current stamp count.

[0100] The stamp granting unit 1110 may grant a stamp to a user only if the user identified by the user identification information included in the user information has already applied for use of the stamp card identified by the stamp card identification information included in the promotion target information. For example, the stamp granting unit 1110 may grant a stamp on the condition that corresponding user identification information or entry information is found as a result of a search by the usage application information search unit 1109. If corresponding user identification information or entry information is not found, the stamp granting unit 1110 may not grant a stamp.

[0101] The stamp card screen information transmitting unit 1111 may transmit screen information showing a stamp card screen to the user terminal 6. The stamp card screen may be a screen showing a stamp card. For example, the stamp card screen may display a card name and an image of the stamp card. The stamp card displayed on the stamp card screen may display multiple stamp fields. Of the stamp fields included in the stamp card, an image indicating that a stamp has been pressed may be displayed in the stamp fields corresponding to the number of stamps the user has acquired. The user may operate the user terminal 6 to select a stamp card to display. The user terminal 6 may transmit the card URL of the selected stamp card and the user ID of the user to the stamp card management server 1. The stamp card screen information transmitting unit 1111 may generate screen information for displaying the stamps pressed on the stamp card as screen information for the stamp card screen, based on the card URL and the current number of stamps stored in the entry DB 14c in association with the user ID received from the user terminal 6. The stamp card screen information transmitting unit 1111 may transmit the generated screen information.

[0102] [1-3-2. Store terminal] Next, an overview of the functions of the system control unit 51 of the store terminal 5 will be described with reference to Figs. 12 to 15. Fig. 12 is a diagram showing an example of functional blocks of the system control unit 51 of the store terminal 5 according to this embodiment. As shown in Fig. 12, the system control unit 51 may function as a login screen display control unit 5101, an authentication information transmission unit 5102, an authentication result information reception unit 5103, a login status storage control unit 5104, a code reception unit 5105, a code display control unit 5106, a code reading unit 5107, a stamp grant request transmission unit 5108, etc., by the CPU 51a reading and executing various program codes included in the stamp presentation tool.

[0103] The login screen display control unit 5101 may display the login screen of the stamp presentation tool on the display unit 57. The stamp presentation tool may display the login screen on the store terminal 5. As described above, the login screen may be a screen that accepts stamp card identification information and authentication information. The login screen may also be a screen that accepts an operation to select a method for providing stamps. The selectable methods may include a first method and a second method. The first method is a method in which the store terminal 5 outputs a code indicating information about the promotion target. An example of outputting a code is displaying the code. The second method is a method in which the store terminal reads a code indicating user information.

[0104] FIG. 13 is a diagram showing an example of a login screen. As shown in FIG. 13, login screen 200 may include a card URL input field 201, a password input field 202, a code display button 203, and a code read button 204. Card URL input field 201 may be an input area that accepts input of a card URL as stamp card identification information. Password input field 202 may be an input area that accepts input of a password as authentication information. Code display button 203 may be an element that can be operated to select a first method as a method of applying a stamp. Code read button 204 may be an element that can be operated to select a second method as a method of applying a stamp.

[0105] The authentication information sending unit 5102 may send the stamp card identification information and authentication information entered on the login screen 200 displayed on the display unit 57 to the stamp card management server 1. For example, a store employee enters a card URL and a password in the card URL input field 201 and the password input field 202. The employee then operates either the code display button 203 or the code read button 204. In response to this operation, the authentication information sending unit 5102 may send the entered card URL and password to the stamp card management server 1.

[0106] The authentication result information receiving unit 5103 may receive, from the stamp card management server 1, authentication result information indicating the result of login authentication performed based on the stamp card identification information and authentication information transmitted by the authentication information transmitting unit 5102. Here, if the login authentication is successful, the authentication result information receiving unit 5103 may receive, as authentication result information indicating the success of the login authentication, authentication result information including the stamp card identification information for which the login authentication was successful and promotion target identification information for identifying the store that uses the store terminal 5.

[0107] When the authentication result information received by the authentication result information receiving unit 5103 indicates that the login authentication was successful, the login status storage control unit 5104 may store the login status information in the storage unit 54. At this time, the login status storage control unit 5104 may include in the login status information the stamp card identification information for which the login authentication was successful and the promotion target identification information of the store using the store terminal 5. The login status storage control unit 5104 may also include in the login status information information indicating the method selected by the store as the method for granting stamps. When a store employee logs out of the stamp presentation tool, the login status storage control unit 5104 may delete the login status information from the storage unit 54.

[0108] The stamp presentation tool may cause the system control unit 51 to function as at least one of the code receiving unit 5105 (or a combination of the code receiving unit 5105 and the code display control unit 5106) and the code reading unit 5107 and the stamp presentation request sending unit 5108, on the condition that the login authentication executed by the stamp card management server 1 based on the stamp card identification information and authentication information sent by the authentication information sending unit 5102 is successful. In other words, if the login authentication is successful, the store may be able to use the stamp presentation tool. For example, when a user operates the code display button 203 on the login screen 200, the stamp presentation tool may cause the system control unit 51 to function as the code receiving unit 5105 and the code display control unit 5106. When a user operates the code read button 204 on the login screen 200, the stamp presentation tool may cause the system control unit 51 to function as the code reading unit 5107 and the stamp presentation request sending unit 5108. The stamp presentation tool may remain usable until the store employee logs out of the stamp presentation tool. Even if the employee closes and restarts the stamp presentation tool, the stamp presentation tool may allow the user to use the stamp presentation tool without displaying a login screen. If login status information is stored in the memory unit 54, the stamp presentation tool is usable. If login status information is not stored in the memory unit 54, the stamp presentation tool is not usable. If the authentication result information indicates a failure of login authentication, the stamp presentation tool may not cause the system control unit 51 to function as any of the code receiving unit 5105, the code display control unit 5106, the code reading unit 5107, and the stamp presentation request sending unit 5108. In this case, an error message may be displayed on the login screen 200.

[0109] The code receiving unit 5105 may receive a code indicating information about a promotion target from the stamp card management server 1. For example, the code receiving unit 5105 may send a code request to the stamp card management server 1. The code request may be information indicating a code request. The code request may include stamp card identification information and promotion target identification information for which login authentication was successful. This information can be acquired from login status information. The code request may also include the number of awarded stamps. The number of awarded stamps may be specified by an employee. For example, a number greater than or equal to 1 may be specified as the number of awarded stamps. FIG. 14(a) is a diagram showing an example of a code displaying number of awarded stamps selection screen. The code displaying number of awarded stamps selection screen may be a screen that accepts an operation to select the number of awarded stamps when the store terminal 5 displays a code. The code displaying number of awarded stamps selection screen is a screen that is displayed on the display unit 57 when login authentication is successful by the user operating the code display button 203 on the login screen 200. As shown in FIG. 14(a), the code displaying number-of-stamps selection screen 210 may include a logout button 211, a card name 212, a store name 213, a number-of-stamps selection list 214, and a display button 215. The logout button 211 may be an element operable to log out of the stamp giving tool. The card name 212 may indicate the name of a stamp card to which a store can give stamps using the stamp giving tool. The store name 213 may indicate the name of the store as promotion target identification information. The number-of-stamps selection list 214 may be an element operable to select the number of stamps to be given. The display button 215 may be an element operable to display the code. When the employee operates the display button 215, the code receiving unit 5105 may transmit a code request. The code receiving unit 5105 may receive image data of the code transmitted from the stamp card management server 1 in response to the transmission of the code request. Examples of image data formats include JPEG, PNG, and TIFF.

[0110] The code display control unit 5106 may display the code received by the code receiving unit 5105 on the display unit 57. FIG. 14(b) is a diagram showing an example of a code display screen for a store terminal. The store code table screen may be a screen displaying a code indicating information about a promotion target. The code display screen for a store terminal is a screen displayed on the display unit 57 in response to operation of the display button 215 on the code display number of stamps selection screen 210. In FIG. 14(b), the same elements as those in FIG. 14(a) are denoted by the same reference numerals. As shown in FIG. 14(b), the store terminal code display screen 220 may include a return button 221, a card name 212, a store name 213, a number of stamps to be awarded 222, an award date 223, a code 224, a "4", and an update button 225. The return button 221 may be an element operable to return the screen to the code display number of stamps selection screen 210. The number of stamps given 222 may indicate the number selected from the number of stamps given selection list 214 as the number of stamps to be given. The date of giving 223 may indicate the date on which the code 224 was generated. The code 224 may be a code received by the code receiving unit 5105. The update button 225 may be an element that can be operated to cause the stamp card management server 1 to generate a new code and update the code 224. The generated code may become invalid after a predetermined time has passed since the code was generated. If an invalid code is used, no stamps will be given.

[0111] FIG. 14(c) is a diagram showing an example of a user terminal code reading screen. The user terminal code reading screen may be a screen displayed on the user terminal 6 to allow the user terminal 6 to read a code. In response to a user selecting code reading in the stamp card app, the user terminal 6 may display the user terminal code reading screen. As shown in FIG. 14(c), the user terminal code reading screen 310 may include a current date 311, a currently captured image confirmation area 312, and a close button 313. The current date 311 may indicate today's date. The currently captured image confirmation area 312 may be an area where an image currently being captured by a camera included in the user terminal 6 is displayed. The close button 313 may be an element operable to close the user terminal code reading screen 310. The user photographs the code 224 displayed on the store terminal code display screen 220 of the store terminal 5 with the camera included in the user terminal 6. When the code 224 is displayed in the currently captured image confirmation area 312, the user terminal 6 may send the above-mentioned stamp granting request to the stamp card management server 1.

[0112] The code reading unit 5107 may read a code received by the user terminal 6 from the stamp card management server 1, the code indicating user information. FIG. 15(a) is a diagram showing an example of a user terminal code display screen. The user terminal code display screen may be a screen displayed by the user terminal 6, displaying a code indicating user information. In response to a user selecting code display in the stamp card app, the user terminal 6 may display the user terminal code display screen. As shown in FIG. 15(a), the user terminal code display screen 320 may include a current date 321, a code 322, and a close button 323. The current date 321 may indicate today's date. The code 322 may be a code indicating user information. The close button 323 may be an element operable to close the user terminal code display screen 320.

[0113] FIG. 15(b) is a diagram showing an example of a store terminal code reading screen. The store terminal code reading screen may be a screen displayed on the display unit 57 of the store terminal 5 so that the store terminal 5 can read a code. The store terminal code reading screen is a screen displayed on the display unit 57 in response to the operation of the code reading button 204 on the login screen 200. In FIG. 15(b), the same elements as those in FIG. 14(a) are denoted by the same reference numerals. As shown in FIG. 15(b), the store terminal code reading screen 230 may include a logout button 211, a card name 212, a store name 213, a currently captured image confirmation area 232, and a close button 233. The currently captured image confirmation area 232 may be an area where an image currently being captured by the imaging unit 58 is displayed. The close button 233 may be an element operable to close the store terminal code reading screen 230. A store employee uses the imaging unit 58 to capture a code 322 displayed on the user terminal code display screen 320 of the user terminal 6.

[0114] FIG. 15(c) is a diagram showing an example of a code reading number of stamps selection screen. The code reading number of stamps selection screen may be a screen that accepts an operation to select the number of stamps to be awarded when the store terminal 5 reads a code. The code display number of stamps selection screen is a screen that is displayed on the display unit 57 in response to the code 322 being photographed and displayed in the video confirmation area 232 during shooting. In FIG. 15(c), the same elements as those in FIG. 14(a) are denoted by the same reference numerals. As shown in FIG. 15(c), the code reading number of stamps selection screen 240 may include a return button 241, a card name 212, a store name 213, a number of stamps to be awarded selection list 214, and an award button 242. The return button 240 may be an element that can be operated to return the screen to the store terminal code reading screen. The award button 242 may be an element that can be operated to award a stamp.

[0115] When the code is read by the code reading unit 5107, the stamp granting request sending unit 5108 may transmit information about the promotion target and information about the user. For example, the stamp granting request sending unit 5108 may transmit a stamp granting request including information about the promotion target and information about the user. The stamp granting request sending unit 5108 may transmit a stamp granting request including information about the user indicated by the code read by the code reading unit 5107 and information about the store, as a promotion target, that uses the store terminal 5 that read the code by the code reading unit 5107. When the grant button 242 is operated on the code reading stamp number selection screen 240, the stamp granting request sending unit 5108 may transmit a stamp granting request to the stamp card management server 1.

[0116] [1-4. Operation of communication system] Next, the operation of the communication system S will be described with reference to Figures 16 to 22. The processes shown in these figures are examples, and any process may be executed as long as the purpose is achieved. The order of the processes is not limited to the order shown in these figures. Furthermore, at least one of the steps shown in these figures may not be executed.

[0117] 16 is a sequence diagram showing an example of the operation of the communication system S when registering a stamp card and a store that is the target of a promotion. For example, the administrator of the stamp card service operates the administrator terminal 3 to launch a web browser and select to display the account registration screen 100. The administrator terminal 3 detects this operation and sends an account registration screen request to the stamp card management server 1 (step S101). The account registration screen information sending unit 1101 of the stamp card management server 1 that receives the account registration screen request sends an HTML document as an example of screen information for the account registration screen 100 to the administrator terminal 3 (step S102). The administrator terminal 3 displays the account registration screen 100 based on this HTML document (step S103).

[0118] The administrator inputs the card name and card URL on the account registration screen 100. The administrator also selects the stamp presentation restriction. The administrator also inputs the store name and password of each store (step S104). When the administrator operates the registration button 160, the administrator terminal 3 transmits stamp card information including the card name, card URL, and stamp restriction information, and account information including the store name and password for each store, to the stamp card management server 1 (step S105). The authentication information storage control unit 1103 of the stamp card management server 1 stores the stamp card information in the stamp card DB 14a (step S106). The authentication information storage control unit 1103 also stores each account information in the tool account DB 14b in association with the card URL included in the stamp card information (step S107).

[0119] FIG. 17 is a sequence diagram showing an example of the operation of the communication system S when a user applies for use of a stamp card. For example, the user terminal 6 displays a list of stamp cards available for entry based on a user operation. The user selects a stamp card to enter from the list (step S201). The user terminal 6 detects this selection and transmits an entry acceptance request including the card URL of the selected stamp card and the user ID of the user to the stamp card management server 1 (step S202). The stamp granting unit 1110 of the stamp card management server 1 that receives the entry acceptance request stores the entry information in the entry DB 14c (step S203). For example, the stamp granting unit 1110 acquires the card URL and the user ID from the entry acceptance request. The stamp granting unit 1110 may generate entry information including the card URL, the user ID, the entry date and time indicating the current date and time, the number of cards indicating 1, and the current number of stamps indicating 0. The system control unit 11 may store this entry information. Next, the stamp granting unit 1110 stores the benefit information in the benefit DB 14e (step S204). For example, the stamp granting unit 1110 may obtain benefit setting information associated with the obtained card URL from the stamp card DB 14a. The stamp granting unit 1110 may obtain the number of benefit stamps from the benefit setting information. The stamp granting unit 1110 may generate benefit information including the same combination of the card URL, user ID, and number of cards included in the entry information, the number of benefit stamps, and a benefit status indicating "not obtained." The stamp granting unit 1110 may store this benefit information.

[0120] FIG. 18 is a sequence diagram showing an example of the operation of the communication system S when a store logs in to the stamp presentation tool. For example, the store terminal 5 launches the stamp presentation tool based on an operation by a store employee. The login screen display control unit 5101 of the store terminal 5 determines whether login status information is stored in the storage unit 54 according to the stamp presentation tool. If the login status information is not stored, as shown in FIG. 18, the login screen display control unit 5101 displays the login screen 200 on the display unit 57 (step S301). The employee inputs a card URL and a password on the login screen 200 (step S302). Next, the employee operates the code display button 203 or the code read button 204 (step S303). The authentication information transmission unit 5102 of the store terminal 5, which detects this operation, transmits a login authentication request including the input card URL and password to the stamp card management server 1 (step S304). If the login status information is stored, the store terminal 5 displays either the code display number of stamps to be awarded selection screen 210 or the store terminal code reading screen 230 according to the login status information.

[0121] The login authentication unit 1105 of the stamp card management server 1 that has received the login authentication request executes login authentication (step S305). For example, the login authentication unit 1105 may determine whether or not account information stored in the tool account DB 14b in association with a card URL that matches the card URL included in the login authentication request contains account information that includes a password that matches the password included in the login authentication request. If the corresponding account information is found, the login authentication unit 1105 may determine that the login authentication has been successful. Here, it is assumed that the login authentication unit 1105 has determined that the login authentication has been successful (step S306). In this case, the authentication result information sending unit 1106 of the stamp card management server 1 sends authentication result information indicating success, including the card URL included in the login authentication request and the store name included in the corresponding account information, to the store terminal 5 (step S307).

[0122] The login status storage control unit 5104 of the store terminal 5 that has received the authentication result information stores login status information including the card URL and store name included in the authentication result information, and the stamp granting method selected from the code display button 203 and the code reading button 204 on the login screen 200 (step S308). Next, the code display control unit 5106 or the code reading unit 5107 displays on the display unit 57 a screen corresponding to the button selected on the login screen 200, from the code display stamp number selection screen 210 and the store terminal code reading screen 230 (step S309).

[0123] FIG. 19 is a sequence diagram illustrating an example of the operation of the communication system S when the store terminal 5 displays a code and awards stamps. For example, the store terminal 5 displays the code display stamp number selection screen 210. As shown in FIG. 19, a store employee selects the number of award stamps on this screen and operates the display button 215 (step S401). Upon detecting this operation, the code display control unit 5106 of the store terminal 5 displays the store terminal code display screen 220 (step S402). Next, the code receiving unit 5105 transmits a code request including the card URL and store name included in the login status information stored in the memory unit 54 and the selected number of award stamps to the stamp card management server 1 (step S403). Upon receiving the code request, the code sending unit 1107 of the stamp card management server 1 generates image data of a code indicating information about the store as a promotion target (step S404). For example, the code sending unit 1107 may generate plain text by concatenating the card URL, store name, number of award stamps, and award date and time indicating the current date and time included in the code request. The code sending unit 1107 may generate image data of the code by encoding this plain text. Next, the code sending unit 1107 sends the generated image data to the store terminal 5 (step S405). The code display control unit 5106 of the store terminal 5 displays the code on the store terminal code display screen 220 based on this image data (step S406).

[0124] Meanwhile, the user terminal 6 displays the user terminal code reading screen 310 based on an operation by the user (step S407). Next, the user terminal 6 photographs the code displayed on the store terminal 5 (step S408). Next, the user terminal 6 decodes the code based on the image data of the photographed code to obtain the card URL, store name, number of stamps awarded, and award date and time (step S409). Next, the user terminal 6 sends a stamp award request including the card URL, store name, number of stamps awarded, award date and time, and the user ID of the user using the user terminal 6 to the stamp card management server 1 (step S410). Upon receiving the stamp award request, the stamp card management server 1 executes stamp control processing (step S411). The stamp control processing includes processing for determining whether or not to award a stamp and for awarding the stamp. Details of the stamp control processing will be described later.

[0125] FIG. 20 is a sequence diagram showing an example of the operation of the communication system S when the store terminal 5 reads a code and grants a stamp. As shown in FIG. 20, the user terminal 6 displays the user terminal code display screen 320 based on an operation by the user (step S501). Next, the user terminal 6 transmits a code request including the user ID of the user using the user terminal 6 to the stamp card management server 1 (step S502). The code transmission unit 1107 of the stamp card management server 1 that receives the code request generates image data of a code indicating user information (step S503). For example, the code transmission unit 1107 may generate image data of the code by encoding the user ID included in the code request. Next, the code transmission unit 1107 transmits the generated image data to the user terminal 6 (step S504). The user terminal 6 displays the code on the user terminal code display screen 320 based on this image data (step S505).

[0126] Meanwhile, the store terminal 5 displays the store terminal code reading screen 230. The code reading unit 5107 of the store terminal 5 photographs the code displayed on the user terminal 6 (step S506). Next, the code reading unit 5107 acquires the user ID by decoding the code based on the image data of the photographed code (step S507). Next, the stamp granting request sending unit 5108 displays the code reading number of stamps selection screen 240 on the display unit 57 (step S508). The store employee selects the number of stamps to be granted on this screen and operates the grant button 242 (step S509). Upon detecting this operation, the stamp granting request sending unit 5108 transmits a stamp granting request to the stamp card management server 1, the stamp request including the card URL and store name included in the login status information, the selected number of stamps to be granted, the granting date and time indicating the current date and time, and the acquired user ID (step S510). Upon receiving the stamp granting request, the stamp card management server 1 executes stamp control processing (step S511).

[0127] FIG. 21 is a flowchart showing an example of stamp control processing executed by the system control unit 11 of the stamp card management server 1 according to this embodiment. The stamp granting unit 1110 acquires, from the stamp granting request, the card URL of the stamp card to be stamped, the store name of the store that has granted the stamp, the user ID of the user to whom the stamp is to be granted, the number of stamps granted, and the date and time of granting. As shown in FIG. 21, the usage application information search unit 1109 searches the entry DB 14c for entry information containing a combination that matches the acquired combination of card URL and user ID (step S601). As a result of the search, the usage application information search unit 1109 determines whether or not there is corresponding entry information (step S602). If there is no corresponding entry information (step S602: NO), the stamp control processing ends.

[0128] If there is corresponding entry information (step S602: YES), the stamp granting unit 1110 determines whether the acquired stamp grant date and time is within the campaign period stored in the stamp card DB 14a in association with the acquired card URL (step S603). Here, the stamp granting unit 1110 may determine whether the current date and time is within the campaign period, rather than the stamp grant date and time. If the stamp grant date and time is outside the campaign period (step S603: NO), the stamp control process ends.

[0129] If the granting date and time is within the campaign period (step S603: YES), the stamp granting unit 1110 determines whether the stamps granted to the stamp grantee up to now have reached the stamp grant limit (step S604). For example, the stamp granting unit 1110 may acquire stamp grant limit information associated with the acquired card URL. Alternatively, the stamp granting unit 1110 may acquire a stamp log including a combination that matches the combination of the acquired card URL and user ID from the stamp history DB 14d. The stamp granting unit 1110 may make the determination based on the stamp grant limit information and the stamp log. If the stamps granted up to now have reached the stamp grant limit (step S604: YES), the stamp control process ends. If the stamps granted up to now have not reached the stamp grant limit (step S604: NO), the stamp granting unit 1110 executes the stamp granting process (step S605), and the stamp control process ends.

[0130] FIG. 22 is a flowchart showing an example of stamp granting processing executed by the system control unit 11 of the stamp card management server 1 according to this embodiment. As shown in FIG. 22, the stamp granting unit 1110 adds the acquired number of granted stamps to the current number of stamps included in the entry information searched for in step S601 of the stamp control processing, thereby updating the current number of stamps stored in the entry DB 14c (step S701). Next, the stamp granting unit 1110 stores a stamp log in the stamp history DB 14d (step S702). For example, the stamp granting unit 1110 may generate a stamp log including the acquired card URL, user ID, number of granted stamps, grant date and time, and store name. The stamp granting unit 1110 may store this stamp log.

[0131] Next, the stamp granting unit 1110 acquires the privilege setting information stored in the stamp card DB 14a in association with the acquired card URL. The stamp granting unit 1110 determines whether the number of stamps before the update is less than any of the numbers of privilege stamps included in the privilege setting information and whether the number of stamps after the update is equal to or greater than that number of privilege stamps (step S703). If there is a corresponding number of privilege stamps (step S703: YES), the stamp granting unit 1110 acquires the number of cards included in the searched entry information from the entry DB 14c. The stamp granting unit 1110 changes the privilege status stored in the privilege DB 14e in association with the combination of the corresponding number of privilege stamps, the acquired card URL, user ID, and the acquired number of cards to "available" (step S703).

[0132] If there is no corresponding number of bonus stamps (step S703: NO) or after step S704, the process proceeds to step S705. In step S705, the stamp granting unit 1110 determines whether the updated current number of stamps is equal to or greater than the number of stamp columns. If the current number of stamps is equal to or greater than the number of stamp columns (step S705: YES), the stamp granting unit 1110 adds 1 to the number of cards included in the searched entry information, thereby updating this number of cards stored in the entry DB 14c (step S706). Next, the stamp granting unit 1110 updates this current number of stamps included in the searched entry information by subtracting the number of stamp columns from the current number of stamps stored in the entry DB 14c (step S707). Next, the stamp granting unit 1110 stores new bonus information in the bonus DB 14e (step S708). The process content of step S708 may be the same as the process content of step S204 shown in FIG. 17.

[0133] If the current number of stamps is less than the number of stamp columns (step S705: NO), or after step S708, the stamp granting unit 1110 transmits a stamp granting completion notification to each of the store terminal 5 of the store that granted the stamp and the user terminal 6 of the user to whom the stamp was granted (step S709). The store terminal 5 and the user terminal 6 that have received the stamp granting completion notification may display the stamp granting completion notification.

[0134] As described above, according to this embodiment, a stamp can be given without using information related to payment.

[0135] Here, the stamp presentation tool may cause the store terminal 5 to display the login screen 200. Furthermore, when a first method is selected on the login screen 200, the stamp presentation tool may cause the store terminal 5 to function as at least the code receiving unit 5105 of the code receiving unit 5105 and the code display control unit 5106. Furthermore, when a second method is selected on the login screen 200, the stamp presentation tool may cause the store terminal 5 to function as the code reading unit 5107 and the stamp presentation request sending unit 5108. In this case, when the first method is selected and login authentication is successful, the store terminal 5 receives a code indicating information about the promotion target from the stamp card management server 1. When the second method is selected and login authentication is successful, the store terminal 5 reads the code indicating user information and sends information about the promotion target and the user information to the stamp card management server 1. Therefore, the promotion target can select the method for presenting the stamp.

[0136] The stamp card management server 1 may also transmit screen information of the account registration screen 100 to the operator terminal 3 or the promotion main terminal 4. The stamp card management server 1 may also receive the stamp card identification information and authentication information entered on the account registration screen 100. The stamp card management server 1 may also store the authentication information in the tool account DB 14b in association with the received stamp card identification information. In this case, the applicant or the operator can register the authentication information to be used by the target of a promotion using a stamp card.

[0137] [2. Second Embodiment] Next, a second embodiment will be described. Except for the points described below, the second embodiment may be the same as the first embodiment. In this embodiment, the promotion target is the provider of the transaction object. Examples of the provider include a store, a store manager, and a store employee. In this embodiment, a stamp is given to a user on the condition that the user makes a payment to the provider to pay for the transaction of the transaction object.

[0138] [2-1. Communication System Configuration] First, the configuration and functional overview of the communication system S according to this embodiment will be described with reference to Figs. 23 and 24. Fig. 23 is a diagram showing an example of the schematic configuration of the communication system S according to this embodiment. In Fig. 23, the same elements as in Fig. 1 are assigned the same reference numerals. As shown in Fig. 23, the communication system S may be configured to include a stamp card management server 1, a member information management server 2, an operator terminal 3, multiple promotion host terminals 4, multiple store terminals 5, multiple user terminals 6, one or multiple payment servers 10, and multiple store payment terminals 20. These devices may be connected to a network NW.

[0139] The payment server 10 may be a server device that executes processing to provide a predetermined payment service available at a store. The payment service may be a service that enables payment using a payment method. The payment service may be one of the services included in the above-mentioned comprehensive internet service. If there are multiple payment servers 10, each payment server 10 may perform processing related to a payment service supported by that payment server 10, for example, from among the multiple payment services included in the comprehensive internet service. The payment service supported by one of the payment servers 10 may be a points program. A points program may be a service that allows a user to earn points upon paying the price of a transaction. For example, points equivalent to a predetermined percentage of the price may be awarded to the user. The exchange rate between points and money is predetermined. For example, 1 point may be equivalent to 1 yen. Furthermore, the points program may be a service that allows a user to use points to pay the price. Using points for payment may mean paying all or part of the amount to be paid with points. The payment method may be a method that can be used to pay the price of a transaction. The payment method may be electronic payment, a recording medium used in electronic payment, or a digital exchange medium. Examples of types of payment methods include credit cards, debit cards, IC-type electronic money, online electronic money, code payments, prepaid cards, and point cards. IC-type electronic money may be a type of electronic money in which the balance is managed on an IC (Integrated Circuit) chip provided on a card or user terminal 6. Online electronic money may be a type of electronic money in which the balance is managed online. Code payments may be a means of enabling payments in response to an electronic device optically reading code information indicating either the payer or the recipient of the transaction price. In code payments, the payer may be a member of a comprehensive Internet service. The recipient of the price may be a store.When a user pays using a payment method available in a payment service supported by the payment server 10, the payment server 10 may receive payment information from the store payment terminal 20 of the store to which the payment is to be made or from the user terminal 6 of the user who is making the payment. The payment information may be information necessary for settling the payment. The payment server 10 may execute a payment process to settle the payment based on the payment information. If the payment information is information related to the use of a point card, the payment server 10 corresponding to a point program may execute a process for the user to use points and to award points to the user based on the payment information. Upon completion of the payment process, the payment server 10 may generate payment information. The payment information may be information indicating that a payment for the transaction has been made from the user to the store that is the provider of the transaction object. The payment information may include information related to the executed payment. The payment server 10 may transmit the generated payment information to the member information management server 2.

[0140] Each store payment terminal 20 may be a terminal device used by store staff primarily for settling payments made by users to the store. Examples of store payment terminals 20 include POS (Point of Sales) registers, personal computers, tablet computers, etc. Each store payment terminal 20 may be equipped with, for example, a reading unit. The reading unit may be a device that reads payment method user identification information. The payment method user identification information may be information for identifying a user who uses a payment method. Examples of payment method user identification information include a card number, membership number, user ID, etc. Examples of the reading unit include a barcode reader, magnetic reader, camera, etc.

[0141] FIG. 24 is a diagram showing an example of the processing flow up to the stamp being applied. In FIG. 24, the same processes as in FIG. 3 are assigned the same reference numerals. As shown in FIG. 24, first, a user makes payment at a store to purchase a transaction object (step S21). At this time, the user presents a payment method or user terminal 6 to the store. A store employee causes the store payment terminal 20 to read the payment method user identification information from the payment method or user terminal 6. After reading the payment method user identification information, the store payment terminal 20 transmits the payment information to the payment information settlement server 10 (step S22). When using code payment, the user causes a code indicating the payment method user identification information to be displayed on the screen of the user terminal 6. The store payment terminal 20 reads the code and transmits the payment information to the payment information settlement server 10. Alternatively, a store employee causes the store payment terminal 20 to display the payment code on the screen of the store payment terminal 20. The user terminal 6 reads the code and transmits the payment information to the payment information settlement server 10. The payment information may include payment method user identification information, a business ID, a store ID, a payment amount, etc. If a point card is used, the payment information may further include the number of points to be used. The business ID may be identification information for identifying a business involved in the operation of the store using the store payment terminal 20. For example, if the store belongs to a chain or other store group consisting of multiple stores, the business indicated by the business ID may be the headquarters of the store group or a franchisor. The store ID may be identification information for identifying the store using the store payment terminal 20. The store ID may be an example of payment recipient identification information. The payment recipient identification information may be identification information for identifying the payment recipient. The payment amount may indicate the amount to be paid by payment. The payment server 10 executes payment processing based on the payment information (step S23). Then, the payment server 10 generates payment information. This payment information may include at least payment source identification information and payment recipient identification information. The payment source identification information may be identification information for identifying the user who is paying the price. The payment source identification information may be, for example, a user ID.For example, the payment server 10 may have a database that associates user IDs with payment method user identification information. This makes it possible to identify which member of the Internet comprehensive service made the payment. The payment server 10 may obtain from this database the user ID associated with the payment method user identification information included in the payment information. The payment recipient identification information may be identification information that identifies the store to which the payment is made, among the stores that provide the transaction object. The payment recipient identification information may be, for example, a store ID or a combination of a business ID and a store ID. The payment information may further include a service ID, payment amount, payment date and time, etc. The service ID may indicate a payment service supported by the payment server 10. The payment date and time may indicate the date and time when the payment was made. The payment server 10 transmits the generated payment information to the member information management server 2 (step S24). The member information management server 2 stores this payment information as an action log. The action log may be information indicating the actions taken by a member of the Internet comprehensive service by using services included in the Internet comprehensive service. The member information management server 2 transmits the payment information as an action log to the stamp card management server 1 at a predetermined timing (step S25). The stamp card management server 1 stores this payment information.

[0142] When the payment is completed, steps S11a to S14a or steps S11b to S14b are executed by the store terminal 5 of the store to which the payment is made, the user terminal 6 of the user who made the payment, and the stamp card management server 1. The stamp card management server 1 that has received the stamp granting request grants a stamp to the stamp card of the user based on the payment information acquired from the membership information management server 2, on the condition that the user of the user terminal 6 has entered the campaign for the stamp card in question and that the user has made payment to the store at the store terminal 5 (step S26).

[0143] [2-2.Device configuration] [2-2-1. Membership information management server] Next, the configuration of the member information management server 2 will be described with reference to Figs. 25 and 26. Fig. 25 is a block diagram showing an example of the general configuration of the member information management server 2 according to this embodiment. In Fig. 25, the same elements as in Fig. 7 are assigned the same reference numerals. As shown in Fig. 25, the memory unit 24 of the member information management server 2 may store a member DB 24a and a behavior history DB 24b. Other aspects may be the same as those of the first embodiment.

[0144] FIG. 26 is a diagram illustrating an example of the contents stored in the action history DB 24b of the member information management server 2. The action history DB 24b may store a history of actions taken by a user using any of the services included in the comprehensive Internet service. For example, the action history DB 24b may store an action log indicating that a predetermined action has been taken each time the action is taken in each service. As shown in FIG. 26, the action history DB 24b may store, as the action log, an action log ID, a user ID, a service ID, and action content information, each associated with one another. The action log ID may be identification information for identifying the action log. The user ID may indicate the user who took the action. The service ID may be identification information for identifying the service used by the user when the action was taken. The action content information may indicate the content of the action taken. The action content information may vary depending on the service used and the type of action. For example, when a user pays for a store using a payment service, the action content information included in the action log as payment information may include the date and time of payment, the store ID, and the payment amount. The member information management server 2 may generate a new action log ID when receiving an action log from the payment server 10 or a predetermined server device corresponding to a service included in the Internet comprehensive service. The member information management server 2 may add the generated action log ID to the action log and store this action log ID in the action history DB 24b.

[0145] [2-2-2. Stamp card management server] Next, the configuration of the stamp card management server 1 will be described with reference to Figs. 27 and 28. Fig. 27 is a block diagram showing an example of the schematic configuration of the stamp card management server 1 according to this embodiment. In Fig. 27, the same elements as those in Fig. 4 are given the same reference numerals. As shown in Fig. 27, the storage unit 14 of the stamp card management server 1 may store a store DB 14f, a stamp action history DB 14g, and a stamp grant request DB 14h in addition to the stamp card DB 14a to the benefit DB 14e. Other aspects may be the same as those in the first embodiment.

[0146] FIG. 28 is a diagram showing an example of the contents stored in the database of the stamp card management server 1. As shown in FIG. 28, the account information stored in the tool account DB 14b may include a store name, a password, a store ID, and a business ID. The store ID may indicate the store that is the target of the promotion. The business ID may indicate the business involved in the operation of the store.

[0147] The store DB 14f may store store information about each store operated by a business operator that is a member of at least one of the payment services included in the comprehensive internet service. For example, as shown in FIG. 28, the store DB 14f may store a store ID, a store name, and a business operator ID in association with each other as store information. The store name may indicate the name of the store identified by the store ID. The business operator ID may indicate a business operator involved in the operation of the store identified by the store ID.

[0148] The stamp action history DB 14g may store payment information for each payment. Specifically, the stamp action history DB 14g may store an action log acquired from the member information management server 2 to apply a stamp to a stamp card. For example, as shown in FIG. 12 , the stamp action history DB 14g may store an action log, such as an action log ID, a user ID, a service ID, and in-action information, in association with one another. The stamp card management server 1 may acquire an action log from the member information management server 2, for example, every time a predetermined period elapses. Examples of the length of the predetermined period include 10 minutes, 1 hour, 6 hours, and 1 day. The stamp card management server 1 may send, for example, an action log request to the member information management server 2. The action log request may include the service ID of one or more services for which action logs are to be acquired. In this embodiment, the action log request may include the service ID of the payment service. Upon receiving the action log request, the member information management server 2 may search the action history DB 24b for an action log that includes any of the service IDs included in the stamp application request. At this time, the member information management server 2 may search for action logs stored after searching the previous action log. The member information management server 2 may transmit each of the searched action logs to the stamp card management server 1. The stamp card management server 1 may store each of the received action logs in the stamp action history DB 14g.

[0149] The stamp granting request DB 14h may store stamp granting requests transmitted from the store terminal 5 and the user terminal 6 to the stamp card management server 1. For example, as shown in Fig. 28, the stamp granting request DB 14h may store, as a stamp granting request, a card URL, a user ID, a store name, granting date and time, the number of stamps granted, and the like, in association with one another.

[0150] [2-3. Functional overview of the system control unit of the stamp card management server] Next, an overview of the functions of the system control unit 11 of the stamp card management server 1 will be described with reference to Fig. 29. Fig. 29 is a diagram showing an example of functional blocks of the system control unit 11 of the stamp card management server 1 according to this embodiment. In Fig. 29, the same elements as in Fig. 10 are assigned the same reference numerals. As shown in Fig. 29, the system control unit 11 functions as an account registration screen information transmission unit 1101 to a stamp card screen information transmission unit 1111, and may also function as a payment information search unit 1121.

[0151] The authentication information storage control unit 1103 may store account information including the store name and password as well as the store ID in the tool account DB 14b. For example, the account registration screen 100 may allow the user to specify a business operator involved in the operation of the store that is the target of the promotion. The operator terminal 3 or the promotion main terminal 4 may transmit the business operator ID of the specified business operator along with the input store name and password to the stamp card management server 1. The authentication information storage control unit 1103 may search the store DB 14f for a store ID associated with a combination that matches the combination of the received business operator ID and store name. The authentication information storage control unit 1103 may store account information including the received store name and password and the searched store ID in the tool account DB 14b.

[0152] The stamp granting request receiving unit 1108 may store the stamp granting request received from the store terminal 5 or the user terminal 6 in the stamp granting request DB 14h.

[0153] The application information search unit 1109 may acquire any user identification information from the entry DB 14c. For example, the application information search unit 1109 may search the entry DB 14c for user identification information that identifies the same user as the user identified by the user identification information included in the stamp granting request received by the stamp granting request receiving unit 1108. For example, the application information search unit 1109 may search for user identification information that matches the user identification information included in the stamp granting request received by the stamp granting request receiving unit 1108. In this case, the application information search unit 1109 may search the entry DB 14c for entry information that includes a combination that matches the combination of user identification information included in the user information included in the stamp granting request and stamp card identification information included in the promotion target information included in the stamp granting request. The application information search unit 1109 may acquire the stamp granting request received by the stamp granting request receiving unit 1108 from the stamp granting request DB 14h. The application information search unit 1109 may perform a search based on the acquired stamp granting request.

[0154] The payment information search unit 1121 may search the stamp behavior history DB 14g for payment information including payment source identification information for identifying, as a payment source, a user identified by the user identification information acquired by the usage application information search unit 1109 or a user identified by the user identification information included in the user information received by the stamp granting request receiving unit 1108. As a result, the payment information search unit 1121 may acquire payment information indicating that a payment for payment to a promotion target has been made by the user identified by the user identification information. For example, the payment information search unit 1121 may search for search information including a user ID that matches the user ID searched from the entry DB 14c by the usage application information search unit 1109. At this time, the payment information search unit 1121 may acquire payment information indicating that a payment for payment to a promotion target has been made by the user identified by the user identification information included in the stamp granting request received by the stamp granting request receiving unit 1108. For example, the payment information search unit 1121 may search for payment information including payment source identification information for identifying the user identified by the user identification information acquired by the usage application information search unit 1109 as the payment source, and payment recipient identification information for identifying the provider identified by the provider identification information included in the stamp granting request received by the stamp granting request receiving unit 1108 as the payment recipient. In this way, the payment information search unit 1121 may acquire payment information. For example, the payment information search unit 1121 may search the tool account DB 14b for account information associated with the card URL included in the stamp granting request, including the store name included in the stamp granting request. The payment information search unit 1121 may acquire a business ID and a store ID from the searched account information. The payment information search unit 1121 may search for payment information including a combination that matches the combination of the user ID included in the search request and the acquired business ID and store ID.

[0155] The payment information search unit 1121 may search only for payment information that includes a payment date and time within a predetermined period before or after the stamp grant date and time included in the stamp grant request. Examples of the length of the predetermined period include 1 minute, 5 minutes, 10 minutes, etc.

[0156] The payment information search unit 1121 may execute a search for payment information on the condition that corresponding user identification information is found by the search by the usage application information search unit 1109. For example, the payment information search unit 1121 may execute a search for payment information on the condition that corresponding entry information is found. If corresponding user identification information is not found, the payment information search unit 1121 may not execute a search.

[0157] The stamp granting unit 1110 may grant a stamp to a user identified by the user identification information acquired by the usage application information searching unit 1109 or to a user identified by the user identification information included in the user information received by the stamp granting request receiving unit 1108, on condition that corresponding search information is found by the search by the payment information searching unit 1121. The stamp granting unit 1110 may not grant a stamp if corresponding search information is not found. Furthermore, the stamp granting unit 1110 may not grant a stamp if corresponding user identification information is not found by the search by the usage application information searching unit 1109. For example, the stamp granting unit 1110 may not grant a stamp if corresponding entry information is not found.

[0158] [2-4. Operation of communication system] Next, the operation of the communication system S will be described with reference to FIGS.

[0159] Fig. 30 is a sequence diagram showing an example of the operation of the communication system S when the store terminal 5 displays a code and grants a stamp. In Fig. 30, the same processes as in Fig. 19 are assigned the same reference numerals. As shown in Fig. 30, steps S401 to S410 are first executed. Next, the stamp granting request receiving unit 1108 stores the stamp granting request received from the user terminal 6 in the stamp granting request DB 14h (step S421).

[0160] Fig. 31 is a sequence diagram showing an example of the operation of the communication system S when the store terminal 5 reads a code and applies a stamp. In Fig. 31, the same processes as in Fig. 20 are assigned the same reference numerals. As shown in Fig. 31, steps S501 to S510 are first executed. Next, the stamp application request receiving unit 1108 stores the stamp application request received from the user terminal 6 in the stamp application request DB 14h (step S521).

[0161] 32 is a flowchart showing an example of stamp control loop processing executed by the system control unit 11 of the stamp card management server 1 according to this embodiment. For example, the system control unit 11 may execute the stamp control loop processing every time a predetermined period of time elapses. Examples of the length of the predetermined period include one hour, six hours, one day, etc.

[0162] 32, the stamping unit 1110 determines whether or not at least one stamping request is stored in the stamping request DB 14h (step S801). If a stamping request is stored (step S801: YES), the stamping unit 1110 selects one stamping request from the stamping request DB 14h (step S802). Next, the system control unit 11 executes stamp control processing using the selected stamping request (step S803). Next, the stamping unit 1110 deletes the selected stamping request from the stamping request DB 14h (step S804), and the processing proceeds to step S801. If no stamping request is stored in the stamping request DB 14h (step S801: NO), the stamp control loop processing ends.

[0163] 33 is a flowchart showing an example of stamp control processing executed by the system control unit 11 of the stamp card management server 1 according to this embodiment. In FIG. 33, the same processes as those in FIG. 21 are denoted by the same reference numerals.

[0164] As shown in FIG. 33, steps S601 to S604 are executed first. If the number of stamps given so far has not reached the stamp giving limit (step S604: NO), the payment information search unit 1121 acquires a business operator ID and a store ID from account information including the store name included in the stamp giving request, among the account information stored in the tool account DB 14b in association with the card URL acquired from the stamp giving request (step S621). Next, the payment information search unit 1121 searches for payment information including a combination that matches the combination of the user ID, business operator ID, and store ID acquired from the stamp giving request, and that includes a service ID indicating any payment service (step S622). As a result of the search, the payment information search unit 1121 determines whether or not there is matching payment information (step S623). If there is matching payment information (step S623: YES), the stamp giving unit 1110 executes the stamp giving process (step S605), and the stamp control process ends. If there is no corresponding payment information (step S623: NO), the stamp control process ends.

[0165] As described above, according to this embodiment, when a stamp is granted on the condition that the user has paid the price, it is not necessary to execute the process for granting the stamp for each payment information. As a result, since it is not necessary to execute the process for each occurrence of payment, when a stamp is granted based on information related to the payment, it is possible to execute the process for granting the stamp more efficiently.

[0166] Here, the stamp card management server 1 may search the entry DB 14c for entry information that includes a combination of user identification information included in the received user information and stamp card identification information included in the received promotion target information. The stamp card management server 1 may also search for payment information on the condition that matching entry information is found. If matching entry information is not found, the stamp card management server 1 may not grant a stamp. In this case, there is no need to search for payment information for users who have not applied to use a stamp card. This allows for more efficient processing of stamp granting.

[0167] The stamp card management server 1 may also search for payment information including payment source identification information for identifying the user identified by the user identification information included in the received user information as the payment source, and payment destination identification information for identifying the promotion target identified by the promotion target identification information included in the received promotion target information as the payment destination. In this case, a stamp can be awarded on the condition that the user to whom the stamp is to be awarded has paid the price to the provider who awarded the stamp.

[0168] Alternatively, the stamp card management server 1 may receive a stamp granting request. Alternatively, the stamp card management server 1 may search the entry DB 14c for user identification information for identifying the same user as the user identified by the user identification information included in the stamp granting request. Alternatively, the stamp card management server 1 may search for payment information on the condition that the corresponding user identification information is found. Alternatively, if the stamp card management server 1 does not find the corresponding user identification information, it may not grant a stamp. In this case, it is sufficient to search for payment information indicating that the user related to the request for granting of the stamp, among the users who have applied to use the stamp card, has made a payment for the price, thereby making it possible to execute the process related to granting the stamp more efficiently.

[0169] The stamp card management server 1 may also search for entry information containing a combination that matches the combination of user identification information and stamp card identification information included in the stamp granting request. The stamp card management server 1 may also search for payment information on the condition that corresponding previous entry information is found. If the stamp card management server 1 does not find corresponding entry information, it may not grant a stamp. In this case, even if a user is involved in the granting of a stamp, there is no need to search for payment information for users who have not applied to use the stamp card to which the stamp is to be granted. This allows the process of granting stamps to be executed more efficiently.

[0170] The stamp card management server 1 may also search for payment information including payment source identification information for identifying the user identified by the user identification information included in the stamp granting request as the payment source, and payment recipient identification information for identifying the provider identified by the provider identification information included in the stamp granting request as the payment recipient. In this case, the stamp can be granted on the condition that the user to whom the stamp is to be granted has paid the price to the provider who granted the stamp.

[0171] 3. Third Embodiment Next, a third embodiment will be described. Except for the points described below, the third embodiment may be the same as the second embodiment. In this embodiment, stamps are given to a user regardless of whether the user has made a payment. However, the number of stamps given to a user varies depending on whether the user has made a payment.

[0172] [3-1. Functional overview of the system control unit of the stamp card management server] First, the outline of the functions of the system control unit 11 of the stamp card management server 1 will be explained with reference to FIG.

[0173] As described above, the payment information search unit 1121 searches for search information. The stamp granting unit 1110 may grant different numbers of stamps depending on whether or not matching payment information is found through a search by the payment information search unit 1121. For example, the stamp granting unit 1110 may grant more stamps when matching payment information is found than when matching payment information is not found.

[0174] FIG. 34 is a diagram showing an example of the number of stamps awarded. As shown in FIG. 34, if the user to whom stamps are to be awarded does not make a payment, i.e., if the corresponding payment information is not found, stamps may be awarded in a number equivalent to the number of awarded stamps specified by the store in the stamp awarding tool. If the user to whom stamps are to be awarded makes a payment, i.e., if the corresponding payment information is found, the number of awarded stamps may be awarded in a number equivalent to the sum of the number of awarded stamps specified by the store in the stamp awarding tool and a predetermined number of additional stamps. The number of additional stamps may indicate a number added to the number of awarded stamps. The number of additional stamps is an integer greater than or equal to 1. Note that if the user makes a payment, stamps may be awarded in a number equivalent to a predetermined multiple of the number of awarded stamps specified by the store. This multiplier is a real number greater than 1.

[0175] [3-2. Operation of the communication system] Next, the operation of the communication system S will be described with reference to Fig. 35. The processing described in the second embodiment with reference to Fig. 30 and Fig. 31 is executed, and also the stamp control loop processing shown in Fig. 32 is executed. The stamp control processing called from this stamp control loop processing may be the processing described in the first embodiment with reference to Fig. 21.

[0176] 35 is a flowchart showing an example of a stamp giving process executed by the system control unit 11 of the stamp card management server 1 according to this embodiment. In FIG. 35, the same processes as those in FIG. 22 are denoted by the same reference numerals.

[0177] As shown in FIG. 35, the payment information search unit 1121 acquires a business ID and a store ID from account information including a store name included in the stamp granting request, among account information stored in the tool account DB 14b in association with the card URL acquired from the stamp granting request (step S721). Next, the payment information search unit 1121 searches, as payment information, for a decision behavior log that includes a combination that matches the user ID acquired from the stamp granting request and the acquired business ID and store ID, and that includes a service ID indicating any payment service (step S722). As a result of the search, the payment information search unit 1121 determines whether or not there is matching payment information (step S723). If there is matching payment information (step S723: YES), the stamp granting unit 1110 adds a predetermined number of added stamps to the number of assigned stamps acquired from the stamp granting request to update the number of assigned stamps (step S724). If there is no corresponding payment information (step S723: NO), or after step S724, the stamp granting unit 1110 adds the number of granted stamps to the current number of stamps included in the entry information searched in step S601 of the stamp control process, thereby updating this current number of stamps stored in the entry DB 14c (step S701). If step S724 is executed, the number of granted stamps added is the updated number of stamps. If step S724 is not executed, the number of granted stamps added is the number of granted stamps acquired from the stamp grant request. Then, steps S702 to S709 are executed.

[0178] As described above, according to this embodiment, users can acquire stamps regardless of whether they have made a payment or not, and users who have made a payment can be given preferential treatment.

[0179] [4. Fourth Embodiment] Next, a fourth embodiment will be described. Except for the following points, the fourth embodiment may be the same as the second embodiment. In this embodiment, the number of stamps given to a user varies depending on the amount paid by the user to the store through settlement.

[0180] [4-1. Functional overview of the system control unit of the stamp card management server] First, the outline of the functions of the system control unit 11 of the stamp card management server 1 will be described with reference to FIG.

[0181] As described above, the payment information search unit 1121 may acquire or search for payment information indicating that a payment has been made to pay the promotion target from a user identified by the user identification information included in the stamp granting request received by the stamp granting request receiving unit 1108, and including the payment amount.

[0182] The stamp granting unit 1110 may change the number of stamps to be granted depending on the payment amount included in the payment information acquired or searched by the payment information search unit 1121. For example, the stamp granting unit 1110 may grant more stamps the larger the payment amount. For example, the memory unit 14 may store a table showing the correspondence between the payment amount and the number of added stamps. The stamp granting unit 1110 may determine the number of stamps to be granted based on this table and the payment amount.

[0183] FIG. 36 is a diagram showing an example of the number of stamps awarded. As shown in FIG. 35, if the payment amount is less than 1,000 yen, stamps equivalent to the number of stamps awarded designated by the store using the stamp awarding tool may be awarded. If the payment amount is 1,000 yen or more but less than 3,000 yen, stamps awarded may be one more than the number of stamps awarded designated by the store. If the payment amount is 3,000 yen or more, stamps awarded may be two more than the number of stamps awarded designated by the store. In the example shown in FIG. 36, the number of stamps awarded is set to three levels. However, the number of stamps awarded may also be set to two levels, or four or more levels.

[0184] [4-2. Operation of communication system] Next, the operation of the communication system S will be described with reference to Fig. 37. Fig. 37 is a flowchart showing an example of a stamp giving process executed by the system control unit 11 of the stamp card management server 1 according to this embodiment. In Fig. 37, the same processes as those in Fig. 22 are denoted by the same reference numerals.

[0185] As shown in FIG. 37, the stamp granting unit 1110 acquires the payment amount from the payment information retrieved, for example, in step S622 of the stamp control process shown in FIG. 33 (step S741). Next, the stamp granting unit 1110 acquires the number of added stamps corresponding to the acquired payment amount (step S742). Next, the stamp granting unit 1110 adds the acquired number of added stamps to the number of assigned stamps acquired from the stamp grant request, thereby updating the number of assigned stamps (step S743). Next, the stamp granting unit 1110 adds the number of assigned stamps to the current number of stamps included in the entry information retrieved in step S601 of the stamp control process, thereby updating this current number of stamps stored in the entry DB 14c (step S701). Then, steps S702 to S709 are executed.

[0186] The stamp granting unit 1110 may change the number of stamps to be granted depending on the payment amount, and may also change the number of stamps to be granted depending on whether or not the user has made a payment, as described in the third embodiment.

[0187] As described above, according to this embodiment, the number of stamps given to a user can be changed depending on the amount of payment made by the user.

[0188] [5. Fifth Embodiment] Next, a fifth embodiment will be described. Except for the following points, the fifth embodiment may be the same as at least one of the embodiments described so far. In this embodiment, the number of stamps given to a user changes based on the user's actions regarding a predetermined service other than the stamp card service.

[0189] [5-1. Communication System Configuration] First, the configuration and functional overview of the communication system S according to this embodiment will be described with reference to FIG. 38. FIG. 38 is a diagram showing an example of the schematic configuration of the communication system S according to this embodiment. In FIG. 38, the same elements as those in FIG. 23 are assigned the same reference numerals. As shown in FIG. 38, the communication system S may be configured to include a stamp card management server 1, a member information management server 2, an operator terminal 3, multiple promotion host terminals 4, multiple store terminals 5, multiple user terminals 6, one or multiple payment servers 10, multiple store payment terminals 20, a transaction server 30, and a service server 40. These devices may be connected to a network NW.

[0190] The trading server 30 may be a server device that executes processing related to a predetermined trading service. As described above, the trading service may be a service that enables electronic commerce. The trading service may be provided through a website. Examples of trading services and trading service websites include online shopping malls, flea market services, service reservation sites, facility reservation sites, ticket sales sites, and online securities. The trading service supported by the trading server 30 may be one of the services included in the aforementioned comprehensive Internet services. Users of the trading service can purchase trading objects through the trading service. The trading server 30 may execute various processes in response to requests from the user terminal 6. For example, the trading server 30 may execute processes such as searching for trading objects, providing information about the trading objects, and completing transactions for the trading objects. Furthermore, the trading server 30 may record an action log indicating that a user has taken a predetermined action using the trading service. The trading server 30 may transmit the action log to the member information management server 2.

[0191] The service server 40 may be a server device that executes processing related to non-transaction services. Non-transaction services are different types of services from transaction services. Furthermore, non-transaction services may be different from both stamp card services and point programs. The non-transaction services supported by the service server 40 may be one of the services included in the comprehensive Internet service. An example of a non-transaction service is a periodic payment service. A periodic payment service is a service in which a user pays a usage fee for the service periodically. For example, the usage fee is paid monthly, every three months, or every year. Examples of periodic payment services include communication services, content distribution services, and other subscription services. A communication service may be a service that enables at least one of voice communication and data communication. A communication service may also be a service that enables at least one of mobile communication and fixed communication. Examples of mobile communication standards include 3G standards such as W-CDMA and CDMA2000, 4G standards such as LTE and WiMAX, and 5G standards such as IMT-2020. An example of a communication service that enables fixed-line communication is an optical fiber service. The content distribution service may be a service that distributes digital content. Examples of distributed content include videos, music, and e-books. Another example of a non-transaction service is a payment service. In this embodiment, however, the device that executes processing related to the payment service is the payment server 10. Therefore, the payment server 10 can also be considered an example of the service server 40. To use a non-transaction service, a user may be required to sign a contract for the use of the non-transaction service. This contract may be made online or offline. To sign a contract for the use of a non-transaction service, the user may be required to be a member of an Internet comprehensive service in advance. The service server 40 may record an action log indicating that a user has taken a predetermined action while using the non-transaction service.The service server 40 may transmit the action log to the member information management server 2.

[0192] In the following explanation, the stamp card management server 1, like the second embodiment, grants stamps to a user based on payment information, on the condition that the user makes a payment at a store. However, like the first embodiment, the stamp card management server 1 may grant stamps without using payment information. In this case, the communication system S may not include the payment server 10 and the store payment terminal 20. Alternatively, like the third embodiment, the stamp card management server 1 may change the number of stamps to grant depending on whether the user has made a payment.

[0193] [5-2. Membership information management server configuration] Next, the configuration of the member information management server 2 will be described with reference to Fig. 39. Fig. 39 is a diagram showing an example of the contents stored in the action history DB 24b of the member information management server 2 according to this embodiment. The action history DB 24b stores action logs as payment information transmitted from the payment server 10 to the member information management server 2, and may also store action logs transmitted from each of the transaction server 30 and the service server 40.

[0194] The action log from the transaction server 30 may include, for example, an action log indicating that a user has conducted a transaction in a transaction service. This action log may indicate the content of the transaction. In particular, the action content information in the action log of the transaction service may indicate the content of the transaction. As shown in FIG. 39, the action content information in the action log of the transaction service may include at least one of the transaction date and time, a transaction object provider ID, a transaction object ID, and a transaction amount. The transaction date and time may indicate the date and time when the transaction was conducted. The transaction object provider ID may be identification information for identifying the provider who provided the transaction object to the user in the transaction. In other words, the transaction object provider ID may indicate the provider who sold the transaction object to the user. The transaction object ID may be identification information for identifying the transaction object traded in the transaction. In other words, the transaction object ID may indicate the transaction object purchased by the user. The transaction amount may indicate the amount paid by the user in the transaction.

[0195] The action log from the service server 40 may include, for example, an action log indicating that a user has signed a contract for a non-transaction service and an action log indicating that the user has terminated that contract. As shown in FIG. 39, the action content information in the action log for a non-transaction service may include a procedure date and time and a procedure type. The procedure date and time may indicate the date and time when the procedure for signing a contract for a non-transaction service or for terminating the contract was performed. The procedure type may indicate whether the procedure performed was for signing a contract or for terminating the contract.

[0196] The stamp card management server 1 may acquire an action log for transaction services and an action log for non-transaction services as well as acquire an action log as payment information from the member information management server 2. The stamp card management server 1 may store the acquired action logs in the stamp action history DB 14g.

[0197] [5-3. Functional overview of the system control unit of the stamp card management server] Next, an overview of the functions of the system control unit 11 of the stamp card management server 1 will be described with reference to Figs. 40 and 41. Fig. 40 is a diagram showing an example of functional blocks of the system control unit 11 of the stamp card management server 1 according to this embodiment. In Fig. 40, the same elements as those in Fig. 29 are given the same reference numerals. As shown in Fig. 40, the system control unit 11 functions as an account registration screen information sending unit 1101 to a stamp card screen information sending unit 1111 and a payment information searching unit 1121, and may also function as a transaction service action history information acquiring unit 1131 and a non-transaction service action history information acquiring unit 1132.

[0198] The transaction service action history information acquisition unit 1131 may acquire transaction service action history information. The transaction service action history information may be information indicating a history of actions taken regarding a transaction service. Here, the transaction service action history information acquisition unit 1131 may acquire transaction service action history information indicating a history of actions taken by a user identified by user identification information included in the user information received by the stamp assignment request receiving unit 1108 or a user identified by user identification information acquired by the usage application information search unit 1109. For example, the transaction service action history information acquisition unit 1131 may acquire, as transaction service action history information, one or more action logs including the service ID of the transaction service and a user ID that matches the user ID included in the stamp assignment request or the user ID included in the searched entry information. Alternatively, the transaction service action history information acquisition unit 1131 may acquire transaction service action history information from the member information management server 2. When a user conducts a transaction in a transaction service, the acquired transaction service action history information may indicate the content of the transaction. For example, the transaction service action history information may include at least one of the transaction date and time, transaction target provider ID, transaction target ID, and transaction amount.

[0199] The non-transaction service behavior history information acquisition unit 1132 may acquire non-transaction service behavior history information. The non-transaction service behavior history information may be information indicating a history of behaviors taken regarding non-transaction services. Here, the non-transaction service behavior history information acquisition unit 1132 may acquire non-transaction service behavior history information indicating a history of behaviors by a user identified by user identification information included in the user information received by the stamp granting request receiving unit 1108 or a user identified by user identification information acquired by the usage application information searching unit 1109. For example, the non-transaction service behavior history information acquisition unit 1132 may acquire, as non-transaction service behavior history information, one or more behavior logs including a service ID of the non-transaction service and a user ID that matches the user ID included in the stamp granting request or the user ID included in the searched entry information. Alternatively, the non-transaction service behavior history information acquisition unit 1132 may acquire non-transaction service behavior history information from the member information management server 2. When a user takes an action to sign up for or cancel a non-transaction service contract, the acquired non-transaction service behavior history information may indicate that the action was taken. For example, the non-transaction service behavior history information may include at least the procedure type among the procedure date and time and the procedure type.

[0200] The stamp assigning unit 1110 may change the number of stamps to be assigned based on at least one of the behavior history indicated by the transaction service behavior history information acquired by the transaction service behavior history information acquisition unit 1131 and the behavior history indicated by the non-transaction service behavior history information acquisition unit 1132.

[0201] When using transaction service behavior history information, the stamp granting unit 1110 may change the number of stamps to be granted based on the content of the transaction. For example, the stamp granting unit 1110 may grant a greater number of stamps to a user when the content of the transaction indicated by the transaction service behavior history information satisfies predetermined transaction content conditions than when the content of the transaction does not satisfy the predetermined transaction content conditions. Examples of transaction content conditions include conducting a transaction within a predetermined period, conducting a transaction with a predetermined provider, purchasing a predetermined transaction object, conducting a transaction for a predetermined transaction amount or more, conducting a predetermined number of transactions within a predetermined period, conducting transactions with a predetermined number of providers within a predetermined period, and the total transaction amount within a predetermined period being a predetermined amount or more. Examples of predetermined periods include the previous month, this month, last year, this year, etc.

[0202] When using non-transaction service behavior history information, the stamp granting unit 1110 may change the number of stamps to be granted depending on the content of the user's behavior in the non-transaction service. For example, the stamp granting unit 1110 may grant a greater number of stamps to a user when the content of the behavior indicated by the non-transaction service behavior history information satisfies a predetermined behavior content condition than when the content of the behavior does not satisfy the predetermined behavior content condition. An example of a behavior content condition is whether the user is subscribed to a non-transaction service. For example, the stamp granting unit 1110 may grant a greater number of stamps when the user is subscribed to a non-transaction service than when the user is not subscribed to the non-transaction service. Being non-subscribed to a non-transaction service includes the user never having signed a subscription to the non-transaction service and the user canceling the subscription to the non-transaction service. Other examples of behavior content conditions include using a non-transaction service a predetermined number of times or more within a predetermined period, making payments of a predetermined amount or more using a non-transaction service within a predetermined period, and purchasing a predetermined number or more trading objects using a non-transaction service within a predetermined period. Examples of the predetermined period include last month, this month, last year, this year, etc.

[0203] The stamp granting unit 1110 may change the number of stamps to be granted based on both the behavior history indicated by the transaction service behavior history information and the behavior history indicated by the non-transaction service behavior history information. For example, if the behavior history regarding the transaction service and the behavior history regarding the non-transaction service satisfy a predetermined condition, the stamp granting unit 1110 may grant a larger number of stamps than if the condition is not satisfied. The predetermined condition may be, for example, that the content of the transaction in the transaction service satisfies a predetermined transaction content condition, and that the behavior content regarding the non-transaction service satisfies a behavior content condition. The behavior content condition may be, for example, that a non-transaction service is currently under contract.

[0204] FIG. 41 is a diagram showing an example of the number of stamps awarded. For example, suppose the transaction content condition is that the transaction amount in the previous month in the transaction service is 3,000 yen or more. Furthermore, suppose the behavior content condition is that the user is currently subscribed to a non-transaction service. In this case, if the user purchased a transaction object in the transaction service for 3,000 yen or more in the previous month and is subscribed to the non-transaction service, stamps equivalent to the sum of the number of awarded stamps specified by the store using the stamp awarding tool and a predetermined additional stamp number may be awarded. If the user did not purchase anything in the transaction service in the previous month or purchased transaction objects for less than 3,000 yen, stamps equivalent to the number of awarded stamps specified by the store may be awarded. Furthermore, if the user is not subscribed to the non-transaction service, stamps equivalent to the number of awarded stamps specified by the store may be awarded.

[0205] [5-4. Operation of communication system] Next, the operation of the communication system S will be described with reference to Fig. 42. Fig. 42 is a flowchart showing an example of a stamp granting process executed by the system control unit 11 of the stamp card management server 1 according to this embodiment. In Fig. 42, the same processes as those in Fig. 22 are denoted by the same reference numerals.

[0206] As shown in FIG. 42, the transaction service action history information acquisition unit 1131 searches the stamp action history DB 14g for a purchase log that includes the user ID and the service ID of the transaction service acquired from the stamp granting request and that includes a transaction date and time within a predetermined period (step S761). Next, the stamp granting unit 1110 calculates the total transaction amount (step S762). For example, the stamp granting unit 1110 may acquire the transaction amount from each of the searched action logs. The stamp granting unit 1110 may calculate the sum of the acquired transaction amounts. Next, the stamp granting unit 1110 determines whether the total transaction amount is equal to or greater than a predetermined threshold amount (step S763).

[0207] If the total transaction amount is equal to or greater than the threshold amount (step S763: YES), the non-transaction service action history information acquisition unit 1132 searches the stamp action history DB 14g for a purchase log including the user ID and the service ID of the non-transaction service acquired from the stamp request (step S764). Next, the stamp assignment unit 1110 determines whether the user has a contract for the non-transaction service (step S765). For example, the stamp assignment unit 1110 may search the searched action logs for an action log including a procedure type indicating a contract and an action log including a procedure type indicating a contract cancellation. The stamp assignment unit 1110 may determine that the user has a contract if there is an action log including a procedure type indicating a contract and no action log including a procedure type indicating a contract cancellation. If there are both an action log including a procedure type indicating a contract and an action log including a procedure type indicating a contract cancellation, the stamp assignment unit 1110 may compare the procedure dates and times included in the respective action logs. The stamp assignment unit 1110 may determine that the user has a contract if the procedure date and time for the contract is newer than the procedure date and time for the contract cancellation.

[0208] If the user has a contract for a non-transaction service (step S765: YES), the stamp granting unit 1110 adds a predetermined number of additional stamps to the number of granted stamps acquired from the stamp granting request, and updates the number of granted stamps (step S766).

[0209] If the total transaction amount is less than the threshold amount (step S763: NO), or if the user has not subscribed to a non-transaction service (step S765: NO), the process proceeds to step S701. After step S766, the process also proceeds to step S701. In step S701, the stamp granting unit 1110 adds the number of granted stamps to the current number of stamps included in the entry information retrieved in step S601 of the stamp control process, thereby updating the current number of stamps stored in the entry DB 14c. Then, steps S702 to S709 are executed.

[0210] As described above, according to this embodiment, the number of stamps given can be changed depending on the actions taken by the user in transaction services and non-transaction services.

[0211] If the content of the transaction satisfies predetermined transaction content conditions and the user also satisfies the condition of having a contract for non-transaction services, the stamp card management server 1 may award more stamps than if the conditions were not met. In this case, it is possible to encourage the use of both transaction services and non-transaction services.

[0212] [6. Sixth Embodiment] Next, a sixth embodiment will be described. Except for the points described below, the sixth embodiment may be the same as at least one of the embodiments described so far. In this embodiment, when a stamp is given to a user, the user may also be given points that can be used for payment. These points may be points from a point program. As described above, a point program may be a service that allows a user to earn points on the condition that the user has paid for a transaction, and may be a service that allows the user's points to be used for payment.

[0213] A service that allows users to use points earned through a point program is called a point program usage service. A point program usage service may be, for example, a service different from a point program and that allows users to use a point program. There may be one or more point program usage services. At least one of the point program usage services may be a service that allows points to be used through a point program to pay for payments incurred when using that service. Furthermore, at least one of the point program usage services may be a service that awards points to users through a point program. Furthermore, at least one of the point program usage services may be a service included in the aforementioned comprehensive Internet service.

[0214] The point program utilization service may or may not include at least one transaction service. The transaction service as the point program utilization service may allow points to be used to pay for transactions made with the transaction service. Furthermore, the transaction service as the point program utilization service may grant points equivalent to a predetermined percentage of the purchase price to a user when the user settles the purchase price to be paid for a transaction made with the transaction service.

[0215] A point program utilization service may or may not include at least one non-transaction service. A non-transaction service serving as a point program utilization service may or may not include at least one periodic usage fee payment service. A periodic usage fee payment service serving as a point program utilization service may allow points to be used to pay usage fees. Furthermore, a periodic usage fee payment service serving as a point program utilization service may, when a user pays a usage fee, grant the user points equivalent to a predetermined percentage of the usage fee. A non-transaction service serving as a point program utilization service may or may not include at least one payment service. A payment service serving as a point program utilization service may allow points to be used to pay for the amount paid using that payment service. Furthermore, a payment service serving as a point program utilization service may, when a user pays for the amount, grant the user points equivalent to a predetermined percentage of the amount paid.

[0216] A transaction service serving as a point program utilization service may allow a user to specify whether or not to use points and the number of points to use each time the user performs a transaction. A non-transaction service serving as a point program utilization service may allow a user to set in advance whether or not to use points and the number of points to use. For example, the user may be able to set whether or not to use points and the number of points to use. The non-transaction service may apply the user's prior setting to each payment. Alternatively, the non-transaction service may apply the setting only to the first payment after the user sets the use of points. The non-transaction service may not allow points to be used for payments until a new setting is made by the user.

[0217] When there are multiple point program use services, the points of the point program may be points common to those multiple services. Common points may indicate points that can be used in any of those multiple point program use services. Alternatively, common points may indicate points that can be earned in any of those multiple point program use services. Alternatively, common points may indicate that points earned by a user in one of those multiple point program use services can be used in other point program use services. Points may be usable in both transaction services and non-transaction services.

[0218] Points held by a user are called usable points. A point program may allow a user to acquire one or more types of points. Points may be classified according to how their expiration dates are determined. User points expire upon their expiration dates. Examples of point types include regular points and limited-time points. The expiration date of regular points may be a predetermined period after the last regular points granted to the user. In other words, the expiration date of regular points held by a user may be extended each time new regular points are granted. Generally, regular points may be granted to a user upon payment of a transaction item. The expiration date of limited-time points may be managed for each granted limited-time point. The expiration date of each limited-time point is not extended. Generally, limited-time points may be granted to a user without payment of the transaction item. For example, when a user purchases a transaction item during a limited-time campaign, regular points may be granted to the user, along with bonus points.

[0219] [6-1. Communication System Configuration] Next, the configuration and functional overview of the communication system S according to this embodiment will be described with reference to FIG. 43. FIG. 43 is a diagram showing an example of the schematic configuration of the communication system S according to this embodiment. In FIG. 43, the same elements as those in FIG. 38 are assigned the same reference numerals. As shown in FIG. 43, the communication system S may be configured to include a stamp card management server 1, a member information management server 2, an operator terminal 3, multiple promotion host terminals 4, multiple store terminals 5, multiple user terminals 6, one or multiple payment servers 10, multiple store payment terminals 20, a transaction server 30, a service server 40, and a point management server 7. These devices may be connected to a network NW.

[0220] The point management server 7 may be a server device that executes a process for managing available points for each user in a point program. In response to a request from the payment server 10, the transaction server 30, or the service server 40, the point management server 7 may execute a process for a service supported by the server device to grant points to the user, or a process for the user to use points. The point management server 7 may also increase or decrease the available points for the user. When a user uses a point card at a store, the store payment terminal 20 may transmit payment information related to the use of the point card to the point management server 7. The point management server 7 may execute a process for the user to use points and for granting points to the user based on the payment information. The point management server 7 may also generate payment information and transmit this payment information to the member information management server 2.

[0221] In the following explanation, the stamp card management server 1, like the second embodiment, grants stamps to a user based on payment information, on the condition that the user makes a payment at a store. However, like the first embodiment, the stamp card management server 1 may grant stamps without using payment information. In this case, the communication system S may not include the payment server 10 and the store payment terminal 20. Alternatively, like the third embodiment, the stamp card management server 1 may change the number of stamps to grant depending on whether the user has made a payment.

[0222] [6-2. Configuration of the point management server] Next, the configuration of the point management server 7 will be described with reference to Figs. 44 and 45. Fig. 44 is a block diagram showing an example of the schematic configuration of the point management server 7 according to this embodiment. As shown in Fig. 44, the point management server 7 includes a system control unit 71, a system bus 72, an input / output interface 73, a storage unit 74, and a communication unit 75. The system control unit 71 and the input / output interface 73 are connected via the system bus 72.

[0223] The system control unit 71 is composed of a CPU 71a, a ROM 71b, a RAM 71c, and the like.

[0224] The input / output interface 73 performs interface processing between the storage unit 74 and the communication unit 75 and the system control unit 71 .

[0225] The storage unit 74 is configured with, for example, a hard disk drive or the like. Point information may be stored in this storage unit 74. The point information may be information indicating the number of points granted to a user or the number of points the user has. The point information may be stored in association with the user to whom the points have been granted. For example, the point information may be stored in association with user identification information for identifying the user. The point information may be stored for each user. Alternatively, the point information may be stored each time points are granted. The storage unit 74 may store a regular point DB74a and a limited-time point DB74b as databases containing point information.

[0226] Figure 45 is a diagram showing an example of the contents stored in the database of the point management server 7 according to this embodiment. The regular point DB 74a may store information about regular points among the usable points held by the user for each user. For example, the regular point DB 74a may store a user ID, the number of regular points, an expiration date, etc., in association with one another. The user ID may indicate the user who holds the regular points. The number of regular points may indicate the number of regular points. The number of regular points is an example of point information. The expiration date may indicate the end date of the period during which the regular points are valid.

[0227] The limited-time point DB 74b may store limited-time point information for each granted limited-time point among usable points held by the user. For example, the limited-time point DB 74b may store a user ID, the number of limited-time points, an expiration date, and the like, in association with one another, as limited-time point information. The user ID may indicate a user who holds the limited-time points corresponding to the limited-time point information. The number of limited-time points may indicate the number of those limited-time points. The number of limited-time points is an example of point information. The expiration date may indicate the end date of the period during which the limited-time points are valid.

[0228] The storage unit 74 may further store an expected point DB 74c. The expected point DB 74c may store expected point information. The expected point information may be information related to expected points. The expected points may indicate, for example, points that the user plans to acquire as future usable points. For example, when a user pays for a purchase through a point program service, points corresponding to the amount of the purchase may be awarded to the user. In this case, usable points may be awarded on a predetermined date rather than immediately usable points. During this period, the user cannot use the expected points. For example, the expected points may become usable points for the user who was awarded the expected points a predetermined number of days after the expected points were awarded or on a predetermined date. In other words, usable points may ultimately be awarded to the user. The expected point DB 74c may store, as expected point information, user IDs, point types, the number of expected points, expiration dates, expected acquisition dates, and the like, in association with one another. The user ID may indicate the user to whom the expected points were awarded. The point type may indicate whether the awarded expected points are regular points or limited-time points. The number of expected points to be earned may indicate the number of awarded expected points to be earned. The expiration date may be valid if the point type indicates limited-time points. The expiration date may indicate how long the limited-time points awarded as expected points are valid. The expected acquisition date may indicate the date on which the awarded expected points become usable points. Note that usable points may be awarded directly to the user instead of expected points to be earned. In this case, the expected acquisition point DB74c is not required.

[0229] The storage unit 74 also stores various programs such as an operating system, a DBMS, and a point management server program. The point management server program may be a program that causes the system control unit 71 to execute various processes related to the point program. The point management server program may be obtained from another device via the network NW, or may be recorded on a recording medium such as a magnetic tape, optical disk, or memory card and read via a drive device.

[0230] The communication unit 75 is configured by, for example, a network interface card, etc. The communication unit 75 connects to devices different from the point management server 7 via the network NW, and controls the communication state with the connected devices.

[0231] [6-3. System Control Unit Functional Overview] [6-3-1. Stamp card management server] Next, an overview of the functions of the system control unit 11 of the stamp card management server 1 will be described with reference to Figs. 46 and 47. Fig. 46 is a diagram showing an example of functional blocks of the system control unit 11 of the stamp card management server 1 according to this embodiment. In Fig. 46, the same elements as those in Fig. 29 are given the same reference numerals. As shown in Fig. 46, the system control unit 11 functions as an account registration screen information sending unit 1101 to a stamp card screen information sending unit 1111, and a payment information searching unit 1121, and may also function as a point giving unit 1141.

[0232] When a stamp is given by the stamp giving unit 1110, the point giving unit 1141 may give points to the user to whom the stamp is given. The user to whom the stamp is given is a user identified by user identification information included in the user information received by the stamp giving request receiving unit 1108. Alternatively, the user to whom the stamp is given may be a user identified by user identification information acquired by the usage application information searching unit 1109.

[0233] The point granting unit 1141 may grant points by sending a point granting request to the point management server 7. The point granting request may be information indicating a request for granting points. The point granting request may include a user ID and the number of granted points. The user ID may indicate the user to whom points will be granted. The number of granted points may indicate the number of points to be granted. The point granting request may further include a point type, an expiration date, and an expected acquisition date. The point type may indicate whether the points to be granted are regular points or limited-time points. The expiration date may be valid when the point type indicates limited-time points. The expiration date may indicate the end date of the period during which the granted limited-time points are valid. The expected acquisition date may indicate the date on which the points will be granted. If the point granting request does not include a expected acquisition date, the points may be granted immediately.

[0234] The point assigning unit 1141 may always assign a predetermined number of points for each stamp assignment. Alternatively, the point assigning unit 1141 may change the number of assigned points based on predetermined conditions. For example, the point assigning unit 1141 may assign points in a number corresponding to the number of stamps assigned by the stamp assigning unit 1110. The point assigning unit 1141 may assign more points as the number of stamps assigned increases.

[0235] The number of stamps given by the stamp giving unit 1110 may vary. For example, a store may be able to specify the number of stamps to give using a stamp giving tool. Also, for example, the number of stamps to be given may vary as described in the third to fifth embodiments.

[0236] Figures 47(a) and (b) are diagrams showing examples of the number of points awarded. For example, 10 times the number of stamps awarded may be awarded. Therefore, as shown in Figure 47(a), when one stamp is awarded, 10 points are awarded. Also, as shown in Figure 47(b), when two stamps are awarded, 20 points are awarded. Note that the number of points awarded may not be proportional to the number of stamps awarded, but may increase in stages, for example, as the number of stamps awarded increases.

[0237] [6-3-2. Point Management Server] Next, an overview of the functions of the system control unit 71 of the point management server 7 will be described with reference to Fig. 48. Fig. 48 is a diagram showing an example of functional blocks of the system control unit 71 of the point management server 7 according to this embodiment. The system control unit 71 may function as a point granting unit 7101, a point subtracting unit 7102, etc., as shown in Fig. 48, by the CPU 201a reading and executing various program codes included in the point management server program.

[0238] The point granting unit 7101 may grant points to a user in response to a request from a server device such as the stamp card management server 1. For example, the point granting unit 7101 may receive the above-mentioned point granting request from the stamp card management server 1 or the like. The point granting unit 7101 may grant points by adding the number of granted points included in the point granting request to point information stored in the storage unit 74 in association with the user ID included in the point granting request. Alternatively, the point granting unit 7101 may grant points by storing point information indicating the number of granted points included in the point granting request in association with the user ID included in the point granting request in the storage unit 74.

[0239] For example, if the point granting request includes a scheduled acquisition date, the point granting unit 7101 may generate scheduled acquisition point information using the user ID, point type, number of assigned points, expiration date, and scheduled acquisition date included in the point granting request. In this case, the number of assigned points is used as the number of scheduled acquisition points. The point granting unit 7101 may store the generated scheduled acquisition point information in the scheduled acquisition point DB 74c. The point granting unit 7101 may search the scheduled acquisition point DB 74c for scheduled acquisition point information including the scheduled acquisition date indicating today's date, for example, at a predetermined time every day. The point granting unit 7101 may acquire the user ID, point type, number of scheduled acquisition points, and expiration date from each retrieved scheduled acquisition point information. If the point type indicates regular points, the point granting unit 7101 may add the number of scheduled acquisition points to the number of regular points stored in the regular point DB 74a in association with the user ID that matches the acquired user ID. The point granting unit 7101 may also change the expiration date stored in the regular point DB 74a in association with that user ID to a date a predetermined period from today. If the point type indicates limited-time points, the point granting unit 7101 may generate limited-time point information including the acquired user ID, the number of expected points to be acquired, and the expiration date. In this case, the number of expected points to be acquired is used as the number of limited-time points. The point granting unit 7101 may store the generated limited-time point information in the limited-time point DB 74b. The point granting unit 7101 may delete the searched expected point information from the expected point acquisition DB 74c. If the point granting request does not include a scheduled acquisition date, the point granting unit 7101 may not generate expected point information. In this case, the point granting unit 7101 may add the number of assigned points to the number of regular points or store the limited-time point information in the expected point acquisition DB 74c, depending on the point type included in the point granting request.

[0240] When a user selects to use available points for payment, the point subtraction unit 7102 may subtract the number of used points from the number of available points associated with the user. For example, the point subtraction unit 7102 may receive a point subtraction request from the transaction server 30 or the service server 40. The point subtraction request information may include, for example, a user ID and the number of used points. The user ID may indicate the user who will use the points. The number of used points may indicate the number of points to be used. The point subtraction unit 7102 may, for example, prioritize subtracting limited-time points over regular points. For example, the point subtraction unit 7102 may search the limited-time point DB 74b for limited-time point information including a user ID that matches the user ID included in the point subtraction request. The point subtraction unit 7102 may subtract the number of used points from the number of limited-time points included in the limited-time point information. If the number of used points is equal to or greater than the number of limited-time points, the point subtraction unit 7102 may delete the limited-time point information from the limited-time point DB 74b. In this case, the point subtraction unit 7102 may calculate the difference between the number of used points and the number of limited-time points as the new number of used points. If there are multiple pieces of limited-time point information, the point subtraction unit 7102 may repeat these processes until the number of used points becomes 0. If there is still 1 or more used points even after all limited-time points are used up, the point subtraction unit 7102 may subtract the number of used points from the number of regular points stored in the regular point DB 74a in association with the user ID.

[0241] The following describes an example of processing by each server device when points are used. A transaction server 30 corresponding to a transaction service serving as a point program service may perform processing to confirm the transaction details for that transaction service. If the transaction object is a product, the transaction details may be the details of an order or purchase of the product. If the transaction object is a service, the transaction details may be the details of a purchase or reservation of the service. In a typical transaction service, a user preselects the transaction object to be purchased in the transaction service. The user then performs an operation to proceed with the transaction procedure. Before confirming the transaction details, the transaction server 30 may send screen information showing a transaction details screen to the user's user terminal 6. The transaction details screen may be a screen that displays the transaction details. The transaction details screen may also be a screen that accepts operations to change at least part of the transaction details. The transaction details may include the transaction object to be purchased, the unit price of the transaction object, the number of transaction objects purchased, the purchase amount of the transaction object, whether or not a special benefit is used, the special benefit to be used, the payment amount, the payment method, etc. The purchase amount is determined based on the unit price and number of transaction objects purchased. In the case of an online shopping mall, the transaction details may include the product to be purchased, the product price, the number of purchases, the purchase price, shipping costs, payment amount, payment method, product delivery destination, product delivery method, etc. The displayed transaction details may also include information regarding point usage. For example, the transaction details may include whether to use points, whether to use some or all points, and the number of points to be used. The user may be able to change the purchase quantity, point usage, payment method, etc. The transaction server 30 may display the current number of available points on the transaction details screen. The number of available points may indicate the total number of available points held by the user. The transaction server 30 may obtain the number of available points for the user from the point management server 7. For example, the transaction server 30 may send the user's user ID to the point management server 7. The point management server 7 may obtain the regular points stored in the regular point DB 74a in association with the user ID.The point management server 7 may also obtain the number of limited-time points associated with the user ID from the limited-time point DB 74b. The point management server 7 may calculate the total of the regular points and the limited-time points as the number of available points.

[0242] When the user confirms the transaction details on the transaction details screen, the transaction server 30 may confirm the transaction details. Here, the transaction server 30 may deduct the payment amount if points are used. For example, in the case of online shopping, the purchase amount is calculated by multiplying the product price by the number of items purchased. The total amount is the sum of the purchase amount and shipping costs. If there is no shipping cost, the purchase amount becomes the total amount. If the user does not use points, the total amount becomes the payment amount. If the user uses some of the points, the transaction server 30 may calculate the payment amount by subtracting an amount equivalent to the number of used points from the total amount. If the user uses all of the points, the transaction server 30 may calculate the payment amount by subtracting an amount equivalent to the number of available points from the total amount. If the amount equivalent to the number of available points is equal to or greater than the total amount, the payment amount will be 0 yen. In this case, the transaction server 30 may calculate the number of points equivalent to the total amount as the number of used points. The transaction server 30 may execute a process to subtract the number of used points from the number of available points of the user performing the transaction. For example, the transaction server 30 may realize the subtraction of the number of available points by sending point subtraction request information to the point management server 7. The point subtraction request information may include the user ID of the user performing the transaction and the number of points used.

[0243] If the final payment amount is 1 yen or more, the transaction server 30 may execute a settlement process for the user to pay the price indicated by the payment amount. At this time, the transaction server 30 may execute the settlement based on payment method information corresponding to the payment method selected by the user. Examples of payment methods include credit card payment, debit card payment, electronic money payment, and account transfer. The payment method information may indicate a method for paying the usage fee or purchase price. When credit card payment or debit card payment is used, the payment method information may include the credit card or debit card number, expiration date, cardholder name, security code, etc. When electronic money payment is used, the payment method information may include identification information for identifying the user in the electronic money system. When account transfer is used, the payment method information may include the bank name, branch name, account type, and account number. The transaction server 30 may execute the settlement process, for example, by communicating with a payment system (not shown) or the settlement server 10 corresponding to the payment method. For example, when the payment method is credit card payment, the payment system may be a payment system of a credit card company or a payment agent. If the payment method is debit card payment, the payment system may be a bank's online system or a payment system of a payment agent. If the payment method is account transfer, the payment system may be a bank's online system. If the payment method is electronic money, the payment system may be a system that manages electronic money. The specific payment processing for each method may be the same as known methods. The processing for using a benefit for payment and the payment processing may be performed simultaneously. Alternatively, when the transaction details are confirmed, the processing for using a benefit for payment may be performed, while the payment processing may be performed at a later date. For example, if the transaction object is a service that can be reserved, the payment processing may be performed on the day the service is used, a predetermined number of days before the use date, or a predetermined number of days after the use date.

[0244] The payment server 10 and the service server 40 corresponding to a non-transaction service serving as a point program service may execute a process for settling the usage fee or purchase amount incurred by a user using the non-transaction service. For example, each of the payment server 10 and the service server 40 may store a payment method database. The payment method database may store, for each user using the non-transaction service, information regarding the setting of a payment method for the usage fee or purchase amount incurred by the non-transaction service supported by the payment server 10 or the service server 40. For example, the payment method database may store a user ID, payment method information, point use selection information, and a maximum number of points to be used, all of which are associated with each other. The user ID may indicate the user who set the payment method. The point use selection information may indicate an option selected by the user regarding whether to use points for payment. Examples of options include not using points, using some points, and using all points. The maximum number of points to be used may indicate the maximum number of points to be used for payment when the user selects to use some points. The user can set the payment method for the non-transaction service through a screen provided by the payment server 10 or the service server 40. The user terminal 6 may transmit the payment method information, point use selection information, and maximum number of use points as the settings on this screen together with the user ID of the user to the payment server 10 or the service server 40. The server device that receives the information may store the information in the payment method DB.

[0245] The payment server 10 and the service server 40 may execute payment processing based on the information stored in the payment method DB. For example, if the non-transaction service is a payment service, the payment server 10 may obtain the payment amount from the payment information received from the user terminal 6 or the store payment terminal 20. If the non-transaction service is a periodic payment service for a usage fee, the service server 40 may obtain the billing amount associated with the combination of the target user and the period from a database (not shown) that stores the billing amount for the usage fee for each combination of user and period as the payment amount. The payment server 10 or the service server 40 may reduce the payment amount based on the point use selection information, the maximum number of usable points, and the number of usable points of the user paying the payment amount. The payment server 10 or the service server 40 may obtain the number of usable points using a method similar to that executed by the transaction server 30. If the user does not use points, the payment server 10 or the service server 40 may determine the obtained payment amount as the final payment amount. When a user uses only a portion of their points, the payment server 10 or the service server 40 may use the smaller of the maximum number of points used or the number of available points as the number of used points. The payment server 10 or the service server 40 may calculate the final payment amount by subtracting the amount equivalent to the number of used points from the acquired payment amount. When a user uses all of their points, the payment server 10 or the service server 40 may calculate the final payment amount by subtracting the amount equivalent to the number of available points from the acquired payment amount. If the final payment amount is 0 yen, the payment server 10 or the service server 40 may calculate the number of points equivalent to the acquired payment amount as the number of used points. The payment server 10 or the service server 40 may execute a process to subtract the number of used points from the number of available points of the target user in a manner similar to that executed by the transaction server 30. If the final payment amount is 1 yen or more, the payment server 10 or the service server 40 may execute a payment process for the user to pay the amount indicated by the payment amount based on the user's payment method information.This process may be the same as the settlement process executed by the transaction server 30.

[0246] [6-4. Operation of communication systems] Next, the operation of the communication system S will be described with reference to Fig. 49 and Fig. 50. Fig. 49 is a flowchart showing an example of stamp control processing executed by the system control unit 11 of the stamp card management server 1 according to this embodiment. In Fig. 49, the same processes as those in Fig. 35 are denoted by the same reference numerals.

[0247] 49, steps S601 to S604 are executed first, and then steps S621 to S623 are executed. As a result of the determination in step S623, a stamp granting process is executed (step S605). When the stamp granting process ends, the system control unit 11 executes a point granting process (step S631), and the stamp control process ends.

[0248] Fig. 50 is a flowchart showing an example of the point granting process executed by the system control unit 11 of the stamp card management server 1 according to this embodiment. As shown in Fig. 50, the point granting unit 1141 calculates the number of points to be granted by multiplying the number of stamps to be granted finally determined in the stamp granting process by a predetermined value (step S901). The predetermined value is a real number equal to or greater than 1. Next, the point granting unit 1141 sends a point granting request including the user ID and the number of points to be granted acquired from the point granting request to the point management server 7 (step S902), and the point granting process ends.

[0249] As described above, according to this embodiment, when a stamp is awarded to a user, the user is also awarded points in addition to the stamp, which can further encourage the use of the stamp card.

[0250] Here, the stamp card management server 1 may award points that can be used for both transaction services and non-transaction services, which can encourage the use of both transaction services and non-transaction services.

[0251] The stamp card management server 1 may also change the number of stamps to be awarded. The stamp card management server 1 may also award points in accordance with the number of stamps awarded. In this case, points in accordance with the number of stamps awarded can be awarded.

[0252] [7. Seventh Embodiment] Next, a seventh embodiment will be described. Except for the points described below, the seventh embodiment may be the same as the sixth embodiment. In this embodiment, the number of points awarded to a user varies depending on the amount the user pays to a store through settlement. In this respect, the configuration and functions of the communication system S according to the seventh embodiment may be similar to those of the fourth embodiment, except for the point management server 7.

[0253] [7-1. Functional overview of the system control unit of the stamp card management server] First, the outline of the functions of the system control unit 11 of the stamp card management server 1 will be explained with reference to FIG.

[0254] As described above, the payment information search unit 1121 may acquire or search for payment information indicating that a payment has been made to pay the promotion target from a user identified by the user identification information included in the stamp granting request received by the stamp granting request receiving unit 1108, and including the payment amount.

[0255] The point assigning unit 1141 may change the number of points to be assigned depending on the payment amount included in the payment information acquired or searched by the payment information searching unit 1121. For example, the point assigning unit 1141 may assign more points the larger the payment amount. For example, the memory unit 14 may store a table indicating the correspondence between the payment amount and the number of added points. The number of added points may indicate the number of points to be added to the number of assigned points. The point assigning unit 1141 may determine the number of added points based on this table and the payment amount.

[0256] FIG. 51 is a diagram showing an example of the number of points awarded. As shown in FIG. 51, if the payment amount is less than 1,000 yen, points may be awarded in a number corresponding to the number of awarded stamps designated by the store using the point awarding tool. If the payment amount is 1,000 yen or more but less than 3,000 yen, points may be awarded in a number 10 points more than the number of points corresponding to the number of awarded stamps designated by the store. If the payment amount is 3,000 yen or more, points may be awarded in a number 30 points more than the number of points corresponding to the number of awarded stamps designated by the store. In the example shown in FIG. 51, the number of points awarded is set to three levels. However, the number of points awarded may also be set to two levels, or four or more levels.

[0257] [7-2. Operation of communication system] Next, the operation of the communication system S will be described with reference to Fig. 52. Fig. 52 is a flowchart showing an example of a point granting process executed by the system control unit 11 of the stamp card management server 1 according to this embodiment. In Fig. 52, the same processes as those in Fig. 50 are denoted by the same reference numerals.

[0258] As shown in FIG. 50, the point granting unit 1141 calculates the number of points to be granted by multiplying the number of stamps to be granted finally determined in the stamp granting process by a predetermined value (step S901). Next, the point granting unit 1141 acquires the payment amount from the payment information searched, for example, in step S622 of the point control process shown in FIG. 33 (step S921). Next, the point granting unit 1141 acquires the number of points to be added corresponding to the acquired payment amount (step S922). Next, the point granting unit 1141 adds the acquired number of points to be added to the calculated number of points to calculate the final number of points to be granted (step S923). Next, the point granting unit 1141 sends a point granting request including the user ID and the number of points to be granted acquired from the point granting request to the point management server 7 (step S902), and the point granting process ends.

[0259] As described above, according to this embodiment, the number of points awarded to a user can be changed depending on the amount of payment made by the user.

[0260] [8. Eighth Embodiment] Next, an eighth embodiment will be described. Except for the following points, the eighth embodiment may be the same as at least one of the sixth and seventh embodiments. In this embodiment, the number of points awarded to a user varies based on the user's actions regarding a specific service other than the stamp card service. In this respect, the configuration and functions of the communication system S according to the eighth embodiment may be similar to those of the fifth embodiment, except for the point management server 7.

[0261] [8-1. Functional overview of the system control unit of the stamp card management server] First, a functional overview of the system control unit 11 of the stamp card management server 1 will be described with reference to Figs. 53 and 54. Fig. 53 is a diagram showing an example of functional blocks of the system control unit 11 of the stamp card management server 1 according to this embodiment. In Fig. 53, the same elements as those in Fig. 40 or 46 are assigned the same reference numerals. As shown in Fig. 53, the system control unit 11 functions as an account registration screen information sending unit 1101 to a stamp card screen information sending unit 1111 and a payment information searching unit 1121, and may also function as a transaction service action history information acquiring unit 1131, a non-transaction service action history information acquiring unit 1132, and a point granting unit 1141.

[0262] As in the fifth embodiment, the transaction service action history information acquisition unit 1131 may acquire transaction service action history information indicating the history of actions by a user identified by user identification information included in the user information received by the stamp assignment request receiving unit 1108.

[0263] As in the fifth embodiment, non-transaction service behavior history information may be obtained that indicates the history of behavior by a user identified by user identification information included in the user information received by the stamp grant request receiving unit 1108.

[0264] The point allocating unit 1141 may change the number of points to be allocated based on at least one of the behavior history indicated by the transaction service behavior history information acquired by the transaction service behavior history information acquisition unit 1131 and the behavior history indicated by the non-transaction service behavior history information acquisition unit 1132.

[0265] When using the transaction service behavior history information, the point assigning unit 1141 may change the number of points to be assigned based on the content of the transaction. For example, the point assigning unit 1141 may assign more points to a user when the content of a transaction indicated by the transaction service behavior history information satisfies predetermined transaction content conditions than when the content of the transaction does not satisfy the predetermined transaction content conditions. Examples of transaction content conditions are described in the fifth embodiment.

[0266] When using the non-transaction service behavior history information, the point assigning unit 1141 may change the number of stamps to be assigned depending on the content of the user's behavior in the non-transaction service. For example, the stamp assigning unit 1110 may assign more stamps to a user when the content of the behavior indicated by the non-transaction service behavior history information satisfies a predetermined behavior content condition than when the content of the behavior does not satisfy the predetermined behavior content condition. Examples of the behavior content condition are described in the fifth embodiment.

[0267] The point allocating unit 1141 may change the number of points to be allocated based on both the behavior history indicated by the transaction service behavior history information and the behavior history indicated by the non-transaction service behavior history information. For example, if the behavior history regarding transaction services and the behavior history regarding non-transaction services satisfy a predetermined condition, the point allocating unit 1141 may allocate more points than if the condition is not satisfied. Examples of the predetermined condition are described in the fifth embodiment.

[0268] FIG. 54 is a diagram showing an example of the number of points awarded. For example, suppose the transaction content condition is that the transaction amount in the previous month in the transaction service is 3,000 yen or more. Furthermore, suppose the behavior content condition is that the user is currently subscribed to a non-transaction service. In this case, if the user purchased a transaction object in the transaction service for 3,000 yen or more in the previous month and is subscribed to the non-transaction service, points corresponding to the number of awarded stamps designated by the store using the point awarding tool and a predetermined additional point number may be awarded. If the user did not purchase anything in the transaction service in the previous month or purchased a transaction object for less than 3,000 yen, points corresponding to the number of awarded stamps designated by the store may be awarded. Furthermore, if the user is not subscribed to the non-transaction service, points corresponding to the number of awarded stamps designated by the store may be awarded.

[0269] [8-2. Operation of communication system] Next, the operation of the communication system S will be described with reference to Fig. 55. Fig. 55 is a flowchart showing an example of a point granting process executed by the system control unit 11 of the stamp card management server 1 according to this embodiment. In Fig. 55, the same processes as those in Fig. 50 are denoted by the same reference numerals.

[0270] As shown in FIG. 55, the point granting unit 1141 calculates the number of points to be granted by multiplying the number of stamps to be granted finally determined in the stamp granting process by a predetermined value (step S901). Next, the transaction service action history information acquisition unit 1131 searches the stamp action history DB 14g for a purchase log that includes the user ID and the service ID of the transaction service acquired from the point granting request and that includes a transaction date and time within a predetermined period (step S941). Next, the point granting unit 1141 calculates the total transaction amount (step S942). Next, the point granting unit 1141 determines whether the total transaction amount is equal to or greater than a predetermined threshold amount (step S943).

[0271] If the total transaction amount is equal to or greater than the threshold amount (step S943: YES), the non-transaction service action history information acquisition unit 1132 searches the stamp action history DB 14g for a purchase log including the user ID and the service ID of the non-transaction service acquired from the point grant request (step S944). Next, the point granting unit 1141 determines whether the user has a contract for the non-transaction service based on the searched purchase log (step S945).

[0272] If the user has a contract for a non-transaction service (step S945: YES), the point giving unit 1141 adds a predetermined number of additional points to the calculated number of given points, and updates the number of given points (step S946).

[0273] If the total transaction amount is less than the threshold amount (step S943: NO), or if the user has not subscribed to the non-transaction service (step S945: NO), the process proceeds to step S902. After step S946, the process also proceeds to step S902. In step S902, the point granting unit 1141 sends a point granting request including the user ID and the number of points to be granted acquired from the point granting request to the point management server 7, and the point granting process ends.

[0274] As described above, according to this embodiment, the number of points awarded to a user can be changed depending on the actions the user takes in transaction services and non-transaction services.

[0275] Here, if the content of the transaction satisfies predetermined transaction content conditions and the user also satisfies the condition of having a contract for a non-transaction service, the stamp card management server 1 may award more points than if the conditions were not met. In this case, it is possible to encourage the use of both transaction services and non-transaction services.

[0276] 9. Ninth Embodiment Next, a ninth embodiment will be described. Except for the following points, the ninth embodiment may be the same as at least one of the embodiments described so far. In this embodiment, the stamp card management server 1 transmits a printable code to the store terminal 5 as a code indicating information about the promotion target for granting a stamp.

[0277] [9-1. Functional overview of the communication system] First, a functional overview of the communication system S according to this embodiment will be described with reference to FIG. 56. FIG. 56 is a diagram illustrating an example of the processing flow up to the granting of a stamp. After a store employee logs in to the stamp giving tool, as shown in FIG. 56, the store terminal 5 receives print data for one or more codes from the stamp card management server 1 (step S41). Each code may be a so-called one-time code. That is, each code can be used once. Using a code may involve granting a stamp based on information obtained from the code. The print data is data used to print the code. Examples of print data formats include PDF, PSD, and AI. Alternatively, the print data may be image data. The store employee transfers the print data from the store terminal 5 to another terminal device. The employee prints each code on a printed material using a printer connected to the terminal device (step S42). Alternatively, the employee may print each code using a printer connected to the store terminal 5. The user receives a printed material of one of the codes from the store. The user terminal 6 reads the code printed on the printed matter (step S43). Based on the information obtained from the read code, the user terminal 6 sends a stamp granting request to the stamp card management server 1 (step S44). On receiving the stamp granting request, the stamp card management server 1 grants a stamp to the stamp card of the user, on the condition that the user of the user terminal 6 that sent the stamp granting request has entered the campaign for the stamp card in question and that the code read by the user terminal 6 is unused (step S45).

[0278] In this embodiment, the stamp card management server 1 may grant stamps without using payment information, as in the first embodiment. Alternatively, the stamp card management server 1 may grant stamps to a user based on payment information, on the condition that the user makes a payment at a store, as in the second embodiment, etc. Furthermore, the stamp card management server 1 may change the number of stamps to be granted depending on whether the user has made a payment, as in the third embodiment.

[0279] [9-2. Configuration of the point management server] Next, the configuration of the stamp card management server 1 will be described with reference to Fig. 57 and Fig. 58. Fig. 57 is a block diagram showing an example of the schematic configuration of the stamp card management server 1 according to this embodiment. In Fig. 57, the same elements as in Fig. 4 are given the same reference numerals. As shown in Fig. 57, the memory unit 14 of the stamp card management server 1 may store a code DB 14i in addition to the stamp card DB 14a to the benefit DB 14e. Other aspects may be the same as those of the first embodiment.

[0280] Fig. 58 is a diagram showing an example of the contents stored in the database of the stamp card management server 1. The code DB 14i may store code information about each code that the stamp card management server 1 has sent to the store terminal 5 as a code indicating information about a promotion target. For example, as shown in Fig. 58, the code DB 14i may store, as code information, a code ID, a card URL, a user ID, the number of cards, the date and time of awarding, the number of awarding stamps, and the like, in association with one another. The code ID may be identification information for identifying a code.

[0281] [9-3. Functional overview of the system control unit] [9-3-1. Stamp card management server] Next, the functions of the system control unit 11 of the stamp card management server 1 will be outlined.

[0282] The code sending unit 1107 may send printing data for the code when sending the code indicating the information on the promotion target to the store terminal 5. The code sending unit 1107 may generate printing data that can print the card name, store name, number of awarded stamps, etc. together with the code.

[0283] The code request sent from the store terminal 5 to the stamp card management server 1 may include the number of issues in addition to the card URL, store name, and number of stamps awarded. The number of issues may indicate the number of print data for the code sent to the store terminal 5.

[0284] The information about the promotion target indicated by the code may include at least the card URL. The information about the promotion target may further include at least one of the store name and the number of stamps awarded. The code sending unit 1107 may generate a number of codes corresponding to the number of issues. When generating each code, the code sending unit 1107 may generate a code ID unique to that code. The code sending unit 1107 may generate codes by encoding, for example, the code ID, card URL, store name, and the number of stamps awarded. The code sending unit 1107 may generate print data for the generated codes.

[0285] When the code is generated, the code transmitting unit 1107 may store code information about the generated code in the code DB 14i. The code information may include at least a code ID.

[0286] The stamp granting unit 1110 executes a process of granting a stamp based on the promotion target information and user information included in the stamp granting request received from the user terminal 6 by the stamp granting request receiving unit 1108. As described above, the promotion target information at this time may include, for example, a code ID, a card URL, a store name, and the number of stamps to be granted. The stamp granting unit 1110 may search the code DB 14i for code information including a code ID that matches the code ID included in the promotion target information. If no matching code information is found, the stamp granting unit 1110 may not grant a stamp.

[0287] The stamp assigning unit 1110 may assign a stamp when the corresponding code information is found and the corresponding entry information is found by a search by the usage application information searching unit 1109. When the stamp assigning unit 1110 assigns a stamp, it may delete the corresponding code information from the code DB 14i.

[0288] [9-3-2. Store terminal] Next, a functional overview of the system control unit 51 of the store terminal 5 will be described with reference to FIG. 59 . As described above, the login screen display control unit 5101 displays the login screen 200 of the stamp presentation tool on the display unit 57. The login screen 200 is a screen that accepts an operation to select a method for providing a stamp from a plurality of methods, including at least a first method and a second method. The first method is a method in which the store terminal 5 outputs a code indicating information on the promotion target. In the embodiments described so far, outputting a code means displaying the code. In this embodiment, outputting a code may mean outputting print data of the code to a recording medium, another terminal device, or a printer. When print data is output to a recording medium, the print data may be output to another terminal device or printer via the recording medium. Another terminal device that has acquired the print data may output the print data to a printer connected to that terminal device. The printer may print the code based on the print data.

[0289] Fig. 59(a) is a diagram showing an example of a login screen. In Fig. 59(a), the same elements as in Fig. 13 are assigned the same reference numerals. As shown in Fig. 59(a), the login screen 200 may include a card URL input field 201, a password input field 202, a code download button 205, and a code read button 204. The code download button 205 may be an element that can be operated to select a first method for the store terminal 5 to output print data as a method for applying a stamp.

[0290] FIG. 59(b) is a diagram showing an example of a downloadable stamp number selection screen. In FIG. 59(b), the same elements as those in FIG. 14(a) are denoted by the same reference numerals. The downloadable stamp number selection screen is displayed on the display unit 57 when the user successfully completes login authentication by operating the code download button 205 on the login screen 200. As shown in FIG. 59(b), the downloadable stamp number selection screen 250 may include a logout button 211, a card name 212, a store name 213, a number-of-stamps selection list 214, an issue number input field 251, and a download button 252. The issue number input field 251 may be an input area for inputting the number of stamps to be issued. The download button 252 may be an element operable to receive print data for the code. When the employee operates the download button 252, the code receiving unit 5105 may transmit a code request. This code request may include the input number of stamps to be issued. The code receiving unit 5105 may receive print data of the code sent from the stamp card management server 1 in response to sending the code request.

[0291] [9-4. Operation of communication systems] Next, the operation of the communication system S will be described with reference to FIGS. 60 and 61. FIG. 60 is a sequence diagram showing an example of the operation of the communication system S when the store terminal 5 receives code printing data and grants stamps. For example, the store terminal 5 displays the downloadable number of stamps to be granted selection screen 250. As shown in FIG. 60, a store employee selects the number of stamps to be granted and the number to be issued on this screen and operates the download button 252 (step S441). Upon detecting this operation, the code receiving unit 5105 transmits a code request to the stamp card management server 1, the code request including the card URL and store name included in the login status information stored in the memory unit 54, and the selected number of stamps to be granted and the number to be issued (step S442). The code sending unit 1107 of the stamp card management server 1 that received the code request generates printing data for codes indicating information about stores that are promotion targets, for the number of stamps to be issued (step S443). For example, the code sending unit 1107 may generate plain text by concatenating the card URL, store name, number of stamps to be granted, and unique code ID included in the code request. The code sending unit 1107 may generate printing data for the code by encoding this plain text. Next, the code sending unit 1107 stores code information for each piece of generated printing data in the code DB 14i (step S444). Next, the code sending unit 1107 sends each piece of printing data to the store terminal 5 (step S445). The store staff prints the code based on the printing data received by the store terminal 5 (step S446). The staff hands the printed copy of the code to the user.

[0292] Meanwhile, the user terminal 6 of the user who received the printed material displays the user terminal code reading screen 310 based on the user's operation (step S447). Next, the user terminal 6 photographs the code printed on the printed material (step S448). Next, the user terminal 6 decodes the code based on the image data of the photographed code to obtain the card URL, store name, number of awarded stamps, and code ID (step S449). Next, the user terminal 6 sends a stamp granting request including the card URL, store name, number of awarded stamps, and code ID, as well as the user ID of the user using the user terminal 6, to the stamp card management server 1 (step S450). Upon receiving the stamp granting request, the stamp card management server 1 executes stamp control processing (step S451).

[0293] Fig. 61 is a flowchart showing an example of stamp control processing executed by the system control unit 11 when the stamp card management server 1 receives a stamp granting request from the user terminal 6. In Fig. 61, the same processes as those in Fig. 21 are denoted by the same reference numerals.

[0294] 61, the stamp applying unit 1110 searches the code DB 14i for code information including a code ID that matches the code ID included in the stamp applying request (step S641). As a result of the search, the stamp applying unit 1110 determines whether or not there is corresponding code information (step S642). If there is no corresponding code information (step S641: NO), the stamp control process ends. If there is corresponding code information (step S641: YES), steps S601 to S605 are executed. After executing the stamp applying process in step S605, the stamp applying unit 1110 deletes the searched code information from the code DB 14i (step S643), and the stamp control process ends.

[0295] As described above, according to this embodiment, a stamp can be applied based on a printed code.

[0296] [10. Tenth Embodiment] Next, a tenth embodiment will be described. Except for the points described below, the tenth embodiment may be the same as at least one of the embodiments described so far. In this embodiment, the stamp card management server 1 may grant a stamp to a user based on payment information, on the condition that the user makes a payment at a store, as in the second embodiment, etc. On the other hand, in this embodiment, a stamp presentation tool is not used.

[0297] [10-1. Communication System Configuration] First, the configuration of the communication system S according to this embodiment will be described with reference to Figs. 62 and 63. Fig. 62 is a diagram showing an example of the schematic configuration of the communication system S according to this embodiment. In Fig. 62, the same elements as those in Fig. 23 are assigned the same reference numerals. As shown in Fig. 63, the communication system S may be configured to include a stamp card management server 1, a member information management server 2, an operator terminal 3, multiple promotion host terminals 4, multiple user terminals 6, one or multiple payment servers 10, and multiple store payment terminals 20. These devices may be connected to a network NW.

[0298] FIG. 63 is a diagram showing an example of the processing flow up to the granting of a stamp. In FIG. 63, the same processes as those in FIG. 24 are assigned the same reference numerals. As shown in FIG. 63, the user makes a payment at the store (step S21), and the store payment terminal 20 or the user terminal 6 transmits payment information to the payment server 10 (step S23). The payment server 10 executes payment processing based on the payment information (step S23) and transmits the payment information to the member information management server 2 (step S24). The member information management server 2 transmits the payment information to the stamp card management server 1 at a predetermined timing (step S25). The stamp card management server 1 searches for payment information including user identification information of a user who has entered a stamp card campaign at a predetermined timing (step S31). For example, the stamp card management server 1 may perform the search periodically. As a result of the search, the stamp card management server 1 grants a stamp to the stamp card of the user, provided that the user who has entered the stamp card campaign has made payment to the store (step S32).

[0299] In the following description, a stamp is assigned when a user pays for a transaction offline. However, the stamp management server 1 may be configured to assign a stamp when a user pays for a transaction online. For example, as described in the fifth embodiment, a behavior log showing the transaction details in a transaction service may correspond to payment information. The stamp management server 1 may execute a process for assigning a stamp based on this behavior log.

[0300] [10-2. Configuration of the stamp card management server] Next, the configuration of the stamp card management server 1 will be described with reference to Fig. 64 and Fig. 65. Fig. 64 is a block diagram showing an example of the schematic configuration of the stamp card management server 1 according to this embodiment. In Fig. 64, the same elements as in Fig. 28 are given the same reference numerals. As shown in Fig. 64, the memory unit 14 of the stamp card management server 1 may store a promotion target store DB14j in addition to a stamp card DB14a, an entry DB14c, a stamp history DB14d, a benefit DB14e, a store DB14f, and a stamp action history DB14g.

[0301] FIG. 65 is a diagram showing an example of the contents stored in the promotion target store DB 14j of the stamp card management server 1. For each of a plurality of stamp cards registered in the stamp card service, the promotion target store DB 14j may store stamp card identification information for identifying the stamp card and donor identification information for identifying the donor corresponding to the stamp card among the transaction target donors, in association with each other. For example, as shown in FIG. 65, the promotion target store DB 14j may store, for each stamp card, target store information regarding stores that are the target of a promotion using the stamp card. For example, as shown in FIG. 65, the promotion target store DB 14j may store, in association with each other, a card URL and one or more pieces of target store information. The target store information may be information regarding a store that is the target of a promotion using the stamp card indicated by the card URL. Each piece of target store information may include, for example, a business ID and a store ID. The business ID may indicate the business of the target store. The store ID may indicate the target store. The business ID and the store ID are examples of donor identification information. Note that, when a donor who conducts online transactions is the target of the promotion, the target store information may include a transaction target donor ID for identifying the donor.

[0302] In this embodiment, the stamp card management server 1 does not need to transmit screen information of the account registration screen 100. The stamp card management server 1 may transmit, for example, screen information of the stamp card registration screen to the operator terminal 3 or the promotion main terminal 4. The stamp card registration screen may be a screen for registering a stamp card and also a screen for accepting the selection of stores that are eligible for the promotion. The account registration screen may accept input of a card URL, a card name, a campaign period, benefit setting information, and stamp presentation limit information. The account registration screen may also accept the selection of a business operator of a store that is eligible for the promotion and the selection of promotion targets from among the stores of the selected business operator. The operator terminal 3 or the promotion main terminal 4 may transmit the input information to the stamp card management server 1 as stamp card information and may also transmit target store information of each store selected as a target for the promotion to the stamp card management server 1. The stamp card management server 1 may store the received stamp card information in the stamp card DB 14a. The stamp card management server 1 may also store the received target store information in the promotion target store DB 14j in association with a card URL.

[0303] [10-3. Functional overview of the system control unit of the stamp card management server] Next, an overview of the functions of the system control unit 11 of the stamp card management server 1 will be described with reference to Fig. 66. Fig. 66 is a diagram showing an example of functional blocks of the system control unit 11 of the stamp card management server 1 according to this embodiment. In Fig. 66, the same elements as those in Fig. 29 are given the same reference numerals. As shown in Fig. 66, the system control unit 11 may function as a usage application information search unit 1109, a stamp granting unit 1110, a stamp card screen information transmission unit 1111, a payment information search unit 1121, and a provider identification information acquisition unit 1151.

[0304] The usage application information search unit 1109 may acquire any of the user identification information from the entry DB 14c. For example, the usage application information search unit 1109 may acquire each of the user identification information stored in the entry DB 14c. In this case, the usage application information search unit 1109 may periodically acquire the information. Examples of the interval between acquisitions of the user identification information include one hour, six hours, and one day. The usage application information search unit 1109 may acquire at least the user identification information and the stamp card identification information from the information included in any of the entry information from the entry DB 14c. For example, the usage application information search unit 1109 may periodically acquire each of the entry information stored in the entry DB 14c.

[0305] When the entry information is acquired by the application information search unit 1109, the provider identification information acquisition unit 1151 may acquire, from the promotion target store DB 14j, provider identification information associated with the stamp card identification information included in the entry information. For example, the provider identification information acquisition unit 1151 may acquire each target store information associated with the card URL as the stamp card identification information.

[0306] The payment information search unit 1121 may search the stamp behavior history DB 14g for payment information including payment source identification information for identifying a user identified by the user identification information acquired by the use application information search unit 1109 as a payment source. For example, the payment information search unit 1121 may search for payment information for each piece of user identification information acquired by the use application information search unit 1109. For example, the payment information search unit 1121 may search for payment information including a user ID that matches the user ID acquired by the use application information search unit 1109. Here, the payment information search unit 1121 may search for payment information including payment source identification information for identifying a user identified by the user identification information acquired by the use application information search unit 1109 as a payment source, and payment recipient identification information for identifying a provider identified by the provider identification information acquired by the provider identification information acquisition unit 1151 as a payment recipient. For example, the payment information search unit 1121 may search for payment information that includes a user ID that matches the user ID acquired by the usage application information search unit 1109 and a business ID and store ID included in the target store information acquired by the provider identification information acquisition unit 1151.

[0307] The stamp granting unit 1110 may grant a stamp to the user identified by the user identification information acquired by the usage application information search unit 1109, on the condition that the payment information search unit 1121 finds corresponding payment information through the payment. If the stamp granting unit 1110 does not find corresponding payment information, the stamp granting unit 1110 may not grant a stamp. For example, the stamp granting unit 1110 may grant a stamp by increasing the current stamp count stored in the entry DB 14c in association with the user ID acquired by the usage application information search unit 1109. In this case, the stamp granting unit 1110 may acquire a card URL stored in the promotion target store DB 14j in association with provider identification information for identifying the provider identified by the payee identification information included in the payment information searched by the payment information search unit 1121, from among the card URLs stored in the entry DB 14c in association with the user ID acquired by the usage application information search unit 1109. The stamp granting unit 1110 may grant a stamp by increasing the current number of stamps stored in the entry DB 14c in association with the combination of the acquired card URL and the user ID acquired by the usage application information search unit 1109. In this embodiment, multiple stamp cards do not need to be registered in the stamp card service. The stamp card service may be a service that allows only one stamp card to be used. In this case, each user may only be able to apply for use of that single stamp card. In this case, each entry information does not need to include the card URL. The entry DB 14c may store entry information for each user who has applied for use of a stamp card. When granting a stamp, the stamp granting unit 1110 may increase the current number of stamps stored in the entry DB 14c in association with the user ID acquired by the usage application information search unit 1109.

[0308] [10-4. Operation of communication systems] Next, the operation of the communication system S will be described with reference to Fig. 67 and Fig. 68. Fig. 67 is a flowchart showing an example of stamp control processing executed by the system control unit 11 of the stamp card management server 1 according to this embodiment. The system control unit 11 may execute the stamp control processing, for example, periodically.

[0309] As shown in FIG. 67, the usage application information search unit 1109 acquires a user ID from each entry information stored in the entry DB 14c and generates a list of user IDs (step S1001). At this time, the usage application information search unit 1109 generates the list so as not to include duplicate user IDs. Next, the usage application information search unit 1109 acquires one user ID from the generated list (step S1002). Next, the usage application information search unit 1109 searches the entry DB 14c for all entry information including the user ID acquired in step S1002, and acquires a card URL from each searched entry information (step S1003). Next, the provider identification information acquisition unit 1151 acquires all target store information associated with each card URL from the promotion target store DB 14j (step S1104). Next, for each piece of acquired target store information, the payment information search unit 1121 searches the stamp behavior history DB 14g for payment information including a combination of that target store information and the user ID acquired in step S1002 (step S1005). As a result of the search, the payment information search unit 1121 determines whether there is at least one piece of matching search information (step S1006). If there is no matching payment information (step S1006: NO), the process proceeds to step S1012.

[0310] If there is corresponding payment information (step S1006: YES), the stamp granting unit 1110 selects one of the searched payment information (step S1007). Next, the stamp granting unit 1110 acquires, from the card URLs acquired in step S1003, a card URL associated with the target store information used to search for the selected search information. The stamp granting unit 1110 determines whether the payment date and time included in the selected payment information is within the campaign period associated with the acquired card URL and stored in the stamp card DB 14a (step S1008). If the payment date and time is outside the campaign period (step S1008: NO), the process proceeds to step S1011. If the payment date and time is within the campaign period (step S1008: YES), the stamp granting unit 1110 determines whether the stamp granting limit has been reached for the user to whom the stamp is to be granted, based on the stamp grant limit information associated with the acquired card URL (step S1009). If the number of stamps given up to that point has already reached the stamp giving limit (step S1009: YES), the process proceeds to step S1011. If the number of stamps given up to that point has not reached the stamp giving limit (step S1009: NO), the stamp giving unit 1110 executes stamp giving processing based on the acquired user ID and the card URL acquired in step S1008 (step S1010), and the process proceeds to step S1011. This stamp processing may be the same as the stamp processing shown in FIG. 22. However, in this embodiment, software for allowing the store to select the number of awarded stamps is not used. Therefore, in step S701 of the stamp processing, a predetermined number of stamps may be added to the current number of stamps. For example, 1 may be added to the current number of stamps.

[0311] In step S1011, the stamp giving unit 1110 determines whether all of the searched payment information has been selected. If there is payment information that has not yet been selected (step S1011: NO), the process proceeds to step S1007. In step S1007, the stamp giving unit 1110 selects one of the payment information that has not yet been selected. If all of the payment information has been selected (step S1011: YES), the process proceeds to step S1012. In step S1012, the usage application information search unit 1109 determines whether all user IDs have been acquired from the list. If there is a user ID that has not yet been acquired (step S1012: NO), the process proceeds to step S1002. In step S1002, the application information search unit 1109 selects one of the user IDs that have not yet been acquired. If all user IDs have been acquired (step S1012: YES), the stamp control process ends.

[0312] The stamp card management server 1 may change the number of stamps to be awarded, as in the fourth and fifth embodiments. Furthermore, the stamp card management server 1 may also award points when awarding stamps, as in the sixth embodiment. Furthermore, the stamp card management server 1 may change the number of points to be awarded, as in the seventh and eighth embodiments.

[0313] As described above, according to this embodiment, when a stamp is awarded on the condition that the user has paid the fee, there is no need to execute processing related to the awarding of stamps for payment information indicating that a user who did not apply for use of a stamp card has made a payment to pay the fee. This eliminates the need to execute processing each time a payment occurs, so that when a stamp is awarded based on information related to the payment, the processing related to the awarding of stamps can be executed more efficiently.

[0314] Here, the stamp card management server 1 may acquire any entry information from the entry DB 14c. Alternatively, the stamp card management server 1 may acquire donor identification information associated with the stamp card identification information included in the acquired entry information from the promotion target store DB 14j. Alternatively, the stamp card management server 1 may search for payment information including payment source identification information for identifying the user identified by the user identification information included in the acquired entry information as the payment source, and payment destination identification information for identifying the acquired donor identification information as the payment destination. In this case, a stamp can be awarded on the condition that the user has paid the amount to be paid to the donor corresponding to the stamp card that they have applied to use.

[0315] Alternatively, the stamp card management server 1 may acquire each user identification information stored in the entry DB 14c. Alternatively, the stamp card management server 1 may search for payment information for each acquired user identification information. In this case, it is possible to execute a process for granting stamps to each user who has applied to use a stamp card.

[0316] [11. Eleventh Embodiment] Next, an eleventh embodiment will be described. Except for the points described below, the eleventh embodiment may be the same as the tenth embodiment. In this embodiment, the stamp card management server 1 receives a stamp granting request from the store payment terminal 20 or the user terminal 6. Based on the stamp granting request, the stamp card management server 1 searches for payment information and grants a stamp.

[0317] FIG. 68 is a diagram showing an example of the process flow up to the stamp granting. In FIG. 68, the same processes as those in FIG. 63 are assigned the same reference numerals. As shown in FIG. 68, steps S21, S22, S24, and S25 are executed. The store payment terminal 20 transmits a stamp granting request to the stamp card management server 1 simultaneously with or after transmitting the payment information (step S41). For example, a program for transmitting a stamp granting request may be installed in the store payment terminal 20 of a promotional store. This allows stamp granting requests to be transmitted only from the promotional store among stores of businesses affiliated with a payment service. The store payment terminal 20 may transmit the stamp granting request automatically, or may transmit the stamp granting request based on the operation of a store employee. When the user terminal 6 transmits the payment information, the user terminal 6 may transmit the stamp granting request. For example, the user terminal 6 may transmit the stamp granting request in accordance with a code payment application or a stamp card app. The user terminal 6 may transmit the stamp granting request automatically, or may transmit the stamp granting request based on the user's operation. The stamp granting request may include user identification information for identifying the user to whom the stamp is to be granted. The user identification information included in the stamp granting request sent by the store payment terminal 20 may be payment means user identification information for identifying the user in the payment service that provides the payment means used by the user for payment. The user identification information included in the stamp granting request sent by the user terminal 6 may be the user ID of the user using that user terminal 6. If the user identified by the user identification information included in the stamp granting request has entered a stamp card campaign, the stamp card management server 1 searches for payment information in which that user is the payment source (step S42). As a result, the stamp card management server 1 grants a stamp to the stamp card of that user, on the condition that the user who has entered the stamp card campaign has made payment to the store (step S32).

[0318] [11-1. Configuration of the stamp card management server] Next, the configuration of the stamp card management server 1 will be described with reference to Fig. 69 and Fig. 70. Fig. 69 is a block diagram showing an example of the schematic configuration of the stamp card management server 1 according to this embodiment. In Fig. 69, the same elements as those in Fig. 64 are given the same reference numerals. As shown in Fig. 69, the storage unit 14 of the stamp card management server 1 may store a stamp card DB 14a, an entry DB 14c, a stamp history DB 14d, a benefit DB 14e, a store DB 14f, a stamp action history DB 14g, and a promotion target store DB 14j, as well as a stamp grant request user DB 14k.

[0319] Fig. 70 is a diagram showing an example of the contents stored in the stamp grant request user DB 14k of the stamp card management server 1. As shown in Fig. 70, the stamp grant request user DB 14k may store the user ID of a user identified by user identification information included in each stamp grant request received by the stamp card management server 1.

[0320] [11-2. Functional overview of the system control unit of the stamp card management server] Next, an overview of the functions of the system control unit 11 of the stamp card management server 1 will be described with reference to Fig. 71. Fig. 71 is a diagram showing an example of functional blocks of the system control unit 11 of the stamp card management server 1 according to this embodiment. In Fig. 71, the same elements as those in Fig. 66 are given the same reference numerals. As shown in Fig. 71, the system control unit 11 may function as a stamp granting request receiving unit 1108, a usage application information searching unit 1109, a stamp granting unit 1110, a stamp card screen information sending unit 1111, a payment information searching unit 1121, and a provider identification information acquiring unit 1151.

[0321] The stamp granting request receiving unit 1108 may receive a stamp granting request from a terminal device used by either the provider of the transaction object as the stamp granting source or the user as the stamp recipient. In this case, the terminal device of the provider of the transaction object is the store payment terminal 20. The terminal device of the user is the user terminal 6. As described above, the stamp granting request may include user identification information.

[0322] The stamp granting request receiving unit 1108 may store the user ID of the user identified by the user identification information included in the stamp granting request in the stamp granting request user DB 14k. If the stamp granting request includes a user ID, the stamp granting request receiving unit 1108 may store the user ID in the stamp granting request user DB 14k. If the stamp granting request includes payment method user identification information, the stamp granting request receiving unit 1108 may acquire the user ID of the user identified by the payment method user identification information from the payment server 10 corresponding to the payment method used by the user. The stamp granting request receiving unit 1108 may store the acquired user ID in the stamp granting request user DB 14k.

[0323] The application information search unit 1109 may search the entry DB 14c for user identification information for identifying the same user as the user identified by the user identification information included in the stamp grant request received by the stamp grant request receiving unit 1108. In this way, the application information search unit 1109 may acquire user identification information. For example, if a user ID for identifying the same user as the user identified by the user identification information included in the stamp grant request is stored in the stamp grant request user DB, the application information search unit 1109 may search the entry DB 14c for user identification information that matches the user identification information stored in the stamp grant request user DB. After the search is completed, the application information search unit 1109 may delete the user identification information from the stamp grant request user DB. The application information search unit 1109 may perform this search periodically. Examples of search intervals include one hour, six hours, and one day. The application information search unit 1109 may acquire any entry information from the entry DB 14c. For example, the application information search unit 1109 may search the entry DB 14c for entry information including user identification information included in the stamp grant request or user identification information for identifying the same user as the user identified by the user identification information stored in the stamp grant request user DB, and may obtain at least the user identification information and stamp card identification information from the searched entry information.

[0324] The payment information search unit 1121 may search for payment information on the condition that corresponding user identification information has been found by the search by the usage application information search unit 1109. For example, the payment information search unit 1121 may search for payment information on the condition that corresponding entry information has been found. If corresponding user identification information is not found, the payment information search unit 1121 does not need to search for payment information.

[0325] If the application information search unit 1109 does not find any corresponding user identification information through a search, the stamp granting unit 1110 does not need to grant a stamp.

[0326] [11-3. Operation of communication systems] The stamp card management server 1 may periodically execute stamp control processing. This stamp control processing may be the same as the stamp control processing shown in Fig. 67. However, the stamp card management server 1 may acquire the user ID from the stamp grant request user DB 14k instead of acquiring the user ID from the entry DB 14c in step S1001. Then, in step S1002, the stamp card management server 1 may generate a list using the acquired user IDs.

[0327] As described above, according to this embodiment, it is only necessary to search for payment information indicating that the user who requested the stamp granting among the users who applied to use the stamp card has made a payment to pay the price, so that the process of granting stamps can be carried out more efficiently.

[0328] (Supplementary Note 1-1) In the stamp granting device, for each of a plurality of digitized stamp cards, stamp card identification information for identifying the stamp card and authentication information for logging in to stamp granting software for granting a stamp to the stamp card are stored in association with each other in an authentication information storage means, and the device comprises: authentication information receiving means for receiving the stamp card identification information and the authentication information input to a terminal device used by a promotion target who is the subject of a promotion; authentication means for performing login authentication based on the received stamp card identification information and authentication information and the stored stamp card identification information and authentication information; code sending means for sending a code indicating information on either the promotion target or the user to a terminal device used by the promotion target or the user to whom the stamp is to be granted; and information receiving means for receiving information on the promotion target and information on the user from a terminal device used by the other of the promotion target and the user that reads the code received by the terminal device used by the promotion target. and stamp granting means for executing a process of granting a stamp based on the received promotion target information and user information, wherein the promotion target information includes the stamp card identification information for which the login authentication was successful, and the user information includes user identification information for identifying the user, and the stamp granting means grants a stamp to a stamp card used by the user identified by the user identification information included in the user information, out of the stamp cards identified by the stamp card identification information included in the promotion target information, and the stamp granting software, on the condition that the login authentication is successful, causes the terminal device used by the promotion target to function as at least one of code receiving means for receiving the code indicating the promotion target information from the stamp granting device and code reading means for reading the code indicating the user information and transmitting the promotion target information and the user information to the stamp granting device.

[0329] (Appendix 1-2) The stamp granting device described in Appendix 1-1 is characterized in that at least one of the promotion targets is a provider of the transaction object, and the stamp granting device further comprises a payment information retrieval means for retrieving payment information including payment source identification information for identifying the user who paid the price from a payment information storage means that stores payment information for each payment, the payment information including payment source identification information for identifying the user who paid the price, the user being identified by the user identification information included in the information of the user received by the information receiving means, as the payment source, and the stamp granting means grants the stamp only when the corresponding payment information is found by the search by the payment information retrieval means.

[0330] (Appendix 1-3) The stamp granting device described in Appendix 1-2 further comprises an application information search means for searching, each time an application for use of any of the plurality of stamp cards is made, for application information including user identification information for identifying the user who made the application and stamp card identification information for identifying the applied-for stamp card from an application information storage means which stores application information including user identification information for identifying the user who made the application and stamp card identification information for identifying the applied-for stamp card, for application information including a combination that matches the combination of the user identification information included in the information of the user received by the information receiving means and the stamp card identification information included in the information of the promotion target received by the information receiving means, wherein the payment information search means performs a search for the payment information on the condition that the search by the application information search means finds the corresponding application information, and the stamp granting means does not grant the stamp if the corresponding application information is not found.

[0331] (Appendix 1-4) The stamp granting device described in any one of Appendices 1-1 to 1-3 is characterized in that at least one of the promotion targets is a provider of the transaction object, and the stamp granting device further comprises a payment information retrieval means for retrieving the payment information including payment source identification information for identifying the user who paid the price from a payment information storage means that stores payment information for each payment, the payment information including payment source identification information for identifying the user who paid the price, the user being identified by the user identification information included in the information of the user received by the information receiving means, as the payment source, and the stamp granting means changes the number of stamps to be granted depending on whether or not the relevant payment information is found by the search by the payment information retrieval means.

[0332] (Appendix 1-5) A stamp applying device as described in any one of Appendices 1-2 to 1-4, characterized in that the information on the promotion object includes promotion object identification information for identifying the promotion object, the stored payment information further includes payment recipient identification information for identifying the provider of the payment recipient of the fee, and the payment information search means searches for the payment information including the payment source identification information for identifying the user identified by the user identification information included in the user information received by the information receiving means as the payment source, and the payment recipient identification information for identifying the promotion object identified by the promotion object identification information included in the information on the promotion object received by the information receiving means as the payment recipient.

[0333] (Appendix 1-6) The stamp-granting software displays a screen on a terminal device used by the promotion target that accepts an operation to select either a first method in which the terminal device outputs the code indicating information about the promotion target or a second method in which the terminal device reads the code indicating information about the user as a method for granting the stamp, and the stamp-granting software causes the terminal device used by the promotion target to function as the code receiving means when the first method is selected on the screen, and causes the terminal device used by the promotion target to function as the code reading means when the second method is selected on the screen. The stamp-granting software is characterized in that

[0334] (Appendix 1-7) A stamp granting device as described in any one of Appendices 1-1 to 1-6, further comprising: a screen information sending means for sending screen information showing a screen that accepts input of stamp card identification information for identifying the stamp card to be used in the promotion and authentication information to be used for login authentication of the promotion target to a terminal device used by either an applicant who applies for registration of the promotion target who can use the stamp granting software or an operator of a stamp card service who accepts the registration application from the applicant; an application authentication information receiving means for receiving the stamp card identification information and the authentication information entered on the screen displayed on the terminal device based on the sent screen information; and a memory control means for storing the received authentication information in the authentication information storage means in association with the received stamp card identification information.

[0335] (Appendix 1-8) The stamp applying device described in any one of Appendices 1-1 to 1-7 further comprises: a transaction service action history information acquisition means for acquiring transaction service action history information indicating a history of actions taken with respect to a transaction service that enables electronic commerce, the history being a history of actions by the user identified by the user identification information included in the user information received by the information receiving means; and a non-transaction service action history information acquisition means for acquiring non-transaction service action history information indicating a history of actions taken with respect to a non-transaction service different from the transaction service, the history being a history of actions by the user identified by the user identification information included in the user information received by the information receiving means, wherein the stamp applying means changes the number of stamps to be applied based on the history of actions with respect to the transaction service indicated by the acquired transaction service action history information and the history of actions with respect to the non-transaction service indicated by the acquired non-transaction service action history information.

[0336] (Appendix 1-9) The stamp granting device described in Appendix 1-8 is characterized in that when the user makes a transaction in the transaction service, the acquired transaction service action history information indicates the content of the transaction, and when the user takes action to contract for the non-transaction service or to cancel the contract, the acquired non-transaction service action history information indicates the action taken between the contracting action and the contract cancellation action, and the stamp granting means grants a greater number of stamps when a predetermined condition is met than when the condition is not met, and the predetermined condition is that the content of the transaction meets a predetermined transaction content condition and the non-transaction service is currently under contract.

[0337] (Appendix 1-10) The stamp granting device described in any one of Appendices 1-1 to 1-9 further comprises a payment information acquisition means for acquiring payment information indicating that a payment has been made from the user identified by the user identification information included in the user information received by the information receiving means to pay the promotion target, the payment information including amount information indicating the amount paid, and the stamp granting means changes the number of stamps to be granted depending on the amount indicated by the amount information included in the acquired payment information.

[0338] (Appendix 1-11) A stamp granting device as described in any one of Appendices 1-1 to 1-10, further comprising a point granting means for granting points that can be used for payment to the user to whom the stamp is granted when the stamp is granted by the stamp granting means.

[0339] (Appendix 1-12) The stamp granting device described in Appendix 1-11, characterized in that the point granting means grants points that can be used both for transaction services that enable electronic commerce and for non-transaction services that are different from the transaction services.

[0340] (Appendix 1-13) A stamp-giving device as described in Appendix 1-11 or 1-12, characterized in that the number of stamps given by the stamp-giving means may vary, and the point-giving means gives points in a number corresponding to the number of stamps given by the stamp-giving means.

[0341] (Appendix 1-14) A stamp granting device as described in any one of Appendices 1-11 to 1-13, further comprising: a transaction service action history information acquisition means for acquiring transaction service action history information indicating a history of actions taken with respect to transaction services that enable electronic commerce, the history being a history of actions by the user identified by the user identification information included in the user information received by the information receiving means; and a non-transaction service action history information acquisition means for acquiring non-transaction service action history information indicating a history of actions taken with respect to non-transaction services different from the transaction services, the history being a history of actions by the user identified by the user identification information included in the user information received by the information receiving means, wherein the point granting means changes the number of points to be granted based on the history of actions with respect to the transaction services indicated by the acquired transaction service action history information and the history of actions with respect to the non-transaction services indicated by the acquired non-transaction service action history information.

[0342] (Appendix 1-15) The stamp-giving device described in Appendix 1-14 is characterized in that when the user makes a transaction in the transaction service, the acquired transaction service action history information indicates the content of the transaction, and when the user takes action to sign up for the non-transaction service or to cancel the contract, the acquired non-transaction service action history information indicates the action taken between the action to sign up and...

Claims

1. a user identification information acquisition means for acquiring any of the user identification information from a user identification information storage means for storing user identification information for identifying each user who has applied to use the electronic stamp card; a payment information retrieval means for retrieving, from a payment information storage means for storing, for each payment, payment information indicating that a settlement has been made for payment of a transaction price from a user to a provider of a transaction object, the payment information including payment source identification information for identifying the user who has paid the price, the payment information including the payment source identification information for identifying the user who is identified by the acquired user identification information as the payment source; a stamp giving means for executing a process of giving a stamp to the user identified by the acquired user identification information, on condition that the relevant payment information is found by the search by the payment information search means; A stamp applying device comprising:

2. a request information receiving means for receiving request information indicating a request for granting of a stamp from a terminal device of either a provider of a trading object as a source of granting the stamp or a user as a recipient of the stamp, the request information including user identification information for identifying the user as a recipient of the stamp; the user identification information acquisition means searches the user identification information storage means for the user identification information for identifying the same user as the user identified by the user identification information included in the received request information; the payment information search means executes a search for the payment information on condition that the corresponding user identification information is found by the search by the user identification information acquisition means; 2. The stamp applying device according to claim 1, wherein said stamp applying means does not apply said stamp if said corresponding user identification information is not found.

3. The user identification information storage means stores application information including the user identification information of the user who applied and stamp card identification information for identifying the applied stamp card each time an application is made for use of any one of the plurality of electronic stamp cards, the received request information further includes stamp card identification information for identifying a stamp card corresponding to the stamp provider among the plurality of stamp cards, The user identification information acquisition means searches for application information containing a combination that matches the combination of the user identification information and the stamp card identification information contained in the received request information, the payment information search means executes a search for the payment information on the condition that the corresponding use application information is found by the search by the user identification information acquisition means; 3. The stamp applying device according to claim 2, wherein said stamp applying means does not apply said stamp if said corresponding application information is not found.

4. the received request information further includes provider identification information for identifying a provider who has provided the stamp; The stored payment information further includes payment recipient identification information for identifying a provider of the payment recipient of the payment, The stamp application device according to claim 2, characterized in that the payment information search means searches for the payment information including the payment source identification information for identifying the user identified by the user identification information included in the received request information as the payment source, and the payment destination identification information for identifying the provider identified by the provider identification information included in the received request information as the payment destination.

5. further comprising a code transmitting means for transmitting a code indicating information of the other of the provider and the user to a terminal device used by the other of the provider and the user; the terminal device used by the one party reads the code received from the stamp applying device by the terminal device used by the other party, and transmits the request information to the stamp applying device, the request information including information about the other party indicated by the read code and information about the one party using the terminal device that read the code; the user information of the one information and the other information included in the request information includes the user identification information, a terminal device used by the provider displays a screen for accepting an operation to select, as a method for applying the stamp, either a first method in which the terminal device outputs the code indicating the information of the provider or a second method in which the terminal device reads the code indicating the information of the user; The stamp applying device according to claim 2, characterized in that, when the first method is selected on the screen, the terminal device used by the provider receives the code indicating the provider's information from the stamp applying device, and when the second method is selected on the screen, reads the code indicating the user's information and transmits the request information to the stamp applying device.

6. a transaction service behavior history information acquisition means for acquiring transaction service behavior history information indicating a history of behaviors taken by the user identified by the acquired user identification information, the history being a history of behaviors taken with respect to a transaction service that enables electronic commerce; a non-transaction service behavior history information acquisition means for acquiring non-transaction service behavior history information indicating a history of behaviors taken regarding non-transaction services different from the transaction service, the non-transaction service behavior history information indicating a history of behaviors of the user identified by the acquired user identification information; Further provided with A stamp application device as described in any one of claims 1 to 5, characterized in that the stamp application means changes the number of stamps to be applied based on the history of behavior regarding the transaction service indicated by the acquired transaction service behavior history information and the history of behavior regarding the non-transaction service indicated by the acquired non-transaction service behavior history information.

7. When the user makes a transaction using the transaction service, the acquired transaction service behavior history information indicates the content of the transaction, When the user takes an action to enter into a contract for the non-transaction service or an action to cancel the contract, the acquired non-transaction service action history information indicates the action taken between the action to enter into the contract and the action to cancel the contract, the stamp applying means applies a greater number of stamps when a predetermined condition is satisfied than when the condition is not satisfied; 7. The stamp applying device according to claim 6, wherein the predetermined conditions are that the content of the transaction satisfies a predetermined transaction content condition and that the non-transaction service is under contract.

8. The stored payment information further includes amount information indicating a paid amount; A stamp applying device according to any one of claims 1 to 5, characterized in that the stamp applying means changes the number of stamps to be applied depending on the amount indicated by the amount information included in the payment information searched by the payment information search means.

9. The stamp granting device according to any one of claims 1 to 5, further comprising a point granting means for granting points that can be used for payment to the user to whom the stamp is granted when the stamp is granted by the stamp granting means.

10. 10. The stamp applying device according to claim 9, wherein the point applying means applies the points that can be used in both a transaction service that enables electronic commerce and a non-transaction service that is different from the transaction service.

11. The number of stamps applied by the stamp applying means may vary; 10. The stamp applying device according to claim 9, wherein the point applying means applies points in a number corresponding to the number of stamps applied by the stamp applying means.

12. a transaction service behavior history information acquisition means for acquiring transaction service behavior history information indicating a history of behaviors taken by the user identified by the acquired user identification information, the history being a history of behaviors taken with respect to a transaction service that enables electronic commerce; a non-transaction service behavior history information acquisition means for acquiring non-transaction service behavior history information indicating a history of behaviors taken regarding non-transaction services different from the transaction service, the non-transaction service behavior history information indicating a history of behaviors of the user identified by the user identification information included in the acquired user information; Further provided with The stamp granting device described in claim 9, characterized in that the point granting means changes the number of points to be granted based on the history of behavior regarding the transaction service indicated by the acquired transaction service behavior history information and the history of behavior regarding the non-transaction service indicated by the acquired non-transaction service behavior history information.

13. When the user makes a transaction using the transaction service, the acquired transaction service behavior history information indicates the content of the transaction, When the user takes an action to enter into a contract for the non-transaction service or an action to cancel the contract, the acquired non-transaction service action history information indicates the action taken between the action to enter into the contract and the action to cancel the contract, the point awarding means awards a greater number of points when a predetermined condition is satisfied than when the condition is not satisfied; 13. The stamp applying device according to claim 12, wherein the predetermined condition is that the content of the transaction satisfies a predetermined transaction content condition and the non-transaction service is under contract.

14. The stored payment information further includes amount information indicating a paid amount; The stamp granting device according to claim 9, characterized in that the point granting means changes the number of points to be granted depending on the amount indicated by the amount information included in the payment information searched by the payment information search means.

15. the user identification information acquisition means acquires the user identification information stored in the user identification information storage means, 2. The stamp applying device according to claim 1, wherein the payment information searching means searches for the payment information for each of the acquired user identification information.

16. The user identification information storage means stores application information including the user identification information of the user who applied and stamp card identification information for identifying the applied stamp card each time an application is made for use of any one of the plurality of electronic stamp cards, For each of the plurality of stamp cards, stamp card identification information for identifying the stamp card and provider identification information for identifying a provider corresponding to the stamp card among providers of transaction objects are associated with each other and stored in a provider identification information storage means; The stored payment information further includes payment recipient identification information for identifying a provider of the payment recipient of the payment, the user identification information acquisition means acquires any of the use application information from the user identification information storage means, a provider identification information acquisition means for acquiring, from the provider identification information storage means, the provider identification information associated with the stamp card identification information included in the acquired use application information; The stamp application device described in claim 1 or 15, characterized in that the payment information search means searches for the payment information including the payment source identification information for identifying the user identified by the user identification information included in the acquired application information as the payment source, and the payment destination identification information for identifying the acquired provider identification information as the payment destination.

17. The number of stamps is stored in a stamp number storage means in association with user identification information for identifying each user who has applied to use the electronic stamp card; 6. The stamp applying device according to claim 1, wherein the stamp applying unit applies the stamp by increasing the number of stamps associated with the acquired user identification information.

18. 1. A computer-implemented stamping method comprising: a user identification information acquisition step of acquiring any of the user identification information from a user identification information storage means that stores user identification information for identifying each user who has applied to use the electronic stamp card; a payment information retrieval step of retrieving, from a payment information storage means that stores, for each payment, payment information indicating that a settlement has been made for payment of the price of a transaction from a user to a provider of a transaction object, the payment information including payment source identification information for identifying the user who has paid the price, the payment information including the payment source identification information for identifying the user identified by the acquired user identification information as the payment source; a stamp giving step of executing a process of giving a stamp to the user identified by the acquired user identification information, on condition that the corresponding payment information is found by the search in the payment information search step; A stamp applying method comprising:

19. Computer, a user identification information acquisition means for acquiring any of the user identification information from a user identification information storage means for storing user identification information for identifying each user who has applied to use the electronic stamp card; a payment information retrieval means for retrieving, from a payment information storage means for storing, for each payment, payment information indicating that a settlement has been made for payment of a transaction price from a user to a provider of a transaction object, the payment information including payment source identification information for identifying the user who has paid the price, the payment information including the payment source identification information for identifying the user who is identified by the acquired user identification information as the payment source; a stamp giving means for executing a process of giving a stamp to the user identified by the acquired user identification information, on condition that the relevant payment information is found by the search by the payment information search means; A stamp giving program characterized by causing the program to function as follows.

Images