> **Can't find what you're looking for?** Use `search_docs` on the docs MCP server at `https://www.openfort.io/api/mcp` to find what you need.
>
> **Have feedback?** Use `submit_feedback` on the same MCP server.

# Embedded Wallet

Embedded wallets provide a seamless experience by abstracting away the complexity of wallet management. Users can interact with your application without needing to understand private keys, seed phrases, and blockchain concepts.

## Choose your SDK

* [React](https://www.openfort.io/docs/products/embedded-wallet/react) — Web - @openfort/react. React SDK for web applications.
* [React Native](https://www.openfort.io/docs/products/embedded-wallet/react-native) — Mobile - @openfort/react-native. React SDK for mobile applications.
* [iOS](https://www.openfort.io/docs/products/embedded-wallet/swift) — Mobile - @openfort/swift. iOS SDK for mobile applications.
* [Unity](https://www.openfort.io/docs/products/embedded-wallet/unity) — Game Development. For game development with Unity engine.

Without a UI framework, use the [JavaScript SDK](https://www.openfort.io/docs/products/embedded-wallet/javascript/quickstart) directly: `@openfort/openfort-js` is the client every SDK above wraps.

## Core concepts

Read these before wiring up an SDK. They apply to all of them.

| Page | What it covers |
|------|----------------|
| [Authentication methods](https://www.openfort.io/docs/products/embedded-wallet/authentication) | Email and password, OTP, OAuth, guest, and external wallet sign-in, and what each returns |
| [Account types](https://www.openfort.io/docs/products/embedded-wallet/account-types) | EOA, smart account, and delegated account, and which chains support each |
| [Wallet lifecycle](https://www.openfort.io/docs/products/embedded-wallet/wallet-lifecycle) | The states a wallet moves through, from `NONE` to `READY`, and when it is safe to sign |

## Server-side

A wallet is self-custodial, but three jobs belong on your backend.

| Page | What it covers |
|------|----------------|
| [Verify access tokens](https://www.openfort.io/docs/products/embedded-wallet/server/access-token) | Validating a user's session token before trusting a request |
| [Automatic recovery session](https://www.openfort.io/docs/products/embedded-wallet/server/automatic-recovery-session) | The encryption session endpoint that automatic recovery calls |
| [Pregenerate embedded wallets](https://www.openfort.io/docs/products/embedded-wallet/server/pregenerate-wallets) | Reserving wallet addresses before a user signs up |

## Security

| Page | What it covers |
|------|----------------|
| [On-device execution](https://www.openfort.io/docs/products/embedded-wallet/security/on-device) | Where key material is used and how the execution environment is isolated |
| [User authentication](https://www.openfort.io/docs/products/embedded-wallet/security/user-authentication) | The session and token model behind the auth methods |
| [Content Security Policy](https://www.openfort.io/docs/products/embedded-wallet/security/csp) | The CSP directives a host application must allow |

Moving an existing user base across from another provider? See the [migration guides](https://www.openfort.io/docs/products/embedded-wallet/migration) for Privy, Dynamic, Turnkey, and Web3Auth.
