What are the main system components?

The system components include the Fraud Detection Engine, the Rules Engine, the Transaction Monitor, and the Reporting Module. These components communicate through internal APIs and messaging queues.

What databases are used?

FIS Fraud Navigator likely uses a relational database such as Db2 on z/OS for storing transaction data, rules, and fraud event information.

What protocols are used for communication?

The product uses standard protocols such as TCP/IP for network communication. Specific ports depend on the configuration and the components involved.

How does FIS Fraud Navigator integrate with other systems?

The system supports integration via REST APIs. Specific API endpoint patterns and method names are detailed in the API documentation.

What is the business value of FIS Fraud Navigator?

FIS Fraud Navigator helps reduce financial losses due to fraud by providing early detection and prevention capabilities. It enables real-time monitoring and intervention.

How does it improve operational efficiency?

By automating fraud detection, the system reduces the manual effort required to identify and investigate suspicious transactions, improving operational efficiency.

How does it help with decision-making?

The system's reporting module provides insights into fraud trends and patterns, enabling better decision-making and strategy adjustments.

What access control model is used?

The system uses a role-based access control (RBAC) model to manage user permissions and access to sensitive data and functions.

What encryption is used?

Encryption is used to protect sensitive data both in transit and at rest. Specific encryption algorithms are detailed in the security documentation.

What audit logging capabilities exist?

The system provides audit logging capabilities to track user activities and system events, aiding in compliance and forensic analysis.

What administrative interfaces are available?

Administrative interfaces include a command-line interface (CLI) and potentially a web-based console for managing the system. Specific commands are detailed in the administration guide.

How is user management handled?

User management is handled through the administrative interface, allowing administrators to create, modify, and delete user accounts and assign roles.

What are the main configuration parameters?

Main configuration parameters include database connection settings, API endpoint configurations, rule definitions, and security settings. These are typically managed through configuration files.

What monitoring and logging capabilities exist?

The system provides monitoring and logging capabilities, allowing administrators to track system performance, detect issues, and analyze fraud events. Logs are typically stored in a dedicated directory on the z/OS USS.

Are You a Vendor? Claim Your Listing

Take control of your product listings. Add verified information, showcase updates, and unlock a Claimed Vendor badge across the directory.

Claim Your Listing Now

FIS Fraud Navigator

FIS Active z/OS

Application - Banking/Finance Administration

Vendor

FIS

Product Overview

FIS Fraud Navigator is designed with a multi-tiered architecture, featuring the following key components: * **Fraud Detection Engine:** The core component responsible for analyzing transactions and identifying potentially fraudulent activities based on defined rules and models. * **Rules Engine:** Allows administrators to define and manage fraud detection rules. These rules are evaluated against incoming transactions to identify suspicious patterns.

* **Transaction Monitor:** Provides real-time monitoring of transaction flow, enabling immediate detection and intervention. * **Reporting Module:** Generates reports on fraud trends, system performance, and other key metrics. These components communicate through internal APIs and messaging queues, ensuring efficient and reliable data exchange.

The system likely uses Db2 for persistent data storage. Integration with external systems is achieved through REST APIs, allowing for seamless data exchange and coordination. Security is enforced through a role-based access control (RBAC) model and supports authentication methods such as LDAP and Kerberos.

Competing products may use different architectural patterns or data storage solutions. FIS Fraud Navigator is optimized for the z/OS environment and the FIS Payments ecosystem.

Frequently Asked Questions

What is FIS Fraud Navigator?

FIS Fraud Navigator is a component of the FIS Payments system designed to assist in early fraud protection. It operates within the z/OS USS environment.

How is FIS Fraud Navigator configured?

FIS Fraud Navigator primarily uses configuration files within the z/OS USS environment for setup and customization. Specific file names and formats are detailed in the product documentation.

Does FIS Fraud Navigator have an API?

The system exposes APIs, potentially including REST, for integration with other systems. Specific endpoint patterns and method names are detailed in the API documentation.

What authentication methods are supported?

FIS Fraud Navigator supports standard authentication methods such as LDAP, potentially Kerberos, and possibly multi-factor authentication depending on the configuration.

Related Products

View Details →

Application - Banking/Finance

View Details →

ACI Communication Services

Active

by ACI Payment Systems

z/OS

ACI Communication Services is a financial messaging platform designed for high availability and secure message exchange. The core architecture includes the Message Router, Protocol Adapters,...

Application - Banking/Finance MQ

View Details →

Help Improve This Directory

Notice outdated information? Have insights about this product? Help the mainframe community stay informed with accurate, current data.

Report Issue Suggest Product Share Event

Are You a Vendor? Claim Your Listing

Take control of your product listings. Add verified information, showcase updates, and unlock a Claimed Vendor badge across the directory.

Claim Your Listing Now