> 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/others/faqs.md).

# FAQs

### What is ASPAN?

ASPAN is building a programmable account for AI agents that combines payments and AI-managed yield under the owner's spending, investment, and liquidity rules.

### Do I need apUSD to use the account?

The planned account separates stablecoin funding from investment selection. Users would deposit an asset supported by a particular release and could authorize payments without buying apUSD, s-apUSD, or Vault shares. Supported chains, assets, and funding routes have not been finalized by this documentation.

### What is available today?

The existing source foundation is native ASPAN DeFi. The prototype demonstrates DeFi and payment flows with sample balances and simulated approvals. The integrated account, independent policy enforcement, AI management, and external-strategy ASPAN Vaults remain planned. See [Product Status & Roadmap](https://docs.aspanfi.com/agent-payments/product-status-and-roadmap).

### What does the AI manager do?

It is intended to estimate upcoming cash needs, identify funds eligible for investment, compare approved strategies after costs, and decide when to adjust or exit. Execution must remain within independently enforced permissions. Better performance than simple rule-based management still needs to be demonstrated.

### What are the two yield options?

**Native ASPAN DeFi** uses the existing BNB collateral and apUSD / s-apUSD / xBNB structure. **ASPAN Vaults** are a planned separate option for allocating to approved external yield protocols. Both require explicit investment authorization and strategy-specific risk and exit disclosures.

### Where does yield come from?

Native DeFi distributes income from its underlying staking assets according to protocol rules. Planned external-strategy Vaults would receive actual income from their underlying protocols, such as lending interest or disclosed rewards. AI and Vault shares do not create an additional guaranteed source of yield.

### Is ASPAN Vaults the same as the s-apUSD vault?

No. The existing apUSD staking vault, or Stability Pool, issues s-apUSD and belongs to native ASPAN DeFi. Planned ASPAN Vaults would have their own mandates, accounting, share structure, and external integrations. s-apUSD is not a universal share token for the new Vaults.

### Can all my funds earn and remain instantly spendable?

No. The account must distinguish available payment funds, committed funds, investments, and pending withdrawals. Investment proceeds become spendable only after any required exit and conversion completes. A higher total account value does not guarantee a payment can settle now.

### What happens if a payment needs funds that are invested?

The proposed manager would plan permitted exits against payment deadlines. If liquidity is insufficient, the account must follow the owner's configured response, such as pausing the payment and requesting action. It cannot assume immediate redemption or expand its mandate to cover a shortfall.

### Can I revoke an agent's authority?

Scoped authorization, expiry, owner approvals, and revocation are planned account requirements. Revocation should stop new delegated actions; it does not undo confirmed payments or waive withdrawal conditions on existing investments.

### What are apUSD, s-apUSD, and xBNB?

apUSD is a dollar-denominated native protocol liability designed to target $1. s-apUSD represents shares in its staking vault. xBNB is the residual collateral claim with variable leveraged exposure and can lose all value. The $1 target and vault withdrawals are not guaranteed; stability-mode withdrawals may include xBNB. See [Native ASPAN DeFi](https://docs.aspanfi.com/core-concepts/the-dual-token-model).

### What are the DeFi fees?

In the documented 150%–170% collateral-ratio reference band, apUSD minting is 0.1% and redemption is 0.3%; xBNB minting and redemption are each 1%. The complete [Dynamic Fee](https://docs.aspanfi.com/aspan-mechanics/dynamic-fee) table remains a native DeFi reference, subject to contract configuration and the actual quote. Network and conversion costs are separate.

### Will there be a subscription?

ASPAN plans optional team subscriptions for account controls and reporting. These features are not yet available; pricing will be announced when ready. No account, payment, or external-strategy Vault price is established by the native DeFi fee table.

### What has been audited?

The [initial Adevar Labs report](https://github.com/AdevarLabs/audit-reports/blob/main/reports/2026-03-19_Aspan_Finance_audit_report.pdf), dated 19 March 2026, covers only the existing DeFi scope. It does not cover the payment layer, new account and AI execution controls, or planned ASPAN Vaults. See [Smart Contract Security](https://docs.aspanfi.com/risk-management/smart-contract-security).

### Does ASPAN support x402 or RWA strategies today?

x402 compatibility remains planned. RWA strategies are a possible expansion requiring asset-specific integration, eligibility, and redemption checks. Neither is established as a production integration in these docs.

### How can I explore the concept?

The [interactive payment prototype](https://aspanfi.xyz/app/payments) illustrates selected flows using simulated actions. Start with [ASPAN Account](https://docs.aspanfi.com/agent-payments/operating-balance) to understand the broader planned experience.
