Skip to main content
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

Org admins see the current balance for the network they’re on in two places: the Payments page, where agentic.anchorage.com lands you after sign-in, and the Budgets tab of your organization’s page. Both show the available balance and the held amount separately. Plain org members don’t see the org balance; their Payments page stops at their own budget slice (see Budgets). The held amount is money set aside for something still in progress: a payment, incoming funds in compliance screening, or a withdrawal. Select the held amount to open Held funds, which lists each hold behind it with its amount, the reason it is held, the payment or deposit history it belongs to, the agent that started it for a payment, and when it was placed. The listed holds add up to the total at the bottom of the page. An account with more than 500 holds shows the total without listing them. Holds clear when a payment or withdrawal finishes, or when a deposit clears screening. A deposit that needs sender details stays held until you provide them on the Deposit page and screening passes. A deposit blocked on screening stays held until compliance review releases it.

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. While an account is locked for review, its deposit addresses are unavailable — the Deposit page says so in place of the address, and both generating a new address and viewing the current one wait until the lock lifts — while the account’s deposit history stays visible. Deposits arrive the same way whoever sends them. When the sender is another Anchorage Agentic Banking customer — an agent paying for your priced service, say — that payment credits your account like any other arrival, and the paying account is debited by the same transfer. A crypto deposit moves through four steps before it’s spendable:
  1. Deposit — on the Deposit page, pick the chain you’re depositing on to see its address, then send funds there. 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. The Deposit page shows the rate each accepted token converts at, so you can check what a deposit will credit before you send it. Your deposit history shows the USD amount a deposit credited once that amount is on record, older deposits included.
  3. Screen — a confirmed deposit still needs to clear compliance screening before the funds release. Each deposit carries one of these labels: 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, 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. 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.

What the agent sees

The agent sees the spend limit configured by the budget it draws on: its allotted cap and spend-to-date. See Budgets for the limit model.