End-user wallets allow your application’s users to own and control their digital assets while you provide the wallet infrastructure. For background on the architecture and trade-offs, see delegated wallets.Documentation Index
Fetch the complete documentation index at: https://docs.dfns.co/llms.txt
Use this file to discover all available pages before exploring further.
What you’ll need
- A service account for backend operations
- WebAuthn configuration for passkey collection
Components to configure
End-user registration
Register end users with Dfns so they can create a passkey. Two methods are available: delegated registration (your service account creates users, recommended for full control) or social registration (users authenticate with Google directly, simpler but less flexible).Wallet creation and delegation
Create wallets and delegate them to your end users, either during registration or as a separate step. After delegation:- Only the end user can authorize transactions via their passkey
- Your organization cannot move the funds
- Your organization cannot apply policies or controls to the wallet
User login and actions
Authenticate returning users and let them perform transactions. Write operations require the user to sign with their passkey.User recovery
End users may need to recover access if they lose their device. Implement recovery flows that allow users to register a new passkey.See the implementing delegated wallets guide for step-by-step code examples covering all four components, and the recovery guide for recovery implementation.
Related solutions
Security best practices
Permissions, policies, and security controls
Automate deposits
Deposits and transfers