PRIVILEGE GIVING SYSTEM, PRIVILEGE GIVING METHOD, AND PROGRAM
The benefit granting system addresses the issue of users missing out on points by allowing provisional point awards in non-receivable states, improving user convenience and system efficiency.
Patent Information
- Application Number
- JP2023016917
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2023-02-07
- Publication Date
- 2024-11-21
- Estimated Expiration
- 2042-03-04
AI Technical Summary
Conventional systems fail to provide points to users who do not have a membership card, forget to bring their membership card, or are not registered members, leading to reduced convenience in using services.
A benefit granting system that includes a usage determination unit to identify non-receivable states, a provisional benefit generation unit to create provisional benefits, and a receiving condition determining unit to grant benefits once conditions are met, allowing users to receive points even if they cannot do so immediately.
Enhances user convenience by enabling users to receive points retrospectively, increasing the appeal of membership and reducing processing loads on the system.
Smart Images

Figure 0007588165000001 
Figure 0007588165000002 
Figure 0007588165000003
Abstract
Description
[Technical field]
[0001] The present disclosure relates to a reward granting system, a reward granting method, and a program. [Background technology]
[0002] Conventionally, there are known techniques for providing benefits to users who use a service. For example, Patent Document 1 describes a technique that sets stricter conditions for using points for a user who does not associate a card number of a membership card with member identification information in an online service than conditions for using points for a user who associates a card number with member identification information.
[0003] For example, Patent Document 2 describes a technology in which 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 identified, the provisionally assigned point value associated with the fixed identification code information is included in the point value corresponding to the user identification information. [Prior art documents] [Patent documents]
[0004] [Patent Document 1] JP 2017-054282 A [Patent Document 2] JP 2020-166740 A Summary of the Invention [Problem to be solved by the invention]
[0005] However, with the technology 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 card and users who forget to present their membership card at the store, and they are unable to receive points. The same is true with the technology of Patent Document 2, and users who have not registered as members, users who forget to bring their user terminal, and users who forget to present their user terminal at the store are unable to receive points. For this reason, conventional technologies have not been able to sufficiently improve the convenience of users who use services.
[0006] One of the objectives of the present disclosure is to increase convenience for users of the service. [Means for solving the problem]
[0007] The reward granting system of the present disclosure includes a usage determination unit that determines whether a service has been used in a non-receivable state in which the user cannot receive a reward, a provisional reward generation unit that generates a provisional reward when it is determined that the service has been used in the non-receivable state, a receiving condition determination unit that determines whether a receiving condition for receiving the provisional reward is satisfied after use of the service, and a provisional reward granting unit that grants the provisional reward to the user when it is determined that the receiving condition is satisfied. Effect of the Invention
[0008] According to the present disclosure, convenience for users of services is improved. [Brief description of the drawings]
[0009] [Figure 1] FIG. 1 is a diagram illustrating an example of an overall configuration of a privilege granting system. [Diagram 2] A diagram showing an example of a user who has registered as a member of a points service using a physical store. [Diagram 3] A diagram showing an example of how a user who is not a member of a point service uses a physical store. [Figure 4]FIG. 13 is a diagram showing an example of a user reading a receiving code. [Diagram 5] FIG. 2 is a functional block diagram showing an example of functions realized by the privilege granting system. [Figure 6] FIG. 13 is a diagram showing an example of a benefit database. [Figure 7] FIG. 13 is a diagram showing an example of a provisional benefit database. [Figure 8] FIG. 4 is a diagram illustrating an example of a member database. [Figure 9] A figure showing an example of a physical store usage process executed in the bonus granting system. [Figure 10] FIG. 2 is a diagram illustrating an example of a member registration process executed in the privilege granting system. [Figure 11] FIG. 11 is a diagram showing an example of a flow of receiving receivable points in the second embodiment. [Figure 12] FIG. 13 is a diagram showing an example of a flow of receiving receivable points in the third embodiment. [Figure 13] FIG. 1 is a diagram showing an example of a chronological flow until a user issues an affiliated credit card. [Figure 14] FIG. 13 is a diagram illustrating an example of a functional block according to a modified example. [Figure 15] FIG. 23 is a diagram showing an example of a screen displayed in Modification 6. [Figure 16] FIG. 23 is a diagram showing an example of a point management screen displayed in Modification Example 8. [Figure 17] FIG. 23 is a diagram showing an example of a points management screen displayed in Modification Example 10. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0010] [1. First embodiment] A first embodiment, which is an example of an embodiment of the reward granting system according to the present disclosure, will be described. In the first embodiment, an example is given of a partnership between a retail service that retails products at a physical store and a point service that provides points that can be used for payments at the physical store. It is assumed that users of the physical store are not members of the point service. The reward granting system can also be applied to other situations. Examples of application to other situations will be described later.
[0011] [1-1. Overall structure of the reward system] 1 is a diagram showing an example of the overall configuration of a reward granting system. For example, the reward granting system S includes a store server 10, a reward 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.
[0012] The reward-granting system S only needs to include at least one computer, and is not limited to the example of Fig. 1. For example, the reward-granting system S may include only the reward 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 reward-granting system S. For example, the reward-granting system S may include only the reward management server 20, and the member management server 30 may exist outside the reward-granting system S. The reward-granting system S may include other computers not shown in Fig. 1.
[0013] The store server 10 is a server computer managed by a retailer that provides retail services. The control unit 11 includes at least one processor. The storage unit 12 includes a volatile memory such as a RAM and a non-volatile memory such as a flash memory. The communication unit 13 includes at least one of a communication interface for wired communication and a communication interface for wireless communication.
[0014] The reward management server 20 is a server computer managed by a point service provider. The physical configurations of the control unit 21, the storage unit 22, and the communication unit 23 are similar to those of the control unit 11, the storage unit 12, and the communication unit 13, respectively.
[0015] Member management server 30 is a server computer managed by the point business operator. The physical configurations of control unit 31, memory unit 32, and communication unit 33 are similar to those of control unit 11, memory unit 12, and communication unit 13, respectively.
[0016] The store terminal 40 is a computer installed in a retailer's physical store. In the first embodiment, 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 unit 41, the memory unit 42, and the communication unit 43 are similar to those of the control unit 11, the memory unit 12, and the communication unit 13, respectively. The operation unit 44 is an input device such as a touch panel. The display unit 45 is a liquid crystal display or an organic EL display.
[0017] 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 an image or a storage medium. In the first embodiment, a case where the reading device 46 is a code reader will be described, but the reading device 46 may be another device, for example, a camera, a scanner, an NFC reader, or a magnetic card reader. The reading device 46 may have not only a reading function but also a writing function.
[0018] The output device 47 is an image forming device. In the first embodiment, 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, an image forming device that is not classified as a printer, a copier, or a multifunction device. Receipts may be output as electronic data rather than as physical paper.
[0019] The user terminal 50 is a user's computer. In the first embodiment, the case where the user terminal 50 is a smartphone will be described, but the user terminal 50 may be another computer, for example, a personal computer, a tablet terminal, or a wearable terminal. The physical configurations of the control unit 51, the storage unit 52, the communication unit 53, the operation unit 54, and the display unit 55 are similar to those of the control unit 11, the storage unit 12, the communication unit 13, the operation unit 44, and the display unit 45, respectively. The reading unit 56 may be similar to the reading device 46, but in the first embodiment, the reading unit 56 is a camera of a smartphone.
[0020] The programs stored in the storage units 12, 22, 32, 42, and 52 may be supplied via the network N. Also, the programs stored in an information storage medium may be supplied via a reading unit (e.g., an optical disk drive or a memory card slot) that reads a computer-readable information storage medium, or an input / output unit (e.g., a USB port) that inputs and outputs data to and from an external device.
[0021] [1-2. Overview of the first embodiment] For example, when a user becomes a member of a point service, the user can receive points according to the amount of spending at a physical store. The physical store is an affiliated store of the point service. The user may become a member of the point service by being issued with a physical point card, or by registering as a member through the user terminal 50. When the user becomes a member of the point service, the user presents the point card at the physical store as proof that he or she is a member.
[0022] 2 is a diagram showing an example of a state in which a user who has registered as a member of a point service uses a physical store. In the first embodiment, a case will be described in which a 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, a magnetic card, an NFC card, or other cards may be used. The IC chip of the user terminal 50 may be used as a point card.
[0023] For example, a point service application (hereinafter, the point app) is installed in 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. The point card screen G1 displays the user's point balance as well as a code C10 including a display ID that can identify the user. The code C10 may be of any type, such as a barcode or a two-dimensional code.
[0024] A store clerk at the physical store reads the barcode of the product and the code C10 on the point card screen G1 with a reader 46. If the checkout is self-service, the customer reads these with the reader 46. The customer can use all or part of the point balance, or can save the points without using them. Once the customer has completed the transaction, a receipt R2 is output from the output device 47. Usage history information I20 relating to the usage history of the physical store and point information I21 relating to the user's points are printed on the receipt R2.
[0025] For example, the usage history information I20 may include the store name, the store's phone number, the store's address, the date and time of use, details of the products purchased by the user, and the billing amount. For example, the points information I21 may include a portion of the card number that can identify the point card, the amount of points awarded, the points to be received, the points available, and a transaction code that can identify the transaction.
[0026] In the example of Fig. 2, the point service has a redemption rate of 1%, and 40 points will be awarded if the user spends 4,000 yen. 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 also receive points immediately after shopping. As shown in Fig. 2, if the user is a member of the point service, the user can receive points according to the amount of spending at the physical store.
[0027] 3 is a diagram showing an example of a user who is not a member of a point service using a physical store. Since the user is not a member of the point service, he / she basically cannot receive points even if he / she uses the 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 has completed the transaction, a receipt R3 is output from the output device 47.
[0028] Usage history information I30 and point information I31 are printed on receipt R3. Usage history information I30 is the same as usage history information I20 in Fig. 2. Point information I31 is different from point information I21 in Fig. 2. For example, the amount that would have been eligible for points if the customer were a member of the point service, the receivable points, and a receipt code C310 are printed on receipt R3 as point information I31.
[0029] In the first embodiment, a user who is not a member of a point service can receive receivable points by becoming a member of the point service by reading the receiving code C310 with the reading unit 56. The receiving points are points that the user cannot receive on the spot when he or she uses a physical store, but can receive if he or she becomes a member of the point service. The receiving code C310 includes a receiving ID that can identify the receiving points, and a link to a member registration screen for the point service.
[0030] 4 is a diagram showing an example of how a user reads the receipt code C310. When the user reads the receipt code C310 with the user terminal 50, a membership registration screen G4 is displayed on the display unit 55. For example, the user inputs membership information such as an email address, member ID, password, name, and date of birth in input forms F40 to F44. When the user inputs the membership information and selects button B45, membership registration for the point service is completed, and receivable points are granted to the user.
[0031] 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 granted to the user and the member information registered with the point service. In the example of FIG. 4, the user is granted 40 receivable points printed on the same receipt R3 as the receipt code C310 read during membership registration. The user selects button B50 to download and install the point app on the user terminal 50.
[0032] When the point app is installed on the user terminal 50, the user can use the 40 points granted 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 granted as a bonus for membership registration, the point balance including these points is displayed on the point card screen G1. For example, if 2000 points are granted as a campaign for membership registration, the user can use 2040 points from the beginning, which is the sum of the 40 receivable points and the granted points.
[0033] As described above, in the first embodiment, when a user uses a physical store without being a member of the 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, the user can receive receivable points. This allows the user to receive points that could not be received before, which increases the convenience for the user and increases the appeal of becoming a member of the point service. Details of the first embodiment will be described below.
[0034] [1-3. Functions realized by the reward system] FIG. 5 is a functional block diagram showing an example of functions realized by the privilege granting system S. As shown in FIG.
[0035] [1-3-1. Functions realized by the store server] The data storage unit 100 is realized mainly by the storage unit 12. The service providing unit 101 and the output unit 102 are realized mainly by the control unit 11.
[0036] [Data storage section] The data storage unit 100 stores data necessary to provide retail services to users. For example, the data storage unit 100 stores a product database related to products sold in the retail service. The product database stores information such as product codes capable of identifying products, product names, prices, and stock. The product database itself can use various databases in known retail services. For example, the data storage unit 100 stores a usage result database related to the results of users' use of the retail service. The usage result database stores information equivalent to the usage history information I20, I30 and point information I21, I31 printed on receipts R2, R3.
[0037] [Service Provision Department] The service providing unit 101 provides a retail service to a user. The method of providing the retail service itself can use various known methods. The process for a point service user to use or accumulate points at a physical store can also use various known methods. However, in the first embodiment, the method of outputting a receipt R3 when a user who is not registered with the point service uses a physical store differs from conventional methods. As for the functions of the store server 10, mainly the function of the output unit 102 differs from conventional functions. As other functions of the store server 10 can be reused from conventional functions, the retail service side can introduce the functions of the first embodiment with minimal modifications.
[0038] [Output section] The output unit 102 outputs receipts R2, R3 at the physical store. Outputting receipts R2, R3 means causing the output device 47 to print the usage history information I20, I30 and point information I21, I31 on the receipts R2, R3 and ejecting the receipts R2, R3. In the first embodiment, a case is described in which the receipts R2, R3 are output by communication between the store server 10 and the store terminal 40 at the time of the user's checkout, but the receipts R2, R3 may also be output by communication between the benefit management server 20 and the store terminal 40. The store terminal 40 does not need to communicate with other computers when outputting receipts R2, R3.
[0039] For example, when it is determined that a retail service has been used in a state where receipt is not available, the output unit 102 causes a receipt ID to be output at the physical store by outputting a receipt R3 including the receipt ID at the physical store. Receipt R3 is an example of a first receipt. Therefore, any description of receipt R3 can be read as the first receipt. The first receipt is a receipt for a user in a state where receipt is not available. The first receipt is printed in the first layout.
[0040] The non-receiving 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 the point service corresponds to the non-receiving state. Therefore, the part explaining the state of not being a member of the point service can be read as the non-receiving state. The non-receiving state may be a 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.
[0041] For example, if a user can receive points immediately on the spot when using a retail service, the non-receiving state is a state in which points cannot be received immediately. Even if the user is a member of a point service, points cannot be received immediately unless the user presents a 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 non-receiving state.
[0042] For example, if a user is able to receive points after a certain period of time has passed after using a retail service (within three days in the example of Figure 2), the non-receiving state is a state in which points are not awarded even after this period has passed. Even if a user is a member of a point service, if they do not present their point card, they will not be able to receive points even after the above-mentioned period has passed since using the retail service. For this reason, a state in which a user who is a member of a point service does not present their point card corresponds to a non-receiving state.
[0043] For example, when a retail service is used in a receipt-ready state, the output unit 102 outputs receipt R2 at the physical store, which has a different layout from receipt R3 and does not include a receipt ID. The sections describing receipt R2 can be read as a second receipt. The second receipt is a receipt for a user in a receipt-ready state. The second receipt is printed in a second layout that is different from the first layout.
[0044] The receivable state is a state in which the user can receive points. The receivable state is a state that is not a non-receivable state. In the first embodiment, the receivable state corresponds to a state in which the user is a member of the point service. Therefore, the sections that explain this state can be read as the receivable state. More specifically, the receivable state corresponds to a state in which the user is a member of the point service and has presented a point card at a physical store. For example, in cases in which it is not necessary to present a point card, such as by verbally confirming that the user is a member of the point service, the receivable state corresponds to a state in which it has been confirmed that the user is a member of the point service.
[0045] The output unit 102 transmits information necessary for outputting receipts R2, R3 to the store terminal 40, thereby causing the store terminal 40 to output receipts R2, R3. This information may be the content to be printed on the receipts R2, R3, or may be information equivalent to a command for outputting the receipts R2, R3. The method for outputting receipt R2 is similar to conventional methods, so in the first embodiment, the method for outputting receipt R3 will be described.
[0046] The output unit 102 causes the store terminal 40 to output a receipt R3 on which the receipt code C310 is printed. In the first embodiment, when the benefit management server 20 generates the receivable points, it sends a generation completion notification to the store server 10 indicating that the generation of the receivable points has been completed. The generation completion notification includes the receipt code C310 or a receipt ID described below, and the numerical value of the receivable points. When the store server 10 receives the generation completion notification, it sends an output request to the store terminal 40 based on this numerical value, indicating that a receipt R3 should be output.
[0047] An output request is made by sending data in a prescribed format. The output request may include information indicating whether receipt R2 or R3 should be output. An output request for receipt R3 includes point information I31. An output request may also include usage history information I30. The store terminal 40 outputs receipt R3 based on the output request. By sending the output request, the output unit 102 causes the store terminal 40 to output receipt R3.
[0048] In the first embodiment, there are two layouts for receipts R2 and R3, so the output request includes layout identification information that can identify one of the two layouts. If the user is a member of the point service, the output unit 102 sends an output request to the store terminal 40 that includes layout identification information indicating the layout of receipt R2. If the user is not a member of the point service, the output unit 102 sends an output request to the store terminal 40 that includes layout identification information indicating the layout of receipt R3.
[0049] [1-3-2. Functions realized by the reward management server] The data storage unit 200 is realized mainly by the storage unit 22. The use determination unit 201, the provisional privilege generation unit 202, the output unit 203, the receiving condition determination unit 204, the provisional privilege granting unit 205, and the privilege granting unit 206 are realized mainly by the control unit .
[0050] [Data storage section] The data storage unit 200 stores various data related to points. Points are an example of a benefit. Therefore, any section that describes points can be read as benefit. A benefit is something that brings some kind of benefit to a user. The benefit itself can be any of a variety of well-known things, and for example, a coupon, electronic money, content such as a video, or a physical product may correspond to a benefit. Any section that describes points can be read as various other benefits. The data storage unit 200 stores a benefit database DB1 and a temporary benefit database DB2.
[0051] Fig. 6 is a diagram showing an example of the benefit 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 related to points held by members of a point service. For example, the benefit database DB1 stores member IDs, card numbers, display IDs, point balances, and point history.
[0052] The member ID is an ID that can identify a member of the point service. The card number is information that can identify a point card. As mentioned above, the point card in the first embodiment is not limited to a physical card, but may be an electronic card (virtual card) that uses a point app. If a member holds multiple point cards, multiple card numbers are associated with the member ID of this member. The member ID and card number may not be distinguished and may be treated as a single ID.
[0053] The display ID is information contained 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, the code C10 includes a display ID that is valid for only a short period of time, such as about five minutes. For example, when the benefit management server 20 receives a request to generate the code C10 from the user terminal 50, it generates a display ID that does not overlap with other display IDs. The method of generating the display ID itself can use various publicly known methods. The benefit management server 20 stores the display ID in the benefit database DB1 and transmits the display ID to the user terminal 50.
[0054] The point balance is the current balance of points. In cases where points are awarded some time after use of a physical store, the points to be received may be stored in the benefit database DB1 in addition to the point balance. The point history is at least one of the point receipt history and the point usage history. For example, the point history stores information such as a store ID capable of identifying the physical store, the points to be received, the points used, the date and time of use of the physical store, and details of the products purchased at the physical store.
[0055] 7 is a diagram showing an example of the temporary bonus database DB2. The temporary bonus database DB2 is a database for managing receivable points. Various information related to the receivable points is stored in the temporary bonus database DB2. For example, the temporary bonus database DB2 stores a receiving ID, receivable points, and service usage history.
[0056] The receiving ID is an example of temporary bonus identification information. Therefore, the part that says receiving ID can be read as temporary bonus identification information. The temporary bonus identification information is information that can identify a temporary bonus. The temporary bonus identification information is expressed by letters, numbers, other symbols, or a combination of these. The temporary bonus identification information is also information that can identify a transaction at a physical store. The temporary bonus identification information is generated so that it does not overlap with other temporary bonus identification information.
[0057] Receivable points are an example of a provisional benefit. Therefore, any section that states "receivable points" can be read as "provisional benefit." A provisional benefit is a benefit that has not been confirmed as being granted to a user. A provisional benefit can also be said to be a benefit that is not confirmed as being received. As with the benefits described above, a provisional benefit may be of another type, such as a coupon.
[0058] The service usage history is information about the usage history of a retail service. For example, when a user uses a retail service, receivable points are generated, and information about the product purchased by the user at that time is stored. For example, the service usage history stores the store ID of the actual store, the date and time of use, details of the product, the amount used, and the amount eligible for the points.
[0059] [Usage Judgment Department] The usage determination unit 201 determines whether or not the retail service has been used in a non-receivable state. For example, when a user uses a retail service, the store server 10 or the store terminal 40 transmits information indicating whether the state is non-receivable or receivable to the benefit management server 20. Based on this information, the usage determination unit 201 determines whether or not the retail service has been used in a receivable state. This information is generated based on input from the operation unit 44 or the reading device 46 in the store terminal 40.
[0060] The retail service is an example of a service related to the present disclosure. Therefore, the phrase "retail service" may be read as "service." The service is a service that can provide some kind of benefit when used by a user. When a user uses the service, the benefit does not necessarily have to be provided, and the benefit may be provided only when certain conditions are met. The service may be any service and is not limited to a retail service.
[0061] For example, the service may be a food and drink service, a beauty service, an electricity service, a moving service, or other services related to daily life. The 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 beauty salon, or an esthetic salon. The service is not limited to one provided in a real space such as a physical store or a user's home, but may be one 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.
[0062] The point service is an example of the other service according to the present disclosure. Therefore, the part that says "point service" can be read as "other service." The other service is a service different from the service, which is an example of a retail service. The other service is a service for receiving benefits, which is an example of points. The other service may be any service and is not limited to the point service. The combination of the service according to the present disclosure and the other service may be any combination and is not limited to the example of the first embodiment.
[0063] In the first embodiment, the usage determination unit 201 determines whether the retail service was used when the user was not a member of the point service, thereby determining whether the service was used in a non-acceptable state. For example, the usage determination unit 201 determines whether the display ID included in the code C10 displayed on the point card screen G1 of the point app was acquired, thereby determining whether the retail service was used when the user was not a member of the point service.
[0064] For example, using a retail service without obtaining a display ID corresponds to using the retail service when the user is not a member of the point service. Using a retail service after obtaining a display ID corresponds to using the retail service when the user is a member of the point service. The information used in the determination by the usage determination unit 201 need only be 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, a card number, or other information.
[0065] In the first embodiment, the usage determination unit 201 determines whether the service has been used in a non-receivable state by determining whether the service has been used without presenting the user terminal 50 on which the code C10 is displayed at the physical store. When the code C10 displayed on the point card screen G1 is read by the reader 46, the store terminal 40 transmits the display ID to the benefit management server 20.
[0066] The usage determination unit 201 refers to the benefit database DB1 and determines whether or not the display ID received from the store terminal 40 exists. If the display ID does not exist in the benefit database DB1, or if the display ID was not received in the first place, the usage determination unit 201 determines that the retail service was used in a non-receivable state. If the display ID exists in the benefit database DB1, the usage determination unit 201 determines that the retail service was used in a receivable state.
[0067] For example, since a user who is not a member of the point service cannot present the code C10 at a physical store, the store terminal 40 does not send a display ID to the benefit management server 20 until the use of the retail service is completed. Therefore, if the usage determination unit 201 does not receive a display ID from the store terminal 40 until the use of the retail service is completed, it determines that the retail service was used in a non-receivable state. In the first embodiment, the completion of the transaction at the physical store corresponds to the completion of the use of the retail service.
[0068] For example, the usage determination unit 201 detects that usage of the retail service has been 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 usage determination unit 201 does not receive a display ID before receiving the usage completion notification, it determines that the retail service has been used in a non-receivable state. If the display ID is included in the usage completion notification, the usage determination unit 201 may determine whether or not the retail service has been used in a non-receivable state by determining whether or not the usage completion notification includes a display ID.
[0069] The user terminal 50 on which the display ID is displayed is an example of an object related to receiving a benefit. Therefore, any part describing the user terminal 50 can be read as an object related to receiving a benefit. 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, other cards, or a membership card other than a card may correspond to an object related to receiving a benefit. It is assumed that these objects contain information that proves eligibility to receive a benefit.
[0070] 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 benefit management server 20. The usage determination unit 201 may determine whether or not the retail service has been used in a non-receivable state, based on the transferred display ID.
[0071] Furthermore, in the case of electronic payment in which a code at a physical store is read by the user terminal 50 or which is completed by only operating the user terminal 50, the user terminal 50 may transmit a display ID to the benefit management server 20. In this case, the usage determination unit 201 determines whether or not a retail service has been used in a non-receivable state based on the display ID received from the user terminal 50. In this case, the user terminal 50 may also transmit the display ID to another computer such as the store server 10, rather than to the benefit management server 20.
[0072] [Temporary Bonus Generation Department] The temporary reward generating unit 202 generates receivable points when it is determined that the retail service has been used in a non-receivable state. Generating receivable points means generating information on the receivable points. When a reward other than points is used as the temporary reward, the temporary reward generating unit 202 may generate the temporary reward by generating information according to the type of the temporary reward. For example, the temporary reward generating unit 202 may generate, as the temporary reward, a coupon, an electronic ticket, electronic money, content (digital content) such as a video, ownership of digital content, a token associated with digital content, a digital asset, or information on a physical product. The temporary reward may be, for example, information on something managed on a distributed ledger such as a blockchain network.
[0073] In the first embodiment, generating a receiving ID and information indicating the numerical value of receivable points corresponds to generating receivable points. The provisional reward generation unit 202 generates a receiving ID so that the receiving ID does not overlap with other receiving IDs. The receiving ID may be generated based on a predetermined rule. The provisional reward generation unit 202 determines the receivable points based on the result of the user's use of the retail service.
[0074] For example, the temporary reward generation unit 202 determines the receivable points to be a numerical value obtained by multiplying the amount of use by the user by a predetermined return rate. The temporary reward generation unit 202 may determine the receivable points to be a fixed numerical value regardless of the amount of use. For example, the temporary reward generation unit 202 associates a receiving ID with the generated receivable points and registers them in the temporary reward database DB2. These can be registered in any database other than the temporary reward database DB2.
[0075] In the first embodiment, since the temporary benefit database DB2 also stores the service usage history, the temporary benefit generation unit 202 generates three pieces of information, namely, the receipt ID, the receivable points, and the service usage history, and stores the generated three pieces of information in the temporary benefit database DB2. The service usage history is included in the usage completion notice received from the store server 10 or the store terminal 40.
[0076] In the first embodiment, the provisional reward generation unit 202 does not generate receivable points if it is determined that the user is a member of a point service and has used a retail service. In this case, points are awarded to the user by the reward allocation unit 206, which will be described later. As in the second embodiment, which will be described later, the provisional reward generation unit 202 generates receivable points if the user does not present a point card, even if the user is a member of a point service.
[0077] [Output section] The output unit 203 outputs receipts R2, R3 at the physical store. The output unit 203 transmits information necessary for outputting receipts R2, R3 to the store server 10 or the store terminal 40, thereby causing the store terminal 40 to output receipts R2, R3. This information may be the content to be printed on receipts R2, R3, or may be information equivalent to a command for outputting receipts R2, R3. The method for outputting receipt R2 is similar to conventional methods, so in the first embodiment, the method for outputting receipt R3 will be described.
[0078] The output unit 203 causes the receipt ID to be output at the physical store. In the first embodiment, the output unit 203 sends a generation completion notification, as explained in the processing of the output unit 102 of the store server 10, to the store server 10 based on the receipt ID. After that, the output unit 102 of the store server 10 sends an output request for receipt R3 to the store terminal 40, so the output unit 203 sends a generation completion notification, thereby causing the receipt ID to be output at the physical store. The output unit 203 may also send the receipt ID directly to the store terminal 40, instead of to the store server 10, causing the store terminal 40 to output receipt R3.
[0079] [Receipt Condition Judgment Section] The receiving condition determination unit 204 determines whether or not the receiving conditions for receiving receivable points are satisfied after the use of the retail service. For example, the benefit management server 20 receives information for determining whether or not the receiving conditions are satisfied from the member management server 30 or the user terminal 50. The receiving condition determination unit 204 determines whether or not the receiving conditions are satisfied based on this information.
[0080] In the first embodiment, a case will be described in which becoming a member of a point service corresponds to the receiving condition. Therefore, the part explaining becoming a member of a point service can be read as receiving condition. Receiving condition is a condition for receiving receivable points. Receiving condition may be any condition and is not limited to becoming a member of a point service. For example, receiving condition may be a certain period of time having passed since becoming a member of a point service, using a retail service a certain number of times or for a certain amount after becoming a member of a point service, becoming a member of a service other than the point service, purchasing a specific product in a retail service, or registering certain member information for a point service.
[0081] 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 the point service. Since the 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 information acquired from the member management server 30.
[0082] In the first embodiment, the provisional benefit database DB2 associates a receiving ID with receivable points. Simply becoming a member of a point service does not identify which receivable points a user is eligible to receive. For this reason, the receiving condition determination unit 204 determines whether the receiving conditions are met by determining whether a receiving ID has been acquired from the user terminal 50. If the receiving condition determination unit 204 does not determine that a receiving ID has been acquired from the user terminal 50, it does not determine that the receiving conditions are met, and if it determines that a receiving ID has been acquired from the user terminal 50, it determines that the receiving conditions are met.
[0083] In the first embodiment, since the receipt ID is included in the receipt code C310, the receipt condition determination unit 204 determines whether the receipt ID included in the receipt code C310 has been acquired from the user terminal 50. For example, the user terminal 50 reads the receipt code C310 on the receipt R3. The user terminal 50 acquires the receipt ID and link included in the receipt code C310, and transmits the receipt ID to the member management server 30 to access the member registration screen G4. The user terminal 50 displays the member registration screen G4 on the display unit 55. When the user enters member information in the input forms F40 to F44 and selects the button B45, the member registration process is executed by the member registration unit 301, which will be described later.
[0084] When the member registration process is completed, the member management server 30 sends a registration completion notification to the benefit management server 20, which includes the receiving ID received from the user terminal 50 and member information including the member ID. The registration completion notification is data in a prescribed format indicating that the member registration has been completed. When the benefit management server 20 receives the receiving ID and member information from the member management server 30, it creates a new record in the benefit database DB1. The benefit management server 20 stores the member information received from the member management server 30 in the new record.
[0085] The receiving condition determination unit 204 refers to the temporary benefit database DB2 and determines whether or not the receiving ID received from the benefit management server 20 exists. If the receiving ID does not exist in the temporary benefit database DB2, the receiving condition determination unit 204 does not determine that the receiving conditions are met, and if the receiving ID exists in the temporary benefit database DB2, the receiving condition determination unit 204 determines that the receiving conditions are met. If a user registers as a member without reading the receiving code C310, the benefit management server 20 does not receive the receiving ID, and therefore the receiving condition determination unit 204 does not determine that the receiving conditions are met if it does not receive the receiving ID.
[0086] [Temporary Benefits Granting Department] The provisional bonus granting unit 205 grants receivable points to the user when it is determined that the receiving conditions are met. Granting receivable points means making the receivable points available for use. In the first embodiment, reflecting the receivable points in the user's point balance stored in the bonus database DB1 corresponds to granting the receivable points. Reflecting the receivable points means increasing the point balance by the numerical value of the receivable points.
[0087] The temporary reward granting unit 205 may grant the temporary reward in a manner according to the type of the temporary reward. For example, when a coupon is generated as the temporary reward, the temporary reward granting unit 205 grants the coupon to the user. For example, when electronic money is generated as the temporary reward, the temporary reward granting unit 205 increases the electronic money balance of the user. For example, when content such as a video is generated as the temporary reward, the temporary reward 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 the temporary reward, the temporary reward granting unit 205 executes a process for transferring the token from a wallet address corresponding to the administrator of the reward granting system S to a wallet address corresponding to the user in cooperation with a distributed ledger such as a blockchain network. For example, when information on a physical product is generated as the temporary reward, the temporary reward granting unit 205 executes a process for delivering the physical product to the user.
[0088] In the first embodiment, if the receiving ID received from the member management server 30 exists in the temporary benefit database DB2, it is determined that the receiving condition is satisfied. In this case, the temporary benefit granting unit 205 grants the receivable points associated with the 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 that stores the member ID included in the member information received from the member management server 30 by the amount of receivable points to be granted to the user.
[0089] If the provisional reward granting unit 205 does not determine that the receiving conditions are met, it does not grant the receivable points to the user. In this case, the user's point balance does not increase. However, if a campaign or the like is being held at the time of member registration, the user's point balance may increase due to other factors.
[0090] [Benefits Granting Department] The reward giving unit 206 gives a reward such as points to the user when it is determined that the retail service has been used in a state where the user can receive the reward. In this case, the process for giving points to the user can use a known process. For example, the reward giving unit 206 may give points to the user by increasing the point balance associated with the display ID included in the code C10 by the number of points to be received. The reward giving unit 206 may give points immediately when the retail service is used. The type of reward may include a provisional reward type. In this case, the reward giving unit 206 may give the reward in a manner according to the type of reward. The reward is not limited to points, as in the provisional reward. Examples of rewards other than points can also be applied to those exemplified in the explanation of the provisional reward.
[0091] [1-3-3. Functions realized by the member management server] The data storage unit 300 is realized mainly by the storage unit 32. The member registration unit 301 is realized mainly by the control unit 31.
[0092] [Data storage section] The data storage unit 300 stores data necessary for member management of the point service. For example, the data storage unit stores a member database DB3.
[0093] Fig. 8 is a diagram showing an example of member database DB3. Member database DB3 is a database in which member information relating to members of a point service is stored. For example, member ID, password, email address, name, date of birth, address, and telephone number are stored in member database DB3. The member information stored in member database DB3 may be any information and is not limited to the example in Fig. 8.
[0094] For example, the member database DB3 may store card numbers, display IDs, points balances, and point histories as member information. In this case, the information is consistent between the member database DB3 and the privilege database DB1. Furthermore, the privilege database DB1 and the member database DB3 may be integrated into a single database.
[0095] [Member Registration Department] The member registration unit 301 executes member registration for the point service. The member registration process itself can utilize various known processes. For example, when the member registration unit 301 receives a member registration request from the user terminal 50, it creates a new record in the member database DB3. The member registration unit 301 executes member registration by storing in that record the member ID, password, email address, name, date of birth, address, and telephone number of the user who will become a new member. When member registration is complete, the member registration unit 301 transmits a registration completion notification to the benefit management server 20 as described in the processing of the receiving condition determination unit 204.
[0096] [1-3-4. Functions realized by store terminals] The data storage unit 400 is realized mainly by the storage unit 42. The service providing unit 401 and the output unit 402 are realized mainly by the control unit 41.
[0097] [Data storage section] The data storage unit 400 stores data necessary for providing retail services to users. For example, the data storage unit 400 may store a product database and a usage result database, similar to the data storage unit 100 of the store server 10. The data storage unit 400 may store product information regarding products before payment and a display ID acquired from the code C10 displayed on the point card screen G1 of the point app. The data storage unit 400 may store a card number and a 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.
[0098] [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, the method of providing the retail services itself can use various known methods, and the function of the store terminal 40 is mainly different from the conventional one in the function of the output unit 402. Therefore, the retail service side can introduce the function of the first embodiment with a minimum of modification.
[0099] [Output section] The output unit 402 outputs the receipt ID at the physical store. The output unit 402 causes the output device 47 to output the receipts R2 and R3. In the first embodiment, the store terminal 40 outputs the receipts R2 and R3 based on an output request received from the store server 10. However, the output unit 402 may cause the output device 47 to output the receipts R2 and R3 based on some request from each of the store server 10 and the benefit management server 20. The output unit 402 may cause the output device 47 to output the receipts R2 and R3 based on a request from the benefit management server 20, not based on 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, not based on a request from each of the store server 10 and the benefit management server 20.
[0100] [1-3-5. Functions realized on user terminals] The data storage unit 500 is realized mainly by the storage unit 52. The display control unit 501 and the operation receiving unit 502 are realized mainly by the control unit 51.
[0101] [Data storage section] The data storage unit 500 stores data necessary for using a point service. For example, the data storage unit 500 stores a point application and a display ID.
[0102] [Display control section] The display control unit 501 displays any screen on the display unit 55. For example, the display control unit 501 displays each of the point card screen G1 in Fig. 2, the member registration screen G4 and the registration completion screen G5 in Fig. 4 on the display unit 55. Each screen may be displayed using an app other than the point app or a browser.
[0103] [Operation reception section] The operation reception unit 502 receives any operation. For example, the operation reception unit 502 receives operations for each of the point card screen G1 in Fig. 2, the member registration screen G4, and the registration completion screen G5 in Fig. 4.
[0104] [1-4. Processing performed by the reward system] In the first embodiment, as an example of processing executed by the benefit awarding system S, a physical store usage processing executed when a user uses a physical store, and a membership registration processing executed when a user who is not a member of the point service registers as a member using receipt R3 are described.
[0105] [Actual store usage processing] Fig. 9 is a diagram showing an example of a physical store usage process executed by the reward granting system S. The physical store usage process is executed by the control units 11, 21, and 41 operating in accordance with the programs stored in the storage units 12, 22, and 42, respectively. Note that Fig. 9 describes a case where a user purchases a product with cash, but if the user uses electronic payment (cashless payment), the electronic payment process is also executed.
[0106] 9, the store terminal 40 identifies an operation performed in a physical store (S100). In S100, an operation is performed to read a barcode of a product with the reader 46, an operation is performed to read a code C10 displayed on a point card screen G1 of a point application with the reader 46, or a transaction operation is performed on the operation unit 44, which means completion of the transaction.
[0107] In S100, when the barcode of a product is read by the reading device 46 (S100; product reading), the store terminal 40 acquires the product code of the product from the barcode (S101), and executes a product information acquisition process to acquire product information such as the product name of the product (S102). In FIG. 9, a case is described in which the store terminal 40 acquires product information by communicating with the store server 10, but the store terminal 40 may acquire product information from a product database stored in the storage unit 42 without communicating with the store server 10.
[0108] In S100, when the code C10 is read by the reading device 46 (S100; code reading), the store terminal 40 acquires a display ID from the code C10 (S103), and executes a point inquiry process to inquire about the point balance with the benefit management server 20 (S104). In S104, the store terminal 40 communicates with the benefit management server 20 to acquire the point balance associated with the display ID from the benefit database DB1. The store terminal 40 records the acquired point balance in the memory unit 42. The point balance may be displayed on the display unit 45. In the point inquiry process, other information such as a card number may also be acquired.
[0109] In S100, when an operation is performed on the operation unit 44 indicating that the transaction is complete (S100; transaction operation), the store terminal 40 determines whether or not a display ID has been acquired by the process of S103 (S105). In S105, the store terminal 40 determines whether or not information such as the display ID and point balance is stored in the memory unit 42. In other words, the store terminal 40 determines whether or not the user is a member of the point service.
[0110] If it is determined in S105 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 executes a transaction process to complete the transaction for the product and a granting process to grant points to the user (S106), and the store terminal 40 outputs a receipt R2 that does not include the receipt code C310 (S107), and the process ends. The user receives the product and receipt R2 and leaves the store. The transaction process and granting process in S106 may be the same as conventional processes. The process for outputting receipt R2 may also be the same as conventional processes.
[0111] If it is determined in S105 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, executes a transaction process and a generation process for generating receivable points (S108), outputs a receipt R3 including a receipt code C310 (S109), and the process ends. The user receives the product and receipt R3 and leaves the store. The transaction process in S108 may be the same as the conventional process.
[0112] In S108, when the transaction process is completed, the store server 10 or the store terminal 40 sends the reward management server 20 a usage completion notification including a service usage history such as the amount used and product details. The reward management server 20 generates a receipt ID and receivable points. The reward management server 20 stores the receipt ID, receivable points, and service usage history in a temporary reward database DB2. The reward management server 20 sends the store server 10 a generation completion notification including the receipt ID and receivable points. Upon receiving the generation completion notification, the store server 10 sends a request to the store terminal 40 to output a receipt R3. In S109, the store terminal 40 outputs a receipt R3 based on this output request.
[0113] [Member registration process] 10 is a diagram showing 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 in accordance with the programs stored in the storage units 22, 32, and 52, respectively.
[0114] As shown in FIG. 10, the user terminal 50 reads the receipt code C310 on the receipt R3 with the reading unit 56 (S200). The user terminal 50 acquires a receipt ID and a link to a member registration screen G4 from the receipt code C310 (S201), and accesses the member management server 30 to display the member registration screen G4 on the display unit 55 (S202). The member management server 30 may receive the receipt ID from the user terminal 50 in S202 and retain the receipt ID. The user terminal 50 accepts input of member information on the member registration screen G4 (S203). When the user selects the button B45, the user terminal 50 sends a member registration request to the member management server 30 (S204).
[0115] When the member management server 30 receives the member registration request (S205), it executes the member registration of the user (S206). The member management server 30 transmits a registration completion notice to the benefit management server 20 (S207), which includes the member ID of the user whose registration has been completed and the receipt ID received from the user terminal 50. When the benefit management server 20 receives the registration completion notice (S208), it creates a new record in the benefit database DB1 (S209).
[0116] The member management server 30 refers to the temporary benefit database DB and determines whether the receiving 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 the receiving points to the user who has registered as a member (S211), and the process ends. If it is not determined that the receiving ID exists (S210; N), the process of S211 is not executed and the process ends.
[0117] The reward system S of this embodiment generates receivable points when it is determined that the retail service has been used in a non-receivable state. The reward system S grants the receivable points to the user when it is determined that the receiving conditions have been met after the use of the retail service. As a result, even if the user uses the retail service in a non-receivable state, the receivable points are granted after the fact, thereby improving the convenience of the user. For example, even if the user is not a member of the point service and is in a non-receivable state, the receivable points are granted after the fact, so that the appeal of becoming a member of the point service is enhanced for users who are not members of the point service. When other conditions are set as the receiving conditions, the appeal of satisfying the other conditions is enhanced. From the perspective of the retailer, if the store becomes a member of the point service, the convenient system increases the customer attraction effect, and the retailer also generates profits.
[0118] Furthermore, the reward granting system S grants points to the user when it is determined that the retail service has been used in a receivable state. The reward granting system S does not generate receivable points when it is determined that the retail service has been used in a receivable state. This prevents unnecessary receivable points from being generated, thereby reducing the processing load on the reward management server 20 and suppressing memory consumption in the temporary reward database DB2.
[0119] In addition, the reward system S determines whether the retail service was used in a non-receivable state by determining whether the retail service was used when the user was not a member of the point service. The reward system S determines whether the receiving conditions are met by determining whether the user has become a member of the point service. This allows the user to receive receivable points when he or she becomes a member of the point service, thereby increasing the appeal of becoming a member of the point service to users who are not members of the point service. As a result, the number of members of the point service can be effectively increased.
[0120] In addition, the reward system S determines whether the receiving condition is satisfied by determining whether the receiving ID outputted at the physical store is acquired from the user terminal 50. This allows the user to receive receivable points using the receiving ID that is known in principle only to users who visit the physical store. As a result, it is possible to prevent fraud such as a third party not using the physical store receiving receivable points without permission.
[0121] In addition, the reward system S determines whether a retail service has been used in a non-receivable state by determining whether the user has used the retail service without presenting the point card at the actual store. This allows the reward system S to generate receivable points after reliably determining whether the user is a member of the point service using the point card.
[0122] In addition, when it is determined that the retail service was used in a non-receivable state, the reward system S causes the receipt R3 including the receipt ID to be output at the actual store, thereby outputting the receipt ID at the actual store. This increases the convenience of the user because the usage history information I30 and the point information I31 are printed on the same receipt R3, not on separate receipts. The user only needs to take home one receipt R3, so the receipt ID is less likely to be lost. In addition, when the retail service was used in a receivable state, the reward system S causes the receipt R2, which has a different layout from the receipt R3 and does not include the receipt ID, to be output at the actual store. This saves space on the receipt R2 and can save receipt paper. The shorter receipt R2 also increases the convenience of the user. By making the layouts of the receipts R2 and R3 different from each other, the user can easily understand whether the receipt ID has been output.
[0123] In addition, the reward system S outputs the receiving ID at the actual store by outputting the receipt R3 on which the receiving code C310 including the receiving ID is formed at the actual store. The reward system S determines whether the receiving ID included in the receiving code C310 has been acquired from the user terminal 50. This allows the user to acquire the receiving ID with a simple operation of reading the receiving code C310 with the reading unit 56 of the user terminal 50, thereby improving the user's convenience. When the user manually inputs the receiving ID from the operation unit 54 of the user terminal 50, there is a possibility that an input error will occur, but by using the receiving code C310, such an input error can be prevented. Furthermore, when the link to the member registration screen G4 is included in the receiving code C310, users who are not members of the point service can easily access the member registration screen G4, improving the user's convenience. It is also possible to effectively increase the number of members of the point service.
[0124] [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 an affiliated store of the point service, the user may use the physical store without presenting the point card screen G1. For example, if the user is reluctant to start the point app or has forgotten the user terminal 50, the user may use the physical store without presenting the point card screen G1. These points are the same when the user uses a physical point card.
[0125] In conventional technology, if a user does not present the point card screen G1 at a physical store, points are not awarded even if the user visits the physical store. If a user who did not present the point card screen G1 visits the physical store again and presents a receipt, it is possible that points may be awarded retroactively through the operations of the physical store. In this case, however, the burden on the physical store increases. Therefore, in the second embodiment, a case will be described in which points are awarded retroactively to a user who is a member of a point service by using a receipt R3, even if the user does not present the point card screen G1 at a physical store.
[0126] 11 is a diagram showing an example of a flow for receiving receivable points in the second embodiment. In the second embodiment, a case where a user receives receivable points using a point app is taken as an example. For example, when the user selects the link L11 for "receive receivable points" displayed on the point card screen G1, the reading unit 56 is activated and a reading screen G6 is displayed on the display unit 55.
[0127] The reading screen G6 displays the captured image I60 generated by the reading unit 56. When the user terminal 50 reads the receipt code C310 on the receipt R3, the user terminal 50 obtains a receipt ID from the receipt code C310. The receipt code C310 also includes a link to a member registration screen G4, but in the second embodiment, the user has already registered for the point service and is logged in to the point service from the point app, so the member registration screen G4 is not displayed. The user terminal 50 discards the link to the member registration screen G4 and sends the receipt ID to the benefit management server 20.
[0128] When the reward management server 20 receives a receiving ID, the receiving condition determination unit 204 refers to the temporary reward database DB2 and determines whether the received receiving ID exists, thereby determining whether the receiving conditions are met. If it is determined that the receiving ID exists in the temporary reward database DB2, the temporary reward granting unit 205 grants the receivable points associated with the receiving ID to the logged-in user. The temporary reward granting unit 205 refers to the reward database DB1 and increases the point balance associated with the member ID of the user by the receivable points. The temporary reward granting unit 205 deletes the record corresponding to the granted receivable points from the reward database DB1.
[0129] When the receivable points are awarded, an award completion screen G7 is displayed on the display unit 55. For example, the award completion screen G7 displays the receivable points awarded to the user and the point balance after the receivable points are received. When the user selects the button B70, the screen returns to the point card screen G1. As shown in the point card screen G1 in the lower 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.
[0130] The user terminal 50 may also transmit a 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 benefit management server 20. When the benefit management server 20 receives the member ID and the receiving ID from the member management server 30, the receiving condition determination unit 204 and the temporary benefit granting unit 205 execute the same processing as described above and grant the receivable points to the logged-in user.
[0131] The benefit granting system S of the second embodiment can grant receivable points to a user who is a member of a point service after the fact. This increases the convenience of the user because the receivable points are granted after the fact even if the user who is a member of the point service does not present the point card screen G1 at a physical store. This also reduces the burden on the physical store because there is no need for a special operation to be performed at the physical store.
[0132] [3. Third embodiment] In the first and second embodiments, a situation where a user uses a retail service at a brick-and-mortar store is taken as an example, but the reward granting system S can also be applied to a situation where a user uses an online service. 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, a description of the same configuration as in the first and second embodiments will be omitted.
[0133] In the third embodiment, the online shopping service and the point service are linked to each other. However, in order for a user to receive points for shopping on the online shopping service, the user must associate the member ID of the online shopping service with the member ID of the point service. Once this association is made, the user can receive points according to the amount of spending on the online shopping service.
[0134] In the third embodiment, a user does not shop at a real store, but at a virtual store on an online shopping service. The store server 10 is a server of the virtual store. The store terminal 40 is a computer operated by an operator of the virtual store. When 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.
[0135] Fig. 12 is a diagram showing an example of the flow of receiving receivable points in the third embodiment. As shown in Fig. 12, when a user operates the user terminal 50 to access the website of the online shopping service, a 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 in to the online shopping service.
[0136] When a user selects and purchases a product from the top screen G8, a purchase completion screen G9 is displayed on the display unit 55. A message such as an e-mail containing the same content as that of the purchase completion screen G9 may be sent to the user. The purchase completion screen G9 displays the product purchase details, the receivable points, and a link L90 to the membership registration screen G4. The flow of generating receivable points may be the same as in the first and second embodiments.
[0137] In the third embodiment, 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 in FIG. 4 are displayed on the display unit 55. The flow of member registration may be the same as that of the first embodiment. The receiving ID may be displayed on the purchase completion screen G9, or may be included in an email sent to the user after purchasing the product. In this case, the user may manually input the receiving ID when registering as a member for the points service or thereafter.
[0138] When a user completes membership registration for the point service, the user is granted receivable points. The user's point card is also automatically registered with 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 receivable points displayed on the purchase completion screen G9. Thereafter, whenever the user uses the online shopping service, points are granted according to the amount of use.
[0139] The reward granting system S of the third embodiment increases the convenience of users of the online shopping service for the same reasons as the reward granting system S of the first embodiment. It also increases the appeal of becoming a member of the point service to users who are not members of the point service. Note that in the third embodiment, even if a user orders a product as a guest user without logging in to the online shopping service, the receivable points may be granted after the fact in the same manner as in the second embodiment.
[0140] In the third embodiment, the case where the user is a member of an online shopping service has been described, but the same processing as in the third embodiment may be executed when the user is a member of a retail service provided in a brick-and-mortar store. In this case, a processing combining the first and third embodiments and a processing combining the second and third embodiments may be executed.
[0141] First, a process combining the first and third embodiments will be described. For example, assume that a user is an "AAA member" who is a member of a retail service provided by a physical store "AAA Shop." For example, when the user presents a "AAA member" point card to use the physical store, the user can receive "AAA points" which are points for the retail service, or can use member-only services such as home delivery services or discount services. For example, when a user becomes an "XXX member" who is a member of a point service, the user can receive "XXX points" in addition to the "AAA points" for the retail service.
[0142] For example, suppose that a user is an "AAA member" but not an "XXX member." In this case, the user cannot receive "XXX points," so the state corresponds to a non-receivable state. When the user presents a "AAA member" point card to use a physical store, receipt points are generated. These receipt points may be associated with the member ID of the "AAA member" rather than the receipt ID. When a user registers as an "XXX member," if the user enters the member ID of the "AAA member," the benefit management server 20 can identify the receivable points to be granted to the user.
[0143] Similarly, when the second and third embodiments are combined, if a user presents a point card for an "AAA member" at a physical store but does not present a point card for an "XXX member," the receivable points may be associated with the member ID of the "AAA member." If the user enters the member ID of the "AAA member" on the website of the "XXX member," etc., the user can subsequently receive the receivable points associated with the member ID.
[0144] In addition, when the member ID of the "AAA Member" and the member ID of the "XXX Member" are linked to each other, the "XXX Points" may be automatically awarded when the user presents the "AAA Member" point card even if the user does not present the "XXX Member" point card at the actual store. Conversely, the "AAA Member" points may be automatically awarded when the user presents the "XXX Member" point card even if the user does not present the "AAA Member" point card at the actual store.
[0145] [4. Fourth embodiment] For example, some online services offer a higher point redemption rate when a user meets certain conditions. In the fourth embodiment, a case will be described in which receivable points are generated each time a user uses such an online service until the certain conditions are met. When the certain conditions are met later, it is determined that the receiving conditions are met, and the user can receive the receivable points generated for past usage. In the fourth embodiment, a description of the same configuration as in the first to third embodiments will be omitted.
[0146] In the fourth embodiment, when a user becomes a member of the online shopping service, the user automatically becomes a member of the point service. Furthermore, in the fourth embodiment, the electronic commerce business providing the online shopping service and the point business providing the point service are the same. It can also be said that there exists a concept of membership for one large service that encompasses the online shopping service and the point service. The user is a member of this one large service.
[0147] For example, operators of online shopping services and point services are affiliated with a specific card company that issues credit cards. Hereinafter, this card company will be referred to as an affiliated card company. A credit card issued by an affiliated card company will be referred to as an affiliated credit card. A card company other than an affiliated card company will be referred to as another company. A credit card issued by another company will be referred to as a other company's credit card.
[0148] In the fourth embodiment, when a user uses an affiliated credit card for an online shopping service, the point redemption rate is higher than when a credit card of another company is used. Based on the high point redemption rate in the online shopping service, the affiliated card company uses banner advertisements or campaigns to appeal to users who do not have an affiliated credit card to issue the affiliated credit card. Issuing an affiliated credit card is equivalent to becoming a member of the credit card service provided by the affiliated card company (i.e., joining the affiliated credit card).
[0149] In this respect, even if a user who does not have an affiliated credit card issues an affiliated credit card, the only benefit is that the point redemption rate for future purchases will be higher, and this does not have a sufficient appealing effect. Although a certain amount of points may be given to users as a bonus when an affiliated credit card is issued, this is not a sufficient appealing effect because various card companies offer similar bonuses.
[0150] Therefore, the reward granting system S of the fourth embodiment uses the processes of the first to third embodiments when a user who does not have an affiliated credit card makes a purchase at an online shopping service, and generates receivable points that would have been received if the user had an affiliated credit card. When the user issues an affiliated credit card, the user can receive receivable points retroactively for past purchases. This increases the appeal of affiliated credit cards to users.
[0151] FIG. 13 is a diagram showing an example of a chronological flow until a user issues an affiliated credit card. For example, assume that a user becomes a member of an online shopping service on February 1, 2022. As described above, the user automatically becomes a member of the point service as well. For example, assume that the point balance immediately after membership registration is 0 points. The rebate rate of the other company's credit card is 1%, and the rebate rate of the affiliated credit card is 1.5%.
[0152] For example, assume that a user makes a purchase of 5,000 yen with a credit card of another company on February 9, 2022. As in the first embodiment, points may be awarded after a certain amount of time has passed, but here, points are awarded immediately. The amount used for this purchase is 5,000 yen, and the rebate rate of the credit card of the other company is 1%, so 50 points are awarded. The point balance goes from 0 points to 50 points.
[0153] For example, if a user uses an affiliated credit card for shopping on February 9, 2022, the affiliated credit card's rebate rate is 1.5%, so 75 points should have been awarded. Therefore, 25 receivable points are generated, which is the difference between the 75 points that should have been awarded and the 50 points that were actually awarded. The 25 receivable points are associated with the user's membership ID and stored in the provisional benefit database DB2.
[0154] Similarly, receivable points are generated for purchases made by the user up until the time the user issues the affiliated credit card. In the example of FIG. 13, 60 receivable points are generated for a purchase of 12,000 yen on February 16, 2022. 30 receivable points are generated for a purchase of 6,000 yen on February 21, 2022. Receivable points are generated and added at the rate of 0.5%, which is the difference in the rebate rate. Points equivalent to 1%, which is the rebate rate of the other company's credit card, are awarded immediately and added to the point balance.
[0155] For example, suppose a user issues an affiliated credit card on February 25, 2022. In this case, as a bonus for issuing an affiliated credit card, the user will be awarded 115 points, which is the total value of receivable points generated in the past. In other words, points are awarded retroactively so that the user can receive points under the same conditions as if the user had used the affiliated credit card for a past purchase.
[0156] The functional block diagram of the fourth embodiment is similar to that of the first to third embodiments. However, some functions are different from those of the first to third embodiments. For example, the temporary reward generation unit 202 associates a member ID that can identify a user in the online shopping service and the point service with the generated receivable points and registers them in the temporary reward database DB2. The method of generating receivable points is the same as that of the third embodiment, but in the fourth embodiment, since the user is a member of the online shopping service and the point service, the receivable points are associated with the member ID instead of the receiving ID.
[0157] The receiving condition determination unit 204 determines whether the receiving conditions are met by determining whether the user has become a member of the credit card service. Issuing an affiliated credit card corresponds to becoming a member of the credit card service. In the fourth embodiment, the credit card service corresponds to the other service. In the fourth embodiment, the user enters the member IDs of the online shopping service and the point service, and then issues an affiliated credit card. The receiving condition determination unit 204 receives the member ID of the user who has been issued the affiliated credit card from the server computer of the affiliated card company. The receiving condition determination unit 204 determines whether the user has become a member of the credit card service based on this member ID.
[0158] When it is determined that the user has become a member of the credit card service, the provisional benefit granting unit 205 grants the user receivable points associated with the member ID. This embodiment differs from the first to third embodiments in that receivable points associated with the member ID, not with the receiving ID, are granted, but the method of granting the receivable points is the same as the first to third embodiments.
[0159] The reward 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 the credit card service. This increases the appeal of becoming a member of the credit card service. From the user's perspective, since receivable points are granted retroactively, it is more convenient.
[0160] [5. Modifications] The present disclosure is not limited to the first to fourth embodiments described above, and may be modified as appropriate without departing from the spirit and scope of the present disclosure.
[0161] 14 is a diagram showing an example of functional blocks in a modified example. A first limiting unit 207, a second limiting unit 208, a third limiting unit 209, a fourth limiting unit 210, a first presenting unit 211, a second presenting unit 212, and a third presenting unit 213 are realized mainly by the control unit 21.
[0162] [5-1. Variation 1] For example, some users may throw away the receipt R3 described in the first embodiment in a bin for unnecessary receipts or a trash can at a store. A malicious third party may obtain a large number of receipts R3 from a store or other place and attempt to illegally receive receivable points from their own user terminal 50. Such fraudulent acts are contrary to the purpose of the point service and are also undesirable in terms of crime prevention at stores or other places.
[0163] Therefore, in order to prevent fraudulent acts by a third party, certain restrictions may be placed on the receivable points. In the first variant, the temporary benefit generation unit 202 sets an expiration date for the generated receivable points. The expiration date is the date by which the receivable points are valid. The expiration date can also be said to be the date by which the receivable points can be received. The expiration date is a certain time after the receivable points are generated.
[0164] Hereinafter, the length of the period from when the receivable points are generated until the expiration date is referred to as the expiration date length. In the first modified example, a case where the expiration date length is two weeks will be described, but the expiration date length may be any length. For example, the expiration date length may be about several minutes to several days, or about one week to six months. The expiration date length may be fixed or variable. For example, the expiration date length may differ depending on the type or area of the physical store.
[0165] For example, the length of the expiration date may vary depending on the amount used. If the expiration date is made shorter as the amount used increases, the deterrent effect against fraudulent activities will increase. However, this will decrease convenience for users, so conversely, the expiration date may be made longer as the amount used increases. Since there is a trade-off between deterrence against fraudulent activities and user convenience, the length of the expiration date may be set according to the requests of the administrator of the reward granting system S, the person in charge at the physical store, etc.
[0166] The temporary reward database DB2 of the first modified example also stores the expiration date of the receivable points. For example, when the temporary reward generation unit 202 generates the receivable points, it determines the expiration date to be set for the receivable points. The temporary reward generation unit 202 may determine the expiration date before generating the receivable points. For example, the temporary reward generation unit 202 determines the expiration date to be a point two weeks after the current date and time when the process of determining the expiration date is executed. The current date and time may be obtained using a real-time clock or a GPS signal, etc. The temporary reward generation unit 202 stores the receiving ID, expiration date, receivable points, and service usage history in the temporary reward database DB2 in association with each other.
[0167] The receiving condition determination unit 204 determines whether the receiving conditions are met by determining whether the receiving ID is acquired from the user terminal 50 within the expiration date. The receiving condition determination unit 204 references the temporary bonus database DB2 and acquires the expiration date associated with the receiving ID. The receiving condition determination unit 204 determines whether the acquired expiration date has passed based on the current date and time. If the current date and time is later than the expiration date, the receiving condition determination unit 204 determines that the expiration date has passed. If the expiration date has passed, receivable points are not awarded even if the receiving ID is stored in the temporary bonus database DB2.
[0168] Records of receivable points whose expiration date has passed may be deleted from the temporary bonus database DB2. In this case, the receipt ID whose expiration date has passed will no longer exist in the temporary bonus database DB2, so even if a receipt ID for receivable points whose expiration date has passed is obtained, the receivable points will not be granted. Whether or not the expiration date of receivable points stored in the temporary bonus database DB2 has passed may be determined periodically by an overnight batch or the like. Receivable points whose expiration date has passed may not be deleted from the temporary bonus database DB2, but may be managed by a flag or the like indicating whether or not the expiration date has passed.
[0169] The reward granting system S of the first modification determines whether the receiving condition is met by determining whether the receiving ID is obtained from the user terminal 50 within the expiration date. This acts as a deterrent against malicious third parties, preventing fraudulent activities. Even if the prevention of fraudulent activities is not the objective, it can prevent a situation in which receivable points that are not received are left indefinitely in the temporary reward database DB2 if the user discards the receipt R3.
[0170] [5-2. Variation 2] For example, methods for preventing fraudulent activities by malicious third parties are not limited to the method described in Variation 1. Variation 2 describes a case in which an upper limit is set on the receivable points that can be received with a certain member ID during a certain period of time. Even if a malicious third party illegally obtains a large number of receipts R3, they will not be able to receive more than a certain number of receivable points due to the upper limit described in Variation 2. In Variation 2, this upper limit is set to act as a deterrent against fraudulent activities. Anyone who has been issued a member ID will be recognized as a user by the system, whether they are a legitimate user or a malicious third party, so the word "user" does not necessarily refer to a legitimate user.
[0171] In the second modification, the point history stored in the privilege database DB1 also includes the history of receivable points granted to a certain member ID. When the temporary privilege granting unit 205 grants receivable points to a certain user, the temporary privilege granting unit 205 stores the granted receivable points and the grant date and time of the receivable points in the privilege database DB1 as the point history associated with the member ID of the user. The grant date and time is the current date and time when the process of granting the receivable points is executed.
[0172] The privilege granting system S of the second modification includes a first limiting unit 207. The first limiting unit 207 determines whether the receivable points granted to a user within a predetermined period have reached an upper limit. The predetermined period may be the entire past period, but in the second modification, it is a part of the most recent period. In the second modification, the predetermined period is the most recent one week, but the length of the predetermined period may be any length. For example, the predetermined period may be about several hours to several days, or may be longer than one week.
[0173] The upper limit is information equivalent to a threshold value for limiting the awarding of receivable points. For example, the upper limit is the maximum number of times that receivable points can be awarded. For example, the upper limit is the maximum number of points that can be awarded. In variant example 2, a case is described in which both the maximum number of times and the maximum number of points are used, but only one of the maximum number of times or the maximum number of points may be used.
[0174] For example, when it is determined that a certain user meets the receiving conditions, the first limiting unit 207 refers to the privilege database DB1 and acquires the point history of this user. The first limiting unit 207 determines whether or not the upper limit has been reached based on the acquired point history. For example, the first limiting unit 207 tallies the number of times that receivable points have been granted to this user in the most recent week and the total number of points based on the point history of this user. The first limiting unit 207 determines whether or not the number of times that points have been granted has reached the upper limit. The first limiting unit 207 determines whether or not the total number of points has reached the upper limit number of points.
[0175] The first limiting unit 207 limits the granting of receivable points to the user when it is determined that the upper limit has been reached. The limit here means not granting receivable points to the user. In other words, prohibiting the granting of receivable points to the user corresponds to the limit. For example, the first limiting unit 207 limits the granting of receivable points to the user when it is determined that the number of grants has reached the upper limit. For example, the first limiting unit 207 limits the granting of receivable points to the user when it is determined that the number of granted points has reached the upper limit point number. The first limiting unit 207 does not limit the granting of receivable points to the user when it is not determined that the upper limit has been reached.
[0176] The reward granting system S of the second modification restricts the granting of receivable points to a user when it is determined that the receivable points granted to the user within a predetermined period of time have reached the upper limit. This acts as a deterrent against malicious third parties, thereby preventing fraudulent acts.
[0177] [5-3. Variation 3] For example, the method of preventing fraudulent acts by malicious third parties is not limited to the method described in Modification 1-2. In Modification 3, a case will be described in which if the location relationship between the actual store that printed receipt R3 and the user's usual location is unnatural, the points that can be received are not awarded.
[0178] For example, suppose a malicious third party uses a resale site or the like to sell a large number of receipts R3 obtained illegally from a nearby brick-and-mortar store to another third party located far away. Since the other third party is located far away from the brick-and-mortar store, even if the third party reads the receiving code C310, the receiving points will not be awarded. In the third modification, the spatial relationship between the brick-and-mortar store where the receipt R3 was printed and the person to whom the receiving points are to be awarded acts as a deterrent against fraudulent acts.
[0179] In the third variant, the service usage history stored in the provisional benefit database DB2 includes location information on the location of the physical store. The location information of the physical store may be stored in another database, not in the service usage history. In this case, the service usage history includes the store ID of the physical store. The location information stored in the other database may be obtained using this store ID. The location information itself may be various information, and may be, for example, latitude and longitude information, coordinate information, an address, or a postal code.
[0180] The reward system S includes a second restriction unit 208. The second restriction unit 208 determines whether a first location related to the brick-and-mortar store corresponds to a second location related to the user. The first location is a location where the brick-and-mortar store is located. The second location is a location associated with the user. For example, the second location is an address registered by the user in a point service, a center of multiple brick-and-mortar stores where the user used retail services, or a location of the user terminal 50. The location of the user terminal 50 may be acquired by a GNSS such as GPS, or may be acquired using a mobile base station or an access point.
[0181] 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 limiting unit 208 acquires first location information related to the first location and second location information related to the second location. The second limiting 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 limiting unit 208 determines whether this distance is equal to or greater than a threshold. If it is determined that this distance is equal to or greater than the threshold, the second limiting unit 208 determines that the first location and the second location do not correspond to each other, and if it is determined that this distance is less than the threshold, the second limiting unit 208 determines that the first location and the second location correspond to each other.
[0182] The second restriction unit 208 restricts the granting of receivable points to the user when it is determined that the first location and the second location do not correspond to each other. The meaning of the restriction is as explained in Modification 2. 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 to each other.
[0183] The reward system S of the third modification restricts the reward points from being given to the user when it is determined that the first location of the actual store and the second location of the user do not correspond to each other. This provides a deterrent against malicious third parties, thereby preventing fraudulent acts.
[0184] [5-4. Variation 4] For example, the method of preventing fraudulent acts by malicious third parties is not limited to the method described in Modification 1-3. Modification 4 describes a case where, when a user attempts to receive receivable points, if the relationship between the service usage history associated with the receivable points and the service usage history of previously granted receivable points is unnatural, the receivable points are restricted from being granted.
[0185] For example, suppose a malicious third party obtains a large number of receipts R3 from a bin for unnecessary receipts at a nearby brick-and-mortar store. The third party attempts to receive receivable points one after another from a large number of receipts R3 printed at the same brick-and-mortar store. This is unnatural, as it is difficult for a legitimate user to do this. In addition, it is unnatural, as it is difficult for a legitimate user to try to receive receivable points one after another from multiple receipts R3 on which details of the same product are printed. For this reason, in variant example 4, a deterrent against fraudulent activity is provided based on the service usage history at the time receipt R3 was printed.
[0186] In the fourth modification, even if the receivable points stored in the provisional reward database DB2 are granted, the record corresponding to the receivable points is not deleted. Instead, the provisional reward database DB2 stores granted information indicating whether the receivable points have been granted. When the receivable points are granted, the value of the granted information changes to indicate that the receivable points have been granted.
[0187] The privilege granting system S includes a third restriction unit 209. When a receiving ID is acquired from the user terminal 50, the third restriction unit 209 judges whether or not the usage history of the service corresponding to the acquired receiving ID is valid. The usage history being valid means that the service usage history satisfies a predetermined condition. This condition can be set to any condition. In the fourth modification, a condition judged based on a past service usage history and a current service usage history is given as an example, but other conditions may be used. For example, the condition may be judged based on a user's attribute and a current service usage history.
[0188] For example, the third restriction unit 209 judges whether or not a transaction is legitimate based on a certain user's past service usage history and the current service usage history of the user. The third restriction unit 209 judges whether or not the number of times that receivable points are consecutively awarded on receipts R3 from the same physical store is equal to or greater than a threshold. For example, the third restriction unit 209 may judge whether or not the number of times that receivable points are consecutively awarded on receipts R3 on which details of the same product are printed is equal to or greater than a threshold. If it is determined that these numbers are equal to or greater than the threshold, the third restriction unit 209 does not judge the transaction to be legitimate, and if it is determined that these numbers are less than the threshold, the third restriction unit 209 judges the transaction to be legitimate.
[0189] 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 Modification 2. For example, the third restriction unit 209 does not restrict the granting of receivable points to the user when the usage history is determined to be valid.
[0190] The reward granting system S of the fourth modification restricts the granting of receivable points to a user when the service usage history corresponding to the receiving ID acquired from the user terminal 50 is not determined to be valid. This acts as a deterrent against malicious third parties, thereby preventing fraudulent acts.
[0191] [5-5. Variation 5] For example, the method of preventing fraudulent acts by malicious third parties is not limited to the methods described in Modifications 1 to 4. Modification 5 describes a case in which, when a user attempts to receive receivable points, if the user information registered in the retail service does not match the user information registered in the point service, the receivable points are not granted.
[0192] In the fifth variant, the user is a member of the retail service. The user is also registered as a member of the retail service. When shopping at a physical store, the user can accumulate both points unique to the retail service and points from the point service. This is the same as the example explained at the end of the third embodiment. If the user is a member of the retail service but not a member of the point service, receivable points can be awarded retroactively when the user becomes a member of the point service, as in the first embodiment. If the user forgets to present their point card, receivable points can be awarded retroactively, as in the second embodiment.
[0193] In the fifth modification, the data storage unit 100 of the store server 10 stores a membership database related to members of the retail service. This membership database stores user information such as the address and name that the user registered with the retail service. When a legitimate user reads the receipt code C310 on the receipt R3, the person who made the purchase indicated on the receipt R3 is the same as the person who is about to receive the receivable points, so the user information of the retail service matches the user information registered with the point service.
[0194] On the other hand, if a malicious third party reads the receiving code C310 on receipt R3, the person who made the purchase indicated on receipt R3 will be different from the person receiving the receivable points, and the user information for the retail service identified from receipt R3 will not match the user information registered with the point service. For this reason, in variant 5, if the user information does not match, a restriction is imposed so that receivable points are not awarded, thereby providing a deterrent against fraudulent activity.
[0195] The service usage history in the temporary benefit database DB2 also includes the user's membership ID in the retail service. The benefit management server 20 can use this membership ID to identify which member of the retail service has used the physical store. The receipt condition determination unit 204 determines whether or not a receipt ID has been obtained from a user terminal 50 that has logged in to a point service different from the retail service. This is the same as in the first to third embodiments. The benefit granting system S of the third modification includes a fourth restriction unit 210. The fourth restriction unit 210 determines whether or not the first membership information of the user in the retail service matches the second membership information of the user in the point service.
[0196] The fourth restriction unit 210 may compare only one item of the first member information and the second member information, or may compare multiple 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 compare other items such as a credit card number or an electronic money ID. A perfect match or a partial match may be required for the first member information and the second member information.
[0197] The fourth restriction unit 210 restricts the granting of receivable points to the user when it is determined that the first membership information and the second membership information do not match. The meaning of the restriction is as explained in Modification Example 3. The fourth restriction unit 210 does not restrict the granting of receivable points to the user when it is determined that the first membership information and the second membership information match.
[0198] The reward system S of the fifth modification restricts the granting of receivable points to a user when it is determined that the first member information of the user in the retail service and the second member information of the user in the point service do not match. This prevents fraudulent acts, even if a malicious third party attempts to receive receivable points by impersonating a legitimate user, because the information such as the name does not match.
[0199] [5-6. Variation 6] For example, in the example of the fourth embodiment, receivable points may be presented in advance to a user who has not issued an affiliated credit card. Although the configuration for presenting receivable points was not described in the fourth embodiment, the appealing effect of issuing an affiliated credit card can be obtained by the user being aware of the mechanism of the fourth embodiment itself. Therefore, even without the configuration of the modified example 6, the appealing effect described in the fourth embodiment can be obtained, but with the configuration of the modified example 6, a stronger appealing effect can be obtained.
[0200] Fig. 15 is a diagram showing an example of a screen displayed in Modification 6. The privilege granting system S includes a first presentation unit 211. The first presentation unit 211 presents receivable points to a user before the user becomes a member of another service. In the example of Fig. 15, when a link L80 on a top screen G8 of an online shopping service is selected, the first presentation unit 211 presents the receivable points to the user by displaying on the display unit 55 a points management screen G10 showing the receivable points associated with the user's membership ID.
[0201] The first presentation unit 211 is realized by the benefit management server 20, and therefore presents the receivable points to the user by transmitting data for displaying the points management screen G10 to the user terminal 50. For example, when the user selects link L100 on the points management screen G10, the user is connected to the website of the affiliated card company. The user issues an affiliated credit card from this website. The process of issuing an affiliated credit card may be a known process. The process by which the benefit management server 20 detects the issuance of an affiliated credit card is as described in the fourth embodiment.
[0202] The first presentation unit 211 may present the receivable points to the user using any screen other than the point management screen G10. The first presentation unit 211 may present the receivable points using any other medium. For example, the first presentation unit 211 may present the receivable points using email, a message in a messaging app, SNS, SMS, a banner advertisement, a receipt from a physical store, or voice. This point also applies to the second presentation unit 212 and the third presentation unit 213 described later.
[0203] The reward granting system S of the sixth modification presents the receivable points to the user before the user becomes a member of the credit card service, which makes it possible to more strongly urge the user to become a member of the credit card service.
[0204] [5-7. Variation 7] For example, in the sixth modification, the reward system S can handle a plurality of services other than the online shopping service. That is, there may be services other than the online shopping service that can provide rewards related to the affiliated credit card. In the sixth modification, the point redemption rate is increased when the affiliated credit card is used not only for the online shopping service but also for the electricity service, the travel reservation service, and the communication service.
[0205] The provisional reward granting unit 205 of the seventh modified example grants the user receivable points for each of a plurality of services when it is determined that the receiving conditions are satisfied. For example, when the user issues an affiliated credit card, the provisional reward granting unit 205 adds up the receivable points generated during past use of four services, namely, an online shopping service, an electricity service, a travel reservation service, and a communication service. The provisional reward granting unit 205 may grant the user the added up receivable points.
[0206] The method of generating receivable points when each service is used may use the same process as in the fourth embodiment. When a user uses each of a plurality of services, the provisional benefit generating unit 202 generates receivable points according to the content of the service used, and stores the points in the provisional benefit database DB2 in association with the user's membership ID. The service usage history in the provisional benefit database DB2 may include information that can identify the service used by the user.
[0207] The processing of the provisional benefit granting unit 205 differs from that of the fourth embodiment in that it adds up receivable points for a plurality of services, but the method of granting the receivable points itself is the same as that of the fourth embodiment. For example, if the receivable points for the online shopping service, the electricity service, the travel reservation service, and the communication service are 1420 points, 2580 points, 3000 points, and 1512 points, respectively, the provisional benefit granting unit 205 will grant the user, when an affiliated credit card is issued, 7512 points, which is the total value of these points, retroactively based on past use of these four services.
[0208] The reward system S of the seventh modification example provides the user with receivable points for each of a plurality of services when it is determined that the receiving conditions are met. This makes it more appealing to the user to become a member of the credit card service. From the user's perspective, the user can receive more receivable points, which increases convenience.
[0209] [5-8. Variation 8] For example, even when there are multiple services as in Variation 7, the receivable points to be awarded when the user issues an affiliated credit card may be presented as in Variation 6. The privilege awarding system S of Variation 8 includes a second presentation unit 212. The second presentation unit 212 presents to the user the total receivable points for each of the multiple services and the receivable points for each service. In Variation 8, as in Variation 6, the points are presented to the user on the points management screen G10.
[0210] Fig. 16 is a diagram showing an example of a points management screen G10 displayed in Modification 8. As shown in Fig. 16, the points management screen G10 displays the total receivable points generated in the past when four services, namely, an online shopping service, an electricity service, a travel reservation service, and a communication service, and the individual receivable points for each service. In the example of Fig. 16, the number of points exemplified in Modification 7 is displayed.
[0211] For example, when presenting the point management screen G10 to a certain user, the second presentation unit 212 refers to the provisional benefit database DB2 and acquires the receivable points and service usage history associated with the user's membership ID. Based on this information, the second presentation unit 212 tallies the receivable points for each service and calculates the total of the multiple receivable points. Based on these tallying and calculation results, the second presentation unit 212 displays the point management screen G10 of FIG. 16 on the display unit 55.
[0212] The privilege granting system S of the eighth modification example presents the total receivable points for each of a plurality of services and the receivable points for each service to the user. This makes it possible to strongly appeal to the user to become a member of the credit card service. From the user's perspective, it becomes easier to grasp the receivable points that can be received retroactively when an affiliated credit card is issued, which increases the user's convenience.
[0213] [5-9. Variation 9] For example, the reward system S that provides a mechanism like that of the fourth embodiment can handle a plurality of other services in addition to the credit card service. The receivable points generated when using the online shopping service may be provided to services other than the credit card service. In the ninth modification, the receivable points can be received not only when the user becomes a member of the credit card service but also when the user becomes a member of the communication service.
[0214] For example, if a user is not a member of either the credit card service or the communications service, the point redemption rate for the online shopping service is 1%. If the user becomes a member of the credit card service, the redemption rate increases by 0.5%, and if the user becomes a member of the communications service, the redemption rate increases by 1%. Therefore, if the user becomes a member of both the credit card service and the communications service, the redemption rate becomes 2.5%.
[0215] The credit card service and the communication service are examples of the other services. The number of the other services is not limited to two, and may be three or more. The provisional benefit generation unit 202 of the ninth modification registers a member ID and receivable points for each other service in the provisional benefit database DB2 in association with each other service. For example, when a user who is not a member of either the credit card service or the communication service uses an online shopping service, the provisional benefit generation unit 202 registers a numerical value obtained by multiplying the amount of use by 0.5% as the receivable points corresponding to the credit card service in the provisional benefit database DB2. The provisional benefit generation unit 202 registers a numerical value obtained by multiplying the amount of use by 1% as the receivable points corresponding to the communication service in the provisional benefit database DB2.
[0216] When it is determined that the user has become a member of any one of a plurality of other services, the provisional privilege granting unit 205 of the ninth modification grants the user receivable points associated with the member ID of the other service. For example, when the user has become a member of a credit card service, the provisional privilege granting unit 205 grants the user receivable points corresponding to the credit card service, which are associated with the user's member ID and registered in the provisional privilege database DB2. When the user has become a member of a communication service, the provisional privilege granting unit 205 grants the user receivable points corresponding to the communication service, which are associated with the user's member ID and registered in the provisional privilege database DB2.
[0217] The privilege granting system S of the ninth modification grants the user receivable points associated with the member ID of the other service when it is determined that the user has become a member of one of a plurality of other services. This increases the appeal of becoming a member of more other services. It also becomes easier for the user to receive receivable points, which increases convenience.
[0218] [5-10. Variation 10] For example, even when there are multiple other services as in Modification 9, receivable points to be granted when the user becomes a member of the other services may be presented as in Modification 6 or Modification 8. The privilege granting system S of Modification 10 includes a third presentation unit 213. The third presentation unit 213 presents to the user, for each other service, the receivable points to be granted when the user becomes a member of the other service. In Modification 10, as in Modification 6 or Modification 8, the points are presented to the user on the points management screen G10.
[0219] FIG. 17 is a diagram showing an example of a points management screen G10 displayed in Modification Example 10. As shown in FIG. 17, the points management screen G10 displays the total number of receivable points granted when a user becomes a member of two other services, a credit card service and a communication service, and the individual receivable points of each of the other services. In the example of FIG. 17, when a user becomes a member of the credit card service, 1500 receivable points are granted. When a user becomes a member of the communication service, 3000 receivable points are granted.
[0220] For example, when presenting the points management screen G10 to a certain user, the third presentation unit 213 refers to the provisional benefit database DB2 and obtains the receivable points for each other service associated with the user's membership ID. Based on this information, the third presentation unit 213 tallies up the receivable points for each other service and calculates the total of the multiple receivable points. Based on these tallied and calculated results, the second presentation unit 212 displays the points management screen G10 of FIG. 17 on the display unit 55.
[0221] The privilege granting system S of the modification 10 presents the user with the receivable points that will be granted if the user becomes a member of each other service. This makes it possible to more strongly appeal to the user to become a member of each of the multiple other services. It is also easier for the user to understand how many receivable points he or she can receive by becoming a member of which service, which increases convenience.
[0222] [5-11. Other variations] For example, the above-described modifications may be combined.
[0223] For example, a function described as being realized by the store server 10 may be realized by the benefit management server 20, the member management server 30, or another server computer. A function 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. A function described as being realized by the member management server 30 may be realized by the store server 10, the benefit management server 20, or another server computer. For example, a function described as being realized by one computer may be shared among multiple computers. Each function may be realized by at least one computer. [Explanation of symbols]
[0224] S reward system, N network, 10 store server, 11, 21, 31, 41, 51 control unit, 12, 22, 32, 42, 52 memory unit, 13, 23, 33, 43, 53 communication unit, 20 reward management server, 30 member management server, 40 store terminal, 50 user terminal, 44, 54 operation unit, 45, 55 display unit, 46 reading device, 47 output device, 56 reading unit, DB1 reward database, DB2 temporary reward database, DB3 member database, 100 data storage unit, 101 service provision unit, 102 output unit, 200 data storage unit, 201 usage determination unit, 202 temporary reward generation unit, 203 output unit, 204 receipt condition determination unit, 205 temporary reward grant unit, 206 reward grant unit, 207 first restriction unit, 208 Second restriction unit, 209, third restriction unit, 210, fourth restriction unit, 211, first presentation unit, 212, second presentation unit, 213, third presentation unit, 300, data storage unit, 301, member registration unit, 400, data storage unit, 401, service providing unit, 402, output unit, 500, data storage unit, 501, display control unit, 502, operation reception unit.
Claims
1. a usage determination unit that determines whether or not identification information capable of identifying a member of a service to which the physical store is affiliated has been received from a store terminal of the physical store used by the user; a server including a temporary reward generation unit that generates temporary reward identification information capable of identifying a temporary reward, which is a token on a blockchain network associated with the digital content, when it is determined that the identification information has not been received, and associates the temporary reward identification information with the temporary reward and registers the temporary reward in a database; a receiving condition determination unit that determines whether or not a receiving condition for receiving the provisional benefit is satisfied based on the provisional benefit identification information after the service is used; a provisional privilege granting unit that grants the provisional privilege associated with the provisional privilege identification information to the user when it is determined that the receiving condition is satisfied; A reward system including:
2. A server comprising: a usage determination step of determining whether or not identification information capable of identifying a member of a service to which the physical store is affiliated has been received from a store terminal of the physical store used by the user; a temporary reward generation step of generating temporary reward identification information capable of identifying a temporary reward, which is a token on a blockchain network associated with the digital content, when it is determined that the identification information has not been received, and associating the temporary reward identification information with the temporary reward and registering the temporary reward in a database; a receiving condition determination step of determining whether or not a receiving condition for receiving the provisional benefit is satisfied based on the provisional benefit identification information after the service is used; a provisional reward granting step of granting the provisional reward associated with the provisional reward identification information to the user when it is determined that the receiving condition is satisfied; A reward granting method that executes the above.
3. a usage determination unit that determines whether or not identification information capable of identifying a member of a service to which the physical store is affiliated has been received from a store terminal of the physical store used by the user; a temporary reward generation unit that generates temporary reward identification information capable of identifying a temporary reward, which is a token on a blockchain network associated with the digital content, when it is determined that the identification information has not been received, and associates the temporary reward identification information with the temporary reward and registers the temporary reward in a database; a receiving condition determining unit that determines whether or not a receiving condition for receiving the provisional benefit is satisfied based on the provisional benefit identification information after the service is used; a provisional privilege granting unit that grants the provisional privilege associated with the provisional privilege identification information to the user when it is determined that the receiving condition is satisfied; A program that functions as a server.
Citation Information
Patent Citations
Point service system
JP2006318163A
Point management method utilizing two-dimensional code
JP2008287347A
Point management device, control method, and program
JP2017054282A
Information processing equipment, point providing method, and program
JP2018055564A
Member information management server giving privilege for personal information registration and method for managing member information
JP2018136724A
