August brought new investigation and rules capabilities along with improvements to the merchant experience and a round of fixes.

Alert and case creation from Transaction Monitoring rules. Transaction Monitoring rules can now create an alert or a case as its action, turning a risky event into a tracked, assignable investigation instead of an item sitting in a review queue. This feature is available for clients using Solutions within Merchant Monitoring or Customer Risk Monitoring.

This gives you the audit trail, grouping, ownership, and reporting you need for oversight, and lets investigators review all of a customer's alerts together rather than working transaction by transaction. The existing action group (Approve, Cancel, Queue, Monitor) and the new Case Management action group can each be set independently, or set to None, so a rule is only ever assigned the actions it needs. 

Your data is protected under PCI DSS Level 1, the highest standard in payment security, validated through our most recent annual assessment. Trust Center | FraudNet 

• Opening an already assigned case no longer automatically assigns it to you.
• Resolved SSO errors that prevented invited users from setting a password and logging in.
• Fixed missing Entity Names and MCC on specific alerts.

July brings major updates across two of our solutions, Merchant Risk Monitoring and Customer Risk Monitoring, expanding the data and tools available for building risk strategies.

Merchant Risk Monitoring: Merchant Detail Files

FraudNet can now ingest Merchant Detail file feeds as part of the Merchant Risk Monitoring solution, bringing in non-transaction merchant data from client-supplied file feeds. This can add valuable context for setting targets and thresholds, refining rules, and supporting investigations.

---

Customer Risk Monitoring now Available for Banking

We're excited to announce that we've expanded our fraud and risk solutions for Banking with the launch of Customer Risk Monitoring solution for early access, giving organizations the ability to continuously monitor customer activity and flag potential risk based on configurable policies.

As part of this release, clients using Customer Risk Monitoring solution also get access to the Alert & Case Manager experience, providing a unified and intuitive workspace for reviewing alerts, managing investigations, and viewing customer information.

What's Included

1. Customer Risk Monitoring for Banking: Continuously monitor Customer Entity activity and generate alerts when configured policies are triggered.
2. Customer Entities: Create and manage Customer Entities, providing a centralized view of customer information and investigation history.
3. Targets & Thresholds for Customer Entities: Configure metrics and thresholds for Customer Entities to detect unusual behavior and generate alerts when defined conditions are met.
4. Investigation Pages: The Alert Detail, Case Detail, and Entity Detail pages are now available, providing Banking clients with a unified experience to review alerts, manage investigations, and view customer information in one place.

Why This Matters

With support for Customer Entities, Targets & Thresholds, and the Alert & Case Manager investigation experience, clients can now build customer-centric monitoring strategies that proactively identify potential risk.

These capabilities provide greater flexibility to define business-specific monitoring policies while giving investigators the context and tools they need to review alerts and manage cases efficiently from a unified workspace.

This release marks another step in expanding our Customer Risk Monitoring capabilities for Banking clients, with additional enhancements planned for future releases.

Over the coming weeks, we'll be rolling out a series of user experience enhancements to the Alert & Case Manager for our Merchant Risk Monitoring solution. These improvements are the result of extensive user research and feedback from investigators and operations teams, helping us streamline common workflows and make key information easier to find at a glance.

Our goal is simple: reduce clicks, improve visibility of important information, and create a more intuitive investigation experience so your teams can work faster and with greater confidence.

Rolling Out This Week: 

Alert Detail Page

• Create Case and Withdraw actions are moving to the right-hand side of the page, placing primary actions in a more consistent and accessible location for faster decision-making.
• Alert Status is moving to the top-right corner, making the current state of an alert immediately visible without requiring users to scan the page.
• Alert, Case, and Entity names will now appear as page titles, improving context and making navigation between records clearer.
• Page structure improvements deliver a cleaner, more consistent layout, making it easier to locate critical information and reducing cognitive load during investigations.

Entity Detail Page

• Entity Status is moving to the right-hand side of the page, aligning with the updated design patterns across Alert & Case Manager and making status information quicker to identify.

Case Detail Page:

 Why We're Making These Changes

These enhancements are informed by user research and direct customer feedback. We observed how teams navigate investigations day-to-day and identified opportunities to improve efficiency by:

• Making important actions and statuses easier to find.
• Creating a more consistent experience across Alerts, Cases, and Entities.
• Reducing visual clutter so investigators can focus on the information that matters most.
• Supporting faster workflows with a more intuitive page layout.

This is just the beginning. We'll continue to introduce thoughtful usability improvements over the coming weeks as part of our ongoing investment in making Alert & Case Manager faster, simpler, and more effective for investigation teams.

Something big is coming. New FraudNet solutions are in the works, and we can't wait to share more next month. Here's what rolled out in June while we put the finishing touches on our next major releases.

Improvements

• User's count of Seller IDs (including current). A new Transaction Monitoring rule filter, available in the Marketplace and Banking schemas, that counts the unique Seller IDs a user has interacted with, including the current transaction's seller, for more accurate relationship-based risk detection.

Bug Fixes

• Resolved an issue with the user list in the case assignment dropdown.
• Resolved transactions not moving out of custom queues after being actioned.

This month's release brings improvements to the investigation workflow across alerts and cases.

Policy Monitoring

• Escalated alert status
  
  Alerts that have been escalated to a case now display a dedicated "Escalated" status on both the alert detail page and the alert discover page. The status also surfaces a direct link to the associated case, so investigators can tell at a glance which alerts are already being handled and move from an alert to its case in fewer clicks.

• Audit tab for cases and alerts
  
  Cases and alerts now include an Audit tab - a chronological timeline of every action taken, including who did it and when. Built across both the alert detail page and case detail page, the tab gives managers and compliance teams direct visibility into workflow history without needing to chase down teammates or piece together activity from other sources.
  
  
  
  

Bug Fixes

• Cases assignment issue fixed.
• Resolved an issue affecting deletion of consecutive alerts.
• Resolved an issue on Entity Discover page.

April brought a round of portal stabilization fixes alongside the release of Card Testing Detection.

Card Testing Detection

Designed for payment companies looking to proactively detect and track potential card testing activity, this new capability helps identify suspicious patterns tied to repeated card prefix usage. Related transactions are surfaced directly within the portal to support faster, more efficient investigations. Clients interested in enabling this feature can contact their Customer Success representative for activation.

Bug Fixes

• Resolved Sandbox transactions visibility issue in portal.
• Resolved limited label statuses when reordering labels.
• Resolved Queue not displaying alerts.
• Resolved calendar date picker issue in Cases Merchant view.
• Resolved daily currency exchange rate issue.

improvement 

This month’s release includes enhancements to Policy Monitoring and Transaction Monitoring, along with bug fixes and reliability improvements.

Policy Monitoring

Additional Columns at Alert and Case Discover

• MCC Column at Alert Discover - Investigators can now see the Merchant Category Code directly in the alert list view. This provides additional context when reviewing alerts, particularly when evaluating transaction counts and amounts relative to merchant category.
• Entity Name and Entity ID at Case Discover - These fields are now available as standalone columns at the case level. Previously, investigators would include the entity name in the case title as a workaround, making it difficult to search or filter cases by entity. This resolves that gap and improves investigative efficiency.

Transaction Monitoring

Count of Seller IDs per User ID
A new rule filter has been added to Transaction Monitoring that tracks the number of unique Seller IDs a user is interacting with. This filter is available in the Marketplace and Banking schemas and strengthens relationship-based risk detection across user-seller interaction patterns.

Bug Fixes 

Resolved queue and SSO configuration errors.

These updates improve visibility, strengthen monitoring capabilities, and enhance overall system reliability.

This month's releases include new API capabilities, portal usability improvements, expanded rule-building options, and a few bug fixes.

API

• New Payment Method Values Added
  Four new values have been added to the payment.method field: klarna, blik, and virtual_account,click_to_pay. These allow transactions processed via these payment methods to be correctly categorized, filtered, and used in rule creation.

Transaction Monitoring

• Network History Table Logic Updated
  The Network History table has been updated to improve the accuracy and consistency of the data displayed.
  
  
• New Rule to Flag When Sender and Receiver are the Same Entity
  New rule to flag transactions in Banking Marketplace Schema where the sender and receiver appear to be the same person, addressing potential self-processing behavior indicative of money laundering.

Portal & Usability

• Deleted and Unknown Labels No Longer Appear in Discover Filters 
  Labels that have been deleted or are otherwise unrecognized will no longer surface as options in the Events > Discover > Labels filter, reducing clutter and preventing confusion when filtering transactions.

Bug Fixes

• Resolved entity API returning unexpected not-found errors.
• Deleted and unknown labels no longer appear in Discover filters.
• Resolved a login email issue.

This month's releases include a major platform upgrade, enhancements to Policy Monitoring, new device intelligence integrations, and a series of bug fixes that improve portal usability and system reliability.

Platform

• Platform-Wide Upgrade to Node.js v20 - We have completed a full upgrade of our platform infrastructure from Node.js 14 to Node.js 20. This ensures continued security, stability, and performance across the platform, and keeps us ahead of end-of-life runtime deadlines. No action is required from clients for this update.
  
  

Policy Monitoring

• Rule Filters Now Reflect Custom Time Range Targets - Rule filters now include targets that use custom time range configurations. Previously, targets created with the newer interval or time range options were not appearing in rule filter selections.
  
  

DataHub & Integrations

• Shield Device Intelligence Integration - FraudNet has partnered with Shield as a device intelligence provider. Clients using Shield can now send Shield response data to FraudNet via API. All supported Shield fields have been added to the Device object, enabling clients to map, visualize, and write rules against this data in Transaction Monitoring.

Bug Fixes & Reliability Improvements

• Policy Monitoring alerts now move out of queues after being actioned.
• Deny list upload issue resolved. 
• Transaction Overview seller object count display issue resolved.
• Duplicate and inconsistent field naming across Events/Discover and Rule filters corrected.
• Resolved issue with device language filter.
• Batch-level failure alerting added during SFTP file sync extract phase.

For questions about any of these updates, please reach out to your account team.

This month's releases include enhancements to Policy Monitoring, Integration and API updates, and a few bug fixes that improve system reliability and data accuracy.

Policy Monitoring

• Stale Auth Rule Logic Adjusted to 25-Day Window - The stale authorization rule has been updated to evaluate within a 25-day window, improving the accuracy of stale auth detection.
  
  
• Expanded Time Range Options for Target Thresholds - Users now have two new, more flexible time-range configurations when setting target thresholds:
  • Interval – Choose from This Day, This Week, or This Month to define true daily, weekly, or monthly limits instead of relying on generic lookback periods.
  • Time Range – Define precise "from–to" windows (e.g., 1 to 30 days ago or 15 to 14 days ago). This supports both traditional rolling lookbacks and new use cases like identifying stale authorizations or detecting dormancy.
    
    

Integrations

• Enhanced TSYS Integration with New Direct Feed - Client data can now be pulled directly from TSYS, rather than clients sending a copy of the TSYS data to FraudNet. This reduces operational overhead while ensuring FraudNet receives the data straight from the source (TSYS).

API

• New transfer_date Field in the Banking Marketplace API - A new optional transfer_date field has been added to the transaction object for both transaction creation and updates. This field represents the intended future date on which a scheduled transaction is set to execute, useful for payments that are approved today but settled at a later date.
  
  

Bug Fixes & Reliability Improvements

• Resolved transaction visibility issues.
• Resolved policy alerts-to-transaction linking.
• Synced alert closure status with case closure.