For Governments
Sovereign interoperability, deployed under your control
myID Africa enables national authorities to connect existing identity infrastructure to standards-based cross-border verification without creating a central continental database or transferring control of national identity records.
Trust model
Government is the trust layer
Cross-border interoperability cannot be created by an app alone. It requires participating authorities to recognise each other's trust anchors, assurance rules, credential profiles, revocation signals and authorised relying parties through bilateral, multilateral or recognised regional arrangements — such as those within the East African Community and ECOWAS. myID keeps two directions of trust explicit: government-to-government (G2G) exchange between authorities, and business-to-government (B2G) access, where an approved organisation verifies through a national route.
How the system works
One control layer, end to end
proConsul is the control layer for governments and organisations. It issues organisation identity tokens (the Relying Party Identifier, RPID), enforces who-can-see-what policy, maps people to organisations, validates and issues digital credentials, verifies mobile and digital IDs, and monitors risk and abuse — with signing keys held in trustVault.
Deployment
Deploy inside national infrastructure
The myID Government Node runs where you decide — on government cloud or bare metal — and keeps national data local.
- Government cloud or bare metal
- Local PostgreSQL and Redis
- Restricted, read-only national-database connectors
- MOSIP and non-MOSIP integration
- HSM-backed keys and local Vault or KMS
- Air-gapped deployment support
- Local audit, backup and disaster recovery
- No central raw-identity repository
Onboarding
From agreement to active route
B2G access
Govern B2G access through the RPID
An organisation does not become a trusted verifier merely by installing an API client. The responsible authority must approve the organisation and issue its Relying Party Identifier (RPID) — a government-issued authorisation anchor, never a password or API key. The RPID binds the organisation's permitted purposes and claims, provisions its client credentials, and gates activation of the production route.
- Apply
- Review
- Issue RPID
- Enrol client
- Test in sandbox
- Activate
- Monitor
- Suspend or revoke
Use cases
G2G and B2G use cases
- Regional mobility and government-service access
- Cross-border financial onboarding under applicable regulation
- Remittance and payment identity checks
- Education and professional credential verification
- Cross-border trade and authorised business onboarding
- Resident, diaspora and consular service access
- Border or travel facilitation where the competent authorities approve the credential and profile
myID is not a passport and does not by itself grant border entry.
Standards
Open standards and trust
myID Africa is engineered to interoperate with open identity standards so credentials can be issued, presented and verified across systems and borders:
- MOSIP Claim 169
- OpenID4VP and OpenID4VCI
- SD-JWT VC
- ISO/IEC 18013-5 and 18013-7
- ICAO DTC and VDS-NC
- VICAL / RICAL, IACA, CSCA, DSC, CRL and OCSP where applicable
Standards alignment does not imply a certification, regulatory approval or deployment within any national or international trust framework. Each capability is enabled per deployment and confirmed by conformance testing.
Sovereignty
Sovereignty and privacy
- National source data stays under national control
- Only the minimum authorised claims cross a border
- Each government controls its own trust anchors and policies
- Consent and lawful-basis processing are supported as distinct modes
- All relying-party and federation activity is auditable
- Routes can be suspended or revoked locally at any time
Licensing
Deployment and licensing
Governments can download and deploy the platform on their own infrastructure without purchasing a prescribed hardware stack. The first 20,000 billable verification transactions are included by default. Signed licences enable higher volumes and optional services.
console.myid.africa is a live demonstration deployment of the sovereign operator console — the same interface a government team uses to run its own node: data-source connectors, trust anchors, key management, tokenisation and the tamper-evident audit chain. Explore it hands-on; it runs on demonstration data only.
Questions
Government FAQ
Does myID replace the national ID system?
No. myID complements a national identity system; it does not replace a national ID, passport or government-issued document.
Does national identity data leave the country?
No. Raw national records remain inside the government-controlled deployment. Only the minimum signed claims needed for an authorised transaction cross a border.
Can it integrate with MOSIP?
Yes. MOSIP Claim 169 is a first-class profile, and the node can consume approved attributes through supported MOSIP interfaces or an authorised local database integration.
Can it integrate with a non-MOSIP database?
Yes. Read-only connectors map an existing national register to a local canonical model, without requiring MOSIP.
Who controls keys and trust anchors?
The government does. Production keys are HSM-backed and non-exportable; trust anchors and policies are configured and held locally.
Can an organisation connect directly?
Not for production. An organisation must be approved by the responsible authority and issued an active RPID before it can use a production verification route.
What happens if no bilateral or recognised trust arrangement exists?
The cross-border request is rejected and audited. A route exists only when an active agreement and verified trust anchors are in place.
Is a hardware HSM required?
For production, yes — software HSM is permitted only in development and conformance modes, and is clearly labelled as non-production. Hardware is not supplied free unless a contract says so.
Can the system run without Internet access?
Yes. An air-gapped deployment with signed offline trust-bundle and licence import is supported.
How is verification licensed?
The self-deployment package is free and includes the first 20,000 billable verification transactions. Signed licences raise the allowance and enable optional modules.
For Governments
myID Africa enables national authorities to connect existing identity infrastructure to standards-based cross-border verification without creating a central continental database or transferring control of national identity records.
myID Africa does not claim adoption, endorsement or a contract with any government unless separately and verifiably stated.