<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/how-whatsapp-upgraded-to-secure-seamless-sign-in-for-1-billion-users-with-passkeys-igqy5lpy0" -->

---
title: How WhatsApp Upgraded to Secure, Seamless Sign-In for 1...
description: WhatsApp shares an engineering deep-dive on rolling out passkey-based authentication to over a billion users. The piece covers why WhatsApp adopted passkeys in...
canonical: https://daily.dev/posts/how-whatsapp-upgraded-to-secure-seamless-sign-in-for-1-billion-users-with-passkeys-igqy5lpy0
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: How WhatsApp Upgraded to Secure, Seamless Sign-In for 1 Billion Users with Passkeys | daily.dev
og:description: WhatsApp shares an engineering deep-dive on rolling out passkey-based authentication to over a billion users. The piece covers why WhatsApp adopted passkeys in...
og:url: https://daily.dev/posts/how-whatsapp-upgraded-to-secure-seamless-sign-in-for-1-billion-users-with-passkeys-igqy5lpy0
og:image: https://api.daily.dev/og/posts/iGQy5lPy0.png
og:image:alt: How WhatsApp Upgraded to Secure, Seamless Sign-In for 1 Billion Users with Passkeys
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# How WhatsApp Upgraded to Secure, Seamless Sign-In for 1 Billion Users with Passkeys

**[Android Developers Blog](https://daily.dev/sources/androiddev)** · 6 min read · 0 upvotes · 0 comments

## Summary

WhatsApp shares an engineering deep-dive on rolling out passkey-based authentication to over a billion users. The piece covers why WhatsApp adopted passkeys in 2023, how the Android Credential Manager API simplified client integration despite OEM and device fragmentation, and how the backend (written in Erlang, calling the Rust webauthn-rs library) handles WebAuthn registration and authentication ceremonies. It also explains WhatsApp's multi-passkey architecture, its decision to avoid the standard cross-device Bluetooth/QR WebAuthn flow in favor of platform-native passkey storage (Google Password Manager, iCloud Keychain), and recommendations for developers integrating passkeys at scale.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://android-developers.googleblog.com/2026/08/whatsapp-passkeys-secure-sign-in.html>

## Questions this post answers

### How does WhatsApp implement WebAuthn passkey verification on its backend?

WhatsApp's backend is written in Erlang and calls the Rust webauthn-rs library through a native interface to handle signature verification and credential parsing. The Erlang code orchestrates four core entry points paired into Begin/Finish sequences for Registration and Authentication, handling storage, eligibility, rate-limiting, and credential lifecycle logic around the Rust library's cryptographic verification.

_Developers architecting multi-language auth systems can follow ongoing passkey implementation patterns on daily.dev._

### Why did WhatsApp avoid the standard WebAuthn cross-device QR code and Bluetooth flow for passkeys?

WhatsApp found the Bluetooth dependency unreliable and users often confused the WebAuthn cross-device QR codes with the existing WhatsApp Web linking process. Instead, WhatsApp lets users hold passkeys natively within each platform's own credential store, such as Google Password Manager on Android and iCloud Keychain on iOS, and simply generate a fresh passkey when switching platforms.

_Teams weighing cross-device auth tradeoffs can track real-world passkey UX decisions on daily.dev._

### What Android device fragmentation issues did WhatsApp encounter when rolling out passkeys?

WhatsApp hit edge cases across OEMs, Android versions (13 versus 14+), and device configurations like PIN-only versus biometric screen locks. Problems included users without any screen lock set, unexpected exception types, outdated Play Services versions, and inconsistent behavior from underlying credential providers, requiring close collaboration with Google's Android team to resolve.

_Mobile engineers debugging credential provider inconsistencies can follow related fixes on daily.dev._

## Similar posts on daily.dev

- [Supporting passkeys to create a secure and seamless login experience](https://daily.dev/posts/supporting-passkeys-to-create-a-secure-and-seamless-login-experience-uenxzvw0e) · Doordash · 0 upvotes · 0 comments
- [Things I learnt about passkeys when building passkeybot](https://daily.dev/posts/things-i-learnt-about-passkeys-when-building-passkeybot-rw6rlip9s) · Hacker News · 2 upvotes · 0 comments
- [Modernize authentication with passkeys, digital credentials, and more](https://daily.dev/posts/modernize-authentication-with-passkeys-digital-credentials-and-more-nzvsxhett) · Chrome Developers · 1 upvotes · 0 comments

---

Tags: [#android](https://daily.dev/tags/android), [#authentication](https://daily.dev/tags/authentication), [#passkeys](https://daily.dev/tags/passkeys)

[View this post on daily.dev](https://daily.dev/posts/how-whatsapp-upgraded-to-secure-seamless-sign-in-for-1-billion-users-with-passkeys-igqy5lpy0)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"How WhatsApp Upgraded to Secure, Seamless Sign-In for 1 Billion Users with Passkeys","url":"https://daily.dev/posts/how-whatsapp-upgraded-to-secure-seamless-sign-in-for-1-billion-users-with-passkeys-igqy5lpy0","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/how-whatsapp-upgraded-to-secure-seamless-sign-in-for-1-billion-users-with-passkeys-igqy5lpy0"},"datePublished":"2026-08-27T17:18:31.677Z","dateModified":"2026-08-27T19:53:51.169Z","description":"WhatsApp shares an engineering deep-dive on rolling out passkey-based authentication to over a billion users. The piece covers why WhatsApp adopted passkeys in...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/2de4b47fe9e68a870dec41b620f0d487?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/2de4b47fe9e68a870dec41b620f0d487?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Android Developers Blog","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Android Developers Blog","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/a3d55bb1d63c48e7bd91b833eb5c2c3c","url":"https://daily.dev/sources/androiddev"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/how-whatsapp-upgraded-to-secure-seamless-sign-in-for-1-billion-users-with-passkeys-igqy5lpy0","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"android,authentication,passkeys","timeRequired":"PT6M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Android Developers Blog","item":"https://daily.dev/sources/androiddev"},{"@type":"ListItem","position":3,"name":"How WhatsApp Upgraded to Secure, Seamless Sign-In for 1 Billion Users with Passkeys"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/how-whatsapp-upgraded-to-secure-seamless-sign-in-for-1-billion-users-with-passkeys-igqy5lpy0#faq","mainEntity":[{"@type":"Question","name":"How does WhatsApp implement WebAuthn passkey verification on its backend?","acceptedAnswer":{"@type":"Answer","text":"WhatsApp's backend is written in Erlang and calls the Rust webauthn-rs library through a native interface to handle signature verification and credential parsing. The Erlang code orchestrates four core entry points paired into Begin/Finish sequences for Registration and Authentication, handling storage, eligibility, rate-limiting, and credential lifecycle logic around the Rust library's cryptographic verification. Developers architecting multi-language auth systems can follow ongoing passkey implementation patterns on daily.dev."}},{"@type":"Question","name":"Why did WhatsApp avoid the standard WebAuthn cross-device QR code and Bluetooth flow for passkeys?","acceptedAnswer":{"@type":"Answer","text":"WhatsApp found the Bluetooth dependency unreliable and users often confused the WebAuthn cross-device QR codes with the existing WhatsApp Web linking process. Instead, WhatsApp lets users hold passkeys natively within each platform's own credential store, such as Google Password Manager on Android and iCloud Keychain on iOS, and simply generate a fresh passkey when switching platforms. Teams weighing cross-device auth tradeoffs can track real-world passkey UX decisions on daily.dev."}},{"@type":"Question","name":"What Android device fragmentation issues did WhatsApp encounter when rolling out passkeys?","acceptedAnswer":{"@type":"Answer","text":"WhatsApp hit edge cases across OEMs, Android versions (13 versus 14+), and device configurations like PIN-only versus biometric screen locks. Problems included users without any screen lock set, unexpected exception types, outdated Play Services versions, and inconsistent behavior from underlying credential providers, requiring close collaboration with Google's Android team to resolve. Mobile engineers debugging credential provider inconsistencies can follow related fixes on daily.dev."}}]}
```

