Configure recovery when an app-origin account is created. Verified-identity recovery lets a user who loses every passkey prove the same email or OAuth identity and add a new passkey to that application’s existing smart account.
This managed-wallet flow is separate from SDK guardian recovery, where your application installs and operates its own onchain guardian accounts.
Add the verified-identity fallback to the same client used for sign-up and login. clientConfig is your provider, client ID, and sponsorship configuration from the shared client initialization:
During account creation, the embedded wallet SDK first attempts passkey-based recovery using the passkey provider’s PRF capability. The configured fallback applies only when passkey-based recovery is unavailable.
recovery.fallback is an account-creation policy. Adding it to a client later does not retrofit recovery onto an already-created account.
Keep the account namespace unchanged. clientId selects registered
application metadata; it does not move recovery to the hosted provider’s
centralized WebAuthn namespace. Changing the host name, RP ID, or WebAuthn
mode selects another credential, signer, and smart account.
Open the recovery backup flow
Call setupRecovery() after a successful login or account creation. It opens the authenticated backup flow where the user creates a recovery passphrase and downloads a backup file:
A completed result means the user completed this backup flow. It does not prove that every recovery mechanism or guardian is ready, so do not use it as a universal “recovery ready” check.
Continue with Recover an account for the flow after every usable passkey is lost.