<!-- tempo-docs-context -->
> Source: [/docs/accounts](https://tempo.xyz/developers/docs/accounts.md)
> Section: [Accounts](https://tempo.xyz/developers/docs/accounts.md). Create accounts, set up signing methods, policies, access keys, key rotation, and fees, and follow guides for users, automations, agents, and teams.
> [Documentation index](https://tempo.xyz/developers/llms.txt) · [Docs skill](https://tempo.xyz/developers/SKILL.md)

> Tempo MCP: Use `search`, `find_pages`, `read_page`, and `code` at `https://mcp.tempo.xyz` for Tempo and related documentation.
> If an indexed page is missing or reflects an older site, read this site’s [documentation index](https://tempo.xyz/developers/llms.txt) and Markdown pages directly.

<span id="build-your-account-integration" />

# Tempo Accounts

Give every customer and business a stablecoin account with security rules that Tempo enforces onchain.

[Create an account →](https://tempo.xyz/developers/docs/accounts/create)

A Tempo account: an address that holds stablecoin balances, a passkey and a private key as signers with weight 1 each toward a threshold of 2, and an access key with a daily limit.

<span id="whats-in-a-tempo-account" />

<span id="how-tempo-accounts-work" />

<span id="account-model" />

## Overview

A Tempo account is an address that holds stablecoins. Its rules live onchain, and each account has three parts:

* **Address:** Holds the account's stablecoins. It never changes, even when you [replace its signers](https://tempo.xyz/developers/docs/accounts/account-configuration).
* **Signers:** Approve payments and changes to the account. Each is a [private key, device key, or passkey](https://tempo.xyz/developers/docs/accounts/authentication) with a weight. A transaction runs once its approvers' weights reach the [threshold](https://tempo.xyz/developers/docs/accounts/policies/signing-thresholds), such as any 2 of 3.
* **Access Keys:** Let a customer's phone, your backend, or an AI agent [pay on its own](https://tempo.xyz/developers/docs/accounts/access-keys). Each works within the limits, expiry, and allowed calls you set.

<span id="account-capabilities" />

<span id="accounts-capabilities" />

## Why Tempo Accounts

* **Native Account Abstraction:** Every [Tempo Transaction](https://tempo.xyz/developers/docs/guide/tempo-transaction) has passkey signatures, access keys, batched calls, and [fee sponsorship](https://tempo.xyz/developers/docs/accounts/fees/fee-sponsorship) built in. You run no wallet contracts, bundlers, or paymasters.
* **Self-Custodial:** Signing rules live onchain, and Tempo checks every transaction against them. When the customer holds the [passkey](https://tempo.xyz/developers/docs/accounts/authentication/passkeys) or [private key](https://tempo.xyz/developers/docs/accounts/authentication/private-keys), neither you nor Tempo can move their funds.
* **Your Wallet Stack Works:** Tempo is [EVM compatible](https://tempo.xyz/developers/docs/quickstart/evm-compatibility). [Wallet providers](https://tempo.xyz/developers/docs/accounts/apps) and [custodians](https://tempo.xyz/developers/docs/accounts/custodians) such as Privy, Turnkey, Dynamic, and Fireblocks work, and so do browser wallets like MetaMask.

## What You Can Build

* **Stablecoin Accounts for Your Users:** Each user gets their own account in your app. They approve with a key they hold, such as a [passkey](https://tempo.xyz/developers/docs/accounts/authentication/passkeys) or a provider key from Privy or Turnkey. You never hold their funds.
* **Automated Payments:** Your backend, card program, or AI agent pays with its own revocable [access key](https://tempo.xyz/developers/docs/accounts/access-keys). Tempo rejects any payment over its limit, to an unlisted payee, or after it expires.
* **Business Accounts:** Hold customer funds in one [omnibus account](https://tempo.xyz/developers/docs/accounts/custodians/omnibus-accounts), with a [deposit address](https://tempo.xyz/developers/docs/accounts/virtual-addresses) per customer and no sweep transactions. Or run a treasury from a [custodian](https://tempo.xyz/developers/docs/accounts/custodians) like Fireblocks.

<span id="choose-an-account-model" />

<span id="choose-who-controls-signing" />

<span id="tempo-account-building-blocks" />

<span id="configure-account-controls" />

<span id="keys-and-permissions" />

<span id="control-account-access" />

<span id="control-who-can-use-an-account" />

<span id="delegate-access-to-applications-and-services" />

<span id="signing-methods" />

<span id="signing-thresholds" />

<span id="access-keys" />

<span id="key-management" />

<span id="fee-management" />

<span id="tempo-account-use-cases" />

<span id="what-you-can-build-with-tempo-accounts" />

<span id="building-on-accounts" />

<span id="accounts-and-wallets" />

<span id="fit-accounts-into-your-application" />

<span id="fund-accounts-and-reconcile-payments" />

<span id="put-an-account-to-use" />

<span id="connect-accounts-to-your-payment-system" />

<span id="what-do-you-want-to-do" />

<span id="create-an-account" />

<span id="embedded-wallets" />

<span id="consumer-self-custody" />

<span id="automations" />

<span id="ai-agents" />

<span id="spending-accounts" />

<span id="company-treasury" />

## Start Building

On mainnet, [create a single-key account](https://tempo.xyz/developers/docs/accounts/create#create-a-single-key-account) or support the [wallets your users already have](https://tempo.xyz/developers/docs/accounts/wallets). To try several signers and recovery, [create a configurable account](https://tempo.xyz/developers/docs/accounts/create#create-a-configurable-account) on the devnet. Then [add funds](https://tempo.xyz/developers/docs/accounts/fund).

:::warning
**Multiple signers arrive with the [T14 network upgrade](https://tempo.xyz/developers/docs/protocol/upgrades/t14).** Until T14 activates, an account with several signers and a threshold runs only on the [Tempo Accounts devnet](https://tempo.xyz/developers/docs/accounts/create#connect-to-the-devnet), not on mainnet or testnet, and may still change.
:::

[Set Up a Self-Custodial Wallet With a Provider](https://tempo.xyz/developers/docs/accounts/apps/self-custodial-wallets): Your provider's key and the user's passkey approve together, and only the user can recover or leave without you. Devnet until T14.

[Recover a User's Account](https://tempo.xyz/developers/docs/accounts/apps/recover-an-account): Replace a lost passkey with the signers the user still has, at the same address. Devnet until T14.

[Pay Out From a Backend](https://tempo.xyz/developers/docs/accounts/automations/pay-out-from-a-backend): Your backend pays approved payees, up to a daily limit, with a key in your KMS.

[Pay From a User's Embedded Wallet](https://tempo.xyz/developers/docs/accounts/automations/pay-from-an-embedded-wallet): A user's Privy or Turnkey wallet authorizes a key once, so your card or subscription backend pays within limits.

[Give an Agent a Wallet](https://tempo.xyz/developers/docs/accounts/automations/give-an-agent-a-wallet): An AI agent's own key, with a budget, an expiry, and only the calls it needs.

[Hold Customer Funds in an Omnibus Account](https://tempo.xyz/developers/docs/accounts/custodians/omnibus-accounts): A deposit address per customer, paying into one account that accepts only the stablecoins you list.

[Set Up a Team Multisig](https://tempo.xyz/developers/docs/accounts/custodians/team-multisig): Any two of three approvers sign each payment, so no one moves funds alone. Devnet until T14.

[Add Tempo to Your Wallet](https://tempo.xyz/developers/docs/accounts/wallets/add-tempo-to-your-wallet): Add the networks, show stablecoin balances, and send Tempo Transactions from your wallet.

<span id="account-features" />

## Related

[Signing Methods](https://tempo.xyz/developers/docs/accounts/authentication): Covers approving payments with a passkey, a key on the device, or a private key.

[Account Policies](https://tempo.xyz/developers/docs/accounts/policies): Covers requiring several approvals, and which stablecoins and senders can pay the account.

[Access Keys](https://tempo.xyz/developers/docs/accounts/access-keys): Covers keys that let a backend, a device, or an agent pay on its own, within limits you set.

[Account Configuration](https://tempo.xyz/developers/docs/accounts/account-configuration): Covers adding, removing, and rotating signers while the address stays the same.

[Fee Management](https://tempo.xyz/developers/docs/accounts/fees): Covers paying network fees in stablecoins, or paying them for your customers.

[Virtual Addresses](https://tempo.xyz/developers/docs/accounts/virtual-addresses): Covers giving each customer a deposit address that pays into one account.
