About
I'm Vikas Pandey — a software engineer and founder who has spent 17+ years building the infrastructure that moves money reliably at scale.
My career has been shaped by one consistent challenge: making complex distributed systems behave predictably under pressure. Whether that's a UPI payment completing in 300ms, a card transaction routing through the right acquirer, or a reconciliation engine processing millions of rows overnight — reliability is never an accident.
I started as a backend engineer, moved into platform work, led engineering teams, and eventually founded Veepe — a payment orchestration platform designed to make multi-gateway integration straightforward for businesses of any size. Veepe is the product I wish had existed when I was building payment systems from scratch.
My technical foundation is in Kotlin, Java, and Spring Boot for service development; AWS, Kubernetes, and event-driven architecture for platform design; and deep domain expertise in UPI, card networks (Visa/Mastercard), 3D Secure, tokenization, and settlement systems.
I write on Medium about payment systems, fintech infrastructure, and distributed systems design. I try to write the articles I needed when I was learning these topics.
What I'm working on now
- Building Veepe's payment orchestration engine and merchant dashboard.
- Writing a series on UPI internals — architecture, flows, and failure modes.
- ReconFlow: an open-source automated reconciliation toolkit for payment teams.
Principles
How I think about engineering
Systems Thinking
Good software is about tradeoffs, not perfection. Every architectural decision is a bet on the future.
Developer Experience
Engineers work better when their tools are sharp. Investing in DX compounds over time.
Clarity Over Cleverness
The best code is the code your team can reason about at 2am during an incident.
Build in Public
Writing about what you build accelerates your thinking and helps the community around you.