Privacy protection method, device, electronic device and medium for user digital wallet

Abstract

The disclosed embodiment discloses a privacy protection method, device, electronic device and medium for a user digital wallet, the method comprising: obtaining the first encrypted information of the user digital wallet ID of the target user at the user end; determining the target bank corresponding to the first encrypted information, and obtaining the bank private key and the payment private key of the third-party payment acquiring end pre-agreed with the target bank; using the bank private key and the payment private key to encrypt the payment digital wallet ID of the target user at the third-party payment acquiring end, and obtaining the second encrypted information of the payment digital wallet ID of the target user at the third-party payment acquiring end; establishing an association relationship between the first encrypted information and the second encrypted information, and adding the association relationship to the set association relationship list of the third-party payment acquiring end. The scheme can determine the user identity and protect the user privacy without knowing the user digital wallet ID.

Description

Technical Field

[0001] The present disclosure relates to the field of computer technology, and more particularly to a method, device, electronic device, and medium for protecting the privacy of a user's digital wallet. Background Art

[0002] With the rapid development of the Internet, artificial intelligence technology, 5G and other technologies, the digital economy has brought a great impetus to development. The form of currency is also changing in the process of digital economic development. Compared with traditional currency, digital currency has the advantages of low cost and high efficiency. It is an inevitable trend for digital currency to replace existing paper money, coins and other currencies.

[0003] Each bank will assign a unique user digital wallet ID to users who open digital currency. Due to sensitive data and data security considerations, banks are reluctant to pass digital wallet IDs to third-party payment acquirers. In order to protect user privacy, third-party payment acquirers are also not suitable for passing the payment digital wallet ID assigned to users to other institutions, such as banks. However, for third-party payment acquirers, it is very important to obtain the user's user digital wallet ID along with the payment order to analyze and identify transaction risks. Similarly, it is necessary for the target bank to conduct risk analysis based on the target user's payment digital wallet ID. If the user's digital wallet ID cannot be obtained, it is not conducive to determining risks, such as determining whether large transactions involve money laundering risks.

[0004] To this end, it is necessary to provide a solution that can obtain the user identity along with the payment order without reducing data security and protecting user privacy. Summary of the invention

[0005] The embodiments of the present disclosure provide a privacy protection method, device, electronic device and medium for a user's digital wallet.

[0006] In a first aspect, the present disclosure provides a privacy protection method for a user's digital wallet, including:

[0007] Obtaining first encrypted information of the user digital wallet ID of the target user at the user end;

[0008] Determine the target bank corresponding to the first encrypted information, and obtain the bank private key and the payment private key of the third-party payment acquirer pre-agreed with the target bank;

[0009] After encrypting the payment digital wallet ID of the target user at the third-party payment acquiring terminal using the bank private key and the payment private key, second encrypted information of the payment digital wallet ID of the target user at the third-party payment acquiring terminal is obtained;

[0010] An association relationship between the first encrypted information and the second encrypted information is established, and the association relationship is added to a set association relationship list of the third-party payment acquirer.

[0011] In a second aspect, the present disclosure provides a privacy protection method for a digital payment wallet, including:

[0012] Obtain the second encrypted information of the payment digital wallet ID of the target user at the third-party payment acquiring terminal;

[0013] Determine the third-party payment acquirer corresponding to the second encrypted information, and obtain the bank private key and the payment private key of the third-party payment acquirer pre-agreed with the third-party payment acquirer;

[0014] After encrypting the user digital wallet ID of the target user using the bank private key and the payment private key, first encrypted information of the user digital wallet ID of the target user on the user side is obtained;

[0015] An association relationship between the first encrypted information and the second encrypted information is established, and the association relationship is added to a set association relationship list of the target bank.

[0016] In a third aspect, an embodiment of the present disclosure provides a method for confirming a user identity, including:

[0017] Obtain payment information; the payment information includes first encrypted information of a user digital wallet ID of a target user;

[0018] Matching the first encrypted information with a set association relationship list to obtain second encrypted information matching the first encrypted information; the set association relationship list is established based on the method described in the first aspect;

[0019] Determine the payment digital wallet ID of the target user corresponding to the payment information based on the second encrypted information;

[0020] The identity of the target user is determined based on the payment digital wallet ID.

[0021] In a fourth aspect, an embodiment of the present disclosure provides a method for confirming a user identity, including:

[0022] Acquire settlement information; the settlement information includes second encrypted information of the payment digital wallet ID of the target user;

[0023] Matching the second encrypted information with a set association relationship list to obtain first encrypted information matching the second encrypted information; the set association relationship list is established based on the method described in the second aspect;

[0024] Determine the user digital wallet ID of the target user based on the first encrypted information;

[0025] The identity of the target user is determined based on the user digital wallet ID.

[0026] In a fifth aspect, an embodiment of the present disclosure provides a privacy protection device for a user's digital wallet, including:

[0027] A first acquisition module is configured to acquire first encrypted information of a user digital wallet ID of a target user at a user terminal;

[0028] A first determination module is configured to determine a target bank corresponding to the first encrypted information, and obtain a bank private key pre-agreed with the target bank and a payment private key of a third-party payment acquirer;

[0029] The second acquisition module is configured to encrypt the payment digital wallet ID of the target user at the third-party payment acquirer by using the bank private key and the payment private key, and obtain the second encrypted information of the payment digital wallet ID of the target user at the third-party payment acquirer;

[0030] The first establishing module is configured to establish an association relationship between the first encrypted information and the second encrypted information, and add the association relationship to a set association relationship list of the third-party payment acquiring terminal.

[0031] In a sixth aspect, an embodiment of the present disclosure provides a privacy protection device for a digital payment wallet, including:

[0032] A third acquisition module is configured to obtain second encrypted information of the payment digital wallet ID of the target user at the third-party payment acquiring terminal;

[0033] A second determination module is configured to determine the third-party payment acquirer corresponding to the second encrypted information, and obtain a bank private key and a payment private key of the third-party payment acquirer pre-agreed with the third-party payment acquirer;

[0034] A fourth acquisition module is configured to encrypt the user digital wallet ID of the target user by using the bank private key and the payment private key, and obtain first encrypted information of the user digital wallet ID of the target user at the user end;

[0035] The second establishing module is configured to establish an association relationship between the first encrypted information and the second encrypted information, and add the association relationship to a set association relationship list of the target bank.

[0036] In a seventh aspect, an embodiment of the present disclosure provides a device for confirming a user identity, including:

[0037] A fifth acquisition module is configured to acquire payment information; the payment information includes first encrypted information of a user digital wallet ID of a target user;

[0038] a sixth acquisition module, configured to match the first encrypted information with a set association relationship list to obtain second encrypted information matching the first encrypted information; the set association relationship list is established based on the apparatus according to the fifth aspect;

[0039] A third determination module is configured to determine the payment digital wallet ID of the target user corresponding to the payment information based on the second encrypted information;

[0040] The fourth determination module is configured to determine the identity of the target user based on the payment digital wallet ID.

[0041] In an eighth aspect, an embodiment of the present disclosure provides a device for confirming a user identity, including:

[0042] A seventh acquisition module is configured to acquire settlement information; the settlement information includes second encrypted information of the payment digital wallet ID of the target user;

[0043] an eighth acquisition module, configured to match the second encrypted information with a set association relationship list to obtain first encrypted information matching the second encrypted information; the set association relationship list is established based on the apparatus according to the sixth aspect;

[0044] A fifth determination module is configured to determine a user digital wallet ID of the target user based on the first encrypted information;

[0045] The sixth determination module is configured to determine the identity of the target user based on the user digital wallet ID.

[0046] The functions can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the functions.

[0047] In one possible design, the structure of the above-mentioned device includes a memory and a processor, the memory is used to store one or more computer instructions that support the above-mentioned device to execute the above-mentioned corresponding method, and the processor is configured to execute the computer instructions stored in the memory. The above-mentioned device may also include a communication interface for the above-mentioned device to communicate with other devices or communication networks.

[0048] In a fifth aspect, an embodiment of the present disclosure provides an electronic device, including a memory and a processor, wherein the memory is used to store one or more computer instructions that support any of the above-mentioned devices to execute the above-mentioned corresponding methods, and the processor is configured to execute the computer instructions stored in the memory. Any of the above-mentioned devices may also include a communication interface for communicating with other devices or communication networks.

[0049] In a sixth aspect, an embodiment of the present disclosure provides a computer-readable storage medium for storing computer instructions used by any of the above-mentioned devices, which includes computer instructions involved in executing any of the above-mentioned methods.

[0050] In a seventh aspect, an embodiment of the present disclosure provides a computer program product, which includes computer instructions, and when the computer instructions are executed by a processor, they are used to implement the steps of the method described in any of the above aspects.

[0051] The technical solution provided by the embodiments of the present disclosure may have the following beneficial effects:

[0052] In the disclosed embodiment, at the third-party payment acquiring end, the bank private key and the payment private key are negotiated with the target bank in advance, the bank private key is the private key of the target bank, and the payment private key is the private key of the third-party payment acquiring end. When the target bank needs to transmit the user digital wallet ID of the target user, it can use the bank private key negotiated in advance with the third-party payment acquiring end and the payment private key of the third-party payment acquiring end to encrypt the user digital wallet ID to obtain the first encrypted information, which can be provided to the third-party payment acquiring end when needed, for example, it can be sent to the third-party payment acquiring end by the target bank alone, or transmitted to the third-party payment acquiring end along with the payment order of the target user. After the third-party payment acquirer obtains the first encrypted information, it can determine the target bank corresponding to the first encrypted information, that is, determine which bank encrypted the first encrypted information, and then obtain the bank private key pre-negotiated with the target bank and the payment private key set by the third-party payment acquirer for the target bank, and use the bank private key and the payment private key to encrypt the payment digital wallet ID of the target user, obtain the second encrypted information of the payment digital wallet ID of the target user at the third-party payment acquirer, establish the association relationship between the first encrypted information and the second encrypted information at the third-party payment acquirer, and add the association relationship to the set association relationship list of the third-party payment acquirer. In this way, an association relationship is established between the first encrypted information of the user digital wallet ID and the second encrypted information of the payment digital wallet ID of the same target user, so that even if the third-party payment acquirer does not know the user digital wallet ID of the target user, it can still determine the identity of the target user based on the first encrypted information of the user digital wallet ID, so that risk assessment can be performed at the third-party payment acquirer. This method can not only enable the third-party payment acquirer to determine the identity of the user without knowing the user digital wallet ID, but also protect the privacy of the user.

[0053] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the embodiments of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0054] Other features, purposes and advantages of the embodiments of the present disclosure will become more apparent through the following detailed description of non-limiting embodiments in conjunction with the accompanying drawings. In the accompanying drawings:

[0055] Figure 1 A flow chart of a method for protecting the privacy of a user's digital wallet according to an embodiment of the present disclosure is shown.

[0056] Figure 2 A flowchart of a method for protecting the privacy of a digital payment wallet according to an embodiment of the present disclosure is shown.

[0057] Figure 3A flow chart showing a method for confirming a user identity according to an embodiment of the present disclosure is shown.

[0058] Figure 4 A flow chart showing a method for confirming a user identity according to another embodiment of the present disclosure.

[0059] Figure 5 A structural block diagram of a privacy protection device for a user's digital wallet according to an embodiment of the present disclosure is shown.

[0060] Figure 6 A structural block diagram of a privacy protection device for a digital payment wallet according to an embodiment of the present disclosure is shown.

[0061] Figure 7 A structural block diagram of a device for confirming a user identity according to an embodiment of the present disclosure is shown.

[0062] Figure 8 A structural block diagram of a device for confirming a user identity according to another embodiment of the present disclosure is shown.

[0063] Fig. 9 It is a structural diagram of a computer system suitable for implementing a privacy protection method for a user digital wallet, a privacy protection method for a payment digital wallet and / or a method for confirming a user identity according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0064] Hereinafter, exemplary embodiments of the present disclosure will be described in detail with reference to the accompanying drawings so that those skilled in the art can easily implement them. In addition, for the sake of clarity, parts not related to the description of the exemplary embodiments are omitted in the accompanying drawings.

[0065] In the embodiments of the present disclosure, it should be understood that terms such as "including" or "having" are intended to indicate the existence of features, numbers, steps, behaviors, components, parts, or a combination thereof disclosed in this specification, and are not intended to exclude the possibility of one or more other features, numbers, steps, behaviors, components, parts, or a combination thereof existing or being added.

[0066] It should also be noted that, in the absence of conflict, the embodiments and features in the embodiments of the present disclosure may be combined with each other. The embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0067] Figure 1 A flowchart of a method for protecting the privacy of a user's digital wallet according to an embodiment of the present disclosure is shown as follows: Figure 1 As shown, the privacy protection method of the user digital wallet includes the following steps:

[0068] In step S101, first encrypted information of a user digital wallet ID of a target user at a user terminal is obtained;

[0069] In step S102, the target bank corresponding to the first encrypted information is determined, and the bank private key pre-agreed with the target bank and the payment private key of the third-party payment acquirer are obtained;

[0070] In step S103, after encrypting the payment digital wallet ID of the target user at the third-party payment acquirer using the bank private key and the payment private key, second encrypted information of the payment digital wallet ID of the target user at the third-party payment acquirer is obtained;

[0071] In step S104, an association relationship between the first encrypted information and the second encrypted information is established, and the association relationship is added to a set association relationship list of the third-party payment acquirer.

[0072] As mentioned above, each bank will assign a unique user digital wallet ID to users who open digital currency. Due to sensitive data and data security considerations, banks are reluctant to pass digital wallet IDs to third-party payment acquirers. In order to protect user privacy, third-party payment acquirers are also not suitable for passing the payment digital wallet ID assigned to users to other institutions, such as banks. However, for third-party payment acquirers, it is very important to obtain the user's user digital wallet ID along with the payment order to analyze and identify transaction risks. Similarly, it is necessary for the target bank to conduct risk analysis based on the target user's payment digital wallet ID. If the user's digital wallet ID cannot be obtained, it is not conducive to determining risks, such as determining whether large transactions involve money laundering risks.

[0073] To this end, a solution is needed that can obtain the user identity along with the payment order without reducing data security.

[0074] To this end, the third-party payment acquirer negotiates with the target bank in advance on the bank private key and the payment private key, where the bank private key is the private key of the target bank, and the payment private key is the private key of the third-party payment acquirer. When the target bank needs to transmit the user digital wallet ID of the target user, it can use the bank private key negotiated in advance with the third-party payment acquirer and the payment private key of the third-party payment acquirer to encrypt the user digital wallet ID to obtain the first encrypted information, which can be provided to the third-party payment acquirer when needed, for example, it can be sent to the third-party payment acquirer by the target bank alone, or transmitted to the third-party payment acquirer along with the payment order of the target user. After the third-party payment acquirer obtains the first encrypted information, it can determine the target bank corresponding to the first encrypted information, that is, determine which bank encrypted the first encrypted information, and then obtain the bank private key pre-negotiated with the target bank and the payment private key set by the third-party payment acquirer for the target bank, and use the bank private key and the payment private key to encrypt the payment digital wallet ID of the target user, obtain the second encrypted information of the payment digital wallet ID of the target user at the third-party payment acquirer, establish the association relationship between the first encrypted information and the second encrypted information at the third-party payment acquirer, and add the association relationship to the set association relationship list of the third-party payment acquirer. In this way, an association relationship is established between the first encrypted information of the user digital wallet ID and the second encrypted information of the payment digital wallet ID of the same target user, so that even if the third-party payment acquirer does not know the user digital wallet ID of the target user, it can still determine the identity of the target user based on the first encrypted information of the user digital wallet ID, so that risk assessment can be performed at the third-party payment acquirer. This method can not only enable the third-party payment acquirer to determine the identity of the user without knowing the user digital wallet ID, but also protect the privacy of the user.

[0075] In some embodiments, the target user may be any user who has opened a digital wallet at the target bank, and the target user pays for the order through the digital wallet, and the third-party payment acquirer is the payment acquirer for the order. The target bank may be any bank. The third-party payment acquirer may pre-negotiate the bank private key and the payment private key with one or more target banks. The bank private key is the private key of the target bank, and the payment private key is the private key of the third-party payment acquirer. Each target bank may have a fixed and unique bank private key, and each third-party payment acquirer may also have a fixed and unique payment private key.

[0076] In some embodiments, different target banks correspond to different bank private keys, and the third-party payment acquirer also corresponds to different payment private keys.

[0077] In other embodiments, the same target bank may correspond to the same or different bank private keys for different third-party payment acquirers, and the same third-party payment acquirer may correspond to the same or different bank private keys for different target banks. The payment private key of the third-party payment acquirer may be provided in advance to the corresponding target bank, and the bank private key of the target bank may be provided in advance to the corresponding third-party payment acquirer.

[0078] In some embodiments, the first encrypted information may be information obtained by encrypting the user digital wallet ID of the target user on the user side by using the bank private key and the payment private key of the third-party payment acquirer.

[0079] In some embodiments, the target bank may transmit the first encrypted information separately to the third-party payment acquirer so that the third-party payment acquirer can establish a connection between the user digital wallet ID and the payment digital wallet ID of the same target user based on the first encrypted information. Such connection can be established through the corresponding association relationship between the first encrypted information of the user digital wallet ID and the payment digital wallet ID.

[0080] After the third-party payment acquirer obtains the first encrypted information from the target bank, it can determine the target bank corresponding to the first encrypted information. In some embodiments, the target bank can transmit the identification of the target bank together with the first encrypted information to the third-party payment acquirer, so that the target bank corresponding to the first encrypted information can be determined.

[0081] After determining the target bank, the bank private key and payment private key that the third-party payment acquirer has pre-negotiated with the target bank can be determined, and the payment digital wallet ID of the target user can be encrypte using the bank private key and payment private key to obtain the second encrypted information of the target user.

[0082] The payment digital wallet ID of the target user can be allocated to the target user by the third-party payment acquirer, and the payment digital wallet ID is unique to the third-party payment acquirer.

[0083] The third-party payment acquirer can establish an association relationship between the first encrypted information and the second encrypted information corresponding to the target user, and add the association relationship to the set association relationship list of the third-party payment acquirer. In the subsequent transaction process, the target bank can encrypt the user digital wallet ID of the target user into the first encrypted information, and transmit it to the third-party payment acquirer along with the payment order. After the third-party payment acquirer obtains the first encrypted information, it can match the first encrypted information with the set association relationship list to obtain the second encrypted information that matches the first encrypted information, thereby determining the payment wallet ID of the target user corresponding to the payment order. In this way, even if the third-party payment acquirer is not sure of the user digital wallet ID of the target user of the payment order, it can still uniquely determine the identity of the target user through the payment digital wallet ID, and can also conduct risk assessment for the target user or the merchant involved in the payment order of the target user.

[0084] In one embodiment of the present disclosure, the privacy protection method of the user's digital wallet is suitable for execution at a third-party payment acquiring end.

[0085] In the disclosed embodiment, for the same bank and the same third-party acquiring payment terminal, the agreed bank private key and payment private key are fixed and unique, which can ensure that the encrypted result of the user digital wallet ID is unique. Because the target bank has the user digital wallet ID of the C-end user, and the third-party acquiring payment terminal has the payment digital wallet ID of the B-end user, the bank private key and payment private key are used to encrypt the user digital wallet ID at the bank end, and the payment digital wallet ID is encrypted at the third-party acquiring payment terminal, which can ensure that the user digital wallet ID and the payment digital wallet ID cannot be unilaterally cracked.

[0086] In one embodiment of the present disclosure, for the same third-party payment acquirer, the same target bank corresponds to the same bank private key and the payment private key, while different target banks correspond to different bank private keys and the payment private keys.

[0087] In one embodiment of the present disclosure, step S103, i.e., using the bank private key and the payment private key to encrypt the payment digital wallet ID of the target user at the third-party payment acquirer, to obtain the second encrypted information of the payment digital wallet ID of the target user at the third-party payment acquirer, further includes the following steps:

[0088] The bank private key and the payment private key are mixed with the payment digital wallet ID, and then an MD5 operation is performed to obtain the second encrypted information.

[0089] In this optional implementation, the bank private key and the payment private key can be mixed in the payment digital wallet ID, and then the mixed result is subjected to MD5 operation, and the operation result is used as the second encrypted information. In this way, the second encrypted information is the encrypted information of the payment digital wallet ID, and the second encrypted information can be transmitted to the target bank when needed. The target bank can confirm the identity of the target user based on the second encrypted information, but the target bank cannot decrypt the payment digital wallet ID of the target user. In this way, the target bank can have the user digital wallet ID of the target user, but cannot have the payment digital wallet ID of the target user, and the third-party payment acquiring end can have the payment digital wallet ID of the target user, but cannot have the user digital wallet ID of the target user. This method further protects the privacy of the target user. In addition, since the third-party payment acquiring end establishes an association relationship between the first encrypted information and the second encrypted information, after receiving the first encrypted information from the target bank, the third-party payment acquiring end can match and determine the second encrypted information of the target user through the association relationship, and the second encrypted information is correspondingly associated with the payment digital wallet ID of the target user, so the identity of the target user can be confirmed, so that risk assessment can be performed on the information related to the payment order of the target user.

[0090] MD5 is an irreversible encryption algorithm, but for a user digital wallet ID that is of fixed length and composed entirely of numbers, direct MD5 encryption can still be used to crack the original user digital wallet ID through database collision. However, if the bank private key and payment private key are mixed with the user digital wallet ID and then encrypted, it will not be possible to crack it through database collision.

[0091] In one embodiment of the present disclosure, the step of mixing the bank private key and the payment private key with the payment digital wallet ID and performing MD5 operation to obtain the second encrypted information further includes the following steps:

[0092] After placing the bank private key and the payment private key at fixed positions of the payment digital wallet ID, an MD5 operation is performed to obtain the second encrypted information.

[0093] In this optional implementation, the bank private key and the payment private key can be placed at a fixed position of the payment digital wallet ID, and then an MD5 operation can be performed, and the result of the operation can be used as the second encrypted information. In this way, each time the third-party payment acquirer encrypts the payment digital wallet ID, the bank private key and the payment private key are placed at a fixed position of the payment wallet ID, so that the second encrypted information obtained each time is the same. Therefore, after the second encrypted information is transmitted to the target bank, it can be used as the fixed encrypted information of the payment digital wallet ID of the target user. After establishing an association relationship with the first encrypted information, the second encrypted information can be used to match and determine the user identity of the target user in the future. This method will not leak the payment digital wallet ID of the target user, and can also confirm the user identity of the target user based on the second encrypted information, that is, it protects the privacy of the target user and facilitates the target bank to confirm the identity of the target user.

[0094] In some embodiments, the bank private key and the payment private key may be placed at the end of the user's digital wallet ID, for example.

[0095] Figure 2 A flowchart of a method for protecting the privacy of a digital payment wallet according to an embodiment of the present disclosure is shown as follows: Figure 2 As shown, the privacy protection method of the payment digital wallet includes the following steps:

[0096] In step S201, the second encrypted information of the payment digital wallet ID of the target user at the third-party payment acquiring terminal is obtained;

[0097] In step S202, the third-party payment acquirer corresponding to the second encrypted information is determined, and a bank private key and a payment private key of the third-party payment acquirer pre-agreed with the third-party payment acquirer are obtained;

[0098] In step S203, the user digital wallet ID of the target user is encrypted using the bank private key and the payment private key to obtain first encrypted information of the user digital wallet ID of the target user on the user end;

[0099] In step S204, an association relationship between the first encrypted information and the second encrypted information is established, and the association relationship is added to a set association relationship list of the target bank.

[0100] As mentioned above, each bank will assign a unique user digital wallet ID to users who open digital currency. Due to sensitive data and data security considerations, banks are reluctant to pass digital wallet IDs to third-party payment acquirers. In order to protect user privacy, third-party payment acquirers are also not suitable for passing the payment digital wallet ID assigned to users to other institutions, such as banks. However, for third-party payment acquirers, it is very important to obtain the user's user digital wallet ID along with the payment order to analyze and identify transaction risks. Similarly, it is necessary for the target bank to conduct risk analysis based on the target user's payment digital wallet ID. If the user's digital wallet ID cannot be obtained, it is not conducive to determining risks, such as determining whether large transactions involve money laundering risks.

[0101] To this end, it is necessary to provide a solution that can facilitate banks in risk assessment and protect user privacy.

[0102] To this end, the target bank negotiates with the third-party payment acquirer in advance on the bank private key and the payment private key, where the bank private key is the private key of the target bank, and the payment private key is the private key of the third-party payment acquirer. When the third-party payment acquirer needs to transmit the payment digital wallet ID of the target user, it can use the bank private key negotiated in advance with the target bank and the payment private key of the third-party payment acquirer to encrypt the payment digital wallet ID to obtain the second encrypted information, which can be provided to the target bank when needed, for example, it can be sent to the target bank by the third-party payment acquirer alone, or carried in other data and transmitted to the target bank. After the target bank obtains the second encrypted information, it can determine the third-party payment acquirer corresponding to the second encrypted information, that is, determine which third-party payment acquirer encrypted the second encrypted information, and then obtain the bank private key pre-negotiated with the third-party payment acquirer and the payment private key set by the target bank for the third-party payment acquirer, and use the bank private key and the payment private key to encrypt the user digital wallet ID of the target user, obtain the first encrypted information of the user digital wallet ID of the target user at the third-party payment acquirer, establish the association relationship between the first encrypted information and the second encrypted information in the target bank, and add the association relationship to the set association relationship list of the target bank. In this way, an association relationship is established between the first encrypted information of the user digital wallet ID of the same target user and the second encrypted information of the payment digital wallet ID, so that even if the target bank does not know the payment digital wallet ID of the target user, it can still determine the identity of the target user based on the second encrypted information of the payment digital wallet ID, so that it can perform risk assessment at the target bank. This method can enable the target bank to determine the identity of the user without knowing the payment digital wallet ID, thereby protecting the privacy of the user.

[0103] In some embodiments, the target user may be any user who has opened a digital wallet at the target bank, and the target user has made order payments through the digital wallet, and the third-party payment acquirer is the payment acquirer for the order. The target bank may be any bank. The target bank may pre-negotiate the bank private key and the payment private key with one or more third-party payment acquirers. The bank private key is the private key of the target bank, and the payment private key is the private key of the third-party payment acquirer. Each target bank may have a fixed and unique bank private key for the same third-party payment acquirer, and each third-party payment acquirer may also have a fixed and unique payment private key for the same target bank. Of course, it is understandable that the target bank may only set one bank private key for all third-party payment acquirers, and the third-party payment acquirer may only set one payment private key for all target banks.

[0104] In some embodiments, different target banks correspond to different bank private keys, and the third-party payment acquirer also corresponds to different payment private keys.

[0105] In other embodiments, the same target bank may correspond to the same or different bank private keys for different third-party payment acquirers, and the same third-party payment acquirer may correspond to the same or different bank private keys for different target banks. The payment private key of the third-party payment acquirer may be provided in advance to the corresponding target bank, and the bank private key of the target bank may be provided in advance to the corresponding third-party payment acquirer.

[0106] In some embodiments, the second encrypted information may be information obtained by encrypting the payment digital wallet ID of the target user at the third-party payment acquirer using the bank private key and the payment private key.

[0107] In some embodiments, the third-party payment acquirer can transmit the second encrypted information separately to the target bank, so that the target bank can establish a connection between the user digital wallet ID and the payment digital wallet ID of the same target user based on the second encrypted information. This connection can be established through the corresponding association relationship between the first encrypted information of the user digital wallet ID and the payment digital wallet ID.

[0108] After the target bank obtains the second encrypted information from the third-party payment acquirer, it can determine the third-party payment acquirer corresponding to the second encrypted information. In some embodiments, the third-party payment acquirer can transmit the identification of the third-party payment acquirer together with the second encrypted information to the target bank, so as to determine the third-party payment acquirer corresponding to the second encrypted information.

[0109] After determining the third-party payment acquirer, the bank private key and payment private key that the target bank has pre-negotiated with the third-party payment acquirer can be determined, and the user digital wallet ID of the target user can be encrypted using the bank private key and payment private key to obtain the first encrypted information of the target user.

[0110] The user digital wallet ID of the target user may be allocated to the target user by the target bank, and the user digital wallet ID is unique in the target bank.

[0111] The target bank can establish an association relationship between the first encrypted information and the second encrypted information corresponding to the target user, and add the association relationship to the set association relationship list of the target bank. In the subsequent transaction process, the target bank can encrypt the user digital wallet ID of the target user into the first encrypted information and transmit it to the target bank along with other data. After the target bank obtains the second encrypted information, it can match the second encrypted information with the set association relationship list to obtain the first encrypted information that matches the second encrypted information, thereby determining the user digital wallet ID of the target user corresponding to the other data. In this way, even if the target bank is not sure of the payment digital wallet ID of the target user corresponding to the other data, it can still uniquely determine the identity of the target user through the user digital wallet ID, and can also conduct risk assessment for the target user or the merchant involved in the target user.

[0112] In one embodiment of the present disclosure, the privacy protection method of the payment digital wallet is suitable for execution at the target bank end.

[0113] In the disclosed embodiment, for the same bank and the same third-party acquiring payment terminal, the agreed bank private key and payment private key are fixed and unique, which can ensure that the encrypted result of the user digital wallet ID is unique. Because the target bank has the user digital wallet ID of the C-end user, and the third-party acquiring payment terminal has the payment digital wallet ID of the B-end user, the bank private key and payment private key are used to encrypt the user digital wallet ID at the bank end, and the payment digital wallet ID is encrypted at the third-party acquiring payment terminal, which can ensure that the user digital wallet ID and the payment digital wallet ID cannot be unilaterally cracked.

[0114] In one embodiment of the present disclosure, for the same third-party payment acquirer, the same target bank corresponds to the same bank private key and the payment private key, while for different third-party payment acquirers, the same target bank corresponds to different bank private keys and the payment private keys.

[0115] In one embodiment of the present disclosure, step S203, i.e., using the bank private key and the payment private key to encrypt the user digital wallet ID of the target user to obtain the first encrypted information of the user digital wallet ID of the target user on the user side, further includes the following steps:

[0116] The bank private key and the payment private key are mixed with the user digital wallet ID, and an MD5 operation is performed to obtain the first encrypted information of the user digital wallet ID of the target user at the user end.

[0117] In this optional implementation, the bank private key and the payment private key can be mixed in the user digital wallet ID, and then the mixed result is subjected to MD5 operation, and the operation result is used as the first encrypted information. In this way, the first encrypted information is the encrypted information of the user digital wallet ID, and the first encrypted information can be transmitted to the third-party payment acquiring terminal when needed. The third-party payment acquiring terminal can confirm the identity of the target user based on the first encrypted information, but the third-party payment acquiring terminal cannot decrypt the user digital wallet ID of the target user. In this way, the target bank can have the user digital wallet ID of the target user, but cannot have the payment digital wallet ID of the target user, and the third-party payment acquiring terminal can have the payment digital wallet ID of the target user, but cannot have the user digital wallet ID of the target user. This method further protects the privacy of the target user. In addition, since the target bank establishes an association relationship between the first encrypted information and the first encrypted information, after the target bank receives the second encrypted information from the third-party payment acquiring terminal, it can match and determine the first encrypted information of the target user through the association relationship, and the first encrypted information is correspondingly associated with the user digital wallet ID of the target user, so the identity of the target user can be confirmed, so that risk assessment can be performed on other relevant information of the target user.

[0118] MD5 is an irreversible encryption algorithm, but for a user digital wallet ID that is of fixed length and composed entirely of numbers, direct MD5 encryption can still be used to crack the original user digital wallet ID through database collision. However, if the bank private key and payment private key are mixed with the user digital wallet ID and then encrypted, it will not be possible to crack it through database collision.

[0119] In one embodiment of the present disclosure, the step of mixing the bank private key and the payment private key with the user digital wallet ID and performing MD5 operation to obtain the first encrypted information of the user digital wallet ID of the target user at the user end further includes the following steps:

[0120] After placing the bank private key and the payment private key at fixed positions of the user digital wallet ID, an MD5 operation is performed to obtain the first encrypted information.

[0121] In this optional implementation, the bank private key and the payment private key can be placed at a fixed position of the payment digital wallet ID, and then an MD5 operation can be performed, and the result of the operation can be used as the first encrypted information. In this way, each time the target bank encrypts the user's digital wallet ID, the bank private key and the payment private key are placed at a fixed position of the payment wallet ID, so that the first encrypted information obtained each time is the same. Therefore, after the first encrypted information is transmitted to the third-party payment acquiring end, it can be used as the fixed encrypted information of the user digital wallet ID of the target user. After establishing an association relationship between it and the second encrypted information, the first encrypted information can be used to match and determine the user identity of the target user in the future. This method will not leak the user digital wallet ID of the target user, and can also confirm the user identity of the target user based on the first encrypted information, that is, it protects the privacy of the target user and facilitates the third-party payment acquiring end to confirm the identity of the target user.

[0122] In some embodiments, the bank private key and the payment private key may be placed at the end of the payment digital wallet ID.

[0123] Figure 3 A flowchart showing a method for confirming a user identity according to an embodiment of the present disclosure is shown as follows: Figure 3 As shown, the method for confirming the user identity includes the following steps:

[0124] In step S301, transaction information is obtained; the transaction information includes first encrypted information of the user digital wallet ID of the target user;

[0125] In step S302, the first encrypted information is matched with a set association relationship list to obtain second encrypted information matching the first encrypted information; the set association relationship list is established based on the privacy protection method of the user digital wallet;

[0126] In step S303, the payment digital wallet ID of the target user corresponding to the payment information is determined based on the second encrypted information;

[0127] In step S304, the identity of the target user is determined based on the payment digital wallet ID.

[0128] As mentioned above, each bank will assign a unique user digital wallet ID to users who open digital currency. Due to sensitive data and data security considerations, banks are reluctant to pass digital wallet IDs to third-party payment acquirers. In order to protect user privacy, third-party payment acquirers are also not suitable for passing the payment digital wallet ID assigned to users to other institutions, such as banks. However, for third-party payment acquirers, it is very important to obtain the user's user digital wallet ID along with the payment order to analyze and identify transaction risks. Similarly, it is necessary for the target bank to conduct risk analysis based on the target user's payment digital wallet ID. If the user's digital wallet ID cannot be obtained, it is not conducive to determining risks, such as determining whether large transactions involve money laundering risks.

[0129] To this end, a solution is needed that can confirm the user's identity without reducing data security.

[0130] To this end, the third-party payment acquirer negotiates with the target bank in advance on the bank private key and the payment private key, where the bank private key is the private key of the target bank, and the payment private key is the private key of the third-party payment acquirer. When the target bank needs to transmit the user digital wallet ID of the target user, it can use the bank private key negotiated in advance with the third-party payment acquirer and the payment private key of the third-party payment acquirer to encrypt the user digital wallet ID to obtain the first encrypted information, which can be provided to the third-party payment acquirer when needed, for example, it can be sent to the third-party payment acquirer by the target bank alone, or transmitted to the third-party payment acquirer along with the payment order of the target user. After the third-party payment acquirer obtains the first encrypted information, it can determine the target bank corresponding to the first encrypted information, that is, determine which bank encrypted the first encrypted information, and then obtain the bank private key pre-negotiated with the target bank and the payment private key set by the third-party payment acquirer for the target bank, and use the bank private key and the payment private key to encrypt the payment digital wallet ID of the target user, obtain the second encrypted information of the payment digital wallet ID of the target user at the third-party payment acquirer, establish the association relationship between the first encrypted information and the second encrypted information at the third-party payment acquirer, and add the association relationship to the set association relationship list of the third-party payment acquirer. In this way, an association relationship is established between the first encrypted information of the user digital wallet ID and the second encrypted information of the payment digital wallet ID of the same target user, so that even if the third-party payment acquirer does not know the user digital wallet ID of the target user, it can still determine the identity of the target user based on the first encrypted information of the user digital wallet ID, so that risk assessment can be performed at the third-party payment acquirer. This method can not only enable the third-party payment acquirer to determine the identity of the user without knowing the user digital wallet ID, but also protect the privacy of the user.

[0131] In some embodiments, the target user may be any user who has opened a digital wallet at the target bank, and the target user pays for the order through the digital wallet, and the third-party payment acquirer is the payment acquirer for the order. The target bank may be any bank. The third-party payment acquirer may pre-negotiate the bank private key and the payment private key with one or more target banks. The bank private key is the private key of the target bank, and the payment private key is the private key of the third-party payment acquirer. Each target bank may have a fixed and unique bank private key, and each third-party payment acquirer may also have a fixed and unique payment private key.

[0132] The payment information may be information generated when the target user makes a payment during a transaction at a merchant, including but not limited to the first encrypted information of the user digital wallet ID of the target user.

[0133] In some embodiments, the first encrypted information may be information obtained by encrypting the user digital wallet ID of the target user on the user side by using the bank private key and the payment private key of the third-party payment acquirer.

[0134] In some embodiments, the target bank may transmit the first encrypted information separately to the third-party payment acquirer so that the third-party payment acquirer can establish a connection between the user digital wallet ID and the payment digital wallet ID of the same target user based on the first encrypted information. Such connection can be established through the corresponding association relationship between the first encrypted information of the user digital wallet ID and the payment digital wallet ID.

[0135] After the third-party payment acquirer obtains the first encrypted information carried in the payment information from the target bank, it can match the first encrypted information with a pre-established set association relationship list. The set association relationship list can be determined based on the privacy protection method of the user digital wallet mentioned above, and the specific details can be found in the description of the privacy protection method of the user digital wallet above, which will not be repeated here.

[0136] After matching the corresponding second encrypted information, the payment digital wallet ID of the target user corresponding to the payment information can be determined based on the second encrypted information.

[0137] The payment digital wallet ID of the target user can be allocated to the target user by the third-party payment acquirer, and the payment digital wallet ID is unique to the third-party payment acquirer.

[0138] The second encrypted information is obtained by the third-party payment acquirer encrypting the payment digital wallet ID of the target user based on the bank private key and payment private key of the target bank. Therefore, after matching the second encrypted information, the payment digital wallet ID of the target user can be determined, and thus the identity of the target user can be determined.

[0139] In this way, the user identity of the target user can be confirmed based on the first encrypted information of the target user obtained from the target bank without knowing the user digital wallet ID assigned to the target user by the target bank, thereby protecting the privacy of the target user and ensuring the security of the data.

[0140] In the disclosed embodiment, for the same bank and the same third-party acquiring payment terminal, the agreed bank private key and payment private key are fixed and unique, which can ensure that the encrypted result of the user digital wallet ID is unique. Because the target bank has the user digital wallet ID of the C-end user, and the third-party acquiring payment terminal has the payment digital wallet ID of the B-end user, the bank private key and payment private key are used to encrypt the user digital wallet ID at the bank end, and the payment digital wallet ID is encrypted at the third-party acquiring payment terminal, which can ensure that the user digital wallet ID and the payment digital wallet ID cannot be unilaterally cracked.

[0141] In one embodiment of the present disclosure, the method further includes:

[0142] Count all payment information with the same payment digital wallet ID to obtain statistical results;

[0143] The transaction risk is determined based on the statistical results.

[0144] In this optional implementation, in order to determine the risks in the transaction, the third-party payment acquirer can count all payment information based on the target user. At the third-party payment acquirer, the payment wallet digital ID can be used as the identity information of the same target user, so that all payment information generated by the same payment wallet digital ID can be counted, and after analyzing and processing the statistical results, the possible transaction risks can be determined. For example, it can be determined whether a large transaction involves risks such as money laundering.

[0145] Figure 4 A flowchart showing a method for confirming a user identity according to another embodiment of the present disclosure is shown as follows: Figure 4 As shown, the method for confirming the user identity includes the following steps:

[0146] In step S401, settlement information is obtained; the settlement information includes second encrypted information of the payment digital wallet ID of the target user;

[0147] In step S402, the second encrypted information is matched with a set association relationship list to obtain first encrypted information matching the second encrypted information; the set association relationship list is established based on the above-mentioned privacy protection method for the digital payment wallet;

[0148] In step S403, the user digital wallet ID of the target user is determined based on the first encrypted information;

[0149] In step S404, the identity of the target user is determined based on the user digital wallet ID.

[0150] As mentioned above, each bank will assign a unique user digital wallet ID to users who open digital currency. Due to sensitive data and data security considerations, banks are reluctant to pass digital wallet IDs to third-party payment acquirers. In order to protect user privacy, third-party payment acquirers are also not suitable for passing the payment digital wallet ID assigned to users to other institutions, such as banks. However, for third-party payment acquirers, it is very important to obtain the user's user digital wallet ID along with the payment order to analyze and identify transaction risks. Similarly, it is necessary for the target bank to conduct risk analysis based on the target user's payment digital wallet ID. If the user's digital wallet ID cannot be obtained, it is not conducive to determining risks, such as determining whether large transactions involve money laundering risks.

[0151] To this end, it is necessary to provide a solution that can facilitate banks in risk assessment and protect user privacy.

[0152] To this end, the target bank negotiates with the third-party payment acquirer in advance on the bank private key and the payment private key, where the bank private key is the private key of the target bank, and the payment private key is the private key of the third-party payment acquirer. When the third-party payment acquirer needs to transmit the payment digital wallet ID of the target user, it can use the bank private key negotiated in advance with the target bank and the payment private key of the third-party payment acquirer to encrypt the payment digital wallet ID to obtain the second encrypted information, which can be provided to the target bank when needed, for example, it can be sent to the target bank by the third-party payment acquirer alone, or carried in other data and transmitted to the target bank. After the target bank obtains the second encrypted information, it can determine the third-party payment acquirer corresponding to the second encrypted information, that is, determine which third-party payment acquirer encrypted the second encrypted information, and then obtain the bank private key pre-negotiated with the third-party payment acquirer and the payment private key set by the target bank for the third-party payment acquirer, and use the bank private key and the payment private key to encrypt the user digital wallet ID of the target user, obtain the first encrypted information of the user digital wallet ID of the target user at the third-party payment acquirer, establish the association relationship between the first encrypted information and the second encrypted information in the target bank, and add the association relationship to the set association relationship list of the target bank. In this way, an association relationship is established between the first encrypted information of the user digital wallet ID of the same target user and the second encrypted information of the payment digital wallet ID, so that even if the target bank does not know the payment digital wallet ID of the target user, it can still determine the identity of the target user based on the second encrypted information of the payment digital wallet ID, so that it can perform risk assessment at the target bank. This method can enable the target bank to determine the identity of the user without knowing the payment digital wallet ID, thereby protecting the privacy of the user.

[0153] In some embodiments, the target user may be any user who has opened a digital wallet at the target bank, and the target user has made order payments through the digital wallet, and the third-party payment acquirer is the payment acquirer for the order. The target bank may be any bank. The target bank may pre-negotiate the bank private key and the payment private key with one or more third-party payment acquirers. The bank private key is the private key of the target bank, and the payment private key is the private key of the third-party payment acquirer. Each target bank may have a fixed and unique bank private key for the same third-party payment acquirer, and each third-party payment acquirer may also have a fixed and unique payment private key for the same target bank. Of course, it is understandable that the target bank may only set one bank private key for all third-party payment acquirers, and the third-party payment acquirer may only set one payment private key for all target banks.

[0154] In some embodiments, the second encrypted information may be information obtained by encrypting the payment digital wallet ID of the target user at the third-party payment acquirer using the bank private key and the payment private key.

[0155] In some embodiments, the third-party payment acquirer can transmit the second encrypted information separately to the target bank, so that the target bank can establish a connection between the user digital wallet ID and the payment digital wallet ID of the same target user based on the second encrypted information. This connection can be established through the corresponding association relationship between the first encrypted information of the user digital wallet ID and the payment digital wallet ID.

[0156] When the third-party payment acquirer sends settlement information to the target bank, the second encrypted information of the payment digital wallet ID of the target user can be carried in the settlement information. After the target bank obtains the second encrypted information from the third-party payment acquirer, it can match the second encrypted information with the pre-established set association relationship list, which can be determined based on the privacy protection method of the payment digital wallet, and the specific details can be found in the description of the privacy protection method of the payment digital wallet above, which will not be repeated here.

[0157] After matching the corresponding first encrypted information, the user digital wallet ID of the target user corresponding to the payment information can be determined based on the first encrypted information.

[0158] The user digital wallet ID of the target user may be assigned to the target user by the target bank, and the user digital wallet ID is unique.

[0159] Since the first encrypted information is obtained by the target bank encrypting the user digital wallet ID of the target user based on the bank private key and payment private key of the target bank, after matching the first encrypted information, the user digital wallet ID of the target user can be determined, and thus the identity of the target user can be determined.

[0160] In this way, the user identity of the target user can be confirmed based on the second encrypted information of the target user obtained from the third-party acquiring payment terminal without knowing the payment digital wallet ID assigned to the target user by the third-party acquiring payment terminal, thereby protecting the privacy of the target user and ensuring the security of the data.

[0161] In the disclosed embodiment, for the same bank and the same third-party acquiring payment terminal, the agreed bank private key and payment private key are fixed and unique, which can ensure that the encrypted result of the user digital wallet ID is unique. Because the target bank has the user digital wallet ID of the C-end user, and the third-party acquiring payment terminal has the payment digital wallet ID of the B-end user, the bank private key and payment private key are used to encrypt the user digital wallet ID at the bank end, and the payment digital wallet ID is encrypted at the third-party acquiring payment terminal, which can ensure that the user digital wallet ID and the payment digital wallet ID cannot be unilaterally cracked.

[0162] The following are embodiments of the apparatus of the present disclosure, which can be used to execute embodiments of the method of the present disclosure.

[0163] Figure 5 The structure block diagram of the privacy protection device of the user digital wallet according to one embodiment of the present disclosure is shown. The device can be implemented as part or all of the electronic device through software, hardware or a combination of both. Figure 5 As shown, the privacy protection of the user's digital wallet includes:

[0164] The first acquisition module 501 is configured to acquire first encrypted information of the user digital wallet ID of the target user at the user terminal;

[0165] A first determination module 502 is configured to determine a target bank corresponding to the first encrypted information, and obtain a bank private key pre-agreed with the target bank and a payment private key of a third-party payment acquirer;

[0166] The second acquisition module 503 is configured to encrypt the payment digital wallet ID of the target user at the third-party payment acquirer by using the bank private key and the payment private key, and obtain the second encrypted information of the payment digital wallet ID of the target user at the third-party payment acquirer;

[0167] The first establishing module 504 is configured to establish an association relationship between the first encrypted information and the second encrypted information, and add the association relationship to a set association relationship list of the third-party payment acquirer.

[0168] As mentioned above, each bank will assign a unique user digital wallet ID to users who open digital currency. Due to sensitive data and data security considerations, banks are reluctant to pass digital wallet IDs to third-party payment acquirers. In order to protect user privacy, third-party payment acquirers are also not suitable for passing the payment digital wallet ID assigned to users to other institutions, such as banks. However, for third-party payment acquirers, it is very important to obtain the user's user digital wallet ID along with the payment order to analyze and identify transaction risks. Similarly, it is necessary for the target bank to conduct risk analysis based on the target user's payment digital wallet ID. If the user's digital wallet ID cannot be obtained, it is not conducive to determining risks, such as determining whether large transactions involve money laundering risks.

[0169] To this end, a solution is needed that can obtain the user identity along with the payment order without reducing data security.

[0170] To this end, the third-party payment acquirer negotiates with the target bank in advance on the bank private key and the payment private key, where the bank private key is the private key of the target bank, and the payment private key is the private key of the third-party payment acquirer. When the target bank needs to transmit the user digital wallet ID of the target user, it can use the bank private key negotiated in advance with the third-party payment acquirer and the payment private key of the third-party payment acquirer to encrypt the user digital wallet ID to obtain the first encrypted information, which can be provided to the third-party payment acquirer when needed, for example, it can be sent to the third-party payment acquirer by the target bank alone, or transmitted to the third-party payment acquirer along with the payment order of the target user. After the third-party payment acquirer obtains the first encrypted information, it can determine the target bank corresponding to the first encrypted information, that is, determine which bank encrypted the first encrypted information, and then obtain the bank private key pre-negotiated with the target bank and the payment private key set by the third-party payment acquirer for the target bank, and use the bank private key and the payment private key to encrypt the payment digital wallet ID of the target user, obtain the second encrypted information of the payment digital wallet ID of the target user at the third-party payment acquirer, establish the association relationship between the first encrypted information and the second encrypted information at the third-party payment acquirer, and add the association relationship to the set association relationship list of the third-party payment acquirer. In this way, an association relationship is established between the first encrypted information of the user digital wallet ID and the second encrypted information of the payment digital wallet ID of the same target user, so that even if the third-party payment acquirer does not know the user digital wallet ID of the target user, it can still determine the identity of the target user based on the first encrypted information of the user digital wallet ID, so that risk assessment can be performed at the third-party payment acquirer. This method can not only enable the third-party payment acquirer to determine the identity of the user without knowing the user digital wallet ID, but also protect the privacy of the user.

[0171] In some embodiments, the target user may be any user who has opened a digital wallet at the target bank, and the target user pays for the order through the digital wallet, and the third-party payment acquirer is the payment acquirer for the order. The target bank may be any bank. The third-party payment acquirer may pre-negotiate the bank private key and the payment private key with one or more target banks. The bank private key is the private key of the target bank, and the payment private key is the private key of the third-party payment acquirer. Each target bank may have a fixed and unique bank private key, and each third-party payment acquirer may also have a fixed and unique payment private key.

[0172] In some embodiments, different target banks correspond to different bank private keys, and the third-party payment acquirer also corresponds to different payment private keys.

[0173] In other embodiments, the same target bank may correspond to the same or different bank private keys for different third-party payment acquirers, and the same third-party payment acquirer may correspond to the same or different bank private keys for different target banks. The payment private key of the third-party payment acquirer may be provided in advance to the corresponding target bank, and the bank private key of the target bank may be provided in advance to the corresponding third-party payment acquirer.

[0174] In some embodiments, the first encrypted information may be information obtained by encrypting the user digital wallet ID of the target user on the user side by using the bank private key and the payment private key of the third-party payment acquirer.

[0175] In some embodiments, the target bank may transmit the first encrypted information separately to the third-party payment acquirer so that the third-party payment acquirer can establish a connection between the user digital wallet ID and the payment digital wallet ID of the same target user based on the first encrypted information. Such connection can be established through the corresponding association relationship between the first encrypted information of the user digital wallet ID and the payment digital wallet ID.

[0176] After the third-party payment acquirer obtains the first encrypted information from the target bank, it can determine the target bank corresponding to the first encrypted information. In some embodiments, the target bank can transmit the identification of the target bank together with the first encrypted information to the third-party payment acquirer, so that the target bank corresponding to the first encrypted information can be determined.

[0177] After determining the target bank, the bank private key and payment private key that the third-party payment acquirer has pre-negotiated with the target bank can be determined, and the payment digital wallet ID of the target user can be encrypte using the bank private key and payment private key to obtain the second encrypted information of the target user.

[0178] The payment digital wallet ID of the target user can be allocated to the target user by the third-party payment acquirer, and the payment digital wallet ID is unique to the third-party payment acquirer.

[0179] The third-party payment acquirer can establish an association relationship between the first encrypted information and the second encrypted information corresponding to the target user, and add the association relationship to the set association relationship list of the third-party payment acquirer. In the subsequent transaction process, the target bank can encrypt the user digital wallet ID of the target user into the first encrypted information, and transmit it to the third-party payment acquirer along with the payment order. After the third-party payment acquirer obtains the first encrypted information, it can match the first encrypted information with the set association relationship list to obtain the second encrypted information that matches the first encrypted information, thereby determining the payment wallet ID of the target user corresponding to the payment order. In this way, even if the third-party payment acquirer is not sure of the user digital wallet ID of the target user of the payment order, it can still uniquely determine the identity of the target user through the payment digital wallet ID, and can also conduct risk assessment for the target user or the merchant involved in the payment order of the target user.

[0180] In one embodiment of the present disclosure, the privacy protection method of the user's digital wallet is suitable for execution at a third-party payment acquiring end.

[0181] In the disclosed embodiment, for the same bank and the same third-party acquiring payment terminal, the agreed bank private key and payment private key are fixed and unique, which can ensure that the encrypted result of the user digital wallet ID is unique. Because the target bank has the user digital wallet ID of the C-end user, and the third-party acquiring payment terminal has the payment digital wallet ID of the B-end user, the bank private key and payment private key are used to encrypt the user digital wallet ID at the bank end, and the payment digital wallet ID is encrypted at the third-party acquiring payment terminal, which can ensure that the user digital wallet ID and the payment digital wallet ID cannot be unilaterally cracked.

[0182] Figure 6 The structure block diagram of the privacy protection device of the digital wallet for payment according to one embodiment of the present disclosure is shown. The device can be implemented as part or all of the electronic device through software, hardware or a combination of both. Figure 6 As shown, the privacy protection of the payment digital wallet includes:

[0183] The third acquisition module 601 is configured to obtain the second encrypted information of the payment digital wallet ID of the target user at the third-party payment acquirer;

[0184] The second determination module 602 is configured to determine the third-party payment acquirer corresponding to the second encrypted information, and obtain a bank private key and a payment private key of the third-party payment acquirer pre-agreed with the third-party payment acquirer;

[0185] The fourth acquisition module 603 is configured to encrypt the user digital wallet ID of the target user by using the bank private key and the payment private key to obtain the first encrypted information of the user digital wallet ID of the target user at the user end;

[0186] The second establishing module 604 is configured to establish an association relationship between the first encrypted information and the second encrypted information, and add the association relationship to the set association relationship list of the target bank.

[0187] As mentioned above, each bank will assign a unique user digital wallet ID to users who open digital currency. Due to sensitive data and data security considerations, banks are reluctant to pass digital wallet IDs to third-party payment acquirers. In order to protect user privacy, third-party payment acquirers are also not suitable for passing the payment digital wallet ID assigned to users to other institutions, such as banks. However, for third-party payment acquirers, it is very important to obtain the user's user digital wallet ID along with the payment order to analyze and identify transaction risks. Similarly, it is necessary for the target bank to conduct risk analysis based on the target user's payment digital wallet ID. If the user's digital wallet ID cannot be obtained, it is not conducive to determining risks, such as determining whether large transactions involve money laundering risks.

[0188] To this end, it is necessary to provide a solution that can facilitate banks in risk assessment and protect user privacy.

[0189] To this end, the target bank negotiates with the third-party payment acquirer in advance on the bank private key and the payment private key, where the bank private key is the private key of the target bank, and the payment private key is the private key of the third-party payment acquirer. When the third-party payment acquirer needs to transmit the payment digital wallet ID of the target user, it can use the bank private key negotiated in advance with the target bank and the payment private key of the third-party payment acquirer to encrypt the payment digital wallet ID to obtain the second encrypted information, which can be provided to the target bank when needed, for example, it can be sent to the target bank by the third-party payment acquirer alone, or carried in other data and transmitted to the target bank. After the target bank obtains the second encrypted information, it can determine the third-party payment acquirer corresponding to the second encrypted information, that is, determine which third-party payment acquirer encrypted the second encrypted information, and then obtain the bank private key pre-negotiated with the third-party payment acquirer and the payment private key set by the target bank for the third-party payment acquirer, and use the bank private key and the payment private key to encrypt the user digital wallet ID of the target user, obtain the first encrypted information of the user digital wallet ID of the target user at the third-party payment acquirer, establish the association relationship between the first encrypted information and the second encrypted information in the target bank, and add the association relationship to the set association relationship list of the target bank. In this way, an association relationship is established between the first encrypted information of the user digital wallet ID of the same target user and the second encrypted information of the payment digital wallet ID, so that even if the target bank does not know the payment digital wallet ID of the target user, it can still determine the identity of the target user based on the second encrypted information of the payment digital wallet ID, so that it can perform risk assessment at the target bank. This method can enable the target bank to determine the identity of the user without knowing the payment digital wallet ID, thereby protecting the privacy of the user.

[0190] In some embodiments, the target user may be any user who has opened a digital wallet at the target bank, and the target user has made order payments through the digital wallet, and the third-party payment acquirer is the payment acquirer for the order. The target bank may be any bank. The target bank may pre-negotiate the bank private key and the payment private key with one or more third-party payment acquirers. The bank private key is the private key of the target bank, and the payment private key is the private key of the third-party payment acquirer. Each target bank may have a fixed and unique bank private key for the same third-party payment acquirer, and each third-party payment acquirer may also have a fixed and unique payment private key for the same target bank. Of course, it is understandable that the target bank may only set one bank private key for all third-party payment acquirers, and the third-party payment acquirer may only set one payment private key for all target banks.

[0191] In some embodiments, different target banks correspond to different bank private keys, and the third-party payment acquirer also corresponds to different payment private keys.

[0192] In other embodiments, the same target bank may correspond to the same or different bank private keys for different third-party payment acquirers, and the same third-party payment acquirer may correspond to the same or different bank private keys for different target banks. The payment private key of the third-party payment acquirer may be provided in advance to the corresponding target bank, and the bank private key of the target bank may be provided in advance to the corresponding third-party payment acquirer.

[0193] In some embodiments, the second encrypted information may be information obtained by encrypting the payment digital wallet ID of the target user at the third-party payment acquirer using the bank private key and the payment private key.

[0194] In some embodiments, the third-party payment acquirer can transmit the second encrypted information separately to the target bank, so that the target bank can establish a connection between the user digital wallet ID and the payment digital wallet ID of the same target user based on the second encrypted information. This connection can be established through the corresponding association relationship between the first encrypted information of the user digital wallet ID and the payment digital wallet ID.

[0195] After the target bank obtains the second encrypted information from the third-party payment acquirer, it can determine the third-party payment acquirer corresponding to the second encrypted information. In some embodiments, the third-party payment acquirer can transmit the identification of the third-party payment acquirer together with the second encrypted information to the target bank, so as to determine the third-party payment acquirer corresponding to the second encrypted information.

[0196] After determining the third-party payment acquirer, the bank private key and payment private key that the target bank has pre-negotiated with the third-party payment acquirer can be determined, and the user digital wallet ID of the target user can be encrypted using the bank private key and payment private key to obtain the first encrypted information of the target user.

[0197] The user digital wallet ID of the target user may be allocated to the target user by the target bank, and the user digital wallet ID is unique in the target bank.

[0198] The target bank can establish an association relationship between the first encrypted information and the second encrypted information corresponding to the target user, and add the association relationship to the set association relationship list of the target bank. In the subsequent transaction process, the target bank can encrypt the user digital wallet ID of the target user into the first encrypted information and transmit it to the target bank along with other data. After the target bank obtains the second encrypted information, it can match the second encrypted information with the set association relationship list to obtain the first encrypted information that matches the second encrypted information, thereby determining the user digital wallet ID of the target user corresponding to the other data. In this way, even if the target bank is not sure of the payment digital wallet ID of the target user corresponding to the other data, it can still uniquely determine the identity of the target user through the user digital wallet ID, and can also conduct risk assessment for the target user or the merchant involved in the target user.

[0199] In one embodiment of the present disclosure, the privacy protection method of the payment digital wallet is suitable for execution at the target bank end.

[0200] In the disclosed embodiment, for the same bank and the same third-party acquiring payment terminal, the agreed bank private key and payment private key are fixed and unique, which can ensure that the encrypted result of the user digital wallet ID is unique. Because the target bank has the user digital wallet ID of the C-end user, and the third-party acquiring payment terminal has the payment digital wallet ID of the B-end user, the bank private key and payment private key are used to encrypt the user digital wallet ID at the bank end, and the payment digital wallet ID is encrypted at the third-party acquiring payment terminal, which can ensure that the user digital wallet ID and the payment digital wallet ID cannot be unilaterally cracked.

[0201] Figure 7 The structure block diagram of a user identity confirmation device according to an embodiment of the present disclosure is shown. The device can be implemented as part or all of an electronic device through software, hardware, or a combination of both. Figure 7 As shown, the user identity confirmation device includes:

[0202] The fifth acquisition module 701 is configured to acquire payment information; the payment information includes first encrypted information of the user digital wallet ID of the target user;

[0203] A sixth acquisition module 702 is configured to match the first encrypted information with a set association relationship list to obtain second encrypted information matching the first encrypted information; the set association relationship list is established based on the privacy protection device of the user digital wallet;

[0204] A third determination module 703 is configured to determine the payment digital wallet ID of the target user corresponding to the payment information based on the second encrypted information;

[0205] The fourth determination module 704 is configured to determine the identity of the target user based on the payment digital wallet ID.

[0206] As mentioned above, each bank will assign a unique user digital wallet ID to users who open digital currency. Due to sensitive data and data security considerations, banks are reluctant to pass digital wallet IDs to third-party payment acquirers. In order to protect user privacy, third-party payment acquirers are also not suitable for passing the payment digital wallet ID assigned to users to other institutions, such as banks. However, for third-party payment acquirers, it is very important to obtain the user's user digital wallet ID along with the payment order to analyze and identify transaction risks. Similarly, it is necessary for the target bank to conduct risk analysis based on the target user's payment digital wallet ID. If the user's digital wallet ID cannot be obtained, it is not conducive to determining risks, such as determining whether large transactions involve money laundering risks.

[0207] To this end, a solution is needed that can confirm the user's identity without reducing data security.

[0208] To this end, the third-party payment acquirer negotiates with the target bank in advance on the bank private key and the payment private key, where the bank private key is the private key of the target bank, and the payment private key is the private key of the third-party payment acquirer. When the target bank needs to transmit the user digital wallet ID of the target user, it can use the bank private key negotiated in advance with the third-party payment acquirer and the payment private key of the third-party payment acquirer to encrypt the user digital wallet ID to obtain the first encrypted information, which can be provided to the third-party payment acquirer when needed, for example, it can be sent to the third-party payment acquirer by the target bank alone, or transmitted to the third-party payment acquirer along with the payment order of the target user. After the third-party payment acquirer obtains the first encrypted information, it can determine the target bank corresponding to the first encrypted information, that is, determine which bank encrypted the first encrypted information, and then obtain the bank private key pre-negotiated with the target bank and the payment private key set by the third-party payment acquirer for the target bank, and use the bank private key and the payment private key to encrypt the payment digital wallet ID of the target user, obtain the second encrypted information of the payment digital wallet ID of the target user at the third-party payment acquirer, establish the association relationship between the first encrypted information and the second encrypted information at the third-party payment acquirer, and add the association relationship to the set association relationship list of the third-party payment acquirer. In this way, an association relationship is established between the first encrypted information of the user digital wallet ID and the second encrypted information of the payment digital wallet ID of the same target user, so that even if the third-party payment acquirer does not know the user digital wallet ID of the target user, it can still determine the identity of the target user based on the first encrypted information of the user digital wallet ID, so that risk assessment can be performed at the third-party payment acquirer. This method can not only enable the third-party payment acquirer to determine the identity of the user without knowing the user digital wallet ID, but also protect the privacy of the user.

[0209] In some embodiments, the target user may be any user who has opened a digital wallet at the target bank, and the target user pays for the order through the digital wallet, and the third-party payment acquirer is the payment acquirer for the order. The target bank may be any bank. The third-party payment acquirer may pre-negotiate the bank private key and the payment private key with one or more target banks. The bank private key is the private key of the target bank, and the payment private key is the private key of the third-party payment acquirer. Each target bank may have a fixed and unique bank private key, and each third-party payment acquirer may also have a fixed and unique payment private key.

[0210] The payment information may be information generated when the target user makes a payment during a transaction at a merchant, including but not limited to the first encrypted information of the user digital wallet ID of the target user.

[0211] In some embodiments, the first encrypted information may be information obtained by encrypting the user digital wallet ID of the target user on the user side by using the bank private key and the payment private key of the third-party payment acquirer.

[0212] In some embodiments, the target bank may transmit the first encrypted information separately to the third-party payment acquirer so that the third-party payment acquirer can establish a connection between the user digital wallet ID and the payment digital wallet ID of the same target user based on the first encrypted information. Such connection can be established through the corresponding association relationship between the first encrypted information of the user digital wallet ID and the payment digital wallet ID.

[0213] After the third-party payment acquirer obtains the first encrypted information carried in the payment information from the target bank, it can match the first encrypted information with a pre-established set association relationship list. The set association relationship list can be determined based on the privacy protection method of the user digital wallet mentioned above, and the specific details can be found in the description of the privacy protection method of the user digital wallet above, which will not be repeated here.

[0214] After matching the corresponding second encrypted information, the payment digital wallet ID of the target user corresponding to the payment information can be determined based on the second encrypted information.

[0215] The payment digital wallet ID of the target user can be allocated to the target user by the third-party payment acquirer, and the payment digital wallet ID is unique to the third-party payment acquirer.

[0216] The second encrypted information is obtained by the third-party payment acquirer encrypting the payment digital wallet ID of the target user based on the bank private key and payment private key of the target bank. Therefore, after matching the second encrypted information, the payment digital wallet ID of the target user can be determined, and thus the identity of the target user can be determined.

[0217] In this way, the user identity of the target user can be confirmed based on the first encrypted information of the target user obtained from the target bank without knowing the user digital wallet ID assigned to the target user by the target bank, thereby protecting the privacy of the target user and ensuring the security of the data.

[0218] In the disclosed embodiment, for the same bank and the same third-party acquiring payment terminal, the agreed bank private key and payment private key are fixed and unique, which can ensure that the encrypted result of the user digital wallet ID is unique. Because the target bank has the user digital wallet ID of the C-end user, and the third-party acquiring payment terminal has the payment digital wallet ID of the B-end user, the bank private key and payment private key are used to encrypt the user digital wallet ID at the bank end, and the payment digital wallet ID is encrypted at the third-party acquiring payment terminal, which can ensure that the user digital wallet ID and the payment digital wallet ID cannot be unilaterally cracked.

[0219] Figure 8 The following is a structural block diagram of a user identity confirmation device according to another embodiment of the present disclosure. The device can be implemented as part or all of an electronic device through software, hardware, or a combination of both. Figure 8 As shown, the user identity confirmation device includes:

[0220] The seventh acquisition module 801 is configured to acquire settlement information; the settlement information includes the second encrypted information of the payment digital wallet ID of the target user;

[0221] An eighth acquisition module 802 is configured to match the second encrypted information with a set association relationship list to obtain first encrypted information matching the second encrypted information; the set association relationship list is established based on the privacy protection device of the payment digital wallet;

[0222] A fifth determination module 803 is configured to determine a user digital wallet ID of the target user based on the first encrypted information;

[0223] The sixth determination module 804 is configured to determine the identity of the target user based on the user digital wallet ID.

[0224] As mentioned above, each bank will assign a unique user digital wallet ID to users who open digital currency. Due to sensitive data and data security considerations, banks are reluctant to pass digital wallet IDs to third-party payment acquirers. In order to protect user privacy, third-party payment acquirers are also not suitable for passing the payment digital wallet ID assigned to users to other institutions, such as banks. However, for third-party payment acquirers, it is very important to obtain the user's user digital wallet ID along with the payment order to analyze and identify transaction risks. Similarly, it is necessary for the target bank to conduct risk analysis based on the target user's payment digital wallet ID. If the user's digital wallet ID cannot be obtained, it is not conducive to determining risks, such as determining whether large transactions involve money laundering risks.

[0225] To this end, it is necessary to provide a solution that can facilitate banks in risk assessment and protect user privacy.

[0226] To this end, the target bank negotiates with the third-party payment acquirer in advance on the bank private key and the payment private key, where the bank private key is the private key of the target bank, and the payment private key is the private key of the third-party payment acquirer. When the third-party payment acquirer needs to transmit the payment digital wallet ID of the target user, it can use the bank private key negotiated in advance with the target bank and the payment private key of the third-party payment acquirer to encrypt the payment digital wallet ID to obtain the second encrypted information, which can be provided to the target bank when needed, for example, it can be sent to the target bank by the third-party payment acquirer alone, or carried in other data and transmitted to the target bank. After the target bank obtains the second encrypted information, it can determine the third-party payment acquirer corresponding to the second encrypted information, that is, determine which third-party payment acquirer encrypted the second encrypted information, and then obtain the bank private key pre-negotiated with the third-party payment acquirer and the payment private key set by the target bank for the third-party payment acquirer, and use the bank private key and the payment private key to encrypt the user digital wallet ID of the target user, obtain the first encrypted information of the user digital wallet ID of the target user at the third-party payment acquirer, establish the association relationship between the first encrypted information and the second encrypted information in the target bank, and add the association relationship to the set association relationship list of the target bank. In this way, an association relationship is established between the first encrypted information of the user digital wallet ID of the same target user and the second encrypted information of the payment digital wallet ID, so that even if the target bank does not know the payment digital wallet ID of the target user, it can still determine the identity of the target user based on the second encrypted information of the payment digital wallet ID, so that it can perform risk assessment at the target bank. This method can enable the target bank to determine the identity of the user without knowing the payment digital wallet ID, thereby protecting the privacy of the user.

[0227] In some embodiments, the target user may be any user who has opened a digital wallet at the target bank, and the target user has made order payments through the digital wallet, and the third-party payment acquirer is the payment acquirer for the order. The target bank may be any bank. The target bank may pre-negotiate the bank private key and the payment private key with one or more third-party payment acquirers. The bank private key is the private key of the target bank, and the payment private key is the private key of the third-party payment acquirer. Each target bank may have a fixed and unique bank private key for the same third-party payment acquirer, and each third-party payment acquirer may also have a fixed and unique payment private key for the same target bank. Of course, it is understandable that the target bank may only set one bank private key for all third-party payment acquirers, and the third-party payment acquirer may only set one payment private key for all target banks.

[0228] In some embodiments, the second encrypted information may be information obtained by encrypting the payment digital wallet ID of the target user at the third-party payment acquirer using the bank private key and the payment private key.

[0229] In some embodiments, the third-party payment acquirer can transmit the second encrypted information separately to the target bank, so that the target bank can establish a connection between the user digital wallet ID and the payment digital wallet ID of the same target user based on the second encrypted information. This connection can be established through the corresponding association relationship between the first encrypted information of the user digital wallet ID and the payment digital wallet ID.

[0230] When the third-party payment acquirer sends settlement information to the target bank, the second encrypted information of the payment digital wallet ID of the target user can be carried in the settlement information. After the target bank obtains the second encrypted information from the third-party payment acquirer, it can match the second encrypted information with the pre-established set association relationship list, which can be determined based on the privacy protection method of the payment digital wallet, and the specific details can be found in the description of the privacy protection method of the payment digital wallet above, which will not be repeated here.

[0231] After matching the corresponding first encrypted information, the user digital wallet ID of the target user corresponding to the payment information can be determined based on the first encrypted information.

[0232] The user digital wallet ID of the target user may be assigned to the target user by the target bank, and the user digital wallet ID is unique.

[0233] Since the first encrypted information is obtained by the target bank encrypting the user digital wallet ID of the target user based on the bank private key and payment private key of the target bank, after matching the first encrypted information, the user digital wallet ID of the target user can be determined, and thus the identity of the target user can be determined.

[0234] In this way, the user identity of the target user can be confirmed based on the second encrypted information of the target user obtained from the third-party acquiring payment terminal without knowing the payment digital wallet ID assigned to the target user by the third-party acquiring payment terminal, thereby protecting the privacy of the target user and ensuring the security of the data.

[0235] In the disclosed embodiment, for the same bank and the same third-party acquiring payment terminal, the agreed bank private key and payment private key are fixed and unique, which can ensure that the encrypted result of the user digital wallet ID is unique. Because the target bank has the user digital wallet ID of the C-end user, and the third-party acquiring payment terminal has the payment digital wallet ID of the B-end user, the bank private key and payment private key are used to encrypt the user digital wallet ID at the bank end, and the payment digital wallet ID is encrypted at the third-party acquiring payment terminal, which can ensure that the user digital wallet ID and the payment digital wallet ID cannot be unilaterally cracked.

[0236] Fig. 9 It is a structural diagram of a computer system suitable for implementing a privacy protection method for a user digital wallet, a privacy protection method for a payment digital wallet and / or a method for confirming a user identity according to an embodiment of the present disclosure.

[0237] like Fig. 9 As shown, the computer system 900 includes a processing unit 901, which can perform various processes in the above-mentioned embodiments according to a program stored in a read-only memory (ROM) 902 or a program loaded from a storage part 908 into a random access memory (RAM) 903. In the RAM 903, various programs and data required for the operation of the computer system 900 are also stored. The processing unit 901, the ROM 902, and the RAM 903 are connected to each other via a bus 904. An input / output (I / O) interface 905 is also connected to the bus 904.

[0238] The following components are connected to the I / O interface 905: an input section 906 including a keyboard, a mouse, etc.; an output section 907 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker; a storage section 908 including a hard disk, etc.; and a communication section 909 including a network interface card such as a LAN card, a modem, etc. The communication section 909 performs communication processing via a network such as the Internet. A drive 910 is also connected to the I / O interface 905 as needed. A removable medium 911, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 910 as needed, so that a computer program read therefrom is installed into the storage section 908 as needed. Among them, the processing unit 901 can be implemented as a processing unit such as a CPU, a GPU, a TPU, an FPGA, an NPU, etc.

[0239] In particular, according to an embodiment of the present disclosure, the method described above can be implemented as a computer software program. For example, an embodiment of the present disclosure includes a computer program product, which includes a computer program tangibly contained on a readable medium thereof, and the computer program includes a program code for executing the data transmission method. In such an embodiment, the computer program can be downloaded and installed from a network through the communication part 909, and / or installed from a removable medium 911.

[0240] The embodiment of the present disclosure also discloses a computer program product, which includes a computer program / instruction, and when the computer program / instruction is executed by a processor, any of the above method steps is implemented.

[0241] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, functions and operations of the system, method and computer program product according to various embodiments of the present disclosure. In this regard, each square box in the road map or block diagram can represent a part of a module, program segment or code, and the part of the module, program segment or code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the square box can also occur in a different order from the order marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs the specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0242] The units or modules involved in the embodiments described in the present disclosure may be implemented by software or hardware. The units or modules described may also be set in a processor, and the names of these units or modules do not constitute limitations on the units or modules themselves in some cases.

[0243] As another aspect, the embodiments of the present disclosure further provide a computer-readable storage medium, which may be a computer-readable storage medium included in the device described in the above-mentioned embodiment; or a computer-readable storage medium that exists independently and is not assembled into the device. The computer-readable storage medium stores one or more programs, and the programs are used by one or more processors to execute the methods described in the embodiments of the present disclosure.

[0244] The above description is only a preferred embodiment of the present disclosure and an explanation of the technical principles used. Those skilled in the art should understand that the scope of the invention involved in the embodiments of the present disclosure is not limited to the technical solutions formed by a specific combination of the above technical features, but should also cover other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the inventive concept. For example, the above features are replaced with (but not limited to) technical features with similar functions disclosed in the embodiments of the present disclosure.

Claims

1. A privacy protection method for a user's digital wallet, comprising: Obtaining first encrypted information of the user digital wallet ID of the target user at the user end; The first encrypted information is obtained by encrypting the user's digital wallet ID in advance using the bank private key of the target bank and the payment private key of the third-party payment acquirer; Determine the target bank corresponding to the first encrypted information, and obtain the bank private key and the payment private key of the third-party payment acquirer pre-agreed with the target bank; After encrypting the payment digital wallet ID of the target user at the third-party payment acquiring terminal using the bank private key and the payment private key, second encrypted information of the payment digital wallet ID of the target user at the third-party payment acquiring terminal is obtained; An association relationship between the first encrypted information and the second encrypted information is established, and the association relationship is added to a set association relationship list of the third-party payment acquirer.

2. The method according to claim 1, wherein: For the same third-party payment acquirer, the same target bank corresponds to the same bank private key and payment private key, while different target banks correspond to different bank private keys and payment private keys.

3. The method according to claim 1 or 2, wherein: After encrypting the payment digital wallet ID of the target user at the third-party payment acquiring terminal using the bank private key and the payment private key, the second encrypted information of the payment digital wallet ID of the target user at the third-party payment acquiring terminal is obtained, including: The bank private key and the payment private key are mixed with the payment digital wallet ID, and then an MD5 operation is performed to obtain the second encrypted information.

4. The method according to claim 3, wherein: The bank private key and the payment private key are mixed with the payment digital wallet ID, and then an MD5 operation is performed to obtain the second encrypted information, including: After placing the bank private key and the payment private key at fixed positions of the payment digital wallet ID, an MD5 operation is performed to obtain the second encrypted information.

5. A privacy protection method for a digital payment wallet, comprising: Obtain the second encrypted information of the payment digital wallet ID of the target user at the third-party payment acquiring terminal; The second encrypted information is obtained by encrypting the payment digital wallet ID in advance using the bank private key of the target bank and the payment private key of the third-party payment acquirer; Determine the third-party payment acquirer corresponding to the second encrypted information, and obtain the bank private key and the payment private key of the third-party payment acquirer pre-agreed with the third-party payment acquirer; After encrypting the user digital wallet ID of the target user by using the bank private key and the payment private key, first encrypted information of the user digital wallet ID of the target user on the user side is obtained; An association relationship between the first encrypted information and the second encrypted information is established, and the association relationship is added to a set association relationship list of the target bank.

6. The method according to claim 5, wherein: For the same third-party payment acquirer, the same target bank corresponds to the same bank private key and payment private key, while for different third-party payment acquirers, the same target bank corresponds to different bank private keys and payment private keys.

7. The method according to claim 5 or 6, wherein: After encrypting the user digital wallet ID of the target user using the bank private key and the payment private key, the first encrypted information of the user digital wallet ID of the target user on the user side is obtained, including: The bank private key and the payment private key are mixed with the user digital wallet ID, and an MD5 operation is performed to obtain the first encrypted information of the user digital wallet ID of the target user at the user end.

8. The method according to claim 7, wherein: After the bank private key and the payment private key are mixed with the user digital wallet ID, an MD5 operation is performed to obtain the first encrypted information of the user digital wallet ID of the target user at the user end, including: After placing the bank private key and the payment private key at fixed positions of the user digital wallet ID, an MD5 operation is performed to obtain the first encrypted information.

9. A method for confirming a user identity, comprising: Obtain payment information; The payment information includes first encrypted information of a user digital wallet ID of the target user; Matching the first encrypted information with the set association relationship list to obtain second encrypted information matching the first encrypted information; The set association relationship list is established based on the method described in any one of claims 1 to 4; Determine the payment digital wallet ID of the target user corresponding to the payment information based on the second encrypted information; The identity of the target user is determined based on the payment digital wallet ID.

10. The method according to claim 9, wherein: The method further comprises: Counting all payment information with the same payment digital wallet ID to obtain statistical results; The transaction risk is determined based on the statistical results.

11. A method for confirming a user identity, comprising: Get settlement information; The settlement information includes second encrypted information of the payment digital wallet ID of the target user; Matching the second encrypted information with the set association relationship list to obtain first encrypted information matching the second encrypted information; The set association relationship list is established based on the method described in any one of claims 5 to 8; Determine the user digital wallet ID of the target user based on the first encrypted information; The identity of the target user is determined based on the user digital wallet ID.

12. A privacy protection device for a user's digital wallet, comprising: A first acquisition module is configured to acquire first encrypted information of a user digital wallet ID of a target user at a user terminal; A first determination module is configured to determine a target bank corresponding to the first encrypted information, and obtain a bank private key pre-agreed with the target bank and a payment private key of a third-party payment acquirer; The second acquisition module is configured to encrypt the payment digital wallet ID of the target user at the third-party payment acquirer by using the bank private key and the payment private key, and obtain the second encrypted information of the payment digital wallet ID of the target user at the third-party payment acquirer; The first establishing module is configured to establish an association relationship between the first encrypted information and the second encrypted information, and add the association relationship to a set association relationship list of the third-party payment acquiring terminal.

13. A privacy protection device for a digital payment wallet, comprising: A third acquisition module is configured to obtain second encrypted information of the payment digital wallet ID of the target user at the third-party payment acquiring terminal; A second determination module is configured to determine the third-party payment acquirer corresponding to the second encrypted information, and obtain a bank private key and a payment private key of the third-party payment acquirer pre-agreed with the third-party payment acquirer; A fourth acquisition module is configured to encrypt the user digital wallet ID of the target user by using the bank private key and the payment private key, and obtain first encrypted information of the user digital wallet ID of the target user at the user end; The second establishing module is configured to establish an association relationship between the first encrypted information and the second encrypted information, and add the association relationship to a set association relationship list of a target bank.

14. A device for confirming a user identity, comprising: a fifth acquisition module, configured to acquire payment information; The payment information includes first encrypted information of a user digital wallet ID of the target user; a sixth acquisition module, configured to match the first encrypted information with a set association relationship list to obtain second encrypted information matching the first encrypted information; The set association relationship list is established based on the device according to claim 12; A third determination module is configured to determine the payment digital wallet ID of the target user corresponding to the payment information based on the second encrypted information; The fourth determination module is configured to determine the identity of the target user based on the payment digital wallet ID.

15. A device for confirming a user identity, comprising: a seventh acquisition module, configured to acquire settlement information; The settlement information includes second encrypted information of the payment digital wallet ID of the target user; an eighth acquisition module, configured to match the second encrypted information with a set association relationship list to obtain first encrypted information matching the second encrypted information; The set association relationship list is established based on the device according to claim 13; A fifth determination module is configured to determine a user digital wallet ID of the target user based on the first encrypted information; The sixth determination module is configured to determine the identity of the target user based on the user digital wallet ID.

16. An electronic device comprising a memory and a processor; wherein: The memory is used to store one or more computer instructions, wherein the one or more computer instructions are executed by the processor to implement the steps of the method according to any one of claims 1 to 10.

17. A computer-readable storage medium having computer instructions stored thereon, wherein: When the computer instructions are executed by a processor, the steps of the method according to any one of claims 1 to 10 are implemented.

18. A computer program product, comprising a computer program / instruction, which, when executed by a processor, implements the steps of the method according to any one of claims 1 to 10.

Images