From Email to @Handle: A Payable Directory Identity
Email addresses are precise but clumsy to say out loud and easy to mistype. Handles — the @name form popularised by social apps — are short, memorable, and unambiguous when spoken. Giving every registered user a handle turns the act of signing up into the act of becoming payable. That is the quiet upgrade behind a directory identity.
Why a handle beats a raw email for payments
An email works as an alias, but a handle is friendlier at the point of payment. It is shorter to type, cleaner on a QR code, and less likely to leak a real address you would rather keep private. Crucially, a handle is a public identity by design, whereas an email often doubles as a login secret people are wary of sharing.
- Memorable:
@amarais easier than a full email to recall. - Speakable: you can tell someone your handle across a table.
- Private: sharing a handle need not reveal your email or bank.
How registration mints an identity
When a user verifies their email — for instance via a magic link — KibiPay creates a directory entry and assigns or lets them choose a handle. From that moment, the handle is resolvable: anyone can look it up and be handed the user's payable destinations. Registration and addressability become the same event, with no extra setup step.
| Step | Result |
|---|---|
| Verify email | Identity is authenticated |
| Create directory entry | User becomes lookup-able |
| Assign @handle | Friendly public identity exists |
| Attach aliases | Phone, bank, wallet become payable |
Uniqueness and squatting
Handles are a namespace, and namespaces attract squatters. A directory has to enforce global uniqueness, reserve obviously sensitive names, and decide what happens when someone wants a handle that is taken. Getting this policy right early avoids painful migrations later, because a handle people have shared is expensive to change.
The handle as a hub
The real power is that the handle becomes a hub for every other alias. Resolve @amara and you can reach whichever destination is verified and reachable — phone, bank, or wallet. The handle does not replace those addresses; it points at them, so the person can change banks or add a wallet without reprinting a single business card.
Where it connects
An @handle is the front door of the directory; the rooms behind it are the typed aliases we cover in addressing a payment. In KibiPay, giving everyone a handle is what makes "pay anyone by name" more than a slogan — it is the identity layer the routing engine resolves against.
Handles as portable reputation
Once a handle is stable, it can accrue meaning. A recipient who has been paid many times, whose name has been confirmed again and again, becomes a handle payers recognise and trust on sight. That portability is powerful: the identity travels with the person even as their underlying accounts change, so a plumber who switches banks keeps the handle their customers already know. It also raises the stakes for recovery — if someone loses access to the email behind their handle, they must be able to prove they are the rightful owner and reclaim it, without ever letting an impostor hijack a trusted identity. Designing that recovery path carefully is part of treating a handle as the durable public identity it is meant to be, not a disposable username. The same care applies to changing a handle: because people share and save handles, a change should be rare, deliberate, and ideally leave a forwarding trail so payments aimed at the old name are not simply lost. A handle is an asset, and assets deserve lifecycle rules.
Turn a verified email into a spoken, shareable handle, and paying someone becomes as easy as knowing what to call them.