JP6298205B1 - Transaction management system, transaction management method, and program thereof - Google Patents

Abstract

A technology for complementing member store information is provided. When a transaction is performed between a user and a member store using a card provided by a card issuer, the transaction management system 1 determines whether or not the card issuer approves the transaction. A receiving unit that receives authorization result information including information on member stores, a user-specific member store storage unit that stores information relating to member stores and user identifiers in association with each other, and a member store based on the authorization result information. When receiving a correction instruction including a user identifier and correction information related to the corrected member store from the notification unit that transmits the information and the determination result including the determination result to the user terminal and the user terminal, The user-specific member store storage unit includes a correction accepting unit that associates and registers the identifier of the user and the correction information regarding the corrected member store included in the correction instruction. When the correction information is associated, the notification unit creates notification information based on the correction information. [Selection] Figure 3

Description

  The present invention relates to a transaction management system, a transaction management method, a program thereof, and the like.

  In recent years, not only domestic purchases but also overseas purchases, Internet shopping purchases, and other opportunities to use cards such as credit cards and David cards are increasing. Along with this, the number of damages due to unauthorized use of cards is also increasing. Therefore, the importance of a mechanism by which a user can confirm the usage information of a card owned by the user is increasing (for example, Patent Document 1).

JP 2007-213491 A

  For example, if you use a credit card for transactions at a merchant that has a merchant contract with a card company, information about this transaction is sent to the card company's system via a dedicated network connecting the merchant and the card company. Is transmitted. However, the structure of data transmitted in this dedicated network is not uniform among the dedicated networks. For this reason, a part of the information may be lost on the system side of the card company that has received the transaction information. In this case, since the information regarding the card usage provided to the user is also incomplete, it is difficult for the user to confirm the information on the card usage.

  In view of the above circumstances, an object of the present invention is to provide a technique for supplementing information on member stores.

  The transaction management system according to the present invention determines whether or not to approve the transaction at the card issuer when the transaction is performed between the user and the member store using the card provided by the card issuer. Based on the authorization result information, the receiving unit that receives the authorization result information including the result and the information about the member store, the member store storage unit for each user that stores the information about the member store and the user identifier in association with each other, and the authorization result information Notification information including information related to the store and the determination result is transmitted to the user terminal of the user, and a correction instruction including the identifier of the user and the correction information regarding the corrected member store is received from the user terminal. In this case, based on the correction instruction, the user-specific member store storage unit stores the identifier of the user and the correction information regarding the corrected member store included in the correction instruction. And a correction receiving unit for registration, and when the notification unit creates notification information including information on a predetermined member store for a predetermined user, the notification unit stores the identifier of the predetermined user in the user-specific member store storage unit. When correction information related to a predetermined member store is associated, notification information is created based on the correction information.

  The program of the present invention can be installed or loaded on a computer through various recording media such as an optical disk such as a CD-ROM, a magnetic disk, or a semiconductor memory, or via a communication network.

  Further, in this specification and the like, the “unit” does not simply mean a physical configuration, but also includes a case where the functions of the configuration are realized by software. In addition, functions of one configuration may be realized by two or more physical configurations, or functions of two or more configurations may be realized by one physical configuration.

  ADVANTAGE OF THE INVENTION According to this invention, the technique which complements the information regarding a member store can be provided.

It is a block diagram of the system containing the transaction management system in embodiment of this invention. It is a figure which shows an example of the functional block of the issuer system in embodiment of this invention. It is a figure which shows an example of the functional block of the transaction management system in embodiment of this invention. It is a figure which shows an example of transaction history DB in embodiment of this invention. It is a figure which shows an example of the member store master in embodiment of this invention. It is a figure which shows an example of member store DB classified by user in embodiment of this invention. It is a figure which shows the aspect by which the member store master in embodiment of this invention is updated. It is a figure which shows the aspect in which member store DB classified by user in embodiment of this invention is updated. It is a figure which shows an example of the screen which the transaction management system in embodiment of this invention provides. It is a figure which shows an example of the screen which the transaction management system in embodiment of this invention provides. It is a figure which shows an example of the screen which the transaction management system in embodiment of this invention provides. It is a figure which shows an example of the screen which the transaction management system in embodiment of this invention provides. It is a figure which shows an example of the screen which the transaction management system in embodiment of this invention provides. It is a figure which shows an example of the sequence diagram of the system in embodiment of this invention. It is a figure which shows an example of the hardware constitutions of the system in embodiment of this invention.

[First Embodiment]
Hereinafter, one embodiment of the present invention will be described in detail. The following embodiments are examples for explaining the present invention, and are not intended to limit the present invention only to the embodiments. The present invention can be variously modified without departing from the gist thereof. Furthermore, those skilled in the art can employ embodiments in which the elements described below are replaced with equivalent ones, and such embodiments are also included in the scope of the present invention.

<1. Overview of system configuration>
FIG. 1 shows an example of the configuration of a transaction management system 1 according to the present embodiment. As shown in FIG. 1, the transaction management system 1 is a system (hereinafter referred to as “Issuer”) owned by a plurality of card issuing companies (hereinafter also referred to as “Issuer”) via a network N such as the Internet or a dedicated line. System 2), a terminal (hereinafter also referred to as “Member Store Terminal”) 3 owned by a retail store (hereinafter also referred to as “Member Store”) contracted with Issuer, and a card contract The user terminal 4 owned by the person is connected to each other. The member stores are not limited to actual retail stores, but include websites for non-face-to-face sales such as ATMs and Internet shopping. The issuer is not limited to a card company, and may be a bank.

  The network N is configured by a wireless network or a wired network. Examples of networks include cellular phones, PHS (Personal Handy-phone System) networks, wireless LAN (Local Area Network), 3G (3rd Generation), LTE (Long Term Evolution), 4G (4th Generation), (Registered trademark), infrared communication, Bluetooth (registered trademark), wired LAN, telephone line, power line network, IEEE 1394, and other networks.

  The portion of the network N that connects the member store terminal 3 and the issuer system 2 is a CAFIS (Credit And Finance Information System) network, VisaNet (registered trademark), BankNet, or other payment depending on the type of the issuer system 2. A network is used.

  In the following description, a credit card will be described as an example of a card used for transactions managed by the transaction management system 1 according to the present embodiment. However, the card is not limited to a credit card, and may be, for example, a prepaid card, a cash card, a David card, or a payment card.

  Further, the card according to the present embodiment can be used not only for face-to-face sales but also for non-face-to-face sales such as Internet shopping, services for withdrawing cash at overseas or domestic ATMs, and cashing services. When using a card for non-face-to-face sales, the user can use, for example, a card identifier (card ID) instead of an actual card for transactions. Furthermore, in non-face-to-face sales, the user can make a transaction using a predetermined ID linked to a card ID. The predetermined ID includes, for example, a login ID and a mobile ID for a predetermined system. For example, the user can make a transaction using a card ID associated with a login ID by logging in to a predetermined system. Further, the card ID may be linked to Osaifu-Keitai (registered trademark), other IC chip settlement, or the like.

<2. Detailed configuration>
<2-1. Merchant terminal 3>
The member store terminal 3 is a computer connected to the network N. Specifically, the member store terminal 3 is realized by, for example, a mobile phone, a smartphone, a PC (Personal Computer), a PDA (Personal Digital Assistant), a tablet, a wearable (Wearable) terminal, or the like.

  When the member store has an actual store, the member store terminal 3 has a function of scanning information recorded on the card, and credit approval information (hereinafter also referred to as “authorization information”) based on the scanned information. And has a function of transmitting to the issuer system 2. The authorization information includes, for example, a card ID, an identifier of the member store, an identifier of the member store terminal that performed the transaction (hereinafter also referred to as “terminal ID”), and a transaction price (hereinafter also referred to as “use amount”). The transaction date, the transaction identifier (hereinafter also referred to as “transaction ID”), the name of the member store, and the type (industry) of the member store. The authorization information may also include information related to the predetermined ID described above.

  When the information included in the authorization information is transmitted to the issuer system 2 through the payment network, the information may be lost depending on the type of the payment network. For example, when the authorization information is transmitted to the issuer system 2 via the CAFIS network, the name of the member store cannot be included in the data transmitted through the network. As a result, the name of the member store connected via the CAFIS network cannot be obtained on the issuer system 2 side. In the present embodiment, a case where information relating to a member store (for example, the name of a member store or the type of a member store) is missing from the authorization information when transmitting a specific payment network will be described as an example.

  When the authorization information is transmitted, the merchant terminal 3 receives a notification from the issuer system 2 to approve the use of the card read by the member store terminal 3 (hereinafter also referred to as “approval notification”). Sales information is transmitted to the issuer system 2. The sales information is information including at least a card ID, an identifier of a member store, a terminal ID, a sales amount, and a transaction date. On the other hand, when the member store terminal 3 receives a notification from the issuer system 2 that the member store terminal 3 does not approve the use of the reading card (hereinafter also referred to as “non-repudiation notification”), the transaction is not established.

  When the member store is engaged in mail order sales via the Internet or telephone, the member store terminal 3 and the function of scanning the information recorded on the card can be omitted.

<2-2. Function of Issuer System 2>
The issuer system 2 is a system managed by the issuer, and is realized by a PC or a server device connected to a network N such as the Internet or a dedicated line. The issuer system 2 has a function of examining whether or not the card read by the member store terminal 3 is usable in response to a request from the member store terminal 3.

  With reference to FIG. 2, the functional configuration of the issuer system 2 according to the present embodiment will be described. FIG. 2 is a diagram illustrating an example of a functional block diagram of the issuer system 2. The issuer system 2 includes a contractor information DB 231, a card information DB 232, a member store information DB 233, a fraud detection unit 201, a screening unit 202, and a matching unit 203.

  The contractor information DB 231 includes an identifier of a user who has a card contract with a corresponding issuer (hereinafter, also referred to as “contractor”), and a card contracted by the contractor. Are stored in association with each other. The card ID is an identifier assigned when the contractor concludes a card usage contract with the issuer. When the contractor has a plurality of cards, for example, by signing a plurality of usage contracts with the issuer, a plurality of card IDs are associated with one contractor identifier.

  In the card information DB 232, for example, a card ID, a contractor account from which a usage amount is deducted when the card is used, a usage history of the card, and a limit amount are stored in association with each other. Yes. The card information DB 232 may store an ID (such as the system ID or mobile ID described above) associated with the contractor account.

  Card usage history includes, for example, identifiers and transaction IDs of member stores where the card was used, usage amount, total amount of usage amount for the current month, usage date and time, date and time when the usage amount was withdrawn from the contractor account, and withdrawal Including the presence or absence of delays in

  In addition, the limit set when the contractor concludes the use contract with the issuer is stored as the initial value of the limit stored in the card information DB 232.

  The member store information DB 233 stores information about member stores. Specifically, in the member store information DB 233, the identifier of the member store, the name of the member store, the type of business, the business history, the monthly sales amount by the card, the information on the transition of the monthly sales amount, and the information on the illegal transaction. And so on.

  The member store information DB 233 can store, for example, information indicating an abrupt decrease or disappearance of sales as information on the transition of monthly sales. In addition, the member store information DB 233 can store, for example, information indicating that the unit sales price is unreasonably high as information on fraudulent transactions. Further, the member store information DB 233 can store, as other information, information on cancellation of member store contracts, closing of stores and changes of representatives, corporate bankruptcy and bankruptcy information posted in the official gazette, and the like.

  The name, type of business, and business history of the member store, etc. stored in the member store information DB 233 can be acquired for the member store directly managed by the issuer when the member store contract is made.

  On the other hand, for member stores other than directly managed stores, the name, type of industry, and business history of member stores, etc. are obtained from the received authorization information. Depending on the type of payment network with the member stores, such information may be missing. End up. For example, when the issuer system 2 is connected to a member store terminal via the CAFIS network, the name of the member store is missing in each record of the member store information DB. Therefore, for some member stores, the name, type of business, and business history of the member stores may be registered in a missing state.

  Note that other information stored in the member store information DB 233 can be added / updated on the basis of payment results with a card after the member store contract, regardless of whether the store is a directly managed store.

  The fraud detection unit 201 executes fraud detection processing based on the contractor information DB 231, the card information DB 232, and the member store information DB 233 when the authorization information is received from the member store terminal 3.

  For example, the fraud detection unit 201 refers to the card information DB 232 as fraud detection processing, and determines whether or not to defer use of the card from the use history corresponding to the card identifier included in the authorization information. Can do. Specifically, the fraud detection unit 201 can suspend the use of a card corresponding to a usage history for which the previous card usage amount has not been deducted from the contractor account and the payment due date has arrived. .

  Further, the fraud detection unit 201 may refer to the card information DB 232 and the member store information DB 233 to analyze a past fraudulent usage history and create a fraud detection rule in advance. For example, the fraud detection rules can be applied to the case where a contractor has used a card for a certain period of time in the case of “a lot of high-priced use in remote areas” or “highly cashable and high-priced products. For example, when the use continues. In this case, the fraud detector 201 can suspend use of a card that matches the fraud detection rule.

  When receiving the authorization information from the member store terminal 3, the examination unit 202 determines whether or not the card use should be approved for the transaction indicated by the transaction ID included in the authorization information. Specifically, the examination unit 202 examines whether or not the usage amount is within the range of the credit limit. At this time, the examination unit 202 can refer to the card information DB 232 and determine whether or not the added amount obtained by adding the current usage amount to the total usage amount for the current month exceeds the limit amount. When the added amount is equal to or less than the limit amount, the examination unit 202 approves the use of the card. On the other hand, when the added amount is larger than the limit amount or when the fraud detection unit 201 suspends the use, the examination unit 202 denies the use of the card.

  The examination unit 202 creates authorization result information for each transaction ID based on the determination result (hereinafter also referred to as “authorization result”), and transmits the authorization result information to the member store terminal 3 and the transaction management system 1. The authorization result information includes, for example, information included in the authorization information (card ID, member store identifier, terminal ID, usage amount, transaction date, transaction ID, member store name, type, etc.) together with the determination result. And an identifier of the issuer (hereinafter also referred to as “Issuer ID”).

  The matching unit 203 determines whether or not the information included in the authorization information matches the information included in the sales information. For example, the matching unit 203 determines, based on a predetermined logic, whether information such as a transaction date, a card ID, an identifier of a member store, a sales amount / use amount, and the like included in the sales information and the authorization data match. I do. If the information included in the authorization information matches the information included in the sales information, the matching unit 203 performs a sales amount withdrawal process from the user's contractor account. If the card used by the user is a credit card, the matching unit 203 performs a withdrawal process by designating a date determined at the time of the contract.

<2-3. User terminal 4>
The user terminal 4 is a computer connected to the network N. Specifically, the user terminal 4 is realized by, for example, a mobile phone, a smartphone, a PC, a PDA, a tablet terminal, a wearable terminal, or the like. The user terminal 4 is installed with a predetermined application, and can correct information (for example, a member store name, a business type, etc.) regarding the member store included in the received authorization result. At this time, the user terminal 4 transmits to the transaction management system 1 a user ID and a correction instruction including information related to the terminal ID and the corrected member store.

<2-4. Transaction management system 1>
The transaction management system 1 is realized by a PC or server device connected to the network N described above. The transaction management system 1 has a function of notifying the user terminal 4 based on the authorization information issued from the issuer system 2.

  With reference to FIG. 3, the functional configuration of the transaction management system 1 according to the present embodiment will be described. FIG. 3 is a diagram illustrating an example of a functional block diagram of the transaction management system 1. The transaction management system 1 includes an authorization notifying unit 101, a complementing unit 102, a correction receiving unit 103, a providing unit 104, a user information DB 131, a transaction history DB 132, a member store master 133, and a user-specific member store DB 134. It has.

  In the user information DB 131, a user ID is stored in association with a card ID.

  FIG. 4A shows the transaction history DB 132. As shown in FIG. 4, the transaction history DB 132 stores a card ID, an issuer ID, a terminal ID, a member store name, a member store type, a transaction date and time, and the like in association with the transaction ID. In FIG. 4A, an example is shown in which the record of the member store name and member store type is filled in as an example, but the member store name or member store type is missing in some or all of the records. There may be.

  FIG. 4B is the member store master 133. As shown in FIG. 4B, the member store master 133 stores an issuer ID, a terminal ID, and a member store name in association with each other. Similar to the transaction history DB 132, the member store master 133 may lack the member store name or the member store type.

  FIG. 4C shows the user-specific member store DB 134. As shown in FIG. 4C, the user-specific member store DB 134 stores a user ID, a terminal ID, a member store name, and a member store type in association with each other. Similar to the transaction history DB 132, the member store name or member store type may be missing in the user-specific member store DB 134.

  Upon receiving the authorization result information transmitted from the issuer system 2, the authorization notification unit 101 creates a usage notification. The usage notification is information including a transaction ID corresponding to the received authorization result information, information about the member store, an authorization result, and the reason if the authorization result is denied.

  The authorization notification unit 101 according to the present embodiment, when creating the usage notification, if the information about the corrected member store is registered in the user-specific member store DB 134, the registered corrected information is displayed. Use with priority. Specifically, the authorization notifying unit 101 refers to the user information DB 131 and identifies the user ID corresponding to the card ID included in the received authorization result information. Next, the authorization notifying unit 101 refers to the user-specific member store DB 134 and performs a search using the identified user ID and the terminal ID included in the authorization result information as keys. When the corresponding record is found in the user-specific member store DB 134, the authorization notification unit 101 creates a use notification using information about the member store corresponding to the record. On the other hand, when the corresponding record is not found, the authorization notifying unit 101 creates a usage notification using information regarding the member store included in the authorization result information.

  The authorization notification unit 101 transmits the created usage notification to the identified user.

  The notification to the user terminal 4 by the authorization notification unit 101 may be notified by e-mail or the like in addition to notifying a predetermined application installed in the user terminal 4.

  The complementing unit 102 performs member store name supplement processing for records in which the member store name is not registered in the member store master 133. The supplementing process will be specifically described with reference to FIG. 5. The complementing unit 102 refers to the member store master 133 and specifies the terminal ID corresponding to the record in which the member store name is not registered (FIG. 5 (1)). Line A). Next, the complementing unit 102 searches the member store master 133 using the identified terminal ID as a key, and extracts a record in which the member store name is registered (line B in FIG. 5 (1)). The complementing unit 102 registers the member store name of the extracted record in a record in which the member store name is not registered (FIG. 5 (2). Note that FIG. 5 (2) is the same state as FIG. 4B).

  The complementing unit 102 may perform the member store name complementing process at predetermined intervals, or may be performed each time the authorization result information is received. For example, when the complement process is performed every time the authorization result information is received, the complement unit 102 can perform the complement process when the received authorization result information does not include the member store name.

  In this way, the complementing unit 102 can supplement the authorization result information from a certain issuer using data of a different issuer even when data is lost during transmission through the network N.

  The processing when the complementing unit 102 complements the member store type is the same as that when the member store name is supplemented.

  When the correction receiving unit 103 receives a data correction instruction from the user terminal 4, the correction receiving unit 103 performs a correction process for updating the records of the transaction history DB 132 and the user-specific member store DB 134 based on the received correction instruction. The correction accepting unit 103 may update only one of the transaction history DB 132 and the user-specific member store DB 134.

The correction process will be specifically described with reference to FIG. 6 as an example in which the member store name is updated in the user-specific member store DB 134. As an example, it is assumed that the following information is included in the correction instruction.
-User ID User002
・ Terminal ID 002
-Member Store Name after Correction XXX Shop Shinjuku Store At this time, the correction reception unit 103 uses the user ID (User002) and the terminal ID (002) included in the correction instruction received from the user terminal 4 as keys, and the user-specific member store DB 134. Search for. When the corresponding record is found, the correction receiving unit 103 extracts the record (line C in FIG. 6 (1)), and updates the member store name of the extracted record to the member store name included in the correction instruction ( FIG. 6 (2)).

  On the other hand, when the corresponding record is not found, the correction receiving unit 103 creates a record by associating the user ID, the terminal ID, and the corrected member store name included in the correction instruction. At this time, the correction receiving unit 103 searches the member store master 133 with the terminal ID included in the correction instruction, and information on member stores other than the member store name corresponding to the terminal ID (in this embodiment, the type of member store corresponds). )) To create a record. The correction accepting unit 103 adds the created record to the user-specific member store DB 134.

  The update process for updating information related to other member stores is the same as the member store name update process, and a detailed description thereof will be omitted. Moreover, since the update process with respect to transaction history DB132 is the same as that of the member store DB134 classified by user, description is abbreviate | omitted. However, when correcting the transaction history DB 132, the correction receiving unit 103 preferably updates all records corresponding to the terminal ID included in the correction instruction. As a result, even when the user refers to the past transaction history, the user terminal 4 displays information regarding the corrected member store.

  The correction instruction may include a transaction ID instead of the terminal ID. In this case, the correction accepting unit 103 first searches the transaction history DB 132 and identifies the terminal ID corresponding to the transaction ID included in the correction instruction. The subsequent correction process is as described above. In addition, in the correction instruction, the user can not only correct the information regarding the member store but also complement the omission.

  The providing unit 104 performs a process of feeding back the complemented member store master 133 to the issuer system 2. Specifically, the providing unit 104 preferably extracts and provides a record corresponding to the ID of the issuer that manages the issuer system of the providing destination from the records registered in the member store master 133. The providing unit 104 preferably performs this feedback processing at a predetermined interval (for example, once a month or once a week), but may perform it every time the member store master 133 is supplemented.

  In the issuer system 2, the member store information DB 233 can be updated using the supplemented record provided from the providing unit 104.

<3. Screen example>
With reference to FIG. 7A thru | or FIG. 7F, an example of the screen which the transaction management system 1 which concerns on this embodiment provides is demonstrated. 7A to 7F are examples of screens displayed on the user terminal 4.

  FIG. 7A is a transaction information list screen. On the transaction information list screen, a list of transactions that have been performed in the past using the card with which the user of the user terminal 4 has contracted is displayed. When a transaction record displayed in a list is selected, a transaction information detail screen (FIG. 7B) is displayed. In the example of FIG. 7A, as an example, only the transaction for which the approval notification is issued in the issuer system 2 is displayed, but the present invention is not limited to this, and a denied transaction may be displayed.

  FIG. 7B is a diagram illustrating an example of a transaction information detail screen. In the example of FIG. 7B, the transaction information detail screen displays a transaction date and time, a transaction amount, the name of a member store 403 that performed the transaction, an icon 402 indicating the type of the member store, and the like. In addition, on the transaction information detail screen, an icon 401 for correcting information related to the member store is displayed. When the icon 401 is selected, a correction screen (FIG. 7C) is displayed.

  FIG. 7C is a diagram illustrating an example of a correction screen. In the example of FIG. 7C, on the correction screen, the member store name and the member store type can be corrected. For example, on the correction screen of FIG. 7C, the user can correct the name of the member store displayed in the input field 405. Further, by selecting an arbitrary type from the check box displayed in the type selection field 404, the type of the member store can be changed. In FIG. 7C, the type selection field 404 displays check boxes for four types of “home appliance / furniture”, “fashion”, “department store”, and “train / taxi”. Is not limited to this. Further, the type selection method in the type selection field 404 is not limited to a check box, and any method such as pull-down or manual input by the user can be used. When the information about the member store is corrected on the correction screen, a correction instruction including the corrected information is transmitted to the transaction management system 1.

  FIG. 7D is a diagram illustrating an example of a transaction information detail screen after the information about the member store is corrected. As shown in FIG. 7D, it can be seen that the member store name 403 and the icon 402 indicating the type have been modified from the screen shown in FIG. 7B.

  FIG. 7E is a transaction information list screen after the information on the member store is corrected. As shown in FIG. 7E, the corrected member store names are displayed in the records relating to the member stores that have been corrected.

<4. Processing sequence>
Next, a processing sequence of the system according to the present embodiment will be described with reference to FIG.

  When a user performs a transaction using a card at a member store (S11), authorization information is transmitted from the member store terminal 3 to the issuer system 2 (S12). In the issuer system 2, when the authorization information is received, the card information DB 232 and the member store information DB 233 are referred to and it is determined whether or not the current transaction is illegal (S13). Further, the issuer system 2 determines whether or not to approve the use of the card (S14), creates authorization result information from the determination result, and notifies the member store terminal 3 and the transaction management system 1 (S15). .

  In the transaction management system 1, a usage notification is created based on the received authorization result information and the user-specific member store DB 134. The usage notification includes a transaction ID, information about the member store, a determination result, and a reason for disapproval when the determination result is disapproval. The transaction management system 1 preferentially uses information related to a member store when the corrected information corresponding to the user to whom the use notification is transmitted is registered in the user-specific member store DB 134. To create a usage notification. The transaction management system 1 transmits the created usage notification to the user terminal 4 (S16).

  In the user terminal 4, the user selects and corrects the record of the transaction for which the member store information is to be corrected (S17). At this time, a correction instruction is transmitted from the user terminal 4 to the transaction management system 1 (S18). Upon receipt of the correction instruction, the transaction management system 1 updates the corresponding record in the transaction history DB 132 based on the correction instruction, and registers information on the corrected member store in association with the user ID in the user-specific member store DB 134. (S19).

  As a result, the updated transaction history is displayed on the user terminal 4. Further, the providing unit 104 provides the updated member store master 133 to the issuer system 2 at predetermined intervals (S20).

  As described above, according to the transaction management system 1 according to the present embodiment, the user can correct or supplement the information about the member store displayed on the user terminal 4 by operating the user terminal 4. Information on the modified member store is managed for each user in the transaction management system 1. Thereby, the user can change the information regarding the member store displayed on the user terminal 4 according to his / her preference. Furthermore, the transaction management system 1 can complement the record in which the information about the member store is missing in the member store master 133 based on the authorization result information transmitted from another issuer. As a result, in the transaction management system 1, it is possible to make a usage notification in a state in which the user can easily confirm the card usage history.

<5. Hardware configuration>
Hereinafter, an example of a hardware configuration when the above-described transaction management system 1, issuer system 2, member store terminal 3, and user terminal 4 are realized by a computer 800 will be described with reference to FIG. The function of each device can be realized by dividing it into a plurality of devices.

  As illustrated in FIG. 9, the computer 800 includes a processor 801, a memory 803, a storage device 805, an input I / F unit 807, a data I / F unit 809, a communication I / F unit 811, and a display device 813.

  The processor 801 controls various processes in the computer 800 by executing a program stored in the memory 803. For example, the authorization notifying unit 101, the complementing unit 102, the correction receiving unit 103, the providing unit 104, the fraud detection unit 201 and the examination unit 202 of the issuer system 2 in the transaction management system 1 are temporarily stored in the memory 803. It can be realized as a program that mainly operates on the processor 801.

  The memory 803 is a storage medium such as a RAM (Random Access Memory). The memory 803 temporarily stores a program code of a program executed by the processor 801 and data necessary for executing the program.

  The storage device 805 is a non-volatile storage medium such as a hard disk drive (HDD) or a flash memory. The storage device 805 stores an operating system and various programs for realizing the above-described configurations. In addition, the storage device 805 can also store a user information DB 131, a transaction history 132, a member store master 133, a user-specific member store DB 134, a contractor information DB 231, a card information DB 232, and a member store information DB 233. Such programs and data are referred to by the processor 801 by being loaded into the memory 803 as necessary.

  The input I / F unit 807 is a device for receiving input from the user. Specific examples of the input I / F unit 807 include a keyboard, a mouse, a touch panel, various sensors, and a wearable device. The input I / F unit 807 may be connected to the computer 800 via an interface such as a USB (Universal Serial Bus).

  A data I / F unit 809 is a device for inputting data from the outside of the computer 800. Specific examples of the data I / F unit 809 include a drive device for reading data stored in various storage media. The data I / F unit 809 may be provided outside the computer 800. In this case, the data I / F unit 809 is connected to the computer 800 via an interface such as a USB.

  The communication I / F unit 811 is a device for performing data communication with the external device of the computer 800 via the Internet N by wire or wireless. The communication I / F unit 811 may be provided outside the computer 800. In that case, the communication I / F unit 811 is connected to the computer 800 via an interface such as a USB.

  The display device 813 is a device for displaying various information. Specific examples of the display device 813 include a liquid crystal display, an organic EL (Electro-Luminescence) display, and a wearable device display. The display device 813 may be provided outside the computer 800. In that case, the display device 813 is connected to the computer 800 via, for example, a display cable. When a touch panel is employed as the input I / F unit 807, the display device 813 can be configured integrally with the input I / F unit 807.

  Each embodiment described above is for facilitating understanding of the present invention, and is not intended to limit the present invention. The present invention can be changed / improved without departing from the spirit thereof, and the present invention includes equivalents thereof. Each embodiment is an exemplification, and it is needless to say that a partial replacement or combination of configurations shown in different embodiments is possible, and these are also included in the scope of the present invention as long as they include the features of the present invention. .

DESCRIPTION OF SYMBOLS 1 Transaction management system 2 Issuer system 3 Merchant terminal 4 User terminal 101 Authorization notification part 102 Supplementation part 103 Correction reception part 104 Provision part

Claims (7)

When a transaction is performed between a user and a member store using a card provided by the card issuer, the card issuer determines whether to approve the transaction, and relates to the member store. A receiver for receiving authorization result information including information and an identifier of the card ;
A user-specific member store storage unit that stores information relating to the member store and the identifier of the user in association with each other;
A user information storage unit for storing the card identifier and the user identifier in association with each other;
Information on the member store based on the authorization result information for a user terminal corresponding to the identifier of the user associated with the identifier of the card included in the authorization result information in the user information storage unit ; a notification unit to send the notification information including the results of the determination,
When receiving a correction instruction including the identifier of the user and the correction information related to the corrected member store from the user terminal, based on the correction instruction, the user-specific member store storage unit stores the user's A correction accepting unit that registers and associates an identifier with correction information related to a corrected member store included in the correction instruction;
With
The notification unit
When creating notification information including information related to a predetermined member store for a predetermined user, the correction information related to the predetermined member store is associated with the identifier of the predetermined user in the user-specific member store storage unit. In this case, the notification information is created based on the correction information.
Transaction management system. The authorization result information further includes a terminal identifier of a terminal used for the transaction at the member store,
A member store master storage unit that stores the terminal identifier included in the authorization result information and the information about the member store in association with each other;
In the first authorization result information received from the first card issuer, if the information about the member store corresponding to the first terminal identifier is missing, the first received from the second card issuer A complementing unit that supplements information about the member store in the first authorization result information based on the second authorization result information including one terminal identifier and registers the information in the member store master storage unit;
The transaction management system according to claim 1, further comprising: A providing unit that provides the card issuer with the member store master storage unit that includes information about the member store supplemented by the complement unit;
The transaction management system according to claim 2, further comprising: Information about the member stores
The name or business type of the member store,
The transaction management system according to any one of claims 1 to 3. A transaction history storage unit that stores the identifier of the user, the information about the transaction, and the information about the member store where the transaction was performed, in association with each other;
The correction reception unit
When the correction instruction is accepted, based on the correction instruction, information on the member store associated with the user identifier included in the correction instruction in the transaction history storage unit is updated to the correction information. The transaction management system according to any one of claims 1 to 4. Computer
When a transaction is performed between a user and a member store using a card provided by the card issuer, the card issuer determines whether to approve the transaction, and relates to the member store. Receiving means for receiving authorization result information including information and an identifier of the card ;
User-specific member store storage means for storing information relating to the member store and the identifier of the user in association with each other,
User information storage means for storing the card identifier and the user identifier in association with each other;
For the user terminal corresponding to the identifier of the user associated with the identifier of the card included in the authorization result information in the user information storage means, based on the authorization result information, information about the member store, the judgment result and signal notifying means send the notification information including, and from the user terminal, the identifier of the user, when receiving the correction instruction including the correction information relating to modified the merchant, the modified A correction accepting means for registering the identifier of the user and correction information relating to the corrected member store included in the correction instruction in association with each other in the user-specific member store storage means based on the instruction;
Function as
When the notification means creates notification information including information related to a predetermined member store for a predetermined user, the notification means stores the predetermined member in the identifier of the predetermined user in the user-specific member store storage means. When the correction information related to the store is associated, it functions as a means for creating the notification information based on the correction information.
Program . A computer comprising a storage device
When a transaction is performed between a user and a member store using a card provided by the card issuer, the card issuer determines whether to approve the transaction, and relates to the member store. Receiving the authorization result information including information and an identifier of the card ; and
Storing in the storage device information relating to the member store and the identifier of the user in association with each other;
Storing the identifier of the card and the identifier of the user in association with each other in the storage device;
For the user terminal corresponding to the user identifier associated with the card identifier included in the authorization result information in the storage device, based on the authorization result information, information on the member store, and the determination a notification step of sending the notification information including the result and,
When receiving a correction instruction including the user identifier and the correction information related to the modified member store from the user terminal, based on the correction instruction, the storage device, the user identifier, A correction accepting step of registering the correction information related to the corrected member store included in the correction instruction in association with each other;
Run
The notification step includes
When creating notification information including information related to a predetermined member store for a predetermined user, the storage device stores correction information related to the predetermined member store in association with the identifier of the predetermined user. the further includes the step of creating the notification information based on the correction information, transaction management method.