PayIt

Overview

PayIt is a product-style payments clone designed to model how a real digital payments system behaves across users, merchants, and bank-like services.

The goal was not only to reproduce screens. The goal was to build the transaction flow end to end.

What I built

• separate user and merchant experiences
• authentication flows for secure account access
• transaction and payment records backed by Prisma and PostgreSQL
• mock banking APIs to simulate payment initiation and processing
• webhook-based status updates to keep records in sync
• auxiliary backend services to support a more realistic architecture

Architecture focus

This project pushed me to think carefully about state transitions, transaction records, and external event handling.

• Requests must map cleanly to users and merchants.
• Payment attempts must remain traceable.
• Status updates must be reflected consistently across the system.

That combination made the project a strong exercise in both product thinking and backend reliability.

Strong areas demonstrated

• payment and transaction flow design
• webhook-driven updates and state synchronization
• multi-service thinking across frontend and backend boundaries
• shipping a realistic full-stack clone with product depth

Outcome

PayIt is one of the clearest examples of my interest in systems where UI, API design, data modeling, and external-event handling need to work together without gaps.