Settlement nodes
Banks and authorized institutions able to confirm, reject, or settle instruments according to local rules and operational agreements.
Region & Language
·
Omnichannel Banking (Omniban) is currently in the research and construction phase. This site presents the protocol's vision and architecture.
Omniban brings banks, operators, institutions, and integrators around a shared protocol: verifiable identity, signed instruments, ORE routing, and Ledger audit.
We aim to progressively cover Africa, then corridors beyond, after a solid validation of the model in Guinea with certified partners.
Banks and authorized institutions able to confirm, reject, or settle instruments according to local rules and operational agreements.
Field networks, mobile money, and service points supporting the last mile: deposit, notification, assistance, and verification.
Applications and platforms consuming Omniban APIs to launch financial journeys without rebuilding the trust infrastructure.
Validate legal status, network role, use cases, and covered jurisdiction.
Access endpoints, webhooks, test scenarios, Omnify signatures, and controlled datasets.
Review security, compliance, proof quality, error handling, and fallback procedures.
Progressive activation with limits, monitoring, Ledger logging, and operational support.
Every actor is identified, verified, and authorized before issuing or receiving protocol decisions.
Integrators test real flows safely: errors, webhooks, statuses, signatures, and ORE rules.
ORE decides from rules and available capabilities, not from a single app or privileged partner.
Every important event is traceable: who submitted, validated, signed, routed, or changed status.
A good integration starts with simple scoping: role, jurisdiction, use case, technical requirements, and sandbox timeline.