Ledger-first architecture for a partner-bank neobank
How we structure a neobank so that balances always reconcile with the sponsor bank and partners can be added or replaced.
This is a reference architecture describing how Shivacha approaches this class of system. It does not describe a specific client engagement and contains no client names or results.
Challenge
Neobanks built directly on a single BaaS provider's data model struggle to reconcile, add card processors or switch providers, and face scrutiny from partners about the accuracy of their books.
Context
Applicable to fintechs launching accounts and cards through licensed sponsor banks or BaaS providers.
Approach
How we approach it
- 1
Independent ledger
A double-entry ledger owned by the neobank records every movement.
- 2
Provider adapters
BaaS, card processor and KYC providers integrated behind interfaces.
- 3
Idempotent money movement
Every transfer and card event processed exactly once.
- 4
Daily reconciliation
Automated matching against partner statements with exception queues.
Implementation
Key implementation elements
Real-time authorisation
Card auth decisions against ledger balances within processor limits.
Outbox pattern
Reliable event publishing from ledger transactions.
Maker-checker
Dual control for manual adjustments.
Statement generation
Customer statements from ledger data.
Outcome
The architecture is designed so the neobank can always prove its balances, onboard new partners through adapters and pass partner and auditor scrutiny with confidence.
Lessons
- Owning the ledger is what gives a fintech independence from its providers.
- Holds and reversals need as much design attention as settled transactions.
- Reconciliation should run from the first day of production, not after problems appear.
Services
Services involved
Neobank Development
Launch a neobank with a mobile-first experience, modern ledger and licensed banking partners — from MVP to scale.
Learn moreCore Banking Platform Development
Modern core banking components — ledger, product engine, interest, fees and limits — or integration with existing cores.
Learn moreCard Issuing Platform Integration
Integrate card issuing into your product — processor APIs, real-time authorisation, ledgers and cardholder experiences.
Learn morePayment Reconciliation Automation
Automated reconciliation of payments, provider reports, settlements and bank statements — with exception workflows.
Learn moreProducts
Related products
Shivacha Neobank
Launch a mobile-first neobank on a platform built to scale.
Learn moreShivacha Card Management
Technology infrastructure for card-program integrations.
Learn moreShivacha Digital Bank
A configurable digital banking platform for banks and licensed partners.
Learn moreMore work
Other reference architectures
Stablecoin settlement layer for a card-accepting payment platform
A hybrid design that lets merchants accept cards as usual while optionally settling in stablecoins.
Learn morePermission-aware enterprise knowledge assistant
How we design a RAG assistant that answers from thousands of internal documents while respecting every user's access rights.
Learn moreAgentic claims intake with human approval
A reference design for an AI workflow that reads claim submissions, extracts and validates data, and prepares cases for adjusters.
Learn moreNext step
Discuss a similar project.
Building something like "Ledger-first architecture for a partner-bank neobank"? Tell us about your goals and constraints and we will reply with an approach and next steps.
- Senior engineer reads every enquiry
- Reply within one business day
- NDA on request
Your details are used only to reply to this enquiry.