Payments is an unglamorous specialty and I've grown to like it: certification cycles, correctness under partial failure, and code that has to survive an audit.
Nearly five years on LS Pay. I maintain and extend the engine and the 40+ provider connections running on it, build and certify new integrations end to end, and own most of the Android work on the team. When a payment fails in production at a customer in another country, I'm one of the people who gets called.
The work I'm proudest of is the work that made everyone else faster. A set of Claude Code skills now reads a provider's specification and drives the integration through to reviewed code, which cut a typical delivery from six weeks to two — measured across real integrations, at the same quality bar. Cloud log ingestion I designed for LS Pay V3 replaced "ask the customer to email us their logs" with production telemetry we can query from anywhere.
Outside work I build Skorva, a real-time distributed darts scoring platform on ASP.NET Core and Flutter. Every architectural decision on it is written down and argued through, because that's the habit I want to have.
