2026-10-14
We updated the navigation in Kount 360 to improve speed and performance. This update resolves a side navigation routing issue that caused latency and screen flashing, and it eliminates forced page reloads when clicking side navigation links to restore a smooth single-page application experience.
2026-10-13
We have expanded the Email Verification Service model to incorporate additional event data, including Login, New Account Opening, Identity Proofing, and Authorized Payment Protection events. Previously, email touchpoints were evaluated using more isolated data sets. This update consolidates these data sets into a unified, global view of an email's history. This comprehensive data set improves the system's ability to identify suspicious emails at the point of login or account creation, while also establishing trust profiles earlier for legitimate customers to reduce checkout friction.
Impact on Email Attributes
Because historical activity from these additional events is now integrated into global email profiles, there are changes in the following data attributes:
-
First Seen Date (shifts to an earlier date)
-
Last Seen Date
-
Occurrence Count
-
Usage Score
Example: An email previously recorded with a First Seen Date of 01/01/2026 during a payment event, but that was active during an earlier New Account Opening event on 12/01/2025, will now display its global First Seen Date as 12/01/2025.
No action is required to receive this update.
If your organization relies on First Seen Date, Last Seen Date, Occurrence Count, or Usage Score for downstream routing, logic, or internal decision-making outside of Kount 360, review your configurations. Your existing risk scores and policies remain unaffected by this update.
2026-10-15
We added the Ekata Insights report to Analytics. This feature integrates high-fidelity verification data from Ekata directly into your Analytics dashboard. By combining Ekata identity signals with standard transaction data, this report correlates automated Policy Management decisions with your manual Case Queue review process.
The report defaults to a standard Last 7 Days view for immediate insights upon access, with customizable date ranges available.
Note
This report only appears for organizations currently subscribed to Ekata services. To add Ekata Insights to your account, contact your Customer Success Manager.
Key metrics and features
-
Ekata Call Order Total Count: A new section tied to your selected Event Timestamp (period) that works as a complement to the Daily Count.
-
Request Source Tracking: The report categorizes Ekata calls by how they were triggered, allowing you to monitor volume across three methods:
-
Policy Management: Initial inquiry flow
-
Queue Manager: Post-Order Case Manager flow
-
Order Details: Triggered manually via the portal
-
Benefits:
-
Eliminate the need to switch between the user interface and separate Ekata look-ups. You can now correlate identity risk scores with order outcomes in a single, centralized view.
-
Analyze aggregated, Ekata-specific identity signals at the transaction level to identify broader identity fraud trends.
To access this feature, you must be subscribed to Ekata services then sign in to Kount 360 and go to Analytics > Folders > Payments Fraud Reports > Ekata Insights.
2026-10-15
We updated the Anomalies report in Analytics. The report features a new visualization format and separated graphs to better highlight data trends.
Updates include:
-
All graphs now utilize a line graph instead of a bar graph and displays upper and lower bounds. Predictions are kept as a continuous line, and actual observations are now added as a separate line. Distinct timestamps have been added to the graphs to indicate anomaly occurrences.
-
Bank Authorization Status data is separated from one combined graph into three graphs for Approved, Declined, and Null statuses.
Action Required for Saved Views and alerts
You might need to recreate conditional alerts and/or Saved Views depending on how your existing ones were created.
2026-10-06
We added a new Global Search feature to Kount 360, allowing you to locate Payments Fraud orders from the past two years using a single search term. Global Search simultaneously scans multiple data points across your orders, eliminating the need to know exactly which field contains your target value before searching.
The search box remains in the top navigation bar, allowing you to enter a search from any page.
You can use a single query to search transaction identifiers (OrderID, payment token, session ID), contact data (emails, phone numbers), card data (BIN and last 4 digits), location data, and custom data fields. Global Search automatically applies the optimal matching logic for each specific data type. It requires complete values for exact identifiers (like phone numbers or OrderIDs), allows partial matches for emails and names, and utilizes fuzzy matching for address fields to account for typos or misspellings.
Note
If your search yields exactly one matching order, you are routed directly to that Order Details page. If multiple orders match, you are taken to a filterable results table with your matching values highlighted.
For complete documentation on searchable fields, supported syntax, and how fuzzy matching works, go to Global Search.
2026-10-26
We have released the Person-to-Business (P2B) transaction score in Authorized Payment Protection. The P2B score provides real-time risk assessment and fraud detection for commercial transactions, such as:
-
E-commerce checkouts
-
Utility bill payments
-
Gig economy disbursements
With the P2B score, you get the following benefits:
-
Unified Analytics and Reporting: Feed P2B scores and key attributes directly into your analytics pipelines, such as Snowflake, to enable seamless data journaling, monitoring, and reporting alongside existing P2P metrics.
-
Advanced Anomaly Detection: Applies sophisticated, unsupervised risk scoring to commercial payment flows, broadening coverage against complex incoming transaction risks.
-
E-Commerce and Bill Pay Fraud Prevention: Identifies and flags suspicious activity directed at high-risk merchant accounts or synthetic business profiles in real time during checkout and payment processing.
To activate the P2B score feature, contact your Customer Success Manager or Account Manager.
To use the score, you will need to set the destinationRiskScore as true on a request.
destinationRiskScore=true
2026-10-13
We have updated the Case Queue workflow for Authorized Payment Protection. Case Queue now provides a workflow that ends in the resolution of a case.
For more information about Case Queue workflows, go to Manually Review a Case.
2026-10-13
We have added a new Transaction Totals widget to the Authorized Payment Protection dashboard. This widget provides aggregate total volumes, amounts, and currency, with filters for initial guidance, direction, and type.
Parent organizations can also view children totals and have an organization filter.
For more information about adding widgets and customizing your dashboard, go to Customize the Dashboard.
2025-10-13
We have added two new report types to Authorized Payment Protection.
-
Policy Performance Report: A downloadable report that provides key information for regulators. Only available to end-users with the Admin role.
-
Event Details Report: Comprehensive, customizable report that combines transaction summaries, investigation outcomes, and deep-dive event data. Enabling Explore Mode expands the report to include more than 40 filterable columns.
For more information about these reports, go to Authorized Payment Protection Reports.
2026-10-13
We have added a new property to the Branding: Product Names: Authorized Payment Protection Risk API: paymentDirection. This property expands the capabilities of the API across end-to-end bank transfer flows, allowing you to evaluate both incoming and outgoing transactions.
This update also prepares you for upcoming directional velocity features.
The paymentDirection string is for bank account transactions only (excluding credit cards), and contains two possible enumerations:
-
Inbound: Represents incoming transactions relative to theclientId -
Outbound: Represents outgoing transactions relative to theclientId
Here is an example payload:
{
"clientId": "992196953004912",
"paymentDirection": "Inbound"
}