Choose a wallet model
| Type | Ownership & custody | Best for | Highlights |
|---|---|---|---|
| Embedded | End-user owned, MPC key shares (user + Dynamic). Non-custodial. | Smooth onboarding, in-app wallets, smart accounts. | Sub-second signing, exportable keys, recovery options, works with smart wallets. |
| External | User’s own wallet (MetaMask, Phantom, Coinbase Smart Wallet, etc.). | Let users sign up/login with their wallet; multi-wallet experiences. | Connect vs authenticate modes, multi-wallet, wallet recommendations, risk screening. |
| Server | Backend-controlled MPC wallets. | Automation, agents, scheduled/triggered transactions. | Backend ownership, gas sponsorship, supports EVM and SVM. |
| Global | End-user owned; make embedded wallets usable across apps in your ecosystem. | Cross-app interoperability, ecosystem/chain programs, branded wallet reach. | QR/URI connect with WalletConnect, web3 library guides, ecosystem tooling. |
When to use what
- Embedded wallets: fastest onboarding, no extensions required, works with smart wallets for gas sponsorship and programmable flows.
- External wallets: serve web3-native users, keep their wallet of choice, add multi-wallet and recommendations.
- Server wallets: fully programmatic control for agents, schedulers, and backend-driven transactions.
- Global wallets: extend embedded wallets across partner apps or your ecosystem using WalletConnect-based flows or partner integrations.
- Mixed setups: enable both embedded and external so users can link or switch; your backend can still run server wallets separately.