Payments Fraud

Customer implementation choices or customer business practices can lead to transactions erroneously link...

This guide explains Omniscore—a comprehensive safety rating designed to help you distinguish between leg...

Reason codes are created and assigned to orders in Kount 360 Payments Fraud to help users search, filter...

Orders that require agent attention are identified as Cases in Kount 360 and are located in Case Manag...

The Persona service is a Graph Clustering Engine that builds clusters of connected transaction data. The...

Since Omniscore is so accurate in predicting fraud, you can set one rule around it instead of creating a...

View or export reports for sensitive account event details, such as list changes and user changes. Vi...

On the Order Details page, you can view the breakdown of an order's Omniscore to help you assign a decis...

Payments Fraud gives you the ability to add chargeback and refund data to prevent fraud. You can add cha...

The Queue Manager allows you to create and manage case workflow and queue policies. As an admin, the Que...

sidebar. Within the Queue Manager, you can create triggers. Triggers are event-based rules created ...

The following list contains all of the policy conditions for Payments Fraud. Select a category from...

Linked Analysis lets you compare relationships between different datasets (for example, billing email, I...

In Details, you can add order values to existing lists without leaving the page. To add an order value t...

After creating and defining your own custom fields, you can add, filter, and sort them in Event Analysis...

List automation integrates a new automated action into Policy Management. It lets you configure policies...