Overview

Inbound or incoming transactions are transfers sent from an external source to any wallet available in your workspace. External sources include third-party accounts connected to your workspace and transactions created outside of your workspace by any party.

Fireblocks detects incoming transactions by scanning all supported blockchains relevant to your vault accounts, connected third-party accounts, and internal whitelisted addresses in your workspace. When Fireblocks recognizes a relevant transaction, the transaction is added to the recent activity panel and transaction history. After the transaction completes, the transaction’s source and destination balances are updated.

Incoming transaction types by destination

The following table includes a summary of how incoming transactions are recognized.

*Pre-requisites for incoming transactions based on asset type:

• The incoming asset must be a globally supported asset or a locally supported asset that you have approved in your workspace.

Learn more about recognizing incoming transactions based on the transaction’s asset below.

All sources to vault accounts

Incoming transactions from a vault account, connected exchange account, connected fiat account, whitelisted address, Fireblocks Network connection, the Fireblocks Gas Station, or outside external source to any vault account are automatically recognized and added to your workspace depending on the asset.

Create an asset wallet for the specific asset before a transaction is sent to avoid unrecognized transactions. For example, if you want to receive Uniswap (UNI) on Ethereum, create an asset wallet for UNI in the destination vault account, even if an address for ETH or a different ERC-20 token is already available in that vault account.

If an asset is sent to a vault account that includes a valid deposit address for that asset type, but doesn't include the specific asset wallet, the asset wallet may be created automatically. Learn more about recognizing incoming transactions based on their asset below.

External sources to connected exchange accounts

Incoming transactions from any external source to connected exchange accounts are automatically recognized only if the deposit was transferred within your workspace. Transactions created outside of your workspace that are sent to a connected exchange account are not recognized, but balances are updated in your workspace after the transaction is complete.

All transactions to Circle accounts with assets supported by Fireblocks are recognized. Learn more about supported assets for Circle accounts.

External sources to connected fiat accounts

All incoming transactions from external sources to connected fiat accounts are automatically recognized for all currencies supported by Fireblocks. Learn more about fiat asset support.

External sources to whitelisted addresses

Incoming transactions from external sources to whitelisted addresses are only recognized if the transaction was created within your Fireblocks workspace using a connected third-party account and depending on the asset.

Incoming transactions created outside of your workspace to whitelisted addresses are not automatically recognized or included in your workspace transaction history. Balances are updated automatically for all internal whitelisted addresses and are included in your deposit address total for billing purposes. Whitelisted addresses labeled external do not display a balance.

Recognizing incoming transactions based on the transaction’s asset

When Fireblocks detects a transaction to a deposit address in your Vault or Internal Whitelisted Addresses, the system determines the transaction’s asset and whether this transaction should be recognized in your workspace.

In order to recognize an incoming transaction, the transaction's asset must both be defined in your workspace and the deposit address must be valid for that asset. Assets that are only available locally in your workspace, or globally for all Fireblocks customers are both valid. If the asset is not defined in your workspace, the transaction is ignored and your total balance does not include this incoming transaction. Undefined assets are ignored because they may be a security risk or sent on an unsupported blockchain.

Automatically recognizing ERC-20 assets

As of January 9th, 2023, any EVM-based deposit address is sufficient to recognize an incoming transaction on any EVM blockchain to a vault account or whitelisted wallet. This includes all similar token formats such as ARC-20 and BEP-20. A new asset wallet is created when an incoming transaction on any EVM blockchain is automatically recognized if there was no matching asset wallet in the vault account or whitelisted wallet.

For example, if an incoming transaction with USDT on Polygon is detected to a vault account that only has an ETH asset wallet, the transaction will be recognized and a USDT (Polygon) asset wallet will be added to that vault account. 

Automatic listing of ERC-20 tokens from contract calls with manual approval

When you enable automatic ERC-20 listing for contract calls in your workspace, transactions sent to your workspace as a result of contract calls initiated from your workspace are automatically recognized. After an Admin user approves the asset, it's allowed in the workspace, and an asset wallet is automatically created in the destination account. This includes ERC-20 formatted assets on any EVM blockchain, such as ARC-20 and BEP-20.

Learn more about automatically adding ERC-20 assets from contract calls.

Recognizing non-EVM incoming transactions

Incoming transactions on non-EVM blockchains with locally or globally available assets are recognized in your workspace depending on the destination, as described above.

If there is no asset wallet in the destination vault account or whitelisted wallet that matches the asset in a transaction, an asset wallet is automatically added to the destination account. For example, an incoming transaction for aUSD on Polkadot to a vault account that only has a LINK deposit address on Polkadot, or an incoming transaction for USDT on Algorand to an internal whitelisted address that only has the ASA base token will both create a new asset wallet in the destination account.

Beginning October 26, 2022, incoming transactions for all assets on Algorand, Solana, or Tron are automatically recognized. Before this date, an asset wallet was required in the destination account before an incoming transaction was broadcast.

Identifying external source addresses

Incoming transfers can be automatically mapped to a whitelisted address in your workspace. The source address is identified in the recent activity panel and transaction history. The address must be whitelisted in your workspace before the transaction is sent to the blockchain for correct identification.

This helps manage your workspace by labeling external sources with easily readable names instead of deposit address values. You can search for transactions from known sources by name in the Transaction History.

You can also use known or unknown sources to control other incoming transaction behavior. For example, you can set specific rules in your AML policy to screen incoming transactions that match external whitelisted addresses or skip screening for incoming transactions that match an internal whitelisted address.

This feature is automatically enabled for all workspaces created after March 4, 2021. Contact Fireblocks Support to enable this feature.