Page Comparison

This guide will review how to set up {Feature/Enhancement Description} KountCommand in Aspenware Commerce. For more information about voucher set up see Peak Commerce Documentation or for general release notes, see {Link to 2.24 Commerce 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 provide 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 though 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.

• In the current Integration with Auth.net Kount rejects transactions where the Aspenware Short Description has strange characters in it. (ShortDescription LIKE ‘%’%' OR ShortDescription LIKE ‘%“%' OR ShortDescription LIKE ‘%–%' OR ShortDescription LIKE ‘%…%'). When this happened the guests get an error message and can’t complete the transaction. As part of this project, we need to add logic to either not pass these characters or better handle Kount Error handling. For example, if Kount rejects a transaction for a reason other than a decline or there is a failure of some type, let the transaction process anyway. Because we don’t know all the special characters that Kount does not like we need to find a solution that will allow the transaction to process if Kount returns a failure for any reason other than a decline.

NOTES from Standup:

See in Cycle-C

Pre-payment validation step - Kount begins tracking session as soon as the customer clicks “checkout”. So the validation happens before a call is even made to the payment gateway. The resort doesn't incur fees for a decline.

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

Language string for error message if your transaction is declined because of Kount.

Document the process once Complete Order (Click Checkout) is clicked (10 steps)

...

Key Terms

Persona

Description

Count

Description

Device Fingerprint

Feature Detail

Descriptions and images

Feature Detail Header 1

Paragraph

Feature Detail Header 2

Paragraph

Configuration Guide

Prerequisite Steps

POS Tasks

Infrastructure Tasks

Commerce Tasks

Settings, Language Strings, and HTML Widgets

Detailed Setup Guide

• Step 1

  1. sub-bullet

     1. sub bullet

Common Troubleshooting guide

Q: Question 1

A: Answer 1

DELETE CONTENT AFTER THIS LINE

How-to Guide of this page can be found here: [Internal] Release Guide

...

Configuration Guide

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: STARTDTE

    • Type: Select Date

  • Click Save UDF.

    Image Added

• 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

1. Install the KountCommand plugin.

• Go to Configuration > Local plugins.

• Scroll down to the KountCommand plugin.
  

  Image Added

• 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.

  Image Added

...

2. Configure the KountCommand plugin.

• Once installed, click Configure to get to the Configure - KountCommand Plugin screen.
  

  Image AddedImage Added

  • 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.
      

      Image Added

    • Click Save.

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

...

...