Industry
Finance & Fintech software.
Financial systems have one property most software does not: being wrong is unrecoverable. A double-charged customer or a ledger that does not balance is not a bug to fix next sprint. That pushes architecture toward immutability and explicitness over convenience.
What shapes the architecture
Constraints that are specific to this sector.
These are the things that would be wrong or meaningless if written about a different industry. They are design inputs, not compliance paperwork added at the end.
- 01
Double-entry, not a balance column
A mutable balance field cannot be audited or reconstructed. An append-only ledger of paired entries can, and balances become a derived projection.
- 02
Idempotency on every write path
Networks retry. Without idempotency keys enforced at the storage layer, a retried payment is a second payment.
- 03
PCI scope is something you shrink
The cheapest compliance strategy is to never hold card data. Tokenise at the edge so the cardholder data environment stays as small as possible.
- 04
Reconciliation is a first-class feature
Your ledger and the processor will disagree eventually. A system without an automated reconciliation path discovers this manually, months late.
Typical work in finance & fintech.
- Ledger and accounting cores
- Payment orchestration and routing
- KYC and onboarding flows
- Lending and underwriting workflows
- Reconciliation and settlement
- Regulatory and statutory reporting
What it has to talk to.
- UPI
- Razorpay
- Stripe
- ISO 20022
- Account Aggregator
Integration surfaces are where most sector projects actually fail. We treat each one as a boundary with its own translation layer, rather than letting an external format leak into the domain model.
Reference build
How we'd build it, decisions included.
An illustrative architecture for this sector — the problem, the approach, and the alternatives we rejected with reasons.
Other sectors
Explore the rest.
Start here
Tell us the problem.
We'll be honest about the fit.
A first conversation costs nothing and is useful even if you go elsewhere — you'll leave with an architecture opinion and a realistic sense of scope.
- Reply within 24 hours
- No sales sequence