A rights management method, device and computer-readable storage medium
By conducting risk assessment and dynamic permission management on transaction data, the existing transaction permission management methods are solved, and the transaction security and difficulty of cracking users are improved.
Patent Information
- Application Number
- CN202110034907.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2021-01-12
- Publication Date
- 2024-11-22
- Estimated Expiration
- 2041-01-12
AI Technical Summary
The existing transaction permission management methods are based on fixed conditions, with a low threshold and easy to be cracked, resulting in reduced transaction security.
By receiving permission application requests for user identification, obtaining transaction data, determining characteristic data under the transaction risk dimension, conducting risk assessment, determining transaction security level based on the evaluation results, and dynamically granting transaction permissions.
It improves the security of transaction permission management, increases the difficulty of cracking users in black industry, and improves the real-time and accuracy of transaction security levels.
Smart Images

Figure CN112749973B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of communication technology, and in particular to a rights management method, device and computer-readable storage medium. Background Art
[0002] In recent years, with the rapid development of Internet technology, online transactions have become more and more convenient. Trading permissions are required to conduct transactions online, and trading permissions are directly related to the financial security of users. Therefore, trading permissions need to be managed. Existing permission management is mainly managed through fixed permission granting conditions such as transaction time.
[0003] In the process of research and practice of the prior art, the inventor of the present invention found that the threshold of the existing fixed permission granting conditions such as transaction time is low and easy to crack, which makes the transaction risky and thus reduces the security of permission management. Summary of the invention
[0004] The embodiments of the present invention provide a rights management method, device and computer-readable storage medium, which can improve the security of transaction rights management.
[0005] A permission management method, comprising:
[0006] Receive a permission application request for a target transaction permission, wherein the permission application request carries a user identifier;
[0007] According to the permission application request, obtaining transaction data corresponding to the user identifier;
[0008] Determining transaction feature data under multiple transaction risk dimensions from the transaction data, and performing risk assessment on the user identifier under the transaction risk dimensions based on the transaction feature data;
[0009] Determining the transaction security level of the user identification according to the risk assessment result;
[0010] Based on the transaction security level, the target transaction authority is assigned to the user identification.
[0011] Accordingly, an embodiment of the present invention provides a rights management device, including:
[0012] A receiving unit, configured to receive a permission application request for a target transaction permission, wherein the permission application request carries a user identifier;
[0013] An acquisition unit, configured to acquire transaction data corresponding to the user identifier according to the permission application request;
[0014] an evaluation unit, configured to determine transaction feature data under a plurality of transaction risk dimensions from the transaction data, and perform risk evaluation on the user identifier under the transaction risk dimensions based on the transaction feature data;
[0015] A determination unit, configured to determine a transaction security level of the user identification according to a risk assessment result;
[0016] The granting unit is used to grant the target transaction authority to the user identification based on the transaction security level.
[0017] Optionally, in some embodiments, the evaluation unit can be specifically used to filter out transaction data of a preset time unit from the transaction data to obtain basic transaction data; perform data cleansing on the basic transaction data to obtain cleansed transaction data; and determine transaction feature data under multiple transaction risk dimensions in the cleansed transaction data.
[0018] Optionally, in some embodiments, the evaluation unit can be specifically used to obtain transaction risk dimension information corresponding to the target transaction authority; determine the data type corresponding to each transaction risk dimension based on the transaction risk dimension information; and based on the data type, filter out transaction feature information corresponding to the multiple transaction risk dimensions in the cleaned transaction data.
[0019] Optionally, in some embodiments, the evaluation unit can be specifically used to determine the evaluation items of the risk assessment according to the type of the transaction risk dimension; based on the evaluation items, perform risk assessment on the transaction feature data to obtain an initial risk assessment result of the user identifier under the transaction dimension; and fuse the initial risk assessment results to obtain the risk assessment result.
[0020] Optionally, in some embodiments, the evaluation unit can be specifically used to, when the evaluation project is a transaction behavior evaluation, use a preset transaction behavior evaluation model to perform risk evaluation on the transaction behavior data to obtain the initial risk evaluation result; when the evaluation project is a transaction scenario evaluation, use a preset transaction scenario evaluation model to perform risk evaluation on the transaction scenario data to obtain the initial risk evaluation result; when the evaluation project is a suspicious transaction data evaluation, use a preset suspicious transaction data evaluation model to perform risk evaluation on the suspicious transaction data to obtain the initial risk evaluation result.
[0021] Optionally, in some embodiments, the evaluation unit can be specifically used to classify the transaction behavior data according to the transaction behavior type; based on the classification result, perform feature extraction on the transaction behavior data to obtain transaction behavior features; use the preset transaction behavior evaluation model to perform risk assessment on the transaction behavior features to obtain the initial risk assessment result.
[0022] Optionally, in some embodiments, the evaluation unit can be specifically used to classify the transaction scenario data according to the transaction scenario type; based on the classification result, perform text recognition on the transaction scenario data to obtain the text content corresponding to each transaction scenario type; use a preset transaction scenario evaluation model to perform risk assessment on the text content to obtain the scenario risk assessment result corresponding to each scenario type; and fuse the scenario risk assessment results to obtain the initial risk assessment result.
[0023] Optionally, in some embodiments, the determination unit can be specifically used to use a preset rating model to extract features of multiple dimensions for the risk assessment results to obtain transaction security features of multiple dimensions; fuse the transaction security features to obtain global transaction security features of the user identifier; and determine the transaction security level of the user identifier based on the global transaction security features.
[0024] Optionally, in some embodiments, the granting unit may be specifically used to identify basic user information corresponding to the user identifier in the transaction data; and grant the target transaction authority to the user identifier according to the basic user information and the transaction security level.
[0025] Optionally, in some embodiments, the granting unit can be specifically used to detect the basic user information according to a preset detection strategy; compare the transaction security level with a preset transaction security level threshold; when the basic user information detection passes and the transaction security level is not lower than the preset transaction security level threshold, grant the target transaction authority to the user identifier.
[0026] Optionally, in some embodiments, the assigning unit can be specifically used to obtain the transaction time corresponding to the user identifier in the transaction time information, and compare the transaction time with a preset transaction time threshold; match the user identity information with the preset risk identity information; when the transaction time is not lower than the preset transaction time threshold, and the user identity information does not match the preset risk identity information, determine that the basic user information detection has passed.
[0027] Optionally, in some embodiments, the assigning unit can be specifically used to identify the total transaction time and normal transaction time corresponding to the user identifier in the transaction time, the total transaction time being the total time since the user corresponding to the user identifier opened the transaction service, and the normal transaction time being the duration of continuous transactions of transaction events that meet the normal transaction status; comparing the total transaction time with the preset total transaction time threshold, and comparing the normal transaction time with the preset normal transaction time threshold; when the total transaction time is not less than the preset total transaction time threshold, or the normal transaction time is not less than the preset normal transaction time threshold, determining that the transaction time is not less than the transaction time threshold.
[0028] Optionally, in some embodiments, the acquisition unit can be specifically used to determine at least one transaction data type corresponding to the target transaction authority based on the authority application request; filter out transaction data corresponding to the transaction data type in a preset transaction data set to obtain a candidate transaction data set; and identify transaction data corresponding to the user identifier in the candidate transaction data set.
[0029] In addition, an embodiment of the present invention further provides an electronic device, including a processor and a memory, wherein the memory stores an application program, and the processor is used to run the application program in the memory to implement the permission management method provided by the embodiment of the present invention.
[0030] In addition, an embodiment of the present invention further provides a computer-readable storage medium, which stores a plurality of instructions, and the instructions are suitable for a processor to load to execute the steps in any one of the rights management methods provided in the embodiments of the present invention.
[0031] After receiving a permission application request for a target transaction permission, the embodiment of the present invention carries a user identifier. Then, according to the permission application request, the transaction data corresponding to the user identifier is obtained, transaction feature data under multiple transaction risk dimensions are determined in the transaction data, and risk assessment is performed on the user identifier under the transaction risk dimension based on the transaction feature data. Then, according to the risk assessment result, the transaction security level of the user identifier is determined, and based on the transaction security level, the target transaction permission is granted to the user identifier. Since the scheme performs a risk assessment on the user corresponding to the user identifier and determines the transaction security level of the user according to the assessment result, and uses the transaction security level as a condition for granting transaction permissions, the threshold for applying for transaction permissions is raised, and the transaction security level is assessed in real time, thereby greatly increasing the difficulty for black market users to crack transaction permissions. Therefore, the security of permission management can be improved. BRIEF DESCRIPTION OF THE DRAWINGS
[0032] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative work.
[0033] Figure 1 is a schematic diagram of a scenario of rights management provided by an embodiment of the present invention;
[0034] Figure 2 It is a flowchart of a rights management method provided by an embodiment of the present invention;
[0035] Figure 3 It is a schematic diagram of evaluating transaction behavior data using a preset transaction behavior evaluation model provided by an embodiment of the present invention;
[0036] Figure 4 is a schematic diagram of evaluating transaction scenario data using a preset transaction scenario evaluation model provided by an embodiment of the present invention;
[0037] Figure 5 is a rating diagram of transaction security levels provided by an embodiment of the present invention;
[0038] Figure 6 is a schematic diagram of a process of granting target transaction authority provided by an embodiment of the present invention;
[0039] Figure 7 It is a structural diagram of a data sharing system for applying a rights management device to a blockchain provided by an embodiment of the present invention;
[0040] Figure 8 is another flow chart of the rights management method provided by an embodiment of the present invention;
[0041] Fig. 9 It is a schematic diagram of the structure of the blockchain provided by an embodiment of the present invention;
[0042] Fig.10 It is a schematic diagram of the process of generating a new block in the blockchain provided by an embodiment of the present invention;
[0043] Fig.11 It is a schematic diagram of the structure of a rights management device provided by an embodiment of the present invention;
[0044] Fig.12 It is a schematic diagram of the structure of an electronic device provided by an embodiment of the present invention. DETAILED DESCRIPTION
[0045] 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 those skilled in the art without creative work are within the scope of protection of the present invention.
[0046] The embodiment of the present invention provides a rights management method, device and computer-readable storage medium. The rights management device can be integrated in an electronic device, which can be a server or a terminal.
[0047] Among them, the server can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, network acceleration services (Content Delivery Network, CDN), and basic cloud computing services such as big data and artificial intelligence platforms. The terminal can be a smart phone, tablet computer, laptop computer, desktop computer, smart speaker, smart watch, etc., but is not limited to this. The terminal and the server can be directly or indirectly connected via wired or wireless communication, and this application does not limit this.
[0048] For example, see Figure 1 Taking the integration of the permission management device in an electronic device as an example, after the electronic device receives the permission application request for the target transaction permission, the permission application request carries the user identification, and then, according to the permission application request, the transaction data corresponding to the user identification is obtained, and transaction feature data under multiple transaction risk dimensions are determined in the transaction data, and based on the transaction feature data, the user identification is risk assessed under the transaction risk dimension, and then, based on the risk assessment result, the transaction security level of the user identification is determined, and based on the transaction security level, the target transaction permission is granted to the user identification.
[0049] Among them, the transaction authority can be the authority for users to conduct transactions, for example, it can be the payment authority for users to make payments, and it can also be the collection authority for users to collect payments. Users can be divided into individual users and merchants. When the user is a merchant, the merchant's payment authority can be corporate payment capability, which can be understood as a collection capability specifically used in B2C (Business-to-Consumer) transaction scenarios using mobile payment. The corporate payment product corresponding to the collection capability can be a means for merchant B who conducts transactions through mobile payment to actively issue a series of benefits / benefits to user C through the corporate payment product corresponding to the corporate payment capability, for example, it can actively issue coupons for promotions, actively issue cash red envelopes for rebates, actively issue cash to personal mobile payment accounts for refunds, and can also issue cash to personal mobile payment accounts for withdrawal (withdraw to the personal mobile payment account of the merchant user), etc.
[0050] Among them, the transaction risk dimension can be a dimension in which transaction risks exist. For example, the transaction risk dimension can be a dimension in which risks exist in transaction behavior, and the transaction risk dimension can be a transaction behavior risk dimension. It can also be a dimension in which risks exist in transaction scenarios, and the transaction risk dimension can be a transaction scenario risk dimension. It can also be a dimension in which risks exist in suspicious transaction data, and the transaction risk dimension can be a suspicious transaction data risk dimension, etc.
[0051] It should be noted that the description order of the following embodiments is not intended to limit the preferred order of the embodiments.
[0052] This embodiment will be described from the perspective of a rights management device, which can be specifically integrated into an electronic device, which can be a server or a terminal. The terminal can include a tablet computer, a laptop computer, a personal computer (PC), a wearable device, a virtual reality device, or other smart devices that can perform rights management.
[0053] A permission management method, comprising:
[0054] After receiving the permission application request for the target transaction permission, the permission application request carries the user ID. According to the permission application request, the transaction data corresponding to the user ID is obtained, and the transaction feature data under multiple transaction risk dimensions are determined in the transaction data. Based on the transaction feature data, the user ID is subjected to risk assessment under the transaction risk dimension. According to the risk assessment result, the transaction security level of the user ID is determined, and based on the transaction security level, the target transaction permission is granted to the user ID.
[0055] like Figure 2 As shown, the specific process of the permission management method is as follows:
[0056] 101. Receive a permission application request for a target transaction permission.
[0057] The permission application request carries a user identifier, and the so-called user identifier may be an identity identifier of an individual user, such as a transaction account number, or an identifier of a merchant's merchant account number.
[0058] For example, a permission application request for the target transaction permission directly sent by the terminal can be directly received. For example, a user triggers a permission application request for the target transaction permission through the terminal, adds a user ID to the permission application request, and the terminal sends the permission application request with the added user ID to the permission management device. When there are batch applications for target transaction permissions for users corresponding to multiple user IDs, the user ID can also be obtained indirectly. For example, the terminal stores the user ID, adds the storage address to the permission application request for the target transaction permission, and then sends the permission application request carrying the storage address to the permission management device. The permission management device obtains the storage address in the permission application request, and obtains the user ID in the terminal's memory or cache according to the storage address.
[0059] 102. According to the permission application request, obtain the transaction data corresponding to the user ID.
[0060] Among them, transaction data can be data generated in transaction services or transaction behaviors. The transaction data may include the user's own transaction-related data, data evaluated by a third-party organization on the user's transaction, and data assisting the transaction.
[0061] For example, based on the permission application request, at least one transaction data type corresponding to the target transaction permission can be determined. For example, a preset transaction data type set is obtained, and at least one transaction data type corresponding to the target transaction permission is screened out from the preset transaction data type set. For example, taking the target transaction permission as the enterprise payment permission as an example, the important data types for risk assessment corresponding to the enterprise payment permission can include manual review data of manual reviews of merchants, real-time transaction flow data of real-time transactions of merchants, associated text data consistent with merchant static information, black clues for merchants to be excluded by external structures, and other suspicious data.
[0062] Filter out transaction data corresponding to the transaction data type in the preset transaction data set to obtain a candidate transaction data set. For example, taking the transaction data type including manual review data, real-time transaction flow data, associated text data and other suspicious data as an example, filter out these types of data in the preset transaction data set to obtain a candidate transaction data set, which can include a manual review data subset, a real-time transaction data subset, an associated text data subset and other suspicious data subsets. The manual review data subset may include key information such as whether the manual review merchant is normal / malicious, as well as text information such as the merchant's transaction scenario. The real-time transaction data subset may include the merchant's real-time transaction flow record, which describes the merchant's transaction information. The associated text data subset may include text data such as the merchant's associated public account and complaint information, and the other suspicious data subset may include suspicious data such as black clue data accessed by other external organizations.
[0063] Transaction data corresponding to the user identifier is identified in the candidate transaction data set. For example, taking the candidate transaction data set including a manual review data subset, a real-time transaction data subset, an associated text data subset, and other suspicious data subsets, the manual review data, real-time transaction data, associated text data, and other suspicious data corresponding to the user identifier can be screened out in the manual review data subset to obtain the transaction data corresponding to the user identifier, wherein the other suspicious data corresponding to the user identifier may be other suspicious data corresponding to the user type of the user identifier, other suspicious data corresponding to the time period during which the user corresponding to the user identifier has transaction behavior, and other suspicious data directly corresponding to the user identifier.
[0064] 103. Determine transaction feature data under multiple transaction risk dimensions from the transaction data, and perform risk assessment on the user identifier under the transaction risk dimension based on the transaction feature data.
[0065] For example, the transaction data may be cleaned, and transaction feature data under multiple transaction risk dimensions may be determined from the cleaned transaction data. Based on the transaction feature data, the user identification may be risk assessed under the transaction risk dimension, as follows:
[0066] S1. Determine transaction feature data under multiple transaction risk dimensions in the transaction data.
[0067] Among them, the transaction feature data can be feature data used for risk assessment of user identification under the transaction risk dimension. For example, taking the transaction risk dimension as the transaction behavior risk dimension where the transaction behavior has risks as an example, the transaction feature data under the transaction risk dimension can be the real-time transaction flow data and associated text data corresponding to the user identification. The transaction feature data under different transaction risk dimensions are different, but the same data can exist in the transaction feature data under different transaction risk dimensions. For example, both the transaction behavior risk dimension and the transaction scenario risk dimension can include associated text data. There may not be any same data in the transaction feature data under different transaction risk dimensions.
[0068] For example, the transaction data of the preset time unit is filtered out from the transaction data to obtain the basic transaction data. For example, the preset time unit can be the time interval from the user ID opening the transaction service to the day before applying for the target transaction authority. The transaction data within the time interval can be filtered out from the transaction data to obtain the basic transaction data corresponding to the user ID. The basic transaction data is cleaned to obtain the cleaned transaction data. For example, data cleaning can include checking data consistency, processing invalid values and missing values, etc. Therefore, the data cleaning of the basic transaction data can be to check the consistency of the data in the basic transaction data and process the invalid values and missing values in the basic transaction data to obtain the cleaned transaction data, and then the standard data can be obtained, and the standard data is used as the cleaned transaction data.
[0069] Transaction feature data under multiple transaction risk dimensions are determined in the cleaned transaction data. For example, the transaction risk dimension information corresponding to the target transaction authority is obtained, and the transaction risk dimension information user indicates at least one transaction risk dimension corresponding to the target transaction authority. According to the transaction risk dimension information, the data type of each transaction risk dimension is determined. For example, according to the transaction risk dimension information, at least one transaction risk dimension corresponding to the target transaction authority can be determined. The data type corresponding to the transaction risk dimension is screened out from the preset data type set. For example, when the transaction risk dimension is the transaction behavior risk dimension, the data type corresponding to the transaction risk dimension can be real-time transaction flow data and associated text data. When the transaction risk dimension is the transaction scenario risk dimension, the data type corresponding to the transaction risk dimension can be associated text data and other transaction data. When the transaction risk dimension is the suspicious transaction data risk dimension, the data type corresponding to the transaction risk dimension can be manual review data and other transaction data. Based on the data type, the transaction feature data corresponding to multiple transaction risk dimensions are screened out in the cleaned transaction data. For example, taking the transaction risk dimension as the transaction behavior risk dimension as an example, the real-time transaction flow data and associated text data can be screened out in the cleaned transaction data, and the real-time transaction flow data and associated text data are used as the transaction feature information corresponding to the transaction behavior risk dimension. The transaction characteristic data under other risk dimensions can be obtained by adopting the same method to obtain the transaction characteristic data under each transaction risk dimension.
[0070] S2. Based on the transaction feature data, a risk assessment is performed on the user ID under the transaction risk dimension.
[0071] Among them, risk assessment can be understood as an assessment of the risks existing in the user identification under the transaction risk dimension, and the assessment method can be scoring, rating or other assessment methods.
[0072] For example, the risk assessment items can be determined according to the transaction risk dimension, and the transaction feature data can be risk assessed based on the assessment items to obtain the initial risk assessment results of the user identification under the transaction dimension. The initial risk assessment results are integrated to obtain the risk assessment results, which can be specifically as follows:
[0073] (1) Determine the risk assessment items based on the transaction risk dimensions.
[0074] For example, a set of preset evaluation items corresponding to the target transaction authority can be obtained, and the evaluation items corresponding to the transaction risk dimension can be screened out from the preset evaluation item set. For example, when the transaction risk dimension is a transaction behavior risk dimension, the evaluation item corresponding to the transaction risk dimension can be a transaction behavior evaluation; when the transaction risk dimension is a transaction scenario risk dimension, the evaluation item corresponding to the transaction risk dimension can be a transaction scenario evaluation; when the transaction risk dimension is a suspicious transaction data risk dimension, the evaluation item corresponding to the transaction risk dimension can be a suspicious transaction data evaluation.
[0075] (2) Based on the assessment items, a risk assessment is performed on the transaction feature data to obtain an initial risk assessment result of the user ID under the transaction dimension.
[0076] Among them, transaction characteristic data may include transaction behavior data, transaction scenario data and suspicious transaction data. The so-called transaction behavior data may be transaction characteristic data under the transaction behavior risk dimension, the transaction scenario data may be transaction characteristic data under the transaction scenario risk dimension, and the suspicious transaction data may be transaction characteristic data under the suspicious transaction data risk dimension.
[0077] For example, when the assessment project is a transaction behavior assessment, a preset transaction behavior assessment model is used to conduct a risk assessment on the transaction behavior data to obtain an initial risk assessment result. When the assessment project is a transaction scenario assessment, a preset transaction scenario assessment model is used to conduct a risk assessment on the transaction scenario data to obtain an initial risk assessment result. When the assessment project is a suspicious transaction data assessment, a preset suspicious transaction data assessment model is used to conduct a risk assessment on the suspicious transaction data to obtain an initial risk assessment result. The specific results may be as follows:
[0078] C1. When the assessment project is a transaction behavior assessment, a preset transaction behavior assessment model is used to conduct risk assessment on the transaction behavior data to obtain an initial risk assessment result.
[0079] Among them, the preset transaction behavior evaluation model may include multiple evaluation sub-models, and the evaluation sub-model may include an account maintenance evaluation model, a white merchant evaluation model, and a subject transaction evaluation model. The evaluation sub-model may be a multi-classification model, etc. The account maintenance evaluation model is used to evaluate whether the user corresponding to the user ID has the account maintenance merchant behavior characteristics. The account maintenance merchant behavior characteristics may be a small number of low-amount transactions per day, for example, a transaction of 1 cent per day, or a single transaction scenario, for example, all jsapi (a transaction method) transactions, or a single transaction counterparty, for example, 5 consecutive days are all related transactions with the same Class C account, or the number of consecutive transaction days is only the minimum requirement, for example, only 30 consecutive days of transactions. The account maintenance merchant behavior characteristics are used to indicate that the user ID has the behavior characteristics of black industry account maintenance. The so-called account maintenance is the operation behavior of a black industry user (a black industry user used for evil) to operate a user ID so that the user ID has certain permissions. The white merchant model is used to evaluate whether the user ID corresponds to white merchant behavior characteristics. White merchant behavior characteristics can be frequent transactions, transactions mainly concentrated between 08:00 and 23:00, diversified counterparties, or other behavior characteristics of normal users. White merchant behavior characteristics are used to indicate that the user ID is a behavior characteristic of a normal user. The subject transaction evaluation model is used to identify whether the user corresponding to the user ID has other transaction subjects (transaction users) with similar transaction behaviors. It mainly evaluates whether the user ID has similar transaction behavior characteristics with other user IDs of the subject. It can also be used to evaluate whether the user ID has no obvious transaction behavior similarity with other user IDs of the subject and other subject transaction characteristics.
[0080] For example, transaction behavior data is classified according to the transaction behavior type. For example, transaction behavior data can be divided into transaction time data, transaction object data, transaction frequency data or transaction amount data. Based on the classification result, feature extraction is performed on the transaction behavior data to obtain transaction behavior features corresponding to each transaction behavior type. For example, feature extraction is performed on transaction time data, transaction object data, transaction frequency data or transaction amount data to obtain account-maintaining merchant behavior features, white merchant behavior features and subject similar transaction behavior features, etc., which are used as transaction behavior features. By using the account maintenance assessment model to perform risk assessment on the account maintenance merchant behavior features, the account maintenance assessment result of the user identification can be obtained. By using the white merchant assessment model to perform risk assessment on the white merchant behavior features, the white merchant assessment result of the user identification can be obtained. By using the subject transaction assessment model to obtain the similarity assessment result of the user identification, the specific example is as follows. Figure 3 The account maintenance assessment results, white merchant assessment results and similarity assessment results are used as the initial risk assessment results of user identification.
[0081] Among them, when the account maintenance assessment model conducts risk assessment on the behavioral characteristics of account maintenance merchants, if the assessment result shows that the user ID is likely to have account maintenance behavior, it can be fed back to the trading platform, and the trading platform can handle the user corresponding to the user ID as a suspicious user during the process.
[0082] C2. When the assessment project is a transaction scenario assessment, a preset transaction scenario assessment model is used to conduct risk assessment on the transaction scenario data to obtain an initial risk assessment result.
[0083] Among them, the preset transaction scenario evaluation model can also be called an associated scenario recognition model, which is mainly used to identify the real transaction scenario of the user identity through some transaction channels or other transaction information associated with the user identity, and perform multi-scenario evaluation on the identified transaction scenario. The transaction scenario data used to identify the transaction scenario can be the data of the user corresponding to the mini program, public account or user identity on the network associated with the user identity. The preset transaction scenario evaluation model can also include multiple evaluation sub-models for different transaction scenarios, for example, it can include an application (App) evaluation model, an application ID evaluation model and a user public opinion evaluation model. The App evaluation model is mainly used to identify and evaluate the scenario associated with the user identity through the APP text information, and the AppID evaluation model identifies and evaluates the scenario associated with the ID of the user identity through the AppID text information. For example, it can identify and evaluate the scenario corresponding to the text information of the public account corresponding to the user identity. The user public opinion evaluation model is mainly used to obtain the text information of the public opinion information of the user identity from the network to identify the corresponding scenario and evaluation, and is used to evaluate whether there is similarity with other user identities that are similar to the user identity.
[0084] For example, transaction scenario data is classified according to the transaction scenario type. For example, transaction scenario data can be divided into App text data in App scenario, AppID text data in AppID scenario, and public opinion data corresponding to user identification in user public opinion scenario. App text data can be data corresponding to text information of App associated with user identification in transaction behavior, for example, data corresponding to configuration information and attribute information of App. AppID text data can be information of identity identification of user identification in APP, for example, data corresponding to text information of WeChat public account. Public opinion information corresponding to user identification can be data corresponding to public opinion of user identification on the Internet, for example, webpage of user identification crawled from the Internet. Based on the classification results, text recognition is performed on transaction scenario data to obtain text content corresponding to each transaction scenario type. For example, text recognition can be performed on App text data to obtain APP text content, recognition can be performed on AppID text data to obtain AppID text content, and text recognition can be performed on public opinion data corresponding to user identification to obtain public opinion text content of public opinion corresponding to user identification. Use the preset transaction scenario assessment model to conduct risk assessment on the text content to obtain the scenario risk assessment results corresponding to each scenario type. For example, use the App assessment model to conduct risk assessment on the App text content to obtain the App risk assessment result. Use the AppID assessment model to conduct risk assessment on the AppID text content to obtain the AppID risk assessment result. Use the user public opinion assessment model to conduct risk assessment on the public opinion text content to obtain the public opinion risk assessment result. The public opinion risk assessment result can be the similarity assessment result of the public opinion of the user ID and other user IDs. When the assessment is in the form of scoring, use the preset transaction scenario assessment model to conduct risk assessment on the transaction scenario data to obtain the initial risk assessment result, which can be as follows: Figure 4 The initial risk assessment results are integrated to obtain the risk assessment results. For example, taking the assessment form as a score, the multi-scenario score and the similarity score are integrated to obtain the initial risk assessment result.
[0085] C3. When the assessment project is a suspicious transaction data assessment, a preset suspicious transaction data assessment model is used to conduct a risk assessment on the suspicious transaction data to obtain an initial risk assessment result.
[0086] Among them, the preset suspicious transaction data evaluation model can be used to evaluate whether the user identifier is a suspicious user, whether it is a user in a suspicious community, or whether there is suspicious public opinion information, etc. Therefore, the preset suspicious transaction data evaluation model can include multiple sub-evaluation models according to the evaluation type, for example, it can include a black material identification model and other auxiliary models, and other auxiliary models can include a suspicious community mining model and a public opinion mining model, etc. The so-called black material identification model can be some data that is manually reviewed, and the historical user identifier that is manually reviewed and judged as black industry is associated with the mobile phone number and bank card information corresponding to the black industry user, so as to evaluate whether the user identifier is a suspicious user and obtain a black industry evaluation result. The suspicious community mining model can be used to mine the community that has an association relationship with the user identifier, and determine whether the mined community is a suspicious community, and obtain a suspicious community evaluation result. The public opinion mining model can be used to mine the public opinion information that has an association relationship with the user identifier, and determine whether there is suspicious public opinion information in the public opinion information, for example, whether the user identifier has suspicious public opinion information such as being punished or reported on the Internet, and obtain a suspicious public opinion evaluation result.
[0087] For example, when the assessment project is suspicious transaction data assessment, the black material identification model is used to identify suspicious transaction data, and the user ID is evaluated to see if it is a suspicious user based on the identification result, and a black industry assessment result is obtained. The suspicious community mining model is used to identify suspicious transaction data, and the community associated with the user ID is evaluated to see if it is a suspicious community based on the identification result, and a suspicious community assessment result is obtained. The public opinion mining model is used to identify suspicious transaction data, and the user ID is evaluated to see if there is suspicious public opinion information based on the identification result, and a suspicious public opinion assessment result is obtained. The black industry assessment results, suspicious community assessment results, and suspicious public opinion assessment results are integrated to obtain the initial risk assessment result.
[0088] It should be noted that the evaluation sub-model for risk assessment of transaction feature data can be a scorecard model or a neural network model, and the evaluation sub-model can be increased or decreased according to actual applications.
[0089] (3) The initial risk assessment results are integrated to obtain the risk assessment results.
[0090] For example, the risk assessment result can be obtained by weighting the initial risk results. For example, the assessment weight corresponding to each transaction risk dimension is obtained, and the initial risk assessment result corresponding to each transaction risk dimension is weighted according to the assessment weight to obtain the risk assessment result. The initial risk assessment results can also be combined to obtain the risk assessment result. For example, taking the assessment method as scoring, the score values corresponding to the initial risk assessment results can be combined in the form of a matrix or vector to obtain the risk assessment result.
[0091] 104. Determine the transaction security level of the user ID based on the risk assessment results.
[0092] The transaction security level is used to evaluate the security level of the user corresponding to the user ID in the transaction. The lower the security level, the lower the security of the user corresponding to the user ID in the transaction.
[0093] For example, a preset rating model is used to extract features of multiple dimensions from the risk assessment results to obtain transaction security features. For example, a feature extraction module composed of a convolutional layer and a pooling layer can be used to extract features of multiple scales, thereby obtaining transaction security features of multiple dimensions. The transaction security features are fused to obtain the global security features of the user ID. Based on the global transaction security features, the transaction security level of the user ID is determined. For example, the global transaction security features are mapped to the preset transaction security level set through the fully connected layer to obtain the transaction security level of the user ID.
[0094] The transaction security level of the user ID may be calculated once a day starting from the second day when the user ID activates the transaction service, or the transaction security level of the user ID may be calculated after receiving the permission application request.
[0095] Among them, the rating of the transaction security level of the user identification can actually be regarded as processing the cleaned transaction data, and then obtaining an intermediate variable, which can be the risk assessment result. The intermediate variable is input into the preset rating model, and the transaction security level of the user identification is rated through the preset rating model. Therefore, the rating of the transaction security level of the transaction data of the user identification can be specifically as follows: Figure 5As shown, the transaction data of the user identification is screened out from the manual review data set, the real-time transaction flow data set, the associated text data set and other transaction data sets, and the transaction data is cleaned to obtain standardized data, and the standard data is evaluated using a preset evaluation model to obtain intermediate variables. The preset evaluation model may include a transaction behavior evaluation model, a transaction scenario evaluation model (also referred to as an associated scenario recognition model) and a suspicious transaction data evaluation model to process the standardized data, and the transaction behavior evaluation model and the transaction scenario evaluation model may include multiple evaluation sub-models. The suspicious transaction data evaluation model may include a black material identification model and other auxiliary evaluation models. The intermediate variable is input into the preset rating model to determine the transaction security level corresponding to the user identification.
[0096] 105. Based on the transaction security level, the user ID is granted target transaction authority.
[0097] For example, basic user information corresponding to the user identifier is identified in the transaction data. For example, identity information and transaction time information associated with the user corresponding to the user identifier may be obtained to obtain the basic user information corresponding to the user identifier.
[0098] According to the basic user information and transaction security level, the target transaction authority is granted to the user ID. For example, the basic user information can be tested according to the preset detection strategy, and the transaction security level can be compared with the preset transaction security level threshold. When the basic user information passes the detection and the transaction security level is not lower than the preset transaction security level threshold, the target transaction authority is granted to the user ID. The specific method is as follows:
[0099] (1) Detect basic user information according to the preset detection strategy.
[0100] Among them, basic user information may include transaction time information and user identity information. The so-called transaction time information may be the time information recorded when the user identifier activates the transaction service and conducts the transaction. The user identity information may be the identity information associated with the user identifier, for example, it may include the identity information such as the bank card, legal person, business license, ID card, etc. bound to the user corresponding to the user identifier.
[0101] For example, the transaction time corresponding to the user identifier is obtained in the transaction time information, and the transaction time is compared with the preset transaction time threshold. The preset transaction time threshold may include a preset total transaction time threshold and a preset normal transaction time threshold. For example, the time when the user identifier opens the transaction service and the time when each transaction record is completed are obtained in the transaction time information, so as to obtain the transaction time corresponding to the user identifier. The total transaction time corresponding to the user identifier is identified in the transaction time. The normal transaction time can be the total time from the user corresponding to the user identifier to the time when the transaction service is opened to the present. For example, taking the user corresponding to the user identifier as a merchant as an example, the total transaction time can be the time from the merchant entering the transaction platform to the time when the transaction service is opened to the present. The normal transaction time can be the time for the transaction event that meets the normal transaction status to continue the transaction. For example, taking the normal transaction status as at least one transaction greater than 0.1 yuan as an example, the existence of a transaction greater than 0.1 in a day can mean that today's transaction event is a normal transaction, and the normal transaction time can be the number of days for the normal transaction to continue. For example, if there are 30 days of transaction events that are all normal transactions, the normal transaction time can be 30 days. The total transaction time is compared with the preset total transaction time threshold, and the normal transaction time is compared with the preset normal transaction time threshold. When the total transaction time is not less than the preset total transaction time threshold, or the normal transaction time is not less than the preset normal transaction time threshold, it can be determined that the transaction time is not less than the transaction time threshold. For example, taking the preset total transaction time threshold as 90 days and the preset normal transaction time threshold as 30 days, it is only necessary for the total transaction time corresponding to the user ID to reach 90 days or the normal transaction time to reach 30 days to determine that the transaction time is not less than the transaction time threshold.
[0102] Match the user identity information with the preset risk identity information. For example, match the user identity information corresponding to the user identifier in the black data system and the government restricted information synchronization system. For example, the black data system and the government restricted information synchronization system may include subsystems such as a black bank card system, a black ID card system, a black legal person system, and a black business license system. When the bank card, ID card, legal person information, and business license information of the user identifier associated with the user identity information are matched with the subsystems such as the black bank card system, the black ID card system, the black legal person system, and the black business license system, respectively, when the bank card, ID card, legal person information, and business license information of the user identifier associated with the black bank card system, the black ID card system, the black legal person system, and the black business license system do not exist in the subsystems such as the black bank card system, the black ID card system, the black legal person system, and the black business license system, it can be determined that the user identity information does not match the preset risk identity information.
[0103] When the transaction time is not less than the preset transaction time threshold and the user identity does not match the preset risk identity information, it is determined that the basic user information detection has passed.
[0104] (2) Compare the transaction security level with a preset transaction security level threshold.
[0105] For example, the security level information corresponding to the target transaction authority is obtained, a preset transaction security level threshold is determined from the security level information, and the transaction security level of the user identifier is compared with the preset transaction security level threshold.
[0106] (3) When the basic user information is detected and the transaction security level is not lower than the preset transaction security level threshold, the target transaction authority is granted to the user ID.
[0107] For example, when the basic user information detection passes and the transaction security level is not lower than the preset transaction security level threshold, the target transaction authority is granted to the user ID so that the user ID has the target transaction authority. There are many ways to grant it. For example, the user ID can be added to the permitted user list in the authority configuration information corresponding to the target transaction authority so that the user ID has the target transaction authority. The permission information of the target transaction authority can also be sent to the terminal corresponding to the user ID so that the user corresponding to the user ID can complete the transaction behavior corresponding to the target transaction authority through the permission information.
[0108] Among them, the order between basic information detection and comparison of transaction security level with preset transaction security level threshold before granting target transaction authority to user identification can be performed simultaneously or sequentially. For sequentially, if the previous step fails, the subsequent step can be automatically stopped. If the review is performed sequentially, it can be understood that three levels are used to check the target transaction authority. The first level can be to detect the transaction time information in the basic user information of the user. According to the relevant transaction policy, the preset total transaction time threshold is 90 days and the preset normal transaction time threshold is 30 days. For example, if the total transaction time corresponding to the user identification reaches 90 days or the normal transaction time reaches 30 days, it can be considered that the first level has been passed, and then the second level will be continued. If there is no total transaction time corresponding to the user identification or the normal transaction time does not meet the thresholds of 90 days and 30 days, it can be considered that the first level has not been passed. At this time, there is no need to pass the second and third levels, and the target transaction authority application fails. The second checkpoint can be used to detect the transaction security level of the user ID, and compare the transaction security level with the preset transaction security level threshold. When the transaction security level is not lower than the preset transaction level threshold, it can be determined that the second checkpoint has been passed, otherwise it has not been passed. When the second checkpoint is passed, it is necessary to pass the black data system and the government restricted information synchronization system to make a final judgment on whether the user ID is associated with black industry information / government restricted information, so as to achieve the bottom line. When the user ID is not associated with black industry information / government restricted information, it can be determined that the third checkpoint has been passed. At this time, the user ID can be granted target transaction permissions, which can be done as follows Figure 6 As shown, the basic user information of the user ID, the government restricted information synchronization system and the black data system are updated in real time every day, and the transaction security level of the user ID is the transaction security level from the time when the transaction service was opened to the day before the current time. The order of these levels is not fixed and can be set according to actual applications.
[0109] Optionally, in some embodiments, reference Figure 7 The above-mentioned terminal and server may be a node in a data sharing system. The data sharing system refers to a system 100 for sharing data between nodes. The data sharing system may include multiple nodes 100A. The multiple nodes 100A may refer to various network devices in the data sharing system 100. Each node 100A stores an identical blockchain. The authority management device may store transaction data corresponding to the user identifier in the blockchain, thereby sharing data with other network devices.
[0110] From the above, it can be seen that after the embodiment of the present invention receives the permission application request for the target transaction permission, the permission application request carries the user identification, and then, according to the permission application request, the transaction data corresponding to the user identification is obtained, and the transaction feature data under multiple transaction risk dimensions are determined in the transaction data, and the user identification is risk assessed under the transaction risk dimension based on the transaction feature data, and then, according to the risk assessment result, the transaction security level of the user identification is determined, and based on the transaction security level, the target transaction permission is granted to the user identification; because the scheme performs a risk assessment on the user corresponding to the user identification, and determines the transaction security level of the user according to the assessment result, and uses the transaction security level as a condition for granting transaction permissions, the threshold for applying for transaction permissions is raised, and the transaction security level is evaluated in real time, thereby greatly increasing the difficulty for black market users to crack the transaction permissions, and therefore, the security of permission management can be improved.
[0111] According to the method described in the above embodiment, the following is further described in detail with examples.
[0112] In this embodiment, the permission management device is specifically integrated in an electronic device, the electronic device is a server, the target transaction permission is an enterprise payment permission, the user identifier is a merchant identifier, and the risk assessment method is scoring.
[0113] like Figure 8 As shown, a permission management method, the specific process is as follows:
[0114] 201. The server receives a permission application request for enterprise payment permission.
[0115] For example, the merchant triggers the generation of a permission application request for corporate payment permission through the terminal, adds the merchant ID in the permission application request, and the terminal sends the permission application request with the added merchant ID to the server. When there are batch applications for corporate payment permission for users corresponding to multiple merchant IDs, the terminal stores the merchant ID, adds the storage address to the permission application request for corporate payment permission, and then sends the permission application request carrying the storage address to the server. The server obtains the storage address in the permission application request, and obtains the merchant ID in the terminal's memory or cache according to the storage address.
[0116] 202. The server obtains transaction data corresponding to the merchant ID according to the permission application request.
[0117] For example, the server obtains a preset transaction data type set, and filters out at least one transaction data type corresponding to the enterprise payment authority from the preset transaction data type set. The transaction data type can be manually reviewed data for manual review of merchants, real-time transaction flow data for real-time transactions of merchants, associated text data consistent with the merchant's static information, black clues for merchants to be excluded by external structures, and other suspicious data. By filtering out these types of data from the preset transaction data set, a candidate transaction data set can be obtained. The candidate transaction data set may include a manually reviewed data subset, a real-time transaction data subset, an associated text data subset, and other suspicious data subsets. The manually reviewed data, real-time transaction data, associated text data, and other suspicious data corresponding to the merchant ID are filtered out from the manually reviewed data subset to obtain the transaction data corresponding to the merchant ID.
[0118] 203. The server determines transaction feature data under multiple transaction risk dimensions from the transaction data.
[0119] For example, the server selects the transaction data of the preset time unit from the transaction data to obtain the basic transaction data. The preset time unit can be the time interval from the time when the merchant ID opens the transaction service to the day before the application for the enterprise payment authority. The consistency of the data in the basic transaction data is checked, and the invalid values and missing values in the basic transaction data are processed to obtain the cleaned transaction data, and then the standard data can be obtained, and the standard data is used as the cleaned transaction data.
[0120] The server obtains the transaction risk dimension information corresponding to the enterprise payment authority, and the transaction risk dimension information user indicates at least one transaction risk dimension corresponding to the enterprise payment authority. According to the transaction risk dimension information, at least one transaction risk dimension corresponding to the enterprise payment authority can be determined. When the transaction risk dimension is the transaction behavior risk dimension, the data type corresponding to the transaction risk dimension can be real-time transaction flow data and associated text data. When the transaction risk dimension is the transaction scenario risk dimension, the data type corresponding to the transaction risk dimension can be associated text data and other transaction data. When the transaction risk dimension is the suspicious transaction data risk dimension, the data type corresponding to the transaction risk dimension can be manual review data and other transaction data. Taking the transaction risk dimension as the transaction behavior risk dimension as an example, the real-time transaction flow data and associated text data can be screened out from the cleaned transaction data, and the real-time transaction flow data and associated text data can be used as the transaction feature information corresponding to the transaction behavior risk dimension. The transaction feature data under other risk dimensions are obtained by the same method, and the transaction feature data under each transaction risk dimension can be obtained.
[0121] 204. The server determines risk assessment items according to the transaction risk dimension.
[0122] For example, when the transaction risk dimension is the transaction behavior risk dimension, the assessment item corresponding to the transaction risk dimension can be the transaction behavior assessment; when the transaction risk dimension is the transaction scenario risk dimension, the assessment item corresponding to the transaction risk dimension can be the transaction scenario assessment; when the transaction risk dimension is the suspicious transaction data risk dimension, the assessment item corresponding to the transaction risk dimension can be the suspicious transaction data assessment.
[0123] 205. The server performs risk assessment on the transaction feature data based on the assessment items, and obtains an initial risk assessment result of the merchant ID under the transaction dimension.
[0124] For example, when the evaluation project is transaction behavior evaluation, the server uses a preset transaction behavior evaluation model to perform risk evaluation on the transaction behavior data to obtain an initial risk evaluation result; when the evaluation project is transaction scenario evaluation, the server uses a preset transaction scenario evaluation model to perform risk evaluation on the transaction scenario data to obtain an initial risk evaluation result; when the evaluation project is suspicious transaction data evaluation, the server uses a preset suspicious transaction data evaluation model to perform risk evaluation on the suspicious transaction data to obtain an initial risk evaluation result, which may be as follows:
[0125] (1) When the assessment project is a transaction behavior assessment, the server uses a preset transaction behavior assessment model to perform risk assessment on the transaction behavior data to obtain an initial risk score.
[0126] For example, when the evaluation project is a transaction behavior evaluation, the server divides the transaction behavior data into transaction time data, transaction object data, transaction frequency data, or transaction amount data. Feature extraction is performed on the transaction time data, transaction object data, transaction frequency data, or transaction amount data to obtain the account-raising merchant behavior characteristics, white merchant behavior characteristics, and subject similar transaction behavior characteristics, which are used as transaction behavior characteristics. The account-raising merchant behavior characteristics are evaluated by the account-raising evaluation model to obtain the account-raising score of the merchant identification. The white merchant behavior characteristics are evaluated by the white merchant evaluation model to obtain the white merchant score of the merchant identification. The subject transaction evaluation model is used to obtain the similarity score of the merchant identification. The account-raising score, white merchant score, and similarity score are used as the initial risk score of the merchant identification.
[0127] (2) When the assessment project is a transaction scenario assessment, the server uses a preset transaction scenario assessment model to perform risk assessment on the transaction scenario data to obtain an initial risk score.
[0128] For example, when the evaluation project is a transaction scenario evaluation, the server can divide the transaction scenario data into App text data in the App scenario, AppID text data in the AppID scenario, and public opinion data corresponding to the merchant ID in the user public opinion scenario. By performing text recognition on the App text data, the APP text content can be obtained. By performing text recognition on the AppID text data, the AppID text content can be obtained. By performing text recognition on the public opinion data corresponding to the merchant ID, the public opinion text content of the public opinion corresponding to the merchant ID can be obtained. By using the App evaluation model to perform risk assessment on the App text content, the App risk score can be obtained. By using the AppID evaluation model to perform risk assessment on the AppID text content, the AppID risk score can be obtained. By using the user public opinion evaluation model to perform risk assessment on the public opinion text content, the similarity score of the public opinion risk can be obtained. By integrating the multi-scenario scores and similarity scores, the initial risk score can be obtained.
[0129] (3) When the assessment item is suspicious transaction data assessment, the server uses a preset suspicious transaction data assessment model to perform risk assessment on the suspicious transaction data and obtain an initial risk score.
[0130] For example, when the assessment project is suspicious transaction data assessment, the black material identification model is used to identify suspicious transaction data, and the merchant logo is evaluated as a suspicious user based on the identification result to obtain a black industry suspicious score. The suspicious community mining model is used to identify suspicious transaction data, and the community associated with the merchant logo is evaluated as a suspicious community based on the identification result to obtain a suspicious community score. The public opinion mining model is used to identify suspicious transaction data, and the merchant logo is evaluated as to whether there is suspicious public opinion information based on the identification result to obtain a suspicious public opinion score. The black industry suspicious score, suspicious community score and suspicious public opinion score are integrated to obtain the initial risk assessment score.
[0131] 206. The server integrates the initial risk scores to obtain a risk score.
[0132] For example, the server obtains the assessment weight corresponding to each transaction risk dimension, and weights the initial risk score corresponding to each transaction risk dimension according to the assessment weight to obtain the risk score. The server can also combine the score values corresponding to the initial risk score in the form of a matrix or vector to obtain the risk score.
[0133] 207. The server determines the transaction security level of the merchant ID according to the risk assessment result.
[0134] For example, the server can use the feature extraction module composed of convolutional layers and pooling layers in the preset rating model to extract features at multiple scales, thereby obtaining transaction security features of multiple dimensions. The transaction security features are integrated to obtain the global security features of the merchant logo. By mapping the global transaction security features to the preset transaction security level set through the fully connected layer, the transaction security level of the merchant logo can be obtained.
[0135] 208. The server grants enterprise payment authority to the merchant ID based on the transaction security level.
[0136] For example, the server obtains the user-associated identity information and transaction time information corresponding to the merchant ID, and obtains the basic user information corresponding to the merchant ID. The transaction time information obtains the time when the merchant ID activates the transaction service and the time when each transaction record is completed, thereby obtaining the transaction time corresponding to the merchant ID.
[0137] The total transaction time and normal transaction time corresponding to the merchant ID are identified in the transaction time. According to relevant national policies, the application threshold for the enterprise payment product corresponding to the enterprise payment authority is whether the merchant corresponding to the merchant ID has been settled in the transaction platform to open the transaction service for 90 days, or the merchant corresponding to the merchant ID has been trading normally on the transaction platform for 30 days. Therefore, the preset total transaction time threshold can be 90 days, and the preset normal transaction time threshold can be 30 days. Compare the total transaction time with the preset total transaction time threshold, and compare the normal transaction time with the preset normal transaction time threshold. When the total transaction time corresponding to the merchant ID meets 90 days or the normal transaction time meets 30 days, the next condition can be tested. If not, stop the test of the enterprise payment authority application and do not test the next test condition.
[0138] The next detection condition is whether the transaction security level exceeds the preset transaction security level threshold. Therefore, on the basis that the total transaction time corresponding to the merchant ID satisfies 90 days or the normal transaction time satisfies 30 days, the transaction security level corresponding to the merchant ID is compared with the preset transaction security level threshold. When the transaction security level corresponding to the merchant ID is not lower than the preset transaction security level threshold, the next condition can be tested. If the transaction security level is lower than the preset transaction security level threshold, the test of the enterprise payment authority application is stopped, and the next test condition is not tested.
[0139] The next detection condition is whether the merchant identity information corresponding to the merchant identifier matches the preset risk identity information. For example, the merchant identity information corresponding to the merchant identifier is matched in the black data system and the government restricted information synchronization system. For example, the black data system and the government restricted information synchronization system may include subsystems such as the black bank card system, the black ID card system, the black legal person system, and the black business license system. The bank card, ID card, legal person information, and business license information of the merchant identifier associated with the merchant identity information are matched with the subsystems such as the black bank card system, the black ID card system, the black legal person system, and the black business license system. When the bank card, ID card, legal person information, and business license information of the merchant identifier associated with the black bank card system, the black ID card system, the black legal person system, and the black business license system do not exist in the subsystems such as the black bank card system, the black ID card system, the black legal person system, and the black business license system, it can be determined that the merchant identity information does not match the preset risk identity information. At this point, it can be determined that the detection of the enterprise payment authority applied for the merchant identifier has passed, and the merchant identifier can open the enterprise payment authority.
[0140] Granting enterprise payment authority to a merchant ID can be understood as opening enterprise payment authority for the merchant ID. There are many ways to open it. For example, the merchant ID can be added to the authorized user list in the authority configuration information corresponding to the enterprise payment authority, so that the merchant ID has enterprise payment authority. The permission information of the enterprise payment authority can also be sent to the terminal corresponding to the merchant ID, so that the merchant corresponding to the merchant ID can complete the transaction corresponding to the enterprise payment authority through the permission information.
[0141] Optionally, in one embodiment, the rights management method further includes storing transaction data corresponding to the user identifier in a blockchain.
[0142] Among them, reference Figure 7 , the electronic device integrated with the permission management device is a node in the data sharing system. Each node in the data sharing system can receive input information during normal operation and maintain the shared data in the data sharing system based on the received input information. In order to ensure the information intercommunication in the data sharing system, there can be an information connection between each node in the data sharing system, and the nodes can transmit information through the above information connection. For example, when any node in the data sharing system receives input information, other nodes in the data sharing system obtain the input information according to the consensus algorithm, and store the input information as data in the shared data, so that the data stored on all nodes in the data sharing system are consistent.
[0143] Each node in the data sharing system has a node identifier corresponding to it, and each node in the data sharing system can store the node identifiers of other nodes in the data sharing system, so that the generated blocks can be broadcast to other nodes in the data sharing system according to the node identifiers of other nodes. A node identifier list as shown in the following table can be maintained in each node, and the node name and node identifier are stored in the node identifier list accordingly. Among them, the node identifier can be an IP (Internet Protocol, a protocol for interconnecting networks) address and any other information that can be used to identify the node. The following table only uses the IP address as an example for explanation.
[0144] Node Name Node ID Node 1 117.114.151.174 Node 2 117.116.189.145 … … Node N 119.123.789.258
[0145] Each node in the data sharing system stores the same blockchain. The blockchain consists of multiple blocks, see Fig. 9 The blockchain consists of multiple blocks. The genesis block includes a block header and a block body. The block header stores the input information characteristic value, version number, timestamp and difficulty value, and the block body stores the input information; the next block of the genesis block takes the genesis block as the parent block, and the next block also includes a block header and a block body. The block header stores the input information characteristic value of the current block, the block header characteristic value, version number, timestamp and difficulty value of the parent block, and so on, so that the block data stored in each block in the blockchain is associated with the block data stored in the parent block, ensuring the security of the input information in the block.
[0146] When generating each block in the blockchain, see Fig.10 When the node where the blockchain is located receives the input information, it verifies the input information. After the verification is completed, the input information is stored in the memory pool and the hash tree used to record the input information is updated. After that, the update timestamp is updated to the time when the input information is received, and different random numbers are tried to calculate the eigenvalue multiple times so that the calculated eigenvalue can satisfy the following formula:
[0147] SHA256(SHA256(version+prev_hash+merkle_root+ntime+nbits+x)) <TARGET
[0148] Among them, SHA256 is the eigenvalue algorithm used to calculate the eigenvalue; version (version number) is the version information of the relevant block protocol in the blockchain; prev_hash is the block header eigenvalue of the parent block of the current block; merkle_root is the eigenvalue of the input information; ntime is the update time of the update timestamp; nbits is the current difficulty, which is a fixed value within a period of time and is determined again after exceeding the fixed time period; x is a random number; TARGET is the eigenvalue threshold, which can be determined based on nbits.
[0149] In this way, when the random number that satisfies the above formula is calculated, the information can be stored accordingly, the block header and block body can be generated, and the current block can be obtained. Subsequently, the node where the blockchain is located sends the newly generated block to other nodes in the data sharing system according to the node identification of other nodes in the data sharing system. Other nodes verify the newly generated block and add the newly generated block to the blockchain stored in them after the verification is completed.
[0150] From the above, it can be seen that after the server of this embodiment receives the permission application request for the target transaction permission, the permission application request carries the user identification, and then, according to the permission application request, obtains the transaction data corresponding to the user identification, determines the transaction feature data under multiple transaction risk dimensions in the transaction data, and performs risk assessment on the user identification under the transaction risk dimension based on the transaction feature data, and then, according to the risk assessment result, determines the transaction security level of the user identification, and grants the target transaction permission to the user identification based on the transaction security level; because this scheme performs risk assessment on the user corresponding to the user identification, and determines the transaction security level of the user according to the assessment result, and uses the transaction security level as a condition for granting transaction permission, it raises the threshold for applying for transaction permission, and the transaction security level is evaluated in real time, thereby greatly increasing the difficulty for black market users to crack the transaction permission, and therefore, can improve the security of permission management.
[0151] In order to better implement the above method, an embodiment of the present invention also provides a rights management device, which can be integrated in an electronic device, such as a server or a terminal. The terminal may include a tablet computer, a laptop computer and / or a personal computer.
[0152] For example, Fig.11 As shown, the authority device may include a receiving unit 301, an acquiring unit 302, an evaluating unit 303, a determining unit 304 and an assigning unit 305, as follows:
[0153] (1) receiving unit 301;
[0154] The receiving unit 301 is used to receive a permission application request for a target transaction permission, where the permission application request carries a user identifier.
[0155] For example, the receiving unit 301 can be specifically used for a user to trigger a permission application request for generating a target transaction permission through a terminal, add a user identifier to the permission application request, and the terminal sends the permission application request with the added user identifier to the permission management device.
[0156] (2) Acquisition unit 302;
[0157] The acquisition unit 302 is used to acquire transaction data corresponding to the user identification according to the permission application request.
[0158] For example, the acquisition unit 302 can be specifically used to determine at least one transaction data type corresponding to the target transaction authority based on the authority application request, filter out transaction data corresponding to the transaction data type in a preset transaction data set, obtain a candidate transaction data set, and identify transaction data corresponding to the user identifier in the candidate transaction data set.
[0159] (3) an evaluation unit 303;
[0160] The evaluation unit 303 is used to determine transaction feature data under multiple transaction risk dimensions in the transaction data, and perform risk evaluation on the user identification under the transaction risk dimension according to the transaction feature data.
[0161] For example, the evaluation unit 303 can be specifically used to determine transaction feature data under multiple transaction risk dimensions in the transaction data, and perform risk assessment on the user identifier under the transaction risk dimension based on the transaction feature data, determine the assessment items for the risk assessment based on the type of the transaction risk dimension, perform risk assessment on the transaction feature data based on the assessment items, obtain an initial risk assessment result of the user identifier under the transaction dimension, and integrate the initial risk assessment results to obtain a risk assessment result.
[0162] (4) determining unit 304;
[0163] The determination unit 304 is used to determine the transaction security level of the user identification according to the risk assessment result.
[0164] For example, the determination unit 304 can be specifically used to use a preset rating model to extract features of multiple dimensions for the risk assessment results, obtain transaction security features of multiple dimensions, fuse the transaction security features, obtain the global transaction security features of the user identifier, and determine the transaction security level of the user identifier based on the global transaction security features.
[0165] (5) granting unit 305;
[0166] The granting unit 305 is used to grant the target transaction authority to the user identification based on the transaction security level.
[0167] For example, the granting unit 305 may be specifically configured to identify basic user information corresponding to the user identifier in the transaction data, and grant the target transaction authority to the user identifier according to the basic user information and the transaction security level.
[0168] In specific implementation, the above units can be implemented as independent entities, or can be arbitrarily combined to be implemented as the same or several entities. The specific implementation of the above units can refer to the previous method embodiments, which will not be repeated here.
[0169] As can be seen from the above, in this embodiment, after the receiving unit 301 receives the permission application request for the target transaction permission, the permission application request carries the user identifier, and then the obtaining unit 302 obtains the transaction data corresponding to the user identifier according to the permission application request, and the evaluating unit 303 determines the transaction feature data under multiple transaction risk dimensions in the transaction data, and performs risk evaluation on the user identifier under the transaction risk dimension based on the transaction feature data, and then the determining unit 304 determines the transaction security level of the user identifier according to the risk evaluation result, and the granting unit 305 grants the target transaction permission to the user identifier based on the transaction security level; because the scheme performs risk evaluation on the user corresponding to the user identifier, and determines the transaction security level of the user according to the evaluation result, and uses the transaction security level as a condition for granting transaction permissions, the threshold for applying for transaction permissions is raised, and the transaction security level is evaluated in real time, thereby greatly increasing the difficulty for black market users to crack the transaction permissions, and therefore, the security of permission management can be improved.
[0170] The embodiment of the present invention further provides an electronic device, such as Fig.12 As shown, it shows a schematic diagram of the structure of an electronic device involved in an embodiment of the present invention, specifically:
[0171] The electronic device may include components such as a processor 401 with one or more processing cores, a memory 402 with one or more computer-readable storage media, a power supply 403, and an input unit 404. Those skilled in the art will appreciate that Fig.12 The electronic device structure shown in the figure does not constitute a limitation on the electronic device, and may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently.
[0172] The processor 401 is the control center of the electronic device, and uses various interfaces and lines to connect various parts of the entire electronic device. By running or executing software programs and / or modules stored in the memory 402, and calling data stored in the memory 402, the processor 401 performs various functions of the electronic device and processes data, thereby performing overall detection of the electronic device. Optionally, the processor 401 may include one or more processing cores; preferably, the processor 401 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface, and application programs, and the modem processor mainly processes wireless communications. It is understandable that the above-mentioned modem processor may not be integrated into the processor 401.
[0173] The memory 402 can be used to store software programs and modules. The processor 401 executes various functional applications and data processing by running the software programs and modules stored in the memory 402. The memory 402 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc.; the data storage area may store data created according to the use of the electronic device, etc. In addition, the memory 402 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other volatile solid-state storage devices. Accordingly, the memory 402 may also include a memory controller to provide the processor 401 with access to the memory 402.
[0174] The electronic device also includes a power supply 403 for supplying power to each component. Preferably, the power supply 403 can be logically connected to the processor 401 through a power management system, so as to manage charging, discharging, power consumption and other functions through the power management system. The power supply 403 can also include one or more DC or AC power supplies, recharging systems, power failure detection circuits, power converters or inverters, power status indicators and other arbitrary components.
[0175] The electronic device may further include an input unit 404, which may be used to receive input digital or character information and generate keyboard, mouse, joystick, optical or trackball signal input related to user settings and function control.
[0176] Although not shown, the electronic device may further include a display unit, etc., which will not be described in detail herein. Specifically in this embodiment, the processor 401 in the electronic device will load the executable files corresponding to the processes of one or more application programs into the memory 402 according to the following instructions, and the processor 401 will run the application programs stored in the memory 402, thereby realizing various functions, as follows:
[0177] Receive a permission application request for a target transaction permission, the permission application request carries a user ID, obtain transaction data corresponding to the user ID according to the permission application request, determine transaction feature data under multiple transaction risk dimensions in the transaction data, and perform risk assessment on the user ID under the transaction risk dimension based on the transaction feature data; determine the transaction security level of the user ID according to the risk assessment result, and grant the target transaction permission to the user ID based on the transaction security level.
[0178] For example, a user triggers a permission application request for generating a target transaction permission through a terminal, adds a user ID to the permission application request, and the terminal sends the permission application request with the user ID added to the electronic device. According to the permission application request, at least one transaction data type corresponding to the target transaction permission is determined, and transaction data corresponding to the transaction data type is screened out from a preset transaction data set to obtain a candidate transaction data set, and transaction data corresponding to the user ID is identified in the candidate transaction data set. Transaction feature data under multiple transaction risk dimensions are determined in the transaction data, and risk assessment is performed on the user ID under the transaction risk dimension based on the transaction feature data. According to the type of the transaction risk dimension, an assessment item for risk assessment is determined. Based on the assessment item, risk assessment is performed on the transaction feature data to obtain an initial risk assessment result of the user ID under the transaction dimension, and the initial risk assessment result is integrated to obtain a risk assessment result. A preset rating model is used to extract features of multiple dimensions from the risk assessment result to obtain transaction security features of multiple dimensions, and the transaction security features are integrated to obtain a global transaction security feature of the user ID. According to the global transaction security feature, the transaction security level of the user ID is determined. Identify the basic user information corresponding to the user ID in the transaction data, detect the basic user information according to the preset detection strategy, and compare the transaction security level with the preset transaction security level threshold. When the basic user information passes the detection and the transaction security level is not lower than the preset transaction security level threshold, grant the target transaction authority to the user ID.
[0179] The specific implementation of the above operations can be found in the previous embodiments and will not be described in detail here.
[0180] From the above, it can be seen that after the embodiment of the present invention receives the permission application request for the target transaction permission, the permission application request carries the user identification, and then, according to the permission application request, the transaction data corresponding to the user identification is obtained, and the transaction feature data under multiple transaction risk dimensions are determined in the transaction data, and the user identification is risk assessed under the transaction risk dimension based on the transaction feature data, and then, according to the risk assessment result, the transaction security level of the user identification is determined, and based on the transaction security level, the target transaction permission is granted to the user identification; because the scheme performs a risk assessment on the user corresponding to the user identification, and determines the transaction security level of the user according to the assessment result, and uses the transaction security level as a condition for granting transaction permissions, the threshold for applying for transaction permissions is raised, and the transaction security level is evaluated in real time, thereby greatly increasing the difficulty for black market users to crack the transaction permissions, and therefore, the security of permission management can be improved.
[0181] A person of ordinary skill in the art will appreciate that all or part of the steps in the various methods of the above embodiments may be completed by instructions, or by controlling related hardware through instructions. The instructions may be stored in a computer-readable storage medium and loaded and executed by a processor.
[0182] To this end, an embodiment of the present invention provides a computer-readable storage medium, in which a plurality of instructions are stored, and the instructions can be loaded by a processor to execute the steps in any one of the rights management methods provided in the embodiments of the present invention. For example, the instructions can execute the following steps:
[0183] Receive a permission application request for a target transaction permission, the permission application request carries a user ID, obtain transaction data corresponding to the user ID according to the permission application request, determine transaction feature data under multiple transaction risk dimensions in the transaction data, and perform risk assessment on the user ID under the transaction risk dimension based on the transaction feature data; determine the transaction security level of the user ID according to the risk assessment result, and grant the target transaction permission to the user ID based on the transaction security level.
[0184] For example, a user triggers a permission application request for generating a target transaction permission through a terminal, adds a user ID to the permission application request, and the terminal sends the permission application request with the user ID added to the electronic device. According to the permission application request, at least one transaction data type corresponding to the target transaction permission is determined, and transaction data corresponding to the transaction data type is screened out from a preset transaction data set to obtain a candidate transaction data set, and transaction data corresponding to the user ID is identified in the candidate transaction data set. Transaction feature data under multiple transaction risk dimensions are determined in the transaction data, and risk assessment is performed on the user ID under the transaction risk dimension based on the transaction feature data. According to the type of the transaction risk dimension, an assessment item for risk assessment is determined. Based on the assessment item, risk assessment is performed on the transaction feature data to obtain an initial risk assessment result of the user ID under the transaction dimension, and the initial risk assessment result is integrated to obtain a risk assessment result. A preset rating model is used to extract features of multiple dimensions from the risk assessment result to obtain transaction security features of multiple dimensions, and the transaction security features are integrated to obtain a global transaction security feature of the user ID. According to the global transaction security feature, the transaction security level of the user ID is determined. Identify the basic user information corresponding to the user ID in the transaction data, detect the basic user information according to the preset detection strategy, and compare the transaction security level with the preset transaction security level threshold. When the basic user information passes the detection and the transaction security level is not lower than the preset transaction security level threshold, grant the target transaction authority to the user ID.
[0185] The specific implementation of the above operations can be found in the previous embodiments, which will not be described in detail here.
[0186] The computer-readable storage medium may include: a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.
[0187] Since the instructions stored in the computer-readable storage medium can execute the steps in any one of the permission management methods provided in the embodiments of the present invention, the beneficial effects that can be achieved by any one of the permission management methods provided in the embodiments of the present invention can be achieved. Please refer to the previous embodiments for details and will not be repeated here.
[0188] According to one aspect of the present application, a computer program product or a computer program is provided, the computer program product or the computer program includes computer instructions, and the computer instructions are stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the methods provided in various optional implementations of the above-mentioned rights management aspects.
[0189] The above is a detailed introduction to a permission management method, device and computer-readable storage medium provided in an embodiment of the present invention. Specific examples are used in this article to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only used to help understand the method of the present invention and its core idea; at the same time, for technical personnel in this field, according to the idea of the present invention, there will be changes in the specific implementation method and application scope. In summary, the content of this specification should not be understood as a limitation on the present invention.
Claims
1. A rights management method, characterized in that: include: Receive a permission application request for a target transaction permission, wherein the permission application request carries a user identifier; Determine, according to the permission application request, at least one transaction data type corresponding to the target transaction permission, the transaction data type including manual review data of manual review of merchants, real-time transaction flow data of real-time transactions of merchants, associated text data consistent with merchant static information, and black clues for merchants to be excluded by external structures; Filtering out transaction data corresponding to the transaction data type from a preset transaction data set to obtain a candidate transaction data set; Identifying transaction data corresponding to the user identifier in the candidate transaction data set; Determining transaction feature data under multiple transaction risk dimensions from the transaction data, and determining assessment items for the risk assessment according to the types of the transaction risk dimensions, wherein the transaction feature data includes transaction behavior data, transaction scenario data, and suspicious transaction data, and the assessment items include transaction behavior assessment, transaction scenario assessment, and suspicious transaction data assessment; Based on the assessment items, risk assessment is performed on the transaction feature data to obtain an initial risk assessment result of the user identifier under the transaction dimension; Fusion the initial risk assessment results to obtain a risk assessment result; Determining the transaction security level of the user identification according to the risk assessment result; Identifying basic user information corresponding to the user identifier in the transaction data, the basic user information including transaction time information and user identity information; According to a preset detection strategy, the basic user information is detected; When the basic user information is detected to be passed, the transaction security level is compared with a preset transaction security level threshold; When the transaction security level is not lower than the preset transaction security level threshold, the target transaction authority is granted to the user identification.
2. The rights management method according to claim 1, characterized in that: The determining of transaction feature data under multiple transaction risk dimensions in the transaction data includes: Filtering out transaction data of a preset time unit from the transaction data to obtain basic transaction data; Cleaning the basic transaction data to obtain cleaned transaction data; Transaction feature data under multiple transaction risk dimensions are determined from the cleaned transaction data.
3. The rights management method according to claim 2, characterized in that: The determining of transaction feature data under multiple transaction risk dimensions in the cleaned transaction data includes: Obtaining transaction risk dimension information corresponding to the target transaction authority; Determine the data type corresponding to each transaction risk dimension according to the transaction risk dimension information; Based on the data type, transaction feature information corresponding to the multiple transaction risk dimensions is screened out from the cleaned transaction data.
4. The rights management method according to claim 1, characterized in that: The step of performing risk assessment on the transaction feature data based on the assessment item to obtain an initial risk assessment result of the user identifier under the transaction dimension includes: When the assessment item is the transaction behavior assessment, a preset transaction behavior assessment model is used to perform risk assessment on the transaction behavior data to obtain the initial risk assessment result; When the assessment project is the transaction scenario assessment, a preset transaction scenario assessment model is used to perform risk assessment on the transaction scenario data to obtain the initial risk assessment result; When the assessment item is the suspicious transaction data assessment, a preset suspicious transaction data assessment model is used to perform risk assessment on the suspicious transaction data to obtain the initial risk assessment result.
5. The rights management method according to claim 4, characterized in that: The risk assessment of the transaction behavior data using a preset transaction behavior assessment model to obtain the initial risk assessment result includes: Classifying the transaction behavior data according to the transaction behavior type; Based on the classification result, feature extraction is performed on the transaction behavior data to obtain transaction behavior features; The preset transaction behavior assessment model is used to perform risk assessment on the transaction behavior characteristics to obtain the initial risk assessment result.
6. The rights management method according to claim 4, characterized in that: The risk assessment of the transaction scenario data using the preset transaction scenario assessment model to obtain the initial risk assessment result includes: Classifying the transaction scenario data according to the transaction scenario type; Based on the classification results, text recognition is performed on the transaction scenario data to obtain text content corresponding to each transaction scenario type; Using a preset transaction scenario assessment model to perform risk assessment on the text content, and obtain a scenario risk assessment result corresponding to each scenario type; The scenario risk assessment results are integrated to obtain the initial risk assessment result.
7. The method for managing rights according to any one of claims 1 to 3, characterized in that: Determining the transaction security level of the user identification according to the risk assessment result includes: Using a preset rating model to extract features in multiple dimensions from the risk assessment results to obtain transaction security features in multiple dimensions; The transaction security features are integrated to obtain a global transaction security feature of the user identifier; A transaction security level of the user identification is determined based on the global transaction security feature.
8. The rights management method according to claim 1, characterized in that: The detecting of the basic user information according to a preset detection strategy includes: Obtaining the transaction time corresponding to the user identifier in the transaction time information, and comparing the transaction time with a preset transaction time threshold; Matching the user identity information with preset risk identity information; When the transaction time is not less than the preset transaction time threshold, and the user identity information does not match the preset risk identity information, it is determined that the basic user information detection has passed.
9. The method for rights management according to claim 8, characterized in that: The preset transaction time threshold includes a preset total transaction time threshold and a preset normal transaction time threshold, and obtaining the transaction time corresponding to the user identifier from the transaction time information and comparing the transaction time with the preset transaction time threshold includes: The total transaction time and normal transaction time corresponding to the user identifier are identified in the transaction time, wherein the total transaction time is the total time since the user corresponding to the user identifier opened the transaction service, and the normal transaction time is the continuous transaction time of the transaction event that meets the normal transaction status; Comparing the total transaction time with the preset total transaction time threshold, and comparing the normal transaction time with the preset normal transaction time threshold; When the total transaction time is not less than the preset total transaction time threshold, or the normal transaction time is not less than the preset normal transaction time threshold, it is determined that the transaction time is not less than the transaction time threshold.
10. A rights management device, characterized in that: include: A receiving unit, configured to receive a permission application request for a target transaction permission, wherein the permission application request carries a user identifier; an acquisition unit, configured to determine, according to the permission application request, at least one transaction data type corresponding to the target transaction permission, the transaction data type including manual review data for manual review of merchants, real-time transaction flow data for real-time transactions of merchants, associated text data consistent with static information of merchants, and black clues for excluding merchants by external structures, filter out transaction data corresponding to the transaction data type from a preset transaction data set, obtain a candidate transaction data set, and identify transaction data corresponding to the user identifier from the candidate transaction data set; an evaluation unit, configured to determine transaction feature data under a plurality of transaction risk dimensions in the transaction data, and determine evaluation items for the risk evaluation according to the types of the transaction risk dimensions, wherein the transaction feature data include transaction behavior data, transaction scenario data, and suspicious transaction data, and the evaluation items include transaction behavior evaluation, transaction scenario evaluation, and suspicious transaction data evaluation; based on the evaluation items, perform risk evaluation on the transaction feature data to obtain an initial risk evaluation result of the user identifier under the transaction dimension; Fusion the initial risk assessment results to obtain a risk assessment result; A determination unit, configured to determine a transaction security level of the user identification according to the risk assessment result; The granting unit is used to identify the basic user information corresponding to the user identification in the transaction data, the basic user information including transaction time information and user identity information, and detect the basic user information according to a preset detection strategy. When the basic user information passes the detection, the transaction security level is compared with a preset transaction security level threshold. When the transaction security level is not lower than the preset transaction security level threshold, the user identification is granted the target transaction authority.
11. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a plurality of instructions, and the instructions are suitable for being loaded by a processor to execute the steps in the rights management method according to any one of claims 1 to 9.
12. An electronic device, characterized in that: It comprises a processor and a memory, wherein the memory stores an application program, and the processor is used to run the application program in the memory to execute the steps in the rights management method according to any one of claims 1 to 9.
Citation Information
Patent Citations
Method and apparatus for managing transaction right
CN104781822A
Transaction risk assessment method and system
CN108537671A
Risk assessment treating method and device based on business information, server and medium
CN108876133A
Transaction risk assessment method, device and computer system
CN110533536A
Appeal processing method and device and electronic equipment
CN110738401A
