Page Comparison

...

Prerequisite Tasks

...

• Ensure that you have a working agreement with Kount and that you have access to your Kount Dashboard/Administration screen.

• Ensure that the Kount Command plugin is set up with API credentials. Failure to do so will result in checkout being blocked on order complete.

• Obtain API Key from Kount Portal

  Obtain and make note of your API Key

  .

  • Log in to Kount Portal through  https://awc.test.kount.net using credentials provided by Kount.

    1. Click ADMIN and select API Keys.

       Image Modified

    2. Option 1: You may copy an existing API key and paste it into the configuration panel below.

       1. IMPORTANT: If you copy and paste the key, best practices suggest you copy, paste the key into a text editor, and inspect it for any additional characters, leading spaces, etc.  Remove any extra characters. Once verified, copy from the text editor and paste it into the configuration pane.

          Image Modified

    3. Option 2: Generate a new API Key by clicking Create API Key.

       1. IMPORTANT: If you generate a new API key you do not need to revoke it. You can use multiple keys simultaneously. Please follow the instructions above for copying and pasting the newly generated API Key.

          Image Modified

    4. Make note of the API Key for use below in Detailed Setup Step #4.

Settings, Language Strings and/or HTML Widgets for this Feature

...

• These settings can be set by going to Settings > All settings, but using the UI described below in the Detailed Setup Guide is the recommended method.

Detailed Setup Guide

1. Install the Kount Command Plugin.

2. Obtain API Key from Kount Portal.

3. Configure the Kount Command Test environment.

4. Work with your Kount Representative to create Kount rules.

5. Verify transactions are working as expected.

6. Configure the Kount Command Production environment.

1. Install the KountCommand Plugin

• Go to Configuration > Local plugins.

• Scroll down to the KountCommand plugin.

  

• Click Install.

• Make sure the plugin is both installed and enabled.

...

Once the plugin has been installed and the site has been restarted, the plugin needs to be enabled.

• Go to Configuration > Local plugins.

• Scroll down to the KountCommand plugin.

• To enable, click Edit and check Is enabled? and click Save.

  

...

4. Configure the Kount Command TEST Environment

• Click Configure to get to the Configure - KountCommand Plugin screen.

  

  

• Enter data into the following fields:

  1. Multi-store configuration: Select the appropriate choice if you have a multi-store configuration.

  2. Use Sandbox?: Check for TEST environment.

  3. API key: Enter the API Key obtained in the

  previous

  1. prerequisite step above.

  2. Device Data Collector Endpoint: https://tst.kaptcha.com

  3. Risk Inquiry Service Endpoint: https://risk.test.kount.net

  4. Merchant ID: Obtain your unique merchant ID from Kount. This is always a 6-digit number.

  5. Site ID: Enter the Website ID defined in Kount. You can find this in the Kount Agent Web Console (Under Fraud Control > Websites). The default name for Site ID is DEFAULT, however can be updated if you use Kount for various sites or resorts.

  6. Connection Timeout: Set to

  60000

  1. 6000

  2. Failed Kount Validation Message: Enter the text that will be displayed to the user if Kount declines the transaction. (See NOTE below.)
     

     Image Modified

  3. Click Save.

5. Work with Kount Representative to Create Kount Rules

...

• Log into your Kount Portal.

• Create a user-defined field (UDF) called STARTDATE ( all caps, all one word). This will allow the earliest Start Date on any product in the transaction to be displayed, and can be used in setting rules for declines.

  • Click Add UDF and enter the following:

    • Label: STARTDATE

    • Description: STARTDATE

    • Type: Select Date

  • Click Save UDF.

    

• Ensure that all Kount rules have been defined per your resort’s Kount strategy. Rules need to be included in a ruleset, and the ruleset must be activated for the rules to apply to transactions.

...

Once you have established that Kount is functioning properly, you may create your PROD environment.

• Click Configure to get to the Configure - KountCommand Plugin screen.

  

  

• Enter data into the following fields:

  1. Multi-store configuration: Select the appropriate choice if you have a multi-store configuration.

  2. Use Sandbox?: Uncheck for PROD environment.

  3. API key: Obtain a new API Key as you did for TEST (Step 2 above) by logging into https://portal.kount.net. This CANNOT be the same API Key that was used for your TEST environment.

  4. Device Data Collector Endpoint: https://ssl.kaptcha.com (for PROD environment)

  5. Risk Inquiry Service Endpoint: https://risk.kount.net (for PROD environment)

  6. Merchant ID: Obtain your unique merchant ID from Kount. This is always a 6-digit number.

  7. Site ID: Enter the Website ID defined in Kount. You can find this in the Kount Agent Web Console (Under Fraud Control > Websites). The default name for Site ID is DEFAULT, however can be updated if you use Kount for various sites or resorts.

  8. Connection Timeout: Set to 60000

  9. Failed Kount Validation Message: Enter the text that will be displayed to the user if Kount declines the transaction. (See NOTE below.)

     Image Modified

  10. Click Save.

...