JP7404120B2 - Information processing device, information processing method, and information processing program - Google Patents

Description

The present invention relates to an information processing device, an information processing method, and an information processing program.

Conventionally, there are review sites that collect store reviews (so-called word of mouth) posted by users and publish review collections. By viewing reviews of a store published on a review site, a user can make a decision as to whether or not to use that store.
For such review sites, credibility of reviews is important. Therefore, Patent Document 1 discloses a technology that manages store usage history based on location information notified from a user terminal carried by the user, and determines whether or not the user can write a post based on this usage history. is disclosed. According to such technology, it is possible to restrict posting by users who have not actually visited the store.

Japanese Patent Application Publication No. 2011-221805

However, the technique disclosed in Patent Document 1 cannot confirm whether the user has actually used the store, and is insufficient as a technique for ensuring the reliability of reviews. Furthermore, if the user refuses to provide location information, it is impossible to determine whether the user is allowed to post.

Further, the number of reviews of a store published on a review site is important for both the user and the store. For example, by viewing more reviews of a store, the user can more accurately judge the reliability of each review about the store. A store can expect that the more reviews it has about its own store, the more attention it will receive from users, and the more effective it will be in attracting customers. However, Patent Document 1 does not disclose a technique for effectively collecting reviews from users.

An object of the present invention is to provide an information processing device, an information processing method, and an information processing program that can effectively collect reliable reviews.

The information processing device of the present invention requests a user to transmit payment review request information including payment request information requesting electronic payment at a target store and review request information requesting posting of a review regarding the target store. a transmission unit, a payment information acquisition unit that acquires payment information including identification information of the store where the electronic payment was executed and identification information of the user who executed the electronic payment, and a payment information acquisition unit that corresponds to the target store by the payment information acquisition unit. and a posting control unit that accepts posting of a review regarding the target store from the user corresponding to the payment information when the payment information is acquired.

In the present invention, by checking the payment review request information transmitted from the information processing device, the user can learn that electronic payment can be performed at the target store and that the target store is soliciting reviews. This gives the target user an incentive to make an electronic payment at the target store and post a review.
Further, in the present invention, by using the payment information, the information processing device allows the user who made the electronic payment to post a review regarding the target store, on the condition that the electronic payment was made at the target store. I can accept it. That is, review submissions can be accepted from users who have actually used the target store. Thereby, even if the user refuses to provide location information, it is possible to sufficiently ensure the reliability of the review.
Therefore, according to the information processing device of the present invention, reliable reviews can be collected effectively.

1 is a schematic diagram showing a schematic configuration of an information processing system including a server device according to an embodiment of the present invention. FIG. 1 is a block diagram showing a schematic configuration of a server device according to the present embodiment. 2 is a flowchart showing review request processing according to the present embodiment. 5 is a flowchart illustrating an example of user detection processing according to the present embodiment. 7 is a flowchart showing another example of user detection processing according to the present embodiment. 7 is a flowchart showing another example of user detection processing according to the present embodiment. 5 is a flowchart showing review posting processing according to the present embodiment.

Hereinafter, one embodiment of the present invention will be described based on the drawings.
[Overall configuration of information processing system]
FIG. 1 is a block diagram showing a schematic configuration of an information processing system 1 of this embodiment.
As shown in FIG. 1, the information processing system 1 of the present embodiment includes a user terminal 10 used by a user, a store terminal 20 installed in a store, and a server device 30 that is an information processing device of the present invention. , these are communicably connected via a network such as the Internet.
In this embodiment, the information processing system 1 functions as a system that collects store reviews based on users' code payments. Specifically, the server device 30 transmits request information to any user using the information processing system 1, requesting code payment at a store and posting of a store review. Further, the server device 30 accepts posting of store reviews from the user terminal 10 on the condition that the user has made a code payment at the store.
Note that the server device 30 may transmit the collected store reviews to another review site management server, or the server device 30 itself may be a server device that manages a review site. Furthermore, in the present embodiment, a store refers to any facility that provides goods or services through the exchange of money, and these goods and services are collectively referred to as products.

Note that code payment is a cashless payment that is performed using a code when buying and selling products at a store. These include store-presented code payment, in which payment is executed, and user-presented code payment, in which payment is executed by a store terminal 20 installed in the store reading a code displayed on the user terminal 10. The code is any display object whose content can be recognized by a machine, such as a one-dimensional code or a two-dimensional code, and is linked to store information or user information.

[Configuration of user terminal 10]
The user terminal 10 is a terminal device owned by a user, and is configured by, for example, a computer such as a smartphone or a tablet terminal. Although illustration of the specific configuration of the user terminal 10 is omitted, the user terminal 10 has the basic configuration of a general computer. That is, the user terminal 10 includes an input operation unit that accepts user operations, a display that displays images and text, a recording unit that records various information, and an arithmetic processing unit (such as a CPU) that processes various information. There is. Further, the user terminal 10 may include a camera for reading codes and a GPS device for measuring the current position of the user terminal 10.

The storage unit of the user terminal 10 stores a code payment application program (payment application) for the user to perform code payment. In the user terminal 10, the arithmetic processing unit executes various functions of the payment application by reading and executing the payment application stored in the recording unit. Further, the recording unit of the user terminal 10 stores various information used in the payment application.

[Configuration of store terminal 20]
The store terminal 20 is a computer that controls a POS system, and is installed within a store, for example. Note that in this embodiment, the store terminal 20 may be installed at a payment counter in the store and function as a cash register (POS register).
Although illustration of the specific configuration of the store terminal 20 is omitted, the store terminal 20 has the basic configuration of a general computer. That is, the store terminal 20 includes an input operation section that receives operations from a store clerk, a display that displays various types of information, a recording section that records various types of information, and an arithmetic circuit (such as a CPU) that processes various types of information. The store terminal 20 may also include a reader for reading the code.

Note that the storage unit of the store terminal 20 stores a store code payment application program (store payment application) for the store to perform code payment. In the store terminal 20, the arithmetic processing section executes various functions of the store payment application by reading and executing the store payment application stored in the recording section.
Further, the storage unit of the store terminal 20 stores product information, store information, and the like.
The product information includes a product ID, price, product name, product category, etc. for each product.
The store information includes a store ID, store name, store category, store location, and the like.

[Configuration of server device 30]
FIG. 2 is a block diagram showing a schematic configuration of the server device 30. As shown in FIG.
The server device 30 is configured by a computer and functions as an information processing device of the present invention. This server device 30 includes a communication section 31, a storage section 32, a control section 33, and the like.

The communication unit 31 is connected to the Internet and communicates with devices such as the user terminal 10 and the store terminal 20 via the Internet.

The storage unit 32 is a data recording device composed of, for example, a memory or a hard disk. This storage unit 32 stores an information processing program for controlling the server device 30.
The storage unit 32 is also provided with a user database 321, a store database 322, a payment database 323, a review database 324, a map database 325, and the like.

The user database 321 stores user information for each user who uses this system. This user information includes a user ID, user name, user attributes, payment history, account balance, coupon holding information, location history, posting history, request list, list of stores where posting is possible, and the like.
The user ID is identification information that identifies each user.
User attributes include the user's age, gender, occupation, place of residence, and the like.
The payment history is a history of past code payments, and includes payment date and time, payment amount, product ID, store ID, and the like.
The account balance is the balance of electronic money charged to the payment app account.
Coupon holding information is information about coupons that can be used by the user.
The location history is a history of user location information measured by GPS.
The posting history is historical information of store reviews posted by users.
The request list is a list of review request information requested by the user. Further, in the request list, a tag indicating that there is a history of code payments may be added to review request information regarding stores that have a history of code payments by the user.

The store database 322 stores store information and product information for each store that uses the information processing system 1. The product information and store information stored in the store database 322 are the same as the product information and store information stored in the store terminal 20.

The payment database 323 stores payment information received by the server device 30. This payment information includes at least information that identifies the store where the code payment was executed (eg, store ID) and information that identifies the user who executed the code payment (eg, user ID). The payment information in this embodiment includes a payment ID, a user ID, a store ID, a product ID, a payment amount, and the like. The payment ID is identification information that identifies each piece of payment information. The payment information may also include location information (GPS information) of the user at the time the code payment was executed.

The review database 324 records store review information and review request information.
The store review information includes a store ID, a user ID of a user who posted a store review, a store name, review content, an image (photo or video) of the store or product, and the like.

The review request information includes a request ID, store ID, store name, user condition information, review content instruction information, and benefit information.
The request ID is identification information that identifies review request information.
The user condition information includes conditions regarding attributes, payment history, location information, etc. of the user who is the review request destination. For example, "I am a woman,""I am in my 20s to 30s,""I am located within X m of the review target store," and "I have a high degree of relevance to the target store." In addition, the user condition information associated with the code payment history includes ``have a code payment history within a specified distance from the target store (have purchase experience in the area that includes the target store)'', ``have reviewed within a specified amount of time in the past from now. "There is a history of code payments made within a specified distance from the target store (for example, you are shopping in an area that includes the target store)", "There is a history of code payments made within a specified distance from the target store X or more times within the specified period" (For example, there is a habit of shopping in the area that includes the target store.)

The review content instruction information is information that indicates the content of the store review, and includes, for example, the store atmosphere, product satisfaction, store crowding, product inventory status, and store or product images (photos or videos). It may include instructions regarding various items such as.
The benefit information is information indicating the details of the benefit given to the user who posted the store review. Examples include the provision of electronic money that can be used for code payments and the provision of discount coupons that can be used at target stores.
Further, the review request information may further include information such as a deadline for posting store reviews and the desired number of posts.

The map database 325 records map information and point information regarding each point on the map (for example, a facility such as a store). The point information includes, for example, location coordinates for facilities, addresses, and the like.

The control unit 33 is composed of an arithmetic circuit such as a CPU, and a recording circuit such as a RAM. The control unit 33 loads the information processing program recorded in the storage unit 32 into the RAM, and executes various processes in cooperation with the program loaded into the RAM. Then, by reading and executing the information processing program, the control unit 33 controls the payment information acquisition unit 331, the request generation unit 332, the user detection unit 333, the request transmission unit 334, and the posting process, as shown in FIG. It functions as a control unit 335 and a privilege granting unit 336.

Note that the number of computers that constitute the server device 30 is not particularly limited. For example, the server device 30 may be configured by one computer, or may be a cloud server constructed by connecting multiple computers via a network.

The payment information acquisition unit 331 receives payment information regarding code payment from a payment management server device or the like via the Internet.
The request generation unit 332 generates request information for requesting a store review of the target store.
The user detection unit 333 detects a target user to whom request information is to be transmitted.
The request transmitting unit 334 transmits request information to the target user.
The posting control unit 335 receives a post of a store review of the target store from the user on the condition that the user executes code payment at the target store.
The benefit granting unit 336 grants a benefit to a user who has posted a store review.

[Generation process of review request information]
The request generation unit 332 can generate review request information using various methods. An example of how to generate review request information will be described below.

The request generation unit 332 may generate review request information based on a review request sent by a store staff member or a user.
Specifically, the store staff or user operates the store terminal 20 or the user terminal 10, selects a desired store from the list of stores sent from the server device 30, and receives review content instruction information regarding the store and the review request destination user. Enter your information. When the store terminal 20 or the user terminal 10 transmits the input information together with the store ID to the server device 30, the request generation unit 332 of the server device 30 combines the received information (review content instruction information and review request destination user information) with appropriate information. The bonus information is associated with the request ID and the store ID, and stored in the review database 324 as review request information.

Furthermore, when a store staff member sends a review request, the store staff member may input store review content instruction information and review request destination user information, as well as bonus information. In this case, the request generation unit 332 of the server device 30 associates the received information (review content instruction information, review request destination user information, and benefit information) with the request ID and store ID, and stores it in the review database 324 as review request information. Make me remember.

The request generation unit 332 may automatically generate the review request information without depending on receiving the review content instruction information from the store terminal 20 or the user terminal 10.
For example, if there is a store for which no store reviews have been posted for a predetermined period or more, the request generation unit 332 may generate review request information regarding the store.
Further, the request generation unit 332 may obtain user location information and, if a large number of users are visiting a certain area, generate review request information regarding a store located in the area.
In such a case, templates set in advance according to various situations may be used as the review content instruction information, review request destination user information, and benefit information.

[Review request processing]
The review request process performed by the server device 30 will be described below with reference to the flowchart of FIG. 3. In addition, below, the target store is store A, and the example which performs a review request based on the review request information T regarding this store A is demonstrated.

In the server device 30, the user detection unit 333 detects a user matching the review request information T as a target user based on the payment information acquired by the payment information acquisition unit 331 (step S1). That is, the user detection unit 333 detects a user who matches the review request information T from among a plurality of users who execute code payment.

There are various specific examples of step S1.
For example, as shown in FIG. 4, the user detection unit 333 determines whether the payment information acquisition unit 331 has acquired payment information (step S11).
When the payment information acquisition unit 331 acquires the payment information (step S11; Yes), the user detection unit 333 searches the store database 322 for store information corresponding to the store ID based on the store ID of the payment information. The location is acquired as payment location information (step S12). Alternatively, if the payment information includes the user's location information, the user detection unit 333 may acquire the location information as the payment location information.
On the other hand, if the payment information acquisition unit 331 has not acquired payment information (step S11; No), step S11 is repeated.
After step S12, the user detection unit 333 refers to the map database 325 and determines whether the payment location information is within a predetermined distance from the store location of store A (step S13).
If the payment location information is within a predetermined distance from the store location of the target store, the user detection unit 333 identifies the user corresponding to the user ID of the payment information acquired in step S11 as the target user (step S14). On the other hand, if the payment location information is farther than the predetermined distance from the store location of store A, the process returns to step S11.
Thereby, a user who is shopping in an area including store A can be detected as a target user.

As another example, as shown in FIG. 5, the user detection unit 333 refers to the payment information of a plurality of users obtained in the most recent predetermined period from the payment database 323 (step S15), and Based on the store ID, the store location of the store information corresponding to the store ID is acquired from the store database 322 as payment location information (step S16). Alternatively, if the payment information includes the user's location information, the user detection unit 333 may acquire the location information as the payment location information.
Then, the user detection unit 333 determines whether each payment location information is within a predetermined distance from the store location of the target store by referring to the map database 325, and determines whether the payment location information is within a predetermined distance from the store location of the target store. The number of payment information within a predetermined distance is counted for each user (step S17). The user detection unit 333 identifies one or more users for whom the number of payment information counted in step S17 is a predetermined number or more as target users (step S18).
Note that in step S17, payment information whose payment location information is equal to the store location of the target store may be included in the count.
Further, the predetermined number used as a criterion for determining the number of payment information in step S18 may be a number of 1 or more. When the predetermined number is 1, a user who has shopping experience in the area including store A can be detected as the target user. Furthermore, if the predetermined number is plural, users who have a habit of shopping in the area including store A can be detected as target users.

As another example, as shown in FIG. 6, the user detection unit 333 refers to the payment information of a plurality of users obtained in the most recent predetermined period from the payment database 323 (step S15), and Based on the user ID, user information corresponding to the user ID is acquired from the user database 321 (step S19).
Then, the user detection unit 333 calculates, for each user, the degree of association between the payment history of the user information acquired in step S19 and store A, which is the target store (step S20).
For example, based on the store ID and product ID in the payment history of the user information, the user detection unit 333 retrieves from the store database 322 the store category of the store corresponding to the store ID or the product of the product corresponding to the product ID. Identify categories. Further, based on the store ID of the review request information T, the user detection unit 333 identifies the store category of the store A corresponding to the store ID from the store database 322. Then, the user detection unit 333 calculates the degree of association between the store category or product category specified based on the user information and the store category specified based on the review request information T using a known scoring technique. do.
After that, the user detection unit 333 identifies one or more users whose degree of association calculated in step S20 is equal to or higher than a predetermined value as target users (step S21).
As a result, a user who can be expected to be interested in the store A corresponding to the review request information T or the products handled by the store A is detected as the target user.

The explanation will be returned to the flow in FIG. 3. The request transmitting unit 334 creates payment review request information including review request information T and payment request information for requesting code payment at store A, and transmits this payment review request information to the target detected in step S1. The request is sent to the user (step S2; request sending step).
Note that the request transmission unit 334 may create a recommendation according to the content transmission time period and include it in the payment review request information. For example, the payment review request information includes text information such as "How do you like the omelette rice at store A for lunch today? Pay with the code and write a review to earn XX points!"
The user terminal 10 notifies the user that payment review request information has been received from the server device 30.

Further, the request transmitting unit 334 updates the request list of the user information of the target user by adding the payment review request information (step S3).
When the user operates the user terminal 10 to start the payment application, the user terminal 10 can acquire a request list from the server device 30 and display it on the display. The user can check the review requests requested to him/her by viewing the request list displayed on the display.

Note that the payment review request information may be transmitted to multiple target users at any time by repeatedly performing the flow shown in FIG. 3 . When the review request information T is associated with restriction information such as a request deadline and the number of requesting users, the number of repetitions of the flow shown in FIG. 3 may be adjusted based on the restriction information.

[Review reception process]
The review reception process in the server device 30 will be explained with reference to the flowchart of FIG. 7. In addition, below, the case where the user U operates the user terminal 10, starts a payment application, and performs code payment at store A which is a target store will be explained.
Here, as a specific method of code payment, various known techniques can be used, such as user presentation type code payment and store presentation type code payment.
For example, in the case of user-presented code payment, the user terminal 10 causes the display to display a code in which user information such as a user ID is embedded. The store terminal 20 uses a reader to read the code displayed on the user terminal 10, and provides payment information including the read information (user ID, etc.) and information regarding product payment (payment amount, store ID, product ID, etc.) is sent to the payment management server device.
In the case of store-presented code payment, the store terminal 20 causes the display to display a code in which information regarding payment for the product is embedded. Alternatively, the store is provided with a code embedded with information regarding payment for the product in advance. The user terminal 10 reads the code using a camera and transmits payment information including the read information (payment amount, store ID, product ID, etc.) and user information (user ID, etc.) to the payment management server device.

As shown in FIG. 7, in the server device 30, the payment information acquisition unit 331 acquires payment information from the payment management server device (step S31; payment information acquisition step). Note that the payment information acquisition unit 331 may acquire payment information accumulated in the payment management server device at preset predetermined intervals, or may acquire payment information that is transmitted every time the payment management server device performs payment processing. You may obtain it.
Thereafter, the posting control unit 335 refers to the user database 321 and determines whether the store A corresponding to the store ID of the payment information is the store corresponding to the review request information included in the request list of the user U, that is, the store A It is determined whether or not is the target store for which user U has requested a store review (step S32).

If store A is the target store for which user U has requested a store review (step S32; if Yes), the posting control unit 335 transmits the review posting content to user U's user terminal 10 (step S33).
The user terminal 10 displays the review posted content received from the server device 30 on the display unit. This review posting content includes, for example, a store name display section that displays the name of store A, a review input section for the user to input a review, an image input section for the user to input an image, and a posting button. Be prepared. When a user inputs a review or the like and selects a post button, review post information is transmitted from the user terminal 10 to the server device 30. This review posting information includes a store ID, user ID, review information, image information, and the like.

When the posting control unit 335 of the server device 30 receives the review posting information from the user terminal 10 (step S34; in the case of Yes), the posting control unit 335 identifies the store information corresponding to the store ID from the review database 324, and updates the store information with respect to the store information. to record review submission information. The posting control unit 335 then updates the review site based on the review posting information (step S35). For example, the posting control unit 335 updates the review site so that the review posting information received in step S35 is displayed on the store A's introduction page.
That is, when the payment processing information corresponding to store A is acquired in steps S33 to S35, the posting control unit 335 of the present embodiment allows the user corresponding to the user ID of the payment information to post a review regarding store A. Execute the process of accepting the request (posting control step).

The benefit granting unit 336 specifies user information corresponding to the user ID from the user database 321 and also specifies review request information corresponding to the store ID from the review database 324. Then, the benefit granting unit 336 grants the user information a benefit in accordance with the benefit information recorded in the review request information (step S36). For example, the benefit granting unit 336 adds a predetermined amount of electronic money to the balance information of the user information, or stores predetermined coupon information to the coupon holding information of the user information.

On the other hand, if the communication with the user terminal 10 ends without receiving review posting information from the user terminal 10 (step S35; in the case of Yes), the posting control unit 335 selects the store from the user U's request list in the user database 321. A tag indicating that there is a code payment history is attached to the review request information corresponding to A (step S37).
The flow ends with the above steps.

[Actions and effects of this embodiment]
The server device 30 of the present embodiment includes a storage unit 32 and a control unit 33, and the control unit 33 reads the information processing program stored in the storage unit 32, and controls the payment information acquisition unit 331 and the request transmission unit. 334 and a posting control section 335. The request transmitting unit 334 transmits to the user payment review request information including payment request information requesting code payment at the target store and review request information requesting posting of a review regarding the target store. When payment information regarding the target store is acquired by the payment information acquisition unit 331, the posting control unit 335 accepts posting of a review regarding the target store from the user corresponding to the payment information.
In this embodiment, by checking the payment review request information sent from the server device 30, the user can learn that code payment can be executed at the target store and that the target store is soliciting reviews. . This gives the target user an incentive to make code payment at the target store and post a review.
Furthermore, in the present embodiment, by using the payment information, the server device 30 allows the user who executed the code payment to post a review regarding the target store, on the condition that the code payment was performed at the target store. can be accepted. That is, review submissions can be accepted from users who have actually used the target store. Thereby, even if the user refuses to provide location information, it is possible to sufficiently ensure the reliability of the review.
Therefore, according to the server device 30 of this embodiment, reliable reviews can be collected effectively.

The control unit 13 of this embodiment also functions as the user detection unit 333 by reading the information processing program stored in the storage unit 12. The user detection unit 333 detects a target user to whom the request transmission unit 334 transmits the payment review request information based on the payment information acquired by the payment information acquisition unit 331. This increases the possibility that the request will be fulfilled compared to the case where payment review request information is sent to users at random.

For example, the user detection unit 333 acquires payment location information based on the payment information, and if the payment location information is within a predetermined distance from the store location of the target store, the user detection unit 333 detects the user corresponding to the payment information as the target user. As a result, payment review request information can be sent to users who are shopping in the area that includes the target store, so compared to the case where payment review request information is simply sent to users who are passing around the target store, the target user Increases the probability of completing the request.

In addition, the user detection unit 333 acquires payment location information based on the payment information, counts the number of payment information whose payment location information is within a predetermined distance from the store location of the target store for each user, and counts the number of payment information for each user. may be detected as a target user. This allows payment review request information to be sent to users who have the habit of shopping in areas that include the target store, so even if the payment review request information is on a different day than the day on which the payment information was obtained, the target user can complete the request. Probability improves.

Further, the user detection unit 333 acquires user information based on the payment information, calculates the degree of association between the payment history of the user information and the review request information, and detects users whose degree of association is equal to or higher than a predetermined value as target users. It's okay. This allows the payment review request information to be sent to users who are expected to be interested in the target store, improving the probability of fulfilling the request.

[Modified example]
The present invention is not limited to the embodiments described above, but includes modifications within a range that can achieve the object of the present invention, some of which will be shown below as modified examples.

[Modification 1]
In the embodiment described above, the request transmitting unit 334 transmits the payment review request information to the target user detected based on the payment information, but the present invention is not limited to this.
That is, the request transmitting unit 334 may transmit payment review request information to any user.
For example, the request transmitting unit 334 may refer to the posting record in the user information of the user database 321 and transmit payment review request information to a user who has a large review posting record.
Further, the request transmitting unit 334 may use information acquired from another server device that can communicate over the Internet. Specifically, the request transmitting unit 334 acquires the user's planned location from the schedule management server device or the user's destination from the route search server device, so that the requested location or destination is targeted. Payment review request information may be sent to a user near the store.

[Modification 2]
In the embodiment, the posting control unit 335 transmits the review posting content to the user terminal 10 in response to the execution of the payment process, but the present invention is not limited to this.
For example, in response to a request from the user terminal 10, the server device 30 extracts a list of review requests with tags indicating that there is a history of code payments from a list of user requests in the user database 321 (reviews can be posted). A request list) is created and this list of requests that can be submitted for review is sent to the user terminal 10.
At the user terminal 10, the user selects a desired review request from the list of requests that can be posted by the server device 30, and the user terminal 10 sends the content request for posting the review request to the server along with the request ID. The information is transmitted to the device 30.
In the server device 30, the posting control unit 335 transmits the review posting content of the review request information corresponding to the request ID to the user terminal 10 in response to receiving the content request.
With such processing as well, it is possible to receive a review posting regarding the target store from the user who executed the electronic payment on the condition that the electronic payment was performed at the target store.

[Modification 3]
In the storage unit of the embodiment, a list of requests is stored for each user, but a list of requests common to all users may be stored.
In this case, the request transmitting unit 334 may transmit payment review request information to any user, as in the first modification described above.

[Modification 4]
In the embodiment, the user detection unit 333 detects a target user to whom payment review request information is to be sent based on payment information and the like. As a modification of the above embodiment, the target user may be detected using machine learning using AI. For example, the user detection unit 333 may use machine learning to generate a model using the payment information and the review posting history of each user as input and outputting the target user. Thereby, users who are expected to post reviews can be detected with high accuracy as target users.

[Modification 5]
In the embodiment described above, code payment is used as a means of electronic payment of the present invention, but the present invention is not limited to this. That is, other forms of electronic payment, such as electronic payment using electronic money, can be used as long as the payment information including the identification information of the payment store and the identification information of the payment user can be obtained.

DESCRIPTION OF SYMBOLS 1... Information processing system, 10... User terminal, 20... Store terminal, 30... Server device, 31... Communication department, 32... Storage part, 321... User database, 322... Store database, 323... Payment database, 324... Review database , 325...Map database, 33...Control unit, 331...Payment information acquisition unit, 332...Request generation unit, 333...User detection unit, 334...Request transmission unit, 335...Posting control unit, 336...Benefit granting unit.

Claims (7)

Send a request to the user to send payment review request information including payment request information requesting electronic payment at the target store that is the target of the store review and review request information requesting to post a store review regarding the target store. Department and
a payment information acquisition unit that acquires payment information including identification information of the store where the electronic payment was performed and identification information of the user who performed the electronic payment;
When the payment information corresponding to the target store is acquired by the payment information acquisition unit, the post control unit receives a post of a store review regarding the target store from a user corresponding to the payment information. Information processing equipment. The information processing device according to claim 1,
Information processing further comprising: a user detection unit that detects a target user to whom the request transmission unit transmits the payment review request information based on the payment information acquired by the payment information acquisition unit. Device. The information processing device according to claim 2,
The user detection unit acquires payment location information based on the payment information, and if the payment location information is within a predetermined distance from the store location of the target store, the user detection unit identifies the user corresponding to the payment information as the target user. An information processing device characterized by detecting as follows. The information processing device according to claim 2,
The user detection unit acquires payment location information based on the payment information, counts for each user the number of payment information in which the payment location information is within a predetermined distance from the store location of the target store, and calculates the payment location information based on the payment information. An information processing apparatus characterized in that a user whose number of users is equal to or greater than a predetermined number is detected as the target user. The information processing device according to claim 2,
The user detection unit acquires user information based on the payment information, calculates the degree of association between the payment history of the user information and the target store, and selects the user for whom the degree of association is greater than or equal to a predetermined value as the target user. An information processing device characterized by detecting as follows. An information processing method for accepting review submissions regarding a target store by a computer, the method comprising:
A request to send payment review request information to the user, including payment request information requesting electronic payment at the target store that is the target of the store review, and review request information requesting posting of a store review regarding the target store. a sending step;
a payment information acquisition step of acquiring payment information regarding the electronic payment performed by the user at the store;
After the payment information corresponding to the target store is acquired in the payment information acquisition step, performing a posting control step of accepting a post of a store review regarding the target store from the user corresponding to the payment information. An information processing method characterized by: An information processing program that can be read and executed by a computer,
An information processing program that causes the computer to function as an information processing apparatus according to any one of claims 1 to 5.

Images