Notabene is one of the Travel Rule providers you can connect. Fireblocks sends transaction details to Notabene, and uses the response to decide what happens to the transaction automatically. See Building a Compliance Policy for how Trigger and Outcome work in general, and About Travel Rule for how Travel Rule fits into your compliance policy overall.
This is a premium, opt-in feature that requires an additional purchase.
Contact your Customer Success manager for more information.
How it works
If Anti-Money Laundering (AML) screening is enabled for your workspace, it runs before Travel Rule screening. Beyond that, screening works a little differently depending on direction:
- Outgoing. Your Trigger determines whether the transaction gets sent to Notabene. If it does, Fireblocks shares the asset, amount, origin address, beneficiary address, and blockchain hash.
- Incoming. The same check runs only after the transaction receives its first blockchain confirmation, since checking any earlier can mean Notabene does not yet recognize the transaction exists. If no Travel Rule message is attached, Fireblocks creates a blank one so it can still be screened.
Notabene returns a status, and your Outcome applies an action based on it:
Status |
What it means |
|---|---|
Completed |
Screening finished successfully. |
Pending |
Still in progress. You can accept the transaction as-is, or wait up to four hours for a result before it is automatically canceled. |
Rejected |
The destination VASP was not recognized, or the beneficiary VASP declined the request. |
Failed |
Screening could not complete, for reasons like incomplete Travel Rule data or a Notabene-side error. |
Blocking Time Expired |
The configured time for holding a transaction while waiting for a result ran out. |
Canceled |
Screening was canceled; for outgoing transactions, you can choose whether to proceed anyway. |
Some transaction routes are never sent to Notabene at all: vault-to-vault, vault-to-exchange, Gas Station-to-vault, and non-custodial-wallet-to-non-custodial-wallet within the same workspace.
Fireblocks does not permanently store Travel Rule data. It is encrypted and held by Notabene; Fireblocks does not hold the decryption keys.
Setup
Before you begin: create a Notabene account, configure it to your preferences, and complete the general setup of your compliance integrations.
By default, your Notabene production environment connects to Fireblocks production, and your Notabene sandbox connects to Fireblocks sandbox. For any other pairing, contact Fireblocks Support.
To connect a single entity:
- In the Fireblocks Console, go to Settings > Compliance > Travel rule > Connect provider.
- Enter the API key, Secret key, and VASP DID from your Notabene dashboard.
- Select Connect provider. You will get an email once it is approved.
- Integrate the Travel Rule SDK or API calls to submit transactions for validation.
Default Screening and Post-Screening policies apply automatically until you create your own.
If you operate multiple legal entities, you can connect them as a Gateway VASP with subsidiary Virtual Asset Service Providers (VASPs) beneath it, so each vault account maps to the right entity. This involves creating the entities in Notabene, having Notabene establish the Gateway/subsidiary relationship, generating a shared encryption key, and mapping vault accounts to VASPs via the API.
Each vault maps to exactly one VASP; each VASP can cover many vaults.
We recommend defining which Notabene status a transaction must reach before Fireblocks treats screening as complete; this is configured in your Notabene dashboard.
To switch to new API keys, submit a ticket to Fireblocks Support with the new API key, Secret key, and VASP DID.
Processing
The subsections below describe how processing works.
Testing
Use Notabene's test VASPs (RoboVASPs) to verify your integration before relying on it in production.
Supported assets
Notabene generally supports any asset listed on CoinGecko; Fireblocks supports a subset. Testnet assets BTC_TEST, ETH_TEST4, and XRP_TEST are supported. You can request additional assets by contacting Fireblocks Support.
Incoming transfers from Fireblocks P2P Network connections default to an "Unsupported Asset" status.
Developer portal
See Travel Rule with Notabene for the API and SDK integration.