Use connected provider accounts to monitor balances, deposit and withdraw funds, transfer between account types, and manage collateral through Off-Exchange. Connected accounts include main accounts, sub-accounts, trading accounts, fiat accounts, and Off-Exchange accounts.
All connected provider accounts appear on the Connected Accounts/Fiat page in the Console.
Connected account types
Main accounts
Main accounts are the primary connection to each provider. They support:
- Deposits and withdrawals
- Transfers to and from Fireblocks vault accounts
- Rebalancing across sub-accounts and trading accounts
Key rules:
- You must connect the main account before connecting sub-accounts
- All deposits and withdrawals must flow through the main account
- Providers may require you to whitelist your vault address or other destinations
- You may need to adjust workspace Policies to allow provider-to-provider or external withdrawals
Sub-accounts
Sub-accounts allow you to segment funds by team or strategy.
- Sub-accounts are usually funded through the main account
- Withdrawals must typically route through the main account
- Transfers between main ↔ sub-accounts are off-chain and do not incur network fees
- Transfers between sub-accounts may not be supported
- All sub-account transfers follow your workspace Policies
- Assets held in sub-accounts do not appear on the My Assets page
Trading accounts
Trading accounts include spot, margin, derivatives, futures, and options accounts. Fireblocks provides visibility and rebalancing support for trading accounts.
- Deposit funds into a main or sub-account first, then transfer to trading accounts
- Transfers between trading accounts and the main account are off-chain and do not incur network fees
- Some providers require enabling trading in the API settings
- Trading account balances appear under each provider on the Accounts page
(Provider-specific trading account mappings are available in the Account Types and Provider Features Glossary.)
Fiat accounts
Connected fiat accounts support:
- Balance monitoring
- Transfers to Fireblocks P2P Network peers
Connecting a provider account
For provider-specific connection requirements and supported account types, see the Integrated exchange accounts article.
Use the following general steps to connect provider accounts:
-
Generate API credentials
- Create an API key and secret in the provider portal
- Enable required permissions (for example: Read/Write, Withdrawals, Spot, Margin, Futures)
-
Restrict access
- Whitelist Fireblocks IP addresses and remove any open access entries
-
Connect in Fireblocks
- In the Console, go to Accounts > Connected Accounts/Fiat
- Select the provider and enter the credentials
-
Request approval
- The Admin Quorum or an Approval Group must approve the connection
-
Verify the account
- Confirm that balances appear and test small operations such as a deposit, withdrawal, or balance retrieval
Fireblocks encrypts provider API keys and stores them in a secure environment.
View balances
- All connected provider accounts appear on the Connected Accounts/Fiat page
- Assets held in main accounts and sub-accounts also appear in aggregated balances and on the My Assets page
- Asset representation: Assets held in connected accounts are often represented by a single balance that can be transferred via multiple blockchain networks.
- Network Selection: When transferring these assets, you must select the appropriate network from the drop-down menu in the transfer dialog.
- Visibility Constraints: Assets in sub-accounts or trading accounts may not appear on the My Assets page, depending on the specific provider's API capabilities.
Withdraw funds
Withdrawal flow
Withdrawing funds from a provider account to a vault account or external destination includes the following steps:
- Submit a withdrawal request in Fireblocks.
- Approve the request on your mobile device according to your workspace Policies.
- Approval is only required because the provider is the source of funds.
- The provider broadcasts the transaction to the blockchain.
Whitelisting addresses
Most providers require you to whitelist withdrawal destinations.
To whitelist a vault address:
- In the Console, go to Accounts > Vault.
- Open the vault account.
- Select See Deposit Addresses for the asset.
- Copy the address and paste it into the provider’s whitelist or address book.
To whitelist a Fireblocks external whitelisted address:
- In the Console, go to Whitelisted Addresses.
- Copy the address.
- Paste it into the provider’s whitelist or address book.
Notes:
- Some providers may enforce a delay of up to 48 hours when enabling a new whitelisted address
- Bitcoin and some other assets support multiple address types; use the legacy address when required
- Withdrawals to external wallets or one-time addresses do not generate a network record or transaction ID in Fireblocks, because the source and destination are outside Fireblocks' custody
- Withdrawals must route through the main account. Sub-account > Main > Destination.
Deposit funds
Deposit flow
Depositing funds from your vault to a provider account includes the following steps:
- Submit a deposit request in Fireblocks.
- Sign the transaction on your mobile device or using an API Co-Signer.
- Signing is required because Fireblocks is the source of funds.
- Fireblocks broadcasts the transaction on-chain.
Deposit rules
- Deposits must flow through the main account.
- Some providers enforce minimum deposit amounts. Deposits below the threshold fail.
- For some providers (such as OKX), below-minimum deposits are not recoverable.
Internal transfers and rebalancing
You can transfer funds internally between supported account types:
- Main ↔ Sub-accounts
- Main ↔ Trading accounts
- (For some providers) Trading ↔ Trading accounts
Notes:
- Transfers are off-chain and do not incur network fees
- All internal transfers appear in the Fireblocks Audit Log
- Assets held in sub-accounts do not appear on the My Assets page
- Workspace Policies may require updates to allow certain transfer directions
Off-Exchange
Off-Exchange lets you manage collateral directly through Fireblocks while trading on supported centralized providers. Supported operations include:
- Adding and removing collateral through a collateral vault account
- Settling account balances with the provider
- Tracking assets, balances, available collateral, provider credit, and transactions
Security of provider API keys
Fireblocks encrypts provider API keys and stores them in a secure Fireblocks environment as part of its secure cloud architecture.