HomeWith 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.Documentation Index
Fetch the complete documentation index at: https://turnkey-0e7c1f5b-graham-docs-revamp.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
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.
Powered by Turnkey
- Mural Pay — cross-border stablecoin payments platform processing 5,000+ monthly transactions for global businesses, fintechs, and banks
- AllScale — 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 |
| 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, Policy 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, Delegated Access |
| 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 |
| Authentication methods | Choose user auth methods: Passkeys, OAuth/email, or SMS. You can use the Auth Proxy for backend-signed OTP/OAuth/signup without your own backend, or wire auth to your app. | Authentication Overview, 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 |
| Gas sponsorship | Integrate a gasless UX via sponsored transactions to cover who pays gas and how transactions are broadcast. | Transaction Management, Sending sponsored transactions |
| Key portability | Determine whether users can import or export keys. | Import wallets, Export wallets |
| Recovery flows | Define how users regain access if they lose their authenticator. Options include email recovery and backup passkeys. | Email recovery |
| 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 |
Example: Payments platform with role-based controls
Typical requirements and how Turnkey addresses them:| Requirement | Turnkey capability |
|---|---|
| Multi-user team access | One sub-organization per business customer with isolated wallets, users, and role-based policies |
| Non-custodial with oversight | Hybrid custody with policy engine controls. See Custody models |
| Multi-party approval | Policies requiring 2+ approvers for high-value transactions or policy changes |
| Vendor and recipient controls | Allowlisted addresses and spending limits via policy language |
| Familiar auth for non-crypto users | Passkey and email authentication with email recovery. No seed phrases |
| Cross-border payments | Chain-agnostic derivation and signing. See Networks and Wallets Concept |
| Gasless UX | Sponsored transactions and sending sponsored transactions |
| Fast integration | Use the Embedded Wallet Kit for built-in auth and wallet UI components. See Quickstart |