> For the complete documentation index, see [llms.txt](https://help.tokenpocket.pro/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tokenpocket.pro/en/transfer-tutorial/token-batchsender.md).

# TokenPocket Multi-chain Token Batch sender

The batch transfer feature allows users to transfer the same native asset to multiple receiving addresses at once. It is suitable for scenarios such as batch distribution, batch payments, or asset allocation across multiple addresses.

TokenPocket’s batch transfer feature can help users reduce repetitive transfer operations. Users only need to select the token to be transferred, add multiple receiving addresses and corresponding amounts one by one, and then complete the batch transfer at once after confirming the transaction details.

Currently, this feature is only available on iOS devices. Android support will be available later. Please refer to the actual display in the TokenPocket App.

***

#### Feature Description <a href="#feature-description" id="feature-description"></a>

Batch transfer is applicable to transferring assets from the current wallet address to multiple addresses, such as public chain assets on BNB Chain, Ethereum, Polygon, and others. Users can set different transfer amounts for each receiving address and view the network fee, payment method, and transaction details together before submission.

Please note that batch transfer is an on-chain transaction. Once the transaction is initiated and successfully recorded on-chain, it cannot be revoked. Therefore, before confirmation, please carefully check the receiving addresses, transfer amounts, payment method, and network fees.

***

#### Enter the Batch Transfer Feature <a href="#enter-native-batch-transfer" id="enter-native-batch-transfer"></a>

Users can enter “More Tools” from the asset page of the TokenPocket wallet and find “Native Batch Transfer” in the tool list.

More Tools supports two types of batch collection. One is native batch collection, which is more suitable for mobile operations, while the other batch collection tool is a DApp, which is more suitable for operation through the web. It supports directly adding prepared text content with one click to quickly perform batch transfers.

**Steps**

Open TokenPocket, enter the asset page of the corresponding wallet, and tap “More Tools” at the top of the page.

<figure><img src="/files/O2mRZhJYJns4LhM3XxHF" alt=""><figcaption></figcaption></figure>

In the pop-up tool panel, find the “System Tools” section and tap “Native Batch Transfer” to enter the feature page.

***

#### Select Transfer Token <a href="#select-transfer-token" id="select-transfer-token"></a>

After entering the native batch transfer feature, you need to first select the token to be used for the batch transfer.

**Steps**

On the “Select Transfer Token” page, select the token that needs to be transferred in batch. You can also enter the token symbol in the search box to search.

<figure><img src="/files/nqywoJ7q7x6PeGZc3LTY" alt=""><figcaption></figcaption></figure>

After selecting the token, you will enter the “Batch Transfer” page, where the currently selected token and available balance will be displayed.

***

#### Add Receiving Addresses and Transfer Amounts <a href="#add-recipient-addresses-and-amounts" id="add-recipient-addresses-and-amounts"></a>

After selecting the transfer token, you need to add one or more receiving addresses and set the corresponding transfer amount for each address.

**Steps**

On the “Batch Transfer” page, tap “Tap to Add.” In the pop-up add window, enter or paste the receiving address. You can also tap “Select Wallet” to select an address from saved wallets.

<figure><img src="/files/Y3GKR5ToBMmv5bTtBhuy" alt=""><figcaption></figcaption></figure>

Then enter the amount that the address needs to receive in the “Transfer Amount” field. After confirming that everything is correct, tap “Confirm.”

After the address is added, the page will display the added receiving address and the corresponding amount. Users can continue tapping “Tap to Add” to add more receiving addresses, or tap the delete button on the right to remove an added address.

***

#### Check Network Fee and Select Payment Method <a href="#check-network-fee-and-select-payment-method" id="check-network-fee-and-select-payment-method"></a>

After adding the receiving addresses, the system will estimate the network fee required for this batch transfer based on the current network conditions. Users can view the recommended fee and also select the payment method for the network fee. Stablecoin payment methods are also supported.

**Select Payment Method**

After tapping “Payment Method,” you can select the asset used to pay the network fee. The page will display the available payment assets, balances, and corresponding fees.

<figure><img src="/files/9GobWfHIFOiqBt6ubSBg" alt=""><figcaption></figcaption></figure>

After selecting the appropriate payment method, tap “Confirm” to return to the batch transfer page.

Please make sure the selected payment asset has sufficient balance. If the balance is insufficient, the transaction may fail to be initiated or confirmed.

***

### What Is the Difference Between Batch Transfer and Asset Collection?

Both batch transfer and asset collection are batch operation tools, but they are used in different scenarios.

| **Function**         | **Operation Direction**                | **Use Cases**                                                               |
| -------------------- | -------------------------------------- | --------------------------------------------------------------------------- |
| **Batch Transfer**   | From one address to multiple addresses | Batch distribution, batch payments, multi-address allocation                |
| **Asset Collection** | From multiple addresses to one address | Organizing assets across multiple addresses, centralized balance management |

Simply put, **batch transfer** is a “one-to-many” outgoing operation, while **asset collection** is a “many-to-one” incoming operation.