The Indian government has ordered Meta to halt the rollout of WhatsApp's new username feature due to concerns over fraud and impersonation [1, 2].

This intervention marks a significant clash between the Ministry of Electronics and Information Technology and one of the world's largest messaging platforms. The dispute centers on whether the ability to use usernames instead of phone numbers creates new vulnerabilities for phishing and scams in a market with millions of mobile users [1, 3].

Authorities in India said that the feature could be exploited by bad actors to deceive users through impersonation [2, 5]. The government has demanded that Meta provide clarifications regarding the functionality and security of the feature within three days [4].

WhatsApp responded by stating that the username system is intended to be optional and is not searchable [3]. The company said that it has already implemented security measures to mitigate the risks identified by the government.

"The feature is optional and not searchable, and we have built safeguards that will prevent scams and impersonation," a WhatsApp spokesperson said [3].

Despite these assurances, the Indian government maintains that more robust safeguards are necessary before the tool can be used widely across the country [1, 5]. The Ministry of Electronics and Information Technology continues to monitor the situation as it awaits the company's formal response [4].

Meta has previously faced regulatory scrutiny in India over data privacy and content moderation. This latest conflict highlights the ongoing tension between global tech deployment and national security mandates, specifically regarding how users are identified and contacted on encrypted platforms [1, 2].

The Indian government has ordered Meta to halt the rollout of WhatsApp's new username feature.

This standoff reflects India's increasingly aggressive stance on digital sovereignty and consumer protection. By pausing a global feature rollout, the Indian government is signaling that platform-wide updates must align with local security concerns regarding phishing and fraud, potentially forcing Meta to create region-specific versions of its software to satisfy national regulators.