Skip to main content
Business Accounts are in early access. See Business Accounts for the model.
A business-account wallet is a Dynamic embedded wallet that the account owns instead of a single user, so everything in Embedded Wallets, including the MPC-backed architecture, key shares, and recovery, still applies. What changes is who controls access: each wallet has a set of signers that the account’s owner or admins manage.

​
Wallets

An account gets a wallet in one of two ways. You can create a fresh wallet that the account owns from the start, or you can link an embedded wallet you already own so the team can share it. In both cases you become the wallet’s first signer. A wallet can belong to only one business account, and only the wallet’s owner can link it. Linking and removing a wallet are sensitive account actions, so they require step-up authentication and can be covered by governance.

​
Signers

A signer approves transactions and messages with a specific wallet. Adding a signer grants that member access to the wallet, and removing a signer revokes only their access, so the wallet and the other signers are unaffected. Only an owner or admin who is already an active signer on the wallet can add signers. A wallet must always keep at least one active signer, because no one could approve anything afterward. Removing the last active signer is rejected, so add another signer or remove the wallet first. Server signers, which let an automated process sign without a person present, are coming soon. Only end-user signers are supported today.

​
Signing

A signer signs with a business-account wallet the same way as with any embedded wallet. A quorum policy can require approvals from other members before the wallet signs.

​
Next steps

Pick your SDK under Implement in the sidebar to add wallets, manage signers, and sign.
Last modified on September 30, 2026