> ## Documentation Index
> Fetch the complete documentation index at: https://docs.anchorage.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Accounts

> Your org's USD balance per network, and how to fund it.

An **account** is your org's balance on Anchorage Agentic Banking. Your org
has one account per network it runs on (mainnet and/or testnet), each
denominated in **USD** as a single decimal figure. Every member of the org
accesses their org's accounts through their org membership.

## Where to find it

The **dashboard** (the home page in [agentic.anchorage.com](https://agentic.anchorage.com)
after sign-in) shows org admins the current balance for each network. It
also shows the amount held against pending payments and approvals, so the
dashboard displays both the **available** balance and the **held** amount
separately. Plain org members don't see the org balance; their dashboard
view stops at their own budget slice (see [Budgets](/agentic-banking/concepts/budgets)).

## How it gets funded

The **Deposit** page in the web UI is the funding entry point. Anchorage
Agentic Banking generates a deposit address for each crypto chain it
supports.

A deposit moves through four steps before it's spendable:

1. **Deposit** — send funds to your account's deposit address. Some
   addresses need one-time setup before they're ready to receive funds; the
   Deposit page warns you if yours does. Follow that warning before sending
   funds. Testnet and mainnet deposit addresses are different: copy the
   address shown for the network you are transacting on — funds sent to the
   other network's address land in a separate balance.
2. **Confirm** — the deposit shows as **pending** until the chain confirms
   (seconds in practice), then moves to **confirmed**. Anchorage Agentic
   Banking converts the incoming crypto to USD as part of that step, so the
   balance you see is always one USD figure regardless of which chain the
   deposit came in on.
3. **Screen** — a confirmed deposit still needs to clear compliance
   screening before the funds release. Each deposit carries one of these
   labels:

   | Label                 | Meaning                                               |
   | --------------------- | ----------------------------------------------------- |
   | Needs attribution     | We need the sender's details before the funds release |
   | Reviewing attribution | Details received, review in progress                  |
   | Cleared               | Review passed, funds available                        |
   | Blocked on screening  | Review did not pass                                   |

   When a deposit reads **Needs attribution**, the form to provide the
   sender's name and country appears directly in your deposit history — no
   extra step to open it. Submitting those details runs the review and, if
   it passes, releases the funds in the same step. After you attribute a
   self-hosted sender once, later deposits from that same sender in your org
   can reuse those details automatically; each deposit still runs screening
   before the funds become available, so a later review can still leave
   funds blocked.
4. **Release** — once a deposit reads **Cleared**, the funds are available
   to spend.

Bank linking and ACH deposits are on the roadmap.

## How budgets draw against the account

When an agent spends against a [budget](/agentic-banking/concepts/budgets), the spend
consumes part of the account's USD balance, bounded by the budget's cap.

## What spends from the account

Today, the account funds **crypto payments** — each crypto spend draws
from the USD balance. Linked-card purchases settle through the card's own
issuer rather than through the account, so a linked-card spend leaves the
account balance alone. See [Cards](/agentic-banking/concepts/cards) for the linked-card
flow.

Spending directly from the account at card-accepting merchants is on the
roadmap — it would let an agent use the account balance at any merchant
that takes cards, with no external card linked.

## What the agent sees

The agent sees the **spend limit** configured by the budget it draws on:
its remaining cap and reset window. See [Budgets](/agentic-banking/concepts/budgets) for
the limit model.