| Table of Contents |
|---|
...
1. KOUNT TASKS | |||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| ||||||||||||||||||||||||||||||||||||||||||
2. COMMERCE TASKS | |||||||||||||||||||||||||||||||||||||||||||
|
|
...
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.
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.
Log in to Kount Portal through https://awc.test.kount.net using credentials provided by Kount.
Click ADMIN and select API Keys.
Option 1: You may copy an existing API key and paste it into the configuration panel below.
IMPORTANT: If you copy and paste the key, best practices suggest you copy, paste the key into a test 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.
Option 2: Generate a new API Key by clicking Create API Key.
IMPORTANT: If you generate a new API key you do not need to “revoke” (click on the gear to the right of the key in the console” the validity of any existing keysrevoke it. You can have use multiple valid keys simultaneously. Follow Please follow the instructions above for copying and pasting the newly generated API Key.
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:
Multi-store configuration: Select the appropriate choice if you have a multi-store configuration.
Use Sandbox?: Checked Check for TEST environment.
API key: Enter the API Key obtained in the previous step.
Device Data Collector Endpoint: https://tst.kaptcha.com
Risk Inquiry Service Endpoint: https://risk.test.kount.net
Merchant ID: Obtain your unique merchant ID from Kount. This is always a 6-digit number.
Site ID: DEFAULT
Connection Timeout: Set to 60000
Failed Kount Validation Message: Enter the text that will be displayed to the user if Kount declines the transaction. (See NOTE below.)
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. |
...
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:
Multi-store configuration: Select the appropriate choice if you have a multi-store configuration.
Use Sandbox?: Unchecked Uncheck for PROD environment.
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.
Device Data Collector Endpoint: https://ssl.kaptcha.com (for PROD environment)
Risk Inquiry Service Endpoint: https://risk.kount.net (for PROD environment)
Merchant ID: Obtain your unique merchant ID from Kount. This is always a 6-digit number.
Site ID: DEFAULT
Connection Timeout: Set to 60000
Failed Kount Validation Message: Enter the text that will be displayed to the user if Kount declines the transaction. (See NOTE below.)
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. |
...