Release Notes: November 2025

Effective: 2025-11-21

We have added an Authorization Status column to the data tables in Case Queue, Event Analysis, and Linked Analysis in Order/Case Details. The value populated is collected from the API request for paymentAuthorizationStatus.

The value provided in the column can be one of the following:

Effective: 2025-11-21

We have released new policy conditions for Payments Fraud. These conditions provide you with more ways to create policy sets for different use cases.

Go to Kount 360 Conditions to view the complete list of current policy conditions.

Order category

Email Address category

Velocities category

Effective: 2025-11-20 

The Email Insights service in Kount 360 has been updated to utilize a new, more comprehensive dataset and is now called the Email Verification service. This update provides more accurate email data by including all native Payments Fraud orders, which were not part of the legacy Email Insights service.

To implement this new service, you must:

For more information about the Email Verification service and the deprecated and updated conditions, go to Email Verification Service in Kount 360.

Effective: 2025-11-17

We have updated Case Queue to improve the user experience and speed-up batch actions and queue management. Previously, the checkbox and Assignee columns were coupled, preventing the user from configuring the Assignee column.

Effective: 2025-11-17

We have added the ability to unassign cases from an agent.

Users can unassign a case that was assigned to them or another agent in Case Queue. The unassigned case is returned to the general queue and can be reassigned.

To unassign a case:

Effective: 2025-11-11

In Case Management > Queue Manager > Ekata Service, we added the option to enable Ekata to inform automated or manual review decisions. You can set up conditions to run before calling Ekata service to minimize how often the service is called.

Ekata conditions used in Policy Management and Queue Manager do not run if Ekata is disabled. You do not need to remove these conditions. When Ekata is enabled, the conditions run.

Refer to Ekata Service in Kount 360, for more information about the Ekata Service in Kount 360.

Effective: 2025-11-07

We added the ability to change your base currency in Payments Fraud to assist financial analysis by automatically converting all transactions to a single, user-defined currency. Base currency is visible across all Payments Fraud reports. This update eliminates manual conversions from one currency to another and reduces overall manual effort and conversion errors.

Other changes with this update:

Base currency is set during the creation of your organization, but you can request an update if your business needs have changed. Contact support@kount.com to learn more about changing your base currency.

Effective: 2025-11-05

We have added the Auto Decision action to Case Management > Queue Manager > Triggers. With Auto Decision, you can create conditions to evaluate an automatic decision of Approve or Decline on all orders held for review. The Auto Decision action can help you:

Effective: 2025-11-03

We added new properties to the webhook API payload. The new properties are associated with the user or system agent that made an update to an order. You can use these properties in workflows for auditing purposes. Refer to Implementing a Webhook Notification for more information.

The new properties are:

{
  "id": "f276e154-23ef-4366-933b-e1f12e159901",
  "eventType": "OrderUpdate",
  "apiVersion": "1",
  "clientId": "900900900900900",
  "orderId": "8V6CFF359HS5QQ6G",
  "channel": "MOBILE",
  "merchantOrderId": "qjlm9gvol6olejcs",
  "orderCreationDate": "2022-05-24T23:13:02Z",
  "eventDate": "2022-05-24T23:18:00Z",
  "agent": {
    "name": "Jane Doe",
    "emailAddress": "jane.doe@example.com",
    "id": "d121ea2210434ffc8a90daff9cc97e76"
  },
  "tags": [
    "risky_device",
    "unverified_location",
    "device_outsideUS"
  ],
  "tagWeights": [
    {
      "name": "risky_device",
      "weight": 110
    },
    {
      "name": "unverified_location",
      "weight": 10
    }
  ],
  "fields": [
    {
      "name": "order.decision",
      "oldValue": "REVIEW",
      "newValue": "DECLINE"
    },
    {
      "name": "order.chargeback.isChargeback",
      "oldValue": "false",
      "newValue": "true"
    },
    {
      "name": "order.chargeback.chargebackReasonCode",
      "oldValue": null,
      "newValue": "10.2"
    },
    {
      "name": "order.transaction[\"d121ea2210434ffc8a90daff9cc97e76\"].authorizationStatus.authResult",
      "oldValue": null,
      "newValue": "10.2"
    },
    {
      "name": "order.fulfillments[\"d121ea2210434ffc8a90daff9cc97e76\"].status",
      "oldValue": "SCHEDULED",
      "newValue": "FULFILLED"
    }
  ]
}

Effective: 2025-11-06

We updated the Web Client SDK to 2.2.3. In this update, we improved our library for accessibility. Developer tools, like Lighthouse, no longer flag the Device Data Collector during audits. This minor update does not change any functionality or features. Use the latest Web Client SDK to ensure the best development compatibility.

Refer to Checksums on our Developer website for updated GitHub and NPM hashes.