Web Dev

Passkeys for Customer Logins: What Changes for Your Website

In this article
  1. Key takeaways
  2. What is a passkey, in plain terms?
  3. What changed for passkeys in 2026?
  4. What results do businesses report after adding passkeys?
  5. What actually changes on your website when you add passkeys for customer logins?
  6. How do you roll out passkeys without locking customers out?
  7. Which fallback and recovery options should you keep?
  8. What should your support team know?
  9. Frequently Asked Questions
  10. Sources

Short answer: Passkeys for customer logins replace the password with a key pair stored in the customer's phone, computer or password manager, using the FIDO2 and WebAuthn standards. For a business website, that means new database fields, a passkey option on the sign-in page, a management screen in account settings, and a fallback and recovery path that is not weaker than the passkey itself.

Key takeaways

  • A passkey only works on the website it was created for, so a fake look-alike page cannot collect it. That is the main reason to adopt it.
  • The standard is settled: WebAuthn Level 3 became a W3C Recommendation on August 25, 2026, and the UK NCSC now tells businesses to offer passkeys to consumers by default.
  • Do not delete passwords on day one. Add passkeys next to the current sign-in, then strengthen the fallback (one-time codes or federation) instead of leaving password-only access.
  • Account recovery and support scripts are where most rollouts fail. Design them before you launch, not after the first locked-out customer calls.

What is a passkey, in plain terms?

A passkey is a sign-in credential made of two keys: a private key that stays with the user's device or passkey manager, and a public key that your server stores. At sign-in, the device proves it holds the private key, usually after the user unlocks it with a fingerprint, face scan or PIN. Your server never receives a secret it could leak.

The technical name for the web part is WebAuthn, and FIDO2 is the wider family of standards it belongs to. The W3C specification says each credential is scoped to one relying party (your site), and only origins that belong to that relying party can use it, per W3C: Web Authentication Level 3 (2026). In practice, a customer who lands on a convincing phishing copy of your portal simply has no passkey to offer it.

Passkeys come in two kinds. Synced passkeys are copied between a user's devices by a provider such as Apple, Google or a password manager. Device-bound passkeys stay on one device or security key. The specification exposes this through a backup eligibility flag that your server can record at registration.

What changed for passkeys in 2026?

Three things moved passkeys from "nice to have" to "expected" this year.

  • The standard was finalized. WebAuthn Level 3 was published as a W3C Recommendation on 25 August 2026, succeeding the 2021 Level 2 edition, according to W3C (2026).
  • A national security agency changed its advice. On 23 April 2026 the UK National Cyber Security Centre said it will recommend passkeys wherever a service supports them, with two-step verification as the fallback, and described all traditional multi-factor methods as phishable, in NCSC: Passkeys are more secure than traditional ways to log in (2026). Its press release asked businesses to make passkeys the default option they offer consumers and said passkey logins can be up to eight times faster than a password plus a code, per NCSC news release (2026).
  • Customers are already using them. The FIDO Alliance estimated about 5 billion passkeys in use on World Passkey Day (May 7, 2026), and its survey of 11,000 consumers in ten countries found 75% had enabled a passkey on at least one account, per FIDO Alliance (2026).

For US public-sector work, NIST's digital identity guidelines (SP 800-63B-4, July 2025) allow syncable authenticators at the AAL2 assurance level but not at AAL3, because syncing exports the key, per NIST: Syncable authenticators (2025). If a contract names an assurance level, check which kind of passkey it permits.

What results do businesses report after adding passkeys?

The best published numbers come from the FIDO Alliance's Passkey Index (October 15, 2026), which pools data from participating companies. Across those participants, 36% of successful sign-ins used a passkey, up from 26% in 2025, and passkey sign-ins succeeded 93% of the time against 78% for traditional multi-factor sign-ins, according to FIDO Alliance: Passkey Index (2026). The same report says every participant that measures phishing saw fewer successful attacks, and every one that shared savings data reported lower SMS one-time-code costs.

Treat these as industry figures from large adopters, not a forecast for your site. They do show where the benefit lands: fewer failed logins, fewer reset requests, fewer paid text messages. The FIDO consumer survey also found 47% of people say they are likely to abandon a purchase or sign-in when they forget a password, per FIDO Alliance (2026), which matters if your login sits in front of a checkout. Our guide to why international customers abandon checkout covers the other friction points.

What actually changes on your website when you add passkeys for customer logins?

The database

Each account can hold several passkeys (phone, laptop, security key). For each one, Google's web.dev guidance suggests storing the credential ID, the public key, a stable user ID with no personal data in it, the AAGUID that identifies the passkey provider, the backup eligibility flag, creation and last-used dates, and a display name, per web.dev: Create a passkey for passwordless logins (2026). Use a maintained open-source WebAuthn server library rather than parsing credentials yourself.

The sign-in page

Modern browsers can offer saved passkeys inside the username field's autofill list, so returning users tap once. Keep the existing sign-in visible for everyone else. If your portal runs on more than one domain (for example a .com and a country domain), WebAuthn's Related Origin Requests let one passkey work across them through a file at /.well-known/webauthn, but the passkeys.dev documentation says to treat five distinct domain labels as the practical maximum, per passkeys.dev: Related Origin Requests (2026).

Account settings

Customers need a page that lists their passkeys, names them by provider, shows when each was last used, and lets them remove one. When a user deletes a passkey on your side, Chrome's Signal API (from Chrome 132) can tell the passkey manager to hide it, per Chrome for Developers: WebAuthn Signal API (2026). Safari and Firefox had not shipped it at the time of writing, so also tell users how to delete it from their password manager.

Notifications

Send an email whenever a new passkey is added. An attacker who briefly gets into an account could register their own passkey, and a password change would not remove it.

How do you roll out passkeys without locking customers out?

  1. Check your audience's devices. The passkeys.dev support matrix lists synced passkeys from iOS 16, macOS 13 and Android 9, with Windows and Linux support depending on version and third-party managers, per passkeys.dev: Device support (2026).
  2. Offer creation at natural moments: right after sign-up, right after a successful sign-in, and on the account settings page.
  3. Verify before you create. web.dev warns against creating a passkey after password-only verification, because a leaked password would let an attacker attach their own passkey. Ask for an email or SMS code first.
  4. Run a pilot. Start with staff accounts or one customer segment, and watch failed sign-ins and support tickets for a few weeks.
  5. Measure and widen. Track passkey sign-in share, success rate and reset requests before you push harder prompts.
  6. Decide later about passwords. Google's passkey developer guide recommends keeping existing sign-in methods for now, per Google for Developers: Passkey developer guides (2026). Remove passwords only for users who have more than one working passkey and a tested recovery route.

For a portal or SaaS product, plan this as a small feature release with its own testing, not a plugin you switch on. The SaaS product development and web application development teams at Alive Inc. scope it that way.

Which fallback and recovery options should you keep?

Your login is only as strong as its weakest route in. If a phishing-proof passkey sits next to a reset link that anyone with mailbox access can use, attackers take the reset link.

Fallback or recovery routePhishing resistanceWhere it fits A second passkey on another deviceHighThe best recovery: prompt users to add one Hardware security keyHighAdmin, finance and high-value accounts Federated sign-in (Google, Apple, Microsoft)Depends on the provider accountConsumer portals that already offer it Authenticator app or email one-time codeLow (codes can be phished)General fallback while passwords remain SMS one-time codeLow, plus per-message costLast resort for users with no other option Password onlyNonePhase out; never use it to authorize a new passkey The NCSC also expects services to give users clear ways to manage and remove credentials and to set up recovery options. A periodic security audit should test the recovery flow as an attacker would, not just the sign-in page.

What should your support team know?

  • "My passkey disappeared." Usually a new phone or a different passkey manager. Guide the user to sign in on another device or through the fallback, then create a new passkey.
  • "It asks for my phone on my laptop." That is cross-device sign-in by QR code. Explain it, and suggest creating a passkey on the laptop too.
  • "Did you get my fingerprint?" No. The biometric check happens on the device; your server receives only a signature.
  • Agents should never add or reset sign-in methods over the phone without the same identity checks your recovery flow uses.

Frequently Asked Questions

Are passkeys safer than passwords plus two-factor codes?

For phishing, yes. A passkey only works on the site it was created for, so a fake page cannot reuse it, while codes sent by SMS, email or an app can be typed into a phishing page. The UK NCSC said in April 2026 that passkeys are as secure as or more secure than traditional multi-factor methods against common attacks.

Do customers need special hardware to use passkeys?

Usually not. Current iPhones, Android phones, Macs and Windows computers can create and use passkeys, and many password managers store them. Older devices and some locked-down corporate machines may not, which is why a fallback sign-in method should stay available during the rollout.

What happens if a customer loses the phone that holds their passkey?

If the passkey was synced through Apple, Google or a password manager, it is restored when they sign in to that account on a new device. If it was device-bound, they need another registered passkey or your recovery process, so encourage every customer to register a second passkey early.

Should we remove passwords completely once passkeys work?

Not at first. Google's developer guidance recommends keeping existing sign-in methods for now while passkey support matures across devices. Remove a password only for accounts that have at least two working passkeys and a recovery path you have tested, and give users a clear way to opt in.

Sources

Share:
Back to Insights