KibiPay
HomeBlog › Sign-in

Email or Text: Choosing Where Your Sign-In Code Lands

6 min read Sign-in
Sign-inOTPAccounts
Email or Text: Choosing Where Your Sign-In Code Lands

When you sign in to KibiPay, we send you a one-time code to prove you are you. But where should that code arrive — in your email inbox or as a text message on your phone? KibiPay supports both, and the choice is genuinely yours. This post lays out the trade-offs so you can pick the channel that fits how you work, and shows how each fits into the wider passwordless flow.

Two channels, one goal

Whether it arrives by email or SMS, a one-time code does the same job: it confirms that you control a destination we can reach. If you can read the code we sent, you can prove ownership of that inbox or phone number, and that is enough to let you in. The mechanics are identical; only the delivery path changes. For the bigger picture of how this replaces passwords entirely, see creating a KibiPay user with one-time codes.

When email is the better fit

Email shines in a few situations:

The catch with email

Email delivery can be slower, and codes occasionally land in spam. If your code has not arrived in a minute, check your junk folder before requesting a new one.

When text is the better fit

SMS tends to win when you are on the move:

The catch with SMS

Text delivery depends on carrier networks, which can hiccup or delay messages, especially across borders. And a code visible on a lock screen is readable by anyone holding your phone, so lock your device.

A quick comparison

FactorEmailText (SMS)
Typical speedSeconds to a minuteUsually seconds
Best whenAt a desk, multi-devicePhone in hand, on the move
Cross-borderReliableCan be carrier-dependent
History keptYes, in inboxIn messages app

Switching channels

You are never locked in. If your text is slow to arrive, you can fall back to email, and vice versa. Because both channels resolve to the same account, switching does not create a duplicate user — the underlying identity is the same. This ties into how KibiPay keeps one identity per person, which we cover in one phone, one identity.

Security notes for both channels

Whichever you choose, the same rules keep you safe: codes expire quickly, work only once, and should never be shared with anyone — KibiPay staff will never ask you to read a code aloud. Because the code is single-use, even if someone glimpses an old one it does them no good. That single-use property is the heart of why one-time codes are safer than passwords, explained in why passwordless one-time codes are good UX and security.

Pick one and get started

A note on international sign-in

If you are testing across countries, the channel choice matters more than usual. SMS delivery can vary with local carriers and roaming, and some networks throttle automated messages. Email sidesteps all of that, arriving the same way no matter where you are. For that reason, many people testing global flows default to email and keep SMS for the local, phone-in-hand experience. Whichever you use, remember the underlying account is the same — you are choosing a delivery path, not creating a different identity, so you can move between channels freely without fragmenting your history.

There is no wrong answer — many people use email at their desk and SMS on their phone, depending on the moment. Open the KibiPay app, enter whichever destination suits you, and your funded demo wallet is a code away. For the full first-run experience, follow the two-minute walkthrough, and browse more on the blog.

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