Fraud Mitigation Tool Integration Guide

Introduction

Welcome to the OTT Pay integration guide for KOUNT, a powerful fraud mitigation solution designed to enhance the security of your payment processing transactions. KOUNT’s advanced technology provides real-time risk assessment to minimize fraudulent activity and ensure the safety of your financial transactions.

What is KOUNT?

KOUNT is a comprehensive fraud detection and deterrence platform that utilizes device fingerprinting, machine learning, and artificial intelligence to analyze transactional data and flag suspicious activities. By default, KOUNT is activated for all OTT Pay accounts to bolster the security of payment processing. Learn More Understanding the DDC Flow (Device Data Collection)

To effectively utilize KOUNT, it is crucial to comprehend the DDC flow, which collects device-specific information to create a unique digital signature. This data enables KOUNT to identify devices and assess transaction risks based on historical behavior and global trends. Explore the Process Integrating the Web Client SDK for Device Data Collection into Your Website

To start collecting device data for web-based transactions, follow these steps to integrate the KOUNT Web Client SDK into your website: (Detailed Instructions , How to create a Session ID)

1. Obtain the latest SDK package using:

npm install @kount/kount-web-client-sdk

2. Configuring the SDK

const kountConfig = {
"clientID": "101193 ", // clientID assigned to you by OTT  
"environment": "PROD", // Environment for data collection provided by Kount
"isSinglePageApp": false // Or true, changes some internal behavior.
}

• For environment, when testing your integration with the kount-web-client-sdk, do not load test. Test new features against the TEST environment. When you are done testing, execute in the PROD environment.

3. Create a variable which represents a session ID to join device data with login or order information. It must meet the following:
   • Must be unique per request and for a minimum of 30 days.
   • Must contain only alphanumeric characters (0-9, a-z, or A-Z), dashes (-) or underscores (_).
   • Session ID values cannot exceed 32 characters in length.
   • Our suggestion is to create the session ID by integrating the merchant ID, timestamp data and a series of random characters. Samples as below. – MID-Timestamp in milliseconds-random number 4 digits – Example: ON00****97-1713534968007-1234
4. Invoking the SDK

import kountSDK from "@kount/kount-web-client-sdk";
kountSDK(kountConfig, YOUR_SESSION_ID);

5. Incorporate the session ID (names “session_id" in payload) into the payload when making a checkout request with OTT Pay Payment API.

Important Notes:

• If the session ID exceeds 32 characters or contains any invalid characters, an error is returned when attempting to download the SDK.
• Perform a test cooperated with OTT Pay after completing the integration, make sure the session ID is valid and working properly.

By completing these integrations, you’ll be able to harness the power of OTT Pay’s fraud protection system, extending a secure and reliable payment processing environment for your customers.

Supported cards