Skip to content

Hammad Alamgir · Java Backend Developer — Building reliable systems. Solving real problems.

I build secure, reliable backends for banking and payments — currently at Warmbytes.

Portrait of Hammad Alamgir

01About me

Backend engineering for a production banking app.

I'm a Bahria University IT graduate who moved into backend development through two internships — first as a software developer at Lexon IT, then as a Java backend intern at Warmbytes — and now work there as a Java Backend Developer.

Today I build and support Aik Tijarat, a production merchant-banking backend serving mobile and portal clients. It connects to two core banks, card and payment switches and national ID verification, so most of my work sits where security and reliability matter: passkey (FIDO2) login, RSA-encrypted credentials, Redis-based session control, the Aik Khata credit ledger and NFC Tap to Pay.

Alongside features, I handle production deployments and hotfixes, write migration scripts and triage live issues from server logs on UAT and production.

“Good software is not just about writing code. It's about understanding problems, building thoughtful solutions, and creating experiences people can rely on.”

At a glance

Role
Java Backend Developer
Focus
Fintech · payments · banking
Current
Warmbytes
Product
Aik Tijarat · merchant banking
Stack
Java 17 · Spring Boot 3 · Redis
Based in
Islamabad, Pakistan

BS Information Technology

Bahria University, Islamabad

CGPA 3.1 / 4.0

View full CV

02Fintech & payments

Specialised in banking and payment systems.

Most of my work sits inside a production merchant-banking backend — where money moves, identities are verified and every request has to be secure and traceable.

Banking app on Google Play
Live
Core banks connected
2
Modern, secure login
Passkeys
Payments, transfers & Tap to Pay
QR & NFC

How a payment works

Simplified

  1. 01Encrypted PIN

    The app encrypts the PIN (RSA) before it leaves the phone.

  2. 02Login check

    One valid session per user; old or logged-out tokens are rejected.

  3. 03No double payments

    A Redis lock stops the same payment from going through twice.

  4. 04Money sent

    By interbank transfer (IBFT), Raast QR or wallet transfer.

  5. 05Bank systems

    Connected to two core banking systems: iMAL and MicroBank.

  6. 06Alerts & logs

    The customer gets an alert, and every external call is logged with a request ID.

  • Payments & transfers

    Request to Pay, interbank transfers (IBFT) through Euronet, Raast QR payments, wallet-to-core and wallet-to-wallet transfers, bills, top-ups and fee payments.

    • IBFT
    • Raast QR
    • Request to Pay
    • Wallet transfers
  • Banking security

    Passkey (FIDO2) login with an MPIN fallback, RSA-OAEP encrypted MPIN and OTP, a two-device limit and every VAPT finding closed.

    • FIDO2
    • RSA-OAEP
    • JWT
    • VAPT
  • Bank connections

    Onboarding for new and existing customers across iMAL and MicroBank, merchant upgrades with portal approval, and account-lifecycle APIs.

    • iMAL
    • MicroBank
    • Onboarding
  • Cards & Tap to Pay

    The debit card lifecycle — issuance, activation, PIN, block and limits — and onboarding APIs for the NFC Tap to Pay SDK over mTLS with signed requests.

    • Debit cards
    • NFC
    • mTLS
    • JWS
  • Digital credit book

    Aik Khata: customers, transactions, payment allocations, QR collection codes with expiry, credit limits and an overdue-account scheduler.

    • Aik Khata
    • QR collection
    • Scheduler
  • ID checks & data safety

    NADRA CNIC verification, CNIC-expiry checks and reminders, masking of card numbers, mobile numbers and IBANs in logs, and account certificates.

    • NADRA CNIC
    • Log masking
    • Certificates

03Experience

From intern to Java backend developer at Warmbytes.

Three roles across Warmbytes and Lexon IT — from Spring Boot features and REST APIs to building and supporting a production merchant-banking backend.

  1. —

    Current

    Java Backend Developer

    Warmbytes

    • Build and support the production backend of Aik Tijarat, a merchant-banking app serving mobile and portal clients, on Java 17, Spring Boot 3, PostgreSQL, SQL Server and Redis.
    • Built passkey (FIDO2 / WebAuthn) login with an MPIN fallback, RSA-OAEP encryption of MPIN and OTP, and fixes for every VAPT finding.
    • Use Redis for single active sessions, token blacklisting, login lockouts and an atomic duplicate-payment guard.
    • Java 17
    • Spring Boot 3
    • PostgreSQL
    • SQL Server
    • Redis
    • FIDO2
    • REST APIs
    • Postman
  2. Java Backend Developer Intern

    Warmbytes

    • Developed backend features and REST APIs using Java and Spring Boot in a production development environment.
    • Worked with Controllers, Services, Repositories, DTOs, JPA/Hibernate, and SQL databases.
    • Learned and applied backend development practices including API design, validation, exception handling, database integration, and debugging.
    • Java
    • Spring Boot
    • REST APIs
    • JPA/Hibernate
    • SQL
    • Postman
  3. Software Developer Intern

    Lexon IT

    • Developed and maintained web application features and database-driven functionality.
    • Worked with backend APIs, frontend integration, debugging, and application improvements.
    • Collaborated with developers using Git/GitHub and followed Agile software development practices.
    • Web Applications
    • Backend APIs
    • Git/GitHub
    • Agile

04Selected work

Financial, healthcare and academic backends.

A live merchant-banking app in depth — the screens, the problem, my part, the decisions and the result — followed by a diagnostics platform and a hands-on Spring Boot system.

FeaturedFintech · Production

Aik Tijarat

Merchant banking app backend · Warmbytes

Built and supported a production merchant-banking backend serving mobile and portal clients. It integrates with two core banks, card and payment switches, and national ID verification. Highlights are passkey (FIDO2) login, RSA-encrypted credentials, Redis-based session and rate control, a credit-ledger module, and NFC Tap to Pay.

  • Java 17
  • Spring Boot 3
  • PostgreSQL
  • SQL Server
  • Redis

aik Tijarat

Live on Google Play

Sharia-compliant QR payments, money transfers and bill payments for businesses.

View on Google Play

Inside the app

  • aik Tijarat home screen with balance, quick actions and recent transactions
    Home
  • aik Tijarat Generate QR screen showing a merchant's Raast QR code
    QR payments
  • aik Tijarat Send Money screen with aik, bank and Raast transfer options
    Send money
  • aik Tijarat Pay Bills screen with gas, electricity, water and other billers
    Pay bills

01The problem

Aik Tijarat's backend serves mobile and portal clients and has to work with two core banking systems, card and payment switches and national ID verification — while staying secure enough to pass a VAPT security test.

02My contribution

  • Passkey (FIDO2) login with an MPIN fallback
  • RSA-OAEP encryption of MPIN and OTP
  • Redis session, lockout and duplicate-payment controls
  • The Aik Khata credit-ledger module (~4,700 lines)
  • Onboarding APIs for the NFC Tap to Pay SDK
  • Production deployments, hotfixes and migrations

03Key technical decisions

Redis for security state
Single active sessions, token blacklisting and login lockouts live in Redis with expiry, so stale state clears itself.
Atomic duplicate-payment guard
A SETNX check with a time window blocks double payments.
Parallel dashboard loading
CompletableFuture loads dashboard data in parallel instead of one call after another.
Traceable by default
An MDC request ID on every log line and an integration log table for all external calls.

04Outcome

Running in production for mobile and portal clients, with every reported VAPT finding closed and live issues triaged from UAT and production logs.

Engineering deep dive

10 topics

  • Security and authentication

    6 items

    • FIDO2 / WebAuthn passkeys

      Passkey registration and login built on Yubico java-webauthn-server. Challenges expire after a set time, and login falls back to MPIN if the passkey fails.

    • RSA encryption

      The app encrypts the MPIN and OTP with RSA-OAEP (SHA-256) before sending them; the server decrypts and then hashes them. A PKCS#1 variant serves the merchant-service integration, and I handled key rotation on production.

    • Security test (VAPT) fixes

      Closed every reported finding: a hardened JWT filter, the token blacklist, input validation, and masking of card numbers, mobile numbers and IBANs in logs.

    • Partner API security

      An API-key filter and credential check for partner endpoints, kept separate from the JWT flow.

    • Device control

      A limit of two devices per user, plus a lockout for device-registration attempts.

    • Code obfuscation

      Obfuscation of the production build.

  • Redis usage

    6 items

    • Single active session

      One valid token per user.

    • Token blacklist

      Tokens are rejected on logout, and every token is invalidated after a PIN change.

    • Login lockout

      Failed-attempt counters with a lockout that expires after a set time.

    • Onboarding session store

      Sessions for new-customer onboarding, indexed by mobile number.

    • Duplicate-transaction guard

      An atomic SETNX check with a time window, so double payments are blocked.

    • Token and data caching

      OAuth tokens for partner APIs, recents and favourites, and banners.

  • Aik Khata module

    About 4,700 lines · 3 items

    • Digital credit ledger

      Merchants track customers, transactions, line items and payment allocations.

    • QR collection

      QR collection codes with expiry, plus credit limits and status rules.

    • Scheduling and reporting

      A scheduler for overdue accounts, separate reporting APIs, and database indexes for search.

  • Payments and integrations

    7 items

    • Request to Pay

      Aliases, pay now or later, and invoice numbers.

    • QR and Raast payments

      QR inquiry, payment and intimation (payment notification), Raast QR payment, and bulk QR generation.

    • Transfers

      Interbank transfers (IBFT) through Euronet, plus wallet-to-core and wallet-to-wallet transfers.

    • Debit card lifecycle

      Issuance, activation, PIN set and change, block and unblock, and limits.

    • Bills and top-ups

      Mobile top-ups and bundles, bill payments, donations, and fee payments.

    • Identity and language

      NADRA CNIC verification, and Urdu transliteration (AKSA v2).

    • Account certificates

      Withholding tax, account maintenance, and statements.

  • NFC Tap to Pay

    2 items

    • SDK onboarding APIs

      Onboarding APIs for the NFC Tap to Pay SDK.

    • Signed, mutually authenticated calls

      mTLS, OAuth client credentials, detached JWS signatures (ES256), and webhook signature verification.

  • Onboarding and accounts

    4 items

    • Two core banking systems

      Onboarding for new and existing customers across iMAL and MicroBank.

    • Merchant upgrade

      Document upload, with approval in the admin portal.

    • CNIC expiry

      Expiry checks, reminders and the update flow.

    • Account lifecycle

      Account-closure handling and an account-status API.

  • Notifications

    3 items

    • Firebase push notifications

    • Transaction alerts

    • Asynchronous SMS OTP

  • Performance

    4 items

    • Query fixes

      Fixed N+1 queries, and added gzip responses.

    • Parallel dashboard

      The dashboard loads its data in parallel using CompletableFuture.

    • Views and indexes

      Replaced complex portal queries with optimized database views and indexes.

    • Async recents

      Moved recents saving to run asynchronously.

  • Production support and DevOps

    6 items

    • Releases

      Production deployments and hotfix releases.

    • Migrations

      Hand-written migration scripts for UAT, pre-production and production.

    • Configuration

      Moved configuration out to environment variables.

    • Live issues

      Triaged and fixed live issues from server logs on UAT and production.

    • Mock modes

      Built mock modes so QA could test without partner systems.

    • CI/CD

      Tested the CI/CD pipeline.

  • Observability

    3 items

    • Request IDs

      A request ID on every log line (MDC).

    • Integration log

      An integration log table for all external calls.

    • Logging config

      Per-environment logging config, and request/response logging.

  • Healthcare · Diagnostics

    Rahila Labs

    Diagnostic Platform

    Built REST APIs for laboratory test booking, appointments, patient records, and multi-role workflows, integrated with SQL Server and React.js.

    • Python
    • SQL Server
    • React.js
  • Academic · Backend

    University Management System

    Spring Boot Backend

    Hands-on Spring Boot backend applying REST APIs, dependency injection, layered architecture, JPA/Hibernate, entity relationships, DTOs, validation, exception handling and authentication, with CRUD and business logic on MySQL.

    • Java
    • Spring Boot
    • REST APIs
    • MySQL

05Technical profile

Technologies I work with.

Java and Spring Boot at the core, with security, data and integrations around them — the stack behind a live merchant-banking backend.

Core stack

  • Java 17
  • Spring Boot 3
  • PostgreSQL
  • SQL Server
  • Redis
  • Spring Data JPA
  • REST APIs
  • JWT
  • Git
  • Maven
  • Backend

    07
    • Spring Boot 3
    • REST APIs
    • Spring Data JPA
    • Hibernate
    • JDBC
    • Maven
    • CompletableFuture
  • Security

    08
    • Spring Security
    • JWT
    • FIDO2 / WebAuthn
    • RSA-OAEP
    • AES-GCM
    • OAuth 2.0
    • mTLS
    • JWS (ES256)
  • Languages

    05
    • Java 17
    • Python
    • SQL
    • JavaScript
    • C++
  • Data & caching

    04
    • PostgreSQL
    • SQL Server
    • MySQL
    • Redis
  • Fintech & payments

    09
    • Core banking (iMAL, MicroBank)
    • IBFT
    • Raast QR
    • Request to Pay
    • NFC Tap to Pay
    • Debit card lifecycle
    • NADRA CNIC verification
    • Webhooks
    • Firebase push
  • Observability & ops

    05
    • MDC request tracing
    • Integration logs
    • DB migrations
    • CI/CD
    • Hotfix releases
  • Architecture

    04
    • Layered Architecture
    • MVC
    • API Gateway
    • Microservices
  • Tools

    05
    • Git
    • GitHub
    • Postman
    • IntelliJ IDEA
    • VS Code
  • Concepts

    06
    • OOP
    • DSA
    • DBMS
    • SOLID
    • Agile
    • SDLC

06Beyond the code

Beyond the code.

I like understanding how technology works behind the scenes, and I keep challenging myself to get a little better at what I do.

07Contact

Let's build something meaningful.

Have an opportunity, an interesting project, or simply want to connect? I'd love to hear from you.

Send a message