ACI Payment Systems z/OS

ACI Acquirer Modernization Guide

Application - Banking/Finance

ACI Acquirer is a application - banking/finance product by ACI Payment Systems. Explore technical details, modernization strategies, and migration paths below.

Product Overview

ACI Acquirer is a multi-platform system designed for managing merchant transactions and processing payments in multiple currencies.

ACI Acquirer integrates with existing systems through APIs and supports various security measures to protect sensitive data.

Modernization Strategies

Rehost

Timeline:
6-12 months

Lift-and-shift to cloud infrastructure with minimal code changes. Fast migration with lower risk.

Refactor (Recommended)

Timeline:
18-24 months

Optimize application architecture for cloud while preserving business logic. Best ROI long-term.

Replatform

Timeline:
3-5 years

Complete rewrite to cloud-native architecture with microservices and modern tech stack.

Frequently Asked Questions

General

What does ACI Acquirer do?

ACI Acquirer is a multi-currency merchant management system designed for handling payment transactions. It provides the tools and infrastructure necessary for businesses to manage and process payments from various sources. It supports client/server architecture with database options on z/OS and UNIX.

Is this a system, an application, or a tool?

ACI Acquirer is primarily an application, although it includes system-level components for database interaction and transaction processing. It is not a tool set or framework in the traditional sense, but a complete solution for payment management.

What types of organizations use this?

Organizations that require robust and scalable payment processing capabilities, particularly those dealing with multiple currencies, benefit most from ACI Acquirer. This includes large retail businesses, financial institutions, and payment service providers.

When should we consider ACI Acquirer?

A company should consider ACI Acquirer when it needs a comprehensive solution for managing merchant transactions, especially if it operates in multiple countries or handles various currencies. It is also suitable when a business requires a system that can integrate with existing mainframe or UNIX-based infrastructures.

What are the alternatives to ACI Acquirer?

Alternatives to ACI Acquirer include BASE24-eps, T24 Enterprise, Connex, and CAMS II. These products offer similar functionalities in payment processing and merchant management, but may differ in their specific features, architecture, or platform support.

Technical

What infrastructure is required?

ACI Acquirer can run on z/OS, utilizing DB2, or on UNIX systems with Oracle databases. It is designed as a client/server application, with components running on both mainframe and UNIX environments.

For mainframe products: Does this run in an LPAR?

For z/OS deployments, ACI Acquirer typically runs in an LPAR and is dependent on the z/OS operating system. It may require specific subsystems for transaction processing and database connectivity.

How does ACI Acquirer integrate with other systems?

ACI Acquirer integrates with various systems through APIs, including transaction processing systems, fraud detection systems, and reporting tools. It supports standard communication protocols for data exchange and system integration.

What are the main system components of ACI Acquirer?

The main system components include transaction processing modules, database interfaces, communication handlers, and security modules. These components work together to manage the end-to-end payment processing lifecycle.

Business Value

What business problem does ACI Acquirer solve?

ACI Acquirer solves the business problem of efficiently managing and processing payment transactions across multiple currencies and channels. It enables organizations to streamline their payment operations and reduce the complexity of handling diverse payment methods.

What would happen if an organization did NOT use this product?

If an organization did not use ACI Acquirer or a similar system, it would likely face increased operational costs, higher error rates, and greater complexity in managing payment transactions. It might also struggle to support multiple currencies and payment methods effectively.

What is the business value of using ACI Acquirer?

ACI Acquirer provides a centralized platform for managing merchant relationships, processing transactions, and generating reports. This leads to improved efficiency, reduced costs, and better visibility into payment operations.

How does ACI Acquirer help with regulatory compliance?

ACI Acquirer helps organizations comply with industry regulations and security standards related to payment processing. It provides features for data encryption, access control, and audit logging to ensure the security and integrity of payment transactions.

Security

What specific authentication methods are supported?

ACI Acquirer supports authentication methods such as username/password, multi-factor authentication, and integration with external authentication systems like LDAP. The specific methods used depend on the configuration and security policies of the organization.

What access control model is used?

ACI Acquirer uses an access control model based on roles and permissions. This allows administrators to define roles with specific privileges and assign users to those roles, controlling their access to different functions and data within the system.

What encryption is used and where?

ACI Acquirer uses encryption to protect sensitive data both in transit and at rest. This includes encrypting payment card data, personal information, and other confidential data stored within the system. Encryption algorithms such as AES and TLS are commonly used.

What audit/logging capabilities exist?

ACI Acquirer provides comprehensive audit logging capabilities, recording all significant events and transactions within the system. This includes user logins, data modifications, and system configuration changes. These logs can be used for security monitoring, compliance auditing, and forensic analysis.

Operations

How is ACI Acquirer typically deployed?

ACI Acquirer is typically deployed on-premise or in a hybrid environment, with some components running on mainframe systems and others on UNIX servers. The specific deployment model depends on the organization's infrastructure and security requirements.

What level of technical expertise is required to implement ACI Acquirer?

Implementing ACI Acquirer requires a team with expertise in mainframe systems, UNIX servers, database administration, and payment processing. The implementation process involves configuring the system, integrating it with existing infrastructure, and testing its functionality.

What ongoing operational requirements exist?

Ongoing operational requirements include monitoring system performance, maintaining database integrity, applying security patches, and managing user access. Regular maintenance and updates are necessary to ensure the system remains secure and reliable.

What are common implementation challenges?

Common implementation challenges include integrating ACI Acquirer with legacy systems, ensuring data consistency across different platforms, and addressing security vulnerabilities. Thorough planning and testing are essential to overcome these challenges.

Ready to Start Your Migration?

Download our comprehensive migration guide for ACI Acquirer or calculate your ROI.

Calculate ROI