Skip to main content
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.
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.

​
What you can do

Fund

Receive AUD through issued BSB/account instructions or deposit a supported stablecoin on the exact network shown.

Pay

Save a BSB/account beneficiary, then create and track an AUD payout.

Convert

Review a short-lived quote and convert AUD to stablecoin or stablecoin to AUD.

Withdraw

Send an available stablecoin balance to a saved, validated destination on its matching network.

Track and reconcile

Follow statuses, immutable wallet movements, webhooks, and external references.

Use the console

Run the same workflows from the institutional console without building an integration.

​
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

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

​
First API check

Fetch the overview after authenticating. It confirms the account, balances, funding setup, and enabled capabilities in one response.
Then fetch the tenant-level effective settings before building forms or sending money:
Both calls are read-only and need no idempotency key. Browse their request and response schemas in the API reference.

​
Environment safety

The sandbox (https://api.sandbox.rails.wayex.com) is fully simulated: no real funds ever move, and its funding instructions are test fixtures. Production (https://api.rails.wayex.com) moves real funds — confirm the asset and network, and start with small amounts before your first production funding.

​
Choose a workflow