Sumsub is one of the providers you can connect for Travel Rule messaging. 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. Setup is through the API only, and Fireblocks Support configures the rules on request.
How it works
A transaction with Sumsub moves through three rule stages, in order:
- Trigger (Screening Policy): decides whether a transaction needs Travel Rule review at all: Screen (continue to the next stage) or Pass (approve immediately, no review).
- Missing Travel Rule Message: if review is needed but no Travel Rule message exists yet, this stage decides what happens while one is obtained: Wait, Accept anyway, or Reject. You can set different rules based on how long it has been waiting, for example accepting small transactions after 30 minutes but rejecting large ones.
- Outcome (Post-Screening Policy): once Sumsub returns a result, this stage applies the final action: Accept, Reject, Alert, or continue to Wait if the result is still pending.
Each stage evaluates its rules top to bottom, with a required catch-all default, the same as any other Trigger or Outcome.
If a transaction has multiple destinations, each one is evaluated independently, and the most restrictive result across all of them applies to the transaction as a whole.
If a Travel Rule message you created for the same transaction already exists, Fireblocks links it when its ID is on the transaction. For incoming transfers, Fireblocks also asks Sumsub for a matching message by transaction hash, address, amount, and asset. For outgoing transfers, you supply the message ID.
A transaction's screening status is one of: Completed, Pending, Bypassed (approved without review, per your Trigger rule), or Failed.
Setup
Before you begin, contact your Customer Success Manager to enable this feature, and plan your legal entity structure. Most customers only need one legal entity, covering their whole workspace.
Setup happens through the API rather than the Console:
- Create a legal entity, specifying its scope (your whole workspace, or specific vault accounts) and a discoverability setting: Anonymous (default: counterparties cannot see your entity details, though Fireblocks confirms the address exists), Hidden (nothing disclosed at all), or Discoverable (full details shared).
- Connect the legal entity to Sumsub. Sumsub supports auto-connect: once you generate an integration ID, you share it with Sumsub and Sumsub sends your credentials to Fireblocks directly, rather than you entering them manually.
Rule configuration for all three stages is not self-service. You fill out a policy template and submit it to Fireblocks Support, who apply it on your behalf. Policy changes should go through your organization's compliance approval process before you submit them.
Policy templates and examples are on the Developer Portal’s Sumsub page, Step 3.
To update credentials later, submit a ticket to Fireblocks Support.
Several Fireblocks workspaces can use one Sumsub account.
Supported assets
Download the attached spreadsheet of supported assets.
System timeouts
Fireblocks enforces non-configurable limits so a transaction never waits indefinitely: 1.5 hours maximum for outbound transactions, 7 days maximum for incoming ones. When approaching a limit, a Wait rule is skipped rather than holding the transaction past it.
Testing
Start with testnet assets (BTC_TEST, ETH_TEST5, XRP_TEST) before testing with real value.
Monitoring
The Transaction History page in the Console shows the applied policies and rules, Sumsub's responses, and the final verdict with an explanation for each transaction.
Limitations
Sumsub runs alongside GTR and TRUST, not Notabene. Disconnecting through the API removes the policy and permanently deletes the stored credentials. Deleting a legal entity deletes its integrations and messages. Sumsub generates the key pair; you cannot upload your own.
Developer Portal
See Sumsub for the API steps, message encryption, and the policy templates.