JP2023067689A - Information processing apparatus, information processing method, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To identify a status of use of cashless settlement means.

SOLUTION: An information processing apparatus includes: a statement acquisition unit which acquires statement data of cashless settlement means; a commodity information storage unit which stores commodity information relating to a commodity; an electronic mail acquisition unit which acquires electronic mail data transmitted to a user of the cashless settlement means; a transaction data extraction unit which analyzes the electronic mail data to extract transaction data; a data collation unit which associates the transaction data with the statement data and specifies commodity information corresponding to the transaction data from a commodity information storage unit; and an output unit which outputs the statement data in association with the commodity information.

SELECTED DRAWING: Figure 1

COPYRIGHT: (C)2023,JPO&INPIT

Description

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

Patent Literature 1 describes associating credit card usage detail information with usage histories.

JP 2017-162296 A

However, in Patent Literature 1, the usage history is created based on the usage information of the credit card, and the usage history is created even if the usage information is illegally used.

SUMMARY OF THE INVENTION The present invention has been made in view of such a background, and an object of the present invention is to provide a technology capable of grasping the usage status of cashless payment means.

The main invention of the present invention for solving the above problems is an information processing apparatus comprising a usage statement acquisition unit for acquiring usage statement data of cashless payment means, and a product information storage unit for storing product information related to products. , an e-mail acquisition unit that acquires e-mail data sent to the user of the cashless payment means; a transaction data extraction unit that analyzes the e-mail data and extracts transaction data; a data match unit that associates usage detail data and identifies the product information corresponding to the transaction data from the product information storage unit; and an output unit that associates the usage detail data with the product information and outputs the product information. It is characterized by having

Other problems disclosed by the present application and solutions thereof will be clarified by the section of the embodiment of the invention and the drawings.

ADVANTAGE OF THE INVENTION According to this invention, the utilization condition of a cashless payment means can be grasped|ascertained.

It is a figure which shows the hardware structural example of the information processing apparatus 10 which concerns on this embodiment. 2 is a diagram showing a software configuration example of the information processing apparatus 10 of the embodiment; FIG. It is a figure explaining an example of e-mail data. It is a figure explaining operation|movement of the information processing apparatus 10 of this embodiment.

<Overview of the invention>
The contents of the embodiments of the present invention are listed and explained. The present invention has, for example, the following configurations.
[Item 1]
a usage detail acquisition unit that acquires usage detail data of cashless payment means;
a product information storage unit that stores product information about products;
an e-mail acquisition unit that acquires e-mail data sent to the user of the cashless payment means;
a transaction data extraction unit that analyzes the email data and extracts transaction data;
a data matching unit that associates the transaction data with the usage detail data and identifies the product information corresponding to the transaction data from the product information storage unit;
an output unit that outputs the usage detail data in association with the product information;
An information processing device comprising:
[Item 2]
The information processing device according to item 1,
the data matching unit confirms with the user whether or not the correspondence between the transaction data and the usage detail data is correct;
An information processing device characterized by:
[Item 3]
The information processing device according to item 1 or 2,
The transaction data extracting unit accesses the EC site that sent the email data when the email data does not include the transaction data but includes information specifying the transaction data, obtaining the transaction data;
An information processing device characterized by:
[Item 4]
The information processing device according to any one of items 1 to 3,
the transaction data includes a payment instrument;
Further comprising a product proposal unit that proposes products to the user based on the transaction data that includes a second payment method other than a predetermined first payment method, and proposes the use of the first payment method. ,
An information processing device characterized by:
[Item 5]
a step of obtaining usage detail data of cashless payment means;
storing product information about the product;
obtaining e-mail data sent to the user of the cashless payment means;
parsing the email data to extract transaction data;
a step of associating the transaction data with the usage detail data and identifying the product information corresponding to the transaction data from the product information storage unit;
a step of outputting the usage details data in association with the product information;
An information processing method characterized in that a computer executes
[Item 6]
a step of obtaining usage detail data of cashless payment means;
storing product information about the product;
obtaining e-mail data sent to the user of the cashless payment means;
parsing the email data to extract transaction data;
a step of associating the transaction data with the usage detail data and identifying the product information corresponding to the transaction data from the product information storage unit;
a step of outputting the usage details data in association with the product information;
A program that causes a computer to run

<System Overview>
An information processing apparatus 10 according to an embodiment of the present invention will be described below. The information processing apparatus 10 of the present embodiment stores the details of the payment displayed on the credit card usage statement as an electronic document issued when a commercial transaction is performed, such as when a product is purchased on an electronic commerce (EC) site. I am trying to get it from email. Transaction histories sent by e-mail have the same meaning as receipts in the real world. By linking with e-mail on the credit card usage statement screen on smartphone apps and on the web, it is possible to match product names and give hints to conventional statements. Specifically, the contents settled in commercial transactions are arranged in a list together with the usage details of the credit card, and by facilitating the confirmation of the expenditure, the actual product can be easily found. In addition, when matching with the total amount, date and time, and store name is successful, a specific product name can be linked and displayed. Furthermore, if there are any suspicious points in the credit card usage details, the user can confirm the transaction linked to the usage details, so it is expected that the user will be able to complete the transaction without contacting the credit card company. Support costs in the company can be reduced.

<Hardware configuration example>
FIG. 1 is a diagram showing a hardware configuration example of an information processing apparatus 10 according to this embodiment. The information processing apparatus 10 may be, for example, a general-purpose computer such as a workstation or personal computer, or may be logically realized by cloud computing. Note that the illustrated configuration is an example, and other configurations may be employed. The information processing apparatus includes a CPU 101 , a memory 102 , a storage device 103 , a communication interface 104 , an input device 105 and an output device 106 . The storage device 103 is, for example, a hard disk drive, solid state drive, flash memory, etc., which stores various data and programs. The communication interface 104 is an interface for connecting to the communication network 3, and includes, for example, an adapter for connecting to Ethernet (registered trademark), a modem for connecting to a public telephone network, and a wireless communication device for performing wireless communication. , a USB (Universal Serial Bus) connector and an RS232C connector for serial communication. The input device 105 is, for example, a keyboard, a mouse, a touch panel, a button, a microphone, etc. for inputting data. The output device 106 is, for example, a display, printer, speaker, or the like that outputs data. Each functional unit provided in the information processing apparatus 10, which will be described later, is implemented by the CPU 101 reading a program stored in the storage device 103 into the memory 102 and executing the program. 102 and a part of the storage area provided by the storage device 103 .

<Software configuration example>
FIG. 2 is a diagram showing a software configuration example of the information processing apparatus 10 of this embodiment. The information processing device 10 includes a usage statement acquisition unit 111, a product information acquisition unit 112, an e-mail acquisition unit 113, a transaction data extraction unit 114, a data matching unit 115, a data output unit 116, a data correction unit 117, an alert output unit 118, A product proposal unit 119 , a transaction data storage unit 131 , a rule storage unit 132 , an invoice name storage unit 133 , and a product information storage unit 134 are provided.

The usage statement acquisition unit 111 acquires usage statement data of a user's credit card. The usage statement acquisition unit 111 retrieves the usage statement by, for example, calling an API from the server of the card company that issues the credit card, or by automatically logging in to the web service and scraping the statement data list. Data can be obtained. Note that a known technique can be used for the usage detail data acquisition process. The usage detail data can include the date of use of the credit card, the name of the store used, the user, the amount of money used, and the like.

The transaction data storage unit 131 stores information on commercial transactions (hereinafter referred to as transaction data). The transaction data includes the date and time of receipt, date of transaction, name of the store where the transaction was made, name of the EC site where the store is located (EC site name), payment amount for the product or service, payment method, product It can include shipping charges, transaction amounts, product or service names (product names), and the like. The reception date and time can be the reception date and time of the e-mail. If the store independently sells online, the EC site name does not have to be set. Transaction data may include multiple goods or services that were the subject of a single payment. The transaction amount is the final amount after adding the shipping fee to the payment amount and performing additions and subtractions according to points, fees, etc., and is the settlement amount to be settled. The payment method indicates which payment method was used among various payment methods such as credit card, points, prepaid card, and QR code (registered trademark) payment.

When a plurality of commodities or services are traded in one commercial transaction, for example, when a plurality of commodities are purchased in one purchase procedure, one transaction data may contain a plurality of product names. In this case, the payment amount will be set to the total amount of multiple products (if points or coupons are used, the total amount will be adjusted for discounts, etc. related to the use of points or coupons). will be

Also, when a payment is made in one transaction, the e-mail data may contain one transaction amount and multiple payment amounts related to multiple transactions. In such a case, multiple store names may be registered in one transaction data. Also, one transaction data may include a plurality of combinations of payment amounts, payment means, and one or more product names.

The transaction data can also include, for example, payment categories (cash payment, lump-sum payment, revolving payment, installment payment, etc.) by means of payment.

The rule storage unit 132 stores rules for analyzing email data. The rule storage unit 132 can store rules for each store. A rule may be, for example, a learning model learned by machine learning of e-mail data. The rule storage unit 132 further associates and stores the pattern of the address that is the transmission source of the e-mail (it may be the address itself, or it may be a pattern expressing the address using a regular expression or the like). can also be

The billing name storage unit 133 associates and stores the name of the store, which is the subject of the commercial transaction, with the name of the billing person (description) who makes the billing as the member store of the credit card.

The product information storage unit 134 stores information (hereinafter referred to as product information) on products to be traded. Product information includes user purpose related to product, product category, consumables flag, product name, product name pattern, manufacturer name, manufacturer name pattern, product description, target Attributes, list prices, etc. may be included.

Multiple objectives can be set. For example, it is possible to set the purpose of "writing" and "decoration" for a ballpoint pen.

Categories can be set for each purpose. A category may have a plurality of hierarchies, and for example, large classification, medium classification, small classification, etc. can be set.

The consumables flag is information indicating whether or not the product corresponds to consumables.

The product name pattern can be a pattern that allows identification of variations in the notation of the product. In addition to the formal name of the product name, one or a plurality of names used to identify the product, such as a common name or an abbreviated name, may be set.

The target attribute may be, for example, information (demographic information, etc.) specifying a user segment assumed by this product, or information (segment information) for specifying a user or segment who likes this product. The segment information can be a feature quantity common to users corresponding to purchase data including a product ID.

The product information acquisition unit 112 acquires product information and registers it in the product information storage unit 134 . The product information acquisition unit 112 can receive input of product information from an operator, for example. For example, it can be product information attached to the JAN code. In addition, the product information acquisition unit 112 accesses the server of the manufacturer or the store and reads the product information provided on the website by scraping, for example. , the product information can be obtained by calling the API. The product information acquisition unit 112 can register the acquired product information in the product information storage unit 134 . When registering product information,

The e-mail acquisition unit 113 acquires e-mail data addressed to the user. E-mail acquisition unit 113 can access a mail server and acquire e-mail data from a user's mailbox according to protocols such as POP (Post Office Protocol) and IMAP (Internet Message Access Protocol). The information processing apparatus 10 includes a mail server storage unit that manages mail servers to be accessed in association with user IDs, and the e-mail acquisition unit 113 accesses all mail servers registered in the mail server storage unit. to collect email data.

The transaction data extractor 114 analyzes the e-mail data and extracts transaction data. E-mail data related to commercial transactions includes information related to transactions (transaction data). Transaction data extraction unit 114 can extract transaction data from e-mail data according to rules registered in rule storage unit 132 . The transaction data extraction unit 114 reads a rule corresponding to an address pattern matching the source address included in the e-mail data from the rule storage unit 132, and extracts transaction data from the e-mail data based on the read rule. can be extracted. Further, the transaction data extraction unit 114 may apply all the rules stored in the rule storage unit 132 and use the rules that successfully extract transaction data. A store name corresponding to the rule can be specified.

FIG. 3 is a diagram illustrating an example of e-mail data. FIG. 3 shows an example of a purchase notification mail 21, which is an electronic mail notified when a product is purchased on an EC (electronic commerce) site. The purchase notification mail 21 contains text data indicating the date and time 211 when the product was purchased, the purchased product 212, and the transaction amount 213 (including the amount paid for the product and the shipping fee). The transaction data extraction unit 114 can extract these data from the e-mail data according to rules and create transaction data based on the extracted data.

In addition, the transaction data extraction unit 114 acquires from the e-mail data information (for example, a URL for viewing the transaction history) for specifying a transaction history managed by an EC site, etc., and uses the acquired information as Based on this, it is possible to access the EC site and acquire the transaction data. In this case, the transaction data extraction unit 114 can extract the transaction data displayed as the transaction history from the linked web page by scraping or the like. Further, the transaction data extraction unit 114 can acquire transaction data by passing information for identifying the transaction history extracted from the e-mail data to an API provided by the EC site.

The data collating unit 115 associates the transaction data and usage detail data. In this embodiment, the billing name storage unit 133 is constructed as master data for notation of the store name displayed on the usage statement side of the credit card, and is compared with the purchase history issued as an e-mail. The data matching unit 115 determines whether the usage amount (settlement amount) and usage date (settlement date) included in the usage detail data match the transaction amount and transaction date included in the transaction data. can be associated with transaction data. In addition, if a billing name that matches the name of the store included in the billing statement data is registered in the billing name storage unit 133, the data matching unit 115 stores the shop name corresponding to the billing name storage unit 133 in the billing name storage unit 133. , and whether or not the read store name matches the store name in the transaction data may be used for association.

In addition, the data matching unit 115 determines the similarity of items for each pair of transaction data and usage detail data for which the difference between the usage date of the usage detail data and the transaction date of the transaction data is within a predetermined period (for example, one day). It is possible to calculate and associate those with the highest degree of similarity.

In addition, when the transaction data extracted from the e-mail data includes transactions related to multiple products, the data collating unit 115 can associate multiple products with one record of credit card usage details. . In this case, the data matching unit 115 can match the usage details of the credit card using the combined settlement amount for the multiple products.

In addition, the data matching unit 115 can match the transaction data extracted from the e-mail data with the usage details of the credit card using a learning model learned by machine learning. For example, machine learning can be performed using transaction data items and usage details items as feature vectors and whether or not matching is correct as teacher data. The information processing apparatus can be provided with a learning model storage unit that stores this learning model.

The feature amount vector can include the transaction date, store name, and transaction amount of the transaction data. In addition, the date of use, the name of the store used, and the amount of money used can be added to the feature quantity vector.

Also, the feature quantity vector for machine learning may include the EC site name of the transaction data. The feature vector may also include the payment method of the transaction data. The feature quantity vector may include the number of products (the number of product names) included in the transaction data. The feature amount vector may include the number of points used that are included in the transaction data. The feature amount vector may include the date and time when the transaction data was received, or the date and time zone of the date and time when the transaction data was received. Also, the feature amount vector may include the payment category included in the transaction data.

Also, the feature amount vector for machine learning may include the payment category of credit card usage details.

The data collating unit 115 can give the transaction data item and the usage detail data item to the learning model, determine whether the matching is correct or not, and associate the correct transaction data and the usage detail data with each other. Here, when the reliability of the inference by the learning model is equal to or less than a predetermined value, the data matching unit 115 inquires of the user whether the matching is correct or not, uses the result as teacher data, and uses it as an item of transaction data. It is also possible to carry out machine learning using items of detailed data as input data, and advance the learning model.

For each pair of transaction data and usage detail data for which the difference between the usage date of the usage detail data and the transaction date of the transaction data is within a predetermined period (for example, one day), the data matching unit 115 selects the above characteristics from the included items. A quantity vector can be created and applied to the learning model to determine whether the match is correct or not, and associate the correct pair. In addition, when a plurality of pairs yields correct results, the data matching unit 115 can associate the pair with the highest inference reliability as the correct answer.

In addition, when there are multiple pieces of transaction data on the same day and with the same store name, the data matching unit 115 creates a pair of each of the plurality of transaction data and each of the usage details on the same day and with the same store name. Pairs with the highest degree of similarity may be associated. In addition, the data matching unit 115 creates a feature amount vector from these pairs, gives it to the learning model, determines whether the matching is correct, associates the correct pairs, and if there are multiple correct answers, may try to match the pair with the highest confidence.

In addition, the data matching unit 115 may identify product information corresponding to the transaction data matched with the detailed usage data from the product information storage unit 134, and associate the specified product information with the detailed usage data. The data collating unit 115 can specify, for example, product information whose product name included in the transaction data matches the product name pattern. Further, when the transaction data includes the maker name and the product name, the data matching unit 114 searches for product information in which the maker name matches the maker name pattern and the product name matches the product name pattern. can also be specified.

In addition to pattern matching, the data collating unit 115 may specify product information using a learning model for estimating product information using, for example, each item of transaction data extracted from e-mail data as input data. can. In this case, for example, a learning model can be created and updated by machine learning using each item of transaction data as input data and a product ID specifying product information as teacher data.

The data collating unit 115 can also confirm with the user whether e-mail data sent from a preset EC site should be collated. The data matching unit 115 presents, for example, transaction data or product information for usage details data, displays a confirmation message such as "Is this content?" It can be determined that the match was successful only when it is accepted and entered correctly. Here, if matching fails, matching may be performed again using other rules.

The data collating unit 115 can also allow the user to collate usage detail data and product information for e-mail data sent from a preset EC site or shop. In this case, the data collating unit 115 confirms with the user as described above about transaction data or product data that are similar to the usage detail data but do not completely match but whose similarity is equal to or less than a predetermined value. can do.

<Display>
The data output unit 116 outputs the usage detail data in association with the transaction data. The data output unit 116 may, for example, transmit list data for displaying a list of usage detail data and transaction data in association with each other to the user terminal of the user or to the server of the credit card company. You may do so. As a result, when the credit card company displays the usage details, it is possible to display the transaction data linked to the usage details using the list data from the information processing apparatus 10 of the present embodiment.

Further, the data output unit 116 can also output the product information corresponding to the transaction data in association with the usage statement data instead of or in addition to the transaction data.

The data correction unit 117 accepts correction of matching from the user. The data correction unit 117 can receive, for example, an indication from the user that there is an error in matching the transaction data output by the data output unit 116 . The data correction unit 117 can notify the operator of the received error.

The data correction unit 117 can also accept designation of transaction data corresponding to usage detail data. For example, when an error is pointed out by the user, the data correction unit 117 transmits to the user's user terminal so as to display all of the transaction data or data not matched with the usage detail data, and Designation of correct transaction data can be accepted.

Further, the data corrector 117 may learn from the user's indication of an error. For example, if the rule is a learning model created by machine learning, the data correction unit 117 can update the learning model by reinforcement learning. Also, the learning model and pattern matching can be used together to estimate product information using the learning model for transaction data that does not match the pattern.

<fraud detection/guessing>
The alert output unit 118 can output an alert when transaction data cannot be associated with usage detail data. The alert output unit 118 may notify the alert by e-mail, may notify the alert by direct message or posting on a social network (SNS), or may notify the user of the mobile phone such as a smartphone. A push notification may be sent to the terminal, or a text message may be sent to the mobile phone by SMS or the like.

In addition, the alert output unit 118 notifies a message indicating that the matching has been performed or that the payment has been performed when the matching by the data matching unit 115 (matching of card payment and purchase history) is successful. You may make it

<Product proposal>
The product proposal unit 119 can propose products to the user. For example, based on transaction data and corresponding product information, the product proposal unit 119 can identify a category of interest to the user and propose other products in the identified category to the user.

In addition, the product proposal unit 119 can propose a product based only on transaction data settled by a payment method other than the credit card associated with the usage statement data. In this case, the product proposal unit 119 can propose payment with the credit card and perform rewards (for example, giving points, issuing coupons, etc.) on the condition of payment with the credit card. This makes it possible to recommend a so-called brand switch for a credit card company.

Further, when the transaction data is extracted from the e-mail data, if the payment method included in the transaction data is different from the credit card related to the usage statement data, the product proposal unit 119 displays an advertisement related to the credit card. Alternatively, a reward for using the credit card can be proposed along with the product proposal.

The information processing apparatus 10 may be provided with a campaign storage section for storing campaign information from a credit card company, and may make a proposal according to the campaign information. For example, the campaign information includes information specifying a product or category, a payment method (credit card, etc.), a campaign period, and a target user. For campaign information that is included in the campaign period and matches the user's target, advertising that the specified product or product belonging to the specified category will be paid by the specified payment method. can be displayed.

<Action>
FIG. 4 is a diagram for explaining the operation of the information processing apparatus 10 of this embodiment.

The e-mail acquisition unit 113 acquires user e-mail data (S301), and the transaction data extraction unit 114 extracts transaction data from the e-mail data (S302). As described above, the transaction data extraction unit 114 can read out rules corresponding to patterns matching the sender of the e-mail from the rule storage unit 132 and extract transaction data according to the read rules. Alternatively, the rules registered in the rule storage unit 132 may be tried in order until the transaction data is successfully extracted. The transaction data extraction unit 114 registers the extracted transaction data in the transaction data storage unit 131 (S303).

The usage statement acquisition unit 111 acquires usage statement data from, for example, a credit card website (S304). The data matching unit 115 searches for transaction data including the transaction date and transaction amount that match the usage date and usage amount of the usage detail data, and performs matching processing (S305). Note that the matching of data may be performed using the store name in addition to the transaction date and transaction amount (date of use and amount of use). In this case, the data matching unit 115 reads from the billing name storage unit 133 the store name corresponding to the statement notation that matches the usage store name of the usage details data, and matches the read store name with the store name of the transaction data. can be

If there is transaction data that includes the transaction date and transaction amount that match the usage date and usage amount, that is, if the usage detail data and the transaction data are successfully matched (S306: YES), the data matching unit 115 The product information corresponding to the data is specified from the product information storage unit 134 (S307), and the data output unit 116 outputs the usage details data and the product information in association with each other (S308). Here, the alert output unit 118 may notify the user that the matching is successful.

On the other hand, if the usage detail data and the transaction data are not matched (S306: NO), the alert output unit 118 outputs an alert (S309).

As described above, the usage details of the credit card and the transaction history sent by e-mail can be associated with each other and output.

Although the present embodiment has been described above, the above-described embodiment is intended to facilitate understanding of the present invention, and is not intended to limit and interpret the present invention. The present invention can be modified and improved without departing from its spirit, and the present invention also includes equivalents thereof.

For example, in the present embodiment, the information processing apparatus 10 acquires usage statement data on its own initiative, but the present invention is not limited to this. It is also possible to match transaction data corresponding to the data and respond with product information corresponding to the transaction data. For example, when a user viewing usage details discovers a suspicious usage statement (for example, when a bill is made from a store name that the user does not remember using), the usage details data is sent to the information processing apparatus 10. It is possible to confirm the transaction data corresponding to the usage detail data. In this case, for example, on the web page of the credit card company or in the smartphone application for viewing the usage details, a list of the usage details data is displayed, and a button or link for checking the details of the usage details data is arranged. Then, the usage detail data specified by the button or link is transmitted to the information processing device 10, and the information processing device 10 returns the transaction data in response to this, and displays the responded transaction data on the web page or application. can be made to

In addition, in the present embodiment, credit card usage statement data and transaction data extracted from e-mails and managed by the information processing device 10 are collated, but the present invention is not limited to this, and various cashless payments can be made. It can be applied to match usage detail data and transaction data related to means. Cashless payment means may include debit cards, electronic money, prepaid cards, smartphone payments (QR code (registered trademark) payments), etc., in addition to credit cards. In this case, the usage statement acquisition unit 111 naturally calls an API from the server of a business operator that provides cashless payment means such as debit card, electronic money, playpaid card, smartphone payment, etc., or performs automatic login to a web service. It is possible to scrape the list of detailed data by using

In addition, it is also possible to apply to settlement using points issued by operating companies. Points can be used for payment (settlement) only with points, or for other cashless payment means used together with points. When payment is made only with points, it is possible to compare point usage detail data with transaction data in the same manner as payment with a credit card. Here, the data matching unit 115 determines whether or not the transaction date, store name, and payment amount included in the transaction data match the usage date, store name, and number of points used in the detailed point usage data. can be applied.

When the points are partially used (the same processing may be performed when all the points are used for payment), the transaction data extraction unit 114 extracts the transaction data from the e-mail. Separately, the number of points used can be extracted. That is, transaction data includes the number of points used. The data matching unit 115 determines whether or not the transaction date, store name, and number of points used in the transaction data match the date of use, name of store used, and number of points used in the detailed point usage data. It can be carried out.

When the data matching unit 115 uses a learning model based on machine learning, the feature amount vector can include the number of usage points.

In addition, if the issuing entity that issues points obtains the transaction amount when points are used, and the point usage details include the transaction amount or payment amount and the number of points used, the data Matching unit 115 can match using transaction amounts or payment amounts. That is, the data collating unit 115 determines whether or not the transaction amount or the payment amount and the usage date included in the point usage specification data match the transaction amount or the payment amount and the transaction date included in the transaction data. Data and transaction data can be associated. Moreover, when the data matching unit 115 uses a learning model based on machine learning, the transaction amount or payment amount included in the usage detail data can be included in the feature amount vector.

It is also possible to collate the history of giving points with the transaction data. The issuer of the points provides grant statement data including the date when the points were granted (date of grant), the number of points granted, and the name of the store (store name) where the points were granted. Data can be obtained. The grant detail data can include the grant rate of the granted points. In this case, the data matching unit 115 can calculate the transaction amount (payment amount) based on the number of points and the award rate, and the calculated transaction amount and award date match the transaction amount and transaction date of the transaction data. Depending on whether or not to do so, the grant detail data and the transaction data can be associated with each other. Also, the store name included in the provision detail data and the store name included in the transaction data may be used for matching. In addition, the point issuer can include the transaction amount at the time of awarding the points in the granting detail data. may be used.) and the transaction date and transaction amount (furthermore, the store name may be used) of the transaction data. Alternatively, an EC site name may be used in place of the store name or in addition to the store name. That is, matching is performed according to whether the name included in the attached detail data matches with either the EC site name or the store name included in the transaction data, and whether the transaction date and transaction amount match. can be done. In addition, when creating a learning model by machine learning, the data matching unit 115 can add the grant date, the number of points, and the grant rate or the transaction amount included in the grant detail data to the feature amount vector.

111 usage statement acquisition unit 112 product information acquisition unit 113 e-mail acquisition unit 114 transaction data extraction unit 115 data matching unit 116 data output unit 117 data correction unit 118 alert output unit 119 product proposal unit 131 transaction data storage unit 132 rule storage unit 133 Billing name storage unit 134 Merchandise information storage unit

Claims (6)

a usage detail acquisition unit that acquires usage detail data of cashless payment means;
a product information storage unit that stores product information about products;
an e-mail acquisition unit that acquires e-mail data sent to the user of the cashless payment means;
a transaction data extraction unit that analyzes the email data and extracts transaction data;
a data matching unit that associates the transaction data with the usage detail data and identifies the product information corresponding to the transaction data from the product information storage unit;
an output unit that outputs the usage detail data in association with the product information;
An information processing device comprising: The information processing device according to claim 1,
the data matching unit confirms with the user whether or not the correspondence between the transaction data and the usage detail data is correct;
An information processing device characterized by: The information processing device according to claim 1 or 2,
The transaction data extracting unit accesses the EC site that sent the email data when the email data does not include the transaction data but includes information specifying the transaction data, obtaining the transaction data;
An information processing device characterized by: The information processing device according to any one of claims 1 to 3,
the transaction data includes a payment instrument;
Further comprising a commodity proposal unit that proposes a commodity to the user based on the transaction data including the second settlement means other than the predetermined first settlement means, and proposes the use of the first settlement means. ,
An information processing device characterized by: a step of obtaining usage detail data of cashless payment means;
storing product information about the product;
obtaining e-mail data sent to the user of the cashless payment means;
parsing the email data to extract transaction data;
a step of associating the transaction data with the usage detail data and identifying the product information corresponding to the transaction data from the product information storage unit;
a step of outputting the usage details data in association with the product information;
An information processing method characterized in that a computer executes a step of obtaining usage detail data of cashless payment means;
storing product information about the product;
obtaining e-mail data sent to the user of the cashless payment means;
parsing the email data to extract transaction data;
a step of associating the transaction data with the usage detail data and identifying the product information corresponding to the transaction data from the product information storage unit;
a step of outputting the usage details data in association with the product information;
A program that causes a computer to run

Images