Custom Inputs Guide
Introducing Custom Inputs
Custom inputs enable you to extend the minFraud service by defining data points for use with Custom Rules and for display on the Transaction Details page.
You know your business and its fraud patterns. Leverage this expertise to create one or more custom inputs to add as part of your minFraud query. Then, use your custom inputs in custom rules and include them on the Transaction details page for fraud analyst review.
Before we get started, note that the Custom Inputs feature is only available for use with the minFraud Score, minFraud Insights, and minFraud Factors services.
In addition, once you have defined a custom input following the instructions below, you will need to update your minFraud integration so that the new input will be sent to the minFraud service. See here for more information on this required step.
To get started, consider the data points you find helpful in identifying fraud patterns. For example, perhaps you are seeing higher rates of fraud for orders placed online but picked up at a retail location. You can create a custom input to identify such orders, and then create a custom rule to ensure each is manually reviewed.
Once you’ve determined additional data points of interest, create a custom input in association with each, using the Custom Inputs interface, accessed from the MaxMind Account Portal. You can then incorporate them in custom rules as well as include them on the Transaction Details page for use during manual review.
Note that, once you have defined custom inputs using the interface, you will need to update your minFraud integration so that the new input will be sent to the minFraud service.
You can have up to 24 active inputs at any one time.
Accessing Custom Inputs
Before you begin, please check the version of the client API you have installed to ensure that it includes disposition as part of the minFraud service response. Then, to create a custom input, log in to your account and select Custom Inputs from the left-hand menu.
Creating a Custom Input
To create a custom input, follow these steps:
- Select a custom input type.
Determine which type of custom input you wish to create:
Use boolean if you want to associate the custom input with custom rules using the operator is true / is false
Example: If customer type of BUSINESS is true, then…
Use a custom input type of number if the associated custom rule will use the operators =, ≠, >, ≥, or <.
Example: If account age in days is > 120, then….
A custom input of type string uses matches, contains, or starts with as an operator with custom rules.
Example: If reseller SKU matches WX-190, then….
A custom input of type phone number uses matches, contains, or starts with as an operator with custom rules.
Example: If affiliate phone number matches….
Then, click on “New custom input” on the Custom Input Parameters screen to select the type and provide a label for the custom input.
The label you provide here will display on the transaction details page as well as be included on the panel of custom inputs in the Custom Rules wizard.
If you select a custom input type of Number, you can optionally add a units label. The Transaction Details screen will display this label as well, for example, Account Age in Days.
Once you’ve selected a custom input type and provided a label, click on Next step to generate a parameter key.
The parameter key name will be based on the label you specified. You are provided with the option to edit it. For example, you may wish to change the name of the parameter key to meet a naming convention used by your IT department.
Once you have reviewed the parameter key, click on Save input to create the new input. The new input is added to the list of inputs with a First received status of No activity.
You can delete custom inputs with a First received status of No activity. Once you have added the custom input to your integration and a query has been received which includes that custom input as part of the request, you can make the input inactive but no longer delete it.
Once you have created a custom input using the Custom Input Parameters screen, update your minFraud integration so that the new input will be sent to the minFraud service.
If you wish to place a custom input in an inactive state, you must first deactivate any custom rules using that custom input.