Page Comparison

Table of Contents

Note
IMPORTANT: The Kount Command plugin differs from our legacy Kount plugin in that it supports all payment gateways EXCEPT Authorize.net, while the earlier Kount plugin was limited to only Authorize.net and Braintree users. Both plugins CANNOT be installed simultaneously or checkout will fail.

Note
WARNING: Once installed, the Kount Command plugin must be set up with API credentials. If the plugin is installed and the credentials are not added, checkout will be blocked on order complete.

Setup Checklist

Insert excerpt

	Set-up Checklist
	Set-up Checklist
nopanel	true

1. KOUNT TASKS

Ensure that working agreement with Kount is finalized.
Status
colour Red
title Required
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.
Status
colour Red
title required

Status

colour	Yellow
title	Prerequisite

2. COMMERCE TASKS

Install the Kount Command Plugin.
Status
colour Red
title required
Obtain API Key from Kount Portal.
Status
colour Red
title required
Configure the Kount Command Test environment.
Status
colour Red
title required
Work with your Kount Representative to create Kount rules.
Status
colour Red
title required
Verify transactions are working as expected.
Status
colour Red
title required
Configure the Kount Command Production environment.
Status
colour Red
title required

Status

colour	Green
title	Detailed Setup

...

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.

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.

...

Install the Kount Command Plugin.
Obtain API Key from Kount Portal.
Configure the Kount Command Test environment.
Work with your Kount Representative to create Kount rules.
Verify transactions are working as expected.
Configure the Kount Command Production environment.

Note
WARNINGIMPORTANT: Once installed, the Kount Command plugin must be set up with API credentials. If the plugin is installed and the credentials are not added, checkout will be blocked on order complete.

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.
If it is not enabled, click Edit and check Is enabled? and click Save.

...

2. Obtain API Key from Kount Portal

Obtain and make note of your API Key.
1. Log in to Kount Portal through https://awc.test.kount.net using credentials provided by Kount.
2. Click ADMIN and select API Keys.
3. 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.
4. 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.
5. Make note of the API Key for use below.

3. 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 step.
4. Device Data Collector Endpoint: https://tst.kaptcha.com
5. Risk Inquiry Service Endpoint: https://risk.test.kount.net
6. Merchant ID: Obtain your unique merchant ID from Kount. This is always a 6-digit number.
7. Site ID: DEFAULT
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.)
10. Click Save.

Info

NOTE: For the Failed Kount Validation Message, Kount cautions against providing any information that would assist bad actors in fraudulent activities. One way to provide an excellent customer experience, but not unintentionally support fraudsters, would be to create a unique identifier that would signify to your resort staff that the transaction in question had been declined by Kount, rather than the payment gateway.

For example, you could customize your message to be “We had a problem processing your payment. Error Code: KT 65. Please call us at 800-123-4567 for assistance.”

Then, when call center staff hears the “Code KT 65”, they know that the decline was triggered by Kount, and that this is a potentially fraudulent transaction, rather than a card being declined by the gateway for any number of reasons.

...

Contact your Kount Representative to establish your resort’s Kount strategy and to obtain assistance in establishing Kount rules so that declines process are processed as expected.

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: DEFAULT
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.)
10. Click Save.