tl;dr
- An embedded wallet lives inside an app or platform, removing the need for an external wallet application.
- Traditional wallets such as MetaMask and Rainbow are separate interfaces; embedded wallets are part of the product the user is already in.
- Embedded wallets cut onboarding friction: users sign in with email or a social login, and the wallet is ready in seconds.
- The main risk is fragmentation: one wallet per app, per chain, with no way to recover it. Users end up with scattered balances and no clear ownership.
- Polygon embedded wallets are non-custodial, enforce rules in the account, work across chains, link multiple sign-in methods to one wallet, and recover without seed phrases.
What is an embedded wallet?
Every onchain product needs a wallet: it is how a user holds assets, signs transactions, and proves they are who they say they are. For years that meant an external wallet such as MetaMask or Rainbow, installed separately and connected to each app by hand.
That works for people who already live in crypto. For everyone else it is the step where they leave. Fintechs, marketplaces, and payment platforms that tried to bring mainstream users onchain ran into the same wall: a disjointed experience where the customer has to manage a second product just to use the first one.
Embedded wallets solve this. An embedded wallet is created and managed inside your application, so users can hold and move money without leaving it. No extension to install, no seed phrase to store, no separate interface to learn.
Below: how embedded wallets differ from traditional wallets, where they can go wrong, and how Polygon’s embedded wallets are built to avoid those problems.
How embedded wallets differ from traditional wallets
To understand the advantages of embedded wallets, start with what a traditional wallet asks of the user.
External wallets such as MetaMask and Rainbow are standalone applications or browser extensions. They hold the user’s private keys, and the user connects them to each app they want to use. That means installing the wallet, writing down a recovery phrase, connecting it manually, approving a session, and switching between the app and the wallet to sign. For a first-time user, each of those steps is a place to get confused and stop.
An embedded wallet is integrated directly into the application. The user signs in the way they sign in to anything else, and a wallet is created for them behind the scenes. They can hold a balance, pay, and receive money as part of the product’s native experience.
The keys behind an embedded wallet are protected either on the user’s device or in secure infrastructure such as hardware enclaves. Done well, the wallet is still non-custodial: the user owns the account, the application cannot move funds without their authorization, and the provider never holds a usable key. That distinction matters for regulated businesses; Custodial vs non-custodial wallets walks through it, The role of non-custodial wallets in blockchain payments covers the payments angle, and the webinar Wallets: Choosing Your Architecture helps you choose for your product.
Challenges with embedded wallets
Embedded wallets are easier to use, but a naive implementation creates problems of its own. The biggest is fragmentation.
When each app spins up its own wallet, users accumulate one per product, and often one per chain. That recreates the old problem of a different account for every service, now with money in each. A customer who has used three apps may hold funds in three places with three recovery stories, none of which they understand.
Fragmentation compounds as a product grows. Every new chain the app supports risks another wallet; every new sign-in method risks a duplicate account. If the user loses access to the email they signed up with, a wallet tied only to that email is gone. The convenience that made embedded wallets attractive turns into a support burden and a trust problem.
The answer is to build the embedded wallet so one account follows the user everywhere. Going back to external wallets does not solve it.
How Polygon embedded wallets avoid fragmentation
Polygon’s embedded wallets are non-custodial, and the architecture is designed around a single account per user, with the rules enforced in the account itself:
- One wallet across chains. The wallet is chain-agnostic. A user holds one account that works on every supported EVM network, and Polygon Trails routes cross-chain in a single confirmation, so users rarely have to think about which chain they are on.
- Multiple sign-in methods, one wallet. Google, Apple, email, and custom OIDC providers can all be linked to the same account. A user who signed up with Google can add email sign-in later and still land in the same wallet with the same balance.
- Recovery without seed phrases. Access is recovered through the linked sign-in methods, with timed recovery as a last resort, so losing a phone or an email does not mean losing funds.
- Rules at the wallet layer. Smart sessions let a user pre-authorize subscriptions, payouts, or agent budgets within limits they set: which contracts the wallet can call, how much it can spend, and when the permission expires. The wallet enforces those limits onchain, so the app cannot exceed them.
- Fees handled for the user. Your project can sponsor gas, in full or for a user’s first transactions, and let later fees be paid in stablecoins. See Gasless transactions and gas abstraction.
For developers, this means an embedded wallet that behaves like an account rather than a disposable key. Users keep one balance and one identity as your product adds chains, features, and sign-in options, and you never have to migrate them.
The wallet is part of the Polygon Open Money Stack, so the same integration gives you fiat on- and off-ramps, building blocks for customer-approved yield, and settlement. For the design principles behind a good first session, read Web3 user onboarding: how to simplify it for your app; for what MPC protects and what a payments product still needs from the account, read MPC wallets: what they protect, and what a payments product still needs.
Explore the embedded wallet documentation, or talk to a payments specialist about adding wallets to your product.

Nuvera is live on Polygon Open Money Stack for cross-border stablecoin settlement

Web3 user onboarding: how to simplify it for your app

SoFiUSD lands on Polygon Chain, bringing America's first bank-issued stablecoin to everyday use

Polygon Trails partners with Foresight to bring 1-click fund flows to prediction markets

Scalable payment infrastructure: scaling payment apps without sacrificing UX

MPC wallets: what they protect, and what a payments product still needs

Polygon Trails partners with Katana to solve DeFi fragmentation with 1-click liquidity and real yield

Stablecoin infrastructure is fragmented: the structural barriers to scaling crypto payments

What is an embedded wallet? How embedded wallets work

