KibiPay
HomeBlog › Privacy

Privacy by Design: Why the Directory Hides Your Numbers

7 min read Privacy
PrivacyDirectorySecurity
Privacy by Design: Why the Directory Hides Your Numbers

There is a tension at the heart of every payment directory: to be paid, people need to find you — but you should not have to broadcast your phone number or bank details to the world to make that happen. KibiPay resolves the tension with privacy by design: the public directory shows a handle and a display name, and never a phone number, email, or account number. This post explains how that works and why it is the right default.

The problem with exposed contact details

When a directory publishes raw phone numbers or account numbers, it becomes a goldmine for bad actors. Numbers get scraped for spam and smishing, account details invite fraud attempts, and the mere fact that "this number is on a payments network" is itself useful to attackers. Convenience for legitimate payers should not come at the cost of exposing users to that risk.

The core idea: resolve, don't reveal

KibiPay separates identity from addressing. Your public identity is a handle; the sensitive addressing details (phone, email, account, wallet) live behind it and are only ever used server-side to route a payment. When someone pays your handle, KibiPay resolves it internally and moves the money — the payer never sees, and never needs, the details underneath. This resolve-don't-reveal pattern is the same one that powers the cross-rail directory.

What is public vs private

Public (in the directory)Private (never shown)
HandlePhone number
Display nameEmail address
Optional photoBank account / routing number
Verified badgeSolana wallet address

Why not just show the phone number?

Some mobile-money systems let you pay a raw phone number, which is convenient but leaks the number to every payer. KibiPay treats the number as a private key to your identity, not a public label. You can still sign up phone-first — see phone-first accounts — but that number stays behind your handle rather than on your public card.

Verification without exposure

Privacy does not mean anonymity. You can prove you control your phone or email through verified aliases, and the directory shows a verified badge — the fact of verification — without revealing the contact detail itself. Payers get trust; you keep privacy. It is the best of both.

Opt-in, always

Being in the public directory is a choice. If you would rather stay unlisted, you simply share your handle directly with the people who need it, as in get paid: share your handle or QR. Privacy by design includes the choice not to be discoverable at all.

Why this is the right default

Good privacy should not require expert configuration. By making "hide the numbers" the built-in behavior rather than an option buried in settings, KibiPay ensures the safe choice is the automatic one. Users cannot accidentally expose their bank details, because there is no toggle that would let them. Designing the safe path as the default path is what "privacy by design" really means.

See it in the directory

Privacy that survives mistakes

The strongest privacy guarantees are the ones a user cannot accidentally undo. Because KibiPay never puts a toggle in front of you that would publish your phone number or account details, there is no setting to misconfigure and no slip that exposes them. The safe state is the only state. This is a deliberate philosophy: rather than trusting every user to navigate privacy controls correctly, the system removes the dangerous option entirely. It is the same reasoning that leads good engineers to make unsafe operations impossible rather than merely discouraged — the best protection is the one you cannot switch off by mistake.

None of this makes the network less useful — that is the whole trick. Payers can still find people, confirm names, and send money with confidence, because everything they legitimately need is public while everything they do not is hidden. Privacy by design is not privacy at the expense of function; it is a careful line drawn so that the network stays open and browsable while the sensitive details that attract abuse never leave the server. Get that line right and users get discoverability and safety together, which is exactly the goal.

Open the public network directory and notice what you can and cannot see about each person — a handle and a name, never a number. Then create your own listing in the KibiPay app and confirm your details stay private. New to KibiPay? The two-minute walkthrough gets you going, and the blog has more.

See it in motion

KibiPay connects UK Faster Payments, Bacs, CHAPS, Mojaloop mobile money, a mock ACH rail and Solana behind one API, with a cross-rail alias directory, ISO 20022 messaging and real-time fraud & AML screening.

Open the live console Directory demo