Skip to main content
Deposit with Crypto is in Early Access. Contact us to join the design partner program.
Deposit with Crypto 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.
In the SDK, this product uses the checkout namespace on the JavaScript client. For implementation details, see Checkout Flow and createCheckoutTransaction.

​
How it works

  1. Create a checkout — Set your settlement token, chain, destination, and accepted sources.
  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 checkout flows with a fixed price.
  • Deposit — The user sets the amount. Configure minimums and presets. Use this for account funding.

​
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 transaction, and settle directly to a Fireblocks vault or embedded wallet.

​
Agentic deposits

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

​
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

Deposit with Crypto supports many source chains: EVM, Solana, Sui, Bitcoin, Stellar, and TON. Users can deposit from whichever chain they hold assets on.
Automatic swap and bridging is currently available for EVM, Solana, Sui, and Bitcoin. Deposits from Stellar and TON settle as-is in the source token.

​
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

Coming soon: unique per-transaction deposit addresses so users or systems can send funds without connecting a wallet or exchange.

​
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 checkout transaction. 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 transaction lifecycle and are included in webhook payloads. Memos also satisfy chain-level requirements for networks like Stellar and 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.

​
Building your UI

This release is API-first. Call the SDK methods directly and render your own interface. This works across web, React Native, and any mobile framework. A pre-built UI widget is coming soon.

​
Webhooks

HMAC-signed events fire at every lifecycle transition:
  • Execution state changes (created → submitted → confirmed → settled)
  • Settlement state changes
  • Risk and compliance state changes
  • Quote updates
See Webhooks setup for configuration.