Rust Engineer - Payment Infrastructure

Company Introduction-

iServeU is a modern banking infrastructure provider in APAC region, empowering financial enterprises with embedded fintech solutions for their customers. iServeU is one of the few certified partners with National Payment Corporation of India (NPCI), VISA for various products.

iServeU also provides a cloud-native, micro services-enabled, distributed platform with over 5000 possible product configurations with a low code/no code interface to banks, NBFCs, Fintech, and other regulated entities.

• We process around 2500 transactions per second by levering distributed & auto scale technology like K8.

• Our core platform combines of 1200+ micro services.

• Our customer list includes Fintech start-ups, top tier private banks to PSU bank. We operate in five countries and help customers constantly change the way financial institutions operate and innovate.

• Our solutions currently empowers over 20 banks and 250+ enterprises across India and abroad.

• Our platform seamlessly manages the entire transaction lifecycle, including withdrawals, deposits, transfers, payments, and lending through various channels like digital, branch, agents.

Our team of 500+ employees, with over 80% in technology roles is spread across offices in Bhubaneswar, Bangalore and Delhi. We have raised $8 million in funding to support our growth and innovation.

For more details visit: www.iserveu.in

About the Role

We are building a high-performance Payment Hub and orchestration platform that connects merchants with multiple payment gateways, processors and acquirers. As a Rust Engineer, you will work on the core systems behind it: transaction processing and routing, gateway integrations, asynchronous workflows and production reliability. You own problems end-to-end instead of working on isolated modules.

The lifecycle you will work on: Merchant › Payment API › Decision Engine › Routing › Gateway / Acquirer › Webhooks › Refunds › Reconciliation

What You Will Own

• Core payment services: high-throughput, low-latency transaction processing, authorization/capture, refunds and reversals in Rust.

• Routing and decision engine: configurable routing rules, success-rate based selection, fallback and cascading retries across gateways and acquirers.

• Provider connectors: adapters and abstraction layers that hide provider-specific APIs, auth schemes, response formats and error codes.

• Transaction state machines: explicit, auditable lifecycle management that stays correct under timeouts, duplicate callbacks and partial failures.

• Idempotency and consistency: duplicate-request handling and idempotent distributed operations that never double-charge or double-refund.

• Async and event-driven pipelines: webhook delivery, reconciliation feeds and background workflows on queues/streams.

• Internal and merchant-facing APIs used by merchants, internal teams and payment providers.

Production Ownership

• Own features across the full cycle: design, development, testing, deployment, monitoring and debugging in production.

• Run root-cause analysis for latency spikes, transaction failures and incidents, and ship permanent fixes instead of patching symptoms.

• Profile and optimize CPU, memory, I/O, network and database usage; remove bottlenecks before they become outages.

• Build observability into everything you ship: structured logs, metrics and traces tied to transaction IDs.

Requirements

What You Bring (Must-Have)

• 3–6 years of backend engineering with professional Rust experience in production.

• Solid command of ownership and borrowing, lifetimes, traits and generics, error handling, memory management, and async/concurrent Rust.

• Experience building REST APIs or distributed services, and sound database fundamentals (PostgreSQL, Cassandra and Redis preferred: transactions, isolation, indexing, query tuning).

• Good grasp of Linux and networking (TCP, HTTP/TLS, DNS, timeouts, connection pooling).

• Strong debugging and problem-solving skills, and the habit of reasoning about failure modes first.

Good to Have (Tech)

• Tokio, Axum or Actix-web

• Redis, Kafka / RabbitMQ / NATS

• Docker and Kubernetes; GCP or AWS

• OpenTelemetry, Prometheus, Grafana, distributed tracing

• Go or Python for tooling and integrations is an added advantage

• Open-source contributions or performance write-ups

Good to Have (Payments)

• Payment gateways, orchestration and acquirers

• Authorization / capture, refunds / reversals

• Webhooks and reconciliation

• Idempotency and retry design

• HMAC, AES, API authentication, PCI-DSS concepts

• UPI / card network flows

You Will Thrive If You

• Think deeply about the problem rather than only implementing the ticket.

• Are comfortable working close to the infrastructure and the metal when needed.

• Care about correctness and reliability when money is moving.

• Enjoy chasing down a hard production bug to its root cause.

• Learn unfamiliar parts of a system quickly and take ownership.