Overview

The Fireblocks Network provides a robust set of services and connections for implementing financial flows on the Fireblocks platform. These flows often span multiple steps, such as trading agreements with service providers, wiring fiat funds to bank accounts, and tracking stablecoin transfers to their final destinations. Using Orders, Fireblocks allows you to orchestrate and execute these operations directly from within your workspace, ensuring both security and efficiency. For a list of service providers via our API, see this endpoint. 

Financial Flows on the Fireblocks Network

On-ramp

An on-ramp refers to converting fiat money, like USD or EUR, into digital assets such as stablecoins. This process is commonly used for fast, transparent settlements and payments. For example, a business may convert dollars into USDC stablecoins for cross-border transactions, gaining real-time settlement speeds, simplified reconciliation, and improved capital efficiency.

Off-ramp

An off-ramp is the reverse process: converting digital assets back into fiat currency. This enables businesses or individuals to bridge digital and traditional financial systems. For instance, a customer holding stablecoins can use a service provider to convert them back into euros, which are then wired to their bank account, or they may choose to cash out at a kiosk or local shop.

Same-chain swaps

These are transactions where one digital asset is exchanged for another on the same blockchain. Fireblocks integrates with DeFi partners that allow 24/7, accountless swaps using smart contracts. Because smart contracts automate and enforce the trade, counterparty risk is minimized. For example, a user may swap ETH for DAI on Ethereum without relying on a centralized intermediary.

Cross-chain bridging

This is the movement of assets across different blockchains, often via centralized (CeFi), regulated service providers. It is useful for assets pegged to the same base currency. For example, a business might bridge USDC on Ethereum to USDC on Solana, or convert USDG to PYUSD to make specific payments.

First-Party vs. Third-Party Payments

The Fireblocks Network supports both first-party and third-party payments for service providers that offer the option:

• First-party transaction: A transaction where you transfer funds between accounts or wallets that belong to your organization. For example, a company that converts its fiat treasury into USDC for operational payments.
• Third-party transaction: A transaction where you initiate payments or asset conversions on behalf of a client or end-user. For example, a payment processor that converts a customer’s fiat deposit into stablecoins and delivers them to the customer’s wallet.

By supporting both models, Fireblocks enables institutions to operate for their own treasury needs and serves clients as part of a larger payment, trading, or settlement workflow.

Getting Started

To begin, you’ll need to onboard with one of the service providers available on the Fireblocks Network, depending on what you want to implement (On-ramp, off-ramp, swaps, bridging, or other use cases) and the required corridor. Once connected, you can orchestrate these flows directly within your Fireblocks workspace and securely manage all fund movement from end to end.

Prerequisites

• Complete commercial agreements and compliance requirements with one or more providers
• Add your provider account as a connected account
• Configure supporting Policy rules

Account hierarchy and capabilities

In some cases, your business model with the provider will have main and sub-accounts. You can use these to segregate accounts between your clients, using the account hierarchy held by the service provider. For instance, a PSP that serves different merchants for payouts and wants to keep each merchant account separate might use a different sub-account for each merchant.

When connecting a service provider account, Fireblocks discovers the sub-account list automatically and adds it to your workspace. If the service provider sets limits on some sub-accounts, that will be reflected in your workspace. 

As part of the account hierarchy discovery, Fireblocks also queries the service provider about capabilities for each account and sub-account. Accordingly, different actions, such as on/off ramp orders, swaps, deposits, withdrawals, and others, will be available in your Fireblocks workspace. 

Security capabilities for order management

The Fireblocks policy engine governs the creation and submission of policies. The engine is designed to provide granular control over all types of orders in a single policy rule.

To create a policy rule to allow an order, navigate to the Policies page in the Fireblocks Console, select Orders policy, select Edit policy, and add a new rule.

Please refer to the following policy examples to help you set up the correct rule according to the desired order type.

Viewing order history

The Order History page allows you to view, filter, and export all past and present orders with all available details. Orders from bank accounts take longer to process than transactions on a blockchain.