Card management methods, user terminals, servers, systems, and storage media

Abstract

A card management method, a user terminal, a server, a system, and a storage medium, belonging to the field of data processing, includes the steps of: sending a card binding message to a server (S201), the message including card authentication information of a binding card; receiving a card type of the binding card and dedicated card information of the binding card sent from the server (S202), the dedicated card information including a card transaction identifier; and loading the dedicated card information of the binding card into a security element (S203), the dedicated card information of the binding card and matching general-purpose personalization data are used to verify the transaction of the binding card, the matching general-purpose personalization data being a first type of general-purpose personalization data or a second type of general-purpose personalization data matching the card type of the binding card. The method can reduce the storage resources occupied by the user terminal.

Claims

[Claim 1] A card management method performed on a user terminal, The card management method manages transaction verification data used when making payment transactions via the application program using a card associated with the application program installed on the user terminal. The user terminal includes a security element, the security element stores first general-purpose personal data and second general-purpose personal data, the first general-purpose personal data being personal data necessary for transaction verification when the card type of the card is a first type, and the second general-purpose personal data being personal data necessary for transaction verification when the card type of the card is a second type different from the first type. The aforementioned card management method is: A transmission step in which the transmission module of the user terminal transmits a message containing the card authentication information to the server in order to cause the server to determine the card type of the card based on the card authentication information of the card and to assign dedicated card information including a card transaction identifier to the card, The receiving module of the user terminal receives the card type and dedicated card information transmitted from the server in a receiving step, A loading step in which the processing module of the user terminal loads the dedicated card information received by the receiving module in the receiving step into the security element, and if the card type received by the receiving module in the receiving step is the first type, stores the dedicated card information in the security element in association with the first general-purpose personal data, and if the card type received by the receiving module in the receiving step is the second type, stores the dedicated card information in the security element in association with the second general-purpose personal data, Includes, The dedicated card information stored in the security element during the load step, and the first general-purpose personal data or the second general-purpose personal data associated with the dedicated card information, are used for transaction verification when making a payment transaction with the card via the application program. Card management methods. [Claim 2] If the aforementioned card includes a first card and a second card of the same card type, the dedicated card information and general-purpose personalized data for target matching of the first card are used to verify the transaction of the first card, and the dedicated card information and general-purpose personalized data for target matching of the second card are used to verify the transaction of the second card. The aforementioned target matching general-purpose personalized data is either the first general-purpose personalized data or the second general-purpose personalized data, corresponding to the card type of the first card. The card management method according to claim 1. [Claim 3] A setting step comprising setting the usage status of the card to an enabled state using the security element and generating or updating a first mapping relationship, wherein the first mapping relationship is a mapping relationship that associates the dedicated card information of the card with the card type of the card and the usage status of the card. It further includes, The aforementioned usage state includes enabled state, disabled state, and default usage state. The card management method according to claim 1. [Claim 4] A step of transmitting the usage status of the card and the first mapping relationship set in the setting step to the server, The card management method according to claim 3, further comprising: [Claim 5] The aforementioned message includes a first message, a second message, and a verification message, and the card authentication information includes a card identifier, card type verification information, and input verification code. The step of sending the aforementioned message to the server is: A step of sending the first message to the server, wherein the first message includes the card identifier of the card, Upon receiving a first response message transmitted from the server, the step of transmitting a second message to the server, wherein the first response message includes the card type of the card, and the second message includes card type verification information of the card; When a second response message is received from the server, the verification message is sent to the server, wherein the second response message includes a dynamic verification code, and the verification message includes the input verification code. Includes, The aforementioned card type verification information is used to perform verification for a certain type of card. The aforementioned input verification code is a verification code entered by the user, or a verification code entered based on the received dynamic verification code. The card management method according to claim 1. [Claim 6] If the card type of the card is the first type, the card type verification information includes the first type verification information. If the card type of the card is the second type, the card type verification information includes the second type verification information. The first type of verification information differs from the second type of verification information. The card management method according to claim 5. [Claim 7] When the card used for transactions via the application program is associated for the first time with the application program installed on the user terminal, the card management method is: The steps include receiving a general-purpose program data packet containing a program necessary for the operation of the security element, transmitted from the server, The steps include loading the general-purpose program data packet into the security element, The card management method according to claim 1, further comprising: [Claim 8] A step of receiving a default card selection input entered by a user, wherein the default card selection input is used to indicate the selected default card, A step of controlling the security element to update the original default card's usage state to an enabled state, wherein the original default card's usage state before the update is the default usage state, The steps include controlling the security element to update the usage state of the default card to the default usage state, The steps include synchronizing the updated usage status of the default card and the updated usage status of the original default card with the server, The card management method according to claim 3, further comprising: [Claim 9] A step of sending a card deletion request message to the server so as to receive a response from the server containing the card transaction identifier of the card to be deleted, wherein the card deletion request message is a message indicating the selected card to be deleted. The steps include receiving the card transaction identifier of the card to be deleted, which has been fed back from the server, The steps include controlling the security element to update the usage status of the card to be deleted to an invalid state, The steps include synchronizing the updated usage status of the card to be deleted with the server, The card management method according to claim 3, further comprising: [Claim 10] After receiving the card transaction identifier of the card to be deleted, transmitted from the server, A step of deleting a second mapping relationship, which is a mapping relationship that associates the dedicated card information of the card to be deleted with the card type of the card to be deleted and the usage status of the card to be deleted. The card management method according to claim 9, further comprising: [Claim 11] A card management method executed on a server, The card management method, in cooperation with the user terminal, manages transaction verification data used when making payment transactions via an application program using a card associated with the application program installed on the user terminal. The server stores first general-purpose personal data and second general-purpose personal data, wherein the first general-purpose personal data is personal data necessary for transaction verification when the card type of the card is a first type, and the second general-purpose personal data is personal data necessary for transaction verification when the card type of the card is a second type different from the first type. The aforementioned card management method is: A response step in which, in response to a message from the user terminal received containing the card authentication information of the card, the card type of the card is determined based on the card authentication information, verification is performed on the card, and if the verification is successful, dedicated card information containing a card transaction identifier is assigned to the card; A transmission step of sending a response message to the user terminal in order to store the dedicated card information assigned to the card in the response step in the security element of the user terminal, in association with the first general-purpose personal data or the second general-purpose personal data, according to the card type determined in the response step, wherein the response message includes the card type of the card determined in the response step and the dedicated card information of the card assigned in the response step. Includes, The dedicated card information transmitted in the transmission step and stored in the security element, and the first general-purpose personal data or the second general-purpose personal data associated with the dedicated card information are used for transaction verification when making a payment transaction with the card via the application program. Card management methods. [Claim 12] If the aforementioned card includes a first card and a second card of the same card type, the dedicated card information and general-purpose personalized data for target matching of the first card are used to verify the transaction of the first card, and the dedicated card information and general-purpose personalized data for target matching of the second card are used to verify the transaction of the second card. The aforementioned target matching general-purpose personalized data is either the first general-purpose personalized data or the second general-purpose personalized data, corresponding to the card type of the first card. The card management method according to claim 11. [Claim 13] A step of synchronizing data obtained from the user terminal, the card usage status and first mapping relationship set on the user terminal, with the server, wherein the first mapping relationship is a mapping relationship that associates the dedicated card information of the card with the card type of the card and the card usage status. The card management method according to claim 11, further comprising: [Claim 14] The response message includes a first response message, a second response message, and a third response message, and the card authentication information includes a card identifier, card type verification information, and input verification code. The transmission step of sending the response message to the user terminal is: When determining the card type of the card in response to a first message transmitted from the user terminal, the steps include: transmitting a first response message to the user terminal, wherein the first response message includes the card type of the card, and the first message includes the card identifier of the card; If the verification of the card type of the card is successful in response to the second message transmitted from the user terminal, the step of sending the second response message to the user terminal, wherein the second message includes the card type verification information corresponding to the card type of the card, and the second response message includes a dynamic verification code. If the verification of the card's verification code is successful in response to the verification message sent from the user terminal, the third response message is sent to the user terminal, wherein the verification message includes an input verification code, and the third response message includes the dedicated card information of the card. The card management method according to claim 11, including the following: [Claim 15] The aforementioned message includes the first message, the second message, and the verification message. The response step, which determines the card type of the card in response to the message sent from the user terminal, performs verification on the card, and if the verification is successful, assigns the dedicated card information to the card, A step of determining the card type of the card based on the card identifier of the card in the first message, A step of performing card type verification on the card using the card type verification information of the card in the second message, If the input verification code in the verification message matches the dynamic verification code, the step is to assign the dedicated card information to the card. The card management method according to claim 14, including the following: [Claim 16] If the card type of the card is the first type, the card type verification information includes the first type verification information. If the card type of the aforementioned card is type 2, the card type verification information includes type 2 verification information. The first type of verification information differs from the second type of verification information. The card management method according to claim 15. [Claim 17] When the card used for transactions via the application program is associated for the first time with the application program installed on the user terminal, the card management method is: A step of sending a general-purpose program data packet containing the program necessary for the operation of the security element to the user terminal, The card management method according to claim 11, further comprising: [Claim 18] A step of synchronizing the usage status of the updated default card on the user terminal and the usage status of the original default card with the server. It further includes, The aforementioned usage state includes the enabled state, the disabled state, and the default usage state. The usage state of the original default card before the update was the default usage state. The card management method according to claim 11. [Claim 19] The steps include: sending the card transaction identifier of the card to be deleted to the user terminal in response to a card deletion request message sent from the user terminal, wherein the card deletion request message is a message indicating the selected card to be deleted; The steps include: synchronizing the updated usage status of the card to be deleted from the user terminal to the server; The card management method according to claim 11, further comprising: [Claim 20] A step of deleting a second mapping relationship, which is a mapping relationship that associates the dedicated card information of the card to be deleted with the card type of the card to be deleted and the usage status of the card to be deleted. The card management method according to claim 19, further comprising: [Claim 21] A user terminal, This system manages transaction verification data used when making payment transactions via an application program using a card associated with the application program installed on the user terminal. The user terminal has a security element, the security element stores first general-purpose personal data and second general-purpose personal data, the first general-purpose personal data is personal data necessary for transaction verification when the card type of the card is a first type, and the second general-purpose personal data is personal data necessary for transaction verification when the card type of the card is a second type different from the first type. The aforementioned user terminal further, A transmission module that sends a message containing the card authentication information to the server in order to cause the server to determine the card type of the card based on the card authentication information of the card and to assign dedicated card information including a card transaction identifier to the card, A receiving module that receives the card type and dedicated card information transmitted from the server, A processing module that loads the dedicated card information received by the receiving module into the security element, stores the dedicated card information in the security element in association with the first general-purpose personal data if the card type received by the receiving module is the first type, and stores the dedicated card information in the security element in association with the second general-purpose personal data if the card type received by the receiving module is the second type, Equipped with, The dedicated card information stored in the security element by the processing module, and the first general-purpose personal data or the second general-purpose personal data associated with the dedicated card information, are used for transaction verification when making a payment transaction with the card via the application program. User terminal. [Claim 22] It is a server, The system manages transaction verification data, which is used when making payment transactions via an application program using a card associated with the application program installed on the user terminal, in cooperation with the user terminal. The server stores first general-purpose personal data and second general-purpose personal data, wherein the first general-purpose personal data is personal data necessary for transaction verification when the card type of the card is a first type, and the second general-purpose personal data is personal data necessary for transaction verification when the card type of the card is a second type different from the first type. The aforementioned server, A receiving module that receives a message containing the card authentication information of the card, transmitted from the user terminal, A processing module that, in response to the message received by the receiving module, determines the card type of the card based on the card authentication information, performs verification on the card, and if the verification is successful, assigns dedicated card information including a card transaction identifier to the card. A transmitting module transmits to the user terminal a response message that includes the card type determined by the processing module and the dedicated card information assigned to the card, in order to store the dedicated card information assigned by the processing module to the card in the security element of the user terminal in association with the first general-purpose personal data or the second general-purpose personal data, according to the card type determined by the processing module. Equipped with, The dedicated card information transmitted from the transmission module and stored in the security element, and the first general-purpose personal data or the second general-purpose personal data associated with the dedicated card information are used for transaction verification when making a payment transaction with the card via the application program. server. [Claim 23] A user terminal, It comprises a processor and memory in which computer program instructions are stored, When the computer program instructions are executed by the processor, the card management method according to any one of claims 1 to 10 is realized. User terminal. [Claim 24] It is a server, It comprises a processor and memory in which computer program instructions are stored, When the computer program instructions are executed by the processor, the card management method according to any one of claims 11 to 20 is realized. server. [Claim 25] It is a card management system, A user terminal as described in claim 23 and a server as described in claim 24, Card management system.

Images