Passwordless authorizationPasskey
Payment signed with passkey
The on-chain payment was authorized with the passkey protected by this device.
Passkey Smart Wallet
Levery combines passkey-native smart accounts, familiar authentication, optional hardware-bound access, and programmable permissions in one white-label wallet experience.
Clients access and authorize their smart wallet with the biometric, device PIN, or security method they already use.
Offer compatible FIDO2 smart cards and security keys as physical authenticators, including card formats similar to those clients already carry.
Where supported by the configured network, Relay, and quote, clients can pay execution fees with an institution-selected stablecoin instead of maintaining a separate native-asset balance.
From wallet friction to familiar access
Levery uses WebAuthn passkeys as smart-account authority. The standard client journey does not require a browser-extension wallet, a recovery phrase, or manual handling of raw private keys.
Connect your Passkey Smart Wallet to the platform.
Use passkey to sign in
Fast, secure access with biometrics and phishing-resistant passkeys stored on your trusted device, password manager, USB security key, or compatible NFC smart card.
Keep account creation, transaction review, authorization, and account administration inside the institution's own application.
The authenticator or credential provider protects the passkey material. Clients do not need to copy, export, store, or restore a mnemonic phrase in the standard flow.
Biometric and PIN verification occurs locally through the authenticator. The biometric template or device PIN is not exposed to Levery or the institution's wallet application.
Compatible environments can use Apple Passwords with iCloud Keychain, Google Password Manager, Windows Hello, Microsoft Edge, and other WebAuthn credential providers. On supported devices, passkey operations may be hardware-backed by a secure enclave or TPM. Availability, synchronization, and recovery depend on the provider, operating system, browser, relying-party configuration, and device.
Credential environment
Compatible WebAuthn providers and authenticators
Apple Passwords
iCloud Keychain
Google Password Manager
Android and Chrome
Microsoft
Windows Hello and Edge
Passkey credential
Hardware-backed where supported
Device biometrics
USB security key
NFC smart card
Physical and hardware-bound access
For programs that require a separate physical credential, compatible FIDO2 smart cards and security keys can provide a hardware-bound authorization path alongside platform passkeys.
Passkey Smart Card
Hardware-bound authorization
Issue a compatible smart card in a familiar credit-card form factor for tap, insert, or reader-based authorization, depending on card and device support.
Depending on the authenticator model, credential material can remain non-exportable and bound to the physical device instead of being synchronized across a platform account.
Cryptographic approval occurs on the authenticator while the application prepares, submits, and tracks the transaction online. This provides a cold-style credential boundary without implying offline on-chain settlement.
The institution defines accepted authenticator models, issuance, inventory, replacement, redundancy, recovery, and support procedures for its deployment.
Stablecoins can do more than move value. With the appropriate network and Relay configuration, the institution can make an approved stablecoin available as the fee token for eligible smart-wallet activity.
The Relay can quote execution costs in a supported token, including an institution-selected stablecoin where available.
Clients can complete eligible activity without first acquiring and managing a separate balance of the network's native asset.
The institution can alternatively sponsor approved execution under its own authentication, eligibility, transaction, budget, and abuse-prevention policies.
Fee-token preferences operate alongside call scopes, expiration, token-based spend limits, transaction review, and deployment-specific sponsorship rules.
Execution fee quote
Illustrative Relay interface
Selected fee token
Institution-selected stablecoin
Smart-wallet activity
Prepared for on-chain execution
Fee-token availability depends on the configured network, Relay, token, and quote. Sponsorship remains subject to the institution's operating policies.
Programmable account controls
Every client account can combine familiar authorization with enforceable limits on what the wallet may do, for how long, and with which assets.
Account control view
Illustrative smart-account policy
Authorization model
Passkey administrator
Scoped session activity enabled
Authority stays bounded
Passkey authentication confirms the credential. Smart-account permissions enforce what approved keys and sessions may do.
Make on-chain access feel as familiar as signing in or using a card.