JP2023129285A - Privilege assigning system, privilege assigning method and program - Google Patents

Abstract

To improve convenience of users using a service.SOLUTION: A privilege assigning system (S) includes: a use determination part (201) for determining whether or not a service has been used in an unreceivable state where a user cannot receive a privilege; a temporary privilege generation part (202) for generating a temporary privilege when it is determined that the service has been used in the unreceivable state; a reception condition determination part (204) for determining, after use of the service, whether or not a reception condition relating to reception of the temporary privilege has been satisfied; and a temporary privilege assigning part (205) for assigning the temporary privilege to the user when it is determined that the reception condition has been satisfied.SELECTED DRAWING: Figure 5

Description

The present disclosure relates to a benefit granting system, a benefit granting method, and a program.

2. Description of the Related Art Conventionally, techniques for granting benefits to users who use a service are known. For example, Patent Document 1 describes the conditions for using points for users who do not associate the card number of a membership card with member identification information in an online service, and the conditions for using points for users who do not associate the card number of a membership card with member identification information in an online service. It describes a technique that makes the usage conditions stricter than the usage conditions.

For example, in Patent Document 2, fixed identification code information sent to a user terminal is associated with a provisionally assigned point value, and when the user terminal is logged in and the user identification information is specified, Accordingly, a technique is described in which a temporary point value associated with fixed identification code information is included in a point value corresponding to user identification information.

JP2017-054282A Japanese Patent Application Publication No. 2020-166740

However, with the technique of Patent Document 1, a user who does not have a membership card cannot accumulate points even if he or she uses a store. The same applies to users who forget to bring their membership cards and users who forget to present their membership cards at stores, and cannot receive points. The technology of Patent Document 2 is similar, and users who have not completed membership registration, users who forget to bring their user terminals, and users who forget to present their user terminals at a store receive points. I can't. For this reason, conventional techniques have not been able to sufficiently enhance the convenience of users of services.

One of the purposes of the present disclosure is to improve convenience for users of services.

The benefit granting system according to the present disclosure includes a usage determination unit that determines whether the service is used in a non-receivable state in which the user cannot receive benefits, and a case where it is determined that the service is used in the non-receivable state. a provisional benefit generation unit that generates a provisional benefit; a reception condition determination unit that determines whether or not a receipt condition regarding receipt of the provisional benefit is met after using the service; and a receipt condition determination unit that determines whether the receipt condition is satisfied. and a provisional benefit granting unit that grants the provisional benefit to the user when it is determined that the provisional benefit has been granted to the user.

According to the present disclosure, convenience for users who use the service increases.

It is a diagram showing an example of the overall configuration of a privilege granting system. FIG. 2 is a diagram illustrating an example of how a user who has registered as a member of a point service uses a physical store. FIG. 2 is a diagram illustrating an example of how a user who is not a member of a point service uses a physical store. FIG. 3 is a diagram showing an example of how a user reads a receipt code. It is a functional block diagram showing an example of a function realized by a privilege granting system. It is a figure showing an example of a privilege database. It is a figure showing an example of a provisional privilege database. It is a diagram showing an example of a member database. It is a diagram showing an example of a physical store usage process executed by the privilege granting system. It is a figure showing an example of member registration processing performed by a privilege granting system. It is a figure which shows an example of the flow of receiving receivable points in 2nd Embodiment. It is a figure which shows an example of the flow of receiving receivable points in 3rd Embodiment. It is a diagram showing an example of a chronological flow until a user issues an affiliated credit card. It is a figure which shows an example of the functional block in a modification. 12 is a diagram showing an example of a screen displayed in Modification 6. FIG. 12 is a diagram showing an example of a point management screen displayed in Modification 8. FIG. 12 is a diagram showing an example of a point management screen displayed in Modification 10. FIG.

[1. First embodiment]
A first embodiment, which is an example of an embodiment of a privilege granting system according to the present disclosure, will be described. In the first embodiment, a case will be exemplified in which a retail service that retails products at a physical store and a point service that provides points that can be used for payment at the physical store are affiliated with each other. It is assumed that the users of the physical store are not members of the point service. The benefit award system can also be applied to other situations. Examples of application to other scenes will be described later.

[1-1. Overall configuration of benefit granting system]
FIG. 1 is a diagram showing an example of the overall configuration of a privilege granting system. For example, the benefit granting system S includes a store server 10, a benefit management server 20, a member management server 30, a store terminal 40, and a user terminal 50. These computers can be connected to a network N such as the Internet or a LAN.

The privilege granting system S may include at least one computer, and is not limited to the example shown in FIG. 1. For example, the privilege granting system S may include only the privilege management server 20 and the member management server 30, and the store server 10, the store terminal 40, and the user terminal 50 may exist outside the privilege granting system S. For example, the privilege granting system S may include only the privilege management server 20, and the member management server 30 may exist outside the privilege granting system S. The privilege granting system S may include other computers not shown in FIG.

The store server 10 is a server computer managed by a retailer that provides retail services. Control unit 11 includes at least one processor. The storage unit 12 includes volatile memory such as RAM and nonvolatile memory such as flash memory. The communication unit 13 includes at least one of a communication interface for wired communication and a communication interface for wireless communication.

The benefit management server 20 is a server computer managed by a point company that provides point services. The physical configurations of the control section 21, the storage section 22, and the communication section 23 are the same as those of the control section 11, the storage section 12, and the communication section 13, respectively.

The member management server 30 is a server computer managed by a point company. The physical configurations of the control section 31, the storage section 32, and the communication section 33 are the same as those of the control section 11, the storage section 12, and the communication section 13, respectively.

Store terminal 40 is a computer located at a retailer's physical store. In the first embodiment, a case will be described in which the store terminal 40 is a POS terminal, but the store terminal 40 may be another computer, for example, a personal computer, a tablet terminal, or a smartphone. The physical configurations of the control section 41, the storage section 42, and the communication section 43 are the same as those of the control section 11, the storage section 12, and the communication section 13, respectively. The operation unit 44 is an input device such as a touch panel. The display section 45 is a liquid crystal display or an organic EL display.

A reading device 46 and an output device 47 are connected to the store terminal 40 . The reading device 46 is a device that reads images or storage media. In the first embodiment, a case will be described in which the reading device 46 is a code reader, but the reading device 46 may be another device, such as a camera, a scanner, an NFC reader, or a magnetic card reader. Good too. The reading device 46 may have not only a reading function but also a writing function.

The output device 47 is an image forming device. In the first embodiment, a case will be described in which the output device 47 is a receipt printer, but the output device 47 may be another device, such as a printer that outputs paper other than receipts, or an image that is not classified as a printer. It may be a forming device, a copy machine, or a multifunction device. The receipt may be output as electronic data instead of physical paper.

The user terminal 50 is a user's computer. In the first embodiment, a case will be described in which the user terminal 50 is a smartphone, but the user terminal 50 may be another computer, for example, a personal computer, a tablet terminal, or a wearable terminal. good. The physical configurations of the control unit 51, storage unit 52, communication unit 53, operation unit 54, and display unit 55 are the same as those of the control unit 11, storage unit 12, communication unit 13, operation unit 44, and display unit 45, respectively. be. The reading unit 56 may be the same as the reading device 46, but in the first embodiment, the reading unit 56 is a camera of a smartphone.

Note that the programs stored in the storage units 12, 22, 32, 42, and 52 may be supplied via the network N. In addition, the program stored in the information storage medium may be used as a reading unit (for example, an optical disk drive or a memory card slot) for reading a computer-readable information storage medium, or an input/output unit for inputting and outputting data with external equipment. (e.g., a USB port).

[1-2. Overview of first embodiment]
For example, if a user becomes a member of a point service, he or she can receive points corresponding to the amount spent at a physical store. The physical store is a point service member store. A user may become a member of a point service by issuing a physical point card, or may become a member of a point service by registering as a member from the user terminal 50. When a user becomes a member of a point service, he/she presents a point card proving his or her membership at a physical store.

FIG. 2 is a diagram illustrating an example of how a user who has registered as a member of the point service uses a physical store. In the first embodiment, a case will be described in which the point card screen G1 displayed on the user terminal 50 is used as a virtual point card, but a physical point card such as an IC card, magnetic card, NFC card, or other card may be used. A point card may also be used. The IC chip of the user terminal 50 may be used as a point card.

For example, a point service application (hereinafter referred to as a point application) is installed on the user terminal 50. When the user launches the point app, a login process to the point service is executed. If the login process is successful, a point card screen G1 is displayed on the display unit 55. On the point card screen G1, a code C10 including a display ID that can identify the user is displayed together with the user's point balance. The code C10 may be of any type such as a barcode or a two-dimensional code.

A clerk at the physical store reads the barcode of the product and the code C10 on the point card screen G1 using the reading device 46. If it is a self-checkout, the user reads these with the reading device 46. The user can use all or part of the point balance, or can accumulate points without using them. When the user finishes paying, the output device 47 outputs a receipt R2. Usage history information I20 regarding the usage history of the physical store and point information I21 regarding the user's points are printed on the receipt R2.

For example, information such as the store name, store telephone number, store address, date and time of use, details of products purchased by the user, and transaction amount is printed on the receipt R2 as the usage history information I20. For example, as point information I21, a part of the card number that can identify the point card, the amount of money that is eligible for points, the points to be received, the points that can be used, and the transaction code that can identify the transaction are printed on the receipt R2. .

In the example of FIG. 2, the return rate of the point service is 1%, and when the user makes a purchase of 4,000 yen, 40 points are scheduled to be given. In the first embodiment, a case will be described in which the user can receive points after a certain amount of time has passed, but the user may be able to receive points immediately after shopping. As shown in FIG. 2, if the user is a member of a point service, he or she can receive points according to the amount spent at the physical store.

FIG. 3 is a diagram illustrating an example of how a user who is not a member of a point service uses a physical store. Since users are not members of a point service, they basically cannot receive points even if they use a physical store. Since the user does not have a point card, he/she uses the physical store without presenting the point card. When the user finishes paying, the output device 47 outputs a receipt R3.

Usage history information I30 and point information I31 are printed on the receipt R3. The usage history information I30 is similar to the usage history information I20 in FIG. 2. Point information I31 is different from point information I21 in FIG. For example, as the point information I31, the amount of money that would have been eligible for points if you were a member of a point service, the receivable points, and the receiving code C310 are printed on the receipt R3.

In the first embodiment, when a user who is not a member of a point service reads the receiving code C310 with the reading unit 56 and becomes a member of the point service, he or she can receive receivable points. Receivable points are points that cannot be received on the spot when the user visits a physical store, but can be received if the user becomes a member of a point service. The receipt code C310 includes a receipt ID that can identify receivable points and a link to the point service member registration screen.

FIG. 4 is a diagram showing an example of how the user reads the receipt code C310. When the user reads the receipt code C310 with the user terminal 50, a member registration screen G4 is displayed on the display unit 55. For example, the user inputs member information such as email address, member ID, password, name, and date of birth into input forms F40 to F44. When the user inputs member information and selects button B45, membership registration for the point service is completed and receivable points are granted to the user.

For example, when membership registration for a point service is completed, a registration completion screen G5 is displayed on the display unit 55. The registration completion screen G5 displays the receivable points given to the user and member information registered in the point service. In the example of FIG. 4, the user is given 40 receivable points printed on the same receipt R3 as the receipt code C310 read at the time of membership registration. The user selects the button B50 to download and install the point application on the user terminal 50.

When the point app is installed on the user terminal 50, the user can use the 40 points given at the time of membership registration by presenting the code C10 on the point card screen G1 of the point app at a physical store. If points other than the receivable points are awarded as a benefit at the time of member registration, the point balance including these points is displayed on the point card screen G1. For example, if 2000 points are awarded as part of a membership registration campaign, the user can use 2040 points from the beginning, which is the sum of 40 points that can be received.

As described above, in the first embodiment, when a user uses a physical store without being a member of a point service, receivable points are generated. When the user reads the receiving code C310 with the reading unit 56 and becomes a member of the point service, he or she can receive receivable points. This allows users to receive points that they could not receive in the past, increasing convenience for users and increasing the appeal to become members of a point service. Hereinafter, details of the first embodiment will be described.

[1-3. Functions realized by the benefit granting system]
FIG. 5 is a functional block diagram showing an example of functions realized by the privilege granting system S.

[1-3-1. Functions realized by store server]
The data storage unit 100 is mainly realized by the storage unit 12. The service providing unit 101 and the output unit 102 are mainly realized by the control unit 11.

[Data storage unit]
The data storage unit 100 stores data necessary for providing retail services to users. For example, the data storage unit 100 stores a product database regarding products sold through retail services. The product database stores information such as a product code, product name, price, and inventory that can identify the product. As the product database itself, various databases in known retail services can be used. For example, the data storage unit 100 stores a usage result database regarding usage results of retail services by users. The usage result database stores information corresponding to usage history information I20, I30 and point information I21, I31 printed on receipts R2, R3.

[Service provision department]
The service providing unit 101 provides retail services to users. Various known methods can be used to provide retail services. Processing for users of point services to use and accumulate points at physical stores can also be performed using various known methods. However, in the first embodiment, the method of outputting the receipt R3 when a user who is not registered with the point service uses a physical store is different from the conventional method. As for the functions of the store server 10, the function of the output unit 102 is mainly different from the conventional function. Since conventional functions can be used for other functions of the store server 10, the retail service side can introduce the functions of the first embodiment with minimal modification.

[Output section]
The output unit 102 outputs receipts R2 and R3 at the physical store. Outputting the receipts R2 and R3 means having the output device 47 print usage history information I20 and I30 and point information I21 and I31 on the receipts R2 and R3, and then ejecting the receipts R2 and R3. In the first embodiment, a case will be described in which receipts R2 and R3 are output by communicating between the store server 10 and the store terminal 40 at the time of the user's checkout. It may also be output by the terminal 40 communicating. The store terminal 40 does not need to communicate with other computers when outputting the receipts R2 and R3.

For example, if it is determined that the retail service was used in a non-receivable state, the output unit 102 causes the physical store to output the receipt R3 including the receiving ID, thereby causing the physical store to output the receiving ID. Receipt R3 is an example of a first receipt. Therefore, the portion describing receipt R3 can be read as the first receipt. The first receipt is a receipt for a user who is unable to receive the item. The first receipt is printed in the first layout.

The unreceivable state is a state in which the user cannot receive points. In the first embodiment, a state in which the user is not a member of a point service corresponds to a state in which receiving is not possible. For this reason, the part that describes the state of not being a member of the point service can be read as the state of not being able to receive the item. The unreceivable state may be any other state other than the state of not being a member of the point service, and is not limited to the example of the first embodiment.

For example, if a user can receive points immediately on the spot when using a retail service, the unreceivable state is a state in which points cannot be received immediately. Even if the user is a member of a point service, he or she cannot receive points immediately unless he or she presents his or her point card. Therefore, a state in which a user who is a member of a point service does not present a point card corresponds to a state in which receipt is not possible.

For example, if a user can receive points after a certain period of time has passed (in the example in Figure 2, within 3 days) after using a retail service, the unreceivable state means that this period has passed. Points are not awarded even after the time has passed. Even if the user is a member of a point service, if he does not present his point card, he will not receive points even if the above-mentioned period has elapsed since he used the retail service. Therefore, a state in which a user who is a member of a point service does not present a point card corresponds to a state in which receipt is not possible.

For example, when the retail service is used in a ready-to-receive state, the output unit 102 causes the physical store to output a receipt R2 that has a different layout from the receipt R3 and does not include a receiving ID. The portion describing the receipt R2 can be read as the second receipt. The second receipt is a receipt for a user who is in a receivable state. The second receipt is printed in a second layout different from the first layout.

The receivable state is a state in which the user can receive points. The receivable state is a state that is not a receivable state. In the first embodiment, the state in which the user is a member of the point service corresponds to the receivable state. Therefore, the portions describing this state can be read as the receivable state. More specifically, a state in which the user is a member of a point service and presents a point card at a physical store corresponds to a receivable state. For example, in cases where it is not necessary to present a point card, such as verbally confirming that the user is a member of a point service, the state in which the user is confirmed to be a member of a point service is the state in which the user can receive the item. corresponds to

The output unit 102 causes the store terminal 40 to output the receipts R2 and R3 by transmitting information necessary for outputting the receipts R2 and R3 to the store terminal 40. This information may be the content to be printed on the receipts R2, R3, or may be information equivalent to a command to output the receipts R2, R3. The method of outputting the receipt R2 is the same as the conventional method, so in the first embodiment, the method of outputting the receipt R3 will be described.

The output unit 102 causes the store terminal 40 to output the receipt R3 on which the receipt code C310 is printed. In the first embodiment, upon generating receivable points, the benefit management server 20 transmits a generation completion notification indicating that generation of receivable points is completed to the store server 10. The generation completion notification includes a receipt code C310 or a receipt ID to be described later, and a numerical value of receivable points. Upon receiving the generation completion notification, the store server 10 transmits an output request to the store terminal 40 to output the receipt R3 based on this numerical value.

The output request is made by transmitting data in a predetermined format. The output request may include information indicating which receipt R2 or R3 should be output. The request to output the receipt R3 includes point information I31. The output request may include usage history information I30. The store terminal 40 outputs the receipt R3 based on the output request. The output unit 102 causes the store terminal 40 to output the receipt R3 by transmitting an output request.

In the first embodiment, since there are two layouts of receipts R2 and R3, the output request includes layout identification information that allows identification of either of the two layouts. If the user is a member of the point service, the output unit 102 transmits an output request including layout identification information indicating the layout of the receipt R2 to the store terminal 40. If the user is not a member of the point service, the output unit 102 transmits an output request including layout identification information indicating the layout of the receipt R3 to the store terminal 40.

[1-3-2. Functions realized by benefit management server]
The data storage section 200 is mainly realized by the storage section 22. The usage determination unit 201, the provisional benefit generation unit 202, the output unit 203, the receiving condition determination unit 204, the provisional benefit provision unit 205, and the benefit provision unit 206 are mainly realized by the control unit 21.

[Data storage unit]
The data storage unit 200 stores various data regarding points. Points are an example of a benefit. Therefore, the parts that explain points can be read as benefits. A benefit is something that brings some kind of benefit to the user. Various known benefits can be used as the benefit itself, and for example, the benefit may be a coupon, electronic money, content such as a video, or a physical product. The parts described as points can be read as various other benefits. The data storage unit 200 stores a privilege database DB1 and a temporary privilege database DB2.

FIG. 6 is a diagram showing an example of the privilege database DB1. The benefit database DB1 is a database for managing points, which are an example of benefits. The benefit database DB1 stores various information regarding points held by members of the point service. For example, the privilege database DB1 stores a member ID, card number, display ID, point balance, and point history.

The member ID is an ID that can identify a member of the point service. The card number is information that can identify the point card. As mentioned above, the point card of the first embodiment is not limited to a physical card, but may be an electronic card (virtual card) using a point app. When a certain member holds a plurality of point cards, the member ID of this member is associated with a plurality of card numbers. The member ID and card number may be used as one ID without distinguishing them.

The display ID is information included in the code C10 displayed on the point card screen G1 of the point app. The code C10 may include a member ID or a card number, but in the first embodiment, it is assumed that the code C10 includes a display ID that is valid for a short time of about 5 minutes. For example, upon receiving a request to generate the code C10 from the user terminal 50, the privilege management server 20 generates a display ID so as not to overlap with other display IDs. Various known methods can be used to generate the display ID. The privilege management server 20 stores the display ID in the privilege database DB1, and transmits the display ID to the user terminal 50.

The point balance is the current balance of points. If points are awarded after a certain amount of time has passed after using a physical store, the points to be received may be stored in the benefit database DB1, separately from the point balance. The point history is at least one of a point receipt history and a point usage history. For example, the point history stores information such as a store ID that can identify a physical store, points to be received, points to be used, date and time of use of the physical store, and details of products purchased at the physical store.

FIG. 7 is a diagram showing an example of the provisional privilege database DB2. The temporary benefit database DB2 is a database for managing receivable points. The provisional benefit database DB2 stores various information regarding receivable points. For example, the temporary benefit database DB2 stores a receiving ID, receivable points, and service usage history.

The receiving ID is an example of temporary benefit identification information. Therefore, the part described as receiving ID can be read as provisional award identification information. The temporary benefit identification information is information that allows identification of a temporary benefit. The temporary award identification information is expressed by letters, numbers, other symbols, or a combination thereof. The temporary award identification information is also information that can identify transactions at a physical store. Temporary benefit identification information is generated so as not to overlap with other temporary benefit identification information.

Receivable points are an example of a temporary benefit. For this reason, the part where it is written as receivable points can be read as provisional benefits. A provisional benefit is a benefit that has not yet been determined to be granted to a user. A provisional benefit can also be said to be a benefit that is not certain to be received. Similar to the benefits described above, the temporary benefits may be of other types, such as coupons.

The service usage history is information regarding the usage history of retail services. For example, when a user uses a retail service, receivable points are generated, and information regarding products purchased by the user at this time is stored. For example, the service usage history stores the store ID of the physical store, date and time of usage, product details, usage amount, and amount eligible for points.

[Usage Judgment Department]
The usage determination unit 201 determines whether the retail service is used in a non-receivable state. For example, when the user uses a retail service, the store server 10 or the store terminal 40 transmits information indicating whether the user is in a non-receivable state or a receivable state to the benefit management server 20. Based on this information, the usage determination unit 201 determines whether the retail service is used in a receivable state. It is assumed that this information is generated based on input from the operation unit 44 or the reading device 46 in the store terminal 40.

Retail services are an example of services according to the present disclosure. For this reason, the portions described as retail services can be read as services. A service is a service that can provide some kind of benefit when the user uses the service. When a user uses a service, a benefit does not necessarily need to be generated, and a benefit may be generated only when some condition is met. The service may be any service and is not limited to retail services.

For example, the service may be a food service, a beauty service, a power service, a moving service, or other services related to daily life. A physical store is not limited to a retail store such as a convenience store or a supermarket, but may be any store such as a restaurant that provides food and drink, a hair salon, or a beauty salon. Services are not limited to those provided in a real space such as a physical store or a user's home, but may be provided online or in a virtual space. For example, the service may be an online shopping service (electronic commerce service), a travel reservation service, a payment service, a financial service, or a communication service. These examples are also applicable to other services described below.

A point service is an example of another service according to the present disclosure. For this reason, the portions described as point services can be read as other services. The other services are services different from the services of which retail services are an example. Other services are services for receiving benefits, for example points. The other services may be any services and are not limited to point services. The combination of the service according to the present disclosure and other services may be any combination and is not limited to the example of the first embodiment.

In the first embodiment, the usage determination unit 201 determines whether the retail service is used in a state where the user is not a member of the point service, thereby determining whether the service is used in a state where the user cannot receive the service. do. For example, the usage determination unit 201 determines whether or not the display ID included in the code C10 displayed on the point card screen G1 of the point app has been acquired, thereby determining whether the user is not a member of the point service. Determine whether the retail service is used.

For example, using a retail service without acquiring a display ID corresponds to using the retail service when the user is not a member of a point service. Obtaining the display ID and using the retail service corresponds to using the retail service while the user is a member of the point service. The information used in the determination by the usage determination unit 201 may be any information that can prove that the user is a member of the point service, and is not limited to the display ID. For example, this information may be a member ID, card number, or other information.

In the first embodiment, the usage determination unit 201 determines whether or not the service is used without presenting the user terminal 50 on which the code C10 is displayed at the physical store. Determine whether or not it has been done. When the code C10 displayed on the point card screen G1 is read by the reading device 46, the store terminal 40 transmits the display ID to the benefit management server 20.

The usage determination unit 201 refers to the benefit database DB1 and determines whether the display ID received from the store terminal 40 exists. The usage determination unit 201 determines that the retail service has been used in a non-receivable state if the display ID does not exist in the benefit database DB1 or if the display ID has not been received in the first place. The usage determination unit 201 determines that the retail service has been used in a receivable state when the display ID exists in the benefit database DB1.

For example, since a user who is not a member of a point service cannot present the code C10 at a physical store, the store terminal 40 does not send the display ID to the benefit management server 20 until the use of the retail service is completed. . Therefore, if the display ID is not received from the store terminal 40 until the use of the retail service is completed, the usage determination unit 201 determines that the retail service has been used in a non-receivable state. In the first embodiment, completing the checkout at the physical store corresponds to completing the use of the retail service.

For example, the usage determination unit 201 detects that usage of the retail service is completed based on a usage completion notification sent from the store server 10 or the store terminal 40 to the benefit management server 20. The usage completion notification is data in a predetermined format indicating that usage of the retail service has been completed. If the display ID is not received before the usage completion notification is received, the usage determination unit 201 determines that the retail service has been used in a non-receivable state. When the display ID is included in the usage completion notification, the usage determination unit 201 determines whether the retail service was used in a non-receivable state by determining whether the display ID is included in the usage completion notification. All you have to do is decide.

The user terminal 50 on which the display ID is displayed is an example of a device related to receiving benefits. Therefore, the portions that describe the user terminal 50 can be read as information regarding receiving benefits. This object may be an object other than the user terminal 50. For example, an IC card, a magnetic card, a card with an NFC function, another card, or a membership card other than a card may correspond to the item related to receiving benefits. These items shall contain information proving eligibility to receive benefits.

Note that the store terminal 40 may transmit the display ID to another computer such as the store server 10 instead of the benefit management server 20. In this case, the other computer transfers the display ID to the privilege management server 20. The usage determination unit 201 may determine whether or not the retail service is used in a non-receivable state based on the transferred display ID.

In addition, when electronic payment is performed by reading a code at a physical store with the user terminal 50 or by simply operating the user terminal 50, the user terminal 50 is connected to the privilege management server 20. Alternatively, a display ID may be transmitted. In this case, the usage determination unit 201 determines whether the retail service is used in a non-receivable state based on the display ID received from the user terminal 50. In this case as well, the user terminal 50 may transmit the display ID to another computer such as the store server 10 instead of the privilege management server 20.

[Temporary benefit generation department]
The provisional benefit generation unit 202 generates receivable points when it is determined that the retail service is used in a non-receivable state. Generating receivable points means generating information regarding receivable points. When using a benefit other than points as a temporary benefit, the temporary benefit generation unit 202 may generate the temporary benefit by generating information according to the type of temporary benefit. For example, the provisional benefit generation unit 202 generates content (digital content) such as coupons, electronic tickets, electronic money, and videos, ownership of digital content, tokens associated with digital content, and digital assets as temporary benefits. , or may generate information about a physical product. The temporary benefit may be, for example, information about something managed on a distributed ledger such as a blockchain network.

In the first embodiment, generating a receiving ID and information indicating a numerical value of receivable points corresponds to generating receivable points. The temporary benefit generation unit 202 generates a receiving ID so as not to overlap with other receiving IDs. The receiving ID may be generated based on a predetermined rule. The provisional benefit generation unit 202 determines receivable points based on the results of the use of the retail service by the user.

For example, the provisional benefit generation unit 202 determines a value obtained by multiplying the user's usage amount by a predetermined return rate as the receivable points. The provisional benefit generation unit 202 may determine a fixed numerical value as the receivable points regardless of the usage amount. For example, the temporary benefit generation unit 202 associates the receiving ID and the generated receivable points and registers them in the temporary benefit database DB2. These can be registered in any other database other than the provisional privilege database DB2.

In the first embodiment, the service usage history is also stored in the provisional award database DB2, so the provisional award generation unit 202 generates three pieces of information: the receiving ID, the receivable points, and the service usage history, and The three generated pieces of information are stored in the temporary privilege database DB2. It is assumed that the service usage history is included in the usage completion notification received from the store server 10 or the store terminal 40.

In the first embodiment, the temporary benefit generation unit 202 does not generate receivable points if it is determined that the retail service is used while the user is a member of the point service. In this case, points are awarded to the user by the benefit granting unit 206, which will be described later. As in the second embodiment described below, the provisional benefit generation unit 202 generates receivable points even if the user is a member of a point service if the user does not present a point card.

[Output section]
The output unit 203 outputs receipts R2 and R3 at the physical store. The output unit 203 causes the store terminal 40 to output the receipts R2 and R3 by transmitting information necessary for outputting the receipts R2 and R3 to the store server 10 or the store terminal 40. This information may be the content to be printed on the receipts R2, R3, or may be information equivalent to a command to output the receipts R2, R3. The method of outputting the receipt R2 is the same as the conventional method, so in the first embodiment, the method of outputting the receipt R3 will be described.

The output unit 203 outputs the receiving ID at the physical store. In the first embodiment, the output unit 203 transmits the generation completion notification described in the process of the output unit 102 of the store server 10 to the store server 10 based on the receiving ID. Thereafter, the output unit 102 of the store server 10 transmits a request to output the receipt R3 to the store terminal 40, so the output unit 203 causes the physical store to output the receipt ID by transmitting a generation completion notification. The output unit 203 may cause the store terminal 40 to output the receipt R3 by directly transmitting the receipt ID to the store terminal 40 instead of the store server 10.

[Receipt condition determination section]
The receiving condition determining unit 204 determines whether receiving conditions regarding receiving receivable points are satisfied after using the retail service. For example, the benefit management server 20 receives information for determining whether the receiving conditions are satisfied from the member management server 30 or the user terminal 50. The receiving condition determination unit 204 determines whether the receiving condition is satisfied based on this information.

In the first embodiment, a case where becoming a member of a point service corresponds to a receiving condition will be described. Therefore, the section explaining about becoming a member of the point service can be read as the receiving conditions. The receiving conditions are conditions for receiving receivable points. The receiving condition may be any condition and is not limited to becoming a member of a point service. For example, the conditions for receipt include that a certain period of time has passed since you became a member of a point service, that you have used the retail service more than a predetermined number of times or for a specified amount after becoming a member of a point service, and that you are eligible for other services other than the point service. This may include becoming a member of a service, purchasing a specific product in a retail service, or registering predetermined member information for a point service.

In the first embodiment, the receiving condition determination unit 204 determines whether the receiving condition is satisfied by determining whether the user has become a member of a point service. Since members of the point service are managed by the member management server 30, the receiving condition determination unit 204 determines whether the user has become a member of the point service based on the information acquired from the member management server 30. do.

In the first embodiment, a receiving ID and receivable points are associated with each other in the temporary privilege database DB2. Just because a user becomes a member of a point service, it is not possible to specify which receivable points he or she is eligible to receive. Therefore, the receiving condition determination unit 204 determines whether the receiving condition is satisfied by determining whether the receiving ID has been acquired from the user terminal 50. If it is not determined that the receiving ID has been acquired from the user terminal 50, the receiving condition determination unit 204 does not determine that the receiving condition is satisfied, and it is determined that the receiving ID has been acquired from the user terminal 50. , it is determined that the receiving conditions are met.

In the first embodiment, since the receiving ID is included in the receiving code C310, the receiving condition determining unit 204 determines whether the receiving ID included in the receiving code C310 has been acquired from the user terminal 50. judge. For example, the user terminal 50 reads the receipt code C310 of the receipt R3. The user terminal 50 acquires the receiving ID and link included in the receiving code C310, transmits the receiving ID to the member management server 30, and accesses the member registration screen G4. The user terminal 50 causes the display unit 55 to display the member registration screen G4. When the user inputs member information into input forms F40 to F44 and selects button B45, member registration processing is executed by member registration section 301, which will be described later.

When the member registration process is completed, the member management server 30 transmits a registration completion notification including the receiving ID received from the user terminal 50 and member information including the member ID to the privilege management server 20. The registration completion notification is data in a predetermined format indicating that membership registration has been completed. Upon receiving the receiving ID and member information from the member management server 30, the benefit management server 20 creates a new record in the benefit database DB1. The privilege management server 20 stores the member information received from the member management server 30 in the new record.

The receiving condition determining unit 204 refers to the provisional privilege database DB2 and determines whether or not the receiving ID received from the privilege management server 20 exists. The receiving condition determining unit 204 does not determine that the receiving condition is satisfied when the receiving ID does not exist in the temporary privilege database DB2, and does not determine that the receiving condition is satisfied when the receiving ID exists in the temporary privilege database DB2. It is determined that If the user registers as a member without reading the receipt code C310, the benefit management server 20 will not receive the receipt ID, so the receipt condition determination unit 204 will , it is not determined that the receiving conditions are met.

[Temporary Benefit Grant Department]
The provisional benefit granting unit 205 grants receivable points to the user when it is determined that the receiving conditions are satisfied. Giving receivable points means making the receivable points usable. In the first embodiment, reflecting receivable points in the user's point balance stored in the benefit database DB1 corresponds to providing receivable points. Reflecting receivable points means increasing the point balance by the value of receivable points.

The provisional benefit granting unit 205 may grant a provisional benefit using a method according to the type of provisional benefit. For example, when a coupon is generated as a temporary benefit, the temporary benefit granting unit 205 grants the coupon to the user. For example, when electronic money is generated as a temporary benefit, the temporary benefit granting unit 205 increases the user's electronic money balance. For example, when content such as a video is generated as a temporary benefit, the temporary benefit granting unit 205 grants the content to the user. For example, when a token such as a token associated with digital content is generated as a temporary benefit, the temporary benefit granting unit 205 manages the benefit granting system S in cooperation with a distributed ledger such as a blockchain network. Execute the process to transfer the token from the wallet address corresponding to the user to the wallet address corresponding to the user. For example, when information regarding a physical product is generated as a temporary benefit, the temporary benefit provision unit 205 executes processing for delivering the physical product to the user.

In the first embodiment, if the receiving ID received from the member management server 30 exists in the provisional privilege database DB2, it is determined that the receiving condition is satisfied. In this case, the provisional benefit granting unit 205 grants receivable points associated with this receiving ID to the user. For example, the temporary benefit granting unit 205 increases the point balance of the record in the benefit database DB1 in which the member ID included in the member information received from the member management server 30 is stored, by the amount of receivable points to be granted to the user. let

The provisional benefit granting unit 205 does not grant receivable points to the user if it is determined that the receiving conditions are not satisfied. In this case, the user's point balance does not increase. However, if a campaign is being held at the time of membership registration, the user's point balance may increase due to other factors.

[Bonus Grant Department]
The benefit granting unit 206 grants benefits such as points to the user when it is determined that the retail service is used in a receivable state where the user can receive the benefit. In this case, the process itself for awarding points to the user can be performed using a known process. For example, the benefit granting unit 206 may grant points to the user by increasing the point balance associated with the display ID included in the code C10 by the points scheduled to be received. The benefit award unit 206 may immediately award points when using the retail service. Note that the types of benefits may include types of temporary benefits. At this time, the benefit granting unit 206 may grant the benefit by a method according to the type of benefit. Similar to the provisional benefits, the benefits are not limited to points. As examples of other benefits other than points, those exemplified in the explanation of the provisional benefits can also be applied.

[1-3-3. Functions realized by member management server]
The data storage section 300 is mainly realized by the storage section 32. The member registration section 301 is realized mainly by the control section 31.

[Data storage unit]
The data storage unit 300 stores data necessary for point service member management. For example, the data storage unit stores a member database DB3.

FIG. 8 is a diagram showing an example of the member database DB3. The member database DB3 is a database that stores member information regarding members of the point service. For example, member database DB3 stores member ID, password, email address, name, date of birth, address, and telephone number. The member information stored in the member database DB3 may be any information and is not limited to the example shown in FIG. 8.

For example, the member database DB3 may store a card number, display ID, point balance, and point history as member information. In this case, it is assumed that the information is consistent between the member database DB3 and the privilege database DB1. Furthermore, the benefit database DB1 and the membership database DB3 may be combined into one database.

[Member Registration Department]
The member registration unit 301 executes member registration for the point service. Various known processes can be used for the membership registration process itself. For example, upon receiving a membership registration request from the user terminal 50, the membership registration unit 301 creates a new record in the membership database DB3. The member registration unit 301 executes member registration by storing the member ID, password, email address, name, date of birth, address, and telephone number of the user who newly becomes a member in the record. When membership registration is completed, the member registration unit 301 transmits the registration completion notification described in the process of the receiving condition determination unit 204 to the benefit management server 20.

[1-3-4. Functions realized on store terminals]
The data storage section 400 is mainly realized by the storage section 42. The service providing unit 401 and the output unit 402 are mainly realized by the control unit 41.

[Data storage unit]
The data storage unit 400 stores data necessary for providing retail services to users. For example, like the data storage unit 100 of the store server 10, the data storage unit 400 may store a product database and a usage result database. The data storage unit 400 may store product information regarding the product before checkout and a display ID obtained from the code C10 displayed on the point card screen G1 of the point app. The data storage unit 400 may store the card number and point balance associated with this display ID. The data storage unit 400 may store layout data regarding the layout of each of the receipts R2 and R3.

[Service provision department]
The service providing unit 401 provides retail services to users. As explained in the processing of the service providing unit 101 of the store server 10, various known methods can be used to provide the retail service, and the functions of the store terminal 40 mainly include the function of the output unit 402. is different from the conventional one. Therefore, on the retail service side, the functions of the first embodiment can be introduced with minimal modification.

[Output section]
The output unit 402 causes the physical store to output the receiving ID. The output unit 402 causes the output device 47 to output receipts R2 and R3. In the first embodiment, a case will be described in which the store terminal 40 outputs receipts R2 and R3 based on an output request received from the store server 10. The output device 47 may output the receipts R2 and R3 based on some request from each. The output unit 402 may cause the output device 47 to output the receipts R2 and R3 based on a request from the privilege management server 20 instead of a request from the store server 10. The output unit 402 may cause the output device 47 to output the receipts R2 and R3 based on an operation performed from the operation unit 44 instead of a request from each of the store server 10 and the benefit management server 20.

[1-3-5. Functions realized on user terminal]
The data storage section 500 is mainly realized by the storage section 52. The display control unit 501 and the operation reception unit 502 are mainly realized by the control unit 51.

[Data storage]
The data storage unit 500 stores data necessary for using the point service. For example, the data storage unit 500 stores a point app and a display ID.

[Display control section]
The display control unit 501 causes the display unit 55 to display an arbitrary screen. For example, the display control unit 501 causes the display unit 55 to display each of the point card screen G1 in FIG. 2, and the member registration screen G4 and registration completion screen G5 in FIG. Each screen may be displayed using an application other than the point application or a browser.

[Operation reception department]
The operation reception unit 502 accepts any operation. For example, the operation accepting unit 502 accepts operations on each of the point card screen G1 in FIG. 2, and the member registration screen G4 and registration completion screen G5 in FIG.

[1-4. Processing executed by the benefit granting system]
In the first embodiment, as an example of the process executed by the benefit granting system S, there is a physical store usage process executed when a user uses a physical store, and a process in which a user who is not a member of a point service receives a receipt R3. The member registration process that is executed when registering as a member by using this service will be explained.

[Physical store usage processing]
FIG. 9 is a diagram illustrating an example of a physical store usage process executed by the privilege granting system S. The physical store usage process is executed by the control units 11, 21, and 41 operating according to programs stored in the storage units 12, 22, and 42, respectively. Although FIG. 9 describes a case where the user purchases a product with cash, when the user uses electronic payment (cashless payment), payment processing for electronic payment is also executed.

As shown in FIG. 9, the store terminal 40 identifies the operation performed at the physical store (S100). In S100, an operation of reading the barcode of the product with the reading device 46, an operation of reading the code C10 displayed on the point card screen G1 of the point app with the reading device 46, or a checkout operation on the operation unit 44 indicating completion of checkout. will be held.

In S100, when the barcode of the product is read by the reader 46 (S100; Product reading), the store terminal 40 acquires the product code of the product from the barcode (S101), and stores the product name and other information of the product. A product information acquisition process for acquiring information is executed (S102). In FIG. 9, a case will be described in which the store terminal 40 acquires product information by communicating with the store server 10. However, the store terminal 40 acquires product information by communicating with the store server 10. Product information may be acquired from a product database.

In S100, when the code C10 is read by the reading device 46 (S100; code reading), the store terminal 40 acquires the display ID from the code C10 (S103), and exchanges the point balance with the benefit management server 20. A point inquiry process for inquiring is executed (S104). In S104, the store terminal 40 acquires the point balance associated with the display ID from the benefit database DB1 by communicating with the benefit management server 20. The store terminal 40 records the obtained point balance in the storage unit 42. The point balance may be displayed on the display section 45. In the point inquiry process, other information such as a card number may also be acquired.

In S100, when an operation indicating that the checkout is completed is performed on the operation unit 44 (S100; checkout operation), the store terminal 40 determines whether the display ID has been acquired through the process in S103. (S105). In S105, the store terminal 40 determines whether information such as the display ID and point balance is stored in the storage unit 42. That is, the store terminal 40 determines whether the user is a member of the point service.

In S105, if it is determined that the display ID has been acquired (S105; Y), the store terminal 40 communicates with at least one of the store server 10 and the benefit management server 20, and performs accounting processing to complete product accounting. , and a grant process for granting points to the user (S106), the store terminal 40 outputs a receipt R2 that does not include the receipt code C310 (S107), and this process ends. The user receives the product and receipt R2 and leaves the store. The accounting process and grant process in S106 may be the same as conventional processes. The process for outputting the receipt R2 may also be similar to the conventional process.

In S105, if it is determined that the display ID has not been acquired (S105; N), the store terminal 40 communicates with at least one of the store server 10 and the benefit management server 20 to perform accounting processing and generate receivable points. The generation process is executed (S108), the receipt R3 including the receipt code C310 is output (S109), and this process ends. The user receives the product and receipt R3 and leaves the store. The accounting process in S108 may be the same as the conventional process.

In S108, when the checkout process is completed, the store server 10 or the store terminal 40 transmits a usage completion notification including service usage history such as usage amount and product details to the benefit management server 20. The benefit management server 20 generates a receiving ID and receivable points. The privilege management server 20 stores the receiving ID, receivable points, and service usage history in the temporary privilege database DB2. The benefit management server 20 transmits a generation completion notification including the receiving ID and receivable points to the store server 10. Upon receiving the generation completion notification, the store server 10 transmits a request to output the receipt R3 to the store terminal 40. In S109, the store terminal 40 outputs the receipt R3 based on this output request.

[Member registration process]
FIG. 10 is a diagram illustrating an example of a member registration process executed by the privilege granting system S. The member registration process is executed by the control units 21, 31, and 51 operating according to programs stored in the storage units 22, 32, and 52, respectively.

As shown in FIG. 10, the user terminal 50 reads the receipt code C310 of the receipt R3 with the reading unit 56 (S200). The user terminal 50 acquires the receiving ID and the link to the member registration screen G4 from the receiving code C310 (S201), accesses the member management server 30, and displays the member registration screen G4 on the display unit 55. Display it (S202). The member management server 30 may receive the receiving ID from the user terminal 50 in S202 and may hold the receiving ID. The user terminal 50 receives input of member information on the member registration screen G4 (S203). When the user selects button B45, the user terminal 50 transmits a member registration request to the member management server 30 (S204).

Upon receiving the membership registration request (S205), the membership management server 30 executes membership registration of the user (S206). The member management server 30 transmits a registration completion notification including the member ID of the user who has completed membership registration and the receiving ID received from the user terminal 50 to the privilege management server 20 (S207). Upon receiving the registration completion notification (S208), the benefit management server 20 creates a new record in the benefit database DB1 (S209).

The member management server 30 refers to the temporary privilege database DB and determines whether or not the receipt ID received from the member management server 30 exists (S210). If it is determined that the receiving ID exists (S210; Y), the benefit management server 20 grants receivable points to the user who has registered as a member (S211), and this process ends. If it is not determined that the receiving ID exists (S210; N), the process ends without executing the process of S211.

The privilege granting system S of this embodiment generates receivable points when it is determined that the retail service is used in a non-receivable state. The benefit granting system S grants receivable points to the user when it is determined that the receiving conditions are satisfied after using the retail service. As a result, even if the user uses the retail service in a state where the item cannot be received, points that can be received are given after the fact, which increases convenience for the user. For example, even if a user is not a member of a point service and cannot receive points, receivable points will be awarded after the fact, so it is possible for users who are not members of a point service to become members of a point service. The appeal effect will be increased. When other conditions are set as receiving conditions, the effect of appealing to users to satisfy the other conditions increases. From a retailer's point of view, if a store becomes a member of the point service, the highly convenient system will increase the effect of attracting customers, which will generate profits for the retailer.

Further, the privilege awarding system S awards points to the user when it is determined that the retail service is used in a receivable state. The privilege granting system S does not generate receivable points when it is determined that the retail service is used in the receivable state. As a result, unnecessary receivable points are not generated, so the processing load on the privilege management server 20 can be reduced, and the memory consumption of the temporary privilege database DB2 can be suppressed.

Further, the privilege granting system S determines whether the retail service is used in a state where the user is not a member of the point service by determining whether the retail service is used in a state where the user is not a member of the point service. The privilege granting system S determines whether the receiving conditions are satisfied by determining whether the user has become a member of a point service. This allows users to receive receivable points when they become a member of a point service, increasing the appeal of becoming a member of a point service to users who are not members of a point service. . As a result, the number of members of the point service can be effectively increased.

Further, the benefit granting system S determines whether the receiving condition is satisfied by determining whether the receiving ID output at the physical store has been acquired from the user terminal 50. This makes it possible to grant receivable points to a user by using a receivable ID that, in principle, is known only to users who have visited a physical store. As a result, it is possible to prevent fraud in which a third party who does not use the physical store receives receivable points without permission.

Additionally, the benefit granting system S determines whether the retail service is used in a state where the user is unable to receive the item by determining whether the retail service is used in a state where the user does not present the point card at the physical store. . Thereby, receivable points can be generated after reliably determining whether the user is a member of a point service using a point card.

In addition, if it is determined that the retail service was used in a state where receipt is not possible, the benefit granting system S causes the physical store to output the receipt R3 including the receipt ID, thereby causing the physical store to output the receipt ID. . As a result, the usage history information I30 and the point information I31 are printed on the same receipt R3 instead of on separate receipts, improving convenience for the user. Since the user only needs to take home one receipt R3, it becomes difficult for the user to lose the receipt ID. Further, when the retail service is used in the receipt ready state, the privilege granting system S causes the physical store to output a receipt R2 which has a different layout from the receipt R3 and does not include the receipt ID. This saves space on the receipt R2 and saves receipt paper. Since the receipt R2 is shorter, user convenience is also improved. By making the layouts of the receipts R2 and R3 different from each other, it becomes easier for the user to understand whether the receipt ID has been output or not.

Further, the privilege granting system S outputs the receipt ID at the physical store by causing the receipt R3 on which the receipt code C310 including the receipt ID is formed to be output at the physical store. The benefit granting system S determines whether the receiving ID included in the receiving code C310 has been acquired from the user terminal 50. As a result, the receiving ID can be obtained by a simple operation such as reading the receiving code C310 with the reading unit 56 of the user terminal 50, thereby increasing convenience for the user. When a user manually inputs the receipt ID from the operation unit 54 of the user terminal 50, there is a possibility that an input error may occur, but by using the receipt code C310, such input errors can be avoided. It can be prevented. Furthermore, when a link to the membership registration screen G4 is included in the receiving code C310, it becomes easier for users who are not members of the point service to access the membership registration screen G4, thereby increasing convenience for the users. It is also possible to effectively increase the number of points service members.

[2. Second embodiment]
For example, even if a user is a member of a point service, if the user does not know that the physical store is a member store of the point service, the user may not use the physical store without presenting the point card screen G1. be. For example, if the user is too lazy to start the point app or forgets the user terminal 50, the user may use the physical store without presenting the point card screen G1. These points also apply when the user uses a physical point card.

In the conventional technology, if the user does not present the point card screen G1 at the physical store, no points will be awarded even if the user uses the physical store. When a user who did not present the point card screen G1 visits the physical store again and presents a receipt, it is also possible to award points after the fact through the operation of the physical store. However, in this case, the burden on the physical store increases. Therefore, in the second embodiment, even if a user who is a member of a point service does not present the point card screen G1 at a physical store, points will be awarded after the fact using the receipt R3. explain.

FIG. 11 is a diagram illustrating an example of the flow of receiving receivable points in the second embodiment. In the second embodiment, a case will be exemplified in which a user uses a point app to receive receivable points. For example, when the user selects the link L11 "Receive receivable points" displayed on the point card screen G1, the reading section 56 is activated and the reading screen G6 is displayed on the display section 55.

The captured image I60 generated by the reading section 56 is displayed on the reading screen G6. When the user terminal 50 reads the receipt code C310 of the receipt R3, the user terminal 50 acquires the receipt ID from the receipt code C310. The receipt code C310 also includes a link to the member registration screen G4, but in the second embodiment, the user has already registered with the point service and has logged in to the point service from the point app. Therefore, the member registration screen G4 is not displayed. The user terminal 50 discards the link to the member registration screen G4 and transmits the receiving ID to the privilege management server 20.

When the benefit management server 20 receives the receiving ID, the receiving condition determining unit 204 refers to the provisional privilege database DB2 and determines whether the received receiving ID exists or not, thereby determining whether the receiving condition is satisfied. Determine whether or not it has been done. If it is determined that the receiving ID exists in the temporary privilege database DB2, the temporary benefit granting unit 205 grants the receivable points associated with the receiving ID to the logged-in user. The provisional benefit granting unit 205 refers to the benefit database DB1 and increases the point balance associated with the member ID of the user by the receivable points. The provisional benefit granting unit 205 deletes the record corresponding to the granted receivable points from the benefit database DB1.

When receivable points are awarded, an assignment completion screen G7 is displayed on the display unit 55. For example, the grant completion screen G7 displays the receivable points granted to the user and the point balance after receiving the receivable points. When the user selects button B70, the screen returns to point card screen G1. As shown in the point card screen G1 at the bottom right of FIG. 11, the receivable points received by the user are reflected in the point balance. The receivable points may be reflected in the point balance after a certain amount of time has passed.

Note that the user terminal 50 may transmit the receiving ID to the member management server 30. In this case, the member management server 30 transfers the member ID of the logged-in user and the receiving ID received from the user terminal 50 to the privilege management server 20. When the privilege management server 20 receives the member ID and receipt ID from the member management server 30, the receipt condition determining unit 204 and the provisional privilege granting unit 205 execute the same process as above, and allow the logged-in user to receive the receipt. Assign possible points.

The benefit granting system S of the second embodiment can grant receivable points after the fact to users who are members of a point service. As a result, even if a user who is a member of a point service does not present the point card screen G1 at a physical store, receivable points will be awarded after the fact, increasing convenience for the user. Since there is no need for special operations at physical stores, the burden on physical stores can also be reduced.

[3. Third embodiment]
In the first and second embodiments, the scenario in which the user uses a retail service at a physical store is taken as an example, but the benefit granting system S is also applicable to a scenario in which the user uses an online service. It is possible. For example, even when a user uses an online shopping service instead of a retail service, the same processing as in the first and second embodiments can be executed. In the third embodiment, descriptions of the same configurations as those in the first and second embodiments will be omitted.

In the third embodiment, an online shopping service and a point service cooperate with each other. However, in order to receive points for shopping in the online shopping service, the user needs to associate the member ID of the online shopping service with the member ID of the point service. Once these associations are made, the user will be able to receive points according to the amount spent on the online shopping service.

In the third embodiment, the user does not shop at a physical store but at a virtual store on an online shopping service. The store server 10 is a virtual store server. The store terminal 40 is a computer operated by a virtual store operator. If an online shopping mall with multiple stores is provided, the store server 10 may be a server computer of an administrator of the online shopping mall.

FIG. 12 is a diagram illustrating an example of the flow of receiving receivable points in the third embodiment. As shown in FIG. 12, when the user operates the user terminal 50 to access the website of the online shopping service, the top screen G8 of the online shopping service is displayed on the display unit 55. Here, it is assumed that the user is a member of the online shopping service and logs into the online shopping service.

When the user selects and purchases a product from the top screen G8, a purchase completion screen G9 is displayed on the display section 55. A message such as an e-mail containing the same content as the purchase completion screen G9 may be sent to the user. On the purchase completion screen G9, a link L90 to the membership registration screen G4 is displayed together with the purchase details of the product and the points that can be received. The flow of generating receivable points may be the same as in the first embodiment and the second embodiment.

In the third embodiment, it is assumed that the link L90 includes a receiving ID. When the user selects the link L90, a member registration screen G4 and a registration completion screen G5 similar to those shown in FIG. 4 are displayed on the display section 55. The flow of member registration may be the same as in the first embodiment. Note that the receiving ID may be displayed on the purchase completion screen G9, or may be included in the e-mail sent to the user after purchasing the product. In this case, the user may manually input the receiving ID at the time of member registration for the point service or afterward.

When the user completes membership registration for the point service, receivable points are awarded to the user. The user's point card shall also be automatically registered in the online shopping service. As shown in FIG. 12, when the user displays the top screen G8 again, the user's point balance becomes 65P of the receivable points displayed on the purchase completion screen G9. From then on, when users use the online shopping service, they will be awarded points based on the amount spent.

The privilege granting system S of the third embodiment is more convenient for users of the online shopping service for the same reason as the privilege granting system S of the first embodiment. The appeal of becoming a member of a point service also increases for users who are not members of a point service. In addition, in the third embodiment, even if the user orders a product as a guest user without logging into the online shopping service, receivable points will be awarded after the fact in the same way as in the second embodiment. It is also possible to do so.

Although the third embodiment describes the case where the user is a member of an online shopping service, the same method as in the third embodiment can also be applied when the user is a member of a retail service provided at a physical store. Processing may be performed. In this case, a process combining the first embodiment and the third embodiment and a process combining the second embodiment and the third embodiment may be executed.

First, processing that combines the first embodiment and the third embodiment will be described. For example, assume that the user is a "AAA member" who is a member of a retail service provided by a physical store "AAA Shop." For example, when a user presents their "AAA Member" point card and visits a physical store, they can receive "AAA Points," which are points for retail services, or use members-only services such as home delivery services or discount services. I can do it. For example, when a user becomes a "XXX member" who is a member of a point service, he or she can receive "XXX points" in addition to the "AAA points" of the retail service.

For example, assume that the user is a "AAA member" but not a "XXX member." In this case as well, the user cannot receive "XXX points", so this corresponds to a non-receivable state. When a user presents his "AAA member" point card and uses the physical store, points for receipt are generated. These receiving points may be associated with the member ID of "AAA member" instead of the receiving ID. When a user registers as a "XXX member," by inputting his or her own "AAA member" member ID, the benefit management server 20 can specify the receivable points to be given to this user.

Similarly, when the second embodiment and the third embodiment are combined, if the user presents the "AAA member" point card at a physical store but does not present the "XXX member" point card, , Receivable points may be associated with the member ID of "AAA member". If the user inputs the member ID of "AAA member" from the "XXX member" website, etc., the user can subsequently receive the receivable points associated with the member ID.

In addition, if the member ID of "AAA member" and the member ID of "XXX member" are linked to each other, the user does not have to present the "XXX member" point card at the physical store. , "XXX points" may be automatically granted by presenting a "AAA member" point card. On the contrary, even if the user does not present the "AAA member" point card at a physical store, if the user presents the "XXX member" point card, "AAA member" points will be automatically awarded. It's okay.

[4. Fourth embodiment]
For example, some online services offer a higher point return rate if the user satisfies certain conditions. In the fourth embodiment, a case will be described in which receivable points are generated every time a user uses an online service until a specific condition is met in such an online service. If a specific condition is met after the fact, it is determined that the receiving condition is satisfied, and the user can receive the receivable points generated from past usage. In the fourth embodiment, descriptions of configurations similar to those of the first to third embodiments will be omitted.

In the fourth embodiment, when a user becomes a member of an online shopping service, he or she automatically becomes a member of a point service. Furthermore, in the fourth embodiment, it is assumed that an electronic commerce company that provides online shopping services and a point business that provides point services are the same. It can also be said that there is a concept of one large service membership that includes online shopping services and point services. It is assumed that the user is a member of this one large service.

For example, operators of online shopping services and point services are affiliated with specific card companies that issue credit cards. Hereinafter, this card company will be referred to as an affiliated card company. A credit card issued by an affiliated card company is called an affiliated credit card. Card companies other than affiliated card companies are referred to as other companies. A credit card issued by another company is called a third-party credit card.

In the fourth embodiment, when a user uses an affiliated credit card for an online shopping service, the point return rate is higher than when a user uses another company's credit card. Affiliated card companies use banner advertisements, campaigns, etc. to appeal to users who do not have an affiliated credit card to issue affiliated credit cards based on the high point return rate of online shopping services. . Issuing an affiliated credit card corresponds to becoming a member of a credit card service provided by an affiliated card company (that is, joining an affiliated credit card).

In this regard, even if a user who does not have an affiliated credit card is issued with an affiliated credit card, this will only increase the return rate of points for future purchases, so this is not a sufficient promotional effect. A certain amount of points may be given to users as a benefit when an affiliated credit card is issued, but since various card companies offer similar benefits, this is not a sufficient promotional effect.

Therefore, the benefit granting system S of the fourth embodiment utilizes the processes of the first to third embodiments when a user who does not have an affiliated credit card makes a purchase using an online shopping service, and uses the affiliated credit card. Generate the receivable points that you would have received if you had the card. When a user issues an affiliated credit card, they can receive receivable points retroactively to past purchases. This increases the appeal of affiliated credit cards to users.

FIG. 13 is a diagram showing an example of a chronological flow until a user issues an affiliated credit card. For example, assume that the user became a member of an online shopping service on February 1, 2022. As mentioned above, the user automatically becomes a member of the point service. For example, assume that the point balance immediately after membership registration is 0 points. The return rate for other companies' credit cards is 1%, and the return rate for affiliated credit cards is 1.5%.

For example, assume that the user made a purchase of 5,000 yen on February 9, 2022 using another company's credit card. As in the first embodiment, points may be awarded after a certain amount of time has passed, but here it is assumed that points are awarded immediately. The amount spent on this purchase is 5,000 yen, and since the return rate for other companies' credit cards is 1%, 50 points are awarded. The point balance will range from 0 points to 50 points.

For example, assuming that the user used an affiliated credit card for shopping on February 9, 2022, the return rate of the affiliated credit card is 1.5%, so 75 points would have been awarded. Therefore, 25 receivable points are generated, which is the difference between the 75 points that should have been given and the 50 points that were actually given. The 25 receivable points are stored in the provisional benefit database DB2 in association with the user's member ID.

Thereafter, receivable points are generated for purchases made until the user issues an affiliated credit card. In the example of FIG. 13, 60 receivable points are generated for a purchase worth 12,000 yen on February 16, 2022. For purchases worth 6,000 yen on February 21, 2022, 30 receivable points will be generated. The receivable points are generated and added in increments of 0.5%, which is the difference in the return rate. Points equivalent to 1%, which is the return rate of other companies' credit cards, shall be immediately granted and added to the point balance.

For example, assume that a user issues an affiliated credit card on February 25, 2022. In this case, as a benefit for issuing the affiliated credit card, the user is given 115 points, which is the total value of the receivable points generated in the past. That is, points are awarded retroactively so that the user can receive points under the same conditions as if they had used an affiliated credit card for past purchases.

The functional block diagram of the fourth embodiment is similar to the first to third embodiments. However, some functions are different from the first to third embodiments. For example, the temporary benefit generation unit 202 associates a member ID that can identify a user in an online shopping service and a point service with the generated receivable points and registers them in the temporary benefit database DB2. The method of generating receivable points is the same as in the third embodiment, but in the fourth embodiment, since the user is a member of an online shopping service and a point service, the method of generating receivable points is not the receivable ID but the member ID. Receivable points are associated with.

The receiving condition determination unit 204 determines whether the receiving condition is satisfied by determining whether the user has become a member of a credit card service. Issuing an affiliated credit card corresponds to becoming a member of a credit card service. In the fourth embodiment, a credit card service corresponds to another service. In the fourth embodiment, it is assumed that the user issues an affiliated credit card after inputting the member ID of the online shopping service and point service. The receiving condition determining unit 204 receives the member ID of the user who issued the affiliated credit card from the server computer of the affiliated card company. The receiving condition determining unit 204 determines whether the user has become a member of a credit card service based on this member ID.

When it is determined that the user has become a member of a credit card service, the provisional benefit granting unit 205 grants receivable points associated with the member ID to the user. Although it differs from the first to third embodiments in that receivable points are given that are associated with the member ID rather than the receiving ID, the method of awarding receivable points itself is different from the first to third embodiments. This is similar to the embodiment.

The benefit granting system S of the fourth embodiment grants the user receivable points associated with the member ID when it is determined that the user has become a member of a credit card service. This increases the appeal to become a member of the credit card service. From the user's point of view, the points that can be received are retroactively awarded, increasing convenience.

[5. Modified example]
Note that the present disclosure is not limited to the first to fourth embodiments described above. Changes can be made as appropriate without departing from the spirit of the present disclosure.

FIG. 14 is a diagram illustrating an example of functional blocks in a modified example. The first restriction section 207, the second restriction section 208, the third restriction section 209, the fourth restriction section 210, the first presentation section 211, the second presentation section 212, and the third presentation section 213 mainly realize the control section 21. be done.

[5-1. Modification example 1]
For example, some users may throw away the receipt R3 described in the first embodiment in a store's unnecessary receipt bin or trash can. A malicious third party may obtain a large number of unspecified receipts R3 from a store or other location and attempt to fraudulently receive receivable points from his or her own user terminal 50. Such fraudulent acts go against the purpose of the point service, and are also undesirable in terms of crime prevention at stores or other locations.

Therefore, in order to prevent fraudulent acts by third parties, certain restrictions may be placed on the points that can be received. In Modification 1, the provisional benefit generation unit 202 sets an expiration date to the generated receivable points. The expiration date is the period during which the receivable points are valid. The expiration date can also be referred to as the deadline for receiving receivable points. The expiration date is a certain period of time after the receivable points are generated.

Hereinafter, the length of the period from when receivable points are generated until the expiration date will be referred to as the length of the expiration date. In Modification 1, a case will be described in which the length of the expiration date is two weeks, but the length of the expiration date may be any length. For example, the length of the expiration date may be from several minutes to several days, or from one week to half a year. The length of the expiration date may be fixed or variable. For example, the length of the expiration date may vary depending on the type or area of the physical store.

For example, the length of the expiration date may vary depending on the usage amount. If the length of the expiry date is shortened as the amount spent is large, the deterrent effect against fraudulent activity will increase. However, since the convenience for the user decreases, the expiration date may be set to be longer as the usage amount increases. Since there is a trade-off relationship between deterrence of fraud and convenience for users, the length of the expiration date will be set according to the requests of the administrator of the reward granting system S, the person in charge of the physical store, etc. Just do it.

It is assumed that the temporary privilege database DB2 of Modification 1 also stores the expiration date of receivable points. For example, upon generating receivable points, the temporary benefit generation unit 202 determines the expiration date set for the receivable points. The temporary benefit generation unit 202 may determine the expiration date before generating receivable points. For example, the temporary benefit generation unit 202 determines, as the expiration date, two weeks after the current date and time when executing the processing for determining the expiration date. The current date and time may be acquired using a real-time clock, a GPS signal, or the like. The temporary benefit generation unit 202 associates the receipt ID, expiration date, receivable points, and service usage history with each other and stores them in the temporary benefit database DB2.

The receiving condition determination unit 204 determines whether the receiving condition is satisfied by determining whether the receiving ID is acquired from the user terminal 50 within the expiration date. The receiving condition determining unit 204 refers to the provisional privilege database DB2 and obtains the expiration date associated with the receiving ID. The receiving condition determining unit 204 determines whether the acquired expiration date has passed based on the current date and time. If the current date and time is after the expiration date, the receiving condition determination unit 204 determines that the expiration date has passed. If the expiration date has passed, no receivable points will be awarded even if the receiving ID is stored in the temporary privilege database DB2.

Note that the record of receivable points whose expiration date has passed may be deleted from the provisional privilege database DB2. In this case, since the receiving ID for which the expiration date has passed no longer exists in the provisional award database DB2, even if the receiving ID for the receivable points for which the expiration date has passed is acquired, the receivable points will not be granted. Whether or not the expiration date of the receivable points stored in the provisional privilege database DB2 has passed may be determined periodically by night batch processing or the like. Receivable points whose expiration date has passed may not be deleted from the provisional benefit database DB2, but may be managed using a flag or the like indicating whether or not the expiration date has passed.

The privilege granting system S of the first modification determines whether the receiving condition is satisfied by determining whether the receiving ID is acquired from the user terminal 50 within the expiration date. This acts as a deterrent against malicious third parties, thereby preventing fraudulent acts. Even if the purpose is not to prevent fraudulent acts, if the user throws away the receipt R3, it is possible to prevent receivable points that are not received from remaining in the provisional privilege database DB2 forever.

[5-2. Modification 2]
For example, the method for preventing fraudulent acts by a malicious third party is not limited to the method described in Modification 1. In a second modification, a case will be described in which an upper limit is set on the receivable points that can be received with a certain member ID during a certain period. Even if a malicious third party fraudulently obtains a large amount of receipts R3, the upper limit described in Modification 2 prevents the malicious third party from receiving more than a certain level of receivable points. In Modification 2, this upper limit is used to deter fraudulent acts. A person to whom a member ID has been issued is recognized as a user by the system, whether it is a legitimate user or a malicious third party, so a place where the word "user" is written does not necessarily mean a legitimate user.

In the second modification, it is assumed that the point history stored in the benefit database DB1 also includes a history of receivable points granted to a certain member ID. When the provisional benefit granting unit 205 grants receivable points to a certain user, the provisional benefit granting unit 205 stores the receivable points that have been granted, the grant date and time of the receivable points, and the grant date and time of the receivable points as a point history associated with the member ID of this user. is stored in the privilege database DB1. The grant date and time is the current date and time when the process of granting receivable points was executed.

The privilege granting system S of the second modification includes a first restriction section 207. The first restriction unit 207 determines whether the receivable points granted to the user within a predetermined period have reached the upper limit. The predetermined period may be the entire past period, but in the second modification, it is assumed to be a part of the most recent period. In Modification 2, the predetermined period is assumed to be the most recent week, but the length of the predetermined period may be any length. For example, the predetermined period may be approximately several hours to several days, or may be longer than one week.

The upper limit is information equivalent to a threshold value for restricting the granting of receivable points. For example, the upper limit is the upper limit number of times that receivable points can be awarded. For example, the upper limit is the upper limit number of points to which receivable points can be given. In the second modification, a case will be described in which both the upper limit number of times and the upper limit number of points are used, but only either the upper limit number of times or the upper limit number of points may be used.

For example, when it is determined that a certain user satisfies the receiving conditions, the first restriction unit 207 refers to the benefit database DB1 and acquires the point history of this user. The first restriction unit 207 determines whether the upper limit has been reached based on the acquired point history. For example, the first restriction unit 207 totals the number of times receivable points are given to a certain user in the past week and the total number of points based on the point history of the certain user. The first restriction unit 207 determines whether the number of times of granting has reached the upper limit number of times. The first restriction unit 207 determines whether the total number of points has reached the upper limit number of points.

The first restriction unit 207 restricts the granting of receivable points to the user when it is determined that the upper limit has been reached. The restriction here means that receivable points are not granted to the user. In other words, prohibiting the granting of receivable points to a user corresponds to a restriction. For example, the first restriction unit 207 restricts the granting of receivable points to the user when it is determined that the number of times of granting has reached the upper limit number of times. For example, the first restriction unit 207 restricts the granting of receivable points to the user when it is determined that the number of granted points has reached the upper limit number of points. The first restriction unit 207 does not restrict the granting of receivable points to the user if it is not determined that the upper limit has been reached.

The privilege granting system S of the second modification restricts the granting of receivable points to the user when it is determined that the receivable points granted to the user within a predetermined period have reached the upper limit. . This acts as a deterrent against malicious third parties, thereby preventing fraudulent acts.

[5-3. Modification 3]
For example, the method for preventing fraudulent acts by a malicious third party is not limited to the method described in Modification 1-2. In a third modification, a case will be described in which if the physical store that outputs the receipt R3 is in an unnatural positional relationship with the place where the user is usually present, the receivable points are not granted.

For example, assume that a malicious third party illegally obtained a large amount of receipts R3 from a nearby brick-and-mortar store and sold them to another distant third party using a resale site or the like. Since the other third party is located far away from the physical store, even if the third party reads the receiving code C310, no receivable points will be given to the third party. In the third modification, the locational relationship between the physical store where the receipt R3 was output and the person to whom the receivable points are to be given is used to deter fraudulent acts.

In the third modification, it is assumed that the service usage history stored in the temporary privilege database DB2 includes location information regarding the location of the physical store. The location information of the physical store may be stored in another database instead of the service usage history. In this case, it is assumed that the service usage history includes the store ID of the actual store. Location information stored in another database may be acquired using this store ID. Various types of information can be used as the location information itself, and for example, it may be latitude and longitude information, coordinate information, address, or postal code.

The privilege granting system S includes a second restriction section 208. The second restriction unit 208 determines whether the first location related to the physical store and the second location related to the user correspond. The first location is a location where a physical store is located. The second location is a location associated with the user. For example, the second location is the address registered by the user in the point service, the center of a plurality of physical stores where the user used the retail service, or the location of the user terminal 50. The location of the user terminal 50 may be obtained by GNSS such as GPS, or may be obtained using a mobile base station or an access point.

The first location and the second location correspond to each other when the distance between the first location and the second location falls within a certain range. The second restriction unit 208 acquires first location information regarding the first location and second location information regarding the second location. The second restriction unit 208 calculates the distance between the first location and the second location based on the first location information and the second location information. The second restriction unit 208 determines whether this distance is greater than or equal to a threshold value. The second restriction unit 208 determines that the first location and the second location do not correspond when it is determined that this distance is equal to or greater than the threshold, and when it is determined that this distance is less than the threshold, the second restriction section 208 determines that the first location and the second location do not correspond. It is determined that the first location and the second location correspond.

The second restriction unit 208 restricts the granting of receivable points to the user when it is not determined that the first location and the second location correspond. The meaning of the restriction is as explained in the second modification. The second restriction unit 208 does not restrict the granting of receivable points to the user when it is determined that the first location and the second location correspond.

The benefit granting system S of the third modification restricts the granting of receivable points to the user when it is not determined that the first location related to the physical store and the second location related to the user correspond. This acts as a deterrent against malicious third parties, thereby preventing fraudulent acts.

[5-4. Modification example 4]
For example, the method for preventing fraudulent acts by a malicious third party is not limited to the method described in Modification 1-3. In modification example 4, when a user wants to receive receivable points, the relationship between the service usage history associated with the receivable points and the service usage history of the receivable points granted in the past is inconsistent. A case will be explained in which, if it is natural, it would be restricted not to give receivable points.

For example, suppose that a malicious third party obtains a large number of receipts R3 from an unnecessary receipt cabinet at a nearby physical store. The third party attempts to receive receivable points one after another using a large number of receipts R3 output from the same physical store. It is unnatural because it would be hard for a legitimate user to think of something like this. For example, it would be unnatural for a legitimate user to try to receive receivable points one after another using multiple receipts R3 on which details of the same product are printed. Therefore, in the fourth modification, a deterrent against fraudulent activity is provided based on the service usage history at the time the receipt R3 was output.

In the fourth modification, even if the receivable points stored in the provisional privilege database DB2 are awarded, the record corresponding to the receivable points is not deleted. Instead, provisional award database DB2 stores information indicating whether or not receivable points have been assigned. When receivable points are assigned, the value of the assigned information changes to indicate that receivable points have been assigned.

The privilege granting system S includes a third restriction section 209. When a receiving ID is acquired from the user terminal 50, the third restriction unit 209 determines whether the usage history of the service corresponding to the acquired receiving ID is valid. The valid usage history means that the service usage history satisfies predetermined conditions. Any condition can be set as this condition. In the fourth modification, the conditions determined based on the past service usage history and the current service usage history are exemplified, but other conditions may be used. For example, the condition may be determined based on the user's attributes and the current service usage history.

For example, the third restriction unit 209 determines whether or not the service is legitimate based on a certain user's past service usage history and this user's current service usage history. The third restriction unit 209 determines whether the number of times receivable points are consecutively given for receipt R3 from the same physical store is equal to or greater than a threshold value. For example, the third restriction unit 209 may determine whether the number of times receivable points are consecutively given on receipt R3 on which details of the same product are printed is equal to or greater than a threshold value. The third restriction unit 209 does not determine that the process is valid when these counts are determined to be equal to or greater than the threshold value, and determines that the process is valid when it is determined that these counts are less than the threshold value. do.

The third restriction unit 209 restricts the granting of receivable points to the user when the usage history is not determined to be valid. The meaning of the restriction is as explained in the second modification. For example, if the usage history is determined to be valid, the third restriction unit 209 does not restrict the granting of receivable points to the user.

The benefit granting system S of the fourth modification provides that receivable points are granted to the user when the usage history of the service corresponding to the receiving ID acquired from the user terminal 50 is not determined to be valid. Restrict. This acts as a deterrent against malicious third parties, thereby preventing fraudulent acts.

[5-5. Modification 5]
For example, methods for preventing fraudulent acts by malicious third parties are not limited to the methods described in Modifications 1 to 4. In modification example 5, when a certain user attempts to receive receivable points, if the user information registered in the retail service and the user information registered in the point service do not match, the receivable points will not be accepted. A case of restricting points from being awarded will be explained.

In modification 5, it is assumed that the user is a member of a retail service. Users also register as members for retail services. When a user shops at a physical store, the user can accumulate both points unique to the retail service and points from the point service. This point is similar to the example described at the end of the third embodiment. Assuming that the user is a member of a retail service but not a member of a point service, similar to the first embodiment, if the user becomes a member of a point service, the receivable points will be calculated after the fact. Can be granted. If the user forgets to present the point card, receivable points can be awarded after the fact in the same manner as in the second embodiment.

In modification 5, the data storage unit 100 of the store server 10 stores a member database regarding members of a retail service. This member database stores user information such as addresses and names registered by users in the retail service. When an authorized user reads the receipt code C310 of the receipt R3, since the person who made the purchase indicated by this receipt R3 is the same person who is trying to receive the receivable points, the user information of the retail service is read. The user information registered in the point service matches.

On the other hand, if a malicious third party reads the receipt code C310 of receipt R3, the person who made the purchase indicated by this receipt R3 is different from the person who is trying to receive the receivable points. The user information of the specified retail service and the user information registered in the point service do not match. Therefore, in the fifth modification, if these user information items do not match, receivable points are not granted, thereby providing a deterrent against fraudulent acts.

It is assumed that the service usage history of the provisional privilege database DB2 also includes the user's member ID in the retail service. The benefit management server 20 can specify which member of the retail service has used the physical store based on this member ID. The receiving condition determining unit 204 determines whether a receiving ID has been acquired from the user terminal 50 that has logged into a point service different from the retail service. This point is similar to the first to third embodiments. The privilege granting system S of the third modification includes a fourth restriction section 210. The fourth restriction unit 210 determines whether the first membership information of the user in the retail service and the second membership information of the user in the point service match.

The comparison target by the fourth restriction unit 210 may be only one item of the first member information and the second member information, or may be a plurality of items. The items to be compared may be any items and are not limited to those exemplified in the first embodiment and the like. For example, the fourth restriction unit 210 may use other items such as a credit card number or an electronic money ID as a comparison target. For the first member information and the second member information to match, a complete match may be required, or a partial match may be required.

The fourth restriction unit 210 restricts the granting of receivable points to the user when it is determined that the first member information and the second member information do not match. The meaning of the restriction is as explained in the third modification. The fourth restriction unit 210 does not restrict the provision of receivable points to the user when it is determined that the first member information and the second member information match.

The benefit granting system S of modification 5 grants receivable points to the user when it is determined that the user's first member information in the retail service and the user's second member information in the point service do not match. limit what can be done. As a result, even if a malicious third party pretends to be a legitimate user and attempts to receive receivable points, the names and other information will not match, so fraudulent activity can be prevented.

[5-6. Modification 6]
For example, in the example of the fourth embodiment, receivable points may be presented in advance to a user who has not been issued an affiliated credit card. Although the fourth embodiment did not explain the configuration for presenting receivable points, if the user knows the mechanism of the fourth embodiment itself, the appealing effect of issuing an affiliated credit card can be obtained. Therefore, even without the configuration of Modification Example 6, the appeal effect described in the fourth embodiment can be obtained, but with the configuration of Modification Example 6, a stronger appeal effect can be obtained.

FIG. 15 is a diagram illustrating an example of a screen displayed in Modification 6. The privilege granting system S includes a first presentation section 211. The first presentation unit 211 presents receivable points to the user before the user becomes a member of another service. In the example of FIG. 15, when the link L80 on the top screen G8 of the online shopping service is selected, the first presentation unit 211 displays a point management screen G10 showing receivable points associated with the user's member ID. By displaying the points on the section 55, the receivable points are presented to the user.

Since the first presentation unit 211 is realized by the benefit management server 20, the first presentation unit 211 transmits the receivable points by transmitting data for displaying the point management screen G10 to the user terminal 50. is presented to the user. For example, when the user selects the link L100 on the point management screen G10, the user is connected to the website of the affiliated card company. Users issue affiliated credit cards from this website. The flow of issuing the affiliated credit card itself may be a known flow. The process by which the benefit management server 20 detects the issuance of an affiliated credit card is the same as described in the fourth embodiment.

Note that the first presentation unit 211 may present the receivable points to the user using any other screen other than the point management screen G10. Further, the first presenting unit 211 may present the receivable points using any other medium. For example, the first presentation unit 211 may present the receivable points using e-mail, a message from a message app, SNS, SMS, a banner advertisement, a receipt from a physical store, or voice. This point also applies to a second presentation section 212 and a third presentation section 213, which will be described later.

The benefit granting system S of the sixth modification presents receivable points to the user before the user becomes a member of a credit card service. This makes it possible to more strongly appeal to users to become members of the credit card service.

[5-7. Modification 7]
For example, in Modification 6, the privilege granting system S is capable of supporting a plurality of services in addition to the online shopping service. That is, benefits related to the affiliated credit card may be obtained through other services than the online shopping service. In modification 6, the point return rate is increased when an affiliated credit card is used not only for online shopping services but also for electric power services, travel reservation services, and communication services.

The provisional benefit granting unit 205 of Modified Example 7 grants receivable points for each of a plurality of services to the user when it is determined that the receiving conditions are satisfied. For example, when the user issues an affiliated credit card, the provisional benefit granting unit 205 may receive receivable points generated when using four services in the past, such as an online shopping service, an electric power service, a travel reservation service, and a communication service. Add up. The provisional benefit granting unit 205 may grant the total receivable points to the user.

As a method for generating receivable points when each service is used, the same process as in the fourth embodiment may be used. When a user uses each of a plurality of services, the provisional benefit generation unit 202 generates receivable points according to the usage details of the service, and associates the points with the user's member ID to store them in a provisional benefit database. Store in DB2. The service usage history of the temporary privilege database DB2 may include information that allows identification of the service used by the user.

Although the process of the provisional benefit granting unit 205 differs from the fourth embodiment in that it adds up receivable points for a plurality of services, the method of granting receivable points itself is the same as in the fourth embodiment. For example, if the receivable points for online shopping service, electricity service, travel reservation service, and communication service are 1420 points, 2580 points, 3000 points, and 1512 points, respectively, the provisional benefit granting unit 205 determines that the affiliated credit card is When issued, the total value of 7512 points will be given to the user, going back to past usage of these four services.

The privilege granting system S of Modification 7 grants receivable points for each of a plurality of services to the user when it is determined that the receiving conditions are satisfied. This makes it possible to more strongly appeal to users to become members of the credit card service. Users can also receive more receivable points, which increases convenience.

[5-8. Modification 8]
For example, even when a plurality of services exist as in Modification 7, receivable points that will be given when the user issues an affiliated credit card may be presented as in Modification 6. The privilege granting system S of modification 8 includes a second presentation section 212. The second presentation unit 212 presents the total receivable points for each of the plurality of services and the receivable points for each service to the user. In modification 8, similarly to modification 6, it is assumed that the point management screen G10 is presented to the user.

FIG. 16 is a diagram showing an example of the point management screen G10 displayed in Modification 8. As shown in FIG. 16, the point management screen G10 displays the total receivable points generated when using four services in the past, such as online shopping service, electricity service, travel reservation service, and communication service, as well as the points for each individual service. Individual receivable points are displayed. In the example of FIG. 16, the number of points illustrated in Modification 7 is displayed.

For example, when presenting the point management screen G10 to a certain user, the second presentation unit 212 refers to the temporary benefit database DB2 and acquires the receivable points and service usage history associated with the member ID of this user. do. Based on this information, the second presentation unit 212 totals the receivable points for each service and calculates the total of the plurality of receivable points. The second presentation unit 212 causes the display unit 55 to display the point management screen G10 of FIG. 16 based on these tally results and calculation results.

The privilege granting system S of Modification 8 presents the user with the total receivable points for each of a plurality of services and the receivable points for each service. This makes it possible to more strongly appeal to users to become members of the credit card service. Users also find it easier to grasp the points they can receive retroactively when they issue an affiliated credit card, which increases convenience for users.

[5-9. Modification 9]
For example, the privilege granting system S that provides a mechanism like the fourth embodiment is capable of supporting a plurality of other services in addition to credit card services. Receivable points generated when using the online shopping service may be awarded to services other than the credit card service. In modification 9, it is assumed that the user can receive receivable points not only when using a credit card service but also when the user becomes a member of a communication service.

For example, assume that if the user is not a member of either a credit card service or a communication service, the point return rate in the online shopping service is 1%. It is assumed that when a user becomes a member of a credit card service, the return rate increases by 0.5%, and when a user becomes a member of a communication service, the return rate increases by 1%. Therefore, if the user becomes a member of both the credit card service and the communication service, the return rate will be 2.5%.

Credit card services and communication services are examples of other services. The number of other services is not limited to two, and may be three or more. The provisional benefit generation unit 202 of modification 9 associates the member ID and the receivable points with each other service and registers them in the provisional benefit database DB2. For example, when a user who is not a member of either a credit card service or a communication service uses an online shopping service, the provisional benefit generation unit 202 adds 0.5 points to the usage amount as receivable points corresponding to the credit card service. The value multiplied by % is registered in the provisional benefit database DB2. The provisional benefit generation unit 202 registers a value obtained by multiplying the usage amount by 1% in the provisional benefit database DB2 as the receivable points corresponding to the communication service.

When it is determined that the user has become a member of any of a plurality of other services, the provisional benefit granting unit 205 of Modification 9 provides the receivable points associated with the member ID of the other service. , granted to the user. For example, when a user becomes a member of a credit card service, the provisional benefit granting unit 205 can receive a reward corresponding to the credit card service registered in the temporary benefit database DB2 in association with the member ID of the user. Give points to this user. When a user becomes a member of a communication service, the provisional benefit granting unit 205 assigns receivable points corresponding to the communication service that are associated with the user's member ID and registered in the temporary benefit database DB2. Granted to the user.

In the case where it is determined that the user has become a member of any of a plurality of other services, the benefit granting system S of Modification 9 provides receivable points associated with the member ID of the other service. Granted to the user. This increases the appeal of becoming a member of more other services. It is also more convenient for users because it becomes easier to receive receivable points.

[5-10. Modification 10]
For example, even if there are multiple other services as in Modification 9, the points that can be received when a user becomes a member of another service, as in Modification 6 or 8, are may be presented. The privilege granting system S of Modification 10 includes a third presentation section 213. The third presentation unit 213 presents to the user, for each other service, points that can be received if the user becomes a member of the other service. In modification 10, similarly to modification 6 or modification 8, it is assumed that the point management screen G10 is presented to the user.

FIG. 17 is a diagram illustrating an example of a point management screen G10 displayed in Modification 10. As shown in FIG. 17, the point management screen G10 displays the total amount of points that can be received when becoming a member of two other services, such as a credit card service and a communication service, and the individual points for each other service. Receivable points will be displayed. In the example of FIG. 17, when a user becomes a member of a credit card service, he or she is given 1500 receivable points. When a user becomes a member of a communication service, he or she is given 3000 receivable points.

For example, when presenting the point management screen G10 to a certain user, the third presentation unit 213 refers to the provisional benefit database DB2 and determines the receivable points for each other service associated with the member ID of this user. get. Based on this information, the third presentation unit 213 totals the receivable points for each other service and calculates the total of the plurality of receivable points. The second presentation unit 212 causes the display unit 55 to display the point management screen G10 of FIG. 17 based on these tally results and calculation results.

The privilege granting system S of Modification 10 presents to the user, for each other service, the points that can be received if the user becomes a member of the other service. This makes it possible to more strongly appeal to users to become members of each of a plurality of other services. Users also find it easier to understand how many points they can receive by becoming a member of which service, which increases convenience.

[5-11. Other variations]
For example, the modifications described above may be combined.

For example, the functions described as being implemented by the store server 10 may be implemented by the benefit management server 20, the membership management server 30, or another server computer. The functions described as being realized by the benefit management server 20 may be realized by the store server 10, the member management server 30, or another server computer. The functions described as being implemented by the member management server 30 may be implemented by the store server 10, the benefit management server 20, or another server computer. For example, functions described as being implemented by one computer may be shared among multiple computers. Each function may be realized by at least one computer.

S Benefit granting system, N Network, 10 Store server, 11, 21, 31, 41, 51 Control unit, 12, 22, 32, 42, 52 Storage unit, 13, 23, 33, 43, 53 Communication department, 20 Benefit management server, 30 member management server, 40 store terminal, 50 user terminal, 44, 54 operation section, 45, 55 display section, 46 reading device, 47 output device, 56 reading section, DB1 privilege database, DB2 provisional privilege database, DB3 member database, 100 data storage unit, 101 service provision unit, 102 output unit, 200 data storage unit, 201 usage determination unit, 202 provisional benefit generation unit, 203 output unit, 204 receipt condition determination unit, 205 provisional benefit provision unit, 206 privilege granting section, 207 first restriction section, 208 second restriction section, 209 third restriction section, 210 fourth restriction section, 211 first presentation section, 212 second presentation section, 213 third presentation section, 300 data storage section, 301 member registration section, 400 data storage section, 401 service provision section, 402 output section, 500 data storage section, 501 display control section, 502 operation reception section.

Claims (20)

a usage determination unit that determines whether the service is used in a non-receivable state in which the user cannot receive benefits;
a provisional benefit generation unit that generates a provisional benefit when it is determined that the service is used in the non-receivable state;
a receiving condition determining unit that determines whether receiving conditions regarding receiving the temporary benefit are satisfied after using the service;
a provisional benefit granting unit that grants the provisional benefit to the user when it is determined that the receiving condition is met;
A benefit granting system that includes. The benefit granting system further includes a benefit granting unit that grants the benefit to the user when it is determined that the service is used in a receivable state where the user can receive the benefit;
The temporary benefit generation unit does not generate the temporary benefit if it is determined that the service is used in the receivable state.
The privilege granting system according to claim 1. The usage determination unit determines whether or not the service is used in the non-receivable state by determining whether or not the service is used while the user is not a member of another service different from the service. determine whether
The receiving condition determination unit determines whether the receiving condition is satisfied by determining whether the user has become a member of another service different from the service.
The privilege granting system according to claim 1 or 2. The said service is provided at a physical store,
The temporary benefit generation unit associates temporary benefit identification information that can identify the temporary benefit with the generated temporary benefit and registers the generated temporary benefit in a database;
The benefit granting system further includes an output unit that outputs the provisional benefit identification information at the physical store,
The receiving condition determination unit determines whether the receiving condition is satisfied by determining whether the provisional benefit identification information is acquired from the user terminal.
The privilege granting system according to any one of claims 1 to 3. The usage determination unit determines whether the service is used in a state where the receipt is not possible by determining whether the service is used in a state where the item related to receiving the benefit is not presented at the physical store. do,
The privilege granting system according to claim 4. The output section is
If it is determined that the service is used in the non-receivable state, the physical store outputs the provisional benefit identification information by causing the physical store to output a first receipt including the provisional benefit identification information. ,
If the service is used in a state in which the user can receive the benefit, a second receipt with a layout different from the first receipt and which does not include the provisional benefit identification information is sent to the physical store. output,
The privilege granting system according to claim 4 or 5. The output unit outputs the provisional benefit identification information at the physical store by causing the physical store to output a receipt on which a code including the temporary benefit identification information is formed;
The user terminal reads the code of the receipt,
The receiving condition determination unit determines whether the provisional benefit identification information included in the code is acquired from the user terminal.
The privilege granting system according to any one of claims 4 to 6. The temporary benefit generation unit sets an expiration date to the generated temporary benefit,
The receiving condition determination unit determines whether the receiving condition is satisfied by determining whether the temporary benefit identification information is acquired from the user terminal within the expiration date.
The privilege granting system according to any one of claims 4 to 7. The benefit granting system determines whether the provisional benefits granted to the user within a predetermined period have reached the upper limit, and if it is determined that the upper limit has been reached, the bonus granting system provides a reward to the user. further comprising a first restriction part that restricts the provisional benefit from being granted;
The privilege granting system according to any one of claims 4 to 8. The benefit granting system determines whether a first location related to the physical store and a second location related to the user correspond, and determines that the first location and the second location correspond. further comprising a second restriction part that restricts the temporary benefit from being granted to the user if the provisional benefit is not granted to the user;
The privilege granting system according to any one of claims 4 to 9. When the provisional benefit identification information is acquired from the user terminal, the benefit granting system determines whether the usage history of the service corresponding to the acquired provisional benefit identification information is valid; further comprising a third restriction unit that restricts the granting of the provisional benefit to the user if the usage history is not determined to be valid;
The privilege granting system according to any one of claims 4 to 10. The receiving condition determining unit determines whether the provisional benefit identification information has been acquired from the user terminal that has logged into another service different from the service;
The user is a member of the service,
The privilege granting system determines whether or not the first membership information of the user in the service and the second membership information of the user in the other service match, and , and the second member information, further including a fourth restriction unit that restricts the provisional benefit from being granted to the user when it is determined that the information does not match the second member information.
The privilege granting system according to any one of claims 4 to 11. The user is a member of the service,
The temporary benefit generation unit associates and registers user identification information that can identify the user in the service with the generated temporary benefit in a database,
The temporary benefit granting unit grants the temporary benefit associated with the user identification information to the user when it is determined that the user has become a member of the other service.
The privilege granting system according to claim 3. The benefit granting system further includes a first presentation unit that presents the provisional benefit to the user before the user becomes a member of the other service.
The privilege granting system according to claim 13. The benefit granting system corresponds to a plurality of the services,
The provisional benefit granting unit grants the provisional benefit of each of the plurality of services to the user when it is determined that the receiving condition is satisfied.
The privilege granting system according to claim 13 or 14. The benefit granting system further includes a second presentation unit that presents the total of the provisional benefits of each of the plurality of services and the provisional benefits for each service to the user.
The privilege granting system according to claim 15. The benefit granting system corresponds to a plurality of other services,
The temporary benefit generation unit associates and registers the user identification information and the temporary benefit in the database for each of the other services,
When it is determined that the user has become a member of any one of the plurality of other services, the provisional benefit granting unit provides the provisional benefit provision unit associated with the user identification information of the other service. Granting benefits to the user;
The privilege granting system according to any one of claims 13 to 16. The benefit granting system further includes a third presentation unit that presents to the user, for each of the other services, the provisional benefit that will be granted when the user becomes a member of the other service.
The privilege granting system according to claim 17. a usage determination step of determining whether the service is used in a non-receivable state in which the user cannot receive benefits;
a temporary benefit generation step of generating a temporary benefit when it is determined that the service is used in the non-receivable state;
a receiving condition determining step of determining whether receiving conditions regarding receiving the provisional benefit are satisfied after using the service;
a temporary benefit granting step of granting the temporary benefit to the user when it is determined that the receiving condition is satisfied;
Benefit granting methods including. a usage determination unit that determines whether the service is used in a non-receivable state in which the user cannot receive benefits;
a provisional benefit generation unit that generates a provisional benefit when it is determined that the service is used in the non-receivable state;
a receiving condition determining unit that determines whether receiving conditions regarding receiving the provisional benefit are satisfied after using the service;
a provisional benefit granting unit that grants the provisional benefit to the user when it is determined that the receiving condition is satisfied;
A program that allows a computer to function as a computer.

Images