Skip to main content

[V2.1] Wallet Providers

Link your Fireblocks workspace so the Travel Rule message of each withdrawal reaches Notabene and your policies.

Written by Emanuel

If your assets are held in Fireblocks, Notabene can be your Travel Rule provider. Your transactions keep running in Fireblocks, and the Travel Rule message of each withdrawal comes to Notabene, where your policies run on it. You link the two once, under Settings › Wallet Providers, where Fireblocks is the provider listed.

Who does what

  • Fireblocks: sends Notabene the Travel Rule message of each withdrawal, holds the transaction until the Travel Rule checks are complete, and reports the transaction hash once the funds move.

  • Notabene: screens the data, runs your policies, exchanges the message with the counterparty institution, and tells Fireblocks every status change.

  • Your team: sets your policies in the dashboard, and approves or rejects the transfers your policies leave to it.

Requirements

  • TR Link turned on for your Fireblocks workspace, which Fireblocks Support does, and an API user for that workspace.

  • An API credential for your Notabene account, as described in Generating API Credentials. Fireblocks uses it to call Notabene.

  • The region your Fireblocks workspace is hosted in: US, EU, EU2 or Sandbox.

Your engineering team then adds Notabene as your Travel Rule provider in Fireblocks and gives Fireblocks the API credential. Fireblocks answers with a customer integration ID, which you enter in the dashboard. The steps on the Fireblocks side are in Fireblocks in the developer docs.

Link your workspace

  1. In the dashboard, go to Settings › Wallet Providers.

  2. Under Providers, select Fireblocks.

  3. Enter the ID Fireblocks gave you in Customer Integration ID.

  4. Under Region, choose the region your Fireblocks workspace is hosted in.

  5. Turn Enabled on.

  6. Click Save.

The Wallet Providers screen with the Fireblocks settings

Choose the region your workspace is hosted in. Notabene sends its status updates to Fireblocks in that region, so with the wrong one they never arrive. A testnet workspace on Fireblocks production is in a production region, usually US.

A change can take up to 15 minutes to apply. To test first, link a Fireblocks test workspace to your Notabene sandbox account, then repeat the setup in production.

If you replace the API credential later, give Fireblocks the new one, or its calls to Notabene stop working.

Check the connection

Send a withdrawal from your Fireblocks workspace to an address outside it, because transfers between your own vaults are not screened. The transfer appears under Transactions in the dashboard, where you approve or reject it if your policies leave it to your team, and Fireblocks then shows the matching status.

Transfers through Fireblocks

Your screening policy in Fireblocks decides which transactions go to Notabene, and your post-screening policy decides what Fireblocks does at each status. In Notabene, your policies approve the transfer, or flag it so a person on your team decides, as described in Policies. When a counterparty institution sends you a Travel Rule message, Notabene passes it on to Fireblocks as well.

Fireblocks shows one of three statuses for the Travel Rule message:

  • PENDING: Notabene, the counterparty institution or your team still has something to do.

  • ACCEPTED: the Travel Rule checks are complete and Fireblocks may send the transaction. It does not mean the funds have moved.

  • REJECTED: one of your policies, your team or the counterparty institution rejected the transfer, or it was canceled.

To connect a screening provider such as Chainalysis instead, see Integrations. If you need help linking your workspace, write to support@notabene.id.

Did this answer your question?