| Table of Contents |
|---|
This guide will review how to set up {Feature/Enhancement Description} in Aspenware Commerce. For more information about voucher set up see Peak Commerce Documentation or for general release notes, see {Link to Release Notes}
Overview
Kount 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 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
In addition to passing in all required fields, the Product Date is also passed though 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.
Key Terms
Key Term 1
Description
...
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
...