Farnaz Bagheri

Software Engineer · Payment Infrastructure

I'm a software engineer with a focus on payment infrastructure, point-of-sale system integrations, and the backend architecture that underlies modern financial software. My work sits at the intersection of distributed systems engineering and the operational realities of real-world payment processing.

I'm particularly interested in the structural problems that make payment systems difficult to build correctly — the fragmentation, inconsistent APIs, proprietary device protocols, and the hidden complexity of managing transaction state reliably.

My engineering background spans backend development, payment device integrations, and fintech platform architecture. I have hands-on experience building systems in Node.js, working with React on the frontend, and designing data models in MongoDB for transaction-heavy applications.

A significant part of my technical work has been in POS system integrations — understanding how payment terminals communicate with backend services, how EMV certification constrains device-side logic, and how different processors expose wildly different integration surfaces for conceptually identical operations.

I've worked on systems where the gap between what a payment processor says their API does and what it actually does in production is significant — where the cost of getting it wrong is measured in failed transactions, chargebacks, and lost merchant trust.

I'm developing a systems architecture concept called PayBridge — a conceptual framework for unified payment orchestration that explores how POS and SaaS platforms could connect to payment processors and certified devices through a normalized, interoperable layer.

PayBridge is a research and design exercise, not a commercial product. It's a way to rigorously work through the architectural decisions required to meaningfully reduce the integration burden that falls on POS developers and payment engineers.

Payment systems today remain deeply fragmented. A software engineer integrating a POS platform with a new processor typically faces: a bespoke SDK with inconsistent abstractions, a certification process that constrains device logic, undocumented edge cases in transaction state management, and little shared tooling to draw from.

Through technical writing, systems design exploration, and architectural documentation, I'm working toward a more coherent body of knowledge about how payment infrastructure should be designed — and what interoperability in this space could actually look like.

Language
Node.js · TypeScript
Frontend
React
Database
MongoDB
Domain
Payment Infrastructure
Protocols
EMV · ISO 8583 · REST
  • Payment orchestration & processor routing
  • Offline-capable transaction handling for POS
  • Normalized state machines for payment lifecycle
  • Device-cloud payment interoperability
  • The cost of payment processor fragmentation
  • Reliable financial software at the infra layer