Credit card use information management device and program

Abstract

To enable a user to easily check his / her credit card's unauthorized use.SOLUTION: A credit card use information management device according to an embodiment acquires photographic images from an imaging apparatus that captures paper media containing information related to the user's credit card use. At the time of use, it acquires location information from a GPS sensor provided in its own credit card use information management device. It acquires card usage detailed information from a credit card company, including the date of use, card identification information, amount used, and store information. From the photographic image, it recognizes credit card usage information, including the usage date, card identification information, usage amount, and store information. By using the credit card use detailed information, the credit card usage information, and the location information, it determines whether the credit card use detailed information is valid.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] An embodiment of the present invention relates to a credit card usage information management device and a program. [Background technology]

[0002] 2. Description of the Related Art In recent years, cashless transactions have become more common, and payments using credit cards (hereinafter also referred to as "cards") (hereinafter also referred to as "credit payments") have become widespread.

[0003] To check whether their credit card has been used fraudulently, credit card users can cross-check the statement they receive when using their card (such as a paper slip or, in the case of online payments, the order confirmation email) against the statement provided by the credit card company. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Patent No. 7029211 [Patent Document 2] Patent No. 4357235 [Patent Document 3] Patent No. 3729436 Summary of the Invention [Problem to be solved by the invention]

[0005] However, the above-mentioned confirmation method has problems such as being time-consuming, etc. In addition, while there is a conventional technology in which a service is in practical use in which the card company transmits the user's location information to the card company via an app provided by the card company and the card company detects fraudulent use, this does not reduce the burden on the user to check the card usage history.

[0006] SUMMARY OF THE PRESENT EMBODIMENT An object of the present invention is to provide a credit card usage information management device and program that enable a user to easily check whether or not a credit card has been used fraudulently. [Means for solving the problem]

[0007] The credit card usage information management device of the embodiment includes a photographed image acquisition unit that acquires a photographed image from a photographing device that photographs a paper medium on which information regarding a user's credit card usage is recorded, a location information acquisition unit that acquires location information from a GPS sensor provided in the credit card usage information management device at the time of the usage, a card usage statement information acquisition unit that acquires card usage statement information from a credit card company, the card usage statement information including at least the date of usage, card identification information, amount used, and store information, and a card usage statement information acquisition unit that acquires card usage statement information including at least the date of usage, card identification information, amount used, and store information from the photographed image. The card usage statement device includes a recognition unit which recognizes usage information, a judgment unit which judges whether the card usage statement is valid or not using the usage date, card identification information, usage amount, store information in the card usage statement information, the usage date, card identification information, usage amount, store information in the card usage information, and the location information, and in that case, when only the store information in the card usage statement information and the store information in the card usage information differ, judges that the card usage statement information is valid if the store information in the card usage statement information and the location information correspond, and a control unit which controls the display of the judgment result by the judgment unit on a display unit. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 is a block diagram showing an outline of the overall configuration of a card usage information management system according to an embodiment. [Diagram 2] FIG. 2 is a block diagram illustrating a functional configuration of a card usage history checking application according to the embodiment. [Diagram 3] FIG. 3 is a flowchart illustrating a process performed by the card usage history checking application according to the embodiment. [Figure 4] FIG. 4 is a flowchart showing details of the process in step S2 of FIG. [Diagram 5] FIG. 5 is a flowchart showing details of the process in step S4 of FIG. [Figure 6] FIG. 6 is a block diagram showing an outline of the overall configuration of a card usage information management system according to a modified example. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, an embodiment of a credit card usage information management device and a program according to the present invention will be described with reference to the drawings.

[0010] 1 is a block diagram showing an outline of the overall configuration of a card usage information management system S according to an embodiment. The card usage information management system S includes a server 10 provided in a card company 1, a server 20 provided in a card company 2, a card reader 31 and a card payment system 32 provided in a physical store 3, a card payment system 41 provided in an online store 4, and a mobile terminal 5 (card usage information management device).

[0011] The server 10 is a computer device that manages information relating to credit cards handled by the card company 1, and includes a card statement information DB (Data Base) 11 and an API (Application Program Interface) 12.

[0012] The card usage statement information DB11 stores card usage statement information regarding credit card usage, including at least the usage date, card identification information (card type (brand), credit card number, etc.), usage amount, and store information (store name, location information, etc.). Note that in this specification, card usage statement information may refer to a collection of one or more card usage history data, or may refer to a single card usage history data.

[0013] The API 12 is software for transmitting and receiving data (information) to and from external devices (such as the mobile terminal 5 and the card payment system 41).

[0014] The server 20 is a computer device that manages information related to credit cards handled by the card company 2, and includes a card statement information DB 21 and an API 22.

[0015] The card statement information DB21 stores card statement information regarding credit card usage, including at least the usage date, card identification information, usage amount, and store information.

[0016] The API 22 is software for transmitting and receiving data (information) to and from external devices (such as the mobile terminal 5 and the card payment system 32).

[0017] The card reader 31 is a device that reads a credit card when a user who purchases goods or services at the physical store 3 makes a credit card payment.

[0018] The card payment system 32 is a computer device that executes credit card payment based on the credit card information read by the card reader 31. For example, when a credit card issued by the card company 2 is used at the physical store 3, the card payment system 32 transmits card usage statement information including at least the date of use, card identification information (credit card information), amount used, and store information to the server 20 of the card company 2 at the time of credit card payment. The card payment system 32 also issues a paper slip containing the card usage statement information, and the user receives the paper slip. The paper slip may include a two-dimensional barcode indicating the card usage statement information.

[0019] The server 20 receives the card statement information from the card payment system 32 and stores the card statement information in the card statement information DB 21 .

[0020] The card payment system 41 of the online store 4 is a computer device that executes online credit card payment (hereinafter also referred to as "online payment") when a user purchases a product or service online at the online store 4 via a web browser 54 using a mobile terminal 5. For example, when a credit card issued by the card company 1 is used at the online store 4, the card payment system 41 transmits card usage statement information including at least the date of use, card identification information, amount used, and store information to the server 10 of the card company 1 at the time of credit card payment.

[0021] The server 10 receives the card statement information from the card payment system 41 and stores the card statement information in the card statement information DB11.

[0022] Next, the mobile terminal 5 will be described with reference to Fig. 2. Fig. 2 is a block diagram showing the functional configuration of a card usage history checking application 56 (hereinafter, also simply referred to as "application") according to the embodiment.

[0023] The mobile terminal 5 includes a camera 51 (photographing device), a GPS sensor 52, a touch panel 53 (display unit), a web browser 54, a mailer 55, and a card usage history confirmation application 56. The mobile terminal 5 is, for example, a smartphone, and includes, as hardware, in addition to the above-mentioned camera 51, for example, a RAM (Random Access Memory), a ROM (Read Only Memory), an SSD (Solid State Drive), and a CPU (Central Processing Unit).

[0024] The camera 51 is a device that takes pictures in response to operations by a user and outputs the taken images.

[0025] The GPS sensor 52 is a sensor that calculates the position information (for example, latitude information and longitude information) of the mobile terminal 5 based on radio waves received from a plurality of GPS satellites.

[0026] The touch panel 53 is a device that combines a display device that displays an image with a position detection device that detects a position touched during an operation.

[0027] The web browser 54 is software for browsing websites.

[0028] The mailer 55 is software for creating, displaying, sending and receiving e-mail.

[0029] 2, the card usage history checking application 56 includes a processing unit 57 and a storage unit 58. The storage unit 58 stores various types of information.

[0030] The processing unit 57 includes an acquisition unit 571 , a recognition unit 572 , a determination unit 573 , and a control unit 574 .

[0031] The acquisition unit 571 acquires various information and stores the acquired information in the storage unit 58. For example, the acquisition unit 571 (captured image acquisition unit) acquires a captured image from the camera 51 that captures an image of a paper slip (paper medium) on which information regarding the use of a credit card by a user is written.

[0032] Furthermore, when a user uses a credit card, the acquiring unit 571 (location information acquiring unit) acquires location information from the GPS sensor 52. This location information is stored in the storage unit 58 in association with date and time information.

[0033] The acquisition unit 571 (card statement information acquisition unit) acquires, for example, once a month, card statement information including at least the date of use, card identification information, amount used, and store information regarding credit card usage from the servers 10 and 20 of the credit card companies (card companies 1 and 2). The card statement information is stored in the storage unit 58.

[0034] Moreover, the acquiring unit 571 (online payment information acquiring unit) acquires online payment information including at least the date of use, card identification information, amount used, and store information as information related to the use of a credit card by a user for online payment.

[0035] Furthermore, acquisition unit 571 (URL information acquisition unit) acquires URL (Uniform Resource Locator) information used at the time of online payment. This URL information is stored in storage unit 58 in association with date and time information.

[0036] The recognition unit 572 recognizes card usage information including at least the usage date, card identification information, usage amount, and store information from the captured image of the paper slip acquired by the acquisition unit 571 using the camera 51. This may be achieved, for example, by reading the character information on the paper slip using an OCR (Optical Character Recognition) function, or by reading a two-dimensional barcode if one is attached to the paper slip.

[0037] The card usage information is stored in the storage unit 58, and a confirmation status flag (either "unconfirmed" or "confirmed") is added. The captured image used to recognize the card usage information may be stored in the storage unit 58, but it does not have to be stored.

[0038] Next, the processing of the determination unit 573 will be explained separately for the case of credit card payment at the physical store 3 and the case of credit card payment at the online store 4. In the case of credit card payment at the physical store 3, the determination unit 573 determines whether the card card statement information is valid or not, using the date of use, card identification information, amount used, and store information in the card statement information obtained from the card companies 1 and 2, and the date of use, card identification information, amount used, store information, and location information in the card statement information managed within the app.

[0039] In this case, when only the store information in the card statement information and the store information in the card usage information are different, and the store information in the card statement information and the location information correspond to each other, the determination unit 573 determines that the card statement information is valid. This corresponds to the case where the store information of both is different even if the card statement information is valid (for example, the case where one store name is the official store name of the actual store 3 and the other store name is the name of the station building in which the actual store 3 is located, etc.).

[0040] In addition, in the case of credit card payment at online store 4, the judgment unit 573 judges whether the card statement information is valid or not using the date of use, card identification information, amount used, and store information in the card statement information, and the date of use, card identification information, amount used, store information, and URL information in the online payment information.

[0041] In this case, when only the store information in the card statement information and the store information in the online payment information differ, and the store information in the card statement information corresponds to the URL information, the judgment unit 573 judges that the card statement information is valid.

[0042] The control unit 574 executes various controls. For example, the control unit 574 controls displaying the determination result by the determination unit 573 on the touch panel 53.

[0043] In addition, the control unit 574 displays a confirmation request screen to the user on the touch panel 53 for card statement information that is not determined to be valid, and if the user selects an item for responding to an inquiry to the credit card company, displays information regarding the inquiry to the credit card company.

[0044] Next, the processing by the card usage history checking application 56 will be described with reference to Fig. 3 to Fig. 5. Fig. 3 is a flowchart showing the processing by the card usage history checking application 56 of the embodiment. This processing is executed when the user performs a predetermined operation on the mobile terminal 5, periodically (for example, once a week, once a month, etc.), or when card usage statement information (card usage history confirmation notice) is received from the card companies 1 and 2.

[0045] In step S1, the acquisition unit 571 acquires card statement information from the card companies 1 and 2.

[0046] Next, in step S2, the processor 57 executes a card usage history confirmation process. Fig. 4 is a flowchart showing the details of the process in step S2 in Fig. 3.

[0047] In steps S21 to S28, the processing unit 57 executes the process for each piece of card usage statement information (card usage history data).

[0048] In step S22, the determination unit 573 refers to the storage unit 58 for one piece of target card usage history data, and extracts information that matches the search conditions from the card usage information group within the application. The search conditions are as follows. <Search criteria> (1) The dates of use match (2) Card identification information matches (3) The amounts used match (4) The confirmation status flag is "Unconfirmed"

[0049] Next, in step S23, the determination unit 573 determines whether or not the number of extracted data items is greater than 0. If Yes, the process proceeds to step S25, and if No, the process proceeds to step S24.

[0050] If the answer is No in step S23, it means that the number of extracted data items is 0, so in step S24, the control unit 574 sets the corresponding card usage history data as data to be confirmed. In other words, if the number of extracted data items is 0, it is possible that the card company has billed the user even though there is no record of the card being used (the user has no recollection of using the card), so it is considered appropriate to check the corresponding card usage history data later as data to be confirmed.

[0051] In step S25, the determination unit 573 determines whether or not any of the store name, location information, and URL of the store information matches, and if Yes, the process proceeds to step S27, and if No, the process proceeds to step S26.

[0052] For example, if one of the two store information data sets has a store name that is the official name of physical store 3 and the other store name is the name of the station building in which physical store 3 is located, then the wording will not match.

[0053] However, in the case of credit card payment at the physical store 3, if the store information in the card statement corresponds to the GPS location information, it is reasonable to determine that the card statement is valid. Therefore, in such a case, the determination unit 573 determines that the card statement is valid (i.e., determines Yes in step S25).

[0054] Furthermore, in the case of credit card payment at online store 4, if the store information in the card statement corresponds to the URL information used for online payment, it is reasonable to determine that the card statement is valid. Therefore, in such a case, judgment unit 573 judges that the card statement is valid (i.e., judges Yes in step S25).

[0055] If the answer is No in step S25, it means that the store information could not be determined to be valid using not only the store name but also the location information and URL information, so in step S26, the control unit 574 designates the pair of the corresponding card usage history data and the card usage information managed within the app as data to be confirmed.

[0056] In step S27, the control unit 574 updates the corresponding card usage information managed within the app, that is, changes the confirmation status flag from “unconfirmed” to “confirmed.” Card usage information whose confirmation status flag has become “confirmed” will not be subject to the card usage history confirmation process in step S2 from the next time onwards.

[0057] When the processes of steps S21 to S28 have been completed for all the card usage statement information (card usage history data), the process of step S2 ends.

[0058] 3, after step S2, in step S3, the determination unit 573 determines whether there is any data to be confirmed, and if Yes, the process proceeds to step S4, and if No, the process ends. Note that if No in step S3, the control unit 574 displays on the touch panel 53 that all card usage statement information (card usage history data) matches the card usage information.

[0059] In step S4, the control unit 574 executes a process for handling the data to be confirmed. 5 is a flowchart showing the details of the process in step S4 in FIG.

[0060] In step S41, the control unit 574 displays on the touch panel 53 a list of data to be checked.

[0061] Next, in steps S42 to S46, the control unit 574 executes a process for each piece of check-required data.

[0062] In step S43, if "No problem" is selected from the three options displayed on the touch panel 53, the control unit 574 proceeds to step S44, if "Hold" is selected, the control unit 574 proceeds to step S46, and if "Contact card company" is selected, the control unit 574 proceeds to step S45.

[0063] In step S44, the control unit 574 updates the confirmation status flag for the corresponding card usage information managed within the application from "unconfirmed" to "confirmed."

[0064] In step S44, control unit 574 displays contact information. For example, control unit 574 displays the telephone number of the call center of the relevant credit card company (either card company 1 or 2) on touch panel 53, allowing the user to make a call with one touch. Also, for example, control unit 574 displays an email template for sending an email to the relevant credit card company (either card company 1 or 2) on touch panel 53, allowing the user to send an email with a simple operation.

[0065] When the processes of steps S42 to S46 have been completed for all the check-required data, the process of step S4 ends.

[0066] In this way, according to the card usage information management system S of this embodiment, a user can easily check whether or not there has been any fraudulent use of his / her credit card at any time (for example, when a specified operation is performed by the user, periodically, or when card usage statement information is received from card companies 1 and 2).

[0067] In addition, even when the store information in the card statement information obtained from card companies 1 and 2 differs from the store information in the card statement information managed within the app, by using location information from GPS sensor 52 and URL information at the time of online payment, it is possible to determine with high accuracy whether the store information in the card statement information is legitimate.

[0068] In addition, when a user obtains a paper receipt at a physical store 3, the user can photograph the paper receipt with camera 51 and store the photograph as card usage information managed within the app, eliminating the need to store the paper receipt thereafter, thereby improving convenience.

[0069] In addition, in the case where a user has multiple types of credit cards, in the conventional technology, it was necessary to visually check whether or not the card has been used fraudulently for each credit card, which made the checking process cumbersome. However, in this embodiment, whether or not a credit card payment is made at the brick-and-mortar store 3 or the online store 4, the user can save card usage information in the app with a simple operation, and then easily check whether or not the card has been used fraudulently for all credit cards held at once.

[0070] More specifically, for example, if a user makes purchases of the same amount with the same credit card at two different stores on the same day, the process will flow as follows: In step S22 of FIG. 4, for one piece of card usage history data from the card company, two hits are found in the card usage information group within the app that match the above-mentioned search conditions (1) to (4). Then, in step S25, one of the two pieces of card usage information matches the store name, location information, or URL of the store information, so the result is Yes and the process proceeds to step S27. Therefore, that card usage history data is not data requiring confirmation.

[0071] Furthermore, if fraudulent use of the same amount occurs on the same day as the user's own purchase, the process will proceed as follows. In step S22 of FIG. 4, the card usage history data (fraudulent use) from the card company is hit with card usage information corresponding to the user's own purchase from among the card usage information group in the app as matching the above-mentioned search conditions (1) to (4). However, in step S25, the store information does not match the store name, location information, or URL (highly likely), so the result is No and the process proceeds to step S26. Therefore, the card usage history data becomes data that requires confirmation, and the user can easily deal with it by following the process in step S4 (FIGS. 3 and 5).

[0072] (Modification) Next, a modified example will be described. Even if a user does not remember using a credit card, a family member may have used the credit card. The modified example addresses this issue.

[0073] 6 is a block diagram showing an outline of the overall configuration of a modified card usage information management system S. Descriptions of matters similar to those of the card usage information management system S of FIG.

[0074] In the card usage information management system S in FIG. 6, a PC (Personal Computer) 6 and a cloud server 7 are added to the card usage information management system S in FIG.

[0075] The PC 6 includes an input unit 61 , a display unit 62 , a web browser 63 , a mailer 64 , and a card usage history confirmation application 65 .

[0076] The input unit 61 is an information input means, such as a keyboard or a mouse.

[0077] The display unit 62 is an information display means, and is, for example, an LCD (Liquid Crystal Display).

[0078] The web browser 63 is software for browsing websites.

[0079] Mailer 64 is software for creating, displaying, sending and receiving e-mail.

[0080] The card usage history checking application 65 has the same functions as the card usage history checking application 56 in FIG.

[0081] Cloud server 7 is a computer device, and includes card usage information DB 71 that stores card usage information received from mobile terminal 5 and PC 6. For example, card usage information of mobile terminal 5 is stored in card usage information DB 71 of cloud server 7, and PC 6 can obtain the card usage information by accessing cloud server 7. In other words, card usage information for multiple terminals such as mobile terminal 5 and PC 6 is managed in a unified manner by cloud server 7 (for example, a cloud server in a cloud environment such as OneDrive (registered trademark) or iCloud (registered trademark)) that can be accessed only by the user and his / her family.

[0082] When shopping using multiple terminals such as mobile terminals 5 and PCs 6 with credit card payment, or when shopping using multiple mobile terminals 5 using a family card (a card issued to a family member of the main member who is the credit card contract holder), the connection information to the cloud server 7 which is centrally managed, the terminal identifier which identifies the own terminal, and the authority are set in advance in each terminal's app (card usage history confirmation app 56, card usage history confirmation app 65).

[0083] The authority is specified in two levels, for example, "only data on the own terminal can be referenced" and "data on other terminals can also be referenced." When the card usage information is updated on the mobile terminal 5 or PC 6, the card usage information is transmitted from the app to the cloud server 7, and the data in the card usage information DB 71 of the cloud server 7 is updated. In this case, a terminal identifier, which is identification information for the mobile terminal 5 or PC 6, is also added to the card usage information.

[0084] When executing the card usage history confirmation process in step S2 of Figure 3, a terminal with the authority setting of "may also refer to data from other terminals" will match all data in the card usage information DB71 of the cloud server 7, while a terminal with the authority setting of "may only refer to data from its own terminal" will match only data in the card usage information DB71 of the cloud server 7 whose terminal identifier matches that of its own terminal.

[0085] Such permission settings make it possible, for example, for a parent to check their child's credit card purchase history for any fraudulent card use, but for the child to not check their parent's credit card purchase history for any fraudulent card use (in other words, restricting a child's access to their parent's shopping history altogether).

[0086] Although some embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be implemented in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their modifications are included in the scope and spirit of the invention, and are included in the scope of the invention and its equivalents described in the claims.

[0087] Furthermore, the programs executed as the card usage history checking application 56 and the card usage history checking application 65 of the present embodiment can be provided by being recorded in an installable or executable file format on a recording medium readable by a computer device, such as a CD (Compact Disc)-ROM (Read Only Memory), a flexible disk (FD), a CD-R (Recordable), a DVD (Digital Versatile Disk), etc. Furthermore, the programs may be provided or distributed via a network such as the Internet. [Explanation of symbols]

[0088] 1, 2...card company, 3...physical store, 4...online store, 5...mobile terminal, 6...PC, 7...cloud server, 10...server, 11...card usage statement information DB, 12...API, 20...server, 21...card usage statement information DB, 22...API, 31...card reader, 32...card payment system, 41...card payment system, 51...camera, 52...GPS sensor, 53...touch panel, 54...web browser, 55...mailer, 56...card usage history confirmation application, 57...processing unit, 58...memory unit, 61...input unit, 62...display unit, 63...web browser, 64...mailer, 65...card usage history confirmation application, 571...acquisition unit, 572...recognition unit, 573...determination unit, 574...control unit, S...card usage information management system

Claims

1. a captured image acquisition unit that acquires a captured image from an image capturing device that captures an image of a paper medium on which information regarding a user's use of a credit card is recorded; a location information acquisition unit that acquires location information from a GPS (Global Positioning System) sensor provided in the credit card usage information management device at the time of the usage; a card usage statement information acquisition unit that acquires card usage statement information including at least a usage date, card identification information, a usage amount, and store information from a credit card company regarding the usage of the credit card; a recognition unit that recognizes card usage information including at least the date of credit card usage, card identification information, usage amount, and store information from the captured image; a determination unit which determines whether the card statement information is valid by using the usage date, card identification information, usage amount, and store information in the card statement information, the usage date, card identification information, usage amount, and store information in the card statement information, and the location information, and in this case, when only the store information in the card statement information and the store information in the card statement information differ, and when the store information in the card statement information and the location information correspond to each other, determines that the card statement information is valid; A credit card usage information management device comprising: a control unit that controls displaying a result of the judgment by the judgment unit on a display unit.

2. an online payment information acquisition unit that acquires online payment information including at least a date of use, card identification information, a usage amount, and store information as information regarding a user's use of a credit card for online payment; a URL information acquisition unit that acquires URL (Uniform Resource Locator) information used at the time of the online payment; a card usage statement information unit that acquires card usage statement information including at least a usage date, card identification information, a usage amount, and store information from a credit card company regarding the usage of the credit card; a determination unit which determines whether the card statement information is valid by using the usage date, card identification information, usage amount, and store information in the card statement information, the usage date, card identification information, usage amount, and store information in the online payment information, and the URL information, and in this case, determines that the card statement information is valid when only the store information in the card statement information and the store information in the online payment information differ and the store information in the card statement information corresponds to the URL information; A credit card usage information management device comprising: a control unit that controls displaying a result of the judgment by the judgment unit on a display unit.

3. The credit card usage information management device of claim 1 or claim 2, wherein the control unit displays a confirmation request screen to the user on the display unit for the card usage statement information that is not determined to be valid, and when an item for responding to an inquiry to the credit card company is selected by the user, displays information regarding the inquiry to the credit card company.

4. Computer, a captured image acquisition unit that acquires a captured image from an image capturing device that captures an image of a paper medium on which information regarding a user's use of a credit card is recorded; a location information acquisition unit that acquires location information from a GPS sensor provided in the credit card usage information management device at the time of the usage; a card usage statement information acquisition unit that acquires card usage statement information including at least a usage date, card identification information, a usage amount, and store information from a credit card company regarding the usage of the credit card; a recognition unit that recognizes card usage information including at least the date of credit card usage, card identification information, usage amount, and store information from the captured image; a determination unit which determines whether the card statement information is valid by using the usage date, card identification information, usage amount, and store information in the card statement information, the usage date, card identification information, usage amount, and store information in the card statement information, and the location information, and in this case, when only the store information in the card statement information and the store information in the card statement information differ, and when the store information in the card statement information and the location information correspond to each other, determines that the card statement information is valid; A program for causing the control unit to function as a control unit that controls displaying the determination result by the determination unit on a display unit.

5. Computer, an online payment information acquisition unit that acquires online payment information including at least a date of use, card identification information, a usage amount, and store information as information regarding a user's use of a credit card for online payment; a URL information acquisition unit that acquires URL information used at the time of the online payment; a card usage statement information unit that acquires card usage statement information including at least a usage date, card identification information, a usage amount, and store information from a credit card company regarding the usage of the credit card; a determination unit which determines whether the card statement information is valid by using the usage date, card identification information, usage amount, and store information in the card statement information, the usage date, card identification information, usage amount, and store information in the online payment information, and the URL information, and in this case, determines that the card statement information is valid when only the store information in the card statement information and the store information in the online payment information differ and the store information in the card statement information corresponds to the URL information; A program for causing the control unit to function as a control unit that controls displaying the determination result by the determination unit on a display unit.

Images