Embedded Wallet

Overview

An embedded wallet gives an application a native interface for address creation, balances, signing, deposits, transfers, or payments. Key control may remain with the user, be shared through distributed signing, or be managed by a provider, so embedded describes placement rather than custody.

The integration can simplify onboarding by using familiar authentication, account recovery, sponsored fees, or application-specific permissions. However, the application may become a critical dependency for discovery, authorization, and recovery. Users can misunderstand whether they own portable keys or only access an account through the host service.

Product teams should disclose custody, recovery, export, network support, fees, and failure behavior. They should isolate wallet authority from ordinary application sessions, protect SDK and API credentials, verify transaction intent, and test provider outages. Account deletion, device change, and compromised login must have explicit wallet outcomes.

Records for Embedded Wallet should preserve account and address identifiers, asset and network identity, policy version, requester, approvers, signed payload or transaction reference, fees, timestamps, status history, confirmations, exceptions, and final balance and accounting effects. For Embedded Wallet, corrections must remain linked rather than overwrite the original event.

Embedded Wallet should be distinguished from the asset balance and from the application that displays it. For example, a customer-facing success message does not prove that the intended transaction executed on the correct network; operations should verify execution and reconcile the result before irreversible fulfillment.

Material risks for Embedded Wallet include credential compromise, malicious destinations, unsupported assets, wrong-network transfers, stale balances, compromised software, provider outage, privacy leakage, and inaccessible recovery material. For Embedded Wallet, controls should reflect value, automation, reversibility, and whether the organization or a third party controls signing.