Effective: 2025-09-24
We changed our source data to use the same source as Card Brand Type in Transaction Details. This change improves the expected triggering of rules when using the Payment Brand condition.
Effective: 2025-09-24
We added a new rule condition to the Ekata section. The rule allows you to have transactions evaluated if the Ekata call made during the Risk Inquiry Process (RIS) processing was successful.
Note
An Ekata call might be unsuccessful if the Ekata service is down, or an Ekata trial API key has failed or expired.
For example, if you want to review any transaction without Ekata responses, choose the No option. The rule triggers as TRUE if no Ekata response was received.
This rule condition only displays if you have Ekata enabled and active. The condition is not evaluated if no Ekata call is attempted during RIS processing.
For more information about Ekata rules, go to How to Create an Ekata Rule.
Effective: 2025-09-23
The Autoblock List help you automatically reject identity verification attempts when specific Personally Identifiable Information (PII) matches items on your blocklist. This protects your business from known fraudulent identities, suspicious email addresses, phone numbers, and other risky information.
The Autoblock list enhances:
-
Data addition automation
Relevant data is automatically added to the blocklist. This ensures that the blocklist is always up to date with the latest information necessary for policy management.
-
Configurable lists
You can add specific data fields to the blocklist to customize the blocklists for your policies.
-
Integration with Case Closure
The automation triggers every time a case is closed that includes one of the predefined rejection codes. This ensures that only cases that meet certain criteria contribute to the blocklist, maintaining its relevance and accuracy.
-
Validation
A validation step has been added that checks whether the addresses added to the blocklist are identified as single-family addresses. This prevents the inclusion of inappropriate or irrelevant data, ensuring that the blocklist remains effective and targeted.
The autoblock list is located in Admin > Product Configuration > Identity Proofing > Autoblock List. For more information about creating an autoblock list, go to Autoblock List in Kount 360.
Effective: 2025-09-15
The API fields in Login and New Account Opening (NAO) reports have been updated to support version 2 of the API. To see which fields have been added, removed, or changed, refer to Account Protection API Version Comparison. Version 2 of the API has more fields, which allows you to run more detailed reports and gather more data. To access the reports in Kount 360, go to Analytics > Folders > Account Protection Reports.
Note
As data location has changed, some of your Saved Views may no longer work. Please recreate any Saved Views that use outdated data. For step-by-step instructions, go to Saved Views in Analytics Reports.
Effective: 2025-09-15
When you make changes to a policy set, your changes are noted as Pending Changes in Version Details until you publish the policy set. Before this update, there was no additional context as to what the pending changes consisted of. Now, you have the option to view all pending changes for a policy set.
To view pending changes, go to View pending changes for a policy set.
This update improves transparency by surfacing detailed information about pending and historical policy changes, gives users control to verify and manage unpublished changes before publishing them, and supports a more efficient review and publishing process.
After viewing the pending changes for a policy set, you can publish or discard policy set changes as needed. Go to Publish pending changes for a set or Discard set changes for more information.
Effective: 2025-09-09
You can now add activation schedules to policy sets in Policy Management. Using schedules completely automates when policy sets are activated. Scheduling helps you:
-
Reduce manual effort
Before this update, policy sets had to be manually activated. This could be time consuming or cause errors. Now, you can fully automate multiple policy sets to run depending on your use cases.
-
Adapt to various business requirements
Business requirements and risk profiles often change depending on time and purchasing trends. For example, fraud attempts might spike during specific hours or on weekends. You can create different policy sets and schedule them to run during these times to protect you against shifting fraud threats.
-
Improve efficiency and consistency
By automating policy set activation, you ensure a consistent and reliable risk strategy. Policy sets are guaranteed to run at the scheduled times to prevent fraud.
-
React to emerging threats
You can decrease the amount of time needed to create and run new policy sets for emerging fraud threats.
Scheduling is found in Policy Management > Decisioning.
For information on how to use scheduling, go to Schedules in Policy Management.
Effective: 2025-09-09
Order ID and Omniscore table values have been added to all Payments Fraud reports. To view these values, go to Analytics and open the reports folder, then select a report.
Effective: 2025-09-09
The Email Legitimacy Score has been added to the Payments Details report table in Analytics. This score helps you determine whether or not an email address is legitimate or fraudulent.
Effective: 2025-09-09
The time frame for Omnsicore distribution now displays in the title of the Omniscore Distribution widget on the Dashboard. This clearly identifies the time frame of the Omniscore data being displayed.
Effective: 2025-09-09
The Payment Details table has been updated to show all attributes for one order per table row. This helps you see all data for one order in a single location. Before this update, data was grouped based on a common attribute, like Policy Name.
Note
When multiple policies are executed, Payment Details might show duplicate data.
To find the Payment Details table:
-
Log in to Kount 360.
-
Select Analytics.
-
Open the Reports folder, then select Payment Details.
For more information about Analytics Reports, refer to our Analytics support articles.
Note
As data location has changed, some of your Saved Views may no longer work. Please recreate any Saved Views that use outdated data. For step-by-step instructions, go to Saved Views in Analytics Reports.