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

# Activity and history

> Follow direct-route transfers and reconcile Treasury wallet activity inside one tenant account.

The console gives you a running view of everything that is moving: a live **activity feed**, a per-transfer
**detail view** with its full lifecycle timeline, and a **Revenue & fees** report.

## Activity feed

A live activity feed runs down the left side of the console. It shows recent transfers across **all** of
your customers in reverse-chronological order — corridor (on-ramp or off-ramp), customer, the amount in and
out, and the current status — so you always have a running history of what is moving without leaving the
page you are on.

* **Status is shown explicitly** — held, failed, and returned transfers carry their own tone and are never
  collapsed into a generic "success".
* The feed refreshes on its own, and each item links straight to that transfer's detail view.

## Transfer detail & timeline

Select any item in the activity feed — or open a conversion from a [payment route](/console/payment-routes) —
to see the complete picture of a single transfer:

<CardGroup cols={2}>
  <Card title="Summary" icon="receipt">
    The corridor, customer, the amount you send and the amount the customer receives, and the
    destination (AUD bank account or crypto address).
  </Card>

  <Card title="Funding instructions" icon="building-columns">
    While a transfer is still awaiting the customer's deposit or pay-in, the funding instructions
    are shown here to share with them.
  </Card>

  <Card title="Lifecycle" icon="timeline">
    A progress checklist plus a timeline of every state change — what happened and when. Held and
    failed states appear as an explicit banner with their reason.
  </Card>

  <Card title="References" icon="link">
    Linked references for reconciliation — including the route the funding arrived on, the executed
    FX trade, the on-chain transaction, and the AUD rail reference — appear as the transfer
    progresses.
  </Card>
</CardGroup>

While a transfer is still in progress, the detail view refreshes automatically so you see the current
state without reloading. You can also refresh on demand.

## Revenue & fees

The **Revenue & fees** screen reports **your developer fees** — the markup you configure and charge your
end customers on each conversion. It is scoped to your organisation only.

* **Headline totals** per asset, with the number of completed transfers.
* A **by-asset breakdown** of your fees.
* A **time series** you can view at daily, weekly, or monthly granularity.

All amounts are shown with their currency exactly as reported. Your fees appear here once transfers
complete, so the view fills in as you move money.

## Treasury transactions

Treasury has its own **Transactions** page because its wallet movements are different from direct-route
customer transfers. Use it to search credits, reservations, captures, releases, fees, returns,
conversions, payouts, and withdrawals for the signed-in tenant account.

Open an operation to see its source debit, fee, reservation, settlement step, external references,
reason, and next action. `accepted` and `submitted` do not mean external settlement. Exported CSV data
uses the same account boundary and must not be combined with another account as if their balances net.

See [Console Treasury](/console/treasury) and
[Operations and reconciliation](/treasury/operations-and-reconciliation).

<Note>
  The exchange rate you and your customers see is the **all-in rate Wayex quotes** — Wayex's margin
  is inside the rate and is not your revenue, so it never appears in this report. Your revenue is
  your **developer fee**: a markup you configure (see [Developer
  fees](/console/developers#developer-fees)) that is withheld from each conversion's payout and
  credited against your monthly Wayex invoice.
</Note>

## Billing & invoices

Wayex bills platform fees on a monthly invoice, and your accrued developer fees are credited against it:

* **Platform fees due** — the per-event fees on your Wayex plan (for example verification or transfer
  fees) for the period.
* **Developer-fee credit** — the developer fees withheld from your conversions during the period, owed
  to you.
* **Net due = platform fees due (plus any tax) − developer-fee credit.** A negative net due means Wayex
  owes you for the period.

Retrieve your invoices through the API: `GET /v1/invoices` lists your issued and settled invoices, and
`GET /v1/invoices/{id}` returns one with its line items, the developer-fee credit, and an informational
memo of what was already collected in-flow. All amounts are exact decimal strings with an explicit
currency.