Kount360

Kount360 is your AI-powered security guard that checks transactions before they hit your payment processor. It uses advanced machine learning and device fingerprinting to catch fraudsters while letting good customers through smoothly.

Think of it as a smart filter that learns from millions of transactions across the internet to protect your business from fraud, chargebacks, and bad actors.

How VRIO + Kount360 Works Together

The Protection Flow

1. Customer visits your site → Kount360 silently collects device fingerprint
2. Customer places order → Your site/app sends order to VRIO API
3. Pre-gateway check → VRIO automatically sends details to Kount360 BEFORE attempting payment
4. Kount360 analyzes risk → Combines device data + order info for instant decision
5. Decision made:
   • APPROVE → Payment proceeds to gateway normally
   • DECLINE → VRIO API returns order_precheck_fail error, no gateway attempt
6. You stay protected → Risky transactions never reach your payment processor

What Events Does Kount360 Track?

Kount360 continuously learns from your business by listening for key events:

• Transaction Completed → Updates with payment results to improve future decisions
• Refunds/Voids → Identifies potential refund abuse patterns
• Chargebacks/Alerts → Learns from disputes to prevent similar fraud

This feedback loop makes Kount360 smarter over time, improving accuracy specifically for your business.

Getting Started

What You'll Need

• Active Kount360 account
• API Key from your Kount360 dashboard
• Client ID (also called Merchant ID)

If you can't locate these items in your Kount360 dashboard, reach out to your Kount360 account manager for assistance.

Quick Setup Guide

1. Add the Connection

   • Go to Settings > Connections > Add New Connection
   • Find Kount360 under the "Fraud" category
   • Click "Connect Now"

   

   
   

2. Enter Your Credentials

   • Connection Name: Something descriptive like "Kount360 Production"
   • API Key: Get this from your Kount360 dashboard
   • Client ID: Your Kount360 merchant ID
   • Live Mode: ✓ Check for production, ✗ Uncheck for sandbox
   • Test Mode: ✓ Check to see decisions without blocking orders (see details below)
   
   

3. Add the Pixel

   This is the secret sauce! The pixel collects device fingerprints from your customers.

   Add this code to your checkout and product pages ( note you can get the exact pixel from the connection page after it has been added, you will only need to generate the UNIQUE_SESSION_ID):

   HTML

   <iframe width=1 height=1 frameborder=0 scrolling=no 
           src="https://your-vrio-domain.com/pixel/k?conn_id=YOUR_CONNECTION_ID&session_id=UNIQUE_SESSION_ID">
   </iframe>

   ⚠️ Critical: The session_id must match between the pixel and your order submission!

4. Save

   • Click "Save" to activate

5. Add to Campaign and Test

   Once you have the connection added, you need to add it to the campaign you want to enable it on. Once that is added, place test orders on the campaign and you can review all activity on the customer screen.

Understanding the Session ID

The session ID is the bridge between device data and order data. Here's why it matters:

What's a Session ID?

A unique identifier you create for each customer visit. Think of it like a temporary name tag that connects everything the customer does.

The Golden Rule

Same session ID everywhere!

• When the pixel loads → Use the session ID
• When creating the order → Use the SAME session ID
• This is how Kount360 knows the device data belongs to this specific order

Where to See Results

After Kount360 analyzes an order, you'll find all the details in the Fraud tab on the customer screen:

Click on the ID link to see the full response

What You'll See:

• Risk Score: 0-99 (higher = riskier)
• Decision: APPROVE or DECLINE
• Device Info: Type of device, location data, etc.
• Triggered Policies: Which Kount360 rules affected the decision
• Session Details: Confirmation the device data was captured

Configuration Options Explained

Test Mode

When Test Mode is enabled, Kount360 still analyzes every transaction and provides risk scores and decisions, but no orders are actually blocked. All transactions proceed to the payment gateway regardless of Kount360's decision. This lets you:

• See what would have been blocked in your Fraud Details
• Fine-tune your Kount360 rules without impacting sales
• Build confidence before enforcing decisions

Live Mode

Controls which Kount360 environment you're using:

• ✓ Checked = Production environment (real fraud data)
• ✗ Unchecked = Sandbox environment (for development/testing)

These are independent settings - you can use Test Mode in either environment.

Risk Once Per Card

When a new order is pre-checked (before hitting the gateway), Kount360 performs a "Risk Inquiry" - and they charge per inquiry. This setting controls how often you pay for those checks:

• ✅ Enabled: Only one Risk Inquiry per unique card number
  • First new order with a card = Full risk check (charged)
  • Subsequent new orders with same card = Reuse the original decision (no charge)
  • All completed transactions still send updates to Kount360 for learning
• ❌ Disabled: Risk Inquiry for every new order
  • Every new order gets a fresh risk check (charged each time)
  • More thorough but higher costs

Important:

• Risk Inquiries only happen on new orders (initial purchases)
• Renewals/rebills never trigger Risk Inquiries - they skip the pre-check entirely
• All completed transactions (new orders, renewals, refunds, chargebacks) still flow to Kount360 as events to improve their fraud models

What Data Gets Shared?

VRIO automatically sends the right information to Kount360 for accurate fraud detection:

Customer Information

• Name, email, phone number
• Billing and shipping addresses
• Customer account age
• IP address (when available)

Order Details

• Order ID and amount
• Product details (names, SKUs, quantities)
• Campaign information
• Any custom tracking fields

Payment Data

• First 6 and last 4 digits of card (middle digits are protected)
• Card type and bank info
• Transaction results

🔒 Privacy Note: Full card numbers are never sent. Kount360 uses a secure hashing method to identify cards without exposing sensitive data.

Troubleshooting Common Issues

🔴 Device Data Missing

The Problem: Kount360 isn't seeing the device fingerprint

The Fix:

1. Open browser developer tools (F12)
2. Check Network tab for the pixel request
3. Verify the session_id in the pixel URL matches your order
4. Look for JavaScript errors blocking the pixel

🔴 "Authentication Failed"

The Problem: Can't connect to Kount360

Check These:

• API Key is from Kount360 dashboard (already Base64-encoded)
• Live Mode matches your credentials (sandbox vs production)
• Connection is marked Active

If credentials are correct but still failing, reach out to your Kount360 account manager for assistance.

🏥 Need Help?

Check connection logs in VRIO:

1. Go to the customer screen
2. Click the "Webhooks" tab to see connection logs
3. Click the "Fraud" tab to see Kount360 results
4. Error messages will show exactly what went wrong