Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

This guide will review how to set up KountCommand in Aspenware Commerce. For more information about Kount, see Aspenware Commerce Documentation or for general release notes, see {Link to Release Notes}

Overview

Kount Command is now available as a plugin for all payment gateways that Aspenware supports. Detailed information about Kount is available here - Configuration: Kount This enhancement utilizes APIs provided by Kount to insert the KOUNT query/response either PRE or POST authorization. - known as KOUNT Command. Specific features include:

  • Integration to the Kount API before the credit card is sent to authorize. https://kount.github.io. This happens in the pre-payment validation step - Kount begins tracking the session as soon as the customer clicks “checkout”, before a call is made to the payment gateway. The resort doesn't incur transaction fees for a decline.

  • In addition to passing in all required fields, the Product Date is also passed through to Kount as a user-defined field so that resorts can prioritize investigating same-day bookings or bookings for tomorrow as these have the highest fraud potential.

NOTES -REMOVE FROM FINAL DRAFT

See in Cycle-C

Date of birth passing - Yo wants this, but Derrick is thinking

Configuration Guide

Kount Tasks

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

  • Ensure that all Kount rules have been defined per your resort’s Kount strategy.

Commerce Tasks

1. Install the KountCommand plugin.

  • Go to Configuration > Local plugins.

  • Scroll down to the KountCommand plugin.

  • INSERT SCREEN SHOT of the plugin

  • Click Install.

  • Make sure the plugin is both installed and enabled.

  • If it is not enabled, click Edit and check Is enabled?


2. Configure the KountCommand plugin.

  • Once installed, click Configure.

    • Enter data into the following fields:

      • Multi-store configuration: WHAT ARE THE OPTIONS HERE?

      • 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 (What is the recommendation here?)

      • 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 and set the following settings:

Setting

Value

kountcommandsettings.apikey

Find your unique API key in your Kount login admin.

kountcommandsettings.devicedatacollectorendpoint

https://tst.kaptcha.com

kountcommandsettings.riskinquiryserviceendpoint 

https://risk.test.kount.net

kountcommandsettings.merchantid

Find your unique merchant id in your Kount login admin.

kountcommandsettings.siteid

DEFAULT

kountcommandsettings.connectiontimeout

4000

3. Test the feature and verify that transactions can be seen in Kount.

Log into your Kount Dashboard and verify that you can see transactions in Kount.

Common Troubleshooting guide

Q: Question 1

A: Answer 1


 


  • No labels