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

> @extendable function after_ init_ transfer(sender: account , recipient_ id: byte_ array, asset: asset , amount: big_ integer, hops: list<byte_ array>, dead

Source: https://docs.chromia.com/pages/ft4-rell/-f-t4-library/lib.ft4.core.crosschain/after_init_transfer/

FUNCTION

# after\_init\_transfer

```signature
@extendable function after_init_transfer(sender: account, recipient_id: byte_array, asset: asset, amount: big_integer, hops: list<byte_array>, deadline: integer, pending_transfer: pending_transfer)
```

[Source](https://gitlab.com/chromaway/ft4-lib/-/blob/development/rell/src/lib/ft4/core/crosschain/extensions.rell#lines-46)

Extendable function that allows the developer to add more functionality to the
`init_transfer` function, after the transfer is initialised.

This allows, for example, to check that any condition is met after the transfer is
initialised.

If this function throws, the transfer will not be initialized.

Throws when any extension of this function throws.

**Parameters**

* **sender** — the account that has transferred the tokens
* **recipient\_id** — the ID of the recipient account on the end chain
* **asset** — the asset that was transferred
* **amount** — the amount that was transferred
* **hops** — the IDs of the chains this transfer will go through
* **deadline** — a timestamp after which the transfer can only be recalled

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