The Cross-Rail Directory: One Handle, Any Rail
The hardest part of paying someone is usually knowing how. Do they want a bank transfer? A mobile-money push? A crypto wallet address? KibiPay's cross-rail directory dissolves that problem: it maps one handle to any rail, so a single identity can receive money over Mojaloop, mock ACH, Faster Payments, or Solana. The payer just picks the person; the rail sorts itself out. This post explains how the directory works and why one handle across many rails is such a powerful idea.
The problem with rail-specific addressing
Traditionally, every rail has its own way of addressing an account: a sort code and account number here, a routing number there, an MSISDN for mobile money, a base58 string for a blockchain wallet. To pay someone you had to know both their identity and which rail-specific address to use. That is brittle and error-prone. We surveyed these addressing schemes in addressing a payment.
One handle to rule them all
The directory flips this around. Your handle is a single, stable identity. Behind it, KibiPay knows the rail-specific details needed to reach you. When someone pays your handle, the directory resolves it to whatever address is appropriate for the chosen rail, and the money flows. You share one thing — your handle — and it works everywhere. This is the same proxy-directory pattern that national schemes use; we compared several in comparing aliases.
What sits behind a handle
- A phone number for Mojaloop-style mobile money.
- An account and routing number for the mock ACH rail.
- A sort code and account for Faster Payments.
- A wallet address for Solana.
You do not have to expose or even think about these — the directory holds the mapping so payers never see the underlying details. That separation is central to privacy by design.
Resolving, then routing
There are two steps hiding behind "pay this handle." First, resolution: the directory turns the handle into a concrete destination. Second, routing: the orchestrator decides which rail to use given cost, speed, and reach. We cover the routing brain in how the orchestrator picks your rail and the wider smart-routing idea in cross-rail smart routing.
Why cross-rail matters
A cross-rail directory is what lets otherwise incompatible systems interoperate. Mobile money and bank rails and blockchains do not naturally speak to each other; a shared identity layer bridges them. For users, it means you can pay anyone by name regardless of what they bank with. For builders, it means you can add or swap rails without changing how anyone addresses a payment — the handle stays the same. This is the closest thing payments has to a universal address book.
Uniqueness keeps it trustworthy
A directory only works if each handle points to exactly one person and each person's phone or email cannot be claimed by someone else. KibiPay enforces that uniqueness, which we explain in one phone, one identity. Combined with verified aliases, it means the name you look up is really the person you think it is.
Browse the network
The directory is also a place to discover who is reachable. The public network directory lets you browse participants by handle and display name — safely, without exposing anyone's private details. We describe that experience in the network directory.
See one handle, many rails in action
Adding new rails without breaking anything
One quiet superpower of a handle-based directory is that it decouples who from how. Because payers only ever address your handle, the set of rails behind it can grow or change without anyone updating their address books. Add a new rail tomorrow and existing handles can start using it immediately; retire one and payments simply route elsewhere. In a world where the map of payment rails is constantly shifting, that stability is priceless — the identity layer stays put while the plumbing underneath evolves freely.
In short, the directory is the connective tissue of a multi-rail network. It gives every participant a single, durable name and quietly holds the map from that name to every rail that can reach them. Payers get simplicity, builders get flexibility, and the rails underneath are free to change without anyone noticing. That is what makes one handle across any rail more than a slogan — it is the architecture that lets otherwise incompatible payment systems behave, from the outside, like one.
Open the KibiPay app, look up a handle in the directory, and send a payment — then try again over a different rail to the same handle. It just works. For a guided first run, follow the two-minute walkthrough, and find more on the KibiPay blog.