Information processing device, information processing method, and information processing program

Abstract

To properly evaluate a shop according to a user.SOLUTION: An information processing device according to the present application includes an acquisition unit and a calculation unit. The acquisition unit acquires shop information of a shop and the settlement history of a user. The calculation unit calculates a shop score regarding a shop for the user on the basis of the shop information and the settlement history of the user.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to an information processing device, an information processing method, and an information processing program. [Background technology]

[0002] Conventionally, store search techniques have been proposed that enable users to search for stores that are highly rated for a particular dish. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent No. 6052690 Summary of the Invention [Problem to be solved by the invention]

[0004] However, the above-mentioned conventional techniques do not necessarily enable evaluation of stores according to the user.

[0005] The above-mentioned conventional technology merely describes a configuration for controlling the display of store information about stores that have received high ratings for a particular dish to users on a preferential basis, but does not necessarily provide store ratings that are tailored to the user.

[0006] The present application has been made in consideration of the above, and has an object to provide an information processing device, an information processing method, and an information processing program that can appropriately evaluate stores depending on the user. [Means for solving the problem]

[0007] The information processing device according to the present application includes an acquisition unit and a calculation unit. The acquisition unit acquires store information related to a store and a payment history of a user. The calculation unit calculates a store score related to the store for the user based on the store information and the payment history of the user. Effect of the Invention

[0008] According to one aspect of the embodiment, it is possible to provide an effect of allowing stores to be appropriately evaluated according to users. [Brief description of the drawings]

[0009] [Figure 1] FIG. 1 is a diagram illustrating an example of information processing according to an embodiment. [Diagram 2] FIG. 2 is a diagram illustrating an example of the configuration of the payment server according to the embodiment. [Diagram 3] FIG. 3 is a diagram illustrating an example of store management information according to the embodiment. [Figure 4] FIG. 4 is a diagram illustrating an example of payment history information according to the embodiment. [Diagram 5] FIG. 5 is a diagram illustrating an example of evaluation information according to the embodiment. [Figure 6] FIG. 6 is a diagram illustrating an example of the configuration of a user terminal according to the embodiment. [Figure 7] FIG. 7 is a diagram illustrating an example of the configuration of a service providing device according to the embodiment. [Figure 8] FIG. 8 is a flowchart illustrating an example of a procedure of information processing according to the embodiment. [Figure 9] FIG. 9 is a hardware configuration diagram illustrating an example of a computer that realizes the functions of the payment server. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] Hereinafter, the information processing device, the information processing method, and the information processing program according to the present application will be described in detail with reference to the drawings. Note that the information processing device, the information processing method, and the information processing program according to the present application are not limited to the embodiments. In addition, the same parts in the following embodiments are given the same reference numerals, and duplicated explanations will be omitted.

[0011] 1. Embodiment The information processing realized by the information processing device etc. of the present embodiment will be described with reference to Fig. 1. Fig. 1 is a diagram showing an example of the information processing according to the embodiment. Note that in Fig. 1, the information processing etc. according to the embodiment is realized by an information processing system 1 including a payment server 10 which is an example of the information processing device according to the present embodiment.

[0012] As shown in Fig. 1, the information processing system 1 according to the embodiment includes a payment server 10, a user terminal 100, and a service providing device 200. The payment server 10, the user terminal 100, and the service providing device 200 are connected to each other via a network N (see Fig. 2, for example) in a wired or wireless manner so as to be able to communicate with each other. The network N is, for example, a Wide Area Network (WAN) such as the Internet. Note that the information processing system 1 shown in Fig. 1 may include a plurality of payment servers 10, a plurality of user terminals 100, and a plurality of service providing devices 200.

[0013] The payment server 10 shown in FIG. 1 is an information processing device that executes at least a part of the information processing according to the embodiment, and is realized by a server device, a cloud system, or the like. For example, the payment server 10 provides an electronic payment service related to electronic payment using a user terminal 100. For example, the payment server 10 manages the accounts of providers (businesses) of transaction objects and users U1 to whom transaction objects are provided, and realizes various payments by transferring electronic money between accounts in accordance with a payment request from user U1. Note that electronic money may be, for example, points or currency used independently by various companies, or may be electronically tradable currency provided by a country, such as Japanese yen or dollars.

[0014] The payment server 10 also manages and holds, for example, evaluations of affiliated stores (hereinafter also simply referred to as stores) affiliated with the electronic payment service. This evaluation is an evaluation made by the user U1 of the store where the user U1 made a payment. The payment server 10 manages and holds the evaluation of the store in association with the user U1 who made the evaluation.

[0015] In addition, the payment server 10 provides a store evaluation service using the evaluations stored therein. For example, the payment server 10 provides a store evaluation service that performs evaluation for each store according to the user U1 using the evaluations stored therein. For example, the payment server 10 performs store evaluation for the user U1 in response to a request from the service providing device 200.

[0016] For example, the payment server 10 has a payment management unit that manages the electronic payment service (in other words, controls processing related to the electronic payment service) and a review management unit that manages the store evaluation service (in other words, controls processing related to the store evaluation service).

[0017] The user terminal 100 shown in Fig. 1 is an information processing device used by a user U1. The user terminal 100 is realized, for example, by a smartphone, a tablet terminal, a notebook PC (Personal Computer), a desktop PC, a mobile phone, a PDA (Personal Digital Assistant), or the like. The user terminal 100 displays information distributed by at least one of the payment server 10 and the service providing device 200 using a web browser or an application. Note that the example shown in Fig. 1 shows a case where the user terminal 100 is a smartphone.

[0018] The service providing device 200 shown in FIG. 1 is an information processing device that provides store information to user U1, and is realized by, for example, a server device or a cloud system. The service providing device 200 holds user information about user U1 and store information about stores. As user information, the service providing device 200 holds, for example, attribute information of user U1 and user identification information that identifies user U1. As store information, the service providing device 200 holds, for example, store identification information that identifies a store. The service providing device 200 can acquire the user information and store information from user U1 via the user terminal 100, for example.

[0019] When at least one of the user terminal 100 and the service providing device 200 receives control information for implementing a predetermined information processing from the payment server 10, the control information implements the information processing according to the control information. Here, the control information may be described in, for example, a script language such as JavaScript (registered trademark), a style sheet language such as CSS (Cascading Style Sheets), a programming language such as Java (registered trademark), or a markup language such as HTML (HyperText Markup Language). The predetermined application itself delivered from the payment server 10 may be regarded as the control information.

[0020] 1-1. Payment using the user terminal 100 Here, prior to the information processing executed by the information processing system 1, an example of payment (electronic payment) using the user terminal 100 will be described. In the following description, an example will be described in which a user U1 makes a payment using the user terminal 100 using a two-dimensional code (QR code (registered trademark)) placed in store A, which indicates store identification information that identifies store A, but the embodiment is not limited to this. The example of payment described below is also applicable to a case in which an arbitrary user makes a payment at an arbitrary store using an arbitrary user terminal 100. In addition, the store identification information may be not only a QR code (registered trademark), but also a barcode, a predetermined mark, a number, etc.

[0021] For example, when user U1 makes a payment for the use or purchase of a payment object (transaction object) such as various goods or services at store A, user U1 launches a payment app pre-installed on user terminal 100. User U1 then photographs the store identification information installed in store A via the payment app. In such a case, user terminal 100 displays a screen for inputting the price of the payment object and accepts input of the payment amount from user U1 or a clerk at store A. User terminal 100 then transmits to payment server 10 payment information indicating user identification information that identifies user U1, store identification information (or information indicated by the store identification information, i.e., information indicating store A (e.g., store ID)), and the payment amount.

[0022] In such a case, the payment server 10 transfers electronic money in the amount indicated by the payment amount from the account of user U1 indicated by the user identification information to the account of store A indicated by the store identification information. Then, the payment server 10 transmits a notification that the payment has been completed to the user terminal 100. In such a case, the user terminal 100 notifies that the payment has been made with electronic money by outputting a screen or a predetermined sound indicating that the payment has been completed.

[0023] It should be noted that the payment using the user terminal 100 is not limited to the above-mentioned process. For example, the payment using the user terminal 100 may be made using a store terminal installed in store A. For example, the user terminal 100 displays user identification information for identifying the user U1 on a screen. In such a case, the store terminal installed in store A reads the user identification information displayed on the user terminal 100, and transmits payment information indicating the user identification information (or information indicated by the user identification information, i.e., information indicating user U1 (e.g., user ID)), the payment amount, and information identifying store A to the payment server 10. In such a case, the payment server 10 transfers electronic money in an amount indicated by the payment amount from the account of user U1 indicated by the user identification information to the account of store A, and may notify the store terminal of store A or the user terminal 100 of the completion of the payment by outputting a screen or a predetermined sound indicating that the payment has been completed.

[0024] Furthermore, the payment using the user terminal 100 may not only be a process of transferring electronic money from an account to which user U1 has previously charged electronic money to the account of store A, but may also be, for example, a payment using a credit card previously registered by user U1. In such a case, for example, the user terminal 100 may transfer electronic money of the payment amount to the account of store A, and may also bill the management company of user U1's credit card for the payment amount.

[0025] 1-2. Information Processing According to the Embodiment Conventionally, store search techniques have been proposed that can search for stores that have received high ratings for a specific dish, but such techniques do not necessarily provide store ratings that are appropriate for the user.

[0026] For example, conventional technologies do not necessarily search for stores that match the user's preferences (preferences), such as store atmosphere, genre, etc. Furthermore, conventional technologies do not necessarily take into consideration how the user evaluates the store selected by the user, that is, whether the store matches the user's preferences.

[0027] Therefore, the information processing system 1 executes information processing according to the embodiment. This information processing is mainly executed by the payment server 10. In the following description, an example is shown in which the user terminal 100 is used by the user U1, and the service providing device 200 acquires an evaluation of a store specified by the user U1 from the payment server 10 and presents it to the user U1.

[0028] As shown in FIG. 1, the service providing device 200 acquires user-specified information and store-specified information from the user terminal 100 (step S1).

[0029] The user-specified information is, for example, information specified by user U1 and includes information about user U1. The user-specified information includes, for example, user identification information and attribute information about user U1. The attribute information about user U1 includes, for example, information about age, gender, preferences, and place of residence of user U1. The user identification information is information linked to a payment made by user U1.

[0030] The user terminal 100 generates user-specified information based on information input by the user U1, for example, and notifies the service providing device 200. The user terminal 100 may acquire the user-specified information from the user U1 in advance, or may acquire the user-specified information from the user U1 when evaluating a store. For example, the user terminal 100 may acquire the user-specified information by the user U1 logging in to learn about a service provided by the service providing device 200.

[0031] The store designation information is, for example, information designated by user U1, and includes information about the store for which a rating is to be obtained. The store designation information includes, for example, store identification information. The store identification information may be a store ID, or may be the name, address, or telephone number of the store. Alternatively, the store designation information may be information about the area, the genre of the store, or the like.

[0032] If the store designation information acquired from the user terminal 100 is information that is not store identification information (e.g., store name, address, telephone number, etc.), the service providing device 200 may acquire store identification information from the payment server 10 based on that information.

[0033] For example, the service providing device 200 transmits store designation information to the payment server 10 via an API. This API is, for example, an API for acquiring store identification information. The payment server 10 searches for a store that matches the store designation information acquired via the API, for example, from store management information related to the store. The store management information includes information related to the store, such as store identification information, store name, address, and telephone number.

[0034] The payment server 10 notifies the service providing device 200 of the search result and the store identification information of the store that matches the store designation information via the API.

[0035] In addition, when the store designation information is not information designating a specific store, such as an area or a genre, the service providing device 200 acquires at least one store identification information corresponding to the store designation information. For example, when the store designation information is an area, the service providing device 200 acquires store identification information of a store included in the area. In this case, too, the service providing device 200 can acquire store identification information of a store corresponding to the store designation information from the payment server 10 via an API.

[0036] Next, the payment server 10 acquires the user attribute information, the user identification information, and the store identification information from the service providing device 200 (step S2).

[0037] The service providing device 200 transmits user attribute information and user identification information to the payment server 10 based on the user designation information acquired from the user U1. In addition, the service providing device 200 transmits store identification information to the payment server 10 based on the store designation information. The service providing device 200 transmits these pieces of information to the payment server 10 via, for example, an API.

[0038] Next, the payment server 10 acquires the payment history of the user U1 from the user identification information (step S3).

[0039] The payment server 10 holds payment history information including past payment information (payment history) for each user. Based on the user identification information acquired from the service providing device 200 via the API, the payment server 10 acquires the payment history of the user U1 corresponding to the user identification information.

[0040] The settlement server 10 extracts store evaluations of other users who have similar user attribute information and usage histories (step S4).

[0041] For example, the payment server 10 extracts other users (hereinafter also referred to as similar users) whose user attribute information and user history are similar to that of the user U1. Next, the payment server 10 extracts evaluations of stores (hereinafter also referred to as evaluated stores) that match the store identification information from among the store evaluations made by other users.

[0042] Alternatively, the payment server 10 may first extract store evaluations of the store to be evaluated. In this case, the payment server 10 extracts store evaluations made by similar users from the extracted store evaluations. Alternatively, the payment server 10 may obtain store evaluations of the store to be evaluated made by similar users using store identification information, user attribute information, and user history.

[0043] The payment server 10 calculates the store score based on the store ratings by other users (step S5).

[0044] For example, the payment server 10 calculates the average value of the evaluations of the evaluated stores performed by the similar users as the store score. Alternatively, the payment server 10 may calculate the store score by weighting according to the similarity of the similar users (similarity between the user U1 and the similar users).

[0045] The payment server 10 provides the calculated shop score to the service providing device 200 (step S6).

[0046] The payment server 10 provides the shop score to the service providing device 200 by using, for example, an API that has acquired the user attribute information, etc. Alternatively, the payment server 10 may provide the shop score to the service providing device 200 by using an API different from the API that has acquired the user attribute information, etc.

[0047] The service providing device 200 provides the acquired shop score to the user U1 (step S7).

[0048] The service providing device 200 provides the shop score to the user U1, for example, by transmitting the shop score to the user terminal 100 and displaying it on the display of the user terminal 100.

[0049] For example, when the service providing device 200 requests the payment server 10 to calculate store scores of a plurality of evaluated stores, the service providing device 200 may provide the store scores of the plurality of evaluated stores to the user U1 in a ranking format.

[0050] For example, when user U1 requests acquisition of evaluation results by specifying an area or genre rather than an evaluation of a specific store, the service providing device 200 may request the payment server 10 to calculate store scores for one or more stores included in the area or genre as evaluation target stores. In this case, the service providing device 200 obtains store scores for one or more evaluation target stores from the payment server 10. The service providing device 200 provides information on the evaluation target stores and the store scores to user U1, for example, in descending order of store score.

[0051] As described above, the payment server 10 according to the embodiment acquires the store evaluation (an example of store information) for the evaluated store (an example of a store) and the payment history of the user U1 (an example of a user). The payment server 10 calculates the store score for the evaluated store for the user U1 based on the store evaluation and the payment history of the user U1.

[0052] This allows the payment server 10 according to the embodiment to perform store evaluations according to user U1. User U1 can check the store score that has been customized for him / her. Furthermore, the payment server 10 calculates the store score using the evaluations of similar users who have similar usage histories. Therefore, user U1 can check the evaluations of similar users who actually used the store (made a payment at the store). In this way, the payment server 10 can calculate a more reliable store score and present it to user U1.

[0053] When the service providing device 200 presents the store score to the user U1, the service providing device 200 may present to the user U1, together with the store score, guarantee information (e.g., a guarantee mark) indicating that the store score is an evaluation by a similar user who actually used the payment service at that store. For example, the service providing device 200 may present to the user U1 guarantee information indicating that the store score is calculated by the payment server 10 that provides the payment service. In other words, when the payment server 10 provides the store score via a predetermined API, the payment server 10 may permit the service providing device 200 to present the guarantee information to the user U1.

[0054] This allows user U1 to confirm that the presented shop score has a high degree of reliability.

[0055] In addition, although the case where user U1 obtains a store evaluation suited to him / her has been described here, the entity that obtains the store evaluation is not limited to user U1. For example, store A may obtain an evaluation of its own store. In this case, for example, store A requests the service providing device 200 to obtain a store evaluation by specifying its own store and user attribute information (for example, age, address, preferences, etc.).

[0056] The service providing device 200 requests the payment server 10 to calculate a store score by specifying the user attribute information and the store identification information. In response to the request, the payment server 10 extracts the evaluation of the evaluation target store based on the payment history of a user similar to the user attribute information, and calculates the store score. When the service providing device 200 obtains the store score from the payment server 10, it provides the store score to store A.

[0057] This allows store A to narrow down its target and check the evaluation of its store. Store A can check, for example, what kind of evaluation it has received from men in their 30s. In this way, the information processing according to this embodiment can be used as a customer analysis tool by being utilized by the store.

[0058] Instead of user attribute information, store A may specify a payment to request calculation of the store score. In this case, the payment server 10 calculates the store score based on, for example, store evaluations made by similar users who are similar to the user who made the specified payment.

[0059] Alternatively, store A may request calculation of the store score by specifying a product sold or a service provided by store A instead of the user attribute information. In this case, the payment server 10 calculates the store score based on, for example, store evaluations made by a user who made a payment for the specified product or service and similar users similar to the user.

[0060] In this embodiment, the payment server 10 provides the store score, but the store evaluation provided by the payment server 10 is not limited to the store score. For example, the payment server 10 may provide evaluation comments and evaluation values ​​by similar evaluators.

[0061] In addition, although the service providing device 200 requests the payment server 10 to provide a store score by specifying a store here, the service providing device 200 may request the payment server 10 to provide a store score without specifying a store. In this case, the service providing device 200 notifies the payment server 10 of, for example, user identification information and user attribute information. The payment server 10 calculates a store score for each store based on, for example, the payment history of user U1 and the evaluation of a similar user who is similar to the user attribute information. The stores to be evaluated at this time may be selected from stores included in the payment history of the similar users, for example.

[0062] In addition, although it has been assumed here that the terminal where user U1 makes electronic payment and the terminal where the store score is presented to user U1 are the same user terminal 100, the terminal where user U1 makes electronic payment and the terminal where the store score is presented may be different terminals. User U1 only needs to notify the service providing device 200 of user-specified information including user identification information for electronic payment, and the type of terminal used by user U1 does not matter.

[0063] [2. Payment Server Configuration] Next, the configuration of the payment server 10 will be described with reference to Fig. 2. Fig. 2 is a diagram showing an example of the configuration of the payment server according to the embodiment. As shown in Fig. 2, the payment server 10 includes a communication unit 20, a storage unit 30, and a control unit 40.

[0064] (Regarding communication unit 20) The communication unit 20 is realized by, for example, a network interface card (NIC) etc. The communication unit 20 is connected to the network N by wire or wirelessly, and transmits and receives information to and from the user terminal 100, the service providing device 200, etc.

[0065] (Regarding the storage unit 30) The storage unit 30 is realized by, for example, a semiconductor memory element such as a random access memory (RAM) or a flash memory, or a storage device such as a hard disk or an optical disk. As shown in FIG. 2, the storage unit 30 has a store information database 31, a payment information database 32, and a review information database 33.

[0066] (About store information database 31) The store information database 31 stores various types of information related to stores. For example, the store information database 31 stores store management information.

[0067] Fig. 3 is a diagram illustrating an example of store management information according to an embodiment. In the example of Fig. 3, the store management information includes information related to "store ID", "store name", "location", "telephone number", and "category".

[0068] "Store ID" is an example of store identification information that identifies a store. "Store name" is information indicating the name of the store. "Location" is information indicating the location information of the store (e.g., address). "Telephone number" is information indicating a telephone number as a contact number for the store. "Category" is information indicating a store category. Store category is information for classifying stores, for example, by business type or by products / services offered. A "category" may include multiple store categories. Alternatively, "categories" may be organized hierarchically. For example, "subcategories" indicating products offered, such as "Chinese" or "Italian," may be set below a "category" indicating a business type, such as "restaurant."

[0069] That is, in the example of Figure 3, the store information database 31 stores store management information for a store identified by the store ID "SID#1", whose location is "Location #1", whose telephone number is "Telephone Number #1", and whose category is "Category #1".

[0070] (Regarding payment information database 32) The payment information database 32 stores various information related to payments. For example, the payment information database 32 stores payment history information.

[0071] Fig. 4 is a diagram showing an example of payment history information according to an embodiment. In the example of Fig. 4, the payment history information includes information on "user ID", "payment ID", "payment date and time", "payment store", "payment target", and "payment amount".

[0072] "User ID" is an example of user identification information that identifies a user. "Payment ID" is identification information that identifies an electronic payment. "Payment date and time" is information indicating the date and time when the electronic payment was made. "Payment store" is information indicating the store where the electronic payment was made, and includes, for example, a store ID. "Payment item" is information indicating the object of the electronic payment, such as a product. "Payment amount" is information indicating the amount of the payment.

[0073] That is, the example in Figure 4 shows a payment with payment ID "PID#1" in which a user identified by user ID "UID#1" paid "payment amount #1" for "payment item #1" at a store identified by store ID "SID#1" on "XX / YY / ZZ TT:MM."

[0074] (About Evaluation Information Database 33) The evaluation information database stores various information related to evaluations made by users to stores. For example, the evaluation information database 33 stores evaluation information.

[0075] Fig. 5 is a diagram illustrating an example of evaluation information according to an embodiment. In the example of Fig. 5, the evaluation information includes information related to "user ID", "evaluated store", "payment ID", "evaluation value", and "evaluation comment".

[0076] "User ID" is an example of user identification information that identifies the user who made the rating. "Rated store" is information that indicates the store that was the subject of the rating, and includes, for example, the store ID. "Payment ID" is identification information that identifies the payment that triggered the user to make the rating. "Rating value" is information that indicates the result of the rating made by the user in the form of a score. "Rating comment" is information that indicates the result of the rating made by the user in writing, etc.

[0077] That is, the example in Figure 5 shows a case in which a user identified by user ID "UID#1" gave an evaluation value of "3" and "evaluation comment #1" at the time of payment identified by payment ID "PID#1" at a store identified by store ID "SID#1."

[0078] (Regarding the control unit 40) Returning to FIG. 2, the control unit 40 is a controller, and is realized, for example, by a CPU (Central Processing Unit) or an MPU (Micro Processing Unit) executing various programs stored in a storage device inside the payment server 10 using a RAM as a working area. The control unit 40 is also a controller, and is realized, for example, by an integrated circuit such as an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array). As shown in FIG. 2, the control unit 40 according to the embodiment has an acquisition unit 41, a calculation unit 42, a provision unit 43, a payment processing unit 44, and a reception unit 45, and realizes or executes the functions and actions of information processing described below.

[0079] (Regarding acquisition unit 41) The acquisition unit 41 acquires various information from the storage unit 30 and the service providing device 200. The acquisition unit 41 acquires at least one of user attribute information, user identification information, and store identification information from the service providing device 200 via the communication unit 20.

[0080] The acquisition unit 41 acquires the payment history of a user identified by the user identification information from the storage unit 30. Furthermore, the acquisition unit 41 acquires information on similar users who are similar to the user based on the user's payment history and user attribute information from the storage unit 30. The acquisition unit 41 acquires evaluation information on store evaluations of stores made by the similar users from the information on the similar users.

[0081] (Regarding the calculation unit 42) The calculation unit 42 calculates a store score of the store identified by the store identification information (evaluated store) based on the evaluation information acquired by the acquisition unit 41. The calculation unit 42 calculates, for example, the average value of the evaluation values ​​by similar users as the store score. Alternatively, the calculation unit 42 may calculate the store score by weighting the evaluation values ​​according to the similarity between the similar users and the user.

[0082] (About provider 43) The providing unit 43 provides the shop score calculated by the calculation unit 42 to the service providing device 200 via the communication unit 20. The providing unit 43 may provide the evaluation comments made by similar users to the service providing device 200 together with the shop score.

[0083] The providing unit 43 may provide information (guarantee information) indicating that the store score is based on evaluations by similar users who actually made payments at the evaluated store together with the store score to the service providing device 200. The guarantee information is, for example, information indicating that the store score is highly reliable.

[0084] The service providing device 200 that has received the guarantee information may present the shop score to the user with, for example, a guarantee mark, which allows the user to recognize that the shop score has a high degree of reliability.

[0085] (Regarding the payment processing unit 44) The payment processing unit 44 executes payment processing according to the payment information accepted by the acceptance unit 45 described later. For example, the payment processing unit 44 transfers electronic money in an amount indicated by the payment amount from the account of the user indicated by the user ID to the account of the store indicated by the store ID.

[0086] (Regarding Reception Section 45) The reception unit 45 receives payment information related to payment from a user to a business operator. For example, the reception unit 45 receives from the user terminal 100 payment information indicating user identification information for identifying a user, store identification information photographed via a payment app, and a payment amount input by the user or a store clerk.

[0087] [3. User terminal configuration] Next, the configuration of the user terminal 100 according to the embodiment will be described with reference to Fig. 6. Fig. 6 is a diagram showing an example of the configuration of the user terminal 100 according to the embodiment. As shown in Fig. 6, the user terminal 100 has a communication unit 110, an input unit 120, an output unit 130, and a control unit 140.

[0088] (Regarding communication unit 110) The communication unit 110 is realized by, for example, a NIC, etc. The communication unit 110 is connected to a predetermined network N by wire or wirelessly, and transmits and receives information to and from the payment server 10, etc., via the predetermined network N.

[0089] (Regarding input unit 120) The input unit 120 accepts various operations from the user U1. For example, the input unit 120 may accept various operations from the user U1 via a display surface using a touch panel function. The input unit 120 may also accept various operations from buttons provided on the user terminal 100 or a keyboard or mouse connected to the user terminal 100.

[0090] (Regarding the output unit 130) The output unit 130 is a display screen of a tablet terminal or the like realized by, for example, a liquid crystal display or an organic EL (Electro-Luminescence) display, and is a display device for displaying various information. For example, the output unit 130 displays information acquired from the payment server 10.

[0091] (Regarding the control unit 140) The control unit 140 is, for example, a controller, and is realized by a CPU, an MPU, or the like executing various programs stored in a storage device inside the user terminal 100 using a RAM as a working area. For example, the various programs include application programs installed in the user terminal 100. For example, the various programs include application programs that display information obtained from the payment server 10. The control unit 140 is also realized by an integrated circuit, for example, an ASIC, an FPGA, or the like.

[0092] As shown in FIG. 6, the control unit 140 has a receiving unit 141 and a transmitting unit 142, and realizes or executes the information processing operations described below.

[0093] (Regarding the receiving unit 141) The receiving unit 141 receives various information. The receiving unit 141 receives various information from an external information processing device. The receiving unit 141 receives various information from other information processing devices such as the payment server 10 and the service providing device 200. For example, the receiving unit 141 receives identification information indicating the account of the user U1 transmitted in response to a request for issuing identification information.

[0094] (Regarding the transmitting unit 142) The transmission unit 142 provides various information to an external information processing device. The transmission unit 142 transmits various information to an external information processing device. The transmission unit 142 transmits various information to other information processing devices such as the payment server 10 and the service providing device 200. For example, the transmission unit 142 transmits a request for issuing identification information that can be used for payment at a specified location in response to an operation from the user U1.

[0095] 4. Configuration of the service providing device Next, a configuration of the service providing device 200 according to the embodiment will be described with reference to Fig. 7. Fig. 7 is a diagram showing an example of the configuration of the service providing device 200 according to the embodiment. As shown in Fig. 7, the service providing device 200 has a communication unit 210, a storage unit 220, and a control unit 240.

[0096] (Regarding communication unit 210) The communication unit 210 is realized by, for example, a NIC, etc. The communication unit 210 is connected to a predetermined network N by wire or wirelessly, and transmits and receives information to and from the payment server 10, etc., via the predetermined network N.

[0097] (Regarding the storage unit 220) The storage unit 220 is realized by, for example, a semiconductor memory element such as a RAM or a flash memory, or a storage device such as a hard disk or an optical disk.

[0098] (Regarding the control unit 240) The control unit 240 is, for example, a controller, and is realized by a CPU, an MPU, or the like executing various programs stored in a storage device inside the service providing device 200 using a RAM as a working area. For example, the various programs include application programs installed in the service providing device 200. For example, the various programs include application programs that display information acquired from the payment server 10. The control unit 240 is also realized by an integrated circuit, for example, an ASIC, an FPGA, or the like.

[0099] As shown in FIG. 7, the control unit 240 has a receiving unit 241 and a transmitting unit 242, and realizes or executes the information processing operations described below.

[0100] (Receiving unit 241) The receiving unit 241 receives various information. The receiving unit 241 receives various information from an external information processing device. The receiving unit 241 receives various information from other information processing devices such as the payment server 10 and the user terminal 100. For example, when calculating the shop score, the receiving unit 241 receives information (e.g., user-specified information and shop-specified information) for notifying the payment server 10 of a request for calculating the shop score from the user terminal 100. Also, for example, the receiving unit 241 receives the shop score from the payment server 10.

[0101] (Transmitter 242) The transmission unit 242 provides various information to an external information processing device. The transmission unit 242 transmits various information to an external information processing device. The transmission unit 242 transmits various information to other information processing devices such as the payment server 10 and the user terminal 100. For example, the transmission unit 242 transmits a store score calculation request to the payment server 10. In addition, the transmission unit 242 transmits the store score received from the payment server 10 to the user terminal 100.

[0102] [5. Information processing flow] The procedure of information processing of the payment server 10 according to the embodiment will be described with reference to Fig. 8. Fig. 8 is a flowchart showing an example of the procedure of information processing according to the embodiment.

[0103] 8, the payment server 10 receives user attribute information, user identification information, and store identification information (step S101). The payment server 10 acquires the payment history of the user identified by the user identification information (step S102).

[0104] The payment server 10 extracts similar users based on the payment history and the user attributes (step S103). The payment server 10 extracts evaluations made by similar users from evaluations of the store identified by the store identification information (step S104).

[0105] The payment server 10 calculates a shop score based on the evaluations made by the similar users (step S105). The payment server 10 notifies the calculated shop score to the service providing device 200 (step S106).

[0106] 6. Modifications The above-described embodiment is merely an example, and various modifications and applications are possible.

[0107] [6-1. User Attribute Information] In the above embodiment, the user attribute information is, for example, age, address, preferences, etc., but the user attribute information is not limited to this. For example, the user attribute information may include usage time information indicating the time period when the user U1 plans to use the store (for example, lunch time, dinner time, morning, afternoon, etc.), usage purpose information indicating the purpose of using the store, etc.

[0108] 6-2. Information Acquired by Acquisition Unit 41 In the above embodiment, the acquisition unit 41 of the payment server 10 acquires at least one of the user attribute information, the user identification information, and the store identification information, but the information acquired by the acquisition unit 41 is not limited to this. For example, the acquisition unit 41 may acquire information (hereinafter, companion information) about a person (hereinafter, also referred to as a companion) who is scheduled to use the store together with the user U1.

[0109] For example, if the accompanying person is a user who uses the payment service provided by the payment server 10, the accompanying person is also assigned a user identification number. In this case, the payment server 10 acquires the user identification information of the accompanying person (for example, the above-mentioned user ID), for example, via the service providing device 200. Hereinafter, the user identification information of the accompanying person is also referred to as accompanying person identification information when it is to be distinguished from the user identification information of the user U1.

[0110] The service providing device 200 acquires accompanying person identification information from the user U1. For example, the service providing device 200 presents to the user U1 a list of users who have exchanged money with the user U1 via a payment service as accompanying person candidates. For example, when the user U1 selects a store or the like, the service providing device 200 presents accompanying person candidates to the user U1.

[0111] Assume that the user U1 selects one or more companions from the list of companion candidates presented by the service providing device 200. In this case, the service providing device 200 notifies the payment server 10 of the companion identification numbers of the companions selected by the user U1, together with at least one of the user attribute information, the user identification information, and the store identification information.

[0112] The acquisition unit 41 of the payment server 10 acquires the payment history of the accompanying person from the accompanying person identification number. The payment server 10 extracts other users who have a payment history similar to that of the accompanying person (hereinafter, also referred to as "similar accompanying users"). The acquisition unit 41 of the payment server 10 extracts the evaluations of the similar accompanying users for the evaluated store.

[0113] The calculation unit 42 of the payment server 10 calculates the store score based on the evaluations of the accompanying similar users and the evaluations of the similar users. For example, the calculation unit 42 determines the total (or average) of the evaluation values ​​included in the evaluations of the accompanying similar users and the evaluations of the similar users as the store score of the evaluated store.

[0114] Alternatively, the calculation unit 42 may determine the store score of the evaluated store to be the total (or average) of the first store score calculated based on the evaluation of the accompanying similar users and the second store score calculated based on the evaluation of the similar users. In this case, the calculation unit 42 may calculate the store score by weighting the first store score and the second store score.

[0115] The payment server 10 presents the calculated shop score to the user U1 via the service providing device 200.

[0116] Here, the payment server 10 extracts accompanying-similar users based on accompanying person identification information, but the information used by the payment server 10 to extract accompanying-similar users is not limited to accompanying person identification information. For example, the payment server 10 may extract accompanying-similar users using attribute information (hereinafter also referred to as accompanying person attribute information) of a user (accompanying person) identified by accompanying person identification information.

[0117] The accompanying person attribute information is information indicating the attributes of the accompanying person (e.g., age, address, preferences, etc.). When the memory unit 30 of the payment server 10 stores the accompanying person attribute information in association with the accompanying person identification information, the acquisition unit 41 acquires the accompanying person attribute information by using the accompanying person identification information. Alternatively, the acquisition unit 41 may acquire the accompanying person attribute information from the accompanying person terminal (not shown) by making an inquiry to the accompanying person terminal used by the accompanying person.

[0118] Alternatively, the acquisition unit 41 may acquire the accompanying person attribute information from the user terminal 100 via the service providing device 200. In this case, the user terminal 100 acquires the accompanying person attribute information based on information input by the user U1 (e.g., the age and gender of the accompanying person).

[0119] The payment server 10 does not present the accompanying person attribute information held by the payment server 10 or the accompanying person attribute information acquired from the accompanying person to the user U1. This allows the payment server 10 to protect the privacy of the accompanying person.

[0120] Alternatively, the payment server 10 may present at least a part of the companion attribute information to the user U1 on the condition of consent from the companion. For example, the companion may agree to the disclosure (presentation to the user) of the companion attribute information by limiting the scope of disclosure of the companion attribute information. For example, the companion may agree to the disclosure of the companion attribute information by limiting the content, such as disclosing information about allergies and inedible ingredients, but not about hobbies, etc.

[0121] In addition, for example, it may be possible to set whether or not to disclose information or the scope of disclosure on a user-by-user (or on a group basis that includes a user), such as disclosing information to accompanying users to user U1 but not to user U2.

[0122] In addition, for example, the accompanying person may be allowed to specify a deadline for disclosure. For example, the accompanying person may be allowed to specify a period for disclosure, such as "disclose this time only" or "disclose for a specified period" such as one week.

[0123] The payment server 10 may also receive a disclosure statement from the accompanying person to disclose at least a part of the accompanying person attribute information. In this case, the payment server 10 discloses the accompanying person attribute information for which the disclosure statement has been received to the user U1, and calculates the store score by increasing the weighting of the accompanying person attribute information to be disclosed. The accompanying person may also make a disclosure statement by limiting the content and period of the accompanying person attribute information.

[0124] In this embodiment, the payment server 10 calculates the store score of the evaluated store. However, the payment server 10 may present stores with high store scores to the user U1 as, for example, recommended stores.

[0125] For example, the payment server 10 calculates store scores of multiple evaluated stores and presents a predetermined number of stores in descending order of score as recommended stores to the user U1. Alternatively, the payment server 10 may present to the user U1, among multiple evaluated stores, stores with scores equal to or greater than a predetermined score as recommended stores.

[0126] Alternatively, the payment server 10 may calculate store scores for multiple first-rated stores based on the evaluations of similar users, and may calculate store scores for multiple second-rated stores based on the evaluations of accompanying similar users. In this case, the payment server 10 may present to user U1, for example, stores whose store scores are equal to or greater than a predetermined score and that are included in both the first-rated stores and the second-rated stores as recommended stores. In other words, the payment server 10 may present to user U1, as recommended stores, stores that are highly rated by both similar users and accompanying similar users.

[0127] For example, if user U1 selects multiple companions, the payment server 10 may calculate the store score by weighting the companions using different weights. For example, the payment server 10 may calculate the store score so that the evaluation by similar users of the companion who is the main character of the gathering (for example, if the purpose of using the store is a birthday party, the companion whose birthday is close to the store use date) is largely reflected in the store score.

[0128] As described above, the payment server 10 acquires the information of the accompanying person and calculates the shop score, so that the payment server 10 can calculate the shop score according to the user U1 and the accompanying person.

[0129] Here, it is assumed that user U1 selects a companion from a list of companion candidates, but the method of selecting a companion by user U1 is not limited to this. User U1 may select a companion by directly notifying the service providing device 200 of user identification information. Alternatively, user U1 may select a companion by inputting part of the companion's attributes (e.g., name, etc.).

[0130] [6-3. Payment History] In the above embodiment, the payment server 10 extracts similar users based on the payment history of the user U1, but the payment server 10 may use the payment history of the user U1 for purposes other than the extraction of similar users. For example, the payment server 10 may modify the store score using the payment history.

[0131] For example, the payment server 10 modifies the store score according to payments made consecutively within a certain period of time. More specifically, the payment server 10 modifies the store score according to the attributes of the stores where payments have been made consecutively within a certain period of time and the timing (time) of the payments.

[0132] For example, if the user U1 often makes a payment at a karaoke bar after making a payment at a pub, the payment server 10 modifies the store score so that the karaoke store score is larger than the store scores of other types of businesses. For example, the payment server 10 weights the store score calculation so that the weight of the business type (e.g., karaoke) is larger.

[0133] Such correction of the store score is useful, for example, when the user U1 searches for a store after making a payment at an izakaya. Alternatively, such correction of the store score is useful when a recommended store is presented to the user U1 immediately after the user U1 makes a payment at an izakaya.

[0134] In this way, when the payment server 10 modifies the shop score according to the order (flow) of payments made within a certain period of time, the payment server 10 may modify the shop score according to the accompanying person. The accompanying person may be selected by the user U1. Alternatively, the payment server 10 may set another user who exchanged money with the user U1 at the time of payment as the accompanying person.

[0135] Also, for example, the payment server 10 may modify the store score according to the payment flow of user U1 and his / her companions (hereinafter collectively referred to as participants). For example, if the payment flow of multiple participants shows that many (e.g., more than half of the participants) make a payment at an izakaya and then often make a payment at another izakaya, the payment server 10 modifies the store score so that the store score of the izakaya is higher than the store scores of other types of businesses. For example, the payment server 10 weights the business type (e.g., izakaya) more heavily when calculating the store score.

[0136] Alternatively, if many of the participants (e.g., more than half) have not made consecutive payments, the payment server 10 may not present recommended stores. For example, if many of the participants do not attend the after-party, the payment server 10 may not present information on the store score after the first-party payment is completed.

[0137] As described above, the payment server 10 can calculate a shop score that is more suited to the user U1 by modifying the shop score depending on the payment flow.

[0138] [6-4. About Similar Users] In the above embodiment, the payment server 10 extracts other users whose user attribute information and user history are similar to those of user U1 as similar users, but the similar users extracted by the payment server 10 are not limited to this.

[0139] For example, the payment server 10 may extract other users who have similar evaluations of the store where the user U1 has made the payment as similar users.

[0140] In this case, the payment server 10 acquires evaluation information of the payment store (an example of a store where payment has been made) included in the user history of the user U1. For example, the payment server 10 acquires evaluation information of the payment store where the user U1 made payment by referring to the payment information database 32 and the evaluation information database 33 using the acquired usage history of the user U1.

[0141] Based on the acquired evaluation information, the payment server 10 refers to the evaluation information database 33 and extracts other users whose evaluation information is similar to the acquired evaluation information as similar users. Here, similar evaluation information means that "the tendency of evaluations of the same store is the same or similar."

[0142] In this way, the payment server 10 may extract other users who have a similar tendency to evaluate stores as similar users to the user U1. In this way, the payment server 10 can extract similar users who have similar evaluations of the stores where the payments were made in addition to (or instead of) the stores where the payments were made being similar.

[0143] [6-5. Processing mode] Among the processes described in the above embodiments, all or part of the processes described as being performed automatically can be performed manually, and conversely, all or part of the processes described as being performed manually can be performed automatically by a known method. In addition, the information including the processing procedures, specific names, various data and parameters shown in the above documents and drawings can be changed arbitrarily unless otherwise specified. For example, the various information shown in each drawing is not limited to the illustrated information.

[0144] In addition, each component of each device shown in the figure is a functional concept, and does not necessarily have to be physically configured as shown in the figure. In other words, the specific form of distribution and integration of each device is not limited to that shown in the figure, and all or part of them can be functionally or physically distributed and integrated in any unit according to various loads, usage conditions, etc.

[0145] Furthermore, the above-described embodiments can be appropriately combined as long as the processing contents are not contradictory.

[0146] [7. Effects] As described above, the payment server 10 includes an acquisition unit 41 and a calculation unit 42. The acquisition unit 41 acquires store information about a store and a payment history of the user U1. The calculation unit 42 calculates a store score for the user U1 based on the store information and the payment history of the user U1.

[0147] This allows the payment server 10 to calculate a store score that takes into account the payment history of the user U1, and therefore allows the payment server 10 to appropriately evaluate the store according to the user U1.

[0148] In addition, in the payment server 10 according to the embodiment, for example, the acquisition unit 41 acquires store identification information for identifying a store and user identification information for identifying a user U1. The acquisition unit 41 acquires store information corresponding to the store identification information and a payment history of the user U1 corresponding to the user identification information.

[0149] This allows the payment server 10 to calculate a store score that takes into account the payment history of the user U1, and therefore allows the payment server 10 to appropriately evaluate the store according to the user U1.

[0150] Furthermore, in the payment server 10 according to the embodiment, for example, the calculation unit 42 calculates a store score based on evaluations of the store by similar users whose payment histories are similar to those of the user U1.

[0151] This allows the payment server 10 to calculate a store score based on store evaluations made by similar users whose payment histories are similar to those of user U1, and therefore allows the payment server 10 to appropriately evaluate stores according to user U1.

[0152] In the payment server 10 according to the embodiment, for example, the acquisition unit 41 acquires attribute information of the user U1. The calculation unit 42 calculates a shop score based on the attribute information.

[0153] This allows the payment server 10 to calculate the store score using attribute information of the user U1 in addition to the payment history, and therefore allows the payment server 10 to appropriately evaluate the store according to the user U1.

[0154] Furthermore, in the payment server 10 according to the embodiment, for example, the calculation unit 42 calculates a store score based on evaluations of a store by similar users who are similar to the user U1 in at least one of the payment history and attribute information.

[0155] This allows the payment server 10 to calculate a store score based on store evaluations made by similar users whose payment history and attribute information are similar to that of user U1, thereby enabling the payment server 10 to appropriately evaluate stores according to user U1.

[0156] In the payment server 10 according to the embodiment, for example, the acquisition unit 41 acquires a payment history of a second user (an example of an accompanying person) different from the user U1. The calculation unit 42 calculates a store score for the store for the user U1 and the second user based on the payment history of the user U1 and the second user.

[0157] This allows the payment server 10 to calculate a store score taking into account the payment history of user U1 and the second user, thereby enabling the store to be appropriately evaluated according to user U1 and the second user.

[0158] In addition, in the payment server 10 according to the embodiment, for example, the acquisition unit 41 acquires the payment history of the second user designated by the user U1.

[0159] This allows the payment server 10 to calculate a store score taking into account the payment history of user U1 and the second user, thereby enabling the store to be appropriately evaluated according to user U1 and the second user.

[0160] [8. Hardware Configuration] The payment server 10 according to each of the above-described embodiments is realized, for example, by a computer 1000 configured as shown in FIG. 9. The payment server 10 will be described below as an example. FIG. 9 is a hardware configuration diagram showing an example of a computer that realizes the functions of the payment server. The computer 1000 has a CPU 1100, a RAM 1200, a ROM 1300, a HDD 1400, a communication interface (I / F) 1500, an input / output interface (I / F) 1600, and a media interface (I / F) 1700.

[0161] The CPU 1100 operates and controls each unit based on a program stored in the ROM 1300 or the HDD 1400. The ROM 1300 stores a boot program executed by the CPU 1100 when the computer 1000 is started up, programs that depend on the hardware of the computer 1000, and the like.

[0162] The HDD 1400 stores programs executed by the CPU 1100, data used by such programs, etc. The communication interface 1500 receives data from other devices via a communication network 500 (corresponding to the network N in the embodiment) and sends the data to the CPU 1100, and also transmits data generated by the CPU 1100 to other devices via the communication network 500.

[0163] The CPU 1100 controls output devices such as a display and a printer, and input devices such as a keyboard and a mouse, via the input / output interface 1600. The CPU 1100 acquires data from the input devices via the input / output interface 1600. The CPU 1100 also outputs data generated via the input / output interface 1600 to the output devices.

[0164] The media interface 1700 reads a program or data stored in the recording medium 1800 and provides it to the CPU 1100 via the RAM 1200. The CPU 1100 loads the program from the recording medium 1800 onto the RAM 1200 via the media interface 1700 and executes the loaded program. The recording medium 1800 is, for example, an optical recording medium such as a DVD (Digital Versatile Disc) or a PD (Phase change rewritable Disc), a magneto-optical recording medium such as an MO (Magneto-Optical disk), a tape medium, a magnetic recording medium, or a semiconductor memory.

[0165] For example, when the computer 1000 functions as the payment server 10, the CPU 1100 of the computer 1000 executes a program loaded on the RAM 1200 to realize the function of the control unit 40. In addition, the HDD 1400 stores each data in the storage device of the payment server 10. The CPU 1100 of the computer 1000 reads and executes these programs from the recording medium 1800, but as another example, the CPU 1100 may obtain these programs from another device via a predetermined communication network.

[0166] [9. Others] Although some of the embodiments of the present application have been described in detail above with reference to the drawings, these are merely examples, and the present invention can be embodied in other forms that incorporate various modifications and improvements based on the knowledge of those skilled in the art, including the forms described in the Disclosure of the Invention section.

[0167] Further, the above-mentioned payment server 10 can be flexibly changed in configuration, for example, by calling an external platform or the like using an API (Application Programming Interface) or network computing, depending on the function.

[0168] Furthermore, the term "unit" in the claims may be read as "means" or "circuit," etc. For example, an acquisition unit may be read as an acquisition means or an acquisition circuit. [Explanation of symbols]

[0169] 1. Information Processing Systems 10 Payment Server 20,110,210 Communications Department 30,220 storage unit 31 Store Information Database 32 Payment Information Database 33 Evaluation Information Database 40,140,240 Control section 41 Acquisition Department 42 Calculation section 43 Providing Department 44 Payment processing section 45 Reception 100 User terminals 120 Input section 130 Output section 141,241 Receiver 142,242 Transmitter 200 Service Providing Equipment

Claims

1. an acquisition unit that acquires store designation information indicating store search conditions from a specific user, references a storage device in which the history of payments made using a terminal device of each user is registered, and acquires evaluations of the evaluation target store by similar users who have similar attributes of the specific user and usage history of the payment store where the specific user made the payment using the terminal device, among users who have made payments at the evaluation target store corresponding to the store designation information; A calculation unit that calculates a store score for the evaluated store based on the evaluation; a providing unit that provides the store score calculated by the calculation unit to another information processing device in order to provide the store score to the predetermined user; 13. An information processing device comprising:

2. The store designation information includes store identification information for identifying the evaluation target store, The calculation unit calculates the store score based on an evaluation of the evaluation target store identified by the store identification information.

2. The information processing apparatus according to claim 1,

3. the calculation unit calculates, as the store score, an average value of the evaluations by the similar users for the evaluation target store corresponding to the store designation information; 2. The information processing apparatus according to claim 1,

4. The calculation unit calculates the store score by weighting the evaluation by the similar user for the evaluation target store corresponding to the store designation information according to a similarity between an attribute of the predetermined user and an attribute of the similar user.

2. The information processing apparatus according to claim 1,

5. The acquisition unit is acquiring user-specified information including attribute information from the predetermined user; Based on the attribute information, information on the similar users having attributes similar to those of the predetermined user is acquired.

2. The information processing apparatus according to claim 1,

6. The acquisition unit is Refer to the storage device and a second storage device that stores information regarding evaluations made by the user with respect to the evaluation target store, and obtain evaluation information regarding the payment store where the specified user made a payment; Refer to the storage device, and obtain the evaluation of the evaluation target store corresponding to the store designation information by a second similar user whose evaluation information of the payment store is similar to the evaluation information; The calculation unit is Calculating the store score for the evaluated store based on the evaluation 2. The information processing apparatus according to claim 1,

7. The acquisition unit is Acquiring companion information regarding a companion who is scheduled to visit the evaluation target store together with the predetermined user, Refer to the storage device, and obtain evaluations of the evaluation target store corresponding to the store designation information by accompanying similar users who have similar attributes to the accompanying user among the users who have made a payment at the evaluation target store corresponding to the store designation information, The calculation unit is Calculating the store score for the evaluated store based on the evaluation 2. The information processing apparatus according to claim 1,

8. 1. A computer-implemented information processing method, comprising: an acquisition step of acquiring store designation information indicating store search conditions from a specific user, referencing a storage device in which the payment history using each user's terminal device is registered, and acquiring evaluations of the evaluation target store by similar users who have similar attributes of the specific user and usage history of the payment store where the specific user made the payment using the terminal device, among users who have made payments at the evaluation target store corresponding to the store designation information; A calculation step of calculating a store score for the evaluated store based on the evaluation; a providing step of providing the shop score calculated by the calculation step to another information processing device in order to provide the shop score to the predetermined user; 13. An information processing method comprising:

9. an acquisition step of acquiring store designation information indicating store search conditions from a specific user, referencing a storage device in which the payment history using each user's terminal device is registered, and acquiring evaluations of the evaluation target store by similar users who have similar attributes of the specific user and usage history of the payment store where the specific user made the payment using the terminal device among users who have made payments at the evaluation target store corresponding to the store designation information; A calculation step of calculating a store score for the evaluated store based on the evaluation; a providing step of providing the shop score calculated by the calculation step to another information processing device in order to provide the shop score to the predetermined user; An information processing program characterized by causing a computer to execute the above.

Images