Card determination system, card determination method, and program

Abstract

Enable management according to the user's card. 【Solution means】The usage setting request reception unit (101) of the card determination system (1) receives a usage setting request regarding the usage setting of the card used by the user in a predetermined service from the user's user terminal. When a usage setting request is received, the card determination unit (102) determines whether the card is a virtual card or a physical card.

Description

Technical Field

[0001] The present disclosure relates to a card determination system, a card determination method, and a program.

Background Art

[0002] Conventionally, services that allow a user to use a card such as a credit card have been known. For example, in Patent Document 1, in order for a user to shop on the Internet, a virtual card having the same card information as a physical card, which is a physical credit card, is issued separately from the physical card, and the user can use the virtual card for shopping. A wallet device is described.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, although the wallet device of Patent Document 1 issues a virtual card that can be used by a user for shopping, it does not manage the user's physical card and virtual card separately from each other. This is the same for other technologies other than the wallet device of Patent Document 1. In the conventional technology, the physical card and the virtual card are not distinguished from each other, and the management of the cards applied for by the user is not sufficient.

[0005] One of the objects of the present disclosure is to enable management according to a user's card.

Means for Solving the Problems

[0006] The card determination system according to the present disclosure includes a usage setting request reception unit that receives, from a user's user terminal, a usage setting request regarding the usage setting of a card used by the user for a predetermined service, and a card determination unit that determines whether the card is a virtual card or a physical card when the usage setting request is received.

Effect of the Invention

[0007] The present disclosure can enable management according to the user's card.

Brief Description of the Drawings

[0008]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Embodiments for Carrying Out the Invention

[0009] [1. Hardware Configuration of Card Determination System] An example of an embodiment of a card determination system, a card determination method, and a program according to the present disclosure will be described. FIG. 1 is a diagram showing an example of the hardware configuration of the card determination system. For example, the card determination system 1 includes a settlement server 10, a card server 20, and a user terminal 30. Each of the settlement server 10, the card server 20, and the user terminal 30 is connected to a network N such as the Internet or a LAN.

[0010] The settlement server 10 is a server computer for settlement services. The settlement service is a service that provides users with electronic settlement (cashless settlement). For example, the settlement server 10 includes a control unit 11, a storage unit 12, and a communication unit 13. The control unit 11 includes at least one processor. The storage unit 12 includes at least one of a volatile memory such as a RAM and a non-volatile memory such as a flash memory. The communication unit 13 includes at least one of a communication interface for wired communication and a communication interface for wireless communication.

[0011] The card server 20 is a server computer for card services. The card service is a service using a card. The card service can be coordinated with the settlement service. The card used in the card service can be any card. For example, the card may be a credit card, a cash card, a debit card, a transportation card, an electronic money card, a point card, a membership card, a personal number card used as an identity certificate, or other cards. The operator of the settlement service and the operator of the card service may be the same or different.

[0012] In this embodiment, a credit card is described as an example of a card. Therefore, wherever the term "card" is used in this embodiment, it means a credit card. The card service of this embodiment is a service provided by the card company that issued the card. For example, the card service is a service that enables payment using the card, application for installment payment, application for bonus payment, or change of the user's registration information. The card server 20 includes a control unit 21, a storage unit 22, and a communication unit 23. The hardware configurations of the control unit 21, the storage unit 22, and the communication unit 23 may be the same as those of the control unit 11, the storage unit 12, and the communication unit 13, respectively.

[0013] The user terminal 30 is the user's computer. For example, the user terminal 30 is a smartphone, a tablet, a personal computer, or a wearable terminal. The user terminal 30 includes a control unit 31, a storage unit 32, a communication unit 33, an operation unit 34, and a display unit 35. The hardware configurations of the control unit 31, the storage unit 32, and the communication unit 33 may be the same as those of the control unit 11, the storage unit 12, and the communication unit 13, respectively. The communication unit 33 may be capable of NFC (Near Field Communication). The operation unit 34 is an input device such as a touch panel or a mouse. The display unit 35 is a display such as a liquid crystal or an organic EL.

[0014] Note that the programs stored in the storage units 12, 22, and 32 may be supplied to the payment server 10, the card server 20, or the user terminal 30 via the network N. Also, at least one of a reading unit (for example, a memory card slot) for reading a computer-readable information storage medium and an input / output unit (for example, a USB port) for inputting / outputting data to / from an external device may be included in the payment server 10, the card server 20, or the user terminal 30. For example, a program stored in the information storage medium may be supplied to the payment server 10, the card server 20, or the user terminal 30 via at least one of the reading unit and the input / output unit.

[0015] Also, the card determination system 1 may include at least one computer. The computer included in the card determination system 1 is not limited to the example of FIG. 1. For example, the card determination system 1 may include only the payment server 10 and the user terminal 30. In this case, the card server 20 exists outside the card determination system 1. The card determination system 1 may include only the payment server 10. In this case, the card server 20 and the user terminal 30 exist outside the card determination system 1. For example, the card determination system 1 may include the payment server 10 and other computers not shown in FIG. 1.

[0016] [2. Overview of Card Determination System] In this embodiment, the user applies to the card company for the issuance of a card. The application for the issuance of a card may be made in accordance with known procedures. For example, the user operates the user terminal 30 to access the website of the card company. The user inputs information (e.g., phone number) required for card issuance to the website of the card company. At least a part of the information required for card issuance may be diverted from other services such as e-commerce services. The user operates the user terminal 30 to upload the identification documents required for card issuance. The application for the issuance of a card may be made offline. For example, the user may apply for card issuance in writing.

[0017] For example, when the user has completed the application for card issuance, the card company conducts a review for card issuance. The review may be conducted in accordance with known procedures and criteria. When the user passes the review, the card company issues a physical card, which is a physical card. The physical card may be of a known type. For example, the physical card may be an IC card compatible with NFC, an IC card not compatible with NFC, a magnetic card, or other types. The card company sends the physical card to the address specified by the user. The user receives the physical card from the card company via a delivery service provider. Through such a process, the user can use the physical card.

[0018] For example, after a user passes the review, it takes a certain amount of time for the physical card to reach the user's hands. This time can be about several days or even more than a week. During this period, since the user has not received the physical card, the physical card cannot be used. For example, even if the user tries to use the physical card for a payment service, without the physical card in hand, the card number cannot be known. The user also cannot know the security code written on the back of the physical card.

[0019] Therefore, in this embodiment, the user can use a virtual card, which is a virtual card, until the physical card arrives. A virtual card is a card without a physical entity. In other words, a virtual card can also be said to be a card that the user can use until the physical card arrives. The information of the virtual card may basically be the same as that of the physical card. For example, the card number, expiration date, cardholder name, and security code of the virtual card are the same as those of the physical card respectively. Note that at least a part of the information of the virtual card and at least a part of the information of the physical card may be different.

[0020] Note that the virtual card is not limited to a card whose credit card information can be used for payments or the like until the physical card reaches the user. A virtual card may be a card whose credit card information such as the card number and expiration date can be used for payments or the like without issuing a physical card. For example, the virtual card may not only be for temporary use, but also only virtual cards may be issued according to the user's request. In this embodiment, although it is described as a card, it means that the credit card information such as the card number and expiration date is issued, rather than being issued in the form of a card.

[0021] Hereinafter, when virtual cards and physical cards are not distinguished, they are simply referred to as cards. In this embodiment, the user can use virtual cards in the payment service until the physical cards are delivered. The user can use any payment method in the payment service. The payment method is the method used by the user for payment. For example, the payment method may be a credit card, electronic money, points, cryptocurrency, debit card, wallet, an account such as a bank account, or other means. Codes such as barcodes or two-dimensional codes are also means for payment, so they correspond to payment methods. Since the payment method may be used for payment, it can also be called a payment means.

[0022] In this embodiment, an example is given where the user executes payment using the payment application installed on the user terminal 30. The payment application is an application provided by an operator who operates the payment service. For example, if the user has not yet registered as a member of the payment service, the user registers as a member of the payment service from the payment application. When the user installs the payment application on the user terminal 30, the user activates the payment application for member registration of the payment service. For example, the user performs the procedure for registering as a member of the payment service from the payment application.

[0023] FIG. 2 is a diagram showing an example of the process of the user registering as a member of the payment service. In this embodiment, when the user proceeds with the member registration of the payment service, as shown in the upper left of FIG. 2, the user terminal 30 causes the display unit 35 to display a pre-authentication screen SC1 that requests pre-authentication from the user. Pre-authentication is authentication performed before the first authentication and the second authentication described later. For example, pre-authentication is performed at the time of member registration.

[0024] In this embodiment, telephone authentication will be described as an example of pre-authentication. Telephone authentication is authentication in which at least one of an outgoing call and an incoming call is used. The method of telephone authentication may be the same as a known method. For example, telephone authentication is performed by matching the telephone number entered by the user during membership registration for the payment service with the telephone number called by the user from the pre-authentication screen SC1. Telephone authentication is performed depending on whether the telephone number entered during membership registration for the payment service is called and an incoming call is received on the pre-authentication screen SC1.

[0025] For example, when pre-authentication, taking telephone authentication as an example, is successful, as shown in the upper right of FIG. 2, the user terminal 30 causes the display unit 35 to display a payment source setting screen SC2 for accepting the designation of a payment source in the payment service. The payment source is a payment means used in the payment of the payment service. The user can specify any payment source. For example, at the time of membership registration for the payment service, when the user passes the card review and has not yet received the physical card, the user can specify the virtual card as the payment source. At the time of membership registration for the payment service, when the user has already received the physical card, the user can specify the physical card as the payment source. The user can specify a payment means other than a card as the payment source.

[0026] In this embodiment, when the user passes the card review, the card server 20 cooperates with the payment server 10 to exchange information such as the card number. In the example in the upper right of FIG. 2, based on the exchanged information, a button B20 for designating the card as the payment source is displayed on the payment source setting screen SC2. For example, even if the physical card has not yet arrived, the user can set the virtual card as the payment source by selecting the button B20. However, in this embodiment, it is assumed that a predetermined authentication is required for the user to set the virtual card as the payment source. Hereinafter, the authentication for the user to set the virtual card as the payment source will be referred to as the first authentication.

[0027] On the other hand, when the payment source setting screen SC2 is displayed, the user may already have received the physical card. In this case, the user can use the physical card as the payment source. In the present embodiment, it is assumed that a predetermined authentication is required even when the user sets the physical card as the payment source. Hereinafter, the authentication for the user to set the physical card as the payment source is referred to as the second authentication. For example, even when a user who is using a virtual card (a user who has completed the first authentication) receives a physical card, the second authentication may or may not be required. Thus, in the present embodiment, the authentication required of the user differs depending on whether the user's card is a virtual card or a physical card.

[0028] FIG. 3 is a diagram showing an example of the flow in which the user performs the first authentication. When the user selects the button B20 in the state of the payment source setting screen SC2 at the upper left of FIG. 3, as shown in the upper right of FIG. 3, the user terminal 30 causes the payment source setting screen SC2 to display a modal M21 for the user to start the first authentication. In the present embodiment, the case where attribute authentication is executed as the first authentication is taken as an example. Attribute authentication is authentication in which the attributes of the user are confirmed. In other words, attribute authentication is authentication in which information capable of proving that the user is the person himself / herself is confirmed. The specific method of attribute authentication may be the same as a known method.

[0029] In the present embodiment, the case where two attributes, the user ID and the phone number, are confirmed in the first authentication as the attributes of the user is taken as an example. The user ID is an ID that can identify the user in the payment service. The user ID may be common to the payment service and the card service. The user ID may further be common to other services other than the payment service and the card service. The user ID may be an ID that is not common to other services other than the payment service and is valid only for the payment service.

[0030] For example, when the user selects button B22, the first authentication is executed. If the first authentication fails, the user cannot use the virtual card for the payment service. If the first authentication is successful, as shown in the lower left of FIG. 3, the user terminal 30 causes the payment source setting screen SC2 to display a window W23 indicating that the first authentication has been successful. Since the first authentication is successful, the virtual card is set as the payment source. When the user selects button B24, as shown in the lower right of FIG. 3, the user terminal 30 causes the display unit 35 to display a top screen SC3 corresponding to the first view of the payment application.

[0031] For example, the top screen SC3 includes a code C30 generated based on a code ID that can temporarily identify the user. The code C30 is at least one of a barcode and a two-dimensional code. When the code C30 is read at a store that subscribes to the payment service, the payment is executed based on the payment means set as the payment source. In the example in the lower right of FIG. 3, since the virtual card is set as the payment source, the payment is executed based on the virtual card. The virtual card is not displayed visually on the top screen SC3. Note that the virtual card may be displayed visually on the top screen SC3.

[0032] Note that the payment is not limited to the type in which the code C30 displayed on the user terminal 30 is read. The payment may be of any type. For example, the payment may be of a type in which the user terminal 30 reads a code displayed on the terminal of the store, a type in which the user terminal 30 reads a code posted in the store, a type that is completed only by an operation on the user terminal 30 (e.g., ID payment or account payment), a type in which the IC chip of the user terminal 30 is used, a carrier payment that is a payment using the carrier used by the user terminal 30, or other types.

[0033] FIG. 4 is a diagram showing an example of the process of a user performing a second authentication. In the state of the payer setting screen SC2 at the upper left of FIG. 4, when the user selects the button B20, as shown at the upper right of FIG. 4, the user terminal 30 causes a modal M25 for starting the second authentication to be displayed on the payer setting screen SC2. In the present embodiment, a case where possession authentication is executed as the second authentication is taken as an example. Possession authentication is authentication for confirming that the user has a card. The specific method of possession authentication may be the same as a known method. For example, the possession authentication may be scan authentication performed by reading a card.

[0034] In the present embodiment, as an example, a case where card reading (scanning) using the NFC function of the communication unit 33 is performed to confirm that the user has a card is taken. For example, when the user reads a card, the second authentication is executed. If the second authentication fails, the user cannot use the physical card for the payment service. If the second authentication is successful, as shown at the lower left of FIG. 4, the user terminal 30 causes a window W26 indicating that the second authentication has been successful to be displayed on the payer setting screen SC2. Since the second authentication is successful, the physical card is set as the payer. When the user selects the button B27, as shown at the lower right of FIG. 4, the user terminal 30 causes the top screen SC3 including the code C30 to be displayed on the display unit 35.

[0035] As described above, the card determination system 1 of the present embodiment determines whether the user's card is a virtual card or a physical card when the usage setting of the payer is performed. When the user's card is a virtual card, the card determination system 1 executes the first authentication to set the virtual card as the payer. When the user's card is a physical card, the card determination system 1 executes the second authentication to set the physical card as the payer. Thereby, the card determination system 1 can perform flexible management according to the card. Hereinafter, the details of the card determination system 1 will be described.

[0036] [3. Functions Realized by the Card Determination System] FIG. 5 is a diagram showing an example of functions realized by the card determination system 1. Each part realized by the card determination system 1 can be configured by integrating them into one device or further dispersing the devices more finely.

[0037] [3-1. Functions Realized by the Settlement Server] For example, the settlement server 10 includes a data storage unit 100, a usage setting request reception unit 101, a card determination unit 102, a pre-authentication execution unit 103, a first authentication execution unit 104, a first usage setting unit 105, a second authentication execution unit 106, and a second usage setting unit 107. The data storage unit 100 is realized by the storage unit 12. Each of the usage setting request reception unit 101, the card determination unit 102, the pre-authentication execution unit 103, the first authentication execution unit 104, the first usage setting unit 105, the second authentication execution unit 106, and the second usage setting unit 107 is realized by the control unit 11.

[0038] [Data Storage Unit] The data storage unit 100 stores data necessary for the settlement service. For example, the data storage unit 100 stores the settlement database DB1.

[0039] FIG. 6 is a diagram showing an example of the settlement database DB1. The settlement database DB1 is a database in which various types of information related to users in the settlement service are stored. For example, the user ID, password, code ID, phone number, settlement means information, payment source information, and charge source information are stored in the settlement database DB1. Other data may be stored in the settlement database DB1. For example, usage history information related to the usage history of the settlement service may be stored in the settlement database DB1.

[0040] The user ID is an example of user identification information that can identify a user. Separate from the user ID, there may be an account for login. The login account may be allowed to be freely changed by the user. The login account is also an example of user identification information. The password is information confirmed at the time of login. Since the code ID is also an ID that can identify the user in the payment service, it is an example of user identification information. The code ID is updated every time the code C30 is displayed. The user identification information may be other information other than the user ID, the login account, and the code ID.

[0041] In this embodiment, an example is given where the user ID is common in both the payment service and the card service. Further, an example is given where the user ID is common in other services such as e-commerce services. For example, when a user starts membership registration for a payment service, the user uses the information already issued by the card service or other services to execute a predetermined login process. When the login process is successful, the payment server 10 creates a record of the user in the payment database DB1 and stores information such as the user ID in the record. Some information in the record may not be stored at the start of membership registration. As the user proceeds with the membership registration, information may be registered in the record.

[0042] The phone number stored in the payment database DB1 is the phone number used in pre-authentication. The payment method information is information that can identify the payment methods available to the user in the payment service. The payment methods indicated by the payment method information can be said to be payment methods that are candidates for at least one of the payer and the charger. For example, the payment method information is information such as a credit card number, information such as an electronic money number, information such as a bank account, or information such as a point card number.

[0043] In this embodiment, when the user passes the card review, the payment server 10 obtains the card information of the virtual card from the card server 20. The payment server 10 may obtain the card information of the virtual card immediately after the user passes the card review. In this case, the payment server 10 may obtain the user ID from the card server 20 so as to be able to identify which user's virtual card it is. The payment server 10 may store the user ID and card information obtained from the card server 20 in the payment database DB1 before the user starts the membership registration for the payment service.

[0044] For example, the payment server 10 may obtain the card information of the virtual card from the card server 20 when the user starts the membership registration for the payment service. The payment server 10 may store the card information of the virtual card in the payment database DB1 as one of the payment means information. Based on the card information stored as one of the payment means information, the button B20 on the payer setting screen SC2 is displayed. The payer information stored in the payment database DB1 is information that can identify the payment means set for the payer. The charging source information stored in the payment database DB1 is information that can identify the payment means set for the charging source. Charging is a process of increasing the balance of electronic money. The charging source is the payment means that is the source of the charge.

[0045] Note that the data stored in the data storage unit 100 is not limited to the above example. The data storage unit 100 may store the data necessary for the payment service. For example, the data storage unit 100 may store the data necessary for the display of each of the pre-authentication screen SC1, the payer setting screen SC2, and the top screen SC3. The data storage unit 100 may store the data necessary for each of the pre-authentication, the first authentication, and the second authentication.

[0046] [Usage Setting Request Reception Unit] The usage setting reception unit 101 receives, from the user terminal 30, a usage setting request regarding the usage setting of the card used by the user in the payment service. The payment service is an example of a predetermined service. Therefore, the places described as the payment service can be read as the predetermined service. The predetermined service is not limited to the payment service. The predetermined service may be any service in which the user can use the card. For example, the predetermined service may be an e-commerce service, a travel reservation service, a ticket reservation service, a communication service, an online free market service, a financial service, or other services.

[0047] The usage setting is a setting regarding the usage of the card. For example, whether to use the card in a predetermined service corresponds to the usage setting. To what extent to use the card in a predetermined service corresponds to the usage setting. When the user can use multiple cards, the priority order at the time of use set for each card corresponds to the usage setting. The usage setting may be a setting for changing the upper limit amount of the card. The usage setting is not limited to the setting of the payment application, and may be a setting for touch payment. The usage setting may be a new usage setting or an update of an existing usage setting. The usage setting request is data indicating that it is a request for a usage setting. In the examples of FIGS. 2 to 4, the data indicating that the user has selected the button B20 corresponds to the usage setting request. The usage setting request may be data indicating that the user has performed other operations for the usage setting. The usage setting request may be transmitted from the user terminal 30 without the user performing any special operations.

[0048] In this embodiment, since a predetermined service is a payment service in which payment is executed based on a card, the usage setting request reception unit 101 receives a usage setting request regarding the usage setting of the payment source or recharge source used by the user in the payment service. In the examples of FIGS. 3 and 4, the case where the usage setting of the payment source is performed is taken as an example, but the usage setting request may be the usage setting of the recharge source. For example, data indicating that the user has designated a virtual card or a physical card as the recharge source may correspond to the usage setting request. Note that the usage setting may be other settings other than the payment source or the recharge source. For example, the usage setting may be a setting for using the card for identity verification. When the card is used for other purposes in a predetermined service, there may be usage settings for other purposes.

[0049] [Card determination unit] When a usage setting request is received, the card determination unit 102 determines whether the card is a virtual card or a physical card. In this embodiment, the card determination unit 102 obtains a card flag indicating whether the card is a virtual card or a physical card from the card server 20, and determines whether the card is a virtual card or a physical card based on the card flag. For example, the card flag indicates either a first value indicating that the card is a virtual card or a second value indicating that the card is a physical card.

[0050] For example, the card determination unit 102 requests the card server 20 to acquire a card flag. The card determination unit 102 shall also request the card server 20 for user identification information that can identify the user for whom the card flag is to be acquired. The card server 20 may store the card flag itself, or may store only the information necessary for generating the card flag (for example, the delivery history information described later) without storing the card flag. In this embodiment, the case where the card server 20 stores the card flag itself is taken as an example. The card determination unit 102 acquires the card flag stored in the card server 20 from the card server 20. When the card flag is the first value, the card determination unit 102 determines that the card is a virtual card. When the card flag is the second value, the card determination unit 102 determines that the card is a physical card.

[0051] In this embodiment, when a usage setting request is received before the physical card is issued and delivered to the user, the card determination unit 102 determines that the card is a virtual card. The card flag or the delivery history information stored in the card server 20 is used for this determination. When a usage setting request is received after the physical card is issued and delivered to the user, the card determination unit 102 determines that the card is a physical card. The card flag or the delivery history information stored in the card server 20 is also used for this determination. Other information than the card flag or the delivery history information may be used for these determinations. An example of other information will be described in the modification example later.

[0052] Note that the card flag may be stored in the settlement database DB1. In this case, the card determination unit may determine whether the card is a virtual card or a physical card based on the card flag stored in the settlement database DB1 without requesting the card flag from the card server 20. Also, the delivery history information may be stored in the settlement database DB1. In this case as well, the card determination unit 102 may determine whether the card is a virtual card or a physical card based on the delivery history information stored in the settlement database DB1 without requesting the card flag from the card server 20.

[0053] Also, the card flag or the delivery history information may be stored in another database other than the settlement database DB1, another computer other than the settlement server 10 and the card server 20, or an external information storage medium. In this case, the card determination unit 102 may acquire the card flag or the delivery history information from the other database, the other computer, or the external information storage medium, and determine whether the card is a virtual card or a physical card based on the acquired delivery history information.

[0054] [Pre-authentication Execution Unit] The pre-authentication execution unit 103 executes pre-authentication. In this embodiment, an example is given where the pre-authentication execution unit 103 executes pre-authentication before a usage setting request is received. The pre-authentication execution unit 103 may execute pre-authentication after a usage setting request is received. For example, the pre-authentication execution unit 103 may execute pre-authentication when a usage setting request is received and the user has not performed pre-authentication. Thereafter, the first authentication by the user may be executed.

[0055] The pre - authentication is a different authentication from the first authentication and the second authentication. In this embodiment, the case where telephone authentication corresponds to the pre - authentication is taken as an example. The pre - authentication may be other authentication than telephone authentication. For example, the pre - authentication may be SMS authentication, email authentication, biometric authentication, password authentication, password phrase authentication, or other authentication. The authentication information used in these pre - authentications may be diverted in at least one of the first authentication and the second authentication.

[0056] For example, when a call to the user from the payment service is used, the pre - authentication execution unit 103 executes pre - authentication by determining whether the user responds to the call to the user's telephone number. The user's telephone number may be input by the user during membership registration of the payment service, or may be the telephone number registered in another service such as a card service. The pre - authentication execution unit 103 determines that the pre - authentication is successful when the user responds to the call. The pre - authentication execution unit 103 determines that the pre - authentication has failed when the user does not respond to the call.

[0057] For example, when the user responds to a call from the payment service, authentication information such as a password may be conveyed by voice. In this case, the pre - authentication execution unit 103 may execute pre - authentication by determining whether the authentication information input by the user to the user terminal 30 matches the authentication information conveyed by voice. The pre - authentication execution unit 103 determines that the pre - authentication is successful when these authentication information match. The pre - authentication execution unit 103 determines that the pre - authentication has failed when these authentication information do not match.

[0058] For example, when a call from the user to the payment service is used, the pre - authentication execution unit 103 executes pre - authentication by determining whether there is a call from the user's telephone number to the payment service's telephone number. The pre - authentication execution unit 103 determines that the pre - authentication is successful when there is a call from the user's telephone number. The pre - authentication execution unit 103 determines that the pre - authentication has failed when there is no call from the user's telephone number.

[0059] Note that the pre - authentication execution unit 103 may execute processing according to the authentication method adopted as pre - authentication. For example, when SMS authentication, e - mail authentication, biometric authentication, password authentication, passphrase authentication, or other authentication corresponds to pre - authentication, the pre - authentication execution unit 103 may obtain the authentication information necessary for these authentications from the user terminal 30 and execute pre - authentication based on the authentication information. The authentication information necessary for pre - authentication may also be well - known information used in these authentications.

[0060] [First Authentication Execution Unit] The first authentication execution unit 104 executes the first authentication when it is determined that the user's card is a virtual card. The first authentication execution unit 104 may execute at least a part of the processing necessary for the first authentication. For example, the first authentication execution unit 104 executes the first authentication in which user information about the user, which is managed by the card server 20 of the card issuer that issued the card, is confirmed. The card server 20 is an example of a card issuer system. Therefore, the part where the card server 20 is described can be read as the card issuer system. The card issuer system may include the card server 20 and other computers other than the card server 20.

[0061] The user information is the authentication information used in the first authentication. In this embodiment, since the first authentication is attribute authentication, the user information indicates the attributes of the user. For example, the user information indicates the user ID and the phone number. The user information may be any information about the user. The user information is not limited to the user ID and the phone number. For example, the user information may be only the user ID or only the phone number. The user information may be the user's name, date of birth, address, or other information.

[0062] In this embodiment, an example is given where the verification of the validity of user information is performed by the card server 20. For example, the first authentication execution unit 104 acquires user information to be verified in the first authentication. The first authentication execution unit 104 may acquire the user information from the user terminal 30 or another computer. The first authentication execution unit 104 transmits the user information to the card server 20 and requests verification of its validity. The first authentication execution unit 104 may make a request to the card server 20 via another computer such as a gateway.

[0063] For example, the first authentication execution unit 104 acquires verification result information regarding the verification result of the user information from the card server 20, and based on the verification result information, executes the first authentication. The verification result information indicates either a valid value meaning that it is valid or an invalid value meaning that it is not valid. The first authentication execution unit 104 determines that the first authentication has succeeded when the verification result information is a valid value. The first authentication execution unit 104 determines that the first authentication has failed when the verification result information is an invalid value.

[0064] In this embodiment, when it is determined that the user's card is a virtual card, the first authentication execution unit 104 executes the first authentication based on the authentication information authenticated in the pre-authentication. The authentication information authenticated in the pre-authentication is the authentication information whose validity has been verified in the pre-authentication. For example, the first authentication execution unit 104 executes the first authentication based on the phone number authenticated in the pre-authentication. The phone number among the user information to be verified in the first authentication is the phone number verified in the pre-authentication. Therefore, the user can execute the first authentication without entering the phone number again.

[0065] For example, when it is determined that the card is a virtual card, the first authentication execution unit 104 may execute a first authentication in which the authentication information regarding the user held on the card administrator (e.g., card company) side is compared with the authentication information regarding the user at the time of receiving the usage setting request. For example, the authentication information regarding the user at the time of receiving the usage setting request may be the authentication information regarding the user held in the settlement server 10. The authentication information regarding the user at the time of receiving the usage setting request may also be the authentication information regarding the user acquired from the user terminal 30.

[0066] In this embodiment, the case where the above authentication information is user information is taken as an example, but the authentication information may be other information rather than information regarding the user. For example, the authentication information may be other information such as a password. For example, it may be authentication information (e.g., authentication code) issued from the card server 20 (card company). The first authentication execution unit 104 acquires the confirmation result information, which is the result of these comparisons, from the card server 20, and executes the first authentication by referring to the confirmation result information. When the confirmation result information indicates a match, the first authentication execution unit 104 determines that the first authentication has succeeded; when the confirmation result information does not indicate a match, the first authentication execution unit 104 determines that the first authentication has failed. The authentication information regarding the user may be the authentication information at the time of applying for the card.

[0067] Note that the first authentication execution unit 104 may execute the first authentication without making a request to the card server 20. In this case, the first authentication execution unit 104 may request another computer other than the card server 20 to confirm the validity of the user information. The first authentication execution unit 104 may acquire the confirmation result information from another computer and execute the first authentication based on the confirmation result information. Another computer executes the same processing as the processing described as being executed by the card server 20. Another computer transmits the confirmation result information indicating the processing result to the settlement server 10.

[0068] Further, the first authentication execution unit 104 may execute the first authentication without making a request to the card server 20 or the like. When the information necessary for the first authentication is stored in the data storage unit 100, the first authentication execution unit 104 may execute the first authentication so as to be completed only within the settlement server 10. The first authentication execution unit 104 may execute the first authentication by comparing the authentication information regarding the user held on the card administrator side with the authentication information regarding the user at the time of receiving the usage setting request. For example, when these match, the first authentication execution unit 104 determines that the first authentication has succeeded, and when these do not match, the first authentication execution unit 104 determines that the first authentication has failed.

[0069] [First Usage Setting Unit] The first usage setting unit 105 performs usage setting based on the execution result of the first authentication. For example, when the first authentication succeeds, the first usage setting unit 105 performs usage setting for the virtual card. When the first authentication fails, the first usage setting unit 105 does not perform usage setting for the virtual card. In the present embodiment, the first usage setting unit 105 performs usage setting by updating the payer information or recharge source information stored in the settlement database DB1. For example, the first usage setting unit 105 updates the payer information or recharge source information so that the payer information or recharge source information indicates the virtual card.

[0070] Note that the first usage setting unit 105 may perform usage setting by storing the usage setting information in the settlement database DB1 or another database. For example, when it is indicated in other information other than the payer information and recharge source information whether the user uses the virtual card, the first usage setting unit 105 may perform usage setting by generating or updating the other information. When the usage setting is a change in the upper limit amount of the card, the first usage setting unit 105 may perform usage setting by changing the information indicating the upper limit amount. When the usage setting is other content, the first usage setting unit 105 may perform usage setting by generating or updating the information indicating the other content.

[0071] [Second Authentication Execution Unit] When it is determined that the user's card is a physical card, the second authentication execution unit 106 executes the second authentication. The second authentication is different from the first authentication. For example, the second authentication may be an authentication that cannot succeed without a physical card. The second authentication may be performed not only by reading the physical card, but also by photographing the physical card, inputting characters or numbers printed on the physical card, or other actions. The second authentication may be an authentication in which the physical card is not particularly used. For example, the second authentication may be an authentication with higher security than the first authentication. The second authentication can also be said to be an authentication using authentication information different from the first authentication.

[0072] In this embodiment, since the second authentication is possession authentication, when it is determined that the card is a physical card, the second authentication execution unit 106 executes the second authentication using the physical card. Each of the second authentications may be any authentication and is not limited to the examples of this embodiment. For example, the second authentication may be an authentication called 3D Secure. 3D Secure is an authentication using a password previously registered by the user. The second authentication may be other authentications such as an authentication called CVV2 or biometric authentication. When the second authentication is another authentication, the second authentication execution unit 106 may execute the second authentication based on the authentication information corresponding to the second authentication.

[0073] In this embodiment, an example is given where the validity confirmation of the card information obtained from the physical card is executed by the card server 20. For example, the second authentication execution unit 106 acquires the card information to be confirmed in the second authentication. For example, the second authentication execution unit 106 acquires the card information stored in the IC chip of the physical card. The card information may be any information stored in the IC chip of the physical card, and for example, may be a card number, an electronic money number in a card with an electronic money function, a point number in a card with a point card function, or other information. The second authentication execution unit 106 transmits the card information to the card server 20 and requests a validity confirmation. The second authentication execution unit 106 may make a request to the card server 20 via another computer such as a gateway.

[0074] For example, the second authentication execution unit 106 acquires confirmation result information regarding the confirmation result of the card information from the card server 20, and executes the second authentication based on the confirmation result information. The confirmation result information indicates either a legitimate value that means it is legitimate or an improper value that means it is not legitimate. The second authentication execution unit 106 determines that the second authentication has succeeded when the confirmation result information is a legitimate value. The second authentication execution unit 106 determines that the second authentication has failed when the confirmation result information is an improper value.

[0075] Note that the second authentication execution unit 106 may execute the second authentication without making a request to the card server 20. In this case, the second authentication execution unit 106 may request another computer other than the card server 20 to confirm the legitimacy of the card information. The second authentication execution unit 106 may acquire the confirmation result information from another computer and execute the second authentication based on the confirmation result information. Another computer executes the same processing as the processing described as being executed by the card server 20. Another computer transmits the confirmation result information indicating the processing result to the settlement server 10.

[0076] Also, the second authentication execution unit 106 may execute the second authentication without making a request to the card server 20 or the like. When the information necessary for the second authentication is stored in the data storage unit 100, the second authentication execution unit 106 may execute the second authentication so as to be completed only within the settlement server 10. For example, the data storage unit 100 stores authentication information such as card information that is the correct answer at the time of the second authentication. The second authentication execution unit 106 executes the second authentication based on the authentication information that becomes the correct answer stored in the data storage unit 100 and the authentication information obtained by reading the physical card or the like.

[0077] [Second Usage Setting Unit] The second usage setting unit 107 performs usage settings based on the execution result of the second authentication. When the second authentication is successful, the second usage setting unit 107 performs usage settings for the physical card. When the second authentication fails, the second usage setting unit 107 does not perform usage settings for the physical card. In the present embodiment, the second usage setting unit 107 performs usage settings by updating the payer information or recharge source information stored in the payment database DB1. For example, the second usage setting unit 107 updates the payer information or recharge source information so that the payer information or recharge source information indicates the physical card. Since the information such as the card numbers of the virtual card and the physical card is the same, if the virtual card is already the payer information or recharge source information, the payer information or recharge source information may not be changed.

[0078] Note that the second usage setting unit 107 may perform usage settings by storing the usage setting information in the payment database DB1 or another database. For example, when it is indicated in other information other than the payer information and recharge source information whether the user uses the virtual card, the second usage setting unit 107 may perform usage settings by generating or updating the other information. When the usage setting is a change in the upper limit amount of the card, the second usage setting unit 107 may perform usage settings by changing the information indicating the upper limit amount. When the usage setting is other content, the second usage setting unit 107 may perform usage settings by generating or updating the information indicating the other content.

[0079] Also, after the usage settings are made by the first usage settings unit 105, if the card determination unit 102 determines that the card is a physical card, the usage settings made by the first usage settings unit 105 may be cancelled. For example, the settlement server 10 returns the user's usage settings to the original state (the state before the usage settings are made by the first usage settings unit 105). In this case, the user may be unable to use the virtual card. Since the user has a physical card at hand, in order to use the same card number (i.e., the physical card) as the virtual card in the settlement service, it is necessary to succeed in the second authentication. If the second authentication is successful, the second usage settings unit 107 makes usage settings for the physical card.

[0080] [3-2. Functions Implemented by the Card Server] For example, the card server 20 includes a data storage unit 200, a delivery determination unit 201, a card determination unit 202, a first authentication execution unit 203, and a second authentication execution unit 204. The data storage unit 200 is realized by the storage unit 22. Each of the delivery determination unit 201, the card determination unit 202, the first authentication execution unit 203, and the second authentication execution unit 204 is realized by the control unit 21.

[0081] [Data Storage Unit] The data storage unit 200 stores data necessary for the card service. For example, the data storage unit 200 stores a card database DB2.

[0082] FIG. 7 is a diagram showing an example of the card database DB2. The card database DB2 is a database in which various types of information related to users in the card service are stored. For example, the card database DB2 stores a user ID, a password, application information, card information, delivery history information, and a card flag. Other data may be stored in the card database DB2.

[0083] In this embodiment, it is assumed that the user ID of the payment service and the user ID of the card service are common. When the user ID of the payment service and the user ID of the card service are different from each other, it is assumed that a relationship database indicating the relationship between the user ID of the payment service and the user ID of the card service is stored in the data storage unit 200. The relationship database may be stored in the payment server 10, another computer, or an external information storage medium.

[0084] The application information is the information input by the user at the time of card application. For example, the application information may indicate a telephone number, an address, a date of birth, a gender, an occupation, an annual income, a family composition, or other information. When a certain user logs in to the card service and applies, the card server 20 stores the application information input by the user at the time of application in the card database DB2 in association with the user ID of the user. The application information may be diverted from information registered in other services other than the card service.

[0085] The card information indicates various information regarding the card. For example, the card information indicates each of a credit card number, an expiration date, a cardholder, and a security code. The card information may indicate an electronic money number of a card with an electronic money function, a point number of a card with a point card function, or other information. The delivery history information is information regarding the delivery history in the delivery service. For example, the delivery history information is a slip number of the delivery service, an address of the delivery destination, a telephone number, and a delivery status. The delivery status indicates information such as the necessity of delivery, before delivery, during delivery, or after delivery. The card server 20 acquires the latest delivery history information from the system of the delivery company and updates the delivery history information in the card database DB2. Note that instead of the card server 20 acquiring the delivery history information, the delivery history information in the card database DB2 may be input or updated manually.

[0086] The card flag is a flag indicating whether the card is a virtual card or a physical card. For example, the card flag indicates either a first value meaning that the card is a virtual card or a second value meaning that the card is a physical card. The initial value of the card flag is the first value. In the present embodiment, the card flag is updated by the delivery determination unit 201. The card flag may be updated based on other conditions. The other conditions will be described in a modification example below.

[0087] Note that the data storage unit 200 may store data corresponding to the card service. For example, the data storage unit 200 may store information necessary for at least one of the first authentication and the second authentication. The data storage unit 200 may store information necessary for providing the card service.

[0088] [Delivery Determination Unit] The delivery determination unit 201 determines whether a physical card has been delivered to the user based on the delivery history information regarding the delivery history of the delivery service for delivering the physical card to the user. The delivery determination unit 201 determines whether it is before or after the physical card has been delivered to the user based on the delivery history information regarding the delivery history of the delivery service for delivering the physical card to the user. If the delivery history information associated with a user ID of a certain user does not indicate delivery completion, the delivery determination unit 201 does not update the card flag associated with the user ID. If the delivery history information associated with a user ID of a certain user indicates delivery completion, the delivery determination unit 201 updates the card flag so that the card flag associated with the user ID indicates a physical card.

[0089] [Card Determination Unit] The card determination unit 202 executes processing for the cooperation between the card service and the payment service. For example, the card determination unit 202 receives a request to obtain a card flag indicating whether the card is a virtual card or a physical card from the payment server 10. The card determination unit 202 obtains the card flag from the card database DB2. The card determination unit 202 transmits the card flag to the payment server 10. The card determination unit 202 may transmit delivery history information instead of the card flag to the payment server 10. Note that the card determination unit 202 may include the delivery determination unit 201. In this case, the card determination unit 202 may determine whether the card is a physical card or a virtual card by determining whether the physical card has been delivered to the user based on the delivery history information. The card determination unit 202 may determine whether the card is a physical card or a virtual card based on information other than the delivery history information.

[0090] [First authentication execution unit] The first authentication execution unit 203 executes the first authentication. The first authentication execution unit 203 only needs to execute at least a part of the processing required for the first authentication. In the present embodiment, the first authentication execution unit 203 executes processing for assisting the processing of the first authentication execution unit 104 of the payment server 10. For example, when the first authentication execution unit 203 is requested to confirm the validity of user information from the payment server 10, the first authentication execution unit 203 determines whether the user information received from the payment server 10 matches the user information stored in the card database DB2. In the present embodiment, since the user information is a pair of a user ID and a phone number, the first authentication execution unit 203 determines whether the pair exists in the card database DB2. When the pair exists, the first authentication execution unit 203 determines that the user information is valid. When the pair does not exist, the first authentication execution unit 203 determines that the user information is invalid. The first authentication execution unit 203 transmits confirmation result information to the payment server 10.

[0091] [Second authentication execution unit] The second authentication execution unit 204 performs the second authentication. The second authentication execution unit 204 may execute at least a part of the processes necessary for the second authentication. In the present embodiment, the second authentication execution unit 204 executes processes for assisting the processes of the second authentication execution unit 106 of the settlement server 10. For example, when the second authentication execution unit 204 is requested by the settlement server 10 to confirm the validity of card information, the second authentication execution unit 204 determines whether the card information received from the settlement server 10 matches the card information stored in the card database DB2. For example, if the card information is the electronic money number of a card with an electronic money function, the second authentication execution unit 204 determines whether the electronic money number is associated with the user ID of the user in the card database DB2. When the electronic money number is associated with the user ID, the second authentication execution unit 204 determines that the card information is valid. When the electronic money number is not associated with the user ID, the second authentication execution unit 204 determines that the card information is invalid. The second authentication execution unit 204 transmits confirmation result information to the settlement server 10.

[0092] [Functions Implemented on the User Terminal] For example, the user terminal 30 includes a data storage unit 300, an operation reception unit 301, and a display control unit 302. The data storage unit 300 is implemented by the storage unit 32. The operation reception unit 301 and the display control unit 302 are implemented by the control unit 31.

[0093] [Data Storage Unit] The data storage unit 300 stores data necessary for the user to use each of the settlement service and the card service. For example, the data storage unit 300 stores a settlement application. When the user uses the settlement service from a browser instead of the settlement application, the data storage unit 300 stores the browser.

[0094] [Operation Reception Unit] The operation reception unit 301 receives various operations of the user. For example, the operation reception unit 301 receives operations on the payment application. The operation reception unit 301 transmits data indicating the operation content of the user to the payment server 10 or the card server 20.

[0095] [Display control unit] The display control unit 302 causes the display unit 35 to display various screens. For example, the display control unit 302 causes the display unit 35 to display the pre-authentication screen SC1, the payment source setting screen SC2, and the top screen SC3. The display control unit 302 communicates with the payment server 10, the card server 20, or another computer, receives data necessary for displaying these screens, and causes these screens to be displayed on the display unit 35.

[0096] [4. Processing Executed in the Card Judgment System] FIG. 8 is a diagram showing an example of the processing executed in the card judgment system 1. The control units 11, 21, 31 execute the programs stored in the storage units 12, 22, 32, respectively, whereby the processing of FIG. 8 is executed. In FIG. 8, the processing when the user passes the card review is explained.

[0097] As shown in FIG. 8, when the user passes the card review, the card server 20 executes processing for coordinating various information (for example, card number) related to the card with the payment server 10 (S1). Through the processing of S1, the information necessary for using the virtual card is coordinated with the payment server 10. It is assumed that the payment server 10 also acquires the user ID of the user who has passed the card review from the card server 20. The payment server 10 associates the user ID with the information necessary for using the virtual card and stores it in the payment database DB1 or another database.

[0098] When the user activates the payment app, the user terminal 30 executes a process to start the membership registration procedure for the payment service with the payment server 10 (S2). In S2, the user inputs information necessary for membership registration. In this embodiment, the user ID for the payment service and the user ID for the card service are common, and since the user ID has already been issued, the user may log in based on the user ID. In this case, information such as the name registered by the user for the card service may be transferred to the payment service.

[0099] When the membership registration procedure has progressed to a certain extent, the user terminal 30 executes a process to display the pre-authentication screen SC1 with the payment server 10 (S3). The user terminal 30 executes phone authentication, which is an example of pre-authentication, with the payment server 10 (S4). Note that the timing at which pre-authentication is executed is not limited to the time of membership registration and may be other timings such as when the user registers a phone number. When phone authentication, which is an example of pre-authentication, is successful, the user terminal 30 executes a process to display the payment source setting screen SC2 with the payment server 10 (S5). If the phone authentication fails, the processes after S5 are not executed and this process ends.

[0100] When the user selects the button B20, the user terminal 30 sends a usage setting request to the payment server 10 to set the user's card as the payment source (S6). The payment server 10 receives the usage setting request from the user terminal 30 (S7). The payment server 10 executes a process to obtain a card flag indicating whether the card is a virtual card or a physical card with the card server 20 (S8).

[0101] In S8, the payment server 10 transmits the user ID of the user to be judged to the card server 20. The card server 20 receives the user ID from the payment server 10. The card server 20 refers to the card database DB2 and acquires the card flag associated with the user ID. The card server 20 transmits the card flag to the payment server 10. The payment server 10 receives the card flag from the card server 20. Note that in S8, the payment server 10 may transmit card information to the card server 20 instead of the user ID. The payment server 10 may transmit both the user ID and the card information to the card server 20. For example, when the user has a plurality of cards, the card server 20 can identify which card is the target based on the card information.

[0102] Based on the card flag obtained in S8, the payment server 10 determines whether the card is a virtual card or a physical card (S9). In S9, when it is determined that the card is a virtual card (S9: virtual card), the payment server 10 executes attribute authentication, which is an example of the first authentication, between the card server 20 and the user terminal 30 (S10). In S10, the payment server 10 executes a process for displaying the modal M21 with the user terminal 30. When the user selects the button B22, the payment server 10 transmits the user ID and the phone number used in the pre-authentication to the card server 20. When the card server 20 receives the user ID and the phone number from the payment server 10, it determines whether this pair exists in the card database DB2. The card server 20 transmits the confirmation result information to the payment server 10. The payment server 10 refers to the confirmation result information and determines whether the first authentication has succeeded. When the first authentication is successful, the payment server 10 sets the virtual card as the payment source (S11), and this process ends.

[0103] In S9, when it is determined that the card is a physical card (S9: Physical Card), the payment server 10 executes possession authentication, which is an example of the second authentication, between the card server 20 and the user terminal 30 (S12). In S12, the payment server 10 executes a process for displaying the modal M25 with the user terminal 30. When the user reads the physical card, the payment server 10 transmits the user ID and the card information read from the physical card to the card server 20. When the card server 20 receives the user ID and the card information from the payment server 10, it determines whether these pairs exist in the card database DB2. The card server 20 transmits the confirmation result information to the payment server 10. Note that the flow of the possession authentication is not limited to the example of this embodiment. For example, the possession authentication may be executed by the payment server 10 determining whether the user ID of the currently logged-in user matches the card information read from the physical card and is stored in the database in the payment server 10. The payment server 10 refers to the confirmation result information and determines whether the second authentication has been successful. When the second authentication is successful, the payment server 10 sets the physical card as the payment source (S13), and this process ends.

[0104] [Summary of the Embodiment] The card determination system 1 of this embodiment receives a usage setting request from the user terminal 30. When the usage setting request is received, the card determination system 1 determines whether the card is a virtual card or a physical card. Thereby, the card determination system 1 can manage the card according to whether the card is a virtual card or a physical card. For example, the card determination system 1 can make subsequent processes different according to whether the card is a virtual card or a physical card. An example of the subsequent process is the first authentication and the second authentication. The card determination system 1 executes a certain process when the card is a virtual card and does not execute the process when the card is a physical card. Depending on whether the card is a virtual card or a physical card, the necessity of executing the process can be properly determined. Similarly, the card determination system 1 can properly determine the necessity of executing the process depending on whether the card is a virtual card or a physical card, such as executing a certain process when the card is a physical card and not executing the process when the card is a virtual card. For example, when virtual cards and physical cards are not distinguished, the choice of which card to use is left to the user's discretion. Therefore, especially for users who are accustomed to physical cards, they may not use a virtual card even if it is issued. In this case, the usage rate of virtual cards does not increase sufficiently. In this regard, since the card determination system 1 can manage virtual cards and physical cards separately, the usage rate of virtual cards can be increased. That is, the card determination system 1 can assist the user in using virtual cards.

[0105] Also, when a usage setting request is received before a physical card is issued and delivered to the user, the card determination system 1 determines that the card is a virtual card. When a usage setting request is received after the physical card is issued and delivered to the user, the card determination system 1 determines that the card is a physical card. Thereby, the card determination system 1 can accurately determine whether the card is a virtual card or a physical card. For example, by treating the card as a virtual card until the physical card is delivered to the user, the user can use the virtual card without waiting for the delivery of the physical card. The card determination system 1 can promote the use of the card.

[0106] Also, the card determination system 1 determines whether it is before the physical card is delivered to the user or after the physical card is delivered to the user based on the delivery history information regarding the delivery history of the delivery service that delivers the physical card to the user. Thereby, the card determination system 1 can more accurately determine whether the card is a virtual card or a physical card.

[0107] In addition, when the card determination system 1 determines that the card is a virtual card, it executes the first authentication, and when it determines that the card is a physical card, it executes the second authentication. The card determination system 1 performs usage settings based on the execution result of at least one of the first authentication and the second authentication. As a result, the card determination system 1 can selectively use authentication according to whether the card is a virtual card or a physical card, enabling flexible authentication. Regardless of whether the card is a virtual card or a physical card, the user can perform some form of authentication, so the card determination system 1 can improve the convenience for the user. For example, since the virtual card has completed identity verification at the time of application and has a limited available period, the possibility of being phished in terms of time is low. Therefore, even if the first authentication is different from the second authentication for the physical card, the risk of unauthorized use is low. Therefore, by making the first authentication simpler than the second authentication, the card determination system 1 can improve the convenience for the user.

[0108] In addition, when the card determination system 1 determines that the card is a physical card, it executes the second authentication in which the physical card is used. The card determination system 1 can enhance security through the second authentication that uses a physical object such as a physical card. For example, even if a malicious third party obtains information such as the card number in some way, the second authentication cannot be successful without obtaining the physical card, so the card determination system 1 can enhance security.

[0109] In addition, the card determination system 1 executes the first authentication in which the user information obtained from the card server 20 is verified. Thereby, the card determination system 1 can enhance security through the first authentication in which the user information strictly managed by the card company is verified.

[0110] In addition, when the card determination system 1 executes pre-authentication and determines that the card is a virtual card, it executes first authentication based on the authentication information authenticated in the pre-authentication. Since the authentication information authenticated in the pre-authentication is used in the first authentication by the card determination system 1, the user does not need to input the authentication information again, so the user's labor can be saved.

[0111] In addition, when the card determination system 1 determines that the card is a virtual card, it executes first authentication in which the authentication information regarding the user held on the card administrator side is compared with the authentication information regarding the user at the time of receiving the usage setting request. Thereby, the card determination system 1 can enhance security by the first authentication in which the authentication information strictly managed by the card company is confirmed.

[0112] Also, a predetermined service is a settlement service in which settlement is executed based on a card. The card determination system 1 receives a usage setting request regarding the usage setting of the payment source or charge source used by the user in the settlement service. Thereby, the card determination system 1 can perform management according to the card used in the settlement service.

[0113] [6. Modification Example] The present disclosure is not limited to the embodiments described above. The present disclosure can be appropriately changed without departing from the gist of the present disclosure.

[0114] FIG. 9 is a diagram showing an example of functions realized in a modification example. For example, the settlement server 10 includes a release unit 108, a holding unit 109, an execution presence / absence information setting unit 110, a privilege granting unit 111, and a screen transition unit 112. Each of the release unit 108, the holding unit 109, the execution presence / absence information setting unit 110, the privilege granting unit 111, and the screen transition unit 112 is realized by the control unit 11.

[0115] [6-1. Modification Example 1] For example, when the card determination unit 102 of the embodiment determines that the physical card has been delivered to the user, it determines that the card is a physical card. Some users may not receive the physical card because they have been away for a long time or intentionally reject the receipt of the physical card. In this case, the user can use the virtual card in the payment application for a long time. Such use of the virtual card is not appropriate for the original intention (the intention to use it temporarily until the physical card arrives). Therefore, when the user does not receive the physical card for a long time, the use of the virtual card may be prohibited.

[0116] When it is determined that the card is a virtual card, the first usage setting unit 105 in Modification 1 performs the usage setting of the virtual card. In Modification 1, an example is given where the use of the virtual card in payment corresponds to the use of the virtual card. That is, an example is given where payment or recharge is executed with the virtual card set as the payment source or recharge source, which corresponds to the use of the virtual card. The use of the virtual card only needs to be such that the virtual card is referenced in the processing of the payment service. The use of the virtual card is not limited to the example of Modification 1. For example, the virtual card being referenced in the authentication in the payment service may also correspond to the use of the virtual card.

[0117] For example, when it is determined that a certain user's card is a virtual card, the first usage setting unit 105 updates the payment source information or recharge source information of the user so that the virtual card becomes the payment source or recharge source. The first usage setting unit 105 stores in the payment database DB1 the payment source information indicating that the payment source is a virtual card or the recharge source information indicating that the recharge source is a virtual card. The first usage setting unit 105 may permit the use of the virtual card by recording in the data storage unit 100 other information indicating that the user can use the virtual card in the payment service.

[0118] The card determination system 1 of Modification Example 1 includes a release unit 108. When the physical card is not delivered to the user by a predetermined deadline, the release unit 108 of Modification Example 1 releases the usage setting of the virtual card. To release the usage setting means to return to the state before the use of the virtual card is permitted. For example, when it is determined that a certain user's card is a virtual card, the release unit 108 updates the payment source information or recharge source information of the user so that the virtual card is released from the payment source or recharge source. The first usage setting unit 105 may prohibit the use of the virtual card by recording information indicating that the user cannot use the virtual card in the payment service in the data storage unit 100.

[0119] Note that the predetermined deadline may be determined by any method. For example, a predetermined time after the physical card is shipped (e.g., two months later) may be the predetermined deadline. Instead of the shipment of the physical card, any point in time may be the starting point of the predetermined deadline. For example, it may be the time when the user passes the review, the time when the user applies for the issuance of the card, the time after the physical card is shipped, or other points in time. The payment server 10 may store information indicating the predetermined deadline and determine whether the predetermined deadline has arrived. Alternatively, for example, another computer such as the card server 20 may store the information and determine whether the predetermined deadline has arrived. In this case, the payment server 10 acquires information indicating the determination result of whether the predetermined deadline has arrived from the other computer. The release unit 108 may release the usage setting of the virtual card based on the information.

[0120] When the physical card is not delivered to the user by a predetermined deadline, the card determination system 1 of Modification Example 1 releases the usage setting of the virtual card. Thereby, the card determination system 1 can prevent the virtual card from being used in an unintended way when the user does not receive the physical card for a long time. For example, the card determination system 1 can prevent unauthorized use of the virtual card.

[0121] [6-2. Modification Example 2] For example, the card determination unit 102 may determine whether the physical card is before or after being delivered to the user based on an operation using the physical card. Hereinafter, this operation will be referred to as a physical card usage operation. For example, the user performs a physical card usage operation. The physical card usage operation is an operation that cannot be performed without having the physical card at hand. In Modification 2, an example is given where the physical card usage operation is an operation of reading the physical card with the NFC function of the communication unit 33. The physical card usage operation may be other operations. For example, the physical card usage operation may be an operation of photographing the physical card with the camera of the user terminal 30, an operation of reading the physical card with a function other than the NFC function, an operation for settlement with the physical card in a physical store (for example, an operation of having the user or the store clerk read the physical card with a reading device), or other operations. For example, the card server 20 can identify that the user has used the physical card received by the user (that is, the delivery of the physical card is completed) by an operation for settlement with the physical card in a physical store.

[0122] In Modification 2, when the user receives the physical card, the user brings the user terminal 30 close to the physical card and uses the NFC function of the communication unit 33 to read the IC chip of the physical card. The user terminal 30 can read any information in the IC chip. For example, the user terminal 30 reads the card number in the IC chip, the number of electronic money attached to the card, the number of points attached to the card, or other information. The user terminal 30 transmits the information read from the IC chip to the settlement server 10. The settlement server 10 receives the information from the user terminal 30. The card determination unit 102 may determine that the physical card is after being delivered to the user when the information obtained based on the physical card usage operation is received. The method of confirming these information may be the same as the process described as the process of the second authentication execution unit 106 in the embodiment.

[0123] The card determination system 1 of Modification Example 2 determines whether the physical card is before being delivered to the user or after being delivered to the user based on the physical card usage operation. The card determination system 1 can accurately determine whether the card is a virtual card or a physical card by the physical card usage operation. For example, even in an environment where the delivery history information cannot be obtained from the delivery carrier, the card determination system 1 can determine whether the physical card has been delivered to the user.

[0124] [6-3. Modification Example 3] For example, the card determination unit 102 may determine whether the card is a virtual card or a physical card based on the delivery period required for the delivery of the physical card. The delivery period is a predetermined period generally estimated to be required for the delivery of the physical card. The length of the delivery period may be of any length. For example, the length of the delivery period may be any of 1 to 6 days, one week, or other lengths. The starting point (for example, the starting date) of the delivery period may be any point in time. For example, the starting point of the delivery period may be the time when the user's review is completed, the time when the physical card is issued, the time when the physical card is shipped, or other times.

[0125] In Modification Example 3, assume that the delivery period is the period one week after the physical card is shipped. For example, when the physical card is shipped, the card server 20 transmits delivery period information indicating the period from the current time to one week later as the delivery period to the settlement server 10. When the settlement server 10 receives the delivery period information from the card server 20, it stores the delivery period information in the settlement database DB1. The card determination unit 102 determines whether the delivery period has elapsed based on the delivery period information. When the delivery period has not elapsed, the card determination unit 102 determines that the card is a virtual card. When the delivery period has elapsed, the card determination unit 102 determines that the card is a physical card. The delivery period information may not be stored in the settlement database DB1. In this case, the card determination unit 102 may inquire the card server 20 about the delivery period information of each user.

[0126] The card determination system 1 of Modification Example 3 determines whether a card is a virtual card or a physical card based on the delivery period required for delivering the physical card. Thereby, the card determination system 1 can accurately determine whether the card is a virtual card or a physical card. For example, even in an environment where the card determination system 1 cannot obtain delivery history information from the delivery carrier, the card determination system 1 can determine whether the physical card has been delivered to the user.

[0127] [6-4. Modification Example 4] For example, in the embodiment, the case where the first authentication is executed based on user information such as a user ID and a phone number is taken as an example. When the settlement server 10 obtains user information from the card server 20, the settlement server 10 may hold the user information in the data storage unit 100. In this case, the first authentication execution unit 104 may perform the comparison by itself without requesting the card server 20 to compare the user information, and execute the first authentication. The user information held in the data storage unit 100 may be used when the first authentication is required again.

[0128] The card determination system 1 of Modification Example 4 includes a holding unit 109. The holding unit 109 holds the user information managed by the card server 20 in the data storage unit 100 of the card determination system 1. Holding the user information in the data storage unit 100 means continuously recording the user information in the data storage unit 100 (recording the user information in the data storage unit 100 without deleting it). For example, the holding unit 109 holds the user information in the data storage unit 100 by storing the user information in the settlement database DB1. The holding unit 109 may hold the user information in another database other than the settlement database DB1, another computer other than the settlement server 10, or an external information storage medium.

[0129] The first authentication execution unit 104 of Modification Example 4 executes the first authentication after the next time based on the user information held in the data storage unit 100. "After the next time" refers to the first authentication performed after the first authentication that caused the user information to be held in the data storage unit 100. That is, the second time and after correspond to "after the next time". For example, when the first authentication is repeatedly requested while the virtual card is set as the payer, the first authentication execution unit 104 may, when the second and subsequent first authentications are required, acquire the user information held in the data storage unit 100 and execute the first authentication without querying the card server 20. Although it is different from the embodiment in that no query to the card server 20 occurs, the content of the first authentication process itself is the same as in the embodiment.

[0130] The card determination system 1 of Modification Example 4 holds the user information managed by the card server 20 in the data storage unit 100 of the card determination system 1. The card determination system 1 executes the first authentication after the next time based on the user information held in the data storage unit 100. Thereby, the card determination system 1 can omit the request for user information to the card server 20, so that the processing load and the communication load can be reduced. When a cost is incurred for the request for user information, the card determination system 1 can reduce the cost.

[0131] [6-5. Modification Example 5] For example, even if the first authentication fails, for users who satisfy a certain predetermined condition, the use setting of the virtual card may be permitted. The predetermined condition is a condition that serves as a criterion for whether the use setting of the virtual card is permitted or not. For example, the predetermined condition may be a condition determined based on the available amount of the virtual card, the user's usage amount in services other than the payment service, the user's credit information managed by a credit company or services other than the payment service, the user's information obtained from other cards, or other information.

[0132] Note that the predetermined conditions are not limited to the above example. The predetermined conditions may be any conditions under which the operator of the settlement service considers it acceptable to permit the use of the virtual card. The predetermined conditions may also be conditions under which the available amount is less than when the first authentication is successful. For example, the predetermined conditions may be such that when the first authentication is successful, the usage limit for one time or within a predetermined period is the first amount, and when the first authentication fails, the usage limit becomes a second amount lower than the first amount. Further authentication may be required after the physical card is delivered. With such a configuration, by permitting the use of the card once on the condition of suppressing the available amount, it is possible to improve the user's convenience while ensuring security. Also, when the further authentication is performed, the security can be enhanced.

[0133] In Modification 5, the first usage setting unit 105 performs usage setting of the virtual card when the first authentication fails and the user satisfies the predetermined conditions. The first usage setting unit 105 determines whether the user satisfies the predetermined conditions when the first authentication fails. When the first usage setting unit 105 determines that the user does not satisfy the predetermined conditions, it does not perform the usage setting of the virtual card, and when it determines that the user satisfies the predetermined conditions, it performs the usage setting of the virtual card. Note that the further authentication execution unit 106 in Modification 5 performs further authentication when the physical card is delivered to the user. The further authentication in this case is as described in the embodiment.

[0134] For example, when the available amount of the virtual card or the user's usage amount in other services corresponds to the predetermined conditions, the first usage setting unit 105 acquires information regarding the user's usage amount from other services. The first usage setting unit 105 determines whether the user's usage amount is equal to or greater than the threshold based on the information. When the user's usage amount is less than the threshold, the first usage setting unit 105 determines that the user does not satisfy the predetermined conditions, and when the user's usage amount is equal to or greater than the threshold, the first usage setting unit 105 determines that the user satisfies the predetermined conditions.

[0135] For example, when the credit information of a user managed by a service other than a credit company or a settlement service meets a predetermined condition, the first usage setting unit 105 acquires the credit information of the user from the credit company or the like. Here, a case where the credit information is a numerical value indicating the user's creditworthiness is taken as an example. The first usage setting unit 105 determines whether the creditworthiness indicated by the credit information is equal to or greater than a threshold value. When the user's creditworthiness is less than the threshold value, the first usage setting unit 105 determines that the user does not meet the predetermined condition, and when the user's creditworthiness is equal to or greater than the threshold value, the first usage setting unit 105 determines that the user meets the predetermined condition. Similarly, when the predetermined condition is another condition, the first usage setting unit 105 may acquire the information necessary for determining the predetermined condition and determine whether the predetermined condition is satisfied based on the information.

[0136] When the first authentication fails and the user meets a predetermined condition, the card determination system 1 of Modification Example 5 performs usage setting of the virtual card. Thereby, even if there is a situation where the user cannot succeed in the first authentication, the card determination system 1 can perform usage setting of the virtual card if the predetermined condition is satisfied, so that the convenience of the user can be improved. For example, when the user changes the phone number after applying for card issuance, the first authentication may fail. Even in such a case, since the user only needs to meet the predetermined condition, the card determination system 1 can improve the convenience of the user. The card determination system 1 can reduce the loss of opportunity loss by temporarily permitting the user to use the virtual card.

[0137] [6-6. Modification Example 6] For example, in some cases, it may be more appropriate for the card determination system 1 not to perform the first authentication. For example, if a failure has occurred in the card determination system 1, if the card determination system attempts to perform the first authentication, there may be a risk of further failures. Therefore, the card determination system 1 may determine whether to perform the first authentication based on the execution information regarding whether to perform the first authentication in the payment service. The execution information indicates either a value indicating that the first authentication is to be performed or a value indicating that the first authentication is not to be performed. In Modification Example 6, the case where the execution information is stored in the data storage unit 100 is taken as an example. The execution information may be stored in another computer other than the payment server 10 or in an external information storage medium.

[0138] The card determination system 1 of Modification Example 6 includes an execution information setting unit 110. The execution information setting unit 110 sets the execution information based on a predetermined condition. The predetermined condition of Modification Example 6 is different from the predetermined condition of Modification Example 5. The predetermined condition of Modification Example 6 is a condition serving as a criterion for changing the value of the execution information. For example, the predetermined condition may be that an administrator of the payment service performs an operation for changing the value of the execution information, a failure occurs in the card determination system 1, a predetermined date and time arrives, the card determination system 1 receives predetermined information from the card server 20, or other conditions. The execution information setting unit 110 sets the execution information based on these predetermined conditions.

[0139] The first authentication execution unit 104 of Modification Example 6 performs the first authentication based on the execution information. For example, when the execution information indicates that the first authentication is to be performed, the first authentication execution unit 104 performs the first authentication, and when the execution information indicates that the first authentication is not to be performed, the first authentication execution unit 104 does not perform the first authentication.

[0140] The card determination system 1 of Modification Example 6 sets execution availability information regarding whether to execute the first authentication in the service based on a predetermined condition. The card determination system 1 executes the first authentication based on the execution availability information. Thereby, the card determination system 1 can prevent attempting to execute the first authentication when there is a situation where the first authentication cannot be executed.

[0141] [6-7. Modification Example 7] For example, the card determination system 1 may prepare a plurality of first authentications. The user may be able to perform an arbitrary first authentication among the plurality of first authentications. In Modification Example 7, as an example, a case where 3D Secure is prepared as the first authentication separately from the first authentication described in the embodiment is given. The number of first authentications is not limited to two as in Modification Example 7. The card determination system 1 may prepare three or more first authentications.

[0142] The first authentication execution unit 104 of Modification Example 7 executes the first authentication selected by the user among the plurality of first authentications when it is determined that the card is a virtual card. For example, when the user selects the button B20 on the payment source setting screen SC2, the user terminal 30 causes the display unit 35 to display the payment source setting screen SC2 on which the user can select any one of the plurality of first authentications. The user selects any one of the plurality of first authentications. The user terminal 30 notifies the settlement server 10 of the first authentication selected by the user. The first authentication execution unit 104 executes the first authentication selected by the user. Other first authentications other than the first authentication described in the embodiment may be executed according to a known process. For example, when 3D Secure corresponds to the first authentication, the first authentication execution unit 104 executes the first authentication by determining whether the password input by the user matches the password registered in advance by the user.

[0143] When the card determination system 1 of Modification Example 7 determines that the card is a virtual card, among a plurality of first authentications, the first authentication selected by the user is executed. As a result, the user can select any first authentication among the plurality of first authentications, so that the card determination system 1 can improve the convenience for the user. For example, when the user changes the phone number and cannot succeed in phone authentication, by executing 3D Secure, the virtual card can be used in the payment service. The card determination system 1 can promote the use of virtual cards by enhancing the flexibility of the first authentication.

[0144] [6-8. Modification Example 8] For example, in the embodiment, the case where the user can set a virtual card as the payer before receiving the physical card is taken as an example. In this case, some privilege may be given to the user. The privilege can also be called a reward. For example, the privilege may be points, an increased point awarding rate, electronic money, a coupon, a free use ticket, a product exchange ticket, content such as a video, a lottery ticket, or other privileges. The privileges are not limited to these and may be various known privileges.

[0145] The card determination system 1 of Modification Example 8 includes a privilege granting unit 111. When it is determined that the card is a virtual card, the privilege granting unit 111 grants a predetermined privilege to the user. When it is determined that the card is a physical card, the privilege granting unit 111 does not grant the privilege to the user. When it is determined that the card is a physical card, the privilege granting unit 111 may grant another privilege to the user. For example, the privilege granting unit 111 may grant a privilege by associating privilege information indicating the privilege granted to the user (for example, privilege information indicating that the point awarding rate is increasing) with the user ID, or may grant a privilege by increasing the balance of the user's points or electronic money. The method of granting the privilege may be the same as the method adopted in the known privilege granting. Note that the privilege granting unit 111 may grant a privilege to the user when it is determined that the card is a virtual card and the usage setting is performed in the state of the virtual card.

[0146] When the card determination system 1 of Modification Example 8 determines that the card is a virtual card, it grants a predetermined privilege to the user. Thereby, the card determination system 1 can motivate the user to use the virtual card.

[0147] [6-9. Modification Example 9] For example, although somewhat described in FIGS. 3 and 4, when it is determined whether the card is a virtual card or a physical card, the screen may transition to the next screen in a state where the card is selected. The state where the card is selected is a state where it is selected as the card to be used for setting. In the examples of FIGS. 3 and 4, when the user selects button B20, the card displayed on button B20 is selected as the card to be used for setting. The screen transitions to the next screen while this selected state of the card is maintained.

[0148] In Modification Example 9, when the screen of the payment source setting screen SC2 in FIG. 3 is displayed, if the card applied for by the user is displayed on the payment source setting screen SC2 (that is, if the card applied for by the user has been pre-linked), an example is given where it automatically transitions to the next screen (for example, the payment source setting screen SC2 including the modal M21) without the user selecting button B20. The operation of the automatic transition may be only a predetermined number of times (for example, once). Whether the card is a virtual card or a physical card, the automatic transition may be performed. With such a configuration, the usability and utilization rate regarding the card can be improved. Also, by limiting the number of times, an opportunity can be given to the user to set a card other than a specific card.

[0149] The card determination system 1 of Modification Example 9 includes a screen transition unit 112. When the determination by the card determination unit 102 is made, the screen transition unit 112 automatically transitions the user terminal 30 to the next screen in a state where a card is selected. Automatically transitioning to the next screen means transmitting data necessary for displaying the next screen to the user terminal 30 without requiring the user's operation. In the examples of FIGS. 3 and 4, the screen transition unit 112 transitions to a payment source setting screen SC2 including modals M21 and M25 as the next screen. For this reason, the screen transition unit 112 transitions to the next screen by transmitting data necessary for displaying the modals M21 and M25 to the user terminal 30.

[0150] Note that the next screen to be transitioned by the screen transition unit 112 is not limited to the payment source setting screen SC2 including the modals M21 and M25. Any screen on which some process is executed based on the selected card may be the next screen. For example, the screen transition unit 112 may transition the user terminal 30 to a screen for raising the upper limit amount of the selected card as the next screen. The screen transition unit 112 may transition the user terminal 30 to a screen for executing payment with the selected card as the next screen. The screen transition unit 112 may transition the user terminal 30 to another screen where the selected card is used in some way. It is assumed that the data necessary for displaying the destination screen is stored in the data storage unit 100.

[0151] When the determination by the card determination unit 102 is made, the card determination system 1 of Modification Example 9 automatically transitions the user terminal 30 to the next screen in a state where a card is selected. Thereby, the card determination system 1 can transition to an appropriate screen in a state where a card is selected, so that the convenience for the user can be improved.

[0152] [6-10. Other Modification Examples] For example, the above modification examples may be combined.

[0153] For example, the functions described as being implemented by the payment server 10 may be implemented by the card server 20, the user terminal 30, or other computers. The processes described as being implemented by the payment server 10 may be shared among a plurality of computers. The processes described as being implemented by the card server 20 may be implemented by the payment server 10, the user terminal 30, or other computers. The processes described as being implemented by the card server 20 may be shared among a plurality of computers.

[0154] [7. Appendix] For example, the card determination system may also have the following configuration. (1) A usage setting request reception unit that receives a usage setting request regarding the usage settings of the card used by the user in a predetermined service from the user's user terminal, A card determination unit that determines whether the card is a virtual card or a physical card when the usage setting request is received, A card determination system including the above. (2) The card determination unit Determines that the card is the virtual card when the usage setting request is received before the physical card is issued and delivered to the user, Determines that the card is the physical card when the usage setting request is received after the physical card is issued and delivered to the user. The card determination system according to (1). (3) The card determination system further includes a delivery determination unit that determines whether the physical card has been delivered to the user based on delivery history information regarding the delivery history of the delivery service that delivers the physical card to the user, The card determination unit Determines that the card is the virtual card when the usage setting request is received before it is determined that the physical card has been delivered to the user, When the usage setting request is received after it is determined that the physical card has been delivered to the user, determine that the card is the physical card. The card determination system according to (2). (4) The card determination system includes When it is determined that the card is the virtual card, a first usage setting unit that performs the usage setting of the virtual card; A cancellation unit that cancels the usage setting of the virtual card when the physical card is not delivered to the user by a predetermined deadline; The card determination system according to (2) or (3), further including the above. (5) The card determination unit determines whether the physical card is before or after being delivered to the user based on an operation in which the physical card is used. The card determination system according to any one of (2) to (4). (6) The card determination unit determines whether the card is a virtual card or a physical card based on a delivery period required for delivering the physical card. The card determination system according to any one of (1) to (5). (7) The card determination system includes When it is determined that the card is the virtual card, a first authentication execution unit that executes first authentication; A first usage setting unit that performs the usage setting based on the execution result of the first authentication; When it is determined that the card is the physical card, a second authentication execution unit that executes second authentication; A second usage setting unit that performs the usage setting based on the execution result of the second authentication; The card determination system according to any one of (1) to (6), further including the above. (8) When it is determined that the card is the physical card, the second authentication execution unit executes the second authentication in which the physical card is used. The card determination system described in (7). (9) The first authentication execution unit executes the first authentication for confirming user information regarding the user, which is managed by the card issuer system of the card issuer that issued the card. The card determination system described in (7) or (8). (10) The card determination system further includes a holding unit that holds the user information managed by the card issuer system in a data storage unit of the card determination system. The first authentication execution unit executes the first authentication after the next time based on the user information held in the data storage unit. The card determination system described in (9). (11) When the first authentication fails and the user satisfies a predetermined condition, the first usage setting unit performs the usage setting of the virtual card. When the physical card is delivered to the user, the second authentication execution unit executes the second authentication. The card determination system according to any one of (7) to (10). (12) The card determination system further includes an execution presence / absence information setting unit that sets execution presence / absence information regarding the execution of the first authentication based on a predetermined condition. The first authentication execution unit executes the first authentication based on the execution presence / absence information. The card determination system according to any one of (7) to (11). (13) The card determination system further includes a pre-authentication execution unit that executes pre-authentication. When it is determined that the card is the virtual card, the first authentication execution unit executes the first authentication based on the authentication information authenticated by the pre-authentication. The card determination system according to any one of (7) to (12). (14) When it is determined that the card is the virtual card, the first authentication execution unit executes the first authentication in which the authentication information regarding the user held on the administrator side of the card is compared with the authentication information regarding the user at the time of reception of the usage setting request. The card determination system according to any one of (7) to (13). (15) When it is determined that the card is the virtual card, the first authentication execution unit executes the first authentication selected by the user among the plurality of first authentications. The card determination system according to any one of (7) to (14). (16) The predetermined service is a settlement service in which settlement is executed based on the card. The usage setting request reception unit receives the usage setting request regarding the usage setting of the payment source or charge source used by the user in the settlement service. The card determination system according to any one of (1) to (15). (17) When it is determined that the card is the virtual card, the card determination system further includes a privilege granting unit that grants a predetermined privilege to the user. The card determination system according to any one of (1) to (16). (18) When the determination by the card determination unit is made, the card determination system further includes a screen transition unit that automatically transitions the user terminal to the next screen in a state where the card is selected. The card determination system according to any one of (1) to (17).

Explanation of Signs

[0155] 1 Card determination system, N network, 10 Payment server, 11, 21, 31 Control unit, 12, 22, 32 Memory unit, 13, 23, 33 Communication unit, 20 Card server, 30 User terminal, 34 Operation unit, 35 Display unit, 100, 200, 300 Data storage unit, 101 Usage setting request reception unit, 102, 202 Card determination unit, 103 Pre-authentication execution unit, 104, 203 First authentication execution unit, 105 First usage setting unit, 106, 204 Second authentication execution unit, 107 Second usage setting unit, 108 Release unit, 109 Holding unit, 110 Execution presence / absence information setting unit, 111 Privilege granting unit, 112 Screen transition unit, 201 Delivery determination unit, 301 Operation reception unit, 302 Display control unit, B20, B22, B24, B27 Button, C30 Code, DB1 Payment database, DB2 Card database, M21, M25 Modal, SC1 Pre-authentication screen, SC2 Payment source setting screen, SC3 Top screen, W23, W26 Window.

Claims

1. A usage setting request reception unit that receives, from a user's user terminal, a usage setting request regarding the usage setting of a card used by the user in a predetermined service; A card determination unit that determines that the card is a virtual card when the usage setting request is received before the physical card is issued and delivered to the user, and determines that the card is the physical card when the usage setting request is received after the physical card is issued and delivered to the user; A card determination system including the above.

2. The card determination system further includes a delivery determination unit that determines whether or not the physical card has been delivered to the user based on delivery history information regarding the delivery history of a delivery service that delivers the physical card to the user, The card determination unit, determines that the card is the virtual card when the usage setting request is received before it is determined that the physical card has been delivered to the user, and determines that the card is the physical card when the usage setting request is received after it is determined that the physical card has been delivered to the user. The card determination system according to Claim 1.

3. The card determination system, when it is determined that the card is the virtual card, a first usage setting unit that performs the usage setting of the virtual card; a release unit that releases the usage setting of the virtual card when the physical card has not been delivered to the user by a predetermined deadline; The card determination system according to Claim 1 or 2, further including the above.

4. The card determination unit determines whether it is before the physical card is delivered to the user or after the physical card is delivered to the user based on an operation in which the physical card is used. The card determination system according to Claim 1 or 2.

5. A usage setting request reception unit that receives, from a user's user terminal, a usage setting request regarding the usage setting of a card used by the user in a predetermined service; When the usage setting request is received, it is determined whether or not a delivery period required for the delivery of the physical card has elapsed. When it is determined that the delivery period has not elapsed, it is determined that the card is a virtual card. When it is determined that the delivery period has elapsed, a card determination unit that determines that the card is a physical card; A card determination system including the above.

6. A usage setting request reception unit that receives a usage setting request regarding the usage setting of a card used by the user in a predetermined service from the user's user terminal; A card determination unit that determines whether the card is a virtual card or a physical card when the usage setting request is received; When it is determined that the card is the virtual card, a first authentication execution unit that executes a first authentication for confirming user information regarding the user, which is managed by a card issuer system of a card issuer that issued the card; A first usage setting unit that performs the usage setting based on the execution result of the first authentication; A holding unit that holds the user information managed by the card issuer system in a data storage unit of the card determination system; A second authentication execution unit that executes a second authentication when it is determined that the card is the physical card; A second usage setting unit that performs the usage setting based on the execution result of the second authentication; including The first authentication execution unit executes the first authentication after the next time without inquiring the card issuer system about the user information based on the user information held in the data storage unit. Card determination system.

7. The second authentication execution unit executes the second authentication when it is determined that the card is the physical card and the physical card is used. The card determination system according to claim 6.

8. The first usage setting unit performs the usage setting of the virtual card when the first authentication fails and the user satisfies a predetermined condition. The second authentication execution unit executes the second authentication when the physical card is delivered to the user. The card determination system according to claim 6.

9. The card determination system further includes an execution presence / absence information setting unit that sets execution presence / absence information regarding the execution of the first authentication based on a predetermined condition. The first authentication execution unit executes the first authentication based on the execution presence / absence information. The card determination system according to claim 6.

10. A pre-authentication execution unit that executes pre-authentication based on authentication information input by the user; A usage setting request reception unit that receives a usage setting request regarding the usage setting of a card used by the user in a predetermined service from the user's user terminal; When the usage setting request is received, a card determination unit that determines whether the card is a virtual card or a physical card; When it is determined that the card is the virtual card, a first authentication execution unit that executes first authentication based on the authentication information authenticated in the pre-authentication without the user inputting the authentication information again; A first usage setting unit that performs the usage setting based on the execution result of the first authentication; When it is determined that the card is the physical card, a second authentication execution unit that executes second authentication; A second usage setting unit that performs the usage setting based on the execution result of the second authentication; A card determination system including the above.

11. When it is determined that the card is the virtual card, the first authentication execution unit executes the first authentication in which the authentication information regarding the user held on the administrator side of the card is compared with the authentication information regarding the user at the time of receiving the usage setting request. The card determination system according to claim 6.

12. When it is determined that the card is the virtual card, the first authentication execution unit executes the first authentication selected by the user among the plurality of first authentications. The card determination system according to claim 6.

13. The predetermined service is a payment service in which payment is executed based on the card, The usage setting request reception unit receives the usage setting request regarding the usage setting of the payment source or recharge source used by the user in the payment service. The card determination system according to claim 1 or 2.

14. When it is determined that the card is the virtual card, the card determination system further includes a privilege granting unit that grants a predetermined privilege to the user. The card determination system according to claim 1 or 2.

15. When the determination by the card determination unit is made, the card determination system further includes a screen transition unit that automatically transitions the user terminal to the next screen with the card selected. The card determination system according to claim 1 or 2.

16. A computer, A usage setting request reception step of receiving, from a user terminal of a user, a usage setting request regarding the usage setting of a card used by the user in a predetermined service; When the usage setting request is received before the physical card is issued and delivered to the user, it is determined that the card is a virtual card, and when the usage setting request is received after the physical card is issued and delivered to the user, a card determination step of determining that the card is the physical card; A card determination method for executing the above.

17. A usage setting request reception unit that receives a usage setting request regarding the usage setting of a card used by the user in a predetermined service from the user terminal of the user; A card determination unit that determines that the card is a virtual card when the usage setting request is received before the physical card is issued and delivered to the user, and determines that the card is the physical card when the usage setting request is received after the physical card is issued and delivered to the user; A program for causing a computer to function as the above.

Images