A worldwide FinTech company approached Trianz to manage millions of credit and debit card transactions each year. It needed a partner to host, monitor, and optimize its payment gateway application, which was important to the company’s overall market penetration plan.
HOSTING, MONITORING AND SUPPORT OF A LARGE PAYMENT GATEWAY
BUSINESS CHALLENGES FOR THE GLOBAL FINTECH PROVIDER
The following technical components were implemented by Trianz in collaboration with the worldwide FinTech provider:
- Microsoft Azure was picked as the cloud service platform of choice because it offers auto scaling, pay-as-you-go charging, and a wide range of integration options.
- EDB Postgres enhances the capabilities of PostgreSQL databases by adding security for Kubernetes containers.
- Microsoft Azure was used to move and host the client’s proprietary payment gateway system.
- Splunk was chosen as a data platform that uses machine learning to find trends, offer analytics, and diagnose problems with data sources.
- Dynatrace was chosen to help with application and infrastructure security monitoring in the cloud, with automation and AI capabilities.
- Using centralized access controls and an encryption key management repository, Vormetric was employed to encrypt any at-rest data included within EDB Postgres for the FinTech client.
- Thales HSMs, or hardware security modules, are hardware-based security devices that are compatible with Microsoft Azure cloud services (HSMs).
- When internal personnel accesses sensitive applications and data in Azure, RSA SecureID was used as a two-factor authentication layer.
- The Citrix Application Delivery Controller (previously Netscaler) was used to load balance containers-hosted apps across Azure, ensuring security and visibility.
HOW TRIANZ TRANSFORMED THE FINTECH CLIENT’S PAYMENT GATEWAY ON AZURE
Trianz created a managed services strategy centered on the payment gateway. This would cover hosting, infrastructure and application monitoring, as well as ongoing platform updates as the client requests.
The infrastructure architecture, as well as a migration and rapid stabilization approach, were then created on Azure. During this phase, stakeholders were consulted to better understand inter-departmental business requirements.
A managed services framework based on Business-as-a-Service was implemented, encapsulating the fundamental features required for the FinTech client’s payment gateway to function properly. Transitional processes, management over time, and planned modifications to the payment gateway system were all part of this.
The whole payment gateway, as well as security, data, and access control setup, was then transferred to Azure. The Azure architecture was built to meet the client’s stringent security and compliance needs.
Finally, depending on cloud service usage and various Infrastructure-as-a-Service and Platform-as-a-Service modules, service level agreements and support methods were agreed upon.
TRANSFORMATIONAL EFFECTS AFTER MIGRATING THE PAYMENT GATEWAY TO AZURE FOR THE FINTECH CLIENT
Trianz created a managed services strategy centered on the payment gateway. This would cover hosting, infrastructure and application monitoring, as well as ongoing platform updates as the client requests.
The infrastructure architecture, as well as a migration and rapid stabilization approach, were then created on Azure. During this phase, stakeholders were consulted to better understand inter-departmental business requirements.
A managed services framework based on Business-as-a-Service was implemented, encapsulating the fundamental features required for the FinTech client’s payment gateway to function properly. Transitional processes, management over time, and planned modifications to the payment gateway system were all part of this.
The whole payment gateway, as well as security, data, and access control setup, was then transferred to Azure. The Azure architecture was built to meet the client’s stringent security and compliance needs.
Finally, depending on cloud service usage and various Infrastructure-as-a-Service and Platform-as-a-Service modules, service level agreements and support methods were agreed upon.