Virtual account transaction verification and recording system based on block chain
Through a blockchain-based virtual account transaction verification and recording system, combined with smart contracts and dual identity authentication, the security and compliance issues of special fund transactions in real estate management are solved, and effective supervision and management of capital flows are achieved.
Patent Information
- Application Number
- CN202411153503.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-21
- Publication Date
- 2024-11-12
- Estimated Expiration
- Not applicable · inactive patent
AI Technical Summary
In real estate management, the transaction verification and recording system of special funds is difficult to ensure the security and compliance of multiple users' shared accounts, which makes it difficult to supervise and manage capital flows, and is prone to security problems such as misappropriation.
Adopt a virtual account transaction verification and recording system based on blockchain, including login monitoring module, identity verification module, transaction verification module and blockchain storage module, transaction compliance verification through smart contracts, and use dual identity authentication and randomness Token generator reduces risk.
It effectively weakens the risk of shared accounts, improves the management control of physical account owners over shared accounts, ensures compliance with transaction operations, and avoids security issues such as misappropriation of special funds.
Smart Images

Figure CN118941288A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of information technology, and more specifically, to a virtual account transaction verification and recording system based on blockchain. Background Art
[0002] In the field of modern real estate management, special fund management is a key link in the management of the real estate industry; these special funds include but are not limited to pre-sale funds for commercial housing, transaction funds for existing housing, special funds for residential maintenance, special funds for elevator fire protection, and public revenue funds generated by the management of public facilities and equipment in the community (such as advertising revenue, etc.); the management and use of these funds are directly related to the vital interests of residents and enterprises and the credibility of the government; therefore, ensuring the transparency, efficiency and security of these funds is an important task in the process of real estate digital upgrading; however, in the management of special funds, in the process of handling special fund transactions, different institutions (such as banks, developers, brokerage agencies, property service companies and administrative departments), different roles and users are often required to participate together; in this case, how to ensure the compliance, tamper-proof and security of fund transactions involving each business has become a technical problem.
[0003] At present, there is a lack of transaction verification and recording systems for the above scenarios. Although there are some relevant technical documents, such as the patent publication number CN113487430A, which discloses a method, device, equipment and medium for monitoring operation behavior, the method improves the security of transaction operations through transaction monitoring; however, research and practical application of the above methods and prior arts have found that the above methods and prior arts have at least the following defects: (1) When multiple users share an account, the risk of the shared account cannot be reduced, and the management and control of the shared account by the physical account owner should be increased as much as possible; (2) The lack of an effective transaction verification mechanism makes it difficult to ensure the compliance of each user's transaction operations, which in turn makes it difficult to effectively supervise and manage the flow of funds. Furthermore, it is difficult to effectively avoid security issues such as the misappropriation of special funds. Summary of the invention
[0004] In order to overcome the above-mentioned defects of the prior art, an embodiment of the present invention provides a virtual account transaction verification and recording system based on blockchain.
[0005] To achieve the above object, the present invention provides the following technical solutions: A virtual account transaction verification and recording system based on blockchain, the system includes a login monitoring module, an identity authentication module, a transaction verification module, a transaction generation module and a blockchain storage module; wherein, A login monitoring module, used to obtain login data when a user logs in to a target virtual account, and record the time when the user enters the target virtual account number as a first target time; the target virtual account is associated with a physical account, the physical account belongs to a special fund management node on the blockchain, the special fund management node associates a plurality of virtual accounts with different transaction authority levels for the physical account on the blockchain, and the target virtual account is the virtual account that performs the current login operation; The identity authentication module is used to retrieve the corresponding identity token attributes according to the target virtual account, and verify whether the user is allowed to enter the management interface of the target virtual account based on the login data and the identity token attributes; A transaction verification module, which is used to perform compliance verification on the transaction request using a smart contract containing verification conditions when a user enters the management interface and initiates a transaction request, and obtain a compliance verification result; the verification condition includes a first verification condition and a second verification condition; the compliance verification result includes a first verification result and a second verification result; The transaction generation module is used to send the transaction request to the registered bank of the entity account according to the first verification result and generate a transaction form.
[0006] Furthermore, the login data includes the account number, password and login authentication data of the virtual account input by the user; the login authentication data is specifically the identity token attribute input by the user; The transaction authority levels include a first-level authority level, a second-level authority level and a third-level authority level; the first-level authority level is higher than the second-level authority level, and the second-level authority level is higher than the third-level authority level.
[0007] Furthermore, the identity token attributes are obtained based on the mapping relationship between the virtual account and the random token generator; there are multiple mapping relationships, and the random token generator in each mapping relationship will generate and update the identity token every 3 minutes, and the token attribute processor will extract attributes of the corresponding identity token to obtain the identity token attributes; the number of random token generators is consistent with the number of virtual accounts, and each virtual account is randomly assigned to a random token generator.
[0008] Further, the verification based on the login data and the identity token attributes includes: a1: retrieve the account and password entered by the user in the login data; a2: Based on the account number and password input by the user, determine whether the account number and password belong to any virtual account associated with the physical account. If it is determined that the account number and password input by the user belong to any virtual account associated with the physical account, use the corresponding virtual account as the target virtual account and jump to step a3; otherwise, jump to step a4; a3: retrieve the login authentication data input by the user in the login data, retrieve the identity token attribute corresponding to the target virtual account, compare the login authentication data input by the user with the corresponding identity token attribute, if the login authentication data is inconsistent with the corresponding identity token attribute, jump to step a4; if the login authentication data is consistent with the corresponding identity token attribute, jump to step a5; a4: Do not allow the user to enter the management interface of the target virtual account; a5: Allows the user to enter the management interface of the target virtual account.
[0009] Furthermore, the second verification condition includes a transaction risk coefficient threshold, the transaction risk coefficient threshold is divided into a first transaction risk coefficient threshold and a second transaction risk coefficient threshold, and the first transaction risk coefficient threshold is greater than the second transaction risk coefficient threshold.
[0010] Furthermore, the use of a smart contract containing verification conditions to verify the compliance of a transaction request includes: b1: Obtain the transaction request initiated by the user and determine whether the transaction request meets the first verification condition. If yes, jump to step b2; if not, jump to step b5; b2: Obtain transaction log data and generate a transaction risk coefficient based on the transaction log data; The transaction log data includes transaction amount, daily transaction frequency, transaction user type, and transaction authority level of the target virtual account; b3: Compare the transaction risk coefficient with the transaction risk coefficient threshold in the second verification condition. If the transaction risk coefficient is greater than or equal to the first transaction risk coefficient threshold, jump to step b5; if the transaction risk coefficient is less than the first transaction risk coefficient threshold and greater than the second transaction risk coefficient threshold, jump to step b4; if the transaction risk coefficient is less than or equal to the second transaction risk coefficient threshold, jump to step b6; b4: Delay the transaction request and force the user to enter the identity token at the second target time, and determine the authenticity of the identity token at the second target time. If the identity token at the second target time is true, jump to step b6; if the identity token at the second target time is false, jump to step b5; b5: The transaction request is deemed non-compliant, the transaction request is cancelled, and the cancellation of the transaction request is used as the second verification result; b6: Determine that the transaction request is compliant, approve the transaction request, and use the approval of the transaction request as the first verification result.
[0011] Furthermore, the generation logic of the transaction risk coefficient is as follows: Define the amount risk function based on transaction log data , frequency risk function and user type risk function : ; ; ; Where: is the transaction amount, is the daily transaction frequency, d is the transaction user type, The trading permission level of the non-target virtual account; The amount risk function , frequency risk function and user type risk function The input will be into the pre-configured mathematical calculation model to obtain the transaction risk coefficient; The mathematical calculation model is expressed as follows: ; Where: is the transaction risk coefficient, e is a natural constant, , and is a weight factor greater than zero, .
[0012] Furthermore, the time interval between the first target time and the second target time is at least 3 minutes.
[0013] Furthermore, the blockchain storage module is used to temporarily cache the mapping relationship between each virtual account and the random token generator, as well as the identity token generated and updated in real time by the random token generator; the blockchain storage module is also used to store encrypted blocks of transaction risk coefficients and transaction forms.
[0014] Compared with the prior art, the present invention has the following beneficial effects: The present application discloses a virtual account transaction verification and recording system based on blockchain, including: obtaining login data when a user logs into a target virtual account, and recording the time when the user enters the target virtual account account number as a first target time; retrieving the corresponding identity token attribute according to the target virtual account, and verifying whether the user is allowed to enter the management interface of the target virtual account based on the login data and the identity token attribute; when the user enters the management interface and initiates a transaction request, using a smart contract containing verification conditions to verify the compliance of the transaction request and obtain a compliance verification result; used to send the transaction request to the registered bank of the entity account according to the first verification result, and generate a transaction form; based on the above technical features, the present invention can reduce the risk of shared accounts when multiple users share accounts, and maximize the management and control of the entity account owner over the shared account; in addition, by setting an effective transaction verification mechanism, the present invention can ensure the compliance of each user's transaction operation, which is conducive to effective supervision and management of funds flow, and further, it is conducive to effectively avoiding security issues such as misappropriation of special funds. BRIEF DESCRIPTION OF THE DRAWINGS
[0015] Figure 1 A module diagram of the blockchain-based virtual account transaction verification and recording system provided by the present invention. DETAILED DESCRIPTION
[0016] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.
[0017] Example 1 See also Figure 1 As shown, this embodiment discloses a virtual account transaction verification and recording system based on blockchain, the system includes a login monitoring module 110, an identity authentication module 120, a transaction verification module 130, a transaction generation module 140 and a blockchain storage module 150; wherein, The login monitoring module 110 is used to obtain login data when the user logs in to the target virtual account, and record the time when the user enters the target virtual account number as the first target time; the target virtual account is associated with the entity account, the entity account belongs to the special fund management node on the blockchain, the special fund management node associates a plurality of virtual accounts with different transaction authority levels for the entity account on the blockchain, and the target virtual account is the virtual account that performs the current login operation; It should be noted that: the type of the blockchain can be a public chain, a private chain or a consortium chain, or other types of blockchains, which are not particularly limited; the blockchain is a platform for special fund transaction management, and in addition to the special fund management node, the blockchain also includes nodes associated with the special fund management node, such as: elevator fire protection node, advertiser node, repair and maintenance node and community user node, etc.; the entity account is obtained based on the registration of the manager of the special fund management agency, and the special fund management agency is used to manage special funds, including but not limited to elevator fire protection special funds, house maintenance funds and income funds for managing public facilities and public services in the community (such as advertising income, etc.); for example, the special fund management agency is a community property, etc.; based on the entity account, it can be used for the special fund management agency to manage transactions of special funds, for example, if an advertiser rents a display board in the community for advertising display, the advertiser conducts a leasing transaction with the special fund management node belonging to the entity account through the advertiser node; The target virtual account is specifically one of the multiple virtual accounts associated with the physical account, which is determined according to the current login operation; for example, there are three virtual accounts Z1, Z2 and Z3. When the user enters the account number of Z2, the time when the Z2 account number is successfully entered is recorded as the first target time, and Z2 is used as the target virtual account; The login data includes the account number, password and login authentication data of the virtual account entered by the user; the login authentication data is specifically the identity token attribute entered by the user, the identity token attribute is associated and bound with the corresponding virtual account, and the identity token attribute includes but is not limited to the total length of the token, the number of character types contained in the token, the minimum ratio of character types, the maximum repetition ratio of the same character type, and the maximum number of consecutive same character types; Exemplarily, following the above assumptions, Z2 is the target virtual account, and the identity token associated with the target virtual account is "aaaB3$kMnZ5yP4s5"; it can be seen that the identity token attributes of "aaaB3$kMnZ5yP4s5" include: the total length of the token is 16, the number of character types contained in the token is 4 (i.e., including lowercase letters, uppercase letters, numbers and special characters), the minimum character type ratio is 1 / 16 (where there is only one special character "$"), the maximum repetition ratio of the same character type is 3 / 16 (where the lowercase letter "a" has the largest repetition ratio), and the maximum number of consecutive identical character types is 3 (where the number of consecutive lowercase letters "a" is the largest); Specifically, the transaction authority levels include the first level authority level, the second level authority level and the third level authority level; the first level authority level is higher than the second level authority level, and the second level authority level is higher than the third level authority level; wherein, the transaction limit of the first level authority level is more than 100,000 yuan (not including 100,000 yuan), the maximum daily transaction limit frequency is more than 10 times (not including 10 times), and the restricted transaction user type is a senior user; the transaction limit of the second level authority level is less than 100,000 yuan (including 100,000 yuan) and more than 50,000 yuan (not including 50,000 yuan), the maximum daily transaction limit frequency is less than 10 times (including 10 times) and more than 5 times (not including 5 times), and the restricted transaction user type is an intermediate user; the transaction limit of the third level authority level is less than 50,000 yuan (including 50,000 yuan), the maximum daily transaction limit frequency is less than 5 times (including 5 times), and the restricted transaction user type is a basic user; It should be understood that each of the virtual accounts uses 6 digits of administrative division + random digits (8 digits) + 2 digits of account classification, for example: 110000 (administrative division code of a city) 12345678 (random digits) 01 (2 digits of account classification); among which, the administrative division locks the area where the business is located, and the random digits generate an 8-digit code number through the data number of the business system according to the hash algorithm.
[0018] The identity authentication module 120 is used to retrieve the corresponding identity token attributes according to the target virtual account, and verify whether the user is allowed to enter the management interface of the target virtual account based on the login data and the identity token attributes; Specifically, the identity token attributes are obtained based on the mapping relationship between the virtual account and the random token generator; there are multiple mapping relationships, and the random token generator in each mapping relationship generates and updates the identity token every 3 minutes, and the token attribute processor extracts the attributes of the corresponding identity token to obtain the identity token attributes; the number of random token generators is consistent with the number of virtual accounts, and each virtual account is randomly assigned to a random token generator; It should be noted that: only one virtual account and a random token generator associated and bound to the virtual account are set in each mapping relationship; each mapping relationship between a virtual account and a random token generator is associated and bound in advance by a technician; the ownership and access rights of the random token generator belong only to the owner of the physical account; the token attribute processor is a program that executes fixed rules, which is developed and set in advance by a technician, and extracts attributes from the identity token according to a predetermined time limit (3 minutes) and predetermined extraction rules, so as to obtain and update the identity token attributes in real time; For example, based on the above assumptions, there are three virtual accounts Z1, Z2 and Z3, and it is assumed that there are three random token generators Y1, Y2 and Y3, and Z1 is associated and bound with Y1, Z2 is associated and bound with Y2, Z2 is associated and bound with Y2, and Z3 is associated and bound with Y3; when the virtual account number logged in by the user is Z3, and the first target time is 19:03, then Z3 is the target virtual account; therefore, based on Z3, the identity token generated by Y3 can be obtained, if Y3 is at 19:03 at the first target time If the generated identity token is "aaaB3$kMnZ5yP4s5" at the time of sharing, the attribute of "aaaB3$kMnZ5yP4s5" is used as the attribute of the identity token corresponding to the target virtual account; if it is assumed that the first target time of Z3 is 19:06, and the identity token generated by Y3 at the first target time of 19:06 is "bbbD7#pJrX2vN6u8", the attribute of "bbbD7#pJrX2vN6u8" is used as the attribute of the identity token corresponding to the target virtual account; In implementation, the verification based on login data and identity token attributes includes: a1: retrieve the account and password entered by the user in the login data; a2: Based on the account number and password input by the user, determine whether the account number and password belong to any virtual account associated with the physical account. If it is determined that the account number and password input by the user belong to any virtual account associated with the physical account, use the corresponding virtual account as the target virtual account and jump to step a3; otherwise, jump to step a4; It can be understood that: the physical account is associated with multiple virtual accounts with different transaction permission levels, and each virtual account has its own unique account number and password. If the account number and password entered by the user when logging in are different from any of the multiple virtual accounts associated with the physical account, the user identity is determined to be inconsistent; when it is determined to be inconsistent, it means that the current user has input login information or has violated regulations (such as brute force login, etc.); on the contrary, if the account number and password entered by the user when logging in are the same as any of the multiple virtual accounts associated with the physical account, the user identity is determined to be consistent; a3: retrieve the login authentication data input by the user in the login data, retrieve the identity token attribute corresponding to the target virtual account, compare the login authentication data input by the user with the corresponding identity token attribute, if the login authentication data is inconsistent with the corresponding identity token attribute, jump to step a4; if the login authentication data is consistent with the corresponding identity token attribute, jump to step a5; It can be understood that: when the login authentication data input by the user at login is different from the corresponding identity token attribute extracted by the token attribute processor (the corresponding identity token attribute is obtained by extracting the attribute of the identity token generated by the random token generator associated with the target virtual account), the user is not allowed to enter the management interface of the target virtual account. On the contrary, it is considered that the user has passed the two-factor authentication and the user is allowed to enter the management interface of the target virtual account. a4: Do not allow the user to enter the management interface of the target virtual account; a5: Allows the user to enter the management interface of the target virtual account; By setting up multiple virtual accounts and equipping each virtual account with a different random token generator, and performing explicit (i.e., the account number and password of the virtual account) and implicit (i.e., the identity token attributes) dual identity authentication without obtaining and disclosing the content generated by the random token generator, the present invention can reduce the risk of shared accounts and maximize the management and control of shared accounts by physical account owners.
[0019] The transaction verification module 130 is used to perform compliance verification on the transaction request using a smart contract containing verification conditions when the user enters the management interface and initiates a transaction request, and obtain a compliance verification result; the verification condition includes a first verification condition and a second verification condition; the compliance verification result includes a first verification result and a second verification result; The transaction request at least includes information such as the transaction amount, transaction object account, transaction time, transaction method and transaction business; wherein the transaction business has various types, for example, including advertising leasing or elevator maintenance; It should be noted that: the smart contract containing verification conditions is constructed and deployed by technicians who compile pre-defined rules (i.e., verification conditions) into smart contract codes; wherein, the first verification condition is a conventional trigger condition, which is determined according to the actual transaction business rules or the content of the actual transaction contract, including but not limited to payment method, payment time, payment conditions, and virtual accounts associated with physical accounts, etc.; Specifically, the second verification condition includes a transaction risk coefficient threshold, the transaction risk coefficient threshold is divided into a first transaction risk coefficient threshold and a second transaction risk coefficient threshold, the first transaction risk coefficient threshold is greater than the second transaction risk coefficient threshold, and the first transaction risk coefficient threshold and the second transaction risk coefficient threshold are specifically set by technicians in advance based on experiments or experience; In implementation, the use of a smart contract containing verification conditions to verify the compliance of a transaction request includes: b1: Obtain the transaction request initiated by the user and determine whether the transaction request meets the first verification condition. If yes, jump to step b2; if not, jump to step b5; b2: Obtain transaction log data and generate a transaction risk coefficient based on the transaction log data; The transaction log data includes transaction amount, daily transaction frequency, transaction user type, and transaction authority level of the target virtual account; It should be understood that the transaction log data is collected in real time by a third-party monitoring software built into the system platform or by a monitoring program pre-configured by the system; The generation logic of the transaction risk coefficient is as follows: Define the amount risk function based on transaction log data , frequency risk function and user type risk function : ; ; ; Where: is the transaction amount, is the daily transaction frequency, d is the transaction user type, The trading permission level of the non-target virtual account; For example, following the above assumptions, the virtual account number logged in by the user is Z3, and the first target time is 19:03, so Z3 is the user's login target virtual account, and it is assumed that the transaction authority level of Z3 is the third level authority level, and it is further assumed that the user performs a Z3 transaction operation on Z3, and the transaction amount initiated by the user in the transaction operation is 30,000 yuan, the daily transaction frequency has accumulated to 6 times, and the transaction user type is an intermediate user; therefore, combined with the above specific example content, it can be seen that the transaction amount belongs to the transaction limit of the third level authority level, but the daily transaction frequency does not belong to the maximum daily transaction limit frequency of the third level authority level, and the transaction user type does not belong to the restricted transaction user type of the third level authority level; The amount risk function , frequency risk function and user type risk function The input will be into the pre-configured mathematical calculation model to obtain the transaction risk coefficient; The mathematical calculation model is expressed as follows: ; Where: is the transaction risk coefficient, e is a natural constant, , and is a weight factor greater than zero, ; b3: Compare the transaction risk coefficient with the transaction risk coefficient threshold in the second verification condition. If the transaction risk coefficient is greater than or equal to the first transaction risk coefficient threshold, jump to step b5; if the transaction risk coefficient is less than the first transaction risk coefficient threshold and greater than the second transaction risk coefficient threshold, jump to step b4; if the transaction risk coefficient is less than or equal to the second transaction risk coefficient threshold, jump to step b6; b4: Delay the transaction request and force the user to enter the identity token at the second target time, and determine the authenticity of the identity token at the second target time. If the identity token at the second target time is true, jump to step b6; if the identity token at the second target time is false, jump to step b5; Specifically, the time interval between the first target time and the second target time is at least 3 minutes; Exemplarily, continuing with the above assumptions, Z3 is the target virtual account, Z3 is associated and bound with the random token generator Y3, and the identity token generated by Y3 at the first target time of 19:03 is "aaaB3$kMnZ5yP4s5"; assuming that a delayed transaction request occurs, the user will be forced to enter the identity token, and the time of entering the identity token will be recorded as the second target time. If the identity token entered by the user at the second target time is "aaaB3$kMnZ5yP4s5", it means that the time interval between the first target time and the second target time is less than 3 minutes, and the identity token is judged to be false, and it will not be passed, and the user is required to re-enter; if the identity token generated by Y3 at 19:06 is "bbbD7#pJrX2vN6u8", and the user enters "bbbD7#pJrX2vN6u8" between 19:06 and 19:09, the identity token at the second target time is judged to be true; b5: The transaction request is deemed non-compliant, the transaction request is cancelled, and the cancellation of the transaction request is used as the second verification result; b6: Determine that the transaction request is compliant, approve the transaction request, and use the approval of the transaction request as the first verification result; The transaction generation module 140 is used to send the transaction request to the registered bank of the entity account according to the first verification result and generate a transaction form; It should be noted that: when the transaction request is sent to the registered bank of the entity account according to the first verification result, it means that the transaction request passes through the smart contract, and the amount is transferred through the registered bank of the entity account, and a transaction form is generated, which at least includes the transaction time, transaction amount and transaction account of the two parties to the transaction; The blockchain storage module 150 is used to temporarily cache the mapping relationship between each virtual account and the random token generator, as well as the identity token generated and updated in real time by the random token generator; the blockchain storage module 150 is also used to store encrypted blocks of transaction risk coefficients and transaction forms; It should be noted that the data stored in the blockchain storage module 150 are all automatically encrypted, and the algorithm used for the automatic encryption includes but is not limited to asymmetric encryption, symmetric encryption or SHA-256, etc.; in addition, whether the transaction request is approved or cancelled, the system will hash the transaction risk coefficient and transaction form in the corresponding transaction record and upload them to the blockchain storage module 150; On the basis of double identity authentication, the transaction request is verified for compliance using a smart contract containing verification conditions, and the transaction risk coefficient and transaction form are uploaded to the blockchain for storage. The present invention can ensure the compliance of transaction operations when users trade through virtual accounts, and can effectively supervise and manage the flow of funds and abnormal transaction events, effectively avoiding security issues such as misappropriation of special funds. The above formulas are all dimensionless and numerical calculations. The formula is a formula for the most recent real situation obtained by collecting a large amount of data and performing software simulation. The preset parameters, weights and thresholds in the formula are set by technicians in this field according to actual conditions.
[0020] The above embodiments may be implemented in whole or in part by software, hardware, firmware or any other combination thereof. When implemented by software, the above embodiments may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, the process or function described in the embodiment of the present invention is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired network or a wireless network. The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more available media sets. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD) or a semiconductor medium. The semiconductor medium may be a solid-state hard disk.
[0021] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed in the present invention can be implemented in electronic hardware or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present invention.
[0022] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.
[0023] In the several embodiments provided by the present invention, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic, for example, the division of the units is only one, and there may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.
[0024] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
[0025] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
[0026] The above is only a specific embodiment of the present invention, but the protection scope of the present invention is not limited thereto. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed by the present invention, which should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention should be based on the protection scope of the claims.
[0027] Finally: The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the protection scope of the present invention.
Claims
1. A virtual account transaction verification and recording system based on blockchain, characterized in that: The system includes a login monitoring module, an identity authentication module, a transaction verification module, a transaction generation module and a blockchain storage module; wherein, A login monitoring module, used to obtain login data when a user logs in to a target virtual account, and record the time when the user enters the target virtual account number as a first target time; the target virtual account is associated with a physical account, the physical account belongs to a special fund management node on the blockchain, the special fund management node associates a plurality of virtual accounts with different transaction authority levels for the physical account on the blockchain, and the target virtual account is the virtual account that performs the current login operation; The identity authentication module is used to retrieve the corresponding identity token attributes according to the target virtual account, and verify whether the user is allowed to enter the management interface of the target virtual account based on the login data and the identity token attributes; A transaction verification module, which is used to perform compliance verification on the transaction request using a smart contract containing verification conditions when a user enters the management interface and initiates a transaction request, and obtain a compliance verification result; the verification condition includes a first verification condition and a second verification condition; the compliance verification result includes a first verification result and a second verification result; Wherein, the use of a smart contract containing verification conditions to verify the compliance of a transaction request includes: b1: Obtain the transaction request initiated by the user and determine whether the transaction request meets the first verification condition. If yes, jump to step b2; if not, jump to step b5; b2: Obtain transaction log data and generate a transaction risk coefficient based on the transaction log data; The transaction log data includes transaction amount, daily transaction frequency, transaction user type, and transaction authority level of the target virtual account; b3: Compare the transaction risk coefficient with the transaction risk coefficient threshold in the second verification condition. If the transaction risk coefficient is greater than or equal to the first transaction risk coefficient threshold, jump to step b5; if the transaction risk coefficient is less than the first transaction risk coefficient threshold and greater than the second transaction risk coefficient threshold, jump to step b4; if the transaction risk coefficient is less than or equal to the second transaction risk coefficient threshold, jump to step b6; b4: Delay the transaction request and force the user to enter the identity token at the second target time, and determine the authenticity of the identity token at the second target time. If the identity token at the second target time is true, jump to step b6; if the identity token at the second target time is false, jump to step b5; b5: The transaction request is deemed non-compliant, the transaction request is cancelled, and the cancellation of the transaction request is used as the second verification result; b6: Determine that the transaction request is compliant, approve the transaction request, and use the approval of the transaction request as the first verification result; The transaction generation module is used to send the transaction request to the registered bank of the entity account according to the first verification result and generate a transaction form.
2. The blockchain-based virtual account transaction verification and recording system according to claim 1, characterized in that: The login data includes the account number, password and login authentication data of the virtual account entered by the user; the login authentication data is specifically the identity token attribute entered by the user; The transaction authority levels include a first-level authority level, a second-level authority level and a third-level authority level; the first-level authority level is higher than the second-level authority level, and the second-level authority level is higher than the third-level authority level.
3. The blockchain-based virtual account transaction verification and recording system according to claim 2, characterized in that: The identity token attributes are obtained based on the mapping relationship between the virtual account and the random token generator; there are multiple mapping relationships, and the random token generator in each mapping relationship generates and updates the identity token every 3 minutes, and the token attribute processor extracts the attributes of the corresponding identity token to obtain the identity token attributes; The number of random token generators is consistent with the number of virtual accounts, and each virtual account is randomly assigned to a random token generator.
4. The blockchain-based virtual account transaction verification and recording system according to claim 3, characterized in that: The verification based on login data and identity token attributes includes: a1: retrieve the account and password entered by the user in the login data; a2: Based on the account number and password input by the user, determine whether the account number and password belong to any virtual account associated with the physical account. If it is determined that the account number and password input by the user belong to any virtual account associated with the physical account, use the corresponding virtual account as the target virtual account and jump to step a3; otherwise, jump to step a4; a3: retrieve the login authentication data input by the user in the login data, retrieve the identity token attribute corresponding to the target virtual account, compare the login authentication data input by the user with the corresponding identity token attribute, if the login authentication data is inconsistent with the corresponding identity token attribute, jump to step a4; if the login authentication data is consistent with the corresponding identity token attribute, jump to step a5; a4: Do not allow the user to enter the management interface of the target virtual account; a5: Allows the user to enter the management interface of the target virtual account.
5. The blockchain-based virtual account transaction verification and recording system according to claim 4, characterized in that: The second verification condition includes a transaction risk coefficient threshold, the transaction risk coefficient threshold is divided into a first transaction risk coefficient threshold and a second transaction risk coefficient threshold, and the first transaction risk coefficient threshold is greater than the second transaction risk coefficient threshold.
6. The blockchain-based virtual account transaction verification and recording system according to claim 5, characterized in that: The generation logic of the transaction risk coefficient is as follows: Define the amount risk function based on transaction log data , frequency risk function and user type risk function : ; ; ; Where: is the transaction amount, is the daily transaction frequency, d is the transaction user type, The trading permission level of the non-target virtual account; The amount risk function , frequency risk function and user type risk function The input will be into the pre-configured mathematical calculation model to obtain the transaction risk coefficient; The mathematical calculation model is expressed as follows: ; Where: is the transaction risk coefficient, e is a natural constant, , and is a weight factor greater than zero, .
7. The blockchain-based virtual account transaction verification and recording system according to claim 6, characterized in that: The time interval between the first target time and the second target time is at least 3 minutes.
8. The blockchain-based virtual account transaction verification and recording system according to claim 7, characterized in that: The blockchain storage module is used to temporarily cache the mapping relationship between each virtual account and the random token generator, as well as the identity token generated and updated in real time by the random token generator; the blockchain storage module is also used to store encrypted blocks of transaction risk coefficients and transaction forms.
Citation Information
Patent Citations
Corporate account client transaction limiting method and device based on block chain
CN113469668A
Operation behavior monitoring method and device, equipment and medium
CN113487430A
Block chain-based cross-border transaction collection method and device
CN114926161A
Transaction control method and system based on bank intelligent counter and storage medium
CN115907772A
E-commerce platform transaction risk assessment method and system based on artificial intelligence
CN117934043A
Cited By
Multi-factor identity verification method applied to security transaction
CN119228383A
Block chain-based separate account settlement method
CN119762250A
