Use proposal system, use proposal method, and program

Abstract

To promote the use of a settlement service.SOLUTION: An application information acquisition unit (202) of a use proposal system (2) acquires application information regarding an application made in a reception service which receives an application for a predetermined facility. A use proposal unit (203) proposes the use of a settlement service, based on the application information, to a user who made an application for a target facility through the reception service, in association with a privilege provided that the user makes the application and makes a payment at a target store through the settlement service.SELECTED DRAWING: Figure 10

Description

[Technical Field]

[0001] The present disclosure relates to a usage suggestion system, a usage suggestion method, and a program. [Background technology]

[0002] With the spread of electronic payments (cashless payments), various payment services have become known. For example, Patent Document 1 describes an information processing device that acquires the date and time of a user's stay at an accommodation facility and the location where the user will be staying based on the user's accommodation reservation facility information, and delivers advertisements for stores located near the location where the user will be staying to the user terminal at a time according to the date and time of stay. Such stores can use the payment service. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Publication No. 2020-052976 Summary of the Invention [Problem to be solved by the invention]

[0004] However, with the technology of Patent Document 1, even if advertisements for stores near the accommodation facility booked by the user are delivered to the user's terminal, it may be possible to encourage use of the stores, but it is not possible to encourage use of payment services. This is also true for facilities other than accommodation facilities. For this reason, conventional technology has not been able to sufficiently encourage use of payment services.

[0005] One of the purposes of this disclosure is to promote the use of payment services. [Means for solving the problem]

[0006] The usage suggestion system of the present disclosure includes an application information acquisition unit that acquires application information regarding an application made at a reception service that accepts applications for a specified facility, and a usage suggestion unit that, based on the application information, suggests to a user who has made an application for a target facility at the reception service that they use the payment service, associating the application with a benefit that will be granted if the user makes a payment to a target store using the payment service. [Effects of the Invention]

[0007] The present disclosure can promote the use of payment services. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram illustrating an example of a hardware configuration of a privilege granting system. [Figure 2] FIG. 10 is a diagram illustrating an example of a screen displayed by a reception application. [Figure 3] FIG. 10 is a diagram illustrating an example of a screen displayed on a payment application. [Figure 4] FIG. 2 is a diagram illustrating an example of functions realized by the privilege granting system of the first embodiment. [Figure 5] FIG. 10 is a diagram illustrating an example of a payment database. [Figure 6] FIG. 10 is a diagram illustrating an example of a benefit database. [Figure 7] FIG. 10 is a diagram illustrating an example of a reception database. [Figure 8] FIG. 2 is a diagram illustrating an example of a process executed in the privilege granting system of the first embodiment. [Figure 9] FIG. 10 is a diagram showing an example of an email from a reception service. [Figure 10] FIG. 10 is a diagram illustrating an example of functions realized by the usage suggestion system according to the second embodiment. [Figure 11] FIG. 10 is a diagram illustrating an example of processing executed in the usage suggestion system according to the second embodiment. [Figure 12] FIG. 10 is a diagram illustrating an example of functions realized in a modified example of the first embodiment. [Figure 13] FIG. 10 is a diagram showing an example of an administrative district advertisement. [Figure 14] FIG. 10 is a diagram showing an example of a benefit presented to a user in a payment service. [Figure 15] FIG. 10 is a diagram showing an example of a benefit presented to a user in a reception service. [Figure 16] FIG. 10 is a diagram showing an example of a questionnaire presented to a user. [Figure 17] FIG. 10 is a diagram showing an example of a facility advertisement. [Figure 18] FIG. 10 is a diagram illustrating an example of an entry screen. [Figure 19] FIG. 10 is a diagram illustrating an example of functions realized in a modified example of the second embodiment. [Figure 20] FIG. 10 is a diagram showing an example of a screen on which the reception service proposes the use of a payment service. DETAILED DESCRIPTION OF THE INVENTION

[0009] [1. First embodiment] A first embodiment, which is an example of an embodiment of a reward granting system, a reward granting method, and a program according to the present disclosure, will be described.

[0010] [1-1. Hardware configuration of the reward system] Fig. 1 is a diagram showing an example of the hardware configuration of a reward system. For example, the reward system 1 includes a payment server 10, a reception server 20, and a user terminal 30. Each of the payment server 10, the reception server 20, and the user terminal 30 is connected to a network N such as the Internet or a LAN. Although Fig. 1 shows one each of the payment server 10, the reception server 20, and the user terminal 30, there may be multiple of at least one of the payment server 10, the reception server 20, and the user terminal 30.

[0011] The payment server 10 is a server computer for a payment service. A payment service is a service that provides users with electronic payments (cashless payments). Any type of payment means may be available to users for the payment service. A payment means is a means used by a user for payment. For example, a payment means may be a credit card, electronic money (including what is called a balance), points, cryptocurrency, a debit card, a wallet, an account such as a bank account, or other means. Codes such as barcodes or two-dimensional codes are also means for payment and therefore correspond to a payment means. A payment means can also be called a payment instrument.

[0012] For example, the payment server 10 includes a control unit 11, a storage unit 12, and a communication unit 13. The control unit 11 includes at least one processor. The storage unit 12 includes at least one of a volatile memory such as a RAM and a non-volatile memory such as a flash memory. The communication unit 13 includes at least one of a communication interface for wired communication and a communication interface for wireless communication.

[0013] The reception server 20 is a server computer for the reception service. The reception service is a service that accepts applications related to a specified facility. The operator that operates the reception service and the operator that operates the payment service may be the same or different. If these operators are different, they are considered to be in a cooperative relationship. The facility for which applications are accepted by the reception service may be any facility. For example, the facility may be an accommodation facility such as a hotel or inn, a sports facility such as a golf course or baseball field, an event venue such as a concert venue or convention center, a tourist facility, a public facility, an amusement facility such as an amusement park or game center, a shopping mall, a store such as a restaurant or beauty salon, a complex of these, or another facility.

[0014] An application is an application for a user to use a facility or an application for a user to enter a facility (for example, an application for a user to participate in an event held at the facility). For example, a reservation application for a user to use the facility itself (for example, an application to reserve an accommodation facility or an application to reserve a golf course), an application to purchase a ticket for a user to enter a facility (for example, a ticket for a sports game, a ticket for a concert, or a ticket for a play), or an application for a user to enter a facility without a ticket corresponds to an application accepted by the reception service.

[0015] In the first embodiment, an example is given in which an accommodation facility corresponds to the facility. Furthermore, an example is given in which the reception service accepts reservation applications for accommodation facilities. The reception service may also accept reservation applications for travel products such as tours in addition to accommodation facilities. For example, the reception server 20 includes a control unit 21, a memory unit 22, and a communication unit 23. The hardware configurations of the control unit 21, the memory unit 22, and the communication unit 23 may be similar to those of the control unit 11, the memory unit 12, and the communication unit 13, respectively.

[0016] The user terminal 30 is a user's computer. For example, the user terminal 30 is a smartphone, a tablet, a personal computer, or a wearable terminal. The user terminal 30 includes a control unit 31, a memory unit 32, a communication unit 33, an operation unit 34, and a display unit 35. The hardware configurations of the control unit 31, the memory unit 32, and the communication unit 33 may be similar to those of the control unit 11, the memory unit 12, and the communication unit 13, respectively. The operation unit 34 is an input device such as a touch panel or a mouse. The display unit 35 is a display such as a liquid crystal or organic EL display.

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

[0018] Furthermore, the reward granting system 1 may include at least one computer. The computers included in the reward granting system 1 are not limited to the example of FIG. 1. For example, the reward granting system 1 may include only the payment server 10 and the reception server 20. In this case, the user terminal 30 exists outside the reward granting system 1. The reward granting system 1 may include only the payment server 10. In this case, the reception server 20 and the user terminal 30 exist outside the reward granting system 1. For example, the reward granting system 1 may include the payment server 10 and other computers not shown in FIG. 1.

[0019] [1-2. Overview of the First Embodiment] In the first embodiment, a user operates user terminal 30 to use each of the payment service and the reception service. For example, a payment app, which is an application for the payment service, and a reception app, which is an application for the reception service, are installed on user terminal 30. The user uses the payment service from the payment app. The user uses the reception service from the reception app. The user may use at least one of the payment service and the reception service from a browser on user terminal 30.

[0020] Fig. 2 is a diagram showing an example of a screen displayed by the reception app. As shown on the left side of Fig. 2, when a user operates the user terminal 30 to launch the reception app, the user terminal 30 communicates with the reception server 20 and displays a top screen SC1 of the reception app on the display unit 35. The user inputs search conditions for searching for facilities from the top screen SC1. For example, the user inputs at least one of the accommodation location, check-in date, check-out date, number of rooms, and number of people as search conditions.

[0021] For example, the user selects a desired facility from among the facilities that match the search criteria and applies for it. When the user finds the desired facility, the user enters the necessary information to complete the application. Once the application is complete, the user terminal 30 displays a completion screen SC2 indicating that the application has been completed on the display unit 35, as shown on the right side of FIG. 2. The application flow in the reception service may be similar to that of known reception services.

[0022] In the first embodiment, an example is given in which the reception service and the payment service cooperate with each other and a local government campaign in a certain administrative district is held. For example, if a user makes an application for a target facility in the administrative district through the reception service and uses the payment service at a target store in the administrative district, the user will be granted a campaign benefit. A target facility is a facility that meets the conditions for the benefit to be granted. For example, a target facility is a facility that is the target of a campaign. A target store is a store that meets the conditions for the benefit to be granted. For example, a target store is a store that is the target of a campaign.

[0023] In the example on the right side of Figure 2, a campaign is being held in DDD City, an example of a local government. For example, if a user applies for a participating facility in DDD City through the reception service and then uses the payment service at a participating store in DDD City, the user will receive a benefit of an increased point return rate. All facilities in DDD City may be participating facilities, or only some of the facilities in DDD City may be participating facilities. Similarly, all stores in DDD City may be participating stores, or only some of the stores in DDD City may be participating stores. For example, when a user visits DDD City to use the participating facility for which they have applied, they make a payment to the participating store in DDD City using the payment app.

[0024] FIG. 3 is a diagram showing an example of a screen displayed by the payment app. As shown on the left side of FIG. 3, when a user operates the user terminal 30 to launch the payment app, the user terminal 30 communicates with the payment server 10 and displays the payment app's top screen SC3 on the display unit 35. For example, the top screen SC3 displays a code C30 generated based on a code ID that can temporarily identify the user in the payment service. The code C30 is at least one of a barcode and a two-dimensional code. When the code C30 is read by a terminal at the target store, payment is executed based on the code ID obtained from the code C30. Payments to stores other than the target store are also executed in a similar manner.

[0025] The payment methods available to users in the payment service are not limited to having the terminal of the target store read the code C30. The payment method may be any method adopted by known payment services. For example, the payment method may be a type in which the user terminal 30 reads a code displayed on a terminal of the target store, a type in which the user terminal 30 reads a code posted in the target store, a type in which the user terminal 30 reads a code displayed on a terminal of the target store, a type in which the payment is completed by operating the user terminal 30 alone, a type in which an IC chip in the user terminal 30 is used, online payment (e.g., account payment using the user's account or ID payment using the user's ID), carrier payment by the carrier used by the user terminal 30, or any other type. Similarly, the payment method for payments to stores other than the target store may be any method.

[0026] For example, when a user makes a payment to a target store using the payment service, the user terminal 30 displays a completion screen SC4 on the display unit 35, indicating that the payment has been completed, as shown on the right side of FIG. 3. In the example on the right side of FIG. 3, the user is granted a benefit in the form of a doubled return rate on points awarded for the payment. If the user applies for admission to a facility other than the target facility, the user will not be granted a benefit even if they use the payment service at the target store. If the user applies for admission to a target facility using a method other than the reception service, or if they use the payment service at the target store, the user will not be granted a benefit. If the user is not granted a benefit, the user will earn points at the normal return rate.

[0027] As described above, the reward system 1 rewards a user who applies for admission to a target facility using the reception service and makes a payment to the target store using the payment service with a reward that increases the point redemption rate. This allows the reward system 1 to motivate the user to use the target store, thereby promoting use of the target store. The reward system 1 will be described in detail below.

[0028] [1-3. Functions realized by the reward granting system of the first embodiment] FIG. 4 is a diagram showing an example of functions realized by the privilege granting system 1 of the first embodiment.

[0029] [1-3-1. Functions realized by the payment server] For example, the payment server 10 includes a data storage unit 100, an application information acquisition unit 101, a payment information acquisition unit 102, and a reward granting unit 103. The data storage unit 100 is realized by the memory unit 12. Each of the application information acquisition unit 101, the payment information acquisition unit 102, and the reward granting unit 103 is realized by the control unit 11.

[0030] [Data storage section] The data storage unit 100 stores various data related to the payment service. For example, the data storage unit 100 stores a payment database DB1 and a benefit database DB2.

[0031] Figure 5 is a diagram showing an example of payment database DB1. Payment database DB1 is a database that stores various information related to users who use the payment service. For example, payment database DB1 stores user IDs, passwords, code IDs, payment source information, and payment information. Payment database DB1 may also store other information. For example, payment database DB1 may store information on payment methods that users have registered with the payment service.

[0032] The user ID is an example of user identification information that can identify a user. A login account may exist in addition to the user ID. The login account may be freely changeable by the user. The login account is also an example of user identification information. A password is information that is confirmed when logging in. The code ID is also an example of user identification information, as it is an ID that can identify a user in the payment service. The code ID is updated each time the code C30 is displayed. The user identification information may be information other than the user ID, login account, and code ID.

[0033] Payment source information is information about the source of payment. A payment source is a payment method that serves as the source of funds for payment. For example, payment source information may be credit card information (e.g., credit card number, expiration date, and cardholder), electronic money information (e.g., electronic money ID and balance), account information such as a bank account (e.g., financial institution code, branch code, and account number), or some of these. If only one payment method is available as a payment source, payment source information may be information about that payment method.

[0034] Payment information is information about payments made with a payment service. Payment information can also be referred to as information about a user's usage history of the payment service. For example, payment information indicates the payment destination, payment amount, and payment date and time. The payment destination is the store that was the subject of the payment. For example, the payment destination is store identification information such as a store ID or store name that can identify the store. The payment amount is the amount of payment to the store. The payment amount can also be referred to as the payment amount. The payment date and time is the date and time when the payment was made. Payment information may include other information. For example, payment information may indicate points earned by the user. Payment information may indicate the product or service that was the subject of the payment. The format of the payment information may be similar to formats used in known payment services.

[0035] For example, when code C30 is read by a store terminal, the store terminal sends a payment request including the code ID obtained from code C30 to the payment server 10. The payment request also includes other information necessary for payment, such as store identification information and payment amount. When the payment server 10 receives the payment request from the store terminal, it determines whether the code ID included in the payment request is stored in the payment database DB1. If the code ID is stored in the payment database DB1, the payment server 10 executes the payment based on the payment source information associated with the code ID.

[0036] For example, the payment server 10 generates payment information based on the result of the payment execution. The payment server 10 stores the payment information in the same record in the payment database DB1 as the record in which the code ID included in the payment request is stored. The payment server 10 may store the payment information in a database other than the payment database DB1. The payment server 10 may record the payment information in a computer other than the payment server 10 or in an external information storage medium. The payment information may include a user ID indicating which user made the payment. The user ID may not be included in the payment information, but may be associated with the payment information as separate data from the payment information.

[0037] 6 is a diagram showing an example of the benefit database DB2. The benefit database DB2 is a database that stores various information related to benefits. For example, the benefit database DB2 stores a campaign ID, basic information about the campaign, target facility ID, target store ID, and benefit information. The benefit database DB2 may also store other information. For example, the benefit database DB2 may store the user ID of a user to whom a benefit has been granted.

[0038] The campaign ID is campaign identification information that can identify a campaign. The campaign identification information may be information other than the campaign ID (for example, the name of the campaign or the name of the local government hosting the campaign). The campaign basic information is basic information about the campaign. For example, the campaign basic information may indicate the name of the campaign, the name of the local government hosting the campaign, the campaign period, or the maximum amount of benefits that can be granted in the campaign.

[0039] The target facility ID is the facility ID of the target facility. The facility ID is an example of facility identification information that can identify a facility. The facility identification information may be information other than the facility ID (e.g., the name, telephone number, email address, or address of the facility). At least one target facility ID is associated with one campaign ID. For example, when a local government in a certain administrative district holds a campaign, the facility ID of at least one facility in that administrative district is stored in the benefit database DB2 as a target facility ID.

[0040] The target store ID is the store ID of the target store. The store ID is an example of store identification information that can identify a store. The store identification information may be information other than the store ID (for example, the store's name, telephone number, email address, or address). At least one store ID is associated with one campaign ID. For example, when a local government in a certain administrative district holds a campaign, the store ID of at least one store in that administrative district is stored as a store ID in the benefit database DB2. If the target facility is a member of a payment service, the target facility may also be a target store. In this embodiment, an example is given in which the target facility and the target store are different.

[0041] The benefit information is information related to the benefit. For example, the benefit information may indicate the specific content of the benefit, the conditions for granting the benefit, or the maximum amount of benefit that can be granted to one user. For example, when a new campaign is held, the administrator of the payment service operates his / her own terminal to register information about the new campaign in the payment server 10. The payment server 10 issues a new campaign ID and creates a new record in the benefit database DB2. Based on the information entered by the administrator, the payment server 10 stores basic information about the campaign, the target facility ID, the target store ID, and benefit information in the new record. This information may be entered by the administrator or by another party (for example, the local government holding the campaign).

[0042] The data stored in the data storage unit 100 is not limited to the above examples. The data storage unit 100 may store data related to the payment service. For example, the data storage unit 100 may store a store database that stores various information related to stores affiliated with the payment service. The store database may store basic information such as a store ID, the name and address of the store, payment information for payments to the store, or other information. The data storage unit 100 may store data for various screens displayed on the payment app. For example, the data storage unit 100 may store data for the payment service and the reception service to cooperate with each other.

[0043] [Application Information Acquisition Section] The application information acquisition unit 101 acquires application information related to applications made at a reception service that accepts applications for a predetermined facility. The application information acquisition unit 101 may acquire application information each time application information is generated, or may acquire all application information generated during a certain period at once. For example, if the processing of the benefit granting unit 103 is executed at a predetermined date and time by a batch file or the like, the application information acquisition unit 101 may acquire all application information generated during the processing period (for example, the period from the last time the processing of the benefit granting unit 103 was executed to the present time) at once.

[0044] For example, the application information acquisition unit 101 may record the acquired application information in the data storage unit 100. The data storage unit 100 may store a database similar to the reception database DB3, or may store a database similar to the portion of the reception database DB3 that contains user IDs and application information. The payment server 10 may acquire application information from the reception server 20 as appropriate and ensure consistency of the databases.

[0045] In the first embodiment, the application information is stored in the reception database DB3 of the reception server 20, and therefore the application information acquisition unit 101 acquires the application information from the reception database DB3 of the reception server 20. If the application information is stored in a database other than the reception database DB3 of the reception server 20, the application information acquisition unit 101 may acquire the application information from the other database. If the application information is stored in a computer other than the reception server 20 or in an external information storage medium, the application information acquisition unit 101 may acquire the application information from the other computer or external information storage medium.

[0046] [Payment Information Acquisition Department] The payment information acquisition unit 102 acquires payment information related to payments made in a payment service. The payment information acquisition unit 102 may acquire payment information each time payment information is generated, or may acquire all of the payment information generated over a certain period at once. For example, if the processing of the reward granting unit 103 is executed at a predetermined date and time using a batch file or the like, the payment information acquisition unit 102 may acquire all of the payment information generated over the processing period (e.g., the period from the last time the processing of the reward granting unit 103 was executed to the present time) at once.

[0047] In the first embodiment, the payment information is stored in the payment database DB1 of the payment server 10, and therefore the payment information acquisition unit 102 acquires the payment information from the payment database DB1 of the payment server 10. If the payment information is stored in a database other than the payment database DB1 of the payment server 10, the payment information acquisition unit 102 may acquire the payment information from the other database. If the payment information is stored in a computer other than the payment server 10 or an external information storage medium, the payment information acquisition unit 102 may acquire the payment information from the other computer or external information storage medium.

[0048] [Benefits Granting Department] The benefit granting unit 103 grants a benefit to a user who has made an application for a target facility using the reception service and made a payment to the target store using the payment service, based on the application information and the payment information. In the first embodiment, an example is given in which the target facility and the target store are located in the same administrative district, so the benefit granting unit 103 grants a benefit to a user who has made an application for a target facility using the reception service and made a payment to the target store in the administrative district where the target facility is located using the payment service.

[0049] A reward is a benefit to a user. The reward may be any reward adopted in a known service, such as a payment service. For example, the reward may be an increase in the point redemption rate, the awarding of a predetermined amount of points, the return of electronic money according to the payment amount, a coupon, a product, a service, or other reward. The method of awarding the reward may also be a method adopted in a known service. The process by which the reward awarding unit 103 determines whether to award a reward to a user or the process by which the reward awarding unit 103 identifies a user to whom a reward is to be awarded is a novel configuration, but the awarding of the reward itself may be realized by a process adopted in a known service.

[0050] For example, the reward granting unit 103 may grant a reward by calculating points to be returned to the user (for example, the amount of points obtained by multiplying the payment amount by the reward rate) based on a higher reward rate than when no reward is granted, and granting the points to the user. Granting points means increasing the balance of points. The reward granting unit 103 may grant a reward by calculating the amount of electronic money to be returned to the user, and granting the electronic money to the user. Returning electronic money means increasing the balance of electronic money.

[0051] Note that even when a coupon, a product, or a service corresponds to the benefit, the benefit granting unit 103 may grant the benefit to the user by a known process for granting the coupon, product, or service to the user. For example, the benefit granting unit 103 grants the benefit to the user by transmitting coupon data to the user terminal 30. The benefit granting unit 103 grants the benefit to the user by transmitting voucher data for the product or service to the user terminal 30. Similarly, when other benefits are granted, the granting of the benefit itself may be realized by a known process.

[0052] For example, the reward granting unit 103 may execute a process of granting a reward each time a user makes a payment. In this case, when a user makes a payment, the application information acquiring unit 101 acquires application information indicating an application made by the user. When a user makes a payment, the payment information acquiring unit 102 acquires payment information indicating a payment made by the user. The user's application and payment may be identified by a user ID included in the application information and payment information, or a user ID associated with the application information and payment information.

[0053] For example, the reward granting unit 103 determines whether the user has applied for the target facility using the reception service based on the facility ID indicated in the application information of the user who made the payment and the target facility ID stored in the reward database DB2. If these IDs match, the reward granting unit 103 determines that the user has applied for the target facility using the reception service. If these IDs match, the reward granting unit 103 determines whether the user has made a payment to the target store using the payment service based on the store ID indicated in the payment information of the user who made the payment and the target store ID stored in the reward database DB2. If these IDs match, the reward granting unit 103 determines that the user has made a payment to the target store using the payment service.

[0054] For example, the reward granting unit 103 grants a reward to a user when it is determined that the user has applied for a facility using the reception service and made a payment to the store using the payment service. That is, the reward granting unit 103 grants a reward to a user on the two conditions that the user has applied for a facility using the reception service and that the user has made a payment to the store using the payment service. The reward granting unit 103 does not grant a reward to a user when it is determined that the user has not applied for a facility using the reception service or when it is determined that the user has not made a payment to the store using the payment service. That is, the reward granting unit 103 does not grant a reward to a user when at least one of the above two conditions is not met.

[0055] The reward granting unit 103 may determine whether or not the user has applied for the target facility through the reception service before the user executes payment. In this case, the reward granting unit 103 may store application presence / absence information indicating the determination result of whether or not the user has applied for the target facility through the reception service in the payment database DB1 or another database in association with the user ID of the user. The application presence / absence information can also be said to be information indicating whether or not the user is a target to whom a reward can be granted. The application presence / absence information can also be said to be information indicating whether or not the user is a target for a campaign.

[0056] For example, when a user makes a payment, the reward granting unit 103 may grant a reward to the user based on the application presence / absence information and the payment information acquired in the prior determination. The reward granting unit 103 does not grant a reward to a user whose application presence / absence information indicates that he or she has not applied for the target facility through the reception service. When a user whose application presence / absence information indicates that he or she has applied for the target facility through the reception service makes a payment, the reward granting unit 103 determines, based on the payment information, whether the user has made a payment to the target store using the payment service. When it is determined that the user has made a payment to the target store using the payment service, the reward granting unit 103 grants a reward to the user. When it is determined that the user has not made a payment to the target store using the payment service, the reward granting unit 103 does not grant a reward to the user.

[0057] Furthermore, the reward granting unit 103 may execute a process of granting a reward not when a user makes a payment, but at any timing thereafter. For example, the reward granting unit 103 may execute a process of granting a reward to multiple users when a certain time arrives using a batch file. In this case, the reward granting unit 103 identifies multiple users who have made payments during a period to be processed by the batch file (for example, the period from the last time the batch file was executed to the present), based on the payment date and time indicated by the payment information stored in the payment database DB1.

[0058] For example, the reward granting unit 103 determines, for each user who made a payment during the processing period, whether the user made an application for the target facility using the reception service and made a payment to the target store using the payment service, based on the user's application information and payment information.These determination methods may be the same as those used when a reward is granted each time a user makes a payment.The reward granting unit 103 grants a reward to a user who, among multiple users who made a payment during the processing period, made an application for the target facility using the reception service and made a payment to the target store using the payment service.

[0059] Note that even when the reward granting unit 103 executes the process of granting a reward after a user has made a payment, the reward granting unit 103 may determine in advance whether or not the user has applied for the target facility through the reception service. In this case, it is assumed that the application presence / absence information described above has been acquired in advance. The reward granting unit 103 may determine, for each user who has made a payment during the processing period using a batch file or the like, based on the application presence / absence information and payment information of the user, whether or not the user has applied for the target facility through the reception service and made a payment to the target store through the payment service.

[0060] Furthermore, the reward granting unit 103 may execute the process of granting a reward to each of a plurality of users all at once at another timing other than the execution timing of a batch file, etc. For example, the reward granting unit 103 may execute the process of granting a reward to each of a plurality of users all at once at the timing when a campaign ends, at a predetermined timing after the campaign ends, at a timing instructed by an administrator of the payment service, at a timing instructed by a person in charge of the local government hosting the campaign, or at another timing.

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

[0062] [Data storage section] The data storage unit 200 stores various data for the reception service. For example, the data storage unit 200 stores a reception database DB3.

[0063] 7 is a diagram showing an example of the reception database DB3. The reception database DB3 is a database that stores various information related to users who use the reception service. For example, the reception database DB3 stores user IDs, passwords, and application information. The reception database DB3 may also store other information. For example, the reception database DB3 may store information indicating the user's email address, phone number, SNS account, messaging app account, or user application history.

[0064] The user ID and password differ from the user ID and password of the payment service in that they are information for the user to log in to the reception service, but are otherwise similar. In the first embodiment, a case will be described in which a common user ID and password are used for the payment service and the reception service, but at least one of the user ID and password may be different for the payment service and the reception service.

[0065] In addition, when the user IDs for the payment service and the reception service are different, it is assumed that the relationship between a user's user ID for the payment service and the user ID for the reception service is predefined. A relational database indicating this relationship may be stored in the payment server 10 or the reception server 20. At least one of the payment server 10 and the reception server 20 may identify which user ID belongs to which user based on the relational database.

[0066] The application information is information relating to an application made through a reception service. For example, the application information indicates the facility ID of the facility to which the application is made, the application content, and the application date and time. The application content is information on the items required for the application. When a reservation application for an accommodation facility is made as in the first embodiment, the application content includes the check-in date, check-out date, number of rooms, and number of people. The application content may be other content. The application information may include other information. The format of the application information may be similar to the format adopted by known reception services.

[0067] For example, if the reception service accepts a reservation application for a facility such as a golf course, the application information may indicate the date or time of use of the facility, the plan specified by the user, and the number of users. If the reception service accepts an application to purchase tickets for an event such as a concert, the application information may indicate the date or time of the event to be held at the facility, information such as the name of the facility, the type of seat purchased by the user, and the number of users. Similarly, for other reception services, the application information may be information that indicates the content of the user's application.

[0068] The data stored in the data storage unit 200 is not limited to the above examples. The data storage unit 200 may store data related to the reception service. For example, the data storage unit 200 may store a facility database that stores facility information related to facilities for which applications can be made through the reception service. The facility database may store basic information such as a facility ID, the name and address of the facility, a history of applications to the facility, or other information. The data storage unit 200 may store data for various screens displayed on the reception app. For example, the data storage unit 200 may store data for the payment service and the reception service to link with each other.

[0069] [Reception] The reception unit 201 receives applications from users. For example, when a user performs an operation to apply on the user terminal 30, the user terminal 30 transmits an application request including the facility ID of the facility selected by the user to the reception server 20. The application request also includes other information such as the content of the application. When the reception unit 201 receives the application request from the user terminal 30, it completes the application based on the application request. For example, the reception unit 201 generates application information based on the application request. The reception unit 201 stores the application information in the same record in the reception database DB3 as the record in which the user ID of the user who made the application request is stored. The reception unit 201 may store the application information in a database other than the reception database DB3. The reception unit 201 may record the application information in a computer other than the reception server 20 or in an external information storage medium. The application information may include a user ID indicating which user has made the application.

[0070] [1-3-3. Functions implemented on user devices] For example, the user terminal 30 includes a data storage unit 300, an operation reception unit 301, and a display control unit 302. The data storage unit 300 is realized by the storage unit 32. The operation reception unit 301 and the display control unit 302 are realized by the control unit 31.

[0071] [Data storage section] The data storage unit 300 stores data necessary for the user to use each of the payment service and the reception service. For example, the data storage unit 300 stores a payment application, a reception application, and a browser.

[0072] [Operation reception section] The operation acceptance unit 301 accepts various operations from the user. For example, the operation acceptance unit 301 accepts operations on the payment app. The operation acceptance unit 301 transmits data indicating the user's operation content to the payment server 10. The operation acceptance unit 301 accepts operations on the acceptance app. The operation acceptance unit 301 transmits data indicating the user's operation content to the acceptance server 20.

[0073] [Display control section] The display control unit 302 displays various screens on the display unit 35. For example, the display control unit 302 displays each of a top screen SC1, a completion screen SC2, a top screen SC3, and a completion screen SC4 on the display unit 35. The display control unit 302 communicates with the payment server 10, the reception server 20, or another computer, receives data necessary to display these screens, and displays these screens on the display unit 35.

[0074] [1-4. Processing Executed in the Benefit Granting System of the First Embodiment] Fig. 8 is a diagram showing an example of processing executed in the reward granting system 1 of the first embodiment. The processing of Fig. 8 is executed by the control units 11, 21, and 31 executing programs stored in the storage units 12, 22, and 32, respectively. Fig. 8 shows an example of a case where processing for granting a reward is executed each time a user makes a payment.

[0075] 8, when the user selects the reception app, the user terminal 30 communicates with the reception server 20 and executes processing to display a top screen SC1 of the reception service (S100). The user terminal 30 executes processing to accept an application for a facility by the user with the reception server 20 (S101). In S101, when the application is completed, the user terminal 30 displays a completion screen SC2 on the display unit 35. Payment to the facility may be completed at the time of application, or may be completed when the user actually visits the facility.

[0076] When the user selects the payment app, the user terminal 30 communicates with the payment server 10 and executes processing to display the payment service top screen SC3 (S102). When the payment server 10 receives a payment request from the store terminal, it executes the payment (S103). When the payment server 10 executes the payment, it generates payment information and stores the payment information in the payment database DB1 in association with the user ID of the user who executed the payment. The payment server 10 executes processing to acquire application information of the user who executed the payment with the reception server 20 (S104). In S104, the payment server 10 requests the reception server 20 to acquire application information associated with the user ID of the user who executed the payment. The reception server 20 acquires the application information associated with the user ID from the reception database DB3 and transmits it to the payment server 10. The payment server 10 receives the application information from the reception server 20.

[0077] The payment server 10 acquires payment information based on the execution result of the payment in S103 (S105). In S105, the payment server 10 acquires the payment information of the payment executed in S105 from the payment database DB1. The payment server 10 may use the payment information acquired by the processing of S105 in the processing from S106 onwards before storing the payment information in the payment database DB1. The payment server 10 determines whether to grant a benefit to the user based on the benefit database DB2, the application information acquired in S104, and the payment information acquired in S105 (S106). In S106, the payment server 10 determines whether to grant a benefit to the user by determining whether the user has applied for a facility of interest using the reception service and has made a payment to the store of interest using the payment service.

[0078] If it is determined in S106 that a benefit is to be granted to the user (S106: Y), that is, if it is determined that the user has applied for admission to the target facility using the reception service and made payment to the target store using the payment service, the payment server 10 executes processing to grant the benefit to the user (S107), and this processing ends. If the benefit is to be granted immediately when payment is executed, the payment server 10 executes processing to display a completion screen SC4 between the user terminal 30. The completion screen SC4 notifies the user that the benefit has been granted, and the user's points may be increased immediately.

[0079] In S106, if it is determined that the user is not to be granted a benefit (S106: N), that is, if it is determined that the user did not apply for a facility using the reception service, or if it is determined that the user did not make a payment to the store using the payment service, the process of S107 is not executed, and this process ends. In this case, a completion screen SC4 indicating that the payment was made without granting a benefit is displayed on the user terminal 30. Note that, after a certain amount of time has passed since the payment was made, the process for acquiring application information, the process for acquiring payment information, and the process for granting a benefit may be executed.

[0080] [1-5. Summary of the first embodiment] The reward granting system 1 of the first embodiment grants a reward to a user who applies for a target facility using the reception service and makes a payment to the target store using the payment service, based on application information and payment information. A user who applies for a target facility using the reception service is attracted to the reward that is granted when the user makes a payment to the target store using the payment service. Therefore, the reward granting system 1 can motivate the user to use the target store and promote use of the target store. Since a user must also apply for a target facility using the reception service in order to receive a reward, the reward granting system 1 can motivate the user to apply for the target facility and promote application to the target facility. Since a user does not receive a reward if the user applies for a target facility using a means other than the reception service, the reward granting system 1 can motivate the user to use the reception service and promote use of the reception service. Since a user does not receive a reward if the user makes a payment to the target store using a means other than the payment service, the reward granting system 1 can motivate the user to use the payment service and promote use of the payment service.

[0081] Furthermore, the reward granting system 1 grants rewards to users who use the reception service to apply for a target facility and then use the payment service to pay for a target store in the administrative district where the target facility is located. This allows the reward granting system 1 to promote use of target stores in a specific administrative district. The reward granting system can also promote applications for target facilities in a specific administrative district. As a result, the operator of the payment service, the operator of the reception service, and the local government cooperate with each other, and the reward granting system 1 is realized, thereby revitalizing the economy of a specific administrative district.

[0082] [2. Second Embodiment] A second embodiment will be described, which is an example of an embodiment of a usage suggestion system, a usage suggestion method, and a program according to the present disclosure. In the second embodiment, an example will be given in which the reward granting system 1 described in the first embodiment corresponds to the usage suggestion system. However, in the second embodiment, for convenience of explanation, the reward granting system 1 described in the first embodiment will be referred to as a usage suggestion system 2. Of the configuration of the usage suggestion system 2 of the second embodiment, a description of the configuration similar to that of the reward granting system 1 of the first embodiment will be omitted.

[0083] Note that at least a portion of the description of the reward granting system 1 in the first embodiment can be read as the usage suggestion system 2 in the second embodiment. For example, the hardware configuration of the usage suggestion system 2 may be the same as that of the reward granting system 1 in the first embodiment. The usage suggestion system 2 in the second embodiment may include only the reception server 20. In this case, the payment server 10 and the user terminal 30 exist outside the usage suggestion system 2. For example, the usage suggestion system 2 may include the reception server 20 and another computer not shown in FIG. 1.

[0084] [2-1. Overview of the Second Embodiment] In the second embodiment, an example is taken of a case where a user uses the reception service but does not use the payment service. For example, the user is a member of the reception service but not a member of the payment service. The user applies for a facility of interest through the reception service in the same manner as in the first embodiment. The user receives a confirmation email from the reception service a predetermined time before the check-in date of the facility of interest. The user checks the application details contained in the email.

[0085] Figure 9 shows an example of an email from the reception service. As shown on the left side of Figure 9, email M includes basic information such as the facility name and address of the facility to which the user has applied, as well as the application details entered by the user when applying. For example, if the user is not using a payment service, email M includes details of the benefits that will be granted when the user makes a payment at a target store using the payment service, and a link L for the user to download the payment app. In other words, email M includes a path to the payment service.

[0086] For example, when a user selects link L in email M, user terminal 30 accesses a computer that distributes the payment app (e.g., payment server 10 or another computer) and displays a payment app download screen SC5 on display 35. The user downloads the payment app from the download screen SC5. Once installation of the payment app is complete, user terminal 30 communicates with payment server 10 and executes a process for membership registration for the payment service in the same manner as known payment services. The process after the user becomes a member of the payment service may be the same as in the first embodiment.

[0087] If the user is already a member of the payment service, the link L does not have to be included in the email M. In this case, details of the benefits and the campaign may be notified in the email M. If a user who is not a member of the payment service applies for a facility other than the target facility, the link L does not have to be included in the email M. In this case, details of the benefits and the campaign may be notified in the email M.

[0088] As described above, in the second embodiment, when a user who is not a member of the payment service applies for a facility of interest through the reception service, the usage suggestion system 2 sends the user an email M including details of the benefit and a link L. This allows the usage suggestion system 2 to motivate users who are not members of the payment service to become members of the payment service, thereby promoting the use of the payment service. Details of the second embodiment will be described below.

[0089] [2-2. Functions realized by the usage suggestion system of the second embodiment] FIG. 10 is a diagram showing an example of functions realized by the usage suggestion system 2 of the second embodiment.

[0090] Note that the use suggestion system 2 of the second embodiment may not include at least some of the functions of the reward granting system 1 described in the first embodiment. For example, in the example of Fig. 10, the payment server 10 of the use suggestion system 2 includes an application information acquisition unit 101, a payment information acquisition unit 102, and a reward granting unit 103 for a user who has become a member of the payment service. However, the use suggestion system 2 may not include the payment server 10, and therefore may not include the application information acquisition unit 101, the payment information acquisition unit 102, and the reward granting unit 103. In this case, the application information acquisition unit 101, the payment information acquisition unit 102, and the reward granting unit 103 are realized by the payment server 10 located outside the use suggestion system 2. It is a matter that a person skilled in the art can naturally understand from the description of this disclosure that both aspects of the usage suggestion system 2 are described in this disclosure: one in which the usage suggestion system 2 does not include the application information acquisition unit 101, the payment information acquisition unit 102, and the benefit granting unit 103; and one in which the usage suggestion system 2 includes the application information acquisition unit 101, the payment information acquisition unit 102, and the benefit granting unit 103.

[0091] [2-2-1. Functions realized by the payment server] For example, the functions realized by the payment server 10 may be the same as those in the first embodiment.

[0092] [2-2-2. Functions realized by the reception server] For example, the reception server 20 includes a data storage unit 200 , a reception unit 201 , an application information acquisition unit 202 , and a usage suggestion unit 203 .

[0093] [Data storage section] The data storage unit 200 may be the same as in the first embodiment. In the second embodiment, the data storage unit 200 stores a database similar to the benefit database DB2. The reception server 20 may communicate with the payment server 10, appropriately acquire the contents of the benefit database DB2, and ensure consistency with the benefit database DB2. The data storage unit 200 may store a database that shows only the target facility ID portion and the benefit information portion of the benefit database DB2.

[0094] [Reception] The reception unit 201 may be the same as in the first embodiment. Note that the use suggestion system 2 does not need to include the reception unit 201. If the use suggestion system 2 does not include the reception unit 201, the use suggestion system 2 may acquire application information of an application received in an external system from the external system.

[0095] [Application Information Acquisition Section] The application information acquisition unit 202 acquires application information related to applications made at a reception service that accepts applications for a specified facility. The application information acquisition unit 202 may acquire application information each time application information is generated, or may acquire all application information generated over a certain period at once. For example, if the processing of the usage suggestion unit 203 is executed at a specified date and time by a batch file or the like, the application information acquisition unit 202 may acquire all application information generated over the period that is the target of batch file processing at once.

[0096] In the second embodiment, the application information is stored in the reception database DB3, and therefore the application information acquisition unit 202 acquires the application information from the reception database DB3. If the application information is stored in a database other than the reception database DB3, the application information acquisition unit 202 may acquire the application information from the other database. If the application information is stored in a computer other than the reception server 20 or in an external information storage medium, the application information acquisition unit 202 may acquire the application information from the other computer or external information storage medium.

[0097] [Usage proposal department] The usage suggestion unit 203 suggests to the user who has made an application for a target facility in the reception service, based on the application information, that they use the payment service by associating the application with a benefit that will be granted on condition that they make a payment to the target store in the payment service. In the second embodiment, since the target facility and the target store are in the same administrative district, the usage suggestion unit 203 suggests to the user that they use the payment service by associating the application for the target facility in the reception service with a benefit that will be granted on condition that they make a payment to the target store in the administrative district where the target facility is located.

[0098] As in the first embodiment, the benefit in the second embodiment is granted to the user on two conditions: the user applies for admission to the facility using the reception service, and the user makes a payment to the store using the payment service. Proposing the use of the payment service in association with the benefit means providing information about the benefit and proposing the use of the payment service. In the example of FIG. 9, sending an email M including the benefit details and a link L corresponds to proposing the use of the payment service in association with the benefit.

[0099] The method by which the usage suggestion unit 203 suggests the use of a payment service is not limited to email M. The usage suggestion unit 203 may suggest the use of a payment service in association with a benefit using a means for notifying the user of some information. For example, the usage suggestion unit 203 may suggest the use of a payment service in association with a benefit using a notification function of a reception app, a push notification, a banner notification, a pop-up, an SMS message, a message on an SNS, a message on a messaging app, or other means.

[0100] For example, the use suggestion unit 203 may execute a process of suggesting the use of a payment service when a predetermined time has passed since the user's visit to the facility for which an application has been made (for example, the check-in date). The use suggestion unit 203 determines whether an application for the target facility has been made based on the application information. For example, the use suggestion unit 203 determines whether the facility ID indicated in the application information is the target facility ID. When it is determined that an application for the target facility has been made, the use suggestion unit 203 suggests the use of the payment service in association with a benefit. When it is not determined that an application for the target facility has been made, the use suggestion unit 203 does not suggest the use of the payment service. Note that when an application has been made, the use suggestion unit 203 may execute a process of suggesting the use of a payment service at that time. The processing of the use suggestion unit 203 in this case will be described in a modified example described later.

[0101] For example, the usage suggestion unit 203 may suggest the use of a payment service in association with a benefit to a user who is a member of a payment service but has not used the payment service for a predetermined period of time. In this case, the usage suggestion unit 203 obtains from the payment server 10 the date and time of last use of the payment service by the user who applied for the target facility, and determines whether a predetermined period (e.g., one month) has passed since the date and time of use. If it is determined that the predetermined period has not passed since the date and time of use, the usage suggestion unit 203 may not particularly suggest the use of the payment service, but if it is determined that the predetermined period has passed since the date and time of use, the usage suggestion unit 203 may suggest the use of the payment service in association with a benefit to a user who is a member of a payment service but has not downloaded the payment app.

[0102] For example, the usage suggestion unit 203 suggests to the user to use a payment service by presenting a link L for downloading a payment app to the user. The link L includes a URL to a computer that distributes the payment app (e.g., the payment server 10 or another computer). Data indicating the URL of the link L is assumed to be stored in the data storage unit 200. The usage suggestion unit 203 presents the link L to the user based on the data. In the example of FIG. 9 , the usage suggestion unit 203 sends the user an email M including the link L. The usage suggestion unit 203 may present the link L to the user by means other than the email M.

[0103] [2-2-3. Functions implemented on user devices] The functions realized by the user terminal 30 may be the same as those in the first embodiment.

[0104] [2-3. Processing Executed in the Usage Proposal System of the Second Embodiment] Fig. 11 is a diagram showing an example of processing executed in the usage suggestion system 2 of the second embodiment. The processing in Fig. 11 is executed by the control units 21 and 31 executing programs stored in the storage units 22 and 32, respectively.

[0105] 11, the processes of S200 and S201 are the same as the processes of S100 and S101. Based on the reception database DB3, the reception server 20 acquires application information of a user who has checked in a certain time before the check-in date (S202). Based on the application information obtained in S202 and the target facility ID stored in a database similar to the benefit database DB2 stored in the storage unit 22, the reception server 20 determines whether the user has applied for a facility of interest (S203).

[0106] If the user has applied for the facility in S203 (Y in S203), the reception server 20 sends the user an email M including the details of the benefit and a link L, thereby proposing the use of the payment service (S204), and the process ends. If the user has not applied for the facility in S203 (N in S203), the reception server 20 confirms the details of the application by sending the user a regular email M that does not include the link L (S205), and the process ends.

[0107] [2-4. Summary of the second embodiment] The usage suggestion system 2 of the second embodiment proposes the use of a payment service to a user who has applied for a facility using the reception service, based on application information, by associating the application with a benefit that is granted only when the user makes a payment to the facility using the payment service. Because a user who applied for a facility using the reception service finds the benefit attractive when the user makes a payment to the facility using the payment service, the usage suggestion system 2 can motivate users who do not use the payment service to use the payment service, thereby promoting its use. For example, if a user who applied for a facility using the reception service is not a member of the payment service, the usage suggestion system 2 can motivate the user to become a member of the payment service, thereby increasing the number of members of the payment service. If a user who applied for a facility using the reception service is a member of the payment service but is not using the payment service, the usage suggestion system 2 can motivate the user to use the payment service, thereby promoting its use. Because a user's application for a facility using the reception service is a condition for receiving a benefit, the usage suggestion system 2 can motivate users to apply for the facility, thereby promoting its use. Since no special benefits are given to the user even if the user applies for a facility by a means other than the reception service, the usage suggestion system 2 can motivate the user to use the reception service and promote the use of the reception service.Since no special benefits are given to the user even if the user makes a payment to a facility by a means other than the payment service, the usage suggestion system 2 can motivate the user to use the payment service and promote the use of the payment service.

[0108] Furthermore, the usage suggestion system 2 suggests to the user the use of a payment service by associating a benefit that is granted when the user applies for a facility that is a target of the reception service and makes a payment to a target store in the administrative district where the facility is located. In this way, the usage suggestion system 2 can promote the use of target stores in a specific administrative district. The usage suggestion system 2 can also promote applications for target facilities in a specific administrative district. As a result, the operator of the payment service, the operator of the reception service, and the local government cooperate with each other, and the realization of the usage suggestion system 2 can revitalize the economy of a specific administrative district.

[0109] Furthermore, the usage suggestion system 2 suggests the use of a payment service by presenting the user with a link L for downloading a payment app. This allows the usage suggestion system 1 to encourage the user to download the payment app. The usage suggestion system 1 can promote the use of payment services from the payment app.

[0110] [3. Modifications] The present disclosure is not limited to the above-described embodiments, and may be modified as appropriate without departing from the spirit of the present disclosure.

[0111] [3-1. Modification of the first embodiment] 12 is a diagram showing an example of functions realized in a modification of the first embodiment. For example, the payment server 10 includes an administrative district advertisement presentation unit 104, a first benefit presentation unit 105, a questionnaire presentation unit 106, a facility advertisement presentation unit 107, and an entry screen control unit 108. The administrative district advertisement presentation unit 104, the first benefit presentation unit 105, the questionnaire presentation unit 106, the facility advertisement presentation unit 107, and the entry screen control unit 108 are each realized by the control unit 11. The reception server 20 includes a second benefit presentation unit 204 and a third benefit presentation unit 205. The second benefit presentation unit 204 and the third benefit presentation unit 205 are each realized by the control unit 21.

[0112] [Variation 1-1] For example, a user who has applied for a facility in a particular administrative district through the reception service and made a payment to a store in the administrative district through the payment service may feel a potential attraction to the administrative district. For this reason, an administrative district advertisement related to the administrative district may be presented to the user. An administrative district advertisement is an advertisement related to the administrative district. For example, an administrative district advertisement may be information about the administrative district's specialty products, tourist destinations, famous people, or other information. An advertisement for hometown tax donations in Japan may correspond to an administrative district advertisement. Note that hometown tax donations are a system in which users can receive a special deduction when making donations to local governments in addition to the deductions available for donations to non-local governments. The definition of hometown tax donations may be a well-known definition in Japan.

[0113] The data storage unit 100 of variant example 1-1 stores administrative district advertisement data related to administrative district advertisements. The administrative district advertisement data indicates specific content of the administrative district advertisement. For example, the administrative district advertisement data may indicate text, images, videos, or a combination thereof. The administrative district advertisement data may be in any format. For example, the administrative district advertisement data may be text data, document data, image data, data in a markup language such as HTML, or other formats.

[0114] The administrative district advertisement data may be uploaded to the payment server 10 by a local government official, or may be uploaded to the payment server 10 by another party (for example, a payment service operator). When a campaign is held in each of multiple administrative districts, the data storage unit 100 may store administrative district advertisement data for each of the multiple administrative districts. The data storage unit 100 stores information that can identify an administrative district (for example, an ID assigned to the administrative district or the name of the administrative district) and the administrative district advertisement data in association with each other.

[0115] The reward granting system 1 of Modification 1-1 includes an administrative district advertisement presentation unit 104. The administrative district advertisement presentation unit 104 presents an administrative district advertisement to a user. The administrative district advertisement presentation unit 104 presents the administrative district advertisement to a user based on administrative district advertisement data stored in the data storage unit 100. For example, based on application information and payment information, the administrative district advertisement presentation unit 104 identifies a user who has applied for a target facility in a specific administrative district using the reception service and made a payment to a target store in the administrative district using the payment service. The method of identifying the user may be the same as that of the reward granting unit 103 described in the first embodiment. The administrative district advertisement presentation unit 104 presents an administrative district advertisement to the identified user based on the administrative district advertisement data.

[0116] Fig. 13 is a diagram showing an example of an administrative district advertisement. In the example of Fig. 13, the administrative district advertisement presentation unit 104 presents the administrative district advertisement to the user by displaying an administrative district advertisement including a message such as "Click here to make a hometown tax donation to DDD City" on a completion screen SC4 of the payment app. The completion screen SC4 on which the administrative district advertisement is presented may be a screen indicating that payment to the target store has been completed, or may be a screen indicating that payment to a store that is not the target store has been completed.

[0117] In the example of Figure 13, the administrative district advertisement includes a link to a hometown tax donation website. The administrative district advertisement presentation unit 104 may present the administrative district advertisement in any presentation method. For example, the administrative district advertisement presentation unit 104 may present the administrative district advertisement to the user by displaying it on another screen of the payment app (for example, the top screen SC3 or a screen for the notification function of the payment app).

[0118] For example, the administrative district advertisement presentation unit 104 may present the administrative district advertisement to the user using a presentation method other than a payment app, such as email, push notification, banner notification, pop-up, SMS message, SNS message, message in a messaging app, or other means. When these presentation methods are used, the administrative district advertisement data indicates the content of these messages or notifications. The administrative district advertisement presentation unit 104 may present the administrative district advertisement to the user using these presentation methods based on the administrative district advertisement data.

[0119] The administrative district advertisement presentation unit 104 can present the administrative district advertisement to the user at any timing. For example, the administrative district advertisement presentation unit 104 may present the administrative district advertisement to the user after the user has used a target facility and a target store. The administrative district advertisement presentation unit 104 may present the administrative district advertisement to the user before the user uses a target facility. The administrative district advertisement presentation unit 104 may present the administrative district advertisement to the user before the user uses a target store.

[0120] Furthermore, when a campaign is held in each of a plurality of administrative districts, the administrative district advertisement presentation unit 104 may identify the administrative district in which the user applied for the target facility based on the application information, and present the administrative district advertisement for that administrative district based on the administrative district advertisement data for that administrative district.The administrative district advertisement presentation unit 104 may identify the administrative district in which the user made a payment for the target store based on the payment information, and present the administrative district advertisement for that administrative district based on the administrative district advertisement data for that administrative district.

[0121] The administrative district advertisement may be presented on the reception service side. In this case, the administrative district advertisement presentation unit 104 may be realized by the reception server 20. The data storage unit 200 stores administrative district advertisement data. The administrative district advertisement presentation unit 104 of the reception server 20 may present the administrative district advertisement to the user on the reception app based on the administrative district advertisement data. The reception server 20 may acquire payment information from the payment server 10 and identify that the user has made a payment at a target store. The administrative district advertisement presentation unit 104 of the reception server 20 may present the administrative district advertisement to the user by another presentation method, such as email, as described above.

[0122] The reward granting system 1 of the modification 1-1 presents administrative district advertisements related to administrative districts to users. This allows the reward granting system 1 to present administrative district advertisements to users who are likely to be interested in administrative districts, thereby increasing the advertising effectiveness of the administrative district advertisements. Users can learn useful information that interests them.

[0123] [Variation 1-2] For example, a benefit may be presented to a user in a payment service. The presentation of a benefit means the presentation of specific details of the benefit. If a benefit is granted as part of a campaign, the presentation of the benefit can also be said to be the presentation of specific details of the campaign. The benefit granting system 1 of variant example 1-2 includes a first benefit presentation unit 105. The first benefit presentation unit 105 presents a benefit to a user in a payment service. For example, the first benefit presentation unit 105 presents a benefit to a user based on benefit information stored in benefit database DB2.

[0124] For example, the first benefit presentation unit 105 identifies a user who has applied for a facility of interest through the reception service based on the application information. The method for identifying the user may be the same as that used by the benefit granting unit 103 described in the first embodiment. The first benefit presentation unit 105 presents a benefit to the identified user based on the benefit information. Note that the first benefit presentation unit 105 may also identify a user who has applied for a facility of interest through the reception service and made a payment to a facility of interest through the payment service based on the application information and payment information, and present a benefit to the user.

[0125] FIG. 14 is a diagram showing an example of a benefit presented to a user in a payment service. In the example of FIG. 14, the first benefit presentation unit 105 presents the benefit to the user by displaying information indicating the content of the benefit, such as "DDD City Campaign Now On! Earn Double Points When Shopping at Participating Stores," on the top screen SC3 of the payment app. The first benefit presentation unit 105 may present the benefit to the user in any presentation method. For example, the first benefit presentation unit 105 may present the benefit to the user by displaying information indicating the content of the benefit on another screen of the payment app (e.g., a completion screen SC4 indicating that payment to a store other than the participating store has been completed, or a screen for the payment app's notification function).

[0126] For example, the first benefit presentation unit 105 may present the benefit to the user using a presentation method other than the payment app, such as email, push notification, banner notification, pop-up, SMS message, SNS message, message app message, or other means. These messages or notifications are sent as messages or notifications from the payment service. When these presentation methods are used, the benefit information indicates the content of these messages or notifications. The first benefit presentation unit 105 may present the benefit to the user using these presentation methods based on the benefit information.

[0127] The first benefit presentation unit 105 can present a benefit to the user at any timing. For example, the first benefit presentation unit 105 may present a benefit to the user after the user has visited a target facility and a target store. The first benefit presentation unit 105 may present a benefit to the user before the user has visited a target facility. The first benefit presentation unit 105 may present a benefit to the user before the user has visited a target store.

[0128] Furthermore, when a campaign is held in each of a plurality of administrative districts, first benefit presentation unit 105 may identify the administrative district in which the user applied for the target facility based on the application information, and present the benefit of that administrative district based on benefit information for that administrative district. First benefit presentation unit 105 may identify the administrative district in which the user made a payment at the target store based on payment information, and present the benefit of that administrative district based on benefit information for that administrative district.

[0129] The reward system 1 of the modification 1-2 presents rewards to users in payment services. This allows users who use the payment services to know that they will receive a reward, so the reward system 1 can strongly motivate users to use the target store and effectively promote use of the target store.

[0130] [Variation 1-3] For example, in Variation 1-2, a case was described in which a benefit is presented to a user in a payment service. The benefit may also be presented in a reception service. The benefit granting system 1 of Variation 1-3 includes a second benefit presentation unit 204. The second benefit presentation unit 204 presents a benefit to a user in a reception service. The data storage unit 200 of Variation 1-3 may store a database similar to the benefit database DB2, or may store only the benefit information portion of the benefit database DB2. It is assumed that the data storage unit 200 stores at least the benefit information.

[0131] For example, the second benefit presentation unit 204 identifies a user who has applied for a facility of interest through the reception service based on the application information. The method for identifying the user may be the same as that used by the benefit granting unit 103 described in the first embodiment. The second benefit presentation unit 204 presents a benefit to the identified user based on the benefit information. Note that the second benefit presentation unit 204 may also identify a user who has applied for a facility of interest through the reception service and made a payment to the facility of interest through the payment service based on the application information and payment information, and present a benefit to the user. In this case, it is assumed that the payment information is stored in the data storage unit 200.

[0132] FIG. 15 is a diagram showing an example of a benefit presented to a user in the reception service. In the example of FIG. 15, the second benefit presentation unit 204 presents the benefit to the user by displaying information indicating the content of the benefit, such as "DDD City Campaign Now On! Apply for a Visit to a Target Facility and Pay at the Target Store with AAA Pay to Earn Double Points," on the top screen SC1 of the reception app. The second benefit presentation unit 204 may present the benefit to the user in any presentation method. For example, the second benefit presentation unit 204 may present the benefit to the user by displaying information indicating the content of the benefit on another screen of the reception app (for example, a completion screen SC2 indicating that the application for the target facility has been completed, or a screen for the notification function of the reception app).

[0133] For example, the second benefit presentation unit 204 may present the benefit to the user using a presentation method other than the reception app, such as email, push notification, banner notification, pop-up, SMS message, SNS message, message in a messaging app, or other means. These messages or notifications are sent as messages or notifications from the reception service. When these presentation methods are used, the benefit information indicates the content of these messages or notifications. The second benefit presentation unit 204 may present the benefit to the user using these presentation methods based on the benefit information.

[0134] The second benefit presentation unit 204 can present a benefit to the user at any timing. For example, the second benefit presentation unit 204 may present a benefit to the user after the user has visited a target facility and a target store. The second benefit presentation unit 204 may present a benefit to the user before the user has visited a target facility. The second benefit presentation unit 204 may present a benefit to the user before the user has visited a target store.

[0135] Furthermore, when a campaign is held in each of a plurality of administrative districts, second benefit presentation unit 204 may identify the administrative district in which the user applied for the target facility based on the application information, and present the benefit of that administrative district based on benefit information for that administrative district. Second benefit presentation unit 204 may identify the administrative district in which the user made a payment at the target store based on payment information, and present the benefit of that administrative district based on benefit information for that administrative district.

[0136] The reward granting system 1 of Modification 1-3 presents a reward to a user during the reception service. This allows the user who uses the reception service to know that a reward will be granted, so the reward granting system 1 can strongly motivate the user to use the target store and effectively promote use of the target store.

[0137] [Variation 1-4] For example, the benefit to the user may be presented via an email indicating that the application for the facility has been completed. The benefit granting system 1 of Modification 1-4 includes a third benefit presentation unit 205. The third benefit presentation unit 205 presents the benefit to the user via an application completion notice indicating that the application for the facility has been completed. Modification 1-4 takes as an example a case where the third benefit presentation unit 205 presents the benefit to the user by sending an email to be sent when the application is completed. This email may have the same format as in FIG. 9. Note that the data storage unit 200 of Modification 1-4 stores benefit information, as in Modification 1-3.

[0138] For example, third benefit presentation unit 205 determines whether the user has applied for the facility based on the facility ID indicated in the application information. When it is determined that the user has applied for the facility, third benefit presentation unit 205 generates an email including specific details of the benefit based on the benefit information stored in data storage unit 200, and sends the email to the user. Note that, although Modifications 1-4 illustrate an example in which the application completion notification is email, the application completion notification may be sent by any notification means. For example, third benefit presentation unit 205 may send the application completion notification by a notification function on the reception app, a push notification, a banner notification, a pop-up, SMS, SNS, a messaging app, or other means.

[0139] The reward granting system 1 of Variation 1-4 presents a reward to a user in an application completion notice indicating that an application for a target facility has been completed. This allows the user who receives the application completion notice to know that a reward will be granted. Therefore, the reward granting system 1 can strongly motivate the user to use the target store and effectively promote use of the target store. For example, users often pay attention to the application completion notice to confirm that the application has been completed correctly. The reward granting system 1 can enhance its appeal to users by presenting a reward in the application completion notice, which users pay more attention to.

[0140] [Variation 1-5] For example, the reward granting unit 103 may grant a reward to a user who applies for a target facility using the reception service, checks in to the target facility, and makes a payment to a target store using the payment service. That is, the reward granting unit 103 may grant a reward to a user on the condition that the user checks in to the target facility, as well as on the condition that the user applies for the target facility. The reward granting unit 103 may detect check-in to the target facility by a method used in a known service in which check-in to some facility is performed.

[0141] For example, when a user checks in to a facility, a person in charge of the facility performs an operation on a terminal at the facility to indicate that the user has checked in. The terminal at the facility transmits check-in information that can identify the checked-in user to the reception server 20. Information about the user to be checked in may be stored in advance in the terminal at the facility. The check-in information may include the user ID of the checked-in user, or may include an ID for identifying the application. These IDs may be used to identify which user has checked in.

[0142] For example, the reception server 20 transmits check-in information to the payment server 10. The payment server 10 receives the check-in information from the reception server 20. The benefit granting unit 103 identifies the user who has checked in to the target facility based on the check-in information. Note that the check-in information may be transmitted directly from a terminal at the target facility to the payment server 10. Alternatively, the user may check in by operating the user terminal 30. In this case, the user terminal 30 may transmit the check-in information to the payment server 10 or the reception server 20.

[0143] For example, the reward granting unit 103 determines whether a user who has made an application for the target facility using the reception service has checked in, based on the check-in information. When it is determined that a user who has made an application for the target facility using the reception service has checked in, the reward granting unit 103 grants a reward to the user on the condition that the user makes a payment to the target store using the payment service. When it is not determined that a user who has made an application for the target facility using the reception service has checked in, the reward granting unit 103 does not grant a reward to the user even if the user makes a payment to the target store using the payment service.

[0144] The reward granting unit 103 may determine that the user has used the target facility by a method other than check-in. For example, the reward granting unit 103 may determine that the user has used the target facility by determining whether or not the user has checked out from the target facility. The reward granting unit 103 may determine that the user has used the target facility by determining whether or not the user has paid for the facility. The reward granting unit 103 may grant a reward to the user not only on the condition that the user applies for use of the target facility, but also on the condition that the user uses the target facility. The reward granting unit 103 may not grant a reward to the user if the user has applied for use of the target facility but has not used the target facility, even if the user has applied for use of the target facility.

[0145] The reward granting system 1 of Modification 1-5 grants a reward to a user who applies for a facility using the reception service, checks in to the facility, and makes a payment to the facility using the payment service. This prevents the reward granting system 1 from granting a reward to an unauthorized user who applies for a facility but does not check in.

[0146] [Variation 1-6] For example, the application information may include information regarding the length of stay that the user will have at the target facility. The length of stay is the period from when the user arrives at the target facility until when the user leaves the facility. If the target facility is an accommodation facility, as in the first embodiment, the length of stay is the period from check-in to check-out. If the target facility is an event venue, the length of stay is the period during which the user will participate in an event at the event venue. Similarly, the application information for other target facilities may also indicate the length of stay. The length of stay is specified by the user at the time of application.

[0147] The benefit granting unit 103 of variant 1-6 grants a benefit to a user who makes an application for a target facility using the reception service and makes a payment to a target store using the payment service during their stay. The benefit granting unit 103 determines whether a payment to a target store using the payment service is made during their stay by determining whether the payment date and time indicated in the payment information is included in the stay period indicated in the application information. Even if a user makes an application for a target facility using the reception service and makes a payment to a target store using the payment service, if the payment is not made during their stay, the benefit granting unit 103 does not grant a benefit to the user.

[0148] The reward granting system 1 of Variation 1-6 grants a reward to a user who applies for a target facility through the reception service and makes a payment to a target store through the payment service during their stay. For example, suppose a user visits the target facility for which they applied through the reception service, and then visits a location near the target facility for a different purpose and uses the target store without applying through the reception service. In this case, if the reward is granted even when the user visits a location near the target facility for a different purpose, this may be contrary to the purpose of the campaign. The reward granting system 1 can ensure the legitimacy of the reward by not granting the reward in such cases. For example, the reward granting system 1 can prevent a user from fraudulently obtaining a reward by visiting a target store multiple times for a different purpose after completing a trip that includes a stay at the target facility.

[0149] [Variation 1-7] For example, in a reception service, each facility may be ranked. The ranks can also be considered as classifications of facilities. Each facility may be ranked based on any criteria. For example, each facility may be ranked by price range. The operator of the reception service may rank each facility, or the person in charge of each facility may specify the rank of their own facility. The rank of each facility is stored in a facility database stored in the data storage unit 200. For example, when a reception service accepts applications for accommodation, the facilities may be ranked into luxury, normal, reasonable, etc. The ranks may be any number of levels and are not limited to three levels. The ranks may be two levels, or four or more levels.

[0150] The benefit granting unit 103 of Modification 1-7 grants a benefit to the user according to the rank of the target facility. The relationship between ranks and benefits is assumed to be defined in the benefit database DB2. For example, the benefit information indicates specific details of the benefit for each rank. The rank of the target facility may be indicated in the application information. The payment server 10 may obtain the rank of the target facility by inquiring about the rank of the target facility from the reception server 20. The benefit granting unit 103 identifies the rank of the target facility for which the user has applied based on the application information or the inquiry. The benefit granting unit 103 refers to the benefit information and grants a benefit associated with the rank of the target facility. When a benefit is presented, as in Modifications 1-2 to 1-4, the benefit may be presented according to the rank of the target facility.

[0151] For example, the reward granting unit 103 may determine the point redemption rate to be granted as a reward to the user such that the higher the rank of the target facility, the higher the point redemption rate. That is, the reward granting unit 103 may determine the point redemption rate to be granted as a reward to the user such that the lower the rank of the target facility, the lower the point redemption rate. Similarly, when a reward other than the point redemption rate is granted, the reward granting unit 103 may grant the user a reward according to the rank of the target facility.

[0152] The reward granting system 1 of Modification Example 1-7 grants a reward to a user according to the rank of the target facility. This allows the reward granting system 1 to grant an appropriate reward to a user according to the rank of the target facility. In other words, the reward granting system 1 can vary the reward according to the rank of the target facility. For example, if the reward granting system 1 grants a reward at a high point redemption rate to a user who has applied for a luxury target facility, it can encourage applications for the luxury target facility.

[0153] [Variation 1-8] For example, in Modification Example 1-7, the benefit granting unit 103 may grant a user a benefit related to a target store according to the rank of the target facility. The relationship between the rank and the target store is defined in the benefit database DB2. For example, for each rank, the store ID of the target store from which a user who has applied for a target facility of that rank can obtain a benefit is defined in the benefit database DB2. For example, the higher the rank, the more luxurious the target store whose store ID is associated with that rank may be.

[0154] For example, the reward granting unit 103 identifies the rank of the target facility for which the user has applied, based on the application information or an inquiry to the reception server 20. The reward granting unit 103 references the reward database DB2 to identify the target store associated with the identified rank. The reward granting unit 103 determines whether the user used a payment service to pay for the identified target store, based on the payment information. If it is determined that the user used a payment service to pay for the target store, the reward granting unit 103 grants a reward to the user. The reward granting unit 103 does not grant a reward to the user even if the user uses a payment service at a store other than the target store associated with the rank (for example, a target store associated with a different rank).

[0155] The reward granting system 1 of Modification Example 1-8 grants a reward to a user at a target store according to the rank of the target facility. This allows the reward granting system 1 to grant a reward to a user who uses an appropriate target store according to the rank of the target facility. In other words, the reward granting system 1 can vary the target store to which a reward is granted according to the rank of the target facility. For example, when a user who has applied for a luxury target facility uses the luxury target store, the reward granting system 1 can grant a reward to the user. This allows the reward granting system 1 to encourage the use of target stores according to the rank of the target facility.

[0156] [Variation 1-9] For example, after the user uses a target facility, the payment service may conduct a survey for the user. The data storage unit 100 of Modification Example 1-9 stores survey data related to the survey. The survey data is data indicating the specific content of the survey. The survey data may be in any format. For example, when a survey is presented on a payment app, the survey data may be data (e.g., HTML data or image data) for displaying a screen on the payment app.

[0157] The reward granting system 1 of Variation 1-9 includes a questionnaire presentation unit 106. The questionnaire presentation unit 106 presents a questionnaire about a target facility to a user who has used the target facility in the payment service. For example, the questionnaire presentation unit 106 determines whether the user has checked out of the target facility based on the check-out date indicated in the application information. The questionnaire presentation unit 106 may also determine that the user has checked out of the target facility based on information received from a terminal of the target facility. For example, when it is determined that the user has checked out of the target facility, the questionnaire presentation unit 106 presents a questionnaire to the user based on the questionnaire data.

[0158] FIG. 16 is a diagram showing an example of a questionnaire presented to a user. In the example of FIG. 16, the questionnaire presentation unit 106 presents the questionnaire on a completion screen SC4 indicating that payment has been completed. When the user operates the user terminal 30 to answer the questionnaire, the user terminal 30 transmits answer result data indicating the user's answer results to the payment server 10. The payment server 10 receives the answer result data from the user terminal 30. The payment server 10 records the answer result data in the data storage unit 100. The payment server 10 may transmit the answer result data to an external party such as the target facility.

[0159] The questionnaire presentation unit 106 may present the questionnaire in any presentation method. For example, the questionnaire presentation unit 106 may present the questionnaire to the user by displaying the questionnaire on another screen of the payment app (for example, the top screen SC3 or a screen for a notification function of the payment app).

[0160] For example, the survey presentation unit 106 may present the survey to the user using a presentation method other than the payment app, such as email, push notification, banner notification, pop-up, SMS message, SNS message, message in a messaging app, or other means. When these presentation methods are used, the survey data indicates the content of these messages or notifications. The survey presentation unit 106 may present the survey to the user using these presentation methods based on the survey data.

[0161] In the payment service, the reward granting system 1 of Variation 1-9 presents a questionnaire about a target facility to a user who has used the target facility. This allows the reward granting system 1 to obtain the results of the questionnaire responses, such as impressions of the target facility, from the users who have used the target facility. For example, if a questionnaire is conducted about a campaign itself, the local government that sponsored the campaign can consider the content of future campaigns based on the results of the questionnaire responses.

[0162] [Variation 1-10] For example, a user who has applied for a target facility using the reception service and made a payment to a target store using the payment service may be interested in an advertisement for the target facility. Therefore, the user may be presented with an advertisement for the target facility. The advertisement for the target facility may be an advertisement for the target facility, or an advertisement for a facility other than the target facility. The other facility may be another facility in the same administrative district as the target facility, or another facility of the same rank as the target facility. For example, the facility advertisement may be an introduction to the facility, available plans, prices, or other information.

[0163] The data storage unit 100 of variant example 1-1 stores facility advertisement data related to facility advertisements. The facility advertisement data indicates specific content of the facility advertisement. For example, the facility advertisement data may indicate text, images, videos, or a combination thereof. The facility advertisement data may be in any format. For example, the facility advertisement data may be text data, document data, image data, data in a markup language such as HTML, or another format. The facility advertisement data may be uploaded to the payment server 10 by a facility staff member, or may be uploaded to the payment server 10 by another person (for example, a payment service operator).

[0164] The reward granting system 1 of Modification 1-10 includes a facility advertisement presentation unit 107. The facility advertisement presentation unit 107 presents a facility advertisement corresponding to a target facility to a user in the payment service. The facility advertisement presentation unit 107 presents the facility advertisement to a user based on facility advertisement data stored in the data storage unit 100. For example, the facility advertisement presentation unit 107 identifies a user who has applied for a target facility in the reception service and made a payment to a target store in the payment service based on application information and payment information. The method of identifying the user may be the same as that of the reward granting unit 103 described in the first embodiment. The facility advertisement presentation unit 107 presents a facility advertisement to the identified user based on the facility advertisement data.

[0165] FIG. 17 is a diagram showing an example of a facility advertisement. In the example of FIG. 17, the facility advertisement presentation unit 107 presents the facility advertisement to the user by displaying the facility advertisement on a completion screen SC4 of the payment app. The facility advertisement presentation unit 107 may present the facility advertisement by any presentation method. For example, the facility advertisement presentation unit 107 may present the facility advertisement to the user by displaying the facility advertisement on another screen of the payment app (for example, the top screen SC3 or a screen for the notification function of the payment app).

[0166] For example, the facility advertisement presentation unit 107 may present a facility advertisement to a user using a presentation method other than a payment app, such as email, push notification, banner notification, pop-up, SMS message, SNS message, message in a messaging app, or other means. When these presentation methods are used, the facility advertisement data indicates the content of these messages or notifications. The facility advertisement presentation unit 107 may present a facility advertisement to a user using these presentation methods based on the facility advertisement data.

[0167] The facility advertisement presentation unit 107 can present a facility advertisement to a user at any timing. For example, the facility advertisement presentation unit 107 may present a facility advertisement to a user after the user has used a target facility and a target store. The facility advertisement presentation unit 107 may present a facility advertisement to a user before the user uses a target facility. The facility advertisement presentation unit 107 may present a facility advertisement to a user before the user uses a target store.

[0168] The reward system 1 of Modification 1-10 presents a facility advertisement corresponding to a target facility to a user in a payment service. This allows the reward system 1 to present the facility advertisement to users who are likely to be interested in the facility advertisement corresponding to the target facility, thereby increasing the advertising effectiveness of the facility advertisement. The user can learn useful information that interests him or her.

[0169] [Variation 1-11] For example, a user may need to enter the campaign described in the first embodiment to receive a reward. The payment service may detect that the user has applied for a facility in the reception service and accept the entry. The reward awarding system 1 of Modification 1-11 includes an entry screen control unit 108. The entry screen control unit 108 causes the payment service to display an entry screen that accepts entries for a reward campaign based on the application information.

[0170] FIG. 18 is a diagram showing an example of an entry screen. In the example of FIG. 18, a top screen SC3 is described as an example of an entry screen. The entry screen control unit 108 displays the top screen SC3 on the payment app as an example of an entry screen including user interface parts (e.g., buttons) for entry. Data (e.g., HTML data or image data) for displaying the entry screen is assumed to be stored in the data storage unit 100. Note that the entry screen may be a screen other than the top screen SC3. The entry screen may be any screen on the payment app (e.g., a completion screen SC4 or a screen for a notification function on the payment app).

[0171] For example, the entry screen control unit 108 determines whether or not the user has applied for the target facility based on the application information. If it is determined that the user has applied for the target facility, the entry screen control unit 108 causes the entry screen to be displayed on the user terminal 30 by transmitting data for displaying the entry screen to the user terminal 30. If it is determined that the user has not applied for the target facility, the entry screen control unit 108 does not transmit data for displaying the entry screen to the user terminal 30. In this case, a top screen SC3 that does not include user interface parts for entry may be displayed on the user terminal 30.

[0172] The reward granting unit 103 of Modification Example 1-11 grants a reward to a user who has made an entry. For example, when a user performs an entry operation on an entry screen, the user terminal 30 transmits an entry request for the user to enter the campaign to the payment server 10. Upon receiving the entry request, the payment server 10 stores entry information indicating that the user has entered the campaign in the payment database DB1 or another database.

[0173] For example, the reward granting unit 103 grants a reward to a user for whom entry information is stored. The reward granting unit 103 does not grant a reward to a user for whom entry information is not stored. In other words, even if a user applies for admission to a target facility using the reception service and makes payment to a target store using the payment service, the reward granting unit 103 does not grant a reward unless the user has entered. The reward granting unit 103 may control whether or not to grant a reward to a user based on the entry information.

[0174] The reward granting system 1 of Variation 1-11 displays an entry screen based on application information. The reward granting system 1 grants a reward to a user who has entered. This allows the reward granting system 1 to display the entry screen on the user terminal 30 of a user who is the target of the campaign, thereby improving user convenience. By requesting the user to enter, the reward granting system 1 can make the user more aware of the existence of the campaign.

[0175] [Variation 1-12] For example, the reward granting unit 103 may grant a reward to a user according to the user's application history in the reception service. The application history is a history of past use of the reception service. For example, if a user has made multiple applications in the past, the application information for each of the multiple past applications is stored in the reception database DB3. The reward granting unit 103 acquires the application information for each of the multiple past applications from the reception server 20, and grants a reward according to the application history indicated by the application information.

[0176] The relationship between the application history of the reception service and the benefits is defined in the benefit database DB2. For example, the benefit information indicates the specific details of the benefit for each number of uses of the target facility (or the total number of uses of all target facilities in the administrative district) calculated from the application history. The benefit granting unit 103 calculates the number of uses of the target facility (or the total number of uses of all target facilities in the administrative district) from the application history of the reception service, and grants the user a benefit according to the calculation result. For example, the more times the number of uses, the higher the point redemption rate may be.

[0177] The reward granting system 1 of Variation 1-12 grants a reward to a user according to the user's application history in the reception service. This allows the reward granting system 1 to grant an appropriate reward to the user according to the user's application history. In other words, the reward granting system 1 can vary the reward according to the user's application history. For example, the reward granting system 1 can encourage use of a specific target facility by granting a reward at a high point redemption rate to a user who has repeatedly used the target facility (or a user who has repeatedly used a target facility in a specific administrative district).

[0178] [Variation 1-13] For example, the application information may include information about each of the user who made the application and other users who will use the facility together with the user. The other users may be any person, and in the case of an application for accommodation, they may be accompanying persons. For example, the other users may be family members or friends of the user. When making an application through the reception service, the user inputs the user IDs of the other users. The application information of variant 1-13 includes the user IDs of the other users.

[0179] The benefit granting unit 103 of Modification Example 1-13 grants a benefit to another user when that other user uses a payment service at a target store. For example, the benefit granting unit 103 identifies that the other user will use the target facility based on application information. After identifying that the other user will use the target facility, the identification granting unit determines whether the other user has used a payment service at the target store based on the payment information. If it is determined that the other user has used a payment service at the target store, the identification granting unit grants a benefit to the other user. The method of granting the benefit itself may be the same as that for the user who made the application.

[0180] The reward granting system 1 of Modification Example 1-13 grants a reward to another user when the other user uses a payment service at a target store. This allows the reward granting system 1 to motivate not only the user who made the application but also other users accompanying them to use the target store, thereby effectively promoting use of the target store.

[0181] [3-2. Modification of the second embodiment] 19 is a diagram showing an example of functions realized in a modification of the second embodiment. For example, the reception server 20 includes an administrative district advertisement presentation unit 206. The administrative district advertisement presentation unit 206 is realized by the control unit 21.

[0182] [Variation 2-1] For example, even in the usage suggestion system 2 of the second embodiment, an administrative district advertisement like that of Modification 1-1 may be presented to a user. The usage suggestion system 2 of Modification 2-1 includes an administrative district advertisement presentation unit 206. The administrative district advertisement presentation unit 206 presents an administrative district advertisement related to an administrative district to a user. The administrative district advertisement presentation unit 206 differs from Modification 1-1 in that it presents an administrative district advertisement to a user who does not use a payment service, but the administrative district advertisement may be the same as that of Modification 1-1. The data storage unit 200 of Modification 2-1 stores administrative district advertisement data.

[0183] For example, the administrative district advertisement presentation unit 206 identifies users who have applied for a target facility in a specific administrative district that is the target of the campaign through the reception service based on the application information. Data indicating which target facilities are facilities in the specific administrative district is assumed to be stored in the data storage unit 200. For example, the target facilities in the specific administrative district may be indicated in a facility database that stores basic information about the facilities, or the target facilities in the specific administrative district may be indicated in another database.

[0184] For example, the administrative district advertisement presentation unit 206 presents an administrative district advertisement based on the administrative district advertisement data to a user who has applied for a target facility in a specific administrative district through the reception service. The administrative district advertisement may be similar to that shown in FIG. 13. However, while the administrative district advertisement in FIG. 13 is displayed on the completion screen SC4 of the payment app, the administrative district advertisement presentation unit 206 in variant example 2-1 displays the administrative district advertisement on the completion screen SC2 of the reception app. The administrative district advertisement presentation unit 206 may present the administrative district advertisement on another screen of the reception app (for example, the top screen SC1), or may present the administrative district advertisement by email, push notification, banner notification, pop-up, SMS message, SNS message, message app message, or other means.

[0185] The administrative district advertisement presentation unit 206 may present an administrative district advertisement to the user regardless of whether the user is using a payment service, or may present an administrative district advertisement to the user on the condition that the user is not using a payment service. For example, the reception server 20 may send the user ID of a user who has applied for a target facility in a specific administrative district through the reception service to the payment server 10, and inquire whether the user is using a payment service. The payment server 10 determines whether the user is using a payment service by determining whether the user ID received from the reception server 20 is stored in the payment database DB1. The payment server 10 determines whether the user is using a payment service by determining whether a predetermined time has passed since the user with the user ID last used the payment service.

[0186] For example, the payment server 10 transmits the execution result of the determination to the reception server 20. The reception server 20 receives the execution result of the determination from the payment server 10 and determines whether or not a user who has applied for a target facility in a specific administrative district through the reception service is using a payment service. If it is determined that the user is not using the payment service, the administrative district advertisement presentation unit 206 may present an administrative district advertisement to the user. If it is determined that the user is using the payment service, the administrative district advertisement presentation unit 206 may not present an administrative district advertisement to the user.

[0187] The usage suggestion system 2 of variant example 2-1 presents administrative district advertisements related to administrative districts to users. This allows the usage suggestion system 2 to present administrative district advertisements to users who are likely to be interested in administrative districts, thereby increasing the advertising effectiveness of the administrative district advertisements. Users can learn useful information that interests them.

[0188] [Variation 2-2] For example, in the second embodiment, an example was given in which email M suggested the use of a payment service in association with a benefit, but the suggestion may be made by a method other than email M. The usage suggestion unit 203 may suggest the use of a payment service to the user in association with a benefit during the reception service. The data storage unit 200 of modification 2-2 may store a database similar to the benefit database DB2, or may store only the benefit information portion of the benefit database DB2. It is assumed that the data storage unit 200 stores at least the benefit information.

[0189] FIG. 20 is a diagram showing an example of a screen on which the reception service suggests the use of a payment service. FIG. 20 shows an example in which the usage suggestion unit 203 suggests the use of a payment service in association with a benefit on the completion screen SC2. For example, similar to the second embodiment, the usage suggestion unit 203 identifies a user who has applied for a target facility in the reception service based on the application information. The usage suggestion unit 203 suggests the use of the payment service to the identified user in association with a benefit.

[0190] The usage suggestion unit 203 may present the administrative district advertisement on another screen of the reception app (for example, the top screen SC1), or may present the administrative district advertisement by email, push notification, banner notification, pop-up, SMS message, SNS message, message in a messaging app, or other means sent when the reservation is completed. These messages or notifications are sent as messages or notifications from the reception service.

[0191] In the reception service, the usage suggestion system 2 of the modification 2-2 suggests to the user the use of the payment service in association with the benefit. In this way, the usage suggestion system 2 can effectively appeal to the user to use the payment service in the reception service.

[0192] [Variation 2-3] For example, in the second embodiment, the case where the use of a payment service is suggested in the email M sent a predetermined time before the check-in date has been described, but the usage suggestion unit 203 may suggest to the user the use of the payment service in association with a benefit in the application completion notice indicating that the application has been completed. When the user has completed an application for a facility, the usage suggestion unit 203 in Modification Example 2-3 determines whether the user has applied for the facility in question based on the application information of the application.

[0193] For example, when it is determined that the user has applied for the target facility, the usage suggestion unit 203 sends the user an email containing content similar to that shown in FIG. 9 as an application completion notification. The usage suggestion unit 203 may send the application completion notification to the user by means other than email. For example, the usage suggestion unit 203 may send the application completion notification suggesting the use of a payment service in association with a benefit by using a notification function of a reception app, a push notification, a banner notification, a pop-up, an SMS message, a message on an SNS, a message on a messaging app, or other means. These messages or notifications are sent as messages or notifications from the reception service.

[0194] If the usage suggestion unit 203 does not determine that the user has applied for the facility, it sends the user an application completion notice that does not include any special benefits. This application completion notice may or may not suggest the use of a payment service.

[0195] The usage suggestion system 2 of variant example 2-3 suggests to the user the use of a payment service in association with a benefit in an application completion notification indicating that the application has been completed. This allows the usage suggestion system 2 to effectively appeal to the user to use the payment service in the reception service. For example, users often pay attention to the application completion notification to confirm that the application has been completed correctly. The usage suggestion system 2 can enhance the appeal to the user by presenting a benefit in the application completion notification, which is more noticeable to the user.

[0196] [Variation 2-4] For example, when a user checks in to a target facility, the usage suggestion unit 203 may suggest to the user that the user use a payment service in association with a benefit. Similar to the benefit granting unit 103 of Modification 1-5, the usage suggestion unit 203 may detect check-in to the target facility by a method used in a known service. For example, similar to Modification 1-5, the reception server 20 may receive check-in information from a terminal of the target facility or may receive check-in information from the user terminal 30.

[0197] For example, when the usage suggestion unit 203 detects that a user has checked in to a target facility, it suggests to the user that they use a payment service in association with a benefit. That is, the usage suggestion unit 203 suggests to the user that they use a payment service in association with a benefit, on the condition that the user has checked in to the target facility. For example, the usage suggestion unit 203 may display the details of the benefit and information suggesting the use of the payment service on a terminal at the target facility (e.g., a self-check-in terminal operated by the user). As another example, when the usage suggestion unit 203 detects that a user has checked in to the target facility, it may suggest to the user that they use a payment service in association with a benefit by other methods such as email or push notification.

[0198] When a user checks in to a target facility, the usage suggestion system 2 of variant example 2-4 suggests to the user that they use a payment service in association with a benefit. When a user checks in to a target facility and becomes more aware of the facility, the user may become interested in a benefit associated with the target facility. By making a suggestion at this time, the usage suggestion system 2 can effectively increase the appeal for using the payment service.

[0199] [Variation 2-5] For example, the usage suggestion unit 203 may suggest to the user the use of a payment service in association with a benefit according to the rank of the target facility. In Variation 2-5, as in Variation 1-7, each facility is ranked. In the usage suggestion system 2 of Variation 2-5, as in Variation 1-7, the data storage unit 200 stores a facility database indicating the rank of each facility. The explanation of the rank may also be the same as in Variation 1-7. For example, the usage suggestion unit 203 refers to the facility database and identifies the rank of the target facility for which the user has applied.

[0200] In Modification 2-5, the usage suggestion unit 203 suggests to the user the use of a payment service in association with a benefit corresponding to the rank of the target facility. As in Modification 1-7, the relationship between the rank and the benefit is defined in the benefit database DB2. The data storage unit 200 may store a database similar to the benefit database DB2, or may store data indicating only the portion of the benefit database DB2 that represents the relationship. The usage suggestion unit 203 may acquire the relationship by inquiring about the relationship from the payment server 10. Based on the relationship, the usage suggestion unit 203 identifies a benefit associated with the rank of the target facility. The usage suggestion unit 203 suggests the use of the payment service in association with the identified benefit. Although which benefit is referenced differs from the second embodiment, the method of associating the benefit with the use of the payment service may be the same as the second embodiment.

[0201] The usage suggestion system 2 of variant example 2-5 suggests to the user the use of a payment service in association with a benefit according to the rank of the target facility. This allows the usage suggestion system 2 to suggest to the user the use of a payment service in association with an appropriate benefit according to the rank of the target facility. In other words, the usage suggestion system 2 can vary the benefit according to the rank of the target facility. For example, the usage suggestion system 2 suggests the use of a payment service in association with a benefit of a high point redemption rate to a user who has applied for admission to a high-end target facility, thereby increasing the appeal of using the payment service.

[0202] [Variation 2-6] For example, the usage suggestion unit 203 may suggest to the user the use of a payment service in association with a benefit related to a target store according to the rank of the target facility. In Modification 2-6, as in Modification 1-8, the relationship between the rank and the target store is defined in the benefit database DB2. The data storage unit 200 in Modification 2-6 may store a database similar to the benefit database DB2, or may store data indicating only the part of the benefit database DB2 that represents the relationship. The usage suggestion unit 203 may acquire the relationship by querying the payment server 10 about the relationship. The data storage unit 200 also stores basic information such as the name and address of the store.

[0203] For example, based on the above relationship, the usage suggestion unit 203 suggests to the user the use of the payment service by associating information about target stores corresponding to the rank of the target facility with a benefit that will be granted if payment at the target store is made using the payment service. When email M is used as shown in FIG. 9, the usage suggestion unit 203 suggests the use of the payment service by sending the user email M including a list of all or part of target stores corresponding to the rank of the target facility for which the user has applied. The usage suggestion unit 203 may obtain information about the target stores from the data storage unit 200 and include the information in the email M. Similarly, when the use of the payment service is suggested by a method other than email M, the usage suggestion unit 203 may obtain information about the target stores from the data storage unit 200 and make a suggestion to the user based on the information.

[0204] The usage suggestion system 2 of Variation Example 2-6 suggests to a user the use of a payment service in association with a benefit related to a target store according to the rank of the target facility. This allows the usage suggestion system 2 to suggest the use of a payment service in association with a benefit related to an appropriate target store according to the rank of the target facility. In other words, the usage suggestion system 2 can vary the target store to which a benefit is granted depending on the rank of the target facility. For example, the usage suggestion system 2 can suggest to a user who has applied for a luxury target facility the use of a payment service in association with a benefit that is granted if the user uses a target store corresponding to the luxury target facility.

[0205] [Variation 2-7] For example, in the second embodiment, as in Modification 1-6, the application information may include information regarding the length of stay that the user will be staying at the facility. The meaning of the length of stay is as explained in Modification 1-6.

[0206] The usage suggestion unit 203 in Modification Example 2-7 suggests to the user the use of a payment service by associating a benefit, the condition for which is to be granted, with an application for a target facility in the reception service and payment at a target store during the stay period. For example, the usage suggestion unit 203 sends the user an email M including information (e.g., a message) indicating that payment at a target store during the stay period is a condition for granting the benefit. The usage suggestion unit 203 may also send the user an email M including information (e.g., a message) indicating that the benefit will not be granted even if payment is made at a target store outside the stay period.

[0207] The usage suggestion system 2 of Variation 2-7 suggests to a user the use of a payment service by associating a benefit with a condition for granting the benefit, which is a condition for applying for a target facility through the reception service and making a payment at a target store during the stay. For example, suppose a user visits a target facility for which they applied through the reception service, and then visits a location near the target facility for a different purpose and uses the target store without applying through the reception service. In this case, if the benefit is granted even when the user visits a location near the target facility for a different purpose, this may be contrary to the purpose of the campaign. The usage suggestion system 2 can notify the user in advance that the benefit will not be granted in such cases, making it less likely that the user will misunderstand.

[0208] [Variation 2-8] For example, in Variation 2-4, a case has been described in which the use of a payment service is suggested when the user checks in to a target facility. However, the usage suggestion unit 203 may suggest to the user the use of the payment service in association with a benefit on a screen for checking in to the target facility. This screen may be a screen displayed on the user terminal 30, or may be a terminal of the target facility (e.g., a self-check-in terminal operated by the user). Data (e.g., HTML data) required to display this screen is stored in the data storage unit 200. The usage suggestion unit 203 in Variation 2-8 makes a suggestion to the user based on the data.

[0209] For example, when a user operates the user terminal 30 at the time of check-in (for example, when the user causes the user terminal 30 to display a check-in code), the usage suggestion unit 203 may cause the user terminal 30 to display the details of the benefit and information suggesting the use of a payment service. The usage suggestion unit 203 causes the user terminal 30 to display the screen for check-in, including the details of the benefit and the information suggesting the use of a payment service, by transmitting the screen display data (for example, HTML data of a screen including the user's check-in code) to the user terminal 30.

[0210] For example, when a user operates a terminal at the target facility at the time of check-in (for example, when a user operates a self-check-in terminal), the usage suggestion unit 203 may cause the terminal at the target facility to display the details of the benefit and information suggesting the use of a payment service. The usage suggestion unit 203 causes the terminal at the target facility to display display data for a check-in screen including the details of the benefit and information suggesting the use of a payment service (for example, HTML data for a screen including a user's check-in code) by transmitting the display data to the terminal at the target facility.

[0211] The usage suggestion system 2 of Variation 2-8 suggests to the user the use of a payment service in association with benefits on the screen for checking in to a target facility. When checking in to a target facility, the user may become more aware of the target facility and may become interested in benefits associated with the target facility. By making a suggestion at this time, the usage suggestion system 2 can effectively increase the appeal for using the payment service.

[0212] [Variation 2-9] For example, the usage suggestion unit 203 may suggest to the user the use of a payment service in association with a benefit corresponding to the user's application history in the reception service. In Variation 2-9, as in Variation 1-12, the reception server 20 stores the application history, and the relationship between the application history and the benefit is defined in the benefit database DB2. The data storage unit 200 in Variation 2-9 may store a database similar to the benefit database DB2, or may store data indicating only the part of the benefit database DB2 that represents the relationship. The usage suggestion unit 203 may acquire the relationship by inquiring about the relationship from the payment server 10.

[0213] For example, the usage suggestion unit 203 identifies a benefit corresponding to the user's application history based on the above relationship, and suggests to the user the use of a payment service in association with the identified benefit. When email M is used as shown in Figure 9, the usage suggestion unit 203 suggests the use of a payment service by sending email M to the user including information about a benefit corresponding to the user's application history. For example, the usage suggestion unit 203 suggests the use of the payment service along with the content of the benefit indicating that the more times the user applies for use of a target facility, the greater the increase in point redemption rate.

[0214] The usage suggestion system 2 of Variation 2-9 suggests to a user the use of a payment service in association with a benefit according to the user's application history in the reception service. This allows the usage suggestion system 2 to suggest the use of a payment service in association with an appropriate benefit according to the user's application history. In other words, the usage suggestion system 2 can vary the benefit according to the user's application history. For example, the usage suggestion system 2 can strongly motivate users who have repeatedly used a specific target facility (or a target facility in a specific administrative district) to use the payment service by granting a benefit with a high point redemption rate.

[0215] [Variation 2-10] For example, as in Variation 1-13, the application information may include information about the user who made the application and other users who will use the facility together with the user. In Variation 2-10, as in Variation 1-13, the application information includes the user IDs of the other users. The usage suggestion unit 203 in Variation 2-10 suggests the use of the payment service to the other users in association with a benefit.

[0216] For example, the usage suggestion unit 203 determines whether other users are using a payment service. The usage suggestion unit 203 transmits the user IDs of the other users to the payment server 10 and inquires whether the other users are using a payment service. The reception server 20 obtains from the payment server 10 the determination result of whether the other users are using a payment service and refers to the determination result. When it is determined that the other users are using a payment service, the usage suggestion unit 203 suggests to the other users the use of the payment service in association with a benefit. When it is not determined that the other users are using a payment service, the usage suggestion unit 203 particularly suggests the use of the payment service. The method of suggesting the use of the payment service itself may be the same as that for the user who made the application.

[0217] The usage suggestion system 2 of variation 2-10 suggests to other users the use of a payment service in association with a benefit. The usage suggestion system 2 can motivate not only the user who applied but also other users accompanying them to use the payment service, thereby effectively promoting the use of the payment service.

[0218] [3-3. Other Modifications] For example, the above modifications may be combined.

[0219] For example, a function described as being realized by the payment server 10 may be realized by the reception server 20, the user terminal 30, or another computer. A process described as being realized by the payment server 10 may be shared among multiple computers. A process described as being realized by the reception server 20 may be realized by the payment server 10, the user terminal 30, or another computer. A process described as being realized by the reception server 20 may be shared among multiple computers. A process described as being realized by the user terminal 30 may be realized by the payment server 10, the reception server 20, or another computer.

[0220] [4. Notes] For example, in the present disclosure, the following configuration is also possible.

[0221] [4-1. Supplementary notes on the first embodiment] For example, the privilege granting system of the first embodiment can also be configured as follows. (1-1) an application information acquisition unit that acquires application information regarding an application made by a reception service that accepts applications regarding a predetermined facility; a payment information acquisition unit that acquires payment information regarding a payment made through the payment service; a benefit granting unit that grants a benefit to a user who has made an application for a target facility using the reception service and who has made a payment to a target store using the payment service based on the application information and the payment information; A reward system including: (1-2) the benefit granting unit grants the benefit to the user who has made an application for the target facility using the reception service and who has made a payment to the target store in the administrative district where the target facility is located using the payment service; The reward system described in (1-1). (1-3) The reward granting system further includes an administrative district advertisement presenting unit that presents an administrative district advertisement related to the administrative district to the user. The reward system described in (1-2). (1-4) The reward system further includes a first reward presentation unit that presents the reward to the user in the payment service. A benefit granting system according to any one of (1-1) to (1-3). (1-5) The benefit granting system further includes a second benefit presentation unit that presents the benefit to the user in the reception service. A privilege granting system according to any one of (1-1) to (1-4). (1-6) the reward granting system further includes a third reward presentation unit that presents the reward to the user in an application completion notice indicating that the application for the target facility has been completed. A benefit granting system according to any one of (1-1) to (1-5). (1-7) the benefit granting unit grants the benefit to the user who has made an application for the target facility using the reception service, checked in to the target facility, and made a payment to the target store using the payment service; A privilege granting system according to any one of (1-1) to (1-6). (1-8) The application information includes information regarding the length of stay of the user at the target facility, the benefit granting unit grants the benefit to the user who has made an application for the target facility using the reception service and who has made a payment to the target store using the payment service during the stay; A benefit granting system according to any one of (1-1) to (1-7). (1-9) the benefit granting unit grants the user the benefit according to the rank of the target facility. A benefit granting system according to any one of (1-1) to (1-8). (1-10) the benefit granting unit grants the user the benefit related to the target store according to the rank of the target facility; The reward system described in (1-9). (1-11) The reward granting system further includes a questionnaire presentation unit that presents a questionnaire regarding the target facility to the user who has used the target facility in the payment service. A benefit granting system according to any one of (1-1) to (1-10). (1-12) The reward granting system further includes a facility advertisement presenting unit that presents a facility advertisement corresponding to the target facility to the user in the payment service. A benefit granting system according to any one of (1-1) to (1-11). (1-13) The reward system further includes an entry screen control unit that displays an entry screen for accepting entries to a campaign related to the reward in the payment service based on the application information, the reward granting unit grants the reward to the user who has made the entry. A benefit granting system according to any one of (1-1) to (1-12). (1-14) the benefit granting unit grants the user the benefit according to the user's application history in the reception service. A benefit granting system according to any one of (1-1) to (1-13). (1-15) The application information includes information about each of the user who made the application and other users who will use the target facility together with the user, the benefit granting unit grants the benefit to the other user when the other user uses the payment service at the target store; A benefit granting system according to any one of (1-1) to (1-14).

[0222] [4-2. Supplementary notes on the second embodiment] For example, the usage suggestion system of the second embodiment can also be configured as follows. (2-1) an application information acquisition unit that acquires application information regarding an application made by a reception service that accepts applications regarding a predetermined facility; a usage suggestion unit that suggests to a user who has applied for a target facility through the reception service, based on the application information, that the user use the payment service by associating the application with a benefit that is granted when the user makes a payment to a target store through the payment service; and A usage suggestion system including: (2-2) the usage suggestion unit suggests to the user the use of the payment service in association with the benefit, the conditions for which are an application for the target facility in the reception service and the payment at the target store in the administrative district where the target facility is located; The usage suggestion system according to (2-1). (2-3) The usage suggestion system further includes an administrative district advertisement presentation unit that presents an administrative district advertisement related to the administrative district to the user. The usage suggestion system according to (2-2). (2-4) the usage suggestion unit, in the reception service, suggests to the user the use of the payment service in association with the benefit; A usage suggestion system according to any one of (2-1) to (2-3). (2-5) the usage suggestion unit proposes to the user the use of the payment service in association with the benefit in an application completion notice indicating that the application has been completed; A usage suggestion system according to any one of (2-1) to (2-4). (2-6) the usage suggestion unit suggests to the user, when the user checks in to the target facility, the use of the payment service in association with the benefit; A usage suggestion system according to any one of (2-1) to (2-5). (2-7) the usage suggestion unit suggests to the user the use of the payment service in association with the benefit according to the rank of the target facility. A usage suggestion system according to any one of (2-1) to (2-6). (2-8) the usage suggestion unit suggests to the user the use of the payment service in association with the benefit related to the target store according to the rank of the target facility; The usage suggestion system according to (2-7). (2-9) the application information includes information regarding the length of stay for the user at the facility; the usage suggestion unit suggests to the user the use of the payment service in association with the benefit, the conditions for which will be provided being an application for the target facility in the reception service and the payment at the target store during the stay; A usage suggestion system according to any one of (2-1) to (2-8). (2-10) the usage suggestion unit suggests to the user on a screen for checking in to the target facility that the user use the payment service in association with the benefit; A usage suggestion system according to any one of (2-1) to (2-9). (2-11) the usage suggestion unit suggests to the user the use of the payment service in association with the benefit according to the application history of the user in the reception service; The usage suggestion system according to any one of (2-1) to (2-10). (2-12) the application information includes information about the user who made the application and other users who will use the facility together with the user, the usage suggestion unit suggests to the other user the use of the payment service in association with the benefit; A usage suggestion system according to any one of (2-1) to (2-11). (2-13) the usage suggestion unit suggests to the user to use the payment service by presenting a link for downloading a payment app that is an application for the payment service; A usage suggestion system according to any one of (2-1) to (2-12). [Explanation of symbols]

[0223] 1 Reward granting system, 2 Usage suggestion system, 10 Payment server, 11, 21, 31 Control unit, 12, 22, 32 Memory unit, 13, 23, 33 Communication unit, 20 Reception server, 30 User terminal, 34 Operation unit, 35 Display unit, 100 Data storage unit, 101 Application information acquisition unit, 102 Payment information acquisition unit, 103 Reward granting unit, 104 Administrative district advertisement presentation unit, 105 First benefit presentation unit, 106 Questionnaire presentation unit, 107 Facility advertisement presentation unit, 108 Entry screen control unit, 200 Data storage unit, 201 Reception unit, 202 Application information acquisition unit, 203 Usage suggestion unit, 204 Second benefit presentation unit, 205 Third benefit presentation unit, 206 Administrative district advertisement presentation unit, 300 Data storage unit, 301 Operation reception unit, 302 Display control unit, C30 Code, DB1 Payment database, DB2 benefits database, DB3 reception database, SC1 top screen, SC2 completion screen, SC3 top screen, SC4 completion screen, SC5 download screen, L link, M email, N network.

Claims

1. an application information acquisition unit that acquires application information regarding an application made by a reception service that accepts applications regarding a predetermined facility; a usage suggestion unit that suggests to a user who has applied for a target facility through the reception service, based on the application information, that the user use the payment service by associating the application with a benefit that is granted when the user makes a payment to a target store through the payment service; and A usage suggestion system including:

2. the usage suggestion unit suggests to the user the use of the payment service in association with the benefit, the conditions for which are an application for the target facility in the reception service and the payment at the target store in the administrative district where the target facility is located; The usage suggestion system according to claim 1 .

3. The usage suggestion system further includes an administrative district advertisement presentation unit that presents an administrative district advertisement related to the administrative district to the user. The usage suggestion system according to claim 2 .

4. the usage suggestion unit, in the reception service, suggests to the user the use of the payment service in association with the benefit; 4. The usage suggestion system according to claim 1.

5. the usage suggestion unit proposes to the user the use of the payment service in association with the benefit in an application completion notice indicating that the application has been completed; 4. The usage suggestion system according to claim 1.

6. the usage suggestion unit suggests to the user, when the user checks in to the target facility, the use of the payment service in association with the benefit; 4. The usage suggestion system according to claim 1.

7. the usage suggestion unit suggests to the user the use of the payment service in association with the benefit according to the rank of the target facility.

4. The usage suggestion system according to claim 1.

8. the usage suggestion unit suggests to the user the use of the payment service in association with the benefit related to the target store according to the rank of the target facility; The usage suggestion system according to claim 7.

9. the application information includes information regarding the length of stay for the user at the facility; the usage suggestion unit suggests to the user the use of the payment service in association with the benefit, the conditions for which will be provided being an application for the target facility in the reception service and the payment at the target store during the stay; 4. The usage suggestion system according to claim 1.

10. the usage suggestion unit suggests to the user on a screen for checking in to the target facility that the user use the payment service in association with the benefit; 4. The usage suggestion system according to claim 1.

11. the usage suggestion unit suggests to the user the use of the payment service in association with the benefit according to the application history of the user in the reception service; 4. The usage suggestion system according to claim 1.

12. the application information includes information about the user who made the application and other users who will use the facility together with the user, the usage suggestion unit suggests to the other user the use of the payment service in association with the benefit; 4. The usage suggestion system according to claim 1.

13. the usage suggestion unit suggests to the user to use the payment service by presenting a link for downloading a payment app that is an application for the payment service; 4. The usage suggestion system according to claim 1.

14. an application information acquisition step of acquiring application information related to an application made by a reception service that accepts applications related to a predetermined facility; a usage suggestion step of suggesting to a user who has applied for a target facility through the reception service based on the application information, the use of the payment service being associated with a benefit that will be granted when the user applies for the target facility and makes a payment to the target store through the payment service; A usage suggestion method including:

15. an application information acquisition unit that acquires application information regarding an application made by a reception service that accepts applications regarding a predetermined facility; a usage suggestion unit that suggests to a user who has made an application for a target facility through the reception service, based on the application information, to use the payment service by associating the application with a benefit that will be granted when the user makes a payment to the target store through the payment service; A program that allows a computer to function as a

Images