How the platform works, in the open.
Concepts, product guides and security notes for participants, verifiers and partners. Written the way the institution is built — precise, sourced, and honest about what is live versus what is coming.
Start here
What Miziba is
The institution, the four primitives, and how a single verified event moves money. The mental model before the mechanics.
Who does what
Clients, contractors, verifiers, financiers and the operator — the responsibilities and boundaries of each role.
Fund → verify → release
The end-to-end journey of a milestone or consignment, from escrow to signed verdict to settlement and record.
Core concepts
Signed verdicts
How independent inspection produces the event that unlocks a release.
KYC & registry
How participants are verified and how the registry stays neutral.
Escrow & waterfall
How licensed escrow holds funds and the order in which they release.
The audit record
What is written, why it holds, and who can read it.
Product guides
Trade
The verification gate, the Loading Certificate, and the bank-first settlement waterfall.
Read Trade →Build
Milestone escrow, certified inspection, and the project's permanent record.
Read Build →Developers
API concepts, events and webhooks for partners integrating with Miziba.
For developers →Security & compliance
Licensed custody
Funds held by licensed banking and payment partners under Act 987. Miziba never holds client money directly.
Data protection
Personal and KYC data processed under Act 843 — lawful basis, minimisation, retention limits and subject rights.
Auditability
Append-only, hash-linked records of every money-or-state transition, with separation of duties enforced by design.
Full technical documentation is being written alongside the pilots. Need something specific for a diligence or integration conversation? Ask us directly and we'll share what's ready.