> For the complete documentation index, see [llms.txt](https://docs.aspanfi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aspanfi.com/agent-payments/operating-balance.md).

# ASPAN Account

ASPAN Account is the proposed shared workspace for agent payments and AI-managed funds. Owners define how money may be spent, how it may be invested, and when it must be available.

**Status:** the integrated account is planned. Existing DeFi and payment demonstrations use sample balances and simulated actions.

### Fund the account

The intended entry point is a deposit of a supported stablecoin. Each release must identify supported assets, chains, deposit routes, and payment routes. Funding the account does not automatically mint apUSD or buy an investment.

The owner can use permitted payment functions without opting into a yield strategy. Native ASPAN DeFi and planned ASPAN Vaults require separate investment authorization.

### Set three kinds of rules

* **Spending:** agent budgets, recipients, allowed assets, per-payment limits, authorization expiry, and approval requirements.
* **Investment:** approved strategies, asset and protocol exposure limits, leverage restrictions, and adjustment permissions.
* **Liquidity:** minimum liquid reserves, scheduled payments, withdrawal requirements, and how to handle a shortfall.

These are proposed controls. Production implementation must specify where they are enforced and how the owner can pause or revoke authority.

### Understand the balance

* **Available to pay:** liquid assets usable on the selected payment route after commitments and restrictions.
* **Reserved or committed:** funds set aside for approved payments or tasks; these cannot be counted again as freely investable.
* **Invested:** positions or shares with their own market, protocol, and exit risks.
* **Pending withdrawal:** requested exits that have not yet produced usable payment assets.

An account's total value is not its immediately spendable balance. Different payment assets are not interchangeable without an available conversion route and its costs.

### A team example

A team deposits $100,000 in a supported stablecoin. It expects $20,000 of payments over the next seven days, caps each agent payment at $500, requires approval for new recipients, and limits exposure to each yield protocol.

ASPAN would reserve funds for expected spending and the owner's additional liquidity buffer. Only the remaining authorized amount would be eligible for investment. The AI manager could propose or execute allocations within the approved rules, taking fees and exit timing into account.

If spending rises, it would reassess reserves and arrange permitted withdrawals. If usable funds are insufficient, the account would apply the owner's configured response, such as pausing a payment and requesting action. It would not assume investment shares can settle a bill immediately.

This is a product illustration, not a recommended allocation, return forecast, or live customer account.

### Review and retain control

The intended activity record connects each payment or investment action to its authorization, reason, fees, and outcome. Owners should be able to change future rules and revoke agent authority. Revocation stops new delegated actions; it does not reverse completed payments or remove a strategy's withdrawal conditions.

Read [Programmable Payments](https://docs.aspanfi.com/agent-payments/programmable-payments) for settlement behavior and [Product Status & Roadmap](https://docs.aspanfi.com/agent-payments/product-status-and-roadmap) for implementation status.

Explore [Rules & Permissions](https://docs.aspanfi.com/agent-payments/rules-and-permissions), [AI Capital Management](https://docs.aspanfi.com/agent-payments/ai-capital-management), and [Yield Options](https://docs.aspanfi.com/yield-options/yield-options) for the policies and strategies behind this workflow.
