About
I build adaptable payment technology that works across devices, transaction flows, and the systems behind them.
01 / Foundation
I began my career in .NET backend development, learning how to build the services and data flows behind an application. I then worked across the full stack with AngularJS and moved into hybrid mobile applications. That progression taught me to see a product from its user interface through its APIs, operations, and infrastructure.
02 / Specialisation
My work later moved to Android payment terminals across device families from Landi, Ingenico, PAX, Verifone, KOZEN, Sunmi, Newland, and others. Each device has its own SDK and hardware behavior, while merchants and acquirers need a consistent payment experience. I focus on a common application layer that separates shared transaction behavior from vendor-specific integrations.
03 / Leadership
At Ingenico, I progressed from Technical Lead to Engineering Manager, working on Android payment applications, device-to-cloud connectivity, and engineering delivery through July 2025. Since September 2025, I have been Head of Technology at SeaPos Payment Services Pvt. Ltd., working across payment device software and the wider platforms that support it.
04 / Exploration
I am now exploring where AI can improve payment engineering and commerce, especially when an automated system must explain what it knows, stay within its authority, and handle uncertain transaction outcomes. On this site, I share practical writing, interactive tools, and selected work from that journey.
Career chronology
Head of Technology
SeaPos Payment Services Pvt. Ltd.
Engineering Manager
Ingenico India International
Technical Lead
Ingenico India International
Lead Engineering
Commdel Consulting Services
Sr. Associate Engineer Lead
Commdel Consulting Services
Team Lead
Oath Infosystems Pvt. Ltd.
Senior Developer
Oath Infosystems Pvt. Ltd.
Software Developer
Winsoft Software Solution
Global delivery
Across both on-site and remote engagements, spanning terminal deployments, transaction platform integrations, and merchant-side rollouts.
Technical expertise
Experience with Android payment terminals and SDKs across multiple device families, using explicit capability contracts rather than assuming every terminal behaves identically.
Distributed switching, orchestration, reversal and reconciliation, high-throughput authorization pipelines, connector abstraction, per-contract profiles.
Cryptographic key management, HSM integrations, PCI-DSS-aware architecture, secure device provisioning, key-ceremony orchestration.
Mandate design, consent freshness, step-up authentication, audit-trail-first agent flows, rails-aware policy — commerce for parties that aren't humans.
Principles
UNKNOWN is not the absence of information. It's information — that a layer sent a request and did not observe a response. Design your schema so every layer can say so.
An approval and a subsequent reversal are two facts. Overwriting the first with the second is lying about the past. Every dispute you'll ever answer will want the trail.
The logical-operation id is sticky across retries. The attempt id changes. If your terminal firmware generates a fresh transaction id every time the operator presses ‘retry’, you have duplicate transactions.
The terminal reports what it observed. The ledger is the source of truth. When they disagree, the ledger wins. Everything downstream should be built on that hierarchy.
Contact