> 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/programmable-payments.md).

# Programmable Payments

ASPAN's planned payment workflow lets an authorized agent pay for services from usable liquid funds in an ASPAN Account. Payment rules operate alongside investment and liquidity rules, so investing does not consume funds already needed for approved spending.

**Current status:** the prototype's conditional, streaming, escrow, and split flows use sample apUSD balances and simulated approvals. The broader account design supports release-specific payment assets; this is not a claim that additional token routes are already integrated.

### Authorize a payment

A spending policy should identify the agent, allowed assets and recipients, per-payment and total budgets, expiry, and any required owner approval. New recipients or payments outside the existing mandate require the relevant approval before execution.

Payment permission alone does not allow the agent to buy a yield strategy, borrow, or change investment rules.

### Check liquidity and settle

Before settlement, the account must check the payment rule, available balance, commitments, route costs, and the actual asset the recipient accepts. Invested funds may need to be withdrawn and converted first.

A planned withdrawal is not a settled balance. When funds cannot arrive in time, the account should follow its configured shortfall rule and notify the owner. It must not silently increase risk limits or assume credit is available.

### Payment patterns

**Conditional payments:** release funds after a defined acceptance rule. Production terms must specify evidence, the verifier, deadlines, and the outcome when a condition fails or cannot be established.

**Streaming payments:** accrue amounts while a service runs, subject to a rate, budget cap, and authorized start and stop controls. Stopping future accrual does not refund amounts already earned.

**Escrow:** commit a budget until acceptance, refund, or dispute resolution. Release authority, timeouts, and dispute rules must be explicit.

**Split payments:** distribute a settlement among specified recipients. The implementation must validate allocation totals, rounding, authorization, and partial-failure behavior.

These patterns are concept demonstrations. Production priorities should follow the payment needs established with design partners.

### Payment records

The intended record includes the authorized agent, recipient, asset, amount, fees, applicable rule, transaction status, and receipt or acceptance evidence. A submitted transaction must not be labeled as successfully settled before confirmation.

### Integrations and release status

Provider adapters, agent-SDK integrations, and x402 compatibility remain planned and require validation for each chain, asset, and settlement route. The streaming demo does not establish an implemented Superfluid integration.

[Explore the payment concept demo](https://aspanfi.xyz/app/payments), or see [Product Status & Roadmap](https://docs.aspanfi.com/agent-payments/product-status-and-roadmap).
