Short answer
Custodial, non-custodial and embedded are not interchangeable labels. They describe different boundaries of economic control, key/signing responsibility and user experience. “Embedded” mainly describes where the wallet experience lives; the wallet can still be user-controlled or application-controlled depending on the architecture.
Decision 1: who controls value movement?
If the user must approve each transfer, use a user-controlled/non-custodial model. If the platform needs automated payouts, deposit collection or server-side settlement, a developer-controlled model may fit. If business treasury requires institutional controls, add explicit vault/policy/approval architecture.
Custodial / developer-controlled
The application or business controls transaction execution. This enables automation and simplifies UX, but it increases the importance of licensing analysis, authorization policy, segregation of duties, recovery and operational security. Circle explicitly notes that regulatory licensing may apply when a platform holds assets for users.
User-controlled / non-custodial
The user authorizes the signing operation. Circle documents user-controlled wallets where users authenticate with familiar methods and approve transactions from their device. The application orchestrates the flow but should not silently convert user-owned signing into backend authorization.
Embedded wallet
Embedded wallet is a product-experience pattern: onboarding, balance and transaction actions live inside your application rather than forcing the user into an external wallet extension. Coinbase CDP and Circle both document application-integrated wallet experiences. The key question remains who ultimately controls signing.
Architecture comparison
| Model | Best for | Primary risk to design |
|---|---|---|
| User-controlled embedded | Consumer fintech, rewards, user-owned assets | Recovery, session/signing UX, user intent |
| Developer-controlled | Payouts, deposits, automation, marketplaces | Authorization, custody responsibility, key-operation policy |
| Treasury/institutional | Company reserves and operational funds | Approvals, limits, segregation of duties, incident response |
Questions we answer during architecture discovery
- Who economically owns the assets at each stage?
- Who may initiate a transaction?
- Who must approve it?
- Can the backend execute while the user is offline?
- What recovery path exists?
- What happens during provider outage?
- Which state is authoritative for the product balance?
- Which jurisdictional or custody constraints must the legal team confirm?
Recommendation
Do not select a wallet provider based only on the prettiest onboarding demo. Write the control matrix first. Then compare providers against that matrix.