Check-in system, reward distribution method, and program
The check-in system addresses the challenge of insufficient customer attraction by allowing users to check-in and receive rewards at both affiliated and non-affiliated facilities, enhancing engagement and promotion effectiveness.
Patent Information
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- RAKUTEN GROUP INC
- Filing Date
- 2024-11-19
- Publication Date
- 2026-07-02
AI Technical Summary
Existing technologies for enhancing customer attraction to facilities are insufficient, as many users show no interest in advertising information, and even interested users may not visit the facilities shown in the advertising.
A check-in system that allows users to check-in to affiliated and non-affiliated facilities, granting rewards for checking into non-member facilities, thereby promoting user engagement.
Enhances customer attraction and promotes appropriate promotions to users by enabling check-ins and rewards for both member and non-member facilities, improving engagement and interest.
Smart Images

Figure 0007884052000001 
Figure 0007884052000002 
Figure 0007884052000003
Abstract
Description
Technical Field
[0001] The present disclosure relates to a check-in system, a method for granting privileges, and a program.
Background Art
[0002] Conventionally, techniques for enhancing the effect of attracting customers to facilities have been studied. For example, Patent Document 1 describes an advertising device that creates highly effective advertising information in which the current situation of a user and the user's preference tendency are considered by creating advertising information such as coupons based on the purchase history of the user's purchase of goods or services. Patent Document 1 also describes that the advertising device verifies the effect of the advertising information based on the usage status of the advertising information.
Prior Art Documents
Patent Documents
[0003]
Patent Document 1
Summary of the Invention
Problems to be Solved by the Invention
[0004] However, in the technology of Patent Document 1, there are many users who show no interest in the advertising information, and the effect of attracting customers to facilities such as stores handling the goods or services shown in the advertising information is not sufficient. Even if a user is interested in the advertising information, the user may not visit a facility such as a store handling the goods or services shown in the advertising information. Therefore, the technology of Patent Document 1 is not sufficient as a promotion for enhancing the customer attraction effect for facilities.
[0005] One of the objects of the present disclosure is to perform appropriate promotion for users.
Means for Solving the Problems
[0006] The check-in system relating to this disclosure includes a check-in unit that allows a user to check in to any of the following: a check-in service member facility that is affiliated with a check-in service different from the payment service, and a check-in service non-member facility that is affiliated with the payment service but is not affiliated with the check-in service; and a reward granting unit that grants a reward to the user when the user checks in to the check-in service non-member facility. [Effects of the Invention]
[0007] This disclosure allows for appropriate promotion to users. [Brief explanation of the drawing]
[0008] [Figure 1] This figure shows an example of the hardware configuration of the check-in system according to the first embodiment. [Figure 2] This figure shows an example of a screen displayed on the user terminal of the first embodiment. [Figure 3] This figure shows an example of the functions implemented in the check-in system of the first embodiment. [Figure 4] This figure shows an example of a user database in the first embodiment. [Figure 5] This figure shows an example of a facility database according to the first embodiment. [Figure 6] This figure shows an example of the processing performed by the check-in system of the first embodiment. [Figure 7] This figure shows an example of a function realized by a modified version of the first embodiment. [Figure 8] This figure shows an example of the screen displayed on the user terminal in variation 5. [Figure 9] This figure shows an example of the screen displayed on the user terminal in Modification Example 6. [Figure 10] This figure shows an example of the screen displayed on the user terminal in Modification Example 7. [Figure 11] This figure shows an example of the screen displayed on the user terminal in Modification Example 8. [Figure 12] This figure shows an example of the screen displayed on the user terminal in Modification Example 9. [Figure 13] This figure shows an example of the functions implemented in the check-in system of the second embodiment. [Figure 14] This figure shows an example of a screen displayed on the user terminal of the second embodiment. [Modes for carrying out the invention]
[0009] [1. First Embodiment] A first embodiment, which is an example of an embodiment of the check-in system, reward granting method, and program related to this disclosure, will be described.
[0010] [1-1. Hardware configuration of the check-in system] Figure 1 shows an example of the hardware configuration of the check-in system according to the first embodiment. For example, the check-in system 1 includes a server 10, a user terminal 20, and a facility terminal 30. Each of the server 10, user terminal 20, and facility terminal 30 is connected to a network N such as the Internet or a LAN. Note that there may be multiple units of at least one of the server 10, user terminal 20, and facility terminal 30.
[0011] Server 10 is a server computer. For example, 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 volatile memory such as RAM and non-volatile memory such as flash memory. The communication unit 13 includes at least one of a communication interface for wired communication and a communication interface for wireless communication.
[0012] The user terminal 20 is the user's computer. For example, the user terminal 20 is a smartphone, a tablet, a personal computer, or a wearable terminal. The user terminal 20 includes a control unit 21, a storage unit 22, a communication unit 23, an operation unit 24, a display unit 25, and a GPS (Global Positioning System) receiver unit 26. The hardware configurations of the control unit 21, the storage unit 22, and the communication unit 23 may be the same as those of the control unit 11, the storage unit 12, and the communication unit 13, respectively. The operation unit 24 is an input device such as a touch panel or a mouse. The display unit 25 is a display such as a liquid crystal or an organic EL. The GPS receiver unit 26 is a receiver that receives signals from satellites. The user terminal 20 may have functions of other GNSS (Global Navigation Satellite System) other than GPS.
[0013] The facility terminal 30 is the computer of the facility visited by the user. In the first embodiment, since the case where there are a plurality of facilities is taken as an example, at least one facility terminal 30 may exist for each facility. The facility may be any place (a place existing on the ground or underground) visited by the user for some purpose. For example, the facility may be a commercial facility such as a store or a shopping mall, an accommodation facility such as a hotel, an event venue, a public facility such as a park or a station, a tourist facility, or other facilities. The facility may be indoors or outdoors. The facility may be a mobile facility (for example, a mobile store).
[0014] For example, the facility terminal 30 is a POS (Point Of Sale) terminal, a self-checkout terminal, a handy terminal, a smartphone, a tablet, or a personal computer. The facility terminal 30 includes a control unit 31, a storage unit 32, a communication unit 33, an operation unit 34, a display unit 35, and a reading unit 36. The hardware configurations of the control unit 31, the storage unit 32, the communication unit 33, the operation unit 34, and the display unit 35 may be the same as those of the control unit 11, the storage unit 12, the communication unit 13, the operation unit 24, and the display unit 25, respectively. The reading unit 36 is a code reader that reads codes such as barcodes or two-dimensional codes, a reader / writer terminal that reads and writes IC chips by short-range wireless communication, or a reader terminal that reads media such as cards.
[0015] Note that the programs stored in the storage units 12, 22, and 32 may be supplied to the server 10, the user terminal 20, or the facility terminal 30 via the network N. Further, at least one of a reading unit (for example, a memory card slot) that reads a computer-readable information storage medium and an input / output unit (for example, a USB port) for inputting / outputting data to / from an external device may be included in the server 10, the user terminal 20, or the facility terminal 30. For example, a program stored in an information storage medium may be supplied to the server 10, the user terminal 20, or the facility terminal 30 via at least one of the reading unit and the input / output unit.
[0016] Also, the check-in system 1 may include at least one computer. The computer included in the check-in system 1 is not limited to the example of FIG. 1. For example, the check-in system 1 may include only the server 10. In this case, the user terminal 20 and the facility terminal 30 exist outside the check-in system 1. The check-in system 1 may include the server 10 and another computer not shown in FIG. 1 (for example, a server computer for a point service described later). For example, the check-in system 1 may include a dedicated device for check-in separately from the facility terminal 30.
[0017] [1-2. Outline of the First Embodiment] In the first embodiment, an example is given where a user operates a user terminal 20 to use a payment service and a check-in service. The payment service is a service that provides the user with electronic payment (cashless payment). The payment methods available to the user in the payment service may be any means. For example, the payment methods available to the user in the payment service may be a credit card, other cards other than credit cards, electronic money, points, balances not called electronic money or points, a bank account, other accounts other than a bank account, crypto assets, a wallet, or other payment methods. In the first embodiment, an example is given where the payment service can be linked with the check-in service, but the payment service does not necessarily have to be linked with the check-in service.
[0018] The check-in service is a service that accepts check-ins to a facility. Check-in is the process of allowing the check-in system 1 to detect that a user has visited the facility. Users who check in to the facility may or may not be granted any benefits. Details of the benefits will be described later. The check-in service is a different service from the payment service. For example, a user registers to use the check-in service separately from registering to use the payment service. In the first embodiment, we give an example where the business operator that operates the payment service and the business operator that operates the check-in service are different, but these businesses may be the same. Hereafter, when payment service and check-in service are not distinguished, they will simply be referred to as services.
[0019] In the first embodiment, each of the multiple facilities subscribes to at least one of the payment service and the check-in service. A facility's subscription to at least one of the payment service and the check-in service means that a party involved with the facility (e.g., the store's operating company) subscribes to at least one of the payment service and the check-in service. The facility can also be called a member store. Subscription to the service can also be considered an acceptance of the use of the service or a contract for the service. Among the multiple facilities, there are three types: facilities that subscribe only to the payment service, facilities that subscribe only to the check-in service, and facilities that subscribe to both the payment service and the check-in service.
[0020] For example, a user can use the payment service and check-in service that the facility they visit is affiliated with. Among multiple facilities, there are three types: facilities where the user can use only the payment service, facilities where the user can use only the check-in service, and facilities where the user can use both the payment service and the check-in service.
[0021] Hereafter, facilities that participate in the check-in service will be referred to as check-in service member facilities. In the first embodiment, we will take as an example a case in which, among multiple check-in service member facilities, there are check-in service member facilities that participate not only in the check-in service but also in the payment service, and check-in service member facilities that participate in the check-in service but not in the payment service. In addition, among multiple check-in service member facilities, there may be only check-in service member facilities that participate in both the check-in service and the payment service, or there may be only check-in service member facilities that participate in the check-in service but not in the payment service.
[0022] Hereafter, facilities that do not participate in the check-in service will be referred to as non-participating facilities. In the first embodiment, non-participating facilities will not participate in the check-in service but will participate in the payment service. When there is no distinction between participating and non-participating facilities, they will simply be referred to as facilities. That is, when explaining a concept that encompasses both participating and non-participating facilities, they will simply be referred to as facilities.
[0023] In the first embodiment, we take as an example the case in which a user uses a payment service from a payment app on the user terminal 20 and also uses a check-in service from a check-in app on the user terminal 20. The payment app is an application for the payment service. The check-in app is an application for the check-in service. The check-in app is a different application from the payment app. The user has already installed both the payment app and the check-in app on the user terminal 20, and has also registered to use both the payment service and the check-in service.
[0024] Furthermore, users may use the payment service from the browser on their user terminal 20 instead of the payment app. Users may also use the check-in service from the browser on their user terminal 20 instead of the check-in app. Users may use at least one of the payment service and the check-in service using the hardware of their user terminal 20, such as the IC chip or communication function, instead of using software such as a browser. Users may also use at least one of the payment service and the check-in service using other means such as biometric authentication without using the user terminal 20.
[0025] Figure 2 shows an example of a screen displayed on the user terminal 20 of the first embodiment. For example, when a user starts up the user terminal 20, the user terminal 20 displays a menu screen SC1, which shows the menus of the user terminal 20's operating system, on the display unit 25, as shown in the upper left of Figure 2. The menu screen SC1 displays the icon I10 of a payment application and the icon I11 of a check-in application.
[0026] For example, when a user selects icon I10, the user terminal 20 launches the payment application. Once the payment application is launched, the user terminal 20 displays the code screen SC2, which is the payment application screen, on the display unit 25, as shown in the upper right of Figure 2. In the example in the upper right of Figure 2, the code screen SC2 displays a code C20 generated based on a code ID that can identify the user in the payment service. Code C20 is at least one of a barcode and a two-dimensional code. The user can execute a payment using the payment function of the payment service by having the facility terminal 30 read code C20. The payment flow may be the same as that of a known payment service.
[0027] Furthermore, payment may be carried out by methods other than those using code C20. For example, payment may be a type in which the user terminal 20 reads a code displayed on the facility terminal 30, a type in which the user terminal 20 reads a code posted at the facility, a type that is completed solely by operations on the user terminal 20, a type that uses the IC chip of the user terminal 20, online payment (for example, account payment using the user's account, or ID payment using the user's ID), carrier payment which is the payment method of the carrier used by the user terminal 20, or other types.
[0028] In the first embodiment, the payment service has a check-in function that accepts user check-ins to a facility. The check-in function of the payment service can also be considered a different check-in service from the check-in service. The check-in function is one of several functions that the payment service has. The program for implementing the check-in function of the payment service and the program for implementing the check-in service are different. For example, the check-in function of the payment service may be developed by reusing the program of the check-in service (for example, it may be developed using the SDK (Software Development Kit) of the check-in service), or it may be a unique function that does not specifically reuse the program of the check-in service.
[0029] In the example in the upper right of Figure 2, the code screen SC2 displays an icon I21 indicating the check-in function of the payment service. In the first embodiment, we take the case where the payment application is a so-called super application and the check-in function of the payment service is implemented as a so-called mini application. However, the check-in function of the payment service may be implemented in a regular application that is not a mini application (for example, another application different from the payment application and the check-in application), or it may be implemented in a browser. The check-in function of the payment service may be implemented not in software such as a browser, but in hardware such as the IC chip or communication function of the user terminal 20. The check-in function of the payment service may be implemented by other means such as biometric authentication without using the user terminal 20 in particular.
[0030] For example, a user can use the check-in function of the payment service by selecting icon I21. An example of the screen displayed after icon I21 is selected will be explained in the modified example below. In the first embodiment, the screen displayed after icon I21 is selected may be any screen. A user can use the check-in function of the payment service to check in to either a facility that is a member of the check-in service or a facility that is not a member of the check-in service. That is, the check-in function of the payment service has a function for the user to check in to a facility that is a member of the check-in service and a function for the user to check in to a facility that is not a member of the check-in service.
[0031] In the first embodiment, we take the example of a case where the check-in function of the payment service also supports check-ins to check-in service member facilities that are members of the check-in service but not of the payment service. For example, the check-in service member facility agrees in the terms of use of the check-in service to allow check-ins from the check-in function of the payment service. Therefore, even if the check-in service member facility is not a member of the payment service, the user can check in to the check-in service member facility using the check-in function of the payment service.
[0032] Furthermore, the check-in function of a payment service does not need to support check-ins at check-in service member facilities that are members of the check-in service but not the payment service. In other words, the check-in function of a payment service may only support check-ins at check-in service member facilities that are members of both the payment service and the check-in service, and at check-in service non-member facilities. These facilities can also be called payment service member facilities that are members of the payment service.
[0033] Furthermore, the check-in method in the payment service's check-in function may be the same as a publicly known method. For example, the check-in method may be a method that uses location information obtained by GNSS such as GPS, a method that uses ultrasound emitted by the facility, a method that uses beacons emitted by the facility, a method in which the user terminal 20 reads a check-in code at the facility, a method in which the facility terminal 30 reads a check-in code displayed on the user terminal 20, or other methods. The payment service's check-in function may support multiple check-in methods.
[0034] For example, when a user selects icon I11, the user terminal 20 launches the check-in app. When the check-in app is launched, the user terminal 20 displays the check-in app screen SC3, which is the screen of the check-in app, on the display unit 25, as shown in the lower right of Figure 2. The check-in app screen SC3 displays a list of check-in service member facilities near the user's current location. The user selects a check-in service member facility from the check-in app screen SC3 and checks in. In the first embodiment, an example is given where the user cannot check in to a non-check-in service member facility from the check-in service, but the user may be allowed to check in to a non-check-in service member facility from the check-in service.
[0035] The check-in method in the check-in service may be the same as the check-in method in the payment service's check-in function, or it may be different from the check-in method in the payment service's check-in function. Similar to the check-in method in the payment service's check-in function, the check-in method in the check-in service may be the same as a publicly known method. In the first embodiment, an example is given where a user cannot check in to the same check-in service participating facility using both the check-in service and the payment service's check-in function, but duplicate check-ins may be permitted.
[0036] As described above, the check-in system 1 of the first embodiment allows users to check in to either a facility participating in the check-in service or a facility not participating in the check-in service, based on the check-in function of the payment service. As a result, users can use the check-in function of the payment service to check in not only to facilities participating in the check-in service but also to facilities not participating in the check-in service. Therefore, the check-in system 1 can enhance the customer attraction effect of various facilities and conduct appropriate promotions to users. The details of the check-in system 1 will be described below.
[0037] [1-3. Functions realized by the check-in system of the first embodiment] Figure 3 shows an example of the functions implemented in the check-in system 1 of the first embodiment. The components implemented in the check-in system 1 of the first embodiment can be configured by combining them into a single device or by further distributing them among multiple devices. In the first embodiment, an example is given where the check-in service is provided by an external system, which is an external system to the check-in system 1. For this reason, the check-in system 1 does not include functions for the check-in service, but it is capable of cooperating with the external system. The check-in service may also be implemented within the check-in system 1.
[0038] Figure 3 shows the functions implemented by the server 10 among the functions implemented by the check-in system 1. In the first embodiment, the functions of the server 10 will mainly be described as those related to the payment function and check-in function of the payment service. For example, the server 10 includes a data storage unit 100, a payment execution unit 101, a check-in unit 102, and a reward granting unit 103. The data storage unit 100 is implemented by the storage unit 12. The payment execution unit 101, the check-in unit 102, and the reward granting unit 103 are implemented by the control unit 11.
[0039] [1-3-1. Data Storage Unit] The data storage unit 100 stores various types of data related to the payment service. For example, the data storage unit 100 stores the user database DB1 and the facility database DB2.
[0040] Figure 4 shows an example of the user database DB1 in the first embodiment. The user database DB1 is a database that stores various information about each of multiple users who use the payment service. For example, the user database DB1 stores user ID, login account, password, code ID, payment method information, payment source information, and check-in information. The information stored in the user database DB1 is not limited to the example in Figure 4. Other information may be stored in the user database DB1. For example, the user database DB1 may store basic information such as the user's email address and payment history information regarding the usage history of the payment function.
[0041] A user ID is an example of user identification information that can identify a user. A login account is also an example of user identification information. A login account is user identification information that a user enters to log in to a payment service. Users may be allowed to change their login account at will. A user ID is user identification information that is managed separately from the login account. In the first embodiment, we take the example of a case where there is a login account separate from the user ID (where there are at least two pieces of user identification information), but there may be only one piece of user identification information. That is, the user ID and the login account do not have to be separate. A password is authentication information that is verified during login.
[0042] In the first embodiment, we take the example that the user ID and login account for the payment service and the user ID and login account for the check-in service are the same, but they may be different. If they are different, their correspondence is defined in the user database DB1 or another database. The other database may be stored in the check-in system 1 or in an external system. By defining these correspondences, at least one of the check-in system 1 and the external system can identify which user corresponds to which user ID and login account. The same may apply to other user identification information besides user IDs and login accounts.
[0043] A code ID is also an ID that can identify a user, and is therefore an example of user identification information. In the first embodiment, we take the case where the server 10 issues a code ID as an example. For example, when the server 10 issues a code ID for a certain user, it issues a new code ID so as not to overlap with other code IDs. The server 10 stores the new code ID in the user database DB1, associating it with the user's user ID and login account. An expiration date may be set for the code ID.
[0044] Payment method information is information that identifies the payment methods available to the user through the payment service. For example, payment method information may include credit card numbers, electronic money numbers and balances, bank account and balance information, or point card numbers. Payment source information is information that identifies the payment method selected by the user as the payment source from among multiple payment methods available to the user.
[0045] Check-in information refers to information about facilities that a user has checked into using the check-in function of a payment service. It can also be described as information about a user's usage of the payment service's check-in function. For example, check-in information may include a facility ID that identifies the facility the user checked into, the facility name, check-in date and time, granted benefits, whether a payment was made at the facility, details of the payment, or other information. When a user checks into a facility using the payment service's check-in function, check-in information is generated and stored in the user database DB1, associated with the user's user ID.
[0046] The reward information included in the check-in information is information about the rewards that a user receives when they check in to a facility using the check-in function of the payment service. The reward can be anything that provides some kind of benefit to the user and may be any reward. For example, the reward may be points, an increased rate of points that can be earned through payment, a lottery draw, coupons, a free product exchange voucher, a free service voucher, content such as videos, electronic value other than content, or something else. If the reward is not granted immediately, the reward information may indicate when the reward will be granted. The reward information may be separate from the check-in information.
[0047] In the first embodiment, we take as an example the case in which, in the facility database DB2 described later, the detailed information of the benefits associated with the facility ID of the facility where the user checked in is stored in the user database DB1 as granted benefit information. The granted benefit information may include only a part of the detailed benefit information, or it may include information different from the detailed benefit information. For example, if the benefit is granted after a certain amount of time has passed since the user checked in to the facility, the granted benefit information may include information about when the benefit is granted.
[0048] Figure 5 shows an example of the facility database DB2 in the first embodiment. The facility database DB2 is a database that stores various information about each of the multiple facilities that users can check in to using the check-in function of the payment service. For example, the facility database DB2 stores facility ID, facility name, facility location information, type information, and benefit details. The information stored in the facility database DB2 is not limited to the example in Figure 5. Other information may be stored in the facility database DB2. For example, the facility database DB2 may store information that can identify the facility terminal 30 placed in the facility (e.g., IP address or terminal name), or actual data of facility content as described in the modified examples below.
[0049] The facility ID is an example of facility identification information that can identify a facility. Facility identification information may be other information besides the ID. In the first embodiment, the facility ID for the payment service and the facility ID for the check-in service are given as an example, but they may be different. If they are different, their correspondence is defined in the facility database DB2 or another database. The other database may be stored in the check-in system 1 or in an external system. By defining these correspondences, at least one of the check-in system 1 and the external system can identify which facility corresponds to which facility ID. The same may apply to other facility identification information besides the facility ID.
[0050] The facility name is the name of the facility. The facility location information is information about the location of the facility. The location of the facility may be identified by publicly known information. For example, the facility location information may be latitude and longitude, coordinates (e.g., GPS coordinates, or coordinates used by GNSS other than GPS), address, access point information, mobile base station information, information on other communication equipment, or other information. If the facility can be identified by the facility name and facility location information, then the facility name and facility location information may be considered facility identification information.
[0051] Type information is information about the type of facility. For example, type information indicates whether a facility is a check-in service participating facility or a check-in service non-participating facility. In other words, type information indicates which of the payment service and check-in service the facility participates in. In the first embodiment, there are three types: a check-in service non-participating facility that participates only in the payment service, a check-in service participating facility that participates only in the check-in service, and a check-in service participating facility that participates in both the payment service and the check-in service. Therefore, the type information for each facility indicates which of these three types the facility belongs to.
[0052] In the example in Figure 5, the facility "BBB Shop" is a check-in service participating facility that only participates in the check-in service among the payment service and check-in service. The facility "CCC Store" is a check-in service non-participating facility that only participates in the payment service among the payment service and check-in service. The facility "DDD Mart" is a check-in service participating facility that participates in both the payment service and check-in service.
[0053] Note that in the SC3 check-in app screen, as shown in the example in the lower right of Figure 2, facilities "BBB Shop" and "DDD Mart," which are participating facilities in the check-in service, are displayed, but facility "CCC Store," which is not a participating facility in the check-in service, is not displayed. In other words, users cannot check in to facility "CCC Store" through the check-in service. On the other hand, users can check in to all three types of facilities through the check-in function of the payment service, so they can check in to each of "BBB Shop," "CCC Store," and "DDD Mart."
[0054] The reward details section contains information about the details of the reward granted to the user. The reward details section indicates the specific content of the reward. If the reward is not granted immediately, the reward details section may indicate when the reward will be granted. In the first embodiment, when a user checks in at a facility participating in the check-in service, the reward is granted by the check-in service provider. When a user checks in at a facility not participating in the check-in service, the reward is granted by the payment service provider. The reward granting information may indicate the entity granting the reward.
[0055] Furthermore, the benefit details may also include other information related to the benefit. For example, if there are other conditions other than check-in for the benefit to be granted, the benefit details may include those other conditions. In the first embodiment, we take the example of a case where there are no other conditions, but as shown in the modifications described later, for facilities that are not members of the check-in service, payment as well as check-in may be conditions for the benefit to be granted. If there are designated time slots during which users can check in to the facility, the time slot during which the user checks in to the facility may also be a condition for the benefit to be granted.
[0056] In the first embodiment, since the payment service is linked to the check-in service, the payment service can also obtain information from the check-in service about check-in service member facilities that are members of the check-in service but not the payment service. Information about check-in service member facilities that are members of the check-in service but not the payment service is shared from the check-in service to the payment service and stored in the facility database DB2. Therefore, even if a check-in service member facility is a member of the check-in service but not the payment service, the information about that check-in service member facility is stored in the facility database DB2.
[0057] The data stored in the data storage unit 100 is not limited to the above example. The data storage unit 100 only needs to store the data necessary to provide the check-in function in the payment service. For example, the data storage unit 100 may store data for displaying each screen, with the code screen SC2 being one example.
[0058] [1-3-2. Payment Execution Department] The payment execution unit 101 executes the payment based on the payment function of the payment service. For example, when the facility terminal 30 reads code C20 with the reading unit 36, it obtains a code ID from code C20. The facility terminal 30 sends a payment request to the server 10, which includes the code ID and other information such as the payment amount. The server 10 receives the payment request from the facility terminal 30. The payment execution unit 101 obtains the payer information associated with the code ID included in the payment request based on the user database DB1, and executes the payment of the payment amount included in the payment request based on the payment method information of the payment method indicated by the payer information. When a user makes a payment at a facility, the payment execution unit 101 updates the payment history information associated with the user's user ID and login account. For example, the payment history information shows the facility ID of the facility where the payment was made, the date and time of the payment, and the payment amount.
[0059] The payment execution unit 101 may execute the payment using processing similar to that of known payment services. If other types of payment methods are used, the payment execution unit 101 may execute those other types of payments. The check-in system 1 does not have to include the payment execution unit 101. That is, the payment may be executed outside of the check-in system 1. The check-in system 1 may identify the facility where the user made the payment by acquiring data indicating the result of the payment executed externally.
[0060] [1-3-3. Check-in Section] The check-in unit 102 checks the user into a facility they have visited. In the first embodiment, the check-in unit 102 checks the user into either a facility that is a member of a check-in service different from the payment service, or a facility that is not a member of a check-in service but is a member of the payment service. For example, the check-in unit 102 communicates with at least one of the user terminal 20 and the facility terminal 30 and checks the user into either a facility that is a member of a check-in service or a facility that is not a member of a check-in service, based on the check-in function of the payment service.
[0061] "Anyone from among the participating and non-participating facilities of the check-in service" refers to a person who actually visited the facility, either a participating or non-participating facility. "Anyone from among the participating and non-participating facilities of the check-in service" can also refer to a person selected by the user, or a person who is eligible for check-in by the user.
[0062] In the first embodiment, the check-in unit 102 checks the user into either a check-in service member facility that participates in both the check-in service and the payment service, or a check-in service member facility that participates in the check-in service but not the payment service. In other words, in the payment service of the first embodiment, facilities that do not participate in its own service are also subject to check-in. Users cannot use the payment function of the payment service at check-in service member facilities that participate in the check-in service but not the payment service, but they can use the check-in function of the payment service.
[0063] In the first embodiment, a check-in method in which a user checks in to a facility using GPS is given as an example. For example, the user terminal 20 acquires user location information based on the signal received by the GPS receiver 26. User location information can also be said to be information about the location of the user terminal 20. When the GPS receiver 26 is used, GPS coordinates correspond to user location information, but the user's location may be identified by publicly known information. For example, user location information may be latitude and longitude, coordinates (e.g., GNSS coordinates other than GPS), address, access point information, mobile base station information, information on other communication devices, or other information.
[0064] The user terminal 20 may also acquire user location information based on a GNSS receiver other than the GPS receiver 26. The user terminal 20 may also acquire user location information based on the communication content of the communication unit 23. For example, the user terminal 20 may acquire user location information by acquiring at least one of access point information and mobile base station information based on the communication content of the communication unit 23. Furthermore, the user terminal 20 can transmit user location information to the server 10 at any time. For example, the user terminal 20 may acquire user location information when the payment application is launched and transmit it to the server 10, or it may acquire user location information before the payment application is launched and transmit it to the server 10. The user terminal 20 may repeatedly acquire the latest user location information and transmit it to the server 10.
[0065] For example, server 10 obtains user location information from user terminal 20. Check-in unit 102 identifies facilities within a predetermined distance from the location indicated by the user location information as facilities to be checked in, based on the facility location information stored in the facility database DB2. Check-in unit 102 performs check-in to the identified facilities. If the user selects a facility to be checked in on user terminal 20, check-in unit 102 may permit check-in to the facility selected by the user, provided that the distance between the location indicated by the facility location information of the selected facility and the location indicated by the user location information is within a predetermined distance.
[0066] In the first embodiment, the check-in unit 102 allows a user to check in to a facility by recording in the data storage unit 100 that the user has checked in to the facility. For example, the check-in unit 102 generates check-in information indicating that the user has checked in to the facility (for example, check-in information indicating the facility ID of the specified facility and the current date and time of check-in), and stores it in the user database DB1 in association with the user's user ID and login account, thereby allowing the user to check in to the specified facility.
[0067] Furthermore, if check-in information is managed on a computer other than server 10, check-in unit 102 may notify the other computer that the user has checked into the facility, thereby allowing the user to check in to the facility. For example, check-in unit 102 may send user identification information, such as a user ID, and the facility ID of the specified facility to the other computer, thereby allowing the user to check in to the facility. The other computer receives this information and records the check-in information indicating that the user has checked into the facility.
[0068] Furthermore, the processing performed by the check-in unit 102 to allow the user to check in to a facility may be the same as the processing employed in known check-in methods. For example, if a check-in method other than GPS is used, the check-in unit 102 will allow the user to check in to the facility by executing the processing employed in the other check-in method. For example, if ultrasound emitted by the facility is used, the server 10 will obtain information from the user terminal 20 indicating that the user terminal 20 has detected a predetermined ultrasound. The check-in unit 102 may allow the user to check in to the facility based on this information. The facility to be checked in may be identified from the ultrasound pattern or from the user's location information.
[0069] For example, if a beacon emitted by a facility is used, the server 10 obtains information from the user terminal 20 indicating that the user terminal 20 has detected a predetermined beacon. The check-in unit 102 may, based on this information, have the user check in to the facility. The facility to be checked in to may be identified from the beacon information or from the user's location information. Similarly, if other check-in methods are used, such as the user terminal 20 reading a check-in code at the facility, or the facility terminal 30 reading a check-in code displayed on the user terminal 20, the check-in unit 102 may identify the facility to be checked in to and have the user check in to that facility in the same manner as known check-in methods.
[0070] [1-3-4. Benefits Distribution Section] The reward granting unit 103 grants a reward to a user when the user checks in to the facility. When a user checks in to the facility, it means that the check-in to the facility was performed by the check-in unit 102. When the reward granting unit 103 grants a reward, it means that the reward granting unit 103 associates information indicating that a reward has been granted with user identification information such as a user ID or login account. In the first embodiment, the reward granting unit 103 grants a reward to a user by associating the user ID and login account of a user with granted reward information indicating the reward to be granted to that user and storing it in the user database DB1. The reward granting unit 103 may also grant a reward to a user by storing the reward granting information in another database or by sending a notification to the user terminal 20 indicating that a reward has been granted.
[0071] For example, the reward granting unit 103 may grant the reward to the user immediately after the user checks in to the facility, or it may grant the reward to the user after a certain amount of time (for example, 2-3 days) has passed since the user checked in to the facility. The reward granting unit 103 only needs to grant the reward to the user on the condition that the user has checked in to the facility. The user checking in to the facility may be one of several conditions for granting the reward to the user. The content of the reward may be the same for all facilities, but in the first embodiment, since each facility has its own set of rewards, the reward granting unit 103 identifies which reward to grant by obtaining detailed reward information associated with the facility the user checked in to from the facility database DB2.
[0072] In the first embodiment, the reward granting unit 103 grants a reward to the user when the user checks in to a facility that is not a member of the check-in service. That is, the reward granting unit 103 grants a reward to the user on the condition that the user checks in to a facility that is not a member of the check-in service. Since the user can also check in to a facility that is a member of the check-in service, the reward granting unit 103 grants a reward to the user when the user checks in to a facility that is a member of the check-in service. That is, the reward granting unit 103 grants a reward to the user on the condition that the user checks in to a facility that is a member of the check-in service. For example, the reward granting unit 103 may grant a reward to the user by updating the check-in information to indicate the rewards available at facilities that are members of the check-in service.
[0073] In the first embodiment, the benefit granted when a user checks in to a participating facility is given by the system of an external check-in service rather than by the check-in system 1. However, the benefit granting unit 103 may grant the benefit to the user when the user checks in to a participating facility. The user may receive both the benefit from the payment service and the benefit from the check-in service when checking in to a participating facility.
[0074] [1-4. Processing performed by the check-in system of the first embodiment] Figure 6 shows an example of the process performed by the check-in system 1 of the first embodiment. The control units 11, 21, and 31 execute the programs stored in the storage units 12, 22, and 32, respectively, thereby executing the process shown in Figure 6. The steps in Figure 6 are an example of a method for granting benefits.
[0075] As shown in Figure 6, when a user performs an operation to start the user terminal 20, the user terminal 20 displays the menu screen SC1 on the display unit 25 (S1). The user terminal 20 identifies the user operation performed from the operation unit 24 (S2). In S2, the user performs either an operation to select icon I10 or an operation to select icon I11. If the user selects icon I11 in S2 (S2:I11), the user terminal 20 performs a check-in process with the check-in service computer and this process ends.
[0076] In S2, if the user selects icon I10 (S2:I10), the user terminal 20 accesses the server 10 (S3). The server 10 performs a login process with the user terminal 20 to allow the user to log in to the payment service (S4). The server 10 performs a process with the user terminal 20 to display the code screen SC2 (S5). In S5, the server 10 issues a new code ID and stores it in the user database DB1. The server 10 displays the code screen SC2 on the user terminal 20 by sending the display data (e.g., HTML data) of the code screen SC2, which includes the code C20 indicating the issued code ID, to the user terminal 20. The generation of code C20 may be performed on the user terminal 20 side.
[0077] When the code screen SC2 is displayed, the user can perform any operation to use the payment service. Here, we will take the case where the user selects icon I21 as an example. When the user selects icon I21, the user terminal 20 sends a usage request to the server 10 requesting to use the check-in function of the payment service (S6). When the server 10 receives the usage request, it performs a process with the user terminal 20 to check the user into either a facility that is a member of the check-in service or a facility that is not a member of the check-in service (S7). The details of the process in S7 are as described in the process of the check-in unit 102.
[0078] When the user has the facility terminal 30 read code C20, the facility terminal 30 executes a settlement with the server 10 (S8). The details of the S8 process are as described in the settlement execution unit 101 process. The server 10 executes a process to grant the user a benefit (S9), and this process ends. The details of the S9 process are as described in the benefit granting unit 103 process. If the execution of the settlement does not constitute a condition for granting a benefit, the S9 process may be executed before the S8 process. If the user checks in at a check-in service participating facility, the S9 process may not be executed.
[0079] [1-5. Summary of the First Embodiment] The first embodiment of the check-in system 1 allows users to check in to either a facility participating in the check-in service or a facility not participating in the check-in service. The check-in system 1 grants the user a benefit when the user checks in to a facility not participating in the check-in service. As a result, users can use the check-in function of the payment service to check in not only to facilities participating in the check-in service but also to facilities not participating in the check-in service. Therefore, the check-in system 1 can increase the effectiveness of attracting customers to various facilities and conduct appropriate promotions to users.
[0080] [2. Modified Examples of the First Embodiment] This disclosure is not limited to the first embodiment described above. This disclosure may be modified as appropriate without departing from the spirit of this disclosure.
[0081] Figure 7 shows an example of a function realized in a modified version of the first embodiment. For example, the server 10 includes a check-in notification unit 104, a user location information acquisition unit 105, a facility information acquisition unit 106, a facility location information acquisition unit 107, a display control unit 108, and an automatic application unit 109. Each of the check-in notification unit 104, the user location information acquisition unit 105, the facility information acquisition unit 106, the facility location information acquisition unit 107, the display control unit 108, and the automatic application unit 109 is realized by the control unit 11.
[0082] [2-1. Variation 1] For example, the reward granting unit 103 does not have to grant a reward to a user if the user checks in to a facility that is not a member of the check-in service and does not make a payment using the payment service at that facility. The reward granting unit 103 may grant a reward to a user if the user checks in to a facility that is not a member of the check-in service and makes a payment using the payment service at that facility. In other words, the reward granting unit 103 may grant a reward to a user not only on the condition that the user checks in to a facility that is not a member of the check-in service, but also on the condition that the user makes a payment using the payment service at that facility. In the example in Figure 5, the reward granting unit 103 grants a reward to a user on the condition that both check-in and payment are performed at the facility "CCC Store", which is a facility that is not a member of the check-in service.
[0083] For example, the reward granting unit 103 identifies, based on the processing result of the payment execution unit 101 and the processing result of the check-in unit 102, that a user has checked in to a facility that is not a member of the check-in service and that the user has made a payment using the payment service at the facility that is not a member of the check-in service. In the example described in the first embodiment, the processing result of the check-in unit 102 is stored in the user database DB1 as check-in information. Payment history information showing the processing result of the payment execution unit 101 may also be stored in the user database DB1. For example, if a user checks in to a facility that is not a member of the check-in service on the day the user does not make a payment using the payment service at the facility that is not a member of the check-in service, the reward granting unit 103 may determine that the user has checked in to the facility that is not a member of the check-in service and that the user has not made a payment using the payment service at the facility that is not a member of the check-in service.
[0084] For example, the reward granting unit 103 identifies a user who has both checked in and made a payment at a facility that is not a member of the check-in service, based on multiple payment history information and multiple check-in information, through batch processing. Based on this information, the reward granting unit 103 may also identify that the user checked in to a facility that is not a member of the check-in service and that the user made a payment using the payment service at that facility. The batch processing may be executed at any time, for example, at a predetermined time on a given day, or multiple times on a given day.
[0085] Furthermore, the reward granting unit 103 may determine, rather than in batch processing, whether a user has already performed either check-in or payment at a facility that is not a member of the check-in service, when that user has performed either check-in or payment at that facility. In other words, the reward granting unit 103 may determine in real time whether a user has performed either check-in or payment. In this case as well, the reward granting unit 103 only needs to make the determination based on at least one of the payment history information and the check-in information. The payment history information and the check-in information may be managed in separate databases.
[0086] Furthermore, check-in and payment may be performed in any order. For example, the reward granting unit 103 may grant a reward to a user if the user checks in to a facility that is not a member of the check-in service and then makes a payment using the payment service at that facility. The reward granting unit 103 may also grant a reward to a user if the user makes a payment using the payment service at a facility that is not a member of the check-in service and then checks in to that facility.
[0087] Furthermore, the reward granting unit 103 may grant a reward to the user on the condition that the check-in at a facility not affiliated with the check-in service and the payment at the facility are made within a predetermined period. That is, even if the user checks in at a facility not affiliated with the check-in service and makes a payment at the facility, if both of these are not made within the predetermined period, the reward granting unit 103 does not have to grant the reward to the user. The predetermined period can be any predetermined period. For example, the predetermined period can be a single day, or a predetermined time period within a single day. The predetermined period can also be any other period, such as a week or a month.
[0088] Furthermore, the reward granting unit 103 may also grant rewards to users for check-in service member facilities that participate in both check-in and payment services, on the condition that both check-in and payment are performed at the check-in service member facility. In the example in Figure 5, the reward granting unit 103 grants rewards to users on the condition that both check-in and payment are performed at the facility "DDD Mart," which is a check-in service member facility that participates in both check-in and payment services. In the check-in service, users may be granted rewards other than the aforementioned reward, or measures may be taken to prevent users from receiving rewards twice.
[0089] In Modification 1, Check-in System 1 does not grant any benefits to a user if the user checks in to a facility that is not a member of the Check-in Service and does not make a payment using the payment service at that facility. Check-in System 1 grants benefits to a user if the user checks in to a facility that is not a member of the Check-in Service and makes a payment using the payment service at that facility. As a result, Check-in System 1 can not only motivate users to visit facilities that are not a member of the Check-in Service, but also to make payments at those facilities. Check-in System 1 can not only increase the number of customers at facilities that are not a member of the Check-in Service, but also promote payments at those facilities. Check-in System 1 can effectively promote facilities that are not a member of the Check-in Service.
[0090] [2-2. Variation 2] For example, as explained to some extent in the first embodiment, check-in benefits at check-in service member facilities that do not participate in the payment service may be granted by the check-in service provider. In the example in Figure 5, the benefits for the facility "BBB Shop," which is a check-in service member facility that does not participate in the payment service, may be granted by the check-in service provider rather than by the payment service provider.
[0091] For example, a user may not check in to a participating facility using the check-in service by launching a payment app, rather than by launching a check-in app and using the payment service's check-in function. In this case, server 10 notifies the check-in service computer that the user has checked in to a participating facility. Upon receiving the notification, the check-in service computer grants the user a reward. The process by which the check-in service computer grants the user a reward may be the same as that used in publicly known check-in services.
[0092] In Modification 2, the reward granting unit 103 does not grant a reward to a user if the user checks in to a check-in service member facility that is a member of the check-in service but not a member of the payment service. For example, when the check-in process to a facility is executed by the check-in unit 102, the reward granting unit 103 obtains the type information of the facility based on the facility database DB2. If the type information indicates that the facility is a check-in service member facility that is a member of the check-in service but not a member of the payment service, the reward granting unit 103 does not grant a reward to the user. In this case, the process of granting a reward to the user is executed on the check-in service side.
[0093] In the modified example 2, the reward granting unit 103 grants a reward to the user when the user checks in to a check-in service member facility that participates in both check-in and payment services. For example, when the check-in process to a facility is executed by the check-in unit 102, the reward granting unit 103 obtains the type information of the facility based on the facility database DB2. If the type information indicates that the facility is a check-in service member facility that participates in both check-in and payment services, the reward granting unit 103 grants a reward to the user. The process for granting a reward to the user is as described in the first embodiment.
[0094] In Modification 2, Check-in System 1 does not grant rewards to users when they check in to a Check-in Service participating facility that is a participant in the Check-in Service but not in the Payment Service. This prevents the payment service from executing the process of granting rewards to users even though the Check-in Service participating facility is not a participant in the Payment Service. If the user is familiar with using a payment app, they can check in to a Check-in Service participating facility from the payment app without having to launch the Check-in app, thus improving user convenience. Furthermore, Check-in System 1 grants rewards to users when they check in to a Check-in Service participating facility that is a participant in both the Check-in Service and the Payment Service. This allows the payment service to execute the process of granting rewards to users who check in to a Check-in Service participating facility that is a participant in the Payment Service. Check-in System 1 can effectively promote Check-in Service participating facilities that are a participant in both the Check-in Service and the Payment Service.
[0095] [2-3. Variation 3] For example, as explained to some extent in the first embodiment and modification 2, the benefits of checking in to a check-in service participating facility may be granted by the check-in service provider. Modification 2 described checking in to a check-in service participating facility that participates in the check-in service without participating in the payment service, but check-in may also be performed to check-in service participating facilities that participate in both the payment service and the check-in service, not just the aforementioned check-in service participating facility.
[0096] The check-in system 1 of Modification 3 includes a check-in notification unit 104. When a user checks in to a facility affiliated with the check-in service, the check-in notification unit 104 notifies the check-in service that the user has checked in to the facility. The notification can be any data in a predetermined format indicating that a user has checked in to a facility affiliated with the check-in service. For example, the notification may include a facility ID and user identification information of the user who checked in to the facility affiliated with the check-in service (e.g., user ID and at least one of the login account). The notification may also include other information such as the check-in date and time. The check-in notification unit 104 generates a notification based on the processing result of the check-in unit 102 and sends the notification to the computer of the check-in service.
[0097] In Modification 3, when a notification is issued by the check-in notification unit 104, the user is granted a benefit by the check-in service. The benefit granted by the check-in service is different from the benefit granted by the payment service. For example, when the check-in service computer receives a notification from the check-in notification unit 104, it records information indicating that the user has checked in to a participating facility of the check-in service. The check-in service computer then executes a process to grant the user the benefit for checking in to a participating facility of the check-in service. In Modification 3, as in Modification 2, the process by which the check-in service computer grants the user the benefit may be the same as the process used in publicly known check-in services.
[0098] In Modified Example 3, Check-in System 1 notifies the Check-in Service when a user checks in to a participating facility. Upon notification, the Check-in Service grants the user a benefit. This allows Check-in System 1 to work in conjunction with the Check-in Service to grant users benefits for checking into participating facilities. Check-in System 1 can effectively promote participating facilities.
[0099] [2-4. Modification 4] For example, the check-in system 1 may acquire facility information corresponding to the user's location information. Facility information is information about a facility. Facility information can be any information related to a facility in some way. For example, facility information may be information stored in the facility database DB2 described in the first embodiment. In the example described in the first embodiment, each of the facility ID, facility name, facility location information, type information, and benefit details are examples of facility information. Facility information may also include facility images or videos, facility business hours, facility description, facility advertisements, facility coupons, products or services handled at the facility, facility industry, facility capacity, or other information. In modification 4, the facility name is described as an example of facility information.
[0100] The check-in system 1 in Modification 4 includes a user location information acquisition unit 105 and a facility information acquisition unit 106. The user location information acquisition unit 105 acquires user location information regarding the user's location when the user selects the check-in function on the user terminal 20. Selecting the check-in function is an operation on the user terminal 20. In the example in the upper right of Figure 2, the user selecting icon I21 corresponds to selecting the check-in function. Selecting the check-in function may also be the selection of other parts (user interface parts) other than icon I21 on the code screen SC2.
[0101] Furthermore, the selection of the check-in function is not limited to operations on the code screen SC2. For example, the selection of the check-in function may be performed on any screen other than the code screen SC2 within the payment app. If the check-in function of the payment service is implemented by an application other than the payment app, selecting that application may be equivalent to selecting the check-in function. If the check-in function of the payment service is implemented by a browser, specifying the URL or link on the website for the check-in function may be equivalent to selecting the check-in function.
[0102] For example, when a user selects the check-in function, the user terminal 20 acquires user location information. The method for acquiring user location information is as described in the first embodiment. The user terminal 20 may acquire user location information using the GPS receiver 26 or using the communication unit 23. The user terminal 20 transmits the user location information to the server 10. The user location information acquisition unit 105 acquires user location information from the user terminal 20. The user location information acquisition unit 105 may store the user location information in the user database DB1 in association with the user ID and login account of the user operating the user terminal 20. The user location information acquisition unit 105 may acquire user location information from devices other than the user terminal 20. For example, the user location information acquisition unit 105 may acquire user location information from a facility terminal 30 that communicates wirelessly with the user terminal 20.
[0103] The facility information acquisition unit 106 acquires facility information relating to at least one of the facilities participating in the check-in service and facilities not participating in the check-in service, based on the user's location information. The user's location information is used as a search query for facility information. The facility information is assumed to be associated with a search index. In Modification 4, the case in which facility location information is used as an index is given as an example, but the facility information itself may also be used as an index. For example, if the facility location information corresponds to facility information, the facility information itself is used as an index.
[0104] For example, the facility information acquisition unit 106 searches the facility database DB2 based on the user's location information and acquires facility information for the facilities that are found in the search. In the modified example 4, the case where the facility name corresponds to facility information is given as an example, so the facility information acquisition unit 106 acquires the facility name of the facility that is found in the search as facility information. Similarly, if other information besides the facility name corresponds to facility information, the facility information acquisition unit 106 should acquire other information about the facility that is found in the search as facility information.
[0105] For example, if facility location information is used as an index, the facility information acquisition unit 106 may identify facilities within a predetermined distance from the location indicated by the user location information based on the facility location information stored in the facility database DB2, and acquire the facility information for those facilities. The facility information acquisition unit 106 may also acquire facility information for a predetermined number of facilities in order of proximity to the location indicated by the user location information based on the facility location information stored in the facility database DB2. If the facility location information corresponds to facility information, the facility information acquisition unit 106 can use the facility information itself as an index to perform a search and acquire the facility location information corresponding to the facility information.
[0106] The facility information acquired by the facility information acquisition unit 106 can be used for any purpose. The check-in system 1 can perform predetermined processing for a predetermined purpose based on the facility information acquired by the facility information acquisition unit 106. For example, facility information may be used to display at least one of the facility list screen SC4, check-in completion screen SC5, and payment completion screen SC6, which will be described in Modification Example 5 and later. Facility information may also be used to display other screens other than these screens, or for purposes other than displaying screens in payment services. Other purposes may include facility promotion. For example, facility information may be used for sending direct mail to users, displaying web advertisements, distributing coupons, or for marketing purposes.
[0107] In the modified version 4, the check-in system 1 acquires user location information when the user selects the check-in function on the user terminal 20. Based on the user location information, the check-in system 1 acquires facility information for at least one of the facilities that are members of the check-in service and facilities that are not members of the check-in service. This allows the check-in system 1 to acquire facility information corresponding to the user's location. For example, if the check-in system 1 performs a facility promotion based on the acquired facility information, it can perform a promotion according to the user's location, thus providing the user with an appropriate promotion.
[0108] [2-5. Variation 5] For example, the facility information described in Modification 4 may be used for display control of the screen displayed on the user terminal 20. The check-in system 1 of Modification 5 includes a facility location information acquisition unit 107 and a display control unit 108. When a user selects the check-in function on the user terminal 20, the facility location information acquisition unit 107 acquires facility location information regarding the locations of facilities participating in the check-in service and facilities not participating in the check-in service. For example, the facility location information acquisition unit 107 acquires facility location information for each of multiple facilities from the facility database DB2. If the facility location information is stored in a database other than the facility database DB2, a computer other than the server 10, or an information storage medium, the facility location information acquisition unit 107 can acquire facility location information for each of multiple facilities from the other database, other computer, or information storage medium.
[0109] The facility information acquisition unit 106 in Modification 5 acquires multiple facility contents as facility information, corresponding to the user's location information, based on the location information of each facility, including facilities participating in the check-in service and facilities not participating in the check-in service. Facility contents are content related to the facility. Content is electronic information provided to the user. For example, content may be an entire screen, a part of a screen, an advertisement, a coupon, text, an image, a video, or other information. Content is not limited to information that the user can visually recognize, but may also be information that the user can auditorily recognize.
[0110] For example, the facility location information acquired by the facility location information acquisition unit 107 is used as an index for searching facility content. The facility information acquisition unit 106 searches for facility content by using the user location information as a search query and the facility location information as an index. The facility information acquisition unit 106 may identify facilities within a predetermined distance from the location indicated by the user location information based on the facility location information acquired by the facility location information acquisition unit 107 and acquire the facility content of those facilities. The facility information acquisition unit 106 may acquire the facility content of a predetermined number of facilities in order of proximity to the location indicated by the user location information based on the facility location information acquired by the facility location information acquisition unit 107.
[0111] In variation 5, we take the example where the actual facility content data is stored in the facility database DB2. Therefore, the facility information acquisition unit 106 acquires the facility content from the facility database DB2. If the facility content is stored in a database other than the facility database DB2, a computer other than the server 10, or an information storage medium, the facility information acquisition unit 106 can acquire the facility content from the other database, other computer, or information storage medium.
[0112] The display control unit 108 displays the screen to be displayed on the user terminal 20 by transmitting the display data of the screen to be displayed to the user terminal 20. The display data is the data necessary for displaying the screen. The display data may be in any format. For example, the display data may be data in a markup language such as HTML, or it may be image data or text data that is fitted into the screen format in the payment application. The display data may be data for the entire screen or data for a part of the screen.
[0113] Figure 8 shows an example of a screen displayed on the user terminal 20 in the modified example 5. As shown in Figure 8, the display control unit 108 displays a facility list screen SC4 on the user terminal 20, in which multiple facility contents C40 are arranged in order of proximity to the user's location as indicated by the user location information. The facility list screen SC4 may also show a map of the area around the user's location as indicated by the user location information. The display control unit 108 may also display each of the multiple facility contents C40 on the map in order of proximity to the user's location.
[0114] For example, the display control unit 108 sorts each of the multiple facility contents C40 acquired by the facility information acquisition unit 106 based on the distance between the user's location indicated by the user location information and the facility's location indicated by the facility location information, and generates display data for the facility list screen SC4 in which the multiple facility contents C40 are arranged. The display control unit 108 transmits the display data for the facility list screen SC4 to the user terminal 20, thereby displaying the facility list screen SC4 on the user terminal 20.
[0115] The check-in app screen SC3 in the lower right of Figure 2 is a screen on the check-in app, so the facility "CCC Mart," which is a facility that is not affiliated with the check-in service and therefore cannot be checked in by the user via the check-in service, is not displayed on the check-in app screen SC3. The facility list screen SC4 in Figure 8 is a screen on the payment app, so the facility content C40 of the facility "CCC Mart," which is a facility that is not affiliated with the check-in service and can be checked in by the user via the check-in function of the payment service, is displayed on the facility list screen SC4.
[0116] In the example shown in Figure 8, the display control unit 108 arranges multiple facility contents C40 in order of proximity to the user's position, starting from the top to the bottom of the facility list screen SC4. However, the multiple facility contents C40 can be arranged in order of proximity to the user's position in a predetermined direction on the facility list screen SC4, and this predetermined direction may be any other direction. For example, the display control unit 108 may arrange multiple facility contents C40 from left to right on the facility list screen SC4, from right to left on the facility list screen SC4, or from bottom to top on the facility list screen SC4. The display control unit 108 can arrange multiple facility contents C40 in ascending or descending order of the distance between the user's position indicated by the user position information and the facility's position indicated by the facility position information.
[0117] In Modification 5, the check-in unit 102 performs check-in for the facility selected by the user from the facility list screen SC4. The check-in unit 102 does not perform check-in for facilities not selected by the user from the facility list screen SC4, nor for facilities whose facility content C40 is not displayed on the facility list screen SC4. This differs from the first embodiment in that the facilities selected by the user from the facility list screen SC4 are the targets of check-in, but the processing performed by the check-in unit 102 itself may be the same as in the first embodiment.
[0118] In the modified version 5, the check-in system 1 acquires facility location information regarding the locations of both participating and non-participating facilities when the user selects the check-in function on the user terminal 20. Based on the facility location information of both participating and non-participating facilities, the check-in system 1 acquires multiple facility contents as facility information corresponding to the user's location. The check-in system 1 displays a facility list screen SC4 on the user terminal 20, in which multiple facility contents are arranged in order of proximity to the user's location indicated by the user's location information. As a result, the check-in system 1 can display a facility list screen SC4 on the user terminal 20 that makes it easier for the user to select a facility close to their current location, thereby improving user convenience.
[0119] [2-6. Variation 6] For example, in Modification 5, a facility list screen SC4 is given as an example in which facility content C40 is arranged in order of proximity to the user's location. However, the order of facility content C40 on the facility list screen SC4 may be determined based on factors other than the user's location. In Modification 6, an example is given in which the order of facility content C40 on the facility list screen SC4 is determined based on facility type information. The check-in system 1 in Modification 6 includes a display control unit 108. The display control unit 108 in Modification 6 may be similar to at least some of the functions of the display control unit 108 described in Modification 5.
[0120] Figure 9 shows an example of a screen displayed on the user terminal 20 in Modification 6. For example, the display control unit 108 displays a facility list screen SC4 on the user's terminal 20, in which the facility content C40 of each facility, whether a facility is a member of the check-in service or a non-member of the check-in service, is arranged according to whether it is a member of the check-in service or a payment service. Since the type information indicates whether each facility is a member of the check-in service or a payment service, the display control unit 108 in Modification 6 determines the arrangement of the facility content C40 of each facility on the facility list screen SC4 based on the type information of each facility.
[0121] In the example shown in Figure 9, the display control unit 108 displays a facility list screen SC4 on the user terminal 20 in which the facility content C40 of facilities participating in the check-in service (for example, the facility content C40 of facility "BBB Shop" and facility "DDD Mart") is given priority over the facility content C40 of facilities not participating in the check-in service (for example, the facility content C40 of facility "CCC Store"). Here, priority means earlier in the order. In the example shown in Figure 9, the facility content C40 is arranged from top to bottom, so being at the top corresponds to priority. The display control unit 108 may also display a facility list screen SC4 on the user terminal 20 in which the facility content C40 of facilities not participating in the check-in service is given priority over the facility content C40 of facilities participating in the check-in service.
[0122] The display control unit 108 may also display a facility list screen SC4 on the user terminal 20 in which facility content C40 of check-in service member facilities that are members of the check-in service but not the payment service is given priority over facility content C40 of check-in service member facilities that are members of both the payment service and the check-in service. The display control unit 108 may also display a facility list screen SC4 on the user terminal 20 in which facility content C40 of check-in service member facilities that are members of both the payment service and the check-in service is given priority over facility content C40 of check-in service member facilities that are members of the check-in service but not the payment service.
[0123] In the modified version 6, the check-in system 1 displays a facility list screen SC4 on the user terminal 20, in which the facility content C40 of each facility, whether a facility is a member of the check-in service or a non-member of the check-in service, is arranged according to whether it is a member of the check-in service or a payment service. As a result, the check-in system 1 can display a facility list screen SC4 on the user terminal 20 that makes it easy for the user to intuitively understand whether each facility, whether a member of the check-in service or a non-member of the check-in service, is a member of the check-in service or a payment service, thereby improving user convenience.
[0124] [2-7. Variation 7] For example, the content displayed on the user terminal 20 may change depending on whether the user checks in at a facility that is a member of the check-in service or a facility that is not a member of the check-in service. In Modification 7, the case where the content is facility content C40 is given as an example, but the content may be other content different from the facility content C40 in Modifications 5 and 6. The check-in system 1 in Modification 7 includes a display control unit 108. The display control unit 108 in Modification 7 may be similar to at least some of the functions of the display control unit 108 described in Modifications 5 and 6.
[0125] Figure 10 shows an example of the screen displayed on the user terminal 20 in Modification 7. The display control unit 108 in Modification 7 displays facility content C40, which is an example of content depending on whether the user is checking in at a facility that is a member of the check-in service or a facility that is not a member of the check-in service, on the user terminal 20. In the example in Figure 10, the display control unit 108 displays facility content C40 on the user terminal 20 that indicates whether each facility is a member of the check-in service or a facility that is not a member of the check-in service. The display control unit 108 only needs to identify whether a facility is a member of the check-in service or a facility that is not based on the type information.
[0126] Furthermore, if separate check-in methods are available for facilities participating in the check-in service and facilities not participating in the check-in service, the display control unit 108 may display facility content C40 on the user terminal 20 that indicates the respective check-in methods for participating and non-participating facilities. The display control unit 108 may also display facility content C40 on the user terminal 20 that indicates the respective benefits for participating and non-participating facilities. The display control unit 108 may also display content similar to facility content C40 on screens other than the facility list screen SC4.
[0127] In the modified example 7, the check-in system 1 displays content on the user's terminal that corresponds to whether the user is checking in at a facility that is a member of the check-in service or a facility that is not. This makes it easier for the user to understand whether the facility they are checking into is a member of the check-in service or a facility that is not, thus improving user convenience.
[0128] [2-8. Variation 8] For example, the content that a user checks into, depending on whether it is a facility participating in the check-in service or a facility not participating in the check-in service, is not limited to the example described in Modification 7. Modification 8 gives an example of a case where the content is check-in benefit content related to the benefits granted upon check-in. Check-in benefit content is content that shows the specific details of the benefits granted to the user.
[0129] Figure 11 shows an example of a screen displayed on the user terminal 20 in Modification 8. For example, when the user selects icon I21 on the code screen SC2, the display control unit 108 displays the facility list screen SC4 on the user terminal 20, as shown in the upper left of Figure 11. The processing for displaying the facility list screen SC4 may be the same as in any of Modifications 5 to 7. When the user selects the facility content C40 of the facility to be checked in, a screen for confirmation of check-in is displayed, and then the check-in process is executed by the check-in unit 102. In Modification 8, the check-in process may be executed without the facility list screen SC4 being displayed.
[0130] For example, as shown in the upper right of Figure 11, the display control unit 108 displays the check-in reward content C50 on the user terminal 20 when a user checks in to a facility participating in the check-in service. The display control unit 108 displays the check-in reward content C50 on the user terminal 20 on the condition that the user has checked in to a facility participating in the check-in service. When the user checks in to the facility, the display control unit 108 displays a check-in completion screen SC5 on the user terminal 20 to indicate that the check-in has been completed.
[0131] Furthermore, if check-in at a participating facility is performed by the check-in service provider, the display control unit 108 will work in conjunction with the check-in service's computer to detect that check-in has been performed and will display the check-in completion screen SC5 on the user terminal 20. In the example in the upper right of Figure 11, the check-in completion screen SC5 includes the check-in benefit content C50. The display control unit 108 retrieves the check-in benefit content C50 based on the benefit details of the facility the user checked into, and displays the check-in completion screen SC5, which includes the retrieved check-in benefit content C50, on the user terminal 20. The display control unit 108 may also display the check-in benefit content C50 on a screen other than the check-in completion screen SC5.
[0132] For example, as shown in the lower right of Figure 11, the display control unit 108 does not display the check-in benefit content C50, which is content related to the benefits granted by check-in, on the user terminal 20 when the user checks in at a facility that is not a member of the check-in service. In the example in the lower right of Figure 11, the check-in completion screen SC5 does not include the check-in benefit content C50. The display control unit 108 can obtain information on the type of facility the user checked into based on the processing result of the check-in unit 102 and determine whether the user checked into a facility that is a member of the check-in service or a facility that is not a member of the check-in service.
[0133] In the modified version 8, the check-in system 1 does not display the check-in benefit content C50 on the user terminal 20 when the user checks in at a facility that is not a member of the check-in service. The check-in system 1 displays the check-in benefit content C50 on the user terminal 20 when the user checks in at a facility that is a member of the check-in service. This allows the user to understand the benefits they are entitled to by checking the check-in benefit content C50, thus improving user convenience.
[0134] [2-9. Variation 9] For example, the display control unit 108 may display payment reward content, which is content relating to rewards that are conditional on both checking in and making a payment using the payment service, on the user terminal 20 when a user checks in at a facility that is not a member of the check-in service, or when a user checks in at a facility that is a member of the check-in service and also participates in the payment service.
[0135] The payment reward content is content related to rewards that are conditional on both check-in and payment being performed. Rewards may be granted if check-in is performed first and payment is performed later, or if payment is performed first and check-in is performed later. The actual data for the payment reward content is stored in the data storage unit 100. Common payment reward content may be provided for all facilities, or payment reward content may be provided for each facility.
[0136] Figure 12 shows an example of a screen displayed on the user terminal 20 in Modification 9. Figure 12 shows an example where a user checks in to a facility that is not a member of the check-in service. For example, when the user selects icon I21 on the code screen SC2, the display control unit 108 displays the facility list screen SC4 on the user terminal 20, as shown in the upper left of Figure 12. This process may be the same as in any of Modifications 5 to 7. When the user selects facility content C40 of the facility that is not a member of the check-in service to be checked in, a screen for confirmation of check-in is displayed, and then the check-in process is executed by the check-in unit 102. In Modification 9, the check-in process may be executed without the facility list screen SC4 being displayed.
[0137] For example, when a user checks in to a facility that is eligible for check-in, the display control unit 108 displays a check-in completion screen SC5 on the user terminal 20 to indicate that the check-in is complete. If the user checks in to a facility that is not a member of the check-in service, the display control unit 108 displays payment reward content C51 on the user terminal 20, which is content related to the benefits granted by check-in and payment, as shown in the upper right of Figure 12. At this point, since payment has not yet been made, the benefits are not granted to the user. In the example in the upper right of Figure 12, the payment reward content C51 shows the details of the benefits granted when the user also makes a payment at the non-member of the check-in service facility where they checked in.
[0138] For example, when the user returns to the code screen SC2, the display control unit 108 displays the code screen SC2 on the user terminal 20, as shown in the lower left of Figure 12. The process for displaying the code screen SC2 is as described in the first embodiment. When the user has the facility terminal 30 read the code C20, the payment execution unit 101 executes the payment. The process for payment is also as described in the first embodiment.
[0139] For example, when a user completes payment at a non-participating facility where they have checked in, the display control unit 108 displays a payment completion screen SC6 on the user terminal 20, as shown in the lower right of Figure 12. The payment completion screen SC6 displays the payment details (e.g., facility name, payment amount, and payment date and time) and the details of the benefits granted by the payment. The display control unit 108 generates the display data for the payment completion screen SC6 based on the processing result of the payment execution unit 101 and the benefit details stored in the facility database DB2. The display control unit 108 displays the payment completion screen SC6 on the user terminal 20 by sending the display data for the payment completion screen SC6 to the user terminal 20.
[0140] Furthermore, the same screen transitions as in Figure 12 may occur when a user checks in to a check-in service participating facility that also participates in payment services in addition to check-in services. When a user checks in to such a check-in participating facility, the user may be able to receive both the benefits of the check-in service and the benefits of the payment service. In this case, the display control unit 108 may display check-in benefit content C50, which indicates the benefits of the check-in service, separately from the payment benefit content C51, on the check-in completion screen SC5, which indicates that the user has checked in to the check-in participating facility.
[0141] Furthermore, the display control unit 108 may display the payment reward content C51 on screens other than the check-in completion screen SC5. For example, the display control unit 108 may display the payment reward content C51 on the facility list screen SC4. The display control unit 108 may also display the payment reward content C51 on the confirmation screen that appears after the facility list screen SC4. The display control unit 108 may also display the payment reward content C51 on other screens such as the code screen SC2. The display control unit 108 may also display the payment reward content C51 in applications other than the payment application, or in a browser instead of a dedicated application.
[0142] In the modified version 9, the check-in system 1 displays payment reward content C51 on the user terminal 20 when a user checks in at a facility that is not a member of the check-in service, or when a user checks in at a facility that is a member of the check-in service and also participates in the payment service. This allows the user to understand the rewards they are entitled to by checking the payment reward content C51, thus improving user convenience. For example, if the payment reward content C51 is displayed on the check-in completion screen SC5, the user can understand that there are rewards that cannot be obtained by checking in alone. The check-in system 1 can motivate the user to make a payment using the payment service, thereby promoting the use of the payment service at the facility where the user has checked in.
[0143] [2-10. Variation 10] For example, in Modification 9, the display control unit 108 may display coupons usable at non-member or member facilities of the check-in service where the user checks in, as payment reward content C51 on the user terminal 20 before payment is executed. Modification 10 takes the example of a case where the reward details stored in the facility database DB2 indicate a coupon. The reward details show the details of the coupon. For example, the reward details may show the discount amount or discount rate obtained by using the coupon, the product or service to which the coupon applies, the price after applying the coupon, the validity period of the coupon, or other information.
[0144] The screen transition flow in Modification 10 may be the same as in Modification 9. Taking Figure 12 as an example, when a user checks in to a facility that is not a member of the check-in service, the display control unit 108 displays the payment reward content C51, which shows a coupon, on the check-in completion screen SC5. In Modification 10, the payment reward content C51 in the upper right of Figure 12 shows a coupon that can be used at the check-in service non-member facility where the user checked in. The display control unit 108 obtains the reward details of the check-in service non-member facility where the user checked in from the facility database DB2, and based on the obtained reward details, generates the display data for the check-in completion screen SC5, which includes the payment reward content C51, and sends it to the user terminal 20.
[0145] Furthermore, the same screen transitions may occur when a user checks in at a check-in service participating facility that also participates in payment services in addition to check-in services. Similar to Modification 9, the display control unit 108 may also display payment reward content C51, which indicates a coupon, on screens other than the check-in completion screen SC5. In Modification 10, a coupon that the user can use on their next visit may be granted as a reward after payment is completed.
[0146] In the modified version 10, the check-in system 1 displays coupons usable at the non-member or member facility of the check-in service where the user is checking in, as payment reward content C51, on the user terminal 20 before payment is processed. This allows the user to understand which coupons are available to them by checking the coupons shown in the payment reward content C51, thus improving user convenience. The check-in system 1 can also motivate users to use coupons, thereby promoting the use of the facility where the user has checked in.
[0147] [2-11. Variation 11] For example, the coupon described in Modification 10 may be automatically applied during payment using the payment service. Modification 11 provides an example of a case where the same screen transitions as in Modification 10 occur. In the example shown in Figure 12, the display control unit 108 displays the payment reward content C51 indicating the coupon on the check-in completion screen SC5, and then displays the payment completion screen SC6 when the user performs the payment operation. The payment completion screen SC6 may indicate that the coupon has been automatically applied. In Modification 11, when a user checks in at a facility that is not a member of the check-in service or a facility that is a member of the check-in service and has a coupon, the details of the coupon are shown in the check-in information.
[0148] The check-in system 1 of Modification 11 includes an automatic application unit 109. The automatic application unit 109 automatically applies the coupon when payment is made. Automatically applying the coupon means that the coupon is applied without the user having to perform any operation to apply the coupon on the user terminal 20. Applying a coupon can also be referred to as using a coupon. For example, providing a discount using a coupon, or exchanging a coupon for goods or services, is equivalent to applying a coupon. Coupons acquired by the user through check-in are included in the granted benefit information contained in the check-in information.
[0149] For example, when the server 10 receives a payment request from the user terminal 20 or the facility terminal 30, the automatic application unit 109 determines, based on the check-in information, whether or not there is a coupon that can be automatically applied. If the automatic application unit 109 determines that there is no coupon that can be automatically applied, it does not automatically apply the coupon. If it determines that there is a coupon that can be automatically applied, it automatically applies the coupon. The automatic application unit 109 calculates the final payment amount by deducting the amount corresponding to the coupon from the payment amount indicated by the payment request. The payment execution unit 101 executes the payment based on the payment amount calculated by the automatic application unit 109.
[0150] Furthermore, the processing performed by the automatic application unit 109 is not limited to processing for discounts. For example, if the coupon is for the exchange of goods or services rather than a discount, the automatic application unit 109 can automatically apply the coupon by sending a notification to the user terminal 20 or facility terminal 30 indicating that the coupon will be applied and the goods or services will be exchanged.
[0151] The check-in system 1 in modified example 11 automatically applies the coupon when payment is made. This eliminates the need for the user to perform any action to apply the coupon, thus improving user convenience. The check-in system 1 can also prevent users from missing the opportunity to use a coupon by forgetting to present it.
[0152] [2-12. Variation 12] For example, as explained to some extent in modified examples 10 and 11, the display control unit 108 may display the payment reward content C51 on the user terminal 20 at a predetermined timing when a payment is executed. The predetermined timing is the timing at which the payment reward content C51 is displayed. The data indicating the predetermined timing is stored in the data storage unit 100. Based on this data, the display control unit 108 determines whether or not the predetermined timing has arrived. If the display control unit 108 determines that the predetermined timing has not arrived, it does not display the payment reward content C51 on the user terminal 20. If it determines that the predetermined timing has arrived, it displays the payment reward content C51 on the user terminal 20.
[0153] For example, if the predetermined timing is the timing when the code screen SC2 is displayed, the display control unit 108 receives a notification from the user terminal 20 indicating that the payment app has been launched or the user has performed an operation to display the code screen SC2, and determines that the predetermined timing has arrived. When the display control unit 108 determines that the predetermined timing has arrived, it displays the code screen SC2, including the payment reward content C51, on the user terminal 20. The payment reward content C51 may also be displayed as a pop-up on the code screen SC2.
[0154] For example, when a payment is made in which the user terminal 20 reads a code displayed on the facility terminal 30 or a code posted at the facility, the predetermined timing may be the timing when the screen for reading these codes is displayed on the user terminal 20. When the display control unit 108 determines that the screen for reading the codes is displayed on the user terminal 20, it causes the payment reward content C51 to be displayed on the user terminal 20. When a payment is made in which the transaction is completed solely by operations on the user terminal 20, the predetermined timing may be the timing when the facility to be paid for is selected. When the facility to be paid for is selected, the display control unit 108 causes the payment reward content C51 to be displayed on the user terminal 20.
[0155] In the modified version 12, the check-in system 1 displays the payment reward content C51 on the user terminal 20 at a predetermined time when payment is made. This allows the user to check the payment reward content C51 at the appropriate time, thus improving user convenience. The check-in system 1 can also enhance the appeal of the payment reward content C51.
[0156] [2-13. Variation 13] For example, in Modification 12, the display control unit 108 may display the payment reward content C51 on the payment completion screen SC6, which indicates that the payment has been completed. That is, the predetermined timing described in Modification 12 may be the timing of the completion of the payment. In Modification 12, when the payment is executed by the payment execution unit 101, the display control unit 108 displays the payment completion screen SC6, which includes the payment reward content C51, on the user terminal 20. The payment reward content C51 on the payment completion screen SC6 shows the details of the rewards granted to the user through check-in and payment.
[0157] As shown in Modification 11, if a coupon is equivalent to a benefit and the coupon is applied automatically, the display control unit 108 displays payment benefit content C51 showing the details of the automatically applied coupon on the payment completion screen SC6. If the awarding of points or an increase in the point redemption rate is equivalent to a benefit, the display control unit 108 displays payment benefit content C51 on the payment completion screen SC6 indicating that points have been awarded or the point redemption rate has been increased.
[0158] In the modified version 13, the check-in system 1 displays the payment reward content C51 on the payment completion screen SC6, which indicates that payment has been completed. This allows the user to confirm the payment reward content C51 on the payment completion screen SC6, thus improving user convenience.
[0159] [2-14. Variation 14] For example, in modified examples 10 to 13, the display control unit 108 may prevent the payment reward content C51 from being displayed on the user terminal 20 when a user checks in at a check-in service participating facility that does not participate in the payment service. When a user checks in at a facility, the display control unit 108 determines, based on the facility type information, whether or not the user has checked in at a check-in service participating facility that does not participate in the payment service.
[0160] For example, if the display control unit 108 determines that the user has checked in to a check-in service participating facility that does not participate in the payment service, it will not display the payment reward content C51 on the user terminal 20. If the display control unit 108 does not determine that the user has checked in to a check-in service participating facility that does not participate in the payment service (i.e., if the user has checked in to a facility that does not participate in the check-in service, or to a check-in service participating facility that participates in the payment service), the display control unit 108 will display the payment reward content C51 on the user terminal 20 in the same manner as in the modified examples 10 to 13.
[0161] In the modified version 14, the check-in system 1 does not display the payment reward content C51 on the user terminal 20 when a user checks in at a check-in service participating facility that does not participate in the payment service. This prevents the check-in system 1 from displaying the payment reward content C51 on the user terminal 20 even though the user is not being granted any rewards.
[0162] [2-15. Variation 15] For example, when a user checks in to a check-in service participating facility that does not participate in the payment service, the display control unit 108 may display content other than the payment reward content C51 on the user terminal 20. The other content is content related to the check-in service participating facility where the user checked in. For example, the other content may be an advertisement or coupon for the check-in service participating facility where the user checked in, or it may be content for affiliated stores. The actual data for the other content is stored in the facility database DB2.
[0163] In the example shown in the upper left of Figure 11, the facility "BBB Shop" is a check-in service participating facility that does not participate in the payment service. When a user checks in to the facility "BBB Shop" using the check-in function of the payment service, the display control unit 108 displays a check-in completion screen SC5, which includes other content along with the check-in reward content C50 shown in the upper right of Figure 11, on the user terminal 20. The display control unit 108 may also display a check-in completion screen SC5 on the user terminal 20 that includes other content but does not include the check-in reward content C50.
[0164] The display control unit 108 may also display other content on screens other than the check-in completion screen SC5. The display control unit 108 may also display the check-in benefit content C50 and other content on separate screens in two separate steps on the user terminal 20. The display control unit 108 may also display other content on the user terminal 20 before the user checks in to a check-in service participating facility that does not participate in the payment service, rather than after the user has checked in. For example, the display control unit 108 may display other content on the user terminal 20 before the check-in process is executed when the user selects a check-in service participating facility from the facility list screen SC4.
[0165] In the modified version 15, when a user checks in at a check-in service participating facility that does not participate in the payment service, the check-in system 1 displays content other than the payment reward content C51 on the user terminal 20. This allows the user to see content other than the payment reward content C51, thereby improving user convenience.
[0166] [3. Second Embodiment] Hereafter, a second embodiment, which is an example of an embodiment of the lottery system, lottery method, and program relating to this disclosure, will be described. In the second embodiment, the case in which the check-in system 1 corresponds to the lottery system will be given as an example. For this reason, wherever "check-in system 1" is written in the second embodiment, it can be read as "lottery system". Note that the lottery system does not have to perform check-in. That is, check-in may be performed outside the lottery system. The lottery system does not have to include a check-in function. In the second embodiment, the same points as in the first embodiment will be omitted from the explanation.
[0167] For example, a user may only check in at a facility they visit without making a payment. Conversely, a user may make a payment at a facility they visit without checking in. Therefore, it is necessary to have users perform both check-in and payment. In the second embodiment, the check-in system 1 performs a first lottery when either check-in or payment is performed, and a second lottery when the other is performed, thereby providing the user with an incentive to perform both check-in and payment.
[0168] Figure 13 shows an example of the functions implemented in the check-in system 1 of the second embodiment. As shown in Figure 13, the server 10 includes a data storage unit 100, a first lottery unit 110, an execution result notification unit 111, and a second lottery unit 112. The first lottery unit 110, the execution result notification unit 111, and the second lottery unit 112 are implemented by the control unit 11. The processing performed by each of the first lottery unit 110, the execution result notification unit 111, and the second lottery unit 112 is an example of a lottery method. Although Figure 13 does not show the functions described in the first embodiment (for example, the payment execution unit 101, the check-in unit 102, and the reward granting unit 103), the server 10 may include the functions described in the first embodiment. Also, the data storage unit 100 may be the same as in the first embodiment.
[0169] Figure 14 shows an example of a screen displayed on the user terminal 20 in the second embodiment. For example, when the user selects icon I21 on the code screen SC2, the display control unit 108 displays the facility list screen SC4 on the user terminal 20, as shown in the upper left of Figure 14. This process may be the same as in any of the modifications 5 to 7. When the user selects a facility, a screen for check-in confirmation is displayed, and then the check-in process is executed by the check-in unit 102. In the second embodiment, the check-in process may be executed without the facility list screen SC4 being displayed.
[0170] The first lottery unit 110 executes the first lottery when either check-in to the facility or payment at the facility is performed. The one between check-in and payment is the one that is performed first. The user may be allowed to freely choose which of check-in and payment is performed first, or the one that is performed first may be predetermined. In other words, the user may not be allowed to freely choose which of check-in and payment is performed first. In the example in Figure 14, check-in is performed before payment, but payment may be performed before check-in.
[0171] The first lottery is a lottery that is executed on the condition that either check-in or payment is performed. The first lottery is a process that performs a predetermined determination based on a first probability. In the second embodiment, an example is given in which the process of determining whether or not a reward is granted to the user corresponds to the first lottery. The details of the reward are not determined in the first lottery. The first lottery program for the first lottery is stored in the data storage unit 100. The first probability may be defined in the first lottery program or may be defined in data separate from the first lottery program.
[0172] For example, the first lottery unit 110 performs a first lottery based on a first probability and determines whether or not the user is awarded a prize. That is, by performing the first lottery, the first lottery unit 110 determines whether or not the user has been given the right to win a prize. If the user wins the first lottery, the right is given to the user. The lottery itself may be performed by a known lottery method. If multiple prizes are available, the probability of winning may be determined for each prize. The first lottery unit 110 may determine which prize the user will win based on the probability determined for each prize.
[0173] The execution result notification unit 111 notifies the user of the result of the first draw after one of the check-in and settlement has been performed, and before the other of the check-in and settlement has been performed. The other of the check-in and settlement is the one that is not the one mentioned above. The other of the check-in and settlement can also be said to be the one that is performed after the check-in and settlement. If the check-in corresponds to one of the above, then the settlement corresponds to the other. If the settlement corresponds to one of the above, then the check-in corresponds to the other.
[0174] When the execution result notification unit 111 notifies the user of the results of the first draw, it means that the execution result notification unit 111 transmits data indicating the results of the first draw to the user terminal 20. In the example in Figure 14, the execution result notification unit 111 notifies the user of the results of the first draw by displaying a check-in completion screen SC5 on the user terminal 20, which includes execution result content C52 indicating the results of the first draw. The actual data of the execution result content C52 is assumed to be stored in the data storage unit 100. Based on this actual data, the execution result notification unit 111 displays the execution result content C52 on the check-in completion screen SC5.
[0175] The execution result notification unit 111 may also notify the user of the results of the first lottery on a screen other than the check-in completion screen SC5. For example, the execution result notification unit 111 may display the execution result content C52 on the code screen SC2, the notification function screen in the payment service, or another screen on the payment application. The execution result notification unit 111 may also notify the user of the results of the first lottery on a screen on the browser, rather than on a screen on the payment application. The execution result notification unit 111 may also notify the user of the results of the first lottery using the notification function of the user terminal 20 itself or other notification means such as email.
[0176] The second lottery unit 112 executes the second lottery when the other of check-in and payment is performed. The second lottery is a lottery that is executed on the condition that the other of check-in and payment is performed. The second lottery is a process that performs a predetermined determination based on a second probability. In the second embodiment, an example is given in which the process of determining the details of the benefit to be granted to the user corresponds to the second lottery. At the time the second lottery is executed, it is assumed that it has been determined by the first lottery that the user will be granted a benefit. For users who did not win in the first lottery, the second lottery will not be executed. Note that all users may win in the first lottery. The second lottery program for the second lottery is stored in the data storage unit 100. The second probability may be defined in the second lottery program or may be defined in data separate from the second lottery program.
[0177] In the example shown in Figure 14, after the execution result notification unit 111 has finished processing, when the user performs an operation to display the code screen SC2, the code screen SC2 is displayed as shown in the lower left of Figure 14. An example of the processing for displaying the code screen SC2 and the processing for payment is as described in the first embodiment. For example, when the user makes a payment at the facility where they checked in, the second lottery unit 112 performs a second lottery based on a second probability and determines the details of the reward to be given to the user. That is, the second lottery unit 112 determines the details of the reward by performing a second lottery.
[0178] For example, if a second probability is set for each of several benefits, the second lottery unit 112 may determine the details of the benefit to be granted to the user based on the second probability set for each benefit. As shown in the lower right of Figure 14, the display control unit 108 causes the user terminal 20 to display a payment completion screen SC6 showing the result of the second lottery. The result of the second lottery may also be displayed on a screen other than the payment completion screen SC6. The benefit granting unit 10103 of the second embodiment grants a benefit to the user based on the results of the first and second lotteries. This differs from the first embodiment in that the first and second lotteries determine whether or not a benefit is granted to the user and the details of the benefit, but the process by which the benefit granting unit 103 grants the benefit may be the same as in the first embodiment.
[0179] The first and second draws may be different draws, and are not limited to the above example. For example, the first draw may be a process that determines the details of the prize, and the second draw may be a process that determines whether or not the prize determined by the first draw will be awarded. Also, although Figure 14 shows an example where payment is made after check-in, check-in may be made after payment. That is, the first draw unit 110 may execute the first draw on the condition that payment has been made, and the second draw unit 112 may execute the second draw on the condition that check-in has been made.
[0180] The check-in system 1 of the second embodiment executes a first lottery when either check-in to a facility or payment at the facility is performed. The check-in system 1 notifies the user of the result of the first lottery after one of the two actions has been performed and before the other of check-in or payment is performed. The check-in system 1 executes a second lottery when the other action has been performed. In this way, the check-in system 1 can motivate the user to perform both check-in and payment. In the example in Figure 14, the user can learn from the execution result content C52 that they can win some kind of benefit if they make a payment, so the check-in system 1 can motivate the user to make a payment at the facility where they have checked in.
[0181] [4. Modified Examples of the Second Embodiment] This disclosure is not limited to the second embodiment described above. This disclosure may be modified as appropriate without departing from the spirit of this disclosure.
[0182] For example, in the second embodiment, unlike in the first embodiment, there may be no distinction between facilities that participate in the check-in service and facilities that do not. The check-in system 1 of the second embodiment does not need to support check-ins at facilities that participate in the check-in service but do not participate in the payment service. Even in this case, the check-in system 1 of the second embodiment can solve the problem of providing users with an incentive to both check in and pay through the first and second lotteries.
[0183] Furthermore, the issues addressed in this disclosure are not limited to those described in the means for solving the issues. The issues described in the means for solving the issues are merely one of the issues addressed by this disclosure. There are multiple issues addressed in this disclosure. This disclosure also includes embodiments that solve only one of the multiple issues. For example, a lottery system, such as the check-in system 1 described in the second embodiment, does not need to include the check-in unit 102 and the reward granting unit 103 described in the first embodiment, and therefore does not need to solve the issue of "providing appropriate promotion to users" that the check-in system 1 of the first embodiment solves. Such a lottery system is also within the scope of this disclosure. For this reason, it is obvious to a person skilled in the art who has read the contents of this disclosure that the lottery system described in appendix (2) below is supported in this disclosure.
[0184] [5. Other variations] For example, the first embodiment, the second embodiment, and several of the above modifications may be combined. In the case of combining the first and second embodiments, as explained to some extent in the second embodiment, the check-in system 1 includes a check-in unit 102, a reward granting unit 103, a first lottery 110, an execution result notification unit 111, and a second lottery unit 112. The first lottery and the second lottery may both be lotteries relating to rewards granted by the reward granting unit 103. This is as described in the example of the first and second lotteries explained in the second embodiment. The reward granting unit 103 may grant a reward to the user based on the execution result of the second lottery. For example, if the first lottery is a lottery to decide whether or not to grant a reward, and the second lottery is a lottery to decide the specific content of the reward, the reward granting unit 103 grants the user the reward determined in the second lottery if the user wins in the first lottery.
[0185] For example, if both the first and second draws are for determining whether or not to award a prize, the prize awarding unit 103 awards the prize to the user if the user wins in both the first and second draws. If both the first and second draws are for determining the content of the prize (for example, if the category of the prize is determined in the first draw and the specific content of the prize within that category is determined in the second draw), the prize determined in both the first and second draws is awarded to the user. Thus, combining the first and second embodiments is also within the scope of this disclosure. According to this embodiment, the check-in system 1 can provide the user with an incentive to perform both check-in and payment.
[0186] For example, the functions described as being implemented on server 10 may be implemented on user terminal 20, facility terminal 30, or other computers. The functions described as being implemented on server 10 may be shared among multiple computers. For example, if there is a separate server computer for the check-in service in addition to server 10, the functions described as being implemented on server 10 may be implemented on the check-in service server computer. The functions may be shared between server 10 and the check-in service server computer.
[0187] [6. Addendum] For example, a check-in system can also be configured as follows: (1-1) A check-in unit that allows users to check in to either a check-in service member facility that is affiliated with a check-in service different from the payment service, or a check-in service non-member facility that is affiliated with the payment service but is not affiliated with the check-in service. A reward granting unit that grants a reward to the user when the user checks in to a facility that is not a member of the check-in service, A check-in system that includes this. (1-2) The aforementioned benefit granting unit is: If the user checks in to a facility that is not a member of the check-in service, and the user does not make a payment using the payment service at the facility, the user will not be granted the aforementioned benefit. The user is granted the aforementioned benefit when the user checks in to a facility that is not a member of the aforementioned check-in service and makes a payment using the aforementioned payment service at the facility that is not a member of the aforementioned check-in service. The check-in system described in (1-1). (1-3) The aforementioned benefit granting unit is: If the user checks in to a facility that is a member of the check-in service but is not a member of the payment service, the user will not be granted the aforementioned benefit. When the user checks in to a facility that is a member of the check-in service and is also a member of the payment service, the user is granted the aforementioned benefit. The check-in system described in (1-1) or (1-2). (1-4) The check-in system further includes a check-in notification unit that, when the user checks in to a facility affiliated with the check-in service, notifies the check-in service that the user has checked in to the facility affiliated with the check-in service. When a notification is issued by the aforementioned check-in notification unit, the user is granted a benefit through the aforementioned check-in service. The check-in system is one of the following: (1-1) to (1-3). (1-5) The aforementioned check-in system is When the user selects the check-in function on the user terminal, a user location information acquisition unit acquires user location information regarding the user's location. A facility information acquisition unit acquires facility information relating to at least one of the facilities that are members of the check-in service and the facilities that are not members of the check-in service, based on the user location information. The check-in system described in any of (1-1) to (1-4), which further includes the above. (1-6) The check-in system further includes a facility location information acquisition unit that acquires facility location information relating to the locations of the check-in service member facilities and the check-in service non-member facilities when the user selects the check-in function on the user terminal, The facility information acquisition unit acquires multiple facility contents corresponding to the user's location information, based on the facility location information of each of the facilities participating in the check-in service and the facilities not participating in the check-in service, as facility information. The check-in system further includes a display control unit that displays a list of facilities on the user terminal, in which the multiple facility contents are arranged in order of proximity to the user's location as indicated by the user's location information. The check-in system described in (1-5). (1-7) The check-in system further includes a display control unit that displays a list of facilities on the user's terminal, in which the facility content of each facility, whether a facility is a member of the check-in service or a facility that is not a member of the check-in service, is arranged according to whether it is a member of the check-in service or the payment service. The check-in system is one of the following: (1-1) to (1-6). (1-8) The check-in system further includes a display control unit that displays content on the user's user terminal according to whether the user checks in at a facility affiliated with the check-in service or a facility not affiliated with the check-in service. The check-in system described in any of (1-1) to (1-7). (1-9) The display control unit, When the user checks in to a facility that is not a member of the check-in service, the check-in benefit content, which is the content related to the benefits granted by check-in, will not be displayed on the user's terminal. When the user checks in to a facility participating in the check-in service, the check-in benefit content is displayed on the user's terminal. The check-in system described in (1-8). (1-10) The display control unit causes the user terminal to display payment benefit content, which is content relating to a benefit that requires both check-in and payment of the payment service, when the user checks in at a facility that is not a member of the check-in service, or when the user checks in at a facility that is a member of the check-in service and is also a member of the payment service. The check-in system described in (1-8) or (1-9). (1-11) The display control unit causes the user terminal to display, as payment reward content, a coupon that can be used at the non-member facility or member facility of the check-in service where the user checks in, before the payment is executed. The check-in system described in (1-10). (1-12) The check-in system further includes an automatic application unit that automatically applies the coupon when the payment is executed. The check-in system described in (1-11). (1-13) The display control unit, when the payment is executed, causes the payment reward content to be displayed on the user terminal at a predetermined timing. The check-in system is one of the following: (1-10) to (1-12). (1-14) The display control unit displays the payment reward content on the payment completion screen, which indicates that the payment has been completed. The check-in system described in (1-13). (1-15) The display control unit, when the user checks in at a check-in service participating facility that is not a member of the payment service, will not display the payment reward content on the user terminal. The check-in system is one of the following: (1-1) to (1-14). (1-16) The display control unit, when the user checks in to a check-in service participating facility that is not a member of the payment service, causes the user terminal to display content other than the payment reward content. The check-in system described in (1-15). (1-17) The aforementioned check-in system is A first lottery execution unit executes a first lottery regarding the aforementioned benefits when either a check-in by the aforementioned person or payment by the aforementioned person is performed, An execution result notification unit that notifies the user of the result of the first lottery after one of the above has been performed and before the other of the check-in and the payment has been performed, If the other action is performed, a second lottery execution unit executes a second lottery regarding the aforementioned benefits, Includes, The reward granting unit grants the reward to the user based on the result of the second lottery. The check-in system is one of the following: (1-1) to (1-16).
[0188] For example, the lottery system can also be configured as follows: (2) A first lottery execution unit executes a first lottery when either check-in to the facility or payment at the said facility is performed, An execution result notification unit that notifies the user of the result of the first lottery after one of the above has been performed and before the other of the check-in and the payment has been performed, If the other is executed, a second lottery execution unit executes a second lottery, A lottery system that includes this. [Explanation of Symbols]
[0189] 1 Check-in system, N Network, 10 Server, 11,21,31 Control unit, 12,22,32 Storage unit, 13,23,33 Communication unit, 20 User terminal, 24,34 Operation unit, 25,35 Display unit, 26 GPS receiver, 30 Facility terminal, 36 Reading unit, 100 Data storage unit, 101 Payment execution unit, 102 Check-in unit, 103 Reward granting unit, 104 Check-in notification unit, 105 User location information acquisition unit, 106 Facility information acquisition unit, 107 Facility location information acquisition unit, 108 Display control unit, 109 Automatic application unit, 110 First lottery unit, 111 Execution result notification unit, 112 Second lottery unit, C20 Code, C40 Facility content, C50 Check-in reward content, C51 Payment reward content, C52 Execution result content, DB1 User database, DB2 Facility database, I10, I11, I21 icons, SC1 menu screen, SC2 code screen, SC3 check-in app screen, SC4 facility list screen, SC5 check-in completion screen, SC6 payment completion screen.
Claims
1. A check-in unit that causes a user to check in to any of the following: a check-in service member facility that is a member of a check-in service different from the payment service, and a check-in service non-member facility that is a member of the payment service but not the check-in service; or a check-in unit that causes a user to check in to any of the following: based on user location information relating to the location of the user's user terminal, information indicating that the user terminal has detected a predetermined ultrasonic wave or beacon, information obtained by the user terminal reading a check-in code, or information obtained by the facility terminal reading a check-in code displayed on the user terminal; A reward granting unit that, if the user checks in to a facility that is not affiliated with the check-in service and does not make a payment using the payment service at that facility, does not grant the user the reward, and grants the user the reward if the user checks in to a facility that is not affiliated with the check-in service and makes a payment using the payment service at that facility, A check-in system that includes this.
2. A check-in unit that causes a user to check in to any of the following: a check-in service member facility that is a member of a check-in service different from the payment service, and a check-in service non-member facility that is a member of the payment service but not the check-in service; or a check-in unit that causes a user to check in to any of the following: based on user location information relating to the location of the user's user terminal, information indicating that the user terminal has detected a predetermined ultrasonic wave or beacon, information obtained by the user terminal reading a check-in code, or information obtained by the facility terminal reading a check-in code displayed on the user terminal; A reward granting unit that grants a reward to the user when the user checks in at a facility that is not a member of the check-in service, does not grant the reward to the user when the user checks in at a facility that is a member of the check-in service but is not a member of the payment service, and grants the reward to the user when the user checks in at a facility that is a member of the check-in service but is also a member of the payment service, A check-in system that includes this.
3. The check-in system further includes a check-in notification unit that, when the user checks in to a facility affiliated with the check-in service, notifies the check-in service that the user has checked in to the facility affiliated with the check-in service. When a notification is issued by the aforementioned check-in notification unit, the user is granted a benefit through the aforementioned check-in service. The check-in system according to claim 1 or 2.
4. The aforementioned check-in system is When the user selects the check-in function on the user terminal, a user location information acquisition unit acquires user location information regarding the user's location. A facility information acquisition unit acquires facility information relating to at least one of the facilities that are members of the check-in service and the facilities that are not members of the check-in service, based on the user location information. The check-in system according to claim 1 or 2, further comprising:
5. The check-in system further includes a facility location information acquisition unit that acquires facility location information relating to the locations of the check-in service member facilities and the check-in service non-member facilities when the user selects the check-in function on the user terminal, The facility information acquisition unit acquires multiple facility contents corresponding to the user's location information, based on the facility location information of each of the facilities participating in the check-in service and the facilities not participating in the check-in service, as facility information. The check-in system further includes a display control unit that displays a list of facilities on the user terminal, in which the multiple facility contents are arranged in order of proximity to the user's location as indicated by the user's location information. The check-in system according to claim 4.
6. The check-in system further includes a display control unit that displays a list of facilities on the user's terminal, in which the facility content of each facility, whether a facility is a member of the check-in service or a facility that is not a member of the check-in service, is arranged according to whether it is a member of the check-in service or the payment service. The check-in system according to claim 1 or 2.
7. A check-in unit that causes a user to check in to any of the following: a check-in service member facility that is a member of a check-in service different from the payment service, and a check-in service non-member facility that is a member of the payment service but not the check-in service; or a check-in unit that causes a user to check in to any of the following: based on user location information relating to the location of the user's user terminal, information indicating that the user terminal has detected a predetermined ultrasonic wave or beacon, information obtained by the user terminal reading a check-in code, or information obtained by the facility terminal reading a check-in code displayed on the user terminal; A reward granting unit that grants a reward to the user when the user checks in to a facility that is not a member of the check-in service, When the user checks in at a facility that is not a member of the check-in service, the check-in benefit content, which is content related to the benefits granted by the check-in, is not displayed on the user terminal, and when the user checks in at a facility that is a member of the check-in service, the check-in benefit content is displayed on the user terminal. A check-in system that includes this.
8. A check-in unit that causes a user to check in to any of the following: a check-in service member facility that is a member of a check-in service different from the payment service, and a check-in service non-member facility that is a member of the payment service but not the check-in service; or a check-in unit that causes a user to check in to any of the following: based on user location information relating to the location of the user's user terminal, information indicating that the user terminal has detected a predetermined ultrasonic wave or beacon, information obtained by the user terminal reading a check-in code, or information obtained by the facility terminal reading a check-in code displayed on the user terminal; A reward granting unit that grants a reward to the user when the user checks in to a facility that is not a member of the check-in service, When the user checks in at a facility that is not a member of the check-in service, or when the user checks in at a facility that is a member of the check-in service and is also a member of the payment service, a display control unit causes the user terminal to display payment benefit content, which is content relating to a benefit that is conditional on check-in and payment of the payment service. A check-in system that includes this.
9. The display control unit causes the user terminal to display, as payment reward content, a coupon that can be used at the non-member facility or member facility of the check-in service where the user checks in, before the payment is executed. The check-in system according to claim 8.
10. The check-in system further includes an automatic application unit that automatically applies the coupon when the payment is executed. The check-in system according to claim 9.
11. The display control unit, when the payment is executed, causes the payment reward content to be displayed on the user terminal at a predetermined timing. A check-in system according to any one of claims 8 to 10.
12. The display control unit displays the payment reward content on the payment completion screen, which indicates that the payment has been completed. The check-in system according to claim 11.
13. The display control unit, when the user checks in at a check-in service participating facility that is not a member of the payment service, will not display the payment reward content on the user terminal. A check-in system according to any one of claims 8 to 10.
14. The display control unit, when the user checks in to a check-in service participating facility that is not a member of the payment service, causes the user terminal to display content other than the payment reward content. The check-in system according to claim 13.
15. A check-in unit that causes a user to check in to any of the following: a check-in service member facility that is a member of a check-in service different from the payment service, and a check-in service non-member facility that is a member of the payment service but not the check-in service; or a check-in unit that causes a user to check in to any of the following: based on user location information relating to the location of the user's user terminal, information indicating that the user terminal has detected a predetermined ultrasonic wave or beacon, information obtained by the user terminal reading a check-in code, or information obtained by the facility terminal reading a check-in code displayed on the user terminal; A first lottery execution unit executes a first lottery regarding the prize when either a check-in by the aforementioned person or payment by the aforementioned person is performed, An execution result notification unit that notifies the user of the result of the first lottery after one of the above has been performed and before the other of the check-in and payment has been performed, If the other is executed, a second lottery execution unit executes a second lottery regarding the aforementioned benefits, When the user checks in to a facility that is not a member of the check-in service, the reward granting unit grants the reward to the user based on the result of the second lottery, A check-in system that includes this.
16. Computers A check-in step that causes the user to check in to any of the following: a check-in service member facility that is a member of a check-in service different from the payment service, and a check-in service non-member facility that is a member of the payment service but not a member of the check-in service; or a check-in step that causes the user to check in to any of the following: based on user location information regarding the location of the user's user terminal, information indicating that the user terminal has detected a predetermined ultrasonic wave or beacon, information obtained by the user terminal reading a check-in code, or information obtained by the facility terminal reading a check-in code displayed on the user terminal, the user checks in to any of the following: A benefit granting step in which, if the user checks in to a facility that is not affiliated with the check-in service and does not make a payment using the payment service at the facility, the user is not granted the benefit, and if the user checks in to a facility that is not affiliated with the check-in service and makes a payment using the payment service at the facility, the user is granted the benefit. A method for granting benefits to perform this action.
17. A check-in unit that causes a user to check in to any of the following: a check-in service member facility that is a member of a check-in service different from the payment service, or a check-in service non-member facility that is a member of the payment service but not the check-in service; or a check-in unit that causes a user to check in to any of the following: based on user location information relating to the location of the user's user terminal, information indicating that the user terminal has detected a predetermined ultrasonic wave or beacon, information obtained by the user terminal reading a check-in code, or information obtained by the facility terminal reading a check-in code displayed on the user terminal. If the user checks in to a facility that is not affiliated with the check-in service and does not make a payment using the payment service at that facility, the user will not be granted any benefits. However, if the user checks in to a facility that is not affiliated with the check-in service and makes a payment using the payment service at that facility, the user will be granted the benefits. A program that makes a computer function.