Chanzelu

A shared register check, not a shared record.

Banks, MFIs and mobile money operators ask the same question of three registers: does the name on this application match the name someone else already holds. Signing in puts that question, and everything it returns, against your name in the audit trail.

IdentityWork email and password, checked against your institution's staff list
Session8 hours from sign-in, then it ends regardless of activity
RolesOperator runs checks and reads history. Read only reads history alone
RecordedEvery sign-in, sign-out and check, against your name
Data heldYour session and what you did. Never the customer's name or identifiers

Mphando Technologies Limited · Lusaka
Data Protection Act No. 3 of 2021

Sign in

API credentials do not belong in a browser: a client ID and secret are for machine-to-machine calls.

Set a password

This link is single use. Choosing a password here opens your first session.

Connect with API credentials

For testing machine-to-machine access, not for a person signing in.

Your institution's credentials. The secret is exchanged for a one-hour token and kept in this tab only.

Chanzelu verification console

Work
Institutionnot connected
Tokennone
Signed in as
Role
Institution
Queue
not connected

Queue

Every check your institution has run. The row is permanent. The detail behind it, the names and the reasons, was never stored: it went to you at the time and lives in your own file.

New check

Enter what the customer gave you. Do not tidy the spelling: the near misses are the signal, and the matcher scores them rather than rejecting them.

Choose what to check

The reference and actor are the only things about this check that outlive the tab, so keep them opaque. A name in either puts personal data into a store built not to hold any.

You are recorded as the actor on this check. Your reference is the only thing about it that outlives the tab, so keep it opaque. A name in it puts personal data into a store built not to hold any.

Give an NRC or a TPIN. At least one is required.

These are corroboration checks. A match proves the application agrees with what another institution holds, not that any document is genuine. The decision to approve or decline belongs to the caller, not to this service.

Evidence


  

    This payload is what your integration receives. The console renders it, it does
    not add to it.