Partner settlement ledger
Hypothetical. Not a client, not a result.
// The problem
A payments company and its partner institutions each keep their own record of transfers and settlements, and month end is a dispute over whose record is right.
// What we would build
A private permissioned ledger where each party runs a node and every transfer and settlement is written once and read by all, with a web console for operations staff. If one party is trusted to keep the record, a shared database is cheaper and we will say so.
// What is in it
- Settled amounts posted to the books in QuickBooks Online, built on the QuickBooks Online API
- A node for the company and for each partner institution
- Transfers and settlements recorded once, with each party's signature
- Breaks flagged the day they happen, not at month end
- A console for operations to investigate and resolve a break
- Exports for auditors and each partner's own systems
// Stack
- Hyperledger Besu (private, permissioned)
- Next.js
- PostgreSQL
- Kafka
- AWS
// estimate
- Build
- ≈ US$164,000 to US$251,000, delivered within 44 weeksCAD 233,300 to 356,800
- Hosting
- ≈ US$492 a monthCAD 700 a month
- Support
- ≈ US$2,500 a monthCAD 3,565 a month
Prices in your currency are estimates from today's Bank of Canada rate. All invoicing is in CAD or USD.
Timeline by milestone
- Discovery
- 2.9 to 3.4 weeks
- Architecture
- 0.4 weeks
- Data mapping and sandbox connection
- 0.4 weeks
- Design approved
- 2.9 to 4.9 weeks
- Core features
- 1.9 to 3.4 weeks
- Full build
- 1.4 to 2.4 weeks
- Devnet
- 4.4 to 7.4 weeks
- Sync built and reconciled in sandbox
- 1.4 to 2.4 weeks
- Testing and fixes
- 0.4 weeks
- Testnet
- 2.9 to 3.4 weeks
- Regulatory reports accepted
- 2.9 to 3.4 weeks
- Controls built and evidenced
- 2.9 to 3.4 weeks
- Readiness review
- 2.9 to 3.4 weeks
- Launch
- 0.9 to 1.4 weeks
- Mainnet
- 0.9 to 1.4 weeks
- Live cutover
- 0.9 to 1.4 weeks
- Hypercare
- 0.9 to 1.4 weeks
- Observation window (auditor)
- 26 weeks
- Auditor report (SOC 2 Type II)
- 4 to 8 weeks
Outside our hands, and added to the calendar
- Sandbox and API access from the vendor
- 1 to 4 weeks
- Readiness review with your auditor
- 6 to 12 weeks
- Booking a penetration tester and their report
- 2 to 4 weeks
How it is paid
- Deposit 20%
- CAD 46,660 to 71,360
- Discovery 1.5%
- CAD 3,499.50 to 5,352.00
- Architecture 4%
- CAD 9,332 to 14,272
- Data mapping and sandbox connection 1.1%
- CAD 2,566.30 to 3,924.80
- Design approved 1.5%
- CAD 3,499.50 to 5,352.00
- Core features 4.5%
- CAD 10,498.50 to 16,056.00
- Full build 3%
- CAD 6,999 to 10,704
- Devnet 12.2%
- CAD 28,462.60 to 43,529.60
- Sync built and reconciled in sandbox 3.3%
- CAD 7,698.90 to 11,774.40
- Testing and fixes 1.5%
- CAD 3,499.50 to 5,352.00
- Testnet 8.1%
- CAD 18,897.30 to 28,900.80
- Regulatory reports accepted 7%
- CAD 16,331 to 24,976
- Controls built and evidenced 7%
- CAD 16,331 to 24,976
- Readiness review 7%
- CAD 16,331 to 24,976
- Launch 1.5%
- CAD 3,499.50 to 5,352.00
- Mainnet 4%
- CAD 9,332 to 14,272
- Live cutover 1.1%
- CAD 2,566.30 to 3,924.80
- Hypercare 1.7%
- CAD 3,966.10 to 6,065.60
- Holdback, 30 days after launch (10%)
- CAD 23,330 to 35,680