WO2018149386A1 - 一种风险管控方法及装置 - Google Patents
一种风险管控方法及装置 Download PDFInfo
- Publication number
- WO2018149386A1 WO2018149386A1 PCT/CN2018/076514 CN2018076514W WO2018149386A1 WO 2018149386 A1 WO2018149386 A1 WO 2018149386A1 CN 2018076514 W CN2018076514 W CN 2018076514W WO 2018149386 A1 WO2018149386 A1 WO 2018149386A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- event
- verification
- weight
- determining
- risk
- Prior art date
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
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F17/00—Digital computing or data processing equipment or methods, specially adapted for specific functions
- G06F17/10—Complex mathematical operations
- G06F17/16—Matrix or vector computation, e.g. matrix-matrix or matrix-vector multiplication, matrix factorization
-
- 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
-
- 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
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/08—Insurance
Definitions
- the present application relates to the field of Internet information processing technologies and computer technologies, and in particular, to a risk management method and apparatus.
- Risk management is an important part of payment security management, which includes determining what control actions to output for risky trading events, that is, controlling decisions.
- the control actions include, but are not limited to, directly letting go, performing various verifications on transaction events such as short messages, faces, and the like.
- Control decision-making is a safety valve for payment behavior risk control, and also a direct contact point for customer experience. Whether the strategy of controlling decision-making is reasonable will directly affect the effect of risk control and the quality of user experience.
- the ideal control decision is reflected in two aspects: on the one hand, the direct release of as many outputs as possible for secure trading events, and on the other hand, the most likely output of the risky trading events is difficult to pass. . These two aspects affect the user experience and risk control quality of the control decision.
- the traditional methods of decision-making are divided into two categories: first, based on rules or rule trees, that is, first to give some rules for control decisions based on business understanding, including but not limited to factors such as amount, scenario, risk size, etc., and then Comparing a specific transaction event with a rule or a rule tree, and satisfying a specific rule or a definition in the rule tree, outputting a corresponding control method, for example, the transaction event is a low-risk, small-value, offline payment taxi service, In the rule tree, it corresponds to the control action of outputting SMS verification.
- Second, on the basis of the first method the user's research or a similar method is further combined, and the rules are adjusted through the results of the research. This approach helps improve the customer experience because the results of the survey can include personalized content for a specific category of users to a certain extent.
- the present invention provides a risk management and control method and device for solving the problem of excessive dependence on subjective understanding in the existing control decision. Further, the present application can also solve the problem that the prior art cannot balance transaction security and user experience. Therefore, in the control decision-making, multiple business indicators are considered, such as minimizing the financial loss caused by the stolen equipment bypass control, minimizing the interruption to normal users, and minimizing the cost of verifying the identity. In other words, the problem to be solved in this application is how to output the most appropriate management and control method based on indicators such as transaction security and user experience.
- the embodiment of the present application provides a risk management method, including:
- the embodiment of the present application further provides a risk management device, including:
- a receiving module configured to receive an object event to be controlled
- the processing module is configured to: determine an alternative verification mode set, and determine an output weight of at least part of the candidate verification mode in the candidate verification mode set;
- an output module configured to output, according to the output weight corresponding to the candidate verification mode, a verification manner for performing risk management on the object event from the candidate verification mode.
- the embodiment of the present application further provides a transaction management method, which uses the risk management method proposed by the present application.
- the embodiment of the present application also provides a transaction management device that uses the risk management device proposed by the present application.
- the weights of various outputs in the process of controlling the decision are weighted, thereby avoiding the excessive dependence of the prior decision process on subjective understanding.
- various factors can be included in the risk decision-making, such as risk applicability, equipment availability, user preferences, scenario suitability, and so on.
- quantitative measures are taken into account for multiple business indicators, such as reducing theft, which leads to financial losses caused by bypassing control, reducing the interruption to normal users, thereby improving the user experience and reducing the cost of identity verification calculation.
- this application can minimize the dependence on rule makers on business understanding through data. Based on process quantification, existing data can be maximized.
- the solution of the present application is easy to adjust and expand, and different changes such as new business scenarios and new identity verification methods can be easily incorporated into the quantitative concept of the present application.
- FIG. 1 is a schematic flowchart of a risk management method according to an embodiment of the present application.
- FIG. 2 is a schematic flowchart of a payment risk management and control method according to an embodiment of the present application
- FIG. 3 is a schematic structural diagram of a risk management device according to an embodiment of the present application.
- FIG. 4 is a schematic structural diagram of a payment risk management device according to an embodiment of the present application.
- an embodiment of the present application provides a risk management method.
- the risk management includes any process that needs to make a decision based on the risk event itself or select a control action for the risk event.
- the optional control action is two or more.
- the mentioned risk events include various types, such as security check in different scenarios, account login, online transaction and payment identity verification, and the like. It can be understood that for each of the above events, there are various alternative control methods. In other words, all the events involving the risk and the control decision may belong to the object event in the embodiment of the present application, and are not further limited herein.
- the user initiates an event, that is, an object event, and the event is usually recognized by the wind control system after receiving the event.
- the identified content may include, but is not limited to, device information, risk type information, and the like. It can be understood that the identified content is determined according to the parameters required for the subsequent risk control. In the embodiment of the present application, the content of the identification is especially the factor considered in the quantification, and the factors considered will be exemplified later. I will not repeat them here.
- an alternative set of verification modes is determined based on the results identified in step 101.
- the set of alternative verification modes may be a set of all possible verification modes or a part of all possible verification mode sets.
- a part of all possible sets of verification modes is selected, it is possible to exclude certain inappropriate verification methods based on the result of the identification.
- Reasons that lead to the exclusion of some inappropriate verification methods may include risk type factors and equipment factors.
- determining the set of the candidate verification mode is specifically: identifying a risk type corresponding to the object event, and determining, according to the risk type, a first verification mode set related to the risk type, identifying the initiation and/or Or a device type of the device that processes the object event, and determining, according to the device type, a second set of verification modes related to the device type, the first verification mode set and the second verification mode
- the set performs intersection processing, and the result of the intersection processing is used as the set of the alternative verification methods.
- an applicable management mode ie, a first set of verification modes
- an available control mode ie, a second set of verification modes
- the applicable control method is a set of management methods determined by considering the impact of the risk type of the event on the management and control mode.
- the so-called available control mode is a management manner determined after considering the device type of the device initiating and/or processing the object event in the event. For example, whether the hardware or software supports the set of verification methods determined by the corresponding verification mode.
- the device that initiates the object event refers to a device that proposes or starts the event
- the device that processes the object event refers to a device that has processed the event to complete one of the events after receiving the event.
- the reason for considering the device that initiates and/or processes the object event is because the object being verified may vary depending on the situation.
- the applicable management mode and the available management mode for the event are determined in step 102 in order to determine an optional set of verification modes for the event output, and the determination method provided in the step is not The only way, for example, one skilled in the art can omit the applicable management method, and only use the available management mode as an alternative set of verification methods.
- the two control modes set in step 102 that is, the applicable control mode and the available control mode, are used for intersection screening, and the management mode included in the two is selected as an alternative to the object event.
- Select the set of verification methods Select the management method that meets both the applicable management and control methods and the available management and control methods as an alternative verification method set.
- the event attribute weight of the element to be quantized is determined according to the identified event, and the element to be quantized is a factor that needs to be considered in the decision making, and different factors need to be considered in different application scene quantification processes.
- the factors include, but are not limited to, the user type corresponding to the object event, the scene type corresponding to the object event, the user's preference corresponding to the object event, and correspondingly, determining the user according to the user type.
- the type weight determines a scene type weight according to the scene type, and determines a preference weight according to the preference.
- what factors are considered as factors to be considered, that is, which factors are included in the control decision.
- the weight of the event attribute of each factor represents its importance in the overall risk management.
- the event attribute weights are usually determined after considering various factors as a whole, and the determined event attribute weights are the same for each type of management, and the event attribute weights are not changed because of different verification methods.
- the event attribute weights generally reflect the importance of each element to be considered, and are the comparison of the attributes between the elements to be considered. In other words, if the weight of the event attribute of a feature to be considered is higher, it means that it has more influence on the control decision.
- step 105 the set of alternative verification modes determined in step 103 is quantized and ordered.
- the governing attribute weight vector for each alternative check mode is first obtained.
- the control attribute weight vector is a vector composed of the weights of the control attributes of the elements to be quantized, and the N elements to be quantized correspond to the N control attribute weights, that is, the control attribute weight vector has N dimensions or elements.
- the vector is multiplied by a vector consisting of each event attribute weight of the element to be quantized. Thereby the output weight of each verification mode is obtained.
- the weight of the event attribute reflects the attribute of the event
- the weight of the management attribute reflects the comparison between various management methods, that is, the attribute of the management mode, and the higher the weight of a management attribute, indicating that The more the management method pays attention to the quantitative elements corresponding to the weight of the management attribute.
- the managed attribute weight vector is a vector estimated in advance according to historical big data.
- it may be obtained by using a genetic algorithm or other optimization algorithms, for example, after obtaining historical big data or some samples thereof, Count the actual occurrence values of some of the indicators, and then optimize certain target indicators (ie, presets) given certain indicator thresholds or constraints (such as determining the ratio of certain verification methods, etc.) Indicators, such as pass rate, etc., to obtain weights of management attributes.
- the optimization process for obtaining a weight vector for a managed attribute can be expressed as:
- the meaning of Index1 is the target indicator
- the meaning of Index2 is the constraint indicator. That is to say, the meaning of the above optimization process is that, under the premise that the given constraint index is less than 0.02%, the aforementioned control attribute weight is optimized by minimizing the target index, thereby obtaining the control attribute weight vector for the check mode. .
- w i1 , w i2 , w i3 are the control attribute weights of the event attribute weights of the first, second, and third, respectively, so that for each verification mode, the corresponding quantization vector can be calculated.
- the weight of its output, for the i-th verification mode, its output weight (or output score) is:
- K 1 , K 2 , K 3 ... in Equation 3 represent the event attribute weights of each of the factors to be quantified, respectively.
- the quantization parameter of the present application can input the main business constraint condition as a parameter, and adjust the quantization parameter according to different service requirements.
- step 106 based on the quantized ranking result in step 105, the final control decision is determined, that is, what control action or check mode is output.
- the method further comprises the step of testing the weight of the management attribute.
- the testing process first, the historical sample data, that is, the historical event for testing, including the identified event and the actual The check method for the output of the event in the control. Then, the historical sample is quantized by using the managed attribute weight vector to be tested, and the process of the quantization process is consistent with that described in steps 101-106, thereby obtaining a test verification mode, and the evaluation control output sample and the The actual control output samples are compared to test the weighted vector of the management attribute to be evaluated. Further, according to the test result, the control attribute weight vector is adjusted, that is, some or all of the weights in the control attribute weight vector are adjusted, that is, the importance degree of each event attribute weight is adjusted.
- the testing specifically includes: obtaining a test event for testing from each historical event, that is, acquiring a specific historical event as a target of the test.
- a first number of test events satisfying the specified condition is determined based on the recorded check mode determined for each test event, the first number being the number of control modes actually occurring.
- Determining, according to the management attribute weight, a test verification manner determined for each test event, and determining, according to the test verification manner, a second quantity of the test event that satisfies the specified condition, where the second quantity is based on the present The number of management methods determined by the quantitative method in the embodiment of the application. Comparing the first quantity and the second quantity, adjusting the management attribute weight according to the comparison result.
- control attribute weight vector of the present application can obtain the desired control effect among the event categories in which the test event is located, and The control effect is expressed by the second quantity described.
- the inventor proposed a sample of four test events and corresponding specified conditions as evaluation indicators through a large number of samples and evaluation process:
- test event is a security history event that passes the verification, and the specified condition is that the determined verification mode is directly let go.
- This indicator reflects the white sample for successful identity verification, based on whether the quantization vector can determine more direct control methods;
- the test event is a security history event that fails the verification.
- the specified condition is that the determined verification mode is to directly release or re-determine the verification mode different from the actual verification mode. This indicator reflects the white sample for the failure of identity verification.
- the actual verification mode refers to The manner of verification of the output in the historical event that occurred;
- the test event is a risk history event that is directly released, and the specified condition is that the determined verification mode is a non-directly let-off verification mode.
- This indicator reflects whether the black sample that is identified by the risk but directly discharged by the actual control output can be determined to be indirectly discharged;
- the test event is a risk history event that passes the verification, and the specified condition is that the determined verification mode is a verification mode different from the actual verification mode.
- This indicator reflects whether the black sample that has passed the actual output control can determine the control method that is different from the actual verification mode.
- the evaluation index 1 it is reflected whether, for the white sample, whether the quantization vector to be evaluated can reduce the number of successful verification methods. Since the white sample is a risk-free trading event, the ideal state is that all white samples are directly outputted, but in reality it is difficult to achieve, so as much as possible output directly let go, indicating that the quantized vector can belong to the white sample. Provide a better user experience in the transaction.
- evaluation indicator 2 Similar to evaluation indicator 1, for white samples, output more direct release is the pursuit of improving the user experience, and for the control of the identity verification failure in white samples, output again. Identity verification or output transaction failure will lead to poor user experience. Therefore, it can be understood that if the quantization vector to be evaluated can output a different control method than the actual verification method, the possibility of successful identity verification is improved. Can get a better user experience.
- evaluation indicator 3 it evaluates the security of the quantization vector. For black samples, the way the output is directly dropped is not ideal. Therefore, it can be understood that for the black sample that is identified by the risk but directly controlled by the actual control output, if the quantized vector to be evaluated can be outputted directly, such as short message check or face check, the Quantization vectors can improve the security of management.
- evaluation indicator 4 the same is evaluated for the security of the quantization vector.
- the black sample that passes the verification after the actual output control may occur in the case of a phone loss, virus, or hacker's access to certain control information. The occurrence of such an event indicates that the original output management method cannot avoid the risk.
- the quantization vector to be evaluated can output a different control method than the original management method, it will at least help to improve the possibility of defending such risks. Taking the loss of mobile phone as an example, if the original control decision output SMS verification, it is obvious that the loss of funds cannot be avoided. However, if the control method of generating the quantization vector is face recognition or transaction failure, the risk can be avoided, and of course, the security is also Improved.
- the object event may be a transaction payment event, in particular, a transaction event that uses a device to perform payment, and the transaction event may be, for example, a merchant initiates payment. And the process of completing the payment by the user.
- the user initiates an event, such as a transaction activity, and the weather control system usually recognizes the event after receiving the event.
- the identified content may include, but is not limited to, device information, risk type information, and the like. It can be understood that the identified content is determined according to the parameters required for the subsequent risk control. In the embodiment of the present application, the content of the identification is especially the factor considered in the quantification, and the factors considered will be exemplified later. I will not repeat them here.
- Determining the set of the alternative verification methods is specifically: identifying a risk type corresponding to the transaction payment event, and determining the risk according to the risk type (eg, transaction amount, online/offline, risk size, etc.) a first type of verification mode associated with the type, identifying a device type of a device (eg, a mobile phone) that initiates and/or processes the transaction payment event, and determining a second verification mode associated with the device type according to the device type And performing an intersection process on the first verification mode set and the second verification mode set, and using the result of the intersection process as the candidate verification mode set.
- the risk type eg, transaction amount, online/offline, risk size, etc.
- an applicable management manner ie, a first set of verification modes
- an available management mode ie, a second set of verification modes
- the set of alternative verification modes may be a set of all possible verification modes or a part of all possible verification mode sets.
- it is possible to exclude certain inappropriate verification methods according to the result of the identification for example, the mobile phone used by the user who completed the payment is not used for fingerprint verification.
- the hardware or software determines to the user that the fingerprint verification method is inappropriate).
- Reasons that lead to the exclusion of some inappropriate verification methods may include risk type factors and equipment factors.
- an applicable management manner and an available management manner for the event are determined.
- the so-called applicable management and control method is a set of management and control methods determined by considering the influence of the risk type of the event on the management and control mode. For example, if the event is identified as a transaction in which there is a risk of loss of the mobile phone, it can be understood that the set of applicable management methods should not include the short message verification mode.
- the so-called available control mode is to consider whether the hardware or software of the controlled object user in the event supports the corresponding verification mode. For example, if the mobile phone applicable to the event does not have an element that supports fingerprint recognition, it can be understood that the manner of fingerprint verification should be excluded from the available control set.
- the transaction security will be improved to a certain extent, because it can avoid, for example, the loss or theft of the mobile phone.
- the resulting loss of funds due to consideration of whether the hardware and software support verification of the identity mode, can avoid the output is not supported by the verification method, which can also improve the user experience to a certain extent.
- step 203 the two control modes set in step 202, that is, the applicable control mode and the available control mode, are used for intersection screening, and the management mode included in the two is selected as an alternative check for the target event candidate.
- Way set For example, in a certain scenario, all possible control methods include: 0, direct release, 1, SMS verification, 2. Dynamic questionnaire verification based on user memory (referred to as KBA), 3. Face verification 4, fingerprint verification, 5, the output transaction failed, 6, the output transaction failed and the account balance was frozen.
- the applicable management and control manners determined according to the influence of the risk type include: 0, direct release, 1, short message verification, 3. face verification, 5. output transaction failure; and in step 202, according to the event Factors such as equipment and software are determined.
- the available management methods include: 0, direct release, 1, SMS verification, 2. Dynamic questionnaire verification based on user memory (referred to as KBA), 5. Output transaction failure.
- the two sets of management modes are subjected to intersection processing, thereby determining an output check set, that is, 0, directly let go, 1, SMS check, and 5, the output transaction fails.
- the determined output check set is used as an alternative set of decision results, and the output check set reflects a combination of transaction security and user experience.
- the weight of the element to be quantized that is, the event attribute weight is determined according to the identified event, and the element is a factor that needs to be considered in the decision, and the event attribute weight of each factor represents Its importance in the overall risk management.
- the event attribute weights are usually determined after considering various factors as a whole, and the determined event attribute weights are the same for each type of management, and the event attribute weights are not changed because of different verification methods. And including, but not limited to, a user type corresponding to the object event, a scene type corresponding to the object event, and a user preference corresponding to the object event, and correspondingly, determining a user type weight according to the user type, and determining a scene type weight according to the scene type.
- the user type to which the verified user belongs in the event can be divided into: student according to experience or historical data. Young people, middle-aged people, the elderly, other people with limited ability, etc., and each user is given a weight (or user-applicable score) for each type of user.
- the scene type in the event it can also be divided into offline payment, online payment, etc., and the scene applicable weight (or scene applicable score) is equally given to each type of scene.
- user preferences For user preferences, it can also be divided into preference SMS verification, preferred fingerprint verification, preferred face verification, and the like, and similarly assigns user preference weights (or user preference scores) to each type of scene.
- user preference weights or user preference scores
- the above classifications for user types, scene types, and user preferences are not unique. In fact, these classifications can be determined by considering various aspects such as experience, historical data, and trade-offs for calculating costs, such as in a scene.
- offline payment can also consider various transaction types, such as taxi, shopping, catering, etc.
- Online payment can also be subdivided into online shopping, credit card repayment and so on.
- the weights are preset in advance, such as:
- step 205 the set of alternative verification modes determined in step 203 is quantized and ordered.
- the managed attribute weight vector for each alternative check mode is first obtained.
- the control attribute weight vector is a vector composed of the weights of the management attributes of the elements to be quantized, and the N elements to be quantized correspond to the weights of the N management attributes.
- the vector is multiplied by a vector consisting of each event attribute weight of the element to be quantized.
- the managed attribute weight vector is a vector estimated in advance according to historical big data.
- it may be obtained by using a genetic algorithm or other optimization algorithms, for example, after obtaining historical big data or some samples thereof, Calculate the actual occurrence value of some of the indicators (such as the amount of financial loss), and then optimize a certain target indicator given certain indicator thresholds or constraints (such as the rate of sending a certain verification method) (such as pass rate, or amount of money lost, etc.).
- the optimization process for obtaining a weight vector for a managed attribute can be expressed as:
- the meaning of Cost1 is the target indicator
- the meaning of Index2 is the constraint indicator.
- the meaning of Cost1 is the total amount of financial loss of the transaction set
- the meaning of Index 2 is the proportion of the output SMS verification method in all management methods. That is to say, the meaning of the above optimization process is that, under the premise that the proportion of the given output short message verification mode in all the control modes is less than 0.03%, the goal of minimizing the total amount of capital loss of the transaction set is to optimize the foregoing.
- the management attribute weights are obtained, thereby obtaining the weight of the management attribute weight for the short message verification mode.
- a weighted vector of control attributes for each type of management can be obtained.
- the quantization vector in a quantization process with three event attribute weights is:
- w i1 , w i2 , w i3 are the weights of the control attributes of the first, second, and third event attribute weights, respectively, so that for each type of control, the weight of the output can be calculated by its corresponding quantization vector.
- the output weight (or output score) is:
- K 1 , K 2 , and K 3 in Equation 6 represent the event attribute weights of each of the factors to be quantized, respectively, and the specific values are as shown in Table 1-3.
- the output check set determined in step 203 is 0, directly let go, 1, the short message check, 5, the output transaction fails to be quantified.
- Weights The governing attribute weight vectors W 0 , W 1 , and W 5 are obtained, respectively.
- the respective control attribute weight vectors are (w 01 , w 02 , w 03 ), (w 11 , w 12 , w 13 ), (w 51 , w 52 , w 53 ), respectively.
- the vector consisting of the weights of the management attributes of the elements to be quantized is (X 4 , Y 1 , Z 1 ). Therefore, the output weight or the output score of each verification mode is calculated according to Equation 6, and the short message verification method is taken as an example:
- the quantization parameter of the present application can input the main business constraint condition as a parameter, and adjust the quantization parameter according to different service requirements.
- step 206 according to the quantized ranking result in step 205, the final control decision is fed back to the wind control system, that is, what control action or check mode is output.
- the step of evaluating the weight of the management attribute is similar to the first embodiment of the present application, except that the historical event is a transaction payment event.
- the verification method is a verification method suitable for use in a transaction payment event, and the relevant specified condition is a condition expected in the transaction payment.
- the present application further provides a risk management device, where the risk management device includes: a receiving module 301 capable of receiving an object event to be controlled; and a processing module 302 capable of determining an output verification mode. And determining, according to the object event, at least one event attribute weight, acquiring a preset at least one management attribute weight, and determining, according to the event attribute weight and the preset at least one management attribute weight, at least the candidate verification mode set An output weight of the partial candidate check mode; and an output module 303 configured to determine a check mode output for the object event according to an output weight corresponding to the candidate check mode.
- the risk management device includes: a receiving module 301 capable of receiving an object event to be controlled; and a processing module 302 capable of determining an output verification mode. And determining, according to the object event, at least one event attribute weight, acquiring a preset at least one management attribute weight, and determining, according to the event attribute weight and the preset at least one management attribute weight, at least the candidate verification mode set An output weight of the partial candidate
- the processing module is further configured to: identify a risk type corresponding to the object event, and determine a first verification mode set related to the risk type according to the risk type; identify an initiation and/or processing Determining a device type of the device of the object event, and determining a second set of verification modes related to the device type according to the device type; intersecting the first verification mode set and the second verification mode set Processing, and using the result of the intersection processing as the set of alternative verification methods.
- the processing module is further configured to: determine a weight of the object event related to the user type, determine a weight of the object event related to the scene, and determine a weight related to the user event and the user preference.
- the processing module is further configured to: acquire at least one of the management attribute weights determined according to a management history related to the candidate verification manner.
- acquiring at least one of the management attribute weights determined according to the management history record related to the candidate verification manner includes: determining an event attribute weight of each historical event; and based on the preset indicator and the constraint condition, based on the The constraint condition and the event attribute weight are used to optimize the indicator to determine the weight of the management attribute.
- the processing module is further configured to: adopt a formula The output weight S i of the i-th verification mode is determined; where: w ij is the j-th management attribute weight, K j is the j-th event attribute weight, and n represents a total of n event attribute weights. .
- the processing module is further configured to:
- the present application further provides a risk management device for a transaction payment event.
- the historical event is a transaction payment event
- the verification method is It is applicable to the verification method in the transaction payment event, and the relevant specified conditions are the conditions expected in the transaction payment.
- the present application also discloses a transaction management method that utilizes a risk management method as described herein.
- the application also discloses a transaction management device comprising a risk management device as described herein.
- PLD Programmable Logic Device
- FPGA Field Programmable Gate Array
- HDL Hardware Description Language
- the controller can be implemented in any suitable manner, for example, the controller can take the form of, for example, a microprocessor or processor and a computer readable medium storing computer readable program code (eg, software or firmware) executable by the (micro)processor.
- computer readable program code eg, software or firmware
- examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, The Microchip PIC18F26K20 and the Silicone Labs C8051F320, the memory controller can also be implemented as part of the memory's control logic.
- the controller can be logically programmed by means of logic gates, switches, ASICs, programmable logic controllers, and embedding.
- Such a controller can therefore be considered a hardware component, and the means for implementing various functions included therein can also be considered as a structure within the hardware component.
- a device for implementing various functions can be considered as a software module that can be both a method of implementation and a structure within a hardware component.
- the system, device, module or unit illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product having a certain function.
- a typical implementation device is a computer.
- the computer can be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or A combination of any of these devices.
- 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.
- a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
- processors CPUs
- input/output interfaces network interfaces
- memory volatile and non-volatile memory
- 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.
- embodiments of the present application can be provided as a method, system, or computer program product.
- the present application can take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment in combination of software and hardware.
- the application 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.
- the application can be described in the general context of computer-executable instructions executed by a computer, such as a program module.
- program modules include routines, programs, objects, components, data structures, and the like that perform particular tasks or implement particular abstract data types.
- the present application can also be practiced in distributed computing environments where tasks are performed by remote processing devices that are connected through a communication network.
- program modules can be located in both local and remote computer storage media including storage devices.
Landscapes
- Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- Accounting & Taxation (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Finance (AREA)
- Theoretical Computer Science (AREA)
- Strategic Management (AREA)
- General Business, Economics & Management (AREA)
- Computer Security & Cryptography (AREA)
- Mathematical Physics (AREA)
- Development Economics (AREA)
- Technology Law (AREA)
- Marketing (AREA)
- Economics (AREA)
- Pure & Applied Mathematics (AREA)
- Computational Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Mathematical Analysis (AREA)
- Mathematical Optimization (AREA)
- Software Systems (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Algebra (AREA)
- Databases & Information Systems (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
- Train Traffic Observation, Control, And Security (AREA)
- Control By Computers (AREA)
- Alarm Systems (AREA)
Abstract
Description
用户类型 | 学生 | 青年人 | 中年人 | 老年人 | 其他限制行为能力人 |
用户类型权重 | X 1 | X 2 | X 3 | X 4 | X 5 |
场景类型 | 线下支付 | 线上支付 |
场景类型权重 | Y 1 | Y 2 |
用户偏好 | 短信校验 | 指纹校验 | 人脸校验 |
用户偏好权重 | Z 1 | Z 2 | Z 3 |
Claims (20)
- 一种风险管控方法,其特征在于,包括:接收待管控的对象事件;根据所述对象事件确定备选校验方式集;确定所述备选校验方式集中的至少部分校验方式的输出权重;根据所述校验方式对应的输出权重,从所述备选校验方式集中确定用于对所述对象事件进行风险管控的校验方式。
- 根据权利要求1所述的风险管控方法,其特征在于,确定所述备选校验方式集中的至少部分校验方式的输出权重,包括:根据所述对象事件确定至少一个事件属性权重;根据所述事件属性权重和预设的至少一个管控属性权重,确定所述备选校验方式集中的至少部分校验方式的输出权重。
- 根据权利要求1所述的风险管控方法,其特征在于,确定所述备选校验方式集,包括:识别所述对象事件对应的风险类型,并根据所述风险类型确定与所述风险类型相关的第一校验方式集;识别发起和/或处理所述对象事件的设备的设备类型,并根据所述设备类型确定与所述设备类型相关的第二校验方式集;对所述第一校验方式集和所述第二校验方式集进行交集处理,并将所述交集处理的结果作为所述备选校验方式集。
- 根据权利要求2所述的风险管控方法,其特征在于,根据所述对象事件确定至少一个事件属性权重,至少包括以下之一:识别所述对象事件对应的用户类型,根据所述用户类型确定用户类型权重;识别所述对象事件对应的场景类型,根据所述场景类型确定场景类型权重;识别所述对象事件对应的用户的偏好,根据所述偏好确定偏好权重。
- 根据权利要求2所述的风险管控方法,其特征在于,预设至少一个管 控属性权重,具体包括:根据记录的针对各历史事件分别确定出的校验方式,预设至少一个管控属性权重。
- 根据权利要求5所述的风险管控方法,其特征在于,根据记录的针对各历史事件分别确定出的校验方式,预设至少一个管控属性权重,具体包括:确定各历史事件的事件属性权重;根据预设的指标和约束条件,以基于所述约束条件和所述事件属性权重优化所述指标的方式确定所述管控属性权重。
- 根据权利要求6所述的风险管控方法,其特征在于,所述方法还包括:从各历史事件中获取用于测试的测试事件;根据记录的针对各测试事件确定出的校验方式,确定满足指定条件的测试事件的第一数量;基于所述管控属性权重,确定针对各测试事件确定出的测试校验方式;根据所述测试校验方式,确定满足所述指定条件的测试事件的第二数量;比较所述第一数量和所述第二数量,根据比较结果调整所述管控属性权重。
- 根据权利要求8所述的风险管控方法,其特征在于,所述测试事件为通过校验的安全历史事件,所述指定条件为确定出的校验方式为直接放过;和/或所述测试事件为未通过校验的安全历史事件,所述指定条件为确定出的校验方式为直接放过或再次确定出了与实际校验方式不同的校验方式;和/或所述测试事件为直接放过的风险历史事件,所述指定条件为确定出的校验 方式为非直接放过的校验方式;和/或所述测试事件为通过校验的风险历史事件,所述指定条件为确定出的校验方式为与实际校验方式不同的校验方式。
- 一种风险管控设备,其特征在于,包括:接收模块,配置为,接收待管控的对象事件;处理模块,配置为,确定备选校验方式集,确定所述备选校验方式集中的至少部分备选校验方式的输出权重;输出模块,配置为,输出根据所述备选校验方式对应的输出权重从所述备选校验方式集中确定用于对所述对象事件进行风险管控的校验方式。
- 根据权利要求10所述的风险管控设备,其特征在于,所述处理模块,进一步配置为:根据所述对象事件确定至少一个事件属性权重,获取预设的至少一个管控属性权重,根据所述事件属性权重和预设的至少一个管控属性权重确定所述备选校验方式集中的至少部分备选校验方式的输出权重。
- 根据权利要求10所述的风险管控设备,其特征在于,所述处理模块,进一步配置为:识别所述对象事件对应的风险类型,并根据所述风险类型确定与所述风险类型相关的第一校验方式集;识别发起和/或处理所述对象事件的设备的设备类型,并根据所述设备类型确定与所述设备类型相关的第二校验方式集;对所述第一校验方式集和所述第二校验方式集进行交集处理,并将所述交集处理的结果作为所述备选校验方式集。
- 根据权利要求11所述的风险管控设备,其特征在于,所述处理模块,进一步配置为:识别所述对象事件中对应的用户类型,根据所述用户类型确定用户类型权重;识别所述对象事件中对应的场景类型,根据所述场景类型确定场景类型权重;识别所述对象事件中的用户的偏好,根据所述用户偏好确定偏好权重。
- 根据权利要求11所述的风险管控设备,其特征在于,所述处理模块,进一步配置为:根据记录的针对各历史事件分别确定出的校验方式,预设至少一个管控属性权重。
- 根据权利要求14所述的风险管控设备,其特征在于,根据记录的针对各历史事件分别确定出的校验方式,预设至少一个管控属性权重,具体包括:确定各历史事件的事件属性权重;根据预设的指标和约束条件,以基于所述约束条件和所述事件属性权重优化所述指标的方式确定所述管控属性权重。
- 根据权利要求15所述的风险管控设备,其特征在于,所述处理模块,进一步配置为:从各历史事件中获取用于测试的测试事件;根据记录的针对各测试事件确定出的校验方式,确定满足指定条件的测试事件的第一数量;基于所述管控属性权重,确定针对各测试事件确定出的测试校验方式;根据所述测试校验方式,确定满足所述指定条件的测试事件的第二数量;比较所述第一数量和所述第二数量,根据比较结果调整所述管控属性权重。
- 根据权利要求17所述的风险管控设备,其特征在于,所述处理模块, 进一步配置为:所述测试事件为通过校验的安全历史事件,所述指定条件为确定出的校验方式为直接放过;和/或所述测试事件为未通过校验的安全历史事件,所述指定条件为确定出的校验方式为直接放过或再次确定出了与实际校验方式不同的校验方式;和/或所述测试事件为直接放过的风险历史事件,所述指定条件为确定出的校验方式为非直接放过的校验方式;和/或所述测试事件为通过校验的风险历史事件,所述指定条件为确定出的校验方式为与实际校验方式不同的校验方式。
- 一种交易管控方法,其特征在于,利用如权利要求1-9中任意一项所述的风险管控方法。
- 一种交易管控设备,其特征在于,包括如权利要求10-18中任意一项所述的风险管控设备。
Priority Applications (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
KR1020197025649A KR20190113893A (ko) | 2017-02-20 | 2018-02-12 | 위험 관리 및 제어 방법 및 디바이스 |
EP18754126.3A EP3567542A4 (en) | 2017-02-20 | 2018-02-12 | METHOD AND DEVICE FOR MANAGING AND CONTROLLING RISKS |
JP2019544885A JP6912591B2 (ja) | 2017-02-20 | 2018-02-12 | リスク管理制御方法及びデバイス |
SG11201907518UA SG11201907518UA (en) | 2017-02-20 | 2018-02-12 | Risk management and control method and device |
US16/535,746 US11488171B2 (en) | 2017-02-20 | 2019-08-08 | Risk management and control method and device |
PH12019501913A PH12019501913A1 (en) | 2017-02-20 | 2019-08-16 | Risk management and control method and device |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201710089854.5 | 2017-02-20 | ||
CN201710089854.5A CN108460681B (zh) | 2017-02-20 | 2017-02-20 | 一种风险管控方法及装置 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/535,746 Continuation US11488171B2 (en) | 2017-02-20 | 2019-08-08 | Risk management and control method and device |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2018149386A1 true WO2018149386A1 (zh) | 2018-08-23 |
Family
ID=63170091
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2018/076514 WO2018149386A1 (zh) | 2017-02-20 | 2018-02-12 | 一种风险管控方法及装置 |
Country Status (9)
Country | Link |
---|---|
US (1) | US11488171B2 (zh) |
EP (1) | EP3567542A4 (zh) |
JP (1) | JP6912591B2 (zh) |
KR (1) | KR20190113893A (zh) |
CN (1) | CN108460681B (zh) |
PH (1) | PH12019501913A1 (zh) |
SG (1) | SG11201907518UA (zh) |
TW (1) | TWI769190B (zh) |
WO (1) | WO2018149386A1 (zh) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN113506164A (zh) * | 2021-07-05 | 2021-10-15 | 普洛斯科技(重庆)有限公司 | 一种风控决策方法、装置、电子设备及机器可读存储介质 |
Families Citing this family (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10986138B2 (en) * | 2018-11-19 | 2021-04-20 | SOURCE Ltd. | System and method for adaptively determining an optimal authentication scheme |
CN109598425B (zh) * | 2018-11-22 | 2023-07-25 | 阿里巴巴集团控股有限公司 | 一种对风险对象进行管控的方法、装置及设备 |
CN110020775A (zh) * | 2019-01-30 | 2019-07-16 | 阿里巴巴集团控股有限公司 | 一种风险交易管控方法及装置 |
CN110033092B (zh) * | 2019-01-31 | 2020-06-02 | 阿里巴巴集团控股有限公司 | 数据标签生成、模型训练、事件识别方法和装置 |
CN110147967B (zh) * | 2019-05-28 | 2023-05-30 | 创新先进技术有限公司 | 风险防控方法及装置 |
CN110322139B (zh) * | 2019-06-28 | 2023-11-28 | 创新先进技术有限公司 | 策略推荐方法及装置 |
CN112396425B (zh) * | 2019-08-19 | 2024-09-13 | 马上消费金融股份有限公司 | 一种识别码处理方法及装置 |
CN110647345B (zh) * | 2019-08-30 | 2022-10-14 | 中国人民财产保险股份有限公司 | 一种针对应用开发的指标测算方法和系统 |
CN112579407A (zh) * | 2019-09-29 | 2021-03-30 | 北京国双科技有限公司 | 风险用户检测方法、装置、电子设备和计算机可读介质 |
CN111160740A (zh) * | 2019-12-19 | 2020-05-15 | 上海赛可出行科技服务有限公司 | 一种网约车风险控制系统及控制方法 |
CN111709746A (zh) * | 2020-06-09 | 2020-09-25 | 支付宝(杭州)信息技术有限公司 | 一种风险处理方法、装置和电子设备 |
CN112036890B (zh) * | 2020-09-01 | 2024-04-16 | 中国银行股份有限公司 | 客户身份认证方法及装置 |
CN113989043B (zh) * | 2021-10-28 | 2024-07-12 | 支付宝(杭州)信息技术有限公司 | 一种事件的风险识别方法、装置及设备 |
CN117252487B (zh) * | 2023-11-15 | 2024-02-02 | 国网浙江省电力有限公司金华供电公司 | 一种基于终端验证的多粒度加权分析方法及装置 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101504745A (zh) * | 2008-12-04 | 2009-08-12 | 阿里巴巴集团控股有限公司 | 基于网络线上业务的风险规则/模型建立和优化系统及方法 |
WO2013191857A1 (en) * | 2012-06-21 | 2013-12-27 | Motorola Mobility Llc | Privacy manager for restricting correlation of meta-content having protected information based on privacy rules |
CN104202738A (zh) * | 2014-08-30 | 2014-12-10 | 华为技术有限公司 | 策略控制方法、系统及网关 |
CN105323248A (zh) * | 2015-10-23 | 2016-02-10 | 绵阳师范学院 | 一种基于规则的交互式中文垃圾邮件过滤方法 |
Family Cites Families (37)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US3028901A (en) | 1959-11-18 | 1962-04-10 | George J Batori | Traction device for vehicles |
US7089592B2 (en) * | 2001-03-15 | 2006-08-08 | Brighterion, Inc. | Systems and methods for dynamic detection and prevention of electronic fraud |
US20020160711A1 (en) * | 2001-04-30 | 2002-10-31 | Carlson Bradley S. | Imager integrated CMOS circuit chip and associated optical code reading systems |
JP4082028B2 (ja) | 2001-12-28 | 2008-04-30 | ソニー株式会社 | 情報処理装置および情報処理方法、並びに、プログラム |
US20040267660A1 (en) | 2003-02-21 | 2004-12-30 | Automated Financial Systems, Inc. | Risk management system |
CN101073219A (zh) | 2003-09-12 | 2007-11-14 | Rsa安全公司 | 用于基于风险的验证的系统和方法 |
US20070288397A1 (en) * | 2006-06-12 | 2007-12-13 | Nec Europe Ltd. | Methodology for robust portfolio evaluation and optimization taking account of estimation errors |
JP2008204313A (ja) * | 2007-02-22 | 2008-09-04 | Clover Network Com:Kk | リスク分析処理装置およびその方法ならびにプログラム |
WO2008144555A1 (en) | 2007-05-17 | 2008-11-27 | Shift4 Corporation | Secure payment card transactions |
US8028896B2 (en) | 2007-12-14 | 2011-10-04 | Bank Of America Corporation | Authentication methods for use in financial transactions and information banking |
US8352346B2 (en) * | 2008-07-02 | 2013-01-08 | Carpenter Steven A | Systems and methods for providing investment performance data to investors |
US8295898B2 (en) | 2008-07-22 | 2012-10-23 | Bank Of America Corporation | Location based authentication of mobile device transactions |
CN101685526A (zh) * | 2008-09-28 | 2010-03-31 | 阿里巴巴集团控股有限公司 | 一种贷款准入评估方法和系统 |
US8984628B2 (en) * | 2008-10-21 | 2015-03-17 | Lookout, Inc. | System and method for adverse mobile application identification |
US8020763B1 (en) * | 2009-06-30 | 2011-09-20 | Intuit Inc. | Method and system for assessing merchant risk during payment transaction |
US8504456B2 (en) | 2009-12-01 | 2013-08-06 | Bank Of America Corporation | Behavioral baseline scoring and risk scoring |
WO2011106451A1 (en) * | 2010-02-23 | 2011-09-01 | Life Technologies Corporation | Methods of treating metal oxide surfaces and surfaces produced thereby |
US8453226B2 (en) | 2010-07-16 | 2013-05-28 | Visa International Service Association | Token validation for advanced authorization |
GB2497900A (en) | 2010-09-28 | 2013-06-26 | Barclays Bank Plc | Mobile payment system |
US8527418B2 (en) | 2011-11-22 | 2013-09-03 | The Western Union Company | Risk analysis of money transfer transactions |
US8639619B1 (en) | 2012-07-13 | 2014-01-28 | Scvngr, Inc. | Secure payment method and system |
WO2014066559A1 (en) | 2012-10-23 | 2014-05-01 | Visa International Service Association | Transaction initiation determination system utilizing transaction data elements |
US8613055B1 (en) * | 2013-02-22 | 2013-12-17 | Ping Identity Corporation | Methods and apparatus for selecting an authentication mode at time of issuance of an access token |
US10270748B2 (en) * | 2013-03-22 | 2019-04-23 | Nok Nok Labs, Inc. | Advanced authentication techniques and applications |
US9972005B2 (en) | 2013-12-19 | 2018-05-15 | Visa International Service Association | Cloud-based transactions methods and systems |
US20150262184A1 (en) * | 2014-03-12 | 2015-09-17 | Microsoft Corporation | Two stage risk model building and evaluation |
US9787723B2 (en) * | 2014-07-18 | 2017-10-10 | Ping Identify Corporation | Devices and methods for threat-based authentication for access to computing resources |
US9589118B2 (en) * | 2014-08-20 | 2017-03-07 | Google Technology Holdings LLC | Context-based authentication mode selection |
GB201417565D0 (en) | 2014-10-03 | 2014-11-19 | Moqom Ltd | Identity and risk management system and method |
US9984371B2 (en) | 2015-03-27 | 2018-05-29 | Ca, Inc. | Payment de-tokenization with risk evaluation for secure transactions |
US10970431B2 (en) * | 2015-04-09 | 2021-04-06 | Equifax Inc. | Automated model development process |
CN104881783A (zh) * | 2015-05-14 | 2015-09-02 | 中国科学院信息工程研究所 | 电子银行账户欺诈行为及风险检测方法与系统 |
US10628826B2 (en) * | 2015-11-24 | 2020-04-21 | Vesta Corporation | Training and selection of multiple fraud detection models |
CN105931051A (zh) | 2015-12-31 | 2016-09-07 | 中国银联股份有限公司 | 一种安全支付方法及装置 |
US10210518B2 (en) | 2016-04-13 | 2019-02-19 | Abdullah Abdulaziz I. Alnajem | Risk-link authentication for optimizing decisions of multi-factor authentications |
US11106994B1 (en) * | 2016-09-30 | 2021-08-31 | Amazon Technologies, Inc. | Tuning of machine learning models using accuracy metrics selected to increase performance |
WO2018090499A1 (zh) | 2016-11-21 | 2018-05-24 | 华为技术有限公司 | 交易方法、支付设备、校验设备和服务器 |
-
2017
- 2017-02-20 CN CN201710089854.5A patent/CN108460681B/zh active Active
- 2017-11-16 TW TW106139683A patent/TWI769190B/zh active
-
2018
- 2018-02-12 JP JP2019544885A patent/JP6912591B2/ja active Active
- 2018-02-12 KR KR1020197025649A patent/KR20190113893A/ko not_active IP Right Cessation
- 2018-02-12 EP EP18754126.3A patent/EP3567542A4/en not_active Ceased
- 2018-02-12 SG SG11201907518UA patent/SG11201907518UA/en unknown
- 2018-02-12 WO PCT/CN2018/076514 patent/WO2018149386A1/zh unknown
-
2019
- 2019-08-08 US US16/535,746 patent/US11488171B2/en active Active
- 2019-08-16 PH PH12019501913A patent/PH12019501913A1/en unknown
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101504745A (zh) * | 2008-12-04 | 2009-08-12 | 阿里巴巴集团控股有限公司 | 基于网络线上业务的风险规则/模型建立和优化系统及方法 |
WO2013191857A1 (en) * | 2012-06-21 | 2013-12-27 | Motorola Mobility Llc | Privacy manager for restricting correlation of meta-content having protected information based on privacy rules |
CN104202738A (zh) * | 2014-08-30 | 2014-12-10 | 华为技术有限公司 | 策略控制方法、系统及网关 |
CN105323248A (zh) * | 2015-10-23 | 2016-02-10 | 绵阳师范学院 | 一种基于规则的交互式中文垃圾邮件过滤方法 |
Non-Patent Citations (1)
Title |
---|
See also references of EP3567542A4 * |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN113506164A (zh) * | 2021-07-05 | 2021-10-15 | 普洛斯科技(重庆)有限公司 | 一种风控决策方法、装置、电子设备及机器可读存储介质 |
CN113506164B (zh) * | 2021-07-05 | 2023-05-26 | 普洛斯科技(重庆)有限公司 | 一种风控决策方法、装置、电子设备及机器可读存储介质 |
Also Published As
Publication number | Publication date |
---|---|
KR20190113893A (ko) | 2019-10-08 |
CN108460681B (zh) | 2020-07-03 |
EP3567542A1 (en) | 2019-11-13 |
CN108460681A (zh) | 2018-08-28 |
US11488171B2 (en) | 2022-11-01 |
EP3567542A4 (en) | 2019-11-27 |
JP2020510917A (ja) | 2020-04-09 |
US20190362355A1 (en) | 2019-11-28 |
TWI769190B (zh) | 2022-07-01 |
SG11201907518UA (en) | 2019-09-27 |
JP6912591B2 (ja) | 2021-08-04 |
TW201832149A (zh) | 2018-09-01 |
PH12019501913A1 (en) | 2020-03-16 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2018149386A1 (zh) | 一种风险管控方法及装置 | |
US11379855B1 (en) | Systems and methods for prioritizing fraud cases using artificial intelligence | |
US11093908B2 (en) | Routing transactions to a priority processing network based on routing rules | |
WO2019154115A1 (zh) | 一种资源转移监测方法及装置 | |
US20180046939A1 (en) | Automated Machine Learning Feature Processing | |
US20190279217A1 (en) | Method for adjusting risk parameter, and method and device for risk identification | |
CN112184239A (zh) | 一种安全支付方法、装置、设备和可读介质 | |
US10825109B2 (en) | Predicting entity outcomes using taxonomy classifications of transactions | |
US20200005195A1 (en) | Machine Learning and Security Classification of User Accounts | |
TW201833851A (zh) | 風控事件自動處理方法及裝置 | |
CN112214652B (zh) | 一种报文生成方法、装置及设备 | |
AU2021290143B2 (en) | Machine learning module training using input reconstruction techniques and unlabeled transactions | |
JP2023546849A (ja) | 通貨市場において証券を予想、推奨、および売買するための機械学習 | |
US20230274282A1 (en) | Transaction tracking and fraud detection using voice and/or video data | |
US20220156645A1 (en) | Machine Learning based on Post-Transaction Data | |
US20190325523A1 (en) | Systems and methods of generating a pooled investment vehicle using shared data | |
US20150032617A1 (en) | Secure Channel Payment Processing System and Method | |
US20240095742A1 (en) | Machine learning for fraud tolerance | |
US11093887B2 (en) | Managing disbursement signals at payment systems | |
US20230245230A1 (en) | System and method for generating and controlling celebrity investment stock currency | |
US20230195056A1 (en) | Automatic Control Group Generation | |
AU2014204560B2 (en) | Secure channel payment processing system and method | |
US20200265410A1 (en) | Automatically delaying payment for a transaction for an item until the item is delivered |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 18754126 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2019544885 Country of ref document: JP Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 2018754126 Country of ref document: EP Effective date: 20190809 Ref document number: 20197025649 Country of ref document: KR Kind code of ref document: A |