Overview

These substatuses apply to transactions in the Failed primary status. They are organized into five categories: user input issues, Fireblocks system issues, third-party account issues, third-party system issues, and blockchain issues.

User input issues

These substatuses indicate the transaction failed due to incorrect or invalid parameters provided by the user or the API request.

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 when network transaction fees increase 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. For more details, see 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. Some blockchains require a minimum transaction amount, or the transaction fee may be higher than the net transfer amount on a gross transaction.

Resolution

Confirm the transfer amount is above the required minimum for the blockchain, and that the transfer amount is greater than the required transaction fee before resubmitting the transaction. Minimum transfer amounts vary per blockchain. Known limits include 582 satoshi for Bitcoin (BTC) and 1 ADA plus applicable transaction fees for Cardano (ADA).

AUTHORIZATION_FAILED

The AUTHORIZATION_FAILED substatus indicates 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 or because the only available authorizer is the transaction's initiator.

Resolution

This occurs when the MPC device setup is not completed for an authorizer or one authorizer in a Policy 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 through 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 because the current blockchain fee is higher than the fee specified in the transaction. Fireblocks fails a transaction when 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 the blockchain to reject it. For more details, see EVM 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 a Replace-by-Fee (RBF) transaction. For more details, see 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

The GAS_PRICE_TOO_LOW substatus indicates the transaction failed on an Ethereum-based blockchain because the gas price encoded at the time the transaction was created was below the minimum allowed on the blockchain when sent to it. The vault has sufficient funds to cover fees, but the gas price itself is too low.

Resolution

Resubmit the transaction with a higher transaction fee, or wait for the gas price to decrease and try again with your original fee rate.

FEE_TOO_LOW

The FEE_TOO_LOW substatus indicates the transaction failed on a BTC-based blockchain because the overall fee is too low for the transaction.

Resolution

Resubmit the transaction with a higher fee.

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.

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 through the API. If the vault account's available balance is sufficient 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 (for example, USDC) are paid in the base asset (for example, ETH) from the same vault account as the transaction source.

Resolution

This substatus occurs when using the API. 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 through the API. You can also use the Fireblocks Gas Station to manage fees automatically and avoid this issue.

INTEGRATION_SUSPENDED

The INTEGRATION_SUSPENDED substatus indicates the transaction failed because Fireblocks halted an exchange integration. The substatus displayed in the Fireblocks Console is similar to one of the following:

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

Resolution

Contact Fireblocks Support to determine why the connection was blocked and to re-establish the connection.

INVALID_ADDRESS

The INVALID_ADDRESS substatus indicates the transaction failed because the destination is an unsupported format for a one-time address. For more details, see address types and formats.

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

Resolution

Verify the address format matches the asset and blockchain, and that the source and destination addresses are different, before resubmitting the transaction.

INVALID_CONTRACT_CALL_DATA

The INVALID_CONTRACT_CALL_DATA substatus indicates the transaction failed because its data was not encoded properly. This typically occurs due to an internal error or user error when using the Raw Signing feature.

Resolution

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

INVALID_FEE_PARAMS

The INVALID_FEE_PARAMS substatus indicates the transaction failed due to inconsistent or unknown fee parameters. For more details, see EVM fee parameters.

Resolution

Confirm all fee parameters are 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. For more details, see RBF transactions.

Resolution

Confirm the status of the original transaction before resubmitting the RBF transaction. RBF transactions can only replace transactions that are not Failed or Confirmed. Check the Fireblocks Status page for ongoing service disruptions. If there are none, resubmit the transaction. Contact Fireblocks Support 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 the 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 does not exist. This substatus appears in the Console as Approved wallet not found.

Resolution

Verify the wallet ID 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. For more details, see EVM 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 because the exchange did not record enough confirmations 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 because the exchange did not record enough confirmations 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 the transaction failed due to a missing destination tag or memo, which some assets require.

Resolution

Resubmit the 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. Polkadot requires a 1 DOT minimum deposit and Kusama requires a 0.0000333333 KSM minimum deposit. For more details, see the Polkadot existential deposit documentation.

NO_MORE_PREPROCESSED_INDEXES

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

The total number of signatures is determined during onboarding with your Customer Success Manager. This number is typically set to last around three years based on average transaction volume, but unusual working patterns may exhaust all available signatures sooner than expected.

Resolution

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 the transaction. For some exchanges, you may need to generate a deposit address manually in the exchange's account settings.

NOT_ENOUGH_DEPOSIT_CONFIRMATIONS

The NOT_ENOUGH_DEPOSIT_CONFIRMATIONS substatus indicates the transaction failed because the exchange did not receive 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 the transaction failed because the signer's key share must be updated to the MPC-CMP protocol.

Resolution

The designated signer must update their key share to the MPC-CMP protocol before attempting to sign a transaction again. For more details, see the MPC-CMP update for all Fireblocks users.

RAW_MSG_EMPTY_OR_INVALID

The RAW_MSG_EMPTY_OR_INVALID substatus indicates a raw signing transaction failed due to incorrect raw data. For more details, see raw data for off-chain messages.

Resolution

Validate the raw data before resubmitting the transaction.

RAW_MSG_LEN_INVALID

The RAW_MSG_LEN_INVALID substatus indicates a raw signing transaction failed due to incorrect raw data. Specifically, the message length parameter that applies to ECDSA signing is incorrect. For more details, see raw data for off-chain messages and how ECDSA signatures are used in Fireblocks.

Resolution

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

SMART_CONTRACT_EXECUTION_FAILED

The SMART_CONTRACT_EXECUTION_FAILED substatus indicates the transaction failed due to a smart contract error. If you are using the Fireblocks API, you can find the specific revert reason in the TransactionResponse object's errorDescription field.

Resolution

To resolve this error, try one of the following: initiate the transaction again with different parameters, use a different vault account to perform the transaction, or read the contract's source code to understand the error.

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

UTXO transactions on Fireblocks are limited to 250 inputs, except Cardano transactions (limited to 110 inputs) and ZCash transactions (limited to 50 inputs). Testnet workspaces using the Fireblocks Communal API Co-signer are limited 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, 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 it exceeded the allowed size. 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. Reduce the data size of the transaction before resubmitting.

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 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 when a user's setup is incomplete or a user was disabled before the transaction 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 if the transaction fails repeatedly.

UNALLOWED_RAW_PARAM_COMBINATION

The UNALLOWED_RAW_PARAM_COMBINATION substatus indicates a raw signing transaction failed due to incorrect raw data parameters. For more details, see raw data for off-chain messages.

Resolution

Validate the raw data parameters before resubmitting the 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 the transaction. Contact Fireblocks Support 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 through the Fireblocks API, confirm that the specified value for operation is TRANSFER or another valid value, and that 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 typed_message or raw transaction type, are not supported.

The transaction may also have failed due to a Fireblocks internal error. Contact Fireblocks Support if the transaction fails repeatedly.

ZERO_BALANCE_IN_PERMANENT_ADDRESS

The ZERO_BALANCE_IN_PERMANENT_ADDRESS substatus indicates the transaction failed because the permanent address does not hold enough Omni.

Resolution

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

Fireblocks system issues

These substatuses indicate the transaction failed due to an internal error in the Fireblocks system. For most of these, check the Fireblocks Status page for ongoing service disruptions, resubmit the transaction if there are none, and contact Fireblocks Support if the transaction fails repeatedly.

CONNECTIVITY_ERROR

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

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 appears as an Internal Error in the Recent activity panel. The Fireblocks API and the Transaction History page display the substatus directly.

INTERNAL_ERROR

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

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. The transaction cannot be processed until the gap is filled.

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 previously confirmed transaction on this account.

Resolution

This may occur when an RBF or drop transaction replaces a pending transaction that completed before being replaced. If this transaction references another transaction, confirm the status of both transactions before resubmitting. Contact Fireblocks Support 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 is specific to Fireblocks Network transactions.

LOCKING_NONCE_ACCOUNT_TIMEOUT

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

NETWORK_ROUTING_MISMATCH

The NETWORK_ROUTING_MISMATCH substatus indicates the transaction failed because the Fireblocks Network could not identify a valid routing destination. This substatus appears as an Internal Error in the Recent activity panel. The Fireblocks API and the Transaction History page display the substatus directly.

NONCE_ALLOCATION_FAILED

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

RESOURCE_ALREADY_EXISTS

The RESOURCE_ALREADY_EXISTS substatus indicates the transaction failed due to a Fireblocks internal error during processing. This substatus appears as an Internal Error in the Recent activity panel. The Fireblocks API and the Transaction History page display the substatus directly.

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 Policy does not have an MPC signing device setup, or the designated signer is no longer active in your workspace. Confirm the designated signer is available and has completed their MPC device setup before resubmitting the 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 update their Fireblocks mobile app to the current version before resubmitting the transaction. If the issue persists, contact Fireblocks Support and include the Fireblocks mobile app version. If the API Co-signer signed the transaction, generate your Co-signer's logs and include them in your support request.

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.

Resolution

Confirm all approvers and signers are using the most recent version of the Fireblocks mobile app before resubmitting. All relevant users must approve and sign the transaction within the required time.

If approval and signing were completed within the required time, check the Fireblocks Status page for ongoing service disruptions. If there are none, resubmit the transaction. Contact Fireblocks Support 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.

UNKNOWN_ERROR

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

UNSUPPORTED_MEDIA_TYPE

The UNSUPPORTED_MEDIA_TYPE substatus indicates the transaction failed due to a Fireblocks internal error during processing. This substatus appears as an Internal Error in the Recent activity panel. The Fireblocks API and the Transaction History page display the substatus directly.

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 usually occurs after creating multiple asset wallets in the same vault account at once through the API. Activate the asset wallet using the API before resubmitting the transaction.

Third-party account issues

These substatuses indicate the transaction failed due to a configuration problem with a third-party account connected to your Fireblocks workspace.

ADDRESS_NOT_WHITELISTED

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

API_KEY_MISMATCH

The API_KEY_MISMATCH substatus indicates the transaction failed because the third-party account API connectivity information is no longer accurate.

Resolution

Confirm that the API Key, API Secret, and other parameters are valid according to your third-party account portal. Delete and re-add the third-party account to your Fireblocks workspace before resubmitting the transaction.

ASSET_NOT_ENABLED_ON_DESTINATION

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

DEST_TYPE_NOT_SUPPORTED

The DEST_TYPE_NOT_SUPPORTED substatus indicates 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, so 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. If the destination is a whitelisted address, the name of the whitelisted wallet is identified as the beneficiary.

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

EXCEEDED_DECIMAL_PRECISION

The EXCEEDED_DECIMAL_PRECISION substatus indicates the transaction failed because a third-party service does not support the same number of decimal digits for a transaction amount as Fireblocks. This issue most commonly occurs with Coinbase, Coinbase Pro, and Crypto.com.

Resolution

Resubmit the transaction with fewer decimals in the transaction amount.

EXCHANGE_CONFIGURATION_MISMATCH

The EXCHANGE_CONFIGURATION_MISMATCH substatus indicates 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 results in a failed transaction.

EXCHANGE_VERSION_INCOMPATIBLE

The EXCHANGE_VERSION_INCOMPATIBLE substatus indicates 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 results in a failed transaction.

INVALID_EXCHANGE_ACCOUNT

The INVALID_EXCHANGE_ACCOUNT substatus indicates the transaction failed because the associated exchange account is disabled or does not exist.

METHOD_NOT_ALLOWED

The METHOD_NOT_ALLOWED substatus indicates 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 results in a failed transaction.

NON_EXISTENT_AUTO_ACCOUNT

The NON_EXISTENT_AUTO_ACCOUNT substatus indicates the transaction failed because the third-party account configuration is incorrect in your Fireblocks workspace. Currently, this only occurs with Paxos exchange accounts.

Resolution

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 resubmit the transaction.

ON_PREMISE_CONNECTIVITY_ERROR

The ON_PREMISE_CONNECTIVITY_ERROR substatus only applies to transactions using the Fireblocks On-Prem Exchange Service (FOPES). It indicates Fireblocks could not retrieve the third-party account details due to a connectivity error with 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: the sub-account name no longer exists on the third-party account, or the Fireblocks Network settings that previously directed to this account have been deleted.

Resolution

Verify your third-party sub-account configuration or Fireblocks Network settings before resubmitting the transaction.

UNAUTHORISED__IP_WHITELISTING

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

Resolution

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 for third-party integrations, and resubmit the transaction.

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 API permission on a third-party service, such as an exchange.

UNAUTHORISED__OTP_FAILED

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

Resolution

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 resubmit the transaction.

WITHDRAW_LIMIT

The WITHDRAW_LIMIT substatus indicates the transaction failed because it exceeded the exchange's withdrawal limit.

Third-party system issues

These substatuses indicate the transaction failed due to an error on the third-party service's side, such as an exchange outage or invalid response.

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 the transaction. Contact Fireblocks Support 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.

Resolution

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

API_INVALID_SIGNATURE

The API_INVALID_SIGNATURE substatus indicates the transaction failed because a third-party service's API provided an invalid signature.

Resolution

If this issue occurs more than once, delete the exchange account from your Fireblocks workspace and reconnect it. 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 because a third-party service canceled it.

Resolution

Contact the exchange with the transaction details to determine the issue. If the exchange is unable to resolve it, contact Fireblocks Support.

FAILED_AML_SCREENING

The FAILED_AML_SCREENING substatus indicates the transaction failed post-screening because the Anti-Money Laundering (AML) service provider or Travel Rule service provider did not communicate results. For more details, see 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 for the asset required for withdrawal and transaction fees. For more details, see 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 verify there is a sufficient balance for all fees before resubmitting the transaction.

INVALID_THIRD_PARTY_RESPONSE

The INVALID_THIRD_PARTY_RESPONSE substatus indicates the transaction failed because Fireblocks received an unrecognized or invalid response from a third-party service.

Resolution

Consult the third-party service for additional information. Exchanges may not communicate complete transaction status information to Fireblocks.

If this issue occurs repeatedly, delete the exchange account from your Fireblocks workspace and 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.

MANUAL_DEPOSIT_ADDRESS_REQUIRED

The MANUAL_DEPOSIT_ADDRESS_REQUIRED substatus indicates the transaction failed because Fireblocks encountered an error while retrieving a deposit address from an exchange.

Resolution

Generate a deposit address manually 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 resubmit the transaction. If this issue occurs repeatedly, delete the exchange account from your Fireblocks workspace and reconnect it. This may require generating a new API key and API secret from your exchange account settings. 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.

Resolution

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

SPEND_COINBASE_TOO_EARLY

The SPEND_COINBASE_TOO_EARLY substatus indicates the transaction failed because the UTXO assets received as mining awards in your Coinbase account have not reached the minimum number of blockchain confirmations. Bitcoin mining rewards require 100 confirmations before they can be withdrawn.

SUB_ACCOUNTS_NOT_SUPPORTED

The SUB_ACCOUNTS_NOT_SUPPORTED substatus indicates the transaction failed because this exchange integration does not support transactions between main and sub-accounts or between different sub-accounts. This substatus appears as an Internal Error in the Recent activity panel. The Fireblocks API and the Transaction History page display the substatus 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 the sub-account.

THIRD_PARTY_INTERNAL_ERROR

The THIRD_PARTY_INTERNAL_ERROR substatus indicates the transaction failed because Fireblocks received an internal error response from a third-party service. This error is most commonly associated with Binance.

Resolution

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

UNSUPPORTED_ASSET

The UNSUPPORTED_ASSET substatus indicates the transaction failed because the specified asset is not supported by the third-party service.

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

These substatuses indicate the transaction failed due to a blockchain-level rejection or error, such as being dropped from the mempool or rejected by a node.

DOUBLE_SPENDING

The DOUBLE_SPENDING substatus indicates the transaction failed because the blockchain determined a transaction with a duplicate hash exists in the mempool. This could result from a Fireblocks internal error or from 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.

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 the transaction. Contact Fireblocks Support if the transaction fails repeatedly.

DROPPED_BY_BLOCKCHAIN

The DROPPED_BY_BLOCKCHAIN substatus indicates the transaction failed before being confirmed on the blockchain, or was mined but dropped. Funds become available again in the source account. This can occur for several reasons:

• Nonce replacement (RBF): A higher-fee transaction with the same nonce replaced the original. This can result from a manual RBF submission or a Fireblocks boost or drop operation.
• Mempool eviction: The transaction was removed from the mempool due to a low gas price, network congestion, or a timeout.
• Network rejection: The transaction was rejected by the node before it could be included in a block.

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.

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 the transaction. Contact Fireblocks Support if the transaction fails repeatedly.

PARTIALLY_FAILED

The PARTIALLY_FAILED substatus indicates one or more aggregated transactions submitted as a single operation have failed. Aggregated transactions are submitted to the blockchain network individually and can partially or fully complete 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 fee processing on the EOS blockchain. This substatus appears as an Internal Error in the Recent activity panel. The Fireblocks API and the Transaction History page display the substatus directly.

Resolution

Check the Fireblocks Status page for ongoing service disruptions on the EOS blockchain. If there are none, resubmit the transaction. Contact Fireblocks Support 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 Tezos mempool does not allow more than one active transaction from an account, so if a transaction from that source vault account already exists in the mempool, all other transactions pending blockchain confirmations are rejected.

Resolution

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

REJECTED_BY_BLOCKCHAIN

The REJECTED_BY_BLOCKCHAIN substatus indicates the transaction failed because the blockchain or the EOS node rejected it.

Resolution

Transactions are typically rejected when the selected fee is significantly lower than the current average rate. Resubmit the 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 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 causes the transaction to be rejected. To prevent this, deposit more SOL into the account or verify that the transaction leaves enough SOL to cover rent before submitting. You can also empty your Solana wallet, which prevents the rejection 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 descendant transactions.

Resolution

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