> ## Documentation Index
> Fetch the complete documentation index at: https://docs.turnkey.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Embedded Business Wallets

> Shared wallets with role-based signing controls for teams, operators, and finance workflows.

export const FeatureCard = ({title, description, icon, logo, href}) => {
  return <a href={href} className="not-prose font-normal group ring-0 ring-transparent cursor-pointer block rounded-lg border border-zinc-950/10 dark:border-white/10 bg-white dark:bg-transparent p-5 no-underline hover:border-primary/40 transition-colors">
      <div className="tk-card-row">
        <span className="tk-card-icon-wrap">
          {logo ? <img src={`/images/networks/${logo}.svg`} className="tk-card-network-logo" alt="" /> : <span className="tk-card-icon" style={{
    maskImage: `url(/images/icons/${icon}.svg)`,
    WebkitMaskImage: `url(/images/icons/${icon}.svg)`
  }} />}
        </span>
        <div>
          <div className="font-semibold text-sm text-zinc-950 dark:text-white group-hover:text-primary transition-colors">
            {title}
          </div>
          {description && <div className="text-sm text-zinc-500 dark:text-zinc-400 mt-1">
              {description}
            </div>}
        </div>
      </div>
    </a>;
};

With Turnkey, your application can provision wallets designed for team usage. Multiple end users operate within a single sub-organization with role-based access control governed by the policy engine. No seed phrases, no browser extensions.

## Architecture at a glance

Your parent organization sits at the top with read-only visibility. Each business customer gets its own sub-organization — fully isolated, with independent wallets, team members, and policy configurations.

<Frame>
  <img
    src="https://mintcdn.com/turnkey-0e7c1f5b/CvYCjuuK7cCl6tHg/images/embedded-wallets/embedded-business-wallets-diagram.png?fit=max&auto=format&n=CvYCjuuK7cCl6tHg&q=85&s=ffab98096f127001b81a4c4ca71ebe10"
    alt="Embedded Business Wallets architecture: sub-organizations with users, roles, policies, and
wallets per business"
    width="2607"
    height="1908"
    data-path="images/embedded-wallets/embedded-business-wallets-diagram.png"
  />
</Frame>

## Powered by Turnkey

* [**Mural Pay**](https://www.turnkey.com/customers/mural-pay-cross-border-payments) -- cross-border stablecoin payments platform processing 5,000+ monthly transactions for global businesses, fintechs, and banks
* [**AllScale**](https://www.turnkey.com/customers/allscale-cross-border-stablecoin-transactions) -- stablecoin neobank where small businesses manage payments with team-based wallet access

## Key implementation decisions

Turnkey enables developers to build shared business wallets with role-based controls across dimensions such as organization hierarchy, access control, and custody. See the key implementation decisions below to curate the exact experience your business customers need.

| Decision                      | Explanation                                                                                                                                                                                                                                                 | Learn more                                                                                                                                                    |
| :---------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Organization hierarchy**    | Create a sub-organization for each business customer. Each sub-org is a fully isolated environment with its own wallets, users, and policies.                                                                                                               | [Sub-Organizations](/features/sub-organizations)                                                                                                              |
| **Role-based access control** | Assign roles to users via tags (e.g. `finance-team`, `operator`, `admin`). Write policies that reference these roles to control who can sign, what they can sign, and under what conditions.                                                                | [Policies](/features/policies/overview), [Policy Language](/features/policies/language)                                                                       |
| **Policies and guardrails**   | With roles in place, enforce spending limits, require multi-party approval for high-value transactions, restrict payments to allowlisted addresses, or require quorum for policy changes. Optionally let business customers configure their own guardrails. | [Policies](/features/policies/overview), [Delegated Access](/features/policies/delegated-access/overview)                                                     |
| **Custody model**             | Choose who can authorize the enclave to sign: the user only (non-custodial), your application (custodial), or both with scoped permissions (hybrid). Business wallets commonly use hybrid custody with policy-backed controls.                              | [Custody models](/solutions/embedded-wallets/overview#custody-models)                                                                                         |
| **Authentication methods**    | Choose user auth methods: Passkeys, OAuth/email, or SMS. You can use the [Auth Proxy](/features/authentication/auth-proxy) for backend-signed OTP/OAuth/signup without your own backend, or wire auth to your app.                                          | [Authentication Overview](/features/authentication/overview), [Auth Proxy](/features/authentication/auth-proxy)                                               |
| **Session management**        | Allow a user to take multiple, contiguous actions in a defined period of time. Actions include: Read-write or read-only.                                                                                                                                    | [Sessions](/features/authentication/sessions)                                                                                                                 |
| **Gas sponsorship**           | Integrate a gasless UX via sponsored transactions to cover who pays gas and how transactions are broadcast.                                                                                                                                                 | [Transaction Management](/features/transaction-management), [Sending sponsored transactions](/features/transaction-management/sending-sponsored-transactions) |
| **Key portability**           | Determine whether users can import or export keys.                                                                                                                                                                                                          | [Import wallets](/features/wallets/import-wallets), [Export wallets](/features/wallets/export-wallets)                                                        |
| **Recovery flows**            | Define how users regain access if they lose their authenticator. Options include email recovery and backup passkeys.                                                                                                                                        | [Email recovery](/features/authentication/email)                                                                                                              |
| **Agent-delegated signing**   | Let end users grant scoped signing authority to AI agents or automated systems from their own wallet. The user retains root control and can revoke access at any time.                                                                                      | [End-User Delegated Agent Signing](/features/policies/delegated-access/agentic-wallets)                                                                       |

## Example: Payments platform with role-based controls

Typical requirements and how Turnkey addresses them:

| Requirement                        | Turnkey capability                                                                                                                                                                            |
| :--------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Multi-user team access             | One [sub-organization](/features/sub-organizations) per business customer with isolated wallets, users, and [role-based policies](/features/policies/overview)                                |
| Non-custodial with oversight       | Hybrid custody with [policy engine](/features/policies/overview) controls. See [Custody models](/solutions/embedded-wallets/overview#custody-models)                                          |
| Multi-party approval               | [Policies](/features/policies/language) requiring 2+ approvers for high-value transactions or policy changes                                                                                  |
| Vendor and recipient controls      | Allowlisted addresses and spending limits via [policy language](/features/policies/language)                                                                                                  |
| Familiar auth for non-crypto users | Passkey and email authentication with [email recovery](/features/authentication/email). No seed phrases                                                                                       |
| Cross-border payments              | Chain-agnostic derivation and signing. See [Networks](/features/networks/overview) and [Wallets Concept](/features/wallets)                                                                   |
| Gasless UX                         | [Sponsored transactions](/features/transaction-management) and [sending sponsored transactions](/features/transaction-management/sending-sponsored-transactions)                              |
| Fast integration                   | Use the [Embedded Wallet Kit](/solutions/embedded-wallets/integration-guide/react/index) for built-in auth and wallet UI components. See [Quickstart](/solutions/embedded-wallets/quickstart) |

## Next steps

<div style={{display: 'grid', gridTemplateColumns: 'repeat(2, 1fr)', gap: '12px'}}>
  <FeatureCard title="Quickstart" icon="rocket-01" href="/solutions/embedded-wallets/quickstart" description="Explore the live demo, clone a starter app, or jump straight into building." />

  <FeatureCard title="Integration Guide" icon="book-open-01" href="/solutions/embedded-wallets/integration-guide/overview" description="Step-by-step guides for React, React Native, Flutter, Swift, and Kotlin." />
</div>