Configuring Kount

To help you protect your business against fraudulent transactions, Lime Light CRM has integrated with Kount.

 

What is Kount?

Kount delivers an all-in-one fraud and risk management solution for companies that have card-not-present environments looking to simplify their fraud/risk operations while dramatically improving bottom line results. Kount provides a single, turnkey fraud solution that is easy-to-implement and easy-to-use. Kount’s proprietary technology has reviewed hundreds of millions of transactions and provides maximum protection for some of the world’s best-known brands.

For more information about this risk mitigation service provider, or to sign up for an account today, please contact our client success team at clientsuccess@limelightcrm.com.

 

How to configure Kount within Lime Light CRM

Once you have your account set up with them, you can go into your Lime Light CRM and configure your risk mitigation provider. You will go to Payment Systems>Risk Mitigation Providers and select Kount from the Risk Mitigation Providers drop down menu. Click on “Add Risk Mitigation Provider” and fill out the parameters for Kount.

These parameters are briefly described here for your reference:

API Key: This is needed to send chargeback information to Kount and will need to be created in Kount’s web console. Please talk to your Kount Client Success Manager for assistance in creating one.

Billing Type: Select the billing type for your profile. The fraud checks can be performed on initial transactions only or both initial and rebill transactions. 

Chargeback Alert: Select if you would like to send an update to Kount for when a chargeback occurs within the CRM. 

Custom Fields 1 -4: Select the custom fields that you have configured within Kount's web console. The following custom field tokens are available for configuration within Kount's web console: affiliate, sub_affiliate, campaign_id, and gateway_id. In order to configure the custom fields in Kount's web console, you will need login to the AWC and go to the Fraud Control Tab --> "User Defined Fields; make sure the label and type matches the configuration in the CRM.

Is Test: Select if you would like to use Kount in test mode.

Merchant Id: This will be provided to you by Kount.

Site Id: This is an optional field for you to provide an 8 character or less description of your website if you currently have more than one website. Please contact your Kount representative before modifying the Site Id field.

Void/Refund Alert: Select if you would like to send an update to Kount for when a void / refund occurs within the CRM. 

Alias: This is the name that you will assign to your risk mitigation provider. It is for internal purposes only; it helps you identify a specific provider account among several accounts in your CRM.

 

 Updated_Kount.png

 

Additional Kount Configuration Notes

  • Orders that have passed the Kount fraud check will be sent to your payment gateway.
  • Orders that have failed the Kount fraud check will not be sent your payment gateway.
  • The orders which have been flagged for review after the Kount fraud check will be sent your payment gateway, and a note will be added to the order history within the CRM to indicate that the order is under review. If the order fails the fraud check after review, you can then manually mark the order as fraud from within the interface of the CRM.
  • The IP address is suppressed on orders placed by Customer Service representatives on the Place Order page within the CRM so that Kount's fraud checks can be performed without IP concerns.
  • Your account with Kount will need to be configured with the following (1x1) pixel location: https://{yourlimelightdomain}.limelightcrm.com/pixel.gif

 

How to apply Kount to your campaigns in Lime Light

After you have configured your Kount profile within your CRM, you will need assign it at the campaign-level by checking the 'Third Party Providers' box in the floating side-panel of the campaign edit page. This will will bring up the providers module where you will simply select your Kount profile by its “alias” in the drop down menu under the Risk Mitigation Providers field, like so:

 Kount_Campaign.png

 

Using Kount with a Webform-based campaign in Lime Light

Kount's technology uses a pixel to gather device data on the checkout page. If you are using a Webform-based campaign in Lime Light, this pixel is already built into the webform pieces that you would download from within the CRM, which will not require any further development on your part.

 

Using Kount with a API-based campaign in Lime Light

If you are using an API-based campaign, you will need to include the following snippet of code on your checkout page to allow for a unique session to be generated and fired through the pixel to Kount, on page load. The following snippet will handle all of this for you, but you will be responsible for populating the appropriate domain name (see {yourlimelightdomain} below) and campaign_id (see {x} below) within this pixel:

 

<?php

/*After this pixel has fired, the customer will complete the checkout process where you will be responsible for passing this same session ID to Lime Light through the 'sessionId' parameter of our NewOrder methods (including NewOrder, NewOrderCardOnFile and NewOrderWithProspect).*/

$kount_session = str_replace('.', '', microtime(true));
?>
<html>
<body>
<!--YOUR_API_FORM_GOES_HERE-->

<!--KOUNT PIXEL-->
<input type="hidden" name="sessionId" value="<?=$kount_session?>" />
<iframe width=1 height=1 frameborder=0 scrolling=no src="https://{yourlimelightdomain}.limelightcrm.com/pixel.php?t=htm&campaign_id={x}&sessionId=<?=$kount_session?>">
<img width=1 height=1 src="https://{yourlimelightdomain}.limelightcrm.com/pixel.php?t=gif&campaign_id={x}&sessionId=<?=$kount_session?>>"/>
</iframe>
<!--/KOUNT PIXEL-->
</body>
</html>

 

After this pixel has fired, eventually the customer will complete the checkout process, where you will be responsible for passing this same session ID to Lime Light through the 'sessionId' parameter of our NewOrder methods (including NewOrder, NewOrderCardOnFile and NewOrderWithProspect).

NOTE: The campaign_id in the pixel can be hard-coded to a single campaign, if unknown at the time the pixel fires, so long as this campaign has a Kount profile configured within it. Further, the session ID must be within 32 characters in length, which will not be a concern for you if using the snippet found above.

*Additional Kount Notes*- Please note that when creating an order in Lime Light the phone number is a required field.  If you are NOT using a real phone number and need to use a fake phone number for the order, please use 0123456789.  The use of the same phone number on each order will cause orders to be linked together in Kount.

Have more questions? Submit a request

0 Comments

Article is closed for comments.