The session identifier, or sessionID, is used to join the device data with the order data sent by the Risk Inquiry System (RIS) process. When the RIS process posts data to Kount, it must use the session identifier that was created when the customer initiated the data collector HTML.
The customer determines what the sessionID is, but you must follow the limitation guidelines. Many customers use a portion of the application session that is generated when the page is created as the session identifier.
Limitation guidelines state that it must be alpha-numeric value with a minimum of one character and a maximum of 32 characters.
The session identifier must be unique over a 30-day time period. If there are duplicate session IDs, data obtained via the Device Data Collector may be erroneously linked to RIS order data.
The integration allows for two ways to create a sessionID.
Let Kount Do it
This method is recommended by Kount. The value (UUIDv4 without the dashes) is created by Kount and is returned when the device data collection SDK is downloaded. This method ensures the uniqueness of the sessionID, and also ensures that it meets the requirements of a valid sessionID. This is accomplished by excluding the sessionID parameter in the call to download the Device Data Collection SDK, like this (web implementation only):
Generate your Own
If you want or need control over the sessionID that is passed to Kount, you have the option to generate your own. This is accomplished by creating the sessionID that meets the criteria described below and including that in the call to download the Device Data Collection SDK (web implementation only). Assuming the session ID used in this example is abcdefg12345abababab123456789012, the call to download the SDK looks like this:
How do I Access my Session ID
Whether you let Kount generate your sessionID, or you generate your own, it is made available to the script on the page via the ka.sessionId attribute that is included in the downloaded Device Data Collection SDK. This is discussed in greater detail on the Web Client and Browser Setup documentation page.
Session ID Requirements
- SessionID must be unique per request. They must be unique for a minimum of 30 days.
- SessionID must contain only alphanumeric characters (0-9, a-z or A-Z), dashes (-) or underscores (_).
- SessionID values should be 32 characters in length. SessionID values of less than 32 characters are accepted, but it is strongly recommended to use a 32 character value.