WhatsApp usernames: what changes, and what doesn't, for checking a number

WhatsApp usernames let people start chats without showing their phone number to new contacts, but every account is still registered to a phone number. So checking whether a number is on WhatsApp keeps working. What changes is that a business may not see a new customer's number on first contact, so match customers by identifiers they gave you with consent.

The facts below come from Meta's announcement (29 June 2026), Meta's developer documentation and Rest of World's report on India, all linked and fetched on 26 September 2026. WhatsApp is named descriptively; MobileValidate is not affiliated with WhatsApp or Meta.

#What are WhatsApp usernames, and when do they launch?

A username is an optional handle you can share instead of your phone number. Meta opened reservations on 29 June 2026: "Starting this week, you can reserve a username to use later this year when we launch this feature" (Meta, 2026). You reserve one in Settings > Account > Username.

Key points from the announcement:

• Number hidden on first contact. "When you message a person or business for the first time they will no longer see your phone number, if you enabled your username."
• Optional username key. An extra code "that others will need to know to message you", to cut unwanted messages.
• No directory. "There's no directory to browse and no suggestions – people will need to know your exact username."
• Gradual rollout. Meta will roll usernames out "gradually over the coming months" and notify people in WhatsApp "when they're available in your country".
• Reserved handles. Creators, small businesses and organizations can claim their existing Instagram or Facebook username.

As of 26 September 2026, Meta had not announced a general launch date.

Timeline:

#Do WhatsApp accounts still need a phone number?

Yes. A WhatsApp spokesperson told Rest of World that "users still require a phone number to use WhatsApp" (Rest of World, 2026). Meta's own announcement describes the username as something that hides the number from new contacts, not something that replaces it.

That distinction matters. A username changes what other people see. It doesn't change how the account is registered. The account is still created and verified with a phone number, and it still belongs to that number.

#Does a WhatsApp number check still work?

Yes, because it answers a different question. A number check asks: does this phone number have a WhatsApp account? Usernames don't change that answer. They only change whether the number is shown to people the user messages first.

What a check returns stays the same:

Here is the same test-mode request as before usernames, using documented test numbers:

curl https://api.mobilevalidate.com/v1/lookup \
  -H "Authorization: Bearer $MOBILEVALIDATE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"numbers": ["+447700900001", "+447700900002", "+447700900003"], "checks": ["whatsapp"], "wait": 5}'

…001 answers registered: true, …002 registered: false, and …003 registered: null (unknown), each conclusive answer with a checked_at time. Nothing in the response mentions usernames. It never did, because the check never returns profile data.

What we won't do. There is no "find someone's username from their number" feature, and there won't be. Mapping a number to a username, name or profile is a reverse lookup, which we exclude. Usernames are designed to stop strangers from reaching people through their numbers. A tool that undid that would work against the feature and against the people it protects.

#What changes for businesses messaging customers?

Businesses may see customers without seeing their numbers. Meta's developer docs describe business-scoped user IDs (BSUIDs) (Meta for Developers, 2026):

• A BSUID looks like a two-letter ISO country code, a period and up to 128 alphanumeric characters (the docs' example is US.13491208655302741918). It is scoped to your business portfolio, so another business sees a different ID for the same person.
• When a user with a username messages you, the phone number "will not be included in webhooks, unless you have interacted with the user before". The docs define that as a message or call either way within the last 30 days, checked per business phone number, or the user being in your contact book.
• Webhooks carry the BSUID in user_id, and username if the user has one. wa_id is left out when the phone number isn't available.
• Meta said its APIs would support sending to BSUIDs from July 2026. After that you can message users by BSUID, phone number or both. One-tap, zero-tap and copy-code authentication templates still need the phone number.
• A business that adopts a business username still shows its phone number in the app.

What changes and what doesn't, for senders:

#Why did India object to usernames?

Rest of World reported on 13 July 2026 that the Indian government "has objected to the feature" (Rest of World, 2026). Its concern, as reported, was that "pseudonymous accounts could make it easier for bad actors to impersonate others and carry out scams and financial fraud". The government asked WhatsApp, Telegram and Signal to respond by 9 July, and WhatsApp reportedly sent a written response. The article's summary says the government "forced Meta to halt its global WhatsApp username rollout in its largest market".

Be careful with the details. The article refers to a "public notice" but doesn't publish the document, and we found no Meta statement confirming a halt in India. WhatsApp told Rest of World that usernames were "not yet live" and would "roll out slowly later this year". The company also said it would limit how many new people an account can contact and block repeated attempts to guess someone's username key.

For planning, assume usernames will arrive at different times in different countries, and possibly not in India for some time. Build flows that work both ways.

#Do usernames reduce spam and scams?

They are designed to cut unwanted contact, but they also bring new risks, which is the argument India's government made. On the protective side, Meta lists three controls (Meta, 2026): an optional username key that senders must know, no directory to browse, and no username suggestions. WhatsApp also told Rest of World it will limit how many new people an account can contact and block repeated guessing of username keys.

On the risk side, a handle can imitate a brand or a person more easily than a phone number can. That was the Indian government's concern, as reported. For businesses, this means brand protection work: reserve your business username early (Meta lets businesses claim their Instagram or Facebook handle), and tell customers which handle and which number you really use.

Account security is changing at the same time. On 25 August 2026 Meta announced that two-step verification moves from a six-digit PIN to a full password, plus support for multiple passkeys (Meta, 2026). None of this changes what a number check returns.

#What should I change in my sign-up and support flows?

Mostly small things. You don't need to replace phone numbers.

1. Keep collecting the number where you need it, with a clear purpose and consent. Sign-up, delivery and account-recovery flows still rely on it.
2. Store the BSUID next to the customer record when a chat arrives. Treat it as a separate key, not a replacement for the number.
3. Match on what the customer tells you. If a new chat arrives without a number, ask for an order reference or the e-mail address on the account instead of guessing. Meta's docs also describe a request-contact-info button that lets the user choose to share their number.
4. Don't try to unmask users. Don't build tools that turn a username or BSUID back into a number, and don't buy them.
5. Keep number checks where they belong. Use them before sending to numbers you already hold, for example to choose between WhatsApp and SMS for a one-time code. The channel selection flow is unchanged.
6. Update webhook parsing. Handle a missing wa_id and read user_id and username when present. A handler that assumes wa_id always exists will fail on the first username chat.

Our privacy checklist for phone and e-mail checks covers consent and retention for the numbers you keep.

#What are the key takeaways?

• WhatsApp usernames hide a user's phone number from new contacts. Reservations opened on 29 June 2026, with a gradual, country-by-country launch "later this year".
• Accounts still require a phone number, so a WhatsApp number check keeps answering registered, not registered or unknown as before.
• On the Cloud API, first-contact webhooks from username users may carry a business-scoped user ID and username instead of the number.
• India's government objected to usernames, and Rest of World (13 July 2026) summarised this as a halt of the rollout in India. Plan for different timing by country.
• We don't offer number-to-username lookups, and you shouldn't build them. Match customers on identifiers they gave you.