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

# Treasury overview

> How an isolated Wayex Treasury account funds, pays, converts, withdraws, and reconciles AUD and stablecoins.

Treasury is a prefunded PSP wallet for moving money on behalf of your business. You fund the account,
then use its balance to make AUD payouts, convert between AUD and supported stablecoins, or withdraw
stablecoin.

## One account, one boundary

Every login and API key belongs to one **tenant account**. That account has its own:

* AUD and stablecoin balances;
* funding instructions;
* fees, limits, rails, and networks;
* beneficiaries and stablecoin destinations;
* API keys, webhook subscriptions, users, and reporting.

If you operate accounts with different commercial terms, Wayex provisions them separately. Sign in
and prefund each one independently. Their money and records never net, spend, or report across
accounts. The login or API key determines the account, so money forms need no account selector.

<Warning>
  An API key for one tenant account cannot read or spend another account's wallet. Keep each
  account's credentials in a separate secret and choose the credential before starting a workflow.
</Warning>

## What you can do

<CardGroup cols={2}>
  <Card title="Fund" icon="building-columns" href="/treasury/funding-and-balances">
    Receive AUD through issued BSB/account instructions or deposit a supported stablecoin on the
    exact network shown.
  </Card>

  <Card title="Pay" icon="send" href="/treasury/beneficiaries-and-payouts">
    Save a BSB/account beneficiary, then create and track an AUD payout.
  </Card>

  <Card title="Convert" icon="arrow-right-arrow-left" href="/treasury/conversions-and-withdrawals">
    Review a short-lived quote and convert AUD to stablecoin or stablecoin to AUD.
  </Card>

  <Card title="Withdraw" icon="wallet" href="/treasury/conversions-and-withdrawals">
    Send an available stablecoin balance to a saved, validated destination on its matching network.
  </Card>

  <Card title="Track and reconcile" icon="list-check" href="/treasury/operations-and-reconciliation">
    Follow statuses, immutable wallet movements, webhooks, and external references.
  </Card>

  <Card title="Use the console" icon="window" href="/console/treasury">
    Run the same workflows from the institutional console without building an integration.
  </Card>
</CardGroup>

## Before you start

Your Wayex contact must activate Treasury for the tenant account and configure its commercial terms, limits,
rails, networks, and evidence policy. For an API integration, create a secret key with
`treasury:read` and `treasury:write`. A reporting integration only needs `treasury:read`.

Read the effective settings before exposing an action. Wayex enforces the same settings again when
you submit it; client-side checks improve the experience but never replace server-side policy.

## The wallet model

| Amount      | Meaning                                                                                           |
| ----------- | ------------------------------------------------------------------------------------------------- |
| `available` | Backed funds that can be used for a new operation.                                                |
| `reserved`  | Funds committed to accepted work but not yet captured or released.                                |
| `pending`   | Incoming funds detected but not yet spendable.                                                    |
| `total`     | The account's posted amount. Read the balance response for its exact composition and `asOf` time. |

An operation can only spend `available`. When Wayex accepts a payout, conversion, or withdrawal, it
moves the full source debit into `reserved` in the same durable decision. This prevents the same funds
from backing two operations.

<Info>
  `accepted` means validation passed, the balance was durably reserved, and execution can continue.
  It does not mean a bank payment, blockchain transaction, trade, or post-trade settlement
  completed.
</Info>

## First API check

Fetch the overview after authenticating. It confirms the account, balances, funding setup, and
enabled capabilities in one response.

```bash theme={null}
curl https://api.sandbox.wayex.com/v1/treasury \
  -H "Authorization: Bearer $WAYEX_SECRET_KEY"
```

Then fetch the tenant-level effective settings before building forms or sending money:

```bash theme={null}
curl https://api.sandbox.wayex.com/v1/treasury/configurations/effective \
  -H "Authorization: Bearer $WAYEX_SECRET_KEY"
```

Both calls are read-only and need no idempotency key. Browse their request and response schemas in
the [API reference](/api-reference/overview).

## Environment safety

The sandbox URL is an integration environment. It may be connected to controlled live-provider
rails for an explicitly enabled tenant. Treat every funding instruction as value-bearing and never
send funds until Wayex confirms the environment, asset/network, and test limit for your account.

## Choose a workflow

* Start with [Funding and balances](/treasury/funding-and-balances) to make money available.
* Continue with [Beneficiaries and payouts](/treasury/beneficiaries-and-payouts) for AUD delivery.
* Use [Conversions and withdrawals](/treasury/conversions-and-withdrawals) for FX and stablecoin delivery.
* Implement [Operations and reconciliation](/treasury/operations-and-reconciliation) before going live.