This article covers common Travel Rule issues and how to resolve them. If you need additional assistance, see the support resources at the end of this article.

Issue: Transactions are not being screened 

Resolution: 

• Verify that your legal entity configuration is completed properly.
• Check that vault accounts are correctly assigned to the appropriate legal entities in your workspace configuration.
• Review your Screening Policy rules to ensure they are structured correctly.

Issue: Unexpected verdicts

Resolution:

• Check rule ordering in your policies (e.g., first-match principle).
• Verify all matching criteria in your rules are configured with the correct values, thresholds, and conditions for your compliance requirements.
• Review timing constraints like validAfter and validUntil to ensure rules are active during the time periods when you expect them to apply. 

Issue: Provider connection errors

Resolution: 

• Confirm that the Integration ID generated during setup was properly shared with your Travel Rule provider (TRP).
• Verify that API credentials (e.g., secret key) are correctly entered in Fireblocks if you’re using a manual integration provider.
• Check with your provider to rule out any interruptions on their side.

Support resources

• Contact your Customer Success Manager for feature enablement
• Reach out to support@fireblocks.com for technical issues
• Consult your TRP for provider-specific questions