API requirements for custom fields

Custom fields are sent to Kount 360 in the request payload. To add custom fields in the request payload, you must include the customFields property with the name and value of the custom field.

For Login, New Account Opening, and Identity Proofing, you must create the custom field in the user interface first. The value sent in the Login, New Account Opening, or Identity Proofing request payload should match the defined custom field. The custom field is evaluated only if the values match. In Payments Fraud, you can create custom fields in the user interface or through the Orders API request payload.

Refer to the following customFields code example:

 "customFields": {
    "name1": "value1",
    "name2": "value2",
    }

Caution

In Payments Fraud, custom fields are case sensitive. Custom fields created in the user interface must match with the API custom fields. We recommend creating custom fields in the user interface with all uppercase letters to match the case used when rules are migrated to policies.

Was this article helpful?
0 out of 0 found this helpful