| Table of Contents |
|---|
...
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.
NOTES from Standup:
See in Cycle-C
Key Terms
Key Term 1
Description
Key Term 2
DescriptionPre-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
...
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
...