WO2017162113A1 - 一种风险信息输出、风险信息构建方法及装置 - Google Patents

一种风险信息输出、风险信息构建方法及装置 Download PDF

Info

Publication number
WO2017162113A1
WO2017162113A1 PCT/CN2017/077248 CN2017077248W WO2017162113A1 WO 2017162113 A1 WO2017162113 A1 WO 2017162113A1 CN 2017077248 W CN2017077248 W CN 2017077248W WO 2017162113 A1 WO2017162113 A1 WO 2017162113A1
Authority
WO
WIPO (PCT)
Prior art keywords
risk
risk information
information
level
service
Prior art date
Application number
PCT/CN2017/077248
Other languages
English (en)
French (fr)
Inventor
杨陆毅
陆青
云蕾
王文雯
崔阳
Original Assignee
阿里巴巴集团控股有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 阿里巴巴集团控股有限公司 filed Critical 阿里巴巴集团控股有限公司
Priority to EP17769390.0A priority Critical patent/EP3435260A4/en
Priority to JP2018550377A priority patent/JP6696001B2/ja
Priority to KR1020187030588A priority patent/KR102211374B1/ko
Priority to SG11201808341SA priority patent/SG11201808341SA/en
Publication of WO2017162113A1 publication Critical patent/WO2017162113A1/zh
Priority to US16/140,039 priority patent/US20190026744A1/en
Priority to PH12018502049A priority patent/PH12018502049A1/en
Priority to US16/722,609 priority patent/US20200143378A1/en

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/401—Transaction verification
    • G06Q20/4016—Transaction verification involving fraud or risk level assessment in transaction processing
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • G06Q10/063—Operations research, analysis or management
    • G06Q10/0635—Risk analysis of enterprise or organisation activities
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/04—Forecasting or optimisation specially adapted for administrative or management purposes, e.g. linear programming or "cutting stock problem"
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • G06Q10/063—Operations research, analysis or management
    • G06Q10/0637—Strategic management or analysis, e.g. setting a goal or target of an organisation; Planning actions based on goals; Analysis or evaluation of effectiveness of goals
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/401—Transaction verification
    • G06Q20/4014—Identity check for transactions
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/409—Device specific authentication in transaction processing
    • G06Q20/4093—Monitoring of device authentication
    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16Z—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS, NOT OTHERWISE PROVIDED FOR
    • G16Z99/00—Subject matter not provided for in other main groups of this subclass

Definitions

  • the present application relates to the field of information technology, and in particular, to a risk information output, a risk information construction method and apparatus.
  • the online business platform generally performs risk control on the business performed on the business platform based on predetermined risk control rules and/or risk control models, and obtains risk control decision results and outputs the results to the business.
  • the party, and the subsequent processing of the service according to the risk control decision result, wherein the risk control decision result may be: reject the service or pass the service.
  • the corresponding risk information may also be output to the owner of the service, and the risk information is used to explain the cause of the risk control decision result.
  • each service platform is generally The risk control rules used are simply translated in advance and then output as risk information to the business owner.
  • the industry experience and risk control capabilities of different parties of the business are uneven.
  • the degree or depth of demand for risk information may be different for different parties of the business, and the output of the above prior art is different. This difference is not taken into account in the risk information. Therefore, the risk information outputted in the above prior art is less suitable for different parties of the service.
  • the embodiment of the present invention provides a risk information output, a risk information construction method, and a device, which are used to solve the problem that the risk information outputted in the prior art has poor applicability to different users of the service.
  • a predetermined risk control rule and/or risk control model containing one or more risk factors in each Determining, in the risk factor, a risk factor corresponding to a risk control decision result of the business, the risk control decision result being according to the risk control rule and/or the risk control model, and the service related to the corresponding risk factor Data determined;
  • a risk factor determining module configured to determine, according to a predetermined risk control rule and/or a risk control model including one or more risk factors, a risk factor corresponding to a risk control decision result of the service, among the risk factors, The risk control decision result is determined according to the risk control rule and/or the risk control model, and the service data related to the corresponding risk factor;
  • a risk information first determining module configured to determine a risk information set corresponding to the corresponding risk factor, where the corresponding risk information set includes multi-level risk information with different degrees of refinement, where the risk information is used to explain the cause Describe the reasons for the risk control decision results;
  • a risk information second determining module configured to determine, in the multi-level risk information, at least a level of refinement that matches a risk information demand level of a party of the service according to a risk information requirement level of a party to the service Primary risk information;
  • a risk information output module configured to output the determined risk information, so that the determined party of the service obtains the determined risk information.
  • the corresponding risk information set includes multi-level risk information with different degrees of refinement, and the risk information is used to explain the risk control decision result that leads to the business.
  • the cause, the risk control decision result is determined according to the risk control rule and/or the risk control model, and the service data related to the corresponding risk factor;
  • a risk factor obtaining module configured to disassemble a predetermined risk control rule and/or a risk control model, and obtain one or more risk factors included in the risk control rule and/or the risk control model;
  • a risk information construction module configured to respectively construct a corresponding risk information set for each of the obtained risk factors, where the corresponding risk information set includes multi-level risk information with different degrees of refinement, and the risk information is used to explain The risk control decision result of the business, the risk control decision result is determined according to the risk control rule and/or the risk control model, and the service data related to the corresponding risk factor;
  • the risk control decision result In order to output the risk control decision result, according to the risk information requirement level of the owner of the service, determine, in the multi-level risk information, the degree of refinement and the degree of the output to the owner of the service. At least one level of risk information matching the risk information demand level of the owner of the business.
  • the multi-level risk information corresponding to the risk factor and different degree of refinement may be constructed for each risk factor, so as to adapt to different needs of the different parties of the service for the risk information.
  • the level of demand and/or depth of the hierarchy, and the different levels of risk information requirements can be used to characterize the level and/or depth of demand for different levels of risk information requirements.
  • the risk information output by the solution of the present application has better applicability to different parties of the service, and the problems in the prior art described above can be partially or completely solved.
  • FIG. 1 is a flowchart of a method for outputting risk information according to an embodiment of the present application
  • FIG. 2 is a part of a schematic diagram of a risk information set constructed for each risk factor in a risk control scenario for a payment service according to an embodiment of the present application;
  • FIG. 3 is a schematic diagram of a schematic diagram of a risk information set constructed for each risk factor in a risk control scenario for a payment service according to an embodiment of the present application;
  • FIG. 5 is used to output a risk signal in a risk control scenario for a payment service according to an embodiment of the present disclosure.
  • FIG. 6 is a schematic diagram of a three-layer frame of infocode in a risk control scenario for a payment service according to an embodiment of the present application
  • FIG. 7 is a schematic structural diagram of a risk information output apparatus corresponding to FIG. 1 according to an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of a risk information construction apparatus corresponding to FIG. 4 according to an embodiment of the present application.
  • the risk information can be used to explain the cause of the corresponding risk control decision result, and the degree or depth of demand for the risk information by different parties of the service may also be different.
  • the merchant whose service belongs to the service is taken as an example.
  • they would like to see the risk signals of various aspects of the business behind the risk control decision-making results, that is, they prefer to see a higher degree of refinement (more specific and in-depth Risk information, which helps to improve the level of risk control and understand current risk trends.
  • a higher degree of refinement more specific and in-depth Risk information, which helps to improve the level of risk control and understand current risk trends.
  • the risk information with a lower level of refinement is easier to understand, and therefore more suitable for such merchants.
  • the risk information is not considered in the above-mentioned differences, so that the risk information of the output may be less suitable for different parties of the service.
  • the core idea of the solution of the present application is to construct multi-level (multi-level) risk information with different degrees of refinement to adapt to the different levels of demand of different levels of risk information of the business. / or depth, thereby improving the applicability of the output risk information to different owners of the business, wherein the degree and/or depth of demand for different levels of risk information can be characterized by different levels of risk information requirements, and the multi-level risk information can be Based on historical risk control experience.
  • the scheme of the present application will be described in detail below.
  • FIG. 1 is a process of a method for outputting risk information according to an embodiment of the present disclosure.
  • the execution subject of the process may be a server or a terminal. More specifically, the execution entity may be a function module for outputting risk information on a server or a terminal.
  • Devices that can be used as the server include, but are not limited to, personal computers, large and medium-sized computers, computer clusters, and the like; devices that can be used as the terminals include, but are not limited to, mobile phones, tablet computers, smart watches, car mobile stations, and individuals. Computer, etc.
  • the executor of the present invention is not limited to the present application. For the convenience of description, the embodiments of the present application are described by taking the execution subject as a server as an example.
  • the process in Figure 1 can include the following steps:
  • S101 Determine, according to a predetermined risk control rule and/or a risk control model including one or more risk factors, a risk factor corresponding to a risk control decision result of the service, where the risk control decision The result is determined based on the risk control rules and/or risk control models, and the business data relating to the corresponding risk factors.
  • the service may be referred to as “a business”, and the process in FIG. 1 may be separately performed for each service.
  • risk control may be performed on the business based on the risk control rule and/or the risk control model, and the risk control decision result is obtained, wherein the risk control rule is generally performed by the risk control model, and the risk control model itself is also Risk control rules can be included.
  • the risk control rules and risk control models can be viewed as a whole, and this whole can be called: risk strategy system.
  • the current risk control rules can be a single behavior in some simple scenarios.
  • the process of risk control on the business that is, the behavior characteristics of the service (which can be extracted through the relevant data of the service) and the behavior characteristics of the risk control rule respectively correspond to the matching process, and then the decision can be made according to the matching result. Determine the outcome of risk control decisions.
  • each behavioral feature can be summarized by a risk factor.
  • the risk control rule may contain one or more risk factors, and correspondingly, the risk control rules may be disassembled into one or more risk factors.
  • the risk control model can also contain one or more risk factors.
  • the service data related to the corresponding risk factor may refer to data that belongs to the service and reflects behavior characteristics corresponding to the risk factor.
  • the risk control decision result may correspond to one or more risk factors, wherein if the risk control decision result of the service is caused by a behavior characteristic belonging to the service and reflecting the corresponding behavior factor of one or several risk factors, it may be called:
  • the risk control decision result corresponds to the one or several risk factors.
  • the result of the risk decision of the business may specifically include: rejecting the service, or passing the service, or manually reviewing the service, and the like.
  • S102 Determine a risk information set corresponding to the corresponding risk factor, where the corresponding risk information set includes multi-level risk information with different degrees of refinement, the risk information is used to explain the result of the risk control decision s reason.
  • the risk information used to explain the result of the risk decision may be different for the risk decision results corresponding to different risk factors.
  • a corresponding risk information set may be separately constructed for each risk factor in advance.
  • the risk information set may include multi-level risk information with different degrees of refinement, and the risk factor corresponding to the risk information set is: the risk factor corresponding to the multi-level risk information included in the risk information set.
  • the risk information set described in the present application includes multiple levels of risk information, and the specific meaning may be: the multi-level risk information has been constructed and stored in the risk information set; or the multi-level risk Although the information has not been constructed yet, the material used to construct the multi-level risk information is already ready in the risk information set.
  • the multi-level risk information is to be output, the multi-level risk information can be constructed in real time according to the material. And then output.
  • the multi-level risk information may specifically be multiple levels of risk information, and the multiple levels of risk information may be refined layer by layer.
  • the risk information at the top level is macro and general, and the risk information at the top level is a further refinement of the risk information at the top level (specifically, and/or augmenting new content, etc.), and so on, except for the top layer.
  • the following risk information for each layer can be a further refinement of the risk information of the previous layer.
  • the risk information of the multiple levels may not have a "layer-by-layer refinement" relationship.
  • the risk information of each level may be constructed relatively independently. In this case, it is not necessary to construct the risk information of the layer based on the risk information of the previous layer.
  • the division of the multi-level risk information hierarchy may be performed according to historical risk control experience, and/or the needs of the owner of the service. Different services may have different ways of dividing. This application does not limit the specific division of multi-level risk information levels.
  • S103 Determine, according to the risk information requirement level of the owner of the service, at least one level of risk information whose level of refinement matches the risk information requirement level of the party to which the service belongs.
  • the risk information requirement level of the owner of the service may be used to represent the degree and/or depth of the risk information requirement of the party to the service.
  • the risk information requirement level of the party to which the service belongs may be estimated by the server based on historical data, or may be specified by the owner of the service.
  • the former method can reduce the operation of the owner of the service, and the convenience is high; the latter method has higher accuracy because it is directly adopted by the owner's own opinion.
  • This application is described
  • the specific number of levels and the specific division of the level of risk information requirements are not limited.
  • the risk information requirement levels of different affiliations of the service may be different. Accordingly, the risk information of the corresponding level may be separately output to the different affiliation to adapt to the requirements of different affiliations.
  • each risk information requirement level may uniquely match one of the multi-level risk information, or may simultaneously match two or more levels of the multi-level risk information. information.
  • S104 Output the determined risk information, so that the owner of the service obtains the determined risk information.
  • the determined risk information may be directly output to the owner of the service; the risk information may be output to other devices or function modules, and then the other device or function module sends the risk information to the service.
  • the party can also save the risk information first, passively wait for the owner of the business to query, and then output the risk information; and so on.
  • the risk control decision result and the risk information determined for the risk control decision result may be output by the same device, or may be output by different devices, which is not limited in this application. Further, the present application does not limit the result of the risk control decision and the output timing and output sequence of the risk information. Generally, the risk information may be outputted when the risk control decision result is output, which may be convenient. The party to the business knows in a timely manner the cause of the decision on the risk control decision.
  • multi-level risk information with different degree of refinement corresponding to the risk factor can be constructed for each risk factor, so as to adapt to different levels of demand and/or depth of different levels of risk information demand of the different parties of the business.
  • different levels of risk information requirements can be used to characterize the degree and/or depth of demand for different levels of risk information requirements. Further, when outputting risk information, it can be based on the risk information demand level of the business owner.
  • At least one level of risk information whose level of refinement matches the risk information requirement level of the business owner is determined and output, so that the owner of the service obtains the output risk information, and therefore, the risk information output by the solution of the present application.
  • the embodiments of the present application further provide some specific implementation manners of the foregoing methods, and an extended solution, which will be described below.
  • each risk factor included in the risk control rule and/or the risk control model may be respectively associated with a predetermined one of the risk information sets.
  • determining the risk information set corresponding to the corresponding risk factor may specifically include: according to the correspondence, In each of the predetermined sets of risk information, a risk information set corresponding to the corresponding risk factor is determined.
  • determining the risk information set corresponding to the corresponding risk factor may specifically include: constructing a risk information set corresponding to the corresponding risk factor according to the corresponding risk factor.
  • the risk information requirement level information of the owner of the service is used.
  • two methods for obtaining the information level of the risk information are provided below. As an example:
  • the risk information requirement level of the business owner may be specified in advance by the owner of the service, or the risk information demand level of the owner of the service may be specified by the server; and then the specified risk information demand level information is written into the predetermined configuration file. . Then, before performing step S103, the risk requirement level information can be read from the predetermined configuration file.
  • the first way can reduce the operation of the owner of the service, and the convenience is high.
  • the risk information demand level of the owner of the service is estimated by the server in real time.
  • the server may estimate the risk information requirement level of the owner of the service according to the obtained risk control level information and/or risk control demand information of the owner of the service.
  • the second method has higher accuracy because it refers to the relevant information of the owner of the service.
  • the method for acquiring the risk control level information and/or the risk control requirement information is not limited, and may be collected by the server during the historical interaction with the owner of the service, or may be collected by the server.
  • the management personnel on the side are informed by the communication with the owner of the business, and input into the server, and so on.
  • step S104 In the embodiment of the present application, several embodiments have been given above for step S104. In practical applications, a more common implementation is as follows:
  • the outputting the determined risk information may include: outputting the determined risk information to the owner of the service when the risk control decision result is output to the owner of the service.
  • the advantage of this embodiment is that the owner of the service can see the corresponding risk information relatively synchronously when seeing the result of the risk control decision, and the experience of the owner of the service is better, and it is convenient to have directionality according to the risk information.
  • the business performs subsequent processing on the business, for example, re-submission of the business after removing the risk.
  • Multi-level risk information and “risk information demand level” are all one of the focuses of the solution of the present application, and they are further explained here for ease of understanding.
  • the risk information requirement level of the owner of the service is one of a predetermined plurality of risk information requirement levels, and is used to represent the degree and/or depth of the risk information requirement of the owner of the service.
  • the plurality of risk information requirement levels may be corresponding to and matched with the multi-level risk information, and represent the degree of risk information demand and/or Or the higher the depth of the risk information requirement level, the higher the level of refinement of the level of risk information matched in the multi-level risk information.
  • the service is a payment service, and the owner of the payment service is a merchant corresponding to the payment service.
  • the payment service may be mainly based on a third-party payment platform, or may be mainly based on a payment platform provided by the bank.
  • All merchants in the payment business scenario can be divided into three categories, and the level of risk information demand and/or depth is relatively low: “weakly controlled merchants”; the degree of risk information demand and/or depth is relatively moderate. It is: “Generally controlled merchants”; a category with a relatively high degree of risk information demand and/or depth is called “strongly controlled merchants”.
  • the multi-level risk information may specifically be three levels of risk information.
  • the risk information When the risk information is output, if the owner of the service is a weakly controlled merchant, the risk information of the level with the lowest level of refinement may be output, if the If the party is a general management and control merchant, it can output the risk information of the level with a moderate degree of refinement. If the party is a strong management and control merchant, it can output the risk information of the level with the highest level of refinement.
  • the multi-level risk information may be constructed according to the risk control rule and/or the risk control model, and related historical risk control experience data, and described in a manner that is easy for the owner of the service to understand. describe.
  • Historical risk control experience can include the experience of the server in the risk control process for historical business, as well as the ready-to-use experience provided by the business's affiliates.
  • the server may estimate the risk information required by the affiliation or other affiliation similar to the affiliation according to the information provided by the affiliation of the service, and what kind of risk information is easy for the affiliation or the affiliation Similar to other parties' understanding; the owner of the business can also actively inform the server of what kind of risk information it needs, as well as its own easy-to-understand description of the risk information; these data can be used as historical risk control experience data.
  • the risk information may be information in the form of program code or information in the form of natural language.
  • the simple translation of the risk control rule is taken as the risk information, and the solution of the present application can describe the risk information in an easy-to-understand language according to the historical risk control experience, so as to be easy for the owner of the business to understand, therefore, based on the present
  • the risk information output by the proposed scheme is more applicable.
  • the embodiment of the present application provides a schematic diagram of a risk information set constructed for each risk factor in a risk control scenario for a payment service, as shown in FIG. 2 and FIG. 2 and FIG. 3 are respectively a part of the schematic diagram of the risk information set, and each child node of the “stolen card risk” in FIG. 2 is shown in FIG. 3.
  • risk information is referred to as “risk information hint code (infocode)”, and the risk information set constructed for each risk factor is collectively referred to as “infocode system”.
  • infocode risk information hint code
  • infocode system the risk information set constructed for each risk factor
  • the infocode system is represented by a tree structure, and the "risk information prompt coding system" node is the root node of the tree structure.
  • infocode sets are respectively: the content of the "stolen card risk” node and the contents of all its child nodes, "theft” The account risk “node content and its collection of all child node content, the "trusted system” node content and its collection of all child node content, the "bank system rejection” node content and its collection of all child node content.
  • each infocode set corresponds to a risk factor (risk factor omitted is not shown), each infocode set contains multiple levels of infocode, starting from the second layer of the tree structure, each layer is in a multi-level infocode One level of infocode, the more detailed the infocode is down.
  • the infocode set contains three levels of infocode.
  • the first level of infocode includes the content of the "stolen card risk” node;
  • the second level of infocode includes "high risk account”, “information conflict”, "high risk environment”, “risk network”, “high risk event attribute”, "abnormal behavior path” "7" node content.
  • the second level of infocode is a further refinement of the first level of infocode; similarly, the third level of infocode is a further refinement of the second level of infocode, for example, the "high risk account” in the second level of infocode.
  • the node content is refined into four contents of the "new account”, “dormant account”, “information completion degree”, and "batch behavior when the account is logged in” in the third level infocode, and the information in the second level infocode
  • the content of the "conflict" node is refined into two contents of "the transaction information conflicts", "credit card verification information conflict” in the third level infocode, and the like.
  • FIG. 2 and FIG. 3 are only examples of the multi-level infocode, and do not constitute a limitation on the present application.
  • the risk information output method provided by the embodiment of the present application is described in detail. Based on the same idea, the embodiment of the present application further provides a risk information construction method.
  • FIG. 4 is a process of the risk information construction method, and the execution subject of the process may be the same as the execution body of the process in FIG. 1 , and details are not described herein.
  • the process in Figure 4 can include the following steps:
  • S401 Disassemble a predetermined risk control rule and/or a risk control model to obtain the risk control rule And/or one or more risk factors included in the risk control model.
  • S402 Construct a corresponding risk information set for each of the obtained risk factors, where the corresponding risk information set includes multi-level risk information with different degrees of refinement, and the risk information is used to explain the risk control decision that leads to the service. For the reason of the result, the risk control decision result is determined according to the risk control rule and/or the risk control model, and the service data related to the corresponding risk factor.
  • the risk control decision result In order to output the risk control decision result, according to the risk information requirement level of the owner of the service, determine, in the multi-level risk information, the degree of refinement and the degree of the output to the owner of the service. At least one level of risk information matching the risk information demand level of the owner of the business.
  • the embodiment of the present application further provides a structure diagram of an infocode hierarchical output module for outputting risk information in a risk control scenario for a payment service, as shown in FIG. 5 .
  • the module in Figure 5 can be divided into three main parts:
  • the first part, the infocode framework is used to build a three-layer framework for infocode based on historical risk control experience data from the payment service platform. Multi-level risk information is built based on the infocode three-tier framework.
  • the second part the infocode mapping.
  • the “mapping” main risk control rules and/or risk factors included in the risk control module ie: risk factor 1, risk factor 2, ..., risk factor X
  • each risk information set ie: infocode A, infocode B
  • Correspondence mapping between ,..., infocode X ie: infocode A, infocode B
  • Each risk information set contains corresponding multi-level risk information.
  • infocode A contains three levels of codeA1, codeA2, and codeA3.
  • the third part the infocode output. It is used to grade the multi-level risk information to the owner of the business whose risk information needs level matching.
  • the risk information demand level has three levels, namely: the level of weakly controlled merchants, the level of general regulated merchants, and the level of strong managed merchants.
  • the weakly controlled merchants can be small merchants or new merchants with no risk control ability or no risk control.
  • the general control merchants can be small and medium-sized merchants with certain risk control capabilities but no professional risk control team. Large and medium-sized merchants with strong risk control capabilities and established professional risk control teams.
  • the server can analyze each payment service in real time, and when the risk control decision result is given by “rejecting the service” or “passing the service” in combination with the risk control rule and the risk control model, the corresponding level can also be
  • the infocode is output to the owner of the business.
  • the embodiment of the present application further provides an example of an infocode three-layer framework in a risk control scenario for a payment service, as shown in FIG. 6.
  • Each risk factor corresponds to an infocode set.
  • the risk factor can be characterized from a more detailed dimension, and then a three-level infocode can be constructed.
  • the third-level infocode constitutes an infocode set.
  • “conflict” has the risk of stolen card and stolen account (can be used as the first level of infocode).
  • the risk of stolen card can be classified into card bin conflict, device conflict, etc. (can be used as the second level of infocode), and further
  • the card bin conflict can be divided into the conflict between the issuing country and the IP country, the conflict between the issuing country and the receiving country (can be used as the third level of infocode).
  • the benign interaction between the payment service platform and the merchant can be effectively enhanced, and the payment risk control experience is improved.
  • multi-level risk information of three levels is used as an example of “multi-level risk information”.
  • multi-level risk information may also have two levels. Or there are more than three levels, and so on.
  • the solution of the present application may be implemented for all risk factors, or may be implemented only for partial risk factors.
  • the embodiment of the present application further provides a corresponding risk information output device and a risk information construction device, as shown in FIG. 7 and FIG. 8.
  • FIG. 7 is a schematic structural diagram of a risk information output apparatus corresponding to FIG. 1 according to an embodiment of the present disclosure, specifically including:
  • the risk factor determination module 701 is configured to determine, according to a predetermined risk control rule and/or a risk control model including one or more risk factors, a risk factor corresponding to the risk control decision result of the service among each of the risk factors
  • the risk control decision result is determined according to the risk control rule and/or the risk control model, and the service data related to the corresponding risk factor;
  • the risk information first determining module 702 is configured to determine a risk information set corresponding to the corresponding risk factor, where the corresponding risk information set includes multi-level risk information with different degrees of refinement, where the risk information is used to explain The reason for the risk control decision result;
  • the risk information second determining module 703 is configured to determine, in the multi-level risk information, that the degree of refinement matches the risk information requirement level of the owner of the service according to the risk information requirement level of the belonging party of the service. At least level one risk information;
  • a risk information output module 704 configured to output the determined risk information to facilitate the owner of the service Obtaining the determined risk information.
  • each risk factor included in the risk control rule and/or the risk control model is respectively associated with a predetermined one of the risk information sets;
  • the risk information first determining module 702 is specifically configured to: determine, according to the correspondence relationship, a risk information set corresponding to the corresponding risk factor in each predetermined risk information set.
  • the device further includes:
  • the risk information requirement level determining module 705 is configured to determine, before the risk information second determining module 703 determines at least one level of risk information that the degree of refinement matches the risk information demand level of the belonging party of the service, The risk information requirement level of the owner of the service; or, based on the obtained risk control level information and/or risk control demand information of the owner of the service, the risk information demand level of the owner of the service is estimated.
  • the risk information output module 704 is specifically configured to: when the risk control decision result is output to the owner of the service, output the determined risk information to the owner of the service.
  • the risk information requirement level of the belonging party of the service is one of a predetermined plurality of risk information requirement levels, and is used to represent the degree and/or depth of the risk information requirement of the owner of the service;
  • the plurality of risk information requirement levels are correspondingly matched with the multi-level risk information, and the risk information demand level indicating the degree of risk information demand and/or the depth is higher, and the matching in the multi-level risk information The level of refinement of the primary risk information is higher.
  • the multi-level risk information is constructed according to the risk control rule and/or the risk control model, and related historical risk control experience data, and is described in a description manner that is easy for the owner of the service to understand. .
  • the risk control decision result of the service includes: rejecting the service, or passing the service, or performing manual review on the service.
  • the service includes a payment service
  • the owner of the service includes a merchant corresponding to the payment service.
  • the device in Figure 7 can be located specifically on a server or terminal.
  • FIG. 8 is a schematic structural diagram of a risk information construction apparatus corresponding to FIG. 4 according to an embodiment of the present application, which specifically includes:
  • a risk factor obtaining module 801 configured to disassemble a predetermined risk control rule and/or a risk control model, and obtain one or more risk factors included in the risk control rule and/or the risk control model;
  • the risk information construction module 802 is configured to respectively construct a corresponding risk information set for each of the obtained risk factors, where the corresponding risk information set includes multi-level risk information with different degrees of refinement, where the risk information is used.
  • the risk control decision result is determined according to the risk control rule and/or the risk control model, and the service data related to the corresponding risk factor;
  • the risk control decision result In order to output the risk control decision result, according to the risk information requirement level of the owner of the service, determine, in the multi-level risk information, the degree of refinement and the degree of the output to the owner of the service. At least one level of risk information matching the risk information demand level of the owner of the business.
  • the device in Figure 8 can be located specifically on a server or terminal.
  • the apparatus provided by the present application is in one-to-one correspondence with the method provided by the present application, and therefore, the apparatus also has similar beneficial technical effects as the method, because the beneficial technical effects of the method have been above.
  • the detailed description is made, and therefore, the beneficial technical effects of the device will not be described herein.
  • embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
  • computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.
  • the computing device includes one or more processors (CPUs), input/output interfaces, and networks.
  • processors CPUs
  • input/output interfaces and networks.
  • Network interface and memory are examples of processors (CPUs), input/output interfaces, and networks.
  • the memory may include non-persistent memory, random access memory (RAM), and/or non-volatile memory in a computer readable medium, such as read only memory (ROM) or flash memory.
  • RAM random access memory
  • ROM read only memory
  • Memory is an example of a computer readable medium.
  • Computer readable media includes both permanent and non-persistent, removable and non-removable media.
  • Information storage can be implemented by any method or technology.
  • the information can be computer readable instructions, data structures, modules of programs, or other data.
  • Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read only memory. (ROM), electrically erasable programmable read only memory (EEPROM), flash memory or other memory technology, compact disk read only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, Magnetic tape cartridges, magnetic tape storage or other magnetic storage devices or any other non-transportable media can be used to store information that can be accessed by a computing device.
  • computer readable media does not include temporary storage of computer readable media, such as modulated data signals and carrier waves.

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Human Resources & Organizations (AREA)
  • Strategic Management (AREA)
  • Economics (AREA)
  • Entrepreneurship & Innovation (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • General Business, Economics & Management (AREA)
  • Physics & Mathematics (AREA)
  • Educational Administration (AREA)
  • Accounting & Taxation (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • Marketing (AREA)
  • Development Economics (AREA)
  • Game Theory and Decision Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Finance (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Selective Calling Equipment (AREA)

Abstract

本申请公开了一种风险信息输出、风险信息构建方法及装置，用以解决现有技术中输出的风险信息对于业务的不同所属方的适用性较差的问题。该风险信息输出方法包括：根据预定的、包含一个或多个风险因子的风险控制规则和/或风险控制模型，在各风险因子中，确定与业务的风险控制决策结果对应的风险因子；确定与对应的风险因子对应的风险信息集合，对应的风险信息集合包含细化程度不同的多级风险信息，风险信息用于解释导致风险控制决策结果的原因；根据业务的所属方的风险信息需求等级，在多级风险信息中，确定细化程度与业务的所属方的风险信息需求等级匹配的至少一级风险信息；输出确定的风险信息，以便于业务的所属方获得确定的风险信息。

Description

一种风险信息输出、风险信息构建方法及装置
本申请要求2016年03月25日递交的申请号为201610176988.6、发明名称为“一种风险信息输出、风险信息构建方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及信息技术领域，尤其涉及一种风险信息输出、风险信息构建方法及装置。
背景技术
随着信息技术的迅速发展，很多业务都可以在网上进行，给人们的生活带来了很多便利，同时，在网络上进行的业务也是存在风险的。比如，某些业务可能是非法业务，或者，某些业务虽然是合法业务，但是由非法用户冒充合法用户进行的，等等。针对这类情况，网上的业务平台一般会基于预定的风险控制规则和/或风险控制模型，对在该业务平台上进行的业务进行风险控制，得出风险控制决策结果，并输出给该业务的所属方，并根据风险控制决策结果对该业务进行后续处理，其中，风险控制决策结果可以是：拒绝该业务或通过该业务等。
在现有技术中，在输出风险控制决策结果时，还可以输出相应的风险信息给业务的所属方，该风险信息用于解释导致该风险控制决策结果的原因，目前，各业务平台一般都是预先对使用的风险控制规则进行简单的翻译，然后作为风险信息输出给业务的所属方。
但是，在实际应用中，业务的不同所属方的行业经验、风险控制能力参差不齐，相应地，业务的不同所属方对风险信息的需求程度或深度也可能不同，而上述现有技术中输出风险信息时并未考虑到这种差异，因此，上述现有技术中输出的风险信息对于业务的不同所属方的适用性较差。
发明内容
本申请实施例提供一种风险信息输出、风险信息构建方法及装置，用以解决现有技术中输出的风险信息对于业务的不同所属方的适用性较差的问题。
本申请实施例提供的一种风险信息输出方法，包括：
根据预定的、包含一个或多个风险因子的风险控制规则和/或风险控制模型，在各所 述风险因子中，确定与业务的风险控制决策结果对应的风险因子，所述风险控制决策结果是根据所述风险控制规则和/或风险控制模型，以及涉及所述对应的风险因子的所述业务数据确定的；
确定与所述对应的风险因子对应的风险信息集合，所述对应的风险信息集合包含细化程度不同的多级风险信息，所述风险信息用于解释导致所述风险控制决策结果的原因；
根据所述业务的所属方的风险信息需求等级，在所述多级风险信息中，确定细化程度与所述业务的所属方的风险信息需求等级匹配的至少一级风险信息；
输出所述确定的风险信息，以便于所述业务的所属方获得所述确定的风险信息。
本申请实施例提供的一种风险信息输出装置，包括：
风险因子确定模块，用于根据预定的、包含一个或多个风险因子的风险控制规则和/或风险控制模型，在各所述风险因子中，确定与业务的风险控制决策结果对应的风险因子，所述风险控制决策结果是根据所述风险控制规则和/或风险控制模型，以及涉及所述对应的风险因子的所述业务数据确定的；
风险信息第一确定模块，用于确定与所述对应的风险因子对应的风险信息集合，所述对应的风险信息集合包含细化程度不同的多级风险信息，所述风险信息用于解释导致所述风险控制决策结果的原因；
风险信息第二确定模块，用于根据所述业务的所属方的风险信息需求等级，在所述多级风险信息中，确定细化程度与所述业务的所属方的风险信息需求等级匹配的至少一级风险信息；
风险信息输出模块，用于输出所述确定的风险信息，以便于所述业务的所属方获得所述确定的风险信息。
本申请实施例提供的一种风险信息构建方法，包括：
对预定的风险控制规则和/或风险控制模型进行拆解，获得所述风险控制规则和/或风险控制模型包含的一个或多个风险因子；
分别为获得的各所述风险因子构建一个对应的风险信息集合，所述对应的风险信息集合包含细化程度不同的多级风险信息，所述风险信息用于解释导致业务的风险控制决策结果的原因，所述风险控制决策结果是根据所述风险控制规则和/或风险控制模型，以及涉及所述对应的风险因子的所述业务数据确定的；
以便于在所述风险控制决策结果输出时，根据所述业务的所属方的风险信息需求等级，在所述多级风险信息中，确定并向所述业务的所属方输出细化程度与所述业务的所 属方的风险信息需求等级匹配的至少一级风险信息。
本申请实施例提供的一种风险信息构建装置，包括：
风险因子获得模块，用于对预定的风险控制规则和/或风险控制模型进行拆解，获得所述风险控制规则和/或风险控制模型包含的一个或多个风险因子；
风险信息构建模块，用于分别为获得的各所述风险因子构建一个对应的风险信息集合，所述对应的风险信息集合包含细化程度不同的多级风险信息，所述风险信息用于解释导致业务的风险控制决策结果的原因，所述风险控制决策结果是根据所述风险控制规则和/或风险控制模型，以及涉及所述对应的风险因子的所述业务数据确定的；
以便于在所述风险控制决策结果输出时，根据所述业务的所属方的风险信息需求等级，在所述多级风险信息中，确定并向所述业务的所属方输出细化程度与所述业务的所属方的风险信息需求等级匹配的至少一级风险信息。
本申请实施例通过上述至少一种技术方案，可以针对每个风险因子，构建对应于该风险因子的、细化程度不同的多级风险信息，以适应业务的不同所属方对于风险信息需求的不同层级的需求程度和/或深度，并且可以用不同的风险信息需求等级，表征对于风险信息需求的不同层级的需求程度和/或深度，进而，在输出风险信息时，可以根据业务的所属方的风险信息需求等级，在多级风险信息中，确定并输出细化程度与业务的所属方的风险信息需求等级匹配的至少一级风险信息，以便于业务的所属方获得输出的风险信息，因此，本申请的方案输出的风险信息对于业务的不同所属方的适用性较好，可以部分或全部地解决上述现有技术中的问题。
附图说明
此处所说明的附图用来提供对本申请的进一步理解，构成本申请的一部分，本申请的示意性实施例及其说明用于解释本申请，并不构成对本申请的不当限定。在附图中：
图1为本申请实施例提供的风险信息输出方法的过程；
图2为本申请实施例提供的在一种针对支付业务的风险控制场景下，为各风险因子构建的风险信息集合示意图的一部分；
图3为本申请实施例提供的在一种针对支付业务的风险控制场景下，为各风险因子构建的风险信息集合示意图的一部分；
图4为本申请实施例提供的风险信息构建方法的过程；
图5为本申请实施例提供的一种针对支付业务的风险控制场景下，用于输出风险信 息的infocode分级输出模块的结构示意图；
图6为本申请实施例提供的一种针对支付业务的风险控制场景下，infocode三层框架示例图；
图7为本申请实施例提供的对应于图1的风险信息输出装置结构示意图；
图8为本申请实施例提供的对应于图4的风险信息构建装置结构示意图。
具体实施方式
为使本申请的目的、技术方案和优点更加清楚，下面将结合本申请具体实施例及相应的附图对本申请技术方案进行清楚、完整地描述。显然，所描述的实施例仅是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
在背景技术中已经提到，风险信息可以用于解释导致对应的风险控制决策结果的原因，业务的不同所属方对风险信息的需求程度或深度也可能不同。
具体地，以业务的所属方是业务对应的商户为例。对于从业时间较长、经验丰富的商户，他们更希望看到风险控制决策结果背后的业务呈现出的各方面的风险信号，也即，更希望看到细化程度较高(比较具体的、深入的等)的风险信息，从而有助于提高自身风险控制水平、了解当前风险趋势；而对于行业新商户，他们更多投入在市场拓展，没有专业的团队接收和处理专业的风险信息输出，鉴于这种情况，细化程度较低(比较宏观的、浅显的等)的风险信息由于容易理解，因此，反而更适用于这类商户。
而现有技术中输出风险信息时并未考虑诸如上述差异，从而导致输出的风险信息对业务的不同所属方的适用性可能较差。
针对上述现有技术中的问题，本申请的方案的核心思想是：构建细化程度不同的多级(多个层级)风险信息，以适应业务的不同所属方对风险信息不同层级的需求程度和/或深度，从而提高输出的风险信息对业务的不同所属方的适用性，其中，对风险信息不同层级的需求程度和/或深度可以用不同的风险信息需求等级表征，多级风险信息可以是基于历史风险控制经验构建的。下面对本申请的方案进行详细说明。
图1为本申请实施例提供的风险信息输出方法的过程，该过程的执行主体可以是服务器或终端，更具体地，执行主体可以是服务器或终端上用于输出风险信息的功能模块。可作为所述服务器的设备包括但不限于：个人计算机、大中型计算机、计算机集群等；可作为所述终端的设备包括但不限于：手机、平板电脑、智能手表、车载移动台、个人 计算机等。执行主体并不构成对本申请的限定，为了便于描述，本申请实施例均以执行主体是服务器为例进行说明。
图1中的过程可以包括以下步骤：
S101：根据预定的、包含一个或多个风险因子的风险控制规则和/或风险控制模型，在各所述风险因子中，确定与业务的风险控制决策结果对应的风险因子，所述风险控制决策结果是根据所述风险控制规则和/或风险控制模型，以及涉及所述对应的风险因子的所述业务数据确定的。
在本申请实施例中，所述业务可以指“一笔业务”，针对每笔业务都可以分别执行一次图1中的过程。
在本申请实施例中，可以基于风险控制规则和/或风险控制模型，对业务进行风险控制，获得风险控制决策结果，其中，风险控制规则一般是由风险控制模型执行的，风险控制模型本身也可以包含有风险控制规则。在实际应用中，可以将风险控制规则、风险控制模型作为一个整体看待，并可以将这个整体称为：风险策略体系。
随着网络业务的日益复杂化，在对业务进行风险控制时，单一的风险行为刻画已难以精准地防控风险，因此，目前的风险控制规则在某些简单场景下虽然也可以是单一的行为特征，但在更多的场景下是多种行为特征的组合。对业务进行风险控制的过程，即是对该业务的各行为特征(可通过该业务的相关数据提取)与风险控制规则的各行为特征，分别对应匹配的过程，进而可以根据匹配结果进行决策，以确定风险控制决策结果。
进一步地，每种行为特征可以分别用一个风险因子进行概括。在这种情况下，风险控制规则可以包含有一个或多个风险因子，相应地，可以将风险控制规则拆解为一个或多个风险因子。类似地，风险控制模型也可以包含有一个或多个风险因子。
在本申请实施例中，涉及所述对应的风险因子的所述业务数据可以指：属于该业务的、反映该风险因子对应的行为特征的数据。风险控制决策结果可以对应于一个或多个风险因子，其中，若业务的风险控制决策结果是由属于该业务的、反映某个或某几个风险因子对应的行为特征导致的，则可以称：该风险控制决策结果对应于所述某个或某几个风险因子。
业务的风险决策结果具体可以包括：拒绝该业务、或通过该业务、或对该业务进行人工审核，等等。
S102：确定与所述对应的风险因子对应的风险信息集合，所述对应的风险信息集合包含细化程度不同的多级风险信息，所述风险信息用于解释导致所述风险控制决策结果 的原因。
由于不同的风险因子分别对应不同的行为特征，因此，对于对应于不同风险因子的风险决策结果，用于解释导致风险决策结果的风险信息相应地也可以不同。
如上所述，可以据此预先建立风险因子与风险信息之间的对应关系。具体的，在本申请实施例中，可以预先分别为每个风险因子构建一个对应的风险信息集合。风险信息集合中可以包含细化程度不同的多级风险信息，该风险信息集合对应的风险因子也即：该风险信息集合包含的多级风险信息对应的风险因子。
需要说明的是，本申请中所述的风险信息集合中包含多级风险信息，具体含义可以是：该多级风险信息已经构建完毕，并存放与该风险信息集合中；或者，该多级风险信息虽然尚未构建完毕，但是，用于构建该多级风险信息的素材已经在风险信息集合中准备就绪，当要输出该多级风险信息时，可以根据这些素材实时地构建出该多级风险信息，再输出。
在本申请实施例中，多级风险信息具体可以是多个层级的风险信息，所述多个层级的风险信息可以是逐层进行细化的。例如，顶层的风险信息是宏观的、笼统的，次层的风险信息是对顶层的风险信息进一步的细化(具体地解释，和/或扩充部分新内容等)，以此类推，除了顶层的风险信息以外，以下每层的风险信息都可以是对上一层风险信息进一步的细化。
当然，所述多个层级的风险信息也可以不具有“逐层细化”的关联关系。例如，可以是相对独立地构建各个层级的风险信息的，在这种情况下，并不一定要基于上一层风险信息构建本层的风险信息。
在本申请实施例中，对多级风险信息层级的划分可以是根据历史风险控制经验，和/或业务的所属方的需求等进行的。不同业务可以有不同的划分方式，本申请对多级风险信息层级的具体划分方式并不做限定。
S103：根据所述业务的所属方的风险信息需求等级，在所述多级风险信息中，确定细化程度与所述业务的所属方的风险信息需求等级匹配的至少一级风险信息。
在本申请实施例中，业务的所属方的风险信息需求等级可以用于表征：该业务的所属方的风险信息需求程度和/或深度。
在实际应用中，业务的所属方的风险信息需求等级可以由服务器根据历史数据推定，也可以由该业务的所属方指定等。前一种方式可以减少业务的所属方的操作，便利性较高；后一种方式由于是直接采用的所属方自身的意见，因此准确性较高。本申请对所述 风险信息需求的等级具体数量和等级具体划分方式并不做限定。
在本申请实施例中，业务的不同所属方的风险信息需求等级可能不同，相应地，可以分别向所述不同所属方输出对应层级的风险信息，以分别适应不同所属方的需求。
进一步地，对于多级风险信息，每个风险信息需求等级可以唯一匹配该多级风险信息中的其中一级风险信息，也可以同时匹配该多级风险信息中的其中两级甚至更多级风险信息。
S104：输出所述确定的风险信息，以便于所述业务的所属方获得所述确定的风险信息。
在本申请实施例中，可以将确定的风险信息直接输出给业务的所属方；也可以将该风险信息输出给其他设备或功能模块，再由其他设备或功能模块将该风险信息发送给业务的所属方；还可以先保存该风险信息，被动地等待业务的所属方查询后，再输出该风险信息；等等。
在本申请实施例中，风险控制决策结果、以及为该风险控制决策结果确定的风险信息可以由同一个设备输出，也可以分别由不同设备输出，本申请对此并不做限定。进一步地，本申请对该风险控制决策结果和该风险信息的输出时刻与输出先后顺序也不做限定，一般地，可以在输出该风险控制决策结果时，一并输出该风险信息，如此可以便于业务的所属方及时知晓导致该风险控制决策结果的原因。
通过上述方法，可以针对每个风险因子，构建对应于该风险因子的、细化程度不同的多级风险信息，以适应业务的不同所属方对于风险信息需求的不同层级的需求程度和/或深度，并且可以用不同的风险信息需求等级，表征对于风险信息需求的不同层级的需求程度和/或深度，进而，在输出风险信息时，可以根据业务的所属方的风险信息需求等级，在多级风险信息中，确定并输出细化程度与业务的所属方的风险信息需求等级匹配的至少一级风险信息，以便于业务的所属方获得输出的风险信息，因此，本申请的方案输出的风险信息对于业务的不同所属方的适用性较好，可以部分或全部地解决上述现有技术中的问题。
基于上述方法，本申请实施例还提供了上述方法的一些具体实施方案，以及扩展方案，下面进行说明。
在本申请实施例中，如前所述，风险控制规则和/或风险控制模型包含的每个风险因子可以分别与预定的一个风险信息集合建立有对应关系。在这种情况下，对于步骤S102，确定与所述对应的风险因子对应的风险信息集合，具体可以包括：根据所述对应关系， 在预定的各所述风险信息集合中，确定与所述对应的风险因子对应的风险信息集合。
当然，也可以不预先构建风险信息集合，而是在要使用时再实时地构建。在这种情况下，对于步骤S102，确定与所述对应的风险因子对应的风险信息集合，具体可以包括：根据所述对应的风险因子，构建与所述对应的风险因子对应的风险信息集合。
在本申请实施例中，在执行步骤S103的过程中，用到了业务的所属方的风险信息需求等级信息，为了便于实施本申请的方案，下面提供两种获得该风险信息需求等级信息的方式，作为示例：
第一种方式，可以预先由业务的所属方指定自己的风险信息需求等级，或者，由服务器指定业务的所属方的风险信息需求等级；然后将指定的风险信息需求等级信息写入预定配置文件中。则在执行步骤S103前，可以从该预定配置文件中读取到该风险需求等级信息。第一种方式可以减少业务的所属方的操作，便利性较高。
第二种方式，可以在要执行步骤S103时，再实时地由服务器推定业务的所属方的风险信息需求等级。具体地，服务器可以根据获取的所述业务的所属方的风险控制水平信息和/或风险控制需求信息，推定所述业务的所属方的风险信息需求等级。第二种方式由于参考了业务的所属方的相关信息，因此，准确性较高。
需要说明的是，本申请对风险控制水平信息和/或风险控制需求信息的获取方式并不做限定，可以是由服务器在与业务的所属方的历史交互过程中采集的，也可以是由服务器侧的管理人员通过与业务的所属方进行的沟通获知，并输入服务器的，等等。
在本申请实施例中，对于步骤S104，前面已经给出了若干实施方式。在实际应用中，比较常见的一种实施方式如下：
输出所述确定的风险信息，具体可以包括：在所述风险控制决策结果输出给所述业务的所属方时，向所述业务的所属方输出所述确定的风险信息。这种实施方式的优点是：业务的所属方可以在看到风险控制决策结果时，相对同步地看到对应的风险信息，业务的所属方的体验较好，便于根据该风险信息，有方向性地对业务进行后续处理，比如，去除风险后重新提交业务等。
“多级风险信息”、“风险信息需求等级”均是本申请的方案的重点之一，为了便于理解，在此分别对它们进一步地说明。
在本申请实施例中，所述业务的所属方的风险信息需求等级是预定的多个风险信息需求等级之一，用于表征所述业务的所属方的风险信息需求程度和/或深度。所述多个风险信息需求等级可以与所述多级风险信息一一对应并匹配，且表征风险信息需求程度和/ 或深度越高的风险信息需求等级，在所述多级风险信息中匹配的那一级风险信息的细化程度可以越高。
以所述业务是支付业务，该支付业务的所属方是该支付业务对应的商户为例。其中，所述支付业务可以主要基于第三方支付平台进行，也可以主要基于银行提供的支付平台进行。
可以将支付业务场景下的所有商户划分为三类，风险信息需求程度和/或深度相对低的一类称为：“弱管控商户”；风险信息需求程度和/或深度相对适中的一类称为：“一般管控商户”；风险信息需求程度和/或深度相对高的一类称为：“强管控商户”。
相应地，多级风险信息具体可以是三个层级的风险信息，在输出风险信息时，若业务的所属方是弱管控商户，则可以输出细化程度最低的那个层级的风险信息，若该所属方是一般管控商户，则可以输出细化程度适中的那个层级的风险信息，若该所属方是强管控商户，则可以输出细化程度最高的那个层级的风险信息。
在本申请实施例中，多级风险信息可以是根据所述风险控制规则和/或风险控制模型，以及相关的历史风险控制经验数据构建，以及以易于所述业务的所属方理解的描述方式进行描述的。
历史风险控制经验可以包括服务器在针对历史业务的风险控制过程中总结出的经验，以及业务的所属方提供的现成可用的经验等。例如，服务器可以根据业务的所属方已提供的信息，推定该所属方或与该所属方相似的其他所属方所需求的风险信息，以及什么样的风险信息是易于该所属方或与该所属方相似的其他所属方理解的；业务的所属方也可以主动告知服务器自己需要怎样的风险信息，以及自己容易理解的风险信息描述方式等；这些数据都可以作为历史风险控制经验数据。
所述风险信息可以是程序代码形式的信息，也可以是自然语言形式的信息。现有技术中对风险控制规则进行简单翻译就作为风险信息，而本申请的方案可以根据历史风险控制经验，以通俗易懂的语言描述风险信息，以易于业务的所属方理解，因此，基于本申请的方案输出的风险信息适用性更好。
本申请实施例提供了在一种针对支付业务的风险控制场景下，为各风险因子构建的风险信息集合示意图，如图2、图3组合所示。其中，图2和图3分别为该风险信息集合示意图的一部分，图2中“盗卡风险”的各子节点是在图3中示出的。
在该场景下，将风险信息称为“风险信息提示编码(infocode)”，将为各风险因子构建的风险信息集合合称为“infocode体系”。需要说明的是，这两个名称仅是一种示 例，并不构成对本申请的限定，在其他的场景，也可以用其他的名称命名。
在图2、图3中是以一个树形结构表示该infocode体系的，“风险信息提示编码体系”节点是该树形结构的根节点。在该树形结构的第二层一共有4个分支，每一个分支下分别是一个infocode集合，这些infocode集合分别为：“盗卡风险”节点内容及其所有子节点内容构成的集合、“盗账户风险”节点内容及其所有子节点内容构成的集合、“可信体系”节点内容及其所有子节点内容构成的集合、“银行系统拒绝”节点内容及其所有子节点内容构成的集合。
每个infocode集合分别对应于一个风险因子(风险因子省略未示出)，每个infocode集合包含多级infocode，从树形结构的第二层开始往下，每一层分别是多级infocode中的其中一级infocode，越往下的infocode的细化程度越高。
以“盗卡风险”节点所属的infocode集合为例，在图3中可以看见，该infocode集合包含有三级infocode。第一级infocode包括“盗卡风险”节点内容；第二级infocode包括“高风险账户”、“信息冲突”、“高风险环境”、“风险网络”、“高危事件属性”、“异常行为路径”、“速率”这7个节点内容。
可以看到，第二级infocode是对第一级infocode的进一步细化；类似地，第三级infocode是对第二级infocode的进一步细化，比如，第二级infocode中的“高风险账户”节点内容被细化为第三级infocode中的“新账户”、“休眠账户”、“情报完成度”、“账户登录时存在批量行为”这4个节点内容，第二级infocode中的“信息冲突”节点内容被细化为第三级infocode中的“交易信息存在冲突”、“信用卡验证信息冲突”这2个节点内容，等等。
从图2、图3可以看出，细化程度越高的infocode可以越具体地解释导致风险控制决策结果的原因。
需要说明的是，图2、图3中的节点内容可能并未完全示出，而且图2、图3仅是对多级infocode的示例而已，并不构成对本申请的限定。
上面对本申请实施例提供的风险信息输出方法进行了详细说明，基于同样的思路，本申请实施例还提供了一种风险信息构建方法。
图4为该风险信息构建方法的过程，该过程的执行主体可以与图1中的过程的执行主体相同，在此不赘述。
图4中的过程可以包括以下步骤：
S401：对预定的风险控制规则和/或风险控制模型进行拆解，获得所述风险控制规则 和/或风险控制模型包含的一个或多个风险因子。
S402：分别为获得的各所述风险因子构建一个对应的风险信息集合，所述对应的风险信息集合包含细化程度不同的多级风险信息，所述风险信息用于解释导致业务的风险控制决策结果的原因，所述风险控制决策结果是根据所述风险控制规则和/或风险控制模型，以及涉及所述对应的风险因子的所述业务数据确定的。
以便于在所述风险控制决策结果输出时，根据所述业务的所属方的风险信息需求等级，在所述多级风险信息中，确定并向所述业务的所属方输出细化程度与所述业务的所属方的风险信息需求等级匹配的至少一级风险信息。
通过图4中的方法，输出的风险信息对于业务的不同所属方的适用性较好，可以部分或全部地解决上述现有技术中的问题。
基于同样的思路，本申请实施例还提供一种针对支付业务的风险控制场景下，用于输出风险信息的infocode分级输出模块的结构示意图，如图5所示。
图5中的模块主要可以分为三个部分：
第一部分，infocode框架，用于根据支付业务平台的历史风险控制经验数据，构建infocode三层框架。多级风险信息即是基于该infocode三层框架构建的。
第二部分，infocode映射。这里的“映射”主要风险控制规则和/或风险控制模块包含的各风险因子(即：风险因子1、风险因子2、…、风险因子X)与各风险信息集合(即：infocode A、infocode B、…、infocode X)之间的对应关系映射。
其中，每个风险信息集合都包含有对应的多级风险信息，比如，infocode A包含了codeA1、codeA2、codeA3这三级逐级细化的风险信息。
第三部分，infocode输出。用于将多级风险信息分级输出给风险信息需求等级匹配的业务的所属方。
其中，风险信息需求等级一共有三个级别，即为：弱管控商户的级别、一般管控商户的级别、强管控商户的级别。其中，弱管控商户可以是无风险控制能力或不关注风险控制的小商户或新商户，一般管控商户可以是有一定风险控制能力，但无专业风险控制团队的中小型商户，强管控商户可以是有较强风险控制能力、已组建专业风险控制团队的大中型商户。
在实际应用中，服务器可以实时地分析每笔支付业务，在结合风险控制规则和风险控制模型给出“拒绝该业务”或“通过该业务”等风险控制决策结果时，也可以将对应级别的infocode输出给该业务的所属方。
进一步地，本申请实施例还提供了一种针对支付业务的风险控制场景下，infocode三层框架示例图，如图6所示。
在图6中，采用的风险控制规则称为“新账户冲突换多卡”，其可以拆解为“新账户”、“冲突”、“换多卡”这3个风险因子。
每个风险因子分别对应于一个infocode集合，风险因子可以从更为细化的维度进行刻画，进而可以构建出三级infocode，三级infocode即构成一个infocode集合。例如，“冲突”存在盗卡和盗账户风险(可作为第一级infocode)，进一步地，盗卡风险可以分为卡bin冲突、设备冲突等类型(可作为第二级infocode)，更进一步地，卡bin冲突可以分为发卡国与IP国冲突、发卡国与收货国冲突等(可作为第三级infocode)。
基于图5、图6中的方案，可以有效增强支付业务平台与商户的良性互动，提升支付风险控制体验。
需要说明的是，在以上各例中均是以“一共有三级的多级风险信息”作为“多级风险信息”的示例的，在实际应用中，多级风险信息也可以共有两级，或者共有三级以上，等等。另外，本申请的方案可以针对全部风险因子实施，也可以只针对部分风险因子实施。
以上为本申请实施例提供的风险信息输出方法、风险信息构建方法，基于同样的思路，本申请实施例还提供相应的风险信息输出装置、风险信息构建装置，如图7、图8所示。
图7为本申请实施例提供的对应于图1的风险信息输出装置结构示意图，具体包括：
风险因子确定模块701，用于根据预定的、包含一个或多个风险因子的风险控制规则和/或风险控制模型，在各所述风险因子中，确定与业务的风险控制决策结果对应的风险因子，所述风险控制决策结果是根据所述风险控制规则和/或风险控制模型，以及涉及所述对应的风险因子的所述业务数据确定的；
风险信息第一确定模块702，用于确定与所述对应的风险因子对应的风险信息集合，所述对应的风险信息集合包含细化程度不同的多级风险信息，所述风险信息用于解释导致所述风险控制决策结果的原因；
风险信息第二确定模块703，用于根据所述业务的所属方的风险信息需求等级，在所述多级风险信息中，确定细化程度与所述业务的所属方的风险信息需求等级匹配的至少一级风险信息；
风险信息输出模块704，用于输出所述确定的风险信息，以便于所述业务的所属方 获得所述确定的风险信息。
可选地，所述风险控制规则和/或风险控制模型包含的每个风险因子分别与预定的一个风险信息集合建立有对应关系；
风险信息第一确定模块702具体用于：根据所述对应关系，在预定的各所述风险信息集合中，确定与所述对应的风险因子对应的风险信息集合。
可选地，所述装置还包括：
风险信息需求等级确定模块705，用于在风险信息第二确定模块703确定细化程度与所述业务的所属方的风险信息需求等级匹配的至少一级风险信息前，确定预定配置文件中指定的所述业务的所属方的风险信息需求等级；或者，根据获取的所述业务的所属方的风险控制水平信息和/或风险控制需求信息，推定所述业务的所属方的风险信息需求等级。
可选地，风险信息输出模块704具体用于：在所述风险控制决策结果输出给所述业务的所属方时，向所述业务的所属方输出所述确定的风险信息。
可选地，所述业务的所属方的风险信息需求等级是预定的多个风险信息需求等级之一，用于表征所述业务的所属方的风险信息需求程度和/或深度；
所述多个风险信息需求等级与所述多级风险信息一一对应并匹配，且表征风险信息需求程度和/或深度越高的风险信息需求等级，在所述多级风险信息中匹配的那一级风险信息的细化程度越高。
可选地，所述多级风险信息是根据所述风险控制规则和/或风险控制模型，以及相关的历史风险控制经验数据构建，以及以易于所述业务的所属方理解的描述方式进行描述的。
可选地，所述业务的风险控制决策结果包括：拒绝所述业务、或通过所述业务、或需对所述业务进行人工审核。
可选地，所述业务包括支付业务，所述业务的所属方包括所述支付业务对应的商户。
图7中的装置具体可以位于服务器或终端上。
图8为本申请实施例提供的对应于图4的风险信息构建装置结构示意图，具体包括：
风险因子获得模块801，用于对预定的风险控制规则和/或风险控制模型进行拆解，获得所述风险控制规则和/或风险控制模型包含的一个或多个风险因子；
风险信息构建模块802，用于分别为获得的各所述风险因子构建一个对应的风险信息集合，所述对应的风险信息集合包含细化程度不同的多级风险信息，所述风险信息用 于解释导致业务的风险控制决策结果的原因，所述风险控制决策结果是根据所述风险控制规则和/或风险控制模型，以及涉及所述对应的风险因子的所述业务数据确定的；
以便于在所述风险控制决策结果输出时，根据所述业务的所属方的风险信息需求等级，在所述多级风险信息中，确定并向所述业务的所属方输出细化程度与所述业务的所属方的风险信息需求等级匹配的至少一级风险信息。
图8中的装置具体可以位于服务器或终端上。
需要说明的是，本申请提供的装置是与本申请提供的方法一一对应的，因此，所述装置也具有与所述方法类似的有益技术效果，由于上面已经对所述方法的有益技术效果进行了详细说明，因此，这里不再赘述所述装置的有益技术效果。
本领域内的技术人员应明白，本发明的实施例可提供为方法、系统、或计算机程序产品。因此，本发明可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本发明可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本发明是参照根据本发明实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
在一个典型的配置中，计算设备包括一个或多个处理器(CPU)、输入/输出接口、网 络接口和内存。
内存可能包括计算机可读介质中的非永久性存储器，随机存取存储器(RAM)和/或非易失性内存等形式，如只读存储器(ROM)或闪存(flash RAM)。内存是计算机可读介质的示例。
计算机可读介质包括永久性和非永久性、可移动和非可移动媒体可以由任何方法或技术来实现信息存储。信息可以是计算机可读指令、数据结构、程序的模块或其他数据。计算机的存储介质的例子包括，但不限于相变内存(PRAM)、静态随机存取存储器(SRAM)、动态随机存取存储器(DRAM)、其他类型的随机存取存储器(RAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、快闪记忆体或其他内存技术、只读光盘只读存储器(CD-ROM)、数字多功能光盘(DVD)或其他光学存储、磁盒式磁带，磁带磁磁盘存储或其他磁性存储设备或任何其他非传输介质，可用于存储可以被计算设备访问的信息。按照本文中的界定，计算机可读介质不包括暂存电脑可读媒体(transitory media)，如调制的数据信号和载波。
还需要说明的是，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、商品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、商品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、商品或者设备中还存在另外的相同要素。
以上所述仅为本申请的实施例而已，并不用于限制本申请。对于本领域技术人员来说，本申请可以有各种更改和变化。凡在本申请的精神和原理之内所作的任何修改、等同替换、改进等，均应包含在本申请的权利要求范围之内。

Claims (18)

  1. 一种风险信息输出方法，其特征在于，包括：
    根据预定的、包含一个或多个风险因子的风险控制规则和/或风险控制模型，在各所述风险因子中，确定与业务的风险控制决策结果对应的风险因子，所述风险控制决策结果是根据所述风险控制规则和/或风险控制模型，以及涉及所述对应的风险因子的所述业务数据确定的；
    确定与所述对应的风险因子对应的风险信息集合，所述对应的风险信息集合包含细化程度不同的多级风险信息，所述风险信息用于解释导致所述风险控制决策结果的原因；
    根据所述业务的所属方的风险信息需求等级，在所述多级风险信息中，确定细化程度与所述业务的所属方的风险信息需求等级匹配的至少一级风险信息；
    输出所述确定的风险信息，以便于所述业务的所属方获得所述确定的风险信息。
  2. 如权利要求1所述的方法，其特征在于，所述风险控制规则和/或风险控制模型包含的每个风险因子分别与预定的一个风险信息集合建立有对应关系；
    确定与所述对应的风险因子对应的风险信息集合，具体包括：
    根据所述对应关系，在预定的各所述风险信息集合中，确定与所述对应的风险因子对应的风险信息集合。
  3. 如权利要求1所述的方法，其特征在于，确定细化程度与所述业务的所属方的风险信息需求等级匹配的至少一级风险信息前，所述方法还包括：
    确定预定配置文件中指定的所述业务的所属方的风险信息需求等级；或者，
    根据获取的所述业务的所属方的风险控制水平信息和/或风险控制需求信息，推定所述业务的所属方的风险信息需求等级。
  4. 如权利要求1所述的方法，其特征在于，输出所述确定的风险信息，具体包括：
    在所述风险控制决策结果输出给所述业务的所属方时，向所述业务的所属方输出所述确定的风险信息。
  5. 如权利要求1所述的方法，其特征在于，所述业务的所属方的风险信息需求等级是预定的多个风险信息需求等级之一，用于表征所述业务的所属方的风险信息需求程度和/或深度；
    所述多个风险信息需求等级与所述多级风险信息一一对应并匹配，且表征风险信息需求程度和/或深度越高的风险信息需求等级，在所述多级风险信息中匹配的那一级风险 信息的细化程度越高。
  6. 如权利要求1～5任一项所述的方法，所述多级风险信息是根据所述风险控制规则和/或风险控制模型，以及相关的历史风险控制经验数据构建，以及以易于所述业务的所属方理解的描述方式进行描述的。
  7. 如权利要求1～5任一项所述的方法，其特征在于，所述业务的风险控制决策结果包括：拒绝所述业务、或通过所述业务、或需对所述业务进行人工审核。
  8. 如权利要求1～5任一项所述的方法，其特征在于，所述业务包括支付业务，所述业务的所属方包括所述支付业务对应的商户。
  9. 一种风险信息构建方法，其特征在于，包括：
    对预定的风险控制规则和/或风险控制模型进行拆解，获得所述风险控制规则和/或风险控制模型包含的一个或多个风险因子；
    分别为获得的各所述风险因子构建一个对应的风险信息集合，所述对应的风险信息集合包含细化程度不同的多级风险信息，所述风险信息用于解释导致业务的风险控制决策结果的原因，所述风险控制决策结果是根据所述风险控制规则和/或风险控制模型，以及涉及所述对应的风险因子的所述业务数据确定的；
    以便于在所述风险控制决策结果输出时，根据所述业务的所属方的风险信息需求等级，在所述多级风险信息中，确定并向所述业务的所属方输出细化程度与所述业务的所属方的风险信息需求等级匹配的至少一级风险信息。
  10. 一种风险信息输出装置，其特征在于，包括：
    风险因子确定模块，用于根据预定的、包含一个或多个风险因子的风险控制规则和/或风险控制模型，在各所述风险因子中，确定与业务的风险控制决策结果对应的风险因子，所述风险控制决策结果是根据所述风险控制规则和/或风险控制模型，以及涉及所述对应的风险因子的所述业务数据确定的；
    风险信息第一确定模块，用于确定与所述对应的风险因子对应的风险信息集合，所述对应的风险信息集合包含细化程度不同的多级风险信息，所述风险信息用于解释导致所述风险控制决策结果的原因；
    风险信息第二确定模块，用于根据所述业务的所属方的风险信息需求等级，在所述多级风险信息中，确定细化程度与所述业务的所属方的风险信息需求等级匹配的至少一级风险信息；
    风险信息输出模块，用于输出所述确定的风险信息，以便于所述业务的所属方获得 所述确定的风险信息。
  11. 如权利要求10所述的装置，其特征在于，所述风险控制规则和/或风险控制模型包含的每个风险因子分别与预定的一个风险信息集合建立有对应关系；
    所述风险信息第一确定模块具体用于：根据所述对应关系，在预定的各所述风险信息集合中，确定与所述对应的风险因子对应的风险信息集合。
  12. 如权利要求10所述的装置，其特征在于，所述装置还包括：
    风险信息需求等级确定模块，用于在所述风险信息第二确定模块确定细化程度与所述业务的所属方的风险信息需求等级匹配的至少一级风险信息前，确定预定配置文件中指定的所述业务的所属方的风险信息需求等级；或者，根据获取的所述业务的所属方的风险控制水平信息和/或风险控制需求信息，推定所述业务的所属方的风险信息需求等级。
  13. 如权利要求10所述的装置，其特征在于，所述风险信息输出模块具体用于：在所述风险控制决策结果输出给所述业务的所属方时，向所述业务的所属方输出所述确定的风险信息。
  14. 如权利要求10所述的装置，其特征在于，所述业务的所属方的风险信息需求等级是预定的多个风险信息需求等级之一，用于表征所述业务的所属方的风险信息需求程度和/或深度；
    所述多个风险信息需求等级与所述多级风险信息一一对应并匹配，且表征风险信息需求程度和/或深度越高的风险信息需求等级，在所述多级风险信息中匹配的那一级风险信息的细化程度越高。
  15. 如权利要求10～14任一项所述的装置，其特征在于，所述多级风险信息是根据所述风险控制规则和/或风险控制模型，以及相关的历史风险控制经验数据构建，以及以易于所述业务的所属方理解的描述方式进行描述的。
  16. 如权利要求10～14任一项所述的装置，其特征在于，所述业务的风险控制决策结果包括：拒绝所述业务、或通过所述业务、或需对所述业务进行人工审核。
  17. 如权利要求10～14任一项所述的装置，其特征在于，所述业务包括支付业务，所述业务的所属方包括所述支付业务对应的商户。
  18. 一种风险信息构建装置，其特征在于，包括：
    风险因子获得模块，用于对预定的风险控制规则和/或风险控制模型进行拆解，获得所述风险控制规则和/或风险控制模型包含的一个或多个风险因子；
    风险信息构建模块，用于分别为获得的各所述风险因子构建一个对应的风险信息集合，所述对应的风险信息集合包含细化程度不同的多级风险信息，所述风险信息用于解释导致业务的风险控制决策结果的原因，所述风险控制决策结果是根据所述风险控制规则和/或风险控制模型，以及涉及所述对应的风险因子的所述业务数据确定的；
    以便于在所述风险控制决策结果输出时，根据所述业务的所属方的风险信息需求等级，在所述多级风险信息中，确定并向所述业务的所属方输出细化程度与所述业务的所属方的风险信息需求等级匹配的至少一级风险信息。
PCT/CN2017/077248 2016-03-25 2017-03-20 一种风险信息输出、风险信息构建方法及装置 WO2017162113A1 (zh)

Priority Applications (7)

Application Number Priority Date Filing Date Title
EP17769390.0A EP3435260A4 (en) 2016-03-25 2017-03-20 METHOD AND DEVICE FOR TRANSMITTING RISK INFORMATION AND BUILDING RISK INFORMATION
JP2018550377A JP6696001B2 (ja) 2016-03-25 2017-03-20 リスク情報を出力し、リスク情報を構築するための方法及びデバイス
KR1020187030588A KR102211374B1 (ko) 2016-03-25 2017-03-20 리스크 정보를 출력하고 리스크 정보를 구축하기 위한 방법 및 디바이스
SG11201808341SA SG11201808341SA (en) 2016-03-25 2017-03-20 Method and device for outputting risk information and constructing risk information
US16/140,039 US20190026744A1 (en) 2016-03-25 2018-09-24 Method and device for outputting risk information and constructing risk information
PH12018502049A PH12018502049A1 (en) 2016-03-25 2018-09-25 Method and device for outputting risk information and constructing risk information
US16/722,609 US20200143378A1 (en) 2016-03-25 2019-12-20 Method and device for outputting risk information and constructing risk information

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610176988.6 2016-03-25
CN201610176988.6A CN107230008B (zh) 2016-03-25 2016-03-25 一种风险信息输出、风险信息构建方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/140,039 Continuation US20190026744A1 (en) 2016-03-25 2018-09-24 Method and device for outputting risk information and constructing risk information

Publications (1)

Publication Number Publication Date
WO2017162113A1 true WO2017162113A1 (zh) 2017-09-28

Family

ID=59899338

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/077248 WO2017162113A1 (zh) 2016-03-25 2017-03-20 一种风险信息输出、风险信息构建方法及装置

Country Status (9)

Country Link
US (2) US20190026744A1 (zh)
EP (1) EP3435260A4 (zh)
JP (1) JP6696001B2 (zh)
KR (1) KR102211374B1 (zh)
CN (2) CN107230008B (zh)
PH (1) PH12018502049A1 (zh)
SG (1) SG11201808341SA (zh)
TW (1) TWI668655B (zh)
WO (1) WO2017162113A1 (zh)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108154368A (zh) * 2017-12-26 2018-06-12 阿里巴巴集团控股有限公司 一种资源风险的检测方法、装置及设备
CN109447455A (zh) * 2018-10-24 2019-03-08 海南新软软件有限公司 一种企业内部风控引擎搭建方法及装置
CN110148000A (zh) * 2019-04-17 2019-08-20 阿里巴巴集团控股有限公司 一种应用于支付平台的安全管控系统和方法
CN110766040A (zh) * 2019-09-03 2020-02-07 阿里巴巴集团控股有限公司 用于对交易风险数据进行风险聚类的方法及装置

Families Citing this family (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110020862B (zh) * 2018-01-10 2021-10-29 中国移动通信有限公司研究院 一种业务风险评估方法、装置和计算机可读存储介质
CN108876600B (zh) * 2018-08-20 2023-09-05 平安科技（深圳）有限公司 预警信息推送方法、装置、计算机设备和介质
CN109034660B (zh) * 2018-08-22 2023-07-14 平安科技（深圳）有限公司 基于预测模型的风险控制策略的确定方法及相关装置
US11924290B2 (en) * 2018-10-26 2024-03-05 Dell Products, Lp Aggregated stochastic method for predictive system response
US10949853B2 (en) * 2018-11-07 2021-03-16 Paypal, Inc. Systems and methods for providing concurrent data loading and rules execution in risk evaluations
CN109472609B (zh) * 2018-11-09 2022-01-25 创新先进技术有限公司 一种风控原因确定方法及装置
CN109656904B (zh) * 2018-11-13 2023-05-30 上海百事通信息技术股份有限公司 一种案件风险检测方法及系统
CN109583731B (zh) * 2018-11-20 2023-04-18 创新先进技术有限公司 一种风险识别方法、装置及设备
CN110020766A (zh) * 2018-11-21 2019-07-16 阿里巴巴集团控股有限公司 风险控制方法、装置、服务器及存储介质
CN110020780A (zh) * 2019-02-26 2019-07-16 阿里巴巴集团控股有限公司 信息输出的方法、装置和电子设备
CN110059920B (zh) * 2019-03-08 2021-08-06 创新先进技术有限公司 风险决策方法及装置
CN110147925B (zh) * 2019-04-10 2023-10-03 创新先进技术有限公司 一种风险决策方法、装置、设备及系统
CN110245954B (zh) * 2019-05-27 2023-06-27 创新先进技术有限公司 用于风险控制的方法和装置
CN110288462A (zh) * 2019-05-31 2019-09-27 北京随信云链科技有限公司 风控系统、风控方法、计算机可读存储介质和计算设备
US10657591B1 (en) 2019-08-16 2020-05-19 Coupang Corp. Computer-implemented systems and methods for real-time risk-informed return item collection using an automated kiosk
CN111144744B (zh) * 2019-12-26 2022-06-24 支付宝(杭州)信息技术有限公司 业务处理方法、装置及电子设备
CN113888181A (zh) * 2021-10-25 2022-01-04 支付宝(杭州)信息技术有限公司 业务处理及其风险检测策略体系的构建方法、装置及设备
CN116703148B (zh) * 2023-04-26 2024-01-23 中国安全生产科学研究院 基于云计算的矿山企业风险画像方法

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101764798A (zh) * 2009-07-01 2010-06-30 北京华胜天成科技股份有限公司 一种基于客户端的安全管理系统和方法
CN103455719A (zh) * 2013-08-27 2013-12-18 柳州市博源环科科技有限公司 一种制造业环境风险源评价方法

Family Cites Families (28)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1014287A3 (en) * 1998-12-14 2002-04-24 General Electric Company Multi-source information fusion system for dynamic risk assessment
AU2002228700A1 (en) * 2000-11-02 2002-05-15 Cybersource Corporation Method and apparatus for evaluating fraud risk in an electronic commerce transaction
US20020138371A1 (en) * 2001-03-20 2002-09-26 David Lawrence Online transaction risk management
US7865427B2 (en) * 2001-05-30 2011-01-04 Cybersource Corporation Method and apparatus for evaluating fraud risk in an electronic commerce transaction
US8510300B2 (en) * 2004-07-02 2013-08-13 Goldman, Sachs & Co. Systems and methods for managing information associated with legal, compliance and regulatory risk
US8336085B2 (en) * 2004-11-15 2012-12-18 Microsoft Corporation Tuning product policy using observed evidence of customer behavior
US8095441B2 (en) * 2005-11-01 2012-01-10 Barclays Capital Inc. Method and system for administering money laundering prevention program
WO2008140683A2 (en) * 2007-04-30 2008-11-20 Sheltonix, Inc. A method and system for assessing, managing, and monitoring information technology risk
CN101655966A (zh) * 2008-08-19 2010-02-24 阿里巴巴集团控股有限公司 一种贷款风险控制方法及系统
CN101388104A (zh) * 2008-10-15 2009-03-18 中国工商银行股份有限公司 基于客户间关系对融资风险进行评价的系统及方法
US8185430B2 (en) * 2009-01-30 2012-05-22 Bank Of America Corporation Supplier stratification
TW201040858A (en) * 2009-05-04 2010-11-16 Alibaba Group Holding Ltd Method for loan risk control and system thereof
CN101714273A (zh) * 2009-05-26 2010-05-26 北京银丰新融科技开发有限公司 一种基于规则引擎的银行异常业务监控方法和系统
US8020763B1 (en) * 2009-06-30 2011-09-20 Intuit Inc. Method and system for assessing merchant risk during payment transaction
CN102214348A (zh) * 2010-04-07 2011-10-12 Sap股份公司 自上而下的基于风险的审计方法的数据管理
US20120053982A1 (en) * 2010-09-01 2012-03-01 Bank Of America Corporation Standardized Technology and Operations Risk Management (STORM)
CN101976419A (zh) * 2010-10-19 2011-02-16 中国工商银行股份有限公司 交易数据的风险监控处理方法和系统
US20130080352A1 (en) * 2011-09-22 2013-03-28 Frank Russell Company Method of creating and maintaining multi-manager exchange traded funds
CN103123712A (zh) * 2011-11-17 2013-05-29 阿里巴巴集团控股有限公司 一种网络行为数据的监控方法和系统
US20140052494A1 (en) * 2012-08-16 2014-02-20 Bank Of America Identifying Scenarios and Business Units that Benefit from Scenario Planning for Operational Risk Scenario Analysis Using Analytical and Quantitative Methods
US20140316959A1 (en) * 2013-04-18 2014-10-23 International Business Machines Corporation Estimating financial risk based on non-financial data
US20140324519A1 (en) * 2013-04-25 2014-10-30 Bank Of America Corporation Operational Risk Decision-Making Framework
CN103279883B (zh) * 2013-05-02 2016-06-08 上海携程商务有限公司 电子支付交易风险控制方法及系统
US10380575B2 (en) * 2014-06-26 2019-08-13 Capital One Services, Llc Systems and methods for transaction pre authentication
CN109063969B (zh) * 2014-07-09 2022-02-01 创新先进技术有限公司 一种账户风险评估的方法及装置
US20160292687A1 (en) * 2014-10-13 2016-10-06 Empire Technology Development Llc Verification location determination for entity presence confirmation of online purchases
US20160232600A1 (en) * 2015-02-08 2016-08-11 Visa International Service Association One-Click Checkout Apparatuses, Systems, and Methods
CN105282131B (zh) * 2015-02-10 2018-10-23 中国移动通信集团广东有限公司 基于风险项扫描的信息安全评估方法、装置及系统

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101764798A (zh) * 2009-07-01 2010-06-30 北京华胜天成科技股份有限公司 一种基于客户端的安全管理系统和方法
CN103455719A (zh) * 2013-08-27 2013-12-18 柳州市博源环科科技有限公司 一种制造业环境风险源评价方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3435260A4 *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108154368A (zh) * 2017-12-26 2018-06-12 阿里巴巴集团控股有限公司 一种资源风险的检测方法、装置及设备
CN109447455A (zh) * 2018-10-24 2019-03-08 海南新软软件有限公司 一种企业内部风控引擎搭建方法及装置
CN110148000A (zh) * 2019-04-17 2019-08-20 阿里巴巴集团控股有限公司 一种应用于支付平台的安全管控系统和方法
CN110766040A (zh) * 2019-09-03 2020-02-07 阿里巴巴集团控股有限公司 用于对交易风险数据进行风险聚类的方法及装置
CN110766040B (zh) * 2019-09-03 2024-02-06 创新先进技术有限公司 用于对交易风险数据进行风险聚类的方法及装置

Also Published As

Publication number Publication date
CN111507638A (zh) 2020-08-07
TWI668655B (zh) 2019-08-11
KR20180129850A (ko) 2018-12-05
US20200143378A1 (en) 2020-05-07
CN111507638B (zh) 2024-03-05
US20190026744A1 (en) 2019-01-24
SG11201808341SA (en) 2018-10-30
KR102211374B1 (ko) 2021-02-04
JP6696001B2 (ja) 2020-05-20
TW201738825A (zh) 2017-11-01
JP2019511059A (ja) 2019-04-18
PH12018502049A1 (en) 2019-07-01
EP3435260A1 (en) 2019-01-30
CN107230008B (zh) 2020-03-27
EP3435260A4 (en) 2019-09-04
CN107230008A (zh) 2017-10-03

Similar Documents

Publication Publication Date Title
WO2017162113A1 (zh) 一种风险信息输出、风险信息构建方法及装置
US11544794B2 (en) Claim settlement method and apparatus employing blockchain technology
WO2020192272A1 (zh) 基于区块链的转账方法、系统、计算设备及存储介质
US11074350B2 (en) Method and device for controlling data risk
CN105337928B (zh) 用户身份识别方法、安全保护问题生成方法及装置
WO2018014814A1 (zh) 终端规则引擎装置、终端规则运行方法
CN110020542B (zh) 数据读写方法及装置、电子设备
CN107368259A (zh) 一种向区块链系统中写入业务数据的方法和装置
CN110032598B (zh) 字段更新方法及装置、电子设备
US10599985B2 (en) Systems and methods for expediting rule-based data processing
CN112184191B (zh) 基于区块链的资源交易方法、装置及系统
CN106033510B (zh) 一种用户设备识别方法及系统
US10217178B2 (en) Customer identity verification
US20160034861A1 (en) Method and apparatus of controlling network payment
WO2020108152A1 (zh) 身份数据的防误用方法及装置、电子设备
WO2020125224A1 (zh) 数据结构的读取及更新方法、装置、电子设备
WO2020038099A1 (zh) 一种签约风险量化方法、代扣风险量化方法、装置及设备
CN114463110A (zh) 一种基于区块链的授信系统和方法
CN113094414A (zh) 流转图谱生成方法及装置
CN113469696A (zh) 一种用户异常度评估方法、装置及计算机可读存储介质
CN106557472B (zh) 用户数据库的建立方法和装置
CN113888322A (zh) 一种信用评价方法、系统、存储介质及电子设备
CN114418764A (zh) 一种基于区块链和sql的数据处理方法
CN115730574A (zh) 生成数据表的方法及装置
CN118071512A (zh) 穿透式风险分析方法、装置、计算机设备和存储介质

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 2018550377

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 11201808341S

Country of ref document: SG

ENP Entry into the national phase

Ref document number: 20187030588

Country of ref document: KR

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 2017769390

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2017769390

Country of ref document: EP

Effective date: 20181025

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17769390

Country of ref document: EP

Kind code of ref document: A1