Bank Pekao adopts NCR Atleos Authentic payment switching platform

What happened

NCR Atleos Corporation has announced that Bank Pekao S.A., one of the largest financial institutions in Central and Eastern Europe, has selected its Atleos Authentic payment switching platform as part of a modernisation of its card payment processing infrastructure.

The deployment forms part of a broader technology upgrade at the bank, with Atleos Authentic set to underpin how Bank Pekao routes and processes card transactions going forward.

Why it matters

Payment switching sits at the core of how banks authorise, route and settle card transactions, so upgrading this layer is a structural decision rather than a cosmetic one. For a large regional bank like Pekao, moving to a modern switching platform is typically about resilience, scalability and the ability to support new payment types and channels without re-engineering core systems each time.

For the wider banking and payments sector, the move underlines a steady shift away from legacy, hard-to-change switching infrastructure toward platforms designed for flexibility — a prerequisite for banks that want to keep pace with evolving consumer payment behaviours, real-time processing expectations and regulatory change across Central and Eastern Europe.

The Renascence take

Payment switching upgrades rarely make headlines because they are invisible to the end customer when done well — and that invisibility is precisely the point.

Most coverage of infrastructure deals like this focuses on the vendor and the technology, but the real story is behavioral: customers only ever notice their payment infrastructure when it fails — a declined card, a slow authorisation, a system outage at the worst possible moment. Banks that treat switching platform modernisation purely as a back-office IT decision miss the chance to use it as a lever for trust; every millisecond shaved off authorisation time and every reduction in false declines is a direct, if silent, improvement to customer confidence. Operators undertaking this kind of upgrade should resist treating it as "plumbing" alone and instead map the customer-facing failure points — declined transactions, latency, downtime — that the new platform is meant to fix, then measure and communicate improvement against those specific moments rather than the migration itself.