Skip to content

Rule Engine

Define and review automated Travel Rule decisions as part of your compliance process.

The Rule Engine lets VASPs define automated policies for Travel Rule processing. It evaluates the information available when a Travel Rule message is created and gives your team a consistent decision to apply to the transfer.

Use this page together with the Travel Rule Risk Score, the end-to-end Travel Rule lifecycle, and Outgoing transactions guides.

What the Rule Engine evaluates

The Rule Engine can combine multiple decision inputs, including:

  • Travel Rule message status
  • Travel Rule Risk Score
  • transaction amount
  • whether a blockchain transaction hash is present
  • canonical counterparty entity and country information

Based on those inputs, the Rule Engine determines an action such as:

  • proceed with the transaction
  • wait for a defined time
  • review the transaction
  • block the transaction

The Rule Engine runs within CryptoSwift. Compliance teams can define and review policies in the Client Dashboard. Evaluation happens automatically when a Travel Rule message is created.

How the Rule Engine fits into the lifecycle

  1. Your VASP prepares a transfer and its Travel Rule information.
  2. CryptoSwift evaluates the applicable incoming or outgoing policy using the information available at that point.
  3. Your VASP applies the resulting proceed, wait, review, or block decision according to its operating procedure.
  4. If new counterparty information arrives later, your team reassesses the case and takes any required follow-up action.

For a waiting decision, define what should happen when the wait ends and who handles cases that require review. A later counterparty response may change the information available to the team, even after an initial decision.

Configure and review the policy

Compliance or operations teams can manage Rule Engine policies in the Client Dashboard.

Typical configuration principles:

  • rules define conditions and outcomes
  • rules can combine multiple variables in one policy
  • rules are versioned for change control
  • the active rule set is applied automatically during message creation

Test a proposed change

Use the Simulation service under the selected policy to test proposed and active policies against representative cases before relying on them in production workflows. Keep a record of who approved each change and what cases were tested.

When to use it

Use the Rule Engine when your VASP wants consistent decisions for cases that follow a defined policy. A common rollout path is:

  1. start with the post-transaction flow for broad compliance coverage
  2. introduce pre-transaction workflows for selected corridors or risk tiers
  3. automate repeatable decisions in the Rule Engine once the policy is stable

How the outcome appears in Travel Rule transactions

After a policy is applied, the resulting outcome is visible in the Travel Rule transaction detail view in the Client Dashboard. This lets operations and compliance teams see how the configured policy affected the transaction workflow.

Next steps