On-premises

Tietoevry offers EGW as an on-premises deployment, providing banks, processing centers, and PSPs with a secure, and scalable payment infrastructure—while maintaining full control over the hosting environment.

Who is Suits

Organization requiring full control over their infrastructure, strict data governance, or advanced compliance can benefit from the on-premises model’s independence ad deeper customization.

Key Characteristics of On-Premises Deployment

• Hosted within Financial Institution Infrastructure - EGW is deployed on the customer’s servers, whether in a private data center, managed customomer public cloud, or a corporate IT environment, ensuring complete control over data and system management.

• Customer-Managed Operations - The financial institution is responsible for managing the hosting environment, including hardware maintenance, software updates, monitoring, backups, and compliance.

• Infrastructure Independence - EGW operates independently within the customer’s IT environment, offering flexibility to integrate with existing banking systems, core payment processing solutions, and maintaining full control over data processing.

• High Availability and Performance - The on-premises version supports resilient configurations with options for load balancing, failover, and redundancy, tailored to the financial institution’s infrastructure setup.

• Scalability on Demand - Institutions can scale according to their internal capacity planning, allowing flexible resource expansion to accommodate growing transaction volumes.

• Customizable Maintenance and Upgrade Schedules - Updates and improvements are performed according to the institution’s internal schedule, reducing disruption and aligning with operational processes.

PCI DSS Readiness of the EGW Solution

The E-Commerce Payment Gateway (EGW) is PCI DSS ready, meaning it is designed and configured to meet PCI DSS requirements. However, the actual PCI DSS certification must be obtained by the customer who deploys and operates the solution.

Scope of PCI DSS Readiness

• Card Data Transmission and Processing - EGW is developed to handle card payment data securely, following PCI DSS best practices. All data is encrypted and processed within a PCI DSS-compliant framework when properly configured.

• Tokenization and Sensitive Data Protection - EGW supports tokenization of sensitive data and ensures that raw cardholder data is not stored. All sensitive data is tokenized and encrypted both in transit and at rest.

• Secure Interfaces and APIs - EGW APIs are designed to follow PCI DSS security requirements, including strong authentication, encryption, access control, and audit logging.

• Certified Environment Requirement - The on-premises version of EGW requires the customer to ensure that the hosting environment meets PCI DSS standards. This includes performing regular audits, implementing necessary security measures, and achieving certification.

Audits and Certification

EGW software itself is PCI DSS ready, but the final PCI DSS certification must be obtained by the financial institution that owns and operates the on-premises deployment. Tietoevry can provide guidance and support on achieving compliance as part of the implementation process.