Correctness First
Payment systems must handle retries, integrations, and real-world failures without losing integrity. Edge cases are part of the product.
Software Architect • Payments Platforms
I design and maintain payment services in regulated environments — from PCI-driven portals and vendor integrations to IVR (Asterisk) infrastructure and kiosk applications. My focus is stability, correctness, and controlled evolution.
Production discipline over theoretical elegance.
Payment systems must handle retries, integrations, and real-world failures without losing integrity. Edge cases are part of the product.
PCI constraints shape architecture decisions. Security and delivery must coexist — not compete.
Systems should be maintainable, observable, and understandable by the team that supports them.
Long-term ownership in payment services platforms.
Software Architect — 2014 to Present
Lead payment portal upgrades, vendor integrations, IVR infrastructure, and kiosk-based payment applications within a PCI-regulated environment.
Web Application Developer — 2014 to Present
Contribute to payment platform development using Sencha and PHP, enhancing stability and feature depth.
Detailed roles, systems, and platform work across payments, infrastructure, and integrations.