# Sends \[Move tokens from an account to any recipient]

A send moves tokens from one of your [accounts](/docs/accounts) to any recipient: a raw address, an ENS name, a Farcaster username, a saved [contact](/docs/contacts), another of your accounts, or (with [banking](/docs/banking) set up) a bank account. The amount you enter is the amount **the recipient receives**. NFTs (ERC-721 and ERC-1155) can be sent the same way.

You can send a token the account doesn't hold: as long as the account holds enough value to cover it, pick which token to sell and the swap and send execute as one transaction. See [just-in-time swaps](/docs/transactions/swaps#just-in-time-swaps).

## Memos

Add a [memo](/docs/transactions/memos) when creating the send; it makes your [accounting](/docs/accounting) dramatically easier later.

## Batching

Instead of submitting a send right away, select *Add to batch* in the review dialog to group it with other transactions under one signature. See [Batch](/docs/transactions/batch).

## Signing

Like every [transaction](/docs/transactions), a send executes once signatures meet the account's [threshold](/docs/accounts/thresholds): immediately on a 1-of-n account, after the remaining signatures otherwise.

## Recurring sends

To pay out pre-defined amounts on an interval (e.g. payroll), use [Schedules](/docs/transactions/schedules).

## Programmatic access

Via the [Splits CLI / MCP](/docs/introduction/agents):

* `splits transactions create transfer --account 0x... --chainId 8453 --recipient 0x... --token 0x... --amount 100`: propose a transfer, with optional `--memo` and `--properties` (**Write** scope)