Open to SDE/backend/platform roles

Yogesh Sai Dondapati

Software Engineer @ Juspay

Building payment infrastructure, authentication systems, and risk pipelines for real-world transaction platforms.

Lead developer for Air India integration

View Engineering Work

production-shell

$ whoami

backend/platform engineer @ Juspay

$ focus

payment auth, risk systems, merchant analytics, production reliability

$ status

Open to SDE/backend/platform roles

Live system topology

Scroll through transaction lanes, architecture boundaries, production impact, and engineering judgment.

Scroll controls camera depthPointer controls perspective

250K+

monthly card transactions supported

Lead dev

Air India integration

Tech lead

AIX integration

20M/day

Express Checkout analytics support

NIT

Durgapur CSE

Juspay

Associate SDE

JuspayNIT DurgapurPayment Infrastructure3DS AuthenticationFraud Risk ManagementMerchant Analytics

Engineering Impact

Production systems, not portfolio filler

Selected work across payment authentication, merchant integrations, wallet routing, fraud risk, and analytics.

Lead Developer

Air India 3DS Authentication

Air India needed a production-ready card authentication path that fit merchant checkout expectations while preserving payment correctness and operational visibility.

Designed API contracts, card-auth orchestration, data movement, load testing coverage, and reusable onboarding patterns for merchant-specific authentication flows.

3DSUASEulerAPI Contracts

Supported authentication flow for 250K+ monthly card transactions.

Tech Lead

AIX Integration Leadership

AIX required careful alignment between merchant expectations, payment flow behavior, provider boundaries, and production reliability standards.

Led integration architecture, system flow alignment, API contracts, merchant-specific handling, edge-case review, and rollout readiness.

Technical LeadershipMerchant IntegrationReliabilityAPI Design

Owned technical design, integration readiness, and production-oriented execution.

Backend Developer

Apple Pay Gateway Routing

Apple Pay support required transaction routing that could handle tokenized payment data safely across gateways with different expectations.

Implemented token decryption mapping, API extensions, gateway decision logic, and secure forwarding for encrypted and decrypted flows.

Apple PayTokenizationGateway RoutingSecure Data

Enabled Apple Pay support through dynamic encrypted/decrypted transaction flows.

Backend Engineer

Fraud Risk Pipeline

Merchants needed risk decisions at multiple transaction stages, while operations needed feedback loops for failures, refunds, and chargeback signals.

Integrated Accertify and Feedzai flows, risk policy controls, country/currency lists, lifecycle scoring, and feedback handling.

AccertifyFeedzaiRisk ScoringPolicies

Integrated fraud-risk providers across pre-transaction, post-transaction, and pre-refund stages.

Backend Engineer

Multi-Currency Merchant Analytics

Merchants operating across currencies needed dashboard analytics that could compare global transaction volume without manual reporting overhead.

Designed scheduled exchange-rate ingestion, USD-normalized storage, query-time conversion wrappers, optimized queries, and schema extensions.

AnalyticsCurrency ConversionData PipelinesClickHouse

Supported analytics for 20M/day transactions through the Express Checkout product.

Architecture Thinking

How I reason about payment flows

The diagrams are sanitized, but the concerns are real: contracts, state, provider behavior, observability, and failure modes.

Card Authentication Flow

Authentication state moves through merchant checkout, Euler, UAS, 3DS provider, gateway, and issuer response.

1Checkout

2Euler

3UAS

43DS

5Gateway

6Issuer

Fraud Risk Pipeline

Risk controls and provider scoring operate before payment, after payment, and before refund decisions.

1Intent

2Policy

3Provider

4Decision

5Feedback

6Controls

Merchant Analytics Data Flow

Transaction events and exchange-rate data become normalized metrics for global merchant dashboards.

1Events

2Rates

3Normalize

4Store

5Query

6Dashboard

Case Studies

Technical memos from production work

Each case study is written at a high level to show the engineering judgment without exposing confidential internals.

Lead Developer

Air India 3DS Authentication

A sanitized look at integrating UAS into the Euler transaction flow and operationalizing 3DS card authentication for a large merchant.

3DSUASEuler

Read memo

Tech Lead

AIX Integration Leadership

How technical ownership across merchant flows, contracts, edge cases, and readiness turned a complex integration into a production path.

Technical LeadershipMerchant IntegrationReliability

Read memo

Backend Developer

Apple Pay Gateway Routing

A generalized case study on Apple Pay token handling, gateway routing, and secure support for encrypted and decrypted payment paths.

Apple PayTokenizationGateway Routing

Read memo

Backend Engineer

Fraud Risk Pipeline

A sanitized view of integrating Accertify and Feedzai into transaction lifecycle risk scoring with merchant-configurable controls.

AccertifyFeedzaiRisk Scoring

Read memo

Backend Engineer

Multi-Currency Merchant Analytics

How exchange-rate ingestion, normalized values, and query-time conversion APIs can make global merchant reporting usable.

AnalyticsCurrency ConversionData Pipelines

Read memo

Principles

Principles I engineer by

Reliability before cleverness

Production systems reward clear recovery paths, bounded complexity, and predictable behavior under pressure.

Observability is part of the feature

A payment flow is not complete until operators can explain what happened, where it failed, and what to do next.

APIs are contracts, not just endpoints

Strong contracts reduce ambiguity between merchants, providers, gateways, and internal services.

Payment systems require defensive design

Retries, idempotency, validation, secure forwarding, and fallback paths are core design material.

Ownership means staying close to production

The work includes rollout readiness, monitoring, incident feedback, and keeping the system understandable.

Scale starts with data and failure modes

Before code gets complicated, the hard questions are usually correctness, shape of data, and behavior during partial failure.

Writing

Notes on payment systems and production engineering

Realistic article drafts and notes for topics that map directly to Yogesh's backend/platform work.

Draft8 min

How 3DS Authentication Works in Payment Systems

A practical walkthrough of authentication requests, issuer challenge flows, gateway handoffs, status mapping, and production failure modes.

3DSPaymentsAuthentication

Note6 min

Designing Merchant-Scale Currency Analytics

Notes on exchange-rate ingestion, normalized storage, query-time conversion, and why analytics correctness is a trust feature.

AnalyticsCurrencyData

Draft7 min

Fraud Scoring Pipelines: Pre, Post, and Refund Risk

How risk systems change when scoring spans transaction intent, payment completion, refund review, and operational feedback.

RiskFraudPipelines

Note5 min

Apple Pay Token Flows and Gateway Routing

A sanitized systems note on tokenized payments, encrypted/decrypted flow selection, gateway capabilities, and secure forwarding.

Apple PayTokenizationRouting

Essay9 min

Idempotency Patterns in Payment Systems

A production-oriented view of duplicate requests, retries, status reconciliation, and designing APIs that survive network uncertainty.

ReliabilityAPIsPayments

Note6 min

What Production Monitoring Teaches You

Lessons from staying close to production: alerts, dashboards, failure narratives, ownership boundaries, and operational judgment.

ObservabilityMonitoringOperations

Recruiter CTA

Hiring for backend, platform, infrastructure, payments, or distributed systems?

I bring production ownership across payment authentication, risk systems, merchant integrations, analytics pipelines, and reliability-focused backend engineering.

Contact Yogesh Download Resume View LinkedIn