JP2020166671A - Request management system, request management method and computer program - Google Patents

Abstract

To enable smooth communication between member stores and issuers.SOLUTION: The request management system includes: a request information storage unit for storing request information in which an approval number indicating an approval of a payment using a cashless medium, an identification number of the cashless medium used in the payment, and information indicating a request content related to the payment using the cashless medium are associated with one another; and a control unit that executes a first notification process for, in response to the request information being registered in the request information storage unit by one of an entity associated with the identification number of the cashless medium and an entity capable of making payment using the cashless medium, notifying the other entity that the request information has been registered, associates a response to the request content included in the request information with the request information, and executes a second notification process for, in response to the request information being registered in the request information storage unit by the other entity, notifying the response having been registered to the entity that has registered the request information.SELECTED DRAWING: Figure 1

Description

The present invention relates to a request management system, a request management method, and a computer program.

If credit card fraud is suspected in a credit card business transaction, the merchant may ask the issuer to confirm that the transaction is genuine. Then, it is determined whether or not to deliver the product according to the result of the confirmation. On the other hand, the issuer may suspend or suspend the delivery of goods to the member store if it considers that the product has been misused without confirmation from the member store. Such exchanges between the merchant and the issuer are carried out manually by telephone, e-mail or fax. For this reason, there are cases where the communication between the member store and the issuer is not smooth due to information leakage due to the use of telephone, e-mail or fax, delay due to reception outside business hours, and misunderstanding of telephone.

JP-A-2018-200596

In view of the above circumstances, it is an object of the present invention to provide a technique capable of more smoothly communicating between a member store and an issuer.

One aspect of the present invention includes a communication unit that communicates with another device via a network, an approval number indicating that payment is permitted using a cashless medium, and cashless used for the payment. A request information storage unit that stores request information associated with an identification number of a medium and information representing a request content related to payment using the cashless medium, and a subject associated with the identification number of the cashless medium. Alternatively, the communication unit indicates that the request information has been registered in response to the request information being registered in the request information storage unit by any one of the entities that can pay using the cashless medium. The first notification process for notifying the other subject via the above is executed, the response to the request content included in the request information is associated with the request information, and the other subject registers the request information in the request information storage unit. A request management system including a control unit that executes a second notification process for notifying the entity that registered the request information via the communication unit that the answer has been registered.

One aspect of the present invention is the request management system, wherein the control unit communicates from a subject associated with an identification number of the cashless medium or a subject capable of paying using the cashless medium. When a request for charting the request information is received via the unit, the request information stored in the request information storage unit is classified according to the request content and the answer, and the chart information is charted. Is generated, and the chart information is transmitted to the subject who transmitted the request via the communication unit.

One aspect of the present invention is the above-mentioned request management system, in which the cashless medium is a credit card, and the identification number of the cashless medium is the first six digits of the credit card number.

One aspect of the present invention includes a communication unit that communicates with another device via a network, an approval number indicating that payment is permitted using a cashless medium, and cashless used for the payment. It is a request management method performed by a request management device including a request information storage unit that stores request information associated with an identification number of a medium and information representing a request content related to payment using the cashless medium. The request information is stored in the request information storage unit by either the subject associated with the identification number of the cashless medium or the subject capable of paying using the cashless medium. In response to the registration, the first notification process for notifying the other entity that the request information has been registered is executed via the communication unit, and the response to the request content included in the request information is given. In association with the request information, in response to being registered in the request information storage unit by the other entity, the subject who registered the request information is notified via the communication unit that the answer has been registered. It is a request management method having a control step for executing the notification process of 2.

One aspect of the present invention is a computer program for operating a computer as the above-mentioned request management system.

According to the present invention, the communication between the member store and the issuer can be performed more smoothly.

It is a schematic block diagram which shows the system configuration of the request management system 1. It is a schematic block diagram which shows the outline of the functional structure of the request management apparatus 100. It is a figure which shows one of the specific examples of an authentication information table. It is a figure which shows one of the specific examples of a member store information table. It is a figure which shows one of the specific examples of an issuer information table. It is a figure which shows one of the specific examples of a request information table. It is a figure which shows one of the specific examples of the attribute information which a request information table has. It is a figure which shows one of the specific examples of the chart information. It is a schematic block diagram which shows the outline of the functional structure of the member store terminal 200. It is a schematic block diagram which shows the outline of the functional structure of the issuer terminal 300. It is a sequence chart which shows the specific example of the processing flow when the identity verification request is executed among the operation of the request management system 1. It is a sequence chart which shows the specific example of the processing flow when delivery stop is executed as a request content in the operation of the request management system 1. It is a sequence chart which shows the specific example of the processing flow at the time of carrying out delivery hold as a request content in the operation of the request management system 1. It is a sequence chart which shows the specific example of the processing flow at the time of carrying out delivery hold as a request content in the operation of the request management system 1. It is a schematic block diagram which shows the system configuration of the request management system 1a. It is a schematic block diagram which shows the outline of the functional structure of the proxy terminal 500.

Hereinafter, a specific configuration example of the present invention will be described with reference to the drawings. FIG. 1 is a schematic block diagram showing a system configuration of the request management system 1. The request management system 1 includes a request management device 100, a member store terminal 200, and an issuer terminal 300. The request management system 1 manages the requests made between the member store terminal 200 and the issuer terminal 300 by executing the request management program. The request made from the member store terminal 200 to the issuer terminal 300 is, for example, an identity verification request. An identity verification request is a procedure by which an issuer confirms whether a payment for a commercial transaction using a credit card is a payment made by the authentic owner of the credit card. In this embodiment, payment means that the cardholder pays money to the issuer. Money is, for example, the price of goods purchased from a merchant by the cardholder. Specific procedures for requesting identity verification include identity verification and attribute inquiry. Identity verification is a procedure for directly confirming with the owner whether or not the person who made the payment for the commercial transaction using the credit card at the member store is the genuine owner of the credit card used for the commercial transaction. is there. Attribute confirmation is a procedure for confirming whether the attribute information notified to the member store by the person who made the payment for the commercial transaction using the credit card has the same attribute information as the genuine owner of the credit card. is there. Attribute information is information about the credit card owner, such as name, delivery address, telephone number or date of birth. In the present embodiment, the case where the card is a credit card will be described as an example, but the card is not limited to the credit card. For example, the card may be a cashless payable card such as a prebate card or a debit card.

The request made from the issuer terminal 300 to the member store terminal 200 is, for example, a delivery status confirmation request. The delivery status confirmation request is a procedure for requesting a member store to confirm whether or not the purchased product has been delivered from the member store. The delivery status confirmation request includes, for example, delivery suspension and delivery suspension. Suspension of delivery is a procedure for requesting a member store to suspend delivery of purchased products. Delivery hold is a procedure for requesting a member store to hold delivery of a purchased product. With delivery hold, the issuer asks the authentic owner of the credit card if the item has been purchased while the delivery is pending.

The request management device 100, the member store terminal 200, and the issuer terminal 300 can all communicate with each other via the network 400. The network 400 is a wide area communication network such as the Internet. The network 400 may be a network using wireless communication or a network using wired communication. The network 400 may be configured by combining a plurality of networks. The network 400 is only a specific example of a network for realizing communication of each device, and another configuration may be adopted as a network for realizing communication of each device. For example, communication between specific devices may be realized using a network different from the network used for communication between other devices. Specifically, the communication between the request management device 100 and the member store terminal 200 may be realized by a network different from the communication between the request management device 100 and the issuer terminal 300.

FIG. 2 is a schematic block diagram showing an outline of the functional configuration of the request management device 100. The request management device 100 is configured by using an information processing device such as a server device or a mainframe. The request management device 100 includes a communication unit 101, an authentication information storage unit 102, a member store information storage unit 103, an issuer information storage unit 104, a request information storage unit 105, and a control unit 106.

The communication unit 101 is a communication device such as a network interface. The communication unit 101 is communicably connected to the network 400 by a predetermined protocol. The communication unit 101 communicates data with other devices via the network 400 under the control of the control unit 106.

The authentication information storage unit 102 is configured by using a storage device such as a magnetic hard disk device or a semiconductor storage device. The authentication information storage unit 102 stores the authentication information table. FIG. 3 is a diagram showing one of the specific examples of the authentication information table. The authentication information table has a plurality of authentication information records. The authentication information record has each value of identification information and password. The identification information is information for identifying a subject registered in advance as a subject requesting authentication from the request management device 100. The entity requesting authentication is, for example, a member store terminal 200 or an issuer terminal 300. A password is composed of a plurality of letters and numbers. The password is information used by the request management device 100 to identify whether or not the subject requesting authentication is a genuine subject. As the password, for example, a one-time password may be used. The one-time password may be composed of a plurality of characters or numbers including, for example, a randomly generated character string.

The member store information storage unit 103 is configured by using a storage device such as a magnetic hard disk device or a semiconductor storage device. The member store information storage unit 103 stores the member store information table. FIG. 4 is a diagram showing one of the specific examples of the member store information table. The merchant information table has a plurality of merchant information records. The member store information record has each value of identification information, member store name, member store identification information, terminal identification information, and contact information. The member store name represents the name of the member store that owns the member store terminal 200. A member store is a facility or store that has signed a contract with the issuer to accept the use of the card. The member store identification information is information for identifying the member store that owns the member store terminal 200. The member store identification information may be composed of a plurality of letters and numbers. The member store identification information may be information issued by the issuer according to the contract between the member store and the issuer. The terminal identification number is a number that identifies the credit card reader used in the member store that owns the member store terminal 200. The reading device is, for example, a CAT (Credit Authorization Terminal) terminal. The terminal identification number may be, for example, a number pre-assigned to the reader. The contact information is information on the contact information of the user of the member store to which the received request is notified when the request (for example, delivery status confirmation request) or the like is received from the issuer terminal 300 to the member store terminal 200. The member store user is, for example, a person who uses the request management system 1 via the member store terminal 200. The user of the member store may be, for example, an employee of the member store. The contact information is, for example, information regarding the means of contacting the user of the member store (for example, an e-mail address, a telephone number, a messenger ID, etc.). The means of communication may be e-mail, SMS (Short Message Service), or messenger. The contact means may be any means as long as it can notify the user of the member store of the request. A member store is an aspect of an entity that can make payments using cashless media.

The issuer information storage unit 104 is configured by using a storage device such as a magnetic hard disk device or a semiconductor storage device. The issuer information storage unit 104 stores the issuer information table. FIG. 5 is a diagram showing one of the specific examples of the issuer information table. The issuer information table has a plurality of issuer information records. The issuer information record has the issuer name, issuer identification information, and contact values. The issuer name represents the name of the issuer who owns the issuer terminal 300. The issuer identification information is information for identifying the issuer who owns the issuer terminal 300. The issuer identification information may be composed of a plurality of letters and numbers. The issuer identification information may be, for example, the issuer identification number (IIN: Issuer Identification Number) of the first 6 digits of the credit card, or the bank identification number (BIN: Bank Identification Number). The contact information is information on the contact information of the issuer user who is notified of the received request when a request (for example, an identity verification request) is received from the member store terminal 200 for the issuer terminal 300. The issuer user is, for example, a subject who uses the request management system 1 via the issuer terminal 300. The issuer user may be, for example, an issuer employee. The contact information is, for example, information regarding the means of contacting the issuer user (for example, an email address, a telephone number, a messenger ID, etc.). The means of communication may be e-mail, SMS (Short Message Service), or messenger. The means of contact may be any means that can notify the issuer user of the request. An issuer is an aspect of a subject associated with an identification number of a cashless medium. The issuer identification information is an aspect of the identification number of the cashless medium.

The request information storage unit 105 is configured by using a storage device such as a magnetic hard disk device or a semiconductor storage device. The request information storage unit 105 stores the request information table. FIG. 6 is a diagram showing one of specific examples of the request information table. The request information table has a plurality of request information records. The request information record has each value of request date, status, member store identification information, issuer identification information, card information, approval number, authorization date and time, attribute information, amount of money, identity verification information, and delivery status information. The request date represents the date when the request is made from the member store terminal 200 to the issuer terminal 300, or from the issuer terminal 300 to the member store terminal 200. The status represents the progress of the request. The status has, for example, information on the progress status of the request (for example, personal use confirmation request, personal use confirmation hearing, attribute inquiry request, attribute inquiry result reply, delivery stop request, delivery result reply, delivery hold request, etc.). Status values are not limited to these. Status is determined based on the progress of the Merchant or Issuer's work and the content of the request. Card information represents information about the card used in the commercial transaction. The card information is information that can identify a commercial transaction paid using the card by combining with other information. The card information may be, for example, the last four digits of the credit card when a commercial transaction is carried out using the credit card. The approval number is the number given by the issuer when payment is approved using the card. For example, when payment is made by credit card, authorization is required of the issuer by the credit card reader provided in the member store. The authorization number is given by the issuer if the issuer approves the requested authorization. The approval number is an aspect of a payment identification number given to payments using cashless media. Authorization is the issuer's approval process for card payments. The authorization date and time is the date and time when the issuer approves the authorization requested by the issuer. Attribute information is information about a customer who makes a payment using a credit card (hereinafter, referred to as "customer"). The attribute information is the information notified by the customer when the payment is made. The attribute information represents, for example, information about the customer such as a name, a delivery address, a telephone number, and a date of birth. The amount represents the amount paid using a credit card. The identity verification information is information representing the result of identity verification or attribute inquiry performed by the issuer. The identity verification information is input via the issuer terminal 300. When "identity verification" is performed by the issuer, information regarding the result of identity verification such as, for example, the person who was the person, who was not the person, or who could not be contacted is input as the identity verification information. When an "attribute inquiry" is performed by the issuer, information regarding the result of inquiring the attribute information such as, for example, matching with the person or not matching the person is input as the identity verification information. The delivery status information is information indicating the result of the delivery of the product being suspended or suspended by the member store. The delivery status information is input via the member store terminal 200. As the delivery status information, for example, information on the delivery status such as shipped, unshipped or unknown is input.

FIG. 7 is a diagram showing one of the specific examples of the attribute information included in the request information table. The attribute information represents information about the customer such as name, delivery address, telephone number, and date of birth. The name represents the customer's name. The name is the information notified by the customer when payment is made using a credit card. The shipping address represents the shipping address of the goods purchased by the customer. The shipping address is information notified by the customer in response to payment by credit card. The telephone number represents a telephone number that can call the customer. The telephone number is information notified by the customer in response to payment using a credit card. The date of birth represents the date of birth of the customer. The date of birth is information notified by the customer in response to payment using a credit card. The information represented by the attribute information is not limited to the above. The attribute information may have, for example, a zip code, an e-mail address, or an apartment name representing a delivery address, or may have a name divided into a surname and a first name.

The control unit 106 is configured by using a processor such as a CPU (Central Processing Unit) and a memory. The control unit 106 functions as an authentication unit 161, an identity verification processing unit 162, a delivery status confirmation processing unit 163, and a request information management unit 164 when the processor executes a specific program.

The authentication unit 161 performs processing related to authentication. When the authentication unit 161 receives the authentication request from the member store terminal 200, for example, the authentication unit 161 determines whether or not the identification information and the password included in the authentication request are valid information. Specifically, the authentication unit 161 has one of the authentication information records in which the identification information included in the authentication request and the password associated with the identification information are recorded in the authentication information table. It is determined whether or not the identification information and the password match. In the authentication unit 161, when the identification information included in the authentication request and the password associated with the identification information match the identification information and the password in the authentication information record, the identification information and the password included in the authentication request are valid. It is judged that the information is information. When the identification information included in the authentication request and the password associated with the identification information do not match the identification information and password of the authentication information record, the authentication unit 161 validates the identification information and password included in the authentication request. It is judged that the information is not correct. The authentication unit 161 transmits an authentication response to the member store terminal 200 according to the determination result. When, for example, the authentication unit 161 determines that the identification information and the password included in the authentication request are valid information, the authentication unit 161 transmits an authentication response indicating that the authentication is approved. When, for example, the authentication unit 161 determines that the identification information and the password included in the authentication request are not valid information, the authentication unit 161 transmits an authentication response indicating that the authentication is not permitted. Even when the authentication request is received from the issuer terminal 300, the authentication unit 161 performs the authentication-related process in the same manner.

The identity verification processing unit 162 performs processing related to identity verification. When the identity verification processing unit 162 receives the identity verification request from the member store terminal 200, for example, the identity verification processing unit 162 acquires the member store identification information regarding the member store terminal 200 that sent the identity verification request. The identity verification processing unit 162 generates request information based on the information included in the received identity verification request and the acquired member store identification information. The identity verification request includes, for example, information representing the content of the request (for example, identity verification or attribute inquiry), issuer identification information, card information, approval number, authorization date and time, attribute information, and values related to the amount of money. The identity verification processing unit 162 sets the date on which the identity verification request is received as the value of the request date of the request information. When the information representing the content of the request is "identity verification", the identity verification processing unit 162 sets the value of the status of the request information to "identity verification request". When the information representing the request content is "attribute inquiry", the identity verification processing unit 162 sets the status value of the request information as "attribute inquiry request". The identity verification processing unit 162 records the generated request information as a request information record in the request information table. Further, when the request information record is recorded in the request information table, the identity verification processing unit 162 notifies a predetermined contact of the identity verification request. The identity verification request may include information such as a URL (Uniform Resource Locator) for the issuer user to access the request information record, and information regarding the request content such as status. Further, when the identity verification processing unit 162 receives the identity verification response from the issuer terminal 300 that has received the identity verification request, the identity verification processing unit 162 transmits a confirmation notice to the member store terminal 200 that has made the identity verification request. The confirmation notification may include identification information such as a URL for accessing the request information record and information regarding the request content such as status.

The delivery status confirmation processing unit 163 performs processing related to the delivery status confirmation. When the delivery status confirmation processing unit 163 receives a delivery status confirmation request from, for example, the issuer terminal 300, the delivery status confirmation processing unit 163 generates request information based on the information included in the received delivery status confirmation request. The delivery status confirmation request includes, for example, information indicating the content of the request (for example, delivery suspension or delivery suspension), member store identification number, issuer identification information, card information, approval number, authority date and time, attribute information, and values related to the amount. Is done. The delivery status confirmation processing unit 163 sets the date on which the delivery status confirmation request is received as the value of the request date of the request information. When the information representing the request content is "delivery stop", the delivery status confirmation processing unit 163 sets the value of the status of the request information to "delivery stop request". When the information representing the request content is "delivery hold", the delivery status confirmation processing unit 163 sets the value of the status of the request information to "delivery hold request". The delivery status confirmation processing unit 163 records the generated request information as a request information record in the request information table. Further, when the request information record is recorded in the request information table, the delivery status confirmation processing unit 163 notifies the predetermined contact of the delivery status request. The delivery status request may include information such as a URL for accessing the request information record and information regarding the request content such as status. Further, when the delivery status confirmation processing unit 163 receives the delivery status response from the member store terminal 200 that has received the delivery status request, the delivery status confirmation processing unit 163 transmits a confirmation notification to the issuer terminal 300 that has made the delivery status confirmation request.

The request information management unit 164 processes the request information recorded in the request information management table. When the request information management unit 164 receives a chart information request from, for example, the member store terminal 200 or the issuer terminal 300, the request information management unit 164 generates chart information based on the request information record recorded in the request information table. Hereinafter, processing when a chart information request is received from the member store terminal 200 will be described. Even when the chart information request is received from the issuer terminal 300, the request information management unit 164 performs the same processing. The request information management unit 164 acquires all the member store information records having the identification information included in the authentication information transmitted by the member store terminal 200 in the authentication process from the member store information table. The request information management unit 164 classifies the request information record according to the status of the acquired request information record. The request information management unit 164 counts the number of classified request information records. The request information management unit 164 generates a drawn bar graph as chart information with the horizontal axis representing the status and the vertical axis representing the number of counted records.

FIG. 8 is a diagram showing one of specific examples of chart information. The chart information includes a chart image 231 and a button image 232, a chart image 233, a button image 234, a chart image 235, and a button image 236. Chart image 231 is a graph showing the number of request information in which the member store is waiting for a response or notification from the issuer. According to the chart image 231, the number of attribute inquiries is 409, the number of personal use confirmation requests is 10, and the number of delivered communications is 1. The number of attribute inquiries is, for example, the number obtained by counting the number of request information whose status of the request information is "attribute inquiry request". The personal use confirmation request is, for example, a number obtained by counting the number of request information whose status of the request information is "personal use confirmation request". The delivered contact is, for example, a number obtained by counting the number of request information whose status of the request information is "delivered contact". Above the bar graph of the chart image 231 is the number of request information records counted for each status.

The button image 232 is associated with the chart image 231. When the button image 232 is clicked via the member store terminal 200, the request information management unit 164 receives a reference instruction for the report. The reference instruction of the report is an instruction to output the values of all the request information records related to the chart image associated with the button image to the member store terminal 200.

Chart image 233 is a graph showing the number of request information in which the issuer is waiting for a response or notification from a member store. According to the chart image 233, there are two attribute inquiry result responses and one delivery suspension request. The attribute inquiry result answer is, for example, the number obtained by counting the number of request information whose status of the request information is "attribute inquiry result answer". The delivery stop request is, for example, a number obtained by counting the number of request information whose status of the request information is "delivery stop request". Above the bar graph of the chart image 233, the number of request information records counted for each status is displayed. The button image 234 is associated with the chart image 233. When the button image 234 is clicked via the member store terminal 200, the request information management unit 164 receives a reference instruction for the report.

Chart image 235 is a graph counted for each status of the acquired request information record. According to the chart image 235, there are 410 attribute inquiry requests, 10 personal use confirmation requests, 2 attribute inquiry results, 1 delivery suspension request, and 1 delivered contact. The button image 236 is associated with the chart image 235. When the button image 236 is clicked via the member store terminal 200, the request information management unit 164 receives a reference instruction for the report.

Further, the request information management unit 164 may receive the reference instruction of the report and output the value of the request information record output to the member store terminal 200 to an external file. The external file may be, for example, an XLS file or a CSV file. The value of the request information record is written in the external h file.

FIG. 9 is a schematic block diagram showing an outline of the functional configuration of the member store terminal 200. The member store terminal 200 is configured by using an information processing device such as a personal computer, a smart device, or a tablet computer. The member store terminal 200 includes a communication unit 201, an input unit 202, an output unit 203, and a control unit 204.

The communication unit 201 is a communication device such as a network interface. The communication unit 201 is communicably connected to the network 400 using a predetermined protocol. The communication unit 201 communicates data with another device via the network 400 under the control of the control unit 204.

The input unit 202 is configured by using existing input devices such as a keyboard, a pointing device (mouse, tablet, etc.), buttons, and a touch panel. The input unit 202 is operated when inputting an instruction from the user of the member store to the member store terminal 200. The input unit 202 may be an interface for connecting the input device to the member store terminal 200. In this case, the input unit 202 inputs the input signal generated in response to the input of the user of the member store to the member store terminal 200 in the input device.

The output unit 203 outputs data to the user of the member store terminal 200 via an output device (not shown) connected to the member store terminal 200. The output device may be configured by using, for example, a device that outputs an image or characters to the screen. For example, the output device can be configured by using a CRT (Cathode Ray Tube), a liquid crystal display, an organic EL (Electro Luminescence) display, or the like. Further, the output device may be configured by using a device that prints (prints) an image or characters on a sheet. For example, the output device can be configured by using an inkjet printer, a laser printer, or the like. Further, the output device may be configured by using a device that converts characters into voice and outputs the characters. In this case, the output device can be configured by using a voice synthesizer and a voice output device (speaker). The output device may be configured by using a light emitting device such as an LED (Light Emitting Diode). The output unit 203 may transmit the determination result to another information processing device via the communication device provided in the member store terminal 200.

The control unit 204 is configured by using a processor such as a CPU and a memory. The control unit 204 functions as a communication control unit 241 when the processor executes a specific program.

The communication control unit 241 requests the request management device 100, for example, an authentication request, an identity verification request, or a chart information request by executing a predetermined communication program. First, the authentication request will be described. The communication control unit 241 transmits an authentication request to the request management device 100. Specifically, the communication control unit 241 receives the identification information and the password via the input unit 202. The communication control unit 241 transmits an authentication request in which the identification information and the password are associated with each other to the request management device 100.

Next, the identity verification request will be described. When the communication control unit 241 receives an authentication response indicating that the authentication is approved from the request management device 100, the communication control unit 241 sends an identity verification request to the request management device 100. Specifically, the communication control unit 241 uses the input unit 202 to provide information necessary for an identity verification request such as information representing the request content, issuer identification information, card information, approval number, authorization date and time, attribute information, and amount of money. Accepts input. The communication control unit 241 transmits the received information to the request management device 100 as an identity verification request. Next, when the communication control unit 241 receives the confirmation notification from the request management device 100, the communication control unit 241 accesses the request information record included in the confirmation notification to output the result of the identity confirmation request to the output unit 203. If the session with the request management device 100 has already been disconnected, the communication control unit 241 outputs the result of the identity verification request to the output unit 203 after making the authentication request.

Next, the chart information request will be described. When the communication control unit 241 receives an authentication response indicating that the authentication is approved from the request management device 100, the communication control unit 241 transmits a chart information request to the request management device 100. When the communication control unit 241 transmits the chart information request to the request management device 100, the communication control unit 241 receives the chart information from the request management device 100. When the communication control unit 241 receives the chart information, the communication control unit 241 outputs the chart information to the output unit 203. Further, when the communication control unit 241 clicks the button image included in the chart information via the input unit 202, the communication control unit 241 requests the values of all the request information records related to the chart image associated with the clicked button image. Get from 100. The communication control unit 241 outputs the acquired request information record to the output unit 203. The specific communication program of the communication control unit 241 may be, for example, a Web browser. The communication control unit 241 may be a dedicated application installed in advance.

FIG. 10 is a schematic block diagram showing an outline of the functional configuration of the issuer terminal 300. The issuer terminal 300 is configured by using an information processing device such as a personal computer, a smart device, or a tablet computer. The issuer terminal 300 includes a communication unit 301, an input unit 302, an output unit 303, and a control unit 304.

The communication unit 301 is a communication device such as a network interface. The communication unit 301 is communicably connected to the network 400 by a predetermined protocol. The communication unit 301 communicates data with another device via the network 400 under the control of the control unit 304.

The input unit 302 is configured by using an existing input device such as a keyboard, a pointing device (mouse, tablet, etc.), a button, and a touch panel. The input unit 302 is operated when inputting an instruction from the issuer user to the issuer terminal 300. The input unit 302 may be an interface for connecting the input device to the issuer terminal 300. In this case, the input unit 302 inputs the input signal generated in response to the input of the issuer user to the issuer terminal 300 in the input device.

The output unit 303 outputs data to the user of the issuer terminal 300 via an output device (not shown) connected to the issuer terminal 300. The output device may be configured by using, for example, a device that outputs an image or characters to the screen. For example, the output device can be configured by using a CRT, a liquid crystal display, an organic EL display, or the like. Further, the output device may be configured by using a device that prints (prints) an image or characters on a sheet. For example, the output device can be configured by using an inkjet printer, a laser printer, or the like. Further, the output device may be configured by using a device that converts characters into voice and outputs the characters. In this case, the output device can be configured by using a voice synthesizer and a voice output device (speaker). The output device may be configured by using a light emitting device such as an LED. The output unit 303 may transmit the determination result to another information processing device via the communication device provided in the issuer terminal 300.

The control unit 304 is configured by using a processor such as a CPU and a memory. The control unit 304 functions as a communication control unit 341 when the processor executes a specific program.

The communication control unit 341 requests the request management device 100, for example, an authentication request, a delivery status confirmation request, or a chart information request by executing a predetermined communication program. The authentication request and the chart information request are the same as the processes executed by the communication control unit 241, and thus the description thereof will be omitted.

Next, the delivery status confirmation request will be described. When the communication control unit 341 receives an authentication response indicating that the authentication is approved from the request management device 100, the communication control unit 341 sends a delivery status confirmation request to the request management device 100. Specifically, the communication control unit 341 delivers the information representing the request content, the member store identification information, the issuer identification information, the card information, the approval number, the authorization date and time, the attribute information, the amount of money, etc. via the input unit 302. Accepts the input of information required for confirmation request. The communication control unit 341 transmits the received information to the request management device 100 as a delivery status confirmation request. When the communication control unit 341 receives the confirmation notification from the request management device 100, the communication control unit 341 outputs the result of the identity verification request to the output unit 303 by accessing the request information record included in the confirmation notification. If the session with the request management device 100 has already been disconnected, the communication control unit 341 outputs the result of the identity verification request to the output unit 303 after making the authentication request.

FIG. 11 is a sequence chart showing a specific example of the processing flow when the identity verification request is executed in the operation of the request management system 1. First, the input unit 202 of the member store terminal 200 accepts the identification information and the password according to the operation by the user of the member store (step S101). The communication control unit 241 transmits an authentication request in which the identification information and the password are associated with each other to the request management device 100 (step S102).

The authentication unit 161 of the request management device 100 determines whether or not the identification information and the password included in the authentication request are valid information (step S103). Specifically, the authentication unit 161 has one of the authentication information records in which the identification information included in the authentication request and the password associated with the identification information are recorded in the authentication information table. If the identification information and the password match, it is determined that the identification information and the password included in the authentication request are valid information. The authentication unit 161 has the identification information and password of one of the authentication information records in which the identification information included in the authentication request and the password associated with the identification information are recorded in the authentication information table. If it does not match, it is determined that the identification information and password included in the authentication request are not valid information. The authentication unit 161 transmits an authentication response representing the determination result to the member store terminal 200 that has transmitted the authentication request (step S104). Specifically, when the authentication unit 161 determines that the identification information and the password included in the authentication request are valid information, the authentication unit 161 transmits an authentication response indicating that the authentication is approved. When the authentication unit 161 determines that the identification information and the password included in the authentication request are not valid information, the authentication unit 161 transmits an authentication response indicating that the authentication is not permitted.

When the communication control unit 241 receives the authentication response indicating that the authentication is approved from the request management device 100, the communication control unit 241 accepts the identity verification request via the input unit 202 (step S105). Specifically, the communication control unit 241 acquires from the request management device 100 an input form in which information necessary for transmitting the identity verification request to the request management device 100 can be input. The communication control unit 241 receives input of information representing the request content, issuer identification information, card information, approval number, authorization date and time, attribute information, amount of money, and other information necessary for the identity verification request via the input unit 202. The communication control unit 241 inputs the received information into the input form. The communication control unit 241 transmits the information input in the input form to the request management device 100 as an identity verification request (step S106).

Upon receiving the identity verification request from the member store terminal 200, the identity verification processing unit 162 of the request management device 100 acquires the member store identification information regarding the member store terminal 200 that sent the identity verification request (step S107). Specifically, the identity verification processing unit 162 has the identification information included in the authentication request transmitted by the member store terminal 200 connected in the same session as the member store terminal 200 that transmitted the authentication request in step S102. Obtain the store information record from the member store information table. The identity verification processing unit 162 acquires the member store identification information held by the acquired member store information record. Next, the identity verification processing unit 162 generates request information based on the information included in the received identity verification request and the acquired member store identification information. When the information representing the request content is "personal use confirmation", the identity verification processing unit 162 sets the value of the status of the request information to "personal use confirmation request". When the information representing the request content is "attribute inquiry", the identity verification processing unit 162 sets the status value of the request information as "attribute inquiry request". The identity verification processing unit 162 records the generated request information as a request information record in the request information table. When the request information record is recorded in the request information table, the identity verification processing unit 162 identifies the issuer to which the identity verification request is sent (step S108). Specifically, the identity verification processing unit 162 acquires the issuer identification information included in the request information. The identity verification processing unit 162 identifies the issuer by acquiring the issuer information record having the acquired issuer identification information from the issuer information table. The identity verification processing unit 162 acquires the contact information from the issuer information record. The identity verification processing unit 162 notifies the acquired contact of the identity verification request (step S109).

When the communication control unit 341 of the issuer terminal 300 receives the identity verification request, it outputs the request information record specified in the identity verification request to the output unit 303. The issuer user confirms his / her identity according to the status value of the request information record (step S110). Specifically, when the status value of the request information record is "personal use confirmation request", the issuer user contacts the cardholder. While contacting the cardholder, the status value of the request information record is changed from "Personal usage confirmation request" to "Personal usage confirmation hearing". Communication to the cardholder is based on the information registered in the issuer's database. Attribute information about the cardholder (eg, name, address, telephone number, date of birth, etc.) is recorded in the database held by the issuer. The attribute information regarding the cardholder is, for example, information collected at the time of examination of card issuance. The issuer user inputs the result of contacting the cardholder to the issuer terminal 300 via the input unit 302. For example, an issuer user may enter "matched" if the transaction was made by the cardholder, or "matched" if the transaction was not made by the cardholder. You may enter "I did not match you", or if you could not contact the cardholder, you could enter "I could not contact you". In addition, when the status value of the request information record is "attribute inquiry request", the issuer user matches the attribute information of the request information record with the attribute information registered in the database held by the issuer. It is judged whether or not it is. The issuer user inputs the result of determining whether or not the attribute information matches to the issuer terminal 300. For example, the issuer user may enter "matched" if the attribute information matches, or "did not match" if the attribute information does not match. You may. When the communication control unit 341 receives the result of the identity verification, the communication control unit 341 transmits the received content as the identity verification response to the request management device 100 (step S111).

When the identity verification processing unit 162 receives the identity verification response from the issuer terminal 300 that has received the identity verification request, it transmits a confirmation notice to the member store terminal 200 that made the identity verification request (step S112). First, when the identity verification processing unit 162 receives the identity verification response, it records the result of the identity verification in the value of the identity verification information in the request information record. Next, the identity verification processing unit 162 changes the status value of the request information record. The identity verification processing unit 162 changes, for example, the status value from "attribute inquiry request" to "attribute inquiry result answer". The identity verification processing unit 162 changes, for example, the status value from "identification confirmation hearing" to "personal use confirmation request result reply".

When the communication control unit 241 receives the confirmation notification from the request management device 100, the communication control unit 241 accesses the request information record based on the confirmation notification, and outputs the result of the identity verification request to the output unit 203 (step S113).

FIG. 12 is a sequence chart showing a specific example of the processing flow when delivery suspension is executed as the request content in the operation of the request management system 1. First, the input unit 302 of the issuer terminal 300 accepts the identification information and the password according to the operation by the issuer user (step S201). The communication control unit 341 transmits an authentication request in which the identification information and the password are associated with each other to the request management device 100 (step S202).

The authentication unit 161 of the request management device 100 determines whether or not the identification information and the password included in the authentication request are valid information (step S203). Since the determination process is the same as step S103, the description thereof will be omitted. The authentication unit 161 transmits an authentication response representing the determination result to the issuer terminal 300 that has transmitted the authentication request (step S204).

When the communication control unit 341 receives an authentication response indicating that the authentication is approved from the request management device 100, the communication control unit 341 receives a delivery status confirmation request via the input unit 302 (step S205). Specifically, the communication control unit 341 acquires from the request management device 100 an input form in which information necessary for transmitting the delivery status confirmation request to the request management device 100 can be input. The communication control unit 341 is required for a delivery status confirmation request such as information representing the request content, member store identification information, issuer identification information, card information, approval number, authorization date and time, attribute information, and amount of money via the input unit 302. Accepts information input. The communication control unit 341 inputs the received information into the input form. The communication control unit 341 transmits the information input in the input form to the request management device 100 as a delivery status confirmation request (step S206).

The delivery status confirmation processing unit 163 generates request information based on the information included in the received delivery status confirmation request. Since the information representing the request content is "delivery stop", the delivery status confirmation processing unit 163 sets the status value of the request information to "delivery stop request". The delivery status confirmation processing unit 163 records the generated request information as a request information record in the request information table. When the request information record is recorded in the request information table, the delivery status confirmation processing unit 163 acquires the member store identification information from the request information (step S207). The delivery status confirmation processing unit 163 identifies the member store to which the delivery status request is transmitted based on the acquired member store identification information (step S208). Specifically, the delivery status confirmation processing unit 163 acquires the member store information record having the member store identification information from the member store information table. The delivery status confirmation processing unit 163 acquires the contact information of the member store information record (step S208). The delivery status confirmation processing unit 163 notifies the acquired contact of the delivery status request (step S209).

When the communication control unit 241 of the member store terminal 200 receives the delivery status request, it outputs the value of the request information record specified in the delivery status request to the output unit 203. The user of the member store confirms the delivery status according to the status value of the request information record (step S210). Specifically, since the status value of the request information record is "delivery stop request", the user of the member store can set each value (for example, card information, approval number, authority date and time, amount, etc.) of the request information. Based on this, it is confirmed whether or not the item purchased using the card has been delivered. While the member store user confirms the delivery status, the status value of the request information record is changed from "delivery stop request" to "delivery status confirmation". The user of the member store inputs the result of confirming the delivery status to the member store terminal 200 via the input unit 202. For example, a merchant user may enter "delivered" if the item has already been delivered, or "undelivered" if the item has not yet been delivered. If you are not sure if the item has been delivered, you may enter "Unknown". In addition, the user of the member store stops the delivery of the product if the product has not been delivered yet. When the communication control unit 341 receives the result of confirming the delivery status, the communication control unit 341 transmits the received content as a delivery status response to the request management device 100 (step S211).

When the delivery status confirmation processing unit 163 receives the delivery status response from the member store terminal 200 that has received the delivery status request, the delivery status confirmation processing unit 163 transmits a confirmation notification to the issuer terminal 300 that has made the delivery status confirmation request (step S212). First, when the delivery status confirmation processing unit 163 receives the delivery status response, it records the result of confirming the delivery status in the value of the delivery status information in the request information record. Next, the delivery status confirmation processing unit 163 changes the status value of the request information record. The delivery status confirmation processing unit 163 changes, for example, the status value from "delivery status confirmation" to "delivery result reply".

When the communication control unit 341 receives the confirmation notification from the request management device 100, the communication control unit 341 accesses the request information record based on the confirmation notification, and outputs the result of the delivery status confirmation request to the output unit 303 (step S213).

13 and 14 are sequence charts showing specific examples of the processing flow when delivery hold is executed as the request content in the operation of the request management system 1. Since the processes in steps S301 to S308 are the same as the processes in steps S201 to S208 in FIG. 12, the description thereof will be omitted.

The delivery status confirmation processing unit 163 generates request information based on the information included in the received delivery status confirmation request. Since the information representing the request content is "delivery hold", the delivery status confirmation processing unit 163 sets the status value of the request information to "delivery hold request". The delivery status confirmation processing unit 163 records the generated request information as a request information record in the request information table. When the request information record is recorded in the request information table, the delivery status confirmation processing unit 163 acquires the member store information record having the member store identification information included in the request information from the member store information table. The delivery status confirmation processing unit 163 acquires the contact information of the member store information record. The delivery status confirmation processing unit 163 notifies the acquired contact of the delivery status request (step S309).

When the communication control unit 241 of the member store terminal 200 receives the delivery status request, it outputs the request information record specified in the delivery status request to the output unit 203. The user of the member store confirms the delivery status according to the status value of the request information record (step S310). Specifically, since the status value of the request information record is "delivery hold request", the user of the member store can set each value (for example, card information, approval number, authority date and time, amount, etc.) of the request information. Based on this, it is confirmed whether or not the item purchased using the card has been delivered. While the member store user confirms the delivery status, the status value of the request information record is changed from "delivery hold request" to "delivery status confirmation". The user of the member store inputs the result of confirming the delivery status to the member store terminal 200 via the input unit 202. For example, a merchant user may enter "delivered" if the item has already been delivered, or "undelivered" if the item has not yet been delivered. If you are not sure if the item has been delivered, you may enter "Unknown". In addition, the user of the member store suspends the delivery of the product if the product has not been delivered yet. When the communication control unit 341 receives the result of confirming the delivery status, the communication control unit 341 transmits the received content as a delivery status response to the request management device 100 (step S311).

When the delivery status confirmation processing unit 163 receives the delivery status response from the member store terminal 200 that has received the delivery status request, the delivery status confirmation processing unit 163 transmits a confirmation notification to the issuer terminal 300 that has made the delivery status confirmation request (step S312). First, when the delivery status confirmation processing unit 163 receives the delivery status response, it records the result of confirming the delivery status in the value of the delivery status information in the request information record. Next, the delivery status confirmation processing unit 163 changes the status value of the request information record. For example, when the value of the delivery status information is "delivered" or "unknown", the delivery status confirmation processing unit 163 changes the status value from "delivery status confirmation" to "delivery result reply". For example, when the value of the delivery status information is "undelivered", the delivery status confirmation processing unit 163 changes the status value from "delivery status confirmation" to "delivery pending". The delivery status confirmation processing unit 163 transmits a confirmation notice to the issuer terminal 300 that has made the delivery status confirmation request.

When the communication control unit 341 receives the confirmation notification from the request management device 100, the communication control unit 341 accesses the request information record based on the confirmation notification, and outputs the result of the delivery status confirmation request to the output unit 303 (step S313). Upon receiving the verification notice, the issuer user verifies the identity of the cardholder. Since the specific flow of identity verification is the same as in step S109, the description thereof will be omitted. The issuer user inputs the result of contacting the cardholder to the issuer terminal 300 via the input unit 302. For example, an issuer user may enter "matched" if the transaction was conducted by the cardholder, or "matched" if the transaction was not performed by the cardholder. You may enter "I did not match you", or if you could not contact the cardholder, you could enter "I could not contact you". When the communication control unit 341 receives the result of the identity verification, the communication control unit 341 transmits the received content as the identity verification result to the request management device 100 (step S314).

When the delivery status confirmation processing unit 163 receives the identity verification result, the delivery status confirmation processing unit 163 records the result of the identity verification in the value of the identity verification information in the request information record. A confirmation notice is transmitted to the member store terminal 200 that has responded to the delivery status (step S315). When the communication control unit 241 receives the confirmation notification from the request management device 100, the communication control unit 241 outputs the identity verification result to the output unit 203 based on the identification information for accessing the request information record included in the confirmation notification (step S316). .. The user of the member store confirms the delivery status based on the identity verification result (step S317). Specifically, when the status value of the request information record is "delivered", the user of the member store does not perform any particular processing. When the status value of the request information record is "Unknown", the member store user uses the card based on each value (for example, card information, approval number, authorization date and time, amount, etc.) of the request information. Check if the purchased item has been delivered. If the status value of the request information record is "Undelivered", the user of the member store releases the delivery suspension according to the content of the identity verification result. Specifically, when the content of the identity verification result is "matched with the person", the user of the member store releases the delivery hold and resumes the delivery of the product. The user of the member store stops the delivery when the content of the identity verification result is "does not match the identity". The user of the member store keeps the delivery hold if the content of the identity verification result is "cannot be contacted". The user of the member store inputs the result of confirming the delivery status to the member store terminal 200 via the input unit 202. When the result of confirming the delivery status is input, the communication control unit 241 transmits a confirmation response to the request management device 100 (step S318). When the delivery status confirmation processing unit 163 receives the delivery status response, the delivery status confirmation processing unit 163 transmits a confirmation notification to the issuer terminal 300 that has transmitted the identity verification result (step S319). When the communication control unit 341 receives the confirmation notification from the request management device 100, the communication control unit 341 accesses the request information record based on the confirmation notification and outputs the result of the delivery status confirmation request to the output unit 303 (step S320).

The request management system 1 configured in this way generates request information in response to the identity verification request or the delivery status request sent to the request management device 100. The request management device 100 notifies the member store terminal 200 or the issuer terminal 300 based on the information contained in the request information. Therefore, it is not necessary for a third party to mediate the transmission of information between the member store terminal 200 and the issuer terminal 300. Therefore, it is possible to respond 24 hours a day, 365 days a year, and it is possible to reduce the delay due to the reception not being accepted due to reasons such as outside business hours. In addition, by reducing the delay, the member store can shorten the delivery suspension period when the delivery is suspended. Further, the request information is input by the user of the member store or the user of the issuer via the input unit. Therefore, it is possible to suppress human error such as misunderstanding due to oral transmission of information such as by telephone. Only part of the card number is retained in the request information. Therefore, it is possible to prevent a security accident due to leakage of card information. Therefore, the request management system 1 enables smoother communication between the member store and the issuer.

Further, the request management device 100 records the request information as a request information record in the request information table. By recording the request information in the request information table, the request management device 100 can centrally manage the exchanges performed between the member store and the issuer. With this configuration, the member store or issuer can collectively manage the projects requested by the company and the projects requested by other companies. For this reason, it is possible to prevent the user of the member store or the user of the issuer from personalizing the work, and it is possible to carry out the work with a larger number of personnel. Further, the request management device 100 generates chart information classified according to the status of the request information based on the centrally managed request information. Merchant users or issuer users will be able to grasp the total amount of projects related to their company based on the generated chart information. In addition, since the chart information is classified and generated for each status, it is possible to grasp at a glance what kind of status the matter is accumulated. In addition, since the chart information is generated in separate charts for the projects requested by the company and the projects requested by other companies, the amount of work to be done by the company and the amount of work performed by other companies It becomes possible to make a business execution plan while weighing the above.

(Modification example)
In the request management system 1, the member store terminal 200 may be configured to make a delivered contact to the issuer terminal 300. The delivered notification is a process of notifying the issuer that the product has been delivered by the member store. For example, the member store terminal 200 may make a delivery notification while the issuer is performing identity verification or attribute inquiry in step S110 of FIG. The communication control unit 241 of the member store terminal 200 makes an authentication request to the request management device 100. When the authentication is approved, the communication control unit 241 transmits a delivered notification to the request management device 100 in response to the input from the input unit 202. When the identity verification processing unit 162 of the request management device 100 receives the delivered contact, the value of the status of the request information is set to "delivered contact". The identity verification processing unit 162 transmits the delivered notification to the issuer terminal 300. With such a configuration, the user of the issuer terminal 300 who has received the delivered notification can stop the identity verification or the attribute inquiry in the middle by knowing the delivery of the product. In addition, the member store terminal 200 may perform the delivery notification at a timing other than step S110 in FIG. For example, the member store terminal 200 may make a delivery notification at any timing as long as the issuer is responding.

In the above-described embodiment, the member store terminal 200 or the issuer terminal 300 is configured to transmit the request information to the request management device, but the proxy terminal 500 may be configured to transmit the request information. The proxy terminal 500 may function as a member store terminal 200 of a member store that does not use the request management device 100. For example, the proxy terminal 500 may send an identity verification request to the request management device 100 instead of the member store terminal 200. The proxy terminal 500 may function as an issuer terminal 300 of an issuer that does not use the request management device 100. For example, the proxy terminal 500 may send a delivery status confirmation request to the request management device 100 instead of the issuer terminal 300.

FIG. 15 is a schematic block diagram showing a system configuration of the request management system 1a. The request management system 1a is different from the first embodiment in that the proxy terminal 500 is further provided, but the other configurations are the same. Hereinafter, the points different from the first embodiment will be described.

FIG. 16 is a schematic block diagram showing an outline of the functional configuration of the proxy terminal 500. The proxy terminal 500 is configured by using an information processing device such as a personal computer, a smart device, or a tablet computer. The proxy terminal 500 includes a communication unit 501, an input unit 502, an output unit 503, and a control unit 504.

The communication unit 501 is a communication device such as a network interface. The communication unit 501 is communicably connected to the network 400 by a predetermined protocol. The communication unit 501 performs data communication with another device via the network 400 under the control of the control unit 504.

The input unit 502 is configured by using an existing input device such as a keyboard, a pointing device (mouse, tablet, etc.), a button, and a touch panel. The input unit 502 is operated when inputting an instruction from the user of the proxy terminal 500 to the proxy terminal 500. The input unit 502 may be an interface for connecting the input device to the proxy terminal 500. In this case, the input unit 502 inputs the input signal generated in response to the input of the user of the proxy terminal 500 to the proxy terminal 500 in the input device. The user of the proxy terminal 500 may be a person who provides the request management device 100 to the member store and the issuer. The user of the proxy terminal 500 may be a person who manages a member store.

The output unit 503 outputs data to the user of the proxy terminal 500 via an output device (not shown) connected to the proxy terminal 500. The output device may be configured by using, for example, a device that outputs an image or characters to the screen. For example, the output device can be configured by using a CRT, a liquid crystal display, an organic EL display, or the like. Further, the output device may be configured by using a device that prints (prints) an image or characters on a sheet. For example, the output device can be configured by using an inkjet printer, a laser printer, or the like. Further, the output device may be configured by using a device that converts characters into voice and outputs the characters. In this case, the output device can be configured by using a voice synthesizer and a voice output device. The output device may be configured by using a light emitting device such as an LED. The output unit 503 may transmit the determination result to another information processing device via the communication device provided in the proxy terminal 500.

The control unit 504 is configured by using a processor such as a CPU and a memory. The control unit 504 functions as a communication control unit 541 when the processor executes a specific program.

The communication control unit 541 requests the request management device 100, for example, an authentication request, an identity verification request, a delivery status confirmation request, or a chart information request by executing a predetermined communication program. When requesting the identity verification request from the request management device 100, the communication control unit 541 transmits the identity verification request including the member store identification information. The member store identification information may be, for example, member store identification information related to a member store that does not use the request management system 1a. With this configuration, the proxy terminal 500 can send the identity verification request to the request management device 100 as a member store. In this case, the contact information of the proxy terminal 500 is held as the contact information of the member store information record regarding the member store that does not use the request management system 1a. Further, the delivery status confirmation request transmitted by the communication control unit 541 includes predetermined issuer identification information. The predetermined issuer identification information may be, for example, issuer identification information regarding an issuer who does not use the request management system 1a. With this configuration, the proxy terminal 500 can send a delivery status confirmation request to the request management device 100 as an issuer. In this case, the contact information of the proxy terminal 500 is held as the contact information of the issuer information record regarding the issuer that does not use the request management system 1a. The detailed processing of the authentication request, the identity verification request, the delivery status confirmation request, and the chart information request is the same as the processing executed by the communication control unit 241 or the communication control unit 341, and thus the description thereof will be omitted.

In this way, the proxy terminal 500 can transmit the identity verification request to the request management device 100 as the member store terminal 200. Further, the proxy terminal 500 can send a delivery status confirmation request to the request management device 100 as the issuer terminal 300. Therefore, even if there is a member store or issuer who does not use the request management device 100, the proxy terminal 500 can send an identity verification request or a delivery status confirmation request on behalf of the member store or issuer. Therefore, even if some member stores or issuers have not introduced the request management system 1a, the users of the member stores and the users of the issuer can use the request management system 1a.

The request information does not necessarily have to be recorded in the request information record. Of the information contained in the request information, if it is information that is not used to identify the commercial transaction paid using the card (for example, attribute information), a storage unit or the like that stores all the transaction history (not shown). It may be recorded in another storage unit. In this case, the identity verification processing unit 162 or the delivery status confirmation processing unit 163 is configured to acquire from another storage unit.

The request information may be configured so that the re-examination destination is input. In this case, the communication control unit 241 accepts the input of the re-examination destination via the input unit 202 when receiving the information necessary for the identity verification request. The re-examination destination may be, for example, another employee of the member store. For the re-examination destination, for example, information regarding the contact information for the subject of the re-examination destination (for example, an e-mail address, a telephone number, a messenger ID, etc.) is input. When the identity verification processing unit 162 receives the identity verification request including the re-examination destination, the identity verification processing unit 162 also transmits the identity verification request to the re-identification destination. Further, the re-examination destination may be configured to be input by the communication control unit 341 of the issuer terminal 300.

The request information management unit 164 may be configured to generate a plurality of request information records by acquiring a predetermined file from the outside. Specifically, the request information management unit 164 acquires a predetermined file from the member store terminal 200 or the issuer terminal 300. The predetermined file is a file in which a plurality of information necessary for generating request information is recorded. The predetermined file may be, for example, a CSV file or an XLS file. The request information management unit 164 generates a plurality of request information according to the information recorded in the acquired file. The request information management unit 164 records the generated request information as a request information record in the request information table. With such a configuration, it becomes possible to suppress the labor required for the user of the member store or the user of the issuer to make a request.

In the above-described embodiment, the case of payment using a card has been described, but the payment does not necessarily have to be made by a card. For example, the payment may be made using any cashless medium such as a smartphone or NFC (Near Field Communication) that can be used for cashless payment. For example, payment may be made by reading identification information such as a QR (Quick Response) code (registered trademark) displayed on a smartphone by a reading device installed in a member store. For example, payment may be made by a communication device installed in a member store communicating with NFC.

The request management device 100 may be implemented by using a plurality of information processing devices that are communicably connected via a network. In this case, each functional unit included in the request management device 100 may be distributed and mounted in a plurality of information processing devices. For example, the authentication unit 161 and the request information management unit 164 may be mounted on different information processing devices.

Although the embodiments of the present invention have been described in detail with reference to the drawings, the specific configuration is not limited to this embodiment, and the design and the like within a range not deviating from the gist of the present invention are also included.

1 ... Request management system, 100 ... Request management device, 101 ... Communication unit, 102 ... Authentication information storage unit, 103 ... Merchant information storage unit, 104 ... Issuer information storage unit, 105 ... Request information storage unit, 106 ... Control unit , 161 ... Authentication unit, 162 ... Identity verification processing unit, 163 ... Delivery status confirmation processing unit, 164 ... Request information management department, 200 ... Merchant terminal, 201 ... Communication unit, 202 ... Input unit, 203 ... Output unit, 204 ... Control unit, 241 ... Communication control unit, 300 ... Issuer terminal, 301 ... Communication unit, 302 ... Input unit, 303 ... Output unit, 304 ... Control unit, 341 ... Communication control unit, 400 ... Network

Claims (5)

With the communication unit that communicates with other devices via the network,
An approval number indicating that payment is permitted using a cashless medium, an identification number of the cashless medium used for the payment, and information indicating the content of a request for payment using the cashless medium. A request information storage unit that stores request information associated with,
In response to the request information being registered in the request information storage unit by either the subject associated with the identification number of the cashless medium or the subject who can pay using the cashless medium. , The first notification process for notifying the other entity via the communication unit that the request information has been registered is executed, and the response to the request content included in the request information is associated with the request information. In response to being registered in the request information storage unit by the other entity, a second notification process is executed to notify the entity that registered the request information via the communication unit that the answer has been registered. Control unit and
Request management system equipped with. When the control unit receives a request for charting the request information from the subject associated with the identification number of the cashless medium or a subject who can pay using the cashless medium via the communication unit, the control unit receives a request. The request information stored in the request information storage unit is classified according to the request content and the answer to generate chart information, and the request is transmitted via the communication unit. Send the chart information to the subject,
The request management system according to claim 1. The cashless medium is a credit card.
The identification number of the cashless medium is the first 6 digits of the credit card number.
The request management system according to claim 1 or 2. A communication unit that communicates with other devices via a network, an approval number indicating that payment is permitted using a cashless medium, an identification number of the cashless medium used for the payment, and the above. It is a request management method performed by a request management device including a request information storage unit that stores information indicating request contents related to payment using a cashless medium and request information associated with the request information.
The request information is registered in the request information storage unit by the request management device by either a subject associated with the identification number of the cashless medium or a subject who can pay using the cashless medium. In response to the request, the first notification process for notifying the other entity that the request information has been registered is executed via the communication unit, and the request for the response to the request content included in the request information is requested. A second that notifies the subject who registered the request information via the communication unit in response to the fact that the answer has been registered in the request information storage unit by the other subject in association with the information. The control step that executes the notification processing of
Request management method with. A computer program for operating a computer as the request management system according to any one of claims 1 to 3.

Images