CA RiskMinder Administration Guide › Managing Global Configurations › Managing Global Rule Configurations › Adding New Rules › Examples of Using New Rules

Examples of Using New Rules

The following subsections illustrate how you can combine out-of-the-box RiskMinder rules and your rules to define custom combination rules by using multiple factors and conditions:

• High Amount Check
• High User Velocity from Unexpected Locations
• High Device Velocity from Unexpected Locations
• Wire Transfers from Unexpected Locations

Note: The rule (for example, SAFE_COUNTRIES) that you see in the following examples represent a simple list rule that uses a list of countries considered to be the origin of safe transfers.

High Amount Check

Consider the following details for an AMOUNT_CHECK rule that must check for transaction amounts more than $500:

• Rule Mnemonic: HIGHAMTCHK
• Rule Display Name: High Amount Check
• Description: This rule checks for high transaction amounts that exceed $500.
• Amount: 500

This example rule performs the following:

1. Parses the AdditionalInput string (say Amount=750) that is passed in the evaluateRisk() API call by the tag named Amount, and extract the value of this tag in a variable, say ActualAmount.

   Note: Refer to the Javadocs for details on parsing the AdditionalInput elements.

2. Extracts the parameter value (500) for the rule, and store it in a variable, say ParameterAmount.
3. Returns Matched because ActualAmount(750), in this case, is greater than ParameterAmount (500).

High User Velocity from Unexpected Locations

Consider that the SAFE_COUNTRIES refers to a simple list rule (where some of the elements are US,CA, UK, DE), then you can define a new rule to determine transactions with high User Velocity from unusual locations as:

USERVELOCITY AND NOT SAFE_COUNTRIES

High Device Velocity from Unexpected Locations

Similar to "High User Velocity from Unexpected Locations", you can define a new rule to determine transactions with high Device Velocity from unusual locations as:

DEVICEVELOCITY AND NOT SAFE_COUNTRIES

Wire Transfers from Unexpected Locations

Consider that you have created a rule called HIGHAMTCHK (as discussed in "High Amount Check".) Also, if the SAFE_COUNTRIES rule uses a list of countries considered to be origin of safe transfers, then you can define a rule to track low-value or high-amount wire transfers from unusual locations as:

(HIGHAMTCHK OR Amount < 20) AND NOT SAFE_COUNTRIES