2026-06-30
The Anomaly report is a dedicated analytics view in Analytics that is designed to provide high-visibility insights into suspicious transactional spikes and outliers. Previously, users managing complex organizational structures had to manually switch between accounts to analyze complete data. With this release, automated hierarchy mapping provides a seamless, aggregated view of your fraud risk status.
Benefits:
-
You can now view an aggregated Anomaly report for all child accounts in one centralized dashboard. This makes it easier to identify systemic fraud trends across your entire portfolio without switching accounts.
-
Fraud Analysts in child organizations can only access their specific anomaly data, ensuring a clean, focused, and secure reporting environment.
To access this feature, sign in to Kount 360 and go to Analytics > Folders > Payments Fraud Reports > Anomalies.
2026-06-09
In Case Details, we have updated Decision selection to be dynamic, instead of binary. Before this update, decisioning was limited to two options and could not be changed under certain circumstances.
Dynamic decisioning allows you to manage your order lifecycle by re-evaluating and changing decision statuses—including Approve, Decline, and Review—at any point. Whether using the new drop-down menu or the enhanced Update Order API, your team has the real-time flexibility to correct errors or act on new fraud intelligence instantly.
Key benefits
-
Workflow flexibility: Move orders between any decision state at any time. This allows your team to re-evaluate transactions if new risk signals, such as chargeback spikes, emerge after authorization.
-
API automation: Developers can programmatically trigger manual reviews based on external events, ensuring your automated workflows are as flexible as your manual ones. You can now send a
PATCHrequest with the Update Order API to change the decision status at any time, even if the case was not previously in a Review state.
Before:
After:
2026-06-03
We have added the Explicit Approve policy outcome to Policy Management. This feature lets you create dedicated policies that specifically trigger an approval and supersedes any other policy outcome if evaluated as true. Whether you are managing trusted VIP lists or high-value segments, you now have the direct control to ensure your most important customers move through the checkout process with zero friction.
Refer to Manage Policies for how to build a policy and select an outcome.
Building policies with an Approve outcome:
-
Eliminates ambiguity by replacing implicit logic with clear, intentional approval policies that bypass secondary friction for trusted transactions.
-
Resolves conflict by leveraging a new hierarchy where an Approve outcome acts as the highest priority, automatically resolving rule conflicts in your favor.
-
Improves reporting accuracy by gaining more visibility with a dedicated Approve grouping in your Policies Triggered widget and updated outcome reports. Go to Event Analysis > Order Details > Policies Triggered to see the Approve grouping for an order that has been approved.
Before:
After:
2026-06-08
The Bulk Chargeback Uploader has been updated to support the Order ID (order_id). This enhancement simplifies data reconciliation and improves your workflow.
Previously, the Bulk Chargeback Uploader required merchants to use the Merchant Order ID (merchant_order_id) as the primary unique identifier to process files. The uploader has been expanded to also accept order_id. This provides greater flexibility for merchants who rely on the Order ID as their primary identifier, allowing you to upload chargeback files and update outcomes without performing manual data mapping beforehand.
The process for uploading chargeback files remains the same, but the system now recognizes two distinct header options for the identifier column. When preparing your bulk chargeback files, adhere to the following file formatting rules:
-
Supported headers: Your file must include either
merchant_order_idORorder_idin the header row. -
One identifier per file: The uploader accepts only one type of identifier per file. You cannot mix
merchant_order_idandorder_idwithin the same upload. -
Error handling: If a file contains both headers, or if neither header is present, the system rejects the file and generates a clear error message indicating that mixed or missing identifier columns are not supported.
By using the identifier that best fits your internal processes, you can manage chargebacks more efficiently.
2026-06-03
We have added AND/OR logic to Linked Analysis in Case Queue > Case Details and Event Analysis > Event Details. This toggle feature allows you to switch between AND and OR matching logic to control how your data connects. Whether you need to broaden your search to find related activity or tighten your focus to uncover specific, high-confidence clusters, this feature provides the precise control required for in-depth fraud investigations.
Key benefits
-
Custom investigation: Choose OR logic for broad initial discovery across multiple data points, or switch to AND logic to isolate precise clusters that match every selected data point.
-
Reduce time-to-completion: Reduce manual filtering time by narrowing your results to exact matches. This allows your team to identify and block sophisticated fraud rings faster.
Before:
After:
We have fixed multiple issues this month. Refer to the following list for more information:
-
Added the missing User Attribute in
order.statuspayloads for unassigned agents. -
Added missing Auto-Decision data and Ekata journaling to Snowflake in Queue Manager.
-
Fixed the country code AU mapping error that incorrectly routed to Indian Ocean Territories.
-
Fixed an issue where the Save Layout feature was reverting to the default layout after saving.
-
Fixed an issue where Event Analysis filtering was not finding order older than one year when searching by
transactionId. -
Fixed email tumble logic overriding exact matches and causing erroneous decline of auto-approve orders.
2026-06-24
We have normalized our prevention alert resolutions in Chargeback Management. All alerts, regardless of provider or type, now use the same resolutions in the Kount 360 user interface (UI).
The new resolutions are:
-
Full Refund Issued: A full refund was issued on this transaction or voided the transaction prior to settlement.
-
Remaining Balance Refunded: The remaining balance was refunded. This transaction is now fully refunded.
-
No Refund Issued: Did not issue a refund; allow to advance to a chargeback.
-
Refund Previously Issued: The transaction was refunded prior to receiving the alert.
-
Duplicate Alert: The transaction has already received another alert from the same provider.
-
Already a Chargeback: A chargeback was issued on this transaction prior to receiving the alert.
-
Declined Transaction/Failed Authorization: The transaction was declined; no refund was required.
-
3DS Authentication: This transaction was authenticated by 3D Secure; no refund was required.
-
Not Found: The transaction could not be found in CRM or gateway.
-
Unable to Issue Refund: The refund was declined for this transaction.
For more information about resolving prevention alerts, go to Manage CDRN Alerts and Ethoca Alerts in Chargeback Management.
2026-06-24
We have updated the user interface (UI) for Chargeback Management. These updates help to clarify terminology and improve searchability of alerts.
Removed the search box and added column search filters
Removed the search box on the Prevention Alerts table and added a search filters for individual column filters. Select a a column to display the filter or search options.
New Resolution column
The Outcome and Refunded columns have been combined into a single Resolution column. This new column can be filtered by resolution type, and is viewable in the Completed and All tabs. Go to Chargeback Management Alert Resolutions for a list of all resolution types.
Relabeled columns for clarity
Relabeled several columns for clarity.
-
Partner ID is now Alert ID
-
System is now Provider
-
Order Date, Time is now Transaction Date, Time
-
Created Date, Time is now Issue Date, Time
-
Amount is now Transaction Amount
Added a filter to the Transaction Date, Time column
Added a date filter to the Transaction Date, Time column.
Added a multi-select menu filter to the Payment Type column
Filter options for Payment Type are:
-
Visa
-
MasterCard
-
American Express
-
Discover
Updated column order
Updated the default column order.
Note
The Status column only displays on the Completed and All tabs.
Removed Refunded buttons
Removed the Refunded options for resolutions. The Yes, No, and Not Settled options were removed as part of our resolution normalization.
Moved the Reset Filters and Export Buttons
The Reset Filters and Export buttons have been moved to the top-right of Prevention Alerts.
2026-06-24
We have normalized our prevention alert resolutions in Chargeback Management. All alerts, regardless of provider or type, now use the same resolutions. With this normalization, the request payload has changed. You will need to update your process for submitting alert actions.
The required fields are:
-
id -
statusCode
For complete details about submitting alert actions and a complete list of status codes, go to Respond to Alerts in Chargeback Management.
2026-06-24
We have updated the Chargeback Management user interface (UI) in Kount 360. Duplicate alerts now display with a resolution of Duplicate Alert in the Completed and All tabs of the Prevention Alerts table.
Duplicate alerts are considered non-billable events. For further clarity, we have added an information icon to these table entries. Hovering over this icon displays the Non-billable event message.
This update helps you:
-
View analytics and reporting, enabling you to conduct analysis on duplicate alerts.
-
Reconcile invoices by clearly displaying which alerts are not billed.
2026-06-18
We added a new report called the Policy Management Backtesting Comparison report, located in Analytics. This report displays the results of simulations run on historical data, allowing you to compare your active configuration against a proposed backtest configuration.
-
Original vs. simulated traffic: Compare the original request and the exact segments and policies that triggered against the segments and policies that would have triggered during the backtest.
-
Metadata comparison: Evaluate granular differences, including conditions in each segments, policies, tags, and tag weights.
This mitigates the risk of policy optimization. You can visually map out how a rule change would alter your decline, review, or approval rates before publishing. To find this report, go to Analytics > Report Folders.
2026-06-18
We added a new report, Policy Management Version Snapshot, in Analytics. Every time a new policy set version is published, this report captures a snapshot of your Policy Management set configuration. You can use this report to:
-
Identify exactly who published the changes and when they were published.
-
Review all segments and policies included in the set version, along with their underlying conditions, tags, and tag weights.
This report provides compliance and fraud teams with a record of the exact state of your fraud logic at any specific point in time. To find this report, go to Analytics > Report Folders.
2026-06-12
We have added the option to switch between light and dark mode. The default setting is System. This update is designed to enhance your day-to-day user experience by offering:
-
Visual comfort: Adapt the interface to your current environment, significantly reducing eye strain in low-light conditions.
-
Personalized accessibility: Edit your workspace to meet your individual visual preferences and needs.
You can update your theme at any time using either of the following methods.
Method 1:
Note
Selecting System automatically syncs your user interface with your device's or browser's default appearance settings.
-
Sign in to Kount 360.
-
Select your email, then Theme.
-
Select Dark, Light, or System.
Method 2:
Note
Selecting System automatically syncs your user interface with your device's or browser's default appearance settings.
-
Sign in to Kount 360.
-
Select your email, then My Profile.
-
In Preferences, select Dark, Light, or System.
2026-06-02
We have added the option to duplicate a policy in Policy Management. Policy duplication streamlines the policy creation workflow. Previously, creating a policy similar to an existing one required manually transcribing rules, metadata, and configurations across multiple screens, which was time-consuming and increased the risk of data entry errors. With the new Duplicate action, you can clone existing policies, significantly reducing your time to publish.
Duplicating a policy captures all associated data from the source policy to provide a complete template. This includes: Description, Outcome, Tags, Policy Conditions, and Linked Segments.
To prevent naming conflicts, duplicated policies are automatically named using the format: Copy of [Original Policy Name]. When you select Duplicate, the system generates a unique database record and immediately redirects you to the Edit view of the new policy so you can begin making modifications.
Note
All duplicated policies are created as pending changes. They do not take effect until the version is officially published.
For security and tracking, the creation event is logged in your system journal, recording both the user who initiated the action and the original source policy.
To find this feature, go to Policy Management > Sets > Edit Set > Policies > Quick Actions > Duplicate. Refer to Manage Policies for comprehensive instructions.
2026-06-17
We have added one new column and new filtering options to other columns on the Event Analysis and Case Queue tables.
|
Column |
New filter option |
|
Transaction Type |
Unknown |
|
Event Status |
Unknown |
|
Fraud Type |
Unknown |
|
(New) Assigned Agent |
Unassigned (Case Queue only) |
For more information about Event Analysis and Case Queue filtering, go to Filter and Sort Data Tables.