Fireblocks Flow

Fireblocks Flow lets your users pay from any wallet, exchange, or chain and you receive the token you want, on the chain you want, at the address you want.

​

Build with Fireblocks Flow

Integrate with Fireblocks Flow using the JavaScript SDK or raw HTTP. Both paths cover the full payment and deposit flow — pick the one that fits your stack: A pre-built UI widget is coming soon.

​

How it works

1. Create a flow (from your backend) — Set the mode, amount, settlement token, chain, and destination. Each flow is a single instance.
2. User connects — External wallet, exchange account, or deposit address.
3. Quote and convert — If the user’s asset doesn’t match your settlement config, a swap or bridge runs automatically.
4. Settle — Converted funds land at your destination. HMAC-signed webhooks fire at every state transition.

​

Modes

Two operating modes depending on your use case:

• Payment — You set the amount (for example, $25.00 in USDC). Use this for flows with a fixed price.
• Deposit — The user sets the amount. Configure minimums and presets. Use this for account funding.

​

Money in and money out

Fireblocks Flow is direction-agnostic. The source wallet, settlement token, and destination wallet are configured independently — so the same flow handles withdrawals and conversions out of your platform as well as deposits in. For per-user withdrawals from a shared treasury, specify the end user’s destination in the flow creation body. Withdrawals are supported through the Fireblocks Flow API guide only.

​

Use cases

​

Merchant and PSP crypto acceptance

Accept deposits in any token from any chain. Settle in USDC, USDT, or whichever stablecoin you prefer. Users don’t need to bridge or swap manually. Works whether you’re accepting deposits directly or processing them on behalf of your merchants.

​

Payment service providers

Offer crypto deposit acceptance to your merchant base without building wallet, conversion, or compliance infrastructure. Use the API behind your own UI.

​

iGaming and prediction markets

High-volume platforms can accept deposits from any user wallet or exchange, enforce compliance on every flow, and settle directly to a Fireblocks vault or embedded wallet.

​

Agentic deposits

AI agents can programmatically create flows, attach funding sources, and submit via the API. Combine with server wallets to automate deposits and make payments.

​

Withdrawals and currency conversion

Send funds from your platform out to a user-owned wallet, converting across chains and tokens in a single flow. Use withdraw mode with your treasury or vault as the source and the user’s wallet as the destination — for example, withdraw SOL from a Fireblocks vault and deliver USDC on Ethereum to the user’s self-custody address. Each withdrawal flow specifies the end user’s destination directly. See the Withdrawal flow in the API guide for step-by-step HTTP instructions.

​

Capabilities

​

Settlement currencies

Choose your settlement token and chain. If a user deposits a different asset, the system routes through a swap or bridge automatically. You receive what you configured.

​

Multi-chain support

Fireblocks Flow supports many source chains: EVM, Solana, Sui, Bitcoin, and TRON. Users can deposit from whichever chain they hold assets on.

​

Funding sources

​

Wallets

Users connect any supported external wallet — MetaMask, Phantom, Coinbase Wallet, and dozens more.

​

Exchanges

Users deposit directly from their exchange account balance. Supported exchanges include Coinbase, Kraken, Crypto.com, and Binance. Robinhood is coming soon.

​

Deposit addresses

​

Swap and bridging

Cross-chain and cross-token conversion is fully abstracted. Provider selection, execution, and failover happen behind the scenes. Integrator fees: You set your own fee on every swap transaction. This is direct revenue for your business.

​

Memos

Attach a memo to any flow. Use memos to tie deposits to internal order IDs, user accounts, invoices, or any identifier your system needs for reconciliation and reporting. Memos persist through the full flow lifecycle and are included in webhook payloads. Memos also satisfy chain-level requirements for networks like Cosmos where a memo or tag is required to route funds correctly.

​

Destination types

Funds can settle to:

• Custom address — Any address you provide. Works with Fireblocks vaults and embedded wallets.

​

Verification

Built-in compliance checks apply to all transactions. By default:

• Sanctions screening — Connected wallet addresses are screened before funds move.
• Geographic restrictions — IP-based blocking per your configuration.

Optional:

• Spam token filtering — Known spam tokens are blocked when signature verification is enabled.
• Name matching (optional) — Verify depositor identity against expected names.
• Signature verification — Require a signed message to prove wallet ownership.

​

Webhooks

HMAC-signed events fire at every lifecycle transition. There are three event types — one per axis:

• flow.execution.updated — execution state changes (e.g. initiated → source_attached → quoted → signing → broadcasted → source_confirmed)
• flow.settlement.updated — settlement state changes (e.g. none → routing → completed)
• flow.risk.updated — risk and compliance state changes (e.g. unknown → cleared)

Each event payload includes previousState and newState so your backend can react to specific transitions. See Webhook events for the full payload shape and Webhooks setup for configuration.