One Phone, One Identity: How Alias Uniqueness Works

A directory only works if every address points somewhere unambiguous. If two people could both claim the same phone number, paying "that number" would be a coin flip. KibiPay prevents this with a simple, strict rule: one phone or email maps to exactly one identity. This post explains how alias uniqueness works, why it matters, and how it underpins trust across the whole network.

The collision problem

Imagine two accounts both registered the same mobile number. When someone pays that number, which account gets the money? There is no good answer — the system would have to guess, and any guess is sometimes wrong. Uniqueness eliminates the question entirely: a given number belongs to one account, full stop. That determinism is what makes alias payments safe to automate, as in paying by alias.

How KibiPay enforces it

When you sign up or add an alias, KibiPay checks whether that phone or email is already bound to an account. If it is, it cannot be claimed again. Combined with the fact that you must prove control of an alias via a one-time code — see verified aliases — this means only the genuine owner can hold a given number, and only one account can hold it. Uniqueness plus verification is a powerful pair.

Why proof of control matters here

Uniqueness without verification would let someone squat on a number they do not own. Verification without uniqueness would let a number be verified by multiple accounts. You need both: the code proves control, and the uniqueness rule ensures that control is exclusive. This is the same one-time-code machinery that signs you in, described in creating a user with one-time codes.

Handles are unique too

The same principle applies to your public handle. No two accounts can share one, so when you pay a handle in the directory, there is exactly one recipient it can resolve to. Display names may repeat — several people can be "Sam" — but the underlying handle disambiguates them, which is why the directory leans on handles, verification badges, and photos to help payers pick the right person. We cover that in the network directory.

Uniqueness and privacy together

Because a number maps to one identity, KibiPay can keep that number private and still route payments correctly — the handle out front, the unique number safely behind it. This is what makes privacy by design workable: uniqueness guarantees that resolving a handle always finds the one right destination without ever exposing it.

Why this prevents fraud

Impersonation often relies on ambiguity — a lookalike account, a claimed-but-unowned number. Uniqueness plus verification closes those doors. An attacker cannot register your number (they cannot receive its code), and cannot create a second account on it (uniqueness forbids it). This complements the transaction-time safeguard of Confirmation of Payee: identity is locked down before a payment even starts.

What it means for you

In practice, uniqueness is invisible when it works — which is the point. You never see a collision, never wonder if your number is being used elsewhere, and can trust that paying an alias reaches exactly one person. It is quiet infrastructure that makes everything above it dependable.

See uniqueness in action

The quiet infrastructure of correctness

Uniqueness is the kind of guarantee you only notice when it is missing. When it holds, paying an alias is boringly reliable: one address, one destination, every time. When it fails, everything above it becomes suspect — you can no longer trust that a lookup found the right person. That is why KibiPay treats it as bedrock rather than a feature. Like a well-chosen primary key in a database, alias uniqueness is invisible when it works and catastrophic when it does not, so the system enforces it rigorously and lets everyone above simply assume it.

So while uniqueness rarely gets top billing, it is doing heavy lifting under everything you see. Directory lookups, alias payments, verification badges, and privacy all lean on the simple promise that one number means one person. Guarantee that, and the whole network above it can be built with confidence. Break it, and none of the conveniences stacked on top can be trusted. It is a small rule with an enormous blast radius, which is exactly why KibiPay enforces it without exception.

Try adding an alias in the KibiPay app and note that a number already in use cannot be claimed twice. Then look up handles in the directory and see how each resolves to one person. New here? Start with the two-minute walkthrough, and browse more on the blog.