> ## Documentation Index
> Fetch the complete documentation index at: https://docs.algovoi.co.uk/llms.txt
> Use this file to discover all available pages before exploring further.

# Travel Rule

> FATF Travel Rule (Recommendation 16) as signed, no PII, post quantum confidential evidence exchanged between VASPs, with a Falcon-1024 signed receipt.

<Note>
  **Also in the on-prem suite.** This product is included in the [AlgoVoi Compliance and Payments On-Prem Suite](/substrate-2), one commercial licence that unlocks and runs the complete self-hosted platform.
</Note>

<Info>
  **Free for every Substrate 2 customer.** Travel Rule is included at no additional charge — any valid
  AlgoVoi suite licence unlocks it. There is no separate purchase.
</Info>

## What it is

Every regulated VASP must exchange originator/beneficiary information for crypto transfers above the
FATF de-minimis threshold — and be able to **prove** it did. **Travel Rule** does both the AlgoVoi way:
the regulated data is exchanged **post-quantum** between VASPs, and what you keep is a
**Falcon-1024-signed receipt that contains no PII** and verifies offline.

It is the compliance-evidence layer for [FATF Recommendation 16](https://www.fatf-gafi.org/), built on
the same discipline as the rest of the suite — content-addressed, signed, offline-verifiable — and it
binds into the [Substrate 2](/substrate-2) evidence chain alongside [Compliance Gate](/compliance-gate-v2)
and [Proofs](/proofs).

<CardGroup cols={2}>
  <Card title="No PII in the receipt" icon="eye-slash">
    The originator/beneficiary data goes VASP-to-VASP; the receipt carries only
    `ivms101_hash = sha256(JCS(ivms101))`. Hand a regulator the proof, not the customer's data.
  </Card>

  <Card title="Post-quantum exchange" icon="atom">
    The IVMS101 payload is sealed to the counterparty VASP's **ML-KEM-1024** key (+ AES-256-GCM) — the
    PII is confidential *and* quantum-resistant on the wire. Receipts are Falcon-1024 signed.
  </Card>

  <Card title="Applicability, on the record" icon="scale-balanced">
    Above the configured de-minimis the rule applies, below it doesn't — and the determination is part
    of the signed receipt, not a side note.
  </Card>

  <Card title="Offline verification" icon="plug-circle-check">
    Verify the receipt from the issuing VASP's public key alone; the recipient confirms the decrypted
    IVMS101 hashes to the receipt — binding data to attestation with no PII in the attestation.
  </Card>
</CardGroup>

## What you get

* **Proof without disclosure.** A signed Travel Rule receipt you can show a regulator or counterparty
  with **no customer PII in it** — the evidence the obligation was met, not the underlying data.
* **Post-quantum confidentiality.** The IVMS101 exchange is ML-KEM-1024 + AES-256-GCM; receipts are
  Falcon-1024 signed — quantum-resistant on the wire and in the signature.
* **Transport-agnostic.** Emits and verifies the evidence; plug it into TRP, TRISA, or any messaging
  rail you already run. AlgoVoi never holds your customers' data.
* **Substrate 2-bound.** Each Travel Rule receipt folds into the broader Substrate 2 evidence chain
  next to your compliance and settlement receipts.

## How it works

| Step          | What happens                                                                                                                                                                     |
| ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Determine** | Is the transfer at/above the FATF de-minimis? The rule applies — or it doesn't — and the determination is signed in.                                                             |
| **Exchange**  | The IVMS101 originator/beneficiary payload is sealed to the beneficiary VASP's ML-KEM key and sent — confidential, post-quantum.                                                 |
| **Certify**   | A Falcon-1024-signed receipt records the transfer ref, the VASP DIDs, `ivms101_hash`, the threshold determination, and the result (`PREPARED / SENT / RECEIVED / ACKNOWLEDGED`). |
| **Verify**    | The counterparty checks the signature offline and confirms the received IVMS101 hashes to the receipt — binding data to attestation. No PII in the receipt.                      |

## Cryptography

* **No-PII receipts.** The receipt's only reference to the regulated data is `sha256(JCS(ivms101))`.
* **Post-quantum exchange + signature.** IVMS101 payloads are sealed with **ML-KEM-1024 + AES-256-GCM**;
  receipts are signed with **Falcon-1024** (NIST Level 5) and verify offline.
* **Content-addressed + canonical.** `canon_version: jcs-rfc8785-v1`; everything is bound by JCS
  (RFC 8785) canonical bytes, so the same receipt verifies byte-identically anywhere.

## Who it's for

* **VASPs, exchanges, and PSPs** that must meet FATF Recommendation 16 and evidence it to a regulator.
* **Compliance / MLRO teams** that need a provable Travel Rule trail **without retaining PII in the
  evidence**.
* **Anyone exchanging IVMS101** who wants the data confidential post-quantum and the proof portable.

## Get Travel Rule

Travel Rule is **included free for every Substrate 2 customer** — any valid AlgoVoi suite licence
unlocks it; install it from the private index and it runs alongside the rest of your suite. It pairs
with [Compliance Gate](/compliance-gate-v2) (the screening verdict) and [Proofs](/proofs) (privacy-
preserving proof) as a complete compliance-evidence story.

<CardGroup cols={2}>
  <Card title="Talk to us" icon="envelope" href="/trial-and-pricing">
    Already a Substrate 2 customer? Travel Rule is included — we'll help you wire it into your VASP
    messaging rail and choose your de-minimis policy.
  </Card>

  <Card title="The compliance suite" icon="user-shield" href="/compliance-gate-v2">
    Compliance Gate → Proofs → Travel Rule: screen, prove, and meet the Travel Rule — all signed, all
    no-PII, all offline-verifiable.
  </Card>
</CardGroup>