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.

Dispute and Chargeback Management

New RDR Cancellation Event Type

Effective: 2024-09-30

We updated our webhook configuration to include a new event type, RDR_CANCELLATION. This attribute reverses and cancels the RDR dispute. The funds that were taken from the merchant and given back to the cardholder during the RDR dispute process are sent back to the merchant.

This update is in response to Verifi allowing RDR disputes to be canceled within 72 hours. You must update your code to account for the RDR_CANELLATION attribute to prevent potential issues.

Payments Fraud

New Action Bar in Event Details

Effective: 2024-09-30

The actions widget in the Event Details page has been replaced with a new action bar. The new action bar increases review speed, accuracy, and efficiency by providing clear access to actions for the Event Details page. The action bar includes the following actions for a case:

Assign or reassign an agent
Edit a decision status — Approved or Declined
Write an event note
Access the event's history log
Mark the transaction result as a chargeback or refund

Additionally, the action bar includes improved status visibility:

Decision status
Case status
Assignee

Before:

After:

New API Improvements

Effective: 2024-09-30

We have added several new properties including identifiers related to data points, additional shopping cart item details, merchant-provided identifiers, and expanded person name, properties, and currency of all amounts.

Other improvements:

Added the option for Device to be excluded
Improved consistency, internationalization, and white-label support in property names and values
Removed properties that were not used or not helpful

To find the updated API properties, refer to the properties tables in the Payments Fraud Integration Guide.

New Conditions in Payments Fraud

Effective: 2024-09-30

We have added multiple new conditions for Payments Fraud.

sidebar. Table of New Payments Fraud Conditions

Category	Condition	Description
Device	Device First Seen	Date of when device was first seen in the Kount system based off of the Device Data Collector.
Device	Mobile Device	Evaluates if a mobile device (smartphone, tablet, etc.) is used or not.
Device	Region	The region associated to the device's location. The rule condition Data Collector Present must be added to the rule and set to Yes for this rule to run properly.
Email Address	Billing Email Status	Evaluates the billing email address from the request payload against different Melissa Data validation codes for Email Status.
Email Address	Shipping Email Status	Evaluates the shipping email address from the request payload against different Melissa Data validation codes for Email Status.
Email Address	Billing Email Trustworthy	The trustworthiness of the billing email address.
Email Address	Shipping Email Trustworthy	The trustworthiness of the shipping email address.
Email Address	Billing Email/Address Association	The association between the address in the request payload with the billing address linked to the billing email address. Can be true or false.
Email Address	Shipping Email/Address Association	The association between the address in the request payload with the shipping address linked to the shipping email address. Can be true or false.
Email Address	Billing Email/Name Association	The association between the billing name in the request payload with the billing address linked to the email address. Can be true or false.
Email Address	Shipping Email/Name Association	The association between the shipping name in the request payload with the shipping address linked to the email address. Can be true or false.
List	Device Country	The physical country that the device is located in.
List	IP Registering Org	The IP Registering Organization associated with the IP Address.
List	User ID	The unique Identifier assigned to an end user sent by the customer in the Kount API request payload.
List	Username	The username of an end user sent by a customer in the Kount API request payload.
Network	TOR Detection	A true/false flag indicating the use of a TOR network. If the TOR network is being used, the location of the user has been obfuscated and there is no reliable way to use attributes to identify device authenticity.
Network	IP Address Mismatch	The evaluation of the IP address passed in with the login request to the IP address collected by the device collector.
Network	IP Address Range	The evaluation of the device during login against a range of IPs. The range can only be within the final octet.
Network	IP Address Value	The evaluation of the IP address of the device during login.
User and Accounts	Account Age	The account age is determined on the account creation date sent with the login request.
User and Accounts	Time of Day	A time of day and range before or after a certain time to create a time frame.

New Explore Mode and Reporting Enhancements

Effective: 2024-09-30

Explore Mode has been added to Analytics in Payments Fraud. Previously, this feature was only in Account Protection. Explore Mode provides an isolated environment where you can customize workbook content and perform ad hoc analysis without altering previously saved versions. This improves reporting by decreasing the time it takes you to create reports and analyze data.

For more information about Explore Mode and how it works, refer to Explore Mode in Kount 360.

New Fraud Prevented Widget for the Dashboard

Effective: 2024-09-30

The Fraud Prevented widget has been added to the Payments Fraud dashboard. This widget displays the value of fraud that has been prevented. This data helps quantify the value provided by Kount 360.

Note

You can drag and drop widgets in your custom layouts to organize them as needed.

Persona Data Added to Event Details and Case Queue

Effective: 2024-09-30

Persona Data has been added to the Order Details for all events and cases in Event Details and Case Details. The Persona service is a Graph Clustering Engine that builds clusters of connected Personally Identifiable Information (PII). The cluster of PII is called the Persona Data and is used in machine learning models to provide several datasets. You can use this information to expose trends and determine if an order is fraudulent or to identify attacks happening across multiple orders.

A screenshot of the Persona Details widget in Order Details.

The Persona datasets are:

Kount Network — This includes network-wide data for Associated Payment Methods, Associated Emails, and Associated Devices.
Merchant Specific — This includes the Riskiest Country, Total Bank-Approved Orders, Total Bank-Declined Orders, and Max Velocity.
Device Collection — This indicates if the device data was successfully collected from the end user's device.

Note

Device Collection is located in the Order Info, not in the Persona Data tile.

Command

Added more Distance Rule Conditions

Effective: 2024-09-11

Four new distance conditions have been added to the Rule Conditions list in the Rules Editor. These conditions can be used to identify transactions that are an unusual proxy distance from the billing or shipping locations.

The new distance conditions are:

Distance from Proxy to Billing Address
Distance from Proxy to Shipping Address
Distance from Proxy to Billing Phone
Distance from Proxy to Shipping Phone

Go to Rule Conditions to view all available rule conditions in the Agent Web Console.

Added Recovery Status for Interrupted Adhoc Reports

Effective: 2024-09-11

When running an Adhoc Report and a disruption occurs, the report status now automatically changes from Working (W) to Error (E). Before this fix, reports would get stuck after experiencing a disruption, which would require users to manually change the report status.

Added Report ID in the User Interface for Adhoc Reports

Effective: 2024-09-11

The Report ID column has been added to Adhoc Reports. Now, after an adhoc report is submitted, the Report ID column displays between the Date and Description columns. This update helps users find the Report ID quicker, which can reduce processing delays.

Users can Delete Rule Groups with Titles that Contain Special Characters

Effective: 2024-09-11

Users can now delete rule groups with titles that contain angle brackets (< or >), single quotes ('), double quotes ("), or ampersands (&) in the Auto Agent and Auto Decision Engine. Prior to this change, when a user tried to delete a rule group with a title that included the previously listed special characters, the rule group would not be deleted.

Shipping Address Type Now Displays as an Icon on Transaction Details

Effective: 2024-09-11

The Shipping Address Type (SHTP) now displays as an informative icon on the Transaction Details page for recently added values Delivery (DE) and Pick-up (PU). Prior to this change, DE and PU were displaying as text.

Before:

After:

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 toKount 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

Dispute and Chargeback Management

New RDR Cancellation Event Type

Payments Fraud

New Action Bar in Event Details

New API Improvements

New Conditions in Payments Fraud

New Explore Mode and Reporting Enhancements

New Fraud Prevented Widget for the Dashboard

Note

Persona Data Added to Event Details and Case Queue

Note

Command

Added more Distance Rule Conditions

Added Recovery Status for Interrupted Adhoc Reports

Added Report ID in the User Interface for Adhoc Reports

Users can Delete Rule Groups with Titles that Contain Special Characters

Shipping Address Type Now Displays as an Icon on Transaction Details

Kount 360

Added Channel to Webhooks

Command

Improved Omniscore fraud detection stability

Improved Omniscore prediction accuracy

Data on Demand

New chargeback fields for TRANSACTION_STATES view in Data on Demand

Understanding BINs

Transitioning from 6 to 8-Digit BIN

Preparing for the BIN Expansion

Frequently Asked Questions

Additional Resources

Can’t find what you’re looking for?

Contact Us

Welcome to
Kount Support