Custom inputs are available to users of all of the minFraud services for use with custom rules and for display on the minFraud transaction review screen. You can have up to 24 active custom inputs at any one time.
You should never send a full credit card number as an input. If you attempt to send a full credit card number as an input, the minFraud service will reject the input and issue a warning.
Once you have defined a new custom input in your account portal, you will need to update your minFraud integration so that the new input will be sent to the minFraud service. You can learn more about this required step on our developer portal.
If you plan to use custom inputs with custom rules, make sure you know how custom rules work and that you have set up your integration to work with custom rules. Learn more about using custom rules.
Create a custom input
Click on 'Custom Inputs' in the minFraud menu in your account portal [direct link, login required]. This feature is available to admin users and standard users with product/service permissions. Learn more about user permissions.
Begin by clicking the “Create an input” button.
Every Custom Input is defined by designating a type of data which will be passed (boolean, number, phone number, or string), and a label. There are four data types that you may choose from.
|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.|
|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.”
|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.|
|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.|
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.
Delete a custom input before using it
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.
Deactivate a custom input
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 use it. Learn how to deactivate a custom rule.
Once all custom rules that use the custom input have been deactivated, you can deactivate the custom input by clicking on the blue X icon in the “Make inactive” column of the custom input display.
This page was last updated on .