# Sending assets

Sending works the same way across networks: a single guided send screen where you set the recipient and amount, review the fee, and authorise on your Physical Security Device (PSD). A few networks add options on top of this flow, covered in [Network-specific guidance](/helpcenter2/when-network-behaviour-differs.md).

A send doesn't leave your control immediately: it creates a request that follows the account's rules and is approved before it's broadcast. See [How requests and approvals work](/helpcenter2/getting-started/how-requests-and-approvals-work.md).

## Start a send

You can begin a send in two places:

* from the **Accounts list**, using the **Send** action on an account row, or
* from inside an **account**, using the **Send** button.

Either way you land on the send screen, pre-loaded with the account you're sending from.

## Fill in the transaction

**Recipient.** Click the recipient field to choose where the funds go. If your account's rules use whitelists, you select an approved contact (and when several whitelists apply, you can see which one an address belongs to). Where a custom address is allowed, you can type one in, and it's checked for valid format and screened against sanctions before you can continue.

**Amount.** Enter the amount in fiat by default, with the crypto-asset equivalent shown alongside; you can switch which one you type in, and the value is kept when you switch. Webapp 2.0 validates the amount as you go:

* A **warning** appears if the amount is above the available balance, below the minimum, or if the amount plus fee exceeds the available balance.
* An **error** appears if the amount doesn't match any of the account's rules, or if the fee can't be fetched.
* When the amount is valid, the **matching rule** is shown so you know which rule is authorising the transaction.

**Note (optional).** You can add a note of up to 256 characters that appears in the request for approvers.

## Fees

The transaction fee is **fetched automatically** once you've set the amount and shown in both crypto and fiat. It **refreshes every 15 seconds** to track network conditions. The figure shown is always a **maximum fee**: it's the ceiling authorised on your device, and the network may use less.

## Authorise on your device

When the transaction is complete and valid, the **create transaction** button becomes active and starts the review on your PSD. After you've reviewed the details on the device:

* if yours is the **only approval required**, you get a final confirmation and the transaction is broadcast;
* if **more approvals are required**, Webapp 2.0 tells you how many are still needed and lets you share a link to the request.

{% hint style="warning" %}
**Important:** Blocking reasons. If something is blocking the account (for example a workspace-level restriction), a message explains the blocking reason and the transaction can't be created until it's resolved.
{% endhint %}

Once the request is approved and broadcast, the account balance and [operations history](/helpcenter2/for-operators/operations-history-and-statuses.md) update.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.enterprise.ledger.com/helpcenter2/for-operators/sending-assets.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.