Passkey Uses Beyond Login: 18 Things They Can Do

Passkey uses beyond login shown on a phone and laptop

Most explainers stop at the sign-in button, but passkey uses go well beyond login. Under the hood, a passkey is a cryptographic key pair bound to a single domain, usually on the P-256 curve, and it only acts when its owner approves. It does two things: sign a challenge, or (through an extension) produce a secret that nothing else can recreate. Every use below applies one of those to a different problem.

This list assumes the passkey in your password manager, such as iCloud Keychain, Google Password Manager, Bitwarden or 1Password. Uses that need a hardware key, like SSH or disk unlock, are a separate topic.

Getting in

The familiar use is passwordless sign-in. The site issues a random challenge, you confirm with a fingerprint or PIN, and the signature covers the domain the browser is on. Possession and verification happen together, and NIST’s SP 800-63B-4 accepts synced passkeys at AAL2. Phishing sites get nowhere, since their domain yields a signature the real site refuses. The weak point is the fallback: an emailed recovery link becomes the account’s true security level.

A site can also open accounts that never have a password. What it keeps is a public key and a credential ID, which are useless to anyone who steals the database. Recovery becomes urgent sooner, so sites should encourage a backup passkey from a different manager.

A passkey can serve as a second factor behind a password too. Fake sites can’t relay it, unlike SMS or TOTP codes, but it works best as a stepping stone. GitHub already lets a passkey satisfy password and 2FA in a single step.

Other sign-in uses:

  • Cross-device sign-in lets you scan a QR code and approve on your phone.
  • One passkey can cover a website and its apps. Apple relies on an apple-app-site-association file, and Android on a Digital Asset Links file.
  • Related Origin Requests let one passkey work across example.com, example.co.nz and example-pay.com, through a JSON file on the main domain listing the other sites.

Proving it’s still you

An hour-old login proves little when someone is about to change a payout account. Asking for a new passkey approval just before the action takes seconds. Set userVerification to required, since the default setting lets a manager skip the biometric check, and verify the flag server-side. Too many prompts teach people to approve blindly, so pick the triggering actions carefully.

Identity providers can go further. In Microsoft Entra, Privileged Identity Management can require a Conditional Access authentication context on role activation. Point it at a phishing-resistant strength with sign-in frequency set to every time, and activating Global Administrator then requires a passkey. Register the passkeys before enforcing the policy and exclude emergency access accounts, or you can lock yourself out. A password-manager passkey can’t prove what device it lives on, so check how admins enrol passkeys before trusting the policy.

A site picks the challenge, so it can hash a description of an action, say a production release, together with a nonce and timestamp. The signed response then records that this passkey approved that exact action. It is a workaround, and W3C’s payments group considers it a misuse of the challenge field. The user sees only what the page shows, so a compromised page can display one thing and hash another.

Secure Payment Confirmation closes that gap for payments. The browser shows its own dialog with the merchant, amount and currency, out of the page’s reach, and the passkey signs those details. Chromium browsers on Android, macOS and Windows support it, though the spec remains a draft. Elsewhere, use the hashed challenge.

Keeping secrets

A signature changes every time, so it can’t be an encryption key. The prf extension gets around this: the site supplies a salt at sign-in, and each salt maps to its own fixed 32 bytes. Run them through HKDF to get an AES key that wraps the key protecting the user’s data. The server stores ciphertext it can’t read. Some password managers still lack prf, and losing the passkey loses the key, so protect the data key with two passkeys or print a recovery code.

Bitwarden applies the same extension to vaults. With the option on, one passkey approval signs you in and decrypts the vault with no master password. Without prf support, Bitwarden still asks for the master password.

Blockchains are another use. Through EIP-7951 in the Fusaka upgrade, Ethereum gained built-in verification for the passkey curve, so a smart account can name a passkey as its signer and skip the seed phrase. OpenZeppelin publishes a reference implementation. Lose every copy of the passkey without a second signer and the account is gone.

Looking after itself

Conditional create asks for a passkey right after a successful password sign-in, using mediation set to conditional. If the manager holds that password and agrees, it creates the passkey and tells the user afterwards. Apple shipped it with iOS 18 and macOS 15, and Chrome 136 followed.

The FIDO Credential Exchange specifications now allow moving passkeys between managers through an encrypted hand-off, with no plaintext export file. Apple’s version arrives in the 26 releases of its operating systems, and Google and Bitwarden support it too. The Signal API helps remove stale passkeys and update account names, though few browsers support it yet.

Where passkeys fall short

A passkey can’t verify who you are, only that the same manager came back. It doesn’t solve account recovery, and it can’t run unattended in cron jobs or CI. Sites also can’t trust it to prove which hardware it sits on.

What to ship first

The sign-in, step-up and conditional create uses are safe on every major platform today and deliver most of the benefit. Encrypted data with prf works but needs testing against each password manager. Payments and the Signal API need fallbacks until more browsers support them. This list was checked in November 2026, and support in this area changes monthly.

Source: fenko.nz

Written by

Saksham Bhargava

Saksham Bhargava runs Alteroid and has been writing about consumer technology for over five years, covering iPhone, Android, Windows, AI tools and gaming. With an MCA and six years of hands-on web development experience, he tests the features he writes about on his own devices and focuses on clear, practical guides that solve real problems. Away from the screen, he enjoys travelling to places most tourists skip.