JP2024072376A - Information processing device and information processing method - Google Patents

Abstract

To grasp a customer attraction effect of bonus offering based on a past payment result.SOLUTION: A settlement processing device 1 includes: a payment processing unit 134 that, after payment based on a user ID of a user who performs payment in a prescribed shop and a payment request including a payment amount concerning the payment is made, stores the user ID, the payment amount included in the payment request, and the payment time in association with each other as payment history information in a storage unit 12; a bonus offering unit 135 that, when receiving, from a user terminal 2 being used by the user, a post-payment offer request which is a request for offering of a bonus which can be offered on the basis of the payment in the prescribed shop according to the payment history information, offers the bonus to the user; and a reporting unit 136 that identifies user's new payment history information which is newly stored after the bonus is offered to the user on the basis of the payment time and the user ID included in the payment history information, and reports user's prescribed shop re-visiting information based on the identified new payment history information, to a person concerned in the prescribed shop.SELECTED DRAWING: Figure 2

Description

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

Systems that apply rewards to users who have made payments are known. For example, Patent Literature 1 discloses a system that applies rewards to users who have installed an application for using rewards on their own devices, based on their past payment records before the application was installed.

JP 2018-13896 A

The conventional system had the problem of being unable to grasp the customer attraction effect of applying special offers based on past payment history.

The present invention was made in consideration of these points, and aims to make it possible to understand the customer attraction effect of applying special offers based on past payment records.

The information processing device according to the first aspect of the present invention has: a storage control unit that, after a payment is made based on user identification information for identifying a user making a payment at a specified store and a payment request including a payment amount related to the payment, associates the user identification information, the payment amount included in the payment request, and the payment time at which the payment was made and stores them in a storage unit as payment history information; a benefit application unit that, upon receiving a post-payment application request from a user terminal used by the user, which is a request to apply a benefit applicable based on a payment at the specified store corresponding to the payment history information stored in the storage unit, applies the benefit to the user based on the received post-payment application request; and a notification unit that, based on the payment time and the user identification information included in the payment history information stored in the storage unit, identifies new payment history information that is the payment history information of the user that was newly stored in the storage unit after the benefit application unit applied the benefit to the user, and notifies related parties of the specified store of the user's revisit to the specified store based on the identified new payment history information.

The notification unit may identify new payment history information corresponding to each of the multiple users, and notify relevant parties of the specified store of the re-visit information based on the new payment history information of each of the identified multiple users.

The notification unit may identify, based on new payment history information corresponding to each of the multiple users, a percentage of the multiple users to whom the benefit was applied who revisited the specified store within a specified time period after the benefit was applied, and notify relevant parties of the specified store of the identified percentage of users as the revisit information.

The notification unit may generate statistical information relating to at least one of the period from when the benefit was applied to when each of the multiple users revisits the store, the frequency of revisits, and the payment amount at the time of the revisit, for each of the multiple users to whom the benefit was applied, based on new payment history information corresponding to each of the multiple users, and notify relevant parties of the specified store of the generated statistical information as the revisit information.

When the benefit application unit receives from the user terminal a payment application request that is a request to apply a benefit that is applicable based on a payment at the time of payment at the specified store, the benefit application unit applies the benefit to the user based on the received payment application request, and stores the payment history information in association with the benefit grant time at which the benefit was granted. The notification unit may identify a payment application user to whom a benefit was applied based on the payment application request and a post-payment application user to whom a benefit was applied based on the post-payment application request, based on the payment time included in the payment history information and the benefit grant time associated with the payment history information, and notify the payment application user of the re-visit tendency of the payment application user based on the new payment history information of the payment application user and the post-payment application user of the re-visit tendency of the post-payment application user based on the new payment history information of the post-payment application user.

The notification unit may notify information indicating the effect of granting a benefit to a user after payment, based on a comparison result between the tendency of the applicable user at the time of payment to revisit a store, based on new payment history information of the applicable user at the time of payment, and the tendency of the applicable user after payment to revisit a store, based on new payment history information of the applicable user after payment.

The notification unit may identify, among a plurality of users to whom a benefit was applied pursuant to the post-payment application request, one or more users who made a relatively small number of payments before the benefit was applied, based on the payment time and the user identification information included in the payment history information stored in the memory unit, and notify the one or more users of information indicating the presence or absence of new payment history information corresponding to the one or more users.

When the bonus application unit receives, from the user terminal used by the user, a payment application request that is a request to apply a bonus that is applicable based on the payment at the time of payment at the specified store, it applies the bonus to the user based on the received payment application request, and stores the payment history information in association with the bonus grant time at which the bonus was granted, and the notification unit may refer to the payment time included in the payment history information and the bonus grant time associated with the payment history information, identify the ratio between the number of times the bonus was applied to the user based on the payment application request and the number of times the bonus was applied to the user based on the post-payment application request, and notify information indicating the identified ratio.

The notification unit may refer to user information that associates user identification information that identifies a user with attribute information that indicates the attributes of the user, identify attribute information associated with the user identification information of a user who has revisited the store, and notify the user of the identified attribute information.

The notification unit may identify a user who has revisited the store after the benefit application unit has applied the benefit in response to the post-payment application request based on the payment time and the user identification information included in the payment history information stored in the memory unit, and notify the user of information related to the payment before the benefit was applied, based on the payment history information corresponding to the user before the benefit was applied.

The information processing device further includes a storage unit that stores, in association with each other, bonus identification information that identifies the bonus and bonus information that indicates the content of the bonus, and a bonus information providing unit that, upon receiving from the user terminal of the user a request to view bonus information including the user identification information and bonus identification information of the user, transmits the bonus information to the user terminal and stores in the storage unit browsing history information that associates the user identification information, the bonus identification information, and the transmission time of the bonus information. When the notification unit determines, based on the payment time and the user identification information included in the payment history information stored in the storage unit, that a user to whom a bonus has been granted based on the post-payment application request has not revisited the store within a predetermined period of time since the bonus was granted, the notification unit may notify the user of information indicating the user's browsing status of the bonus information after the bonus was granted based on the browsing history information.

The notification unit may also notify the provider of the funds for the benefit of information about the user's revisit to the specified store based on the new payment history information.

The information processing method according to the second aspect of the present invention includes the steps of: after a payment is made based on user identification information for identifying a user making a payment at a specified store and a payment request including a payment amount related to the payment, the user identification information, the payment amount included in the payment request, and the payment time at which the payment was made are associated with each other and stored in a storage unit as payment history information, when a post-payment application request is received from a user terminal used by the user, which is a request to apply a benefit applicable based on a payment at the specified store corresponding to the payment history information stored in the storage unit, applying the benefit to the user based on the received post-payment application request, and identifying new payment history information that is the payment history information of the user that is newly stored in the storage unit after the benefit is applied to the user, based on the payment time and the user identification information included in the payment history information stored in the storage unit, and notifying related parties of the specified store of the user's revisit to the specified store based on the identified new payment history information.

The present invention has the effect of making it possible to grasp the customer attraction effect of applying a special offer based on past payment records.

FIG. 1 is a diagram showing an overview of a payment system. FIG. 2 is a diagram illustrating a functional configuration of a payment processing device. FIG. 11 is a diagram showing an example of benefit management information. FIG. 11 is a diagram showing an example of payment history information. FIG. 13 is a diagram illustrating an example of an analysis screen. FIG. 13 is a diagram illustrating an example of display of period statistical information. FIG. 11 is a diagram illustrating an example of attribute distribution information.

[Overview of payment system S]
1 is a diagram showing an overview of a payment system S. The payment system S is a system that, when a user purchases a product or service at a store, performs payment in response to a payment request received from a user terminal 2 carried by the user or a store terminal 3 used by the store.

The payment system S comprises a payment processing device 1 as an information processing device, a user terminal 2, a store terminal 3, and a business operator terminal 4. The payment processing device 1 is a server that processes payment of the purchase amount. The user terminal 2 is an information terminal used by a user, such as a smartphone, tablet, or personal computer. The store terminal 3 is a terminal used in a store that sells products or provides services, such as a POS terminal. The business operator terminal 4 is a terminal used by a business operator who operates the store as a related party to the store, such as a smartphone, tablet, or personal computer. The business operator who operates the store may also be a provider that provides funds for benefits applied to users for payments made at the store.

In the following explanation, goods or services are collectively referred to as goods. In addition, in the following explanation, an example is described in which the payment processing device 1 receives a payment request related to a specified store and performs payment processing, but this is not limited to this, and the payment processing device 1 can receive payment requests related to one or more stores other than the specified store and perform payment processing.

In the payment system S, a user purchases a product at a specific store. The payment processing device 1 receives, in response to a specific payment method, a user ID (Identification) for identifying the user, a store ID of the specific store, and a payment request including the payment amount for the user's purchase of a product at the specific store from at least one of the user terminal 2 and the store terminal 3 used at the specific store ((1) in Figure 1). The user ID is, for example, an ID given to the user by a payment business operator that provides a payment service related to the payment processing device 1.

The specified payment method is, for example, a payment method using a code. Payment methods using codes include the CPM (Consumer Presented Mode) payment method and the MPM (Merchant Presented Mode) payment method. The CPM method is a method in which a payment code such as a two-dimensional barcode is displayed on the user terminal 2, and payment is made when the payment code is read by the store. The MPM method is a method in which a payment code is presented at the store, and payment is made when the payment code is read by the user. In the following explanation, the payment method using a code is referred to as code payment.

When the payment processing device 1 receives the user ID, store ID, and payment request, it performs payment based on the received user ID, store ID, and payment amount included in the payment request, and stores payment history information indicating the payment history ((2) in Figure 1).

The payment processing device 1 receives from the user terminal 2 a post-payment application request, which is a request to apply a benefit that is applicable based on a payment at a specific store and corresponds to the payment history information ((3) in FIG. 1). Upon receiving the post-payment application request, the payment processing device 1 applies the benefit to the user of the user terminal 2 ((4) in FIG. 1).

If the user subsequently returns to the specified store and purchases an item, the payment processing device 1 receives a payment request, performs payment processing, and stores payment history information ((5) and (6) in FIG. 1). The payment processing device 1 receives a request from the business operator terminal 4 to view information indicating the effect of applying the benefit ((7) in FIG. 1).

Based on the payment history information, the payment processing device 1 identifies new payment history information for the user that has been newly stored after the benefit has been applied to the user based on the post-payment application request. When the payment processing device 1 receives a request to view information indicating the effect of the benefit application, it notifies the business terminal 4 of the user's revisit to a specified store based on the identified new payment history information ((8) in FIG. 1).

In this way, the business using the business terminal 4 can check the re-visit information and understand the customer attraction effect of applying the special offer based on past payment records. The details of the configuration of the payment processing device 1 are explained below. Note that the following explanation is given assuming that the specified payment method is a CPM code payment.

[Functional configuration of payment processing device 1]
2 is a diagram showing the functional configuration of the payment processing device 1. The payment processing device 1 has a communication unit 11, a storage unit 12, and a control unit 13.

The communication unit 11 is a communication interface for transmitting and receiving data to and from the user terminal 2 and the store terminal 3 via a network such as the Internet.
The memory unit 12 is a storage medium that stores various data, and includes a ROM (Read Only Memory), a RAM (Random Access Memory), a hard disk, etc. The memory unit 12 stores programs executed by the control unit 13. The memory unit 12 stores programs that cause the control unit 13 to function as a registration unit 131, a privilege information providing unit 132, a payment request receiving unit 133, a payment processing unit 134, a privilege application unit 135, and a notification unit 136.

The memory unit 12 stores benefit management information for managing benefits. FIG. 3 is a diagram showing an example of benefit management information. As shown in FIG. 3, benefit management information is information that associates a benefit ID for identifying a benefit, a store ID of a store where the benefit can be used, summary information indicating a summary of the benefit, and benefit information indicating the content of the benefit. Here, a benefit is a benefit that can be used at a store indicated by a store ID, such as coupons or points. The summary information is information that is displayed, for example, as a list of benefits that can be used by a user on the user terminal 2. Note that the benefit management information may also include condition information indicating the conditions under which a benefit is granted.

The memory unit 12 stores payment history information that indicates the history of payments made using a specified payment method. FIG. 4 is a diagram showing an example of payment history information. As shown in FIG. 4, the payment history information is information that associates the user ID of a user who purchased a product, the store ID of the store where the user purchased the product, the payment amount, and the payment time as the time of payment.

As shown in FIG. 4, the payment history information is stored in association with the bonus application history information. The bonus application history information is information indicating the history of bonuses applied to a user based on the payment indicated by the payment history information. Note that the payment history information stores the payment time as the payment time, but is not limited to this, and may also include the payment date instead of the payment time. The payment history information may also include a product ID as product identification information for identifying the product purchased by the user.

The control unit 13 is, for example, a CPU (Central Processing Unit). The control unit 13 executes a payment program stored in the memory unit 12, thereby functioning as a registration unit 131, a privilege information providing unit 132, a payment request receiving unit 133, a payment processing unit 134, a privilege application unit 135, and a notification unit 136.

The registration unit 131 receives bonus information indicating the contents of the bonus and the store ID of the store from the store terminal 3, and stores the bonus information in the memory unit 12 in association with the store ID. For example, the registration unit 131 receives a registration request for bonus information including the store ID from the store terminal 3. Upon receiving the registration request, the registration unit 131 displays a setting screen on the store terminal 3 for setting the bonus contents, and accepts bonus information indicating the contents of the bonus and summary information indicating a summary of the bonus.

When the registration unit 131 receives the bonus information and summary information via the setting screen, it generates a bonus ID for identifying the bonus. The registration unit 131 then stores in the memory unit 12 bonus management information that associates the generated bonus ID, the bonus information, the summary information, and the store ID included in the received registration request. The registration unit 131 is configured to receive the bonus information and the summary information, but may also receive the bonus granting conditions in addition to these, and include the bonus granting conditions in the bonus management information. The registration unit 131 is configured to receive a registration request for bonus information from the store terminal 3, but is not limited to this, and may also receive a registration request for bonus information from another terminal such as the business terminal 4.

When the privilege information providing unit 132 receives a request to view privilege information including the user ID and privilege ID of the user from the user terminal 2 of the user, it transmits the privilege information to the user terminal 2. For example, when the user terminal 2 accepts an operation to view a list of privileges by the user, it causes the user terminal 2 to display a privilege list including summary information of privileges available to the user on its display unit. When a privilege is selected in the list of privileges, the user terminal 2 transmits a request to view privilege information including the user ID and the privilege ID of the selected privilege to the payment processing device 1. When the privilege information providing unit 132 receives a request to view privilege information, it transmits the privilege information stored in the memory unit 12 in association with the privilege ID included in the received viewing request to the user terminal 2, and causes the privilege information to be displayed on the user terminal 2. In addition, the privilege information providing unit 132 stores in the memory unit 12 viewing history information that associates the received user ID, the privilege ID, and the transmission date and time as the transmission time of the privilege information.

Note that, although the request to view the bonus information includes the bonus ID, this is not limited thereto. The request to view the bonus information may not include the bonus ID, and may include a store ID instead of the bonus ID. For example, a list of stores to which bonuses are granted is displayed on the user terminal 2, and when a store is selected by the user, the user terminal 2 transmits a request to view bonus information including the user ID and the store ID of the selected store to the payment processing device 1. When the bonus information providing unit 132 receives a request to view bonus information, it transmits one or more pieces of bonus information associated with the store ID included in the received request in the bonus management information stored in the storage unit 12 to the user terminal 2, and displays the one or more pieces of bonus information on the user terminal 2. In addition, the bonus information providing unit 132 stores in the storage unit 12 browsing history information that associates the received user ID, bonus IDs corresponding to each of the one or more pieces of bonus information, and the transmission date and time as the transmission time of the bonus information.

The payment request receiving unit 133 receives a payment request including a user ID for identifying the user making a payment at a specific store and the payment amount from a store terminal 3 used at a specific store or a user terminal 2 used by the user.

Specifically, first, the payment request receiving unit 133 receives from the user terminal 2 the user ID of the user of the user terminal 2 and a request to issue a payment code for the user to make a payment at a store. When the payment request receiving unit 133 receives the request to issue a payment code, it generates a payment token. The payment token is a data string for generating a payment code corresponding to the user ID received along with the request to issue a payment code. The payment request receiving unit 133 associates the received user ID with the generated payment token and stores them in the memory unit 12. The payment request receiving unit 133 transmits the generated payment token to the user terminal 2 that transmitted the request to issue a payment code.

The payment request receiving unit 133 receives a payment request from the store terminal 3 that has read the payment code displayed by the user terminal 2 based on the transmitted payment token, the payment token extracted from the payment code, the store ID, and payment information corresponding to the payment for the purchase of the product at the user's store. The payment information includes the payment amount corresponding to the purchase of the product at the user's store. Note that the payment information may include the product ID of the product purchased by the user in order to include the product ID of the product purchased by the user in the payment history information.

The payment request receiving unit 133 may also receive, from the user terminal 2, a payment application request, which is a request to apply a benefit that can be used at a specific store, when receiving a payment request or a request to issue a payment code. Details will be described later, but when the payment request receiving unit 133 receives a payment application request, the benefit application unit 135 grants the user a benefit corresponding to the payment application request.

When the payment request receiving unit 133 receives a payment request, the payment processing unit 134 performs payment based on the received user ID, store ID, and payment amount included in the payment request. Specifically, when the payment request receiving unit 133 receives a payment request, the payment processing unit 134 first determines whether a payment token matching the payment token included in the payment request is stored in the memory unit 12. When the payment processing unit 134 determines that a matching payment token is stored in the memory unit 12, it identifies the user ID associated with the payment token and stored in the memory unit 12, i.e., the user ID received by the payment request receiving unit 133 along with the request to issue a payment code.

The payment processing unit 134 executes a payment process to debit the payment amount from the user's electronic currency account corresponding to the identified user ID. For example, the memory unit 12 stores a user ID in association with the user's electronic currency account number. The payment processing unit 134 identifies the user's electronic currency account number associated with the identified user ID, and debits the payment amount from the user's electronic currency account indicated by that number.

The payment processing unit 134 executes a process of debiting the payment amount from the user's electronic currency account as payment processing, but this is not limited to this. If the user's payment method is a payment method using a credit card rather than debiting from an electronic account, the payment processing unit 134 may execute a payment process by requesting pre-approval (authorization) for the payment of the payment amount from the credit card company. In this case, the payment process may be completed when pre-approval for the payment of the payment amount is received from the credit card company.

The payment processing unit 134 also executes a process of depositing an amount corresponding to the payment amount included in the received payment request into the account of the store identified by the store ID included in the payment information. For example, the payment processing unit 134 calculates the store receipt amount by subtracting a payment fee corresponding to the payment service from the payment amount, and executes a process of depositing the calculated store receipt amount into the account of the store identified by the store ID included in the payment information. Note that the payment processing unit 134 may add up the store receipt amounts calculated over a predetermined period (e.g., one month) at predetermined time intervals (e.g., one month), and deposit the total store receipt amount into the account of the store identified by the store ID.

The payment processing unit 134 functions as a memory control unit, and after a payment is made based on a user ID for identifying a user making a payment at a specific store and a payment request including the payment amount for the payment, it associates the user ID, the payment amount included in the payment request, and the payment time as the time the payment was made, and stores them in the memory unit 12 as payment history information.

Specifically, the payment processing unit 134 associates the amount of payment, i.e., the amount deducted from the user's electronic account corresponding to the payment, the received store ID, the user ID stored in association with the received payment token, and the payment time, which is the time the payment was made, and stores them in the storage unit 12 as payment history information. If the payment information includes a product ID, the payment processing unit 134 stores the payment history information including the product ID in the storage unit 12.

The details of the functions of the payment request receiving unit 133 and the payment processing unit 134 have been explained using an example in which a user purchases a product at a specific store, but similar processing is assumed to be performed not only at the specific store, but also at other services and other stores where payment can be made using the specific payment method. As a result, the memory unit 12 accumulates not only payment history information indicating the payment history corresponding to the specific store, but also payment history information indicating the payment history for other services and other stores.

The benefit application unit 135 applies a benefit corresponding to a specific store to a user based on a payment at the specific store. For example, when the payment request receiving unit 133 receives from the user terminal 2 a payment application request that is a request for application of a benefit applicable based on the payment and that includes a benefit ID when a payment is made at a specific store, the benefit application unit 135 applies the benefit to the user based on the received payment application request.

In this case, the bonus application unit 135 applies a bonus to a user corresponding to the user ID received by the payment request receiving unit 133, on the condition that the store ID received by the payment request receiving unit 133 from the store terminal 3 is associated with the bonus ID included in the payment application request in the bonus management information stored in the memory unit 12. If the bonus is points, the bonus application unit 135 grants the points to the user. When applying the bonus, the bonus application unit 135 stores bonus application history information including the bonus ID of the applied bonus and the bonus application time as the bonus application time when the bonus was granted, in association with the payment history information stored in the memory unit 12 by the payment processing unit 134 in response to the payment at the specified store. In the following description, a user to whom a bonus is granted based on a payment application request is also referred to as a payment application user.

Some of the benefits are applicable after a payment is completed, based on the payment history corresponding to that payment. The benefit application unit 135 receives a post-payment application request from the user terminal 2 used by the user, which is a request to apply a benefit that is applicable based on a payment at a specific store corresponding to the payment history information stored in the memory unit 12. The post-payment application request includes the user ID of the user of the user terminal 2 and the benefit ID.

When the benefit application unit 135 receives a post-payment application request, it applies a benefit to the user based on the received post-payment application request. Specifically, the benefit application unit 135 refers to the benefit management information stored in the memory unit 12 and identifies the store ID associated with the benefit ID included in the post-payment application request. The benefit application unit 135 refers to the memory unit 12 and identifies payment history information that associates the identified store ID with the user ID and benefit ID included in the post-payment application request. Then, the benefit application unit 135 applies to the user the benefit indicated by the benefit ID included in the post-payment application request, on the condition that benefit application history information is not associated with the identified payment history information.

When the benefit application unit 135 applies a benefit to a user based on a post-payment application request, it associates the benefit ID of the applied benefit with the benefit application history information including the benefit application time when the benefit was granted, and stores the benefit application history information, which includes the benefit application time when the benefit was granted, in the identified payment history information. In the following description, a user to whom a benefit is granted based on a post-payment application request is also referred to as a post-payment application user.

The notification unit 136 receives a request to view an analysis screen including information indicating the effect of applying a benefit based on a post-payment application request from the business terminal 4 used by a business associated with a specific store. The request to view the analysis screen includes a store ID and a benefit ID, and notifies the business terminal 4 of an analysis screen including various information indicating the effect of applying a benefit based on a post-payment application request corresponding to the store ID and benefit ID. FIG. 5 is a diagram showing an example of an analysis screen. In the example shown in FIG. 5, it can be seen that an analysis screen is displayed that includes re-visit information of post-payment application users, such as the percentage of post-payment application users who re-visit a specific store and the period from when the benefit was granted until the re-visit.

When displaying the analysis screen, the notification unit 136 performs processing for generating various information to be included in the analysis screen. Below, an example of generating various information notified by the notification unit 136 will be described. In the following description, an example will be described in which a request to view the analysis screen includes a store ID of a specific store and a benefit ID corresponding to the specific store, and the notification unit 136 refers to payment history information including the store ID of the specific store, and generates various information to be included in the analysis screen corresponding to the benefit indicated by the benefit ID. Note that the notification unit 136 may similarly generate various information to be included in the analysis screen for other stores different from the specific store. In addition, the various information to be included in the analysis screen is generated using a user ID, but in order to protect personal information, the analysis screen does not include information that can identify an individual, such as a user ID.

At predetermined time intervals, the notification unit 136 identifies new payment history information of the user that has been newly stored in the memory unit 12 after the benefit application unit 135 applied a benefit to the user based on a post-payment application request, based on the payment time and user ID included in the payment history information, including the store ID of a specified store, stored in the memory unit 12. Then, the notification unit 136 generates re-visit information of the post-payment application user based on the identified new payment history information.

Specifically, first, the notification unit 136 refers to the payment history information and the bonus granting history information, and identifies the payment history information associated with a bonus granting time that is later than the payment time as the payment history information corresponding to the post-payment application user. The notification unit 136 calculates the number of post-payment application users based on the identification status of the payment history information corresponding to the post-payment application user. On the analysis screen shown in FIG. 5, it can be seen that an object O1 is displayed, which indicates the number of post-payment application users who have revisited a specified store.

The notification unit 136 also identifies, as new payment history information, payment history information that includes a user ID and a store ID that are the same as the user ID and the store ID of a specified store that are included in the identified payment history information, and that includes a payment time that is later than the payment time included in the identified payment history information. The notification unit 136 identifies new payment history information that corresponds to each of the identified multiple post-payment applying users.

The notification unit 136 generates revisit information of the post-payment application users at a specified store based on new payment history information corresponding to each of the identified multiple post-payment application users. For example, the notification unit 136 identifies, as revisit information, the percentage of post-payment application users who revisited the specified store within a specified time after the application of the benefit, among the multiple post-payment application users to whom the benefit was applied, based on new payment history information corresponding to each of the multiple post-payment application users and the benefit application time of the benefit corresponding to the post-payment application request. The specified time is a predetermined time, such as one week, but the specified time may be specified from the business terminal 4. It can be seen that an object O4 indicating the percentage of post-payment application users who revisited the specified store is displayed on the analysis screen shown in FIG. 5.

In addition, the notification unit 136 generates revisit information based on new payment history information corresponding to each of the multiple post-payment application users, and statistical information related to at least one of the period until each of the multiple post-payment application users revisits the store, the frequency of revisits, and the payment amount at the time of revisit.

For example, the notification unit 136 determines, for each of multiple post-payment applying users, the period from the benefit grant time when the benefit based on the post-payment application request is applied to the post-payment applying user to the payment time included in the new payment history information as the period from when the post-payment applying user receives the benefit until the user revisits the store. Here, if there are multiple pieces of new payment history information corresponding to one post-payment applying user, the notification unit 136 may determine the new payment history information with the oldest payment time, and determine the period from the payment time included in the new payment history information to the benefit grant time as the period until the post-payment applying user revisits the store.

The notification unit 136 generates statistical information indicating the period until revisiting identified for each of the multiple post-payment application users. For example, the analysis screen shown in FIG. 5 displays a button O5 labeled "Period until revisiting." In response to the selection of button O5, the notification unit 136 displays period statistical information indicating the period until revisiting for the multiple post-payment application users. FIG. 6 is a diagram showing an example of the display of period statistical information. As shown in FIG. 6, it can be seen that a graph showing the distribution of the period until revisiting identified for each of the multiple post-payment application users is displayed. Note that the notification unit 136 may generate the average, median, or intermediate value of the period until revisiting identified for each of the multiple post-payment application users as the period statistical information.

The notification unit 136 also identifies the frequency of revisits by each of the multiple post-payment application users based on the number of new payment history information identified for each of the multiple post-payment application users, and generates statistical information showing the distribution of the identified frequencies. For example, the analysis screen shown in FIG. 5 displays a button O6 labeled "revisit frequency." In response to button O6 being selected, the notification unit 136 displays frequency statistical information showing the frequency of revisits by the multiple post-payment application users. For example, the notification unit 136 notifies, as the frequency statistical information, a graph showing the distribution of the revisit frequencies identified for each of the multiple post-payment application users. Note that the notification unit 136 may generate, as the frequency statistical information, the average, median, or intermediate value of the revisit frequencies identified for each of the multiple post-payment application users.

The notification unit 136 also identifies the payment amount at the time of revisiting each of the multiple post-payment applicable users based on the payment amount included in the new payment history information identified for each of the multiple post-payment applicable users, and generates statistical information showing the distribution of the identified payment amounts. For example, the analysis screen shown in FIG. 5 displays a button O7 labeled "Revisit Payment Amount." In response to the selection of button O7, the notification unit 136 displays payment amount statistical information showing the payment amounts at the time of revisiting each of the multiple post-payment applicable users. For example, the notification unit 136 notifies a graph showing the distribution of the payment amounts at the time of revisiting each of the multiple post-payment applicable users as the payment amount statistical information. Note that the notification unit 136 may generate the average, median, or intermediate value of the payment amounts at the time of revisiting each of the multiple post-payment applicable users as the payment amount statistical information.

In addition, when the payment history information includes a product ID, the notification unit 136 may identify one or more products that have a relatively high purchase rate based on the product ID included in the new payment history information corresponding to each of multiple post-payment application users. For example, the analysis screen shown in FIG. 5 displays a button O2 labeled "Purchased Product Information." In response to the selection of button O2, the notification unit 136 displays a list of the identified products.

The notification unit 136 also identifies the at-payment application user and the post-payment application user based on the payment time included in the payment history information and the benefit grant time associated with the payment history information. The notification unit 136 then generates revisit information including the revisit tendency of the at-payment application user based on the new payment history information of the at-payment application user and the revisit tendency of the post-payment application user based on the new payment history information of the post-payment application user. Here, the revisit tendency is, for example, the percentage of users who revisit, the period until a revisit, the frequency of revisits, and the payment amount at the time of revisit, as described above.

In this case, the notification unit 136 identifies the re-visit tendency of the payment-applied user in the same way as it identifies the re-visit tendency of the post-payment-applied user. For example, the notification unit 136 refers to the payment history information and the bonus grant history information, and identifies the payment history information associated with the bonus grant time that is the same as the payment time as the payment history information corresponding to the payment-applied user. Then, the notification unit 136 identifies the payment history information including the same user ID and store ID as the user ID and store ID of the specified store included in the identified payment history information, and including a payment time later than the payment time included in the identified payment history information, as new payment history information corresponding to the payment-applied user. The notification unit 136 identifies the re-visit tendency of the payment-applied user based on the new payment history information corresponding to the payment-applied user.

For example, the analysis screen shown in FIG. 5 displays a button O9 labeled "Compare with users who applied coupons at time of payment." In response to button O9 being selected, the notification unit 136 displays the revisit tendency of users who applied coupons at time of payment and the revisit tendency of users who applied coupons after payment in a format that allows comparison. For example, the notification unit 136 displays a graph showing the distribution of the period until users who applied coupons at time of payment revisit, and a graph showing the distribution of the period until users who applied coupons after payment revisit side by side. In this way, the business can understand the revisit tendency when a special offer is applied to a user at time of payment and when a special offer is applied to a user after payment, and analyze whether applying a special offer to a user after payment is effective.

The notification unit 136 may also include in the analysis screen information indicating the effectiveness of granting a special benefit to a user after payment, based on a comparison result between the revisit tendency of the application user at the time of payment, based on the new payment history information of the application user at the time of payment, and the revisit tendency of the application user after payment, based on the new payment history information of the application user after payment. For example, the notification unit 136 calculates a score indicating the effectiveness of granting a special benefit for each of the revisit tendency of the application user at the time of payment, which is the period until the revisit, the frequency of the revisit, and the payment amount at the revisit.

For example, the notification unit 136 calculates the score so that the shorter the period until a revisit, the higher the score. The notification unit 136 also calculates the scoring so that the higher the frequency of revisits, the higher the score. The notification unit 136 also calculates the score so that the higher the payment amount at the revisit, the higher the score.

The notification unit 136 includes information in the analysis screen indicating that it is effective to give a benefit to a user after payment when the total score corresponding to the tendency of the applied user at the time of payment to revisit based on the new payment history information of the applied user after payment is higher than the total score corresponding to the tendency of the applied user at the time of payment to revisit based on the new payment history information of the applied user at the time of payment.

The notification unit 136 may include both the total score value when a reward is granted at the time of payment and the total score value when a reward is granted after payment in the analysis screen as information indicating the effectiveness of granting the reward. In this way, the business operator can understand whether applying a reward to a user after payment is more effective than applying a reward to a user at the time of payment.

The notification unit 136 may also identify payment-time application users and post-payment application users based on the payment time included in the payment history information and the bonus grant time associated with the payment history information, and identify the number of payment-time application users and the number of post-payment application users identified. The notification unit 136 may then identify the ratio between the number of times the bonus was applied to the user by a payment-time application request and the number of times the bonus was applied to the user by a post-payment application request, and include information indicating the identified ratio in the analysis screen. It can be seen that the analysis screen shown in FIG. 5 displays object O8 indicating the ratio between the number of times the bonus was applied to the user by a payment-time application request and the number of times the bonus was applied to the user by a post-payment application request.

The notification unit 136 also generates attribute distribution information indicating the distribution of attributes of the multiple post-payment application users. For example, the storage unit 12 stores user information that associates a user's user ID with attribute information indicating the user's attributes. The user attributes include various attributes such as age, sex, place of residence, and occupation. The notification unit 136 refers to the user information and identifies the attribute information associated with the user ID of each of the multiple post-payment application users. The notification unit 136 then notifies the attribute distribution information indicating the distribution of the identified attributes. Figure 7 is a diagram showing an example of attribute distribution information.

For example, the analysis screen shown in FIG. 7 displays a button O3 labeled "Attribute Information." In response to button O3 being selected, the notification unit 136 displays attribute distribution information indicating the distribution of attributes of multiple post-payment application users. FIG. 7 is a diagram showing an example of the display of attribute distribution information. As shown in FIG. 7, it can be seen that a graph indicating the distribution of age and gender, which are attributes of multiple post-payment application users, is displayed as the attribute distribution information. In this way, the business can understand what attributes users have who will be eligible for the application of benefits based on a post-payment application request.

Note that among post-payment application users, there may be users who frequently visit a specific store regardless of whether the benefit is applied or not. If such users are included in the analysis, there is a problem that it is difficult to grasp the effect of the benefit. In response to this, the notification unit 136 identifies, from among the multiple post-payment application users, one or more post-payment application users who have made a relatively small number of payments before the benefit is applied, based on the payment time and user ID included in the payment history information stored in the memory unit 12.

For example, the notification unit 136 identifies, for each of multiple post-payment application users, the number of payment history information pieces for which the benefit application time of the benefit based on the post-payment application request is not associated and the payment time is earlier than the benefit application time. The notification unit 136 then generates information indicating the presence or absence of new payment history information (revisit or not) corresponding to one or more identified users, and includes the generated information in the analysis screen. In this way, the payment processing device 1 can exclude users who frequently visit a specific store regardless of whether a benefit is applied, making it easier to understand the effect of the benefit.

The notification unit 136 may also identify, among post-payment application users, a user who revisited the store after the benefit was applied, based on the payment time and user ID included in the payment history information stored in the memory unit 12, and identify the payment history information before the benefit corresponding to that user was applied.

In this case, the notification unit 136 identifies, from among multiple pieces of payment history information corresponding to the post-payment application user for which new payment history information has been identified, payment history information that is not associated with the benefit application time of the benefit based on the post-payment application request and whose payment time is earlier than the benefit application time. When there are multiple pieces of payment history information whose payment times are earlier than the benefit application time, the notification unit 136 may identify a predetermined number of payment history information that include payment times relatively close to the benefit application time.

The notification unit 136 may identify information about the payment before the benefit was applied based on the payment history information before the benefit was applied, and notify the information about the payment. Here, the information about the payment before the benefit was applied is, for example, the payment amount and the time of payment. Note that if the payment history information includes a product ID, the information about the payment before the benefit was applied may include information indicating the product that the post-payment applying user purchased before the benefit was applied, based on the product ID. In this way, the business can grasp the payment trends before the benefit was applied corresponding to the post-payment applying user who returns to the store.

In addition, when the notification unit 136 determines, based on the payment time and user ID included in the payment history information stored in the memory unit 12, that the post-payment applicable user has not revisited the store within a specified period of time since the benefit was granted, the notification unit 136 may notify the user of information indicating the user's viewing status of the benefit information after the benefit was granted, based on viewing history information indicating the viewing history of the benefit information stored in the memory unit 12.

In this case, the notification unit 136 identifies, from among the multiple post-payment applicable users, one or more users who have not revisited the store within a specified period of time since the benefit was granted. The notification unit 136 refers to the browsing history information and identifies, from among the identified one or more users who have not revisited the store, users who viewed benefit information related to the benefit of a specified store after the benefit was granted time. The notification unit 136 then calculates the ratio of the number of users who viewed the benefit information to the number of users who have not revisited the store, and includes browsing status information indicating this ratio in the analysis screen. If the ratio of users who viewed the benefit information to users who will not revisit the store is high, it is considered that there are many users who do not find the benefit information attractive. For this reason, the payment processing device 1 can allow the business operator to understand whether the benefit information is effective by notifying the browsing status information.

[Modification 1]
In the above description, the predetermined payment method is a payment method using a code, but is not limited to this. For example, as long as the payment processing device 1 can acquire a user ID, a store ID, and payment information at the time of a user's payment, the predetermined payment method may be a payment method using short-range wireless communication such as NFC, a credit card, or a prepaid card, which is different from a payment method using code payment.

[Modification 2]
In the above description, the analysis screen does not include information that can identify an individual, such as a user ID, but this is not limited to the above. For example, if a user corresponding to a user ID has given permission for analysis based on payment history information in advance, the analysis screen may allow the user's revisit information to be viewed.

[Modification 3]
In the above description, the analysis screen includes various information indicating the application effect of a benefit based on a post-payment application request corresponding to the store ID and benefit ID of a specific store, but is not limited to this. For example, if a business operator operates multiple stores, the analysis screen may include various information indicating the application effect of a benefit based on a post-payment application request at each of the multiple stores.

In this case, the memory unit 12 stores an operator ID for identifying the operator and the store IDs of one or more stores operated by the operator in association with each other. The notification unit 136 receives a request to view an analysis screen including the operator ID from the operator terminal 4 used by the operator. The notification unit 136 identifies one or more store IDs associated with the operator ID included in the request to view the analysis screen, and identifies one or more bonus IDs associated with each of the identified one or more store IDs. The notification unit 136 then notifies the operator terminal 4 of an analysis screen including various information indicating the application effect of a bonus based on a post-payment application request corresponding to the identified bonus ID. In this way, the operator can understand the effect of a bonus based on a post-payment application request at a store that the operator operates, without specifying a store ID or bonus ID.

In this case, if there are multiple store IDs associated with the business ID, the notification unit 136 may notify an analysis screen showing various information indicating the application effect of the benefit based on the post-payment application request for each store. In addition, if there are multiple benefit IDs associated with the store ID associated with the business ID, the notification unit 136 may notify an analysis screen showing various information indicating the application effect of the benefit based on the post-payment application request for each benefit. In this way, the business can understand the effect of the benefit based on the post-payment application request for each store or benefit at the stores that they operate, without specifying the store ID or benefit ID.

[Effects of payment processing device 1]
As described above, the payment processing device 1 according to the present embodiment stores the user ID, the payment amount included in the payment request, and the payment time in the storage unit 12 as payment history information after a payment is made based on a payment request including the user ID of the user making a payment at a specific store and the payment amount of the payment, in association with the user ID, the payment amount included in the payment request, and the payment time as payment history information, and applies the benefit to the user based on the received post-payment application request when receiving from the user terminal 2 a post-payment application request that is a request to apply a benefit that can be applied based on a payment at a specific store corresponding to the payment history information. The payment processing device 1 identifies new payment history information of the user that is newly stored after the benefit is applied to the user based on the payment time and user ID included in the payment history information, and notifies related parties of the specific store of the user's revisit to the specific store based on the identified new payment history information. In this way, the payment processing device 1 can grasp the customer attraction effect of applying a benefit based on past payment records.

Furthermore, this invention will make it possible to contribute to Goal 9 of the United Nations' Sustainable Development Goals (SDGs), which is "Build resilient infrastructure, promote inclusive and sustainable industrialization, and promote innovation and infrastructure."

Although the present invention has been described above using embodiments, the technical scope of the present invention is not limited to the scope described in the above embodiments, and various modifications and changes are possible within the scope of the gist of the invention. For example, all or part of the device can be configured by distributing or integrating functionally or physically in any unit. In addition, new embodiments resulting from any combination of multiple embodiments are also included in the embodiments of the present invention. The effect of the new embodiment resulting from the combination also has the effect of the original embodiment.

Reference Signs List 1 Payment Processing Device 2 User Terminal 3 Shop Terminal 4 Business Operator Terminal 11 Communication Unit 12 Storage Unit 13 Control Unit 131 Registration Unit 132 Benefit Information Providing Unit 133 Payment Request Receiving Unit 134 Payment Processing Unit 135 Benefit Application Unit 136 Notification Unit S Payment System

Claims (13)

a storage control unit that, after a payment is made based on user identification information for identifying a user making a payment at a specific store and a payment request including a payment amount relating to the payment, stores the user identification information, the payment amount included in the payment request, and a payment time at which the payment was made in a storage unit as payment history information in association with each other;
a privilege application unit that, when receiving a post-payment application request from a user terminal used by the user, which is a request for application of a privilege applicable based on a payment at the specified store corresponding to the payment history information stored in the storage unit, applies the privilege to the user based on the received post-payment application request;
a notification unit that identifies new payment history information of the user that is newly stored in the storage unit after the benefit application unit applies the benefit to the user, based on the payment time and the user identification information included in the payment history information stored in the storage unit, and notifies related parties of the specified store of information regarding the user's revisit to the specified store based on the identified new payment history information;
An information processing device having the above configuration. The notification unit identifies new payment history information corresponding to each of the plurality of users, and notifies a person related to the predetermined store of the re-visit information based on the new payment history information of each of the identified plurality of users.
The information processing device according to claim 1 . The notification unit identifies a ratio of users who have revisited the specified store within a predetermined time period after the benefit was applied, based on new payment history information corresponding to each of the users, and notifies related parties of the specified store of the identified ratio of users as the revisit information.
The information processing device according to claim 2 . The notification unit generates statistical information relating to at least one of a period from when the benefit is applied to when each of the users revisits the store, a frequency of revisits, and a payment amount at the time of the revisit, based on new payment history information corresponding to each of the users, and notifies related parties of the specified store of the generated statistical information as the revisit information.
The information processing device according to claim 2 . when the privilege application unit receives from the user terminal a payment application request which is a request for applying a privilege applicable based on a payment at the time of payment at the specified store, the privilege application unit applies the privilege to the user based on the received payment application request, and stores the payment history information in association with a privilege granting time at which the privilege was granted;
The notification unit identifies a payment-time application user to whom a benefit is applied in response to the payment-time application request and a post-payment application user to whom a benefit is applied in response to the post-payment application request, based on the payment time included in the payment history information and the benefit grant time associated with the payment history information, and notifies the payment-time application user of a re-visit tendency of the payment-time application user based on new payment history information of the payment-time application user and a re-visit tendency of the post-payment application user based on new payment history information of the post-payment application user.
The information processing device according to claim 2 . The notification unit notifies information indicating an effect of granting a privilege to the user after payment based on a comparison result between a re-visit tendency of the application user at the time of payment based on new payment history information of the application user at the time of payment and a re-visit tendency of the application user after payment based on new payment history information of the application user after payment.
The information processing device according to claim 5 . The notification unit identifies, among the multiple users to whom the benefit was applied in response to the post-payment application request, one or more users who made a relatively small number of payments before the benefit was applied, based on the payment time and the user identification information included in the payment history information stored in the storage unit, and notifies the one or more users of information indicating the presence or absence of the new payment history information corresponding to the one or more users.
The information processing device according to claim 5 . the benefit application unit, when receiving, from the user terminal used by the user, a payment application request which is a request for applying a benefit applicable based on a payment at the time of payment at the specified store, applies the benefit to the user based on the received payment application request, and stores the payment history information in association with a benefit granting time at which the benefit was granted;
the notification unit refers to the payment time included in the payment history information and the benefit grant time associated with the payment history information, specifies a ratio between the number of benefits applied to the user in response to the payment application request and the number of benefits applied to the user in response to the post-payment application request, and notifies the user of information indicating the specified ratio.
The information processing device according to claim 1 . The notification unit refers to user information in which user identification information for identifying a user is associated with attribute information indicating attributes of the user, identifies attribute information associated with the user identification information of the user who has revisited the store, and notifies the user of the identified attribute information.
The information processing device according to claim 1 . The notification unit identifies a user to whom the benefit application unit has applied the benefit in response to the post-payment application request, based on the payment time and the user identification information included in the payment history information stored in the storage unit, and who has revisited the store after the benefit has been applied, and notifies the user of information regarding the payment before the benefit was applied, based on payment history information corresponding to the user before the benefit was applied.
The information processing device according to claim 1 . a storage unit that stores privilege identification information that identifies the privilege and privilege information that indicates the content of the privilege in association with each other;
a privilege information providing unit that, when receiving a request to view privilege information including user identification information and privilege identification information of the user from the user terminal of the user, transmits the privilege information to the user terminal, and stores in the storage unit viewing history information that associates the user identification information, the privilege identification information, and a transmission time of the privilege information;
When the notification unit determines, based on the payment time and the user identification information included in the payment history information stored in the storage unit, that the user to whom a privilege has been granted based on the post-payment application request has not revisited the store within a predetermined period of time since the privilege was granted, the notification unit notifies the user of information indicating the user's browsing status of the privilege information after the privilege was granted based on the browsing history information.
The information processing device according to claim 1 . The notification unit notifies a provider of funds for the benefit of information about the user's revisit to the specified store based on the new payment history information.
The information processing device according to claim 1 . The computer executes
a step of, after a payment is made based on user identification information for identifying a user making a payment at a specified store and a payment request including a payment amount relating to the payment, storing the user identification information, the payment amount included in the payment request, and a payment time at which the payment was made in a storage unit as payment history information in association with each other;
receiving, from a user terminal used by the user, a post-payment application request which is a request for application of a benefit applicable based on a payment at the specified store corresponding to the payment history information stored in the storage unit, applying the benefit to the user based on the received post-payment application request;
based on the payment time and the user identification information included in the payment history information stored in the storage unit, identifying new payment history information of the user that has been newly stored in the storage unit after the benefit has been applied to the user, and notifying related parties of the specified store of revisit information of the user to the specified store based on the identified new payment history information;
An information processing method comprising the steps of:

Images