Joint transaction processing method and device, equipment, storage medium and program product

Abstract

The embodiment of the invention provides a joint transaction processing method and device, equipment, a storage medium and a program product, and relates to the field of financial science and technology or other related fields. The method comprises the following steps: receiving transaction request information of a user; wherein the transaction request information is request information of a joint transaction, and the joint transaction is a transaction involving a plurality of transaction subjects; in response to the transaction request information, calling an intelligent contract to determine transaction subjects involved in the joint transaction and transaction amounts of the transaction subjects, and calling feature vectors of user identity verification information uploaded by the transaction subjects; generating target verification data according to the transaction amount and the feature vector of each transaction subject; according to the target verification data, determining a verification result of the joint transaction; and executing the joint transaction according to the verification result. According to the method provided by the invention, the security of the transaction is improved, the risk that the user identity verification information is directly leaked is reduced, and the privacy of the transaction participant is protected.

Description

Technical Field

[0001] The present application relates to the field of financial technology or other related fields, and in particular to a joint transaction processing method, device, equipment, storage medium and program product. Background Art

[0002] In modern financial transactions, with the continuous advancement of globalization and digitalization, more and more transactions involve multiple trading entities. Such transactions involving multiple independent trading entities are usually called joint transactions.

[0003] In traditional transaction processing, when performing security verification, each transaction subject is usually required to perform identity authentication and transaction confirmation separately, and each transaction subject is required to upload the user's identity authentication information, which is not only time-consuming but may also lead to direct leakage of user identity authentication information.

[0004] Therefore, how to improve the security of user identity verification information during the security verification process and reduce the risk of user identity verification information leakage has become a technical problem that needs to be solved urgently. Summary of the invention

[0005] The present application provides a joint transaction processing method, device, equipment, storage medium and program product to solve technical problems such as how to improve the security of user identity authentication information during the security verification process and reduce the risk of leakage of user identity authentication information.

[0006] In a first aspect, the present application provides a joint transaction processing method, the method comprising:

[0007] Receiving transaction request information from a user; wherein the transaction request information is request information for a joint transaction, and the joint transaction is a transaction involving multiple transaction entities;

[0008] In response to the transaction request information, calling a smart contract to determine the transaction subjects involved in the joint transaction and the transaction amounts of each of the transaction subjects, and retrieving a feature vector of the user identity authentication information uploaded by each of the transaction subjects;

[0009] Generate target verification data according to the transaction amount of each transaction subject and the feature vector;

[0010] Determining a verification result of the joint transaction according to the target verification data;

[0011] The joint transaction is executed according to the verification result.

[0012] Optionally, generating target verification data according to the transaction amount of each transaction subject and the feature vector includes:

[0013] Determining the weight of the feature vector corresponding to each of the transaction entities according to the transaction amount of each of the transaction entities;

[0014] Target verification data is generated according to the feature vectors corresponding to each of the transaction entities and the weights.

[0015] Optionally, determining the verification result of the joint transaction according to the target verification data includes:

[0016] Compare the target verification data with the feature vectors of the user identity verification information pre-stored by each of the transaction entities to determine the similarity corresponding to each of the transaction entities;

[0017] Determine the comprehensive similarity based on the similarities corresponding to the transaction entities;

[0018] If the comprehensive similarity is greater than or equal to a preset value, determining that the verification result of the joint transaction indicates that the verification has passed;

[0019] If the comprehensive similarity is less than the preset value, it is determined that the verification result of the joint transaction indicates a verification failure.

[0020] Optionally, determining a comprehensive similarity according to the similarities corresponding to the transaction entities includes:

[0021] Determining an average value of the similarities according to the similarities corresponding to the transaction entities;

[0022] The average value is determined as the comprehensive similarity.

[0023] Optionally, determining a comprehensive similarity according to the similarities corresponding to the transaction entities includes:

[0024] Determine the product of the similarity corresponding to the transaction subject and the weight of the feature vector corresponding to the transaction subject, and determine the sum of the products as the comprehensive similarity.

[0025] Optionally, executing the joint transaction according to the verification result includes:

[0026] If the verification result indicates that the verification is passed, the joint transaction is completed;

[0027] If the verification result indicates that the verification has failed, a prompt message is displayed; wherein the prompt message is used to indicate that the transaction has failed.

[0028] Optionally, before displaying the prompt information, the method further includes:

[0029] The step of responding to the transaction request information is executed again until a preset number of times is reached.

[0030] In a second aspect, the present application provides a joint transaction processing device, the device comprising:

[0031] A receiving unit, configured to receive transaction request information from a user; wherein the transaction request information is request information for a joint transaction, and the joint transaction is a transaction involving multiple transaction entities;

[0032] A response unit, configured to respond to the transaction request information, call a smart contract to determine the transaction subjects involved in the joint transaction and the transaction amounts of each of the transaction subjects, and retrieve a feature vector of the user identity authentication information uploaded by each of the transaction subjects;

[0033] A processing unit, configured to generate target verification data according to the transaction amount of each transaction subject and the feature vector;

[0034] A verification unit, configured to determine a verification result of the joint transaction according to the target verification data;

[0035] An execution unit is used to execute the joint transaction according to the verification result.

[0036] In a third aspect, the present application provides an electronic device, the electronic device comprising: a processor, and a memory communicatively connected to the processor;

[0037] The memory stores computer-executable instructions;

[0038] The processor executes the computer-executable instructions stored in the memory to implement the aforementioned method.

[0039] In a fourth aspect, the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions, and the computer-executable instructions are used to implement the method as described above when executed by a processor.

[0040] In a fifth aspect, the present application provides a computer program product, including a computer program, which is used to implement the method as described above when executed by a processor.

[0041] In the joint transaction processing method, device, equipment, storage medium and program product provided by the present application, the method includes: receiving the transaction request information of the user; wherein the transaction request information is the request information of the joint transaction, and the joint transaction is a transaction involving multiple transaction subjects; in response to the transaction request information, calling the smart contract to determine the transaction subjects involved in the joint transaction and the transaction amount of each transaction subject, and retrieving the characteristic vector of the user identity verification information uploaded by each transaction subject; generating target verification data according to the transaction amount of each transaction subject and the characteristic vector; determining the verification result of the joint transaction according to the target verification data; and executing the joint transaction according to the verification result. The scheme of the present application completes identity verification through the characteristic vector of the user identity verification information, which can not only effectively prevent identity fraud and unauthorized transactions, improve the security of the transaction, but also reduce the risk of direct leakage of user identity verification information, and protect the privacy of transaction participants; in addition, by using smart contracts to automatically process joint transactions, the time of manual intervention and manual review is also reduced. Based on the smart contract, the transaction subject can be quickly identified, the transaction amount can be calculated, and the verification data can be automatically generated and verified, thereby speeding up the transaction processing speed and improving the transaction processing efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0043] Figure 1 A flowchart of a joint transaction processing method provided in an embodiment of the present application;

[0044] Figure 2 A flowchart of another joint transaction processing method provided in an embodiment of the present application;

[0045] Figure 3 A schematic diagram of the structure of a joint transaction processing device provided in an embodiment of the present application;

[0046] Figure 4 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application.

[0047] The above drawings have shown clear embodiments of the present application, which will be described in more detail later. These drawings and text descriptions are not intended to limit the scope of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0048] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0049] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of the relevant data comply with the relevant laws, regulations and standards of the relevant countries and regions, take necessary confidentiality measures, do not violate public order and good morals, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0050] In addition, this application involves big data analysis of user information (including but not limited to personal biometrics, identity data, consumption data, asset data, electronic terminal operation data, etc.), and the use of artificial intelligence technology for automated decision-making, and a technical solution for making decisions that have a significant impact on personal rights and interests based on the results of automated decision-making. The application provides users with corresponding operation entrances for them to choose to agree or reject the results of automated decision-making; if the user chooses to reject, the expert decision-making process will be entered.

[0051] It should be noted that the joint transaction processing method, device, equipment, storage medium and program product provided in this application can be used in the field of financial technology, and can also be used in any field other than the field of financial technology. The application does not limit the application field of the joint transaction processing method, device, equipment, storage medium and program product.

[0052] With the rapid development of financial technology and e-commerce, people's demand for transaction automation and convenience has become increasingly prominent. In order to meet this demand, banks will cooperate with many third-party service providers to provide diversified services, such as withholding of utility bills, mortgage and car loans, and credit card repayments. This service model of withholding by banks not only simplifies the transaction process for users, but also improves the settlement efficiency between banks and third-party service providers.

[0053] The traditional withholding model is usually that banks establish cooperative relationships with a single service provider and conduct one-to-one withholding operations. However, with the increase in the number of third-party service providers and the expansion of service types, this single withholding model can no longer meet the needs of fast and efficient processing. Therefore, the multi-party withholding system came into being.

[0054] Among them, based on the multi-party withholding system, banks can establish connections with multiple third-party service providers through a unified interface or platform to achieve batch and automated withholding operations. This type of system not only reduces the cumbersome docking process between banks and third-party service providers, but also improves the processing efficiency of withholding business. Through the multi-party withholding system, banks can also monitor the withholding status in real time to improve the accuracy and security of transactions. Of course, in order to ensure transaction security, security verification is still an essential process during the execution of transactions.

[0055] In traditional transaction processing, when performing security verification, each transaction subject (that is, third-party service provider) is usually required to perform user identity verification and transaction confirmation separately. The bank needs to obtain the user's manual signature, face data and other user identity verification information uploaded by the user through the third-party service provider, and then compare and verify it with the user identity verification information pre-stored in the blockchain by the third-party service provider. Although this processing method has relatively high transaction security to a certain extent, it also brings the risk of direct leakage of user identity verification information.

[0056] In order to solve the above technical problems, an embodiment of the present application provides a new joint transaction processing method. On the one hand, in the present application, only the feature vector of user identity authentication information is pre-stored, rather than directly storing the user identity authentication information. In this way, when performing identity authentication, the feature vector of the user identity authentication information is also retrieved, which greatly reduces the risk of direct leakage of user identity authentication information and improves the security of user identity authentication information. On the other hand, the present application also generates target verification data based on the transaction amount of each transaction subject in the joint transaction, so as to improve the credibility of the data, thereby also improving transaction security to a certain extent.

[0057] The technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems are described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0058] Figure 1A flowchart of a joint transaction processing method provided for an embodiment of the present application. Exemplarily, the execution subject of the embodiment of the present application may be a joint transaction processing device, which may be located on a server or other electronic device running a bank transaction processing system, and the electronic device may be a mobile terminal such as a laptop computer, etc., which is not limited by the embodiment of the present application. Among them, in order to improve transaction security, the bank transaction processing system may also be deployed on a blockchain, and the processing of joint transactions is completed based on the blockchain, which can not only improve transaction transparency, but also improve transaction security, and can meet the user's fast, efficient, and secure processing needs. Therefore, the execution subject of the embodiment of the present application may also be a blockchain, which is not limited by the embodiment of the present application.

[0059] This application embodiment takes the execution subject as a joint transaction processing device as an example for detailed description. Figure 1 As shown, the joint transaction processing method provided in the embodiment of the present application may include:

[0060] S101. Receive transaction request information from a user; wherein the transaction request information is request information for a joint transaction, and a joint transaction is a transaction involving multiple transaction entities.

[0061] Exemplarily, the joint transaction in this application is a transaction involving multiple transaction entities. The transaction entity refers to a third-party service provider that cooperates with the bank. The third-party service provider can provide diversified services, such as water and electricity bill deduction, mortgage and car loan deduction, credit card repayment deduction, etc. The transaction request information in the embodiment of this application is the request information of the joint transaction. The joint transaction processing device in the embodiment of this application can receive the transaction request information from the user through a pre-set interface or entry. This interface can be an API endpoint, a Web form, or other communication channels (such as a message system, etc.), which is not limited in the embodiment of this application.

[0062] Among them, the user's transaction request information includes the information required to execute the joint transaction, such as user information (including the user's name, contact information, account information, etc.), transaction time, transaction purpose (that is, the business type, purpose or reason of the transaction), payee information (such as merchant name, merchant number or other identification information to identify the payee), transaction subject, transaction amount of each transaction subject, etc. This information can ensure that the joint transaction can be carried out accurately and smoothly and comply with relevant laws, regulations and agreement requirements. In actual scenarios, the specific information may vary from financial institution to financial institution, and this application embodiment does not limit it.

[0063] Optionally, the user's transaction request information can be sent by the user in real time. For example, the user can select the deduction business he wants to execute according to actual needs, and then initiate the transaction request through a function key like "one-click deduction". In addition, the user's transaction request information can also be sent regularly based on a scheduled sending function. The user can pre-set the transaction business and transaction time of the joint transaction, and the system will then send the user's transaction request regularly, etc. This embodiment of the present application is not limited.

[0064] S102. In response to the transaction request information, the smart contract is called to determine the transaction subjects involved in the joint transaction and the transaction amounts of each transaction subject, and the feature vector of the user identity authentication information uploaded by each transaction subject is retrieved.

[0065] Exemplarily, after the joint transaction processing device of the embodiment of the present application receives the transaction request information of the user, it will parse and respond to the transaction request information of the user and execute the transaction request of the user. Specifically, the joint transaction processing device will call the smart contract pre-deployed on the blockchain, wherein the smart contract is a self-executing code that can automatically execute transactions according to preset conditions. In the embodiment of the present application, based on the smart contract, the transaction subjects involved in the joint transaction and the transaction amounts of each transaction subject can be determined. After determining the transaction subjects involved in the joint transaction, the joint transaction processing device of the embodiment of the present application can retrieve the feature vector of the user identity authentication information stored in the blockchain uploaded in advance by each transaction subject to perform identity verification.

[0066] Among them, the user identity authentication information may include one or more of the user's facial information, fingerprint information, manual signature, pupil information, etc., which can be used to verify the user's identity, and the embodiments of the present application are not limited.

[0067] It should be noted that no matter whether each transaction subject uploads user identity authentication information or feature vectors of user identity authentication information in advance when signing a contract with the bank, in this application, they will be converted into feature vectors of user identity authentication information. In other words, what is stored in the blockchain are feature vectors of user identity authentication information, rather than the user identity authentication information itself. Based on this, not only can security verification be completed, but also the risk of direct leakage of user identity authentication information during identity verification is reduced.

[0068] S103: Generate target verification data according to the transaction amount and feature vector of each transaction subject.

[0069] Exemplarily, the target verification data is the key data for identity verification. In order to improve the accuracy of identity verification, more accurate target verification data needs to be generated. In the embodiment of the present application, the joint transaction processing device can generate target verification data based on the transaction amount of each transaction subject and the feature vector of the user identity verification information uploaded by each transaction subject.

[0070] Optionally, in a possible embodiment, generating target verification data according to the transaction amount and feature vector of each transaction subject may include:

[0071] S1. Determine the weight of the feature vector corresponding to each transaction subject according to the transaction amount of each transaction subject;

[0072] S2. Generate target verification data based on the feature vectors and weights corresponding to each transaction subject.

[0073] Exemplarily, the transaction amount of each transaction subject reflects the economic participation of each subject in the joint transaction. The larger the transaction amount, the higher the participation. According to the transaction amount of each transaction subject, the weight of the feature vector corresponding to each transaction subject can be determined. For example, the sum of the transaction amounts of all transaction subjects can be calculated. For each transaction subject, the weight of its feature vector is calculated according to the ratio of its transaction amount to the total amount. The weight reflects the relative importance of each transaction subject in the entire transaction.

[0074] Furthermore, according to the feature vectors and weights corresponding to each transaction subject, the target verification data can be generated. Specifically, the calculated weight can be applied to the feature vector of each transaction subject, and then the weighted feature vectors of all transaction subjects are integrated to form a comprehensive feature vector, and then the comprehensive feature vector is fused and encrypted to obtain the target verification data.

[0075] By first determining the weight of the characteristic vector corresponding to each transaction subject based on the transaction amount of each transaction subject, and then generating a weighted scheme for the target verification data based on the characteristic vector and weight corresponding to each transaction subject, it is possible to generate target verification data that reflects the relative importance of the transaction subject. This not only improves the security and uniqueness of the verification data, but also enhances the overall reliability and trust of the transaction system.

[0076] S104. Determine the verification result of the joint transaction according to the target verification data.

[0077] Exemplarily, identity verification is a key step in executing a transaction. The embodiment of the present application completes user identity verification based on the generated target verification data and determines the verification result of the joint transaction.

[0078] Optionally, in a possible embodiment, determining the verification result of the joint transaction according to the target verification data includes:

[0079] S10, comparing the target verification data with the feature vectors of the user identity authentication information pre-stored by each transaction subject to determine the similarity corresponding to each transaction subject;

[0080] S20, determining a comprehensive similarity based on the similarities corresponding to the transaction entities;

[0081] S30, if the comprehensive similarity is greater than or equal to a preset value, determining that the verification result of the joint transaction indicates that the verification has passed;

[0082] S40: If the comprehensive similarity is less than a preset value, it is determined that the verification result of the joint transaction indicates a verification failure.

[0083] For example, in a joint transaction, it is crucial to ensure the authenticity and integrity of the transaction. By comparing the target verification data with the user identity verification information provided by the transaction subject, the legitimacy of the transaction can be effectively verified.

[0084] Specifically, the target verification data is compared with the feature vector of the user identity authentication information pre-stored by each transaction subject to calculate the similarity. Among them, the similarity can be calculated using a variety of methods, such as cosine similarity, Euclidean distance, or Pearson correlation coefficient, etc., which are not limited in the embodiments of the present application. According to the similarity corresponding to each transaction subject, a comprehensive similarity can be determined, and the comprehensive similarity is used to indicate the overall verification result of the joint transaction.

[0085] Optionally, in a possible embodiment, determining the comprehensive similarity according to the similarities corresponding to the transaction entities may include:

[0086] S211. Determine an average value of the similarities according to the similarities corresponding to the transaction entities;

[0087] S212: Determine the average value as the comprehensive similarity.

[0088] For example, after obtaining the similarity corresponding to each transaction subject, the average value of these similarity values ​​can be calculated, and the average value of the similarity can be used as the comprehensive similarity. By calculating the average value of the similarity between the transaction subjects, a simplified method is provided to evaluate the overall verification result of the joint transaction, which is not only simple to calculate, but also easy to understand and apply.

[0089] Optionally, in another possible embodiment, determining the comprehensive similarity according to the similarities corresponding to the transaction entities may include:

[0090] S221. Determine the product of the similarity corresponding to the transaction subject and the weight of the feature vector corresponding to the transaction subject, and determine the sum of the products as the comprehensive similarity.

[0091] Exemplarily, the similarities corresponding to each transaction subject can also be weighted in combination with the transaction amount to obtain a comprehensive similarity. Specifically, for the similarity corresponding to each transaction subject, the product of the similarity and the weight of the corresponding feature vector is calculated to adjust the similarity value so that it reflects its corresponding importance in combination with the size of the transaction amount, and then all the product results are added together to obtain a comprehensive similarity value, which represents the overall verification result of the joint transaction taking into account the weights of each feature. In this way, the comprehensive similarity not only takes into account the verification results corresponding to each transaction subject, but also combines the importance of the feature vectors of the user identity authentication information uploaded by each transaction subject, thereby providing a more comprehensive and accurate evaluation scheme and improving the accuracy of the comprehensive similarity.

[0092] For example, if the comprehensive similarity is greater than or equal to a preset value, it indicates that the user identity verification information uploaded by the transaction subject is highly consistent with the target verification data, the transaction is considered legal, and the verification can be considered to have passed; if the comprehensive similarity is less than the preset value, it indicates that the user identity verification information uploaded by the transaction subject is inconsistent with the target verification data, there may be a risk of data tampering, and the verification can be considered to have failed. Among them, the embodiment of the present application does not limit the specific value of the preset value, which can be set according to the security requirements of the system and historical data.

[0093] Through similarity calculation and comprehensive judgment, a flexible and reliable transaction verification mechanism is provided, which can effectively verify the authenticity and integrity of joint transactions and improve the security and legality of transactions.

[0094] S105. Execute the joint transaction based on the verification result.

[0095] Exemplarily, the verification result indicates whether the user identity authentication information uploaded by each transaction subject has been authenticated. Different verification results will result in different subsequent processing procedures for the joint transaction.

[0096] Optionally, based on the verification result, executing the joint transaction may include:

[0097] S100, if the verification result indicates that the verification is passed, the joint transaction is completed;

[0098] S200. If the verification result indicates that the verification has failed, a prompt message is displayed; wherein the prompt message is used to indicate that the transaction has failed.

[0099] Exemplarily, if the verification result indicates that the verification is passed, it means that the user identity verification information uploaded by the transaction subject is highly consistent with the target verification data, and the user identity verification is passed. The joint transaction processing device of the embodiment of the present application can execute the subsequent steps to complete the joint transaction. For example, if the joint transaction involves a deduction transaction involving water and electricity bills, mortgage and car loan deductions, and credit card repayment deductions, the deduction system can be notified to transfer money to the transaction subject of the water and electricity bill deduction, the transaction subject of the mortgage and car loan deduction, and the transaction subject of the credit card repayment deduction, respectively, to complete the subsequent deduction operation. If the verification result indicates that the verification fails, it means that the user identity verification information uploaded by the transaction subject is inconsistent with the target verification data, and the user identity verification fails. At this time, a prompt message can be displayed to prompt the user and the transaction subject that the transaction has failed.

[0100] Through this decision-making process based on verification results, the success and failure of transactions can be effectively managed, ensuring that transactions are executed only when conditions are met, thereby improving the security and reliability of transactions. At the same time, by providing clear prompt information, users can also better understand the transaction status and take corresponding actions, thereby improving the user's trading experience.

[0101] Optionally, in a possible embodiment, in order to improve the transaction success rate, before displaying the prompt information, the joint transaction processing method provided in the embodiment of the present application may also include: executing the step of responding to the transaction request information again until a preset number threshold is reached.

[0102] Exemplarily, in order to improve the transaction success rate of the joint transaction, when the verification result indicates that the verification has failed, you can try several more times, re-respond to the user's transaction request information, and re-determine the verification result until the preset number of times threshold is reached, and then display the prompt information. Among them, the embodiment of the present application does not limit the value of the preset number of times threshold. For example, it can be 3 times. After repeatedly responding to the user's transaction request information 3 times, if the verification fails 3 times, then display the prompt information. By repeatedly responding, transaction failures caused by abnormal processing can be avoided, thereby improving the transaction success rate of the joint transaction.

[0103] The joint transaction processing method provided by the embodiment of the present application includes: receiving the transaction request information of the user; wherein the transaction request information is the request information of the joint transaction, and the joint transaction is a transaction involving multiple transaction subjects; in response to the transaction request information, calling the smart contract to determine the transaction subjects involved in the joint transaction and the transaction amount of each transaction subject, and retrieving the characteristic vector of the user identity verification information uploaded by each transaction subject; generating target verification data according to the transaction amount and characteristic vector of each transaction subject; determining the verification result of the joint transaction according to the target verification data; and executing the joint transaction according to the verification result. The scheme of the present application completes identity verification through the characteristic vector of the user identity verification information, which can not only effectively prevent identity fraud and unauthorized transactions, improve the security of the transaction, but also reduce the risk of direct leakage of user identity verification information, and protect the privacy of transaction participants; in addition, by using smart contracts to automatically process joint transactions, the time of manual intervention and manual review is also reduced. Based on the smart contract, the transaction subject can be quickly identified, the transaction amount can be calculated, and the verification data can be automatically generated and verified, thereby speeding up the transaction processing speed and improving the transaction processing efficiency.

[0104] Figure 2 A flowchart of another joint transaction processing method provided in an embodiment of the present application. Figure 2 As shown, the joint transaction processing method provided in the embodiment of the present application may include:

[0105] S201. Receive transaction request information from a user; wherein the transaction request information is request information for a joint transaction, and a joint transaction is a transaction involving multiple transaction entities.

[0106] S202. In response to the transaction request information, the smart contract is called to determine the transaction subjects involved in the joint transaction and the transaction amounts of each transaction subject, and the feature vector of the user identity authentication information uploaded by each transaction subject is retrieved.

[0107] S203: Determine the weight of the feature vector corresponding to each transaction subject according to the transaction amount of each transaction subject.

[0108] S204: Generate target verification data according to the feature vectors and weights corresponding to each transaction subject.

[0109] S205: Compare the target verification data with the feature vectors of the user identity verification information pre-stored by each transaction subject to determine the similarity corresponding to each transaction subject.

[0110] S206. Determine the comprehensive similarity according to the similarities corresponding to the transaction entities;

[0111] S207: Determine whether the comprehensive similarity is greater than or equal to a preset value.

[0112] If yes, execute step S208; if no, execute step S209, or execute step S202 again until the preset number threshold is reached and then execute step S209.

[0113] S208. Complete the joint transaction.

[0114] S209: Display prompt information; wherein the prompt information is used to indicate that the transaction has failed.

[0115] It should be noted that the specific implementation of the above steps in this embodiment can refer to the detailed description of other embodiments, which will not be repeated here. In the joint transaction processing method in actual application, some or all of the above steps may be included, and the embodiment of this application is not limited.

[0116] The joint transaction processing method provided in the embodiment of the present application completes identity authentication through the feature vector of user identity authentication information, which can not only effectively prevent identity fraud and unauthorized transactions and improve the security of transactions, but also reduce the risk of direct leakage of user identity authentication information and protect the privacy of transaction participants; in addition, by using smart contracts to automatically process joint transactions, the time for manual intervention and manual review is also reduced. Based on smart contracts, the transaction subject can be quickly identified, the transaction amount can be calculated, and verification data can be automatically generated and verified, thereby speeding up transaction processing and improving transaction processing efficiency.

[0117] The following is an embodiment of the device of the present application, which can be used to execute the embodiment of the method of the present application. For details not disclosed in the embodiment of the device of the present application, please refer to the embodiment of the method of the present application.

[0118] Figure 3 This is a schematic diagram of the structure of a joint transaction processing device provided in an embodiment of the present application. Figure 3 As shown, the joint transaction processing device 30 provided in the embodiment of the present application includes a receiving unit 301, a responding unit 302, a processing unit 303, a verification unit 304 and an execution unit 305.

[0119] The receiving unit 301 is used to receive transaction request information from a user; wherein the transaction request information is request information for a joint transaction, and a joint transaction is a transaction involving multiple transaction entities;

[0120] The response unit 302 is used to respond to the transaction request information, call the smart contract to determine the transaction subjects involved in the joint transaction and the transaction amount of each transaction subject, and retrieve the feature vector of the user identity authentication information uploaded by each transaction subject;

[0121] The processing unit 303 is used to generate target verification data according to the transaction amount and feature vector of each transaction subject;

[0122] A verification unit 304, configured to determine a verification result of the joint transaction according to the target verification data;

[0123] The execution unit 305 is used to execute the joint transaction according to the verification result.

[0124] The device provided in this embodiment can be used to execute the method of the above embodiment. Its implementation principle and technical effect are similar and will not be described in detail here.

[0125] Based on the above device embodiment, in some possible examples, the processing unit 303 is specifically configured to:

[0126] According to the transaction amount of each transaction subject, the weight of the feature vector corresponding to each transaction subject is determined;

[0127] Generate target verification data based on the feature vectors and weights corresponding to each transaction entity.

[0128] Based on the above device embodiment, in some possible examples, the verification unit 304 is specifically used to:

[0129] Compare the target verification data with the feature vectors of the user identity verification information pre-stored by each transaction subject to determine the similarity corresponding to each transaction subject;

[0130] Determine the comprehensive similarity based on the similarities corresponding to each transaction subject;

[0131] If the comprehensive similarity is greater than or equal to a preset value, then determining that the verification result of the joint transaction indicates that the verification has passed;

[0132] If the comprehensive similarity is less than a preset value, it is determined that the verification result of the joint transaction indicates a verification failure.

[0133] Based on the above device embodiment, in some possible examples, the verification unit 304 is further specifically configured to:

[0134] According to the similarities corresponding to each transaction subject, an average value of the similarities is determined;

[0135] Determine the average value as the comprehensive similarity.

[0136] Based on the above device embodiment, in some possible examples, the verification unit 304 is further specifically configured to:

[0137] The product of the similarity corresponding to the transaction subject and the weight of the feature vector corresponding to the transaction subject is determined, and the sum of the products is determined as the comprehensive similarity.

[0138] Based on the above device embodiment, in some possible examples, the execution unit 305 is further specifically configured to:

[0139] If the verification result indicates that the verification is passed, the joint transaction is completed;

[0140] If the verification result indicates that the verification has failed, a prompt message is displayed; wherein the prompt message is used to indicate that the transaction has failed.

[0141] Based on the above device embodiment, in some possible examples, the execution unit 305 is further specifically configured to:

[0142] Before displaying the prompt information, the step of responding to the transaction request information is executed again until a preset number of times threshold is reached.

[0143] It should be noted that it should be understood that the division of the various modules of the above device is only a division of logical functions. In actual implementation, they can be fully or partially integrated into one physical entity, or they can be physically separated. And these modules can all be implemented in the form of software called by processing elements; they can also be all implemented in the form of hardware; some modules can also be implemented in the form of software called by processing elements, and some modules can be implemented in the form of hardware. In addition, it can also be stored in the memory of the above device in the form of program code, and the functions of the above data processing modules can be called and executed by a processing element of the above device. The implementation of other modules is similar. In addition, all or part of these modules can be integrated together, or they can be implemented independently. The processing element here can be an integrated circuit with signal processing capabilities. In the implementation process, each step of the above method or each module above can be completed by an integrated logic circuit of hardware in the processor element or instructions in the form of software.

[0144] Figure 4 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. Figure 4 As shown, the electronic device 40 includes: a processor 401, and a memory 402 communicatively connected to the processor.

[0145] The memory 402 stores computer-executable instructions; the processor 401 executes the computer-executable instructions stored in the memory 402 to implement any of the aforementioned methods.

[0146] In the specific implementation of the above electronic device, it should be understood that the processor can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), etc. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc. The method disclosed in the embodiment of the present application can be directly embodied as a hardware processor for execution, or a combination of hardware and software modules in the processor for execution.

[0147] An embodiment of the present application also provides a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are executed by a processor, they are used to implement any of the methods described above.

[0148] Those skilled in the art can understand that all or part of the steps of implementing the above-mentioned method embodiments can be completed by hardware related to computer instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, the steps of the above-mentioned method embodiments are executed; and the aforementioned storage medium includes: ROM, RAM, disk or optical disk and other media that can store program codes.

[0149] An embodiment of the present application also provides a computer program product, including a computer program, which is used to implement any of the aforementioned methods when executed by a processor.

[0150] It should be noted that, for the aforementioned method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that the present application is not limited by the described order of actions, because according to the present application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all optional embodiments, and the actions and modules involved are not necessarily required by the present application.

[0151] It should be further noted that, although the various steps in the flow chart are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps is not strictly limited in order, and these steps can be executed in other orders. Moreover, at least a portion of the steps in the flow chart may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these sub-steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a portion of the sub-steps or stages of other steps.

[0152] It should be understood that the above-mentioned device embodiments are only illustrative, and the device of the present application can also be implemented in other ways. For example, the division of units / modules in the above-mentioned embodiments is only a logical function division, and there may be other division methods in actual implementation. For example, multiple units, modules or components can be combined, or can be integrated into another system, or some features can be ignored or not executed.

[0153] In addition, unless otherwise specified, each functional unit / module in each embodiment of the present application may be integrated into one unit / module, each unit / module may exist physically separately, or two or more units / modules may be integrated together. The above-mentioned integrated unit / module may be implemented in the form of hardware or in the form of a software program module.

[0154] If the integrated unit / module is implemented in the form of hardware, the hardware may be a digital circuit, an analog circuit, etc. The physical implementation of the hardware structure includes but is not limited to transistors, memristors, etc. If not specifically stated, the processor may be any appropriate hardware processor, such as a CPU, a GPU, an FPGA, a DSP, an ASIC, etc. If not specifically stated, the storage unit may be any appropriate magnetic storage medium or magneto-optical storage medium, such as a resistive random access memory RRAM (Resistive Random Access Memory), a dynamic random access memory DRAM (Dynamic Random Access Memory), a static random access memory SRAM (Static Random-Access Memory), an enhanced dynamic random access memory EDRAM (Enhanced Dynamic Random Access Memory), a high-bandwidth memory HBM (High-Bandwidth Memory), a hybrid memory cube HMC (Hybrid Memory Cube), etc.

[0155] If the integrated unit / module is implemented in the form of a software program module and sold or used as an independent product, it can be stored in a computer-readable memory. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art or all or part of the technical solution, can be embodied in the form of a software product, which is stored in a memory and includes several instructions for a computer device (which can be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the various embodiments of the present application. The aforementioned memory includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, disk or optical disk and other media that can store program codes.

[0156] In the above embodiments, the description of each embodiment has its own emphasis. For the part not described in detail in a certain embodiment, please refer to the relevant description of other embodiments. The technical features of the above embodiments can be combined arbitrarily. In order to make the description concise, all possible combinations of the technical features in the above embodiments are not described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0157] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the invention disclosed herein. The present application is intended to cover any modification, use or adaptation of the present application, which follows the general principles of the present application and includes common knowledge or customary techniques in the art that are not disclosed in the present application. The specification and examples are intended to be exemplary only, and the true scope and spirit of the present application are indicated by the following claims.

[0158] It should be understood that the present application is not limited to the precise structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.

Claims

1. A joint transaction processing method, characterized in that: The method comprises: Receiving transaction request information from a user; wherein the transaction request information is request information for a joint transaction, and the joint transaction is a transaction involving multiple transaction entities; In response to the transaction request information, calling a smart contract to determine the transaction subjects involved in the joint transaction and the transaction amounts of each of the transaction subjects, and retrieving a feature vector of the user identity authentication information uploaded by each of the transaction subjects; Generate target verification data according to the transaction amount of each transaction subject and the feature vector; Determining a verification result of the joint transaction according to the target verification data; The joint transaction is executed according to the verification result.

2. The method according to claim 1, characterized in that Generate target verification data according to the transaction amount of each transaction subject and the feature vector, including: Determining the weight of the feature vector corresponding to each of the transaction entities according to the transaction amount of each of the transaction entities; Target verification data is generated according to the feature vectors corresponding to each of the transaction entities and the weights.

3. The method according to claim 1, characterized in that Determining a verification result of the joint transaction according to the target verification data includes: Compare the target verification data with the feature vectors of the user identity verification information pre-stored by each of the transaction entities to determine the similarity corresponding to each of the transaction entities; Determine the comprehensive similarity based on the similarities corresponding to the transaction entities; If the comprehensive similarity is greater than or equal to a preset value, determining that the verification result of the joint transaction indicates that the verification has passed; If the comprehensive similarity is less than the preset value, it is determined that the verification result of the joint transaction indicates a verification failure.

4. The method according to claim 3, characterized in that According to the similarities corresponding to the transaction entities, a comprehensive similarity is determined, including: Determining an average value of the similarities according to the similarities corresponding to the transaction entities; The average value is determined as the comprehensive similarity.

5. The method according to claim 3, characterized in that: According to the similarities corresponding to the transaction entities, a comprehensive similarity is determined, including: Determine the product of the similarity corresponding to the transaction subject and the weight of the feature vector corresponding to the transaction subject, and determine the sum of the products as the comprehensive similarity.

6. The method according to any one of claims 1 to 5, characterized in that According to the verification result, executing the joint transaction includes: If the verification result indicates that the verification is passed, the joint transaction is completed; If the verification result indicates that the verification has failed, a prompt message is displayed; wherein the prompt message is used to indicate that the transaction has failed.

7. The method according to claim 6, characterized in that Before displaying the prompt information, the method further includes: The step of responding to the transaction request information is executed again until a preset number of times is reached.

8. A joint transaction processing device, characterized in that: The device comprises: A receiving unit, configured to receive transaction request information from a user; wherein the transaction request information is request information for a joint transaction, and the joint transaction is a transaction involving multiple transaction entities; A response unit, configured to respond to the transaction request information, call a smart contract to determine the transaction subjects involved in the joint transaction and the transaction amounts of each of the transaction subjects, and retrieve a feature vector of the user identity authentication information uploaded by each of the transaction subjects; A processing unit, configured to generate target verification data according to the transaction amount of each transaction subject and the feature vector; A verification unit, configured to determine a verification result of the joint transaction according to the target verification data; An execution unit is used to execute the joint transaction according to the verification result.

9. An electronic device, characterized in that: include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory to implement the method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, which are used to implement the method according to any one of claims 1 to 7 when executed by a processor.

11. A computer program product, characterized in that The invention comprises a computer program, which implements the method according to any one of claims 1 to 7 when being executed by a processor.

Images