Fireblocks Flow

Fireblocks Flow is the layer between your app and the wallets, exchanges, and chains your users already use. It has three parts, each with its own section in this guide:

• Connections connect a user’s wallet or exchange account to your app. They work on their own, with no payment attached.
• Payments move value from a payer to a destination you control, converting the token and chain on the way when needed.
• Compliance checks, such as wallet ownership verification and spam token filtering, run on their own whenever your app needs them.

Moving value is enterprise-only. Please contact us to enable it. Connecting an external wallet natively through a Dynamic SDK is available on all plans, and is useful on its own as an authentication method with no transfer attached.

Connections

A connection links something the user already has to your app:

• Wallet connections let a user connect a wallet they own, natively in your app or through a hosted page.
• Exchange connections let a user link an exchange account so you can read balances and make transfers.

Connections

The kinds of connection, and which work on their own or in a payment.

Exchange connections

Linking an exchange account, permissions, and transfers.

Payments

Flow payments moves value from a payer to a destination you control. A payment passes through three stages.

1. Payment source

   Where the payer’s funds come from: a wallet they own, an exchange purchase, or a deposit address generated for the payment.

2. Conversion

   How funds are requested from that source and routed. If it holds something other than what you settle in, a swap or bridge runs automatically.

3. Settlement

   Where and how the funds land. Your token, your chain, your address.

Each stage is configured independently, which is what makes Flow payments direction-agnostic: the same three stages handle value arriving and value leaving.

Flow payments

Who does what, the modes, and when a payment is done.

Payment lifecycle

Every state a payment moves through.

Screening

Which addresses are screened, and when.

Compliance

Compliance checks run outside a payment, and your app decides when to trigger them: for example, verifying that a user owns a wallet, or filtering spam tokens out of the balances you show. They are separate from the screening that every Flow payment includes.

Compliance

Wallet ownership verification, spam token filtering, and name matching.

Screening

The risk screening included in every Flow payment.

Use cases

• Merchant and PSP acceptance. Accept any token on any chain, and settle in the stablecoin you choose. Users never bridge or swap manually, whether you’re accepting deposits directly or processing them for your own merchants.
• iGaming and prediction markets. Accept deposits from a wallet, through an exchange, or to a deposit address, screen wallet payers, and settle to a Fireblocks vault or embedded wallet.
• Agentic deposits. AI agents create flows and submit deposits through the API, paired with server wallets for automated payments.
• Withdrawals. Pay out from your treasury or vault to a user’s wallet, converting chains and tokens in one flow. See Modes.

Dynamic does not control the swap, bridge, or routing protocols used to convert and deliver assets. Rates and fees are sourced from third-party providers and may change between quote and execution. Cross-chain transfers carry risk, including slippage, partial fills, and failed conversions. On-chain transactions are final and cannot be reversed. These materials are not investment, financial, legal, or tax advice. You are responsible for evaluation at your own discretion. Fireblocks Flow is infrastructure. Please review Dynamic terms and conditions for full details on acceptable use.