2026-03-18
We have updated the user interface for Chargeback Management in Kount 360. These changes were made to improve the workflow when resolving Verifi and Ethoca alerts.
The following changes have been made to Alerts:
-
Alerts is now Prevention Alerts.
-
The Prevention Alerts table now has three tabs: Unresolved, Completed, and All.
-
The Cancel and Dismiss buttons have been removed. Cancel was removed due to the ability to unselect alerts, and Dismiss is no longer necessary as actioned alerts now display on the Completed tab.
-
The Dismiss filter has been removed from the Filter options.
-
When a filter is applied to a column in the table, a counter displays the number of cases that filter applies to.
Unresolved, Completed, and All Tab Details
-
When you navigate to the Prevention Alerts table, the Unresolved tab is selected by default. This is the primary location to action alerts.
-
The Completed tab displays any alert with a Completed status. You cannot action any alerts on this tab. Alerts that still require action display on the Unresolved tab.
-
The All tab displays both Unresolved and Completed alerts. You can only action Unresolved alerts on this tab.
New Columns Details
The following columns were added to the Prevention Alerts table for enhanced clarity and detail:
-
BIN: The Bank Identification Number.
-
Last 4: The last four digits of the card number.
-
Reason Code Description: A text description that defines what the reason code means.
-
Payment Type: The card type, such as VISA or Mastercard (this column was previously Card Brand).
Previous Alerts Page
New Prevention Alerts Page
For more information on resolving alerts, go to Manage CDRN Verifi and Ethoca Alerts in Chargeback Management.
2026-03-20
We have added the ability to create custom event (transfer) types as an option to Authorized Payment Protection. This enables you to use an existing API attribute to customize the name of your transfer type.
There is no change to the API. To add a custom event type, add your event type in the eventTypeName API field.
You can view your event type in Event Details > Transaction Summary > Event Type. This update includes a new policy condition, APP Customer Event Type Name, and a new Event Type Name filter for dashboards and reports.
2026-03-20
We have added new policy conditions for Authorized Payment Protection. For a complete list of policy conditions for Authorized Payment Protection, go to Authorized Payment Protection Policy Conditions.
|
Category |
Condition |
Description |
|
List Type |
IP Addresses |
The IPv4 address of the device. If unavailable, the IP address sent in the request payload. |
|
List Type |
Device ID |
The unique identifier of the device. |
|
List Type |
Destination Account Key List |
Destination Account Key as sent in the request payload that will be evaluated against Destination Accounts. |
|
Velocity |
Approved Transactions by Destination Account Key |
Counts approved transactions by Destination Account Key (paymentKey). |
|
Velocity |
Total Approved Payment Transfer Amount by Destination Account Key |
Total approved payment transfer amount for transactions by Destination Account Key (paymentKey). |
|
Transaction |
APP Customer Event Type Name |
The specific name of the event type, as entered by the customer. For example, Withdrawl or P2P. |
2026-03-17
We have introduced stricter validation and state-handling rules to Authorized Payment Protection. Certain combinations of states that were incorrect (but allowed) are now rejected. This update is related to the new Labeling options in the Kount 360 UI.
Due to these changes, an HTTP 400 error response displays when API integrations send an incorrect combination. In the Kount 360 user interface, a Failed to Update Event error message displays after selecting Submit.
Examples:
-
You cannot combine a Fraud Type with the Not Fraud outcome.
-
You cannot submit a Fraud Type with no Fraud Outcome.
-
You cannot submit a bankEventId with an eventId that is not associated with the same transaction.
2026-03-17
We have added labeling for the Authorized Payments Protection user interface (UI) in Kount 360. Labels allow you to improve the handling of operational statuses, investigative outcomes, and fraud subtypes. We have also included a remove option for these values. The values in the UI adhere to the same rules as the API, and changes in one are reflected in the other.
These changes coincide with stricter validation and state-handling rules.
Labeling
You can now update the following values in Event Details:
-
Event Status
-
Investigation Outcome
-
Fraud Type
These updated values can be viewed in Event History, Case Details, and Event Analysis.
You can also view the following important information in the new Transaction Summary.
-
Event Type
-
Amount
-
Direction
-
Transaction Type
-
Event Timestamps
-
Bank Event ID
-
Event Id
Remove option
The remove option requires you to select the x in the field next to the label you want to remove. This removal option allows an analyst to correct the data without forcing an incorrect label.
Selecting the remove option
Event Details after a label is removed
Effective: 2026-03-09
We have released a major update to our flagship fraud detection tool, Omniscore. By retraining the Omniscore model, we have implemented critical infrastructure upgrades and improved data modeling to provide you with unprecedented fraud capture rates and industry-leading stability.
What’s new?
-
New email risk engine: We have replaced legacy email insights with an enhanced email risk signal. This service utilizes broader network traffic to provide a higher-fidelity "Payments Fraud email signal," resulting in significantly better fraud detection.
-
Native platform intelligence: As more customers migrate to Kount 360, our model now leverages a larger pool of native transaction data. This transition reduces reliance on legacy bridge data and allows the model to learn from the unique behaviors of your specific customer base.
-
Advanced signal processing: The new model employs a refined "Curated Training Set" that excludes low-signal noise while aggressively targeting high-signal fraud claims and chargebacks.
Observed performance impact
-
73% overall improvement in general fraud capture
-
593% improvement in chargeback detection
-
Passed all rigorous stability tests, providing consistent scoring through peak and off-peak cycles