JP7500841B2 - Information management system, information management method, and computer program - Google Patents

Description

The present invention relates to technology for registering customer information for payment media.

In recent years, cashless payments have become more widespread, and the number of people applying for payment media used in cashless payments is also increasing. For this reason, technologies related to the processing at the time of application for payment media have also been proposed. For example, Patent Document 1 discloses a technology for easily providing a payment card that can be used as an alternative to conventional credit cards.

JP 2011-192293 A

When applying for a payment medium, a large amount of customer information is required. As a result, it was a burden for users to input all of the requested customer information. In particular, for users who had already registered customer information for a payment medium, it was a heavy burden to have to input all of the customer information again when registering a new payment medium. Furthermore, after customer information was registered, it was sometimes necessary to switch from the previously used payment medium to the new payment medium.

In view of the above circumstances, the present invention aims to provide a technology that can reduce the effort required by users to apply for a payment medium.

One aspect of the present invention is an information management system that includes a storage unit that stores medium information of a first payment medium that is a payment medium used for payment and has already been issued to a user, and a control unit that, when an application for a new payment medium, a second payment medium, is made in association with the first payment medium, instructs a token management device that stores a token associated with the first payment medium to newly associate the second payment medium with the token in place of the first payment medium and store the token.

One aspect of the present invention is an information management system that includes a storage unit that stores first attribute information and second attribute information, which are attribute information related to a user of a payment medium used for payment, and a control unit that, when applying for a new payment medium, transmits data of a normal registration screen, which is a screen requesting registration of the first attribute information and the second attribute information, to a user whose first attribute information is not registered in the storage unit, and transmits data of a simplified registration screen, which is a screen requesting registration of the second attribute information, to a user whose first attribute information is already registered in the storage unit.

In one aspect of the present invention, in the information management system described above, the control unit instructs a token management device that stores tokens associated with payment media already issued to the user to associate the newly issued payment medium with the token for the new payment medium.

One aspect of the present invention is an information management method in which an information management system having a storage unit that stores medium information of a first payment medium that is a payment medium used for payment and has already been issued to a user, when an application for a new payment medium, a second payment medium, is made in association with the first payment medium, instructs a token management device that stores a token associated with the first payment medium to newly associate the second payment medium with the token in place of the first payment medium and store the token.

One aspect of the present invention is an information management method in which an information management system having a storage unit that stores first attribute information and second attribute information, which are attribute information related to a user of a payment medium used for payment, transmits data of a normal registration screen, which is a screen requesting registration of the first attribute information and the second attribute information, to a user whose first attribute information is not registered in the storage unit, when applying for a new payment medium, and transmits data of a simplified registration screen, which is a screen requesting registration of the second attribute information, to a user whose first attribute information is already registered in the storage unit.

One aspect of the present invention is a computer program for causing a computer to function as the above-mentioned information management system.

This invention makes it possible to reduce the effort required by users to apply for a payment medium.

1 is a schematic block diagram showing the system configuration of a payment system 100. FIG. 2 is a schematic block diagram showing an outline of the functional configuration of a user terminal 10. FIG. 2 is a schematic block diagram showing an outline of the functional configuration of an information management server 30. FIG. FIG. 11 is a diagram showing a specific example of a customer information table. A schematic block diagram showing an outline of the functional configuration of the token management server 40. FIG. 11 is a diagram showing a specific example of a token table. 11 is a sequence chart showing a specific example of the process flow when registering customer information for a new payment medium using a user terminal 10. 13 is a sequence chart showing a specific example of a process flow after a post-stage process is completed.

Hereinafter, specific configuration examples of the present invention will be described with reference to the drawings.
FIG. 1 is a schematic block diagram showing the system configuration of a payment system 100. The payment system 100 includes a user terminal 10, a store terminal 20, an information management server 30, a token management server 40, and a linkage server 50. In the payment system 100, a payment is realized using one or more types of payment protocols. In the payment system 100, a payment is made using a payment medium issued to a user in advance upon application by the user. For example, when a postpaid payment medium is used, a payment process is first performed using the payment medium, and then a payment is made according to the payment medium. When making a payment, a physical medium carried by the user (hereinafter referred to as a "user medium") is used. Also, when making a payment or making a settlement, information issued in association with the payment medium (hereinafter referred to as "medium information") is used. For example, when the payment medium is a credit card, the medium information is a real card number (e.g., Funding Primary Account Number: FPAN), and a card medium such as a plastic card on which the real card number of the credit card is recorded may be used as the user medium, or an information device such as a smartphone on which a token corresponding to the real card number is recorded may be used. As a specific example of a payment protocol, a payment may be made using a card medium such as a credit card. In this case, the payment medium is a credit card, and the actual card number (a specific example of medium information) recorded on the card medium (a specific example of a user medium) of the credit card owned by the user is read by the store terminal 20, and processing related to the payment is executed in cooperation with the information management server 30. Then, processing related to the settlement is executed by the information management server 30.

As a specific example of a payment protocol, a credit card payment may be made using a token. In this case, the token recorded on the user terminal 10 (a specific example of a user medium) owned by the user is read by the store terminal 20. The token read by the store terminal 20 is converted into medium information (e.g., a real card number) registered in accordance with the token in the token management server 40. The medium information (real card number) is sent to the information management server 30, and processing related to the payment is executed. Then, processing related to the payment is executed by the information management server 30.

Although two specific examples have been given above, the payment protocol implemented in the payment system 100 does not have to be limited to those mentioned above. For example, a payment protocol using electronic value may be used, or a payment protocol for a debit card may be used. The user terminal 10 is one specific example of a user medium that is a medium used when a user makes a payment based on a payment protocol. In the following explanation, as a specific example of the payment system 100, a payment system 100 in which a payment protocol for payment using a card medium such as a credit card and a payment protocol for payment using a token are implemented will be explained.

The user terminal 10, the store terminal 20, the information management server 30, the token management server 40, and the link server 50 can all communicate via a network 60. The network 60 is, for example, a wide area communication network such as the Internet. The network 60 may be a network using wireless communication or a network using wired communication. The network 60 may be configured by combining multiple networks. Note that the network 60 is merely a specific example of a network for realizing communication between each device, and other configurations may be adopted as the network for realizing communication between each device. For example, communication between specific devices may be realized using a network different from the network used for communication between other devices. Specifically, communication between the store terminal 20 and the information management server 30 and communication between the information management server 30 and the token management server 40 may be realized using a network different from the network used for communication between other devices.

Figure 2 is a schematic block diagram showing an outline of the functional configuration of the user terminal 10. The user terminal 10 is configured using a portable information processing device such as a smartphone, tablet terminal, mobile phone, smart watch, or portable game console. The user terminal 10 is equipped with a function for realizing a payment protocol that can be used in the payment system 100. The payment protocol function may be implemented in the user terminal 10 by hardware, or may be implemented by installing software. The user terminal 10 includes a first communication unit 11, a second communication unit 12, an input unit 13, a display unit 14, an identification information storage unit 15, a token storage unit 16, and a control unit 17.

The first communication unit 11 is a communication device such as a network interface. The first communication unit 11 is communicatively connected to the network 60 using a predetermined protocol. The first communication unit 11 may be configured using, for example, a device that communicates with a base station device using a mobile communication protocol. The first communication unit 11 may be configured using, for example, a device that communicates using wireless LAN (Local Area Network) technology such as WiFi (registered trademark). The first communication unit 11 communicates data with other devices via the network 60 according to the control of the control unit 17.

The second communication unit 12 is a communication device that performs short-range wireless communication. The second communication unit 12 communicates with the store terminal 20 using a predetermined protocol. The second communication unit 12 may communicate using technologies such as Near Field Communication (NFC) or RFID. The second communication unit 12 may communicate using infrared communication technology, for example. Any short-range wireless communication technology may be applied to the second communication unit 12 as long as it is possible to communicate with the store terminal 20.

The input unit 13 is configured using existing input devices such as a keyboard, a pointing device (mouse, tablet, etc.), buttons, a touch panel, etc. The input unit 13 is operated by the user when inputting the user's instructions to the user terminal 10. The input unit 13 may be an interface for connecting the input device to the user terminal 10. In this case, the input unit 13 inputs an input signal generated in the input device in response to the user's input to the user terminal 10.

The display unit 14 is an image display device such as a liquid crystal display, an organic EL (Electro Luminescence) display, or an electrophoretic display. The display unit 14 displays an image according to the control of the control unit 17. The display unit 14 may be an interface for connecting an image display device to the user terminal 10. In this case, the display unit 14 generates a video signal for displaying an image according to the control of the control unit 17, and outputs the video signal to the image display device connected to the display unit 14.

The identification information storage unit 15 is configured using a storage device such as a magnetic hard disk device or a semiconductor storage device. The identification information storage unit 15 stores identification information used in the user terminal 10 (hereinafter referred to as "terminal identification information"). The terminal identification information may be an identification number used by an application installed in the user terminal 10 to make a payment using a payment medium.

The token storage unit 16 is configured using a storage device such as a magnetic hard disk device or a semiconductor storage device. The token storage unit 16 stores a token. A token is data used in payment using the user terminal 10. A token is data different from medium information (e.g., physical card number (FPAN)) used in payment and settlement processing by the information management server 30. The token may be, for example, a value issued by the token management server 40 in association with the FPAN. In this case, the token may be a Digitized Primary Account Number (DPAN).

The control unit 17 is configured using a processor such as a Central Processing Unit (CPU) and a memory. The control unit 17 functions as a payment control unit 171 and an application control unit 172 by the processor executing a specific program.

The payment control unit 171 performs processing related to payment with the store terminal 20. The payment control unit 171 communicates with the store terminal 20, for example, via the second communication unit 12, and when it receives a request for a token using a specified communication protocol, it reads out the token stored in the token storage unit 16 of its own device and transmits it to the store terminal 20. When the payment control unit 171 subsequently receives a payment completion notification from the store terminal 20, it causes the display unit 14 to display an image indicating that the payment has been completed. Such processing by the payment control unit 171 is merely one specific example, and any processing for making a payment using a payment medium may be implemented.

The application control unit 172 executes processing to apply for a new payment medium. A new payment medium is a payment medium that is not available to the user before the application process is performed, and that becomes available to the user after the application process is performed. The application control unit 172, for example, displays a screen for inputting information requested by the information management server 30 on the display unit 14, and transmits data input by the user via the input unit 13 to the information management server 30.

The store terminal 20 is configured using an information processing device such as a smartphone, tablet terminal, or dedicated terminal. The store terminal 20 is used by store staff or customers themselves. When the store terminal 20 acquires information related to the payment medium from a user medium such as a user terminal 10, the store terminal 20 performs payment processing using the acquired information related to the payment medium. For example, if the user medium is the user terminal 10, the store terminal 20 may acquire a token recorded in the user terminal 10 and perform payment processing. For example, if the user medium is a plastic card of a credit card, the store terminal 20 may read the actual card number recorded on the plastic card and perform payment processing.

Figure 3 is a schematic block diagram showing an outline of the functional configuration of the information management server 30. The information management server 30 is configured using an information processing device such as a server device or a mainframe. The information management server 30 includes a communication unit 31, a customer information storage unit 32, a payment information storage unit 33, and a control unit 34.

The communication unit 31 is a communication device such as a network interface. The communication unit 31 is communicatively connected to the network 60 using a predetermined protocol. The communication unit 31 communicates data with other devices via the network 60 under the control of the control unit 34.

The customer information storage unit 32 is configured using a storage device such as a magnetic hard disk drive or a semiconductor storage device. The customer information storage unit 32 stores a customer information table. FIG. 4 is a diagram showing one specific example of a customer information table. The customer information table has multiple customer information records. The customer information record has values for customer identification information, image number, first attribute information, second attribute information, and medium information. The customer identification information is identification information of a customer who is a user of the payment medium. The image number is a specific example of medium identification information. The image number may be, for example, a 20-digit number.

The first attribute information is information about the attributes of a customer. The first type attribute information is information registered when applying for a payment medium that can be used with relatively little customer information among multiple types of payment media. For example, the first attribute information may be information registered by a customer when making available a payment medium with a relatively low usage limit. The first attribute information may include nine items, such as the customer's name, address, gender, age, and information about the financial institution used for payment.

The second attribute information is information about the attributes of the customer. The first attribute information and the second attribute information are information about different items. However, some of them may overlap. The second attribute information is part of the information registered when applying for a payment medium that requires relatively more customer information among multiple types of payment media. For example, the first attribute information and the second attribute information are the information registered by the customer when making available a payment medium with a relatively high credit limit. In other words, when both the first attribute information and the second attribute information are available, an application for the above-mentioned payment medium is made. The second attribute information may include 26 items, such as the customer's annual income and whether or not they have a mortgage.

The medium information is identification information of the payment medium. The medium information may be, for example, a multi-digit number. For example, if the payment medium is a credit card, the physical card number (FPAN) corresponds to the medium information.

Returning to FIG. 3, the explanation will continue. The payment information storage unit 33 is configured using a storage device such as a magnetic hard disk drive or a semiconductor storage device. The payment information storage unit 33 stores information related to payments made using a payment medium. The payment information storage unit 33 includes, for example, the date and time the payment was made, information about the store where the payment was made, the product that was the subject of the payment, and information about the payment medium used for the payment.

The control unit 34 is configured using a processor such as a CPU and a memory. The control unit 34 functions as a payment control unit 341 and an application control unit 342 by the processor executing a specific program.

The payment control unit 341 performs processing related to payments using a payment medium. When the payment control unit 341 receives a token from the store terminal 20, it sends the received token to the token management server 40 and requests medium information. When the payment control unit 341 receives medium information in response to the request, it uses the received medium information to record information related to the payment at the store terminal 20 in the payment information storage unit 33. The payment control unit 341 then notifies the store terminal 20 that the payment has been completed.

The application control unit 342 performs processing related to applications for new payment media. When the application control unit 342 receives first attribute information and second attribute information from an information device such as the user terminal 10, it registers the received information in the customer information storage unit 32. The application control unit 342 may provide an interface (e.g., a screen with input fields) for inputting the first attribute information and second attribute information to the information device such as the user terminal 10.

Figure 5 is a schematic block diagram showing an outline of the functional configuration of the token management server 40. The token management server 40 may be configured as a device equivalent to a Token Vault, for example. The token management server 40 is configured using an information processing device such as a server device or a mainframe. The token management server 40 includes a communication unit 41, a token storage unit 42, and a control unit 43.

The communication unit 41 is a communication device such as a network interface. The communication unit 41 is communicatively connected to the network 60 using a predetermined protocol. The communication unit 41 communicates data with other devices via the network 60 under the control of the control unit 43.

The token storage unit 42 is configured using a storage device such as a magnetic hard disk device or a semiconductor storage device. The token storage unit 42 stores a token table. FIG. 6 is a diagram showing one specific example of a token table. The token table has multiple token records. The token record has media information and each value of the token. The token record has the value of the token issued for each piece of media information. The media information is, for example, an FPAN, and the token is, for example, a DPAN.

Returning to FIG. 5 for further explanation, the control unit 43 is configured using a processor such as a CPU and a memory. The control unit 43 functions as a token control unit 431 and a registration control unit 432 by the processor executing a specific program.

The token control unit 431 receives a request for media information associated with a token from a specific device, such as the information management server 30. The token control unit 431 reads the media information associated with the token from the token storage unit 42. The token control unit 431 then transmits the media information to the device that made the request.

When a registration process for new media information is performed on the information management server 30, if a request is received to change the media information associated with a token, the registration control unit 432 changes the media information in the token record in response to the request.

Next, the linking server 50 will be described. The linking server 50 may be configured as a server that links with an application installed in the user terminal 10, for example. The linking server 50 is configured using an information processing device such as a server device or a mainframe.

The linking server 50 includes a processor, memory, and auxiliary storage device. The auxiliary storage device of the linking server 50 stores the terminal identification information stored in the user terminal 10 in association with information for identifying the payment medium used in the user terminal 10 (hereinafter referred to as "medium identification information"). The medium identification information may be, for example, an image number issued when registering customer information for a new payment medium. The image number is registered in the information management server 30 in association with the medium information of the payment medium. When the linking server 50 receives the terminal identification information from the user terminal 10, it reads out the medium identification information stored in association with the terminal identification information, and transmits it to the user terminal 10.

Figure 7 is a sequence chart showing a specific example of the process flow when applying for a new payment medium using the user terminal 10. The user operates the input unit 13 of the user terminal 10 to instruct the user terminal 10 to apply for a new payment medium. In response to the user's input, the user terminal 10 transmits terminal identification information to the linking server 50 and inquires about the image number (step S101). When the linking server 50 receives the inquiry for the image number, it reads out the medium identification information stored in association with the terminal identification information. The linking server 50 then transmits the read out medium identification information (e.g., the image number) to the user terminal 10 as a response (step S102).

When the user terminal 10 acquires the medium identification number from the link server 50, it generates application request information including the acquired medium identification number. Then, the user terminal 10 transmits the application request information to the information management server 30 (step S103). The following description explains an example of a process in which an image number is used as the medium identification number.

When the application control unit 342 of the information management server 30 receives the application request information from the user terminal 10, it reads out the image number from the received application request information. The application control unit 342 searches the customer information table for the first attribute information associated with the read out image number (step S104).

If the corresponding first attribute information is not found (step S105-NO), the application control unit 342 sends data of a normal registration screen to the user terminal 10 (step S106). The normal registration screen is a screen that requests the user to enter the first attribute information and the second attribute information. The normal registration screen may be provided with, for example, input fields for inputting the first attribute information and the second attribute information, respectively. After the normal registration screen is sent to the user terminal 10, processing for applying for a payment medium is carried out in the same manner as before.

If the corresponding first attribute information is found (step S105-YES), the application control unit 342 reads and acquires the searched first attribute information (step S107). Then, the application control unit 342 generates data for a simple registration screen and transmits the data for the simple registration screen to the user terminal 10 (step S108). The simple registration screen is a screen that requests the second attribute information from the user. The simple registration screen has, for example, input fields for inputting the first attribute information and the second attribute information, and the input field for the first attribute information may already have the value of the first attribute information read out in step S107 input. The values of these first attribute information may be set to be changeable.

When the application control unit 172 of the user terminal 10 receives the data of the simple registration screen, it displays the received simple registration screen on the display unit 14 (step S109). The application control unit 172 accepts changes to the first attribute information and new input of second attribute information (step S110). The application control unit 172 transmits the information entered in each input field on the simple registration screen (first attribute information and second attribute information) to the information management server 30 (step S111). At this time, in this embodiment, if no changes have been made to the first attribute information by the user, the first attribute information read out in step S107 is transmitted as is to the information management device 30.

The application control unit 342 of the information management server 30 generates a new customer information record and newly registers the customer identification information, image number (medium identification number), and medium information. The application control unit 342 registers the first attribute information and the second attribute information transmitted from the user terminal 10 in the newly generated customer information record described above (steps S112, S113). At this time, the application control unit 342 may also register information indicating whether the registration was simple or normal, in association with the customer information record. Simple registration is registration performed without requesting the user to newly input the first attribute information, and indicates, for example, registration performed using a simple registration screen. Normal registration is registration performed by requesting the user to newly input the first attribute information and the second attribute information, and indicates, for example, registration performed using a normal registration screen. Then, the application control unit 342 executes the subsequent process (step S114). The subsequent process is, for example, processing such as foreign credit inquiries and credit judgments.

Figure 8 is a sequence chart showing a specific example of the process flow after the end of the latter process. In the latter process, when the review for issuing a new payment medium to the user is completed successfully, the application control unit 342 of the information management server 30 acquires a review completion notice (step S201). The review completion notice is a notice indicating that the above review has been completed successfully. The review completion notice may be transmitted to the information management server 30 from another information processing device, may be input to the information management server 30 by the administrator of the information management server 30 operating an input device, or may be notified in other manners. When the application control unit 342 acquires the review completion notice, it determines whether the notified review was a simplified registration (step S202). For example, it may be determined whether the simplified registration was based on the identification information included in the review completion notice. Specific examples of such identification information may include customer identification information, image number, medium information, etc.

If it is a normal registration (step S202-NO), the application control unit 342 executes normal link processing (step S203). Normal link processing is processing for linking payments, etc. by sending medium information of a newly issued payment medium to other devices as necessary. For example, normal link processing may be processing for requesting the token management server 40 to generate a new token record.

If it is a simplified registration (step S202-YES), the application control unit 342 reads out the media information from the customer information record used when reading out the first attribute information in the processing of step S107. The media information read out here is referred to as "old media information" in the following explanation. The application control unit 342 also obtains media information for the new payment medium for which screening has been completed. This media information is referred to as "new media information" in the following explanation. The application control unit 342 generates a media information update notification that includes the old media information and the new media information. The application control unit 342 sends the generated media information update notification to the token management server 40 (step S204).

When the registration control unit 432 of the token management server 40 receives the media information update notification, it searches for a token record that includes the old media information included in the received media information update notification. The registration control unit 432 changes the media information included in the searched token record to the new media information (step S205).

In the payment system 100 configured in this manner, a user who has already registered first attribute information can complete the application process for a new payment medium by inputting less information than usual. Specifically, a new payment medium can be applied for by inputting second attribute information without newly inputting first attribute information. This reduces the effort required by the user to apply for a payment medium.

In addition, in the payment system 100, when a token has already been registered and used in association with old medium information, the old medium information associated with that token is updated to new medium information. As a result, the user can continue to use the token associated with the old medium information without making any particular changes. This makes it possible to improve convenience for users who have been issued a new payment medium.

(Modification)
The simplified registration screen may be a screen provided with an input field for inputting the second attribute information and no input field for the first attribute information.The simplified registration screen may be a screen provided with an input field for inputting the second attribute information and displaying the first attribute information as a fixed value (a value that cannot be changed) in a field similar to the input field.

The user terminal 10 as the user medium used for payment and the user terminal 10 used to apply for the payment medium may be different devices. On the other hand, the user terminal 10 as the user medium used for payment and the user terminal 10 used to apply for the payment medium may be the same device.

The user terminal 10 used to apply for the payment medium may not be owned by the individual user who is applying, but may be a shared terminal device shared by multiple people for the application. For example, the user terminal 10 used to apply may be an application terminal device prepared by a non-user, such as a campaign organizer, when an application campaign is held at a store or the like. In this case, when generating application request information, necessary information (e.g., medium information already used by the user, medium identification information, terminal identification information, etc.) may be transmitted from the user terminal 10 possessed by the applicant user to the application terminal device by means of short-range wireless communication or the like. In addition, the above-mentioned necessary information may be encoded into an image such as a two-dimensional barcode and passed from the user terminal 10 to the application terminal device via an imaging device.

Processing equivalent to the application process shown in FIG. 7 may be performed for an application using paper media, rather than an application using an information processing device such as the user terminal 10 or the information management server 30. Even in this case, the information management server 30 may be configured to perform the processing from step S202 onwards after the screening management notice is obtained (after step S201). In addition, when a user desires to link tokens, the old medium information and new medium information may be obtained by the information management server 30 as a result of the user operating an information processing device such as the user terminal 10. In this case, the information management server 30 may perform processing equivalent to step S204 using the obtained old medium information and new medium information.

The registration process for old media information may be carried out at a financial institution such as a bank. In this case, if the user attempting to carry out the registration process already has an account at the financial institution, part of the user's registration process may be simplified or omitted by using attribute information already registered at the financial institution in association with the account.

The information management server 30 may be implemented as an information management system using multiple information processing devices. For example, the control unit 34 functioning as the payment control unit 341 and the control unit 34 functioning as the application control unit 342 may each be implemented in a different information processing device. In addition, the customer information storage unit 32 and the payment information storage unit 33 may each be implemented in the same storage device, or may each be implemented in a different storage device.

The information management server 30 and the token management server 40 may be implemented in the same device. Also, a part of the information management server 30 and the token management server 40 may be implemented in the same device, or a part of the information management server 30 and a part of the token management server 40 may be implemented in the same device, or a part of the information management server 30 and a part of the token management server 40 may be implemented in the same device.

In place of the user terminal 10, a recording medium on which a token is recorded may be used as the user medium used for payment. For example, a card-type recording medium may be used as the user medium instead of the user terminal 10. In this case, a reading device for reading the token from the card-type recording medium must be provided in the store terminal 20. Similarly, an appliance equipped with a recording medium such as an IC chip may be used as the user medium. Specific examples of such appliances include accessories such as watches and rings, mobile phone cases, etc. In this case, a reading device for reading the token from the recording medium provided in the appliance must be provided in the store terminal 20.

The payment system 100 may be applied not only to payments in physical stores, but also to payments via communication (e.g., television shopping, online shopping, etc.).
The identification information storage unit 15 of the user terminal 10 may store medium identification information instead of the terminal identification information. In this case, the processes from step S103 onward may be executed without communication between the user terminal 10 and the linking server 50 (without executing the processes of steps S101 and S102).

The above describes an embodiment of the present invention in detail with reference to the drawings, but the specific configuration is not limited to this embodiment, and includes designs that do not deviate from the gist of the present invention.

100...Payment system, 10...User terminal, 11...First communication unit, 12...Second communication unit, 13...Input unit, 14...Display unit, 15...Identification information storage unit, 16...Token storage unit, 17...Control unit, 171...Payment control unit, 172...Application control unit, 20...Store terminal, 30...Information management server (information management system), 31...Communication unit, 32...Customer information storage unit, 33...Payment information storage unit, 34...Control unit, 341...Payment control unit, 342...Application control unit, 40...Token management server, 41...Communication unit, 42...Token storage unit, 43...Control unit, 431...Token control unit, 432...Registration control unit, 50...Linked server, 60Network

Claims (4)

a storage unit that stores first attribute information and second attribute information, which are attribute information related to a user of a payment medium used for payment;
a control unit that, when applying for a new payment medium, transmits data of a normal registration screen, which is a screen requesting registration of the first attribute information and the second attribute information, to a user whose first attribute information is not registered in the storage unit, and transmits data of a simplified registration screen, which is a screen requesting registration of the second attribute information, to a user whose first attribute information is already registered in the storage unit;
An information management system comprising: The information management system of claim 1, wherein the control unit instructs a token management device that stores tokens associated with payment media already issued to the user to associate the newly issued payment medium with the token for the new payment medium. An information management system including a storage unit for storing first attribute information and second attribute information, which are attribute information relating to a user of a payment medium used for payment,
An information management method in which, when applying for a new payment medium, data of a normal registration screen, which is a screen requesting registration of the first attribute information and the second attribute information, is sent to a user whose first attribute information is not registered in the memory unit, and data of a simplified registration screen, which is a screen requesting registration of the second attribute information, is sent to a user whose first attribute information is already registered in the memory unit. A computer program for causing a computer to function as the information management system according to claim 1 or 2.

Images