Double-Entry Ledger
Proper accounting with balanced debit/credit entries. Every transaction creates immutable journal entries that always sum to zero.
A fintech engineering showcase — 9 Go microservices, double-entry ledger, React frontends, and the architecture patterns behind real digital banking.
Architecture
Each service owns its domain, database schema, and API surface. Communication via internal HTTP with circuit breakers.
API routing, auth verification, SSE real-time updates
User registration, JWT authentication, KYC verification
Double-entry accounting with balanced journal entries
Role-based access control, granular permissions
Balance management, wallet lifecycle, fund operations
Peer-to-peer transfers, payment processing, UPI
Fraud detection, velocity limits, risk scoring
Synthetic data generation, test scenario automation
Multi-channel alerts — email, SMS, in-app messaging
Engineering
Every component follows production-grade patterns from real fintech platforms.
Proper accounting with balanced debit/credit entries. Every transaction creates immutable journal entries that always sum to zero.
Secure authentication with role-based access control. Granular permissions, token refresh, and admin/user role separation.
Transaction risk scoring, velocity limits, and fraud detection. Rule-based engine evaluating every financial operation in real-time.
Asynchronous event processing with SSE for real-time updates. Services communicate through events with durable delivery guarantees.
Stack
A carefully chosen stack balancing performance, developer experience, and production readiness.
Explore
Everything is open source. Read the code, explore the docs, understand the decisions.