Person verification against Ethiopia’s national ID
Confirm that a real, uniquely identified person is behind a signup — with their consent, in seconds, without ever handling their national identifier.
Verified attributes
Name, birth date, gender and the other claims your account is entitled to — read from the national register at the moment of verification, not typed in by the user.
Assurance and liveness
Every result carries the authentication assurance level and, where the provider supplies it, liveness evidence — so you can treat a strong verification differently from a weak one.
Duplicate detection
The per-tenant identity key is stable, so a person who tries to register twice under different details resolves to the same key — without you storing anything that identifies them nationally.
Provenance you can audit
Each result records the provider, the source and the exact verification time, so you can show a regulator where an attribute came from years later.
Who uses it
| Sector | What Emnet Identity answers |
|---|---|
| Remittance & payments | Is this sender a real, verified person, and is this the same person who registered last month? |
| Banking & microfinance | Can I open this account against verified national attributes rather than a photographed document? |
| Betting & gaming | Is this player over the legal age, and have they already registered under another name? |
| Marketplaces & gig platforms | Is this seller or driver a uniquely identified individual I can hold accountable? |
| Telecom & utilities | Does this subscriber match a verified identity before I activate service? |
What a result looks like
{
"sessionId": 4711,
"identityKey": "3f9c1a0b7e5d4c2a9b8e7f6d5c4b3a29…",
"claims": {
"name": "Yigermal Fantaye",
"birthdate": "1996-04-11",
"gender": "male"
},
"availableClaims": ["name", "birthdate", "gender", "address", "phone"],
"assuranceLevel": "L2",
"livenessEvidence": "PRESENTED",
"provider": "FAYDA",
"source": "esignet",
"verifiedAt": "2026-07-26T09:14:22Z"
}claims holds what was released to you. availableClaims shows what the provider could return for your account, so you can see what you would gain by requesting a broader entitlement — without that data ever being sent to you first.
No Fayda number. No KYC tier, risk score or approval flag. Emnet reports verified facts; turning those into a decision is your product’s job, and keeping it that way is what lets your compliance evidence stay in your own systems.
Integration effort
A working integration is two API calls plus a redirect. Most teams have the test flow running in an afternoon and production behind a feature flag within a week.
- Backend — one endpoint to start a verification, one callback route to finish it. Use the Java SDK or call the REST API directly.
- Frontend — a button that sends the user to the authorization URL, and a landing page for when they come back.
- Storage — persist the identity key and the claims you need, against your own user record.