Three live scenarios — checkout, deposit, withdraw — built on Fireblocks Flow infrastructure[†]. Run any of them in the browser and read the integration side-by-side.
Buyers pay with any token on any chain. Merchant receives the configured stablecoin every time.
Users fund a platform balance from any wallet or centralized exchange. Settles to their embedded wallet or your Fireblocks vault.
Cash out from a vault, embedded wallet, or external source to any user-chosen wallet and asset.
A Flow connects one of these on either side of the swap. Pick a source for the sender; pick a destination for settlement.
Dynamic-issued, non-custodial. Created in seconds.
Custodial, merchant-controlled. Settlement-ready.
MetaMask, Phantom, Coinbase Wallet, and 50+ more.
Coinbase, Kraken, Crypto.com — OAuth-delegated.
Pick the surface that matches the platform you're embedding into. Both speak to the same underlying Flow primitives.
Drop-in client for browser-based platforms. Handles wallet signing, broadcast, and settlement polling. The fastest path when your platform is a web app.
Language-agnostic and server-side. Same lifecycle, full control over the surface — pick this when your client isn't a browser, or when an autonomous workflow needs to drive the flow.
Webhooks aren't a way to build — they're how you stay informed about transactions running through your Flow. HMAC-signed lifecycle events your server can subscribe to from either integration path above.
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. Please review Dynamic's terms and conditions for full details on acceptable use.
