KotlinConf Recap: Lessons from Verifone’s Architect on Kotlin in Mission-Critical Payments

Summary

Verifone architect Yuri Geronimus presented at KotlinConf 2026 on using Kotlin’s type system to enforce payment specifications at compile time. He described six incident patterns where a single misused word caused outages, compliance failures, or financial loss, including a terminal fleet outage from a nullable mandatory field. His method uses value classes for spec nouns, validate factories at boundaries, non-null types, masked sensitive data by default, and state-specific classes to make illegal states unrepresentable. Geronimus advocates incremental migration from legacy Java and C++ systems using four parallel tracks rather than a rewrite, noting that payment terminals must operate offline for up to 40 days by regulation. The approach shifts reliability from developer discipline to compiler enforcement, enabling engineers to speak the business language and propose regulatory changes.

Takeaways

1. 1

   Kotlin’s inline value classes prevent argument swapping at compile time by wrapping spec nouns like Stan, TerminalId, and AmountMinor in distinct types, turning a runtime bug into a build error.

2. 2

   Validate factories parse external fields into sealed results at the boundary, ensuring exhaustive handling without exceptions or silent fallbacks, and structured rejection instead of try/catch.

3. 3

   Incremental migration using four parallel tracks—optimize existing code, acceptance tests, fitness functions, and incremental migration—avoids the risks of a rewrite in live payment systems with no acceptable downtime.

FAQ