Operation system and operation method

Abstract

To provide an operation system that enables an issuer (a credit card issue company) to handle an activation operation after authentication (an operation to activate a credit card according to an authentication result obtained by authenticating whether a recipient who receives the credit card is a user) without increasing a burden on the issuer.SOLUTION: An operation system includes: a notification control unit that notifies a user of one of an authentication code or an authentication address by medium delivery for delivering a credit card, and notifies the user of the other by electronic notification; and an authentication unit that, at a site corresponding to the authentication address having an input request field for requesting input of the authentication code, determines whether or not input information entered into the input request field matches the authentication code notified to the user by the medium delivery or the electronic notification. If the input information matches the authentication code, the credit card is validated by the credit card issue company.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to an operation system and an operation method. [Background technology]

[0002] Issuers (credit card issuing companies) deliver credit cards to users in response to new applications and renewals (for example, Patent Document 1). When delivering a credit card to a user, the issuer may deliver the credit card by personal delivery mail, which requires identity verification, or by registered mail, etc., in order to prevent the credit card from being used fraudulently. In this case, there is a tendency for delivery costs to be incurred when delivering the credit card to the user.

[0003] On the other hand, some issuers operate by delivering unactivated (unusable) credit cards to users via relatively inexpensive regular mail, etc. These issuers operate a post-authentication activation process in which the credit card is activated depending on the authentication result of authenticating whether the recipient of the credit card is the user, and have built a system that enables such an operation. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Patent No. 5736475 Summary of the Invention [Problem to be solved by the invention]

[0005] However, issuers that do not support post-authentication activation operations will need to modify their core systems to enable such operations, but modifying core systems requires costs, manpower, and time, making it difficult to respond quickly.

[0006] For example, when upgrading a core system, a mid- to long-term upgrade plan is made in advance based on the priority of the items to be upgraded and the scale of the upgrade, etc. For this reason, it is difficult to interrupt the upgrade plan and make an upgrade to accommodate a different operation (activation operation after authentication). In addition, after the system has been modified, it is necessary to set aside a system freeze period (a period during which the system is not modified) to confirm whether the modified system operates stably. It is also necessary to set aside a period during which an investigation is conducted into the impact of the modified parts on the entire system. For this reason, the time required for modification becomes enormous. Furthermore, system department personnel need to have specialized knowledge about the systems their department handles, and they often outsource repair support work (such as coding work) that cannot be handled by in-house system engineers (SEs) alone to external system companies. However, because personnel are assigned to handle outsourced work based on a mid- to long-term recovery plan, there is no room to assign personnel to repairs that occur due to interruptions.

[0007] The present invention has been made in consideration of the above circumstances, and its purpose is to provide an operation system and operation method that enables an issuer (credit card issuing company) to handle post-authentication activation operation (operation in which a credit card is activated depending on the authentication result that authenticates whether the recipient who received the credit card is a user) without increasing the burden on the issuer. [Means for solving the problem]

[0008] In order to solve the above-mentioned problems, the operation system of the present invention is an operation system that performs operations in a credit card delivery business, delivering an unactivated credit card to a user and activating the credit card depending on the authentication result of authenticating whether the recipient of the credit card is the user, and is equipped with a notification control unit that notifies the user of either an authentication code or an authentication address by media delivery on which the credit card is delivered and notifies the user of the other by electronic notification, and an authentication unit, at a site corresponding to the authentication address having an input request field requesting input of the authentication code, that determines whether input information entered in the input request field matches the authentication code notified to the user by media delivery or electronic notification, and if the input information matches the authentication code, the credit card is activated at the credit card issuing company.

[0009] Furthermore, the operating method of the present invention is an operating method executed by a computer used in an operating system that performs operations in a credit card delivery business, in which an unactivated credit card is delivered to a user, and the credit card is activated depending on the authentication result of authenticating whether the recipient who received the credit card is the user, and the method notifies the user of either an authentication code or an authentication address by media delivery that delivers the credit card, and notifies the user of the other by electronic notification, and at a site corresponding to the authentication address having an input request field requesting input of the authentication code, it is determined whether input information entered in the input request field matches the authentication code notified to the user by media delivery or electronic notification, and if the input information matches the authentication code, the credit card is activated at the credit card issuing company. Effect of the Invention

[0010] According to the present invention, it is possible to enable an issuer (credit card issuing company) to handle post-authentication activation operations (operations in which a credit card is activated depending on the authentication results of authenticating whether the recipient who received the credit card is a user) without increasing the burden on the issuer. [Brief description of the drawings]

[0011] [Figure 1] 1 is a block diagram showing an example of the configuration of an operation system 1 according to an embodiment. [Diagram 2] 2 is a diagram showing an example of information stored in a member attribute information storage unit 201 according to the embodiment. FIG. [Diagram 3] A figure showing an example of information stored in a ticket issuance data storage unit 202 according to an embodiment. [Figure 4A] FIG. 2 is a diagram showing an example of a medium (envelope) to be delivered according to the embodiment. [Figure 4B] FIG. 2 is a diagram showing an example of a medium (card) to be delivered according to the embodiment. [Figure 4C] FIG. 2 is a diagram showing an example of a medium (card mount) to be delivered according to the embodiment. [Figure 5A] FIG. 11 is a diagram showing an example of a message transmitted to a user terminal 50 according to the embodiment. [Figure 5B] FIG. 11 is a diagram showing an example of a message transmitted to a user terminal 50 according to the embodiment. [Figure 6] 4 is a sequence diagram showing the flow of processing performed by the operation system 1 according to the embodiment. FIG. [Figure 7] 4 is a sequence diagram showing the flow of processing performed by the operation system 1 according to the embodiment. FIG. [Figure 8] 1 is a block diagram showing an example of the configuration of an operation system 1 according to a first modified example of an embodiment. [Figure 9] 11 is a sequence diagram showing a flow of processing performed by an operation system 1 according to a first modified example of the embodiment. FIG. [Figure 10] FIG. 11 is a block diagram showing an example of the configuration of an operation system 1 according to a second modified example of the embodiment. [Figure 11] FIG. 11 is a diagram showing an example of a medium (card mount) to be delivered according to a second modified example of the embodiment. [Figure 12] FIG. 11 is a diagram illustrating an example of a message transmitted to a user terminal 50 according to a second modification of the embodiment. [Figure 13] FIG. 11 is a sequence diagram showing a flow of processing performed by an operation system 1 according to a second modified example of the embodiment. [Figure 14] FIG. 11 is a block diagram showing a configuration example of an operation system 1 according to a third modified example of the embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] Hereinafter, an embodiment of the present invention will be described with reference to the drawings.

[0013] (Regarding Operational System 1) 1 is a block diagram showing an example of the configuration of an operation system 1 according to an embodiment. The operation system 1 includes, for example, an operation server 10, a credit card issuing company server 20, an issuance processing server 30, a telecommunications carrier server 40, and a user terminal 50.

[0014] The operation system 1 delivers an unactivated credit card to a user U, and activates the credit card depending on the authentication result that authenticates whether the recipient of the credit card is the user U. Here, the user U is an applicant who applies for a new credit card, an updater who updates his / her credit card when it expires, or a reissue requester who requests a reissue due to loss or other reasons.

[0015] The credit card issuing company server 20 is a server device managed by an issuer (a credit card issuing company). The issuer performs operations to issue a credit card in response to a new application from a user U or the expiration date of an issued credit card. The credit card issuing company server 20 is connected to the operation server 10 and the issuance processing server 30 so as to be able to communicate with each other.

[0016] The credit card issuing company server 20 includes, for example, a ticket issuing data generating unit 200, a member attribute information storage unit 201, a ticket issuing data storage unit 202, and a validation processing unit 203.

[0017] The ticket issuance data generation unit 200 generates information (ticket issuance data) used to issue a card. The ticket issuance data includes card information and member attribute information. The card information is information related to the card to be issued. The member attribute information is information indicating the attributes of a user U who uses the credit card corresponding to the card information. The member attribute information is stored, for example, in the member attribute information storage unit 201.

[0018] FIG. 2 is a diagram showing an example of member attribute information stored in member attribute information storage unit 201. As shown in FIG. 2, for example, member attribute information storage unit 201 stores name, telephone number, address, date of birth, and gender as attribute information of a credit card member. The member attribute information is personal information entered by user U on an application form when user U applies for a new credit card, for example. A credit card issuing company stores information about user U (name, address, date of birth, gender, telephone number, e-mail address, etc.) as member attribute information in member attribute information storage unit 201 by having user U register as a customer as a credit card member. For example, when applying for a new credit card, attribute information of user U can be registered and stored in member attribute information storage unit 201. If user U's name or address is changed thereafter, user U can be asked to carry out a procedure for changing the information, thereby updating the personal information of user U stored in member attribute information storage unit 201.

[0019] Fig. 3 is a diagram showing an example of information (ticket issuance data) stored in the ticket issuance data storage unit 202. As shown in Fig. 3, for example, the ticket issuance data storage unit 202 stores information corresponding to each of card information and member attribute information as ticket issuance data. The card information is information related to the card to be issued, and includes information indicating, for example, the card number, the card expiration date, and the security code. The member attribute information is information indicating the attributes of a user U who uses a credit card corresponding to the card information, and includes information extracted from the member attribute information storage unit 201 indicating the name, address, date of birth, gender, etc. of the user U.

[0020] The ticket issuance data generating unit 200 also generates a unique ID. The unique ID is identification information for identifying a credit card. The unique ID is information specific (unique) to each credit card, used to manage credit cards issued by an issuer. For example, the unique ID is determined according to an arbitrary format defined for each issuer. It is desirable that the unique ID be generated independently of card information (card number, card expiration date, security code, etc.). By generating the unique ID independently of card information, even if the unique ID is leaked, it becomes difficult to infer card information from the unique ID.

[0021] The credit card issuing company server 20 transmits the ticket issuance data and the unique ID generated by the ticket issuance data generation unit 200 to the issuance processing server 30. As a result, the credit card issuing company server 20 requests the production of a credit card according to the card information in the ticket issuance data and the delivery of the produced credit card.

[0022] 1, the validation processing unit 203 activates the credit card in accordance with the authentication result notified by the operation server 10. The specific contents of the authentication result notified by the operation server 10 will be described in detail later. If the validation processing unit 203 determines based on the authentication result that the recipient who received the credit card is user U, it validates the credit card. On the other hand, if the validation processing unit 203 determines based on the authentication result that the recipient who received the credit card is not user U, it does not validate the credit card and maintains the credit card in an unvalidated state.

[0023] As described above, in operation system 1, credit card issuing company server 20 determines whether or not to activate a credit card depending on the authentication result by operation server 10. Therefore, the issuer does not need to perform authentication itself, and it is sufficient to determine whether or not to activate a credit card based on the authentication result performed by operation server 10. Therefore, it is possible for the issuer (credit card issuing company) to handle activation operation after authentication without increasing the burden on the issuer.

[0024] The issuance processing server 30 is a server device managed by a business that manufactures credit cards and arranges for the delivery of the manufactured credit cards in response to a request from the credit card issuer server 20. The issuance processing server 30 includes, for example, a ticket issuing data acquisition unit (not shown), an authentication data generation unit 300, and a medium delivery handling unit 301. The ticket issuance data acquisition unit acquires the ticket issuance data notified from the credit card issuer server. The credit card issuer server 20 transmits the ticket issuance data and the unique ID to the issuance processing server 30. The ticket issuance data acquisition unit acquires the ticket issuance data via a communication unit (not shown) of the issuance processing server 30.

[0025] The authentication data generating unit 300 generates information (authentication data) to be used for authentication. The authentication data includes an authentication number and personal identification data. The authentication number is a number printed on the backing paper of a credit card delivered to the user U. The identity verification data is information used for identity verification to confirm whether the master (member attribute information) managed by the credit card issuing company server 20 matches the personal information of the user U, and information used when the operation server 10 issues an electronic notification. For example, identity verification is determining whether the contents of any of the items included in the member attribute information, such as name, address, date of birth, and gender, match the contents notified via the user terminal 50.

[0026] The authentication data generating unit 300 generates an authentication number. The authentication data generating unit 300 generates the authentication number, for example, by generating random numbers. The authentication number may include a character string, a number, and a symbol, or may be composed of only a character string, only a number, only a symbol, or a combination of at least two of a character string, a number, and a symbol. This authentication number is an example of an "authentication code." The authentication data generating unit 300 outputs the ticket issuance data and the authentication number to the medium delivery handling unit 301.

[0027] The authentication data generating unit 300 also generates identity verification data. The authentication data generating unit 300 generates identity verification data by extracting personal information used for identity verification from the member attribute information in the ticket issuance data. The authentication data generating unit 300 also generates information used when the operation server 10 issues an electronic notification from the member attribute information in the ticket issuance data. Which personal information among the member attribute information is used for identity verification may be determined in advance according to the issuer's intention, as long as it includes at least the authentication number. For example, only the name may be used for identity verification, or the name, date of birth, and address may be used for identity verification.

[0028] The issue processing server 30 transmits to the operation server 10 the authentication data including the authentication number and unique ID generated by the authentication data generating unit 300, and the personal identification data.

[0029] The medium delivery unit 301 produces a credit card according to the card information and arranges for the produced credit card to be delivered to the user U. The medium delivery unit 301 produces a credit card according to the card information, for example, by performing a write process to write card information onto an initial credit card on which no information has been written. When delivering a credit card, the medium delivery unit 301 arranges for an authentication number to be delivered together with the credit card. For example, the medium delivery unit 301 prints the authentication number on a mount used when delivering the credit card. The medium delivery unit 301 arranges for the delivery of a delivery item with the credit card affixed to the mount on which the authentication number is printed, thereby ensuring that the authentication number is delivered together with the credit card.

[0030] FIG. 4 (FIGS. 4A to 4C) is a diagram showing an example of a medium (delivery) to be delivered according to the embodiment. Fig. 4A shows an envelope B as a medium for medium delivery. Fig. 4B shows a credit card C as a medium for medium delivery. Fig. 4C shows a mount D as a medium for medium delivery. As shown in Fig. 4C, an authentication number D1 is printed on the mount D.

[0031] The medium delivery unit 301 generates a delivery item by instructing a worker or the like to attach a credit card C to a mount D on which an authentication number D1 is printed as shown in FIG. 4, insert the credit card C attached to the mount D into an envelope B, and seal the envelope B. The medium delivery unit 301 also arranges for the delivery of the delivery item. The address and name indicated in the member attribute information in the ticket issuance data can be used as the delivery destination. In this way, the medium delivery unit 301 delivers the credit card to the user U (medium delivery). The user U receives the delivery item including the credit card C and the mount D on which the authentication number D1 is printed. When the user U opens the delivery item (envelope) and peels the credit card C from the mount D, the authentication number printed on the mount D becomes visible. Note that the authentication number does not necessarily have to be printed on the mount D at the location where the credit card C is attached. It may be printed on the mount D at a position where the authentication number can be visible without peeling off the credit card C.

[0032] Returning to the explanation of FIG. 1, when the medium delivery section 301 of the issuance processing server 30 completes arrangements for delivery of the credit card, the issuance processing server 30 transmits information indicating this (delivery information) to the operation server 10.

[0033] The communication carrier server 40 is a server device managed by a communication carrier. The communication carrier is, for example, an MNO (Mobile Network Operator) that provides a communication service using a telephone number to the user terminal 50 using a communication line owned or operated by the carrier. The communication service using a telephone number here includes a messaging service that sends a message to a telephone number as a destination, such as RCS (Rich Communication Services) and SMS (Short Message Service). This messaging service that sends a message to a telephone number as a destination is an example of an "electronic notification."

[0034] The user terminal 50 is, for example, any one of terminal devices such as a smartphone, a tablet terminal, a personal computer, etc. The user U makes a contract with the telecommunications carrier of the telecommunications carrier server 40 for using a communication service using the user terminal 50. The user terminal 50 is capable of communicating using a communication service provided by the contracted telecommunications carrier. The user terminal 50 is assigned a telephone number and has a function of communicating with this telephone number as a destination. The user terminal 50 has a display unit such as a liquid crystal display for displaying information, and an operation unit such as a touch panel for accepting operations by a user. The user terminal 50 transmits and receives messages using RCS and SMS via the communication carrier server 40.

[0035] The operational server 10 is a server device that mediates between an issuer and a user U and performs authentication on behalf of the issuer. The operational server 10 includes, for example, an authentication data acquisition unit 100, an authentication URL issuing unit 101, an electronic notification control unit 102, and an authentication unit 103.

[0036] The authentication data acquisition unit 100 acquires the authentication data notified from the issue processing server 30. The authentication data acquisition unit 100 outputs the acquired authentication data to the electronic notification control unit 102 and the authentication unit 103. The authentication URL issuing unit 101 issues an authentication URL. The authentication URL is a URL (Uniform Resource Locator) that indicates the address of the site where authentication is performed. Here, the authentication URL issuing unit 101 may issue, for example, a so-called one-time URL that can be accessed only once, within a limited period of time, or a limited number of times as the authentication URL. The authentication URL may be information that indicates at least a site that represents authentication, and may be a URI (Uniform Resource Identifier). The authentication URL is an example of an "authentication address". The authentication URL issuing unit 101 outputs information indicating the issued authentication URL to the electronic notification control unit 102 and the authentication unit 103 .

[0037] The electronic notification control unit 102 generates a message including the authentication URL issued by the authentication URL issuing unit 101. This message needs to include at least the authentication URL, but may also include text showing a sentence for prompting authentication, still images and moving images including figures such as illustrations and photographs, and sound. The electronic notification control unit 102 generates a message including an authentication URL, and generates a request to send a message including the generated message and destination information specifying the telephone number of user U as the destination of the message. The electronic notification control unit 102 can obtain the telephone number of user U from the authentication data notified by the issue processing server 30. The operation server 10 transmits the transmission request generated by the electronic notification control unit 102 to the telecommunications carrier server 40. This enables the operation server 10 to transmit a message to the user terminal 50 via the telecommunications carrier server 40.

[0038] The authentication unit 103 performs authentication. As authentication, the authentication unit 103 performs, for example, a match check of authentication numbers and identity check. The match check of authentication numbers is to determine whether the authentication number notified to the operation server 10 from the issue processing server 30 matches the number notified from the user terminal 50. Note that as authentication, only a match check of authentication numbers may be performed and identity check may be omitted.

[0039] As a preparation for authentication, the authentication unit 103 acquires the authentication data notified to the operation server 10 by the issue processing server 30 via the authentication data acquisition unit 100. The authentication unit 103 also acquires the authentication URL issued by the authentication URL issuer 101. In preparation for verifying whether the authentication numbers match, the authentication unit 103 extracts the authentication number from the authentication data and stores it in a storage unit (not shown). In preparation for verifying the identity of the user, the authentication unit 103 extracts identity verification data from the authentication data and stores it in the storage unit.

[0040] The authentication unit 103 performs a match check of the authentication number for a terminal device that has accessed a site indicated by an authentication URL. For example, the authentication unit 103 transmits information for displaying a request screen to the terminal device. This request screen has an input request field for requesting input of an authentication number. By receiving this information (information for displaying the request screen), the terminal device displays the request screen and accepts input into the input request field. When input is made into the input request field, the terminal device transmits the input information (input information) to the operation server 10. The operation server 10 receives the input information from the user terminal 50. The authentication unit 103 determines whether the input information matches an authentication number stored in advance. As a result, the authentication unit 103 performs a match check of the authentication number.

[0041] If the input information matches the authentication number as a result of the authentication number match check, the authentication unit 103 performs identity verification. The authentication unit 103 causes the terminal device to display an identity verification screen by transmitting information for displaying the identity verification screen. When personal information is input, the terminal device transmits the input personal information to the operation server 10. The operation server 10 receives the personal information from the user terminal 50. The authentication unit 103 performs identity verification by determining whether the contents of the personal information transmitted from the terminal device match the contents of the identity verification data.

[0042] On the other hand, if the input information does not match the authentication number as a result of checking the matching of the authentication numbers, the operation server 10 may output a response signal indicating that the authentication numbers do not match to the terminal device. For example, when the terminal device receives this response signal, it displays a character string such as "The authentication numbers did not match. Please re-enter the authentication number" on the display screen. Note that if the number of times the authentication number does not match even after being re-entered reaches a certain number, acceptance of the authentication number may be stopped (locked).

[0043] If the operation server 10 confirms that the input information matches the authentication number, it performs identity verification and notifies the credit card issuer server 20 of the unique ID of the credit card associated with the matching authentication number and the identity verification result as the authentication result.

[0044] When the credit card issuing company server 20 receives the authentication result from the operation server 10, it validates the credit card according to the authentication result. The credit card issuing company server 20 validates the credit card corresponding to the unique ID included in the authentication result. In other words, when the input information matches the authentication number, the credit card is validated by the issuer. When the credit card issuing company server 20 validates the credit card, it notifies the operation server 10 of this fact together with the unique ID corresponding to the validated credit card.

[0045] When the operation server 10 receives notification from the credit card issuing company server 20 that the credit card has been activated, it sends a message to the user terminal 50 of the user U via the telecommunications carrier server 40 that the credit card has been activated.

[0046] For example, the electronic notification control unit 102 generates a message to the effect that the credit card has been activated. The electronic notification control unit 102 generates a message transmission request including the generated message and destination information specifying the telephone number of the user U as the destination of this message. The operation server 10 transmits the transmission request generated by the electronic notification control unit 102 to the telecommunications carrier server 40. This enables the operation server 10 to transmit the message to the user terminal 50 via the telecommunications carrier server 40. The user terminal 50 displays the message received via the telecommunications carrier server 40 on a display screen. By visually checking this display screen, the user U can recognize that the credit card has been activated.

[0047] The storage unit (not shown) of the operation server 10 is configured by a storage medium, for example, a hard disk drive (HDD), a flash memory, an electrically erasable programmable read only memory (EEPROM), a random access read / write memory (RAM), a read only memory (ROM), or any combination of these storage media. For example, a non-volatile memory can be used for this storage unit. This storage unit stores programs for realizing the functions of the operation server 10 (including an authentication data acquisition unit 100, an authentication URL issuing unit 101, an electronic notification control unit 102, an authentication unit 103, and, if an authentication URL output unit 104 described later is included, a function corresponding to the authentication URL output unit 104). The functions of the operation server 10 are realized by a processor such as a CPU (Central Processing Unit) of the operation server 10 executing a program stored in this storage unit. At least some of the functions of the operation server 10 may be executed by an electric circuit. Also, at least some of the functions of the operation server 10 may be realized by executing a program acquired via a network.

[0048] FIG. 5 (FIGS. 5A and 5B) are diagrams showing examples of messages transmitted to the user terminal 50 according to the embodiment. 5A shows an example of an image displayed on the display screen when a message including an authentication URL is sent to the user terminal 50. The message including the authentication URL shows, for example, the authentication URL (M3) together with a message (M1) prompting authentication and a message (M2) informing the user of the authentication method. When the user U taps on the authentication URL, the user terminal 50 transitions to the site indicated by the authentication URL.

[0049] 5B shows an example of an image (an image of the site indicated by the authentication URL) displayed on the display screen when a tap operation is performed on the authentication URL. The site indicated by the authentication URL shows text guiding the site, a display field (reference symbol H) displaying the user's name, an input request field (reference symbol N) for inputting an authentication number, and an operation button (reference symbol BT). The user terminal 50 transmits input information to the operation server 10 when a user U performs an input operation on the input request field and taps the operation button.

[0050] 6 and 7 are sequence diagrams showing the flow of processing performed by the operation system 1 according to the embodiment.

[0051] The sequence in FIG. 6 shows a process flow when a user U applies for use of a credit card. 6, when applying for a new card or updating a card, the user terminal 50 transmits information required for the application to use a credit card to the credit card issuing company server 20 (step S10). The information required for the application to use a credit card includes information related to the user U, such as the address, name, age, telephone number, and occupation of the user U, as well as information related to the card, such as the type of credit card to be used and the account number linked to the credit card.

[0052] The credit card issuing company server 20 receives the transmission data (information necessary for applying to use a credit card) sent from the user terminal 50, and performs processing to generate ticket issuance data (step S11). The ticket issuance data generation unit 200 of the credit card issuing company server 20 stores the information related to user U contained in the transmission data in the member attribute information storage unit 201 as member attribute information. The ticket issuance data generation unit 200 generates card information corresponding to the credit card to be issued based on the card-related information contained in the transmission data. The ticket issuance data generation unit 200 generates data including the member attribute information and card information of user U as ticket issuance data. The ticket issuing data generating unit 200 of the credit card issuing company server 20 generates a unique ID (step S12). When the credit card issuing company server 20 generates the ticket issuance data and the unique ID by the ticket issuance data generation unit 200, it transmits them to the issuance processing server 30 (step S13).

[0053] The issuance processing server 30 receives the ticket issuance data and the unique ID sent from the credit card issuer server 20, and generates identity verification data (step S14). The authentication data generating unit 300 of the issuance processing server 30 extracts personal information used for identity verification from the member attribute information of the ticket issuance data, thereby generating identity verification data. The authentication data generating unit 300 generates an authentication number (step S15). The issuance processing server 30 transmits the personal identification data, the authentication number, and the unique ID generated by the authentication data generating unit 300 to the operation server 10 as authentication data (step S16). The operation server 10 receives the authentication data transmitted from the issue processing server 30, and issues an authentication URL by the authentication URL issuer 101 (step S17).

[0054] The issuing processing server 30 performs processing to manufacture a credit card (step S18). The medium delivery handling unit 301 of the authentication data generating unit 300 manufactures a credit card according to the card information. The medium delivery handling unit 301 makes arrangements for delivery of the manufactured card (step S19). The medium delivery handling unit 301 generates a delivery item with a credit card affixed to a mount on which an authentication number is printed, and makes arrangements for delivery of the generated delivery item to user U. User U receives the delivery item including the credit card and authentication number (step S20). When the issuance processing server 30 makes arrangements for delivery of the delivery item to user U, it transmits information indicating that (delivery information) to the operation server 10 (step S21).

[0055] When the operations server 10 receives the delivery information sent from the issuance processing server 30, it generates a message notifying the user U of the authentication URL and requests delivery of the message by sending the telephone number to the telecommunications carrier server 40 as the destination (step S22). When the communication carrier server 40 receives the delivery request transmitted from the operation server 10, it transmits a message to the user terminal 50 (step S23). The user terminal 50 receives the message notified from the operation server 10 (the message including the authentication URL) via the communication carrier server 40 (step S24).

[0056] The sequence in Fig. 7 shows the flow of processing performed by the operation system 1 after the sequence shown in Fig. 6. That is, it is assumed that the user U has received the delivery (including the authentication number) and the user terminal 50 has received the message (including the authentication URL). As shown in FIG. 7, when the user U taps on the authentication URL, the user terminal 50 accesses the site indicated by the authentication URL (step S30). The operational server 10 requests an authentication number from the terminal device (here, the user terminal 50) that has accessed the site indicated by the authentication URL (step S31). The authentication unit 103 of the operational server 10 transmits information for displaying a request screen to the user terminal 50. The request screen has an input request field for requesting input of the authentication number. By receiving this information, the user terminal 50 displays the request screen and accepts input into the input request field. The user terminal 50 transmits the input information input by the user U as the authentication number to the operation server 10 (step S32).

[0057] When the authentication unit 103 of the operation server 10 receives the input information transmitted by the user terminal 50, it compares the authentication number with the input information (step S33) and determines whether the authentication number and the input information match. If the authentication number matches the input information, the authentication unit 103 performs identity verification (step S34). The authentication unit 103 displays a screen for identity verification on the user terminal 50, and transmits the personal information input on that screen. Here, the screen for identity verification may be the same screen as the screen on which the authentication number is input. The operation server 10 receives the personal information from the user terminal 50. The authentication unit 103 determines whether the contents of the personal information input from the terminal device match the contents of the identity verification data (step S35). When identity verification is completed by the authentication unit 103 and the contents of the personal information input from the terminal device match the contents of the identity verification data, the operation server 10 transmits the verification result and the authenticated unique ID to the credit card issuing company server 20 (step S36). The authenticated unique ID is the unique ID of the credit card corresponding to the authentication number whose input information matches the authentication number in the authentication number match verification. If the personal information entered from the terminal device in step S35 does not match the identity verification data, the operation server 10 ends the process.

[0058] The credit card issuing company server 20 receives the authenticated unique ID sent from the operation server 10 and validates the credit card corresponding to the received unique ID (step S37). In response to the authenticated unique ID received from the operation server 10, the credit card issuing company server 20 transmits information about the validated credit card (e.g., the unique ID) to the operation server 10 (step S38).

[0059] When the operation server 10 receives the response (information about the activated credit card) sent from the credit card issuing company server 20, it generates a message notifying that the credit card has been activated and requests delivery of the message by sending the telephone number to the telecommunications carrier server 40 as the destination (step S39). When the communication carrier server 40 receives the delivery request sent from the operation server 10, it transmits a message to the user terminal 50 (step S40). The user terminal 50 receives the message notified from the operation server 10 via the communication carrier server 40. The user terminal 50 displays the received message. By visually checking the message displayed on the user terminal 50, the user U knows that the credit card has been validated, and starts using the credit card (step S41).

[0060] On the other hand, if the authentication number does not match the input information in step S34, the operation server 10 ends the process. Alternatively, if the authentication number does not match the input information in step S34, the operation server 10 may transmit a message to the user terminal 50 notifying that the authentication numbers do not match. In this case, the operation server 10 generates a message notifying that the authentication numbers do not match, and requests delivery of the message by transmitting the message to the telecommunications carrier server 40 with the telephone number as the destination. When the telecommunications carrier server 40 receives the delivery request transmitted from the operation server 10, it transmits the message to the user terminal 50. The user terminal 50 receives the message transmitted from the operation server 10 via the telecommunications carrier server 40.

[0061] As described above, the operation system 1 of the embodiment is an operation system that delivers an unactivated credit card to a user in a credit card delivery business, and activates the credit card depending on the authentication result of authenticating whether the recipient of the delivered credit card is the user. The operation system 1 includes a medium delivery response unit 301 (an example of a notification control unit), an electronic notification control unit 102 (an example of a notification control unit), and an authentication unit 103. The medium delivery response unit 301 notifies the user of an authentication number, which is either an authentication number (an example of an authentication code) or an authentication URL (an authentication address), by a medium delivery that delivers the credit card. The electronic notification control unit 102 notifies the user of the authentication URL, which is the other of the authentication number (an example of an authentication code) and the authentication URL (an authentication address), by an electronic notification. The site corresponding to the authentication URL has an input request field that requests input of the authentication number. The authentication unit 103 determines whether the input information input in the input request field at the site corresponding to the authentication URL matches the authentication number notified to the user by the medium delivery or electronic notification. If the input information matches the authentication number, the credit card is validated by the credit card issuing company. As a result, in the operation system 1 of the embodiment, the credit card can be activated according to the result of judging whether the input information and the authentication number match in the operation system 1. Therefore, it is possible for the issuer (credit card issuing company) to be able to handle activation operations after authentication, such as activating a credit card according to the authentication result of authenticating whether the recipient who received the credit card is the user, without increasing the burden on the issuer.

[0062] (First Modification of the Embodiment) Here, a first modified example of the embodiment will be described. This modified example differs from the above-described embodiment in that public personal authentication is used for identity verification. Public personal authentication is an authentication method for verifying identity using a personal card, which is a public certificate. Public personal authentication is an authentication method that uses JPKI (Public Personal Authentication Service). This public personal authentication uses a personal card. The personal card is, for example, an IC (integrated circuit card) card that can store personal information. More specifically, the personal card is a My Number card. In the following, the same components as those in the above-described embodiment are denoted by the same reference numerals and their description will be omitted, and the following mainly describes the components that differ from those in the above-described embodiment.

[0063] 8 is a block diagram showing a configuration example of an operation system 1 according to a first modified example of the embodiment. The operation system 1 of this modified example includes a signature verification server 60. The signature verification server is, for example, a server device that provides a public personal authentication service operated by J-LIS (Japan Agency for Local Government Information Systems). The signature verification server 60 is communicatively connected to the operation server 10, and performs personal authentication of a user U by communicating with a user terminal 50 via the operation server 10.

[0064] When official personal authentication is performed, the user is asked to input a password for using an electronic signature and the My Number card is read by the user terminal 50, whereby official personal authentication processing is performed in the signature verification server 60, and if validity is confirmed, four basic pieces of information, such as the user's name, address, date of birth, and gender, can be obtained. Also, the serial number of the electronic certificate used in the My Number card or its alternative information may be used to confirm its validity for identity verification.

[0065] Fig. 9 is a sequence diagram showing the flow of processing performed by the operation system 1 according to the first modified example of the embodiment. The processing shown in steps S130 to S134 and S141 to S145 in Fig. 9 is similar to steps S30 to S34 and S37 to S41 in Fig. 7, and therefore the description thereof will be omitted. Also, the sequence in Fig. 9, like Fig. 7, shows the flow of processing performed by the operation system 1 after the sequence shown in Fig. 6. That is, it is assumed that the user U has received a delivery (including an authentication number), and the user terminal 50 has received a message (including an authentication URL).

[0066] If the authentication number and the input information match in step S134, the authentication unit 103 notifies the user terminal 50 of a request to perform public personal authentication (step S135). The authentication unit 103 transmits information for executing public personal authentication application software (hereinafter, public personal authentication app) to the user terminal 50. Upon receiving this information (information for executing the public personal authentication app), the user terminal 50 starts the public personal authentication app and displays a screen for performing public personal authentication. Here, a character string is displayed that prompts the user to enter a password and read the personal card, such as "Please enter your password and allow the terminal to read your personal card."

[0067] When the user U inputs a password and brings the personal card close to the card reader of the user terminal 50, the user terminal 50 accepts the input of the password and transmits the password to the personal card. If the input password matches the password stored in the personal card, the personal card outputs the electronic certificate stored in the personal card to the user terminal 50. The user terminal 50 receives the electronic certificate output from the personal card.

[0068] Although the case where the user terminal 50 executes a public personal authentication application when performing public personal authentication processing has been described above, the public personal authentication processing may be performed by accessing a site that provides a public personal authentication service through a browser, instead of executing application software, and entering a password, reading a personal card, etc. Also, application software other than the public personal authentication application may be executed to accept password input and determine whether the password matches, and the determination result may be returned to the public personal authentication application.

[0069] Also, although the case where the user terminal 50 communicates with the personal card and obtains the electronic certificate has been described here, the information stored in the personal card may be stored in a memory provided in the user terminal 50, and this memory may be accessed instead of reading the personal card. For example, when a password is input by the user U, the user terminal 50 may refer to its internal memory, and if the password matches, the electronic certificate may be read from the memory.

[0070] When the user terminal 50 receives the electronic certificate from the personal card because the input password matches the password stored in the personal card, the user terminal 50 transmits the received electronic certificate to the operation server 10 (step S136). Here, the user terminal 50 not only transmits the electronic certificate, but also transmits, together with the electronic certificate, association information (linking key) that can identify which user's electronic certificate this electronic certificate belongs to. The linking key may be, for example, a telephone number assigned to the user terminal 50, an account ID assigned in a public personal authentication application, or token information (such as a one-time password). However, as long as it is possible to identify which user terminal 50 is the sender of the electronic certificate, it is not necessary to transmit the linking key.

[0071] When the operation server 10 receives the electronic certificate and the linked key from the user terminal 50, it transmits (relays) the electronic certificate and the linked key to the signature verification server 60 (step S137). Here, a case has been described in which the electronic certificate and the linked key are transmitted from the user terminal 50 to the operation server 10, and then the operation server 10 transmits them to the signature verification server 60, but it is also possible for the user terminal 50 to transmit the electronic certificate and the linked key to the signature verification server 60 without relaying by the operation server 10. When relaying by the operation server 10 is not performed, the user terminal 50 transmits to the signature verification server 60, together with the electronic certificate and the linked key, information indicating that the notification destination of the authentication result is the operation server 10.

[0072] When the signature verification server 60 receives the electronic certificate and the linking key from the operational server 10, it performs authentication processing based on whether or not the electronic certificate is valid (step S138). If the signature verification server 60 determines that the electronic certificate is valid (step S139-OK), it reads out personal information corresponding to the electronic certificate from the storage unit, and transmits the personal information and the linking key to the operational server 10. Here, a case will be described in which the signature verification server 60 transmits the confirmation result and the basic four information to the operational server 10, but the operational server 10 may also request the signature verification server 60 to obtain the basic four information. The personal information transmitted here includes, for example, the user U's name, address, date of birth, and gender (basic four pieces of information).

[0073] When the operational server 10 receives personal information (basic four pieces of information) and a linking key as a result of public personal authentication from the signature verification server 60 in response to determining that the electronic certificate is valid, the operational server 10 compares whether there is a correspondence between the identity verification data and the received personal information.

[0074] Furthermore, if the personal card is a My Number card, the information (four basic pieces of information: address, name, date of birth, and gender) obtained from the signature verification server 60 is the latest information. In other words, even if the address is changed due to moving, etc., the new address after the move is registered in the signature verification server 60 by the user U completing the moving procedure (moving out notification, moving in notification, etc.) with the local government. Therefore, the operational server 10 can obtain the latest address. Furthermore, if the name of the user U is changed, the user U completes the name change procedure with the local government, and the changed name is registered in the signature verification server 60. Therefore, the operational server 10 can obtain the latest name.

[0075] The operation server 10 collates the identity verification data with the personal information and judges whether the verification condition is satisfied. Here, the verification condition may be, for example, that the contents of any of the predetermined items, such as name, address, date of birth, and sex, included in the verification information match the contents of the predetermined items included in the personal information. For example, the four items may match, or some of the items may match. The some of the items may be, for example, the date of birth and the name. This is because the address stored in the member attribute information storage unit 201 may not match the address stored in the signature verification server 60 due to a move or the like. In addition, the name may be the entire name as a condition, or the surname may be changed, so the condition may be whether a part of the name (for example, the first name) matches.

[0076] When operation server 10 has completed matching the identity verification data with the personal information using public personal authentication, it transmits the matching result and the authenticated unique ID to credit card issuing company server 20 (step S140).

[0077] On the other hand, if the operation server 10 determines in step S139 that the electronic certificate is invalid, it transmits a response signal to that effect to the operation server 10. The operation server 10 may generate a message indicating that the electronic certificate is invalid, and transmit the generated message to the user terminal 50 via the telecommunications carrier server 40. The message generated here may include content indicating that the electronic certificate is invalid, or may include content indicating that the electronic certificate is invalid and urging the user to be authenticated again.

[0078] As described above, in the operation system 1 according to the first modified embodiment, when the input information and the authentication number match, the authentication unit 103 performs public personal authentication using a personal card, which is a public certificate. In this way, in the operation system 1 according to the first modified embodiment, identity verification based on the public certificate can be performed. The personal information input by the user U's operation input may include incorrect notation due to an erroneous operation, etc., and in such a case, it is determined that the input information and the notation of the authentication number do not match in identity verification. In contrast, by performing identity verification based on the public certificate, accurate verification without the possibility of incorrect notation can be performed. Furthermore, when there is a change in the address, name, etc. of the user U, in a situation where the member attribute information in the master (member attribute information storage unit 201) managed by the credit card issuing company server 20 has not been updated, it is possible to know that the address, name, etc. of the user U have been changed, and therefore it is also possible to prompt the user U to carry out the change procedure.

[0079] (Modification 2 of the embodiment) Here, a second modification of the embodiment will be described. This modification differs from the above-described embodiment in that the authentication URL is notified (delivered) to the user U by medium delivery, and the authentication number is notified to the user terminal 50 by electronic notification. In the following, the same components as those in the above-described embodiment are denoted by the same reference numerals and their description will be omitted, and the following mainly describes the components that differ from those in the above-described embodiment.

[0080] 10 is a block diagram showing a configuration example of an operation system 1 according to Modification 1 of the embodiment. The operation system 1 of this modification includes an authentication URL acquisition unit 302 in the issue processing server 30, and an authentication URL output unit 104 in the operation server 10. The authentication URL output unit 104 transmits the authentication URL issued by the authentication URL issue unit 101 to the issue processing server 30. The issue processing server 30 receives the authentication URL transmitted from the operation server 10, and outputs the received authentication URL to the authentication URL acquisition unit 302.

[0081] The authentication URL acquisition unit 302 acquires the authentication URL, and outputs the acquired authentication URL to the medium delivery unit 301. The medium delivery unit 301 generates a delivery item with a credit card attached to a mount on which the authentication URL is printed, and makes arrangements to deliver the generated delivery item to the user U.

[0082] Fig. 11 is a diagram showing an example of a medium (backing sheet) to be delivered according to the second modified example of the embodiment. As shown in Fig. 11, a two-dimensional code D2 with an authentication URL embedded therein is printed on a backing sheet D. A user U performs an operation to read the authentication URL from the two-dimensional code, and the user terminal 50 accesses the site indicated by the authentication URL.

[0083] Alternatively, the medium delivery handling unit 301 may write the authentication URL in a storage medium of an integrated circuit included in the credit card. In this case, for example, if the credit card is compatible with NFC (Near Field Communication), data (authentication URL) is written in NDEF (NFC Data Exchange Format) format. This allows the user U to read the authentication URL via a dedicated application program (NDEF application) in the user terminal 50 equipped with an NFC reader. The user U performs an operation to read the authentication URL via the NDEF application, and the user terminal 50 accesses the site indicated by the authentication URL.

[0084] In this modification, the electronic notification control unit 102 of the operation server 10 generates a message including an authentication number. The electronic notification control unit 102 acquires the authentication data notified from the issuance processing server 30 via the authentication data acquisition unit 100, and acquires the authentication number from the acquired authentication data. The electronic notification control unit 102 generates a message including the authentication number, and generates a request to send a message including the generated message and destination information specifying the telephone number of the user U as the destination of this message. The operation server 10 transmits the transmission request generated by the electronic notification control unit 102 to the telecommunications carrier server 40. This enables the operation server 10 to transmit a message (a message including an authentication number) to the user terminal 50 via the telecommunications carrier server 40.

[0085] Fig. 12 is a diagram showing an example of a message transmitted to the user terminal 50 according to the second modified example of the embodiment. Fig. 12 shows an example of an image displayed on the display screen when a message including an authentication number is transmitted to the user terminal 50. The message including the authentication number shows, for example, the authentication number (M3) together with a statement (M11) urging authentication and a statement (M12) informing the user of the authentication method.

[0086] FIG. 13 is a sequence diagram showing the flow of processing performed by the operation system 1 according to the second modification of the embodiment.

[0087] The sequence of Fig. 13, like Fig. 6, shows the flow of processing when a user U applies for use of a credit card. The processing shown in steps S110 to S117, S119, and S122 in Fig. 13 is similar to steps S10 to S17, S18, and S21 in Fig. 6, and therefore description thereof will be omitted.

[0088] In step S117, when the operation server 10 issues the authentication URL by the authentication URL issuer 101, the operation server 10 transmits the authentication URL to the issue processing server 30 by the authentication URL output unit 104 (step S118). The issue processing server 30 receives the authentication URL transmitted from the operation server 10. The medium delivery unit 301 arranges for the delivery of the manufactured card (step S120). The medium delivery unit 301 generates a delivery item with a credit card attached to a mount on which an authentication URL is printed, and arranges for the generated delivery item to be delivered to the user U. The user U receives the delivery item including the credit card and the authentication URL (step S121).

[0089] When the operations server 10 receives the delivery information sent from the issuance processing server 30 in step S122, it generates a message notifying the user U of the authentication number and requests delivery of the message by sending the telephone number to the telecommunications carrier server 40 as the destination (step S123). When the communication carrier server 40 receives the delivery request transmitted from the operation server 10, it transmits a message to the user terminal 50 (step S124). The user terminal 50 receives the message (message including the authentication number) notified from the operation server 10 via the communication carrier server 40 (step S125).

[0090] As described above, in the operation system 1 according to the second modification of the embodiment, the medium delivery handling unit 301 notifies the user of either the authentication number (one example of an authentication code) or the authentication URL (authentication address) by medium delivery that delivers a credit card. The electronic notification control unit 102 notifies the user of the other authentication number (one example of an authentication code) or the authentication URL (authentication address) by electronic notification. As a result, the operation system 1 according to the second modification of the embodiment achieves the same effects as those described above.

[0091] In addition, in the operation system 1 according to the second modification of the embodiment, a two-dimensional code with an embedded authentication URL is delivered in the delivery of the medium. This allows the user U to easily access the site indicated by the authentication URL by simply reading the two-dimensional code without having to input the authentication URL.

[0092] In addition, in the operation system 1 according to the second modified embodiment, the authentication URL is stored in the memory (storage medium) of the IC (integrated circuit) of the credit card during the medium delivery. This makes it impossible to obtain the authentication URL without using a card reader dedicated to the NDEF application or the like, making it difficult for others to recognize the authentication URL.

[0093] (Modification 3 of the embodiment) Here, a third variation of the embodiment will be described. This variation differs from the above-described embodiment in that it combines the first and second variations. That is, in this variation, public personal authentication is used for identity verification. Also, in this variation, the authentication URL is notified (delivered) to the user U by medium delivery, and the authentication number is notified to the user terminal 50 by electronic notification.

[0094] 14 is a block diagram showing a configuration example of an operation system 1 according to Modification 3 of the embodiment. The operation system 1 of this modification includes a signature verification server 60. The configuration and functions of the signature verification server 60 are similar to those of the signature verification server 60 in Modification 1, and therefore a description thereof will be omitted. Furthermore, operation system 1 of this modification includes authentication URL acquisition unit 302 in issue processing server 30, and authentication URL output unit 104 in operation server 10. The configuration and function of authentication URL acquisition unit 302 are similar to those of authentication URL acquisition unit 302 in modification 2, and therefore a description thereof will be omitted. The configuration and function of authentication URL output unit 104 are similar to those of authentication URL output unit 104 in modification 2, and therefore a description thereof will be omitted.

[0095] As described above, in the operation system 1 according to the third modification of the embodiment, when the input information matches the authentication number, the authentication unit 103 performs official personal authentication using a personal card, which is an official certificate. Furthermore, the medium delivery handling unit 301 notifies the user of either the authentication number (one example of an authentication code) or the authentication URL (authentication address) by medium delivery that delivers a credit card. The electronic notification control unit 102 notifies the user of the authentication number (one example of an authentication code) or the authentication URL (authentication address) by electronic notification. As a result, the operation system 1 according to the third modification of the embodiment achieves the same effects as those described above.

[0096] As described above, in the operation system 1 according to the embodiment and its modified example, when the input information and the authentication number match, the authentication unit 103 performs official personal authentication using a personal card, which is an official certificate. In addition, the medium delivery handling unit 301 notifies the user of either the authentication number (an example of an authentication code) or the authentication URL (an address for authentication) by medium delivery. The electronic notification control unit 102 notifies the user of the other of the authentication number (an example of an authentication code) and the authentication URL (an address for authentication) by electronic notification. As a result, in the operation system 1 according to the modified example 3 of the embodiment, the credit card can be activated according to the result of the determination in the operation system 1 as to whether the input information and the authentication number match, and the issuer can handle the activation operation after authentication without increasing the burden on the issuer.

[0097] The operation system 1 and the operation server 10 in the above-mentioned embodiment may be realized in whole or in part by a computer. In that case, a program for realizing this function may be recorded in a computer-readable recording medium, and the program recorded in the recording medium may be read into the computer system and executed to realize the function. The term "computer system" as used herein includes hardware such as an OS and peripheral devices. The term "computer-readable recording medium" refers to portable media such as flexible disks, optical magnetic disks, ROMs, and CD-ROMs, and storage devices such as hard disks built into the computer system. The term "computer-readable recording medium" may also include a medium that dynamically holds a program for a short period of time, such as a communication line when a program is transmitted via a network such as the Internet or a communication line such as a telephone line, and a medium that holds a program for a certain period of time, such as a volatile memory inside a computer system that is a server or client in that case. The above-mentioned program may be a program for realizing a part of the above-mentioned function, or may be a program that can realize the above-mentioned function in combination with a program already recorded in the computer system, or may be a program that is realized using a programmable logic device such as an FPGA (Field Programmable Gate Array).

[0098] Although an embodiment of the present invention has been described in detail above with reference to the drawings, the specific configuration is not limited to this embodiment, and designs that do not deviate from the gist of the present invention are also included. [Explanation of symbols]

[0099] 1...operation system, 10...operation server, 100...authentication data acquisition unit, 101...authentication URL issuing unit, 102...electronic notification control unit, 103...authentication unit, 104...authentication URL output unit, 20...credit card issuing company server, 200...ticket issuance data generation unit, 30...issuance processing server, 300...authentication data generation unit, 301...media delivery response unit, 40...communications carrier server, 50...user terminal

Claims

1. An operation system for delivering credit cards, which delivers an unactivated credit card to a user, and activates the credit card depending on an authentication result of authenticating whether a recipient who receives the credit card is the user, a notification control unit that notifies the user of either the authentication code or the authentication address by a medium delivery that delivers the credit card, and notifies the user of the other by electronic notification; an authentication unit that, at a site corresponding to the authentication address having an input request field for requesting input of the authentication code, determines whether or not input information entered into the input request field matches the authentication code notified to the user by the medium delivery or electronic notification; Equipped with If the input information matches the authentication code, the credit card is validated by the credit card issuing company. Operational system.

2. the authentication unit performs official personal authentication using a personal card, which is an official certificate, when the input information and the authentication code match. The operation system according to claim 1 .

3. 1. An operation method executed by a computer for use in an operation system that performs an operation of delivering an unactivated credit card to a user and activating the credit card in accordance with an authentication result of authenticating whether a recipient who receives the credit card is the user, comprising: notifying the user of either the authentication code or the authentication address by a medium delivery for delivering the credit card, and notifying the user of the other by electronic notification; determining whether or not input information entered into a request field for inputting the authentication code at a site corresponding to the authentication address, the request field having an input request field for inputting the authentication code, matches the authentication code notified to the user by the medium delivery or electronic notification; If the input information matches the authentication code, the credit card is validated by the credit card issuing company. Operation method.

Images