Effective: 2026-04-29
We have updated how tags are managed in Kount 360.
New user interface
Managing tags in Policy Management has been improved with a refreshed user interface. The new user interface includes a toggle switch to hide inactive tags and new columns (Active Usage Count and Quick Actions) in the tags table.
The Quick Actions column includes View References and Archive Tag
.
Viewing tag references
You can view additional tag details such as Event Type, Active Set, or Current Version. This view also has a link to the segment or policy that the tag is used in for quick reference.
Archiving and restoring tags
You can now archive tags that are not being used in any policies or segments. This lets you remove an old tag and create a new one to fix naming conventions or revise typos. After a tag is archived, it can be restored by going through the create a new tag process and inputting the case sensitive name of the archived tag.
Refer to Tags in Kount 360 for detailed instructions.
Case sensitivity for tag names
Tags are now case sensitive. This gives you more control over how you manage tag names.
Active usage count
The Active Usage Count column has been added to the tags table, which consolidates and replaces the previous two columns: # of Active Policies Assigned to and # of Active Segments Assigned to. This value displays the number of policies or segments that each tag is assigned to.
Effective: 2026-04-13
You can now assign reason codes with a policy in Policy Management. When creating or editing a policy, you can select which reason code you want to add to the policy outcome. When the policy is triggered for an order, the reason is assigned. When multiple policies trigger, our system automatically selects the highest-priority code based on your custom-ordered ranking for consistent decisioning. This automation triggers specific workflows or manual reviews by delivering the most critical reason code directly in the POST /orders response.
For instructions on using this feature, go to Reason Codes in Kount 360.
Effective: 2026-04-13
Kount 360 Policy Management now supports auto-add to lists. This enhancement allows you to configure policies that automatically populate specific lists upon a policy trigger, directly linking detection to automated list management. Auto-add to lists eliminates repetitive manual data entry for list maintenance, reducing analyst overhead and freeing resources for complex investigations.
These new capabilities are integrated directly into your existing workspace. To find this feature:
-
Go to Policy Management and edit or create a new Policy Set.
-
Edit or create a new policy.
-
Select the Lists tab to add list additions that you want to automate on real-time transaction screening.
For comprehensive instructions on how to use the auto-add to lists feature, refer to Auto-Add Order Values to Lists in Policy Management.
Effective: 2026-04-13
The new Automations feature in Product Configuration allows Admins to create self-executing workflows that instantly close the gap between risk detection and prevention. By setting triggers for chargebacks, refunds, or fraud codes, you can automatically route high-risk attributes—like emails and device IDs—directly to your blocklists.
With automations you can:
-
Eliminate manual bottlenecks by replacing tedious, transaction-level data collection with instant, programmatic list updates, freeing your fraud team to focus on high-level strategy rather than data entry.
-
Prevent "hit-and-run" fraud by blocking compromised data points the second a chargeback is reported, drastically reducing the time fraudsters have to place additional unprotected orders.
To access this feature:
Note
Even when a value is added with automation, Fraud Analysts can still manually override or remove entries directly from the Order Details page to correct false positives.
-
Go to Admin > Product Configuration > Payments Fraud > Automations.
-
Select Create Automation to add trigger details that respond to post-authorization events like refunds and chargebacks.
For detailed instructions, go to Automations in Product Configuration.
Effective: 2026-04-13
We have added the ability to instantly track the number of unique values—such as loyalty IDs or email addresses—within a single Persona cluster. By identifying abnormal diversity in custom data, the customer can pinpoint even more sophisticated fraud patterns.
-
Detect advanced fraud patterns by identifying high-risk behavior, like a single Persona rotating through dozens of different loyalty numbers or accounts, by setting automated thresholds on unique custom field count.
-
Maximize Persona intelligence by transforming raw custom data into actionable, case-insensitive insights that drive faster and more accurate good-versus-bad actor decisions.
Effective: 2026-04-13
Eliminate manual cross-referencing in favor of automated precision. Riskiest Country is now integrated directly into the Compare String Variables condition, which allows customers to instantly match high-risk network data against order locations. This update increases efficiency for power users by ensuring that they can identify geographical discrepancies and stop sophisticated fraud attempts without interrupting their workflow.
-
Maintain essential feature parity for legacy users and partners, ensuring that existing, proven fraud-prevention strategies remain uninterrupted and effective during migration.
-
Automatically flag high-risk anomalies by comparing the Equifax Network’s riskiest identified country against customer-provided locations to catch deceptive shipping or billing tactics.
Effective: 2026-04-13
Implement a new level of precision with a new release that allows a customer to compare Custom Field values (String, Number, or Date) directly against curated lists. Whether the customer is blacklisting risky email recipients or whitelisting trusted accounts, this powerful update gives them the flexibility to turn any unique data point into a decisive action.
-
Utilize unique business data—like gift certificate recipients or specialized user IDs—to create highly specific blacklists or whitelists that generic tools miss.
-
Customers can bridge the gap from legacy systems, ensuring that existing Command workflows transition into Payments Fraud without losing critical logic.
Effective: 2026-04-13
We have added new columns to the Event Analysis, Case Queues, and Link Analysis tables. By centralizing this data, we have eliminated information gaps and provided the visibility needed to manage complex fraud patterns.
Note
Some values appear in specific tables or have not yet been added to all the tables. Refer to the Available in column in the reference table below.
Refer to the following list of added columns:
The new columns help you:
-
Access transaction attributes in your primary workspace, which enables faster, more accurate risk assessments without the need for manual data comparisons.
-
Identify fraud patterns with expanded visibility across tables. This allows investigators to surface subtle correlations and sophisticated fraud rings that were previously hidden behind limited data views.
Effective: 2026-04-06
The Email Address policy condition in the List Type category was constructed in a way that caused confusion. We cleared up the issue by having the Email Address populate true if either the billing address or the shipping address is in the list.
Effective: 2026-03-17
The system was unintentionally calling the Ekata Queue Manager Service when it should not. The order was incorrectly auto-decisioned instead of being routed for mandatory agent review. We updated the system so that the Contains function operates correctly and leaves the request in review.
Effective: 2026-03-24
After a platform-wide audit, we implemented an update that improves the case sensitivity consistency throughout Payments Fraud. We made changes so that the case sensitivity is more consistent, with more intentional reasoning for cases in which we need to deviate.
Effective: 2026-03-24
The Link Analysis gadget would not dynamically update or enable linking for fields updated with the PATCH API. This caused a disparity between the user interface (UI) and the database. We updated the system so that the refresh function now displays the correct order matches.
Effective: 2026-02-05
During testing, customers expected a No value for Address Deliverable field when they used an invalid address. Instead, a value of -- displayed. We have updated the system to display the expected No value when an invalid address is supplied.
Effective: 2026-04-01
When customers submitted orders with the payment type Klarna, they were unable to create or edit policies based on that payment method. We updated the system so that Klarna now appears in the Payment Type condition drop-down menu in Policy Management.
Effective: 2026-04-09
We implemented an update that improves country code matching and ZIP code detection. The Data Quality Service now recognizes the ZIP+4 format as a unique identifier for the United States. Before this update, only the ZIP+4 data without identifying the country was returned. Now the service automatically identifies and assigns the US country code.
2026-04-20
We have added new columns to the Prevention Alerts table in Chargeback Management. Both of these columns provide information for alert expiration.
Verifi CDRN alerts expire in 72-hours and Ethoca alerts expire in 24-hours. For more information about resolving alerts, go to Manage Verifi CDRN and Ethoca Alerts in Chargeback Management.
-
Expiration Countdown: Displays in the Unresolved tab and displays the time remaining until an alert expires. When an alert is resolved or expires, it moves to the Completed tab.
-
Expiration Date, Time: Displays the date and time that the alert will expire.
2026-04-06
We have added a Visa Acquirer Monitoring Program (VAMP) Calculator to Chargeback Management. The VAMP calculator provides you with an easy way to check your estimated VAMP ratio and make sure that you are in compliance.
The view and functionality of the calculator changes if you are or are not enrolled in the Verifi Inform service.
-
Enrolled in Verifi Inform: Fields are automatically populated with dispute data from your Inform file. You only need to enter the total Visa transactions for the selected month.
-
Not enrolled in Verifi Inform: Fields for dispute information display. You must manually enter your dispute and transaction data for the selected month.
For more information about VAMP, go to What is the Visa Acquirer Monitoring Program?. For instructions about using the VAMP calculator, go to Visa Acquirer Monitoring Program Calculator.
2026-04-16
We have released a new version, 5.0.1, of the Device Data Collector Android SDK. The following dependencies have been added or changed:
-
Updated to compileSdk 36
-
Added appcompat 1.71 dependency
-
Updated to material 1.13.0
-
Updated to gson 2.12.1
-
Removed multidex support.
For detailed Android SDK integration steps, go to the Device homepage.