Skip to content

Travel Rule Risk Score

Understand how CryptoSwift derives the Travel Rule Risk Score for outgoing and incoming transactions.

The Travel Rule Risk Score provides a quick and reliable assessment of a transaction's risk profile. Use it as one input in your withdrawal and deposit decisioning, alongside transaction status, amount, counterparty data, and any Rule Engine policies you configure.

Outgoing transactions

For outgoing transactions, CryptoSwift determines the Travel Rule Risk Score based on the best counterparty context available at the time the Travel Rule message is created.

  • If the beneficiary VASP can be identified automatically, the risk score is based on that VASP's risk rating.
  • VASP risk ratings are provided by our AML compliance partner, Scorechain, and enhanced with CryptoSwift's internal scoring for verified VASPs.
  • Verified VASPs within the CryptoSwift network are always assigned the lowest possible risk score.
  • If the beneficiary VASP cannot be identified at the time of transaction creation, the Travel Rule Risk Score defaults to the destination wallet's risk score.
  • The destination wallet risk score is calculated using KYT (Know Your Transaction) data from our integrated AML providers, Scorechain and AMLBot.

This means the outgoing score can be based either on the identified beneficiary VASP or, when that context is not available yet, on the destination wallet.

Incoming transactions

For incoming transactions, the Travel Rule Risk Score is always based on the originator VASP's risk rating.

  • Originator VASPs may be part of the CryptoSwift network or integrated partner Travel Rule networks.
  • For verified VASPs within the CryptoSwift network, the risk score is assigned directly by CryptoSwift.
  • For VASPs outside the CryptoSwift network, the risk score is provided by our AML compliance partner, Scorechain.

How to use the score

The Travel Rule Risk Score is designed to support operational decisions, not replace them. Typical uses include:

  • allowing low-risk transactions to proceed automatically
  • sending medium-risk transactions to manual review
  • blocking or escalating high-risk transactions

Combine it with the end-to-end Travel Rule lifecycle, Outgoing transactions, Incoming transactions, and the Rule Engine when building your decision workflow.

Next steps