Zeller.
Payments hardware and software fail differently, and both reach the same merchant.
- Client
- Zeller
- Sector
- Fintech
- Scope
- App + web
- Stack
- TypeScript, Node.js, React
A fintech product on app and web for business payments, spanning merchant onboarding, transactions and reporting.
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 on app and web for business payments, spanning merchant onboarding, transactions and reporting.
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 systemSettlement and reporting derive from one transaction record, so what a merchant sees matches what was banked.
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 →More fintech work.
All 42 case studies →Building something like Zeller?
Tell us what you are building. A senior engineer replies within one business day. NDA on request.