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

# Transfer Flow

> How to move funds out of a Treasury Account: the enter-amount screen, the confirmation screen, and how to simulate a transfer’s outcome with the API.

A **transfer** moves funds out of a [Treasury Account](/platform-overview/clever-concepts/treasury-accounts) to a recipient. Because Treasury Accounts always use the [Dedicated Balance](/platform-overview/clever-concepts/balance-models) model, the transfer is taken only from the selected account’s balance; no other account is affected. This page walks through the transfer screens and how to test a transfer’s outcome.

<Note>
  A transfer out of a Treasury Account is an [Account Transfer](/platform-overview/clever-concepts/moving-money). This page focuses on the step-by-step experience and how to simulate the result.
</Note>

## The Transfer screen

When you start a transfer, the **Transfer** screen shows:

* **Transfer from** - A dropdown to select the source Treasury account.
* **Who are you transferring to?** - A search bar for finding saved recipients.
* **New recipient button** - a button that opens the **Enter recipient details** page where the new recipient’s details are entered.
* **Recipients list** - provides a list of saved recipient accounts. Select the one that you want to transfer to.

## The Enter amount screen

Once you’ve selected the recipient, the **Enter amount** screen shows:

* **You transfer exactly**: the amount taken from your Treasury Account balance.
* **Recipient gets exactly**: the amount the recipient receives after fees.
* **Total fees (included)**: the fees, already factored into the figures above.
* **Transfer from**: the source Treasury Account.
* **Recipient**: the recipient’s name plus their BSB, account number, account name, email, and phone number.
* **Should arrive**: the expected delivery time (typically within a few hours on weekdays; the next working day on weekends).

You can also add an optional **Reference** and **Description**, then click **Continue** to review and confirm the transfer.

### Worked example

Transferring AUD 788 from the Amuseables Espresso Cup Treasury Account, the recipient receives AUD 716.36 after AUD 71.64 in fees. The available balance of AUD 1,388.00 sits on that specific Treasury Account only; no other account is touched.

| Field                  | Value      |
| ---------------------- | ---------- |
| You transfer exactly   | AUD 788.00 |
| Total fees (included)  | AUD 71.64  |
| Recipient gets exactly | AUD 716.36 |

***

## After you confirm

Once you confirm, you will see a “Your transfer has been created” screen. At this point the transfer’s status is **Processing**; it has been created but has not yet settled.

This screen summarises the transfer (amount sent, fees, recipient gets, recipient details, and expected arrival) and shows a **Balance ID** at the top, for example `po_1tjreKKucrcM`. This Balance ID is the transfer’s unique identifier (its `uuid`), and you will need it to simulate the transfer’s outcome in the next step. You can copy it directly from this screen.

<Steps>
  <Step title="Enter the amount and recipient">
    On the Enter amount screen, set the amount and review the recipient and fee details, then click **Continue**.
  </Step>

  <Step title="Review and confirm">
    Check the summary and confirm the transfer.
  </Step>

  <Step title="Transfer is created (Processing)">
    You see the confirmation screen. The status is **Processing**, and a **Balance ID** is shown; copy it for the next step.
  </Step>
</Steps>

***

## Simulating a transfer outcome (API)

A newly created transfer stays in **Processing**. To test how your integration behaves when a transfer succeeds or fails, you can simulate its final outcome with the simulate transfer API.

**Method:** `POST`
**URL:** `{{v2_url}}/transfers/simulate` (for example, `https://api.cleverhub.co/api/v2/transfers/simulate`)

Headers:

| Header       | Value                   |
| ------------ | ----------------------- |
| `app-id`     | Your store’s App ID     |
| `secret-key` | Your store’s secret key |

<Note>
  Not sure where these come from? See [where to find `app-id` and `secret-key`](/platform-overview/clever-concepts/treasury-accounts#where-to-find-app-id-and-secret-key).
</Note>

Request body:

```json theme={null}
{
  "uuid": "po_Vht3sk482nGH",
  "status": "completed"
}
```

Response body:

```json theme={null}
{
    "http_status": 200,
    "response": {
        "status": "ok"
    }
}
```

Field reference:

| Field    | Description                                                                                              |
| -------- | -------------------------------------------------------------------------------------------------------- |
| `uuid`   | The transfer’s identifier, the Balance ID shown on the confirmation screen (e.g. `po_1tjreKKucrcM`).     |
| `status` | The outcome to simulate. Valid values are `completed` (mark as successful) or `failed` (mark as failed). |

After the call, the transfer moves out of Processing to the status you chose, and the result is reflected in the account’s balance and transaction history. Use `completed` to verify the successful path, and `failed` to confirm how your integration handles failed transfers.


## Related topics

- [Managing Balances and Accounts](/portal/balances.md)
- [Moving Money: Settlements, Withdrawals, and Transfers](/platform-overview/clever-concepts/moving-money.md)
- [Treasury Accounts](/platform-overview/clever-concepts/treasury-accounts.md)