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

# Wallets and payments

> Separate balances, payment initiation, provider flows, and transaction lifecycle state

Wallet and payment integrations combine account authorization, value semantics, provider selection, initiation, and asynchronous transaction state. A balance read and a completed payment are different workflows.

## Transaction model

```text theme={null}
Authorized account
        ↓
Confirm environment and value semantics
        ↓
Read balance and supported provider/options
        ↓
Initiate an operator-approved payment flow
        ↓
Persist transaction identifier
        ↓
Observe pending → finalized or failed
        ↓
Reconcile balance and audit information
```

## Protect credentials and value

* Confirm whether the environment contains test value or real value.
* Confirm the supported wallet/payment product and provider before initiating anything.
* Do not infer financial harmlessness from a hostname containing words such as `dev`, `test`, or `sandbox`.
* Require explicit human approval before an AI application performs a value-moving tool call unless a separately approved policy defines a safe autonomous boundary.
* Keep credentials and bearer tokens out of browser code and logs.
* Do not retry initiation blindly; use documented idempotency and transaction-state behavior.

## Product availability

Agent API wallet operations and Neuro-Pay are separate interfaces. Ask the Neuron operator which product and provider are supported before implementing a payment flow.

## Build a payment integration

* [Build a payment integration](/build/payments/overview)
* [Wallet reference](/neuron-api/api-reference/wallet/overview)
* [Prepare a development environment](/get-started/environments)