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

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, damage to unauthorized use of cards tends to increase, and the importance of a mechanism for detecting unauthorized use is increasing.

  Patent Document 1 discloses a service for notifying a contractor of the use of a card by e-mail when sales data is registered in a card company database after the card is used.

JP 2007-213491 A

  In the system described in Patent Document 1, when a card is used at a member store or the like, first, information about the transaction (authorization information) is transmitted from the terminal of the member store to the card company system, and the transaction is performed at the card company system. It is determined whether or not to approve, and a determination result (authorization result) is transmitted to the terminal. In the authorization result, if the transaction is approved, the terminal of the member store transmits the sales data to the card company system, and after the predetermined processing is performed on the sales data in the card company system, the sales data Is registered in the database.

  When a card is illegally used, generally, the amount of damage can be reduced by detecting the unauthorized use as soon as possible. However, in the conventional method of detecting unauthorized use, such as the method described in Patent Document 1, even if the card is illegally used, the card subscriber does not use it until the sales data is registered in the database. It cannot be detected.

  SUMMARY OF THE INVENTION In view of the above circumstances, an object of the present invention is to provide a technique for detecting unauthorized use of a card based on authorization information.

  In the transaction management system according to the present invention, when a transaction is performed between a user and a member store using a card provided by the card company, a result of determining whether or not to approve the transaction in the card company is determined. Notification information including a receiver that receives authorization result information to be shown, notification information including a transaction identifier and a determined result based on the authorization result information, and notification information from the user terminal. An inquiry reception unit that issues a unique inquiry number, a storage unit that stores the inquiry number and the transaction identifier in association with each other, an inquiry number, an identifier of the transaction, and an inquiry content in the inquiry request An inquiry response unit that provides the card company system with a screen on which is displayed.

  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 detects the unauthorized use of a card | curd based on authorization information 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 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.

  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, a member store identifier, a transaction price (hereinafter also referred to as “use amount”), a transaction date, and a transaction identifier (hereinafter also referred to as “transaction ID”). , Preferably. The authorization information can also include information on the predetermined ID described above.

  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, a member store identifier, 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.

  In the contractor information DB 231, among the users according to the present embodiment, an identifier of a user who contracts a card with a corresponding issuer (hereinafter referred to as “contractor”), an ID of a card contracted by the contractor, and 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 an identifier of the member store, the name of the member store, the business type, the business history, the monthly sales amount by card, the information on the transition of the monthly sales amount, the information on fraudulent transactions, and the like. Has been.

  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, business type, and business history of the member store, etc. stored in the member store information DB 233 can be acquired when the issuer makes a contract with the member store. Further, other information stored in the member store information DB 233 can be added / updated based on the payment results by the card after the member store contract.

  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 132 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 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 make an inquiry about the authorization result via the application. At this time, an inquiry request including at least a transaction ID is transmitted from the user terminal 4 to the transaction management system 1.

  For example, when the transaction approval is received as an authorization result, but the transaction is unrecognized, the transaction may be illegally used. In this case, the user can make an inquiry request to the approved authorization result information, and can request a survey or stop using the card.

  Further, when the user tries to use the card but receives a denial notification, an inquiry request can be made to request permission to use the card.

<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, an inquiry receiving unit 102, an inquiry response unit 103, a user information DB 131, and an action information DB 132.

  In the user information DB 131, a user ID is stored in association with a card ID. In the action information DB 132, a transaction ID is stored in association with a card ID, transaction date / time, action reason, inquiry number, status, and the like.

  The inquiry number is a number issued by an inquiry receiving unit 102 described later. The action reason is information related to an overview of the inquiry from the user. The status is a status of an inquiry from the user, and is an identifier indicating a state such as in-progress, in-response, in-response.

  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, an authorization result, and the reason if the authorization result is denied. The authorization notifying unit 101 transmits a usage notification to the user corresponding to the card ID included in the authorization result information received with reference to the user information DB 131.

  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 inquiry reception unit 102 provides an inquiry screen to the user when receiving an inquiry request from the user terminal 4. The inquiry request includes at least a transaction ID. For example, when receiving an inquiry request, the inquiry reception unit 102 can issue an inquiry number, create a record in association with the transaction ID included in the received inquiry request, and add the record to the action information DB 132.

  Further, the inquiry reception unit 102 provides the user terminal 4 with a screen (see FIG. 6) for confirming the action method to the user. In this embodiment, there are two types of action methods: message inquiry and telephone inquiry. When the user selects a telephone inquiry as an action method, the inquiry reception unit 102 notifies the telephone number. On the other hand, when a web inquiry is selected, an inquiry screen is created and provided to the user terminal 4.

  The inquiry response unit 103 acquires detailed information necessary for the inquiry from the user terminal 4. The detailed information includes, for example, user authentication information (personal information such as date of birth), transaction ID, action reason, inquiry details, information for specifying a card, and the like. Upon receiving the detailed information, the inquiry response unit 103 provides an inquiry response screen (see FIGS. 7 and 8) to the issuer system 2. The inquiry response screen is a screen on which at least detailed information, a transaction ID, an inquiry number, and a status are displayed.

  Furthermore, the inquiry response unit 103 updates a corresponding record in the user information DB 131 when an operator using the issuer system 2 completes a response to the inquiry on the inquiry response screen. The inquiry response unit 103 can determine that the response has been completed when, for example, the status displayed on the response screen is updated so as to be handled by the operator. When the inquiry response unit 103 determines that the response has been completed, the inquiry response unit 103 transmits an answer to the inquiry input on the response screen to the user terminal 4.

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

  FIG. 4 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. 5) is displayed. Further, when the icon 401 is pressed in the record, an inquiry request is transmitted to the transaction management system 1. When an inquiry number is issued from the transaction management system 1, the transaction information list screen transits to the action method selection screen (FIG. 6). In the example of FIG. 4, 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. 5 is a diagram illustrating an example of a transaction information detail screen. In the example of FIG. 5, the transaction date and time, the transaction amount, the name of the store that performed the transaction, and the like are displayed on the transaction information detail screen. Further, the same icon 401 as the transaction information list screen is displayed on the transaction information detail screen.

  FIG. 6 is a diagram illustrating an example of an action method selection screen. In the example of FIG. 6, the action method selection screen includes a query number issued from the transaction management system 1 and a link 402 for selecting an action method (inquiry by message and inquiry by telephone in the example of FIG. 6). Is displayed. When the user presses the link 402 on the action method selection screen, information regarding the selected action method is transmitted to the transaction management system 1.

  7 and 8 are examples of screens displayed in the issuer system 2. FIG. 7 is an action user list screen. In the example of FIG. 7, the action user list screen displays a list of card IDs, transaction dates, transaction IDs, action reasons (inquiry outline), and statuses for transactions for which an inquiry request has been made. When the displayed record is selected on the action user list screen, the screen transitions to the action user detail screen (FIG. 8).

  FIG. 8 is a diagram illustrating an example of the action user details screen. In the example of FIG. 8, as the action user details screen, status, inquiry number, member ID, card number (for example, last 4 digits), transaction ID, transaction date / time, action reason, action method, inquiry details, inquiry history, etc. are displayed. Has been. An operator or the like who uses the issuer system 2 can respond to an inquiry from the user while referring to the action user detail screen of FIG.

<4. Processing sequence>
Next, a processing sequence of the system according to the present embodiment will be described with reference to FIG. In the example of FIG. 9, a case where the user selects inquiry by message as an action method will be described as an example.

  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). .

  The transaction management system 1 creates a usage notification based on the received authorization result information. The usage notification includes a transaction ID, a determination result, and a reason for rejection when the determination result is disapproval. The transaction management system 1 transmits the created usage notification to the user terminal 4 (S16).

  In the user terminal 4, the user selects a record of a transaction to be inquired (S17). At this time, an inquiry request is transmitted from the user terminal 4 to the transaction management system 1 (S18). When the inquiry request is received, the transaction management system 1 issues an inquiry number, adds a record to the action information DB 132 in association with the transaction ID included in the inquiry request (S19). The transaction management system 1 notifies the issued inquiry number and provides an action method selection screen to the user terminal 4 (S20).

  When the user selects an action method (S21), information on the selected action method is transmitted to the transaction management system 1 (S22). In the example of FIG. 9, since inquiry by message is selected as the action method, the transaction management system 1 creates an inquiry screen and provides it to the user terminal 4 (S23).

  A screen that allows the transaction management system 1 to confirm the authentication information and the inquiry details from the transaction management system 1 to the issuer system 2 when the user enters and sends the authentication information and the detailed information of the inquiry on the inquiry screen (S24). Is provided (S25). In the issuer system 2, when user authentication is performed by an operator using the issuer system 2 (S26), a response to the inquiry is made (S27). When an answer is input by the operator (S28), the content of the answer is transmitted to the user terminal 4 (S29).

  Thus, according to transaction management system 1 concerning this embodiment, a user can inquire an operator about past transactions based on an authorization result by operating user terminal 4. At this time, the user can make an inquiry with the same operation for both the approved transaction and the rejected transaction. Further, since the inquiry can be made based on the authorization result, the user can make an inquiry about unauthorized use before the usage amount is actually deducted from his / her account. Furthermore, the transaction management system 1 can request input of authentication information when the user makes an inquiry. Since the authentication information is presented to the issuer system 2 via a response screen, it can be managed more securely.

<5. Hardware configuration>
Hereinafter, an example of a hardware configuration in the case where 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. 10, 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 notification unit 101, the inquiry reception unit 102, the inquiry response unit 103, the fraud detection unit 201 and the examination unit 202 of the issuer system 2 in the transaction management system 1 are mainly stored in the memory 803, It can be realized as a program operating 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 store a user information DB 131, an action information DB 132, 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 Reception part 103 Response part 201 Fraud detection part 202 Examination part

Claims (7)

When a transaction is performed between a user and a member store using a card provided by a card company, authorization result information indicating a result of determining whether the card company approves the transaction is received. A receiver,
Based on the authorization result information, a notification unit that transmits notification information including an identifier of the transaction and information indicating a determination result of whether or not to approve the transaction to the user terminal of the user;
When receiving a query request for the notification information from the user terminal, a query receiving unit that issues a unique query number;
A storage unit for storing the inquiry number and the transaction identifier in association with each other;
An inquiry response unit that provides a screen displaying the inquiry number, the transaction identifier, and the inquiry content in the inquiry request to the card company system;
Equipped with a,
The notification information further includes:
If the information indicating the result of determining whether to approve the transaction indicates that the transaction has been rejected, including the reason for rejecting the transaction,
Transaction management system. The inquiry reception unit
When receiving an inquiry request for the notification information, providing a screen for selecting a method for making an inquiry to the user terminal;
The transaction management system according to claim 1. The inquiry response unit
Allowing the user to input authentication information for authenticating the user at the card company;
The transaction management system according to claim 1 or 2. The inquiry response unit
When a response to the inquiry request is completed in the card company, the user terminal is notified of an answer to the inquiry,
The transaction management system according to any one of claims 1 to 3. The inquiry reception unit
In the authorization result information, the inquiry request is received both when indicating that the transaction is approved and when indicating that the transaction is rejected.
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 a card company, authorization result information indicating a result of determining whether the card company approves the transaction is received. means,
Means for transmitting, to the user terminal of the user, notification information including an identifier of the transaction and information indicating a determination result of whether to approve the transaction based on the authorization result information;
Means for issuing a unique inquiry number when receiving an inquiry request for the notification information from the user terminal;
Means for storing the inquiry number and the transaction identifier in association with each other, and means for providing the screen of the inquiry number, the transaction identifier and the inquiry content in the inquiry request to the card company system,
To function as,
The notification information further includes:
If the information indicating the result of determining whether to approve the transaction indicates that the transaction has been rejected, including the reason for rejecting the transaction,
program. Computer
When a transaction is performed between a user and a member store using a card provided by a card company, authorization result information indicating a result of determining whether the card company approves the transaction is received. Steps,
Based on the authorization result information, transmitting notification information including an identifier of the transaction and information indicating a determination result on whether to approve the transaction to the user terminal of the user;
When receiving a query request for the notification information from the user terminal, issuing a unique query number;
Storing the inquiry number and the transaction identifier in association with each other;
Providing the card company system with a screen displaying the inquiry number, the transaction identifier, and the inquiry content in the inquiry request;
The execution,
The notification information further includes:
If the information indicating the result of determining whether to approve the transaction indicates that the transaction has been rejected, including the reason for rejecting the transaction,
Transaction management method.