Payment method and device, equipment, storage medium and program product
By storing the virtual card number in the user terminal of the wallet application and generating unique virtual card data in the virtual card management system for contactless payment, the problems of high security and cost in the existing technology are solved, and the effects of improved security and reduced costs are achieved.
Patent Information
- Application Number
- CN202510765722.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-06-09
- Publication Date
- 2025-10-03
AI Technical Summary
The contactless payment functions of existing wallet applications have security risks and high hardware costs. Especially in cross-border payment scenarios, existing technologies cannot simultaneously ensure payment security and reduce costs.
By storing the virtual card number in the user terminal of the wallet application and the key information in the virtual card management system, when contactless payment is required, the complete virtual card data is obtained from the virtual card management system, and the virtual card number and the number of times it is used are used to generate unique virtual card data for contactless payment, avoiding the storage of sensitive information in the user terminal, and using dynamic tokens and cloud verification to enhance security.
It improves payment security and reduces hardware costs, avoids card information leakage and counterfeit card risks, improves user experience, simplifies encryption and decryption processes, and reduces payment costs.
Smart Images

Figure CN120746564A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of payment technology, and in particular to a payment method, device, equipment, storage medium and program product. Background Art
[0002] With the rapid development of payment technology, the dominant domestic payment method is now image code payment using wallet apps, while the dominant overseas payment method is card-based contactless payment. For the "in-house outsourcing" scenario of cross-border payments, resolving the conflict between the dominant overseas card-based contactless payment method and the dominant domestic image code payment method using wallets is crucial.
[0003] Currently, some wallet applications have contactless payment functions. The contactless payment function of wallet applications is usually implemented based on the mobile payment application of Mobile QuickPass or Host-based Card Emulation (HCE) combined with a secure white box product. Among them, the mobile payment application of Mobile QuickPass refers to a mobile payment solution based on a secure element (SE) that integrates hardware-level security technology. Sensitive information is stored in SE to ensure payment security, but the hardware cost is relatively high. HCE combined with a secure white box product is a mobile payment solution that combines software simulation with advanced encryption algorithms. Sensitive information is stored in white box software. However, the security levels of different white box software vary greatly, and there is a risk of sensitive information leakage, making it difficult to ensure payment security.
[0004] Therefore, there is an urgent need for a payment method that can realize the contactless payment function of wallet applications to ensure payment security and reduce payment costs. Summary of the Invention
[0005] The embodiments of the present application provide a payment method, apparatus, device, computer-readable storage medium, and computer program product that can both ensure payment security and reduce payment costs.
[0006] In a first aspect, an embodiment of the present application provides a payment method, applied to a wallet application, the method comprising:
[0007] In response to a user's card payment operation, obtaining a virtual card number pre-stored in the user terminal where the wallet application is located;
[0008] Based on the virtual card number, generating a card data acquisition request;
[0009] Sending the card data acquisition request to a virtual card management system so that the virtual card management system acquires the number of times the virtual card number is used, and generates virtual card data based on the virtual card number and the number of times it is used;
[0010] receiving the virtual card data returned by the virtual card management system;
[0011] Based on the virtual card data, a contactless interaction signal is sent;
[0012] In response to the user's operation of bringing the wallet application close to the merchant terminal, contactless payment is performed based on the contactless interaction signal.
[0013] In a second aspect, an embodiment of the present application provides a payment method applied to a virtual card management system, the method comprising:
[0014] Receive a card data acquisition request for a virtual card number sent by a wallet application;
[0015] In response to the card data acquisition request, acquiring the number of times the virtual card number has been used;
[0016] generating virtual card data based on the virtual card number and the number of uses;
[0017] The virtual card data is sent to the wallet application, so that the wallet application issues a contactless interaction signal based on the virtual card data, and in response to a user's operation of bringing the wallet application close to a merchant terminal, performs a contactless payment based on the contactless interaction signal.
[0018] In a third aspect, an embodiment of the present application provides a payment method, which is applied to a transfer and clearing system, and the method includes:
[0019] Receiving transaction data and target virtual card data sent by the wallet application via the merchant terminal and the acquiring system, wherein the target virtual card data includes a virtual card number;
[0020] generating a virtual card identification request based on the virtual card number;
[0021] Sending the virtual card identification request to a token service providing server, so that the token service providing server determines a routing object of the transaction data and the target virtual card data based on the virtual card number in response to the virtual card identification request;
[0022] In a case where the routing object is a virtual card management system, the transaction data and the target virtual card data are sent to the virtual card management system so that the virtual card management system verifies the target virtual card data, and if the verification passes, generates transaction confirmation information based on the transaction data, and sends the transaction confirmation information to the wallet application to perform contactless payment.
[0023] In a fourth aspect, an embodiment of the present application provides a payment device, applied to a wallet application, comprising:
[0024] A first acquisition module is configured to acquire a virtual card number pre-stored in the user terminal where the wallet application is located in response to a user's card payment operation;
[0025] A first generating module, configured to generate a card data acquisition request based on the virtual card number;
[0026] a first sending module, configured to send the card data acquisition request to a virtual card management system, so that the virtual card management system acquires the number of times the virtual card number is used, and generates virtual card data based on the virtual card number and the number of times it is used;
[0027] A first receiving module, configured to receive the virtual card data returned by the virtual card management system;
[0028] A communication module, configured to send a contactless interaction signal based on the virtual card data;
[0029] The payment module is configured to perform contactless payment based on the contactless interaction signal in response to a user's operation of bringing the wallet application close to a merchant terminal.
[0030] In a fifth aspect, an embodiment of the present application provides a payment device, applied to a virtual card management system, the device comprising:
[0031] A second receiving module is configured to receive a card data acquisition request for a virtual card number sent by a wallet application;
[0032] a second acquisition module, configured to acquire the number of times the virtual card number is used in response to the card data acquisition request;
[0033] A second generating module, configured to generate virtual card data based on the virtual card number and the number of uses;
[0034] a second sending module, configured to send the virtual card data to the wallet application, so that the wallet application issues a contactless interaction signal based on the virtual card data, and perform contactless payment based on the contactless interaction signal in response to a user placing the wallet application close to a merchant terminal.
[0035] In a sixth aspect, an embodiment of the present application provides a payment device, applied to a transfer and clearing system, the device comprising:
[0036] a third receiving module, configured to receive transaction data and target virtual card data sent by the wallet application via the merchant terminal and the acquiring system, wherein the target virtual card data includes a virtual card number;
[0037] a third generating module, configured to generate a virtual card identification request based on the virtual card number;
[0038] a third sending module, configured to send the virtual card identification request to a token service providing server, so that the token service providing server determines, in response to the virtual card identification request, a routing object for the transaction data and the target virtual card data based on the virtual card number;
[0039] The third sending module is further configured to, when the routing object is a virtual card management system, send the transaction data and the target virtual card data to the virtual card management system, so that the virtual card management system verifies the target virtual card data, and, if the verification passes, generate transaction confirmation information based on the transaction data, and send the transaction confirmation information to the wallet application to perform contactless payment.
[0040] In a seventh aspect, an embodiment of the present application provides an electronic device, the device comprising: a processor and a memory storing computer program instructions;
[0041] When the processor executes the computer program instructions, the method in any possible implementation method of the first aspect, the second aspect, or the third aspect is implemented.
[0042] In an eighth aspect, an embodiment of the present application provides a computer-readable storage medium having computer program instructions stored thereon. When the computer program instructions are executed by a processor, the method of any possible implementation method in the first aspect, the second aspect, or the third aspect mentioned above is implemented.
[0043] In the ninth aspect, an embodiment of the present application provides a computer program product. When the instructions in the computer program product are executed by the processor of an electronic device, the electronic device executes a method in any possible implementation method of the first aspect, the second aspect, or the third aspect mentioned above.
[0044] The payment methods, devices, equipment, computer-readable storage media, and computer program products of the embodiments of the present application store a virtual card number in the user terminal where the wallet application resides. When a contactless payment is required, the complete virtual card data, including sensitive information, is retrieved from the virtual card management system based on the virtual card number, and the contactless payment is performed based on the complete virtual card data. This separates the storage of the complete virtual card data used for contactless payment, rather than storing all card information in the user terminal where the wallet application resides. This ensures the security of card information and, consequently, payment security. Furthermore, the virtual card management system generates virtual card data based on the virtual card number and the number of times the virtual card number is used, ensuring that each generated virtual card data is unique. Each virtual card data is used for only one contactless payment, thus avoiding the risk of card information leakage and counterfeit cards and further enhancing payment security. Furthermore, the embodiments of the present application do not require hardware devices to store sensitive information, reducing hardware costs and, in turn, payment costs. Thus, the embodiments of the present application can both ensure payment security and reduce payment costs. BRIEF DESCRIPTION OF THE DRAWINGS
[0045] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following is a brief introduction to the drawings required for use in the embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.
[0046] Figure 1 This is a schematic diagram of the structure of a payment system provided in an embodiment of the present application;
[0047] Figure 2 This is a flow chart of a payment method applied to a wallet application provided in an embodiment of the present application;
[0048] Figure 3 This is a schematic diagram of a payment method selection interface provided in an embodiment of the present application;
[0049] Figure 4 This is a schematic diagram of a wallet application provided by an embodiment of the present application performing data interaction with a user terminal based on a contactless interaction signal;
[0050] Figure 5 This is a flow chart of another payment method applied to a wallet application provided in an embodiment of the present application;
[0051] Figure 6 This is a flow chart of a payment method applied to a virtual card management system provided in an embodiment of the present application;
[0052] Figure 7 This is a flow chart of another payment method applied to a virtual card management system provided in an embodiment of the present application;
[0053] Figure 8 This is a flow chart of a payment method applied to a transfer clearing system provided in an embodiment of the present application;
[0054] Figure 9 This is a schematic diagram of a virtual card activation process provided by an embodiment of the present application;
[0055] Figure 10 This is a schematic diagram of the structure of a payment device applied to a wallet application provided by an embodiment of the present application;
[0056] Figure 11 This is a structural diagram of a payment device applied to a virtual card management system provided by an embodiment of the present application;
[0057] Figure 12 This is a schematic diagram of the structure of a payment device applied to a transfer and clearing system provided in an embodiment of the present application;
[0058] Figure 13 This is a structural diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0059] The features and exemplary embodiments of various aspects of the present application will be described in detail below. In order to make the purpose, technical solutions and advantages of the present application clearer, the present application will be further described in detail below in conjunction with the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain the present application, rather than to limit the present application. For those skilled in the art, the present application can be implemented without the need for some of these specific details. The following description of the embodiments is merely to provide a better understanding of the present application by illustrating the examples of the present application.
[0060] It should be noted that, in this document, relational terms such as first and second, etc., are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the terms "comprises," "comprising," or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article, or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or device. In the absence of further limitations, the elements defined by the phrase "comprising..." do not exclude the presence of other identical elements in the process, method, article, or device comprising the elements.
[0061] In addition, the acquisition, storage, use, and processing of data in the technical solution of this application comply with the relevant provisions of national laws and regulations.
[0062] As mentioned in the background technology section, at present, the contactless payment function of the wallet application is usually implemented based on the mobile phone flash payment application or the host-based card emulation (Host Card Emulation, HCE) combined with a secure white box product. Among them, the mobile phone flash payment application refers to a mobile phone mobile payment solution based on a secure element (SE) that integrates hardware-level security technology. The SE chip is embedded in the mobile phone or smart device as an independent security module, and protects the user's sensitive payment information (such as bank card number, transaction key, etc.) through physical isolation and encryption algorithms to ensure the security of data storage and transmission. In the payment scenario, the user can use fingerprint, facial recognition or password verification, and then use Near Field Communication (NFC) technology to complete the convenient "wave and pay" operation. The anti-tampering characteristics and international financial certification standards of the SE chip enable it to effectively resist malicious attacks and prevent data leakage. This technology takes into account both security and user experience, and has become a digital payment option to replace physical cards.
[0063] However, SE-based mobile payment solutions need to rely on security chip hardware to achieve secure storage of sensitive data on integrated circuit (IC) cards. Although the security is high, the hardware cost is high.
[0064] HCE combined with secure white box products is a mobile payment solution that combines software emulation with advanced cryptographic algorithms. These products use HCE technology to simulate a mobile phone as a virtual bank card, leveraging NFC for convenient "wave and pay" payments. They also rely on white box cryptography to enhance transaction security and mitigate potential risks inherent in HCE in local environments. Compared to traditional SE-based solutions, the HCE + white box approach sacrifices hardware-level security but significantly improves security within the software environment through dynamic tokens, cloud-based authentication, and optimized cryptographic algorithms.
[0065] However, mobile payment solutions based on HCE and secure white boxes rely on software white boxes to store sensitive IC card information. Due to the varying security levels of different white box software, this presents the risk of IC card information leakage. Furthermore, this solution suffers from delayed white box updates, further compromising security. Limited by white box performance, users experience a poor virtual card experience.
[0066] In addition, traditional device cards based on SE chips or HCE+white box software need to write IC card data to the bottom layer of the user device, involving complex encryption and decryption processes. The card writing speed is generally slow (minutes) and the user experience is poor.
[0067] Furthermore, existing virtual card mobile payment solutions reuse the transaction process of physical cards. The security of the issued virtual card relies on the user's mobile phone, which may pose a risk of leakage. Furthermore, confirmation of user intent relies on the collection of a Personal Identification Number (PIN) or signature at an offline terminal. Consequently, the security of the card and transaction relies on offline point-of-sale (POS) terminals, which creates the risk of user denial. Furthermore, since users cannot reconfirm transactions during the transaction process, transactions may be vulnerable to counterfeit card attacks.
[0068] Thus, to address the problems of the prior art, embodiments of the present application provide a payment method, apparatus, device, computer-readable storage medium, and computer program product. The payment method can be applied to contactless payment scenarios using a virtual card in a wallet application. Furthermore, the payment method can be applied to a payment system.
[0069] The following is an introduction to the payment system provided in the embodiment of the present application.
[0070] Figure 1 FIG. 1 is a schematic diagram of a payment system provided in an embodiment of the present application. Figure 1 As shown, the payment system 100 includes a virtual card management system 11, a user terminal 12, a merchant terminal 13, an acquiring system 14, a transfer and clearing system 15, a token service provider server 16, and a wallet service system 17. Specifically, the user terminal 12 is provided with a wallet application 121, an HCE plug-in 122, a modem 123, and a near-field communication plug-in 124. The wallet service system 17 may include a backend server for the wallet application 121. Furthermore, the HCE plug-in 122, the modem 123, and the near-field communication plug-in 124 may be independent of the wallet application 121 or integrated into the wallet application 121, which is not limited here.
[0071] Based on the payment system 100, the payment method in the embodiment of the present application may include a virtual card activation stage and a transaction stage.
[0072] During the virtual card activation phase, the wallet application 121 can respond to the user's virtual card activation operation by obtaining a joint identifier (including the wallet application 121's application identifier, the user identifier for logging into the wallet application 121, and the device identifier of the user terminal 12). Based on the joint identifier, the wallet application 121 generates a virtual card activation request and invokes the HCE plug-in 122 to send the virtual card activation request to the virtual card management system 11. Upon receiving the virtual card activation request, the virtual card management system 11 can first request the token service provider server 16 to generate and return token information (token information) corresponding to the joint identifier. The virtual card management system 11 then uses the master key to perform key diversification based on the token information, generates a subkey corresponding to the token information, and stores the subkey. The token information includes the virtual card number. The virtual card management system 11 can then return a successful virtual card activation response and token information to the wallet application 121. After receiving the token information, the wallet application 121 can store the virtual card number in the token information. It should be noted that if the HCE plug-in 122 is independent of the wallet application 121, the wallet application 121 can call the HCE plug-in 122 to receive the response information and token information, and store the token information in the HCE plug-in 122. If the HCE plug-in 122 is integrated into the wallet application 121, the wallet application 121 can receive the response information and token information, and store the token information in the HCE plug-in 122 in the wallet application 121. In addition, the virtual card management system 11 can also send a notification message indicating the successful activation of the virtual card to the wallet service system 17.
[0073] During the transaction phase, wallet application 121 can, in response to a user's card payment operation, retrieve a pre-stored virtual card number, generate a card data retrieval request based on the virtual card number, and call HCE plug-in 122 to send the card data retrieval request to virtual card management system 11. After receiving the card data retrieval request, virtual card management system 11 can first obtain the number of times the virtual card number has been used, then generate complete virtual card data based on the virtual card number and the number of times the virtual card has been used, and then return the complete virtual card data to wallet application 121. Generating complete virtual card data based on the virtual card number and the number of times the virtual card has been used includes: utilizing a subkey to perform key diversification based on the number of uses, generating a process key corresponding to the number of uses, and then determining the complete virtual card data based on the virtual card number and the process key. After receiving the virtual card data, wallet application 121 can display a prompt message corresponding to the virtual card number based on the virtual card data and issue a contactless interaction signal. After seeing the prompt message, the user can place the wallet application 121 close to the merchant terminal 13 to enable the wallet application 121 to exchange data with the merchant terminal 13 via contactless interaction signals (data interaction includes the wallet application 121 obtaining transaction data from the merchant terminal 13) to make contactless payments. Specifically, the wallet application 121 can call the HCE plug-in 122 to send the contactless interaction signal to the modem 123. The modem 123 can convert the format of the contactless interaction signal to a signal recognizable by the near-field communication plug-in 124, and then send the contactless interaction signal recognizable by the merchant terminal 13 through the near-field communication plug-in 124.
[0074] During contactless payment, the wallet application 121 can send transaction data and virtual card data to the virtual card management system 11 via the merchant terminal 13, the acquiring system 14, and the transfer and clearing system 15. After receiving the virtual card data, the virtual card management system 11 can verify the virtual card data. If verification passes, it generates transaction confirmation information based on the transaction data and sends the transaction confirmation information to the wallet application 121 via the wallet service system 17. The wallet application 121 can display the transaction confirmation information. After the user confirms the transaction confirmation information, the subsequent deduction process can be continued.
[0075] The embodiments of the present application separate the complete virtual card data, that is, store the virtual card number in the user terminal where the wallet application is located, store the key information in the virtual card management system, and then obtain the complete virtual card data including sensitive information from the virtual card management system based on the virtual card number when contactless payment is required. This allows contactless payment based on the complete virtual card data, thereby ensuring the security of card information and, in turn, payment security. In addition, the virtual card management system generates virtual card data based on the virtual card number and the number of times the virtual card number is used, so that the virtual card data generated each time is different, that is, each virtual card data is only used for one contactless payment, avoiding the risk of card information leakage and counterfeit cards, and further improving payment security. In addition, the embodiments of the present application do not require hardware devices to store sensitive information, reducing hardware costs and, in turn, payment costs. Therefore, the embodiments of the present application can both ensure payment security and reduce payment costs.
[0076] The payment method provided in the embodiment of the present application is introduced below.
[0077] Figure 2 The following is a flow chart showing a payment method applied to a wallet application provided by an embodiment of the present application. Figure 2 As shown, the payment method provided in the embodiment of the present application includes the following steps:
[0078] S210: In response to a card payment operation by the user, obtaining a virtual card number pre-stored in the user terminal where the wallet application is located;
[0079] S220: Generate a card data acquisition request based on the virtual card number;
[0080] S230: Send a card data acquisition request to the virtual card management system, so that the virtual card management system acquires the number of times the virtual card number is used, and generates virtual card data based on the virtual card number and the number of times it is used;
[0081] S240: Receive virtual card data returned by the virtual card management system;
[0082] S250: Sending a contactless interaction signal based on the virtual card data;
[0083] S260: In response to the user placing the wallet application close to the merchant terminal, performing contactless payment based on the contactless interaction signal.
[0084] The payment method of the embodiment of the present application stores a virtual card number in the user terminal where the wallet application is located. When a contactless payment is required, the complete virtual card data including sensitive information is obtained from the virtual card management system based on the virtual card number, and the contactless payment is performed based on the complete virtual card data. That is, the complete virtual card data used for contactless payment is stored separately, rather than storing all card information in the user terminal where the wallet application is located. This ensures the security of card information and, in turn, payment security. In addition, the virtual card management system generates virtual card data based on the virtual card number and the number of times the virtual card number is used, so that each generated virtual card data is different. That is, each virtual card data is only used for one contactless payment, avoiding the risk of card information leakage and counterfeit cards, and further improving payment security. In addition, the embodiment of the present application does not require hardware equipment to store sensitive information, reducing hardware costs and, in turn, payment costs. Therefore, the embodiment of the present application can both ensure payment security and reduce payment costs.
[0085] The specific implementation methods of the above steps are introduced below.
[0086] In some embodiments, in S210, the wallet application may display a payment method selection interface. Figure 3 As shown, the payment method selection interface may display multiple payment methods. The multiple payment methods may include scan code payment, card payment, etc. The user's selection of card payment in the payment method selection interface may be a card payment operation.
[0087] In addition, a virtual card number may be pre-stored in the user terminal where the wallet application is located. The virtual card number may be a virtual card number corresponding to a physical card, or a virtual card number corresponding to a joint identifier, which is not limited here. The joint identifier may include the application identifier of the wallet application, the user identifier for logging into the wallet application, and the device identifier of the user terminal where the wallet application is located. The user identifier may include at least one of the account identifier, mobile phone number, and email address of the user logging into the wallet. If the virtual card number is a virtual card number corresponding to the joint identifier, when the user uses the virtual card number for payment, the payment can be deducted from at least one payment account such as a bank card account, a balance account, a consumer finance account, a passbook account, etc. that is bound to the wallet application. The joint identifier can identify the user from dimensions such as the application identifier, the device identifier, and the user identifier.
[0088] In addition, the pre-stored virtual card number can be one or more. If there is only one virtual card number, the wallet application can directly obtain the virtual card number after the user selects to swipe the card to pay. If there are multiple virtual card numbers, after the user selects to swipe the card to pay, multiple virtual card numbers can be displayed, and the user can select a virtual card number from the multiple virtual card numbers.
[0089] To simplify user operations, in some embodiments, if there are multiple virtual card numbers, a default virtual card number can be pre-set for contactless payment. The default virtual card number can be, for example, a virtual card number corresponding to the joint identifier.
[0090] In addition, the joint identifier and the virtual card number can have a one-to-one correspondence. Thus, if contactless payment is pre-configured using the virtual card number corresponding to the joint identifier, the wallet application can also, in response to a user's card swipe payment operation, obtain the wallet application's application identifier, the identifier of the user logging into the wallet application, and the device identifier of the user terminal where the wallet application is located, thereby obtaining the joint identifier and generating a card data acquisition request based on the joint identifier.
[0091] As described above, when a user uses the virtual card number corresponding to the joint identifier to make a payment, the payment can be deducted from at least one of the payment accounts bound to the wallet application, such as a bank card account, a balance account, a consumer finance account, and a passbook account. Therefore, if the default virtual card number is pre-set to the virtual card number corresponding to the joint identifier, in order to ensure successful payment, in some embodiments, the above S210 may specifically include:
[0092] In response to a user's card payment operation, displaying multiple payment accounts;
[0093] Receive a selection operation from a user to select a target payment account from among multiple payment accounts;
[0094] In response to the selection operation, a virtual card number pre-stored in the user terminal where the wallet application is located is obtained.
[0095] Here, multiple payment accounts can include bank card accounts, balance accounts, consumer finance accounts, passbook accounts, and so on. A bank card account can include the payment account corresponding to any physical card linked to the wallet application. A balance account can be the payment account corresponding to the wallet balance. The target payment account can be the account from which funds are debited during contactless payments. After the user selects the target payment account, the wallet application will retrieve the default virtual card number.
[0096] It should be noted that this embodiment of the application is the process of selecting a debit account when a default virtual card number (i.e., the virtual card number corresponding to the joint identifier) has been pre-set for contactless payment. Therefore, no matter which debit account the user selects, the virtual card number obtained by the wallet application is the same.
[0097] In the embodiment of the present application, the success of payment can be ensured by allowing the user to select the target payment account for deduction.
[0098] In addition, to simplify user operations, in some embodiments, a default debit account can be pre-set to save the user the process of selecting a debit account. Furthermore, to ensure payment success, in some embodiments, the payment order between multiple payment accounts can be pre-set so that if the balance of the first-priority payment account is insufficient, the payment will continue using the second-priority payment account.
[0099] Furthermore, the virtual card number can be specifically stored in an HCE plug-in. The HCE plug-in can be independent of the wallet application or integrated into the wallet application, without limitation herein. When the virtual card number corresponds to a joint identifier, the information stored in the HCE plug-in can also include the correspondence between the joint identifier and the virtual card number.
[0100] Based on this, in some embodiments, the above S210 may specifically include:
[0101] In response to a card payment operation by a user, obtaining a joint identifier;
[0102] Based on the federation ID, get the virtual card number stored in the host-based card emulation plugin.
[0103] Specifically, based on the correspondence between the joint identifier and the virtual card number, the virtual card number corresponding to the joint identifier may be searched in the HEC plug-in.
[0104] In some embodiments, at S220, after obtaining the virtual card number, the wallet application may generate a card data acquisition request based on the virtual card number. The card data acquisition request may include the virtual card number, and the card data acquisition request may be used to request the complete virtual card data corresponding to the virtual card number from the virtual card management system. The complete virtual card data may include the virtual card number and key information.
[0105] In addition, if the wallet application obtains a joint identifier, it can generate a card data acquisition request based on the joint identifier to request the virtual card management system to obtain the complete virtual card data corresponding to the joint identifier. In this case, the card data acquisition request can include the joint identifier.
[0106] In some embodiments, in S230 , after generating the card data acquisition request, the wallet application may call the HCE plug-in to send the card data acquisition request to the virtual card management system.
[0107] Alternatively, the virtual card number usage count can be the number of times the virtual card management system receives a card data acquisition request. The virtual card management system can include an application transaction counter (ATC), which can be used to record the number of times the virtual card management system receives a card data acquisition request, thereby obtaining the virtual card number usage count. Thus, upon receiving a card data acquisition request, the virtual card management system can obtain the virtual card number usage count and generate virtual card data based on the virtual card number and the usage count.
[0108] As an example, after the virtual card management system responds to the virtual card activation request of the wallet application, activates the virtual card, obtains the virtual card number and the subkey corresponding to the virtual card number, and then returns the virtual card number to the wallet application and stores the subkey corresponding to the virtual card number in the virtual card management system.
[0109] Since the virtual card management system generates virtual card data based on the virtual card number and the number of times the virtual card number is used, the virtual card data generated each time is different, that is, each virtual card data is only used for one contactless payment. Therefore, the virtual card data can also be called one-time IC card data.
[0110] Based on this, the virtual card management system generates virtual card data based on the virtual card number and the number of uses. Specifically, it may include: using subkeys to disperse the keys based on the number of uses, and generating process keys corresponding to the number of uses; based on the virtual card number and the process key, determining the virtual card data, and returning the virtual card data to the wallet application.
[0111] In some embodiments, in S240 , the wallet application may receive the virtual card data returned by the virtual card management system through the HCE plug-in.
[0112] In some embodiments, in S250, the contactless interaction signal can be used for data exchange between the wallet application and the merchant terminal to implement contactless payment. The contactless interaction signal can be, for example, an NFC signal.
[0113] Furthermore, to improve user experience, in some embodiments, after S240, the method may further include:
[0114] Based on the virtual card data, a prompt message corresponding to the virtual card number is displayed, and the prompt message is used to prompt the user to make a contactless payment based on the virtual card number.
[0115] Here, the prompt information can be a prompt interface displaying a virtual card. In addition to displaying the virtual card, the prompt page can also display an interactive animation corresponding to the contactless interaction signal, as well as text information prompting the user to make a contactless payment, thereby improving the user experience.
[0116] In some embodiments, in S260, the user may bring the user terminal containing the wallet application close to the merchant terminal. If the user terminal and the merchant terminal are successfully connected based on the contactless interaction signal, data interaction between the wallet application and the merchant terminal may be achieved, thereby enabling subsequent contactless payment.
[0117] The schematic diagram of a wallet application provided in an embodiment of the present application interacting with a user terminal for data based on a contactless interactive signal can be as follows: Figure 4 shown.
[0118] Based on this, in order to ensure that the transaction complies with the user's wishes and avoid the risk of the user denying the transaction, in some embodiments, the above S260 may specifically include:
[0119] Receive transaction confirmation information sent by the virtual card management system;
[0120] Display transaction confirmation information;
[0121] In response to the user's confirmation operation on the transaction confirmation information, contactless payment is performed based on the contactless interaction signal.
[0122] Here, the transaction confirmation information may include information such as the transaction party, transaction amount, and transaction details. The virtual card management system may include an online module. During contactless payment, the wallet application may transmit transaction data and virtual card data to the online module of the virtual card management system via the merchant terminal, acquiring system, and transfer and clearing system. After receiving the virtual card data, the online module verifies the virtual card data and, if verification passes, generates transaction confirmation information based on the transaction data. The online module then transmits the transaction confirmation information to the wallet application, which then displays the transaction confirmation information for the user to instantly view the transaction details. The user then completes the transaction confirmation by entering a password, fingerprint, facial recognition, or other verification element on the user terminal, thus providing a secondary confirmation of the transaction. After the user confirms the transaction confirmation information, the subsequent deduction process can proceed. If the user does not confirm the transaction confirmation information, the subsequent deduction process will not proceed and the transaction will fail. Furthermore, if the deduction order between multiple payment accounts is not pre-set, the user can switch the deduction account if a single deduction fails, significantly improving the user's card usage experience.
[0123] In the embodiment of the present application, by requiring the user to perform a second confirmation of the transaction when making a contactless payment, it is possible to ensure that the transaction is in accordance with the user's wishes and avoid the risk of the user denying the transaction.
[0124] In addition, after the wallet application uses the HCE plug-in to complete card emulation, the remaining contactless payment interactive processes with the merchant terminal can reuse the physical card contactless payment process, which will not be detailed here.
[0125] On this basis, in order to ensure the security of card information and thus ensure payment security, as another implementation method of this application, this application also provides another implementation method of the payment method applied to the wallet application. Please refer to the following embodiments for details.
[0126] See Figure 5 The payment method provided in the embodiment of the present application may further include steps S510-S540 before S210 shown in the above embodiment.
[0127] S510 , in response to the user's virtual card activation operation, obtaining a joint identifier, where the joint identifier includes an application identifier of the wallet application, an identifier of a user who logs into the wallet application, and a device identifier of a user terminal where the wallet application is located.
[0128] Here, a virtual card activation control may be displayed in the wallet application. When a user clicks the virtual card activation control, the virtual card activation operation may be performed. After the user clicks the virtual card activation control, the wallet application obtains the application identifier, user identifier, and device identifier to obtain a joint identifier.
[0129] S520: Generate a virtual card activation request based on the joint identifier.
[0130] Here, the virtual card activation request may be used to request the virtual card management system to activate a virtual card corresponding to the joint identifier. The virtual card activation request may include the joint identifier.
[0131] S530, sending a virtual card activation request to the virtual card management system, so that the virtual card management system responds to the virtual card activation request, requests the token service provider server to generate and return token information corresponding to the joint identifier, and uses the master key to disperse the key based on the token information to generate a sub-key corresponding to the token information, the token information includes the virtual card number, the sub-key is used to generate a process key based on the number of uses, and the process key is used to generate virtual card data.
[0132] As mentioned above, the user terminal may be configured with an HCE plug-in. If the HCE plug-in is independent of the wallet application, the wallet application may call the HCE plug-in to send a virtual card activation request to the virtual card management system. Specifically, the wallet application may call the HCE plug-in to send the virtual card activation request to the virtual card management system via the gateway.
[0133] After receiving a virtual card activation request, the virtual card management system can generate a token generation request based on the virtual card activation request and send it to the Token Service Provider (TSP), requesting the TSP to generate token information corresponding to the federated identifier. The token information includes the virtual card number and other relevant information. Other relevant information may include the virtual card number's expiration date, i.e., the virtual card's expiration date. After generating the token information, the TSP can return the token information to the virtual card management system.
[0134] In addition, the master key can include the User Data Key (UDK), the Encryption Key (ENC Key), and the Message Authentication Code Key (MACKey). The UDK is typically used to encrypt user data (such as database fields and file contents) to ensure data confidentiality. The ENCKey is specifically used for symmetric encryption during communication or storage, protecting data in transit. The MAC Key is used to generate a message authentication code to verify data integrity and prevent tampering.
[0135] After receiving the token information, the virtual card management system can use the three master keys to perform key diversification based on the token information, generate three subkeys corresponding to the token information, and store these three subkeys for subsequent generation of complete virtual card data corresponding to the virtual card number. The three subkeys can include UDK (sub), ENCKey (sub), and MAC Key (sub).
[0136] S540: Receive the virtual card number returned by the virtual card management system.
[0137] Here, after the virtual card management system generates the subkey, it can return the virtual card number to the wallet application via the gateway. If the HCE plugin is integrated into the wallet application, the wallet application can receive the virtual card number returned by the virtual card management system through the HCE plugin. If the HCE plugin is independent of the wallet application, the wallet application can call the HCE plugin to receive the virtual card number returned by the virtual card management system and store it in the HCE plugin.
[0138] In some specific examples, after generating the subkey, the virtual card management system may also generate a response message indicating successful virtual card activation, and return the response message and token information to the wallet application via the gateway. Thus, if the HCE plug-in is integrated into the wallet application, the wallet application may receive the response message and token information returned by the virtual card management system through the HCE plug-in. If the HCE plug-in is independent of the wallet application, the wallet application may call the HCE plug-in to receive the response message and token information returned by the virtual card management system, and store the token information in the HCE plug-in.
[0139] In this embodiment, the wallet application responds to user actions, requesting the virtual card management system to activate a virtual card corresponding to the joint identifier. The wallet application also stores the complete virtual card data corresponding to the virtual card separately: the virtual card number is stored in the user terminal, and the key information is stored in the virtual card management system. This ensures that no sensitive information is stored or exposed on the user terminal, thus ensuring the security of contactless payments using virtual cards. Furthermore, by only sending token information to the user terminal when a user first applies for a virtual card, without transmitting sensitive information and eliminating complex encryption and decryption procedures, the card can be issued quickly (in seconds), significantly improving the user's card binding experience.
[0140] Figure 6 FIG1 shows a flow chart of a payment method applied to a virtual card management system provided by an embodiment of the present application. Figure 6 As shown, the payment method provided in the embodiment of the present application includes the following steps:
[0141] S610: Receive a card data acquisition request for a virtual card number sent by a wallet application;
[0142] S620: Responding to the card data acquisition request, obtaining the number of times the virtual card number has been used;
[0143] S630: Generate virtual card data based on the virtual card number and usage count;
[0144] S640: Send the virtual card data to the wallet application, so that the wallet application issues a contactless interaction signal based on the virtual card data, and performs contactless payment based on the contactless interaction signal in response to the user placing the wallet application close to the merchant terminal.
[0145] In an embodiment of the present application, to implement contactless payment, the wallet application needs to carry the virtual card number and request the complete virtual card data from the virtual card management system. This means that by storing the complete virtual card data separately, rather than storing all card information on the user terminal, card information security is ensured, and thus payment security. Furthermore, the virtual card management system responds to the card data acquisition request by obtaining the number of times the virtual card number has been used, and then generates virtual card data based on the virtual card number and the number of uses, ensuring that each generated virtual card data is unique. Thus, by sending virtual card data to the wallet application, the wallet application can perform contactless payment based on this virtual card data. Each virtual card data is used for only one contactless payment, thus avoiding the risk of card information leakage and counterfeit cards, and further enhancing payment security.
[0146] The specific implementation methods of the above steps are introduced below.
[0147] In some embodiments, in S610, the card data acquisition request may be used to acquire complete virtual card data corresponding to the virtual card number. The complete virtual card data may include the virtual card number and sensitive information. The sensitive information may be, for example, key information.
[0148] As an example, the virtual card management system may receive a card data acquisition request sent by the wallet application via the HCE plug-in and the gateway.
[0149] In some embodiments, in S620 , the number of times the virtual card number is used may be the number of times the virtual card management system receives a card data acquisition request.
[0150] Based on this, in order to ensure the accuracy of the usage count, in some embodiments, after the above S610, the method may further include:
[0151] The number of card data acquisition requests corresponding to the virtual card number is recorded to obtain the number of times the virtual card number has been used.
[0152] Here, the virtual card management system may include an application transaction counter (ATC), and the ATC may be used to record the number of times the virtual card management system receives card data acquisition requests, thereby obtaining the number of times the virtual card number is used.
[0153] In this way, after receiving a card data acquisition request for a certain virtual card number, the virtual card management system can respond to the card data acquisition request by first using ATC to perform continuous counting based on this card data acquisition request, and then obtain the number of times obtained after this count from ATC, and then obtain the number of times the virtual card number is used.
[0154] In the embodiment of the present application, the accuracy of the usage count can be ensured by using ATC to record the usage count of the virtual card number and obtaining the usage count from the ATC.
[0155] In some embodiments, in S630 , the virtual card data may include a virtual card number and key information corresponding to the number of uses.
[0156] Based on this, in order to ensure the one-time and integrity of the virtual card data, in some embodiments, the above S630 may specifically include:
[0157] Get the subkey corresponding to the virtual card number;
[0158] Using the subkey, the key is dispersed based on the number of times it is used, and a process key corresponding to the number of times it is used is generated;
[0159] Based on the virtual card number and the session key, the virtual card data is determined.
[0160] Here, the subkey corresponding to the virtual card number can be the key information generated and stored in the background by the virtual card management system during the virtual card activation phase. The subkeys can include UDK (sub), ENC Key (sub), and MAC Key (sub). By using these three subkeys and performing key diversification based on the number of uses, three process keys corresponding to the number of uses can be generated. The three process keys can include UDK (process), ENC Key (process), and MAC Key (process).
[0161] In this way, by determining the virtual card data based on the virtual card number and the process key generated based on the number of uses, the one-time use and integrity of the virtual card data can be guaranteed.
[0162] In some embodiments, in S640, the code-to-card management system can return virtual card data to the wallet application through the gateway and the HCE plug-in. After receiving the virtual card data, the wallet application can send a contactless interaction signal based on the virtual card data, and in response to the user's operation of bringing the wallet application close to the merchant terminal, perform contactless payment based on the contactless interaction signal. Among them, the wallet application and the merchant terminal can exchange data based on the contactless interaction signal. During the data interaction process, the wallet application can use a process key to encrypt relevant data. The specific process of which process keys the wallet application uses to encrypt which data can be referred to the relevant technology and will not be described in detail here.
[0163] In addition, the process of how the wallet application performs contactless payment based on contactless interaction signals can be seen above. Figure 2 The description related to the illustrated embodiment will not be repeated here.
[0164] On this basis, in order to further improve payment security, in some embodiments, after the above S640, the method may further include:
[0165] Receive transaction data and target virtual card data sent by the wallet application via the merchant terminal, acquiring system and transfer clearing system;
[0166] Verify the target virtual card data based on the virtual card data to obtain a verification result;
[0167] If the verification result is passed, a transaction confirmation message is generated based on the transaction data;
[0168] Send transaction confirmation information to the wallet application so that the wallet application displays the transaction confirmation information.
[0169] Here, the virtual card management system may include an online module. The online module may be configured to receive target virtual card data sent by the wallet application, verify the target virtual card data, and, if the verification passes, generate transaction confirmation information based on the transaction data and send the transaction confirmation information to the wallet application.
[0170] Alternatively, the transaction data may be data encrypted using a process key. The target virtual card data may be virtual card data sent by the virtual card management system and received by the wallet application. After receiving the target virtual card data, the online module may parse the target virtual card data to obtain a virtual card number and retrieve the virtual card data corresponding to the virtual card number from the virtual card management system. If the target virtual card data is identical to the target virtual card data, verification of the target virtual card data may be confirmed to have passed. If the target virtual card data is different from the target virtual card data, verification of the target virtual card data may be confirmed to have failed, and the transaction may be canceled.
[0171] If verification passes, the online module generates a transaction confirmation based on the transaction data and sends it to the wallet application via the wallet service system. The wallet application then displays the confirmation. After the user confirms the confirmation, the subsequent deduction process can proceed.
[0172] In addition, in the case where the virtual card number is a virtual card number corresponding to the joint identifier, the embodiment of the present application actually decouples the account attributes of the virtual card (i.e., the virtual card number) and the transaction medium (i.e., the physical card). The virtual card number is only used for contactless interaction and user identity routing of the merchant terminal, and the user uses his own user terminal to confirm the transaction in the logged-in wallet application. Among them, user identity routing is to identify the user identity through the joint identifier, send the transaction confirmation information to the target user terminal held by the target user, and display the transaction confirmation information in the target wallet application. Among them, the target user is the user corresponding to the user identifier in the joint identifier, the target user terminal is the user terminal corresponding to the device identifier in the joint identifier, and the target wallet application is the wallet application corresponding to the application identifier in the joint identifier.
[0173] The embodiment of the present application can further improve payment security by generating transaction confirmation information based on transaction data when the target virtual card data is verified, and sending the transaction confirmation information to the wallet application, so that the wallet application displays the transaction confirmation information for the user to re-confirm the transaction.
[0174] In addition, after the wallet application uses the HCE plug-in to complete card emulation, the remaining contactless payment interactive processes with the merchant terminal can reuse the physical card contactless payment process, which will not be detailed here.
[0175] On this basis, in order to further improve payment security and ensure the system performance of the virtual card management system, in some embodiments, the above S620 may specifically include:
[0176] In response to the card data acquisition request, if the target number of uses within the target duration is less than or equal to a preset threshold, the number of uses of the virtual card number is acquired.
[0177] Here, the target duration can be a pre-set limit on the duration during which virtual card data can be requested. The target usage count can be the number of times a wallet application requests virtual card data within the target duration. The number of uses of a virtual card number can be the total number of times a wallet application requests virtual card data since the virtual card corresponding to the virtual card number was activated. The preset threshold can be the number of virtual card data requests that can be made within the target duration, and the preset threshold can be denoted as N. For example, if the target duration is 10 minutes and N is 3, then within 10 minutes, the wallet application can request and obtain virtual card data three times.
[0178] As an example, after receiving a card data acquisition request, the virtual card management system may first obtain the number of card data acquisition requests received within a target duration, i.e., a target usage count. If the target usage count is less than a preset threshold, the virtual card management system may obtain the total usage count of the virtual card number, generate virtual card data based on the total usage count, and return the virtual card data to the wallet application.
[0179] The embodiment of the present application can prevent malicious users from generating keys indefinitely by limiting the number of times virtual card data is obtained within a target time period, and has the effects of preventing blast attacks and resource abuse, thereby further improving payment security and ensuring the system performance of the virtual card management system.
[0180] Based on this, in order to reduce the maintenance cost of the virtual card management system and further improve payment security, in some embodiments, the above S630 may specifically include:
[0181] When the target number of uses within the target duration is greater than a preset threshold, target virtual card data is obtained, where the target virtual card data is generated based on the virtual card number and the number of uses corresponding to the preset threshold.
[0182] Based on this, the above S640 may specifically include:
[0183] If the target virtual card data is within the validity period, the virtual card data is sent to the wallet application.
[0184] Here, the limited period can be a pre-set validity period for each virtual card data. The validity period can be denoted by T. If the virtual card data is within the validity period, transactions can proceed normally based on the virtual card data. If the virtual card data is not within the validity period, transactions are terminated. Furthermore, the number of uses corresponding to the preset threshold can be the total number of uses corresponding to the virtual card number when the target number of uses is greater than or equal to the preset threshold.
[0185] For example, if the target duration is 10 minutes and N is 3, then within 10 minutes, if the virtual card management system has generated virtual card data three times, when the virtual card management system receives a fourth card data generation request, it will not generate new virtual card data. Instead, it will use the third generated virtual card data as the target virtual card data and send the virtual card data to the wallet application if the target virtual card data is still valid. If the target virtual card data has expired, the transaction will be rejected.
[0186] In this way, by limiting the number of times virtual card data is obtained within the target time period and the validity period of each virtual card data, the attack window is shortened, invalid data is automatically cleaned up, the maintenance cost of the virtual card management system is reduced, and payment security is further improved.
[0187] On this basis, in order to ensure the security of card information and thus ensure payment security, as another implementation method of this application, this application also provides another implementation method of the payment method applied to the wallet application. Please refer to the following embodiments for details.
[0188] See Figure 7The payment method provided in the embodiment of the present application may further include steps S710-S730 before S610 shown in the above embodiment.
[0189] S710: Receive a virtual card activation request sent by a wallet application. The virtual card activation request includes a joint identifier. The joint identifier includes an application identifier of the wallet application, an identifier of a user who logs in to the wallet application, and a device identifier of a user terminal where the wallet application is located.
[0190] S720 : In response to the virtual card activation request, request the token service providing server to generate and return token information corresponding to the joint identifier, where the token information includes the virtual card number.
[0191] After receiving a virtual card activation request, the virtual card management system can generate a token generation request based on the virtual card activation request and send it to the Token Service Provider (TSP), requesting the TSP to generate token information corresponding to the federated identifier. The token information includes the virtual card number and other relevant information. Other relevant information may include the virtual card number's expiration date, i.e., the virtual card's expiration date. After generating the token information, the TSP can return the token information to the virtual card management system.
[0192] Based on this, in order to save system resources, in some embodiments, the above S720 may specifically include:
[0193] In response to the virtual card activation request, determining whether to add a new virtual card number based on the joint identifier;
[0194] When it is determined that a new virtual card number is added, the token service provider server is requested to generate and return token information.
[0195] Here, after generating the token information corresponding to the joint identifier, the virtual card management system can store the joint identifier and its corresponding token information. Thus, upon receiving a virtual card activation request, the virtual card management system can first check whether the joint identifier exists in the system. If not, it can determine that a new virtual card number corresponding to the joint identifier is needed, and then request the token service provider server to generate and return the token information.
[0196] In addition, as mentioned above, the token information may also include the validity period of the virtual card number. Thus, after determining whether to add a new virtual card number, the method may further include:
[0197] In the case where it is determined that no new virtual card number is to be added, determining the validity of the virtual card based on the validity period of the virtual card number;
[0198] In the event that the virtual card is invalid, the token service provider is requested to update the token information corresponding to the virtual card number.
[0199] If the joint identifier exists in the system, it can be determined that there is no need to add a new virtual card number. The validity of the virtual card can then be determined based on the virtual card number's expiration date. If the virtual card number is within the validity period, the virtual card number can be directly returned to the wallet application without reactivating the card. If the virtual card number is not within the validity period, meaning the virtual card is invalid, the token service provider can be requested to update the token information corresponding to the virtual card number, while keeping the virtual card number unchanged.
[0200] In this way, by first determining whether token information needs to be generated before requesting the token service provider server to generate token information, resource waste can be avoided, thereby saving system resources.
[0201] Furthermore, to ensure the security of card information and thus payment security, in some embodiments, after S720, the method may further include:
[0202] Obtain the master key used to encrypt transaction data and card data;
[0203] Using the master key, the key is dispersed based on the token information to generate a subkey corresponding to the token information;
[0204] Store subkeys.
[0205] Here, the master key can include the User Data Key (UDK), the Encryption Key (ENC Key), and the Message Authentication Code Key (MACKey). The UDK is typically used to encrypt user data (such as database fields and file contents) to ensure data confidentiality. The ENCKey is specifically used for symmetric encryption during communication or storage, protecting data in transit. The MAC Key is used to generate a message authentication code to verify data integrity and prevent tampering.
[0206] After receiving the token information, the virtual card management system can use the three master keys to perform key diversification based on the token information, generate three subkeys corresponding to the token information, and store these three subkeys for subsequent generation of complete virtual card data corresponding to the virtual card number. The three subkeys can include UDK (sub), ENCKey (sub), and MAC Key (sub).
[0207] In this way, the complete virtual card data corresponding to the virtual card is stored separately, that is, the virtual card number is stored in the user terminal, and the key information is stored in the virtual card management system, so that no sensitive information is stored or exposed in the user terminal, which can ensure the security of virtual card contactless payment.
[0208] Furthermore, to ensure the success of subsequent contactless payments, in some embodiments, after S720, the method may further include:
[0209] Send a notification message to the wallet business system that the virtual card has been successfully activated.
[0210] By sending a notification message of successful virtual card activation to the wallet business system, the wallet business system can understand for which user the virtual card management system has activated the virtual card, so as to facilitate subsequent virtual card contactless payment and thus ensure the success of subsequent contactless payment.
[0211] S730: Return the virtual card number to the wallet application.
[0212] In addition, other steps of the method in the embodiment of the present application can be found in the above Figure 5 The description of the embodiments shown will not be repeated here.
[0213] In this embodiment of the application, the virtual card management system responds to a virtual card activation request from a wallet application, activates a virtual card corresponding to the joint identifier, and separately stores the complete virtual card data corresponding to the virtual card. Specifically, the virtual card number is stored in the user terminal, and the key information is stored in the virtual card management system. This prevents sensitive information from being stored or exposed on the user terminal, thus ensuring the security of contactless payments using virtual cards. Furthermore, by only sending token information to the user terminal when a user first applies for a virtual card, without transmitting sensitive information and without complex encryption and decryption procedures, the card can be quickly issued (in seconds), greatly improving the user's card binding experience.
[0214] Figure 8 The figure shows a flow chart of a payment method applied to a transfer clearing system provided by an embodiment of the present application. Figure 8 As shown, the payment method provided in the embodiment of the present application includes steps S810-S840.
[0215] S810, receiving transaction data and target virtual card data sent by the wallet application via the merchant terminal and the acquiring system, where the target virtual card data includes a virtual card number.
[0216] S820: Generate a virtual card identification request based on the virtual card number.
[0217] Here, the virtual card identification request can be used to request the TSP to determine a routing target for the transaction data and target virtual card data. The routing target can be the destination to which the transaction data and target virtual card data are sent. If the target virtual card data corresponds to a joint identifier, the routing target can be an online module in the virtual card management system. If the target virtual card data corresponds to a physical card, the routing target can be the issuing system for that physical card.
[0218] S830, sending a virtual card identification request to the token service providing server, so that the token service providing server responds to the virtual card identification request and determines the routing object of the transaction data and the target virtual card data based on the virtual card number.
[0219] Since the token information is generated by the TSP, the TSP can store the correspondence between the token information and the joint identifier, or the correspondence between the token information and the physical card, so that the routing object of the transaction data and the target virtual card data can be determined based on the virtual card number.
[0220] S840, when the routing object is a virtual card management system, sending the transaction data and the target virtual card data to the virtual card management system so that the virtual card management system verifies the target virtual card data, and when the verification passes, generating transaction confirmation information based on the transaction data, and sending the transaction confirmation information to the wallet application to perform contactless payment.
[0221] In addition, other steps of the method in the embodiment of the present application can be found in the above Figure 2 and Figure 6 The description of the embodiments shown will not be repeated here.
[0222] The embodiment of the present application can ensure the accuracy of the sending objects of transaction data and target virtual card data by transferring the routing objects of the clearing system transaction data and target virtual card data, thereby ensuring the success of the transaction.
[0223] In order to better describe the entire solution, some specific examples are given based on the above embodiments.
[0224] For example, Figure 9 As shown, the activation process of a virtual card provided in an embodiment of the present application may include the following steps:
[0225] S91. The wallet application obtains a joint identifier in response to the user's virtual card activation operation, and generates a virtual card activation request based on the joint identifier.
[0226] S92: The wallet application sends a virtual card activation request to the HCE plug-in.
[0227] S93. The HCE plug-in sends a virtual card activation request to the gateway.
[0228] S94. The gateway sends a virtual card activation request to the virtual card management system;
[0229] S95. The virtual card management system generates a token acquisition request based on the virtual card activation request.
[0230] S96. The virtual card management system sends a token acquisition request to the TSP.
[0231] S97. The TSP generates token information in response to the token acquisition request.
[0232] S98. The TSP sends the token information to the virtual card management system.
[0233] S99. The virtual card management system generates a subkey and response information based on the token information, and stores the subkey.
[0234] S910. The virtual card management system sends token information and response information to the gateway.
[0235] S911: The gateway sends token information and response information to the HCE plug-in.
[0236] S912, HCE plug-in stores token information;
[0237] S913. The HCE plug-in sends a response message to the wallet application.
[0238] S914. The virtual card management system sends a notification message indicating successful virtual card activation to the wallet service system.
[0239] In addition, Figure 1 In the example, the virtual card management system on the right can be an online module of the virtual card management system. Figure 1 From the above, the process of contactless payment based on a virtual card in a wallet application provided by an embodiment of the present application may include the following steps:
[0240] S1. The wallet application obtains a joint identifier in response to a user's card payment operation and generates a card data acquisition request based on the virtual card number.
[0241] S2. The wallet application calls the HCE plug-in to send a card data acquisition request to the virtual card management system;
[0242] S3. After responding to the card data acquisition request, the virtual card management system acquires the usage count of the virtual card number corresponding to the joint identifier, and generates virtual card data based on the virtual card number and the usage count of the virtual card.
[0243] S4. The virtual card management system sends the virtual card data to the wallet application through the HCE plug-in;
[0244] S5. The wallet application displays a prompt message corresponding to the virtual card number based on the virtual card data and sends a contactless interaction signal;
[0245] S6. In response to the user placing the wallet application close to the merchant terminal, data interaction is performed with the merchant terminal via a contactless interaction signal; the data interaction includes: obtaining original transaction data, encrypting the original transaction data to obtain transaction data, and sending the transaction data and target virtual card data to the merchant terminal;
[0246] S7. The merchant terminal sends the transaction data and target virtual card data to the acquiring system;
[0247] S8. The acquiring system sends the transaction data and target virtual card data to the transfer and clearing system;
[0248] S9. The transfer clearing system interacts with the TSP to determine the routing object of the transaction data and the target virtual card data;
[0249] S10. When the routing object is a virtual card management system, the transfer clearing system sends the transaction data and target virtual card data to the online module of the virtual card management system;
[0250] S11. The online module verifies the target virtual card data and, if the verification passes, generates transaction confirmation information based on the transaction data and sends the transaction confirmation information to the wallet business system;
[0251] S12. The wallet business system sends transaction confirmation information to the wallet application;
[0252] S13. The wallet application displays transaction confirmation information, allowing the user to reconfirm the transaction;
[0253] S14. After the user confirms the transaction confirmation information, the subsequent deduction process is executed.
[0254] In summary, this application mainly proposes an innovative virtual card generation and application solution. Among them, the innovation of payment elements includes:
[0255] 1) Disposable IC card data (i.e., virtual card data): A data combination that contains all the elements of an IC card contactless transaction. This data can be combined with the IC card application in the HCE plug-in for contactless transactions. Compared to traditional device card local storage, this data is limited to a short-term validity period, eliminating the risk of counterfeit cards and ensuring transaction security.
[0256] 2) Lightweight HCE plug-in: This plug-in is based on Android HCE functionality and integrates IC card applications. It does not store sensitive IC card data and can interact with the backend to achieve flexible updates and upgrades. Since the HCE plug-in does not store sensitive user personal data, it eliminates the complex security chip interaction process in traditional solutions, greatly improving the efficiency of initial card writing (i.e., virtual card activation);
[0257] 3) Virtual card management system: It has the functions of virtual card management, storage and HCE plug-in management.
[0258] In addition, process innovation includes:
[0259] 1) During the virtual card activation phase, the virtual card management system generates virtual IC card data for the user and stores it in the background. It also feeds back the virtual card activation result and desensitized non-sensitive IC data to the user's wallet application for display;
[0260] 2) During the transaction phase, when using the card, the user applies for a one-time IC card data from the virtual card management system backend in real time and writes it into the HCE plug-in in the wallet application to achieve IC card data simulation;
[0261] 3) During the transaction phase, the virtual card management system verifies the transaction data sent from the user terminal in real time, converts it into the actual debit account information, and routes it to the wallet application. Users can reconfirm the transaction as needed;
[0262] 4) The user confirms the transaction information displayed on the wallet application and performs enhanced verification to achieve the unification of the card code payment process.
[0263] Through the issuance and use of disposable IC cards proposed in this application, users can apply for disposable IC card data in real time for contactless NFC interaction, improving data security and increasing card binding speed. Through the new online transaction process proposed in this application, users can confirm transactions on their own mobile phones in real time, achieving a unified card and code transaction experience and improving the prevention and control of counterfeit transactions. In other words, through this application, the security of device cards and the user experience are improved, and the risks of online transactions are reduced. In addition, the payment method of this application is a purely software implementation solution, which does not require the SE to store sensitive information, resulting in rapid function expansion, convenient updates, and low implementation costs.
[0264] Based on the payment method provided in the above embodiment, this application also provides a specific implementation of the payment device. Please refer to the following embodiment.
[0265] like Figure 10 As shown, the payment device 1000 applied to the wallet application provided in the embodiment of the present application includes the following modules:
[0266] A first acquisition module 1010 is configured to acquire a virtual card number pre-stored in the user terminal where the wallet application is located in response to a user's card payment operation;
[0267] A first generating module 1020 is configured to generate a card data acquisition request based on the virtual card number;
[0268] The first sending module 1030 is configured to send a card data acquisition request to the virtual card management system, so that the virtual card management system acquires the number of times the virtual card number is used, and generates virtual card data based on the virtual card number and the number of times the virtual card number is used;
[0269] The first receiving module 1040 is configured to receive virtual card data returned by the virtual card management system;
[0270] The communication module 1050 is used to send a contactless interaction signal based on the virtual card data;
[0271] The payment module 1060 is configured to perform contactless payment based on a contactless interaction signal in response to a user placing the wallet application close to a merchant terminal.
[0272] The payment device 1000 is described in detail below.
[0273] In some embodiments, the payment module 1060 may specifically include:
[0274] A receiving submodule, configured to receive transaction confirmation information sent by the virtual card management system;
[0275] Display submodule, used to display transaction confirmation information;
[0276] The payment submodule is configured to perform contactless payment based on the contactless interaction signal in response to a user's confirmation operation on the transaction confirmation information.
[0277] In some embodiments, the first obtaining module 1010 may specifically include:
[0278] The display submodule is further configured to display multiple payment accounts in response to a card payment operation by the user;
[0279] The receiving submodule is further configured to receive a selection operation by a user to select a target payment account from among multiple payment accounts;
[0280] The first acquisition submodule is configured to, in response to a selection operation, acquire a virtual card number pre-stored in the user terminal where the wallet application is located.
[0281] In some embodiments, the payment device 1000 may further include:
[0282] The display module is used to display prompt information corresponding to the virtual card number based on the virtual card data after receiving the virtual card data returned by the virtual card management system, and the prompt information is used to prompt the user to make contactless payment based on the virtual card number.
[0283] In some embodiments, the first acquisition module 1010 is further configured to, before obtaining, in response to a user's card payment request, a virtual card number pre-stored in the user terminal where the wallet application is located, obtain a joint identifier in response to a user's virtual card activation operation, the joint identifier including an application identifier of the wallet application, an identifier of a user who logs in to the wallet application, and a device identifier of the user terminal where the wallet application is located;
[0284] The first generating module 1020 is further configured to generate a virtual card activation request based on the joint identifier;
[0285] The first sending module 1030 is further configured to send a virtual card activation request to the virtual card management system, so that the virtual card management system, in response to the virtual card activation request, requests the token service provider server to generate and return token information corresponding to the joint identifier, and uses the master key to perform key diversification based on the token information to generate a subkey corresponding to the token information, where the token information includes the virtual card number, and the subkey is used to generate a process key based on the number of uses, and the process key is used to generate virtual card data;
[0286] The first receiving module 1040 is further configured to receive the virtual card number returned by the virtual card management system.
[0287] In some embodiments, a host-based card emulation plug-in is provided in the user terminal. Based on this, the receiving submodule is further configured to call the host-based card emulation plug-in, receive the virtual card number returned by the virtual card management system, and store the virtual card number in the host-based card emulation plug-in.
[0288] Based on this, the first acquisition submodule is further used to:
[0289] In response to a card payment operation by a user, obtaining a joint identifier;
[0290] Based on the federation ID, get the virtual card number stored in the host-based card emulation plugin.
[0291] The embodiments of the present application store a virtual card number in the user terminal where the wallet application is located. When a contactless payment is required, the complete virtual card data, including sensitive information, is obtained from the virtual card management system based on the virtual card number, and the contactless payment is performed based on the complete virtual card data. This means that the complete virtual card data used for contactless payment is stored separately, rather than storing all card information in the user terminal where the wallet application is located. This ensures the security of card information and, in turn, payment security. Furthermore, the virtual card management system generates virtual card data based on the virtual card number and the number of times the virtual card number is used, so that each generated virtual card data is different. That is, each virtual card data is used for only one contactless payment, thus avoiding the risk of card information leakage and counterfeit cards, and further improving payment security. Furthermore, the embodiments of the present application do not require hardware devices to store sensitive information, reducing hardware costs and, in turn, payment costs. Thus, the embodiments of the present application can both ensure payment security and reduce payment costs.
[0292] like Figure 11 As shown, the payment device 1100 applied to the virtual card management system provided in the embodiment of the present application includes the following modules:
[0293] The second receiving module 1110 is configured to receive a card data acquisition request for a virtual card number sent by a wallet application;
[0294] The second acquisition module 1120 is configured to obtain the number of times the virtual card number has been used in response to the card data acquisition request;
[0295] The second generating module 1130 is used to generate virtual card data based on the virtual card number and the number of times used;
[0296] The second sending module 1140 is configured to send the virtual card data to the wallet application, so that the wallet application issues a contactless interaction signal based on the virtual card data, and performs contactless payment based on the contactless interaction signal in response to the user placing the wallet application close to the merchant terminal.
[0297] The payment device 1100 is described in detail below.
[0298] In some embodiments, the second receiving module 1110 is further configured to receive transaction data and target virtual card data sent by the wallet application via the merchant terminal, the acquiring system, and the transfer and clearing system after sending the virtual card data to the wallet application.
[0299] The payment device 1100 may further include:
[0300] A verification module, configured to verify target virtual card data based on the virtual card data to obtain a verification result;
[0301] The second generating module 1130 is further configured to generate transaction confirmation information based on the transaction data when the verification result is that the verification is passed;
[0302] The second sending module 1140 is further configured to send transaction confirmation information to the wallet application, so that the wallet application displays the transaction confirmation information.
[0303] In some embodiments, the second generating module 1130 may specifically include:
[0304] The second acquisition submodule is used to obtain the subkey corresponding to the virtual card number;
[0305] A generation submodule, configured to utilize the subkey to perform key dispersion based on the number of uses and generate a process key corresponding to the number of uses;
[0306] The determination submodule is used to determine the virtual card data based on the virtual card number and the process key.
[0307] In some embodiments, the second acquisition submodule is further configured to, in response to the card data acquisition request, acquire the number of times the virtual card number has been used if the target number of times used within the target duration is less than or equal to a preset threshold.
[0308] In some embodiments, the second acquisition submodule is further used to obtain target virtual card data when the target number of uses within the target time period is greater than a preset threshold. The target virtual card data is virtual card data generated based on the virtual card number and the number of uses corresponding to the preset threshold.
[0309] Based on this, the second sending module 1140 may include:
[0310] The sending submodule is used to send the virtual card data to the wallet application when the target virtual card data is within the validity period.
[0311] In some embodiments, the payment device 1100 may further include:
[0312] The recording module is used to record the number of card data acquisition requests corresponding to the virtual card number after receiving the card data acquisition request for the virtual card number sent by the wallet application, so as to obtain the number of times the virtual card number has been used.
[0313] In some embodiments, the second receiving module 1110 is further configured to receive a virtual card activation request sent by the wallet application before receiving a card data acquisition request for a virtual card number sent by the wallet application. The virtual card activation request includes a joint identifier, which includes an application identifier of the wallet application, an identifier of a user who logs in to the wallet application, and a device identifier of a user terminal where the wallet application is located.
[0314] The payment device 1100 may further include:
[0315] A request module, configured to, in response to a virtual card activation request, request a token service providing server to generate and return token information corresponding to the joint identifier, wherein the token information includes a virtual card number;
[0316] The second sending module 1140 is further configured to return the virtual card number to the wallet application.
[0317] In some embodiments, the second obtaining module 1120 is further configured to obtain a master key for encrypting transaction data and card data after requesting the token service providing server to generate and return token information corresponding to the joint identifier in response to the virtual card activation request;
[0318] The second generation module 1130 is further configured to use the master key to perform key dispersion based on the token information and generate a subkey corresponding to the token information;
[0319] The payment device 1100 may further include:
[0320] A storage module is used to store subkeys.
[0321] In some embodiments, the request module may specifically include:
[0322] a determination submodule, configured to determine whether to add a new virtual card number based on the joint identifier in response to the virtual card activation request;
[0323] The request submodule is used to request the token service provider server to generate and return token information when a new virtual card number is determined.
[0324] In some embodiments, the token information also includes the validity period of the virtual card number. Based on this, the determination submodule is further configured to determine the validity of the virtual card based on the validity period of the virtual card number when it is determined that the virtual card number is not to be added;
[0325] The request submodule is also used to request the token service provider server to update the token information corresponding to the virtual card number when the virtual card is invalid.
[0326] In some embodiments, the second sending module 1140 is further used to send a notification message of successful virtual card activation to the wallet business system after requesting the token service providing server to generate and return token information corresponding to the joint identifier in response to the virtual card activation request.
[0327] In an embodiment of the present application, to implement contactless payment, the wallet application needs to carry the virtual card number and request the complete virtual card data from the virtual card management system. This means that by storing the complete virtual card data separately, rather than storing all card information on the user terminal, card information security is ensured, and thus payment security. Furthermore, the virtual card management system responds to the card data acquisition request by obtaining the number of times the virtual card number has been used, and then generates virtual card data based on the virtual card number and the number of uses, ensuring that each generated virtual card data is unique. Thus, by sending virtual card data to the wallet application, the wallet application can perform contactless payment based on this virtual card data. Each virtual card data is used for only one contactless payment, thus avoiding the risk of card information leakage and counterfeit cards, and further enhancing payment security.
[0328] like Figure 12 As shown, the payment device 1200 provided in the embodiment of the present application for use in the transfer and clearing system includes the following modules:
[0329] The third receiving module 1210 is configured to receive transaction data and target virtual card data sent by the wallet application via the merchant terminal and the acquiring system, wherein the target virtual card data includes a virtual card number;
[0330] The third generating module 1220 is configured to generate a virtual card identification request based on the virtual card number;
[0331] The third sending module 1230 is configured to send a virtual card identification request to the token service providing server, so that the token service providing server determines a routing object of the transaction data and the target virtual card data based on the virtual card number in response to the virtual card identification request;
[0332] The third sending module 1230 is also used to send transaction data and target virtual card data to the virtual card management system when the routing object is a virtual card management system, so that the virtual card management system can verify the target virtual card data, and generate transaction confirmation information based on the transaction data when the verification is passed, and send the transaction confirmation information to the wallet application to perform contactless payment.
[0333] The embodiment of the present application can ensure the accuracy of the sending objects of transaction data and target virtual card data by transferring the routing objects of the clearing system transaction data and target virtual card data, thereby ensuring the success of the transaction.
[0334] Based on the payment method provided in the above embodiment, the embodiment of the present application also provides a specific implementation of the electronic device. Figure 13 A schematic diagram of an electronic device 1300 provided in an embodiment of the present application is shown.
[0335] The electronic device 1300 may include a processor 1310 and a memory 1320 storing computer program instructions.
[0336] Specifically, the processor 1310 may include a central processing unit (CPU), or an application-specific integrated circuit (ASIC), or may be configured to implement one or more integrated circuits of the embodiments of the present application.
[0337] Memory 1320 may include a large capacity memory for data or instructions. By way of example and not limitation, memory 1320 may include a hard disk drive (HDD), a floppy disk drive, a flash memory, an optical disk, a magneto-optical disk, a magnetic tape, or a universal serial bus (USB) drive, or a combination of two or more of these. Where appropriate, memory 1320 may include removable or non-removable (or fixed) media. Where appropriate, memory 1320 may be internal or external to electronic device 1300. In a particular embodiment, memory 1320 is a non-volatile solid-state memory.
[0338] In certain embodiments, memory 1320 can be implemented in the form of ROM (Read Only Memory), RAM (Random Access Memory), static storage devices, dynamic storage devices, etc. Memory 1320 can store an operating system and other application programs. When the technical solutions provided in the embodiments of this specification are implemented through software or firmware, the relevant program code is stored in memory 1320 and called and executed by processor 1310. Processor 1310 implements any of the payment methods in the above embodiments by reading and executing the computer program instructions stored in memory 1320.
[0339] The processor 1310 implements any one of the payment methods in the above embodiments by reading and executing computer program instructions stored in the memory 1320 .
[0340] In one example, the electronic device 1300 may further include a communication interface 1330 and a bus 1340. Figure 13 As shown, the processor 1310 , the memory 1320 , and the communication interface 1330 are connected via a bus 1340 and communicate with each other.
[0341] The communication interface 1330 is mainly used to implement communication between various modules, devices, units and / or equipment in the embodiments of the present application.
[0342] Bus 1340 comprises hardware, software or both, couples the parts of electronic equipment to each other.For example, and not limitation, bus can comprise accelerated graphics port (AGP) or other graphics bus, enhanced industry standard architecture (EISA) bus, front side bus (FSB), hypertransport (HT) interconnection, industry standard architecture (ISA) bus, infinite bandwidth interconnection, low pin count (LPC) bus, memory bus, micro channel architecture (MCA) bus, peripheral component interconnection (PCI) bus, PCI-Express (PCI-X) bus, serial advanced technology attachment (SATA) bus, video electronics standard association local (VLB) bus or other suitable bus or two or more of these combinations.In suitable cases, bus 1340 can comprise one or more buses.Although the present application embodiment describes and shows specific bus, the application considers any suitable bus or interconnection.
[0343] Illustratively, the electronic device 1300 may be a mobile phone, a tablet computer, a laptop computer, a PDA, an in-vehicle electronic device, an ultra-mobile personal computer (UMPC), a netbook, or a personal digital assistant (PDA).
[0344] The electronic device can execute the payment method in the embodiment of the present application, thereby realizing the combination Figures 2 to 12 The payment method and device described herein have the beneficial effects of the corresponding method embodiments and will not be described in detail here.
[0345] In addition, in conjunction with the payment methods in the above embodiments, embodiments of the present application may provide a computer-readable storage medium for implementation. The computer-readable storage medium stores computer program instructions; when the computer program instructions are executed by a processor, any one of the payment methods in the above embodiments is implemented.
[0346] The computer-readable media of this embodiment include permanent and non-permanent, removable and non-removable media that can be used to store information by any method or technology. The information can be computer-readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, read-only compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, tape disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device.
[0347] The computer program instructions stored in the storage medium of the above embodiment are used to enable the computer to execute the payment method shown in any of the above embodiments, and have the beneficial effects of the corresponding method embodiments, which will not be repeated here.
[0348] In combination with the payment method in the above embodiments, the present application can provide a computer program product to implement the payment method in the above embodiments. When the instructions in the computer program product are executed by a processor of an electronic device, any one of the payment methods in the above embodiments is implemented.
[0349] The computer program product of the above embodiment is used to implement the payment method shown in any of the above embodiments, and has the beneficial effects of the corresponding method embodiment, which will not be repeated here.
[0350] It should be understood that the present application is not limited to the specific configurations and processes described above and illustrated in the figures. For the sake of brevity, a detailed description of known methods is omitted here. In the above embodiments, several specific steps are described and illustrated as examples. However, the method process of the present application is not limited to the specific steps described and illustrated. Those skilled in the art can make various changes, modifications, and additions, or change the order of the steps after understanding the spirit of the present application.
[0351] The functional blocks shown in the above-described block diagram can be implemented as hardware, software, firmware or a combination thereof. When implemented in hardware, they can be, for example, electronic circuits, application specific integrated circuits (ASICs), appropriate firmware, plug-ins, function cards, etc. When implemented in software, the elements of the present application are programs or code segments that are used to perform the required tasks. The program or code segment can be stored in a machine-readable medium, or transmitted on a transmission medium or a communication link by a data signal carried in a carrier wave. "Machine-readable medium" can include any medium that can store or transmit information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, ROMs, flash memories, erasable ROMs (EROMs), floppy disks, CD-ROMs, optical disks, hard disks, optical fiber media, radio frequency (RF) links, etc. The code segment can be downloaded via a computer network such as the Internet, an intranet, etc.
[0352] It should also be noted that the exemplary embodiments mentioned in this application describe some methods or systems based on a series of steps or devices. However, this application is not limited to the order of the above steps. In other words, the steps can be performed in the order mentioned in the embodiments, or in a different order, or several steps can be performed simultaneously.
[0353] Aspects of the present application have been described above with reference to the flowcharts and / or block diagrams of the methods, devices (systems) and computer program products according to the embodiments of the present application. It should be understood that each box in the flowchart and / or block diagram and the combination of each box in the flowchart and / or block diagram can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer or other programmable data processing device to produce a machine so that these instructions executed via the processor of the computer or other programmable data processing device enable the implementation of the function / action specified in one or more boxes of the flowchart and / or block diagram. This processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor or a field programmable logic circuit. It is also understood that each box in the block diagram and / or the flowchart and the combination of the boxes in the block diagram and / or the flowchart can also be implemented by the dedicated hardware that performs the specified function or action, or can be implemented by the combination of dedicated hardware and computer instructions.
[0354] The above description is only a specific embodiment of the present application. Those skilled in the art will clearly understand that for the convenience and brevity of description, the specific working processes of the systems, modules and units described above can refer to the corresponding processes in the aforementioned method embodiments, and will not be repeated here. It should be understood that the scope of protection of the present application is not limited thereto. Any person skilled in the art can easily think of various equivalent modifications or replacements within the technical scope disclosed in the present application, and these modifications or replacements should be included in the scope of protection of the present application.
Claims
1. A payment method, characterized in that: Applied to a wallet application, the method includes: In response to a user's card payment operation, obtaining a virtual card number pre-stored in the user terminal where the wallet application is located; Based on the virtual card number, generating a card data acquisition request; Sending the card data acquisition request to a virtual card management system so that the virtual card management system acquires the number of times the virtual card number is used, and generates virtual card data based on the virtual card number and the number of times it is used; receiving the virtual card data returned by the virtual card management system; Based on the virtual card data, a contactless interaction signal is sent; In response to the user's operation of bringing the wallet application close to the merchant terminal, contactless payment is performed based on the contactless interaction signal.
2. The method according to claim 1, characterized in that The performing contactless payment based on the contactless interaction signal includes: Receiving transaction confirmation information sent by the virtual card management system; displaying the transaction confirmation information; In response to a user's confirmation operation on the transaction confirmation information, a contactless payment is performed based on the contactless interaction signal.
3. The method according to claim 1, characterized in that The step of obtaining a virtual card number pre-stored in the user terminal where the wallet application is located in response to the user's card payment operation includes: In response to a user's card payment operation, displaying multiple payment accounts; receiving a selection operation by a user to select a target payment account from the multiple payment accounts; In response to the selection operation, a virtual card number pre-stored in the user terminal where the wallet application is located is obtained.
4. The method according to claim 1, wherein After receiving the virtual card data returned by the virtual card management system, the method further includes: Based on the virtual card data, prompt information corresponding to the virtual card number is displayed, where the prompt information is used to prompt the user to make a contactless payment based on the virtual card number.
5. The method according to any one of claims 1 to 4, characterized in that Before obtaining the virtual card number pre-stored in the user terminal where the wallet application is located in response to the user's card payment request, the method further includes: In response to a user's virtual card activation operation, obtaining a joint identifier, the joint identifier including an application identifier of the wallet application, an identifier of a user logging into the wallet application, and a device identifier of a user terminal where the wallet application is located; generating a virtual card activation request based on the joint identifier; sending the virtual card activation request to the virtual card management system, so that the virtual card management system, in response to the virtual card activation request, requests a token service providing server to generate and return token information corresponding to the joint identifier, and uses a master key to perform key diversification based on the token information to generate a subkey corresponding to the token information, wherein the token information includes the virtual card number, the subkey is used to generate a process key based on the number of uses, and the process key is used to generate the virtual card data; Receive the virtual card number returned by the virtual card management system.
6. The method according to claim 5, characterized in that The user terminal is provided with a host-based card simulation plug-in, and the receiving of the virtual card number returned by the virtual card management system includes: calling the host-based card emulation plug-in, receiving the virtual card number returned by the virtual card management system, and storing the virtual card number in the host-based card emulation plug-in; The step of obtaining a virtual card number pre-stored in the user terminal where the wallet application is located in response to the user's card payment operation includes: In response to a card payment operation by the user, obtaining the joint identifier; Based on the joint identifier, the virtual card number stored in the host-based card emulation plug-in is obtained.
7. A payment method, characterized in that: Applied to a virtual card management system, the method includes: Receive a card data acquisition request for a virtual card number sent by a wallet application; In response to the card data acquisition request, acquiring the number of times the virtual card number has been used; generating virtual card data based on the virtual card number and the number of uses; The virtual card data is sent to the wallet application, so that the wallet application issues a contactless interaction signal based on the virtual card data, and in response to a user's operation of bringing the wallet application close to a merchant terminal, performs a contactless payment based on the contactless interaction signal.
8. The method according to claim 7, characterized in that After sending the virtual card data to the wallet application, the method further includes: Receiving transaction data and target virtual card data sent by the wallet application via the merchant terminal, the acquiring system, and the transfer and clearing system; Verifying the target virtual card data based on the virtual card data to obtain a verification result; If the verification result is that the verification is passed, generating transaction confirmation information based on the transaction data; The transaction confirmation information is sent to the wallet application, so that the wallet application displays the transaction confirmation information.
9. The method according to claim 7, characterized in that The generating virtual card data based on the virtual card number and the number of times used includes: Obtaining a subkey corresponding to the virtual card number; Using the subkey, performing key dispersion based on the number of uses, and generating a process key corresponding to the number of uses; Based on the virtual card number and the process key, the virtual card data is determined.
10. The method according to claim 7, characterized in that The step of obtaining the number of times the virtual card number is used in response to the card data acquisition request includes: In response to the card data acquisition request, if the target number of uses within the target duration is less than or equal to a preset threshold, the number of uses of the virtual card number is acquired.
11. The method according to claim 10, characterized in that The generating virtual card data based on the virtual card number and the number of times used includes: If the target number of uses within the target duration is greater than the preset threshold, obtaining target virtual card data, the target virtual card data being virtual card data generated based on the virtual card number and the number of uses corresponding to the preset threshold; The sending the virtual card data to the wallet application includes: If the target virtual card data is within a valid period, the virtual card data is sent to the wallet application.
12. The method according to any one of claims 7 to 11, characterized in that: After receiving the card data acquisition request for the virtual card number sent by the wallet application, the method further includes: The number of card data acquisition requests corresponding to the virtual card number is recorded to obtain the number of times the virtual card number has been used.
13. The method according to any one of claims 7 to 11, characterized in that: Before receiving the card data acquisition request for the virtual card number sent by the wallet application, the method further includes: Receiving a virtual card activation request sent by the wallet application, the virtual card activation request including a joint identifier, the joint identifier including an application identifier of the wallet application, a user identifier for logging into the wallet application, and a device identifier of a user terminal where the wallet application is located; In response to the virtual card activation request, requesting a token service providing server to generate and return token information corresponding to the joint identifier, wherein the token information includes the virtual card number; The virtual card number is returned to the wallet application.
14. The method according to claim 13, characterized in that After requesting the token service providing server to generate and return token information corresponding to the joint identifier in response to the virtual card activation request, the method further includes: Obtain the master key used to encrypt transaction data and card data; Using the master key, performing key dispersion based on the token information to generate a subkey corresponding to the token information; The subkey is stored.
15. The method according to claim 14, characterized in that The step of requesting the token service providing server to generate and return token information corresponding to the joint identifier in response to the virtual card activation request includes: In response to the virtual card activation request, determining whether to add a new virtual card number based on the joint identifier; When it is determined that a new virtual card number is added, the token service providing server is requested to generate and return the token information.
16. The method according to claim 15, characterized in that The token information also includes the validity period of the virtual card number. After determining whether to add a new virtual card number, the method further includes: If it is determined that no new virtual card number is to be added, determining the validity of the virtual card based on the validity period of the virtual card number; In the event that the virtual card is invalid, the token service providing server is requested to update the token information corresponding to the virtual card number.
17. The method according to claim 13, wherein After requesting the token service providing server to generate and return token information corresponding to the joint identifier in response to the virtual card activation request, the method further includes: Send a notification message to the wallet business system that the virtual card has been successfully activated.
18. A payment method, characterized in that: Applied to a transfer clearing system, the method includes: Receiving transaction data and target virtual card data sent by the wallet application via the merchant terminal and the acquiring system, wherein the target virtual card data includes a virtual card number; generating a virtual card identification request based on the virtual card number; Sending the virtual card identification request to a token service providing server, so that the token service providing server determines a routing object of the transaction data and the target virtual card data based on the virtual card number in response to the virtual card identification request; In a case where the routing object is a virtual card management system, the transaction data and the target virtual card data are sent to the virtual card management system so that the virtual card management system verifies the target virtual card data, and if the verification passes, generates transaction confirmation information based on the transaction data, and sends the transaction confirmation information to the wallet application to perform contactless payment.
19. A payment device, characterized in that: Applied to wallet applications, the device includes: A first acquisition module is configured to acquire a virtual card number pre-stored in the user terminal where the wallet application is located in response to a user's card payment operation; A first generating module, configured to generate a card data acquisition request based on the virtual card number; a first sending module, configured to send the card data acquisition request to a virtual card management system, so that the virtual card management system acquires the number of times the virtual card number is used, and generates virtual card data based on the virtual card number and the number of times it is used; A first receiving module, configured to receive the virtual card data returned by the virtual card management system; A communication module, configured to send a contactless interaction signal based on the virtual card data; The payment module is configured to perform contactless payment based on the contactless interaction signal in response to a user's operation of bringing the wallet application close to a merchant terminal.
20. A payment device, characterized in that: Applied to a virtual card management system, the device comprises: A second receiving module is configured to receive a card data acquisition request for a virtual card number sent by a wallet application; a second acquisition module, configured to acquire the number of times the virtual card number is used in response to the card data acquisition request; A second generating module, configured to generate virtual card data based on the virtual card number and the number of uses; a second sending module, configured to send the virtual card data to the wallet application, so that the wallet application issues a contactless interaction signal based on the virtual card data, and perform contactless payment based on the contactless interaction signal in response to a user placing the wallet application close to a merchant terminal.
21. A payment device, characterized in that: Applied to a transfer and clearing system, the device comprises: a third receiving module, configured to receive transaction data and target virtual card data sent by the wallet application via the merchant terminal and the acquiring system, wherein the target virtual card data includes a virtual card number; a third generating module, configured to generate a virtual card identification request based on the virtual card number; a third sending module, configured to send the virtual card identification request to a token service providing server, so that the token service providing server determines, in response to the virtual card identification request, a routing object for the transaction data and the target virtual card data based on the virtual card number; The third sending module is further configured to, when the routing object is a virtual card management system, send the transaction data and the target virtual card data to the virtual card management system, so that the virtual card management system verifies the target virtual card data, and, if the verification passes, generate transaction confirmation information based on the transaction data, and send the transaction confirmation information to the wallet application to perform contactless payment.
22. An electronic device, characterized in that: The electronic device includes: a processor and a memory storing computer program instructions; When the processor executes the computer program instructions, the payment method according to any one of claims 1-6, 7-17 or 18 is implemented.
23. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer program instructions, which, when executed by a processor, implement the payment method according to any one of claims 1-6, 7-17 or 18.
24. A computer program product, characterized in that When the instructions in the computer program product are executed by a processor of an electronic device, the electronic device executes the payment method as described in any one of claims 1-6 or 7-17 or 18.
Citation Information
Cited By
Cross-border non-contact payment method, device and system
CN121073472A
Cross-border contactless payment method, apparatus and system
CN121073472B
