Card management apparatus, card management method, and program

Abstract

To provide a card management apparatus, a card management method, and a program configured to allow a user to easily activate a received card which is not activated.SOLUTION: A card management apparatus includes: a storage unit which stores identification information which is different from a card number, the identification information corresponding to a card number of a card issued in an inactive state in response to an application from an applicant; a receiving unit which receives identification information acquired by a terminal of the applicant from a card received by the applicant and transmitted from the terminal; a determination unit which determines, if identification information stored in the storage unit include identification information corresponding to the identification information received by the receiving unit, that a card corresponding to the identification information received by the receiving unit is to be activated; and an activation control unit which controls execution of activation processing on the card determined to be activated.SELECTED DRAWING: Figure 4

Description

[Technical field]

[0001] The present invention relates to a card management device, a card management method, and a program. [Background technology]

[0002] Traditionally, credit card companies have mailed credit cards in a usable state (i.e., activated state) to credit card applicants by registered mail or registered mail. Recently, some credit card companies have started to mail credit cards with new expiration dates by regular mail only, to make it easier for users to receive their cards. By mailing by regular mail, credit card companies can reduce mailing costs. However, if a credit card is mailed in an activated state, there is a risk that someone other than the applicant (the person himself / herself) will receive the credit card and misuse it. Furthermore, when mailed by regular mail, the credit card is placed in a mailbox, so there is a possibility that the credit card may be stolen from the mailbox and misused.

[0003] Therefore, in order to reduce the risk of credit cards being misused when they are sent by regular mail, it is possible to send the credit card to the applicant in an unusable state (i.e., in an unactivated state), and have the applicant activate the credit card themselves upon receiving it. For example, the following Patent Document 1 proposes a technology in which a user activates a credit card service used on a communication terminal such as a smartphone by himself / herself. In this technology, the user requests an application screening for the credit card service from the user terminal. If the application screening is passed, activation information for enabling the application of the credit card service is transmitted to the user terminal of the user. The user activates the application using the received activation information. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2019-145071 A Summary of the Invention [Problem to be solved by the invention]

[0005] However, in the technology described in Patent Document 1, if a user passes the membership examination, the user must activate the device by himself / herself using the activation information, which is time-consuming.

[0006] In view of the above-mentioned problems, an object of the present invention is to provide a card management device, a card management method, and a program that enable a user to easily activate a card that he or she has received in an unactivated state. [Means for solving the problem]

[0007] In order to solve the above-mentioned problems, a card management device according to one embodiment of the present invention is a card management device comprising: a memory unit that stores identification information different from a card number corresponding to the card number of a card to be issued in an unactivated state upon receipt of an application from an applicant; a reception unit that receives the identification information acquired from the card received by the applicant by a terminal held by the applicant and transmitted from the terminal; a determination unit that determines that the card corresponding to the identification information accepted by the reception unit is to be activated if identification information matching the identification information accepted by the reception unit is present among the identification information stored in the memory unit; and an activation control unit that controls the execution of an activation process for the card determined to be to be activated.

[0008] A card management method according to one embodiment of the present invention is a card management method executed by a computer, including a storage process for storing identification information different from a card number corresponding to the card number of a card to be issued in an unactivated state upon receipt of an application from an applicant; a reception process for receiving the identification information acquired from the card received by the applicant by a terminal held by the applicant and transmitted from the terminal; a determination process for determining that the card corresponding to the identification information accepted by the reception process is to be activated if identification information matching the identification information accepted by the reception process is present among the identification information stored by the storage process; and an activation control process for controlling execution of an activation process for the card determined to be to be activated.

[0009] A program according to one embodiment of the present invention is a program for causing a computer to function as: a storage means for storing identification information different from a card number, which corresponds to the card number of a card to be issued in an unactivated state upon receipt of an application from an applicant; a reception means for receiving the identification information obtained from the card received by the applicant by a terminal held by the applicant and transmitted from the terminal; a determination means for determining that the card corresponding to the identification information accepted by the reception means is eligible for activation if identification information matching the identification information accepted by the reception means is present among the identification information stored in the storage means; and an activation control means for controlling the execution of an activation process for the card determined to be eligible for activation. Effect of the Invention

[0010] According to the present invention, a user can easily activate a card that he or she receives in an unactivated state. [Brief description of the drawings]

[0011] [Figure 1]1 is a block diagram showing an example of a configuration of a card management system according to a first embodiment. [Diagram 2] FIG. 2 is a block diagram showing an example of a functional configuration of a user terminal according to the first embodiment. [Diagram 3] FIG. 2 is a block diagram showing an example of a functional configuration of an issuer server according to the first embodiment. [Figure 4] 2 is a block diagram showing an example of a functional configuration of a card management server according to the first embodiment. FIG. [Diagram 5] FIG. 4 is a sequence diagram showing an example of a processing flow according to the first embodiment. [Figure 6] FIG. 11 is a block diagram showing an example of a functional configuration of an issuer server according to a second embodiment. [Figure 7] FIG. 11 is a block diagram showing an example of a functional configuration of a card management server according to a second embodiment. [Figure 8] FIG. 11 is a sequence diagram showing an example of a processing flow according to the second embodiment. [Figure 9] FIG. 13 is a block diagram showing an example of a functional configuration of an issuer server according to a third embodiment. [Figure 10] FIG. 13 is a block diagram showing an example of a functional configuration of a card management server according to a third embodiment. [Figure 11] FIG. 13 is a sequence diagram showing an example of a processing flow according to the third embodiment. [Figure 12] FIG. 13 is a block diagram showing an example of a functional configuration of an issuer server according to a fourth embodiment. [Figure 13] FIG. 13 is a block diagram showing an example of a functional configuration of a card management server according to a fourth embodiment. [Figure 14] FIG. 13 is a sequence diagram showing an example of a processing flow according to the fourth embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. In each embodiment described below, an example will be described in which the specific type of card is a credit card. Therefore, the service that issues the card is a service that issues a credit card (hereinafter also referred to as a "credit card issuing service"), and the business that issues the card is a credit card company (hereinafter also referred to as an "issuer"). In each embodiment, the credit card is issued in an unusable state (i.e., in an unactivated state) and mailed to the user. The type of card is not limited to a credit card, and may be a cash card, a debit card, etc. Furthermore, the name of the service for which the card is issued and the name of the issuer may vary depending on the type of card.

[0013] <<1. First embodiment>> The first embodiment will be described with reference to FIGS.

[0014] <1-1. Card management system configuration> First, the configuration of a card management system according to the first embodiment will be described with reference to Fig. 1. Fig. 1 is a block diagram showing an example of the configuration of a card management system according to the first embodiment.

[0015] The card management system 1 shown in Fig. 1 is a system for managing card issuance. In the first embodiment, the specific type of card is a credit card, so the object of issuance by the card management system 1 is a credit card. Note that the object of issuance by the card management system 1 may change depending on the type of card.

[0016] As shown in FIG. 1, the card management system 1 includes a user terminal 10, an issuer server 20, and a card management server 30. The network NW may be configured to transmit and receive information using, for example, a Local Area Network (LAN), a Wide Area Network (WAN), a telephone network (mobile phone network, landline telephone network, etc.), a regional Internet Protocol (IP) network, the Internet, etc.

[0017] (1) User terminal 10 The user terminal 10 is a terminal owned by a user who is an applicant for a credit card. The user terminal 10 is, for example, a mobile terminal such as a smartphone or a tablet terminal, or a PC (Personal Computer). The user terminal 10 is connected to the card management server 30 via a network NW so as to be able to communicate with the card management server 30.

[0018] In communication with the card management server 30, the user terminal 10 transmits identification information acquired from the credit card received by the user. The identification information is information used to determine whether or not the credit card is to be activated. The identification information is information different from the card number (PAN: Primary Account Number) of the credit card, and is prepared for each card number. The identification information in the first embodiment is, for example, an individual URL (Uniform Resource Locator). The individual URL is information including address information for accessing the card management server 30 (card management device) from the user terminal 10, and an identifier unique to the card number.

[0019] (2) Issuer Server 20 The issuer server 20 is a server device for managing various information related to credit cards and activating credit cards. The issuer server 20 is composed of one or more servers (e.g., cloud servers). The issuer server 20 is connected to the card management server 30 via a network NW so as to be able to communicate with the card management server 30.

[0020] In communication with the card management server 30, the issuer server 20 transmits, for example, an individual URL generated for each card number by the issuer server 20, and receives information for activation processing (hereinafter also referred to as "activation information"), etc. The activation information is, for example, a determination result of an activation target, etc.

[0021] (3) Card management server 30 The card management server 30 is a server device for managing various information related to credit cards and controlling the activation of credit cards. The card management server 30 is an example of a card management device. The card management server 30 is composed of one or more servers (e.g., cloud servers). The card management server 30 is communicatively connected to the user terminal 10 and the issuer server 20 via the network NW.

[0022] In communication with the user terminal 10, the card management server 30 receives, for example, an individual URL acquired by the user terminal 10 from a credit card. In communication with the issuer server 20, the card management server 30 receives, for example, an individual URL generated for each card number by the issuer server 20, and transmits activation information and the like.

[0023] <1-2. Functional configuration of user terminal> The configuration of the card management system 1 according to the first embodiment has been described above. Next, the functional configuration of the user terminal 10 according to the first embodiment will be described with reference to Fig. 2. Fig. 2 is a block diagram showing an example of the functional configuration of the user terminal 10 according to the first embodiment. As shown in FIG. 2, the user terminal 10 includes a communication unit 110, an input unit 120, a reading unit 130, a storage unit 140, a control unit 150, and an output unit 160.

[0024] (1) Communications Department 110 The communication unit 110 has a function of transmitting and receiving various information. For example, the communication unit 110 communicates with the card management server 30 via the network NW. In communication with the card management server 30, the communication unit 110 transmits the individual URL obtained from the credit card received by the user.

[0025] (2) Input unit 120 The input unit 120 has a function of accepting input from a user. The input unit 120 is, for example, configured with an input device provided in the user terminal 10 as hardware, such as a button, a touch panel, a microphone, a mouse, a keyboard, and the like.

[0026] (3) Reading unit 130 The reading unit 130 has a function of acquiring an individual URL from a credit card. The individual URL is written, for example, to an IC (integrated circuit) chip provided on the credit card. In this case, the reading unit 130 acquires the individual URL by reading the individual URL from the IC chip, for example, by communication using NFC (Near field communication). A two-dimensional code having an individual URL may be attached to the credit card. In this case, the reading unit 130 obtains the individual URL by reading the individual URL from the two-dimensional code, for example, with a camera. This allows the user to read the individual URL from the two-dimensional code when the user terminal 10 does not have an NFC function or when reading by NFC does not work well.

[0027] (4) Storage section 140 The storage unit 140 has a function of storing various information. The storage unit 140 is configured by a storage medium provided in the user terminal 10 as hardware, such as a hard disk drive (HDD), a solid state drive (SSD), 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.

[0028] (5) Control unit 150 The control unit 150 has a function of controlling the overall operation of the user terminal 10. The control unit 150 is realized, for example, by causing a CPU (Central Processing Unit) provided as hardware in the user terminal 10 to execute a program. As shown in FIG. 2, the control unit 150 includes an operation receiving unit 151, a reading control unit 152, an access control unit 153, and an output control unit 154.

[0029] (5-1) Operation reception unit 151 Operation acceptance unit 151 has a function of accepting a user operation input to input unit 120. The user performs, for example, an operation to read an individual URL.

[0030] (5-2) Reading control unit 152 The reading control unit 152 has a function of controlling the reading of the individual URL by the reading unit 130. For example, when an operation to read an individual URL is accepted by the operation accepting unit 151, the reading control unit 152 activates the reading unit 130 to read the individual URL from the credit card.

[0031] (5-3) Access control unit 153 The access control unit 153 has a function of controlling access to an individual URL. For example, when an individual URL is read by the reading unit 130, the access control unit 153 accesses the card management server 30 from the address information indicated by the read individual URL. When accessing, the access control unit 153 transmits the individual URL to the card management server 30 via the communication unit 110.

[0032] (5-4) Output control unit 154 The output control unit 154 has a function of controlling the output of various screens and information. For example, the output control unit 154 causes the output unit 160 to display a screen showing the result of reading an individual URL, the result of activation processing, and the like.

[0033] (6) Output unit 160 The output unit 160 has a function of outputting various information. The output unit 160 is, for example, an output device provided in the user terminal 10 as hardware, such as a display device or a touch screen (touch panel), or an audio output device such as a speaker. The output unit 160, under the control of the output control unit 154, displays on the display device a screen showing, for example, the results of reading the individual URL and the results of the activation process.

[0034] <1-3. Issuer server functional configuration> The functional configuration of the user terminal 10 according to the first embodiment has been described above. Next, the functional configuration of the issuer server 20 according to the first embodiment will be described with reference to Fig. 3. Fig. 3 is a block diagram showing an example of the functional configuration of the issuer server 20 according to the first embodiment. As shown in FIG. 3, the issuer server 20 includes a communication unit 210, a storage unit 220, and a control unit 230.

[0035] (1) Communications unit 210 The communication unit 210 has a function of transmitting and receiving various information. For example, the communication unit 210 communicates with the card management server 30 via the network NW. In communication with the card management server 30, the communication unit 210 transmits an individual URL generated for each card number by the issuer server 20 and receives activation information.

[0036] (2) Storage section 220 The storage unit 220 has a function of storing various information. The storage unit 220 is configured by a storage medium provided in the issuer server 20 as hardware, such as a HDD, an SSD, a flash memory, an EEPROM, a RAM, a ROM, or any combination of these storage media. As shown in FIG. 3, the storage unit 220 includes a member attribute information storage unit 221, an issuing information storage unit 222, and a corresponding information storage unit 223.

[0037] (2-1) Member attribute information storage unit 221 The member attribute information storage unit 221 has a function of storing member attribute information. The member attribute information is information indicating the attributes of a person (member) to whom a credit card is issued. The member attribute information is, for example, name, address, age, occupation, date of birth, card number (16 digits), card code, etc.

[0038] (2-2) Issue information storage unit 222 The issuing information storage unit 222 has a function of storing issuing information. The issuing information is information about the credit card to be issued. The issuing information is, for example, a card code, an individual URL, and the like.

[0039] (2-3) Correspondence information storage unit 223 The correspondence information storage unit 223 has a function of storing correspondence information. The correspondence information is information indicating a correspondence relationship between a card number and an individual URL (identification information). In other words, the correspondence information is information in which the card number and the individual URL are associated with each other.

[0040] (3) Control unit 230 The control unit 230 has a function of controlling the overall operation of the issuer server 20. The control unit 230 is realized, for example, by causing a CPU provided as hardware in the issuer server 20 to execute a program. As shown in FIG. 3, the control unit 230 includes a card number allocation unit 231, an identification information generation unit 232, an identification information linking unit 233, and an activation processing unit 234.

[0041] (3-1) Card Number Allocation Unit 231 The card number assignment unit 231 has a function of assigning a card number. The card number assignment unit 231 assigns a unique card number to each credit card to be issued. The assigned card number is stored in the issuance information storage unit 222 together with the issuance information of the credit card corresponding to the own card number. The assigned card number is also stored in the correspondence information storage unit 223 as correspondence information in association with an individual URL generated for the credit card corresponding to the own card number.

[0042] (3-2) Identification information generation unit 232 The identification information generating unit 232 has a function of generating an individual URL (identification information). The individual URL corresponds to the card number of a credit card that is issued in an unactivated state upon receipt of an application from a user, and is information different from the card number. The individual URL is generated for each card number by the identification information generating unit 232. For example, the identification information generating unit 232 generates address information for accessing the card management server 30 from the user terminal 10 and an identifier unique to the card number, and generates information including the address information and the identifier as an individual URL. The generated individual URL is stored in the correspondence information storage unit 223 as correspondence information in association with a card number corresponding to the individual URL among the card numbers assigned by the card number assigning unit 231. The address information may be common to multiple credit cards.

[0043] (3-3) Identification information linking unit 233 The identification information linking unit 233 has a function of linking the individual URL to the outside. For example, the identification information linking unit 233 transmits (links) the individual URL generated by the identification information generating unit 232 from the communication unit 210 to the card management server 30.

[0044] (3-4) Activation processing unit 234 The activation processing unit 234 has a function of executing activation processing. For example, the activation processing unit 234 executes activation processing based on activation information that the communication unit 210 receives from the card management server 30. Specifically, when an activation request is received from the card management server 30, the activation processing unit 234 activates a credit card that is determined to be the target of activation as indicated by the activation information.

[0045] <1-4. Functional configuration of the card management server> The functional configuration of the issuer server 20 according to the first embodiment has been described above. Next, the functional configuration of the card management server 30 according to the first embodiment will be described with reference to Fig. 4. Fig. 4 is a block diagram showing an example of the functional configuration of the card management server 30 according to the first embodiment. As shown in FIG. 4, the card management server 30 includes a communication unit 310, a storage unit 320, and a control unit 330.

[0046] (1) Communications unit 310 The communication unit 310 has a function of transmitting and receiving various information. For example, the communication unit 310 communicates with the user terminal 10 and the issuer server 20 via the network NW. In communication with the user terminal 10, the communication unit 310 receives the individual URL that the user terminal 10 has acquired from the credit card. In communication with the issuer server 20, the communication unit 310 receives an individual URL generated for each card number by the issuer server 20, and transmits activation information.

[0047] (2) Storage section 320 The memory unit 320 is configured by a storage medium provided as hardware in the card management server 30, such as an HDD, SSD, flash memory, EEPROM, RAM, ROM, or any combination of these storage media. As shown in FIG. 4, the storage unit 320 includes a member attribute information storage unit 321 and an identification information storage unit 322.

[0048] (2-1) Member attribute information storage unit 321 Member attribute information storage unit 321 has a function of storing member attribute information. Member attribute information storage unit 321 stores a portion of the member attribute information stored in member attribute information storage unit 221 of issuer server 20. For example, member attribute information storage unit 321 stores only information necessary for determining the accuracy of information about a user (applicant) performed by card management server 30, among the member attribute information stored in member attribute information storage unit 221 of issuer server 20. As an example, member attribute information storage unit 321 stores a name, a telephone number, and a unique ID (a number that can identify an individual other than a card number).

[0049] (2-2) Identification information storage unit 322 The identification information storage unit 322 has a function of storing identification information. The identification information storage unit 322 is an example of a storage unit. For example, the identification information storage unit 322 stores an individual URL that is transmitted from the issuer server 20 to the card management server 30 and received by the communication unit 310.

[0050] (3) Control unit 330 The control unit 330 has a function of controlling the overall operation of the card management server 30. The control unit 330 is realized, for example, by causing a CPU provided as hardware in the card management server 30 to execute a program. As shown in FIG. 4, the control unit 330 includes a receiving unit 331, a determining unit 332, and an activation control unit 333.

[0051] (3-1) Reception Section 331 The reception unit 331 has a function of receiving an input of an individual URL. For example, the reception unit 331 receives an input of an individual URL that is acquired by the user terminal 10 from a credit card received by a user and transmitted from the user terminal 10. The individual URL received by the reception unit 331 is an individual URL that belongs to a credit card that is to be determined as an object of activation.

[0052] (3-2) Judgment section 332 The determination unit 332 has a function of determining an object to be activated. For example, the determination unit 332 determines whether or not a credit card corresponding to an individual URL accepted by the acceptance unit 331 is an object to be activated based on an individual URL generated by the issuer server 20 and stored in the identification information storage unit 322. Specifically, the determination unit 332 checks whether or not an individual URL that matches the individual URL accepted by the acceptance unit 331 exists among the individual URLs stored in the identification information storage unit 322. If an individual URL exists, the determination unit 332 determines that the credit card corresponding to the individual URL accepted by the acceptance unit 331 is an object to be activated. On the other hand, if an individual URL does not exist, the determination unit 332 determines that the credit card corresponding to the individual URL accepted by the acceptance unit 331 is not an object to be activated.

[0053] (3-3) Activation control unit 333 The activation control unit 333 has a function of controlling the execution of activation processing. For example, the activation control unit 333 controls the execution of activation processing for a credit card determined to be an activation target based on the determination result by the determination unit 332. Specifically, the activation control unit 333 shares the determination result (activation information) by the determination unit 332 with the issuer server 20. At this time, when the determination result indicates that the credit card being determined is an activation target, the activation control unit 333 requests the issuer server 20 to execute the activation processing for the credit card determined to be an activation target.

[0054] <1-5. Processing flow> The functional configuration of the card management server 30 according to the first embodiment has been described above. Next, a process flow according to the first embodiment will be described with reference to Fig. 5. Fig. 5 is a sequence diagram showing an example of a process flow according to the first embodiment.

[0055] As shown in FIG. 5, first, the card number assignment unit 231 of the issuer server 20 assigns a card number to a credit card to be issued (step S101). Next, the identification information generating unit 232 of the issuer server 20 generates an individual URL for each card number assigned by the card number assigning unit 231 (step S102). After the card number is assigned and the individual URL is generated, the correspondence information storage unit 223 of the issuer server 20 associates the card number with the corresponding individual URL and stores them as correspondence information (step S103). Next, the identification information linking unit 233 of the issuer server 20 links (transmits) the individual URL generated by the identification information generating unit 232 from the communication unit 210 to the card management server 30 (step S104). The identification information storage unit 322 of the card management server 30 stores the individual URL that the communication unit 310 received from the issuer server 20 (step S105).

[0056] The user performs an operation to read the individual URL on the user terminal 10 (step S106). Specifically, after the user receives the credit card that has been issued and mailed in an unactivated state, the user performs an operation on the user terminal 10 to read the individual URL from the credit card. When operation reception unit 151 receives an operation to read the individual URL from the user, read control unit 152 of user terminal 10 activates reading unit 130 and causes it to read the individual URL from the credit card (step S107). After reading the individual URL, the access control unit 153 of the user terminal 10 accesses the card management server 30 from the address information indicated by the read individual URL (step S108). At the time of access, the access control unit 153 transmits the individual URL to the card management server 30 via the communication unit 110 (step S109).

[0057] The accepting unit 331 of the card management server 30 accepts an input of the individual URL transmitted from the user terminal 10 and received by the communication unit 310 (step S110). Next, the judgment unit 332 of the card management server 30 judges whether or not the credit card corresponding to the individual URL accepted by the acceptance unit 331 is eligible for activation, based on the individual URL generated by the issuer server 20 stored in the identification information memory unit 322 (step S111). Next, the activation control unit 333 of the card management server 30 performs activation control processing based on the determination result by the determination unit 332 (step S112). Specifically, the activation control unit 333 communicates the determination result by the determination unit 332 to the issuer server 20. At this time, if the determination result indicates that the credit card being determined is to be activated, the activation control unit 333 requests the issuer server 20 to execute activation processing for the credit card determined to be to be activated. The activation processing unit 234 of the issuer server 20 executes activation processing based on the activation information received by the communication unit 210 from the card management server 30 (step S113). Specifically, when an activation request is received from the card management server 30, the activation processing unit 234 activates a credit card determined to be subject to activation as indicated by the activation information.

[0058] As described above, the card management server 30 (card management device) according to the first embodiment includes an identification information memory unit (memory unit) 322 that stores an individual URL (identification information) different from the card number, which corresponds to the card number of a credit card (card) issued in an unactivated state upon receipt of an application from a user (applicant); a reception unit 331 that receives an individual URL acquired by a user terminal 10 (a terminal possessed by the applicant) from a credit card received by a user and transmitted from the user terminal 10; a determination unit 332 that determines that the credit card corresponding to the individual URL accepted by the reception unit 331 is to be activated if an individual URL matching the individual URL accepted by the reception unit 331 is present among the individual URLs stored in the identification information memory unit 322; and an activation control unit 333 that controls the execution of an activation process for the credit card determined to be to be activated.

[0059] With this configuration, the user can activate the received credit card simply by operating the user terminal 10 and reading the individual URL from the credit card. Therefore, the card management server 30 according to the first embodiment enables a user to easily activate a card that he or she has received in an unactivated state.

[0060] Conventionally, in order to enable applicants to activate the credit cards they received by themselves, it has been necessary to modify existing core systems owned by issuers, but it has been difficult to modify existing core systems owned by issuers in order to allow for activation. For example, for existing core systems, development plans were made in advance from a mid- to long-term perspective, making it difficult to interrupt development related to activation. In addition, after system modifications, a system freeze period (period during which the system cannot be modified) was required to ensure stable operation of the system. In addition, it was necessary to consider the impact of modified parts on the entire system, which resulted in considerable development costs. Also, since there were not enough system engineers in-house, development support (coding work, etc.) was often outsourced to external system companies. However, because the number of developers for development plans was limited from a mid- to long-term perspective, there was always a lack of resources when it came to increasing development requests. In contrast, in the card management system 1 according to the first embodiment, a card management server 30 having a function of enabling an applicant to activate a received credit card by himself is provided in addition to an issuer server 20 corresponding to an existing core system owned by the issuer. In this card management system 1, the issuer server 20 can activate a credit card using an existing function based on activation information linked from the card management server 30. Therefore, the issuer does not need to modify the core system to incorporate a function that enables an applicant to activate a received credit card by himself, by making a minimum modification to the core system that enables the card management server 30 to link the activation information. Therefore, by using the card management system 1 of the first embodiment, an issuer can easily introduce into an existing core system a mechanism that enables applicants to activate the credit cards they receive themselves.

[0061] <<2. Second embodiment>> Having described the first embodiment, the second embodiment will now be described with reference to Figs. In the following, explanations that overlap with the first embodiment will be omitted as appropriate.

[0062] <2-1. Card Management System Configuration> The card management system of the second embodiment includes a user terminal, an issuer server, and a card management server, similar to the card management system 1 of the first embodiment described with reference to Figure 1. In addition, the user terminal according to the second embodiment has the same functions as the user terminal 10 according to the first embodiment, so it will be described with the same reference numeral 10. Moreover, the issuer server according to the second embodiment will be described with a different reference numeral 20a because its functions are different from those of the issuer server 20 according to the first embodiment. Moreover, the card management server according to the second embodiment will be described with a different reference numeral 30a because its functions are different from those of the card management server 30 according to the first embodiment. In addition, in the card management system according to the second embodiment, the functions of the issuer server 20a and the card management server 30a are different from those of the issuer server 20 and the card management server 30 according to the first embodiment, so they will be described using different reference symbols 1a. In the above-described first embodiment, an example in which an individual URL is generated by the issuer server 20 has been described, but the present invention is not limited to such an example. In the second embodiment, an example in which an individual URL is generated by the card management server 30a will be described.

[0063] <2-2. Functional configuration of user terminal> The functional configuration of the user terminal 10 according to the second embodiment is the same as the functional configuration of the user terminal 10 according to the first embodiment described with reference to FIG. 2, and therefore the description thereof will be omitted.

[0064] <2-3. Issuer server functional configuration> The functional configuration of the issuer server 20a according to the second embodiment will be described with reference to Fig. 6. Fig. 6 is a block diagram showing an example of the functional configuration of the issuer server 20a according to the second embodiment. As shown in FIG. 6, the issuer server 20a includes a communication unit 210a, a storage unit 220a, and a control unit 230a.

[0065] (1) Communication unit 210a The communication unit 210a transmits (collaborates with) issuance information and receives activation information in communication with the card management server 30a.

[0066] (2) Storage unit 220a As shown in FIG. 6, the storage unit 220a includes a member attribute information storage unit 221 and an issuance information storage unit 222.

[0067] (2-1) Member attribute information storage unit 221 The function of the member attribute information storage unit 221 according to the second embodiment is similar to the function of the member attribute information storage unit 221 according to the first embodiment described with reference to FIG. 3, and therefore the description thereof will be omitted.

[0068] (2-2) Issue information storage unit 222 The function of the issuing information storage unit 222 according to the second embodiment is similar to the function of the issuing information storage unit 222 according to the first embodiment described with reference to FIG. 3, and therefore the description thereof will be omitted.

[0069] (3) Control unit 230a As shown in FIG. 6, the control unit 230a includes a card number allocation unit 231, an activation processing unit 234, and an issuance information linking unit 235.

[0070] (3-1) Card Number Allocation Unit 231 The function of the card number allocating unit 231 according to the second embodiment is similar to the function of the card number allocating unit 231 according to the first embodiment described with reference to FIG. 3, and therefore the description thereof will be omitted.

[0071] (3-2) Activation processing unit 234 The function of the activation processing unit 234 according to the second embodiment is similar to the function of the activation processing unit 234 according to the first embodiment described with reference to FIG. 3, and therefore the description thereof will be omitted.

[0072] (3-3) Publication Information Collaboration Department 235 The issuing information linking unit 235 has a function of linking the issuing information to an external device. For example, the issuing information linking unit 235 transmits (links) the issuing information stored in the issuing information storage unit 222 from the communication unit 210a to the card management server 30a.

[0073] <2-4. Functional configuration of the card management server> The functional configuration of the issuer server 20a according to the second embodiment has been described above. Next, the functional configuration of the card management server 30a according to the second embodiment will be described with reference to Fig. 7. Fig. 7 is a block diagram showing an example of the functional configuration of the card management server 30a according to the second embodiment. As shown in FIG. 7, the card management server 30a includes a communication unit 310a, a storage unit 320a, and a control unit 330a.

[0074] (1) Communication unit 310a The communication unit 310a receives an individual URL in communication with the user terminal 10. Furthermore, the communication unit 310a receives issuing information and transmits activation information in communication with the issuer server 20a.

[0075] (2) Storage section 320a As shown in FIG. 7, the storage unit 320a includes a member attribute information storage unit 321, an issuing information storage unit 323, and a corresponding information storage unit 324.

[0076] (2-1) Member attribute information storage unit 321 The function of the member attribute information storage unit 321 according to the second embodiment is similar to the function of the member attribute information storage unit 321 according to the first embodiment described with reference to FIG. 4, and therefore the description thereof will be omitted.

[0077] (2-2) Issue information storage unit 323 The issued information storage unit 323 according to the second embodiment has a function of storing issued information The issued information storage unit 323 stores the issued information that the communication unit 310a receives from the issuer server 20a.

[0078] (2-3) Correspondence information storage unit 324 The corresponding information storage unit 324 according to the second embodiment has a function of storing corresponding information. The corresponding information storage unit 324 is an example of a storage unit. The corresponding information storage unit 324 stores, as corresponding information, a card number transmitted from the issuer server 20a to the card management server 30a and an individual URL generated by an identification information generation unit 335, which will be described later, in association with each other. The card number is a card number included in the issuance information transmitted from the issuer server 20a and received by the communication unit 310a.

[0079] (3) Control unit 330a As shown in FIG. 7, the control unit 330a includes a reception unit 331, a determination unit 332, an activation control unit 333, a card number acquisition unit 334, and an identification information generation unit 335.

[0080] (3-1) Reception Section 331 The reception unit 331 according to the second embodiment has a function of receiving an input of issuing information in addition to an input of an individual URL. For example, the reception unit 331 receives an input of issuing information transmitted from the issuer server 20a and received by the communication unit 310a.

[0081] (3-2) Judgment section 332 The function of the determination unit 332 according to the second embodiment is similar to the function of the determination unit 332 according to the first embodiment described with reference to FIG. 4, and therefore the description thereof will be omitted.

[0082] (3-3) Activation control unit 333 The function of the activation control unit 333 according to the second embodiment is similar to the function of the activation control unit 333 according to the first embodiment described with reference to FIG. 4, and therefore the description thereof will be omitted.

[0083] (3-4) Card number acquisition unit 334 The card number acquisition unit 334 according to the second embodiment has a function of acquiring a card number. For example, the card number acquisition unit 334 acquires the card number by extracting the card number from the issuance information received by the communication unit 310a from the issuer server 20a.

[0084] (3-5) Identification information generation unit 335 The identification information generating unit 335 according to the second embodiment has a function of generating an individual URL (identification information) for each card number. The identification information generating unit 335 generates the individual URL in the same manner as the identification information generating unit 232 of the issuer server 20 according to the first embodiment described with reference to Fig. 3. The generated individual URL is associated with a card number corresponding to its own individual URL among the card numbers acquired by the card number acquiring unit 334, and is stored as association information in the association information storage unit 324.

[0085] <2-5. Processing flow> The functional configuration of the card management server 30a according to the second embodiment has been described above. Next, a process flow according to the second embodiment will be described with reference to Fig. 8. Fig. 8 is a sequence diagram showing an example of a process flow according to the second embodiment.

[0086] As shown in FIG. 8, first, the card number assignment unit 231 of the issuer server 20a assigns a card number to a credit card to be issued (step S201). After the card number is assigned, the issuance information storage unit 222 of the issuer server 20a stores the issuance information including the card number assigned by the card number assignment unit 231 (step S202). Next, the issuance information linking unit 235 of the issuer server 20a links (transmits) the issuance information from the communication unit 210a to the card management server 30a (step S203).

[0087] The issuance information storage unit 323 of the card management server 30a stores the issuance information received by the communication unit 310a from the issuer server 20a (step S204). Next, the card number acquisition unit 334 of the card management server 30a acquires the card number from the issuance information received by the communication unit 310a (step S205). After acquiring the card numbers, the identification information generating unit 335 of the card management server 30a generates an individual URL for each card number acquired by the card number acquiring unit 334 (step S206). After obtaining the card number and generating the individual URL, the correspondence information storage unit 324 of the card management server 30a associates the card number with the corresponding individual URL and stores them as correspondence information (step S207).

[0088] The user performs an operation to read the individual URL on the user terminal 10 (step S208). Specifically, after the user receives the credit card that has been issued and mailed in an unactivated state, the user performs an operation on the user terminal 10 to read the individual URL from the credit card. When operation reception unit 151 receives an operation to read the individual URL from the user, read control unit 152 of user terminal 10 activates reading unit 130 and causes it to read the individual URL from the credit card (step S209). After reading the individual URL, the access control unit 153 of the user terminal 10 accesses the card management server 30a from the address information indicated by the read individual URL (step S210). At the time of access, the access control unit 153 transmits the individual URL to the card management server 30a via the communication unit 110 (step S211).

[0089] The accepting unit 331 of the card management server 30a accepts the input of the individual URL transmitted from the user terminal 10 and received by the communication unit 310a (step S212). Next, the judgment unit 332 of the card management server 30a judges whether or not the credit card corresponding to the individual URL accepted by the acceptance unit 331 is eligible for activation, based on the individual URL generated by the identification information generation unit 335 of the card management server 30a stored in the correspondence information storage unit 324 (step S213). Next, the activation control unit 333 of the card management server 30a performs activation control processing based on the determination result by the determination unit 332 (step S214). Specifically, the activation control unit 333 communicates the determination result by the determination unit 332 to the issuer server 20a. At this time, if the determination result indicates that the credit card being determined is to be activated, the activation control unit 333 requests the issuer server 20a to execute activation processing for the credit card determined to be to be activated. The activation processing unit 234 of the issuer server 20a executes activation processing based on the activation information that the communication unit 210a receives from the card management server 30a (step S215). Specifically, when an activation request is received from the card management server 30a, the activation processing unit 234 activates the credit card that is determined to be the activation target indicated by the activation information.

[0090] As described above, the card management server 30a (card management device) according to the second embodiment includes a correspondence information storage unit (storage unit) 324 that stores an individual URL (identification information) different from the card number, which corresponds to the card number of a credit card (card) issued in an unactivated state upon receipt of an application from a user (applicant), a reception unit 331 that receives an individual URL acquired by a user terminal 10 (a terminal possessed by the applicant) from a credit card received by a user and transmitted from the user terminal 10, a determination unit 332 that determines that the credit card corresponding to the individual URL accepted by the reception unit 331 is to be activated if an individual URL matching the individual URL accepted by the reception unit 331 is present among the individual URLs stored in the correspondence information storage unit 324, and an activation control unit 333 that controls the execution of an activation process for the credit card determined to be to be activated.

[0091] With this configuration, the user can activate the received credit card simply by operating the user terminal 10 and reading the individual URL from the credit card. Therefore, the card management server 30a according to the second embodiment enables a user to easily activate a card that he or she has received in an unactivated state.

[0092] In the card management system 1a according to the second embodiment, the function of the identification information generation unit 232 provided in the issuer server 20 of the card management system 1 according to the first embodiment is provided in the card management server 30a, not in the issuer server 20a, as an identification information generation unit 335. As a result, by using the card management system 1a according to the second embodiment, the issuer can further reduce the amount of modification to the core system compared to the case of using the card management system 1 according to the first embodiment. Therefore, by using the card management system 1a of the second embodiment, issuers can introduce a mechanism that allows applicants to activate credit cards they receive into their existing core systems more easily than with the card management system 1 of the first embodiment.

[0093] <<3. Third embodiment>> Having described the second embodiment, the third embodiment will now be described with reference to Figs. In the following, descriptions that overlap with the first and second embodiments will be omitted as appropriate.

[0094] <3-1. Card Management System Configuration> The card management system of the third embodiment includes a user terminal, an issuer server, and a card management server, similar to the card management system 1 of the first embodiment described with reference to Figure 1. In addition, the user terminal according to the third embodiment has the same functions as the user terminal 10 according to the first embodiment, so it will be described with the same reference numeral 10. Moreover, the issuer server according to the third embodiment will be described with a different reference numeral 20b because its functions are different from those of the issuer server 20 according to the first embodiment. Moreover, the card management server according to the third embodiment will be described with a different reference numeral 30b because its functions are different from those of the card management server 30 according to the first embodiment. In addition, in the card management system according to the third embodiment, the functions of the issuer server 20b and the card management server 30b are different from those of the issuer server 20 and the card management server 30 according to the first embodiment, so they will be described using different reference symbols 1b. In the above-mentioned first and second embodiments, an example in which the card management server 30 has a function that enables the applicant to activate the credit card he or she received by himself or herself has been described, but the present invention is not limited to such an example. In the third embodiment, an example in which the issuer server 20b has a function that enables the applicant to activate the credit card he or she received by himself or herself will be described. That is, the issuer server 20b according to the third embodiment is an example of a card management device. Therefore, in the third embodiment, the address information included in the individual URL is information for accessing the issuer server 20b (card management device) from the user terminal 10.

[0095] <3-2. Functional configuration of user terminal> The functional configuration of the user terminal 10 according to the third embodiment is the same as the functional configuration of the user terminal 10 according to the first embodiment described with reference to FIG. 2, and therefore the description thereof will be omitted.

[0096] <3-3. Issuer server functional configuration> The functional configuration of the issuer server 20b according to the third embodiment will be described with reference to Fig. 9. Fig. 9 is a block diagram showing an example of the functional configuration of the issuer server 20b according to the third embodiment. As shown in FIG. 9, the issuer server 20b includes a communication unit 210b, a storage unit 220b, and a control unit 230b.

[0097] (1) Communication department 210b The communication unit 210b transmits (collaborates with) the card management server 30b in communication with the card management server 30b. Furthermore, the communication unit 210b receives an individual URL in communication with the user terminal 10.

[0098] (2) Storage section 220b As shown in FIG. 9, the storage unit 220b includes a member attribute information storage unit 221, an issuing information storage unit 222, and a corresponding information storage unit 223.

[0099] (2-1) Member attribute information storage unit 221 The function of the member attribute information storage unit 221 according to the third embodiment is similar to the function of the member attribute information storage unit 221 according to the first embodiment described with reference to FIG. 3, and therefore the description thereof will be omitted.

[0100] (2-2) Issue information storage unit 222 The function of the issuing information storage unit 222 according to the third embodiment is similar to the function of the issuing information storage unit 222 according to the first embodiment described with reference to FIG. 3, and therefore the description thereof will be omitted.

[0101] (2-3) Correspondence information storage unit 223 The correspondence information storage unit 223 according to the third embodiment associates a card number assigned by a card number assignment unit 231 (described later) with an individual URL generated by an identification information generation unit 232, and stores the associated information as correspondence information. The correspondence information storage unit 223 according to the third embodiment is an example of a storage unit.

[0102] (3) Control unit 230b As shown in FIG. 9, the control unit 230b includes a card number allocation unit 231, an identification information generation unit 232, an activation processing unit 234, an issuance information linking unit 235, a reception unit 236, a determination unit 237, and an activation control unit 238.

[0103] (3-1) Card Number Allocation Unit 231 The function of the card number allocating unit 231 according to the third embodiment is similar to the function of the card number allocating unit 231 according to the first embodiment described with reference to FIG. 3, and therefore the description thereof will be omitted.

[0104] (3-2) Identification information generation unit 232 The function of the identification information generating unit 232 according to the third embodiment is similar to the function of the identification information generating unit 232 according to the first embodiment described with reference to FIG. 3, and therefore the description thereof will be omitted.

[0105] (3-3) Activation processing unit 234 The function of the activation processing unit 234 according to the third embodiment is similar to the function of the activation processing unit 234 according to the first embodiment described with reference to FIG. However, the function of the activation processing unit 234 in the third embodiment differs from the function of the activation processing unit 234 in the first embodiment in that the activation processing unit 234 executes the activation processing based on activation information output from the activation control unit 238 provided in the issuer server 20b.

[0106] (3-4) Publication Information Collaboration Department 235 The function of the issuing information linking unit 235 according to the third embodiment is similar to the function of the issuing information linking unit 235 according to the second embodiment described with reference to FIG. 6, and therefore the description thereof will be omitted.

[0107] (3-5) Reception Desk 236 The function of the reception unit 236 according to the third embodiment is similar to the function of the reception unit 331 of the card management server 30 according to the first embodiment described with reference to FIG. 4, and therefore the description thereof will be omitted.

[0108] (3-6) Judgment section 237 The function of the judgment unit 237 according to the third embodiment is similar to the function of the judgment unit 332 of the card management server 30 according to the first embodiment described with reference to FIG. 4, and therefore the description thereof will be omitted.

[0109] (3-7) Activation control unit 238 The function of the activation control unit 238 according to the third embodiment is similar to the function of the activation control unit 333 of the card management server 30 according to the first embodiment described with reference to FIG. However, the function of the activation control unit 238 in the third embodiment differs from the function of the activation control unit 333 of the card management server 30 in the first embodiment in that the activation control unit 238 links activation information to the activation processing unit 234 of the issuer server 20b.

[0110] <3-4. Functional configuration of the card management server> The functional configuration of the issuer server 20b according to the third embodiment has been described above. Next, the functional configuration of the card management server 30b according to the third embodiment will be described with reference to Fig. 10. Fig. 10 is a block diagram showing an example of the functional configuration of the card management server 30b according to the third embodiment. As shown in FIG. 10, the card management server 30b includes a communication unit 310b, a storage unit 320b, and a control unit 330b.

[0111] (1) Communication department 310b The communication unit 310b receives the issuing information through communication with the issuer server 20b.

[0112] (2) Storage section 320b As shown in FIG. 10, the storage unit 320b includes a member attribute information storage unit 321 and an issuance information storage unit 323.

[0113] (2-1) Member attribute information storage unit 321 The function of the member attribute information storage unit 321 according to the third embodiment is similar to the function of the member attribute information storage unit 321 according to the first embodiment described with reference to FIG. 4, and therefore the description thereof will be omitted.

[0114] (2-2) Issue information storage unit 323 The function of the issuing information storage unit 323 according to the third embodiment is similar to the function of the issuing information storage unit 323 according to the second embodiment described with reference to FIG. 7, and therefore the description thereof will be omitted.

[0115] (3) Control unit 330b The control unit 330b includes a reception unit 331 as shown in FIG.

[0116] (3-1) Reception Section 331 The reception unit 331 according to the third embodiment has a function of receiving an input of issuing information. For example, the reception unit 331 receives an input of issuing information transmitted from the issuer server 20b and received by the communication unit 310b. Note that while the receiving unit 331 according to the second embodiment has a function of receiving an input of an individual URL, the receiving unit 331 according to the third embodiment does not have a function of receiving an input of an individual URL.

[0117] <3-5. Processing flow> The functional configuration of the card management server 30b according to the third embodiment has been described above. Next, a process flow according to the third embodiment will be described with reference to Fig. 11. Fig. 11 is a sequence diagram showing an example of a process flow according to the third embodiment.

[0118] As shown in FIG. 11, first, the card number assignment unit 231 of the issuer server 20b assigns a card number to the credit card to be issued (step S301). Next, the identification information generating unit 232 of the issuer server 20b generates an individual URL for each card number assigned by the card number assigning unit 231 (step S302). After the card number is assigned and the individual URL is generated, the correspondence information storage unit 223 of the issuer server 20b associates the card number with the corresponding individual URL and stores them as correspondence information (step S303). Next, the issuance information linking unit 235 of the issuer server 20b links (transmits) the issuance information stored in the corresponding information storage unit 223 from the communication unit 210b to the card management server 30b (step S304). The issuance information storage unit 323 of the card management server 30b stores the issuance information received by the communication unit 310b from the issuer server 20b (step S305).

[0119] The user performs an operation to read the individual URL on the user terminal 10 (step S306). Specifically, after the user receives the credit card that has been issued and mailed in an unactivated state, the user performs an operation on the user terminal 10 to read the individual URL from the credit card. When operation reception unit 151 receives an operation to read the individual URL from the user, read control unit 152 of user terminal 10 activates reading unit 130 and causes it to read the individual URL from the credit card (step S307). After reading the individual URL, the access control unit 153 of the user terminal 10 accesses the issuer server 20b from the address information indicated by the read individual URL (step S308). At the time of access, the access control unit 153 transmits the individual URL to the issuer server 20b via the communication unit 110 (step S309).

[0120] The accepting unit 236 of the issuer server 20b accepts the input of the individual URL transmitted from the user terminal 10 and received by the communication unit 210b (step S310). Next, the judgment unit 237 of the issuer server 20b judges whether or not the credit card corresponding to the individual URL accepted by the acceptance unit 236 is eligible for activation, based on the individual URL generated by the issuer server 20b and stored in the correspondence information storage unit 223 (step S311). Next, the activation control unit 238 of the issuer server 20b performs activation control processing based on the determination result by the determination unit 237 (step S312). Specifically, the activation control unit 238 communicates the determination result by the determination unit 237 of the issuer server 20b to the activation processing unit 234 of the issuer server 20b. At this time, if the determination result indicates that the credit card being determined is to be activated, the activation control unit 238 requests the activation processing unit 234 of the issuer server 20b to execute activation processing for the credit card determined to be to be activated. The activation processing unit 234 of the issuer server 20b executes activation processing based on activation information provided by the activation control unit 238 of the issuer server 20b (step S313). Specifically, when an activation request is received from the activation control unit 238 of the issuer server 20b, the activation processing unit 234 activates a credit card determined to be subject to activation as indicated by the activation information.

[0121] As described above, the issuer server 20b (card management device) according to the third embodiment includes a correspondence information storage unit (storage unit) 223 that stores an individual URL (identification information) different from the card number, which corresponds to the card number of a credit card (card) issued in an unactivated state upon receipt of an application from a user (applicant), a reception unit 236 that receives an individual URL acquired by a user terminal 10 (a terminal possessed by the applicant) from a credit card received by a user and transmitted from the user terminal 10, a determination unit 237 that determines that the credit card corresponding to the individual URL accepted by the reception unit 236 is to be activated if an individual URL matching the individual URL accepted by the reception unit 236 is present among the individual URLs stored in the correspondence information storage unit 223, and an activation control unit 238 that controls the execution of an activation process for the credit card determined to be to be activated.

[0122] With this configuration, the user can activate the received credit card simply by operating the user terminal 10 in the card management system 1b and reading the individual URL from the credit card. Therefore, the issuer server 20b according to the third embodiment enables a user to easily activate a card that he or she has received in an unactivated state.

[0123] <<4. Fourth embodiment>> Having described the third embodiment, the fourth embodiment will now be described with reference to Figs. In the following, descriptions that overlap with the first, second, and third embodiments will be omitted as appropriate.

[0124] <4-1. Card Management System Configuration> The card management system of the fourth embodiment includes a user terminal, an issuer server, and a card management server, similar to the card management system 1 of the first embodiment described with reference to Figure 1. In addition, the user terminal according to the fourth embodiment has the same functions as the user terminal 10 according to the first embodiment, so it will be described with the same reference numeral 10. Moreover, the issuer server according to the fourth embodiment will be described with a different reference numeral 20c because its functions are different from those of the issuer server 20 according to the first embodiment. Moreover, the card management server according to the fourth embodiment will be described with a different reference numeral 30c because its functions are different from those of the card management server 30 according to the first embodiment. In addition, in the card management system according to the fourth embodiment, the functions of the issuer server 20c and the card management server 30c are different from those of the issuer server 20 and the card management server 30 according to the first embodiment, so they will be described using different reference symbols 1c. In the above-mentioned third embodiment, an example was described in which the issuer server 20b has a function that allows the applicant to activate the credit card he or she received by himself or herself. In the above example, an example was described in which the identification information is an individual URL, but the present invention is not limited to such an example. In the fourth embodiment, an example will be described in which the identification information is a UID (Unique Identifier) ​​read from a credit card.

[0125] <4-2. Functional configuration of user terminal> The functional configuration of the user terminal 10 according to the fourth embodiment is the same as the functional configuration of the user terminal 10 according to the first embodiment described with reference to FIG. However, the function of the reading unit 130 of the user terminal 10 according to the fourth embodiment differs from that of the reading unit 130 of the user terminal 10 according to the first embodiment in that the reading unit 130 obtains a UID, not an individual URL, from a credit card. The reading unit 130 according to the fourth embodiment obtains a UID, for example, by reading a UID written in an IC chip provided on a credit card. Also, as in the case of an individual URL, the reading unit 130 may be able to obtain a UID by reading the UID from a two-dimensional code.

[0126] <4-3. Issuer server functional configuration> The functional configuration of the issuer server 20c according to the fourth embodiment will be described with reference to Fig. 12. Fig. 12 is a block diagram showing an example of the functional configuration of the issuer server 20c according to the fourth embodiment. As shown in FIG. 12, the issuer server 20c includes a communication unit 210c, a storage unit 220c, and a control unit 230c.

[0127] (1) Communication department 210c The communication unit 210c transmits (collaborates with) issuing information and receives corresponding information in communication with the card management server 30c. Furthermore, the communication unit 210c receives a UID during communication with the user terminal 10.

[0128] (2) Storage section 220c As shown in FIG. 12, the storage unit 220c includes a member attribute information storage unit 221, an issuing information storage unit 222, and a corresponding information storage unit 223.

[0129] (2-1) Member attribute information storage unit 221 The function of the member attribute information storage unit 221 according to the fourth embodiment is similar to the function of the member attribute information storage unit 221 according to the third embodiment described with reference to FIG. 9, and therefore the description thereof will be omitted.

[0130] (2-2) Issue information storage unit 222 The function of the issuing information storage unit 222 according to the fourth embodiment is similar to the function of the issuing information storage unit 222 according to the third embodiment described with reference to FIG. 9, and therefore the description thereof will be omitted.

[0131] (2-3) Correspondence information storage unit 223 The corresponding information storage unit 223 according to the fourth embodiment has the same function as the corresponding information storage unit 223 according to the third embodiment described with reference to FIG. However, the function of the correspondence information storage unit 223 according to the fourth embodiment is different from that of the correspondence information storage unit 223 according to the third embodiment in that the correspondence information storage unit 223 stores correspondence information acquired by a correspondence information acquisition unit 239 described later. The correspondence information storage unit 223 according to the fourth embodiment is an example of a storage unit.

[0132] (3) Control unit 230c As shown in FIG. 12, the control unit 230c includes a card number allocation unit 231, an activation processing unit 234, an issuance information linking unit 235, a reception unit 236, a determination unit 237, an activation control unit 238, and a correspondence information acquisition unit 239.

[0133] (3-1) Card Number Allocation Unit 231 The function of the card number allocating unit 231 according to the fourth embodiment is similar to the function of the card number allocating unit 231 according to the third embodiment described with reference to FIG. 9, and therefore the description thereof will be omitted.

[0134] (3-2) Activation processing unit 234 The function of the activation processing unit 234 according to the fourth embodiment is similar to the function of the activation processing unit 234 according to the third embodiment described with reference to FIG. 9, and therefore the description thereof will be omitted.

[0135] (3-3) Publication Information Collaboration Department 235 The function of the issuing information linking unit 235 according to the fourth embodiment is similar to the function of the issuing information linking unit 235 according to the third embodiment described with reference to FIG. 9, and therefore the description thereof will be omitted.

[0136] (3-4) Reception Desk 236 The function of the receiving unit 236 according to the fourth embodiment is similar to the function of the receiving unit 236 according to the third embodiment described with reference to FIG. However, the function of the reception unit 236 according to the fourth embodiment differs from that of the reception unit 236 according to the third embodiment in that the reception unit 236 receives input of a UID instead of an individual URL.

[0137] (3-5) Judgment section 237 The function of the determination unit 237 according to the fourth embodiment is similar to the function of the determination unit 237 according to the third embodiment described with reference to FIG. However, the function of the determination unit 237 according to the fourth embodiment differs from that of the determination unit 237 according to the third embodiment in that it determines whether or not a credit card is to be activated based on a UID rather than an individual URL. Specifically, the determination unit 237 according to the fourth embodiment determines whether or not the credit card corresponding to the UID accepted by the acceptance unit 236 is to be activated, based on the UID included in the correspondence information stored in the correspondence information storage unit 223. Specifically, the determination unit 237 checks whether or not a UID that matches the UID accepted by the acceptance unit 236 exists among the UIDs stored in the correspondence information storage unit 223. If the UID exists, the determination unit 237 determines that the credit card corresponding to the UID accepted by the acceptance unit 236 is to be activated. On the other hand, if the UID does not exist, the determination unit 237 determines that the credit card corresponding to the UID accepted by the acceptance unit 236 is not to be activated.

[0138] (3-6) Activation control unit 238 The function of the activation control unit 238 according to the fourth embodiment is similar to the function of the activation control unit 238 according to the third embodiment described with reference to FIG. 9, and therefore the description thereof will be omitted.

[0139] (3-7) Correspondence information acquisition unit 239 The corresponding information acquisition unit 239 has a function of acquiring corresponding information. For example, the corresponding information acquisition unit 239 acquires, from the card management server 30c, corresponding information in which a card number assigned by the issuer server 20c is associated with a UID acquired from a credit card corresponding to the card number. The UID is read in advance from an IC chip of the issued credit card by, for example, a business entity that issues the credit card.

[0140] <4-4. Functional configuration of card management server> The functional configuration of the issuer server 20c according to the fourth embodiment has been described above. Next, the functional configuration of the card management server 30c according to the fourth embodiment will be described with reference to Fig. 13. Fig. 13 is a block diagram showing an example of the functional configuration of the card management server 30c according to the fourth embodiment. As shown in FIG. 13, the card management server 30c includes a communication unit 310c, a storage unit 320c, and a control unit 330c.

[0141] (1) Communication department 310c The communication unit 310c receives issuing information and transmits (collaborates with) corresponding information in communication with the issuer server 20c.

[0142] (2) Storage section 320c As shown in FIG. 13, the storage unit 320c includes a member attribute information storage unit 321 and an issuance information storage unit 323.

[0143] (2-1) Member attribute information storage unit 321 The function of the member attribute information storage unit 321 according to the fourth embodiment is similar to the function of the member attribute information storage unit 321 according to the third embodiment described with reference to FIG. 10, and therefore the description thereof will be omitted.

[0144] (2-2) Issue information storage unit 323 The function of the issuing information storage unit 323 according to the fourth embodiment is similar to the function of the issuing information storage unit 323 according to the third embodiment described with reference to FIG. 10, and therefore the description thereof will be omitted.

[0145] (3) Control unit 330c As shown in FIG. 13, the control unit 330c includes a reception unit 331, an identification information acquisition unit 336, a corresponding information generation unit 337, and a corresponding information linking unit 338.

[0146] (3-1) Reception Section 331 The function of the receiving unit 331 according to the fourth embodiment is similar to the function of the receiving unit 331 according to the third embodiment described with reference to FIG. 10, and therefore the description thereof will be omitted.

[0147] (3-2) Identification information acquisition unit 336 The identification information acquisition unit 336 has a function of acquiring a UID. For example, the identification information acquisition unit 336 acquires a UID corresponding to each credit card issued by a business. As an example, the identification information acquisition unit 336 acquires a UID read by the business from an IC chip of each credit card.

[0148] (3-3) Correspondence information generation unit 337 The correspondence information generating unit 337 has a function of generating correspondence information. For example, the correspondence information generating unit 337 obtains the card number of each credit card from the issuance information received by the communication unit 310c, and generates the correspondence information by associating the UID obtained by the identification information obtaining unit 336 with the corresponding card number.

[0149] (3-4) Response Information Coordination Department 338 The corresponding information linking unit 338 has a function of linking the corresponding information to an external device. For example, the corresponding information linking unit 338 transmits (links) the corresponding information generated by the corresponding information generating unit 337 from the communication unit 310c to the issuer server 20c.

[0150] <4-5. Processing flow> The functional configuration of the card management server 30c according to the fourth embodiment has been described above. Next, a process flow according to the fourth embodiment will be described with reference to Fig. 14. Fig. 14 is a sequence diagram showing an example of a process flow according to the fourth embodiment.

[0151] As shown in FIG. 14, first, the card number assignment unit 231 of the issuer server 20c assigns a card number to the credit card to be issued (step S401). Next, the issuance information linking unit 235 of the issuer server 20c links (transmits) the issuance information from the communication unit 210c to the card management server 30c (step S402).

[0152] The issuance information storage unit 323 of the card management server 30c stores the issuance information received by the communication unit 310c from the issuer server 20c (step S403). Next, the identification information acquisition unit 336 of the card management server 30c acquires a UID for each credit card (step S404). For example, the identification information acquisition unit 336 acquires a UID corresponding to each card number indicated in the issuance information received by the communication unit 310c. After acquiring the UID, the correspondence information generating unit 337 of the card management server 30c generates correspondence information (step S405). For example, the correspondence information generating unit 337 acquires the card number of each credit card from the issuance information received by the communication unit 310c, and generates the correspondence information by associating the UID acquired by the identification information acquiring unit 336 with the corresponding card number. After generating the correspondence information, the correspondence information linking unit 338 of the card management server 30c links (transmits) the correspondence information from the communication unit 310c to the issuer server 20c (step S406).

[0153] The corresponding information acquisition unit 239 of the issuer server 20c acquires the corresponding information received by the communication unit 210c from the card management server 30c (step S407). The corresponding information storage unit 223 of the issuer server 20c stores the corresponding information acquired by the corresponding information acquisition unit 239 (step S408).

[0154] The user performs an operation to read the UID on the user terminal 10 (step S409). Specifically, after the user receives the credit card that has been issued and mailed in an unactivated state, the user performs an operation on the user terminal 10 to read the UID from the credit card. When the operation reception unit 151 receives an operation to read a UID from the user, the read control unit 152 of the user terminal 10 activates the reading unit 130 and causes it to read the UID from the credit card (step S410). After reading the UID, the access control unit 153 of the user terminal 10 transmits the UID read by the reading unit 130 to the card management server 30c via the communication unit 110 (step S411).

[0155] The accepting unit 236 of the issuer server 20c accepts the input of the UID transmitted from the user terminal 10 and received by the communication unit 210c (step S412). Next, the judgment unit 237 of the issuer server 20c judges whether or not the credit card corresponding to the UID accepted by the acceptance unit 236 is eligible for activation, based on the UID indicated by the card management server 30c correspondence information stored in the correspondence information memory unit 223 (step S413). Next, the activation control unit 238 of the issuer server 20c performs activation control processing based on the determination result by the determination unit 237 (step S414). Specifically, the activation control unit 238 communicates the determination result by the determination unit 237 of the issuer server 20c to the activation processing unit 234 of the issuer server 20c. At this time, if the determination result indicates that the credit card being determined is to be activated, the activation control unit 238 requests the activation processing unit 234 of the issuer server 20c to execute activation processing for the credit card determined to be to be activated. The activation processing unit 234 of the issuer server 20c executes activation processing based on activation information provided by the activation control unit 238 of the issuer server 20c (step S415). Specifically, when an activation request is received from the activation control unit 238 of the issuer server 20c, the activation processing unit 234 activates a credit card determined to be subject to activation as indicated by the activation information.

[0156] As described above, the issuer server 20c (card management device) according to the fourth embodiment includes a corresponding information memory unit (storage unit) 223 that stores a UID (identification information) different from the card number, which corresponds to the card number of a credit card (card) issued in an unactivated state upon receipt of an application from a user (applicant), a reception unit 236 that receives a UID acquired by a user terminal 10 (a terminal possessed by the applicant) from a credit card received by a user and transmitted from the user terminal 10, a determination unit 237 that determines that the credit card corresponding to the UID accepted by the reception unit 236 is to be activated if a UID matching the UID accepted by the acceptance unit 236 is present among the UIDs stored in the corresponding information memory unit 223, and an activation control unit 238 that controls the execution of an activation process for the credit card determined to be to be activated.

[0157] With this configuration, the user can activate the received credit card simply by operating the user terminal 10 in the card management system 1c and reading the UID from the credit card. Therefore, the issuer server 20c according to the fourth embodiment enables a user to easily activate a card that he or she has received in an unactivated state.

[0158] <<5. Modifications>> The embodiments of the present invention have been described above. Next, modified examples of the above-mentioned embodiments will be described. Each modified example described below may be applied to each embodiment alone, or may be applied to each embodiment in combination. Furthermore, each modified example may be applied in place of the configuration described in each embodiment, or may be applied in addition to the configuration described in each embodiment.

[0159] In the above-described fourth embodiment, an example has been described in which a UID is used instead of the individual URL used in the third embodiment. In the first and second embodiments as well as the third embodiment, a UID may be used instead of an individual URL.

[0160] In each of the above-described embodiments, the result of the activation process may be linked to the user terminal 10. For example, the issuer server in each embodiment transmits the result of the activation process to the user terminal 10 directly or via the card management server, and causes the user terminal 10 to display the result. The result of the activation process is, for example, information indicating whether or not the activation was successful.

[0161] In each of the above-described embodiments, a process for confirming the authenticity of the individual URL or UID transmitted from the user terminal 10 to the issuer server or card management server, and a process for confirming that the person requesting activation is the applicant for the credit card may be performed. Based on the results of these processes, the activation processing unit executes the activation process only if the individual URL or UID is genuine or if the person requesting activation is the applicant. This prevents unauthorized activation and impersonation by a third party who is not the applicant for the credit card, and can prevent unauthorized use of the credit card.

[0162] In each of the above-described embodiments, an example has been described in which the memory units 220, 220a, 220b, and 220c of the issuer servers 20, 20a, 20b, and 20c each include a member attribute information memory unit 221 and an issuance information memory unit 222, but the present invention is not limited to such an example. For example, the member attribute information memory unit 221 and the issuance information memory unit 222 may be integrated into a single memory unit. As an example, a member information memory unit in which the member attribute information memory unit 221 and the issuance information memory unit 222 are integrated may store information including the member attribute information and the issuance information as member information.

[0163] The above describes the modified embodiment of the present invention. Note that some or all of the functions of the card management system 1, 1a, 1b, 1c, the user terminal 10, the issuer server 20, 20a, 20b, 20c, and the card management server 30, 30a, 30b, 30c in the above-mentioned embodiment may be realized by a computer. In that case, a program for realizing the functions may be recorded in a computer-readable recording medium, and the program recorded in the recording medium may be read into a computer system and executed to realize the functions. Note that the "computer system" here includes hardware such as an OS and peripheral devices. Furthermore, the "computer-readable recording medium" refers to portable media such as a flexible disk, a magneto-optical disk, a ROM, a CD-ROM, and a storage device such as a hard disk built into a computer system. Furthermore, the "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. Furthermore, the above program may be for realizing part of the functions described above, or may be capable of realizing the functions described above in combination with a program already recorded in a computer system, or may be realized using a programmable logic device such as an FPGA (Field Programmable Gate Array).

[0164] Although the embodiment of the present invention has been described in detail above with reference to the drawings, the specific configuration is not limited to the above, and various design changes, etc. are possible within the scope that does not deviate from the gist of the present invention. [Explanation of symbols]

[0165] 1, 1a, 1b, 1c... card management system, 10... user terminal, 20, 20a, 20b, 20c... issuer server, 30, 30a, 30b, 30c... card management server, 110... communication unit, 120... input unit, 130... reading unit, 140... memory unit, 150... control unit, 151... operation reception unit, 152... reading control unit, 153... access control unit, 154... output control unit, 160... output unit, 210, 210a, 210b, 210c... communication unit, 220, 220a, 220b, 220c... memory unit, 221... member attribute information memory unit, 222... issuance information memory unit, 223... correspondence information memory unit, 230, 230a, 230b, 230c... control unit, 231... card number allocation unit, 232... identification information information generation unit, 233... identification information linking unit, 234... activation processing unit, 235... issuance information linking unit, 236... reception unit, 237... judgment unit, 238... activation control unit, 310, 310a, 310b, 310c... communication unit, 320, 320a, 320b, 320c... storage unit, 321... member attribute information storage unit, 322... identification information storage unit, 323... issuance information storage unit, 324... corresponding information storage unit, 330, 330a, 330b, 330c... control unit, 331... reception unit, 332... judgment unit, 333... activation control unit, 334... card number acquisition unit, 335... identification information generation unit, 336... identification information acquisition unit, 337... corresponding information generation unit, 338... corresponding information linking unit, NW... network

Claims

1. a storage unit that stores identification information corresponding to a card number of a card to be issued in an unactivated state upon receipt of an application from an applicant, the identification information being different from the card number; a reception unit that receives the identification information acquired from the card received by the applicant by a terminal held by the applicant and transmitted from the terminal; a determination unit that, when identification information stored in the storage unit matches the identification information accepted by the acceptance unit, determines that the card corresponding to the identification information accepted by the acceptance unit is to be activated; and an activation control unit that controls execution of an activation process for the card that has been determined to be the activation target; A card management device comprising:

2. The activation control unit requests an issuer server to execute an activation process for the card determined to be the activation target, in cooperation with the determination result by the determination unit.

2. The card management device according to claim 1.

3. the identification information is generated for each of the card numbers by a server of the issuer; The storage unit stores the identification information transmitted from the issuer's server to the card management device.

3. The card management device according to claim 2.

4. an identification information generating unit that generates the identification information for each of the card numbers; Further equipped with the storage unit stores the card number transmitted from the issuer's server to the card management device in association with the identification information generated by the identification information generation unit; 3. The card management device according to claim 2.

5. the card management device is an issuer server; an activation processing unit that executes an activation process for the card determined to be the activation target in response to a request from the activation control unit; The card management device according to claim 1 , further comprising:

6. a card number assignment unit that assigns the card number; an identification information generating unit that generates the identification information for each of the assigned card numbers; Further equipped with the storage unit stores the card number assigned by the card number assignment unit and the identification information generated by the identification information generation unit in association with each other; 6. The card management device according to claim 5.

7. the identification information includes address information for accessing the card management device from the terminal and an identifier unique to the card number; 6. The card management device according to claim 2 or 5.

8. a card number assignment unit that assigns the card number; a correspondence information acquiring unit that acquires correspondence information in which the assigned card number is associated with identification information acquired from the card corresponding to the card number; Further equipped with The storage unit stores the corresponding information acquired by the corresponding information acquisition unit.

6. The card management device according to claim 5.

9. The identification information is a UID (Unique Identifier) ​​read from the card.

9. The card management device according to claim 8.

10. a storage step of storing identification information, different from the card number, corresponding to the card number of a card to be issued in an unactivated state upon receipt of an application from an applicant; a receiving step of receiving the identification information acquired from the card received by the applicant by a terminal held by the applicant and transmitted from the terminal; a determination step of determining that the card corresponding to the identification information received in the reception step is to be activated when the identification information stored in the storage step matches the identification information received in the reception step; an activation control process for controlling execution of an activation process for the card determined to be the activation target; A card management method executed by a computer, comprising:

11. Computer, a storage means for storing identification information corresponding to a card number of a card to be issued in an unactivated state upon receipt of an application from an applicant, the identification information being different from the card number; a receiving means for receiving the identification information acquired from the card received by the applicant by a terminal held by the applicant and transmitted from the terminal; a determination means for determining that the card corresponding to the identification information accepted by the acceptance means is to be activated when the identification information stored in the storage means matches the identification information accepted by the acceptance means; an activation control means for controlling the execution of an activation process for the card determined to be the activation target; A program to function as a

Images