Rollout & operations
Prompting users to create a passkey after sign-in: timing, copy and \"not now\"
6 min read
Key points
- Offer a passkey right after a successful sign-in with a password or SMS code, after account recovery, or after signing in with a passkey from another device.
- Show the prompt only on devices that can create a passkey, back off after "not now," and never block the sign-in flow.
- On supporting browsers, conditional create can also create a passkey automatically after sign-in with a saved password.
The best moment to offer a passkey is right after someone signs in successfully with a password or an SMS code. They've just proven who they are, and "next time, sign in with your fingerprint or face on this device" lands well. Show the prompt only on devices that can create a passkey, wait a while before asking again after "not now," and never block the sign-in flow. On supporting browsers there is also conditional create, which can create a passkey automatically right after sign-in with a saved password.
When to show it
Google's passkey deployment checklist on web.dev and the FIDO Alliance design guidelines point to these moments (the SMS one comes from FIDO, the rest from web.dev):
| Moment | Why |
|---|---|
| Right after sign-in with a password (and second factor) | Identity was just verified, and the time saved next time is easy to see |
| Right after verifying with a one-time code such as SMS | "No more waiting for codes" is an easy message |
| After account recovery (password reset) | People can create a passkey instead of a new password |
| Right after signing in with a passkey from another device | Next time they can sign in on this device without scanning a QR code |
Avoid showing it before sign-in (to unverified visitors) or while people are focused on something else, such as checking out.
Whom to show it to
If everyone sees it every time, people stop reading it. Narrow it down:
- The device can create a passkey. Show it only when
PublicKeyCredential.isUserVerifyingPlatformAuthenticatorAvailable()(orSealGate.platformAuthenticatorAvailable()in the SDK) returns true. On a device with no biometrics or screen lock, people can't proceed - This device doesn't have a passkey yet. Your server can't know exactly which devices hold a key, so leave a marker in a cookie or localStorage on the device after registration. If a duplicate registration starts anyway, the authenticator refuses it as long as existing keys are in
excludeCredentials - They signed in recently. The web.dev checklist recommends verifying the user with the strongest method available before creating a passkey. If the session is old, ask them to confirm their password again first
Designing the screen
Content
- Heading: what it does for them (for example, "Sign in with your fingerprint or face next time")
- Body: one or two sentences on what a passkey is and that there's no password to remember
- Primary button: "Create a passkey"
- Secondary button: "Not now"
- A link: "What's a passkey?"
In its pattern for offering passkeys after SMS OTP, the FIDO Alliance design guidelines use a headline along the lines of "With passkeys, you don't need to remember complex passwords and codes" and explain that "Passkeys are encrypted digital keys you create using your fingerprint, face, or screen lock." Passkey UX copy covers wording in more depth.
Placement
- Use a full-screen interstitial, or the top of the first page after sign-in
- "Not now" always closes it and takes people where they were going before sign-in
- If someone closes the OS dialog (cancel or timeout), don't treat it as an error; continue to where they were going
Handling "not now"
- Record "not now" with the user on your server, so the decision follows them across devices
- Ask again only after a number of days or sign-ins. Asking every time trains people to ignore it
- For people who decline repeatedly, stop prompting after sign-in and leave the option in account settings
The FIDO Alliance design guidelines list creating, viewing and managing passkeys in account settings as a required pattern. Even if you stop prompting, keep a place where people can create one themselves.
Automatic creation (conditional create)
WebAuthn Level 3 lets you call navigator.credentials.create() with mediation: 'conditional' to register a passkey without prominent modal UI. The browser creates a passkey automatically when, for example, the password manager has a saved password for your site that was used recently to sign in.
- Chrome supports it on desktop from version 136. Creation succeeds when a password for the site is saved in Google Password Manager and was recently used to sign in
- Safari 18.0 added support for
mediation=conditionalon credential creation - Check support with
conditionalCreatefromPublicKeyCredential.getClientCapabilities(), as the spec recommends - The spec says user presence and user verification are not required for conditional creation unless they're performed during the ceremony. If your server requires user verification, keys created this way may be rejected at registration
Automatic creation adds no steps for people, but they may not notice it happened. Sending a notification (by email, for example) after creation keeps them informed and helps them spot registrations they didn't make. The web.dev checklist also recommends notifying users after a passkey is created.
After registration
- Give the key a name (the device name, or the passkey provider's name derived from the AAGUID)
- Say briefly that it will work next time, and continue to where they were going
- Send a notification about the new passkey
- Measure. Count prompts shown, "create" taps and completed registrations separately so you can see where people drop off. Passkey adoption metrics goes deeper
Implementing this with SealGate
On the page right after sign-in, call sg.register({ name: 'This device' }) from the browser SDK. Your server checks the session to confirm the user is signed in, then calls /v1/register/options with signed_in: true. If this authenticator already has a key for the user, the SDK fails with already_registered; close the prompt and say "This device already has a passkey." If the person closes the dialog, the code is cancelled.
The SDK's register() shows the regular registration dialog; it does not take the mediation: 'conditional' option described above. You can send the new-passkey notification from your side when you receive the register.completed webhook, and check the registration count with registrations from GET /v1/apps/{app_id}/stats. See the docs for details.
FAQ
Should new sign-ups create a passkey right away?
On devices that can, yes, offer it. Just make sure a recovery path (such as a verified email address) is in place first.
How many times can we show it after "not now"?
There's no fixed number. Record it on the server and space the prompts out. For people who keep declining, stop prompting after sign-in and leave the option in settings.
What about browsers without automatic creation?
If getClientCapabilities() doesn't report conditionalCreate, show the regular prompt.
Sources
- Secure and seamless passkeys: A deployment checklist (web.dev, June 5, 2025)
- Automatically create passkeys in Google Password Manager on Chrome desktop (Chrome for Developers, May 9, 2025)
- WebKit Features in Safari 18.0 (WebKit, September 16, 2024)
- Web Authentication: An API for accessing Public Key Credentials Level 3 (W3C, August 25, 2026)
- Required Patterns (FIDO Alliance, Passkey Central)
- Deprecate SMS OTP (FIDO Alliance, Passkey Central)
Related posts
Implementation · SealGate
How to add passkeys to an existing login without dropping passwords
A step-by-step plan for adding passkeys to a password login you already run, covering the RP ID, enrollment after sign-in, button and autofill sign-in, device management, recovery, and when to retire passwords.
Rollout & operations · Account security
Moving from SMS one-time codes to passkeys, step by step
SMS codes can be phished and stolen via SIM swaps, and NIST calls them restricted. How to move users to passkeys without lockouts, and how much SMS to keep.
Account security · Rollout & operations
After a data breach: what passkeys stop, what they don't, and what to check in your login
A practical checklist for teams that run a login after a wave of customer data breaches: what passkeys can and cannot prevent, credential stuffing and phishing, recovery flows, and how to add passkeys to an existing login step by step.