Platon rebuilt its payment infrastructure in Ukraine without starting from scratch

Ukrainian PSP Platon moved from a stable but aging setup to a new payment platform model with a SaaS test phase first, then an on-premises deployment on dedicated servers in one of Ukraine’s major data centers. For PSPs, the point is simple: if you need bank and acquirer integrations, more routing control, and room to scale, infrastructure eventually stops being “just IT” and starts deciding how fast you can operate.

1. Platon has been operating since 2012, serves more than 1,000 businesses in Ukraine, and processes over 3 million transactions per day. Over time, its existing payment system no longer matched the pace of the market, so the company needed new integrations, more flexibility, and a way to manage infrastructure independently.
2. Instead of replacing everything in one shot, Platon tested Akurateco’s white-label payment platform in a SaaS format first. That let the team validate functionality, payment capabilities, and operational scenarios before moving to a dedicated environment.
3. After the pilot, Akurateco deployed Platon’s on-premises infrastructure on dedicated servers in one of Ukraine’s major data centers. The work included installing the payment software, migrating the necessary data, and preparing the environment for independent PSP operations.
4. Bank-acquirer integrations were central to Platon’s model, so Akurateco also trained the client’s team. For three months, its specialists supported setup, configuration, and knowledge transfer. Within six months, Platon was managing the core part of its infrastructure independently, with support from Akurateco, and by the end of the year it had full control over its payment system in a dedicated environment.
5. Since 2021, Platon has been operating on the upgraded payment platform with access to modern integrations and technologies. The practical payoff for a PSP is more control over configuration, security, performance, and future infrastructure development, without being boxed in by the previous system.

The interesting part for high-risk operators and their PSPs is the migration pattern itself: SaaS first to de-risk the switch, then on-premises once the setup is proven. That is a tidy way to avoid rebuilding a live payment stack blind.