In some cases, transactions are sent from an outside source to an account connected to your workspace, but Fireblocks does not show them.

Not all transactions sent from an outside source to your non-vault accounts, i.e. exchange accounts, fiat accounts, or whitelisted addresses, are recognized by Fireblocks. For more information, refer to the recognizing incoming transactions article.

There are additional conditions for incoming transactions to your vault accounts:

• Some vault accounts do not appear in your Console due to how they are defined. In these cases, the incoming transactions only appear in the transaction history and not in the Recent activity panel. You can still see such transactions via the APIs. To learn more, see the Archiving and hiding vaults article.
• The asset must be recognized in your workspace. Add it to your workspace in advance (ERC-20: by yourself, other assets: by contacting Fireblocks Support) before receiving the transaction.

If you already received the transaction and just now added the asset, submit a Support ticket to have them recognize the incoming transaction. To learn more, see the add support for EVM-based assets and add support for non-EVM-based assets articles.

Alternatively, you can enable the Auto-list ERC-20 Assets as a result of the contract calls feature by submitting a Support ticket.

This automatically adds assets to your workspace if you received them via a contract call that you initiated from your workspace. Learn more about automatic contract call listing in add support for EVM-based assets to your workspace (ERC-20, etc).

Missing Solana testnet transactions

When attempting to receive an incoming transfer of Solana, you may not see it in your Fireblocks Console transaction history or when using Fireblocks API. If this occurs when transferring SOL_TEST to a Fireblocks vault account, you may see the transaction as confirmed on-chain but you do not see it in your Fireblocks wallet. See how to resolve this issue in the cannot see Solana transactions article.

Still cannot identify the incoming transaction?

If you confirm that none of the above conditions should prevent your transaction from being seen in your workspace, contact Support. Fireblocks Support can rescan the missing transaction and a new incoming transaction record will be created.
You can submit a ticket for this using this link.