Fampay.
Building for younger users means the compliance work is harder, not easier.
- Client
- Fampay
- Sector
- Fintech
- Scope
- App + web + admin
- Stack
- TypeScript, Node.js, React
A fintech product across app, web and an internal admin console, covering onboarding, spending and the controls behind it.
What made it hard.
Ledgers must balance to the cent across providers, currencies and retries. Approximate is the same as wrong.
Onboarding compliance
KYC and AML checks have to satisfy regulation without becoming the reason users abandon signup.
Provider dependency
Payment rails fail in ways you do not control. The system has to degrade without losing money.
Audit expectations
Regulators ask what happened on a specific date to a specific account. The answer has to take minutes.
What we shipped.
A fintech product across app, web and an internal admin console, covering onboarding, spending and the controls behind it.
How it holds up.
Double-entry from the first commit, idempotency on every money-moving endpoint, and a reconciliation job that runs whether or not anyone is watching.
The systemCard and ledger events are append-only, so a balance can always be reconstructed from what actually happened.
Theirs, from day one.
Repositories, cloud accounts and documentation sat with the client throughout. Senior engineers wrote the production code rather than specifying it.
Ask for the full metrics on a call →How Fampay is built.
The stack, layer by layer, from what customers touch to the infrastructure underneath.
More fintech work.
All 42 case studies →Building something like Fampay?
Tell us what you are building. A senior engineer replies within one business day. NDA on request.