Kount

Welcome to
Kount Support

How can we help?

Search

Select a Product

Kount 360

Kount 360 is trust and safety technology that protects your business across the entire customer journey.
Midigator

Midigator provides a complete, intelligent chargeback solution through an easy-to-use web portal.
Kount Command

Prevent digital payments fraud with accurate identity trust decisions, powered by AI, machine learning, and global network data.
Dispute and Chargeback Management

Stop disputes before they become chargebacks from one dashboard that integrates with post-authorization tools from major card brands.
- Getting Started
Data on Demand

Access thousands of additional data points that can improve marketing campaigns, upsells, and cross-sells.
- Getting Started

Support Updates

Note: Neustar (Targus/TARGUSinfo) is set to be deprecated at the end of January 2024 and will no longer be available in Kount Command. Ekata, an available alternate solution to Neustar, provides significantly more valuable data at a lower cost. To ensure continuous coverage of these services, contact your Customer Success representative to implement an appropriate solution.

Neustar, also known as Targus or TARGUSinfo, is an optional third-party service offered within the Agent Web Console (AWC). Targus defines the relationship between the input name, address, and phone number. It then provides a Contact Quality Rating (CQR) outlining the relationship between the different data points. The ratings can be used to automate processes that utilize the information on the name, address, and phone number relationship.

Neustar may be useful for merchants who need additional information and verification of order information such as customer name, shipping address, and phone number.

Neustar subscribers will have access to Neustar data in the Agent Web Console (AWC), where they will be presented with the detailed responses to Neustar callouts.

Contact Quality Rating

The Contact Quality Rating (CQR) is the score assigned by Neustar and can be found at the top of the Contact Quality Rating gadget. The CQR defines the relationship between the input name, address, and phone number. The following provides a result description and interpretation for each CQR. These ratings can be used to automate processes that utilize information on the name, address, and phone number relationship.

CQR	Result Description	Interpretation
1	Invalid Address and Phone	The address cannot be standardized according to the USPS, and the phone number cannot be dialed.
2	Name, Address and Phone all go together	All three are linked together.
3	Name and Phone go together, no address available	Name and phone are linked together but there is no address information available.
4	Name and Phone go together, TargusInfo has different address	The name and phone are linked together and there is a different address associated with the phone.
5	Address and Phone go together, no Name available	The address and phone are linked together and there is no name associated with the phone.
6	Address and Phone go together, TargusInfo has different consumer Name	The address and phone are linked together and there is a different consumer name linked with the phone.
7	Address and Phone go together, TargusInfo has different business name	The address and phone are linked together and there is a different business name associated with the phone.
8	Name and Address go together, input Phone is invalid	The name and address are linked together and the phone number cannot be dialed.
9	Name and Address go together, input Phone is business	The name and address are linked together and the phone submitted is associated with a business.
10	Name and Address go together, input Phone is wireless	The name and address are linked together and the phone submitted is wireless.
11	Name and address go together	The name and address are linked together.
12	Name and Phone do not go together, Targus has different Consumer name	A different consumer name is associated with the phone.
13	Name and Phone do not go together, Targus has different Business name	A different business name is associated with the phone.
14	Wireless Phone, no name or address match	The phone submitted is wireless and is not linked to the name and address submitted.
15	Valid Address but Invalid Phone	The address can be standardized according to the USS and the phone number cannot be dialed.
16	No Data is Available	There is no information available for the input name, address or phone number.
0	No Result is Available	No rules can be satisfied.

Additional CQR Data Descriptions

The standard Neustar page contains four data tables presenting information about the transaction, the data scrutinized to calculate the CQR, and address information. The following defines the variables that might be presented within the CQR table.

CQR Table Field	Variable Data Outputs
CQR	0-12
Phone Verify	Y: Name matches phone number N: Name does not match phone number I: No name submitted U: No data available X: Data missing from either the input record or the TARGUSinfo repository
Phone Type	L: Landline W: Wireless U: No data available X: Data missing from either the input record or the TARGUSinfo repository
Listing Type	B: Business C: Customer P: Pay Phone F: Fax O: Other U: No data available X: Data missing from either the input record or the TARGUSinfo repository
Valid Address	Y: Address standardized against USPS valid address ranges. N: Address cannot be standardized against USPS valid address ranges. X: Data missing from either the input record or the TARGUSinfo repository.
Valid Phone	Y: Area Code and Exchange can be validated against NANP records. N: Area Code and Exchange cannot be validated against NANP records. X: Data missing from either the input record or the TARGUSinfo repository.
Phone Active	Y: The phone number has been active at the current address for 6 months or more. N: The phone number has not been active at the current address for 6 months or more. X: Data missing from either the input record or the TARGUSinfo repository.
On Do Not Call	Y: The phone number is listed on FTC or DMA national Do Not Call lists or any Do Not Call state list. N: The phone number is not listed on FTC or DMA national Do Not Call lists or any Do Not Call state list. X: Data missing from either the input record or the TARGUSinfo repository.
Near Address	Y: The address of the phone switch is within 6 miles of the submitted address. N: The address of the phone switch is not within 6 miles of the submitted address. X: Data missing from either the input record or the TARGUSinfo repository.
Recent Change	Y: Directory Assistance records indicate that the phone was removed from phone company listings within the past 18 months. N: Directory Assistance records indicate that the phone was not removed from phone company listings within the past 18 months. X: Data missing from either the input record or the TARGUSinfo repository.
Phone Provider	OCN: The Operating Company Name S: This is a Switched Provider, indicating the input phone is valid and has been ported. U: The input phone is valid and has been ported but no OCN information is available. X: Data missing from either the input record or the TARGUSinfo repository.

Payments Fraud

New Case Management report in Analytics

Effective: 2025-06-10

We added a new report for Case Management in Analytics. This report includes an event timestamp, case statuses, and changed values. You can sort, filter, and export elements of this report as needed. To find this report, go to Analytics > Payments Fraud Reports > Case Management.

Case Management analytics offers a customizable view of manual review activities, providing the information needed to effectively manage case volumes and activity.

For more information about Analytics reports, go to our Analytics articles on the Kount Support website.

New Comparison Variables conditions in Policy Management

Effective: 2025-06-10

We added the following conditions to the new Comparison Variables section in Policy Management:

Compare Date Variables
Compare Number Variables
Compare String Variables

Compare Variable conditions allows you to compare two sets of variables to each other, including any custom fields you have created.

These conditions are located in Policy Management > Decisioning > Payments Fraud (event type) > Policies > Payment Conditions > Compare Variables. Go to Creating, Editing, and Deleting Policies and Payments Fraud Policies for more information.

Account Protection

New Login and New Account Opening Event Types in the Dashboard

Effective: 2025-06-06

We added two new Event Types to select from in the Dashboard. Now that there are multiple Event Types to choose from, we added an Event Type selection menu. The available Event Types are Login, New Account Opening, and Payments Fraud.

Note

The available Event Types depend on which ones you are subscribed to.

Selecting an Event Type changes which widgets display in the custom layout view. You can build and save custom layouts per Event Type. For more information on creating custom Dashboard layouts, go to Customizing the Dashboard.

Kount 360 Fundamentals

Updated user interface for Kount 360

Effective: 2025-05-29

We've refreshed the Kount 360 interface with a cleaner visual theme. Updates include a new color palette, improved table styles, and better readability for a more consistent experience across the platform.

All existing processes and workflows remain unchanged. See the screenshots below for a comparison and preview of the new look:

Updated session timeout duration and user interface notification

Effective: 2025-05-29

We updated the duration that a user can be inactive before the session times out and sends the user back to the login screen. When you are inactive for 15 minutes in all open browser tabs, a modal displays with a two-minute timer. When the timer runs out, you are automatically logged out. The modal gives you the option to stay logged in.

When the modal displays, select Yes to stay logged in.

Note

Selecting no automatically logs you out.

User activity is measured in all open browser tabs. If you become active in a secondary tab where the modal did not display, the timer resets and your session remains active.

Improvements to API Key Management

Effective: 2025-05-14

We've updated how API keys are created and managed. You can now generate multiple keys for a single client ID, lifting the previous two-key limit.

The interface has also been streamlined. API keys are organized into collapsible sections for easier viewing, and the button is now labeled Generate API key:

For step-by-step guidance, refer to the updated documentation: Generate an API Key.

New self-service account unlock feature

Effective: 2025-05-14

If you get locked out of your account due to multiple failed attempts, you can now submit a verification request. The request is sent to your account email. The verification link expires after five minutes. If you receive a request to unlock your account, but you did not submit a request, you can ignore the email.

To use this feature, refer to Unlocking Your Kount 360 Account.

SMS authentication added to MFA sign-in options

Effective: 2025-05-14

When signing in to Kount 360, you have the option to set up multiple different Multi-Factor Authentication (MFA) options. We have now enabled the ability to authenticate with SMS text messaging.

To set up MFA for SMS messaging, refer to Signing in to Kount 360 with Multi-Factor Authentication.

Account Protection

New Custom Fields for New Account Opening and Login Event Types

Effective: 2025-05-29

We have added the ability to add custom fields to the New Account Opening and Login request payload. You can also now create custom fields in the user interface in Policy Management Tools. All newly created custom fields are automatically added to the conditions catalog in Policy Management so that you can build policies and segments.

Example of Custom Fields in Policy Management:

For more information, go to Custom Fields in Kount 360.

Payments Fraud

Update to Custom Fields

Effective: 2025-05-29

In Payments Fraud, you can now create and update custom fields in the user interface. Previously, Payments Fraud users could only create custom fields through the Orders API. For more information, refer to Custom Fields in Kount 360.

New Payments Fraud conditions

Effective: 2025-05-28

The following conditions have been added to Payments Fraud in Kount 360:

Persona:

Associated Devices (Kount Network)
Associated Emails (Kount Network)
Associated Payment Methods (Kount Network)
Max Velocity (Merchant Specific)
Riskiest Country (Merchant Specific)
Total Bank-Approved Orders (Merchant Specific)
Total Bank-Declined Orders (Merchant Specific)

Device:

Apple Private Relay
Browser
Operating System

Order:

Total Items in Cart

For a complete list of Payments Fraud conditions and their descriptions, go to Payments Fraud Policies.

Strings of numbers are used for different facets of everyday life. These categorical numbers are often unique to a person, place, telephone, credit card, and so on. However, when you have a limited string of numbers, eventually you will run out of unique variations. For instance, telephone numbers have an area code which help bucket phone numbers.

The 3-digit area code allows for 7.9 million unique telephone numbers; but as more people move into an area and register new phones, eventually you run out of unique variations. Thus, you would need to create another area code to accommodate newly registered phones.

The same is true of credit card numbers, more specifically, the credit card Bank Identification Number (BIN).

Understanding BINs

A BIN, otherwise known as an Issuer Identification Number (IIN), is the first four to six numbers of the 16-digit personal account number (PAN) that identifies the issuing bank, the card network (Visa, Mastercard, etc.), and so on. The BIN also identifies which type of card is being used (debit, credit, corporate, etc.). BINs are updated daily which allows point-of-sale (POS) software to automatically identify the type of card being processed.

Transitioning from 6 to 8-Digit BIN

Currently, card issuers are using the first six digits of the PAN for BIN ranges; but, the allotted number strings in that range are running out. Therefore, the BIN is being expanded to accommodate eight digits of the PAN instead of six.

To address the limitation of available numbers that can be used in a BIN, BIN is expanding to eight digits. Visa and Mastercard have both committed to implementing 8-digit BINs by April 2022. After April 2022, the payments industry will be operating with both 6 and 8-digit BINs. Card issuers are not required to use new 8-digit BINs because some of them still have a usable range of 6-digit BINs. These companies might not use the 8-digit BINs for a few years or until their supply of 6-digit BINs runs out.

However, all new cards released after April 2022 will include an 8-digit BIN, while International Card Schemes will only be issuing 8-digit BINs. As such, both 6 and 8-digit BINs will continue to be supported. Contact your acquirer for more information on how to accept and manage both 6 and 8-digit BINs.

Preparing for the BIN Expansion

In anticipation for the BIN expansion, you should contact your card acquirer to better understand what this change means for your business. For example, customer receipts might need to be adjusted to accommodate 8-digit BINs. Other actions you can take are:

Updating POS hardware/software
Reviewing chargeback handling
Reviewing fraud management systems
Updating security tools
Reviewing how you accept payments with 6 and 8-digit BINs

Multiple companies are getting ready for the 8-digit BIN including Kount.

Kount is preparing its services to accommodate the BIN expansion and provide compliance to the subsequent revised PCI DSS requirements. Kount customers that incorporate sending 8-digit BINs will be able to see additional card details in the Agent Web Console (AWC) and reports, including issuer name and prepaid card indicator. Customers will also see additional BIN attributes when creating rules in the AWC.

Kount customers will have the option to send 8-digit BIN to receive accurate BIN issuer information. If a customer chooses to continue sending 6-digit BIN, the accuracy of BIN matching results might decrease. To offset this possibility, Kount is integrating an enhanced BIN lookup to improve matching rates (coverage) and accuracy.

Frequently Asked Questions

Will fees change when accepting cards with an 8-digit BIN?

Ask your card acquirer for more information about associated fees with 8-digit BIN.

Will card numbers be longer than before?

No. The 8-digit BIN is included in the existing card number; therefore, the PAN will continue to have 16 digits.

Will 8-digit BIN change how we use 3D Secure?

3D Secure 1.0 does not support 8-digit BINs. EMV 3D Secure is the minimum requirement to support 8-digit BIN numbers.

When will the BIN change for acquirers?

The acquirer reference number (ARN) is generated during a card payment transaction. The ARN is a 23-digit number with a check digit at the beginning and is followed by the BIN for the acquiring bank or processor. This BIN is not subject to change.

Will the new 8-digit BIN affect my compliance with PCI DSS?

There have been no recent updates to PCI rules concerning the number of digits that are required to be removed with storing card data.

Kount

Welcome to
Kount Support

How can we help?

Search

Select a Product

Kount 360

Midigator

Kount Command

Dispute and Chargeback Management

Data on Demand

Support Updates

Contact Quality Rating

Additional CQR Data Descriptions