Wallets and signers

How a business account owns wallets and who is allowed to sign with each one.

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. An owner or admin can create a fresh wallet that the account owns from the start, as the add wallets guide shows. You can also link an embedded wallet that already exists so the team can share it, as the same guide shows. Before it is linked, an embedded wallet belongs to the one user it was created for, and only that user can link it. If you link it into an existing account, you must also be an owner or admin of that account. In both cases you become the wallet’s first signer. A wallet can belong to only one business account.

An account can hold up to 10 wallets by default. See Limits for the configurable caps.

Linking and removing a wallet are sensitive account actions, so they require step-up authentication and can be covered by approvals.

Signers

A signer approves transactions and messages with a specific wallet. Adding a signer grants that person access to the wallet, and removing a signer revokes only their access, so the wallet and the other signers are unaffected. A signer is active once its key share is set up for the wallet and it has not been removed. Only an owner or admin who is already an active signer on the wallet can add signers. An owner or admin who is not a signer cannot add themselves, so another owner or admin who is an active signer has to add them.

A signer is not the same as an approver in an approval requirement. An approver signs off on a proposed action before it proceeds but holds no signing power, so a member with the viewer role can be a required approver. A signer is the only party that can produce the wallet’s signatures.

	Signer	Approver
What they do	Authorizes transactions and messages	Signs off on a proposal before it proceeds
Moves funds	Yes	No
How they get power	Granted per wallet	Named by an approval requirement

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 first. An owner or admin can instead remove the wallet from the account, which removes all of its signers. A wallet can have up to 10 signers by default; see Limits.

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, and the signing guide shows the SDK calls. A quorum policy is a rule that requires approvals from eligible members, meaning members whose role the rule allows to approve, before the wallet signs. While approvals are pending, the signing request waits as a proposal. Once they are in, the initiator resumes it as a separate step to get the signature.

Next steps

Pick your SDK under Implement in the sidebar to add wallets, manage signers, and sign.