Skip to content

Rule Engine

Automate pre-transaction Travel Rule decisions with policies configured in the Client Dashboard.

The Rule Engine lets VASPs define automated policies for Travel Rule processing before funds move. It evaluates the data available when a Travel Rule message is created and returns an action your application can apply immediately.

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
  • counterparty information
  • wallet context
  • other variables available to CryptoSwift at message creation time

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 configure policies in the Client Dashboard, and the evaluation happens automatically when a Travel Rule message is created.

How the Rule Engine fits into the lifecycle

  1. Your VASP creates a Travel Rule message before sending the blockchain transaction.
  2. CryptoSwift validates the payload, routes the message, and evaluates the Rule Engine policy.
  3. The synchronous response returns the Travel Rule message status together with the decision data available for that workflow.
  4. Your application applies the outcome and either proceeds, waits, reviews, or blocks.
  5. If the transaction proceeds, your VASP later updates the Travel Rule message with the blockchain transaction hash.

If your rules include waiting logic, asynchronous updates still matter. A later counterparty response can change the final outcome, so keep webhook or polling handlers active even after the initial decision.

Configuration in the Client Dashboard

Rule Engine rules are configured in the Client Dashboard by compliance or operations teams.

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

Simulation service

Use the Simulation service under the selected policy to test published and draft policies before relying on them in production workflows.

When to use it

Use the Rule Engine when you want pre-transaction automation without hard-coding every policy into your own withdrawal service. 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. move those pre-transaction decisions into 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.

The same calculated outcome is also accessible via the API for every Travel Rule message. Your backend services can use it to make decisions and execute the next steps based on the applied policy.

Next steps