# transfer_to_recipient_id · FT4 Rell API · Chromia Docs (concept)

> function transfer_ to_ recipient_ id(sender: account , recipient_ id: byte_ array, asset: asset , amount: big_ integer) Transfers tokens to a certain recip

Source: https://docs.chromia.com/pages/ft4-rell/-f-t4-library/lib.ft4.core.assets.Unsafe/transfer_to_recipient_id/

FUNCTION

# transfer\_to\_recipient\_id

```signature
function transfer_to_recipient_id(sender: account, recipient_id: byte_array, asset: asset, amount: big_integer)
```

[Source](https://gitlab.com/chromaway/ft4-lib/-/blob/development/rell/src/lib/ft4/core/assets/transfer.rell#lines-78)

Transfers tokens to a certain recipient. If the recipient exists, a normal transfer
will take place. Otherwise, if account creation on transfer is enabled, the account
creation procedure will be started.
Marked as Unsafe because it does not check whether the account authorized the transfer.

Throws if the required assets cannot be transferred. Common cases include:

* the amount to transfer is not in the accepted range (0, 2^256) (exclusive)
* some conditions added in development through transfer extensions (`before_transfer` or
  `after_transfer`) aren't met
* the sender account's balance is lower than `amount`

Throws `"INVALID RECIPIENT ID"` if the recipient's id length is longer than 1024 bytes

Throws `"INVALID RECIPIENT"` if the recipient does not exist and
`is_create_on_internal_transfer_enabled` returns false.

Can only be called from operations.

**Parameters**

* **sender** — the account that started the transfer
* **recipient\_id** — the account that should receive the transfer or be created
* **asset** — the asset that should be sent
* **amount** — the amount to transfer

[View this page on docs.chromia.com](https://docs.chromia.com/pages/ft4-rell/-f-t4%20-library/lib.ft4.core.assets.Unsafe/transfer_to_recipient_id.html)Generated API reference, mirrored from the live docs