IMPORTANT: The KountCommand 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.
Setup Checklist
This section is a comprehensive and high level summary of all tasks and prerequisites required for this feature to function properly. This section is purposed for use after an administrator is familiar with configuring this feature as an “audit” checklist. For detailed set-up instructions, jump down to “Prerequisite Tasks” and “Detailed Setup Guide” and then follow up with this checklist to ensure all steps are completed.
1. KOUNT TASKS | |
|---|---|
| PREREQUISITE |
2. COMMERCE TASKS | |
Settings REQUIRED Update the following settings:
| PREREQUISITE |
| DETAILED SETUP |
Prerequisite Tasks
This section describes all requirements that must be completed before you can begin setting up this feature. Once these tasks are complete continue to the next section.
Kount Tasks
Ensure that you have a working agreement with Kount and that you have access to your Kount Dashboard/Administration screen.
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 rule set, and the rule set must be activated for the rules to apply to transactions.
Commerce Tasks
AW Commerce task that must be completed first
Settings, Language Strings and/or HTML Widgets for this Feature
This feature may require updates to the following settings, language strings and/or HTML Widgets. Learn more about how to update and create Settings, Language Strings, and HTML widgets follow the links to the respective section.
Settings
These settings can be set by going to Settings > All settings or by using the UI described below in the Detailed Setup Guide.
Setting | Value |
kountcommandsettings.apikey | Find your unique API key in your Kount login admin. |
kountcommandsettings.devicedatacollectorendpoint | |
kountcommandsettings.riskinquiryserviceendpoint | |
kountcommandsettings.merchantid | Find your unique merchant id in your Kount login admin. |
kountcommandsettings.siteid | DEFAULT |
kountcommandsettings.connectiontimeout | 60000 |
Detailed Setup Guide
Install the KountCommand Plugin.
Configure the KountCommand Plugin.
Verify Transactions.
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. Configure the KountCommand Plugin
Once installed, 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 for dev, Unchecked for prod
API key: Find your unique API key in your Kount login admin.
Device Data Collector Endpoint: https://tst.kaptcha.com
Risk Inquiry Service Endpoint: https://risk.test.kount.net
Merchant ID: Find your unique merchant id in your Kount login admin.
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.
Click Save.
NOTE: These can also be set through Settings > All settings as desribed above.
3. Verify Transactions
Log into your Kount Dashboard and verify that you can see transactions in Kount.
Like this page? Click the like button below. Don't like this page and/or want to give feedback about this page, leave a comment below and Aspenware will address to improve this article.