Embedded wallets
Learn how to create embedded wallets for users within your application using the Okto API.
Creating Embedded Wallets
Okto's embedded wallets provide a seamless way to integrate wallet functionality into your application. This guide explains how to create and manage embedded wallets for your users.
Automatic Wallet Creation
Okto automatically handles wallet creation for your users. When a user authenticates with your application, Okto creates their embedded wallet addresses across supported chains. This means:
- No manual wallet creation is required
- Wallets are instantly available after authentication
- Users can immediately start interacting with supported chains
Understanding Wallet Providers
Okto's embedded wallets are managed through Wallet Providers (WP), which define distinct ecosystems for wallets and control their interoperability. Key concepts:
-
Wallet Provider Types: Okto currently offers two wallet providers:
- Okto EOA Wallets: Standard Externally Owned Accounts for EVM chains
- Okto AA Wallets: Account Abstraction (ERC-4337) wallets with enhanced features
-
Client Association: Your application is associated with one specific Wallet Provider
-
Interoperability: Wallets are interoperable within the same Wallet Provider ecosystem, meaning users get the same wallet address across different apps using the same WP
Learn More
For a detailed understanding of wallet providers, interoperability, and how they work within the Okto ecosystem, see our Embedded Wallets guide.
Accessing User Wallets
To retrieve a user's wallets across different chains, use the Get Wallet API
Note
Ensure that the user is authenticated before calling getAccount(). You should prompt users to log in if they are not already authenticated.