LAGOS, NG
Verify Nigerian student status in real time.
Institutions maintain the record. Platforms verify through one API. Students control who sees their data, and can see every check made against them.
Studentship is confirmed on paper, and paper is slow and forgeable.
A student ID is printed plastic. It costs less to forge than the account it opens, and nobody at the counter has any way to check it against the institution that issued it.
A bona fide letter means a queue at the registry, a signature from someone who is travelling, and a wait — for a fact the institution already holds in a database.
Nobody tells a bank when a student graduates. The student account, the concessionary loan, the discounted data bundle — all of it keeps running on a fact that expired two years ago.
Three parties. One record.
Registries upload their student list and process graduations, progressions and withdrawals. The record stays theirs — Bona never becomes its owner, and an institution can take its data out on the day it decides to.
Banks, NELFUND, telcos and scholarship boards ask one REST endpoint instead of phoning a registry. The answer comes back scoped to the tier they were approved for, and to what the student agreed to share.
Nothing leaves the record without the student agreeing to it, field by field, with the real values shown before they decide. Every check made against them appears in their app, and any grant can be revoked.
No party can act alone: the institution cannot share a field the student has not consented to, the platform cannot read outside its tier, and Bona never becomes the owner of the record. That is the whole design — three parties who each hold one piece of the permission.
Status expires on its own.
Nobody declares a status in Bona. Every enrolment carries a completion date computed from entry date plus programme duration, adjusted by direct-entry credit and by every strike and closure the institution has declared. A student still enrolled past that date files a re-validation, and a named person at their institution reviews it. The arithmetic is visible to everyone it affects.
Past her expected completion date and inside the three-month grace period. Her institution has until 31 October 2026 to confirm she is still enrolled.
Every date shown anywhere in Bona is explainable by a trace like this one, down to the circular number behind the adjustment. It is what a student contesting a status, a registrar reviewing a re-validation and a bank auditing a lending decision are all actually asking for.
curl https://api.bona.ng/c/NS-TEST-0001-AAAM # The same record behind a key, with consent-scoped fields: curl https://api.bona.ng/v1/verify/NS-TEST-0001-AAAM \ -H "Authorization: Bearer bona_test_…"
{
"status": "…",
"institution": "…",
"programme": "…",
"level": …
}Attestation — enrolled or not, and where — needs no consent and no key. Everything past that does: a student grants fields, not scopes, and the grant is checked live on every call, so a revocation takes effect immediately rather than at the end of a cache window.
Onboarding takes about three weeks, most of it ours, and the first upload is a spreadsheet you already have. Bona costs the institution nothing.
Start onboarding →A landlord, a shop, a small employer. No account and no integration — just the student’s NSID and ₦500.
Open Quick Verify →