Reward server, reward granting system, reward granting method, and program

Abstract

To accurately identify a user to whom a reward is to be granted without causing user trouble.SOLUTION: A reward granting system (1) comprises: a check-in information acquisition unit (301) for acquiring check-in information including check-in user information and check-in time information; a payment information acquisition unit (302) for acquiring payment information including payment user information and payment time information; and a reward granting unit (304) for granting a reward to a granting target user who has both checked in and made a payment at a check-in location within a predetermined period of time, based on the check-in information and the payment information.SELECTED DRAWING: Figure 4

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 is known a technique for providing a privilege to a user who checks in to a place such as a store. For example, Patent Document 1 describes a point-granting system that acquires, from a mobile terminal that receives beacon information transmitted by a beacon transmitter of a cash register when registering an item, predetermined information and user information contained in the beacon information, and the date and time of reception of the beacon information, acquires predetermined information contained in the beacon information transmitted from the cash register when registering an item, product purchase information based on the product registration, and the date and time of the product registration, and identifies a user corresponding to the product purchase information based on the information and grants points. [Prior art documents] [Patent documents]

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

[0004] However, the point-granting system of Patent Document 1 identifies the user corresponding to the product purchase information based on the date and time of receiving the beacon information and the date and time of product registration, so there is a possibility that a stranger in the vicinity may be erroneously detected as the user corresponding to the product purchase information. There is also a possibility that a malicious third party may use a mobile terminal capable of receiving the beacon information to impersonate the user corresponding to the product purchase information. For this reason, there is a demand for accurately identifying the user to whom the privilege is to be granted without causing the user trouble.

[0005] One of the objectives of the present disclosure is to accurately identify users to whom rewards will be granted without causing any effort on the part of the users. [Means for solving the problem]

[0006] The point-granting system of the present disclosure includes a check-in information acquisition unit that acquires check-in information including check-in user information regarding a check-in user who has checked in at a specified check-in location and check-in time information regarding the check-in time at which the check-in occurred, a payment information acquisition unit that acquires payment information including payment user information regarding a payment user who has made a payment at the check-in location and payment time information regarding the payment time at which the payment was made, and a bonus granting unit that grants a bonus to a bonus-granting eligible user who has both checked in and made the payment at the check-in location within a specified period of time based on the check-in information and the payment information. Effect of the Invention

[0007] The present disclosure, for example, makes it possible to accurately identify users to whom benefits will be granted without causing the users any trouble. [Brief description of the drawings]

[0008] [Figure 1] FIG. 2 is a diagram illustrating an example of a hardware configuration of the privilege granting system. [Diagram 2] FIG. 1 is a diagram showing an example of a check-in location. [Diagram 3] FIG. 13 is a diagram illustrating an example of a screen displayed on a user terminal. [Figure 4] FIG. 2 is a diagram illustrating an example of functions realized by the privilege granting system. [Diagram 5] FIG. 2 is a diagram illustrating an example of a check-in database. [Figure 6] FIG. 13 is a diagram illustrating an example of a payment database. [Figure 7] FIG. 13 is a diagram showing an example of a benefit database. [Figure 8]FIG. 2 is a diagram illustrating an example of a process executed in the privilege granting system. [Figure 9] FIG. 13 is a diagram illustrating an example of a function realized in a modified example. [Figure 10] FIG. 23 is a diagram showing an example of functions realized by a privilege granting system of a seventh modified example. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] [1. Hardware configuration of the reward system] An example of an embodiment of a reward granting system, a reward granting method, and a program according to the present disclosure will be described.

[0010] 1 is a diagram showing an example of the hardware configuration of a reward granting system. For example, the reward granting system 1 includes a check-in server 10, a payment server 20, a reward server 30, a check-in terminal 40, a payment terminal 50, and a user terminal 60. Each of the check-in server 10, the payment server 20, the reward server 30, the check-in terminal 40, the payment terminal 50, and the user terminal 60 is connected to a network N such as the Internet or a LAN.

[0011] The check-in server 10 is a server computer for the check-in service. The check-in service is a service that accepts user check-ins at a specified location. Hereinafter, the location that is the subject of check-in is referred to as a check-in location. A check-in location is a location managed by a member who is a member of the check-in service. For example, a member joins the check-in service in order to increase the customer attraction effect of the check-in location that he or she manages. When a user checks in at a check-in location, the user can obtain a benefit corresponding to the check-in location.

[0012] In this embodiment, the user can not only check in but also make a payment at the check-in location. For example, the user makes a payment when purchasing a product sold at the check-in location or using a service provided at the check-in location. The check-in location may be any location where check-in and payment are possible. For example, the check-in location may be a store, accommodation facility, shopping mall, event venue, public facility, tourist facility, or other facility. The check-in location may be outdoors as well as indoors.

[0013] For example, the check-in server 10 includes a control unit 11, a storage unit 12, and a communication unit 13. The control unit 11 includes at least one processor. The storage unit 12 includes at least one of 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 payment server 20 is a server computer of the payment service. The payment service is a service related to electronic payment (cashless payment). In this embodiment, the members of the check-in service are also members of the payment service. The payment means available to the user in the payment service may be any means. For example, the user may be able to use a credit card, electronic money, points, a bank account, an account other than a bank account, cryptocurrency, or other payment means in the payment service. For example, the payment server 20 includes a control unit 21, a memory unit 22, and a communication unit 23. The hardware configurations of the control unit 21, the memory unit 22, and the communication unit 23 may be similar to those of the control unit 11, the memory unit 12, and the communication unit 13, respectively.

[0015] The reward server 30 is a server computer for a reward service. The reward service is a service that manages rewards granted to users. A reward is a benefit for a user. A reward may be any reward. For example, a reward may be points, electronic money, coupons, lottery tickets, free product vouchers, free service vouchers, or other rewards. In this embodiment, members of the check-in service are also members of the reward service. For example, the reward server 30 includes a control unit 31, a memory unit 32, and a communication unit 33. The hardware configurations of the control unit 31, the memory unit 32, and the communication unit 33 may be similar to those of the control unit 11, the memory unit 12, and the communication unit 13, respectively.

[0016] The check-in terminal 40 is a computer at the check-in location. For example, the check-in terminal 40 is a personal computer, a tablet, or a smartphone. The check-in terminal 40 includes a control unit 41, a memory unit 42, a communication unit 43, an operation unit 44, a display unit 45, and an ultrasonic generator 46. The hardware configurations of the control unit 41, the memory unit 42, and the communication unit 43 may be similar to those of the control unit 11, the memory unit 12, and the communication unit 13, respectively. For example, the operation unit 44 is an input device such as a touch panel or a button. The display unit 45 is a display such as a liquid crystal or organic EL. The ultrasonic generator 46 is a speaker capable of generating ultrasonic waves.

[0017] In this embodiment, an example is given in which ultrasonic waves generated by the ultrasonic generating unit 46 are used for check-in. The mechanism of check-in may be a known mechanism. For example, check-in may be performed using a beacon that does not have a calculation function and only has a transmission function, instead of the check-in terminal 40. Furthermore, the mechanism of check-in is not limited to a method using ultrasonic waves. When a method other than ultrasonic waves is used for check-in, the check-in terminal 40 may include hardware corresponding to the other method. For example, when a camera is used for check-in, the check-in terminal 40 includes a camera. When short-range wireless communication is used for check-in, the communication unit 43 is capable of short-range wireless communication. In particular, the check-in terminal 40 may not be used, and only the user terminal 60 may be used for check-in. For example, check-in may be performed based on location information acquired by the user terminal 60 using a GPS or the like.

[0018] The payment terminal 50 is a computer at the check-in location. For example, the payment terminal 50 is a POS terminal, a handheld terminal, a tablet, a smartphone, or a personal computer. The payment terminal 50 includes a control unit 51, a memory unit 52, a communication unit 53, an operation unit 54, a display unit 55, and an imaging unit 56. The hardware configurations of the control unit 51, the memory unit 52, the communication unit 53, the operation unit 54, and the display unit 55 may be similar to those of the control unit 11, the memory unit 12, the communication unit 13, the operation unit 44, and the display unit 45, respectively.

[0019] For example, the photographing unit 56 includes at least one camera. The payment terminal 50 may include other hardware used in payment. For example, the payment terminal 50 may include a code reader that reads at least one of a barcode and a two-dimensional code, a device that can read and write at least one of an IC chip of the user terminal 60, a device that can read and write at least one of a physical card such as a credit card or a point card, or other devices. A short-range wireless communication function of the communication unit 54 may be used in payment.

[0020] The user terminal 60 is a user's computer. For example, the user terminal 60 is a smartphone, a tablet, a personal computer, or a wearable terminal. For example, the user terminal 60 includes a control unit 61, a storage unit 62, a communication unit 63, an operation unit 64, a display unit 65, an imaging unit 66, and an ultrasonic detection unit 67. The hardware configurations of the control unit 61, the storage unit 62, the communication unit 63, the operation unit 64, the display unit 65, and the imaging unit 66 may be similar to those of the control unit 11, the storage unit 12, the communication unit 13, the operation unit 44, the display unit 45, and the imaging unit 56, respectively.

[0021] For example, the ultrasonic detection unit 67 is a microphone capable of detecting ultrasonic waves. The user terminal 60 may include other hardware used for at least one of check-in and payment. For example, the user terminal 60 may include an IC chip used for at least one of check-in and payment. A short-range wireless communication function of the communication unit 63 may be used for at least one of check-in and payment.

[0022] The programs stored in the storage units 12, 22, 32, 42, 52, and 62 may be supplied to each of the check-in server 10, the payment server 20, the privilege server 30, the check-in terminal 40, the payment terminal 50, and the user terminal 60 via the network N. Also, at least one of a reading unit (e.g., a memory cart slot) that reads a computer-readable information storage medium and an input / output unit (e.g., a USB port) for inputting and outputting data to and from an external device may be included in each of the check-in server 10, the payment server 20, the privilege server 30, the check-in terminal 40, the payment terminal 50, and the user terminal 60. For example, a program stored in an information storage medium may be supplied to each of the check-in server 10, the payment server 20, the privilege server 30, the check-in terminal 40, the payment terminal 50, and the user terminal 60 via at least one of the reading unit and the input / output unit.

[0023] Furthermore, the reward-granting system 1 only needs to include at least one computer. The computers included in the reward-granting system 1 are not limited to the example of FIG. 1. For example, the reward-granting system 1 may include only the check-in server 10. In this case, the payment server 20, the reward server 30, the check-in terminal 40, the payment terminal 50, and the user terminal 60 are external to the reward-granting system 1. The reward-granting system 1 may include only the check-in server 10, the payment server 20, and the reward server 30. In this case, the check-in terminal 40, the payment terminal 50, and the user terminal 60 are external to the reward-granting system 1. The reward-granting system 1 may include other computers not shown in FIG. 1.

[0024] [2. Overview of the reward system] In this embodiment, the user uses each of the check-in service, payment service, and special offer service from a dedicated application installed on the user terminal 60. For example, a check-in app that is an application for the user to use the check-in service and a payment app that is an application for the user to use the payment service are installed on the user terminal 60. The user can also use the special offer service from each of the check-in app and the payment app. The user may use these services from a browser instead of the dedicated application.

[0025] Fig. 2 is a diagram showing an example of a check-in location. In the example at the top of Fig. 2, a user checks in to the check-in location using a check-in app, and then makes a payment at the check-in location using a payment app. For example, when a user selects the check-in app on user terminal 60, the check-in app starts up. The user performs an operation for check-in on the check-in app.

[0026] 3 is a diagram showing an example of a screen displayed on the user terminal 60. For example, when a check-in app is launched, the user terminal 60 displays a list screen SC1 showing a list of nearby check-in locations on the display unit 65. When the user selects an arbitrary check-in location from the list screen SC1, the ultrasonic detection unit 67 is launched. When the ultrasonic detection unit 67 detects ultrasonic waves generated by the ultrasonic generation unit 46 of the check-in terminal 40, the check-in is completed. The flow of check-in using ultrasonic waves may be a known flow.

[0027] For example, when a user checks in at a check-in location, the user terminal 60 displays a check-in completion screen SC2 on the display unit 65, indicating that check-in has been completed, as shown in the upper right corner of FIG. 3. When a user checks in at a check-in location, the user acquires a benefit. Note that a benefit does not necessarily have to be awarded in the check-in service. In the example of FIG. 3, the user can draw a lottery as a benefit for checking in. After checking in, the user makes a payment to purchase a product at the check-in location or to use a service at the check-in location.

[0028] For example, when a user selects a payment app on the user terminal 60, the payment app is launched. When the payment app is launched, the user terminal 60 displays a code screen SC3 including a code C30 required for payment on the display unit 65, as shown in the lower left of Fig. 3. The code C30 is generated based on information that can temporarily identify a user in the payment service. The flow of payment using the code C30 may be a known flow.

[0029] For example, when the user selects button B31, the user terminal 60 displays a code screen SC4 including a code C40 as a point card for a special service on the display unit 65, as shown in the lower right of FIG. 3. For example, a point card is a card that allows a user to earn points according to the amount of payment. The code C40 is generated based on information that can temporarily identify a user in a special service. The flow of granting a special benefit using the code C40 may be a known flow. When the user selects button B41, the display returns to the code screen SC3 in the lower left of FIG. 3.

[0030] In this embodiment, the code C30 for payment is not used as a point card. For example, a user who does not use the check-in service needs to select the button B31 to display the code C40 on the display unit 65 in order to use the point card at the check-in location. After the user has the payment terminal 50 read the code C40, the user returns to the code screen SC3 again and has the payment terminal 50 read the code C30. In this case, the user's operation and the operation of the store clerk at the check-in location become complicated.

[0031] Therefore, the reward granting system 1 of this embodiment is configured to identify which point card a user holding in the store has by the user checking in. This allows the reward granting system 1 to identify which point card a user has by checking in, even if the user does not present the code C40 of the point card. When payment is completed, the user can earn points according to the payment amount, even if the code C40 is not read by the payment terminal 50.

[0032] In addition, the user may check in after making a payment. For example, as shown in the lower part of FIG. 2, the user may check in at the check-in location using the check-in app after making a payment at the check-in location using the payment app. Even if the user checks in from the list screen SC1 after making a payment using the code screen SC3, the user can earn points according to the payment amount without presenting the code C40. However, in this embodiment, the user may check in or make a payment first, but both check in and payment must be made on the same day. Details of this embodiment will be described below.

[0033] [3. Functions realized by the reward system] FIG. 4 is a diagram showing an example of functions realized by the reward granting system 1. Hereinafter, a user in the check-in service is referred to as a check-in user. A user in the payment service is referred to as a payment user. A user in the reward service is referred to as a reward user. A user who is eligible to be awarded points according to the payment amount is referred to as a reward target user. When there is no need to distinguish between a check-in user, a payment user, a reward user, and a reward target user, they are simply referred to as users.

[0034] [3-1. Functions realized by the check-in server] For example, the check-in server 10 includes a data storage unit 100 and a check-in execution unit 101. The data storage unit 100 is realized by the storage unit 12. The check-in execution unit 101 is realized by the control unit 11.

[0035] [Data storage section] The data storage unit 100 stores data necessary for providing a check-in service. For example, the data storage unit 100 stores a check-in database DB1.

[0036] FIG. 5 is a diagram showing an example of the check-in database DB1. The check-in database DB3 described later may have the same data structure as that of FIG. 5. The check-in database DB1 is a database in which check-in information related to check-ins performed by check-in users is stored. The check-in information can also be said to be information indicating the results of check-in execution. The check-in information may be publicly known information adopted in a publicly known check-in service. Any information may be stored in the check-in database DB1. The information stored in the check-in database DB1 is not limited to the example of FIG. 5. For example, the check-in database DB1 may store personal information registered by a user in a check-in service.

[0037] For example, the check-in information includes check-in user information and check-in time information. In this embodiment, the check-in information further includes check-in location information. The check-in information does not have to include check-in location information.

[0038] Check-in user information is information about a check-in user. Check-in user information is information that can identify a check-in user. For example, check-in user information is letters, numbers, other symbols, or a combination of these. For example, check-in user information may be a user's login account in a check-in service, a temporary ID issued to the user by the check-in server 10, the user's email address, the user's phone number, or other information.

[0039] Check-in time information is information relating to the check-in time when check-in occurred. Check-in time information is information capable of identifying the check-in time. Check-in time information is information that pinpoints the check-in time, or information that indicates a period including the check-in time. In this embodiment, an example is given in which the check-in time information indicates the date and time (a combination of date and time) when check-in occurred. Check-in time information may be information that directly or indirectly indicates the check-in time. Check-in time information is not limited to date and time. For example, check-in time information may indicate only the day when check-in occurred, only the day of the week when check-in occurred, only the time when check-in occurred, or only the time period when check-in occurred.

[0040] The check-in location information is information related to the check-in location where the check-in took place. The check-in location information is information that can identify the check-in location. In this embodiment, an example is given in which an ID that can identify the check-in location corresponds to the check-in location information. The check-in location information may be any information related to the check-in location. For example, the check-in location information may be the name, address, latitude and longitude, telephone number, email address, or other information of the location where the check-in took place.

[0041] The data stored in the data storage unit 100 is not limited to the above examples. The data storage unit 100 may store any data necessary for the check-in service. For example, the data storage unit 100 may store a database indicating benefits that a user can obtain by checking in. The data storage unit 100 may store a database indicating a relationship between a check-in location and an ultrasonic wave pattern generated from the check-in terminal 40 at the check-in location. The check-in execution unit may identify which check-in location the check-in user has checked in to based on the relationship and the ultrasonic wave pattern detected by the user terminal 60.

[0042] [Check-in Execution Department] The check-in execution unit 101 executes processing for a check-in user to check in at a check-in location. For example, when the ultrasonic detection unit 67 detects ultrasonic waves generated by the ultrasonic generation unit 46 of the check-in terminal 40, the user terminal 60 transmits a check-in request to the check-in server 10. The check-in request is data in a predetermined format indicating a check-in request. The check-in server 10 receives the check-in request from the user terminal 60. The check-in request may be transmitted by a computer other than the user terminal 60 (for example, the check-in terminal 40 or the payment terminal 50).

[0043] For example, the check-in request includes check-in user information stored in the user terminal 60 and pattern information indicating the pattern of ultrasound generated by the ultrasound generator 46. The check-in execution unit 101 acquires check-in location information of the check-in location where the check-in user will check in based on the pattern information. The check-in execution unit 101 adds the check-in information, including the check-in user information included in the check-in request, check-in time information indicating the current date and time, and check-in location information acquired based on the pattern information, to the check-in database DB1. Note that when the user terminal 60 specifies the check-in location, the check-in request may include check-in location information.

[0044] The process executed by the check-in execution unit 101 may be a process adopted in a known check-in service. For example, the check-in execution unit 101 may execute the check-in process based on check-in user information acquired by the check-in terminal 40 capturing an image of some code displayed on the user terminal 60 with a camera, check-in user information acquired by the check-in terminal 40 from the user terminal 60 through short-range wireless communication, location information acquired from the user terminal 60, information read by the check-in terminal 40 from the user terminal 60, information read by the user terminal 60 from the check-in terminal 40, or other information.

[0045] [3-2. Functions realized by the payment server] For example, the payment server 20 includes a data storage unit 200 and a payment execution unit 201. The data storage unit 200 is realized by the storage unit 22. The payment execution unit 201 is realized by the control unit 21.

[0046] [Data storage section] The data storage unit 200 stores data necessary for providing a payment service. For example, the data storage unit 200 stores a payment database DB2.

[0047] FIG. 6 is a diagram showing an example of a payment database DB2. A payment database DB4 described later may have the same data structure as that of FIG. 6. The payment database DB2 is a database in which payment information relating to a payment made by a payment user is stored. The payment information may also be information indicating the execution result of a payment. The payment information may be publicly known information adopted in a publicly known payment service. Any information may be stored in the payment database DB2. The information stored in the payment database DB2 is not limited to the example of FIG. 6. For example, the payment database DB2 may store personal information registered by a user in a payment service.

[0048] For example, the payment information includes payment user information and payment time information. In this embodiment, the payment information further includes payment location information. The payment information does not have to include payment location information.

[0049] The payment user information is information about a payment user. The payment user information is information that can identify a payment user. For example, the payment user information is letters, numbers, other symbols, or a combination of these. For example, the payment user information may be a user's login account in a payment service, a temporary ID issued to the user by the payment server 20 (e.g., an ID coded into code C30), the user's email address, the user's phone number, or other information. The payment user information may be information that can identify a payment means, such as a credit card number, an electronic money ID, or a bank account number.

[0050] Payment time information is information relating to the time when a payment was made. Payment time information is information that enables the time of payment to be identified. Payment time information is information that pinpoints the time of payment, or information that indicates a period including the time of payment. In this embodiment, an example is given in which the payment time information indicates the date and time (a combination of day and time) when the payment was made. The payment time information may be information that directly or indirectly indicates the time of payment. The payment time information is not limited to date and time. For example, the payment time information may indicate only the day when the payment was made, only the day of the week when the payment was made, only the time when the payment was made, or only the time zone when the payment was made.

[0051] The payment location information is information about the payment location where the payment was made. In this embodiment, the payment is made at the check-in location, so the payment location is also the check-in location. The payment location information is information that can identify the payment location. In this embodiment, an example is given of a case where an ID that can identify the payment location corresponds to the payment location information. The payment location information may be any information related to the payment location. For example, the payment location information may be the name, address, latitude and longitude, phone number, email address, or other information of the location where the payment was made.

[0052] The payment information may include other information. For example, the payment information may include the payment amount, information on the product or service that is the subject of the payment, whether or not points are used, or other information. Furthermore, the data stored in the data storage unit 200 is not limited to the above examples. The data storage unit 200 only needs to store data necessary for the payment service. For example, the data storage unit 200 may store a database that stores information on payment methods that the user can use in the payment service (for example, payment methods that the user has registered in a payment app). The data storage unit 200 may store information on the user's usage history of the payment service.

[0053] [Payment Execution Department] The payment execution unit 201 executes various processes related to the payment service. For example, when the payment terminal 50 reads the code C30 with the photographing unit 56, it transmits a payment request to the payment server 20. The payment request is data in a predetermined format indicating a request for payment. The payment server 20 receives the payment request from the payment terminal 50. The payment request may be transmitted by a computer other than the payment terminal 50 (for example, the check-in terminal 40 or the user terminal 60).

[0054] For example, the payment request includes payment user information, payment amount, and payment location information read from code C30. The payment location information is assumed to be pre-stored in the payment terminal 50. The payment execution unit 201 identifies the payment user based on the payment user information, and executes the payment of the payment amount included in the payment request based on the payment means of the payment source that the user has pre-registered in the payment service. The payment execution unit 201 adds payment information including the payment user information included in the payment request, payment time information indicating the current date and time, and payment location information included in the payment request to the payment database DB2.

[0055] The process executed by the payment execution unit 201 may be a process adopted in a known payment service. For example, the payment execution unit 201 may execute the payment process based on information acquired by the user terminal 60 by photographing a code displayed on the payment terminal 50, information acquired by the user terminal 60 by photographing a code posted at a check-in location, information on the payment location input to the user terminal 60, information acquired by the payment terminal 50 using short-range wireless communication, or other information.

[0056] [3-3. Functions realized by the bonus server] For example, the privilege server 30 includes a data storage unit 300, a check-in information acquisition unit 301, a payment information acquisition unit 302, a privileged user information acquisition unit 303, and a privilege granting unit 304. The data storage unit 300 is realized by the memory unit 32. The check-in information acquisition unit 301, the payment information acquisition unit 302, the privileged user information acquisition unit 303, and the privilege granting unit 304 are realized by the control unit 31.

[0057] [Data storage section] The data storage unit 300 stores data necessary for the special service. For example, the data storage unit 300 stores a check-in database DB3, a payment database DB4, and a special service database DB5.

[0058] For example, check-in database DB3 of data storage unit 300 is the same as check-in database DB1 of data storage unit 100. When check-in database DB1 of data storage unit 100 is updated, check-in server 10 reflects the update in check-in database DB3 of data storage unit 300. This ensures consistency between check-in database DB3 of data storage unit 300 and check-in database DB1 of data storage unit 100.

[0059] For example, the payment database DB4 of the data storage unit 300 is the same as the payment database DB2 of the data storage unit 200. When the payment database DB2 of the data storage unit 200 is updated, the payment server 20 reflects the update in the payment database DB4 of the data storage unit 300. This ensures consistency between the payment database DB4 of the data storage unit 300 and the payment database DB2 of the data storage unit 200.

[0060] Fig. 7 is a diagram showing an example of the privilege database DB5. The privilege database DB5 is a database in which various information related to privilege users is stored. For example, the privilege database DB5 stores privilege user information, check-in user information, payment user information, and privilege information. Any information may be stored in the privilege database DB5. The information stored in the privilege database DB5 is not limited to the example of Fig. 7. For example, if there is user information common to the check-in service, the payment service, and the privilege service, the common user information may be stored in the privilege database DB5.

[0061] The privileged user information is information that can identify a user in a privileged service. For example, the privileged user information is letters, numbers, other symbols, or a combination of these. For example, the privileged user information may be the user's login account in the privileged service, a temporary ID issued to the user by the privileged server 30 (e.g., an ID coded into code C40), the user's email address, the user's phone number, or other information. The privileged user information may be a point card number that can identify a point card.

[0062] In this embodiment, the privilege database DB5 is associated with privilege user information, check-in user information, and payment user information. The privilege service, check-in service, and payment service cooperate with each other to share this information. The privilege server 30 can identify which check-in user information indicates which user and which payment user information indicates which user based on these associations. The payment user information does not need to be stored in the privilege database DB5. When the check-in server 10 updates the check-in user information, it transmits the check-in user information before the update and the check-in user information after the update to the privilege server 30. The privilege server 30 receives these and updates the check-in user information in the privilege database DB5 to the latest information. Similarly, when the payment server 20 updates the payment user information, it transmits the payment information before the update and the payment information after the update to the privilege server 30. The privilege server 30 receives these and updates the payment information in the privilege database DB5 to the latest information.

[0063] Note that the privilege user information does not have to be stored in the privilege database DB5. That is, the privilege database DB5 may only indicate the association between the check-in user information and the payment user information. Also, when the check-in user information and the payment user information are the same information (when the information that can identify the user is common to the check-in service and the payment service), only the same information may be stored in the privilege database DB5.

[0064] The reward information is information related to rewards. For example, the reward information indicates the specific content of the rewards granted to the user, the total amount of rewards, the date and time when the rewards were granted to the user, or other information. For example, in the case where points correspond to rewards, the reward information may indicate the balance of points held by the user. The reward information may indicate the point usage history and the point acquisition history. In the case where coupons correspond to rewards, the reward information may indicate the coupons acquired by the user.

[0065] The data stored in the data storage unit 300 is not limited to the above example. The data storage unit 300 may store any data necessary for the special service. For example, the data storage unit 300 may store data necessary for providing special benefits, such as a point return rate.

[0066] [Check-in information acquisition section] The check-in information acquisition unit 301 acquires check-in information including check-in user information related to a check-in user who has checked in at a specific check-in location, and check-in time information related to the check-in time at which the user checked in. In this embodiment, the check-in information also includes check-in location information, so the check-in information acquisition unit 301 acquires check-in information including check-in location information.

[0067] In this embodiment, since the check-in information is stored in the check-in database DB3 of the data storage unit 300, the check-in information acquisition unit 301 acquires the check-in information from the check-in database DB3 of the data storage unit 300. Note that the check-in information acquisition unit 301 can acquire the check-in information from any computer or information storage medium. For example, if the check-in information is not managed in the data storage unit 300, the check-in information acquisition unit 301 may acquire the check-in information from the check-in server 10. For example, the check-in information acquisition unit 301 may acquire the check-in information from the check-in terminal 40 or the user terminal 60.

[0068] [Payment Information Acquisition Department] The payment information acquisition unit 302 acquires payment information including paying user information related to the paying user who made the payment at the check-in location and payment time information related to the time when the payment was made. In this embodiment, the payment information also includes payment location information, so the payment information acquisition unit 302 acquires payment information including payment location information.

[0069] In this embodiment, since the payment information is stored in the payment database DB4 of the data storage unit 300, the payment information acquisition unit 302 acquires the payment information from the payment database DB4 of the data storage unit 300. The payment information acquisition unit 302 can acquire the payment information from any computer or information storage medium. For example, if the payment information is not managed in the data storage unit 300, the payment information acquisition unit 302 may acquire the payment information from the payment server 20. For example, the payment information acquisition unit 302 may acquire the payment information from the payment terminal 50 or the user terminal 60.

[0070] [Benefit User Information Acquisition Section] The privileged user information acquisition unit 303 acquires privileged user information on a privileged user who uses a privilege service related to a privilege, which is associated with at least one of the check-in user information and the payment user information. In this embodiment, the privileged user information is associated with both the check-in user information and the payment user information, but the privileged user information may be associated with only one of the check-in user information or the payment user information.

[0071] In this embodiment, since the privileged user information is stored in the privileged database DB5 of the data storage unit 300, the privileged user information acquisition unit 303 acquires the privileged user information from the privileged database DB5 of the data storage unit 300. For example, the privileged user information acquisition unit 303 acquires the privileged user information associated with the check-in user information. The privileged user information acquisition unit 303 acquires the payment user information associated with the payment user information.

[0072] The privileged information acquisition unit can acquire the privileged user information from any computer or information storage medium. For example, when the privileged user information is not managed in the data storage unit 300, the privileged information acquisition unit may acquire the privileged user information from a computer other than the privileged server 30. For example, the privileged information acquisition unit may acquire the privileged user information from the payment terminal 50 or the user terminal 60.

[0073] [Benefits Granting Department] The reward granting unit 304 grants a reward to a grantee user who has both checked in and made a payment at a check-in location within a predetermined period based on the check-in information and the payment information. The predetermined period is a criterion for whether or not to grant a reward. The predetermined period may be a fixed period determined in advance, or may be a dynamic period determined according to the time of check-in or the time of payment (for example, within 10 minutes from the time of check-in or the time of payment).

[0074] For example, the reward granting unit 304 judges whether the check-in time information included in the check-in information and the payment time information included in the payment information are included in a predetermined period. The reward granting unit 304 judges whether the check-in location information included in the check-in information and the payment location information included in the payment information indicate the same location. The reward granting unit 304 judges whether the check-in user information included in the check-in information and the payment user information included in the payment information indicate the same user. In this embodiment, the same user means that the check-in user information and the payment user information are associated with the reward database DB5. The match between the check-in user information and the payment user information may correspond to the same user. The reward granting unit 304 performs these three judgments based on a large number of check-in information and a large number of payment information. For example, the reward granting unit 304 performs these three judgments as a batch process.

[0075] For example, the reward granting unit 304 identifies a target user who has both checked in and made a payment at a check-in location within a predetermined period based on the above three determination results. The reward granting unit 304 grants a reward to the identified target user. The process for granting the reward may be a known process. For example, when points correspond to the reward, the reward granting unit 304 updates the reward information of the target user so that the points held by the target user are increased. The reward granting unit 304 may grant the target user a reward according to the payment amount (for example, points obtained by multiplying the payment amount by a predetermined point return rate), or may grant a reward unrelated to the payment amount.

[0076] In this embodiment, the predetermined period is days (1 day) as an example. The reward granting unit 304 grants a reward to a grantee user who has both checked in and made a payment at a check-in location on the same day. For example, the timing for executing batch processing occurs every day. The reward granting unit 304 acquires check-in information indicating a check-in made on a day to be subjected to batch processing and payment information indicating a payment made on the day from among a large number of check-in information and a large number of payment information. It is determined whether the check-in location information included in the acquired check-in information and the payment location information included in the acquired payment information indicate the same location. The reward granting unit 304 determines whether the check-in user information included in the acquired check-in information and the payment user information included in the acquired payment information indicate the same user.

[0077] For example, the reward granting unit 304 refers to the reward database DB5 in which the check-in user information and the payment user information are associated with each other, and identifies the grantee user. In this embodiment, since there is other reward user information than the check-in user information and the payment user information as information capable of identifying a user, the reward granting unit 304 grants a reward based on the reward user information of the grantee user. For example, when the check-in user information and the payment user information are associated with the same reward user information, the reward granting unit 304 determines that the check-in user information and the payment user information indicate the same user. The same user is the grantee user. When the check-in user information and the payment user information are not associated with the same reward user information, the reward granting unit 304 determines that the check-in user information and the payment user information do not indicate the same user. The reward granting unit 304 grants a reward to the grantee user by updating the reward information associated with the same reward user information.

[0078] In addition, when the privileged user information does not exist, the privilege granting unit 304 determines that the check-in user information and the payment user information indicate the same user when the check-in user information and the payment user information are stored in the same record of the privilege database DB5. When the check-in user information and the payment user information are not stored in the same record of the privilege database DB5, the privilege granting unit 304 determines that the check-in user information and the payment user information do not indicate the same user. The privilege database DB5 is an example of a database in which the check-in user information and the payment user information are associated with each other. These associations may be shown in a database other than the privilege database DB5.

[0079] Also, the check-in user information and the payment user information may be the same. In this case, the check-in user information and the payment user information do not have to be particularly associated with each other. The reward granting unit 304 determines whether the check-in user information and the payment user information match. If the check-in user information and the payment user information match, the reward granting unit 304 determines that the check-in user information and the payment user information indicate the same user. If the check-in user information and the payment user information do not match, the reward granting unit 304 determines that the check-in user information and the payment user information do not indicate the same user.

[0080] In this embodiment, since it does not matter whether check-in or payment is performed first, the reward granting unit 304 grants a reward to a grantee user who checks in at a check-in location within a predetermined period and then makes a payment, and grants a reward to a grantee user who checks in at a check-in location within a predetermined period and then makes a payment. In other words, when the reward granting unit determines that the same user has checked in and made a payment at the same check-in location within a predetermined period, it identifies the user as a grantee user regardless of whether check-in or payment was performed first. Note that a condition for granting a reward may be that check-in is performed before payment.

[0081] [3-4. Functions realized by the check-in terminal] For example, the check-in terminal 40 includes a data storage unit 400 and a check-in execution unit 401. The data storage unit 400 is realized by the storage unit 42. Each of the check-in execution units 401 is realized by the control unit 41.

[0082] [Data storage section] The data storage unit 400 stores data necessary for the check-in service. For example, the data storage unit 400 stores ultrasound data indicating an ultrasound corresponding to a check-in location. The data storage unit 400 may store check-in location information.

[0083] [Check-in Execution Department] The check-in execution unit 401 executes processing required for check-in. For example, the check-in execution unit 401 generates ultrasonic waves from the ultrasonic generation unit 46 based on the ultrasonic data. When communication with another computer such as the check-in server 10 or the user terminal 60 is required for check-in, the check-in execution unit 401 communicates with the other computer.

[0084] [3-5. Functions realized by the payment terminal] For example, the payment terminal 50 includes a data storage unit 500 and a payment execution unit 501. The data storage unit 500 is realized by the storage unit 52. The payment execution unit 501 is realized by the control unit 51.

[0085] [Data storage section] The data storage unit 500 stores data necessary for payment. For example, the data storage unit 500 may store a database in which various information related to products or services available at the check-in location is stored. The data storage unit 500 may also store payment location information.

[0086] [Payment Execution Department] The payment execution unit 501 executes processing required for payment. For example, the payment execution unit 501 transmits a payment request to the payment server 20. In this embodiment, the payment execution unit 501 transmits a payment request including the payment user information extracted from the code C30 and the payment location information stored in the data storage unit 500 to the payment server 20. The payment execution unit 501 may include other information such as a payment amount acquired by reading a barcode of a product, etc., in the payment request.

[0087] [3-6. Functions realized on user terminals] For example, the user terminal 60 includes a data storage unit 600, a check-in executor 601, and a payment executor 602. The data storage unit 600 is realized by the storage unit 62. The check-in executor 601 and the payment executor 602 are realized by the control unit 61.

[0088] [Data storage section] The data storage unit 600 stores data necessary for each of the check-in service, the payment service, and the reward service. For example, the data storage unit 600 stores each of a check-in application, a payment application, and a reward application. When a user uses each of the check-in service, the payment service, and the reward service from a browser, the data storage unit 600 may store the browser. The data storage unit 600 may store check-in user information, payment user information, and reward user information.

[0089] [Check-in Execution Department] The check-in execution unit 601 executes processing required for check-in. For example, the check-in execution unit 601 transmits a check-in request to the check-in server 10. In this embodiment, when ultrasound is detected with the check-in app running, the check-in execution unit 601 transmits a check-in request including the check-in user information stored in the data storage unit 600 and the detection result of the ultrasound to the check-in server 10. The check-in execution unit 601 may include check-in location information indicating a check-in location selected by the user or a check-in location identified from the current location in the check-in request.

[0090] [Payment Execution Department] The payment execution unit 602 executes the process required for the payment. For example, the payment execution unit 602 displays the code C30 on the code screen SC3. When a payment is executed in which the code displayed on the payment terminal 50 is read by the user terminal 60, or in which the payment is completed only by operating the user terminal 60, the payment execution unit 602 may transmit a payment request to the payment server 20.

[0091] [4. Processing performed by the reward system] Fig. 8 is a diagram showing an example of the processing executed in the reward granting system 1. Fig. 8 shows the processing of the check-in server 10, the payment server 20, and the reward server 30 among the processing executed in the reward granting system 1. The processing of Fig. 8 is executed by the control units 11, 21, and 31 executing the programs stored in the storage units 12, 22, and 32. It is assumed that check-in and payment are performed at various check-in locations when the processing of Fig. 8 is executed.

[0092] As shown in FIG. 8, the bonus server 30 executes a process for acquiring check-in information from the check-in server 10 (S1). The process of S1 may be executed periodically or each time a check-in occurs. In S1, the bonus server 30 stores the check-in information acquired from the check-in server 10 in a check-in database DB3. The bonus server 30 executes a process for acquiring payment information from the payment server 20 (S2). The process of S2 may be executed periodically or each time a payment occurs. In S2, the bonus server 30 stores the payment information acquired from the payment server 20 in a payment database DB4.

[0093] The privilege server 30 judges whether or not the timing for executing the batch process has arrived (S3). For example, the batch process is executed once a day. If the execution timing is 2:00 a.m. every day, the process of S4 described below is executed based on the check-in information of the check-in executed on the previous day and the payment information of the payment executed on the previous day. If it is not judged in S3 that the timing for executing the batch process has arrived (S3:N), this process ends.

[0094] If it is determined in S3 that the time to execute the batch process has arrived (S3:Y), the reward server 30 grants a reward to the grantee users who have both checked in and made a payment at the same check-in location on the day targeted for the batch process, based on the check-in information stored in the check-in database DB3 and the payment information stored in the payment database DB4 (S4), and this process ends. Details of the process in S4 are as described above as the process of the reward granting unit 304. In S4, the reward server 30 grants the grantee users a reward according to the payment amount.

[0095] [5. Summary of the embodiment] The reward-granting system 1 of the present embodiment grants a reward to a grantee user who has both checked in and made a payment at a check-in location within a predetermined period based on the check-in information and the payment information. This allows the reward-granting system 1 to accurately identify a user to whom a reward is to be granted without causing the user trouble. For example, the user can earn points according to the payment amount without having to perform an operation such as presenting the code C40 as a point card at the payment after checking in at the check-in location, and then returning to the code screen SC3 and presenting the code C30. Therefore, the reward-granting system 1 can reduce the operational burden on the user and the operational burden on the person in charge at the check-in location. The reward-granting system 1 can accurately identify a grantee user by using not only time-related information such as check-in time information and payment time information, but also information such as check-in user information and payment user information. The reward-granting system 1 can encourage users to check in periodically by setting a time limit of a predetermined period. The reward-granting system 1 can accurately identify a grantee user with existing facilities without requiring special modifications to a check-in location where a check-in service and a payment service have already been introduced. Also, because check-in is a condition for the user not having to present the code C40 as a point card, the check-in location is more effective at attracting customers. For example, it is possible to make the code C30 double as the code for the point card, in which case the user would not have to check in and would not have to present the point card, but by making check-in a condition, the check-in location is more effective at attracting customers.

[0096] Furthermore, the privilege granting system 1 refers to a privilege database DB5 in which the check-in user information and the payment user information are associated with each other, and identifies the grantee user. This allows the privilege granting system 1 to accurately identify the grantee user even if the check-in user information and the payment user information are different information. For example, even if the check-in user information is information for logging in to the check-in service and the payment user information is temporary information for displaying the code C30, and these are different pieces of information, the privilege granting system 1 can accurately identify the grantee user.

[0097] In addition, the reward system 1 grants a reward to a grantee user who has both checked in and made a payment at the check-in location on the same day. This increases user convenience because the user does not need to make a payment in a hurry after checking in or check in in a hurry after making a payment. For example, even if a user does not check in at the check-in location, makes a payment without presenting a point card, and leaves the check-in location, if the user later returns to the check-in location on the same day and checks in, the user can earn points corresponding to the payment. Conversely, even if a user only checks in at the check-in location without making a payment, and then returns to the check-in location on the same day and makes a payment, the user can earn points corresponding to the payment.

[0098] The reward granting system 1 also grants a reward based on the reward user information of the grantee user associated with at least one of the check-in user information and the payment user information. This allows the reward granting system 1 to accurately identify the grantee user even if the reward is managed by reward user information different from the check-in user information and the payment user information.

[0099] In addition, the reward system 1 rewards a reward to a rewardee user who checks in at a check-in location within a specified period and then makes a payment, and also rewards a reward to a rewardee user who checks in at a check-in location within a specified period and then makes a payment. This increases user convenience because the user can check in or make a payment first. For example, if a user makes a first payment on a certain day without checking in at a check-in location, and then checks in at the same check-in location on the same day and makes a second payment, the user can obtain rewards for these two payments without presenting a point card.

[0100] [6. Modifications] The present disclosure is not limited to the above-described embodiments. The present disclosure can be modified as appropriate without departing from the spirit and scope of the present disclosure.

[0101] Fig. 9 is a diagram showing an example of functions realized in the modified example. As shown in Fig. 9, in the modified example of the privilege granting system 1, a different privilege user information acquisition unit 305 and a privilege target amount calculation unit 306 are realized. Each of the different privilege user information acquisition unit 305 and the privilege target amount calculation unit 306 is realized by the control unit 31.

[0102] [6-1. Variation 1] For example, a user may be able to obtain a privilege for any of a plurality of privilege services at a check-in location. In this case, if the user has obtained a privilege for a privilege service other than the privilege service described in the embodiment, the privilege for the privilege service described in the embodiment may not be granted to the user even if the user checks in and makes a payment at the same check-in location on the same day.

[0103] The privilege granting system 1 includes an other privilege user information acquisition unit 305. The other privilege user information acquisition unit 305 acquires other privilege user information capable of identifying other privilege users to be granted other privileges different from the privilege granted by the privilege granting unit 304 at the check-in location. The other privileges are privileges in other privilege services different from the privilege services described in the embodiment. In the first modified example, the other privilege user information acquisition unit 305 acquires other privilege user information from the payment server 20 as an example. The other privilege user information acquisition unit 305 may acquire other privilege user information from a system of another privilege service that manages other privileges, the check-in server 10, or another computer.

[0104] The other privilege user information is information about the other privilege user. The other privilege user information is information that can identify the other privilege user. For example, the other privilege user information is letters, numbers, other symbols, or a combination of these. For example, the other privilege user information may be the user's login account in the other privilege service, a temporary ID issued to the user by a system that manages other privileges, the user's email address, the user's phone number, or other information.

[0105] In the first modified example, the other privilege user information is the same as the payment user information. For example, the payment server 20 manages the payment user information of the user to whom the other privilege has been granted as the other privilege user information in the payment database DB2. The other privilege user information acquisition unit 305 acquires the other privilege user information. If the other privilege user information is different from the payment user information, the privilege database DB5 associates at least one of the privilege user information, the check-in user information, and the payment user information with the other privilege user information. The privilege server 30 can identify which privilege user has been granted the other privilege by these associations.

[0106] In the first variant, a user can acquire any of "AAA points", "BBB points", and "CCC points". The number of benefits that a user can acquire at a check-in location is not limited to three, and may be two, or may be four or more. The benefit described in the embodiment is "AAA points". "BBB points" and "CCC points" are benefits other than the benefit described in the embodiment. "AAA points" are not awarded to a user who acquires "BBB points" or "CCC points" through payment at a check-in location by the processing of the first variant. In other words, the user is not identified as an eligible user.

[0107] The privilege granting unit 304 of the first modified example grants a privilege to a grantee user to whom no other privileges are granted, further based on the other privilege user information. Even if a user checks in and makes a payment at a check-in location within a specified period, the privilege granting unit 304 does not identify the user as a grantee user if the user is a other privilege user. The privilege granting unit 304 identifies the user as a grantee user if a user checks in and makes a payment at a check-in location within a specified period and is not a other privilege user. That is, the condition for identifying a user as a grantee user is that the user is not a other privilege user, in addition to the conditions described in the embodiment.

[0108] The privilege granting system 1 of the first modification grants a privilege to a grantee user to whom no other privilege is granted, based on the other privileged user information. This allows the privilege granting system 1 to prevent the privileges of multiple privileged services from being granted in duplicate.

[0109] [6-2. Variation 2] For example, some products or services available at the check-in location are not eligible for the benefit. In this case, the benefit granting system 1 may grant the benefit to the eligible user by subtracting the amount not eligible for the benefit from the total payment amount. The benefit is a product for which a benefit is granted when the user purchases it, or a service for which a benefit is granted when the user uses it. A database indicating which products or services are eligible for the benefit is stored in the benefit server 30. This database may be stored in the payment server 20, the payment terminal 50, or another computer.

[0110] The reward granting system 1 includes a reward target amount calculation unit 306. The reward target amount calculation unit 306 calculates the reward target amount that is the subject of the reward out of the payment amount of the payment. In the second modification, the payment request and the payment information include information that can identify the product or service that is the subject of the payment (i.e., the product purchased by the user or the service used by the user) and the payment amount of the product or service (i.e., the price of the product or service). For example, the information that can identify the product or service that is the subject of the payment is the product ID (e.g., JAN code), the product name, the product category, the service ID, the service name, the service category, or other information.

[0111] For example, the reward target amount calculation unit 306 identifies the product or service that is eligible for the reward based on information that can identify the product or service that is the subject of the payment and a database that indicates which products or services are eligible for the reward. The reward target amount calculation unit 306 calculates the reward target amount by adding up the payment amounts of the identified products or services. The reward target amount calculation unit 306 may calculate the reward target amount by subtracting the payment amounts of products or services that are not eligible for the reward from the total payment amount in the payment.

[0112] The reward granting unit 304 of the second modification grants a reward to the grantee user according to the reward target amount. For example, the reward granting unit 304 calculates the number of points to be granted as a reward to the grantee user by multiplying the reward target amount by a predetermined point return rate. The reward granting unit 304 may determine whether the reward target amount is equal to or greater than a threshold, and grant the reward to the grantee user if the reward target amount is equal to or greater than the threshold.

[0113] The reward granting system 1 of the second modification grants a reward to a user according to the reward target amount. This prevents the reward granting system 1 from erroneously granting a reward for a product or service that is not eligible for a reward when the payment is made for the product or service.

[0114] [6-3. Variation 3] For example, the reward granting unit 304 may grant a reward to a grantee user who has both checked in and made a payment at a check-in location within a predetermined period of time whose length corresponds to the check-in location. The data storage unit 300 of the third modification stores a database showing the relationship between check-in location information and the length of the predetermined period. The reward granting unit 304 specifies the length associated with the check-in location information included in the check-in information based on the database. The reward granting unit 304 may specify the length associated with the same check-in location information as the payment location information included in the payment information. The reward granting unit 304 grants a reward to a grantee user who has both checked in and made a payment at the same check-in location within the specified period of time whose length has been specified.

[0115] For example, assume that a first length of time (e.g., two hours from check-in) is set for a first check-in location (e.g., a high-end store or restaurant). The reward granting unit 304 grants a reward to a grantee user who has both checked in and made a payment at the first check-in location within the first length of time (e.g., within two hours from check-in) based on check-in information whose check-in location information indicates the first check-in location and payment information whose payment location information indicates the first check-in location.

[0116] For example, assume that a second length of time (e.g., 10 minutes from check-in) is set for a second check-in location (e.g., a convenience store). The reward granting unit 304 grants a reward to a grantee user who has both checked in and made a payment at the second check-in location within the second length of time (e.g., within 10 minutes from check-in) based on check-in information whose check-in location information indicates the second check-in location and payment information whose payment location information indicates the second check-in location.

[0117] The reward-granting system 1 of the third modification grants a reward to a grantee user who has both checked in and made a payment at a check-in location within a predetermined period of time, the length of which depends on the check-in location. In this way, the reward-granting system 1 can increase user convenience. For example, if the check-in location is a high-end store or restaurant where it takes a long time from check-in to payment, the user's convenience can be increased by lengthening the predetermined period. If the check-in location is a convenience store where it does not take long from check-in to payment, the frequency of user visits can be increased by shortening the predetermined period.

[0118] [6-4. Variation 4] For example, the reward granting unit 304 may grant a further reward to the grantee user based on the difference between the check-in time indicated by the check-in time information and the payment time indicated by the payment time information. The difference here is a time difference. As described in the embodiment, the check-in time may be earlier than the payment time, or the payment time may be earlier than the check-in time. For example, when the difference between the check-in time indicated by the check-in time information and the payment time indicated by the payment time information is less than a threshold, the reward granting unit 304 grants a further reward to the grantee user. The threshold may be common to a plurality of check-in locations, or may be determined for each check-in location.

[0119] For example, the reward granting unit 304 may determine a reward for the grantee user such that the shorter the difference between the check-in time indicated by the check-in time information and the payment time indicated by the payment time information, the better the reward. A better reward means a higher point redemption rate, a higher number of points, a higher coupon discount rate, a higher price for the product or service granted to the grantee user, or a larger amount of reward. Data indicating the relationship between the difference between the check-in time and the payment time, and the content of the reward is stored in the data storage unit 300. The reward granting unit 304 refers to the data and grants the grantee user a reward with content associated with the difference between the check-in time indicated by the check-in time information and the payment time indicated by the payment time information.

[0120] The reward granting system 1 of the fourth modification grants an additional reward to the grantee user based on the difference between the check-in time indicated by the check-in time information and the payment time indicated by the payment time information. This allows the reward granting system 1 to increase the game-like nature of the reward service, thereby increasing the interest of the user. For example, if the shorter the difference between the check-in time and the payment time is, the better the reward, the reward granting system 1 can motivate the user to make a payment immediately after checking in, or to check in immediately after making a payment. This allows the reward granting system 1 to promote check-in and payment at the check-in location.

[0121] [6-5. Variation 5] For example, in the embodiment, a case has been described in which if a user performs both check-in and payment at the same check-in location in a given day, he or she does not need to present the code C40 as a point card. A user may be able to check-in at a certain check-in location only once a day, or may be able to check-in multiple times a day.

[0122] At the check-in location of variant 5, check-in is possible during each of a plurality of possible check-in periods. The possible check-in periods are periods during which a user can check in. A database showing the relationship between each check-in location and the possible check-in periods for that check-in location is stored in the data storage unit 100. The check-in server 10 determines, based on the database, whether or not the current time when the check-in request is received is within a possible check-in period.

[0123] For example, if the check-in server 10 does not determine that the current time is within the check-in possible period, the check-in server 10 does not execute the check-in. If the check-in server 10 determines that the current time is within the check-in possible period, the check-in server 10 determines whether or not the check-in user included in the check-in request has already checked in during the current check-in possible period, based on the check-in database DB1. If the check-in server 10 determines that the check-in user has already checked in during the current check-in possible period, the check-in server 10 does not execute the check-in. If the check-in server 10 determines that the check-in user has not yet checked in during the current check-in possible period, the check-in server 10 executes the check-in.

[0124] In variant 5, an example is taken in which a user can check in once during a certain check-in period. A user may be able to check in more than once during a certain check-in period. A user can check in up to a predetermined number of times during a certain check-in period. In variant 5, it is assumed that there is a check-in period from midnight to 3pm and a check-in period from 3am to 12pm. For example, the predetermined period for which a benefit is awarded is longer than the check-in period. In variant 5 as well, it is assumed that the predetermined period is one day.

[0125] The benefit granting unit 304 of the fifth modified example grants a benefit to a benefit-recipient user who has both checked in and made a payment at a check-in location within a predetermined period including multiple possible check-in periods. For example, assume that a user checks in to a check-in location during the possible check-in period from 12:00 AM to 3:00 PM. Even if the user does not check in to the check-in location during the possible check-in period from 3:00 AM to 12:00 PM, the user can earn points if the user makes a payment at the check-in location without presenting the code C40 as a point card.

[0126] The reward granting system 1 of the fifth modification grants a reward to a grantee user who has both checked in and made a payment at a check-in location within a predetermined period including multiple possible check-in periods. As a result, even if a user has not checked in during the current possible check-in period, as long as the user has checked in during another possible check-in period within the predetermined period, the user can earn points without presenting the code C40 as a point card, so that the reward granting system 1 can improve user convenience.

[0127] [6-6. Variation 6] For example, the check-in location may correspond to each of a plurality of payment services linked to a privilege service related to a privilege. In the sixth modification, a payment server 20 exists for each payment service. The privilege server 30 links with each of the payment servers 20 of the plurality of payment services. The privilege granting unit 304 may grant a privilege to a grantee user regardless of which of the plurality of payment services is used for payment. The privilege database DB5 of the sixth modification stores privilege user information, check-in user information, payment user information for each of the plurality of payment services, and privilege information.

[0128] The payment information acquisition unit 302 acquires payment information indicating a payment made in the payment service from each of the payment servers 20 of the multiple payment services. The reward granting unit 304 identifies which paying user is the same as which check-in user, based on the payment user information included in the payment information acquired from each of the payment servers 20 of the multiple payment services and the reward database DB5. This embodiment differs from the embodiment in that the payment information acquired from each of the payment servers 20 of the multiple payment services is used to identify the grantee user, but the method of identifying the grantee user itself is the same as the embodiment.

[0129] The reward granting system 1 of the sixth modification grants a reward to a grantee user regardless of which of a plurality of payment services is used for payment. This allows the user to earn points without presenting the code C40 as a point card regardless of which of a plurality of payment services is used, so that the reward granting system 1 can improve user convenience.

[0130] [6-7. Variation 7] For example, the method of eliminating the need for the user to present the code C40 as a point card is not limited to the example of the embodiment. In the seventh modification, when the user checks in to the check-in location, the user terminal 60 receives the privileged user information from the privileged server 30 via the check-in server 10. The user terminal 60 transmits the privileged user information to the payment terminal 50 using wireless communication such as a beacon. The payment terminal 50 may receive the privileged user information using wireless communication so that the user does not need to present the code C40 as a point card.

[0131] FIG. 10 is a diagram showing an example of functions realized by the privilege granting system 1 of Modification 7. The privilege server 30 of Modification 7 includes a data storage unit 300, a privileged user information acquisition unit 303, a privilege granting unit 304, and a privileged user information transmission unit 307. The privileged user information transmission unit 307 is realized by the control unit 31. Note that the privilege granting system 1 of Modification 7 may not include some of the functions described in the embodiment. For example, the privilege granting system 1 may not include the check-in information acquisition unit 301 and the payment information acquisition unit 302. Some of the functions of the privilege granting unit 304 described in the embodiment may not be realized.

[0132] When a user checks in to a specified check-in location, the privileged user information transmitting unit 307 transmits privileged user information to the user's user terminal 60 for granting the user a privilege through payment at the check-in location. In the seventh modification, when the check-in server 10 detects a check-in by a user, it transmits check-in information to the privilege server 30. The privilege server 30 receives the check-in information from the check-in server 10.

[0133] For example, the privilege server 30 may generate new privilege user information when it receives check-in information from the check-in server 10. In this case, the privilege server 30 stores the new privilege user in the privilege database DB5 in association with the check-in user information included in the check-in information. That is, the privilege server 30 may update the privilege user information when it receives check-in information from the check-in server 10. Note that the privilege user information does not have to be updated every time a check-in occurs. For example, the privilege user information may be updated when multiple check-ins are performed, when a user performs an operation for updating, when a specific update timing arrives, or in other cases. The privilege user information may be a fixed value without being updated.

[0134] For example, the privileged user information transmitting unit 307 refers to the privileged database DB5 and acquires privileged user information associated with the check-in user information included in the check-in information. The privileged user information transmitting unit 307 transmits the acquired privileged user information to the user terminal 60. The privileged user information transmitting unit 307 may transmit the privileged user information directly to the user terminal 60, or may transmit the privileged user information indirectly via another computer such as the check-in server 10.

[0135] The user terminal 60 records the privileged user information transmitted by the privileged user information transmitting unit 307 in the data storage unit 600. The user terminal 60 transmits the privileged user information to the payment terminal 50. When wireless communication capable of estimating the distance between the payment terminal 50 and the user terminal 60 is used, such as a beacon, the user terminal 60 may transmit the privileged user information to the payment terminal 50 when it approaches the vicinity of the payment terminal 50 (for example, within 1 m). The payment terminal 50 records the privileged user information received from the user terminal 60 in the data storage unit 500.

[0136] In addition, when wireless communication capable of estimating the distance between the payment terminal 50 and the user terminal 60, such as a beacon, is used, the payment terminal 50 may record only the privileged user information received from a user terminal 60 in its vicinity (for example, within 1 m) in the data storage unit 500. For example, the payment terminal 50 may record in the data storage unit 500 the privileged user information received from a user terminal 60 that is not in its vicinity, but may validate only the privileged user information received from a user terminal 60 in its vicinity or from the closest user terminal 60.

[0137] For example, when a payment is made, the payment terminal 50 transmits a payment request including privileged user information to the payment server 20. The payment server 20 performs the payment in the same manner as in the embodiment. The payment server 20 transmits the privileged user information included in the payment request to the privileged server 30. Even if multiple users check in to a check-in location, the payment terminal 50 includes only the privileged user information received from a user terminal 60 in the vicinity of the payment terminal 50 or from the nearest user terminal 60 in the payment request, so that the user who made the payment can be accurately identified. Note that the payment terminal 50 may transmit the privileged user information to the payment server 20 or the privileged server 30 before an instruction to make a payment is given. In this case, points may be used at the time of payment based on the transmitted privileged user information.

[0138] The privileged user information acquisition unit 303 of the seventh modification acquires the privileged user information transmitted by wireless communication from the user terminal 60 to the payment terminal 50 at the check-in location. In the seventh modification, the privileged user information acquisition unit 303 acquires the privileged user information from the payment server 20. The privileged user information acquisition unit 303 may acquire the privileged user information from a computer other than the payment server 20. In the seventh modification, since the privileged user information is included in the payment request, the privileged user information acquisition unit 303 acquires the privileged user information included in the payment request. In the seventh modification, it is assumed that the payment information also includes the privileged user information.

[0139] The privilege granting unit 304 of the seventh modification grants a privilege to a user based on privileged user information transmitted by wireless communication when a payment is made by the payment terminal 50. Although the method of identifying a user to whom a privilege is to be granted is different from that of the embodiment, the privilege is granted in the same manner as in the embodiment. The privilege granting unit 304 grants a privilege to a user by updating the privilege information associated with the privileged user information.

[0140] The privilege-granting system 1 of the seventh modification transmits privileged user information to the user terminal 60 when the user checks in at the check-in location. The privilege-granting system 1 acquires the privileged user information transmitted from the user terminal 60 to the payment terminal 50 by wireless communication. When payment is made by the payment terminal 50, the privilege-granting system 1 grants a privilege to the user based on the privileged user information transmitted by wireless communication. This allows the privilege-granting system 1 to accurately identify the user to whom the privilege should be granted without causing the user to take the trouble of doing so. For example, if the user checks in at the check-in location, the user can earn points according to the payment amount without presenting the code C40 as a point card. This allows the privilege-granting system 1 to reduce the operational burden on the user and the operational burden on the person in charge at the check-in location.

[0141] [6-8. Other Modifications] For example, the above modifications may be combined.

[0142] For example, in the embodiment, the case where the reward server 30 identifies the grantee user has been exemplified, but a computer other than the reward server 30 may identify the grantee user. For example, the check-in terminal 40 or the payment terminal 50 may identify the grantee user. In this case, the check-in terminal 40 or the payment terminal 50 can identify the grantee user by focusing only on the check-in and payment at the check-in location where the check-in terminal 40 or the payment terminal 50 is located, and therefore can identify the grantee user without using check-in location information and payment location information. The check-in terminal 40 or the payment terminal 50 may request the granting of a reward by transmitting information that can identify the grantee user (for example, check-in user information or payment user information) to the reward server 30.

[0143] For example, in the embodiment, the case where the identification of the grantee user is executed as a batch process has been described, but the grantee user may be identified each time a check-in or payment is made. In this case, the reward server 30 may acquire check-in information, acquire payment information, and identify the grantee user each time a check-in or payment is made. If the user checks in and then makes a payment, the reward may be granted at the same time as the payment is completed. In this case, even if the user does not present the code C40 as a point card, a reward according to the payment amount may be displayed on the payment completion screen. Conversely, if the user checks in after making a payment, the reward may be granted at the same time as the check-in is completed. In this case, even if the user does not present the code C40 as a point card, a reward according to the payment amount may be displayed on the check-in completion screen.

[0144] For example, the process described as being executed by the reward server 30 may be executed by the check-in server 10 or the payment server 20. The process described as being executed by the check-in server 10 may be executed by the payment server 20 or the reward server 30. The process described as being executed by the payment server 20 may be executed by the check-in server 10 or the reward server 30. The process described as being executed by the check-in server 10, the payment server 20, or the reward server 30 may be shared among multiple computers.

[0145] [7. Notes] For example, the reward system can be configured as follows. (1) a check-in information acquisition unit that acquires check-in information including check-in user information related to a check-in user who has checked in at a predetermined check-in location and check-in time information related to a check-in time at which the check-in was performed; A payment information acquisition unit that acquires payment information including payment user information related to a payment user who made a payment at the check-in location and payment time information related to a time when the payment was made; a reward granting unit that grants a reward to a grantee user who has both checked in and made the payment at the check-in location within a predetermined period based on the check-in information and the payment information; A reward system including: (2) The privilege granting system further includes an other privilege user information acquisition unit that acquires other privilege user information capable of identifying other privilege users to be granted other privileges different from the privilege at the check-in location, The privilege granting unit grants the privilege to the grantee user to whom the other privilege is not granted, based on the other privilege user information. The reward system according to (1). (3) The reward granting system further includes a reward target amount calculation unit that calculates a reward target amount that is subject to the reward out of a payment amount of the payment, The reward granting unit grants the reward to the grantee user according to the reward target amount. A reward system according to (1) or (2). (4) The benefit granting unit refers to a database in which the check-in user information and the payment user information are associated with each other, and identifies the benefit recipient user. A reward system according to any one of (1) to (3). (5) the predetermined period is days, The reward granting unit grants the reward to the grantee user who has performed both the check-in and the payment at the check-in location on the same day. A reward system according to any one of (1) to (4). (6) The reward granting unit grants the reward to the grantee user who has both checked in and made the payment at the check-in location within the predetermined period whose length corresponds to the check-in location. A reward system according to any one of (1) to (5). (7) The reward granting unit grants a further reward to the grantee user based on a difference between the check-in time indicated by the check-in time information and the payment time indicated by the payment time information. A reward system according to any one of (1) to (6). (8) The privilege granting system further includes a privilege user information acquisition unit that acquires privilege user information related to a privilege user who uses a privilege service related to the privilege, the privilege user information being associated with at least one of the check-in user information and the payment user information; The privilege granting unit grants the privilege based on the privilege user information of the grantee user. A reward system according to any one of (1) to (7). (9) the benefit granting unit grants the benefit to the grantee user who has checked in at the check-in location within the predetermined period and then made the payment, and grants the benefit to the grantee user who has checked in at the check-in location within the predetermined period and then made the payment, A reward system according to any one of (1) to (8). (10) At the check-in location, the check-in is possible during each of a plurality of check-in possible periods; The reward granting unit grants the reward to the grantee user who has performed both the check-in and the payment at the check-in location within the predetermined period including the plurality of check-in possible periods. A reward system according to any one of (1) to (9). (11) the check-in location corresponds to each of a plurality of payment services associated with a privilege service related to the privilege; The reward granting unit grants the reward to the grantee user regardless of which of the plurality of payment services is used for the payment. A reward system according to any one of (1) to (10). [Explanation of symbols]

[0146] 1 Benefit granting system, 10 Check-in server, 11, 21, 31, 41, 51, 61 Control unit, 12, 22, 32, 42, 52, 62 Memory unit, 13, 23, 33, 43, 53, 63 Communication unit, 20 Payment server, 30 Benefit server, 40 Check-in terminal, 44, 54, 64 Operation unit, 45, 55, 65 Display unit, 46 Ultrasound generation unit, 50 Payment terminal, 56, 66 Photography unit, 60 User terminal, 67 Ultrasound detection unit, 100 Data storage unit, 101, 401, 601 Check-in execution unit, 200 Data storage unit, 201, 501, 602 Payment execution unit, 300 Data storage unit, 301 Check-in information acquisition unit, 302 Payment information acquisition unit, 303 Benefit user information acquisition unit, 304 Benefit granting unit, 305 Other privilege user information acquisition unit, 306 privilege amount calculation unit, 307 privilege user information transmission unit, 400 data storage unit, 500 data storage unit, 501 payment execution unit, 600 data storage unit, B31, B41 buttons, C30, C40 codes, DB1, DB3 check-in database, DB2, DB4 payment database, DB5 privilege database, SC1 list screen, SC2 check-in completion screen, SC3, SC4 code screen.

Claims

1. a check-in information acquisition unit that acquires check-in information including check-in user information related to a check-in user who has checked in at a predetermined check-in location and check-in time information related to the check-in time at which the check-in was performed; A payment information acquisition unit that acquires payment information including payment user information related to a payment user who made a payment at the check-in location and payment time information related to a time when the payment was made; a reward granting unit that grants a reward to a reward target user who has both checked in and made the payment at the check-in location within a predetermined period based on the check-in information and the payment information; A reward system including:

2. The privilege granting system further includes an other privilege user information acquisition unit that acquires other privilege user information capable of identifying other privilege users to be granted other privileges different from the privilege at the check-in location, The privilege granting unit grants the privilege to the grantee user to whom the other privilege is not granted, based on the other privilege user information. The reward system according to claim 1 .

3. The reward granting system further includes a reward target amount calculation unit that calculates a reward target amount that is subject to the reward out of a payment amount of the payment, The reward granting unit grants the reward to the grantee user according to the reward target amount. The reward system according to claim 1 or 2.

4. The benefit granting unit refers to a database in which the check-in user information and the payment user information are associated with each other, and identifies the benefit recipient user. The reward system according to claim 1 or 2.

5. the predetermined period is days, The reward granting unit grants the reward to the grantee user who has performed both the check-in and the payment at the check-in location on the same day. The reward system according to claim 1 or 2.

6. The reward granting unit grants the reward to the grantee user who has both checked in and made the payment at the check-in location within the predetermined period whose length corresponds to the check-in location. The reward system according to claim 1 or 2.

7. The reward granting unit grants a further reward to the grantee user based on a difference between the check-in time indicated by the check-in time information and the payment time indicated by the payment time information. The reward system according to claim 1 or 2.

8. The privilege granting system further includes a privilege user information acquisition unit that acquires privilege user information related to a privilege user who uses a privilege service related to the privilege, the privilege user information being associated with at least one of the check-in user information and the payment user information; The privilege granting unit grants the privilege based on the privilege user information of the grantee user. The reward system according to claim 1 or 2.

9. the benefit granting unit grants the benefit to the grantee user who has checked in at the check-in location within the predetermined period and then made the payment, and grants the benefit to the grantee user who has checked in at the check-in location within the predetermined period and then made the payment, The reward system according to claim 1 or 2.

10. At the check-in location, the check-in is possible during each of a plurality of check-in possible periods; The reward granting unit grants the reward to the grantee user who has performed both the check-in and the payment at the check-in location within the predetermined period including the plurality of check-in possible periods. The reward system according to claim 1 or 2.

11. the check-in location corresponds to each of a plurality of payment services associated with a privilege service related to the privilege; The reward granting unit grants the reward to the grantee user regardless of which of the plurality of payment services is used for the payment. The reward system according to claim 1 or 2.

12. a privileged user information transmitting unit that transmits, when a user checks in at a predetermined check-in location, privileged user information to a user terminal of the user for granting the user a privilege through a payment at the check-in location; a privileged user information acquiring unit that acquires the privileged user information transmitted from the user terminal to a payment terminal at the check-in location via wireless communication; a privilege granting unit that grants a privilege to the user based on the privileged user information transmitted via the wireless communication when the payment is made by the payment terminal; A reward system including:

13. a check-in information acquisition step of acquiring check-in information including check-in user information related to a check-in user who has checked in at a predetermined check-in location and check-in time information related to the check-in time at which the check-in was performed; A payment information acquisition step of acquiring payment information including payment user information related to a payment user who made a payment at the check-in location and payment time information related to a payment time when the payment was made; a reward granting step of granting a reward to a grantee user who has both checked in and made the payment at the check-in location within a predetermined period based on the check-in information and the payment information; A method of awarding benefits, including:

14. a check-in information acquisition unit that acquires check-in information including check-in user information related to a check-in user who has checked in at a predetermined check-in location and check-in time information related to the check-in time at which the check-in was performed; a payment information acquisition unit that acquires payment information including payment user information related to a payment user who made a payment at the check-in location and payment time information related to a time when the payment was made; a privilege granting unit that grants a privilege to a grantee user who has both checked in and made the payment at the check-in location within a predetermined period based on the check-in information and the payment information; A program that makes a computer function as a

Images