Kount

Utilizing external risk checks such as Kount can significantly enhance your transaction security. This guide provides detailed information on the specific parameters and scripts required to enable Kount risk checks in your transactions.

Transaction extra data

For Kount external risk checks, you need to include specific items and parameters in the extraData of your transaction. The parameters Site and at least one item are mandatory. If you are not using payment.js, the parameter SessionId becomes necessary as well. Additionally, the customer provided in the transaction request must have a valid IPv4 address (customer.ipAddress).

Here's a breakdown of the required and optional parameters:

Name	Type	Description
KOUNT_SITE	requiredstring	Your Kount Site configured in Kount
KOUNT_SESSION_ID	requiredstring	Unique kountSessionId
KOUNT_UDF[YOUR_USER_DEFINED_FIELD_1]	optionalstring?	Anything
KOUNT_UDF[YOUR_USER_DEFINED_FIELD_2]	optionalstring?	Anything
KOUNT_TOTAL_AMOUNT	optionalstring?	If amount to evaluate differs from transaction amount
KOUNT_CURRENCY	optionalstring?	If currency to evaluate differs from transaction currency

For each item, you need to provide specific details beginning with an index of 0. Alternatively, you can use the items[].extraData field on the transaction request to add the necessary data:

Name	Type	Description
KOUNT_PROD_TYPE[0]	requiredstring	Item type
KOUNT_PROD_ITEM[0]	requiredstring	Item name
KOUNT_PROD_DESC[0]	requiredstring	Item description
KOUNT_PROD_QUANT[0]	requirednumber	Item quantity
KOUNT_PROD_PRICE[0]	requiredstring	Item price

If using the transaction item extra data:

Name	Type	Description
KOUNT_PROD_TYPE	requiredstring	Item type
KOUNT_PROD_ITEM	requiredstring	Item name
KOUNT_PROD_DESC	requiredstring	Item description
KOUNT_PROD_QUANT	requirednumber	Item quantity
KOUNT_PROD_PRICE	requiredstring	Item price

Initializing the risk script

Similar to other external risk checks, you need to initialize risk scripts to enable Kount risk checks. Depending on your settings, you might have to manually initialize these scripts.

Using payment.js

In cases where the connector or risk profile associated with your Public Integration Key isn't set to automatically initialize Kount, you need to manually initiate it with payment.js. If Init Scripts Automatically is enabled, no further javascript steps are required for embedding Kount.

<script>
  const payment = new PaymentJs("1.2");

  payment.init("public-integration-key", "number_div", "cvv_div", (payment) => {
    // ...
    try {
      payment.initRiskScript({ type: "kount" });
    } catch (exception) {
      //this might happen on an invalid configuration at risk profile or connector level
    }
  });
</script>

Without payment.js

If you are not utilizing PaymentJS, you can still manually initialize the Kount risk script with the following steps.

<script src="https://gateway.ixopay.com/js/risk-scripts/kount-dc.min.js"></script>
<script>
  const kountMerchantId = "kount-merchant-id";
  const kountTestMode = false; // using Kount sandbox or not
  const kountHandler = new KountDcHandler(kountMerchantId, kountTestMode);

  kountHandler.initKountDc((kountSessionId) => {
    document.getElementById("hidden-kount-session-id").value = kountSessionId;
  });
</script>

Remember to accurately include all necessary information for successful risk checks with Kount. If you encounter issues, review your connector configuration or the extra data you're providing.