> ## 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

> Use the client console to fund, pay, convert, withdraw, track, and configure one isolated Treasury account.

The **Treasury** area is the client-facing PSP workspace for one tenant account. It shows the same
wallet and operations available through the Treasury API.

## Account isolation

Your login opens one account with its own balances, fees, limits, users, API keys, webhooks, and
history. Staff use the login for the account they intend to operate. The login determines the
account for every money form.

<Warning>
  Confirm the account identity in the console header before funding or submitting an operation.
  Funds cannot be spent or netted across the two accounts.
</Warning>

## Pages

| Page              | What you do there                                                                                                     |
| ----------------- | --------------------------------------------------------------------------------------------------------------------- |
| **Overview**      | Read available, reserved, pending, and total balances; check freshness, recent activity, and action-required notices. |
| **Funding**       | Copy AUD or stablecoin instructions and follow incoming funding until it becomes available.                           |
| **Beneficiaries** | Create and review individual or business BSB/account recipients and identity-evidence state.                          |
| **Payouts**       | Preview fees and source debit, confirm an AUD payout, and follow settlement or return state.                          |
| **Convert**       | Review and accept an expiring AUD/stablecoin quote, then follow physical settlement progress.                         |
| **Withdraw**      | Manage destinations, preview fees and source debit, then confirm and track a withdrawal.                              |
| **Transactions**  | Filter cursor-paginated wallet and operation history, inspect references, and export a bounded CSV.                   |
| **Settings**      | Read the effective fees, limits, rails, networks, and evidence requirements for this account.                         |

## Money actions

Payout, conversion, and withdrawal forms follow the same pattern:

<Steps>
  <Step title="Enter the request">
    Select a saved beneficiary or destination and enter the amount. Add a client reference only when
    your own system uses one for reconciliation.
  </Step>

  <Step title="Review the request and effective terms">
    The console calls the payout or withdrawal preview endpoint and shows its principal, fee, source
    debit, eligibility, and any hold reason. For conversion, the exact expiring quote is the preview
    and also shows the all-in rate, destination amount, available source balance, and network. The
    console keeps the generated quote ID internal. No preview reserves money.
  </Step>

  <Step title="Confirm with MFA">
    Operators and administrators complete a fresh MFA step-up before the console submits the action.
  </Step>

  <Step title="Follow the operation">
    The console keeps the same action identity across MFA and safe retries, then shows reservation,
    external settlement, reason, and next action.
  </Step>
</Steps>

`accepted` means the source debit was durably reserved; it is not a bank or blockchain receipt. Keep
the operation open until its detail shows the terminal outcome.

The create request repeats policy, balance, screening, and provider checks after confirmation. If
conditions changed after preview, the console shows the authoritative create error or hold instead
of assuming the earlier preview still applies.

## Funding safely

Copy instructions from **Funding** immediately before use. For a stablecoin deposit, check the asset
and network together. Incoming money appears as pending while it is detected, confirmed, and screened,
then becomes available only after the wallet credit.

If a funding record is held, the page shows whether you should wait or contact support. Stale or
unavailable provider data appears as unavailable—not as a zero balance.

## Transactions and exports

Transactions are loaded from the server in cursor pages. Filters for reference, type, status, and
date range remain fixed while the console passes each opaque `nextCursor` unchanged. The CSV action
uses the same filters and downloads at most 5,000 non-PII rows. If the selection is larger, narrow
the date range or filters and export again.

## Roles

| Role         | Treasury access                                                                                                                      |
| ------------ | ------------------------------------------------------------------------------------------------------------------------------------ |
| **Viewer**   | Read balances, funding, activity, statements/exports, and effective settings.                                                        |
| **Operator** | Viewer access plus beneficiary, payout, conversion, and withdrawal actions.                                                          |
| **Admin**    | Operator access plus funding instruments, stablecoin destinations, API keys, webhooks, team, and account settings allowed by policy. |

The API enforces tenant and role access even if a button is hidden in the browser. See
[Team and roles](/console/team-roles).

## When something is unclear

Open the operation and read its status reason, reservation state, settlement step, references, and
next action. Never submit a replacement simply because the first result is slow or unknown. Use the
request ID when contacting support, but never include an API key, signing secret, Sumsub token, or
unnecessary beneficiary data.

For integration behavior, start with the [Treasury overview](/treasury/overview) and then browse the
[API reference](/api-reference/overview).