The Full Pay-by-Alias Journey: Lookup to Settlement
We have covered the pieces — aliases, verification, resolution, routing, receipts. Now let us walk one payment through all of them, from the moment a sender types a handle to the moment funds land. Seeing the full pay-by-alias journey end to end shows how the parts snap together into something that feels, to the user, like a single tap.
Step 1: The sender names a person
It starts with a handle, not an account number. The sender types @amara, or scans a QR, or taps an SMS request-to-pay link. Whatever the entry point, the input is a friendly alias, not routing details. This is the whole premise of pay-by-alias: name the person, not the plumbing, as we introduced in aliases and proxy lookups.
Step 2: Directory lookup
KibiPay resolves the alias against the directory. It returns not a single account but the set of destinations attached to that identity — perhaps a verified phone, a US bank account, and a Solana wallet — each tagged with a rail and a verification status. Unverified destinations are filtered out, because only proven aliases are payable.
- Resolve the handle to a directory identity.
- Return the candidate destinations and their rails.
- Drop anything unverified or unreachable.
Step 3: Confirmation of payee
Before anything moves, the sender sees the resolved recipient name and confirms it. This is the anti-fraud checkpoint — the sender is agreeing that this is the Amara they meant. A mismatch warns them; a match reassures them. It is the human-in-the-loop step that stops authorised push payment fraud, detailed in confirmation of payee.
Step 4: Smart routing chooses the rail
With confirmed, verified destinations in hand, the routing engine scores each viable rail on cost, speed, and reach, and picks the best one for this specific payment. A small, urgent transfer to a phone leans Mojaloop; a large routine payout leans ACH; a domestic instant transfer leans FPS; a crypto-native counterparty leans Solana.
| Stage | Owner | Output |
|---|---|---|
| Lookup | Directory | Candidate destinations |
| Confirm | Sender | Approved recipient |
| Route | Engine | Chosen rail + fallback |
| Settle | Rail | Funds delivered |
Step 5: Settlement on the chosen rail
Now the selected rail does its work. Mojaloop runs its lookup-quote-transfer with a two-phase commit; ACH submits into a batch; FPS clears in seconds; Solana confirms on-chain. Each rail has its own mechanics, but the sender saw none of them — they confirmed a name and tapped send. If the top rail fails, routing falls back to the next candidate rather than bouncing the payment.
Step 6: The recipient gets a receipt
The instant settlement completes, a live SMS receipt tells the recipient they were paid — amount, sender, reference, timestamp. The loop closes: the sender named a person, the platform did the routing and settlement, and the recipient got an immediate, trustworthy confirmation.
The journey as a whole
Six steps, one tap. Everything between "I typed a handle" and "they got a text" — resolution, verification gating, name confirmation, rail scoring, settlement — is complexity KibiPay absorbs so the user does not have to. That is what pay-by-alias really is: a lot of careful machinery in service of a payment that feels effortless. For the catalogue of rails behind step five, see the rails.
What the sender never sees
The measure of this whole journey is how little of it reaches the sender. They do not see the account-lookup call, the fee quote, the two-phase commit, the ACH batch window, or the fallback logic that fires when a rail misbehaves. They see a name, an amount, and a confirmation. Every layer we have described exists to keep that surface calm while doing serious work underneath. When something does need the sender's attention — a name that does not match, a payment that failed cleanly — the platform surfaces exactly that and nothing more. Good payments infrastructure is defined as much by what it hides as by what it does, and pay-by-alias is a long exercise in hiding the right things.
Name the person, confirm the name, and let the platform settle on whichever rail wins — from lookup to settlement, that is the whole journey in a sentence.