EVM chains support transfers to a single address, while UTXO chains support transfers to one or more addresses. You can transfer funds in either native coin or token in a single request.

Transactions from v2 wallets are screened by Liminal Firewall (if enabled). It performs compliance checks and provides outcomes before broadcasting to the blockchain. If your organisation has a Travel Rule policy enabled in Firewall, include the travelRule object in the request body to avoid transaction failure. If the policy is disabled, you can skip this object. Use the Verify Addresses API to validate the destination addresses before using the API. Refer to wallet versions: v1 & v2 to learn more about the types of wallet versions and their respective supported chains.

Accepted parameter values:

• The transactions.recipients.address[] parameter must have a valid address length ( > 0). It will not accept any null value or empty String value.
• The data type of transactions.recipients.amount[] is updated to String and must be a positive decimal string. It will not accept empty string, null, or number value.

Optional Parameters

1. Using feeLevel and evmCustomfee :
   1. The feeLevel parameter is applicable for EVM chains. Use only maxFeePerGas (Wei) if the coin value is BNB. Use both parameters for EIP 1599 chains.
   2. The maxPriorityFeePerGas (Wei) cannot be greater than maxFeePerGas (Wei).
2. Use evmCustomfee object only when the feeLevel parameter is custom.
   Refer to the Retrieve estimated gas fees and rates API reference to get the required fee estimation rates.

Refer to the Create transaction requests API instead if you are using the v1 wallet. While all liminal supported chains support firewall for Mobile MPC Wallets, please refer to the latest supported chains for hot V2 wallets supporting firewall.