Release Notes: January 2026

Effective: 2026-01-27

We have refreshed the Account Creation Score model to improve overall accuracy.

This update does not affect your score distribution, and no action is required from you to implement this update. If you experience any issues or have questions, please email us at support@kount.com or reach out to your Customer Success Manager.

Effective: 2026-01-27

The accountCreationSafetyAssessment object has been added to the New Account Opening (NAO) API response. This update provides more transparency by including a numerical Safety Assessment, ranging from 0.1 (unsafe) to 99.9 (safe), alongside the specific risk factors that influenced the score.

Before this update, the NAO API response only provided policy-based decision. Now, you can use the Account Creation Score and the Safety Assessment to make more informed decisions.

"accountCreationSafetyAssessment": {
    "safetyScore": 88.5,
    "reasonCodes": [
      "ACS01",
      "ACS07"
    ]

Refer to the New Account Opening API help documentation for more details.

Effective: 2026-01-29

When an address was added with the Add to List feature, Line 2 of the address was duplicated. This caused decline lists to not fire on the addresses containing the duplication because it was no longer an exact match. This issue has been resolved and the Add to List feature now works as intended.

Effective: 2026-01-21

Under specific conditions, the Auto Decision feature failed to apply an Approve action to certain orders. The conditions were:

This issue has been resolved and now the auto decision applies an Approve decision as intended.

Effective: 2026-01-26

The following issues have been resolved with filtering in the Case Queue:

Effective: 2026-01-15 

We are enhancing your policy creation process with the ability to test new or existing sets against your historical order data. This early preview “beta” allows you to test against 30,000 historic orders per month. In April, the beta period will end and the full feature becomes available. The enhanced full feature will enable you to test against higher volumes of orders, exceeding the previous limit of 30,000.

When testing sets against historical order data, the system compares the new outcome generated by the selected rule set against the original historical outcome and then quantifies the difference. This helps you identify different iterations of your sets that outperforms the others before enabling them live.

Go to Policy Management > Testing to find the new feature:

To maintain an accurate "what-if" scenario based on the historical context, the system uses the same information gathered from the device, email, and Geolocation used at the time of the original transaction.

To start testing against your complimentary 30,000 orders, refer to Testing in Policy Management. If you encounter any bugs (common in betas) and a job fails to complete, rerun the job. This commonly resolves the issue. If an issue persists, or if you decide that you would like to extend your ability to test against more than the courtesy 30,000 orders, reach out to support@kount.com or your Customer Success Manager.

Effective: 2026-01-14

We have added the option to create custom roles in Kount 360.

The Custom Roles feature allows Organization Owners to create tailored roles with specific permissions that align with their organization's unique workflows. While Kount 360 provides a set of default roles, Custom Roles offer granular control, allowing you to combine permissions from multiple solutions or entitlements into a single user profile.

Refer to Creating and Managing Custom Roles in Kount 360 for more information.

Effective: 2026-01-14 

We have added a new cross-org reporting feature to Kount 360 Payments Fraud. The new feature is available in Analytics > Reports.

Cross-org reporting lets you load data for one or more customer organizations into the reporting view. The partners now can run reports on their customers' data, both individually and as an aggregate of the whole, or as subsets of their customers. When partners have visibility into the data of other organizations, such as child and partner organizations, they can build and run reports against any and all of the data available to them. In turn, the partner can solve problems that span the entirety of that organization’s responsibilities and might be visible only to certain organizations.

For more information about cross-org reporting, go to View Cross-Org Reports for Partners.