Plans, Billing, and Payments

Fireblocks offers two subscription plans (Essentials and Custom), each with defined usage limits, billing metrics, and payment options. This article explains what's included in each plan, how Fireblocks measures your usage, and how to send payments.

Plans at a glance

Fireblocks offers two plans to match different stages of growth and operational complexity.

Essentials is a fixed monthly plan designed for teams getting started on the platform. It includes a production environment with a defined set of limits and features, and runs for up to six months.

Custom plans (Pro, Enterprise, and Enterprise+) are annual plans with negotiated limits, premium support options, and access to additional features. Contact your account team to discuss Custom plan options.

For the full feature breakdown, see the Fireblocks pricing page.

How Fireblocks measures usage

Fireblocks measures your platform activity across several billing metrics. Only mainnet activity counts toward billable usage. Testnet transactions and activity are never billed.

Outbound volume

Outbound volume is the total USD value of on-chain transactions sent outside your internal organization during a billing period. It is the primary metric used to calculate your service charges.

The following transaction types count toward your outbound volume:

• Vault to exchanges
• Vault to whitelisted addresses
• Vault to one-time addresses
• Vault to network connections
• Vault to smart contracts
• Vault to DeFi integrations, including swaps and liquidity provider (LP) tokens
• Exchange to any destination other than your vault accounts or whitelisted wallet addresses

The following transaction types do not count toward your outbound volume:

• Vault to vault within your workspace
• Vault to Gas Station
• Exchange to vault account
• Exchange to whitelisted wallet addresses in your workspace
• Exchange to subaccount or special account
• Assets not priced on standard price feeds
• LP tokens with no discernible value
• Mint and burn transactions for tokens

Overages

On the Essentials plan, if your outbound volume exceeds your $1,000,000 quota over your 6-month term, Fireblocks charges an overage rate of 0.20% per transaction on the excess volume. Overage rates on Custom plans are negotiated as part of your contract.

Assets under custody (AUC)

Assets under custody (AUC) is the total USD value of all assets held in vault accounts across your subscription. The platform calculates AUC daily at midnight UTC to produce a consistent snapshot of assets under your management.

Workspace users

Fireblocks counts workspace users toward your plan limit based on the following rules:

• Users who have reached "pending approval" status are counted.
• API users, disabled users, and users in disabled workspaces are not counted.
• Counting applies to all mainnet workspaces across your subscription.

Only active, human participants in your operations count toward your user quota.

Non-custodial wallets

Fireblocks tracks all active non-custodial wallets associated with your account toward your embedded wallet limit.

Vault accounts

A vault account counts toward your usage if it was used in one or more transactions during your subscription period, or if it holds a wallet with $1,000 or more in assets.

Billable addresses

Billable addresses are the deposit addresses Fireblocks monitors across your workspace. Monitoring covers all incoming and outgoing transactions and their statuses, maintains accurate balances, and determines whether new tokens sent to these addresses should be recognized in the workspace.

Two categories of addresses are billable:

• Vault addresses: All addresses in every vault account, including archived and hidden accounts.
• Whitelisted addresses: All addresses in whitelisted wallets that are assigned as internal.

Address counts vary by blockchain type:

• Account-based blockchains: One address is monitored for all assets on each blockchain per vault account. For example, an ETH asset wallet and a USDC (ERC-20) asset wallet in the same vault account count as one address.
• UTXO-based blockchains: Each permanent or deposit address is counted separately.
• Ripple: Each destination tag is counted as a separate address.
• Stellar, EOS, and Hedera Hashgraph: Each memo is counted as a separate address.
• Algorand: Each note is counted as a separate address.

To update the total number of billable addresses in your workspace, contact your Customer Success Manager.

User quota

Your plan includes a set number of users. When you reach that limit, the platform prevents you from adding new users. To regain access, you can:

• Remove an existing user to free up a slot.
• Contact your Customer Success Manager to expand your quota.

Sending payments to Fireblocks

Fireblocks accepts payment by stablecoin (preferred), credit card, and wire transfer or ACH/SEPA. If we are required to collect sales or use tax on your order, we will add applicable taxes to your invoiced amount unless you provide a valid tax exemption certificate at the time your Master Service Agreement is signed.

Fireblocks P2P Network

Fireblocks accepts and prefers payment via stablecoin over the Fireblocks P2P Network. Payments must be made using USDC or USDP (formerly PAX) on one of the following blockchains:

• Algorand
• Avalanche
• Ethereum
• Polygon
• Solana
• Stellar

If your workspace is in full production mode and the Fireblocks P2P Network is enabled, connect to Fireblocks Payments using counterparty ID: 6Z9dRPaC. This method requires no additional remittance information.

If your workspace is not yet set up or you have not received a Welcome email, use one of the methods below.

Direct stablecoin transfer

If you are not using the Fireblocks P2P Network, you can send USDC or USDP directly to a Fireblocks deposit address. After payment, email ar@fireblocks.com with the following remittance information so we can identify and credit your payment:

• Transaction hash
• Quote number or invoice number
• Payment amount
• Payment date

Fireblocks deposit addresses by network:

• ERC-20: 0x511D5d43DBbF359ae5Eb1Dc8265Ff7e014DF7A06
• Solana: HoW8uqBjmZpAWehqXtvip159bMs5AZLtcGE3S7ujLJMM
• Stellar: GAY3DNAXDMLD6KPPRXM2KC6FVRFRKERETN63TDU2B7XDL76WJSKAEAGH
• Algorand: OA75YXBYNM3JV2KXE2TJGSXNPSCD3CB2MBVVQGBPFO6BRWAA6BO4ESHT2U

Other payment methods

To arrange other methods of payment, email ar@fireblocks.com.

Frequently asked questions

What counts as outbound volume?

Any on-chain transaction sent outside your internal organization — including transfers to exchanges, whitelisted addresses, one-time addresses, smart contracts, and DeFi integrations. Internal transfers between your own vault accounts or workspaces under the same subscription do not count.

Are testnet transactions billable?

No. Only mainnet activity counts toward billable usage.

What happens when I reach my user limit?

The platform prevents you from adding new users. You can free up a slot by removing an existing user, or contact your Customer Success Manager to expand your quota.

How do I upgrade my plan or add users?

Contact your Customer Success Manager to discuss upgrading or adding users.

Where do I find my invoice or order form?

Your order form is provided at the time of contract signing. For invoice questions, email ar@fireblocks.com.

Which payment methods does Fireblocks accept?

Fireblocks accepts stablecoin payments via the Fireblocks P2P Network (preferred), direct stablecoin transfer, credit card via Stripe, and wire transfer or ACH/SEPA.

What stablecoins does Fireblocks accept?

Fireblocks accepts USDC and USDP (formerly PAX) on Algorand, Avalanche, Ethereum, Polygon, Solana, and Stellar.