Note:
This feature is currently in Early Access. If you are interested in joining the Early Access phase, contact your Fireblocks Customer Success Manager.
The Manual Screening Verdict feature provides a simplified, non-automated flow for managing the compliance status of incoming transactions. Instead of relying on automated screening providers, this flow allows your team to review and decide on transactions manually, using your own internal tools and processes.
Important:
Manual Screening Verdict cannot be used together with Chainalysis or Elliptic integrations. You must choose one method for screening incoming transactions.
How it works
-
Pending Screening State
All incoming transactions are automatically flagged and moved to the PENDING_SCREENING state. At this stage, the transaction is paused until reviewed by your team. -
Manual Review
Your compliance team reviews the transaction using your internal procedures (e.g., AML checks or other risk controls). -
Submit a Verdict
Once the review is complete, submit your decision via the dedicated API endpoint:
POST /aml/verdict/manual
- ACCEPT: Releases the transaction from its pending state and allows it to be processed.
- REJECT: Flags the transaction as rejected for AML reasons. Rejected transactions are automatically frozen in Fireblocks.
-
No Verdict Submitted
If no verdict is provided within the timeout window (default: one hour), Fireblocks will automatically REJECT the transaction. -
Outgoing Transactions
Manual Screening Verdict applies only to incoming transactions. Outgoing transactions are not affected and bypass this flow automatically.
Configuration and setup
To enable and configure Manual Screening Verdict:
-
Enable the Feature
Contact your Fireblocks Customer Success Manager to have the feature flag enabled in your workspace. -
Set a Timeout
- The default timeout is one hour.
- Fireblocks can extend this timeout if required.
- If no verdict is submitted before the timeout, the system will automatically reject the transaction.
Note:
Without a timeout configuration, transactions may stall indefinitely. To prevent this, we strongly recommend setting a timeout and timeout action through Fireblocks Support.