Common Troubleshooting: Kount Command

Q: I installed the Kount Command plugin and now checkout doesn’t work. What’s wrong?

A: The Kount Command configuration must be completed in its entirety before checkout will work. If the plugin has been installed, but the site has not been restarted, checkout won’t work. If the plugin has been installed and the site has been restarted, but the plugin has not been enabled and configured with the API key, checkout will not work. The plugin must be installed, enabled and configured for checkout to work. For configuration steps, see Configuration: Kount Command.

Q: We were using the old Kount plugin and upgraded to the Kount Command plugin and now checkout is failing. How do we fix this?

A: The Kount Command 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. You must uninstall the original Kount plugin and restart the site. Once the new Kount Command plugin has been enabled and configured with an API key, checkout will work.

Q: Why is Kount is returning an error when a guest attempts a specific product?

A: Kount enforces a 254 character/254 byte limit on their product name field and product description field. Exceeding the limit causes Kount to send back an error, and blocks the customer from completing the sale. To avoid this situation, resorts must never exceed the 254 character limit on product name. Product Names that include special characters ( apostrophes, hyphens, html styling, etc.) are at risk of triggering errors because those characters use extra bytes, inflating the byte count over the character count. Aspenware no longer passes the product description from the PDP. Instead, we pass the product name. To resolve the issue, edit the product name to conform to the 254 character/254 byte limit.