How to Install and Configure the Kount Anti-Fraud Solution in VTEX

Provide fraud protection to your storefront by installing the Kount Anti-Fraud Solution in the VTEX marketplace. Kount is the leading AI-driven fraud protection solution for your business. Kount Command is available as an Anti-Fraud Solution within the VTEX Payment Gateway Affiliations of your VTEX shop. To successfully set up the Kount app, you must have your Agent Web Console (AWC) sign-in credentials and an existing VTEX account.

Adding and Configuring the Kount Anti-Fraud Solution

  1. Sign in to the VTEX commerce platform.

  2. Go to the VTEX store settings, select Payment and then Settings.

  3. Select Gateway Affiliations.

    vtex_gateway_1.png
  4. Select Add (+), and then select Kount.

    vtex_add_1.png
    vtex_add_2.png
  5. Configure the Gateway Affiliation settings:

    • Affiliation Name: This setting defaults to Kount - New configuration. You can change this setting to fit your organizational needs. The recommended best practice is to match the corresponding WebsiteID, for example, Kount - [WebsiteID].

    • Test or Live/Production: This setting lets you choose between sending traffic to the Kount test environment or the Kount production environment. Production access is only available for customers under agreement with Kount after testing and production certification has been completed.

    • Application Key: Enter your Kount-provided Merchant ID (MID). If you do not have your MID, contact your Kount Customer Success Manager.

    • Application Token: Enter your Kount API key. Refer to How to Create an API Key for Authentication to Kount if you have not already created one. The API key must correspond to the chosen test/production environment setting.

    • Enable Risk Pre-Analysis: This setting enables the Kount Risk Assessment to occur before Authorization (pre-auth), which lets customers perform a fraud risk analysis before attempting a payment authorization from your gateway.

    • Kount Website ID: Kount supports the ability to send traffic from multiple Websites to the same Kount environment for customers with more than one website property. Website IDs are used to identify and differentiate that traffic. The Website ID used in this field must correspond to a Website ID within the Agent Web Console (AWC) of the applicable Kount test/production environment. The Website ID is set to Default unless custom Website IDs are created by a customer.

  6. Select Save.

Linking the Kount Anti-Fraud Solution to Payment Conditions

Once the Kount Anti-Fraud Solution has been configured as a Payment Gateway Affiliation, it needs to be associated with each active and applicable payment condition within the VTEX store.

  1. Sign in to the VTEX commerce platform.

  2. Go to the VTEX store settings, select Payment and then Settings.

  3. Select the store card you want to add the Kount app to.

  4. Select the Use anti-fraud solution checkbox.

  5. Select the Kount Affiliation Name you created during configuration.

    vtex_useantifraud_1.png
  6. Select Save.

  7. Repeat this process for each applicable payment condition.

Configuring ENS for Manual Review

We provide our customers with the flexibility to be automated or manual. The Event Notification Service (ENS) provides functionality for customers to manually review and update the status of transactions in the Agent Web Console (AWC) after the initial Risk Inquiry Service (RIS) evaluation, and then automatically communicate those changes back to VTEX.

  1. Sign in to the AWC using your Kount credentials.

  2. Select Fraud Control and then Websites.

  3. Select the Website ID settings (the gear icon), and then select Edit.

  4. Select Yes to enable ENS.

  5. In the Merchant ENS URL field, enter the ENS URL. Use the shop identifier from your VTEX store URL. Example: <shop identifier>.myvtex.com

    The URL must follow this template: https://api.kount.com/tpa/ens/platform/VTEX/shop/<shop identifier>

Reviewing the Kount Anti-Fraud response on VTEX transactions

Once you have installed and configured the Kount Anti-Fraud Solution, you are able to review data from the Kount risk assessment for status changes on transactions within your VTEX store.

  1. Sign in to the VTEX commerce platform.

  2. Select Orders and then Transactions.

    vtex_orders_1.png
  3. You can view the status of the orders in Transactions. The three order statuses are:

    • Approved: These orders have passed risk analysis and the payment is processed.

    • Canceled: These orders have not passed risk analysis and the payment is not processed.

    • Analyzing Risk: These orders are pending review in the Kount Agent Web Console (AWC). You must sign in to the AWC to process these transactions.

Configuring the Kount Anti-Fraud Solution for the Device Data Collector with Google Tag Manager

The Device Data Collector (DDC) is implemented within VTEX using the Google Tag Manager. Once the Google Tag Manager is set up within your VTEX environment, perform the following steps to configure the DDC.

  1. Sign in to the VTEX commerce platform.

  2. Go to Settings > Storefront > Checkout.

  3. Go to the store you want to add the Device Data Collector (DDC) to and then go to the store settings. Once in the store settings, select Checkout.

    Note

    Use the default store if you want to apply the DDC to all of your stores.

    vtex_settings_checkout_2.png
  4. Enter your Google Tag Manager Collection ID (GTM-XXXX) in the Google Tag Manager field.

    vtex_gtag_id_1.png
  5. To set up the Google Tag for DDC, create a new custom HTML Google Tag, update line four of the code with ssl or tst, and then update the merchant ID with your merchant ID. Set triggering for this tag to All Pages. Go to Setting up Google Tag Manager on the VTEX developer site for more information.

    Refer to the following code example:

    <script>
    document.body.setAttribute("class", "kaxsdc " + document.body.getAttribute("class"));
      
    var url = "https://tst.kaptcha.com/collect/sdk?m=XXXXXX";
    var startTime = new Date().getTime();
    
    var loadSecondScript = function () {
            var kclient = new ka.ClientSDK();
            kclient.setupCallback(
                {
                    'collect-end':
                            function (params) {
                                    var endTime = new Date().getTime();
                                    /* console.log("Client side collector (approx) time: " + (endTime - startTime) + " mills"); */
                            },
                    'collect-begin':
                            function (params) {
                                    sessionStorage.setItem("kMercSessId", params['MercSessId']);
                            /* console.log("Begin\nMercSessId: " + sessionStorage.getItem("kMercSessId")); */
                                    if (window.vtex !== undefined && sessionStorage.getItem("kMercSessId") !== window.vtex.deviceFingerprint) {
                                            window.vtex.deviceFingerprint = sessionStorage.getItem("kMercSessId");
                              /* console.log("Setting deviceFingerprint - MercSessId: " + window.vtex.deviceFingerprint + " - " + sessionStorage.getItem("kMercSessId")); */
                                    }
                            }
            });
            kclient.autoLoadEvents();
    }
    
    if (sessionStorage.getItem("kMercSessId") === null) {
            loadScript(url, loadSecondScript);
    };
    
    if (window.vtex !== undefined && sessionStorage.getItem("kMercSessId") !== window.vtex.deviceFingerprint) {
      window.vtex.deviceFingerprint = sessionStorage.getItem("kMercSessId");
       console.log("Setting deviceFingerprint - MercSessId: " + window.vtex.deviceFingerprint + " - " + sessionStorage.getItem("kMercSessId"));
    }
      
    function loadScript(url, callback) {
            var head = document.getElementsByTagName('head')[0];
            var adapterScript = document.createElement('script');
            adapterScript.src = url;
            adapterScript.type = "text/javascript";
            adapterScript.onreadystatechange = callback;
            adapterScript.onload = callback;
            head.appendChild(adapterScript);
    }
    </script>

    Note

    Use ssl.kaptcha.com when the anti-fraud provider is configured for Live or Production, and use tst.kaptcha.com when the anti-fraud provider is configured for Test.

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