Data Collector FAQ and Troubleshooting

Quick links

• General Questions
• JavaScript
• Session Identifier
• Troubleshooting

General:

Q: Where do I get the Merchant ID?
A Sandbox Boarding Information document will be sent following the initial kick-off call with the Merchant ID and URLs associated with the DC and RIS processes. A separate document for production will be sent with the production service URLs once the test transaction have been certified.

Q: How do I receive a login to the AWC?
Kount will create the initial administrator user. Once the user has been created an automated e-mail will be sent requesting a password creation.

Q: Should I send production traffic to the test environment?
Production traffic should not be sent to the test environment due to the possibility of skewed scoring from the test orders.

JavaScript

Q: Where should I place the Javascript on my website?
On any webpage prior to the completion of the order, typically somewhere in the order summary or checkout process. This could be different if various payment methods take the customer “off of the site” prior to completion of the order.

Session Identifier

Q: What does the session identifier do?
The session identifier is used to join the device data with the order data sent by the RIS process. When the RIS process posts data to Kount it must use the session identifier that was created when the customer initiated the DC HTML.

Q: Does the session identifier need to be unique?
Yes, the session identifier must be unique over a thirty day time period. If there are duplicate session identifiers, device data originating from the DC process may be erroneously connected to RIS order data.

Q: Are there limitations on the session identifier?
Yes, it must be alpha-numeric with a minimum of 10 and a maximum of 32 characters.

Q: What should I use for the session identifier?
The merchant may determine what is used, as long as the limitation guidelines are followed. Potential identifiers include the unique web session, UNIX time stamp, and order number appended by time stamp.

Troubleshooting

Q: Is the correct Kount URL being used?
Verify that the correct Kount Data Collector URL is being used.

Q: Have appropriate DNS entries, NATs, and firewall settings been configured correctly?
Due to the security concerns regarding test environments or production environment the merchant’s network operations may need to verify that proper access is available.

Q: Does the JavaScript contain the correct Merchant ID?
Verify that the Merchant ID is the correct six digit ID supplied by Kount.

Q: Is the Session ID created in the DC process the same session ID being sent with the RIS post?
Ensure that the Session ID being created and stored during the DC process is the correct one being used in the RIS post to Kount and adheres to the session ID requirements.

Q: How do I know the Data Collection process is successful? Determine if the process was successful by using Developer Tools within Chrome or Firefox. A successful data collection will be represented by multiple GET/POST requests, including one in which the file, “fin,” indicates the data collection process is complete.