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
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2017/077248
Other languages
English (en)
French (fr)
Chinese (zh)
Inventor
杨陆毅
陆青
云蕾
王文雯
崔阳
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Alibaba Group Holding Ltd
Original Assignee
Alibaba Group Holding Ltd
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 Alibaba Group Holding Ltd filed Critical Alibaba Group Holding Ltd
Priority to MYPI2018703487A priority Critical patent/MY204882A/en
Priority to KR1020187030588A priority patent/KR102211374B1/ko
Priority to SG11201808341SA priority patent/SG11201808341SA/en
Priority to EP17769390.0A priority patent/EP3435260A4/en
Priority to JP2018550377A priority patent/JP6696001B2/ja
Publication of WO2017162113A1 publication Critical patent/WO2017162113A1/zh
Priority to US16/140,039 priority patent/US20190026744A1/en
Priority to PH12018502049A priority patent/PH12018502049A1/en
Anticipated expiration legal-status Critical
Priority to US16/722,609 priority patent/US20200143378A1/en
Ceased legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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 OR CALCULATING; 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 OR CALCULATING; 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 OR CALCULATING; 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 OR CALCULATING; 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 OR CALCULATING; 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)
PCT/CN2017/077248 2016-03-25 2017-03-20 一种风险信息输出、风险信息构建方法及装置 Ceased WO2017162113A1 (zh)

Priority Applications (8)

Application Number Priority Date Filing Date Title
MYPI2018703487A MY204882A (en) 2016-03-25 2017-03-20 Method and device for outputting risk information and constructing risk information
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
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 リスク情報を出力し、リスク情報を構築するための方法及びデバイス
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 Ceased WO2017162113A1 (zh) 2016-03-25 2017-03-20 一种风险信息输出、风险信息构建方法及装置

Country Status (10)

Country Link
US (2) US20190026744A1 (cg-RX-API-DMAC7.html)
EP (1) EP3435260A4 (cg-RX-API-DMAC7.html)
JP (1) JP6696001B2 (cg-RX-API-DMAC7.html)
KR (1) KR102211374B1 (cg-RX-API-DMAC7.html)
CN (2) CN111507638B (cg-RX-API-DMAC7.html)
MY (1) MY204882A (cg-RX-API-DMAC7.html)
PH (1) PH12018502049A1 (cg-RX-API-DMAC7.html)
SG (1) SG11201808341SA (cg-RX-API-DMAC7.html)
TW (1) TWI668655B (cg-RX-API-DMAC7.html)
WO (1) WO2017162113A1 (cg-RX-API-DMAC7.html)

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 (20)

* 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 支付宝(杭州)信息技术有限公司 业务处理及其风险检测策略体系的构建方法、装置及设备
CN114819542B (zh) * 2022-04-07 2025-10-03 中国联合网络通信集团有限公司 风险数据的处理方法、设备及存储介质
CN116703148B (zh) * 2023-04-26 2024-01-23 中国安全生产科学研究院 基于云计算的矿山企业风险画像方法
CN119166661B (zh) * 2024-11-20 2025-04-11 恒生电子股份有限公司 信息展示方法及系统

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
US8744894B2 (en) * 2007-04-30 2014-06-03 Evantix Grc, Llc 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
CN105243252B (zh) * 2014-07-09 2018-08-07 阿里巴巴集团控股有限公司 一种账户风险评估的方法及装置
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
JP2019511059A (ja) 2019-04-18
TW201738825A (zh) 2017-11-01
TWI668655B (zh) 2019-08-11
CN111507638A (zh) 2020-08-07
EP3435260A4 (en) 2019-09-04
JP6696001B2 (ja) 2020-05-20
PH12018502049A1 (en) 2019-07-01
KR102211374B1 (ko) 2021-02-04
CN111507638B (zh) 2024-03-05
KR20180129850A (ko) 2018-12-05
US20190026744A1 (en) 2019-01-24
SG11201808341SA (en) 2018-10-30
CN107230008B (zh) 2020-03-27
CN107230008A (zh) 2017-10-03
MY204882A (en) 2024-09-20
EP3435260A1 (en) 2019-01-30
US20200143378A1 (en) 2020-05-07

Similar Documents

Publication Publication Date Title
WO2017162113A1 (zh) 一种风险信息输出、风险信息构建方法及装置
US11544794B2 (en) Claim settlement method and apparatus employing blockchain technology
TWI673666B (zh) 資料風險控制的方法及裝置
WO2020192272A1 (zh) 基于区块链的转账方法、系统、计算设备及存储介质
CN110032598B (zh) 字段更新方法及装置、电子设备
CN111539811B (zh) 风险账户的识别方法及装置
WO2018014814A1 (zh) 终端规则引擎装置、终端规则运行方法
CN110032599A (zh) 数据结构的读取及更新方法、装置、电子设备
US10599985B2 (en) Systems and methods for expediting rule-based data processing
US20160343101A1 (en) Customer identity verification
WO2020108152A1 (zh) 身份数据的防误用方法及装置、电子设备
CN113888322B (zh) 一种信用评价方法、系统、存储介质及电子设备
CN113094414A (zh) 流转图谱生成方法及装置
CN113378183A (zh) 基于多方安全计算的用户隐私保护方法、装置和系统
CN114625899B (zh) 信息处理方法、装置、电子设备以及存储介质
CN116823279A (zh) 申诉处理方法、装置、存储介质以及终端
CN106557472B (zh) 用户数据库的建立方法和装置
HK40034907B (zh) 一种风险信息输出、风险信息构建方法及装置
HK40034907A (en) Risk information output method and device and risk information construction method and device
CN118278928A (zh) 终端支付管理方法、装置、存储介质和计算机设备
CN120872833A (zh) 一种流量回放测试方法、装置、设备、介质及程序产品
CN118550886A (zh) 凭证信息的动态配置方法、装置、计算机设备和介质
CN118071512A (zh) 穿透式风险分析方法、装置、计算机设备和存储介质
CN121210461A (zh) 基于区块链的数据处理方法、相关装置和介质
CN115496612A (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