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

Abstract

The present invention provides a payment app that improves user convenience when transferring electronic money between individuals.
[Solution] The information processing device of the present application is characterized by comprising an acquisition unit that acquires information about a first user who is the recipient in a person-to-person money transfer via a payment app and information about a second user who is the sender, an estimation unit that infers the relationship between the first and second users based on the information about the first and second users and infers the purpose of the money transfer from the second user to the first user from the relationship between the first and second users, a selection unit that selects a message corresponding to the purpose of the money transfer, a proposal unit that proposes the selected message to the second user, and a transmission unit that sends the message to the first user if the second user agrees to the proposal.
[Selected Figure] Figure 1

Description

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

A technology has been disclosed that allows for the efficient payment of rewards (tips) as part of the electronic payment process at brick-and-mortar stores.

Patent No. 7053924

However, while the above-mentioned conventional technology supports the payment of tips at physical stores, it does not support the sending of thank-you messages, etc. in private transfers, such as person-to-person transfers of electronic money via a payment app, to representatives, etc. who have made payments at physical stores.

This application has been made in light of the above, and aims to further improve user convenience when transferring electronic money between individuals using a payment app.

The information processing device according to the present application is characterized by comprising an acquisition unit that acquires information about a first user who is the recipient in a person-to-person remittance via a payment app and information about a second user who is the sender, an estimation unit that estimates the relationship between the first user and the second user based on the information about the first user and the information about the second user and estimates the purpose of the remittance from the second user to the first user from the relationship between the first user and the second user, a selection unit that selects a message corresponding to the purpose of the remittance, a proposal unit that proposes the selected message to the second user, and a transmission unit that transmits the message to the first user if the second user agrees to the proposal.

According to one aspect of the embodiment, it is possible to further improve the convenience for users when transferring electronic money between individuals using a payment app.

FIG. 1 is an explanatory diagram showing an overview of an information processing method according to an embodiment. FIG. 2 is an explanatory diagram showing an overview of an information processing method according to a specific embodiment. FIG. 3 is an explanatory diagram showing an overview of a method for making a message suggestion based on the payment history of the other party. FIG. 4 is a diagram illustrating an example of the configuration of an information processing system according to the embodiment. FIG. 5 is a diagram illustrating an example of the configuration of a terminal device according to the embodiment. FIG. 6 is a diagram illustrating an example of the configuration of a server device according to the embodiment. FIG. 7 is a diagram illustrating an example of the user information database. FIG. 8 is a diagram illustrating an example of the history information database. FIG. 9 is a diagram illustrating an example of the payment information database. FIG. 10 is a diagram showing an example of the remittance information database. FIG. 11 is a flowchart showing the first processing procedure (with remittance) according to the embodiment. FIG. 12 is a flowchart showing a second processing procedure (without remittance) according to the embodiment. FIG. 13 is a diagram illustrating an example of a hardware configuration.

Below, the information processing device, information processing method, and information processing program according to the present application will be described in detail with reference to the drawings. Note that the information processing device, information processing method, and information processing program according to the present application are not limited to these embodiments. In addition, the same components in the following embodiments will be denoted by the same reference numerals, and duplicated descriptions will be omitted.

[1. Overview of information processing method]
First, an overview of an information processing method performed by an information processing device according to an embodiment will be described with reference to Fig. 1. Fig. 1 is an explanatory diagram showing an overview of an information processing method according to an embodiment. Note that Fig. 1 will be described by taking as an example a case in which user convenience in person-to-person remittance of electronic money of a payment application is further improved.

As shown in FIG. 1, the information processing system 1 includes a terminal device 10 and a server device 100. The terminal device 10 and the server device 100 are connected to each other via a network N (see FIG. 4) in a wired or wireless manner so as to be able to communicate with each other. In this embodiment, the terminal device 10 cooperates with the server device 100.

The terminal device 10 is a smart device such as a smartphone or tablet terminal used by a user U, and is a mobile terminal device capable of communicating with any server device via a wireless communication network such as 5G (Generation) or LTE (Long Term Evolution). The terminal device 10 has a screen such as a liquid crystal display with a touch panel function, and accepts various operations on displayed data such as content, such as tapping, sliding, scrolling, etc., performed by the user U with a finger or a stylus. An operation performed on an area of the screen where the content is displayed may be considered to be an operation on the content. The terminal device 10 may be not only a smart device, but also an information processing device such as a desktop PC (Personal Computer) or a notebook PC.

The server device 100 is an information processing device that cooperates with the terminal device 10 of each user U and provides API (Application Programming Interface) services for various applications (hereinafter, apps) and the like, as well as various data, to the terminal device 10 of each user U, and is realized by a computer, a cloud system, or the like.

The server device 100 may also be an information processing device that provides some kind of web service online to the terminal device 10 of each user U. For example, the server device 100 may provide services such as Internet connection, search services, SNS (Social Networking Service), electronic commerce (EC), electronic payment, online games, online banking, online trading, accommodation and ticket reservations, video and music distribution, news, maps, route searches, route guidance, line information, operation information, and weather forecasts as web services. In practice, the server device 100 may cooperate with various servers that provide the above-mentioned web services, and may act as an intermediary for the web services or be responsible for processing the web services.

The server device 100 can acquire user information about the user U. For example, the server device 100 acquires information about the attributes of the user U, such as the gender, age, and area of residence of the user U. The server device 100 then stores and manages the information about the attributes of the user U together with identification information (such as a user ID) indicating the user U.

The server device 100 also acquires various history information (log data) indicating the behavior of the user U from the terminal device 10 of the user U or from various servers based on the user ID, etc. For example, the server device 100 acquires a location history, which is a history of the location and date and time of the user U, from the terminal device 10. The server device 100 also acquires a search history, which is a history of search queries entered by the user U, from a search server (search engine). The server device 100 also acquires a browsing history, which is a history of content viewed by the user U, from a content server. The server device 100 also acquires a purchase history (payment history), which is a history of product purchases and payment processing by the user U, from an electronic commerce server or a payment processing server. The server device 100 may also acquire a listing history and a sales history, which are a history of listings on the marketplace by the user U, from an electronic commerce server or a payment processing server. The server device 100 also acquires a posting history, which is a history of posts by the user U, from a posting server that provides a word-of-mouth posting service or an SNS server. The various servers and the like described above may be the server device 100 itself. In other words, the server device 100 may function as the various servers and the like described above.

The server device 100 also serves as a payment server, providing an electronic payment service related to payments (electronic payments) using the terminal device 10. For example, when the server device 100 acquires user identification information, which is identification information of user U displayed on the terminal device 10 of the user U, from a store terminal that has read the user identification information, store identification information that identifies the store, and payment details, or when the server device 100 acquires user identification information, store identification information, and payment details from the terminal device 10 that has read the store identification information, the server device 100 has a payment processing function that transfers electronic money according to the payment details from the account of user U indicated by the user identification information to the account indicated by the store identification information, based on the payment details.

1-1. Payment using terminal device 10
Here, prior to the information processing according to the embodiment, an example of payment (electronic payment) using the terminal device 10 will be described. In the following description, an example will be described in which a user U makes a payment using the terminal device 10 using a two-dimensional code (QR code (registered trademark)) arranged in a store, which indicates store identification information that identifies the store, but the embodiment is not limited to this. The example of payment described below can also be applied when an arbitrary user makes a payment at an arbitrary store using an arbitrary terminal device 10. 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. In addition, the QR code (registered trademark) is not limited to a two-dimensional code, and may be a three-dimensional code, etc.

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

In such a case, the server device 100 transfers electronic money in the amount indicated by the payment amount from the account of user U indicated by the user identification information to the account of the store indicated by the store identification information. The server device 100 then sends a notification to the terminal device 10 that the payment has been completed. In such a case, the terminal device 10 notifies that the payment has been made with electronic money by outputting a screen or a specified sound indicating that the payment has been completed.

A more detailed example will be described. For example, the store identification information installed in the store is a URL (Uniform Resource Locator) set for each store, and is linked to group identification information indicating the group to which the store belongs and group store identification information identifying the store in the group, and is managed so that the server device 100, which is a payment server, can refer to it. The URL that is the store identification information is a URL for accessing the server device 100. When the terminal device 10 photographs the store identification information, it accesses the URL indicated by the photographed store identification information and transmits the user identification information. In such a case, the server device 100 identifies the group identification information corresponding to the accessed URL, and identifies the electronic money account (sometimes displayed as "wallet") that is linked to the identified group identification information. Next, the server device 100 causes the terminal device 10 to display an amount input screen and input the amount. The server device 100 then identifies group identification information from the wallet associated with the user identification information received from the terminal device 10, and transfers the input amount of electronic money to the wallet associated with the identified group identification information. Note that the server device 100 may also transfer electronic money to a wallet associated with the group identification information and group store identification information.

Note that the payment using the terminal device 10 is not limited to the above-mentioned process. For example, the payment using the terminal device 10 may be made using a store terminal installed in a store. For example, the terminal device 10 displays user identification information for identifying the user U on a screen. In such a case, the store terminal installed in the store reads the user identification information displayed on the terminal device 10 and transmits payment information indicating the user identification information (or information indicated by the user identification information, i.e., information indicating the user U (e.g., user ID)), the payment amount, and information identifying the store to the server device 100. In such a case, the server device 100 may transfer electronic money in an amount indicated by the payment amount from the account of the user U indicated by the user identification information to the store's account, and notify the store terminal or the terminal device 10 of the fact that the payment has been completed by outputting a screen or a predetermined sound indicating that the payment has been completed.

More specifically, the terminal device 10 sends a payment request to the server device 100 together with the user identification information. In such a case, the server device 100 generates a one-time code, links the generated one-time code to the user identification information, and sends the one-time code to the terminal device 10. The terminal device 10 then displays the one-time code (i.e., information that identifies the user) on the screen. In such a case, the store terminal reads the one-time code displayed on the terminal device 10 and transmits the read one-time code, group identification information, group store identification information, and payment amount to the server device 100. The server device 100 then transfers electronic money equivalent to the payment amount from the wallet linked to the user identification information linked to the one-time code to the wallet linked to the group identification information and group store identification information.

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

In this way, in a payment using the terminal device 10, the payment app withdraws electronic money equivalent to the payment amount from the user's account and manages it as sales information for the affiliated store (different from deposits into the affiliated store account). In addition, at a specified time, based on the sales information, cash is deposited into the affiliated store's bank account in an amount equal to the sales minus a management fee. Note that electronic money may be deposited from the user's account into the affiliated store's electronic money account managed by the affiliated store, and the fee may be obtained from the affiliated store account managed by the affiliated store at the time of deposit or at a specified time. Furthermore, if the source of funds for a coupon provided to user U in relation to the payment app is borne by the affiliated store, the affiliated store will provide the coupon after deducting the amount of cash or electronic money borne when depositing cash into the bank account or when depositing electronic money into the affiliated store's account, etc.

With the above-mentioned payment methods and payment services, the affiliated store does not handle electronic money balances, and sales for each affiliated store using the above-mentioned payment methods and payment services are managed on the payment server. At this time, sales are not transferred to the affiliated store's account as electronic money balances, but are converted into cash and deposited in a bank account. When depositing, if the original funds for coupons are borne by the affiliated store, the amount of the sales minus the original funds for the coupons is transferred.

In this embodiment, coupons provided to user U in relation to the payment app are automatically applied in conjunction with payment. Therefore, user U does not need to present a coupon at the cash register. For example, when user U scans a two-dimensional code installed in a store (user scan), the server acquires a coupon ID associated with the user ID. Also, when the store scans a two-dimensional code presented by user U (store scan), the store acquires a one-time code corresponding to the two-dimensional code presented by user U, and the server acquires the user ID and coupon ID associated with the one-time code. In this case, the one-time code becomes information indicating user U.

The above-mentioned payment means and payment services are not limited to those for providing a price (settlement of debt) for the purchase of goods or the provision of services. For example, the above-mentioned payment means and payment services may have a function related to transfer between accounts held by multiple users. That is, the above-mentioned payment means and payment services may be services that control the transmission and reception of electronic money between accounts of any owner linked to the owner of electronic money, such as a user or a store. That is, the payment means and payment services according to the embodiment may be transaction means and transaction services that execute various controls for realizing the exchange of electronic money (not only various inter-account transfer controls via electronic money, but also controls related to exchanges between electronic money accounts and bank accounts, various credit processes such as installments and processes associated with bonus payments, and various controls related to the exchange of assets including electronic money) and may be provided in any form. In addition, the various controls realized by such transaction means and transaction services may include both control related to payment and control related to remittance, or only one of them. That is, a "transaction" is a concept that includes not only "settlement" related to electronic money, but also "remittance" of electronic money and various other processes. In other words, the server device 100 may be an information processing device that realizes a transaction means for controlling the exchange of electronic money between any owners.

For example, when transaction information is generated regarding electronic money transactions such as settlement and remittance, the server device 100 accepts from the user a choice of whether or not to receive a profit based on the transaction information, and if the user receives the profit, the server device 100 will grant the user a profit for conducting the transaction. In addition, if the user does not receive the profit, the server device 100 will grant the user a more favorable profit based on the user's behavior in the transaction service.

[1-2. Selection of message candidates to be sent from the sender to the recipient]
In this embodiment, the server device 100 transfers electronic money to a designated recipient (recipient) in response to a request from the remitter (remitter) in peer-to-peer (P2P) remittance. For example, when a remitter transfers electronic money to a recipient in order for the recipient to collect money from the remitter and pay a bill or other charges at a store or the like, the server device 100 transfers electronic money from the remitter's electronic money account to the recipient's electronic money account. At this time, the server device 100 selects a candidate message to be sent from the remitter to the recipient based on the recipient's settlement history. The server device 100 then transmits the selected candidate message to the remitter's terminal device 10 together with the remittance history to the recipient. If the remitter agrees (permits), the server device 100 transmits the message to the recipient. If there are multiple candidate messages, the remitter selects an appropriate message from the proposed candidate messages. The server device 100 then transmits the message selected by the remitter to the remitter.

In general, person-to-person remittances are used for splitting the bill at a drinking party, settling the bill when traveling with a group, collecting money for events and activities, sending money to children living alone, etc. However, in reality, the use of remittances is not limited to these examples.

In this embodiment, examples of user U are user U1, the recipient (recipient) of a person-to-person remittance, and user U2, the sender (source). Examples of terminal devices 10 are terminal device 10A of user U1 and terminal device 10B of user U2.

For example, as shown in FIG. 1, user U1 makes a payment using a payment app on terminal device 10A (step S1). At this time, server device 100 may obtain payment information of user U1 and accumulate the payment history of user U1. This allows server device 100 to obtain information about the place where the payment was made (a store such as an izakaya).

In the example of FIG. 1, electronic payment is made between the terminal device 10A and the store terminal 200. The store terminal 200 is an information processing device that is installed/placed in a physical store (or a facility or business) and is used for payment by the user U. The store terminal 200 may be movable (portable). The main body of the store terminal 200 may be a terminal device similar to the terminal device 10, or a server device similar to the server device 100. The store terminal 200 may also be an electronic cash register, a POS cash register, a POS terminal, a multi-copy machine, etc. When an electronic payment is made, the server device 100 can obtain payment information from the store terminal 200 (or the terminal device 10A) and accumulate it as a payment history.

Next, user U2 uses the payment app on terminal device 10B to transfer money to user U1 through person-to-person remittance (step S2). At this time, server device 100 may carry out or confirm user U2's person-to-person remittance and accumulate the history of user U2's person-to-person remittances (remittance history).

Next, the server device 100 checks the time (date and time, etc.) when user U2 remits the money and the location information (latitude and longitude, etc.) when the money is remitted, and the time (date and time, etc.) when user U1 makes the payment and the location information (latitude and longitude, etc.) when the payment is made (step S3).

Then, the server device 100 judges whether the time and location information of user U2 at the time of remittance and the time and location information of user U1 at the time of payment satisfy a predetermined condition (step S4). For example, the server device 100 judges whether the condition is satisfied that the time of payment by user U1 is within a predetermined time (e.g., within 10 minutes) of the time of remittance by user U2, and the distance between the location information of user U1 at the time of payment and the location information of user U2 at the time of remittance is within a predetermined range (e.g., within 500 meters).

Next, if the time and location information of user U2 at the time of remittance and the time and location information of user U1 at the time of payment satisfy the above-mentioned predetermined conditions, the server device 100 selects and proposes to user U2 an appropriate candidate message according to the satisfied conditions (step S5). For example, if the conditions are satisfied that the time of payment by user U1 is within a predetermined time (e.g., within 10 minutes) from the time of remittance by user U2, and the distance between the location information of user U1 at the time of payment and the location information of user U2 at the time of remittance is within a predetermined range (e.g., within 500 meters), the server device 100 assumes that the transaction is a money transaction at a drinking party between user U1 and user U2, and proposes a message saying "Thank you, drinking party organizer." As a result, the proposed message is displayed on the terminal device 10B of user U2. In this embodiment, the server device 100 can propose an appropriate message depending on the type of payment, location information, and last message (purpose of remittance). Select the message displayed on user U2's terminal device 10B or agree (permit) to send the message.

Next, the server device 100 transmits the message selected by user U2 in response to the proposed candidate messages to the remittance destination user U1 (step S6). For example, if user U2 agrees (allows) to the proposed message "Thank you, drinking party organizer," the server device 100 transmits the message "Thank you, drinking party organizer" to the terminal device 10A of user U1.

Alternatively, when transferring money between individuals from the sender (remitter) to the recipient (recipient), the server device 100 selects candidate messages from the sender to the recipient based on remittance histories from other users (other senders) to the recipient, and sends the selected candidate messages to the sender's terminal device 10 to suggest them. For example, the server device 100 selects candidate messages from the sender to the recipient based on remittance histories from multiple senders to the recipient, and sends the selected candidate messages to the terminal device 10 of each sender to suggest them. The sender selects a desired message from the candidate messages displayed on the terminal device 10. The server device 100 sends the message selected by the sender to the recipient's terminal device 10.

In other words, the server device 100 determines the message based on the relationship between the payment history of the recipient (recipient) and the remittance history of the remittance side (sender). For example, the server device 100 determines the message depending on which payment of the recipient (remittance destination) is related to the purpose of the remittance of the remittance side (sender).

At this time, the server device 100 may estimate the purpose of the remittance from the remitter based on the payment history of the remittance destination (electronic money usage history, use) and select a candidate message corresponding to the purpose of the remittance. If there are multiple candidates for the estimated purpose of the remittance, the server device 100 may select a candidate message corresponding to the purpose of the remittance selected by the remitter from among the estimated candidates for the purpose of the remittance.

The server device 100 may also select corresponding message candidates based on the time (date, time zone, time of day, etc.) of the remittance destination's payment. Furthermore, the server device 100 may select corresponding message candidates based on the remittance destination's location information. For example, the server device 100 may select corresponding message candidates based on the remittance destination's location information at the time of payment.

Note that message candidates may be predetermined for each condition. The server device 100 may select message candidates that include the name or category of the store where the payment was made and that correspond to the purpose of the remittance.

For example, if the server device 100 is able to confirm that payment was made at a coffee shop based on the remittance recipient's payment history (or the location information of the remittance recipient and the remittance source), it may select a candidate message such as "Thank you for the coffee shop." Also, if the server device 100 is able to confirm that payment was made in a taxi based on the remittance recipient's payment history (or the location information of the remittance recipient and the remittance source), it may select a candidate message such as "Thank you for shopping at the convenience store."

The server device 100 may use machine learning to learn the messages selected by the remitter and build an estimation model to estimate the message (or a candidate message). The server device 100 may also use this estimation model to estimate the message that the remitter is likely to select, and automatically send the estimated message to the remitter. The server device 100 may also request permission from the remitter to set up automatic message sending (whether or not).

1-3. Overview of the embodiment
A specific embodiment of the present invention will be described with reference to Fig. 2. Fig. 2 is an explanatory diagram showing an overview of an information processing method according to a specific embodiment.

For example, as shown in FIG. 2, the sender user U2 designates the remittance destination user and calls up the remittance screen on the payment application of the terminal device 10B (step S11). Here, the sender user U2 designates the remittance destination user U1 as the remittance destination user.

Next, the server device 100 generates a remittance screen with content for person-to-person remittance (step S12).

Next, in response to the call of the remittance screen, the server device 100 provides the remittance screen with content to the terminal device 10B of the remittance source user U2 (step S13).

Next, the remittance source user U2 executes a remittance instruction on the remittance screen with content displayed on the terminal device 10B (step S14). The remittance instruction also includes the remittance amount.

Next, in response to the remittance instruction, the server device 100 transfers electronic money from the remittance source user's account to the remittance destination user's account (step S15). Here, the server device 100 transfers electronic money equivalent to the instructed remittance amount from the remittance source user U2's account to the remittance destination user U1's account.

Next, the server device 100 provides the remittance destination user with a remittance completion screen indicating that electronic money has been remitted from the remittance source user (step S16). Here, the server device 100 provides the terminal device 10A of the remittance destination user U1 with a remittance completion screen indicating that money has been remitted from the remittance source user U2.

Then, the server device 100 decides whether to make a message suggestion based on the remittance history of the remittance source user and the payment history of the remittance destination user (step S17). At this time, the server device 100 decides to make a message suggestion if the remittance date and location in the remittance history of the remittance source user U2 and the payment date and location in the payment history of the remittance destination user U1 satisfy a predetermined condition.

Next, when making a message suggestion, the server device 100 selects and acquires a message from a table related to message candidates (message candidate table) (step S18). Note that the table related to message candidates may be a database that accumulates message candidates. Furthermore, the server device 100 may estimate message candidates using an estimation model obtained by machine learning on messages.

Then, the server device 100 displays message suggestions in the chat room to the remittance source user (step S19). Here, the server device 100 presents a guide to the chat room to the terminal device 10B of the remittance source user U2, and displays the message suggestions in the chat room.

Next, the sender user U2 agrees to the message proposal displayed on the terminal device 10B (step S20). If there are multiple message candidates related to the message proposal, user U2 selects the desired message from the presented message candidates and agrees to it.

Then, the server device 100 transmits the message, which has been agreed to by the remittance source user, to the remittance destination user (step S21). Here, the server device 100 transmits the message, which has been agreed to by the remittance source user U2, to the terminal device 10A of the remittance destination user U1.

[1-4. Other Perspectives]
From another perspective, the server device 100 estimates whether a payment by the first user is related to a second user based on information (first user information) related to a first user (user U1) and information (second user information) related to a second user (user U2) (e.g., location information, time information, etc.), and provides a message corresponding to the payment estimated to be related to the second user. For example, the server device 100 finds a payment made at an izakaya or restaurant by comparing location information, time information, etc. from the payment history of the first user and a payment made by a person in advance or a payment made by all members, and provides the second user with a message of thanks for the payment made by an person in advance or a payment made by all members as a candidate.

Specifically, the server device 100 acquires location information of the first user at the time of payment and location information of the second user at the time of remittance, and if the location of the first user at the time of payment and the location of the second user at the time of remittance are within a predetermined range, it presumes that the payment made by the first user using the payment app is related to the second user, and if there is a relationship with the second user, selects a message corresponding to the payment.

The server device 100 also acquires date and time information of the first user's payment and the second user's remittance, and if the date and time of the first user's payment and the date and time of the second user's remittance are within a predetermined range, it presumes that the payment made by the first user using the payment app is related to the second user, and if there is a relationship with the second user, selects a message corresponding to the payment.

The server device 100 also acquires the payment information of the first user and the remittance information of the second user, and if the payment amount of the first user and the remittance amount of the second user are within a predetermined range, it presumes that the payment made by the first user using the payment app is related to the second user, and if there is a relationship with the second user, selects a message corresponding to the payment.

At this time, the server device 100 may select and suggest a candidate message to be sent from the second user to the first user, who has transferred electronic money to the first user by person-to-person transfer, based on the payment history of the first user who has paid electronic money at a store or the like. The second user selects an appropriate message from the suggested candidate messages. The server device 100 transmits the message selected by the second user to the first user. Alternatively, the server device 100 may select and automatically transmit a message to be sent from the second user who has transferred electronic money to the first user by person-to-person transfer, based on the payment history of the first user who has paid electronic money at a store or the like.

Furthermore, the server device 100 may infer the purpose of sending the message from the first user information and the second user information. For example, the server device 100 infers that the second user and the first user are in a parent-child relationship based on the first user information and the second user information, and infers the purpose of the remittance from the second user to the first user.

The server device 100 also estimates the purpose of the first user and the second user from the name or category (such as an izakaya) of the store where the first user and the second user made the payment when they were within a specified range at the time of the payment, based on the location information of each of the first user and the second user and the payment history of the first user.

The server device 100 also estimates the purpose of when the first user and the second user were together from the first user information and the second user information, and selects and suggests message candidates according to the purpose. For example, the server device 100 estimates whether the reason the first user and the second user were together was a date from the location information and payment history of each user, and if it is estimated to be a date, selects and suggests message candidates according to the situation.

In addition, the server device 100 estimates the degree of intimacy between the first and second users based on past messages and the history of person-to-person remittances at the time of payment (remittance history), and selects and suggests message candidates according to the degree of intimacy.

The server device 100 may use machine learning to learn messages selected by the second user and build an estimation model to estimate messages (or candidates for messages). The server device 100 may also use this estimation model to estimate messages that the second user is likely to select and automatically send the estimated messages to the first user. The second user may be asked to give permission to set up automatic message sending (whether or not).

[1-5. Message suggestions based on the other party's payment history]
In reality, even if the first user (user U1) makes a payment including the payment for the second user (user U2), there are cases where the second user (user U2) does not remit money to the first user (user U1). For example, when the first user (user U1) treats the second user (user U2) to a restaurant, the second user (user U2) does not remit money to the first user (user U1). Even in such a case, a method of proposing a message based only on the payment history of the other party so that the second user (user U2) can send a thank-you message to the first user (user U1) will be described. FIG. 3 is an explanatory diagram showing an overview of a method of proposing a message based on the payment history of the other party.

For example, as shown in FIG. 3, user U1 makes a payment using a payment app on terminal device 10A (step S31). In the example of FIG. 3, electronic payment is made between terminal device 10A and the store terminal 200.

Next, the server device 100 acquires the payment information of user U1 from the terminal device 10A of user U1 or the store terminal 200 (step S32). At this time, the server device 100 may store the payment information of user U1 as the payment history of user U1.

Next, user U2 uses the payment app of terminal device 10B to designate (or select) user U1 and call up a talk room (chat room) (step S33). That is, user U2 opens a talk room in which he can send and receive messages to user U1.

Then, the server device 100 acquires the payment history of user U1 (step S34). That is, the server device 100 refers to the accumulated payment history of user U1. At this time, the server device 100 may use the payment information of user U1 acquired in step S32 (the most recent payment information) as the payment history of user U1.

Next, the server device 100 determines whether the payment history of user U1 satisfies a predetermined condition (step S35). For example, the server device 100 may determine, as a predetermined condition (first condition), whether a predetermined time period elapsed between the most recent payment by user U1 and the call of the talk room. The server device 100 may also determine, as a predetermined condition (second condition), whether the most recent payment by user U1 and the call of the talk room were made within a predetermined distance (whether the most recent payment location (location) of user U1 and the location (location) from which the talk room was called are within a predetermined range). The server device 100 may also determine, as a predetermined condition (third condition), whether the most recent payment by user U1 was a small amount payment of a predetermined amount or less. Note that these are merely examples.

At this time, the server device 100 determines whether there is a remittance history of user U2 that corresponds to the payment history of user U1, and if there is a remittance history of user U2 that corresponds to the payment history of user U1, it may proceed to step S4 in FIG. 1 (or step S17 in FIG. 2), and if there is no remittance history of user U2 that corresponds to the payment history of user U1, it may continue the series of processes shown below. Here, we will explain the case where there is no remittance history of user U2 that corresponds to the payment history of user U1.

Next, if the payment history of user U1 satisfies a predetermined condition, the server device 100 generates a message proposal (content) in the chat room opened by user U2 (step S36). The content is, for example, a message proposal such as "Thank you for the meal." The message proposal may be multiple message candidates, or may be a message or a stamp, etc. At this time, the server device 100 may infer the purpose of the payment of user U1 and select multiple message candidates, stamps, etc. that are considered appropriate as a message to be sent from user U2 to user U1. The server device 100 may also infer the purpose of the payment of user U1 from the result of the above determination and select multiple message candidates, stamps, etc.

Then, the server device 100 displays message suggestions in the talk room opened on the terminal device 10B of user U2 (step S37).

Next, user U2 agrees to the message proposal displayed in the talk room of terminal device 10B (step S38). Note that if the message proposal includes multiple message candidates, stamps, etc., user U2 may select and agree to the one that he or she considers appropriate (the one that he or she wishes to send).

Then, the server device 100 transmits the message to which user U2 has agreed to the message to the terminal device 10A of user U1 (step S39). For example, the server device 100 transmits a message such as "Thank you for the meal" to the terminal device 10A of user U1. The terminal device 10A of user U1 then displays the transmitted message. The message may be displayed in the talk room of the terminal device 10A of user U1.

This allows user U2 to send a message of thanks to user U1 for treating them to a meal without having to make a person-to-person remittance.

2. Example of information processing system configuration
Next, a configuration of an information processing system 1 including a server device 100 according to an embodiment will be described with reference to Fig. 4. Fig. 4 is a diagram showing an example of a configuration of the information processing system 1 according to an embodiment. As shown in Fig. 4, the information processing system 1 according to an embodiment includes a terminal device 10 and a server device 100. These various devices are connected to each other via a network N so as to be able to communicate with each other by wire or wirelessly. The network N is, for example, a local area network (LAN) or a wide area network (WAN) such as the Internet.

Furthermore, the number of devices included in the information processing system 1 shown in FIG. 4 is not limited to that shown. For example, in FIG. 4, only one terminal device 10 is shown to simplify the illustration, but this is merely an example and is not limiting, and there may be two or more devices.

The terminal device 10 is an information processing device used by a user U. For example, the terminal device 10 is a smart device such as a smartphone or a tablet terminal, a mobile phone such as a feature phone, a personal computer (PC), a personal digital assistant (PDA), a game console or AV device with a communication function, an information appliance or digital appliance, a car navigation system, a wearable device such as a smart watch or a head-mounted display, smart glasses, etc. The terminal device 10 may also be a house or building, a car, a home appliance, an electronic device, etc. that is compatible with the Internet of Things (IOT).

In addition, the terminal device 10 can connect to the network N via a wireless communication network such as LTE (Long Term Evolution), 4G (4th Generation), or 5G (5th Generation: 5th generation mobile communication system), or via short-range wireless communication such as Bluetooth (registered trademark) or wireless LAN (Local Area Network), and communicate with the server device 100.

The server device 100 is, for example, a computer such as a PC or a blade server, or a mainframe or a workstation. The server device 100 may also be realized by cloud computing.

3. Example of terminal device configuration
Next, the configuration of the terminal device 10 will be described with reference to Fig. 5. Fig. 5 is a diagram showing an example of the configuration of the terminal device 10. As shown in Fig. 5, the terminal device 10 includes a communication unit 11, a display unit 12, an input unit 13, a positioning unit 14, a sensor unit 20, a control unit 30 (controller), and a storage unit 40.

(Communication unit 11)
The communication unit 11 is connected to a network N (see FIG. 4 ) by wire or wirelessly, and transmits and receives information to and from the server device 100 via the network N. For example, the communication unit 11 is realized by a network interface card (NIC), an antenna, or the like.

(Display unit 12)
The display unit 12 is a display device that displays various information such as position information. For example, the display unit 12 is a liquid crystal display (LCD) or an organic electro-luminescent display (OLED). The display unit 12 is also a touch panel display, but is not limited to this.

(Input unit 13)
The input unit 13 is an input device that accepts various operations from the user U. For example, the input unit 13 has buttons for inputting characters, numbers, and the like. The input unit 13 may be an input/output port (I/O port) or a Universal Serial Bus (USB) port, and the like. In addition, when the display unit 12 is a touch panel display, a part of the display unit 12 functions as the input unit 13. In addition, the input unit 13 may be a microphone that accepts voice input from the user U, and the like. The microphone may be wireless.

(Positioning unit 14)
The positioning unit 14 receives signals (radio waves) transmitted from satellites of a GPS (Global Positioning System), and acquires position information (e.g., latitude and longitude) indicating the current position of the terminal device 10 based on the received signals. That is, the positioning unit 14 measures the position of the terminal device 10. Note that the GPS is merely an example of a GNSS (Global Navigation Satellite System).

The positioning unit 14 can also measure the position using various methods other than GPS. For example, the positioning unit 14 may measure the position using various communication functions of the terminal device 10 as an auxiliary positioning means for position correction, etc., as described below.

(Wi-Fi positioning)
For example, the positioning unit 14 uses the Wi-Fi (registered trademark) communication function of the terminal device 10 or a communication network provided by each communication company to measure the position of the terminal device 10. Specifically, the positioning unit 14 performs Wi-Fi communication or the like and measures the distance to a nearby base station or access point to measure the position of the terminal device 10.

(Beacon positioning)
Furthermore, the positioning unit 14 may measure the position by using a Bluetooth (registered trademark) function of the terminal device 10. For example, the positioning unit 14 measures the position of the terminal device 10 by connecting to a beacon transmitter connected by the Bluetooth (registered trademark) function.

(geomagnetic positioning)
In addition, the positioning unit 14 locates the position of the terminal device 10 based on a geomagnetic pattern of a structure that has been measured in advance and a geomagnetic sensor provided in the terminal device 10 .

(RFID positioning)
Furthermore, for example, if the terminal device 10 has a function of an RFID (Radio Frequency Identification) tag equivalent to a contactless IC card used at station ticket gates, stores, etc., or has a function of reading an RFID tag, the location of use is recorded together with information on a payment or the like made by the terminal device 10. The positioning unit 14 may obtain such information to measure the location of the terminal device 10. Furthermore, the location may be measured by an optical sensor, an infrared sensor, or the like provided in the terminal device 10.

If necessary, the positioning unit 14 may use one or a combination of the positioning means described above to determine the position of the terminal device 10.

(Sensor unit 20)
The sensor unit 20 includes various sensors mounted on or connected to the terminal device 10. The connection may be wired or wireless. For example, the sensors may be detection devices other than the terminal device 10, such as wearable devices and wireless devices. In the example shown in FIG. 5, the sensor unit 20 includes an acceleration sensor 21, a gyro sensor 22, an air pressure sensor 23, a temperature sensor 24, a sound sensor 25, a light sensor 26, a magnetic sensor 27, and an image sensor (camera) 28.

Note that the above-mentioned sensors 21 to 28 are merely examples and are not limiting. In other words, the sensor unit 20 may be configured to include some of the sensors 21 to 28, or may include other sensors such as a humidity sensor in addition to or instead of the sensors 21 to 28.

The acceleration sensor 21 is, for example, a three-axis acceleration sensor, and detects the physical movement of the terminal device 10, such as the direction of movement, speed, and acceleration of the terminal device 10. The gyro sensor 22 detects the physical movement of the terminal device 10, such as the tilt in three axial directions, based on the angular velocity of the terminal device 10. The air pressure sensor 23 detects, for example, the air pressure around the terminal device 10.

Since the terminal device 10 is equipped with the above-mentioned acceleration sensor 21, gyro sensor 22, air pressure sensor 23, etc., it is possible to determine the position of the terminal device 10 using technology such as Pedestrian Dead-Reckoning (PDR) that utilizes these sensors 21 to 23. This makes it possible to obtain indoor position information that is difficult to obtain using positioning systems such as GPS.

For example, the number of steps, walking speed, and distance walked can be calculated using a pedometer that uses the acceleration sensor 21. In addition, the gyro sensor 22 can be used to know the user U's direction of travel, line of sight, and body inclination. In addition, the air pressure detected by the air pressure sensor 23 can be used to know the altitude and floor on which the user U's terminal device 10 is located.

The air temperature sensor 24 detects, for example, the air temperature around the terminal device 10. The sound sensor 25 detects, for example, sound around the terminal device 10. The light sensor 26 detects the illuminance around the terminal device 10. The magnetic sensor 27 detects, for example, the geomagnetism around the terminal device 10. The image sensor 28 captures an image around the terminal device 10.

The above-mentioned air pressure sensor 23, temperature sensor 24, sound sensor 25, light sensor 26, and image sensor 28 can detect the environment and situation around the terminal device 10 by detecting air pressure, temperature, sound, and illuminance, and capturing images of the surroundings. In addition, it becomes possible to improve the accuracy of the location information of the terminal device 10 based on the environment and situation around the terminal device 10.

(Control unit 30)
The control unit 30 includes, for example, a microcomputer having a central processing unit (CPU), a read only memory (ROM), a RAM, an input/output port, and various other circuits. The control unit 30 may also be configured with hardware such as an integrated circuit, for example, an application specific integrated circuit (ASIC) or a field programmable gate array (FPGA). The control unit 30 includes a transmitting unit 31, a receiving unit 32, and a processing unit 33.

(Transmitter 31)
The transmission unit 31 can transmit, for example, various information input by the user U using the input unit 13, various information detected by each sensor 21 to 28 mounted on or connected to the terminal device 10, and location information of the terminal device 10 measured by the positioning unit 14 to the server device 100 via the communication unit 11.

(Receiving unit 32)
The receiving unit 32 can receive various information provided by the server device 100 and requests for various information from the server device 100 via the communication unit 11 .

(Processing Unit 33)
The processing unit 33 controls the entire terminal device 10, including the display unit 12, etc. For example, the processing unit 33 can output various information transmitted by the transmission unit 31 and various information received from the server device 100 by the reception unit 32 to the display unit 12 for display.

(Memory unit 40)
The storage unit 40 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 drive (HDD), a solid state drive (SSD), an optical disk, etc. Various programs and various data are stored in the storage unit 40.

4. Example of Server Device Configuration
Next, the configuration of the server device 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 server device 100 according to the embodiment. As shown in Fig. 6, the server device 100 includes a communication unit 110, a storage unit 120, and a control unit 130.

(Communication unit 110)
The communication unit 110 is realized by, for example, a network interface card (NIC), etc. The communication unit 110 is also connected to a network N (see FIG. 4) in a wired or wireless manner.

(Memory unit 120)
The storage unit 120 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 HDD, an SSD, an optical disk, etc. As shown in Fig. 6, the storage unit 120 has a user information database 121, a history information database 122, a payment information database 123, and a remittance information database 124.

(User Information Database 121)
The user information database 121 stores user information related to the user U. For example, the user information database 121 stores various information such as attributes of the user U. Fig. 7 is a diagram showing an example of the user information database 121. In the example shown in Fig. 7, the user information database 121 has items such as "User ID (Identifier)", "Age", "Gender", "Home", "Workplace", and "Interests".

"User ID" indicates identification information for identifying user U. Note that "user ID" may be contact information for user U (telephone number, email address, etc.) or may be identification information for identifying user U's terminal device 10.

Furthermore, "age" indicates the age of user U identified by the user ID. Note that "age" may be information indicating the specific age of user U (e.g., 35 years old) or information indicating the generation of user U (e.g., 30s). Alternatively, "age" may be information indicating user U's date of birth or information indicating user U's generation (e.g., born in the 1980s). Furthermore, "gender" indicates the gender of user U identified by the user ID.

"Home" indicates the location information of the home of user U, which is identified by the user ID. In the example shown in FIG. 7, "Home" is illustrated as an abstract code such as "LC11", but it may also be latitude and longitude information, etc. For example, "Home" may also be the name of a region or an address.

"Workplace" indicates the location information of the workplace (school in the case of a student) of user U identified by the user ID. In the example shown in FIG. 7, "workplace" is illustrated as an abstract code such as "LC12", but it may also be latitude and longitude information, etc. For example, "workplace" may also be the name of a region or an address.

Furthermore, "interests" indicate the interests of user U identified by the user ID. In other words, "interests" indicate subjects in which user U identified by the user ID is highly interested. For example, "interests" may be search queries (keywords) entered by user U into a search engine. Note that, in the example shown in FIG. 7, one "interest" is illustrated for each user U, but there may be multiple "interests."

For example, in the example shown in FIG. 7, the age of user U identified by user ID "U1" is "20s" and the gender is "male." Also, for example, user U identified by user ID "U1" indicates that his/her home address is "LC11." Also, for example, user U identified by user ID "U1" indicates that his/her workplace is "LC12." Also, for example, user U identified by user ID "U1" indicates that he/she is interested in "sports."

In the example shown in FIG. 7, abstract values such as "U1", "LC11", and "LC12" are used to illustrate the data, but it is assumed that specific information such as character strings and numerical values is stored in "U1", "LC11", and "LC12". In the following figures relating to other information, abstract values may also be illustrated.

The user information database 121 may store various information according to the purpose, not limited to the above. For example, the user information database 121 may store various information related to the terminal device 10 of the user U. The user information database 121 may also store information related to the attributes of the user U, such as demographic attributes, psychographic attributes, geographic attributes, and behavioral attributes. For example, the user information database 121 may store information such as name, family structure, place of origin (hometown), occupation, job title, income, qualifications, type of residence (detached house, apartment, etc.), whether or not the user has a car, commuting time, commuting route, commuter pass section (station, line, etc.), frequently used station (other than the nearest station to home or workplace), extracurricular activities (location, time period, etc.), hobbies, interests, and lifestyle.

(History information database 122)
The history information database 122 stores various information related to history information (log data) indicating the behavior of the user U. Fig. 8 is a diagram showing an example of the history information database 122. In the example shown in Fig. 8, the history information database 122 has items such as "user ID", "location history", "search history", "browsing history", "purchase history", and "posting history".

"User ID" refers to identification information for identifying user U. "Location history" refers to location history, which is a history of user U's location and movements. "Search history" refers to search history, which is a history of search queries entered by user U. "Browse history" refers to browse history, which is a history of content viewed by user U. "Purchase history" refers to purchase history, which is a history of purchases made by user U. "Post history" refers to posting history, which is a history of posts made by user U. "Post history" may include questions about user U's possessions.

For example, in the example shown in FIG. 8, user U identified by user ID "U1" moves as shown in "location history #1," searches as shown in "search history #1," views content as shown in "browsing history #1," purchases specific products at specific stores as shown in "purchase history #1," and posts as shown in "post history #1."

In the example shown in FIG. 8, abstract values such as "U1", "Location History #1", "Search History #1", "Browse History #1", "Purchase History #1", and "Post History #1" are used for illustration, but specific information such as character strings and numerical values is stored in "U1", "Location History #1", "Search History #1", "Browse History #1", "Purchase History #1", and "Post History #1".

The history information database 122 may store various information depending on the purpose, not limited to the above. For example, the history information database 122 may store the usage history of a specific service by the user U. The history information database 122 may also store the history of the user U's visit to a physical store or the history of the user U's visit to a facility. The history information database 122 may also store the payment history of payments (electronic payments) made using the user U's terminal device 10.

(Payment information database 123)
The payment information database 123 stores various information related to history information (log data) of payments made using the payment app by the user U. Fig. 9 is a diagram showing an example of the payment information database 123. In the example shown in Fig. 9, the payment information database 123 has items such as "user ID", "payment ID", "store ID", "payment date", "payment amount", and "location".

"User ID" indicates identification information for identifying user U who is the sender of the remittance. Furthermore, "payment ID" indicates identification information for identifying each payment made by user U using the payment app. Furthermore, "store ID" indicates identification information for identifying the store of the other party (payment destination) where the payment was made using the payment app. Note that the store ID may be the name or category of the store, etc. Furthermore, a store is merely one example. In reality, it may be transportation, a public facility, or other places where payment can be made using the payment app. Furthermore, "payment date" indicates the date on which the payment was made. Note that the payment date may be indicated by the year, month, day, day of the week, date, time, time zone, etc. Furthermore, "payment amount" indicates the amount paid by user U in the payment using the payment app. Furthermore, "location" indicates the location or place where the payment was made by user U using the payment app. Note that the location may be indicated by latitude and longitude, or may be indicated by an address, place name, facility name, etc.

For example, in the example shown in FIG. 9, user U1, identified by user ID "U1", paid electronic money for the payment amount of "￥10,000" to store ID "Izakaya #A" on payment date "2022/10/30" in a payment identified by payment ID "0011", and user U1 was in the location "Shinjuku" at that time.

The payment information database 123 may store various information depending on the purpose, not limited to the above. For example, the payment information database 123 may store messages exchanged at the time of payment. Furthermore, the payment information database 123 may store information on the remittance source user when a remittance is made within a specified time before or after a payment.

(Remittance Information Database 124)
The remittance information database 124 stores various information related to the history information (log data) of person-to-person remittances of the user U. Fig. 10 is a diagram showing an example of the remittance information database 124. In the example shown in Fig. 10, the remittance information database 124 has items such as "user ID", "remittance ID", "remittance destination", "remittance date", "remittance amount", and "location".

"User ID" indicates identification information for identifying user U who is the sender of the remittance. Furthermore, "remittance ID" indicates identification information for identifying each person-to-person remittance made by user U. Furthermore, "remittance destination" indicates the recipient to whom user U remits electronic money by person-to-person remittance. Furthermore, "remittance date" indicates the date on which person-to-person remittance was made by user U. Note that the remittance date may be indicated by the year, month, day, day of the week, date, time, time zone, etc. Furthermore, "remittance amount" indicates the amount remitted by user U by person-to-person remittance. Furthermore, "location" indicates the location or place where the person-to-person remittance was made by user U. Note that the location may be indicated by latitude and longitude, or may be indicated by an address, place name, facility name, etc.

For example, in the example shown in FIG. 10, user U2, identified by user ID "U2", remitted electronic money in the amount of "5,000 yen" to user U1, the remittance destination, identified by user ID "U1", on remittance date "2022/10/30" at location "Shinjuku" in a person-to-person remittance identified by remittance ID "0021".

The remittance information database 124 may store various information depending on the purpose, not limited to the above. For example, the remittance information database 124 may store messages exchanged when remittances are made. The remittance information database 124 may also store information regarding whether the remittance is a regular remittance that is automatically made according to a set schedule.

(Control unit 130)
Returning to Fig. 6, the description will be continued. The control unit 130 is a controller, and is realized by, for example, a central processing unit (CPU), a micro processing unit (MPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or the like, executing various programs (corresponding to an example of an information processing program) stored in a storage device inside the server device 100 using a storage area such as a RAM as a working area. In the example shown in Fig. 6, the control unit 130 has an acquisition unit 131, an estimation unit 132, a selection unit 133, a proposal unit 134, a transmission unit 135, a provision unit 136, and a determination unit 137.

(Acquisition unit 131)
The acquisition unit 131 acquires a search query input by a user U (user). For example, when the user U inputs a search query into a search engine or the like to perform a keyword search, the acquisition unit 131 acquires the search query via the communication unit 110. That is, the acquisition unit 131 acquires keywords input by the user U into a search box of a search engine, a site, or an app via the communication unit 110.

The acquisition unit 131 also acquires user information about the user U via the communication unit 110. For example, the acquisition unit 131 acquires identification information (such as a user ID) indicating the user U, location information of the user U, attribute information of the user U, and the like from the terminal device 10 of the user U. The acquisition unit 131 may also acquire identification information indicating the user U, attribute information of the user U, and the like when registering the user U. Then, the acquisition unit 131 registers the user information in the user information database 121 of the storage unit 120.

The acquisition unit 131 also acquires various types of history information (log data) indicating the behavior of the user U via the communication unit 110. For example, the acquisition unit 131 acquires various types of history information indicating the behavior of the user U from the terminal device 10 of the user U, or from various servers, etc. based on the user ID, etc. Then, the acquisition unit 131 registers the various types of history information in the history information database 122 of the storage unit 120.

Here, the acquisition unit 131 acquires the payment history of user U1 (recipient user) in the payment app and the remittance history of user U2 (source user) in person-to-person remittances.

From another perspective, the acquisition unit 131 acquires information about user U1 (first user) who is the recipient in a person-to-person remittance via a payment app, and information about user U2 (second user) who is the sender. For example, the acquisition unit 131 acquires location information of user U1 at the time of payment and location information of user U2 at the time of remittance. The acquisition unit 131 also acquires date and time information of user U1 at the time of payment and date and time information of user U2 at the time of remittance. The acquisition unit 131 also acquires payment information of user U1 and remittance information of user U2.

(Estimation unit 132)
The estimation unit 132 estimates the relationship between user U1 and user U2 based on information about user U1 and information about user U2, and estimates the purpose of the remittance from user U2 to user U1 from the relationship between user U1 and user U2.

For example, the estimation unit 132 estimates whether a payment made by user U1 using a payment app is related to user U2, based on information about user U1 and information about user U2.

At this time, if the location of user U1 at the time of payment and the location of user U2 at the time of remittance are within a predetermined range, the estimation unit 132 estimates that the payment made by user U1 using the payment app is related to user U2.

In addition, if the payment date and time of user U1 and the remittance date and time of user U2 are within a predetermined range, the estimation unit 132 estimates that the payment made by user U1 using the payment app is related to user U2.

In addition, if the payment amount of user U1 and the remittance amount of user U2 are within a predetermined range, the estimation unit 132 estimates that the payment made by user U1 using the payment app is related to user U2.

In addition, based on the information about user U1 and the information about user U2, the estimation unit 132 estimates that user U2 and user U1 are in a parent-child relationship, and estimates the purpose of the remittance from user U2 to user U1.

The estimation unit 132 also estimates the purpose of sending the message from the payment destination when user U1 and user U2 were within a specified range at the time of payment.

The estimation unit 132 also estimates the purpose of users U1 and U2 when they were together, based on the information about users U1 and U2. The estimation unit 132 also estimates the degree of intimacy between users U1 and U2, based on the information about users U1 and U2.

(Selection Unit 133)
The selection unit 133 selects candidates for messages from user U2 to user U1 based on the relationship between the payment history of user U1 and the remittance history of user U2.

For example, if there is a payment history of user U1 that corresponds to a remittance history of user U2, the selection unit 133 selects a candidate message from user U2 to user U1.

The selection unit 133 also selects candidates for messages from user U2 to user U1 based on the remittance history of other user U2 to user U1. For example, the selection unit 133 selects candidates for messages from user U2 to user U1 based on the remittance history of multiple users U2 to user U1.

The selection unit 133 also estimates the purpose of the remittance of user U2 based on the payment history of user U1, and selects candidate messages corresponding to the purpose of the remittance. For example, the selection unit 133 selects candidate messages that include the name or category of the store where the payment corresponding to the purpose of the remittance was made. Note that the selection unit 133 may be the same as the estimation unit 132 or may be a part of the estimation unit 132.

The selection unit 133 also selects candidate messages from user U2 to user U1 based on the time of user U1's payment. The selection unit 133 also selects candidate messages from user U2 to user U1 based on the location information at the time of user U1's payment.

From another perspective, the selection unit 133 selects a message corresponding to the estimated purpose of the remittance. For example, when a payment made by user U1 using a payment app has a relationship with user U2, the selection unit 133 selects a message corresponding to the payment. Furthermore, the selection unit 133 selects a message corresponding to the estimated purpose. Furthermore, the selection unit 133 selects a message according to the degree of intimacy.

(Proposal Unit 134)
The suggestion unit 134 suggests the selected message candidates to the user U2 via the communication unit 110. From another perspective, the suggestion unit 134 suggests the selected message to the user U2 via the communication unit 110.

(Transmitting Unit 135)
The sending unit 135 sends the message selected by the user U2 from the candidate messages to the user U1 via the communication unit 110. In another aspect, the sending unit 135 sends the message to the user U1 via the communication unit 110 if the user U2 agrees with the proposal.

(Providing Unit 136)
The providing unit 136 provides a talk room function that allows a user U1 (first user) and a user U2 (second user) to send and receive messages in the payment app via the communication unit 110. The providing unit 136 can also provide various functions in the payment app via the communication unit 110. The providing unit 136 may be integrated with the above-mentioned proposing unit 134 and transmitting unit 135. That is, the proposing unit 134, the transmitting unit 135, and the providing unit 136 may be integrated.

(Determination unit 137)
The determination unit 137 determines whether the payment history of the user U1 satisfies a predetermined condition. For example, when the user U2 opens a chat room with the user U1 in the payment app, the determination unit 137 determines whether the payment of the user U1 satisfies a predetermined condition based on the payment history of the user U1. The determination unit 137 may be the same as the estimation unit 132 or a part of the estimation unit 132.

At this time, the determination unit 137 may determine, as a predetermined condition (first condition), for example, whether or not the time from the most recent payment by user U1 to the call of the talk room occurred within a predetermined time. Furthermore, the determination unit 137 may determine, as a predetermined condition (second condition), whether or not the most recent payment by user U1 and the call of the talk room were made within a predetermined distance (whether or not the most recent payment location (location) of user U1 and the location (location) from which the talk room was called are within a predetermined range). Furthermore, the determination unit 137 may determine, as a predetermined condition (third condition), whether or not the most recent payment by user U1 was a small amount payment of a predetermined amount or less. Note that these are merely examples.

When the payment history of user U1 satisfies a predetermined condition, the estimation unit 132 estimates the purpose of user U1's payment based on the payment history of user U1. The selection unit 133 selects a message corresponding to the purpose of the payment. The proposal unit 134 proposes the selected message to user U2. The transmission unit 135 transmits the message to user U1 if user U2 agrees with the proposal.

In addition, the suggestion unit 134 suggests the selected message to user U2 when the payment history of user U1 meets a predetermined condition. For example, the suggestion unit 134 suggests the selected message to user U2 when user U2 opens a chat room of the payment app within a predetermined period from the most recent payment history. In addition, the suggestion unit 134 suggests the selected message to user U2 when user U2 opens a chat room of the payment app within a predetermined range from the most recent payment history.

The selection unit 133 may select a stamp corresponding to the purpose of payment instead of a message (or as a message). The suggestion unit 134 suggests the selected stamp to the user U2. The selection unit 133 may select not only a stamp, but also something similar to a stamp (something having similar/equivalent functions, something that can be substituted).

Furthermore, the selection unit 133 may select a message that includes the name or category of the store where the payment was made, based on the payment history of user U1. The selection unit 133 may also select a message from user U2 to user U1, based on the time of user U1's payment. The selection unit 133 may also select a message from user U2 to user U1, based on the location information of user U1 at the time of payment.

For example, the selection unit 133 may select a message from user U2 to user U1 based on the purpose of user U1's payment and the time and location information at the time of payment. The estimation unit 132 may also estimate the purpose of user U1's payment from the name or category of the store where the payment was made, the time and location information at the time of payment, based on user U1's payment history.

5. Processing Procedure
Next, the processing procedure by the server device 100 according to the embodiment will be described with reference to Fig. 11 and Fig. 12. Fig. 11 is a flowchart showing a first processing procedure (with remittance) according to the embodiment. Fig. 12 is a flowchart showing a second processing procedure (without remittance) according to the embodiment. Note that the processing procedure shown below is repeatedly executed by the control unit 130 of the server device 100.

(1) When Remittance Has Been Made For example, as shown in FIG. 11, the acquisition unit 131 of the server device 100 acquires the payment history of the user U1 (remittance destination user) in the payment application (step S101).

Next, the acquisition unit 131 of the server device 100 acquires the remittance history of person-to-person remittances of user U2 (the remitter user) (step S102).

Then, the estimation unit 132 of the server device 100 estimates the relationship between user U1 and user U2 based on the payment history in the payment app of user U1 (recipient user) and the remittance history of person-to-person remittances of user U2 (source user), and estimates the purpose of the remittance from user U2 to user U1 from the relationship between user U1 and user U2 (step S103).

Next, the selection unit 133 of the server device 100 selects message candidates that correspond to the relationship between user U1 and user U2 or the purpose of the remittance (step S104).

Then, the suggestion unit 134 of the server device 100 proposes the selected message candidates to the user U2 via the communication unit 110 (step S105).

Then, the transmitting unit 135 of the server device 100 transmits the message selected by user U2 from the candidate messages to user U1 via the communication unit 110 (step S106).

(2) In the case where no remittance is made For example, as shown in FIG. 12, when user U2 designates user U1 in the payment app and opens a talk room, the provision unit 136 of the server device 100 provides a talk room to user U2 (step S201).

Next, the acquisition unit 131 of the server device 100 acquires the payment history of user U1 in the payment app (step S202).

Then, the determination unit 137 of the server device 100 determines whether the payment history of the user U1 satisfies a predetermined condition (step S203). If the payment history of the user U1 does not satisfy the predetermined condition (step S203: No), the determination unit 137 does not propose a message and ends the series of processes.

At this time, the determination unit 137 of the server device 100 determines whether or not there is a remittance history of user U2 that corresponds to the payment history of user U1, and if there is a remittance history of user U2 that corresponds to the payment history of user U1, it may proceed to the first processing procedure (remittance present) shown in Figure 11 (proceed to step S103 in Figure 11), and if there is no remittance history of user U2 that corresponds to the payment history of user U1, it may continue the series of processes shown below.

For example, the acquisition unit 131 of the server device 100 may acquire the remittance history of person-to-person remittances of user U2, similar to step S102 of FIG. 11. The estimation unit 132 of the server device 100 may estimate the relationship between user U1 and user U2 based on the payment history of user U1 and the remittance history of user U2, similar to step S103 of FIG. 11. Then, if the relationship between user U1 and user U2 can be estimated, the determination unit 137 of the server device 100 may proceed to the first processing procedure (remittance made) shown in FIG. 11 (proceed to step S103 of FIG. 11), and if the relationship between user U1 and user U2 cannot be estimated, the determination unit 137 may continue the series of processes shown below.

Here, we explain the case where there is no remittance history for user U2 that corresponds to the payment history for user U1.

Next, if the payment history of user U1 satisfies a predetermined condition (step S203: Yes), the estimation unit 132 of the server device 100 estimates the purpose of the payment of user U1 (step S204). Note that the estimation unit 132 may estimate the purpose of the payment of user U1 from the result of the above judgment.

Next, the selection unit 133 of the server device 100 selects message candidates that correspond to the purpose of the payment of user U1 (step S205).

Then, the proposal unit 134 of the server device 100 proposes the selected message to the user U2 via the communication unit 110 (step S206).

Next, if user U2 agrees with the proposed message, the transmission unit 135 of the server device 100 transmits the message to user U1 via the communication unit 110 (step S207). Note that the message may be transmitted as an exchange within a talk room. Also, if user U2 does not agree with the proposed message, the transmission unit 135 may end the series of processes without transmitting the message, or may return to step S205 and start over from selecting a candidate message, or may transmit a message that user U2 has inputted himself.

6. Modifications
The above-described terminal device 10 and server device 100 may be implemented in various different forms other than the above-described embodiment. Therefore, the following describes modifications of the embodiment.

In the above embodiment, some or all of the processing executed by the server device 100 may actually be executed by the terminal device 10. For example, the processing may be completed in a stand-alone manner (by the terminal device 10 alone). In this case, the terminal device 10 is assumed to have the functions of the server device 100 in the above embodiment. Also, in the above embodiment, since the terminal device 10 is linked to the server device 100, from the perspective of the user U, it appears that the processing of the server device 100 is also executed by the terminal device 10. In other words, from another perspective, it can also be said that the terminal device 10 is equipped with the server device 100.

In addition, in the above embodiment, the server device 100 may automatically send the same message as before when user U1, the recipient (recipient) of a person-to-person remittance, and user U2, the sender (source) of the remittance, repeatedly perform similar payments and remittances. In this case, the server device 100 may propose to user U2, the sender, setting up automatic sending of a message to user U1, the recipient (recipient), and set up automatic message sending if user U2 agrees.

In addition, in the above embodiment, the server device 100 may use a model obtained by learning user U1, the recipient of the person-to-person remittance (recipient), the location and date and time of payment, and user U2, the sender, the location and date and time of remittance, and the message sent, to estimate candidates for messages to be sent from user U1 to user U2.

In addition, in the above embodiment, the server device 100 may use a model obtained by learning messages sent by other users who are transferring money for a similar payment to estimate candidates for messages to be sent from user U1 to user U2. At this time, the server device 100 may automatically generate the contents of the message using the model.

Furthermore, in the above embodiment, the server device 100 may select candidates for messages to be sent by the user U2 on the remittance side (remitter) and propose them to the user U1 as a reply message for the user U1 on the recipient side (recipient) in response to a message from the remittance side (remitter). For example, when the server device 100 sends a message from the user U2 on the remittance side (remitter) to the user U1, the server device 100 selects candidates for messages to be sent by the user U1 on the recipient side (remitter) in response to a message from the remittance side (remitter) and proposes them to the user U1. Then, the server device 100 transmits (replies to) the message selected by the user U1 from among the candidate messages to the user U2. Alternatively, the server device 100 may automatically select and transmit (reply) a reply message when a message is sent from the user U2 on the remittance side (remitter) to the user U1. At this time, the server device 100 may estimate the reply message using an estimation model obtained by machine learning.

7. Effects
(1) As described above, the information processing device (terminal device 10 and server device 100) of the present application is characterized by comprising an acquisition unit 131 that acquires the payment history of the destination user in a payment app and the remittance history of the source user in person-to-person remittances, a selection unit 133 that selects candidate messages from the source user to the destination user based on the relationship between the destination user's payment history and the source user's remittance history, a proposal unit 134 that proposes the selected candidate messages to the source user, and a transmission unit 135 that transmits a message selected by the source user from the candidate messages to the destination user.

If the remittance history of the sender user corresponds to the remittance history of the recipient user in the payment history of the remittance destination user, the selection unit 133 selects candidates for a message from the sender user to the recipient user.

The selection unit 133 selects candidate messages from the remittance source user to the remittance destination user based on the remittance history of other remittance source users to the remittance destination user.

The selection unit 133 selects candidate messages from the remittance source user to the remittance destination user based on the remittance history of multiple remittance source users to the remittance destination user.

The selection unit 133 estimates the purpose of the remittance by the remittance source user based on the payment history of the remittance destination user, and selects candidate messages that correspond to the purpose of the remittance.

The selection unit 133 selects candidate messages that include the name or category of the store where the payment was made and that corresponds to the purpose of the remittance.

The selection unit 133 selects candidates for messages from the remittance source user to the remittance destination user based on the time of payment by the remittance destination user.

The selection unit 133 selects candidate messages from the remittance source user to the remittance destination user based on the location information of the remittance destination user at the time of payment.

(2) In another aspect, the information processing device (terminal device 10 and server device 100) according to the present application is characterized by comprising an acquisition unit 131 that acquires information about a first user who is the recipient in a person-to-person remittance via a payment app and information about a second user who is the sender, an estimation unit 132 that estimates the relationship between the first user and the second user based on the information about the first user and the information about the second user and estimates the purpose of the remittance from the second user to the first user from the relationship between the first user and the second user, a selection unit 133 that selects a message corresponding to the purpose of the remittance, a proposal unit 134 that proposes the selected message to the second user, and a transmission unit 135 that transmits the message to the first user if the second user agrees to the proposal.

The estimation unit 132 estimates whether a payment made by the first user using the payment app has a relationship with the second user based on information about the first user and information about the second user. If there is a relationship with the second user, the selection unit 133 selects a message corresponding to the payment.

The acquisition unit 131 acquires location information of the first user at the time of payment and location information of the second user at the time of remittance. If the location of the first user at the time of payment and the location of the second user at the time of remittance are within a predetermined range, the estimation unit 132 estimates that a payment made by the first user using a payment app is related to the second user. If there is a relationship with the second user, the selection unit 133 selects a message corresponding to the payment.

The acquisition unit 131 acquires date and time information of the first user's payment and the second user's remittance. The estimation unit 132 estimates that a payment made by the first user using a payment app has a relationship with the second user if the date and time of the first user's payment and the date and time of the second user's remittance are within a predetermined range. The selection unit 133 selects a message corresponding to the payment if there is a relationship with the second user.

The acquisition unit 131 acquires payment information of the first user and remittance information of the second user. If the payment amount of the first user and the remittance amount of the second user are within a predetermined range, the estimation unit 132 estimates that a payment made by the first user using a payment app has a relationship with the second user. If there is a relationship with the second user, the selection unit 133 selects a message corresponding to the payment.

The estimation unit 132 estimates that the second user and the first user are in a parent-child relationship based on information about the first user and information about the second user, and estimates the purpose of the remittance from the second user to the first user.

The estimation unit 132 estimates the purpose of sending the message from the payment destination when the first user and the second user were within a specified range at the time of payment. The selection unit 133 selects a message that corresponds to the estimated purpose.

The estimation unit 132 estimates the purpose of the first user and the second user when they were together, based on information about the first user and information about the second user. The selection unit 133 selects a message that corresponds to the estimated purpose.

The estimation unit 132 estimates the degree of intimacy between the first user and the second user based on information about the first user and information about the second user. The selection unit 133 selects a message according to the degree of intimacy.

(3) The information processing device (terminal device 10 and server device 100) according to the present application is characterized by including a provision unit 136 that provides a talk room function in a payment app that enables a first user and a second user to send and receive messages, an estimation unit 132 that estimates the purpose of payment of the first user based on the payment history of the first user, a selection unit 133 that selects a message corresponding to the purpose of payment, a proposal unit 134 that proposes the selected message to the second user, and a transmission unit 135 that transmits the message to the first user if the second user agrees to the proposal.

If the payment history meets a predetermined condition, the suggestion unit 134 suggests the selected message to the second user.

The suggestion unit 134 suggests the selected message to the second user if the second user opens a chat room of the payment app within a predetermined period from the most recent payment history.

The suggestion unit 134 suggests the selected message to the second user when the second user opens a chat room of the payment app within a predetermined range from the most recent payment history.

The selection unit 133 selects a stamp that corresponds to the purpose of the payment. The suggestion unit 134 suggests the selected stamp to the second user.

The selection unit 133 selects a message that includes the name or category of the store where the payment was made based on the payment history of the first user.

The selection unit 133 selects a message from the second user to the first user based on the time of payment by the first user.

The selection unit 133 selects a message from the second user to the first user based on the location information of the first user at the time of payment.

By using any one or a combination of the above-mentioned processes, the information processing device according to the present application can further improve the convenience of users when transferring electronic money between individuals using a payment app.

8. Hardware Configuration
Moreover, the terminal device 10 and the server device 100 according to the above-described embodiment are realized by a computer 1000 having a configuration as shown in Fig. 13, for example. The server device 100 will be described below as an example. Fig. 13 is a diagram showing an example of a hardware configuration. The computer 1000 is connected to an output device 1010 and an input device 1020, and has a configuration in which a calculation device 1030, a primary storage device 1040, a secondary storage device 1050, an output I/F (Interface) 1060, an input I/F 1070, and a network I/F 1080 are connected by a bus 1090.

The arithmetic device 1030 operates based on programs stored in the primary storage device 1040 and the secondary storage device 1050, programs read from the input device 1020, and the like, and executes various processes. The arithmetic device 1030 is realized, for example, by a CPU (Central Processing Unit), an MPU (Micro Processing Unit), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or the like.

The primary storage device 1040 is a memory device such as a RAM (Random Access Memory) that primarily stores data used by the arithmetic device 1030 for various calculations. The secondary storage device 1050 is a storage device in which data used by the arithmetic device 1030 for various calculations and various databases are registered, and is realized by a ROM (Read Only Memory), a HDD (Hard Disk Drive), a SSD (Solid State Drive), a flash memory, or the like. The secondary storage device 1050 may be an internal storage device or an external storage device. The secondary storage device 1050 may be a removable storage medium such as a USB (Universal Serial Bus) memory or a SD (Secure Digital) memory card. The secondary storage device 1050 may be a cloud storage device (online storage device), a NAS (Network Attached Storage), a file server, or the like.

The output I/F 1060 is an interface for transmitting information to be output to an output device 1010 that outputs various types of information, such as a display, projector, printer, etc., and is realized by a connector conforming to a standard such as USB (Universal Serial Bus), DVI (Digital Visual Interface), or HDMI (registered trademark) (High Definition Multimedia Interface). The input I/F 1070 is an interface for receiving information from various input devices 1020, such as a mouse, keyboard, keypad, button, scanner, etc., and is realized by a USB, etc.

In addition, the output I/F 1060 and the input I/F 1070 may be wirelessly connected to the output device 1010 and the input device 1020, respectively. That is, the output device 1010 and the input device 1020 may be wireless devices.

The output device 1010 and the input device 1020 may be integrated together, such as a touch panel. In this case, the output I/F 1060 and the input I/F 1070 may also be integrated together as an input/output I/F.

The input device 1020 may be a device that reads information from, for example, an optical recording medium such as a CD (Compact Disc), a DVD (Digital Versatile Disc), or a PD (Phase change rewritable Disk), a magneto-optical recording medium such as an MO (Magneto-Optical disk), a tape medium, a magnetic recording medium, or a semiconductor memory.

The network I/F 1080 receives data from other devices via the network N and sends it to the computing device 1030, and also transmits data generated by the computing device 1030 to other devices via the network N.

The arithmetic unit 1030 controls the output device 1010 and the input device 1020 via the output I/F 1060 and the input I/F 1070. For example, the arithmetic unit 1030 loads a program from the input device 1020 or the secondary storage device 1050 onto the primary storage device 1040 and executes the loaded program.

For example, when the computer 1000 functions as the server device 100, the arithmetic unit 1030 of the computer 1000 executes a program loaded onto the primary storage device 1040 to realize the functions of the control unit 130. The arithmetic unit 1030 of the computer 1000 may also load a program acquired from another device via the network I/F 1080 onto the primary storage device 1040 and execute the loaded program. The arithmetic unit 1030 of the computer 1000 may also cooperate with other devices via the network I/F 1080 and use the functions and data of a program by calling them from other programs of the other devices.

[9. Other]
Although the embodiments of the present application have been described above, the present invention is not limited to the contents of these embodiments. The above-described components include those that a person skilled in the art can easily imagine, those that are substantially the same, and those that are within the so-called equivalent range. Furthermore, the above-described components can be appropriately combined. Furthermore, various omissions, substitutions, or modifications of the components can be made without departing from the spirit of the above-described embodiments.

Furthermore, among the processes described in the above embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically using known methods. In addition, the information including the processing procedures, specific names, various data, and parameters shown in the above documents and drawings can be changed as desired unless otherwise specified. For example, the various information shown in each drawing is not limited to the information shown in the drawings.

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 depending on various loads, usage conditions, etc.

For example, the above-mentioned server device 100 may be realized by multiple server computers, and depending on the functions, the configuration can be flexibly changed, such as by calling an external platform using an API (Application Programming Interface) or network computing.

The above-described embodiments and variations can be combined as appropriate to the extent that they do not cause inconsistencies in the processing content.

In addition, the above-mentioned "section, module, unit" can be read as "means" or "circuit." For example, an acquisition unit can be read as an acquisition means or an acquisition circuit.

REFERENCE SIGNS LIST 1 Information processing system 10 Terminal device 100 Server device 110 Communication unit 120 Storage unit 121 User information database 122 History information database 123 Payment information database 124 Remittance information database 130 Control unit 131 Acquisition unit 132 Estimation unit 133 Selection unit 134 Proposal unit 135 Transmission unit 136 Provision unit 137 Determination unit

Claims (11)

an acquisition unit that acquires information about a first user who is a recipient of a person-to-person remittance via a payment app and information about a second user who is a remittance sender;
an estimation unit that estimates a relationship between the first user and the second user based on information about the first user and information about the second user, and estimates a purpose of a remittance from the second user to the first user from the relationship between the first user and the second user;
a selection unit for selecting a message corresponding to the purpose of the remittance;
a suggestion unit that suggests the selected message to the second user;
a sending unit for sending the message to the first user if the second user agrees with the proposal;
An information processing device comprising: The estimation unit estimates whether or not a payment made by the first user using a payment app has a relationship with the second user, based on information about the first user and information about the second user;
The information processing device according to claim 1 , wherein the selection unit selects a message corresponding to the payment when there is a relationship with the second user. The acquisition unit acquires location information of the first user at the time of payment and location information of the second user at the time of remittance,
the estimation unit estimates that a payment made by the first user using a payment app is related to the second user when a location of the first user at the time of payment and a location of the second user at the time of remittance are within a predetermined range;
The information processing device according to claim 1 , wherein the selection unit selects a message corresponding to the payment when there is a relationship with the second user. The acquisition unit acquires date and time information of the first user's payment and date and time information of the second user's remittance,
the estimation unit estimates that a payment made by the first user using a payment app is related to the second user when a payment date and time of the first user and a remittance date and time of the second user are within a predetermined range;
The information processing device according to claim 1 , wherein the selection unit selects a message corresponding to the payment when there is a relationship with the second user. The acquisition unit acquires payment information of the first user and remittance information of the second user,
the estimation unit estimates that a payment made by the first user using a payment app is related to the second user when a payment amount of the first user and a remittance amount of the second user are within a predetermined range;
The information processing device according to claim 1 , wherein the selection unit selects a message corresponding to the payment when there is a relationship with the second user. The information processing device according to claim 1, characterized in that the estimation unit estimates that the second user and the first user are in a parent-child relationship based on information about the first user and information about the second user, and estimates the purpose of a remittance from the second user to the first user. The estimation unit estimates a purpose of sending a message from a payment destination when the first user and the second user were within a predetermined range at the time of payment,
The information processing device according to claim 1 , wherein the selection unit selects a message corresponding to the estimated purpose. The estimation unit estimates a purpose of the first user and the second user when they were together based on information about the first user and information about the second user,
The information processing device according to claim 1 , wherein the selection unit selects a message corresponding to the estimated purpose. The estimation unit estimates a degree of intimacy between the first user and the second user based on information about the first user and information about the second user;
The information processing device according to claim 1 , wherein the selection unit selects a message according to the degree of intimacy. An information processing method executed by an information processing device,
An acquisition step of acquiring information about a first user who is the recipient of a person-to-person remittance via a payment application and information about a second user who is the remittance sender;
an estimation step of estimating a relationship between the first user and the second user based on information about the first user and information about the second user, and estimating a purpose of the remittance from the second user to the first user from the relationship between the first user and the second user;
a selection step of selecting a message corresponding to a purpose of the remittance;
a suggesting step of suggesting the selected message to the second user;
sending the message to the first user if the second user agrees with the proposal;
13. An information processing method comprising: An acquisition step of acquiring information about a first user who is the recipient of a person-to-person remittance via a payment app and information about a second user who is the remittance sender;
an estimation step of estimating a relationship between the first user and the second user based on information about the first user and information about the second user, and estimating a purpose of the remittance from the second user to the first user from the relationship between the first user and the second user;
a selection step for selecting a message corresponding to the purpose of the remittance;
a suggestion step of suggesting the selected message to the second user;
a sending step of sending the message to the first user if the second user agrees with the proposal;
An information processing program characterized by causing a computer to execute the above.

Images