<!-- tempo-docs-context -->
> Source: [/docs/accounts/policies](https://tempo.xyz/developers/docs/accounts/policies.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.

# Account Policies

Enforces onchain who can move an account's funds and who can pay it.

## Overview

A policy is a rule Tempo enforces onchain for an account, so your app doesn't have to.

A Tempo account has two policies, one for each direction money moves. A [signing threshold](https://tempo.xyz/developers/docs/accounts/policies/signing-thresholds) covers funds going out. A [receive policy](https://tempo.xyz/developers/docs/accounts/policies/receive-policies) covers payments coming in.

<span id="escalation-rules" />

<span id="private-policies" />

<span id="what-a-policy-controls" />

<span id="control-money-out-and-money-in" />

<span id="policies" />

<span id="what-account-policies-control" />

<span id="tempo-account-policy-types" />

<span id="tempo-account-policies" />

<span id="what-a-policy-is" />

<span id="how-it-works" />

## Policy Checks

Tempo checks each policy onchain:

* **Outgoing Funds:** Tempo checks the signing threshold on every transaction the account sends.
* **Incoming Funds:** Tempo checks the receive policy on every transfer and mint to the account.

No one can skip either check, including your app, your wallet provider, Tempo, a breached backend, or a buggy client.

<span id="combine-account-policies" />

<span id="combine-policies" />

## Combined Policies

The two policies work independently. Without a receive policy, an account accepts every transfer the token itself allows. Add one only when the account must refuse some stablecoins or senders.

Spending limits aren't a policy. They belong to [access keys](https://tempo.xyz/developers/docs/accounts/access-keys), which pay alone within their limits and never count toward the threshold.

## Related

[Signing Thresholds](https://tempo.xyz/developers/docs/accounts/policies/signing-thresholds): Covers who can move funds out, through signer weights and a threshold. Devnet until T14.

[Receive Policies](https://tempo.xyz/developers/docs/accounts/policies/receive-policies): Covers which stablecoins and senders can pay the account, and how Tempo holds the rest.

[Access Keys](https://tempo.xyz/developers/docs/accounts/access-keys): Covers keys that pay alone within their spending limits.
