🚧

Omnichannel Banking (Omniban) is currently in the research and construction phase. This site presents the protocol's vision and architecture.

Powered by Dymmo
Network Participants

Partner Ecosystem A trusted network for a connected Guinea.

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.

Types

The actors composing the network

Settlement

Settlement nodes

Banks and authorized institutions able to confirm, reject, or settle instruments according to local rules and operational agreements.

Distribution

Distribution operators

Field networks, mobile money, and service points supporting the last mile: deposit, notification, assistance, and verification.

API

Fintech integrators

Applications and platforms consuming Omniban APIs to launch financial journeys without rebuilding the trust infrastructure.

Onboarding

A clear path before production

01

Qualification

Validate legal status, network role, use cases, and covered jurisdiction.

02

Sandbox

Access endpoints, webhooks, test scenarios, Omnify signatures, and controlled datasets.

03

Certification

Review security, compliance, proof quality, error handling, and fallback procedures.

04

Production

Progressive activation with limits, monitoring, Ledger logging, and operational support.

Requirements

What a partner receives and respects

Partner certification

Every actor is identified, verified, and authorized before issuing or receiving protocol decisions.

Technical sandbox

Integrators test real flows safely: errors, webhooks, statuses, signatures, and ORE rules.

Agnostic routing

ORE decides from rules and available capabilities, not from a single app or privileged partner.

Ledger audit

Every important event is traceable: who submitted, validated, signed, routed, or changed status.

Partnership

Become a certified protocol actor

A good integration starts with simple scoping: role, jurisdiction, use case, technical requirements, and sandbox timeline.

Join the network