How I designed the system of record for customer balances on a Go payment platform serving 1.8M+ users at 300+ TPS.
A fintech serving 1.8M+ users needed a payment platform whose record of customer balances could be trusted completely, while payments flowed at 300+ transactions per second.
The ledger is immutable and is the system of record for customer balances. It supports atomic multi-entry postings, reversals, reconciliation, a full audit trail and point-in-time balance reconstruction.
Payment workflows are event-driven on AWS SNS/SQS and PostgreSQL. Consumers are idempotent, which gives exactly-once business semantics.
Each payment moves through the same stages: validation, pricing, ledger posting, notifications and events.
I owned the architecture and delivery, led architecture reviews and production releases, and set backend engineering standards.