Skip to main content
Connect your Fireblocks workspace to Corsa to automatically sync vault accounts, wallets, and transactions into a unified compliance view.

​
What Gets Synced

Fireblocks DataCorsa EntityDescription
Vault AccountsCorporate ClientsEach vault account is mapped to a Corsa corporate client.
Deposit AddressesBlockchain WalletsEvery deposit address becomes a tracked blockchain wallet.
TransactionsDeposits & WithdrawalsIncoming/outgoing transactions are mapped to Corsa operations.

​
Real-Time Updates via Webhooks

EventWhat Happens
transaction.createdNew transaction is synced immediately.
transaction.status.updatedStatus/confirmation changes are reflected.
vault_account.createdNew vault accounts are created as corporate clients.
vault_account.asset.addedNew asset wallets and deposit addresses are synced.

​
Setup Guide

​
Prerequisites

  • A Fireblocks workspace with Admin or Non-Signing Admin access.
  • Access to Corsa’s Settings → Integrations page.

​
Step 1 - Create the Integration in Corsa

  1. Navigate to Settings → Developers → Integrations in Corsa.
  2. Select Fireblocks from the available integrations.
  3. Optionally configure the polling interval (default: 10 minutes).
  4. Click Create.
Corsa will generate:
  • A Certificate Signing Request (CSR) for Fireblocks API authentication
  • A Webhook URL for Fireblocks events
  • A list of webhook events to enable

​
Step 2 - Create an API User in Fireblocks

  1. Open the Fireblocks Console.
  2. Go to Settings → Users → API Users.
  3. Click Add API User.
  4. Upload the CSR file from Corsa.
  5. Set the role to Viewer.
  6. Copy the API User ID (API Key) that Fireblocks provides.

​
Step 3 - Configure Webhooks in Fireblocks

  1. In the Fireblocks Console, go to Settings → Webhooks.
  2. Click Add Webhook.
  3. Paste the Webhook URL from Corsa.
  4. Enable the following events: transaction.created, transaction.status.updated, vault_account.created, vault_account.asset.added.
  5. Save.

​
Step 4 - Complete Setup in Corsa

  1. Enter the Fireblocks API User ID.
  2. Click Complete Setup.
The integration status will change to Active and the first data sync begins automatically.

​
How It Works

​
Data Sync

  • Partial sync - Runs on the configured polling interval (default: every 10 minutes). Fetches only changes since the last sync.
  • Full sync - Can be triggered manually. Re-syncs all vault accounts, wallets, and transactions.

​
Webhook Processing

Webhook events are processed in near real-time. The webhook signature is validated (RSA-SHA512 or JWKS-based verification) before processing.

​
Entity Mapping

  • Vault Accounts → Corporate Clients: Each vault account becomes a corporate client. customerRefId is preserved.
  • Deposit Addresses → Blockchain Wallets: Each deposit address is tracked as a blockchain wallet, associated with the owning corporate client.
  • Transactions → Deposits & Withdrawals: Incoming transfers to your vaults are deposits; outgoing are withdrawals. Full metadata is preserved.

​
Security

  • CSR-based authentication ensures the private key never leaves Corsa’s infrastructure.
  • Webhook signatures are cryptographically verified on every incoming event.
  • API credentials are securely stored and encrypted.
  • All communication uses HTTPS/TLS.

​
Troubleshooting

IssueResolution
Integration stuck on “Pending Setup”Complete all four setup steps including entering the API User ID.
Data is not syncingVerify integration is Active, API user has correct permissions, and is not expired.
Webhooks not receivedConfirm webhook URL matches, all event types are enabled, and webhook is not paused.
Missing vaults or walletsEnsure vault accounts are not hidden. Wait for next sync or trigger a full sync.
Transactions not appearingOnly transactions involving your vault accounts are synced. Ensure webhooks are configured.
Corsa offers native integrations with leading compliance, blockchain analytics, and custody providers. See all integrations or schedule a demo to see how Corsa fits into your stack.