Portfolio Project
Enterprise Payment Management Platform
A production-style Java/Spring Boot backend — the headline of your portfolio.
Evolved from the Recon reconciliation engine. · Stack: Java 21 · Spring Boot 3 · PostgreSQL · Redis · Docker · GitHub Actions · AWS
🧠 Explain it in one minute
What it is: A backend API for an enterprise payment platform. Organisations onboard, invite users with roles, and submit payment requests that flow through an approval workflow. Every state change is written to an immutable audit trail. Money is stored as long (paise) — never floating point.
Why it exists (the problem): In real payment/enterprise systems, you can't let anyone move money. You need who can do what (roles/permissions), a paper trail (audit), correctness under retries (idempotency + transactions), and proof it works (tests). This project is that problem, built from scratch.
How a request flows: Controller → validation (DTO) → Service (business rules + @Transactional) → Repository (JPA) → PostgreSQL. Auth is a JWT filter in front. Hot reads are cached in Redis. It's containerised with Docker Compose and deployed on AWS.
Your interview line: “I have professional exposure to banking/payment systems and testing, and I transitioned into backend engineering by designing and building a production-style Java/Spring Boot payment platform end to end.”
Milestones
Each feature solves a real problem and maps to a concept you're learning. Tick a feature when it's shipped & tested.