Information processing apparatus, information processing method, and program

Abstract

To easily register a credit card to the account of a user.SOLUTION: An information processing device capable of communicating with an external server, the information processing device comprising: a storage unit configured to store first information that is identity verification information of a user of a credit card; an accepting unit configured to accept a registration request of the credit card to the external server; an acquiring unit configured to acquire second information that is the identity verification information of the user from the external server; and a card information providing unit configured to provide information related to the credit card to the external server when the first information matches the second information.SELECTED DRAWING: Figure 8

Description

[Technical Field]

[0001] The present invention relates to an information processing device, an information processing method, and a program. [Background technology]

[0002] Conventionally, there is known an electronic payment service in which code information is displayed on a user terminal device owned by a user and the code information is read by a store terminal device installed in a store to execute electronic payment. Patent Document 1 also proposes an electronic payment system in which credit cards that can be used in the electronic payment service are registered in a payment server. [Prior art documents] [Patent documents]

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

[0004] However, in the electronic payment system described in Patent Document 1, when registering a credit card to a user's account, the user must take the time to input credit card information, which can be a cumbersome input task for the user.

[0005] The present invention has been made in consideration of the above circumstances, and one of its objects is to provide an information processing device, an information processing method, and a program that can easily register a credit card to a user's account. [Means for solving the problem]

[0006] One aspect of the present invention is an information processing device capable of communicating with an external server, comprising: a memory unit that stores first information, which is personal identification information of a credit card user; a reception unit that receives a request to register the credit card to the external server; an acquisition unit that acquires second information, which is personal identification information of the user, from the external server; and a card information providing unit that provides information about the credit card to the external server if the first information and the second information match. [Effects of the Invention]

[0007] According to one aspect of the present invention, it is possible to provide an information processing device, an information processing method, and a program that allow a credit card to be easily registered to a user's account. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram illustrating an example of a configuration for realizing an electronic payment service. [Figure 2] This is a sequence diagram (pattern 1) illustrating the general flow of electronic payment. [Figure 3] This is a sequence diagram (pattern 2) illustrating the general flow of electronic payment. [Figure 4] FIG. 2 is a configuration diagram of a payment server 100. [Figure 5] FIG. 10 is a diagram showing an example of the contents of user information 172. [Figure 6] FIG. 10 is a diagram showing an example of the contents of affiliated store / store information 176. [Figure 7] FIG. 2 is a diagram illustrating the configuration of a user terminal device 200. [Figure 8] FIG. 2 is a diagram illustrating the configuration of an affiliated credit card company server 300. [Figure 9] FIG. 10 is a diagram showing an example of the contents of card information 372. [Figure 10] FIG. 1 is a diagram conceptually illustrating the processes of terminal payment and card payment. [Figure 11]FIG. 4 is a sequence diagram showing a first example of processing related to card issuance / card registration according to the first embodiment. [Figure 12] FIG. 10 is a sequence diagram showing a second example of the process relating to card issuance / card registration according to the first embodiment. [Figure 13] FIG. 10 is a sequence diagram showing a third example of the process relating to card issuance / card registration according to the first embodiment. [Figure 14] FIG. 10 is a diagram showing an example of a card details screen for an affiliated card 57. [Figure 15] 10 is a diagram showing an example of a half sheet SH1 for selecting an affiliated card 57. FIG. [Figure 16] 13 is a diagram showing another example of the card details screen for affiliated card 57. FIG. [Figure 17] FIG. 10 is a diagram showing an example of a screen for changing the display name of an affiliated card 57. [Figure 18] FIG. 10 is a diagram showing an example of a home screen of the payment application 20. [Figure 19] FIG. 10 is a diagram showing an example of a payment screen of payment application 20. [Figure 20] FIG. 10 is a diagram showing an example of a wallet screen of payment application 20. [Figure 21] FIG. 10 is a sequence diagram showing a first example of processing related to card issuance / card registration according to the second embodiment. [Figure 22] FIG. 10 is a sequence diagram showing a second example of the process relating to card issuance / card registration according to the second embodiment. [Figure 23] FIG. 10 is a sequence diagram showing a third example of the process relating to card issuance / card registration according to the second embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0009] Hereinafter, with reference to the drawings, embodiments of an information processing device, an information processing system, an information processing method, and a program of the present invention will be described. An application program, a payment server, and an affiliated credit card company server cooperate to provide an electronic payment service. In the following description, the application program will be referred to as a payment app. An electronic payment service is a service that supports payments for the purchase of goods and services at a store. A store is, for example, a physical store (real store) existing in real space, but may also include a virtual store for e-commerce. A virtual store may also include a store provided by an entity different from the operator of the electronic payment service. In such a case, when paying for purchases at the virtual store, the user is controlled to transition to an interface screen for the electronic payment service. In an electronic payment service, a store is treated as belonging to, for example, an affiliated store (brand), and when a purchase is made at a store, processing such as payment is primarily conducted between the user and the affiliated store. Alternatively, processing such as payment may be conducted between the user and the store.

[0010] First Embodiment [Electronic payment service] Figure 1 shows an example of a configuration for realizing an electronic payment service. The electronic payment service is realized mainly by a payment server 100. The payment server 100 communicates with, for example, one or more user terminal devices 200, one or more first store terminal devices 50, one or more credit processing terminals 55, one or more second store terminal devices 70, an affiliated credit card company server 300, and a shopping server 400 via a network NW. The network NW includes, for example, the Internet, a LAN (Local Area Network), a wireless base station, a provider device, etc.

[0011] User terminal device 200 is, for example, a portable terminal device such as a smartphone or tablet terminal. User terminal device 200 is a computer device having at least an optical reading function, a communication function, a display function, an input acceptance function, and a program execution function. In the following description, components for realizing these functions are referred to as a camera, a communication device, a touch panel, a CPU (Central Processing Unit), etc. In user terminal device 200, a processor such as a CPU executes payment app 20, which operates in cooperation with payment server 100 to provide electronic payment services to users. Payment app 20 is installed on user terminal device 200 from, for example, an application store, and controls the camera, communication device, touch panel, etc.

[0012] The first store terminal device 50 is installed, for example, in a store. The first store terminal device 50 is a computer device having at least a product price acquisition function, an optical reading function, a program execution function, and a communication function. The first store terminal device 50 includes a so-called POS (Point of Sale) device, and the product price acquisition function and the optical reading function may be realized by the POS device. The store code image 60 is placed in the store and is a code image such as a QR code (registered trademark) printed on a paper or plastic medium. The store code image 60 may be displayed on a display placed in the store (which may be the display of a terminal device such as a smartphone).

[0013] The credit processing terminal 55 is installed in the store, similar to the first store terminal device 50. The credit processing terminal 55 includes, for example, a credit card payment terminal (credit card reader) and a POS device. The credit card payment terminal reads a PIN (Personal Identification Number) from an inserted or held credit card (including an affiliated card 57) and compares it with the PIN entered by the user, and transmits a BIN (Bank Identification Number) code and other information read from the credit card to the affiliated credit card company server 300 via the POS device. The POS device cooperates with the credit card payment terminal to transmit information such as the payment amount to the affiliated credit card company server 300. A reimbursement agent server (acquirer) may be interposed between the credit processing terminal 55 and the affiliated credit card company server 300. For simplicity, the following description omits the reimbursement agent server. The affiliated card 57 is, for example, similar to a commonly used credit card, with a communication chip embedded in the card substrate. The communication chip includes a storage medium that stores a PIN, and communicates with an external device via a contactor (or a wireless antenna). Alternatively, the affiliated card 57 may be a magnetic card.

[0014] The second store terminal device 70 is used by the operator of the affiliated store. The second store terminal device 70 is a smartphone, tablet terminal, personal computer, etc. An interface for affiliated stores 72 runs on the second store terminal device 70. The interface for affiliated stores 72 may be an app for affiliated stores or a browser. The interface for affiliated stores 72 accepts coupon settings and the like from the operator of the affiliated store and transmits them to the payment server 100. The second store terminal device 70, which is a smartphone, has the function of displaying a code image corresponding to a store code image and reading the code image displayed by the user terminal device 200 by executing the app for affiliated stores.

[0015] The payment server 100 realizes electronic payment based on payment information received from the user terminal device 200 or the first store terminal device 50. The first store terminal device 50 may include a POS device and an affiliated store server, in which case payment information is sent from the POS device via the affiliated store server to the payment server 100. In the following explanation, this distinction will not be made and it is assumed that payment information is sent from the first store terminal device 50.

[0016] The affiliated credit card company server 300 manages affiliated credit card payments, which are part of the electronic payment service. The affiliated credit card company server 300 is operated, for example, by a group company (affiliated credit card company) of the payment server 100. The affiliated credit card company may be a separate entity from the external credit card company that provides the credit card as a fund source for charging the charge balance.

[0017] The shopping server 400 is a server that provides a service for purchasing products over the Internet. The shopping server 400 is operated by a group company (shopping company) of an affiliated credit card company. For example, the shopping server 400 may provide a shopping site over the Internet and perform product purchase processing in response to a request from the user terminal device 200. The shopping server 400 may also provide an auction site over the Internet.

[0018] Card manufacturing server 500 is a server of a manufacturing company that manufactures affiliated cards 57. For example, card manufacturing server 500 is connected to a printing device that manufactures affiliated cards 57 by printing on physical cards, receives printing data (card number, name, expiration date, display name, etc.) from affiliated credit card company server 300, and controls the printing device based on the received printing data.

[0019] 2 and 3 are sequence diagrams illustrating the general flow of electronic payment. There may be two patterns for electronic payment: Pattern 1 and Pattern 2.

[0020] In the case of pattern 1 (hereinafter referred to as user scan) shown in FIG. 2, user terminal device 200, with payment application 20 running, decodes store code image 60 using its optical reading function (S1). Store code image 60 includes store URL (Uniform Resource Locator) information. This store URL is the domain of the electronic payment service to which store identification information has been added, and is associated with an affiliated store ID, store ID, etc. in payment server 100 (described below). Payment application 20 sends first payment information including the store URL and account ID to payment server 100 (S2). Payment server 100 searches for store information (described below) using the affiliated store ID and store ID corresponding to the store URL, acquires information on the affiliated store name and store name (S3), and sends this information to payment application 20 (S4). The user enters the payment amount into user terminal device 200 on the screen displaying the affiliated store name and store name (S5). Then, the user terminal device 200 generates second payment information including at least the payment amount and sends it to the payment server 100 (S6). The payment server 100 makes the electronic payment based on the received second payment information (S7). The payment server 100 then sends a payment completion notice (information for displaying a payment completion screen) to the payment app 20 (S8), and the payment app 20 displays the payment completion screen (S9). Note that when the store code image 60 is displayed on a display installed in the store, the store code image 60 may include information on the payment amount in addition to the store URL. In this case, the step of the user inputting the payment amount is omitted, and the payment amount information is included in the first payment information and sent to the payment server 100. Information on the affiliated store name and store name may be included and displayed on the payment completion screen.

[0021] In the case of pattern 2 (hereinafter referred to as store scan) shown in FIG. 3, the payment app 20 sends a request to issue a one-time code to the payment server 100 when the payment app 20 is launched, when a payment operation is performed in the payment app 20, at the automatic update timing (e.g., every minute), and at other timings (S11). The payment server 100 generates a one-time code (S12) and sends it to the payment app 20 (S13). The payment app 20 displays a code image, such as a QR code or barcode, generated based on the one-time code (S14). The user holds (presents) the display surface of the user terminal device 200 over the first in-store terminal device 50, and the first in-store terminal device 50 decodes the code image using its optical reading function and obtains the one-time code, etc. (S15). The first in-store terminal device 50 then generates payment information including the one-time code, payment amount, affiliated store ID, store ID, etc., and sends it to the payment server 100 (S16). The payment amount information is acquired in advance by reading a barcode, manually entering it, etc. Based on the received information, the payment server 100 identifies the user corresponding to the one-time code and performs electronic payment (S17). Then, the payment server 100 sends a payment completion notice to the payment application 20 (S18), and the payment application 20 displays a payment completion screen (S19).

[0022] Note that electronic payment may be performed using only one of the above patterns. Furthermore, the "account ID" described in FIG. 2 may be other information (e.g., a phone number) that can be used as user identification information. Furthermore, issuing a one-time code may be omitted in store scanning, and the payment application 20 may display a code image generated based on the user's account ID. In this case, the payment server 100 identifies the user corresponding to the account ID instead of identifying the user corresponding to the one-time code.

[0023] [Payment server] 4 is a configuration diagram of payment server 100. Payment server 100 includes, for example, communication unit 110, payment content providing unit 120, payment processing unit 130, information management unit 140, and storage unit 170. Payment content providing unit 120, payment processing unit 130, and information management unit 140 are realized, for example, by a hardware processor such as a CPU executing a program (software). Some or all of these components may be realized by hardware (including circuitry) such as an LSI (Large Scale Integration), ASIC (Application Specific Integrated Circuit), FPGA (Field-Programmable Gate Array), or GPU (Graphics Processing Unit), or may be realized by a combination of software and hardware. The program may be stored in advance in a storage device such as an HDD (Hard Disk Drive) or flash memory (a storage device with a non-transitory storage medium), or may be stored in a removable storage medium (a non-transitory storage medium) such as a DVD or CD-ROM, and installed in the storage device by inserting the storage medium into a drive device.

[0024] The storage unit 170 is a HDD, flash memory, RAM (Random Access Memory), etc. The storage unit 170 may be a NAS (Network Attached Storage) device that the payment server 100 can access via a network. The storage unit 170 stores information such as user information 172, payment content information 174, and affiliated store / shop information 176.

[0025] The communication unit 110 is a communication interface for connecting to the network NW, and is, for example, a network interface card.

[0026] The payment content providing unit 120 has, for example, a function of a web server, and provides information (content) for displaying various screens of the electronic payment service to the user terminal device 200. The payment content providing unit 120 reads out necessary content from the payment content information 174 as appropriate and provides it to the user terminal device 200. The user terminal device 200 accepts various inputs from the user while content is being played by the payment application 20, and transmits the above-mentioned payment information and the like to the payment server 100.

[0027] The payment processing unit 130 performs payment processing based on the payment information transmitted by the user terminal device 200 or the first store terminal device 50. The payment processing unit 130 performs payment processing while referring to the user information 172.

[0028] FIG. 5 is a diagram showing an example of the contents of user information 172. User information 172 is an example of user registration information. User information 172 includes, for example, a user URL, account ID, telephone number, and password, as well as associated information such as email address, name, address, date of birth, registration date, charge balance, credit card settings, credit card limit, credit card usage amount, available credit card balance, payment method settings, affiliated card number, bank account, credit card number, charge history information, payment history information, and user ID. The user URL is used for remittance processing between users. When registering for an electronic payment service, registration of a phone number and password is required. The account ID is issued to the user by the payment server 100. Similarly, the email address, name, address, and date of birth are information that can be set by the user (or do not have to be set). The registration date is the date the user registered for the electronic payment service (the date the account was created). Hereinafter, a user instance (electronic payment account) associated with this information will be referred to as an account.

[0029] The charge balance indicates the balance of electronic money set by the user by transferring funds to the account in advance. Transfer methods include transfers from a designated service provider (bank) ATM (Automatic Teller Machine) or from a registered bank account. The credit payment setting indicates whether the settings for electronic credit payment have been completed and is set to either "Completed" or "Not Completed." The credit payment limit is the monthly credit payment limit. The credit payment amount is the amount of credit payment already used in the current month. The available credit payment amount is the amount of credit payment available in the current month, calculated by subtracting the credit payment amount from the credit payment limit. While the figure shows only one credit payment limit, in reality, there may also be daily limits, and the lower of these may be set as the credit payment limit. Further details of credit payments will be described later. The payment method setting indicates whether the user will make electronic payments using the charge balance or by credit payment at that time. The affiliated card number is the number of the affiliated card 57 (e.g., PAN (Primary Account Number)). The bank account and credit card number are information on a bank account or credit card number (account number, card number) that can be used to deposit funds into the electronic payment service. This credit card number is the number of a credit card other than the affiliated card 57. The charge history information is a history of the user's previous transfers to the electronic payment service to increase the charge balance. The payment history information is information that shows the breakdown of payments made by the user for each payment (date and time, store ID of the store where the purchase was made, payment amount, payment method, etc.). The user ID is identification information used to identify the user in the affiliated credit card company server 300. Note that for users whose accounts are not linked between the payment server 100 and the affiliated credit card company server 300, the user ID field will be blank.

[0030] 6 is a diagram showing an example of the contents of affiliated store / store information 176. The affiliated store / store information 176 includes, for example, a first table 176A in which an affiliated store ID and a store ID are associated with a store URL, a second table 176B in which an affiliated store ID is associated with an affiliated store name and sales amount (described above), and a third table 176C in which a store ID is associated with a store name. In addition to this information, the affiliated store / store information 176 may also include information such as the category of the affiliated store or store, the store's location, and payment patterns.

[0031] The information management unit 140 manages the user information 172 and the affiliated store / store information 176 based on information acquired from the user terminal device 200 and the second store terminal device 70. The information management unit 140 adds new records to, edits, deletes, etc. the user information 172 and the affiliated store / store information 176.

[0032] [User terminal device] 7 is a configuration diagram of user terminal device 200. User terminal device 200 includes, for example, a communication unit 210, a display unit 220, an input unit 230, a control unit 240, and a storage unit 250. Communication unit 210 is a communication interface for communicating via network NW. Display unit 220 and input unit 230 are realized, for example, by a touch panel display.

[0033] The control unit 240 is realized, for example, by a hardware processor such as a CPU executing a program (software). Some or all of these components may be realized by hardware (including circuit units) such as an LSI, ASIC, FPGA, or GPU, or may be realized by a combination of software and hardware. The program may be stored in advance in a storage device such as an HDD or flash memory (a storage device having a non-transitory storage medium), or may be stored in a removable storage medium (non-transitory storage medium) such as a DVD or CD-ROM, and installed in the storage device by inserting the storage medium into a drive device.

[0034] Storage unit 250 is a HDD, flash memory, RAM, or the like. Storage unit 250 may be a NAS device that user terminal device 200 can access via a network. Storage unit 250 stores user information 252, payment application 20, and the like. User information 252 is some or all of the information in the record corresponding to the user who owns user terminal device 200, among user information 172 shown in FIG. 5. Payment application 20 is read and executed by a hardware processor (such as a CPU) in user terminal device 200.

[0035] [Affiliated credit card company server] 8 is a configuration diagram of affiliated credit card company server 300. Affiliated credit card company server 300 includes, for example, a communication unit 310, a reception unit 315, a personal identification information acquisition unit 320, a card information provision unit 325, an authentication unit 330, a confirmation unit 335, an issuance request acquisition unit 340, an issuance unit 345, a name assignment unit 350, a name change unit 355, a print data provision unit 360, and a storage unit 370. Communication unit 310 is a communication interface for communication via network NW.

[0036] The reception unit 315, personal identification information acquisition unit 320, card information provision unit 325, authentication unit 330, confirmation unit 335, issuance request acquisition unit 340, issuance unit 345, name assignment unit 350, name change unit 355, and print data provision unit 360 are realized, for example, by a hardware processor such as a CPU executing a program (software). Some or all of these components may be realized by hardware (including circuit units) such as an LSI, ASIC, FPGA, or GPU, or may be realized by a combination of software and hardware. The program may be stored in advance in a storage device such as an HDD or flash memory (a storage device with a non-transitory storage medium), or may be stored in a removable storage medium (a non-transitory storage medium) such as a DVD or CD-ROM, and installed in the storage device by inserting the storage medium into a drive device.

[0037] Storage unit 370 is a HDD, flash memory, RAM, etc. Storage unit 370 may be a NAS device that can be accessed by affiliated credit card company server 300 via a network. Storage unit 370 stores card information 372 and the like.

[0038] FIG. 9 is a diagram showing an example of the contents of card information 372. Card information 372 associates information such as an affiliated card number, user ID, telephone number, name, address, date of birth, bank account, display name, payment method setting, and account ID. The affiliated card number is the number of the affiliated card 57 (e.g., PAN). The user ID is identification information for identifying the user in the affiliated credit card company server 300. The telephone number, name, address, and date of birth are information used in the identity verification process described below, and are the user's telephone number, name, address, and date of birth. The bank account is information regarding the bank account from which the billing amount incurred when using the affiliated card 57 is debited. The display name is a nickname that the user can arbitrarily set for the affiliated card 57. The payment method setting and account ID are the same information as those included in the user information 172 in FIG. 5, and are synchronized with the payment server 100. For users whose accounts are not linked between the payment server 100 and the affiliated credit card company server 300, the payment method setting and account ID fields will be left blank. The card information 372 may also include information such as the expiration date and security code of the affiliated card 57.

[0039] Here, we will explain terminal payment and card payment. Figure 10 is a diagram conceptually showing the processing of terminal payment and card payment. As explained below, the electronic payment service allows for four types of electronic payment: (1) terminal payment / payment using the charge balance, (2) terminal payment / payment using a credit card, (3) card payment / payment using the charge balance, and (4) card payment / payment using a credit card.

[0040] [Terminal payment] (1) When the payment server 100 (payment processing unit 130) acquires payment information from the user terminal device 200 or the first store terminal device 50, terminal payment is initiated. The payment server 100 references the user information 172 to acquire the "payment method setting" of the user. The payment server 100 performs electronic payment by its own processing for a user whose "payment method setting" is set to "charge balance." In this case, the payment processing unit 130 performs electronic payment by decreasing the charge balance managed in association with the user ID and increasing the item value of the affiliated store's sales proceeds. The item value of the affiliated store's sales proceeds is not itself used as electronic money, for example, but rather the amount corresponding to the item value of the sales proceeds is transferred to a bank account in a cycle according to an agreement between the affiliated store and the electronic payment service.

[0041] (2) In terminal payment, the payment server 100 transfers payment information to the affiliated credit card company server 300 together with the affiliated card number of the user, obtained by referencing the user information 172, for a user whose "payment method setting" is set to "credit payment." The affiliated credit card company server 300 checks whether the cumulative payment amount indicated in the payment information does not exceed the upper limit for the current month, and if it does not exceed the upper limit, performs processing such as adding the acquired payment amount to the cumulative payment amount for the user. The cumulative payment amount for one month is settled, for example, by debiting from a bank account all at once on the payment date of the following month.

[0042] [Card payment] (3) When the affiliated credit card company server 300 acquires the payment information from the credit processing terminal 55, electronic payment (card payment) using the affiliated card 57 is initiated. The affiliated credit card company server 300 references the card information 372 stored in the memory unit 370. For a user whose "card payment method" is set to "charge balance," the affiliated credit card company server 300 transfers the payment information to the payment server 100 together with the user's account ID obtained by referencing the card information 372. Based on the acquired payment information, the payment server 100 performs the same processing as when the "payment method setting" is set to "charge balance" in terminal payment.

[0043] (4) In the case of card payment, the affiliated credit card company server 300 performs electronic payment by its own processing for users whose "card payment method" is set to "credit payment." In this case, the affiliated credit card company server 300 performs the same processing as when the "payment method setting" is set to "credit payment" in the case of terminal payment.

[0044] [Card issuance / card registration] Next, the card issuance process and the card registration process will be described. The card issuance process is a process of issuing an affiliated card 57 in response to a card issuance request from the user terminal device 200. The card registration process is a process of registering the issued affiliated card 57 in the payment server 100.

[0045] In conventional electronic payment systems, when registering an affiliated card 57 in the payment server 100 in association with a user's account ID, the user must take the time to input information about the affiliated card 57, which can be cumbersome for the user. In contrast, in this embodiment, the user can register the affiliated card 57 in the payment server 100 without having to input information about the affiliated card 57. This makes it possible to easily register the affiliated card 57 (credit card) to the user's account. The card issuance process and card registration process of this embodiment will be described in detail below.

[0046] [Sequence diagram] Fig. 11 is a sequence diagram showing a first example of processing related to card issuance / card registration according to embodiment 1. The sequence diagram shown in Fig. 11 shows processing in the case where the payment server 100 holds the user's personal identification information.

[0047] Before requesting card issuance, the user must obtain a user ID required to use the services of affiliated credit card company server 300. The user ID is the same information as the user ID included in card information 372 (FIG. 9). The user uses user terminal device 200 to access the website of affiliated credit card company server 300 and apply for issuance of affiliated card 57 via the Web.

[0048] First, user terminal device 200 transmits a card issuance request via the Web to affiliated credit card company server 300 (S101). The card issuance request includes personal information (name, address, date of birth, telephone number, bank account, place of employment, annual income, borrowing status, etc.) of the user operating user terminal device 200 and the user ID.

[0049] Next, when the issuance request acquisition unit 340 of the affiliated credit card company server 300 acquires the card issuance request from the user terminal device 200, the affiliated credit card company conducts an examination based on the user's personal information (particularly, place of employment, annual income, borrowing status, etc.). If the examination is not passed, the affiliated credit card company server 300 notifies the user terminal device 200 that the affiliated card 57 cannot be issued.

[0050] On the other hand, if the examination is passed, the issuing unit 345 performs the issuance process of the affiliated card 57 based on the card issuance request (S102). Specifically, the issuing unit 345 issues an affiliated card number, expiration date, security code, etc. to the user who has passed the examination.

[0051] Furthermore, the issuing unit 345 updates the card information 372 (S103). Specifically, the issuing unit 345 links the issued affiliated card number to the user ID, telephone number, name, address, date of birth, and bank account received from the user terminal device 200, and records the linked number in the card information 372 (FIG. 9). Furthermore, if account linkage is performed between the payment server 100 and the affiliated credit card company server 300, the payment method setting and account ID are also recorded in the card information 372. Although not shown in FIG. 9, the expiration date and security code of the affiliated card 57 are also recorded in the card information 372. Thereafter, the issuing unit 345 controls the communication unit 310 to transmit an issuance completion notification to the user terminal device 200 (S104).

[0052] When user terminal device 200 receives an issuance completion notification from affiliated credit card company server 300, it displays an issuance completion screen on display unit 220. Information about the currently issued affiliated card 57 (affiliated card number, etc.) is displayed on the issuance completion screen. This allows the user to understand that affiliated card 57 has been issued.

[0053] After the issuance of the affiliated card 57, the user may wish to register the issued affiliated card 57 as a card for credit payment with the payment server 100. If the user were required to input information about the affiliated card 57 when registering the affiliated card 57, this would be a cumbersome input task for the user. Therefore, in this embodiment, it is possible to register the affiliated card 57 as a card for credit payment with the payment server 100 without requiring the user to input information about the affiliated card 57. The flow of the registration process for the affiliated card 57 will be described below.

[0054] The user accesses the website of the affiliated credit card company server 300 using the user terminal device 200 and instructs via the Web to register the affiliated card 57 as a card for credit payment with the payment server 100. At this time, the user terminal device 200 sends a card registration request via the Web to the affiliated credit card company server 300 (S105). The card registration request includes the user ID of the user operating the user terminal device 200.

[0055] Next, the reception unit 315 of the affiliated credit card company server 300 receives the card registration request sent from the user terminal device 200. Furthermore, the confirmation unit 335 confirms whether or not account linkage has been established between the payment server 100 and the affiliated credit card company server 300. For example, if an account ID is linked to the user's user ID in the card information 372, the confirmation unit 335 determines that account linkage has been established.

[0056] If the confirmation unit 335 determines that account linkage is being performed, the personal identification information acquisition unit 320 acquires the account ID linked to the user ID included in the card registration request from the card information 372. Thereafter, the personal identification information acquisition unit 320 controls the communication unit 310 to transmit the account ID acquired from the card information 372 to the payment server 100 (S106).

[0057] When the information management unit 140 of the payment server 100 acquires the account ID transmitted from the affiliated credit card company server 300, it acquires the telephone number and personal identification information (e.g., name and date of birth) of the user linked to the acquired account ID from the user information 172. Thereafter, the information management unit 140 controls the communication unit 110 to transmit the telephone number and personal identification information (e.g., name and date of birth) acquired from the user information 172 to the affiliated credit card company server 300 (S107).

[0058] The personal identification information acquisition unit 320 of the affiliated credit card company server 300 acquires the personal identification information linked to the user's account ID from the card information 372. The personal identification information acquisition unit 320 also acquires the telephone number and personal identification information sent from the payment server 100 in S107. Thereafter, the authentication unit 330 determines whether the personal identification information acquired from the card information 372 matches the personal identification information acquired from the payment server 100 (S108). If the personal identification information acquired from the card information 372 matches the personal identification information acquired from the payment server 100, the authentication unit 330 determines that personal authentication has been successful. Note that the authentication unit 330 does not perform personal authentication using the telephone number in S108, but may perform personal authentication using the telephone number if personal identification information cannot be obtained from the payment server 100. This point will be described in detail later.

[0059] If the authentication unit 330 is successful in authenticating the user, the card information providing unit 325 controls the communication unit 310 to transmit information about the affiliated card 57 (account ID and affiliated card number) to the payment server 100 (S109).

[0060] On the other hand, if the authentication unit 330 is not successful in authenticating the user, the card information providing unit 325 controls the communication unit 310 to send a notification to the user terminal device 200 indicating that the affiliated card 57 cannot be registered because the user cannot be authenticated. This makes it possible to prevent fraudulent use by others, such as "impersonation."

[0061] When the information management unit 140 of the payment server 100 acquires information (account ID and affiliated card number) related to the affiliated card 57 transmitted from the affiliated credit card company server 300, the information management unit 140 updates the user information 172 (S110). Specifically, the information management unit 140 records the affiliated card number in the user information 172 in association with the acquired account ID. This allows the issued affiliated card 57 to be registered as a card for credit payment in the payment server 100.

[0062] When the information management unit 140 completes updating of the user information 172, it controls the communication unit 110 to send a registration completion notice to the affiliated credit card company server 300 (S111). When the affiliated credit card company server 300 receives the registration completion notice from the payment server 100, it sends the registration completion notice to the user terminal device 200 (S112).

[0063] When the user terminal device 200 receives a registration completion notification from the affiliated credit card company server 300, it displays a registration completion screen on the display unit 220. The registration completion screen displays information (affiliated card number, etc.) about the affiliated card 57 registered in the payment server 100. This allows the user to understand that the affiliated card 57 has been registered as a card for credit payment with the payment server 100.

[0064] In the above explanation, we have described the case where one affiliated card 57 is issued to a user, but in reality, multiple affiliated cards 57 may be issued to a user. For example, a user may wish to use different affiliated cards 57 for different purposes (e.g., food expenses, personal expenses, etc.) or may wish to own multiple affiliated cards 57 of different brands. In such cases, the affiliated credit card company server 300 of this embodiment issues the second and subsequent affiliated cards 57 in response to a card issuance request from the user. As multiple affiliated cards 57, for example, it is conceivable to issue one gold card and multiple regular cards (of different brands).

[0065] When multiple affiliated cards 57 are issued, the affiliated credit card company server 300 of this embodiment enables the multiple affiliated cards 57 to be registered as credit payment cards in the payment server 100 without requiring the user to input information about the multiple affiliated cards 57. For example, in S109 of FIG. 11 , when multiple affiliated cards 57 have been issued to the user and the authentication unit 330 has successfully authenticated the user, the card information providing unit 325 may provide information about the multiple affiliated cards 57 (account IDs and affiliated card numbers) to the payment server 100. Also, in S110 of FIG. 11 , the information management unit 140 of the payment server 100 may update the user information 172 based on the information about the multiple affiliated cards 57 (account IDs and affiliated card numbers) received from the affiliated credit card company server 300. This allows all of the issued multiple affiliated cards 57 to be registered as credit payment cards in the payment server 100.

[0066] 11, if multiple affiliated cards 57 have been issued to the user and the authentication unit 330 has successfully authenticated the user, the card information providing unit 325 may provide the payment server 100 with information about the affiliated card 57 selected by the user from the multiple affiliated cards 57. Also, in S110 of FIG. 11, the information management unit 140 of the payment server 100 may update the user information 172 based on information about the affiliated card 57 selected by the user (account ID and affiliated card number) received from the affiliated credit card company server 300. This allows the affiliated card 57 selected by the user from the multiple issued affiliated cards 57 to be registered as a card for credit payment in the payment server 100.

[0067] Figure 12 is a sequence diagram showing a second example of the processing related to card issuance / card registration according to the first embodiment. The sequence diagram shown in Figure 12 shows the processing when the payment server 100 does not hold the user's personal identification information and the user makes a registration request for the first affiliated card 57. Note that the processing of S201 to S206 in Figure 12 is the same as S101 to S106 in Figure 11, and therefore description thereof will be omitted.

[0068] In the payment server 100, if the identity of the user has not been verified by, for example, eKYC, the identity verification information of the user (e.g., name and date of birth) will not be recorded in the user information 172. In this case, when the information management unit 140 of the payment server 100 acquires the account ID transmitted from the affiliated credit card company server 300 in S206, it acquires the user's telephone number linked to the acquired account ID from the user information 172. On the other hand, the information management unit 140 cannot acquire identity verification information (e.g., name and date of birth). Therefore, the information management unit 140 controls the communication unit 110 to transmit only the telephone number acquired from the user information 172 to the affiliated credit card company server 300 (S207).

[0069] If the authentication unit 330 of the affiliated credit card company server 300 is unable to acquire the user's identity verification information (e.g., name and date of birth) from the payment server 100, it authenticates the user. Specifically, the authentication unit 330 performs processing for 3DS (3-D Secure) authentication as identity authentication (S208). In 3DS authentication, identity authentication is performed using a one-time password, biometric authentication, or the like. If 3DS authentication is successful, the authentication unit 330 determines that identity authentication has been successful.

[0070] If the authentication unit 330 is successful in authenticating the user (3DS authentication), the card information providing unit 325 controls the communication unit 310 to send information about the affiliated card 57 (account ID and affiliated card number) to the payment server 100 (S209).

[0071] On the other hand, if the authentication unit 330 is unsuccessful in authenticating the user (3DS authentication), the card information providing unit 325 controls the communication unit 310 to send a notification to the user terminal device 200 indicating that the affiliated card 57 cannot be registered because the user cannot be authenticated. This makes it possible to prevent fraudulent use by others, such as "impersonation." Note that the processes of S210 to S212 in Figure 12 are the same as S110 to S112 in Figure 11, and therefore their explanation will be omitted.

[0072] Figure 13 is a sequence diagram showing a third example of the processing related to card issuance / card registration according to the first embodiment. The sequence diagram shown in Figure 13 shows the processing when the payment server 100 does not hold the user's personal identification information and the user requests registration of a second or subsequent affiliated card 57. Note that the processing of S301 to S306 in Figure 13 is the same as S101 to S106 in Figure 11, and therefore description thereof will be omitted.

[0073] In the payment server 100, if the identity of the user has not been verified by, for example, eKYC, the identity verification information of the user (e.g., name and date of birth) will not be recorded in the user information 172. In this case, when the information management unit 140 of the payment server 100 acquires the account ID transmitted from the affiliated credit card company server 300 in S306, it acquires the telephone number of the user linked to the acquired account ID from the user information 172. On the other hand, the information management unit 140 cannot acquire the identity verification information (e.g., name and date of birth). Therefore, the information management unit 140 controls the communication unit 110 to transmit only the telephone number acquired from the user information 172 to the affiliated credit card company server 300 (S307).

[0074] If the authentication unit 330 of the affiliated credit card company server 300 is unable to acquire the user's identity verification information (e.g., name and date of birth) from the payment server 100, it authenticates the user. Specifically, the authentication unit 330 performs processing for SMS (Short Message Service) authentication as identity authentication (S308). In SMS authentication, the authentication unit 330 sends a short message containing a temporary authentication code to the user's phone number, and then authenticates the user based on the authentication code entered by the user. The above-mentioned 3DS authentication is not appropriate when multiple affiliated cards 57 have been issued, because it requires authentication by specifying the affiliated credit card number. For this reason, SMS authentication is performed when multiple affiliated cards 57 have been issued. If the SMS authentication is successful, the authentication unit 330 determines that identity authentication has been successful.

[0075] If the authentication unit 330 is successful in authenticating the user (SMS authentication), the card information providing unit 325 controls the communication unit 310 to send information about the affiliated card 57 (account ID and affiliated card number) to the payment server 100 (S309).

[0076] On the other hand, if the authentication unit 330 is not successful in authenticating the user (SMS authentication), the card information providing unit 325 controls the communication unit 310 to send a notification to the user terminal device 200 indicating that the affiliated card 57 cannot be registered because the user cannot be authenticated. This makes it possible to prevent fraudulent use by others, such as "impersonation." Note that the processes of S310 to S312 in Figure 13 are the same as S110 to S112 in Figure 11, and therefore their explanation will be omitted.

[0077] [Display name assignment] When multiple affiliated card numbers are issued to one user account, the naming unit 350 of the affiliated credit card company server 300 assigns different display names (arbitrary names) to each of the multiple affiliated cards 57 corresponding to the multiple affiliated card numbers based on instructions from the user. The display names are nicknames that the user can arbitrarily set for the affiliated cards 57, such as for home use, food expenses, hobbies, or personal use. The user can launch a mini app from the payment app 20 and set a display name for the affiliated card 57 on the mini app.

[0078] Figure 14 is a diagram showing an example of a card details screen for affiliated card 57. The card details screen shown in Figure 14 is displayed on display unit 220 of user terminal device 200 by launching a mini app for affiliated card 57 from payment app 20. The card details screen displays multiple areas 261 and 262 and multiple buttons 263 and 264.

[0079] An image of the user's affiliated card 57 is displayed in area 261. Specifically, the affiliated card number, the user's name, expiration date, security code, etc. are displayed in area 261. Note that the image of affiliated card 57 may be changed depending on the type of affiliated card 57 (regular, gold, etc.).

[0080] Area 262 displays the display name (nickname) of the user's affiliated card 57. Specifically, area 262 displays "Meal Expenses" as the display name of the affiliated card 57 displayed in area 261. Therefore, in the example shown in FIG. 14, it can be seen that the affiliated card 57 displayed in area 261 is a card for meal expenses.

[0081] Button 263 is a button for switching the user's affiliated card 57. When the user selects (tap) button 263, a half sheet SH1 (FIG. 15) described later is displayed on display unit 220 of user terminal device 200.

[0082] Button 264 is a button for issuing an instruction to change the display name of affiliated card 57. When the user selects (tap) button 264, a display name change screen (FIG. 17) described below is displayed.

[0083] FIG. 15 is a diagram showing an example of a half sheet SH1 for selecting an affiliated card 57. For example, when a user selects (tap) button 263 in FIG. 14, half sheet SH1 shown in FIG. 15 is displayed on display unit 220 of user terminal device 200. As shown in FIG. 15, multiple areas 265-268 are displayed on half sheet SH1. An affiliated card 57 owned by the user is displayed in each of the multiple areas 265-268. In the example shown in FIG. 15, the user owns four affiliated cards 57.

[0084] Specifically, area 265 displays the user's first affiliated card 57 (display name: for home use). Area 266 displays the user's second affiliated card 57 (display name: for food expenses). Area 267 displays the user's third affiliated card 57 (display name: for hobbies). Area 268 displays the user's second affiliated card 57 (display name: for private use).

[0085] The user can select an affiliated card 57 by selecting (tapping) any of areas 265 to 268. In the example shown in FIG. 15, the user has selected the second affiliated card 57 (display name: food expenses), so a check mark is displayed in area 266. When the user selects (tap) area 265, the first affiliated card 57 (display name: for home use) is selected. When the user selects (tap) area 267, the third affiliated card 57 (display name: for hobbies) is selected. When the user selects (tap) area 268, the fourth affiliated card 57 (display name: for private use) is selected.

[0086] Figure 16 is a diagram showing another example of the card details screen for the affiliated card 57. For example, when a user selects (tap) area 265 in Figure 15, the card details screen shown in Figure 16 is displayed on the display unit 220 of the user terminal device 200. Area 261 displays an image of the first affiliated card 57 selected by the user. Area 262 displays "For home use" as the display name (nickname) of the affiliated card 57 displayed in area 261.

[0087] In this way, user terminal device 200 displays the display name (nickname) of affiliated card 57 on the card details screen that displays information about affiliated card 57 (affiliated card number, user name, expiration date, security code, etc.). This allows the user to easily distinguish affiliated card 57 even when multiple affiliated cards 57 are registered to one account of the user.

[0088] Fig. 17 is a diagram showing an example of a screen for changing the display name of the affiliated card 57. For example, when the user selects (tap) button 264 in Fig. 14, the screen for changing the display name shown in Fig. 17 is displayed on the display unit 220 of the user terminal device 200.

[0089] The display name change screen displays a display name input area 269 and a keypad 270. When the user inputs a display name using the keypad 270, the input display name is displayed in the display name input area 269. The user terminal device 200 transmits the input display name and affiliated card number to the affiliated credit card company server 300. The name change unit 355 of the affiliated credit card company server 300 links the display name and affiliated card number received from the user terminal device 200 and records them in the card information 372. This allows the name change unit 355 to change the display name (any name) assigned to the affiliated card 57.

[0090] 18 is a diagram showing an example of the home screen of the payment application 20. As shown in FIG. 18, the home screen of the payment application 20 includes an area A1, an area A2, an area A3, a button 271, and a button 272.

[0091] Area A1 displays code information such as a barcode or QR code (registered trademark) used for smartphone payments, as well as information related to credit card payments (display name, affiliated card number). In this way, payment app 20 displays code information (barcode, QR code (registered trademark), etc.) on the display unit 220 of user terminal device 200 on the home screen of the electronic payment service, in association with the display name (any name) of affiliated card 57. This allows the user to easily understand which affiliated card 57 the code information displayed in area A1 corresponds to.

[0092] The payment application 20 may allow the user to select a background image for the code information displayed on the home screen of the electronic payment service based on instructions from the user. The payment application 20 may also display the selected background image in area A1. This allows the user to more easily understand which affiliated card 57 the code information displayed in area A1 corresponds to.

[0093] Furthermore, if the user swipes area A1 left or right, the payment method of the electronic payment service can be switched to another payment method. For example, if the user swipes area A1 right, the payment app 20 switches to a payment method using the electronic money balance. If the user swipes area A1 left, the payment app 20 switches to a payment method using another affiliated card 57 (display name: private). This allows the user to easily switch the payment method of the electronic payment service.

[0094] Area A2 displays icons for instructing the main operations of smartphone payments, such as scanning, remittance, points, usage history, and cards.

[0095] Area A3 displays various icons for launching various mini-apps that can be executed by payment app 20. Specifically, area A3 displays 12 icons. Of these icons, icon IC1 is an icon for launching a mini-app for affiliated card 57. When the user selects (tap) icon IC1, payment app 20 launches the mini-app for affiliated card 57. As a result, for example, a card details screen shown in FIG. 14 is displayed on display unit 220 of user terminal device 200.

[0096] Button 271 is a button for instructing the display of a payment screen. When the user selects (tap) button 271, a payment screen (FIG. 19) described below is displayed.

[0097] Button 272 is a button for instructing the display of a wallet screen. When the user selects (tap) button 272, a wallet screen (FIG. 20) described later is displayed.

[0098] Fig. 19 is a diagram showing an example of a payment screen of payment application 20. For example, when a user selects (tap) button 271 in Fig. 18, the payment screen shown in Fig. 19 is displayed on display unit 220 of user terminal device 200.

[0099] The payment screen displays code information such as a barcode or QR code (registered trademark) used for smartphone payments. When the user selects (tap) a payment method selection button (not shown) on the payment screen, half sheet SH2 is displayed. Half sheet SH2 displays two payment methods: payment using electronic money balance and payment using affiliated card 57. In the example shown in Figure 19, the user has selected payment using electronic money balance, so a check mark is displayed in the electronic money balance column.

[0100] 19, an affiliated card 57 with the display name "Home Use" and an affiliated card 57 with the display name "Private Use" are displayed. By selecting (tapping) one of the columns showing these affiliated cards 57, the user can select credit card payment using the selected affiliated card 57.

[0101] In this way, when making a credit payment in the electronic payment service, payment application 20 displays the display name (any name) given to affiliated card 57 on display unit 220 of user terminal device 200. This allows the user to easily identify affiliated card 57 that they intend to use for credit payment.

[0102] Fig. 20 is a diagram showing an example of the wallet screen of payment application 20. For example, when a user selects (tap) button 272 in Fig. 18, the wallet screen shown in Fig. 20 is displayed on display unit 220 of user terminal device 200. Areas A4 and A5 are displayed on the wallet screen.

[0103] Area A4 displays information regarding charges for each of the multiple affiliated cards 57 owned by the user. Specifically, area A4 displays the display name of the affiliated card 57, the affiliated credit card number, the charged amount, the amount used, and the available amount. In this way, payment application 20 displays the charged amount for the affiliated card 57 on display unit 220 of user terminal device 200 in association with the display name (arbitrary name) of the affiliated card 57. This allows the user to easily understand the charged amount for each affiliated card 57.

[0104] Furthermore, if the user swipes area A4 left or right, it is possible to switch to another affiliated card 57. This allows the user to easily switch between affiliated cards 57 for which they wish to display information about a bill.

[0105] Area A5 displays information about the user's assets. Specifically, area A5 displays the electronic money balance, usable points, valuation gains and losses from asset management, and bank deposit balance. In this way, payment application 20 displays information about affiliated card 57 charges and information about the user's assets side by side on display unit 220 of user terminal device 200. This allows the user to easily understand the relationship between expenses and assets.

[0106] In the above description, the display name (arbitrary name) of affiliated card 57 is displayed in various locations, but the locations where the display name of affiliated card 57 is displayed are not limited to the locations shown in Figures 14 to 20. For example, payment application 20 may display the payment amount, payment date and time, and the store where the electronic payment was made on the display unit 220 of user terminal device 200 on the transaction history screen of the electronic payment service, in association with the display name (arbitrary name) of affiliated card 57. This allows the user to easily identify the affiliated card 57 used in a transaction of the electronic payment service.

[0107] Furthermore, payment application 20 may individually accept assignment of a display name (any name) to affiliated card 57 of a family member between the parent member and family member of affiliated card 57. This allows different display names to be assigned to affiliated card 57 between the parent member and family member.

[0108] Furthermore, the payment application 20 may prohibit the parent member from checking or changing the display name (any name) given by the family member to the family member's affiliated card 57. This ensures the privacy of the family member.

[0109] The print data providing unit 360 of the affiliated credit card company server 300 provides the card manufacturing server 500 with print data for printing a display name (arbitrary name) on the affiliated card 57. The print data includes information such as the affiliated card number, name, and expiration date in addition to the display name. The card manufacturing server 500 controls a printing device that produces the affiliated card 57 by printing on a physical card based on the print data received from the affiliated credit card company server 300. For example, the display name (arbitrary name) is printed in a memo field on the affiliated card 57. This allows the display name (arbitrary name) to be printed on the affiliated card 57, allowing the user to easily identify the affiliated card 57.

[0110] Second Embodiment In the first embodiment described above, account linkage is performed between the payment server 100 and the affiliated credit card company server 300. In contrast, in the second embodiment, account linkage is performed between the payment server 100 and the shopping server 400. Specifically, there are cases where a credit card company and a company operating a shopping service are group companies, and a user ID for identifying a user on the shopping server 400 is required to issue a credit card. In this case, account linkage is performed between the payment server 100 and the shopping server 400, so that the user ID for identifying a user on the shopping server 400 can be shared between the shopping server 400 and the payment server 100. Details of the second embodiment will be described below.

[0111] [Sequence diagram] Fig. 21 is a sequence diagram showing a first example of processing related to card issuance / card registration according to the second embodiment. The sequence diagram shown in Fig. 21 shows processing in the case where the payment server 100 holds the user's personal identification information.

[0112] Before requesting the issuance of a card, the user must obtain a user ID required to use the services of shopping server 400. Using user terminal device 200, the user accesses the website of affiliated credit card company server 300 and applies for issuance of affiliated card 57 via the Web.

[0113] First, user terminal device 200 transmits a card issuance request via the Web to affiliated credit card company server 300 (S401). The card issuance request includes personal information (name, address, date of birth, telephone number, bank account, place of employment, annual income, borrowing status, etc.) of the user operating user terminal device 200 and the user ID.

[0114] Next, when the issuance request acquisition unit 340 of the affiliated credit card company server 300 acquires the card issuance request from the user terminal device 200, the affiliated credit card company conducts an examination based on the user's personal information (particularly, place of employment, annual income, borrowing status, etc.). If the examination is not passed, the affiliated credit card company server 300 notifies the user terminal device 200 that the affiliated card 57 cannot be issued.

[0115] On the other hand, if the examination is passed, the issuing unit 345 performs the issuance process of the affiliated card 57 based on the card issuance request (S402). Specifically, the issuing unit 345 issues an affiliated card number, expiration date, security code, etc. to the user who has passed the examination.

[0116] Furthermore, the issuing unit 345 updates the card information 372 (S403). Specifically, the issuing unit 345 links the issued affiliated card number to the user ID, telephone number, name, address, date of birth, and bank account received from the user terminal device 200, and records the linked number in the card information 372 (FIG. 9). Thereafter, the issuing unit 345 controls the communication unit 310 to transmit an issuance completion notification to the user terminal device 200 (S404).

[0117] When user terminal device 200 receives an issuance completion notification from affiliated credit card company server 300, it displays an issuance completion screen on display unit 220. Information about the currently issued affiliated card 57 (affiliated card number, etc.) is displayed on the issuance completion screen. This allows the user to understand that affiliated card 57 has been issued.

[0118] After the issuance of the affiliated card 57, the user may wish to register the issued affiliated card 57 as a card for credit payment with the payment server 100. If the user were required to input information about the affiliated card 57 when registering the affiliated card 57, this would be a cumbersome input task for the user. Therefore, in this embodiment, it is possible to register the affiliated card 57 as a card for credit payment with the payment server 100 without requiring the user to input information about the affiliated card 57. The flow of the registration process for the affiliated card 57 will be described below.

[0119] The user accesses the website of the affiliated credit card company server 300 using the user terminal device 200 and instructs via the Web to register the affiliated card 57 as a card for credit card payment with the payment server 100. At this time, the user terminal device 200 transmits a card registration request via the Web to the affiliated credit card company server 300 (S405). The card registration request includes the user ID of the user operating the user terminal device 200.

[0120] Next, the reception unit 315 of the affiliated credit card company server 300 receives the card registration request sent from the user terminal device 200. Furthermore, the confirmation unit 335 confirms whether account linkage has been established between the shopping server 400 and the payment server 100. Specifically, the confirmation unit 335 controls the communication unit 310 to transmit the user ID to the shopping server 400 (S406). The shopping server 400 transmits to the affiliated credit card company server 300 account linkage information indicating whether account linkage has been established between the shopping server 400 and the payment server 100 for the user ID received from the affiliated credit card company server 300 (S407). The confirmation unit 335 determines whether account linkage has been established based on the account linkage information received from the shopping server 400.

[0121] If the confirmation unit 335 determines that account linkage is being performed, the personal identification information acquisition unit 320 controls the communication unit 310 to send the user ID included in the card registration request to the payment server 100 (S408).

[0122] When the information management unit 140 of the payment server 100 acquires the user ID transmitted from the affiliated credit card company server 300, it acquires the telephone number and personal identification information (e.g., name and date of birth) of the user linked to the acquired user ID from the user information 172. Thereafter, the information management unit 140 controls the communication unit 110 to transmit the telephone number and personal identification information (e.g., name and date of birth) acquired from the user information 172 to the affiliated credit card company server 300 (S409).

[0123] The personal identification information acquisition unit 320 of the affiliated credit card company server 300 acquires the personal identification information linked to the user ID of the user from the card information 372. The personal identification information acquisition unit 320 also acquires the telephone number and personal identification information sent from the payment server 100 in S409. Thereafter, the authentication unit 330 determines whether the personal identification information acquired from the card information 372 matches the personal identification information acquired from the payment server 100 (S4010). If the personal identification information acquired from the card information 372 matches the personal identification information acquired from the payment server 100, the authentication unit 330 determines that personal authentication has been successful. Note that the authentication unit 330 does not perform personal authentication using the telephone number in S410, but may perform personal authentication using the telephone number if personal identification information cannot be obtained from the payment server 100. This point will be described in detail later.

[0124] If the authentication unit 330 is successful in authenticating the user, the card information providing unit 325 controls the communication unit 310 to transmit information about the affiliated card 57 (user ID and affiliated card number) to the payment server 100 (S411).

[0125] On the other hand, if the authentication unit 330 is not successful in authenticating the user, the card information providing unit 325 controls the communication unit 310 to send a notification to the user terminal device 200 indicating that the affiliated card 57 cannot be registered because the user cannot be authenticated. This makes it possible to prevent fraudulent use by others, such as "impersonation."

[0126] When the information management unit 140 of the payment server 100 acquires information (user ID and affiliated card number) related to the affiliated card 57 transmitted from the affiliated credit card company server 300, the information management unit 140 updates the user information 172 (S412). Specifically, the information management unit 140 records the affiliated card number in the user information 172 in association with the acquired user ID. This allows the issued affiliated card 57 to be registered as a card for credit payment in the payment server 100.

[0127] When the information management unit 140 has completed updating the user information 172, it controls the communication unit 110 to send a registration completion notice to the affiliated credit card company server 300 (S413). When the affiliated credit card company server 300 receives the registration completion notice from the payment server 100, it sends the registration completion notice to the user terminal device 200 (S414).

[0128] When the user terminal device 200 receives a registration completion notification from the affiliated credit card company server 300, it displays a registration completion screen on the display unit 220. The registration completion screen displays information (affiliated card number, etc.) about the affiliated card 57 registered in the payment server 100. This allows the user to understand that the affiliated card 57 has been registered as a card for credit payment with the payment server 100.

[0129] Figure 22 is a sequence diagram showing a second example of the processing related to card issuance / card registration according to the second embodiment. The sequence diagram shown in Figure 22 shows the processing when the payment server 100 does not hold the user's personal identification information and the user makes a registration request for the first affiliated card 57. Note that the processing of S501 to S508 in Figure 22 is the same as S401 to S408 in Figure 21, and therefore description thereof will be omitted.

[0130] In the payment server 100, if the identity of the user has not been verified by, for example, eKYC, the identity verification information of the user (e.g., name and date of birth) will not be recorded in the user information 172. In this case, when the information management unit 140 of the payment server 100 acquires the user ID transmitted from the affiliated credit card company server 300 in S508, it acquires the telephone number of the user linked to the acquired user ID from the user information 172. On the other hand, the information management unit 140 cannot acquire identity verification information (e.g., name and date of birth). Therefore, the information management unit 140 controls the communication unit 110 to transmit only the telephone number acquired from the user information 172 to the affiliated credit card company server 300 (S509).

[0131] If the authentication unit 330 of the affiliated credit card company server 300 is unable to acquire the user's identity verification information (e.g., name and date of birth) from the payment server 100, it authenticates the user. Specifically, the authentication unit 330 performs processing for 3DS authentication as identity authentication (S510). In 3DS authentication, identity authentication is performed using a one-time password, biometric authentication, or the like. If the 3DS authentication is successful, the authentication unit 330 determines that identity authentication has been successful.

[0132] If the authentication unit 330 is successful in authenticating the user (3DS authentication), the card information providing unit 325 controls the communication unit 310 to send information about the affiliated card 57 (user ID and affiliated card number) to the payment server 100 (S511).

[0133] On the other hand, if the authentication unit 330 is unsuccessful in authenticating the user (3DS authentication), the card information providing unit 325 controls the communication unit 310 to send a notification to the user terminal device 200 indicating that the affiliated card 57 cannot be registered because the user cannot be authenticated. This makes it possible to prevent fraudulent use by others, such as "impersonation." Note that the processing of S512 to S514 in Figure 22 is the same as S412 to S414 in Figure 21, and therefore a description thereof will be omitted.

[0134] Figure 23 is a sequence diagram showing a third example of processing related to card issuance / card registration according to the second embodiment. The sequence diagram shown in Figure 23 shows processing when the payment server 100 does not hold the user's personal identification information and the user requests registration of a second or subsequent affiliated card 57. Note that the processing of S601 to S608 in Figure 23 is the same as S401 to S408 in Figure 21, and therefore description thereof will be omitted.

[0135] In the payment server 100, if the identity of the user has not been verified by, for example, eKYC, the identity verification information of the user (e.g., name and date of birth) will not be recorded in the user information 172. In this case, when the information management unit 140 of the payment server 100 acquires the user ID transmitted from the affiliated credit card company server 300 in S608, it acquires the telephone number of the user linked to the acquired user ID from the user information 172. On the other hand, the information management unit 140 cannot acquire identity verification information (e.g., name and date of birth). Therefore, the information management unit 140 controls the communication unit 110 to transmit only the telephone number acquired from the user information 172 to the affiliated credit card company server 300 (S609).

[0136] If the authentication unit 330 of the affiliated credit card company server 300 is unable to obtain the user's identity verification information (e.g., name and date of birth) from the payment server 100, it authenticates the user. Specifically, the authentication unit 330 performs processing for SMS authentication as identity authentication (S610). In SMS authentication, the authentication unit 330 sends a short message containing a temporary authentication code to the user's phone number, and then authenticates the user based on the authentication code entered by the user. The above-mentioned 3DS authentication is not appropriate when multiple affiliated cards 57 have been issued, because it performs authentication by specifying the affiliated credit card number. For this reason, SMS authentication is performed when multiple affiliated cards 57 have been issued. If the SMS authentication is successful, the authentication unit 330 determines that identity authentication has been successful.

[0137] If the authentication unit 330 is successful in authenticating the user (SMS authentication), the card information providing unit 325 controls the communication unit 310 to send information about the affiliated card 57 (user ID and affiliated card number) to the payment server 100 (S611).

[0138] On the other hand, if the authentication unit 330 is not successful in authenticating the user (SMS authentication), the card information providing unit 325 controls the communication unit 310 to send a notification to the user terminal device 200 indicating that the affiliated card 57 cannot be registered because the user cannot be authenticated. This makes it possible to prevent fraudulent use by others, such as "impersonation." Note that the processing of S612 to S614 in Figure 23 is the same as S412 to S414 in Figure 21, and therefore description thereof will be omitted.

[0139] As described above, the affiliated credit card company server 300 (information processing device) of the embodiment includes an issuance request acquisition unit 340, an issuance unit 345, and a naming unit 350. The issuance request acquisition unit 340 acquires an issuance request for an affiliated card 57 (credit card). The issuance unit 345 issues an affiliated card number for the affiliated card 57 based on the issuance request. When multiple affiliated card numbers are issued for one account of a user, the naming unit 350 assigns different display names (arbitrary names) to each of the multiple affiliated cards 57 corresponding to the multiple affiliated card numbers based on instructions from the user. This allows the user to easily distinguish between the affiliated cards 57 even when multiple affiliated cards 57 are registered for one account of the user.

[0140] The information processing system of the embodiment also includes an affiliated credit card company server 300 (information processing device) and a payment application 20. The payment application 20 is an application program installed on a user terminal device 200 operated by a user for using an electronic payment service that performs electronic payments using code information. The payment application 20 causes the user terminal device 200 to display a display name (an arbitrary name) assigned to the affiliated card 57 when making a credit payment in the electronic payment service. This allows the user to easily identify the affiliated card 57 to be used for electronic payment, even if multiple affiliated cards 57 are registered to one user account.

[0141] The above describes the form for carrying out the present invention using an embodiment, but the present invention is not limited to such an embodiment, and various modifications and substitutions can be made within the scope that does not deviate from the gist of the present invention. [Explanation of symbols]

[0142] 20. Payment App 50 First store terminal device 55 Credit card processing terminal 57 Affiliated Cards 100 Payment Server 110 Communications Department 120 Payment Contents Department 130 Payment processing unit 140 Information Management Department 170 Storage section 172 User information 200 User terminal device 210 Communications Department 220 Display section 230 Input section 240 Control Unit 250 Storage section 300 Affiliated credit card company server 310 Communications Department 315 Reception Department 320 Personal Identification Information Acquisition Department 325 Card Information Department 330 Authentication Department 335 Confirmation Department 340 Issuance Request Acquisition Department 345 Publishing Department 350 Naming Department 355 Name Change Department 360 Printing Data Provider 370 Storage section 372 Card Information

Claims

1. An information processing device capable of communicating with an external server, a storage unit that stores first information that is personal identification information of a credit card user; a reception unit that receives a request to register the credit card to the external server; an acquisition unit that acquires second information, which is personal identification information of the user, from the external server; a card information providing unit that provides information about the credit card to the external server when the first information and the second information match; An information processing device comprising:

2. further comprising an authentication unit that performs identity authentication of the user when the second information cannot be acquired from the external server; the card information providing unit provides information about the credit card to the external server when the identity authentication by the authentication unit is successful.

2. The information processing device according to claim 1.

3. the authentication unit, when the registration request is a registration request for the first credit card of the user, performs processing for 3DS (3-D Secure) authentication as the identity authentication.

3. The information processing device according to claim 2.

4. the authentication unit performs processing for SMS (Short Message Service) authentication as the identity authentication when the registration request is a registration request for the second or subsequent credit card of the user.

3. The information processing device according to claim 2.

5. the card information providing unit provides information about the plurality of credit cards to the external server when the plurality of credit cards have been issued to the user and the first information and the second information match; 2. The information processing device according to claim 1.

6. the card information providing unit, when a plurality of credit cards have been issued to the user and the first information and the second information match, provides information on the credit card selected by the user from the plurality of credit cards to the external server; 2. The information processing device according to claim 1.

7. a confirmation unit that confirms whether account linkage is performed between the external server and the information processing device; the acquisition unit, when the account linkage is performed, transmits, to the external server, identification information for the external server to identify the user, and acquires the second information from the external server.

2. The information processing device according to claim 1.

8. the information processing device further includes a confirmation unit that confirms whether account linkage is performed between the external server and a second external server different from the external server; the acquisition unit, when the account linkage is performed, transmits, to the external server, identification information for the second external server to identify the user, and acquires the second information from the external server.

2. The information processing device according to claim 1.

9. An information processing device capable of communicating with an external server, storing first information which is personal identification information of a credit card user; Accepting a request to register the credit card to the external server; acquire second information, which is personal identification information of the user, from the external server; If the first information and the second information match, provide information about the credit card to the external server. Information processing methods.

10. An information processing device capable of communicating with an external server, storing first information which is personal identification information of a credit card user; Accepting a request to register the credit card to the external server; acquiring second information, which is personal identification information of the user, from the external server; If the first information and the second information match, the external server is caused to provide information about the credit card. program.

Images