Overview

This article includes a list of substatuses related to primary transaction statuses. Some primary statuses do not have any substatuses.

Transaction statuses are displayed in the Transaction History and the Recent activity panel in the Fireblocks Console. You can hover over the status in the Recent activity panel to see the substatus and additional details.

Active transfers panel - Transaction status tooltip

Pending third-party substatuses

3RD_PARTY_PENDING_SERVICE_MANUAL_APPROVAL

The 3RD_PARTY_PENDING_SERVICE_MANUAL_APPROVAL substatus indicates the transaction is awaiting manual approval by a third-party service, such as an exchange.

If this status persists for longer than expected, contact your exchange account manager and provide them with the transaction details.

3RD_PARTY_PROCESSING

The 3RD_PARTY_PROCESSING substatus indicates the transaction is awaiting approval by a third-party service, such as an exchange.

Confirming substatuses

3RD_PARTY_CONFIRMING

The 3RD_PARTY_CONFIRMING substatus indicates the transaction is awaiting confirmation by a third-party service, such as an exchange.

PENDING_BLOCKCHAIN_CONFIRMATIONS

The PENDING_BLOCKCHAIN_CONFIRMATIONS substatus indicates the transaction is awaiting confirmation on the blockchain.

Learn more about how many confirmations are required for transactions on each blockchain in the Deposit Control and Confirmation Policy.

Completed substatuses

CONFIRMED

The CONFIRMED substatus indicates the transaction reached the required number of confirmations on the blockchain and is recognized by all parties.

3RD_PARTY_COMPLETED

The 3RD_PARTY_COMPLETED substatus indicates the transaction was completed by a third-party service, such as an exchange.

COMPLETED_BUT_3RD_PARTY_FAILED

The COMPLETED_BUT_3RD_PARTY_FAILED substatus indicates the transaction was completed on the blockchain as shown on block explorers, but failed on the associated third-party platform. This is often a third-party system error.

If the transaction was sent from a vault account in your Fireblocks workspace, the balance will be deducted from the account.

If the exchange does not show the transaction in recent history or labels the transaction as failed, contact the exchange with the transaction details. If they are unable to resolve the issue, contact Fireblocks Support.

COMPLETED_BUT_3RD_PARTY_REJECTED

The COMPLETED_BUT_3RD_PARTY_REJECTED substatus indicates the transaction was completed on the blockchain as shown on block explorers but rejected by the associated third-party platform.

If the transaction was sent from a vault account in your Fireblocks workspace, the balance will be deducted from the account.

An exchange may reject a transaction due to a user input error. For example, some exchanges require an account or deposit minimum. Alternatively, the transaction may have been manually canceled on the exchange.

Blocked by policy substatuses

BLOCKED_BY_POLICY

The BLOCKED_BY_POLICY substatus indicates the transaction was blocked from being completed due to a Transaction Authorization Policy (TAP) rule.

Transactions that are blocked by policy include the TAP rule number as it appears in your workspace TAP settings. If you want to allow these transactions, create a new policy rule in a position that lets the transaction be correctly enforced according to the first-match principle.

The BLOCKED_BY_POLICY substatus can also indicate that your transaction was blocked due to the source address being a sanctioned address.

BLOCKED_BY_GLOBAL_POLICY

The BLOCKED_BY_POLICY substatus indicates that your transaction was blocked when the destination address is sanctioned by the U.S. Department of the Treasury’s Office of Foreign Assets Control (OFAC). We subscribe to OFAC’s public Specially Designated Nationals (SDN) list updates and add OFAC-sanctioned addresses to our backend systems to block outgoing transactions to those addresses.

Cancelled substatuses

3RD_PARTY_CANCELLED

The 3RD_PARTY_CANCELLED substatus indicates the transaction was canceled by a third party, such as an exchange.

3RD_PARTY_REJECTED

The 3RD_PARTY_REJECTED substatus indicates the transaction was rejected by a third party, such as an exchange, or not approved in time by the user.

CANCELLED_BY_USER

The CANCELLED_BY_USER substatus indicates the transaction was canceled using the Fireblocks console or the Fireblocks API, or that the API Co-Signer may have canceled the transaction.

CANCELLED_BY_USER_REQUEST

The CANCELLED_BY_USER_REQUEST substatus indicates that this transaction was canceled by a user in your workspace contacting Fireblocks Support.

REJECTED_BY_USER

The REJECTED_BY_USER substatus indicates the transaction was rejected by one of its signers using the Fireblocks Mobile app, or that the API Co-Signer may have rejected the transaction.

Rejected substatuses

AUTO_FREEZE

The AUTO_FREEZE substatus indicates the incoming transaction was frozen automatically by the post-screening policy. Any associated assets will not be available until a user with an Owner or Admin role unfreezes them.

REJECTED_AML_SCREENING

The REJECTED_AML_SCREENING substatus indicates the transaction was identified as high risk by your AML or Travel Rule screening service provider and rejected accordingly.

For more information about why a transaction was rejected, refer to the transaction’s AML result field or Travel Rule result field on the Transaction History page.

FROZEN_MANUALLY

The FROZEN_MANUALLY substatus indicates the incoming transaction was manually frozen via the Fireblocks API. Any associated assets will not be available until a user with an Owner or Admin role unfreezes them via the API.

Failed substatuses

User input issues

ACTUAL_FEE_TOO_HIGH

The ACTUAL_FEE_TOO_HIGH substatus indicates the transaction failed because the specified fee was lower than the current network fee.

Resolution

This issue usually occurs if network transaction fees have increased significantly between submitting and signing the transaction. Set the transaction fee to current rates, and resubmit the transaction.

ADDRESS_WHITELISTING_SUSPENDED

The ADDRESS_WHITELISTING_SUSPENDED substatus indicates the outgoing transaction failed because the destination address was whitelisted too recently. This only applies to workspaces with this feature manually enabled. Learn more about the address whitelist suspension property.

Resolution

Resubmit the transaction after the whitelisted address is active.

AMOUNT_TOO_SMALL

The AMOUNT_TOO_SMALL substatus indicates the transaction failed due to a withdrawal request below the minimum allowed amount. This may occur because some blockchains have required minimums for transactions to complete successfully, or because the transaction fee is higher than the net transfer amount on a gross transaction.

Resolution

Confirm the transfer amount is above the required minimum for this blockchain, and the transfer amount is greater than the required transaction fee before resubmitting the transaction. Minimum transfer amounts vary per blockchain.

Known Limits:

Bitcoin (BTC): 582 satoshi
Cardano (ADA): 1 ADA + applicable transaction fees

AUTHORIZATION_FAILED

The AUTHORIZATION_FAILED substatus indicates that the API Co-Signer Callback Handler did not correctly approve or sign the transaction.

Resolution

Review your Callback Handler authentication logic or confirm that your Callback Handler and API Co-Signer are correctly configured before resubmitting the transaction.

AUTHORIZER_NOT_FOUND

The AUTHORIZER_NOT_FOUND substatus indicates the transaction failed because an authorizer was not found for it or because the only available authorizer is the transaction’s initiator.

Resolution

This status occurs if the MPC device setup is not completed for an authorizer or one authorizer in a TAP group. Ensure all authorizers have completed their MPC device setup before resubmitting the transaction.

ENV_UNSUPPORTED_ASSET

The ENV_UNSUPPORTED_ASSET substatus indicates the transaction failed because the specified asset is not currently supported in your workspace. This asset may be a testnet asset on a mainnet workspace or vice versa.

Resolution

This issue typically occurs when submitting transactions via the API. Confirm the correct asset ID is selected before resubmitting the transaction.

ERROR_UNSUPPORTED_TRANSACTION_TYPE

The ERROR_UNSUPPORTED_TRANSACTION_TYPE substatus indicates the transaction failed because the transaction type is not supported by Fireblocks for this particular blockchain. For example, only transfers are supported on Bitcoin, Cardano, Ripple, and some other blockchains.

Resolution

Verify the transaction type is TRANSFER. Other transaction types include MINT, BURN, RAW, TYPED_MESSAGE, CONTRACT_CALL, and APPROVE.

FAIL_ON_LOW_FEE

The FAIL_ON_LOW_FEE substatus indicates the transaction failed due to the current blockchain fee being higher than the fee specified in the transaction. Fireblocks will fail a transaction if it is likely to be significantly delayed due to a low fee.

Resolution

Set the transaction fee to current rates, and resubmit the transaction.

GAS_LIMIT_TOO_LOW

The GAS_LIMIT_TOO_LOW substatus indicates the transaction failed because the gas limit was set below the minimum amount to complete the transaction, causing it to be rejected by the blockchain. Learn more about Ethereum Fee Parameters.

Resolution

Set all fee parameters to sufficient amounts before resubmitting the transaction.

GAS_PRICE_TOO_LOW_FOR_RBF

The GAS_PRICE_TOO_LOW_FOR_RBF substatus indicates the transaction failed because the specified gas price was too low for Replace-by-Fee (RBF). Learn more about RBF transactions.

Resolution

Resubmit the RBF transaction with a gas price at least 15% higher than the original transaction’s gas price.

GAS_PRICE_TOO_LOW

On Ethereum-based blockchains, in practice, the vault has sufficient funds available to cover transaction fees, but the gas price encoded at the time the transaction was created was below the minimum allowed on the blockchain when sent to it.

Resolution

Try performing the transaction again with a higher transaction fee, or wait for some time for the gas price to get back down to a suitable level and try again with your original desired fee rate.

FEE_TOO_LOW

On BTC-based blockchains, the overall fee is too low for the particular transaction.

Resolution

Try performing the transaction with a higher gas price.

INCOMPLETE_USER_SETUP

The INCOMPLETE_USER_SETUP substatus indicates the transaction failed because the transaction's initiator did not complete their MPC key setup.

Resolution

Verify that the workspace Owner and the Signer for this transaction have completed their MPC setup before resubmitting it.

INSUFFICIENT_FUNDS

The INSUFFICIENT_FUNDS substatus indicates the transaction failed because the vault account does not have enough funds to fulfill the withdrawal request.

Resolution

This substatus only occurs when using the API. To avoid this issue, refresh your balances or retrieve available vault account balances when creating transactions using the API. If the vault account's available balance is sufficient to fulfill the transaction and the issue persists, contact Fireblocks Support.

INSUFFICIENT_FUNDS_FOR_FEE

The INSUFFICIENT_FUNDS_FOR_FEE substatus indicates the transaction failed because the vault account does not have enough funds for the requested fee. Fees for token transfers (e.g. USDC) are paid in the base asset (e.g. ETH) from the same vault account as the transaction source.

Resolution

This substatus occurs when using the API. To avoid this issue, use the Get the asset balance for a vault account endpoint to retrieve the vault account balance of the base asset needed for the transaction’s fees when creating transactions via the API.

Learn more about using the Fireblocks Gas Station to avoid this issue by automatically managing fees.

INTEGRATION_SUSPENDED

The INTEGRATION_SUSPENDED substatus indicates that the transaction failed due to Fireblocks Customer Support activating the circuit breaker to halt an exchange integration.

Resolution

This substatus is reflected in the Fireblocks Console User Interface in one of the following situations:

Your exchange connection (API key ABCDE-12345) is blocked due to excessive use. Contact Fireblocks support for more information.
Your exchange connection in this workspace (API key ABCDE-12345) is blocked due to excessive use. Contact Fireblocks support for more information.
Your workspace exchange and fiat connections are blocked due to excessive use. Contact Fireblocks support for more information.
Your workspace <exchange-name> connections are blocked due to excessive use. Contact Fireblocks support for more information.
The <exchange-name> integration is currently blocked. Check the Fireblocks Status page for more information.
Your <exchange-name> connection is blocked due to unique circumstances. Contact Fireblocks support for more information.

INVALID_ADDRESS

The INVALID_ADDRESS substatus indicates the transaction failed because the destination is an unsupported format for a one-time address. Learn more about different address formats.

This substatus also appears if the source address and destination address are identical. This issue is common with XRP transactions when sending funds to and from the same address while using a different destination tag.

Resolution

Verify the address format matches the asset and blockchain before resubmitting the transaction. Also, make sure the source address and destination address are different.

INVALID_CONTRACT_CALL_DATA

The INVALID_CONTRACT_CALL_DATA substatus indicates the transaction failed because its data was not encoded properly. Typically, this occurs due to an internal error or user error when using the Raw Signing feature. Learn more about raw data for off-chain messages.

Resolution

Confirm the contract call and raw signing data have been encoded correctly before resubmitting this transaction. Check the Fireblocks Status page for ongoing service disruptions. If there are none, resubmit your transaction. Contact Fireblocks Support for assistance if the transaction fails repeatedly.

INVALID_FEE_PARAMS

The INVALID_FEE_PARAMS substatus indicates the transaction failed due to inconsistent or unknown fee parameters. Learn more about Ethereum Fee Parameters.

Resolution

Confirm all fee parameters were entered correctly for the relevant blockchain.

INVALID_NONCE_FOR_RBF

The INVALID_NONCE_FOR_RBF substatus indicates the replacement transaction failed because the Fireblocks system did not find a matching pending transaction. Learn more about RBF transactions.

Resolution

Confirm the status of the original transaction before resubmitting this RBF transaction. RBF transactions can only be used with transactions that are not Failed or Confirmed. Check the Fireblocks Status page for ongoing service disruptions. If there are none, resubmit your transaction. Contact Fireblocks Support for assistance if the transaction fails repeatedly.

INVALID_TAG_OR_MEMO

The INVALID_TAG_OR_MEMO substatus indicates the transaction failed due to an invalid destination tag or memo, which some assets require.

Resolution

Resubmit this transaction with the correct destination tag or memo for the selected asset type.

INVALID_UNMANAGED_WALLET

The INVALID_UNMANAGED_WALLET substatus indicates the transaction failed because the associated internal whitelisted wallet was removed or is nonexistent. This substatus will appear in the Console as: Approved wallet not found.

Resolution

Verify the wallet ID entered is correct. If the internal whitelisted wallet does not exist, create and approve a wallet and associated address before resubmitting the transaction.

MAX_FEE_EXCEEDED

The MAX_FEE_EXCEEDED substatus indicates the transaction failed because current network gas prices are above the specified maximum fee. Learn more about Ethereum Fee Parameters.

Resolution

Verify all fee parameters are set to current rates before resubmitting the transaction.

MISSING_DEPOSIT_CONFIRMATIONS

The MISSING_DEPOSIT_CONFIRMATIONS substatus indicates the transaction failed due to the exchange not recording a sufficient number of confirmations required to credit the associated account.

Resolution

Verify whether your assets are available for withdrawal using the exchange's account portal.

MISSING_DEPOSIT_CONFIRMATIONS_FOR_WITHDRAWAL

The MISSING_DEPOSIT_CONFIRMATIONS_FOR_WITHDRAWAL substatus indicates the transaction failed due to the exchange not recording a sufficient number of confirmations required to withdraw assets from the associated account.

Resolution

Verify whether your assets are available for withdrawal using the exchange's account portal.

MISSING_TAG_OR_MEMO

The MISSING_TAG_OR_MEMO substatus indicates a transaction failed due to a missing destination tag or memo, which some assets require.

Resolution

Resubmit this transaction with the correct destination tag or memo for the selected asset type.

NEED_MORE_TO_CREATE_DESTINATION

The NEED_MORE_TO_CREATE_DESTINATION substatus indicates the transaction failed due to insufficient funds for creating the destination account. Only the Polkadot, Kusama, and Westend (testnet) blockchains have this limitation.

Resolution

Confirm the transaction amount is above the minimum requirement before resubmitting this transaction. Polkadot requires a 1 DOT minimum deposit. Kusama requires a 0.0000333333 KSM minimum deposit. Learn more in the Polkadot Help Center.

NO_MORE_PREPROCESSED_INDEXES

The NO_MORE_PREPROCESSED_INDEXES substatus only applies to outgoing transactions sent from Cold Wallet workspaces. This substatus indicates that the cold wallet device has used all available signatures for signing.

The total amount of signatures is determined by the customer and their Customer Success Manager during onboarding. This number is typically set to last around three years based on the client’s average number of transactions, but unusual working patterns may result in using all available signatures sooner than expected.

Resolution

If this error occurs, the current cold wallet signing device is no longer available to sign transactions. Either use another existing device or provision a new signing device for your workspace.

NON_EXISTING_ACCOUNT_NAME

The NON_EXISTING_ACCOUNT_NAME substatus indicates the transaction failed because the destination address cannot be validated. This only applies to whitelisted addresses, exchange account addresses, or one-time addresses on EOS, NEAR, or Stellar networks.

Resolution

Verify that the destination address is correct before resubmitting this transaction. For some exchanges, you may need to manually generate a deposit address in the exchange’s account settings.

NOT_ENOUGH_DEPOSIT_CONFIRMATIONS

The NOT_ENOUGH_DEPOSIT_CONFIRMATIONS substatus indicates the transaction failed due to the exchange not receiving the number of confirmations required to credit the associated account. This only applies to Binance exchange accounts.

Resolution

Use Binance's User Asset (USER_DATA) endpoint to verify whether your assets are available for withdrawal.

OUT_OF_DATE_SIGNING_KEYS

The OUT_OF_DATE_SIGNING_KEYS substatus indicates that the transaction failed because the signer's key share must be updated to the MPC-CMP protocol.

Resolution

The designated signer for this transaction must update their key share to the MPC-CMP protocol before attempting to sign a transaction again. Learn more about the MPC-CMP update for all Fireblocks users.

RAW_MSG_EMPTY_OR_INVALID

The RAW_MSG_EMPTY_OR_INVALID substatus indicates that a raw signing transaction failed due to incorrect raw data. Learn more about raw data for off-chain messages.

Resolution

Validate the raw data before resubmitting this transaction.

RAW_MSG_LEN_INVALID

The RAW_MSG_LEN_INVALID substatus indicates that a raw signing transaction failed due to incorrect raw data. Specifically, the message length parameter that applies to ECDSA signing is incorrect.

Learn more about raw data for off-chain messages.
Learn more about how ECDSA signatures are used in Fireblocks.

Resolution

Validate the raw data and ECDSA signature parameters before resubmitting this transaction.

SMART_CONTRACT_EXECUTION_FAILED

This error occurs when the transaction fails due to a smart contract error. If you're using the Fireblocks API, you can find the specific revert reason in the TransactionResponse object's errorDescription field.

Resolution

Here are several ways to resolve this error:

Initiate the transaction again while using different parameters.
Try using a different vault to perform the transaction.
Read the contract's source code to understand the error better.

TOO_MANY_INPUTS

The TOO_MANY_INPUTS substatus indicates the transaction failed because the maximum number of UTXO inputs exceeded the requested amount. This applies to transactions on Bitcoin, Bitcoin Cash, Bitcoin SV, Dash, Litecoin, ZCash, and Cardano

Resolution

These UTXO transactions on Fireblocks are limited to 250 inputs, except Cardano transactions are limited to 110 inputs, and ZCash transactions to 50 inputs. Testnet workspaces using the Fireblocks Communal API Co-Signer are limited to transactions with up to 50 inputs.

First, use the Get the maximum spendable amount in a single transaction endpoint to retrieve the maximum spendable amount of the relevant asset. Then, to resubmit the transaction, either consolidate the available inputs or send the transfer amount as multiple transactions.

TX_SIZE_EXCEEDED_MAX

The TX_SIZE_EXCEEDED_MAX substatus indicates the transaction failed because the transaction exceeded the allowed amount. This only applies to transactions on the Cardano blockchain.

Resolution

Cardano supports transactions up to 16kB including inputs, metadata, scripts, certificates, signatures, and more, as represented on-chain. To re-submit this transaction, reduce the data size of the transaction.

UNAUTHORISED__DEVICE

The UNAUTHORISED__DEVICE substatus indicates the transaction failed because an unauthorized device was used to initiate, approve, or sign it.

Resolution

Confirm the approving and signing devices have the most recent version of the Fireblocks mobile app before resubmitting the transaction. Contact Fireblocks Support for assistance if the transaction fails repeatedly.

UNAUTHORISED__USER

The UNAUTHORISED__USER substatus indicates the transaction failed due to an unauthorized user attempting to initiate or approve it. This may occur if a user’s setup is incomplete or a user was disabled before the transaction was completed.

Resolution

Confirm that all relevant users have completed their mobile setup and are using the most recent version of the Fireblocks mobile app before resubmitting the transaction. Contact Fireblocks Support for assistance if the transaction fails repeatedly.

UNALLOWED_RAW_PARAM_COMBINATION

The UNALLOWED_RAW_PARAM_COMBINATION substatus indicates that a raw signing transaction failed due to incorrect raw data parameters. Learn more about raw data for off-chain messages.

Resolution

Validate the raw data parameters before resubmitting this transaction.

UNSUPPORTED_OPERATION

The UNSUPPORTED_OPERATION substatus indicates the transaction failed because Fireblocks or a third-party service does not currently support the operation.

Resolution

Check the status page for the third-party service if available and the Fireblocks Status page for ongoing service disruptions. If there are none, resubmit your transaction. Contact Fireblocks Support for assistance if the transaction fails repeatedly.

UNSUPPORTED_TRANSACTION_TYPE

The UNSUPPORTED_TRANSACTION_TYPE substatus indicates the transaction failed due to either an API error or an internal system error.

Resolution

If the transaction was created via the Fireblocks API, confirm that the specified value for operation is TRANSFER or another value. Then determine whether the specified parameters match the operation type. For example, a contract call transaction type Mint for the Omni blockchain, or a gasLimit parameter set to a non-default value for a transaction type set to typed_message or raw are not supported.

Alternatively, the transaction may have failed due to a Fireblocks internal error. In this case, contact Fireblocks Support for assistance if the transaction fails repeatedly.

ZERO_BALANCE_IN_PERMANENT_ADDRESS

The ZERO_BALANCE_IN_PERMANENT_ADDRESS substatus indicates the transaction failed due to the permanent address not holding enough Omni.

Resolution

Check the Fireblocks Status page for ongoing service disruptions. If there are none, resubmit your transaction. Contact Fireblocks Support for assistance if the transaction fails repeatedly.

Fireblocks system issues

CONNECTIVITY_ERROR

The CONNECTIVITY_ERROR substatus indicates the transaction failed due to an internal network error.

Resolution

Check the Fireblocks Status page for ongoing service disruptions. If there are none, resubmit your transaction. Contact Fireblocks Support for assistance if the transaction fails repeatedly.

ERROR_ASYNC_TX_IN_FLIGHT

The ERROR_ASYNC_TX_IN_FLIGHT substatus indicates the transaction failed due to a Fireblocks internal error during processing. This substatus is displayed as an Internal Error in the Recent activity panel of the Fireblocks Console. The Fireblocks API and the Fireblocks Console transaction history display this status directly.

Resolution

Check the Fireblocks Status page for ongoing service disruptions. If there are none, resubmit your transaction. Contact Fireblocks Support for assistance if the transaction fails repeatedly.

INTERNAL_ERROR

The INTERNAL_ERROR substatus indicates the transaction failed due to a Fireblocks internal error during processing.

Resolution

Check the Fireblocks Status page for ongoing service disruptions. If there are none, resubmit your transaction. Contact Fireblocks Support for assistance if the transaction fails repeatedly.

INVALID_NONCE_TOO_HIGH

The INVALID_NONCE_TOO_HIGH substatus indicates the transaction failed because the Fireblocks system selected a nonce that is too high, creating a gap between the last transaction and this one. As a result, this transaction cannot be processed until the gap is filled.

Resolution

Check the Fireblocks Status page for ongoing service disruptions. If there are none, resubmit your transaction. Contact Fireblocks Support for assistance if the transaction fails repeatedly.

INVALID_NONCE_TOO_LOW

The INVALID_NONCE_TOO_LOW substatus indicates the transaction failed because the Fireblocks system assigned an illegal nonce. The nonce chosen for this transaction already belongs to a transaction previously confirmed on this account.

Resolution

This may occur when an RBF or drop transaction is used to replace a pending transaction that was completed before being replaced. If this transaction references another transaction, confirm the status of both transactions before resubmitting. Contact Fireblocks Support for assistance if the transaction fails repeatedly.

INVALID_ROUTING_DESTINATION

The INVALID_ROUTING_DESTINATION substatus indicates the transaction failed because the Fireblocks system could not identify a valid destination. This status is specific to Fireblocks Network transactions.

Resolution

Check the Fireblocks Status page for ongoing service disruptions. If there are none, resubmit your transaction. Contact Fireblocks Support for assistance if the transaction fails repeatedly.

LOCKING_NONCE_ACCOUNT_TIMEOUT

The LOCKING_NONCE_ACCOUNT_TIMEOUT substatus indicates the transaction request timed out due to an internal error.

Resolution

Check the Fireblocks Status page for ongoing service disruptions. If there are none, resubmit your transaction. Contact Fireblocks Support for assistance if the transaction fails repeatedly.

NETWORK_ROUTING_MISMATCH

The NETWORK_ROUTING_MISMATCH substatus indicates the transaction failed because a valid routing destination couldn’t be identified by the Fireblocks Network. This substatus is displayed as an Internal Error in the Recent activity panel of the Fireblocks Console. The Fireblocks API and the Fireblocks Console transaction history display this status directly.

Resolution

NONCE_ALLOCATION_FAILED

The NONCE_ALLOCATION_FAILED substatus indicates a transaction could not be created due to an internal error.

Resolution

Check the Fireblocks Status page for ongoing service disruptions. If there are none, resubmit your transaction. Contact Fireblocks Support for assistance if the transaction fails repeatedly.

RESOURCE_ALREADY_EXISTS

The RESOURCE_ALREADY_EXISTS substatus indicates the transaction failed due to a Fireblocks internal error during processing. This substatus is displayed as an Internal Error in the Recent activity panel of the Fireblocks Console. The Fireblocks API and the Fireblocks Console transaction history display this status directly.

Resolution

Check the status page for the third-party service if relevant and the Fireblocks Status page for ongoing service disruptions. If there are none, resubmit your transaction. Contact Fireblocks Support for assistance if the transaction fails repeatedly.

SIGNER_NOT_FOUND

The SIGNER_NOT_FOUND substatus indicates the transaction failed because no signer was found for it.

Resolution

This transaction likely failed because the signer designated in the Transaction Authorization Policy (TAP) does not have an MPC signing device setup, or the designated signer is no longer active in your workspace. Make sure the designated signer is available and has completed their MPC device setup before resubmitting this transaction.

SIGNING_ERROR

The SIGNING_ERROR substatus indicates the transaction failed due to an internal error during the MPC signing process.

Resolution

The transaction signer should make sure their Fireblocks mobile app is updated to the current version before resubmitting this transaction. If this issue persists, contact Fireblocks Support and include the Fireblocks mobile app version. If the transaction was signed by the API Co-Signer, include your API Co-Signer logs. Learn more about generating API Co-Signer logs.

TIMEOUT

The TIMEOUT substatus indicates the transaction request timed out due to an internal error or because it was not approved or signed within the expiration window. Learn more about approval and signing expiration.

Resolution

Make sure that all approvers and signers are using the most recent version of the Fireblocks mobile app before resubmitting the transaction. All relevant users must approve and sign it within the correct amount of time.

If approval and signing were completed within the correct time, check the Fireblocks Status page for ongoing service disruptions. If there are none, resubmit your transaction. Contact Fireblocks Support for assistance if the transaction fails repeatedly.

TX_OUTDATED

The TX_OUTDATED substatus indicates the transaction failed because the nonce set for this transaction by the Fireblocks system was used by another transaction.

Resolution

Check the Fireblocks Status page for ongoing service disruptions. If there are none, resubmit your transaction. Contact Fireblocks Support for assistance if the transaction fails repeatedly.

UNKNOWN_ERROR

The UNKNOWN_ERROR substatus indicates the transaction failed due to an unexpected error in the Fireblocks system.

Resolution

Check the Fireblocks Status page for ongoing service disruptions. If there are none, resubmit your transaction. Contact Fireblocks Support for assistance if the transaction fails repeatedly.

UNSUPPORTED_MEDIA_TYPE

The UNSUPPORTED_MEDIA_TYPE substatus indicates the transaction failed due to a Fireblocks internal error during processing. This substatus is displayed as an Internal Error in the Recent activity panel of the Fireblocks Console. The Fireblocks API and the Fireblocks Console transaction history display this status directly.

Resolution

Check the Fireblocks Status page for ongoing service disruptions. If there are none, resubmit your transaction. Contact Fireblocks Support for assistance if the transaction fails repeatedly.

VAULT_WALLET_NOT_READY

The VAULT_WALLET_NOT_READY substatus indicates the transaction failed because the asset wallet in the specified vault account was not available for the transaction.

Resolution

This status usually occurs after creating multiple asset wallets in the same vault account at once via the API. Activate the asset wallet using the API before resubmitting this transaction. Learn more about activating an asset wallet in the API documentation.

Third-party account issues

ADDRESS_NOT_WHITELISTED

The ADDRESS_NOT_WHITELISTED substatus indicates the transaction failed due to it attempting to withdraw funds from an exchange to a non-whitelisted destination address.

API_KEY_MISMATCH

The API_KEY_MISMATCH substatus indicates the transaction failed due to the third-party account API connectivity information no longer being accurate.

Confirm that the API Key, API Secret, and other parameters are valid according to your third-party account portal, then delete and re-add the third-party account to your Fireblocks workspace before submitting this transaction again.

ASSET_NOT_ENABLED_ON_DESTINATION

The ASSET_NOT_ENABLED_ON_DESTINATION substatus indicates the transaction failed due to the asset type requiring manual enablement at the third-party destination, such as an exchange.

DEST_TYPE_NOT_SUPPORTED

The DEST_TYPE_NOT_SUPPORTED substatus indicates that a transaction from a third-party account to the selected destination is not supported.

Resolution

This substatus currently only applies to withdrawals from a Paxos exchange account to a one-time address. Paxos complies with the Travel Rule. Therefore, every transaction destination must be mapped to a beneficiary company. With Fireblocks, the beneficiary company is the workspace name when the destination is a vault account or connected third-party service, such as exchange or fiat accounts. If the destination is a whitelisted address, the name of the whitelisted wallet is identified as the beneficiary.

To ensure a withdrawal transaction from Paxos is completed, use a whitelisted address instead of a one-time address.

EXCEEDED_DECIMAL_PRECISION

The EXCEEDED_DECIMAL_PRECISION substatus indicates a transaction failed due to a third-party service not supporting the same amount of decimal digits for a transaction amount as Fireblocks. The exchange or fiat connection may then report an error that the amount is not supported. Re-submit the transaction with fewer decimals in the transaction amount.

Currently, this issue most commonly occurs with Coinbase, Coinbase Pro, and Crypto.com.

EXCHANGE_CONFIGURATION_MISMATCH

The EXCHANGE_CONFIGURATION_MISMATCH substatus indicates that the transaction failed because the associated exchange integration is temporarily unavailable. Check the Fireblocks Status page for additional information.

Resolution

Contact Fireblocks Support to resolve this issue. Resubmitting the transaction without Fireblocks Support will result in a failed transaction.

EXCHANGE_VERSION_INCOMPATIBLE

The EXCHANGE_VERSION_INCOMPATIBLE substatus indicates that the transaction failed because the associated exchange integration is temporarily unavailable.

Resolution

Contact Fireblocks Support to resolve this issue. Resubmitting the transaction without Fireblocks Support will result in a failed transaction.

INVALID_EXCHANGE_ACCOUNT

The INVALID_EXCHANGE_ACCOUNT substatus indicates the transaction failed due to the associated exchange account being disabled or nonexistent.

METHOD_NOT_ALLOWED

The METHOD_NOT_ALLOWED substatus indicates that the transaction failed because the associated exchange integration is temporarily unavailable.

Resolution

Contact Fireblocks Support to resolve this issue. Resubmitting the transaction without Fireblocks Support will result in a failed transaction.

NON_EXISTENT_AUTO_ACCOUNT

The NON_EXISTENT_AUTO_ACCOUNT substatus indicates this transaction failed due to the third-party account configuration being incorrect in your Fireblocks workspace.

Currently, this only occurs with Paxos exchange accounts. Verify the third-party account is configured according to the Help Center's step-by-step guide. If needed, delete the account from your Fireblocks workspace, add it again, and then re-submit this transaction.

ON_PREMISE_CONNECTIVITY_ERROR

The ON_PREMISE_CONNECTIVITY_ERROR substatus only applies to transactions using the Fireblocks On-Prem Exchange Service (FOPES). This substatus indicates Fireblocks could not retrieve the third-party account details due to a connectivity error with FOPES.

Learn more about FOPES.

PEER_ACCOUNT_DOES_NOT_EXIST

The PEER_ACCOUNT_DOES_NOT_EXIST substatus indicates the transaction failed because one of the following third-party account details is incorrect: this is a sub-account and this sub-account name no longer exists on your third-party account, or your Fireblocks Network settings that previously directed to this account have been deleted. Verify your third-party sub-account configuration or Fireblocks Network settings before submitting this transaction again.

UNAUTHORISED__IP_WHITELISTING

The UNAUTHORISED__IP_WHITELISTING substatus indicates the transaction failed due to the third-party account being misconfigured. The third-party account requires whitelisting a Fireblocks IP address and that information is currently incorrect or missing.

Read the account configuration step-by-step guide, delete the third-party account from your workspace, add it again using the correct Fireblocks IP address, and then submit this transaction again.

Learn more about Fireblocks IP addresses for third-party integrations.

UNAUTHORISED__MISSING_CREDENTIALS

The UNAUTHORISED__MISSING_CREDENTIALS substatus indicates the transaction failed due to missing credentials from a third-party service, such as an exchange.

UNAUTHORISED__MISSING_PERMISSION

The UNAUTHORISED__MISSING_PERMISSION substatus indicates the transaction failed due to a missing third-party service’s API permission, such as an exchange’s API.

UNAUTHORISED__OTP_FAILED

The UNAUTHORISED__OTP_FAILED substatus indicates the transaction failed due to incorrect third-party account configuration. The third-party account requires specifying a Two-Factor Authentication (2FA) registration code, and a wrong code was entered during the third-party account configuration.

Read the account configuration step-by-step guide, delete the third-party account from your workspace, add it again using the correct 2FA details, and then submit this transaction again.

WITHDRAW_LIMIT

The WITHDRAW_LIMIT substatus indicates the transaction failed due to it exceeding the exchange’s withdrawal limit.

Third-party system issues

3RD_PARTY_FAILED

The 3RD_PARTY_FAILED substatus indicates the transaction failed with a third-party service, such as an exchange.

Resolution

Check the status page for the third-party service and the Fireblocks Status page for ongoing service disruptions. If there are none, resubmit your transaction. Contact Fireblocks Support for assistance if the transaction fails repeatedly.

API_CALL_LIMIT

The API_CALL_LIMIT substatus indicates the transaction failed because it exceeded the API call limit of a third-party service, such as an exchange. API call limits vary between different exchanges. Make sure to follow each exchange’s published limits to avoid failed transactions.

Resolution

Rate limits vary per exchange and account type. Wait a few seconds before making more API calls. If this problem persists, you may need to adjust your API configuration or contact your exchange account manager.

API_INVALID_SIGNATURE

The API_INVALID_SIGNATURE substatus indicates the transaction failed due to a third-party service’s API, such as an exchange’s API, providing an invalid signature.

Resolution

If this issue occurs more than once, delete the exchange account from your Fireblocks workspace and then connect it again. This may require generating a new API key and API secret from your exchange account settings.

CANCELLED_EXTERNALLY

The CANCELLED_EXTERNALLY substatus indicates the transaction failed due to being canceled by a third-party service, such as an exchange.

Resolution

The transaction was canceled by the third-party service associated with the transaction's source address. Contact the exchange with the transaction details to determine the issue. If they are unable to resolve the issue, contact Fireblocks Support.

FAILED_AML_SCREENING

The FAILED_AML_SCREENING substatus indicates the transaction failed post-screening due to the anti-money laundering (AML) service provider or Travel Rule service provider not communicating their results. Learn more about AML screening and Travel Rule screening.

INVALID_FEE

The INVALID_FEE substatus indicates the transaction failed because there is an insufficient balance in the exchange account of the asset required for the withdrawal and transaction fees. Learn more about exchange withdrawal fees.

Resolution

Withdrawal and transaction fees from exchange accounts are calculated after a transaction is submitted. Review the exchange’s withdrawal fee policy, and then verify there is a sufficient balance in the account for all fees before resubmitting this transaction.

INVALID_THIRD_PARTY_RESPONSE

The INVALID_THIRD_PARTY_RESPONSE substatus indicates the transaction failed due to Fireblocks receiving an unrecognized or invalid response from a third-party service, such as an exchange.

Resolution

If this issue occurs repeatedly, delete the exchange account from your Fireblocks workspace and then connect it again. This may require generating a new API key and API secret from your exchange account settings. Resubmit the transaction after reconnecting the exchange account. Contact Fireblocks Support if this issue persists.

MANUAL_DEPOSIT_ADDRESS_REQUIRED

The MANUAL_DEPOSIT_ADDRESS_REQUIRED substatus indicates the transaction failed due to Fireblocks encountering an error while retrieving a deposit address from an exchange.

Resolution

Manually generate a deposit address for the selected asset from your exchange account settings. Resubmit the transaction using that address.

MISSING_DEPOSIT_ADDRESS

The MISSING_DEPOSIT_ADDRESS substatus indicates the transaction failed because Fireblocks was unable to retrieve a deposit address from the exchange.

Resolution

Verify the deposit address is accurate, and then resubmit the transaction. If this issue occurs repeatedly, delete the exchange account from your Fireblocks workspace and then reconnect it. This may require generating a new API key and API secret from your exchange account settings. Resubmit the transaction after reconnecting the exchange account. Contact Fireblocks Support if this issue persists.

NO_DEPOSIT_ADDRESS

The NO_DEPOSIT_ADDRESS substatus indicates the transaction failed because the deposit address was unavailable or has not been created on a third-party service, such as an exchange.

Resolution

Verify the deposit address is accurate, and then resubmit the transaction. If this issue occurs repeatedly, delete the exchange account from your Fireblocks workspace and then connect it again. This may require generating a new API key and API secret from your exchange account settings. Resubmit the transaction after reconnecting the exchange account. Contact Fireblocks Support if this issue persists.

SPEND_COINBASE_TOO_EARLY

The SPEND_COINBASE_TOO_EARLY substatus indicates the transaction failed because the assets you are trying to withdraw from your Coinbase exchange account have not reached the minimum number of blockchain confirmations. You can withdraw the assets after they receive the required number of confirmations.

SUB_ACCOUNTS_NOT_SUPPORTED

The SUB_ACCOUNTS_NOT_SUPPORTED substatus indicates the transaction failed because this exchange integration doesn't support transactions between main and sub-accounts or between different sub-accounts. This substatus is displayed as an Internal Error in the Recent activity panel of the Fireblocks Console. The Fireblocks API and the Fireblocks Console transaction history display this status directly.

Resolution

You can only create transactions in Fireblocks to or from this exchange’s main account. Use your exchange account portal to transact with this sub-account.

THIRD_PARTY_INTERNAL_ERROR

The THIRD_PARTY_INTERNAL_ERROR substatus indicates the transaction failed due to Fireblocks receiving an internal error response from a third-party service, such as an exchange. This error is most commonly associated with Binance.

Resolution

UNSUPPORTED_ASSET

The UNSUPPORTED_ASSET substatus indicates the transaction failed because the specified asset is not supported by the third-party service, such as an exchange.

Resolution

Confirm the asset is available and enabled in your exchange account settings. Then, submit a transaction with a lower asset amount as described in resolving transactions with unmapped or unsupported assets.

Blockchain issues

DOUBLE_SPENDING

The DOUBLE_SPENDING substatus indicates the transaction failed due to the blockchain determining a transaction with a duplicate hash exists in the mempool. This could be caused by a Fireblocks internal error or by another user signing with the full private key outside of Fireblocks. This is only relevant for UTXO-based blockchain transactions. Only the initial transaction is processed in this case.

Resolution

Check the status of the initial transaction in your transaction history for any issues. Check the Fireblocks Status page for ongoing service disruptions. If there are none, resubmit your transaction. Contact Fireblocks Support for assistance if the transaction fails repeatedly.

DROPPED_BY_BLOCKCHAIN

The DROPPED_BY_BLOCKCHAIN substatus indicates the transaction failed because it was replaced on the blockchain by another transaction with a higher fee. The funds and fees from this transaction are returned to the transaction's source account. Learn more about RBF transactions.

Resolution

Confirm the status of the replacement transaction. If the RBF transaction is complete, there is no need to resubmit the transaction.

INSUFFICIENT_RESERVED_FUNDING

The INSUFFICIENT_RESERVED_FUNDING substatus indicates the transaction failed because a minimum amount of the selected asset must remain in the asset wallet at all times.

Resolution

Resubmit the transaction with an amount that leaves at least the minimum required balance in the source account. Learn more about minimum balances.

INVALID_SIGNATURE

The INVALID_SIGNATURE substatus indicates the transaction failed because the blockchain rejected it due to an invalid signature.

Resolution

Check the Fireblocks Status page for ongoing service disruptions. If there are none, resubmit your transaction. Contact Fireblocks Support for assistance if the transaction fails repeatedly.

PARTIALLY_FAILED

The PARTIALLY_FAILED substatus indicates that one or more aggregated transactions submitted as a single operation have failed. Note that aggregated transactions are submitted to the blockchain network individually and can be partially or fully completed or fail.

Resolution

Confirm the status and substatus of each aggregated transaction, and determine the issue for each to find a resolution.

POWERUP_SUGGESTION_FAILURE

The POWERUP_SUGGESTION_FAILURE substatus indicates the transaction failed due to a Fireblocks internal error during processing transaction fees on the EOS blockchain. This substatus is displayed as an Internal Error in the Recent activity panel of the Fireblocks Console. The Fireblocks API and the Fireblocks Console transaction history display this status directly.

Resolution

Check the Fireblocks Status page for ongoing service disruptions on the EOS blockchain. If there are none, resubmit your transaction. Contact Fireblocks Support for assistance if the transaction fails repeatedly.

REACHED_MEMPOOL_LIMIT_FOR_ACCOUNT

The REACHED_MEMPOOL_LIMIT_FOR_ACCOUNT substatus only occurs with transactions on the Tezos blockchain. The blockchain's mempool does not allow more than one active transaction from an account. Therefore, if one transaction from that source vault account already exists in the mempool, all other transactions that are pending blockchain confirmations will be rejected.

Resolution

Wait until all previous Tezos transactions from the same vault account have been completed or failed before sending another transaction from that same source vault account.

REJECTED_BY_BLOCKCHAIN

The REJECTED_BY_BLOCKCHAIN substatus indicates the transaction failed due to being rejected by the blockchain or the EOS node.

Resolution

Typically, transactions are rejected by the blockchain when the selected fee is significantly lower than the current average rate. Resubmit this transaction with a higher fee, or check blockchain network activity and resubmit when the network is less active.

On the Solana network, transactions can be rejected by the blockchain when they leave the account without enough lamports to cover the account's rent. Any amount left in the account that is less than the required rent but greater than zero will cause the transaction to be rejected. To prevent this:

Deposit more SOL into the account or verify that the transaction will leave enough SOL to cover the account's rent before submitting the transaction.
Empty your Solana wallet. This prevents the transaction from being rejected but also deactivates your Solana account.

TOO_LONG_MEMPOOL_CHAIN

The TOO_LONG_MEMPOOL_CHAIN substatus indicates the transaction failed because you are trying to use an unconfirmed output with more than 25 descendent transactions.

Resolution

To prevent this from happening, do not use unconfirmed UTXO transactions. If you have unconfirmed UTXO transactions, use Child Pays for Parent (CPFP) or replace them with new transactions.