This release introduces solution-specific navigation to streamline workflows and a newly upgraded reporting dashboard for faster, more intuitive analytics. These updates help your teams work more efficiently, collaborate seamlessly, and access critical insights with ease.

New Solution-Based Navigation

Overview

You can now manage rules, cases, and alerts within the specific context of the FraudNet solutions your company uses, with easy access within the left-hand navigation bar. This streamlines workflows whether it’s for one FraudNet solution used across multiple teams, or one team utilizing multiple solutions. 

What’s New

Solution-Based Navigation
Each team's available solutions now display in the left-hand navigation bar, and only the alerts, cases, and rules associated with that solution and/or team are surfaced, creating a focused and efficient user experience. 

Seamless Cross-Solution Collaboration
You can easily reassign or escalate cases to different teams or departments. All cross-solution handovers are tracked in the audit log, ensuring full transparency and accountability.

Centralized Incidents Tab
All alerts and cases can be accessed via the main incidents tab, offering administrators and other users a single, consolidated view.

Impact

This update enhances operational efficiency by allowing your teams to work within dedicated solution environments tailored to their specific workflows, while also enabling stronger cross-departmental collaboration to  ensure investigations are handled by the right people at the right time.

Upgraded Reporting Dashboard

Overview

FraudNet's reporting and analytics dashboard now runs on Kibana 9.1.2, delivering enhanced security, performance improvements, and a more intuitive user experience. This upgrade provides faster data analysis capabilities and stronger protection for fraud detection and risk management operations.

What's New

Enhanced Interface Design
Navigate through your data more efficiently with a cleaner, modernized interface. The improved dark mode enhances user comfort and visibility, while streamlined navigation helps you access critical insights faster.

Improved Performance & Efficiency
Experience faster search performance and up to 20% log storage savings, for faster analysis even for complex queries.

Advanced Analysis Capabilities
Combine data sources more easily with new query features that maintain result availability even during search timeouts.

Reliability Enhancements
Access reports from all workspace environments without display issues, while policy configurations maintain consistent reliability.

Strengthened Security Foundation
Your data remains protected with comprehensive security patches that address critical vulnerabilities, and default integrations now include enhanced safety measures.

Impact

These upgrades deliver greater operational efficiency, improved data accessibility, and a more intuitive user experience. The update to Kibana 9.1.2 was made automatically, and clients can now utilize the new enhancements with no actions required on your end.

We're excited to announce several key updates designed to enhance security, improve usability, and provide greater clarity in your risk management workflows. This release introduces OAuth 2.0 Authentication for stronger API authentication, and now allows for the direct submission of full PANs into monitoring lists.

Support for OAuth 2.0 Authentication

Overview

You can now use OAuth 2.0 to authenticate API requests, adding a new authorization framework for our clients to apply within their FraudNet implementation. 

What’s New

We have introduced OAuth 2.0 as a new, secure authentication option for the Risk Check API. This update provides a stronger, standards-based approach to integration, ensuring your data remains protected with modern, time-limited tokens instead of static credentials.

Impact

OAuth 2.0 significantly enhances security and control over API access by replacing static credentials with time-limited tokens, reducing the risk of unauthorized access and aligning with industry best practices for secure integration.

Support for Full PANs in Approve/Deny/Watch Lists

Overview

Users can now add full, Primary Account Numbers (PANs) directly into Approve, Deny, and Watch Lists. This enhancement streamlines the process of flagging known fraudulent card numbers, allowing for quicker and more direct action against suspicious activity.

What’s New

The system now accepts raw PANs submitted into the payment_id field. Upon entry, these numbers are encrypted and matched against encrypted payment IDs in transaction payloads. 

Impact

This improves operational efficiency and strengthens your ability to block fraudulent transactions by enabling users to add known fraudulent card numbers into the system. It also ensures seamless and secure data mapping with FraudNet handling the encryption and matching to Payment IDs.  

Overview

You can now leverage Merchant Activity Segmentation, powered by RFM (Recency, Frequency, Monetary) scores, within Policy Monitoring to segment merchants and create more intelligent alerting logic. This enhancement reduces noise from low-impact anomalies and policy violations, ensuring your alerts reflect both statistical significance and business relevance. Refine alert volume, reduce alert fatigue, and increase investigator efficiency with greater trust in the alerts that matter most.

What's New:

Merchant Activity Segments: Merchants are scored daily (0-9 scale) across three key dimensions to provide comprehensive merchant behavioral analysis and segment merchants into data-driven groups.  

• Recency: How recently the merchant has transacted
• Frequency: How often the merchant has transacted 
• Monetary: Total transaction volume
  
  

Segmentation Categories: Utilize eight pre-configured merchant segments (including High Exposure, High Velocity, and Operational Drainers) to better understand your portfolio's risk landscape.

Rule Enhancements & Filters: Apply Merchant Activity Segmentation to optimize rules, and refine and prioritize alerts with new filtering capabilities:

• Segmentation Filters: Scope rules to specific merchant activity segmentation categories for
  targeted monitoring
• Score Filters: Choose from your chosen merchant activity segments directly within rule parameters to define your rules

Impact:

Focus your investigative resources on high-impact alerts with additional merchant behavioral data that provides context for strategic filtering and prioritization. This update enables teams to refine alert volume, improve investigator efficiency, and strengthen confidence in your anomaly detection logic, all aligned with your operational priorities and risk tolerance.

improvement 

Overview

We have enriched the Alert Discover page within Policy Monitoring, adding additional data fields for each alert designed to help clients better understand and act on policy violations and anomalies with precision and ease. This update is part of our continued optimization of the user experience, providing key details at a glance and streamlining the investigation process. 

What’s New

Primary Entity Name
Quickly identify the specific entity connected to the alert to take proactive measures faster.

Transaction Metrics
Easily assess the severity and scope of each alert using transaction count and sum, and use these metrics to filter, sort, and report on alerts to better prioritize and streamline investigations. These transaction metrics are also available via the Alert API.

• Transaction Count: Number of transactions that triggered an alert
• Transaction Sum: Total monetary impact of those transactions

Alert Dropdown Details
See a snapshot into why an alert was triggered with these added metrics:

• Rule Threshold: The defined policy limit
• Value: The recorded value that triggered the alert
• Difference (%): The percentage deviation from the threshold to help you understand the magnitude of the violation or anomaly

Impact

This update empowers clients to act faster on violations and anomalies with critical details available at quick glance, providing important context up front to better prioritize alerts and investigations, and make informed decisions faster.

Bug Fixes in This Release
fix 

Overview

As part of standard maintenance to ensure a reliable, performant system, the following bug fixes have been made:

1. Update API now supports the following three scenarios:

• To update a value, include the field with the new value.
• To clear a value, send it as an empty string (fraud_type: "").
• To leave a field unchanged, simply omit it from the payload.

2. Custom Field now displaying properly on transaction detail page

improvement 

TSYS File Integration & Batch Processing

Overview 

We’re excited to introduce key updates to our batch processing system in order to support TSYS-standard file formats. TSYS, a leading provider of payment solutions and services globally, plays a critical role in the payments industry. With this release, FraudNet can now ingest and batch process TSYS files, streamlining operations and data flow for organizations using TSYS within their core payments infrastructure.

What’s New

The new addition of TSYS file integration and batch processing provides faster, more reliable data ingestion with real-time triggered uploads, accurate file handling, and robust error management. Our framework also incorporates TSYS Object Mapper Support, guaranteeing accurate parsing, mapping, and processing of data, regardless of variations in the TSYS schema. 

Impact

TSYS files now flow through an automated batch-processing pipeline, reducing manual intervention and the risk of errors. These new capabilities make it easier for TSYS clients to integrate their data with FraudNet, streamlining onboarding and ensuring scalable fraud detection with a reliable, timely flow of data.

New Enhancements to Entity Screening Alerts

Overview

Our Entity Screening capabilities have been expanded to significantly improve investigative workflows and risk management.

This most recent update focuses on improving the productivity and efficiency of investigations by transforming detected matches into actionable and structured alerts, and bringing greater visibility, context, and workflow structure to the screening process.

What's New

Alerts in the Screening Tab

Detected matches from sanctions lists, adverse media, or other sources are automatically converted into clearly defined alerts within the Screening tab.

Dedicated Alert Detail Page

Investigators can now access a comprehensive detail page for each alert, featuring provider-specific data points such as article text, data sources, and direct links to sanctions or media entries. 

Improved Workflows & Automations

• Clearly marked escalation paths enable users to easily withdraw false positives or escalate cases for further investigation, greatly improving decision-making and ensuring auditability,
• To support greater efficiency and focus investigations on high priority items, alerts are automatically created when a potential match to a sanctions list or adverse media is detected, such as a name appearing in negative news or on a government watchlist.

Impact

This release further simplifies reviews by adding enriched contextual data to alerts, reducing manual work and improving accuracy. Clear escalation workflows enable faster resolution and audit-friendly documentation, helping teams address risks more efficiently and confidently.

Enhanced Cardholder Name Logic – Now Aligned with Industry Standards 🌍

Feature Summary

We’ve updated our cardholder name logic to better align with global industry standards. This enhancement enables support for single-field name inputs, streamlining integration with payment processors that use unified name formats.

Why It Matters

Historically, our rules required both first_name and last_name fields to function. However, many payment processors - especially those operating globally - receive cardholder names as a single string (e.g., “Maria del Carmen Ruiz”) in the first_name field alone. This update modernizes our system to meet that reality.

The Result

Cardholder name-based rules now work seamlessly across naming conventions, reducing manual overhead and enabling faster, more reliable rule setup for globally distributed data formats.

This is part of our ongoing commitment to support modern payment practices and global compliance needs.

We’re excited to announce the launch of the Entity Ensemble Score for Entity Screening, a powerful new capability designed to deliver a unified, holistic view of risk at the entity level.

What’s New

The Entity Ensemble Score consolidates multiple solution-specific risk assessments into a single, actionable score - empowering users to make faster, more informed decisions.

Each entity now features:

• Individual Product Risk Scores: A detailed breakdown of risk per product the entity interacts with (e.g., Entity Screening, Policy Monitoring).
• Overall Ensemble Score: A comprehensive risk score that combines all product-specific scores using a weighted ensemble model, offering a full-spectrum view of entity-level risk.

Phase 1 Rollout: This initial release is live for Entity Screening!

Where to Find It

You’ll see the new Entity Ensemble Score displayed prominently in the Entity Overview Card, along with any available component product scores.

Stay tuned for future phases as we expand this capability across additional products!

These updates mark our continued commitment to delivering smarter, more scalable risk and compliance solutions for a global ecosystem 🚀

We’re excited to unveil powerful new capabilities for Entity Screening, including fully integrated rule sets, rules and a dedicated Screening Tab to enhance how Sanctions, Adverse Media, and PEP checks are managed and actioned. These updates streamline screening logic, automate actions, and provide a more transparent, intuitive user experience.

Rule Sets: Define What, Who, and When

Rule Sets allow users to organize and schedule the screening logic:

• What is run: Select the enrichment sources by provider and configuration 

• When it is run: Choose from flexible scheduling intervals:

  • Daily
  • Weekly
  • Monthly
  • Annually
  • Or when the merchant is first created
  • Against whom: Use Entity API filters to run different configurations for specific segments (e.g., countries)

This framework enables precise and scalable control over screening operations solving for initial and ongoing screenings.

Rules: Define What to Do When Results Are Found

Rules let users configure automated actions to take when an entity matches results from a selected enrichment source. Available actions include:

• Create an Alert
• Create a Case
• Change the Screening Status
• Update the Entity Status
• Apply Weight to the Screening Score

This allows teams to automate response workflows and reduce manual intervention, enabling faster and more consistent decision-making.

Screening Tab for Entity Screening

Overview

We are excited to announce the release of the Screening Tab within the Entity Screening product. This marks a significant improvement in how screening data is displayed, understood, and actioned for entities. Users can now navigate to the new Screening tab when viewing a merchant to access a structured, transparent view of all screening incidents and outcomes.

Key Enhancements

Centralized Screening Insights

All screening alerts and cases - past and present - are now available in one consolidated location, organized by the type of screening performed, such as sanctions or adverse media.

For each category, users can:

• View the full history of alerts and cases generated.
• See the last run date for each screening type.

Alert and Case Lifecycle Management

Each alert provides direct access to critical functionality:

• Drill into the alert for deeper context and data.
• Withdraw, escalate to a case, or resolve a case as a true or false positive.
• Visualize both open and closed incidents tied to that entity.

Improved Usability Over Beta Version

The new experience significantly improves on the prior beta version:

• Eliminates confusing columns (such as ambiguous "outcome" labels).
• Introduces the clear concept of screening alerts - making it easier to triage and take action.
• Ensures decisions are made only after reviewing full match details, unlike the beta which allowed blind pass/fail decisions.

By organizing data by screening type and showing a complete decision and results history, this version provides a more intuitive and actionable workflow for compliance and risk teams.

This release lays the foundation for transparent end to end screening operations. Stay tuned for more enhancements as we continue to evolve the platform to meet your growing compliance needs. 🔍⚙️

We are excited to announce the addition of key data fields to the alert index and case index, designed to enhance analytics capabilities and meet growing reporting requirements. These updates include the following fields:

• Merchant Category Code (MCC)
• Region
• Country
• Entity Name
• Entity ID
• Entity Group ID
• Entity Group Name

Key Benefits:

• Enhanced Filtering Options: Alerts can now be filtered by Merchant Country, a critical capability for audit and reporting processes. This feature supports payment processors who manage portfolios across regions such as the EU, UK, and North America.  
• Improved Analytics: Including MCC and Country at the alert level allows for deeper insights and better decision-making when analyzing transaction or case data.

These enhancements provide users with more precise control and clarity over their data, ensuring improved operational efficiency and compliance. Start leveraging these fields today to elevate your analytics and alert management!

We’re excited to introduce a new fraud detection rule designed to identify coordinated transaction patterns involving BINs, IPs, and card usage. This rule enhances our ability to detect and prevent fraud schemes such as card testing, account takeovers, and money laundering.

🔍 What the Rule Does

This rule tracks the number of transactions associated with:

• A single IP address
• Multiple cards sharing the same BIN
• Transactions that exceed a defined amount threshold
• Within a specified timeframe

📌 Trigger Example

The rule will trigger if the following conditions are met:

• Transactions originate from a single IP address
• Involve 5 different cards sharing the same BIN
• A total of 10 or more transactions occur
• Each transaction exceeds 100 EUR
• Transactions happen within a 1 day

🎯 Objectives