Custom Inputs in minFraud

Custom Inputs are available to minFraud Score, Insights, and Factors customers. They enable you to extend the minFraud service by defining data points for use with Custom Rules and for display on the Transaction Details page.

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 our Developers Site for more information on this required step. You can have up to 24 active custom inputs at any one time.

If you plan to use Custom Inputs with Custom Rules, please check the version of the client API you have installed to ensure that it includes disposition as part of the minFraud service response.

Accessing Custom Inputs
Creating a Custom Input
Selecting a Data Type
Labeling Your Input and Generating a Key
Using Custom Inputs


Accessing Custom Inputs

To access Custom Inputs, log in to your account and select Custom Inputs from the left-hand menu.


Creating a Custom Input

Every Custom Input is defined by designating a type of data which will be passed (boolean, number, phone number, or string), and a label.

Begin by clicking the “Create an input” button.


Selecting a Data Type

Select a data type for your Custom Input from the drop-down menu.

There are four data types that you may choose from.

  1. Boolean: Boolean data is either true or false. For example, you could create a boolean Custom Input called “Is Trusted Customer.” You could then pass “true” to this input in your minFraud queries when the customer of the transaction is drawn from a list of trusted customers, and false for all other customers.
  2. Number: Number data can contain any float or integer number. For example, you could create a number Custom Input called “Discount Amount.” You could then pass the value in dollars of all discounts applied to the transaction to this input as part of your minFraud queries.
    Note: When you create a Custom Input with the number data type, you can optionally define the units for the input. In the example given above, you could define the units as “Dollars.”  
  3. Phone Number: Phone number data can contain a phone number. For example, you could create a phone number Custom Input called “Main Account Phone.” You could then pass the primary phone number associated with the customer to this input as part of your minFraud queries.
  4. String: String data contains a string of characters. For example, you could create a string Custom Input called “Customer Status.” You could then pass one of a number of status names (“new,” “verified,” “trusted”) associated with the customer to this input as part of your minFraud Queries.

Labeling Your Input and Generating a Key

Enter a label for your Custom Input and click the “Next step” button.

The system will generate a parameter key based on the label you specified.

You may edit the parameter key. For example, you may wish to change the name of the parameter key to meet a naming convention used by your developers.

When you have finished, click the “Save input” button.


Using Custom Inputs

After saving, the new input is added to the list of inputs with a First received status of No activity. As long as you have not submitted any inquiries utilizing the newly defined input, the First received status will remain set to No activity and you will be able to delete the input.

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 will no longer be able to delete it.

Custom Inputs that have been used as part of submitted queries can be deactivated. If the Custom Input is used in any Custom Rules, you must first deactivate the Custom Rules that utilize the input. Then, you may deactivate the input by clicking on the blue X icon in the “Make inactive” column of the Custom Input display.