Embedded Wallets: Invisible Onboarding and the Infrastructure Behind Them

An embedded wallet is a cryptocurrency wallet built directly into an application, so users interact with blockchain functionality without leaving the app or managing a separate wallet like MetaMask. The wallet is created automatically when the user signs up, often without the user even realizing a wallet exists. There is no seed phrase to write down, no browser extension to install, no separate app to open.

Embedded wallets are the infrastructure behind the "invisible Web3" trend, where crypto functionality is woven into consumer apps, games, and fintech products without the friction that kept mainstream users away. A user signs in with email or a social account and a wallet is provisioned behind the scenes.

This guide covers what embedded wallets are, how they differ from standalone wallets, the developer benefits, the security models, and how MPC secures them.

What an Embedded Wallet Is

An embedded wallet is provisioned and managed inside a host application. The distinguishing features are.

Automatic creation. The wallet is created when the user signs up, typically tied to an email or social login, without a separate wallet setup flow.

No seed phrase burden. The user does not manage a 12 or 24 word seed phrase. Key security is handled by the wallet infrastructure using MPC, secure enclaves, or a custodial model.

In-app experience. All wallet interactions happen inside the host app. The user never leaves to approve transactions in an external wallet.

Developer-controlled UX. The application developer controls the entire experience, including how transactions are presented and approved.

The result is that blockchain functionality feels like a normal app feature rather than a separate technical hurdle. This is why embedded wallets have become central to consumer crypto, gaming, and fintech onboarding.

Embedded vs Standalone Wallets

A standalone wallet suits crypto-native users who already manage their own wallet across applications. An embedded wallet suits applications bringing mainstream users into Web3 for the first time, where the friction of a standalone wallet would lose most of them at signup.

Programmable Wallets

Programmable wallets are closely related. The term, used by providers like Circle and Turnkey, refers to wallets that developers can control programmatically through APIs, provisioning wallets, defining signing policies, and automating transactions at scale.

Embedded and programmable overlap heavily. An embedded wallet is programmable from the developer's side (provisioned and controlled via API) and embedded from the user's side (invisible, in-app). The two terms describe the same infrastructure from different angles.

Programmable wallet infrastructure is what lets an application create thousands or millions of wallets, apply consistent security policies, and integrate wallet functionality into automated workflows.

The Security Models

Embedded wallets differ most importantly in how they secure the underlying keys. Three models dominate.

MPC (multi-party computation). The key is split into shares, typically between the user's device or session and the infrastructure provider. No complete key exists. No single party can sign alone. This preserves a degree of self-custody while removing the seed phrase.

TEE (trusted execution environment). Keys are managed inside a hardware-isolated secure enclave (such as Intel SGX or AWS Nitro). The key exists as a complete value but only inside the protected enclave. Security depends on trusting the hardware and the enclave implementation.

Custodial. The provider holds the keys on the user's behalf. Simplest to implement, but reintroduces counterparty risk and means the wallet is not self-custodial.

The MPC model is generally preferred for embedded wallets that want to preserve self-custody while delivering the seamless UX. The user keeps control (their share is required to sign) without managing a seed phrase.

How MPC Secures Embedded Wallets

For an embedded wallet built on MPC, the flow works as follows.

When a user signs up, a Distributed Key Generation process creates key shares. One share is associated with the user (on their device or in their authenticated session). One or more shares sit with the infrastructure provider. A wallet address is produced. No complete key is created.

When the user takes an action requiring a transaction, the threshold of shares coordinates to produce a signature. The user's share participates, so the provider cannot sign without the user. The signature is standard and settles on-chain normally.

Because no complete key exists and the user's share is required, the wallet is self-custodial in the meaningful sense: the provider cannot move the user's funds alone. And because there is no seed phrase, onboarding is frictionless.

Silent Shard provides the MPC layer that embedded wallet builders integrate. It implements the DKLs23 protocol, generates signatures in under 20ms, and is deployed at consumer scale, Okto by CoinDCX runs 17 million wallets on it. For the underlying detail, see the MPC wallet guide and best MPC wallet SDK guide.

Leading Embedded Wallet Providers

Many embedded wallet products build the developer-facing experience on top of an MPC key management SDK. The wallet product handles onboarding, UX, and integration. The MPC SDK handles the cryptographic key security.

Related Reading

• MPC Wallet: What It Is and How to Choose One

• Best MPC Wallet SDK for Developers

• Account Abstraction Wallets

• Self-Custody Wallets

• Transaction Signing

• Silent Shard Product

FAQ

What is an embedded wallet? An embedded wallet is a cryptocurrency wallet built directly into an application. It is created automatically when the user signs up, requires no seed phrase, and operates inside the host app. Users interact with blockchain functionality without managing a separate wallet.

What is the difference between embedded and programmable wallets? They describe the same infrastructure from different angles. Embedded refers to the user experience (invisible, in-app). Programmable refers to the developer experience (provisioned and controlled via API). An embedded wallet is programmable from the developer side.

How are embedded wallets secured? Three models are common: MPC (key split into shares, no complete key exists), TEE (key inside a hardware enclave), and custodial (provider holds the key). MPC is generally preferred for preserving self-custody while removing the seed phrase.

Are embedded wallets self-custodial? They can be. With an MPC-based embedded wallet where the user holds a required share, the provider cannot sign alone, so the wallet is self-custodial. Custodial embedded wallets, where the provider holds the full key, are not.

Which embedded wallet SDK should developers use? The choice depends on the security model and integration needs. For MPC-based key security, Silent Shard implements DKLs23, is open source, signs in under 20ms, and is proven at consumer scale with 17 million wallets on Okto.